Prints failing

Hi all, I've recently purchased a Prusa i3 and have had some successful prints, but I seem to have a recurring problem which is causing a number of my prints to fail.

When doing larger prints everything starts off great but then the log screen fills with errors and the print slows to a crawl and just sort of blobs filament around the print.



Printer, Prusa i3
Firmware, Repetier_0.91
Software, Repetier V1.5.0
Connection type, Serial Connection, 115200 Baud

Any help on this matter would be greatly appreciated.

Thanks

Ok a bit of an update, attempted to print the same model twice using different settings and they both failed at what I would say is the exact same layer. See Attached file.

Now this is either coincidence or could the problem lie within the gcode? Both times I've used Cura to slice the model, this is not the only model I've had fail but I would say all have been sliced with Cura.

If you think the problem is in the Gcode, can you post the Gcode? And a log showing the *first* error reported?

When the error occurred I reviewed the log and there was nothing in there that pointed to the error it just went from 'printing layer X of Y' to 'warning, missed line detected'

I'll have a look at the log file and see what layer the warning was first generated and compare that to the layer in the gcode.

Edited 1 time(s). Last edit at 07/08/2015 05:06PM by ChavasRegal.

Did you try to print the same gcode from SD-Card?
Maybe the print fails, because your PC is left alone for xx minutes and looses connection?
115200Baud is also known to be error prone with arduino 16MHz chips. Can you change it to 250000Baud? ( both firmware and repetier )
-Olaf

Unfortunately I haven't yet been able to get the SD Card to work, I receive the 'SD init fail' error.
Still a bit of a noob when it comes to the printer, i'll look in to changing the baud.

Video of the printer after the errors,

[youtu.be]

Edited 1 time(s). Last edit at 07/09/2015 02:00AM by ChavasRegal.

ok I attempted a print today to see the outcome and everything was going ok until

> 19:00:29.577 : ok 65533
< 19:00:29.577 : N65539 G1 X128.053 Y75.587 E5922.781 *73
> 19:00:29.577 : ok 65534
< 19:00:29.577 : N65540 G1 X128.729 Y76.541 E5922.819 *74
> 19:00:29.592 : ok 65535
< 19:00:29.592 : N65541 G1 X129.483 Y77.676 E5922.865 *68
> 19:00:29.592 : ok 0
< 19:00:29.592 : Warning: Missed line detected - correcting buffer usage.
< 19:00:29.592 : N65542 G1 X130.122 Y78.713 E5922.905 *75
> 19:00:29.608 : ok 1
< 19:00:29.608 : Warning: Missed line detected - correcting buffer usage.
< 19:00:29.608 : N65543 G1 X130.586 Y79.523 E5922.937 *65
> 19:00:29.624 : ok 2
< 19:00:29.624 : Warning: Missed line detected - correcting buffer usage.
< 19:00:29.624 : N65544 G1 X131.309 Y80.86 E5922.987 *113
> 19:00:29.639 : ok 3

and this proceeded to print fine until

> 19:42:36.513 : ok 65533
< 19:42:36.513 : Warning: Missed line detected - correcting buffer usage.
< 19:42:36.513 : N131075 G1 X102.477 Y103.575 E9010.744 *78
> 19:42:36.544 : ok 65534
< 19:42:36.544 : Warning: Missed line detected - correcting buffer usage.
< 19:42:36.544 : N131076 G1 X102.131 Y104.001 E9010.762 *79
> 19:42:36.560 : ok 65535
< 19:42:36.560 : Warning: Missed line detected - correcting buffer usage.
< 19:42:36.560 : N131077 G1 X101.425 Y104.71 E9010.795 *114
> 19:42:36.591 : ok 0
> 19:42:36.606 : ok 1
> 19:42:36.638 : ok 2
> 19:42:36.653 : ok 3
> 19:42:36.685 : ok 4
> 19:42:36.716 : ok 5
< 19:42:37.388 : N131078 M105 *59
> 19:42:37.388 : ok 6
> 19:42:37.388 : T:243.46 /245 B:115.12 /115 B@:0 @:230
> 19:42:38.388 : wait
> 19:42:39.388 : wait
> 19:42:40.388 : wait
< 19:42:40.388 : Warning: Seems like we missed a ok, got a wait - continue sending.
< 19:42:40.388 : N131079 M117 ETE 30m 22s *80
< 19:42:40.388 : N131080 G1 X100.969 Y105.084 E9010.815 *66
< 19:42:40.388 : N131081 G1 X100.536 Y105.389 E9010.833 *79
< 19:42:40.388 : N131082 G1 X100.09 Y105.661 E9010.85 *67
< 19:42:40.388 : N131083 G1 X99.612 Y105.908 E9010.868 *116
< 19:42:40.388 : N131084 G1 X99.141 Y106.113 E9010.885 *112
> 19:42:40.403 : ok 7
> 19:42:40.435 : ok 8
> 19:42:40.435 : ok 9
> 19:42:40.435 : ok 10
> 19:42:40.435 : ok 11
> 19:42:40.435 : ok 12
< 19:42:40.450 : N131085 M105 *57
> 19:42:40.450 : ok 13
> 19:42:40.450 : T:243.46 /245 B:115.26 /115 B@:0 @:230
> 19:42:41.450 : wait
> 19:42:42.450 : wait
> 19:42:43.450 : wait
< 19:42:43.450 : Warning: Seems like we missed a ok, got a wait - continue sending.
< 19:42:43.450 : N131086 M117 ETE 30m 22s *80
< 19:42:43.450 : N131087 G1 X98.509 Y106.323 E9010.907 *112
< 19:42:43.450 : N131088 G1 X97.995 Y106.466 E9010.925 *127
< 19:42:43.450 : N131089 G1 X97.23 Y106.599 E9010.951 *72
< 19:42:43.450 : N131090 G1 X96.586 Y106.655 E9010.973 *120
< 19:42:43.450 : N131091 G1 X96.445 Y106.658 E9010.977 *126
> 19:42:43.466 : ok 14
> 19:42:43.497 : ok 15
> 19:42:43.497 : ok 16
> 19:42:43.497 : ok 17
> 19:42:43.497 : ok 18
> 19:42:43.497 : ok 19

one thing I have noticed is the OK number , prints fine until OK 65535, resets to OK 0 and gives buffer message, raises OK to 65535, resets to OK 0 and gives 'missed a ok' message and print fails.

Edited 1 time(s). Last edit at 07/09/2015 03:09PM by ChavasRegal.

65535 = 0xFFFF... I'm not surprised that it wraps around from there to 0.

It looks like your firmware (Repetier_0.91) has a 16-bit counter for 'ok' messages, whereas your 'software' (Repetier V1.5.0) has a 32-bit counter.

I'm not familiar with Repetier, but maybe you can turn off the checking of these ok messages? Or maybe your software needs to be upgraded to something that handles this situation? (I note that v1.5.2 is available for Windows). Or downgraded to something which doesn't cause it? Or your firmware upgraded to use with a 32-bit counter?

In any case, the problem is between the two pieces of Repetier software, so I'd check [www.repetier.com]

Frank

I've Just read on the Repeater forums that this was a problem with v1.5.0 and is now fixed in the v1.5.2 release, i'll do a big print later and test it out.

Same problem here last three days with 1.5.0 version , three prints lost after 2 hours of printing , now i installed 1.5.2 version and will try it again this evening

Now with 1.5.2 it is working well ... 5hours to finish my big print

Edited 2 time(s). Last edit at 07/10/2015 02:19PM by krtek2k.

Same here Krtek2k, 1.5.2 fixed all my issues finally got some decent prints done.

Hello,

I got the same Problem with one of my Printers usung Reptier Server on a Raspi.
If I connect my Printer over USB directly i got no Errors.

But after connecting my Printer in RepetierHost using the Server Connection it Comes up with the error "missed line detected: correcting buffer usage".
I did not check if I could print anything.

BTW: using Repetier Server 0.60.4 and Repetier Host 1.5.6 // two Printers are running without any Problems connected to the Raspi Server. one still make Troubles.

any advice would be helpful

thanks
Martin

I'm having a similar problem on my printer but it is also coupled with random errors in reading the temperature from the machine. It will usually say the correct temperature but it will randomly say my extruder is 19c or that its 17833c or that my bed temp is 6633c like it just did, or 0.
My machine is a Da Vinci 3D that is running a custom version of repeiter. It has been losing steps horribly lately and I'm not really sure what the problem is anymore given this recent development. I have a feeling the control board might be completely shot, but I figured I would ask anyway. I'm running Repeiter host V1.5.6. My printer has been failing prints constantly recently, it just failed another(lost about half an inch of steps.) I'm at a loss at this point and don't know if this could be because the printer isn't getting commands correctly or if the printer is damaged and screwing up. Just hoping someone has some advice. Thanks in advance.