Preview Time not accurate ( already did "Read from controller" )

Hello,
pretty new to the Lightburn, I got it like 2-3 months ago but worked with it like 2-3 days. Worked on a pretty big project, it said it would work for like 3 hours, but in reality it worked for about 5-6 hours.

I looked for it on google and it brought me here, I found some articles but every one of them says to click on “Read from controller” and I did that but no luck.

The problem you have many times is the “max” speed in the controller is rarelly the max speed it can engrave at.

Therefore, Lightburn will read the controller data, acceleration and speed
See the engrave speed you selected and do its best to calculate - estimate - engrave times

If however, your controller bogs down - which they do image engraving - Lightburn has no way to estimate this.

I observed the same issue. non-image cuts and burns are almost dead on in the display. Images are typically 2x the displayed time in the Preview. Simple math to determine how many cups of coffee I will get to drink.

This has a lot to do on the ability of GRBL firmware and the controllers themselfs to parse all the data sent by Lightburn.
Gcode cluster features helps hugelly but only a few brands support it
ORTUR/AlgoLaser that i am aware, up to 30-40% improvements on speed

That would complicate my math. I will stick with 2x. :joy:

3 Likes

I don’t know how to tell for myself if it’s supported, but my Ikier K1 seems quite a bit faster with clustering enabled. I would ask their support team but I think it would be easier to get a timely and accurate answer from my cat.

If it doesnt support it you get an error 24 a few seconds into the raster
So if it doesnt, its enabled
You can “HEAR” the difference actually

LOL
Let me ask my contacts

Definitely not getting any errors.

I haven’t tried it with a true raster image but a fill layer definitely runs faster and smoother. I don’t really do all that many raster jobs, but I do run a lot of EXTREMELY complex filled vectors. Basically dithered images but all vector.

Gcode cluster only really works on raster Gcode
You could do a simple test
Open a image, grayscale, 20000mm/min - 1% power(no point wasting material)

Gcode cluster enable
Run
It will either run or… Error24 in a few seconds in

Massive failure. Clustering throws a bunch of “g-code not supported” errors on a greyscale image. No errors on a vector layer. I guess that means it’s not supported. Oh well.

It definitely works on the Algo, tho. I do run greyscale images on that machine and have clustering enabled.

Thank you for the info!

1 Like

Yeah is fun to put both machines running the same. you can literally hear the difference

When I click on “read from controller” it sets the max speed to 83.3 mm/sec which is 4998 mm/min which obviously is not the speed of my controller. Am I correct with that ?

Type in console $$
Press enter
Copy/paste the full output here

or if you want to be sure you are on defaults
$RST=*
press enter
$i
Press enter
$$
Press enter
Copy/paste here the full output

1 Like

I am 100% sure that my controller will not work with Gcode clustering haha.

yeah! Sorry about that
me and @cggorman went on a WIDE tangent! lol

1 Like
$$
$0=10
$1=250
$2=0
$3=6
$4=0
$5=0
$6=0
$10=1
$11=0.010
$12=0.002
$13=0
$20=0
$21=1
$22=1
$23=3
$24=25.000
$25=500.000
$26=250
$27=2.000
$30=1000
$31=0
$32=0
$38=10
$39=0
$100=79.365
$101=80.645
$102=800.000
$110=5000.000
$111=5000.000
$112=100.000
$120=500.000
$121=500.000
$122=200.000
$130=500.000
$131=500.000
$132=200.000
ok

well your max speed is in fact 5000mm/min
You did not reset though did you because your steps per mm are a bit wonky 79.365 + 80.645
Did you run a calibration?

here’s with the reset

$$
$0=10
$1=25
$2=0
$3=6
$4=0
$5=0
$6=0
$10=1
$11=0.010
$12=0.002
$13=0
$20=0
$21=1
$22=1
$23=7
$24=25.000
$25=500.000
$26=250
$27=2.000
$30=1000
$31=0
$32=0
$38=10
$39=1
$100=800.000
$101=800.000
$102=800.000
$110=2000.000
$111=2000.000
$112=100.000
$120=20.000
$121=20.000
$122=20.000
$130=500.000
$131=500.000
$132=200.000
ok

Right so you have a custom config

Glad we took the before and After
Notice $1, $23, $39 $100 $101 $110 $111 $20 $121 $122

I would set your $100 101 to 80
And your max speed to 10000(you wont be able to get to that though)

Your accelerations are a bit low too $120/121
What type of machine you running?

How do I change that tho ? Sorry, pretty newbie on that stuff.

Diode laser 5W.