›

Communication timeout - resetting communication buffer / Artillery Sidewinder / Cura

maeffjusmaeffjus
in Repetier-Server
Hi Guys, I'm actually pretty annoyed - my printers both stop every once in a while.
To me is seems, at least what I can see be the communication, that the Extruder-length has a lot of digits!
But I'm not sure if this is the source of my problems, also I have changed the firmware from Marling 2.0.5.3 to 2.0.5.1 and 2.0.3.
Nothing helped - almost 50% of my prints, of sometimes more, stop in the middle of the print and can not be resumed.
Please help me!

Best Regards, 
Maeffjus

Here is the last code:

Send:10:16:44.034: N20557 G1 X90.802 Y80.571 E2935.43546
Send:10:16:44.084: N20558 G1 X90.802 Y75.175 E2935.70747
Send:10:16:44.452: N20559 G1 X184.549 Y75.175 E2940.43325
Recv:10:16:44.587: echo:Unknown command: ".43325"
Send:10:16:44.587: N20560 G1 X204.374 Y75.174 E2941.43262
Send:10:16:44.587: N20561 G1 X208.323 Y79.124 E2941.71418
Recv:10:16:44.595: echo:Unknown command: ".43262"
Send:10:16:44.595: N20562 G1 X208.323 Y196.15 E2947.61345
Recv:10:16:44.599: echo:Unknown command: ".61345"
Send:10:16:44.601: N20563 G1 X208.324 Y220.876 E2948.85989
Mesg:10:16:48.603: Warning: Communication timeout - resetting communication buffer.
Mesg:10:16:48.603: Connection status: Buffered:86, Manual Commands: 0, Job Commands: 5000
Mesg:10:16:48.603: Buffer used:86 Enforced free byte:43 lines stored:2
Send:10:16:48.603: N20564 G1 X204.374 Y224.825 E2949.14145
Send:10:16:48.604: N20565 G1 X110.451 Y224.825 E2953.8761
Mesg:10:16:52.604: Warning: Communication timeout - resetting communication buffer.
Mesg:10:16:52.604: Connection status: Buffered:86, Manual Commands: 1, Job Commands: 5000
Mesg:10:16:52.604: Buffer used:86 Enforced free byte:25 lines stored:2
Send:10:16:52.605: M117 ETA 13:23:33 day 30
Send:10:16:52.605: N20566 G1 X90.802 Y224.826 E2954.8666
Send:10:16:52.605: N20567 G1 F2700 E2953.0666
Mesg:10:16:56.606: Warning: Communication timeout - resetting communication buffer.
Mesg:10:16:56.606: Connection status: Buffered:96, Manual Commands: 0, Job Commands: 5000
Mesg:10:16:56.606: Buffer used:96 Enforced free byte:24 lines stored:3
Mesg:10:16:56.606: Warning: Too many timeouts without response - disabling timeout message!
Send:10:16:56.607: N20568 G1 F300 Z4.45
Send:10:16:56.607: N20569 G0 F15000 X101.203 Y76.224 Z4.45
Send:10:16:56.608: N20570 G0 X101.203 Y76.224 Z4.7
Send:10:17:00.612: N20571 G1 F300 Z4.5
Send:10:17:00.613: N20572 G1 F2400 E2954.8666
Send:10:17:00.613: N20573 G1 F3600 X98.407 Y79.021 E2955.06596
Send:10:17:04.614: M117 ETA 13:23:36 day 30
Send:10:17:04.614: N20574 G1 X97.877 Y79.02 E2955.09268
Send:10:17:08.617: N20575 G1 X95.082 Y76.225 E2955.29194
Send:10:17:08.618: N20576 G1 X104.511 Y76.225 E2955.76725
Send:10:17:12.625: M117 ETA 13:23:44 day 30
Send:10:17:12.625: N20577 G1 X107.305 Y79.019 E2955.96644
Send:10:17:16.627: N20578 G1 X107.836 Y79.02 E2955.99321
Send:10:17:16.627: N20579 G1 X110.632 Y76.224 E2956.19253
Send:10:17:20.629: N20580 G1 X113.939 Y76.225 E2956.35924
Send:10:17:20.629: N20581 G1 X116.734 Y79.019 E2956.55846
Mesg:10:17:22.626: Connection closed by os during print ... trying reconnect for 10 seconds to continue ...
Mesg:10:17:24.237: Dtr: true Rts: true
Mesg:10:17:24.239: Connection continued
Send:10:17:24.249: M117 ETA 13:23:49 day 30
Send:10:17:24.249: N20582 G1 X117.265 Y79.02 E2956.58523
Mesg:10:17:28.258: Warning: Communication timeout - resetting communication buffer.
Mesg:10:17:28.258: Connection status: Buffered:66, Manual Commands: 0, Job Commands: 5000
Mesg:10:17:28.258: Buffer used:66 Enforced free byte:43 lines stored:2
Send:10:17:28.258: N20583 G1 X120.061 Y76.224 E2956.78456
Send:10:17:28.258: N20584 G1 X123.368 Y76.225 E2956.95126
Mesg:10:17:32.262: Warning: Communication timeout - resetting communication buffer.
Mesg:10:17:32.262: Connection status: Buffered:85, Manual Commands: 1, Job Commands: 5000
Mesg:10:17:32.262: Buffer used:85 Enforced free byte:25 lines stored:2
Send:10:17:32.262: M117 ETA 13:23:59 day 30
Send:10:17:32.262: N20585 G1 X126.162 Y79.019 E2957.15045
Mesg:10:17:36.267: Warning: Communication timeout - resetting communication buffer.
Mesg:10:17:36.267: Connection status: Buffered:67, Manual Commands: 0, Job Commands: 5000
Mesg:10:17:36.267: Buffer used:67 Enforced free byte:41 lines stored:2
Mesg:10:17:36.267: Warning: Too many timeouts without response - disabling timeout message!
Send:10:17:36.267: N20586 G1 X126.693 Y79.02 E2957.17721
Send:10:17:36.267: N20587 G1 X129.489 Y76.224 E2957.37654
Send:10:17:40.269: N20588 M106 P0 S127
Send:10:17:40.269: N20589 G1 X132.796 Y76.225 E2957.54325
Send:10:17:41.980: M117 ETA 13:24:08 day 30
Mesg:10:17:43.244: Dtr: false Rts: false
Mesg:10:17:43.254: Dtr: true Rts: true
Send:10:17:43.263: N20590 M112
Recv:10:17:44.203: start
Recv:10:17:44.203: echo:Marlin 2.0.3
Recv:10:17:44.203: echo: Last Updated: 2020-01-31 | Author: (RobStar, rob3dprint@gmail.com)
Recv:10:17:44.203: echo:Compiled: Feb 8 2020
Recv:10:17:44.204: echo: Free Memory: 4505 PlannerBufferBytes: 1632
Recv:10:17:44.204: echo:EEPROM version mismatch (EEPROM=V76 Marlin=V75)
Recv:10:17:44.204: echo:Hardcoded Default Settings Loaded
Send:10:17:44.204: N1 M110
Send:10:17:44.205: N3 M115
Send:10:17:44.205: N4 M220 S100
Send:10:17:44.205: N5 M221 S100
Send:10:17:44.205: N6 G92 E0
Send:10:17:44.205: N7 G90
Send:10:17:44.205: N8 M82
Send:10:17:44.545: N9 G21
Send:10:17:44.545: @getip
Recv:10:17:44.611: FIRMWARE_NAME:Marlin 2.0.3 (GitHub) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:3D Printer EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
Recv:10:17:44.611: Cap:SERIAL_XON_XOFF:0
Recv:10:17:44.611: Cap:BINARY_FILE_TRANSFER:0
Recv:10:17:44.612: Cap:EEPROM:1
Recv:10:17:44.612: Cap:VOLUMETRIC:1
Recv:10:17:44.614: Cap:AUTOREPORT_TEMP:1
Recv:10:17:44.614: Cap:PROGRESS:0
Recv:10:17:44.615: Cap:PRINT_JOB:1
Recv:10:17:44.615: Cap:AUTOLEVEL:0
Recv:10:17:44.617: Cap:Z_PROBE:1
Recv:10:17:44.618: Cap:LEVELING_DATA:0
Recv:10:17:44.618: Cap:BUILD_PERCENT:0
Recv:10:17:44.618: Cap:SOFTWARE_POWER:0
Recv:10:17:44.620: Cap:TOGGLE_LIGHTS:0
Recv:10:17:44.621: Cap:CASE_LIGHT_BRIGHTNESS:0
Recv:10:17:44.621: Cap:EMERGENCY_PARSER:0
Recv:10:17:44.622: Cap:PROMPT_SUPPORT:0
Recv:10:17:44.624: Cap:AUTOREPORT_SD_STATUS:0
Recv:10:17:44.625: Cap:THERMAL_PROTECTION:1
Recv:10:17:44.625: Cap:MOTION_MODES:0
Recv:10:17:44.628: Cap:CHAMBER_TEMPERATURE:0
Send:10:17:44.628: M117 192.168.1.209:3344
Send:10:17:44.654: N10 M155 S1
Recv:10:17:44.655: X:0.00 Y:-5.00 Z:0.00 E:0.00 Count X:0 Y:-400 Z:0
Send:10:17:51.989: M117 Finished
Send:10:18:04.707: N11 G1 Z14.50 F1200
Send:10:18:06.061: N12 G1 Z24.50 F1200
Send:10:18:07.560: N13 G1 Z34.50 F1200

Comments

  • RepetierRepetier
    I see you are already on 0.94 - so if this on a raspberry pi do you see the bolt icon in gui and does it get oragnge or red? That would indicate power problems that are known to cause communication errors and even disconnects.

    If I see something like this
    Send:10:16:44.452: N20559 G1 X184.549 Y75.175 E2940.43325
    Recv:10:16:44.587: echo:Unknown command: ".43325"

    it is clear the firmware received a newline before .43325 instead of the full line. So that is a clear communication error like most of the probelms. Log is incomplete - it misses the ack and temp responses. But I guess you would also see many missed "ok" where o or k was missing leading to the timeouts.

    I even spotted this:
    Mesg:10:17:22.626: Connection closed by os during print ... trying reconnect for 10 seconds to continue ...
    Mesg:10:17:24.237: Dtr: true Rts: true
    Mesg:10:17:24.239: Connection continued
    Send:10:17:24.249: M117 ETA 13:23:49 day 30
    Send:10:17:24.249: N20582 G1 X117.265 Y79.02 E2956.58523

    where the os disconnected the serial connection and server tried to reconnect without reset. Not too successful as marlin decided to reset 20 seconds later or you did, can't say.

    Anyhow problem is not really the high precision assuming marlins buffer are long enough to capture the complete line. It is that communication is not error free. So check baud rate and if there are voltage problems which gui now indicates in the bolt icon. Maybe also an other usb cable might help. Try short and shielded if possible.
  • maeffjusmaeffjus
    Alright!
    First things first: Never undervoltage, it used to happen a lot in the past - and never affected anything. But since some months I got an official RPI power-supply which completely eliminated this.
    (BTW: We can also talk German if that is easier for you, I am German ;-)) 

    I have now changed the connection to be directly at the Raspberry PI and currently one print seems to finish.
    Lets wait some more hours ;-)
    So far - thanks!
  • RepetierRepetier
    To see if connection is better check "Verbindungsdaten" and see how many error per hour you get. If that reduces it is better then before.

    Also I speak german better english is better so more users understand the thread and might get answers to their own problem.
  • maeffjusmaeffjus
    That was my idea too - much more people will benefit from an english conversation!
    Thx!
Sign In or Register to comment.