SAE J2602-1 2005 LIN Network for Vehicle Applications(5)

LIN Specification Package

The LIN Specification Package as described in Section 1.4.1 LIN Specification Package is informative only and contains no formal requirements. Also note that the information contained in this section of LIN 2.0 may or may not be representative of J2602-based implementations. However, the Glossary included in this section of the LIN specification contains definitions and terms needed to comprehend the LIN Protocol and J2602.

5.2 J2602 Serial Data Link Characteristics

1. Master/Slave Collision Avoidance

2. Capable of operating with LIN 2.0 and previous devices.

3. Additional definition to meet SAE requirements for serial data communication networks. 4. Slave-to-slave communication is not supported and is highly discouraged. 5.3

Detection of Errors by Master (ref Section 4.1, LIN 2.0 Protocol Specification)

The master task state machine shall detect errors during the transmission of the Break / Synch / Protected ID sequence. If an error is detected (e.g., data mismatch or data not received), the master shall cease transmission of the frame and shall start transmission of the next frame as dictated by the schedule table. 5.4 5.4.1

Frame Processing by Slave Tasks (ref Section 4.2.2, LIN 2.0 Protocol Specification) SLAVE TASK ERROR DETECTION

The slave task state machine (either in a slave node or the master) shall detect the following errors:

ID Parity Error

Byte Field Framing Error (i.e., invalid stop bit)

Data Error (i.e., data transmitted does not match data read, data transmitted is not received, fixed

form data received is incorrect) Checksum Error 5.4.2

SLAVE BEHAVIOR IN THE PRESENCE OF ERRORS WHEN TRANSMITTING

When a slave task state machine detects a Byte Field Framing Error, Data Error, or Checksum Error, the slave task state machine shall cease transmission prior to transmission of the next byte field, unless the error occurs during the transmission of the Checksum byte, 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).

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.

LIN Network for Vehicle ApplicationsIssued 2004-08Revised 2005-09Superseding J2602-1 AUG2004

SAE J2602-1 Revised SEP2005

Support of diagnostics and configuration as defined in the LIN Diagnostic and Configuration Specification in the LIN 2.0 Specification Package is OPTIONAL in J2602 nodes. In other words, support of the services defined as mandatory in Section 2.5 of the LIN Diagnostic and Configuration Specification is optional and is NOT required for J2602 compliance. The following sections define the required SAE J2602 node configuration command/response messages. 5.7.1 5.7.1.1 GENERAL CONFIGURATION REQUIREMENTS Slave Execution of Configuration

Within the limit of its capabilities, a slave device shall immediately execute any configuration command upon receipt of the$3C message; it shall not wait for a$3D message. 5.7.1.2 Slave Device Configuration Capabilities

A NCF file shall be included with a SAE J26 …… 此处隐藏：5955字，全部文档内容请下载后查看。喜欢就下载吧 ……