Consistent Alarm 3

Hello! New user here and very excited.

I’m running Lightburn on OSX, and have managed to get my new Ortur 15W firmware updated and working to do a few simple shapes. However, on some shapes I am seeing a consistent ALARM 3 message on the console. It’s consistent in that it happens in the same place in a given GCode file if I run it multiple times, but I cannot see anything wrong with it nor can I figure out what’s triggering it. I can provide more files if that helps.

For example, this one triggers the following console message:
Starting stream
ALARM:3
On or near line 135:
Stream completed in 0:31
ok

Here’s an abridged version of the GCode file. I have indicated line 135 with an arrow, it’s not there in the actual file.
; LightBurn 0.9.09
; GRBL device profile, absolute coords
G00 G17 G40 G21 G54
G90
M4
; Cut @ 120 mm/min, 20% power
M8
G0X83.77Y73.73
G1X83.59Y73.95S80F120
G1X83.43Y74.2
G1X83.3Y74.5
G1X83.21Y74.83
…(snip)
G1X85.57Y140.55
G1X85.7Y140.93
G1X85.8Y141.32
G1X85.88Y141.87
G1X85.91Y142.41
G1Y142.58
G1X85.98Y143.46
G1X86.1Y144.34
G1X86.28Y145.22
G1X86.51Y146.09
G1X86.84Y147.04 <-- line 135
G1X87.21Y147.91
G1X87.63Y148.71
G1X88.11Y149.45
G1X88.92Y150.53
G1X89.77Y151.58

Any help would be appreciated.

1 Like

GRBL Alarm 3 is “Reset while in motion. Grbl cannot guarantee position. Lost steps are likely. Re-homing is highly recommended.”

What are the travel limits of that machine? The “on or near” thing doesn’t count commented out lines, so it’s probably closer to the bottom of the lines you’ve posted, which makes me think it’s either the X or Y axis going out of bounds - Both of them are steadily increasing in the code shown.

1 Like

Thanks for the quick reply. There are only three commented lines, so what I identified as 135 would be counted as 132.

Travel limits are, according to the documentation, 150x160mm. It’s nowhere near the actual limits of the machine and it’s not when it bumps up against an imaginary one either. The circled spots are two different stopping points. The lower one is the one from the code snippet.

I’ll play with it a bit more, thanks for the info on the error code. Can you provide a link to a reputable reference so I can make use of it in the future?

Grbl-v1.1 grbl Response Messages

Grbl-v1.1 Alarm Messages

Thank you. I think I found the problem - I had my x and y limits mixed up. 150 and 160 are pretty close, but not if you bump into one! The design of the cutter also had me fooled about where the actual edges are, y is a lot shorter than it looks.

Much appreciated.

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