Driver Interference alarm 84h when executing D-SEL0 action.

Discuss Stepper motors, Drivers, Controllers, GUI's and related Accessories here.
Post Reply
dp1
Posts: 10
Joined: Fri Feb 22, 2019 10:16 am

Driver Interference alarm 84h when executing D-SEL0 action.

Post by dp1 » Sat May 11, 2019 5:07 pm

The setup consists of 2 drivers (SlaveID#1 and slaveID#2), daisy chained accessed over RS485/MODbus from a PC, without any external input nor output. MODbus communication does not encounter any Time-Outs!

1 > 06x 0ec1x(3777) 00fex - 5b5ex <<< Slave 1 Associate OD #254 to D-SEL0
1 < 06x 0ec1x(3777) 00fex - 5b5ex
2 > 06x 0ec1x(3777) 00fex - 5b6dx <<< Slave 2 Associate OD #254 to D-SEL0
2 < 06x 0ec1x(3777) 00fex - 5b6dx

1 < 03x 2 ... - bc0cx
1 Regs 007f(127):3680[0e60], <<< Slave 1 in Ready status
2 > 03x 007fx(127) 1 - b5e1x
2 < 03x 2 ... - fd9cx
2 Regs 007f(127):32[0020], <<< Slave 2 in Ready status

Hence both drivers are in Output Status 'Ready'.
Now write OD#254 and OD#255, and Start using D-SEL0 signal.
2 > 10x 5780x(22400) 18 36 0000x(0) 0001x(1)[1] 0000x(0) 34dex(13534)[13534] 0000x(0) 0389x(905)[905] 0000x(0) 0bb8x(3000)[3000] 0000x(0) 0bb8x(3000)[3000] 0000x(0) 03e8x(1000)[1000] 0000x(0) 0001x(1)[1] 0000x(0) 0002x(2)[2] 0000x(0) 00ffx(255)[255] - b7e3x
2 < 10x 5780x(22400) 51abx
2 > 10x 57c0x(22464) 18 36 0000x(0) 0001x(1)[1] ffffx(65535) cb0dx(51981)[-13555] 0000x(0) 0389x(905)[905] 0000x(0) 0bb8x(3000)[3000] 0000x(0) 0bb8x(3000)[3000] 0000x(0) 03e8x(1000)[1000] 0000x(0) 0001x(1)[1] 0000x(0) 0002x(2)[2] 0000x(0) 00fex(254)[254] - 8be2x
2 < 10x 57c0x(22464) 507fx
2 > 06x 007dx(125) 0100x - 1871x <<< Slave 2 action D-SEL0
2 < 06x 007dx(125) 0100x - 1871x
2 > 06x 007dx(125) 0000x - 19e1x
2 < 06x 007dx(125) 0000x - 19e1x

Immediately, and systematically the other slave goes into Alarm.
Why ?
1 > 03x 007fx(127) 1 - b5d2x
1 < 03x 2 ... - bc74x
1 Regs 007f(127):3776[0ec0], <<< Slave 1 in Alarm status
1 > 03x 0081x(129) 1 - d422x
1 < 03x 2 ... - b827x
1 Regs 0081(129):132[0084], <<< Slave 1 Error 84h


When D-SEL0 is given at slave#2, slave#1 goes into Alarm
When D-SEL0 is given at slave#1, slave#2 goes into Alarm
However when a Direct Operation command is given, the other driver doesn't go into alarm.


So, as this trace shows, how is it possible that slave#1 goes into Alarm(84h) when
a D-SEL0 action is given to slave#2?

dp1
Posts: 10
Joined: Fri Feb 22, 2019 10:16 am

Also Driver alarm 84h on other slave when executing START.

Post by dp1 » Wed May 15, 2019 1:42 am

2 > 06x 007dx(125) f80ex - dbe5x <<< Slave 2 action START+M1...M7=OC#254
2 < 06x 007dx(125) f80ex - dbe5x
2 > 06x 007dx(125) 0000x - 19e1x
2 < 06x 007dx(125) 0000x - 19e1x
1 > 03x 007fx(127) 1 - b5d2x
1 < 03x 2 ... - b9e4x
1 Regs 007f(127):128[0080], <<< Slave 1 in status Alarm

How alarm 84h is anyhow possible on a non-addressed slave as according my checks it cannot be a real RS485 transmission problem.
Cfr pag 266:

Framing error? No as the addressed slave gives as response "successful"
Parity error? No as the addressed slave gives as response "successful"
Mismatch CRC? No as the addressed slave gives as response "successful"
Invalid message length? Message is very short.
Why the non-addressed slave goes in error 84h under these circumstances?
If slave 1 addressed -> slave 2 goes into error.
If slave 2 addressed -> slave 1 goes into error.

The RS485 cable between the drivers is .5m long.
For Reading queries I never get RS485 errors.

How can this problem be tackled?

Best regards,
Dominique

Post Reply