Startting WinSSDR with a slice already running

  • 1
  • Question
  • Updated 4 years ago
  • Answered
Work continues apace with my homebrew Mk II controller. Here's a curiosity that I'd be grateful for view on:

Starting point: No client apps, no slices active in radio.

I now start my Mk II controller and, finding no slices in existence, it starts one (slice 0) and sets the associated frequency, panadapter average (70), FPS (15) and Weighted average (false). It also sets the waterfall gain (30). These are values that give a nice display for me. All this works as expected.

Now, I start WinSSDR. WinSSDR detects the existence of slice 0, sets frequency, bandwidth, etc. accordingly. However, the panadapter/waterfall parameters are not retained. Instead, WinSSDR starts up with pan average=0, FPS=25, waterfall gain=50.

This seems to be odd behaviour. It's also a nuisance, as this results in a display that is not nice for me! I wondered if WinSSDR was starting another pan/waterfall but it isn't - it's still slice 0's in each case.

So I am officially perplexed. I suspect a bug (feature?) in WinSSDR start-up, as I can't see how my code could have this effect. It seems to be inconsistent behaviour. Does anyone have any thoughts?


Photo of John G3WGV

John G3WGV

  • 204 Posts
  • 41 Reply Likes

Posted 4 years ago

  • 1
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 951 Posts
  • 359 Reply Likes
Official Response

It sounds like you have already figured out that creating Panadapters on different clients concurrently is not something that support (yet).  I would expect that the values that would be used on SmartSDR for Windows would be the last ones used in a GUI (due to how these settings are saved in band persistence).

At some point, I expect we will implement multi-client capabilities that will remove the single GUI client restriction.  Let us know if you have additional questions about the API and congrats on getting things going to this point.  It is indeed good fun.  :)