Simga2N Traction Advanced Manual– V1.3 Page 122 (166) ©2021 DMC GmbH Herten Germany
The Can node ID number is assigned by means of the pins reported in the following list
• DI 1 (pin 1) (LSB)
• DI 2 (pin 2)
• DI 3 (pin 3)
• DI 5 (pin 5) (MSB)
Inputs have to be considered normally open (if the switch connected to the input is open, then DIx = 0; if the
switch connected to the input is closed, then DIx = 1).
The rule to assign Can node ID number is the following:
Can Node Number = 8*DI5 + 4*DI3 + 2*DI2 + DI1
The can node number ID is assigned once during controller power up.
The CAN node assignment is not compatible with the SafeStop function.
!IMPORTANT With this option is only possible to set node numbers from 1 to 15 !
M7.1-4 Producer heartbeat time “CANOHrBt”
This setting adjusts the transmit refresh rate or the Can Open Heartbeat messages.
M7.1-5 DualMotor and SharedLC messages on 29 or 11 bit IDs “DM&LC ID”
This parameter sets whether the CAN messages used to manage the DualMotor and Shared Line Contactor
functions will be based on 11bit or 29bit CAN IDs.
• If set to 0 (29bit IDs), the Dual Motor and Shared Line Contactor functions will use the following CAN IDs:
▪ 0x00000900 |Dual Motor Master Node Number
▪ 0x00000900 | Dual Motor Slave Node Number
▪ 0x00000A00 | Dual Motor Master Node Number
▪ 0x00000A00 | Dual Motor Slave Node Number
▪ 0x00000880 | Line Contactor Master Node Number
▪ 0x00000880 | Line Contactor Slave #1 Node Number
▪ 0x00000880 | Line Contactor Slave #n Node Number
• If set to 1 (11bit IDs), the Dual Motor and Shared Line Contactor functions will use the following CAN IDs:
▪ 0x400 |Dual Motor Master Node Number
▪ 0x400 | Dual Motor Slave Node Number
▪ 0x500 | Dual Motor Master Node Number
▪ 0x500 | Dual Motor Slave Node Number
▪ 0x480 | Line Contactor Master Node Number
▪ 0x480 | Line Contactor Slave #1 Node Number
▪ 0x480 | Line Contactor Slave #n Node Number
Please notice that if using 11bit IDs for the said function, the user might create conflicts with the standard CAN
Open IDs. Huge attention must be adopted when mapping the Controller’s PDOs.
M7.1-6 CAN communication powerup delay “PwrUpDly”
This parameter sets a delay in starting any activity on the CAN bus. Until the delay is elapsed, the DMC
Controller will not try to send and/or receive any message on the bus.
This delay is useful in case the CAN network is isolated and powered by a DC-DC converter. Under this condition,
in case the DC-DC and Controller are powered up together with the same Key switch, it might happen that the
DC-DC takes time to charge and actually provide output power, while the Controller is already "ready to run"
and tries to start CAN bus activities. This would result in application errors, since the CAN bus could not be
accessed (being it not powered).
To Next Page
Loading...
