X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from cdptpa-omtalb.mail.rr.com ([75.180.132.120] verified) by logan.com (CommuniGate Pro SMTP 5.2c1) with ESMTP id 2552035 for flyrotary@lancaironline.net; Sun, 02 Dec 2007 11:24:50 -0500 Received-SPF: pass receiver=logan.com; client-ip=75.180.132.120; envelope-from=eanderson@carolina.rr.com Received: from edward2 ([24.74.103.61]) by cdptpa-omta01.mail.rr.com with SMTP id <20071202162413.BVPU27254.cdptpa-omta01.mail.rr.com@edward2> for ; Sun, 2 Dec 2007 16:24:13 +0000 Message-ID: <001b01c834ff$ce813c20$2402a8c0@edward2> From: "Ed Anderson" To: "Rotary motors in aircraft" References: Subject: Re: [FlyRotary] Re: Need some advise.. Date: Sun, 2 Dec 2007 11:24:26 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01C834D5.E57B7190" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 This is a multi-part message in MIME format. ------=_NextPart_000_0018_01C834D5.E57B7190 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MessageHey, Bill, don't beat up on yourself about it. If we haven't = done that particular dumb thing, we have certainly done others {:>). I have no personal experience. I have read that silicon is suppose to = be bad for the O2 sensor. I don't know if the damaging effect is = simply coating of the zircon material in the O2 sensor or if there is = some chemical reaction that forever alters and damages the sensor. I = presume you have verified that the sensor is still connected = electrically. More than once, I have found myself assuming that one = action on my part cause a problem and zeroed in on it - only to find = that after much wasted time - it was another cause. =20 So just to rule it out, I would check the continuity between my O2 = sensor and the indicator you are using. I guess I would be tempted to take it out and soak it in gasoline or = something that acts as a solvent. I mean nothing to lose doing that and = perhaps it could clean the stuff off. Ed ----- Original Message -----=20 From: Bill Bradburry=20 To: Rotary motors in aircraft=20 Sent: Sunday, December 02, 2007 9:15 AM Subject: [FlyRotary] Re: Need some advise.. So, it appears that I am the only one dumb enough to do this..:>) Does anyone have any helpful thoughts? I would hate to replace the O2 = sensor and just contaminate the replacement. Thanks, Bill B =20 =20 -------------------------------------------------------------------------= ----- From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] = On Behalf Of Bill Bradburry Sent: Saturday, December 01, 2007 12:38 PM To: Rotary motors in aircraft Subject: [FlyRotary] Need some advise.. I just removed my exhaust to have some welding done on it. When I = replaced it, I added some anti-seize compound on the two EGT = thermocouples and also the O2 sensor boss. When I started the engine, the O2 sensor worked for a few minutes, = then stopped working. I assume that it did not like the anti-seize = compound??? My question is.will it come back after a while? If I need to replace = the O2 sensor, should I try and remove all the compound from the = thermocouples as well? (they are ahead of the O2 sensor) Should I run = the engine for a while after I remove the compound to try and burn it = out of the pipe or should I clean out the pipe? =20 How bad is my situation? What to do..What to do??? =20 Thanks for the help! =20 Bill B=20 ------=_NextPart_000_0018_01C834D5.E57B7190 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message=
Hey, Bill, don't beat up on yourself about = it.  If we=20 haven't done that particular dumb thing, we have certainly done others=20 {:>).
 
I have no personal experience.  I have read = that=20 silicon is suppose to be bad for the O2 sensor.   I don't know = if the=20 damaging effect is simply coating of the zircon material in the O2 = sensor or if=20 there is some chemical reaction that forever alters and damages the=20 sensor.  I presume you have verified that the sensor is still = connected=20 electrically.  More than once, I have found myself assuming that = one action=20 on my part cause a problem and zeroed in on it - only to find that after = much=20 wasted time - it was another cause. 
 
So just to rule it out, I would check the = continuity=20 between my O2 sensor and the indicator you are using.
 
I guess I would be tempted to take it out and = soak it in=20 gasoline or something that acts as a solvent.  I mean nothing to = lose doing=20 that and perhaps it could clean the stuff off.
 
Ed
----- Original Message -----
From:=20 Bill=20 Bradburry
Sent: Sunday, December 02, 2007 = 9:15=20 AM
Subject: [FlyRotary] Re: Need = some=20 advise..

So, it appears that I am the only one dumb = enough to=20 do this..:>)

Does anyone have any helpful thoughts?  = I would=20 hate to replace the O2 sensor and just contaminate the=20 replacement.

Thanks,

Bill B

 

 

From:=20 Rotary motors in aircraft = [mailto:flyrotary@lancaironline.net] On=20 Behalf Of Bill Bradburry
Sent: Saturday, December 01, = 2007 12:38=20 PM
To: = Rotary motors in aircraft
Subject: [FlyRotary] Need some=20 advise..

I just removed my exhaust to have some = welding done on=20 it.  When I replaced it, I added some anti-seize compound on the = two EGT=20 thermocouples and also the O2 sensor = boss.

When I started the engine, the O2 sensor = worked for a=20 few minutes, then stopped working.  I assume that it did not like = the=20 anti-seize compound???

My question is=85will it come back after a = while? =20 If I need to replace the O2 sensor, should I try and remove all the = compound=20 from the thermocouples as well? (they are ahead of the O2 = sensor)  Should=20 I run the engine for a while after I remove the compound to try and = burn it=20 out of the pipe or should I clean out the = pipe?

 

How bad is my situation?  What to = do=85.What to=20 do???

 

Thanks for the = help!

 

Bill=20 B 

------=_NextPart_000_0018_01C834D5.E57B7190--