I made a little test today to see how the laser could react to some settings. Picture
I loaded the file on the USBstick and uploaded the file.
Estimated run time 1h27 min.
It took 4h37 min !!!
Is this a Luban problem ? Should I rather write in the Luban topic section ?
Makes sense to me. But luban and the firmware must each have a algorithm to estimate job time (probably based on the linear distance of the tool path and the running speed. With some other factors thrown in?) So it doesn’t supprised me that predicted time and actual time are different. But as I read your post @xchrisd it sounds like your saying the predicted time in Luban is different them the predicted time in the controller? Why would snapmaker use different algorithms?
I have yet to have the estimated time match the actual print time. I’ve only used the laser module so far. I printed a picture that was estimated at 3 hours 26 minutes. It actually took 9 hours 18 minutes. I had to pause it at 7 hrs as I didn’t want it running overnight while I was sleeping, resumed in the morning just fine. Even short prints, on the order of less than 2 minutes, take longer than the estimate.
I have no idea how it calculates the print time, but somewhere there must be an error in the formulas.
I now assume twice the print time it says, even three times for longer prints.
Thanks xchrisd ! Yes i think i get it…
Throughout other tests i have been able to notice that the calculated time on the controller corresponds to the runtime of the first layer (in a multi-layer file).
From then on the settings make the difference of how many extra hours it goes…
Not for run time.
Not for ability to cut.
Technically it can make a difference for which safety glasses (and windows) are compatible with it. I wouldn’t want to have glasses that didn’t cover both though just to be safe.