y axis crash detection  

Re: y axis crash detection

whats the problem you're having?

Y is usually loudest from what I've heard, mine certainly were.

Re: y axis crash detection

when i print some parts the y axis detects crashes...
it's only the y axis..

i greased the bearings with teflon lube and runs smooth..
i print Pug buddy from the samples and it detects 30 crashes.. 🙁

i don't know what's the real problem is...
i try today to tension the belts again...

Re: y axis crash detection

I have somewhat the same Problem. Y Axis detects Crashes that i cant locate but with crash detection disabled it prints just fine.

Re: y axis crash detection

I am having the same problem on my i3 mk3 kit-version. I can see the printer home itself and restart the print from time to time, but I can not see the reason for it to do so. It is like the crash detection on the y-axis is too sensitive.

Occasionally, some very simple prints may print without any crashes, but most of my prints will report 30-100 crashes on the y-axis.

Re: y axis crash detection

I also have this issue with lots of detected crashes on the y-axis with my MK3 kit. Belt status is 250 for the y-axis. I never noticed that issue before I updated to 3.1.3. Could this be an issue with the new firmware?

Re: y axis crash detection

that is basically what used to happen with older firmware and octoprint/tethered printing, but its been resolved.

crash detection isn't a feature I care much about personally, but I generally leave it in stealth mode all the time anyway so it doesn't matter.

Re: y axis crash detection

On our MK3 Kit we have the same problem.

Since in normal mode it detects a crash very often, I run the printer in stealth mode, which works fine normally. But now on a very large print which should run 21 hours, the y-axis got an offset of about 5cm.

After that I searched the menu for a "rehoming" or something similar, but couldn't find anything.

Then I switched off the power, but then it failed to continue. It started completely normally, as always, without asking to continue a stopped print.

What should I do? I don't want to start this long-running print again, knowing these problems exist....

We are running Firmware V3.1.3-245

Re: y axis crash detection

If in normal mode it detects crashes "often", you need to get to the bottom of this. You must have some excessive friction or rubbing somewhere that trips the crash detection logic.

Turning off the power using the switch defeats the power loss logic- if you want to resume a print by removing power, you have to pull the plug (and pull it cleanly without hesitation).

Re: y axis crash detection

Thanks for the hint for the power-loss feature.

It seems to be the x-axis, which makes problems.
I now removed the x-axis stepper motor, so the head can move as freely as possible.

I found out, that on the right side (X+) the head has a sticky motion. This is also on the left end of the axis, but not that much.

I measured the distance of the rods. They seem to be not parallel. The left distance has 37.38mm-A and the right side has 37.53mm -A. When the head is in the middle of the x-axis, and I measure directly on the left side of the head, I get 37.14mm-A. Note: A is some fixed offset due to the measuring method.

Are the slide bearings one fixed and one loose, so their distance can compensate for the variation of the distance of the rods? If not, this seems to be a very bad design.
It seems, that the bottom bearing should be able to move a bit into the z-direction to compensate for such a variation in the distance of the rods.

Re: y axis crash detection

If in normal mode it detects crashes "often", you need to get to the bottom of this. You must have some excessive friction or rubbing somewhere that trips the crash detection logic.

Turning off the power using the switch defeats the power loss logic- if you want to resume a print by removing power, you have to pull the plug (and pull it cleanly without hesitation).

thanks. I had a great number of y crash detect. Each caused y offsets.
I rebuilted my Y axe. The gear was certainly too close of the motor
Now all works fine