Joe, this has got to be either settings in your Spot Collector or user-specific settings at the clusters - if it were anything else then others would share your pain.

Try this - connect to VE7CC *using the VE7CC client*, set wide open - do you see RBN spots?

Connect to one of the clusters that is known to post RBN spots, and which you've been testing with.  Use a plain vanilla Telnet client like PuTTY.  For the sake of discussion, try  dxc.w3lpl.net port 7373.  Be sure Telnet or Raw is selected in your client - PuTTY defaults to SSH, for some reason. Sign on to the cluster, and enter "set dx filter" (no quotes, <return> at end) to clear any filters stored for your callsign.  You should see CW spots flowing rapidly, 98 percent of them from the RBN.  Each one should have a "-#" on the end of the spotter's callsign.

Now sign off and connect to the same exact Telnet server with Spot Collector.  What do you see?  If you don't see RBN spots, then it's a setting in Spot Collector.

73, Pete N4ZR
Check out the new Reverse Beacon Network
web server at <http://beta.reversebeacon.net>.
For spots, please use your favorite 
"retail" DX cluster.

On 12/29/2021 10:42 AM, Joe WB9SBD wrote:

Hi All,

I'm taking this out to the masses here in Hope someone here has also ran into this problem and fixed it.

Dave has been incredible spending a LOT of time in direct E-Mails to me working on this.
But I think what is happening to me here has even stumped him.

I can not seem to get spots into Spot Collector. The Clusters work with other programs. But Spot Collector just doesn't get the spots.

I have spot collector set to use three clusters AND the direct feed from the RBN.

But Now from all the messages here lately I am not supposed to do this, connect directly to the RBN.

But NONE of the clusters are passing the RBN spots into my Spot collector.

And YES all three are set for set/skimmer One that truly amazes me one is the mighty VE7CC one.

To show how this is NOT working I made this video and experiment.

I set up the RBN web site at the left, The web page that displays the RBN spots.
Then,
the telnet window from N1MM to the right of that web page display. n1mm is using the ve7cc cluster for it's info.

And then three of the windows from SC. one is even VE7CC with the exact same logging in parameters. except for the call in SC I used my wb9sbd and in n1mm I use w9et to log into Ve7CC so it does not see the same call logging in twice.

OK I sent out a short CQ on 40 meters

CQ CQ CQ CQ DE W9ET W9ET K

and you will see what happens.

N1MM is populated almost immediately with the W9ET calling cq, remember that's connected to VE7CC

next you see W9ET appears in the RBN web page, and it may have found W9ET sooner but had to wait for the page refresh.

Notice to the right all three of the dx clusters, for SC. never display W9ET.

There are a few spots for the RBN showing up in Some of the SC windows (-#) seen. but no where near the amount that the N1MM window is seeing. And the VE7CC one is all but dead in SC. Why?

This is what is always happening.  if I have the SC get the direct fed from the RBN then w9ET appears. but via the clusters, nothing, yet we see via n1mm and ve7cc it surely is being heard by ve7cc.

Here is the video.

https://youtu.be/LrouMsP518A

Anyone have any suggestions what might be happening?
Joe WB9SBD

How do I prevent NCDXF beacon spots from being shown in Spot Collector? I have added B, BCN, BEACON, and NCDXF under the Special Callsigns tab but every couple of minutes I'm getting the 4U1UN beacon again. Obviously I need to have 4U1UN as a legitimate spot when the station is active, but not for the beacon. Please and thanks.

Hello folks.  I am trying to install Launcher on a Dell Windows 11 laptop so that I may load the other suite apps.  What follows is the process and results.

1.  Download Launcher from http://www.dxlabsuite.com/download.htm
2.  Run the installation program as instructed and did not change any file locations. 
3.  After install completes, launching the program (Launcher) results in  a short delay while the program loads.
4.  After a moment MS UAC pops up and wants to know if I want to allow 'Launcher' to make changes to this computer and I say "yes"
5.  No launcher window appears.  If  I double click on the Icon it says "Launcher is already running on this machine"
6.  The app was installed using ADMINISTRATOR privilege's.
7.  The app is being run using administrator privilege's.
8.  I have killed the app numerous times using task manager and tried different things like running in compatibility mode etc. all to no avail.  Same results.

Thanks in advance.

Joe K8FC

Joe, this has got to be either settings in your Spot Collector or user-specific settings at the clusters - if it were anything else then others would share your pain.

Try this - connect to VE7CC *using the VE7CC client*, set wide open - do you see RBN spots?

Connect to one of the clusters that is known to post RBN spots, and which you've been testing with.  Use a plain vanilla Telnet client like PuTTY.  For the sake of discussion, try  dxc.w3lpl.net port 7373.  Be sure Telnet or Raw is selected in your client - PuTTY defaults to SSH, for some reason. Sign on to the cluster, and enter "set dx filter" (no quotes, <return> at end) to clear any filters stored for your callsign.  You should see CW spots flowing rapidly, 98 percent of them from the RBN.  Each one should have a "-#" on the end of the spotter's callsign.

Now sign off and connect to the same exact Telnet server with Spot Collector.  What do you see?  If you don't see RBN spots, then it's a setting in Spot Collector.

73, Pete N4ZR

Check out the new Reverse Beacon Network

web server at <http://beta.reversebeacon.net>.

For spots, please use your favorite 

"retail" DX cluster.

Hi All,

I'm taking this out to the masses here in Hope someone here has also ran into this problem and fixed it.

Dave has been incredible spending a LOT of time in direct E-Mails to me working on this.
But I think what is happening to me here has even stumped him.

I can not seem to get spots into Spot Collector. The Clusters work with other programs. But Spot Collector just doesn't get the spots.

I have spot collector set to use three clusters AND the direct feed from the RBN.

But Now from all the messages here lately I am not supposed to do this, connect directly to the RBN.

But NONE of the clusters are passing the RBN spots into my Spot collector.

And YES all three are set for set/skimmer One that truly amazes me one is the mighty VE7CC one.

To show how this is NOT working I made this video and experiment.

I set up the RBN web site at the left, The web page that displays the RBN spots.
Then,
the telnet window from N1MM to the right of that web page display. n1mm is using the ve7cc cluster for it's info.

And then three of the windows from SC. one is even VE7CC with the exact same logging in parameters. except for the call in SC I used my wb9sbd and in n1mm I use w9et to log into Ve7CC so it does not see the same call logging in twice.

OK I sent out a short CQ on 40 meters

CQ CQ CQ CQ DE W9ET W9ET K

and you will see what happens.

N1MM is populated almost immediately with the W9ET calling cq, remember that's connected to VE7CC

next you see W9ET appears in the RBN web page, and it may have found W9ET sooner but had to wait for the page refresh.

Notice to the right all three of the dx clusters, for SC. never display W9ET.

There are a few spots for the RBN showing up in Some of the SC windows (-#) seen. but no where near the amount that the N1MM window is seeing. And the VE7CC one is all but dead in SC. Why?

This is what is always happening.  if I have the SC get the direct fed from the RBN then w9ET appears. but via the clusters, nothing, yet we see via n1mm and ve7cc it surely is being heard by ve7cc.

Here is the video.

https://youtu.be/LrouMsP518A

Anyone have any suggestions what might be happening?
Joe WB9SBD

Hi All,

I'm taking this out to the masses here in Hope someone here has also ran into this problem and fixed it.

Dave has been incredible spending a LOT of time in direct E-Mails to me working on this.
But I think what is happening to me here has even stumped him.

I can not seem to get spots into Spot Collector. The Clusters work with other programs. But Spot Collector just doesn't get the spots.

I have spot collector set to use three clusters AND the direct feed from the RBN.

But Now from all the messages here lately I am not supposed to do this, connect directly to the RBN.

But NONE of the clusters are passing the RBN spots into my Spot collector.

And YES all three are set for set/skimmer One that truly amazes me one is the mighty VE7CC one.

To show how this is NOT working I made this video and experiment.

I set up the RBN web site at the left, The web page that displays the RBN spots.
Then,
the telnet window from N1MM to the right of that web page display. n1mm is using the ve7cc cluster for it's info.

And then three of the windows from SC. one is even VE7CC with the exact same logging in parameters. except for the call in SC I used my wb9sbd and in n1mm I use w9et to log into Ve7CC so it does not see the same call logging in twice.

OK I sent out a short CQ on 40 meters

CQ CQ CQ CQ DE W9ET W9ET K

and you will see what happens.

N1MM is populated almost immediately with the W9ET calling cq, remember that's connected to VE7CC

next you see W9ET appears in the RBN web page, and it may have found W9ET sooner but had to wait for the page refresh.

Notice to the right all three of the dx clusters, for SC. never display W9ET.

There are a few spots for the RBN showing up in Some of the SC windows (-#) seen. but no where near the amount that the N1MM window is seeing. And the VE7CC one is all but dead in SC. Why?

This is what is always happening.  if I have the SC get the direct fed from the RBN then w9ET appears. but via the clusters, nothing, yet we see via n1mm and ve7cc it surely is being heard by ve7cc.

Here is the video.

https://youtu.be/LrouMsP518A

Anyone have any suggestions what might be happening?
Joe WB9SBD

> 1. refuse to directly connect to telnet.reversebeacon.net as a spot source I really wish you wouldn't do this. Perhaps make it a warning, or provide some override option. I don't need nanny software stopping me from doing something that maybe "shouldn't be done". 73 de KM8V Jon

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Jon KM8V via groups.io
Sent: Wednesday, December 29, 2021 15:27
To: DXLab@groups.io
Subject: Re: [DXLab] an analysis of Remote Beacon Network (RBN) spots and their impact on SpotCollector's performance

> 1. refuse to directly connect to telnet.reversebeacon.net as a spot source

I really wish you wouldn't do this. Perhaps make it a warning, or provide some override option.

I don't need nanny software stopping me from doing something that maybe "shouldn't be done".

73 de KM8V Jon