Successfully ran keyboard/1053 diagnostic program and did some additional testing - console printer in perfect condition now

MY PREVIOUSLY HACKED CODE NEEDED MORE WORK TO RUN BUT EVENTUALLY DID

The hack introduced so this would run on the imperfect 1130 simulator caused the code to complain on a real machine working correctly. I did some hand debugging and found the issues. More hacking but eventually the diagnostic ran through all its routines and the typed output looked excellent.

I hooked up the oscilloscope to watch various signals, including the controller logic Busy signal and the feedback circuits coming from the typewriter. It all looked great. The Interlock signal blocked any requests while the long duration functions - tab and carrier return - were underway. 

The CB Response signal activated at the points in the various cycles and didn't release the controller until the appropriate times in those cycles. This covered the space, backspace, printing, shift and tab initiation cycles. I looked at the millisecond timings and compared to the charts in the FE maintenance manual, finding agreement. The beast has been conquered!