K3 How do I uncouple VFO's?

[k6dgw]

Many thanks to he several who replied to me, my two VFO's are now back
to normal [HOLD the SUB key until the display says UNLINKED].  I did
finally find a reference to it on Page 6 of the current on-line PDF by
doing a FIND on "link" as one email suggested.

I wonder if the complexity of the K3 has surpassed human ability to
adequately describe it in written language? :-)

73,

Fred K6DGW
Auburn CA
______________________________________________________________
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

[Don Wilhelm-4]

I don't think it is beyond the ability to adequately describe in written
language, but it is approaching the limit of short term memory for many
owners - notice that we keep seeing many questions repeated over and
over on the reflector.

And the requests for added functions (or changes in a function) just
keep rolling in, and each one that is incorporated just adds a bit more
complexity to the K3.  It is difficult enough to remember which settings
are remembered per band, which are per VFO, and which are remembered by
mode, (any others I missed?).  I like to think I have a pretty good
memory, but the K3 is challenging like that.

The fortunate thing is that the defaults on the K3 *do* work, and work
just fine for many, the tweaks available are many, but do take some
study to figure out what each one does.

73,
Don W3FPR

Fred Jensen wrote:
> I wonder if the complexity of the K3 has surpassed human ability to
> adequately describe it in written language? :-)
>  
>
______________________________________________________________
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

[Guy, K2AV]

On Sun, Jan 24, 2010 at 2:35 PM, Fred Jensen <[hidden email]> wrote:

> I wonder if the complexity of the K3 has surpassed human ability to
> adequately describe it in written language? :-)

This is hardly a K3 only issue.  Superb technical writing is in
extreme frustrated demand everywhere in the entire general
electronics/computer/software industry.  The complaints are the same.
At the center the root user complaint:

  "I only want to do one little thing and I can't find it in the
centimeter thick manual."

Frustrated reflector users reply with RTFM to the thousandth iteration
of the same question.  On the other side is the newbie who is measured
in studies as having no chance whatsoever of reading the centimeter
thick manual like a book and retaining anything other than a tiny
slice of the total content.

"Read a step and do a step" manuals work well.  But they require
complete reading and adherence from start to finish.

Heathkit instruction manuals and Bell System Practices are two iconic
examples of the best of this genre, but neither could be read like a
book for retention BSP's were a massive library organized by equipment
and task that would take a lifetime to read through once. It was
possible (and required) for the reader to be able to complete the
described task 100% accurately at a competent commercial speed without
ever understanding the workings behind the task. Indeed if retention
was the goal, it failed miserably, because even those of us with years
of experience on a given task would never do a BSP spec'd adjustment
without the particular BSP open in front of us, no more than a 40 year
old veteran pilot would start up or shut down a plane without the
checklist for his equipment.

Carefully staged scientific studies on retention of information from
reading of flat paper manuals have only given terribly discouraging
results.  In many technical support centers, really good techies are
stretched to breaking by customers who only get through a task by an
exercise the techies refer to as "reading the manual" to them.

The K3 itself stepped into dangers documentation areas the minute they
tried something that did not have a precise analogue in the world of
analog radios. That meant there were concepts and behaviors in the
radio which had no precedent in earlier radios and were impossible
(yes, impossible) to duplicate in an analog radio.

That took away one of a writer's best tools, relating something new as
an elaboration or extension of something old and understood.

IMHO, "drill-down" tools have the best chance of moving beyond "read
and do" manuals, implementable only in electronic devices.  But these
are constrained by the absolute need to provide common word glossaries
to key search terms. Too often the user is defeated by not knowing the
single secret word (out of dozens of synonyms and phrase
approximations that will index the required knowledge. This was the
number one issue with the monumental IBM knowledge base, with nothing
in second, third, or fourth place.

Usually creating the glossary/term/phrase index for a drill down
manual requires continuous and ongoing work that carefully collects
"can't find" data from tech support activity and updates the indexing
system. This usually requires expenditure of a full-time employee even
in a smaller company, which adds to expense, and is tempting to forgo.

As a society we hit this problem in the 1930's and it only gets worse.

73, Guy.
______________________________________________________________
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

[hf4me]

This is a HUGE benefit to the PDF versions and the use of the PDF search
engine.  Then all you have to do is figure out what you are lookig for is
called. hi hi

73, de Jim KG0KP

----- Original Message -----
From: "Guy Olinger K2AV" <[hidden email]>
To: <[hidden email]>
Cc: "Elecraft Reflector" <[hidden email]>
Sent: Sunday, January 24, 2010 2:36 PM
Subject: Re: [Elecraft] K3 How do I uncouple VFO's?

> On Sun, Jan 24, 2010 at 2:35 PM, Fred Jensen <[hidden email]> wrote:
>
>> I wonder if the complexity of the K3 has surpassed human ability to
>> adequately describe it in written language? :-)
>
> This is hardly a K3 only issue.  Superb technical writing is in
> extreme frustrated demand everywhere in the entire general
> electronics/computer/software industry.  The complaints are the same.
> At the center the root user complaint:
>
>  "I only want to do one little thing and I can't find it in the
> centimeter thick manual."
>
> Frustrated reflector users reply with RTFM to the thousandth iteration
> of the same question.  On the other side is the newbie who is measured
> in studies as having no chance whatsoever of reading the centimeter
> thick manual like a book and retaining anything other than a tiny
> slice of the total content.
>
> "Read a step and do a step" manuals work well.  But they require
> complete reading and adherence from start to finish.
>
> Heathkit instruction manuals and Bell System Practices are two iconic
> examples of the best of this genre, but neither could be read like a
> book for retention BSP's were a massive library organized by equipment
> and task that would take a lifetime to read through once. It was
> possible (and required) for the reader to be able to complete the
> described task 100% accurately at a competent commercial speed without
> ever understanding the workings behind the task. Indeed if retention
> was the goal, it failed miserably, because even those of us with years
> of experience on a given task would never do a BSP spec'd adjustment
> without the particular BSP open in front of us, no more than a 40 year
> old veteran pilot would start up or shut down a plane without the
> checklist for his equipment.
>
> Carefully staged scientific studies on retention of information from
> reading of flat paper manuals have only given terribly discouraging
> results.  In many technical support centers, really good techies are
> stretched to breaking by customers who only get through a task by an
> exercise the techies refer to as "reading the manual" to them.
>
> The K3 itself stepped into dangers documentation areas the minute they
> tried something that did not have a precise analogue in the world of
> analog radios. That meant there were concepts and behaviors in the
> radio which had no precedent in earlier radios and were impossible
> (yes, impossible) to duplicate in an analog radio.
>
> That took away one of a writer's best tools, relating something new as
> an elaboration or extension of something old and understood.
>
> IMHO, "drill-down" tools have the best chance of moving beyond "read
> and do" manuals, implementable only in electronic devices.  But these
> are constrained by the absolute need to provide common word glossaries
> to key search terms. Too often the user is defeated by not knowing the
> single secret word (out of dozens of synonyms and phrase
> approximations that will index the required knowledge. This was the
> number one issue with the monumental IBM knowledge base, with nothing
> in second, third, or fourth place.
>
> Usually creating the glossary/term/phrase index for a drill down
> manual requires continuous and ongoing work that carefully collects
> "can't find" data from tech support activity and updates the indexing
> system. This usually requires expenditure of a full-time employee even
> in a smaller company, which adds to expense, and is tempting to forgo.
>
> As a society we hit this problem in the 1930's and it only gets worse.
>
> 73, Guy.
> ______________________________________________________________
> 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
>

______________________________________________________________
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