Hi.
I’m currently testing a Creality Falcon A1 Pro for Creality prior to it’s release.
I have installed the relevant .lbdev file into Lightburn. Lightburn cannot find/see the camera. Due to this fact I’m unable at present to use the laser with my preferred Lightburn software due to the fact that the laser module on the A1 Pro uses autofocus. There is no way of manually adjusting the laser module height.
I’ve tried running the setup with Falcon Design Space, but find the software incredibly frustrating to use. I’ve been using Lightburn for a couple of years now and find it so easy in comparison.
Has anyone got any ideas on how to overcome this problem please?
Thanks in advance.
The camera and autofocus do not rely on each other. You absolutely need no camera for any auto focus to work. I can’t imagine how the A1 should be different to any other laser in this regard. Move the laser to your workpiece, do the focusing, then move the laser to the desired start position and start the job.
Thanks Misken.
The camera on the A1 Pro doesn’t have a manual focus. It’s gear driven in Falcon Design Space and uses a “Z” axis. When connected to Lightburn it always sets to mid focus or maximum height and therefore I can’t set it to the optimum focus setting..If that makes sense.
To me, that doesn’t make sense 
The camera is fixed to the top, right? It won’t have a manual focus or at least a fiexed focus for the full workspace height.
Are you talking about the laser head? According to the documentation, the auto focus is done in the center of the workspace, you just need to place your workpiece there and start the autofocus using the touch screen. You might also be able to start the process by the correct gcode command, which you might get from your Creality contact if you have a pre-series device.
1 Like
Yes, the camera is mounted top middle. I haven’t found a way of doing the auto focus using the touch screen, but will investigate that idea further.
Thanks.
Cracked it…Activated z axis in Lightburn, so I can manually set focus. It still can’t see the Creality camera, but I can live with that.
1 Like
If you are on Windows, there is a Camera tab, you will find an option to activate or not the autofocus, it can help
1 Like
Thanks Ganitta..I’ll investigate that option.
Creality did say that the A1 Pro camera wasn’t compatible with Lightburn at present. Hopefully that will be addressed in time.
1 Like
The A1 Pro is relatively new and operates differently from the older Falcons.
Two of our developers have a Falcon A1 Pro on its way to them, and we are in contact with Creality to ensure smooth functionality.
We were introduced to this machine for the first time last week at the LBX event in New York, and I’ve had a short moment to try it.
Melvin is correct. With the Autofocus function, you set the focus of the laser head. We don’t know the Gcode that the machine needs for this autofocus sequence, but in the meantime, you can initiate it from the laser’s touchscreen. See here
If I understand correctly, what you are doing here is homing the Z-Axis. (Setting the 0 point of the axis, not in relation to the material height.)
And then manually jogging the Z-Axis with the up- and down-arrows in the “Move” window.
When Creality shares the Macro code or command for their Autofocus sequence, we can choose the Custom Gcode Device Type and enter the command in the Device Settings here:
I would be interested in seeing the .lbdev file you mentioned. Did you get this from Creality?
As far as the camera is concerned:
The A1 Pro does not have a separate USB connection to the camera like the previous Creality lasers had. The camera is only accessible over the network. I’m happy to let you know that we managed to add it in LightBurn by using an internal Dev/Alpha version of LightBurn with IP camera support in testing. (Yes, it’s coming!) 
You can access the image stream at:
http://[IP-OF-THE-LASER]:8080/media/getCapturePhoto
We ask you to be patient until this version is ready — we don’t have a release date to share just yet.
4 Likes
Creality sent me the .lbdev file to import into Lightburn.
Yes, to focus the module height I jog it into the correct position using the up/down arrows in the “Move” window with material in position on the honeycombe. Seems to work well so far.
1 Like
Any update on this? I want to buy Lightburn, but as the A1 Pro is my only laser, and I am a total newbie, I’d like to be able to use the full functionality of it. Thanks!
Yes. The A1 Pro is not using a standard GRBL firmware, and we don’t know everything about their custom implementation.
However, one of our devs reported that it’s mostly working.
(As mentioned earlier, the camera is accessible over WiFi only. LightBurn does not yet support IP cameras, but it’s coming )
Be sure to use the free trial to ensure everything works for you: Download / Trial – LightBurn Software
Creality just updated their instructions and include a Device Profile to import: lightBurn Connection Guide | Creality Wiki
We’d love to hear about your experiences!
1 Like
Hi there,
new owner of the Creality Falcon A1 Pro here.
May it be possible to get the hands on this alpha/dev-software so I can test the wifi camera function?
Thanks and regards,
Jan
I’ll ask if it’s ready to share.
That would be nice. I‘m in the middle of the trial period and will buy a license soon. I‘m happy to act as a beta tester for this release 
IP cameras are not available for public testing just yet.
One more to join while waiting for the Lightburn camera, with a Falcon A1 Pro, for now the machine works very well with the program.
I will post in this thread when it is ready.
That’s good to hear!
Are you using Creality’s device profile from this page?
I’m in the same situation, I absolutely need to be able to access the camera on the Falcon A1 Pro. How long do you think it will take approximately? I just bought Lightburn and found myself in this unpleasant situation. Having tried Lightburn with the regular Falcon A1, I wasn’t expecting this incompatibility.
Neither did we.
It will likely be in the 2.1 Release Candidate, which shouldn’t be too far out. The release candidates come out ‘when they’re ready’ so I cannot provide a specific date, as much as I may like to. So for now, you’ll have to wait until the RC. Please let us know how it goes once you give it a try!