Hi There!
I face annoying problems with connecting current Lightburn to my Longer Ray5 20W (ESP32, GRBL driver.
Lightburn is sometime not able to connect the controller.
Kernel Log:
[ +4,078711] usb 5-6.3: new full-speed USB device number 15 using xhci_hcd
[ +0,104335] usb 5-6.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34
[ +0,000003] usb 5-6.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ +0,000002] usb 5-6.3: Product: USB Serial
[ +0,040008] ch341 5-6.3:1.0: ch341-uart converter detected
[ +0,014345] usb 5-6.3: ch341-uart converter now attached to ttyUSB0
The device is ok, communication works for the user.
Directly after switching on the Controller I recognize the misbehaviors:
A. Protocoll Problems:
-
garbage from the controller on the serial line may not read out the ttyUSB0 interface.
=> Controller is not found by LightBurn.
Solution, Read controller Garbage from the line and dump it.
Like close lightburn,
$ cat /dev/ttyUSB0
some biary trash
Ctrl-C
Start lightburn → All OK.
Conclusion: the Serial Protocaoll driver in Lightburn is buggy -
Connection Problem:
After controller disconnects lightburn does not handle the “dead ttyUSB0” line, lightburn keeps the line open and waits forever unsucsessfully.
Conclusion, Device connection handling in lightburn is buggy.
Solution:
After getting an TIMEOUT (coders: use select function and read out error status) close the Interface.
Linux Kernel will recreate ttyUSB0 after controller powered up again.
B. Lightburn hoes not conmnect the controlle via Network, TCP/IP at all.
In documentation this ist meant, it should work. But does not.
It would be great, if this issues would be fixed.