ODrive V3.6 only recognized in DFU mode, but not in RUN mode

[paradoxic]

I have a 56V Odrive V3.6.
I connected it and tried running odrivetool, but the device could not be found. Upon checking the Device Manager, the device did not appear at all either, even without anything else connected besides the ODrive itself
When I switched to DFU mode, Windows identified it as STM32 Bootloader, and I was able to successfully flash firmware v0.5.4 to the device. However, upon power cycling and switching the device back to RUN mode, it couldn’t be recognized again, and didn’t show up on the device manager, nor could it be found by odrivetool.

The issue posted by ojferro here:

ODrive V3.6 not recognized in RUN mode (Device Manager nor odrivetool). Re-flash does not help

Just unboxed an ODrive V3.6, 24V. Connected and managed to see the ODrive driver updates on Zadig. Installed successfully. Ran odrivetool and odrv0 was recognized. Powered off to connect a BLDC to M0, and upon turning it back on, odrivetool does not recognize it. Nothing shows up in Windows Device Manager. I have tried different laptops, power cycling the board, power cycling the laptops, different USB cables, driver updates, etc. I also checked the forum for other similar posts, but none of t…

seems similar to my situation.

Any assistance or help would be greatly appreciated. Thank you!

[Samuel]

Does this issue still persist? If yes, this might be a hardware issue, so in that case please email info@odriverobotics.com with your order number and a link to this thread.

[paradoxic]

Sorry for the late response! The issue was resolved, though I’m not entirely sure why. I changed the cables, the power supply and some other stuff again, and I guess one of those things was causing the problem. It works completely fine now, thanks!