Flex Lockup on 1.10.16

  • 8
  • Problem
  • Updated 3 years ago
  • In Progress


I had successfuly run my Flex 6500 on Previous full release 1.9.13 for a few months often leaving it running for 24 hrs without any lockups.

I could not use the first recent Beta release due to numerous lockups with continuous audio tone requiring a long button press to reset.

I updated tp 1.10.16 on release and was lockup free until tonight when I experienced a lockup whilst listening to the radio. Same symptoms continuous audio tone and long button press required to reset.

Anybody else have lockup issues on 1.10.16 and does flex acknowledge that the problem still exists.

Not what I really want for the WPX contest.

Regards Andy M5ZAP

Photo of Andy M5ZAP

Andy M5ZAP

  • 215 Posts
  • 41 Reply Likes

Posted 3 years ago

  • 8
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9478 Posts
  • 3666 Reply Likes
Official Response
There have been several requests for FlexRadio to provide an update on this issue.  The issue being addressed here is the random and occasional freezing of the radio, sometimes with an audio tone, other times without, that requires a press and hold of the radio's power button to recover.

I want to assure you that FlexRadio takes customer issues with our products very seriously.  We acknowledge that there is a problem in SmartSDR v.1.10.16 and we are committed to fixing it.  

However, this issue is a low incidence problem when compared to all FLEX-6000s in operation which directly affects the rate at which we can issue a fix.  Because of the low incident rate, it makes the problem much harder to duplicate, isolate and resolve.  We have attempted to capture data on several units experiencing these issues without success.  Whether the logging process actually affects the issue or whether the incidence rate is just too low is inconclusive.  

We continue to troubleshoot this problem and as soon as we can drive it to resolution we will issue a v1.x release that provides a fix.  But with incomplete forensics on the problem, it is hard to predict when this might occur.  

At this time the only recommendation we can suggest is to have you revert to a release that provides a stable operating environment until a fix can be delivered.  

We hear you and we are on it.   Thank you.