Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Swisslog, WSJT-X and JTAlert
20-09-2018, 08:43 AM,
#1
Swisslog, WSJT-X and JTAlert
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:


<ADIF_VER>:5>3.0.8
<PROGRAMID:20>Swisslog for Windows
<PROGRAMVERSION:5>5.98b
<CREATED_TIMESTAMP:15>20180919 221736

Exported Fields :
CALL,QSO_DATE,TIME_ON,TIME_OFF,BAND,FREQ,MODE,RST_SENT,RST_RCVD,GRIDSQUARE,STATION_CALLSIGN,MY_GRIDSQUARE,APP_SWISSLOG_QSONR,LOTW_QSL_RCVD,LOTW_QSLRDATE,APP_SWISSLOG_LOTWSTATUS,APP_SWISSLOG_EQSLSTATUS,EQSL_QSL_RCVD,EQSL_QSLRDATE
<EOH>
<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
Torokszentmiklos
H-5200

Hungary<DXCC:3>239<COUNTRY:7>Hungary<MY_GRIDSQUARE:6>KP20if<MY_CQ_ZONE:2>15<MY_ITU_ZONE:2>18<STATION_CALLSIGN:4>OH2K<QSO_COMPLETE:1>Y<EOR>

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
Happy Swisslog user since 1989.

JW6VDA permanently may 1983 - august 1989 and august 2001 - august 2014.
LA6VDA 1989-2001.

Now OH6VDA since september 2014.
Reply


Messages In This Thread
Swisslog, WSJT-X and JTAlert - by JW6VDA - 20-09-2018, 08:43 AM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 20-09-2018, 01:06 PM
RE: Swisslog, WSJT-X and JTAlert - by EA3GCV - 21-09-2018, 03:15 AM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 21-09-2018, 09:57 AM
RE: Swisslog, WSJT-X and JTAlert - by EA3GCV - 21-09-2018, 11:03 AM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 21-09-2018, 12:15 PM
RE: Swisslog, WSJT-X and JTAlert - by EA3GCV - 21-09-2018, 01:39 PM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 21-09-2018, 02:16 PM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 23-09-2018, 02:57 PM
RE: Swisslog, WSJT-X and JTAlert - by EA3GCV - 24-09-2018, 10:40 AM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 26-09-2018, 08:13 PM
RE: Swisslog, WSJT-X and JTAlert - by EA3GCV - 26-09-2018, 11:34 PM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 27-09-2018, 06:18 AM
RE: Swisslog, WSJT-X and JTAlert - by EA3GCV - 27-09-2018, 10:27 AM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 27-09-2018, 12:37 PM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 01-10-2018, 08:21 PM
RE: Swisslog, WSJT-X and JTAlert - by EA3GCV - 02-10-2018, 12:16 AM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 02-10-2018, 06:11 AM
RE: Swisslog, WSJT-X and JTAlert - by EA3GCV - 02-10-2018, 09:02 AM
RE: Swisslog, WSJT-X and JTAlert - by JW6VDA - 08-11-2018, 08:48 AM
RE: Swisslog, WSJT-X and JTAlert - by EA3GCV - 08-11-2018, 06:56 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)