Bug in Teststand 2014 Simple UI Example ?

[aSquared]

Hi,

I am using Teststand 2014 and LabVIEW 2013 SP1.

I would like to create a UI for a Teststand sequence that I have created.

I have started with the Simple UI example (Source Code) shipped with NI.

Located at  - C:\Users\Public\Documents\National Instruments\TestStand 2014 (32-bit)\UserInterfaces\Simple\LabVIEW\Source Code

I have encountered with an unexpected behaviour - when running the User Interface VI and selecting a Sequence, it works fineat first, but if I Exit the application (the VI return to edit mode), I cannot run the application again until I close LabVIEW completely.

There seems to be more resources that are open.\\

Steps to reproduce - 

1. Create an Empty VI (called 1.vi for example)

2. Create a Sequence that only calls the 1.vi in the Main Group. (called 1.seq for example)

3. Open 'Build Script.lvproj' located at "C:\Users\Public\Documents\National Instruments\TestStand 2014 (32-bit)\UserInterfaces\Simple\LabVIEW\Source Code"

4. Open and run Top-Level.vi.

5. Click on 'Open Sequence File' and Select the 1.seq, Click on 'Single Pass' and the application should finish running the sequence (with the one VI in it) very fast.

6. Exit the application.

7. repeat on steps 4 and 5.

Am I missing something ?

When using the compiled application (exe), it works fine when called repeatedly.

I would like to be able to add changes to the VI and to be able to run it again and again... 

Amitai.

[RaviShrigiri]

Hi,

In the Labview adapter configuration there is a setting "Reserve Loaded VIs for execution".

Disable this and try.

Hope this helps.

Ravi

[aSquared]

Hi Ravi, 

Thanks for your reply,

I have tried your suggestion, but I see the same behavior.

the sequence is hang, and I need to kill LabVIEW process each time I make a change.

Amitai.

[RaviShrigiri]

Hi,

I tried with the same combination and did the exact steps to reproduce.

With the "Reserve Loaded VIs for execution" enabled i am seeing this :

After execution is completed if i click on close execution and close sequence file, the empty test vi is read only (reserved - not in edit mode)

However when i disable this :

After execution and clickingon "close execution" + "close sequence file" -- i can edit the test vi.

Probably i am missing something from the steps to reproduce?

Additionally did you observe this behaviour with other UI/Sequence editor?

Regards,

Ravi

[aSquared]

Hi Ravi, and thanks again for your reply.

Have you clicked on 'Exit' after "close execution" + "close sequence file" ?

When I press Exit and then run the Top-Level VI.vi again select the Seq file and Press 'Single Pass' it hangs.