Since updating to the latest version of the OpenBuilds Control software, everything has gone crazy. Special characters (like smilie faces and other random stuff) showed up in my GRBL settings. I took a backup of the settings previously - how do I restore this text file?
Unlikely to be update related, but do post a screenshot? Click Refresh Grbl settings at the top of the Grbl Settings window to refresh it. (sounds more like EMI related serial corruption) How do restore grbl settings? Paste them in gcode editor, click Play NB must be in Grbl config format gnea/grbl ie Code: $xxx=xxx $xxx=xxx $xxx=xxx $xxx=xxx [code] Also note Grbl eeprom can get corrupted, refer to the use of the $RST command: gnea/grbl
Thanks mate, I had a horrible day with jobs failing due and a number of errors popping up in OpenBuilds. Not sure if my Blackbox is having issues or software related. Have some video of the alarm fake triggering on and off, random commands being executed and stop errors with missing or unexpected values. I manually entered the values from the text file but running it as a job will be way after next time. Let me know if the screenshots and video would help in any way. Otherwise I will just wait until it happens again and see what is going down.
Is your USB cable clear of all power/motor/router cables? And limits cabling routed away from any power/motor/router cables? Are you using Xtension Limit Switch Kit switches?
No limit switches installed yet. Just want to be cutting, so I need to get my butt in gear and sort them. I just have very simple switches I am going to put on there. The USB cable may be close to some of the power and stuff but I don't think close enough to cause interference. I can't say for sure but I will for sure have a check on this. Thanks mate!
So if you don't have limits, then which alarm is triggering on you? (usually thats the complaint for EMI triggering limits falsely: "Alarm: Hard limit triggered. Machine position is likely lost due to sudden and immediate halt. Re-homing is highly recommended." Get the Xtensions if you can, built in EMI filtering, easier to wire, easier to mount Your symptoms beg to differ (;
Still big troubles today. OpenBuilds is taking commands but not doing anything. Also giving me errors if I try to move and nothing is running. Did the job buttons always send $J=G91 commands before? I though it was just sending the X and Y and the feed speed.
Photos are just as I went through. The settings have restored ok but still the issues of the machine not moving.
Loaded a Workbee profile, ran the $1=10 and the rest from the backup. Machine is engaging again. Still getting errors saying that a command was issued while GRBL was running. This is all going crazy for something that was working so well.
Only since Dec 2016 (; - see gnea/grbl $J is the Grbl 1.1 Jog Command And did you remember to set $4=1 again? (or load one of our profiles which has that set for you?) So, lets entertain this thought for a second: Checkout Github Release Stats - based on the fact that at the time of writing, 1.0.237 has been installed on 571 Windows PCs, 30 Macs and 20 Linux PCs I am sure someone else would have started reporting the same issues by now if it was that... (1.0.234 had about 4231+308+240 installs, as its from April and the latest version is still rolling out) But do try an older version: OpenBuilds/OpenBuilds-CONTROL always available here
My apologies, I didn’t mean to imply that the upgrade was the only possible thing - just that it was around the same time and it was a factor that was playing on my mind. Out of all the possibilities such as interference, windows bugs and just about anything else to do with CNC and PCs working together it is not likely a code upgrade in a minor release of the software. I will go back over everything tomorrow morning when I am in front of the machine. Thanks for your help mate. I really do appreciate it.
No apology neccesary, I am really giving you the idea to downgrade as a legit test. It would be odd if it affected only you (around here, if the code really breaks we tend to hear about it all too soon from many screaming fans hehe) , so I'm all ears, and if a older version still does the same, we both feel comfortable that another cause is ticked off the list
