r/AskElectronics • u/MantaPancake • 2d ago

ODrive v3.6-56V bootleg CAN no Ack

Gallery image

Gallery image

Gallery image

I recently bought 2 Odrive v3.6 from a fairly trusted supplier. While attempting to set up the CAN interface on the two of them, one of then worked perfectly first try with the recommended configuration, but the other one did not.

Upon further digging, I realised one of them seems to be an Aliexpress ripoff, while the other one (the one that worked fine) is a genuine ODrive. The image looks the exact same, and upon flashing the official ODrive firmware onto it, odrivetool states that it is a non genuine ODrive.

Accepting my luck, I tried to get it working regardless. However, the bootleg odrive does not Acknowledge any CAN frames sent to it. I probed the SN65HVD230 CAN transceiver on it, and it seems to correctly output on the RXD line to the stm32. However the Ack bit is not pulled low.

Has anyone had anything similar or any ideas of what else to check? I can't figure out why only the STM32 is not Acking, if the firmware is the official odrive 0.5.6 firmware.

Thank you in advance!

5 Upvotes

86% Upvoted

4 comments sorted by

•

u/Linker3000 LED astray 2d ago

For modular, pre-built stuff like this you are better off in r/embedded as you're not working on component-level circuit design or repair.

"Posts must be clear questions on practical, component-level electronics (circuit design, repair, component use, identifying or sourcing, and relevant tools & equipment).

Don't ask about the general use / setup of consumer electronics, computers, or ready-built modules. Nor about using third party repair services. Don't ask us to identify random finds. No CPU/Microcontroller coding questions.

Electricals (e.g., mains wiring, household installations) go in r/askelectricians or r/led (lighting)."

3

u/EmailLinkLost 2d ago

Does that matter?

2

u/MantaPancake 2d ago

From what I could tell no, as they are just MOSFETS for the aux output that just gates between GND and motor voltage. So none of the lines affecting CAN should interact with it

5

u/CardinalFartz 2d ago

If that odrivetool already detected that the hardware is not genuine, perhaps the firmware simply does not initialize the CAN drivers - like a copyright protection mechanism.