RE: i3 mk3s mmu2s rebooting at print start
I too have seen this since upgrading to the latest firmware 3.7.2 and it seems to happen with files others have created (on non MMU2s files).
RE: i3 mk3s mmu2s rebooting at print start
Happens to me with 3.7.1, this is expected and normal. As @jmone said, it happens when you print gcode generated for a non-MMU printer.
Either reslice the model for MMU in single mode or use the Load to Nozzle function in the menu to load filament before starting the print.
RE: i3 mk3s mmu2s rebooting at print start
I did slice it in MMU single mode. With the latest slicer. I'll try again.
I'm rechecking now - it's "Original Prusa i3 MK3S MMU2S Single" mode, 0.30mm DRAFT MK3 print settings, Prusa PLA filament.
file: https://www.thingiverse.com/thing:2765217
20% infill, no support, estimate 1h18m25s.
RE: i3 mk3s mmu2s rebooting at print start
I just upgraded to MMU2S from MK3 and the same thing was happening to me. After scratching my head for a few days, I looked at the sensors (support menu) and my IR sensor and FINDA were out of whack. I recalibrated both in place and that seemed to fix the reboot issue.
It took a little while to tweak the IR sensor but I did not do any other changes, so I hope this helps...
RE: i3 mk3s mmu2s rebooting at print start
@william-d24 out of whack how? I was getting false positives on the IR sensor, replaced the idler piece with one that has an M2 screw at the top for fine tuning. Seems to work right now. I would understand if the IR was wired wrong and shorted the RAMBo when it detected filament, but that doesn't seem to be the case.
RE: i3 mk3s mmu2s rebooting at print start
Getting the IR sensor to consistently read a 0 or 1 took awhile, but it sounds like that's taken care of. The LED on my FINDA was not changing state, whether filament was fed through or not, and I seem to remember it was always off (always sensing filament?). Once I removed the PTFE fitting and cover, I inserted some filament while monitoring the sensor on the LCD and readjusted the probe.
I watched your video and the issue was exactly the same, filament would feed through to extruder, get to temp, then reboot. Most of the time I had to manually pull the filament out or remove the tube from the MMU to extruder and pull the filament.
RE: i3 mk3s mmu2s rebooting at print start
my FINDA probe light is always off, even when the sensor reads 1 or 0... which it does correctly, repeatedly tested with an M1.5 alan key and a piece of 1.75mm filament.
I re-heat and unload filament on startup, something I feel the machine should do automatically to get back to correct initial state.
RE: i3 mk3s mmu2s rebooting at print start
I am having this same issue. Bed level check, navigate to start wipe, but when the MMU2S should draw the filament down to the extruder, the printer restarts! Latest firmware, happens regardless of printing from SD or printing from OctoPrint. I have already tried a complete factory reset, but the problem still exists.
When in Octoprint, it will try to start the print over after restarting, only to get to the same point and restart again. It's an endless cycle.
Even more mysterious, is that the printer will sometimes load filament fine, but it's the wrong filament slot! It's bizzare, and I'm at my wit's end. What if it's a problem with my MMU2S board?
The only way I can start a print now is to select "load to nozzle" in the LCD menu. The print will then work fine, even if it's a multi-material print.
RE: i3 mk3s mmu2s rebooting at print start
@william-h32
What I found was that if the sensor at the extruder said "yes, I have filament" and the sensor at the MMU2 said "no, I don't" then the machine would panic and reboot. I think it doesn't know how to deal with a broken line and doesn't even alert the user what's going on, it just bails.
In nearly a year of ownership we were never able to get the machine to reliably print because of false readings on both sensors. In the end I sold it undervalued to someone more patient that I.
Good luck!
RE: i3 mk3s mmu2s rebooting at print start
@i-make-robots
i have the same problem now, how do you fix it? i have a mk3s with mmu2.
tnx