Date
1 - 20 of 35
FST4W with v3.0.4 on Pi4
|
Erwin - PE3ES - F4VTQ
wd-query -r F4VTQ 48
time | tx_call | tx_grid | rx_id | receiver | rx_grid | freq | tx_dBm | SNR | drift | mode | S width (mHz)
---------------------+---------+---------+-------+----------+---------+-----------+--------+-----+-------+------+---------------
2022-11-02 05:00:00 | 7R9HB | LN87 | F4VTQ | KIWI_0 | JN28ux | 7.0400051 | 53 | -37 | 0 | 6 | 24
2022-10-31 23:55:00 | G6AVK | JO01 | F4VTQ | KIWI_0 | JN28ux | 0.4757851 | 17 | -29 | 0 | 6 | 4
2022-10-31 23:50:00 | G6AVK | JO01 | F4VTQ | KIWI_0 | JN28ux | 0.4757851 | 17 | -31 | 0 | 6 | 4
2022-10-31 23:40:00 | G6AVK | JO01 | F4VTQ | KIWI_0 | JN28ux | 0.4757851 | 17 | -28 | 0 | 6 | 2
2022-10-31 22:50:00 | G6AVK | JO01 | F4VTQ | KIWI_0 | JN28ux | 0.4757851 | 17 | -34 | 0 | 6 | 6
2022-10-31 21:30:00 | G6AVK | JO01 | F4VTQ | KIWI_0 | JN28ux | 0.4757851 | 17 | -35 | 0 | 6 | 4
|
|
|
|
Erwin - PE3ES - F4VTQ
Thanks Rob, that is looking good now.
wd-query
usage: wd-query {-r | -t} ID [HOURS_TO_SEARCH] -r => search for ID of reporter -t => search for ID of transmit beacon
|
|
|
|
Rob Robinett
Log out and log in again On Tue, Nov 1, 2022 at 8:12 AM Erwin - PE3ES - F4VTQ via groups.io <waterwin2=yahoo.com@groups.io> wrote: On Sun, Oct 30, 2022 at 03:40 PM, Rob Robinett wrote: --
|
|
|
|
Erwin - PE3ES - F4VTQ
On Sun, Oct 30, 2022 at 03:40 PM, Rob Robinett wrote:
wd-queryI just did a git pull but still wd-query not found. |
|
|
|
Alan G4ZFQ
On 30/10/2022 14:40, Rob Robinett wrote:
My most recent check in includes a the command 'wd-query' which prints out only FST4W spots (and the frequency twice!):Thanks Rob. Things are a bit different since I became interested in WSPR over 13 years ago! Whatever of my Softrock's 1 Watt FST4W-300 comes out of the poor antenna made 1800Km on MF last night. But I suspect it will be a long time before most abandon WSPR. 73 Alan |
|
|
|
Rob Robinett
My most recent check in includes a the command 'wd-query' which prints out only FST4W spots (and the frequency twice!): usage: wd-query {-r | -t} ID [HOURS_TO_SEARCH] -r => search for ID of reporter -t => search for ID of transmit beacon wd_client@KFS-WD3:~/wsprdaemon$ wd_client@KFS-WD3:~/wsprdaemon$ wd-query -t G4ZFQ 8 time | tx_call | tx_grid | rx_id | receiver | rx_grid | freq | tx_dBm | SNR | drift | mode | freq | S width (mHz) ---------------------+---------+---------+-------+----------+---------+-----------+--------+-------+-------+------+-----------+--------------- 2022-10-30 13:25:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757137 | 3 | -5.6 | 0 | 6 | 0.4757137 | 12 2022-10-30 13:15:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757137 | 3 | -5.6 | 0 | 6 | 0.4757137 | 13 2022-10-30 13:00:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757138 | 3 | -5.7 | 0 | 6 | 0.4757138 | 25 2022-10-30 11:30:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757137 | 3 | -5.9 | 0 | 6 | 0.4757137 | 5 2022-10-30 09:30:00 | G4ZFQ | IO90 | G4ZFQ | G4ZFQ_1 | IO90ir | 0.4757137 | 3 | -23.8 | 0 | 6 | 0.4757137 | 99 2022-10-30 09:30:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757137 | 3 | -6.3 | 0 | 6 | 0.4757137 | 12 2022-10-30 09:20:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757137 | 3 | -5.9 | 0 | 6 | 0.4757137 | 19 2022-10-30 09:10:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757138 | 3 | -6 | 0 | 6 | 0.4757138 | 18 2022-10-30 08:25:00 | G4ZFQ | IO90 | G4ZFQ | G4ZFQ_1 | IO90ir | 0.4757138 | 3 | -27.2 | 0 | 6 | 0.4757138 | 204 2022-10-30 08:25:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757138 | 3 | -6.1 | 0 | 6 | 0.4757138 | 17 2022-10-30 06:55:00 | G4ZFQ | IO90 | ON5KQ | KIWI_5 | JO10os | 0.4757137 | 3 | -31.6 | 0 | 6 | 0.4757137 | 27 2022-10-30 06:55:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757137 | 3 | -5.7 | 0 | 6 | 0.4757137 | 19 2022-10-30 06:35:00 | G4ZFQ | IO90 | ON5KQ | KIWI_5 | JO10os | 0.4757137 | 3 | -29.7 | 0 | 6 | 0.4757137 | 30 2022-10-30 06:35:00 | G4ZFQ | IO90 | G3ZIL | G3ZIL_3 | IO90hw | 0.4757137 | 3 | -5.6 | 0 | 6 | 0.4757137 | 19 2022-10-30 06:35:00 | G4ZFQ | IO90 | G4ZFQ | G4ZFQ_1 | IO90ir | 0.4756638 | 3 | -22.1 | 0 | 6 | 0.4756638 | 165 (15 rows) wd_client@KFS-WD3:~/wsprdaemon$ On Sun, Oct 30, 2022 at 1:36 AM Gwyn Griffiths via groups.io <gxgriffiths=virginmedia.com@groups.io> wrote: Hello Alan --
|
|
|
|
Gwyn Griffiths
Hello Alan
You can find a Grafana Dashboard for FST4W, that I've preset with your tx call and Ulli, ON5KQ, as a receiver that has spotted your FST4W-300 on 630 m the last couple of days at: http://logs1.wsprdaemon.org:3000/d/4xvGwI97z/wspr-and-fst4w-comparisons?orgId=1&var-receiver=KIWI_5&var-sender=G4ZFQ&var-band=630&var-rx_id=ON5KQ&from=now-5d&to=now regular wsprdaemon Grafana users will know the usual userid and password. I'll drop you an email with them. regards Gwyn |
|
|
|
Alan G4ZFQ
On 29/10/2022 07:17, Gwyn Griffiths via groups.io wrote:
The spectral widths look excellent, at mostly under 10 milliHz.Gwyn, Thanks for the check. I've been poking around, found my local noise graphs, maybe find out how you get the spectral widths one day. 73 Alan |
|
|
|
Gwyn Griffiths
Hello Alan
Nice to see that you are now reporting over-the-air FST4W spots on 2200 and 630 m from your Kiwi and WsprDaemon. The spectral widths look excellent, at mostly under 10 milliHz. best wishes Gwyn G3ZIL |
|
|
|
Alan G4ZFQ
On 27/10/2022 14:51, Alan G4ZFQ via groups.io wrote:
Is Buster OK or what?Yes, Buster looks OK. alan@raspberrypi:~/wsprdaemon $ ./bin/jt9 --fst4w -p 120 -f 1500 -F 100 ~/220719_1418.wav 1418 11 1.1 1511 ` G3ZIL IO90 30 <DecodeFinished> 0 1 0 and 2022-10-28 15:00:00 G9ZFQ IO90ir 0 3 -17 475714 G4ZFQ WD_3.0.5 Thanks all for the hints, directing me where to fumble:-) 73 Alan |
|
|
|
Rob Robinett
WSJT-x worked on a Pi running older buster, but there was an update to the buster image on 22/9/2022 at https://www.raspberrypi.com/software/operating-systems/#raspberry-pi-os-legacy which I haven't tested yet. If you can successfully install and run WSJT-x from https://physics.princeton.edu/pulsar/k1jt/wsjtx.html on the Pi's desktop, then WD should install and run fine. On Thu, Oct 27, 2022 at 7:52 AM Alan G4ZFQ <alan4alan@...> wrote: On 27/10/2022 14:16, Rob Robinett wrote: --
|
|
|
|
Alan G4ZFQ
On 27/10/2022 14:16, Rob Robinett wrote:
WSJT-x hasn't been ported to Raspberry Pi OS bullseyeAh! Thanks, my lack of research, I thought as it is based on Debian it would be OK. Is Buster OK or what? 73 Alan |
|
|
|
Rob Robinett
Alan, What OS are you running? WSJT-x hasn't been ported to Raspberry Pi OS bullseye nor to Ubuntu 22.04, so WD can't run on those versions of OSs. Rob On Thu, Oct 27, 2022 at 7:13 AM Alan G4ZFQ <alan4alan@...> wrote: On 27/10/2022 08:33, Gwyn Griffiths via groups.io wrote: --
|
|
|
|
Alan G4ZFQ
On 27/10/2022 08:33, Gwyn Griffiths via groups.io wrote:
Any of these steps may fail, but that will tell us something:Gwyn, Thanks, I got alan@raspberrypi:~ $ /home/alan/wsprdaemon/bin/jt9 --fst4w -p 120 -f 1500 -F 100 ~/220719_1418.wav /home/alan/wsprdaemon/bin/jt9: error while loading shared libraries: libboost_log_setup.so.1.67.0: cannot open shared object file: No such file or directory alan@raspberrypi:~ $ Where now? Also, I've a receiver on 20m FST4-300 at the moment, propagation to USA is not yet open. It is the standard WSPR frequency? 73 Alan |
|
|
|
Rob Robinett
Hi Alan, While WD is running, execute 'wdle', which is an alias which runs' wd -l e'. Every 10 seconds it searches all of the many WD log files looking for lines which contain the word "ERROR", There are a few non-error conditions currently being logged, but you should see and FST4W decoder failures but not failure to find spots in those logs. Beyond that, it would be much easier for us for me to log on to your WD machine and exp[lore further. Rob wd_client@KFS-WD3:~/wsprdaemon$ wdle Thu 27 Oct 2022 13:38:25 UTC: proxy_connection_manager() ALERT: There is an active proxy connection to wd0.wsprdaemon.org where its port 35800 is open to this server Checking every 10 seconds for new ERROR lines in all the log files. Press <CONTROL C> to exit Thu 27 Oct 2022 13:38:31 UTC: wd_logger_check_all_logs() Found 9 new 'ERROR:' lines in /dev/shm/wsprdaemon/recording.d/KIWI_SW/40/decoding_daemon.log among its 5037 new log lines. Thu 27 Oct 2022 11:36:10 UTC: get_wav_levels() ERROR: wav file overflow detected in file 221027_1134.wav of length=120.011 seconds and with Bit-depth=16/16: the min/max levels are: min=-0.968719, max=0.987122 That is the first ERROR: line. Press <ENTER> to check the next log file or 'l' to 'less all the new lines after that new ERROR line /dev/shm/wsprdaemon/new_error_log_lines.txt => On Thu, Oct 27, 2022 at 2:30 AM Alan G4ZFQ <alan4alan@...> wrote: On 27/10/2022 08:33, Gwyn Griffiths via groups.io wrote: --
|
|
|
|
Alan G4ZFQ
On 27/10/2022 08:33, Gwyn Griffiths via groups.io wrote:
It may be useful to run a test in isolation of the jt9 program Gwyn, Thanks! Yes jt9 is there I'll give it a try this afternoon. 73 Alan |
|
|
|
Gwyn Griffiths
Hello Alan
It may be useful to run a test in isolation of the jt9 program that decodes FST4W. Any of these steps may fail, but that will tell us something: 1. A successful installation of wsprdaemon should install the jt9 executable. If you have installed as userid wsprdaemon I'd expect to find it at /home/wsprdaemon/wsprdaemon/bin/jt9 If it isn't then it'd be worth trying to find it. I prefer the utility locate rather than find, it can be installed with sudo apt-get install mlocate then it is simply locate jt9 2. I've attached a wav file with an FST4W-120 signal of mine. Assuming the jt9 is in the default location, if you download the wav file into your Pi's home directory for user wsprdaemon then execute the following: /home/wsprdaemon/wsprdaemon/bin/jt9 --fst4w -p 120 -f 1500 -F 100 ~/220719_1418.wav It should produce a decode 1418 11 1.1 1511 ` G3ZIL IO90 30 <DecodeFinished> 0 1 0 regards Gwyn G3ZIL |
|
|
|
Rob Robinett
Hi Alan, If you want me to look at your WD through WD's remote access connection, then email me and I'll send you instructions. Rob On Wed, Oct 26, 2022 at 1:45 PM Alan G4ZFQ <alan4alan@...> wrote: > If your wsprdaemon install was done per the instructions then 'cd --
|
|
|
|
Alan G4ZFQ
If your wsprdaemon install was done per the instructions then 'cdThanks Glenn, easy, quick, v3.0.5:-) But still no FST4W decodes. W2 fine. Note there is a F5 signal to decode, and I have also provided one from a local TX. declare WSPR_SCHEDULE=( "00:00 G4ZFQ_1,2200,W2:F5:F15 G4ZFQ_1,630,W2:F5 G4ZFQ_1,160 G4ZFQ_1,80 G4ZFQ_1,40 G4ZFQ_1,30 G4ZFQ_1,22 " ) Seems to be the only entry concerning FST4W, I've tried various configurations including 630 on its own. I shall rename /wsprdaemon and install again unless someone has a better suggestion. 73 Alan G4ZFQ |
|
|
|
Alan G4ZFQ
On 24/10/2022 12:23, Gwyn Griffiths via groups.io wrote:
These are the FST4W spots I've received from you over the last 10 days - just these four this morning.Gwyn, Thanks for your comments. I have not transmitted much, I have left that for those with better setup antennas. I was using a LF Softrock with an Si570, good to know how it works. Is your wsprdaemon.config file set up to upload to wsprdaemon.org?No, I have not enabled upload to there, I did not know if it would be welcomed. I'll do that. I am still getting around Linux and wsprdaemon, realising that the only brief record of spots on the pi (apart from the briefer pre upload one) was a record of wsprnet's accepted spots. My tests of reception this morning have been using FST4W with a false call into a dummy load. You may have seen a WSPR report of G9ZFQ from me, but no FST4W modes. I did set SIGNAL_LEVEL_LOCAL_GRAPHS="yes", package scipy was installed but it looks as if I need to do more. 73 Alan |
|
|