Replies: 7 comments 1 reply
|
In other words, you are only interested in DIGI and CW activity from the RBN. Yes, this can be done in QLog by connecting to an RBN telnet server, or another server that provides this data, and setting a filter for DIGI and CW. I’m not sure what you mean by “highlighted” in your case, but I’ll leave that up to you. |
|
Not exactly. Highlighted refers to whether the DXCC is needed (ATNO, band, mode, or slot). Normally, I am interested in all real (human) spots and in needed spots coming from RBN. However, with the skimmers I have enabled now, I get too much “noise”, although it can be filtered. For example, I can select “View only needed”. |
|
The example in the picture corresponds to my current Logger32 configuration, but I’m tired of not having profiles by QTH, etc., etc. |
|
DXSpider has nothing to do with RBN. It is purely up to the administrator whether RBN spots are injected into the output for users. That is why QLog does not have any feature to select only RBN spots. If a user wants relevant data (such as RBN), they should use a relevant DX Cluster. Pure RBN servers are listed here: https://www.reversebeacon.net/pages/Telnet+servers+30 As for filtering, there is nothing simpler in QLog than defining a DXC Filter like this.
|
|
If it is possible to filter RBN traffic, using CW skimmer or FT8 skimmer (available in DXSpider by "set/skimmer cw" or set/skimmer ft8") can be very helpful for DXing without significantly increasing the “noise” in the DXCluster window. This is just an idea. Thanks for your work! |



Uh oh!
There was an error while loading. Please reload this page.
Exist in QLog features like this:
All reactions