viSci

Are you suggesting that the problem was non-uniform application of the pointer-sized integer CLFN parameters?

It crashes running any of the included examples. It seems to be able to open a reference to the .db but any queries crash.

I did try the latest sqlite dll from SQLite.org and also adding the AES symbol to the project but still crashes.

Thanks. I have already started porting to JDP SQLite. I should have done that a long time ago.

That is considerably more modern then my v1.3.1, I would give it a go if you could make it available...

I realize this SQLite LIbrary (by ShaunR) is pretty ancient so not surprised there maybe some dll updating required but I thought I would inquire. I have used it many times in the past and have come to appreciate its performant well crafted design.

In case anyone else runs into the issue...

In LV 2025 the ability to open reentrant clones on the cRIO is supported in the LV IDE. I have confirmed that I can open the front panel and probe the BD of reentrant clones running on my cRIO with Linux RT. There is a bug however that inhibits this ability until the execution properties window of the reentrant vi is opened and the code restarted.

Experiencing strange behavior on a cRIO where I have a heater controller that uses 3 PID vi's. The execution properties of the PID vi's are set to Preallocated clone Reentrant. When running from the project the individual PID vi's do not initially open as clones. Only after opening the properties and then restarting do things start working properly. This is a repeatable issue that reoccurs each time the code is deployed to the cRIO from the project. I suppose I could just save the PID vi multiple times with different name but that is a poor solution and cumbersome since the PID vi is in the NI_PID_autopid.lvlib.

Just to wanted add another voice to the LuaVIEW fan club. LUA is an excellent scripting language and LuaVIEW is an excellent integration with LV. Keep hoping you might see the advantages of open sourcing it to the LV community.

Noticed that MGI RWA does not seem to work when clusters contain things like IMAQdx refnums. Seems like the default Major Vers will always be 1 which is incorrect and causes conversion back to variant problems downstream. When I changed the default of the Scan String first parameter to 2 then it works fine. This is my cluster that I am trying to work with. The problem occurs with the IMAQdx refnum control.

Bridgeview? You must be old as the hills I think if back then they had our modern DDS options We would have never had to suffer NSV’s and the product might be still viable today.

Remember the venerable DSC toolkit? For its time it was a well thought out collection of SCADA tools, historical database, distributed systems manager, Network tag engine, etc. Now that we are NI/Emerson can we hope for a modern version of this? Sans Network Shared Variables of course! I suppose there is Systemlink but I am not sure that really covers SCADA usecases.

The Sequence Toolkit looks like a nice alternative to TestStand that I personally would like to see more of. I doubt there is any copyright infringement here.

Is it possible to use TestScript as a type of test sequencer in LabVIEW where the UI can display the 'script', which would be python code, and be able to run in single step mode or at least be able to highlight the current python line being executed.

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