[Dxspider-support] Failure in cty.dat?

[Jim Reisert AD1C]

Kin, I think if the DX spot comes in with the wrong number, then DX
Spider does not change it.  The CTY file is only used when a user is
making a DX spot from that node.  At least that is my understanding.
So the spotters are using a DX cluster node with an outdated country
file.


On Mon, May 2, 2022 at 12:14 PM Kin via Dxspider-support
<dxspider-support at tobit.co.uk> wrote:
>
> Hi Dirk,
>
> I've been seeing for a while that some callsigns are shown with the wrong entity number, although in the cty.dat they are correctly assigned.
> I have looked at the code and I think you are using the information from cty.dat to assign the entity number.
>
> Here is an example where you can see the entity that arrives in the spot and the one that should appear:
>
> 2022-05-02-02T08:27:33 - KG6JDX: 226 -> 107
> 2022-05-02-02T08:27:56 - RP77AB: 179 -> 182
> 2022-05-02-02T11:12:22 - WB4JTT: 226 -> 112
> 2022-05-02-02T13:04:04 - R9MA/1: 182 -> 179
> 2022-05-02-02T17:11:28 - K2GT: 226 -> 112
> 2022-05-02-02T17:43:19 - W5ERV: 226 -> 117
>
> Could you tell me if it's normal that it doesn't update them?
>
> Regards,
>
> Kin
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support



-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us