LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

accessing a queue in multiple loops?

Big thanks to all, I implemented a second queue, and it actually cleaned up the code if anything. I like the idea of bundling the queues and will keep that in mind if I add much more to this. I am not familiar with the action engine, but will look into that.

I really like the event structures example, had I seen that before I started this, I may have done it differently, but will definetely study it more. One of the problems I had in my original design was an event structure within a read loop, which at the time appeared to not work, although it probably would have using those examples. I would be concerned with the speed though, and perhaps missing events (thus missing data). My sample rates vary between 10k and 3M, would this still be viable?

0 Kudos
Message 11 of 12
(832 Views)

See this Nugget on Actgion Engines to get you started.

"My sample rates vary between 10k and 3M, would this still be viable?"

As long as you process your data in "chunks" and your code is efficient (very loaded word Smiley Wink ) you should be OK. 10K loop rates are do-able in LabVIEW-RealTime. Looping faster is possible but also very challenging.

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 12 of 12
(825 Views)