Slice Master 6000 - aggregating spots and filtering with Logger32

  • 1
  • Question
  • Updated 5 months ago
Can someone help me with some Slice Master 6000 settings?  What I would like to do is aggregate my own CW Skimmer, WSJT spots along with spots from telnet DX cluster.  Then, I would like to pass all those spots to Logger32 so they can be cross-checked against my log for filtering/coloring based on need.  Finally, I would like to pass the filtered spots back to SmartSDR panadapter. 

I'm running:
SmartSDR v2.4.9
Flex6600M
SliceMaster 6000 v0.10.5h
Logger32 3.50.377

Here are my current Slice Master 6000 settings:




At this point, WSJT or CW Skimmer is running and decoding calls.  I've specified a Telnet spot source and WSJT and enabled aggregation server port 7300.  The last step is configuring Logger32 to communicate with the aggregation server, but I do not know exactly how to do this in Logger32 Telnet window.  I tried setting up a telnet connection like this so that the port matches with the aggregation server port 7300:


This brings all the cwskimmer/wsjt spots into the Telnet window in Logger32, however I am not getting any cluster telnet spots.  What am I missing?

73,
Grant K1KD

Photo of Grant Kesselring

Grant Kesselring

  • 9 Posts
  • 0 Reply Likes

Posted 5 months ago

  • 1
Photo of Andy - KU7T

Andy - KU7T

  • 243 Posts
  • 24 Reply Likes
I am not sure if SliceMaster can do this but you need to merge the two spot feeds into one before you connect with your logging program.

I use wintelnetX for this. In my case it merges external telnet cluster and my local spots coming from SliceMaster (which could merge spots from multiple slices) into one feed. Create yourself a config file for WintelnetX and you never have to set anything up. I even launch it from a batch script, so its all automatic.

73
Andy
KU7T
Photo of Grant Kesselring

Grant Kesselring

  • 9 Posts
  • 0 Reply Likes
Andy, thanks for the tip about using wintelnetX.  I will check that out.

73,
Grant K1KD
Photo of K1DBO

K1DBO

  • 532 Posts
  • 111 Reply Likes
Grant,

Your Slice Master setup looks right.  In Logger32, have you enabled the UDP spot broadcast?  The option is on a right click menu in Logger32's DX Spots window.

--Don
Photo of K1DBO

K1DBO

  • 532 Posts
  • 111 Reply Likes
Grant,

I think I missed your question, and that Andy got it.

Logger32 can read spots from more than one source. In the Cluster window, you have already added Slice Master as a source.  I usually put it on the 'localhost' tab and use the 'telnet' tab to connect to the cluster.  Logger32 will then display spots from both the cluster and from Slice Master.  If Logger32's UDP spot broadcast is also enabled and if Slice Master is also listening for those broadcasts via the N1MM+ settings, all should be well.

Andy's suggestion of using wintelnetx will also let you connect to both Slice Master and the cluster at the same time and then let Logger32 connect to it.  I use VE7CC's CCUser program for the same purpose.

The next release of Slice Master will support an option to combine it's internally collected spots with the spots that it gathers from its external spot sources.  For now though, you'll either need to configure Logger32 for both the cluster and Slice Master or use a second program to combine the sources.

--Don

Photo of Grant Kesselring

Grant Kesselring

  • 9 Posts
  • 0 Reply Likes
Don,

Thanks for your feedback.  As you pointed out, Logger32 can combine the locally generated spots with the cluster spots.  When I configured the 'telnet' tab to connect to the cluster and the 'localhost' tab to connect to Slice Master, I am now receiving spots from two slices of CW skimmer plus cluster spots into Logger32.  Neat!

The thing that was tripping me up was the concept of the aggregation server in Slice Master.  I assumed that it was aggregating all internal AND external spots.

I apply some filtering to the spots once they are in Logger32.  I've enabled the UDP spot broadcast in Logger32 and enabled 'Listen for N1MM Logger+ Broadcasts' in Slice Master.  Do I understand correctly that calls displayed in SmartSDR panadapter will be only those that have been filtered by Logger32 filter settings?  That is what I'm hoping it will do.

Thanks, Grant
Photo of K1DBO

K1DBO

  • 532 Posts
  • 111 Reply Likes
Grant,

When I first implemented the aggregation server all spots were internal. There were no external spot sources.  Later, with the bandmap overlays and then Flex's spot API, it was pretty clear there was a need for external spot sources too.  I was a bit concerned about spots coming in from a logger then going back out the aggregation server to a logger that then sent them back in again.  So... only sending out the "internal" spots seemed like the right thing to do. 

Now of course, folks trying to cut down on using third party programs, are asking why have two spot aggregators? Why doesnt Slice Master send all the spots out the aggregation server.  I've eliminated the looping issue, so now it will (next release).

Normally, Slice Master will first display the spots and then send them out the aggregation server.  If Logger32 sends the spot back in, Slice Master will re-display it with color and possibly other information added.  If Logger32 is filtering the spots and not sending all of them back to Slice Master and you would prefer to only see the spots that Logger32 sends back, uncheck the 'Show internal spots' option in the Bandmap section of Slice Master's setting tab.  With that option disabled, you'll only see the spots that Logger32 sends in.

--Don
Photo of Grant Kesselring

Grant Kesselring

  • 9 Posts
  • 0 Reply Likes
Perfect!  I'm getting only the filtered spots on the panadapter now.  Great program!
73,
Grant