![IFM PDM360NG Series System Manual Download Page 162](http://html1.mh-extra.com/html/ifm/pdm360ng-series/pdm360ng-series_system-manual_3875026162.webp)
ifm
System Manual
ecomat
mobile
PDM360NG (CR1080, CR1081, CR9042) Target V01
2011-07-28
CAN in the PDM360
General about CAN
162
9.1.4
System configuration
2270
The controllers are delivered with the following download identifier (= ID):
- ID 127 for CAN interface 1
- ID 126 for CAN interface 2 (if available)
- ID 125 for CAN interface 3 (if available)
- ID 124 for CAN interface 4 (if available)
The download system uses this identifier for the first communication with a non configured module via
CAN.
The download IDs can be set as follows:
- via the PLC browser of the programming system,
- via the the downloader or the maintenance tool or
- via the application program.
Via the mode "Autoconfig" of the boot loader only CAN interface 1 can be set.
As the download mechanism works on the basis of the CANopen SDO service (even if the controller is
not operated in the CANopen mode) all controllers in the network must have a unique identifier. The
actual COB IDs are derived from the module numbers according to the "predefined connection set".
Only one non configured module is allowed to be connected to the network at a time. After assignment
of the new participant number 1...126, a download or debugging can be carried out and then another
device can be connected to the system.
NOTE
►
The download ID is set irrespective of the CANopen identifier. Ensure that these IDs do not
overlap with the download IDs and the CANopen node numbers of the other controllers or network
participants.
Comparison of download-ID vs. COB-ID:
Controller program download
CANopen
Download-ID
COB-ID SDO
Node ID
COB-ID SDO
TX: 580
16
+ download ID
TX: 580
16
+ node ID
1…127
RX: 600
16
+ download ID
1…127
RX: 600
16
+ node ID
TX = slave sends to master
RX = slave receives from master
NOTE
The CAN download ID of the device must match the CAN download ID set in CoDeSys!
In the CAN network the CAN download IDs must be unique!