that would be great … that we are simply used to it is always a weak argument
Unfortunately BSL doesn’t give us direct access to the machine - they provided a library that we’re forced to use for the moment, so we don’t have a lot of control over what happens under the hood.
That said, a 145mm square at 500dpi would be 1.4 million pixels, and even if each of those took an entire kilobyte to encode, that would be 1.4gb of data. It seems insane to me that you’d hitting 9GB. Can you post the file you’re trying to run? (or, if you’d prefer it not be public, email it to support@lightburnsoftware.com and include this link: LightBurn v2.0.00-RC5 Release Candidate - #27 by geraldz)
Hi @LightBurn . File attached, this is in the public domain. I’m only seeing 9GB of ram used when I increase the dpi to 1200. Lightburn hits the 9GB and crashes when the job is only 23% built.
Thanks,
Gerald
production 10 woman with cat.lbrn2 (993.9 KB)
I’ve looked at the code and your file, and the parts that are consuming the most memory and taking the most time are in the library provided by BSL, so I don’t know what’s going on. I’ve provided them the breakdown I’ve done, sent them the file, and told them the two functions that appear to be consuming all the memory and time.
If I leave out one of the two functions in their library, it takes about 20 seconds or so to build up the job, and consumes about 25 Gb of memory. If I remove both, it takes about 5 seconds and uses about 2 Gb. Leaving both in, I get about 2% of the way through the job after a minute or two, so it feels to me like something is wrong - it shouldn’t be that slow or that memory hungry. I’ll let you know what I find out.
1 Like
@LightBurn Thanks for looking into this. I’m going to keep my fingers crossed!
Gweike advertises 0.001 “motion accuracy,” whatever that is, with this high-resolution picture of a tiger.
.
Gerald
Unfortunately, in RC6 I still can’t display the last position of the laser. Even when it‘s activated nothing happen.
It must be a GRBL version thing, here at my place with my dsp version of LB, there have been no problems with it.
1 Like
This is the “Repeat Accuracy ±0.001mm” of the galvo mirrors. - Basically, how precise they can position the laser beam.
The more limiting factor in engraving detail will be the diameter of the beam. They don’t show any info about this “spot size” but with a 150mmX150mm lens, I’d expect it to be around 0.04-0.06mm.
A smaller lens will improve this.
Is this with your Xtool S1?
Since this laser is not using standard GRBL and does not respond to the ? command for reporting the MPos, I’m not sure, how easy / possible this is.
Or!: It’s already supported and you only need to set it up by following these instructions:
Yes that is me 
The ? command works, when i type it in the console Lightburn says in wich position the Laser is. Also the Tab where i query the position works. But not the cross.
To be sure: Are you using an Xtool S1?
Did you set it up following Joe’s instructions from the link I sent?
So, the command in the console and the “Get Position” button work.
What is “the cross?”
That adds up!
@Mico it sounds like you need to enter a Laser Offset
@Aaron.F thanks for the explanation
Ja genau, ich habe einen xTool S1. Der Laser ist wie angegeben eingerichtet worden.
Es geht nicht um das Kreuz des Lasers sondern das Kreuz in Lightburn, um die letzte Position des Lasern anzuzeigen. Die Fonktion klappt leider nicht.
Yes, exactly, I have an xTool S1. The laser was set up as described.
It’s not the laser’s cross that’s the issue, but the cross in Lightburn that indicates the last position of the laser. Unfortunately, that function doesn’t work.
