[Dxspider-support] Understanding propagation of node controls

[Keith, G6NHU]

I believe that the command set/var $Spot::minselfspotqrg 0 only controls what is accepted on the local node and not what’s received via the network.

So if you were connected to Keith's node that had $Spot::minselfspotqrg at the default value of 1240000, it would only allow you to self spot yourself above 23cms but that doesn’t affect network spots.  So if I were to self spot on [say 40m] via a different node, my spot would still be displayed on Keith’s node.

73 ‘NHU

On 14 Feb 2025 at 11:55 +0000, Ciemon Dunville via Dxspider-support <dxspider-support at tobit.co.uk>, wrote:
> I've been pondering the setup of a node here, and taking my time to understand what benefit I might bring rather than just adding to the mesh.
>
> The comment this morning by Keith about self-spotting not being wanted locally has me wondering what effect that has on connected nodes. Does Keith's node prevent the flow of self-spots to other connected nodes, or is it just his own nodeI?
>
> I'm curious because Parks On The Air now has a cluster of nodes that absolutely embraces self-spotting and I want a better understanding. Which then leads me onto thinking about support for QRP ops, who might need another cluster of nodes (perhaps) to enable them to self spot (very weakly)
>
> 73, Ciemon
>
> ---
> Ciemon Dunville - GØTRT
> Warminster, Wiltshire. UK
>
> _______________________________________________
> 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/20250214/d7b7c3a6/attachment.htm>