glitch
Veteran Member
Starting a new thread, though this is related to the PDP-11/34a Cleanup and Repair thread.
I have several RK05 drives, a RK11-D backplane and board set from Conmega, and a RLV11-D that came with the MINC-23 (which is also where some of the RK05 drives are from). I'm starting into them in an effort to have a good baseline system to test with for some upcoming customer work, as well as just to get my RK05s online and usable. Ultimately, I'd like to have at least two drives working really well, and pair them with my PDP-11/10 -- one of the drives is a definite parts drive, I forget if it's had anything stolen off of it but it's in very bad shape from a mouse house.
Since I have the PDP-11/34a on the bench, and since it's got more RAM, can support a RL11 on the system backplane, etc. I will be using it to get the RK11-D up and going first, and I'll use the RK11-D to test and repair the RK05 drives. Yesterday, I got out the RK11-D backplane and cleaned it. Looks like it had a mouse mess in the A and B connectors. I picked out as much of the big chunks as I could, then washed it several times with hot soapy water, until no "particles" came out when shaking the water out. Then it got dried, and after drying the connectors were cleaned with heavy cardstock and isopropyl alcohol, followed by De-Oxit.
I mounted the RK11-D in the PDP-11/34a system chassis this morning. It is the only other backplane in the chassis, as the DD11-DK that was in there had issues back in 2017. I cleaned the four boards in the RK11-D controller set, along with a M930 terminator. Got everything installed and a Unibus jumper to the PDP-11/34a backplane, moved the 11/34a's terminator to the Unibus Out slot, and put the M930 into RK11-D slot 2 since I wouldn't be connecting drives at first (it was not 100% clear whether I needed to terminate the drive connector or not). The system came up and booted the RL02, so that's a good sign! No hung Unibus or anything.
ZRKJ?? controller diagnostics immediately blew up with wrong data errors in the RKCS, RKWC, and other registers. I started fault tracing and eventually isolated one of the bit faults to the data paths board -- bit 15 was stuck low. The other fault was harder to find: bit 6 of the RKCS, RKWC, and a few other registers was stuck low. I traced it through the printsets, replacing what I thought to be the most likely culprits first -- since it affected more than one register, I assumed it was a data paths fault. When that didn't produce results, I replaced the mux and latch on the status/control board. Still no luck! Replaced the Unibus buffer on the bus interface board...and it was still stuck low. Finally, I turned the chassis on its side and checked AF1 continuity with the Simpson 260 -- open connection! The fault ended up being a dirty Unibus Out connector pin on the PDP-11/34a system backplane. Now, that's been cleaned at least twice, so I considered it might be a break in a wire or something. Nope, just persistent crud in the connector. I used a piece of crocus cloth to polish it, and now have passed 35 rounds of ZRKJ?? without issue!
I guess the next step is to get a RK05 out and start going through it...
I have several RK05 drives, a RK11-D backplane and board set from Conmega, and a RLV11-D that came with the MINC-23 (which is also where some of the RK05 drives are from). I'm starting into them in an effort to have a good baseline system to test with for some upcoming customer work, as well as just to get my RK05s online and usable. Ultimately, I'd like to have at least two drives working really well, and pair them with my PDP-11/10 -- one of the drives is a definite parts drive, I forget if it's had anything stolen off of it but it's in very bad shape from a mouse house.
Since I have the PDP-11/34a on the bench, and since it's got more RAM, can support a RL11 on the system backplane, etc. I will be using it to get the RK11-D up and going first, and I'll use the RK11-D to test and repair the RK05 drives. Yesterday, I got out the RK11-D backplane and cleaned it. Looks like it had a mouse mess in the A and B connectors. I picked out as much of the big chunks as I could, then washed it several times with hot soapy water, until no "particles" came out when shaking the water out. Then it got dried, and after drying the connectors were cleaned with heavy cardstock and isopropyl alcohol, followed by De-Oxit.
I mounted the RK11-D in the PDP-11/34a system chassis this morning. It is the only other backplane in the chassis, as the DD11-DK that was in there had issues back in 2017. I cleaned the four boards in the RK11-D controller set, along with a M930 terminator. Got everything installed and a Unibus jumper to the PDP-11/34a backplane, moved the 11/34a's terminator to the Unibus Out slot, and put the M930 into RK11-D slot 2 since I wouldn't be connecting drives at first (it was not 100% clear whether I needed to terminate the drive connector or not). The system came up and booted the RL02, so that's a good sign! No hung Unibus or anything.
ZRKJ?? controller diagnostics immediately blew up with wrong data errors in the RKCS, RKWC, and other registers. I started fault tracing and eventually isolated one of the bit faults to the data paths board -- bit 15 was stuck low. The other fault was harder to find: bit 6 of the RKCS, RKWC, and a few other registers was stuck low. I traced it through the printsets, replacing what I thought to be the most likely culprits first -- since it affected more than one register, I assumed it was a data paths fault. When that didn't produce results, I replaced the mux and latch on the status/control board. Still no luck! Replaced the Unibus buffer on the bus interface board...and it was still stuck low. Finally, I turned the chassis on its side and checked AF1 continuity with the Simpson 260 -- open connection! The fault ended up being a dirty Unibus Out connector pin on the PDP-11/34a system backplane. Now, that's been cleaned at least twice, so I considered it might be a break in a wire or something. Nope, just persistent crud in the connector. I used a piece of crocus cloth to polish it, and now have passed 35 rounds of ZRKJ?? without issue!
I guess the next step is to get a RK05 out and start going through it...