I have had the same issue. Q: Does the interface lead need to be disconnected from the Black Box FIRST to allow the black box to then divert a switching circuit to connect correctly and fully to a PC via the USB socket instead of the Interface? I'm sure I read deep in the docs somewhere that there can be an issue connecting a computer via a USB cable to the black box if the black box is still communicating to an interface. One single comms lead at any time only. Perhaps? I will investigate further once I have an internet connection near the machine to read online and diagnose this and other problems in situ. Also, perhaps dl and install the OpenBuilds USB drivers for the relevant computer being used? Good luck.
No. Presence of USB cable determines it, not Interface cable. Read docs:interface:connect-blackbox-x32 [OpenBuilds Documentation] > important note no 1, which contains link to supplementary info at the BlackBox documentation, docs:blackbox-x32:aux-serial [OpenBuilds Documentation] which explains it in more depth Use Computer, or Interface not both.
Sorted the connection issue. Needed to update USB drivers on the connecting PC with the "OpenBuilds" version from the website. (Installed Ethernet/Internet in workshop today.) Following that action it is now possible to make a connection using COM3 port. Have calibrated the axis travel distances and have done a practice run of a file OK (using a pen, no plasma). Just have a old sticky ballscrew to rebuild and clean on the Z axis but things are going well. cheers.
