I imported a PNG image which sits at the top of my design and then added some text below. So far I have only been doing tests, but dare not try the final engraving because weird things keep happening… each time I engrave, the layout gets changed… the space between the image and the text changes. One one occasion the first line of text disappeared.
Have you traced your PNG file? If not, you can do so, especially when the image is so simple. (there is no obstacle in mixing text and drawings and images with each other)
When you have arranged your project, you can lock the location of the elements. But it should also work fine without locking the project, I guess that either your material moves a little or your machine has problems with loose pulleys or or belt or the machine is not stable enough in relation to your material you want to process.
If you have any doubts about your fille, please post it here so we can look at it.
ps. it could also be that you engrave too fast and everything shakes, what are your parameters?
This suggests mechanical backlash between the motors and the laser head, probably in the Y axis.
Go through this tuneup / checkout list and verify every part is snug / aligned / moves smoothly:
It’s for Sculpfun lasers, but you’ll recognize the parts and being grindingly methodical should solve the problem.
Tracing the PNG and removing the image file solved all problems. It is now engraving as centred and the layout is not changing. Many thanks!
Sometimes the most complex problems have the simplest solutions.
Lightburn is an amazing tool!
Glad it was not mechanically related.
I would consider the apparent fix more concerning than a mechanical problem.
It seems to point to a problem with LB itself.
If so, the devs may want to have a copy of the original project file to see if it can reproduced, diagnosed, and fixed.
I did preserve that file…
trophy-master.lbrn2 (197.2 KB)
Thank you for reporting this and for saving the file.
When you first connect to the Atomstack S20 Pro the engraver will usually communicate the Firmware Revision Number over to LightBurn through the Console Window. I’d really appreciate the Firmware Revision Number for our testing.
The Second thing I need to know for testing is which operating system you were Running Windows 10, or Windows 11 when you experienced this?
After loading your file on my computer, I am seeing the Image mode set to Stucki. Was this your setting for the image as well? (It could have been my previous setting so I’m attempting to confirm.)
Thanks Again!
Windows 11
Lightburn 1.4.03
[VER: 1.1h.2022070601:]
[OPT:V2,15,128]
It is set to “Stucki” but I didn’t set that so it may be the default setting.
The only thing substantially different between the GCode produced by the original (Stucki default) version and the second (traced image) version is that the original has three G0 travel moves (instead of two).
In both cases, there are G0 moves at the start and the end of the engraving.
The difference is the G0 move between the Filled Text and the Image in the original. It’s replaced by a G1 engrave speed move after the image is traced and replaced by a filled vector shape. I found the G0 with a text search but I had to measure the project to find the 9.6mm Y-Axis (zero power output) move.
G0 would follow the Machine Settings for the acceleration values $120, $121, and speed (Max Rate) $110, $111. Definitions of Machine Settings here: https://github.com/gnea/grbl/blob/master/doc/markdown/settings.md
Any lost motion in the first G0 move will only change the start point. Any lost motion in the last G0 move will position the head of the engraver at a distance from the commanded 0,0 which won’t affect the art at all.
The middle G0 move is the only one that will mess up the art if the Machine Settings are optimistic and lost motion occurs.
The G0 move shouldn’t cause lost motion. The Machine Settings for the speeds and accelerations should be lowered until G0 moves can be repeated accurately.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
