›

Prints long then 8 hours will not finish with Repetier-Server on PI

maverickcciemaverickccie
in Repetier-Server
I am running Repetier-Server Pro on a Raspberry PI with a 7" touch screen. When ever I have a print that is long then 8 hours the print finishes on  on the printer and the hot end, bed , and cooling fan all shut off, however Repetier-Server says there is still 6 seconds left. I can cancel the print, but it just puts the print in the queue and will not delete it form the queue or start a new print. The bad part is I am running three of these PI touch units with Repetier-Sever on them each controlling two printers, and no matter what printer or PI unit any print over 8 hours does this. The worst part is the only way to clear it up is to reboot the server and delete the print form the queue. Before you ask yes I have tried with only one printer attached and get the same result.

All three servers are Raspberry Pi 3's
The printer are:
AnyCubic Kossel
AnyCubic I3 Mega
Robo3D R1+
Prusa MK2S
Folgertech FT-5
Tevo Tornado

I use Simplify3d for slicing.

Comments

  • RepetierRepetier
    Can you enable logging and show where it stopped and the last 500 commands in gcode and also what you have in the end gcode definition of your printer. It sounds like some command never finishes also server did not expect it to take time at all. And since this prevented server to send the last commands it never finishes.

    There is no need to restart server I think. You could just run an emergency stop and then delete the file. But would like to find out why it blocks and where the problem exactly lies.
  • maverickcciemaverickccie
    Here is the ending gcode
     ; layer end
    M104 S0 ; turn off extruder
    M140 S0 ; turn off bed
    M107
    G28 X Y ; home x and y axes
    M84 ; disable motors

    I have tried emergency stop does not clear the print. When I start a new print the the server starts it but never sends the code to the printer until a reboot is done. I will enable logging.
  • RepetierRepetier
    Does not look like blocking commands. Does it execute the homing at the end and disabling motors? 
    Do you make a timelapse video so that it could be the conversion? Also I'm quite such this happens in background but starting it can take a while, especially if the images get transferred to another pc for faster conversion.

    You could also check for messages in server.log in /var/lib/Repetier-Server/logs if it shows anything going wrong.
  • maverickcciemaverickccie
    I did a 17 hour print and like clock work it happened again. I did an emergency stop , but still had to restart the server before it would start another print.  Before the reboot I reconnected the printer and started print, the server never sent any commands to printer the printer log was empty! Here is what was in the log after the 17 hour print:

    Messages log:

    Apr 19 06:25:04 RepetierServer rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="428" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
    Apr 20 06:25:04 RepetierServer rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="428" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

    Syslog:

    Apr 20 10:12:34 RepetierServer dbus[437]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    Apr 20 10:12:34 RepetierServer systemd[1]: Starting Network Manager Script Dispatcher Service...
    Apr 20 10:12:34 RepetierServer dbus[437]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    Apr 20 10:12:34 RepetierServer nm-dispatcher: Dispatching action 'dhcp4-change' for wlan0
    Apr 20 10:12:34 RepetierServer systemd[1]: Started Network Manager Script Dispatcher Service.

    Print log:

    < 10:14:20.209: N2263202 G1 X153.582 Y132.453 E0.0209
    > 10:14:20.225: ok
    < 10:14:20.225: N2263203 G1 X154.025 Y132.113 E0.0209
    > 10:14:20.241: ok
    < 10:14:20.242: N2263204 G1 X154.543 Y131.898 E0.0210
    > 10:14:20.262: ok
    < 10:14:20.262: N2263205 G1 X154.680 Y131.881 E0.0051
    > 10:14:20.278: ok
    < 10:14:20.279: N2263206 G1 X154.878 Y131.854 F1920
    > 10:14:20.294: ok
    < 10:14:20.294: N2263207 G1 E-2.0000 F1800
    > 10:14:20.344: ok
    < 10:14:20.344: N2263208 M104 S0 ; turn off temperature
    < 10:14:20.345: N2263209 M140 S0 ; turn off heatbed
    > 10:14:20.384: ok
    < 10:14:20.384: N2263210 M107 ; turn off fan
    < 10:14:20.385: N2263211 G1 X0 Y200; home X axis
    > 10:14:20.392: ok
    < 10:14:20.392: N2263212 M84 ; disable motors
    > 10:14:20.602: ok
    > 10:14:20.602: ok
    > 10:14:20.602: ok
    > 10:14:21.666: ok
    > 10:14:27.499: ok
    > 10:14:51.396: Warning: Communication timeout - resetting communication buffer.
    > 10:14:51.397: Connection status: Buffered:0, Manual Commands: 2, Job Commands: 0
    > 10:14:51.397: Buffer used:0 Enforced free byte:8160724 lines stored:0
    < 10:14:51.397: M117 Finished
    < 10:14:51.397: N2263213 M105
    < 10:14:51.397: N2263214 M105
    > 10:14:51.547: ok
    > 10:14:51.548: ok T:215.8 /0.0 B:88.0 /0.0 T0:215.8 /0.0 @:0 B@:0
    > 10:14:51.548: ok T:215.8 /0.0 B:88.0 /0.0 T0:215.8 /0.0 @:0 B@:0
    > 10:15:22.399: Warning: Communication timeout - resetting communication buffer.
    > 10:15:22.399: Connection status: Buffered:0, Manual Commands: 1, Job Commands: 0
    > 10:15:22.399: Buffer used:0 Enforced free byte:8160724 lines stored:0
    < 10:15:22.400: N2263215 M105
    < 10:15:22.400: N2263216 M105
    > 10:15:22.580: ok T:193.9 /0.0 B:84.7 /0.0 T0:193.9 /0.0 @:0 B@:0
    > 10:15:22.581: ok T:193.9 /0.0 B:84.7 /0.0 T0:193.9 /0.0 @:0 B@:0
    > 10:15:53.403: Warning: Communication timeout - resetting communication buffer.
    > 10:15:53.403: Connection status: Buffered:0, Manual Commands: 1, Job Commands: 0
    > 10:15:53.403: Buffer used:0 Enforced free byte:8160724 lines stored:0
    < 10:15:53.404: N2263217 M105
    < 10:15:53.404: N2263218 M105
    > 10:15:53.550: ok T:175.1 /0.0 B:81.7 /0.0 T0:175.1 /0.0 @:0 B@:0
    > 10:15:53.551: ok T:175.1 /0.0 B:81.7 /0.0 T0:175.1 /0.0 @:0 B@:0
    > 10:16:24.410: Warning: Communication timeout - resetting communication buffer.
    > 10:16:24.410: Connection status: Buffered:0, Manual Commands: 1, Job Commands: 0
    > 10:16:24.410: Buffer used:0 Enforced free byte:8160724 lines stored:0
    < 10:16:24.411: N2263219 M105
    < 10:16:24.411: N2263220 M105
    > 10:16:24.596: ok T:158.7 /0.0 B:79.1 /0.0 T0:158.7 /0.0 @:0 B@:0
    > 10:16:24.596: ok T:158.7 /0.0 B:79.1 /0.0 T0:158.7 /0.0 @:0 B@:0
    > 10:16:55.421: Warning: Communication timeout - resetting communication buffer.
    > 10:16:55.421: Connection status: Buffered:0, Manual Commands: 1, Job Commands: 0
    > 10:16:55.421: Buffer used:0 Enforced free byte:8160724 lines stored:0
    < 10:16:55.422: N2263221 M105
    < 10:16:55.422: N2263222 M105
    > 10:16:55.570: ok T:144.3 /0.0 B:76.6 /0.0 T0:144.3 /0.0 @:0 B@:0
  • RepetierRepetier
    You should enable firmware to include line numbers. Makes debugging easier and also improves communication as we can then see if we missed an ok.

    Did it move to park position and disable motors? With the timeouts at the end it seems the firmware gets unresponsible but on the other side it acknowledges 2 M105 before the next timeout. I also see in the response that temperatures got disabled so whatever happens happens after that.

    Are these timeouts always when you get the problem?

    And if I understood you right, after short prints they finish the same just without this communication errors?
Sign In or Register to comment.