How to get the debug data for a HW crash
I keep getting a HW Crash error, even when It's just doing the initial setup process.
How do I retrieve the crash diagnostics?
The LCD menu Fail Stats will just tell you which axis is failing. If this is sudden it's most likely a bearing somewhere - the general procedure I evolved is:
With the power off, move the axis by hand; is it smooth? Does the resistance stay the same over the whole range?
Clean and lubricate the smooth rods, check they are not damaged/scratched. Check the idler pulley is not clogged, out of line, or damaged (loosen the belt and try turning it with your fingertip, is it smooth?)
With the belt loose try turning the stepper motor by hand; is it smooth? You should feel the steps but no grating.
Retighten the belt until it just begins to make a low musical note when plucked...
If the printer works, make your next print this:
https://www.prusaprinters.org/prints/46639-tension-meter-for-the-gt2-belts-of-i3-mk3s-or-prus
It MUST be printed in Prusament PETG or the spring tension will be wrong.
Cheerio,
RE: How to get the debug data for a HW crash
Actually, I just realized that it says FW crash detected, which I presume mens the Firmware.
I had downloaded the latest Open Source firmware from GitHub and made some additions to it, some extra functions, and a new section in the process_commands() function to handle two new kinds of GCodes.
I compile the code and flash it into the printer. Reboot the printer, and it comes up with the "FW crash detected".
The Fail Stats say nothing about Firmware crashes.
You are on your own here - you may be able to insert some debugging messages in the code but that presumes it works for long enough to set up exceptions handling ...
The Fail Stats say nothing about Firmware crashes.
Well, er, that log is maintained by the firmware - which crashed.
Cheerio,