Pybricks Connection Problem
I want to connect my Lego Mindstorms 51515 Hub to pybricks and install the pybricks firmware but it dosnt work. I can't even install WinUSB driver. It glitches with error code 10. I was doing it on a lg gram 2022 laptop running windows 11.
I expected the firmware to be installed on my hub correctley.
Does the device show up in the Windows Device Manager as "LEGO Technic Large Hub in DFU Mode"?
Do you have a different computer you could try?
No it doesn't show up as Lego technic large hub in dfu mode it shows up as Other Device and sometimes WinUSB Device. I don't have any other computers to try it on.
Is the Bluetooth light on the hub blinking red (pink)/green/blue/off? If not, then the hub is not in DFU mode and that is the problem. If it is, I would try deleting the device from the Device Manager and start over.
It was in dfu mode but it didn't show up.
Can you share a screenshot of your Device Manager? There should be something in there with a :warning: icon if the driver is not loading correctly.
If you right-click that and select Uninstall device then disconnect the hub and plug it back in (making sure to hold the Bluetooth button to get DFU mode) what does it say?
It dosen't even show up on device manager anymore.
Maybe there is a bad USB cable or something like that?
I tried a different cable but it still didn't work.
On my Windows 11, if I uninstall the device like I mentioned in https://github.com/pybricks/support/issues/1368#issuecomment-1879778338 and then unplug the hub and plug it back in, I see this:
You are not seeing this after following the same steps?
Yes.
I'm afraid I've run out of suggestions. It sounds like there could be a hardware issue on your computer or a broken Windows installation if the device is not longer appearing even after a reboot of everything (the hub and your computer).
I don't think it's my computer. I tried it on another computer but it didn't work. Thank you.
This has come up in several other topics. In those cases, using a different (or the original) USB cable fixed it. Let's close this issue until this occurs again. Thanks!