|
|
Post by w9mdb on Oct 8, 2023 19:58:51 GMT
Trying to work W8S.
Whenever I transmit JTDX puts EN72 in the grid location which is not only wrong...but when I change it to the correct grid AH48 JTDX changes it back to EN72 again on every transmit.
This is on 160-rc3
Mike W9MDB
|
|
|
|
Post by Wolfgang OE1MWW on Oct 9, 2023 8:17:46 GMT
in the 'CALL3.TXT' the first match of an search for 'W8S' is the call 'W8SWR' and he lives in EN72
A very strange method of the authorities to assign call signs in this variant. Requires a complete
re-work in JTDX for the lookup in the CALL3.TXT file. Surprisingly there are no other calls with an
'S' following the 'W8'.
|
|
|
|
Post by w9mdb on Oct 9, 2023 13:26:15 GMT
It's this line
if(t.indexOf(hisCall)==0) {
Instead should be doing
QStringList call3Items = t.split(',');
if (call3Items[0] == hisCall)
{
QString hisGrid = call3Items[1];
Plus...the lookup should only happen when the DXCall box is changed...not on every tranmission.
|
|
|
|
Post by Fred k1io on Oct 10, 2023 4:31:49 GMT
In the US, 1x1 call signs, like W8S, N1D, and K2R, are special event call signs. They're actually issued by third parties, including the ARRL, generally for two weeks at a time. So W8S was reserved some months ago for Swains Island, which has no prefix of its own (it's in KH8 but a separate DXCC Entity). So a match in W, K, or N not in one of the remote prefixes (like KL7, KP4 and KH8) should be on the full call sign. Of course W8S will still not show its Entity correctly since the call gets recycled often.
|
|
|
|
Post by Carlo IK6HSM on Oct 14, 2023 13:36:24 GMT
HI
the "add" command (entering the correct grid ah48)
should this solve it, or is it not correct?
Thank you
73 carlo
|
|
