Show:Fields This option enables the operator to choose which of the thirteen fields will be displayed in the ALE. Tracking The Tracking menu enables the ALE to use the data coming from the rid for frequency or mode and automatically populated into the ALE. This lets the operator know that these items have been worked before. Show Worked Status This option enables a W icon to display for Call, Country, and Locator fields. Menu Position The choices of positioning the menu on top or bottom are provided. This is useful when vertical or horizontal space is restrained. RST Rcvd / Sent This provides options for canned values of RST.īutton Position The operator can select from bottom, middle, and right side location of the Update, Cancel, Reset, and Add Spot buttons. This is helpful when using a value like Queued to set the LOTW value so that it’s easy to do a search for QSLs that need to be uploaded to LOTW. QSL Defaults This enables the operator to choose the initial values for the three QSL fields. This accommodates QSOs of longer durations.įont Option This enables the operator to change the fonts used in the dialog ALE.
The ALE’s menu bar has a number of menu items. Menu Barīut first, it’s necessary to understand the options for the ALE. The ALE window is opened by clicking on the Add button in the toolbar. This information is contained within the Add Logbook Entry (ALE) window and its fifteen tabs. Ham Radio Deluxe Logbook has a number of powerful features for tracking QSO data.
In fact the only reason I use JTAlert is to tell me what countries have been decoded and whether I need them for DXCC.Solution home Ham Radio Deluxe User Guides Logbook Creating and Managing QSOs
Reading between the lines it appears that the writer of the JTALert software and the developers of HRD initially were not in communication but now through an intermediary seem to have resolved their differences.Īs it happened my particular setup never made use of JTALert to write to the database at all! JT65-HF-HB9HQX uses the API to write to the database without the use of JTALert. Ham Radio Deluxe was updated (Version 6.3.0.439) to remove the kill mechanism and all is good again. This now means the current version of JTAlert (2.6.21 or greater) writes to the database via the API and is no longer corrupting the database. Then there were various software updates to JTAlert after HRD had given the API details out publicly. I can understand the reasons behind this as they are a relatively small company and potentially could have been swamped with support calls to try to fix something that was not of their making. So they took the drastic steps of preventing JTAlert from running when HRD logbook was running. HRD had found it was corrupting certain aspects of the database and numerous call tickets had been raised around the matter. The reason behind this was to protect their customers databases from being corrupted.Įssentially JTAlert when used with other JT65 software was being used to write the contact details directly to the HRD logbook database. All was working well until the good people at HRD decided to incorporate a kill mechanism into their logbook software (version 6.3.0.435) which would kill the JTAlert.exe process. I also use Ham Radio Deluxe Logbook to store contacts - I am a customer of HRDSoftwareLLC and this is well worth paying for. I also use a paid for Ham Radio Deluxe Rig Control to operate my radio.
First of all I use JTAlert and JT65-HF-HB9HQX (both of which have kindly been given for free for the use of radio amateurs) as my method of transmitting JT65 modes.