›

Printing suddenly interrupts at the end, the printer makes terrible sounds.

AlexeyAlexey
in Repetier-Server
Printing suddenly interrupts at the end, the printer makes terrible sounds. When printing from the SD card, everything is OK.
To stop the terrible sounds you have to turn off the printer.


I attached the last log 3 minutes of printing and the server log. Help me please. This is the third fingerprint that ends in an accident. But some models are pre-printed well.

Comments

  • AlexeyAlexey
    edited May 2018
    Printer Log - https://docs.google.com/document/d/16icJndWYo6NwrvirwjZ6sqbAm_GkuQqNjNsfeki0XNE/edit?usp=sharing 

    Server last Log :


    2018-05-24 17:20:31: Closing websocket for missing ping
    2018-05-24 17:20:31: Closing websocket for missing ping
    2018-05-24 17:20:31: Closing websocket for missing ping
    2018-05-24 19:14:16: Update webcam list
    2018-05-24 20:21:23: Closing websocket for missing ping
    2018-05-24 20:21:26: Closing websocket for missing ping
    2018-05-24 20:21:27: Closing websocket for missing ping
    2018-05-24 21:04:43: Update webcam list
    2018-05-24 21:06:04: Update webcam list
    2018-05-24 21:07:51: Update webcam list
    2018-05-24 23:22:13: Closing websocket for missing ping
    2018-05-24 23:22:13: Closing websocket for missing ping
    2018-05-24 23:22:14: Closing websocket for missing ping
    2018-05-25 07:13:31: error: Reading serial conection failed: End of file. Closing connection.
    2018-05-25 07:13:32: Connection closed: Ultimaker 2 Extended Plus
    2018-05-25 07:13:35: Connection started:Ultimaker 2 Extended Plus
    2018-05-25 07:13:35: Reset printer Ultimaker 2 Extended Plus
  • RepetierRepetier
    Communication look sgood and I assume
    2018-05-25 07:13:31: error: Reading serial conection failed: End of file. Closing connection.
    was when you disconnected the printer?

    Does this happen always or just once? If it happens more often you could enable echo so you also log what the firmware thinks it received. So you can see if it is the gcode, a wrong transmission (which is hard with checksums to get wrong) or just a hardware problem causing the problems. This depends on frequency of this happening. Hardwrae problems can also happen on sd card, but if it is a rare problem it is random and hard to find.
  • AlexeyAlexey
    sorry for the long answer. I wrote down a sudden stop log.
    This is caused by a sudden break in communication after 10-16 hours of printing. The USB cable changed twice. Maybe you have an idea what this can be?
    Or how can I continue printing?


    20:00:23.900: N552086 G1 X74.608 Y156.803 E4.1716
    20:00:24.002: ok
    20:00:24.002: N552087 G1 X74.626 Y156.659 E4.1753
    20:00:55.007: Warning: Communication timeout - resetting communication buffer.
    20:00:55.007: Connection status: Buffered:39, Manual Commands: 1, Job Commands: 5000
    20:00:55.007: Buffer used:39 Enforced free byte:0 lines stored:1
    20:00:55.007: N552088 M105


  • AlexeyAlexey

  • AlexeyAlexey
    And Syslog Ubuntu serverv:

    Jun  4 12:17:01 Repieter CRON[32366]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Jun  4 12:49:02 Repieter wpa_supplicant[925]: wls34: WPA: Group rekeying completed with e0:3f:49:07:ac:b0 [GTK=CCMP]
    Jun  4 13:17:01 Repieter CRON[32575]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Jun  4 13:48:56 Repieter wpa_supplicant[925]: wls34: WPA: Group rekeying completed with e0:3f:49:07:ac:b0 [GTK=CCMP]
    Jun  4 14:13:20 Repieter systemd[1]: Starting Daily apt download activities...
    Jun  4 14:14:15 Repieter systemd[1]: Started Daily apt download activities.
    Jun  4 14:17:02 Repieter CRON[653]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Jun  4 14:48:55 Repieter wpa_supplicant[925]: wls34: WPA: Group rekeying completed with e0:3f:49:07:ac:b0 [GTK=CCMP]
    Jun  4 15:17:01 Repieter CRON[864]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Jun  4 15:48:51 Repieter wpa_supplicant[925]: wls34: WPA: Group rekeying completed with e0:3f:49:07:ac:b0 [GTK=CCMP]
    Jun  4 16:17:01 Repieter CRON[1101]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Jun  4 16:48:49 Repieter wpa_supplicant[925]: wls34: WPA: Group rekeying completed with e0:3f:49:07:ac:b0 [GTK=CCMP]
    Jun  4 17:02:25 Repieter dhclient[1084]: DHCPREQUEST of 192.168.1.70 on wls34 to 192.168.1.1 port 67 (xid=0x5976978d)
    Jun  4 17:02:25 Repieter dhclient[1084]: DHCPACK of 192.168.1.70 from 192.168.1.1
    Jun  4 17:02:25 Repieter dhclient[1084]: bound to 192.168.1.70 -- renewal in 37251 seconds.
    Jun  4 17:17:01 Repieter CRON[1357]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Jun  4 17:48:43 Repieter wpa_supplicant[925]: wls34: WPA: Group rekeying completed with e0:3f:49:07:ac:b0 [GTK=CCMP]
    Jun  4 18:17:01 Repieter CRON[1570]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Jun  4 18:48:39 Repieter wpa_supplicant[925]: wls34: WPA: Group rekeying completed with e0:3f:49:07:ac:b0 [GTK=CCMP]
    Jun  4 19:17:01 Repieter CRON[1781]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Jun  4 19:48:38 Repieter wpa_supplicant[925]: wls34: WPA: Group rekeying completed with e0:3f:49:07:ac:b0 [GTK=CCMP]
    Jun  4 20:01:13 Repieter kernel: [474954.620379] usb 2-2: USB disconnect, device number 4
    Jun  4 20:01:13 Repieter kernel: [474954.620719] cdc_acm 2-2:1.0: failed to set dtr/rts
    Jun  4 20:02:17 Repieter kernel: [475018.972050] usb 2-2: new full-speed USB device number 5 using uhci_hcd
    Jun  4 20:02:17 Repieter kernel: [475019.180040] usb 2-2: New USB device found, idVendor=2341, idProduct=0042
    Jun  4 20:02:17 Repieter kernel: [475019.180050] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=220
    Jun  4 20:02:17 Repieter kernel: [475019.180056] usb 2-2: Manufacturer: Arduino (www.arduino.cc)
    Jun  4 20:02:17 Repieter kernel: [475019.180061] usb 2-2: SerialNumber: 7563031363635181A022
    Jun  4 20:02:17 Repieter kernel: [475019.182282] cdc_acm 2-2:1.0: ttyACM0: USB ACM device
  • AlexeyAlexey
    At the same time, another printer is connected to the server and there are no problems with it :s
  • RepetierRepetier
    The first timeout can happen with communication errors. Your firmware does not send line numbers with "ok" so there is no way to see if one ok was missed. So at some time when you have missed enough ok you will get such a timeout and then it should continue to print. Configuring firmware to also send line numbers helps here to avoid this error.

    I also see this
    Jun  4 20:01:13 Repieter kernel: [474954.620379] usb 2-2: USB disconnect, device number 4
    Jun  4 20:01:13 Repieter kernel: [474954.620719] cdc_acm 2-2:1.0: failed to set dtr/rts
    Jun  4 20:02:17 Repieter kernel: [475018.972050] usb 2-2: new full-speed USB device number 5 using uhci_hcd
    Jun  4 20:02:17 Repieter kernel: [475019.180040] usb 2-2: New USB device found, idVendor=2341, idProduct=0042
    Jun  4 20:02:17 Repieter kernel: [475019.180050] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=220
    Jun  4 20:02:17 Repieter kernel: [475019.180056] usb 2-2: Manufacturer: Arduino (www.arduino.cc)
    Jun  4 20:02:17 Repieter kernel: [475019.180061] usb 2-2: SerialNumber: 7563031363635181A022
    Jun  4 20:02:17 Repieter kernel: [475019.182282] cdc_acm 2-2:1.0: ttyACM0: USB ACM device

    20 seconds after timeout. Did you do the disconnect or is this the problem?
  • AlexeyAlexey
    Yes, after the timeout, the engines begin to knock on the walls with their heads. Therefore I had to disconnect, but I tried not to disconnect, and put the seal on pause. But it did not affect how, the printer continued to knock engines.

    I pinched several cables but the result is still bad. After 10-14 hours printing timeout and stopping printing. This is very distressing.

    Tell me about which place in the firmware you are talking about sending the lines?
    If I understand correctly, do you think that the problem is in the printer or in the firmware of the printer? The problem was observed on the firmware Thinker UM2. I will try the original firmware. Yes, I forgot to say - the server is installed on the barebone Aker with the Intel Atom processor. Ubuntu Server 16.

    And I saw many similar topics in the forum. But unfortunately did not find a solution
  • RepetierRepetier
    Assuming you use marlin, you can set in in configuration_adv.h

    The only problem with all this, it would explain why server stops or gets problems sending commands, but it is no explainations for extruder knocking to the wall. Server just sends the command including checksum and firmware decides to interpret it differently causing the knock. So after all the problem could also be in the firmware as it sounds like a very long move far beyond the bed limits. Until that move is finished firmware can not accept new commands so it would also block communication.

    So have a look at the last 20-30 commands send to printer if the coordinates are outside. If so the gcod eis bad, if not firmware thinks it got something different with big coordinates.
Sign In or Register to comment.