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
73 steve gw0gei / gw9j
UPDate; had another crash today after radio was on for about 24 hours.
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!
Win7 Pro on ASUS Z97A 4790K 4Ghz 16GIG memory. Performance monitor did not reveal anything unusual.
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.
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...
We all know 2.0 is slated for June, presumably june 30, so 1.5 months away..
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.
Win7 Pro no USB or skimmers running.
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.
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.
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.
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...
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.
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?
This conversation is no longer open for comments or replies.
This conversation is no longer open for comments or replies.