I upgraded to SSDR 18.104.22.168 on my 6700. I found the direct USB connection for my Expert Systems 1.3K-FA and improved DStar capability great, but...
I am experiencing crashes and lock ups of my 6700. I get SSDR's lost network connection with my 6700, and when I quit SSDR and restart it, I can't find my 6700. The only way to find my 6700 again is to shut the 6700 down and restart it (it does not quickly power off, but takes a while to consider the command). Occasionally this will only keep it working for 10-15 minutes before it crashes again!
Having been down this road before, I pressed the "OK" center button and the power button, did a factory reset, unplugged the power, replugged the power, turned it on and imported all BUT my preference settings.
This seems to work for most of the day, after which it crashes again!
Is this just me?
Is anyone working on this unexpected "feature"?
I wish that I could say the same here.
It definitely isn't an "RF thing" since it is repeatedly crashing without any transmitting going on through the day.
And it isn't an ethernet switch thing, since the 6700 isn't just dropping the network connection, it is locking up and requires a reboot, not just a power cycle of my ethernet switch.
As an experiment, after a factory reset, I only imported my transverter and frequency memories to see if the crashing might stop - since previous factory resets with all but my preferences re-imported survived for the better part of the day, I won't be able to tell if this improved the situation until tomorrow...
"Life on the bleeding edge...."
The last time my 6500 crashed, a continuous tone of about 250hz started coming out of the Maestro speaker. A long-press of the power button is always required to shutdown the 6500.
This seems to be a 10 problem... 73, Alex - DH2ID
A few days after the SSDR update, Win10 was also updated w/o problems. Three PC are running Win10 w/o issues.
(I thought it was a bad interaction with my "Global Profiles", but even though I did not re-install them, my 6700 crashed again in a day).
I find factory resetting and re-importing my profiles gives me a day before the next crash, while just recycling the 6700 gives me less time between crashes.
I have confidence that FRS will track it down and fix it, as they did before.
Back here, in the trenches, I tried a full factory reset plus temporary power pole disconnect. I then decided not to restore any of my default settings and just let it quietly 'receive' as a general coverage receiver.
By the morning it had crashed again.
I am sure that FRS will find the bug and squash it.
- 7 Posts
- 0 Reply Likes
Mine was fine till today....Crashes aprox every 14 minutes...Says "SmartSDR has lost connection to the radio. Please reconnect".... using a Flex 6500 with the new beta Ver.22.214.171.124.....Also ...bottom right of screen shows Message "Client connected from IP 192.168.0,7".......flashes for 8 sec then repeats every 6 sec ......driving me crazy... Leo, kk0usa
As reported in my reply to an earlier post in this thread, I had a robust crash free experience with Smart SDR 1.9.13. After upgrading to 126.96.36.199 beta I had regular lockups with unresponsive software and 6500 plus a continuous audible tone. The only recovery route was to press and hold the on off switch until a reset ocurred.
There was no error message displayed just a locked radio and software.
I have had to downgrade back to 1.9.13 and all again it is now perfectly stable.
I have two questions
1- has FlexRadio acknowledged this fault with the beta software ( there has been replies alluding to communications issues causing problems but not acknowledging a software problem with the beta release when there are no comms issues)
2- if the flex is in this state will it respond to a remote switch off request via the external rear remote connector. Is this hardware or software driven. I need to know this so when I operate remote can I switch off an unresponsive rig via remote or is a long power button press the only way to reset the transceiver which is obviously not possible when operating remote.
(Yes, I reset to factory defaults and unplugged the power. Yes, I am very glad to hear that YOU aren't having any problems whatsoever.)
(Gee... It's fun being a cranky old guy!)
FWIW I've been running the 1.10.15 Beta since it's release and had no crashes on my 6500 until yesterday! Yesterday was my first attempt to run CW skimmer with DAXIQ turned on. The radio locked up after about 4 hours. Maybe just a coincidence but I've had the radio on 24/7 the entire time and had no freezes until then.
One more thing: DAX seems to quit service and I can only recover by restarting Windows 10. I have this on two computers, one of them brand new.
73, Frédéric, HB9CQK
- 4540 Conversations
- 1265 Followers
- 2604 Conversations
- 528 Followers
- 3099 Conversations
- 775 Followers
- 706 Conversations
- 141 Followers
- 2560 Conversations
- 746 Followers