Xref: utzoo comp.dcom.modems:2164 comp.mail.uucp:1533
Path: utzoo!utgpu!attcan!uunet!n3dmc!johnl
From: johnl@n3dmc.UU.NET (John Limpert)
Newsgroups: comp.dcom.modems,comp.mail.uucp
Subject: Re: Catatonic TrailBlazer Pluses
Message-ID: <407@n3dmc.UU.NET>
Date: 31 Jul 88 12:53:36 GMT
References: <1461@pyrnj.uucp> <22499@amdcad.AMD.COM>
Reply-To: johnl@n3dmc.UUCP (John Limpert)
Distribution: comp
Organization: N3DMC, Silver Spring, Maryland
Lines: 24

In article <22499@amdcad.AMD.COM> rpw3@amdcad.UUCP (Rob Warnock) writes:
>Last weekend, several TB+'s at AMD (amdcad.amd.com) "locked up" exactly as
>you described (*NOTHING* until you power-cycle), and when I got home (about
>25 miles away) I discovered that the TB+ on "redwood.uucp" had locked up
>exactly the same way. Coincidence?

Probably not a coincidence.  I've had the same thing happen to my TB+
with the 4.0 ROM's.  The TB+ appears to have a problem with power supply
output sequencing/reset.  Short power hits from thunderstorms will put
the modem in zombie mode.  I just cycle the power and that fixes it.  I
have had similar problems with other equipment.  If the power supply was
designed properly, the modem would keep on running or reset itself,
dependent on the severity of the power hit.  I'm not an engineer, but
some power supplies monitor the AC input voltage and DC output voltages. 
The power supply can generate a POWER OK signal to the equipment and/or
shutdown the DC output if it is out of spec.  If done properly, this
prevents this type of problem.  I hate having a system go down over a
weekend because of a power glitch.  The system stays down until someone
comes in on monday morning and resets the equipment.

-- 
John A. Limpert
UUCP:	johnl@n3dmc.UUCP, johnl@n3dmc.UU.NET, uunet!n3dmc!johnl
PACKET:	n3dmc@n3dmc.ampr.org	n3dmc@wa3pxx