NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Teststand calls all threads fine, Labview OI does not..

Hello all,
Thanks to the many help provided on this forum, I was able to create a Labview OI and a Teststand seq. file for my application. However, there is something weird happening that has baffled us all.
The TS seq. file has 5 parallel threads running in a sequential process model for approximately 1 minute. After a minute, all of them stop simulatenously. Now among the 5 threads is a DAQmx-Simulink simulation modeling that simulates the motor dynamics of an automobile. This particular thread executes fine in the TS environment, and cleanly shuts down after execution.
Now, when I load the entire sequence file onto my LV 7.1 OI, the DAQmx-Simulink model fails to execute and gets stuck at AO Read, thereby stalling the completion of the entire process. This same seq. file again works just fine in the TS environment. It used to work earlier during the day, and after some modifications in the TS .seq files, we tried it again..and it would not work at all. I didn't make any changes in the OI code.
Can someone please suggest, why this could happen? I've reached a dead end and can't think of any reason
Many thanks in advance,
Anshul
0 Kudos
Message 1 of 2
(2,780 Views)
Hello Anshul,

I would recommend trying to narrow down the problem to a more simple situation. If possible, I would see if you can run your sequence through the OI that ships with TestStand. If that works correctly, then the issue is likely being caused by programming in the custom OI. If that still does not work, I would modify the client application to only have the one thread that is not behaving correctly. Incrementally try to make the code as simple as possible, removing as much extra programming as you can.

Thank you for contacting National Instruments. Please write back when you have more information about the problem. If you are able to narrow it down enough so that it can be replicated on another machine, that would be optimal (but may be impossible if the error is linked to hardware or 3rd party software that our Applications department does not have access to). Take care and good luck!

Regards,

Aaron B.
National Instruments
0 Kudos
Message 2 of 2
(2,774 Views)