![NANOTEC ELECTRONIC N5 Technical Manual Download Page 116](http://html.mh-extra.com/html/nanotec-electronic/n5/n5_technical-manual_705153116.webp)
Technical Manual N5 (CANopen)
8 CANopen
1000:00
Object dictionary
...
6040:00
...
607A:00
...
6005:0E
CAN ID
Data
Byte 1
Byte 2
200+NodeID
Data for 0x6040:0x00
Byte 3
Byte 4
Data for 0x607A:0x00
Byte 5
Byte 0
RX-PDO Message (1. Mapping)
1600:00
1600:01
1600:02
1600:03
...
Amount of Mappings
Mapping #1
Mapping #2
Mapping #3
02
607A0020
60600008
60400010
Index
Description
Data (hex)
40192
Device Type
0000
00000000
00
Controlword
Target Position
http drive catalogue
address
1600:04
Mapping #4
00000000
TX configuration
To configure an RX-PDO, three object categories in the object dictionary must be taken into account:
1. The objects that describe the functionality of the mapping.
2. The objects that describe the content of the mapping.
3. The objects that are to receive the data that are to be sent.
Also note that the time at which the data are copied to the TX-PDO message and the time of sending
do not need to be the same (dependent on mode).
Configuration of the functionality (communication parameter)
The configuration of the functionality of the first mapping is stored in the subindices of object 1800
h
.
The second mapping is configured in 1801
h
and so on. In the following, we refer to 180N
h
. Here, the
configuration affects the COB-ID of the PDO message and the transfer type.
Objects 180N
h
have the following subindices:
•
Subindex 0 (max. subindex): Total number of subindices
•
Subindex 1 (COB-ID): The COB-ID is stored here. For PDO mappings 1–4 (1A00
h
–1A03
h
), the
CAN-ID is fixed depending on the node-ID and only the valid bit (bit 31) can be set in the COB-ID.
From 1A04
h
–1A07
h
, the CAN-ID can be set independently (with the restriction that it not be used
by other services, see table at the start of chapter CANopen services) as can the valid bit. A COB-
ID change does not take effect until after the controller or communication is restarted (see Network
Management (NMT)).Because these data are stored in the DataFlash of the controller, the setting
of the COB-IDs should be performed using the "canopen.on" file with the help of NanoIP or with
Plug & Drive Studio.
Mapping
COB-ID
1A00
h
180
h
+ Node-ID
1A01
h
280
h
+ Node-ID
1A02
h
380
h
+ Node-ID
1A03
h
480
h
+ Node-ID
1A04
h
xxx
h
+ Node-ID
1A05
h
xxx
h
+ Node-ID
1A06
h
xxx
h
+ Node-ID
1A07
h
xxx
h
+ Node-ID
Version: 2.0.1 / FIR-v1650
116