search

prusa3d / Prusa-Firmware-Buddy

Firmware for the Original Prusa MINI, Original Prusa MK4 and the Original Prusa XL 3D printers by Prusa Research.
Other
1.11k stars 217 forks source link

[BFW-5772] [BUG] Prusa Connect doesn't detect MMU3 after printer (re)boot #4063

Open firetech opened 2 months ago

firetech commented 2 months ago

Printer model

MK4, with MMU3

Firmware version

6.0.3 (also seen in at least 6.0.1 and 6.0.2)

Upgrades and modifications

MMU3

Printing from...

Prusa Connect

Describe the bug

Every time I cold boot or reboot my MK4, Prusa Connect shows the printer as a stock MK4, without MMU3, even though the MMU3 is working perfectly fine. If I manually trigger a reconnect to Prusa Connect by either toggling the default network interface back and forth or toggling the Enable setting for Prusa Connect back and forth, Prusa Connect shows the printer as a MK4 with MMU3 after just a few seconds (toggling the MMU Unit off and back on has no effect). If nothing is done, Prusa Connect will continue showing the printer as a non-MMU3 MK4 through at least several prints.

It seems to me that the initial handshake with Prusa Connect is made too early, before the MMU3 has finished booting, so the MMU3 data isn't sent. Then, after the MMU3 has booted, the relevant data is never updated, unless the printer somehow loses connection to Prusa Connect.

This is especially annoying when using the new Prusa Connect integration in Prusa Slicer 2.8.0, as the printer isn't considered compatible with MK4ISMMU3 G-codes ("Printer model does not match") until Prusa Connect has detected the MMU3.

How to reproduce

  1. (Re)boot the printer
  2. Wait for Prusa Connect to detect the printer as idle
  3. Notice that Prusa Connect isn't showing the MMU3 (also not the Slots item in the status bar)

Workaround:

  1. Go to Settings (or Tune, if already printing) > Network > Default and press the knob twice (to toggle back and forth between Eth and Wi-Fi).
  2. Wait for Prusa Connect to show the MMU3.

Expected behavior

Prusa Connect should notice the printer has an MMU3 connected after printer (re)boot without manual intervention.

Files

No response

cozmo14047 commented 1 month ago

And if the printer is off prusa connect doesnt show mmu so when you attempt to upload to prusa connect when the printer is off it says incompatable model

Krosta8 commented 1 month ago

I have the same issue as described. Someone on Discord told me to try reset on the printer, but that did not help at all. Which make sense regarding what firetech wrote. If I reset the printer, MMU3 is fully booted too late for Prusa Connect to recognized connected MMU3. I can not use new feature of PrusaSlicer 2.8.0 as well, because of this :-(

atkinsonaaron commented 1 month ago

Same issue - the MK4 printer doesn't recognize the MMU3 is installed. This occurred with Firmware 6.0.4. The MMU3 stopped working at firmware 6.0.3

danopernis commented 1 month ago

Thanks for reporting. We have a fix for that scheduled for next release. The issue is caused by race condition when printer connects to Prusa Connect before MMU boots.

danopernis commented 1 week ago

This should be fixed in v6.1.2 via https://github.com/prusa3d/Prusa-Firmware-Buddy/commit/fc1b163a0e6e32ee0b9f4a0c29df6bb6b885c31b can you re-test please?

Krosta8 commented 1 week ago

Yesterday I did a print and it was working correctly. Just in Prusa App I see it like without MMU (not sure if the app can show with/without MMU variant)

cozmo14047 commented 1 week ago

Fixed for me but like Krosta8 said in the app the image is just a standered mk3.5 but on the web it shows correctly