Return-Path: Received: (qmail 60375 invoked from network); 20 Dec 2004 18:25:51 -0000 Received: from unknown (HELO ptb-spamcore02.plus.net) (192.168.71.3) by ptb-mailstore02.plus.net with SMTP; 20 Dec 2004 18:25:51 -0000 Received: from mailnull by ptb-spamcore02.plus.net with spamcore-l-b (Exim 4.32; FreeBSD) id 1CgSIf-000HOL-VB for dave@picks.force9.co.uk; Mon, 20 Dec 2004 18:30:30 +0000 Received: from [192.168.67.1] (helo=ptb-mxcore01.plus.net) by ptb-spamcore02.plus.net with esmtp (Exim 4.32; FreeBSD) id 1CgSIf-000HOI-Sj for dave@picks.force9.co.uk; Mon, 20 Dec 2004 18:30:29 +0000 Received: from post.thorcom.com ([193.82.116.20]) by ptb-mxcore01.plus.net with esmtp (Exim 4.30; FreeBSD) id 1CgSEA-0000p0-Oh for dave@picks.force9.co.uk; Mon, 20 Dec 2004 18:25:50 +0000 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1CgSDT-0001X7-9a for rs_out_1@blacksheep.org; Mon, 20 Dec 2004 18:25:07 +0000 Received: from [193.82.116.30] (helo=relay.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1CgSDS-0001Wy-TE for rsgb_lf_group@blacksheep.org; Mon, 20 Dec 2004 18:25:06 +0000 Received: from mailout03.sul.t-online.com ([194.25.134.81]) by relay.thorcom.net with esmtp (Exim 4.41) id 1CgSDP-0007TY-FC for rsgb_lf_group@blacksheep.org; Mon, 20 Dec 2004 18:25:06 +0000 Received: from fwd03.aul.t-online.de by mailout03.sul.t-online.com with smtp id 1CgSDK-0001LG-00; Mon, 20 Dec 2004 19:24:58 +0100 Received: from (VyhCjiZUoeoSEWYXgDLTOKDGYXSdw4xXBsg-eg+jylrFpTwTrx9zEe@[217.251.199.247]) by fwd03.sul.t-online.com with smtp id 1CgSCx-0vTlq40; Mon, 20 Dec 2004 19:24:35 +0100 From: jannsen <0482183881-0001@t-online.de> To: rsgb_lf_group@blacksheep.org References: <004901c4e445$37d68ae0$fe79a8c0@PCVONWALTER> <1Cg2XO-0ls9uC0@fwd02.sul.t-online.com> <418367773.20041219161716@web.de> X-Mailer: T-Online eMail 2.34 MIME-Version: 1.0 Date: Mon, 20 Dec 2004 19:24:35 +0100 Message-ID: <1CgSCx-0vTlq40@fwd03.sul.t-online.com> X-ID: VyhCjiZUoeoSEWYXgDLTOKDGYXSdw4xXBsg-eg+jylrFpTwTrx9zEe X-TOI-MSGID: 28de9a26-3062-4521-95eb-d8aa6e7a0a58 X-SPF-Result: relay.thorcom.net: 194.25.134.81 is neither permitted nor denied by domain of t-online.de X-Spam-Score: 2.7 (++) X-Spam-Report: autolearn=no,FROM_ENDS_IN_NUMS=0.869,FROM_STARTS_WITH_NUMS=1.574,SARE_HEAD_XID=0.305 Subject: Re: LF: MW Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: ** X-Spam-Status: No, hits=2.4 required=5.0 tests=FROM_ENDS_IN_NUMS, FROM_STARTS_WITH_NUMS autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Spam-Filtered: by PlusNet SpamCORE (v3.00) Michael Oexner schrieb: > Hi Uwe, Walter & list: > > > I'm attaching a list with NDBs that are listed on 440 kHz +/- 2 kHz. > > FW or FA is "negative keying" of the Polish NDB DRE on 440 kHz. > > The term "negative keying" describes a strange situation where the > Morse code identification of an NDB becomes "inverted". This can > produce some strange sounding IDs, and can often be characterized by > uneven spacing, or a very long dash, which appears between the > callsigns. Many of the ones that are frequently heard are located in > Eastern Europe, though negative calls have also been heard from > Western European countries from time to time. > > "Negative keying" actually results from a drop (reduction) of the NDB > transmitter's carrier level (amplitude) during the time when the > transmitter is being keyed, i. e. transmitting the NDB's Morse code > identification. Hence the most likely spot to find negative keying is > to tune directly to the NDB's carrier frequency and operating the > receiver in narrow CW mode. > > If you want to translate between positive and negative callsigns (or > vice versa), you might want to try the following procedure: > > - Inside each Morse code character, the short period of silence > between two adjacent "dits" or "dahs" or "dit-dahs" or "dah-dits" > becomes a "dit". > > - A "dah" becomes a character separator. > > - The long period of silence (character separator) between two Morse > code characters becomes a "dah". > > - The very long silence between two consecutive IDs of the NDB becomes > a very long dash. > > Below I've tried to sketch a little graphical representation for some > of the more frequently heard NDBs that are producing negative keying. > The vertical line | indicates a character separator. Please have a > look at the following examples: > > C F > - . - .|. . - . > |. .|. - . .|. > I L E > > G R U > - - .|. - .|. . - > |.|. - .|. - . .| > E R L > > and finally: > > D R E > - . .|. - .|. > |. . - .|. - | > F A > > > > vy 73 + gd DX, > > Michael Hi Michael, thanks for the efforts you made explaining us the effect of negative keying. best regards Uwe/dj8wx