Date   
Re: Finally, I think it is set up right accept for one thing

Morris WA4MIT
 

Hi Bob I had similar with my setup and shutting down HRD, Relay, JTalert and JT software then restarting everything and run scan again and see if this works hope that helps 73 wa4mit Morris

Finally, I think it is set up right accept for one thing

Bob Davet
 

Got all the files pointing to the right direction.

Running JT65-HF V4

JTAlert V2.9.7

QSORelay V1.3.6343.31566


Using HRD logging. When I make a contact and log it it goes into my HRD log very quickly.

What I am not seeing is my contacts, countries and other stuff like that, that I have already contacted show up right in JTAlert.

Seem to be showing in JT65-HF correctly, I see the ones I just contacted today there as qso b4.

But that same ontact in JTAlert shows like I never contacted them before.


It seems like there is something missing coming back from my HRD log.

Is there a setting that I have missed?? I followed the new setup PDF and don't think I missed anything.

I selected the Standard ADIF File in JTAlert for logging. Set up a file name for it.

Selected the same file in QSORelay for JTAlert ADIF file name.

I even tried San Log and Update in JTAlert thinking that might update things but it up dated but I'm still not getting the feed back from my HRD log.

I also tried synchronizing the database in QSORelay after making these contacts just to see if that made a difference but it didn't.

It seems like JTAlert is not getting log feedback from the HRD and QSORelay logs so it can update its log.


Bob

W8RID


Re: JT Alert Scan Log & Update

zs6wn@...
 

Hi Chris, tnx a lot.

I followed the instruction before my post but just to be sure I double checked and all was exactly as per your instructions.

I sync the database once again and then all was fine as before.

What went wrong earlier this week seems a mystery (in IT terms "a hidden feature").

Thanks for your patience.

73 de ZS6WN

Karel


locked Reporting an Issue - MUST READ

Chris VK2BYI
 
Edited

If you encounter a problem, before reporting the issue via our support forum, please read the following information.  You will then be able to provide us with technical information that will help to diagnose and resolve any coding issues more quickly.

Firstly, read the documents available in the Files folder of the forum, as a solution to your problem may be found there.  Also, search the message topics posted by other forum members, as a solution to your problem may be found there as well.

If you still cannot find a resolution, then follow these steps:

        1.  If an application error occurs, an exception log file will be automatically created using the following name format:

       Exception yyyy-MM-dd.log

       where yyyy-MM-dd is the current local date

        2.  If you can repeat the process that causes an error, refer to the Session Tracing section in the QSO Relay document on how to create a session log file.

        3.  Then repeat the process with session tracing enabled.

        4.  Be sure to uncheck the Enable tracing checkbox and click the Close button in the QSO Relay Options dialog when done. This will ensure that the full session tracing information is written and the file closed.

        5.  The exception and session tracing log files are written to the following folder:

       C:\Users\<your username>\AppData\Roaming\VK2BYI\QSORelay\

        6.  Zip up all the files from this folder, and send an email to me (my email address is on my QRZ.com page) explaining the issue you are encountering, and be sure to attach the zipped files.

        7.  You may also want to include a zipped copy of your HRD Logbook as an Access database (*.mdb) file, if that is possible.  I will keep the content confidential, and I will destroy the file when the issue has been resolved.

        8.  If the attachment(s) are too big to be sent via email, you can post it to the files section in our support forum instead.

Thank you,
Chris VK2BYI

locked Re: QSO Relay version 1.3

Chris VK2BYI
 

You're welcome Danny.  73 Chris

locked Re: QSO Relay version 1.3

Chris VK2BYI
 

That is great news Morris.  I am pleased you have it all working now.

I think it is a good idea anytime you change configuration settings, to restart all of the applications so that they all start afresh with the new configuration.  So when you returned and restarted HRD/JTAlert etc., it started working correctly.

I also checked the screen capture you sent of your JTAlert and QSO Relays settings, and they look correct to me.

Thanks for providing the other items I requested.  I will use it to make QSO Relay more resilient against 'goofy' data and make it more stable.

How that value got into RX Power, I have no idea either.  But regardless, it is a valid floating point number and the code should handle it.  It will in the next release.

Thanks for your patience and assistance.

73 Chris
VK2BYI

locked Re: QSO Relay version 1.3

Morris WA4MIT
 

Chris I shut everything down left home for about 3 hours and when returned restarted HRD/JTAlert did a alert scan and this time it worked. Did not change any settings. Have made a few contacts now and everything seems to function normally logging OK. I sent zipped files to your personal email. Appreciate your help and the QSO Relay software it does a great job.

73 Morris wa4mit 

locked Re: QSO Relay version 1.3

Morris WA4MIT
 

Partial success I was able to create a DB and it seems to have all my log in it this all went smooth, in JTAlert I setup for the ADI log it is pointed to the "log.adi" in the app data qso relay folder however a JTAlert scan says I have no states, countries etc confirmed so it is like day one on JT mode. I will send you the screen shots I made of my setup in Alert and Relay and my data base zipped if I can. The sync went without any errors in just a few seconds. In the UT7IJ log entry the number was like .9410000002300 something like that I used bulk edit to erase and I had this column showing and this was the only entry that had anything in this column now how did that get there?. Thanks Chris 73 wa4mit Morris

 

locked Re: QSO Relay version 1.3

Mike Davies <face@...>
 

Chris,

Thanks I've sent three files, session report, exception and zipped logbook .mdb to your email address as given in QRZ.com.  Looking forward to an answer.  Remember that this worked in v1.0.

Regards
--
Mike, G0KAD

locked Re: QSO Relay version 1.3

Chris VK2BYI
 

Crossed they are!  Let me know the goofy value too please. :)

locked Re: QSO Relay version 1.3

Chris VK2BYI
 

The synchronise database operation in version 1.1 downloaded all rows from HRD Logbook and then updated existing rows, and inserted new rows, in the SQLite database as individual transactions which made the performance terrible on larger datasets.  All of the rows but one or two may have been processed successfully, but a missing row or two probably went unnoticed.

But as I said, in order to improve the improve the performance in version 2, we switched to a truncate, then insert all rows in a single transaction model.  The performance improved dramatically, but if one bad row causes an error, then none get inserted.  A small price to pay for a dramatic improvement performance I think, but it also means I have to get the code to handle all types of error conditions, and obviously you have something in your database that my code can't handle - and it should.

I test with a row 100,000 test database that takes about 3 minutes to sync without any issues at all.  So I am keen to get to the bottom of this.

I forgot to ask if you could also zip up all of the '*.log' files, and the 'settings.config' file in your AppData folder and email them to me?

73 Chris
Vk2BYI


locked Re: QSO Relay version 1.3

Morris WA4MIT
 
Edited

Chris I could not get the DB to work at all I have tried uninstalling and reinstall program everything seems to indicate it was working but when look at delete DB there is nothing there. I have now reverted back to 1.1 again and it has the data base and logs to HRD .647 this takes an hour to run the sync. The only thing I can pinpoint as different is I am using the Maria DB in HRD. See my earlier post with info.  OK I put this up before seeing your latest about my problem will look into what you say and let you know back but it is working OK with version 1.1 why is that?. Thanks wa4mit

ok the UT2IJ had some goofy number in that column so after correcting this I will try again and let you know what happens keep your fingers crossed hi hi 73 thanks wa4mit


locked Re: QSO Relay version 1.3

Chris VK2BYI
 

Hi Morris,

Google tells me that Maria DB "is a binary drop in replacement" for MySQL, and that the MySQL client also works with MariaDB server - so it should work with QSO Relay if that is the case.

In order to get the performance to an acceptable level, the synchronise database operation truncates the 'Log' table in the QSO Relay database, and then inserts all rows from the HRD Logbook as a single transaction.  What this means is, if any one of the rows being inserted causes an exception, the whole transaction rollbacks and the 'Log' table in QSO Relay will be empty.  So that is why you see no contacts in QSO Relay.

That exception says in part: "Input string was not in a correct format. Couldn't store <> in RxPwrDecimal Column.  Expected type is Decimal."

You might want to take a look in the database and see what value you have in the Rx Power (COL_RX_PWR) column for a contact just before, or near, a contact with UT2IJ on 2014-05-03 at 00:11:38.

The insert statement reported in the exception log is for this contact, and is a valid statement.  But the row that actually caused the exception, may be the row just before this one in time (the rows are selected in QSO Date and Time On (COL_TIME_ON) order descending during the sync).

It is weird though, as COL_RX_PWR is a double/float type in all platforms supported by HRD Logbook, i.e. Access, SQL Server and MySQL, which can only hold valid floating point numbers or null.

Unless the Rx Power column value is important to you, try setting the value to 0 in the suspect row or rows and see if that allows the sync to run without exception.

Alternatively, you could send me a Maria DB database backup and I can restore it here and see if I can replicate the issue.  I will download a copy of the server from mariadb.org to my development system.

Let me know how you get on.

73 Chris
VK2BYI

locked Re: QSO Relay version 1.3

Chris VK2BYI
 

This is a strange one.

 

The insert statement that is captured in the session trace is for the previous contact for 5U5R is correct and is not the problem.


I believe the problem may lie with the PJ4/K2NG contact.  There should have been an Exception log file for May 17 created in the same folder as the session file, and will tell me more about what happened at around 20:58:58.  Can you send me all *.log files in that folder?

 

It may be an invalid value somewhere in the row for PJ4/K2NG that I haven’t encountered before, and therefore have not needed to code against.  Could you also send me a copy of you Access *.mdb file, if that is what you are using?  An ADIF Export may not help as it may remove the errant value as it is being extracted to the ADIF file.  I will only use your logbook to find the problem and I will destroy it afterwards.

 

73 Chris

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Mike Davies
Sent: Thursday, 18 May 2017 7:04 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] QSO Relay version 1.3

 

All is not quite well here but I have some info for you to consider.  The session log shows a fail at the 2nd instance of the callsign 5U5R which I worked 3 times on the same day in different band/mode slots.  QSO Relay doesn't seem to like this.  Any suggestions?
--
Mike, G0KAD

Re: JT Alert Scan Log & Update

Chris VK2BYI
 

Hi Karel,

Before you Scan Log and Update in JTAlertX, you need to do a similar thing with QSO Relay - it is the Synchronise Databases option on the menu.  This brings down a fresh copy of your HRD Logbook into the QSO Relay database, and then it updates the ADIF file that JTAlert is using for logging.  Then when you can Scan Log and Update in JTAlert, it is using the latest copy of your HRD Logbook data.

If you have done that, and it is still not showing up in JTAlert, then it sounds like the download from HRD Logbook is not working.  So take a look at the Configuring QSO Relay for Microsoft Access Databases document in the files section, as I refer to that document here...

There are two data flow paths in QSO Relay:

  1. The first is that taken by contacts being uploaded to HRD Logbook which is configured by the settings circled in Figure 2 in this document.  You will know if that is correctly configured if your contacts are popping up in HRD Logbook as you log them from JTDX/JTAlert;
  2. The second data flow is the complete HRD Logbook download that occurs during the Synchronise Databases operations.  That requires the settings circled in Figure 3. in this document to be correctly configured.  You will know if that is correctly configured if all of your HRD Logbook rows are being downloaded.  Check the last Sync Report file in your Documents/QSORelay folder, and make sure the numbers of rows synchronised in QSO Relay is the same as the number of rows in HRD Logbook.So pay particular attention to getting the Connection String setting in the QSO Relay Options dialog correct, and make sure it is accessing the same .MDB file that your contacts are kept in within HRD Logbook.

Obviously, it is also necessary that JTAlert and QSO Relay are referring to the same ADIF File that JTAlert is using for Standard ADIF File logging and that JTAlert and QSO Relay are using the same UDP Port values of 2333 for the Last QSO API in JTAlert, and the Incomping UDP Port number in QSO Relay Options.

73 Chris
VK2BYI


locked Re: QSO Relay version 1.3

ON4VT Danny OT4V <danny@...>
 

Hi all


All running smoothly here (with from all software QSOrelay, JTDX and JTAlert, the latest versions)


Thanks Crhis ! 


73 ON4VT aka OT4V

Re: JTAlert 2.9.7

Chris VK2BYI
 

Excellent.

73 Chris
VK2BYI

locked Re: QSO Relay version 1.3

Chris VK2BYI
 

Hi Jacques,

You are most welcome.  Enjoy and good DX.

Thanks for the feedback.

73 Chris
VK2BYI

JT Alert Scan Log & Update

zs6wn@...
 

HI Chris e.a.

First of all thank you for this excellent program. It makes life a lot easier. I was about to jump ship from HRD to Log4OM or DXKeeper but just could not muster the courage to do it.

I installed all the latest versions (QSORelay, JTDX, HRD, etc) and all work FB, thanks.

However, I did am usual JTAlert Scan Log & Update and now all QSO's shows as New DXCC, -continent, zones, etc.

I checked the documentation but maybe I'm missing something.

How do I fix this? (I obviously cannot directly scan the HRD log anymore).

Or is there some work around?

73 es GL de ZS6WN

Karel 

locked Re: QSO Relay version 1.3

f1vev@...
 

Hi CHris


All working great this end many thanks for your work 73 Jacques F1VEV
--
Ic 7300 -  Win 10 Pro  - WJSTX 1.7 - JTalert 2.94 -  HRD 6.4.647 - Maria dB - Avast Premium.