Elecraft

Mouse-n-Click QSY

Classic

List

Threaded

22 messages Options

Elecraft mailing list

Mouse-n-Click QSY

This is just what I was thinking about. If you can prove the concept, I see no reason as to why Elecraft can't build this into the P3. The K3 is now 10 years old; while the performance is certainly there, the basic design is now long in the tooth. When was the last time you saw a tech product design unchanged for a decade? I realize we have had software updates and internal improvements, but the outward appearance and basic function has be stagnant. This at least would offer operational functionality and a small step into current design. Don't get me wrong - I love my K3. But we are slowly watching tech design pass us by (color screen, touch control, etc).

73,
Ed K6CTA

Joe Stone wrote:

>>>Let's assume Paul Saffren delivers >>>Mouse-n-Click QSY support with the >>>next P3 / PX3 firmware release. What >>>else would you like the mouse to do >>>other than QSY the rig's VFO frequency? >>>I demonstrated Mouse-n-Click QSY with >>>an Elecraft PX3 and KX3 almost 18 >>>months ago.

Sent from my iPhone

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Elecraft mailing list

Tech passing us by - was Re: Mouse-n-Click QSY

I have to agree about watching the tech slowly pass us by, I have also been thinking the same thing lately.

Yes I also love my K3, P3, etc but there are a few things that make it show it's age. On the P3 lack of Mouse support and the inability to connect a USB hub to allow for a keypad and a keyboard or built in Bluetooth support. On the K3 the limited number of macros and how the K-Pod uses all 16 of them leaving none left over for other purposes. As I understand it a bit of that is due to the microcontroller having limited programming space but if that's the case then the K3s should have used a more modern chip that had a larger space and possibly a new replacement board available to the older K3 to update them (something I thought that the K3 was supposed to be 100% future-proofed but with apparently not).

I built a little qrp radio (mcHF) last summer that while basically in beta really shows some promise and what a radio can be capable of. For a little QRP rig smaller than a KX3 it has a built in Panadapter, all mode including Digital voice ability to update the firmware by just plugging in a USB key to it etc. So the tech appears to be out there since most the issue I've seen on the mcHF is in the RF stages needing some rework etc but on the firmware side it's impressive.

But on the other hand I also just bought a K2 Kit (though admittedly I'm not sure it was my best move), what I really would like to see is an updated K2 that has to a degree been modernized since in the K2 kit some of the parts are being substituted as the originals are now obsolete, but wit a bit of updating it would still make for a nice rig.

I think there is a market for high end radios as well as smaller simpler kits (the popularity of the BiTX series of radios shows that). I'm not a huge fan of being tied to a computer so the Flex series does not really appeal to me. I had a little Flex 1500 and absolutely loved the way the filtering could be setup , but I did not like being tied to a computer so I went to the K3.
A standalone SDR rig with all the knobs and buttons seem the way to go as it gives the best of both worlds.

Elecraft has a loyal following, though at times I believe a bit too loyal as there is a tendency to overlook things we would not overlook with other manufactures.

From: Ed Schuller via Elecraft <[hidden email]>
To: [hidden email]
Sent: Thursday, February 16, 2017 9:58 AM
Subject: [Elecraft] Mouse-n-Click QSY

This is just what I was thinking about. If you can prove the concept, I see no reason as to why Elecraft can't build this into the P3. The K3 is now 10 years old; while the performance is certainly there, the basic design is now long in the tooth. When was the last time you saw a tech product design unchanged for a decade? I realize we have had software updates and internal improvements, but the outward appearance and basic function has be stagnant. This at least would offer operational functionality and a small step into current design. Don't get me wrong - I love my K3. But we are slowly watching tech design pass us by (color screen, touch control, etc).

73,
Ed K6CTA

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Joe Stone (KF5WBO)

Re: Mouse-n-Click QSY

In reply to this post by Elecraft mailing list

When I see Elecraft dodge a trivial firmware change like this year after year, I can’t help but wonder if they have ulterior motives. Maybe Elecraft plans to introduce a $250 wired remote control knob. Maybe they hope someday the knob will control the P3 / PX3. Maybe they feel adding a few lines of firmware to enable a $5 wireless mouse will impact the sales of their $250 knob. Maybe they’re just busy. When they don’t respond to a feature request, it leaves us guessing.

This brings me back to my previous thread. We need a more structured approach to tracking Elecraft feature requests (and bugs). We need a record of when Mouse-n-Click QSY was first proposed. Elecraft can come back and say, “The P3 / PX3 is out of firmware memory space.” Or, “The P3 / PX3 doesn’t have the MIPS to sample IQ, process the 1024-point FFT, update the displays (spectrum and waterfall), field remote-control commands, … AND position a marker based on the delta-X field in a mouse HID descriptor”. This disposition will be captured along with the feature request in a central repository for everyone to see, now and forever. In another month or two when someone requests Mouse-n-Click QSY, we can simply refer them to the (now closed) feature request. Ideally, they’d search the feature / bug list first.

Clearly, Elecraft isn’t interested in maintaining / exposing a list of features and defects raised by their user community. I’ve received several offers from members willing to host this list. We should have something up and running in a few weeks.

Joe
KF5WBO

Doug Turnbull

Re: Mouse-n-Click QSY

Dear OMs and YLs,
To me this is harsh indeed. Who provides better service for the Ham
Radio community? Do we think that we are the directors of Elecraft? For
a moment it sounded like the K-Pod was being criticised - well this is worth
a lot to me and I have one on each of my K3 radios. Elecraft, I am still a
very happy camper when it comes to your product line, service and
accessibility. Clearly it is hard to please us all and I imagine these
critical e-mails stimulate further design ideas.

I am thankful not to be tied to a PC!!! It will become obsolete. Not
many such radios will make it into the Steam Radio Category still being used
after twenty let alone fifty years.

Well that is my 2 cents. It just surprises me to hear such virulence
directed towards an amazing group of engineers with a first class company.

73 Doug EI2CN

-----Original Message-----
From: Elecraft [mailto:[hidden email]] On Behalf Of Joe
Stone (KF5WBO)
Sent: 16 February 2017 17:26
To: [hidden email]
Subject: Re: [Elecraft] Mouse-n-Click QSY

When I see Elecraft dodge a trivial firmware change like this year after
year, I can't help but wonder if they have ulterior motives. Maybe Elecraft
plans to introduce a $250 wired remote control knob. Maybe they hope
someday the knob will control the P3 / PX3. Maybe they feel adding a few
lines of firmware to enable a $5 wireless mouse will impact the sales of
their $250 knob. Maybe they're just busy. When they don't respond to a
feature request, it leaves us guessing.

This brings me back to my previous thread. We need a more structured
approach to tracking Elecraft feature requests (and bugs). We need a record
of when Mouse-n-Click QSY was first proposed. Elecraft can come back and
say, "The P3 / PX3 is out of firmware memory space." Or, "The P3 / PX3
doesn't have the MIPS to sample IQ, process the 1024-point FFT, update the
displays (spectrum and waterfall), field remote-control commands, . AND
position a marker based on the delta-X field in a mouse HID descriptor".
This disposition will be captured along with the feature request in a
central repository for everyone to see, now and forever. In another month
or two when someone requests Mouse-n-Click QSY, we can simply refer them to
the (now closed) feature request. Ideally, they'd search the feature / bug
list first.

Clearly, Elecraft isn't interested in maintaining / exposing a list of
features and defects raised by their user community. I've received several
offers from members willing to host this list. We should have something up
and running in a few weeks.

Joe
KF5WBO

--
View this message in context:
http://elecraft.365791.n2.nabble.com/Mouse-n-Click-QSY-tp7626984p7626987.htm
l
Sent from the Elecraft mailing list archive at Nabble.com.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Jim Brown-10

Re: Mouse-n-Click QSY

In reply to this post by Joe Stone (KF5WBO)

On Thu,2/16/2017 9:26 AM, Joe Stone (KF5WBO) wrote:
> When I see Elecraft dodge a trivial firmware change like this year after
> year, I can’t help but wonder if they have ulterior motives.

Perhaps they know more about the limitations of the hardware that stand
in the way of implementing a feature you want.

73, Jim K9YC

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Grant Youngman-2

Re: Mouse-n-Click QSY

In reply to this post by Joe Stone (KF5WBO)

>
> When I see Elecraft dodge a trivial firmware change like this year after
> year, I can’t help but wonder if they have ulterior motives. Maybe Elecraft
> plans to introduce a $250 wired remote control knob. Maybe they hope
> someday the knob will control the P3 / PX3. Maybe they feel adding a few
> … <snip>

1. Elecraft is not our mother/wife/husband/caretaker

2. Most likely, the resources are consumed by work on the K3/K3s follow-on radio which may sport many of these features. I’d be very surprised to see much in the way of significant new updates to the K3/s and accessories. But, of course, I’d be happy to be surprised ...

3. A deep breath is probably in order.

:-)

Grant NQ5T
K3 #2091, KX3 #8342

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Ken G Kopp

Re: Mouse-n-Click QSY

In reply to this post by Doug Turnbull

Well-said, Doug! 😁

Ken - K0PP

On Feb 16, 2017 10:39, "Doug Turnbull" <[hidden email]> wrote:

> Dear OMs and YLs,
> To me this is harsh indeed. Who provides better service for the Ham
> Radio community? Do we think that we are the directors of Elecraft?
> For
> a moment it sounded like the K-Pod was being criticised - well this is
> worth
> a lot to me and I have one on each of my K3 radios. Elecraft, I am still
> a
> very happy camper when it comes to your product line, service and
> accessibility. Clearly it is hard to please us all and I imagine these
> critical e-mails stimulate further design ideas.
>
> I am thankful not to be tied to a PC!!! It will become obsolete.
> Not
> many such radios will make it into the Steam Radio Category still being
> used
> after twenty let alone fifty years.
>
> Well that is my 2 cents. It just surprises me to hear such
> virulence
> directed towards an amazing group of engineers with a first class company.
>
> 73 Doug EI2CN
>
> -----Original Message-----
> From: Elecraft [mailto:[hidden email]] On Behalf Of Joe
> Stone (KF5WBO)
> Sent: 16 February 2017 17:26
> To: [hidden email]
> Subject: Re: [Elecraft] Mouse-n-Click QSY
>
> When I see Elecraft dodge a trivial firmware change like this year after
> year, I can't help but wonder if they have ulterior motives. Maybe
> Elecraft
> plans to introduce a $250 wired remote control knob. Maybe they hope
> someday the knob will control the P3 / PX3. Maybe they feel adding a few
> lines of firmware to enable a $5 wireless mouse will impact the sales of
> their $250 knob. Maybe they're just busy. When they don't respond to a
> feature request, it leaves us guessing.
>
> This brings me back to my previous thread. We need a more structured
> approach to tracking Elecraft feature requests (and bugs). We need a
> record
> of when Mouse-n-Click QSY was first proposed. Elecraft can come back and
> say, "The P3 / PX3 is out of firmware memory space." Or, "The P3 / PX3
> doesn't have the MIPS to sample IQ, process the 1024-point FFT, update the
> displays (spectrum and waterfall), field remote-control commands, . AND
> position a marker based on the delta-X field in a mouse HID descriptor".
> This disposition will be captured along with the feature request in a
> central repository for everyone to see, now and forever. In another month
> or two when someone requests Mouse-n-Click QSY, we can simply refer them to
> the (now closed) feature request. Ideally, they'd search the feature / bug
> list first.
>
> Clearly, Elecraft isn't interested in maintaining / exposing a list of
> features and defects raised by their user community. I've received several
> offers from members willing to host this list. We should have something up
> and running in a few weeks.
>
> Joe
> KF5WBO
>
>
>
> --
> View this message in context:
> http://elecraft.365791.n2.nabble.com/Mouse-n-Click-QSY-
> tp7626984p7626987.htm
> l
> Sent from the Elecraft mailing list archive at Nabble.com.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Elecraft mailing list

Re: Mouse-n-Click QSY

In reply to this post by Grant Youngman-2

Elecraft is a business, I believe some erroneously elevate them to near god like status.

I choose to spend my money (that represents hours of my life in labor) with business I believe are worth while. As long as Elecraft stays in-tune with their customers I will continue to spend my money with them.If they fail at delivering I will simply move onto the next vendor who is willing and able to deliver.
Business is business plain and simple.

From: GRANT YOUNGMAN <[hidden email]>
To: Elecraft Mailing List <[hidden email]>
Sent: Thursday, February 16, 2017 12:42 PM
Subject: Re: [Elecraft] Mouse-n-Click QSY

>
> When I see Elecraft dodge a trivial firmware change like this year after
> year, I can’t help but wonder if they have ulterior motives. Maybe Elecraft
> plans to introduce a $250 wired remote control knob. Maybe they hope
> someday the knob will control the P3 / PX3. Maybe they feel adding a few
> … <snip>

1. Elecraft is not our mother/wife/husband/caretaker

2. Most likely, the resources are consumed by work on the K3/K3s follow-on radio which may sport many of these features. I’d be very surprised to see much in the way of significant new updates to the K3/s and accessories. But, of course, I’d be happy to be surprised ...

3. A deep breath is probably in order.

:-)

Grant NQ5T
K3 #2091, KX3 #8342

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Don Wilhelm

Re: Tech passing us by - was Re: Mouse-n-Click QSY

In reply to this post by Elecraft mailing list

Limited Macros ???

Just a bit of information: The number of macros was 8. It was
increased to 16 to support the number of buttons on the K-Pod.

Just because the K-Pod buttons can access the macros does not mean that
those macros are dedicated to the K-Pod. The fact that they are stored
in the K3 allows them to be assigned to buttons as well or called up by
an external source other than the K-Pod.

73,
Don W3FPR

On 2/16/2017 11:50 AM, Harry Yingst via Elecraft wrote:
> On the K3 the limited number of macros and how the K-Pod uses all 16 of them leaving none left over for other purposes. As I understand it a bit of that is due to the microcontroller having limited programming space but if that's the case then the K3s should have used a more modern chip that had a larger space and possibly a new replacement board available to the older K3 to update them (something I thought that the K3 was supposed to be 100% future-proofed but with apparently not).
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Elecraft mailing list

Re: Tech passing us by - was Re: Mouse-n-Click QSY

I am well aware that there are 16.

But since they are all assigned to the K-Pod they are no longer useful for self reprogramming Macros.

From: Don Wilhelm <[hidden email]>
To: Harry Yingst <[hidden email]>; "[hidden email]" <[hidden email]>
Sent: Thursday, February 16, 2017 1:23 PM
Subject: Re: [Elecraft] Tech passing us by - was Re: Mouse-n-Click QSY

Limited Macros ???

Just a bit of information: The number of macros was 8. It was
increased to 16 to support the number of buttons on the K-Pod.

Just because the K-Pod buttons can access the macros does not mean that
those macros are dedicated to the K-Pod. The fact that they are stored
in the K3 allows them to be assigned to buttons as well or called up by
an external source other than the K-Pod.

73,
Don W3FPR

On 2/16/2017 11:50 AM, Harry Yingst via Elecraft wrote:
> On the K3 the limited number of macros and how the K-Pod uses all 16 of them leaving none left over for other purposes. As I understand it a bit of that is due to the microcontroller having limited programming space but if that's the case then the K3s should have used a more modern chip that had a larger space and possibly a new replacement board available to the older K3 to update them (something I thought that the K3 was supposed to be 100% future-proofed but with apparently not).
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Don Wilhelm

Re: Tech passing us by - was Re: Mouse-n-Click QSY

Harry,

So use only 8 of them on your K-Pod - the other 8 can be used as
self-programming (just don't use the buttons relating to
self-programming buttons on the K-Pod unless you want to confuse
yourself by not knowing which state they are in).

The point is that 8 was sufficient in the past, I am just curious why
expanding the number to 16 would be a problem.

73,
Don W3FPR

On 2/16/2017 1:28 PM, Harry Yingst via Elecraft wrote:

> I am well aware that there are 16.
>
> But since they are all assigned to the K-Pod they are no longer useful for self reprogramming Macros.
>
>
>
>
> From: Don Wilhelm <[hidden email]>
> To: Harry Yingst <[hidden email]>; "[hidden email]" <[hidden email]>
> Sent: Thursday, February 16, 2017 1:23 PM
> Subject: Re: [Elecraft] Tech passing us by - was Re: Mouse-n-Click QSY
>
> Limited Macros ???
>
> Just a bit of information: The number of macros was 8. It was
> increased to 16 to support the number of buttons on the K-Pod.
>
> Just because the K-Pod buttons can access the macros does not mean that
> those macros are dedicated to the K-Pod. The fact that they are stored
> in the K3 allows them to be assigned to buttons as well or called up by
> an external source other than the K-Pod.
>
> 73,
> Don W3FPR
>
> On 2/16/2017 11:50 AM, Harry Yingst via Elecraft wrote:
>> On the K3 the limited number of macros and how the K-Pod uses all 16 of them leaving none left over for other purposes. As I understand it a bit of that is due to the microcontroller having limited programming space but if that's the case then the K3s should have used a more modern chip that had a larger space and possibly a new replacement board available to the older K3 to update them (something I thought that the K3 was supposed to be 100% future-proofed but with apparently not).
>>
>
>
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Bill-3

Re: Mouse-n-Click QSY

In reply to this post by Elecraft mailing list

The Kenwood TS-480 has been around as long. Although it is low priced,
it is by no means junk and there are thousands of very happy owners -
self included.

Bill W2BLC K-Line

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Elecraft mailing list

Re: Tech passing us by - was Re: Mouse-n-Click QSY

In reply to this post by Don Wilhelm

Easier said than done; Hold the tap too long and it messes up the reprogramming macro.

It should not be a problem for Elecraft to expand the macro area to hold more macros,providing they had the foresight to use a chip with a larger programming space.

Point is there is room for improvement and either they keep up or they will be passed by.

From: Don Wilhelm <[hidden email]>
To: [hidden email]
Sent: Thursday, February 16, 2017 1:43 PM
Subject: Re: [Elecraft] Tech passing us by - was Re: Mouse-n-Click QSY

Harry,

So use only 8 of them on your K-Pod - the other 8 can be used as
self-programming (just don't use the buttons relating to
self-programming buttons on the K-Pod unless you want to confuse
yourself by not knowing which state they are in).

The point is that 8 was sufficient in the past, I am just curious why
expanding the number to 16 would be a problem.

73,
Don W3FPR

On 2/16/2017 1:28 PM, Harry Yingst via Elecraft wrote:

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

David Gilbert

Re: Mouse-n-Click QSY

In reply to this post by Joe Stone (KF5WBO)

When I read posts like this (both tone and content) I can't help
wondering a lot of things. Probably not the same things you wonder
about, though.

Dave Ab7E

On 2/16/2017 10:26 AM, Joe Stone (KF5WBO) wrote:

> When I see Elecraft dodge a trivial firmware change like this year after
> year, I can’t help but wonder if they have ulterior motives. Maybe Elecraft
> plans to introduce a $250 wired remote control knob. Maybe they hope
> someday the knob will control the P3 / PX3. Maybe they feel adding a few
> lines of firmware to enable a $5 wireless mouse will impact the sales of
> their $250 knob. Maybe they’re just busy. When they don’t respond to a
> feature request, it leaves us guessing.
>
> This brings me back to my previous thread. We need a more structured
> approach to tracking Elecraft feature requests (and bugs). We need a record
> of when Mouse-n-Click QSY was first proposed. Elecraft can come back and
> say, “The P3 / PX3 is out of firmware memory space.” Or, “The P3 / PX3
> doesn’t have the MIPS to sample IQ, process the 1024-point FFT, update the
> displays (spectrum and waterfall), field remote-control commands, … AND
> position a marker based on the delta-X field in a mouse HID descriptor”.
> This disposition will be captured along with the feature request in a
> central repository for everyone to see, now and forever. In another month
> or two when someone requests Mouse-n-Click QSY, we can simply refer them to
> the (now closed) feature request. Ideally, they’d search the feature / bug
> list first.
>
> Clearly, Elecraft isn’t interested in maintaining / exposing a list of
> features and defects raised by their user community. I’ve received several
> offers from members willing to host this list. We should have something up
> and running in a few weeks.
>
> Joe
> KF5WBO
>
>

Joe Stone (KF5WBO)

Re: Mouse-n-Click QSY

In reply to this post by Jim Brown-10

For a moment it sounded like the K-Pod was being criticized

[js] I didn’t mean to criticize the K-Pod. I’m simply speculating as to why Elecraft hasn’t added P3 / PX3 mouse support.

[js] Last time I checked, the K-Pod isn’t capable of functioning as a mouse (and keyboard). However, according to the K-Pod manual, this support is planned.

[js] I’m willing to concede Elecraft may simply be too busy. However, the need for Mouse-n-Click QSY has been raised every few months for years. And it’s a trivial firmware change. I think there’s something more to it.

I am thankful not to be tied to a PC!!!

[js] Same here!!! Hence, the desire for P3 / PX3 mouse support *without* the need for a PC.

Perhaps they know more about the limitations of the hardware that stand in the way of implementing a feature you want.

[js] My point exactly (second paragraph). Let’s capture their knowledge of the limitations (e.g., memory, MIPS, ...) in conjunction with the feature request. Case closed.

Joe Stone (KF5WBO)

K-Pod Macros

In reply to this post by Elecraft mailing list

According to the manual, through a future firmware upgrade, the K-Pod will be able to function as a USB HID (Human Interface Device) such as a keyboard or mouse. Conceivably, the eight K-Pod tap and hold switches could be mapped to 16 P3 / PX3 macros. You could even implement three “banks” of 16 macros for a total of 48 K-Pod macros. Of course, this assumes: 1. you have a P3 equipped with the SVGA option or a PX3; 2. you’re not already using a keyboard in conjunction with your P3 / PX3 (this would require USB hub support); and 3. you haven’t already burned all 50 of your P3 / PX3 macros (unlikely).

In a nutshell, I’m assuming if the K-Pod is to function as a USB HID keyboard, the tap and hold switches would correspond to standard keyboard keys (including combinations of Ctrl, Alt and Shift modifiers). The keys would be assigned to macros on the P3 / PX3. This wouldn’t require any change to the P3 / PX3. The P3 / PX3 wouldn’t be able to differentiate the K-Pod from a keyboard (which it already supports).

With a P3, the K-Pod knob could continue to control the K3s/K3 via the data connector. With the PX3, the K-Pod knob would present itself as a mouse. Of course, this would require the beforementioned Mouse-n-Click QSY support. Alternatively, if you wanted the K-Pod knob to control the P3, the Mouse-n-Click QSY support could be leveraged there as well.

Joe
KF5WBO

Paul Van Dyke

Re: K-Pod Macros

As I sit and look at my station and my K-Pod, just remember Dayton is not
that far away, and Wayne, Eric and the rest of the crew have been very very
quiet. Remember they're very good at blowing people out of the water ....
remember there was a radio that came out last year that caught everybody
flat-footed .. esp the competition.

Paul KB9AVO

On Feb 16, 2017 3:28 PM, "Joe Stone (KF5WBO)" <[hidden email]>
wrote:

> According to the manual, through a future firmware upgrade, the K-Pod will
> be
> able to function as a USB HID (Human Interface Device) such as a keyboard
> or
> mouse. Conceivably, the eight K-Pod tap and hold switches could be mapped
> to 16 P3 / PX3 macros. You could even implement three “banks” of 16 macros
> for a total of 48 K-Pod macros. Of course, this assumes: 1. you have a P3
> equipped with the SVGA option or a PX3; 2. you’re not already using a
> keyboard in conjunction with your P3 / PX3 (this would require USB hub
> support); and 3. you haven’t already burned all 50 of your P3 / PX3 macros
> (unlikely).
>
> In a nutshell, I’m assuming if the K-Pod is to function as a USB HID
> keyboard, the tap and hold switches would correspond to standard keyboard
> keys (including combinations of Ctrl, Alt and Shift modifiers). The keys
> would be assigned to macros on the P3 / PX3. This wouldn’t require any
> change to the P3 / PX3. The P3 / PX3 wouldn’t be able to differentiate the
> K-Pod from a keyboard (which it already supports).
>
> With a P3, the K-Pod knob could continue to control the K3s/K3 via the data
> connector. With the PX3, the K-Pod knob would present itself as a mouse.
> Of course, this would require the beforementioned Mouse-n-Click QSY
> support.
> Alternatively, if you wanted the K-Pod knob to control the P3, the
> Mouse-n-Click QSY support could be leveraged there as well.
>
> Joe
> KF5WBO
>
>
>
> --
> View this message in context: http://elecraft.365791.n2.
> nabble.com/Mouse-n-Click-QSY-tp7626984p7627007.html
> Sent from the Elecraft mailing list archive at Nabble.com.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]

Bill Frantz

Re: Mouse-n-Click QSY

In reply to this post by Jim Brown-10

Given the lag between the turning tuning knob and movement on
the VGA display with the P3, there may be an issue with having
the mouse cursor track with the mouse movement in a usable
maner. I frequently move the frequency too far turning the knob
and watching the VGA display.

73 Bill AE6JV

On 2/16/17 at 9:39 AM, [hidden email] (Jim Brown) wrote:

>On Thu,2/16/2017 9:26 AM, Joe Stone (KF5WBO) wrote:
>>When I see Elecraft dodge a trivial firmware change like this year after
>>year, I can’t help but wonder if they have ulterior motives.
>
>Perhaps they know more about the limitations of the hardware
>that stand in the way of implementing a feature you want.
-----------------------------------------------------------------------
Bill Frantz | I like the farmers' market | Periwinkle
(408)356-8506 | because I can get fruits and | 16345
Englewood Ave
www.pwpconsult.com | vegetables without stickers. | Los Gatos,
CA 95032

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Bill Frantz

Re: Mouse-n-Click QSY

In reply to this post by Elecraft mailing list

Well, I used the starter motor on my car -- certainly a
technological artifact -- this morning. I don't think there have
been significant changes to the design of starter motors in my
72 year lifetime. There have probably been incremental
improvements in things like metallurgy and insulation, but the
overall design remains the same.

73 Bill AE6JV

On 2/16/17 at 6:58 AM, [hidden email] (Ed Schuller via
Elecraft) wrote:

>When was the last time you saw a tech product design unchanged
>for a decade?
-------------------------------------------------------------------------
Bill Frantz | The first thing you need when | Periwinkle
(408)356-8506 | using a perimeter defense is a | 16345
Englewood Ave
www.pwpconsult.com | perimeter. | Los Gatos,
CA 95032

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Wes Stewart-2

Re: Tech passing us by - was Re: Mouse-n-Click QSY

In reply to this post by Elecraft mailing list

I have two re-programming macros, Split + 1 and No Split in Macro 1 and Macro 2
respectively. in my K3S. In the radio these are assigned to PF1. Hold PF1, go
to Split; hold it again, cancel split. Now, to avoid disasters, using the
K-Pod, I must program both tap and hold of PF1 and PF2 respectively to split and
cancel split. So there are four functions tied up to do what I can do with one
button push on the K3S. To get back to one button, I've put radio PF1 on K-Pod
PF3. Confusing, no?

IMHO, to fulfill its promise, the K-Pod should hold the macros and send them to
the radio. They should be programmable in the K-Pod via USB.

Wes N7WS

On 2/16/2017 12:12 PM, Harry Yingst via Elecraft wrote:

> Easier said than done; Hold the tap too long and it messes up the reprogramming macro.
>
> It should not be a problem for Elecraft to expand the macro area to hold more macros,providing they had the foresight to use a chip with a larger programming space.
>
> Point is there is room for improvement and either they keep up or they will be passed by.
>
>
>
>
> From: Don Wilhelm<[hidden email]>
> To:[hidden email]
> Sent: Thursday, February 16, 2017 1:43 PM
> Subject: Re: [Elecraft] Tech passing us by - was Re: Mouse-n-Click QSY
>
> Harry,
>
> So use only 8 of them on your K-Pod - the other 8 can be used as
> self-programming (just don't use the buttons relating to
> self-programming buttons on the K-Pod unless you want to confuse
> yourself by not knowing which state they are in).
>
> The point is that 8 was sufficient in the past, I am just curious why
> expanding the number to 16 would be a problem.
>
> 73,
> Don W3FPR
>
> On 2/16/2017 1:28 PM, Harry Yingst via Elecraft wrote:
>> I am well aware that there are 16.
>>
>> But since they are all assigned to the K-Pod they are no longer useful for self reprogramming Macros.
>>
>>
>>
>>
>> From: Don Wilhelm<[hidden email]>
>> To: Harry Yingst<[hidden email]>;"[hidden email]" <[hidden email]>
>> Sent: Thursday, February 16, 2017 1:23 PM
>> Subject: Re: [Elecraft] Tech passing us by - was Re: Mouse-n-Click QSY
>>
>> Limited Macros ???
>>
>> Just a bit of information: The number of macros was 8. It was
>> increased to 16 to support the number of buttons on the K-Pod.
>>
>> Just because the K-Pod buttons can access the macros does not mean that
>> those macros are dedicated to the K-Pod. The fact that they are stored
>> in the K3 allows them to be assigned to buttons as well or called up by
>> an external source other than the K-Pod.
>>
>> 73,
>> Don W3FPR
>>
>> On 2/16/2017 11:50 AM, Harry Yingst via Elecraft wrote:
>>> On the K3 the limited number of macros and how the K-Pod uses all 16 of them leaving none left over for other purposes. As I understand it a bit of that is due to the microcontroller having limited programming space but if that's the case then the K3s should have used a more modern chip that had a larger space and possibly a new replacement board available to the older K3 to update them (something I thought that the K3 was supposed to be 100% future-proofed but with apparently not).
>>>