1.7.30 installed and problem after 1 hour of use

  • 1
  • Problem
  • Updated 4 years ago
  • Acknowledged
Flex 6500 and version 1.7.30. About 1 hour into a qso I stopped transmitting and the 6500 started emitting a tone ( around 400hz ) and would not power down or respond in any way. I had to pull the power plug, waited a minute or so and re-powered the 6500 and operation was normal? I do not know how to duplicate this but thought everyone should be aware.

73, Al K3TKJ
Photo of Alan Waller

Alan Waller

  • 5 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of Bob G   W1GLV

Bob G W1GLV

  • 833 Posts
  • 148 Reply Likes
No problems here.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9388 Posts
  • 3636 Reply Likes
Since you ended up doing a cold boot of the radio, I don't think you will have any issues now.
Photo of Chris

Chris

  • 2 Posts
  • 0 Reply Likes
I have the same problem and make a downgrade to 1.6.21
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9388 Posts
  • 3636 Reply Likes
Has the downgrade made a difference?
Photo of Chris

Chris

  • 2 Posts
  • 0 Reply Likes
Yes it runs well now. :-)
Photo of Alan Waller

Alan Waller

  • 5 Posts
  • 0 Reply Likes
Yes a small bug has crept in I never had any issue with 1.6 either. Thanks for the confirmation
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9388 Posts
  • 3636 Reply Likes
Official Response
In regards to this specific problem report topic, there seems to be an issue that is causing some radios to crash after an indeterminate amount of time.  The first course of action is to completely boot the internal processors by powering down the radio, then remove DC power from the radio for 30 seconds.  Reconnect power and reboot the radio as you would normally.
 
If the radio continues to crash accompanied by a tone being emitted from the radio, this particular defect is in our bug tracker database, marked as critical. and one we are actively investigating.  If you experience this issue frequently, then one option is to temporarily revert back to SmartSDR for Windows 1.6.20.
(Edited)