N3AGE 160M


Glenn Elmore
 

One vote in defense of the multi-spot filter is related to VHF/UHF WSPR.  It's not uncommon for GPSDO's and/or commercial multi-mode, HF-UHF ham transceivers to have low level mains-related FM (angular modulation) of their clock. Even if there is only a little at HF, say -60 dBC on 20m,  by the time one looks close to the carrier at 23 cm it's 40 dB bigger and perhaps producing a family of 50|60 Hz sidebands around the main carrier which are only 20 dB down. They may not be noticeable on SSB.

On VHF-UHF WSPR it isn't uncommon to run 50-100 watts in order to see the 500 mile/800 km  aircraft scatter spots that are fairly easy to achieve with a mediocre station.  For other spotters local to such a transmitter, each of the smaller sidebands may produce a perfectly valid WSPR spot since it is a legitimate WSPR signal.  This can fill the database with several extra spots that makes a mess of things.  Filtering to the largest removes this irritation.

I suppose the HW solution to improve transmit spectrum is the elegant one, but it's not always practical.  It would seem that a SW solution would be to keep track of modes and always consider them separate spots without filtering.

I don't expect WN to make changes of this sort any time soon...

Glenn n6gn

On 7/29/22 18:25, Rob Robinett wrote:

Unlike the wsprdaemon server, wsprnet maps WSPR-2 and FST4W-120 to the same mode=2 value.  So (stupid) WN sees two signals with different modulation in the same WSPR cycle as duplicates and will throw one of the reports away using an undefined algorithm which I wish they never implemented.
But the WD server will record both of them.


KD2OM
 

I have been decoding Glenn and Elmers spots using KD2OM/T on an APi. 
You also might have noticed that I commented out the first line of the conf file so that both the APi and i7 are using defaults instead of the 10000 that it i7 used.
I get correlation now on 20 meters between the two processors.

Steve

.
 

On Jul 30, 2022, at 11:49, Rob Robinett <rob@...> wrote:

I have just upgraded Steve to v 3.0.3.2 and added F2:F5:F15 on 20M, which means he can now decode Glen's N6GN and Elmer's N3AGE FST4W transmissions


Rob Robinett
 

I have just upgraded Steve to v 3.0.3.2 and added F2:F5:F15 on 20M, which means he can now decode Glen's N6GN and Elmer's N3AGE FST4W transmissions


Gwyn Griffiths
 

Steve
You might find the Grafana graphs at

http://logs1.wsprdaemon.org:3000/d/4xvGwI97z/wspr-and-fst4w-comparisons?orgId=1&var-receiver=BE&var-sender=N3AGE&var-band=160&var-rx_id=KD2OM&from=now-2d&to=now

may be of use to you. Log on as usual with userid wdread and password JTWSPR2008
You can select the rx_id and then pull down which receiver you want to check on the left. WSPR-2 and the different lengths of FST4W are color coded.

Gaps may be due to too much spectral spreading - but I can't be sure as zero is being shown for all spectral widths.
You may need to check with Rob whether your copy of WD has this feature enabled.

73
Gwyn G3ZIL
 


Glenn Elmore
 

Different band/time combinations should be fine.  But it seems to me that when I was transmitting simultaneous WSPR/FST4W with two audio streams into the same radio separated only by frequency that I only got one posted, usually WSPR.  I think Wsprnet.org does filter. Maybe Rob can explain what happens elsewhere.

Glenn n6gn

On 7/29/22 17:06, Elmer G Musser wrote:
if you decode both they will show. different bands different times.


Elmer G Musser
 

if you decode both they will show. different bands different times.

On Jul 29, 2022, at 3:57 PM, Jim Lill <jim@...> wrote:

I don't think my dupe filter on the "8088" page would filter it.

for myself, I show

2022-07-29 09:05 n3age 1.838101 -34 FN30hw 23 WA2ZKD FN13ed FST4W300
2022-07-29 09:15 n3age 1.838101 -37 FN30hw 23 WA2ZKD FN13ed FST4W900

-Jim

On 7/29/22 15:28, KD2OM wrote:
Elmer,
I am not sure about this but believe that the dupe filters will ignore all after the first spot is heard. I hear you on 160 but only mode 2, I have to believe that if I heard you on that mode I would have heard the other modes as well.
Someone will correct me if that is wrong.

73,
Steve KD2OM







Jim Lill
 

I don't think my dupe filter on the "8088" page would filter it.

for myself, I show

2022-07-29     09:05            n3age     1.838101     -34  FN30hw     23           WA2ZKD     FN13ed     FST4W300
2022-07-29     09:15            n3age     1.838101     -37  FN30hw     23           WA2ZKD     FN13ed     FST4W900

-Jim

On 7/29/22 15:28, KD2OM wrote:
Elmer,
I am not sure about this but believe that the dupe filters will ignore all after the first spot is heard. I hear you on 160 but only mode 2, I have to believe that if I heard you on that mode I would have heard the other modes as well.
Someone will correct me if that is wrong.

73,
Steve KD2OM




KD2OM
 

Elmer,
I am not sure about this but believe that the dupe filters will ignore all after the first spot is heard. I hear you on 160 but only mode 2, I have to believe that if I heard you on that mode I would have heard the other modes as well.
Someone will correct me if that is wrong.

73,
Steve KD2OM


Elmer G Musser
 

My first time using GROUP, sorry if I botched this…

 

The 160M system will being broadcasting (1 watt into a 43’ vertical)

MINIUTE     MODE       PERIOD

  0                   WSPR         120

  5                   FST4W       300 (skipping 120 as it is redundant with WSPR (IMHO)

15                  FST4W       900

30                  FST4W      1800

Rinse and repeat forever.

 

630M is back on air (all modes)

2200M awaiting power supply (it got HOT here and environment was not kind to equipmemt)

10, 15, 20, 30, 40 and 80 will soon be connected to a more stable reference. 

On the 10 thru 80 WSPR followed by FST4W 300 and repeat will continue unless there is a “study” where other scheduling is desired.   

 

73’s

N3AGE/Elmer

 

 

Sent from Mail for Windows