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

  • 179 Posts
  • 36 Reply Likes

Posted 2 years ago

  • 8
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
6700 crash; stuck in xmit during wsjtx qso; ssdr lost comm with radio;
had been on about 4 hours. long button push. no tone.
Photo of Rick Hadley - W0FG

Rick Hadley - W0FG

  • 600 Posts
  • 130 Reply Likes
I've had half a dozen instances of the constant tone lockup, but I don't know if they were all since 1.10.16 came out.  Most of them have occured overnight, or at least when I'm away from the shack.  The last one happened a couple of days ago, after I had uninstalled SSDR, done the Build 1703 Windows 10 upgrade, and then reinstalled SSDR.  The rig runs 24/7 and it hasn't happened again...yet.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9186 Posts
  • 3548 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.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9186 Posts
  • 3548 Reply Likes
Rick - I am afraid that Alpha releases are not available for public distribution.
Photo of k0eoo

k0eoo

  • 623 Posts
  • 87 Reply Likes
Tim - I apologize if this has been mentioned before, back in the day, we use to find very intermittent bugs (sometimes called race conditions) by running timing margins and voltage margins... 

Again I apologize if this has already been done....  Just what FRS needs, is some 72 year old yeahoo looking over your shoulder.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9186 Posts
  • 3548 Reply Likes
No problem. We have a variety of tools to help identify these types of issues.
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Tim,

Please don't take this personally; but, if you're existing tools have yet to reproduce the problem in your lab, yet it's occurring on many customers' installations, then your tool kit is less than totally adequate.  That leaves you with two options:  (1)  Expand your alpha/beta testing to include many of those who are frequently experiencing the problem, or (2) Look for the deficiencies in the tools and testing methods you're currently using.  Especially when close to a major release, we found the first approach to be the most productive and least taxing on our own resources.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9186 Posts
  • 3548 Reply Likes
Thanks for your feedback.  We'll take it under consideration.
Photo of Don, VE2HJ

Don, VE2HJ

  • 38 Posts
  • 2 Reply Likes

Hi Tim, from your post on 19 april i want to clarify this:

 "do a normal power off on the radio by pressing and releasing the power button.  Give it a good 15-30 seconds to respond. "

If the radio shutdown after the delay without indicating that it is shutting down, is this a lockup that you want us to report ? ( On my last 4 events,  my 6500 shutdown after 45, 60, 90, 60s)

73,  Donald, VE2HJ

Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
It has always taken my 6700 roughly a minute to shut down following a crash and, so far, it has always eventually reported "Shutting down" on its display.  Only a couple of times have I had to do the long push and hold on the on/off button to shut it down.
(Edited)
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9186 Posts
  • 3541 Reply Likes
Only a couple of times have I had to do the long push and hold on the on/off button to shut it down.

That condition indicates a crash.  The other condition does not.
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 863 Posts
  • 319 Reply Likes
To clarify, there are two separate shutdown measures that the radio takes.  If the radio firmware is up and running properly, a single short press of the power button should initiate a shutdown within 5-10 sec.  Otherwise, there is a 60 sec timer in the power control chip that will shut things down if the firmware does not respond.  

The latter is what indicates the firmware was not running properly.  Holding the power button down for ~4 seconds performs the same shutdown as the end of the 60 sec timer.
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
I think it's fair to say that to, most people, once the radio becomes unresponsive to SmartSDR and will not reconnect, it has "crashed", especially when most of the time a corrupt profile is the 'parting gift'.
Photo of Mike - W8MM

Mike - W8MM

  • 218 Posts
  • 49 Reply Likes
I've lately had a couple of "freeze-ups" running 1.10.16 where my VPN (SoftEther) remote session of SmartSDR just quit and the radio chooser option for that particular radio vanished from the radio-setup screen on my remote CPU running SmartSDR under Windows 10 through Parallels on my office iMac.

After the event, I tried other ways to connect remotely, as well as locally by WiFi/lan, using SmartSDR for iOS, etc., and the radio remained not discoverable.

The situation was remedied by a long press of the power button once and only needed a short press another time.  It's possible that the long press was not needed the first time, I just did it for fun.

These "freeze-ups" only took less than an hour to occur over VPN.  Last night, I ran the same radio for hours using local lan control and front-panel microphone w/powered speakers from the rear panel without any incident.

My observed version of the problem seems VPN/remote dependent.
(Edited)
Photo of Don, VE2HJ

Don, VE2HJ

  • 38 Posts
  • 2 Reply Likes

It would be interesting to know  if any radio shipped with the factory firmware version 1.10.16.xxx ever had a lockup ?

IF NOT

 this would suggest it is not the firmware but something else. ( upgrading process, virus etc.)

So i think that we should indicate the serial no. of the radio when we report a crash.

73, Donald, VE2HJ

Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
It might also be informative to find out, from those experiencing the problem on 1.10.16 after upgrading to it, whether they had reset to factory defaults BEFORE doing the upgrade, as well as what version they were running before they upgraded to 1.10.16.
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
6700 crash with tone this am while sitting idle on 40m cw.  Radio had been on about an hour;
Upon reboot radio had 6 of 8 slices apparently randomly distributed to the 8 pans.

Yesterday radio was on about 12 hours doing cw, no issues... Nothing different between how I ran yesterday or today. Radio has default profiles.
Photo of James Skala

James Skala

  • 103 Posts
  • 24 Reply Likes
Lockup occurred on a freshly rebooted PC and Radio about 10 mins into reboot.  But this time the lockup occurred while TX'ing.  The TX was locked up even with not connection to radio.  Red TX was on the power button, tried to reconnect to radio by relauching the SmartSDR but radio was not listed.  Short button power did not turn off radio.  Long button power off required.

Flex 6300 1.10.16 No USB's
SPE 1.3K-FA
PALSTAR HF AUTO
(Edited)
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Welcome to the club.  I've been experimenting with 1.10.15 for the past 8 days and it's been far more stable on my radio than was 1.10.16.  If you decide to give it a try, be sure to reset your radio to factory defaults on 1.10.16 BEFORE doing the back-rev to 1.10.15. 
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
After several days running without a radio lockup on 1.10.15, but only doing SSB or CW, I fired up WSJT -X to see if DAX might be a factor in precipitating the radio crash.  2.5 hours later, I had my answer.  SSDR had lost connection to the radio and the radio had to be restarted, restored to factory defaults and my profiles reloaded.

Virtually all other crashes I saw on 1.10.16 occurred either while running some kind of digital mode or after having done so for some period of time.  DAX would seem to be a contributor to this lockup problem.
Photo of Bill W2PKY

Bill W2PKY

  • 523 Posts
  • 86 Reply Likes
I have been running 1.10.16 w/DAX but only 4 channels active. Will activate the remainding channels to see if problems return.
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
It may well have nothing to do with DAX.  After this morning's crash, I restarted the radio, forced factory defaults and then reloaded my profiles.  Did nothing more with the radio but it crashed while idling within 20 minutes.  The profile I loaded was newly created 9 days ago, right after a reset to factory defaults.  Then it was saved.
(Edited)
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Well, DAX crashed during the night and took my PC down with it.  The 6700 appeared to be alive because a single, brief push immediately put it into "Shutting down."  When I rebooted the PC, it crashed again while DAX was loading.  Went into safe mode and uninstalled 1.10.15 BETA. leaving FlexVSP still installed.  System booted normally after that.  Will reinstall 1.10.16.174 and try not to think about how much money I've paid for all of these delightful experiences.
Photo of Dave

Dave

  • 97 Posts
  • 13 Reply Likes
Just had a lock up with long button reset. Been a long while since I have had a lock up (months). BTW it is almost 90 degrees here today.


Tim have you tried putting the radio in a heat chamber to see if it has any effect?(hot or cold)
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Dave, my 6700 is in a temperature-controlled room, kept to 70F year-round.
Photo of Dave

Dave

  • 97 Posts
  • 13 Reply Likes
Rick,
The point is, FRS has not actually been able to reliable reproduce the issue. I am suggesting that stressing the radio might help in making the problem more frequent

As an engineer, I know  the hardest problems to find, let alone solve, are the ones that happen once in a blue moon.

The problem with real time systems, it is very difficult to distinguish a FW verse a HW problem. They both act the same.

This is the type of problem I would love to work on. But I am not part of FRS so all I can do is suggest things to try. 

Dave KB1WOD
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
I hear you, Dave.  I'm an old EE who's done decades of embedded systems development, most of it designing data networking equipment.  These are hard problems to solve.

What I'm kicking against isn't the long delay in resolving this; instead, it's the apparent lack of commitment to fixing it right now.  All that's being offered are excuses that it's something on the user's end, whether it's supposedly high latencies in the user's network/PC or something else going on in the PC.

I'm sorry, but this is a client-server architecture and NOTHING which happens on the client side should ever cause the server (radio) side to crash (segmentation fault), overwriting profiles and who knows what else.  NOTHING!

When that does happen, YOU HAVE A PROBLEM IN THE SERVER (RADIO).

I totally agree with you that they're not adequately stressing the systems in their labs and that's why they're not seeing the crashes while dozens of us are.  I know for a fact that they do not have any systems in their lab with an SPE Expert 1.3K-FA and DEMI 2m LDPA connected to the radio's two USB ports, as I do.  I offered to help, at least with testing of SSDR 2.0 alpha/beta, but was flatly told that "the alpha testing is closed."

Who, when faced with problems like these, doesn't make an exception to do testing that they cannot do themselves?  I've helped many other teams in the past and they jumped at my offer.

But not FRS!

I didn't pay nearly 10 grand for my station so that I could spend much of my time grabbing my ankles why repeating "Thou shalt not anger the FRS gods."
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
Just booted the pc; turned on the rig, fired up dxlab, sdrbridge, frstack.... and was just about to get started looking around when I heard that annoying tone and saw ssdr drop connection... Rig hadnt been on 10 minutes... long button push to recover... 
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
Banner night;  I now can state there are at least two levels of tone; Earlier had a more subdued not as loud grocky kind of tone.. 

Just now running 4 wsjtx in a relatively cool room (its 73) I had a much louder tone;
The rig starts emitting the tone, I observe its not in xmit mode, so I start loading this page; After a few seconds  ssdr lost comm;
I hit the rig on/off button once, and began navigating here and typing. The rig shutdown; I didnt notice if it ever said "shutting down", and it took probably a good minute. 
I thought Tim had said this wasnt a crash (since the button push "worked"), but the rig wailing and being non-responsive to ssdr, sure seems to me to be a crash... 
Rig had been on 1.5 hours (or however long it was from my last crash)
Photo of Don, VE2HJ

Don, VE2HJ

  • 38 Posts
  • 2 Reply Likes

Here Eric answer to my question on that point .

"To clarify, there are two separate shutdown measures that the radio takes.  If the radio firmware is up and running properly, a single short press of the power button should initiate a shutdown within 5-10 sec.  Otherwise, there is a 60 sec timer in the power control chip that will shut things down if the firmware does not respond.  

The latter is what indicates the firmware was not running properly.  Holding the power button down for ~4 seconds performs the same shutdown as the end of the 60 sec timer.

Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Sure sounds like a "crash" to me.  I think what Tim was trying to say is that a "crash" to them is a case of the radio going down due to a segmentation fault.

I hope this discussion isn't going to degrade into an argument over semantics.  Whether there are different failure scenarios, which there likely are, the radio has gone down and the effect on the consumer is the same.

These must be resolved soon and every step taken to resolve it, even if it means reaching out more proactively to users like us that are seeing this regularly.  They clearly haven't succeeded in recreating the operating environments that we have; otherwise, they'd be seeing these lockups in their lab.  I know for a fact that they don't have my setup in their lab, which consists of a 6700 with both an SPE Expert 1.3K-FA and a DEMI 2m LDPA connected to the radio's USB ports.

If this isn't a firmware problem, then it's a hardware problem and covered under warranty.  If this is a hardware problem and the incident rate is as low as they insist it to be, then try swapping out the radios of 2 or 3 people who see this problem regularly and see if it goes away.  If it does, then take the hit and do warranty replacements.  In the end, the cost of that could easily be much less than the sales hit for failing to act quickly.

The longer they delay, the hotter everyone gets and the more the word spreads that you might want to avoid the Signature Series for a while.  

I am supposed to give a presentation on my 6700 to our local ham club in August.  I'm sorely tempted to give a FULLY honest presentation.
Photo of Roy Laufer

Roy Laufer

  • 446 Posts
  • 45 Reply Likes
Here are the results of a little experimentation with my 6700.

I reflashed to the latest 1.10.16, reset to factory default, and started my 6700 up in the default 20 meter panadapter. It ran crash free for almost a day. I then added a few more HF panadapters on 10M, 17M, and 40M. 

It ran crash-free for another half a day.

I then configured the XVTR tab for my DEMI LPNA and opened a 2M panadaptor and populated it with 5 slices on five different repeater frequencies. There were 3 other panadapters open - 10M, 20M, and 40M. NO profiles were imported, or even saved. No transmissions were made - receive only.

Two odd hours later it locked up and crashed!

(Your mileage might vary.)

73,
Roy AC2GS 
Photo of Roy Laufer

Roy Laufer

  • 446 Posts
  • 45 Reply Likes
I have the exact same setup - 6700, DEMI LDPA, Expert 1.3K-FA!
(I doubt that our mutual problems are merely coincidental.)

I doubt that it is the USB signals (my DEMI is the older one without USB controls, only the 1.3K-FA has a USB connection to my 6700).

FRS used a few technical "tricks" to get their DACs at 2M frequencies. There has been a "bug" on their list regarding 2M slices not showing a signal. I regularly select an input other than XVTR and then re-select XVTR, to get my 2M reception back. This has been documented from a very early version of SSDR and there is no cure in sight.

I think the firmware has to be very mindful of using the 2M slice and if you don't, the whole thing crashes. Since few people use their 6700 as an All-In-One there is relatively little, in the way of complaints.

There are probably other ways to crash SSDR, but using 2M FM repeater receivers seems to be my particular way.

Perhaps with this new data FRS will borrow someone's DEMI LDPA and fix this bug????????????
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Considering its relatively low cost, FRS should buy one or two of the LDPAs for their lab.
Photo of Norm - W7CK

Norm - W7CK

  • 756 Posts
  • 163 Reply Likes
As far as I know, the 6700 is the only rig that can use the LDPA on native 2m.  The 6700 is now 5 years old and I doubt there is much interest in fixing the problems.  I also doubt there will be another Flex rig in the near future with 2m built in.

I've pretty much given up using 2m FM on my 6700.  When having any other panadapters open at the same time it has difficulty changing bands on multiple panadapter with a 2m panadapter open.  The lack of a good all mode squelch, constant bugs showing up when changing bands and no repeater tone suppression of receive signals pretty much keeps me off of the repeaters.  I do use it for 2m SSB though there isn't much activity down there.

I have to count myself as lucky..  I've only had a few lock ups on my 6700 where I was forced to do a hard reset.  Due to the COM (in-use) issue that has been around for months and still not fixed, I am still using an older version of SmartSDR.

I love my 6700, but my patience is starting to wear thin.  When I purchased my rig, I knew the software was not quite complete.  I had no idea I would still be plagued with these types of problems 5 years later.

I have already solved the remote operations by instituting a VPN, so I really don't need that functionality. Bugs have actually kept me from using my rig remotely. Instead I've been using an IC-7100 for remote.  I just want the basic radio to work as it should and to include the basic functions nearly every other radio built in the last 20 years has.  The bells and whistles should follow basic functionality and major bugs.

Just one software developer (or 2 hrs per day) dedicated to clean up and bug fixes should of been able to take care of most of these issues and would have gone a long way in keeping customers happier.  Bug fixes should have been released in between normal software updates.  Instead, we've had to resort to several work-a-rounds.  5 years is too long.

While I'll most likely keep my 6700 for many more years,  I almost hate to admit that I'm now looking for a 2nd SDR.   Next time, I won't be sold on what the rig will be able to do in the future.
Photo of mikeatthebeach .

mikeatthebeach .

  • 480 Posts
  • 82 Reply Likes
Will think twice before any more $$ for Flex from me for any of its products with so many bugs, & lockups with my Flex6700
7 mike
(Edited)
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Norm, your points are 100% spot on.  I also have an ANAN-100D SDR transceiver that's been rock solid from day one, and the operating software (PowerSDR) and firmware for it have been entirely maintained and enhanced by open source volunteers.  These inspired contributors continue to enhance and maintain that code base at an impressive rate.

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.
Photo of Eric Gruff

Eric Gruff

  • 63 Posts
  • 25 Reply Likes
I have (at least in my case with Flex 6700 and latest SmartSDR version) confirmed that the Dimension time sync program was the cause of my problems. I've never had an issue even with many other programs in use (multiple instances of JT programs, HRD, etc.), and was using SPTimeSync successfully. Two weeks ago, I was on a business trip to Europe, and operated remotely for the entire week with no lockups, etc. The radio was still fine when I got home. Then, I installed Dimension for time synchronization since it's automatic, and experienced a bunch of lockups when I was home. The radio looked fine (display had no errors and the usual info on it), but SmartSDR had lost connection, and the only way to fix was to hold the power button until it powered down (occasionally with an error message), and then restart the radio.

I went on vacation a few days ago, and by the time I arrived at my destination, the radio was offline. Fortunately, our housesitter was able to reboot the radio for me, and before that, I uninstalled Dimension. Everything has been great for two days now, and I'm still connected.

So, I realize this is simply empirical evidence, but may help those who are still having issues, at least if the cause is Dimension. It may not be the "fault" of the program, but associated with the changing PC time? A big thanks to posters in this thread that suggested it as a possible cause - it led me to removing Dimension, which appears to have fixed my problem.

73 de Eric NC6K
Photo of Eric Gruff

Eric Gruff

  • 63 Posts
  • 25 Reply Likes
Just wanted to add that I don't have the GPS option, nor was I using 2 M/transverter. I also want to be clear that I am NOT blaming Dimension, but another day has passed successfully with no crashes, which tells me that something about the combination of my setup with Dimension is likely the root cause of my crashes. 

I should also note that when my radio crashed under the circumstances I described, there was no sound (I have heard that high-pitched tone in the past with a 6300 I used to have). Just trying to provide as much info as I can to help everyone solve the issue.
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Kevin, 1.9.13 seems to be stable for those that have rolled back to it.  That's what I was running without any crashes.  Then I added the DEMI 2m LDPA and SPE Expert 1.3K-FA to the picture, both connected to the 6700 via its 2 USB ports.  Support for those accessories required an update to 1.10, and that's when things began to unravel for me.
Photo of Rick W7YP

Rick W7YP

  • 72 Posts
  • 42 Reply Likes
Eric, are you running Windows or IOS?  If Windows, what version and release?
Photo of Eric Gruff

Eric Gruff

  • 63 Posts
  • 25 Reply Likes
Windows 10 Home v1607 release 14383.1198
Photo of EA4GLI - 8P9EH - Salvador

EA4GLI - 8P9EH - Salvador

  • 1780 Posts
  • 547 Reply Likes
I have the 6700, 1.3k, 2m DEMI amp and 70cm demi xvtr. Using both USB ports, one has the demi the other a hub for the 2 1.3k CATs and 1 ThumbDV for dstar.

No freezes.

I use windows 7 64bit.

Anyone with windows 7 suffering the issue? Just adding my 2 cents in a setup that doesn't suffer the problem. I use 1.10.16.
(Edited)
Photo of Dave

Dave

  • 97 Posts
  • 13 Reply Likes
I don't think the peripheral concerns at the cause of any crashes per se.


Here is my system:

6300 direct connect to PC. no other devices connected to computer Ethernet connector.
Del OptiPlex 740 running windows 10.( internet connection through USB WiFi dongle and wireless router)
running in CW mode.
one slice opened
no DAX

Can't get much simpler. 

Since the 6300 has different hardware then the 6500 and 6700, I am less likely to point the finger at the hardware.

My gut felling is this is a asynchronous timing issue in the software. such as missing a flag or missing an interrupt. something along those lines.

At my company the problem closes to the customer gets the most attention. In other words "All hands on deck!" for customer problems and everything else put on hold.


I will say one more thing:

A good reputation cost money, a bad one comes for free.

Dave KB1WOD
Photo of Mike - ZL1MRC

Mike - ZL1MRC

  • 62 Posts
  • 15 Reply Likes
Hi Howard, could you please share the brand / model.  Most interested as I am preparing my station for remote access.  I have a 6500, SPE 1,3K Amp and a Green Heron rotator.   Any assistance would be welcome.

73
Mike
Photo of Eric Gruff

Eric Gruff

  • 63 Posts
  • 25 Reply Likes
Thanks, Howard. That is very helpful to know. I use Chrome Remote Desktop, which is a very low-tech, but surprisingly reliable solution for access to all my radio/work PCs. I will message you privately about the h/w.

73,

NC6K
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3744 Posts
  • 1608 Reply Likes
Yes. You are correct

I ended up double homing my main router with a 4G connection as an alternative Internet route just in case my cable modem route failed. Used it once so far in a year.

The good thing about the data loggers is that they re programmable ...so I sett up one to control my cable modem and main router. The Data Logger pings the Internet and when it loses connection for 5+ minutes, it reboots the. Cable modem and then 5 minutes later reboots the main router. It logs the reboots .. definitely has had to reboot more than once

In one case the Cable Internet was systemically down for 24+ hours but the 4G worked

with all the redundancy that I've built into the station to eliminate single point failureI'm getting very close to 24 /7/ 365 of uptime
Photo of EA4GLI - 8P9EH - Salvador

EA4GLI - 8P9EH - Salvador

  • 1780 Posts
  • 547 Reply Likes
I also advice you to take a look at https://domoticz.com/
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...
Photo of NM1W

NM1W

  • 136 Posts
  • 24 Reply Likes
Another crash flex 6700; went to run an errand and came back to "ssdr has lost comm with the radio".... short push, wait 60 seconds, then redo everything <again>
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..
Photo of EA4GLI - 8P9EH - Salvador

EA4GLI - 8P9EH - Salvador

  • 1782 Posts
  • 547 Reply Likes
Have any of you tried to turn off the radio bridging the contacts on the Rem On RCA in the back of the radio after a crash?
Photo of Andy M5ZAP

Andy M5ZAP

  • 179 Posts
  • 36 Reply Likes
Hi,
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.
Photo of Mike - VE3CKO

Mike - VE3CKO, Elmer

  • 517 Posts
  • 247 Reply Likes
I have not tried this yet, thanks Andy. Does it behave the same as a long button press (5 seconds) ?
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9186 Posts
  • 3548 Reply Likes
Thank you for the continued incident reports and read each one very carefully to see if there is any additional information provided that (a) has not been reported before and (b) might be of any benefit to the engineering team investigating the issue.  And we appreciate constructive efforts to crowdsource and diagnose a triggering mechanism or configuration that affects the frequency of the issue occurring. 

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).

This conversation is no longer open for comments or replies.