AtomStack is communicating with Lightburn but wont run the cut

[ShepherdsWorkbench (Joseph C Shepherd)]

I have the Atomstack A5 M50 Pro. When I connected the machine it connected with GRBL but it wont not control or move the machine at all. I switched it to the iLaser software (I saw most people online connecting with the iLaser instead of GRBL). This resolved the movement issue. The laser will home and frame the work, however whenever I select start to run the file I have in lightburn, the program says that it is unable to run it. I have gotten away with saving the project as a gcode and running it that way but the gcode does not have the number of passes or speed settings in it and is not completeing the design the way it was set up in lightburn. I have no idea how to start to fix this issue.

Settings:
The project has 3 layers
2 engraving layers at 2500 mm/m at 60% power
final layer is a cut layer 1500 mm/m 100% power and 2 passes.

When I click ‘start’ in lightburn it doesnt run any of the layers it just immediately gives an error message.

[gilaraujo (Gil Araújo)]

@ShepherdsWorkbench

When I click ‘start’ in lightburn it doesnt run any of the layers it just immediately gives an error message.

Please post the full output of console from homing > Start > error
THat woudl be helpful

[ShepherdsWorkbench (Joseph C Shepherd)]

This is the layer settings

After i home the machine

After i attempt to run the design

[gilaraujo (Gil Araújo)]

can you take a screenshot of EDIT → Device settings?

[ShepherdsWorkbench (Joseph C Shepherd)]

[gilaraujo (Gil Araújo)]

assuming you are connecting to the machine via WIFI?

Using GRBL controller correct?

[ShepherdsWorkbench (Joseph C Shepherd)]

no its wired via USB

[gilaraujo (Gil Araújo)]

reconfirm your controller you choose
click devices > double click you atom > make sure is GRBL top one?

[ShepherdsWorkbench (Joseph C Shepherd)]

It originally set to GRBL but that did not give me the ability to control the laser. I could not home or frame through lightburn. I changed it to iLaser. After I changed it it gave me the home function through the software

[gilaraujo (Gil Araújo)]

Definitly you need GRBL
Set it to that, then make sure COM port is correctly set

Unless Atom has a very specific setup for that machine, all are GRBL
top one from the list

Then we can check why its not homing

[ShepherdsWorkbench (Joseph C Shepherd)]

Okay I’ll give that a shot as soon as I get home from work and I’ll update

[MikeyH (Mike Hembrey)]

“…invalid Gcode command…” is sometimes caused by Enable Gcode Clustering in the Device Settings window. GRBL does not support the compact form of Gcode commands.

[JohnJohn (John Johnson)]

@MikeyH

is sometimes caused by Enable Gcode Clustering in the Device Settings window.

And that’s the clue.

With the Device Settings window capture shown, 'Enable GCode Clustering isn’t an option so this eliminates GRBL the device type in LightBurn 1.4.05

.

‘Enable $J Jogging’ is also absent from the Device settings window - so this eliminates GRBL and GRBL-LPC.

I believe we’re looking at a Device Settings window for GRBL-M3.

Changing it to plain old GRBL will be a step toward your Atomstack A5 M50 Pro.