[Dxspider-support] Connect SKIMMER sk0mnr & sk1mnr

[Danilo Brelih]

Laurent-F4BWT via Dxspider-support je 19.2.2025 ob 19:58 napisal:


Read RBN.mojo at /spider

.....

So how do you go about using this:

First you need to create one or two RBN user(s). Now you can use any call you
like and it won't be visible outside of the node. I call mine SK0MMR
and SK1MMR. One of these connects to the "standard" RBN port that
outputs CW, BEACON, DXF, PSK and RTTY spots, and the other connects to
the RBN port that just outputs FT4 and FT8 spots.

set/rbn sk0mmr sk1mmr

Now create connect scripts in /spider/connect/sk0mmr (and similarly
sk1mmr). They look like this:

/spider/connect/sk0mmr:

connect telnet telnet.reversebeacon.net 7000
'call:' '<node callsign here'

/spider/connect/sk1mmr:

connect telnet telnet.reversebeacon.net 7001
'call:' '<node callsign here'

Now put them in your local crontab in /spider/local_cmd/crontab:

* * * * * start_connect('sk0mmr') unless connected('sk0mmr')
* * * * * start_connect('sk1mmr') unless connected('sk1mmr')

This will check once every minute to see if each RBN connection is
active, you can check what is connected with the 'links' command:

                                                  Ave  Obs  Ping Next      Filters
   Callsign Type Started                 Uptime    RTT Count Int. Ping Iso? In  
Out PC92? Address
     GB7DJK DXSP  5-Jul-2020 1722Z     7h 6m 8s   0.02   2 300    
89               Y    163.172.11.79
     SK0MMR RBN   5-Jul-2020 1722Z     7h 6m 8s 0     0                    
198.137.202.75
     SK1MMR RBN   5-Jul-2020 1722Z     7h 6m 8s 0     0                    
198.137.202.75

The RBN connections are sometimes dropped or become stuck. I have a
mechanism to detect this and it will disconnect that RBN connection
and, by this means,it will be automatically reconnected by the
crontab, just like any other (normal) node.

I use the crontab, rather than restarting immediately after
disconnection, to prevent race conditions (or just slow them down to
one disconnection a minute).

The first time a connection is made, after node startup, there is a 5 (configurable)
minute pause before RBN spots come out for users. This is done to fill
up (or "train") the cache. Otherwise the users will be overwhelmed by
spots - it slows down reasonably quickly - but experiment shows that 5
minutes is a reasonable compromise. The delay is configurable,
globally, for all RBN connections, but in future is likely to be
configurable per connection. Basically, because the FTx RBN data is
much more bursty and there is more of it (except on CW contests), it
could do with a somewhat longer training period than the CW etc RBN
connection.

If a connection drops and reconnects. There is no delay or extra
training time. If the node is stopped and restarted within a few
minutes, then no training time will occur.




> Hi All,
>
> How to connect RBN SKIMMER on DXSPIDER ?
> I have this information
>
> IP for SKIMMER :
>
> 44.52.120.51
>
> 44.10.10.51
>
> telnet.reversebeacon.net
>
> And port is 7000 and 7001
>
> Can you help me to connect sk0mnr and sk1mnr ?
>
> Thanks for your answer.
>
> 73 51 QRO Laurent F4BWT
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support


-- 
S50CLX DX Cluster <https://s50clx.infrax.si>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250219/fb475a4a/attachment.htm>