› ›

Problems with Printing with Repetier

BreefubeBreefube
in Questions & Answers
If I print with an SD Card or Cura directly from Windows PC I got no errors and a perfect first layer.
When I print with Repetier on a Raspberry Pi 3 Model B Rev 1.2 I always get holes in the First layer and Blobs.
It is an Anycubic Kobra Neo Firmware 1.3.3.
The Settings i used Autoconfigure.

Comments

  • RepetierRepetier
    Sounds like you have communication issues. Try first activating ping-pong mode and activate logging so you can check communication afterwards. Also check in console where you see any communication errors. Then it might be clearer what goes wrong.
  • BreefubeBreefube
    Mesg:18:25:47.988: Connection status: Buffered:41, Manual Commands: 0, Job Commands: 5000
    Mesg:18:25:47.988: Buffer used:41 Enforced free byte:0 lines stored:1
    Mesg:18:25:53.183: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:25:53.183: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:25:53.183: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:25:53.183: Connection status: Buffered:37, Manual Commands: 0, Job Commands: 5000
    Mesg:18:25:53.183: Buffer used:37 Enforced free byte:0 lines stored:1
    Recv:18:25:54.232: echo:Unknown command: "93 G1 X173.326 Y155.257 E83.47376"
    Mesg:18:25:58.401: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:25:58.401: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:25:58.401: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:25:58.401: Connection status: Buffered:38, Manual Commands: 0, Job Commands: 5000
    Mesg:18:25:58.401: Buffer used:38 Enforced free byte:0 lines stored:1
    Mesg:18:26:03.606: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:26:03.606: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:26:03.606: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:26:03.606: Connection status: Buffered:40, Manual Commands: 0, Job Commands: 5000
    Mesg:18:26:03.606: Buffer used:40 Enforced free byte:0 lines stored:1
    Mesg:18:26:09.004: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:26:09.004: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:26:09.004: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:26:09.004: Connection status: Buffered:41, Manual Commands: 0, Job Commands: 5000
    Mesg:18:26:09.004: Buffer used:41 Enforced free byte:0 lines stored:1
    Recv:18:26:09.855: Error:checksum mismatch, Last Line: 4298
    Recv:18:26:09.855: Resend: 4299
    Mesg:18:26:14.027: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:26:14.027: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:26:14.027: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:26:14.027: Connection status: Buffered:38, Manual Commands: 0, Job Commands: 5000
    Mesg:18:26:14.027: Buffer used:38 Enforced free byte:0 lines stored:1
    Mesg:18:26:19.393: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:26:19.393: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:26:19.393: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:26:19.393: Connection status: Buffered:41, Manual Commands: 0, Job Commands: 5000
    Mesg:18:26:19.393: Buffer used:41 Enforced free byte:0 lines stored:1
    Mesg:18:26:24.437: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:26:24.437: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:26:24.437: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:26:24.437: Connection status: Buffered:41, Manual Commands: 0, Job Commands: 5000
    Mesg:18:26:24.437: Buffer used:41 Enforced free byte:0 lines stored:1
    Mesg:18:26:29.826: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:26:29.826: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:26:29.826: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:26:29.826: Connection status: Buffered:39, Manual Commands: 0, Job Commands: 5000
    Mesg:18:26:29.826: Buffer used:39 Enforced free byte:0 lines stored:1
    Mesg:18:26:34.877: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:26:34.877: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:26:34.877: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:26:34.877: Connection status: Buffered:41, Manual Commands: 0, Job Commands: 5000
    Mesg:18:26:34.877: Buffer used:41 Enforced free byte:0 lines stored:1

    This i got
  • BreefubeBreefube
    sg:18:30:11.924: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:30:11.924: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:30:11.924: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:30:11.924: Connection status: Buffered:39, Manual Commands: 0, Job Commands: 5000
    Mesg:18:30:11.924: Buffer used:39 Enforced free byte:0 lines stored:1
    Send:18:30:11.924: N4402 G1 X51.515 Y61.008 E331.54275
    Send:18:30:12.903: N4403 G1 X160.639 Y170.132 E336.38248
    Send:18:30:13.074: N4404 G1 X160.415 Y170.442 E336.39446
    Mesg:18:30:17.082: Warning: Communication timeout - resetting communication buffer.
    Mesg:18:30:17.082: This means that a expected firmware response was not seen within the expected time.
    Mesg:18:30:17.082: The typical reason is a communication error and print should continue after the communication reset.
    Mesg:18:30:17.082: Connection status: Buffered:41, Manual Commands: 0, Job Commands: 5000
    Mesg:18:30:17.082: Buffer used:41 Enforced free byte:0 lines stored:1
    Send:18:30:17.082: N4405 G1 X51.232 Y61.258 E341.23685
    Send:18:30:18.060: N4406 G1 X50.995 Y61.379 E341.24519
    Send:18:30:18.233: N4407 G1 X50.855 Y61.415 E341.24971
    Recv:18:30:18.238: Error:checksum mismatch, Last Line: 4401
    Recv:18:30:18.238: Resend: 4402
    Send:18:30:18.255: Resend: N4402 G1 X51.515 Y61.008 E331.54275
  • RepetierRepetier
    Looks like you get no busy messages on blocks from slow moves. I'm currently investigating if this is coming from new marlin versions or has an other source. Try increasing timeout to 30 seconds which works in most cases. Guess you have 3 seconds now which requires correct busy messages to not produce these timeouts.
  • BreefubeBreefube
    Okay i will test an report you.
    Thank you :)
    At the moment i have the offical 1.2.8 firmware :)
    If you need other logs or soemthing else let me know :)
Sign In or Register to comment.