@Mads wrote:
Nothing obvious in the framework itself, perhaps something is building up in any of the many missing subVIs...Have you tried logging which states are executed and their execution time...Just streaming it to an open text file e.g., to see if any particular parts are slowing down and at which rate? If any of the underlying functions are building arrays, reopening resources, files etc? There is a save to file function that might indicate that you are budiling the content of that e.g...
I monitored the states and their execution time. Once the monitoring process starts, it's strictly "Idle" and "Monitor Establish Count Time" at the rate of 250ms at the beginning. But after about 1000 seconds, the loop starts to slow down.
The save to file function is not building any file in LabVIEW. It is simply retrieving a file from the instrument over http and writing to a local file.. all done in Python. As I mentioned earlier, there are no arrays being built. No data is being accumulated in LabVIEW. All data is on the instrument.
Could it be some limitation on the rate or duration of opening and closing Python nodes? Every 250ms when the state changes to "Monitor" the Python node is opened to execute the Python function.
