This is another good read about using automated terrain mapping for cruise missile guidance systems.<p><a href="https://en.wikipedia.org/wiki/TERCOM" rel="nofollow">https://en.wikipedia.org/wiki/TERCOM</a><p>Notably how it fit on older computer systems with limited memory by only sampling the terrain using a predefined path which a plane will travel over with imaging sensors beforehand. For minutemen style systems with predefined targets it would work well as the terrain won’t change significantly and there will be plenty of sampling data to support a high error rate and/or a relatively low resolution while moving at high speeds.<p>Of course it increased in quality and effectiveness over time (especially as whole topographical maps could eventually be stored, not just the path in question) but as an entirely ‘unguided’ rocket it seems to be relatively accurate for its era.
I visited the Titan Missile Museum in Tucson, AZ, where you can see the control room from which the missile could have been launched.<p>> At launch, orders from the National Command Authority would have specified one of three pre-programmed targets which, for security reasons, were unknown to the crew. ... Target 2, which is classified to this day but was assumed to be within the borders of the former Soviet Union, was designated as a ground burst, suggesting that the target was a hardened facility such as a Soviet missile base. [Wikipedia]<p>While explaining this, my tour guide showed some punched tape that could be fed into a computer to program the targets. I wonder if the tape was original, and if so, how difficult it would be to decode its coordinates.
If you're interested in the history of the Titan missile program and US nuclear program in general I recommend "Command and Control: Nuclear Weapons, the Damascus Accident, and the Illusion of Safety".
The fascinating thing is that the Titan was completely inertially guided, i.e., no GPS or ground-based navigation. The high precision IMU + gyro send the computer acceleration and angular velocity and you integrate that over time to figure out where you are now. I'd think this would be very challenging and error-prone for inter-continental travel especially when the thing is planning to detonate nuclear war head. I wonder what algorithms they used. Typical code to do dead reckoning from IMU+gyro is fairly short but drifts usually is huge killer.
GM/Delco were very diverse in manufacturing, so I'm not surprised that they also made missile components at one point. At one time they owned Frigidaire too.<p>Motorola made "MTTL II" which had 20xx part numbers for commercial temperature range and 21xx for industrial/military, so these could be Signetics' variant of that. In the late 60s through the 70s semiconductor companies made <i>lots</i> of different logic families.<p>I've always found it a bit sad that the ultimate purpose of things like this was for destruction.
I was just thinking, imagine trying to use a modern-day smartphone for this. So much complexity how could you be sure the missile would even get off the ground. There is a big advantage to systems that engineers can mostly "keep in their heads". Very few systems are that way these days.
I find it fascinating how much those grids resemble RAM chip die photos. I know the principle is different but in a sense we have just been shrinking things for over 70 years.
I'm surprised they opted to use a passively cooled power supply.<p>I imagine it was much heavier than an equivalent active system.<p>I guess MPG doesn't matter much on a Titan missile.
Great read! Intriguing to find out that earlier computers were using rotating drum memory systems in space flight and then delicate wiring in cores, I really hadn't considered that. I wonder about the reliability of those systems and whether there was software compensation for that issue.