![AXIOMATIC AXTC4CO Скачать руководство пользователя страница 31](http://html1.mh-extra.com/html/axiomatic/axtc4co/axtc4co_user-manual_3037100031.webp)
UMAXTC20CO V1.1.1 Preliminary Documentation – May be Subject to Change 31-59
Sub-Index 2h
Description Sensor
Error
Access RW
PDO Mapping
No
Value Range
0 = Pre-Operational
1 = No State Change
2 = Stopped
Default Value
1 (No State Change)
3.2.14. RPDO
Behaviour
The Thermocouple Scanner can support up to four RPDO messages, but in reality, it does not
used them. The other RPDO objects are provided simply for compliance with the standard
CANopen ® Object Dictionary, but are disabled on this module (mapping objects are read-only)
All RPDOs on the Thermocouple Scanner use the same default communication parameters, with
the PDO IDs set according to the pre-defined connection set described in DS-301. All RPDOs do
not exist, there is no RTR allowed, they use 11-bit CAN-IDs (base frame valid) and are event-
driven.
Object Description
Index
1400h to 1403h
Name RPDO
communication
parameter
Object Type
RECORD
Data Type
PDO Communication Record
Entry Description
Sub-Index 0h
Description Number
of
entries
Access RO
PDO Mapping
No
Value Range
5
Default Value
5
Sub-Index 1h
Description
COB-ID used by RPDO
X RPDOx
ID
Access RW
1
0200h
PDO Mapping
No
2
0300h
Value Range
See value definition in DS-301
3
0400h
Default Value
C00 RPDOx + Node-ID
4
0500h
Node-ID = Node-ID of the module. The RPDO COB-IDs are automatically updated if the
Node-ID is changed by LSS protocol.
80000000h in the COB-ID indicates that the PDO does not exist (destroyed)
04000000h in the COB-ID indicates that there is no RTR allowed on the PDO