Return-Path: <owner-rsgb_lf_group@blacksheep.org>
Received: from mtain-db12.r1000.mx.aol.com (mtain-db12.r1000.mx.aol.com [172.29.64.96]) by air-dc07.mail.aol.com (v129.4) with ESMTP id MAILINDC072-862b4ce8ed2a2f0; Sun, 21 Nov 2010 04:58:02 -0500
Received: from post.thorcom.com (post.thorcom.com [195.171.43.25])
	by mtain-db12.r1000.mx.aol.com (Internet Inbound) with ESMTP id 2F0BB3800008D;
	Sun, 21 Nov 2010 04:58:01 -0500 (EST)
Received: from majordom by post.thorcom.com with local (Exim 4.14)
	id 1PK6en-0007F6-Fy
	for rs_out_1@blacksheep.org; Sun, 21 Nov 2010 09:56:25 +0000
Received: from [195.171.43.32] (helo=relay1.thorcom.net)
	by post.thorcom.com with esmtp (Exim 4.14)
	id 1PK6en-0007Ex-2R
	for rsgb_lf_group@blacksheep.org; Sun, 21 Nov 2010 09:56:25 +0000
Received: from cpsmtpb-ews02.kpnxchange.com ([213.75.39.5])
	by relay1.thorcom.net with esmtp (Exim 4.63)
	(envelope-from <pa3abk@kpnmail.nl>)
	id 1PK6em-0004sN-FV
	for rsgb_lf_group@blacksheep.org; Sun, 21 Nov 2010 09:56:25 +0000
Received: from cpbrm-ews03.kpnxchange.com ([10.94.84.134]) by cpsmtpb-ews02.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Sun, 21 Nov 2010 10:56:17 +0100
Received: from CPSMTPM-EML107.kpnxchange.com ([195.121.3.11]) by cpbrm-ews03.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Sun, 21 Nov 2010 10:56:17 +0100
Received: from [192.168.2.13] ([62.131.23.134]) by CPSMTPM-EML107.kpnxchange.com with Microsoft SMTPSVC(7.0.6002.18222);
	 Sun, 21 Nov 2010 10:56:17 +0100
Message-ID: <4CE8ECC1.100@kpnmail.nl>
Date: Sun, 21 Nov 2010 10:56:17 +0100
From: pa3abk <pa3abk@kpnmail.nl>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
References: <8FA94C1DE6F6465C9C511D7A455AB4BB@ns94d01ae4d850> <F26467A8FDE74DEE8C44E22DA4A450C5@2a2d7ed321c6425> <4CE85C77.5010109@kpnmail.nl> <2B3CD1CBF5E640E4940852C83319C537@2a2d7ed321c6425>
In-Reply-To: <2B3CD1CBF5E640E4940852C83319C537@2a2d7ed321c6425>
X-OriginalArrivalTime: 21 Nov 2010 09:56:17.0594 (UTC) FILETIME=[576099A0:01CB8962]
X-RcptDomain: blacksheep.org
X-Spam-Score: 1.4 (+)
X-Spam-Report: autolearn=disabled,RATWARE_GECKO_BUILD=1.426
Subject: Re: AW: LF: MF_Beacon DI2AF is running
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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=none 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: 3039ac1d40604ce8ed2969e9
X-AOL-IP: 195.171.43.25
Content-Transfer-Encoding: quoted-printable
X-Mailer: Unknown (No Version)


I'm bit puzzled with this band.
Every administration seems to have their own rules regarding  the=20
frequency we can use.
Maybe they think that radiowaves just stop at their  borders :-)
Even Marconi prooved that communication on this band can be longrange.
Nevertheless a solution might be, to talk with the other users and  ask =
=20
the "Beh=F6rde" to apply the rules which are generally applied in the EU=
=20
or better worldwide. Temporarely a slottime arrangement with other users=
=20
could be a solution.
Spain joined use lately I was happy to see that they synced their band=20
with ours.

On the other hand I consider it a challenge to decode your signal under =
=20
these circumstances.
It's good visible in Speclab in fragments, but it appears that the=20
dynamic range of soundcard and/or receiver is not sufficient to get it=20
right.

Maybe it's the combination of morse and WSPR is upsetting the software.
The program takes sometimes a very longtime to decode, normally within a=
=20
few seconds, but on "your" QRG sometime 20 secs.
Jan/pa3abk

Op 21-11-2010 1:18, Beckmann, Gerhard schreef:
> Hello Jan,
>
> first of all thank you very much for all your report activity concerning=
 my
> new QRP-beacon. That is a great help for me. I looked for your Mail-adre=
ss
> and did not find it. So I am happy to get your Mail and can say my "Than=
k
> you"!!! Yes you are right it is a big problem for German Hams to work on=
 MF
> because we need an extra licence and have to pay for it. Next problem:=
 We
> are only allowed to operate on 505,1 kHz +/- 100 Hz. SDo we have to shre
> this small band width with all other participants. And the strong beacon
> DI2AM is on 505,180 kHz...That's my problem...
> I will talk to all participants if I can change to 505,040 kHz. Would th=
at
> bee a better solution??
> Thanks again for your kind help, dear Jan.
>
> Best 73 and have a nice Sunday  de Gerhard  /  DK6NI
>
> =3D=3D=3D
>
>
>
> -----Urspr=FCngliche Nachricht-----
> Von:owner-rsgb_lf_group@blacksheep.org
> [mailto:owner-rsgb_lf_group@blacksheep.org] Im Auftrag von pa3abk
> Gesendet: Sonntag, 21. November 2010 00:41
> An:rsgb_lf_group@blacksheep.org
> Betreff: Re: LF: MF_Beacon DI2AF is running
>
> Gerhard,
>
> Q:  Does German rules oblige you to transmit there?
> Your sig is sandwiched between very strong DL CW beacons.
> If I notch out DI7AM (the strongest)  there is a dramatic signal
> improvement .
> Considering your power and my local QRM level the result is vy good.
> Jan/pa3abk
>
>
>
>
>