Duet2 with 2.0 RTOS looses Duex5 on reset
-
It looks like if you reset (M997, M999, etc) a Duet2 with the 2.0 firmware and a Duex5, the Duet2 doesn't recognize the Duex5 when it comes back up. The hardware string just says "Duet Ethernet 1.02 or later" instead of "Duet Ethernet 1.02 or later + DueX5" and commands to motors on the Duex5 are ignored. The only way to get it back is a power cycle. Even rolling back to 1.21 still needs a power cycle to get the Duex5 back.
-
Thanks for your report. I will try to reproduce this.
-
Cannot reproduce this on my setup.
Maybe a problem with the flat cable? -
@whosrdaddy said in Duet2 with 2.0 RTOS looses Duex5 on reset:
Cannot reproduce this on my setup.
Maybe a problem with the flat cable?I would think that if it were a cable problem the issue would occur on 1.21 as well and it doesn't.
-
@gtj0 said in Duet2 with 2.0 RTOS looses Duex5 on reset:
It looks like if you reset (M997, M999, etc) a Duet2 with the 2.0 firmware and a Duex5, the Duet2 doesn't recognize the Duex5 when it comes back up. The hardware string just says "Duet Ethernet 1.02 or later" instead of "Duet Ethernet 1.02 or later + DueX5" and commands to motors on the Duex5 are ignored. The only way to get it back is a power cycle. Even rolling back to 1.21 still needs a power cycle to get the Duex5 back.
But you said that rolling back to 1.21 still requires you per cycle it to get it back is that not the same
-
@dougal1957 said in Duet2 with 2.0 RTOS looses Duex5 on reset:
@gtj0 said in Duet2 with 2.0 RTOS looses Duex5 on reset:
It looks like if you reset (M997, M999, etc) a Duet2 with the 2.0 firmware and a Duex5, the Duet2 doesn't recognize the Duex5 when it comes back up. The hardware string just says "Duet Ethernet 1.02 or later" instead of "Duet Ethernet 1.02 or later + DueX5" and commands to motors on the Duex5 are ignored. The only way to get it back is a power cycle. Even rolling back to 1.21 still needs a power cycle to get the Duex5 back.
But you said that rolling back to 1.21 still requires you per cycle it to get it back is that not the same
Ah, sorry for the confusion. Let me clear. When running 2.0 I have the issue. If I roll back to 1.21 WITHOUT A POWER CYCLE I'll still have the issue until I do a power cycle. Then everything's normal on 1.21. This sounds like a 2.0 firmware issue that puts the hardware in a funky state that can't be recovered without a power cycle even if the firmware is downgraded.
