I am having an issue with Lightburn and the GRBL output to generate a circle, curve, or any item that requires a form of a curve in my cut.
If a square or any item containing straight lines is generated and output to the GBRL laser cuts correctly.
If a circle or any item containing curved lines is generated and output to the GBRL laser, the laser moves to the start position, starts the circle or curved item for a split second then stops and I get this error code
Starting stream
Layer C02
error:20
Unsupported or invalid g-code command found in block.
On or near line 2:
Job halted
Stream completed in 0:00
ok
ok
ok
ok
ok
Any idea as to what could be causing this error and stopping the process ?
This is the file that was generated for the shape of a circle that stops and generates the error code. This would be the same for any shape that would have a curve to it. as far as the curved shape it does not matter if it is drawn in lightburn or imported from a dxf file, the process will stop and the error code indicated.
I suspect the curve aspect of this is a red herring. LightBurn doesn’t generate arcs. So both curves and lines are straight segments, only varying in size.
I don’t see anything significantly different in the gcode content itself so I suspect this is a communication issue.
Try applying the “Enable DTR” fix that @ednisley listed. However, I would expect that to be an always connecting or not connecting type of an issue.
A few other things to look at:
Check baud rate in Edit->Device Settings. What is this set to? Try going back and forth between 921600 and 115200
Can you confirm that you have defined a laser spindle and have it active?
That’s what I’d expect, too, but the thread suggested initial communications work (just barely) well enough to get started, then it chops out chunks of G-Code as things get underway. That would explain the “invalid g-code” part of the error, at least.
Yeah. This is why I’m thinking communication error. The “working” vs “non-working” g-code is not significantly different in terms of content. So implies an issue with volume or something else.
DTR was tried on and off with no change
I will try switching the baud rate
As far as a laser, I will be using a NEJE A40640 that I was using with my previous Rambo controller.
I do not have the laser connected as I was just trying to get the X, Y and Z working correctly prior to firing up the laser.
After I try switching the baud rates I will connect up the laser and try it then
I was actually referring to within the controller. Has a laser been defined and set as active? If not, it’s possible that the controller is not in Laser mode.
I did not get to try hoking up the laser yet
My question is why would the laser matter if the object with only straight lines outputs correctly and the objects with curves do not ?
Maybe I am missing something here
By the way, I appreciate all of the help you have been providing, your help is priceless !
The definition of the laser in the controller is an independent activity to electrically connecting the laser to the controller. I’m referring to the former.
It wouldn’t necessarily. I’m theorizing that this has nothing to do with straight vs curved from a processing perspective which I still suspect is a communication issue. However, I’m leaving it open that there may be multiple things at play with different parts of the erroring from communication and another from a configuration issue.