Whenever CW Skimmer spots some DX it post a spot to the telnet server. There's also an option to append the slice label to the spotter's call sign. Since it's mostly just a pass through for the server in CW Skimmer, if a client works with CW Skimmer's telnet server, it has a pretty good chance of working with Slice Master's. So let me know what works and what doesnt.
I wouldnt mind putting a bit more effort into directly supporting other clients. It works well enough there, so if Slice Master's telnet server doesnt work directly with your client program, you can always put CC User in between. So far I've only tested it with VE7CC's CC User cluster client. Just point your client to the 'Start port'. So long as Slice Master stays running, it's telnet server is there.
With this server enabled, that doesnt matter. With CW Skimmer instances coming and going along with their slices, I thought it would be helpful to give logging programs and telnet cluster clients a single place to connect. The big change for this release is the addition of an aggregation server for the telnet servers in the CW Skimmer instances launched by Slice Master. It sounded like fun to me, so here you go Dave. There was another thread where Dave K3ZJ asked if it was possible to have two slices keep their frequencies in sync but maintain a 75hz offset. I've added an offset field to modify the follow frequency for any slice following the frequency of another. Slice Master 6000 v0.9.5 is now available. I was a bit short sighted when I named this thread.
0 kommentar(er)
