ARCHIVE: Australian Ham Radio Discussion Forum ( AHRDF )

I have now released a free software package which is far improved over my previous WSJTXLogViewer code of a few months ago. It may not look a lot different to the user but certainly functions a lot differently internally. It uses exactly the same file formats as its predecessor so just continues with existing files.

It will only work with WSJT-X 1.9.x or later and requires a specific setting to be made within that software. 
 
The new web page at http://www.vk4adc.com/web/software-proje...for-wsjt-x provides details of the software, settings plus a download link for the updated package.

One of the differences is the inclusion of a map image arrangement that displays the logged callsign (or its grid - user selectable) provided that the logged exchange contains grid square info. This software integrates data from the PSKRepView software to provide a larger list of callsigns versus grid squares to do lookups from. there are 3 map image options available depending on how much screen 'real estate' is available to the user. 

Please advise any bugs encountered to 'doug at vk4adc dot com' with a message subject of 'LogView Bug'. 

Doug VK4ADC

LogView for WSJT-X has been updated to V1.0.1.6 dated 4Sep18 to solve a filename error when exporting the logged QSOs to an ADIF file.  The filename error appeared on computers in some countries and not others and was due to regional date formats.  The new format filename (eg  LogView 04Sep18.ADI) solves issues in all regions.

The only other change was to add nominal Latitude and Longtitude values as calculated from maidenhead grid square when displaying the details of an actual QSO and where a grid square value is available (displayed with a yellow background colour).

Still free software...

LogView v1.0.1.7 was released today 

The File menu now provides an easy way to update the CTY.DAT file if internet access is available.
This is not an automatic feature like most of the other internal updates so should be run at least 4-6 times a year. 

The WSJT-X ALL.TXT file is now automatically deleted if it grows to over 5MB AND has just been copied.
Large filesizes (> 20MB) are taking a considerable time to read from the disk (depending on media type eg HDD/ SSD/ USB stick) and can cause WSJT-X errors to regularly appear (File Open errors ). The desired data in this file is processed often so nothing is lost by doing this and it is really just a throw-away file for WSJT-X too.

Issue with latest versions of LogView for WSJT-X as notified by KF5I :

The issue is that newer versions of the WSJT-X do not put the version indicator in the same place in the Windows registry so it is hard to be sure what version is currently installed. Each version creates a new key location and entry.
 
I have updated the code to V1.0.1.8 which allows the software to be run without checking that version detail at all by looking for /SKIPVERSIONCHECK in the properties of the shortcut – essentially the command line for the software.
 
Download the newest release, add the extra detail to the command line, and all should be ok.
 
V 1.0.1.8 :  The only change from v1.7 is that there is now a command line option to place in the properties of the shortcut. Adding /SKIPVERSIONCHECK bypasses the error detection that causes the "Old WSJT-X version notification - You are not using the latest version of the WSJT-X software.  Go to the https://physics.princeton.edu/pulsar/K1JT/wsjtx.html to get the latest version to install. You need to install before this software will operate." message.  With this option in place, it should work with any V2 release of WSJT-X. 
 
73 Doug VK4ADC