I’ve been using Flipsky 4,20 but they keep failing had two 3rd pary v3.6 w 0.5.1 odrives.
Flipsky doesn’t need encoder. read that odrives can go slow r reverse in sensorless mode.
Seeing scope trigger led flash on all lines on bot motors, but only yellow on ne motor and green n the other actually moves the scope line when hand turning. But nothing that loks like a square wave. 5:1 gear ratio so one turn of the wheel is supposed to rotate. uumotor says its has 10 poles set cpr to 60 and thats 300 pulses per rotation, right?
waiting to hear from uumotor. Little support from them. Odrivetol dfu does work. Afraid o bricking controller by forcing firmwsre update.
Any clues here?
If you’re using third party ODrives, that’s likely the issue. Those are based off of ODrive v3.4 or v3.5 (even if they say v3.6), which had a lot of signal integrity issues.
The v3.6 has a lot of issues with electrical noise too (even though it was better than v3.4 or v3.5) – typically we recommend adding external 22nF capacitors to the hall lines, like so Encoder error ERROR_ILLEGAL_HALL_STATE - #7 by madcowswe . That should help this issue. You can also use ferrite rings on the motor phases, for added benefit.
Generally I wouldn’t bother getting ODrive clones to work, they’re all really bad. I would return them to the manufacturer and consider genuine ODrives.
these controllers have been sitting around for two years. can’t return them. Put a scope n the motors and hand turned them. noting that looked like a square wave, Trigger led lashed on all lines but line moved only on green on one motor and red on the other. So uumotors may not have working encoder or they aren’t hall effect ones. Was using Flipsky’s until they blew up. The dont require sensors to go slow or reverse. Tried senesonrless mode and got a second axis error ‘INVALID STATE’. need to go back through the config to see if I missed some thing
Do you know the motor’s part number, or have a link to the web page it’s from?