Printer Model: Neptune 3 pro
MCU / Printerboard: znc robin nano dw 2.2
Host / SBC Raspberry pi 4 2 gb
klippy.log attached
…I was trying to print a massive model 2 times. And 2 times it was failing in the middle of the process with “mcu: timer is too close”. Gcode file is 300mb. There is 2 Neptunes on my Pi. After first failure i stopped every services of my second printer, because i thought it was the reason. In the first failure try my ram was 1,6/1,6gb even after restarting the firmware (not pi). When it failed in the second time (now, about 21:15) ram stats was 430-460mb/1,6gb. PI has been restarted just before the starting of new (second) try.
The power supply is original pi’s 5v 3,1a.
Hosts temp is and was about 30-35C.
I really can’t understand why it’s happening second time.
Is it just huge gcode file, that klipper can’t eat and randomly fails into error? klippy.log (1).zip (3.6 MB)
In your special case: 300 MB gcode file could point to a very fine resolution that is pushing too much (unneeded) data and thus overloading the system / bandwidth.
I think it was something related with webcam/stream services.
What i’ve done:
Got a new sd.
Removed everything using kiauh.
Done a fresh installation of two nodes of klipper and two of moonraker, one mainsail and two octoeverywhere.
Sliced that model with 0.95% resolution of gcode (i think it was not a cause) and got a 295mb file.
Copied all of previous .cfg’s using WinSCP.
Done a basic calibrations (bedmesh, zprobe, pids).
And… 42h30m printing was done without mcu: timer is too close.
I think the reason was the Crowsnest or pluged in webcam (even with stopped crowsnest), because now ram is not filling without reason just when Pi works.
