Date   

locked Re: v12.14.5 Text Message Don't Work

HamApps Support (VK3AMA)
 

On 3/10/2019 4:24 pm, WB5JJJ - George wrote:
The F5 access to call up text messages does NOT work in the Normal layout version.  Running Win10 all updates.  I5 CPU. 8Gb RAM.  CPU load <15% with everything running as normal.  Rolled back to 12.14.4 Normal layout and F5 again works.
--
73's
George - WB5JJJ
George,

Working here in my tests. There were no changes in the code involving hotkeys.
Does the window open if you use the "View -> Text Message Window" menu?

de Laurie VK3AMA


locked Re: Minor persistent glitch

HamApps Support (VK3AMA)
 

On 3/10/2019 12:35 pm, HH Brakob wrote:

Still one minor glitch at my station.

 

The “#” column in the bottom (US State) line still reflects the same total as the “DXCC” line.

73, de Hans, KØHB

Hans,

I thought I clobbered that defect long ago.

What build of JTAlert are you running "Traditional" or the "Alt Layout", I couldn't tell from your image? Please test the other build type (just use the appropriate shortcut), does it also display the incorrect totals data or is the defect build type specific?

de Laurie VK3AMA


locked Re: Instructions & Initial Setup DXCC Alert for Individual Bands

HamApps Support (VK3AMA)
 

On 3/10/2019 9:43 am, Mark W2OR via Groups.Io wrote:
Thank you.  That was helpful.  Even though I've been using the scan and various alerts for months now, I'm still scratching my head on one or two things (paragraph three below).  I'll figure it all out eventually.

My DXCC alert objectives are not unlike most other stations' DXCC objectives.  Thankfully, JTA continues to work perfectly for the Any Band & Any Mode DXCC alert.  There are 24 entities correctly listed in the Wanted column, and the JTA alert for this main objective appears to work perfectly.

I'm still hung up on how to configure the Second Objective: That is, to configure JTA to alert when band-specific unworked entities are decoded.  I need this alert active simultaneously for multiple bands.  In my JTA, only one band (60m) seems to have the "Wanted" column correctly populated with countries.  All the other bands have nothing at all in the "Wanted" column.  As such, this gives the impression that JTA will not alert for any of those other bands when an unworked band-specific entity is decoded.  In other words, I'm not sure how to get that Wanted column populated for all bands, remain that way, and then have the alerts work simultaneously for all bands. As mentioned above, in a few more days I'll have it figured out. Eventually.

P.S.  The Marathon alert works fine, likewise the Wanted Callsign, and Continent, and other alerts seem to work marvelously well when they are used.  This is one fantastic program !!
Mark,

You mention "
Any Band & Any Mode DXCC alert". If your setting the DXCC alert Band and Mode tracking to Any Band and Any Mode than you will never get Band specific alerts. You need to leave the tracking selector for the dxcc alert to "Individual Band".

When you are viewing an individual Band wanted list in the Settings, and you have by individual Mode tracking selected, make sure you select the mode of interest. It is very easy to have the mode selector on JT65 and if you only log FT8, than the wanted lists will appear incorrect. JTAlert does its best to remember the last mode you selected, but that only works if your not switching Mode and Band tracking types.

So I can better understand what your describing, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis. Include a note of a DXCC Band you feel is populated with Countries.

de Laurie VK3AMA



locked v12.14.5 Text Message Don't Work

WB5JJJ - George
 
Edited

The F5 access to call up text messages does NOT work in the Normal layout version.  Running Win10 all updates.  I5 CPU. 8Gb RAM.  CPU load <15% with everything running as normal.  Rolled back to 12.14.4 Normal layout and F5 again works.
--
73's
George - WB5JJJ


locked Minor persistent glitch

Radio K0HB
 

Installed 2.14.5.  Works as announced!

 

Still one minor glitch at my station.

 

The “#” column in the bottom (US State) line still reflects the same total as the “DXCC” line.

 

 

73, de Hans, KØHB
"Just a boy and his radio"™

 


locked Re: Instructions & Initial Setup DXCC Alert for Individual Bands

Mark W2OR
 

Thank you.  That was helpful.  Even though I've been using the scan and various alerts for months now, I'm still scratching my head on one or two things (paragraph three below).  I'll figure it all out eventually.

My DXCC alert objectives are not unlike most other stations' DXCC objectives.  Thankfully, JTA continues to work perfectly for the Any Band & Any Mode DXCC alert.  There are 24 entities correctly listed in the Wanted column, and the JTA alert for this main objective appears to work perfectly.

I'm still hung up on how to configure the Second Objective: That is, to configure JTA to alert when band-specific unworked entities are decoded.  I need this alert active simultaneously for multiple bands.  In my JTA, only one band (60m) seems to have the "Wanted" column correctly populated with countries.  All the other bands have nothing at all in the "Wanted" column.  As such, this gives the impression that JTA will not alert for any of those other bands when an unworked band-specific entity is decoded.  In other words, I'm not sure how to get that Wanted column populated for all bands, remain that way, and then have the alerts work simultaneously for all bands. As mentioned above, in a few more days I'll have it figured out. Eventually.

P.S.  The Marathon alert works fine, likewise the Wanted Callsign, and Continent, and other alerts seem to work marvelously well when they are used.  This is one fantastic program !!



locked Re: 2.14.5 Issue

Ed Wilson
 

Yes, I am testing FT4 under JTDX. I will contact Igor to report this issue.

On Oct 2, 2019, at 7:18 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 3/10/2019 9:09 am, Ed Wilson via Groups.Io wrote:
I just installed 2.14.5 on my system without incident. I discovered that I cannot single-click on a call sign in the call sign display in JTAlert to answer a CQ when running FT4 under JTDX. This approach works fine with FT8 under JTDX and with JTDX and WSJT-X using both FT4 and FT8. My UDP settings seem identical for both JTDX and WSJT-X.

Is this a JTDX issue or a JTAlert issue or have I configured JTDX incorrectly somehow?

Thanks!

Ed, K0KC
Ed,

Since JTDX with FT4 has not been publicly released (still in beta testing as far as I know), the cause is very likely something within the JTDX.

The JTAlert code for managing sending commands to WSJT-X and JTDX in response to a single-click is Mode independent. There are no mode checks performed before sending the command to the relevant application instance, FT4 clicks  should work the same as FT8 clicks.  This further suggests the problem is with JTDX.

If your beta testing JTDX, I suggest you raise this issue with them.

de Laurie VK3AMA


locked Re: 2.14.5 Issue

HamApps Support (VK3AMA)
 

On 3/10/2019 9:09 am, Ed Wilson via Groups.Io wrote:
I just installed 2.14.5 on my system without incident. I discovered that I cannot single-click on a call sign in the call sign display in JTAlert to answer a CQ when running FT4 under JTDX. This approach works fine with FT8 under JTDX and with JTDX and WSJT-X using both FT4 and FT8. My UDP settings seem identical for both JTDX and WSJT-X.

Is this a JTDX issue or a JTAlert issue or have I configured JTDX incorrectly somehow?

Thanks!

Ed, K0KC
Ed,

Since JTDX with FT4 has not been publicly released (still in beta testing as far as I know), the cause is very likely something within the JTDX.

The JTAlert code for managing sending commands to WSJT-X and JTDX in response to a single-click is Mode independent. There are no mode checks performed before sending the command to the relevant application instance, FT4 clicks  should work the same as FT8 clicks.  This further suggests the problem is with JTDX.

If your beta testing JTDX, I suggest you raise this issue with them.

de Laurie VK3AMA


locked Re: 2.14.5 Issue (Edited)

Ed Wilson
 



On Oct 2, 2019, at 7:09 PM, Ed Wilson via Groups.Io <ed.wilson@...> wrote:

Laurie,

I just installed 2.14.5 on my system without incident. I discovered that I cannot single-click on a call sign in the call sign display in JTAlert to answer a CQ when running FT4 under JTDX. This approach works fine with FT8 under JTDX and with WSJT-X using both FT4 and FT8. My UDP settings seem identical for both JTDX and WSJT-X.

Is this a JTDX issue or a JTAlert issue or have I configured JTDX incorrectly somehow?

Thanks!



On Wednesday, October 2, 2019, 05:55:09 PM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


The Latest JTAlert version 2.14.5 is now available @ https://HamApps.com

With this release there is no longer a separate installer for the "Alternate Layout" (now called "Alt Layout") build of JTAlert. Both JTAlert build types, "Traditional" (menus in titlebar) and "Alt Layout" (menus below titlebar) are included in the one installer package. Switching between build types is now a simple matter or using the correct shortcut, there is no need to install a different build. Each Build type / Operation type  (WSJT-X or JTDX) combination uses a unique coloured shortcut icon.

For users who can't or refuse to read release notes, the shortcuts for each build & operation type are...
  • Red => JTAlert for WSJT-X.
  • Blue => JTAlert for JTDX.
  • Green => JTAlert (Alt Layout) for WSJT-X.
  • Purple => JTAlert (Alt Layout) for JTDX.
See the release notes below for a full list of changes and fixes.

As usual the JTAlert installer file has been run through VirusTotal. HamApps.com has the link to the full analysis results. The installer file produced two false-positives. The GData warning is simply due to JTAlert being created using the AutoIT script compiler and the Trapmine warning is a machine-learning (ml) warning which is similar to the reputation type warnings seen in the past from Norton (low installed user-base). Both are false-positives, neither identifying a know infection.

    <2.14.5_ScanResults.png>


The Release Notes...
  New Features:
    - Option to turn off State Code display after Callsign.
       (Default: OFF, Window: Settings, Section: Alerts, Wanted States).

  Changes:
    - The JTAlert "Alternate Layout" build has been renamed "Alt Layout".
    - "Alt Layout" builds of JTAlert are no longer provided via a seperate installer.
       The one installer now includes both builds of JTAlert, "Traditional" with
       menus in the title bar and "Alt Layout" with the menu below the titlebar.
       Switching to a different layout build is simply handled by executing the
       correct shortcut.
    - "Alt Layout" builds of JTAlert now use unique colored icons for the shortcuts
       and the JTAlert window titlebar.
         Red => JTAlert for WSJT-X.
         Blue => JTAlert for JTDX.
         Green => JTAlert (Alt Layout) for WSJT-X.
         Purple => JTAlert (Alt Layout) for JTDX.
    - Support for JTDX non-standard FT4 UDP decode mode identification
       character. (WSJT-X = "+", JTDX = ":")

  Fixes:
    - ADIF import window progress bar not displaying to the full width when the
       import has completed and reaches 100%.
    - Log4OM MySQL logs not being scanned correctly resulting in all entities
       (dxcc, state, etc) being flagged as needed. (2.14.4 defect)
    - Application auto-start entry "Close" checkbox incorrectly enabled when
       the "Start" checkbox is unchecked.
    - Desktop shortcuts for additional callsigns (under the Station section of
       the Settings window) created for no-longer-supported JT65-HF & HB9HQX
    - TX Mode not displayed in JTAlert titlebar status (between the square
       brackets) when JTAlert is working with JTDX.

de Laurie VK3AMA

<2.14.5_ScanResults.png>


locked 2.14.5 Issue

Ed Wilson
 

Laurie,

I just installed 2.14.5 on my system without incident. I discovered that I cannot single-click on a call sign in the call sign display in JTAlert to answer a CQ when running FT4 under JTDX. This approach works fine with FT8 under JTDX and with JTDX and WSJT-X using both FT4 and FT8. My UDP settings seem identical for both JTDX and WSJT-X.

Is this a JTDX issue or a JTAlert issue or have I configured JTDX incorrectly somehow?

Thanks!



On Wednesday, October 2, 2019, 05:55:09 PM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


The Latest JTAlert version 2.14.5 is now available @ https://HamApps.com

With this release there is no longer a separate installer for the "Alternate Layout" (now called "Alt Layout") build of JTAlert. Both JTAlert build types, "Traditional" (menus in titlebar) and "Alt Layout" (menus below titlebar) are included in the one installer package. Switching between build types is now a simple matter or using the correct shortcut, there is no need to install a different build. Each Build type / Operation type  (WSJT-X or JTDX) combination uses a unique coloured shortcut icon.

For users who can't or refuse to read release notes, the shortcuts for each build & operation type are...
  • Red => JTAlert for WSJT-X.
  • Blue => JTAlert for JTDX.
  • Green => JTAlert (Alt Layout) for WSJT-X.
  • Purple => JTAlert (Alt Layout) for JTDX.
See the release notes below for a full list of changes and fixes.

As usual the JTAlert installer file has been run through VirusTotal. HamApps.com has the link to the full analysis results. The installer file produced two false-positives. The GData warning is simply due to JTAlert being created using the AutoIT script compiler and the Trapmine warning is a machine-learning (ml) warning which is similar to the reputation type warnings seen in the past from Norton (low installed user-base). Both are false-positives, neither identifying a know infection.

   


The Release Notes...
  New Features:
    - Option to turn off State Code display after Callsign.
       (Default: OFF, Window: Settings, Section: Alerts, Wanted States).

  Changes:
    - The JTAlert "Alternate Layout" build has been renamed "Alt Layout".
    - "Alt Layout" builds of JTAlert are no longer provided via a seperate installer.
       The one installer now includes both builds of JTAlert, "Traditional" with
       menus in the title bar and "Alt Layout" with the menu below the titlebar.
       Switching to a different layout build is simply handled by executing the
       correct shortcut.
    - "Alt Layout" builds of JTAlert now use unique colored icons for the shortcuts
       and the JTAlert window titlebar.
         Red => JTAlert for WSJT-X.
         Blue => JTAlert for JTDX.
         Green => JTAlert (Alt Layout) for WSJT-X.
         Purple => JTAlert (Alt Layout) for JTDX.
    - Support for JTDX non-standard FT4 UDP decode mode identification
       character. (WSJT-X = "+", JTDX = ":")

  Fixes:
    - ADIF import window progress bar not displaying to the full width when the
       import has completed and reaches 100%.
    - Log4OM MySQL logs not being scanned correctly resulting in all entities
       (dxcc, state, etc) being flagged as needed. (2.14.4 defect)
    - Application auto-start entry "Close" checkbox incorrectly enabled when
       the "Start" checkbox is unchecked.
    - Desktop shortcuts for additional callsigns (under the Station section of
       the Settings window) created for no-longer-supported JT65-HF & HB9HQX
    - TX Mode not displayed in JTAlert titlebar status (between the square
       brackets) when JTAlert is working with JTDX.

de Laurie VK3AMA


locked New JTAlert 2.14.5 available. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The Latest JTAlert version 2.14.5 is now available @ https://HamApps.com

With this release there is no longer a separate installer for the "Alternate Layout" (now called "Alt Layout") build of JTAlert. Both JTAlert build types, "Traditional" (menus in titlebar) and "Alt Layout" (menus below titlebar) are included in the one installer package. Switching between build types is now a simple matter or using the correct shortcut, there is no need to install a different build. Each Build type / Operation type  (WSJT-X or JTDX) combination uses a unique coloured shortcut icon.

For users who can't or refuse to read release notes, the shortcuts for each build & operation type are...
  • Red => JTAlert for WSJT-X.
  • Blue => JTAlert for JTDX.
  • Green => JTAlert (Alt Layout) for WSJT-X.
  • Purple => JTAlert (Alt Layout) for JTDX.
See the release notes below for a full list of changes and fixes.

As usual the JTAlert installer file has been run through VirusTotal. HamApps.com has the link to the full analysis results. The installer file produced two false-positives. The GData warning is simply due to JTAlert being created using the AutoIT script compiler and the Trapmine warning is a machine-learning (ml) warning which is similar to the reputation type warnings seen in the past from Norton (low installed user-base). Both are false-positives, neither identifying a know infection.

   


The Release Notes...
  New Features:
    - Option to turn off State Code display after Callsign.
       (Default: OFF, Window: Settings, Section: Alerts, Wanted States).

  Changes:
    - The JTAlert "Alternate Layout" build has been renamed "Alt Layout".
    - "Alt Layout" builds of JTAlert are no longer provided via a seperate installer.
       The one installer now includes both builds of JTAlert, "Traditional" with
       menus in the title bar and "Alt Layout" with the menu below the titlebar.
       Switching to a different layout build is simply handled by executing the
       correct shortcut.
    - "Alt Layout" builds of JTAlert now use unique colored icons for the shortcuts
       and the JTAlert window titlebar.
         Red => JTAlert for WSJT-X.
         Blue => JTAlert for JTDX.
         Green => JTAlert (Alt Layout) for WSJT-X.
         Purple => JTAlert (Alt Layout) for JTDX.
    - Support for JTDX non-standard FT4 UDP decode mode identification
       character. (WSJT-X = "+", JTDX = ":")

  Fixes:
    - ADIF import window progress bar not displaying to the full width when the
       import has completed and reaches 100%.
    - Log4OM MySQL logs not being scanned correctly resulting in all entities
       (dxcc, state, etc) being flagged as needed. (2.14.4 defect)
    - Application auto-start entry "Close" checkbox incorrectly enabled when
       the "Start" checkbox is unchecked.
    - Desktop shortcuts for additional callsigns (under the Station section of
       the Settings window) created for no-longer-supported JT65-HF & HB9HQX
    - TX Mode not displayed in JTAlert titlebar status (between the square
       brackets) when JTAlert is working with JTDX.

de Laurie VK3AMA


locked Re: Text Online/Offline

Gilbert Baron <w0mn00@...>
 

Sounds good to abandon those but it is going to be a real task. 😊

Good luck and I am sure it will be a great step up.

 

Outlook Laptop Gil W0MN

Hierro Candente Batir de Repente

44.08226N 92.51265 W en34rb

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Wednesday, October 2, 2019 01:28
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Text Online/Offline

 

On 2/10/2019 1:28 pm, Michael Black via Groups.Io wrote:

How's about we also add "Offline" to the text window status in addition to "Online".

I find myself staring at it wondering if it's been updated or not.

 

Is that possible?

 

de MIke W9MDB

Mike,

I tend to agree. Currently, anything other than the "Online" status indicates either offline, host access denied or unreachable, or internet down.

I will see what I can do for the JTAlert 2.14.6 release (as you know 2.14.5 is imminent).

I wont bother with a technical explanation of the current implementation, I will just say, I will be very glad when I have finally abandoned the single-threaded, synchronous (blocking), non-OOP, AutoIT code I have to work with and the hacks with plugin processes mimicking thread-like behaviour. The JTAlert V2 code-base has become somewhat of a mess over the years.

de Laurie VK3AMA


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: Text Online/Offline

HamApps Support (VK3AMA)
 

On 2/10/2019 1:28 pm, Michael Black via Groups.Io wrote:
How's about we also add "Offline" to the text window status in addition to "Online".
I find myself staring at it wondering if it's been updated or not.

Is that possible?

de MIke W9MDB
Mike,

I tend to agree. Currently, anything other than the "Online" status indicates either offline, host access denied or unreachable, or internet down.

I will see what I can do for the JTAlert 2.14.6 release (as you know 2.14.5 is imminent).

I wont bother with a technical explanation of the current implementation, I will just say, I will be very glad when I have finally abandoned the single-threaded, synchronous (blocking), non-OOP, AutoIT code I have to work with and the hacks with plugin processes mimicking thread-like behaviour. The JTAlert V2 code-base has become somewhat of a mess over the years.

de Laurie VK3AMA


locked Text Online/Offline

Michael Black
 

How's about we also add "Offline" to the text window status in addition to "Online".
I find myself staring at it wondering if it's been updated or not.

Is that possible?

de MIke W9MDB



locked Re: Instructions & Initial Setup DXCC Alert for Individual Bands

HamApps Support (VK3AMA)
 

On 2/10/2019 9:43 am, Mark W2OR via Groups.Io wrote:
Instructions & Initial Setup DXCC Alert for Individual Bands

If anyone knows of written instructions for the above, kindly share them here.  Thank you.

Background:  I thought I had figured out this alert setup many months ago, as it seemed to be working, but apparently I was wrong.  When I check the Wanted DXCC settings, for Individual Band, most all the bands tracked are BLANK in the "Wanted" window, even after checking the Band Enable and Select box, and after completing a Scan Log and Rebuild function.  I'm missing some basic setup procedure here, and instructions would sure help.  The settings for "Any Band" "Any Mode" seem to be fine.  I just need instructions for setting up for individual bands, including needed entities for 60 Meters and needed entities for 160 Meters, two bands where I chase DX entities individually, aside from all-band DXCC.  Thank you.

Yes, I am using JTA v.2.14.4, downloaded after the revision to the initial release.
Mark,

Its all very simple provided you use the Scan Log function and don't try to combine manually managing your Wanted dxcc lists and Log Scanning as the Scan Log will remove any manual changes you have made.

The Scan Log automatically builds the different lists for each of the possible Band & Mode tracking combinations, so only a single scan is needed, there is no need to run an additional scan if you decode to change your mode tracking (as an example) from Any Band to Individual Band.

The issue you need to be aware of is the QSL confirmation settings your using for the dxcc scan. Your log needs to include the QSL confirmations matching what you set in JTAlert. For example, if you set dxcc scan to only consider LoTW confirmed QSOs, you Log needs to have been synced with LoTW to ensure there are LoTW confirmed QSO for JTAlert to find.

Important: Whatever Band & Mode tracking you have selected for the dxcc alert when you exit the Settings will dictate the wanted lists  JTAlert will use for alerting. It is NOT possible to use different Mode Tracking for specific Bands.

de Laurie VK3AMA


locked Instructions & Initial Setup DXCC Alert for Individual Bands

Mark W2OR
 

Greetings,

Instructions & Initial Setup DXCC Alert for Individual Bands


If anyone knows of written instructions for the above, kindly share them here.  Thank you.

Background:  I thought I had figured out this alert setup many months ago, as it seemed to be working, but apparently I was wrong.  When I check the Wanted DXCC settings, for Individual Band, most all the bands tracked are BLANK in the "Wanted" window, even after checking the Band Enable and Select box, and after completing a Scan Log and Rebuild function.  I'm missing some basic setup procedure here, and instructions would sure help.  The settings for "Any Band" "Any Mode" seem to be fine.  I just need instructions for setting up for individual bands, including needed entities for 60 Meters and needed entities for 160 Meters, two bands where I chase DX entities individually, aside from all-band DXCC.  Thank you.

Yes, I am using JTA v.2.14.4, downloaded after the revision to the initial release.


locked Re: WAS States

HamApps Support (VK3AMA)
 

On 1/10/2019 1:57 am, Alfred Reeves wrote:
Thanks for your reply.  Its a mute issue at this time as I worked and confirmed another OR station.

Thanks for your help and most of all thanks for a wonderful product.

Beat 73
Al
W1JHU
Al,

Please, I would like to examine your log, in particular the entry for the 80m FT4 OR QSO that JTAlert was unable to detect during the log scan. an adif export of your log will be sufficient with mention of the Callsign of the QSO in question.

Thanks
de Laurie VK3AMA


locked Re: Text Messaging

John H. Long Jr.
 

I would like more information as I have never gotten it to work.
 
 
 
John H. Long Jr.
KW7A
1370 N 150 E
Nephi, UT 84648
USA
 
(435) 888-LONG
john@...
 
 
 

--------- Original Message ---------
Subject: Re: [HamApps] Text Messaging
From: 'John Holmes W9ILY' <w9ily@...>
Date: 9/30/19 10:28 am
To: Support@HamApps.groups.io

Michael,
YES! JTAlert will definitely send you text messages for the DXpedition (or IOTA, etc.) calls that interest you. It works very well using SendEmail.exe. Let me know if you'd like more info..
John W9ILY


locked Re: Text Messaging

John Holmes W9ILY
 

Michael,
YES! JTAlert will definitely send you text messages for the DXpedition (or IOTA, etc.) calls that interest you. It works very well using SendEmail.exe. Let me know if you'd like more info..
John W9ILY


locked Re: WAS States

Alfred Reeves
 

Ron:

Thanks for your reply.  Yes I do have the latest TQSL config file installed.  However, its a mute issue at this time as I worked and confirmed another OR station.


TNX and 73
Al
W1JHU

On 9/30/2019 8:52 AM, Ron W3RJW via Groups.Io wrote:
Al,

Is your TQSL config file up-to-date ??

"Continuing with the May 2019 implementation of the new MFSK Submode FT4, and the WSJT-X Development Group's July 15, 2019 General Availability (GA) release of WSJT-X 2.1.0, ARRL is updating LoTW and the WAS Awards program to implement FT4 for WAS Digital Award Endorsement.  No other endorsements are under consideration at this time."
--
73
Ron, W3RJW

7161 - 7180 of 32849