Several errors in the same work Creality Falcon A1 Pro

serjforius · August 19, 2025, 5:55pm

I was running a test cut on the Creality Falcon A1 Pro 20W using 3mm MDF material, with the file created in o2creative, with minimum power parameters ranging from 10% to 100% on a scale of 5. Minimum speed was 100, and maximum speed was 3100 on a scale of 100.

There were only a few lines left to finish at all the powers and slowest speeds, and the following errors started to appear:

G-code commands are logged out during alarm or job state, error 9.
Reset white in motion machine position is likely lost due to sudden halt. Rehoming is highly recommended.
ALARM:3
Restart while in motion. GRBL cannot guarantee the position. Steps are likely to be lost. It is recommended to return to 0.
GrblHAL 1.1f [‘$’ or ‘$HELP’ for help]
[MSG:‘$H’|‘$X’ to unlock]
[MSG:Caution: Unlocked]
ok
‘$’ command cannot be used unless controller state is idle. Ensures smooth operation during a job.

I’ve tried deleting the profile from the laser machine and adding it again, but the same thing keeps happening. From what I’ve been reading, it could be the USB cable. I’ve replaced it with three USB cables, although none of them have ferrite. Could it be a cable problem? It recorded fine for the first 20 minutes; it would have failed sooner. Thanks

Aaron.F · August 19, 2025, 6:01pm

Hello Sergio,

The A1 Pro is very new, and I’m curious which settings you are using because we haven’t had hands-on yet.

Could you please export your Device Profile, and send us the .lbzip file? Guide below:

serjforius · August 19, 2025, 8:39pm

Thanks for answering, I’ll go into more detail about the machine.

This is the console log that appears as soon as the machine starts with Lightburn open.

G0
error:7
Error de lectura de EEPROM. Restablecer y restaurar a los valores predeterminados.

Summary

$0=10
$1=100
$2=0
$3=3
$4=7
$5=0
$9=1
$10=511
$11=0.010
$12=0.002
$13=0
$14=2
$15=0
$16=0
$17=0
$18=0
$20=0
$21=1
$22=43
$23=3
$24=1000.0
$25=4000.0
$26=100
$27=5.000
$28=0.100
$29=0.0
$30=1000.000
$31=0.000
$32=1
$33=1000.0
$34=0.0
$35=0.0
$36=1000.0
$37=4
$39=1
$40=1
$43=1
$44=4
$45=1
$46=2
$47=0
$62=0
$63=3
$64=0
$100=80.000
$101=80.000
$102=78.390
$103=8.900
$110=36000.000
$111=36000.000
$112=2000.000
$113=36000.000
$120=1000.000
$121=1000.000
$122=500.000
$123=1000.000
$130=363.000
$131=273.000
$132=33.000
$133=999.000
$140=1500
$141=1500
$142=1200
$143=1200
$150=16
$151=16
$152=16
$153=16
$180=1000.0
$181=1000.0
$182=1000.0
$183=1000.0
$190=4000.0
$191=4000.0
$192=4000.0
$193=4000.0
$200=22.0
$201=22.0
$202=22.0
$203=22.0
$210=50
$211=50
$212=50
$213=50
$220=22.0
$221=22.0
$222=22.0
$223=22.0
$338=15
$339=0
$341=0
$342=30.0
$343=25.0
$344=200.0
$345=200.0
$346=1
$376=0
$384=0
$398=512
$481=0
$486=0
$487=8.000
$810=5.000
$811=5.000
$812=5.000
$813=5.000
[MSG:Warning: SafeDoor Close]
GrblHAL 1.1f [‘$’ or ‘$HELP’ for help]
$I
ok
$#
$0=10
ok
ok
$1=100
ok
ok
$10=511
ok
ok
$100=80.000
ok
ok
$101=80.000
ok
ok
$102=78.390
ok
ok
$103=8.900
ok
ok
$11=0.010
ok
ok
$110=36000.000
ok
ok
$111=36000.000
ok
ok
$112=2000.000
ok
ok
$113=36000.000
ok
ok
$12=0.002
ok
ok
$120=1000.000
ok
ok
$121=1000.000
ok
ok
$122=500.000
ok
ok
$123=1000.000
ok
ok
$13=0
ok
ok
$130=363.000
ok
ok
$131=273.000
ok
ok
$132=33.000
ok
ok
$133=999.000
ok
ok
$14=2
ok
ok
$140=1500
ok
ok
$141=1500
ok
ok
$142=1200
ok
ok
$143=1200
ok
ok
$15=0
ok
ok
$150=16
ok
ok
$151=16
ok
ok
$152=16
ok
ok
$153=16
ok
ok
$16=0
ok
ok
$17=0
ok
ok
$18=0
ok
ok
$180=1000.0
ok
ok
$181=1000.0
ok
ok
$182=1000.0
ok
ok
$183=1000.0
ok
ok
$190=4000.0
ok
ok
$191=4000.0
ok
ok
$192=4000.0
ok
ok
$193=4000.0
ok
ok
$2=0
ok
ok
$20=0
ok
ok
$200=22.0
ok
o
$201=22.0
ok
ok
$202=22.0
ok
ok
$203=22.0
ok
ok
$21=1
ok
ok
$210=50
ok
ok
$211=50
ok
ok
$212=65
ok
ok
$213=50
ok
ok
$22=43
ok
ok
$220=22.0
ok
ok
$221=22.0
ok
ok
$222=22.0
ok
ok
$223=22.0
ok
ok
$23=3
ok
ok
$24=1000.0
ok
ok
$25=4000.0
ok
ok
$26=100
ok
ok
$27=5.000
ok
ok
$28=0.100
ok
ok
$29=0.0
ok
ok
$3=3
ok
ok
$30=1000.000
ok
ok
$31=0.000
ok
ok
$32=1
ok
ok
$33=1000.0
ok
ok
$338=15
ok
ok
$339=0
ok
ok
$34=0.0
ok
ok
$341=0
ok
ok
$342=30.0
ok
ok
$343=25.0
ok
ok
$344=200.0
ok
ok
$345=200.0
ok
ok
$346=1
ok
ok
$35=0.0
ok
ok
$36=1000.0
ok
ok
$37=4
ok
ok
$376=0
ok
ok
$384=0
ok
ok
$39=1
ok
ok
$398=512
ok
ok
$4=7
ok
ok
$40=1
ok
ok
$43=1
ok
ok
$44=4
ok
ok
$45=1
ok
ok
$46=2
ok
ok
$47=0
ok
ok
$481=0
ok
ok
$486=0
ok
ok
$487=8.000
ok
ok
$5=0
ok
ok
$62=0
ok
ok
$63=3
ok
ok
$64=0
ok
ok
$810=5.000
ok
ok
$811=5.000
ok
ok
$812=1.000
ok
ok
$813=5.000
ok
ok
$9=1
ok
ok
[VER:1.1f.20231005:]
[Firmware:Version v1.0.4]
[OPT:VNCZHL,512,65536,4,0]
Target buffer size found
[AXS:4:XYZA]
[NEWOPT:ENUMS,RT+,HOME,NOPROBE,REBOOT,SED,TMC=15]
El tamaño de la máquina no coincide
GrblHAL 1.1f [‘$’ or ‘$HELP’ for help]
ok
ok
ok
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
[VER:1.1f.20231005:]
[Firmware:Version v1.0.4]
[OPT:VNCZHL,512,65536,4,0]
Target buffer size found
[AXS:4:XYZA]
[NEWOPT:ENUMS,RT+,HOME,NOPROBE,REBOOT,SED,TMC=15]
[FIRMWARE:grblHAL]
[FREE MEMORY:14522K]
[DRIVER:Allwinner]
[CPU RATE:600000000 Hz]
[DRIVER VERSION:V1.0.0]
[DRIVER OPTIONS:V1.0.0]
[BOARD:A1 Pro Laser Master]
[MAX STEP RATE:10000000 Hz]
[BUILD:20250618205542]
[PLUGIN:Trinamic v0.12]
[KINEMATICS:CoreXY v2.02]
ok
ok
[G54:0.000,0.000,0.000,0.000]
[G55:0.000,0.000,0.000,0.000]
[G56:0.000,0.000,0.000,0.000]
[G57:0.000,0.000,0.000,0.000]
[G58:0.000,0.000,0.000,0.000]
[G59:0.000,0.000,0.000,0.000]
[G59.1:0.000,0.000,0.000,0.000]
[G59.2:0.000,0.000,0.000,0.000]
[G59.3:0.000,0.000,0.000,0.000]
[G28:0.000,0.000,0.000,0.000]
error:7
Error de lectura de EEPROM. Restablecer y restaurar a los valores predeterminados.
ok
ok
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
ok
ok
ok
ok
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0|Ov:100,100,100>
ok
ok
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0|WCO:0.000,0.000,0.000,0.000>
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
ok
ok
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
ok
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
<Idle|MPos:0.000,0.000,0.000,0.000|Bf:512,65535|FS:0,0>
ok
ok
ok

As you can see, as soon as I start the machine, it throws up an error message about the size of the work area, as well as a message that I was told to ignore.

I’m attaching a file that Creality sent me, since I was configuring the machine as GRBL and it was GRBL-LPC according to Creality. When the machine automatically searches for it, the controller indicates a different size and only GRBL.

falcon_a1_pro.lbdev (19,4 KB)

The following file is the machine image. Once I uploaded the Creality file, I configured some parameters. While engraving, it failed for the first time at 10% power and 100 mm/min speed, not giving a flame error and giving the other errors. I managed to finish everything by removing the entire 100 mm/min test line.

I attached the configuration file when it gave an error

falcon serjforius configuracion.lbzip (5,5 KB)

I attach the current configuration file, if I need to change any parameter or perform any test, I am at your attention.

parametro actuales .lbzip (5,5 KB)

Thank you very much

serjforius · August 20, 2025, 9:51pm

Las palabras de G-Code consisten en una letra y un valor. No se ha encontrado la letra.

error:1

Resumen

error:1

Las palabras de G-Code consisten en una letra y un valor. No se ha encontrado la letra.

error:1

Las palabras de G-Code consisten en una letra y un valor. No se ha encontrado la letra.

ALARM:3

Reinicie mientras está en movimiento. Grbl no puede garantizar la posición. Es probable que se pierdan pasos. Se recomienda volver a retornar a 0.

GrblHAL 1.1f [‘$’ or ‘$HELP’ for help]

[MSG:‘$H’|‘$X’ to unlock]

GrblHAL 1.1f [‘$’ or ‘$HELP’ for help]

[MSG:‘$H’|‘$X’ to unlock]

[MSG:Caution: Unlocked]

ok

<Idle|MPos:155.350,160.588,-20.602,0.000|Bf:512,65535|FS:0,0>

ok

<Idle|MPos:155.350,160.588,-20.602,0.000|Bf:512,65535|FS:0,0>

ok

<Idle|MPos:155.350,160.588,-20.602,0.000|Bf:512,65535|FS:0,0|WCO:0.000,0.000,0.000,0.000>

ok

In the middle of engraving, halfway through the letters, it stopped due to this error again. What configuration could I have wrong? I’m attaching the file again with the configuration after what happened.

20agosto2025.lbzip (5,9 KB)

I have noticed in the community that you have to have the gcode grouping disabled, but I cannot find it in the device settings. I don’t know if the name has changed.

How has this setting changed in Lightburn 2.0.02 for Mac?

Thanks

Edit

I deleted the parts that were already done except for one and continued with the job without a problem. So I don’t understand the error.

Later, on another job, I did the entire job but didn’t finish cutting. I removed the laser output for the areas I didn’t want and re-cut only the parts. The Gcode error occurred again. Then, when the machine stopped, it gave a low air pressure error.

Aaron.F · August 22, 2025, 1:59pm

Yes, this notice about a device mismatch is displaying rightfully: The Device Profile you received from Creality contains a “Working Size” of 358 x 268mm", but the Firmware Settings report 363 x 273 mm (the $130=363 and $131=273mm)

We don’t know the correct maximum travel of the axes on the A1 Pro. It’s either a mistake in the firmware, or in the Device Profile.

If you Ignore this message, LightBurn shouldn’t warn you again and you should be fine.
If the maximum travel of the A1 Pro is really only 363mm, this should be corrected in the firmware!
You would need to ask Creality for more details.

I can see you’ve enabled the Z-Axis:

They might also have had a good reason that they didn’t enable the Z-Axis in their Device Profile.
We currently know as much as you about the settings needed here.
We will need more input from the Creality Devs here.

If you can share the error you received, the steps you performed, and the file used, we might be able to get a clue, what’s going on.

serjforius · August 22, 2025, 10:07pm

Regarding the machine size, if I configure it according to the controller, it won’t let me go beyond the travel they gave me, even if I set the bed to a larger size. They should update this in the controller. They already performed an update, and it doesn’t seem to stop, although the EEPROM error persists.

I enabled the Z-axis because it had travel, as it adjusts itself. But I disabled it because they adjusted an autofocus button, and it allows it to move without having it active.

Right now, the error it always gives when turning on the machine is:

G0
error: 7
EEPROM read error. Reset and restore to default values.

Yesterday and today, I’ve done short jobs and it’s worked fine. Occasionally, a message about the machine having insufficient air pressure appears, but it doesn’t appear in LightBurn.

I’ll continue working with it and will post the problem and a full description of the process if it fails again.

Right now, I’m working from the configuration they sent me as is, and without any problems. It only stopped once with the same error, which was when I posted the last message.

Thanks for your support.

AdiGital · August 24, 2025, 2:23pm

I also experienced issues. I had various errors at random progress of a job at about 30-35%. The console was flooded them. As “various” I mean that I noticed at least two different ones for same job (sorry didn’t copy them). I then found “Enable DTR signal” in machine settings and switched it off. This seemed to help and I could finish the job. Unfortunately today during Material Test it came back flooding the console with:

...
error:25
A G-code word was repeated in the block.
...

And ended with:

error:25
A G-code word was repeated in the block.
ALARM:3
Reset while in motion. Grbl cannot guarantee position. Lost steps are likely. Re-homing is highly recommended.

I tried several times even after restart but no success.

The Falcon is connected via USB (Mac) as WiFi doesn’t work (apparently) yet. No such issues in Falcon Design. But that one on the other had works only via WiFi (for now).

Aaron.F · August 24, 2025, 3:23pm

That sounds tedious..

I don’t own a Creality A1 Pro, and can’t help any further, but will ping a dev to take a look.
Are you in contact with Creality about these issues?

Which firmware version do you have on the the laser?

DTR Signal is enabled in Crealitys device profile, and they likely had a good reason for it. It’s interresting, that you say, turning it off helped. (From my experience, when I got hands on the machine, it didn’t even connect when it was off)

Let us know, if you have any news!

AdiGital · August 24, 2025, 4:44pm

I did contact Creality regarding WiFi connectivity but got reply that it’s not supported “yet”. Also sent the issue with errors in job but didn’t get anything yet.

As for DTR (data transmission ready), from my experience, most serial ports over USB don’t use it, and only TX, RX is used for transmission. That’s why I tried it and was happy it did seem to work.

The profile they published doesn’t look “final”. You can see there some “residue” from dev machine:

"LastMachineFilePath": "C:/Users/114479/Desktop/美国展会文件/L016文件",

…and also as you noticed above the mismatch between firmware and profile dimensions or z axis.

I’ll see if and what they reply and will report here.

AdiGital · August 27, 2025, 8:15am

Creality replied asking if I’m “using genuine Lightburn software”
They asked to install new firmware V1.0.38, which I did but this has not solved the problem. I sent them back the console output.

BTW
Whose part is it to bring WiFi connectivity and camera support, Creality or Lightburn?

Aaron.F · September 4, 2025, 5:48pm

See, if this device profile improves things:

There will be IP-Camera support in LightBurn eventually. Creality plays a major part in how they provide the camera feed over the network. WiFi connectivity for control is 100% on Creality’s side to implement it.