Hey everyone, I was loading up my PC with v1.0.279, connected everything, homed the machine. Everything normal. I got the prompt to update to v1.0.280.... sure, why not. It updated and now when I connect to the machine, it doesn't let me do anything. The home button is greyed out and I can't jog at all. It still seems to connect and detects the firmware. I've rebooted the machine and the pc, but get the same results. Any ideas on what to try? Thanks!
What's the serial log say? Previous releases here, but would like the serial log before you downgrade: Releases · OpenBuilds/OpenBuilds-CONTROL
Sorry, I had an old download for .269 and already re-installed that. Works perfectly and is carving away. Once it's done the carve, I'll update to .280 again and see if it does the same thing.
ok, carve finished. I updated to .280 again and I have the same problem. here is the serial console when I connect: [20:48:56] [ 3D Viewer ] WebGL Support found! success: this application will work optimally on this device! [20:48:56] [ websocket ] Bidirectional Websocket Interface Started Succesfully [20:48:57] [ update ] Checking for Updates [20:48:58] [ update ] You are already running OpenBuilds CONTROL 1.0.280 [20:49:02] [ connect ] PORT INFO: Port is now open: COM4 - Attempting to detect Firmware [20:49:02] [ connect ] Checking for firmware on COM4 [20:49:02] [ connect ] Detecting Firmware: Method 1 (Autoreset) [20:49:03] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [20:49:04] [ connect ] Detecting Firmware: Method 3 (others that are not supported) [20:49:04] [ ] Grbl 1.1h EVOLUTION 4 ['$' for help] [20:49:04] [ ] [MSG:'$H'|'$X' to unlock] [20:49:06] [ connect ] Firmware Detected: grbl version 1.1h on COM4 And that's it. It doesn't go on to list all of the values of the firmware like usual. It also doesn't throw the alarms like it usually does. Normally I have to unlock the alarms on first connect, then the Home All option is available.
1) uninstall CONTROL first - the continuous update may be because your current install has some corruption 2) reboot 3) install v1.0.280 manually from software.openbuilds.com (not an old version + update. Go straight to 280)
I got the prompt to update to .281, so I tried that. Same issues. I uninstalled, rebooted, and installed fresh the .281 exe from the website. I get the exact same issues, so I don't think it's a corrupted update. Any other ideas? For reference, I downloaded the .276 release and installed it. Here is the serial log on first connect: I unlock the alarms and it homes normally. I guess I'll just snooze the update for a while until this gets sorted out?
I have the same problem (exactly as Geo Geer reports in his serial log). For what it is worth, I have been using OpenBuillds Control on a Raspberry Pi, and the same thing happens on that when it was upgraded to 280. Having no recourse, I went back to my Windows machine and carved successfully last night on a previous build. This morning, when I went to continue with the project, it asked me to update, so I did (not knowing of the issue), and my Windows machine came up with this issue. The only old install I had for Windows was a 234, so I uninstalled 280 and installed 234 and it worked fine. Like Geo, I will pause updates for the time being. I will also enter an issue on the GitHub for the Raspberry Pi version.
Press Ctrl+Shift+i Click CONSOLE tab in the Devtools Press F5 Screenshot any errors If there are no errors yet, try connecting first, see if any errors appear in the Console in Devtools after connecting Thats not a standard Grbl startup string. Some custom fork? May be part of the comms issues? Please provide the HEX file and I'll flash and test with it on this end too Do check the console tab as described above first though.
I uninstalled (deleted C:\Program Files\OpenBuildsCONTROL) Rebooted Then installed v281 from OpenBuilds Software - FREE Software for CNC Control: OpenBuilds CONTROL and OpenBuilds CAM Everything seems to be working again. Peter, you were correct about there being multiple instances of openbuilds running... one of which could not be terminated from windows task manager, which i've never seen before. Thanks everyone.
Hi Peter, I did not have any errors on the Windows machine when I used the Devtools Console. This was after completely uninstalling and installing 281 from the website, but the problem still persists. I have included the HEX file for the GRBL flash, for the 1.1h EVOLUTION. I had to change the extension from hex to txt in order for it to allow me to upload.
Flashed it to my testbed, and - same result as you - something funny in that firmware, or at least its not giving some response we expect to see. Will dig in and see what specifically and get back to you shortly
Found what's different, this firmware doesn't have Variable Spindle enabled which is the Grbl Default, and that is one parameter we check (for use with the Override sliders) I will add a workaround in v1.0.282 to ignore it it cannot find the [f:] feedback string in the realtime feedback parser. Good bug, edge case with unexpected non-standard firmware (we can't test every flavour there is, so finding outlying cases like this is very interesting)
So I take it you are also running a non-standard Grbl build Glad it sorted yours out too then if that's the case
I haven't specifically changed the grbl build, as far as I know. I built my Bobs CNC Evolution 4 a few weeks ago, then hooked it up to OpenBuilds Control and everything worked. I haven't changed anything... that's how it came from Bob.
Hmmm, same machine as Ed's? Just curious, are you guys discovering CONTROL on your own, or is that recommended by them?
Yes, I believe Ed and I have the same machine. Bob recommends UGS in all of their documentation. I'm on a Facebook group with a bunch of other Bob users and there are always posts about UGS screwing up. "Clear the cache"... over and over. A couple users recommended Control as an alternative and that's where I started. Control has been flawless (apart from this little issue) for me since the start.
Yes, I wish Bob would take a longer look at OpenBuilds, because I have found it to be infinitely more stable than UGS.
Well, cool, and welcome If nothing else, this all helped you find what we hope is an awesome community, and that you will spend many more happy years with us. (; and when you outgrow those machines someday, click thar Store link above (;
Also, I did a YouTube video and posted in the Bobs CNC group on FaceBook. It was both about switching to Raspberry Pi and OpenBuilds Control. I'm not much of a film star, but it did help some people. Here's the link:
