Date
1 - 3 of 3
locked Odd happenings
|
Hi Laurie and the group,
Since updating to the latest version of JTAlert (2.16.15) I've noticed one small oddity in the behavior of JTA when working a previously worked call. It used to bring up the name, QTH and grid of a call worked on other bands, but with this latest version, if that call was worked on - say RTTY - since the previous FT8 contact, it does not automatically fill in the name and QTH, but sometimes does bring up the grid, if it was matched on LoTW. For example, I had worked Chad WE9V on many bands in FT8 previously (80/40/30/20/17, but not 15m) and when I saw him on 15m today, I gave him a call, but since I worked him on RTTY the last time, it failed to bring up his name and QTH, even though we had previously worked on FT8. I don't see any mention of this in the release notes, so maybe it is a bug, or is it me? I'm running the latest version of DXKeeper, and logging is working fine, as is the lookup of previous contacts. 73 de Phil GU0SUP
|
|
|
|
Paul
Hi, I am also running JTAlert 2.16.15 and DXKeeper 15.8.9. On checking JTAlert Settings> Manager Settings > Logging---Logging options "Do not lookup previous qso data from logbook" is UN TICKED.The same problem of QRZ information not being file in from previous QSO"S Is happening. Paul G4YKQ.
|
|
|
|
Dave Garber
i thought lookups were done via a qrz key, within jtalert Dave Garber VE3WEJ / VE3IE
Hi Laurie and the group,
|
|
|