This is definitely a controller crash.
a) Are you running via USB serial or Wifi?
b) at 1% power, being that the laser won’t burn or be dangerous, would you have any chance to move the laser elsewhere entirely? This would remove the possibility of environmental emf fields.
If you read through all my messages that I put on here you will find that grbl runs my machine just fine and I posted pictures. For some reason laser burn only wants to do wire frame. Anything that’s detailed it won’t do. It just kicks out and resets and if it was my machine or the power cord it wouldn’t be able to do this print. This is 250 mm by 250 mm and grbl is printing it perfectly
I’m sorry for the late reply. They limited me on messages and I had to wait 5 hours before I could comment. I’m not sure why they do that on a help group
Just a side note: it’s called LaserGRBL and that’s a fundamental difference to grbl. grbl is the firmware type that’s in your laser. People here understood what you meant, but this could lead to confusion.
Show the settings you used for both setups. Screenshots, not manually written. Sometimes the culprit lies in a setting that’s not obvious.
Both apps I ran same setting same speed and same temp so there is now reason I also have put a lot of pics up, thanks for the lesson on GRBL but you and everyone else know what I meant
Yes even Lightburn uses GRBL format from CNC but it was clear I was talking about the app. With that said I will be uninstalling Lightburn and installing an older model of Lightburn … Thanks for the help
My post wasn’t meant to be offensive. But LB has many more options to set than LaserGRBL and even if the settings look the same, you might have enabled an option that changes the output.
LaserGRBL and LB create exact the same gcode when using exact the same settings. So there is no chance that one tool will have a different result / behavior of the laser. You could export both gcode files and compare them or upload them for us to compare them.
In your pictures, I don’t see any setting, only results.
10478061.gcode (2.2 MB)
OK here is the gcode that you requested. I uninstalled Lightburn reinstalled older version 1.6.03 I ran an image and Lightburn ran 6 seconds and stopped twice I downloded gcode from Lightburn ran it on LASERGRBL and it printed just fine
On a first glance, there is nothing suspicious in this file, except maybe that the coordinate system is somewhat in the middle of the job instead of a corner. I’d suggest starting at “current position” and not “user origin”, which is often an arbitrary position if not set explicitly. Though, this should not cause a stop (if there is no error complaining about a specific line of gcode).
I guess you always get the “connection lost” error? And you are using USB connection? In device settings, did you enable DTR signal and used 115200 as baud rate?
Then I’m mostly out of ideas, I think. I only can tell that the serial connection of LightBurn has always been much more unstable compared to LaserGRBL. I had some support cases where mainboards / firmwares only worked in LB after having initialized them using LaserGRBL. LaserGRBL always connected, while LB was picky. So I can imagine a bug at LB here.
I am connected with a cable and when I was on Wi-Fi I was at that baud rate. So I guess you were out of ideas just like I am
And I don’t think it matters where the job starts. Whether it’s in the corner which I’m tired of it crashing into corners, that’s why I’m in the middle of the bed, but it shouldn’t matter where you start the job. That should have no effect on the software that’s not working versus the software that is working
That really depends on the configuration. In LaserGRBL, all jobs start at “current position”, basically, where the head is. In LightBurn, you can configure various starting positions and this can lead to the laser stopping because you want to drive it outside the available space. But in that case, the laser gives a warning that the machine limits would be void, and it doesn’t start at all (you need a laser with limit switches and enabled soft limits in this case). I think you didn’t get that warning.
So at USB, you are at that baud rate, too?
It’s challenging to diagnose from the distance, so maybe someone else has additional ideas.
You still could post your settings , since you didn’t do that yet. See here what information would help us more:
si sous lb vos parametres de taille de travail sont bon partout,essaye de graver le meme projet avec moins de puissance,il se peut que l’alimentation d’origine (mayon faible car souvent de mauvaise qualité) ne puis fournir suffisament d epuissance pendant un temps assé long.
Not sure where the translator is but it would help if you spoke English
My problem is solved. I had to delete everything out of my prefs file and it reset completely. Lightburn now it works!
Yay! to that.
Win 11 update may have messed with the USB ports or settings, so try reinstalling the USB drivers for LB and see if that helps any.
Apparently you’re not reading through the entire topic. I got the problem fixed
Welcome to the LightBurn Forum, friend. When you get a reply, it is most likely because they read your message and have something to offer. Folks are not arguing or ignoring what you have shared. You believe this is a LightBurn issue. Everyone is trying to understand the data and answers you provide, as we can not “see” these things for ourselves. Please play nice.
Stuff occurs, production and QA/QC can get out of sync and the quality of what we all get in the box can suffer. Things fail, it happens, no matter how young or old the thing is.
@gilaraujo is great at assisting and has a ton of experience (including working for several laser manufactures in China) with equipment just like yours. You are in good hands with Gil and all our regulars.
Not sure what others use, but I use Google Translate. We have members all over the world, so some may not speak English. Even English to English has translation issues. I had to Google what a “GRUB” screw was. That is what they call SET screws in England.
The beauty of today’s technology is that we can talk to nearly anyone in the world and communicate technical issues. We all have the same problems. Fortunately, communication is not one of them.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.