LIN Network for Vehicle ApplicationsIssued 2004-08Revised 2005-09Superseding J2602-1 AUG2004
5.4.3
SLAVE BEHAVIOR IN THE PRESENCE OF ERRORS WHEN RECEIVING
When a slave task machine detects an ID Parity Error, Byte Field Framing Error, Data Error or Checksum Error, the slave task state machine shall discard any data buffered from the current frame and return to the "Dormant" state. The slave task shall also set the appropriate error flags as defined in Section 5.8.6 (J2602 Status Byte). 5.5
Message Transmission Time Tolerance (ref. Section 2.2, LIN 2.0 Protocol Specification)
Each maximum message transmission time may be specified to be within the range of TFrame_Minimum and TFrame_Maximum, providing both publisher and subscriber of the frame support a maximum message transmission time of less than TFrame_Maximum.
The minimum TFrame_Maximum value to which a slave node can respond shall be identified in its Node Capability File. In the event a value is not provided in the Node Capability File, the Master node shall presume a value of TFrame_Maximum as defined in the LIN 2.0 Protocol Specification. 5.6
LIN Product Identification (ref. Section 2.4, LIN 2.0 Diag and Config Specification)
The following requirements provide further clarification to the intent of the LIN Function ID and Variant ID assignment conditions. 5.6.1
CLARIFICATION TO FUNCTION ID PARAGRAPH:
Two products (ECUs) are identical in function and shall be assigned identical Function Identifiers if they exhibit all of the following characteristics:
They exhibit identical functional behavior
They exhibit identical mandatory Node Capability File declarations
Both LIN communications and Application functionality are configured identically by the IC supplier 5.6.2
CLARIFICATION TO VARIANT ID PARAGRAPH:
Two products (ECUs) are invariant and shall be assigned identical Variant Identifiers if they exhibit all of the following characteristics:
They have identical operating range characteristics (voltage, temperature)
They are constructed from the identical integrated circuit processes and manufacturing technology NOTE—Any change in the binary image loaded in a microprocessor-based slave implementation shall
constitute a difference in the variant ID. 5.7
Mandatory Node Configuration Requests (ref. LIN 2.0 Diag and Config Specification)
These messages are to be used for configuration only; they are not to be used for LIN diagnostics since all relevant diagnostic information is included in the J2602 Status Byte. Furthermore, these configuration messages are only initiated by the master; they are not initiated through the J1962 connector since the LIN bus does not go to this connector.