keyz182
commented
6 years ago It was a fairly quickly thrown together app, so for estimates, I passed the gcode to add up all exposure/pause times, but just quickly estimated move time by timing a few moves on the printer. Not accurate, but better than nothing. I've been meaning to augment the gcode parsing to read in move distance, along with acceleration to get the exact time for each line, so should remain accurate even if someone has tweaked the gcode manually. Hopefully I'll have some time this month, I'll have a think about whether to go with your equation, or go all out gcode parsing.
Thanks!
I love your app (v1.1.0), but I find that the times it estimates are vastly different to the actual print times I achieve from my SparkMaker. For a print I did a few days ago, your app estimated a print time of 9h:7m:16s. However, the actual print took around 14hrs.
I'm not sure how you are calculating the time, but I have produced a Google Spreadsheet which estimates for the same print, 13h:58:20s, which I think is much closer to the reality.
My spreadsheet is based on the following inputs, which are taken from the Sparkmaker Slicer and can be varied for various resins. D - Layer Height (mm) E - Exposure time per layer (s) G - Bottom Layer Exposure Time (s) H - Lift Distance (mm) I - Lift Speed (mm/min) J - Decline Speed (mm/min) L - Number of Layers
Then my time (in spreadsheet time format of days) is calculated from ((((60H(I+J)/(IJ)+E)(L-1)))+G)/(246060)
Hope this helps, keep up the good work.
Regards