Communication timeout - reset send buffer block

edited October 2017 in Repetier-Host
Hi folks,

I'm kind of new to the Repetier- FW (i used marlin until now), thereby I don't know a lot about those error messages. I also searched at the internet for help, but I could not find any equal cases. Maybe someone can tell me where's my poblem.

My Setup:
RADDS V1.5
Repetier- Host V2.0.5

And this is what I get in the logfile after restarting my printer:

18:39:51.175 : Printer reset detected - initalizing
18:39:51.175 : start
18:39:51.175 : Info:PowerUp
18:39:51.175 : N1 M111 S6*102
18:39:51.175 : Free RAM:84412
18:39:51.175 : SelectExtruder:0
18:39:51.175 : FlowMultiply:100
18:39:52.175 : wait
18:39:53.175 : wait
18:39:53.245 : Communication timeout - reset send buffer block
18:39:53.245 : N2 T0*56
18:39:53.255 : Error:expected line 1 got 2
18:39:53.255 : Resend:1
18:39:53.275 : Resend: N1 M111 S6*102
18:39:53.275 : ok
18:39:53.275 : Resend: N2 T0*56
18:39:53.285 : ok 1
18:39:53.285 : DebugLevel:6
18:39:53.285 : ok 2
18:39:53.285 : SelectExtruder:0
18:39:53.285 : N3 M80*24
18:39:53.285 : FlowMultiply:100
18:39:53.285 : N4 M105*35
18:39:53.285 : ok 3
18:39:53.285 : N1 M110*34
18:39:53.295 : ok 4
18:39:53.295 : N2 M115*36
18:39:53.295 : T:24.27 /0 B:24.31 /0 B@:0 @:0
18:39:53.295 : ok
18:39:53.295 : N3 M105*36
18:39:53.315 : ok 2
18:39:53.315 : N4 M114*35
18:39:53.315 : FIRMWARE_NAME:Repetier_0.92.9 FIRMWARE_URL:https://github.com/repetier/Repetier-Firmware/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1 REPETIER_PROTOCOL:3
18:39:53.315 : PrinterMode:FFF
18:39:53.315 : ok 3
18:39:53.315 : T:24.27 /0 B:24.31 /0 B@:0 @:0
18:39:53.315 : N5 M111 S6*98
18:39:53.325 : ok 4
18:39:53.325 : X:0.00 Y:0.00 Z:0.000 E:0.0000
18:39:53.325 : ok 5
18:39:53.325 : DebugLevel:6
18:39:53.325 : N6 T0*60
18:39:53.335 : N7 M80*28
18:39:53.335 : ok 6
18:39:53.335 : N8 M220 S100*105
18:39:53.335 : SelectExtruder:0
18:39:53.335 : FlowMultiply:100
18:39:53.335 : ok 7
18:39:53.335 : N9 M221 S100*105
18:39:53.345 : ok 8
18:39:53.345 : N10 M111 S6*86
18:39:53.345 : SpeedMultiply:100
18:39:53.345 : ok 9
18:39:53.345 : FlowMultiply:100
18:39:53.345 : N11 T0*10
18:39:53.355 : ok 10
18:39:53.355 : DebugLevel:6
18:39:53.355 : ok 11
18:39:53.355 : SelectExtruder:0
18:39:53.355 : FlowMultiply:100
18:39:54.355 : wait
18:39:55.355 : wait
18:39:55.865 : N12 M105*20
18:39:55.865 : ok 12
18:39:55.885 : T:24.15 /0 B:24.31 /0 B@:0 @:0
18:39:56.865 : wait
18:39:57.865 : wait
18:39:58.865 : wait
18:39:58.925 : N13 M105*21
18:39:59.866 : wait
18:40:00.866 : wait
18:40:01.876 : wait
18:40:01.977 : Communication timeout - reset send buffer block
18:40:01.977 : N14 M105*18
18:40:02.877 : wait
18:40:03.877 : wait
18:40:04.877 : wait
18:40:05.037 : Communication timeout - reset send buffer block
18:40:05.037 : N15 M105*19
18:40:05.877 : wait
18:40:06.877 : wait
18:40:07.878 : wait
18:40:08.098 : Communication timeout - reset send buffer block
18:40:08.098 : N16 M105*16
18:40:08.878 : wait
18:40:09.878 : wait
18:40:10.878 : wait
18:40:11.148 : Communication timeout - reset send buffer block
18:40:11.148 : N17 M105*17
18:40:11.878 : wait
18:40:12.878 : wait
18:40:13.888 : wait
18:40:14.208 : Communication timeout - reset send buffer block


What I don't understand are the Bold lines. Why do Ihave an error (how can I figure out the error's source?) and why do I have this communication error? The baud rates in the FW and on Repetier Host are the same (115200).
I can't explain, why do I get informations from the printer, and after a few seconds I have this communication error.

Many thanks in advance,
aykay

Comments

  • Please ignore the first occurence. You never now at which state you get the firmware running after reset so that happens and gets corrected.

    The real problem is after N13 M105*21 where the host does not get an "ok 13" only wait. And wait means nothing to do you missed the "ok" so the error message is correct. But subsequent calls of M105 also do not return an ok so it looks like the firmware is not receiving the data send by host, only send data.

    So why does it work in line 12 and not afterwards. Does this happen the same on all connection attempts?
    Is that on windows with host connected directly or over repetier-server?
  • Hi,

    the printer is connected directly over serial. I could solve the problem. My Arduino DUE- Board is actualli an UDOO- Quad.
    This means, that the USB- interface is controlled by the UDOO itself. Every times, when I power on the system, UDOO needs a few moments to startup. In this time, the communication is not interrupted by UDOO. The problem occure, after UDOO has finished to boot and interrupt the communication. I removed the SD- Card from UDOO (i actually don't need him) and now, all's fine!

    But now I have an other communication problem. I only can communicate with the board using a baud- rate of 115200 instead of 250000. I did the change in the SW and on the host too. I also changed the USB- cable, but it didn't helped.



  • You can set it in eeprom editor to 250000 and after a reset/emergency stop it gets effective. Setting it in configuration.h does not help if you do not change eeprom mode since it is stored in eeprom.
  • edited November 2017
    Well, done! It was truly this point. Thank you very much! ;-) after giving par. EEPROM_MODE an other value, the new baud rate were set and I were able to communicate again.

    But one problem, which I tried to solve by increasing the baud- rate, still occur.The Printer stumble sometimes. Due to the symptoms I suggest the problem is at the host side, repectively at Repetier- Host. Mostly when the printer has to print e. g. holes or round shapes in general. To counteract this phenomen, I lowered the solution of the .stl- file, which helped a bit, but not entirely. Are there any other tasks I can try to solve this issue?

    EDIT:

    Here's a printout from the log:

    20:26:02.099 : Error:expected line 19305 got 19306
    20:26:02.099 : Resend:19305
    20:26:06.915 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:26:06.923 : Error:expected line 19319 got 19325
    20:26:06.923 : Resend:19319
    20:26:08.532 : Error:expected line 19356 got 19357
    20:26:08.532 : Resend:19356
    20:26:11.653 : Error:expected line 19385 got 19389
    20:26:11.653 : Resend:19385
    20:26:14.152 : Error:expected line 19400 got 19402
    20:26:14.152 : Resend:19400
    20:26:20.824 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:26:20.832 : Error:expected line 19461 got 19467
    20:26:20.832 : Resend:19461
    20:26:27.779 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:26:27.791 : Error:expected line 19504 got 19510
    20:26:27.791 : Resend:19504
    20:26:28.900 : Resend:19550
    20:26:33.477 : Error:expected line 19571 got 19572
    20:26:33.477 : Resend:19571
    20:26:34.354 : Error:expected line 19580 got 19583
    20:26:34.354 : Resend:19580
    20:26:36.424 : Error:expected line 19595 got 19597
    20:26:36.424 : Resend:19595
    20:26:38.182 : Error:expected line 19606 got 19608
    20:26:38.182 : Resend:19606
    20:26:40.219 : Error:expected line 19619 got 19620
    20:26:40.219 : Resend:19619
    20:26:41.302 : Error:expected line 19628 got 19630
    20:26:41.302 : Resend:19628
    20:26:46.905 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:26:46.912 : Error:expected line 19685 got 19691
    20:26:46.912 : Resend:19685
    20:26:53.862 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:26:53.870 : Error:expected line 19733 got 19739
    20:26:53.870 : Resend:19733
    20:26:59.076 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:26:59.085 : Error:expected line 19780 got 19786
    20:26:59.085 : Resend:19780
    20:27:00.817 : Error:expected line 19808 got 19809
    20:27:00.817 : Resend:19808
    20:27:02.575 : Error:expected line 19822 got 19823
    20:27:02.575 : Resend:19822
    20:27:04.634 : Error:expected line 19835 got 19836
    20:27:04.634 : Resend:19835
    20:27:05.993 : Error:expected line 19842 got 19845
    20:27:05.993 : Resend:19842
    20:27:08.313 : Error:expected line 19856 got 19858
    20:27:08.313 : Resend:19856
    20:27:16.465 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:27:16.472 : Error:expected line 19942 got 19948
    20:27:16.472 : Resend:19942
    20:27:28.635 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:27:28.642 : Error:expected line 19991 got 19997
    20:27:28.642 : Resend:19991
    20:27:30.272 : Error:expected line 20030 got 20032
    20:27:30.272 : Resend:20030
    20:27:30.488 : Resend:20030
    20:27:33.853 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:27:33.876 : Error:expected line 20030 got 20036
    20:27:33.876 : Resend:20030
    20:27:34.918 : Error:expected line 20059 got 20063
    20:27:34.918 : Resend:20059
    20:27:39.205 : Error:expected line 20085 got 20087
    20:27:39.205 : Resend:20085
    20:27:44.286 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:27:44.292 : Error:expected line 20132 got 20138
    20:27:44.292 : Resend:20132
    20:27:48.692 : Error:expected line 20156 got 20157
    20:27:48.692 : Resend:20156
    20:27:48.906 : Resend:20156
    20:27:52.979 : Warning: Seems like we missed a ok, got a wait - continue sending.
    20:27:52.985 : Error:expected line 20156 got 20163
    20:27:52.985 : Resend:20156

    As you can see, the warnings and errors are very frequently.

  • Have you tried if 115200 has as much errors as now? All this comes from communication errors. I remember that udoo has a problem with this under some circumstances. Seems that these add so much noise that you got problems with crosstalk. sdcard is already one problem you found. Anyhow if 115200 works stable that is good enough. Especially if you are running repetier-server on the udoo you should have good communication speed if it has not so much errors.
  • I tried to run it with 115200 baud, but the amount of errors still remains. Now I went back on using the udoo together with the repetier- server. But now it seems that the server can't connect to the arduino due. I realy don't know what's to do now.
    I used a fresh image (udoobuntu-udoo-qdl-desktop_2.1.4.img) and installed the webserver as described (https://www.repetier-server.com/manuals/0.50/index.html).
    I also did a few changes on my router, to set up the udoo with an static ip.
    After this, I uploaded the configured FW (115200 baud) via the preinstalled arduino ide (1.6.5, I guess) directly from udoo to the sam processor.
    As the changes were done, I rebooted the system and could rech it after, via http://<ip address>:3344
    All went fine so far. But now, at configuration step 2, the server couldn't reach the printer trough port /dev/ttymxc3 with 115200 baud (I also used the autodetect- function).
    I tried this whole procedure a couple times, but without any success.

    Do you have any ideas what can I do further?





  • EDIT: When I upload the FW, using the preinstalled arduino version on udoo, then I get an error somewhen.

    Sketch uses 99,724 bytes (19%) of program storage space. Maximum is 524,288 bytes.
    Erase flash
    Write 102484 bytes to flash
    [                              ] 0% (0/401 pages)
    SAM-BA operation failed

    To solve this issue, I had to burn the udoo Image again, and do all the necessary installations. After this Task, I could reprogram the FW. i guess the Server Problem has something to do with this. But I have no idea where I do an error.

  • As far as I know the UDOO has a switch for the usb connection. You can have it internally on the board and then ttymxc3 would be the device if i understood you right. But if that does not happen you could simply connect usb cable to programming port and use that port (or the native port if you favour that). I think your problem is just that the switch in not activated for internal connection you you need to use the usb cable.
  • edited November 2017
    That's right, there is a Jumper (J18) which allows you to change the way the data goes to. However, it didn't worked for me, even i try with the cmd "stty -F /dev/ttymxc3 cs8 115200 ignbrk -brkint -icrnl -imaxbel -opost -onlcr -isig -icanon -iexten -echo -echoe -echok -echoctl -echoke noflsh -ixon -crtscts"
    from this link: (https://www.udoo.org/docs/Hardware_&_Accessories/IMX6_And_Sam3X_Communication.html) After sending this cmd, i was at least able to download the Firmware to the SAM, but nothing more. I tried a lot of cmd's but without succsess.

    Unfortunally UDOO is dead for me. I bought an arduino due and connected him via usb cable to an host computer.
    Many thanks for your support!
Sign In or Register to comment.