Date
1 - 5 of 5
Overloads
|
Rob,
toggle quoted message
Show quoted text
I was probably getting overloads when I had the minicircuits amplifier on as well as when I am on the shares nets at noon and 7pm edt. Steve . On Aug 11, 2022, at 17:28, Rob Robinett <rob@...> wrote:
|
|
|
|
Rob Robinett
Steve, I have just added the command 'wd-ovt' to the WD 3.0.3.3 build. It lists the four most recent overload lines from each rx job which reports them. Your systems seem to have almost none since WD was restarted about 35 hours ago. Rob plex@Plexserver:~/wsprdaemon$ git pull Updating 3524505..d0b3975 Fast-forward .wd_bash_aliases | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) plex@Plexserver:~/wsprdaemon$ rc plex@Plexserver:~/wsprdaemon$ date Thu 11 Aug 2022 09:23:44 PM GMT plex@Plexserver:~/wsprdaemon$ wd-ovt /dev/shm/wsprdaemon/recording.d/BE/20/decoding_daemon.log has 59 OV lines, the most recent 4 are: Sat 06 Aug 2022 14:20:22 UTC: decoding_daemon() The KiwiSDR reported 45 overload events in this 2 minute cycle Sat 06 Aug 2022 14:22:26 UTC: decoding_daemon() The KiwiSDR reported 8 overload events in this 2 minute cycle Sat 06 Aug 2022 14:24:25 UTC: decoding_daemon() The KiwiSDR reported 2 overload events in this 2 minute cycle Sat 06 Aug 2022 14:28:31 UTC: decoding_daemon() The KiwiSDR reported 4 overload events in this 2 minute cycle plex@Plexserver:~/wsprdaemon$ On Thu, Aug 11, 2022 at 4:12 AM KD2OM <steve@...> wrote: So I guess as long as I don't get new ones the overload events are not happening. --
|
|
|
|
So I guess as long as I don't get new ones the overload events are not happening.
Steve KD2OM |
|
|
|
Rob Robinett
The lines displayed by 'wd-ovs' come from searching all of the decoding_daemon.log files and the results are sorted by the number of overload events in a 2 minute cycle. So the lines are *not* sorted by time but by the 11th space-separated field on those log lines: plex@Plexserver:~$ alias wd-ovs alias wd-ovs='grep "[^0] overload events in this 2 minute cycle" `find /dev/shm/wsprdaemon/ -name decoding_daemon.log` | sort -k 11,11n ' plex@Plexserver:~$ WD 3.0 truncates log files when they grow larger than 1MB, so there is no defined start time for the lines in each log file: plex@Plexserver:~$ head -n 1 `find /dev/shm/wsprdaemon/ -name decoding_daemon.log` | head ==> /dev/shm/wsprdaemon/recording.d/VE/10/decoding_daemon.log <== Wed 10 Aug 2022 23:11:04 GMT: wd_logger() logfile 'decoding_daemon.log' size 1000104 and lines 6292 has grown too large, so truncating the first 1573 lines of it ==> /dev/shm/wsprdaemon/recording.d/VE/10/W_120/decoding_daemon.log <== Fri 05 Aug 2022 11:48:03 UTC: decode_wpsr_wav_file() Decode file 220805_1146.wav for frequency 28124600 and send stdout to wsprd_stdout.txt. rx_khz_offset=0, wsprd_cmd_flags='-C 5000 -o 4 -d' ==> /dev/shm/wsprdaemon/recording.d/VE/12/decoding_daemon.log <== Wed 10 Aug 2022 23:09:03 UTC: cleanup_wav_file_list() Given check_file_list[3]='20220810T230600Z_24924600_usb.wav 20220810T230700Z_24924600_usb.wav 20220810T230800Z_24924600_usb.wav' ==> /dev/shm/wsprdaemon/recording.d/VE/12/W_120/decoding_daemon.log <== plex@Plexserver:~$ On Wed, Aug 10, 2022 at 7:35 PM KD2OM <steve@...> wrote: When do old ov events clear? I am showing some from the 6th of August still today the 11th. --
|
|
|
|
When do old ov events clear? I am showing some from the 6th of August still today the 11th.
73 Steve KD2OM |
|
|