Printers disconnect after each print after update to 1.4.8
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:
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
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
Comments
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.
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 :
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:
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.
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.