Print preview wrong filament #31805 (CORE One/+) #35805 (CO…

What happened?

The printer can memorize the type of filament loaded in the print head. In case a GCode is loaded with a filament material setting different than the loaded material, the printer shows a message "A filament specified in the G-code is either not loaded or wrong type", or "This G-code was set up for another filament type".

Error name: Print preview wrong filament

Error code: #31805 (CORE One/+) #35805 (CORE One L) #26805 (MK4S) #27805 (MK3.9S) #28805 (MK3.5S) #13805 (MK4) #21805 (MK3.9) #23805 (MK3.5) #17805 (XL) #12805 (MINI)

How to fix it?

Double-check both the loaded filament material and the GCode.

If the issue is with the loaded filament, unload it and load new filament using the printer LCD Menu >Filament.

In case the issue is with the GCode, reslice it and double-check it with our PrusaSlicer.

Was this article helpful?

This action is available only to registered users. Please log-in.

11 comments

Toolmaker240

•

THIS IS THE MOST INFURIATING THING! My custom profile 'PCTG" matches both prusaslicer and on my MK4S, same temperatures EVERYTHING. Is there a way to override this? I do not care if I void a warranty down the road, I fix all of my things regardless.
I have disassociated from "compatible print profiles condition" I have tried changing that as well.

Does anyone have an actual solution that doesnt involve manually changing and saving a preset? I have my own hodge podge sort of automation setup in which I will start prints while Im at work and can peek in with an ip camera. The actual problem is that I dont have service inside my work so I have to go outside to tell the printer to print anyway.

Thank you in advance

rtpguy

•

Still some form of this happening. Besides the fact if you're using Prusa Connect, which 'should' sync filaments created in Slicer to the local C1, even if I replicate it manually as a 'custom' filament locally to match what I did in PrusaSlicer, it still winds up with 'wrong filament' issue and links to this page.

Sad to see this has been. along-running problem. IMO, sync filaments from slicer especially if using connect and be done with it, or allow override flags to equate 'filament X on printer is what I call in slicer.'

Richard Miller

•

I want my material to match the name on the custom value on the printer (Core One), so I don't get those "wrong filament" warnings. Core One custom label was set to "3D-PCTG" (they don't allow longer names) and my saved Filament on the slicer is "3D-PCTG". Seems the same to me. I STILL get the error about it not being the right filament. I saw something about slicer not liking the dash, but that was 5 years ago and it certainly allows it in the file names. Any thoughts?

Richard Miller

•

It is confusing (and rarely do I find that from Prusa). I uploaded a 3d-fuel ino file, and this is what is selected in Prusa slicer. Why does it think it isn't that when I go to print via Prusa Connect? I don't see how it would know what is actually in the printer other than my "PETG" choice when heating and loading.

•

Seems like there are two ways how to do insert custom filament. What worked for me: Turn off the printer, wait a bit and turn it on. On the main screen go to filament - filament management - modify first available "custom" profile, insert same name as in your filament type and same temperatures. Unload whatever you have loaded, then load your new filament. Now I have my ESD profile without "Material does not match". First time I get to the custom profiles a bit different way and it didnt work.