RE: Crash Detected
The reading from the strain gauge sensor is fluctuating. It doesn't matter if it's hot or cold. I'm waiting for a new one to arrive.
@Wojta, do you know which wire was bent or damaged too much?
How much fluctuation? I think a certain amount is "normal" but large spikes are a sign you might have issues. On my fully functional zero issues MK4S at any static reading there is about +-20 which seems to be acceptable. I think anything close to that should be fine.
RE: Crash Detected
Printer was assembled, new out of box. No visual damage on cable. Fluctuation was in thousands. Normaly +/-70 then it jumped to -4000(+) I thing that lowest number I saw was -6500.
I tried to pull wires but all seems to be secured. I dont know pinout of this cable so I didnt check for continuity/resistance. But I still have that cable.
RE: Crash Detected
I just upgraded my mk4s to CORE one and this was the first problem after startup. Changing the code to add M104 0 fixed it….but wth…
do I bother opening a ticket and hours of frustration ?
RE: Crash Detected
I have the same . Have you resolve the issue ? I am out of ideas how to fix it
RE:
The answer by @Raaz is correct.
The troubleshooting step for me, which identified the issue:
1. Start print
2. Select Tune
3. Turn off Nozzle Heating
Immediately after doing this, my first print completed.
Previously, I would encounter a screen that said: "Crash Detected": "A printer collision has been detected."
and then got stuck on a screen that said: "Crash Detected": "Unable to home the printer. Do you want to try again?" (below) "Try checking belt tension or debris on the axes". - with the only button being "Retry" - no cancel button, and no Timeout. So your bed and filament heater stays on indefinitely. Isn't this a bug?