Don wrote:
I was thinking more along the lines of excess
noise/ripple on a
supply, not that it had completely failed. If the supplies (+/-15V,
+/-12V, +5V) are out of whack the DC OK led will go off, but if one
of them (like 5V) is noisy, it could result in intermittent logic
operation but still indicate DC OK.
Ok, I did some tests. Still without the VOM or scope ...
And running
without UBI didn't even occur to me! The memory has
dedicated slots, so it is not accessed through the UBI module?
Maybe I should have
been clearer; I meant UNIBUS I/O modules (like
a disk controller) not the UBI module. AFAIK you can only remove the
CIS set, the FPP, and the CACHE module and still have the CPU be in
a runnable condition. The UBI module (M7098?) is not optional.
LOL - yes, I found that out this evening!
I will write down my findings. They might be useful in the future ...
This is (was) my 11/44 backplane "usage":
slot pos board
1 a-b M7090 CIM
c-f empty
2 a-f empty
3 a-f M7093 FP11-F
4 a-f M7094 data path
5 a-f M7095 ctrl
6 a-f M7096 MFM
7 a-f M7097 cache
8 a-f M7098 UBI
9 a-f M8722 22-bit ECC
10 a-f M8743 MS11-P
11 a-f empty
12 a-f empty
13 a-f Quadrasync E
14 a-b M9202 (to next backplane)
c-f G7273
Note the two different memory boards ... this system was working fine!
As first test, I pulled everything, except slot 1, 4, 5, 6.
Slot 13 has in position c-d a G7273, and slot 14 has in a-b the M9302,
and c-d a G7273.
Result: RUN led is OFF (hurray), but I get "?CP didn't start"
and the following output on my entries at the >>> prompt:
>> h
?Already halted
>> t/e
?Parity error
Test #2, inspired by the "parity error" message, I 'added' slot 9.
Power up the system. RUN led is still OFF, these are the messages:
(Console V3.40C)
(Program)
(Console)
?CP didn't start
>> t/e
?Parity error
Ok, the memory board does not add problems, nor does it take a problem
away. I leave it installed, and 'add' slot 9, UBI ... Power up again,
the RUN led is still OFF. These are the messages:
(Console V3.40C)
(Program)
(Console)
Halted at 165020
>> t/e
?Already halted
That last response takes a few seconds, so the test needs some time!
Then I tried the following:
>> e 1000
P 00010000 000011
>>> d 1000 123456
>> e 1000
P 00010000 123456
It's all looking great now! The "Halted at 165020" is because of
how the switch on the CTRL (M7095) is set, and how the console
switch is set (HALT). If the console switch is set to CONT the
line following (Console) is "Halted at 165714". Address 165020 is
a familiar address, it is the start address of the PROM to start
the CPU *with* diagnostics. I always use that address on my 11/34!
Then I 'added' the cache option (M7097). The system is still fine,
no matter how the 2 switches on the cache module are set (forced
generation of misses).
Adding the FP11-F still gives a healthy system.
Just 2 boards left from the point where I started, the Quadrasync E
and the second memory board. I chose to install the second memory
board first. Power on ... RUN led stays ON (!), console printout is
not what it should be, allthough a prompt appears when I hit ^P.
Entering "d 1000 55" returns the "?Halt CP" message.
When I remove that second memory board all is back to "normal"!
I have not had the time to add the Quadrasync E board (leaving the
2nd memory board out of the system of course, and I have not yet
made any measurements ... I know, I should!
But I start guessing that the +/-12V perhaps has an issue. That
might explain (?) the problem when the 2nd memory board is added,
but why is the first memory board OK? Perhaps just the logic on
that 2nd memory board died, and hangs the system (not the UNIBUS
as the memory is *not* on the UNIBUS!).
Note, the 2 memory boards are different, but the system was in
productive operational condition at a company in that configuration.
The +/-12V "issue" (if there is one) also might explain why the
FAULT light is always ON on the RL02.
That was also in perfect order till a week ago ...
So, Don ... cache is indeed optional, UBI (as I found out) is not!!
Tomorrow I will check the power supply voltages. +5.1V is expected
to be OK, but the +/-12V ... hmmm, how come that the RS-232 signals
to and from the VT100 are working ...?
thanks!
(a happier looking) Henk.
This message and attachment(s) are intended solely for the use of the addressee and may
contain information that is privileged, confidential or otherwise exempt from disclosure
under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this
message to the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by
telephone and with a "reply" message.
Thank you for your cooperation.