You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Printer type - MK3s Printer firmware version- 3.9.2
MMU Upgrade - No
SD card or USB/Octoprint
Octoprint
Describe the bug
When I use M702 via octoprint (well, via a button mapped on octodash), sometimes it behaves well (unload and that's it), and sometimes, after the unload, the head is parking like for a filament change, and then the printer asks to insert the new filament
To Reproduce
Use M702 via octoprint. Sometimes it behaves as described
Expected behavior
M702 should only unload filament everytime, and never ask to load new filament as if a filament change was requested
The text was updated successfully, but these errors were encountered:
Its-my-right
changed the title
[BUG]PM702 (Filament unload) sometimes triggers M600 (filament change)
[BUG]M702 (Filament unload) sometimes triggers M600 (filament change)
Dec 6, 2020
If the issue persists via Octoprint (probably not tested), now the user can send M406/M405 codes to disable/enable the filament sensor before/after the M702 filament unload code (PR #1447).
Printer type - MK3s
Printer firmware version- 3.9.2
MMU Upgrade - No
SD card or USB/Octoprint
Octoprint
Describe the bug
When I use M702 via octoprint (well, via a button mapped on octodash), sometimes it behaves well (unload and that's it), and sometimes, after the unload, the head is parking like for a filament change, and then the printer asks to insert the new filament
To Reproduce
Use M702 via octoprint. Sometimes it behaves as described
Expected behavior
M702 should only unload filament everytime, and never ask to load new filament as if a filament change was requested
The text was updated successfully, but these errors were encountered: