[Dxspider-support] Quadrupled spot

[IZ2LSC]

Normally only one spot is considered even if it is received from multiplies
nodes connected to my cluster, below an example with a "normal spot"


First spot coming in form one of my peer :

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
1717842236^(progress) SPOT: MM0ABM on 50313.0 @ 1023Z by
OM1AN(178.143.45.117)@JE3YEK 'FT8 tnx QSO GL 73!' route: G6NHU-2
1717842236^(pc11) END G6NHU-2: NORMAL PC61 key:
50313.0|MM0ABM|1717842180|OM1AN|JE3YEK finished pc11: 25753 pc61: 356669
pc11%: 6.7% pc11->pc61: 741(2.9%)

Subsequent spots coming from other peers are ignored as duplicated:

1717842237^(pc11) INPUT IK2WAD-6: PC61^50313.0^MM0ABM^ 8-Jun-2024^1023Z^FT8
tnx QSO GL 73!^OM1AN^JE3YEK^178.143.45.117^H23^~ via: IK2WAD-6 recurse: 0
1717842237^(pc11) PCPROT: Duplicate Spot  IK2WAD-6: PC61
50313.0|MM0ABM|1717842180|OM1AN|JE3YEK ignored
1717842237^(pc11) INPUT WA9PIE-2: PC61^50313.0^MM0ABM^8-Jun-2024^1023Z^FT8
tnx QSO GL 73!^OM1AN^JE3YEK^178.143.45.117^H96^~ via: WA9PIE-2 recurse: 0
1717842237^(pc11) PCPROT: Duplicate Spot  WA9PIE-2: PC61
50313.0|MM0ABM|1717842180|OM1AN|JE3YEK ignored
1717842237^(pc11) INPUT ZL2ARN-10: PC61^50313.0^MM0ABM^8-Jun-2024^1023Z^FT8
tnx QSO GL 73!^OM1AN^JE3YEK^178.143.45.117^H96^~ via: ZL2ARN-10 recurse: 0
1717842237^(pc11) PCPROT: Duplicate Spot  ZL2ARN-10: PC61
50313.0|MM0ABM|1717842180|OM1AN|JE3YEK ignored
1717842237^(pc11) INPUT 9M2PJU-2: PC61^50313.0^MM0ABM^8-Jun-2024^1023Z^FT8
tnx QSO GL 73!^OM1AN^JE3YEK^178.143.45.117^H95^~ via: 9M2PJU-2 recurse: 0
1717842237^(pc11) PCPROT: Duplicate Spot  9M2PJU-2: PC61
50313.0|MM0ABM|1717842180|OM1AN|JE3YEK ignored
1717842237^(pc11) INPUT LU4EHF-2: PC61^50313.0^MM0ABM^8-Jun-2024^1023Z^FT8
tnx QSO GL 73!^OM1AN^JE3YEK^178.143.45.117^H92^~ via: LU4EHF-2 recurse: 0
1717842237^(pc11) PCPROT: Duplicate Spot  LU4EHF-2: PC61
50313.0|MM0ABM|1717842180|OM1AN|JE3YEK ignored
1717842237^(pc11) INPUT EA4RCH-5: PC61^50313.0^MM0ABM^8-Jun-2024^1023Z^FT8
tnx QSO GL 73!^OM1AN^JE3YEK^178.143.45.117^H94^~ via: EA4RCH-5 recurse: 0
1717842237^(pc11) PCPROT: Duplicate Spot  EA4RCH-5: PC61
50313.0|MM0ABM|1717842180|OM1AN|JE3YEK ignored

Il giorno sab 8 giu 2024 alle ore 12:10 IZ2LSC <iz2lsc.andrea at gmail.com> ha
scritto:

> 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/d573d6a3/attachment.htm>