Error Codes 9 and 20

[Jack2 (Jack Ross)]

I am getting two error codes 20 & 9. What does this mean?

[Will_vl (Will Vander Linden)]

9 = GCode commands invalid in alarm or jog state.
20 = Unsupported or invalid GCode command

Can you provider more details on what’s happening? Maybe describe the events that led up to the error codes?

[ednisley]

@Jack2

error codes 20

This usually happens when you’ve selected the wrong device type, causing LightBurn to send codes that the real device can’t handle.

This thread may help:

LightBurn generates an illegal GRBL code for my AtomStack A10 Pro (GRBL 1.1h)

When I draw a simple test pattern in LightBurn and run, I get an error 20 (near line 0). The code at the top of the file is M101 Pxxxx, where xxxx varies. M101 is “turn extruder on”, I’m using a laser cutter. When I comment that line out, everything is fine. I can’t find anywhere in setup where I can tell LightBurn that this is a laser, not a 3D printer. How can I fix this? Thanks Mark

[Jack2 (Jack Ross)]

So how do I fix it

[Jack2 (Jack Ross)]

I am new to this and was just trying to cut a letter out.

[ednisley]

@Jack2

So how do I fix it

The doc should explain what’s going on:

Adding and Configuring a Laser - LightBurn Software Documentation

[JohnJohn (John Johnson)]

Some folks get the invalid GCode command by accidentally selecting iLaser for the device profile.

With LightBurn running and your project in the workspace,
Click File
then click Save GCode.

Upload that file in a reply here.
If it complains, change the file extension to .txt and retry.

We can verify the selected device.

It’s also pretty handy to capture the first connection message from your AtomStack laser. The first few lines share the GRBL version, GRBL option information and firmware revision dates. Occasionally manufacturers offer updates to the existing firmware to address challenging symptoms.

If you’re willing to copy & paste the connection message I’d be more than happy to take a look.