›

When printing from SD, my Prusa MK3s’s randomly stop

francesco78francesco78
in Repetier-Server
Hello everyone ,

maybe my topic is obvious , but I could not find an entry pointing to this issue.
In my makerspace, I have 4 Prusa MK3s connected to a Intel NUC running Repetier Server on Ubuntu. The printers are connected on the NUC 4 USB ports.

Sometimes we want to print from SD instead of from Repetier (this occurs especially when we have guest people or students making prints). I observed that very frequently, a print started from the SD card would just randomly stop. Unplug the USB cable from the printer, the problem is gone.

So it seems pretty much USB related.
Note: it never occurred to me as I was using Octoprint (and there were 3 printers connected on the server).

I understand Repetier server is meant to manage the printers without SD cards. But if it doesn’t allow to do prints from an SD card, it might not be the right option for my makerspace... that would be too bad, because I really like the software and was seriously considering getting the Premium version.

Thanks to everyone who has any ideas related to this issue!
Francesco

Comments

  • RepetierRepetier
    Can you check on console or if you have logging enabled in connected.log what exactly happened at that point?
    As long as no one tries to print over the server sd prints should be ok since we don't send gcodes that influence prints.
    Another point is does server reconnect usb? If so why? That would reset the prusa but as long as no one restarts server that should also be no issue.
  • francesco78francesco78
    Thanks! I'll check all that.
  • francesco78francesco78
    Here are the server logs. That day, we had repeated failures trying to print from SD with the USB cable connected to the printer.


    2021-04-15 14:32:47: Port closed for Prusa MK3S 3 - Doris
    2021-04-15 14:32:47: Connection closed: Prusa MK3S 3 - Doris
    2021-04-15 14:32:48: Connection started: Prusa MK3S 3 - Doris
    2021-04-15 14:32:48: Reset printer Prusa MK3S 3 - Doris
    2021-04-15 14:40:22: Port closed for Prusa MK3S 3 - Doris
    2021-04-15 14:40:22: Connection closed: Prusa MK3S 3 - Doris
    2021-04-15 14:40:23: Connection started: Prusa MK3S 3 - Doris
    2021-04-15 14:40:23: Reset printer Prusa MK3S 3 - Doris
    2021-04-15 15:03:57: Port closed for Prusa MK3S 3 - Doris
    2021-04-15 15:03:57: Connection closed: Prusa MK3S 3 - Doris
    2021-04-15 15:03:58: Connection started: Prusa MK3S 3 - Doris
    2021-04-15 15:03:58: Reset printer Prusa MK3S 3 - Doris
    2021-04-15 16:35:50: Port closed for Prusa MK3S 1 - Maurice
    2021-04-15 16:35:50: Connection closed: Prusa MK3S 1 - Maurice
    2021-04-15 16:35:51: Connection started: Prusa MK3S 1 - Maurice
    2021-04-15 16:35:51: Reset printer Prusa MK3S 1 - Maurice
    2021-04-15 16:42:15: error: Reading serial conection failed: End of file. Closing connection.
    2021-04-15 16:42:15: Port closed for Prusa MK3S 1 - Maurice
    2021-04-15 16:42:15: Connection closed: Prusa MK3S 1 - Maurice
    2021-04-15 16:43:08: error: Reading serial conection failed: End of file. Closing connection.
    2021-04-15 16:43:08: Port closed for Prusa MK3S 3 - Doris
    2021-04-15 16:43:08: Connection closed: Prusa MK3S 3 - Doris

    Does this help?

  • RepetierRepetier
    I also need to know which printer failed when.
    error: Reading serial conection failed: End of file. Closing connection.
    means linux did close the port. Can be because you removed usb manually or because there were power problems and linux did disconnect. But since you said using repetier you have no problems I do not think it is power problem.

    The interesting part might be
    2021-04-15 14:40:22: Port closed for Prusa MK3S 3 - Doris
    2021-04-15 14:40:22: Connection closed: Prusa MK3S 3 - Doris
    2021-04-15 14:40:23: Connection started: Prusa MK3S 3 - Doris
    2021-04-15 14:40:23: Reset printer Prusa MK3S 3 - Doris
    why was it closed here as it reconnected directly.

    Apart from this server.log does not contain any informations. You need to enable logging for printer when not printing  in printer menu. This will start writing to connected.log when not printing after next start or after next regular print. So there you would see if something happened that made server close a connection.
  • francesco78francesco78
    OK, I see.

    Repetier said:
    I also need to know which printer failed when.
    error: Reading serial conection failed: End of file. Closing connection.
    means linux did close the port. Can be because you removed usb manually or because there were power problems and linux did disconnect. But since you said using repetier you have no problems I do not think it is power problem.
    Yes, I think at that point my colleague did unplug the USB cable from the printer to be able to do a SD-card print.

    ... You need to enable logging for printer when not printing  in printer menu. This will start writing to connected.log when not printing after next start or after next regular print. So there you would see if something happened that made server close a connection.
    So, is this the option "Log communication when idle" in the "Log" window of the "printer" view?

  • francesco78francesco78
    Here we go, I think I had one occurrence logged in the "connected" log file:

    Recv:17:19:31.521: tmc2130_goto_step 1 33 2 1000
    Recv:17:19:31.579: tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x02
    Recv:17:19:33.267: echo:busy: processing
    Recv:17:19:35.331: echo:busy: processing
    Recv:17:19:37.395: echo:busy: processing
    Recv:17:19:39.927: echo:busy: processing
    Recv:17:19:41.995: echo:busy: processing
    Recv:17:19:44.064: echo:busy: processing
    Recv:17:19:46.133: echo:busy: processing
    Recv:17:19:48.205: echo:busy: processing
    Recv:17:19:50.302: echo:busy: processing
    Recv:17:19:52.375: echo:busy: processing
    Recv:17:19:53.313: NORMAL MODE: Percent done: 0; print time remaining in mins: 16
    Recv:17:19:53.321: SILENT MODE: Percent done: 0; print time remaining in mins: 16
    Recv:17:19:53.363: ok T:215.0 /215.0 B:60.7 /60.0 T0:215.0 /215.0 @:33 B@:0 P:31.3 A:42.6
    Send:17:19:53.363: N162 M105
    Recv:17:19:53.371: ok T:215.0 /215.0 B:60.7 /60.0 T0:215.0 /215.0 @:33 B@:0 P:31.3 A:42.6
    Send:17:19:53.371: N163 M105
    Recv:17:19:53.375: ok T:215.0 /215.0 B:60.7 /60.0 T0:215.0 /215.0 @:33 B@:0 P:31.3 A:42.6
    Recv:17:19:53.383: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:19:53.383: Resend: 62
    Recv:17:19:53.383: Ignore due to resend: ok
    Recv:17:19:53.383: Ignore due to resend: Unknown G code: G21  
    Send:17:19:53.466: Resend: N62 M105
    Recv:17:19:55.595: echo:busy: processing
    Recv:17:19:57.659: echo:busy: processing
    Recv:17:19:59.334: echo:Advance K=0.05
    Recv:17:19:59.335:  E/D=Auto
    Recv:17:19:59.339: echo:Advance K=30.00
    Recv:17:19:59.339:  E/D=Auto
    Recv:17:19:59.343: Full RX Buffer
    Recv:17:19:59.417: NORMAL MODE: Percent done: 1; print time remaining in mins: 16
    Recv:17:19:59.421: SILENT MODE: Percent done: 0; print time remaining in mins: 16
    Recv:17:19:59.433: NORMAL MODE: Percent done: 1; print time remaining in mins: 16
    Recv:17:19:59.441: SILENT MODE: Percent done: 1; print time remaining in mins: 16
    Mesg:17:20:01.671: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:20:01.671: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 0
    Mesg:17:20:01.671: Buffer used:12 Enforced free byte:0 lines stored:1
    Send:17:20:01.671: Resend: N63 M105
    Recv:17:20:04.295: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:20:04.295: Resend: 62
    Recv:17:20:04.295: Ignore due to resend: ok
    Send:17:20:04.378: Resend: N62 M105
    Recv:17:20:05.466: Full RX Buffer
    Mesg:17:20:08.395: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:20:08.395: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 0
    Mesg:17:20:08.395: Buffer used:12 Enforced free byte:0 lines stored:1
    Send:17:20:08.395: Resend: N63 M105
    Recv:17:20:09.149: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:20:09.149: Resend: 62
    Recv:17:20:09.149: Ignore due to resend: ok
    Send:17:20:09.233: Resend: N62 M105
    Recv:17:20:10.357: Full RX Buffer
    Recv:17:20:10.902: NORMAL MODE: Percent done: 1; print time remaining in mins: 16
    Recv:17:20:10.910: SILENT MODE: Percent done: 2; print time remaining in mins: 16
    Recv:17:20:10.980: NORMAL MODE: Percent done: 2; print time remaining in mins: 16
    Recv:17:20:10.984: SILENT MODE: Percent done: 2; print time remaining in mins: 16
    Mesg:17:20:13.250: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:20:13.250: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 0
    Mesg:17:20:13.250: Buffer used:12 Enforced free byte:0 lines stored:1
    Send:17:20:13.250: Resend: N63 M105
    Recv:17:20:13.266: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:20:13.266: Resend: 62
    Recv:17:20:13.266: Ignore due to resend: ok
    Send:17:20:13.350: Resend: N62 M105
    Recv:17:20:13.675: Full RX Buffer
    Recv:17:20:16.494: NORMAL MODE: Percent done: 3; print time remaining in mins: 16
    Recv:17:20:16.497: SILENT MODE: Percent done: 2; print time remaining in mins: 16
    Recv:17:20:16.506: NORMAL MODE: Percent done: 3; print time remaining in mins: 16
    Recv:17:20:16.510: SILENT MODE: Percent done: 3; print time remaining in mins: 16
    Mesg:17:20:17.360: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:20:17.360: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 0
    Mesg:17:20:17.360: Buffer used:12 Enforced free byte:0 lines stored:1
    Send:17:20:17.360: Resend: N63 M105
    Recv:17:20:18.582: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:20:18.583: Resend: 62
    Recv:17:20:18.583: Ignore due to resend: ok
    Send:17:20:18.666: Resend: N62 M105
    Recv:17:20:19.393: Full RX Buffer
    Mesg:17:20:22.677: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:20:22.677: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 0
    Mesg:17:20:22.678: Buffer used:12 Enforced free byte:0 lines stored:1
    Send:17:20:22.678: Resend: N63 M105
    Recv:17:20:22.875: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:20:22.879: Resend: 62
    Recv:17:20:22.879: Ignore due to resend: ok
    Send:17:20:22.963: Resend: N62 M105
    Recv:17:20:23.846: Full RX Buffer
    Mesg:17:20:26.975: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:20:26.975: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 0
    Mesg:17:20:26.975: Buffer used:12 Enforced free byte:0 lines stored:1
    Send:17:20:26.975: Resend: N63 M105
    Recv:17:20:26.992: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:20:26.992: Resend: 62
    Recv:17:20:26.992: Ignore due to resend: ok
    Recv:17:20:27.000: Ignore due to resend: NORMAL MODE: Percent done: 4; print time remaining in mins: 16
    Recv:17:20:27.004: Ignore due to resend: SILENT MODE: Percent done: 3; print time remaining in mins: 16
    Recv:17:20:27.012: Ignore due to resend: NORMAL MODE: Percent done: 4; print time remaining in mins: 16
    Recv:17:20:27.020: Ignore due to resend: SILENT MODE: Percent done: 4; print time remaining in mins: 16
    Send:17:20:27.083: Resend: N62 M105
    Recv:17:20:28.110: Full RX Buffer
    Mesg:17:20:31.103: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:20:31.104: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 0
    Mesg:17:20:31.104: Buffer used:12 Enforced free byte:0 lines stored:1
    Send:17:20:31.104: Resend: N63 M105
    Recv:17:20:31.710: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:20:31.711: Resend: 62
    Recv:17:20:31.711: Ignore due to resend: ok
    Send:17:20:31.793: Resend: N62 M105
    Recv:17:20:34.291: Full RX Buffer
    Recv:17:20:35.647: NORMAL MODE: Percent done: 5; print time remaining in mins: 16
    Recv:17:20:35.651: SILENT MODE: Percent done: 4; print time remaining in mins: 16
    Recv:17:20:35.659: NORMAL MODE: Percent done: 5; print time remaining in mins: 16
    Recv:17:20:35.663: SILENT MODE: Percent done: 5; print time remaining in mins: 16
    Mesg:17:20:35.807: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:20:35.807: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 0
    Mesg:17:20:35.807: Buffer used:12 Enforced free byte:0 lines stored:1
    Send:17:20:35.807: Resend: N63 M105
    Recv:17:20:37.031: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:20:37.035: Resend: 62
    Mesg:17:20:37.036: Receiving only error messages. Reset communication for printer Prusa MK3S 1 - Maurice.
    Recv:17:20:37.038: Response while unconnected:ok
    Recv:17:20:37.041: ok
    Mesg:17:20:38.042: Dtr: true Rts: true
    Mesg:17:20:38.042: Connection started
    Mesg:17:20:38.042: Dtr: false Rts: false
    Mesg:17:20:38.063: Dtr: true Rts: true
    Send:17:20:38.074: N1 M105
    Send:17:20:39.078: N2 M105
    Recv:17:20:39.109: start
    Send:17:20:39.110: N1 M110
    Send:17:20:39.110: N2 M105
    Send:17:20:39.110: N3 M115 ; Get firmware capabilities and info
    Send:17:20:39.110: N4 M220 S100 ; Speed multiplier 100%
    Send:17:20:39.110: N5 M221 S100 ; Flow multiplyer 100%
    Send:17:20:39.110: N6 G92 E0
    Send:17:20:39.111: N7 G90
    Send:17:20:39.111: N8 M82
    Recv:17:20:39.112: echo: 3.8.1-2869
    Recv:17:20:39.121: echo: Last Updated: Oct 24 2019 17:11:58 | Author: (none, default config)
    Recv:17:20:39.121: Compiled: Oct 24 2019
    Recv:17:20:39.129: echo: Free Memory: 2123  PlannerBufferBytes: 1392
    Recv:17:20:39.129: echo:Stored settings retrieved
    Recv:17:20:39.133: adc_init
    Recv:17:20:39.473: CrashDetect ENABLED!
    Recv:17:20:40.558: FSensor ENABLED
    Recv:17:20:40.779: echo:SD card ok
    Recv:17:20:41.373: echo:busy: processing
    Recv:17:20:43.593: echo:busy: processing
    Recv:17:20:45.756: echo:busy: processing
    Recv:17:20:46.883: Error:No Line Number with checksum, Last Line: 0
    Recv:17:20:46.887: Resend: 1
    Recv:17:20:46.887: Ignore due to resend: ok
    Send:17:20:46.970: Resend: N1 M110
    Recv:17:20:46.997: ok
    Send:17:20:46.997: Resend: N2 M105
    Recv:17:20:47.006: ok T:212.1 /0.0 B:60.0 /0.0 T0:212.1 /0.0 @:0 B@:0 P:35.3 A:41.9
    Send:17:20:47.006: Resend: N3 M115 ; Get firmware capabilities and info
    Recv:17:20:47.030: FIRMWARE_NAME:Prusa-Firmware 3.8.1 based on Marlin FIRMWARE_URL:https://github.com/prusa3d/Prusa-Firmware PROTOCOL_VERSION:1.0 MACHINE_TYPE:Prusa i3 MK3S EXTRUDER_COUNT:1 UUID:00000000-0000-0000-0000-000000000000
    Recv:17:20:47.031: ok
    Send:17:20:47.031: Resend: N4 M220 S100 ; Speed multiplier 100%
    Recv:17:20:47.034: ok
    Send:17:20:47.034: Resend: N5 M221 S100 ; Flow multiplyer 100%
    Recv:17:20:47.038: ok
    Send:17:20:47.038: Resend: N6 G92 E0
    Recv:17:20:47.042: ok
    Send:17:20:47.042: Resend: N7 G90
    Recv:17:20:47.046: ok
    Send:17:20:47.046: Resend: N8 M82
    Send:17:20:47.047: N9 G21 ; Use mm as unit
    Send:17:20:47.047: N10 M114
    Send:17:20:47.047: @getip
    Send:17:20:47.049: N11 M105
    Send:17:20:47.049: M117 192.168.1.8:3344
    Send:17:20:47.049: N12 M105
    Recv:17:20:47.050: ok
    Recv:17:20:47.055: Unknown G code: $9 G21

    The SD-card print stopped on the machine at 17:20 something, so not sure where this is on the log, but I guess this is more complete information for you...


  • francesco78francesco78
    I had another occurrence, and now I am quite sure that the print stops at the lines in bold below:

    Send:17:29:33.318: N16 M105
    Recv:17:29:33.330: ok T:209.2 /0.0 B:59.9 /0.0 T0:209.2 /0.0 @:0 B@:0 P:38.6 A:41.2
    Send:17:29:34.322: N17 M105
    Recv:17:29:34.334: ok T:208.4 /0.0 B:59.8 /0.0 T0:208.4 /0.0 @:0 B@:0 P:38.6 A:41.4
    Send:17:29:35.315: @getip
    Send:17:29:35.318: M117 192.168.1.8:3344
    Send:17:29:35.318: N18 M105
    Recv:17:29:35.325: ok
    Recv:17:29:35.329: ok T:207.5 /0.0 B:59.8 /0.0 T0:207.5 /0.0 @:0 B@:0 P:38.7 A:41.5
    Send:17:29:36.330: N19 M105
    Recv:17:29:36.341: ok T:206.7 /0.0 B:59.7 /0.0 T0:206.7 /0.0 @:0 B@:0 P:38.7 A:41.2
    Send:17:29:37.333: N20 M105
    Recv:17:29:37.344: ok T:206.4 /0.0 B:59.7 /0.0 T0:206.4 /0.0 @:0 B@:0 P:38.8 A:41.2
    Send:17:29:38.337: N21 M105
  • francesco78francesco78
    And here is the log from the "console" window. Different occurrence than the logs above, but same behavior.
    The print was interrupted at the exact same moment.
    The print stops at the line in bold:

    Mesg:17:56:47.098: Buffer used:14 Enforced free byte:0 lines stored:1
    Recv:17:56:47.290: Error:Line Number is not Last Line Number+1, Last Line: 1056
    Recv:17:56:47.290: Resend: 1057
    Recv:17:56:48.260: Full RX Buffer
    Mesg:17:56:51.390: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:56:51.390: Connection status: Buffered:14, Manual Commands: 1, Job Commands: 0
    Mesg:17:56:51.390: Buffer used:14 Enforced free byte:0 lines stored:1
    Recv:17:56:51.406: Error:Line Number is not Last Line Number+1, Last Line: 1056
    Recv:17:56:51.407: Resend: 1057
    Recv:17:56:52.524: Full RX Buffer
    Mesg:17:56:55.513: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:56:55.513: Connection status: Buffered:14, Manual Commands: 1, Job Commands: 0
    Mesg:17:56:55.513: Buffer used:14 Enforced free byte:0 lines stored:1
    Recv:17:56:56.121: Error:Line Number is not Last Line Number+1, Last Line: 1056
    Recv:17:56:56.125: Resend: 1057
    Recv:17:56:58.706: Full RX Buffer
    Mesg:17:57:00.221: Warning: Communication timeout - resetting communication buffer.
    Mesg:17:57:00.221: Connection status: Buffered:14, Manual Commands: 1, Job Commands: 0
    Mesg:17:57:00.221: Buffer used:14 Enforced free byte:0 lines stored:1
    Recv:17:57:01.446: Error:Line Number is not Last Line Number+1, Last Line: 1056
    Recv:17:57:01.446: Resend: 1057
    Mesg:17:57:01.447: Receiving only error messages. Reset communication for printer Prusa MK3S 1 - Maurice.
    Recv:17:57:01.452: Response while unconnected:ok
    Mesg:17:57:02.456: Dtr: true Rts: true
    Mesg:17:57:02.456: Connection started
    Mesg:17:57:02.456: Dtr: false Rts: false
    Mesg:17:57:02.477: Dtr: true Rts: true
    Recv:17:57:03.524: start
    Recv:17:57:03.527: echo: 3.8.1-2869
    Recv:17:57:03.535: echo: Last Updated: Oct 24 2019 17:11:58 | Author: (none, default config)
    Recv:17:57:03.535: Compiled: Oct 24 2019
    Recv:17:57:03.539: echo: Free Memory: 2123 PlannerBufferBytes: 1392
    Recv:17:57:03.543: echo:Stored settings retrieved
    Recv:17:57:03.547: adc_init
    Recv:17:57:03.887: CrashDetect ENABLED!
    Recv:17:57:04.973: FSensor ENABLED
    Recv:17:57:05.194: echo:SD card ok
    Recv:17:57:11.301: Error:No Line Number with checksum, Last Line: 0
    Recv:17:57:11.302: Resend: 1
    Recv:17:57:11.445: FIRMWARE_NAME:Prusa-Firmware 3.8.1 based on Marlin FIRMWARE_URL:https://github.com/prusa3d/Prusa-Firmware PROTOCOL_VERSION:1.0 MACHINE_TYPE:Prusa i3 MK3S EXTRUDER_COUNT:1 UUID:00000000-0000-0000-0000-000000000000
    Recv:17:57:11.469: Unknown G code: $9 G21
    Recv:17:57:11.473: X:0.00 Y:0.00 Z:0.00 E:0.00 Count X: 0.00 Y:0.00 Z:0.00 E:0.00

  • RepetierRepetier
    Ok lets take this one:
    Send:17:19:53.363: N162 M105
    Recv:17:19:53.371: ok T:215.0 /215.0 B:60.7 /60.0 T0:215.0 /215.0 @:33 B@:0 P:31.3 A:42.6
    Send:17:19:53.371: N163 M105
    Recv:17:19:53.375: ok T:215.0 /215.0 B:60.7 /60.0 T0:215.0 /215.0 @:33 B@:0 P:31.3 A:42.6
    Recv:17:19:53.383: Error:Line Number is not Last Line Number+1, Last Line: 61
    Recv:17:19:53.383: Resend: 62

    that is strange. It looks like it accepting M105 with line 162 and when sending line 163 prusa says last line was 61. Resends are taken as error so in the end server disconnects it, reconnects and resets prusa with this.

    What is your communication settings in server - especially how big is the buffer that it fits 100 commands? I'm pretty sure prusa buffer only has 127 byte. For debugging the problem ping pong mode would be the best so you know to which command a "ok" response belongs to. Will also check if I can reproduce it on my prusa.
    M117 in general is no problem. But it gets send without line number since older marlin versions could not handle it with line numbers or choked on checksum.
  • francesco78francesco78
    Hi! I can check the buffer size setting, but I can't find where the option is. Can you tell me?
  • francesco78francesco78

    that is strange. It looks like it accepting M105 with line 162 and when sending line 163 prusa says last line was 61. Resends are taken as error so in the end server disconnects it, reconnects and resets prusa with this.
    As said, I have 4 printers connected. Is that possible that the communication of the server to the currently active printer is disturbed by the other printers? I have done nothing specific to configure a different address for each printer, I just let Repetier do the network addressing by itself.
  • RepetierRepetier
    No, each printer has an own thread only listening to it's port. But I assume you have set port names /dev/serial/by-path or by-id if they differ.
  • francesco78francesco78
    Yes, they are set by ID, so each one of them differ.
    What do you suggest to do to understand why the problem occurs? Should I activate "ping-pong mode"? Are there any other tests you would like me to do?
  • RepetierRepetier
    As soon as I get some time I will try with my mk3 and hope to get same problems, so I can analyse them locally. ping-Pong helps anaylsing where it fails since only one command is waiting so ok is aways for the previous one. So if you see anything with that report and hope I can reproduce it with one prusa as well.
  • francesco78francesco78
    OK, I will then enable the ping-pong mode, provoke the error (it is actually easy to do on my setup) and post you the logs.
    For my information, is this issue a known one, or maybe even an unsupported use case? Or is probably my specific setup the reason of the failure?
  • RepetierRepetier
    I never heard about that problem, but since we do not officially support sd card I did not test it. But I also haven't written anything to make it fail knowingly and I always expected it to be no problem since we only send non-intrusive commands. Only when printer resets on connect a new connection due to server restart would be a case where I expect sd to fail.
Sign In or Register to comment.