Where to start troubleshooting Major jog issues?

Lightburn worked amazingly well my first couple days using it, I had absolutely no issues and ran my first test minutes after setting up my machines and then all of a sudden after a couple days NOT changing anything at all in my settings I had an issue with both y axes jog buttons going the same way periodically that some how stopped but now I’m having all kinds of issues / problems jogging I have a millright mega v xl with Jtech photonics 24 watt quad pro my work space is 900mm by 900 mm but i have homing switches so in GRBL and light burn i have it set to 855mm x 855mm now in lightburn only the X axes will jog to the halfway point by itself and not come back to the homing switch unless i home the Y axes is opposite it will jog ONLY to the halfway point and WILL jog back… I Home to the back left but was told to still set my origin to front left thats how its been set from day one so i didnt think that would be the issue since i didnt have these problems on day one i tried to change origin to where my homing switches actually are but that did nothing again this is only happening in light burn i can download the gcode from lightburn and run in UGS with no problems… Periodically jogging will stop completely with no errors and not move untill i home this has been ongoing for 3 days now please any help at all will be greatly appreciated or even suggestions on where to start troubleshooting below are my settings and images showing where the x and y axes will move to

my GRBL SETTINGS:
ok

$$
$0 = 10 (Step pulse time, microseconds)
$1 = 0 (Step idle delay, milliseconds)
$2 = 0 (Step pulse invert, mask)
$3 = 2 (Step direction invert, mask)
$4 = 0 (Invert step enable pin, boolean)
$5 = 0 (Invert limit pins, boolean)
$6 = 0 (Invert probe pin, boolean)
$10 = 0 (Status report options, mask)
$11 = 0.010 (Junction deviation, millimeters)
$12 = 0.002 (Arc tolerance, millimeters)
$13 = 0 (Report in inches, boolean)
$20 = 1 (Soft limits enable, boolean)
$21 = 1 (Hard limits enable, boolean)
$22 = 1 (Homing cycle enable, boolean)
$23 = 1 (Homing direction invert, mask)
$24 = 50.000 (Homing locate feed rate, mm/min)
$25 = 800.000 (Homing search seek rate, mm/min)
$26 = 200 (Homing switch debounce delay, milliseconds)
$27 = 5.000 (Homing switch pull-off distance, millimeters)
$30 = 100 (Maximum spindle speed, RPM)
$31 = 0 (Minimum spindle speed, RPM)
$32 = 1 (Laser-mode enable, boolean)
$100 = 57.288 (X-axis travel resolution, step/mm)
$101 = 57.288 (Y-axis travel resolution, step/mm)
$102 = 200.000 (Z-axis travel resolution, step/mm)
$110 = 16510.000 (X-axis maximum rate, mm/min)
$111 = 16510.000 (Y-axis maximum rate, mm/min)
$112 = 4570.000 (Z-axis maximum rate, mm/min)
$120 = 200.000 (X-axis acceleration, mm/sec^2)
$121 = 200.000 (Y-axis acceleration, mm/sec^2)
$122 = 700.000 (Z-axis acceleration, mm/sec^2)
$130 = 855.000 (X-axis maximum travel, millimeters)
$131 = 855.000 (Y-axis maximum travel, millimeters)
$132 = 145.000 (Z-axis maximum travel, millimeters)
ok


This sounds like a homing issue… Does it home properly?

:smile_cat:

yes will home every time no issues

I think @berainlb would be better at this… it sounds like it’s thinks it’s near an edge and won’t move it any further… I’m not a gcode wizard like some of these people…

Give him a spell to get notified and see if he’s better at sorting out your issue.

:smile_cat: +

1 Like

thanks for the input and Mr @berainlb any input? lol thanks in advance!

Some of the behavior I can’t quite reconcile but let’s gather some more data.

  1. Do you use this machine for CNC operation as well? If so, it’s possible that your CNC operations are manipulating work offsets that are making the function of the controller impossible in LightBurn. LightBurn relies on a positive coordinate system to work correctly.
  2. Can you run these commands in Console and return output?
$H
$I
$#
?

Note that the first command will home the machine so be prepared for it.

1 Like

YES I do use for cnc as well

[VER:1.1h MegaV 3axisv1.20190825:CUSTOM]

[OPT:VL,15,128]

Target buffer size found

ok

$H

$I

$#

?

<Home|WPos:-419.599,362.118,10.955|FS:0,0|WCO:-430.404,-367.110,-15.955>

ok

[VER:1.1h MegaV 3axisv1.20190825:CUSTOM]

[OPT:VL,15,128]

Target buffer size found

ok

[G54:-430.404,-367.110,-15.955]

[G55:-788.909,-620.147,-63.950]

[G56:-808.896,-62.212,-12.750]

[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]

[G54:-430.404,-367.110,-15.955]

LightBurn works in the G54 offset so this is likely causing your issue.

Your reported working position is slightly odd though so a few more clarification questions:

  1. To what corner does your machine home?
  2. Can you confirm that reported work position increments as you move up and right? If not, what does it do?
1 Like

On a side note, I noticed that the $30 and S-Value Max are set to 100. Should they both be 1000, or does it not matter as long as they are both the same?

1 Like

The critical bit is that they be the same. 100 is unusual but not unheard of when shared with CNC operation.

1 Like

Sorry for the delay and I home to the back left and I think you are on to something with g54 when I first started running batches about a year ago I set my g54. 55 and 56 to certain locations to be able to just throw a part down and start milling what is lightburn looking for g54 to be? And when I increment is there a way to get the controller state / location without typing the command in the console?

In Move window push “Get position” to determine current position.

1 Like

Hmm It does nothing stays at zero you say my g54 is odd what is lightburn looking for when you say it works off of g54 as in g54 should be set to where my homing switches are ?

There’s nothing specific is looking for in G54 specifically. However, LightBurn is expecting to work in a positive coordinate system, meaning that all coordinates on X and Y are positive.

Let’s assume for the moment that your machine does increment moving up and to the right. And since your machine homes top-left I assume we want that position to read as 0,855.

In that case, can you do the following:

  1. run in Console and return output:
$H
G10 L20 P1 X0 Y855
$#
?
  1. Test jogging controls and report back on behavior

you are the man that worked… its jogging the entire work area and will come back without homing THANK YOU!!! ALSO the get position button is working as well thanks again.

@berainlb sorry to bug you again but do you have any idea why this would suddenly start happening again? I didnt do anything different from when it was working fine. I was cutting out a coaster holder and it just stopped when i tried to jog after homing it started stopping in a different position this time

Rerun these commands in Console and make sure nothing has changed:

$H
$#
?

YES it has changed for some reason
$H

$#

?

<Home|WPos:-58.407,493.629,37.743|FS:0,0|WCO:-791.597,-498.621,-42.743>

ok

[G54:-791.597,-498.621,-42.743]

[G55:-788.909,-620.147,-63.950]

[G56:-808.896,-62.212,-12.750]

[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]

Do you use other programs with your machine? That could be causing the changes.

Run these commands and return the output:

$H
G10 L20 P1 X0 Y855
$#
?

the only thing i have used is Universal G code Sender (UGS) and lightburn but it worked fine afterwards for several weeks then this issue started like 2 nights ago
$H

G10 L20 P1 X0 Y855

$#

?

<Home|WPos:-58.407,493.629,37.743|FS:0,0>

ok

ok

[G54:-850.004,-859.992,-42.743]

[G55:-788.909,-620.147,-63.950]

[G56:-808.896,-62.212,-12.750]

[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]