# "Lost communication with MCU" with no obvious reason

**URL:** <https://klipper.discourse.group/t/lost-communication-with-mcu-with-no-obvious-reason/17080>\
**Category:** General Discussion\
**Created:** [June 16, 2024, 7:07am UTC](https://klipper.discourse.group/t/lost-communication-with-mcu-with-no-obvious-reason/17080 "2024-06-16T07:07:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [June 16, 2024, 7:19am UTC](https://klipper.discourse.group/t/lost-communication-with-mcu-with-no-obvious-reason/17080/2 "2024-06-16T07:19:13Z")

</div>

Unfortunately, there is not much we can contribute apart from the items already listed here: [Timeout with MCU / Lost communication with MCU](https://klipper.discourse.group/t/timeout-with-mcu-lost-communication-with-mcu/6639)

For whatever reason, the respective MCU has suddenly stopped responding. Klipper realizes this, but has no way of knowing why it did this. Like you cannot ask someone why he is not answering when the phone line has been cut.

---

_[View the full topic](https://klipper.discourse.group/t/lost-communication-with-mcu-with-no-obvious-reason/17080)._