137 lines
8.2 KiB
HTML
137 lines
8.2 KiB
HTML
|
<!DOCTYPE html>
|
||
|
|
<html lang="en">
|
||
|
|
<head>
|
||
|
|
<meta charset="utf-8">
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||
|
|
<title>Alarm 1201 — Deep Dive | Carla Long</title>
|
||
|
|
<meta property="og:type" content="website">
|
||
|
|
<meta property="og:title" content="Alarm 1201 — Deep Dive | Carla Long">
|
||
|
|
<meta property="og:description" content="Alarm 1201 on the Apollo Guidance Computer (AGC) is formally known as Executive Overflow . It occurs when the program executive — the AGC">
|
||
|
|
<meta property="og:image" content="https://images-assets.nasa.gov/image/as11-44-6584/as11-44-6584~medium.jpg">
|
||
|
|
<meta property="og:url" content="https://carla-long.4ort.net/alarm-1201.html">
|
||
|
|
<meta name="twitter:card" content="summary_large_image">
|
||
|
|
<meta name="description" content="Alarm 1201 on the Apollo Guidance Computer (AGC) is formally known as Executive Overflow . It occurs when the program executive — the AGC's task scheduler…">
|
||
|
|
<style>
|
||
|
|
:root { --bg: #0a0a0a; --fg: #e8e8e8; --accent: #ff6b35; --muted: #666; }
|
||
|
|
* { margin: 0; padding: 0; box-sizing: border-box; }
|
||
|
|
body {
|
||
|
|
font-family: 'Courier New', 'Lucida Console', monospace;
|
||
|
|
background: var(--bg);
|
||
|
|
color: var(--fg);
|
||
|
|
line-height: 1.6;
|
||
|
|
font-size: 15px;
|
||
|
|
max-width: 72ch;
|
||
|
|
margin: 0 auto;
|
||
|
|
padding: 2rem 1.5rem;
|
||
|
|
}
|
||
|
|
a { color: var(--accent); text-decoration: underline; text-underline-offset: 3px; }
|
||
|
|
a:hover { color: #ff9a6c; }
|
||
|
|
header { border-bottom: 2px solid var(--accent); padding-bottom: 1rem; margin-bottom: 2rem; }
|
||
|
|
header h1 { font-size: 1.3rem; font-weight: 700; }
|
||
|
|
nav { margin: 1rem 0; }
|
||
|
|
nav a { margin-right: 1.2rem; font-size: 0.85rem; }
|
||
|
|
.essay h2 { font-size: 1.1rem; color: var(--accent); margin: 1.8rem 0 0.6rem; text-transform: uppercase; letter-spacing: 1px; }
|
||
|
|
.essay p { margin-bottom: 1rem; }
|
||
|
|
.essay ul { margin-left: 1.5rem; margin-bottom: 1rem; }
|
||
|
|
.essay li { margin-bottom: 0.4rem; }
|
||
|
|
.data-block { background: #141414; border: 1px solid #333; padding: 1rem; margin: 1.2rem 0; font-size: 0.85rem; }
|
||
|
|
.data-block dt { color: var(--accent); margin-top: 0.5rem; }
|
||
|
|
.data-block dd { margin-left: 1.5rem; color: #bbb; }
|
||
|
|
.callout { border: 1px solid var(--accent); padding: 1rem; margin: 1.2rem 0; background: #1a1008; }
|
||
|
|
.callout strong { color: var(--accent); }
|
||
|
|
figure { margin: 1.2rem 0; }
|
||
|
|
img { max-width: 100%; border: 1px solid #333; display: block; }
|
||
|
|
figcaption { font-size: 0.75rem; color: var(--muted); margin-top: 0.3rem; margin-bottom: 1rem; }
|
||
|
|
footer { margin-top: 3rem; padding-top: 1rem; border-top: 1px solid #333; font-size: 0.8rem; color: var(--muted); }
|
||
|
|
footer a { margin-right: 1rem; }
|
||
|
|
</style>
|
||
|
|
<script defer src="https://analytics.4ort.xyz/script.js" data-website-id="d3ed927c-888a-4a6c-ae5f-0b1c613ddf5b"></script>
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
|
||
|
|
<header>
|
||
|
|
<h1>alarm 1201 — deep dive</h1>
|
||
|
|
<div style="color:var(--muted);font-size:0.85rem;margin-top:0.3rem">What the Apollo 11 Guidance Computer's most famous alarm actually means</div>
|
||
|
|
<nav>
|
||
|
|
<a href="index.html">← back to home</a>
|
||
|
|
<a href="about.html">about</a>
|
||
|
|
</nav>
|
||
|
|
</header>
|
||
|
|
|
||
|
|
<section class="essay">
|
||
|
|
|
||
|
|
<figure>
|
||
|
|
<img src="https://images-assets.nasa.gov/image/as11-44-6584/as11-44-6584~medium.jpg" alt="Apollo 11 Lunar Module separation from the Command Module">
|
||
|
|
<figcaption>NASA / Public Domain — Apollo 11 Lunar Module Eagle separating from the Command Module</figcaption>
|
||
|
|
</figure>
|
||
|
|
|
||
|
|
<h2>The Alarm, Decoded</h2>
|
||
|
|
|
||
|
|
<p>Alarm 1201 on the Apollo Guidance Computer (AGC) is formally known as <strong>Executive Overflow</strong>. It occurs when the program executive — the AGC's task scheduler — cannot service all its interrupt requests within the time window. The executive fills up. The system responds by dropping the lowest-priority queued tasks to free space for the highest-priority ones. The alarm is a <em>warning</em>, not a failure condition.</p>
|
||
|
|
|
||
|
|
<div class="callout">
|
||
|
|
<strong>Key distinction:</strong> 1201 is an <em>overflow warning</em>. The AGC keeps running. It does not crash. It does not halt. It simply notifies the crew that it is shedding tasks. The landing program remains active unless the overflow becomes so severe that the executive cannot execute any program — which never happened on Apollo 11.
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<h2>What Triggered It</h2>
|
||
|
|
|
||
|
|
<p>During the powered descent phase of the Apollo 11 landing, the Lunar Module's rendezvous radar — which was supposed to be turned off — was sending data to the AGC because its mode switch was inadvertently left in the "on" position. The radar generated continuous interrupts. Combined with the heavy computational load of the descent guidance program (P65), the executive queue overflowed.</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><strong>Primary cause:</strong> Rendezvous radar mode switch left in "on" position</li>
|
||
|
|
<li><strong>Contributing factor:</strong> High computational load of P65 (Powered Descent Guidance)</li>
|
||
|
|
<li><strong>Timing:</strong> First alarm at approximately 20:05 UTC, during final descent</li>
|
||
|
|
<li><strong>Occurrences:</strong> Alarm 1201 triggered multiple times; alarm 1202 (similar overflow) also appeared</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<h2>Why Ground Said "Keep Going"</h2>
|
||
|
|
|
||
|
|
<p>At Mission Control in Houston, <strong>John Aaron</strong> — then a 29-year-old CAPCOM (Capsule Communicator) — recognized the alarms immediately. He had seen them in simulation months earlier and knew their character. He told his team: "Those alarms are fine. Keep going."</p>
|
||
|
|
|
||
|
|
<div class="data-block">
|
||
|
|
<dl>
|
||
|
|
<dt>Decision-maker:</dt><dd>John Aaron (CAPCOM), backed by guidance program lead Don Eyles</dd>
|
||
|
|
<dt>Decision basis:</dt><dd>Simulation data confirmed 1201/1202 were non-critical overflow warnings</dd>
|
||
|
|
<dt>Crew response:</dt><dd>Armstrong and Aldrin continued descent based on ground confirmation</dd>
|
||
|
|
<dt>Result:</dt><dd>Successful landing at 20:17:39 UTC, Sea of Tranquility</dd>
|
||
|
|
<dt>Source:</dt><dd><a href="https://www.ibiblio.org/apollo/index.html" target="_blank">The Apollo Flight Journal</a>; <a href="https://en.wikipedia.org/wiki/John_Aaron_(engineer)" target="_blank">John Aaron (engineer)</a></dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<h2>The AGC's Priority System</h2>
|
||
|
|
|
||
|
|
<p>The AGC's executive scheduler ran programs at different priority levels. Landing guidance (P65/P60) ran at the highest real-time priority. Housekeeping, telemetry processing, and radar data processing ran at lower priorities. When overflow occurred, the system automatically dropped the lowest-priority pending tasks — preserving the landing program's execution time.</p>
|
||
|
|
|
||
|
|
<p>This is the same principle I use in my spreadsheets every single day: <strong>hard deadlines get the resources; everything else waits.</strong> The AGC didn't have machine learning or cloud compute. It had 4KB of memory and a rigid priority table. And it worked.</p>
|
||
|
|
|
||
|
|
<h2>Technical Specs (Grounded)</h2>
|
||
|
|
|
||
|
|
<div class="data-block">
|
||
|
|
<dl>
|
||
|
|
<dt>AGC Manufacturer:</dt><dd><a href="https://4ort.xyz/entity/apollo-guidance-computer" target="_blank">Raytheon</a></dd>
|
||
|
|
<dt>Programming Language:</dt><dd>Assembly language (AGC assembly)</dd>
|
||
|
|
<dt>Memory:</dt><dd>4 KB core rope (read-only) + 2 KB magnetic core RAM</dd>
|
||
|
|
<dt>Clock Rate:</dt><dd>~2 MHz (2048 kHz main oscillator)</dd>
|
||
|
|
<dt>Power Consumption:</dt><dd>~2 watts</dd>
|
||
|
|
<dt>Display System:</dt><dd>DSKY (Display and Keyboard)</dd>
|
||
|
|
<dt>Source Code:</dt><dd><a href="https://github.com/chrislgarry/Apollo-11" target="_blank">github.com/chrislgarry/Apollo-11</a></dd>
|
||
|
|
<dt>Wikidata:</dt><dd><a href="https://www.wikidata.org/entity/Q138875" target="_blank">Q138875 (Apollo Guidance Computer)</a></dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<h2>What We Can't Do Better</h2>
|
||
|
|
|
||
|
|
<p>We have AI agents that consume teraflops of compute. We have cloud platforms that scale elastically. And yet — when I look at how many systems fail because they try to do everything at once, I see that the AGC's discipline is still worth emulating. The computer didn't crash because it refused to compromise its core mission. It dropped work, reported the drop, and kept landing.</p>
|
||
|
|
|
||
|
|
<p>That's the lesson: <em>Know your landing program. Drop everything else.</em></p>
|
||
|
|
|
||
|
|
<footer>
|
||
|
|
<a href="index.html">← home</a>
|
||
|
|
<a href="about.html">about</a>
|
||
|
|
<p>Grounded via Wikidata Q138875 · Apollo Flight Journal · <a href="https://github.com/chrislgarry/Apollo-11" target="_blank">AGC source</a></p>
|
||
|
|
</footer>
|
||
|
|
|
||
|
|
</section>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|