Date   

Re: Problem with wspr-server ??

Gwyn Griffiths
 

I've emailed Rob with a note that many of the API requests to wsprnet.org are timing out and there are large gaps in the sequence numbers of spots being returned by wsprnet.org. There is certainly congestion at wsprnet,org today.

However, I've found that upload into the wsprdaemon_spots table in the tutorial database is working well, as this is entirely independent of wsprnet.org. I know terminology can sometimes be confusing, so in case it helps, here is a reminder:

On any wsprdaemon server (wsprdaemon.org, logs1.wsprdaemon.org, logs2.wsprdaemon.org):

1. Database 'wsprnet' has a table 'spots' gathered via an API from wsprnet.org

2. Database 'tutorial' has two tables 'wsprdaemon_spots' and 'wsprdaemon_noise' from data sent directly to the wsprdaemon server from your client wsprdaemon application, and so is unaffected by any congestion at wsprnet.org

regards
Gwyn G3ZIL


Re: Problem with wspr-server ??

ON5KQ
 

13h50 utc
can't find any spots on the wsprdaemon server database when connecting via Grafana... since early morning all bands.
Originally I saw a lot of files on my local workstation in the wsprdaemon folder, waiting to be uploaded, however they are all erased now.
Curl.log only zeros... no upload confirmations...
There must be something broken... in the meantime, I keep all running here, although it doesn't seem that decodes are written in files, because there is a network error....
The merge.log shows all the spots from the kiwi on each band, but nothing arrived at the wsprdaemon server...

Ulli, ON5KQ


Re: Problem with wspr-server ??

Stu C
 

Might be a loading/DDOS thing as I can see some of my spots (one band) but tried to refresh for all bands and no luck.
The aggregation site pe1itr.com failed to tally today.
On WA2ZKD's site i'm too far up the listing today so might be worse from some locations as a lot of the top users are missing spots?
Stu


Problem with wspr-server ??

ON5KQ
 

No spots sinds several hours...

My local PC works normally with well above 2000decodes/hour...
But nothing appears at the servers

???

Ulli


Re: Noiseblanker in kiwirecorder as a pre-processor to reduce local fence noise before wd writes the wav-files

Cathal Ferris
 

I have a suspicion that the fence pulse might be overloading the Kiwi frontt-end, in which case information is lost anyway before it gets to the noise blanker stage.

Another option, assuming that you have the room at the bottom of your signal spectrum, is to put an attenuator on the Kiwi antenna input and push your received noise floor down closer to the Kiwi's hardware limit. If the numbers work out right it should mean that the peak of the fence pulse doesn't saturate the Kiwi frontend, but still allowing the Kiwi to have the full bit depth at the quiet end to have all of the information decoded from the incoming signal.

If my reading of the flow of wsprdaemon decoding is right, then the presence of the pulse is of no relevance in itself as the protocol will happily work around the presence of the impulse noise; but that makes the assumption that the inbound signal hasn't been clipped or otherwise affected between the pulses due to the impulse noise.

My two KiwiSDRs and the RaspberrySDR that I have pulling signal from an Active-Antenna AAA-1d amplified loop antenna (via one of SV1AFN's "DXer's High-Linearity Pre-Amp (LNA) for HF Receivers" to split and amplify the signal) all appear at times to have overloading, and I am suspecting the ethernet over powerline that the neighbours are claiming not to have. I have yet to try attenuating the signal into the mixer to see the difference, it's a project for over the Christmas.

Regards,
-Cathal


Re: Noiseblanker in kiwirecorder as a pre-processor to reduce local fence noise before wd writes the wav-files

ON5KQ
 

Yes,

It is my intention to compare the Noise blanker enabled WD script against a standard (original) WD script directly and see, if there is any significant difference in reporting statistics. For that purpose I will use two different computers. But antenna will be exactly the same (power splitter to two different kiwi-SDRs)

Most likely I will set it up beginning of next week.

The strength of the noise influencing the North West antenna is however changing - sometimes stronger, sometimes less... we will see.

I will set-up a different call sign for the modified WD-script such as on5kq-nb, so that we can compare easily the results in Grafana.

Ulli, ON5KQ

Yes, you must modify the WD.sh source code.
So do as you say, run a modified version on one Pi reporting as one call sign, and compare it against a standard versionof WD.sh

 



Re: Noiseblanker in kiwirecorder as a pre-processor to reduce local fence noise before wd writes the wav-files

John
 

Ulli,
I remember articles written when WSPR was new and many were thinking of using noise reduction features. The developer recommended to not use any processing on the I/Q files as the WSPR algorithms were designed to find information deep down in the noise. Noise reductions remove information that WSPR  is able to use.

John
TI4JWC


Re: Noiseblanker in kiwirecorder as a pre-processor to reduce local fence noise before wd writes the wav-files

Rob Robinett
 

Yes, you must modify the WD.sh source code.
So do as you say, run a modified version on one Pi reporting as one call sign, and compare it against a standard versionof WD.sh

On Tue, Dec 15, 2020 at 9:42 AM ON5KQ <ON5KQ@...> wrote:

hi Rob,

I updated to latest version of WD with git pull now on my main WSPR Supermicro workstation...


I realize, that it is not possible to use the .conf-file, but edit directly in the wsprdaemon.sh file ?

Because changing the code in wsprdaemon.sh  it will take effect for all kiwis at once and not just a a specific kiwi with the disturbed antenna. It may not harm and I will try tomorrow.


But it is not possible to report any improvement with decent data from such a simple test, because there is no reference. Instead, I would need a different set-up:

- One kiwi run on a raspberry with the same (fence noisy) antenna and original WD version 2.10i

- Another kiwi controlled by a different PC with WD and enabled Noiseblanker with same fence noise antenna perhaps with modified callsign like ON5KQ-NB  ...

Then we can see any difference over time...

I need to set it up for testing... please qrx a while ...hi


Ulli, ON5KQ


Hi Ulli,
 
Make sure you are running v2.10i:
 
pi@Pi-2-KJ6MKI:~/wsprdaemon $ git pull
Already up to date.
pi@Pi-2-KJ6MKI:~/wsprdaemon
 
 
It will be interesting to learn the results of your experiment.  Before making changes, save a copy of the unmodified wsprdaemon.sh, e.g.
 
pi@Pi-2-KJ6MKI:~/wsprdaemon $ cd ~/wsprdaemon/
pi@Pi-2-KJ6MKI:~/wsprdaemon $ cp -p wsprdaemon.sh wsprdaemon.sh.save

Then you can add the "-nb" to line 1446 of V2.10i, i.e::
 
        python3 -u ${KIWI_RECORD_COMMAND} -nb \
 
Rob

On Tue, Dec 15, 2020 at 1:07 AM ON5KQ <ON5KQ@...> wrote:
Rob, this is a question for the code-expert...:

Sometimes I have some fence pulse noise on one of my antennas.
I found out, that when listening on this antenna with the kiwi, I can completely erase the noise, when switching on the kiwi noise blanker in standard mode.
I believe that the wav-files written by wsprdaemon do no process the audio information before it is written in memory for later decoding. It means that kiwirecorder do NOT use the noiseblanker normally, when writing the WAV files.

Now I found there are many options, which can be set for the kiwirecorder.
One can find the options in the wsprdaemon/kiwiclient directory by doing:

$ python3 kiwirecorder.py --help

This calls a list of all available options for the kiwirecorder. In this list of available options we can find for example:

--nb         Enable noise blanker with default parameters

This is exactly I was looking for...
Now my question:
- Can I use this option somehow as a parameter setting in the wsprdaemon.conf file, to activate the noise blanker as an pre-processor for Wsprdaemon ?
- How would I do it ? What is the syntax, I would need to use, to activate the noise blanker by an additional line in Wsprdaemon.conf...

I am thinking about something similar, as you once showed how to change the parameters for 'wsprd'  decoding engine...
Could you post an example, what exactly I would need to add in wsprdaemon.conf ?

If this is not possible in the conf - file, is there a different method how to activate the noise blanker for some tests ?

Many thanks for some help....

Ulli, ON5KQ




 
--
Rob Robinett
AI6VN
mobile: +1 650 218 8896




--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: Noiseblanker in kiwirecorder as a pre-processor to reduce local fence noise before wd writes the wav-files

ON5KQ
 

hi Rob,

I updated to latest version of WD with git pull now on my main WSPR Supermicro workstation...


I realize, that it is not possible to use the .conf-file, but edit directly in the wsprdaemon.sh file ?

Because changing the code in wsprdaemon.sh  it will take effect for all kiwis at once and not just a a specific kiwi with the disturbed antenna. It may not harm and I will try tomorrow.


But it is not possible to report any improvement with decent data from such a simple test, because there is no reference. Instead, I would need a different set-up:

- One kiwi run on a raspberry with the same (fence noisy) antenna and original WD version 2.10i

- Another kiwi controlled by a different PC with WD and enabled Noiseblanker with same fence noise antenna perhaps with modified callsign like ON5KQ-NB  ...

Then we can see any difference over time...

I need to set it up for testing... please qrx a while ...hi


Ulli, ON5KQ


Hi Ulli,
 
Make sure you are running v2.10i:
 
pi@Pi-2-KJ6MKI:~/wsprdaemon $ git pull
Already up to date.
pi@Pi-2-KJ6MKI:~/wsprdaemon
 
 
It will be interesting to learn the results of your experiment.  Before making changes, save a copy of the unmodified wsprdaemon.sh, e.g.
 
pi@Pi-2-KJ6MKI:~/wsprdaemon $ cd ~/wsprdaemon/
pi@Pi-2-KJ6MKI:~/wsprdaemon $ cp -p wsprdaemon.sh wsprdaemon.sh.save

Then you can add the "-nb" to line 1446 of V2.10i, i.e::
 
        python3 -u ${KIWI_RECORD_COMMAND} -nb \
 
Rob

On Tue, Dec 15, 2020 at 1:07 AM ON5KQ <ON5KQ@...> wrote:
Rob, this is a question for the code-expert...:

Sometimes I have some fence pulse noise on one of my antennas.
I found out, that when listening on this antenna with the kiwi, I can completely erase the noise, when switching on the kiwi noise blanker in standard mode.
I believe that the wav-files written by wsprdaemon do no process the audio information before it is written in memory for later decoding. It means that kiwirecorder do NOT use the noiseblanker normally, when writing the WAV files.

Now I found there are many options, which can be set for the kiwirecorder.
One can find the options in the wsprdaemon/kiwiclient directory by doing:

$ python3 kiwirecorder.py --help

This calls a list of all available options for the kiwirecorder. In this list of available options we can find for example:

--nb         Enable noise blanker with default parameters

This is exactly I was looking for...
Now my question:
- Can I use this option somehow as a parameter setting in the wsprdaemon.conf file, to activate the noise blanker as an pre-processor for Wsprdaemon ?
- How would I do it ? What is the syntax, I would need to use, to activate the noise blanker by an additional line in Wsprdaemon.conf...

I am thinking about something similar, as you once showed how to change the parameters for 'wsprd'  decoding engine...
Could you post an example, what exactly I would need to add in wsprdaemon.conf ?

If this is not possible in the conf - file, is there a different method how to activate the noise blanker for some tests ?

Many thanks for some help....

Ulli, ON5KQ




 
--
Rob Robinett
AI6VN
mobile: +1 650 218 8896



Re: Noiseblanker in kiwirecorder as a pre-processor to reduce local fence noise before wd writes the wav-files

Rob Robinett
 

Hi Ulli,

Make sure you are running v2.10i:

pi@Pi-2-KJ6MKI:~/wsprdaemon $ git pull
Already up to date.
pi@Pi-2-KJ6MKI:~/wsprdaemon


It will be interesting to learn the results of your experiment.  Before making changes, save a copy of the unmodified wsprdaemon.sh, e.g.

pi@Pi-2-KJ6MKI:~/wsprdaemon $ cd ~/wsprdaemon/
pi@Pi-2-KJ6MKI:~/wsprdaemon $ cp -p wsprdaemon.sh wsprdaemon.sh.save

Then you can add the "-nb" to line 1446 of V2.10i, i.e::

        python3 -u ${KIWI_RECORD_COMMAND} -nb \

Rob


On Tue, Dec 15, 2020 at 1:07 AM ON5KQ <ON5KQ@...> wrote:
Rob, this is a question for the code-expert...:

Sometimes I have some fence pulse noise on one of my antennas.
I found out, that when listening on this antenna with the kiwi, I can completely erase the noise, when switching on the kiwi noise blanker in standard mode.
I believe that the wav-files written by wsprdaemon do no process the audio information before it is written in memory for later decoding. It means that kiwirecorder do NOT use the noiseblanker normally, when writing the WAV files.

Now I found there are many options, which can be set for the kiwirecorder.
One can find the options in the wsprdaemon/kiwiclient directory by doing:

$ python3 kiwirecorder.py --help

This calls a list of all available options for the kiwirecorder. In this list of available options we can find for example:

--nb         Enable noise blanker with default parameters

This is exactly I was looking for...
Now my question:
- Can I use this option somehow as a parameter setting in the wsprdaemon.conf file, to activate the noise blanker as an pre-processor for Wsprdaemon ?
- How would I do it ? What is the syntax, I would need to use, to activate the noise blanker by an additional line in Wsprdaemon.conf...

I am thinking about something similar, as you once showed how to change the parameters for 'wsprd'  decoding engine...
Could you post an example, what exactly I would need to add in wsprdaemon.conf ?

If this is not possible in the conf - file, is there a different method how to activate the noise blanker for some tests ?

Many thanks for some help....

Ulli, ON5KQ



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Noiseblanker in kiwirecorder as a pre-processor to reduce local fence noise before wd writes the wav-files

ON5KQ
 

Rob, this is a question for the code-expert...:

Sometimes I have some fence pulse noise on one of my antennas.
I found out, that when listening on this antenna with the kiwi, I can completely erase the noise, when switching on the kiwi noise blanker in standard mode.
I believe that the wav-files written by wsprdaemon do no process the audio information before it is written in memory for later decoding. It means that kiwirecorder do NOT use the noiseblanker normally, when writing the WAV files.

Now I found there are many options, which can be set for the kiwirecorder.
One can find the options in the wsprdaemon/kiwiclient directory by doing:

$ python3 kiwirecorder.py --help

This calls a list of all available options for the kiwirecorder. In this list of available options we can find for example:

--nb         Enable noise blanker with default parameters

This is exactly I was looking for...
Now my question:
- Can I use this option somehow as a parameter setting in the wsprdaemon.conf file, to activate the noise blanker as an pre-processor for Wsprdaemon ?
- How would I do it ? What is the syntax, I would need to use, to activate the noise blanker by an additional line in Wsprdaemon.conf...

I am thinking about something similar, as you once showed how to change the parameters for 'wsprd'  decoding engine...
Could you post an example, what exactly I would need to add in wsprdaemon.conf ?

If this is not possible in the conf - file, is there a different method how to activate the noise blanker for some tests ?

Many thanks for some help....

Ulli, ON5KQ


WSPR reports W6 <==> Europe via long path on 40m

ON5KQ
 

Nice condx from Belgium to west-coast USA on 40m this afternoon - 14h30 utc....
N7XM booming here from close to Carson City, Nevada in CW band ... many others now as well... the CW-band is full of loud west-coast on the V-beam

KFS starts hearing OZ7IT and DK4BM from Northern Germany at 14h35utc
KFS heards my tx signals on 40m in in late oktober already... so signals should be LOUD now in high winter.

Although N7XM is almost S9 here in CW on the V-beam to South East (long path USA) obviously no WSPR tx-stations point the antenna to the pacific....
Have heard LP-W6/W7 WSPR station earlier this year though...
So I keep trying to catch some stations on 40m LP .... amazing 30000+ km distance....

Ulli


Re: FST4W support in WD

Edward Hammond
 

I may not be a "top" station, but I think I'm holding my own for a newbie.  And I have improvement plans for mid-2021.

FSTW4W support would provide a great excuse for building an LW/MW antenna and dedicating a Kiwi to it in March or April.

My wife's gonna love it!

Thanks for all your work Rob.

Edward

W3ENR

On 11/29/20 9:36 AM, Rob Robinett wrote:
In Wednesday's Zoom meeting we discussed my plan to add this feature, and based upon that feedback I won't rush to implement it.
However, since many of the top spotters are running WD, it is at the top of my TODO list and I hope to add it by the end of December.
Let me know if you have a more immediate need for it.


FST4W support in WD

Rob Robinett
 

In Wednesday's Zoom meeting we discussed my plan to add this feature, and based upon that feedback I won't rush to implement it.
However, since many of the top spotters are running WD, it is at the top of my TODO list and I hope to add it by the end of December.
Let me know if you have a more immediate need for it.


Re: Obtaining date/time from the Kiwi's GPS [fixed in v1.417]

jks
 

From the v1.427 release notes:

    Added gps_date parameter to /status query. "gps_date=<enable>,<set>" where <enable> and
        <set> are digits '0' or '1' indicating if gps is enabled to set date/time, and if
        the set has actually occurred.
 


Re: Major update to WsprDaemon Timescale Database Guide V2

ON5KQ
 

Hi Gwyn,

many thanks for all that excellent work ! I am sorry to reserve more time into the data analysis yet - but silently using with great pleasure, what you have done on the log2 server.

I was just too busy with setting up my extensive winter antenna set-up... But winter holiday is cancelled due to Corona and the long winter evenings will offer possibly more time for the shack and also more data analysis, for which I have great interest...

Many thanks,

Ulli, ON5KQ

I've updated and expanded my Guide to the WsprDaemon Timebase installation. It's attached as a file to this message and available via the WsprDaemon Timescale web page. The Guide is now fully consistent with the installation on the logs2.wsprdaemon.org server. It includes many new examples of postgreSQL queries and has Annexes outlining APIs for a range of methods to access the data. I'm grateful to Phil, VK7JJ, for contributing an Annex on how he uses node.js. Other routes include Python, psql, KNIME, and Octave (Win 10 and macOS proven so far).
If you spot errors, or parts are not clear, please let me know.
73
Gwyn G3ZIL



Major update to WsprDaemon Timescale Database Guide V2

Gwyn Griffiths
 

I've updated and expanded my Guide to the WsprDaemon Timebase installation. It's attached as a file to this message and available via the WsprDaemon Timescale web page. The Guide is now fully consistent with the installation on the logs2.wsprdaemon.org server. It includes many new examples of postgreSQL queries and has Annexes outlining APIs for a range of methods to access the data. I'm grateful to Phil, VK7JJ, for contributing an Annex on how he uses node.js. Other routes include Python, psql, KNIME, and Octave (Win 10 and macOS proven so far).
If you spot errors, or parts are not clear, please let me know.
73
Gwyn G3ZIL


V2.10i fixes installation on Ubuntu 20.04.1 LTS

Rob Robinett
 

If your WD is running, then there is no need to upgrade to this version.


Re: Delayed Kiwi connection problems should be fixed in V2.10h

ON5KQ
 

Rob,

I think my start-up problem has been solved as I could download and install the kiwirecorder script.

I also found, that the establishment of receive channels of the kiwis now happens almost instantly. As my set-up grows while building some better antennas I run currently 32 channels on 4 different antennas. It works without problem now on my Dual-Xeon Supermicro Workstation.

Ulli, ON5KQ

I think I found and fixed that problem which has been reported by several users.
Let me know if you still experience rx channels which come up only after some minutes, or never at all.



Delayed Kiwi connection problems should be fixed in V2.10h

Rob Robinett
 

I think I found and fixed that problem which has been reported by several users.
Let me know if you still experience rx channels which come up only after some minutes, or never at all.

601 - 620 of 668