From: Christoph Plattner <christoph.plattner@gmx.at>
To: John David Anglin <dave@hiauly3.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: Apollo 9000 power problem
Date: Thu, 21 Aug 2003 23:32:52 +0200 [thread overview]
Message-ID: <3F453A84.5040305@gmx.at> (raw)
In-Reply-To: 200308182034.QAA13970@hiauly3.hia.nrc.ca
Hello,
of course it is a "hack", but it is a constructive one, not
a bad thing like disconnecting the suppervision or so ...
I have replaced some of the capacitors, but it was not so simple
to detect the one, which has lost a bit of it's fluid ...
The problem is relly the layer of this chemicals of the capacitor and
the dust mixture, which generates the lack current. (I really have
problems to explain this all in English here ....)
I was not my thing to take the power supply out and hold it under
the water to clean, so I tried it with clothes, etc, but - as I
mentioned already in the last mail - some weeks later the problem
occured again. New dust on this checimal stuff .... (or new chemical
stuff ??? ...)
This SIMM-like suppervison thing checks six itmes on the power
supply (the other 6 comperators are use to generate the RESET
signal in case of "power good").
One measures the current. If the input of the comperator increases
2.35V (comming from meassure transformer meassuring the current
of some secondary linesm e.g. 5V, 12V...), then the protection
stops the power supply (the stop is done per thyristor, so one
short "stop" signal hold the power supply down until POFF/PON,
then the cycle starts again).
In idle operation (my test setup was a 10 Ohm + LED to see,
if the power is stable while repairing it), the voltage of
the current transformers is near 0V. All current transformers
have an own diode to one line. So if the output voltage of
the current transformes is lower the e.g. 0.6V (voltage of
the diode), behind the diodes the line has high impedance.
So the very low lack current of the near -12V line can drop
this line easy. If the voltage drops below 0V, the comperator
does not work correctly and asserts the "stop" (although
e.g. -0.5V is below 2.35, which should be OK !).
If there is an over current, there is a voltage on the output
side of the current transformer, and a representative voltage
is on the other side of the diode. This will pull up the the
line up to some voltage (higher than 2.35 leads to the stop ..).
So the 220KOhm resisitor only pulls the high impedance sense
line up against the "dust" resistor. But both "resistors" have
a high value against the output of the over current transformers,
if a big current is comming up.
So this "hack" is acceptable for me.
It was not acceptable for me, to short-cut or isolate the
over-current protection (I did this for one day for tests, but
I could not live with this feeling, not having this important
protection.
And see the alternative. A new powersupply of this type costs
about 1000 EURO, an "fresh repaied" about 300EURO, an old one
- perhaps having the same problem soon - costs about 150EURO ...
So I am happy to have a correct working power supply with a
full functioning protection and a "well defined" hack !
Ok, I cannot take any warranty for others ..., but I thought,
I know what I am doing.
Further questions are welcome.
Christoph P.
John David Anglin wrote:
> Christoph,
>
> I saw your recent note on power supply problems. It looks like
> my 735(730) has suffered a similar failure in the recent blackout.
> The symptoms appear similar to what you described a a couple of
> years ago. On power up, leds flash for 100-200 ms and then all
> go out.
>
> Did you replace the failed capacitor? Adding a resistor between
> the +Vaux line and the current sense line to compensate for leakage
> between the -12V line and the current sense line seems like a
> bit of a hack.
>
> Do you have docs for the supply?
>
> Dave
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
>
--
-------------------------------------------------------
private: christoph.plattner@gmx.at
company: christoph.plattner@alcatel.at
next prev parent reply other threads:[~2003-08-21 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 20:34 [parisc-linux] Re: Apollo 9000 power problem John David Anglin
2003-08-21 21:32 ` Christoph Plattner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-07 21:58 Christoph Plattner
[not found] <1059732252.1227.39.camel@rupa.go.net>
2003-08-01 11:21 ` Alexander Gabert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F453A84.5040305@gmx.at \
--to=christoph.plattner@gmx.at \
--cc=dave@hiauly3.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.