You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A feature that I found very useful in OctoPrint was the ability to override the print time remaining if the GCODE had M73 print times embedded in it from the slicer.
I am currently using a Prusa i3 MK3S with Slic3r PE (PrusaSlicer) as my primary slicer. All of my GCODE files include M73 commands that are used by the Prusa i3 MK3S to update its print time remaining display. While I was using OctoPrint, the print time remaining shown on OctoPrint would be an exact match to the value shown on the 3D printer's display, as both were using the times provided by the M73 command.
Would you consider adding M73 support to AstroPrint? That would make the app and web interface much more useful for planning my workflow, as right now I can not rely on its print time values.
A feature that I found very useful in OctoPrint was the ability to override the print time remaining if the GCODE had M73 print times embedded in it from the slicer.
I am currently using a Prusa i3 MK3S with Slic3r PE (PrusaSlicer) as my primary slicer. All of my GCODE files include M73 commands that are used by the Prusa i3 MK3S to update its print time remaining display. While I was using OctoPrint, the print time remaining shown on OctoPrint would be an exact match to the value shown on the 3D printer's display, as both were using the times provided by the M73 command.
Would you consider adding M73 support to AstroPrint? That would make the app and web interface much more useful for planning my workflow, as right now I can not rely on its print time values.
Here is a link to the OctoPrint plugin that added the M73 feature: https://plugins.octoprint.org/plugins/prusaetaoverride/
The text was updated successfully, but these errors were encountered: