6500 / Win SSDR - Frequent loss of band - any ideas how to prevent?

  • 1
  • Question
  • Updated 4 months ago
  • (Edited)
I continue to have a problem with 40m band selection. I can do a hard reset to recover the situation but all too often the profile appears to become corrupted and the 40m slice that used to work fine is no longer accessible.

On searching the forum I note that many others have had a similar problem (not necessarily confined to 40m). Is there any likelihood of a fix for this apparent bug? 

Please don't tell me that I have corrupted a profile - I realise this, what I would like is to know how NOT to corrupt a profile. This is becoming increasingly irritating so a fix would be much appreciated.

Many thanks
Photo of Paul

Paul

  • 479 Posts
  • 144 Reply Likes

Posted 4 months ago

  • 1
Photo of Michael Walker

Michael Walker, Employee

  • 321 Posts
  • 84 Reply Likes
Hi Paul

I think I know what is happening as I have seen it my self.

Could it be you do a band change to 40M and then do a frequency entry change to 20M where you type in a frequency?  

Does that make sense?

Mike

Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2974 Posts
  • 654 Reply Likes
Did you delete all your profiles so you can't use them again. So when you do a full factory reset you need to make set things up and make new ones.

You must have put in a help Desk ticket? what did Flex say?
Photo of Paul

Paul

  • 479 Posts
  • 144 Reply Likes
Thanks for the quick replies;

Michael - yes that's entirely possible but I don't really see why doing that should render a previously working slice inoperable. Once this happens, the panadaptor displays the spectrum for the band that is already selected. Then, on pressing (say) 40m, nothing changes.

Bill - no, all my profiles are fine and on doing a hard reset everything reverts back to normal (once the default profile takes effect ?) It's just tedious to keep having to do this for no apparent reason.

My searches showed a few other people have had similar problems so it seemed to me that an open  discussion (rather than a help desk ticket) might benefit others as well as myself. No doubt someone from Flex will respond if they have anything to add.

Thank you.
Photo of Craig Williams

Craig Williams

  • 78 Posts
  • 15 Reply Likes
I had the same problem. Someone here suggested I load an older profile. That fixed it. Don,t know how you could tell a profile is corrupted. Mine did everything fine except select the 40M band.
(Edited)
Photo of Paul

Paul

  • 479 Posts
  • 144 Reply Likes
Thanks Craig, your symptoms are the same as mine. It would be very helpful if the root cause could be established so that a proper remedy could be put in place rather than the current 'workarounds' of reloading a profile or doing a hard reset.
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2974 Posts
  • 654 Reply Likes
Keep in mind your problem is not wide spread, and only a few people have had this problem, if it were a software issue all 6500 radios would be effected. It would be hard For flex to have a fix when it can not be repeated at will. For instance, I have never seen this kind of problem here.
Photo of Jon, EA2OT

Jon, EA2OT

  • 50 Posts
  • 3 Reply Likes
It happened on my 6300, so most probably software related...
Photo of Jon, EA2OT

Jon, EA2OT

  • 50 Posts
  • 3 Reply Likes
Same situation here since V1. V2 didn ́t solve it. It happens when you enter a frecuency manually different to the band you have selected in SSDR...

Hopefully it will be noted and solved in the next software update.


Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2973 Posts
  • 653 Reply Likes
Maybe that is why I have never seen it, I have never tried doing that...
Photo of Terry Tankersley

Terry Tankersley

  • 58 Posts
  • 5 Reply Likes
I don't see that with my 6500. I can go to band select one and then manually enter any frequency without a problem.
Photo of Jon, EA2OT

Jon, EA2OT

  • 50 Posts
  • 3 Reply Likes
Terry, it doesn't happen every time. In my case, it happened on 80m more offen than in any other band, despite I don't use 80m much.

For sure there's something more involved in the problem because in doesn't happen always.
Photo of Terry Tankersley

Terry Tankersley

  • 58 Posts
  • 5 Reply Likes
I run Win 8.1 and start off on 80 most of the time. I wonder if it is happening to users of Win 10 or all Win versions.
Photo of Paul

Paul

  • 479 Posts
  • 144 Reply Likes
Many thanks for the replies & comments. It's clear there is an issue. It's also clear that the symptoms are induced by a subtle combination of actions by the operator.

I think the symptoms have (so far) been reported only by users of Windows operators. It would be interesting to hear if anyone has experienced this with IOS SSDR. If not, this looks to me like an underlying problem in Win SSDR.

I agree this will be tricky for Flex to trace but an acknowledgement of the problem and some diagnostic effort would be much appreciated.

73, Paul
(Edited)
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2974 Posts
  • 654 Reply Likes
Paul, for now maybe stop changing Freq in that manner.
And, can you explain the steps you take to cause it to happen?
Photo of Paul

Paul

  • 479 Posts
  • 144 Reply Likes
Terry - I get the same problem with my shack computer which runs Win 7 and with my laptop which runs Win 10. I guess this is not surprising since the machine used to connect to the radio inherits the state it was left in by the previous connected session.

Bill - if only that was the solution. It seems that once the problem arises, it then seems to reoccur when simply dragging the spectrum one way or another.
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2974 Posts
  • 654 Reply Likes
I am not trying to say that this is not happening, I am saying that if it were a software problem we all would have this problem,,but we don't. We all have the same 6500 and software.
Start a help desk ticket, as your problem seems to be local to your radio.
Photo of Paul

Paul

  • 479 Posts
  • 144 Reply Likes
I did not think that you were Bill. I have been on here long enough to have seen many of your replies and I know you always try to be helpful.
However, in this case you are mistaken; there are three of us so far in this thread, plus several others from previous posts, all of whom have experienced this issue on one band or another.
I hoped, therefore, that an open discussion here might attract others who have experienced this and so widen the pool of information to help lead to a diagnosis. A help desk ticket would not do that.
My guess is that it is a combination of user operations which provokes the problem, that would account for the seemingly random occurance of the issue.

Anyway, clutching at straws, but I wonder if the hardware changed in any way since the early days - my 6500 is around 4 years old. Just a thought.
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 2974 Posts
  • 654 Reply Likes
Well, if you start the help ticket and pick their brains and something is found out,,then you can share what you know?
One thing I wonder about, I know our radios have re writable SD cards in them. Perhaps some of them have come to their end in reliable writing and saving?

As I said,, it seems reasonable to me that if it were a software bug, the problem would effect us all with 6500 radio's as the hardware are all the same. And it is possible that Flex can not reproduce this issue in the shop?

If Flex is going to address this they are going to need a list of things that you do to cause it and when.
Lets say a help desk was opened, what would you say in it?
Photo of Paul

Paul

  • 479 Posts
  • 144 Reply Likes
I don't think there is anything unusual in the way I operate the radio. If there was a specific series of operations that led to the problem then I would simply list them. Unfortunately I cannot atribute it to anything in particular. I simply change band and sometimes 40m just doesn't respond. It's as though I had not pushed the 40m button. Once it does this I can load another profile which will work for a while until the symptoms re-appear. A hard reset seems to give a longer period before the next occurence, but it's pretty random.
Unfortunately there's nothing else I can add.

Except perhaps that the radio is on 24/7 and has DAXIQ constantly active & streaming (although NOT from the problem panadaptor/band)
(Edited)
Photo of AA0KM

AA0KM

  • 344 Posts
  • 60 Reply Likes
Make a 40 meter profile or what ever band is giving you the trouble.

This happened to me couple years back and 40 meter band selection  was un-responsive  and all I did was create a profile for 40 meters and never has  happened since.
 Direct entry or whatever it takes to dial in on the vfo 40 meters and create profile.

Not sure this is the same issue.
(Edited)
Photo of AA0KM

AA0KM

  • 344 Posts
  • 60 Reply Likes
The Idea I suppose is to make a profile for each band but I don't operate that way.

Some bands I don't use much so I watch the mic/power selections etc etc and use others for current band I am operating on.

Maybe this is why things get mixed up  the way they did.
2cts.
 https://helpdesk.flexradio.com/hc/en-us/articles/200831185-How-to-Reset-Persistence-Database-for-a-FLEX-6000
(Edited)
Photo of Paul

Paul

  • 479 Posts
  • 144 Reply Likes
Many thanks AA0KM for the link to Tim's article on how to reset the persistence database. It is what I refer to in my posts as a "hard reset" and as mentioned, it does (temporarily) fix this problem.

I do already have working profiles which include 40m which I can turn to when the fault occurs. Unfortunately though, if I then change from 40m to another band and try to go back using the band button, it is then inoperative again. So this is at best, an 'emergency' method to temporarily regain the missing band.

As things stand, resetting the persistence database seems to be the only way to 'work around' this. Unfortunately though, it does get corrupted on a monotonously regular basis.

The big question is why does it get corrupted? A proper diagnosis and cure from Flex would be welcome.
(Edited)
Photo of Paul

Paul

  • 479 Posts
  • 144 Reply Likes
Update on symptoms: If I have two panadaptors running, each with a single slice, it seems that the slice with the faulty band is invisible to the radio. Eg. Pan 1/slice A and Pan 2/slice B both working fine. Then click 40m on Pan 1, the fault occurs and the main status display stops showing slice A details and shows the details of slice B. It's as though the connection to Pan 1 is somehow lost, but only for that one band - all others work as expected.

Hope this additional info might help.
(Edited)