HoverBot, self-balancing vehicle with hoverboard wheels

Neurotronic67 · April 12, 2019, 8:08am

Is it possible that your share the Odrive configuration, since you don’t use speed control ( I assume by readinbg your code you are using direct current torque control) ?
Thanks ^^ !

LuSeKa · April 25, 2019, 9:26pm

Hi, yes the ODrive is in current control mode and the Arduino directly issues current commands. Apart from that the ODrive config is the one described in the Hoverboard-Wheel HowTo.

LuSeKa · April 25, 2019, 9:30pm

The Arduino code is on Github and the readme also has some more general info (diagrams) on the controller and the connections between components. Do you want/need more specific infos?

LuSeKa · May 26, 2019, 9:54pm

Not sure what error you are encountering. Can you specify?
The Arduino library to communicate with the ODrive for this project ist the one found here:

LuSeKa · May 26, 2019, 9:59pm

Hi, there are also Python scripts to automatically configure the ODrive for this vehicle:

LuSeKa · May 27, 2019, 6:46am

Thanks, this screesnhot is helpful. Your sketch is missing the pwmDecoder.ino file. It should be in the same directory as the HoverBot.ino file. In that case the IDE and compiler should find it automatically.

github.com

LuSeKa/HoverBot/blob/master/pwmDecoder.ino

// Interrupt callbacks to measure the pwm duty cycle

void decodePwm_1() {
  static unsigned long riseTime = micros(); // initialize riseTime
  if (digitalRead(PWM_CHANNEL_1) == 1) { // the signal has risen
    riseTime = micros(); // save the rise time
  }
  else { // the signal has fallen
    pwmDutyCycle_steering = micros() - riseTime; // compute the duration of the high pulse
  }
}

void decodePwm_2() {
  static unsigned long riseTime = micros(); // initialize riseTime
  if (digitalRead(PWM_CHANNEL_2) == 1) { // the signal has risen
    riseTime = micros(); // save the rise time
  }
  else { // the signal has fallen
    pwmDutyCycle_throttle = micros() - riseTime; // compute the duration of the high pulse
  }

This file has been truncated. show original

LuSeKa · May 28, 2019, 8:14pm

The compiler cannot find SetCurrent(). I am assuming you are using the odrive-library you found (the one by beak90). This is an outdated copy of the original one. If you use the original odrive lib, this problem will disappear.

LuSeKa · May 30, 2019, 9:47pm

Hi,
not exactly sure what’s the cause for the problem is you are describing, but it could be that the IMU is somehow mounted differently than in my setup? In that case you might get some strange behaviour if you don’t chang the code accordingly.
I suggest you double check that the IMU is mounted in the correct orientation.

LuSeKa · June 7, 2019, 8:06pm

HoverBot was featured in IEEE Spectrum’s Video Friday!

Sami · June 10, 2019, 9:55pm

Thanks LuSeKa for sharing your project with us …

alexisdal · June 11, 2019, 8:32am

and thanks for sharing your automatic setup script ! really useful. I wish i would have had this 9 months ago

Alexey_Maslov · September 3, 2020, 9:55am

Hello, thank you for your great project. One question I have - why are you using current control, not speed control for balancing? Thank you

Samuel_Kearns · November 29, 2020, 7:16am

If anyone would like to make some money I could use help with a project very similar to this all I need is the device to self balance. I could use help with Arduino code.

YousefAdam · December 25, 2022, 2:48am

Greetings,
I need to build normal two wheels robot + one support wheel.
So it’s more simple than this project.
Can any one help me to configure ODrive to works two hoverboard (like this project) but in Step/Dir mode ?
That I’ll replace stepper motors with hoverboard-motors
Hope, to find support .
Regards

Stijn_Carelsbergh · December 25, 2022, 9:56am

Hello

Should be possible, follow the hoverboard wheels guide in the docs and setup step/dir, keep in mind the position accuracy of hall sensors is not very high (standard hoverboard wheels have 30 magnets, so 90 pulses/rev).

Cheers

Carelsbergh Stijn

YousefAdam · December 28, 2022, 6:36pm

Dear All,
Based on “HoverBot” at “GitHub - LuSeKa/HoverBot: Self-balancing robot using hoverboard hub motors”
I try to configure the ODrive with two config file ODrive_hoverboard_motor_setup_part_01.py, and ODrive_hoverboard_motor_setup_part_02.py
It accept the configuration, but I can’t do any other things, how can I test ?
I can’t find Serial configuration inside these file, so how ODrive communicate with Arduino with setting Serial inside ODrive, please clear to me
Thanks

LuSeKa · December 28, 2022, 11:58pm

Hi Yousef, as an aside, the GitHub repo you mentioned is somewhat outdated. However if the setup scripts still work for you, that is great! A newer version of these tools, tested with the more recent ODrive Python 0.5.4. and ODrive firmware version 0.5.4 is here: ChIMP/tools at master · CharlestonRobotics/ChIMP · GitHub
Regarding how to test, you can either use the Arduino code to send current commands via the serial interface and see if the motors spin, or you can use the interactive ODrive tool to send current commands or read the motor positions.

YousefAdam · January 16, 2023, 6:57am

Dear LuSeKa
Really many thanks for your interest and reply to answer my question.
Now, and from two days ago, I have new problem,
The driver reply by this message when rebooting:

Connected to ODrive 2054377E5853 as odrv0
In [1]: odrv0.erase_configuration()
16:04:23.483890900 [LEGACY_OBJ] protocol failed with 3 - propagating error to application
Oh no odrv0 disappeared

I tried with many configuration sequence but fail to solve this problem and pass through
Really I have big problem in my work, Kindly, can you help me?
Best regards

Wetmelon · February 2, 2023, 4:27pm

That’s a normal message at reboot and can be safely ignored

Antonia_Frojdh · June 20, 2024, 12:11pm

Hi LuSeKa!

I’ve been trying to recreate the hoverbot (or ChIMP as well) and I am having one issue that doesn’t seem to be a problem for you in your project. Current control is mapped to set torque in the odrive. That would mean a constant acceleration. I tried to replace the RC part of the project with just direct serial communication, so for starters I just input 5. In the code, it seems to me that the variable “pwmDutyCycle_throttle” is constant if the user is keeping the encoder on the controller in a constant position. This for me means that the robot, given a constant input, is accelerating at a constant speed. It seems like that is not the case for you. It seems that the hoverbot reacts by keeping a constant speed in the videos, like what you would expect from an RC car. I can see that the ODrive is not set to have a velocity limit, so what am I missing that is causing my hoverbot to continuously accelerate? Have I misunderstood how the PWM signals work?