Date   

Re: JTAlert shows incorrect log entries

Bruce Croskey
 

Yes I have it selected as you pointed out.... I feel a little caught in the middle as you say contact JTAlert and JTAlert says contact you....it is easier for me to update JTAlert manually by clicking on the states as I work them... some computer some paper and pencil.... works for us old school folks hi hi


Re: JTAlert shows incorrect log entries

Chris VK2BYI
 

Hi Bruce,

I am assume that before you Synchronize Databases, you have 'All Contacts' selected for the Logbook Extract in the QSO Relay options:



This means that your entire logbook will be extracted as an ADIF file for JTAlert to use for it's Scan Log and Update process.

If JTAlert is not correctly updating worked states, then you need to check the settings in JTAlert for Wanted US State.  It is not dependent upon QSO Relay.

You should seek support from the HamApps support group (Support@HamApps.groups.io) for more detailed assistance.

73 Chris
VK2BYI


JTAlert shows incorrect log entries

Bruce Croskey
 

JTAlert logs perfectly into my HRD log without any problem and I sync the data base without any problem and then I scan and update JTAlert and it seems to work OK except it does not reflect the data in my HRD log...I have checked my log against my LOTW account in ARRL and all my contacts are there and verified and show correctly in my log but after scanning and updating, ... wanted states for example... it shows a different result and list states that are verified as not verified... What am I missing???
73, bc


Re: Synchronize error message

Chris VK2BYI
 

You are most welcome, Roland.
Enjoy!
73 Chris
VK2BYI


Re: Synchronize error message

Joy Rider
 

Hi Chris,

thank you very much, full ACK. After deleting the file contact.cache in the QSO Relay folder sync is working again. Also I have disabled the Log Address option in JTAlert for now.

TU for this great piece of Software and keep it up !
73's de Roland HB9VQQ


Re: Synchronize error message

Chris VK2BYI
 

Hi Roland,
You have a 'cached' contact that QSO Relay is trying to log in HRD Logbook, but can't because it has embedded carriage return/line feed characters (or newlines) in the Address field.  There is a known bug in HRD Logbook, whereby embedded newlines in the Address field can prevent the record from being processed correctly.  The contact is for QSO Date: 2017-08-19, Time On: 05:21:00, Call: EA6BH, Band: 40m and Mode: FT8, which I note has been successfully logged in your Access database that you sent me.  However, the Address field is only partially populated because of the defect in HRD Logbook, and you will need to perform a 'Lookup' in HRD Logbook itself to complete the Address field correctly.

 

Because you have this contact logged, you can simply delete the 'contact.cache' file in the QSO Relay folder, and you will be able synchronise databases and continue working normally.

 

To prevent this from happening again, you will need to exclude the Address field when logging contacts by changing a setting in JTAlert.  If you open the JTAlert settings and select the Logging node, you will see a checkbox labelled 'Log Address returned from an XML or previous QSO lookup'.  Make sure that this checkbox setting is not checked:

 
The downside to this workaround, is that the Address field will be blank in HRD Logbook for any JT-mode contacts you log while this checkbox is unticked, despite JTAlerts ability to look up the address for you.  If JTAlert gets an address from the lookup that contacts embedded newlines - which is perfectly acceptable and typical - the record will not be logged correctly.
 
This defect has been raised previously with HRD, and I have recently lodged another support request asking for it to be fixed.  I have been talking with them and they are working on a fix.  I don't know when this will be fixed, but I will follow up on it from time to time with them.
 
In the meantime, don't log the address field by keeping this checkbox setting unticked.  You can always perform the lookup and update the Address field after it has been logged in HRD Logbook.  This is what I do, as you will see I have no checkboxes selected in JTAlert in the Logging node as shown above.

73 Chris
VK2BYI
 


Re: Synchronize error message

Joy Rider
 

Hi Chris,

I have the exact same problem, running HRD 6.4.0.780.  I will zip the QSORelay folder and mail it to you.

73's
Roland


Re: QSO looging to latest HRD v780

f1vev@...
 

hi Antony  I find it strange also  I have  had to go back to JT alert for the time being but when support stops again ?? 

I too have the My loggbook access under Maria dB  and this way before QSO R came into play .

Maybe a win10 Pro update  messed things up who knows  it not dramatic but anoying  and yes all the developers have done and are doing  a great 

FT8 is fun indeed  

PS I keep a snapshot of all my set ups for all soft  and nothing has moved changed  if I compare since hiccup

I will sort it out one day  when I can devout more time ................. roll on retirement :-)

Cheers 
--
Ic 7300 -  Win 10 Pro  - WJSTX 1.7 - JTalert 2.94 -  HRD 6.4.647 - Maria dB


Re: QSO looging to latest HRD v780

Antony
 

Hi,
All my contacts are being logged as expected using all the latest program versions including the latest windows10.
As has been mentioned I had to produce an empty My Logbook-Access under the Maria DB.
Strange how there are differing outcomes from the same programs!
Having lots of fun with FT8.
Thanks to the developers of WSJT-x, JTAlert and of course QSO-Relay!
Regards,
Antony G4CUS


Re: QSO looging to latest HRD v780

f1vev@...
 

Unfortunately It appears so  will see what HRD have to say ....  Thank you Chris
--
Ic 7300 -  Win 10 Pro  - WJSTX 1.7 - JTalert 2.94 -  HRD 6.4.647 - Maria dB


Re: QSO looging to latest HRD v780

Chris VK2BYI
 
Edited

According to the Session 20170827065143.log file you provided, the QSO with SP8AWL and sent by JTAlert, was received by QSO relay, was saved to the SQLite file used by QSO Relay, and then forwarded on to HRD Logbook which reported that it was successfully logged by HRD.  However, when QSO Relay tried to verify if the QSO was in the database, it could not find it after 10 attempts over 10 seconds.

This would suggest that the combination of JTAlert and QSO relay seems to be working fine, but HRD logbook failed to actually log the contact, despite reporting that it had.  The problem appears to be with HRD Logbook.

A reboot might help.  Good luck.

73 Chris
VK2BYI


Re: QSO looging to latest HRD v780

f1vev@...
 

I have that and had it form day one  when HRD suggested that even before QSO relay came into being.  Now with prior version of JT alert all worked well until  latest version of JT alert

will dig into things later   Cheers Jacques
--
Ic 7300 -  Win 10 Pro  - WJSTX 1.7 - JTalert 2.94 -  HRD 6.4.647 - Maria dB


Re: QSO looging to latest HRD v780

Chris VK2BYI
 

Hi Jacques,

I got the files and from what I can see, your are experiencing a similar issue to that discussed in the HRD Logbook Accepts But Fails To Log Contacts topic.

What seems to have worked there was having an empty Access database open in HRD Logbook at the same time as the Maria DB database.

You might want to give that a try.  let me know how you get on.

73 Chris
VK2BYI


Re: QSO looging to latest HRD v780

Chris VK2BYI
 

Hi Jacques,

Can you please read the Reporting an Issue topic and provide me with the files I need to diagnose the problem?

73 Chris
VK2BYI


QSO looging to latest HRD v780

f1vev@...
 

HI 

did all as per book  all QSO are recorded  in the various logs and get looging prompt from JT alert  except  it is not looged in HRD logbook even with refresh.

went over everything UDPs etc  but for life of me cannot where  I meesed up  any help welcomed 
--
Ic 7300 -  Win 10 Pro  - WJSTX 18rc1 - JTalert 2.10.1 -  HRD 6.4.780 - Maria dB


Re: Cannot sync database

Bruce Croskey
 

Thank you...I still do not understand why it worked so well before, but I guess its just a fluke..Anyway, with the current ver> of JTAlert logging directly to HRD is the same as using QSO Relay so Ill go back to that method and besides Iam still have problems getting QSORelay to load..Again thank you for your EXCELLENT support and gud luck in the future.
73, bc


Re: Cannot sync database

Chris VK2BYI
 

NO.  Your approach will not work.

What happened is you are witnessing the defect in action.  If you keep trying to include the Address field, this will keep happening until the defect in HRD Logbook is fixed.  Be aware, the blank entries are what is left of the contact you just logged with most of the information sent from JTAlert/QSO Relay missing!  You are losing information.

It is better to log all of the detail coming in from JTAlert/QSO Relay except the Address field, so that the other details are not lost.  Once those details about the contact have been correctly captured, you can then use HRD Logbook itself to look up the Address.

In order for JTAlert to lookup the Address, you would have needed to configure it with details of your Online XML Callbook - HamQTH.com or QRZ.com.  With the same information configured in HRD Logbook, it can look up the same address and manually add it.

You open the Modify log entry dialog in HRD Logbook by doubling clicking on the row.  Here is one of my contacts with the Address field missing:



If I click on the Lookup button, HRD Logbook will use QRZ.com to lookup the address and add it to the contact:



This is the best you can do until HRD fix the defect in HRD Logbook.

73 Chris
VK2BYI


Re: Cannot sync database

Bruce Croskey
 

woops!!! Now the address appears in the HRD log then blinks off and is gone.. What happened??


Re: Cannot sync database

Bruce Croskey
 

It worked!!!! there were blank lines....Ill think abut the work around but I really need the addresses.... seems there may be another approach... If I do the blank line fix every time I do a JTAlert log Scan, would it not fix any errors and let me keep logging the address???
Thanks a million EXCELLENT support and I will Paypay you for sure
73


Re: Cannot sync database

Chris VK2BYI
 
Edited

Hi Bruce,

You do have 7 duplicate records in your logbook, but I think you are having trouble locating them because they all have blank values for QSO Date, Time On, Call, Band and Mode.

I have added 3 blank rows to one of my databases, so I can show you how to find and delete them.  Hopefully, the following lengthy explanation will make sense!

If I try to synchronise databases with these 3 blank duplicates present, I get similar results to you in the Synch Report file:

2017-08-25 09:58:10.1816 Synchronise databases started
2017-08-25 09:58:12.2722 The following duplicate contacts where detected in HRD Logbook:
2017-08-25 09:58:12.2722   Time On:  Call:            Band:        Mode:        Duplicates: 3
2017-08-25 09:58:12.2722 You will need to delete the unwanted rows before trying to synchronise the databases
2017-08-25 09:58:15.8435 Time elapsed: 00:00:05.6618755
2017-08-25 09:58:15.8440 Synchronise databases finished
 
When I open this database, everything looks normal so it is easy to assume there are no duplicates:



However, if I scroll to the very bottom of the grid, I can find the 3 blank rows I added:



It will be easier to see them if you click on the QSO Date column header twice to resort the grid and bring them to the top:




Now that they are easier to see, I suggest you click on the Backup button to make a backup of your logbook, then select all of the blank rows and press the Delete key to delete them:



Now that the duplicates are deleted, the database synchronisation can run to completion:

2017-08-25 10:04:11.9449 Synchronise databases started
2017-08-25 10:04:12.1633 HRD Logbook contains 1296 rows
2017-08-25 10:04:13.6019 1296 rows synchronised in QSO Relay
2017-08-25 10:04:13.7250 Time elapsed: 00:00:01.7801448
2017-08-25 10:04:13.7250 Synchronise databases finished

So how did these duplicate rows with blank values for QSO Date, Time On, Call, Band and Mode get into your logbook?  There is a know bug in HRD Logbook whereby embedded carriage return/line feed characters (or newlines) in the Address field cause the record to be logged incorrectly with missing values.

The work around is to exclude the Address field when logging contacts by changing a setting in JTAlert.  If you open the JTAlert settings and select the Logging node, you will see a checkbox labelled 'Log Address returned from an XML or previous QSO lookup'.  Make sure that this checkbox setting is not checked:



The downside to this workaround, is that the Address field will be blank in HRD Logbook for any JT-mode contacts you log while this checkbox is unticked, despite JTAlerts ability to look up the address for you.  If JTAlert gets an address from the lookup that contacts embedded newlines - which is perfectly acceptable and typical - the record will not be logged correctly.

This defect has been raised previously with HRD, and I have recently lodged another support request asking for it to be fixed.  I have been talking with them and they are working on a fix.  I don't know when this will be fixed, but I will follow up on it from time to time with them.

In the meantime, don't log the address field by keeping this checkbox setting unticked.  You can always perform the lookup and update the Address field after it has been logged in HRD Logbook.  This is what I do, as you will see I have no checkboxes selected in JTAlert in the Logging node as shown above.  

73 Chris
VK2BYI