Date   

locked Re: QSO Relay Settings and Data Flow

Chris VK2BYI
 
Edited

PS:  The group email that was sent for the first post in this topic, contains the full resolution image of 1608 x 1250 pixels.  At this resolution it prints clearly enough on A4 size paper, and I hope US-Letter, so that it can be read.

For those who do not subscribe to forum emails, you can download the full resolution image from here: QSO Relay Settings and Data Flow

73 Chris
VK2BYI


Re: sync fail

SV8JNL SV8JNL
 

PLease could you tell me if its critical that the ham radio deluxe ip server rus not in 127.0.0.1 but in 192.168.10.10?


Re: New version and DB

Antony
 

Hi Chris,

just downloaded the latest versions of JTAlert and Relay. The only problem I had was with Mcafee which kept putting a JTAlert file in the quarantine folder. After a lot of reading I managed to get the file into Mcafee's 'trusted list'. Reading your very precise instructions I was successful with logging contacts into HRD without problem, including syncing the logs. 

Many thanks for a great program and all the work put into the precise instructions. Regards, Antony G4CUS

ps. I love the chart you sent out earlier giving the data flow


Re: sync fail

Chris VK2BYI
 

Yes, it is critical.  QSO Relay uses the Logbook API command line interface (CLI) to log contacts in HRD Logbook via 127.0.0.1 port 7826.

It should be no problem as far as the download from HRD Logbook to QSO Relay is concerned, especially if you are using Microsoft SQL Server or Oracle MySQL for the database server, as you can specify the server name in the Connection String (OLEDB) settings.  If you are using a Microsoft Access (.mdb) file for the database in HRD Logbook, you will have to share that file on your local area network so it can be accessed from the PC running QSO Relay. That should work, but I haven't personally tried that.

However, I do not know how you can access the CLI from a different PC. There does not appear to be an option in HRD Logbook settings anywhere, where you change the values of 127.0.0.1 and port 7826 used by the CLI.  This means that QSO Relay and HRD Logbook need to be on the same PC.

You might want to post a question on the Ham Radio Deluxe Support Forum and ask if anyone knows if the Logbook API CLI interface can be accessed from another PC.

If anyone reading this knows, please let us know, as I am only too willing to support it if it can be done.

73 Chris
VK2BYI


Re: sync fail

SV8JNL SV8JNL
 

Thank you for your answer but all programs are in the same pc i dont know why thr hrd uses the ip of the pc and not the 127.0.0.1. All the apps are in the same pc. I use microsoft access mdb.

With the previus version of qso relay  everything was workig fine.




Sent with SolMail App

--------- Original Message ---------
From: Chris VK2BYI
To: vk2byi-qsorelay@groups.io
Date: Mon May 22 05:11:51 EEST 2017
Subject: Re: [vk2byi-qsorelay] sync fail

Yes, it is critical.  QSO Relay uses the Logbook API command line interface (CLI) to log contacts in HRD Logbook via 127.0.0.1 port 7826.

It should be no problem as far as the download from HRD Logbook to QSO Relay is concerned, especially if you are using Microsoft SQL Server or Oracle MySQL for the database server, as you can specify the server name in the Connection String (OLEDB) settings.  If you are using a Microsoft Access (.mdb) file for the database in HRD Logbook, you will have to share that file on your local area network so it can be accessed from the PC running QSO Relay. That should work, but I haven't personally tried that.

However, I do not know how you can access the CLI from a different PC. There does not appear to be an option in HRD Logbook settings anywhere, where you change the values of 127.0.0.1 and port 7826 used by the CLI.  This means that QSO Relay and HRD Logbook need to be on the same PC.

You might want to post a question on the Ham Radio Deluxe Support Forum and ask if anyone knows if the Logbook API CLI interface can be accessed from another PC.

If anyone reading this knows, please let us know, as I am only too willing to support it if it can be done.

73 Chris
VK2BYI


Re: sync fail

Jerry
 

127.0.0.1 is a reserved IP address which systems interpret as meaning "this device".

73,
Jerry KB2GCG


- "Defeat lasts one day, giving up lasts a lifetime."

On May 21, 2017, at 10:28 PM, SV8JNL SV8JNL <sv8jnl@...> wrote:

Thank you for your answer but all programs are in the same pc i dont know why thr hrd uses the ip of the pc and not the 127.0.0.1. All the apps are in the same pc. I use microsoft access mdb.

With the previus version of qso relay  everything was workig fine.




Sent with SolMail App

--------- Original Message ---------
From: Chris VK2BYI
To: vk2byi-qsorelay@groups.io
Date: Mon May 22 05:11:51 EEST 2017
Subject: Re: [vk2byi-qsorelay] sync fail

Yes, it is critical.  QSO Relay uses the Logbook API command line interface (CLI) to log contacts in HRD Logbook via 127.0.0.1 port 7826.

It should be no problem as far as the download from HRD Logbook to QSO Relay is concerned, especially if you are using Microsoft SQL Server or Oracle MySQL for the database server, as you can specify the server name in the Connection String (OLEDB) settings.  If you are using a Microsoft Access (.mdb) file for the database in HRD Logbook, you will have to share that file on your local area network so it can be accessed from the PC running QSO Relay. That should work, but I haven't personally tried that.

However, I do not know how you can access the CLI from a different PC. There does not appear to be an option in HRD Logbook settings anywhere, where you change the values of 127.0.0.1 and port 7826 used by the CLI.  This means that QSO Relay and HRD Logbook need to be on the same PC.

You might want to post a question on the Ham Radio Deluxe Support Forum and ask if anyone knows if the Logbook API CLI interface can be accessed from another PC.

If anyone reading this knows, please let us know, as I am only too willing to support it if it can be done.

73 Chris
VK2BYI


Re: sync fail

Chris VK2BYI
 

Correct, but I thought SV8JNL SV8JNL was trying to run the logbook on a different PC, but the post makes it clear that is not the case.


Re: sync fail

Chris VK2BYI
 

Well, then it must be a configuration issue.

Refer to the QSO Relay Settings and Data Flow diagram and double check all of your QSO Relay settings.

Don't worry about the IP Address of the PC itself, you must use an IP Address value 127.0.0.1, and TCP Port of 7826 to access HRD Logbook from QSO Relay as the following image shows..


Make sure that the Logbook Database: you have selected to upload contacts to QSO Relay, is the same database file you have selected in the Connection String: setting in QSO Relay.  For a detailed explanation on how you check that Logbook Database: and Connection String: are both referencing the same Access (.mdb), read this document: Configuring QSO Relay for Microsoft Access Databases

You can also follow the instructions in the Reporting an Issue, and send me that information if all else fails.

73 Chris


Re: New version and DB

Chris VK2BYI
 

Thank you very much for your kind words.

I am glad QSO Relay is working well for you.

Enjoy!

Chris

VK2BYI


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

Bob Davet
 

Morris:

 

That was it!! Everything looks right and seems to be transferring back and forth between the data bases now.

That was the only thing that I did not do. Usually that is one of the first things I do.

Just missed it.

 

Thanks

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Morris Wideman via Groups.Io
Sent: Friday, May 19, 2017 6:36 PM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] Finally, I think it is set up right accept for one thing

 

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


Virus-free. www.avast.com


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

Chris VK2BYI
 

Great news Bob!

73 Chris
VK2BYI


Re: New version and DB

Bob Davet
 

Anthony:

 

I have the same problem with AVAST.

There is a function in AVAST where you can turn it off for 10min.

I usually do that when I install programs from places that I have confidence in and I have no problems.

I then go back in and turn it back on or it will turn itself back on after the time limit expires.

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Antony
Sent: Sunday, May 21, 2017 9:26 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] New version and DB

 

Hi Chris,

just downloaded the latest versions of JTAlert and Relay. The only problem I had was with Mcafee which kept putting a JTAlert file in the quarantine folder. After a lot of reading I managed to get the file into Mcafee's 'trusted list'. Reading your very precise instructions I was successful with logging contacts into HRD without problem, including syncing the logs. 

Many thanks for a great program and all the work put into the precise instructions. Regards, Antony G4CUS

ps. I love the chart you sent out earlier giving the data flow


Virus-free. www.avast.com


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

Bob Davet
 

Chris:

 

Thanks for being patient with me through this.

 

Bob

W8RID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris VK2BYI
Sent: Monday, May 22, 2017 8:14 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] Finally, I think it is set up right accept for one thing

 

Great news Bob!

73 Chris
VK2BYI


Virus-free. www.avast.com


Re: New version and DB

Antony
 

Hi Bob,

yes, that's what I did with mcafee. One can choose the time in multiples of 15 minutes chunks. During the 'off' time I added the file to the 'trusted list'. My first attempts without doing the above were unsuccessful as mcafee kept putting the file in quarantine!

This is  the first time I've had to do this. One keeps learning!

Regards, Antony G4CUS


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

Chris VK2BYI
 

You're welcome.

73 Chris VK2BYI


QSORelay and HRD will not log

Ian Morrow
 

Hi Chris

 

Sorry to bother you but I am having bother with logging in HRD. Here is my setup software

Ham Radio Deluxe 6.4.0.647

JTAlertX 2.9.7

WSJT-X 1.7.0

QSORelay 1.3.6343.31566

Windows 10 64Bit PRO

 

I setup all the programmes as you said in you manual and everything works 100% (FANTASTIC SOFTWARE), but the problem is when I shut all the software down and the computer and comeback after a while.

When I start all up again HRD will not log at all.  I have changed nothing only switched everything off. I have tried to synchronise database again but it does not fix it!  I have been able to fix it but it is only temporary.  I have to delete the QSO RELAY SQLITE DATABASE, create a new database, and then synchronise the database and then it works 100% again until I shut all down again.

 

I will send you whatever Exception logs there are in the folder and also a Session Tracing Log that I created to your email if needed.

 

Best Regards

 

Ian MI1CCU/EI3HFB

 


Re: QSORelay and HRD will not log

Chris VK2BYI
 
Edited

Hi Ian,
I am not sure what might be happening, but you shouldn't have to recreate the SQLite file to get logging to work again.
So, reproduce the situation where the HRD logging is not working. Then:
  1. Tick the Enable Tracing checkbox in the QSO Relay options dialog to start a new session trace;
  2. Try to log a test contact or two;
  3. Un-tick the Enable Tracing checkbox to flush the session data and close the file;
  4. Zip up all the files from the QSO Relay AppData folder and upload the results to the Reported Issue Uploads folder, or email the zip file to me direct if you prefer.  You can get my email address from QRZ.com.

The session trace file will show me in detail what is happening from the contact being received from JTAlert through to it trying to be logged in HRD Logbook.

73 Chris

VK2BYI


Re: QSORelay and HRD will not log

Ian Morrow
 

Hi chris
I have uploaded the files to the Reported issue Uploads folder as you asked.
Hope this helps solve the problem for me.

73's Ian
MI1CCU/EI3HFB


HRD logging?

AMP
 

Chris:

I want to make sure I understand the operation of QSO-RELAY correctly:
Does HRD logging have to be open for QSO-RELAY to be able to add a qso to it? Or does QSO-RELAY interact directly with the HRD logbook ADIF file without needing the logging program to be running?

Tnx de Arnie W8DU


Re: HRD logging?

Chris VK2BYI
 
Edited

Hi Arnie,
The way contacts are logged is as follows:
  • JTAlert sends the contact to QSO Relay;
  • QSO Relay stores it in its database;
  • QSO Relay then relays it to HRD Logbook via a command line interface.
HRD Logbook has to be running in order for QSO Relay to be able to add a QSO.  The only method supported for writing QSOs into HRD Logbook is via a command line interface (CLI) that requires that HRD Logbook to be running.

If QSO Relay can't get a response from the HRD Logbook CLI, it caches the contact, and the next time you Synchronise Databases in QSO Relay, it will try multiple times to log the contact.  So, if you experience a temporary outage of HRD Logbook, your QSOs will not be lost.  Simply restart HRD Logbook, perform a Synchronise Database operation, and QSO Relay will try again to add any cached contacts into HRD Logbook.  However, this is a costly exercise - it can take many seconds to process each cached contact.  So in the normal course of events, you should always have HRD Logbook running.

The ADIF file is only used by QSO Relay to provide a complete extract from HRD Logbook for JTAlert to read duing its Scan Log and Update process to update your wanted alerts requirements.

73 Chris
VK2BYI