doc: Move pad beeps table to usage chapter

This places all of the sound information in one place.

Signed-off-by: Keith Packard <keithp@keithp.com>

2 files changed, 80 insertions, 33 deletions

diff --git a/doc/system-operation.inc b/doc/system-operation.inc
index dd8d7d02..4503f525 100644
--- a/doc/system-operation.inc
+++ b/doc/system-operation.inc
@@ -59,39 +59,8 @@
 		memory, the flight computer will emit a warbling tone (much
 		slower than the “no continuity tone”)
 
-		Here's a summary of all of the “pad” and “idle” mode indications.
-
-		.Pad/Idle Indications
-		[options="header",cols="1,1,3"]
-		|====
-		|Name		|Beeps		|Description
-
-		|Neither
-		|brap
-		|No continuity detected on either apogee or main igniters.
-
-		|Apogee
-		|dit
-		|Continuity detected only on apogee igniter.
-
-		|Main
-		|dit dit
-		|Continuity detected only on main igniter.
-
-
-		|Both
-		|dit dit dit
-		|Continuity detected on both igniters.
-
-
-		|Storage Full
-		|warble
-		|On-board data logging storage is full. This will
-		 not prevent the flight computer from safely
-		 controlling the flight or transmitting telemetry
-		 signals, but no record of the flight will be
-		 stored in on-board flash.
-		|====
+		See <<_understanding_beeps>> for a summary of all of
+		the audio signals used.
 
 		Once landed, the flight computer will signal that by emitting
 		the “Landed” sound described above, after which it will beep
diff --git a/doc/usage.inc b/doc/usage.inc
index b2ab0c27..caccc168 100644
--- a/doc/usage.inc
+++ b/doc/usage.inc
@@ -124,6 +124,84 @@
 		|Error detected during sensor calibration.
 		|====
 
+		Here's a summary of all of the Pad and Idle mode
+		indications. In Idle mode, you'll hear one of these
+		just once after the two short dits indicating idle
+		mode. In Pad mode, after the dit dah dah dit
+		indicating Pad mode, you'll hear these once every five
+		seconds.
+
+		.Pad/Idle Indications
+		[options="header",cols="1,1,3"]
+		|====
+		|Name		|Beeps		|Description
+
+		|Neither
+		|brap
+		|No continuity detected on either apogee or main igniters.
+
+		|Apogee
+		|dit
+		|Continuity detected only on apogee igniter.
+
+		|Main
+		|dit dit
+		|Continuity detected only on main igniter.
+
+
+		|Both
+		|dit dit dit
+		|Continuity detected on both igniters.
+
+
+		|Storage Full
+		|warble
+		|On-board data logging storage is full. This will
+		 not prevent the flight computer from safely
+		 controlling the flight or transmitting telemetry
+		 signals, but no record of the flight will be
+		 stored in on-board flash.
+		|====
+
+		For devices with a radio transmitter, in addition to
+		the digital and APRS telemetry signals, you can also
+		receive audio tones with a standard amateur
+		70cm FM receiver. While on the pad, you will hear
+		igniter status once every five seconds.
+
+		.Pad Radio Indications
+		[options="header",cols="1,1,3"]
+		|====
+		|Name		|Beeps		|Description
+
+		|Neither
+		|½ second tone
+		|No continuity detected on either apogee or main igniters.
+
+		|Apogee
+		|dit
+		|Continuity detected only on apogee igniter.
+
+		|Main
+		|dit dit
+		|Continuity detected only on main igniter.
+
+
+		|Both
+		|dit dit dit
+		|Continuity detected on both igniters.
+
+		|====
+
+		During ascent, the tones will be muted to allow the
+		telemetry data to consume the full radio bandwidth.
+
+		During descent and after landing, a ½ second tone will
+		be transmitted every five seconds. This can be used to
+		find the rocket using RDF techniques when the signal
+		is too weak to receive GPS information via telemetry
+		or APRS.
+
 	=== Turning On the Power
 
 		Connect a battery and power switch and turn the switch