Buzzing sound

  • 2
  • Problem
  • Updated 2 years ago
  • In Progress
 SmartSDR 1.10.16 software  I've experienced two crashes of my 6300. Along with the crash the radio also was emitting a tone from the speaker. I tried to shut down the radio with the power button, but it wouldn't shut off the radio. I had to shut down the power supply. After restarting the radio it seems to work as it should, but this has happened twice. Both times that I experienced this problem I was in the listening mode, I wasn't doing anything with the radio but listening to a QSO. I found where this problem was reported about 1 year ago, but I haven't seen a solution.
Photo of Bob Brown - N8OB

Bob Brown - N8OB

  • 90 Posts
  • 6 Reply Likes
  • worried.

Posted 2 years ago

  • 2
Photo of Jim  KJ7S

Jim KJ7S

  • 184 Posts
  • 33 Reply Likes
This issue for me has only cropped up three times and it seemed to be because of slightly high voltage (around 14.3+) as near as I can tell. In all three cases I had, the only two ways to shut it down was either unplug the power, or push and hold the power button until it shuts off.  So far I haven't noticed any permanent damage but the  restart may introduce some odd settings. That said I hope you get it taken care of,since I have turned the supply down to 14 volts or a little less, it has not reproduced the problem.
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
There is a lot of discussion about this issue in this thread:https://community.flexradio.com/flexradio/topics/flex-lockup-on-1-10-16
Welcome to the club :(
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9186 Posts
  • 3550 Reply Likes
Official Response
This issue as described sounds like the random radio crashes that have affected some users running SmartSDR 1.10.x.  This issue is in our bug tracker as issue #4534.  I stated in an earlier Community post, We acknowledge that there is a problem in SmartSDR v.1.10.16 and we are committed to fixing it.  The random nature of the crashes and the lack of good forensic data make finding root cause challenging.  We have been working on the problem and when we believe we have a fix, it will be released.  If this becomes too troublesome, reverting back to 1.9.13 has provided relief for others experiencing the issue.  In the meantime, we apologize for the inconvenience.