Swisslog, WSJT-X and JTAlert

[JW6VDA]

Once again, thank you for your quick answer, and sorry for letting my lack of computer skills bother you this much. I will of course convey your points about the flexibility in Swisslog's export facilities to Laurie.

On your view that there is no need to use JTAlert in addition to Swisslog, that is true, but the one facility in JTAlert I use a lot is the direct text message. That alone makes it worth wile.

Basically, at my club, I use JTAlert to log online to Clublog and QRZ.COM, plus I make N1MM+, that we use for daily logging, receive the UDP packet from JTAlert to have full use of the XML lookup from QRZ. As for LOTW, it is usually more convenient to upload the qsos directly using TQSL instead of taking the files home, import them to Swisslog and upload them that way. That is also why I am looking for our operator callsign, as defined in the setup of WSJT-X, and which is also used in N1MM+ (ctrl-O).  I cannot find this field in Swisslog.

I do not use eqsl for the club station callsigns OH2K and OF2K, but for my own calls (OH-, LA- and JW6VDA) I do.
On my next trip to JW-land, I will certainly work a lot of US stations, and the WAS status will be of importance.

So, with my own calls it is a slightly different story. The main reason for using JTAlert is to use the text message utility. I have two options as far as XML lookup from QRZ is concerned, either let JTAlert do it, or leave it to Swisslog. Both works fine. With the online logbooks, Eqsl, QRZ and Clublog, I let Swisslog do the job, and that also works great. And of course the LOTW sync is taken care of via Swisslog.

" I don't see any field in WSJT-X/JTDX to set/save the US State so I have not included it in this query. If you need it I can add it with no problems." Yes please do. I managed to add the e-qsl fields, I think, but the US states (WAS??) i could not find.

I think that sums it up for this time. Enclosed the modified query file.

73 de Tom