locked JTAlert Settings needed to work correctly with HRD 6.7.0.269 : #Announcement #Important


HamApps Support (VK3AMA)
 
Edited

*** IMPORTANT PLEASE READ***



JTAlert users who have upgraded their version of HRD to 6.7.0.269 and followed HRD instructions on updating their existing FT4 QSOs to be adif 3.1.0 compliant, Mode-MFSK, Submode=FT4, need to do the following.

  1. These instructions apply to HRD 6.7.0.269 ONLY.

  2. Upgrade your JTAlert version to 2.16.4 or later.
  3. Open the JTAlert Settings window.

  4. Go to the Logging -> HRD V5/V6 section and enable the "This is a version 6.7.0.269 or later adif 3.1 compliant Log" setting.

    Users of earlier versions of HRD DO NOT enable this option.



  5. Go to the Logging section and scroll the options to reveal the bottom check-boxes (use the right hand scrollbar).
    Enable the "Log FT4 as ADIF 3.1.0 compliant..." setting.

    Users of earlier versions of HRD DO NOT enable this option.


  6. Go to the Scan Log & Rebuild section and run a scan all. This is needed to update the different Alert lists (DXCC, State, etc) to now consider the new MFSK/FT4 recorded QSOs.

  7. NOTE: Any QSOs still in your log that are still set as Mode=FT4 will be ignored by the Scan Log operation. They will need to be update to MFSK/FT4 after which run the Scan Log again.

de Laurie VK3AMA

Join Support@HamApps.groups.io to automatically receive all group messages.