
10
85201A_RK5C_User Manual_02-2017_ENG
3.4 LSS IDENTIFICATION SERVICES
LSS identify remote slave
By means of this service, the LSS master device requests all LSS slave devices to identify themselves by means of the
'LSS identify slave' service, whose LSS address meets the LSS_Address_sel. The LSS_Address_sel consists of a single
vendor-ID and a single product code and a span of revision and serial numbers determined by a low and high number.
The protocol defined in the following figure implements the LSS identify remote slave service. All LSS slave devices
with matching vendor-ID and product-code and whose major revision-number and serial-numbers are located within the
given ranges, identify themselves with the LSS identify slave service. The boundaries are included in the interval.
COB-ID
Rx/Tx
DLC
Data
D0
D1
D2
D3
D4
D5
D6
D7
7E5h
Rx
8
46h
Vendor-ID
Reserved
7E5h
Rx
8
47h
Product-code
Reserved
7E5h
Rx
8
48h
Revision number low
Reserved
7E5h
Rx
8
49h
Revision number high
Reserved
7E5h
Rx
8
4Ah
Serial number low
Reserved
7E5h
Rx
8
4Bh
Serial number high
Reserved
Figure 22 - LSS identify remote slave message sequence
Where:
Vendor-ID is the LSS slave’s identity Vendor-ID (Intel format byte ordering).
Product-code is the LSS slave’s identity Product-code (Intel format byte ordering).
Revision number low and Revision number high identity the Revision number span (Intel format byte ordering).
Serial number low and Serial number high identity the Serial number span (Intel format byte ordering).
LSS identify slave
By means of this service, an LSS slave device indicates that it is a slave device with an LSS address within the LSS_
Address_sel given by an LSS identify remote slave service executed prior to this service.
The protocol is defined in the following figure.
COB-ID
Rx/Tx
DLC
Data
D0
D1
D2
D3
D4
D5
D6
D7
7E4h
Tx
8
4Fh
Reserved
Figure 23 - LSS identify slave message
LSS identify non-configured remote slave
By means of this service, the LSS master device requests all LSS slave devices to identify themselves by means of
the 'LSS identify non-configured slave' service, who got stuck in NMT Initialization state, whose pending node-ID is invalid
(FFh) and who have no active node-ID.
The protocol is defined in the following figure.
COB-ID
Rx/Tx
DLC
Data
D0
D1
D2
D3
D4
D5
D6
D7
7E5h
Rx
8
4Ch
Reserved
Figure 24 - LSS identify non-configured slave message