I’ve read everything I could find, tried all that was suggested but I cannot get an otherwise working Odrive S1 to communicate, neither with the GUI, odrivetools. Replaced the unit with a spare and all works fine as before.
Technically we are very happy with the Odrive it does exactly what we need on our special cable winches. We are still in development and need to make frequent parameter changes to tweak the operation, so being able to communicate with the device is very important.
Here is what it does on a very old windows laptop; communicates with the GUI, tried to do a factory reset by reinstalling the firmware but its stuck on entering the DFU? programming mode.
Unless the greater group has a solution, I’d be inclined to request an RMA and return as defective.
That’s super fascinating. What firmware version is running on the ODrive? Do you have a Linux computer (even a Raspberry Pi or similar) you could try with?
So it’s just this specific S1 that’s having issues on the newer computers?
Correct it’s only one of 3 ODrive S1 that refuses to communicate with Laptop running Windows 11 latest update.
The last time it was working correctly I was connected to 2 0drives AND Ardupilot Mission Planner. That’s when it stopped working. Thereafter we are sure to shut off Mission planner before we connect the USB to Odrive and only to one at a time. We’re in the dessert in Old Mexico and can’t afford to brick another unit.
We tried Android Tablet and Samsung Galaxy Z fold 5.
As you can see from the screenshot it’s working fine. I used the inspector on the GUI in order to obtain the serial numbers, hardware and software revision. However the webserver Software was not designed to run on a phone so the Windows are not scaled properly, so it’s not practical for field use.
I could connect a Raspberry Pi but it would be easier to run Ubuntu in the Windows laptop. I’ll try that if I have time as we’re running trials this weekend.
Thanks for all the detail, it really helps!
On the new laptop, can you check to see if the ODrive shows up in device manager?
When you’re testing with the different computers, are you using the same USB cable each time? Is it a USB A-C cable or a C-C cable? Are you using a USB isolator / is there any difference in functionality/connection with versus without a USB isolator?
I’m curious if mission planner is doing something screwy with the device drivers in Windows – it should be an easy fix – if the ODrive shows up in device manager, just right click → “uninstall device”, then disconnect and connect the ODrive to the computer. That should re-initialize the drivers to default.
If it still doesn’t work after that, let me know your original order number and I’ll get a replacement sent your way!
Different Windows computers, same cables from S1 to computer direct USBC to or via USB C docking station, USB B to C with or without Odrive isolator, makes no difference result is always the same, The S1 that doesn’t like my laptop will not WAKE either Chrome or Edge immediately after being plugged in. However if I load the GUI on the compatible browser it does offer to connect to a “Paired device S1 Odrive”. I select the device, it tries to connect but the red banner at the bottom of the screen lights up after a while.
Odrive does open COM3 in the Device Manager but the name Odrive does not appear. Mission Planner uses COM6 or 5 & 14 for telemetry data. Under Properties I get this:
usbser.sys
I uninstalled the driver, unplugged and plugged in again and Windows installed the same driver with exactly the same results. Let me try Ubuntu on the same laptop, then I will send the order number.
Thanks for your support so far.