Can't move more than 31mm without getting Alarm 3 Reset while in motion error

Just starting out with a Foxalien laser and Masuter Pro and for the life of me can’t get it to move more than 31mm in any direction without it tripping an Alarm 3 Reset while in motion error. The only thing that doesn’t trip this error is homing it. I can home it from anywhere on the bed and it’s not an issue. If I manually try and move it in the Move tab everything is good until it tries to move more than 31mm. I can’t even Frame or Run any jobs without this error. I’ve been at it for a few days and can’t figure it out. Just today I realized it was a common distance that trips the alarm. If I slow down the travel speed it will only move 16mm before tripping the alarm. I’ve used this setup in LaserGRBL without any issues. I would really like to make the move over to Lightburn.

Thanks
Derrick

Can you provide these screenshots:

  1. Edit->Device Settings
  2. Full LightBurn with Move window in view

I don’t see anything particularly odd in your setup.

Can you run these commands in Console and return the full output? What happens when you run this?

$H
G0 X50Y50

First command homed the laser the second command moved 31mm and Alarm 3


Moved 31mm in what direction? Is motion smooth?

When you jog the laser, does it move smoothly in all directions?

I didn’t realize you had a work offset configured.

Can you run these commands in Console and return output?

$H
$$
$#
?

It moves smoothly in all directions. It took me a few days to realize it’s a set distance that seems to cause this issue. As you can see from my X and Y position Running your command it started at 0 and it went 31mm in both directions and tripped the alarm. It doesn’t matter where the laser is on the bed if it tries to move more than 31mm it trips the alarm. The only odd thing is I can home the laser from anywhere on the bed and it doesn’t trip the alarm no matter how far it’s got to move. It’s so bizarre. If I manually set the jog distance to 30mm I can jog it in any direction all over the bed without getting the alarm. If I bump it up to say 50mm it will move 31.??mm in either direction and trip the alarm. I will run those commands and report back when I get home.

You say you’ve used the machine with LaserGRBL without issue. Have you tested it since you discovered the issue?

Yes. I’ve run a few jobs in LaserGBRL with no issue after this.

In addition to the earlier commands, do you see any messages prior to the error:9?

Can you take a simple design that triggers the issue, then go to File->Save gcode, save with .txt extension, and upload that here?

Sure. I’ll get you everything you requested when I get home. There’s nothing out of the ordinary before the alarm. I’ve gone as far as installing Lightburn on another PC, swapped power supplies for the laser and controller, tried different outlets and separating everything. I’ve unplugged unnecessary components etc.

If I pull my design right down on my lasers position and hit play it will actually start burning but as soon as it moves more than 31mm it errors. I tried doing a simple 50mmx50mm square and even my 2 letter initials and of wouldn’t complete either of them

In all honestly I’ve had this machine for a few months and have tried a bunch of different programs as a CNC router and never had any issues with software or errors. Lightburn has been the only one giving me a headache and it’s the one that I’m really wanting to use.

Seems like this is a coordinate issue. Especially if you’re switching from routing software.

I’m pretty confident it’s just a setting I’m overlooking.

Another interesting thing I had happen was the first time I installed Lightburn it wouldn’t find my laser. I entered it manually and was advised to setup an offset for positive coordinates. That didn’t help so I reset Lightburn back to default settings trying to figure out this issue then I uninstalled and reinstalled it and it was able to find my laser this time and no need to setup the offset this time it was already showing positive coordinates.

1 Like

I use both and still struggle with a smooth transition from one to the other.

Interesting. I haven’t gone back to routing yet but I went from routing using Candle to running the laser with LaserGRBL with no issues what so ever. It was basically plug and play with LaserGRBL.

How do you generate your router Gcode?

So far I’ve used Carbide Create Version 6 and Easel Pro. I tried Fusion 360 but found it was a bit much for the simple things I was designing.

I use Lightburn to create project, go to carbide create to do the gcode and then open builds for control. I was hoping developers were going to make a cnc plugin for Lightburn like Vetrics.

As requested.

$H

ok

Grbl 1.1h [‘$’ for help]

Grbl 1.1h [‘$’ for help]

Grbl 1.1h [‘$’ for help]

Grbl 1.1h [‘$’ for help]

Grbl 1.1h [‘$’ for help]

Grbl 1.1h [‘$’ for help]

Grbl 1.1h [‘$’ for help]

Grbl 1.1h [‘$’ for help]

$$

$0=10

$1=255

$2=0

$3=0

$4=0

$5=0

$6=0

$10=0

$11=0.010

$12=0.002

$13=0

$20=0

$21=1

$22=1

$23=3

$24=50.000

$25=1000.000

$26=250

$27=3.000

$30=10000

$31=0

$32=1

$100=80.000

$101=80.000

$102=400.000

$110=2000.000

$111=2000.000

$112=1200.000

$120=300.000

$121=300.000

$122=30.000

$130=400.000

$131=380.000

$132=55.000

ok

$#

[G54:-397.000,-377.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:0.000,0.000,0.000]

[TLO:0.000]

[PRB:0.000,0.000,0.000:0]

ok

?

<Idle|WPos:0.000,0.000,-3.000|FS:0,0|WCO:-397.000,-377.000,0.000>

ok

Lightburn.txt (4.0 KB)

So that file set off the Alarm 3 however I reopened the GCode file and hit the Run GCode button and it ran without issues. So I can run GCode in Lightburn without the Alarm if thats of any importance.

I don’t see anything particularly interesting in any of the output.

This is particularly interesting.

Can you run the gcode any number of times without triggering the issue?

If so, try this:

  1. Power cycle the laser
  2. In Console window enable “Show all”
  3. Run the same job that you attached the gcode for from LightBurn by pushing the Start button in Laser window
  4. Capture all output in Console from time you power cycled until end of job, then include in a reply here.
1 Like