Printers disconnect after each print after update to 1.4.8

p_vnct

Hallo !

updated yesterday Repetier Server and since i get a weird issue:
Indeed after each print it's like Repetier Server Send a Reset to the printer but it get stuck and i have to manually turn off the printers then bak on and they are again alive and connected to the server.

Repetier is running on a Mac M1 and is connected only to Duet 3 mini 5+ printers via ethernet.

What's weird is that after each print on each printer, even the duet interface becomes unaccessible and this behaviour started right after the update - settings for all printers does not have been modified.

here is the end of log of a print that does this issue:

Recv:11:06:37.928: ok

Send:11:06:37.928: Slow command added:M400 ; Wait for current moves to finish, clearing the buffer

Send:11:06:37.928: N237891 M400 ; Wait for current moves to finish, clearing the buffer

Mesg:11:06:57.928: Warning: Communication timeout - resetting communication buffer.

Mesg:11:06:57.928: This means that a expected firmware response was not seen within the expected time.

Mesg:11:06:57.928: The typical reason is a communication error and print should continue after the communication reset.

Mesg:11:06:57.928: Connection status: Buffered:16, Manual Commands: 2, Job Commands: 3

Mesg:11:06:57.928: Buffer used:16 Enforced free byte:30 lines stored:1

Send:11:06:57.928: N237892 M117 S"Layer 123/101"

Send:11:06:57.928: N237893 M408 S2

Send:11:06:57.928: N237894 M408 S2

Send:11:06:57.928: N237895 M104 T0 S0 ; Disable extruder

Send:11:06:57.928: N237896 M140 S0 ; Disable bed

Send:11:06:57.928: N237897 G1 X0 Y0 F9000

Send:11:06:58.002: @stopLog

We can see a communication timeout which i guess should not be there comparing to other normal logs before update.

Is there something in the connection settings that should be modified to avoid this ?

Thanks

Repetier

Can you provide a full log of this e.g. via pastebin?

We now switch to ping-pong mode around slow commands and if an "ok" is missing that would cause a timeout. What I do not understand from what I see is why no ok appears afterwards. Especially if it happens with all prints at that part there must be reason. Also why does it count layer 123 of 101 is strange. So if you can provide the gcode as well if it is not secret might help with searching.

Instead of turning printers off/on you can also in printer menu disable printer and activate it again. Should behave the same.

p_vnct

Hello,

i can't provide full gcodes log publicly and i don't think gcodes are the issues as all the gcodes were running without problem with Repetier server 1.4.2 before the update.
- is there a way to download back this 1.4.2 version and roll back ?

This morning i came back and almost all the printers were disconnected.

Note that i't's not just disconnected where i could deactivate and reactivate the printer:
No no no.
it's like repetier does something like a reset command / close connection (perhaps the ping pong mode around slow command ..? Ping pong mode is deactivated in the printers settings) to the printer after each print (and sometimes even during the print !)

so the printer get stuck and even its own duet web interface is not even accessible.

that's why i have to turn Off/on the printer and this morning had to do it on almost all the printers on this server !

So i suppect something new in the way the server handle the connection with the duet that completely brick the duet.
here is the server logs of this night when this happens :

2023-02-15 21:52:14: Print of PLT_OSL_12_0.35mm_PLA_4h17m_211.12g on printer COREXY 16 finished. Send 477356 lines. Printing time: 5:33:11

2023-02-15 23:02:09: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-15 23:02:09: Connection closed: COREXY 20

2023-02-16 00:09:33: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 08 finished. Send 287136 lines. Printing time: 8:19:44

2023-02-16 00:09:40: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 09 finished. Send 287136 lines. Printing time: 8:19:32

2023-02-16 00:09:44: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 06 finished. Send 287136 lines. Printing time: 8:20:27

2023-02-16 00:11:00: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:11:00: Connection closed: COREXY 08

2023-02-16 00:11:11: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:11:11: Connection closed: COREXY 06

2023-02-16 00:11:14: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:11:14: Connection closed: COREXY 09

2023-02-16 00:12:00: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 14 finished. Send 287136 lines. Printing time: 8:20:13

2023-02-16 00:12:03: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 12 finished. Send 287136 lines. Printing time: 8:20:47

2023-02-16 00:12:24: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 13 finished. Send 287136 lines. Printing time: 8:20:57

2023-02-16 00:13:28: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:13:28: Connection closed: COREXY 14

2023-02-16 00:13:31: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:13:31: Connection closed: COREXY 12

2023-02-16 00:13:52: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:13:52: Connection closed: COREXY 13

2023-02-16 00:13:54: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 18 finished. Send 287136 lines. Printing time: 8:20:28

2023-02-16 00:15:21: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:15:21: Connection closed: COREXY 18

2023-02-16 00:18:11: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 10 finished. Send 287136 lines. Printing time: 8:18:05

2023-02-16 00:19:39: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:19:39: Connection closed: COREXY 10

2023-02-16 00:20:30: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 02 finished. Send 287136 lines. Printing time: 8:18:25

2023-02-16 00:21:08: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 05 finished. Send 287136 lines. Printing time: 8:18:00

2023-02-16 00:21:57: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:21:57: Connection closed: COREXY 02

2023-02-16 00:22:37: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 00:22:37: Connection closed: COREXY 05

2023-02-16 00:59:55: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 25 finished. Send 287136 lines. Printing time: 9:02:58

2023-02-16 01:01:22: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 01:01:22: Connection closed: COREXY 25

2023-02-16 01:20:26: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 22 finished. Send 287136 lines. Printing time: 9:00:51

2023-02-16 01:21:39: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 21 finished. Send 287136 lines. Printing time: 9:04:42

2023-02-16 01:21:53: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 01:21:53: Connection closed: COREXY 22

2023-02-16 01:23:06: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 01:23:06: Connection closed: COREXY 21

2023-02-16 01:40:03: Print of 3x_VAS_ORI_15_0.35mm_PLA_7h29m_323.979g on printer COREXY 23 finished. Send 287136 lines. Printing time: 9:19:32

2023-02-16 01:41:31: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 01:41:31: Connection closed: COREXY 23

2023-02-16 01:47:04: Print of 4xVAS_WAV_15_0.35mm_PLA_8h59m_352.102g on printer COREXY 03 finished. Send 1140429 lines. Printing time: 9:58:34

2023-02-16 01:48:27: Print of 4xVAS_WAV_15_0.35mm_PLA_8h59m_352.102g on printer COREXY 07 finished. Send 1140429 lines. Printing time: 9:58:55

2023-02-16 01:48:33: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 01:48:33: Connection closed: COREXY 03

2023-02-16 01:49:56: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 01:49:56: Connection closed: COREXY 07

2023-02-16 01:57:37: Print of 4xVAS_WAV_15_0.35mm_PLA_8h59m_352.102g on printer COREXY 04 finished. Send 1140429 lines. Printing time: 9:56:31

2023-02-16 01:59:05: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 01:59:05: Connection closed: COREXY 04

2023-02-16 02:02:25: Print of VAS_ISH_20+2X_VAS_ORI_15_0.35mm_PLA_8h32m_343.502g on printer COREXY 24 finished. Send 1084460 lines. Printing time: 10:06:22

2023-02-16 02:03:54: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 02:03:54: Connection closed: COREXY 24

2023-02-16 02:39:51: Print of 2_VAS_OND_BOT_25_PLA_8h57m_450g on printer COREXY 17 finished. Send 723327 lines. Printing time: 10:46:47

2023-02-16 02:58:08: Print of 2_VAS_OND_BOT_25_PLA_8h57m_450g on printer COREXY 19 finished. Send 723327 lines. Printing time: 10:43:45

2023-02-16 03:21:21: Print of VAS_ISH_20+2X_VAS_ORI_15_0.35mm_PLA_8h32m_343.502g on printer COREXY 27 finished. Send 1084460 lines. Printing time: 11:23:57

2023-02-16 03:23:14: error: Reading conection failed: Operation timed out. Closing connection.

2023-02-16 03:23:14: Connection closed: COREXY 27

2023-02-16 07:26:16: Print of Terre dombres COREXY_0.35mm_PLA_11h8m_431.426g on printer COREXY 11 finished. Send 778990 lines. Printing time: 15:35:19

2023-02-16 07:38:16: Print of VAS_WAV_30_0.35mm_PLA_12h52m_496.855g on printer COREXY 26 finished. Send 1608777 lines. Printing time: 15:32:35

And here is the end of the log of the print of the COREXY 27 of this night causing the connection close and duet brick:

Send:3:21:21.180: N114267 M117 S"ETE 00:00:57"

Send:3:21:21.180: N114268 G1 X397.788 Y100.449 E0.07996

Send:3:21:21.181: N114269 G1 E-0.8 F3600

Send:3:21:21.181: N114270 M107

Recv:3:21:21.204: ok

Send:3:21:21.204: N114271 G91 ; relative positioning

Send:3:21:21.330: N114272 M408 S2

Recv:3:21:21.351: ok

Send:3:21:21.351: N114273 G1 Z+10 E-2 Y+10 F250 ;move Z up a bit and retract filament even more

Send:3:21:21.351: N114274 G90 ; absolute positionning

Send:3:21:21.351: N114275 G1 X0 Y500 F9000 ; Move Head Xmin Ymax

Send:3:21:21.352: N114276 G1 Z480 F600 ; Move Z max

Recv:3:21:21.352: ok

Send:3:21:21.352: N114277 M104 S0 ; turn off extruder

Recv:3:21:21.353: ok

Send:3:21:21.353: N114278 M140 S0 ; turn off bed

Recv:3:21:21.541: ok

Recv:3:21:21.613: ok

Recv:3:21:21.614: ok

Recv:3:21:21.616: ok

Recv:3:21:21.618: {"status":"B","coords":{"axesHomed":[1,1,1],"wpl":1,"xyz":[397.788,100.449,150.000],"machine":[396.917,92.155,150.000],"extr":[124189.9]},"speeds":{"requested":34.3,"top":34.3},"currentTool":0,"output":{"message":"S\"ETE 00:00:57\""},"params":{"atxPower":-1,"fanPercent":[0,0,0,0],"speedFactor":70.0,"extrFactors":[100.0],"babystep":0.000},"sensors":{"probeValue":0,"fanRPM":[-1,-1,-1,-1]},"temps":{"bed":{"current":54.9,"active":55.0,"standby":0.0,"state":2,"heater":0},"current":[54.9,195.2],"state":[2,2],"tools":{"active":[[195.0]],"standby":[[195.0]]},"extra":[{"name":"Bed","temp":54.9},{"name":"Hotend","temp":195.2}]},"time":42722.0}

Recv:3:21:21.618: ok

Recv:3:21:21.642: ok

Send:3:21:21.642: Slow command added:M400 ; Wait for current moves to finish, clearing the buffer

Send:3:21:21.642: N114279 M400 ; Wait for current moves to finish, clearing the buffer

Recv:3:21:21.643: ok

Send:3:21:21.643: N114280 M104 T0 S0 ; Disable extruder

Send:3:21:21.643: N114281 M140 S0 ; Disable bed

Send:3:21:21.643: N114282 G1 X0 Y0 F9000

Send:3:21:21.723: @stopLog

Repetier

Sounds like the duet at least disables the network.

2023-02-16 03:21:21: Print of VAS_ISH_20+2X_VAS_ORI_15_0.35mm_PLA_8h32m_343.502g on printer COREXY 27 finished. Send 1084460 lines. Printing time: 11:23:57

2023-02-16 03:23:14: error: Reading conection failed: Operation timed out. Closing connection.

So network is not reachable and it gets closed. In this console log I see no timeout but that is probably timing dependent when exactly the connection stops working. I will try to reproduce and hope I get same issue. Normally I connect via dcs or usb also network works more or less identical to usb.

Regarding rollback that is no problem. Just modify download link to version you want and install it on top. Only incompatibilty would be if you have projects with gcodes you loose the extra functions added. But gcodes will still be there.

Repetier

I just tried it over network connection. Even had similar end gcode and it executed like this:

Send:14:09:09.837: N1873 M84 ; disable motors

Recv:14:09:09.838: ok

Send:14:09:09.838: Slow command added:M400 ; Wait for current moves to finish, clearing the buffer

Send:14:09:09.839: N1874 M400 ; Wait for current moves to finish, clearing the buffer

Recv:14:09:09.839: ok

Send:14:09:09.840: N1875 M141 S0 ; Disable chamber

Recv:14:09:09.842: ok

Send:14:09:09.842: N1876 M104 T0 S0

Recv:14:09:09.844: ok

Send:14:09:09.844: N1877 M104 T1 S0

Recv:14:09:09.846: ok

Send:14:09:09.846: N1878 G1 X0 Y100 F9000

Recv:14:09:09.847: ok

Send:14:09:09.847: N1879 M84 ; Disable motor

Recv:14:09:10.698: ok

Recv:14:09:11.386: {"status":"I","coords":{"axesHomed":[0,0,0],"wpl":1,"xyz":[0.000,100.000,9.950],"machine":[0.000,100.000,9.950],"extr":[298.3,-0.0]},"speeds":{"requested":0.0,"top":0.0},"currentTool":0,"output":{"message":"S\"Layer 42/33\""},"params":{"atxPower":-1,"fanPercent":[0],"speedFactor":100.0,"extrFactors":[100.0,100.0],"babystep":0.000},"sensors":{"probeValue":1000,"fanRPM":[-1]},"temps":{"current":[23.3,23.4],"state":[2,1],"tools":{"active":[[0.0],[0.0]],"standby":[[0.0],[0.0]]},"extra":[]},"time":405.0}

Recv:14:09:11.386: ok

Send:14:09:11.386: @stopLog

Recv:14:09:12.397: {"status":"I","coords":{"axesHomed":[0,0,0],"wpl":1,"xyz":[0.000,100.000,9.950],"machine":[0.000,100.000,9.950],"extr":[298.3,-0.0]},"speeds":{"requested":0.0,"top":0.0},"currentTool":0,"output":{"message":"S\"Layer 42/33\""},"params":{"atxPower":-1,"fanPercent":[0],"speedFactor":100.0,"extrFactors":[100.0,100.0],"babystep":0.000},"sensors":{"probeValue":1000,"fanRPM":[-1]},"temps":{"current":[23.3,23.4],"state":[2,1],"tools":{"active":[[0.0],[0.0]],"standby":[[0.0],[0.0]]},"extra":[]},"time":406.0}

Recv:14:09:12.397: ok

As you see in the end I even got ok and network did not go down. Can't really say why. Test was with my current dev release also I did not change anything tcp related. Firmware was RRF 3.5b2

It might be something I fixed or something in combination with your setting. What is about the the duet web panel when it happens? Does it also stop working? After all we only send and receive data and should not be able to crash the printer firmware even with bad commands, but something seems to interrupt network.

Are there some scripts that can reconfigure network when run?

p_vnct

Hello,

First apologies for the very late response, and thanks for your replies.
I had to roll back as this setup is my production environment and this issue disapeared directly after this roll back.

About duet web panel, when i was using the 1.4.8 release, after each print it became unaccessible. Like you said, if the duet seems to shut off the network the duet web control interface is not accessible - and we have no duet screen on our printers.

Also i do not have any special scripts directly related to network, the only thing i have is a function on printer activation to send basic controls to all the printers at the same time.

I just saw that the new 1.4.9 release is available, i'll try to test this version soon and will let you know if this issue is fixed.