Raptor:Application Monitor Stop: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 15: | Line 15: | ||
! scope="col" style="width: 70%;"|Description | ! scope="col" style="width: 70%;"|Description | ||
|- | |- | ||
! Pause | ! Pause | ||
| Boolean | | Boolean | ||
| When true the program is paused. | | When true the program is paused. | ||
Revision as of 19:52, 31 August 2016
Return to the main Raptor page
Return to Application Monitor page
Description
This block allows the user to pause the application when particular criteria are met in the program. When a true is passed in the input to this block it will cause the application monitor to pause the application. The trigger in which the stop block exists will execute to completion of the current cycle before pausing. All other triggers will pause immediately. This block requires the Raptor Application Monitor block to exist in the model.
Inputs
| Input | Type | Description |
|---|---|---|
| Pause | Boolean | When true the program is paused. |
Parameters
| Parameter | Type | Description |
|---|---|---|
| Tag Name | String | A name which uniquely identifies each application stop. The name will be shown in AppMonitorLastError if this stop is asserted. |