Date   

[rrobinett/wsprdaemon] Possibility of SpyServer Client Support? (Issue

Rob Robinett
 



---------- Forwarded message ---------
From: Mark Jessop <notifications@...>
Date: Sun, Jan 30, 2022 at 1:15 PM
Subject: Re: [rrobinett/wsprdaemon] Possibility of SpyServer Client Support? (Issue #17)
To: rrobinett/wsprdaemon <wsprdaemon@...>
Cc: rrobinett <rob@...>, Comment <comment@...>


Since in this case i'm talking specifically about airspy spyserver support, there's heaps of spyservers online that you can test against - no need to actually own an Airspy.

Another reason behind going with the spyserver route for each band has been that I can fairly easily attach other 'listeners' onto each spyserver, without much penalty in CPU cost. I can happy have maybe 20 users attached to each spyserver at the moment.

Right now i'm running HF APRS receivers up there, and more recently a club member has written a SSTV Skimmer which connects to the spyserver (https://github.com/xssfox/sstv-skimmer output visible on https://botsin.space/@aregsstv ) - if we were doing this on the KiwiSDR we'd nee a lot more kiwisdrs at the site!

Getting an all-band WSPR receiver going at the site is certainly the aim here! We already have airspys set up for 160/80/40/30/20/15m, and are planning on adding 17/12/10m soon. Later on we are also intending on adding omnidirectional horizontally polarised antennas for 6m, 2m and 70cm as well.


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID: <rrobinett/wsprdaemon/issues/17/1025232936@github.com>



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


[rrobinett/wsprdaemon] Possibility of SpyServer Client Support? (Issue

Rob Robinett
 

FYI...

---------- Forwarded message ---------
From: Mark Jessop <notifications@...>
Date: Sun, Jan 30, 2022 at 2:53 AM
Subject: [rrobinett/wsprdaemon] Possibility of SpyServer Client Support? (Issue #17)
To: rrobinett/wsprdaemon <wsprdaemon@...>
Cc: Subscribed <subscribed@...>


Hi!

This looks like a super useful addition to a remote HF site I run, which has (along with multiple KiwiSDRs - see kiwisdr.areg.org.au:8073 ) a pile of Airspy HF+ Spyservers - one for each amateur radio band.

There is an open-source spyserver client here: https://github.com/miweber67/spyserver_client which can stream IQ to stdout. It would be awesome if I could use this client to run WSPR decoders on the Airspys - this would avoid tying up channels of the KiwiSDRs.

I was able to proof-of-concept decoding WSPR via it using the following script (running it manually just before the start time of the WSPR transmissions) and a fork of WSPRd which accepts data from stdin.

FREQ=14095600

# SpyServer Details
HOST=localhost
PORT=5020

# SpyServer Connection, requesting 12 kHz of IQ bandwidth, and using lots of buffering.
ss_iq -a 1200 -r $HOST -q $PORT -f $FREQ -s 12000 -b 16 - | \
# Convert the incoming signed 16-bit IQ to floating point
csdr convert_s16_f |\
# SSB demodulation using a tight bandpass filter (0-3600 Hz), and then taking the real part.
# (I could probably make this a bit narrower) Also add on some AGC and limiting.
csdr bandpass_fir_fft_cc 0 0.3 0.05 | csdr realpart_cf | csdr agc_ff | csdr limit_ff | \
# Convert back into signed 16-bit format and pass into sox, then to wsprd
csdr convert_f_s16 |
sox -t raw -r 12000 -e s -b 16 -c 1 - -c 1 -r 12000 -t wav - trim 0 114 |
./k9an-wsprd -wf "14.0956" /dev/stdin

There's some information on how I compile and use the spyserver client utility for decoding HF APRS here: https://gist.github.com/darksidelemm/6b60767714295962771bca7b728b343c#file-spyserver_hf_aprs-sh-L26

Is this something that could be considered for a future release?


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <rrobinett/wsprdaemon/issues/17@github.com>



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


Re: wsprd upgrade

KD2OM
 

In the meantime I figured out to change the version wsprdaemon.sh asks for from 2.3.0 to 2.5.4. Seems to be running the new version fine now.

.
 

On Jan 22, 2022, at 10:17, Rob Robinett <rob@...> wrote:


I don't think WD 2.10k users suffer from that memory leak, perhaps because it uses the file in/out interface to wsprd.  There are sites running WD untouched on a 1GB Pi4 for years without OS memory problems.
But In WD 3.0 I load the latest 2.5.x wsprd, so installing 3.0 when it becomes available will upgrade your WD site automaticlly

On Sat, Jan 22, 2022 at 5:45 AM KD2OM <steve@...> wrote:
How does someone upgrade wspr to V2.5?
> On Jan 22, 2022, at 08:06, Jim Lill <jim@...> wrote:
>
> Regardless of what OS or computer type you run, you should consider updating your wsprd executable to 2.5.x. As of that revision, a memory leak is fixed.
>
>
>
>
>
>
>








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


Re: wsprd upgrade

Rob Robinett
 

I don't think WD 2.10k users suffer from that memory leak, perhaps because it uses the file in/out interface to wsprd.  There are sites running WD untouched on a 1GB Pi4 for years without OS memory problems.
But In WD 3.0 I load the latest 2.5.x wsprd, so installing 3.0 when it becomes available will upgrade your WD site automaticlly

On Sat, Jan 22, 2022 at 5:45 AM KD2OM <steve@...> wrote:
How does someone upgrade wspr to V2.5?
> On Jan 22, 2022, at 08:06, Jim Lill <jim@...> wrote:
>
> Regardless of what OS or computer type you run, you should consider updating your wsprd executable to 2.5.x. As of that revision, a memory leak is fixed.
>
>
>
>
>
>
>








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


Re: wsprd upgrade

KD2OM
 

How does someone upgrade wspr to V2.5?

On Jan 22, 2022, at 08:06, Jim Lill <jim@...> wrote:

Regardless of what OS or computer type you run, you should consider updating your wsprd executable to 2.5.x. As of that revision, a memory leak is fixed.







wsprd upgrade

Jim Lill
 

Regardless of what OS or computer type you run, you should consider updating your wsprd executable to 2.5.x. As of that revision, a memory leak is fixed.


Odroid XU4

Jim Lill
 

I may be the only one who uses one of those for WD, but just in case there are others...

I compiled from source the latest version of wsprd and jt9 and have them running.

An easy install and if anyone wants copies, let me know

-Jim

WA2ZKD


FiFiSDR - complains about snd_pcm_open error

Erwin - PE3ES - F4VTQ
 

A second Raspberry is running the FiFiSDR

Audio input devices:
**** List of CAPTURE Hardware Devices ****
card 1: FiFiSDR [FiFi-SDR], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: FiFiSDR [FiFi-SDR], device 1: USB Audio [USB Audio #1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
Select audio input device you want to test [0-1] => 1
The audio input to device 1 is being echoed to it line output.  Press ^C (Control+C) to terminate:
sox FAIL formats: can't open output file `hw:1,0': snd_pcm_open error: No such file or directory
Adjust the input gain and restart test? [-+q] =>

This happens when testing either device 0 and 1.

Any suggestions how to get this working would be appreciated.
Thanx, Erwin


Re: Using ./wsprdaemon.sh -i to find the info on connected audio devices

Erwin - PE3ES - F4VTQ
 

Well indeed.
Edit the conf and rerun the script.

E.


Getting wsprdaemon working with Yaesu SCU17

Erwin - PE3ES - F4VTQ
 

I have 2.10k working on my Raspberry Pi Buster
It starts the test and finds the Audio Codec
But what to do then ?

Adjust the input gain and restart test? [-+q] => +
amixer: Unable to find simple control 'Mic',0

Any advice appreciated.

The same setup works with jtdx and wsjt-x on wspr and other modes.

Thanx, Erwin


Re: How to resolve FATAL ERROR: Failed to install 'qt5-default' on RaspberryPi during Wsprdaemon fresh install

Rob Robinett
 

This discussion stimulated me to resume WD 3.0 installation testing on my Pi4b running bullseye, but of course I immediately encountered the 'missing qt5' problem.

However this thread on the Pi forum led me to install libqt5core5a on bullseye instead of qt5-default : https://forums.raspberrypi.com/viewtopic.php?t=323989

The ~wsprdaemon/bin/wsprd then ran, so there appears to be workaround I'll put into WD 3.0 


Re: How to resolve FATAL ERROR: Failed to install 'qt5-default' on RaspberryPi during Wsprdaemon fresh install

Erwin - PE3ES - F4VTQ
 

There is an older message here for the same.

I tried to solve it differently though as it appears that it is not necessary for wsprdaemon

I commented that part out of the install script which seems to work as well.
How:
wsprdaemon.sh search for the if/fi dpkg qt5-default etc and use # to comment out that complete block

I was left with an Error on not finding libboost-log but still the wsprdaemon.sh is completing and doing "something"


Using ./wsprdaemon.sh -i to find the info on connected audio devices

Erwin - PE3ES - F4VTQ
 

I tried this on a brand new WD install but this does not work with an unmodified .conf file.
Catch22 or should I simply do some standard input into the .conf file and run the command again?

Thanks

Erwin


Re: Inconsistency of Grafana Noise data = gaps with no data

ON5KQ
 

Thanks for information.
I am happy that these effects are not coming from an outside attack...
I am sorry for the additional work which it causes/caused...

regards,
Ulli


Re: Inconsistency of Grafana Noise data = gaps with no data

Rob Robinett
 

I have been debugging the WD 3.0 server code and despite all me pre-testing I encountered bugs which caused noise and extended spot losses on the WD2 server which feeds Grafana and wspr.live.
I believe those bugs are fixed and the noise and spots should be current now. 
Please let me know if you encounter any problems in the next few days as I finish debugging WD 3.0 on the three servers which store all the WD spot and noise as well as the clone of the wsprnet spot database used by wspr.live


Re: Inconsistency of Grafana Noise data = gaps with no data

Rob Robinett
 

Hi Ulli,

In installing WD 3.0 server on WD I have uncovered a number of problems, among the most worrisome is that a couple of WD client sites (not yours) are repeatedly uploading the same valid spot+noise data files.  I am currently working on the new 3.0 code to keep it from propagating the errors generated by such repeated uploads to the WD2 server which is the source of the Grafana pages.  I will then contact those two sites to see why their WD client SW is generating such errors.

Rob

On Sat, Jan 15, 2022 at 4:11 AM Gwyn Griffiths via groups.io <gxgriffiths=virginmedia.com@groups.io> wrote:
Hello Ulli
The problem you describe was an unexpected transient 'side-effect' of a change to new WD 3.0 software on the server. 
Later today I will see if I can fill the missing data. 

This was not caused by an attack.

best wishes
Gwyn 



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


Re: Inconsistency of Grafana Noise data = gaps with no data

Gwyn Griffiths
 

Hello Ulli
The problem you describe was an unexpected transient 'side-effect' of a change to new WD 3.0 software on the server. 
Later today I will see if I can fill the missing data. 

This was not caused by an attack.

best wishes
Gwyn 


Inconsistency of Grafana Noise data = gaps with no data

ON5KQ
 

Last night from 01:00h to about 03:00h UTC the Grafana page (clickhouse database, wspr.live) doesn't show any noise date
Later this night periodically the noisedata is missing for shorter periods of time...
It seems that this is happening worldwide..

Is there a problem with one of the servers, which causes the data loss ?
Or is it a similar problem like the  DoS attack we faced some weeks ago ?

What happens ?!

The problem is easily visible on wspr.live...

Ulli, ON5KQ


Reported time

Jim Lill
 

See the attached clip.

What does WD report?


Re: PI image for raspberryKIWI

Jim Lill
 

root has no PW until you set it.   ssh login is with user=debian pw=serial# until you change serial number. You then use su for root or sudo bash with work also

On 1/9/22 7:24 PM, John via groups.io wrote:
Thank you Jim. It was the Raspberry pi 3B that failed. I replaced it and found version 1.359 image.
I loaded that up on a 3B+ I had in the draw. I later ran an update and now at 1.447.
I am still having no luck providing the correct password for SSH root.
I have set the KIWI Admin PW and expected the same for root, but no joy.

John

581 - 600 of 1261