Operator error?

[G4DWV]

I do a lot of JT QSOs and have noticed that JTAlert is not correctly recording Wanted DXCC entities.

I have suspected that something has been amiss for a while, but do not know if it is down to operator error, an issue with JTAlert or Log4OM.

For example, saw Spain as a wanted entity on 15m JT65 today. I work it and log it via JTAlert and the QSO appears correctly in Log4OM. I then do a 'Scan Log and Update' in JTAlert. I did not notice a green bar signifying a change, and lo, Spain is showing as still needed for DXCC in JTAlert for JT65 on 15m. When I did a little deeper, I can find several instances of this by comparing my log and the JTAlert needed DXCC entities.

I have posted on the JTAlert group about this too. Any ideas?

Log4OM 1.21, JTAlert 2.6.1 on Win 7 x64.

73

[G4POP]

Is the jt65 QSO entry in Log4om complete, does it have a country name and DXCC reference?

[G4DWV]

Yes. In the particular instance I mentioned, 'Spain' is present and when I enable the DXCC column, '281' is displayed.

[G4POP]

Yes. In the particular instance I mentioned, 'Spain' is present and when I enable the DXCC column, '281' is displayed.

Have you tried closing JTAlert and re-opening it?

[G4DWV]

Yes. In the particular instance I mentioned, 'Spain' is present and when I enable the DXCC column, '281' is displayed.

Have you tried closing JTAlert and re-opening it?

I have compared the log and the JTAlert data and I have come across more instances of this that have occurred over a longer period, during which JTAlert has been closed and reopened. As per your request, I have just closed JTAlert, reopened it and done another scan of the Log4OM log without any change.

Please see attachment to see what I mean. JTAlert shows that I need Spain on 15M JT65 and below there is a 15M JT65 log entry in Log4OM.

73

[G4POP]

I could be wrong but as Log4om is recording the DXCC Country and number correctly it would seem to be a JTAlert issue

[G4DWV]

I could be wrong but as Log4om is recording the DXCC Country and number correctly it would seem to be a JTAlert issue

I'll see what Laurie says. I just posted in both places as I am ignorant as to how the two programs communicate with each other.

Thanks for your help Terry...I'll keep you posted.

[VK7XX]

I do a lot of JT QSOs

f.w.i.w., so do I.

and have noticed that JTAlert is not correctly recording Wanted DXCC entities.

and

I then do a 'Scan Log and Update' in JTAlert. I did not notice a green bar signifying a change, and lo, Spain is showing as still needed for DXCC in JTAlert for JT65 on 15m.

I have been using JTalert for a very long time and the only way that I can get it to accurately show me the correct colouring for new countries is to actually close it down after logging each contact and then re starting it again before the next contact. I find that doing it this way is actually quicker than a Scan & Update and it works.

73
John

[G4DWV]

The issue was down to my complete misunderstanding as to how JTAlert works.

JTAlert only marks an entity as needed if it has not been confirmed by LoTW, eQSL or a paper QSL card - this is configurable by the user. For it to work as I originally expected, I would have had to enable the 'No QSL confirmation (Any worked station)' option.

AS a result of this, I have decided to deselect the eQSL option from my accepted QSL methods until they are more widely accepted for awards. Only LoTW and paper QSLs will count now.

Thanks to all for their input and help.