If you’re using the GRBL profile instead of the Gerbil profile, that’s why.
For some reason, quite a few people have chosen to use the generic GRBL device profile instead of choosing “Gerbil” when using a Mini Gerbil, and the Gerbil profile enables a few settings that are required for the board to work - the biggest being the DTR signal enable flag. You can turn that on manually in Edit > Device Settings and that will let the board work as expected.
The reason it’s not working with the newer versions is that the toggle wasn’t properly hooked up so all devices actually had the DTR signal on all the time, and Arduino based boards need it off. So it actually works on older versions because of the bug, and now that the bug is fixed, you have to either use the profile that knows your board needs this setting, or set it manually.
When I send a job from my macbook pro, my Ruida laser machine does not respond and I get a message that there is a communication or connection problem with my laser machine. Yes, I can move the head and mark the frame of the work area. The problem only happens when launching the job, the machine does not respond. I have solved it with downgrade to the previous version.
We know the 0.9.20 version works - we’re much more interested in whether the newer 0.9.23 / 0.9.24 versions work. I think the Big Sur specific builds will have camera issues, but the non Big Sur version should work.
Anyone having issues with the current release, please download from the appropriate link above, try it, and post your feedback in this thread with the following info:
What version did you download?
What OS and controller do you have?
Did it work, or fail?
I’ve tested this on all the systems I have, and it has worked for me. This does not address the issues with camera connections on Big Sur, but the Mac (Older) version might work for that.
I also am having issues with builds 0.9.21, 0.9.22, 0.9.23, and the test build 0.9.24 in this thread. All I get is “Waiting for connection…”
I’m using Windows 10 64bit with the latest updates and patches, and the 64bit version of LightBurn.
I’m running on an LPC1768 with the latest version of Marlin, complied from git hub today and the following settings in lightburn:
@rvarone everyone else is falling back to LightBurn v0.9.21 or v0.9.22 and things are working well again.
Since you just built the latest Marlin and no versions of LightBurn are connecting, maybe it is your firmware. So any of the free G-Code sender apps work with your setup or better yet, do you have an earlier version of the firmware which worked so you can validate LightBurn can still connect to that known working firmware?
Sorry I forgot to include here that versions 0.9.20 and below work fine for me, my issues started with 0.9.21, I had another thread and Rick told me to post here instead.
This is likely because you’re using the GRBL device profile in LightBurn instead of using the Gerbil profile. The Gerbil profile knows that your machine needs the “Enable DTR signal” button set, and the GRBL profile does not set that for you.
Instead of using LaserGRBL to process the image, use LightBurn, and have LightBurn save the GCode, then send that GCode from LaserGRBL. If the issue is serial management, then this would work. If the issue is NOT serial management, then LaserGRBL will produce the same jerkiness.
What is most likely happening is that you have not processed the image with the same options, and LaserGRBL is producing much smaller / less dense GCode, and is able to keep up with the 300 mm/sec rate you have asked for, which is quite high for a GCode system.
I have installed the MacOS (Big Sur) version of 0.9.24, and have not encountered issues I was previously… I could do a simple line on 9.23, but any more complex, it would stop part-way through, or not go at all. I have done some cuts/engraves now without any issues with 9.24. I have the KT332N controller (detected as 6445)
