Raptor:Transport Protocol
Return to the main Raptor page
Return to Transport Protocol page
Description
The transport protocol block is similar to the Raptor CAN Definition block. This block will include the Raptor J1939 protocol stack in your model. This is necessary to facilitate all J1939 communication. The J1939 bus name defined in this block will be used in all other Raptor J1939 blocks to link the block to a specific J1939 bus. Multiple transport protocol blocks can be included on the model to facilitate J1939 communication on multiple CAN buses or on a single CAN bus with multiple addresses. The transport protocol block must be inside a periodically triggered subsystem. It is recommended that the block be inside a subsystem executing at the Foreground loop rate in order to best maintain the timings required for J1939.
Inputs
| Input | Type | Description |
|---|
Outputs
| Output | Type | Description |
|---|
Parameters
| Parameter | Type | Description |
|---|---|---|
| Physical CAN Bus Name | The name of the CAN bus that the J1939 protocol will communicate on. | |
| J1939 Bus Name | This is the name of the J1939 bus being defined. | |
| Source Address | The default source address. | |
| Transmit Queue Size | The maximum number of messages which can be queued for transmission at the same time. | |
| Receive Queue Size | The maximum number of multi-frame messages which can be received at the same time. | |
| Max Message Length | The maximum supported length of a multi-frame message. | |
| SPN Custom Field Name | Defines the name of the Raptor OBD Fault Manager Custom field which defines the SPN of the fault. Data Type must be uint32. | |
| FMI Custom Field Name | Defines the name of the Raptor OBD Fault Manager Custom field which defines the FMI of the fault. Data Type must be uint8. | |
| Occ Counts Custom Filed Name | Defines the name of the Raptor OBD Fault Manager Custom field which defines the occurred count of the fault. Data Type must be uint8. |
Supported Versions
- Raptor 2013a_0.0.1 and newer