01-07-2013 03:59 PM
Your loop time will be 0.3 seconds plus the time to run the other code (ULx Read, etc)
You don't have the timeout wired to ULx read, so you don't know how long that subvi is running.
From the ULx read help:
timeout specifies the amount of time in seconds to wait for samples to become available. If the time elapses, the VI returns an error and any samples read before the timeout elapsed. The default timeout is 10 seconds. If you set timeout to –1, the VI waits indefinitely. If you set timeout to 0, the VI tries once to read the requested samples and returns an error if it is unable to.
01-07-2013 04:56 PM
So what exactly do I have to do for the indicator to show realtime values?
01-07-2013 05:11 PM
Show your latest updated code so we can see how you've incorporated it the changes.
01-07-2013 05:16 PM
here ya go,
01-08-2013 07:43 AM
How fast will they update if you remove the elapsed timer?
01-08-2013 07:59 AM
I tried that, there's so set time. Like I said before, the indicator values update intermittently, even when I remove the elapsed timer.
01-08-2013 08:24 AM
How often is "Intermittently"? If you remove the elapsed timer, then something else in the loop is controlling the update rate and the iteration speed of the entire loop. It could be the acquisition settings you are using for the DAQ device.
01-08-2013 08:47 AM
It seems to come through the indicator every 11 seconds or so. I'm using 25000 samples per channel, continuous samples, with onboard clock, as seen in the VI.
01-08-2013 08:49 AM
I'm using a MCC usb-1608fs
01-08-2013 09:46 AM
Here's a cleaned up version without the file save option. Run it and see if it is faster/better.
I don't understand your logic, so I'm not making any guarantees that the codes runs correctly.