100BASE-T1 SPY 12 Port
User Manual
42
4.4
Structure of the LIN payload
The following table shows the structure of a LIN payload encapsulated in a
100BASET1_SPY RAW frame:
Field Name
N
º
of Bytes
Value
Error Field
1
Contains information about the LIN reception
error state
Identifier
1
Received LIN Identifier
LENGTH
1
Length of the LIN frame payload (in bytes)
PAYLOAD
1 to 8
Received LIN Payload
Checksum
1
Received LIN checksum
Zero Padding
X
Table 4-7: Content of LIN Pay Load Encapsulated in 100BASE-T1_SPY_12_Port Raw Frame
Note:
The Error Field byte contains the following information about the LIN reception
state:
7
6
5
4
3
2
1
0
Reserved
Reserved
Reserved
Reserved
Reserved
Parity-
Error
Collision
Error
Checksum
Error
Table 4-8: LIN Reception State byte
•
Checksum Error:
A ‘1’ value in this bit indicates if there was a checksum error
during the reception of the LIN frame.
•
Collision Error:
A ‘1’ value in this bit indi
cates if there was a collision during
the reception of the LIN frame. In this case, the received payload is not valid.
•
Parity Error:
A ‘1’ value in this bit indicates if there is a parity error in the
Protected ID.
Note:
If the LIN Port is working as SPY/SLAVE, the length will be 0x00 and there will
be no payload if there is not any slave response to the LIN Master ID.
Note:
The Zero Padding length depends of the Length Field. There will be Zero Padding
if LIN Payload length is less than the minimum RAW Ethernet Payload size (46 bytes).
There is always zero padding in LIN case due to the LIN maximum length (8 bytes).
