Good afternoon. See attached screen shot. The gray wireframe box. I assume it represents the machine’s work area? It is dislocated from my job toolpath outline. Is that a problem? I turned everything off and back on. Re-homed all axes. Zeroed X/Y at front left of workpiece, Z at the table surface. Thx, rink.
It does show the Machine Coordinates But in your screenshot, either you didn't home, or homing isn't setup up correctly ($23 Homing Dir, Max Travel, etc), or you didn't Home first, then SetZero, or SetZero incorrectly.
Thanks, Peter. I did home. Attached screenshot of my GRBL $23. I homed first (as I always do upon startup), then zeroed. I set zero correctly at the front left corner of the workpiece, using the OB probe. The job ran correctly, as all my jobs have so far. Homing works correctly, at the back right corner of the machine. Jogging is all in the correct directions. Zero probing works correctly. What else can I check?
According to $23 all your switches are at Axis Maximas - is that where they are on the machine? Full Grbl Setting backup would be easier to review (Backup Settings button on CONTROL > Grbl Settings tab) along with pictures of your machine
Yes, the switches are at top, back, right. I'm attaching pics and GRBL backup, and photos of the machine in home position.
but Kicked off with a LEAD1515 profile but lowered the Max Travel values? 1515s Max Travels should be: (Hard to confirm if its a 1515 or not from the pics?)
Yes, sir. It's a LEAD 1515 which you guys shortened for me. Y-axis 1000 instead of 1500. Those max's are what I determined from jogging the machine, and then subtracting the 5mm that the homing cycle backs off.
OK, then Homing and Max Travel should be correct. After homing, GOTO Machine Zero (G53 G0 X-5 Y-5 Z-5) - you should be just shy of the top right corner of the gray cube?
No sir. The pointer is in the lower left quadrant of the gray cube. See pic. If I ignore the gray cube, the pointer is about where it should be in relation to the work coord zero. And jobs run ok. So, it seems the gray cube is simply mislocated in the simulation window. And between the last couple replies, I've turned it off an back on, so whatever is happening is persistent.
BTW...I know it's late in SA. And this is not urgent. Feel free to defer this until your convenience.
Not where it should be so its weird Frequently Asked Questions No worries, I work US hours 15:00 to 00:00 local time still got about an hour in the office and your case is curious
Well, since your'e curious...OB Control is also doing something else unexpected... When I click Pause to pause a job during running, it pauses, just as it should. When I click Resume, it resumes, just as it should...but only for a couple secs. About two secs after resuming, it spontaneously pauses again, the button changes to "Resume", and I have to click that Resume again. Then it continues on normally. Not just a time or two, but every time. I've learned to work with it and I figured it was probably known and would be fixed in some future update, so I haven't said anything. Do you think it would it help to re-download OB Control and reinstall?
I don't think a reinstall would help. But pausing can sometimes be a bit unstable - some old bug we've been chasing for a couple years. So less of a surprise than the offset on Machine Coordinates
Good afternoon. Still happening. See attached. Not causing me any problems, just keeping you informed. Thx, rink.
Post a fresh Grbl Settings Backup please If I load your last backup from the other day onto an X32 - Home it - Run It ends up right where it should See, Blue current position indicator cone, just shy of top-right corner of gray cube. If I do G53 G0 X-1190 Y-795 Z-95 I am at front left bottom corner as I should be (Those are your Max Travel values) If I then SetZeroXYZ, the grid comes and joines me there too So lets see if you had different settings on the controller, than the backup you have us before
Hey Peter, thanks. I haven’t changed any settings (that I’m aware of) but I’ll make another backup and send it as soon as I can.
Hey Peter, sorry for my long delay. Here's a screenshot from today, along with a grbl backup from today. I connected the BB to my laptop, opened OB Control, and homed all axes. Then I loaded this g-code file, snapped the screenshot and generated the grbl backup. Thx, rink.
Good day. I’m back in the workshop after several months’ absence. Simulation still doing the same thing, see attached screenshot. It displays the job as way off the table. I haven’t changed anything since last time (actually haven’t used the machine at all since my last post). Is there any firmware update or other developments on this issue? Reminder, I’m using a 2022 MacBook with M1 processor and the latest OS. thx, rink.
Just making sure we have the latest to see what you have... Will check and get back to you, no other changes in this time, still all switches at axis maximas ($23=0 ; Homing direction invert, mask)? And $130=1190.000 ; X-axis maximum travel, millimeters $131=795.000 ; Y-axis maximum travel, millimeters $132=95.000 ; Z-axis maximum travel, millimeters Correct for your machine?
I understand. But everything is still the same. I haven’t touched the machine since last time I posted about this. I haven’t changed any settings. I haven’t reconfigured any hardware. I’ve been out of the loop for a while and I was just checking to see if you guys had made any changes or implemented any updates/fixes that would have addressed this. It’s not a critical problem, just annoying.
Still doesn't seem like us (no other complaints in all this time) So for the sake of trying to replicate, lets get latest Grbl Settings backup, gcode for review, output of a Serial Terminal > "$#"-command, and a screenshot of 3D view at exact time you take $# output (lets see if theres an issue in your offset positions recognisable from distances on 3D view) Lastly, you are on Apr 2024 version of Grblhal right (as included in CONTROLs flashing tool)
Don’t know. Got the machine in Nov 2023. Last used it about mid-2024. What do I do to find the version?
Here's the output of the Terminal > $# command. The GRBL backup, gcode and screenshot are attached. [09:22:43] [ $# ] [G54:-1078.134,-520.938,-54.516] [09:22:43] [ $# ] [G55:0.000,0.000,0.000] [09:22:43] [ $# ] [G56:0.000,0.000,0.000] [09:22:43] [ $# ] [G57:0.000,0.000,0.000] [09:22:43] [ $# ] [G58:0.000,0.000,0.000] [09:22:43] [ $# ] [G59:0.000,0.000,0.000] [09:22:43] [ $# ] [G59.1:0.000,0.000,0.000] [09:22:43] [ $# ] [G59.2:0.000,0.000,0.000] [09:22:43] [ $# ] [G59.3:0.000,0.000,0.000] [09:22:43] [ $# ] [G28:-601.502,-402.495,-7.147] [09:22:43] [ $# ] [G30:-1199.998,-799.996,-4.995] [09:22:43] [ $# ] [G92:0.000,0.000,-18.200] [09:22:43] [ $# ] [HOME:0.000,0.000,0.000:0] [09:22:43] [ $# ] [TLO:0.000,0.000,0.000] [09:22:43] [ [ PROBE ] ] Probe move ERROR - probe did not make contact within specified distance [09:22:43] [ $# ] [PRB:0.000,0.000,0.000:0] [09:22:43] [ $# ] ok
So this morning's experience was same as yesterday. But 2nd job this morning...unexpectedly...everything looks ok. See attached screenshot, GRBL backup, and code file.
Right so first off I installed your Grbl Settings backup. Then I loaded the gcode. Machine is not yet homed - no jogging or setzero yet etc - as expected, the work zero outside the machine bounds (because work coordinates are always negative quadrant, and your work coordinates (and most usually) are all positive quadrant and we haven't set the Work coordinates yet. Next I homed, then moved to the positions you applied your Setzero (Per your $# your offsets where [09:22:43] [ $# ] [G54:-1078.134,-520.938,-54.516]) So I sent a G53 G0 X-1078.134 Y-520.938 Z-54.516 to reach that same locations, and then I clicked Set Zero there Perfect. So GCODE and Grbl Settings check out. Must be something in your homing/setzeroing workflow that you might be doing differently? ___________________________ Sidenote, you are on CONTROL v1.0.370 in that earlier screenshot. You should be on V1.0.382 by now - no relevant changes off the top of my head, but overall good to be up to date. Review what you missed OpenBuilds-CONTROL/CHANGELOG.txt at master · OpenBuilds/OpenBuilds-CONTROL so please do update if possible V1.0.370 dates back to 7 Jun 2023 (last year), quite outdated Release v1.0.370 · OpenBuilds/OpenBuilds-CONTROL
Peter, good morning. Thanks for checking that out. I will update the CONTROL app to the latest. As for workflow, it’s always the same order: Turn on laptop, let it boot up. Plug BB into laptop. Turn on power supply. Turn on BB. Home All. Move to somewhere and set zero. So, I dunno. Did all of that yesterday, same as always. Anyway, I guess I’ll just not worry too much about it. But I hate it when I can’t solve a mystery. At least it’s not a critical work-stopping problem. Thx again, rink.
Same - on the surface nothing is wrong, so i am stumped too. But lets see maybe the new version does help
