So i recently acquired a Longmill with a rotary as well as an SLB. I was getting acquainted as I have a spindle system from PWN coming in for it. I noticed that the firmware was a few versions out of date. Gsender is being ran from a new to this machine computer by the way (Surface Pro 7). I could pick up the device but it didn’t recognize it as an SLB, i assumed it was due to drivers. Anyways, going through the process and I get the error regarding drivers mentioned in the tutorial. I downloaded Zadig and replaced the drivers for the USB C device with WinUSB, and put in the $DFU command. Now it is not recognizing any device is plugged in (which i assume is a function of that mode?), but it also is not picking anything up when I try to flash the firmware still. Same “Info: Erasing chip starting at address 8000000 - size 287904
Error: Unable to find valid device using vendor ID “483” and product ID “df11”. Make sure the device is in DFU mode.” I was getting before.
Anyone have any experience with this? Should I manually put it in that mode via the terminal jumping or whatever the other option is> In Device manager it now shows up as “STM Virtual ComPort”
I still do not have this problem solved, but I was able to sucesssfully flash the slb by manually jumping the pins to get into DFU…But I still cannot find the SLB in Gsender… Frustrating
Dillon:
Lets just try something
Disconnect your slb from your computer (usb cable), power cycle you SLB.
Power cycle your computer.
From your device manager can you see any com ports? If you can leave your device manager open.
Connect your usb cable to your POWERED ON slb.
Then connect it to an avaible usb port connection
Does another usb connection pop up in your device manager (Mine is com6)
So STM32 can see the SLB.
At this point , I would do as the resource says.
Do not flash your SLB unless you’ve done it before and are absolutely sure you know what you’re doing or are being guided by our team. The flashing process can be touchy the first time, so if you’re having problems then please contact our team first otherwise be prepared to accept a regretful outcome.
I know this won’t please you but follow that course of action. Contact Sienci support.
Theyre sending me a new SLB. I cant imagine the two i have are bad, especially since they show up on my other computer. I’m stumped regarding the matter.
Going back to my freestyle drone building days with STM32 boards, Zadig can be confusing. If memory serves you sometimes have to uninstall the driver in Zadig so that your pc will recognize it as a COM port again.
Closing this out, from what I understand @Dillon-Barton wound up with the driver for the SLB deleted. This might’ve happened while doing stuff in Zadig, but either way apparently reinstalling the driver from STMs website got it all back up and running. Here’s the link in case anyone else happens upon the same issue, otherwise I’ll add this note in the docs too in case anyone else ends up in the same situation
