Date   

Ok, I'm Officially Impressed With ClickHouse

Greg Beam <ki7mt01@...>
 

Hello All,

I was going through their examples (on my local workstation), testing things out, and getting a feel the CLI / API. I decided to load one of their bigger datasets and play around some. I chose the Airline OnTime-Dataset first and went through all the example queries. This thing is seriously fast, and that's putting it mildly.

I don't know what it would do, or how it would handle, hundreds of concurrent users, but, if it scales with clustering the way it's performing on a single node, it's hard to imagine using anything else (at the price point it offers) with the anticipated volumes WSPR is expecting over the next cycle.

I realize there is still a fair bit of ETL needed before shoving things a into the warehouse, but, I can see use cases of all sorts with this thing.

73's
Greg, KI7MT


Re: ClickHouse / PostreSQL FDW Integrations

Greg Beam <ki7mt01@...>
 

Hello All,

I should have looked a bit further before diving into a complex solution.

Third Party UI Clients are Plentiful

I already have a subscription to JetBrains DataGrip (and others), and it has native support for ClickHouse. All I had to do was look for the connector .. Doooh !!!

In any Case, the more I learn about ClickHouse, the more impressed I become. This thing is powerful, and seriously fast !!

73's
Greg, KI7MT


Re: This is not good - All the more reason for distributed services I suppose

Greg Beam <ki7mt01@...>
 

Disaster recovery / backups are never important until ya need them (been there, done that, lost the data).

I've got a full copy of the WSPRnet dataset also, in multiple locations. Not that I really need to, but, its nice not having to re-download those big files.

I've got data center infrastructure on Azure and AWS in multiple zones also. It's costly to have and maintain, but, it's there when the lights go out in a zone.


Re: This is not good - All the more reason for distributed services I suppose

Rob Robinett
 

We maintain 3 copies of the wsprdaemon.org site:  

1) wsprdameon.org is a cloud server maintained by digitalocean.com on a Silicon Valley server
2) wd1.wsprdaemon.org is a Dell server located in a telco engineering lab in Sacramento California , 200 Km from WD2
3) wd2.wsprdaemon.org is a Dell server located in the Hurricane Electric Tier 1 peering point in Fremont California in Silicon Valley

DNS is handled by Google.

So unless all of California burns up or slides in the Pacific Ocean, I think we have a pretty reliable system


Re: This is not good - All the more reason for distributed services I suppose

admin
 

Yeah that was bad luck. I never considered wspr.live to be important enough to include it in my backups and now it is gone into the cloud forever. The dashboards and the information page are lost.

But I just rewrote the page and will put Grafana back on air soon.

The Database itself is easy to restore in case of loss as long as wsprnet.org is available we can just reimport the data.


ClickHouse / PostreSQL FDW Integrations

Greg Beam <ki7mt01@...>
 

Hello All,

I'm probably late to the party, as usual, but, I was playing around with Phill's wspr.rocks site, and it definitely Rocks on the speed front !!

I'm looking to explore ClickHouse Database solutions a good bit more and was wondering two things:
I have a server set up with ClickHouse and walked through a couple of their DataSet examples. There's no question, the thing is seriously fast.

Thanks

73's
Greg, KI7MT


This is not good - All the more reason for distributed services I suppose

Greg Beam <ki7mt01@...>
 

Just saw this today.

Thankfully, the DB looks to be functional still.


Muting in new firmware of KiwiSDR.

KD2OM
 

Does the threshold control have any effect on kiwirecorder, or is it just for the audio that is heard in the browser?

73
Steve KD2OM


Re: http://jimlill.com/today_int.html Down?

Jim Lill
 

It had a hardware failure. Time permitting, it will arise from the ashes soon...  The scraper portion is running. The analysis section will be awhile and I am doing a rewrite since it is already down.
1310.00


Re: migrate wsprdaemon to Atomicpi

John
 

I spent 3 days trying to get port forwarding to work with SSH server and access with Putty from my windows machine. No problems when I use the local NAT addresses.
But no joy when out on the Internet. I have found that I am behind the ISP fiber router in the house that also provides voice service. I have no access to this router so cannot enable port forwarding I have settled on TeamViewer for remote access.


Re: Conf file example - two receivers, different bands, one Pi

Edward Hammond
 

Great, thank you.  I was just figuring out the wickedness of my ways and fixing my immediate problem when this arrived.

You've gone above and beyond and actually answered what would have been my next question below!  :-)

Thank you!

Edward

On 3/14/21 2:34 PM, Glenn Elmore wrote:
The wd.conf below works to allow to different Kiwi's (GN2 remote and GN0 local) to both post as "N6GN/K", run on both same and different bands and be scheduled throughout the day, though lately I've been running the same 24/7. This is  WSPR_SCHEDULE_merged

Declare the RECEIVER_LIST first, individual Kiwi's come before the merged ones.  Then just call out what you want in the schedule.

THere is a subtle 'gotcha' that you shouldn't run different receiver/gridsquare on the same band as they may post twice rather than once as is desired.

Glenn n6gn


# 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="N6GN"     ### 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="yes"    ### 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 pairsyy
### BAND is one of 2200..10, while AJUST is in dBp TO BE ADDED to the raw data, e.g. '-10' will LOWER the reported level
### DEFAULT defaults to zero and is applied to all bands not specified with a BAND:ADJUST

declare RECEIVER_LIST=(
"GN0            10.0.0.161:8073         N6GN/K       DN70ll kiwis_password DEFAULT:-2.0,2200:11.6,630:10.5,160:4.5,80:1.3,60:0.0,40:-0.7,30:-1.0,20:-0.8,17:-1.0,15:-0.4,12:0.2,10:0.0"
"GN2            10.0.0.102:8075         N6GN/K       DN70jo kiwis_password DEFAULT:-2.0,2200:11.6,630:10.5,160:4.5,80:1.3,60:0.0,40:-0.7,30:-1.0,20:-0.8,17:-1.0,15:-0.4,12:0.2,10:0.0"
"GN3            10.0.0.77:8074          N6GN/K       DN70ll kiwis_password DEFAULT:-2.0,2200:11.6,630:10.5,160:4.5,80:1.3,60:0.0,40:-0.7,30:-1.0,20:-0.8,17:-1.0,15:-0.4,12:0.2,10:0.0"
"GN4            10.0.0.67:8076          N6GN/P       DN70ll kiwis_password DEFAULT:-2.0,2200:11.6,630:10.5,160:4.5,80:1.3,60:0.0,40:-0.7,30:-1.0,20:-0.8,17:-1.0,15:-0.4,12:0.2,10:0.0"
"K6RFT          k6rft.proxy.kiwisdr.com:8073     K6RFT   EM47bg kiwis_password     DEFAULT:0.0"

"MERGED_RX_02   GN0,GN2                 N6GN/K       DN70ll kiwis_password"
"MERGED_RX_23   GN2,GN3                 N6GN/K       DN70ll kiwis_password"
"MERGED_RX_03   GN0,GN3                 N6GN/K       DN70ll kiwis_password"
"MERGED_RX_023  GN0,GN2,GN3             N6GN/K       DN70ll kiwis_password"
"MERGED_RX_034  GN0,GN3,GN4             N6GN/K       DN70ll kiwis_password"
"MERGED_RX_34   GN3,GN4                 N6GN/K       DN70ll kiwis_password"
)

### 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_simple1=(
    "00:00                       GN0,2200 GN0,630 GN0,160 GN0,80 GN0,80eu GN0,60 GN0,40 GN0,30 GN0,20 GN0,17 GN0,15 GN0,12 GN0,10"
)

declare WSPR_SCHEDULE_simple2=(
    "00:00                       GN0,2200 MERGED_RX_03,630 MERGED_RX_03,160 GN0,80eu MERGED_RX_03,80 GN0,60 MERGED_RX_03,40 MERGED_RX_03,30 MERGED_RX_03,20 GN0,17 MERGED_RX_03,15  GN0,12 GN0,10"
)

declare WSPR_SCHEDULE_simple4=(
    "00:00                       GN0,2200 GN0,630 GN0,160 GN0,80 GN0,80eu GN0,60 GN0,40 GN0,30 GN0,20 GN0,17 GN0,15 GN0,12 GN0,10    GN3,80 GN3,40 GN3,30 GN3,20 GN3,17 GN3,15 GN3,10"
)


declare WSPR_SCHEDULE_merged=(
    "00:00                       GN0,2200 GN0,630 GN0,160 MERGED_RX_02,80 GN0,80eu GN0,60eu MERGED_RX_02,40 MERGED_RX_02,30  MERGED_RX_02,20  MERGED_RX_02,17 MERGED_RX_02,15 GN0,12 GN0,10 "
)

declare WSPR_SCHEDULE_complex=(
    "sunrise-01:00               KIWI_0,630 KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12          "
    "sunrise+01:00                          KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10"
    "09:00                       KIWI_0,630 KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12          "
    "10:00                                  KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10"
    "11:00                                             KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10"
    "18:00           KIWI_0,2200 KIWI_0,630 KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15                    "
    "sunset-01:00                           KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10"
    "sunset+01:00                KIWI_0,630 KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,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_simple2[@]}" )
declare WSPR_SCHEDULE=( "${WSPR_SCHEDULE_merged[@]}" )

On 3/14/21 11:39 AM, Edward Hammond wrote:
Hi Folks -

I would greatly appreciate it if somebody could please forward an example of a wsprdaemon.conf file that manages two Kiwis *while allocating a different set of bands to each receiver*.

I was getting right proud of myself for merging my receivers ... on the first try even .... and then I realized (duh!) that each Kiwi is now monitoring the same set of bands!

In my setup the receivers are tuned to different bands, but I would love to manage them with a single Pi running a single wsprdaemon instance.  Presently I have two Pis each running its own wsprdaemon.

Unplugging one Pi would be great as I am planning to move the whole WSPR receiving setup off-grid and it would save quite a bit of electricity (relative to a modest solar setup!).

Edward

W3ENR








Re: Conf file example - two receivers, different bands, one Pi

Glenn Elmore
 

The wd.conf below works to allow to different Kiwi's (GN2 remote and GN0 local) to both post as "N6GN/K", run on both same and different bands and be scheduled throughout the day, though lately I've been running the same 24/7. This is  WSPR_SCHEDULE_merged

Declare the RECEIVER_LIST first, individual Kiwi's come before the merged ones.  Then just call out what you want in the schedule.

THere is a subtle 'gotcha' that you shouldn't run different receiver/gridsquare on the same band as they may post twice rather than once as is desired.

Glenn n6gn


# 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="N6GN"     ### 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="yes"    ### 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 pairsyy
### BAND is one of 2200..10, while AJUST is in dBp TO BE ADDED to the raw data, e.g. '-10' will LOWER the reported level
### DEFAULT defaults to zero and is applied to all bands not specified with a BAND:ADJUST

declare RECEIVER_LIST=(
"GN0            10.0.0.161:8073         N6GN/K       DN70ll kiwis_password DEFAULT:-2.0,2200:11.6,630:10.5,160:4.5,80:1.3,60:0.0,40:-0.7,30:-1.0,20:-0.8,17:-1.0,15:-0.4,12:0.2,10:0.0"
"GN2            10.0.0.102:8075         N6GN/K       DN70jo kiwis_password DEFAULT:-2.0,2200:11.6,630:10.5,160:4.5,80:1.3,60:0.0,40:-0.7,30:-1.0,20:-0.8,17:-1.0,15:-0.4,12:0.2,10:0.0"
"GN3            10.0.0.77:8074          N6GN/K       DN70ll kiwis_password DEFAULT:-2.0,2200:11.6,630:10.5,160:4.5,80:1.3,60:0.0,40:-0.7,30:-1.0,20:-0.8,17:-1.0,15:-0.4,12:0.2,10:0.0"
"GN4            10.0.0.67:8076          N6GN/P       DN70ll kiwis_password DEFAULT:-2.0,2200:11.6,630:10.5,160:4.5,80:1.3,60:0.0,40:-0.7,30:-1.0,20:-0.8,17:-1.0,15:-0.4,12:0.2,10:0.0"
"K6RFT          k6rft.proxy.kiwisdr.com:8073     K6RFT   EM47bg kiwis_password     DEFAULT:0.0"

"MERGED_RX_02   GN0,GN2                 N6GN/K       DN70ll kiwis_password"
"MERGED_RX_23   GN2,GN3                 N6GN/K       DN70ll kiwis_password"
"MERGED_RX_03   GN0,GN3                 N6GN/K       DN70ll kiwis_password"
"MERGED_RX_023  GN0,GN2,GN3             N6GN/K       DN70ll kiwis_password"
"MERGED_RX_034  GN0,GN3,GN4             N6GN/K       DN70ll kiwis_password"
"MERGED_RX_34   GN3,GN4                 N6GN/K       DN70ll kiwis_password"
)

### 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_simple1=(
    "00:00                       GN0,2200 GN0,630 GN0,160 GN0,80 GN0,80eu GN0,60 GN0,40 GN0,30 GN0,20 GN0,17 GN0,15 GN0,12 GN0,10"
)

declare WSPR_SCHEDULE_simple2=(
    "00:00                       GN0,2200 MERGED_RX_03,630 MERGED_RX_03,160 GN0,80eu MERGED_RX_03,80 GN0,60 MERGED_RX_03,40 MERGED_RX_03,30 MERGED_RX_03,20 GN0,17 MERGED_RX_03,15  GN0,12 GN0,10"
)

declare WSPR_SCHEDULE_simple4=(
    "00:00                       GN0,2200 GN0,630 GN0,160 GN0,80 GN0,80eu GN0,60 GN0,40 GN0,30 GN0,20 GN0,17 GN0,15 GN0,12 GN0,10    GN3,80 GN3,40 GN3,30 GN3,20 GN3,17 GN3,15 GN3,10"
)


declare WSPR_SCHEDULE_merged=(
    "00:00                       GN0,2200 GN0,630 GN0,160 MERGED_RX_02,80 GN0,80eu GN0,60eu MERGED_RX_02,40 MERGED_RX_02,30  MERGED_RX_02,20  MERGED_RX_02,17 MERGED_RX_02,15 GN0,12 GN0,10 "
)

declare WSPR_SCHEDULE_complex=(
    "sunrise-01:00               KIWI_0,630 KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12          "
    "sunrise+01:00                          KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10"
    "09:00                       KIWI_0,630 KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12          "
    "10:00                                  KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10"
    "11:00                                             KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10"
    "18:00           KIWI_0,2200 KIWI_0,630 KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15                    "
    "sunset-01:00                           KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,10"
    "sunset+01:00                KIWI_0,630 KIWI_0,160 KIWI_1,80 KIWI_2,80eu KIWI_2,60 KIWI_2,60eu KIWI_1,40 KIWI_1,30 KIWI_1,20 KIWI_1,17 KIWI_1,15 KIWI_1,12 KIWI_1,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_simple2[@]}" )
declare WSPR_SCHEDULE=( "${WSPR_SCHEDULE_merged[@]}" )

On 3/14/21 11:39 AM, Edward Hammond wrote:
Hi Folks -

I would greatly appreciate it if somebody could please forward an example of a wsprdaemon.conf file that manages two Kiwis *while allocating a different set of bands to each receiver*.

I was getting right proud of myself for merging my receivers ... on the first try even .... and then I realized (duh!) that each Kiwi is now monitoring the same set of bands!

In my setup the receivers are tuned to different bands, but I would love to manage them with a single Pi running a single wsprdaemon instance.  Presently I have two Pis each running its own wsprdaemon.

Unplugging one Pi would be great as I am planning to move the whole WSPR receiving setup off-grid and it would save quite a bit of electricity (relative to a modest solar setup!).

Edward

W3ENR





Conf file example - two receivers, different bands, one Pi

Edward Hammond
 

Hi Folks -

I would greatly appreciate it if somebody could please forward an example of a wsprdaemon.conf file that manages two Kiwis *while allocating a different set of bands to each receiver*.

I was getting right proud of myself for merging my receivers ... on the first try even .... and then I realized (duh!) that each Kiwi is now monitoring the same set of bands!

In my setup the receivers are tuned to different bands, but I would love to manage them with a single Pi running a single wsprdaemon instance.  Presently I have two Pis each running its own wsprdaemon.

Unplugging one Pi would be great as I am planning to move the whole WSPR receiving setup off-grid and it would save quite a bit of electricity (relative to a modest solar setup!).

Edward

W3ENR


Re: http://jimlill.com/today_int.html Down?

jimcny2
 

dropped out mid day sometime, still down


http://jimlill.com/today_int.html Down?

John
 

can anyone confirm that the  http://jimlill.com/today_int.html   WSPR server is down?


Re: No own call decoding or uploading possible?

Chris Wilson
 

Rob, thanks very much indeed, I am glad you can see and agree it's a sensible use for such a feature and I appreciate your support, all the very best. 2E0ILY


migrate wsprdaemon to Atomicpi

John
 

I hope this will be a long and productive thread.

I have been trying to make the move from a good working arrangement with RaspberryPi 4 to Atomicpi.
I have tried many paths but not found one that provides a good working environment, yet!
 I am asking the group to help me out while Rob works on many more important tasks.
Things that I have tried that have not worked:
I installed the X86 version of Raspbian on the Atomicpi. It installed OK  and wsprdaemon also installed
but I ended up with no spots. wd -s looks ok but still no spots. X86 Raspbian does not come with VNC and I was not able to find an X86 version to install.
I was hoping to use VNC to provide remote access to provide for some remote support. I gave up on the X86 Raspbian.

I have since loaded version 20.04 of UBUNTU. the lite version that still has the GUI but none of the User Apps.
I had to install git to install wsprdaemon. I started with an ID of pi but then also added an ID of wsordaemon, Both in the SUDO group.
This has turned into a big pain as I am asked for the password for all invocations of the SUDO command. UBUNTU would not allow me the short nnnn password and insisted that I have 8 long with Upper and special charters. 
With the install of wsprdaemon I have even more errors.

First: on all starts of wd Error -- LC_numeric 'es_CR.UFT-8 ' on your server is not expected If spot frequency is not correct change the local...
The system sees that I am in Costa Rica and assumes Spanish (es). I do not know where to change this.

Next: 
when I wd -s my KIWI and MERG stack look normal, But, KIWI_2 is normally loaded with all 12 assignments (good China KIWI), But, KIWI_1 has no channels assigned a frequency. I have not found the source of this problem.
And:  I have no spots. I only get the message that there are no spots for the empty files are purged.

Sooooo. I need some guidance.  First -- Should I change the OS? I am getting good at loading new OS on the Atomicpi.
Can I get help here to make this machine visible on the Internet for secure remote access? Hoping for more direct support.

I thought of asking to use PM (private mail) but then I think that there may be others that could benefit from my forthcoming educition.

So now I will QSX for a week.

John
TI4JWC


Re: No own call decoding or uploading possible?

Rob Robinett
 

OK, I'll add that feature to my TODO list.
Howevef WD already suppresses 'phantom' sideband spots:  in each wspr cycle, on each band, WD uploads only the strongest spot from each tx  callsign. 

On Sat, Mar 13, 2021 at 10:21 AM Chris Wilson <chris@...> wrote:
Ah, yes, but my Kiwi running the daemon uses 2E0ILY/KIWI as the RX call sign and I transmit WSPR using 2E0ILY, so I would like a means of telling the KIWI script to ignore 2E0ILY, if you see what I mean?







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


Re: No own call decoding or uploading possible?

Chris Wilson
 

Ah, yes, but my Kiwi running the daemon uses 2E0ILY/KIWI as the RX call sign and I transmit WSPR using 2E0ILY, so I would like a means of telling the KIWI script to ignore 2E0ILY, if you see what I mean?


Re: No own call decoding or uploading possible?

jimcny2
 

wsprnet.org ignores own calls

481 - 500 of 679