Kobra Max - immer wieder nervige Abbrüche...
Hallo,
ich habe bei meinem Anycubic Kobra Max immer wieder nervige Druckabbrüche mitten im Druck.
Das ganze passiert aber leider immer sporadisch.
Ich habe den Log vom letzten Abbruch gespeichert und ein Foto von meinen Einstellungen gemacht.
Vermutlich sitzt das Problem vorm PC, aber kann mir hier mal einen Tipp geben wie man das ganze bei den Kobra Max richtig einstellt?
Ich habe nach einem Mainboard Defekt ein neues Trigorilla Board bekommen mit der Firmware 3.0.4 (zur Info):
https://imgur.com/a/r0KlGwd
ich habe bei meinem Anycubic Kobra Max immer wieder nervige Druckabbrüche mitten im Druck.
Das ganze passiert aber leider immer sporadisch.
Ich habe den Log vom letzten Abbruch gespeichert und ein Foto von meinen Einstellungen gemacht.
Vermutlich sitzt das Problem vorm PC, aber kann mir hier mal einen Tipp geben wie man das ganze bei den Kobra Max richtig einstellt?
Ich habe nach einem Mainboard Defekt ein neues Trigorilla Board bekommen mit der Firmware 3.0.4 (zur Info):
https://imgur.com/a/r0KlGwd
Mesg:16:57:06.204: Warning: Communication timeout - resetting communication buffer.
Mesg:16:57:06.204: This means that a expected firmware response was not seen within the expected time.
Mesg:16:57:06.204: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:57:06.204: Connection status: Buffered:40, Manual Commands: 0, Job Commands: 5000
Mesg:16:57:06.204: Buffer used:40 Enforced free byte:0 lines stored:1
Mesg:16:57:13.216: Warning: Communication timeout - resetting communication buffer.
Mesg:16:57:13.216: This means that a expected firmware response was not seen within the expected time.
Mesg:16:57:13.216: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:57:13.216: Connection status: Buffered:25, Manual Commands: 1, Job Commands: 5000
Mesg:16:57:13.216: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:16:57:13.557: Received extra ok - ignored
Recv:16:57:13.558: echo:Unknown command: "2675"
Mesg:16:57:20.979: Warning: Communication timeout - resetting communication buffer.
Mesg:16:57:20.979: This means that a expected firmware response was not seen within the expected time.
Mesg:16:57:20.979: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:57:20.979: Connection status: Buffered:39, Manual Commands: 1, Job Commands: 5000
Mesg:16:57:20.979: Buffer used:39 Enforced free byte:0 lines stored:1
Mesg:16:57:27.982: Warning: Communication timeout - resetting communication buffer.
Mesg:16:57:27.982: This means that a expected firmware response was not seen within the expected time.
Mesg:16:57:27.982: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:57:27.982: Connection status: Buffered:25, Manual Commands: 1, Job Commands: 5000
Mesg:16:57:27.982: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:16:57:28.760: Received extra ok - ignored (3)
Mesg:16:57:35.770: Warning: Communication timeout - resetting communication buffer.
Mesg:16:57:35.770: This means that a expected firmware response was not seen within the expected time.
Mesg:16:57:35.770: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:57:35.770: Connection status: Buffered:40, Manual Commands: 0, Job Commands: 5000
Mesg:16:57:35.770: Buffer used:40 Enforced free byte:0 lines stored:1
Mesg:16:57:42.775: Warning: Communication timeout - resetting communication buffer.
Mesg:16:57:42.775: This means that a expected firmware response was not seen within the expected time.
Mesg:16:57:42.775: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:57:42.775: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:57:42.775: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:57:43.121: Received extra ok - ignored (2)
Mesg:16:57:50.545: Warning: Communication timeout - resetting communication buffer.
Mesg:16:57:50.545: This means that a expected firmware response was not seen within the expected time.
Mesg:16:57:50.545: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:57:50.545: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:57:50.545: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:57:57.550: Warning: Communication timeout - resetting communication buffer.
Mesg:16:57:57.550: This means that a expected firmware response was not seen within the expected time.
Mesg:16:57:57.550: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:57:57.550: Connection status: Buffered:25, Manual Commands: 0, Job Commands: 5000
Mesg:16:57:57.550: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:16:57:58.325: Received extra ok - ignored
Mesg:16:58:05.340: Warning: Communication timeout - resetting communication buffer.
Mesg:16:58:05.340: This means that a expected firmware response was not seen within the expected time.
Mesg:16:58:05.340: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:58:05.340: Connection status: Buffered:39, Manual Commands: 0, Job Commands: 5000
Mesg:16:58:05.340: Buffer used:39 Enforced free byte:0 lines stored:1
Mesg:16:58:12.347: Warning: Communication timeout - resetting communication buffer.
Mesg:16:58:12.347: This means that a expected firmware response was not seen within the expected time.
Mesg:16:58:12.347: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:58:12.347: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:58:12.347: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:58:13.107: Received extra ok - ignored
Mesg:16:58:20.112: Warning: Communication timeout - resetting communication buffer.
Mesg:16:58:20.112: This means that a expected firmware response was not seen within the expected time.
Mesg:16:58:20.112: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:58:20.112: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:58:20.112: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:58:27.123: Warning: Communication timeout - resetting communication buffer.
Mesg:16:58:27.123: This means that a expected firmware response was not seen within the expected time.
Mesg:16:58:27.123: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:58:27.123: Connection status: Buffered:25, Manual Commands: 0, Job Commands: 5000
Mesg:16:58:27.123: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:16:58:27.471: Received extra ok - ignored
Recv:16:58:27.474: Error:checksum mismatch, Last Line: 8987
Recv:16:58:27.474: Resend: 8988
Mesg:16:58:34.901: Warning: Communication timeout - resetting communication buffer.
Mesg:16:58:34.901: This means that a expected firmware response was not seen within the expected time.
Mesg:16:58:34.901: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:58:34.901: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:58:34.901: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:58:41.921: Warning: Communication timeout - resetting communication buffer.
Mesg:16:58:41.921: This means that a expected firmware response was not seen within the expected time.
Mesg:16:58:41.921: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:58:41.921: Connection status: Buffered:25, Manual Commands: 1, Job Commands: 5000
Mesg:16:58:41.921: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:16:58:42.252: Received extra ok - ignored
Recv:16:58:42.256: echo:Unknown command: "68.423 Y263.546 E94.2993"
Mesg:16:58:49.686: Warning: Communication timeout - resetting communication buffer.
Mesg:16:58:49.686: This means that a expected firmware response was not seen within the expected time.
Mesg:16:58:49.686: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:58:49.686: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:58:49.686: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:58:56.693: Warning: Communication timeout - resetting communication buffer.
Mesg:16:58:56.693: This means that a expected firmware response was not seen within the expected time.
Mesg:16:58:56.693: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:58:56.693: Connection status: Buffered:17, Manual Commands: 0, Job Commands: 5000
Mesg:16:58:56.693: Buffer used:17 Enforced free byte:0 lines stored:1
Mesg:16:58:57.035: Received extra ok - ignored
Mesg:16:59:04.463: Warning: Communication timeout - resetting communication buffer.
Mesg:16:59:04.463: This means that a expected firmware response was not seen within the expected time.
Mesg:16:59:04.463: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:59:04.463: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:59:04.463: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:59:11.469: Warning: Communication timeout - resetting communication buffer.
Mesg:16:59:11.469: This means that a expected firmware response was not seen within the expected time.
Mesg:16:59:11.469: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:59:11.469: Connection status: Buffered:25, Manual Commands: 1, Job Commands: 5000
Mesg:16:59:11.469: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:16:59:12.237: Received extra ok - ignored (2)
Mesg:16:59:19.240: Warning: Communication timeout - resetting communication buffer.
Mesg:16:59:19.240: This means that a expected firmware response was not seen within the expected time.
Mesg:16:59:19.240: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:59:19.240: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:59:19.240: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:59:26.252: Warning: Communication timeout - resetting communication buffer.
Mesg:16:59:26.252: This means that a expected firmware response was not seen within the expected time.
Mesg:16:59:26.252: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:59:26.252: Connection status: Buffered:17, Manual Commands: 0, Job Commands: 5000
Mesg:16:59:26.252: Buffer used:17 Enforced free byte:0 lines stored:1
Recv:16:59:26.604: Error:Line Number is not Last Line Number+1, Last Line: 8995
Recv:16:59:26.607: Resend: 8996
Mesg:16:59:34.025: Warning: Communication timeout - resetting communication buffer.
Mesg:16:59:34.025: This means that a expected firmware response was not seen within the expected time.
Mesg:16:59:34.025: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:59:34.025: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:59:34.025: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:59:41.037: Warning: Communication timeout - resetting communication buffer.
Mesg:16:59:41.037: This means that a expected firmware response was not seen within the expected time.
Mesg:16:59:41.037: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:59:41.037: Connection status: Buffered:17, Manual Commands: 1, Job Commands: 5000
Mesg:16:59:41.037: Buffer used:17 Enforced free byte:0 lines stored:1
Mesg:16:59:41.383: Received extra ok - ignored
Recv:16:59:41.385: echo:Unknown command: "E109.54575"
Mesg:16:59:48.818: Warning: Communication timeout - resetting communication buffer.
Mesg:16:59:48.818: This means that a expected firmware response was not seen within the expected time.
Mesg:16:59:48.818: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:59:48.818: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:16:59:48.818: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:16:59:55.819: Warning: Communication timeout - resetting communication buffer.
Mesg:16:59:55.819: This means that a expected firmware response was not seen within the expected time.
Mesg:16:59:55.819: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:59:55.819: Connection status: Buffered:18, Manual Commands: 0, Job Commands: 5000
Mesg:16:59:55.819: Buffer used:18 Enforced free byte:0 lines stored:1
Mesg:16:59:56.165: Received extra ok - ignored
Mesg:17:00:03.591: Warning: Communication timeout - resetting communication buffer.
Mesg:17:00:03.591: This means that a expected firmware response was not seen within the expected time.
Mesg:17:00:03.591: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:00:03.591: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:00:03.591: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:00:10.597: Warning: Communication timeout - resetting communication buffer.
Mesg:17:00:10.597: This means that a expected firmware response was not seen within the expected time.
Mesg:17:00:10.597: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:00:10.597: Connection status: Buffered:17, Manual Commands: 1, Job Commands: 5000
Mesg:17:00:10.597: Buffer used:17 Enforced free byte:0 lines stored:1
Mesg:17:00:11.368: Received extra ok - ignored (2)
Mesg:17:00:18.382: Warning: Communication timeout - resetting communication buffer.
Mesg:17:00:18.382: This means that a expected firmware response was not seen within the expected time.
Mesg:17:00:18.382: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:00:18.382: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:00:18.382: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:00:25.396: Warning: Communication timeout - resetting communication buffer.
Mesg:17:00:25.396: This means that a expected firmware response was not seen within the expected time.
Mesg:17:00:25.396: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:00:25.396: Connection status: Buffered:18, Manual Commands: 0, Job Commands: 5000
Mesg:17:00:25.396: Buffer used:18 Enforced free byte:0 lines stored:1
Recv:17:00:25.735: Error:Line Number is not Last Line Number+1, Last Line: 9003
Recv:17:00:25.738: Resend: 9004
Mesg:17:00:33.152: Warning: Communication timeout - resetting communication buffer.
Mesg:17:00:33.152: This means that a expected firmware response was not seen within the expected time.
Mesg:17:00:33.152: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:00:33.152: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:00:33.152: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:00:40.153: Warning: Communication timeout - resetting communication buffer.
Mesg:17:00:40.153: This means that a expected firmware response was not seen within the expected time.
Mesg:17:00:40.153: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:00:40.153: Connection status: Buffered:18, Manual Commands: 1, Job Commands: 5000
Mesg:17:00:40.153: Buffer used:18 Enforced free byte:0 lines stored:1
Mesg:17:00:40.513: Received extra ok - ignored
Recv:17:00:40.515: echo:Unknown command: "6 E124.79221"
Mesg:17:00:47.942: Warning: Communication timeout - resetting communication buffer.
Mesg:17:00:47.942: This means that a expected firmware response was not seen within the expected time.
Mesg:17:00:47.942: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:00:47.942: Connection status: Buffered:41, Manual Commands: 0, Job Commands: 5000
Mesg:17:00:47.942: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:00:54.947: Warning: Communication timeout - resetting communication buffer.
Mesg:17:00:54.947: This means that a expected firmware response was not seen within the expected time.
Mesg:17:00:54.947: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:00:54.947: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:00:54.947: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:00:55.295: Received extra ok - ignored
Mesg:17:01:02.729: Warning: Communication timeout - resetting communication buffer.
Mesg:17:01:02.729: This means that a expected firmware response was not seen within the expected time.
Mesg:17:01:02.729: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:01:02.729: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:01:02.729: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:01:09.737: Warning: Communication timeout - resetting communication buffer.
Mesg:17:01:09.737: This means that a expected firmware response was not seen within the expected time.
Mesg:17:01:09.737: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:01:09.737: Connection status: Buffered:18, Manual Commands: 1, Job Commands: 5000
Mesg:17:01:09.737: Buffer used:18 Enforced free byte:0 lines stored:1
Mesg:17:01:10.077: Received extra ok - ignored
Mesg:17:01:17.508: Warning: Communication timeout - resetting communication buffer.
Mesg:17:01:17.508: This means that a expected firmware response was not seen within the expected time.
Mesg:17:01:17.508: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:01:17.508: Connection status: Buffered:41, Manual Commands: 0, Job Commands: 5000
Mesg:17:01:17.508: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:01:24.515: Warning: Communication timeout - resetting communication buffer.
Mesg:17:01:24.515: This means that a expected firmware response was not seen within the expected time.
Mesg:17:01:24.515: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:01:24.515: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:01:24.515: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:01:24.860: Received extra ok - ignored
Recv:17:01:25.286: Error:Line Number is not Last Line Number+1, Last Line: 9011
Recv:17:01:25.288: Resend: 9012
Mesg:17:01:32.334: Warning: Communication timeout - resetting communication buffer.
Mesg:17:01:32.334: This means that a expected firmware response was not seen within the expected time.
Mesg:17:01:32.334: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:01:32.334: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:01:32.334: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:01:39.338: Warning: Communication timeout - resetting communication buffer.
Mesg:17:01:39.338: This means that a expected firmware response was not seen within the expected time.
Mesg:17:01:39.338: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:01:39.338: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:01:39.338: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:01:39.642: Received extra ok - ignored
Mesg:17:01:46.646: Warning: Communication timeout - resetting communication buffer.
Mesg:17:01:46.646: This means that a expected firmware response was not seen within the expected time.
Mesg:17:01:46.646: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:01:46.646: Connection status: Buffered:25, Manual Commands: 1, Job Commands: 5000
Mesg:17:01:46.646: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:17:01:53.651: Warning: Communication timeout - resetting communication buffer.
Mesg:17:01:53.651: This means that a expected firmware response was not seen within the expected time.
Mesg:17:01:53.651: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:01:53.651: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:01:53.651: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:02:00.662: Warning: Communication timeout - resetting communication buffer.
Mesg:17:02:00.662: This means that a expected firmware response was not seen within the expected time.
Mesg:17:02:00.662: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:02:00.662: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:02:00.662: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:02:07.676: Warning: Communication timeout - resetting communication buffer.
Mesg:17:02:07.676: This means that a expected firmware response was not seen within the expected time.
Mesg:17:02:07.676: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:02:07.676: Connection status: Buffered:18, Manual Commands: 0, Job Commands: 5000
Mesg:17:02:07.676: Buffer used:18 Enforced free byte:0 lines stored:1
Mesg:17:02:14.681: Warning: Communication timeout - resetting communication buffer.
Mesg:17:02:14.681: This means that a expected firmware response was not seen within the expected time.
Mesg:17:02:14.681: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:02:14.681: Connection status: Buffered:41, Manual Commands: 1, Job Commands: 5000
Mesg:17:02:14.681: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:02:21.695: Warning: Communication timeout - resetting communication buffer.
Mesg:17:02:21.695: This means that a expected firmware response was not seen within the expected time.
Mesg:17:02:21.695: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:02:21.695: Connection status: Buffered:17, Manual Commands: 1, Job Commands: 5000
Mesg:17:02:21.695: Buffer used:17 Enforced free byte:0 lines stored:1
Mesg:17:02:28.700: Warning: Communication timeout - resetting communication buffer.
Mesg:17:02:28.700: This means that a expected firmware response was not seen within the expected time.
Mesg:17:02:28.700: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:02:28.700: Connection status: Buffered:25, Manual Commands: 1, Job Commands: 5000
Mesg:17:02:28.700: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:17:02:35.707: Warning: Communication timeout - resetting communication buffer.
Mesg:17:02:35.707: This means that a expected firmware response was not seen within the expected time.
Mesg:17:02:35.707: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:02:35.707: Connection status: Buffered:18, Manual Commands: 0, Job Commands: 5000
Mesg:17:02:35.707: Buffer used:18 Enforced free byte:0 lines stored:1
Mesg:17:02:42.728: Warning: Communication timeout - resetting communication buffer.
Mesg:17:02:42.728: This means that a expected firmware response was not seen within the expected time.
Mesg:17:02:42.728: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:02:42.728: Connection status: Buffered:41, Manual Commands: 2, Job Commands: 7
Mesg:17:02:42.728: Buffer used:41 Enforced free byte:0 lines stored:1
Mesg:17:02:49.741: Warning: Communication timeout - resetting communication buffer.
Mesg:17:02:49.741: This means that a expected firmware response was not seen within the expected time.
Mesg:17:02:49.741: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:02:49.741: Connection status: Buffered:13, Manual Commands: 2, Job Commands: 7
Mesg:17:02:49.741: Buffer used:13 Enforced free byte:0 lines stored:1
Mesg:17:02:56.751: Warning: Communication timeout - resetting communication buffer.
Mesg:17:02:56.751: This means that a expected firmware response was not seen within the expected time.
Mesg:17:02:56.751: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:02:56.751: Connection status: Buffered:24, Manual Commands: 0, Job Commands: 7
Mesg:17:02:56.751: Buffer used:24 Enforced free byte:0 lines stored:1
Mesg:17:03:16.757: Warning: Communication timeout - resetting communication buffer.
Mesg:17:03:16.757: This means that a expected firmware response was not seen within the expected time.
Mesg:17:03:16.757: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:03:16.757: Connection status: Buffered:14, Manual Commands: 2, Job Commands: 5
Mesg:17:03:16.757: Buffer used:14 Enforced free byte:0 lines stored:1
Mesg:17:03:23.769: Warning: Communication timeout - resetting communication buffer.
Mesg:17:03:23.769: This means that a expected firmware response was not seen within the expected time.
Mesg:17:03:23.769: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:03:23.769: Connection status: Buffered:19, Manual Commands: 1, Job Commands: 5
Mesg:17:03:23.769: Buffer used:19 Enforced free byte:0 lines stored:1
Mesg:17:03:29.712: Full stop button pressed
Mesg:17:03:29.712: Printer reset requested - emergency:true
Mesg:17:03:29.840: Dtr: false Rts: false
Mesg:17:03:29.871: Dtr: true Rts: true
Mesg:17:03:36.722: Warning: Communication timeout - resetting communication buffer.
Mesg:17:03:36.722: This means that a expected firmware response was not seen within the expected time.
Mesg:17:03:36.722: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:03:36.722: Connection status: Buffered:25, Manual Commands: 3, Job Commands: 0
Mesg:17:03:36.722: Buffer used:25 Enforced free byte:0 lines stored:2
Mesg:17:03:43.732: Warning: Communication timeout - resetting communication buffer.
Mesg:17:03:43.732: This means that a expected firmware response was not seen within the expected time.
Mesg:17:03:43.732: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:03:43.732: Connection status: Buffered:25, Manual Commands: 3, Job Commands: 0
Mesg:17:03:43.732: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:17:03:50.738: Warning: Communication timeout - resetting communication buffer.
Mesg:17:03:50.738: This means that a expected firmware response was not seen within the expected time.
Mesg:17:03:50.738: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:03:50.738: Connection status: Buffered:14, Manual Commands: 2, Job Commands: 0
Mesg:17:03:50.738: Buffer used:14 Enforced free byte:0 lines stored:1
Mesg:17:03:57.744: Warning: Communication timeout - resetting communication buffer.
Mesg:17:03:57.744: This means that a expected firmware response was not seen within the expected time.
Mesg:17:03:57.744: The typical reason is a communication error and print should continue after the communication reset.
Mesg:17:03:57.744: Connection status: Buffered:25, Manual Commands: 0, Job Commands: 0
Mesg:17:03:57.744: Buffer used:25 Enforced free byte:0 lines stored:1
Mesg:17:05:16.415: Connection closed by os.
Mesg:17:05:19.836: Connection started
Mesg:17:05:19.836: Printer reset requested - emergency:false
Mesg:17:05:19.837: Dtr: false Rts: false
Mesg:17:05:19.872: Dtr: true Rts: true
Recv:17:05:22.877: Send init commands because we had no signal from a reset, assuming reset not available.
Mesg:17:05:33.592: Connection started
Mesg:17:05:33.592: Printer reset requested - emergency:false
Mesg:17:05:33.592: Dtr: false Rts: false
Mesg:17:05:33.620: Dtr: true Rts: true
Recv:17:05:36.630: Send init commands because we had no signal from a reset, assuming reset not available.
Comments
Interessant ist z.b. folgender Ausschnitt:
Hier kommen offenbar mehr ok an als möglich bei Ping-Pong. Allerdings wird mit jedem Timeout auch mehr gesendet und kann den Druckerpuffer überfüllen wenn der Drucker blockiert. Ich sehe alle 7 Sekunden kommt ein Timeout - ist das dein Timeout?
Unterstützt die Firmware busy Protokol? Aktiviere ack und sende
G4 S20
und wenn du Zeilen wie busy: ...
siehst ist das wohl der Fall, sonst nicht und du solltest timeout erhöhen.
Wenn du logging aktiviert hast must du dir ansehen wo das Timeout entsteht, also welcher Befehl dazu führt oder ob der Drucker in einen Fehlerstatus gegangen ist und daher nicht mehr entgegen nimmt.
ich habe das Timeout auf 6 Sekunden definiert gehabt.
Testweise habe ich es jetzt mal auf 15 Sekunden angehoben (was ist hier sinnvoll) und habe mit aktivierten Log den fehlgeschlagenen 16 Stunden Druck noch einmal gestartet.
Der G-Code dürfte aber nicht fehlerhaft sein, von der SD-Karte hat alles geklappt.
Das Busy Protokoll wird denke ich nicht unterstützt. Ich habe zumindest keine Busy Command nach aktivieren im Log entdeckt.
Nachdem ich den Befehl eingegeben habe ist das erschienen, ich weiß aber nicht ob das zusammenhängt.
Danke für die Hilfe!
Ansonsten G4 zeight kein busy, scheint also alter Marlin Version zu sein oder das Feature wurde deaktiviert. In dem Fall muss das timeout länger als die langsamste Bewegung sein, sonst kann es dort zu timeouts kommen.
Aber Drucken mit logging ist schon mal gut, dann siehst du wenn es wieder passiert wie es entsteht bzw. was es auslöst.
Ich habe den Druck gestern Abend nach 4 Stunden abgebrochen da ich nicht wollte dass der Drucker sich über Nacht eventuell aufhängt...
Am Wochenende mache ich noch einmal einen neuen Test.
Kann man sich das irgendwie ausrechnen welche Timeouts man einstellen sollte?
Die Marlin Version ist vom Februar 2023.
Das Busy Protocol kann man vermutlich nur beim neukompilieren der Firmware aktiveren oder?
Vielen Dank!
Hier die Ausgabe wenn ich die Maschine starte gefolgt von einem M501 Befehl:
Der Kobra Max hat ja eine Druckbett-Diagonale von 402x402x452 (LxBxH).
Die niedrigste Geschwindigkeit die ich habe ist beim First Layer mit 20mm/s, das würde dann bedeuten dass ich so rechnen muss: 402/20 = 20,1
Aber was hat das mit der Z-Achse zu tun bzw. wie kann ich die in die Rechnung mit einbeziehen?
Danke
Wenn z maximalgeschwindigkeit 10mm/s brauchst du von oben nach untern 452/10 = 45.2s. Ist aber eher selten und vielleicht kann er ja auch schneller.
Sollte ich jetzt 45 Sekunden beim Timeout einstellen?
Hab die Zeit gestoppt beim runterfahren der Z Achse und es waren genau 45,12 Sekunden
Dann nehme ich mal 30 Sekunden
Vielen Dank!
Nochmals Danke!