viSci

Nicely described approach Shaun. I am doing something similar with a lab automation project that involves vacuum chamber and multi-zone temperature control. Elected to use the messenger framework, which supports 'spinning up' instances and TCP capability for remote devices like cRIO. The messenger architecture also supports many types of asynchronous messaging beyond simple synchronous command/response. Your idea of decoupling EC sequencing logic is good, moving it out of the EC subsystem to allow synchronization with other subsystems during ramp/soak profiles. Hey remember Test Stand Lite? This is where an such a scripting component would really shine and be a great benefit to the community.

I wonder, would it be possible to use your SQLite Logger to extend the messenger library to have a logging capability similar to the Worker Framework Message logs. https://docs.workersforlabview.io/workers-tools/workers-tools-menu/workers-debug-server/worker-message-logs

Apologies for the bad example. GrokAI emphasized the importance of closing .net references which I blatently disregarded

Example of camera grab using the Pylon .net API. (Credits: GrokAI)

Asked GrokAI and got a working example...

Hi Yair - Would you mind sharing some example code to grab an image using the Pylon .net interface?

Or this...

A customer asked me to create a powerpoint explaining the advantages of LabVIEW. While putting together the practical rationales, just for grins I asked Chatgpt to create a presentation explaining the philosophy of LabVIEW in a Zen sort of way. Here is what it came up with. Zen_of_LabVIEW.pdf

The Gpower IOLink toolkit looks great but the cost is prohibitive. For $1000 I was inclined to give it a go but I would never saddle up to such a cost on a subscription basis and as you said they are also requiring a annual runtime license. What a disaster that would be for any of my customers when their critical systems stop working on Jan 1st. until they pony up their subscription fees. I think like you I will just dip my toes in the RESTful JSON waters and then see what it will take to generalize it.

Now that we are NI/Emerson I would expect to see more connectivity in the automation sector. It seems that IOLink is a dominate communications standard that would be a good candidate for support in LabVIEW. IFM is one company that makes a ton of really cool sensors and networking hubs that are largely IOLink capable. It should be relatively straightforward to develop a restful IOLink interface using GET/POST with JSON formatted commands. I am planning on doing this and was wondering if anyone has gone down this path before. https://www.ifm.com/us/en/shared/technologies/io-link/select-products/product-configuration-pages/dataline-tee-cable-wiring

What! Does lvserial acutally support regex termination strings? How is that accomplished? Is that capability built into an interrupt service routine or is it just simulated in a polling loop under the hood?

This one slipped under the radar but I think is finally a viable starting point for an open source TestStand Lite that was imagined many years ago. https://github.com/Tom-Lu/TestLite

Anyone know what ever happened to the late great LuaVIEW framework. I used it many moons ago and have an application for a scripting language that interoperates well with LV.

Wondering if anyone has tried to use this LUA wrapper library. It looks very promising and would be a great open source scripting tool for the LV community. https://github.com/antonie-coetzee/GLue See attached pdf documentation MLua Help.pdf

Later this afternoon I plan on remoting into the server. Could you suggest a specific MSC runtime to try?

Greetings, a long running LV 2018/2020 app was recently migrated to run on windows server 2019 and am finding that I can no longer initialize the python script server. I have verified that my python 2.7.6 (32 bit) is installed correctly (BTW, it coexists with python 3.1 which needs to be on the machine for another non LV app). I have tried the usual things like running as admin, checking folder permissions, etc to no avail. Any ideas?

Finally able to create a USB boot disk using a great program called Rufus and an iso image called Rescatux which like Hiren, is a pocketknife of tools and utilites to repair broken Linux and Windows installations. Thanks for all you help. I was able to reset the WES7 password. BTW - One thing that confounded me for awhile was that when the USB boots it presents as a blank desktop screen until a <CR> is entered on the keyboard at which point the USB drive becomes active again and finally starts running the iso software.

Now that i am looking more closely at the NI LInux recovery boot, I can see that the status led is also flashing orange so I guess that is normal. Perhaps the Hiren boot with a windows 2000 image was booting but not able to display with its video driver.

Tried your suggestion using Hiren Boot CD as well as several other similar boot loaders. The cDAQ restarts, is accessing the USB, then the status led blinks orange continuously indicating a boot error. Interestingly I tried using the NI Linux realtime recovery files I had on hand from another project and it actually booted to some sort of quasi linux command prompt. The NI recovery tool uses something called grub which I found is an open source linus boot loader.

I have been given a cDAQ 9137 to reprogram and found that there is a forgotten windows password on this computer. I have tried getting to the bios (F10 or Del) but cannot even get that to work. Called NI but they were no help at all. Anybody have any advise other than reformatting and trying to reestablish the WES7 OS?

Two of the most consummate software architects (AQ and Jack Dunnaway) in league with the worlds greatest technology visionary (Elon), so there is much to be optimistic about. Let's make LabVIEW multi-planetary and beyond...Ad Astra!

It appears that in a built application, the Undo from the App menu works for all UI control value changes.

I seem to remember that at one time the LV runtime did support a basic Undo functionality.

I have found that disabling the Nagle algorithm (using Visa Property TCP NoDelay) greatly improved the responsiveness of my tcpip communications and alleviated intermittent lockup between the raw socket ping and my TCPIP transactions.