¶ 🕛 Mismatched Print Time Prediction
¶ 🔧 Root cause
After an optimization run, the slicer preview updates to show the new, optimized print time. This is calculated from the optimised print speeds written into your G-code.
However, when you load the optimised G-code into your printer, the printer’s display will still show the original (non-optimized) time estimate.
This happens because the printer reads the time estimate from a comment line embedded in the original G-code, which our optimizer does not yet overwrite. At present the printer will display the old, original estimate even though the print time has changed.
→
Original time unchanged comment → Read and displayed by the printer
¶ ✅ Workarounds / Best Practices
- Rely on the slicer time estimate in the slicer as the most accurate prediction of the print duration of your optimized job.
¶ ℹ️ Visualisation
- Original print time computed within the slicer using original speeds in the G-code:
→
Original speeds in G-code → Slicer-computed print time from original speeds
- Helio changes speeds and new optimised print time is calculated:
→
Optimised print speeds → Optimised slicer-computed print time from new speeds