Lightburn Offset post UGS CNC projects

LightBurn Software Questions
1

I have a FoxAlien VastoXXL which I have been using for about 8 months as a dedicated CNC machine via UGS and Easel/VCarvePro. I have had 0 issues with positioning, Homing, Tramming, nor Macro settings.

I powered my Fox Alien Control box down, closed Easel/VCarvePro and UGS, swapped CNC Router and hardware out for my 40W Fox Alien Diode Laser and turned everything back on. I started up LightBurn software (1.4.03) Checked for updates which there aren’t any; and as expected once connected with my COM selection it homed in the bottom left corner of my workspace.

My issue is I cannot seem to get G92 X0 Y0 command to stick and before running $rst=* G54-G59 were all populated with my macro settings from UGS. (Not entirely sure how that information was carried over as they were never set in Lightburn).

Either Way I have managed to clear all G54-G59 coordinates to 0.000, 0.000, 0.000 with exception of [G92: -987.001, -987.001, -3.000]. After the homing sequence and running G92 X0 Y0 it still remains. I am using Absolute Coordinates and Job Origin as Center. I believe what I need is an offset as it appears it thinks it is in negative coordinates.

I can Home then using my Macro “Zero” [G92 X0 Y0] which does nothing as seen here:
<Idle|MPos:-987.001,-987.001,-3.000|Bf:15,127|FS:0,0>
and

Screenshot 2023-11-02 230337

This is currently my settings:
$$
$0=10
$1=25
$2=0
$3=0
$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=25.000
$25=500.000
$26=250
$27=3.000
$30=10000
$31=10
$32=0
$100=321.420
$101=321.860
$102=800.910
$110=1800.000
$111=1800.000
$112=600.000
$120=300.000
$121=300.000
$122=100.000
$130=990.000
$131=990.000
$132=88.000
ok

$#
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:-987.001,-987.001,-3.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok

?
<Idle|MPos:-987.001,-987.001,-3.000|Bf:15,127|FS:0,0>
ok

At this point, After I Home, I can move X, Y & Z axis, say to X: 450 Y: 450 but then I cannot move anywhere after the initial move:

Screenshot 2023-11-02 230932

I was successful at executing:
G10 L2 P1 X-999.998 Y-999.998

$#
[G54:-999.998,-999.998,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:-987.001,-987.001,-3.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok
BUT it does NOT stay, So I did G92 X0 Y0:

$#
[G54:-999.998,-999.998,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:12.997,12.997,-3.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok

?
<Idle|WPos:0.000,0.000,0.000|FS:0,0>
ok

I feel this is something simple, and I’m probably making this much more difficult than it is, but TBH I’m tired and was hoping I could get this up and running quickly. Now saying that I’m not great at GCode and could really use some guidance. I know this has been covered many time, as I’ve searched and tried. And Aside from running the homing sequence followed by: G10 L2 P1 X-999.998 Y-999.998 then: G92 X0 Y0, I can’t get the values to remain in memory. Is this a controller issue? Or did I miss something in Device/Machine or GCode settings.

2

Offsets are stored on the controller, not in software and so would persist when transitioning between applications.

Before getting into specific changes, can you articulate what you’re actually trying to achieve? You don’t state so explicitly.

It’s the very act of setting the G92 that’s creating the G92 offset.

Try issuing G92.1. That should remove any G92 offset.

Did you change $10=0 after getting this status? If so, curious why the machine is reporting MPos. I would have expected WPos reporting here.

3

Offsets are stored on the controller, not in software and so would persist when transitioning between applications.

^^^ That makes sense. So will I have to save presets when I switch between my laser and CNC so to overwrite any macros that may be carried over to be overwritten with the correct information.

Before getting into specific changes, can you articulate what you’re actually trying to achieve? You don’t state so explicitly.

^^^ Yes, I could have been more clear. Specifically i’m was trying to change my negative coordinates to positive coordinates. That was the first issue. The command of G92 etc etc as seen below was indeed what I ran, and though that works, If I power cycle LightBurn, or my laser and controller, there is no retention of the positive coordinates nor the workspace settings. That was actually the second issue and still persistent.

It’s the very act of setting the G92 that’s creating the G92 offset.

Try issuing G92.1. That should remove any G92 offset.

^^^ G92.1 does work for clearing the offsets as opposed to blowing everything away with the $rst=*

Did you change $10=0 after getting this status? If so, curious why the machine is reporting MPos. I would have expected WPos reporting here.
[/quote]

^^^ I did change $10=0 after that status, it was originally set to $10=3; again not sure why.

I have been able to get positive coordinates, Zero XY with G92 X0 Y0, set an Origin utilizing User Origin for a material test to ensure I can navigate the workspace, and the laser is actually correctly. (that was a whole other issue - figured that one out though).

4

I’d suggest using a G10 offset rather than G92. That will persist between uses.

To what corner does your machine home? Can you confirm that your machine is 990x990 mm?

Can you run these commands in Console and return output:

G92.1
$H
$#
?
5

I was successful at executing: G10 L2 P1 X-999.998 Y-999.998

My machine homes to the bottom or (front) left corner.

I can confirm that my machine cutting or working area is 39.37 inches or 999.998mm by 39.37 inches or 999.998mm. Now I do use soft stops when I am using my CNC Router, but not for laser, as the projects I do with the laser are much smaller.

Here are the commands you requested:
G92.1
ok
$H
ok
$#
[G54:-999.998,-999.998,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok
?
<Idle|WPos:12.997,12.997,-3.000|FS:0,0|WCO:-999.998,-999.998,0.000>
ok

Under Move Clicked “Get Position” after the requested commands:
<Idle|WPos:12.997,12.997,-3.000|FS:0,0|Ov:100,100,100>
ok

6

Can I assume that you want position after homing to be 0,0?

If so, you may want to run this:

G10 L2 P1 X-987.001Y-987.001

Can you rerun this to confirm:

$H
?
7

yes I would like to have position after homing to be 0,0.

G10 L2 P1 X-987.001 Y-987.001
ok
$H
ok
?
<Idle|WPos:-0.000,0.000,-3.000|FS:0,0|WCO:-987.001,-987.001,0.000>
ok
Get Position after Homing:
<Idle|WPos:-0.000,0.000,-3.000|FS:0,0>
ok

8

Looks like you’re in business.

The G10 offset will persist but sounds like you don’t want them in CNC mode. I’d suggest setting up Macros in LightBurn with the G10 command. You can set another command to remove all offsets with:

$RST=#
9

Yes I does appear that everything is working!!

I’m going to save all of the configurations and settings and build out my macros (tomorrow). But that’ll help when switching between CNC to laser.

And worst case the power cycling and it deletes everything I can just reload config files and get up and running agin.

So will $rst=# will just delete everything or reset to factory I set as opposed to erasing and zeroing G54-G59 and offsets from EEPROM?

Thank you very much!! I really appreciate your time and guidance.

10

It will effectively zero-out all offsets but without affecting $$ settings.

Glad I was able to help.

11

Excellent, I pulled up the GRBL setting pocket guide; printing that sucker out in the morning.

Thanks again!

12

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