80.1 v4 PRints FAILING mid print.

RhinoRap

Another problem with V4 pi build NOT modified.
see log below - job sent to server via host and printed from front end.
Job STOPS mid-print - no erros, no messges - just....stops..see the end of the log file.
Temps are not plotted in the printer page on front end - but bed temp shows at top of title bar
Firmware is repetier 092.9

I'd appreciate some help from the support team seeing as i've paid my 60 euros for the "PRO" license.

> 23:46:43.846: T:220.56 /0 B:67.70 /0 B@:0 @:0
> 23:46:43.848: ok 12
> 23:46:43.856: ok 13
> 23:46:43.862: T:219.57 /0 B:67.45 /0 B@:0 @:0
> 23:46:43.862: ok 14
removed 30 lines to fit in this body
> 23:51:55.387: ok 328
> 23:51:55.391: T:67.10 /0 B:38.44 /0 B@:0 @:0
< 23:51:56.384: N329 M105
> 23:51:56.391: ok 329
> 23:51:56.392: T:66.81 /0 B:38.35 /0 B@:0 @:0

Repetier

Please show the part before where the interesting thing happens. I see line number 12 so it is likely that something like a printer reset happened which caused the lines to restart at 1. A printer reset causes the server to stop printing of course.

RhinoRap

I understand that - Nothing noteable happens. it's happily printing layers - then stops, drives the head to the right hand side and stops.
I no longer have the log as i've rebuilt the image for the 3rd time - and currently setting up a windows based build.

Repetier

Well if it happens again check for the code at end of print log and beginning of connected.log. Maybe even logs/server.log where you see if a connection was recreated. That might help finding the reason.

RhinoRap

hi,
i've had NO luck at all with Pi2 reliability.
this is the last chunk of code from the print log -as you can see - it just stops. server is still running - carriage is driven to the far extent of travel in both axis, and heaters are turned off..... so far i've wasted a lot of filament.....

< 12:49:31.529: N83225 M105
< 12:49:31.529: N83226 G1 X92.957 Y118.299 E9.02885
> 12:49:31.578: ok 17684
< 12:49:31.579: N83227 G1 X93.574 Y117.682 E9.04216
> 12:49:31.652: ok 17685
< 12:49:31.653: N83228 G1 X93.436 Y117.169 E9.05027
> 12:49:31.701: ok 17686
< 12:49:31.702: N83229 G1 X94.053 Y116.553 E9.06359
> 12:49:31.775: ok 17687
< 12:49:31.776: N83230 G1 X94.566 Y116.690 E9.07170
> 12:49:31.824: ok 17688
< 12:49:31.824: N83231 G1 X95.183 Y116.073 E9.08501
> 12:49:31.898: ok 17689
> 12:49:31.901: T:255.24 /255 B:103.92 /105 B@:255 @:152
> 12:49:31.914: ok 17690
< 12:49:31.914: N83232 G1 X95.045 Y115.560 E9.09312
> 12:49:31.948: ok 17691
< 12:49:31.948: N83233 G1 X95.662 Y114.943 E9.10644
> 12:49:32.025: ok 17692
< 12:49:32.025: N83234 G1 X96.175 Y115.081 E9.11455
> 12:49:32.070: ok 17693
< 12:49:32.070: N83235 G1 X96.792 Y114.464 E9.12787

Repetier

So fat it looks fine. What is happening after that? If print stops logging continues in connected.log. We need the comlete part to see the truth, e.g. if printer just reset.

You can print with dry run enabled so you do not waste filament. If it is printer related it might not happen then. Printer realted problems are often also power usage related.