Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

Slice Master 6000 - aggregating spots and filtering with Logger32

Grant Kesselring
Grant Kesselring Member ✭✭
edited January 2022 in Third-Party Software

Answers

  • Andy - KU7T
    Andy - KU7T Member ✭✭
    edited January 2019
  • K1DBO
    K1DBO Member ✭✭✭
    edited January 2019
  • K1DBO
    K1DBO Member ✭✭✭
    edited January 2019
  • Grant Kesselring
    Grant Kesselring Member ✭✭
    edited January 2019
  • Grant Kesselring
    Grant Kesselring Member ✭✭
    edited January 2019
    Andy, thanks for the tip about using wintelnetX.  I will check that out.

    73,
    Grant K1KD
  • K1DBO
    K1DBO Member ✭✭✭
    edited January 2019
    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

  • Grant Kesselring
    Grant Kesselring Member ✭✭
    edited January 2019
    Perfect!  I'm getting only the filtered spots on the panadapter now.  Great program!
    73,
    Grant
  • Bernd DL9YAJ
    Bernd DL9YAJ Member ✭✭

    Last entry is 2 years ago. Now i tried nearly the same configuration than Grant but couldnt get it running. Some days ago i tried it with Slicemaster v0.10.7 without success. Two days ago i downloaded the new version v0.10.8 offered by Don, same problem!

    At the moment...Configured a localhost for slicemaster at 127.0.0.1:7285 (in L32) an the telnet aggregation server also on port 7285

    Also, I configured a telnet port to telnet cluster db0sue.de:8000 (in L32)

    Now i can see all the spots from the telnetcluster db0sue and also the WSJTX-spots in the DX-Spots window in L32, all the spots are filtered against my logbook, BUT only the WSJTX spots are displayed in the SSDR panadapter.

    At the moment i received the message "ERROR:invalid XML in N1MM UDP packet" in the protocol window of slicemaster. "send call to N1MM Logger +" in the bandmap menu is enabled. L32 UDP socket is listening on port 2237 (standard in L32). In slicemaster port 2237 is not accepted in the N1MM Logger+ menu listen, so i tried the port 12061(standard dx-spot port in L32). But no success. What is my mistake?

    73s Bernd, DL9YAJ

  • K1DBO
    K1DBO Member ✭✭✭

    Bernd,

    Please send a email to the address on the Slice Master start screen and include a zip file with your configuration and logs. It's pretty easy, just navigate to

      C:\Users\<your user name>\AppData\Local\K1DBO

    then right-click on slice-master and select 'Send to\Compressed (zipped) folder'. This will create a zip file that you can then attach to your email.

    --Don

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.