when I type in any command with out the ‘=’ I get a number. Where can I get a reference.for that number. ie. I want to turn of hall encoders to run in sensorless mode and get a 7 return which I think means ILLEGAL_HALL_STATE. V3.6 FW 0.5.1. This is a problem will all commands.states. Why does ODrive return the name of the cammand/state? Yur wasting countless hours of developers time hunting around or the meaning of the returned numbers
You can see the state and error enums on the API reference: ODrive Reference — ODrive Documentation 0.5.6 documentation
Note we have a tool for this 
you can just use dump_errors(odrv0) to decode all the errors.
And is that tools a secret you can share with me it location?
Also, want to have a reference for all the value to the right of the = sign. ie. what are all the hall_stats name and which numbers do they corespond to? I want to try all the diferent encoder types to see i My motor does have hall effect sensors and has a dierent type. Getting illegal hall state
do you have a refernce or fw 0.5.1? I downlad the docs from github but can’t find it there.
Lot of commands are in this controller like brake_resistance. Been trying to run it in sensorless mode but getting axis encoder failed errors and encodererror.illegal_hall_state. Can’t seem to turn hall encoders of to run in sensorless mode. with 5:1 gearing, thought low speed won’t be too big o a problem but not having revse still is. I have had this controll run hoverboard motors. BUt this is for a product we are trying to roll out on our first golf course. I just had to order two more Flipskies. but they don’t last to long. Yet they don’t require sensors. Eventual we want encoders to detect wheel slipage, etc/ but GPS eedback currently limits the need for encoder feed back.
meant cmmands “not” in this controller.
And is that tools a secret you can share with me it location?
No, it’s in ODrivetool Troubleshooting — ODrive Documentation 0.5.6 documentation
Hall states are just the raw binary values of the hall sensors, from 0-7 (with only 1-6 being valid states).
Your motor (you linked it in another thread) does have hall sensors. Are you using 22nF capacitors and ferrite rings? Those are essential to get hall sensors working correctly on the v3.6 (though since you’re using a third party clone, that might not even be enough).
do you have a refernce or fw 0.5.1? I downlad the docs from github but can’t find it there.
You would have to download branch v0.5.1-rc5 and build the docs yourself. ODrive Firmware Developer Guide — ODrive Documentation 0.5.6 documentation
I think overall your problems are mainly caused by the fact you’re using cheap, knockoff ODrive controllers. Even the v3.6 has some EMI issues with hall sensors, and the knockoffs (based on older versions like v3.4 and v3.5) have so many issues I don’t think it’s even worth trying to get them to work. I’m also not surprised the Flipskys explode. I’d strongly recommend picking up some S1s – they’re our new generation product, with much better performance and a lot of new firmware features, and work great with hall sensors – plus you get the new web gui, which makes setup, configuration, and tuning much easier.