STOPPED
Overview
The STOPPED Action is called after the STOP Action to indicate if a process has indeed stopped.An Action may use a Value and an Address
Value: optionally the SyncID of the object that was stopped.
Address: not used.
Details
The STOPPED comes in handy for data sources that take a long time to stop, or that may fail to stop. The STOPPED Action is called if the stopping procedure has been finished successfully, or if a starting procedure has failed.The STARTING, STARTED and STOPPED Actions are automatically called from within a number of operators, although you may also use them in your project to indicate that a certain process has started or stopped.
Example: STARTING, STARTED and STOPPED_Demo
Demonstrates what the action STARTING, STARTED and STOPPED can be used for. In this demo a spike is shown in a signal whenever one of these actions is 'heard'. You may also specify the SyncID of the object that is started, so that the spike is only shown when that object is started or stopped. Of course, normally you would not use this with a Signal Generator, because it starts immediately. But you may have a device which may fail to start, or which takes a long time to start. In that case you may use these actions to verify if a device is started.Examples\DF0407022_001_STARTING_STARTED_STOPPED_Demo.xmc