Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] MK3S with MMU2S "model was sliced for another printer model" #4833

Open
leonet99 opened this issue Jan 10, 2025 · 1 comment
Open

[BUG] MK3S with MMU2S "model was sliced for another printer model" #4833

leonet99 opened this issue Jan 10, 2025 · 1 comment
Labels

Comments

@leonet99
Copy link

Printer model

MK3S/+

MMU model

MMU2S

Firmware versions

MK3S_MK3S+_FW_3.14.1_MULTILANG.hex and MMU2S_MMU3_FW3.0.3+896.hex

Upgrades and modifications

No response

Printing from...

SD Card

Describe the bug

After updating my MK3S and MMU2S (with MK3S_MK3S+_FW_3.14.1_MULTILANG.hex and respective MMU2S_MMU3_FW3.0.3+896.hex), my printer displays this error message "model was sliced for another printer model" every time I try to print a model (sliced correctly using PrusaSlicer 2.9.0 for "Original Prusa i3 MK3S & MK3S+ MMU2S Single" printer).
I verified the gcodes in subject and it contains the correct printer model check: "M862.3 P "MK3SMMU2S"
The only logical issue remaining is that the printer is now looking to find a different string at the printer model check in the gcode.

The logical questions are:

  1. What is the updated printer firmware looking for to find in the gcode when it does the printer model check?
  2. What's the proper temporary band-aid for this issue until fw fix? (hopefully without removing the printer model check from the printer start gcode)
  3. Is Prusa aware of this issue (also present in the previous fw release (3.14.0) and are there any plans to fix this bug?

How to reproduce

The issue repeats itself every time when trying to print a model from a gcode file (SD card).
I suspect that the printer is looking to find a different string than "MK3SMMU2S" when it performs the printer model check when it runs the start gcode.

Expected behavior

The printer firmware should validate the "MK3SMMU2S" as a valid match during printer model check.

Files

Filament Sensor Bracket Kmax M10 v5_0.2mm_PLA_MK3SMMU2S_1h2m.zip

@3d-gussner
Copy link
Collaborator

@leonet99 Thanks for the report. Please see #4792 and #4786

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants