Date
1 - 6 of 6
Second KIWI setup?
John
My first KIWI is using 8 bands of vertical 10M -80M. Mu wsprdaemon.conf lists:
"KIWI_0 192.168.2.160:8073 TI4JWC EK70wb and declare WSPR_SCHEDULE_complex=(
"06:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"07:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"08:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"09:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"10:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"11:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"12:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"13:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"14:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"
"15:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10"...................................
For the schedule. For the second KIWI on the Hex beam I think this will be the new arangement. declare RECEIVER_LIST=(
"KIWI_0 192.168.2.160:8073 TI4JWC EK70wb
KIWI_1 192.168.2.161:8073 TI4JWC EK70WB
and declare WSPR_SCHEDULE_complex=(
"06:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"07:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"08:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"09:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"10:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"11:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10 "
"12:00 KIWI_0,80 KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17 KIWI_0,15 KIWI_0,12 KIWI_0,10
for the combined schedule. I am not clear how to use the "Merge" assignments. I want to avoid double listing the same spots. John TI4JWC |
|
Rob Robinett
It appears that all of your rx channels are the same all day, so your config file can be much simpler. mail your config file and I'll fix it up. My first KIWI is using 8 bands of vertical 10M -80M. Mu wsprdaemon.conf lists: --
|
|
Edward (W3ENR / K3WRG)
On 1/5/21 5:59 PM, John via groups.io wrote:
I am not clear how to use the "Merge" assignments. I want to avoid double listing the same spots.I'm interested in similar antenna experiments, and have the same question about avoiding duplicate submissions. Of course I could put a suffix on the callsign of one of the Kiwis, but it would be preferable to report both under the same call. I fear, though, that there's no easy answer. EH |
|
Rob Robinett
WD fully supports getting spots for 2 or more Kiwis, selecting one set of the best received spots and uploading only one copy of each spot under the single receiver call sign to wsprnet.org.
In addition, WD creates a log file where all spots are listed and a comparison of the SNR of the spots is listed.
Further, all spots from all receives can be recorded in the wsprdaemon.org SQL database for further analysis and text and graphs using SQL and Grafana.
Download WD and you will find in the config file a template for MERGE receivers.
Rob |
|
Gwyn Griffiths
Edward,
Your interests in antenna experiments are very much catered for through Rob's WD script and the Grafana dashboards I've created. To add to Rob's answer with my own example. Having looked at Rob's template, you can see the context for these key lines, where I've substituted *** for the passwords. First the receiver list. The receiver name on the left is included in each spot data row sent to the wsprdaemon database whereas it is the third column that is used as the identifier to wsprnet. In this example I want to identify between the two receivers on wsprnet on some bands, hence the G3ZIL and G3ZIL/S. I'm also creating a merged receiver, where the best SNR between G3ZIL_1 and G3ZIL_2 is reported to wsprnet as G3ZIL; as Rob says, this avoids double reporting to wsprnet. However, the original individual receiver data is available in the wsprdaemon database. declare RECEIVER_LIST=(
"G3ZIL_1 10.0.1.44:8073 G3ZIL IO90hw ****"
"G3ZIL_2 10.0.1.78:8074 G3ZIL IO90hw ****"
"G3ZIL_4 10.0.1.44:8073 G3ZIL/S IO90hw ****"
"MERGED_RX G3ZIL_1,G3ZIL_2 G3ZIL IO90hw ****"
)
And so, we can look at the data from Callsign G3ZIL and receivers G3ZIL_1 and G3ZIL_2 on the Grafana dashboard at http://logs2.wsprdaemon.org:3000/d/MBseDfvMz/merged-receiver-comparisons-from-wsprdaemon-tables?orgId=1&from=now-2d&to=now-1m&var-Callsign=G3ZIL&var-receiver_A=G3ZIL_1&var-receiver_B=G3ZIL_2&var-band_m=20 These dashboards are taking quite some time for initial load and then some panels take a fair time - but I hope that via this comprehensive example dashboard you can see that wsprdaemon really does provide a great starting point for antenna experimentation. Check out more information on our Grafana dashboards at: http://wsprdaemon.org/ewExternalFiles/Setting_up_Timescale_Grafana_dashboards_V2-2.pdf I have dropped you an email to your address on QRZ.com with the password. 73 Gwyn |
|
Edward (W3ENR / K3WRG)
Well, I guess I'm out of touch. I've been running WD for
months. :-) (W3ENR) EH
On 1/5/21 10:12 PM, Rob Robinett wrote:
|
|