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] MMU Overcurrent kept triggering whenever powering back on right after powering down #4492

Open
5jvm0u4 opened this issue Feb 20, 2025 · 2 comments
Labels
bug Something isn't working.

Comments

@5jvm0u4
Copy link

5jvm0u4 commented Feb 20, 2025

Printer model

MK4S(Stock&New)+MMU3(upgraded from MMU2S)

Firmware version

6.2.1+8833 & 3.0.3

Upgrades and modifications

No response

Printing from...

Nothing

Describe the bug

I consider it a bug because if I power down the whole system for 5 minutes and power it back on there's no overcurrent problems, and also, the beeping is really annoying, please limit it to five beeps or under, it's enough, I know there's a problem when my whole screen turned red.

How to reproduce

Everytime when I power back on right after powering down, through the power button on the power supply, it happens, and everytime I wait for 5 minutes, it boots without any problem

Expected behavior

No response

Files

No response

@5jvm0u4 5jvm0u4 added the bug Something isn't working. label Feb 20, 2025
@bigman212-help
Copy link

Yep, I'm on my 4th buddy board and 3rd mmu board and pd board. Not sure how I'm going to get a refund on my mk3.5s since it's hard to return the items without destroying the printer and mmu2s doesn't work on the mk3.5s. Shame on prusa for selling a faulty product. Will probably go with a charge back on Amex and switch to Bambu.

@bigman212-help
Copy link

Sometimes it's 5 minutes, I've gotten one where even after 24 hours it wouldn't boot and I had to take out the printer from my lack enclosure and unplug the whole mmu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working.
Projects
None yet
Development

No branches or pull requests

2 participants