Date   

locked QSO Relay version 1.3

Chris VK2BYI
 
Edited

Please be advised that a new release of QSO Relay (Version 1.3) is now available at http://www.vk2byi.com.au/qsorelay/

QSO Relay (v1.3) addresses the following issues:

 

  • Modified to work with JTAlertX 2.9.7 onwards using its ‘Standard ADIF File’ and ‘Last QSO API’ logging features;
  • Added HRD Logbook duplicate checking and reporting during Database Synchronisation;
  • Added more support for globalization of digit grouping and decimal symbols.

Please ensure you also download and read the latest documentation.

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

We also acknowledge and thank beta testing support from Mikko OH8EJW and Bob K1RI and others who have offered and will no doubt be used in the future.

QSO Relay users, please spread the word via other appropriate Groups and Facebook pages...

 


locked Re: QSO Relay version 1.3

Rick
 

Chris,

Updated my JTDX (17.9), JTAlert (2.9.7)and QSO Relay (1.3).  Everything seems to work just fine. Syncing worked as it should.  Looks like I can be a happy camper for awhile.

Thanks again for all your work.

Rick WB7BOW 73


locked Re: QSO Relay version 1.3

Chris VK2BYI
 

You are most welcome, Rick.

Thank you for your feedback.

73 Chris
VK2BYI


locked Re: QSO Relay version 1.3

Graham G0SCV <graham@...>
 

Great work Chris

Using JTDX 17.9.0.15

QSO Reley 1.3

JTAlertX 2.9.7

HRD 6.4.0.647

and ALL is working !!!

I'll try and not break things

73 de Graham G0SCV


locked Re: QSO Relay version 1.3

Chris VK2BYI
 

Hi Graham,

Thank you Graham.

73 Chris


New file uploaded to vk2byi-qsorelay@groups.io

vk2byi-qsorelay@groups.io Notification <vk2byi-qsorelay+notification@...>
 

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the vk2byi-qsorelay@groups.io group.

File: Configuring QSO Relay for Microsoft Access Databases.pdf

Uploaded By: Chris VK2BYI

Description:
Updated for QSO Relay v1.3

You can access this file at the URL:
https://groups.io/g/vk2byi-qsorelay/files/Configuring%20QSO%20Relay%20for%20Microsoft%20Access%20Databases.pdf

Cheers,
The Groups.io Team


Re: JTAlert 2.9.7

n9ru@...
 

I installed the new version of QSO Relay (1.3) and the newest JT Alert , using them with HRD and WSJT-X.

when logging, I get the Log 4OM Communicator not running error, but the contact is logged correctly in HRD.

Ii really appreciate this program, Thanks.


Tom

N9RU


locked Re: QSO Relay version 1.3

Mike Davies <face@...>
 

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


locked Re: QSO Relay version 1.3

Chris VK2BYI
 

Hi Morris,

Glad to hear you have it working and have de-duped HRD Logbook.

73 Chris
VK2BYI


Re: JTAlert 2.9.7

Chris VK2BYI
 
Edited

Hi Tom,

You shouldn't get the Log4OM Communicator not running error.  QSO Relay 1.3 now uses the Standard ADIF File and Last QSO API features in JTAlertX for logging - Log4OM is no longer being used.

Be sure to check your JTAlertX settings are set up as per page 9 in the QSO Relay v1.3.pdf document.

73 Chris
VK2BYI



locked Re: QSO Relay version 1.3

Morris WA4MIT
 
Edited

Chris I seem to have spoken to soon. Sorry to report that the DB is empty again this is same symptom I had with Version 1.2 I followed the full manual setup and I have again deleted everything including the config file and started from scratch and it all indicates it working the test DB function says OK the sync function does not stop or give any error msgs. When sync finishes delete a contact shows no entries. I discovered the problem when I tried to do a JTAlert log scan and everything came up 0 contacts just like starting out I backed out of this and started over with the install as mentioned but even that did not help. What am I doing wrong?

I think this is the trace file? from the exception log in the Roaming area:

2017-05-17 21:31:26.2532 ERROR System.ArgumentException: Input string was not in a correct format.Couldn't store <> in RxPwrDecimal Column.  Expected type is Decimal. ---> System.FormatException: Input string was not in a correct format.

   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

   at System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt)

   at System.Convert.ToDecimal(String value, IFormatProvider provider)

   at System.String.System.IConvertible.ToDecimal(IFormatProvider provider)

   at System.Data.Common.DecimalStorage.Set(Int32 record, Object value)

   at System.Data.DataColumn.set_Item(Int32 record, Object value)

   --- End of inner exception stack trace ---

   at System.Data.DataColumn.set_Item(Int32 record, Object value)

   at System.Data.DataRow.set_Item(DataColumn column, Object value)

   at QSORelay.Entities.SqliteLogbook.CreateNewRow(DataSet sqliteDataSet, DataRow hrdDataSetRow, IEnumerable hrdColumns)

2017-05-17 21:31:26.3052 ERROR Insert Into [Log] ( QsoId, Address, Age, AIndex, AntAz, AntEl, Band, BandRx, Call, Comment, Cont, ContactedOp, ContestId, Country, Cqz, Distance, Dxcc, EqCall, Email, EqslQslRDate, EqslQslSDate, EqslQslRcvd, EqslQslSent, ForceInit, Freq, FreqRx, GridSquare, Iota, IotaIslandId, Ituz, KIndex, Lat, Lon, MaxBursts, MsShower, MyLat, MyLon, LotwQslRDate, LotwQslSDate, LotwQslRcvd, LotwQslSent, Mode, MyCity, MyCnty, MyCountry, MyCqZone, MyGridSquare, Myiota, MyIotaIslandId, MyItuZone, MyName, MyPostalCode, MyRig, MySig, MySigInfo, MyState, MyStreet, Name, Notes, NrBursts, NrPings, Pfx, TheOperator, OwnerCallsign, Precedence, PropMode, PublicKey, ProgramId, ProgramVersion, QslMsg, QslRDate, QslSDate, QslRcvd, QslRcvdVia, QslSent, QslSentVia, QslVia, QsoComplete, QsoDate, QsoDateOff, QsoRandom, Qth, Rig, Sfi, RstRcvd, RstSent, SatMode, SatName, Sig, SigInfo, Srx, SrxString, State, StationCallsign, Stx, StxString, Swl, TimeOff, TimeOn, ValidatedCallsign, ManualDateTime, Mobile, Qrp, Portable, CallsignUrl, HomepageUrl, Contest, Cnty, AntPath, ArrlSect, ArrlCheck, TheClass, CreditSubmitted, CreditGranted, TenTen, MyAntenna, ClubLogQsoUploadDate

Log sync from Documents

2017-05-17 17:45:20.4331 Synchronise databases started

2017-05-17 17:45:23.3919 HRD Logbook contains 23386 rows

2017-05-17 17:45:34.0624 Time elapsed: 00:00:13.6292385

2017-05-17 17:45:34.0629 Synchronise databases finished

I am using the Maria DB and I believe this must have something to do with this problem but certainly not sure of that as others seem to be working and mine is not with either 1.2 or 1.3. I re-downloaded and uninstalled and installed again. I had not setup the sqlite part but now that is setup. The DB form is there but no contacts in DB. No Joy. Is anyone else using the Maria DB and getting version 1.3 to work?. Thanks Morris wa4mit 


Re: JTAlert 2.9.7

n9ru@...
 

Thanks Chris, I wasn't paying attention to the new release info.

i read the manual and all is good.

73

Tom

N9RU


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.


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

Chris VK2BYI
 

Hi Jacques,

You are most welcome.  Enjoy and good DX.

Thanks for the feedback.

73 Chris
VK2BYI


Re: JTAlert 2.9.7

Chris VK2BYI
 

Excellent.

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: 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

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


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