Getting Y Crash Detected After Printing Fine For A Couple Weeks
 
Notifications
Clear all

Getting Y Crash Detected After Printing Fine For A Couple Weeks  

  RSS
brandon217
(@brandon217)
Active Member
Getting Y Crash Detected After Printing Fine For A Couple Weeks

I included a video of what is happening. Yesterday I started a print job and canceled it when it was in the middle of the 8 point calibration before each print, after that, the y-axis plate backed all the way back and it continued to turn the y-axis motor causing it to skip the belt once or twice before stopping. After that happened I have been getting this y crash detected. I have adjusted the y-axis belt multiple times to be tight and loose, which didn't change it. I also lubricated the x and y-axis bars to cross things off the list. I have also re-calibrated the XYZ axis, today, I got it to print two parts without stopping, but after the print job, it went right back to doing it again. The only thing I can think of is the belt is damaged or out of the proper position after the incident.

Best Answer by brandon217:

After trying countless other things I ended up downgrading the firmware from 3.12.2 to 3.11.0 after reading about it in another forum and that seems to have fixed it.

Opublikowany : 28/06/2023 12:58 am
brandon217
(@brandon217)
Active Member
Topic starter answered:
RE: Getting Y Crash Detected After Printing Fine For A Couple Weeks

Opublikowany : 28/06/2023 11:06 am
brandon217
(@brandon217)
Active Member
Topic starter answered:
RE:

After trying countless other things I ended up downgrading the firmware from 3.12.2 to 3.11.0 after reading about it in another forum and that seems to have fixed it.

This post was modified 1 year temu by brandon217
Opublikowany : 28/06/2023 9:05 pm
Thejiral
(@thejiral)
Noble Member
RE: Getting Y Crash Detected After Printing Fine For A Couple Weeks

y-crash detection is very senstive. It is enough for the bearings to be not 100% optimal for it to randomly trigger. Replacing the y-axis bearings resolved the issue for me but it came back a year later or so. The simply solution for me: disable crash detection. It causes more troubles than it does good IMHO. Also without crash detection you can enable stealth mode. 

Mk3s MMU2s, Voron 0.1, Voron 2.4

Opublikowany : 29/06/2023 6:57 am
Share: