Yes indeed, on the "Peripheral Interface" connector of the US
configuration there was a terminator which seems indicated that nothing
was connected there. Moreover, with the Program Cartridge US, the
terminal does not recognize the PERIPHERAL I/O board of my original
configuration.
This is why I use the CPU board US, its memory extension but with my
Program Cartridge and my PERIPHERAL I/O board on which the subsystem
8406 was connected.
It is not impossible that the PERIPHERAL I/O board US is also able to
manage the 8406 Subsystem, the board is very elaborate, 4 or 5 Zilog 80,
and two rows of dip switches, but without documentation ... I prefer to
try with the board that worked with the subsystem.
It remains to be discovered what the "SERIAL I/O CHANNEL B" is, find the
related component and the breakdown, and there is a good chance that I
can restart this venerable machine.
But I search everywhere, I have not found any information that explains
what it is.
Dominique
On 2/10/2017 21:28, jim stephens via cctalk wrote:
On 10/2/2017 9:13 AM, Dominique Carlier via cctalk wrote:
Everything would be perfectly fine if most of the time I did not have
at startup an error at line 9. of the POC test:
SERIAL I / O CHANNEL B: FAILED
I doubt the US unit you bought was used with a floppy running CPM. It
most likely had a synchronous channel for connection to some network
and ran just standalone.
I recall that there were modules of some sort you added to get some
functionality, so as to not have to open the box. I don't know if you
set anything outside the box, but it may have some switches or such to
indicate some other device is present that now is not. So it would
fail on power on test.
that's just a guess on which way I'd go to figure it out. I don't
have any documentation or anything other than having had one for about
a year for a project I did to go on.
Mine had no floppies, but had a printer interface option attached
which was the same as one that was on a Univac 1100 series mainframe I
was making a controller for. So I could just run a standalone test
and if my controller card was working it would spew on the printer.
That option was also one of these things added on. Never dug into
anything as the device is pretty overengineered and without a lot of
manuals and parts, you can't do much with it.
thanks
Jim
