30-12-2018, 08:21 AM
There will be a new release of WSPRView (V1.0.0.17) early in January - I have a bug that appears only once every few days that I want to solve first.
The new version has a feature that may prove of interest to those who run WSPR beacons themselves. It allows a download of only 'spots' to match the MyCall detail ( ie with /mycall=VK4ADC on the command line) so that you can assess who is actually reporting your transmissions. That function adds any new entries to your 'spots' and into the MyCall log file so that you can get a 'total log' even when WSPRView is not running.
That data is all well and good if you can analyse it to make sense of it. Fingers to keyboard again produced some extra software that processes the MySpots data file and provides a breakdown by callsign and band (160M to 70CM only)), unique callsign counts, total counts in the file and spotter grid square and distance values in KM. You can either browse that on-screen or save the data to a CSV-format summary file to play with further in Ms Excel or similar spreadsheet software.
The extra utility software will be made available at the same time as the V1.0.0.17 is released.
From the start of my summary data file...
Spotter,160M,80M,60M,40M,30M,20M,17M,15M,12M,10M,6M,4M,2M,432,Error,Grid,KM
3D2AG,,,,,,,,,,,4,,,,,RH91fv,2815,
FK1TS,,,,,,,,,,,88,,,,,RG37fr,1488,
KA7OEI-1,,,,,2,,,,,,,,,,,DN31uo,12379,
KPH,,,,,4,,,,,,,,,,,CM88mc,11390,
VK1AAH,,,,,,8,,,,,,,,,,QF44mp,925,
............................
gives..
3D2AG 6M, 4 spots, 2815 KM
FK1TS 6M, 88 spots, 1488 KM
KA7OEI 30M, 2 spots, 12379 KM
KPH 30M, 4 spots, 11390 KM
VK1AAH 20M, 8 spots, 925 KM
.............................
Screen shot below...
Not too shabby for 200mW !!!
Something to look forward to in 2019 ??
The new version has a feature that may prove of interest to those who run WSPR beacons themselves. It allows a download of only 'spots' to match the MyCall detail ( ie with /mycall=VK4ADC on the command line) so that you can assess who is actually reporting your transmissions. That function adds any new entries to your 'spots' and into the MyCall log file so that you can get a 'total log' even when WSPRView is not running.
That data is all well and good if you can analyse it to make sense of it. Fingers to keyboard again produced some extra software that processes the MySpots data file and provides a breakdown by callsign and band (160M to 70CM only)), unique callsign counts, total counts in the file and spotter grid square and distance values in KM. You can either browse that on-screen or save the data to a CSV-format summary file to play with further in Ms Excel or similar spreadsheet software.
The extra utility software will be made available at the same time as the V1.0.0.17 is released.
From the start of my summary data file...
Spotter,160M,80M,60M,40M,30M,20M,17M,15M,12M,10M,6M,4M,2M,432,Error,Grid,KM
3D2AG,,,,,,,,,,,4,,,,,RH91fv,2815,
FK1TS,,,,,,,,,,,88,,,,,RG37fr,1488,
KA7OEI-1,,,,,2,,,,,,,,,,,DN31uo,12379,
KPH,,,,,4,,,,,,,,,,,CM88mc,11390,
VK1AAH,,,,,,8,,,,,,,,,,QF44mp,925,
............................
gives..
3D2AG 6M, 4 spots, 2815 KM
FK1TS 6M, 88 spots, 1488 KM
KA7OEI 30M, 2 spots, 12379 KM
KPH 30M, 4 spots, 11390 KM
VK1AAH 20M, 8 spots, 925 KM
.............................
Screen shot below...
Not too shabby for 200mW !!!
Something to look forward to in 2019 ??
Doug VK4ADC @ QG62LG51
http://www.vk4adc.com
This Forum is only going to be as interesting as the posts it contains.
If you have a comment or question, post it as it may trigger or answer the query in someone else's mind.
http://www.vk4adc.com
This Forum is only going to be as interesting as the posts it contains.
If you have a comment or question, post it as it may trigger or answer the query in someone else's mind.