This issue is similar to others that have been posted in the forum, though I have not gathered enough information from the solution from those posts to solve this issue.
I have a number of 48V ODrive 3.5s for a machine tool application. When I plug in one of the drives via USB to the win10 PC, I only see one interface in Zadig which is the CDC interface. I was originally using a 24V 3.4 model, which I was able to connect on the native interface using libusb-win32. I think I may have screwed something up with the drivers since I don’t ever remember seeing more than one interface on Zadig, and I installed libusb for the CDC interface. Anyway, somehow it worked OK. I then upgraded to the 3.5 and all was well.
Fast forward a bit and I was trying to use the ODrive with a USB hub before I knew this was not supported by libusb (that is my understanding, anyway). I did a lot of installing and uninstalling drivers to try to figure out what was going on, then I read that libusb doesn’t support hubs. That is unfortunate but not a dealbreaker. However, now I cannot connect to the drive on the native interface on this PC at all. I see only the CDC interface in zadig, and switching to usbser and attempting to use the ASCII protocol does not work either.
It is worth mentioning that I have no issue communicating with the drive using a different PC (same cables, for the record, so those are not the problem), which shows both the native interface and the CDC interface in zadig. No problems there. I can communicate with both the native interface and the USB serial. There is something amiss with the original PC, which is the one that I need the drive to work with. Also, I recently upgraded the firmware on the drive to the latest version (0.4.7) to include bugfixes that were released to address problems with USB communication of the drive. Still fine communication to the second PC.
I am hoping that someone might be able to offer some input on this. I see that some other members had problems where they didn’t see both interfaces in zadig. Perhaps I have a driver mixup?