I changed 32 moves buffer - it is not work. Now i can see that if print is freeze in Htop is all OK with CPU and RAM. In console command i can see the freezes also (i mean that an command have got freezes in the console if the print have a freeze also).
For help detect the problem i add an dmesg.log file. I changed port for the printer and it not helped.
<blockquote class="Quote">
Repetier said:
Without knowing exact times of blobs appearing it is not really possible to say where it happens. Best guess is where "wait" appears which is when firmware buffer is empty for a second without getting a new command. Here 2 cases where it happened:
< 18:06:40.691: N278038 G1 X76.424 Y85.736 E1989.07437
> 18:06:44.046: ok 15890
> 18:06:44.046: ok 15891
> 18:06:44.047: ok 15892
> 18:06:44.047: ok 15893
> 18:06:44.047: ok 15894
> 18:06:44.048: T:239.74 /240 B:80.00 /80 B@:85 @:194
> 18:06:44.049: Warning: Seems like we missed a ok - continue sending.
> 18:06:44.049: wait
> 18:06:44.050: T:239.49 /240 B:79.96 /80 B@:133 @:210
> 18:06:44.050: Warning: Seems like we missed a ok - continue sending.
> 18:06:44.050: wait
> 18:06:44.051: T:239.49 /240 B:79.92 /80 B@:71 @:191
> 18:06:44.051: Warning: Seems like we missed a ok - continue sending.
> 18:06:44.051: wait
< 18:06:44.052: N278039 M117 ETE 00:51:50
< 18:06:44.053: N278040 G1 X76.586 Y85.654 E1989.08309
> 18:08:33.574: ok 19927
< 18:08:33.574: N282076 G1 X62.639 Y96.271 E2165.21748
> 18:08:33.606: ok 19928
< 18:08:33.606: N282077 G1 X62.677 Y96.495 E2165.22752
> 18:08:33.632: ok 19929
< 18:08:33.632: N282078 G1 X62.534 Y96.289 E2165.22941
> 18:08:33.636: ok 19930
< 18:08:33.636: N282079 G1 X62.313 Y96.07 E2165.23619
> 18:08:33.641: ok 19931
< 18:08:33.641: N282080 G1 X62.125 Y95.935 E2165.24452
> 18:08:33.645: ok 19932
< 18:08:33.645: N282081 G1 X62.055 Y95.885 E2165.24832
> 18:08:34.847: ok 19933
> 18:08:34.847: ok 19934
> 18:08:34.847: ok 19935
> 18:08:34.848: ok 19936
> 18:08:34.848: ok 19937
> 18:08:34.849: T:239.74 /240 B:79.96 /80 B@:77 @:202
> 18:08:34.849: wait
< 18:08:34.849: N282082 M117 ETA 18:58:25 day 12
< 18:08:34.850: N282083 G1 X61.764 Y95.754 E2165.26242
What you see is that the server sends new commands as soon as it receives the "ok" but they seem to get delayed which you see as firmware also sends wait, so firmware had already send them correctly but it took time to be received.
Please connect during print with your pi and check with "top" cpu and memory usage. See if memory gets too high so it starts swapping or if some processes take too much cpu time so it will delay communication. It might also be a bandwidth problem with usb especially if you have a webcam with high resolution and view it. Network and printer go all over same usb bus so they may block communication to each other. Especially if you have a webcam without mjpg compression.
Good thing is there are no communication errors, so that is ok. It is not a baud rate thing.
One thing to improve might be use 32 moves buffer in firmware instead of default 16. That reduces the pauses and likelyhood to happen.
