I’m running grbl, with dual end stops, worked fine for 6 months now If I move my laser to a start position of x=100, y=100 everything works as it should. But if I create a saved location from that position, x1,y1 go to 100, x2 goes to 80 and y2 doesn’t move. Weird! Anyone have an idea?
It’s possible you have an offset configured that’s throwing things off. Have you recently used laserGRBL or a different program other than LightBurn?
A few questions:
- Do you use a homing cycle?
- If yes to homing, to what corner do you home?
- What corner have you configured your origin to in Device Settings?
Run these commands in Console after a homing cycle (or your standard startup process) and post here:
$I
$$
$#
?
- Do you use a homing cycle? YES
- If yes to homing, to what corner do you home? Lower Left
- What corner have you configured your origin to in Device Settings? Lower Left
Waiting for connection…
[VER:1.1k.20190514:]
[AXS:5:XYZXY]
[OPT:VNM,35,255,18]
Target buffer size found
ok
Homing
ok
$I
[VER:1.1k.20190514:]
[AXS:5:XYZXY]
[OPT:VNM,35,255,18]
Target buffer size found
ok
$$
$0=10
$1=255
$2=0
$3=21
$4=0
$5=0
$6=0
$10=0
$11=0.020
$12=0.002
$13=0
$20=0
$21=0
$22=1
$23=27
$24=500.000
$25=2000.000
$26=250
$27=3.000
$30=1000
$31=0
$32=1
$100=100.000
$101=100.000
$102=400.000
$103=100.000
$104=100.000
$110=7200.000
$111=7200.000
$112=400.000
$113=7200.000
$114=7200.000
$120=400.000
$121=400.000
$122=200.000
$123=400.000
$124=400.000
$130=515.000
$131=365.000
$132=120.000
$133=515.000
$134=365.000
$140=135.000
$141=135.000
$142=135.000
$143=135.000
$144=135.000
$150=0.000
$151=0.000
$152=0.000
$153=0.000
$154=0.000
ok
$#
[G54:-505.000,-391.000,-8.000,-522.000,-364.000]
[G55:0.000,0.000,0.000,0.000,0.000]
[G56:0.000,0.000,0.000,0.000,0.000]
[G57:0.000,0.000,0.000,0.000,0.000]
[G58:0.000,0.000,0.000,0.000,0.000]
[G59:0.000,0.000,0.000,0.000,0.000]
[G28:0.000,0.000,0.000,0.000,0.000]
[G30:0.000,0.000,0.000,0.000,0.000]
[G92:0.000,0.000,0.000,0.000,0.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000,0.000,0.000:0]
ok
?
<Idle|WPos:-7.000,29.000,8.000,10.000,2.000|FS:0,0|Pn:H|WCO:-505.000,-391.000,-8.000,-522.000,-364.000>
ok
Thank-you!
So your output is kind of interesting. You’re working in a negative coordinate system. This might be the reason for your odd behavior but not certain.
Let me ask more questions to make sure I have my bearings:
1.You’re showing GRBL version 1.1k. I believe the latest official version is 1.1h. Where did you get this?
2. Is there a reason why you have a 5-axis setup configured?
3. You have an offset configured current at G54. Is this deliberate? It has you working in a negative coordinate system that LightBurn won’t like. Have you recently connected to the laser with another program?
4. Even after homing, your machine coordinates are not 0,0. Not sure why that would be. Any insight here?
-
I have a Rambo 1.4 board that I’m running a custom version of grbl on, which I downloaded from GitHub.
-
See above, I’m unsure, but could it be because I’m running 5 individual steppers x1,x2,y1,y2, z
-
Sorry not sure what g54 is.
-
Also no
I bought a 3 axis grbl board, that I have on hand I’m beginning to think I should just trash my Rambo with its adhoc firmware and switch over.
I appreciate your help
Thanks
Is this the github site:
GitHub - johnboiles/grbl-Mega-5X: 5/6 Axis version of Grbl, the open source, embedded, high performance g-code-parser and CNC milling controller written in optimized C that will run on an Arduino Mega2560
Ah… that makes sense. Is this a dedicated laser machine or do you also perform routing operations on the CNC?
Also, I realized I was misreading the output from ?. You’re not working in a negative coordinate system. The offset is there to have the origin start at 0,0 in the front left. But for some reason it’s not properly zeroed out. What’s odd is that the numbers don’t seem to follow a rhyme or reason.
Try this. I’m not super familiar with your setup but let’s see if behavior at least changes. This should get your origin after homing to be 0,0:
G10 L2 P1 X-498 Y-420 Z-8 X-532 Y-366
If for some reason that end in catastrophe use this to get back to current:
G10 L2 P1 X-505 Y-391 Z-8 X-522 Y-364
Try rehoming after the change and see if things behave any differently.
Yes, that’s the one I’m using.
Laser dedicated at the moment.
Thank you I will try those.
Mike
I’ve been reviewing some Mega 5X documentation. It seems the 4th and 5th axes may be referred to as A and B… in that case the syntax for those commands may have to be:
G10 L2 P1 X-498 Y-420 Z-8 A-532 B-366
G10 L2 P1 X-505 Y-391 Z-8 A-522 B-364
See which one works. You can check by running ? and look for WCO or $# and look for G52.
Thanks, no luck though I tried both sets of code
G10 L2 P1 X-498 Y-420 Z-8 X-532 Y-366
This one gives me A G-code word was repeated in the block.
and both of these:
G10 L2 P1 X-498 Y-420 Z-8 A-532 B-366
G10 L2 P1 X-505 Y-391 Z-8 A-522 B-364
report
Unsupported or invalid g-code command found in block.
I’m not familiar enough to try to troubleshoot that but I do see that my 0,0 is actually -7,29 for some reason
Yeah. Wasn’t sure if the syntax would take. I’m not familiar with that custom grbl build and the 5-axis situation you’ve got going. I assume the 4th and 5th axes are setup in a slave configuration to X and Y.
A preliminary search didn’t pull up anything obvious about how this is configured.
Did you take a purely stock install? Or did you customize and/or configure in some way?
I don’t recall, but i just flashed the controller with the firmware from GitHub , seemed to be working okay at first but after maybe 20 minutes the laser stopped moving with the beam still on so I shut it down. Light burn didn’t give me an error message. I haven’t seen that behavior before but seems like a good way to start a fire.
That usually indicates a communication break or possibly the controller not getting enough power and crashing.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.