Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-de04.r1000.mx.aol.com (Internet Inbound) with ESMTP id 2C68C380000A9; Wed, 6 Mar 2013 08:15:07 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UDDr6-0005ZN-44 for rs_out_1@blacksheep.org; Wed, 06 Mar 2013 12:54:00 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UDDr5-0005ZE-AT for rsgb_lf_group@blacksheep.org; Wed, 06 Mar 2013 12:53:59 +0000 Received: from mail-ee0-f54.google.com ([74.125.83.54]) by relay1.thorcom.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77) (envelope-from ) id 1UDDr2-0006Ap-Ov for rsgb_lf_group@blacksheep.org; Wed, 06 Mar 2013 12:53:58 +0000 Received: by mail-ee0-f54.google.com with SMTP id c41so5734790eek.41 for ; Wed, 06 Mar 2013 04:53:36 -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=DcbEhjuKvRQSnVcDDHtILLlT/cWNkHdatNwRuBMARPU=; b=MdwUYPWpamhm4EslDYU2Ct8VQyOz5V+f/OVfeHQ9kJ6zF//bU5zBQAIiaEwW+V00k5 J7XWum86+GHoFG568lg+Pe79vmUCRonUa/byFPA+bbuBe23wJh6UFdg7uLq9tsb1k8dq alP3a2+ctL4lsmGex+5RBVvnqLo3dwW8uJPvIOHe0sEzOu1GmdyR0h6ooUsZ/hGI/srf gUYfjb7sDG+UXi9x6UsWdzL+65AsUvBpIFShCqLjQ3uoxGiBm1mX3MjA35ieraRIRsci sW2IgokMvQfMO6LOUG58CKXZCZTIa9FBNTL4W/E3ai567rqNnvXpd3WD4AHure11DNLK 6aiQ== X-Received: by 10.14.216.2 with SMTP id f2mr82002471eep.44.1362574415867; Wed, 06 Mar 2013 04:53:35 -0800 (PST) Received: from PcMinto (dhcp-077-248-065-057.chello.nl. [77.248.65.57]) by mx.google.com with ESMTPS id h5sm42324426eem.1.2013.03.06.04.53.34 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 06 Mar 2013 04:53:35 -0800 (PST) Message-ID: <54D27154B86344358E4FE30D6D7C31C0@PcMinto> From: Minto Witteveen To: References: <51371E11.6020502@psk31.plus.com> <51373420.9020002@psk31.plus.com> In-Reply-To: <51373420.9020002@psk31.plus.com> Date: Wed, 6 Mar 2013 13:53:33 +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: Hi Eddie, Yes, after I sent the message I (re)checked and found that I switched mark and space frequencies (due to some obscure reference I used. serves me well for not checking). So the consensus is * that mark is the higher (TX) frequency and also the frequency that you are operating on * space is the lower (TX) frequency. [...] 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.54 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: 2728faa227459cbf7dd0051df2cd1c1d Subject: LF: Re: RTTY Protocol Content-Type: multipart/alternative; boundary="----=_NextPart_000_009D_01CE1A71.FE36BD70" 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-de04.r1000.mx.aol.com ; domain : gmail.com DKIM : fail x-aol-sid: 3039ac1d40cc5137415b2e38 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_009D_01CE1A71.FE36BD70 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Eddie, Yes, after I sent the message I (re)checked and found that I switched = mark and space frequencies (due to some obscure reference I used. serves = me well for not checking). So the consensus is=20 * that mark is the higher (TX) frequency and also the frequency that you = are operating on * space is the lower (TX) frequency. And as you noticed Stefan and I use the right shift / mode. Thanks for clearing this up. 73=E2=80=99s Minto pa3bca -------------------------------------------------------------------------= - Ceterum censeo Carthaginem delendam esse From: g3zjo=20 Sent: Wednesday, March 06, 2013 13:18 To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: RTTY Protocol Hi Minto On 06/03/2013 11:09, Minto Witteveen wrote:=20 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? Yes, hence the confusion. 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 No the opposite MMTTY Assumes (Demands) (Instructs) LSB.=20 All others that I have tested use the modern convention of USB for Digi = Modes and the Mark is high 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 is the same as fldigi 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. No swap it is already correct.? 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)? This from the author of MMTTY and in the Help :- You should understand the concepts of mark and shift before operating = RTTY.=20 =20 Mark, Shift, and Space Think of a RTTY signal as a continuous, constant -amplitude, = suppressed-carrier signal that shifts back and forth between two distinct frequencies. RTTY = signals can also be seen as a combination of two CW carriers at different RF = frequencies, only one of which is on at any given time. The pattern in which the two = tones are transmitted is what codes the letters.=20 =20 One of these RF frequencies is known as the mark frequency; the other RF = frequency is known as the space frequency. The difference between Mark and space = is known as the shift. For amateur radio, the shift has been somewhat = standardized at 170 Hz. It is customary to refer to the mark frequency as the frequency = you are operating on. For example, if you say you are transmitting on 14085.00 = kHz, that means your mark frequency is 14085.00 kHz and your space frequency is = 170 Hz away.=20 =20 This brings up a question: Is the space frequency shifted 170 Hz. below = the mark frequency, or 170 Hz. above the mark frequency? The answer to this = question is established by convention. The ham radio convention is to operate RTTY = on lower sideband, and to call one carrier the mark tone, and the other carrier, = shifted 170 Hz. (0.170 KHz.) below the mark tone frequency, the space tone. A = shift above the mark frequency is called a reverse-shift.=20 =20 Where Are the Tones?=20 =20 The standard for posting information on the location of a RTTY station = is to post the mark frequency, but many posts are in error. When you operate AFSK = using a standard ham transceiver, and use LSB mode, things get even more = complicated. =20 Here is an outline of what is happening:=20 =20 You are operating AFSK, LSB (transmit and receive). The transceiver = frequency display shows the location of your suppressed carrier. That is the = location where a tone of 0 Hz. would be transmitted.=20 The transceiver shows a frequency of 14080 kHz.=20 You have MMTTY set to use the HAM defaults, with a mark frequency of = 2125 Hz. (2.125 KHz.) and a shift of 170 Hz. (0.170KHz.).=20 You want to tell someone where your mark frequency is located, or you = tuned in a station at this location, and you want to post its mark frequency.=20 The mark frequency you are receiving is actually 14080 KHz. - 2.125 KHz. =3D 14077.875 KHz. This last number is what you should post if you want = to post the mark frequency on a DX Cluster.=20 Your space frequency is shifted down another 0.170 KHz. from your mark = frequency, so your space frequency is on 14077.875 KHz. - 0.170 KHz. =3D 14077.705 = KHz.=20 73 Eddie 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_009D_01CE1A71.FE36BD70 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Eddie,
 
Yes, after I sent the message I (re)checked and found that I = switched mark=20 and space frequencies (due to some obscure reference I used. serves me = well for=20 not checking).
 
So the consensus is
* that mark is the higher (TX) frequency and also the frequency = that you=20 are operating on
* space is the lower (TX) frequency.
 
And as you noticed Stefan and I use the right shift / mode.
Thanks for clearing this up.
 
73=E2=80=99s Minto pa3bca
 
 
-------------------------------------------------------------------= -------
Ceterum=20 censeo Carthaginem delendam esse
 
From: g3zjo
Sent: Wednesday, March 06, 2013 13:18
Subject: Re: LF: RTTY Protocol
 
Hi=20 Minto

On 06/03/2013 11:09, Minto Witteveen wrote:=20

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?

Yes,=20 hence the confusion.

With mark at 2125 Hz and space at 2295 hz and mark = being the=20 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

No the=20 opposite MMTTY Assumes (Demands) (Instructs) LSB.

All others = that I have=20 tested use the modern convention of USB for Digi Modes and the Mark is = high

Still, Stefan and I seem to do RTTY wrong (i.e. amateur = reversed,=20 as in AFSK on USB).  I = just=20 checked my PIC code and I have mark at high (DDS_BASE + 85 Hz) and = space at=20 low (DDS_BASE).

This = is=20 the  same as fldigi

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.

No swap it is = already=20 correct.?

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)=20 frequency.
What _is_ the consensus (if=20 any)?

This from the = author of=20 MMTTY and in the Help :-

You should understand the concepts of = mark and=20 shift before operating RTTY.
 
Mark, Shift, and = Space

Think=20 of a RTTY signal as a continuous, constant -amplitude,=20 suppressed-carrier
signal that shifts back and forth between two = distinct=20 frequencies. RTTY signals
can also be seen as a combination of two CW = carriers at different RF frequencies,
only one of which is on at any = given=20 time. The pattern in which the two tones
are transmitted is what = codes the=20 letters.
 
One of these RF frequencies is known as the mark = frequency; the other RF frequency
is known as the space frequency. = The=20 difference between Mark and space is known
as the shift. For amateur = radio,=20 the shift has been somewhat standardized at
170 Hz. It is customary = to refer=20 to the mark frequency as the frequency you are
operating on. For = example, if=20 you say you are transmitting on 14085.00 kHz, that
means your mark = frequency=20 is 14085.00 kHz and your space frequency is 170 Hz away.
  =
This=20 brings up a question: Is the space frequency shifted 170 Hz. below the=20 mark
frequency, or 170 Hz. above the mark frequency? The answer to = this=20 question is
established by convention. The ham radio convention is to = operate=20 RTTY on lower
sideband, and to call one carrier the mark tone, and = the other=20 carrier, shifted
170 Hz. (0.170 KHz.) below the mark tone frequency, = the=20 space tone. A shift above
the mark frequency is called a = reverse-shift.=20
 
Where Are the Tones?
 
The standard for = posting=20 information on the location of a RTTY station is to post
the mark = frequency,=20 but many posts are in error. When you operate AFSK using a
standard = ham=20 transceiver, and use LSB mode, things get even more=20 complicated.
 
Here is an outline of what is happening: =
 =20
You are operating AFSK, LSB (transmit and receive). The transceiver=20 frequency
display shows the location of your suppressed carrier. That = is the=20 location where
a tone of 0 Hz. would be transmitted.
The = transceiver=20 shows a frequency of 14080 kHz.
You have MMTTY set to use the HAM = defaults,=20 with a mark frequency of 2125 Hz.
(2.125 KHz.) and a shift of 170 Hz. = (0.170KHz.).
You want to tell someone where your mark frequency is = located,=20 or you tuned in a
station at this location, and you want to post its = mark=20 frequency.
The mark frequency you are receiving is actually 14080 = KHz. -=20 2.125 KHz.
=3D 14077.875 KHz. This last number is what you should = post if you=20 want to post the
mark frequency on a DX Cluster.
Your space = frequency is=20 shifted down another 0.170 KHz. from your mark frequency,
so your = space=20 frequency is on 14077.875 KHz. - 0.170 KHz. =3D 14077.705 KHz. =

73=20 Eddie

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=20 confirmed by test, MMTTY is backwards compared to all other Software. = Others=20 idle on the high 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=20 says
You also have to switch the correct phase position = (whether the=20 lower or higher frequency carrier in frequency modulation corresponds = to=20 "Mark" or "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_009D_01CE1A71.FE36BD70--