Configuration
Configure Interfaces > CAN Interface 1 > Transmit PDO {x} (Process ...
Fig. 106: TPDO mapping
COB-ID parameters
314
CANopen allows to send 8 byte of data with each
Transmit PDO. These may be defined separately if no
pre-defined data protocol is used.
All data protocol parameters with a parameter ID may
be sent as an object with a CANopen Transmit PDO.
The data length will be taken from the data byte
column (see Ä Chapter 9.2 "Data Protocols"
on page 492):
1,2 UNSIGNED16 or SIGNED16
–
–
3,4 UNSIGNED16 or SIGNED16
5,6 UNSIGNED16 or SIGNED16
–
1,2,3,4 UNSIGNED32 or SIGNED32
–
3,4,5,6 UNSIGNED32 or SIGNED32
–
etc.
–
The object ID is identical with the parameter ID when
configuring via front panel or ToolKit.
Parameters
9600 Ä p. 315/9610 Ä p. 315/9620 Ä p. 315
communication parameters that adhere to the following
structure.
UNSIGN
ED 32
Bits
Bits
11 bit ID
11 bit ID
Bit number
31 (MSB)
30
29
28-11
10-0 (LSB)
PDO valid / not valid allows to select, which PDOs are
used in the operational state.
easYgen-2200/2500 | Genset Control
MSB
31
30
29
0/1
X
X
Value
Meaning
0
PDO exists / is valid
1
PDO does not exist / is not
valid
X
N/A
X
N/A
0
Always
X
Bits 10-0 of COB-ID
use
LSB
28-11
10-0
0000000
11 bit
0000000
identifier
0000
37535B