› ›

Communication timeout - reset buffer block

CamilaMonizCamilaMoniz
in Bug Reports

Dear support,

I’m experiencing a persistent “communication timeout – reset buffer block” error while printing.

Here are the connection settings I’m using:

  • Port: COM (manually selected, not Auto)

  • BaudRate: 250000

  • Transfer Protocol: Autodetect

  • Receive Cache Size: 127

  • Communication Timeout: 40s

  • Firmware: Marlin

I’ve run multiple tests and the disconnection happens frequently. I’ve already replaced the USB cable, which improved things temporarily, but the issue returned—suggesting the root cause might be elsewhere.

This printer model has worked before with exactly these same parameters. I’ve also tried switching USB ports on the computer, but the timeout still occurs.

When the communication error happens, the Connect button remains blue, but the interface seems to freeze.

Appreciate any guidance you can provide on resolving this.

Comments

  • RepetierRepetier
    Can you provide a communication log part where it happens including a few 100 lines before the error. Also is ping pong mode enabled or not. When enabled any missing linebreak in communication will cause this, otherwise this error often corrects it self when we see the line number in ok response (if enabled in marlin which helps detecing such errors).
  • CamilaMonizCamilaMoniz
    Repetier said:
    Can you provide a communication log part where it happens including a few 100 lines before the error. Also is ping pong mode enabled or not. When enabled any missing linebreak in communication will cause this, otherwise this error often corrects it self when we see the line number in ok response (if enabled in marlin which helps detecing such errors).
    In fact, I only have a few lines because it’s a screenshot I got from a colleague who has the machine.,

    N161 G1 X60.111 Y30.231 E84.8641*95
    N162 M117 ETE 57m 00s*73
    N163 G1 X60.224 Y30.162 F6000*74
    N164 G1 E4.77035 F180.0000*35
    N165 G92 E0*69
    N166 G1 Z1.26000*30
    N167 G1 X61.258 Y31.056 F6000*64
    N168 G1 Z0.2 F6000*17
    N169 G1 E80.09446 F180.0000*72
    N170 M117 ETE 54m 02s*73
    N171 G1 F60*79
    N172 G1 X61.056 Y31.258 E80.11494*94
    N173 G1 X61.056 Y31.765 E80.15121*91
    Communication timeout - reset send buffer block
    N174 M117 ETE 51m 01s*78
    Communication timeout - reset send buffer block
    N175 G1 X61.764 Y31.056 E80.22298*89
    N176 M117 ETE 50m 01s*78
    N177 G1 X62.271 Y31.056 E80.25925*88
    N178 G1 X62.271 Y31.056 E80.38231*94
    N179 G1 X62.775 Y31.056 E80.59293*85
    N180 G1 X63.283 Y31.056 E80.62920*80
    N181 G1 X61.056 Y33.284 E80.8548*94

    I’m not sure if the “ok” response with the line number is enabled, since I’ve never seen it in the log.
    In any case, the ping-pong mode is disabled.
    Best,
    Camila
  • RepetierRepetier
    Unfortunately that is not enough. It is quite clear that it must be some error during communication. But without ok responses you can not see it it continued afterwartds meaning it was ca ommunication or if it was just a slow command triggering it. Also of interest as said if ok responses have line numbers included. This and busy/wait messages can help hosts to detect such errors quite quickly, but must be enabled in printer firmware.
Sign In or Register to comment.