NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Update Sequential Model Entry Points

In our test environment, we pretty much connect one UUT and either run it end-to-end (TestUUTs) or select individual tests and run them (in a debug mode).  We don't really have a need for the Single Pass entry point, but I'm wondering if it's worth the trouble to modify the process model.
 
The behaviour I'd like is to (1) Run and end-to-end test if the user selects TestUUT.  It would bring up a dialog that allows the user to either enter the serial number manually, or read it using a bar code reader.  At the end of the test, the results would display, and the user would NOT be prompted to enter another serial number.  In fact, it's quite typical that the same UUT would stay connected for a little while and either (a) tested again, or (b) individual tests would be performed to isolate some suspected problem.  That being the case, I'd like to modify the process model to
 
(1) Display a customized dialog for serial number entry allowing either manual or automated (bar code) entry,
(2) Run end-to-end, but not ask for the serial number of Next UUT
(3) Retain the information for the previously run UUT (at least while the same sequence file is loaded) so that if they decide to run again, they don't have to re-enter/scan the UUT information.
(4) modify the Single Pass entry point so that it instead runs the selected tests.
 
I know this is a fairly complex operation, but any guidance on 1-4 would be appreciated.  Thanks.
0 Kudos
Message 1 of 2
(3,021 Views)
(1), (2) is quite easy: The dialog is created within the PreUUT-Callback Sequence within the processmodel. Override it.
(3) You have to enter the correct "intelligence" for this within your sequencefile and processmodel. Since you always work within the same execution, the data is not "lost" after finishing one iteration. So either the next iteration will not change the data or you "refresh" it with the same values.
(4) "Run selected Steps" initiates an "Interactive Execution". This normally does not use a processmodel (but you can do that too). So this point is not too easy to solve since you can have two approaches:
a) Copy the selected steps into a temporary sequence and execute this with entry point "Single Pass" using the sequential model.
b) Start an Interactive Execution using correct parameters. This one is heavily based on the UI, so maybe not possible or at least no fun to implement (imho)

hope this helps,
Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 2
(3,000 Views)