Support@HamApps.groups.io

Re: HRD Logbook now has to be refreshed before new entries appear. #HRD

HamApps Support (VK3AMA)

#30544

On 20/06/2020 8:55 am, André C wrote:

I have the same problem as you, but i'm using version 5 of HRD logbook. I would like also to update automatically and refresh itself without me pressing the refresh button. If you get an answer, I would appreciate the feedback

HRD 5 logging with JTAlert involves direct writing to the log file (there is no logging API available with the old HRD5) and that has always needed the log to be refreshed manually.

de Laurie VK3AMA

Re: JTAlert working now but still double logging

HamApps Support (VK3AMA)

#30543

On 21/06/2020 5:26 am, kk5aa_fred via groups.io wrote:

I accidentally found why JTAlert was not working right. JTDX rc151 had unchecked the "Accept UDP Requests" box. Rechecked it and JTAlert is working now.

BUT... for some reason, I am getting double logging into my HRD Logbook. It does not date the entries and does not send them to eQSL (probably because the date is missing). I have noting turned on in JTDX for logging that I am aware of. I sent you two support requests (sorry to be such a PITA and whiner).

The only thing that gets loaded from here on out is your JTAlert updates!

Fred - KK5AA

Double logging will likely be happening because HRDLogbook is set to automatically log QSOs direct from WSJTX/JTDX. You can confirm this by examining the 2 log records, one will likely have more data (from JTAlert) than the other. As to where in HRDLogbook to turn that off, I have no idea, I don't own a copy of HRD to test. Hopefully, one of the groups HRD users will chime in with the info you need.

de Laurie VK3AMA

JTAlert working now but still double logging

kk5aa_fred

#30542

Laurie,

I accidentally found why JTAlert was not working right. JTDX rc151 had unchecked the "Accept UDP Requests" box. Rechecked it and JTAlert is working now.

BUT... for some reason, I am getting double logging into my HRD Logbook. It does not date the entries and does not send them to eQSL (probably because the date is missing). I have noting turned on in JTDX for logging that I am aware of. I sent you two support requests (sorry to be such a PITA and whiner).

The only thing that gets loaded from here on out is your JTAlert updates!

Fred - KK5AA

Re: HRD Logbook now has to be refreshed before new entries appear. #HRD

Bill M

#30541

No issues with latest versions of everything here...
Bill W2CQ

Seeing Double

Bill Tee

#30539

Hello everyone. This is my first post to this group. I don't know if it is my 11 year old computer (that runs just fine other that this problem), ram, integrated Graphics, HRD or JTAlert that is causing this double image. This has been ongoing for the past 3 versions. Any help will be greatly appreciated.

Thank You

Bill---WA3LLF

Re: JTAlert V2.16.8

Jim Denneny

#30538

Thanks for replies. Case closed.

I am unaware why some have no difficulty with EDGE. EDGE has been my default browser for a long time. All prior JTAlert upgrades have been with EDGE. I know all the steps to KEEP JTAlert blocked updates. My system is Win10 with latest Microsoft upgrades. It's time to kill this thread.

73, Jim K7EG

Re: HRD Logbook now has to be refreshed before new entries appear. #HRD

David De Coons

#30537

One other tip on HRD Logbook. If you have a LOT of entries you may consider switching to MariaDB. There is info on HRDs site including a link to YouTube video. If anyone needs assistance, contact me direct off list.

73

Dave wo2x

Sent from my waxed string and tin cans.

Show quoted text

On Jun 20, 2020, at 10:27 AM, Gary - AC6EG <AC6EG@...> wrote:

Thank-you everyone. Your responses told me the problem had to be with HRD Logbook. A few days ago I had accidentally closed the main window in HRD Logbook and my log disappeared. To restore it I had to use HRD File Manager to open one of two available databases. I chose "HRD My Logbook - Access" and my log reappeared. I thought I was good to go and didn't realize till this morning that I had made the wrong choice. I should have chosen "My Logbook." This would have restored my logbook and new entries would have again appeared instantly as they always have in the past. To André and others who might have this problem, check to make sure you are using the "My Logbook" database!

Gary - AC6EG

Re: JTAlert V2.16.8

afa1yy

#30536

Working FB here.
--
Art K0AY

Re: HRD Logbook now has to be refreshed before new entries appear. #HRD

Gary - AC6EG

#30535

Thank-you everyone. Your responses told me the problem had to be with HRD Logbook. A few days ago I had accidentally closed the main window in HRD Logbook and my log disappeared. To restore it I had to use HRD File Manager to open one of two available databases. I chose "HRD My Logbook - Access" and my log reappeared. I thought I was good to go and didn't realize till this morning that I had made the wrong choice. I should have chosen "My Logbook." This would have restored my logbook and new entries would have again appeared instantly as they always have in the past. To André and others who might have this problem, check to make sure you are using the "My Logbook" database!

Gary - AC6EG

Re: Decodes Window not populating in Version 2.16.8

Brad Adams

#30534

Update:

I tried deleting the decodes sqlite files in the jtalert\mycallsign\decodes directory and restarted JT Alert. Decodes window stopped populating altogether after this. I then deleted the files again and ran the install of version 2.16.8. The decodes window began populating, but again stopped at about 1,000 records. It then started populating again after several minutes. Watching the jtalert\mycallsign\decodes directory while JT Alert is decoding, you can see that when the decodes window is populating, the "decodes.sqlite-journal" file comes up, then disappears and the decodes.sqlite file grows in size. When the window is not populating, the "decodes.sqlite-journal" file is always there and the decodes.sqlite file still grows in size. I watched this for a while and saw that when the record count got to 2,112 the window stopped populating again and the "decodes.sqlite-journal" file was always present in the folder and actively counting up and down in size.

I failed to mention previously that my operating system is Windows 10 Professional.

Has anyone else seen this in 2.16.8?

Thanks
Brad, N4PYI

Re: HRD Logbook now has to be refreshed before new entries appear. #HRD

Dev Null

#30533

[ I'm using the latest version of everything, HRD,WSJTX,JTAlert, and WIN 10 with latest update. All being run with IC-7300 USB connection. No issues at all. The system works as smooth as glass.. ]

I second that emotion. Same here, latest versions of all, but with N3FJP. No problems with operation or downloads either.

Show quoted text

------ Original Message ------

From: "kk7h via groups.io" <kk7h@...>

To: Support@hamapps.groups.io

Sent: 6/19/2020 7:06:31 PM

Subject: Re: [HamApps] HRD Logbook now has to be refreshed before new entries appear. #HRD

Hi Gary,.
I'm using the latest version of everything, HRD,WSJTX,JTAlert, and WIN 10 with latest update. All being run with IC-7300 USB connection. No issues at all. The system works as smooth as glass, Click log, it goes in an shows up immediately. It has to be a setting somewhere that is not right. With that said, I have no idea where to look for the problem. I will keep snooping here and if I find something I'll let you know.
Mike KK7H

Re: HRD Logbook now has to be refreshed before new entries appear. #HRD

kk7h@...

#30532

Hi Gary,.
I'm using the latest version of everything, HRD,WSJTX,JTAlert, and WIN 10 with latest update. All being run with IC-7300 USB connection. No issues at all. The system works as smooth as glass, Click log, it goes in an shows up immediately. It has to be a setting somewhere that is not right. With that said, I have no idea where to look for the problem. I will keep snooping here and if I find something I'll let you know.
Mike KK7H

Re: HRD Logbook now has to be refreshed before new entries appear. #HRD

André C

#30531

Hello Gary, I have the same problem as you, but i'm using version 5 of HRD logbook. I would like also to update automatically and refresh itself without me pressing the refresh button. If you get an answer, I would appreciate the feedback

73 André VE2WNF

Garanti sans virus. www.avg.com

Show quoted text

Le ven. 19 juin 2020, à 16 h 51, Jim W4ATK <rogers9466@...> a écrit :

Not true in my standard “no monkeying” with HRD. The logbook shows the new entry immediately with no intervention. Perhaps your have it sitting on something other than date time.

On Jun 19, 2020, at 12:58 PM, Gary - AC6EG <AC6EG@...> wrote:

I've been using HRD Logbook and JTAlert together for many years and without any issues. I've recently found that new log entries no longer appear in the logbook unless I hit the refresh button. I first noticed this three days ago when I saw three FT8 QSO's were missing from the log. I manually entered the three log entries using data from the ALL.txt file and closed the log. When I reopened my HRD Logbook I saw I now had three dupes and discovered that JTAlert had added those entries to the log but I couldn't see them. I deleted the dupes and have been using the refresh button to see all new log entries but wonder why this is happening. I'm using the latest versions of HRD v6 , WSJT-X and JTAlert on a Win10 desktop. I have made no changes to the settings in any of these programs. I can obviously continue to hit the refresh button if I have to but wondered if this has happened to other HRD users & if anyone knows how to get the logbook to refresh automatically.

Gary - AC6EG

No sound v.2.16..6 ....2.16.8

Jesus

#30530

Good evening, although I see that there are problems with the sound, I remain the same for previous versions.

I have observed in About that "JTAlertV2.Manager.exe" does not have "UDP Ports used" activated, as seen in the attached files ...

Could it be the cause? Can it be activated?

Cordially,

Jesus, EA1YR

Re: HRD Logbook now has to be refreshed before new entries appear. #HRD

Jim W4ATK

#30529

Not true in my standard “no monkeying” with HRD. The logbook shows the new entry immediately with no intervention. Perhaps your have it sitting on something other than date time.

Show quoted text

On Jun 19, 2020, at 12:58 PM, Gary - AC6EG <AC6EG@...> wrote:

I've been using HRD Logbook and JTAlert together for many years and without any issues. I've recently found that new log entries no longer appear in the logbook unless I hit the refresh button. I first noticed this three days ago when I saw three FT8 QSO's were missing from the log. I manually entered the three log entries using data from the ALL.txt file and closed the log. When I reopened my HRD Logbook I saw I now had three dupes and discovered that JTAlert had added those entries to the log but I couldn't see them. I deleted the dupes and have been using the refresh button to see all new log entries but wonder why this is happening. I'm using the latest versions of HRD v6 , WSJT-X and JTAlert on a Win10 desktop. I have made no changes to the settings in any of these programs. I can obviously continue to hit the refresh button if I have to but wondered if this has happened to other HRD users & if anyone knows how to get the logbook to refresh automatically.

Gary - AC6EG

Re: JTAlert Scan / Rebuild out of sync with LOTW

Craig

#30528

Perfect. Thanks again for your help. C

Show quoted text

On Fri, Jun 19, 2020 at 3:07 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:

If you have an ADIF file you should be able to import it.

Back up what you have and start from scratch. Restore your old ADIF first, then import your backed up log.

Then do an LOTW update and it should confirm any QSOs that you may have missed.

Mike

On Friday, June 19, 2020, 01:05:33 PM CDT, Craig <nz4cwcraig@...> wrote:

Mike - thanks for your note / help. I was speculating that updating HRD with QSO's not currently noted from LOTW would be the means of rectifying this... just was hoping that there might be a scan option to upgrade the data rather than to replace / rebuild. Using the awards selections in LOTW, the callsigns of the needed entries are noted and if selected, the detailed contact info disclosed. So all is there... just a manual process to do it once, as you noted. Thanks Mike.

On Fri, Jun 19, 2020 at 1:56 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
The real way to fix this is to update your HRD log to contain the QSLs. It's painful but you only have to do it once....then you back it up and that becomes your reference point.

LOTW is a horrible source for archive as it only carries confirmed LOTW entries. It also doesn't know anything about card checks either (yet...that's supposed to be fixed on the next major release of LOTW in the fall).

You don't have a backup log anywhere? Have you used any other web sources like eQSL or Clublog?

Mike W9MDB

On Friday, June 19, 2020, 12:50:16 PM CDT, Craig <nz4cwcraig@...> wrote:

I have been using LOTW as THE source for my logged contacts, confirmations and awards. Using LOTW, I have changed logs over the many years, and not all of my contacts and confirmations reside in my HRD logbook. It has not been an issue in the past. But now since I cannot get enough of JTAlert, when I do a JTAlert scan log and rebuild it all works fine from HRD as selected, but then is out of sync with what is reported in LOTW. At that point, I have to manually update the band, modes and DXCC information which I have set as enabled in JTAlert. This is tedious each day.

So I have a dilemma as I am not always confident that the alerts from JTAlert are accurate. Have others addressed this issue?

73's Craig
NZ4CW

Re: JTAlert V2.16.8

Mike N8FRI

#30527

I downloaded the latest JTAlert and had no problems whatsoever with Defender and the new version of Edge (which functions faster than Google or Firefox).
I stayed away from Edge for a long time because it would not handle extensions, but that is now fixed. The instructions as written by Al, K0VM above are right on.
Mike N8FRI

Re: JTAlert Scan / Rebuild out of sync with LOTW

Michael Black

#30526

If you have an ADIF file you should be able to import it.

Back up what you have and start from scratch. Restore your old ADIF first, then import your backed up log.

Then do an LOTW update and it should confirm any QSOs that you may have missed.

Mike

Show quoted text

On Friday, June 19, 2020, 01:05:33 PM CDT, Craig <nz4cwcraig@...> wrote:

Mike - thanks for your note / help. I was speculating that updating HRD with QSO's not currently noted from LOTW would be the means of rectifying this... just was hoping that there might be a scan option to upgrade the data rather than to replace / rebuild. Using the awards selections in LOTW, the callsigns of the needed entries are noted and if selected, the detailed contact info disclosed. So all is there... just a manual process to do it once, as you noted. Thanks Mike.

On Fri, Jun 19, 2020 at 1:56 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:

The real way to fix this is to update your HRD log to contain the QSLs. It's painful but you only have to do it once....then you back it up and that becomes your reference point.

LOTW is a horrible source for archive as it only carries confirmed LOTW entries. It also doesn't know anything about card checks either (yet...that's supposed to be fixed on the next major release of LOTW in the fall).

You don't have a backup log anywhere? Have you used any other web sources like eQSL or Clublog?

Mike W9MDB

On Friday, June 19, 2020, 12:50:16 PM CDT, Craig <nz4cwcraig@...> wrote:

I have been using LOTW as THE source for my logged contacts, confirmations and awards. Using LOTW, I have changed logs over the many years, and not all of my contacts and confirmations reside in my HRD logbook. It has not been an issue in the past. But now since I cannot get enough of JTAlert, when I do a JTAlert scan log and rebuild it all works fine from HRD as selected, but then is out of sync with what is reported in LOTW. At that point, I have to manually update the band, modes and DXCC information which I have set as enabled in JTAlert. This is tedious each day.

So I have a dilemma as I am not always confident that the alerts from JTAlert are accurate. Have others addressed this issue?

73's Craig
NZ4CW

Re: JTAlert V2.16.8

Al Groff

#30525

First, there are three parts to a successful in stall with false positives. First is the download process which is dependent on the browser download protocols and does not look at Windows Defender file exceptions. Next is installation process and then post install which are effected by the Windows Defender exception list.

Here are the exceptions that I ran with the Windows Edge browser...( V83.0.478.45 )

click on the ... and then select Keep

then select Show more

Select Keep anyway ( or Report this app as safe )

Then proceed to install...

( I did a 'report this app as safe' on this version of JTA and now when I install on another PC, Edge does not flag it during download.. ?? )

AL, K0VM

Show quoted text

On 6/19/2020 12:11 PM, Jim Denneny wrote:

I am on Win10 and recently got their most recent, large upgrade. I was thinking the same thing. They must have tightened their blocking at that time. Strange because I added exception for folders: HamApp and JTalert folders. Since I could not download v2.16.8, I could not add exception for the file.

AVOID EDGE. Use Chrome or Firefox.

&3, Jim K7EG

Re: JTAlert Scan / Rebuild out of sync with LOTW

Craig

#30524

Mike - thanks for your note / help. I was speculating that updating HRD with QSO's not currently noted from LOTW would be the means of rectifying this... just was hoping that there might be a scan option to upgrade the data rather than to replace / rebuild. Using the awards selections in LOTW, the callsigns of the needed entries are noted and if selected, the detailed contact info disclosed. So all is there... just a manual process to do it once, as you noted. Thanks Mike.

Show quoted text

On Fri, Jun 19, 2020 at 1:56 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:

The real way to fix this is to update your HRD log to contain the QSLs. It's painful but you only have to do it once....then you back it up and that becomes your reference point.

LOTW is a horrible source for archive as it only carries confirmed LOTW entries. It also doesn't know anything about card checks either (yet...that's supposed to be fixed on the next major release of LOTW in the fall).

You don't have a backup log anywhere? Have you used any other web sources like eQSL or Clublog?

Mike W9MDB

On Friday, June 19, 2020, 12:50:16 PM CDT, Craig <nz4cwcraig@...> wrote:

I have been using LOTW as THE source for my logged contacts, confirmations and awards. Using LOTW, I have changed logs over the many years, and not all of my contacts and confirmations reside in my HRD logbook. It has not been an issue in the past. But now since I cannot get enough of JTAlert, when I do a JTAlert scan log and rebuild it all works fine from HRD as selected, but then is out of sync with what is reported in LOTW. At that point, I have to manually update the band, modes and DXCC information which I have set as enabled in JTAlert. This is tedious each day.

So I have a dilemma as I am not always confident that the alerts from JTAlert are accurate. Have others addressed this issue?

73's Craig
NZ4CW