Debugging site with frequent overloads needed


KD2OM
 

Rick,

Is your Sky Loop the Chameleon CHA-SKYLOOP or a home brew one? 

73

Steve KD2OM

On 8/10/22 03:56, kk6pr wrote:

Thanks Rob.

My Sky Loop antenna goes through a 4-way splitter to 3 Kiwis and an AirSpy HF+ Discovery.  Only the 80 - 30 meter Kiwi has a preamp.

There is only one Kiwi connected to the EFHW - it seems to be getting the most overloads.

I've installed a Kay Step Attenuator inline with the EFHW.  I'm not seeing any overloads now, but I will keep an eye on it and try to determine a good value of attenuation if needed.

I have everything I need to install the Bodnar clock - except the internal cable for the Kiwis, which should arrive tomorrow.  Probably won't get it installed before tomorrow's meeting, but hopefully sometime that afternoon.

73
Rick / KK6PR





kk6pr
 

Edit - sorry, only the 20 - 10 meter Kiwi has a preamp.


kk6pr
 

Thanks Rob.

My Sky Loop antenna goes through a 4-way splitter to 3 Kiwis and an AirSpy HF+ Discovery.  Only the 80 - 30 meter Kiwi has a preamp.

There is only one Kiwi connected to the EFHW - it seems to be getting the most overloads.

I've installed a Kay Step Attenuator inline with the EFHW.  I'm not seeing any overloads now, but I will keep an eye on it and try to determine a good value of attenuation if needed.

I have everything I need to install the Bodnar clock - except the internal cable for the Kiwis, which should arrive tomorrow.  Probably won't get it installed before tomorrow's meeting, but hopefully sometime that afternoon.

73
Rick / KK6PR





Rob Robinett
 

Hi All,

To simplify viewing the OV events I have added the 'wd-ovs' alias to WD 3.0.3.3.  
So to utilize this OV monitoring feature:

1) cd ~/wsprdaemon
2) git pull
3) rc       (this loads the wd-ovs alias)
4) wdz
5) wda

Then wait 10+ minutes before running 'wd-ovs' may print out useful log lines like that below.  It sorts by # of overload events, so you may want to pipe its output to another sort by date/time.

Rick, 

I have installed 3.0.3 on both your machine and after running for a few minutes I see severe overloading on Rick's machine.

wsprdaemon@KK6PR-WD-TC:~/wsprdaemon$ wd-ovs | tail
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/20/decoding_daemon.log:Wed 10 Aug 2022 00:18:30 UTC: decoding_daemon() The KiwiSDR reported 1781 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/80/decoding_daemon.log:Tue 09 Aug 2022 23:56:24 UTC: decoding_daemon() The KiwiSDR reported 1868 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/40/decoding_daemon.log:Wed 10 Aug 2022 00:16:30 UTC: decoding_daemon() The KiwiSDR reported 1879 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/40/decoding_daemon.log:Wed 10 Aug 2022 00:20:23 UTC: decoding_daemon() The KiwiSDR reported 1882 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/30/decoding_daemon.log:Wed 10 Aug 2022 00:20:23 UTC: decoding_daemon() The KiwiSDR reported 1892 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/20/decoding_daemon.log:Wed 10 Aug 2022 00:20:34 UTC: decoding_daemon() The KiwiSDR reported 1897 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/80/decoding_daemon.log:Wed 10 Aug 2022 00:20:19 UTC: decoding_daemon() The KiwiSDR reported 1941 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/30/decoding_daemon.log:Tue 09 Aug 2022 23:56:29 UTC: decoding_daemon() The KiwiSDR reported 1987 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/20/decoding_daemon.log:Wed 10 Aug 2022 00:16:30 UTC: decoding_daemon() The KiwiSDR reported 2013 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_4_EFHW/30/decoding_daemon.log:Wed 10 Aug 2022 00:16:31 UTC: decoding_daemon() The KiwiSDR reported 2035 overload events in this 2 minute cycle
wsprdaemon@KK6PR-WD-TC:~/wsprdaemon$


Tom,
 
You are recording only a few OV events:

wsprdaemon@WA2TPWDPROD:~/wsprdaemon$ wd-ovs | tail
/dev/shm/wsprdaemon/recording.d/KIWI_2/630/decoding_daemon.log:Wed 10 Aug 2022 00:24:17 UTC: decoding_daemon() The KiwiSDR reported 15 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_2/80eu/decoding_daemon.log:Wed 10 Aug 2022 00:24:07 UTC: decoding_daemon() The KiwiSDR reported 15 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_6/10/decoding_daemon.log:Tue 09 Aug 2022 23:24:05 UTC: decoding_daemon() The KiwiSDR reported 15 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_6/10/decoding_daemon.log:Wed 10 Aug 2022 00:24:02 UTC: decoding_daemon() The KiwiSDR reported 15 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_6/40/decoding_daemon.log:Wed 10 Aug 2022 00:04:12 UTC: decoding_daemon() The KiwiSDR reported 15 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_2/60/decoding_daemon.log:Wed 10 Aug 2022 00:24:08 UTC: decoding_daemon() The KiwiSDR reported 16 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_2/80eu/decoding_daemon.log:Wed 10 Aug 2022 00:04:11 UTC: decoding_daemon() The KiwiSDR reported 16 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_6/80eu/decoding_daemon.log:Wed 10 Aug 2022 00:04:18 UTC: decoding_daemon() The KiwiSDR reported 17 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_2/40/decoding_daemon.log:Wed 10 Aug 2022 00:24:18 UTC: decoding_daemon() The KiwiSDR reported 18 overload events in this 2 minute cycle
/dev/shm/wsprdaemon/recording.d/KIWI_2/15/decoding_daemon.log:Wed 10 Aug 2022 00:24:06 UTC: decoding_daemon() The KiwiSDR reported 19 overload events in this 2 minute cycle
wsprdaemon@WA2TPWDPROD:~/wsprdaemon$




On Tue, Aug 9, 2022 at 12:46 PM kk6pr <pointreyes@...> wrote:
Rob,

As you may recall, my neighbor across the street gets on 80 meters every morning around 8 or 9 am to talk with his buddies, which generates a lot of overloads.  He occasionally gets on the air during other parts of the day using FT8 on various bands as well.

I've just upgraded to Version 3.0.3.3, perhaps my site will have the number of overloads you need.

73
Rick / KK6PR



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


WA2TP - Tom
 

Rob,

 I'm not sure what value of frequent OV's may is needed,  but here are my OV events/uptime by Kiwi:

KIWI1
adc_ov=6576
uptime=159371

KIWI2
adc_ov=18024
uptime=387076


KIWI3
adc_ov=814
uptime=388771
KIWI4
adc_ov=1245
uptime=388861
KIWI5
adc_ov=6
uptime=390625
KIWI6
adc_ov=11507
uptime=389389
KIWI7
adc_ov=7593
uptime=393015
Let me know if any of this is helpful.
You already have access to the system.

Tom
WA2TP



From: wsprdaemon@groups.io <wsprdaemon@groups.io> on behalf of Rob Robinett <rob@...>
Sent: Tuesday, August 9, 2022 3:30 PM
To: wsprdaemon@groups.io <wsprdaemon@groups.io>
Subject: [wsprdaemon] Debugging site with frequent overloads needed
 
I am debugging one of the final new capabilities of WD 3.0 and need a WD site which experiences frequent overload events.
Until now WD has monitored the number of OV events by instructing kiwirecorder to output a line of "ADC OV" each time it detects an overload event.  Those lines are output to its standard out which WD saves in a log file.
However when there are many OV events that log file can grow with no bound on its size, so WD has to kill and restart a kiwirecorder session when that log file grows too large.
Many Kiwi SW version ago, at my request John Seamons added the 'adc_ov=NNNN' line to the Kiwi's status page and I am finally getting around to having WD use that /status page value.
Doing so should reduce or eliminate entirely the 'random' restarts of kiwirecorder sessions.

I have just checked in the code with this change which will report itself as version 3.0.3.3:

wsprdaemon@MauiWebSDR:~$ wdv
Version = 3.0.3.3
wsprdaemon@MauiWebSDR:~$

Since neither KFS nor Maui experiences many OV events, it may take some time for their WD log files to contain lines reporting the proper operation of this new code.  So if you know your site is subject to OV's I would appreciate the chance to install and monitor the operation of this new code


kk6pr
 

Rob,

As you may recall, my neighbor across the street gets on 80 meters every morning around 8 or 9 am to talk with his buddies, which generates a lot of overloads.  He occasionally gets on the air during other parts of the day using FT8 on various bands as well.

I've just upgraded to Version 3.0.3.3, perhaps my site will have the number of overloads you need.

73
Rick / KK6PR


Rob Robinett
 

I am debugging one of the final new capabilities of WD 3.0 and need a WD site which experiences frequent overload events.
Until now WD has monitored the number of OV events by instructing kiwirecorder to output a line of "ADC OV" each time it detects an overload event.  Those lines are output to its standard out which WD saves in a log file.
However when there are many OV events that log file can grow with no bound on its size, so WD has to kill and restart a kiwirecorder session when that log file grows too large.
Many Kiwi SW version ago, at my request John Seamons added the 'adc_ov=NNNN' line to the Kiwi's status page and I am finally getting around to having WD use that /status page value.
Doing so should reduce or eliminate entirely the 'random' restarts of kiwirecorder sessions.

I have just checked in the code with this change which will report itself as version 3.0.3.3:

wsprdaemon@MauiWebSDR:~$ wdv
Version = 3.0.3.3
wsprdaemon@MauiWebSDR:~$

Since neither KFS nor Maui experiences many OV events, it may take some time for their WD log files to contain lines reporting the proper operation of this new code.  So if you know your site is subject to OV's I would appreciate the chance to install and monitor the operation of this new code