[Dxspider-support] Quadrupled spot
IZ2LSC
iz2lsc.andrea at gmail.com
Sat Jun 8 11:53:33 BST 2024
Yep,
also in this case it looks like the originating call (HA4FB) is connected
to 2 clusters (@HG8PRC, @HA2NA-1) and sending the same spot simultaneously.
Looks like the duplicate detection logic considers these 2 spots as unique
because the origin cluster is different even if in reality this is a dupe.
In fact the key is built considering the origin cluster, in my case JE3YEK
1717842236^(pc11) INPUT G6NHU-2: PC61^50313.0^MM0ABM^ 8-Jun-2024^1023Z^FT8
tnx QSO GL 73!^OM1AN^JE3YEK^178.143.45.117^H27^~ via: G6NHU-2 recurse: 0
1717842236^(pc11) PROCESSING G6NHU-2: PC61 key:
50313.0|MM0ABM|1717842180|OM1AN|JE3YEK
Andrea, iz2lsc
-->
Il giorno sab 8 giu 2024 alle ore 12:37 Kin <ea3cv at cronux.net> ha scritto:
> Here is another one:
>
>
>
> 1717796187^(progress) SPOT: JR9HET on 14051.0 @ 2136Z by HA4FB(85.90.180.26)@HG8PRC
> 'CW' route: PI4CC
>
> 1717796187^(progress) SPOT: JR9HET on 14051.0 @ 2136Z by
> HA4FB(85.90.180.26)@HA2NA-1 'CW' route: EA4URE-3
>
>
>
> I think the topology of the Network, the different capacities of the nodes
> involved, the links, the different versions of sw, ... , is the cause, but
> Dirk can clarify it better than anyone else.
>
>
>
> Kin
>
>
>
>
>
> *De:* IZ2LSC <iz2lsc.andrea at gmail.com>
> *Enviado el:* sábado, 8 de junio de 2024 12:10
> *Para:* Kin <ea3cv at cronux.net>
> *CC:* The DXSpider Support list <dxspider-support at tobit.co.uk>
> *Asunto:* Re: [Dxspider-support] Quadrupled spot
>
>
>
> Hi Kin,
>
> I don't think so, as this normally doesn't happen.
>
>
>
> Andrea
>
>
>
>
>
>
>
> -->
>
>
>
>
>
> Il giorno sab 8 giu 2024 alle ore 11:22 Kin <ea3cv at cronux.net> ha scritto:
>
> Hi Andrea,
>
>
>
> This is due to the intrinsic functioning of the network. As it is
> broadcast, it is usual to receive the same SPOT by the different
> neighbouring nodes, almost at the same instant.
>
>
>
> Regards,
>
>
>
> Kin EA3CV
>
>
>
>
>
> *De:* Dxspider-support <dxspider-support-bounces at tobit.co.uk> *En nombre
> de *IZ2LSC via Dxspider-support
> *Enviado el:* viernes, 7 de junio de 2024 21:29
> *Para:* The DXSpider Support list <dxspider-support at tobit.co.uk>
> *CC:* IZ2LSC <iz2lsc.andrea at gmail.com>
> *Asunto:* [Dxspider-support] Quadrupled spot
>
>
>
> Hi,
>
> what is the logic behind duplicate spot detection?
>
>
>
> Right now I'm receiving quadruplicate spots originated by RT5C
>
>
>
> Example below
>
>
>
> 1717787762^(progress) SPOT: HA0HV on 7011.7 @ 1916Z by
> RT5C(5.228.116.194)@EA4RCH-5 'CW' route: EA4RCH-5
> 1717787762^(progress) SPOT: HA0HV on 7011.7 @ 1916Z by
> RT5C(5.228.116.194)@VE7CC-1 'CW' route: IK2WAD-6
> 1717787762^(progress) SPOT: HA0HV on 7011.7 @ 1916Z by
> RT5C(5.228.116.194)@S50ARX 'CW' route: IR2UGI-6
> 1717787762^(progress) SPOT: HA0HV on 7011.7 @ 1916Z by
> RT5C(5.228.116.194)@W3LPL-1 'CW' route: IK2WAD-6
> 1717787762^(progress) SPOT: HA0HV on 7011.7 @ 1916Z by
> RT5C(5.228.116.194)@W9PA-4 'CW' route: G6NHU-2
>
> 1717787944^(progress) SPOT: HA6QU on 7014.9 @ 1919Z by
> RT5C(5.228.116.194)@VE7CC-1 'CW' route: IK2WAD-6
>
> 1717787945^(progress) SPOT: HA6QU on 7014.9 @ 1919Z by
> RT5C(5.228.116.194)@S50ARX 'CW' route: IR2UGI-6
> 1717787945^(progress) SPOT: HA6QU on 7014.9 @ 1919Z by
> RT5C(5.228.116.194)@EA4RCH-5 'CW' route: EA4RCH-5
> 1717787945^(progress) SPOT: HA6QU on 7014.9 @ 1919Z by
> RT5C(5.228.116.194)@W3LPL-1 'CW' route: G6NHU-2
>
>
>
>
>
> Does this mean that RT5C is logged in multiples clusters and is sending
> the same spot on all of them?
>
> How to prevent this from occurring (right now I have blocked spots
> originated by RT5C.
>
>
>
> Thanks
>
>
>
> Andrea,
>
> -->
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240608/3374fa72/attachment.htm>
More information about the Dxspider-support
mailing list