Date   

locked Re: New HRD Release v6.7.0.269 Confusion

Joe Subich, W4TV
 

Could not find the "Log FT4 as ADIF 3.1.0 Compliant" to check.
Scroll *all the way to the bottom of "Logging Options".

73,

... Joe, W4TV


On 2020-04-01 3:21 PM, Bob Davet wrote:
Been Reading this thread.
Upgraded HRD this AM. Made the changes in the logbook.
Could not find the "Log FT4 as ADIF 3.1.0 Compliant" to check. Sent support ticket to HRD. They said it is an issue with  JTAlert and I should upgrade to the latest version.
I didn't have the heart to tell them I already did before I upgraded HRD.
The box is still not there to check.
Read this thread and made a FT4 contact. When it posted it only posted under mode "FT4". Nothing in the submode column.
The other FT4 contacts have the "MFSK" under mode and "FT4 under submode.
So, Who is right here? HRD or JTAlert?
Not trying to pick a fight, just want to have my data correct.
Am I going to have to check my log every month and convert my FT4 contacts to MSFK/FT4??
Bob
W8RID


locked Re: Hamspots

Martin Blaise
 

I just downloaded the newest version of jt alert. will see if it works


On Wed, Apr 1, 2020 at 2:23 PM Martin Blaise via groups.io <martingblaise=gmail.com@groups.io> wrote:
See graphic. I had all three fails. Maybe I have the wrong port settings??

On Wed, Apr 1, 2020 at 2:15 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Actually it's simpler than that...you should be able to just click on the menu item...Manage Settings is the 3rd entry from the bottom of this menu.


Inline image


de Mike W9MDB



On Wednesday, April 1, 2020, 02:09:12 PM CDT, Martin Blaise <martingblaise@...> wrote:


I don't see anything for manage settings. See graphic. Thanks.

On Wed, Apr 1, 2020 at 12:44 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Settings/Manage Settings/Web Services -- Enable the Hamspots.net checkbox.

de Mike W9MDB




On Wednesday, April 1, 2020, 09:15:58 AM CDT, Martin Blaise <martingblaise@...> wrote:


On hamspots I see my call spotted but the section calls I spotted is blank, can someone help me fix this?


locked Re: New HRD Release v6.7.0.269 Confusion

Michael Black
 

You have to scroll down the Logging settings window to get to it...


Inline image

de Mike W9MDB




On Wednesday, April 1, 2020, 02:21:55 PM CDT, Bob Davet <davet354tfd@...> wrote:


Been Reading this thread.

Upgraded HRD this AM. Made the changes in the logbook.

Could not find the "Log FT4 as ADIF 3.1.0 Compliant" to check. Sent support ticket to HRD. They said it is an issue with  JTAlert and I should upgrade to the latest version.
I didn't have the heart to tell them I already did before I upgraded HRD.
The box is still not there to check.
Read this thread and made a FT4 contact. When it posted it only posted under mode "FT4". Nothing in the submode column.
The other FT4 contacts have the "MFSK" under mode and "FT4 under submode.

So, Who is right here? HRD or JTAlert?
Not trying to pick a fight, just want to have my data correct.
Am I going to have to check my log every month and convert my FT4 contacts to MSFK/FT4??

Bob
W8RID


locked Re: Hamspots

Michael Black
 

Sounds like your firewall is blocking it....

Mike




On Wednesday, April 1, 2020, 02:23:10 PM CDT, Martin Blaise <martingblaise@...> wrote:


See graphic. I had all three fails. Maybe I have the wrong port settings??

On Wed, Apr 1, 2020 at 2:15 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Actually it's simpler than that...you should be able to just click on the menu item...Manage Settings is the 3rd entry from the bottom of this menu.


Inline image


de Mike W9MDB



On Wednesday, April 1, 2020, 02:09:12 PM CDT, Martin Blaise <martingblaise@...> wrote:


I don't see anything for manage settings. See graphic. Thanks.

On Wed, Apr 1, 2020 at 12:44 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Settings/Manage Settings/Web Services -- Enable the Hamspots.net checkbox.

de Mike W9MDB




On Wednesday, April 1, 2020, 09:15:58 AM CDT, Martin Blaise <martingblaise@...> wrote:


On hamspots I see my call spotted but the section calls I spotted is blank, can someone help me fix this?


locked Re: Hamspots

Martin Blaise
 

See graphic. I had all three fails. Maybe I have the wrong port settings??

On Wed, Apr 1, 2020 at 2:15 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Actually it's simpler than that...you should be able to just click on the menu item...Manage Settings is the 3rd entry from the bottom of this menu.


Inline image


de Mike W9MDB



On Wednesday, April 1, 2020, 02:09:12 PM CDT, Martin Blaise <martingblaise@...> wrote:


I don't see anything for manage settings. See graphic. Thanks.

On Wed, Apr 1, 2020 at 12:44 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Settings/Manage Settings/Web Services -- Enable the Hamspots.net checkbox.

de Mike W9MDB




On Wednesday, April 1, 2020, 09:15:58 AM CDT, Martin Blaise <martingblaise@...> wrote:


On hamspots I see my call spotted but the section calls I spotted is blank, can someone help me fix this?


locked Re: New HRD Release v6.7.0.269 Confusion

Bob Davet
 

Been Reading this thread.

Upgraded HRD this AM. Made the changes in the logbook.

Could not find the "Log FT4 as ADIF 3.1.0 Compliant" to check. Sent support ticket to HRD. They said it is an issue with  JTAlert and I should upgrade to the latest version.
I didn't have the heart to tell them I already did before I upgraded HRD.
The box is still not there to check.
Read this thread and made a FT4 contact. When it posted it only posted under mode "FT4". Nothing in the submode column.
The other FT4 contacts have the "MFSK" under mode and "FT4 under submode.

So, Who is right here? HRD or JTAlert?
Not trying to pick a fight, just want to have my data correct.
Am I going to have to check my log every month and convert my FT4 contacts to MSFK/FT4??

Bob
W8RID


locked Re: Hamspots

Michael Black
 

Actually it's simpler than that...you should be able to just click on the menu item...Manage Settings is the 3rd entry from the bottom of this menu.


Inline image


de Mike W9MDB



On Wednesday, April 1, 2020, 02:09:12 PM CDT, Martin Blaise <martingblaise@...> wrote:


I don't see anything for manage settings. See graphic. Thanks.

On Wed, Apr 1, 2020 at 12:44 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Settings/Manage Settings/Web Services -- Enable the Hamspots.net checkbox.

de Mike W9MDB




On Wednesday, April 1, 2020, 09:15:58 AM CDT, Martin Blaise <martingblaise@...> wrote:


On hamspots I see my call spotted but the section calls I spotted is blank, can someone help me fix this?


locked Re: Hamspots

Martin Blaise
 

I don't see anything for manage settings. See graphic. Thanks.

On Wed, Apr 1, 2020 at 12:44 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Settings/Manage Settings/Web Services -- Enable the Hamspots.net checkbox.

de Mike W9MDB




On Wednesday, April 1, 2020, 09:15:58 AM CDT, Martin Blaise <martingblaise@...> wrote:


On hamspots I see my call spotted but the section calls I spotted is blank, can someone help me fix this?


locked Re: New HRD Release v6.7.0.269 Confusion

Monty Wilson, NR0A
 

I upgraded to the new version of HRD this morning and made the changes recommended in the video on the HRD website. Now when I use FT4 mode (logging is via JTAlert) the FT4 QSO shows up in my HRD log with the mode and submode as MSFK and FT4, but I get the following message:

FAILURE : QSO Not logged!

ERROR Message : HRD : Unable to confirm QSO logged

Callsign : KS4OT
Frequency : 14.081998 MHz
Logged Mode : FT4

This Error is due to a long-standing defect within HRDLogbook where the HRD TCP logging command fails to write the QSO to the log. This affects non-Access logs only.

This message has been placed in the Windows clipboard.

HRD TCP Logging command result returned =>
Ham Radio Deluxe Version RELEASE 6.7.0.269
[c] Found 36 Valid Fields...
Added 50 Fields to My Logbook...
[c] [c]

I am not sure what this is telling me. HRD has been changed to correctly log FT4 contacts as MODE = MFSK and SUBMODE = FT4. I also change the settings in JTALERT to Lot FT4 as ADIF 3.1.0 compliant Mode-MFKS, SUBMODE=FT4

If in fact HRD is now setting the fields correct, why am I getting an FAILURE message?

Cheers

Monty Wilson, NR0A
Jwilson16@cableone.net

-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of g4wjs
Sent: Wednesday, April 1, 2020 01:19 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] New HRD Release v6.7.0.269 Confusion

On 01/04/2020 18:46, August Treubig wrote:
LOTW and HRD were not really working. The QSOS were not actually
logged as FT4.

As for the MFSK mode and FT4 sub mode. That is what the ADIF Gods
proclaimed. So you must follow.

The Video is very clear on how to clean up your log. and re-submit.

But alas, there is also now an issue between JTAlert and HRD. So we
will have to see who has to sort that issue out for FT4.

Aug
AG5AT
Aug and all,

the ADIF specification requires MODE=MFSK + SUBMODE=FT4, but what most talking about this fail to understand is that ADIF is a specification for passing QSO data between applications. The applications themselves can store QSO mode anyway they feel fit, what is most important is that they export FT4 mode QSOs in the correct ADIF format. Along with that applications can, and probably should, be flexible in what they accept when importing ADIF records. For example an application could easily accept just MODE=FT4 as a valid FT4 QSO mode. The problem with HRD all along has been that it failed to accept valid ADIF records with MODE=MFSK and SUBMODE=FT4 as records of QSOs made using the FT4 mode, so it was neither correct nor flexible.



--
73
Bill
G4WJS.


locked Re: Unable to install JTAlert updates

neil_zampella
 

What is the exact error you're seeing?    Is it when downloading?  When running the installer?

More data is needed.

 

Neil, KN3iLZ


locked Re: New HRD Release v6.7.0.269 Confusion

Joe Subich, W4TV
 

On 2020-04-01 1:46 PM, August Treubig wrote:
But alas, there is also now an issue between JTAlert and HRD.
There is absolutely no "issue between JTAlert and HRD".

If HRD is now ADIF 3.1.0 compliant and accepts MODE=MFSK SUBMODe=JT4,
it is only necessary to open the Settings dialog in JTAlert, select
"Logging", scroll to the bottom of the "Logging Options" and check
"Log FT4 as ADIF 3.1.0 compliant MODE=MFSK, SUBMODE=FT4"

Laurie has had that option in place since FT4 was standardized by
ADIF.ORG.

73,

... Joe, W4TV


On 2020-04-01 1:46 PM, August Treubig wrote:
LOTW and HRD were not really working.  The QSOS were not actually logged as FT4.
As for the MFSK mode and FT4 sub mode.  That is what the ADIF Gods proclaimed.  So you must follow.
The Video is very clear on how to clean up your log. and re-submit.
But alas, there is also now an issue between JTAlert and HRD.  So we will have to see who has to sort that issue out for FT4.
Aug
AG5AT


locked Re: New HRD Release v6.7.0.269 Confusion

g4wjs
 

On 01/04/2020 18:46, August Treubig wrote:
LOTW and HRD were not really working.  The QSOS were not actually logged as FT4.

As for the MFSK mode and FT4 sub mode.  That is what the ADIF Gods proclaimed.  So you must follow.

The Video is very clear on how to clean up your log. and re-submit.

But alas, there is also now an issue between JTAlert and HRD.  So we will have to see who has to sort that issue out for FT4.

Aug
AG5AT
Aug and all,

the ADIF specification requires MODE=MFSK + SUBMODE=FT4, but what most talking about this fail to understand is that ADIF is a specification for passing QSO data between applications. The applications themselves can store QSO mode anyway they feel fit, what is most important is that they export FT4 mode QSOs in the correct ADIF format. Along with that applications can, and probably should, be flexible in what they accept when importing ADIF records. For example an application could easily accept just MODE=FT4 as a valid FT4 QSO mode. The problem with HRD all along has been that it failed to accept valid ADIF records with MODE=MFSK and SUBMODE=FT4 as records of QSOs made using the FT4 mode, so it was neither correct nor flexible.



--
73
Bill
G4WJS.


locked Re: New HRD Release v6.7.0.269 Confusion

 

LOTW and HRD were not really working.  The QSOS were not actually logged as FT4.

As for the MFSK mode and FT4 sub mode.  That is what the ADIF Gods proclaimed.  So you must follow.

The Video is very clear on how to clean up your log. and re-submit. 

But alas, there is also now an issue between JTAlert and HRD.  So we will have to see who has to sort that issue out for FT4.

Aug
AG5AT


locked Re: Hamspots

Michael Black
 

Settings/Manage Settings/Web Services -- Enable the Hamspots.net checkbox.

de Mike W9MDB




On Wednesday, April 1, 2020, 09:15:58 AM CDT, Martin Blaise <martingblaise@...> wrote:


On hamspots I see my call spotted but the section calls I spotted is blank, can someone help me fix this?


locked Unable to install JTAlert updates

Jim Denneny
 

Updates are blocked.  I believe all Security programs have been deleted or turned off.  I removed TotalAV completely and turned off Windows Defender.  Your JTAlert updates are still blocked. I don't know how this could happen. 

73, Jim K7EG


locked Re: JTAlert 2.16.3 Logging

Tom Job
 

I upgraded to JT Alert 2.16.3 this morning and it runs just fine.   Much faster decoding it seems, too.  I am using HRD Log v5.24.0.38 and JTA is still logging to it even though the log is closed.  I guess it's something specific to v6 of HRD. 

Thanks Lauriefor the excellent work.


locked Scan Log not picking up FT4 confirmed QSOs

jushamn@...
 

This is a record copied directly from the adif log that I imported from LOGic 9. The path to the adif is correct in JTAlert. 
Attached is a screenshot of Wanted Provinces window. I have 16 confirmed QSO with various Provinces with some duplicates. The following is an example of one. Note: <lotw_qsl_rcvd:1>Y <lotw_qsl_sent:1>Y 
It is not just Provinces that are not working for FT4. The same is true for Prefixes. 
It seem that none of the modes are being updated not just FT4. It is just the one that is most obvious because I have been using FT4 seriously since the beginning of 2020. That's when I noticed the problem. 
The adif update have been working in the past. Other modes have been updating just fine. However, I suspect that non of them are now updating because I have not observed any green highlighted line when I run a scan log lately.

<call:5>VE4RK <qso_date:8:d>20160426 <time_on:6>224301 <rst_sent:3>-01 <rst_rcvd:3>-08 <name:19>RICHARD EDWARD KING <qth:8>WINNIPEG <mode:5>JT65A <freq:6>14.076 <band:3>20M <dxcc:1>1 <qsl_sent:1>Y <operator:5>K7PDW <tx_pwr:2>20 <gridsquare:4>EN19 
 
<address:69:m>Richard Edward King
238 ROSEBERRY STREET
WINNIPEG, MB  R3J 1T2
CANADA
 
<lotw_qsl_rcvd:1>Y <lotw_qsl_sent:1>Y <eqsl_qsl_sent:1>N <cont:2>NA <cqfield:2>EN <cqz:1>4 <ffma:4>EN19 <ituz:1>3 <pfx:3>VE4 <qslsdate:8>20171014 <ve_prov:2>MB <eor>


locked JTAlert 2.16.3 Logging

Barry <boat.anchor@...>
 

Using HRD6.7.0.269
Logbook must now be open to be able to log
in JTA2.16.3
This is a change from 2.16.2
cheers de
Barry


locked New HRD Release v6.7.0.269 Confusion

Stephen Taylor - K6SJT
 

I just watched the video from HRD about the new version that's supposed to 'correct' FT4 logging to LoTW.

As a result I'm very confused. I've been using JTAlert > HRD > LoTW logging since August 2017. When I look on my LoTW under MODE all the FT8 and FT4 contacts are shown by using the appropriate database filter (FT4 or FT8).

I don't under why I'm now supposed to change these to MODE = MFSK  with SUB MODE = FT4

To me it appears LoTW has been recognizing and accepting FT4 mode all along into my log book, so why the change HRD is suggesting?

Looking for to some clarification - Thanks
Stephen - K6SJT


locked Hamspots

Martin Blaise
 

On hamspots I see my call spotted but the section calls I spotted is blank, can someone help me fix this?

6101 - 6120 of 34798