LV 7.0 ctr/dig vi won't mult thread from TS.Works fine from another VI

[ChrisBurg]

I am having a problem with a TS 3/LV 7 integration issue. I have a VI that runs fine when called from another VI, but will not work when called from TS 3.0. The VI runs two parallel paths. One path configures a counter to capture a pulse width, then "sends" a Notification releasing the other path toggle a couple of dig lines that cause the pulse to occur. When run from TS, the path that toggles the dig bits, never seems to get the notification before the DAQmx read times out.

[Ryan Ramcharan]

Hi Chris,

Perhaps a very simple example (i.e. minus the DAQ elements) of what you are trying to do would be helpful. Thanks!

Bob

[RACEMAN]

Did you solve this problem? I am currently having the same issue. I developed a LabVIEW test that used DAQmx and within the VI it has multiple threads, works fine. When called in Teststand it does not work. It almost seems as though teststand will only allow LabVIEW to run single threads.

If you found out the solution to this please post it.

Thanks

[Ryan Ramcharan]

Hi All,

Have you tried changing the execution system of the VI that is called by TestStand to be something other than User Interface or Same As Caller? Try setting it to Other 2 and let me know what happens. To this,
load the VI in LabVIEW. Right-Click the VI Icon on the top right of the VI front panel. Select VI Properties. Then choose Execution from the Category ring control. Change the Preferred Execution System from Same as Caller to Other 2. Save the VI. Run the TestStand sequence. Let me know if this works.

Ryan
NI

[RACEMAN]

Figured it out, after contacting NI, thanks for completing the thread.