RE: [PSUBS-MAILIST] Emergency tapping code...

[Ray Keefer <Ray.Keefer@Sun.COM>]

Hi,

I have been going through a week's worth of vacation e-mail and mulling over my
response to the original mail. Well here goes:

Why not learn Morse code? More universal?

Posting a copy inside your sub is useless unless the guys on the outside
know your code. Post a copy on the outside hull, give copies to your
support team and who ever you left your dive plan with.

What does "Tapping: 3.3.3" sound like? Is that three taps, pause,
three taps, pause, and three more taps? How long is the pause before it means
a new signal? How long is the pause between taps and series of taps?

Have all tapping codes repeated back by receiver and the original sender
confirming with either a yes or no before any action takes place.

Codes like "Communication closing procedure" surely means that the
trappee, err tappee, inside the sub and the guys outside know the
details of the procedure already layed out in your operational manual.
Tapping the code just means we are going to initiate procedure X.

One axiom is that no plan survives the initiation of battle. If you don't
have a predefined procedure with its corresponding code it is really 
going to be tedious tapping out a new procedure even with Morse code.

I would use tapping codes as an alternative. Part of a multi-layered 
communications protocol. Starting with radio, underwater telephone, writing
slates at the view port, sign language (both diver's and American Sign
Language), face mask to hull, to tapping.

Regards,
Ray

> From: "Gregory Snyder" <gsnyder@mn.rr.com>
> To: <personal_submersibles@psubs.org>
> Subject: RE: [PSUBS-MAILIST] Emergency tapping code...
> Date: Mon, 1 Jul 2002 20:50:37 -0500
> Content-Transfer-Encoding: 7bit
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
> Importance: Normal
> 
> Awesome - 
> Hey Ray -
> This needs to be posted with the White papers!
> Here, Here -
> greg
> 
> -----Original Message-----
> From: owner-personal_submersibles@psubs.org
> [mailto:owner-personal_submersibles@psubs.org] On Behalf Of Ian
> Roxborough
> Sent: Monday, July 01, 2002 12:07 PM
> To: personal_submersibles@psubs.org
> Subject: [PSUBS-MAILIST] Emergency tapping code...
> 
> Hi,
> 
> while we're (always) on a safety kick, I thought I'd post something
> about "Standard bell emergency tapping code".  Something
> that might be handy to have post in a any submersible.
> 
>   Tapping: 3.3.3
>   Meaning: Communication opening procedure (inside and out)
> 
>   Tapping: 1
>   Meaning: Yes or affirmative or agreed.
> 
>   Tapping: 3
>   Meaning: No or negative or disagreed.
> 
>   Tapping: 2.2
>   Meaning: Please repeat.
> 
>   Tapping: 2
>   Meaning: Stop.
> 
>   Tapping: 5
>   Meaning: Have you got a seal?
> 
>   Tapping: 6
>   Meaning: Stand by to be pulled up.
> 
>   Tapping: 1.2.1.2
>   Meaning: Get ready for through water transfer.
>            (open your hatch)
> 
>   Tapping: 2.3.2.3
>   Meaning: You will NOT release your ballasts.
> 
>   Tapping: 4.4
>   Meaning: Do release your ballast in 30 minutes from now
> 
>   Tapping: 1.2.3
>   Meaning: Do increase your pressure.
> 
>   Tapping: 3.3.3
>   Meaning: Communication closing procedure.
> 
> 
> I think I'll put a water proof version clearly posted in
> my sub, when I get one...  it could come in useful one day.
> 
> Ian.
> 
> -- 
> The moon ate the sun on Monday and it was an awsome sight to see.
>