Raptor:App Trigger: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
|- | |- | ||
|Fn | |Fn | ||
| | |FnCall | ||
| | |The function call. | ||
|} | |} | ||
| Line 37: | Line 37: | ||
!Trigger | !Trigger | ||
| | | | ||
| | |The trigger period at which the output runs. | ||
|- | |||
!This trigger is inside another triggered subsystem. | |||
|checkbox | |||
|When checked, this indicates that the block is inside another triggered subsystem. | |||
|- | |- | ||
!Always enabled even when containing system is disabled. | !Always enabled even when containing system is disabled. | ||
| | |checkbox | ||
| | |When checked the trigger block will continue to operate even if the subsystem in which it is contained is disabled. | ||
|- | |- | ||
!Priority | !Priority | ||
| | | | ||
| | |Positive number which determines the order in which multiple trigger blocks for the same trigger are called. Triggers are executed from lowest to highest priority. This option does not work for simulation. | ||
|- | |- | ||
!Trigger Name | !Trigger Name | ||
| | | | ||
| | |A unique name for this trigger. The name must be a valid C identifier. | ||
|} | |} | ||
Latest revision as of 13:09, 12 September 2023
Return to the main Raptor page
Description
This block allows certain base timed trigger periods to be modified. New periods can be specified in 1ms resolution. This block is target dependant. Place this block in a model with a target definition block and then enter the block's help again for more specific help.
Inputs
| Input | Type | Description |
|---|
Outputs
| Output | Type | Description |
|---|---|---|
| Fn | FnCall | The function call. |
Parameters
| Parameter | Type | Description |
|---|---|---|
| Trigger | The trigger period at which the output runs. | |
| This trigger is inside another triggered subsystem. | checkbox | When checked, this indicates that the block is inside another triggered subsystem. |
| Always enabled even when containing system is disabled. | checkbox | When checked the trigger block will continue to operate even if the subsystem in which it is contained is disabled. |
| Priority | Positive number which determines the order in which multiple trigger blocks for the same trigger are called. Triggers are executed from lowest to highest priority. This option does not work for simulation. | |
| Trigger Name | A unique name for this trigger. The name must be a valid C identifier. |