Date   

locked Re: JTAlert 2.16.3 build 0002 #HRD

Ham Radio
 

Thank you Laurie for the info.  RTFM, oh dear!

Now need to figure why some fields such as Name are not being updated by HRD when logging QSO. Same problem as PC1Y.


--
73, Bernie, VE3FWF


locked Re: DX and /MM

Andy k3wyc
 

I realized I did not have latest version.  After update from 2.15.7 to 2.16.3 I no longer hear "DX" for /MM.   

73,
Andy, k3wyc


locked Re: JTAlert 2.16.3 build 0002 #HRD

peter nn
 

Laurie,
ave also the HD .269 and Jtalert .2.16.3 build 2 working together ok........


Only notices that the propagation details are now not transferred into HRD  .... don't know if it is in hrd or jtalert   as i both have upgraded.....last seen 1 april...

Any clue,  73 Peter PC1Y


locked DX and /MM

Andy k3wyc
 

There are several maritime mobile stations active on 40 m and some of the call signs are those of DX I have not worked on 40 m.  JTAlert calls "DX" each time one of these /MM stations is decoded but these stations are not valid for DXCC credit.

Does JTAlert have any option for special handling of /MM callsigns so they are not identified as "DX"?

Thanks and 73,
Andy, k3wyc


locked Re: v2.16.3 TEXT QSO LOGGED

HamApps Support (VK3AMA)
 

On 4/04/2020 2:43 pm, Bob Elliot wrote:
Just loaded v2.16.3 to a clean install meaning all previous files removed.  Setup all my preferences.  Ran some tests and works faster and this is a great update.  One thing it does when logging the qso it sends a text to the logged station saying the qso was logged. Not sure if I like this or not.  Looked through the settings for the option to dis able this feature.

Has anyone found how to turn this notification off/on other than disabling the text?
--
73 Bob K1RI

This does not exist in JTAlert and there are no plans to create such an intrusive feature.

How are you determining that the logged station is receiving a text message from you?

de Laurie VK3AMA


locked v2.16.3 TEXT QSO LOGGED

Bob Elliot
 

Just loaded v2.16.3 to a clean install meaning all previous files removed.  Setup all my preferences.  Ran some tests and works faster and this is a great update.  One thing it does when logging the qso it sends a text to the logged station saying the qso was logged. Not sure if I like this or not.  Looked through the settings for the option to dis able this feature.

Has anyone found how to turn this notification off/on other than disabling the text?
--
73 Bob K1RI
Sent from my Rotary Phone


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

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


locked Re: JTAlert 2.16.3 build 0002 #HRD

Gavin Bennett
 
Edited

Hi Laurie

 

Must have disappeared into the ether, I replied to your locked post.

 

They have introduced a number of issues for third party apps! Note second para, this from Mike at HRD

 

Regards

 

 

Gavin

ZL3GAV

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, 4 April 2020 15:44
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.16.3 build 0002 #HRD

 

On 4/04/2020 1:15 pm, Gavin Bennett wrote:


Experiencing same issue, have reported to Laurie. My response is in moderation as I replied to his locked message.

73

Gavin, ZL3GAV

I don't see any waiting moderation message from you.

This issue is easily resolved by telling JTAlert it needs to log ADIF 3.1.0 compliant FT4 now that your HRD log has been made compliant.

see https://hamapps.groups.io/g/Support/message/28940

de Laurie VK3AMA

 


locked Re: JTAlert 2.16.3 build 0002 #HRD

HamApps Support (VK3AMA)
 

On 4/04/2020 1:38 pm, Ham Radio wrote:
It looks like a Mode mapping issue in JTAlert.  Laurie, if you need a trace log, please let me know.
--
73, Bernie, VE3FWF
No need.

I have already provided the answer here
https://hamapps.groups.io/g/Support/message/28940

de Laurie VK3AMA


locked Re: JTAlert 2.16.3 build 0002 #HRD

HamApps Support (VK3AMA)
 

On 4/04/2020 1:15 pm, Gavin Bennett wrote:

Experiencing same issue, have reported to Laurie. My response is in moderation as I replied to his locked message.

73

Gavin, ZL3GAV
I don't see any waiting moderation message from you.

This issue is easily resolved by telling JTAlert it needs to log ADIF 3.1.0 compliant FT4 now that your HRD log has been made compliant.

see https://hamapps.groups.io/g/Support/message/28940

de Laurie VK3AMA


locked Re: JTAlert 2.16.3 build 0002 #HRD

HamApps Support (VK3AMA)
 

On 4/04/2020 12:59 pm, Ham Radio wrote:
I am having a configuration issue with WSJT-X v2.1.2, JTAlert 2.16.3.beta 002 and HRD 6.7.0.269 logging FT4.

WSJT-X logs directly into HRD with no problem with the correct Mode (MFSK) and Submode  (FT4) in HRD

WSJT-X along with JTAlert running at the same time results Mode being FT4 and Submode being blank when logging the FT4 contact. The alert box indicates Mode being FT4.

I am using UDP port 2237 in WSJT-X and HRD. I have the correct check box set in JTAlert for HRD 6.7.0.269

I am doing something wrong here but no idea what is wrong.


--
73, Bernie, VE3FWF

If JTAlert is logging as Mode=FT4, then you have not followed all the instructions provided by HRD when they first released 6.7.0.269 and you needed to update your log.

You have changed your HRD log to be ADIF 3.1.0 compliant when logging FT4 QSOs but have failed to tell JTAlert to log the QSOs as such.

You need to enable the "Log FT4 as ADIF 3.1.0..." setting in JTAlert, Logging section, scroll down to the bottom.

   

Any FT4 mode QSOs already logged you will need to manually modify to MODE=MFSK, SUBMODE=FT4

de Laurie VK3AMA


locked Re: JTAlert 2.16.3 build 0002 #HRD

Ham Radio
 

It looks like a Mode mapping issue in JTAlert.  Laurie, if you need a trace log, please let me know.
--
73, Bernie, VE3FWF


locked Re: JTAlert 2.16.3 build 0002 #HRD

Monty Wilson
 

It sounds like you are set up to send logs from both WSJT-X and JTALERT to HRD.  You need to turn one of them off.  If you using WSJT-X to send your contacts to HRD logging, then you do not need to the beta version of JTALERT since his fix was for those that use JTALERT for logging.

 

Monty, NR0A

Jwilson16@...

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Ham Radio
Sent: Friday, April 3, 2020 09:00 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.16.3 build 0002 #HRD

 

I am having a configuration issue with WSJT-X v2.1.2, JTAlert 2.16.3.beta 002 and HRD 6.7.0.269 logging FT4.

WSJT-X logs directly into HRD with no problem with the correct Mode (MFSK) and Submode  (FT4) in HRD

WSJT-X along with JTAlert running at the same time results Mode being FT4 and Submode being blank when logging the FT4 contact. The alert box indicates Mode being FT4.

I am using UDP port 2237 in WSJT-X and HRD. I have the correct check box set in JTAlert for HRD 6.7.0.269

I am doing something wrong here but no idea what is wrong.


--
73, Bernie, VE3FWF


locked Re: JTAlert 2.16.3 build 0002 #HRD

Gavin Bennett
 

Hi Bernie

Experiencing same issue, have reported to Laurie. My response is in moderation as I replied to his locked message.

73

Gavin, ZL3GAV


locked Re: JTAlert 2.16.3 build 0002 #HRD

Ham Radio
 

I am having a configuration issue with WSJT-X v2.1.2, JTAlert 2.16.3.beta 002 and HRD 6.7.0.269 logging FT4.

WSJT-X logs directly into HRD with no problem with the correct Mode (MFSK) and Submode  (FT4) in HRD

WSJT-X along with JTAlert running at the same time results Mode being FT4 and Submode being blank when logging the FT4 contact. The alert box indicates Mode being FT4.

I am using UDP port 2237 in WSJT-X and HRD. I have the correct check box set in JTAlert for HRD 6.7.0.269

I am doing something wrong here but no idea what is wrong.


--
73, Bernie, VE3FWF


locked Re: Duplicate logging?

Monty Wilson
 

If you are using HRD, you will need to go into HRD Tool > Configure > QSO Forwarding and uncheck the UDP Receive.

 

I recently changed from WSJT-X feed of my HRD lot to JTALERT and had the same thing until I unchecked the QSO Forwarding boxes.

 

Cheers

Monty, NR0A

Jwilson16@...

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Neil
Sent: Friday, April 3, 2020 04:05 PM
To: Support@HamApps.groups.io
Subject: [HamApps] Duplicate logging?

 

I noticed that if I enable in settings to enable HRD logging I have two entries of the same QSO. I have unticked HRD 6.3 logging in JT Alert and have only the one contact logging in. I wonder why this is? Not a major problem I just want to understand why, and I want to utilize the full potential of JT Alert which IMO is a great piece of work.
Neil   N4FN


locked Re: Windows Defender indicating that version 2.16.3 has PUA.Win32.Presenoler virus

Kyle K7KE
 

Suggestion:Take a look at AVG's privacy policy and what they do with your data.
--
--Kyle--  K7KE


locked Re: Loss of Audio on release 2.16.3

Gary Randall
 

I did reselect the correct speaker.  Did not work.
I uninstalled 2.16.1 and then installed 2.16.3 and it seems
to work for today anyway.
Gary


locked Re: Windows Defender indicating that version 2.16.3 has PUA.Win32.Presenoler virus

m_scot_alex
 

It is the user's fault when they don't even try to understand how AV software works. This isn't a "2020" issue - AV heuristics have been throwing generic warnings on unsigned code for over half of a decade or more and this shouldn't be a surprise to digital-mode operators as PCs are, especially on PC-dependent modes, just a much a part of the system as the antenna or transceiver. 

I get it - a lot of people read these kinds of posts and dismiss them or think that they're an attack, and they're nothing of the sort. What I, and several others, write on a routine basis are attempts to get people to understand that AV software alerts require the same nuanced interpretation that an "check engine" warning lamp does on a car and that the information needed to make an informed decision is typically one Google search away. It's rather unfair to Laurie for people, on a daily basis, to ignore the FAQ stickies and all of the previous posts on this topic to complain and/or seek assurance about a problem that is easily understood and has been solved countless times.

Mike - N8MSA



On Fri, Apr 3, 2020 at 01:10 PM, Michael Coslo wrote:


I would suggest that we don’t act like it is the user's fault if our AV software tells us that a program is malware though. It takes a conscious effort to ignore years of conditioning.

- 73 -
- Michael Coslo -
Frequency Coordinator, Beaver Stadium
814-404-3991
mjc5@...
mjcn3li@...

On Apr 3, 2020, at 11:02 AM, Jim Kajder AF5FH <jkajder@...> wrote:

In my experience you don't have to spend money on a Windows 10 antivirus program. AVG AntiVirus Free version is on my shack computer and does not block WSJT-X, JT-Alert, or DXKeeper.

73, Jim, AF5FH


locked Re: JTALERT Text is not working with TCP error

WB8ASI Herb
 

I just tried it, and got the same thing. Herb WB8ASI

On April 3, 2020 at 7:43 PM "Komkit Listisard via groups.io" <w3kit@...> wrote:

Today I noticed my text msg was not working, I do not see anyone with the line under their callsigns.  And everyone seem to be OFFLINE to me.  I called a friend of mine, he noticed the same.

Looking around the settings under TCP/IP Network Ports, I see the following error.  Was it something on my end?  I tried different ports, all failed the same.

TCP Port (for Text Messages) TCP Connect FAIL : Error=10060 when I run the "test"



73, Kit W3KIT

 

4061 - 4080 of 32849