ID
Parameter
33040
2. Node-ID
33041
3. Node-ID
33042
4. Node-ID
33043
5. Node-ID
4.6.1.2
Receive PDO {x} (Process Data Object)
General notes
COB-ID parameters
37535B
Configure Interfaces > CAN Interface 1 > Receive PDO {x} (Process D...
CL
Setting range
Description
[Default]
2
0 to 127 (dec)
In a multi-master application, each Master needs its own identifier (Node-ID)
from the unit. in order to send remote signals (i.e. remote start, stop, or
[0]
acknowledge) to the unit.
The additional SDO channel will be made available by configuring this Node-
ID to a value different than zero. This is the additional CAN ID for the PLC.
2
0 to 127 (dec)
In a multi-master application, each Master needs its own identifier (Node-ID)
from the unit. in order to send remote signals (i.e. remote start, stop, or
[0]
acknowledge) to the unit.
The additional SDO channel will be made available by configuring this Node-
ID to a value different than zero. This is the additional CAN ID for the PLC.
2
0 to 127 (dec)
In a multi-master application, each Master needs its own identifier (Node-ID)
from the unit. in order to send remote signals (i.e. remote start, stop, or
[0]
acknowledge) to the unit.
The additional SDO channel will be made available by configuring this Node-
ID to a value different than zero. This is the additional CAN ID for the PLC.
2
0 to 127 (dec)
In a multi-master application, each Master needs its own identifier (Node-ID)
from the unit. in order to send remote signals (i.e. remote start, stop, or
[0]
acknowledge) to the unit.
The additional SDO channel will be made available by configuring this Node-
ID to a value different than zero. This is the additional CAN ID for the PLC.
RPDO mapping is carried out as shown in (Fig. 105).
Fig. 105: RPDO mapping principle
easYgen-2200/2500 | Genset Control
Parameters
9300 Ä p. 312/9310 Ä p. 312/9320 Ä p. 312
communication parameters that adhere to the following
structure.
Configuration
use
311