› ›

error Klipper State Shutdown

mechatronicfactorymechatronicfactory
in Bug Reports
hello everyone, maybe someone here can help me. 

I am currently setting up a printer farm with a converted Tronxy X5SA Pro. The control electronics have been upgraded to the 446 v10 board from Tronxy. 
Each 3 Tronxy are controlled with a Raspberry Pi4 8GB 256GB and klipper (Python 3 version). 
At first everything worked great. But now I have a job with larger parts (printing time over 4 days) where I regularly get a fatal error klipper state shutdown. 
The printers sometimes fail together but sometimes also separately. The last error was the first two printers failing together and the third about 4 hours later. 

I have already checked all the standard hardware things. 
Original power supply from Raspberry Pi with 3A. 
Stable power supply to the printer and Pi via a UPS. 
5V pin in the USB cable taped off. 
Good USB cable used. 
No undervoltage and no CPU throttling on the Pi. 

Experimented with different serial modes.
Tested PingPong mode yes and no. 
Tried different buffer sizes. 

Tested with different number of printers on the Raspberry Pi (1 to 3).

Unfortunately the error still occurs. 

I'm still testing, do you have any tips on things I haven't thought of. 

Comments

  • mechatronicfactorymechatronicfactory
    Ihr könnt auch gerne auf Deutsch antworten. 

  • mechatronicfactorymechatronicfactory
    Here is my log file during the error.

    Send:22:40:23.105: N988589 G1 X30.202 Y110.121 E125.42472
    Recv:22:40:23.105: ok (N988589)
    Send:22:40:23.105: N988590 G1 X32.338 Y106.801 E125.63221
    Recv:22:40:23.106: ok (N988590)
    Send:22:40:23.106: N988591 G1 X34.555 Y103.536 E125.83963
    Recv:22:40:23.106: ok (N988591)
    Send:22:40:23.106: N988592 G1 X36.853 Y100.327 E126.04707
    Recv:22:40:23.106: ok (N988592)
    Send:22:40:23.106: N988593 G1 X39.23 Y97.176 E126.25452
    Recv:22:40:23.403: ok (N988593)
    Send:22:40:23.403: N988594 G1 X41.684 Y94.085 E126.46195
    Recv:22:40:23.404: ok (N988594)
    Send:22:40:23.404: N988595 G1 X44.214 Y91.055 E126.66941
    Recv:22:40:23.404: ok (N988595)
    Send:22:40:23.404: N988596 G1 X46.818 Y88.089 E126.87685
    Recv:22:40:23.404: ok (N988596)
    Send:22:40:23.404: N988597 G1 X49.495 Y85.189 E127.08428
    Recv:22:40:23.405: ok (N988597)
    Send:22:40:23.405: N988598 G1 X52.244 Y82.357 E127.29171
    Recv:22:40:43.570: // Klipper state: Shutdown
    Recv:22:40:43.571: ok (N988598)
    Send:22:40:43.572: Slow command added:M400 ; Wait for current moves to finish, clearing the buffer
    Send:22:40:43.572: N988599 M400 ; Wait for current moves to finish, clearing the buffer
    Recv:22:40:43.576: // Lost communication with MCU 'mcu'
    Recv:22:40:43.576: // Once the underlying issue is corrected, use the
    Recv:22:40:43.576: // "FIRMWARE_RESTART" command to reset the firmware, reload the
    Recv:22:40:43.580: // config, and restart the host software.
    Recv:22:40:43.580: // Printer is shutdown
    Recv:22:40:43.580: !! Lost communication with MCU 'mcu'
    Recv:22:40:43.580: ok (N988599)
    Send:22:40:43.580: N988600 M104 T0 S0 ; Disable extruder
    Recv:22:40:43.583: // Lost communication with MCU 'mcu'
    Recv:22:40:43.583: // Once the underlying issue is corrected, use the
    Recv:22:40:43.583: // "FIRMWARE_RESTART" command to reset the firmware, reload the
    Recv:22:40:43.583: // config, and restart the host software.
    Recv:22:40:43.583: // Printer is shutdown
    Recv:22:40:43.583: !! Lost communication with MCU 'mcu'
    Recv:22:40:43.584: ok (N988600)
    Send:22:40:43.584: N988601 M140 S0 ; Disable bed
    Recv:22:40:43.584: // Lost communication with MCU 'mcu'
    Recv:22:40:43.584: // Once the underlying issue is corrected, use the
    Recv:22:40:43.585: // "FIRMWARE_RESTART" command to reset the firmware, reload the
    Recv:22:40:43.585: // config, and restart the host software.
    Recv:22:40:43.585: // Printer is shutdown
    Recv:22:40:43.585: !! Lost communication with MCU 'mcu'
    Recv:22:40:43.585: ok (N988601)
    Send:22:40:43.585: N988602 G91 ;Relative mode
    Recv:22:40:43.586: // Lost communication with MCU 'mcu'
    Recv:22:40:43.586: // Once the underlying issue is corrected, use the
    Recv:22:40:43.586: // "FIRMWARE_RESTART" command to reset the firmware, reload the
    Recv:22:40:43.586: // config, and restart the host software.
    Recv:22:40:43.586: // Printer is shutdown
    Recv:22:40:43.586: !! Lost communication with MCU 'mcu'
    Recv:22:40:43.586: ok (N988602)
    Send:22:40:43.586: N988603 G1 Z10 F1000 ;Move Bed down 10 mm
    Recv:22:40:43.587: // Lost communication with MCU 'mcu'
    Recv:22:40:43.587: // Once the underlying issue is corrected, use the
    Recv:22:40:43.588: // "FIRMWARE_RESTART" command to reset the firmware, reload the
    Recv:22:40:43.588: // config, and restart the host software.
    Recv:22:40:43.588: // Printer is shutdown
    Recv:22:40:43.588: !! Lost communication with MCU 'mcu'
    Recv:22:40:43.588: ok (N988603)
    Send:22:40:43.588: N988604 G90 ;Absolute Mode
    Recv:22:40:43.589: // Lost communication with MCU 'mcu'
    Recv:22:40:43.589: // Once the underlying issue is corrected, use the
    Recv:22:40:43.589: // "FIRMWARE_RESTART" command to reset the firmware, reload the
    Recv:22:40:43.589: // config, and restart the host software.
    Recv:22:40:43.589: // Printer is shutdown
    Recv:22:40:43.589: !! Lost communication with MCU 'mcu'
    Recv:22:40:43.589: ok (N988604)
    Send:22:40:43.590: N988605 G1 X0 Y0 F4000
    Recv:22:40:43.590: // Lost communication with MCU 'mcu'
    Recv:22:40:43.591: // Once the underlying issue is corrected, use the
    Recv:22:40:43.591: // "FIRMWARE_RESTART" command to reset the firmware, reload the
    Recv:22:40:43.591: // config, and restart the host software.
    Recv:22:40:43.591: // Printer is shutdown
    Recv:22:40:43.591: !! Lost communication with MCU 'mcu'
    Recv:22:40:43.592: ok (N988605)
    Send:22:40:43.592: N988606 M84 ; Disable motor
    Recv:22:40:43.592: // Lost communication with MCU 'mcu'
    Recv:22:40:43.592: // Once the underlying issue is corrected, use the
    Recv:22:40:43.593: // "FIRMWARE_RESTART" command to reset the firmware, reload the
    Recv:22:40:43.593: // config, and restart the host software.
    Recv:22:40:43.593: // Printer is shutdown
    Recv:22:40:43.593: !! Lost communication with MCU 'mcu'
    Recv:22:40:43.593: ok (N988606)
    Exec:22:40:43.593: @stopLog

  • RepetierRepetier
    Ping-Pong, buffer size etc on server side will not help I think. The message you get causing fatal error which is important is:
    Recv:22:40:43.589: // Lost communication with MCU 'mcu'

    Here mcu is the printer board and the message comes from klipper. So what happens is that klipper stops communication with printer while commonunction klipper<->Repetier-Server is working stable.

    Check linux syslog around the timestamps where this happens and see why linux does this. I think it is the only place where you find the reason for it. Linux disconnects usb communication not only for undervoltage but also if it thinks it is getting emf signals via usb. 
  • mechatronicfactorymechatronicfactory
    Okay, thanks for the tip. I'll have a look there.
Sign In or Register to comment.