Elecraft

Slow-scan TV (SSTV) display on the P3 and PX3?

Classic

List

Threaded

17 messages Options

ve3dvy

Slow-scan TV (SSTV) display on the P3 and PX3?

I agree with those that would like to see TX monitoring and how about
wider range it'd be handy for quick looks at say 10m for activity to
see 400 or 500 KHZ.

I do some SSTV and enjoy it I think there are more of us than you
think and not just the fools on 14.230 sending soft porn. however if
I want to play SSTV I am running MMSSTV anyway that has good templates
sending and lots of function, ability to store images etc. I am not
sure just to add the ability to monitor incoming pictures would be a
good use of resources. unless you are planning to implement something
with MMSSTV's level of capability. adding more comprehensive
RTTY/psk function or perhaps JT65/9 or even a simple logger so I don't
need to drag the the PC when outside the shack would be nice. just
pie in the sky thing there.

--
David Moes

VE3DVY

______________________________________________________________
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]

k6dgw

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

I agree with you David, I think there are a lot of other things that
would be much more useful to a much larger audience than receive-only SSTV.

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. For
CW, I have been running at 50 KHz because the signals are so much closer
together ... I'll give CW a try at 100 KHz and see how that works. My
K3 is S/N 642, and I'm still playing around with how to use it and what
to set things at. Yet another new dimension to ham radio.

73,

Fred K6DGW
- Northern California Contest Club
- CU in the 2014 Cal QSO Party 4-5 Oct 2014
- www.cqp.org

On 8/17/2014 3:37 PM, david Moes wrote:

> I agree with those that would like to see TX monitoring and how about
> wider range it'd be handy for quick looks at say 10m for activity to
> see 400 or 500 KHZ.
>
> I do some SSTV and enjoy it I think there are more of us than you
> think and not just the fools on 14.230 sending soft porn. however if
> I want to play SSTV I am running MMSSTV anyway that has good templates
> sending and lots of function, ability to store images etc. I am not
> sure just to add the ability to monitor incoming pictures would be a
> good use of resources. unless you are planning to implement something
> with MMSSTV's level of capability. adding more comprehensive
> RTTY/psk function or perhaps JT65/9 or even a simple logger so I don't
> need to drag the the PC when outside the shack would be nice. just
> pie in the sky thing there.
>

Jim Brown-10

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

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:[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]

wayne burdick

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

Administrator

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 <[hidden email]> 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

vk2rq

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

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 <[hidden email]> 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 <[hidden email]> 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:[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]

wayne burdick

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

Administrator

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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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:[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]

W4JBB

Re: P3/PX3 SPAN Settings

I'd prefer it per mode. My presets are:

10 kHz - CW
20 kHz - CW/data
50 kHz - Phone
100 kHz - Phone

I usually operate CW. Switching to phone means I have to mash (that's
what we do to buttons in the South ;) ) a button to get a good span.

Joel - W4JBB

On 8/18/14, 12: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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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:[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]
>

Joe Subich, W4TV-4

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

In reply to this post by wayne burdick

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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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:[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]
>

Cady, Fred

P3 ref level: (was)RE: Slow-scan TV (SSTV) display on the P3 and PX3?

In addition to the below stuff, I'd like to be able to set an automatic reference level. Seems like I am always changing it to keep the waterfall display looking right.
Cheers all,
Fred KE7X

-----Original Message-----
From: Elecraft [mailto:[hidden email]] On Behalf Of Joe Subich, W4TV
Sent: Monday, August 18, 2014 6:17 AM
To: Wayne Burdick
Cc: [hidden email]
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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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:[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
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]

Charlie T, K3ICH

Re: P3 ref level: (was)RE: Slow-scan TV (SSTV) display on the P3 and PX3?

I guess any sort of mouse control of these and possibly other parameters is
out of the question (???)

Chas

----- Original Message -----
From: "Cady, Fred" <[hidden email]>
To: "Wayne Burdick" <[hidden email]>
Cc: <[hidden email]>
Sent: Monday, August 18, 2014 8:43 AM
Subject: [Elecraft] P3 ref level: (was)RE: Slow-scan TV (SSTV) display on
the P3 and PX3?

> In addition to the below stuff, I'd like to be able to set an automatic
> reference level. Seems like I am always changing it to keep the waterfall
> display looking right.
> Cheers all,
> Fred KE7X
>
>

______________________________________________________________
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]

Nate Bargmann

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

In reply to this post by Joe Subich, W4TV-4

* On 2014 18 Aug 07:19 -0500, Joe Subich, W4TV wrote:
>
> 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.

Agreed. I tend to run 20 kHz on phone and 7 to 10 kHz on CW as I'm
mostly interested in the signal I'm receiving and the adjaceant signals.
I typically do not change the spans when I change bands, only when
changing modes.

73, Nate, N0NB

--

"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
______________________________________________________________
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]

gm3sek

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

In reply to this post by Joe Subich, W4TV-4

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:[hidden email]] On Behalf Of
Joe

>Subich, W4TV
>Sent: 18 August 2014 13:17
>To: Wayne Burdick
>Cc: [hidden email]
>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 <[hidden email]>
>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 <[hidden email]>
>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
><[hidden email]> 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:[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
>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 Subich, W4TV-4

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

> 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:[hidden email]] On Behalf Of
> Joe
>> Subich, W4TV
>> Sent: 18 August 2014 13:17
>> To: Wayne Burdick
>> Cc: [hidden email]
>> 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 <[hidden email]>
>> 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 <[hidden email]>
>> 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
>> <[hidden email]> 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:[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
>> 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]
>
>

Brian Hunt

Re: P3/PX3 SPAN Settings

In reply to this post by W4JBB

I think it would be helpful to center the span on the A-cursor when changing spans. Often when going from 50 KHz to 10 KHz (e.g. take a closer look at a pileup) the cursor winds up on the far right side of the screen. My $0.02.

73,
Brian K0DTJ
______________________________________________________________
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]

Iain MacDonnell - N6ML-2

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

In reply to this post by Joe Subich, W4TV-4

On Mon, Aug 18, 2014 at 7:35 AM, Joe Subich, W4TV <[hidden email]> wrote:

>
>> 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.

+1

73,

~iain / N6ML

> 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:[hidden email]] On Behalf Of
>>
>> Joe
>>>
>>> Subich, W4TV
>>> Sent: 18 August 2014 13:17
>>> To: Wayne Burdick
>>> Cc: [hidden email]
>>> 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 <[hidden email]>
>>>
>>> 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 <[hidden email]>
>>>
>>> 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
>>>
>>> <[hidden email]> 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:[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
>>> 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: Slow-scan TV (SSTV) display on the P3 and PX3?

In reply to this post by wayne burdick

On Sun,8/17/2014 10:01 PM, Wayne Burdick 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.

I like that a lot.

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]

Pierfrancesco Caci

Re: Slow-scan TV (SSTV) display on the P3 and PX3?

In reply to this post by wayne burdick

On August 18, 2014 7:10:01 AM GMT+02:00, Wayne Burdick <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]>
>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:[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]

Yes, I'd like it per mode.
Thanks,
Pf
--
Pierfrancesco Caci

______________________________________________________________
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]