Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dc04.r1000.mx.aol.com (Internet Inbound) with ESMTP id 20E963800008A; Thu, 30 Aug 2012 11:58:46 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1T76NI-0008LE-2c for rs_out_1@blacksheep.org; Thu, 30 Aug 2012 16:09:40 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1T76NH-0008L5-4x for rsgb_lf_group@blacksheep.org; Thu, 30 Aug 2012 16:09:39 +0100 Received: from imr-ma04.mx.aol.com ([64.12.206.42]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1T76NE-0004rV-Kj for rsgb_lf_group@blacksheep.org; Thu, 30 Aug 2012 16:09:38 +0100 Received: from mtaomg-ma03.r1000.mx.aol.com (mtaomg-ma03.r1000.mx.aol.com [172.29.41.10]) by imr-ma04.mx.aol.com (8.14.1/8.14.1) with ESMTP id q7UF9LLb020951 for ; Thu, 30 Aug 2012 11:09:21 -0400 Received: from core-msa004c.r1000.mail.aol.com (core-msa004.r1000.mail.aol.com [172.29.233.77]) by mtaomg-ma03.r1000.mx.aol.com (OMAG/Core Interface) with ESMTP id B71B6E00008D for ; Thu, 30 Aug 2012 11:09:20 -0400 (EDT) References: <503EA718.2010301@charter.net> To: rsgb_lf_group@blacksheep.org In-Reply-To: <503EA718.2010301@charter.net> X-MB-Message-Source: WebUI MIME-Version: 1.0 From: Markus Vester X-MB-Message-Type: User X-Mailer: Webmail 36912-BASIC Received: from 194.138.39.52 by webmail-d136.sysops.aol.com (149.174.18.26) with HTTP (WebMailUI); Thu, 30 Aug 2012 11:09:19 -0400 Message-Id: <8CF54D89088EA63-22E8-50D77@webmail-d136.sysops.aol.com> X-Originating-IP: [194.138.39.52] Date: Thu, 30 Aug 2012 11:09:20 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1346339361; bh=ypDEZ2BmryJiM+3pHYCBTbUJ39682tpduc8VL/wMf+M=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=H/hQKypuYdSx+y1K7t5xy7ypNUsTcGFySdoQTUQaOQjeUOSBjWnwP0vAvMbBEyK6T wXmIEHWMW81IyUntfy8uy5WCItZq44soBAjdcT+OdcvGWdRVNnJc0fnyDlpSqHgwtd ycUQkemyB1yPxhCxpJA1IbuxRwHEnKlv4aROEIoM= X-AOL-SCOLL-SCORE: 0:2:405893024:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-Spam-Score: -0.2 (/) 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: Sorry, no joy here from John's Op-8 last night, due to several adverse conditions:  - relatively high QRN levels. Little one can do about it - the ol' rule "listen when QRN is low, transmit when it's high" is probably the best guide for intercontinental LF work.  - wrong RX frequency: I had set up my 2 Hz wide recording on 137561 and went to bed before John's update arrived... In my opinion, splitting subbands for different Opera submodes is not a good idea. I don't see a technical need for it, and it eats up a lot of bandwidth, especially with the software's automatic frequency selection. Anyway the 137.5-.6 band overlaps typical WSPR usage (137.4-.6). And the area above 137.6 (especially the DCF gap around 137.63) would be the best choice for QRSS-3 or 10 QSOs.  - DK7FC was active on a nearby frequency during most of the night. In conjunction with the noise blanker the RX is desensitized by the a nearby strong signal. The problem is exacerbated by high density of keyclicks in Opera (5 to 8x more than QRSS), and that most seem to apply hard keying. Trying to interleave operating times (eg. even vs odd days, or hours) is probably not a satisfactory solution.  If we seriously consider using Opera for intercontinental work, I believe that we should include it in the existing splitband scheme, with widely spaced subbands for East-to-West and West-to-East operation (the well-proven "TA" and "Eu" slots). For example, we could place a narrow Opera slot beneath each of the QRSS segments. So, open to discussion, here is one proposal for slow-mode band usage:  137.77-137.78 W->E DX QRSS, DFCW 30..180 137.76-137.77 W->E DX Op 32  137.60-137.75 mid range QRSS, DFCW 3..10 137.50-137.60 mid range Op 2..8 137.40-137.50 WSPR  136.17-136.18 E->W DX QRSS, DFCW 30..180 136.16-136.17 E->W DX Op 32  Best 73, Markus (DF6NM) [...] Content analysis details: (-0.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [64.12.206.42 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 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: fefa6d96b1284f767a869566d1bc7791 Subject: LF: Opera frequency usage Content-Type: multipart/alternative; boundary="--------MB_8CF54D890B3C2FF_22E8_12171C_webmail-d136.sysops.aol.com" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=HTML_MESSAGE 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-dc04.r1000.mx.aol.com ; domain : mx.aol.com DKIM : fail x-aol-sid: 3039ac1d4084503f8db527ae X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ----------MB_8CF54D890B3C2FF_22E8_12171C_webmail-d136.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Sorry, no joy here from John's Op-8 last night, due to several adverse cond= itions: =C2=A0 - relatively high QRN levels. Little one can do about it - the ol' rule "li= sten when QRN is low, transmit when it's high" is probably the best guide f= or intercontinental LF work. =C2=A0 - wrong RX frequency: I had set up my 2 Hz wide recording on 137561 and wen= t to bed before John's update arrived... In my opinion, splitting subbands for different Opera submodes is not a goo= d idea. I don't see a technical need for it, and it eats up a lot of bandwi= dth, especially with the software's automatic frequency selection. Anyway t= he 137.5-.6 band overlaps typical WSPR usage (137.4-.6). And the area above= 137.6 (especially the DCF gap around 137.63) would be the best choice for = QRSS-3 or 10 QSOs. =C2=A0 - DK7FC was active on a nearby frequency during most of the night. In conju= nction with the noise blanker the RX is desensitized by the a nearby strong= signal. The problem is exacerbated by high density of keyclicks in Opera (= 5 to 8x more than QRSS), and that=C2=A0most seem to apply hard keying. Tryi= ng to interleave operating times (eg. even vs odd days, or hours) is probab= ly not a satisfactory solution. =C2=A0 If we seriously consider using Opera for intercontinental work, I believe t= hat we should include it in the existing splitband scheme, with widely spac= ed subbands for East-to-West and West-to-East operation (the well-proven "T= A" and "Eu" slots). For example, we could place a narrow Opera slot beneath= each of the QRSS segments. So, open to discussion, here is one proposal fo= r slow-mode band usage: =C2=A0 137.77-137.78 W->E DX QRSS, DFCW 30..180=C2=A0=20 137.76-137.77 W->E DX Op 32 =C2=A0 137.60-137.75 mid range QRSS, DFCW 3..10 137.50-137.60 mid range Op 2..8 137.40-137.50 WSPR =C2=A0 136.17-136.18 E->W DX QRSS, DFCW 30..180=C2=A0=20 136.16-136.17 E->W DX Op 32 =C2=A0 Best 73,=20 Markus (DF6NM) -----Urspr=C3=BCngliche Mitteilung-----=20 Von: John Andrews <w1tag@charter.net> An: rsgb_lf_group <rsgb_lf_group@blacksheep.org> Verschickt: Do, 30 Aug 2012 4:15 am Betreff: Re: LF: LF acty Stephan,=20 =20 Actually, Jay was talking about transmitting OP8 also tonight. Not sure =20 of his plans. I will run XES until well after your sunrise.=20 =20 John, W1TAG/WD2XES=20 =20 On 8/29/2012 7:17 PM, Stefan Sch=C3=A4fer wrote:=20 > Hello John, Joe, LF,=20 >=20 > Wow, now there is much going on tonite again. Another time i don't kno= w=20 > if i should RX or TX and in which mode...=20 > I think i will not have a chance to decode W1TAG in OP8, however VO1NA= =20 > in OP32 could be possible and would be my best rx-distance in OP.=20 > Furthermore i want to provide test signals for YV7MAE, so i'm now=20 > sending DFCW-90, after sending DFCW-180 to VK.=20 >=20 > John, will you transmit OP8 until the morning? Has Jay a chance to=20 > receive me in OP8 later or will you nearly overload his RX? :-)=20 >=20 > 73, Stefan/DK7FC=20 >=20 > PS: Our russian friends are doing a good job! Many stations, with good= =20 > receivers and transmitters!=20 >=20 >=20 > Am 30.08.2012 00:33, schrieb John Andrews:=20 >> Forgot about the split Opera band for the two data rates. The actu= al=20 >> frequency tonight will be 137.621 kHz. Stick with 136.0 USB for a = dial=20 >> setting.=20 >>=20 >> John, W1TAG/WD2XES=20 > ----------MB_8CF54D890B3C2FF_22E8_12171C_webmail-d136.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
Sorry, no = joy here from John's Op-8 last night, due to several adverse conditions:
 
- relatively high QRN levels. Little one can do about it - the ol' rul= e "listen when QRN is low, transmit when it's high" is probably the best gu= ide for intercontinental LF work.
 
- wrong RX frequency: I had set up my 2 Hz wide recording on 137561 an= d went to bed before John's update arrived...
In my opinion, splitting subbands for different Opera submodes is not a goo= d idea. I don't see a technical need for it, and it eats up a lot of bandwi= dth, especially with the software's automatic frequency selection. Anyway t= he 137.5-.6 band overlaps typical WSPR usage (137.4-.6). And the area above= 137.6 (especially the DCF gap around 137.63) would be the best choice for = QRSS-3 or 10 QSOs.
 
- DK7FC was active on a nearby frequency during most of the night. In = conjunction with the noise blanker the RX is desensitized by the a nearby s= trong signal. The problem is exacerbated by high density of keyclicks in Op= era (5 to 8x more than QRSS), and that most seem to apply hard keying.= Trying to interleave operating times (eg. even vs odd days, or hours) is p= robably not a satisfactory solution.
 
If we seriously consider using Opera for intercontinental work, I beli= eve that we should include it in the existing splitband scheme, with widely= spaced subbands for East-to-West and West-to-East operation (the well-prov= en "TA" and "Eu" slots). For example, we could place a narrow Opera slot be= neath each of the QRSS segments. So, open to discussion, here is one propos= al for slow-mode band usage:
 
137.77-137.78 W->E DX QRSS, DFCW 30..180 
137.76-137.77 W->E DX Op 32
 
137.60-137.75 mid range QRSS, DFCW 3..10
137.50-137.60 mid range Op 2..8
137.40-137.50 WSPR
 
136.17-136.18 E->W DX QRSS, DFCW 30..180 
136.16-136.17 E->W DX Op 32
 
Best 73,
Markus (DF6NM)

-----Urspr=C3=BCngliche Mitteilung-----
Von: John Andrews <w1tag@charter.net>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Verschickt: Do, 30 Aug 2012 4:15 am
Betreff: Re: LF: LF acty


Stephan, 

 

Actually, Jay was talking about transmitting OP8 also tonight. Not sure  
of his plans. I will run XES until well after your sunrise. 

 

John, W1TAG/WD2XES 

 

On 8/29/2012 7:17 PM, Stefan Sch=C3=A4fer wrote: 

> Hello John, Joe, LF, 

> 

> Wow, now there is much going on tonite again. Another time i don't kno=
w 

> if i should RX or TX and in which mode... 

> I think i will not have a chance to decode W1TAG in OP8, however VO1NA=
 

> in OP32 could be possible and would be my best rx-distance in OP. 

> Furthermore i want to provide test signals for YV7MAE, so i'm now 

> sending DFCW-90, after sending DFCW-180 to VK. 

> 

> John, will you transmit OP8 until the morning? Has Jay a chance to 
> receive me in OP8 later or will you nearly overload his RX? :-) 

> 

> 73, Stefan/DK7FC 

> 

> PS: Our russian friends are doing a good job! Many stations, with good=
 

> receivers and transmitters! 

> 

> 

> Am 30.08.2012 00:33, schrieb John Andrews: 

>> Forgot about the split Opera band for the two data rates. The actu=
al 

>> frequency tonight will be 137.621 kHz. Stick with 136.0 USB for a =
dial 

>> setting. 

>> 

>> John, W1TAG/WD2XES 

>
----------MB_8CF54D890B3C2FF_22E8_12171C_webmail-d136.sysops.aol.com--