EVERYTHING RECORDED FOR WHICH I HAVE ALD ACCESS
Having recovered usable information from multiple blurry camera images of 2501 card reader controller ALD pages, I was able to enter those signals into the database in addition to all the devices that were configured in my system or are included in ALDs for all machines.
The few device controllers that I have no ALD page images for are the Synchronous Communications Adapter (SCA) that sits inboard of the 1130 and the 1230 Optical Mark Reader. The 1130 I am restoring was connected to a 1231 and has the controller logic cards installed, but I have no ALDs for the machine nor practical way to generate them.
One other area of the machine that I have no documentation for is the faster version of core memory that is installed on the 2.2 us machines. I have the SJ-4 Core Memory documents which matches my machine and the one I am restoring, but do not have the SJ-2 Core Memory documentation for the faster memory.
I had previously mentioned that a number of peripherals attach to the 1130 system through its Storage Access Channel (SAC), most hooked first to the 1133 Multiplexor unit that in turn uses the SAC to connect to the 1130. Any ALDs for those devices would be in the 1133 manual; since I have never seen one 'in the wild' I have no access to the diagrams for 1403 printers, 2310 and 2311 disk drives and other peripherals that were used with the IBM 1130.
MISSING ALD PAGE FOR 2501 READER CONTROLLER LOGIC
I discovered that my scans have missed one page of the logic for the device controller for the 2501 reader. I dimly remember that when I was creating my FPGA based replica of the 1130 system I had discovered this and recreated the functionality somehow, but didn't necessarily have the ALD page image.
The page in question is involved in controlling behavior in a number of key areas, based on the signals I see entering the other ALD pages from the missing one:
FINAL COUNT AFTER FIRST PASS RECORDING ALL OUTPUTS AND CABLE PINS
There are 4,080 pins recorded in the database after capturing all the outputs on the right sides of the ALD that have pin connections, all the cable pins that run between backplanes, and some of the inputs from external buttons and peripheral signals.
WHY I WILL PERFORM A SECOND PASS TO GRAB INPUT PINS
A major purpose of this database is to validate connections and test for potential backplane trace failures or cable failures in a machine. A backplane will contain cards from many ALD pages, but only the signals that travel to different backplanes are fully contained in the database. Those that move from one page to another will show up as pins on the left side of ALD pages.
The inputs on the left side are connected to one of the output signals I have already recorded, which gives me complete information for all the entering and exiting signals on each ALD page. Some of the inputs from peripheral devices or switches on the 1130 were already captured on the ALD first pass but some are less visible due to the indirect way IBM documented some of the cable connections. Thus, this second pass will complete the recording of all the inputs.
CONCEPTUAL THIRD PASS I DON'T INTEND TO PERFORM
The final set of data that could be collected, but I don't intend to do so at this time, is the routing between pins on an ALD page. Those complete the full set of traces, wire wrap or cable connections that exist in a system. However, I am not sure how I would name these internal paths, which are nets that don't have an official 1130 signal name because only signals exiting or entering ALD pages are declared. I would need to invent some nomenclature which might obscure the important information I already have collected. More importantly, it would be a very labor intensive activity whose payback is uncertain.