I just received my Blackbox X32 and was so excited to plug it in and use it. The problem is it doesn't show any ports that i can select. I'm very new to this and I have no idea what to do. I was using an Arduino with stepper motor controllers and it worked but after I plugged in the BB X32 it does not. Any help would be appreciated. I have a 64bit windows 11. Thanks!
I don't know the software the terminology or a lot about computers. At first I did connect to the black box 32 but no fan or machine jog. I have installed drivers too many times to count. when I was connected I tried resetting everything even the eeprom settings, all kind of things I know nothing about . My drivers created a usb to UART bridge. I have uninstalled and reinstalled every bit of software. Very dumb things and very frustrating weeks.Is there away to uninstall everything and start over? I can't even figure out how to post, so I jumped on this one. Thanks
You only need to install drivers once. Does it connect now? If so. Drivers: DONE Fan and Motors needs POWER. If neither works, you don't have 24v coming into the BlackBox. Check PSU and wiring Do remember to load a machine profile: CONTROL > Grbl Settings tab > Select machine from the list > Save and reset when - blank eeprom won't know what machine you have
I am just trying to connect to the black box only no power. It will not connect to the controller software. When it did connect the fan did come on but it would not jog the motors. Yes I did save as 1010 Limit switches and Plasma on/off . Waiting for the upgrade. Not being able to connect I can't get into the Grbl Settings now. I was told that the box came already flashed but I flashed it anyway thinking it wasn't. Looking at some videos I noticed that the USB port seems to be configured as a FTDI USB to Serial not like my USB to UART Bridge. Thanks
Plasma On/Off is in the CAM setup - totally different application Check the dates of the video, BlackBox X32 is newer and V1.3 upwards uses the Silabs chip as explained in docs:blackbox-x32:install-drivers [OpenBuilds Documentation] Regardless, Drivers has "nothing" to with this because you could already connect after installing them, see your post above: Driver is fine, done. So why does it no longer connect? Well, as per the onscreen error when it fails to connect, you should visit docs:blackbox-x32:faq-usb-connection-failed [OpenBuilds Documentation] and work your way through it, driver was the lucky first guess (surprising how few customers read and follow the documentation step by step - not related at the moment but if you skipped section 4.1 about the driver installs you possibly skipped section 4.2 and how many other sections of the documentation?) Section 6.3.1 of the USB troubleshooting FAQ is perhaps related then. At the point above you had it working. Now it stopped. What happened in between? Short circuits in wiring? Incompatible components wired to the BlackBox? Review docs:blackbox-x32:faq-usb-connection-failed [OpenBuilds Documentation] carefully, i am guessing (but really hoping against it) that its something related to section 6.3.1 The fact it was working and then stopped - tells us it became damaged (hopefully recoverable, often times not) PS: If you know of any shorts, miswirings, incompatible/3rd party acccesories - best to disclose - we can help if we know - if not we end up spending weeks chasing around the other possibilities because if nothing is declared, then it can't be that Post detailed pictures of any wiring you'd like us to help you review as well
I bought everything from you. I installed both old and new black box drivers, I checked all wiring messaged parts created a ticket. they told me to do what you just stated. I got a little confused because some of the things the directions said to do was already done by you when you buy the kit, after it would not connect I disconnect all the wiring and just tried to get it to connect. trying anything I could think of. The log kept saying it could not recognize the firmware so I focused on the drivers installing the inf. file manually then uninstalling them. I even went back and restored earlier files from my trash thinking maybe I lost some coding I needed. Just tell me what you want me to try. Thanks
I am going to connect the motors, the limit switches, power wires and led lights and try again after loading the right drivers again but I think I need to remove all the drivers. I believe that it stopped because I kept playing with flashing and resetting of everything. The directions said $4=0 my settings were $4=7 (I think) parts told me the settings in the box were right, that's when I found out that the box was already flashed. Can you tell me how to remove the old drivers that I installed.
INF? Per docs:blackbox-x32:install-drivers [OpenBuilds Documentation] we link you to the nice Installer version (EXE) Perhaps you do have the wrong driver installed then? Weird though as you reported it was working
I downloaded cp210x vcp then opened the 64 installer and installed it then installed the slabvcp.inf many times. I don't know how things work but I would like to removed any drivers that I installed for the last black box version. Thanks Did I install the drivers correctly
At first yes, the additional uncalled for INF steps - not sure If correctly installed you should see it in Device Manager under Ports If you double click on it, check the Drivers tab, this is what I have The Uninstall button at the bottom there has a popup if you wanted to delete drivers (if its not the right one installed)
When I try to update driver windows will not install it or can not find it. Driver slabvcp.inf " this driver is not digitally signed" I changed my system settings to load drivers that are not signed, still will not install. First time I did that maybe I didn't do it right. I did not connect the motors or switches yet just the Black Box 32. Thanks
Use the installer! Stop with the INF, update driver and other uncalled for steps. No where in this thread, our documentation or Silabs documentation does the screenshots you took feature as the right way to install the driver Uninstall this unsigned inf driver you found somewhere (button shown above) and install the correct driver, from Silabs using the EXE installer. As easy as download, extract, run, next next next finish. Silabs Drivers are signed, so whereever you found the random unsigned and thus incorrect driver - that's where you created all your own troubles. Follow the documentation and guidance we provide.
Thanks for the help. I know you're not here to answer computer questions, but thanks. I'll have someone help me with the driver installation. The driver I have using came from your driver link. docs:blackbox-x32:install-drivers [OpenBuilds Documentation] Thanks again Frank
Or somewhere else, as yours isn't signed. The installer version IS signed Its so simple, if you just please follow what I tell you 1) uninstall the unsigned driver (Properties on the device in Device Manager, Driver Tab > Click Ininstall Device > Click checkbox for DETELE THE DRIVER SOFTWARE FOR THIS DEVICE > Click UNINSTALL 2) Go to docs:blackbox-x32:install-drivers [OpenBuilds Documentation] and download https://www.silabs.com/documents/public/software/CP210x_VCP_Windows.zip 3) Extract it Run the appropriate installer whether you have 32 or 64 bit OS 4) Replug the USB Cable, it should reinstall itself as device (Windows found new hardware) and use the driver that came from the installer: 5) Done, should see it in PORTs in Device Manager: 6) and its properties will show a nicely signed driver
I followed your directions about five times by uninstalling all of your software and drivers and reinstalling them but it still reads needs further installation but they are listed in the events but still does not connect on the Black Box. I'll keep trying. Thanks
Does it show as NodeMCU in CONTROL yet? Latest Device Manager screenshots shows the right device name at least PS: With all these things ONCE is enough - don't waste your time - build up frustration, etc. Pop back in after the first time. Theres a marked improvement in it showing the Device name so once probably did the job.
I only retried when it didn't connect. Yes it has been showing "NodeMCU com 6" for awhile now. Thanks Is the Baud rate for the drivers 9600 or 115200, just looking for something.
Great then finally the drivers are fine. If it can read the ID then finally the drivers are no longer the issue. Back at Blackbox X32 - Driver where it was only showing the COMx without the ID that was clearly drivers. So, onto the next, there are two chips on the BlackBox. PC > Talks to SiLabs chip. SiLabs chip talks to main chip. Any known wiring mistakes, wrong power supply or similar events that could have damaged the other chip? 1) see Section 6.3.1 of docs:blackbox-x32:faq-usb-connection-failed [OpenBuilds Documentation] 2) if that doesn't work, try reflashing firmware: CONTROL > Wizards and Tools > Firmware flashing tool > BlackBox X32 tab > Flash. I am expecting (2) to fail to activate bootloader (i.e. Main chip dead) but then the question is, what killed it. Because replacing it under warranty gives you one shot. If the same thing (short, 3rd party PSU or VFD or similar, ie preventable mistakes) kills it again, its not going to be possible to warranty it.
When I first connected I was working while watching your video, I tried to jog the table nothing, I noticed the location in the video but my X,Y and z locations were ll at 0. Table would not jog tried to set home still nothing. I checked the z axis motor it felt like it had a lot of resistance on it so did the others then I turned the coupler about half a turn which I read somewhere much later that turning the motors by hand with the power on mite cause problems sending power back into the controller. Turned the power off and motors turned freely. In my mind I only turned the motor a little I didn't think it would have caused any problems. I can't remember but I think I was still connected after turning the motor. I went into the grbl settings and reset everything eeprom etc. I'll try flashing the box but I have already try that many times but that was before reinstalling the driver. Thanks Just flashed the Black Box with nothing connected, would not connect. When it wouldn't jog was when I first flashed it. It was still connecting with the Black Box and the power on and the motors connected the "motors enabled" led light would come on. No lights are on now. When it connected the fan would come on.
Then it is dead. You can contact the store via Support > New ticket - but again, do keep the note in mind, if what damaged this one happens again, it won't be covered under warranty. (Well, technically becoming damaged is not even covered under warranty at all and we've done extensive troubleshooting from our side already) When you get the new one - test it properly BEFORE wiring up. Then wire up per docs.openbuilds.com - no guesswork. Then connect, load a machine profile (CONTROL > Grbl Settings tab > Select machine from the list --- this was the step you skipped over completely in the beginning - how can it enable motors etc if it has no idea what machine to set up for -- and the Save > Reset when Prompted)
Ok I'll go step by step and stop if it doesn't do what it's supposed to do and ask questions before going on. I did in the cam software set Black Box 32, 1010 lead, plasma on/off and limit switches. Thanks for all your help
If the Installer version doesn't work, try https://www.silabs.com/documents/public/software/CP210x_Universal_Windows_Driver.zip instead? This one you do the Driver tab > Update driver method (its not an installer)
Just received my replacement Black Box and it connected right up and I was able to jog motors. Now I must learn how to set home, set G53, G54 and limit switches. Thanks for all your help
