Page 2 of 3
Re: Call sign challenge
Posted: 15 Aug 2019, 11:24
by KD0ZV
Yes, that worked!
Thank you
- 2019-08-15_6-23-02.jpg (153.98 KiB) Viewed 6705 times
Re: Call sign challenge
Posted: 17 Nov 2019, 21:39
by KD0ZV
Having the Clipperton Island deal again. This time as TX7t
Does not show up correctly in the cluster but does show up in the details above. I have worked them 5 or 6 times on various bands/modes and was correct until today
Another local ham is having same issue. All the databases are updated and club-log exception is on. Using QRZ for lookup
Any idea?
Rich
Re: Call sign challenge
Posted: 18 Nov 2019, 00:13
by G4POP
As we have said a couple of times the cluster only does a quick check against the country database for the call whereas when the call is entered into the call sign entry field a full lookup[ of all sources both online and off line so that is going to be the most accurate all of the time.
In version 2 the system is very different so these anomalies will not occur so often
Re: Call sign challenge
Posted: 18 Nov 2019, 00:24
by KD0ZV
OK,
Well the lookup is OK as it puts it in the country (F2) area. Just the cluster.
So hopefully version 2 will fix it
Re: Call sign challenge
Posted: 18 Nov 2019, 17:04
by w9mdb
TX7T does not show up correctly here. I've updated all the databases and restarted Log4OM.
I also tried logging it (from WSJT-X) and it does get inserted correctly as JTAlert does the DXCC lookup...but still the F2 tab in Log4OM shows Clipperton.
I tested with a friend and his shows correctly on the F2 tab. We thought maybe logging it would make a difference but it doesn't (even after a restart).
The clublog.xml does show TX7T correctly.
So how do I figure out why this is wrong? The debug info only shows the log lookup and nothing else.
Re: Call sign challenge
Posted: 18 Nov 2019, 17:38
by KD0ZV
Mike, I am guessing since they are so close to Version 2 which apparently is all different they are not going to be putting any effort into fixing this. I personally think its a Log4om issue but I am not concerned since V2 is just around the corner.
Its a big hassle for me because TX7T switched in the middle and then I could not longer look at the Statistics because It no longer showed bands/modes worked. It was empty because it was looking at Clipperton Island and not Marquesas Islands.
Re: Call sign challenge
Posted: 19 Nov 2019, 16:37
by G4POP
Re: Call sign challenge
Posted: 19 Nov 2019, 16:44
by G4POP
w9mdb wrote: ↑18 Nov 2019, 17:04
TX7T does not show up correctly here. I've updated all the databases and restarted Log4OM.
I also tried logging it (from WSJT-X) and it does get inserted correctly as JTAlert does the DXCC lookup...but still the F2 tab in Log4OM shows Clipperton.
I tested with a friend and his shows correctly on the F2 tab. We thought maybe logging it would make a difference but it doesn't (even after a restart).
The clublog.xml does show TX7T correctly.
So how do I figure out why this is wrong? The debug info only shows the log lookup and nothing else.
1. Do you have the Settings 1 options as shown below?
- Capture.JPG (20.16 KiB) Viewed 6340 times
2. Are you using version 1 release 1.40?
Re: Call sign challenge
Posted: 19 Nov 2019, 16:49
by KD0ZV
In my case I am running 1.40.
Only difference in mine is I do not have Fill Data using previous QSO or Realtime Previous QSO checked.
Re: Call sign challenge
Posted: 19 Nov 2019, 17:04
by G4POP
kd0zv wrote: ↑19 Nov 2019, 16:49
In my case I am running 1.40.
Only difference in mine is I do not have Fill Data using previous QSO or Realtime Previous QSO checked.
That shouldn't make a difference because the country is a new one in the log I am using