Memory in 6000 series software

  • 7
  • Idea
  • Updated 4 years ago

There needs to be a "Memory" stand alone button somewhere, shouldn't have to go thru "Settings" to get to memory    Also an option so when you click the memory you want the memory window goes away like with the 1500 

Photo of Dave Dave

Dave Dave

  • 135 Posts
  • 30 Reply Likes

Posted 4 years ago

  • 7
Photo of N3NER

N3NER

  • 186 Posts
  • 24 Reply Likes
I would have to agree, memory still needs some work but its getting there.
Photo of Ken ve7kwa

Ken ve7kwa

  • 103 Posts
  • 32 Reply Likes
Agreed... the memory function is Clunky at best.  It may lag behind other features in priority,  but
I think memory improvement is important.   Yes... there is additional memory software out there, but the radio should still function smoothly on it's own.
Photo of Sergey, R5AU

Sergey, R5AU

  • 860 Posts
  • 117 Reply Likes
Ken, but SSDR has it on board : SSDR Manual, section 20.1, works fine by the way.
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 975 Posts
  • 180 Reply Likes
You're right of course, Sergey. SSDR memory and FRStack both work quite
well, but what we would like are some memory buttons on the SSDR main
screen, so we wouldn't have to click around. Quick memory and some fast
memory buttons are a must on modern TRX.
Photo of Sergey, R5AU

Sergey, R5AU

  • 860 Posts
  • 117 Reply Likes
Alex you right, however plenty of buttons into one GUI like for ANAN ex. (IMHO) make the screen surface complicated to utilize with other sorts of SW. The best case is of course to implement everything  with dockable DUI with functions block, but it required to redesign SSDR GUI completely(or to make one more separate SW like CAT SSDR but for some specific most wanted functions), even 5k  some time are not enought :-)
(Edited)
Photo of Ken ve7kwa

Ken ve7kwa

  • 103 Posts
  • 32 Reply Likes
Sergey, as you pointed out there are several add ons for memory function . I'd still like the on board memory function improved though. Why not a drop down tab or button that shows quick buttons for memory etc, as earlier suggested. Also as Dave mentioned... the screen should at least close after a memory is selected. All in good time I'm sure. I find the current memory system noticeably lacking.  
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 975 Posts
  • 180 Reply Likes
You have my vote, Ken :-)
Photo of Sergey, R5AU

Sergey, R5AU

  • 860 Posts
  • 117 Reply Likes
Ken i can agree with drop down tab it will be suitable for use in the same way like profiles for today but additional separate Tab as ex.: CWX or Menu from the Right on SSDR will be too much for GUI.
Photo of Mike Christmas

Mike Christmas

  • 5 Posts
  • 0 Reply Likes
How about one of the F-keys we should be able to assign short cuts to them
Photo of Sergey, R5AU

Sergey, R5AU

  • 862 Posts
  • 117 Reply Likes
Photo of Al / NN4ZZ

Al / NN4ZZ

  • 1853 Posts
  • 672 Reply Likes
Sergey,
Here is a memory button idea that was submitted a while back.   It has 9 votes so far and is "under consideration."

https://community.flexradio.com/flexradio/topics/_quick_memories_for_smart_sdr

Does this do what you want? 

Regards, Al / NN4ZZ  
al (at) nn4zz (dot) com

******** snapshot for the idea showing the save and recall panel **********


  
Photo of Bill

Bill

  • 42 Posts
  • 2 Reply Likes
That seems like a really good idea to me. it has my vote.
Bill
Photo of Dave Dave

Dave Dave

  • 135 Posts
  • 30 Reply Likes
Maybe someday ill understand Flex's way of thinking, I sure don't now.
4 complicated Noise reductions buttons and no Squelch.... don't get it.
Memory so very limited ...don't get it.
I fail to see Flex's way because and memory is the simple stuff.
Someone please explain what I'm missing......
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3784 Posts
  • 1637 Reply Likes
@DAVE

Simple Answer. Use Cases , Customer Demand and availability of programming resources.

The target market for the top end radios are DXer and Contesters who need very sophisticated noise tools and rarely use squelch or memory. For example as a DXer and Contester for 55+ years I have never used squelch and except for 60M and 10M FM never used memories But then I rarely if ever rag chew or play with Nets.

When resources are available then I suspect FRS will get around to incorporating lower priority features. In the meantime 3rd party app FRstack already does most of what you want.

BTW. You continually post about squelch. I think FRS has already heard you but I don't see a lot of other requests for it.