Overview
When using LabVIEW to run real-time sequences associated with a particular VeriStand project, you must create a stimulus profile session to control the automation process. This example shows how to configure these sessions and how to respond to the events they generate.
Description
The non-legacy VeriStand Stimulus Profile API does not give us the opportunity to run stimulus profiles directly, so we must create a stimulus profile session to work with real-time sequences the VeriStand engine can execute. Once the session is deployed and running, we can programmatically detect different events associated with them: sequence complete, sequence state change, session complete, and session undeploy events (http://zone.ni.com/reference/en-XX/help/372846H-01/veristandmerge/events_pal/).
To demostrate working with stimulus profile sessions, this example uses the Engine Demo that ships with VeriStand. First the system definition file is deployed and then the stimulus profile session is configured. After the session deploys and runs, an event structure waits for the session to finish before undeploying both the session and the system definition.
*Note: Engine Demo Basic.nivsseq (which is used in this VI) has been modified to include two ByValue parameters, Power and TargetRPM.
Steps to Implement or Execute Code
Requirements
Software
LabVIEW 2014
VeriStand 2014
Hardware
Windows development machine
Additional Images or Video
Related Examples
Example code from the Example Code Exchange in the NI Community is licensed with the MIT license.
perfect example