Framing command runs x-axis into limit switches

I’m having an issue with Lightburn 0.9.09 where asking the laser to frame a job sends the gantry off into the limit switches on the far side of the workspace.

I’ve checked G54 using $#, the result is all zeroes, so no workspace offset.
I’ve ensured I’m using absolute coordinates in the “Start From” selection
I home the machine before each use.
I even engaged $20=1 soft stops to see what happens… sure enough, it thinks I’m sending the laser into the abyss.

G-code output shows some G0 X349 Y99 commands on line 14 which should be a problem, but Lightburn thinks I’m having problems at line 3.

Any ideas what I’m doing funny?

Thanks!

G-Code output
; LightBurn 0.9.09
; GRBL device profile, current position
G00 G17 G40 G21 G54
G91
M4
; Cut @ 70 mm/sec, 80% power
M9
G0X0Y0
G1Y151S800F4200
G1X305
G1Y-151
G1X-305
G0X394Y99
G1Y1
G1Y-1
; Cut @ 60 mm/sec, 80% power
M9
G0X-113.5Y28
G1Y-103F3600
G1X-256
G1Y103
G1X256
M9
G1S0
M5
; return to starting pos
G0 X-280.5Y-127
M2

GRBL 1.1f settings
$$
$0=10
$1=255
$2=0
$3=1
$4=0
$5=0
$6=0
$10=0
$11=0.010
$12=0.002
$13=0
$20=1
$21=1
$22=1
$23=3
$24=100.000
$25=2000.000
$26=100
$27=5.000
$30=1000
$31=0
$32=1
$100=80.000
$101=80.000
$102=80.000
$110=12000.000
$111=12000.000
$112=12000.000
$120=100.000
$121=100.000
$122=100.000
$130=350.000
$131=250.000
$132=5000.000
ok

These two things disagree with each other - you said absolute, but the file says current. If you’re homed it likely won’t matter, but it’s an inconsistency at least.

Is there anything else in your file? What is selected if you press Ctrl+A (select all)?

What does the console output say?

I have a version of LightBurn posted that allows emitting all commands sent: https://drive.google.com/open?id=1OrvCr1ICB3d5CQpqFY2rCY5Z5RB-e2KU
Look on the console for the ‘Show All’ button - if you enable that, framing will show you which commands it’s sending, so that will provide clues.

Hi Oz,

Thanks for that all commands version of LightBurn. I love that! I really think that should be a full / “all the time” feature for the super nerdy amongst us! I’ve included the output from the console below when doing another frame command.

Before I get there though…I’m halfway embarrased to say I figured out my issue! Somehow I got a line element floating outside of my working area at …you guessed it… 394mm in X. That’d be why the laser keeps trying to frame that in! The piece was so far out there that I didn’t see it when the workspace was zoomed in. I wish LightBurn didn’t let me put geometry outside the work area.

The output below is what happens when the framing command is given. The G1 command being told to go to (394,0) from the origin (0,0). My bed is only 350mm long in X, and the soft stop alarm (ALARM:2) gets triggered before any motion happens. It’s going after that line element that I did not see.

LightBurn Console Output
Waiting for connection…
Grbl 1.1f [’$’ for help]
[MSG:’$H’|’$X’ to unlock]
[MSG:Caution: Unlocked]
ok
$H
ok
Starting stream
G00 G17 G40 G21 G54
G90
G0X0Y0
G1X394S0F6000
G1Y151
G1X0
G1Y0
G0
G90
ALARM:2
On or near line 3:
Stream completed in 0:00
[MSG:Reset to continue]

You’re the opposite of what I hear most of the time - Tons of people use that area to stage things, then drag them into the work area to cut them, and use the ‘Cut Selected’ option to keep it from blowing up. I’ve had it requested that anything outside the cutting area just be excluded, which I might try to do, but then anything straddling would be a gray area.

Ctrl+A then Ctrl+Shift+A is your friend: Select all, followed by Frame Selection. It’ll show you anything out of bounds quickly.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.