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

Printer model check problem. #4712

Open
2 tasks
jam2606 opened this issue Jul 9, 2024 · 6 comments
Open
2 tasks

Printer model check problem. #4712

jam2606 opened this issue Jul 9, 2024 · 6 comments

Comments

@jam2606
Copy link

jam2606 commented Jul 9, 2024

Description of the bug

al crear un archivo con prusa slicer 2.8.0 para mi mk3s+ com firmware 3.14.0 y mmu2s con firmware 3.0.2 y con el perfil de mk3s+ con mmu2 s ya sea en modo un filamento o multicolor al mandarlo a la impresora me dice que el archivo es para otra maquina

when creating a file with prusa slicer 2.8.0 for my mk3s+ with firmware 3.14.0 and mmu2s with firmware 3.0.2 and with the profile of mk3s+ with mmu2s either in single filament or multicolour mode when sending it to the printer it tells me that the file is for another machine.

Project file & How to reproduce

IMG_2014
IMG_2015
IMG_2016
IMG_2018
IMG_2021
IMG_2022
IMG_2023
IMG_2024
IMG_2025
IMG_2026
IMG_2028
IMG_2029
IMG_2030
IMG_2032

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.8.0

Operating system

windows 11

Printer model

mk3s+ con mmu2s

@rtyr rtyr transferred this issue from prusa3d/PrusaSlicer Jul 10, 2024
@rtyr
Copy link

rtyr commented Jul 10, 2024

The g-code output uses correct printer model (for years), so it seems like some FW issue.
M862.3 P "MK3SMMU2S" ; printer model check

@rtyr rtyr changed the title fallo en perfil prusa slicer Printer model check problem. Jul 10, 2024
@3d-gussner
Copy link
Collaborator

3d-gussner commented Jul 10, 2024

@jam2606 Thanks for reporting this issue.
I just tested FW 3.14.0+8066 (hash b97131b) + MMU3 3.0.2 on MK3S+ with the MK3S hex file.

Also used PrusaSlicer 2.8 with newest profiles Original Prusa MK3S & MK3S+ MMU3 Single to sclice a 25x25x2 cube and sent it to the printer. No warning that the gcode is sliced for wrong printer.

Please ensure that you have flashed the printer with the MK3S MK3S+ firmware and not the MK3 hex file, which would explain the issue.

Gracias por informar de este problema.

Acabo de probar FW 3.14.0 + MMU3 3.0.2 en MK3S+ con el MK3S hex file.
Tambien use PrusaSlicer 2.8 con los perfiles mas nuevos Original Prusa MK3S & MK3S+ MMU3 Single para sclice un cubo 25x25x2 y lo envie a la impresora. No hay advertencia de que el gcode es rebanado para la impresora equivocada.

Por favor, asegúrate de que has flasheado la impresora con el firmware MK3S MK3S+ y no con el archivo hexadecimal MK3, lo que explicaría el problema.

@3d-gussner 3d-gussner self-assigned this Jul 10, 2024
@ojrik
Copy link

ojrik commented Jul 10, 2024

) + MMU3

MK3S+ FW 3.14.0 - MMU3 FW 3.0.2
It is no longer compatible with SLICER Profil MK3S+ MMU2S. The printer will report an error in the G-code. For MMU from FW 3.0.2 Slicer Profile MK3S+ MMU3 should be used.

Firmware settings for MK3S+:
// Printer revision
#define PRINTER_TYPE PRINTER_MK3S
#define PRINTER_NAME PRINTER_MK3S_NAME
#define PRINTER_NAME_ALTERNATE PRINTER_MK3_NAME //the other similar printer to this.
#define PRINTER_MMU_TYPE PRINTER_MK3S_MMU3
#define PRINTER_MMU_NAME PRINTER_MK3S_MMU3_NAME
#define FILAMENT_SIZE "1_75mm_MK3S"
#define NOZZLE_TYPE "E3DREVO"

// Printer name
#define CUSTOM_MENDEL_NAME "Prusa i3 MK3S+R"

@XSSammy
Copy link

XSSammy commented Jul 12, 2024

I have the same issue same printer with a mmu2s. @ojrik I haven't tried printing with the mmu3 profile but I can confirm it doesn't report the same error if I use that profile.

@ojrik
Copy link

ojrik commented Jul 12, 2024

FW from 3.0.0 to 3.0.3 is for MMU3 device. If you use the mmu2s profile, the G-Code will be for a different type of printer. I have MK3.5 MMU3, MK3S+ MMU2S, MK3S MMU3 Ulti multi everywhere I use SLICER profile for MMU3. By the way, I made g-cod for MK3S+ MMU2S and started printing on my MK3S+ FW 3.14.0 - MMU2S FW 3.0.2 device reported G-Code error for different printer type.

@3d-gussner also used a profile for MMU3 and no report.

@XSSammy do you have a similar but different report?

@ojrik
Copy link

ojrik commented Jul 12, 2024

A small note, if you just flashed FW 3.0.2 to the MMU2S device without UPGRADE, you already have MMU3.

@3d-gussner 3d-gussner removed their assignment Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants