Notifications
Clear all

Random filament change requests  

  RSS
TeachingTheDetails
(@teachingthedetails)
Eminent Member
Random filament change requests

Every couple of prints, the Prusa Mini, FW 4.3.3, will randomly request a filament change mid-print. 

This doesn't occur with every print. 

I've gone through PrusaSlicer 2.3.3 and looked for custom G-code, that would do something funky, but it's all standard G-code. It's a fresh PrusaSlicer installation, anyways.

The filament sensor is not in use and disabled.

Any ideas, what would cause the Mini to randomly request these filament changes. 

hw: PRUSA MINI+, FW 4.3.3 & Cr-10s w/ BLTouch, Ezboard, Hemerasw: PrusaSlicer 2.4, Windows 11

Napsal : 27/11/2021 9:25 am
BogdanH
(@bogdanh)
Honorable Member
RE: Random filament change requests

If filament sensor is not used (not connected), then printer always assumes that filament is there and will never request to change it. Means, command to change filament can only come from G-code.
Are you sure you didn't click the "+" mark next to vertical layer ruler in slicer? In that case vertical ruler also changes color at the layer where you clicked "+" symbol.

[Mini+] [MK3S+BEAR]

Napsal : 27/11/2021 1:20 pm
Neophyl
(@neophyl)
Illustrious Member
RE: Random filament change requests

Unless of course the original poster has something  physically wrong with the printers electronics, where the pin is being falsely triggered.
While I wouldn't class that as a likely cause it is also not impossible either.
Other possibilities also include a bug in the printers firmware, although you would expect it to have multiple users all complaining about the same thing if it was the firmware, so once again a low likelihood.

Have you checked the actual outputted gcode file for a M600 ?

Napsal : 27/11/2021 2:07 pm
TeachingTheDetails
(@teachingthedetails)
Eminent Member
Topic starter answered:
RE: Random filament change requests

Ok, for some reason, there was a color change set at a specific layer height in the Gcode, which came from the slicer.

No idea, why that was active. But: Problem solved!

Thanks for the solid input

hw: PRUSA MINI+, FW 4.3.3 & Cr-10s w/ BLTouch, Ezboard, Hemerasw: PrusaSlicer 2.4, Windows 11

Napsal : 27/11/2021 4:36 pm
Share: