<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-GB link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>I am successfully using RBN filtering on my node.</p><p class=MsoNormal>What works for me is</p><p class=MsoNormal>accept/rbn by_zone 14,15,16,20,33</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So I only see RBN spots where the spotter is in those zones.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Mike</p><p class=MsoNormal>G3YPP</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Message: 2</p><p class=MsoNormal>Date: Sun, 6 Nov 2022 14:13:45 +0000</p><p class=MsoNormal>From: Dirk Koopman <djk@tobit.co.uk></p><p class=MsoNormal>To: dxspider-support@tobit.co.uk</p><p class=MsoNormal>Subject: Re: [Dxspider-support] Possible failure in RBN filters</p><p class=MsoNormal>Message-ID: <97928a74-bc8f-36a3-30a6-28cca6fee651@tobit.co.uk></p><p class=MsoNormal>Content-Type: text/plain; charset=UTF-8; format=flowed</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It'll never work...</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Contrary to what one might reasonably think, RBN spots don't have </p><p class=MsoNormal>comments - as such - what they *do* have is *information* that </p><p class=MsoNormal>squirrelled away in the comment field, as there isn't anywhere else to </p><p class=MsoNormal>put it. I could offer a purpose built cluster friendly format that an </p><p class=MsoNormal>RBN client could use more easily use such an RBN "spot", and the spot </p><p class=MsoNormal>would not then look alarmingly a *real* DX one. But since CCCluster and </p><p class=MsoNormal>DXSpider between us have? about 85% of the nodes and 90% of the users, </p><p class=MsoNormal>have active (well fairly active) (OK alive then) maintainers and rarely </p><p class=MsoNormal>crash, seems to count for diddly squat.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>By the time an RBN Spot is presented to the filtering system, it has no </p><p class=MsoNormal>comment field. So no 'info xxx' clause will work. This is not a bug, it </p><p class=MsoNormal>is a feature. However all the normal zone, itu and similar things should </p><p class=MsoNormal>work as this information is populated into spot. Having said that, I </p><p class=MsoNormal>must confess that multiple zones probably would not work. And I also </p><p class=MsoNormal>confess that might still not do what you want and may require a separate </p><p class=MsoNormal>command ("set/rbn_byzone"?). You should also remember that neither RBN </p><p class=MsoNormal>input, nor DXSpider RBN spots are stored and (one of) the reasons is </p><p class=MsoNormal>that the "sh/dx" command, dx filtering only operate on the spot data </p><p class=MsoNormal>fields that are stored on the disk.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> From the code:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> ?? ???? ??? ? ['freq', 'r', 0, 0, \&decodefreq],</p><p class=MsoNormal> ?? ???? ??? ? ['on', 'r', 0, 0, \&decodefreq],</p><p class=MsoNormal> ?? ???? ??? ? ['call', 'c', 1],</p><p class=MsoNormal> ?? ???? ??? ? ['info', 't', 3],</p><p class=MsoNormal> ?? ???? ??? ? ['by', 'c', 4],</p><p class=MsoNormal> ?? ???? ??? ? ['call_dxcc', 'nc', 5],</p><p class=MsoNormal> ?? ???? ??? ? ['by_dxcc', 'nc', 6],</p><p class=MsoNormal> ?? ???? ??? ? ['origin', 'c', 7, 9],</p><p class=MsoNormal> ?? ???? ??? ? ['call_itu', 'ni', 8],</p><p class=MsoNormal> ?? ???? ??? ? ['call_zone', 'nz', 9],</p><p class=MsoNormal> ?? ???? ??? ? ['by_itu', 'ni', 10],</p><p class=MsoNormal> ?? ???? ??? ? ['by_zone', 'nz', 11],</p><p class=MsoNormal> ?? ???? ??? ? ['call_state', 'ns', 12],</p><p class=MsoNormal> ?? ???? ??? ? ['by_state', 'ns', 13],</p><p class=MsoNormal> ?? ???? ??? ? ['channel', 'c', 14],</p><p class=MsoNormal> ?? ???? ??? ? ['ip', 'c', 15],</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It is not possible (at the moment) to filter on quality. I can see a </p><p class=MsoNormal>reason to allow a minimum quality (>= $RBN::minqual) on a per user </p><p class=MsoNormal>basis, but that would have to be a "set/rbn_minqual" (or similar name) </p><p class=MsoNormal>command.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>73 Dirk G1TLH</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 06/11/2022 12:05, Joaquin via Dxspider-support wrote:</p><p class=MsoNormal>> Hi Dirk,</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Due to a user complaint, I have started researching RBN filters.</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> The tests have been carried out on a newly installed node where only </p><p class=MsoNormal>> RBN traffic is received.</p><p class=MsoNormal>> It is defined as register ON.</p><p class=MsoNormal>> Its version is 444.</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> *Test 1</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> EC3BH session:</p><p class=MsoNormal>> set/skim</p><p class=MsoNormal>> rej/rbn 1 info {[Z:14]}</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> No spot rx</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> EC3BH-1 Session:</p><p class=MsoNormal>> set/skim</p><p class=MsoNormal>> No filters according to sh/filter</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> No spot rx</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> * Test 2</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> EC3BH Session:</p><p class=MsoNormal>> cle/rbn all</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> rbn spots re-enters</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> EC3BH-1 Session:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> They still don't enter spots</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> * Test 3</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> I close and start session of EC3BH-1</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> RX all the spots</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> * Test 4</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> None of these filters work:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> rej/rbn 1 info {Z:}</p><p class=MsoNormal>> rej/rbn 1 info {Z:4}</p><p class=MsoNormal>> rej/rbn 1 info {Z:[45]}</p><p class=MsoNormal>> rej/rbn 1 info {Z:[4|5]}</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> But it does work:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> rej/rbn 1 info {Q:}</p><p class=MsoNormal>> rej/rbn 1 info {Q:2}</p><p class=MsoNormal>> rej/rbn 1 info {Q:[29]}</p><p class=MsoNormal>> rej/rbn 1 info {Q:[2|9]}</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> It seems that it only affects the case of "Z".</p><p class=MsoNormal>> Filters generated in <callsign> are inherited to <callsign>-<ssid> but </p><p class=MsoNormal>> do not appear when doing sh/filter or stop applying when using cle/rbn </p><p class=MsoNormal>> all</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> 73 de Kin EA3CV</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> _______________________________________________</p><p class=MsoNormal>> Dxspider-support mailing list</p><p class=MsoNormal>> Dxspider-support@tobit.co.uk</p><p class=MsoNormal>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>------------------------------</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Subject: Digest Footer</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>Dxspider-support mailing list</p><p class=MsoNormal>Dxspider-support@tobit.co.uk</p><p class=MsoNormal>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>------------------------------</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>End of Dxspider-support Digest, Vol 238, Issue 10</p><p class=MsoNormal>*************************************************</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>