On 15 Mar 2013 , at 6:04 PM, Douglas Meyer wrote:
> Hi, everybody
>
> I have a problem which has taken my Replicator 2 completely down. I just
> posted the following to Makerbot support, but having read several posts on
> this forum which lead me to believe that I can't really expect
> comprehensive support, I am also deliberately 'cross posting' to this
> forum. (I hope that that practice does not get me completely banned from
> this one). I believe that the following snippet, all of which was sent to
> Makerbot, fully describes my predicament. *Any and all responses are
> welcome!*
>
> *snippet*
> I have been happily printing since I received my Replicator 2 about two
> months ago. The Lifetime Total reads exactly 100 hours. I had to adjust the
> plunger
http://www.youtube.com/watch?v=QOJN_8AAC9U at about 50 hours and
> all was well after that.
>
> Recently I tried my largest printable project
>
http://www.youtube.com/watch?v=QOJN_8AAC9U and it failed after printing
> several layers. I should have checked the 'raft' option. Due to that
> failure, much filament (PLA) was extruded that didn't stick to the
> platform. Instead it stuck to the bottom side of the extruder assembly.
>
> After generating new gcode with a raft, I attempted the print again. This
> time, the accumulated gcode blobs at the base of the extruder assembly
> caught the already printed material on the first layer (the raft) and
> dragged it off the platform. I stopped the printing after that.
>
> Assuming that I needed to adjust the plunger once again, I did so, using
> the same technique illustrated in the video cited previously. (Because the
> extruder assembly was now quite hot, I was able to quite easily remove the
> majority of the semi-melted 'blobs' from the bottom. I felt that I had
> gotten back to normal. But a problem remained, and here it is:
>
> 1. My extruder will not heat.
> 2. When I attempt to print, the LED printout reads
> 2a: Extruder: NA, then
The NA is shown when the "monitor" screen sees that the heater has failed,
if(board.getExtruderBoard(0).getExtruderHeater().has_failed()){
lcd.writeFromPgmspace(NA2_MSG);
Now, when the heater was declared "failed", the routine which did that
declaration also made a decision as to whether or not to abort the print.
Since it did not abort the print, the error must have been a "not plugged
in" error. In that case, the routine has some faulty logic which makes
it NOT cancel the print,
if(heatFailMode == HEATER_FAIL_NOT_PLUGGED_IN)
{
// if single tool, one heater is not plugged in on purpose
// do not trigger a heatFail message unless both heaters are unplugged
if(!platform_heater.has_failed() && eeprom::isSingleTool() &&
(!(Extruder_One.getExtruderHeater().has_failed() && Extruder_Two.getExtruderHeater().has_failed())))
return;
// only fire the heater not connected error once. The user should be able to dismiss this one
else if (connectionsErrorTriggered)
return;
else
connectionsErrorTriggered =true;
}
No platform, so platform_heater.has_failed() is false
You only have one extruder so isSingleTool() is true
You don't have Extruder 2 so Extruder_Two.get…has_failed() is false
Net, net, the routine ignores the error and returns. Bad logic.
Now, why does it start printing then? Elsewhere the code asks if the extruder has
reached temp. Well, it has! When it failed, the current temp reading was set to 1024
to indicate an error. (Note how you saw "24/230" -- that was "1024/230" but truncated
to 3 digits and a leading "0" removed!) Now the code to see if it had reached temp
is fooled by the 1024 being > the target temp of 230 and so it says, yup we've reached
emp. So the printing starts.
Bug!
> Question: What do I need to do? Shall I back off that last 1/16 of a turn
> that your video advised me to make? Or is something else wrong? Mainly, why
> doesn't the extruder heat?
Looks like the wiring for the thermocouple isn't screwed down tight? Or it's
wired backwards? Or the thermocouple isn't working.
Dan