Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-da02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 82BBF38000082; Wed, 6 Mar 2013 06:11:24 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UDCEj-0004a3-Jm for rs_out_1@blacksheep.org; Wed, 06 Mar 2013 11:10:17 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UDCEi-0004Zn-Cu for rsgb_lf_group@blacksheep.org; Wed, 06 Mar 2013 11:10:16 +0000 Received: from mail-ee0-f43.google.com ([74.125.83.43]) by relay1.thorcom.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77) (envelope-from ) id 1UDCEg-0005Ye-6Y for rsgb_lf_group@blacksheep.org; Wed, 06 Mar 2013 11:10:15 +0000 Received: by mail-ee0-f43.google.com with SMTP id c50so5603072eek.2 for ; Wed, 06 Mar 2013 03:09:52 -0800 (PST) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:from:to:references:in-reply-to:subject:date :mime-version:content-type:x-priority:x-msmail-priority:importance :x-mailer:x-mimeole; bh=QECtsTem1fU2yc+vygwskKNgGChJyLInwQs/vOERwAY=; b=xkPVzpCrXkRcDPwm6q4pqE9Bb00L9N0zy2U7EBhPvGEj6TU6Iz6SB9Yri5Nc+G18yH COG8Ghun/7IoNjfmvBaWrOak9oJYPCT0zulSD/QoVP3tsjJvJh2XckfLmPSz43OS+PJf J02Uu5+m/YMoIGrYqtUTKpJN0xnVEAfsU1DE7ysz2djExwNK68jKPfvqwOejvllUuTB8 TL8XvnzB7EJ7b2y5bfOYMQsfUuGP2rf3uyPDf/jhFKa/VbUDZ8SKf/1R4WwC00BrkMCN lorBIApSCVX79cC451+I9l9Hrew/m+zjhJWl2NwsrJjodcoJUnlLAsMBi1x6vx6sJUGi GU7Q== X-Received: by 10.14.225.72 with SMTP id y48mr60357582eep.45.1362568192534; Wed, 06 Mar 2013 03:09:52 -0800 (PST) Received: from PcMinto (dhcp-077-248-065-057.chello.nl. [77.248.65.57]) by mx.google.com with ESMTPS id q42sm41845766eem.14.2013.03.06.03.09.51 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 06 Mar 2013 03:09:51 -0800 (PST) Message-ID: From: Minto Witteveen To: References: <51371E11.6020502@psk31.plus.com> In-Reply-To: <51371E11.6020502@psk31.plus.com> Date: Wed, 6 Mar 2013 12:09:50 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3555.308 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308 X-Spam-Score: -0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hmm might this be because ‘in the old days’ (amateur) RTTY was done with the rig in LSB mode using AFSK? With mark at 2125 Hz and space at 2295 hz and mark being the idling position, when using LSB the actual transmitted frequencies would be ‘swapped’ (reversed) So MTTY seems to assume rig at USB, while all (all?) others assume LSB… [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [74.125.83.43 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (minto.witteveen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 13abe497adcf17a4e25c5e2a2ff79111 Subject: Re: LF: RTTY Protocol Content-Type: multipart/alternative; boundary="----=_NextPart_000_0063_01CE1A63.81007B60" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME 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-aol-global-disposition: G X-AOL-SCOLL-AUTHENTICATION: mtain-da02.r1000.mx.aol.com ; domain : gmail.com DKIM : pass x-aol-sid: 3039ac1d404a5137245c5033 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_0063_01CE1A63.81007B60 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hmm might this be because =E2=80=98in the old days=E2=80=99 (amateur) = RTTY was done with the rig in LSB mode using AFSK? With mark at 2125 Hz and space at 2295 hz and mark being the idling = position, when using LSB the actual transmitted frequencies would be = =E2=80=98swapped=E2=80=99 (reversed)=20 So MTTY seems to assume rig at USB, while all (all?) others assume = LSB=E2=80=A6 Still, Stefan and I seem to do RTTY wrong (i.e. amateur reversed, as in = AFSK on USB). I just checked my PIC code and I have mark at high = (DDS_BASE + 85 Hz) and space at low (DDS_BASE). This then gets swapped = around by fldigi because I listen (via websdr) in USB=E2=80=A6 This = explains why fldigi decodes me (and Stefan) just right. This is of course based on the assumption that =E2=80=98right=E2=80=99 = means AFSK on LSB, that the space must be the high tone AND the low(est) = frequency. What _is_ the consensus (if any)? 73=E2=80=99s Minto pa3bca -------------------------------------------------------------------------= - Ceterum censeo Carthaginem delendam esse From: g3zjo=20 Sent: Wednesday, March 06, 2013 11:44 To: rsgb_lf_group@blacksheep.org=20 Subject: LF: RTTY Protocol Graham Just confirmed by test, MMTTY is backwards compared to all other = Software. Others idle on the high tone MMTTY idles on the low, unless = the REV is pressed. >From Wiki the upper tone used for idle condition (MARK).=20 Another site says You also have to switch the correct phase position (whether the lower or = higher frequency carrier in frequency modulation corresponds to "Mark" = or "space"). Mind you a Ham education site on the subject says. Remember that bfo=E2=80=99s help filter out the carrier waves to allow = for the original signals to come through Eddie ------=_NextPart_000_0063_01CE1A63.81007B60 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hmm might this be because =E2=80=98in the old = days=E2=80=99  (amateur) RTTY was done with = the rig in=20 LSB mode using AFSK?
With mark at 2125 Hz and space at 2295 hz and = mark being=20 the idling position, when using LSB the actual transmitted frequencies = would be=20 =E2=80=98swapped=E2=80=99 (reversed)
So MTTY seems to assume rig at = USB, while all (all?)=20 others assume LSB=E2=80=A6

Still, Stefan and I seem to do RTTY wrong (i.e. amateur = reversed,=20 as in AFSK on USB).  I = just checked=20 my PIC code and I have mark at high (DDS_BASE + 85 Hz) and space at low=20 (DDS_BASE). This then gets swapped around by fldigi because I listen = (via=20 websdr) in USB=E2=80=A6 This explains why fldigi decodes me (and Stefan) = just=20 right.

This is of course based on the assumption that = =E2=80=98right=E2=80=99 means AFSK=20 on LSB, that the space must be the high tone AND the low(est) = frequency.
What=20 _is_ the consensus (if any)?

73=E2=80=99s Minto = pa3bca

 
-------------------------------------------------------------------= -------
Ceterum=20 censeo Carthaginem delendam esse
 
From: g3zjo
Sent: Wednesday, March 06, 2013 11:44
Subject: LF: RTTY Protocol
 
Graham

Just = confirmed by=20 test, MMTTY is backwards compared to all other Software. Others idle on = the high=20 tone MMTTY idles on the low, unless the REV is=20 pressed.


From Wiki
the upper tone used = for=20 idle condition (MARK).

Another site = says
You=20 also have to switch the correct phase position (whether the lower or = higher=20 frequency carrier in frequency modulation corresponds to "Mark" or=20 "space").

Mind you a Ham education site on the subject=20 says.
Remember that bfo=E2=80=99s help filter out the carrier = waves to allow for=20 the original signals to come through

Eddie

 ------=_NextPart_000_0063_01CE1A63.81007B60--