Date
1 - 9 of 9
WD config errors
John
I am still seeing ERRORS when I start WD. What is my config error?
John
TI4JWC
=====================
John
TI4JWC
=====================
pi@raspberrypi:~/wsprdaemon $ wd -a -V
wsprdaemon.sh Copyright (C) 2020 Robert S. Robinett
This program comes with ABSOLUTELY NO WARRANTY; for details type './wsprdaemon.sh -h'
This is free software, and you are welcome to redistribute it under certain conditions. execute'./wsprdaemon.sh -h' for details.
wsprdaemon depends heavily upon the 'wsprd' program and other technologies developed by Joe Taylor K1JT and others, to whom we are grateful.
Goto https://physics.princeton.edu/pulsar/K1JT/wsjtx.html to learn more about WSJT-x
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,20' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,17' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,15' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,12' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
ERROR: in WSPR_SCHEDULE line '00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10', job 'MERGED_0_1,10' specifies receiver 'MERGED_0_1' not found in RECEIVER_LIST
++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++
# To enable these options, remove the leading '#' and modify SIGNAL_LEVEL_UPLOAD_ID from "AI6VN" to your call sign:
#SIGNAL_LEVEL_UPLOAD="noise" ### If this variable is defined and not "no", AND SIGNAL_LEVEL_UPLOAD_ID is defined, then upload signal levels to the wsprdaemon cloud database
### SIGNAL_LEVEL_UPLOAD_MODE="no" => (Default) Upload spots directly to wsprnet.org
### SIGNAL_LEVEL_UPLOAD_MODE="noise" => Upload extended spots and noise data. Upload spots directly to wsprnet.org
### SIGNAL_LEVEL_UPLOAD_MODE="proxy" => In addition to "noise", don't upload to wsprnet.org from this server. Regenerate and upload spots to wsprnet.org on the wsprdaemon.org server
SIGNAL_LEVEL_UPLOAD="yes" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then upload extended spots and noise levels to the logs.wsprdaemon.org database and graphics file server.
SIGNAL_LEVEL_UPLOAD_ID="TI4JWC" ### The name put in upload log records, the the title bar of the graph, and the name used to view spots and noise at that server.
SIGNAL_LEVEL_UPLOAD_GRAPHS="yes" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then FTP graphs of the last 24 hours to http://wsprdaemon.org/graphs/SIGNAL_LEVEL_UPLOAD_ID
#SIGNAL_LEVEL_LOCAL_GRAPHS="no" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then make graphs visible at http://localhost/
##############################################################
### The RECEIVER_LIST() array defines the physical (KIWI_xxx,AUDIO_xxx,SDR_xxx) and logical (MERG...) receive devices available on this server
### Each element of RECEIVER_LIST is a string with 5 space-seperated fields:
### " ID(no spaces) IP:PORT or RTL:n MyCall MyGrid KiwPassword Optional SIGNAL_LEVEL_ADJUSTMENTS
### [[DEFAULT:ADJUST,]BAND_0:ADJUST[,BAND_N:ADJUST_N]...]
### A comma-separated list of BAND:ADJUST pairs
### BAND is one of 2200..10, while ADJUST is in dBs TO BE ADDED to the raw data
### So If you have a +10 dB LNA, ADJUST '-10' will LOWER the reported level so that your reports reflect the level at the input of the LNA
### DEFAULT defaults to zero and is applied to all bands not specified with a BAND:ADJUST
declare RECEIVER_LIST=(
"KIWI_0 192.168.2.160:8073 TI4JWC EK70wb 6105
KIWI_1 192.168.2.161:8073 TI4JWC EK70wb 6105
MERGED_0_1 KIWI_0 KIWI_1 TI4JWC EK70wb " )
### This table defines a schedule of configurations which will be applied by '-j a,all' and thus by the watchdog daemon when it runs '-j a,all' ev ery odd two minutes
### The first field of each entry in the start time for the configuration defined in the following fields
### Start time is in the format HH:MM (e.g 13:15) and by default is in the time zone of the host server unless ',UDT' is appended, e.g '01:30,UDT'
### Following the time are one or more fields of the format 'RECEIVER,BAND'
### If the time of the first entry is not 00:00, then the latest (not necessarily the last) entry will be applied at time 00:00
### So the form of each line is "START_HH:MM[,UDT] RECEIVER,BAND... ". Here are some examples:
declare WSPR_SCHEDULE_simple=(
"00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30
MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10 " )
###declare WSPR_SCHEDULE_complex=(
### "06:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10" ### KIWI_0 => 7 rx channels (80/40/30/20/17/15/../10), KIWI_1 => 7 rx channels (../40/30/20/17/15/12/10)
### "18:00 MERGED_0_1,80 MERGED_0_1,40 MERGED_0_1,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 KIWI_0,12 KIWI_1,10" ### KIWI_0 => 7 rx channels (80/40/30/20/17/15/12/..), KIWI_1 => 7 rx channels (80/40/30/20/17/15/../10)
###)
### This array WSPR_SCHEDULE defines the running configuration. Here we make the simple configuration defined above the active one:
declare WSPR_SCHEDULE=( "${WSPR_SCHEDULE_simple[@]}" )
Gwyn Griffiths
John
I think you need a comma in the line below between KIWI_0 and KIWI_1
regards
Gwyn G3ZIL
toggle quoted message
Show quoted text
I think you need a comma in the line below between KIWI_0 and KIWI_1
regards
Gwyn G3ZIL
On Thu, Jan 7, 2021 at 06:02 PM, John wrote:
MERGED_0_1 KIWI_0 KIWI_1 TI4JWC EK70wb " )
John
Here is with a comma added. I get the same errors..
# To enable these options, remove the leading '#' and modify SIGNAL_LEVEL_UPLOAD_ID from "AI6VN" to your call sign:
#SIGNAL_LEVEL_UPLOAD="noise" ### If this variable is defined and not "no", AND SIGNAL_LEVEL_UPLOAD_ID is defined, then upload signal levels to the wsprdaemon cloud database
### SIGNAL_LEVEL_UPLOAD_MODE="no" => (Default) Upload spots directly to wsprnet.org
### SIGNAL_LEVEL_UPLOAD_MODE="noise" => Upload extended spots and noise data. Upload spots directly to wsprnet.org
### SIGNAL_LEVEL_UPLOAD_MODE="proxy" => In addition to "noise", don't upload to wsprnet.org from this server. Regenerate and upload spots to wsprnet.org on the wsprdaemon.org server
SIGNAL_LEVEL_UPLOAD="yes" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then upload extended spots and noise levels to the logs.wsprdaemon.org database and graphics file server.
SIGNAL_LEVEL_UPLOAD_ID="TI4JWC" ### The name put in upload log records, the the title bar of the graph, and the name used to view spots and noise at that server.
SIGNAL_LEVEL_UPLOAD_GRAPHS="yes" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then FTP graphs of the last 24 hours to http://wsprdaemon.org/graphs/SIGNAL_LEVEL_UPLOAD_ID
#SIGNAL_LEVEL_LOCAL_GRAPHS="no" ### If this variable is defined as "yes" AND SIGNAL_LEVEL_UPLOAD_ID is defined, then make graphs visible at http://localhost/
##############################################################
### The RECEIVER_LIST() array defines the physical (KIWI_xxx,AUDIO_xxx,SDR_xxx) and logical (MERG...) receive devices available on this server
### Each element of RECEIVER_LIST is a string with 5 space-seperated fields:
### " ID(no spaces) IP:PORT or RTL:n MyCall MyGrid KiwPassword Optional SIGNAL_LEVEL_ADJUSTMENTS
### [[DEFAULT:ADJUST,]BAND_0:ADJUST[,BAND_N:ADJUST_N]...]
### A comma-separated list of BAND:ADJUST pairs
### BAND is one of 2200..10, while ADJUST is in dBs TO BE ADDED to the raw data
### So If you have a +10 dB LNA, ADJUST '-10' will LOWER the reported level so that your reports reflect the level at the input of the LNA
### DEFAULT defaults to zero and is applied to all bands not specified with a BAND:ADJUST
declare RECEIVER_LIST=(
"KIWI_0 192.168.2.160:8073 TI4JWC EK70wb 6105
KIWI_1 192.168.2.161:8073 TI4JWC EK70wb 6105
MERGED_0_1 KIWI_0, KIWI_1 TI4JWC EK70wb " )
### This table defines a schedule of configurations which will be applied by '-j a,all' and thus by the watchdog daemon when it runs '-j a,all' ev ery odd two minutes
### The first field of each entry in the start time for the configuration defined in the following fields
### Start time is in the format HH:MM (e.g 13:15) and by default is in the time zone of the host server unless ',UDT' is appended, e.g '01:30,UDT'
### Following the time are one or more fields of the format 'RECEIVER,BAND'
### If the time of the first entry is not 00:00, then the latest (not necessarily the last) entry will be applied at time 00:00
### So the form of each line is "START_HH:MM[,UDT] RECEIVER,BAND... ". Here are some examples:
declare WSPR_SCHEDULE_simple=(
"00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30
MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10 " )
###declare WSPR_SCHEDULE_complex=(
### "06:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10" ### KIWI_0 => 7 rx channels (80/40/30/20/17/15/../10), KIWI_1 => 7 rx channels (../40/30/20/17/15/12/10)
### "18:00 MERGED_0_1,80 MERGED_0_1,40 MERGED_0_1,30 MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 KIWI_0,12 KIWI_1,10" ### KIWI_0 => 7 rx channels (80/40/30/20/17/15/12/..), KIWI_1 => 7 rx channels (80/40/30/20/17/15/../10)
###)
### This array WSPR_SCHEDULE defines the running configuration. Here we make the simple configuration defined above the active one:
declare WSPR_SCHEDULE=( "${WSPR_SCHEDULE_simple[@]}" )
Glenn Elmore
On 1/7/21 12:40 PM, John via groups.io wrote:
WD is a bit fussy about white space and delimiters. Check your .conf very carefully.
Glenn
Here is with a comma added. I get the same errors..The comma was no doubt a problem but there's another thing, perhaps formatting was changed in posting. I don't know about the line wrap, but your entry for schedule 00:00 looks suspect
declare WSPR_SCHEDULE_simple=(I see it as two lines and I can't tell if that's what you actually have. I think it needs to be a single line.
"00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30
MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15 MERGED_0_1,12 MERGED_0_1,10 " )
WD is a bit fussy about white space and delimiters. Check your .conf very carefully.
Glenn
Rob Robinett
I am away from home. I’ll check it later today when I get home
On Thu, Jan 7, 2021 at 12:20 PM Glenn Elmore <n6gn@...> wrote:
On 1/7/21 12:40 PM, John via groups.io wrote:
> Here is with a comma added. I get the same errors..
The comma was no doubt a problem but there's another thing, perhaps
formatting was changed in posting. I don't know about the line wrap,
but your entry for schedule 00:00 looks suspect
> declare WSPR_SCHEDULE_simple=(
> "00:00 KIWI_0,80 KIWI_0,40 KIWI_0,30
> MERGED_0_1,20 MERGED_0_1,17 MERGED_0_1,15
> MERGED_0_1,12 MERGED_0_1,10 " )
I see it as two lines and I can't tell if that's what you actually have.
I think it needs to be a single line.
WD is a bit fussy about white space and delimiters. Check your .conf
very carefully.
Glenn
--
Rob Robinett
Hi John,
I'm sorry but in the stress of yesterday's insurrection I failed to test the conf file I emailed you which included a corrupt definition of your RECEIVER_LIST.
That list must include one or more strings, each with 5 space-separated strings, e.g.
declare RECEIVER_LIST=("KIWI_0 192.168.2.160:8073 TI4JWC EK70wb PASSWORD"
"KIWI_1 192.168.2.161:8073 TI4JWC EK70wb PASSWORD"
"MERGED_0_1 KIWI_0,KIWI_1 TI4JWC PASSWORD"
)
The conf file I sent you was missing the double quotes I highlighted in red above, so WD saw there was only one multi-line receiver definition of KIWI_0.
There might have been a second problem with the '\r' (Carriage Return) characters added to each line by your Windows text editor.
I stripped those CRs out using the linux utility 'dos2unix' before editing your conf file.
If you make further edits from Windows and find WD fails to start, it would be safest to edit your conf file from the desktop of the Pi using the text editor supplied as part of that Desktop environment.
Rob
I made the 00:00 a single line --- same error
j
--