Date   

locked Re: IC 7000 and Signal Link #FT8 - CAT Control fails #FT8

m_scot_alex
 

Name? Callsign?

JTAlert has nothing to do with rig control - that's entirely in WSJT-X. You might want to post this in the WSJT-X group:

https://wsjtx.groups.io/g/main/topics 

73,

Mike - N8MSA


locked Re: Log Confirmation Popup Audio

ve7gtc
 

Thanks Laurie (and others).
For some reasdon as I mentioned I somehow skipped v.9 and didn't see the release notes. All good now.

Gus  K2GT


locked Re: Log Confirmation Popup Audio

Chuck Adams
 

In the latest version, it is NOW under JTAlert > Settings > Miscellaneous Alerts > Windows Notifications.  It was right there in the Release Notes like Laurie said if I just bothered to read them.  I am a damn idiot.

Sent from my T-Mobile 5G Device


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: Sunday, August 16, 2020 8:00:18 PM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] Log Confirmation Popup Audio
 
On 17/08/2020 8:48 am, ve7gtc wrote:
I have lost the log confirmation popup audio. It last worked for me in version.8. I do not have .9, but it does not work in .10, .11, or the current .12. Am I missing something?
Gus  K2GT

Try reading the release notes.

For your convenience ...
2.16.9 (18-Jul-2020)

  Changes:

    - Windows notification sounds: Used by some JTAlert popup messages, like logging
       success/failure, have been replaced with a dedicated sound file/volume
       selection. See the "Alerts -> Miscellaneous Alerts -> Windows Notifications"
       section of the Settings window.

de Laurie VK3AMA


locked Re: Log Confirmation Popup Audio

HamApps Support (VK3AMA)
 

On 17/08/2020 8:48 am, ve7gtc wrote:
I have lost the log confirmation popup audio. It last worked for me in version.8. I do not have .9, but it does not work in .10, .11, or the current .12. Am I missing something?
Gus  K2GT

Try reading the release notes.

For your convenience ...
2.16.9 (18-Jul-2020)

  Changes:

    - Windows notification sounds: Used by some JTAlert popup messages, like logging
       success/failure, have been replaced with a dedicated sound file/volume
       selection. See the "Alerts -> Miscellaneous Alerts -> Windows Notifications"
       section of the Settings window.

de Laurie VK3AMA


locked Re: Log Confirmation Popup Audio

Chuck Adams
 

On JTAlert > Settings > Manage Settings > Window > Pop-up Windows 

My latest version of JTAlert does NOT show ANY area to select "sounds for successful log and sounds for failure log."  The top portion of that window is blank.

I have not been able to find where to restore this lost functionality. 

I must be losing my mind.

Any suggestions?

Thanks and 73,

Chuck Adams
KV4VT 


Sent from my T-Mobile 5G Device



-------- Original message --------
From: Joseph Baker <joebaker324@...>
Date: 8/16/20 6:51 PM (GMT-05:00)
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Log Confirmation Popup Audio

Go to settings, window, pop up and select sounds for successful log and sound for failure log. 

On Sun, 16 Aug 2020 at 23:49, ve7gtc <ve7gtc@...> wrote:
I have lost the log confirmation popup audio. It last worked for me in version.8. I do not have .9, but it does not work in .10, .11, or the current .12. Am I missing something?
Gus  K2GT







--
Sent from iPhone 8 Plus


locked IC 7000 and Signal Link #FT8 - CAT Control fails #FT8

Angryconservative
 

Good evening....

I have ran WSJT-X and JT Alert from what seems the beginning.... Love the software.....  I run an IC 7000 with a west mountain plug and play due to the features, being it is compact and mobile as I have set it up as a Mobile EMCOMM system in a 1510 Pelican.  it is my primary digital unit for mobility..  I recently changed the West Mountain to a Signal Link for a couple of reasons...  I wanted to remove the dedication of the radio using the PC sound card and wanted to switch to a standard that all of my digital software assets.

The Problem is...as I configured each software package.... First FLDIGI, then Winlink...Cat control was very easy... and adjustments to power output to the platform was equally easy....

But with WSJT....all of it started out rather easy... RX/TX and PPT control etc...initially setting the Radio control to VOX as was required.  Once the Audio settings was set, FT8 was rolling... clean and easy.  Net step was to setup the CAT control... ICOM radio...  COM port the USB cable to the CAT control port on the back of the radio....  WSJT saw the com port, 8,2, none.  basically the same settings as the plug an play.... worked great for about two days...   I was on 40, the radio would try and click over the 20 meter without my input... CAT control stopped working, trying to change frequencies completely rendered my station unusable... Somehow the condition led to the dreaded error...*INI file not being found, HAMLIB error etc....I ended up having to reinstall WSJT-X and set the radio without CAT controls...it is working but without any CAT control...

But, FLDIGI and Winlink continue to work without any issue.  

I am running the latest version of WSJT-X 2.2.2 and JTALERT all drivers updated on Windows 10....

If anyone has any idea's as to why one day it works, then next it stops, it would be appreciated 


locked Re: Log Confirmation Popup Audio

Joseph Baker <joebaker324@...>
 

Go to settings, window, pop up and select sounds for successful log and sound for failure log. 

On Sun, 16 Aug 2020 at 23:49, ve7gtc <ve7gtc@...> wrote:
I have lost the log confirmation popup audio. It last worked for me in version.8. I do not have .9, but it does not work in .10, .11, or the current .12. Am I missing something?
Gus  K2GT







--
Sent from iPhone 8 Plus


locked Log Confirmation Popup Audio

ve7gtc
 

I have lost the log confirmation popup audio. It last worked for me in version.8. I do not have .9, but it does not work in .10, .11, or the current .12. Am I missing something?
Gus  K2GT


locked Three Screen Shot Examples of Seemingly Inconsistent Wanted Grid Alerts in JTAlert

Chuck Adams
 

Preliminary Disclaimer:  I am a BIG, BIG fan of JTAlert!  It makes using WSJT-X a JOY!  Bless you Laurie! 

My Current Computer Environment:  All latest versions and updates of:  Windows 10, WSJT-X, JTAlert.

Specific/Relevant JTAlert Setting:  Wanted Grid Tracking set to:  ANY BAND and ANY MODE

Issue Description:  JTAlert "seems" to give me incorrect NEW GRID ALERTS even on stations that have: 

  1. Been successfully worked and logged one or more times
  2. Show up in the WSJT-X log correctly
  3. Valid Grid Numbers in the WSJT-X logs for each QSO


Example 1:  N3MK has already been successfully worked and logged three (3) times.  It appears in the WSJT-X log correctly (including the Grid Square FM27 ).

Yet JTAlert shows N3MK as a NEW GRID with a B4 flag no less.

How can this be?






Example 2:  6E6E has been successfully worked and logged twice.  It appears in the WSJT-X log correctly (including the Grid Square EK09).

Yet JTAlert shows 6E6E as a NEW GRID 

How can this be?


Example 3:  Same scenario.  How can this be?



Am I missing something here?

This seems to be an inconsistent processing of Grid Square data and/or incorrect Wanted Grid Alerts.

HELP!

Thanks and 73,

Chuck Adams
KV4VT


locked Re: Version Numbers

Marlo Montanaro - KA2IRQ
 

Hi Laurie,

I figured it was something simple like that.  Carry on!

73,
Marlo- KA2IRQ


locked Re: Entity Naming Conventions

Barry Murrell ZS2EZ
 

Thanks Laurie – that will be brilliant!!

 

Between JTAlert and DXLabs (my logging suite of choice) the support is astonishing – add MicroHam into the mix and I am one very contented operator!!

 

73 de BARRY MURRELL ZS2EZ

KF26ta - Port Elizabeth, South Africa

EPC#0558 DMC#1690  30MDG#4081

DXCC HONOR ROLL (332/340)

website : www.zs2ez.co.za

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Sunday, 16 August 2020 01:28
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Entity Naming Conventions

 

On 14/08/2020 5:21 pm, Barry Murrell ZS2EZ wrote:

Hi Laurie

 

Having loaded the latest version of JTAlert I am now seeing the change to the name of South Africa – now Republic of South Africa.

 

Must say, I haven’t heard my home country referred to as “Republic of South Africa” in ages!!  J

 

This has however raised a conundrum : In JTAlert this just shows as “Rep. Of”…. Not distinguishable from the other 4 Republic Ofs (Korea, Kosovo, South Sudan and Congo). Kind of got used to F.R. meaning Germany, but at a glance both Kosovo and South Sudan start with a Z, which makes matters worse!!

 

As JTAlert only has a VERY small field to display the name (and to the best of my understanding does not actually transfer the name, but rather the DXCC entity number when logging), surely either a shorter (and more readable) option would make more sense…. Or alternatively a way to enlarge the blocks to enable the whole name to be read??

 

Sure, I know that we are supposed to know our prefixes… but some of us are getting a bit slower nowadays!!  J

 

73 de BARRY MURRELL ZS2EZ


Barry.

I changed the naming of "South Africa" to "Republic of South Africa" after a number of requests and some private email exchanges. Changing the name was not clear-cut, as different sources handle the name differently. From one of the email discussions I had on this...

"South Africa" is used by both the ADIF and ARRL and JTAlert has followed that lead, yet looking at DXKeeper, it lists "Republic of South Africa", who is right/wrong in this situation?

LOTW uses 

REPUBLIC OF SOUTH AFRICA


ClubLog uses REPUBLIC OF SOUTH AFRICA


The ARRL is not consistent, with LoTW providing a different naming from the official entities list provided on the ARRL website.

In making my final decision as to which name to go with, I looked to Wikipedia, which indicates that "Republic of South Africa" is the official name. So I went with that.

It looks to me like the ADIF standard and the ARRL are both out of date.

As for the country name field (often abbreviated or truncated) below the Callsign display of JTAlert, I have made some further changes to utilize the common names of some countries rather than trying to abbreviate the long name.
A sample of upcoming changes.

Republic of Korea -> South Korea
Republic of Kosovo -> Kosovo
Republic of South Africa -> South Africa
Republic of South Sudan -> South Sudan
Republic of the Congo -> The Congo


de Laurie VK3AMA


locked Re: Entity Naming Conventions

HamApps Support (VK3AMA)
 

On 16/08/2020 12:35 pm, Joe Subich, W4TV wrote:
This one is dangerous ... There are *TWO* countries called "Congo"
9Q - Democratic Republic of the Congo (Kinshasa)
TN - Republic of the Congo (Leopoldville)

73,

   ... Joe, W4TV
Tnx Joe,

I already had 9Q taken care of, its short name is "D.Rep. Congo"

de Laurie VK3AMA


locked Re: Entity Naming Conventions

Joe Subich, W4TV
 

Republic of the Congo -> The Congo
This one is dangerous ... There are *TWO* countries called "Congo"
9Q - Democratic Republic of the Congo (Kinshasa)
TN - Republic of the Congo (Leopoldville)

73,

... Joe, W4TV


On 2020-08-15 7:28 PM, HamApps Support (VK3AMA) wrote:
On 14/08/2020 5:21 pm, Barry Murrell ZS2EZ wrote:

Hi Laurie

Having loaded the latest version of JTAlert I am now seeing the change to the name of South Africa – now Republic of South Africa.

Must say, I haven’t heard my home country referred to as “Republic of South Africa” in ages!! J

This has however raised a conundrum : In JTAlert this just shows as “Rep. Of”…. Not distinguishable from the other 4 Republic Ofs (Korea, Kosovo, South Sudan and Congo). Kind of got used to F.R. meaning Germany, but at a glance both Kosovo and South Sudan start with a Z, which makes matters worse!!

As JTAlert only has a VERY small field to display the name (and to the best of my understanding does not actually transfer the name, but rather the DXCC entity number when logging), surely either a shorter (and more readable) option would make more sense…. Or alternatively a way to enlarge the blocks to enable the whole name to be read??

Sure, I know that we are supposed to know our prefixes… but some of us are getting a bit slower nowadays!! J

73 de BARRY MURRELL ZS2EZ
Barry.
I changed the naming of "South Africa" to "Republic of South Africa" after a number of requests and some private email exchanges. Changing the name was not clear-cut, as different sources handle the name differently. From one of the email discussions I had on this...
"South Africa" is used by both the ADIF and ARRL and JTAlert has followed that lead, yet looking at DXKeeper, it lists "Republic of South Africa", who is right/wrong in this situation?

LOTW uses
REPUBLIC OF SOUTH AFRICA


ClubLog uses REPUBLIC OF SOUTH AFRICA
The ARRL is not consistent, with LoTW providing a different naming from the official entities list provided on the ARRL website.
In making my final decision as to which name to go with, I looked to Wikipedia <https://en.wikipedia.org/wiki/South_Africa>, which indicates that "Republic of South Africa" is the official name. So I went with that.
It looks to me like the ADIF standard and the ARRL are both out of date.
As for the country name field (often abbreviated or truncated) below the Callsign display of JTAlert, I have made some further changes to utilize the common names of some countries rather than trying to abbreviate the long name.
A sample of upcoming changes.
Republic of Korea -> South Korea
Republic of Kosovo -> Kosovo
Republic of South Africa -> South Africa
Republic of South Sudan -> South Sudan
Republic of the Congo -> The Congo
de Laurie VK3AMA


locked Re: Version 2.16.12 Working Well

Mark Robinson
 

I don't know why the audio wasn't working......maybe because of my Win 7 OS.  I didn't see any other win 7 users mention it either.  I am using an HP Z400 PC.

73 Mark N1UK

On 15-Aug-20 7:09 PM, HamApps Support (VK3AMA) wrote:
On 16/08/2020 7:54 am, Mark Robinson wrote:
I just updated to version 2.16.12 and now my sound alerts are working perfectly and DXLab Suite Pathfinder is being updated as I start to work each new station


Great job   Many thanks

Mark N1UK

Mark,

Likely you were experiencing the rare defect first corrected in the 2.16.11 release. From the release notes...
  Fixes:
    - No audio output: Multiple JTAlert restarts required to get Alert sounds to play.

I say "rare defect" as it was never reproducible in my testing, none of the 30 strong Test team experienced the problem and there were minimal public reports of an audio defect.

Thanks for reporting audio is now working for you.

de Laurie VK3AMA




locked Re: Entity Naming Conventions

HamApps Support (VK3AMA)
 

On 14/08/2020 5:21 pm, Barry Murrell ZS2EZ wrote:

Hi Laurie

 

Having loaded the latest version of JTAlert I am now seeing the change to the name of South Africa – now Republic of South Africa.

 

Must say, I haven’t heard my home country referred to as “Republic of South Africa” in ages!!  J

 

This has however raised a conundrum : In JTAlert this just shows as “Rep. Of”…. Not distinguishable from the other 4 Republic Ofs (Korea, Kosovo, South Sudan and Congo). Kind of got used to F.R. meaning Germany, but at a glance both Kosovo and South Sudan start with a Z, which makes matters worse!!

 

As JTAlert only has a VERY small field to display the name (and to the best of my understanding does not actually transfer the name, but rather the DXCC entity number when logging), surely either a shorter (and more readable) option would make more sense…. Or alternatively a way to enlarge the blocks to enable the whole name to be read??

 

Sure, I know that we are supposed to know our prefixes… but some of us are getting a bit slower nowadays!!  J

 

73 de BARRY MURRELL ZS2EZ


Barry.

I changed the naming of "South Africa" to "Republic of South Africa" after a number of requests and some private email exchanges. Changing the name was not clear-cut, as different sources handle the name differently. From one of the email discussions I had on this...
"South Africa" is used by both the ADIF and ARRL and JTAlert has followed that lead, yet looking at DXKeeper, it lists "Republic of South Africa", who is right/wrong in this situation?

LOTW uses 
REPUBLIC OF SOUTH AFRICA

ClubLog uses REPUBLIC OF SOUTH AFRICA


The ARRL is not consistent, with LoTW providing a different naming from the official entities list provided on the ARRL website.

In making my final decision as to which name to go with, I looked to Wikipedia, which indicates that "Republic of South Africa" is the official name. So I went with that.

It looks to me like the ADIF standard and the ARRL are both out of date.

As for the country name
field (often abbreviated or truncated) below the Callsign display of JTAlert, I have made some further changes to utilize the common names of some countries rather than trying to abbreviate the long name.
A sample of upcoming changes.
Republic of Korea -> South Korea
Republic of Kosovo -> Kosovo
Republic of South Africa -> South Africa
Republic of South Sudan -> South Sudan
Republic of the Congo -> The Congo

de Laurie VK3AMA



locked Re: Version 2.16.12 Working Well

HamApps Support (VK3AMA)
 

On 16/08/2020 7:54 am, Mark Robinson wrote:
I just updated to version 2.16.12 and now my sound alerts are working perfectly and DXLab Suite Pathfinder is being updated as I start to work each new station


Great job   Many thanks

Mark N1UK

Mark,

Likely you were experiencing the rare defect first corrected in the 2.16.11 release. From the release notes...
  Fixes:
    - No audio output: Multiple JTAlert restarts required to get Alert sounds to play.

I say "rare defect" as it was never reproducible in my testing, none of the 30 strong Test team experienced the problem and there were minimal public reports of an audio defect.

Thanks for reporting audio is now working for you.

de Laurie VK3AMA



locked Re: Version Numbers

HamApps Support (VK3AMA)
 

On 15/08/2020 4:53 am, Marlo Montanaro - KA2IRQ wrote:

I just installed 2.16.12 but my Decodes window still says 2.16.11.  Win10.  Everything seems to be working fine.

73,

Marlo- KA2IRQ


Mario,

That was an oversight on my part. 2.16.12 was a fast tracked rebuild of 2.16.11 to fix a critical defect. A single line of code in the main JTAlert program was removed with no changes to the Decodes window. I neglected to recompile the Decodes window executable before packaging the new release..

de Laurie VK3AMA


locked Version 2.16.12 Working Well

Mark Robinson
 

I just updated to version 2.16.12 and now my sound alerts are working perfectly and DXLab Suite Pathfinder is being updated as I start to work each new station


Great job   Many thanks

Mark N1UK


locked Re: Version 2.16.11 Multicast and Multiple Instances

Santiago Mejia
 


This issue was solved. Everything is working fine with Wsjtx, JTAlert and Gridtracker. The issue of Lookup Window only working with 1st instance is a GT issue and Tag will be looking at it in future releases. 

Today's fixed of UDP Rebroadcast has allowed me to also incorporate FRLogger (A logger for Flex Radios) into the mix. No I can have Wsjtx (3 instances), JTAlert (3 instancies), GridTracker, Log4Om and FRLogger running at the same time.

Thanks Laurie.

Santiago
______________
73 de Santiago
HI8SMX
web: www.hi8smx.online 
YouTube: HI8SMX 
Twitter: @hi8smx
Instagram: hi8smx


locked Re: Version Numbers

 

Marlo,

Me too.  Didn’t actually check the version number till I saw you post.  I just re-downloaded and reinstalled and it now reads 2.16.12.

 

__________

Dan – K4SHQ

CFI/II

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Marlo Montanaro - KA2IRQ
Sent: Friday, August 14, 2020 1:54 PM
To: Support@HamApps.groups.io
Subject: [HamApps] Version Numbers

 

I just installed 2.16.12 but my Decodes window still says 2.16.11.  Win10.  Everything seems to be working fine.

73,

Marlo- KA2IRQ


--
Dan - K4SHQ

4321 - 4340 of 35475