So I'll mention a couple of things from my experience
restoring a couple of PDP-11/40s.
Across two PDP-11/40 processor sets, I need to replace about 15 chips:
- 74H50 x3
- 74175 x2
- 74174
- 74153 x2
- 74194
- 74151
- 7474
- 7450
- 7404
- DEC 8815 (more or less a 7425)
Of those chips, none of them were unibus driver chips. I would recommend against attempting to debug the unibus by starting with the suspicion that a driver is at fault. The circuitry for generating the unbus timing/signals is very stateful. In my experience, it has been some state-keeping element that has died, for example, a 74175 or 7474. I don't know the design of the pdp-11/60, but in the case of the PDP-11/40 when doing a unibus transaction, the CPU clocking shuts off. Later, on the completion of the unibus transaction, the CPU is resumed asynchronously. In the case of the 11/40, when there is a serious unibus fault, the CPU will lock up and the system will be unresponsive and or malfunction in odd ways.
Put the unibone to the side for now, and get yourself a set of
UniProbes. It's good to have one installed all the time in the system so you can watch the LEDs. They are good for spotting anomalies. But more importantly, it's a fantastic tool for connecting up a logic analyser; you won't need to connect up all the signals, you can get away with as few as 8 if you have to.
The next thing you need to try and figure out is if there is some kind of maintenance interface available on the system. You're not going to get far from its front console on its own. The 11/40 uses the
KM11.
Doing some spread reading of the available documentation, you will need to find yourself a "DCS (Diagnostic Control Store) Module M7871 (KU116-BB)".
It's described here:
https://www.bitsavers.org/pdf/dec/pdp11/1160/EK-KD11K-TD-PRE_Jan78.pdf
And here is some of the docs: