Received-SPF: pass
 receiver=logan.com; client-ip=75.180.132.121; envelope-from=eanderson@carolina.rr.com
From: "Ed Anderson" <eanderson@carolina.rr.com>
To: "'Rotary motors in aircraft'" <flyrotary@lancaironline.net>
Subject: RE: [FlyRotary] Re: frustrating couple of days
Date: Thu, 2 Jul 2009 11:39:21 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <list-3742629@logan.com>
Thread-Index: Acn7ISPOE1QMvyVdROmyfPp04GAz/QACdfiA
Message-Id: <20090702153921966.WOJE24657@cdptpa-omta01.mail.rr.com>

Thanks Thomas,

Clearly anytime any part of the chip might be operating outside of specs
enhances the odds for something going amiss.  I had not known that bit =
of
history on EEPROMs.  Just started using embedded chips about 4 years ago =
-
still lots to learn.

Ed

Ed Anderson

Rv-6A N494BW Rotary Powered

Matthews, NC

eanderson@carolina.rr.com

http://www.andersonee.com

http://www.dmack.net/mazda/index.html

http://www.flyrotary.com/

http://members.cox.net/rogersda/rotary/configs.htm#N494BW

http://www.rotaryaviation.com/Rotorhead%20Truth.htm


-----Original Message-----
From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On
Behalf Of thomas walter
Sent: Thursday, July 02, 2009 10:26 AM
To: Rotary motors in aircraft
Subject: [FlyRotary] Re: frustrating couple of days


Ed,

Odd electrical trivia.   Older eeproms were rated at 3.3V, so below 2.7V
they ignored any read or write information.

We had a uC that would start "jabbering" on the data and clock lines =
when
power was caming up.   Since reset occurred once power was good, it was
never an issue.   Problem is the eeprom manufactures started shipping =
parts
that were functional from 1.8V to 3.3V.  So once power was at 1.7V, it
accepted writes, corrupting the eeprom. Just to drive the engineers =
crazy
only some lots and some devices 'jibbered' away.   Yes, amazing I still =
have
any hair left. :)

That is pretty rare, but has happened.=20

Yes, Mike -- Interesting you're only seeing an issue with the "B"
controller. Still triple check the power, grounds, and rest of the
connections. =20
=20
> Since the fuel map is stored in non-volute memory, it=92s hard to =
figure out
how it is being re-written or destroyed.=A0 Normally (as you know) =
access to
EEPROM on a chip is a rather non-trivial process.=A0 =A0Since the A and =
B
controller are two different chips, I suppose there could be a problem =
with
the B chip =96 but, while that does happen, it=92s pretty rare.=A0 Have =
not had
one myself (yet).


     =20

--
Homepage:  http://www.flyrotary.com/
Archive and UnSub:
http://mail.lancaironline.net:81/lists/flyrotary/List.html

__________ Information from ESET NOD32 Antivirus, version of virus =
signature
database 3267 (20080714) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

=20

__________ Information from ESET NOD32 Antivirus, version of virus =
signature
database 3267 (20080714) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
=20