Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

Re: LF: wspr decode

To: <[email protected]>
Subject: Re: LF: wspr decode
From: "mal hamilton" <[email protected]>
Date: Sat, 2 Feb 2013 15:56:27 -0000
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>
Reply-to: [email protected]
Sender: [email protected]
Eddie es Co
Not doing badly here copy LA6TPA at 1312 Km best distance on the current list of intercepts
g3kev
 
----- Original Message -----
Sent: Saturday, February 02, 2013 3:50 PM
Subject: Re: LF: wspr decode

Eddie
Now seeing 10 different stns active but not getting that many decodes, so I am seeing everyone strong es weak but decoding is a different story that is where QRSS has the advantage because by now I would have full ID on all 10.
A good test would be to follow each WSPR transmission with a QRSS one for comparison and then we could see who was there but not making a decode
Even the weak ones are good visibility with me and a lot of them are audible
 
de g3kev
 
----- Original Message -----
From: g3zjo
Sent: Saturday, February 02, 2013 2:50 PM
Subject: Re: LF: wspr decode

On 02/02/2013 14:27, mal hamilton wrote:
Eddie
One problem that effects you and your QRP
I am beaming E/W and you are to my south in the 40m loop null. I will switch to the inv L later and maybe see u then. One other thing
Yes you did slew your lobes some time ago and saw me.
I do not see my callsign on the reports although I have ticked the Upload box.
No you have never uploaded a spot according to the DB. Have you filled in you details in the Settings box.
I depend on time sync via internet.
Via a separate time server or Muckysoft? Muckysoft can default to re setting every month or more which is not enough.

Eddie
mal/g3kev
 
----- Original Message -----
From: g3zjo
Sent: Saturday, February 02, 2013 2:13 PM
Subject: Re: LF: wspr decode

Mal

I have increased my power by 10dB so you never know. However the the other morning running this power on QRSS3  I called and called you precisely on your frequency.. After one call the timing was so right that I sent you a report over and over but no, you couldn't see me.
Temperamental? In no way, it is solid and reliable believe me. At first I use to measure accurately the 1.6Hz data steps when setting up a PIC system, now I set it by eye and just look to make sure I get decoded to -31dB from distant stations, tolerant or what.
WSPR copes with frequency drifting TX's some drifting 3 times the width of the signal, and get decoded.

Eddie

On 02/02/2013 13:49, mal hamilton wrote:
Ps
things are improving now decoding DK7FC and M1GEO watch out you could be next. Seems a temperamental mode
g3kev
 
----- Original Message -----
Sent: Saturday, February 02, 2013 1:32 PM
Subject: Re: LF: wspr decode

Eddie
My Logic---If I can decode one then that should apply to all the others
 
----- Original Message -----
From: g3zjo
Sent: Saturday, February 02, 2013 11:42 AM
Subject: Re: LF: wspr decode

Simple one, but timing, is your timing OK?

Eddie

On 02/02/2013 11:32, mal hamilton wrote:
I am seeing quite a lot of acty on the waterfall and you are probably there, 8 visible at present but Decode is a different story.
Like I said if these same stns were on QRSS I would get an ID and you would probably be there also
Most are audible with me and strong enough for a CW qso
de g3kev
 
----- Original Message -----
From: g3zjo
Sent: Saturday, February 02, 2013 10:55 AM
Subject: Re: LF: wspr decode

On 02/02/2013 10:40, mal hamilton wrote:
Strangely enough I can only decode GW8MLA and there are another several stns active at present on WSPR-2. Most are strong and audible
de g3kev
 
Well that will give you a rather distorted view of the usefulness of the mode then.

And you don't see me,

Beatles

You think you've got everything you want
And your bird can sing
But you don't see me

Do I remember the lyrics right?

Eddie



<Prev in Thread] Current Thread [Next in Thread>