[FR] Showing the "real" remaining time #355
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Would it be possible to parse the line
;TIME:<print time in seconds>
from a gcode file that was exported with Cura and display the remaining time (from first command in print, so line;LAYER:0
) somewhere in the UI?Feature Workflow
;TIME:<print time in seconds>
line;LAYER:0
is reached, the printer starts a timer and counts down the time and displays it in the UIAdditional Information
I guess this will be hard, as the UI is not customizable, if I remember correctly, but would be immensely helpful.
The estimation that Cura makes is quite accurate for me (ignoring heat-up times) and would be super helpful to see instead of e.g. the progress in % through the file. Maybe other slicers output similar lines or you could just make it a feature when Cura is used?
Additionally, it would be possible to create custom lines that can be parsed in the start and end gcode, by using the replacement patterns that slicers support (see here e.g. for Cura).
This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
Still relevant. Please do not close.
Hi @PapeCoding ,
I didn't have the opportunity to further develop the firmware for some time. I'm looking into this, but to be honest this is a relatively low priority as there is still one critical bug and one feature that needs to be fixed.
But I'll remember that and put it in my backlog, ok?
You can either close this ticket or leave it open. But I wrote it down.
best regards.,
Olli
This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.