Re: [foxboro] EEPROM update for annunciator keyboard

Jeff,

I also have regularly done EEPROM updates of various modules including
the annunciator keyboards when required.  I don't remember any
annunciator keyboards failing to EEPROM, but I have had modules fail
EEPROM.  The older double wide modules, short FBMs, CP10s and older
COM10s seemed to be the worst as I recall.  When modules did fail
EEPROM about half the time I could cycle power to them and have them
come up as they were before.  I recall very few cases where I could
successfully EEPROM a module that had failed once.  Where they were
under contract, I normally MEP'd them.  Where they were not under
contract I normally put them in the "future advantage upgrade" pile.

In contrast to I/A's EEPROM update, I quite like the EEPROM update
method for the Sun UltraSPARC workstations.  It is very clear and
visible what is happening, and there are enough safeguards built in to
the process it is very unusual to fail an EEPROM in my experience.
The only time I recall having to give up on a Sun workstation was when
I was unfortunate enough to have a power failure part way through the
EEPROM update.  The failure may have been related to the partial
EEPROM, but also may have been related to the massive surge and
brownout prior to loss of power.

Regards,

Kevin FitzGerrell

On Tue, Jun 24, 2008 at 3:19 PM, Weiss, Andreas
<Andreas.Weiss@xxxxxxxxxxxx> wrote:
>> Someone at our facitiy did an EEPROM update for the=20
>> annunciator keyboard in System Monitor.=A0 Needless to say, the=20
>> annunciator keyboard is now inoperable. =A0This=A0is on a P70.=A0=20
>
> Hi Jeff,
>
> we are doing an EEPROM update regularly to get the Annunciator Keyboards =
> working if they fail after a reboot of a connected Solaris station.
>
> We never had a problem with 0.0.
>
> only a proposal:
> - check again the right position of the little DIP switches
> - power off and on the GCIO Box=20
> - reboot the AW/WP
> - try it again with the EEPROM update
>
> Please keep in mind that sometimes also a A. Keyboard fail.
>
> Regards,
> Andreas
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: