Reading the S-Meter on Two Slices

  • 1
  • Question
  • Updated 3 years ago
I am trying to read the S-Meter from two slices on RXA.  I am using the two CAT commands below:

ZZSM0
ZZSM1

 ZZSM0 reads slice A just fine, but ZZSM1 seems to also read slice A instead of slice B.. I am trying to approximate the (S+N/N) by reading the S-meter on slice A (signal+noise) and the noise floor from slice B (noise) on a nearby clear frequency.  My transceiver is the 6700.  Can anyone clear up this mystery for me?  Thanks in advance.

Paul. K4HKX
Photo of Paul Casper

Paul Casper

  • 4 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9152 Posts
  • 3478 Reply Likes
See the note on the ZZSM command in the SmartSDR CAT manual.  It states...

P1 = Slice Receiver Index (0 – 7) Note:  Currently limited to RX A
Photo of Paul Casper

Paul Casper

  • 4 Posts
  • 0 Reply Likes
Tim, thank you for your response. I think I was confusing "slice receiver A" with hardware receiver A (SCU-A). Also, it is a bit confusing to label slice receivers A, B, C, etc. on the panadapter, but specify them as 0, 1, 2, etc. in the CAT commands. Anyway, I now understand only the A receiver on the panadapter can be interrogated. Hopefully this will be expanded in the future to other slices.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9152 Posts
  • 3478 Reply Likes
"Hopefully this will be expanded in the future to other slices."

It and other CAT commands will be extended to multiple slices in the upcoming SmartSDR v1.6.x release.
Photo of Peter K1PGV

Peter K1PGV, Elmer

  • 541 Posts
  • 315 Reply Likes
The Slice A vs Slice B thing versus the API or CAT commands is confusing.  SSDR labels the Slices A and B for user consumption, but IIRC this doesn't necessarily correspond to indices 0 and 1 in the API (or, presumably, in the CAT commands). Again assuming I'm remembering correctly, Slice 0 in the API is always present... it's the first slice, even if that slice happens to be labelled Slice B in SSDR (Slice A having been closed).  Hence the complexity.

Another one of the Flex API programmers, or Tim, or one of the devs, will hopefully chime-in and correct me if I'm wrong here... but that's how I recall it working.

Peter
K1PGV