Printers crashing mid print after upgrading to OpenNept4une v0.1.6

[botlahan]

I have now confirmed the issue on 2 seperate N4P that after flashing the newest OpenNept4une v0.1.6 every single print I have attempted have failed mid print on both N4P attached is a screen shot of the error i get on both printers. I can provide Klippy and Moonraker logs. Of note, both printers are running on an 8gb EMMC with 1.5 gb of free space, it seems like there is a

random spike in CPU with overloads the MCU and causes a crash.

[Cascadier1]

same here. Updated to 0.1.6 and can´t do any longer print. klippy log shows no errors to me.
Printer stops mid print.

klippy(13).log

[halfmanbear]

Could you both please try and update the MCU RpI within the opennept4une script, menu option 4. This should solve this.

Or alternatively run

echo "kernel.sched_rt_runtime_us = -1" | sudo tee -a /etc/sysctl.d/10-disable-rt-group-limit.conf

Then reboot

[elamera96]

Не могли бы вы оба попробовать обновить MCU RpI в скрипте opennept4une, выбрав пункт меню 4. Это должно решить проблему.

Или, в качестве альтернативы, запустить

echo "kernel.sched_rt_runtime_us = -1" | sudo tee -a /etc/sysctl.d/10-disable-rt-group-limit.conf

Затем перезагрузитесь

Is it possible to apply both options sequentially? I have the same problem

[botlahan]

Could you both please try and update the MCU RpI within the opennept4une script, menu option 4. This should solve this.

Or alternatively run

echo "kernel.sched_rt_runtime_us = -1" | sudo tee -a /etc/sysctl.d/10-disable-rt-group-limit.conf

Then reboot

I did both methods of updating the mcu RpI and the issue persists. This time happening during bed mesh calibration, the MCU shuts down at the same probe spot every time. Thank you for looking into this

[cdichiara]

I believe I'm having the same issue. Sort of accidentally upgraded to v0.1.6, though I love the new installation software btw.

1. I had updated only half of the MCU firmware at first (forgot the virtual side) and had a rough go, so the second time of flashing the computer I was leery and reverted the MCU firmware to the version that came with the v0.1.6 drop. At that time the prints were failing about 40? lines up.

2. So I built and installed the MCU update for today, and caught the virtual step this time:

Then it crashed in the automatic bed leveling at the beginning of a print. So I was about to take that final step of running that group limit command, but I decided to turn on the printer again with the microUSB in. This time the filename was changed to a CUR file - interestingly enough it didn't do that after #2 above, even though the data in the GUI seemed to indicate a successful update of the MCU.

Update 11/5: problem is still occurring. Non-deterministic but frequent.

[botlahan]

I was able to get it to complete a bed mesh calibration after redoing all the MCU updates… started a print, 6 hours in to a 7 hour print it crashed again

[Cascadier1]

my 4Max still crashes after the changes. small prints (10min) doing fine.

[halfmanbear]

The display service might be utilising too much CPU, just a theory but I've configured some memory, CPU, and I/O limits for the display service (requires re-installing the display service in the opennept4une installer script, accept any updates)

OpenNeptune3D/display_connector@f577b35

[Cascadier1]

so, just running the script again may help?

[elamera96]

Could you both please try and update the MCU RpI within the opennept4une script, menu option 4. This should solve this.

Or alternatively run

echo "kernel.sched_rt_runtime_us = -1" | sudo tee -a /etc/sysctl.d/10-disable-rt-group-limit.conf

Then reboot

The problem remains. I decided to install version 0.1.5

[elamera96]

[botlahan]

Just did a completely fresh install and even ran the scripts/update after to be thorough. Just started a print and it crashed after the first layer.

[elamera96]

Я только что выполнил полную переустановку и даже запустил скрипты/обновление, чтобы всё было по-честному. Я только начал печать, и она прервалась после первого слоя.

I just reinstalled everything... I probably shouldn't even try, it's very sad.

[elamera96]

I printed several layers and fell into error again. Interestingly, I couldn't log into the web interface at the time of the error.

[cdichiara]

@evgenich96 I got that message when I updated the physical MCU firmware but not the virtual MCU firmware, and the version numbers didn't match in the GUI.

Interesting, just got my system to crash while idling for about a minute. I logged in to the shell, ran opennept4une, got to the menu, and the system crashed.

Might have to go back to v0.1.5 ... I really hope I can with the updated MCU firmware in place, I don't know how to flash that back with the v0.1.5 software.