[Dxspider-support] Skimmer "QRG likely wrong"?

[Frank Grossmann DL2CC]

Hi all, hi Dirk,

trying to connect to a Skimmer directly, which now (thanks Dirk for adding the mode) work in theory I have a problem with a new skimmer node.

First, I do a
SET/RBN DL0XXX

Connecting to that skimmer works, but no spots are forwarded to the users.

Using SET/DEBUG RBN, SET/DEBUG RBNRAW, SET/DEBUG RBNSKIM I get:

1745664786^(*) RBN: noinrush: 1, setting inrushpreventor on DL0XXX to 0
1745664786^(rbnraw) RBN:RAW,
1745664786^(rbnraw) RBN:RAW,DL0XXX de SKIMMER 2025-04-26 10:52Z CwSkimmer >
1745664786^(rbnraw) RBN:RAW,
1745664795^(rbnraw) RBN:RAW,DX de DL0XXX -#:    7030.1  DF4HI           9 dB  38 WPM  CQ            1052Z
1745664795^(rbnraw) RBN:processing RAW,DX de DL0XXX -#:    7030.1  DF4HI           9 dB  38 WPM  CQ            1052Z
1745664795^(*) RBN: inserted CW for missing mode
1745664795^(rbn) RBN:input decode or:DL0XXX qr:7030.1 ca:DF4HI mo:CW s:9 m:dB sp:38 u:WPM sort:CQ t:1052Z tx: qra:
1745664795^(rbn) RBN: key: 'DF4HI|70301' call: DF4HI qrg: 7030.1 NEW
1745664795^(rbn) RBN: key: 'DF4HI|70301' ADD RECORD call: DF4HI qrg: 7030.1 origin: DL0XXX respot: 0
1745664795^(rbnskim) RBN:SKIM cand 0 QRG likely wrong from 'DF4HI|70301' = DF4HI on 7030.1 by DL0XXX @ 1052Z (qrgs: 7030.1=>-5,  c: 1) route: DL0XXX, ignored


Please note the "RBN:SKIM cand 0 QRG likely wrong from" - this is what stops the spot from any further processing.
What does that mean?

When I use another skimmer node which I had been using for a while, processing continues and everything is as expected.
Looking at the debug log I cannot determine any difference when I compare the spots.

Is there a trust level one can set per skimmer node?


Thanks
73
Frank

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250426/cfc5be53/attachment.htm>