Repetier Server Pro 0.92.0, Raspberry Pi 4, Random Stop Printing

Hello,
I realized it now twice that that my printer freeze during a print. 
The last time 2 at the exact same moment. 

My Geeetech A30 Stopped completly, the Geeeetech A20M just go veeeeeeeeery veeeeeeeeeeery slow.

On the console of the A30 it just repeat's the last 3 lines over and over again without reaction. 
The Temperature stayed stable on both mashines

Any solutions ? 

Comments

  • To find the reason more information is needed.
    Did the printers get disconnected from server and job stop?
    What are the lines getting repeated?
    Also check with ACK/Commands in log enabled to see all communication.
    Any messages in /var/lib/Repetier-Server/logs/server.log or /var/log/syslog
    around the time it happened.
    One typical reason for problems is undervoltage that caused disconnection of usb ports and hence disconnect printers so server stops printing in that case. So that is first thing to test. Have no experience with pi 4 but pi 0 - pi 3+ had that problem and pi 4 might use even more power. Also same time for all printers points towards that problem if they run on the same pi.


  • edited August 18
    no the printer showed still connected. 

    what i just realized, i also not able to start a new print job without reconnect the printer.

    Edit, found this before: 

    < 23:00:12.011: N608220 G1 X218.207 Y215.904 E3.13490
    > 23:00:12.107: ok
    < 23:00:12.107: N608221 G1 X218.197 Y209.927 E3.29461
    > 23:00:12.123: ok
    < 23:00:12.123: N608222 G1 X218.245 Y209.507 E3.30592
    > 23:00:12.139: ok
    < 23:00:12.139: N608223 G1 X218.294 Y209.341 E3.31053
    > 23:00:43.146: Warning: Communication timeout - resetting communication buffer.
    > 23:00:43.146: Connection status: Buffered:41, Manual Commands: 2, Job Commands: 5000
    > 23:00:43.146: Buffer used:41 Enforced free byte:41 lines stored:1
    < 23:00:43.146: M117 ETA 23:15:51 day 17
    > 23:01:14.149: Warning: Communication timeout - resetting communication buffer.
    > 23:01:14.149: Connection status: Buffered:25, Manual Commands: 2, Job Commands: 5000
    > 23:01:14.150: Buffer used:25 Enforced free byte:18 lines stored:1
    < 23:01:14.150: M117 ETE 00:15:34
    < 23:01:14.150: N608224 M105
    > 23:01:45.158: Warning: Communication timeout - resetting communication buffer.
    > 23:01:45.158: Connection status: Buffered:34, Manual Commands: 2, Job Commands: 5000
    > 23:01:45.158: Buffer used:34 Enforced free byte:21 lines stored:2
    > 23:01:45.158: Warning: Too many timeouts without response - disabling timeout message!
    < 23:01:45.159: M117 Layer 1036/1102
    < 23:01:45.159: N608225 M105
    < 23:02:16.168: M117 ETA 23:17:21 day 17
    < 23:02:47.178: M117 ETE 00:15:34
    < 23:02:47.179: N608226 M105


    it continues like this for hours

    <  1:17:08.497: M117 ETA 01:32:16 day 18
    <  1:17:39.506: M117 ETE 00:15:34
    <  1:17:39.506: N608400 M105
    <  1:18:10.507: M117 Layer 1036/1102
    <  1:18:10.507: N608401 M105
    <  1:18:41.510: M117 ETA 01:33:46 day 18
    <  1:19:12.518: M117 ETE 00:15:34
    <  1:19:12.518: N608402 M105
    <  1:19:43.527: M117 Layer 1036/1102
    <  1:19:43.527: N608403 M105
    <  1:20:14.532: M117 ETA 01:35:26 day 18
    <  1:20:45.536: M117 ETE 00:15:34
    <  1:21:16.543: M117 Layer 1036/1102
    <  1:21:47.552: M117 ETA 01:36:56 day 18
    <  1:22:18.556: M117 ETE 00:15:34
    <  1:22:49.562: M117 Layer 1036/1102
    <  1:23:20.566: M117 ETA 01:38:26 day 18
    <  1:23:51.569: M117 ETE 00:15:34
    <  1:24:22.577: M117 Layer 1036/1102
    <  1:24:53.583: M117 ETA 01:40:06 day 18
    <  1:25:24.593: M117 ETE 00:15:34
    <  1:25:55.601: M117 Layer 1036/1102
    <  1:26:26.605: M117 ETA 01:41:36 day 18
    <  1:26:57.611: M117 ETE 00:15:34
    <  1:27:28.613: M117 Layer 1036/1102
    <  1:27:59.615: M117 ETA 01:43:06 day 18
    <  1:28:30.616: M117 ETE 00:15:34

    i got the original pi psu for the rp4 so i hope thats not the source of trouble. 
    i can still control other printers or go through the web menu. 

    can i reach log you wanted via the web interface ? 

  • here i tried to reconnect and hoped to continue with the rescue option 
     9:18:45.301: M117 Layer 1036/1102
    <  9:19:16.303: M117 ETA 09:34:23 day 18
    <  9:19:38.280: N608404 M112
    <  9:19:49.321: N608405 M105
    >  9:19:50.314: JumpToApp0
    <  9:19:50.325: N608406 M105
    >  9:19:50.330: JumpToApp1
    >  9:19:50.346: Response while unconnected:MACHINE_TYPE:A30 UUID:                        FIRMWARE_NAME:V1.xx.59
    >  9:19:50.346: Response while unconnected:MACHINE_TYPE:A30 UUID:                        FIRMWARE_NAME:V1.xx.59
    >  9:19:50.346: MACHINE_TYPE:A30 UUID:                        FIRMWARE_NAME:V1.xx.59
    >  9:19:50.442: Response while unconnected:PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1
    >  9:19:50.442: Response while unconnected:PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1
    >  9:19:50.442: PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1
    >  9:19:50.554: echo:SD init fail
    >  9:19:50.570: echo:Unknown command: 
    >  9:19:50.570: Response while unconnected:ok
    >  9:19:50.573: ok
    <  9:19:50.573: N1 M110
    <  9:19:50.574: N2 M105
    <  9:19:50.574: N3 M115
    <  9:19:50.574: N4 M220 S100
    <  9:19:50.574: N5 M221 S100
    <  9:19:50.574: N6 G92 E0
    <  9:19:50.574: N7 G90
    <  9:19:50.574: N8 M82
    >  9:19:50.586: ok
    >  9:19:50.586: ok
    <  9:19:50.586: N9 G21
    <  9:19:50.587: @getip
    >  9:19:50.615: ok T:0.0 /0.0 B:0.0 /0.0 T0:0.0 /0.0 T1:0.0 /0.0 T2:0.0 /0.0 F:0 R:0 @:0 B@:0
    >  9:19:52.194: Error0: Line Number is not Last Line Number+1, Last Line: 0
    >  9:19:52.194: Resend: 1
    >  9:19:52.205: ok
    <  9:19:52.206: Resend: N1 M110
    <  9:19:52.206: Resend: N2 M105
    <  9:19:52.206: Resend: N3 M115
    <  9:19:52.206: Resend: N4 M220 S100
    <  9:19:52.206: Resend: N5 M221 S100
    <  9:19:52.206: Resend: N6 G92 E0
    <  9:19:52.206: Resend: N7 G90
    <  9:19:52.206: Resend: N8 M82
    >  9:19:52.238: ok
    >  9:19:52.238: ok T:0.0 /0.0 B:0.0 /0.0 F:0 R:100 @:0 B@:0
    >  9:19:52.239: MACHINE_TYPE:A30 UUID:                        FIRMWARE_NAME:V1.xx.59
    <  9:19:52.239: Resend: N9 G21
    >  9:19:52.334: PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1
    >  9:19:52.446: ok
    >  9:19:52.446: ok
    >  9:19:52.446: ok
    >  9:19:52.446: ok
    >  9:19:52.446: ok
    >  9:19:52.447: ok
    <  9:19:52.447: M117 192.168.178.120:3344
    <  9:19:52.447: N10 M105
    <  9:19:52.447: N11 M105
    >  9:19:52.462: ok
    >  9:19:52.462: ok
    >  9:19:52.483: ok T:0.0 /0.0 B:0.0 /0.0 F:0 R:100 @:0 B@:0
    >  9:19:52.483: ok T:0.0 /0.0 B:0.0 /0.0 F:0 R:100 @:0 B@:0
    <  9:19:53.453: N12 M105
    >  9:19:53.475: ok T:217.2 /0.0 B:58.0 /0.0 F:0 R:100 @:0 B@:0
    <  9:19:54.455: N13 M105
  • checked via putty 

    /var/lib/Repetier-Server/logs/server.log
    Nothink happend at this time

    var/log/syslog
    just shows some time & date service actions, also only from today no days back

  • server.log rotates on daily basis. Old log is then server.log.0

    In the log of the hanging case you see that firmware stopped responding with "ok". Knowing this normally does not happen I think problem was that the driver on one of the sides got a problem not sending the backwards data to server any more. That is a problem that sometimes also happens, also I never had it. But I have seen it happen for others sometimes. That is not the disconnect from undervoltage! That is why server.log showed no reconnect.

    I assume reconnect was successful as I see "ok" came back when it was reinitialized.
  • had now 2 sucessfull prints over 5 hours, will keep an eye on it if it happens again

Sign In or Register to comment.