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

[Kin]

But they are not different: call, call-1, call-2, ... call-N. Each will have 3 possible sessions, for a total of N*3.
 
Kin EA3CV
 
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Keith, G6NHU via Dxspider-support
Enviado el: domingo, 20 de abril de 2025 14:07
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: Keith, G6NHU <g6nhu at me.com>
Asunto: Re: [Dxspider-support] ‘Bumped off by’ and HamClock
 
I disagree.

1) Normal logger
2) DX Cluster software, like CC User or FL Cluster
3) Contest logger
4) HamClock

That’s four I can think of from the top of my head which could be running at the same time.  I know quite a few amateurs with more than one HamClock running to display different things on the available panes.  I’ve got three here, one is my general one, one is a self monitor and I have one running which is used to create a daily timelapse.  All three have cluster connections.

Some software doesn’t notify the user when the connection drops and reconnects.   By forcing one of the above for examples to use an SSID, this reduces the chance of bumping and reconnecting.

IAADxer.

73 Keith.
On 20 Apr 2025 at 12:31 +0100, Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk>, wrote:


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

_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250420/135cb4d5/attachment-0001.htm>