Print completion threshold stuck at 90% #3

Closed
opened 2021-10-24 22:37:48 +00:00 by Ghost · 7 comments
Ghost commented 2021-10-24 22:37:48 +00:00 (Migrated from codeberg.org)

I have Print completion threshold set to 75% and it shows in settings but the bed never shuts off before the default 90%

I have Print completion threshold set to 75% and it shows in settings but the bed never shuts off before the default 90%
rfinnie commented 2021-10-26 21:11:06 +00:00 (Migrated from codeberg.org)

Could you attach a Systeminfo Bundle from after the print completes? Thanks.

https://community.octoprint.org/t/what-is-a-systeminfo-bundle-and-how-can-i-obtain-one/29887

Could you attach a Systeminfo Bundle from after the print completes? Thanks. https://community.octoprint.org/t/what-is-a-systeminfo-bundle-and-how-can-i-obtain-one/29887
rfinnie commented 2021-10-26 23:16:21 +00:00 (Migrated from codeberg.org)

Also, I've released version 0.1.3 with more debug logging. Please upgrade, and do the following before trying again and submitting the Systeminfo Bundle, thanks.

You will also need to enable debugging on the plugin.
This may be done through the Settings > OctoPrint > Logging > Logging Levels section.
Select the "octoprint.plugins.bedcooldown" Name, and make sure Level is "DEBUG".
Save, then restart OctoPrint.

Also, I've released version 0.1.3 with more debug logging. Please upgrade, and do the following before trying again and submitting the Systeminfo Bundle, thanks. > You will also need to [enable debugging on the plugin](https://docs.octoprint.org/en/master/configuration/logging_yaml.html). > This may be done through the *Settings* > *OctoPrint* > *Logging* > *Logging Levels* section. > Select the "octoprint.plugins.bedcooldown" Name, and make sure Level is "DEBUG". > Save, then restart OctoPrint.
Ghost commented 2021-10-27 16:28:25 +00:00 (Migrated from codeberg.org)

octoprint-systeminfo-20211027172703.zip

Here is the system bundle. I updated the plugin and enabled debugging.

[octoprint-systeminfo-20211027172703.zip](https://github.com/rfinnie/OctoPrint-BedCooldown/files/7427824/octoprint-systeminfo-20211027172703.zip) Here is the system bundle. I updated the plugin and enabled debugging.
rfinnie commented 2021-10-28 05:26:50 +00:00 (Migrated from codeberg.org)

Thanks. It is indeed triggering at >= 75% and <= 300s, but that's 75% of the GCODE which happened later than 75% of the time. I should be able to add an option to track against percentage of estimated time instead of GCODE.

Thanks. It is indeed triggering at >= 75% and <= 300s, but that's 75% of the GCODE which happened later than 75% of the time. I should be able to add an option to track against percentage of estimated time instead of GCODE.
Ghost commented 2021-10-28 15:20:16 +00:00 (Migrated from codeberg.org)

Oh that makes sense. That option would be nice if you're able to do it.
Thanks for looking into it.

On Thu, Oct 28, 2021 at 1:27 AM Ryan Finnie @.***>
wrote:

Thanks. It is indeed triggering at >= 75% and <= 300s, but that's 75% of
the GCODE which happened later than 75% of the time. I should be able to
add an option to track against percentage of estimated time instead of
GCODE.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rfinnie/OctoPrint-BedCooldown/issues/3#issuecomment-953513971,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGWDK6SN7I5WEVR2VDK3AWLUJDNKJANCNFSM5GT544UQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Oh that makes sense. That option would be nice if you're able to do it. Thanks for looking into it. On Thu, Oct 28, 2021 at 1:27 AM Ryan Finnie ***@***.***> wrote: > Thanks. It is indeed triggering at >= 75% and <= 300s, but that's 75% of > the GCODE which happened later than 75% of the time. I should be able to > add an option to track against percentage of estimated time instead of > GCODE. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/rfinnie/OctoPrint-BedCooldown/issues/3#issuecomment-953513971>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGWDK6SN7I5WEVR2VDK3AWLUJDNKJANCNFSM5GT544UQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > >
rfinnie commented 2021-10-28 16:41:03 +00:00 (Migrated from codeberg.org)

v0.2.0 released, and changes the default behavior to time-based percentage, so you shouldn't need to do anything but upgrade. Thanks for the report!

v0.2.0 released, and changes the default behavior to time-based percentage, so you shouldn't need to do anything but upgrade. Thanks for the report!
Ghost commented 2021-10-28 17:34:25 +00:00 (Migrated from codeberg.org)

Cool! Doing a long print at the moment but will definitely check it out when its finished. Thanks!

Cool! Doing a long print at the moment but will definitely check it out when its finished. Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rfinnie/OctoPrint-BedCooldown#3
No description provided.