Date   
Re: JTALert V2.9.6 Problem

Morris WA4MIT
 

Over on the JTAlert yahoo group people are saying the new version 2.9.6 is having trouble saving to several different log types so it is a general problem. 

wa4mit

Re: JTALert V2.9.6 Problem

n9ru@...
 

Thanks much!

Tom

N9RU

Re: JTALert V2.9.6 Problem

Bruce VK2RT
 

Re: JTALert V2.9.6 Problem

n9ru@...
 

I have the exact same problem here, nothing was changed, just the update.

does anyone know where I can get the previous version?  It was working great here.

Thanks es 73

Tom

N9RU

Re: Sync not working on v1.2

Mike Davies <face@...>
 
Edited

I concur.  Everything was working well until the update but now I can log to HRD but after Sync the SQL Database is empty which means of course JTAlert thinks everyting is new.  Reverting to V1.1 fixes the issue.
--
Mike, G0KAD

Re: JTALert V2.9.6 Problem

Hank W6IR
 

Thanks for the link.

Re: JTALert V2.9.6 Problem

Graham G0SCV <graham@...>
 

Hi All

going back to 1.1 and 2.9.6 did not solve the problem here.

so now using 1.2 and 2.9.5

I'll try a restrat of the PC and reinstall the different veresions to see if that has any affect.

73 de Graham G0SCV


Re: JTALert V2.9.6 Problem

Graham G0SCV <graham@...>
 

Re: JTALert V2.9.6 Problem

Hank W6IR
 

Running JTAlert 2.9.6 and no problem logging. Where is JTDX 17.9.1 available for download? I can only find 17.8 which I am running.


Re: JTALert V2.9.6 Problem

Morris WA4MIT
 
Edited

I had to revert to Relay 1.1 but JTDX 17.9.1 & JTAlert 2.9.6 is functioning normally and logging to HRD 6.4.647 73 Morris wa4mit


Re: JTALert V2.9.6 Problem

Chris VK2BYI
 

Hi Graham,

 

Just as well I like fixing software then!

 

I will take you up on the offer, and I will let you know when there is something for you to try and break.

 

73 Chris

 

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Graham G0SCV
Sent: Saturday, 13 May 2017 9:01 PM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] JTALert V2.9.6 Problem

 

Thanks Chris.

Thanks for a great program :-)

If you need a beta tester then please ask, I like breaking software . . . .

73 de

Graham G0SCV

Re: JTALert V2.9.6 Problem

Graham G0SCV <graham@...>
 

Thanks Chris.

Thanks for a great program :-)

If you need a beta tester then please ask, I like breaking software . . . .

73 de

Graham G0SCV

Re: JTALert V2.9.6 Problem

Chris VK2BYI
 

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 we can’t have QSO Relay running at the same time as Log4OM and Lo4OM Communicator.

HamApps does recommend that if your preferred logger is not supported, then you should use ADIF Logging.  So, we will modify QSO Relay to work with HamApps’ recommendation.

This will take some time, so in the meantime we suggest you go back to JTAlertX 2.9.5, until we get this piece of work completed.

73 Chris
VK2BYI


Re: JTALert V2.9.6 Problem

Graham G0SCV <graham@...>
 

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

JTALert V2.9.6 Problem

Mike Davies <face@...>
 

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 V2.9.5 and all is OK.

--
Mike, G0KAD

Sync not working on v1.2

Luca Nerva
 

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 list if I resync again. All QSO are logged 100% in HRD Logbook

 

 

Some time ago I had uninstalled LOG4OM, and at the start of JTALERT I had the log error message, the only way to fix the log name was to reinstall it.

 

 

73’s de Luke IW1FZR

 

Re: Sync not working v1.2

JohnB
 

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 the record, I'm running Windows 10 Creators Update, and HRD's database is in MS Access. I'm back using v1.1 and all is working great.  Note, syncing about 5,000 records took around 2 minutes.

. . . John (WA3CAS)


Re: Sync not working on v1.2

Morris WA4MIT
 
Edited

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

2017-05-12 17:54:21.6266 Trace listener started


2017-05-12 17:54:31.7619 Synchronise databases started

2017-05-12 17:54:31.7629 Creating synchronise database lock file

2017-05-12 17:54:31.8004 Checking for cached contacts

2017-05-12 17:54:31.8004 No cached contacts

2017-05-12 17:54:31.8009 Creating HRD dataset

2017-05-12 17:54:34.3446 Refreshing SQLite

2017-05-12 17:54:34.3446 Truncating Log table

2017-05-12 17:54:34.5271 0 rows deleted

2017-05-12 17:54:34.5306 Log Table truncated

2017-05-12 17:54:34.5306 HRD Logbook contains 23321 rows

2017-05-12 17:54:34.6962 Begin transaction

2017-05-12 17:54:34.6962 Time On: 2017-05-12 01:40:00, Call: RV9CX, Band: 20m, Mode: JT65

2017-05-12 17:54:34.6982 Time On: 2017-05-11 10:15:00, Call: M0PXS, Band: 20m, Mode: JT9

2017-05-12 17:54:34.6987 Time On: 2017-05-11 10:09:00, Call: OT4R, Band: 20m, Mode: JT9

A extended long list of contacts ... then ends with this

SQLite error (2067): abort at 292 in [Insert Into [Log] ( QsoId, Address, Age, AIndex, AntAz, AntEl, Band, BandRx, Call, Comment, Cont, ContactedOp, ContestId, Country, Cqz, Distance, Dxcc, EqCall, Email, EqslQslRDate, EqslQslSDat

2017-05-12 18:29:11.3258 constraint failed

UNIQUE constraint failed: Log.Call, Log.Band, Log.Mode, Log.QsoDate, Log.TimeOn

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, TheCla

wa4mit Morris


Re: New version and DB

Antony
 

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 about 4 QSOs which were exact duplicates (how I don't know) and Relay didn't like those. When I had deleted them the sync of 65k QSOs took 1.51 minutes (elapsed time). I have now installed the latest versions of WSJT-X and JTALERT and QSOs are now being logged to the latest version of HRD.

Many Many thanks to you and the team for a great program. 73,

Antony G4CUS

Re: Sync not working on v1.2

Ian@...
 

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 have all the parts correctly configured.  I just pulled this down a few minutes ago.

Chris will be able to look at what is going on then from the trace.