From: Christoph Plattner <christoph.plattner@gmx.at>
To: "parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] [Fwd: Re: Repair of BM200-3601]
Date: Sat, 11 Oct 2003 00:27:56 +0200 [thread overview]
Message-ID: <3F87326C.2010705@gmx.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
The Mail to "Ed J.M. Veling" was bounced by a BLACKHOLE LIST filter.
So I resend it to PA-RISC group !
Bye
Christoph
--
-------------------------------------------------------
private: christoph.plattner@gmx.at
company: christoph.plattner@alcatel.at
[-- Attachment #2: Re: Repair of BM200-3601 --]
[-- Type: message/rfc822, Size: 2860 bytes --]
From: Christoph Plattner <christoph.plattner@gmx.at>
To: "Ed J.M. Veling" <Ed.Veling@CiTG.TUDelft.nl>
Subject: Re: Repair of BM200-3601
Date: Fri, 10 Oct 2003 23:57:30 +0200
Message-ID: <3F872B4A.1050909@gmx.at>
Sorry to hear that .... I also suffer, if my "old machines"
have troubles ....
Hello,
do we speak here about the same type of power supply, then I may
help you perhaps.
Ths small SIMM-lile module on the 60-pin conntector side, is a
supervision module generating the "emergency stop" signal to
the power supply, if there is a problem. Further it generates the
the RESET signal for the machine (or better the POWER GOOD signal).
As I remember the schematics, there are 6 reasons for switching
off the power supply:
Over 5V, 12V, under -5, -12V, over current and over temperature.
You have to find out, which is true here.
Check the type, and reply if you need further help ....
Christoph
Ed J.M. Veling wrote:
> Dear Christoph,
>
> With interest I have read your contribution w.r.t. the repair of the
> BM200-3601 power supply.
> We have comparable problems: 2 power supplies have worked for 11 years and
> then suddenly
> almost at the same time they stopped. It is possible to restart these UNIX
> workstations
> but after some time, sometimes one hour, sometimes 2 days later, they stop
> again.
> By the way, these workstations are located in a air-conditioned room.
> So, I was very happy to read your suggestion to put some resistance into the
> power supply.
> At our department, a technical person has done this repairment. Last tuesday
> I restarted the workstation
> and I was very happy to see it operating. However, after two days, I was quite
> disappointed: again,
> the workstation was dead.
> Now, you are my last resort. Do you have maybe another suggestion to keep
> these power supplies
> alive ?
> I thank you very well in advance.
> Yours sincerely,
>
> Ed Veling
>
>
>
> --
> Dr. E.J.M. Veling,
> Delft University of Technology,
> Faculty of Civil Engineering and Geosciences,
> Department of Water Management,
> Section for Hydrology and Ecology,
> Stevinweg 1, NL-2628 CN Delft, The Netherlands,
> P.O. Box 5048, NL-2600 GA Delft, The Netherlands,
> phone: (+31)152783156 ((+31)152785074),
> fax: (+31)152785915,
> room: 4.89,
> e-mail: Ed.Veling@CiTG.TUDelft.nl
> URL: http://hydrology.citg.tudelft.nl
>
>
>
>
--
-------------------------------------------------------
private: christoph.plattner@gmx.at
company: christoph.plattner@alcatel.at
reply other threads:[~2003-10-10 22:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F87326C.2010705@gmx.at \
--to=christoph.plattner@gmx.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox