MMU2S doesn't load (fsensor_stop_and_save_print)
Happy New Year!
Going to keep this short. I did a full writeup, and then got some security error about protecting my WordPress site and the entire post was lost. There was no swearing before that point...
Short version of the story: Had a Mk3/MMU2, upgraded to MMU2S a while back, all was well. PrusaSlicer updated, then told me my firmware was out of date. While in there updated MMU2S as well (3.8.1/1.0.6). MMU2S acted weird, don't recall how, so I did a factory reset. Printer then told me my gcode didn't match the printer, so I did a new config setup in PrusaSlicer (probably had had 3/MMU2S instead of 3S/MMU2S).
Now when I print, the printer/bed heat, it does the bed calibration, moves to the front left to extrude some filament, moves very slightly to the right, and then resets. Over and over. Looking at the console, I see 'fsensor_stop_and_save_print'. At no point did it try to load filament, it just resets.
I am able to load filament from all 5 MMU2S slots and do a first layer calibration from the front panel, and I have done the FINDA calibration. But gcode with a selected filament will not load that filament, just resets the printer.
Any suggestions?
Send: M862.3 Q Recv: MK3SMMU2S
Send: N36 G1 X240.0 E25.0 F2200.0*73
Recv: ok
Send: N37 G1 Y-2.0 F1000.0*29
Recv: ok
Send: N38 G1 X55.0 E25 F1400.0*106
Recv: fsensor_stop_and_save_print
Recv: echo:Enqueing to the front: "PRUSA fsensor_recover"
Recv: FIRMWARE_NAME:Prusa-Firmware 3.8.1 based on Marlin FIRMWARE_URL: https://github.com/prusa3d/Prusa-Firmware PROTOCOL_VERSION:1.0 MACHINE_TYPE:Prusa i3 MK3S EXTRUDER_COUNT:1 UUID:00000000-0000-0000-0000-0000000000
Best Answer by michael.c46:
OK, after spending days on this, apparently all I have to do is post and I am able to fix it.
I had searched the forums for something similar with no luck, but once I posted it recommended a similar topic here. This person had not picked the MMU2 profile, but otherwise the described behavior matched exactly. So I looked at the gcode and saw that it did indeed have a T2 command. But what did the printer say about this in the console?
Recv: ok
Not queuing T2, that tool doesn't exist according to the printer profile or was reported as invalid by the firmware
Except the printer had the correct firmware. Must be OctoPrint profile. Sure enough, OctoPrint printer profile had 1 extruder configured, with a note that that only affected when it was doing the slicing. It does NOT influence already sliced files that you upload to OctoPrint! Apparently this is no longer true.
I bumped the extruder count up to 5, and am now able to print again!
RE: MMU2S doesn't load (fsensor_stop_and_save_print)
OK, after spending days on this, apparently all I have to do is post and I am able to fix it.
I had searched the forums for something similar with no luck, but once I posted it recommended a similar topic here. This person had not picked the MMU2 profile, but otherwise the described behavior matched exactly. So I looked at the gcode and saw that it did indeed have a T2 command. But what did the printer say about this in the console?
Recv: ok
Not queuing T2, that tool doesn't exist according to the printer profile or was reported as invalid by the firmware
Except the printer had the correct firmware. Must be OctoPrint profile. Sure enough, OctoPrint printer profile had 1 extruder configured, with a note that that only affected when it was doing the slicing. It does NOT influence already sliced files that you upload to OctoPrint! Apparently this is no longer true.
I bumped the extruder count up to 5, and am now able to print again!
RE: MMU2S doesn't load (fsensor_stop_and_save_print)
Thank you Michael - saved my day 🙂