How to set up connection between the ODrive firmware v0.5.6 with ODrivetool?

Dear all
I’m a new learner for ODrive ,May I ask some questions?
question 1:
I have downloaded the ODrive firmware v0.5.6 into the target board, but how to set up the connection between the board and ODrivetool? what i mean is which version ODrivetool i should use for ODrive firmware V0.5.6 ? or how to install the corresponding version ODrivetool ? and after installation, what command i should type on the screen to set up the connection?
question 2:
I have tried another test, i downloaded the ODrive firmware v0.5.1 into the target board,but i couldn’t set up connection with ODrivetool too. below is the alert message


question 3:
I downloaded the ODrive -fw-v0.3.6 _keil version into the target board, and connected to PC with a mini usb cable, but I hardly found it on the Device Manager.
so would you please give me some advice on these issues?
Thanks a lot

Hi!

what i mean is which version ODrivetool i should use for ODrive firmware V0.5.6 ?

You should use the latest ODrivetool.

and after installation, what command i should type on the screen to set up the connection?

It should automatically connect over USB when you run odrivetool, and USB + DC power to the ODrive is connected.

I have tried another test, i downloaded the ODrive firmware v0.5.1 into the target board,but i couldn’t set up connection with ODrivetool too. below is the alert message

Can you post the whole error message? There’s not enough information here to help with debugging.

I downloaded the ODrive -fw-v0.3.6 _keil version into the target board, and connected to PC with a mini usb cable, but I hardly found it on the Device Manager.

v0.3.6 is very very old – that’s the firmware version, not the board version. I’d recommend using v0.5.6, which you can download here: ODrive Releases

Dear Solomondg
First thanks for you reply very much, after the latest ODrivetool was installed, now the target board can be connected with ODrivetool.
thanks a lot again

Dear Solomong
Now i tried to connect ODriveGUI with target board, such picture is present


i noticed that the top left corner menu is imcomplete The menu selection of “WIZARD” and “tunning” is missing ,if i should solder all components on PCB then power up it

Best regards
Stephen

Hey Stephen,

That’s an old prototype GUI we made for ODrive v3.6 – it’s not under active development, and hasn’t been in a while. The official web GUI is only compatible with the newer ODrive products (S1/Pro/Micro), I’d recommend just using ODrivetool for v3.6.

Dear Solomondg
Sorry for bothering you again. what I mean is the target board is downloaded the ODrive fw v0.5.6 and it can be connected with the latest ODrivetool v5.4 well . what you mean is the file odrivegui.exe is not supported and maintenanced ,so it is not recommed to use this old prototype GUI now,while the official WEB GUI is compatile with the newer ODrive products,such as S1/Pro/Micro. so that is I can use the WEB GUI to connect my target board and control it ?

Best regards
Stephen

what you mean is the file odrivegui.exe is not supported and maintenanced ,so it is not recommed to use this old prototype GUI now

Correct

while the official WEB GUI is compatile with the newer ODrive products,such as S1/Pro/Micro

Correct

so that is I can use the WEB GUI to connect my target board and control it ?

Only if you have an ODrive S1, ODrive Pro, or ODrive Micro, it’s not compatible with the ODrive v3.6

Only if you have an ODrive S1, ODrive Pro, or ODrive Micro, it’s not compatible with the ODrive v3.6s
-------- I see, then thank you a lot again

No worries, please let me know if there’s any other way I can help.

Dear Solomondg
I’m very sorry, I still need to disturb you again, why i can’t find the USB interrupt function in stm32f4xx_it.c file?and where the semaphore sem_usb_irq is released? I found them in ODrive fw v0.3.6 easier, but I can’t find them in ODrive fw v0.5.6.
Another question is the funciton usb_server_thread() can be used to enumerate with computer and after enumeration can be used to communicate with upper machine, is it right?
because sometimes the code is programmed with C++ language,so it is a little difficulty to read and comprehend .
Thanks again .
Best regards
Stephen

Hi! Sorry, I’m definitely not the expert in the ODrive v3 codebase (fw v0.5.6). It’s definitely a pretty complex codebase – I think the USB interrupt will definitely be in a different location than default, there’s not much of the autogenerated code used there. Maybe look here? ODrive/Firmware/communication/interface_usb.cpp at master · odriverobotics/ODrive · GitHub

Dear Solomondg
Thank your very much for your kind reply again.
wish you a happy day.
Best regards
Stephen