[Dxspider-support] ‘Bumped off by’ and HamClock

[Dirk Koopman]

The three connections at a time limit for a callsign is there for the simple reason that no one needs more than one connection for normal operation. There times during development or sysoping where one or two might be required. So, depending on some special reason that I am not aware of, I think this is a retrograde step.

IANADxer. 

Dirk G1TLH

> On 20 Apr 2025, at 01:04, Keith, G6NHU via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> 
> 
> I’m sure that if anyone watches their debug log for any period of time that you’ll see multiple instances of someone getting bumped off, reconnecting and getting bumped off again in a loop. 
>  
> This happens when more than three devices try and connect to the cluster network at the same time with exactly the same callsign.  Often people don’t even notice it because the software just silently reconnects. 
>  
> To help with this, from version 4.17, HamClock insists on an SSID as part of the cluster setup. SSIDs are treated as separate callsigns when it comes to the limit of three so this should help to reduce this bumping, disconnecting and reconnecting loop. 
>  
> If someone is upgrading from 4.16 to 4.17 and they don’t have an SSID configured, HamClock will seamlessly add one for them and for new users, it will display some text telling them they have to use an SSID and giving an example. 
>  
> 4.17 hasn’t been released yet but it should be soon. Once it hits and people start updating, the instances of being bumped off should start to reduce. 
>  
> Takeup of new versions is expected to speed up since 4.16 which introduces an automatic upgrade option. 
>  
> 73 Keith. 
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support