I have not been successful getting Creality’s Falcon2 laser to work from Lightburn on Linux Ubuntu 20.04.
I’ve followed all the steps, including adding $USER to dialout and tty groups . The ttyACM0 port gets created, and Lightburn gives me the “Laser Ready” status.
However, nothing else happens.
Below are the outputs of the Lightburn console and Linux terminal (I’ve also included a screenshot.).
Console:
Waiting for connection…
Waiting for connection…
Waiting for connection…
[OK]system start-up CV50-MASTER-Release V2.0.5 20230308-1436
Linux Terminal:
sudo ./AppRun
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Using the core prefs dir
QMetaObject::connectSlotsByName: Connecting slot on_sbNumberOfPasses_valueChanged() with the first of the following compatible signals: ("valueChanged(int)", "valueChanged(QString)")
QMetaObject::connectSlotsByName: Connecting slot on_sbFrequency_valueChanged() with the first of the following compatible signals: ("valueChanged(double)", "valueChanged(QString)")
QMetaObject::connectSlotsByName: Connecting slot on_sbQPulseWidth_valueChanged() with the first of the following compatible signals: ("valueChanged(double)", "valueChanged(QString)")
QMetaObject::connectSlotsByName: No matching signal for on_sbInterval_valueChanged()
QMetaObject::connectSlotsByName: Connecting slot on_sbMaterialHeight_valueChanged() with the first of the following compatible signals: ("valueChanged(double)", "valueChanged(QString)")
QMetaObject::connectSlotsByName: Connecting slot on_sbSupportHeight_valueChanged() with the first of the following compatible signals: ("valueChanged(double)", "valueChanged(QString)")
QMetaObject::connectSlotsByName: No matching signal for on_actionEdit_Text_closed(int)
connected
"Integrated_Webcam_HD: Integrate" "/dev/video0"
Port open succeeded
4 floaters
PathTree build: 0
4 floaters
PathTree build: 0
Optimize by score: 0 ms
CutBuilder took: 1 ms
------------------------------
Protocol::GenerateCuts time: 0
total time: 0:04.59 distance: 403.616 avg speed: 87.8475 segments: 295
4 floaters
PathTree build: 0
4 floaters
PathTree build: 0
Optimize by score: 0 ms
CutBuilder took: 1 ms
------------------------------
Protocol::GenerateCuts time: 0
total time: 0:04.59 distance: 403.616 avg speed: 87.8475 segments: 295
![Screenshot from 2023-12-01 15-11-56|690x462](upload://aQIxUo0rccqdfcSRP4BEkirbo4S.png)
It’s a popular laser engraver. Many people have it working under Mac and Windoze with cameras and all. This one works fine from the SD card. I had the same issue with an exact model that I had returned. I posted this issue about 6 weeks ago with no solution found and reposted hoping someone might have an answer by now. I’ll try the DTR and see.
The screenshot for device settings is a different device than was shown selected for the full screenshot. Are you working with multiple device profiles?
Can you confirm that GRBL device type is being used?
When you say that the machine works from SD card are you generating the gcode fr LightBurn?
Yes I created profiles by importing the one that Creality provided as well as a manual one created within Lightburn. They’re both GRBL Yes, I use Lightburn to write the gcode file to an SD card that the laser can read. That part works. No luck controlling the laser from Lightburn