Compiler Errors

[sylajen]

Hey there,

We're using this code in a similar fashion for a 2 wheeled self balancing robot, however we ran into some issues with the compiler. We're trying to use the Hoverbot.ino file, however when we try to run the code, a series of errors have come up, with the error in the image below being the one issue we have been having the most trouble with. Just wanted to see if this is an error you've had yourself or if you are familiar with how to resolve this. Thanks.

[CrispyFungus]

I did get past this, I will have to get back to you

On Thu, Nov 4, 2021, 6:06 PM sylajen @.***> wrote:

Hey there,

We're using this code in a similar fashion for a 2 wheeled self balancing robot, however we ran into some issues with the compiler. We're trying to use the Hoverbot.ino file, however when we try to run the code, a series of errors have come up, with the error in the image below being the one issue we have been having the most trouble with. Just wanted to see if this is an error you've had yourself or if you are familiar with how to resolve this. Thanks.

[image: error] https://user-images.githubusercontent.com/33578533/140435569-5d956566-0245-47d3-b14d-f98ed39c978a.png

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/LuSeKa/HoverBot/issues/4, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHPRYKJVSIOIHNIXKTXIXTUKMUZZANCNFSM5HMVHUBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[sylajen]

Sounds good, if possible, would you be willing to do a call so we can explain the situation and show it in greater detail? Please let me know, you can email me at nothinggistrue@gmail.com.

[CrispyFungus]

Yes some time this weekend I could be available, this is what I did with the code, it may be similar to what you're doing.

https://youtu.be/iIDN5WiU3wc

On Fri, Nov 5, 2021, 2:16 PM sylajen @.***> wrote:

Sounds good, if possible, would you be willing to do a call to explain the situation in greater detail? Please let me know, you can email me at @.***

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LuSeKa/HoverBot/issues/4#issuecomment-962193381, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHPRYIYS6OFB7EDO5AATQTUKRCTPANCNFSM5HMVHUBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[sylajen]

What time would you be available tomorrow and your preferred method of contact? I live in the Eastern Time zone

[CrispyFungus]

Did you try using the Adafruit BNO055 sketch they have on their website? I didn't copy the hoverbot code verbatim. Also do you have the motor drivers in close proximity to the BNO055? Are you using other I2C devices? Did you check that the address pre programmed on the BNO055 is matching your sketch?

Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: sylajen @.> Sent: Saturday, November 6, 2021 11:25:51 PM To: LuSeKa/HoverBot @.> Cc: CrispyFungus @.>; Comment @.> Subject: Re: [LuSeKa/HoverBot] Compiler Errors (Issue #4)

We were able to solve the compiling issue above and now we have another issue. We used a example code from Adafruit BNO 055 called sensorapi to test the IMU. We are able to verify and upload the code to the Arduino Mega but the serial monitor does not recognize the IMU.

The error we receive is:

Ooops, no BNO055 detected ... Check your wiring or I2C ADDR!Orientation Sensor Test

Ooops, no BNO055 detected ... Check your wiring or I2C ADDR!

The puzzling thing is that the IMU is detected when using Arduino Uno after checking via serial monitor. The wiring is the same when using both the Mega and the Uno so we think that this might be a hardware issue but we just wanted to ask you in case you ran into the same problem.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/LuSeKa/HoverBot/issues/4#issuecomment-962554455, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANHPRYMFDROREP54FSECCC3UKYLW7ANCNFSM5HMVHUBA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[CrispyFungus]

If you'd Like, I can send my Segway sketch I made and then you try, I used the ODrive as well

Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: Jason Benjamin @.> Sent: Sunday, November 7, 2021 12:18:34 PM To: LuSeKa/HoverBot @.>; LuSeKa/HoverBot @.> Cc: Comment @.> Subject: Re: [LuSeKa/HoverBot] Compiler Errors (Issue #4)

Did you try using the Adafruit BNO055 sketch they have on their website? I didn't copy the hoverbot code verbatim. Also do you have the motor drivers in close proximity to the BNO055? Are you using other I2C devices? Did you check that the address pre programmed on the BNO055 is matching your sketch?

Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: sylajen @.> Sent: Saturday, November 6, 2021 11:25:51 PM To: LuSeKa/HoverBot @.> Cc: CrispyFungus @.>; Comment @.> Subject: Re: [LuSeKa/HoverBot] Compiler Errors (Issue #4)

We were able to solve the compiling issue above and now we have another issue. We used a example code from Adafruit BNO 055 called sensorapi to test the IMU. We are able to verify and upload the code to the Arduino Mega but the serial monitor does not recognize the IMU.

The error we receive is:

Ooops, no BNO055 detected ... Check your wiring or I2C ADDR!Orientation Sensor Test

Ooops, no BNO055 detected ... Check your wiring or I2C ADDR!

The puzzling thing is that the IMU is detected when using Arduino Uno after checking via serial monitor. The wiring is the same when using both the Mega and the Uno so we think that this might be a hardware issue but we just wanted to ask you in case you ran into the same problem.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/LuSeKa/HoverBot/issues/4#issuecomment-962554455, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANHPRYMFDROREP54FSECCC3UKYLW7ANCNFSM5HMVHUBA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[sylajen]

Yes please the Segway sketch would be very helpful. We are also having troubles with recharging the battery with an iMAX B6 balance charger, where it says check cell, low voltage and won't charge the battery. We were wondering if this was an issue you ran into, or if it was something you know how to resolve?

[CrispyFungus]

My battery I custom built, there's 2 battery packs, I use a LUNA brand charger and an integrated BMS in the pack to make sure that the cells are balanced. As far as charging a lithium pack with a balance plug make sure thst the battery isn't below 3.2V/cell. Probe ground to each pin on the balance plug, the 1st shoukd be ~3.7v, the next 7.4, 11.1, and so on in multiples of the first cell's voltage. If it is not, then you have a problem with the battery and the charger shouldn't charge it otherwise there could be fire.

On Wed, Nov 10, 2021, 9:20 PM sylajen @.***> wrote:

Yes please the Segway sketch would be very helpful. We are also having troubles with recharging the battery with an iMAX B6 balance charger, where it says check cell, low voltage and won't charge the battery. We were wondering if this was an issue you ran into, or if it was something you know how to resolve?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LuSeKa/HoverBot/issues/4#issuecomment-965974833, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHPRYO7S3GDTLBUJ3CAULTULNAAFANCNFSM5HMVHUBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[sylajen]

We have the ODrive 3.6v, whereas it seems you guys have the ODrive 3.2v. Our ODrive supplies a voltage of 3.3V, whereas it seems yours had one that supplied 5V. Just wondering if that's something that would cause an issue?

[CrispyFungus]

Yeah if your bno055 requires 5v then yes it wouldn't turn on. Explains why when connected via usb you can see the imu.

On Wed, Nov 10, 2021, 10:11 PM sylajen @.***> wrote:

We have the ODrive 3.6v, whereas it seems you guys have the ODrive 3.2v. Our ODrive supplies a voltage of 3.3V, whereas it seems yours had one that supplied 5V. Just wondering if that's something that would cause an issue?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LuSeKa/HoverBot/issues/4#issuecomment-965995374, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHPRYLLSVHA6646L26AG2LULNGAPANCNFSM5HMVHUBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[sylajen]

Do you know any places we would be able to purchase this specific ODrive? Or if there's some chance you'd be willing to sell yours?

[CrispyFungus]

I actually happen to have a brand new spare never used, I'll probably never use it so I can sell it to you. I'll sell it $125 including shipping if you live in the US. My venmo is @JasonWason

On Fri, Nov 12, 2021, 10:14 AM sylajen @.***> wrote:

Do you know any places we would be able to purchase this specific ODrive? Or if there's some chance you'd be willing to sell yours?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LuSeKa/HoverBot/issues/4#issuecomment-967279375, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHPRYLW42FUMZYMXB2JDBDULVDNRANCNFSM5HMVHUBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[sylajen]

I will have to let you know about the purchase some time soon. We are curious though as to why you are drawing 5V from the ODrive and passing it to the breadboard with the IMU, ODrive and Receiver? Is it used for feedback somehow, or simply to power those components?

[CrispyFungus]

My circuits are custom and are by no means similar to the hoverbot, the Odrive has a 1A 5v bus to power other devices, it makes it simpler, along with the serial communication more reliable to be both powered and grounded to the Odrive. All peripheral devices such as lighting and sound on my project are powered by a separate 5v BEC regulator, but still switched on and off using a MOSFET controlled by devices from the 5v bus

On Wed, Nov 17, 2021, 8:56 PM sylajen @.***> wrote:

I will have to let you know about the purchase some time soon. We are curious though as to why you are drawing 5V from the ODrive and passing it to the breadboard with the IMU, ODrive and Receiver? Is it used for feedback somehow, or simply to power those components?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LuSeKa/HoverBot/issues/4#issuecomment-972499988, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHPRYJA55RYGECPYTT4IKLUMR2NZANCNFSM5HMVHUBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[LuSeKa]

@sylajen looking at the commit log of ODriveArduino, this is the commit that is causing the compiler error that you are seeing. There are multiple ways to work around this. The easiest is probably to replace the line that's causing (line 107 in HoverBot.ino) it with int requested state = AXIS_STATE_IDLE There might be more places where this needs to be changed. It looks like ODriveArduino has changed quite a bit, so maybe there are more changes that broke compatibility with HoverBot. Another option to work around all of them is to use the version of ODriveArduino of the time of the last HoverBot commit (3 years ago).

[LuSeKa]

Fixed in commit 598a4f9bca46923243acd8985dc611be21acde3f. Thanks for flagging this! @sylajen you can just pull the latest version of HoverBot and this issue should be gone.