Home › Repetier-Host › Windows
Communication timeout — reset send buffer block
Comments
-
Is transfer protocol set to automatic?
Did you upload a compatible firmware to the arduino?
Anything in the log? At reset the firmwares send «start» if baud rate is correct. -
Transfer protocol is set to autodetect. I have uploaded the latest version of Marlin to the arduino.
Do you mean pressing the rest button on the board?The log also says «No start signal detected — forcing start».
-
«No start signal detected — forcing start». means it did not see the «start». Pressing reset button on arduino should show it if connection is established and baud rate is correct. RAMPS is the most widely used and tested system. Autodetect is ok. The only thing making sense is wrong baud rate. Please try different baud rates in host especially 115200 and 250000 and see if it changes.
-
Now, when I try to connect I get the error «The port ‘COM6’ does not exist».
-
That is easy to verify in hardware manager. All active com ports are listed there. But also make sure no other software is using the port at the moment. Windows does not support simultaneous opening of same port.
-
Regarding Com port. If you open RH select config — printer settings and hit the drop down arrow on port, you should see your available ports there. It is usually NOT com1 for the printer if shown. There should be at least one other. If I unplug my printer from the USB the available port will disappear from the choices and reappear when I plug it back in. This is before I am connected to the printer.
-
It turned out that there was a duplicate of the port I was using listed, and using the other one worked. It is still having connection problems though.
-
Hi All
i have tried a lot of things blindly and may need to go back and study the issues but I got this Print-Rite/Colido DIY printer with Repetier Host 1_5_5A running on windows 7.02:11:45.430 : Communication timeout — reset send buffer block
02:11:55.804 : No start signal detected — forcing start
02:12:35.880 : Communication timeout — reset send buffer block
02:13:15.961 : Communication timeout — reset send buffer block
02:13:56.065 : Communication timeout — reset send buffer block
02:14:36.157 : Communication timeout — reset send buffer block2:15:52.129 : <Slic3r> => Exporting G-code to composition.gcode
02:15:52.550 : <Slic3r> Done. Process took 0 minutes and 1.232 seconds
02:15:52.550 : <Slic3r> Filament required: 254.0mm (0.6cm3)
02:15:56.247 : Communication timeout — reset send buffer blockiI am also getting this message repeatedly ‘unable to find entry point named ‘glGenBufers’ in dll open gi32.dll’Any nuggets of wisdom for this newbie? -
made another attempt and this is what I got:02:38:30.971 : Starting object analyser …
02:38:30.971 : Object is manifold.
02:38:30.971 : Analysing finished.
02:38:36.151 : Slic3r command:C:Program FilesPrint-Rite-Repetier-HostSlic3rslic3r.exe —load «slic3r_settings.ini» —print-center 128.23,103.14 -o «composition.gcode» «composition.amf»
02:38:37.368 : <Slic3r> => Processing triangulated mesh
02:38:37.399 : <Slic3r> => Generating perimeters
02:38:37.742 : <Slic3r> => Preparing infill
02:38:37.805 : <Slic3r> => Infilling layers
02:38:38.117 : <Slic3r> => Generating skirt
02:38:38.117 : <Slic3r> => Generating brim
02:38:38.148 : <Slic3r> => Exporting G-code to composition.gcode
02:38:38.460 : <Slic3r> Done. Process took 0 minutes and 1.092 seconds
02:38:38.475 : <Slic3r> Filament required: 398.4mm (1.0cm3)
02:38:38.585 : Unable to find an entry point named ‘glGenBuffers’ in DLL ‘opengl32.dll’.
02:38:42.609 : Communication timeout — reset send buffer block
02:39:22.686 : Communication timeout — reset send buffer block
02:40:02.762 : Communication timeout — reset send buffer block
02:40:42.839 : Communication timeout — reset send buffer block
02:41:22.915 : Communication timeout — reset send buffer block
02:42:02.983 : Communication timeout — reset send buffer block
02:42:43.060 : Communication timeout — reset send buffer block
02:42:46.289 : Starting object analyser …
02:42:46.289 : Object is manifold.
02:42:46.289 : Analysing finished.
02:42:54.105 : Slic3r command:C:Program FilesPrint-Rite-Repetier-HostSlic3rslic3r.exe —load «slic3r_settings.ini» —print-center 128.23,103.14 -o «composition.gcode» «composition.amf»
02:42:55.291 : <Slic3r> => Processing triangulated mesh
02:42:55.322 : <Slic3r> => Generating perimeters
02:42:55.665 : <Slic3r> => Preparing infill
02:42:55.727 : <Slic3r> => Infilling layers
02:42:56.055 : <Slic3r> => Generating skirt
02:42:56.071 : <Slic3r> => Generating brim
02:42:56.086 : <Slic3r> => Exporting G-code to composition.gcode
02:42:56.414 : <Slic3r> Done. Process took 0 minutes and 1.123 seconds
02:42:56.414 : <Slic3r> Filament required: 398.4mm (1.0cm3)
02:43:23.168 : Communication timeout — reset send buffer block
02:44:03.244 : Communication timeout — reset send buffer block
02:44:43.321 : Communication timeout — reset send buffer block
02:45:23.397 : Communication timeout — reset send buffer block
02:46:03.474 : Communication timeout — reset send buffer block
02:46:43.550 : Communication timeout — reset send buffer block
02:47:23.627 : Communication timeout — reset send buffer block
02:48:03.719 : Communication timeout — reset send buffer block
02:48:43.795 : Communication timeout — reset send buffer block
02:49:23.872 : Communication timeout — reset send buffer block
02:50:03.948 : Communication timeout — reset send buffer block
02:50:44.025 : Communication timeout — reset send buffer block
02:51:24.097 : Communication timeout — reset send buffer block
02:52:04.139 : Communication timeout — reset send buffer block
02:52:44.180 : Communication timeout — reset send buffer block
02:53:24.196 : Communication timeout — reset send buffer block
02:54:04.271 : Communication timeout — reset send buffer block
02:54:44.346 : Communication timeout — reset send buffer block
02:55:24.425 : Communication timeout — reset send buffer block
02:56:04.514 : Communication timeout — reset send buffer block
02:56:44.606 : Communication timeout — reset send buffer block
02:57:24.687 : Communication timeout — reset send buffer block
02:58:04.763 : Communication timeout — reset send buffer block
02:58:44.837 : Communication timeout — reset send buffer block
02:59:24.884 : Communication timeout — reset send buffer block
03:00:04.990 : Communication timeout — reset send buffer block
03:00:45.082 : Communication timeout — reset send buffer block
03:01:25.160 : Communication timeout — reset send buffer block
03:02:05.161 : Communication timeout — reset send buffer block
03:02:45.228 : Communication timeout — reset send buffer block
03:03:25.316 : Communication timeout — reset send buffer block
03:04:05.387 : Communication timeout — reset send buffer block
03:04:45.498 : Communication timeout — reset send buffer block
03:05:25.573 : Communication timeout — reset send buffer block
03:06:05.668 : Communication timeout — reset send buffer block
03:06:45.775 : Communication timeout — reset send buffer block
03:07:25.867 : Communication timeout — reset send buffer block
03:08:05.960 : Communication timeout — reset send buffer block
03:08:46.067 : Communication timeout — reset send buffer block
03:09:26.131 : Communication timeout — reset send buffer block
03:10:06.141 : Communication timeout — reset send buffer block
03:10:46.206 : Communication timeout — reset send buffer block
03:11:26.309 : Communication timeout — reset send buffer block
03:12:06.401 : Communication timeout — reset send buffer block
03:12:46.431 : Communication timeout — reset send buffer block
03:13:26.492 : Communication timeout — reset send buffer block
03:14:06.600 : Communication timeout — reset send buffer block
03:14:46.676 : Communication timeout — reset send buffer block
03:15:26.753 : Communication timeout — reset send buffer block
03:16:06.854 : Communication timeout — reset send buffer block
03:16:46.870 : Communication timeout — reset send buffer block
03:17:26.968 : Communication timeout — reset send buffer block
03:18:07.020 : Communication timeout — reset send buffer block
03:18:47.074 : Communication timeout — reset send buffer block
03:19:27.173 : Communication timeout — reset send buffer block
03:20:07.277 : Communication timeout — reset send buffer block
03:20:47.357 : Communication timeout — reset send buffer block
03:21:27.430 : Communication timeout — reset send buffer block
03:22:07.510 : Communication timeout — reset send buffer block
03:22:47.584 : Communication timeout — reset send buffer block
03:23:27.664 : Communication timeout — reset send buffer block
03:24:07.734 : Communication timeout — reset send buffer block
03:24:47.754 : Communication timeout — reset send buffer block
03:25:27.834 : Communication timeout — reset send buffer block
03:26:07.904 : Communication timeout — reset send buffer block
03:26:47.984 : Communication timeout — reset send buffer block
03:27:28.064 : Communication timeout — reset send buffer block
03:28:08.134 : Communication timeout — reset send buffer block
03:28:48.214 : Communication timeout — reset send buffer block
03:29:28.286 : Communication timeout — reset send buffer block
03:30:08.288 : Communication timeout — reset send buffer block
03:30:48.369 : Communication timeout — reset send buffer block
03:31:28.439 : Communication timeout — reset send buffer block
03:32:08.519 : Communication timeout — reset send buffer block
03:32:48.599 : Communication timeout — reset send buffer block
03:33:28.669 : Communication timeout — reset send buffer block
03:34:08.751 : Communication timeout — reset send buffer block
03:34:48.844 : Communication timeout — reset send buffer block
03:35:28.914 : Communication timeout — reset send buffer block
03:36:08.994 : Communication timeout — reset send buffer block
03:36:49.066 : Communication timeout — reset send buffer block
03:37:29.146 : Communication timeout — reset send buffer block
03:38:09.226 : Communication timeout — reset send buffer block
03:38:49.299 : Communication timeout — reset send buffer block
03:39:29.381 : Communication timeout — reset send buffer block
03:40:09.453 : Communication timeout — reset send buffer block
03:40:49.533 : Communication timeout — reset send buffer block
03:41:29.604 : Communication timeout — reset send buffer block
03:42:09.684 : Communication timeout — reset send buffer block
03:42:49.764 : Communication timeout — reset send buffer block
03:43:29.834 : Communication timeout — reset send buffer block
03:44:09.914 : Communication timeout — reset send buffer block
03:44:49.986 : Communication timeout — reset send buffer block
03:45:30.066 : Communication timeout — reset send buffer block
03:46:10.147 : Communication timeout — reset send buffer block
03:46:50.217 : Communication timeout — reset send buffer bl
-
Did the printer every respond on any command? If not, your baud rate may be wrong or you have used the wrong port at all. Assuming you did not change the ColLiDo defaults baud rate should match, but you never know. Port is set to auto be default so it uses the first available com port, which is not necessary the right one if you have multiple ports.
-
This solves the Problem for me.
I got a new USB to serial adapter on port 11. «11» is before «7» (it’s Windows10…)
Setting the port to «COM7» instead of «Auto» was the solution. -
Definitely, there are problems of communication with Repetier and Windows 7 since this one is no longer supported. I passed through all the problems and suggestions described above to not avail. After many hours and days found out that the driver for Repetier is strangely missing from my Lenovo Thinkcentre Win7, and is no longer available via the internet or else.Finally, downloaded Repetier to my new Laptop with Win 10 and everything has been fine since the very beginning. Also, I have had Repetier with another small computer with Windows XP since five years ago, and it works perfectly. By the way, the printers in my two laptops are RepRap Prusa i3 and Prusa Mendel, both made five years ago.
-
Standard Repetier-Host does not contain any drivers at all. You need to install them from printer manufacturer. Win 10 has many of them in it’s autodetect system so it installs them when needed.
-
I have Windows 10 (64-bit), RAMPS 1.4 with mega2560, Repetier 1.0.4 (final). I’ve been getting this «Communication timeout — reset send buffer block» / «Serial com error:System.IO.Ports.SerialErrorReceivedEventArgs» error after printer prints up to line N16050.
Port: COM7
Baud Rate: 115200
Transfer Protocol: ASCII
RTS: Low to High
DTR: Low to HighReceive Cache Size: 64
Communication Timeout: 40sUse Ping-Pong Communication: unchecked
I’ve ensured my Power Options does NOT attempt to suspend the USB port. I’ve tried TWO different USB ports on my Dell Optiplex-790.
I have NOT have this problem until a few months ago.
I have dialed my Feedrate down to 50%, I wonder if the Communication Timeout could be too short, with the feedrate reduced…
Will try increasing Cache and Communication Timeout (maybe enable Ping-Pong)
-
Well that didn’t take long (to error)…
Well, the WAIT (for the Communication Timeout) took longer (because I increased it)…
THIS time, it stopped printing after N330 (still laying down the 1st layer)… Previously it got up to 3mm (at .2mm/layer).
So, it doesn’t look like these parameters FIX the problem!
Time to take the printer control box open, and see if there’s anything obvious inside!
-
Serial com error:System.IO.Ports.SerialErrorReceivedEventArgs is an error message coming from windows/driver is most likely the problem. Like lost connection or something else that went wrong unexpectedly. Any changes with cables and their positions/power supply/position of 3d printer before it started to happen?
-
Well, I found that the fan at the extruder was not turning…
Luckily, I already had a replacement…
Testing again…
-
Nope…
Made it to line N10698, then stop.
I did hear the Windows sound for USB disconnect… Guess it’s time for the screwdrivers (to open up the printer controller box).
-
Serial com error:System.IO.Ports.SerialErrorReceivedEventArgs is an error message coming from windows/driver is most likely the problem. Like lost connection or something else that went wrong unexpectedly. Any changes with cables and their positions/power supply/position of 3d printer before it started to happen?
Sadly, no…
I’ve taken control box (housing Arduino/Mega2560 and power supply) apart, checked Power Supply, reseated USB cable.
Even replaced fan cooling the control box.
Same issue.
I’m not ruling out PC being the culprit…
I’ll see what happens if I move the printer to one of my laptops, and see if that makes any difference.
If I become really masochistic, I’ll fire up a Raspberry Pi with Repetier Server…
Thanks for the response.
-
With Mega2560 I had so far no problems with Windows. But lately they are not in use any more due to switching to 32bit boards more and more. You can also test different usb port. Especially usb 3 ports are not really working better and performance is not needed anyway.
A pi is not really masochistic any more. At least pi 4 has a quite good performance. -
guess you use ramps/mega combination.Question:original ArduinoMega or plagiate with CH340 usb Converter? in tat case it might be a driver problem.How is it powered? 12V? 24V?I remember having trouble with a plagiate Mega due to overheating the onboard 5V Voltage regulator .
-
guess you use ramps/mega combination.Question:original ArduinoMega or plagiate with CH340 usb Converter? in tat case it might be a driver problem.How is it powered? 12V? 24V?I remember having trouble with a plagiate Mega due to overheating the onboard 5V Voltage regulator .
RAMPS 1.4/Mega2560. shows up as CH340 USB Serial in Windows.
I moved the USB connection from the PC (case) USB port, to a powered hub (actually one of my monitors), and I was able to print my 10 hour print without USB disconnect.
Looks like my issue is resolved!
- Вопросы
-
Вопросы
+1
Доброго времени суток!
Такая проблема: во время печати перестал печатать принтер. Пользуюсь программой Repetier-Host. Было напечатано примерно 70% модели, как вдруг печать остановилась, при этом в программе произошло «зависание» печати, но сама программа откликалась на команды(мог переходить по вкладкам, нажимать паузу, и возобновлять печать), но никаких действий со стороны принтера не происходило. Будто программа перестала передавать сигналы принтеру. Температурная шкала стола и экструдера «зависла на месте». Скачков напряжения не наблюдалось, Компьютер сильно не «нагружался», работал стабильно. При этом, программа выдала ошибку/ предупреждение: » Communication timeout — reset send buffer block». Кабель USB не трогали.
Сервис поддержки клиентов работает на платформе UserEcho
«Communication timeout — reset send buffer block» — Repetier-Host V1.6.1 ARGH!
This problem seems to be completely random. sometimes it happens within seconds of my print, sometimes the printer doesnt need to have printed and sometimes (most annoyingly) 6 hours into a 6 and a half hour print!
Basically the printer is happy and printing, then I get «Communication timeout — reset send buffer block» in my log on repetier host.
The printer stops moving (but the heaters stay on) and if i click ANYTHING in the repetier software, the software crashes and not even ctrl-alt-delete then end process works. In order to reconnect to my printer, I have to reset my computer, losing all progress on the print and interuppting whatever else I am doing.
I’ve tried hunting forums and google and there is not an answer that I can find that is effective.
I have tried software reinstall and disconnecting the power supply from RAMPS and putting it back, but nothing.
Any advice?
SO ?
PC, Windows are NOT «real time» computer and OS !
Print from the SD card.
Did you extended the usb cable with an extender ?
Would a rasberry Pi work better?
There is no extender.
It has worked fine using windows and PC for the past 6 month… this just came out of the blue.
Tried new USB cable, no difference
OK, all this time and i’m still getting this problem.
I’ve tried changing firmware, changing the USB cable taking the printer down and rebuilding it, tried printing from the SD card but it just beeps at me and does nothing.
Nothing is fixing this problem and it is basically restricting my print times to 2-4 hours, and even then it could be just 10 mins.
Has anyone got any idea how I could fix it?
For the first few months of running the printer I never had a problem, it came out of nowhere.
I’m getting the same issue. At one stage, the USB connector on my RAMBo board came loose, so I soldered on a cable. I think the issue is occurring there, after extended use has perhaps worn the soldered connection.
I have the same problem on two machines with two different PCs running Ubuntu 14.04 and 16.04 and two different control boards—an ArduinoMega2560 with RAMPS 1.4 and a Printrboard Rev. F. One machine runs R-H 1.6.2—The Arduino/RAMPS. The other runs R-H 1.6.0. One of the USB cables uses a cable extender. The other—a 6′ cable—does not. Both run at 115200 bps.
The problem occurs randomly, sometimes after several successful prints. It can occur after a few minutes, or after hours and hours of printing. Similar to Muntahunta’s limiting print time to 2 to 4 hours, I’m mitigating the problem by limiting the number of objects I print at one time.
Last I looked Repetier-Host is a .net application
On Linux this is emulated (badly, being a Microsoft windows thing.)
In my view If you must use Repetier-Host, use windows
Or as others have said, use a SD card. And avoid all the host machine issues
I would advice to run the Repetier server, and print from there, you can then add jobs via Repetier host or via a web based interface.
You can also see the progress, in the host or via web page. With the webserver I didn’t see these problems. But they advice to use good quality usb cables.
Also it is smart to post Repetier problems in the Repetier forum,
[forums.reprap.org]
P3steel DXL, with Due/RADDS/Raps128 dual Wade’s extruder
I’ve been running Repetier on Linux for over four years using the ‘mono’ emulator. Where I did have some issues early on, those seem to have been resolved. Searching the Internet about this problem, it seems unrelated to the OS used.
Thanks for the SD suggestion. I will try the SD card on the Printrbot. The Arduino/RAMPS, though, doesn’t have an SD as an option. (I may swap this out for a Megatronics board I have). Thanks again. You helped. I really do want to feel more comfortable doing prints taking several hours.
Thanks for the advice—and the reminder to post to the Repetier forum. You’re right. Repetier is quite responsive.
do you have the «12864 LCD Full Graphic Smart Display Controller»
if so you have SD card port , it is on the display as far as I can remember
P3steel DXL, with Due/RADDS/Raps128 dual Wade’s extruder
I was finally able to resolve the communication timeout error but pulling the SD card out of the slot behind the display and printing directly from my computer. Every time I tried to print from the SD there was an error, but since removing the SD there have been no errors.
i had the same prob i turned off Rep server and reinstalled usb driver for the printer not had it since touch wood
The fan flicking on is normal at startup, also the red flashing light is a good sign. Sounds to me that the driver that you need to communicate with the printer is either not loaded or corrupt, there is only one baud rate that is correct, so if you haven’t got it set to 115200 then it will never work. Does the USB port show up in the Device manager under ports? It could be any number so go take a look, mines is port 4 on one PC and port 6 on another, so I’d guess it can be anything it finds convenient when it installs.
One other catch-me-out thing that happens with the printer is, that it sometimes waits for the heated bed to warm up to temp and since this printer doesn’t have one then you will wait forever.
I reckon the culprit is simply communication though 
good luck mate.
Cheers Hughee. Yes I have it set to 115200. I just tried all the other to eliminate that as an issue. If I go to the device settings I can see it on port 3. So the printer is connected and can be seen by the computer. On the printrite software it appears to connect but isn’t reading the extruder temp or responding to any commands. I am on a Windows 10 pc so hopefully that isn’t an issue.
My printer is running fine on Windows 10 mate, I have a second printer running on Vista, so I think you can rule out the operating system. Have you tried different USB ports? sometimes the front and back ports can play silly buggers, also are you using the cable that came with the printer, as again sometimes the cables can be a source of problems. The reason I say that is, not all USB cables have that ferrite bead filter thingo around them that the Print-Rite has. You could try Matter Control, that’s another piece of 3D software I use at times and it works well. At least it would let you see if it’s the software that has the problem, if Matter Control see’s the temp and Repetier doesn’t then you know the culprit. Also if you don’t have the latest version of Repetier Host then go grab it and give it a try, it works well for me to. Sounds now like you have a corrupt install of Repetier, I’d definitely uninstall and reinstall just in case.
Thanks for the quick reply. I have uninstalled and reinstalled twice and also downloaded and installed the latest version off the website. the cable works fine on the mac but when I load a file into repetier the code is a strange font and will not run. if I load a file from the usb stick that came with the printer it will load and run fine but unfortunately I cant print any of the pieces I need to. on the pc the files load fine and look good but still no connection. I have tried craftware and cura but seems to be same problem. I will try to find another cable in the morning but I assumed it wasn’t the cable because it works on the mac. Thanks.
What file is it your trying to load and run mate? Do you get the strange font with all the files you load, or only some? that does not sound right. Also is it the Gcode that goes funny or text on the screen? or the log window? I think your going to have to go back to scratch and start all over again. The printer and cable are good if they both work with the Mac so start looking at the software your installing, could it be the anti-virus you have, or corruption in a file, until you resolve the strange text business I think your going to struggle. Have you tried it out using a laptop or other PC to see if it is your PC? Have you checked the USB setup in the Bios settings, they can sometimes be set for Legacy USB support, maybe it’s switched off, I’m just trying to figure out what went wrong mate so if you have tried any or all of this then sorry. Have you checked the file you downloaded to do the install, Windows 10 sometimes marks them as blocked because they came from the net, normally you can right click and look at the files property’s and unblock it, it’s possible that could be causing an issue.
I have about 5 parts from thingiverse I was trying to print and all of the show up as a strange unreadable font in the gcode. I download the files and then in repetier I load file and select the object file. then it loads into the gcode but is all hieroglyphics. I have tried on another pc laptop and I can manually control the extruder and calibrate but it will not execute the print and gives me the same communication timeout error when I select print the will no longer let me manually control it. three different computers with three different issues. This is getting old.
Maybe the slicer isn’t working properly, are you using the default one or some other slicer to do the job? Try a different slicer, I think there is a choice in Repetier Host as to which one to use. Gcode should be all text, so god knows where the hieroglyphics are coming from 