I just got a text message from an OM who is displayed as "Offline".
So the offline indicator seems to be unreliable.

Could anyone tell me or have a formula on how US calls are also recognized with the respective state and CQzone in JTalert?

Is there a specific form of the call to understand how they are recognized, or is a database callsign?

For example, I heard KH6M this afternoon and thought it was Hawaii, instead it turns out to be FL. ;-)

sry, I hadn't turned on JTalert to check if he was giving it to me.

Thanks, 73s
Franco
http://www.qrz.com/db/hb9oab

John,

I believe its a setting in HRD Log.   Make sure that its not setup to 'listen' for the UDP broadcasts.  Can't tell you where to look, but having this on is the number one cause of duplicate entries.

Neil, KN3ILZ

When operating in FT8, if I work DX stations, all works as it should except logging. The completed QSO logs twice with some of the information missing from each logged QSO in HRD. (Screen shot below)
If I work a US station, as soon as the call is entered and posted in JT Alert, JT Alert locks up...the rolling donut. I have to close and re-opon it. When the QSO finishes it asks if I want to log the QSO, it logs it to the WSJT-X ADI file but not to HRD.

I suspect I have something wrong in the setting of JT-Alert or WSJT-X (or possibly even HRD)? This setup has worked for me for many years and this is a recent problem. I hope someone can offer me the solution or at least some thing that I can try.

 

Danny, W0JMP

Hi Can someone please tell me what this symbol means? I have latest version JTAlert. Please see picture included. 73 Mike VK3XZ

I have searched through the files and have not been able to find the answer to my specific problem. Here is my set-up:

-HRD 6.7.0.275
-JT Alert 2.16.4
-WSJT-X 2.1.2
-Windows 10  64 bit OS
-Intel Core i7-6700 CPU @ 3.4 GHz 
When operating in FT8, if I work DX stations, all works as it should except logging. The completed QSO logs twice with some of the information missing from each logged QSO in HRD. (Screen shot below)
If I work a US station, as soon as the call is entered and posted in JT Alert, JT Alert locks up...the rolling donut. I have to close and re-opon it. When the QSO finishes it asks if I want to log the QSO, it logs it to the WSJT-X ADI file but not to HRD.

I suspect I have something wrong in the setting of JT-Alert or WSJT-X (or possibly even HRD)? This setup has worked for me for many years and this is a recent problem. I hope someone can offer me the solution or at least some thing that I can try.

Danny, W0JMP

I have gone to the trouble or uninstalling alert completely..  I even spent 2 hours and 40 minutes going through the registry and removed every single reference to alert that could be found...  I then reinstalled, and still TXT does not work. 

 In addition, I have a few friends that use alert and for what its worth, not one single callsign that appears in the decode window has the Underline on it to show that the call  has TXT messages enabled, even when it is known that they do have it on.   

I miss this feature greatly..  It is (or was for me) a fabulous feature and I wish that I could get it going again.    Funny thing, I have tried ALL of the ports that are available in settings for Text Messages , and all of them say "TCP Connect OK" - I am at a loss as to what to do now to get this great feature working again..... Has Anyone got and Ideas ???

regards

John

If you have uninstalled JTAlert completely, than the likely cause is that you have not enabled receiving of test messages from other users. It is off by default. With the TCP check returning OK, that is further evidence that you don't have text messages enabled.

If receiving of text messages is turned off, than you will never see the underline indicator as your copy of JTAlert is never checking the server to see if decoded callsigns are online. If JTAlert is not checking the Server because of the turned off state than your callsign is never register as being online so other users will never see an underline for your callsign.

   

I see that there are now several people having TXT message problems.   

Around about 8 or 9 versions ago, my TXT message capability ceased to work.   The only way I could send or receive messages was to revert to an earlier version of Alert and now that all support for earlier versions has been removed, they also no longer work.

I have gone to the trouble or uninstalling alert completely..  I even spent 2 hours and 40 minutes going through the registry and removed every single reference to alert that could be found...  I then reinstalled, and still TXT does not work. 

 In addition, I have a few friends that use alert and for what its worth, not one single callsign that appears in the decode window has the Underline on it to show that the call  has TXT messages enabled, even when it is known that they do have it on.   

I miss this feature greatly..  It is (or was for me) a fabulous feature and I wish that I could get it going again.    Funny thing, I have tried ALL of the ports that are available in settings for Text Messages , and all of them say "TCP Connect OK" - I am at a loss as to what to do now to get this great feature working again..... Has Anyone got and Ideas ???

regards

John

After completing a qso, an error
comes up saying the date range is not
within the set date of the tqsl
cert.  After checking it, it is.
Please advise how to fix so I can
continue to get them uploaded to
lotw. This started after I updated
the programs.

John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com