I have the new Blackbox installed and it all appears to be working well. Moved back to using the Control Software's actual window instead of the web interface through chrome as it loaded some of the complex jobs cleaner. My problem is that seemingly after a random (which I know it can't actually be random) number of jobs. When I open the same file that didn't give me any warnings before I get a warning that the opened GCode has a G53 command and that the machine should be homed. After homing I have never had a problem on the next job loaded. But opening the same job say 4 jobs down the track might give me the same warning. Does it sound like the Blackbox is losing home? I can confirm that it hasn't hit and limit switches or anything inbetween. I only have hard limits switched on. My boss has just been ignoring it and the jobs still run perfectly. I will always home and reopen the job if it happens when I am using the machine. Any help would be greatly appreciated. I feel a bit lost on this one as it has only every come up since we installed the new Blackbox. I have never seen this warning before.
Its a new safety feature - people forget to Home (or forget to Rehome after resets, restarting CONTROL, after alarms, after errors etc) all the time leading to tens of "my z moved weird" or "my machine crashed" type of support questions... So we now just remind them to home now. See Check if machine is homed and if any G53 moves are in the GCODE, Ask to Home · Issue #219 · OpenBuilds/OpenBuilds-CONTROL Also see https://raw.githubusercontent.com/OpenBuilds/OpenBuilds-CONTROL/master/CHANGELOG.txt
It’s happening sometimes when I don’t expect to have lost the home though. Run a job without a warning. No errors in the job and not hitting the limits. Open the next job and get the warning.
I am suspect the Blackbox(es) I have always been has been losing home without any reason then. It’s only now that there is a warning it is showing up. The jobs and the return to G53 points after running seem to be working fine. Like it knows where home is.
Note it says "TIP" not "Definate major disaster" - if you are sure its homed, ignore - click close and move on
it is a reminder that homing is necessary, not an "instruction to home now because we detected a fault".
My only concern is that it thinks it’s not homes right after homing. Sometimes I home, then open a job and the tip comes straight back up. I can live with just ignoring it because realistically it’s probably been the same the whole time.
It resets to "not homed" any time Grbl "initialises" - by sending the "Grbl 1.1xxxx" string (Can be seen in serial log) If you really want to dig in, see the Serial log - and it should show the history of where that string was sent It's usually sent after clearing an alarm or error, after first connection, after clicking the Reset buttons (software or on the BlackBox), after a short circuit induced brownout reset, or if you manually send init commands, or after clicking Stop/Abort Doesn't mean it "lost home" but it "could have" - so we rather warn.... Grbl doesn't specifically tell us when its homed or not - so we have to make some assumptions based on events
I think I will invest in a UPS to regulate the power a bit before diving that deep. Metal workshop so welding is a thing and I would like to rule any power fluctuations out. Is there any way to prevent the pop up with a macro? More curious as to the reach of macros system. I love it so much. I feel like it’s my own personalise Blackbox without having to modify the stable core of the Blackbox.
You are over obsessing over this.... It's not power, its just "A helpful tip" But sure, disable it for yourself: Create an JS macro, turn on "Run Macro on Startup" and enter this code Code: window.jobNeedsHoming = function() { console.log("Disable the Popup for Sean, but here we would have popped up") } That replaces our jobNeedsHoming function with a dummy function that doesn't create the popup at all, just logs and exits And then never come asking us why you machine did weird Z moves or crashed and broke a bit because you forgot to Home (;
I hear you and appreciate the tip pop up a bit more. Very admirable focusing on safety. Thank you for helping and for the giggle with adding “for Sean” in the code. I need to find a way to help promote OpenBuilds or make myself rich so I can donate to your projects. I actually feel bad for others dealing with complex systems trying to solve problems your team already fixed many moons ago.
Well if theres a confirmed bug let's investigate Grbl init string sets status...recentlyHomed=false $h sets status...recentlyHomed=true Everytime you open it file, it checks if it contains G53, and if recentlyHomed is false, pops up the warning. If recentlyHomed is true, it should not popup.
Ahhh yes. That might be it, I'll know for sure when I get out to my machine. On my desktop I only have an arduino with nothing connected so no homing. Maybe add a bit more logic to set recentlyHomed to true after the first popup? Then, of course, reset to false after any grbl reset, etc? EDIT: It works as designed at the moment. Sorry for the false alarm.
Ok fair enough - it was right, you didn't home then lol I guess a little "don't bother me again tick" may be good for the non-newbies - will consider
