On Print start I get an MCU Shutdown

[theDrsh]

ON_debug_20260201_122530.zip

[user-536]

Here there is the same issue with a hack to avoid that error

[theDrsh]

@user-536 I tried the fix that was shown in that issue, it did not fix my issue.

[user-536]

Ugh, in my case it worked but I don't have any other idea to help
Maybe you can find something on the klipper github

[leshiy1980]

I have the same issue

ON_debug_20260203_144517.zip

[firstchair]

Same issue

[halfmanbear]

[ON_debug_20260201_122530.zip](https://github.com/user-attachments/files/24995742/ON_debug_20260201_122530.zip)

Your klipper MCU version are quite outdated '0.12.x' please ensure all 3rd party plugins and MCU firmware is up to date.

[halfmanbear]

You can try switching to the Opennept4une dev branch in the main opennept4une script menu (advanced page) then reinstall the display connector.

I've been pushing patches quite frequently there due to klippers ongoing MCU comms & probe code rework.

[theDrsh]

well, I tried switching to dev branch, then I decided to try and update the firmware. Got to the point of rebooting with SD card installed and now my printer won't boot at all. I started trying to restart the instructions for OpenNept4une and reflashed the eMMC, plugged that back in, powered the machine back on and nothing, just a few status LEDs nothing flashing indicating booting, not reachable via SSH, not able to read anything off of the serial port. Think its dead.

[WallBaby]

You can try switching to the Opennept4une dev branch in the main opennept4une script menu (advanced page) then reinstall the display connector.

I've been pushing patches quite frequently there due to klippers ongoing MCU comms & probe code rework.

would switching to the dev branch help with issues with the BTT Eddy Duo? Got it installed and it works great, but now i get constant MCU shutdowns and im not sure why.

[Henkeh]

It does seem to work on my end with an Eddy Duo.

You can try switching to the Opennept4une dev branch in the main opennept4une script menu (advanced page) then reinstall the display connector.
I've been pushing patches quite frequently there due to klippers ongoing MCU comms & probe code rework.

would switching to the dev branch help with issues with the BTT Eddy Duo? Got it installed and it works great, but now i get constant MCU shutdowns and im not sure why.

[WallBaby]

It does seem to work on my end with an Eddy Duo.

You can try switching to the Opennept4une dev branch in the main opennept4une script menu (advanced page) then reinstall the display connector.
I've been pushing patches quite frequently there due to klippers ongoing MCU comms & probe code rework.

would switching to the dev branch help with issues with the BTT Eddy Duo? Got it installed and it works great, but now i get constant MCU shutdowns and im not sure why.

How do I go about switching over to the dev branch? Do I need to reflash my emmc or can I just ssh in and change over?

[Henkeh]

It does seem to work on my end with an Eddy Duo.

You can try switching to the Opennept4une dev branch in the main opennept4une script menu (advanced page) then reinstall the display connector.
I've been pushing patches quite frequently there due to klippers ongoing MCU comms & probe code rework.

would switching to the dev branch help with issues with the BTT Eddy Duo? Got it installed and it works great, but now i get constant MCU shutdowns and im not sure why.

How do I go about switching over to the dev branch? Do I need to reflash my emmc or can I just ssh in and change over?

You can simply ssh in and change over per the instructions of @halfmanbear above.

[user-536]

It does seem to work on my end with an Eddy Duo.

You can try switching to the Opennept4une dev branch in the main opennept4une script menu (advanced page) then reinstall the display connector.
I've been pushing patches quite frequently there due to klippers ongoing MCU comms & probe code rework.

would switching to the dev branch help with issues with the BTT Eddy Duo? Got it installed and it works great, but now i get constant MCU shutdowns and im not sure why.

How do I go about switching over to the dev branch? Do I need to reflash my emmc or can I just ssh in and change over?

You can simply ssh in and change over per the instructions of @halfmanbear above.

I'm on the dev branch but my eddy duo still doesn't work very well.
Is it possible that the addy-ng addon is broking the firmware ? Should I ask on the eddy-ng repository for help ?
The only way to make it work is by adding
Nice=-18
IOSchedulingPriority=1
to the service file, but it still have some strange behavior when doing some calibrations(for example issuing the bed_mesh_calibrate method=scan crashes but with rapid_scan don't )

ON_debug_20260213_152633.zip

[ToasterUwU]

I have a stock N4Pro, and updating the MCUs, applying the dev branch, and adding

[Service]
Nice=-18
IOSchedulingPriority=1

to /etc/systemd/system/klipper.service fixed it for me, only the combination of all did it for me.