[TenTec] FW: Future Radios - Knobs!

[Rick - DJ0IP / NJ0IP]

Not quite, Lee.

See comments below your text...

73 - Rick, DJ0IP
(Nr. Frankfurt am Main)


-----Original Message-----
From: Lee WA3FIY [mailto:wa3fiy at radioadv.com] 


Layer 1 - User interface.....TT 602 POD.  1 nice big knob and 15
programmable buttons....

>>>This does NOT work with an Eagle.  It does not have enough knobs for my
liking.  I want more.  There are a couple available today, but soon there
will be many different "PODs".  

Layer 2 - N4PY control program giving you a graphic interface of common
functions and settings.....a button on the task bar showing operating
frequency (to 1Khz resolution) and providing instant recall of the graphic
panel.....

>>>I've had N4PY software for 10 years and its great, but it does not have
the modularity and user-definable levels that I want for the future.
Perhaps I was not clear on what I mean.  I will prepare some drawings and
explanations and post them on my web for any interested to see.  It's my
understanding that when I open this window I get everything.  I don't want
that.  Much too busy to be watching during a contest.

>>>Let me be clear on this:  I think N4PY software is currently the best
thing going.  The industry is evolving.  What do we want in the future?
That is why I started this idea of future radios.  

Layer 3 - N4PY control program in "Settings" mode for the deep layer
menus....

I've been using this set-up for over ten years with very good success.  You
can run Level 1 with the control program minimized but bring it back with
the touch of one icon on the task bar to access Layer 2.

>>>I don't want it on the task bar; too slow to reach.  My task bar is
normally hidden.  I want it on-screen ALL the time, about the size of a
postage stamp.  I can place it anywhere on the screen I like and it is
always on top.  I double click it to open it, it expands to a (definable)
usable size, and shows just a handful of functions which I have defined.
Then I double-click it again to shrink it back to a postage stamp size.  It
definitely must not show all the functions like the standard N4PY screen
shows.  Too busy.

I have a TT 602 POD connected to my Pegasus and run Carl's N4PY software.  I
have the pod programmed as follows:

>>>> YES, this is exactly along the lines of my concept, but I want more
knobs and behind it, two levels of further software options, with the
mid-level being exactly that what I want it to be.  The lowest level has
everything.  In other words, I want to insert one more user-definable level
between Carl's software (or similar) and my POD.

.

It took a little while to arrive at this configuration and to get used to it
but I now find it very 
comfortable and I'm a 71 year old goat!   :-)

This can be developed in various directions but it works very nicely as it
is now.

>>>> And this is exactly how it must be.  Each of us defines exactly what we
want.  We'll need some time and our own setup will evolve but eventually it
will be perfect for us.  The cake is gonna taste real good!  ;-)


One limitation is that you need a Pegasus, Jupiter, OmniVII or Orion to do
this directly.  

>>>> We were talking about "Future Radios".  It's nice to remind people what
is possible today, because it is perhaps more than what many think, but in
the future it must be and will be much better than it is today.


You can access many (maybe most) of the radios Carl supports if you have a
Pegasus or Jupiter as an interface between the POD and N4PY control program.


>>>> sorry but I'm not going to add a 15 year old transceiver to my future
radio, just so the software can talk to my POD.  Or have I misunderstood
something here?

 If I understand correctly how that works it seems to me that it would be a
small matter to program a Arduino or ChipKIT 32 to act as the interface,
therefore not needing the Pegasus or Jupiter.  

>>>>For me, this falls under the category of "don't care how you do it, just
gimme it!"  It that's the solution, fine but don't expect me to be an expert
programmer.  I want to drag and drop features from one level to the next.


I have the ChipKIT 32 but since I also have several Pegasus transceivers I
have no need of a specialized interface.  
I plan on setting this up with my coming ArgonautVI so it will act mostly
like what I am already used to.  The Argonaut does not have full computer
control (hence POD) control though so I will have to adjust a few knobs on
the radio panel once-in-a-while.

73,

-Lee-

Cheers! - Rick




On 3 Nov 2014 at 17:48, Rick - DJ0IP / NJ0IP wrote:

> My dream includes what Barry just described but goes beyond that.
> 
> Obviously not every feature will be assigned a knob because in the 
> meantime there are a hundred features or functions.
> 
> The critical and most often used ones get assigned to dedicated knobs 
> and buttons on the interface of choice. What next?
> 
> What if you need to adjust something else?  Revert to a complex screen 
> with a hundred features? NOPE.
> 
> I want to have a layered approach to the software behind the user 
> interface. At least two software layers - so 3 layers including the 
> Wood Box (Tmate2)-like user interface.
> 
> ..The first layer is the physical interface with knobs and buttons.
> 
> ..The second layer which I fall back on for common features that are 
> not assigned dedicated knobs, will be a simple interface with perhaps
> 5 or 10 more common features.  KEEP IT SIMPLE.  
> 
> ..THEN if I still need to adjust something more rare, I fall back on 
> the third layer which is a complex menu containing everything.
> 
> Of course the features and functions assigned to layers one and two 
> are completely user-definable.
> 
> The entrance to the second layer (first software layer) will be an 
> icon in the task bar at the bottom of the screen, but must (as an
> option) also be a small Icon, with user definable screen, and if 
> desired, enabled for "always on top".  That way it will always show, 
> no matter what other screen I'm looking at.  I would make mine the 
> size of a postage stamp.  Likewise, the entrance to the third level 
> would be a clickable link which appears within the second layer.
> 
> This approach keeps things totally simple and easy to use.
> We can even define different user profiles for different modes or 
> styles of operation. There can be one for CW, one for SSB, another for 
> PSK, and yet another for short wave listening.
> 
> Now that would be the berries!
> 
> 73 - Rick, DJ0IP
> (Nr. Frankfurt am Main)
> 
> 

---
This email is free from viruses and malware because avast! Antivirus
protection is active.
http://www.avast.com