Raptor-Dev-LIN-Library
New Eagle > Products Wiki > Raptor Platform > Raptor-Dev > Raptor-Dev Library > Raptor-Dev-LIN-Library
Overview
The blocks in this subsystem can be used to send and receive message-based LIN messages. For more information regarding LIN, refer to our public white paper.
Blocks
| Block | Description | Appearance |
|---|---|---|
LIN Definition |
This block is used to create a LIN bus resource and map it to a particular hardware I/O point. This block will generate all of the code necessary to connect and coordinate all the Raptor™ LIN blocks with the hardware LIN interface. Each LIN bus that will be used in the model must include a LIN definition block. |
 |
LIN Rx Message |
The LIN Rx Message block uses a frame definition from the LDF file associated with the LIN Bus definition block to receive and interpret the frame on the specified bus. The reception is scheduled according to the LIN frame schedule. |
 |
LIN Tx Message |
The LIN Tx Message block uses a frame definition from the LDF file associated with the LIN Bus definition block to transmit the frame on the specified bus. The transmission is scheduled according to the LIN frame schedule. |
 |
LIN Trigger |
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. |
 |