flex control

  • 1
  • Question
  • Updated 5 months ago
sometimes tuning doesn't work.  it may work for a few kc but then I'm spinning it and it doesn't move...  any ideas?
Photo of Joe Sartori - K3WTF

Joe Sartori - K3WTF

  • 34 Posts
  • 0 Reply Likes

Posted 1 year ago

  • 1
Photo of Bill English

Bill English

  • 127 Posts
  • 18 Reply Likes
You have it enabled under the settings in SmartSDR, right?
Are you connected to the PC via a USB hub?
Photo of Chris Tate  - N6WM

Chris Tate - N6WM, Elmer

  • 976 Posts
  • 273 Reply Likes
Joe,  you may have a conflict of com ports.  this happens sometimes with flex control.  try adjusting the com port for your flex control to a different port.  use a high number, say like com 55, something that is well out of range of the others.  This has worked in the past for some with this issue.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3559 Reply Likes
This sounds more like an issue with the USB port not keeping up (https://helpdesk.flexradio.com/hc/en-us/articles/202118458-How-to-Mitigate-FlexControl-Latency) or a shaft encoder issue.
Photo of Joe Sartori - K3WTF

Joe Sartori - K3WTF

  • 34 Posts
  • 0 Reply Likes
well I changed com ports and buffers seems the same ....
Photo of Richard Albright

Richard Albright

  • 4 Posts
  • 1 Reply Like
Check the set screw on the knob. I had the same problem.  Rich  W3OT
Photo of W9ILY


  • 81 Posts
  • 7 Reply Likes
Thanks for the tip! I never realized there was a setscrew for the knob and that was my problem!
Photo of N5LB - Lionel B

N5LB - Lionel B

  • 228 Posts
  • 70 Reply Likes
Same issue but nothing to do with the setscrew.  Every so often the FC just stops responding for a few seconds to maybe 10 seconds.  There is nothing obvious in task manager details, CPU is at around 22 - 35% depending on what else is running.

It seems to occur randomly, not very often.  Mostly I use the FC when working contests and S&P, and of course, it will stop responding.  It happens when only SSDR is running as well as when DXlab and DAX, CAT running.  

I have changed com ports, buffers, etc yet it still stops responding.  It has happened for years over different SSDR versions.  I've read the link Tim referenced.  I'm going to do it once more. 

I think it has to do with port data not being captured and passed on to SSDR; no evidence though.