So, I think I may have messed up my Black box, I wanted to try out Estlcam with my Workbee, I have used it in the past on a different CNC and control board and it worked without problems. I read from some different threads that you can try it out and if you don't like it, you can restore the controller. Well, I could not get Estlcam to work on the BB and when I clicked the restore controller button nothing happened. In the control software for openbuilds I am getting the following message. ERROR!: No supported firmware detected - See docs:blackbox:faq-usb-connection-failed [OpenBuilds Documentation] for more details. Closing port COM3 [10:45:54] [ disconnect ] PORT INFO: Port closed [10:51:10] [ connect ] PORT INFO: Port is now open: COM3 - Attempting to detect Firmware [10:51:10] [ connect ] Checking for firmware on COM3 [10:51:10] [ connect ] Detecting Firmware: Method 1 (Autoreset) [10:51:10] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [10:51:11] [ connect ] Detecting Firmware: Method 3 (others that are not supported) [10:51:14] [ connect ] ERROR!: No supported firmware detected - See docs:blackbox:faq-usb-connection-failed [OpenBuilds Documentation] for more details. Closing port COM3 [10:51:14] [ disconnect ] PORT INFO: Port closed Is there anything I can do to save this or am I out of luck?
If EstlCAM didnt damage the Bootloader, you might be able to reflash Grbl from CONTROL > Wizards and Tools > Firmware flashing tool.
I did try the Firmware flashing tool and no luck, but I was able to get Estlcam working by switching the control hardware to the Spark-concepts Xpro V3 / V4 profile, I just can't go back to the openbuilds control software. Lesson learned I should stay in the openbuilds ecosystem with openbuilds electronics.
Post a screenshot of the log of the flashing attempt. Its unlikely Estl would have overwritten the Bootloader - at least they didn't used to
Yip, order a $3 USBTinyISP from amazon, and use the standard Arduino Uno bootloader process from the Arduino IDE. Still sceptical that it would be wiped though. Nothing in the log sounds unlikely too. It should show some steps as it connects, waits, tries flashing etc.
