Locked logging to HRD Logbook #logging


Michael E Wilson Sr <ke5wct@...>
 

I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.


Robert Lorenzini
 

Expect HRD to be problematic on a regular basis.

Bob - wd6dod

On 7/3/2021 6:27 AM, Michael E Wilson Sr wrote:

I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.




Shawn Johnson
 

Sounds Like you have the logging From WSJTX enabled From UDP, and In JT alert.. Double check the settings and go over the procedure.. WSJTX logs to the log file.. you probably have the UDP in WSJTX enabled along with JTalert and why your getting the dupes.. Double check and use one or the other.. hope it helps..

 

Sent from Mail for Windows 10

 

From: Robert Lorenzini
Sent: Saturday, July 3, 2021 11:46 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] logging to HRD Logbook #logging

 

Expect HRD to be problematic on a regular basis.

Bob - wd6dod

On 7/3/2021 6:27 AM, Michael E Wilson Sr wrote:

I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.

 
 
 

 

 


Brad
 

I was having trouble running WSJT-X JTalert and HRD also until I found a video on how to change the HRD log book data file to and MariaDb database and all the problems went away. And put the right configuration in both WSJT and jtalert.

On Jul 3, 2021, at 9:46 AM, Robert Lorenzini <bob@...> wrote:

 Expect HRD to be problematic on a regular basis.

Bob - wd6dod

On 7/3/2021 6:27 AM, Michael E Wilson Sr wrote:
I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.





Brad
 

Watch this YouTube video.

https://www.youtube.com/watch?v=C7f-RZOnmDs

 

Sent from Mail for Windows 10

From: Brad Fox
Sent: Saturday, July 3, 2021 11:49 AM
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] logging to HRD Logbook #logging

 

I was having trouble running WSJT-X JTalert and HRD also until I found a video on how to change the HRD log book data file to and MariaDb database and all the problems went away.  And put the right configuration in both WSJT and jtalert.

> On Jul 3, 2021, at 9:46 AM, Robert Lorenzini <bob@...> wrote:
>
>  Expect HRD to be problematic on a regular basis.
>
> Bob - wd6dod
>
> On 7/3/2021 6:27 AM, Michael E Wilson Sr wrote:
>> I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
>> What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.
>>
>>
>>
>
>
>
>

 


Brad
 

Go to this YouTube video
YouTube.com/watch?v=C7f-RZOnmDs

On Jul 3, 2021, at 11:49 AM, Brad Fox <bradfox42@...> wrote:

I was having trouble running WSJT-X JTalert and HRD also until I found a video on how to change the HRD log book data file to and MariaDb database and all the problems went away. And put the right configuration in both WSJT and jtalert.

On Jul 3, 2021, at 9:46 AM, Robert Lorenzini <bob@...> wrote:

 Expect HRD to be problematic on a regular basis.

Bob - wd6dod

On 7/3/2021 6:27 AM, Michael E Wilson Sr wrote:
I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.





Russ Ravella
 

Agreed. I actually went the OTHER way (HRD to DXKeeper) to get away from things just like that. And also the pretty poor support of their software, despite expecting you to pay for it. My advice would be to change back.
73 Russ KR6W

On Jul 3, 2021, at 8:22 AM, Robert Lorenzini <bob@...> wrote:

Expect HRD to be problematic on a regular basis.

Bob - wd6dod

On 7/3/2021 6:27 AM, Michael E Wilson Sr wrote:
I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.





Bruce Jungwirth
 

I’ve been using WSJTX and JTAlert logging to HRD for over 2years and have never had a problem. Have I just been lucky?
Bruce, K0SON

On Jul 3, 2021, at 10:22 AM, Robert Lorenzini <bob@...> wrote:

Expect HRD to be problematic on a regular basis.

Bob - wd6dod

On 7/3/2021 6:27 AM, Michael E Wilson Sr wrote:
I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.




Bob Turner
 

HRD logs whatever is sent to it.  Only one program should be logging the contact to HRD.  It seems to me that is your problem.  

 

7 3   Bob

N2SCJ

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Michael E Wilson Sr
Sent: Saturday, July 3, 2021 9:27 AM
To: main@WSJTX.groups.io
Subject: [WSJTX] logging to HRD Logbook #logging

 

I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.


Michael E Wilson Sr <ke5wct@...>
 

Turned off the secondary UDP and problem solved. Thanks.


Gilbert Baron
 

Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bruce Jungwirth via groups.io
Sent: Saturday, July 3, 2021 14:58
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] logging to HRD Logbook #logging

I’ve been using WSJTX and JTAlert logging to HRD for over 2years and have never had a problem. Have I just been lucky?

YES


Bruce, K0SON
On Jul 3, 2021, at 10:22 AM, Robert Lorenzini <bob@...> wrote:

Expect HRD to be problematic on a regular basis.

Bob - wd6dod

On 7/3/2021 6:27 AM, Michael E Wilson Sr wrote:
I recently changed from DXKeeper log to HRD Logbook. The change was easy and worked. However, when JTAlert was set to log to HRD Logbook, I got triple entries in the log. Two of the entries were from JTAlert, one of which was flagged in the log with "date/time error". I disabled the JTAlert logging and every thing returned to normal with only WSJT-X providing the log info.
What is going on. Does the HRD Logbook network server port have anything to do with this issue? When I was using DXKeeper, every thing work great.






--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Bill M
 

I used HRD for many years(2010 al;l versions) and had no troubles, and none since logging since adding of WSJT-x FT8 and JTAlert a couple of years ago. Use what you like but avoid trashing others!
Bill W2CQ