Klipper shutdown: Lost communication with MCH nhk

Basic Information:

Printer Model: LDO Trident 300mm Cube
MCU / Printerboard: LDO Nitehawk
Host / SBC ???
klippy.log: klippy.log - Google Drive
Printer config:
Printer config.txt - Google Drive

Hi all,

I have installed and setup my LDO nitehawk for the past 2 weeks and it is has been causing so much fustration with "Lost coummuication with MCU ‘nhk’ "and it got to the point where it will shut down after 5mins of starting a print. I check the cable and connector all seem to be fine and it has lead me to believe it could be in the code. I have attached the klipper and pritner config for you hoping I can find the cause and find a fix for this.

See Timeout with MCU / Lost communication with MCU

i am still confused because I already know have checked these without any results. The only thing I cannot check is the quality power supply as it is a 250w PSU supplied by LDO.

It will be good if the logs can give the exact cause of it.

Unfortunately, the log does not and cannot provide the information. If you read the reasons in the provided link, you will quickly realize, why the root cause cannot be contained in the log.
How should Klipper know that you might have an unstable power supply or some bad wiring?

I am not going to spend too much effect replying back to you except with this, My comment said " ïf ".

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.