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

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

SAE J2602-1 Revised SEP2005

TABLE 1—NAD TO MESSAGE ID MAPPINGNAD$60 Message ID$00$01$02$03$04$05$06$07$08$09$0A$0B$0C$0D$0E$0F$10$11$12$13$14$15$16$17$18$19$1A$1B$1C$1D$1E$1F$20$21$22$23$24$25$26$27$28$29$2A$2B$2C$2D$2E$2F$30$31$32$33$34$35$36$37 No Message IDs defined No Message IDs defined NAD$60 Message ID$00$01$02$03$04$05$06$07$08$09$0A$0B$0C$0D$0E$0F$10$11$12$13$14$15$16$17$18$19$1A$1B$1C$1D$1E$1F$20$21$22$23$24$25$26$27$28$29$2A$2B$2C$2D$2E$2F$30$31$32$33$34$35$36$37 No Message IDs defined No Message IDs defined NAD$60 Message ID$00$01$02$03$04$05$06$07$08$09$0A$0B$0C$0D$0E$0F$10$11$12$13$14$15$16$17$18$19$1A$1B$1C$1D$1E$1F$20$21$22$23$24$25$26$27$28$29$2A$2B$2C$2D$2E$2F$30$31$32$33$34$35$36$37 No Message IDs defined No Message IDs defined

$61

$62

$62

$63

$64

$64

$64

$65

$66

$66

$67

$68

$68

$68

$69

$6A

$6A

$6B

$6C

$6C

$6C

$6D

$6D

$6E$6F

$6E$6F

$6E$6F

NOTE—The Message IDs listed in this table are the unprotected Identifiers.

- 15 Author:Gilligan-SID:9234-GUID:35989776-155.69.4.4

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

SAE J2602-1 Revised SEP2005

5.7.2.3

Configuration Messages

LIN protocol level and application level configuration of each slave node may be accomplished using any combination of the following: 1. Using optional method defined in the LIN Diagnostic and Configuration Specification in the LIN 2.0 Specification Package. 2. Using$3C messages with NADs in the User reserved range of$80 -$FF. 3. Using$3E messages with any NAD. When using$3C or$3E messages to configure the slaves, the lower nibble of the NAD shall be the DNN to prevent conflicts between slaves.$3C NADBit 7 (msb) 1 6 X 5 X 4 X 3 DNN3 2 DNN2 1 DNN1 Bit 0 (lsb) DNN0

$3E NADBit 7 (msb) X 6 X 5 X 4 X 3 DNN3 2 DNN2 1 DNN1 Bit 0 (lsb) DNN0

5.7.2.4

Response Message to Options 2 and 3 in Section 5.7.2.3

The$3D Response message that follows each$3C and$3E Command message shall return the J2602 Status Byte (defined in Section 5.8.6) in Data Byte 0. The value of the other seven data bytes is implementation dependent and beyond the scope of this specification.Tx by Master LIN ID$3D Tx by Slave Data0 J2602 Status Byte Tx by Slave Data1 XX Tx by Slave D

ata2 XX Tx by Slave Data3 XX Tx by Slave Data4 XX Tx by Slave Data5 XX Tx by Slave Data6 XX Tx by Slave Data7 XX

5.7.2.5

DNN Based Broadcast Messages

There are four Message IDs reserved for Broadcast messages. The NAD that will use a specific Broadcast Message, and the data byte within the message that it will use is based on its DNN. The Broadcast Message IDs for a specific NAD are b11 100x and b11 101x, where x= DNN3. The relevant data byte number is equivalent to the three lsbs of the DNN. In the case where a node has more than 4 message IDs, i.e. 8 or 16, it shall also be assigned a proportionate number of Broadcast Message bytes. 5.7.2.5.1LIN ID$38$39$3A$3B

DNN Based Broadcast Message Assignment for 4 Messages per NodeData0 DNN=$0 DNN=$8 DNN=$0 DNN=$8 Data1 DNN=$1 DNN=$9 DNN=$1 DNN=$9 Data2 DNN=$2 DNN=$A DNN=$2 DNN=$A Data3 DNN=$3 DNN=$B DNN=$3 DNN=$B Data4 DNN=$4 DNN=$C DNN=$4 DNN=$C Data5 DNN=$5 DNN=$D DNN=$5 DNN=$D Data6 DNN=$6 XX DNN=$6 XX Data7 DNN=$7 XX DNN=$7 XX

- 16 Author:Gilligan-SID:9234-GUID:35989776-155.69.4.4

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

SAE J2602-1 Revised SEP2005

5.7.2.5.2LIN ID$38$39$3A$3B

DNN Based Broadcast Message Assignment for 8 Messages per NodeData0 DNN=$0 DNN=$8 DNN=$0 DNN=$8 Data1 DNN=$0 DNN=$8 DNN=$0 DNN=$8 Data2 DNN=$2 DNN=$A DNN=$2 DNN=$A Data3 DNN=$2 DNN=$A DNN=$2 DNN=$A Data4 DNN=$4 DNN=$C DNN=$4 DNN=$C Data5 DNN=$4 DNN=$C DNN=$4 DNN=$C Data6 DNN=$6 XX DNN=$6 XX Data7 DNN=$6 XX DNN=$6 XX

5.7.2.5.3LIN ID$38$39$3A$3B

DNN Based Broadcast Message Assignment for 16 Messages per NodeData0 DNN=$0 DNN=$8 DNN=$0 DNN=$8 Data1 DNN=$0 DNN=$8 DNN=$0 DNN=$8 Data2 DNN=$0 DNN=$8 DNN=$0 DNN=$8 Data3 DNN=$0 DNN=$8 DNN=$0 DNN=$8 Data4 DNN=$4 DNN=$C DNN=$4 DNN=$C Data5 DNN=$4 DNN=$D DNN=$4 DNN=$D Data6 DNN=$4 XX DNN=$4 XX Data7 DNN=$4 XX DNN=$4 XX

5.7.3

TARGETED RESET

The Targeted Reset command provides a mechanism for the Master to cause a re-initialization of a specific slave device on the network, designated by the NAD in the command. Upon receipt of the Targeted Reset command, the slave device shall cause an internal reset of operational variables to occur. Examples of operational variables include, but are not limited to, program counters, mode control variables, communications error counters, input source re-initializations, and output device reinitializations, but shall not alter any previously configured application level configuration information stored in non-volatile memory. This Reset operation shall not cause the slave to destructively alter any LIN configuration data or addresses stored in non-volatile memory. Also, the Reset operation shall not cause any configuration parameters in the LIN Data Link device (UART) to be altered. Upon conclusion of the Reset operation, the slave device shall remain configured, and shall assume a state consistent wit

h a power-on initialization, with the exception of the LIN configuration information. The slave shall also retain knowledge that it has undergone a reset operation, such that a positive response can be provided to the Master. The LIN Slave device shall be able to respond to a$3D request frame which starts immediately after the stop bit of the checksum byte of the$3C Targeted Reset command frame. For those devices that are always in the power-o …… 此处隐藏：5847字，全部文档内容请下载后查看。喜欢就下载吧 ……