Swisslog's Forum
Swisslog, WSJT-X and JTAlert - Printable Version

+- Swisslog's Forum (
+-- Forum: Swisslog version 5.x (
+--- Forum: General discussion (
+--- Thread: Swisslog, WSJT-X and JTAlert (/showthread.php?tid=487)

Pages: 1 2 3

Swisslog, WSJT-X and JTAlert - JW6VDA - 20-09-2018

Hi Jordi. I'm very active with FT8 these days because of antenna disaster at my club OH2K. Both with that callsign and with my personal ones I use WSJT-X with JTAlert-X, and I maintain the logs in Swisslog for qsl purposes.

Now Swisslog is not one of the loggers supported by JTAlert, so the scan and rebuild feature of JTAlert is of no signifance for me. I have no idea what is need to have JTAlert support Swisslog. Have you considered trying to make Swisslog one of the supported logs in JTAlert-X?

In the What's new for version 5.98 03.08.2018 you write:

"NEW: Logbook view: WSJT-X Exportation query in the ADIF Export folder. This query is very useful if you want to synchronise QSO from Swisslog to WSJT-X/JTDX. Use this query in a logbook view to select automatically all QSOs with modes recognised by WSJT-X/JTDX. Use the export function to export QSOs from Swisslog to the log file used by WSJT-X/JTDX. Simply save the export file as wsjtx_log.adi and copy it in the log directory of WSJT-X/JTDX, overwriting the existing one. That's all"

So, just for your information, this is yesterday's last qso from the Swisslog export file for OH2K:

<PROGRAMID:20>Swisslog for Windows
<CREATED_TIMESTAMP:15>20180919 221736

Exported Fields :
<CALL:5>HA7CD  <QSO_DATE:8>20180919  <TIME_ON:6>173000  <TIME_OFF:6>173000  <BAND:3>60m  <FREQ:6> 5.358  <MODE:3>FT8  <RST_SENT:3>-18  <RST_RCVD:3>-20  <GRIDSQUARE:4>KN07   <STATION_CALLSIGN:4>OH2K  <MY_GRIDSQUARE:6>KP20IF  <APP_SWISSLOG_QSONR:5>20766  <LOTW_QSL_RCVD:1>N  <EQSL_QSL_RCVD:1>N  <EOR>

Here is that qso in wsjtx_log.adi. Note that there are no fields here containg qsl information:

<call:5>HA7CD <gridsquare:4>KN07 <mode:3>FT8 <rst_sent:3>-18 <rst_rcvd:3>-20 <qso_date:8>20180919 <time_on:6>173000 <qso_date_off:8>20180919 <time_off:6>173100 <band:3>60m <freq:8>5.358233 <station_callsign:4>OH2K <my_gridsquare:6>KP20if <tx_pwr:8>10 watts <comment:14>WSJT-X 2.0 RC1 <operator:6>OH6VDA <eor>

And for comparison the same qso from JTAlert-X_log.adi. Here there are QSL fields, and for some peculiar reason, the QSLMSG field is identical to the COMMENTS field. This I will ask Laurie VK3AMA about:

<CALL:5>HA7CD<QSO_DATE:8>20180919<TIME_ON:6>173000<TIME_OFF:6>173100<FREQ:8>5.358233<FREQ_RX:8>5.358394<BAND:3>60m<BAND_RX:3>60m<MODE:3>FT8<RST_SENT:3>-18<RST_RCVD:3>-20<LOTW_QSL_SENT:1>R<LOTW_QSL_RCVD:1>R<QSLMSG:14>WSJT-X 2.0 RC1<GRIDSQUARE:6>KN07ee<DISTANCE:4>1477<TX_PWR:2>10<A_INDEX:1>6<K_INDEX:1>0<SFI:2>68<COMMENT:14>WSJT-X 2.0 RC1<NAME:12>Jozsef Jakab<QTH:16>Torokszentmiklos<CQZ:2>15<ITUZ:2>28<PFX:3>HA7<CONT:2>EU<ADDRESS:72>Jozsef Jakab
25, Szent Istvan Street


For the moment, I do not want to corrupt any if the WSJT-X or JTAlert files, especially since the contents of the ADIF export file for WSTT-X from Swisslog is so different from the original wsjtx_log.adi and the JTAlert-X_log.adi files.

Again, thanks for your patience, your fantastic work with Swisslog and for your quick responses.

73 de Tom OH6VDA

RE: Swisslog, WSJT-X and JTAlert - JW6VDA - 20-09-2018

I got this from Laurie VK3AMA regarding the scan and rebuid feature of JTAlert.

To export, I used the new WSJT-X exportation query in Swisslog, but as you can see from Laurie's answer, that one does not fullfill what is needed for "Scan and rebuild log" in JTAlert:

---- Quote:

"The Scan Log and Rebuild also supports the ADIF file logging option of JTAlert.

Many ADIF users use an export from their main Logger because the Logger it is not supported by JTAlert.

However, if the Swisslog export snippet you provided is typical of a Swisslog adif export, it is not very suitable for JTAlert. It is missing critical data, DXCC and Zones, and I am guessing that it likely doesn't include States for US Callsigns given that it fails to include something as fundamental as the DXCC. Is that export typical?

Matching QSLMSG and COMMENTS fields is not normal and not a bug. You appear to have the "Log WSJT-X Comments to QSL Message field" option enabled in JTAlert (Logging section of the Settings).

As for adding Swisslog as a supported Logger, it is not on the todo list, so no priority assigned. Last time I checked, Swisslog didn't provide any sort of Interface/API (typically TCPIP or UDP) for 3rd party applications (like JTAlert) to log QSOs. Without that fundamental ability, it will never be supported, sorry. If Swisslog does provide an Interface/API that I am unaware of please send the details and I will add it to the "to be investigated" list. Also, the JTAlert help file contains a FAQ topic titled "How to get support for my Logger in JTAlert", primarily written for Logger owners more so than the users of the Logger.

de Laurie VK3AMA"

----End quote

So how can I get an export that fullfill the criteria that Laurie mentions in his mail? As you clearly see, creating my own queries is reall not a strong side with me ...

73 de Tom

RE: Swisslog, WSJT-X and JTAlert - EA3GCV - 21-09-2018

Hi Tom,

First of all if you work on realtime you don't need that JTALERT supports Swisslog at all! You have to configure Swisslog as clearly explained in the "Digital modes interfaces/Operating with WSJT-X" section in the Swisslog Help. Please read the yellow frame where the UDP connection is explained and also a special note for JTALERT users. This way, when you work with WSJT-X, JTALERT and Swisslog together the QSO is saved in all 3 programs at once:

WSJT-X sends QSO data to JTALERT which broadcast the QSO data to Swisslog

When saving the QSO, QSO data is saved in the corresponding ADIF file of WSJT-X and JTALERT and also in the Swisslog database. That's the reason there is no need that JTALERT supports logging to Swisslog. I could include an interface/API specially to save QSOs in JTALERT. But I insist that if you follow the instructions explained in the Swisslog help there is no need to implement anything. In fact, you could use WSJT-X with Swisslog without JTALERT. Swisslog provides you dupe, statistic, call membership and callbook information much better than JTALERT and supports realtime logging to all online logbooks supporting multicallsign configuration. Except some very specific options (which maybe you don't use it), you can avoid using JTALERT. JTALERT is very useful to be used with other logging programs which doesn't support WSJT-X directly and/or lacks of the Swisslog features.

I have created a special query to export QSOs to JTALERT implementing the required ADIF fields. Some fields are not included simply because are not supported by Swisslog such as BAND_RX, FREQ_RX, A_INDEX, K_INDEX, MY_CQ_ZONE, MY_ITU_ZONE. However, this should not suppose any problem. 

Please unzip the attached file into the ADIF export folder located into the Queries folder. Use this query to export into ADIF from Swisslog giving the same name you gave to the Log ADIF file and replace. Remember that this query will automatically select all the digital modes supported by WSJT-X/JTDX.

You can explain Laurie that Swisslog allows to export any field into ADIF. It depends on the query definition. No other logging program allows this wide flexibility as Swisslog offers. 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. 

In the next version I will include this query (after you tell me that is working OK) and I will also modify the WSJT-X exportation query to include the Operator. DXCC field is already included in this query in 5.98b.

Best 73

RE: Swisslog, WSJT-X and JTAlert - JW6VDA - 21-09-2018

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

RE: Swisslog, WSJT-X and JTAlert - EA3GCV - 21-09-2018

Hello Tom,

Ok now I understand everything. I just wanted to inform that nearly everything (except the message utility and some other functions) is performed by Swisslog. I know mant Swisslog users that now is not using JTALERT because they don't find it interesting after all the implementations of the last versions.

I have not received the modified query but no need to send. The US State is saved in the Region field. I will add it in the query for JTALERT exportation. I saw that JTALERT uses the State field. Just edit tje Query and add the Region field. Or I can send you the new query if you wish.

The Station_Callsign field was already included in the query. All info regarding your QTH is taken from the selected MYQTH used during the QSO. Swisslog don't use a TX Power field for every QSO, but in the MYQTH profile you have the Power field. As you know you can handle unlimited callsigns/QTHs with Swisslog. This query will work perfectly to export to JTALERT if you assign properly every QSO to the corresponding MyQTH.

Don't hesitate to contact me again if you need something else regarding this or other matter.

Best 73

RE: Swisslog, WSJT-X and JTAlert - JW6VDA - 21-09-2018

Thanks a lot. I tried to upload the edited query file (I also added eQSL_Send and EQSL_RECEIVED, Regions and Sub-regions). Maybe I shold have called the zip-file a different nam? I will try that, then you can have a look. I cannot find a field for WAS, even though the Statistic is defined. Anyway, If you have the time, by all means send the exportation file to me, pse also include the eQSL fields.

73 de Tom

RE: Swisslog, WSJT-X and JTAlert - EA3GCV - 21-09-2018

Hi Tom,

Please find attached the new query including the SubRegion and eQSL fields. There are not WAS or US County fields in Swisslog. Swisslog uses the Region field to save the WAS and the SubRegion to save the US County. But these fields (the same as the Diploma or SP fields) are used for many other statistics so depending the DXCC and the award criteria it may contain many other references for other DXCC. The Region field is exported into ADIF as STATE and SubRegion as CNTY. According to ADIF specifications STATE contains the Primary Administrative Subdivision (WAS, VE province, EA province, JA Island, etc) and CNTY contains the Secondary Administrative Subdivision (US county, Ja Gun, Russians Districts RDA, etc).

Best 73

P.S.: I forgot to mention... maybe you should consider using Swisslog at your Club instead of N1MM as regular logging program to get all the benefits of Swisslog , don't you think?  Angel

RE: Swisslog, WSJT-X and JTAlert - JW6VDA - 21-09-2018

We will definitely consider it!

Thanks! Big Grin

RE: Swisslog, WSJT-X and JTAlert - JW6VDA - 23-09-2018

Hello again.

I have looked into the possibility of using Swisslog at my club. Angel

Because of the need to know who has been making the different qsos, we implement the OPERATOR field, which is in use both in N1MM+ (via the ctrl-o quick menu option) and in WSJT-X (set in the settings menu, the reporting tab if I remember correctly). Laurie, VK3AMA has also implemented this JTAlert in the ADIF output in the "last_qso.adi" and the UDF broadcast of the last qso. It will also be implemented for the ADIF file log in the next public release of JTAlert.

This <OPERATOR> field is not present in Swisslog. All the qsos (20733) in the database for OH2K are imported from N1MM+, and thus contains the <OPERATOR> field, but as you can see from the ADIF export from Swisslog (ADIF All fields query), this has not been imported, at least I cannot find it.

In the My qth tab of the qso entry window, there is a field for operator name. Could it be feasible to make a field there for operator callsign?

For illustration, here are the ADIs for the same qso from WSJT-X, from N1MM+ and from Swisslog:

WSJT-X ADIF Export<eoh>
<call:6>OH2FQV <gridsquare:4>KP20 <mode:3>FT8 <rst_sent:3>+04 <rst_rcvd:3>+06 <qso_date:8>20180918 <time_on:6>090000 <qso_date_off:8>20180918 <time_off:6>090045 <band:3>20m <freq:9>14.079215 <station_callsign:4>OH2K <my_gridsquare:6>KP20if <tx_pwr:8>25 watts <comment:14>WSJT-X 2.0 RC1 <operator:6>OH6VDA <eor>

ADIF Export from - Version 1.0.7283.0
Built: 18.9.2018 16:09:00
OH2K logs generated @ 2018-09-22 13:08:05Z
Contest Name: DX - 1900-01-01

Generated for OH6VDA

<PROGRAMID:20>Swisslog for Windows
<CREATED_TIMESTAMP:15>20180923 155217

<CALL:6>OH2FQV  <QSO_DATE:8>20180918  <TIME_ON:6>090000  <TIME_OFF:6>090045  <BAND:3>20m  
<FREQ:6>14.079  <MODE:3>FT8  <NAME:14>Jari Ahdenkari  <RST_SENT:3>+04  <STX:1>0  
<RST_RCVD:3>+06  <SRX:1>0  <QSL_RCVD:1>N  <QSL_SENT:1>N  <LOTW_QSL_SENT:1>Y  <LOTW_QSLSDATE:8>20180919  
<COMMENT:41>A Index: 11
K Index: 2
WSJT-X 2.0 RC1
  <DXCC:3>224  <PFX:3>OH2  <CQZ:2>15  
<MY_RIG:8>FT1000MP  <MY_SIG:8>No Event  <QSO_COMPLETE:1>Y  <APP_SWISSLOG_QSONR:5>20762  

<DXCC:3>224  <PFX:3>OH2  <CQZ:2>15  <ITUZ:2>18  <CONT:2>EU  <SFI:2>68  <STATION_CALLSIGN:4>OH2K  

73 de Tom

RE: Swisslog, WSJT-X and JTAlert - EA3GCV - 24-09-2018

Hi Tom,

Yes, you are right, Swisslog doesn't implement the OPERATOR field. A new field should be added in the MYQTH table to set there the operator's callsign, to fill it out only if it's different from the station callsign. This field will be exported as OPERATOR according the ADIF specifications.

I will check if I can add it in the next version.... In this case you should have to add a new MyQTH for everyone of your operators in the Club. Main call will be the same for all of them but you can set a QTh abbreviaton like "Operator OHxxxx" etc.

Best 73 and stay tuned