Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mk06.r1000.mx.aol.com (Internet Inbound) with ESMTP id CD8C538000085; Sun, 17 Feb 2013 17:42:26 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1U7CvQ-0007je-NC for rs_out_1@blacksheep.org; Sun, 17 Feb 2013 22:41:36 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1U7CvQ-0007jR-6W for rsgb_lf_group@blacksheep.org; Sun, 17 Feb 2013 22:41:36 +0000 Received: from relay.uni-heidelberg.de ([129.206.100.212]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1U7CvO-0005qo-GK for rsgb_lf_group@blacksheep.org; Sun, 17 Feb 2013 22:41:35 +0000 Received: from freitag.iup.uni-heidelberg.de (freitag.iup.uni-heidelberg.de [129.206.29.204]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id r1HMfDHW028308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 17 Feb 2013 23:41:14 +0100 Received: from [129.206.22.206] (pc206.iup.uni-heidelberg.de [129.206.22.206]) by freitag.iup.uni-heidelberg.de (8.12.11.20060308/8.11.2) with ESMTP id r1HMfDFU006218 for ; Sun, 17 Feb 2013 23:41:13 +0100 Message-ID: <51215C84.6030002@iup.uni-heidelberg.de> Date: Sun, 17 Feb 2013 23:41:08 +0100 From: =?windows-1252?Q?Stefan_Sch=E4fer?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <2282795.WEYH53gDWV@fbox.localdomain> <0739D17A209E4085947C84C3590A8B5F@F6CNIHP> <511FFC06.3090906@psk31.plus.com> <0537FE7E5A0C4521A4BC62EF690FA911@Black> <51215C1C.80906@iup.uni-heidelberg.de> In-Reply-To: <51215C1C.80906@iup.uni-heidelberg.de> X-Spam-Score: -1.3 (-) 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: Same message, updated subject. Am 17.02.2013 23:39, schrieb Stefan Schäfer: > Hi Dimitris, > > Thanks for the informations. > Well, if 475.7 kHz is not a good choice due to QRM in VK, then "we" > should discuss where to go. > > "We", that must be explained. I think that "we" are those active > stations who either want to try to receive a station from VK or want > to try to get a decode in VK. > > Of course i would like to join those active TX stations on MF and i > like to try if i can leave a trace or decode, not only in the sand :-) > I thought about running QRSS-10 near 476.170 kHz, as done in the last > months. This would allow me to run the TX during the complete possible > time, arround 15:30...18:00. Or, alternatively, i would like to run > WSPR-2 in 100% TX mode. That would at least require _splitted RX and > TX bands on both sides_, otherwise there will be complaints. There > will be complaints anyway, im afraid... > > So maybe it would be an idea to define a special slot just for this > path and time and active (RX and TX) stations so they can all run > WSPR-2 in 100% mode. Of course there must be stations who are RXing > exclusively but there are only a few who will TX anyway. > > Any recommendations / ideas? Should we discuss in direct emails > including all those from VK who are not member of this group? > > I would start the MF experiment tomorrow. > > 73, Stefan/DK7FC [...] Content analysis details: (-1.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [129.206.100.212 listed in list.dnswl.org] -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 1908b49407fc556987226b536cc4bad0 Subject: LF: Plans for 630m RX-TX experiments from EU to VK and VK to EU Content-Type: multipart/alternative; boundary="------------060800030001040005010600" 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-sid: 3039ac1d618a51215cd21d71 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. --------------060800030001040005010600 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by relay.uni-heidelberg.de id r1HMfDHW028308 Same message, updated subject. Am 17.02.2013 23:39, schrieb Stefan Sch=E4fer: > Hi Dimitris, > > Thanks for the informations. > Well, if 475.7 kHz is not a good choice due to QRM in VK, then "we"=20 > should discuss where to go. > > "We", that must be explained. I think that "we" are those active=20 > stations who either want to try to receive a station from VK or want=20 > to try to get a decode in VK. > > Of course i would like to join those active TX stations on MF and i=20 > like to try if i can leave a trace or decode, not only in the sand :-)=20 > I thought about running QRSS-10 near 476.170 kHz, as done in the last=20 > months. This would allow me to run the TX during the complete possible=20 > time, arround 15:30...18:00. Or, alternatively, i would like to run=20 > WSPR-2 in 100% TX mode. That would at least require _splitted RX and=20 > TX bands on both sides_, otherwise there will be complaints. There=20 > will be complaints anyway, im afraid... > > So maybe it would be an idea to define a special slot just for this=20 > path and time and active (RX and TX) stations so they can all run=20 > WSPR-2 in 100% mode. Of course there must be stations who are RXing=20 > exclusively but there are only a few who will TX anyway. > > Any recommendations / ideas? Should we discuss in direct emails=20 > including all those from VK who are not member of this group? > > I would start the MF experiment tomorrow. > > 73, Stefan/DK7FC --------------060800030001040005010600 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by relay.uni-heidelberg.de id r1HMfDHW028308 Same message, updated subject.

Am 17.02.2013 23:39, schrieb Stefan Sch=E4fer:
Hi Dimitris,

Thanks for the informations.
Well, if 475.7 kHz is not a good choice due to QRM in VK, then "we" should discuss where to go.

"We", that must be explained. I think that "we" are those active stations who either want to try to receive a station from VK or want to try to get a decode in VK.

Of course i would like to join those active TX stations on MF and i like to try if i can leave a trace or decode, not only in the sand :-) I thought about running QRSS-10 near 476.170 kHz, as done in the last months. This would allow me to run the TX during the complete possible time, arround 15:30...18:00. Or, alternatively, i would like to run WSPR-2 in 100% TX mode. That would at least require splitted RX and TX bands on both sides, otherwise there will be complaints. There will be complaints anyway, im afraid...

So maybe it would be an idea to define a special slot just for this path and time and active (RX and TX) stations so they can all run WSPR-2 in 100% mode. Of course there must be stations who are RXing exclusively but there are only a few who will TX anyway.

Any recommendations / ideas? Should we discuss in direct emails including all those from VK who are not member of this group?

I would start the MF experiment tomorrow.

73, Stefan/DK7FC
--------------060800030001040005010600--