Re: morse abbrev. past & future

---------

From: Mike J Pulley (Mike_J_Pulley@ccm.ch.intel.com)
Date: Thu Dec 15 1994 - 19:53:15 EST


Text item:

     I've spent hours on a TDD (telephone device for the deaf) talking
     with friends who are hearing impaired. You would recognize the
     prosigns, but I gather they originated with the old landline
     Morse circuits rather than radio CW.
     
     First, recognize the historical roots of TDDs. The first
     instruments were old TTY floor models refurbished and donated by
     the Telephone Pioneers as a public service to the deaf community.
      The TTY protocols derived from the technological predecessor,
     the Morse wire. My point is CW shares the same grandpappy with
     TDDs, hence the family likeness.
     
     When modern solid state TDDs appeared, there was no reason to
     change the protocol and prosigns. Most of the conversation is
     plain English; Morse abbreviations are uncommon and confusing to
     most folks. Prosigns are only necessary to quickly trade turns
     sending and to close the conversation without rambling on nor
     hanging up prematurely.
     
        GA - Go Ahead. Sent at the end of each transmission. Serves
        the same purpose as K on CW.
        
        SK - I have nothing more; end of exchange. Both parties take
        turns sending this right at the end with minimum comment. SK
        is traditionally sent twice -- "SK SK". I think of "silent
        key", but that's a mental crutch, not historical origin.
        
        When one party is ready to close, he/she sends "GA TO SK" to
        indicate the other person can either make more comments or
        close with "SK SK".
        
        I suppose we use "SK" on CW, but "dit dit" does the job most
        of the time.
     
     Regards,
     
     -- Mike, WB4ZKA

______________________________ Reply Separator _________________________________
Subject: morse abbrev. past & future
Author: owner-qrp-l@netcom.com at Internet_Gateway
Date: 12/15/94 3:14 PM

<snip!>

This thread brings up something that has been tickling my mind for a week
or so. On a recent repeat of the show "Law and Order" the printed text of
a conversation conducted by telephone devices for the deaf was entered
into evidence. One of the characters points out that a party in the
conversation typed SK SK over and over to indicate that he/she was
intending to hang up. I was wondering if anyone had any experience with
TDDs, and if, as I suspect, their prosigns derived from those of the
international morse code?

<snip!>

72,

Bruce G. Robertson Dept. of Classics, U. of T.

Text item: External Message Header

The following mail header is for administrative use
and may be ignored unless there are problems.

***IF THERE ARE PROBLEMS SAVE THESE HEADERS***.

Precedence: list
Sender: owner-qrp-l@netcom.com
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0
Message-Id: <Pine.3.89.9412151319.B20276-0100000@blues.epas.utoronto.ca>
To: qrp list <qrp-l@netcom.com>
Subject: morse abbrev. past & future
>From: Bruce Robertson <brucerob@epas.utoronto.ca>
Date: Thu, 15 Dec 1994 13:34:48 -0500 (EST)
Received: by blues.epas.utoronto.ca (931110.SGI/930416.SGI)
        for @jazz.epas.utoronto.ca:qrp-l@netcom.com id AA22192; Thu, 15 Dec 94 13:34:49
Received: from blues.epas.utoronto.ca by jazz.epas.utoronto.ca via SMTP (931110.
        for qrp-l@netcom.com id AA15106; Thu, 15 Dec 94 13:34:54 -0500
Received: from jazz.epas.utoronto.ca by mail3.netcom.com (8.6.9/Netcom)
        id KAA14018; Thu, 15 Dec 1994 10:35:45 -0800
Received: by mail3.netcom.com (8.6.9/Netcom)
        id KAA14185; Thu, 15 Dec 1994 10:36:31 -0800
Received: from mail3.netcom.com by hermes.intel.com (5.65/10.0i); Thu, 15 Dec 94
Received: from hermes.intel.com by relay.jf.intel.com with smtp
        (Smail3.1.28.1 #2) id m0rIPK4-000twpC; Thu, 15 Dec 94 15:10 PST


Search QRP-L Archives

[ QRP-L Archive | ]
[ 1993 | 1994 | 1995 | 1996 | 1997 | 1998 | 1999 | 2000 ]

---------

This archive was generated by hypermail 2b29 on Fri Jun 02 2000 - 11:27:14 EDT

kd4ab@kd4ab.org