03-20-2008 06:16 PM
03-20-2008 06:22 PM
03-20-2008 07:51 PM
03-21-2008 09:24 AM
Yes as Herbert indicated an example would help.
Wild guess flows.
Is the AE going idle before ther read?
LV cleans up resources of VI's that go idle so make sure the AE is is in a VI that remanis running.
Done guessing.
Ben
03-21-2008 11:32 AM
03-26-2008 09:21 PM
03-26-2008 11:20 PM - edited 03-26-2008 11:21 PM
03-27-2008 10:42 AM
...I am just running it by itself, selecting an action and then hitting the run arrow (i.e. it's not a subVI within a main VI that is constantly executing). I thought that would maintain a valid reference...
03-27-2008 01:44 PM
Thanks Guys!
I figured that LV must be tossing the refnum. I use Action Engines for DAQ tasks all the time and the tasks remain in the shift register just fine as I test them stand-alone. I thought I'd done it before with refnums but I guess I was mistaken. LV and Learn!
K
03-27-2008 01:50 PM
FYI: that trick only works with DAQ tasks based on the legacy driver, aka "Traditional NI-DAQ." The newer DAQmx driver does the same kind of cleanup on its tasks that you saw with the file refnums. Forewarned is forearmed.
I also used to test my DAQ Action Engines in stand-alone mode with the legacy driver. That was how I first started the habit of making a separate action-engine-tester vi.
-Kevin P.