HI
how to generate gcode using fill mode without G91(Minus sign) for the X and Y axes???
thank you
You might need to switch between absolute coordinates and current position as start positions.
If the “hobby laser” in your profile uses a “DSP Controller” similar to a Ruida, it doesn’t use G-Code.
Tell us more about why incremental distance mode causes a problem and we can, perhaps, be more helpful.
hi Misken
I am using a trial light burn with Marlin gcode, absolute coords and custom gcode.
also I was trying to modify But the same still using G91 instead of G90..
cccc.gc (38.2 KB)
cccc.lbrn2 (19.5 KB)
I added the g code with project file.
thank you
hi ednisley
I am using a trial light burn with Marlin gcode, absolute coords and custom gcode.
and the controller is offline controller with sd card.
cccc.gc (38.2 KB)
cccc.lbrn2 (19.5 KB)
I added the g code with project file.
thank you
Marlin firmware has some definite peculiarities.
Did you select the Marlin GCode flavor when setting up the Custom GCode device?
LightBurn may generate different G-Code for a pure Marlin device, as opposed to a Marlin flavored Custom GCode device:
Set up a new Marlin device to see if that changes the results.
Hi
I switched to marlin but still the same issue with G91 instead of G90…
MARLIN2.gc (55.7 KB)
MARLIN2.lbrn2 (19.4 KB)
also I attached the new files.
thank you
According to the RepRap doc, G91 has been available since version 1.0.0:
What version is your controller running?
LightBurn always switches to relative coordinates for fill mode, because it generally takes less code.
Why do you need it to run in absolute coordinates?
1 Like
Actually my laser cnc controller is not supporting G91(relative position),and only support g90 (absolute) .also the g code size is not an issue for my controller.
so, what is the solution for this issue? Is it possible to modify the light burn in the new release?
thank you
Install an up-to-date G-Code interpreter.
An ancient Marlin version lacking support for G91 surely has other problems, so there’s no point working around this particular problem.
3 Likes
There are many places in LightBurn that assume a controller supports relative positioning. If you ever use “current position” mode, it ONLY sends relative moves, ever, and if you use “user origin” it sends a single G0 move in absolute coordinates to move to the starting point, then switches to relative moves for the rest of the job.
LightBurn will not function correctly if the board doesn’t support relative moves.
1 Like