Transmit
This page documents the transmit configuration
Table of Contents
Configuration file fields
This section is autogenerated from the Rule Schema file.
Name lin.transmit.items.name
Optional transmit rule name.
Type |
Max length |
|---|---|
string |
16 |
State lin.transmit.items.state
Disabled transmit rules are ignored.
Type |
Default |
Options |
|---|---|---|
integer |
1 |
Disable: |
Frame ID (hex) lin.transmit.items.id
Type |
Max length |
|---|---|
string |
2 |
Data (hex) lin.transmit.items.data
Type |
Max length |
|---|---|
string |
16 |
Configuration explained
This section contains additional information and examples.
The interpretation of the transmit list depends on the configuration of LIN bus mode:
Publisher mode
The number of bytes entered in the data field determines the interpretation of the transmission frame:
Length of data is zero
The transmit is a SUBSCRIBE frame, meaning that a Subscriber on the bus is expected to provide the data payload (satisfying the frame table).
Length of data is above zero
The transmit is a PUBLISH frame, meaning that the CANedge provides the data payload.
In Publisher mode, the CANedge schedules the frame transmissions configured by the period and delay.
Warning
Be aware that transmit uses period and delay to schedule transmissions. This is a different concept than what is used by LDF files.
Subscriber mode
In Subscriber mode, the CANedge awaits a SUBSCRIBE frame with a matching ID from the bus Publisher node. The number of bytes provided shall satisfy the frame table.
Warning
If the transmit list contains multiple frames using the same ID, then only the first entry is used.