I have been asked by OB to post this issue on the forum, to see if anybody else has run across the issue I have! I'll try to keep it as short as I can Had been running with OB bb32 for 5 months, when after 2 weeks of inactivity I can't connect to bb32. Try the normal troubleshooting advice and steps with no luck. Got in touch with OB by email for more input. Did the troubleshooting steps again! same result! Without request OB sent out a new bb32 hoping to solve the problem "by the way GREAT support on the part of OB" trying to shorten the story I took the first board out of the machine to remove any short issues. Hooked up the new bb32 to USB only to try to connect same result! Tried another computer "connect" NodeMCU com4. Not wanting to use my banking laptop for the machine, I thought I'll get a new laptop just for the machine and solve any future problems with the machine. Well not so fast!! I'm posting the results from testing from 4 different laptops and 2 different windows versions. here Goes. The first results are from my banking laptop NodeMCU com4. [13:36:01] [ 3D Viewer ] WebGL Support found! success: this application will work optimally on this device! [13:36:01] [ websocket ] Bidirectional Websocket Interface Started Succesfully [13:36:02] [ update ] Checking for Updates [13:36:03] [ update ] You are already running OpenBuilds CONTROL 1.0.370 [13:36:11] [ usb ports ] Detected a change in available ports: [COM4] [13:36:13] [ connect ] PORT INFO: Port is now open: COM4 - Attempting to detect Firmware [13:36:13] [ connect ] Checking for firmware on COM4 [13:36:13] [ connect ] Detecting Firmware: Method 1 (Autoreset) [13:36:13] [ ] ok [13:36:14] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [13:36:14] [ ] GrblHAL 1.1f ['$' or '$HELP' for help] This set of results is from the original machine laptop NodeMCU com3. [13:37:42] [ usb ports ] Detected a change in available ports: [COM3] [13:37:50] [ connect ] PORT INFO: Port is now open: COM3 - Attempting to detect Firmware [13:37:50] [ connect ] Checking for firmware on COM3 [13:37:50] [ connect ] Detecting Firmware: Method 1 (Autoreset) [13:37:50] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [13:37:51] [ connect ] Detecting Firmware: Method 3 (others that are not supported) [13:37:54] [ connect ] ERROR!: No supported firmware detected - See docs:blackbox:faq-usb-connection-failed [OpenBuilds Documentation] for more details. Closing port COM3 [13:37:54] [ disconnect ] PORT INFO: Port closed this set of results are from brand new windows 11 HP laptop NodeMCU com3. [13:42:59] [ 3D Viewer ] WebGL Support found! success: this application will work optimally on this device! [13:42:59] [ websocket ] Bidirectional Websocket Interface Started Succesfully [13:43:00] [ update ] Checking for Updates [13:43:00] [ update ] You are already running OpenBuilds CONTROL 1.0.370 [13:43:11] [ connect ] PORT INFO: Port is now open: COM3 - Attempting to detect Firmware [13:43:11] [ connect ] Checking for firmware on COM3 [13:43:11] [ connect ] Detecting Firmware: Method 1 (Autoreset) [13:43:11] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [13:43:12] [ connect ] Detecting Firmware: Method 3 (others that are not supported) [13:43:15] [ connect ] ERROR!: No supported firmware detected - See docs:blackbox:faq-usb-connection-failed [OpenBuilds Documentation] for more details. Closing port COM3 [13:43:15] [ disconnect ] PORT INFO: Port closed The last set of results are from a much older ie 2014 laptop running windows 10 connected and running! NodeMCU com3 [13:32:39] [ disconnect ] PORT INFO: Port closed [13:32:44] [ connect ] PORT INFO: Port is now open: COM3 - Attempting to detect Firmware [13:32:44] [ connect ] Checking for firmware on COM3 [13:32:44] [ connect ] Detecting Firmware: Method 1 (Autoreset) [13:32:44] [ ] ok [13:32:45] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [13:32:45] [ ] GrblHAL 1.1f ['$' or '$HELP' for help] I know I should be happy I have 2 laptops that will run the machine! But after buying a new laptop that won't run the machine, I have concerns and questions weather or not other in our user group have had or will have issues in the future. Is this a windows issue!! that could hit us at some point. Looking for feedback to hopefully help all users and OB with this issue Joe May
there are so many variables! are all these tests with the same USB cable? that might be the root issue, bad cable, bad life (-: are some of the tests plugging into a USB3 socket? not all USB plugs handle USB3 sockets properly, and not all OS drivers handle USB1/2 plugged into USB3 properly. have you tested with laptop PSU plugged in/unplugged? They can be very (electrically) noisy and interfere with USB, so do try without the PSU's plugged in. and don't forget that Windows likes to disable USB sockets if they are not being used to 'save power'. That can make your USB connection to the Blackbox seem random. docs:blackbox-x32:install-windows-selective-suspend [OpenBuilds Documentation] and finally, check this list of things to check.... docs:blackbox-x32:faq-usb-connection-failed [OpenBuilds Documentation]
We worked with Joe extensively via tech support. Main thing is the BlackBox is fine (As it works on some of his machines). The other two PCs maybe could do with a quick reinstall of Windows or similar, but we don't see anything on our end of things we could do further. David has a good point though to look for other variables that we might overlook like using the same cable (Instinctively I would use the same cable for these tests, so would not think to question it) I have a feeling something on the affected PCs are either triggering DTR/RTS out of sequence (serial handshake signals) or at the wrong timings. Make sure you have the proper signed official drivers CP210x USB to UART Bridge VCP Drivers - Silicon Labs Open the top lid of the BlackBox and move the Run/Flash jumper to RUN mode (disables DTR reset - makes future firmware updates harder but might sidestep a signal timing issue) On one of the affected PCs, open Device Manager and go to the Ports section. Select the Silabs port and open its Properties Click on the Drivers tab and click Driver Details Check that your DONT have this: Version 6 drivers are too old! You should ONLY have these THIS: and must be V11.3.x or newer Make sure that silabser.sys is on latest version https://www.silabs.com/documents/pu...10x_Universal_Windows_Driver_ReleaseNotes.txt (11.3.0) and is signed.
My testing method is keep everything the same only change one thing at a time. All laptops plugged in to ac power, one USB cord for all tests, and the same board BB32, new from OB's reading thru your post looking at driver issue I see the 3 different drivers you talk about. I removed the driver, rebooted the laptop that has the issue, only to have the 3 drivers come back! Is there another method I can try I'm following the steps in the link you posted for the driver short of SETUP REGISTRY KEY or is this the only way out! Joe May
File paths are shown, could try deleting the actual files. But Device manager should do a cleanup if you tick the tickbox:
a) please don't use a phone camera to screenshot Copy the window or screen contents - Microsoft Support Use Snipping Tool to capture screenshots - Microsoft Support b) Don't crop out useful info, frame the whole window - if yours wasnt cut off I could have seen versions and signatures (; Example:
Did as directed, and it deleted the drivers. also tried deleting directly in windows 1 said it was being used by another program. I feel we are on to the source of the problem. Now how to get things setup the right way. As you had done with device mgr. could you detail the driver install steps @silabs site? It can be confusing as to what tabs and downloads to pick " drivers for newbies and oldies" Joe May
I tried a test here, seems the older (installer) based driver indeed does install 3 files. I suspect yours shows Version 6x? But the newer https://www.silabs.com/documents/public/software/CP210x_Universal_Windows_Driver.zip is the single file version (V11.3x). Might be worth playing with both, see which one works better for you
Writeup draft: 1) Download https://www.silabs.com/documents/public/software/CP210x_Universal_Windows_Driver.zip and extract it somewhere like your Downloads folder 2) Plug in the BlackBox X32 3) Go to Device Manager and find the Silabs / CP2012N / unknown device: 4) Right-Click on it > Properties > Drivers tab On a new install no drivers will be installed, on a malfunctioning install, some other drivers might be installed. 5) Click on UPDATE DRIVER 6) Click on BROWSE MY COMPUTER FOR DRIVERS On the next window, click Browse and locate the drivers you extracted in the earlier steps as shown Select it and click Next 7) Windows will complete the installation: 8) Now the Driver's tab on the Device's Properties in Device Manager will show If you are seeing Version 11.3.xxx then its the right driver Test if the BlackBox can now connect in CONTROL
That's Windows 7 days? https://www.silabs.com/documents/pu...10x_Universal_Windows_Driver_ReleaseNotes.txt says Windows 11 support was added in drivers version 11.x Keep at it until you get to v11.3... Safe mode cleanup of outdated the files, something like that maybe? And that one - only has this:
It looks like the driver is coming from a windows restore drive on the laptop. It seems that it is over ridding the new driver install. I don't know what the best way to over ride what is going on it keeps putting the 2013 driver in version 6.7.0.0 Joe May
If you write down the paths, reboot into safe mode with Blackbox unplugged, they shouldn't be loaded, so shouldn't be in use?
Even the new HP laptop with windows 11 has the 2013 dated driver. when I try to update drivers I go thru browse,goto downloads pick the just downloaded driver file click on to update windows comes back with "the best drivers for your device are already installed" Joe May
Ok got rid of old driver! I go to the the link on the OB page to download driver, download but no application to install the drivers shows up and doesn't activate an installation. So no drivers are being installed. I just ran across something. In driver release notes it says for Windows 10 version 1803 and later My version of windows 10 version 10.0.2.1000 could this be the issue? Another place in settings about I see version 22h2. I don't know what to make of what I'm seeing, weather windows is up to date enough or not. I just know the drivers aren't loading now. Joe May
Windows Key + R > winver > enter I am on 22H2 as well, learn more about which versions came when at Microsoft Windows and which are still active and which are retired etc Scroll back up and read the info I give you, you seemed to have skipped over some info ZIP/INF based setup, I showed you step by step yesterday above here ^ in Post #11
Peter you rock thank you for your time and effort dealing with this old fart! It was in there I was just over looking it. ### Manual install ### 1. Using Windows File Explorer, locate the driver folder (that you previously unzipped) 2. Right click on the silabser.inf file and select Install 3. Follow the instructions!!!!! Thanks again Joe May
