Flex Lockup on 1.10.16

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

Hi,

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

  • 201 Posts
  • 40 Reply Likes

Posted 3 years ago

  • 8
Photo of Steve Gw0gei

Steve Gw0gei

  • 193 Posts
  • 50 Reply Likes
I have never used skimmer or dax-iq on my w10 pc since I bought it in April and did a fresh install of ssdr N1mm etc and didn't import my old profiles off the older w7 pc. My 6300 has been continuously running since my last crash in early may, and as usual am swapping between 80m ssb, 6m ssb/cw and 4m ssb/cw via kuhne tvtr. Pc has not been rebooted for the same period.
73 steve gw0gei / gw9j
Photo of Rudy HB9MHB

Rudy HB9MHB

  • 12 Posts
  • 0 Reply Likes
And again my Flex 6700 crashed on May 7th at 19.00 UT and May 9th at 13.44 UT. I hope Flex can find the issue soon...
73 Rudy
Photo of Bill W2PKY

Bill W2PKY

  • 560 Posts
  • 101 Reply Likes
Had another crash today, was not in front of the radio when it happened. SSDR, DAX & CAT were still running fine. Long press on the power button and two button reboot plus reloading the profiles the system was back up. SSDR did not require a restart nor did the PC. 

UPDate; had another crash today after radio was on for about 24 hours. 
(Edited)
Photo of HB9CQK

HB9CQK

  • 31 Posts
  • 8 Reply Likes
I have not had a crash for several days, but last night I had another firmware crash that could only be recovered from by a long power button press. SSDR was still running. The conditions were the following:
Window 10 with all the latest updates (including the latest vulnerability fix). JTDX Version 17.8. with 7 instances running on 7 different bands in parallel. ANT1 and receive antenna in use. FlexRadio 6700, SSDR version 1.10.16. No USB cables connected to the 6700. Radio and computer connected to a network switch. In addition to JTDX I had DXKeeper running and Commander connected to slice A, DAX 1 and JTAlert (I only use slice A for tx, so the logging through JTAlert and Commander works well). I was using exclusively TCP ports to connect, the 6 other instances of JTDX were connected directly to SmartSDR CAT. No other software running on the PC. I had done a reset after my last firmware crash.
73 and hoping for a solution!
Frédéric, HB9CQK
Photo of Bill W2PKY

Bill W2PKY

  • 560 Posts
  • 101 Reply Likes
This morning checking the radio after it had been running nearly 24 hours noticed one slice out of 5 was updating in slow motion. Further investigation revealed the quality indicator showing 1 red bar to 2 yellow bars and packets dropping rapidly. Restarted SSDR with no improvement, rebooted the radio with no improvement, finally needed to reboot the PC to restore 5 green bars on the quality indicator. I am using a 5 port switch for connectivity between the radio and PC.

Win7 Pro on ASUS Z97A 4790K 4Ghz 16GIG memory. Performance monitor did not reveal anything unusual. 
Photo of Bill W2PKY

Bill W2PKY

  • 560 Posts
  • 101 Reply Likes
UPDATE: Found the i218-V Intel Ethernet adapter needed a driver update.
Photo of Jim Runge

Jim Runge

  • 93 Posts
  • 18 Reply Likes
Switched from a 6500 to a 6700 today and in 1/2 hour I got the lock up and tone requiring a long hold power button restart.  Latest software and only thing running on the computer with windows 10.  I have a USB going to my SPE 2KA amp.  I was in SSB receive only mode when it happened.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes

I am getting the lock up again more  frequently now (3 times in last 5 days) after a period of no lockups.

Couple of other observations

1 - As before a short button press doesn't turn the radio off but if you wait after the non responsive short button press the radio does shut down approx. 45 seconds later. This is not a controlled shut down but a sudden shut down like you get from the long button press. Is this a feature put in for remote operation allowing shutdown of a non responsive radio.

2 - When you restart the radio it is in the state it was in from the last controlled shutdown Band, slices etc.

Extremely quite from Flex on this recently. I am hoping when they finish launching their new products they swiftly get back to the important business of fixing the current software for there current customers.

Photo of Steve K9ZW

Steve K9ZW, Elmer

  • 1593 Posts
  • 781 Reply Likes
True the absolute date of Hamvention is upon FRS but I'd not presume this issue is forgotten.

Will 1.10.16 see an upgrade soon? Hmmmm kind of likely. Happens most Hamventions. Hopefully this issue is fixed then!

73

Steve
K9ZW
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
Another crash on the 6700, this one with the raspy tone, while mid qso on wsjtx...

The status of this topic says "IN PROGRESS", can we get an update on the status of the radio crashing, and of the dax corruption?

Seems a number of us current customers are hitting these issues, with not much response from Flex..
I certainly cannot recommend flex at this point due to the sw instability of the Flex-6000 line.

My F5K may have to come out of retirement.. In spite of the hassles of vac and firewire, it didnt crash mid qso...
Photo of Steve K9ZW

Steve K9ZW, Elmer

  • 1565 Posts
  • 771 Reply Likes
Heads up, as there are SO many indications of a new version of SmartSDR being readied.

We will all know in a couple days.

73

Steve K9ZW
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
Steve a new version of smartsdr which fails to address the dax corruption and rig crashes, is really not of interest.. I dont want NEW features, I want FIXED WORKING items...

We all know 2.0 is slated for June, presumably june 30, so 1.5 months away..
Photo of Steve K9ZW

Steve K9ZW, Elmer

  • 1565 Posts
  • 771 Reply Likes
FRS side stepped answering whether another v1.x release would happen first.

So maybe?

Curious how you know the v2.x release won't fix the problem though?

Regardless I expect they are all traveling or setting up at Hamvention and it will be until they have dealt with showing their products to a predicted heavy crowd before they say much specific to your needs.

73

Steve
K9ZW
(Edited)
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
Steve - I didnt say 2.0 woud not fix it; However, if you look at the number of comments by flex folks, I sure wouldnt be betting on it...

And its not just my needs, I think we've shown this is a much larger problem and just a few of us..
Photo of Terry Tankersley

Terry Tankersley

  • 58 Posts
  • 5 Reply Likes
My 6500 locked up with the tone for the second time this morning. No auto updates windows 8.1, radio has been on for 11/2 hrs. No other programs running, Dax and Cat loaded. I have been holding posting this until it happened again.
73
Terry
Photo of Bill W2PKY

Bill W2PKY

  • 540 Posts
  • 94 Reply Likes
Terry-
If you haven't tried the two button reset: Export your profiles:

from page 178 of the SSDR user guide:

For the FLEX-6700/FLEX-6500/FLEX-6700R, while pressing and holding the OK button on the front of the radio momentarily press and release the radio’s power button.  You will see a radio console message that says “Reverting to factory settings” and a countdown timer starting at 5.  Keep pressing the OK button until the display counts down to 0 and the Calibrating message is displayed and the LED changes color.  For the FLEX-6300, simply hold the Power button while powering on for 5 seconds until the LED changes color. 

Profiles must be imported after this reset so be sure to export your profiles to a known directory so you can find them afterwards.
Photo of Terry Tankersley

Terry Tankersley

  • 58 Posts
  • 5 Reply Likes
Thank u, I am doing this now.
73
Terry
Photo of Steven G1XOW

Steven G1XOW

  • 297 Posts
  • 129 Reply Likes
It may be useful and informative if those who do use Dimension 4 and are having the lock-ups to use/trial another time sync app instead. I recommend NetTime http://www.timesynctool.com/

Temporarily swapping D4 out for something else that is functionally similar (but different code) will certainly give FRS guys a good steer.

I've used nettime for 2 years without a hiccup in that respect.
Photo of Andy M5ZAP

Andy M5ZAP

  • 195 Posts
  • 40 Reply Likes
I beleive people who don't use Dimension 4 also have the lockup.
Photo of Terry Tankersley

Terry Tankersley

  • 58 Posts
  • 5 Reply Likes
I don't use Dimension 4 or any other time sync program that I know of.
Like I said it has only happened twice but I only run the radio three or four hrs a day.
Terry
Photo of HB9CQK

HB9CQK

  • 31 Posts
  • 8 Reply Likes
I had all my lockups while using NetTime
73, Frédéric
Photo of Jim Runge

Jim Runge

  • 93 Posts
  • 18 Reply Likes
My 6700 locked up again yesterday. The only thing running besides the flex software was the wooden box S meter and a usb cable to my SPE 2k amp.
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
Any news from tonights presentations regarding a fix?
Photo of Bill W2PKY

Bill W2PKY

  • 560 Posts
  • 101 Reply Likes
My 6700 crashed today after running for 4 days 24X7. Required long power button push to power down the radio. SSDR was fine when restarting the radio. 

Win7 Pro no USB or skimmers running.
Photo of Tom

Tom

  • 48 Posts
  • 7 Reply Likes
David, I'm afraid I will not be able to help at this time....just too many things going on now. I'm also having another issue (happened yesterday too) w/6300 losing my SSDR CAT setups. I'm left with the default settings)I suspect a corrupt file.
Photo of David Orman

David Orman

  • 59 Posts
  • 21 Reply Likes
No worries, hopefully someone else can do the same. It may be completely unrelated, but worth looking into.
Photo of Tom

Tom

  • 48 Posts
  • 7 Reply Likes
FWIW---just checked and I am using NTP. If there is a way to check the log you need, I don't see how, so if you'll instruct me, I'll do it.
Photo of David Orman

David Orman

  • 59 Posts
  • 21 Reply Likes
Hi Tom, my post a few above has directions and a screenshot showing you how to check the log. Please let me know if this works for you! I'm not a Windows guy by any means, but I'll try to help out.
Photo of Tom Warren

Tom Warren

  • 59 Posts
  • 24 Reply Likes
David, ah, ok.....I should be able to do that. I'll see what I can find out and reply after the weekend. Thanks and 73 W4TMW
Photo of Greg - KØGDI

Greg - KØGDI

  • 78 Posts
  • 3 Reply Likes
I've been having this problem consistently for a while now.  Hoping beyond hope that 2.0 fixes this as it wouldn't be ideal to remote a radio that is freezing up.  Guess will have to wait for the June release of 2.0.
Photo of Steve Gw0gei

Steve Gw0gei

  • 193 Posts
  • 50 Reply Likes
My understanding is that 2.0 release may not include a fix for this issue, and there will be one or two 1.10 maintenance releases after 2.0 i.e. After the end of June - this info is from Gerald's post in another thread. I think I am going to try a complete removal and fresh install on my few months old w10 pc as it also had a dax driver corruption fault arise this week.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9198 Posts
  • 3558 Reply Likes
If we have determined root cause for the issue, it will be fixed and distributed to all major release versions.
Photo of Steve Gw0gei

Steve Gw0gei

  • 193 Posts
  • 50 Reply Likes
Thanks for that confirmation Tim. I sort of assumed that the problem has still not been narrowed down. I know it's difficult with an issue that appears random but hopefully it will be found and at least a beta fix released so that those of us suffering the issue can help a bit more by trying the beta fix to give you more data or confirm that it fixes it.
Photo of David Livingston

David Livingston

  • 122 Posts
  • 28 Reply Likes
If the locking up issue has not been resolved in V2.xxx has any code been included in this release to track down this issue...?????
Photo of James Skala

James Skala

  • 107 Posts
  • 25 Reply Likes
I would like to suggest a Internal SFTP or SSH server dedicated for logging facilities.  It should run separate and independent from main core code so it can capture when a crash occurs. Then a  client that could be ran on client machine to retrieves logs.
Photo of Paul Mandel

Paul Mandel

  • 84 Posts
  • 21 Reply Likes
I was having crashes a number of times a day sometimes in fact I was one of the first to post about the issue.  About a month and a half ago I made two changes that Tim recommended.  First was to change from Dimension 4 to NTP Time and second was to move the port number of the flex control up to the 200 range of the COM ports.   Since that time I have only had two stops, both on required the simple push of the on/off button.  I have not had a radio freeze since the change.  

I still have an issue where the USB ports on the Flex sometimes will loose sync with the peripherals.  The worst is the SteppIR controller but the SPE 2KFA has had a few failures, also.  The only way I have found to get the band change back working is to disable/enable the USB port on the Flex. This works about 95% of the time.  The other 5% require the radio to be turned off and the relaunch of the software.  Just relaunching  the software will not solve the problem. 
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
Paul - interesting; I've always had my FlexControl connected to DDUTIL,  though it is on COM3; I also have always used Meinberg NTP.  I still get the crashes, even after the two button reset. 
Photo of Paul Mandel

Paul Mandel

  • 84 Posts
  • 21 Reply Likes
I was getting an error window related to the Flex Control on soft stops, stops where all I had to do was restart the radio with a normal push.  Since I changed the port to about 200 I have not had the error but have had two radio stops without and error window.  As i said no lockups and I was twice to three times a day at one time.  I do Run Windows 7 and I have updated to the latest releases as they come out.   
Photo of Tom Warren

Tom Warren

  • 59 Posts
  • 24 Reply Likes
Paul, after reading this: "I still have an issue where the USB ports on the Flex sometimes will loose sync with the peripherals. ", I have been having this problem on and off for a couple of months now, where one of my programs using SmartCAT will lose sync requiring me to "Remove" that CAT setting and "Add" ing it back into SmartCAT again. Now, for some reason, SmartCAT has lost all of my Comport additions except the first 2 of the 3 default settings. Also, SmartCAT will not let me add any new settings...the Com box is greyed out. Since it hasn't hindered my use of the radio, I've been slow to try and resolve it. But now that the crash issue landed on my rig I feel that my situation needs to be added to the pile to help resolve this. W4TMW
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3559 Reply Likes
Photo of Tom Warren

Tom Warren

  • 59 Posts
  • 24 Reply Likes
Tim, Thanks a million....I haven't seen that before and hope it does the trick.
Wishing you a great holiday. 73, Tom
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
My 6700 crashed again during the night after nearly 4 days running 24/7.  I've run much longer with only one panadapter containing one slice receiver and never crashed once; however, my standard configuration now is two panadapters, the first with one slice receiver on one of the HF bands and the second panadapter having four slice receivers monitoring our four primary VHF repeaters.  It was only after going to two panadapters that I began noticing the crashes.  Has anyone been experiencing the crashes with only one panadapter and one slice receiver?

Following this crash, I tried the short push on the on/off button and waited patiently.  After slightly less than a minute, the radio shut down.  When I turned it on again, the HF panadapter was on a different band than I'd left it on and its single slice receiver was gone.  When I added one to it, all seemed well until I changed bands to return to 30m where I'd previously left it.  When I did that, all but one of the slice receivers on the 2m panadapter disappeared and the one that remained went to 30m as well and to the same frequency as the slice receiver in the first panadapter. 

Re-importing my saved configuration seemed to make everything well again.

When I purchased my 6700, it was with the intention of also operating it remotely.  Obviously that's an impossibility as long as this problem remains.  Currently I have a $7500 radio that I can't operate remotely and my wife's $1400 Icom IC-7300 that I can.

I suspect that most if not all of 6000 series owners who haven't seen this problem simply haven't been running their radios long enough.  If FlexRadio truly can't reproduce this problem in their lab, then it's probably time for them to give one of us a new radio in exchange for ours and then run it as we did in their lab.

As someone who's spent years as an EE designing and developing embedded systems, I know that problems like this can be difficult to reproduce and fix; however, I've never seen one that dragged on this long without resolution and that was even involving products costing far less than these radios.

Rick, W7YP
Photo of Norm - W7CK

Norm - W7CK

  • 754 Posts
  • 160 Reply Likes
As much as I love my 6700, I have to agree with Rick.  My intention was to operate remotely.  The only way I've been able to do this is with the addition of special TCP switches to power cycle the rig which no longer works because when the rig freezes up, I can no longer cycle via the connector on the back of the rig.  Since I run my entire station on solar, I now I have to buy yet another device (TCP/DC power switch) which should enable me to turn off the DC power to the 6700 and then turn it back on.

This has been such a problem, I no longer use my 6700 remotely.  I use my old IC-7100 which has never failed me via remote operation.  It doesn't have a scope, but all of the functions of the radio work flawlessly during remote operation.

While Flex has said it is a Software company, I believe they need to focus their attention to some of the problems and shortcomings that are expected to work flawlessly from any modern transceiver.    

Things I'd like to see focused on:

  • Switching between HF and 2m often messes up all of the panadapters.  Workaround has been suggested but it is a bit of a kludge.
  • FM Squelch is terrible. Constantly squawking for no apparent reason.
  • No RF gain on FM
  • All mode squelch has never been implemented.  This makes using more than a couple panadapters at one time pretty much useless.
  • GUI needs work.  Some areas are hard to read due to color, waterfall size/location isn't saved very well in profiles.  When trying to adjust, it sometimes jumps around and is hard to set
  • Noise mitigation causes a lot of distortion (I don't have much noise so don't need to use it but others do).
  • Having to have an external device to turn on/off the rig is usually for emergency shut down. I have to have 2 of these devices.  One for the connector on the back of the rig, a second one for the 12v power going to the rig when the built in relay fails to work due to rig locking up.  Now I have a bunch of wires and external boxes all over the place just to ensure the rig can be cycled.
  • DAX often messes up and I have to shut it down and recycle it and or the rig.  I've had numerous times when on digital modes, I've lost DAX control and it takes a few minutes to get it all recycled and working again.  This is better than it was in the past, but it still seems to be an issue.
  • VOX seems to occasionally stop working
  • What happend to Wave forms
While I LOVE my 6700, I feel 4 years is a bit long waiting for some of the basic functions provided by most modern rigs.  It seems a bit long for some of the other functions and features talked about when the 6700 was first introduced.  If I new it was going to be this long to see some of these features, I may have wanted to purchase a much less costly rig and then just upgraded as the features became available.  I have been crying for an operational all mode Squelch for years. 

Still a great fan but just a bit frustrated.
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
BTW, while I've had several crashes, NONE have left the radio emitting a sound of any kind, let alone a constant tone.  Most reports I've read have seen the tone as an additional symptom.

Interesting....

Rick, W7YP
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Norm, I agree with every point you made in your last post.  I consider myself fortunate that I waited until January of this year to take delivery of a 6700 as I spared myself four years of frustration that you've unfortunately had to patiently endure.  I LOVE my 6700 and can see that it should easily be the king of transceivers for years to come, if only they'd put more work into the software.

I've now added a Mountain West Radio RigRunner 4005i DC power monitoring and control unit to my setup.  It does reliably enable to me to remotely turn on/off DC power to up to 5 different devices.  With it, I can now reliably power-cycle the radio and then re-import my configuration.  I don't know if the latter step will always work or if it will work for everyone.

I can't help but wonder if Flex has ever asked for the configuration files of those reporting this problem so that they can try to reproduce it in their lab.  They never asked for mine or even for much detail about my setup.  That should be the first step in any serious effort to debug a difficult and seemingly random problem.  Failing that, they should swap out one or more radios with users who see the problem quite frequently.  If this radio was a car, there'd be lemon laws that would force a replacement or a refund.

Please don't misunderstand me or my tone.  I've been a Flex customer since the early days of the SDR-1000.  I love all three radios (a Flex-5000 is the other radio) and want to see FlexRadio Systems grow and prosper.  They have caused a revolution in amateur radio that the Big 3 are finally starting to respond to (e.g., Icom IC-7300 and soon-coming IC-7610).  But, PLEASE, devote whatever resources are necessary to fix this problem.  We deserve better in return for our loyalty.

Rick, W7YP
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
Rick - There are at least 3 flavors of crash:
crash needing the long power cycle
crash with tone needing the long power cycle
crash while xmitting

I've hit all 3, but have only had the crash while xmitting happen two or three times..
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
I've yet to see the crash while transmitting; in fact, all of my crashes have occurred while the radio is simply in receive mode in the middle of the night, when everyone and everything else has gone to bed for the evening.  As a result, demands on the network and on my PC are at a minimum.  A couple of my crashes would not respond even to the long push on the on/off button.  I had to disconnect DC power to regain control over the radio.  Most of my crashes required the long push and today's crash is the first that responded to the short push, albeit after about a minute delay.

In every case, one or more of the panadapters had lost at least one slice receiver and radio behavior was odd.  Clearly something got scrambled within the radio.   A re-importation of my saved configuration files restored normal operation until the next crash.

This is clearly a software problem, as it appeared beginning with the 10.16 release.  Others who've gone back a release report that the problem has gone away.  I have a Down East Microwave 2m LDPA which I use with my 6700 and that requires support beginning in the 10.16 release; otherwise, I have to give up my 2m use of the radio.

My gut and 30 years of experience suggest to me that we're chasing ghosts looking at what's plugged into the USB ports, whether an NTP service of some kind is being used, whether a gigabit switch is not fast enough, the ambient air temp is too high, etc.  If the search for the root cause remains focused on peripheral areas such as this, we'll likely never get to the bottom of this.

Rick, W7YP
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
6700 crash; required long push; tone is present. "smartsdr has lost......" rig had been on about 3 hours. Pretty much same as the previous crashes I've reported.
Photo of David Livingston

David Livingston

  • 122 Posts
  • 28 Reply Likes
If the locking up issue has not been resolved in V2.xxx has any code been included in this release to track down this issue...?????
Photo of James Skala

James Skala

  • 107 Posts
  • 25 Reply Likes
For future releases..  maybe V2

I would like to suggest a Internal SFTP or SSH server dedicated for logging facilities.  It should run separate and independent from main core code so it can capture when a crash occurs. Then a  client that could be ran on client machine to retrieves logs.
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Yesterday I experienced my first freeze during transmit.  While the short push of the on/off switch did initiate a shutdown roughly a minute later, I had to reset to factory defaults, then reload my profiles, in order to recover normal operation.  Just reloading my profiles didn't do the trick this time.  Then, after running only a few hours more with WSJT-X, it crashed again, with the same process required to recover normal operation.  I'm having an especially difficult time believing that in all this time they haven't been able to reproduce it.  I've reproduced problems in embedded systems which occurred far less frequently.  They may well need to add logging capabilities to the firmware to successfully debug this; however, it's definitely past time to do so.  
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
"Loss of connection to the radio" on the 6700 this am; had made some cw qsos earlier; rig had been on about 2.5 hours;
Running 1.10.16, win10 1607 14393.1198
i7-6850, 32GB, nvme ssd (samsung 960 pro)
FRstack, dxlab suite; skcc logger, ddutil; ntp (no time changes shown in event log)
8 pans, 8 slices
radio had been reset to factory defaults a week ago and I didnt restore any of my profiles.
A short button press, followed by waiting about a minute and the rig powered off;

There were no network hiccups observed when this happened; windows logs show nothing happening in this time frame..

On reboot and restart of ssdr I had 8 pans and a scrambled set of slices. There were 6 out of 8 slices, randomly distributed; also the antenna settings were mucked up; some slices were on ant1/ant2, some ant2/ant2;  at time of "anomaly" 5 slices were on ant1/ant1, and 3 were ant2/ant2

can we get a build to enable syslog so we can get the logs off the rig? Figuring that might at least help...
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Fired up the 6700 about 8 AM this morning.  Made a trip into town about 1.5 hours later, leaving the radio running.  When I returned 3 hours later, i found it had crashed.  Shut it down with the short push on the on/off button.  When I powered it back up, for the FIRST TIME ever after crashing it had all panadapters and slice receivers.  It ran for several hours before crashing again.  

This time I had to restore to factory defaults, then reload my profiles.  It ran for about 15 minutes before crashing again.  This time it briefly emitted a tone with the SmartSDR panadapters all frozen, followed by SmartSDR reporting it had lost the connection almost right after the tone disappeared.

Restored to factory defaults and again reloaded my profiles.  Will see how long it runs this time.

I have never before paid as much for a transceiver nor been as disappointed with my purchase at the same time.  I'm supposed to give a presentation on this radio to my club in a couple of months.  At this rate, I really don't think Flex Radio Systems wants me giving the presentation that is the only honest presentation I could give; but, given the level of support on this issue, maybe they simply don't give a shit.
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
Problem is there are the crashes and also the dax corruptions. The DAX corruption has been there for several  releases (maybe many), so if you like to do digital modes the corruption is a regular and ongoing pita...
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Larry (W8LLL), I also have the Down East Microwave 2m power amp (LDPA) with preamplifier which is made for the 6700 and uses one of its USB ports so that SmartSDR can transparently control its operation.  If I back-rev from 1.10, I can't use it, as that's the first version of SmartSDR to support it.  I normally monitor our 4 primary VHF repeaters with the 6700 and wouldn't be able to do so while having enough TX power to reply to traffic, as the LDPA is automatically switched on and inline by SmartSDR and gives me no manual capability for doing so myself.
Photo of Larry - W8LLL

Larry - W8LLL

  • 532 Posts
  • 116 Reply Likes
Dax corruptions under windows 10? I use windows 7, no dax issues.
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
I had them under win7; did a clean win7 install still got them. I run 4 wsjtx sessions; 
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
I have had dax corruption on my w7 i3 laptop and my new i5 w10 tower pc.
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
It's also very annoying that I can't sell my 6700, at least in good conscience, without taking a bath doing so.
Photo of Larry - W8LLL

Larry - W8LLL

  • 532 Posts
  • 116 Reply Likes
I get it, My thoughts were for your up coming presentation revert back to a stable version.
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Did you try 1.10.16 and also experience radio freezes, then fall back to 1.10.15 and the problem went away?
Photo of HB9CQK

HB9CQK

  • 31 Posts
  • 8 Reply Likes
From my experience version 1.10.15 is worse than 1.10.16 regarding lockups. 1.9.13 had no lockups for me. I am still running 1.10.16 because I had no lockups recently (a few days only), but I was not very active.
73, Frédéric
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
I had another 6700 owner contact me off-forum to tell me that he's been stable since backing up to 1.10.15.  So, that's what I'm now running and have been for the last 17 hours.  So far it's still running and my fingers are still crossed.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes

Hi,

1 - Could we please have an update from flex reference the radio lock-up issue.

2 - Flex state it is a small number of users has anybody who uses there radio a reasonable amount (2 to 3 hrs a day plus) on version 1.10.16 NOT  had a radio lockup?

Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Steve, be thankful you bought the 6300 and didn't go all the way for the 6700 like some of us did.  At least you're grabbing only one ankle instead of both of them.  I had planned to use my 6700 at our club Field Day event.  Instead, I'll bring my reliable ANAN-100D (one-third the cost).  I'll get a lot of questions as to why I brought the ANAN instead of the 6700 and I'll answer them honestly.  What this is ultimately costing FRS is going to be FAR greater than the cost of adequately staffing the research into the problem today.

Rick, W7YP
Photo of k3Tim

k3Tim

  • 940 Posts
  • 197 Reply Likes
:-)  

I'll be backpacking my 6500 and Maestro out for Field Day to some local mountain top. Since FD isn't a 'contest' per se IF it locks up not a big deal. If I were really worried about it, I'd drop back to the working version.

Tim - k3tim/6
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
In the uk the rsgb hf cw field day is a contest.

I am going to do another full delete of ssdr, factory reset the 6300, and try again, to see what happens. If it still occurs i will roll back to an earlier version prior to 1.10. If that doesnt solve it i will trade the 6300 in for a k3 or new anan this September and suck up the poor trade in price as one of lifes experiences to learn from.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
Steve,

I found 1.9.13 reliable. It was only 1.10.16 and the earlier Public Beta releases that were an issue.

In fact the public Beta's were terrible especially the first release. I had to roll back to 1.9.13 for all contests. In my case there was a lower freq of lockups in 1.10.16 than in the beta releases but the problem was obviously still there.

What did flex attempt to fix between the Beta releases and 1.10.16 and does that not point them to the potential issue which is still a residual problem in some instances.

As alluded to in previous posts Flex have helped people fix the issue can they please post the fixes they have implemented. Or at least state there is no fix so that discussion can be more informed.

The silence is deafening !?
(Edited)
Photo of HB9CQK

HB9CQK

  • 31 Posts
  • 8 Reply Likes
Hi Andy,

maybe I am wrong, but somehow I remember that the same lock-up issue was present in a release (no beta) way back and it was fixed in a subsequent release. It reminds me of issues people have in software development with configuration management, re-introducing errors that were already fixed by linking the wrong software module or component for a new release.

Yes, the silence from FRS is overwhelming!

73, Frédéric
Photo of Paul Bradbeer

Paul Bradbeer

  • 170 Posts
  • 66 Reply Likes
Hmm..just had my first lock-up with constant tone and needing a long-press to close down.  My 6500 is on 1.10.16, running Windows 7, DAX and CAT both in use with N1MM+ and CW Skimmer.  This was mid QSO on a 6m  Es opening to Ukraine.  Fingers crossed it won't repeat; sounds like it is an issue, so hope a fix is in the offing.  Paul M0CVX

This conversation is no longer open for comments or replies.