Page 1 of 1
Posted: 05 Mar 2013, 17:10
When I log a QSO with TX5K I get callsign is not valid, but it sees it as Clipperton Isl
I updated the SCL and Country files yesterday
Posted: 05 Mar 2013, 17:32
This has been noticed and noted. It is not an error.
What it it saying is "The prefix TX is not in the Country file". And, it's absence is by design as the TX prefix can be in many different locations. Same goes for the TO series prefixes and several others.
The TX5K is in the SCL file and resolves to Clipperton Is. as it should.
In my opinion, the message should say something like "User should check for correct country before logging"
Posted: 05 Mar 2013, 17:45
This issue is related to a prefix not listed in any country, due the possibility to be assigned to multiple DXCC. Never happened before, but could happen again in the future.
Will be fixed in the next release.
Posted: 06 Mar 2013, 00:37
Thanks for the info guys,
I hope to see that box pop up many more times in the next few days but it's hard work,
Posted: 06 Mar 2013, 09:05
An update to the Log4OM country file has been issued effective Mar 03, 2013 which will solve this issue for the time being. Users should update their country file.
Posted: 21 Oct 2017, 19:03
TX5JF is showing up now as Clipperton instead of French Polynesia.
He's in the SCL file but it shows "Concluded Operations".
The debug log shows French Polynesia but apparently some check is overriding that?
de Mike W9MDB
Posted: 22 Oct 2017, 07:48
The information we have is that the operation, TX5JF, concluded on Aug 31, 2017.
With the TX series prefix being assigned to more then one entity and the call not active, it defaults to Clipperton.
Same goes for the TO (Tango Oscar) series.