REXGEN 2REXGEN 2 IMU GNSSREXGEN AirREXGEN ProDeveloper
REXGEN XML reference: LIN interfaces and messages
Set up the logger's LIN port and choose which LIN frames it listens to or answers.
LIN on REXGEN
REXGEN 2, REXGEN 2 IMU GNSS, REXGEN Air and REXGEN Pro each have one LIN channel. REXGEN 1 has none. A LIN setup uses two kinds of block: one LININTERFACE for the port and one LINMESSAGE for each frame or range of frames. Each takes a UID attribute (required and unique in the file) and the optional Version, X and Y.
Each entry in the settings lists gives the meaning, then whether the schema requires the element, its type and its default where one exists. For LIN itself, see LIN basics.
The LIN port (LININTERFACE_LIST)
LININTERFACE
This port listens as a slave on a 19,200 bit/s LIN 2.0 bus.
<LININTERFACE UID="16">
<PhysicalNumber>0</PhysicalNumber>
<MasterMode>false</MasterMode>
<BitRate>19200</BitRate>
<ProtocolVersion>V_2_0</ProtocolVersion>
<Time_Base>5</Time_Base>
<Time_Jitter>1</Time_Jitter>
</LININTERFACE>
PhysicalNumber- The LIN channel on the logger. Every model with LIN has one channel, so use
0. Required. Unsigned byte. MasterMode-
truemakes the logger the LIN master.falsemakes it a slave on a bus that already has a master. Required. Boolean. BitRate- LIN bit rate in bit/s, for example
9600or19200. Required. Unsigned short. ProtocolVersion- LIN protocol version of the bus:
V_1_3orV_2_0. Required. Time_Base- LIN time base in milliseconds, for example
5. Required. Unsigned short. Time_Jitter- LIN time jitter in milliseconds, for example
1. Required. Unsigned short.
LIN frames (LINMESSAGE_LIST)
LINMESSAGE
This message takes every LIN frame on the LIN interface with UID 16. LIN identifiers run from 0 to 63.
<LINMESSAGE UID="17">
<InterfaceID>16</InterfaceID>
<MessageIdentStart>0</MessageIdentStart>
<MessageIdentEnd>63</MessageIdentEnd>
<Respond>false</Respond>
<DLC>8</DLC>
<DefaultHex>12340000000000AA</DefaultHex>
<Delay>0</Delay>
<ScheduleTablePosition>0</ScheduleTablePosition>
<InputUID>0</InputUID>
<Name>Log All</Name>
</LINMESSAGE>
InterfaceID- UID of the
LININTERFACE. Required. Unsigned short. -
MessageIdentStart,MessageIdentEnd - Range of LIN identifiers the message covers, used for filtering. Required. Unsigned short.
Respond-
truemakes the logger answer the header for this identifier with its own data.falsemakes it listen. Required. Boolean. DLC- Number of data bytes in the frame. Required. Unsigned byte.
DefaultHex- Default data for the frame, two hexadecimal digits per byte, so 16 digits for 8 bytes. Optional. Type hexBinary.
Delay- Delay in milliseconds. Required. Unsigned short.
ScheduleTablePosition- Position of the frame in the schedule table when the logger is master. Required. Unsigned short.
InputUID- UID of the block that supplies the data the logger sends, or
0for none. Required. Unsigned short. Name- A name for the frame. Optional. String.
LIN signals and recording
The schema also defines LINSIGNAL, which mirrors CANSIGNAL (start bit, bit count, byte order, signal type, factor and offset) for values inside LIN frames. It is not documented here yet. For how the shared fields work, see REXGEN XML reference: CAN messages and signals.
The simplest way to record LIN and decode it with an LDF file is REXDESK. See REXDESK: record CAN, CAN FD and LIN.
Common mistakes
- Putting the bit rate in
PhysicalNumber. It holds the channel,0. - An odd number of digits in
DefaultHex. Each byte takes two. -
MasterModetrueon a bus that already has a master. Two masters send colliding headers.
Next: REXGEN XML reference: analogue, digital, IMU and GNSS inputs.
Products in this guide
Still stuck?
Our engineers answer support questions on every Influx Technology product.