Date   

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

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

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

Chris VK2BYI
 

Hi Morris,

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

73 Chris
VK2BYI


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


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


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


locked Re: QSO Relay version 1.3

Chris VK2BYI
 

Hi Graham,

Thank you Graham.

73 Chris


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
 

You are most welcome, Rick.

Thank you for your feedback.

73 Chris
VK2BYI


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

 


Re: JTAlert 2.9.7

Chris VK2BYI
 

Hi Hank,

 

Yes, we are aware of the issue with QSO Relay not working with JTAlert 2.9.7.  Version 1.2 of QSO Relay does not support Standard ADIF File and Last QSO API logging introduced in this version of JTAlert.

 

However, beta testing of QSO Relay version 1.3 has just been completed, and we will be releasing it shortly.  Version 1.3 works with the Standard ADIF File and Last QSO API logging in JTAlert in 2.9.7.

 

We will announce it when we have finished updating the documentation and have updated the download page on my web site with the new downloads.

 

73 Chris

VK2BYI


Re: JTAlert 2.9.7

Hank W6IR
 

I'm seeing a socket error with 2.9.7 and QSO relay. Also am unable to import to HRD from JT-Alert's lastqso.adi file.


Re: JTAlert 2.9.7

Chris VK2BYI
 

Yep, saw the release notes for JT-AlertX 2.9.7, and we are about to start work on that right now.

73 Chris
VK2BYI


JTAlert 2.9.7

Mike Davies <face@...>
 

Another new version has appeared which judging by the release notes might make the task of restoring the functionality of QSORelay to future updates of JTAlrrt.
--
Mike, G0KAD


Re: Sync not working on v1.2

Chris VK2BYI
 

Hi Danny,

Thank you very much.  I will certainly try!

73 Chris
VK2BYI


Re: Sync not working on v1.2

ON4VT Danny OT4V <danny@...>
 

Well this was a good motivation to clean up my HRD log !

Among my 50k+ QSO's I found about 15 duplicates ... all cleaned up and the sync is working !

Took me some time to clean up all, on the other hand it's good to have a clean up now.  If not on this I would have waste my time on something others ... lol

Keep up the good work Chris !


73 ON4VT.be Danny


Re: Sync not working on v1.2

Chris VK2BYI
 
Edited

My 100,000 QSO test database does not have duplicates, and I have been careful to avoid creating them in HRD Logbook.  But it has happened to me occasionally.  Unfortunately, HRD Logbook does not prevent duplicate contacts from being created.

QSO Relay always checks for duplicates as they are being logged into its database, and when they are being relayed, to avoid creating them in HRD Logbook.

The next release (1.3), which is being tested as I type this, will check for duplicates in HRD Logbook at the start of the sync.  If it finds any, it will add the details to the "Sync Report <datetime>.txt" file it creates during a sync in the Documents/QSORelay folder, and the sync will stop.  Users will then need to remove the unwanted duplicates, being careful to keep the best up-to-date row as the remaining contact, before attempting the sync again.

73 Chris

VK2BYI


Re: Sync not working on v1.2

Antony
 

Have you got any duplicate QSOs in your log? I found that I had 4 in mine and the sync stopped at each one. I deleted the dupe and then restarted the sync. Having done this 4 times the sync now works as it should. 73, Antony G4CUS