At present the K3 has... let's call it an "oversight"... in the way
that it memorizes data sub-modes. It correctly memorizes the
last-used data sub-mode on each band, but not the bandwidth setting
appropriate to that sub-mode. Instead, the bandwidth settings for
*all* data sub-modes on *all* bands are overwritten by the settings
for whichever sub-mode was most recently used on *any* band. This is
often quite inappropriate, and inconvenient for anyone whose
interests cover a range of data sub-modes.
That problem needs to be fixed in the K3/KX3 firmware before moving
on to upgrade to automate the display settings of the P3 and the
PX3.
Agreed - and one of those user interface issues to which I referred
earlier in this thread. DATA A and AFSK A/FSK D need separate default
bandwidth (2.8 or 4 KHz for DATA A, 500 Hz for AFSK A/FSK D) and the
last used BW/FC values need to be stored per sub-mode/band.
73,
... Joe, W4TV
On 2014-08-18 10:10 AM, Ian White wrote:
I would agree with that... but first, there is another point that needs
to be rationalized in the K3 (and, I presume, the KX3 also).
DATA is not a single mode - it is only a "folder name" for a collection
of different data sub-modes. Many of those sub-modes require quite
different settings for the transceiver bandwidth and center frequency;
and that is equally true about the optimum bandwidths for a visual
display.
At present the K3 has... let's call it an "oversight"... in the way that
it memorizes data sub-modes. It correctly memorizes the last-used data
sub-mode on each band, but not the bandwidth setting appropriate to that
sub-mode. Instead, the bandwidth settings for *all* data sub-modes on
*all* bands are overwritten by the settings for whichever sub-mode was
most recently used on *any* band. This is often quite inappropriate, and
inconvenient for anyone whose interests cover a range of data sub-modes.
That problem needs to be fixed in the K3/KX3 firmware before moving on
to upgrade to automate the display settings of the P3 and the PX3.
73 from Ian GM3SEK
-----Original Message-----
From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of
Joe
Subich, W4TV
Sent: 18 August 2014 13:17
To: Wayne Burdick
Cc: elecraft@mailman.qth.net
Subject: Re: [Elecraft] Slow-scan TV (SSTV) display on the P3 and PX3?
On 2014-08-18 1:10 AM, Wayne Burdick wrote:
We're considering per-mode as well,
I agree that per mode is more valuable than per band. I'm nearly
always changing span when I change modes (10 KHz on CW, 20 KHz on
data, 50 or 100 KHz on Phone) but not generally changing span with
bands unless I've also changed mode.
73,
... Joe, W4TV
On 2014-08-18 1:10 AM, Wayne Burdick wrote:
We're considering per-mode as well, but at the moment we're
experimenting with per-band. Input welcome.
Wayne
On Aug 17, 2014, at 10:07 PM, Matt VK2RQ <matt.vk...@gmail.com>
wrote:
Would it make more sense for it to be per-mode rather than per-band?
For example, I can imagine on CW you might want to zoom in more than on
SSB. Maybe some P3 owners can comment?
73, Matt VK2RQ
On 18 Aug 2014, at 3:01 pm, Wayne Burdick <n...@elecraft.com>
wrote:
We just added per-band SPAN settings to the PX3 (and will later add
it
to the P3). We're also adding a menu setting to quantize the SPAN
selections to 2, 5, 10, 20, 50, 100, and 200 kHz. This behavior would
be user-
selectable; the default would be continuously variable, as it is at
present.
For a lot of P3/PX3 users, the combination of these two changes
will
result in less manipulation of the SPAN control, and will save some Fn
switches for other uses.
Wayne
N6KR
On Aug 17, 2014, at 9:45 PM, Jim Brown
<j...@audiosystemsgroup.com> wrote:
On Sun,8/17/2014 7:18 PM, Fred Jensen wrote:
I'm still working at what the "ideal" span on my P3 would be, in
the
NAQP SSB yesterday, I had it at 100 KHz and it seemed pretty good.
I have five of the function keys programmed for different span
settings. The other three are Peak Toggle, Fixed Mode Toggle, and Noise
Blanker Toggle.
I use 2 kHz for looking at the quality of CW signals, 10 kHz for
most CW
pileups, 50 kHz, 100 kHz, and 200 kHz for contesting and general
operating.
I did have 20 kHz programmed, but gave that up for the NB toggle.
Before each contest, I'll run through all the bands and set up the
span
and centering. 50/60 kHz is pretty good for Sprints and state QSO
parties,
100 kHz is good for most CW contests, 200 kHz is not wide enough for
some
SSB contests.
For 6M, I set a 200 kHz span from 50.080 to 50.280. This lets me
see
CW, SSB, and JT65.
73, Jim K9YC
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to matt.vk...@gmail.com
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to li...@subich.com
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to gm3...@ifwtech.co.uk
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com
