Date   

Re: New to the list

VE3VXO
 

Hi Glenn

Thanks for the very quick and informative response.  Since I have no experience with the Pi, before I buy one do you have any other recommendations given that I intend to run this from a battery and am concerned about shielding emissions from the Pi while keeping it cool, the typical plastic cases they push at the Pi outlets are probably not what I want.  I see the Pi 4B requires 3.1A, I was initially envisioning running the Kiwi on one of those 1MHz buck converters which are relatively RF quiet but I guess that idea won't work for the Pi-4B as the SMPS is rated for 3A max.

Joe


Re: New to the list

Glenn Elmore
 

Joe,

You understand this correctly. Even an RPI 3 can handle simple spotting, noise and SNR measurement when used with WD.  Data can be recorded apart from an Internet connection and then automatically uploaded once the RPI returns to one.  This can include not only spot but noise data which can be observed and manipulated by way of various tools.

If you think you might be operating in a situation where you have multiple, busy WSPR bands to receive and decode, it might be a good idea to go for at least an RPI 4 since it is possible to over-run the capability of an RPI3 on busy bands with lots of decoding to do. Either way you will get a better decoder than the extension on the KiwiSDR by itself.

Glenn n6gn

On 7/14/21 9:26 AM, VE3VXO wrote:
Hello to all, I am Joe ve3vxo and have been running a Seed KiwiSDR for a couple of years now.  I have been using it to evaluate low band receive antennas using the wspr extension.  Recent experiments are giving me doubts that nearby conductive objects at my shack are playing havoc with the expected antenna patterns as predicted by eznec modelling and I would like to move the antennas temporarily to a remote location where there is no internet connectivity and do a run of 12 to 24 hours to get a range of spots during both day and night propagation conditions to evaluate the shape of the antenna response.  This would require that spots be recorded and I could upload them to wsprnet.org later when I get home to look at the map.  I just found out about wsprdaemon but have not learned all about it yet so please forgive the ignorant question, but is this something that wsprdaemon can do for me? According to Rob's (AI6VN) TAPR presentation video I just watched there was one bullet saying "cathes spots through loss of internet connectivity" so I think that suggests the answer to my question is yes, but I want to make sure this will work before I begin here as I don't have a Rpi to use for this and I am such a beginner with Linux that it will be a steep learning curve for me, but I will be happy to embark on it if someone can confirm for me this will do what I am hoping. Perhaps I should be asking if there is an easier solution as well? Logging to an SD card and later manual upload for example? A patch for the KiwiSDR code to do this directly on the Kiwi? Ideas anyone?

Best regards all...joe


New to the list

VE3VXO
 

Hello to all, I am Joe ve3vxo and have been running a Seed KiwiSDR for a couple of years now.  I have been using it to evaluate low band receive antennas using the wspr extension.  Recent experiments are giving me doubts that nearby conductive objects at my shack are playing havoc with the expected antenna patterns as predicted by eznec modelling and I would like to move the antennas temporarily to a remote location where there is no internet connectivity and do a run of 12 to 24 hours to get a range of spots during both day and night propagation conditions to evaluate the shape of the antenna response.  This would require that spots be recorded and I could upload them to wsprnet.org later when I get home to look at the map.  I just found out about wsprdaemon but have not learned all about it yet so please forgive the ignorant question, but is this something that wsprdaemon can do for me? According to Rob's (AI6VN) TAPR presentation video I just watched there was one bullet saying "cathes spots through loss of internet connectivity" so I think that suggests the answer to my question is yes, but I want to make sure this will work before I begin here as I don't have a Rpi to use for this and I am such a beginner with Linux that it will be a steep learning curve for me, but I will be happy to embark on it if someone can confirm for me this will do what I am hoping. Perhaps I should be asking if there is an easier solution as well? Logging to an SD card and later manual upload for example? A patch for the KiwiSDR code to do this directly on the Kiwi? Ideas anyone?

Best regards all...joe


Re: Wsprdaemon logs & data overflowing

Rob Robinett
 

Overflowing uploads.d/... suggests that your WD server is failing to upload to wsprnet.org and/or wsprdaemon.org.
To get a list of spot and noise files cache for uploading execute: find ~/wsprdaemon/uploads.d/ -name '*.txt' | grep 'spots\|noise', e.g.:

wsprdaemon@kfs-thinkcentre:~$ find ~/wsprdaemon/uploads.d/ -name '*.txt' | grep 'spots\|noise'
/home/wsprdaemon/wsprdaemon/uploads.d/wsprnet.d/spots.d/KFS_CM87tj/KIWI_Omni_B/12/210708_1728_24924600_wspr_spots.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprnet.d/spots.d/KFS_CM87tj/KIWI_Omni_B/10/210708_1728_28124600_wspr_spots.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprnet.d/spots.d/KFS_CM87tj/KIWI_Omni_B/160/210708_1728_1836600_wspr_spots.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprnet.d/spots.d/KFS_CM87tj/KIWI_Omni-A/60/201001_2240_5287200_wspr_spots.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprnet.d/spots.d/KFS_CM87tj/KIWI_Omni-A/160/201001_2240_1836600_wspr_spots.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprnet.d/spots.d/KFS_CM87tj/KIWI_Omni-A/80eu/201001_2240_3592600_wspr_spots.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprnet.d/spots.d/KFS_CM87tj/KIWI_Omni-A/60eu/201001_2240_5364700_wspr_spots.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprdaemon.d/noise.d/KFS_CM87tj/KIWI_Omni_B/12/210708_1728_24924600_wspr_noise.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprdaemon.d/noise.d/KFS_CM87tj/KIWI_Omni_B/10/210708_1728_28124600_wspr_noise.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprdaemon.d/noise.d/KFS_CM87tj/KIWI_Omni_B/160/210708_1728_1836600_wspr_noise.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprdaemon.d/spots.d/KFS_CM87tj/KIWI_Omni_B/12/210708_1728_24924600_wspr_spots.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprdaemon.d/spots.d/KFS_CM87tj/KIWI_Omni_B/10/210708_1728_28124600_wspr_spots.txt
/home/wsprdaemon/wsprdaemon/uploads.d/wsprdaemon.d/spots.d/KFS_CM87tj/KIWI_Omni_B/160/210708_1728_1836600_wspr_spots.txt
wsprdaemon@kfs-thinkcentre:~$


On Thu, Jul 8, 2021 at 12:37 AM Юрий Максимов <rz3dvp@...> wrote:
Thanks for your answer Rob.
I had problems with overflowing the uploads.d  folder one or two times… I think it’s not a big problem, I will add to cron daily rule for clear old files…
Thank you for grate job and hope v3 will be releasing quickly. :)

--
Best regards, 73!
Yuri 

8 июля 2021 г., в 01:52, Rob Robinett <rob@...> написал(а):


Hi Yuri,

WD v2.x is designed to perform almost no logging when started in its default verbosity level 0 mode, e.g.:  'WD -a'
Many sites have been running for months without overflowing their file systems, so you are suffering an unusual problem which is hard for me to diagnose via email.
If uploads.d/... is now filling up it may be due to failures in the wsprdeamon.org server which I am actively debugging.
I'll be posting progress on that work to the forum.

In WD v3.x (currently in alpha state) I have redesigned the logging system to limit the size of all the log files.

73,

Rob

On Wed, Jul 7, 2021 at 7:47 AM Юрий Максимов <rz3dvp@...> wrote:
Hello Rob,
Maybe you can help me, - how can I reduce data and logs files for wsprdaemon on the file system? For example, folder uplads.d had lot of files after a year and this folder never cleans automatically, maybe exist command for the config file to save data only for 1 week? 
Sorry, maybe I did not read the instructions on GitHub carefully... :)

Best regards,73!
Yuri


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


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


Wsprdaemon logs & data overflowing

Rob Robinett
 

Hi Yuri,

WD v2.x is designed to perform almost no logging when started in its default verbosity level 0 mode, e.g.:  'WD -a'
Many sites have been running for months without overflowing their file systems, so you are suffering an unusual problem which is hard for me to diagnose via email.
If uploads.d/... is now filling up it may be due to failures in the wsprdeamon.org server which I am actively debugging.
I'll be posting progress on that work to the forum.

In WD v3.x (currently in alpha state) I have redesigned the logging system to limit the size of all the log files.

73,

Rob

On Wed, Jul 7, 2021 at 7:47 AM Юрий Максимов <rz3dvp@...> wrote:
Hello Rob,
Maybe you can help me, - how can I reduce data and logs files for wsprdaemon on the file system? For example, folder uplads.d had lot of files after a year and this folder never cleans automatically, maybe exist command for the config file to save data only for 1 week? 
Sorry, maybe I did not read the instructions on GitHub carefully... :)

Best regards,73!
Yuri


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


Re: Intl. WSPR Beacon Project - Grafana Dashboards

ON5KQ
 


Re: Intl. WSPR Beacon Project - Grafana Dashboards

Roland
 

They are TX'ing 24x7x365 following the WSJT-X Band hop plan. Thanks for reports. Stay tuned for more Beacons to come alive in the next couple of days/weeks

https://twitter.com/IntlWspr


Re: Intl. WSPR Beacon Project - Grafana Dashboards

WA2TP
 

I am Also hearing you on 20,30,40
-12 peak.





On Jul 3, 2021, at 9:01 AM, Roland <roland@...> wrote:

Just a quick heads up, first WSPR Beacon has gone live. IUS2PJI is band hopping on 8 Bands. More Beacons will follow very soon
https://www.google.com/maps/d/u/1/edit?mid=14X0GJ4vSQ7D8piZfuHDs902Y9tINuPqB&usp=sharing

73
Roland


Re: Change in noise vertical scale

Rob Robinett
 

Yes, you can change the graph min/max in your conf file, but I can't find it right now.
Clint is using that feature, so maybe he can help.
I have added this to the list server so others can learn too...

On Sat, Jul 3, 2021 at 5:55 AM Bill Liles <lilesw@...> wrote:
Rob, now have two kiwis running at KX4O. Things look good except for noise issues. You can see the noise plots at 

Here is just the plot for 220 meters. 
The reason no points are shown is because the the noise is so high and the vertical access starts at -110. Here is a plot from the wsprdaemon database. 

Is there a way to change the scaling used on the noise display at 

Thanks,
Bill


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


Re: Huge X-flare just hit us...

WA2TP
 

Ulli, I saw the same here. all of s sudden spots count uploads went from ~50-60spots  per cycle down to 6-10.
Image preview


Re: Intl. WSPR Beacon Project - Grafana Dashboards

Roland
 
Edited


Re: Intl. WSPR Beacon Project - Grafana Dashboards

KD2OM
 

I am hearing the beacon on 40,30 and 20. Between -13 and -27 SNR


73

Steve KD2OM

On 7/3/21 1:01 PM, Roland wrote:
Just a quick heads up, first WSPR Beacon has gone live. IUS2PJI is band hopping on 8 Bands. More Beacons will follow very soon
https://www.google.com/maps/d/u/1/edit?mid=14X0GJ4vSQ7D8piZfuHDs902Y9tINuPqB&usp=sharing

73
Roland


Huge X-flare just hit us...

ON5KQ
 

Within a few minutes all signals on shortwave are complete erased and only noise can be heard from 1.8 to 30Mhz....
Just building at the antennas, I thought my equipment is hit by a static discharge and dead (as we have some thunderstorms arround) but is is just the X-flare switching the ionosphere off....

Yes, the sun is awake, and instead of builing beverage antennas for the low bands the coming years is building big Yagis for 20m and up.... hi

73s,
Ulli


Re: Intl. WSPR Beacon Project - Grafana Dashboards

Roland
 
Edited

Just a quick heads up, first WSPR Beacon has gone live. IU2PJI is band hopping on 8 Bands. More Beacons will follow very soon
https://www.google.com/maps/d/u/1/edit?mid=14X0GJ4vSQ7D8piZfuHDs902Y9tINuPqB&usp=sharing

73
Roland


Re: How to configure RTL_SDR

Hidehiko Komachi - JA9MAT
 

Thanks Rob quickly reply!

OK all about RTL_SDR issues, I will continue to looking for your progress to resolve it.

"Wsprdaemon" is the best for energy saving wspr receiving.

73 and thanks for nice project, JA9MAT Hidehiko. 


Re: How to configure RTL_SDR

Rob Robinett
 

Welcome Hidehiko,

The RTL-SDR support in WD V2.x is very experimental and even I haven't used it in many months.
'wd -i' is used with baseband AUDIO input devices which is functional but to use it you will need to attach one or more USB audio input dongles.
In WD v3.x I am adding full support for RTL-SDRs and any other SDRs which have ;SoapyAPI' drivers with the primary goal of having WD support the VHF/UHF bands not supported by the Kiwi. 
However I have foudn that the RTL-SDR drivers tune very inaccurately by WSPR requirements.  When I program a GSPDO driven RTL-SDR to tune up 1 Hz, it may jump up 400 Hz or down 200 Hz. 
I suspect that WSPR users of RTL-SDRs are able to fiddle with their tuning and get WSPR decoding to work, but I haven't been able to find a SW algorithm which can do that tuning adjustment.
So until I (or someone else) finds a way to work around that problem, I don't think RTL-SDRs are going to be useful with WD.

Rob


How to configure RTL_SDR

Hidehiko Komachi - JA9MAT
 

Hello,
I began to install and connect two of RTL_SDR at RaspberryPi 3B+.
I configure wsprdaemon.comf to active two of RTL_SDR and run wsprdaemon correctly.
But nothing seems to happen.

So I check audio devices by "./wsprdaemon.sh -i".
Then the following message returned.

---------------------------------
Audio input devices:

**** List of CAPTURE Hardware Devices ****

 

Can't find any audio INPUT devices on this server
--------------------------------

I don't understand the configuration about RTL_SDR deeply.
So if there is a sample wsprdaemon.conf file for RTL_SDR ?
Sorry but have no KiwiSDR yet.

73, JA9MAT Hidehiko.


getting data

Jim Lill
 

I have added this to the data system I maintain. It's for those wanting to do local plotting etc. and not use Grafana or other means

http://jimlill.com:8088/getdata.html/?call=WA2ZKD

change my call to your own 


Re: kfs Omni - signal levels

ON5KQ
 

Hi Rob,
This night, 22 June just after local Midnight in California, I checked the Omni Antenna at kfs again:
- both ports indeed show exactly the same signal (port 8073 and 8083) as it should - as it is the same signal
- the signal level seem to be further reduced as the background noise on 10m today is at -108dBm level, which is ok...  my earlier observation (see above) showed a background noise level on 10m (at the time of dead band) about 6-8db higher...
- no OV clipping indication
- no IMD at the low end frequency (1.8...3Mhz)
- notch arround 3.5Mhz persists...

Last Sunday, I checked the bands on all antennas in the local morning time at earlier daylight hours. I hoped, that noise and interference may be little less than during the week, assuming sourrounding light industrial/commercial activity be more quit on Sunday.
I was shocked however how strong the QRM from broadband noise sources was at about 8h30 in the morning on the high bands especially 12 and 10m... The Noise was at least 10db higher than I have it usually here. That said, I believe my antenna's net gain is probably not less than what the KFS kiwi's see there. I am using a terminated Rhombic on 10m with additionally 17db net preamplifier gain.
Still my noise level is 10db lower !   Noise level on 10m on all antennas at kfs was extremely high (in the -90s dbm !)
I was not prepared to make a detailed report and didn't have the time at Sunday unfortunately, but I will check it again next weekend.

Now at midnight today the noise on 10m is much lower at kfs = there must be something locally radiating like hell to produce that bad reception last Sunday morning (broadband power line noise ?! Influence of local rain shower ?)
May be other local Hams can have a further look to that as well and report the reception on 12m/10m during local daylight hours from kfs...

Greetings to KH6!

Ulli, ON5KQ


Re: 8088 Page restored

Jim Lill
 

For those that have asked about the dupe % etc.   I did some testing and found that simply consumes too much processing time and with spots > 2M would be an issue

On 6/20/21 5:46 AM, Jim Lill wrote:
After a power loss related issue, a few days ago. The header of my Ranking Page is now working again.

-Jim




261 - 280 of 581