Error 24 on a project that worked fine before

EG72 · January 17, 2024, 7:06pm

Not sure what is happening, but I have had issues with error 24.

research says it might be a communication error, so I changed out to a different USB cord. as soon as I hit frame, it says error 24. I went to a file that I used successfully the day before, and it gave me the same error.

Rebooted the laser and computer, decided to start fresh and draw a rectangle and tried to frame, still got the error 24. I am using the GRBL language.

More research suggested possibly eliminating the USB cord. I saved the file to a USB stick, and loaded it. It did frame, but showed an unknown error when I tried to run the file. (Atezer L2 24W).

attached is a file that worked before, but now doesn’t. gives me the error 24.

any help would be appreciated.

g code file that worked before.gc (413.7 KB)

gilaraujo · January 17, 2024, 7:08pm

Could you post error (exactly) and maybe upload the Gcode here

Additionally though
Can you post your EDit → device settings
Any chance you enabled gcode clustering by mistake?

EG72 · January 17, 2024, 7:11pm

I attached the G-code. I am not sitting in front of the laser at the moment, so I can’t paste in the error. from memory, it says the error is on line 2.

g code file that worked before.gc (413.7 KB)

gilaraujo · January 17, 2024, 7:14pm

Unable to see anything wrong as such on your Gcode

Maybe someone else can put a 2nd set of eyes on it and highlight what might be the issue

berainlb · January 17, 2024, 7:34pm

Most likely a comms issue but would need to show the specific errors to confirm.

The fact that you get a different error when run locally is a good indication of that. Please show both.

EG72 · January 17, 2024, 7:40pm

I’ll post tonight, but if it’s a comm issue, what is the solution? keep swapping out cords? it’s not like i moved the laser to a different area and i’ve tried two different cords already.

berainlb · January 17, 2024, 7:44pm

This will depend on the root cause. Cords are an obvious source. Try a different port on the computer.

If you have any USB hub in between remote it from the equation. You could also try updating the firmware on the laser.

But first confirm function by running locally. That could point to something else going on.

EG72 · January 17, 2024, 7:46pm

I did try two different ports. a usb A x usb c cord and a usb c x usb c cord. neither worked.

no hub in the line.

when I ran it locally, it framed but gave an error when i tried to run the file. this made me think it was something more complicated.

gilaraujo · January 17, 2024, 7:49pm

from what you are saying, and this is just a gut feeling really
Something changed on your Device settings (profile of the machine)

and now the error / missing configuration is being embeded on the code
Which is why even exporting and running offline errors too?

A image of Edit > device settings should clarify

EG72 · January 18, 2024, 1:30pm

Here are the device settings.

Also, you asked for the exact error. See below.

gilaraujo · January 18, 2024, 1:33pm

Couple diagnostics things you could do
In no particular order

disable temporarily the Z axis settings here

check again if you get alarm 2

Also Laser panel - start from
Make sure you are in absolute coordinates

Lastly, i see you have extended lenght
And i see you configured it on Edit > device settings
But did you tell firmware too by changing the
$131 setting?

EG72 · January 18, 2024, 4:00pm

i did change the $131 setting. I am using the absolute coordinates. (I even set a new file to be a 1" square, and got the same errors, which caused even more confusion)

I’ll try disabling the z axis, but i saw that already on a chat forum, and didn’t seem to help. I’ll try again though.

gilaraujo · January 18, 2024, 4:02pm

also try in console
$i
press enter
$$
Press enter
$#
press enter
Thenc opy/paste the whole output here

EG72 · January 18, 2024, 11:00pm

$i

[VER:1.1h.20230501:]

[OPT:VNZHDLI,254,2048]

Target buffer size found

ok

$$

$0=10

$1=25

$2=0

$3=7

$4=0

$5=0

$6=0

$10=1

$11=0.010

$12=0.002

$13=0

$20=1

$21=1

$22=1

$23=3

$24=200.000

$25=2000.000

$26=250

$27=4.000

$30=1000

$31=0

$32=1

$33=1

$34=10

$100=100.302

$101=100.100

$102=3212.851

$110=50000.000

$111=20000.000

$112=200.000

$120=4000.000

$121=1000.000

$122=100.000

$130=410.000

$131=850.000

$132=40.000

$140=30000.000

$141=20000.000

$142=200.000

$143=2000.000

$144=1000.000

$145=100.000

$150=6000.000

$151=6000.000

$152=200.000

$153=1000.000

$154=500.000

$155=100.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:0.000,0.000,0.000]

[TLO:0.000]

[PRB:0.000,0.000,0.000:0]

ok

gilaraujo · January 18, 2024, 11:01pm

weird steps per mm.
are you sure these are the defaults?

EG72 · January 18, 2024, 11:02pm

i never actively changed them

gilaraujo · January 18, 2024, 11:02pm

Try
$RST=*
press enter
Then recheck $$?

maybe you ran a step callibration ?

EG72 · January 18, 2024, 11:02pm

how do i go back to default?

EG72 · January 18, 2024, 11:04pm

$RST=*

[MSG:Restoring defaults]

ok

Grbl 1.1h [‘$’ for help]

$$