[BUG] Stuck filament detection triggered at low temp during startup

[rcmaniac25]

Printer model

MK4S

Firmware version

6.1.4

Upgrades and modifications

MMU3

Printing from...

PrusaLink

Describe the bug

I sliced up a simple print on PrusaSlicer and sent it via PrusaLink to the printer with "upload and print". After a moment, the printer started heating. When the nozzle got to temp, the MMU3 loaded the filament. The filament seemed to load fine, though a couple clicks were heard... this has happened and then it prints without issue.

With the filament loaded, the nozzle dropped in temp to 170C so it can probe. At this point, I looked away. I don't know if it got to homing + nozzle cleaning, or if it finished that step. I heard a noise and looked back and saw the screen said "stuck filament detected" and asked me to unload. I clicked yes, and it unloaded filament at 170C. It then paused a moment before reloading filament at 170C. It asked if the color was correct (it was), did a purge at 170C. Then proceeded to do mesh bed leveling.

The print has been running fine since.

How to reproduce

I'm unsure how to reproduce this

Expected behavior

Stuck filament detection doesn't trigger until the print has started, at a printable temperature.

Files

No response

[github-actions]

Thank you for your contribution to our project. This issue has not received any updates for 60 days and may be considered "stale." If this issue is still important to you, please add an update within the next 7 days to keep it open. Administrators can manually reopen the issue if necessary.

[rcmaniac25]

I've not reproduced this, but I've also not looked to see if this could happen with the newer firmware.