Skip to content

[BUG] MMU3 disappears from PrusaConnect after every successfull print #4874

@neoyarus

Description

@neoyarus

Printer model

MK3S/+

MMU model

MMU3

Firmware versions

3.14.1

Upgrades and modifications

RPI Zero 2w attached to the main board running prusalink 0.8.1, usb camera connected, one extra frint fan added.

Printing from...

PrusaConnect

Describe the bug

Whenever I finish a print with the MMU, PrusaConnect stops seeing the printer as a MK3S+ with an MMU3 and starts seeing it as a regular MK3S+. This then prevents me from uploading MMU gcodes to the printer from PrusaSlicer since it is now considered incompatible. Resetting or power cycling the printer does not help. If I go into PrusaLink, unlink the printer from PrusaConnect, reset the API key, then link in again, it comes back as MK3S+ with MMU3, but will revert to a regular MK3S+ after a print.

How to reproduce

Simply run any MMU print on a MK3S+ equipped with an MMU3, and check its status in PrusaConnect after the print finishes.

Expected behavior

No response

Files

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions