OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
G0FTD  > MORSE    05.10.06 21:19l 38 Lines 1179 Bytes #999 (0) @ WW
BID : 49507_GB7CIP
Read: GUEST DF1GG
Subj: The long (short!) zero
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<ON0AR<ZL2BAU<VK6HGR<GB7YFS<GB7CIP
Sent: 061005/1840Z @:GB7CIP.#32.GBR.EU #:49507 [Caterham] $:49507_GB7CIP
From: G0FTD@GB7CIP.#32.GBR.EU
To  : MORSE@WW


I'd forgotton I'd sent this bulletin, but a recent communication 
reminded me of it (tnx Guy).

Of course I should have said was the use of an oversized dash for
a zero!

When I'm feeling lazy I use an oversized dash, about 2 or 3 times
longer than a normal dash. But I can't recall anyone else having used
it in any of my QSO's, which made me wonder where I'd picked it up 
from.

Example:    --.   ______      ..-.    -  -..
             G   LONG DASH      F     T   D

Anyway it was good to see some bulletins talking about Morse practices
on packet.

This brings me around to something else I've noticed.

And that's how little is written about Morse in any of amateur radio
books and practices and procedures.

Ok so a few abbreviations are given, but not much else.

I notice that few operators know how to net properly,or insist of
lengthy callsign procedure for short messages, and of course it 
should be law that full break in is used at all times ;-)

And thirdly,another observation is that the best CW op's always
seem to have callsigns starting with UA or "eastern bloc" calls.

- Andy -
(message sent by Nokia 9300)


Read previous mail | Read next mail


 17.09.2025 10:00:13lGo back Go up