We have identified an issue where QSO Relay is trying too soon to verify that the contact was logged after requesting HRD to log it,and not allowing enough time for HRD to actually write the contact

Please be advised that a new release of QSO Relay (Version 1.2) is now available at http://www.vk2byi.com.au/qsorelay/ We wish to thank all users for their positive feedback and patience in working

Guys thanks very much for your effort and for sharing this with the HRD community. I have installed the new version and since I was using the old version my DB was in place. Syncing had taken over an

Look in your Documents/QSORelay folder and you should see a file called "Sync Report yyyyMMddHHmmss.txt" where "yyyyMMdd" is the date and "HHmmss" is your local time when the sync was run. This file

Chris, Installed new version and everything seems to work with the logging, but when I try to sync the databases it deletes all the records in the QSOrelay db as though I did not have

Chris, Just read about the sync log, so here is mine: 2017-05-12 05:11:33.0761 Synchronise databases started 2017-05-12 05:11:33.7181 HRD Logbook contains 4890 rows 2017-05-12

There are two data paths involved - relaying JT-mode contacts from QSO Relay to HRD Logbook, and downloading all contacts from HRD Logbook to QSO Relay. The first path requires the IP Address, TCP

Rick Same issue here .... the QSOrelay DB has not declined in size though .... But when trying to DELETE a QSO via QSOrealy it shows NO QSO's The "B4" function in JTAlert also doen't see any B4

Chris, I had verified the paths and had actually read your pdf on configuring QSO Relay for Microsoft Access Database before installing the new version. My post #66 shows the log of the sync. Rick

Hi Chris I am seeing what the others that have posted the log does not show any relay rows and if I open the delete function no contacts are shown. I did not delete anything just ran the update and

I concur that sync is not working in the new version. The entire sql.lite DB was wiped out under the new version. Removed it and reinstalled 1.1 and re-synced. Everything is back in the DB. Will wait

Thanks for QSO Relay new version. Syncronization is ok. Before it was 35 minutes to syncronize and now about 15 secon 73, Clovis- PY3OG

Hank You might try turning on trace (look in the V1.2 Doc on how to turn it on) complete a sync, then turn off trace and post the trace. It should look similar to my one, this will tell you if you

Hi Chris, Having installed the new version I can say that it is working very well. All my previous problems have gone. I did put the trace on as I was getting error messages but this told me I had

Same here guys have tried everything I know to do uninstalled with Revo deleted relay DB reinstalled 1.2 still not working, verified the paths sync shows 23321 rows in HRD nothing in relay DB My

Sync is not working for me either. Syncing took about 5 seconds, but afterwards the QSO Relay database is empty. I tried uninstalling v1.1 and doing a fresh install of v1.2, but that didn't help. For

Hi, I have the same problem here, but if I do some new QSOs they appears in the list of contacts to be deleted. And they are shown also as QSO B4 in JTALERT. Naturally all contacts disappears from

Hi, Just upgraded to JTALert V2.9.6 and find that WSJTX won't log through JTALert via QSO Relay to HRD Log. The error which JTAlert gives is that Log4OM Communicator is not running. Reverted to

Same here Mike, going back to 2.9.5 restored the function, I thought I had done something wrong :-) waiting to test any ideas 73 de Graham G0SCV IO93

Hi Mike and Graham, I too can confirm the change in behavior of JTAlertX with the latest 2.9.6 release. We respect HamApps right to have JTAlertX behave as it sees fit. However, it also means that