Lockup issue and V2.0 / V1.11

  • 2
  • Problem
  • Updated 1 year ago
  • In Progress
Hi,

Is there a fix for the lockup issue in the proposed service release V1.11. And if not  (presumably because route cause has still not been found) has somebody who experiences the problem been used to test V2.0 to determine if the lockup problem carries over to V2.0
Photo of Andy M5ZAP

Andy M5ZAP

  • 162 Posts
  • 35 Reply Likes

Posted 1 year ago

  • 2
Photo of Jim Gilliam

Jim Gilliam

  • 839 Posts
  • 172 Reply Likes

I am not familiar with the lock-up issue nor have I ever experienced it on any of several computers nor my iPad/iPhone. I own two 6500's. Have you tried different computers and experienced this same lock-up problem? It would make me think there is a glitch in your radio.


Jim, K6QE

Photo of David Livingston

David Livingston

  • 121 Posts
  • 27 Reply Likes
Yes I have and the problems continues. I have tried three different computers. Two new computers with new Windows10 installs with all updates.  No other software installed.  With heavy use during a QSO party and with just being left on for and extended period of time. K4CAE. My mobile phone is on QRZ if you would like to contact me.  Regards, David
Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2254 Posts
  • 879 Reply Likes
Changing computers likely won't help. For sure this is in the radio firmware. 
Photo of Andy M5ZAP

Andy M5ZAP

  • 162 Posts
  • 35 Reply Likes
Hi Jim

It is the flex locking up, it doesn't affect all users and has been discussed at great length in other threads.
(Edited)
Photo of Jim Gilliam

Jim Gilliam

  • 839 Posts
  • 172 Reply Likes

Maybe it is a heat issue on your radio. I wish I had followed this issue on other threads. Hope you get it resolved. Since it seems to be related to a few select radios, perhaps Flex would want to use your radio to help diagnose the problem to see why this occurs on a few select radios. Perhaps some of the chips are not up to spec and no software can fix this possible hardware problem.

Jim

(Edited)
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9148 Posts
  • 3467 Reply Likes
The truthful answer is "hopefully".  We have not definitively found the root cause for the relatively small percentage of radios experiencing the crashing problem (the numbers do not minimize the severity, it just makes it much harder to find root cause when it isn't systemic).  If we had found a root cause, the fix would have been released immediately.

Whenever a major feature is added to the software, like SmartLink, it touches many different areas in the code and through whitebox testing exposes weaknesses or issues we may have overlooked.

Through the course of adding the new feature, we address those areas and make fixes and optimizations along the way.  We affectionately refer to this as "under the covers" fixes; things that have no visual component but improves stability and performance.  It is the serendipity effect.  This happened a lot when working on contesting enhancements in the past 2 minor releases.

We have done a lot of "under the covers" type work for 2.0.  Recent alpha testing for 2.0 has provided some strong empirical evidence that one or a multiple of fixes implemented as part of the work done for SmartLink has greatly improved radio stability.  It is partially due to this fact that after 2.0 is released, we will use its code as the basis for the 1.11 maintenance release.  Essentially it will be 2.0 code fixes with the 2.0 specific features removed.  Our expectation is that this will improve the stability of the radio and be a remedy for those experiencing periodic crashes. I anticipate that we'll share 1.11 beta releases with some who have reported the problem and are good candidates for testing.

If the crashes (not disconnects, which has a different problem pathology) continue for some, we'll reopen our investigations and dig a little deeper on those specific issues. 
Photo of NM1W

NM1W

  • 133 Posts
  • 24 Reply Likes
Its very disappointing that DAX will continue to be unreliable in V2.0.... It has yet to be a viable solution, with its frequent receive corruption and xmit corruption. I would hope Flex has been able to repro the frequent DAX issues....
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2767 Posts
  • 610 Reply Likes
mm1w
You know for sure dax will be unreliable?
Photo of NM1W

NM1W

  • 133 Posts
  • 24 Reply Likes
VA3WTB - per Tim's commetnts: "For SmartSDR v2.0, DAX has not undergone any changes.  It is, however, one of the items we have scheduled to address in a future version of SmartSDR v2.x."

Since it hasnt changed, I expect the same problems; FRS had acknowledged the DAX issues.
Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2254 Posts
  • 879 Reply Likes
I only really have occasional problems with DAX, and nothing a reboot won't fix, even on production versions. Yes there are issues with occasional corruption but nothing like some want to make it seem. But that's just me I guess,
(Edited)
Photo of NM1W

NM1W

  • 133 Posts
  • 24 Reply Likes
When running 4 slices on wsjtx one gets to see the dax issues fairly often..
Rebooting due to dax issues, or radio crashes is a PITA. (having now had 4 radio tonal crashes in the past 4 days while only running cw, nothing advanced like using dax or wsjtx...)
Photo of Steve Gw0gei

Steve Gw0gei

  • 192 Posts
  • 50 Reply Likes
Let's hope v2.0 comes out soon, so this wider testing can commence and those of us not wanting wan can wait as little as possible for the subsequent 1.11 maintenance release. I will be travelling tomorrow to a host station with a pair of ft5k radios in antenna diversity mode for 40m cw band slot as part of the rsgb gr2hq team in iaru contest. My 6300 is only being used for casual operating and the odd domestic contest at present until the random crash issue is solved. Tried selling it over the last six months but no takers despite reducing the price several times. On the plus side my wife is happier as I am spending less time on the radio! That may change shortly though as I have just taken delivery of one of the first production models of Linear Amp Uk 's new 1.2kw full duty cycle solid state 2m pa - delivered on time , 24 hours after I paid the emailed invoice and three months after my no deposit order was taken. Will be visiting their workshop on 20th July to see the pre production model of the new solid state fully auto lan enabled 1kw hf/6m pa under test - with the state of the uk pound value it might turn out cheaper to put two of these new amps on my a and b inputs on my 4o3a antenna genius than a single power genius.
Photo of Paul Mandel

Paul Mandel

  • 82 Posts
  • 21 Reply Likes
"It would be resource wasteful to have our engineering team split in order to work on two code bases at the same time.  Instead, we address problems reported on 1.x by testing for them using our 2.0 code base and then address anything we discover in 2.0.  We'll then take the 2.0 code base and merge it into 1.x code base as 1.11 when 2.0 is released.  This way, the 1.x customer receives a more comprehensive set of code fixes and improvements.  In this particular case, it will take a little longer before we got a 1.11 fix out than is ideal, but it will be a better release than if it was released last month, as the fixes we implement today will be in the 1.11 code."

Tim - contrary to your statement this is how companies write new versions.  One team keeps working on the old code so that the customer base stays loyal and the other team develops the new code  incorporating the changes that the maintenance team finds and fixes if appropriate.  
 
"... We'll then take the 2.0 code base and merge it into 1.x code base as 1.11 when 2.0 is released.  This way, the 1.x customer receives a more comprehensive set of code fixes and improvements.  In this particular case, it will take a little longer before we got a 1.11 fix out than is ideal, but it will be a better release than if it was released last month, as the fixes we implement today will be in the 1.11 code."

Not that I expect Flex to take my advice (or get an answer) but why not let the license manager decide what people have paid for and what they have not.  Then you will truly not have to release two versions,just download the current version, put in your license ( or no license) and you will have the options you paid for and nothing more.    

If you detect a change in my tone it is that I have reached my personal end of the rope after your post earlier today.    It just took me right off my support of Flex pedestal and sent me to the why do I want to give this company one more dollar side of the fence.  My 6500 is less than 4 months old, I have never complained about buying only to have it obsoleted two months later.  My choice to buy that close to Dayton and I knew the risk, but to basically be put in the category of 'We'll get to you later' is an insult.  

One last question that I do not expect to get a YES as an answer. Since you seem to have eradicated what is possibly the BUG are you willing to give a release date or reasonable window? 


Paul -W4PGM
Photo of Andy M5ZAP

Andy M5ZAP

  • 161 Posts
  • 35 Reply Likes

Gerald,

I understand you are struggling to reproduce the problem (as I am a sceptic / Realist I also think the development of V2.0 and the new hardware has taken priority to fixing the problem), unfortunately the route of hoping that the V2.0 changes will hopefully inadvertently fix the issue is a bit of a long shot.

I also challenge the statement it affects a tiny minority of users.

I will as Paul purchase the V2.0 and if the issue is not fixed be returning the radio under warranty and looking for a refund of my V2.0 purchase.

I am a believer in voting with your feet!

Photo of Gerald - K5SDR

Gerald - K5SDR, Employee

  • 796 Posts
  • 1444 Reply Likes
Paul,

Thanks for your respectful response.  We have made many bug fixes and code performance enhancements in v2 that we feel are likely but not guaranteed to resolve the lock up problem you are having.  We feel that getting v2 into the "wild" is the best way to find out.  Assuming success, then back porting v2 to v1.11 will be much more timely than looking for the needle in a haystack on v1.10.  If v2 does not resolve the issue, then we have to go back to looking for the needle.  

As to obsolescence since all FLEX-6000s share a common software architecture and SmartSDR continues to be enhanced, it extends the life through the ability to "get a new radio with each update."  I didn't make that up - customers did.  I use my 3 year old iPad every single day and I don't consider it obsolete because I add new apps all the time and most of them get automatic updates all the time.  It does everything I need and gets more useful all the time.  I just got a new update of SmartSDR for iOS on my iPad this afternoon.

Andy,

Fact correction new hardware has taken virtually no resources away from software development to date.  They run the same SmartSDR.  Yes, v2 has taken resources but those resources have been applied to bug fixes and performance enhancements on the evolving code base.  That work we hope will fix the problems you are having.  We won't know until we get it out there.  

73,
Gerald
Photo of Andy M5ZAP

Andy M5ZAP

  • 161 Posts
  • 35 Reply Likes
Hi Gerald,

Thanks for reply, fact correction accepted.

Now my turn :)

Fact correction - Throughout this problem flex have stated that the lockup issue has never been experienced by any of you testers, however Ria has confirmed on 1.10 she experienced lockups dropping in frequency to weekly lockups and even more worryingly that these have reduced but are still present in V2.0 software

Does this not put into doubt your newly adopted policy of hoping that V2.0 will fix the problem. Your only software tester experiencing problems on V1.10 still experiences lockups on V2.0 ? I would call that 100% problem carryover.

Could you not exchange out Ria's hardware to see if it is hardware related and give you some hardware known to exhibit the issue to test in your Lab? It could be unrelated to hardware but at least exchanging the hardware would prove or disprove that hypothesis.

Like Ria I have experienced varying levels of lockup, Initially every day then a period with no lockups now weekly with sporadic periods of 3 or 4 in close proximity.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9148 Posts
  • 3463 Reply Likes
We have no verifiable evidence that your lock up issue is the same as the ones experienced by alpha testers.  Since they are running alpha code you cannot directly equate your experiences to those of alpha team members - you are not running the same code.
Photo of Andy M5ZAP

Andy M5ZAP

  • 161 Posts
  • 35 Reply Likes

Tim

Direct quote from Ria

"With 1.10 release version my experience was similar to yours although not multiple times per week. More like once a week."

Ria had lockups on 1.10.16 release version not alpha or beta or RC

Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2254 Posts
  • 879 Reply Likes
I am running alpha software, and I have had the radio hang in the past but with the 2.0 code these are kept to a minimum now. So if that carries to 1.11 it should be fine.

No promises (I can't make them anyway), just my observation. I also hope that they have definitely found and corrected the root cause. 

Ria
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2755 Posts
  • 607 Reply Likes
Paul, my Flex 3000 still works fine with fire wire and PSDR still works great on computer, it has been discontinued for a time now,,I don't see it as obsolete because it still does everything it is supposed to.

And the 6500 will still use all the same updates as the new radios,,I guess it is how you see it.

Because of that, I just bought a 6500.
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2755 Posts
  • 607 Reply Likes
Ria, some of us were just talking about on 40M about 10 min ago,,we want to know why your so smart. lol
Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2254 Posts
  • 879 Reply Likes
I don't know if I am all that smart... I do know a lot about software, I am immersed in it 24x7...
Photo of Rick Ciotti

Rick Ciotti

  • 12 Posts
  • 4 Reply Likes
My 6500/Maestro have been in operation daily since 12/16. No hangs, just a few disconnects between the two.

For my logging PC there is a Netgear Gigabit switch between the Maestro and radio. Not sure if this helps anything...it works FB so it will remain configured this way.

Rick W3DIY
(Edited)
Photo of David Livingston

David Livingston

  • 121 Posts
  • 27 Reply Likes
RIA,

What do you call a minimum number of lockups??? When I am running remotely I can not tolerate any issues with the radio locking up. No one will be at my home to do a hard reboot of the Flex radio. No problem rebooting the computer, but that does not fix the Flex locking up issue which you confirmed it was in the radios firmware.

PS mine locked up twice yesterday during the ARRL DX contest

If version 2.xx does not fix the problem I will be asking for a replacement of my 6700 under warranty as it appears I have a radio that gives this problem to only a very small group of owners.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9148 Posts
  • 3467 Reply Likes
Please let me remind everyone of the Community's guidelines for posting.  Here they are for your convenience.

...when using the Community always show respect to others regardless of their opinions. Give people the benefit of the doubt, just like you would if talking to them in person. Posts that include personal attacks, overtly negative comments, non-constructive criticism, falsehoods, defamation of character, libelous speech, or gratuitous profanity will be removed, as they do not contribute to the community atmosphere we want to maintain. Any pattern of poor behavior may result in losing your Community posting privileges.
Photo of Craig Williams

Craig Williams

  • 80 Posts
  • 32 Reply Likes
I can't help myself. Will V2 work on my Yaesu FT-101?
(Edited)
Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2254 Posts
  • 879 Reply Likes
No. Sell me your useless rig for $5.
Photo of Michael Aust

Michael Aust

  • 135 Posts
  • 32 Reply Likes
Just upload v2.0 via the USB port on that Yaesu FT-101 !! Hi ! Hi !
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2769 Posts
  • 610 Reply Likes
I see no reason why not...
Photo of Michael Coslo

Michael Coslo

  • 812 Posts
  • 195 Reply Likes
Out of curiosity, Paul - have you tried running SSDR on a different model computer? Having had the problem one time, then gone away because of a Windows update and reinstall, as well as Flex having difficulties finding the problem, I'm conjecturing that looking for the problem in radio hardware might be  a goose chase.

Side note. Those multitudes of hams who have the same problem as you - it might just help Flex if they complained. Otherwise they simply accept what I think is a computer issue that might be solvable.
Photo of Paul Mandel

Paul Mandel

  • 82 Posts
  • 21 Reply Likes
Thanks to all that are altering me to a message but it truly not necessary.  I guess I should reinstate the RSS feed until this thread closes.

Michael-Yes, three specifically.  My normal computer that runs the radio, logging, WSJT-X and other programs. It runs Windows 7 Ultimate and it is an AMD.  A brand new windows 10 i5 with only the Windows operating system and SmartSDR and an i7 Laptop with Windows, minimal  other software, SSDR but no other logging  or Data programs, but it did have Office 13 installed.

I documented three types of crashes.   A Quit of SmartSDR  seemingly due to COM port issues. This always throws an error on screen and the SSDR does not stop until the error box is dismissed.  As long as I used the Com Name Arbiter program once or twice a day, move the Flexcontrol to a higher COM port ( COM240 and Green Heron controller to COM230) I can keep those to a minimum.  The second is a freeze of the 6500 but SSDR does not quit or freeze.  The radio will not shutdown unless you do a long button push or a power down of the power supply;s sometimes it is only a power down that works.  If you do not reboot the computer the radio may not show in the chooser when the radio comes back online.   The third has a tone, the radio will not shutdown with the button, SSDR does not quit or freeze and never shows up if the computer is not rebooted, also.   

I have also changed power supplies and put the old supply om the bench to see if there were sags, or too much ripple.  While it was there I used an Alinco 330 switching supply but had the same issue. While the 70A Astron was on the bench I tested all the pass transistors,replaced two cracked mica, cleaned and properly pasted each.  Beside the variable pasted application which is normal with Astron supply's I found nothing wrong with  the supply and it runs rock solid.

I have run the radios directly connected to the computer to isolate the network, changed to a different switch, run it on an isolated network without internet access as well as our normal household network.  I found no difference in the freezing or stoppage.

Tim put logging software on but after the first crash he felt that they could not learn anything since it was a kernel crash and the logging did not significantly help. It was only there for the one crash.   Tim if I misstated please correct my statement.

The radio does not have to be in any particular mode but it seems to happen more in CW and Data, especially Data.    For the longest time I assumed it was a WSJT-X issue and not the radio.   I did downgrade to 1.9 but the tired of testing and after a few Flexcontrol errors I just gave up.   

The up time before crash is minutes, to days, to a little more than a week but never two weeks.   There does not seem to be a correlation between being off for an extended period of time or run for an extended period of time.  It has crashed in all three modes CW, Data, SSB (both U and L) and it does not seem to be band related.    There is not any correlation that I have found that causes multiple crashes in a row or just a single crash with an extended time before the next crash.

I have been repairing radios and formerly TV's since the mid 60's and still do repairs today for the local ham community on any radio that I can still see the parts.  This is less and less each day.  I lost count of how may HeathKits I built in the 60's but I did build the color TV when I was 16.   I have four patents related to SCSI drives and drive connectivity and have been around electronics as both a hobby and sometimes professionally for most of my life. 

If anyone needs any other information about the crashes just drop me a line at my call at arrl.net.  
Photo of Michael Coslo

Michael Coslo

  • 812 Posts
  • 195 Reply Likes
Just as a differential diagnosis, would we bet our entire fortunes that it is not a software issue. 


And since it is not supposed to be anythign other than firmware, there are two options ( to my thoughts. Option one is that the IC that his firmware  is defective, and option two is that he and some other hams have a defective firmware burn. 

What am I not seeing here? Even if it cannot be reproduced, you would take a person who has the problem and by hook or by crook, replace the firmware and solve the problem. If that doesn't solve the problem.......


then again, if it isn't software, change out the radio and the problem is then a lock to go away, correct? 
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2769 Posts
  • 610 Reply Likes
What does your panadapter do when it crashes?
Photo of Paul Mandel

Paul Mandel

  • 82 Posts
  • 21 Reply Likes
Most of the time there is a message that SSDR has lost communications with the radio (actually never wrote down the exact message) but once or twice SSDR froze with the radio also in transmit.  Signals were displayed (Frozen state) and SSDR had to be terminated with the Task Manager.  Power out was ~2W using WSJT-X on 30M.  Antenna a SteppIR vertical about 60 feet from the house.  
(Edited)
Photo of Rick W7YP

Rick W7YP

  • 69 Posts
  • 42 Reply Likes
Since many people, myself included, didn't experience this problem until after upgrading to 1.10 AND the crashes ceased after back-rev'ing to 1.09, it is most certainly a firmware bug and not a problem in the radio's hardware (e.g. a 'bad' FPGA).  I've seen such version level related problems many times before in my 30+ years in embedded systems development.  We often found the problem by just doing a 'smart' code-base comparison, focusing on the areas that changed which might account for the behavioral difference.  This can be a lengthy and boring process, however.  Would someone from FRS confirm whether or not this has been done?
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3541 Posts
  • 1396 Reply Likes

Out of curiosity... V1.09 works,

But V1.10 Locks Up occasionally in an irreproducible manner for a very few people.

(None of the many Alpha's have ever seen it and we get to test lots of buggy stuff)


Why do they not just revert to V1.09 and enjoy their radios until V2.0 is released and they can test to see if it solves their problems?

Perhaps I am missing something but I really do not understand the urgency to go from 1.09 to 1.10


Example...

My current 2015 Model S Tesla has 1 autodrive camera and surrounding sensors which enable Level 3 Auto-drive. -- it makes driving to LA painless...

2017 Model S Tesla has 8 cameras for Level 5 Autodrive. 

While V8.2 Tesla Software can enable Level 5 Autopilot on 2017 models, my car is stuck at V8.1 on Level 3 because it lacks cameras to be fully autonomous

HOWEVER My Level 3 Autodrive Tesla is already far more advanced (really cool) than any other equivalent car on the road and while I would love Level 5 - my car wont do it..

I just have to wait until 2018 when my lease is up to be able to try the new features.


How is this any different?


Photo of David Livingston

David Livingston

  • 121 Posts
  • 27 Reply Likes
Version 1.09 does not allow the USB ports to operate. I purchased a SPE 2K with the correct USB cable from SPE. The upgrade to use the USB ports is only supported in the latest release of SmartSDR. As long as the Flex continues to operate it works flawlessly on all bands and slices. I love the interface with the USB ports on the Flex, but these continuing locks are a serious issue with me.
(Edited)
Photo of Burch - K4QXX

Burch - K4QXX

  • 358 Posts
  • 59 Reply Likes
Just to clarify the DEMI 2MLDPA 2 meter amp comes in two versions.  If you order it with the "remote" option, the only way to use it is with the USB cable hooked to the Flex and you control the amp through SSDR.  I had to wait several weeks to use the amp until 1.10 came out.  If you didn't order with the remote option, it doesn't matter what version of SSDR you use since it doesn't have the USB control cable.
Photo of Rick W7YP

Rick W7YP

  • 69 Posts
  • 42 Reply Likes
Howard,

I pity the poor guy/gal who ends up with you sitting on their jury if you think that I indirectly implied that I left the DEMI in the box until V1.10.  You'd be convicting them on 'evidence' no one else saw or heard.  There's no way that can be read into my posts; in fact, I didn't order the DEMI until after 1.10 was released.

As for my SPE amp, yes, I'm aware that I can control more of its features via DDUTIL; however, that would only be useful to me if I could reliably remotely operate my 6700.  Having had it hang twice in TX mode, my attempting to operate it remotely at this time would be grossly irresponsible.

To insist is that 1.10 didn't cost me anything is too ridiculous a statement to deserve a reply.
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3541 Posts
  • 1396 Reply Likes
First. You clearly rarely remote or you would know that to operate safely you need to be able to remotely reboot power to all devices.

Second. U will likely have to wait until after V2 is tested in the Wild before you know if it cures the issue and they backport it to V1.11for ur Free upgrade that u paid a lot of money for.
Photo of Rick W7YP

Rick W7YP

  • 69 Posts
  • 42 Reply Likes
Howard, you sure seem to know a lot about me even though you don't know me.  I guess you just can't stop making rash assumptions at this late stage in life.

Yes, I've remoted many times before and have the ability to remotely turn on/off power to the devices in my shack; however, one of my two TX hangs occurred shortly before a brief Internet outage that would have made remote power reset impossible.  Fortunately I was in the shack for that one.

I know that I can get a bit more sophisticated and spend even more money to add more hardware or upgrade my hardware to support wireless connectivity as a backup to the Internet and maybe even a hardware watchdog to detect an apparent TX hang and automatically reset power to the radio.  But when I've never had to do that for ANY transceiver costing far less, why should I have to do it for a radio for which I paid $8100?

Rick
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3541 Posts
  • 1396 Reply Likes

I double homed my systems about a year ago after an Internet Failure and am now using both a cable modem and a MIFI connection just to forestall the eventuality of another Internet Failure.. .  So far that failover has worked flawlessly

However my most recent remote failure was caused when the Digital Logger Web Switch controlling power to 8 different shack devices failed. so now I am duplicating that as well... 

One can Never have too much redundancy when remoting.


"why should I have to do it for a radio for which I paid $8100" 

Sound like me ....

"why did I have to wait for BMW to figure out why my $125+K BMW burned a quart of Oil every 500 miles"

...  BMW did not even try to figure it out or acknowledge the issue but just gave me free cases of oil. 

I eventually dumped the BMW for a Tesla  - no oil...and a bit less expensive...

At least Flex unlike BMW has acknowledged the issue and expects that their assumption that the new code in V2 might fix the issue so that it can be backported to V1.11

In the meantime you will just have to wait and see if the fix works.

Being that you claim to be an expert in embedded systems and I would dare to assume software as well you probably know that no amount of kvetching will speed up the process of getting the software finished and working.

Right now the Alphas are working very hard trying to break V2 which is getting very, very close but no cigar to a final release candidate..

Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2769 Posts
  • 610 Reply Likes
Since Flex has not been able to duplicate this problem,,and none of the Alpha's have seen it,,and only about 1% of customers see it, it would have been great if a customer could have sent their radio in to Flex and have them see it happen. then maybe they could find something out.
Photo of David Livingston

David Livingston

  • 121 Posts
  • 27 Reply Likes
Ria seems to of had lockups even on her alpha V2.xxx
Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2254 Posts
  • 879 Reply Likes
not with the same frequency as 1.10. With that said, my experience is probably not going to mirror yours but let's hope 2.0 and 1.11 maintenance release will fix it.
Photo of Andy M5ZAP

Andy M5ZAP

  • 162 Posts
  • 35 Reply Likes
Hi Ria
Does that mean that you had a high frequency of lockups with 1.10 or even a low frequency of lockups
Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2254 Posts
  • 879 Reply Likes
With 1.10 release version my experience was similar to yours although not multiple times per week. More like once a week.

There could be multiple things at play though. For example I am not using USB cables anymore (sold my amp, getting a power genius). That could factor in but I'm not really sure.

Either way this variation is why Gerald wants to release 2.0 first then when that is proven and stable the dev team will backport the fixes to the 1.x branch (not the exact process but you get the idea).

So understand they have a method to all of this.
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3541 Posts
  • 1396 Reply Likes
First. You clearly rarely remote or you would know that to operate safely you need to be able to remotely reboot power to all devices.

Second. U will likely have to wait until after V2 is tested in the Wild before you know if it cures the issue and they backport it to V1.11for ur Free upgrade that u paid a lot of money for.
Photo of Al / NN4ZZ

Al / NN4ZZ

  • 1706 Posts
  • 580 Reply Likes
HI Howard,

RE: "Why do they not just revert to V1.09 and enjoy their radios until V2.0 is released and they can test to see if it solves their problems?
Perhaps I am missing something but I really do not understand the urgency to go from 1.09 to 1.10"

I get the lock but only if I use the tuner, so I quit using it.  (seems like there is some timing issue in the firmware that causes the lockup in my case) but to your question.  I used to use DDUtil to control my amplifier and antenna switches.  With V1.10.x I converted all the peripheral control over to the USB feature.   

Going back to DDtil is more trouble that it is worth since I can figured out that not using the tuner fixed the problem for me.  Others may also not want to revert if they are also using the USB port feature. 

Regards, Al / NN4ZZ  
al (at) nn4zz (dot) com
SSDR / DAX / CAT/ 6700 -  V 1.10.16
Win10
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3541 Posts
  • 1396 Reply Likes

Hi Al

Yes.. USB seems simple and elegant...BUT

As you know I remote much of the time so I need the FULL control that DDUTIL gives me for my SPE, SteppIR and Rotor.. and until that level of control is available via USB I have to stick to DDUTIL as it is far to dangerous to operate remote with only Band Data.

I understand that adding more control features to USB is under consideration but clearly no announced plans yet


I guess that they need to wait until v2 is released - close but no cigar

Photo of Al / NN4ZZ

Al / NN4ZZ

  • 1706 Posts
  • 580 Reply Likes
Hi Howard,
Totally understand you need for more control capabilities than currently available in the USB feature. In my case for local operating I only need band data so the USB feature works for me . And eliminating a third party program simplifies things although I agree DDUTil is an excellent program and works very well.

More control via the USB ports seems to go hand in hand with the remote WAN / Smartlink capability so it seems logical that remote users will "vote it up."

Regards, Al / NN4ZZ
Photo of David Livingston

David Livingston

  • 121 Posts
  • 27 Reply Likes
I find the USB cable I purchased from SPE works flawlessly. If there is something it does not do properly I can not find it. No problem with the tuner in the SPE all automatic. The SPE changes antennas (6) without additional switches. The SPE controls the power output from the flex in three preset modes of power - Low, Mid, or Max. Works flawlessly with the changing of slices and all bands.  Please tell me what does not work using the USB ports and proper cable... K4CAE... Also is DDtil ready for V2.xxx of SmartSDR??? PS, I am only interested in controlling the SPE 2K-FA.
(Edited)
Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2254 Posts
  • 879 Reply Likes
The only thing I would say DDUTIL does better is the SteppIR control and also tube amps using auto drive
Photo of Al / NN4ZZ

Al / NN4ZZ

  • 1706 Posts
  • 580 Reply Likes
Hi Ria,
Here is another place where DDUtil out shines the rest.

I used to use DDUtil to control one of my FlexControl knobs.  The MACRO capability from DDUtil was superior to what is offered in SSDR or SDR-Bridge.   You could program the buttons to do many neat things that are not available in SSDR.   But since that was the only thing I was using DDUtil for, I decided I could live without those features and eliminate running one more third party program.  

It would be nice to see SSDR offer that MACRO capability for the FlexControl.  Maybe some day...

Regards, Al / NN4ZZ  
al (at) nn4zz (dot) com
SSDR / DAX / CAT/ 6700 -  V 1.10.16
Win10
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2769 Posts
  • 610 Reply Likes
Then that is the short answer. If people do not want to revert, then just wait and see..simple,,all done
Photo of Tony Taddeo

Tony Taddeo

  • 60 Posts
  • 28 Reply Likes
The only time I have had a reproducible lockup is due to user error when using Full Duplex mode (FDX) and not having sufficient isolation between the RX and TX antennas, resulting in an (understandable) RFI issue within my 6700.

It is easy to accidently have FDX on without knowing. Is this the cause of some of these lockups?
(Edited)
Photo of Tony Taddeo

Tony Taddeo

  • 60 Posts
  • 28 Reply Likes
I only use FDX mode when making audio adjustments using transverter level power. Occasional, I TX on an antenna by accident at normal power levels - my bad...(smile)

There was at least one person having lockup issue while using the antenna tuner. TXing while FDX on and not sufficient isolation between the RX and TX antennas?

"This lockup just happens and nobody really knows what caused it to happen."
Should we call a priest ?

The support given by Flex Radio is amazingly good for an amateur radio supplier. They will get to the bottom of it.

Tony
VK5TT
(Edited)
Photo of k3Tim

k3Tim

  • 831 Posts
  • 162 Reply Likes
Maybe Gerald should put on the sack-cloth and crawl on his hands and knees from Austin to Dallas in the noonday sun while being flogged by 4 Vestal Virgins and chanting "debet figere cimex"

I buy a ticket to see that.  

:-)

The FRS  support has been amazing with the prez posting over the holidays and updating as much as he can. Tim's support is also good with him and the folks out here answering questions quickly.
Once 2.0 hits I have a feeling it will be nice to have the networking experts that populate this group around.

Regards All
k3Tim
(Edited)
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2764 Posts
  • 610 Reply Likes
During your long weekend, 4th of July weekend, some were telling Gerald to have a nice long weekend, he spent most of it on here it seems. I asked him if he is taking the weekend off, he replied, NOPE
Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2254 Posts
  • 879 Reply Likes
There's really no networking knowledge needed for 2.0. Just enable UPnP and it will work automatically. If you don't like UPnP for security or other reasons, the manual port forward is pretty straight forward.

Ria
Photo of Michael Aust

Michael Aust

  • 135 Posts
  • 32 Reply Likes
Been running 1.9.13 no  issues, but get that to crash ( completely freeze ) on my Windows 10 notebook Acer ( No Ethernet Port ) only has USB port, if I share an USB to Ethernet Port Adapter to connect to Flex6700 with a USB hub that has other USB devices attached.

When I just have a USB to Ethernet Adapter all is well, but when I add a mouse,
Flex Knob and sit back and wait, after some time, SSDR will freeze up ! just with 1 pan-adapter/waterfall open.

For what that is worth, then again if I have 8 pan-adapters/waterfalls going on and need to with V1.11after a while I get the lockup as others have described.
Photo of John - K3MA

John - K3MA

  • 269 Posts
  • 77 Reply Likes
I mentioned it before but will mention it again.  I have seen the random lock-up issue on two different stations.  One with Flex 6700 on a Window 7 computer and one with Flex 6500 on a Windows 10 computer.  The lockup have occurred when using the radio for TX, when listening only and when not using it at all.  The Flex 6700 station has been on 24/7 for about three years.  The Flex 6500 station has been on 24/7 for about a year.  Neither station had any lockups prior to the latest software release.  Each time there has been a lock-up I have looked at the operating conditions and cannot find any common source/condition.  So I can understand how it can be hard for Flex to diagnosis.  Since they have a representative that read this forum and have already acknowledged the condition I see no reason to continue to bring it up or go further with reporting it.

One thing I would add to the discussion is that....would it not be good customer service if Flex was to provide a copy of V2 to M5ZAP for testing to determine if indeed the issue has been fixed in V2 as they hope.  It seems to me that would verify if it is or is not fixed.  Would satisfy M5ZAP's concerns.  Would not cause a customer to have to purchase V2 just to see if something is fixed or not.  If it works would provide a fix without the customer having to wait longer.  Would shut up all the Flex fan boys who seem to constantly criticize those that have issues.  It would seem like a win win to me and so simple to do.

PS-My comment about the Flex Fan boys is not a joke.  I personally do not post on the forum much due to the regular and predictable responses that come from the half dozen or so regular posters that seem to have a need to talk on Flex's behalf and feel that they have to defend Flex from every issue or negative comment.

John K3MA
Photo of Mike - VE3CKO

Mike - VE3CKO, Elmer

  • 350 Posts
  • 133 Reply Likes
Providing an unreleased product to a customer who is not on the Alpha team would set a dangerous precedence. Why him and not others who have problems hoping to get fixed? What problem and who decides which party to send the unfinished software to?  They have an Alpha team who have signed an NDA for a reason.

As per "defending" Flexradio, if a poster goes out of their way to trash another poster or Flexradio then complain about the backlash, sounds kinda familiar to what we see in the news every night. Presenting concerns and issues in one thing that is promoted here but certainly disrespect is not.
Photo of Rick W7YP

Rick W7YP

  • 69 Posts
  • 42 Reply Likes
Mike,

Why would that be dangerous?  I've spent 30+ years in embedded systems development and we did it all the time.  Doing so helped us to quickly identify and resolve issues that only showed up in certain applications/environments and it's what SERIOUS debugging efforts do when they can't reproduce a problem in the lab or among their 'official' test team.

None of those customers objected to signing an NDA and none of our customers who weren't included felt left out.

Rick
Photo of Mike - VE3CKO

Mike - VE3CKO, Elmer

  • 350 Posts
  • 133 Reply Likes
Rick did you have a public forum for customers to voice concerns and badmouth the company? 30 years ago there was no live interaction you have today. You will get a few complaining why they were not chosen. Flex has a good team of Alpha testers in place and a reporting procedure they are quite comfortable with and why upset the apple cart in this late stage when release is imminent. Training a massive group of new testers would result in a lot more overhead to sort out useful reports from complainers. I have no clue as what measure have or have not been taken to try to duplicate this issue. You can't fix what you can't duplicate. I must assume it's not just radio related but a combination of a setup like O/S, 3rd party software installed, hardware connected to both radio and computer, just to name a few. Mine may go for weeks or a few months without a lockup then get 2 in one week. So let's say I get to test it on my setup. Then nothing happens for a few days, then a few weeks or a few months. At what point does it pass?
In my case it seems to happen days after I open up 2m and 6m, but then it happens the odd time overnight. It could have been a power supply fluctuation or brief interruption and no way to eliminate that with a power line monitor that I don't have. Guess what I'm saying is I certainly can't duplicate the problem so I will wait to see if v2.0 improves or eliminates this issue.
(Edited)
Photo of Rick W7YP

Rick W7YP

  • 69 Posts
  • 42 Reply Likes
Mike, it's true that we didn't have quite the same interactive forum-hosting tools that exist today; however, we did have email lists and various flavors of "bulletin boards" which performed a similar function.  Yes, there were whiners who weren't really helpful but we got a lot of useful feedback and did catch a lot of bugs that would have persisted into a new release by opening up late beta testing to those who saw those problems on a fairly regular basis.

In some cases we sent someone to the customer location; in others, we installed remotely accessible debugging software.  We saved immeasurable embarrassment and support costs by preventing a problem we'd been hoping had disappeared in a pending new release from being pushed out to an already frustrated community.

Several of those who see the crash frequently, myself included, have many years of experience in embedded systems and wouldn't require training.  We've offered our assistance and were turned down flat.  I've never worked for a company that ever would or did turn down such offers when we had a difficult and critical bug nipping at our you-know-what.

And, no, this crash isn't due to a combination of factors external to the radio.  It's a problem in the radio which results in a segmentation fault.  I see it frequently even though I have a conditioned UPS and fast dedicated 6-core PC controlling the radio.

I hope it is gone in V2.0 and obviously have no choice but to wait and see if that proves to be the case.  If not, where do we go from there?  They're talking about a back-port to 1.11 next, but that will mean three versions (1.10, 1.11, 2.0) that have the problem.

That would simply make it seem more apparent that the corporate message is that the minority who are experiencing the problem just aren't important enough to do whatever it takes to resolve this nasty issue.

Rick
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2769 Posts
  • 610 Reply Likes
That would simply make it seem more apparent that the corporate message is that the minority who are experiencing the problem just aren't important enough to do whatever it takes to resolve this nasty issue.

I understand your a bit bitter not taken up on your offer. This comment above would be inconsistent with what we have seen and know of how Gerald runs things. I with I had a buck for each person over the last few years saying they no more about the radio and the software than Flex staff does, or explaining to Gerald how to run a company.
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2769 Posts
  • 610 Reply Likes
John,
Gerald has said he expects to have some who are having this problem test V2. Before release.

The so called fan boy thing,
Everyone has trouble at some point as a Flex owner. It is how people handle their frustration that can be a problem. And everyone are different.
It is the misleading and unfair comments made at times that get people to defend a great product.
It is good to explain our problems on here and see if someone can help,,but when it comes to all out trashing the radio,,and, or the Flex team? then yes I think it may be time to step in. I don't see this as defending Flex as much as defending this community that is here for all of us.

Tim has left guidelines here many times as to proper conduct, that includes the way we vent as well. Respect?