NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Operator Interface

Solved!
Go to solution
In the Simple Operator Interface how would you hard code in a Sequence in the Open Sequence File window ?
0 Kudos
Message 1 of 12
(5,439 Views)
Solution
Accepted by topic author Clint Eastwood

Hi Clint Eastwood,

 

One way to do this is shown in the attached screenshot.  After the "Start" invoke node, you can place down an "OpenSequenceFile" invoke node (pass in a reference to the Application Manager) and then wire in your path to hard code.  This is just a string constant.  You can then place down a "SequenceFile" property node (pass in a reference to the Sequence File View Manager) and wire in the reference from the OpenSequenceFile output.  This will populate the sequence file combo box.

Cheers,
Kelly R.
Applications Engineer
National Instruments
0 Kudos
Message 2 of 12
(5,402 Views)

Thanks Kelly.  Can you stay tuned to see if it works??  I'll try it today or tomorrow.

 

Clint

0 Kudos
Message 3 of 12
(5,372 Views)

Hi Kelly,

May have spoke too soon.  The solution populates the hard coded seq in the "sequnce files" window when I 1st run it.  After I enter the user name and password it repopulates it w the last seq I ran.

 

Clint

0 Kudos
Message 4 of 12
(5,349 Views)

Hi Clint,

 

I have not reproduced this behavior on my system.  I would like to clarify, does this happen after you enter the user name and password initially, and after you do this,  it changes from "Test.seq" to a sequence that you ran previously in another run?  What version of TestStand are you running?  One thing that you could try is in the "Configure Application Manager" diagram, set the "ReloadSequenceFilesOnStart" to "ReloadFile_None."  I have attached a screenshot highlighting this property.
Cheers,
Kelly R.
Applications Engineer
National Instruments
0 Kudos
Message 5 of 12
(5,321 Views)

Kelly,

The Seq is on another machine in another building.  Give me some time and I'll send 3 screen shots.  One of the block diag.chg'd, one before I run the seq and one after I run it.

 

Thanks.

0 Kudos
Message 6 of 12
(5,274 Views)

Kelly,

I tried the "ReloadFile_None" and it appears to work.  Now I get this strange behavior where I get this overlay.  See attached.

To answer your earlier question.  Yes, I hit the RUN arrow.  The "Test2.seq" that I had hardcoded in appears in the Seq File Window.  Then I'm prompted for the TS User Name and Password.  When  I type those in and hit return it displays the previous seq ("Test1.seq") I ran in the Seq File Window.  This ReloadFile_None appears to work but now I have a different problem.

0 Kudos
Message 7 of 12
(5,257 Views)

Hi Clint,

 

Sorry for the slow reply.  I have been out of the office.  Have you seen this behavior on your machine at any other time (e.g. when you run the Simple OI without modification).  If not, we may have a timing issue.   What version of TestStand and LabVIEW are you using?  I haven't been able to replicate this on my system so far, but these parameters may help me.

Cheers,
Kelly R.
Applications Engineer
National Instruments
0 Kudos
Message 8 of 12
(5,118 Views)
This behavior only happens when I use the Source Code for OI.  Once I put it in a Project and create the exe it doesn't appear again....at least for now!
0 Kudos
Message 9 of 12
(5,108 Views)

Check your setting of ApplicationMgr.ReloadSequenceFilesOnStart property.

 

Sorry, I see you've checked this...

 

 

Message Edited by paulmw on 09-29-2009 01:39 PM
Message Edited by paulmw on 09-29-2009 01:40 PM
0 Kudos
Message 10 of 12
(5,091 Views)