[Dxspider-support] RBN

Ron Gibson ve3cgr at sympatico.ca
Sat Jun 16 17:58:06 BST 2018


Thanks Dirk. I'll give it a try.

On 6/16/2018 8:07 AM, Dirk Koopman via Dxspider-support wrote:
> Please upgrade to the latest version in git. If you are not running a 
> version derived from the git repository then please carry out the 
> actions under the heading "Git" on this page: 
> http://www.dxcluster.org/download/
>
> Just to to repeat myself, but in other words  (I do that), do a 'git 
> pull' before you start. The instructions are located in the file 
> /spider/UPGRADE.mojo.
>
> For those wandering whether to "jump", the instructions are attached.
>
> Dirk G1TLH
>
> On 15/06/18 22:15, Ron Gibson via Dxspider-support wrote:
>> Hi Dirk,
>> Can we have a reminder as to how to switch to the mojo branch?
>> Ron
>> VE3CGR
>>
>> On 6/12/2018 6:31 PM, djk via Dxspider-support wrote:
>>>
>>> The program rbn.pl is just a simple test program that does some 
>>> deduping and a certain amount of checking. There room for 
>>> improvement, most of which could be made easier by incorporating it 
>>> into the main DXSpider code. Work which I have started doing but, 
>>> owing to personal circumstances, has had to take a back seat until 
>>> (probably) beginning of July. I have started to put some stubs in 
>>> already, but there are a number of issues that I would like to get 
>>> some guidance on - here are my current views :
>>>
>>>   * RBN spots should always be local - meaning that they are not
>>>     distributed on the cluster - this implies that each node (that
>>>     wants to handle them) will need to make a connection to the RBN.
>>>     Note: any spots ending in -# will be dropped by existing
>>>     DXSpider nodes so, in fact, it would require a network wide
>>>     upgrade to distribute them anyway.
>>>   * When the node has established a connection to the RBN, users
>>>     should have actively opt in and have a set of RBN specific
>>>     filter rules separate from the spot rules.
>>>   * Having access to all this realtime signal strength info should
>>>     allow some enhanced propagation prediction. Is anyone interested
>>>     in this sort of thing and, if so (given that the prediction is
>>>     regarded as good) how is to be used by (or communicated to) users?
>>>   * Some time ago one of my sysops wrote a program to provide
>>>     himself with SMS notifications of spots or conditions that he
>>>     was interested in using the filtered output from a connection to
>>>     a node. Given that there other means, these days, of informing
>>>     users on mobile phones that might be cheaper - should be looking
>>>     this? Twitter, Signal or some other mechanism?
>>>   * The mojo branch can be considered mature, if not "finished". Any
>>>     new features will appear on this branch which will appear,
>>>     somewhen, as DXSpider version 2.
>>>
>>> Discuss.
>>>
>>> Open to any reasonable suggestions.
>>>
>>> Dirk G1TLH
>>>
>>>
>
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20180616/a021540e/attachment.html>


More information about the Dxspider-support mailing list