Raptor:LIN Trigger: Difference between revisions
Jump to navigation
Jump to search
(Created LIN Trigger Page) |
No edit summary |
||
| Line 12: | Line 12: | ||
{| class="wikitable" style="width:100%;" | {| class="wikitable" style="width:100%;" | ||
|- | |- | ||
! scope="col" style="width: | ! scope="col" style="width: 20%;"|Output | ||
! scope="col" style="width: 10%;"|Type | ! scope="col" style="width: 10%;"|Type | ||
! scope="col" style="width: 70%;"|Description | ! scope="col" style="width: 70%;"|Description | ||
Revision as of 17:55, 9 April 2018
Return to the main Raptor page
Description
The LIN trigger block can be used with LIN transmit and receive. The Frame field provides the message on which the trigger is associated. For LIN Receive, the trigger is fired each time the message is received from a slave node. For LIN Transmit, the trigger is fired immediately before the message is transmitted. Placing the LIN Transmit block inside the subsystem called by the trigger allow for values to be updated immediately prior to transmit. Multiple LIN trigger blocks can be associated with the same LIN frame.
Outputs
| Output | Type | Description |
|---|---|---|
| Fn | FnCall | Function call output |
Parameters
| Parameter | Type | Description |
|---|---|---|
| Frame | Identifies the frame that the trigger will be associated with. | |
| 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 | Number | Positive integers that determine the order for multiple trigger blocks of the same mailbox to be called. Triggers are executed from lowest to highest priority. |