Any updates to the single channel odrive concept?
ODrive v4, which Oskar is currently developing, will be a single axis. I’ve also developed a single-axis iteration based on v3.4 architecture.
1 Like
Rad! Looking forward to it.
Do you have the design files for the single channel variant handy by any chance?
I really want to release them and wish I could, but I completed it through my work at an engineering company and they are not allowing me to release the files. For what it’s worth, I’m planning on making my own iteration in late April.
1 Like
pjhayton, did you have to change the firmware a lot? I’m working on single axis board too and wondering what happens when odrive firmware finds out second motor driver IC is not present.
Only for the first iteration, because I took off the CAN IC (so I had to debug through the firmware and comment out any calls to CAN) so that was a nightmare.
With my latest rev, which includes CAN, I hardly had to change the firmware. I only changed the firmware to update my shunt resistance values, the dead time clocks (due to me changing the low-side gate resistor values), and my tup.config file to v3.4-24V.
Thank you for the insight. I hope this can become a community project cuz many people are interested in it. Please do share with us when you get the next design going.
Will do. I’ll be starting on it the last week of April.
Any news on the official single axis odrive?
Yes we are working on it. We are aiming to have beta ready by the end of the year, or maybe early next year.
You can sign up for news about it here:
3 Likes
I am also working on a single motor version based on Odrive3.5 but also re-purposing M1 signals and peripherals for additional features unique to my application. I modified the CubeMx project to remove M1 signals and peripherals and carefully merged the code. I am a bit confused about some of the functions in low_level.cpp and how to isolate M0 from M1 dependencies. Specifically sync_timers() and vbus_sense_adc_cb() . If you have any suggestion or if your new code can provide some information on how to do this, I would really appreciate any help.
What limitations do you expect on the attachable motors?
Can you share more about the pros/cons of making this new design open source?
Thanks
Hey @madcowswe
I’d love to help with V4 design and testing 
I have EE background and lots of robotics experience. Interested in the mini version for a quadruped robot I am working on.
(website mrrobot.ca)
Let me know
1 Like
Cool, thanks for the offer to help! I’ll write to you in DM.
Any chance v4 will include simultaneous hall and encoder monitor?
Still having hugh safety issues with encoder based system losing steps and spinning out of control. Would be nice to use incremental for high resolution and low resolution absolute for safety.
Yes it will have dedicated inputs to halls while also allowing encoder input.
are there plans to release a 56v version of the single axis controller alongside the 24v version, like the full size odrive?
I think we will actually start with a 54V version. We will see if there will even be a 24V version, 70% likely I think.
Hi!
Is the project in schedule? 
If there are to be two different voltage variants, I would vote for a 54V (nominal 48V DC with a bit of room for regen) and 600V version (to drive motors intended for mains voltage, e.g. ACIM or industrial servomotors) 