Random print pausing and fails - multiple machines on Pi4 - CR6SE / Kingroon kp3s

printastique

Hi all - been looking for threads on random stop-starting and also just stopping mid print but maybe I don't know what the correct term is?

I've been using 4x cr6se and a prusa mini on one PI with no problems for a while - I recently tried to add two Kingroon KP3s (which I love!) in place of the prusa, but even with only one CR6 and one KR running I get completely random stalls (ie.e moves reduce to roughly every 3 secs, leaving large blobs/burns on prints), or the whole system just freezes (all printers stop but stay heated - I am forced to abandon all prints manually (as Repetier does not respond).

It's all very weird! I can control all 6 printers at the same time in terms of movement and heat - but it's when I start to print it all goes wrong.

For ref the Kingroon are running their own firmware which is based on marlin. I was forced to use usb hubs for the CR6 - as for some reason they all have exactly the same identifier - but the hubs do not affect the CR6 at all.

Any help appreciated!

Repetier

Check print logs, server log and syslog at times where you see problems. Might be linux disconnecting, might be just com errors because you send too much. If you see in server.log that printer gets disconnected check syslog for same time stamp why linux did it (assuming this was the case). Otherwise check a print log for errors coming from too much data send in parallel for example (try with ping pong enabled first, if that works stable disable and check for best buffer size). There are lots of threads here for more on that specific problem. Especially with multiple machines pi can become instable - you just need one machine that adds some electronic problems for example. But with new machines it can of course also be a bad configuration which I hope here is the case.

printastique

I think it's somewhere in here - hopefully I've grabbed the right chunk... but really don't know what I'm looking at... I got two cali cubes on each KR and a level square on the CR6 perfect - The jobs that failed were a cali cube on each Kingroon and the 'strut single' on the CR6 - so more data...

2022-04-06 16:32:34: Connection started: BA - CR62

2022-04-06 16:32:34: Internal reset printer BA - CR62

2022-04-06 16:32:34: Reset printer BA - CR62

2022-04-06 16:32:45: Job created: /var/lib/Repetier-Server/printer/ClydeCR62/jobs/00000001_cr6 level squares.u

2022-04-06 16:32:45: finish job creation /var/lib/Repetier-Server/printer/Clyde__CR62/jobs/00000001_cr6 level squares.u

2022-04-06 16:32:45: start printjob cr6 level squares on printer BA - CR62

2022-04-06 16:32:45: Updating info for /var/lib/Repetier-Server/printer/ClydeCR62/jobs/00000001_cr6 level squares.g printer ClydeCR62

2022-04-06 16:32:45: Time analysing /var/lib/Repetier-Server/printer/ClydeCR62/jobs/00000001_cr6 level squares.g:56446 us

2022-04-06 16:32:46: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2022-04-06 16:35:10: Closing websocket for missing ping

2022-04-06 16:35:11: Websocket opened

2022-04-06 16:35:14: killing printjob cr6 level squares on printer BA - CR62

2022-04-06 16:35:14: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2022-04-06 16:35:29: Job created: /var/lib/Repetier-Server/printer/Clyde__CR62/models/00000088_CR6 strut single supp.u

2022-04-06 16:35:29: move /var/lib/Repetier-Server/tmp/upload1.bin to /var/lib/Repetier-Server/printer/ClydeCR62/models/00000088_CR6 strut single supp.u

2022-04-06 16:35:29: finish job creation /var/lib/Repetier-Server/printer/Clyde__CR62/models/00000088_CR6 strut single supp.u

2022-04-06 16:35:29: Uploaded CR6 strut single supp size:3292825

2022-04-06 16:35:30: Updating info for /var/lib/Repetier-Server/printer/ClydeCR62/models/00000088_CR6 strut single supp.g printer ClydeCR62

2022-04-06 16:35:30: Time analysing /var/lib/Repetier-Server/printer/ClydeCR62/models/00000088_CR6 strut single supp.g:614166 us

2022-04-06 16:35:31: Job created: /var/lib/Repetier-Server/printer/Clyde__CR62/jobs/00000002_CR6 strut single supp.u

2022-04-06 16:35:32: finish job creation /var/lib/Repetier-Server/printer/ClydeCR62/jobs/00000002_CR6 strut single supp.u

2022-04-06 16:35:32: start printjob CR6 strut single supp on printer BA - CR62

2022-04-06 16:35:32: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2022-04-06 16:35:32: Updating info for /var/lib/Repetier-Server/printer/Clyde__CR62/jobs/00000002_CR6 strut single supp.g printer ClydeCR62

2022-04-06 16:35:33: Time analysing /var/lib/Repetier-Server/printer/Clyde__CR62/jobs/00000002_CR6 strut single supp.g:568539 us

2022-04-06 16:43:14: Print of cr6 level squares on printer Face - CR63 finished. Send 2328 lines. Printing time: 0:17:20

2022-04-06 16:43:14: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2022-04-06 16:49:52: Print of King cali 2 moved purge on printer Triple A - KP3s-1 finished. Send 10010 lines. Printing time: 0:28:13

2022-04-06 16:49:52: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2022-04-06 16:52:28: Print of King cali 2 moved purge on printer Murdoch KP3s 2 finished. Send 10010 lines. Printing time: 0:29:05

2022-04-06 16:52:29: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2022-04-06 16:53:38: Closing websocket for missing ping

2022-04-06 16:53:38: Websocket opened

2022-04-06 17:05:58: error: Reading serial conection failed: End of file. Closing connection.

2022-04-06 17:05:58: Port closed for Murdoch KP3s 2

2022-04-06 17:05:58: Connection closed: Murdoch KP3s 2

2022-04-06 17:06:04: error: Reading serial conection failed: End of file. Closing connection.

2022-04-06 17:06:04: Port closed for Triple A - KP3s-1

2022-04-06 17:06:04: Connection closed: Triple A - KP3s-1

2022-04-06 17:26:58: Connection started: Murdoch KP3s 2

2022-04-06 17:26:58: Internal reset printer Murdoch KP3s 2

2022-04-06 17:26:58: Reset printer Murdoch KP3s 2

2022-04-06 17:28:46: Closing websocket for missing ping

2022-04-06 17:28:46: Websocket opened

2022-04-06 17:35:00: Closing websocket for missing ping

2022-04-06 17:35:00: Websocket opened

2022-04-06 17:36:40: Job created: /var/lib/Repetier-Server/printer/KP3s_1/models/00000007_kinggroothead.u

2022-04-06 17:36:40: move /var/lib/Repetier-Server/tmp/upload2.bin to /var/lib/Repetier-Server/printer/KP3s_1/models/00000007_kinggroothead.u

2022-04-06 17:36:40: finish job creation /var/lib/Repetier-Server/printer/KP3s_1/models/00000007_kinggroothead.u

2022-04-06 17:36:40: Uploaded kinggroothead size:5822238

2022-04-06 17:36:40: Updating info for /var/lib/Repetier-Server/printer/KP3s_1/models/00000007_kinggroothead.g printer KP3s_1

2022-04-06 17:36:41: Time analysing /var/lib/Repetier-Server/printer/KP3s_1/models/00000007_kinggroothead.g:1066326 us

2022-04-06 17:36:43: Job created: /var/lib/Repetier-Server/printer/KP3s_1/jobs/00000002_kinggroothead.u

2022-04-06 17:36:43: finish job creation /var/lib/Repetier-Server/printer/KP3s_1/jobs/00000002_kinggroothead.u

2022-04-06 17:36:43: start printjob kinggroothead on printer Murdoch KP3s 2

2022-04-06 17:36:43: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2022-04-06 17:36:43: Updating info for /var/lib/Repetier-Server/printer/KP3s_1/jobs/00000002_kinggroothead.g printer KP3s_1

2022-04-06 17:36:44: Time analysing /var/lib/Repetier-Server/printer/KP3s_1/jobs/00000002_kinggroothead.g:1074946 us

2022-04-06 17:38:12: error: Reading serial conection failed: End of file. Closing connection.

2022-04-06 17:38:12: Port closed for Face - CR63

2022-04-06 17:38:12: Connection closed: Face - CR63

2022-04-06 18:08:17: Websocket opened

2022-04-06 18:09:17: killing printjob kinggroothead on printer Murdoch KP3s 2

2022-04-06 18:09:17: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2022-04-06 18:09:48: error: Reading serial conection failed: End of file. Closing connection.

2022-04-06 18:09:48: Port closed for Murdoch KP3s 2

2022-04-06 18:09:48: Connection closed: Murdoch KP3s 2

2022-04-06 18:10:16: Repetier-Informer API response: {"error":0,"data":{"receivers":1}}

2022-04-06 18:10:21: Stopping for signal 15

2022-04-06 18:10:21: Stopping MQTT subsystem ...

2022-04-06 18:10:21: Stopping lua runner ...

2022-04-06 18:10:21: Stopping global cloud ...

2022-04-06 18:10:21: Stopping open threads ...

2022-04-06 18:10:21: Shutting down web server.

2022-04-06 18:10:21: Stopped wifi watcher.

2022-04-06 18:10:21: Closing server

2022-04-06 18:10:21: Stopping work dispatcher.

2022-04-06 18:10:21: Work dispatcher thread stopped.

2022-04-06 18:10:21: Internal Work dispatcher thread stopped.

2022-04-06 18:10:21: Waiting for all threads to finish ...

2022-04-06 18:10:21: Worker threads finsihed.

2022-04-06 18:10:21: Stopping printer threads.

2022-04-06 18:10:21: Printer thread for DishpanKP3s3 stopped

2022-04-06 18:10:21: Printjob manager thread for Dishpan__KP3s3 stopped.

2022-04-06 18:10:21: Printer thread for CR63 stopped

2022-04-06 18:10:21: Printjob manager thread for CR63 stopped.

2022-04-06 18:10:21: Port closed for BA - CR62

2022-04-06 18:10:21: Connection closed: BA - CR62

2022-04-06 18:10:21: Printer thread for ClydeCR62 stopped

2022-04-06 18:10:21: Printjob manager thread for Clyde__CR62 stopped.

2022-04-06 18:10:21: Printer thread for CR6SE_1 stopped

2022-04-06 18:10:21: Printjob manager thread for CR6SE_1 stopped.

2022-04-06 18:10:21: Printer thread for KP3s_1 stopped

2022-04-06 18:10:21: Printjob manager thread for KP3s_1 stopped.

2022-04-06 18:10:21: Closing user database.

2022-04-06 18:10:21: Server is now down.

Repetier

Ok, thats the bad case:-(

2022-04-06 17:38:12: error: Reading serial conection failed: End of file. Closing connection.

2022-04-06 17:38:12: Port closed for Face - CR63

This means linux closed the serial connection to printer. Check /var/log/syslog on same day at same timestamp. Every day linux starts a new syslog to today that error is in /var/log/syslog.0

In syslog you see more information why linux did close the usb port.

printastique

Yes it's weird - I don't know about about code though - The CR6 have been 100% for ages until I introduced the Kingroon printers - I tried to download the syslog from the printer but they only seem to pick up one day.... do they keep the rest? I can reproduce the failure and download them all if that helps find the problem...

Repetier

syslog changes every day. Linux renames them then so from syslog it gets syslog.0 and older even get compressed to syslog.1.gz all in /var/log if oyu login to linux over ssh.