Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need the latest SmartSDR and Power Genius Software?
SmartSDR v3.1.12 and the SmartSDR v3.1.12 Release Notes. | SmartSDR v2.6.2 and the SmartSDR v2.6.2 Release Notes.
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes. | Power Genius XL Firmware v3.4.16. | Power Genius XL Utility v2.2.10.
SmartSDR v3.1.12 and the SmartSDR v3.1.12 Release Notes. | SmartSDR v2.6.2 and the SmartSDR v2.6.2 Release Notes.
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes. | Power Genius XL Firmware v3.4.16. | Power Genius XL Utility v2.2.10.
Flex Lockup on 1.10.16
Leave a Comment
Categories
- 69 Community Topics
- 1.9K New Ideas
- 119 The Flea Market
- 5.4K Software
- 4.9K SmartSDR for Windows
- 35 SmartSDR for Maestro and M models
- 85 SmartSDR for Mac
- 143 SmartSDR for iOS
- 149 SmartSDR CAT
- 67 DAX
- 278 SmartSDR API
- 7.1K Radios and Accessories
- 5.8K FLEX-6000 Signature Series
- 554 Maestro
- 14 FlexControl
- 722 FLEX Series (Legacy) Radios
- 149 Power Genius Products
- 117 Power Genius XL Amplifier
- 10 Power Genius Utility
- 22 Tuner Genius
- 41 Shack Infrastructure
- 22 Networking
- 89 Remote Operation (SmartLink)
- 50 Contesting
- 127 Peripherals & Station Integration
- 62 Amateur Radio Interests
- 404 Third-Party Software
Comments
My wife has an ICOM IC-7300 SDR radio ($1350) which has never malfunctioned once and has been running for many weeks on end.
I guess I expect a bit more from a radio setup that cost 7.5 times what my wife's IC-7300 did.
Rick, W7YP
Eric NC6K/KH6
What would you do if there was a severe electrical storm and your radio is connected and running? There's a good chance that if lighting caused your radio to start a fire your insurance company would not cover it because they would say you had no business running a ham radio (and amp, tuner, etc.) during a severe thunderstorm
If FRS isn't going to match that commitment, then the least they could do for us poor suckers is to put the existing code base in the public domain and allow the two branches to compete. I think I know who will win.
It's also an insult to have to pay for "support" annually such as it is, when that 'support' takes years to add features which can readily be found in a $1000 transceiver and should have been in the Signature Series from day one.
@Howard - it would be a LOT simpler to have the FlexRadio monitor some sort of watchdog timer and automatically do a hard reboot if the radio became unresponsive. After spending $7k for the 6700, not to mention all my other toys, I really don't feel the need to buy more hardware to do a remote reset, although I may if I have to. My Yaesu 5000 will run for months without locking up, and may have to go back to being my primary remote radio.
I think it's fair for Flex users to ask for reliability, regardless of why. You guys are starting to sound like the Microsoft apologists that insist users are in the wrong for complaining about Windows (which deserves many of the complaints) when they have problems with lockups, etc.
While the thread is very long, it helped me find my particular problem, and I'm on four straight days of remote operation on 6 Meters without a freeze. I even picked up a few new countries and states. So, a huge thanks to those that contributed useful suggestions and observations.
73
Mike
73,
NC6K
There are tons of things you can do for remote operation.
The way I had it setup is I placed a GSM relay to reboot the Router as last line of defense. Everything else worked with a combination of web accesible relays.
You can actually get fairly fancy but there are neat software packages out there. I really like PSTRotator which includes a couple of features that are great. You can connect it to a weather station or connected to an online accessible weather station and PSTRotator can be programmed to move your antennas to face wind direction or even lower the tower at a certain wind speed. It also has a feature to move the antennas every so often to prevent birds to loiter.
Here is some of the Gear I use:
A ton of stuff from these guys https://www.itead.cc/smart-home.html
http://www.ebay.com/itm/KMTronic-LAN-Ethernet-IP-8-channels-WEB-Relay-board-BOX/281238587222?_trksid...
http://www.ebay.com/itm/2000W-Wireless-GSM-Call-Remote-Control-Relay-Smart-Switch-Home-Security-Syst...
http://www.ebay.com/itm/LAN-Ethernet-2-Way-Relay-Board-Delay-Switch-TCP-UDP-Controller-Module-WEB-Se...
I had 4 wsjtx sessions, 1 cw skimmer.. Prior to the crash I had 8 pans, 8 slices; post crash I had 8 pans, slices A-F; F was in the last pan which had been slice H.
DAX slices also needed resetting..
Yes I have, It behaves the same as a short button press, which is there is a delay of around 50 seconds before the radio shuts down. Which at least lets you shut the radio down if you are operating remote.
Looking back over the past few weeks, the reports have not provided any additional beneficial information that we do not already have logged in the bug report. Most of the reports just describe the operating state of the radio before the crash and we have sufficient information of this nature at this point. What we have determined at this juncture is there is such a wide variability in operating setups, whether or not the radio is transmitting or receiving, the length of time the radio has been powered on, whether or not client software is connected to the radio and if USB cables are or are not used, it validates the random nature of the problem, but unfortunately gets us no closer to determining root cause.
And additional incident reports recently reported with the same type of information can not elevate the criticality of this issue since it is already at the highest level possible.
In addition, the thread has diverged into topics not related to the original poster's topic, which degrades the SNR for people looking for relative and pertinent information on the topic.
At this juncture, I am inclined to close this thread. This does not mean you cannot continue to provide useful information to FlexRadio regarding this issue. It is just that we believe the troubleshooting process would be better served off of the Community at this time.
As I stated early on if anyone has a procedure or a set of steps that reproducibly causes this type of crash to occur, we want to know about them ASAP. The best way to report the reproducible set of events that cause a crash is by opening a HelpDesk support ticket (https://helpdesk.flexradio.com).