Feature Request: only act on last layer infill #7

Open
opened 2021-12-30 18:05:32 +00:00 by Ghost · 1 comment
Ghost commented 2021-12-30 18:05:32 +00:00 (Migrated from codeberg.org)

Hello,

this is a nifty plugin that will save some energy and time. Thanks!

Stefan from CNC Kitchen claims that inconsistent bed temperatures can lead to Z-banding. https://www.youtube.com/watch?v=9JyydfcOcD0

So by using this plugin, you might get some different looking perimeters during the end of a print.

Thus my idea would be: Instead of using time and percentage, cooldown should start when the print has reached the last layer and the perimeters are complete (assuming the print was sliced perimeters-first, which it usually is). This way, you still get some cooldown advantage, especially on larger surfaces, but it cannot possibly leave marks on the perimeters.

Thanks!

Hello, this is a nifty plugin that will save some energy and time. Thanks! Stefan from CNC Kitchen claims that inconsistent bed temperatures can lead to Z-banding. https://www.youtube.com/watch?v=9JyydfcOcD0 So by using this plugin, you might get some different looking perimeters during the end of a print. Thus my idea would be: Instead of using time and percentage, cooldown should start when the print has reached the last layer and the perimeters are complete (assuming the print was sliced perimeters-first, which it usually is). This way, you still get some cooldown advantage, especially on larger surfaces, but it cannot possibly leave marks on the perimeters. Thanks!
rfinnie commented 2021-12-30 19:20:22 +00:00 (Migrated from codeberg.org)

Nice suggestion, thanks! Unfortunately, I think plugins can only hook into when a Z change occurs, and doesn't know whether that's the last layer or not (or whether things like the finishing move-away Z change is the last layer, etc). I'd love to be proven wrong, and will leave this open if someone can figure out how to implement it.

Nice suggestion, thanks! Unfortunately, I think plugins can only hook into when a Z change occurs, and doesn't know whether that's the last layer or not (or whether things like the finishing move-away Z change is the last layer, etc). I'd love to be proven wrong, and will leave this open if someone can figure out how to implement it.
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#7
No description provided.