Flex 6600M making only 35W power output

  • 1
  • Problem
  • Updated 2 years ago
  • Solved
Flex 6600M will only make 35W output power into a 50 Ohm load as measured by LP-100A calibrated wattmeter.  DC supply voltage is 13.8V under load at the input terminals to the radio.
The position of the "Tune Power" slider control does not change the power output except all the way to the left (zero) produces zero output power.  All other settings produce a fixed 35W.
SSB mode produces 35W PEP output.  I have tried reloading ver software and factory default reset of the radio without success.  I have also tried disconnecting from the front panel and controlling the radio with SmartSDR running on a Win10 computer with the same 35W limitation in power output.
Photo of Geoff - W8GNM

Geoff - W8GNM

  • 58 Posts
  • 7 Reply Likes

Posted 2 years ago

  • 1
Photo of Rick - N4RZ

Rick - N4RZ

  • 111 Posts
  • 30 Reply Likes
I am waiting for my 6600M to arrive and currently have no Flex Radio to look at.   But there is a setting where you can limit the maximum output power of the radio to any amount you wish.   On my 6500 I used this to set the power to 40 watts to provide proper drive for my amplifiers.  Is it possible that 35 watts is entered into the box on your radio?   
Photo of Rich McCabe

Rich McCabe

  • 1238 Posts
  • 259 Reply Likes
The tune slider should control the tune button.

If it was mine, I would downgrade it to the last version and try it with that before doing an upgrade again.  Tuner in ByPass?
Photo of Wayne


  • 614 Posts
  • 89 Reply Likes
In ssb your mic level needs set to give you close to 0 on voice peaks. dexp off. mic +20db on. if fh hand mic bias must also be on and make sure you have the correct mic selected.
Photo of Wayne


  • 614 Posts
  • 89 Reply Likes
look in 6400m section tim helped another with a similiar problem and listed the steps which corrected it.
Photo of Michael Walker

Michael Walker, Employee

  • 1368 Posts
  • 406 Reply Likes
Hi All

This is a hardware issue with the radio and we are tracking it as a support ticket.  

So, based on that, we are going to close this conversation for now.


This conversation is no longer open for comments or replies.