Crash Detected
I've had this error happen a few times now, it's happens when I start a print and the printer is doing its normal warm up in the front right corner.
The error comes up on the screen, stays for a few seconds and the printer carries on and prints fine. I don't have to clear the error, it goes away on its own.
I'd say it happens about one print in 10.
Any ideas whats causing it ? Anything I can check ?
I assembled the kit version of Core One, batch one, so it's been up and running about 3 weeks or so.
RE: Crash Detected
I have not yet heard of the error with the Core One, so I would say it's best to write to support.
RE: Crash Detected
Mine did this once but not since,what surprised me was that it was during the normal headbanging session when I would expect this feature to be turned off, is is kind of no surprise that it bangs into things when intentionally raming into ends. It has not done this since that one time.
/Anders
RE: Crash Detected
I can’t print at all. When I try to I get errors about not being able to home the printer, or a printer collision has been detected . Either way the printer is unusable and a waste of money,
Contact Prusa Support via chat. You will need your printer's serial number.
Cheerio,
RE: Crash Detected
There seems to be quite a big issue with the hotend heater and the loadcell signals (homing, probing, nozzle cleaning).
But there's also the issue regarding a little gap in one of the corners, if you move the gantry all the way to the front or back, which needs some squaring/bending and belt tuning.
If the issue is only, when starting a print (hotend heating up!), then try the custom Start G-code from here:
https://forum.prusa3d.com/forum/postid/751199/
Credits to everyone here: https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/4596
And to @David.b36 https://forum.prusa3d.com/forum/profile/david-b36/
If the issue also happens, when the printer is cold and you start a homing from the LCD panel, it's probably the gantry not being perfectly square.
If both solutions don't work, a cable might be pinched or something more serious, like a faulty board etc.