Halfway through Printing I get a Communications error

December 31, 2019, 2:43 pm

≫ Next: Printer suddenly stops mid print

≪ Previous: Firmware upgrade from version 1.x to 2.x. User experience.

Below is part of the log of my print job due to the word limit in the forum. Everything was going fine until it got Communication timeout - reset send buffer block. Please Help me as this is will not allow me to use my 3-D printer until this is fixed. I am using a Monoprice MP Mini Delta Printer. Thanks

< 5:18:37 PM: ok N35087 P0 B15

< 5:18:37 PM: ok N35088 P0 B15

< 5:18:37 PM: ok N35089 P0 B15

< 5:18:37 PM: ok N35090 P0 B15

< 5:18:37 PM: ok N35091 P0 B15

< 5:18:37 PM: ok N35092 P1 B15

< 5:18:37 PM: ok N35093 P1 B15 T:205.2 /205.0 B:51.0 /60.0 T0:205.2 /205.0 @:4 B@:127

< 5:18:37 PM: ok N35094 P1 B15

< 5:18:37 PM: ok N35095 P0 B15

< 5:18:37 PM: ok N35097 P0 B14

< 5:18:37 PM: ok N35098 P0 B14

< 5:18:38 PM: ok N35098 P0 B15

5:18:38 PM: Printing layer 101 of 267

< 5:18:38 PM: ok N35099 P1 B15

< 5:18:38 PM: ok N35100 P0 B15

< 5:18:38 PM: ok N35102 P0 B14 T:204.6 /205.0 B:50.8 /60.0 T0:204.6 /205.0 @:78 B@:127

< 5:18:38 PM: ok N35102 P0 B15

< 5:18:39 PM: ok N35103 P0 B15

< 5:18:39 PM: ok N35104 P0 B15

< 5:18:39 PM: ok N35105 P0 B15

< 5:18:39 PM: ok N35107 P0 B14

< 5:18:39 PM: ok N35108 P0 B14

< 5:18:39 PM: ok N35108 P0 B15

< 5:18:39 PM: ok N35109 P0 B15

< 5:18:39 PM: ok N35111 P0 B14 T:204.8 /205.0 B:49.9 /60.0 T0:204.8 /205.0 @:54 B@:127

< 5:18:39 PM: ok N35111 P0 B15

< 5:18:40 PM: ok N35112 P0 B15

< 5:18:40 PM: ok N35113 P0 B15

< 5:18:40 PM: ok N35114 P0 B15

< 5:18:40 PM: ok N35116 P0 B14

< 5:18:40 PM: ok N35117 P0 B14

< 5:18:40 PM: ok N35117 P0 B15

< 5:18:40 PM: ok N35118 P0 B15

< 5:18:40 PM: ok N35119 P0 B15 T:204.4 /205.0 B:50.3 /60.0 T0:204.4 /205.0 @:95 B@:127

< 5:18:41 PM: ok N35120 P0 B15

< 5:18:41 PM: ok N35121 P0 B15

< 5:18:41 PM: ok N35122 P0 B15

< 5:18:41 PM: ok N35123 P0 B15

< 5:18:41 PM: ok N35124 P0 B15

< 5:18:41 PM: ok N35125 P0 B15

< 5:18:41 PM: ok N35126 P0 B15

< 5:18:41 PM: ok N35127 P1 B15

< 5:18:41 PM: ok N35128 P0 B15

< 5:18:41 PM: ok N35129 P0 B15

< 5:18:41 PM: ok N35130 P0 B15

< 5:18:41 PM: ok N35131 P0 B15

< 5:18:41 PM: ok N35132 P0 B15

< 5:18:41 PM: ok N35133 P0 B15

< 5:18:41 PM: ok N35134 P0 B15

< 5:18:41 PM: ok N35135 P0 B15

< 5:18:41 PM: ok N35136 P0 B15

< 5:18:41 PM: ok N35137 P0 B15

< 5:18:41 PM: ok N35138 P0 B15

< 5:18:41 PM: ok N35139 P0 B15

< 5:18:41 PM: ok N35140 P0 B15

< 5:18:41 PM: ok N35141 P0 B15

< 5:18:41 PM: ok N35142 P0 B15

< 5:18:41 PM: ok N35143 P0 B15

< 5:18:41 PM: ok N35144 P0 B15

< 5:18:41 PM: ok N35145 P0 B15

< 5:18:41 PM: ok N35146 P0 B15

< 5:18:41 PM: ok N35147 P0 B15

< 5:18:41 PM: ok N35149 P0 B14

< 5:18:41 PM: ok N35150 P0 B14

< 5:18:41 PM: ok N35151 P0 B14

< 5:18:41 PM: ok N35151 P0 B15

< 5:18:41 PM: ok N35152 P1 B15 T:205.1 /205.0 B:50.7 /60.0 T0:205.1 /205.0 @:29 B@:127

< 5:18:42 PM: ok N35153 P0 B15

< 5:18:42 PM: ok N35154 P0 B15

< 5:18:42 PM: ok N35155 P0 B15

< 5:18:42 PM: ok N35156 P0 B15

< 5:18:42 PM: ok N35157 P0 B15

< 5:18:42 PM: ok N35158 P1 B15

< 5:18:42 PM: ok N35159 P1 B15 T:204.9 /205.0 B:51.4 /60.0 T0:204.9 /205.0 @:47 B@:74

< 5:18:43 PM: ok N35160 P1 B15

< 5:18:43 PM: ok N35161 P1 B15

< 5:18:43 PM: ok N35162 P1 B15

< 5:18:43 PM: ok N35163 P2 B15

< 5:18:43 PM: ok N35164 P2 B15

< 5:18:43 PM: ok N35166 P0 B14

< 5:18:43 PM: ok N35166 P1 B15

< 5:18:43 PM: ok N35167 P1 B15

< 5:18:43 PM: ok N35168 P1 B15

< 5:18:43 PM: ok N35169 P1 B15

< 5:18:43 PM: ok N35170 P1 B15

< 5:18:43 PM: ok N35171 P0 B15

< 5:18:43 PM: ok N35172 P0 B15

< 5:18:43 PM: ok N35173 P0 B15

< 5:18:43 PM: ok N35174 P0 B15

< 5:18:43 PM: ok N35176 P0 B14 T:204.9 /205.0 B:50.3 /60.0 T0:204.9 /205.0 @:59 B@:127

< 5:18:43 PM: ok N35176 P0 B15

< 5:18:43 PM: ok N35177 P0 B15

< 5:18:43 PM: ok N35178 P0 B15

< 5:18:43 PM: ok N35179 P0 B15

< 5:18:43 PM: ok N35180 P1 B15

< 5:18:43 PM: ok N35181 P1 B15

< 5:18:43 PM: ok N35182 P1 B15

< 5:18:43 PM: ok N35183 P1 B15

< 5:18:43 PM: ok N35184 P1 B15

< 5:18:44 PM: ok N35185 P0 B15

< 5:18:44 PM: ok N35186 P1 B15

< 5:18:44 PM: ok N35187 P2 B15

< 5:18:44 PM: ok N35188 P1 B15

< 5:18:44 PM: ok N35189 P2 B15

< 5:18:44 PM: ok N35190 P0 B15

< 5:18:44 PM: ok N35191 P0 B15

< 5:18:44 PM: ok N35192 P0 B15

< 5:18:44 PM: ok N35193 P0 B15

< 5:18:44 PM: ok N35194 P0 B15

< 5:18:44 PM: ok N35195 P0 B15

< 5:18:44 PM: ok N35197 P1 B14 T:205.1 /205.0 B:50.6 /60.0 T0:205.1 /205.0 @:42 B@:127

< 5:18:44 PM: ok N35197 P0 B15

< 5:18:45 PM: ok N35198 P1 B15

< 5:18:45 PM: ok N35199 P1 B15

< 5:18:45 PM: ok N35200 P1 B15

< 5:18:45 PM: ok N35201 P2 B15

< 5:18:45 PM: ok N35202 P1 B15

< 5:18:45 PM: ok N35203 P2 B15

< 5:18:45 PM: ok N35204 P1 B15

< 5:18:45 PM: ok N35205 P2 B15

< 5:18:45 PM: ok N35206 P1 B15

< 5:18:45 PM: ok N35207 P2 B15

< 5:18:45 PM: ok N35208 P2 B15

< 5:18:45 PM: ok N35209 P2 B15

< 5:18:45 PM: ok N35210 P1 B15

< 5:18:45 PM: ok N35211 P2 B15

< 5:18:46 PM: ok N35212 P1 B15

< 5:18:46 PM: ok N35214 P2 B14 T:205.2 /205.0 B:50.9 /60.0 T0:205.2 /205.0 @:36 B@:127

< 5:18:46 PM: ok N35214 P2 B15

< 5:18:46 PM: ok N35215 P1 B15

< 5:18:46 PM: ok N35216 P2 B15

< 5:18:46 PM: ok N35217 P1 B15

< 5:18:46 PM: ok N35218 P2 B15

< 5:18:46 PM: ok N35219 P1 B15

< 5:18:46 PM: ok N35220 P2 B15

< 5:18:46 PM: ok N35221 P1 B15

< 5:18:46 PM: ok N35222 P2 B15

< 5:18:46 PM: ok N35223 P1 B15

< 5:18:46 PM: ok N35224 P2 B15

< 5:18:46 PM: ok N35225 P1 B15

< 5:18:46 PM: ok N35226 P2 B15

< 5:18:47 PM: ok N35227 P1 B15

< 5:18:47 PM: ok N35228 P1 B15 T:204.9 /205.0 B:51.3 /60.0 T0:204.9 /205.0 @:72 B@:83

< 5:18:47 PM: ok N35229 P2 B15

< 5:18:47 PM: ok N35230 P1 B15

< 5:18:47 PM: ok N35231 P2 B15

< 5:18:47 PM: ok N35232 P1 B15

< 5:18:47 PM: ok N35233 P1 B15

< 5:18:47 PM: ok N35234 P0 B15

< 5:18:47 PM: ok N35235 P1 B15

< 5:18:47 PM: ok N35236 P0 B15

< 5:18:47 PM: ok N35237 P0 B15

< 5:18:47 PM: ok N35238 P0 B15

< 5:18:47 PM: ok N35239 P1 B15

< 5:18:47 PM: ok N35240 P0 B15

< 5:18:47 PM: ok N35241 P1 B15

< 5:18:47 PM: ok N35242 P0 B15

< 5:18:47 PM: ok N35243 P2 B15

< 5:18:47 PM: ok N35244 P1 B15

< 5:18:48 PM: ok N35245 P3 B15

< 5:18:48 PM: ok N35247 P3 B14 T:205.4 /205.0 B:50.8 /60.0 T0:205.4 /205.0 @:23 B@:127

< 5:18:48 PM: ok N35247 P3 B15

< 5:18:48 PM: ok N35248 P3 B15

< 5:18:48 PM: ok N35249 P2 B15

< 5:18:48 PM: ok N35250 P0 B15

< 5:18:48 PM: ok N35251 P0 B15

< 5:18:48 PM: ok N35252 P0 B15

< 5:18:48 PM: ok N35253 P0 B15

< 5:18:48 PM: ok N35254 P1 B15

< 5:18:48 PM: ok N35255 P1 B15

< 5:18:48 PM: ok N35256 P1 B15

< 5:18:48 PM: ok N35257 P2 B15

< 5:18:48 PM: ok N35258 P1 B15

< 5:18:48 PM: ok N35259 P1 B15

< 5:18:48 PM: ok N35260 P1 B15

< 5:18:48 PM: ok N35261 P2 B15

< 5:18:48 PM: ok N35262 P1 B15

< 5:18:48 PM: ok N35263 P1 B15

< 5:18:48 PM: ok N35264 P1 B15

< 5:18:48 PM: ok N35265 P2 B15

< 5:18:49 PM: ok N35266 P1 B15

< 5:18:49 PM: ok N35267 P2 B15

< 5:18:49 PM: ok N35268 P1 B15

< 5:18:49 PM: ok N35269 P2 B15

< 5:18:49 PM: ok N35270 P1 B15

< 5:18:49 PM: ok N35271 P2 B15 T:205.3 /205.0 B:49.9 /60.0 T0:205.3 /205.0 @:29 B@:127

< 5:18:49 PM: ok N35272 P2 B15

< 5:18:49 PM: ok N35273 P1 B15

< 5:18:49 PM: ok N35274 P1 B15

< 5:18:49 PM: ok N35275 P1 B15

< 5:18:49 PM: ok N35276 P2 B15

< 5:18:49 PM: ok N35277 P1 B15

< 5:18:49 PM: ok N35278 P2 B15

< 5:18:49 PM: ok N35279 P1 B15

< 5:18:49 PM: ok N35280 P2 B15

< 5:18:49 PM: ok N35281 P1 B15

< 5:18:49 PM: ok N35282 P2 B15

< 5:18:49 PM: ok N35283 P0 B15

< 5:18:49 PM: ok N35284 P1 B15

< 5:18:49 PM: ok N35285 P0 B15

< 5:18:49 PM: ok N35286 P0 B15

< 5:18:49 PM: ok N35287 P0 B15

< 5:18:50 PM: ok N35288 P0 B15

< 5:18:50 PM: ok N35289 P0 B15

< 5:18:50 PM: ok N35291 P0 B14

< 5:18:50 PM: ok N35291 P0 B15

< 5:18:50 PM: ok N35292 P0 B15

< 5:18:50 PM: ok N35293 P0 B15 T:205.5 /205.0 B:50.7 /60.0 T0:205.5 /205.0 @:20 B@:127

< 5:18:50 PM: ok N35294 P0 B15

< 5:18:50 PM: ok N35295 P1 B15

< 5:18:50 PM: ok N35296 P0 B15

< 5:18:50 PM: ok N35297 P0 B15

< 5:18:50 PM: ok N35298 P0 B15

< 5:18:50 PM: ok N35299 P1 B15

< 5:18:50 PM: ok N35300 P0 B15

< 5:18:50 PM: ok N35301 P0 B15

< 5:18:50 PM: ok N35302 P0 B15

< 5:18:50 PM: ok N35303 P0 B15

< 5:18:50 PM: ok N35304 P0 B15

< 5:18:50 PM: ok N35305 P0 B15

< 5:18:50 PM: ok N35306 P1 B15

< 5:18:51 PM: ok N35308 P0 B14

< 5:18:51 PM: ok N35308 P0 B15

< 5:18:51 PM: ok N35309 P0 B15

< 5:18:51 PM: ok N35310 P0 B15

< 5:18:51 PM: ok N35311 P0 B15

< 5:18:51 PM: ok N35312 P0 B15

< 5:18:51 PM: ok N35313 P0 B15

< 5:18:51 PM: ok N35315 P1 B14 T:205.4 /205.0 B:50.9 /60.0 T0:205.4 /205.0 @:24 B@:127

< 5:18:51 PM: ok N35315 P0 B15

< 5:18:51 PM: ok N35316 P0 B15

< 5:18:51 PM: ok N35317 P0 B15

< 5:18:51 PM: ok N35318 P0 B15

< 5:18:51 PM: ok N35319 P0 B15

< 5:18:51 PM: ok N35320 P0 B15

< 5:18:51 PM: ok N35321 P1 B15

< 5:18:52 PM: ok N35322 P1 B15

< 5:18:52 PM: ok N35323 P1 B15

< 5:18:52 PM: ok N35324 P1 B15

< 5:18:52 PM: ok N35325 P2 B15

< 5:18:52 PM: ok N35326 P2 B15

< 5:18:52 PM: ok N35327 P1 B15

< 5:18:52 PM: ok N35328 P1 B15 T:205.3 /205.0 B:50.8 /60.0 T0:205.3 /205.0 @:35 B@:127

< 5:18:52 PM: ok N35329 P0 B15

< 5:18:52 PM: ok N35331 P0 B14

< 5:18:52 PM: ok N35332 P0 B14

< 5:18:52 PM: ok N35333 P0 B14

< 5:18:52 PM: ok N35333 P0 B15

< 5:18:52 PM: ok N35334 P1 B15

< 5:18:53 PM: ok N35335 P0 B15

< 5:18:53 PM: ok N35336 P0 B15

< 5:18:53 PM: ok N35337 P0 B15

< 5:18:53 PM: ok N35338 P0 B15

< 5:18:53 PM: ok N35339 P0 B15

< 5:18:53 PM: ok N35340 P1 B15

< 5:18:53 PM: ok N35341 P0 B15

< 5:18:53 PM: ok N35342 P0 B15

< 5:18:53 PM: ok N35343 P0 B15

< 5:18:53 PM: ok N35344 P0 B15

< 5:18:53 PM: ok N35345 P0 B15

< 5:18:53 PM: ok N35346 P0 B15

< 5:18:53 PM: ok N35347 P1 B15

< 5:18:53 PM: ok N35349 P0 B14

< 5:18:53 PM: ok N35350 P0 B14

< 5:18:53 PM: ok N35350 P0 B15 T:205.2 /205.0 B:50.7 /60.0 T0:205.2 /205.0 @:47 B@:127

< 5:18:53 PM: ok N35351 P1 B15

< 5:18:53 PM: ok N35352 P3 B15

< 5:18:53 PM: ok N35353 P0 B15

< 5:18:53 PM: ok N35354 P0 B15

< 5:18:54 PM: ok N35355 P0 B15

< 5:18:54 PM: ok N35356 P0 B15

< 5:18:54 PM: ok N35357 P0 B15

< 5:18:54 PM: ok N35358 P0 B15

< 5:18:54 PM: ok N35359 P0 B15

< 5:18:54 PM: ok N35360 P1 B15

< 5:18:54 PM: ok N35361 P0 B15

< 5:18:54 PM: ok N35362 P1 B15

< 5:18:54 PM: ok N35364 P2 B14 T:204.6 /205.0 B:50.5 /60.0 T0:204.6 /205.0 @:101 B@:127

< 5:18:54 PM: ok N35364 P0 B15

< 5:18:54 PM: ok N35365 P1 B15

< 5:18:54 PM: ok N35366 P1 B15

< 5:18:55 PM: ok N35367 P1 B15

< 5:18:55 PM: ok N35368 P0 B15

< 5:18:55 PM: ok N35370 P0 B14

< 5:18:55 PM: ok N35371 P0 B14

< 5:18:55 PM: ok N35372 P0 B14

< 5:18:55 PM: ok N35372 P0 B15

< 5:18:55 PM: ok N35373 P1 B15

< 5:18:55 PM: ok N35374 P1 B15 T:202.9 /205.0 B:51.1 /60.0 T0:202.9 /205.0 @:127 B@:127

< 5:18:55 PM: ok N35375 P0 B15

< 5:18:55 PM: ok N35376 P0 B15

< 5:18:55 PM: ok N35377 P0 B15

< 5:18:55 PM: ok N35378 P0 B15

< 5:18:55 PM: ok N35379 P0 B15

< 5:18:55 PM: ok N35380 P1 B15

< 5:18:55 PM: ok N35382 P0 B14

< 5:18:55 PM: ok N35382 P0 B15

< 5:18:55 PM: ok N35383 P0 B15

< 5:18:55 PM: ok N35384 P0 B15

< 5:18:55 PM: ok N35385 P0 B15

< 5:18:56 PM: ok N35386 P0 B15

< 5:18:56 PM: ok N35387 P0 B15

< 5:18:56 PM: ok N35388 P1 B15

< 5:18:56 PM: ok N35390 P0 B14

< 5:18:56 PM: ok N35391 P0 B14

< 5:18:56 PM: ok N35392 P0 B14

< 5:18:56 PM: ok N35393 P0 B14

< 5:18:56 PM: ok N35393 P0 B15

< 5:18:56 PM: ok N35394 P0 B15

< 5:18:56 PM: ok N35395 P0 B15

< 5:18:56 PM: ok N35396 P0 B15

< 5:18:56 PM: ok N35397 P0 B15

< 5:18:56 PM: ok N35398 P0 B15

< 5:18:56 PM: ok N35399 P0 B15

< 5:18:56 PM: ok N35400 P0 B15

< 5:18:56 PM: ok N35401 P0 B15

< 5:18:56 PM: ok N35402 P0 B15

< 5:18:56 PM: ok N35403 P0 B15

< 5:18:56 PM: ok N35404 P0 B15

< 5:18:56 PM: ok N35405 P0 B15

< 5:18:56 PM: ok N35406 P0 B15

< 5:18:56 PM: ok N35407 P0 B15

< 5:18:56 PM: ok N35408 P0 B15

< 5:18:56 PM: ok N35409 P0 B15

< 5:18:56 PM: ok N35410 P0 B15

< 5:18:56 PM: ok N35412 P0 B14

< 5:18:56 PM: ok N35412 P0 B15

< 5:18:56 PM: ok N35413 P0 B15

< 5:18:56 PM: ok N35414 P0 B15

< 5:18:56 PM: ok N35415 P0 B15 T:205.3 /205.0 B:51.2 /60.0 T0:205.3 /205.0 @:25 B@:124

< 5:18:56 PM: ok N35416 P0 B15

< 5:18:56 PM: ok N35417 P0 B15

< 5:18:56 PM: ok N35418 P0 B15

< 5:18:56 PM: ok N35419 P1 B15

< 5:18:56 PM: ok N35420 P0 B15

< 5:18:56 PM: ok N35421 P0 B15

< 5:18:57 PM: ok N35422 P0 B15

< 5:18:57 PM: ok N35423 P0 B15

< 5:18:57 PM: ok N35424 P0 B15

< 5:18:57 PM: ok N35425 P0 B15

< 5:18:57 PM: ok N35426 P0 B15

< 5:18:57 PM: ok N35427 P1 B15

< 5:18:57 PM: ok N35428 P0 B15

< 5:18:57 PM: ok N35429 P1 B15

< 5:18:57 PM: ok N35431 P2 B14 T:205.1 /205.0 B:50.8 /60.0 T0:205.1 /205.0 @:52 B@:127

< 5:18:58 PM: ok N35431 P0 B15

< 5:18:58 PM: ok N35432 P1 B15

< 5:18:58 PM: ok N35434 P1 B14

< 5:18:58 PM: ok N35435 P0 B14

< 5:18:58 PM: ok N35435 P0 B15

< 5:18:58 PM: ok N35436 P0 B15

< 5:18:58 PM: ok N35437 P0 B15

< 5:18:58 PM: ok N35438 P1 B15

< 5:18:58 PM: ok N35439 P1 B15

< 5:18:58 PM: ok N35440 P1 B15

< 5:18:58 PM: ok N35441 P0 B15

< 5:18:58 PM: ok N35442 P0 B15

< 5:18:58 PM: ok N35443 P0 B15

< 5:18:58 PM: ok N35444 P0 B15

< 5:18:58 PM: ok N35445 P0 B15

< 5:18:58 PM: ok N35446 P0 B15

< 5:18:58 PM: ok N35447 P0 B15

< 5:18:58 PM: ok N35448 P0 B15

< 5:18:58 PM: ok N35449 P0 B15

< 5:18:58 PM: ok N35450 P0 B15

< 5:18:58 PM: ok N35451 P0 B15

< 5:18:58 PM: ok N35452 P0 B15

< 5:18:58 PM: ok N35453 P0 B15

< 5:18:58 PM: ok N35455 P0 B14

< 5:18:58 PM: ok N35455 P0 B15

< 5:18:58 PM: ok N35456 P0 B15

< 5:18:58 PM: ok N35457 P0 B15

< 5:18:58 PM: ok N35458 P1 B15

< 5:18:58 PM: ok N35459 P0 B15

< 5:18:58 PM: ok N35461 P0 B14

< 5:18:58 PM: ok N35462 P0 B14

< 5:18:58 PM: ok N35463 P0 B14

< 5:18:58 PM: ok N35463 P0 B15 T:205.3 /205.0 B:51.1 /60.0 T0:205.3 /205.0 @:25 B@:127

5:19:38 PM: Communication timeout - reset send buffer block

5:20:19 PM: Communication timeout - reset send buffer block

5:22:10 PM: Communication timeout - reset send buffer block

5:22:50 PM: Communication timeout - reset send buffer block

5:23:30 PM: Communication timeout - reset send buffer block

< 5:23:42 PM: ok

5:24:22 PM: Communication timeout - reset send buffer block

< 5:24:28 PM: ok

5:25:09 PM: Communication timeout - reset send buffer block

5:25:49 PM: Communication timeout - reset send buffer block

5:26:29 PM: Communication timeout - reset send buffer block

5:27:09 PM: Communication timeout - reset send buffer block

5:27:49 PM: Communication timeout - reset send buffer block

5:28:30 PM: Communication timeout - reset send buffer block

5:29:10 PM: Communication timeout - reset send buffer block

5:29:50 PM: Communication timeout - reset send buffer block

5:30:30 PM: Communication timeout - reset send buffer block

5:31:10 PM: Communication timeout - reset send buffer block

5:31:50 PM: Communication timeout - reset send buffer block

5:32:32 PM: Communication timeout - reset send buffer block

5:33:13 PM: Communication timeout - reset send buffer block

↧

Printer suddenly stops mid print

December 31, 2019, 3:43 pm

≫ Next: "repetier communication timeout reset send buffer block"

≪ Previous: Halfway through Printing I get a Communications error

Hi, I'm trying to print to a Tronxy X3A (Marlin v. 1.0) with Repetier-Host 2.1.3 and the print starts of ok, but then suddenly stops with an error message about communications. I've gone into the windows settings and changed the buffer to the lowest settings, but it doesn't help. I'm using the slic3r software. It's pretty random where it will stop. Anyone have any ideas about why it suddenly stops? It prints fine off a microsd card. It's very infuriating.

Thanks!

↧

"repetier communication timeout reset send buffer block"

April 19, 2019, 10:51 am

≫ Next: UI design Control / Temperatur

≪ Previous: Printer suddenly stops mid print

windows 10
repetier 2.1.3
printrbot simple pro (lastest firmware)
usb

just started giving me this error last week.
was only doing it after @pause.. i removed the next line that changed the temp and that fixed it for one print
printed sucessfuly last nite. turned off printer, left repetier open, changed nothing, errored out again this morning.

rebooted everybody and it seemed to work on a 1/3 scale of stl.. ..YET... half way thru a full scale ... errored out again!!!

↧

UI design Control / Temperatur

December 31, 2019, 4:24 pm

≫ Next: Error in filament change script?

≪ Previous: "repetier communication timeout reset send buffer block"

Bitte ordnet doch beim nächsten Update die Temperatursteuerung untereinander an, so dass der Graph der jeweiligen Heizelemente daneben ist. Das ist nicht nur optisch schöner, es macht auch mehr Sinn, wenn man den Temperaturverlauf neben der jeweiligen Steuerung sieht. Und bei meinem kleinen Monitor muss ich dann nicht scrollen, um beide Heizelemente angezeigt zu kriegen und gleichzeitig den Not-Aus-Button im Blickfeld zu haben.

↧

Error in filament change script?

December 21, 2019, 7:16 pm

≫ Next: Speed Fan M106 ..... S ???????

≪ Previous: UI design Control / Temperatur

I just wanted to change the filament but instead of stopping, the printer kept moving while it turned off the hotend heating. I just realised it when it had continued about two layers. I assume that this is not the normal behaviour, but maybe a bug?

↧

Speed Fan M106 ..... S ???????

May 4, 2018, 2:03 pm

≫ Next: Unable to connect to Duet2 Wifi

≪ Previous: Error in filament change script?

why does the M106 S50 command send me the maximum fan speed instead with the old firmware corresponding to 20%?

what is the max value and 50%?

↧

Unable to connect to Duet2 Wifi

December 9, 2019, 6:20 am

≫ Next: Waweshare 3,5" TFT screen installing.

≪ Previous: Speed Fan M106 ..... S ???????

Hallo,

I am unable to connect Repetier server to my 3d printer running with a Duet2 Wifi bord.
Connection form the Internet browser from the same computer to the printer works fine.
Duet2 has latest Firmware running in Reprap mode.
Do I Need to specify a TCP/IP adres and a port? If Yes, what Port? Tried 23 but no success.
Any tips?

Spiky

↧

Waweshare 3,5" TFT screen installing.

January 1, 2020, 3:55 am

≫ Next: Connect to PRUSA Mini

≪ Previous: Unable to connect to Duet2 Wifi

Hello Repetier server family,

I have come up with a new curiosity in the field of 3D printer and you will have a few soum.

I bought Raspbery pi 3 B + and Waweshare 3.5 "TFT touchscreen.

While making the steps in the forum https://forum.repetier.com/discussion/5404/installation-of-waveshare-3-5-non-hdmi-lcd-display-touchscreen-on-raspberry-pi;

When I write "cd LCD-show /" in step 3;

I am getting a "No such file directory" error

What ways should I try to solve the problem?

Can you help me?

↧

Connect to PRUSA Mini

December 22, 2019, 2:00 am

≫ Next: Serial com error:System.IO.Ports.SerialErrorReceivedEventArgs

≪ Previous: Waweshare 3,5" TFT screen installing.

Hi guys,

can you confirm that Repetier Server can connect to the PRUSA Mini, as it is running Marlin 2.0, or is thsi unclear?

Thx,

Michael

↧

Serial com error:System.IO.Ports.SerialErrorReceivedEventArgs

January 1, 2020, 5:19 pm

≫ Next: Cnc laser

≪ Previous: Connect to PRUSA Mini

ok my research on this tells me it comes from windows... umm great thats about as helpful as telling me someones is from China so i should be easily able to locate them! There are about 500 variables involved there im just trying to find a way to limit those to the point i can figure out whats going on.

The error seems random and doesnt always end the print i just cant figure out what the cause is.

So really anyone know what the common causes are here ?
1. USB Cable bad
2. Comm port Driver
3. Software trying to access that com port
etc etc ?

↧

Cnc laser

December 27, 2019, 5:48 pm

≫ Next: firmare ignoring z movement in certain gcode files?

≪ Previous: Serial com error:System.IO.Ports.SerialErrorReceivedEventArgs

I use Repetier server to control 3 printers. Can I use it to control my cnc laser? It user GRBL Firmware

↧

firmare ignoring z movement in certain gcode files?

October 13, 2019, 6:20 am

≫ Next: what is the value multiplied next to each line ???

≪ Previous: Cnc laser

Hello mates,

I run repetier-firmware on a CNC router, and I found a very strange behavior:

I have 2 gcode files with should do the same (drill a hole with 6mm diameter and 10mm depth).

Both gcodes are created with the same tool (estlcam) but in "different ways".

The problem that I encountered:
The file "Kreistasche.gcode" doesn't do any "Z" movement, the file "ausschnitt.gcode" works fine.
Can anyone help me?

Thx!

https://www.dropbox.com/s/u1qekujuqqo4ad3/ausschnitt.gcode?dl=0&fbclid=IwAR1k3yc4S7fIMXD7s3SYFugqmwA4J3VVEvRmHLbGXSsftdasp9RKyvcr_hg

https://www.dropbox.com/s/45ih2taouvd8h56/Kreistasche.gcode?dl=0&fbclid=IwAR3Pts-9mtTvqNFQvzTa3z_qSIUZKixPtGWvVQhFeceixhkSvwxGxZypFy0

↧

what is the value multiplied next to each line ???

May 3, 2018, 3:11 pm

≫ Next: No access to the "eeprom firmware configuration" menu

≪ Previous: firmare ignoring z movement in certain gcode files?

what is the value multiplied next to each line ???

G1 X39.239 Y76 E2456.267 * 69; * 69

G0 X39.399 Y76 * 53; * 53

G0 X44 Y75.427 * 63; * 63

what generates this percentage since the listing does not appear?

↧

No access to the "eeprom firmware configuration" menu

January 2, 2020, 11:07 am

≫ Next: bsod from ch340 drivers when using rep host/server

≪ Previous: what is the value multiplied next to each line ???

I was worried about returning data from my Anet A8M printer and I think that by handling my printer, I reset the eeprom.

In any case I no longer have access to the "eeprom firmware configuration" menu of Repetier host vV2.1.6.

I had imported this file and since I no longer have access to it, I can no longer export it again.

I can connect to the Anet printer, but I have no feedback.

I can still print using the SD card.

What do you recommend that I do??? Thank you for explaining to me what I did not understand and where my concern comes from.

cordially

↧

bsod from ch340 drivers when using rep host/server

December 30, 2017, 11:43 pm

≫ Next: Problem upgrade TronXY XY-100 to hotbed

≪ Previous: No access to the "eeprom firmware configuration" menu

Has anyone else ever had windows BSOD crashes from the ch340 (64bit) drivers on Windows 10? I realize this doesn't necessarily point at repetier, but I've been doing a lot of Arduino work for a few months that of course use the drivers and didn't have a single crash of this nature until I started using Repetier.

Using Repeteir 0.86.2 pro trial at the moment. It's quite random, often times coming at 15 to 30 mins into a print, although I just got a few crashes just playing around with the manual controls in rep host. I'm mostly just looking for what I should be looking at - obviously the driver is final and I can't find anybody with similar problems, but it's literally the only way to reliably bsod my machine which I use for gaming and music production with no other hint of instability. Any tips on how to troubleshoot this by getting verbose logging from repetier server or other suggestions would be appreciated.

↧

Problem upgrade TronXY XY-100 to hotbed

December 19, 2018, 4:51 am

≫ Next: Connecting to another Server via TCP/IP

≪ Previous: bsod from ch340 drivers when using rep host/server

Hello everyone,

I am from Romania and I'm new here and the new owner of a 3d printer. I recently purchased a Tronxy xy-100 printer that works normally. I have problems with larger diameter (100mm) worck that did not print correctly. So I went to buy a 120 / 120mm hotpad. After making connections, the temperature indicates 0 C and can not be set either from the printer or from the PC software. Problems with the printer motherboard? Problems setting jumpers? Where is the problem?
Thank you in advance for clarification on how to resolve the situation.
Regards,
Radu

↧

Connecting to another Server via TCP/IP

January 3, 2020, 9:56 am

≫ Next: Repetier Server LCD touch aktivation

≪ Previous: Problem upgrade TronXY XY-100 to hotbed

I have searched the forums and I can't find the issue that I am having. So if it is elsewhere, I apologize. I have two printers and 2 Raspberry Pi's. I originally installed both printers to 1 pi via USB cable and it worked perfectly. I then purchased another pi so I could move one of my printers to a different room and just connect via TCP/IP with ethernet (not WiFi), Copied the Repetier-Server image to the new pi, assigned a static IP and it was working under its own IP Address. So I logged into the first instance of Server and added the printer via TCP/IP. I got connected via TCP/IP, then it would drop the connection, then it kept bouncing to connected to not connected. Anyone have a solution to this issue? Is it something I am not doing correctly.

Any help would be appreciated.

↧

Repetier Server LCD touch aktivation

January 4, 2020, 1:14 am

≫ Next: Installation of Waveshare 3.5" (non-HDMI) LCD display / touchscreen on Raspberry Pi

≪ Previous: Connecting to another Server via TCP/IP

Hello guys,
I am very new to repetier and I managed to get repetierserver running on my Respberry Pi 4. I can control the printer on my mac and everything is fine so far. I installed an 5" LCD (kuman 5" inch Resistive 800x480 HDMI TFT). The display is working and I was able to install the touch driver for the display. After installing repetierserver on the Pi, the touch function does not work anymore. I thought I could just install the touch drivers again.
But: How do I open the terminal in repetierserver to install the LCD touchscreen drivers?

Best wishes
Phill

↧

Installation of Waveshare 3.5" (non-HDMI) LCD display / touchscreen on Raspberry Pi

June 10, 2018, 9:01 am

≫ Next: CR10s pro v2 connected but no control

≪ Previous: Repetier Server LCD touch aktivation

Hereby i want to share how to setup 3.5" LCD display (non-HDMI) based on latest Repetier Server Image (v8) for the Raspberry Pi.

It took me several hours to get it working and hopefully it's also useful for others because this kind of LCD screen are very cheap and widely used.

LCD display (320x480) i am using:

https://www.waveshare.com/product/mini-pc/raspberry-pi/displays/3.5inch-rpi-lcd-b.htm

Steps:

1. Copy Repetier Server Image to SD card (e.g. Win32DiskImager Tool)

2. After booting up the installed Repetier Server on RPI you need to expand the filesystem in order to use the full capactiy from SD card:

CODE:

sudo raspi-config

Select: 7 Advanced Options => A1 Expand Filesystem

3. Install Waveshare 3.5" driver display (you need to find and select the correct one for your LCD screen !!!).

CODE:

wget http://www.waveshare.com/w/upload/7/74/LCD-show-170309.tar.gz
tar xvf /LCD-show-170309.tar.gz

cd LCD-show/
chmod +x LCD35B-show
./LCD35B-show
sudo shutdown now

4. Modify screen configuration file (Before modification it's good to make backup from the file!)

CODE:

sudo vi /usr/share/X11/xorg.conf.d/99-fbturbo.conf

sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf

File content (99-fbturbo.conf) should look like this:

Section "Device"

Identifier "touchscreen"

Driver "fbdev"

Option "fbdev" "/dev/fb1"

EndSection

Afterwards you get rewarded with pretty nice touchscreen control.

The touchscreen control from Repetier Server is really fabulous also on small screens.

This is so much betten than TouchUI on the Octoprint.

;-)

Image: https://forum.repetier.com/uploads/editor/g7/qsbqkr4w0j5y.jpg

Image: https://forum.repetier.com/uploads/editor/ex/adj9kxarexu9.jpg

↧

CR10s pro v2 connected but no control

January 4, 2020, 6:21 am

≫ Next: Is it possible to use 3 Z steppers and also control them to do bed leveling ?

≪ Previous: Installation of Waveshare 3.5" (non-HDMI) LCD display / touchscreen on Raspberry Pi

We just got the CR10s pro V2 and it says connected but temp say zero and we cannot control the printer. If we change the comm port settings it either makes no difference or it disconnects. This printer works perfect on Octoprint with the same connection settings. Anything I can try?

Our CR10s we got early 2019 works great and we tried matching the settings. We also verified we have the latest firmware.

This is the first printer out of 7 that we’ve had issues with. 2 have Repetier firmware, 3 have Marlin and the last two are the CR10s (Marlin?) firmware.

↧