inactive time should be used during filament changes

[netpipe]

if the printer runs out of filament it should cool down using inactive time in eeprom. mine stayed on the filament load screen at full temperature for over 10 min.

[luc-github]

This is good idea for extruder - what about the bed ?

[netpipe]

for the hotbed maybe drop the temp to 40 deg C and beep periodically so PLA parts dont fall off or just disable it and beep. if you wanted to set that longer maybe 30 min for the hotbed and 5 min for the hotend ?

[luc-github]

well this will not work for ABS a little temperature change and ABS will not like

[netpipe]

most good ABS options dont use heat on the bed anyway. the stickers , painters tape etc...

[luc-github]

No heat bed for ABS, really ? I use 110 degres even with 3M glue

[luc-github]

@tecan Did you pushed this to repetier main FW ?

[netpipe]

i dont typically follow what the main repo does, is that were alot of the new changes come from still ?

[luc-github]

Yes I try to stick to repetier main FW as easier to maintain - unless it is Davinci specific

[netpipe]

looking in void Printer::defaultLoopActions() i see some isMenuMode(MENU_MODE_SD_PAUSED) maybe all we have to do is add in the filament change menu

[luc-github]

you mean to count pause time as idle time ?

[luc-github]

I need to read the code again but - I am pretty sure that when just heating and waiting, like for preheat and wait temperature stable - and not printing the inactivity counter is not take in account. same if you are in pause and you cut temperature for any reason so your extruders are cold, then you also heat again and wait temperature is stable, if for example inactivity time is 1 min and we still are heating what will happen ? I think implementation is not that simple - need to take in account all user cases - I am pretty sure also the flag MENU_MODE_PRINTING is enabled when heating so check only MENU_MODE_SD_PAUSED is not enough. Also need to allow user to not use this feature is also important

I am not against - it is good idea but not that simple IMHO if you consider all possible user cases

[stale[bot]]

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[netpipe]

is this still fire hazard ?

[luc-github]

Just a bot that automatically check issues

[stale[bot]]

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[netpipe]

bump

[stale[bot]]

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[netpipe]

bump.... this is annoying and very important

[luc-github]

what is repetier answer ? may need a bump there too ^_^

[stale[bot]]

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[netpipe]

i might have a look at this issue next month, no response from repetier yet.

[luc-github]

Yes may be because issue from custom FW and not pure repetier I had a quick look and I think need to setup specific trigger for this - I add a flag to keep issue open as I have have really no time now

[netpipe]

hmmm, winter is coming. might get to it then, it is a fire hazard so i'de mark this as critical.