Hi, In version 3.0 of my wsprdaemon software for Linux systems ( http://wsprdaemon.org/) I am decoding FST4W by running 'jt9 --fst4w ...' jt9 outputs spot lines for type 1 spots, but for a type 3 spot which follows it in the next WSPR cycle jt9 always outputs the callsign '<...>' I can see that the file 'fst4w_calls.txt' is created when WSJT-x decodes those same spots, and I suspect that file is used to look up the hashed calls in a type 3 packet, but that file is never created when I run jt9 standalone on Linux. The format of fst4w_calls.txt is simple and my code could create it for jt9, but inspecting "fst4_decode.f90" with my limited familiarity with Fortan suggests that jt9 will maintain that file in the same way "wprd" does its hash table file.
So how can I get jt9 to resolve the hashed calls in type 3 FWT4W spots? I now have 30 receive sites worldwide listening for FST4W spots 24/7/365, and solving this hashed calls problem will complete their ability to report all FST4W transmissions. 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
