Prusa-firmware: [BUG]Prompt for Filament change 4 times.. no M600 in gcode
Please, before you create a new bug report, please make sure you searched in open and closed issues and couldn't find anything that matches.
Printer type - MK3S
Printer firmware version- 3.9.0-3421
MMU Upgrade - No
SD card or USB/Octoprint
SD card
Describe the bug
I had a print prompt me to change the filament 3 or 4 times during a print. There were no M600 commands in the gcode.
To Reproduce
Print the gcode
Expected behavior
I expected it not to prompt me for filament change when it wasn't supposed to happen
G-code
gcode on Google Drive
Video
N/A
tommck
All 8 comments
There doesn't need to be a M600 command for the filament switch routine to initialize. It is possible that there is a problem with your filament sensor where it usually senses the filament sensor, but fails randomly. If the firmware detects the lack of filament, it asks for replacement immediately.
leptun
on 7 Sep 2020
@leptun I would have expected it to have a different message when it detects the loss of filament versus an expected filament change (through M600).
tommck
on 7 Sep 2020
Please check your IR sensor, cable and sensor lever.
3d-gussner
on 7 Sep 2020
Turn off filament sensor and try to print. IMHO the unwanted filament change will not occur again.
ochm
on 14 Sep 2020
@tommck Did turning off the filament sensor solve your issue? Did you check the wiring, lever etc.?
DRracer
on 21 Sep 2020
Turning off the sensor let me finish the print. Turned it back on fire the
next print. Had no problems since...
On Mon, Sep 21, 2020, 4:25 AM DRracer notifications@github.com wrote:
@tommck https://github.com/tommck Did turning off the filament sensor
solve your issue? Did you check the wiring, lever etc.?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/Prusa-Firmware/issues/2826#issuecomment-695974478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHPXRNOZKJKJK6NJVIFS6DSG4EY7ANCNFSM4Q6CNFNQ
.
tommck
on 21 Sep 2020
@tommck ok, thank you for your report, closing this issue
DRracer
on 22 Sep 2020
HA! @DRracer, it's like you jinxed me... It just happened again on another print... I disabled the filament sensor again... :(
tommck
on 22 Sep 2020
Related issues
3d-gussner
·
4Comments
sarf2k4
·
3Comments
gusdleon
·
5Comments
3d-gussner
·
4Comments
RacingHell
·
4Comments
Most helpful comment
There doesn't need to be a
M600command for the filament switch routine to initialize. It is possible that there is a problem with your filament sensor where it usually senses the filament sensor, but fails randomly. If the firmware detects the lack of filament, it asks for replacement immediately.