Received: by 10.66.73.1 with SMTP id h1mr1898989pav.0.1351976518755;
        Sat, 03 Nov 2012 14:01:58 -0700 (PDT)
X-BeenThere: makerbot@googlegroups.com
Received: by 10.68.216.6 with SMTP id om6ls3419159pbc.7.gmail; Sat, 03 Nov
 2012 14:01:55 -0700 (PDT)
Received: by 10.68.212.72 with SMTP id ni8mr1445695pbc.14.1351976515532;
        Sat, 03 Nov 2012 14:01:55 -0700 (PDT)
Date: Sat, 3 Nov 2012 14:01:54 -0700 (PDT)
From: Jon Daniels <ape...@gmail.com>
To: makerbot@googlegroups.com
Message-Id: <6a3d5ae9-b3f5-48e2-a7b1-a29b1ceb0d15@googlegroups.com>
In-Reply-To: <9ab08ca2-3219-4179-a937-2e4702e6725e@googlegroups.com>
References: <eb52b149-ac4f-48bf-a2ae-636d76fac668@googlegroups.com>
 <B518BB9A-5217-473F-8326-502A0E309104@mtbaldy.us>
 <C156AA15-4177-4B05-886C-528D6CC2FD2B@mtbaldy.us>
 <f04f473d-bea2-4db5-b6ed-856221f48578@googlegroups.com>
 <5E3E4DC8-53C0-4E1F-9497-8C026C213AF4@mtbaldy.us>
 <9ab08ca2-3219-4179-a937-2e4702e6725e@googlegroups.com>
Subject: Re: [MakerBot] Printer issues (recently upgraded to sailfish)
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1080_16360114.1351976515046"

------=_Part_1080_16360114.1351976515046
Content-Type: multipart/alternative; 
	boundary="----=_Part_1081_19425832.1351976515046"

------=_Part_1081_19425832.1351976515046
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

This happened to me a few days ago.  Same regulator blown apart...  Waiting 
for a replacement board.



On Thursday, November 1, 2012 4:23:38 PM UTC-7, CarryTheWhat wrote:
>
> Ok so that was pretty well timed. 10 minutes later, the same voltage 
> regulator exploded, as before (pictured)
>
> Yeah before, they gave me both a new board and an X axis endstop cable, 
> which I replaced (but was kind of hard because of how perfect the cables 
> are expected to kink in just the right way).
>
> Well, this thing is out of commission for a while.....
>
>
> On Thursday, November 1, 2012 7:19:01 PM UTC-4, dnewman wrote:
>>
>>
>> On 1 Nov 2012 , at 4:14 PM, CarryTheWhat wrote: 
>>
>> > Interesting.. Yeah there were no problems uploading the new firmware. 
>> And 
>> > it continued working fine for a while, I'm not sure if they are related 
>> > problems. In the past, I have had the same LCD display issue, and i 
>> think 
>> > that board eventually fried.. But it did not cause the communication 
>> > interrupt that result in failed prints. 
>> > 
>> > I am reverting the firmware now, but I don't see how that will help the 
>> LCD. 
>> > 
>> > In case it matters; when I start up the Replicator, the LCD displays as 
>> > normal.  But over the course of 2 or 3 minutes, it gradually gets 
>> darker 
>> > and darker. 
>>
>> Sounds like you have another board going bad.  From various reports, they 
>> are susceptible to issues from problematic endstop cables.  Did MBI have 
>> you 
>> replace them when you replaced the board?  (There's been a couple of 
>> reports 
>> in this forum of folks receiving a new board AND a new X axis endstop 
>> cable.) 
>>
>> At any rate, there's nothing in the firmware to slowly fade your LCD 
>> display 
>> or to write lots of black rectangles on it.   And if there's one problem 
>> (display), 
>> then there could just as likely be some other issues (e.g., USB comms). 
>>
>> Dan 
>>
>
------=_Part_1081_19425832.1351976515046
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

This happened to me a few days ago. &nbsp;Same regulator blown apart... &nbsp;Waiting for a replacement board.<div><br></div><div><br></div><div><br>On Thursday, November 1, 2012 4:23:38 PM UTC-7, CarryTheWhat wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">Ok so that was pretty well timed. 10 minutes later, the same voltage regulator exploded, as before (pictured)<div><br></div><div>Yeah before, they gave me both a new board and an X axis endstop cable, which I replaced (but was kind of hard because of how perfect the cables are expected to kink in just the right way).</div><div><br></div><div>Well, this thing is out of commission for a while.....</div><div><br><br>On Thursday, November 1, 2012 7:19:01 PM UTC-4, dnewman wrote:<blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>On 1 Nov 2012 , at 4:14 PM, CarryTheWhat wrote:
<br>
<br>&gt; Interesting.. Yeah there were no problems uploading the new firmware. And 
<br>&gt; it continued working fine for a while, I'm not sure if they are related 
<br>&gt; problems. In the past, I have had the same LCD display issue, and i think 
<br>&gt; that board eventually fried.. But it did not cause the communication 
<br>&gt; interrupt that result in failed prints.
<br>&gt; 
<br>&gt; I am reverting the firmware now, but I don't see how that will help the LCD.
<br>&gt; 
<br>&gt; In case it matters; when I start up the Replicator, the LCD displays as 
<br>&gt; normal. &nbsp;But over the course of 2 or 3 minutes, it gradually gets darker 
<br>&gt; and darker.
<br>
<br>Sounds like you have another board going bad. &nbsp;From various reports, they
<br>are susceptible to issues from problematic endstop cables. &nbsp;Did MBI have you
<br>replace them when you replaced the board? &nbsp;(There's been a couple of reports
<br>in this forum of folks receiving a new board AND a new X axis endstop cable.)
<br>
<br>At any rate, there's nothing in the firmware to slowly fade your LCD display
<br>or to write lots of black rectangles on it. &nbsp; And if there's one problem (display),
<br>then there could just as likely be some other issues (e.g., USB comms).
<br>
<br>Dan
<br></blockquote></div></blockquote></div>
------=_Part_1081_19425832.1351976515046--

------=_Part_1080_16360114.1351976515046--