OdriveTool error and sensorless mode question!

[Neurotronic67]

Hi, i am currently building a Raspberry robot car (H3CTOR) based on an RC car. I am using the Odrive 3.5 48V (that i received last week) for brushless motor control.

Question :

• My Rpi don’t detect the Odrive in odriveTool due to some issueI saw on Github, Is it possible to configure the Odrive and the motor using only a Python script and not the OdriveTool Ipython interface ? (Or is the code will be fix soon ^^)

• Is it possible to use a 7.4V 4400mAh Li-Po battery to operate the Odrive instead of a 12V batt ?

• Is there some exemple for Sensorless configuration and command ?

thanks fo the answer ^^

some photo :

[madcowswe]

Nice picture, looks like a cool project!

---

My Rpi don’t detect the Odrive in odriveTool due to some issueI saw on Github, Is it possible to configure the Odrive and the motor using only a Python script and not the OdriveTool Ipython interface ? (Or is the code will be fix soon ^^)

Do you mind trying this workaround?

ODrive doesn't show up in odrivetool

I was also having the same issue as @alan on Ubuntu 16.04 and v4.1 of the firmware. Based on the suggestion from @metanoic, I added ENV{ID_MM_DEVICE_IGNORE}="1" to the udev rule, so that modem manager ignores the device. This seems to fix the problem for me. I tried a few things before this, so hopefully it working isn’t a combination of previous debugging steps.

We do plan on doing something about this as soon as we can.

---

Is it possible to use a 7.4V 4400mAh Li-Po battery to operate the Odrive instead of a 12V batt ?

Sorry, we don’t support bus voltage that low. Please use a 3S battery.

---

Is there some exemple for Sensorless configuration and command ?

The sensorless algorithm we have right now doesn’t really make sense on a car. It doesn’t provide odometry, and can’t go slow. We could make improvements to this in the future.

[Neurotronic67]

Hi, thank you for your answer !
I don’t really know how to ENV{ID_MM_DEVICE_IGNORE}=“1” to the udev rule…
Do you have any tutorial in mind ?

(ps : i build an other robot using hoverboard motors ^^)

[Neurotronic67]

I write : SUBSYSTEM=="usb", ATTR{idVendor}=="1209", ATTR{idProduct}=="0d[0-9][0-9]", MODE="0666", ENV{ID_MM_DEVICE_IGNORE}="1"

in the etc/udev/rules.d/50-odrive.rules
then : sudo udevadm control --reload-rules

but it doesn’t work…

[sjd.aliyan]

I cannot say anything about the code but about battery you can use even 1 cell but you need a dc-dc converter.or you can use 3 cells as Oskar mentioned.
It depends on you.

[madcowswe]

I’m not sure exactly how it’s done, I asked here:

ODrive doesn't show up in odrivetool

We are working on a fix to an issue which we think is causing this. You can subscribe to it on github. Meanwhile, you can try these workarounds: on Windows: try to disable the ODrive CDC Interface in device manager on Linux: try @tamecoffee’s solution: Speaking of which, @tamecoffee do you mind elaborating how exactly to do this? Is it just like this? https://discourse.odriverobotics.com/t/odrivetool-error-and-sensorless-mode-question/954/4?u=madcowswe