Date   

locked QSO Relay version 1.5

Chris VK2BYI
 

Please be advised that a new release of QSO Relay (Version 1.5) is now available for download at http://www.vk2byi.com.au/qsorelay/, or by selecting the Check for Updates... item on the QSO Relay menu.

This version is a minor release only, that adds a new feature, and that corrects a minor issue.  Most users will notice very little change in functionality.

  • Added a new feature whereby the scope of rows to be extracted from HRD Logbook during a synchronise database operation, can be filtered to 'All contacts', 'JT Mode contacts only' or 'Digital mode contacts only';
  • Corrected the contents of the County field when a new QSO is being added to HRD Logbook, to provide the County value only, and not the State and County values for US contacts.  The State value is still provided in the State field.

Again, we wish to thank all users for their positive feedback and patience in working with us to resolve some of the issues experienced.


Re: Possible small Bug?

Morris WA4MIT
 

version 1.5 seems to work great no double state entries in the county part of ADIF. Thanks Chris you do a great job really enjoy using your software. Noticed we had worked 2/9/16 on JT mode. Thanks 73


Re: Possible small Bug?

Chris VK2BYI
 

Hi Morris,

Thank you for the feedback and your kind words.  We did work 2016-09-02 - and verified on LoTW and eQSL.

73 Chris VK2BYi


jtalert not updating

rdaiprai@...
 

can someone help me ? i am running windows 7 ultimate ,jtdx ver17.9,latest ver of qsorelay, and the latest ver of hrd.
qsorelay works perfectly with hrd , when i sync hrd lod to qsorelay it works perfectly but when i do a scan log in jtalert it dose not update .
i have to put jtdx on a freq that has no signals on it and restart jtalert and then do a scanlog and it seams to work but once jtdx receives a signal  to decode jtalert scanlog dose not work again.
any thoughts on this problem?
thanks rich n0umf
rdaiprai@...


locked Re: QSO Relay version 1.5

Howard Sidorsky
 

Hi Chris,

 

Until Field Day and the prep prior to FD, WSJT with QSO Relay was working just fine.  All of a sudden as I went back to JT65 today, I realized that it is no longer working.  I’ve checked everything and everything seems to be okay. 

 

However, I do not seem to have the current QSO in the log.adi file.  I cannot figure out why contacts are not going there.  I have sync’d QSO Relay… but no luck. 

 

I realize that it is now Saturday for you but if you could let me know what it would be a good time to reach you, either today or during the week, I would greatly appreciate it.  If in the mean time I solve the problem I will let you know…

 

Thanking you in advance,

 

Howard – K6SID….

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris VK2BYI
Sent: Sunday, June 11, 2017 9:13 PM
To: vk2byi-qsorelay@groups.io
Subject: [vk2byi-qsorelay] QSO Relay version 1.5

 

Please be advised that a new release of QSO Relay (Version 1.5) is now available for download at http://www.vk2byi.com.au/qsorelay/, or by selecting the Check for Updates... item on the QSO Relay menu.

This version is a minor release only, that adds a new feature, and that corrects a minor issue.  Most users will notice very little change in functionality.

  • Added a new feature whereby the scope of rows to be extracted from HRD Logbook during a synchronise database operation, can be filtered to 'All contacts', 'JT Mode contacts only' or 'Digital mode contacts only';
  • Corrected the contents of the County field when a new QSO is being added to HRD Logbook, to provide the County value only, and not the State and County values for US contacts.  The State value is still provided in the State field.

Again, we wish to thank all users for their positive feedback and patience in working with us to resolve some of the issues experienced.


Re: QSORelay and HRD will not log

NA6MB Mike <na6mb.mike@...>
 

Was a solution found?
i have a similar problem.
Set up three PCS, win 8 worked fine two win 10 don't work.
Win 8 has HRD UDP set to 2333, as does jtalert and QSO relay.
Win 10 have UDP set to 2237 default.
i changed HRD JTAlert and WJST-X to all have 2333.
No good.

Ideass?

NA6MB
Mike


Re: QSORelay and HRD will not log

Chris VK2BYI
 

Other users experiencing issues with MariaDB have found it helps to have another, empty Access Logbook database open in HRD Logbook at the same time as the MariaDB database.  It also worked for me on a couple of occasions and I use Microsoft SQL Server.
73 Chris VK2BYI


Re: QSORelay and HRD will not log

NA6MB Mike <na6mb.mike@...>
 

 I'm using Microsoft access database not Maria but symtoms sounded the same .


Re: QSORelay and HRD will not log

Dave wo2x
 

2237 is the port for WSJT-X to JT Alert.

2233 is JT Alert to QSO Relay.

 

Here’s a screenshot of settings for WSJT-X and QSO Relay for my setup. I am NOT using Maria DB but everything works fine.

Make sure the TCP port is correct for QSO relay to talk to HRD Logbook. Should be 7826.

 

Dave wo2x

 

 

Sent from Mail for Windows 10

 

From: NA6MB Mike
Sent: Thursday, July 13, 2017 8:35 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] QSORelay and HRD will not log

 

 I'm using Microsoft access database not Maria but symtoms sounded the same .

 


Re: QSORelay and HRD will not log

Chris VK2BYI
 

Thanks Dave!
Mike, if the Windows 8 PC is working, use it as the reference when checking the settings on the Windows 10 PCs and make sure all of the settings are identical.  QSORelay was developed on Windows 10 and tested on Windows 7, 8, 8.1 and 10.
You should also refer to the QSO Relay Settings and Data Flow topic pinned second from the top in the Messages area, which has another diagram showing all of the critical settings in JTAlert and QSORelay and their purpose.  You may have to zoom your browser to 150% or more to make the diagram easy to read.
73 Chris VK2BYI


Re: QSORelay and HRD will not log

Chris VK2BYI
 
Edited

Dave, I just noticed something in the screen capture of your settings posted above.

You have your JTAlert ADIF Log File setting in QSO Relay set to the JTAlert 'lastqso.adi' file.  That is not correct, that file in JTAlert is not used by QSO Relay.

Referring to the diagram in QSO Relay Settings and Data Flow topic as mentioned in my previous reply to Mike, check the "Log File" setting on the "Standard ADIF File" section under "Logging" in JTAlert:

And set the JTAlert ADIF Log File setiing in QSO Relay to the same value:

The examples shown here are from my system.  The actual filenames will be slightly different on your PC.  With the setting you have at the moment, QSO Relay will still relay contacts to HRD Logbook OK, but you will not be able to update your Wanted Alert requirements in JTAlert if that is important to you.


73 Chris VK2BYI


PLEASE ACTIVATE ACCOUNT

k5rcd
 

 


Virus-free. www.avast.com


Re: PLEASE ACTIVATE ACCOUNT

Chris VK2BYI
 

Done.
Only your first post (this one) requires approval.  All future posts will be automatically moderated.
73 Chris


HRD 6.4.0.671 Logbook Logbook API Not working

Chris VK2BYI
 

The Logbook API using TCP on port 7826 in the latest version of HRD Logbook (6.4.0.671) is not working.
It has been reported elsewhere that HRD are aware of the issue and are working on a fix.
In the meantime, you may want to hold off upgrading until further advice from HRD.
73 Chris VK2BYI


Previous Worked B4 not being shown.

k5rcd
 

Today I installed QSO Relay ver. 1.5 
I'm running HRD Logbook ver. 6.3.0.410
JT Alert ver. 2.10.0 and WSJTX ver. 1.8.0 - rc1.

All seems to be working properly EXCEPT, the worked B4 indicator in JT Alert is not showing up for call signs worked before today. The ones I worked today, after setting everything up, are correctly indicating if they were worked B4. I have not checked the "ignore band" or "status before this date" boxes on JT Alert Worked B4 setup.

I have done a scan and update in JT Alert, and synchronized all databases in QSO Relay. 

I've searched JT Alert settings for a screen to find where the worked B4 database is stored, to see if it needs to be changed, but cannot find that information. I clearly remember seeing it before, in case something there needs changed or updated, but just can't find it

Any help getting this corrected will be greatly appreciated.

Thanks & 73,
Randy Davis
K5RCD South Texas


Re: Previous Worked B4 not being shown.

Morris WA4MIT
 
Edited

Hi Randy look in C, users, (your computer name), AppData, local, Ham-Apps, JTAlert-X (for WSJT-X), (YOUR CALL), logs. Here you will find B4log.mdb

Hope I have that right and helps you out. but what I use to find using QSORelay was that I had to scan with JTAlert a couple or more times to get thing to work and show up. If you scan and then go back and look at the results before you click OK
and make sure that it actually scanned and add states or whatever. Cause sometimes the first scan would just not work and say on 20 meters you only needed 5 states well after that first scan you might need all 50 states but scan again and then it would show up correct count. I don`t know if anyone else saw results like that or not but I sure did. You might just want to try that first. Another thing you do not need QSORelay with JTAlert 2.10.0 it will work with HRD version 6.XX you just need to go into the logging and select and setup JTALert to use HRD.
73 Morris WA4MIT


Re: Previous Worked B4 not being shown.

David Espasandin
 

Hi Randy:     I don't know where that is, sorry... You shouldn't need the QSO RELAY with the programs that I am using... 
HRD-6.4.0.647, WSJT-X 1.8.1, and JT Alert 2.10.0....   In fact, I've found there is some kind of feed back when using JT-65...
that is causing my radio to key... According to what I've read, this is the way to go... Over 160 qsos and they logged perfectly.. 
Hope this will help you.. Best 73  Dave KZ8Y

On Mon, Aug 7, 2017 at 9:12 PM, k5rcd <k5rcd@...> wrote:
Today I installed QSO Relay ver. 1.5 
I'm running HRD Logbook ver. 6.3.0.410
JT Alert ver. 2.10.0 and WSJTX ver. 1.8.0 - rc1.

All seems to be working properly EXCEPT, the worked B4 indicator in JT Alert is not showing up for call signs worked before today. The ones I worked today, after setting everything up, are correctly indicating if they were worked B4. I have not checked the "ignore band" or "status before this date" boxes on JT Alert Worked B4 setup.

I have done a scan and update in JT Alert, and synchronized all databases in QSO Relay. 

I've searched JT Alert settings for a screen to find where the worked B4 database is stored, to see if it needs to be changed, but cannot find that information. I clearly remember seeing it before, in case something there needs changed or updated, but just can't find it

Any help getting this corrected will be greatly appreciated.

Thanks & 73,
Randy Davis
K5RCD South Texas



Re: Previous Worked B4 not being shown.

HamApps Support (VK3AMA)
 

On 8/08/2017 11:39 AM, Morris Wideman via Groups.Io wrote:
Hi Randy look in C, users, (your computer name), AppData, local, Ham-Apps, JTAlert-X (for WSJT-X), (YOUR CALL), logs. Here you will find B4log.mdb

Hope I have that right and helps you out. but what I use to find using QSORelay was that I had to scan with JTAlert a couple or more times to get thing to work and show up. If you scan and then go back and look at the results before you click OK
and make sure that it actually scanned and add states or whatever. Cause sometimes the first scan would just not work and say on 20 meters you only needed 5 states well after that first scan you might need all 50 states but scan again and then it would show up correct count. I don`t know if anyone else saw results like that or not but I sure did. You might just want to try that first. Another thing you do not need QSORelay with JTAlert 2.10.0 it will work with HRD version 6.XX you just need to go into the logging and select and setup JTALert to use HRD.
73 Morris WA4MIT

No No No.

Editing the B4Log.mdb file will have no effect. That file is used by JTAlert ONLY when there is no logger enabled. That is why the settings for this file are not visible in JTAlert Settings as ADIF log is being used with QSORelay.

de Laurie VK3AMA
   


Re: Previous Worked B4 not being shown.

Chris VK2BYI
 
Edited

Hi Randy,

Just to be clear - Synchronise Databases should be done first in QSO Relay, followed by Scan Log and Update in JTAlert.

The sync databases process produces an updated version of the ADIF file (e.g. containing QSL/LoTW/eQSL confirmations) that can be in turn scanned by JTAlert to update your wanted alert requirements.

Thanks Laurie!

73 Chris
VK2BYI


Re: Previous Worked B4 not being shown.

k5rcd
 

Thanks to all.

Synchronizing QSO Relay and then Scan & Update of JT Alert did the trick. I am quite pleased with it all.

The reason I was concerned is that after the latest JT Alert release (v2.10.1), Laurie plans to no longer support HRD ver. 6+ and I want to get everything working now. I can't say I blame him after the antics of a certain party, formerly a principal with HRD.

I do urge Laurie to place the information about, & link to QSO RELAY on the HAM APPS page, so more folks are aware of this fine interfacing program.

73 & muchas gracias
de Randy Davis
K5RCD
South Texas (Where summer is thankfully nearing end).