I'm sorry about the delayed response.
You might have an identical ID among your connected DYNAMIXEL which interrupts communication between the Wizard 2.0 and DYNAMIXEL.
Have you connected only one DYNAMIXEL to the U2D2 during firmware recovery?
Are you supplying 12V to the power hub?
Some USB charging cables only transfers power, not data. Try with other USB cables.
No worries and thanks for the response. To your questions above:
- Yes, we tried with each motor separately/individually as well both when trying to ping/communicate normally and for the firmware recovery process.
- Yes, we are supplying 12V to the power hub.
We have also tried multiple USB cables in case of damage. To be clear, we have used these motors before and could successfully connect and control them. However, when using them one day - we had these issues and were unable to ping/communicate any of the motors since.
Thanks again for your time.
Thank you for the updates.
It is very unlikely happening, but it seems like the RS485 communication IC is malfunctioning.
Since the LED blinks when powered, the bootloader works fine, but not responding during the firmware recovery process is mostly due to the problem in the communication part.
And you've already tested with various cables, the last thing I can suspect is the communication IC.
I'd recommend getting the RMA service for further inspection from our engineers to see if the PCB needs to be replaced.