After using WSJT-X for the modes JT65/JT9 now for a couple of time and done more than 1000 contacts in these modes, one drawback occured to me: The Logbook function when you worked stations more than once on different band/mode slots.
When you worked a station for example on 20m in JT65, the build in logbook will show you this call in green, meaning you worked it before, even if you are now on 15m in JT9. So the only meaning to this is yes, we worked before, but no chance to see where and in which mode 🙁
As I’m running an online logbook at www.dk7uy.de the idea was to make a lookup in this database for the stations calling CQ in WSJT-X.
The following shows the concept of a software written in C++.
WSJT-X logs every station activity in the ALL.TXT file, so the task was to write a piece of software which is able to scan the ALL.TXT for the latest CQ-calls in the actuall time slot and make a lookup in the MySQL-database at www.dk7uy.de.
You see F4FSY calling CQ in JT65 mode, the call is in green colour which indicates we worked before.
OK, F4FSY an me worked before, but on 14 MHz in JT9 mode, so no problem to work him on 10 MHz for a new band.
Another idea occured to me when calling CQ by myself on a quiet band. You constantly have to monitor the PC Screen if someone is answering your call, maybe you want to use your time for doing some other work while calling CQ.
So my little program was extended to scan the ALL.txt for incomming calls as well, giving an audio-alarm if there is a station answering my CQ.
Runing my station mostly remote, I desided to go for a Client/Server soloution, so the alarm can be heard on the RDP-Client instead on the PC in the shack running WSJT-X.
Last but not least, why not automaticly updating the Internet-Log?
WSJT-X maintains an ADIF file where all the QSO’s were stored. So my software monitores any change of size of the file WSJT-log.adi, reads the last line of the file and calls a PHP file at my website which writes this data to the MySQL database. Done!
Next option to include is to scan the WSJT-X internal log when there is no internet connection available. In this case you won’t see if you worked a call before in CW or RTTY but at least where you worked him in JT65/JT9.