Welcome to the SeeMeCNC Community

Hi all,

I've been running the the V.0.83 firmware for some time on a Rostock MAX, with an E3D hot-end, without any trouble, but over the past couple days, the machine's been stopping, 60-90% of the way through the job. This has happened twice when streaming the job via USB (Repetier Host V0.95C ), and once running from the SD card (a good-quality Sandisk Ultra card, not the stock one...) It's happened with two different STLs, one of which I printed a couple times before (same G-code, even), so I'm 99% sure that it's not a slicer issue. The other STL has failed both times I've tried to print it (once USB, once SD card); the USB job stopped at ~95%, and the SD card job at ~83%. When running off the SD card, I was able to home the head after it stopped, but couldn't do a "Continue Print"; nevertheless, the printer remained responsive, in the sense that the LCD menu navigation still worked normally, the hot-end and bed temperatures were properly controlled, etc.

One job takes 1.2 hrs, and the other (the one that I've never gotten to work) is estimated at 3.25 hours (137 layers, I think?)... Longer, but not a big job, by any means.

The board has a dedicated cooling fan, and I've been running with the case open, so I don't think it's an overheating issue. I will admit I don't have any ferrite clamps on the ribbon cables... Up until these last few prints, I had never had an issue, though the jobs were usually somewhat shorter (1-2 hrs), but for what it's worth, the ribbon cables are routed well away from the steppers, power cables, etc.

Now, I do suspect that I've got the Rambo 1.2 static issue going on (I can get it to connect via USB, but only by cycling the power, after clicking "Connect", and attempts to upload new firmware lead to the "timeout" error on the Arduino IDE)... The power-cycle requirement started quite suddenly, about three weeks ago... Since then, I have run a number of jobs successfully, but maybe that was just dumb luck? Has anyone else experienced a correlation between a 'static kill' and random job stops?

Any suggestions would be greatly appreciated!

-Luke

There is a known issue with the 0.83 version of repetier firmware, where it just stops.
There are several threads discussing this, it's not clear why it happens, I've personally run 10hr prints on 0.83 without issue and had a 1 Hr print fail, doing things like changing the layer height slightly seem to sometimes fix it on a particular print.

The simple solution is to upgrade to 0.9

Ah, that's excellent, I hadn't come across anything that definitively stated whether the 0.9 firmware solved the problem.

I have a couple jobs I need to slog through before I can get some down-time to swap the RAMBO, recal, etc., so I'll try nudging the layer thickness. Worst-case, I'll just splice parts, if the print stops.

Thanks!

-Luke

Fast forward 1 year (5/21/15) - we're on Firmware v. 1.6.3 and this problem just happened to me too. I now see there is an even newer version available (1.6.4) - I'll try it and hope for the best - will update if problem reoccurs.

Frustrating.

Repetier is still on .92.3, where are you getting this 1.6.4 number?

1.6.4 is the current release of the Arduino IDE. While it's possible for the version of IDE on which the firmware is compiled to affect the behavior of the compiled firmware, I wouldn't expect it on a third-tier version change.

The chances of a compiler bug causing this issue is vanishingly small. (So small IMO, that's it's not even worth considering.)

g.