For the third consecutive day, my X1 Carbon with the latest firmware has exhibited very unusual behavior.
When starting a print from the studio, the process initiates normally. However, as the printer begins extruder calibration, it abruptly halts, rendering the screen completely unresponsive. The concerning part is that the nozzle remains at print temperature, and the build plate retains its heat.
This issue appears out of nowhere. Restarting the printer and running the same print resolves the problem temporarily, but the issue seems to recur after approximately 24 hours of continuous operation. While it may not be directly related, my printer runs 24/7, and a reboot restores functionality for another 24 hours.
I have already opened a support ticket and uploaded both the G-code and the log files for further investigation.
Has anyone else experienced this?
Current setup:
- Printer: X1 Carbon (EU region)
- Firmware: 01.08.02.00
- Filament: External spool with TPU 95A HF
I would try with a new SD card. One from a known manufacturer.
Thank you for the suggestion regarding the SD card potentially being the issue. I appreciate your input!
I recently installed a new SD card from a well-known and reputable manufacturer at the same time I received my printer, so I don’t believe the card itself is the root cause. This problem only occurs when printing directly from the studio software; it never happens when printing from the SD card.
The SD card is only a month old, and if the printer managed to damage it, this would be the fastest any device has ever caused an SD card failure for me. For context, I’ve used the same type of card from the same manufacturer in a much harsher environment with my Raspberry Pi 4, and it survived three years of heavy use without issues.
Before the issue occurs, I notice the video stream starts to stutter, the connection to the printer drops, and eventually, the printer completely locks up. Even if, by some magical reason, the SD card were at fault, the printer locking up entirely is unacceptable as it presents a safety risk.
If the SD card were failing, wouldn’t the print fail consistently or at the start of the job? Additionally, I’ve been able to use the same cached G-code file to produce a successful print, which seems to rule out the card as the cause.
I’d love to hear any additional thoughts or suggestions. Thank you again for your help!