I know its new, but I havent been able to find anything recent about wifi connection status for the Falcon a1 pro. I got this last summer, and it connects to their software with no problems, but its severly lacking compared to lightburn. I can get it working fine via usb, but my laser is 50’ away from my pc near the window andhaving a dedicated machine is a bit much.
How do you keep an eye on the laser while it is running?
Not really helping with my question, but the machine is in line of site by the window so I can vent it.
True, so let us work on that issue. Using WiFi is usually (strongly) not recommended. This does not apply to just the Falcon A1 machines. If you look at a WiFi signal with an analyzer app, you will see the signal strengths vary from maximum to all the way to zero. If Lightburn is streaming data to the laser, (1) that data is lost and (2) there is no means of error correction at the laser end on the data packets.
How are you going to feel if you have about $30 worth of the product in the laser and you get a “Lost Connection” in the Console display about 1/2 way thru the burn?
There are other methods that are much more reliable:
- Use a wired ethernet to the laser, if yours supports it.
- Use a powered (amplified) USB cable to the laser, to get around USB length limits.
- Create a GCode file on a xD card and take it to your laser if it will accept one.
I have a relevant question: If you do not have a PC at the laser, then how are you going to Jog the laser around when doing your setups? Or see if the Framing is where it is supposed to be?
A 50’ line of sight is a long distance in any building. How big would a fire have to be before you will see it? There is a recent posting by a person wanting info about a Sculpfun 33w upgrade that said thankfully the fire did not set their house on fire. Safety first, then production.
1 Like
Please keep responses focused on the original question about wifi connectivity for the A1 Pro and LightBurn.
This is a support forum, not a discussion or opinion thread. If you don’t have relevant experience or a direct answer to the question being asked, there’s no need to respond.
Side commentary, assumptions, or lectures don’t move the issue forward and just add noise. Helpful, on-topic answers only—thank you.
If you can’t use the help and suggestions of the users here in this forum, then use this address - support@lightburnsoftware.com
It may be called official “LB Support Forum”, but here it is normal users who spend their time helping others. And unfortunately it is sometimes misunderstood, especially by new users who think that the support forum has some responsibility for solving their problems. But it is absolutely not the main task of the forum to provide professional software/hardware support, but to exchange experiences and ideas and discuss possibilities for improving both hardware and software. If you can’t use it, then use the address from the beginning of my post or call your laser machine supplier.
There are 10 threads that pop up when I search for Falcon a1 pro and wifi…, I assume you have found it and could use some of it.
3 Likes
“Anyone Connected to their machine via wifi with lightburn yet?”
Matt,
I can hardly add to what @bernd.dk posted. I will say this: When I post, it is with the assumption that many others will see your generic title and read the posting. For this reason, I respond so that they might also benefit from the information provided. You are not the only one having laser issues and the Forum is here to help everyone.
1 Like
Gentlemen, I will point you to the forum guidelines. Specifically:
Keep It Tidy
Make the effort to put things in the right place, so that we can spend more time discussing and less cleaning up. So:
- Don’t start a topic in the wrong category.
- Don’t cross-post the same thing in multiple topics.
- Don’t post no-content replies.
- Don’t divert a topic by changing it midstream.
- Don’t sign your posts — every post has your profile information attached to it.
Rather than posting “+1” or “Agreed”, use the Like button. Rather than taking an existing topic in a radically different direction, use Reply as a Linked Topic.
@LightBurn could you have a mod delete all of these responses that are not related to the original question. I do not have any options/permission to moderate my own topic myself to ensure it stays on point, and there are no flag for review features showing up for the specific posts.(perhaps an account status permissions issue?)
I am simply trying to see if anyone had accomplished getting the wifi working on this specific piece of hardware prior to buying your software which is what your site suggests possible new customers do. My expectation is that this thread would stay empty till someone found a work around or official support had been added. If these 2 cannot follow the community guidelines can I at least block them from further responses hijacking the original question? I refuse to waste any further time time dealing with them.
Thanks for your help.
1 Like
Hi Matt,
The first answer to any request about remotely controlling a laser should always include
“Never laser unattended”. So it’s not a radically different direction to point it out.
You’d be amazed at how quickly a fire grows, and how long it can take before you notice the flames in the corner of your eyes. Ask me, how I know 
3 Likes
Now, on the topic of the Falcon A1 Pro:
LightBurn supports WiFi connection over Telnet. This works for many devices, but the A1 Pro doesn’t offer this option (yet).
(The device runs a full Linux SoC, and would technically be very capable of using telnet - A tried and tested standard.)
Falcon Design Space uses WebSockets to remotely control the laser. LightBurn does not use WebSockets (yet).
The protocol would be complicated to implement because every manufacturer uses different “handlers”
We would require a comprehensive list of the supported commands from the manufacturer in order to implement communication over the WebSockets protocol.
The current solution to run it wirelessly is to Save GCode in LightBurn, move it over to the machine via USB stick, and run it from there.
I also have an A1 Pro in the lab, and found a couple of supported WebSocket handlers by poking at it.
One example of a used handler is /system/getSN - Open this URL in a browser to get back the Serialnumber of the device http://[IP-OF-THE-LASER]:8080/system/getSN
Design Space sends the entire Gcode job to the machine and runs it from there, so there is a command for sending jobs to the laser without sneaker net, but we would need the full documentation in order to implement it.
3 Likes
We will have to talk to Creality about this more and see what can be done.
The problem with a lot of these new machines which people need to understand is that it’s not just “GCode over Network”. It’s generally GCode encapsulated in something like websockets which is a bit more complicated than a serial or TCP/Telnet connection. The biggest problem is that there’s no “one way” to use something like websockets - we would have to implement the specific protocol for each different device type separately. Something that we will and are looking at but will take time as we already have a huge backlog of protocols to support and only so many developers to do the work.
4 Likes
Thank you — this is exactly the kind of answer I was looking for. The response you provided here, along with Adam’s follow-up, is spot on and genuinely helpful.
I’d strongly encourage a quick revisit of how community guidelines are applied, especially in the context of what a support forum is meant to be. I understand the motivation around safety, but a support thread works best when it stays focused on answering the question at hand. What you shared here is valuable not just to me, but to anyone else who comes along later trying to solve the same problem.
For context, I’m a software engineer by trade, and I coach both developers that report to me and forum admins to treat each support post like a ticket with a single responsibility. Answer the question, solve the problem, move on. When that approach is followed, people don’t have to sift through pages of tangential discussion to find the solution. No one wants another stack overflow like site to sift through haha. I know you know what I’m talking about 
Do that consistently, and the forum naturally becomes a living wiki — searchable, referenceable, and actually useful. Which, in the long run, helps everyone.
Thanks for the clear and direct explanation Adam and Aaron — that was exactly what I was looking for, and I really appreciate you taking the time to spell it out.
As a fellow developer, I completely understand the reality here. Once you move into WebSockets, you’re no longer just dealing with a transport, but with vendor-specific protocols, message formats, and asynchronous behavior, all on top of an already full backlog and limited development time.
From a longer-term perspective, it does seem like manufacturers in the consumer, home-based manufacturing space are committing hard to WebSockets. That direction naturally opens the door to cloud-based workflows and remote services in a way raw TCP/Telnet never really could. Even if each vendor requires its own protocol layer, having that foundation in place feels like it would be the right move for the software over time.
Either way, thanks again for the candid answer — it was genuinely helpful. I’ll definitely keep an eye on LightBurn going forward, and once you’re able to work through the backlog, I’ll very likely be a buyer again. In the meantime, I may try a USB-over-Ethernet adapter before my trial runs out, just to see if I can get things working that way.
My main use case is the print-and-cut feature — you and the team did an amazing job with it, and it really takes the guesswork (and in my case lots of back and forth) out of getting everything perfectly aligned.
I wish you all the best, and keep slaying those Jira dragons.
Matt
???
Great 
Excellent 
***I have both developers and community managers(aka mods) I work with*** sorry for the typo, hope this clears it up.
I see it clearly now…