If there is a software crash on the printer, a Crash dump will automatically be saved in the xFlash memory. When troubleshooting the cause of the crash, our Customer support may request this Crash dump. This feature can be used for diagnosing unusual system issues.
The Crash dump has important information about your printers, like the serial number and IP address. Sharing this data publicly is not recommended.
In Windows, it is possible to correctly recover the dump with either PuTTY or OctoPrint.
The Crash dump to xFlash is active at any time, it is stored in xFlash and can be downloaded even after the system reboot until a D22 command (clear the current memory dump in the printer) is sent to the printer.
The MK2.5 and MK2.5S do not contain the xFlash, so the crash dump will not be saved automatically after a crash. Therefore, the crash dump can only be retrieved if the printer is already connected to a serial link at the time of the crash.
Download the program here. Once downloaded, start the program, then:
In order to get the Crash dump using Octoprint, it is necessary to enable "Serial logging" in the OctoPrint Settings -> Printer -> Serial Connection -> General section. Scroll all the way down, check the box under "Serial logging", and click the Save button.
To get the dump, use the serial command D21 (read crash dump).
You can either download the OctoPrint serial log by going to Settings -> Octoprint -> Logging and clicking on the download icon at the right of "serial.log". Or you can copy the dump from "D21" until "ok", and paste it into a text editor like Notepad++. Compress/zip the file before sending it.
If you don't use serial logging by default, disable it after the dump again.
If you have a question about something that isn't covered here, check out our additional resources.
And if that doesn't do the trick, you can send an inquiry to [email protected] or through the button below.