Date   

Re: QSORelay Upgraded Now Double or Triple posting to HRD Log

Chris VK2BYI
 

It sounds like QSO Relay is responding to multiple UDP datagrams to log the one contact.  I don't know, but I suspect you may have to change the configuration settings in either JT65-HF and/or WSJT-X so that communications between them and the two instances of JTAlert are kept separate.

I will leave it to others more knowledgeable than me on how to setup multiple instances like this.  Maybe a post on the HamApps Support site will get you better advice than I can give.

73 Chris
VK2BYI


QSORelay Upgraded Now Double or Triple posting to HRD Log

Bob Davet
 

Just noticed this after upgrading JTAlert to version 2.10.1

I am running 2 instances of JTAlert. JtAlertX and JTAlert. Both version 2.10.1

Had the JTAlert setup and running with JT65-HF HB9HQZ (Like that program for JT65)
Just got into FT8. Using JTAlertX and WSJT-X.

Noticed that I am getting double posts and on occasion triple posts into HRD log.

This was not happening with just JTAlert and JT65-HF before I upgraded.
It has not happening with WSJT-X before I added JTAlertX. I would import the ADIF file into HRD log and there were single entries.

I am not getting any error messages.

I know that this could be a JTAlert or JTAlertX problem but wanted to bring this here first to see if anyone else had an issue like this.

Thanks

Bob
W8RID


Re: Cannot sync database

Chris VK2BYI
 

HI Karel,

Hope you are feeling better soon.

Take care.

73 Chris
VK2BYI


Re: Cannot sync database

zs6wn@...
 

Hi Chris

Sorry for the delayed reply (flu took me out of action for two days)

I am still on 664 but about to download and install the latest version of HRD.

Let me give it another try and I'll let you know.

73 de ZS6WN
Karel


Re: HRD 6.4.0.671 Logbook Logbook API Not working

Chris VK2BYI
 

Thanks for the feedback!

I am glad you find QSO Relay useful.

73 Chris
VK2BYI


Re: HRD 6.4.0.671 Logbook Logbook API Not working

Antony
 

Hi Chris,
Been trying out the latest HRD v6.4.0.777 this afternoon. All auto logging working well with JTAlert. Lots of FT8 QSOs as well as ssb and PSK logged and synced.
Thanks again for a great program. Antony G4CUS


Re: HRD 6.4.0.671 Logbook Logbook API Not working

Chris VK2BYI
 

Ham Radio Deluxe has released v6.4.0.777 which includes the fix for this defect:

 0002189: [Bug] Rig Control: "Favorites" box went missing from "Selection" bar
 0002191: [Bug] Using WSJT-X/JTAlert will no longer save to Log

73 Chris
VK2BYI


Re: Cannot sync database

Chris VK2BYI
 

Hi Howard,

No, not in particular.

It was a response to Karel's post at the very top, and if your "Email Delivery" setting under "Subscription" is set to receive "All Messages" (the default), then you receive a copy of all posts.

73 Chris
VK2BYI


Re: Cannot sync database

Howard Sidorsky
 

Hi Chris,

 

Was this email directed to me?

 

Howard – K6SID

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris VK2BYI
Sent: Wednesday, August 9, 2017 6:20 PM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] Cannot sync database

 

Hi Karel

What version of Ham Radio Deluxe are you running?  There is an issue with the latest available release v6.4.0.671 that affects logging via the Logbook API used by QSO Relay.  HRD are aware of this issue, and are working on the solution.

The defect is preventing contacts being added to the HRD Logbook, so QSO Relay 'caches' the contacts.  When you subsequently run the Database Synchronisation, it tries and fails again to 'relay cached contacts'.

If you have kept the v6.4.0.664 HRD setup file, you can roll back to that version. Otherwise, you will have to wait for the next release from HRD.

If you aren't running v6.4.0.671, then it would be helpful if you follow the steps in the Reporting an Issue post as well.  It will help us to better diagnose what is happening.

73 Chris
VK2BYI

 


Re: Cannot sync database

Chris VK2BYI
 

Hi Karel

What version of Ham Radio Deluxe are you running?  There is an issue with the latest available release v6.4.0.671 that affects logging via the Logbook API used by QSO Relay.  HRD are aware of this issue, and are working on the solution.

The defect is preventing contacts being added to the HRD Logbook, so QSO Relay 'caches' the contacts.  When you subsequently run the Database Synchronisation, it tries and fails again to 'relay cached contacts'.

If you have kept the v6.4.0.664 HRD setup file, you can roll back to that version. Otherwise, you will have to wait for the next release from HRD.

If you aren't running v6.4.0.671, then it would be helpful if you follow the steps in the Reporting an Issue post as well.  It will help us to better diagnose what is happening.

73 Chris
VK2BYI
 


Cannot sync database

zs6wn@...
 

Hi all

I'm getting this error message when trying to sync the database >> The given key was not present in the dictionary.

When I click on OK, it quickly flashes another error message about HRD Logbook not running (it is running) and being unable to relay cached contacts.

The error messages are not helping me to point me in any direction.

Where am I going wrong?

73 de ZS6WN
Karel


Re: Previous Worked B4 not being shown.

Chris VK2BYI
 

You are most welcome Randy.

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).


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.

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.

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.

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


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


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


Re: PLEASE ACTIVATE ACCOUNT

Chris VK2BYI
 

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