Troubles with text and filling etc

hi all i have a sainsmart prover 3018 with sainsmart 5.5w laser

haveing issues making text when ever i write something to burn the text is missing like a 0 will look like a horse shoe sign

soemtimes when i use a different font and the line feature it will burn correctly but cannot find a font that will do it in fill mode

also see photo attached we brought this board off etsy and my wife wants to do the text like this how can we make this kind of text is this a fill setting or is it standard font really quite confused

further to my text burning issue
i am trying to burn a simple fill text as you can see on the pic its focusing on the “o” but the laser goes the full length of the word and missing everything out but this part as you can see in the finished product how much is missing out
so i have just tried to do image tracing to see if it was something i am doing but now its just burning too high on every one i do real heartache

not sure if these details will help but

running at 550 speed and 40 power (40 is the minimum my laser will burn at )

I have the same engraver - 5.5W and all.

What units of speed is the 550 in? in/min? mm/min?

550 mm/min is a good speed for me.

hi mate thanks for reply

ill start using it at this speed i normally use about 250 for lines but fill is really confusing me its either burning or missing test is there a chance you can show me a example of text and what speed/poer you used ?

im pretty sure its something im doing wrong

Happy to help where I can.

I can get laser effect at 20% (and lower) on mine - I think I know what’s going on. Since your machine is also a CNC we should check the Device settings.

Go to Window in the top bar. Make sure Console has a check mark next to it. Click over to that window enter $$. it will spit out all the Device settings. Copy and paste that into a response here.

Click Edit in the top bar and whip almost all the way down to Device settings (Wrench crossing Screwdriver icon) Click that and capture the image - it’ll look like this except the bright red arrow.

if you can’t grab that image just let me know what that number is (as well).

Does not $30 have to be equal to ‘S-value max’…?


Yes… that one bit me a few months back… did it bite you too? :smiley:

No I read the instructions when I installed Lightburn, but found it odd the software didn’t advise you of the issue.

There must be some reason for them not to advise of a mismatch…

I’ve just see it causing problems here multiple times. So many times, it’s configuration…

Good luck


we do see it a lot. and there seem to be two standards the 8 bit word 0-255 and the GRBL 1.1 (guessing) time based 0-1000.

Perhaps I’ll can some of this thinking and put it into an unofficial thread. I don’t want to derail or sideline the discovery process here.

I’d guess it’s just ratios.

I would guess that Lightburn only cares when it’s generating code for the specific controller.

It could apply that ratio to an 8 bit or a Ruida or …?

I have no idea what the pwm steps on my Ruida actually are…

I wonder if there were any changes to the code with the proliferation of these 32 bit grbl machines that can handle a 16 bit pwm range.

How much resolution do we need or can really use. I can see that 256 steps is probably not as useful, but how useful is the 65,535 steps from 0 to max?

If it’s controlled like the Ruida, where the power can be varied and the laser can use that correctly, the greater the better. But I’m sure at some point, it goes the other way.

The tube needs to respond within the ‘period’ of the pwm…


The value is auto-populated if LightBurn detects the machine during “Find my controller”. However, if you setup the machine manually no validation is done at creation time or subsequent runs.

Might be something nice to add in a Troubleshooting wizard or something.

I’m sure the limiting factor now is the laser’s resolution in its ability to resolve and respond to various levels. I see value in having as many levels as can actually be reliably controlled. I suspect that resolution is well below 65,535 for any diode laser today and probably well covered within 1000 levels. We just need to identify a material or sensor sensitive enough to test this on.

Same issue with the tubes response time.

You really need something that can detect the laser beam, for an ‘end’ point in time. Preferably something that won’t be a one shot device.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.