Hi Steve, Thanks for the information, I should have deduced myself that those fields came from the filename. My problem was a bug in my parsing of ALL_WSPR.TXT lines which don't contain the grid field. My debugged SW is now running at 4 of the top 10 North American WSPR receive sites, including KD2OM, KA7OEI-1 and KPH. I will publish it once it works with more than the KiwiSDR as the receive device. Thanks so much for your work on wsprd and your online support.
Rob AI6VN Near real-time data from wsprnet.org, analysis as of 1552Z, raw spots since 0000Z: 914624 Total RankReporterspotsuniqs2200m630m160m80ja80m60eu60m40m30m20m17m15m12m10m 1 KD2OM 9915 570 8 22 29 57 15 6 6 182 114 126 5 0 0 0 2 K9AN 8384 548 0 22 29 54 0 0 0 209 73 144 16 1 0 0 3 N2HQI 9823 507 0 20 22 63 0 0 0 140 83 167 9 2 1 0 4 KA7OEI-1 11539 484 4 21 21 49 12 4 0 160 86 107 14 4 0 2 5 KPH 10307 441 3 14 7 46 9 6 0 161 82 99 9 4 1 0 6 N6GN/K2 8718 408 0 19 21 47 0 4 0 154 78 76 9 0 0 0 7 KD6RF 6024 387 0 0 19 8 0 0 0 154 72 106 28 0 0 0 8 N2NOM 5766 346 0 0 31 50 11 3 0 131 46 68 6 0 0 0 9 NO1D 5533 325 0 0 15 0 9 3 0 141 51 90 13 2 0 1 On Fri, Feb 1, 2019 at 7:09 PM Steven Franke via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Rob, > > - wsprd parses the file name to get date and time. > - the decoding algorithm does not use date and time. > > Steve k9an > > On Feb 1, 2019, at 6:49 PM, Rob Robinett <r...@robinett.us> wrote: > > > My wsprdaemon.sh SW is running at 7 beta sites and detects almost all of > the signals in the bands. > However it seems to miss the second part of type 2 WSPR messages and I > suspect that is due to the lack of date and time fields in the ALL_WSPR.TXT > file. > > An example of the WSJT-x ALL_WSPR.TXT: > > 170711 2234 1 -28 1.26 14.0970558 VE7XT CN88 20 0 190 0 > 170711 2234 5 -17 0.11 14.0971048 W6CLB CM87 20 0 1 0 > 170711 2234 2 -26 0.07 14.0971457 W2GMD CM87 20 0 1 0 > 170711 2236 5 -17 0.07 14.0971049 W6CLB CM87 20 0 1 0 > 170711 2236 2 -26 0.15 14.0971605 W2GMD CM87 20 0 2 0 > 170711 2238 2 -26 0.07 14.0970629 W2GMD CM87 20 q 0 1 > 0 > 170711 2238 4 -9 0.15 14.0970705 WD6DFH CN84 20 -2 1 0 > 170711 2238 5 -17 0.07 14.0971049 W6CLB CM87 20 0 1 0 > > Whereas my ALL_WSPR.TXT looks like this with the freq and USB in the first > two fields: > > 703860 _usb 3 -23 0.45 7.0400585 AJ8S EM89 27 0 1 > 0 1 220 0 > 703860 _usb 3 -18 0.07 7.0400668 W1VR EL98 20 0 1 > 0 1 464 0 > 703860 _usb 5 -13 0.19 7.0400802 KG5OVB EM10 37 0 1 > 0 1 547 0 > 703860 _usb 5 3 0.15 7.0401045 <W0ENO> DN70IC 33 0 1 > 0 1 591 0 > 703860 _usb 4 -6 -1.00 7.0401085 VE7GNU CN88 33 0 1 > 0 1 525 0 > 703860 _usb 7 7 3.99 7.0401146 W6TN DM13 23 0 1 > 0 1 611 0 > 703860 _usb 4 -9 0.37 7.0401189 K4APC EM81 37 0 1 > 0 1 525 0 > 703860 _usb 2 -20 0.45 7.0401333 VA3KV FN25 27 0 630 > 0 1 -33 0 > 703860 _usb 5 -4 0.79 7.0401342 WA4KFZ FM18 37 0 1 > 0 1 564 0 > 703860 _usb 3 -8 0.79 7.0401448 N8VIM FN42 37 -2 1 > 0 1 520 0 > > I can find no date and time fields in the WSJT-x wav file and no mention > of a wsprd date/time command time flag. > > Would the lack of date and time in ALL_WSPR.TXT lead to missed decodes > and if so where is that information communicated to wsprd? > > Thanks, > > Rob > > > -- > Rob Robinett > AI6VN > r...@robinett.us > mobile: +1 650 218 8896 > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- Rob Robinett AI6VN r...@robinett.us mobile: +1 650 218 8896
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
