I have an Atomstack A5 and recently upgraded the laser to the M100. I decided to add limit switches to my frame and reflash the board with GRBL so I can store my settings. After flashing the board with GRBL customized XY homing points, I got my laser to home correctly to the bottom left of the frame with the limit switches working.
The issue I have now is the laser will cut simple square boxes fine, however if I attempt anything other than a simple squares for example, lettering, a circle filled box etc, the laser will halt and will keep emitting a low power beam. The console displays error code 3. I looked into some of the solutions to error code three but haven’t had any luck. I have attempted load the original Atomstack settings back to the board but I still have the same issue.
I’m fairly new to tinkering with the code but I believe it might have to do with the system not knowing the frame size and the relation to the laser, but now I’m lost. I have added some screen shots of the console readings along with my settings. Hopefully someone can spot where I am going wrong.
The software version is GRBL VER 1.1h.20190830: OPT:VZ,1,128. I’m unsure whether it was enabled with zeroing origin after homing. Processing: LIghtburn $.jpg…
I suspect the device is configured with the wrong profile.
Push Devices button in Laser window. Then click on the name of your laser and then Edit. Change the device type to “GRBL” specifically. Then complete the wizard.
Still no luck unfortunately. Here is the report I got from the console when I tried to run a circle.
Waiting for connection…
Grbl 1.1h [‘$’ for help]
[MSG:‘$H’|‘$X’ to unlock]
error:9
G-code locked out during alarm or jog state.
[MSG:Caution: Unlocked]
ok
Homing
[VER:1.1h.20190830:]
[OPT:VZ,15,128]
Target buffer size found
ok
ok
Starting stream
Layer layer1
error:3
Grbl ‘$’ system command was not recognized or supported.
On or near line 0:
Job halted
Stream completed in 0:00ok
ok
ok
ok
ok