Im not sure I would like this at all. sometimes I think that fool-proofing a rig is the wrong way to go as it take the ownership away from the operator to pay attention to what they are doing and panders to the shall I say the bad drivers. if I am working split I make it habbit to set offset where I make the most mistakes is when I set the offset and forget to enable split. or worse make the contact move on to a station working simplex and forget that I am in split. and its really not that embarrassing and most figure it out in a call or so. those that don't aren't paying enough attention. In most cases when someone makes this error its often the Up cops that are worse QRM than the original offender. Thats when I get frustrated.

If this must be done however make the offset mode specific it automatically 1khz in cw and 3 in ssb. but I dont see a great need.

David Moes
President: Peterborough Amateur Radio Club.
[email protected]
VE3DVY,  VE3SD

On 10/3/2014 05:24, Ken Chandler wrote:
I'll agree with that Ian, set it a 3KHz, then let the user define his own split 
offset once split is activated.


Ken.. G0ORH

Sent from my iPad


On 3 Oct 2014, at 09:11, Ian White <[email protected]> wrote:

The reason for programming a default "smart split" is to move the TX VFO
*away* from the frequency of the DX station. "How far to move?" is a
secondary issue.

No single value of frequency offset can be optimum for all modes, but
anything is better than leaving it at zero! As a frequent user of Split
for CW and RTTY, but only very rarely on SSB, I have found +3kHz a very
acceptable compromise. Obviously it isn't perfect; but remember it is
only a starting-point for tuning the pileup, so the exact value isn't
hugely important.

The main point is: the default Split offset should *never, never* be
zero... and that is exactly where the K3 gets it wrong. When the user
double-presses A>B to escape from the "SPLIT N/A" situation, it brings
both VFOs onto the same frequency - leaving the user only one step away
from accidentally calling on top of the DX station.

Other transceiver manufacturers recognise the need for better protection
against that hugely embarrassing mistake, which is why Smart Split has
become an industry standard. With one notable exception.


73 from Ian GM3SEK


-----Original Message-----
From: Elecraft [mailto:[email protected]] On Behalf Of
Joe
Subich, W4TV
Sent: 02 October 2014 17:48
To: [email protected]
Subject: Re: [Elecraft] Split N/A


And I do not have any issue with the K3 not going split with RTTY on
one freq and CW/SSB on the other. You have to admit operating RTTY
and SSB/CW split is not exactly a common mode.
However, it would be appropriate when initiating SPLIT from the A->B
button that VFO B mode be forced to that of VFO A if VFO A is digital
and the frequency of VFO B be forced to that of VFO A if VFO B is on
a different band rather than SPLIT N/A.

Unlike Ian, I would not want the VFO B *frequency* changed (e.g., Quick
Split) as long as it was on the current band since I'm just as likely
to have set it manually even if I have not set the mode and the "Smart
Split" splits will invariably be different mode to mode (up 1 in CW,
UP 2 in RTTY, UP 5 in SSB, etc.) and band to band.

73,

   ... Joe, W4TV


On 2014-10-02 11:13 AM, Dick wrote:
Frank,

Like yourself, I do quite a bit of DX RTTY operation using split, and
to
tell you the truth, I just tried what you are talking about, and you
are
right!   To me honest with you, I hadn't noticed it before because I
have a
nasty habit of "double pushing" the SPLIT button before holding it to
engage
split.  This relative simple operation of double pushing the SPLIT
button
transfers everything from A to B; then pushing the SPLIT button works
just
fine.

Am curious what "a whole lot of button pushing" means to you?
Personally,
I don't consider double pushing the same button I use to go split
once,
before holding the same button to be "extremely annoying".   And I do
not
have any issue with the K3 not going split with RTTY on one freq and
CW/SSB
on the other.  You have to admit operating RTTY and SSB/CW split is
not
exactly a common mode.  SSB and CW split (though not common) does
occur.
In any case, I hope you do not "dump" your K3 because you find a
double
push, and then a "hold" to be that much of an annoyance.

Dick,  K8ZTT

-----Original Message-----
From: Elecraft [mailto:[email protected]] On Behalf Of
Frank
Westphal
Sent: Thursday, October 02, 2014 12:03 AM
To: [email protected]
Subject: [Elecraft] Split N/A

Every time I change modes from CW to RTTY or RTTY to CW I get the
Split
N/A
error message.  I do not get this message when changing modes from
CW to SSB or SSB to CW.   Since I am primarily a DXer who works split
having to change from split operation before mode change and then
change
back to split operation requires a whole lot of button pushing.  This
is
extremely annoying almost to he point of considering selling the K3.
Elecraft told me this was for my own protection.  I don't need a
company
to
tell me this is for my own protection and not willing to make a
product
easy
to operate.  I hope someone out there is radio land has a firmware
fix for
this annoying issue.  Otherwise I have enjoyed operating the K3 for
the
last
year.

Thanks in advance.

Frank
K6FW

-----Original Message-----
From: Elecraft [mailto:[email protected]] On Behalf Of
Frank
Westphal
Sent: Thursday, October 02, 2014 12:03 AM
To: [email protected]
Subject: [Elecraft] Split N/A

Every time I change modes from CW to RTTY or RTTY to CW I get the
Split
N/A
error message.  I do not get this message when changing modes from
CW to SSB or SSB to CW.   Since I am primarily a DXer who works split
having to change from split operation before mode change and then
change
back to split operation requires a whole lot of button pushing.  This
is
extremely annoying almost to he point of considering selling the K3.
Elecraft told me this was for my own protection.  I don't need a
company
to
tell me this is for my own protection and not willing to make a
product
easy
to operate.  I hope someone out there is radio land has a firmware
fix for
this annoying issue.  Otherwise I have enjoyed operating the K3 for
the
last
year.

Thanks in advance.

Frank
K6FW

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

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

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


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

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

Reply via email to