Date   

locked Worked B4 Issue

Brian Kassel K7RE
 

I just upgraded to 2.16.3, but my B4 function does not seem to be able to scan
my ADIF log.  All stations logged since the upgrade do indeed display that
they were worked B4, if they were worked after the upgrade.
No stations that I know that I had worked before on the same band/mode
show up as worked B4.

I understand that the B4 DB gets it data from the ADIF file (in my case).
I also understand that scanning the log  does not apply in this case.

I am a bit bewildered by the log paths displayed below:

Correct path to my ADIF Log:
C:\users\brian\desktop\FT8 Log Spearfish.adi

in F11 (manage settings):
Logging
Log B4 Database

C:\users\brian\appdata\local\HamApps\K7RE\Logs\JTAlertX\B4logV2.mdb




in F11 (manage settings):
Logging
Standard ADIF File

in Red:

C:\users\brian\appdata\local\WSJT-X\wsjtx_log.adi

Can some one steer me in the right direction please?



--

Brian K7RE


locked JTAlert 2.16.4 is available - HRD FT4 Fix. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.16.4 is now available @ https://hamapps.com/JTAlert/

This is the official public release which has the HRD 6.7.0.269 FT4 compatibility fixes of the 2.6.3 build 0002 beta.

Users of the beta need to upgrade to this version asap. All JTAlert beta release have an inbuilt 4 week expiry date after which the software becomes non-functional.

The instructions provided here on correct JTAlert settings to work with HRD 6.7.0.269 are still correct except for the published beta download link which has now been removed. The JTAlert Help file also has these instructions.

de Laurie VK3AMA

Release Notes.

2.16.4 (06-APR-2020)

  Fixes:

    - HRD 6.7.0.269: All JTAlert FT4 functionality broken, B4 checks, Logging
       confirmations, Log scanning and Callsign QSO History when run against
       HRD 6.7.0.269 with an updated adif 3.1 compliant log.
       See JTAlert help file, "HRD 6.7.0.269, JTAlert settings" topic.


locked Re: Scan Log not picking up FT4 confirmed QSOs

jushamn@...
 

Ok this is embarrassing. I was so sure that I had the path to the adif log correct that I fail to check it carefully. I was saving the log exported from LOGic to ALMOST the right directory (a few letters difference). I have now gone to using JTAlert's default directory for adif and it all works. Lesson learned, sometimes it doesn't pay to be creative.

Thanks Laurie for the info on the change in the adif spec concerning Canadian Provinces and especially for being patient with my foolishness.


locked Solution: Cannot locate last used sound card device

Lee W4EIS
 

I know Laurie said to look in the help section for a solution to this startup issue.  I cannot pinpoint the exact date this started showing up and I really don't want to have to go back and delete setting files and then having to reset from scratch. ...with so many different setting options to choose between.  Wondering again if anyone has happened to find out what the specific problem was & ' or how to fix without starting from scratch.

73  Lee
W4EIS


locked Thank you Laurie for doing a super job.

Ham Radio
 

Your patience and expertise is noted and appreciated.

At this point in time,  we hams have the benefit of a great hobby with great tools.

Be safe and healthy!
--
73, Bernie, VE3FWF


locked Re: JTALERT Text is not working with TCP error

Komkit Listisard
 

Got up this morning everything is back to normal.  Text msg once again is working.  Not more TCP/IP port error.

73, Kit W3KIT


locked Re: Ver. 2.16.0 Virus Detected at Download

Rich Holst
 

I keep having issues with Defender running, even after I mark the installer as safe. Sometimes with JTAlert running, it identifies the program as malicious and kills it!

I do not know what the process is for a developer to get their programs whitelisted and I'm sure it is tedious, but this nonsense where I need to fight toe built-in A/V to allow the program is very frustrating and also unsettling.

Rich Holst
K2RH


locked Re: JTALERT Text is not working with TCP error

Willi Passmann
 

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

I did the tests available under Web Services -> TCP/IP Network Ports and
all show "OK".

vy 73,
Willi, DJ6JZ

Am 04.04.2020 um 01:43 schrieb Komkit Listisard via groups.io:

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



locked Re: v2.16.3 TEXT QSO LOGGED

Bob Elliot
 

My bad.  It is not a text but a notice I logged the qso.
--
73 Bob K1RI
Sent from my Rotary Phone


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