forgot to send a screenshot of the preview:
I keep testing and the results are similar but different.
Did a new tracing of my signature.
Created a FILL for the shadow and a LINE for the signature itself.
Look at the burning sample. The top burn was burning both, FILL and LINE, the bottom burn was burning ONLY the LINE.
We can see a new duplication of the FILL, shadow, but this time is horizontal.
My guess is there is a problem or either on the Tracing routine, or the FILL mode, or on both.
This is NOT a problem with the Xtool D1, as the error can be different, after a new tracing.
Here a copy of the photo of the burning and a copy of the LBrm2 file.
JV signature 2.lbrn2 (115.0 KB)
Not following how you came to this conclusion based on the evidence.
What you’re seeing are not duplicates. They are misaligned components of the same design almost certainly caused by missing steps. And again, most likely from loose belts. Did you review the belt tension?
The other thing I noticed was that your speeds on the line and and engraving are quite fast, especially the line. This will cause any mechanical issues to be more pronounced.
Try dramatically slowing down your line and fill speeds. If things improve this reinforces that that the issue is from skipping.
no way… can I speak with your supervisor?
Not sure that would be a benefit as my wife doesn’t know much about lasers or LightBurn.
But perhaps one of the other fine folks on this forum would be willing to help you going forward though. I suggest you provide an update on what you’ve tried of the previous guidance as that will help move things forward.
I thought I was getting comments from LightBurn tech support… didn’t know you were just another end user.
I have some experience with software development (system analyst developing SQL databases for 30+ years), and mechanical understanding of the basics (change my own transmission some years ago), so I have some base to say what I’m saying.
So on the XTool website it mentions control software: laserbox. And also says Lightburn But I didn’t see any other pages describing it. If Lightburn has issues controlling this machine are you able to try laserbox?
What berainlb is saying is that we aren’t aware of any Lightburn settings that would cause your problem.
@jvismara I just ran both files you provided above on my laser here with the only changes being made were to speed and power to be appropriate for my laser see results here:
So I think there could be a couple things happening here. The first and I think the most likely is you have “Scanning Offset” enabled in device settings. This would explain the double image you are seeing on the scan and why its tracking with the direction of your scan. You probably do not need this at all with the xtool. Learn more here: Scanning Offset Adjustment - LightBurn Software Documentation
Next, your acceleration may be too high causing missed steps, but since its tracking with the whole file and not erratic I do not think it is that.
ALSO - the dev’s and support staff are here. We are few and you are many. We read the ENTIRE forum. If we don’t answer your question in a day or two feel free to bump the post or send an email to support@lightburnsoftware.com. The end users here are very knowledgeable and are often able to solve problems before we even see them.
3 Likes
I have posted a problem and several updates on a burning error, and have had ONLY answers from a person identified as berainlb that doesn’t really understand the problem, and offers weird recommendations.
Here is the link to my post:
Thanks
As @JoeSpanier identifies, we are here along with a bunch of very smart and capable members offering to assist you. Please let us know how you progress and we can continue from there. 
looks like the default scanning offset in the xtool config for 6000mm/min is 0.15
If somehow that got changed to 15 for example, this is what the scan would create. Looks a lot like your picture.
thanks Joe… my scanning offset was a recommendation from a page in LightBurn or Xtool, don’t remember now, but its something worth tweaking/thinking.
this problem appeared ONLY after I tried FILL with my own TRACED images… it does not happen with any other figure/drawing before.
it had printed with double images vertically once, and when I traced it again, it printed horizontally double images, my guess is that it is a software related problem.
the fact you can test it successfully makes the case more complicated… but MANY thanks for the input.
just a theory…
start by checking and making sure your scanning offset is 0.15 and not 15.0.
the fact that it moves with the scanning direction tells it all.
The first file you uploaded had the scan direction at 90deg in the cut settings. The second it is at 0deg. That is why one is shifted horizontally and the other is vertically.
This isn’t a software or a machine issue, its a config/settings issue.
thanks for the time reading and the explanation 
2 Likes
yes, it was/is 0.15 for full speed.
as for your advice, I’ll keep testing my settings, thanks.
I was un-installing and re-installing LightBurn to see if that makes a difference… old way to double checking digital issues.
again thanks for taking the time reading and printing… that’s HUGE feedback.
I just realized that I traced those images in my main machine, then, printed / burned them from my MacBook by the laser…
even though both have the same configuration, something might be different, that is triggering the offset.
THANKS Joe…
I followed the completely zero tolerance option… meaning, completely un-installed LightBurn in both machines (including all configurations) and re-installed in ONE machine first, imported the Xtool D1 Device configuration I’ve downloaded before from LightBurn or Xtool webiste, and then, exported that machine configuration to the other one (main).
Guess what… now all is working as expected.
As you suggested, was probably a setting/configuration, or maybe one of the machines got a not 100% code in it, that somehow got repaired in the process.
Old way of doing things… not the most noble, I’d say.
PS the only difference in the configuration that I could see/find, was the code: “M106 S0” in the GCode tab, under the Start GCode box, the rest looked identical.
glad its working now