mk3.5 mmu3 not enough time to hit finda about prusa-firmware-buddy HOT 13 OPEN

It has definitely not "been fixed in the final release", in fact we haven't touched this procedure at all. I'm still curious if we are talking about the same. Do you have a video of the original issue you reported?

no but tommorow i can downgrade firmware and get a video, it does seem to be ok now im not sure if it was a fluke or what but ti definitly happend a few times on the other firmware

from prusa-firmware-buddy.

Hi answering you here at the correct issue tracker:

I am sorry I was unable to verify that. Works well here. Have you switched back to the older 5.2.2 firmware for verification?

from prusa-firmware-buddy.

Hi answering you here at the correct issue tracker:

I am sorry I was unable to verify that. Works well here. Have you switched back to the older 5.2.2 firmware for verification?

Hi, yes the old version works fine.

from prusa-firmware-buddy.

During which operation does this happen?

from prusa-firmware-buddy.

During which operation does this happen?

if you start a print with no fillament preloaded to nozzle.

from prusa-firmware-buddy.

If you start with no filament preloaded in the MMU, then the MMU correctly responds with FINDA_DIDNT_SWITCH_ON. It has been designed this way since the very beginning and nobody objected on MK3S+.

Actually, the problem is much deeper. The MMU cannot distinguish between missing and/or fallen-out filament and stuck filament which didn't reach the FINDA. Therefore we don't want to extend the time until FINDA triggers, moreover, we want this time to be as short as possible. :

• A user's fault (no preloaded filament) is a much less of an issue (can be cleanly resolved) than ...
• ... having a piece of filament stuck in the selector before FINDA so badly that one would need to disassemble the whole thing.
• The second issue is a misconfigured FINDA which sometimes happens to newly assembled MMUs done by users not following the instructions - if we increased the time to push filament and FINDA was not triggering, we could push the filament long into the PTFE tube. That makes another set of edge cases while resolving the issue on the MMU.

So please use the toolmapping screen to check your filaments before printing. We even thought about having this check mandatory during the development. In the end we relaxed this requirement in order to give users more freedom.

from prusa-firmware-buddy.

If you start with no filament preloaded in the MMU, then the MMU correctly responds with FINDA_DIDNT_SWITCH_ON. It has been designed this way since the very beginning and nobody objected on MK3S+.

Actually, the problem is much deeper. The MMU cannot distinguish between missing and/or fallen-out filament and stuck filament which didn't reach the FINDA. Therefore we don't want to extend the time until FINDA triggers, moreover, we want this time to be as short as possible. :

• A user's fault (no preloaded filament) is a much less of an issue (can be cleanly resolved) than ...
• ... having a piece of filament stuck in the selector before FINDA so badly that one would need to disassemble the whole thing.
• The second issue is a misconfigured FINDA which sometimes happens to newly assembled MMUs done by users not following the instructions - if we increased the time to push filament and FINDA was not triggering, we could push the filament long into the PTFE tube. That makes another set of edge cases while resolving the issue on the MMU.

So please use the toolmapping screen to check your filaments before printing. We even thought about having this check mandatory during the development. In the end we relaxed this requirement in order to give users more freedom.

its preloaded into the mmu, it just takes longer then it thinks to load to the finda

from prusa-firmware-buddy.

The default distance limit in the FW is twice the distance from the pulley into FINDA.
So in you case - either the filament is not grabbed by the gears (which means it is not preloaded correctly) or it gets stuck on its way out (which means you should check the HW of your unit).

from prusa-firmware-buddy.

Just to be clear - what sensor are you referring to by saying "finda" @cozmo14047 ? The one on the MMU, or the one at the extruder?

from prusa-firmware-buddy.

Just to be clear - what sensor are you referring to by saying "finda" @cozmo14047 ? The one on the MMU, or the one at the extruder?

ok it seems fixed now with finail release, havent tested it fully though. the finda is the mmu one it only happend if you start a print with no fillament preloaded to nozzle.

from prusa-firmware-buddy.

It has definitely not "been fixed in the final release", in fact we haven't touched this procedure at all. I'm still curious if we are talking about the same. Do you have a video of the original issue you reported?

from prusa-firmware-buddy.

If this starts happening again, the video would be great :)

from prusa-firmware-buddy.

I see that you havent changed this code but deffinitly carnt reproduce it on the new stable release, ive got a few long prints to do then ill downgrade to get a video if u want

from prusa-firmware-buddy.