SSB peak control

  • 2
  • Question
  • Updated 8 months ago
"SSB Peak control"  I have heard this talked about and even see this as a selection in the "Stacks for Flex" application.  Can someone give me some details on this and how to enable it on the flex not using the "Stacks for Flex"?
Photo of N3NER

N3NER

  • 186 Posts
  • 24 Reply Likes

Posted 8 months ago

  • 2
Photo of Michael Walker

Michael Walker, Employee

  • 321 Posts
  • 84 Reply Likes
Can you provide more information?  Links to articles, etc?

Are you confusing this with Controlled Envelope Single Side Band? (CESSB) which gives you an extra effective 2.5db output in SSB mode thanks to no ALC overshooting.

Mike
Photo of Steven Linley

Steven Linley

  • 240 Posts
  • 27 Reply Likes
CESSB would be another Flex game changer
Photo of Joe  N9VX

Joe N9VX

  • 40 Posts
  • 7 Reply Likes
It already has CESSB.
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2965 Posts
  • 644 Reply Likes
That is correct I believe CESSB is built into the Proc, looks like they have changed the game...
Photo of Steve - N5AC

Steve - N5AC, VP Engineering / CTO

  • 1031 Posts
  • 1002 Reply Likes
We actually use a modified version of CESSB that has some enhancements over the original design, FYI
Photo of Gary NC3Z

Gary NC3Z

  • 18 Posts
  • 1 Reply Like
N3NER, you must of been listening to my QSO on 160M! I made a comment last night on the air about how well FRStacks works in my setup but had a question as to a option it has under Radio > Mic >  called "SSB Peak Control". 

As for the replies about CESSB, isn't that already incorporated into the DX+ Comp? FRStacks has the option to select the 3 different Comp levels, but this SSB Peak Control is totally separate.
(Edited)
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 923 Posts
  • 172 Reply Likes
CESSB science: 

http://www.arrl.org/files/file/QEX_Next_Issue/2014/Nov-Dec_2014/Hershberger_QEX_11_14.pdf 

and yes, it's built into SSDR. It's in the manual page 89 ff.
(Edited)
Photo of Gary NC3Z

Gary NC3Z

  • 18 Posts
  • 1 Reply Like
Exactly, so this SSB Peak Control in FRStacks is not for CESSB and is something else, but what is that something else?
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 923 Posts
  • 172 Reply Likes
AFAIK FRStack has a Slice S-Meter peak hold indicator. "SSB Peak control" is nowhere mentioned.
Photo of Gary NC3Z

Gary NC3Z

  • 18 Posts
  • 1 Reply Like
In FRStacks it is under Radio, then Mic, bottom of the list.
Photo of Gary NC3Z

Gary NC3Z

  • 18 Posts
  • 1 Reply Like
I did and all he said was it was a command in the FlexAPI Radio object property called SSBPeakControlEnable.
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 918 Posts
  • 169 Reply Likes
OK, thanks, Gary. I'm not much wiser, then ;-)
Photo of Gary NC3Z

Gary NC3Z

  • 18 Posts
  • 1 Reply Like
Neither am I, inquiring minds would love to know what this can invoke!
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 918 Posts
  • 169 Reply Likes
Here http://www.flexradio.com/flexlib/class_flex_1_1_smoothlake_1_1_flex_lib_1_1_radio.html#aece598832054... is this sentence: 

"bool Flex.Smoothlake.FlexLib.Radio.SSBPeakControlEnablegetset
Enables or disables Peak Control on TX for improved power output"

wich means it is just a clipper?

CESSB should be included in the voice processor setting DX and DX+
(Edited)
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2942 Posts
  • 634 Reply Likes
I am going to play with it,,that can be very useful,,it should work as a limiter
Photo of N3NER

N3NER

  • 186 Posts
  • 24 Reply Likes
Thanks everyone for the replies.  For some reason I'm not getting any notices of replies.  Yes my account has the correct email and it does not send out a verification which I tried many times. 
Photo of Gary NC3Z

Gary NC3Z

  • 18 Posts
  • 1 Reply Like
Was there a correct answer?
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 712 Posts
  • 208 Reply Likes
It looks like this is a leftover of the previous compressor that we had before the CESSB.  There are no references to it in our code, so I think it is just dead code.  We will remove it going forward to reduce confusion.