Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial printTimeLeft update takes forever on long prints #105

Open
nickrbogdanov opened this issue Jun 11, 2021 · 2 comments
Open

Initial printTimeLeft update takes forever on long prints #105

nickrbogdanov opened this issue Jun 11, 2021 · 2 comments

Comments

@nickrbogdanov
Copy link

When I start a long (8hr) print, I see a couple of octoPrint/progress/printing messages and one octoPrint/event/PrintStarted message on MQTT. In the former messages, printTimeLeft is either 0 or null. I don't see a valid printTimeLeft field on MQTT until the progress bar hits 1%, which takes several minutes on a long print job. It would be nice if this field got populated and sent out over MQTT as soon as it is known to OctoPrint, so that anything that wants to display the estimated time (e.g. dashboards) could be updated sooner.

@bglnelissen
Copy link

bglnelissen commented Feb 24, 2022

I have the same issue. You can use DisplayLayerProgress_feedrateChanged or DisplayLayerProgress_heightChanged for progress.

Example

topic: "octoPrint/event/DisplayLayerProgress_heightChanged"

Which contains quite a lot of info as well as the printTimeLeft.

payload: "{"updateReason": "heightChanged", "totalLayer": "666", "currentLayer": "316", "lastLayerDuration": "0h:00m:22s", "lastLayerDurationInSeconds": 22, "averageLayerDuration": "0h:00m:22s", "averageLayerDurationInSeconds": 22, "currentHeight": "47.85", "currentHeightFormatted": "47.9", "totalHeight": "100.69999694824219", "totalHeightFormatted": "100.7", "feedrate": "7200", "feedrateG0": "7200", "feedrateG1": "2400", "fanspeed": "100%", "progress": "66", "m73progress": "", "printTimeLeft": "1h9m", "printTimeLeftInSeconds": 4173, "printerState": "printing", "estimatedEndTime": "13:23", "estimatedChangedFilamentTime": "-", "changeFilamentTimeLeft": "-", "changeFilamentTimeLeftInSeconds": 0, "changeFilamentCount": 0, "currentFilename": "model.gcode", "_event": "DisplayLayerProgress_heightChanged", "_timestamp": 1645701225}"

@nickrbogdanov
Copy link
Author

I have the same issue. You can use DisplayLayerProgress_feedrateChanged or DisplayLayerProgress_heightChanged for progress.

So you're using this additional plugin to generate those events as the corresponding Gcode commands are fed to the printer, then using OctoPrint-MQTT to send the events to clients?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants