Bruce, It's amazing how far you can go with almost nothing. I am usually running QRO here at 200 mW -:) into an old Cushcraft R7 usually on 7 and 14 but then again there are some crafty

Some final comments on my "radio limbo" experiment. I've left it running since October 7th and will shut it down today (October 17th), in order to reclaim the step attenuator I've been using to

Gwyn, Thank you for the quick feedback, happy to know the noise data is being uploaded & with the correct location. Doesn't matter to me whether it is -T or /T, either way it helps me distinguish the

Hello Bruce Your noise data are being reported to the database. There's lots of documentation on wsprdaemon.org on how to query the database, but a quick query brings up the following as a few recent

After a bit of a struggle with naming conventions for my remote receiver site 'KX4AZ/T' at EN74gc, I was able to get wsprdaemon going yesterday on the Pi4, so that spots are now being reported from my

Rolf Using "Quiet receiving site", curve C and "galactic noise" curve D from ITU-R P.372.8 as a guideline, one can probably stand a system noise more than 20 dB above KTB before it impacts SNR from a

Rolf, I am using three different amplifiers built by N4CY Everett Sharp. They all are 11 dB gain. He has changed the version several times, one has a relay to disconnect the antenna when no power is

Not sure I’d consider myself a big gun, but I have had very good results with high spot counts. I am not using any and pre-amplification on the resonant antennas. The only antenna with a pre-amp

Hi again y'all I have run my Kiwi here with AM filter for more than a year now almost 24/7 and I am very happy with it. I am only using an old ground mounted Cushcraft R7. I am still planning to

You are correct! Right after my last post I went back to the original example conf file example (from the web site) and changed the receiver name to remove the '/T' suffix from the call sign, while

I think the problem may be the names. There is no need to use a call as the receiver name. It gets the call from the config file. Your receiver names should be like Kiwi_1, Kiwi_2, etc. if is is an

Also, these are the current contents in the wsprdaemon.log file: Fri 15 Oct 2021 09:40:49 AM UTC: watchdog_daemon() starting as pid 2904 Fri 15 Oct 2021 09:40:49 AM UTC: WARNING:

Thanks for the suggestion, I removed the _1 in the receiver name used in the conf file, rebooted and restarted wsprdaemon. Still not uploading any spots, though the status shows a longer list, with

I'm not sure it likes _ in the RX name or if the various people who track spots do

When I went back and re-read the original installation message I realized it was simply asking me for permission to create a RAM drive, so I answered YES and proceeded from there. After editing the

see man fstab

Thank you, I located the fstab file in the etc directory and will halt the wsprdaemon and add that line.....I am curious about the "0 0" after the size=300m term - what function does it serve?

There is also an access speed issue that the ram disk helps. this line needs to be added to the end of your /etc/fstab file tmpfs /tmp/wsprdaemon tmpfs defaults,noatime,nosuid,size=300m

Very new to Linux & Pi, so being very cautious...but also not afraid to ask the very dumb questions that follow below. When I initiated a new installation of Wsprdaemon, it displayed a warning

Thank you Rob No doubt there could be a difference between a narrow band Air Spy and the Kiwi in a band hopping application. Another possible issue that could influence the outcome will be the