Yes, this does look like (from the demo video results), a decent driver design, however quality of the motor DOES matter, and will eventually become a limiting factor if you are lookig for high precision or high power, as you start to run into things like torque digging, motor heating, etc. There are also little things in the driver design that can bite you if you aren't careful, but I'd need to look at the schematics to comment.
I'm not trying to crap on the project or designer. There was clearly some thought and care put into this! I just don't want people to expect magic, or to think that the only difference between an industrial servo and a hobbyist motor is the electronics. That said, you can get VERY far with good electronics and control software!
A hobbyist project will probably do just fine with something like this (or a motor driver reference design from the chip manufacturers), and by the time they run into limits of those designs and hobbyist motors, they'll probably have a pretty good idea of where they need to go as a next step!
I'll take a closer look at this design later, and update if anyone is interested.
Here are the documentation links to get you started:
Hardware: https://github.com/madcowswe/ODriveHardware/
v3.2 schematic: https://github.com/madcowswe/ODriveHardware/blob/master/v3/v...
Firmware: https://github.com/madcowswe/ODriveFirmware
PC config and analysis support: https://github.com/madcowswe/ODrive
FPGA: https://github.com/madcowswe/ODriveFPGA "... the FPGA logic and software that runs on the FPGA based ODrive. This is not currently in development, but may be resumed at some later date."
----
The hardware is based on a STM32F405RGT6[1] driving two TI DRV8301 brushless motor controller chips[2] and a bunch of MOSFETs to handle the power switching. I/O is a USB, CAN with driver chip, and SPI unbuffered on headers.[1] High-performance foundation line, ARM Cortex-M4 core with DSP and FPU, 1 Mbyte Flash, 168 MHz CPU, ART Accelerator http://www.st.com/en/microcontrollers/stm32f405rg.html
[2] DRV8301 Three-Phase Gate Driver With Dual Current Shunt Amplifiers and Buck Regulator http://www.ti.com/lit/ds/symlink/drv8301.pdf
You could just as well say STM32 or STM32F4 and that is pretty much 99.9% of the information you need to know :)
Brushless servo motors offer the potential for much higher torque and speed in a small package, but require a different form of electronic control, and the gist of this project is that such controls haven't been available for hobbyists. So it's a matter of finding a gap in the existing project / product space, and filling it.
Note that e-bikes use brushless servo motors, so somebody has done the math on what motor technology is most efficient. I also think these motors are in electric cars, and even appliances such as washing machines.
I will be reading with interest. I'll also start keeping an eye out for what kinds of motors are available.
As for "industrial level," I'd say that it's a matter of pushing machine speeds up to a level similar to what you might see in a factory. Often, with stepper motor driven gadgets, you accept the fact that your machine will take a long time to do anything, but who cares, it's a hobby.
On the industrial side, you very quickly run into the situation where your motor is no longer the limiting factor affecting speed and precision, but the design and assembly of the mechanism is.
As for torque, servos again have the edge, but there are pretty large steppers too (1" shaft...).
If you drive steppers with a standard H-bridge you will never get close to what that stepper can do, driving stepper motors to their potential is a black art where at some point during the operational domain you'll be taking energy out of the motor rather than putting it in in order to get past the resonance point. There are companies that specialize in such high speed drivers (Berger-Lahr and RTA for instance), they're not cheap and by the time you're done making this work you might as well install a servo system.
One place where I did see this used frequently is in certain consumer electronics, such as inkjet printers. (Ever wonder why companies like Allegro sell weird combos like a chip for driving 2 steppers, a DC motor and a Buck converter....this is why)...When you are shipping a million printers a year, you save pennies using the cheap actuator and fix it in the controls, but for most projects, yeah totally not worth the hassle!
Steppers do consume full power when not moving, of course, so they're not favored for battery powered systems.
[1] http://www.shopbottools.com/mProducts/ShopBotdesign.htm [2] https://www.tormach.com/technical_questions.html
You can take a copy of the spreadsheet and enter in your own motors that you find. Also do note there is a second tab on the sheet that lets you explore cycle times on trapezoidal trajectories.
There are caveats related to long term durability, but you said "for hobbyists" who I think are less concerned with that aspect. As far as up front performance the answer is yes. Others have explained the details so I'm just adding to the "yes" camp.
Brushless D.C. Motors are the way to go for robotics in many actuation situations for the near to medium term (next decade at least) and the lack of suitable low cost controllers (this is "low cost") has been a major issue, so this product is excellent.
Source: am robotics engineer in Silicon Valley building my own brushless powered robot arm as a hobby and I'm an alpha contributor to the Odrive project. I've also designed my own brushless controllers [1] and built brushless linear motors.
The encoder is what "closes the loop" and allows you to get the accuracy you need. If you have a way to relate the position of the thing being controlled to the motor position, then you can use any motor.
So, it's a nice driver, but it doesn't make the encoder any cheaper.
You are absolutely right that the encoder is a BIG part of your system design, but the motor quality will make a difference. If you are doing something like a robotic arm, or slow speed motor control, you don't just care about encoder ticks, you also start caring about things like torque ripple in the motor if you want decent motion quality, regardless of how good your encoder is!
https://www.aliexpress.com/wholesale?catId=0&SearchText=magn...
So, it would likely work, but have a shorter lifetime. The barrier to using them was having a low voltage / high current controller. This fills that gap.
So, not a bad idea, but there's almost surely a durability tradeoff. And maybe that's fine for a hobbyist cnc application.
There are two things that matter: accuracy and repeatability. Most of the time accuracy is not a problem. But repeatability is. For example when you move something heavy a motor can loose a step. When you don't know this the rest of the accurate moves are out of control.
That's why industrial controllers have good feedback systems. They know a step was performed. If not, you can act on it.
So it's more about control than about motors. But cheap motors wear out faster.
Edit: as other point out 'controlled' is not the best word here. Maybe 'positioned' would have been better.
There is no reference based on a 'step' or a 'pulse', there is only the desired position and the actual position and the difference between the two can be quite large, much larger than with a stepper which can by definition be at most one step ahead or behind or it is game over.
This gets very interesting once you start to combine servos on multiple axis and you want to limit your maximum error compared to some desired trajectory.
But I totaly agree with you, they are completely different. Maybe in this case it was not very clever to oversimplify the problem.
By the way: you point out what I think is great about this business. So much work has been done to control motors very accurate. It's amazing what CNC machines can do today. And also how software optimized motion paths (gcode). And now this hardware. Great stuff!
(Unless you are referring to block commutation of the BLDC phases, which can look sort of similar to step wise control, but I would rebut that in precision servos drives, we would also look at doing non stepwise commutation (sinusoidal, FOC, etc.))
And reliability. Making driver electronics that will live long term is not that simple, sudden stops and overload conditions are tricky to deal with in an effective way without risk to the attached electronics.
> They know a step was performed. If not, you can act on it.
Servo's don't 'step', current is applied to the motor in a continuously varying manner and the delta between the desired movement and the observed movement determines how that current will change over time.
This leads to all kinds of nasty side effects: overshoot, undershoot, runaway in case of a failing feedback mechanism and so on. Steppers are much simpler to interface to in principle (but to drive them at speed is remarkably hard due to all kinds of resonance issues) but much harder to get performance and reliability out of, almost all larger scale industrial control is done with servo motors tightly coupled to their driver electronics.