I am trying to have a more precise control over the thread management in LabVIEW.
Basically I would like to have a dedicated thread in which my loop executes the code.
The simple answer would be Timed Structure, as it does what I need and also allows the control over CPU management.
Normally I would end here but there are two problems with this answer.
1. The numer of Timed Loops is limited (I need quite a lot of them)
2. The RT palette is not available for non-rt linux environment which I am planning to use (or is there a way to have it on non-rt linux?).
The question is: is there a way to "reserve" a thread in LabVIEW for a particular piece of code in the way as the Timed Loop does it?
Somehow I assume that under the hood Timed Loop just tells compiler to book a thread for it and not share it with other pieces of application and there possibly is a way to do the same thing but it is very well hidden under the Timed Loop implementation. So in essence the timed loop is just a wrapper for something we could normally leverage as an experienced lv programmers (again just an assumption).
I already read through a couple of white papers on that.
I also saw a very similar thread to mine but without actual answer being provided: https://forums.ni.com/t5/LabVIEW/How-to-manage-threads-in-LabVIEW-or-have-exclussive-access-to-a/m-p/4284877#M1250104