Nice to hear from you Karl! This was one of those projects where making the video and explaining it was 4x the work of actually building the thing, so it is great to see it appreciated!

I'm working to keep them coming!

Thanks!

Thanks! You called it, it really just does pre-charging and over-current faulting: mjbots.com/products/mjbots-power-dist-r4-5b

@@awesjosh I end up building something like that into almost every board I make, so it makes a lot of sense to have that as a stand-alone unit 🙂 Those who haven't struggled with power management might wonder why they'd need to spend money on a glorified power switch; I think it's up to us who have stubbed our toes to explain why ...

moteus uses a pll filter on the hall effect sensors for commutation purposes, and that is the reported velocity that was used for the outer velocity control loop. The bandwidth of that filter was somewhere between 50-100Hz, so it doesn't do much at low speed with the coarse resolution of the hall encoders.

Thank you! I do similar project and for now use the similar control approach but with some differences kzfaq.info/get/bejne/grOmeNZ3nr-WcY0.htmlsi=PAa4gED8A2Uu-Ezu In the future I'm going to ustilize mpc for increasing the stability and the robot's speed

Cool! Thanks for sharing! As you can see from my video, you don't need to go to MPC to get significantly improved results. Probably the easiest ways to improve your system would be to see if the structure of your control laws can be improved (or perhaps copy the ones here), and the second would be to ensure your attitude and attitude rate solution are operating well and with a sufficiently high bandwidth. It could also be that your tuning is just sub-optimal. Are you using integrative terms anywhere (you probably shouldn't)?

Thank you for recommendations! Yes, I use integrative terms both in attitude loop and in velocity control loop. I have some suspicious about imu. It outputs data only with 100hz. Probably if I replace IMU to better one, the whole system will be more stable.

I'm not sure an integrative term for attitude is useful, certainly this robot does not use one. A feedforward term is probably a lot more valuable there if a plain PD is insufficient. While a 100Hz IMU update rate is borderline feasible, there are lots of things that could potentially make it problematic. That could be if you are just using pitch and not pitch rate, or if the IMU has a software configured low-pass filter, or if it is poorly mounted, or a host of other things. This robot uses a 400Hz update IMU for instance with a 200Hz onboard filter, uses the pitch rate in addition to the pitch, and is known to work well at up to that rate.

Unfortunately no, it can't be used with a raspberry pi 5. It only works with a pi3 or pi4.

Opps checked the manual and it clearly states it isn't.