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
Thanks
Trevor
TX5K
Re: TX5K
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"
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"
K7PT-Chuck "#1 Top of the Honor Roll"
- IW3HMH
- Site Admin
- Posts: 2926
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: TX5K
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.
73
Daniele
Will be fixed in the next release.
73
Daniele
Daniele Pistollato - IW3HMH
Re: TX5K
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.
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.
K7PT-Chuck "#1 Top of the Honor Roll"