Re: [Elecraft] Blinking amber Light

[George_yv5wz]

Hey Jim!!

Thank you!  I appreciate the time you took for answer me
I was really concern about that led blinking.Now I may sleep ...hahahaha

Greetings from Venezuela, and 73's

George
YV5WZ



--
View this message in context: 
http://elecraft.365791.n2.nabble.com/Blinking-amber-Light-tp7616141p7616151.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: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

Re: [Elecraft] Blinking amber Light

[Jim H via Elecraft]

Hi
The led is part of the battery charger/RTC circuits. It tells you the clock 
 is running.
The was a more complete explanation a long time ago on the Reflector when  
the charger/RTC was started to be shipped.
73
Jim H
K7SSS
 
 
In a message dated 4/9/2016 7:51:41 P.M. Pacific Daylight Time,  
yv...@hotmail.com writes:


I am  newbie with KX3Mine doesnt have keyer paddleso It has two
little  hole for screws to fit the KXPD3  ...I got surprise cause After  
turn
KX3 off .I can see a little ambar light bliking through left  
hole.is
it normal?





--
View this message in  context:  
http://elecraft.365791.n2.nabble.com/Blinking-amber-Light-tp7616141.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: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  k7...@aol.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 arch...@mail-archive.com

Re: [Elecraft] Operating remotely via Direct TV satellite provider

[Cliff Frescura]

Yes, the signal has to travel ~22,300 miles x 2 (up and down).

73,

Cliff K3LL/6

-Original Message-
From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of David
Gilbert
Sent: Saturday, April 09, 2016 8:53 PM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] Operating remotely via Direct TV satellite provider


Not sure about the audio, but I think latency would be the bigger issue.  I
had satellite internet (essentially Hughes. net) for about three years
before a wireless ISP opened shop in our area.  My typical pings were on the
order of 1300-1500 msec.  I don't think you'd want to live with that for
anything other than casual ragchewing.

Dave   AB7E



On 4/9/2016 8:23 PM, Don Strom wrote:
> Is anyone operating their K3 remotely using a satellite provider.
>
> I believe I heard that is not possible with satellite internet at the
remote site?
>
> Something to do with the way the audio is passed via the internet
connection.
>
> Don W0EAR
>
>

__
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 c...@cfcorp.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 arch...@mail-archive.com

Re: [Elecraft] Operating remotely via Direct TV satellite provider

[David Gilbert]

Not sure about the audio, but I think latency would be the bigger 
issue.  I had satellite internet (essentially Hughes. net) for about 
three years before a wireless ISP opened shop in our area.  My typical 
pings were on the order of 1300-1500 msec.  I don't think you'd want to 
live with that for anything other than casual ragchewing.


Dave   AB7E



On 4/9/2016 8:23 PM, Don Strom wrote:

Is anyone operating their K3 remotely using a satellite provider.

I believe I heard that is not possible with satellite internet at the remote 
site?

Something to do with the way the audio is passed via the internet connection.

Don W0EAR




__
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

[Elecraft] Ignore my previous post on Satellite Internet

[Don Strom]

DSL internet is available at my remote site.It is only 10MBPS  speed.  

I believe that is the minimum speed for remote radio so might not work that 
well at that speed.

Don W0EAR

Sent from Mail for Windows 10

__
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

Re: [Elecraft] When do I need atten or preamp?

[Bill Frantz]

This statement may not be true if you are using the weak signal 
modes which allow reception to as much as 20 dB below the noise 
floor. With these modes, you will still need to receive the signal.


(These modes work because the signal isn't random but the noise 
is. By averaging the signal and noise, the noise tends to cancel 
out while the signal comes through.)


73 Bill AE6JV

On 4/10/16 at 8:08 PM, alor...@sbcglobal.net (Al Lorona) wrote:

Since it's not possible to hear signals below the external 
noise floor, it doesn't buy you anything to have more 
sensitivity than the noise floor.

---
Bill Frantz| Since the IBM Selectric, keyboards have gotten
408-356-8506   | steadily worse. Now we have touchscreen keyboards.
www.pwpconsult.com | Can we make something even worse?

__
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

Re: [Elecraft] Operating remotely via Direct TV satellite provider

[Doug Person via Elecraft]

The main problem is latency.  It can affect audio spending on how it is 
buffered.


Doug -- K0DXV

On 4/9/2016 8:23 PM, Don Strom wrote:

Is anyone operating their K3 remotely using a satellite provider.

I believe I heard that is not possible with satellite internet at the remote 
site?

Something to do with the way the audio is passed via the internet connection.

Don W0EAR

Sent from Mail for Windows 10

__
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 k0...@aol.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 arch...@mail-archive.com

Re: [Elecraft] Bogus ERR KEY Conditions?

[Ron D'Eau Claire]

I'd look at the resistance to ground through the opto-isolator with power
off.
I have seen some that are rather "leaky" - it is just a transistor after
all, one that is biased on by light instead of current. Obviously if it has
detectable leakage it could be convincing the K3 that a key line is
grounded. 

73, Ron AC7AC

-Original Message-
From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Rick
Tavan
Sent: Saturday, April 9, 2016 6:04 PM
To: Elecraft Reflector
Subject: [Elecraft] Bogus ERR KEY Conditions?

Sometimes when I power up my K3 with my YCCC SO2R Box powered down, the K3
comes up in ERR KEY mode, disallowing transmission and other functions.
Usually, powering up the SO2R Box and power cycling the K3 clears the
problem. I assumed (erroneously, it turns out) that I had an issue with an
indeterminate state on the key out line from the SO2R Box. But the
principals at YCCC remind me that those circuits are opto-isolated and quite
determinate, even when the box is powered down. They also note that with a
recent release of K3 firmware, similar problems are being reported with
other keyers connected. They suspect that this old error message may have an
additional, new meaning in a recent firmware release, perhaps related to
rx/tx timing. I'm not sure, but it has happened frequently in recent weeks,
sometimes in the middle of an operating session. It is incurable when I am
operating remotely until I visit the site and twiddle key lines. Once it
happens, it doesn't clear itself through remote power cycling or anything
else I've tried.  Any ideas here?

Thanks,

Rick N6XI
-- 

Rick Tavan
Truckee, CA
__
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 r...@elecraft.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 arch...@mail-archive.com

Re: [Elecraft] Elecraft Digest, Vol 144, Issue 12

[Doug Person via Elecraft]

The Pi and BB can indeed run Java and pretty much anything else that 
normally runs on linux.


Doug -- K0DXV

On 4/9/2016 1:50 PM, Dave B via Elecraft wrote:

On 08/04/16 23:36, elecraft-requ...@mailman.qth.net wrote:

Message: 8
Date: Fri, 8 Apr 2016 12:08:49 -0600
From: Ken G Kopp
To:elecraft@mailman.qth.net,k...@yahoogroups.com
Subject: [Elecraft] Elecraft Utilities
Message-ID:

Content-Type: text/plain; charset=UTF-8

Wayne and Eric:

PLEASE don't cave in to the requests of those on the reflectors who are
asking
you to disclose the "genetic makeup" of their radios by publishing the
software
that would enable anyone to modify how a given radio operates.

I see this as no different than a breeder of a thoroughbred breed of dog
opening
the pen and letting all comers mate with the females.  You would end up
with a
"contaminated" breed.

I envision an increased workload at Elecraft in dealing with the 
customers

who
manage to "mess up" their radio's "brains" and want help in restoring 
them

to
the original state.  Nothing but non-profit overhead.

I would be wary ... read "never" ... of buying a used Elecraft 
product for

fear
that it's genetic makeup had been altered and really wasn't an Elecraft
anymore.

Perhaps I'm not understanding something ...

73!

Ken Kopp - K0PP
Full K-line, KX3, PX3, KXPA100, K2/100, W2's, etc.

Hi.

It's not the internal secrets of the radios that is wanting to be 
revealed, just the ability to run the firmware maintenance utilities 
(I'd also include the XG3 tool in the list) on a non ix86 platform, 
such as the Pi.


It could be done independently, as it's trivial to intercept the data 
flowing between the PC and rig, then write from scratch something to 
do the same.   That could then be released as open source so could 
then be built (compiled) to be used on other platforms.  I'm sure 
there are some reading this list that have the skills (I don't, but I 
have looked at the serial traffic between rig and software.)


In the case of the Pi, it already runs Linux.   Plus there are already 
Linux versions of the K3/KX3 and XG3 tools, but as they are not open 
source, they can't be built to run on the ARM equipped Pi's or Beagle 
Bones by us "the paying users" of the equipment.  Shame really.


It would be relatively easy for the authors concerned to create an ARM 
compatible Linux version, but that takes time to do and importantly 
test and perfect, as there are always subtle differences to trip over, 
that and "They" don't have Pi's or BBB's in their shack's, to test on.


A "Command line" version of just the firmware up-loader tool's would 
indeed be a fine compromise for many.   Such things can always be 
wrapped in a simple GUI or desktop launcher for those who suffer 
fright of black screens and just text!  ;-)


The 64/32 bit thing is also possible to overcome, in the same way as 
x86/ARM cpu compatibility, but that does mean potentially multiple 
versions of the same tool's!


I don't know if the Pi (or BB's) can have a Java run time installed.   
If so, the Elecraft tools could be ported to Java, then that can be 
run on anything that supports a JRE.   Many many similar tools for 
other (non radio) and some Ham products are run that way.


Anyway, add my name/call to the list of "interested parties" in 
regards to Pi compatible (however done) Elecraft support tools.


73.

Dave G0WBX.



__
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 k0...@aol.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 arch...@mail-archive.com

[Elecraft] Operating remotely via Direct TV satellite provider

[Don Strom]

Is anyone operating their K3 remotely using a satellite provider.

I believe I heard that is not possible with satellite internet at the remote 
site?

Something to do with the way the audio is passed via the internet connection.

Don W0EAR

Sent from Mail for Windows 10

__
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

[Elecraft] When do I need atten or preamp?

[Al Lorona]

I ran several simulations of the K3 receiver using Genesys (from Keysight 
Technologies) to find out how to use the attenuator and preamp optimally.

An article by Jim Fisk W1HR appeared in October 1975 in ham radio magazine 
where he gave the acceptable noise figure (NF) for a receiver on each HF band 
(excluding WARC bands, which didn't exist at the time). For instance, on 80 
meters your receiver can have a NF as high as 37 dB (because the external noise 
level is so high), on 40 the acceptable NF is 27 dB, on 20 it's 24 dB, etc.

Going by the K3 block diagram in the Owner's Manual, I made a number of 
assumptions so my numbers are undoubtedly off by a couple of dB (probably in 
the pessimistic direction). I also assumed a CW filter of 500 Hz, noise blanker 
off, and an outdoor antenna like a dipole. I modeled everything up to and 
including the 2nd IF amp. I included synthesizer phase noise.

Let's talk about 80 meters. As you would expect, even with the 10 dB attenuator 
switched in the K3 has more than enough sensitivity. Since it's not possible to 
hear signals below the external noise floor, it doesn't buy you anything to 
have more sensitivity than the noise floor. In fact, you could have up to 21 dB 
of attenuation and it would still be totally adequate, so K3S owners can use 
all of their 15 dB if they want to. And definitely DO NOT ever turn on your 
preamp on 80; the only time this would be permissible is when using a small 
receiving loop direct into the RX ANT.

On 40, having the 10 dB attenuator in (and preamp out, of course) is still 
right on the good side of sensitivity. So, kick in your attenuator on 40 with a 
clear conscience... your receiver will be quiet, but not deaf. Additional loss 
will just begin to affect you on 40, but only if you're in the habit of 
listening for signals right at the noise floor.

On 20, the 5 dB attenuator would be okay to use. Again, this is where K3S 
owners have a little more flexibility. If you have a K3 don't use the 
attenuator, unless you want to.

The preamp really isn't needed until you get to 10 meters, according to my 
simulations. Using it below 10 meters is just asking for unnecessary noise!

On SSB, the margins are even better [by 7 dB] because of the wider 2.7 kHz 
bandwidth. And if the HF bands are noisier nowadays than in 1975 due to plasma 
TVs, wireless devices and SMPSs, the K3 would have even more margin than I have 
presented here.



Al  W6LX
__
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

[Elecraft] Blinking amber Light

[George_yv5wz]

I am newbie with KX3Mine doesnt have keyer paddleso It has two
little hole for screws to fit the KXPD3  ...I got surprise cause After turn
KX3 off .I can see a little ambar light bliking through left hole.is
it normal?

 



--
View this message in context: 
http://elecraft.365791.n2.nabble.com/Blinking-amber-Light-tp7616141.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: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

[Elecraft] Bogus ERR KEY Conditions?

[Rick Tavan]

Sometimes when I power up my K3 with my YCCC SO2R Box powered down, the K3
comes up in ERR KEY mode, disallowing transmission and other functions.
Usually, powering up the SO2R Box and power cycling the K3 clears the
problem. I assumed (erroneously, it turns out) that I had an issue with an
indeterminate state on the key out line from the SO2R Box. But the
principals at YCCC remind me that those circuits are opto-isolated and
quite determinate, even when the box is powered down. They also note that
with a recent release of K3 firmware, similar problems are being reported
with other keyers connected. They suspect that this old error message may
have an additional, new meaning in a recent firmware release, perhaps
related to rx/tx timing. I'm not sure, but it has happened frequently in
recent weeks, sometimes in the middle of an operating session. It is
incurable when I am operating remotely until I visit the site and twiddle
key lines. Once it happens, it doesn't clear itself through remote power
cycling or anything else I've tried.  Any ideas here?

Thanks,

Rick N6XI
-- 

Rick Tavan
Truckee, CA
__
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

Re: [Elecraft] [K3] Setting RF gain & AGC correctly

[Fred Jensen]

I left all of Bill's post below for context.  Full disclosure - 95% CW

My experience parallels Bill's for much the same reasons.  My K3 [#642] 
has had two EEINIT's, and I haven't changed the AGC settings since the 
second one, 4 or 5 years ago.  The K3 AGC parameters are many and have 
interacting effects.  When playing with them, often I was unable to 
discern a difference between choices, even going very slowly and 
operating for awhile between changes.


I find the APF to be useful with weak signals of course, but also with 
moderate signals in deep QSB ... with APF I don't lose it completely 
even though it went to near ESP levels briefly.  I have spent some 
listening time to SM, LA, OH, and the like during auroral events, with 
rapid, deep QSB, and with AGC off and riding the RF Gain.  Given that 
the propagation under these conditions is essentially a chaotic 
function, I may ... or have just imagined ... a very subtle improvement 
over just running RF at max with AGC on.


I had to max the AF GAIN on my SX-28 and ride the RF of course, now many 
years later, I find the  stock K3 settings to be close to very good for me.


Grizzled Old Engineer advice to an aspiring new engineer [me]:  "The 
fewer the knobs, the less problems from the users."


73,

Fred K6DGW
- Northern California Contest Club
- CU in the Cal QSO Party 1-2 Oct 2016
- www.cqp.org

On 4/9/2016 4:32 PM, Bill Frantz wrote:

Note that to change some of the AGC settings you must have Tech MD ON.

I tried these settings and went back to the stock settings. I think the
reasons were:

I don't run pileups. I am mostly a S contester, and always in the
pileup rather than working it for DX. (Just how many people need Santa
Clara County CA?), so most of the improvements don't affect me very much.

When I'm listening to weak DX, the higher SLP keeps the occasional
person who forgets to go into split mode (and the up police) from
blasting out my eardrums.

My normal background noise on 20M is about S2. (It's about S5 on 160M.)
I think this means that I'm not getting AGC from the normal background.
BTW, I don't know why my noise levels are so low living in suburbia. I
always seem to be a couple of S units weaker than others I hear giving
honest signal reports. In any case, I have enough sensitivity to get the
band noise, and I can certainly hear a lot of stations which can't hear me.

When I run digital modes, I don't have to ride the RF gain to keep the
audio signal to the computer below overload, a nice convenience.

I will have to try turning AGC off when using the Audio Frequency
Peaking feature. With AGC on, it only seems to do a little compared with
50 or 100 HZ on the DSP filter. The DSP filter technique helps suppress
slightly off frequency strong signals better too.

73 Bill AE6JV


__
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

Re: [Elecraft] [K3] Setting RF gain & AGC correctly

[Bill Frantz]

Note that to change some of the AGC settings you must have Tech 
MD ON.


I tried these settings and went back to the stock settings. I 
think the reasons were:


I don't run pileups. I am mostly a S contester, and always in 
the pileup rather than working it for DX. (Just how many people 
need Santa Clara County CA?), so most of the improvements don't 
affect me very much.


When I'm listening to weak DX, the higher SLP keeps the 
occasional person who forgets to go into split mode (and the up 
police) from blasting out my eardrums.


My normal background noise on 20M is about S2. (It's about S5 on 
160M.) I think this means that I'm not getting AGC from the 
normal background. BTW, I don't know why my noise levels are so 
low living in suburbia. I always seem to be a couple of S units 
weaker than others I hear giving honest signal reports. In any 
case, I have enough sensitivity to get the band noise, and I can 
certainly hear a lot of stations which can't hear me.


When I run digital modes, I don't have to ride the RF gain to 
keep the audio signal to the computer below overload, a nice convenience.


I will have to try turning AGC off when using the Audio 
Frequency Peaking feature. With AGC on, it only seems to do a 
little compared with 50 or 100 HZ on the DSP filter. The DSP 
filter technique helps suppress slightly off frequency strong 
signals better too.


73 Bill AE6JV

On 4/9/16 at 12:44 AM, gm3...@ifwtech.co.uk (Ian White) wrote:


Following the release of FW v4.51, the consensus within the
[K3-contesting] Yahoo group about the most important settings for DXing
and contesting has been as follows.
* AGC THR: increase to at least 8 (from default = 5) and preferably to
12, and then take some time to become re-accustomed to the increased
range of audio levels [2]. (Some users recommend as high as 14, if your
ears can handle it.)

* AGC SLP: decrease to 8 or even less (from default = 12). Lower SLP
settings allow stronger signals to sound somewhat louder, and thus more
realistic, but the range of variation will be partly determined by the
THR setting already made; so always experiment with THR first, and with
SLP afterwards.
* AGC DCY = SOFT (not default=NOR). The User Manual claims that "The
SOFT setting can reduce IMD caused by traditional AGC, and is especially
useful in 'pileup' conditions, in some cases making it unnecessary to
turn AGC off."



Bill Frantz|"Insofar as the propositions of mathematics 
refer to
408-356-8506   | reality, they are not certain; and insofar 
they are
www.pwpconsult.com | certain, they do not refer to reality.” 
-- Einstein


__
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

Re: [Elecraft] New KX3 S/N 8769 with a question

[Joel Black]

You know, I think the first KX3 I built had that same issue. Mine was because 
of some extra PCB material left on the PCB but I thought that issue had been 
resolved.

Regardless, I’d wait and see what the tech support folks say.

73,
Joel - W4JBB

> 
> On Sat, Apr 9, 2016 at 5:03 AM, Phillip Zminda  > wrote:
> 
>> I just completed the build on my new KX3 last night and have it up and
>> running but ran into one problem with the build. My kit had the errata
>> sheet with the change in screw length to 2-56 X 1/4 in long for the battery
>> holders. I could not get the screws started on both ends of either battery
>> holder. If I got one screw in, the other end was raised up and the other
>> screw didn’t seem to go through far enough to get the threads started.
>> After struggling for a while I ended up using one of the 9/32 in screws and
>> on one of them and a pan-head screw on the other end of each battery
>> holder. This was just to get the rig completed and tested. I do want to
>> eventually use batteries on occasion so I do need to fix this. I can see
>> where the screw heads sticking up can be a risk.
>> 
>> I am looking for help on getting the battery holders mounted correctly
>> with the screw heads seated into the plastic.
>> 
>> Loving the rig, made my 1st QSO with it last night and hoping for some
>> time with it this weekend.
>> 
>> Thanks,
>> 
>> Phil N3ZP
__
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

[Elecraft] K3-Front Panel switches

[Fred Jensen]

Thanks to all for the advice, I made a list of things that I will do 
first, beginning with some archive lookups.  Removal/re-install front 
panel [after some De-Oxit on the pins will be next.  We'll see how this 
goes.


73,

Fred K6DGW
- Northern California Contest Club
- CU in the Cal QSO Party 1-2 Oct 2016
- www.cqp.org
__
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

Re: [Elecraft] S: Re: Elecraft Utilities

[Dave Cole]

No one said anything about a warranty fix, in fact I mentioned a few
days ago that Elecraft might be discovering a profit center...

Please expand on just exactly what is so telling?

-- 
73's, and thanks,
Dave (NK7Z)

For software/hardware reviews see:
http://www.nk7z.net

For MixW support see:
https://groups.yahoo.com/neo/groups/mixw/info

For SSTV help see:
http://groups.yahoo.com/neo/groups/MM-SSTV/info


On Sat, 2016-04-09 at 13:32 -0500, Kevin Stover wrote:
> And who gets to fix the radio, under warrantee of course, when this
> home 
> brewed command line utility bricks the radio? Through this whole 
> discussion I've heard very little from proponents of open sourcing
> the 
> utilities on this minor little point. Telling isn't it.
> 
> This could be a profit center for Elecraft now that I think about it.
> If 
> it were me, I'd charge $1,500 to fix any Elecraft product which has
> had 
> it's brains blown out by some home brewed and unsupported flash
> utility.
> 
> 
> 
> 
> On 4/9/2016 1:13 PM, ei6iz.Brendan Minish wrote:
> > 
> > I think that all most of us would need would be a command line
> > utility that
> > can be used to update firmware and perhaps back up settings.
> > Either making this open source or just releasing the protocol spec
> > would be
> > all that's needed.
> > This would not require the firmware to be open sourced, it would
> > just mean
> > that the Elecraft provided firmwares can be uploaded  to the radio.
> > 
> > Icing on the cake would be the ability to make radio backups
> > 
__
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

Re: [Elecraft] Elecraft Digest, Vol 144, Issue 12

[Dave B via Elecraft]

On 08/04/16 23:36, elecraft-requ...@mailman.qth.net wrote:

Message: 8
Date: Fri, 8 Apr 2016 12:08:49 -0600
From: Ken G Kopp
To:elecraft@mailman.qth.net,k...@yahoogroups.com
Subject: [Elecraft] Elecraft Utilities
Message-ID:

Content-Type: text/plain; charset=UTF-8

Wayne and Eric:

PLEASE don't cave in to the requests of those on the reflectors who are
asking
you to disclose the "genetic makeup" of their radios by publishing the
software
that would enable anyone to modify how a given radio operates.

I see this as no different than a breeder of a thoroughbred breed of dog
opening
the pen and letting all comers mate with the females.  You would end up
with a
"contaminated" breed.

I envision an increased workload at Elecraft in dealing with the customers
who
manage to "mess up" their radio's "brains" and want help in restoring them
to
the original state.  Nothing but non-profit overhead.

I would be wary ... read "never" ... of buying a used Elecraft product for
fear
that it's genetic makeup had been altered and really wasn't an Elecraft
anymore.

Perhaps I'm not understanding something ...

73!

Ken Kopp - K0PP
Full K-line, KX3, PX3, KXPA100, K2/100, W2's, etc.

Hi.

It's not the internal secrets of the radios that is wanting to be 
revealed, just the ability to run the firmware maintenance utilities 
(I'd also include the XG3 tool in the list) on a non ix86 platform, such 
as the Pi.


It could be done independently, as it's trivial to intercept the data 
flowing between the PC and rig, then write from scratch something to do 
the same.   That could then be released as open source so could then be 
built (compiled) to be used on other platforms.  I'm sure there are some 
reading this list that have the skills (I don't, but I have looked at 
the serial traffic between rig and software.)


In the case of the Pi, it already runs Linux.   Plus there are already 
Linux versions of the K3/KX3 and XG3 tools, but as they are not open 
source, they can't be built to run on the ARM equipped Pi's or Beagle 
Bones by us "the paying users" of the equipment.  Shame really.


It would be relatively easy for the authors concerned to create an ARM 
compatible Linux version, but that takes time to do and importantly test 
and perfect, as there are always subtle differences to trip over, that 
and "They" don't have Pi's or BBB's in their shack's, to test on.


A "Command line" version of just the firmware up-loader tool's would 
indeed be a fine compromise for many.   Such things can always be 
wrapped in a simple GUI or desktop launcher for those who suffer fright 
of black screens and just text!  ;-)


The 64/32 bit thing is also possible to overcome, in the same way as 
x86/ARM cpu compatibility, but that does mean potentially multiple 
versions of the same tool's!


I don't know if the Pi (or BB's) can have a Java run time installed.   
If so, the Elecraft tools could be ported to Java, then that can be run 
on anything that supports a JRE.   Many many similar tools for other 
(non radio) and some Ham products are run that way.


Anyway, add my name/call to the list of "interested parties" in regards 
to Pi compatible (however done) Elecraft support tools.


73.

Dave G0WBX.



__
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

Re: [Elecraft] S: Re: Elecraft Utilities

[Kevin Stover]

My perspective comes from the early days of home brewing PC's.
In the "good old days" with soldered BIOS EEPROMS and manufacturer 
approved command line flash utilities it was entirely possible to trash 
a motherboard. Lose power during a BIOS update or a cosmic ray takes out 
a section of the chip (I'm only partially kidding) and you got to buy a 
new motherboard. Your chances were 60/40 at best, a little better than 
flipping a coin. Next came socketed BIOS where all you had to do after a 
failed flash was buy a new chip from AMI, Award or Phoenix.


These days with dual BIOS chips on board, BIOS backed up to hard drive 
and GUI flash utilities it's a lot easier to recover from a failed flash 
and not nearly as expensive, but failures still happen. That's with mobo 
manufacturer approved and supplied utilities. How many posts do we get 
here a month from folks who have to do an EEINIT or at the very least 
re-flash after a failure?


If I was Elecraft I would run away from this potential Pandora's Box 
rapidly.



On 4/9/2016 1:43 PM, Ken G Kopp wrote:

Well said, Kevin!

This was my initial intent when I started this thread,
but you've done a better job of stating the obvious.

73!

Ken Kopp - K0PP




--
R. Kevin Stover
AC0H
ARRL
FISTS #11993
SKCC #215
NAQCC #3441


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

__
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

Re: [Elecraft] New KX3 S/N 8769 with a question

[Brendon Whateley]

IIRC, I had a similar problem and ended up basically ignoring it. I tried a
bunch of times, but could never quite get it to work the way the
instructions expected.

I've not had any issues... so I've just left it as is. I am just careful
when installing the (rechargeable) batteries to make sure the screw heads
can't puncture the battery outer layer. I think that was the risk of the
screw heads.

- Brendon

On Sat, Apr 9, 2016 at 5:03 AM, Phillip Zminda  wrote:

> I just completed the build on my new KX3 last night and have it up and
> running but ran into one problem with the build. My kit had the errata
> sheet with the change in screw length to 2-56 X 1/4 in long for the battery
> holders. I could not get the screws started on both ends of either battery
> holder. If I got one screw in, the other end was raised up and the other
> screw didn’t seem to go through far enough to get the threads started.
> After struggling for a while I ended up using one of the 9/32 in screws and
> on one of them and a pan-head screw on the other end of each battery
> holder. This was just to get the rig completed and tested. I do want to
> eventually use batteries on occasion so I do need to fix this. I can see
> where the screw heads sticking up can be a risk.
>
> I am looking for help on getting the battery holders mounted correctly
> with the screw heads seated into the plastic.
>
> Loving the rig, made my 1st QSO with it last night and hoping for some
> time with it this weekend.
>
> Thanks,
>
> Phil N3ZP
>
> __
> 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 bren...@whateley.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 arch...@mail-archive.com

Re: [Elecraft] S: Re: Elecraft Utilities

[Doug Person via Elecraft]

If it works it's not likely to brick the K3.  The Utility program has 
nothing to do with the firmware.  Either the connection to the K3 works 
or it doesn't.  Once it works, loading the firmware is not complicated.


An awful lot of linux programs have been successfully recompiled to work 
on the non X86 platforms.  The catalog on the Pi is uuugh.  So its hard 
to say how complicated it would be to recompile for the Pi (and 
others).  Could be fairly trivial. All depends on how well it conforms 
to the standard linux libraries.


What linux et, al lacks is a good best practices to guide developers 
down a path of using a very standard collection of libs that are 
generally available on 99% of linux distros.  Right now it's the wild 
west and the linux reputation suffers as a result.


So, I hope all the Elecraft linux software becomes available for Pi.  If 
not - oh well.  Tiny X86 boxes are right around the corner.


Doug -- K0DXV

On 4/9/2016 11:32 AM, Kevin Stover wrote:
And who gets to fix the radio, under warrantee of course, when this 
home brewed command line utility bricks the radio? Through this whole 
discussion I've heard very little from proponents of open sourcing the 
utilities on this minor little point. Telling isn't it.


This could be a profit center for Elecraft now that I think about it. 
If it were me, I'd charge $1,500 to fix any Elecraft product which has 
had it's brains blown out by some home brewed and unsupported flash 
utility.





On 4/9/2016 1:13 PM, ei6iz.Brendan Minish wrote:
I think that all most of us would need would be a command line 
utility that

can be used to update firmware and perhaps back up settings.
Either making this open source or just releasing the protocol spec 
would be

all that's needed.
This would not require the firmware to be open sourced, it would just 
mean

that the Elecraft provided firmwares can be uploaded  to the radio.

Icing on the cake would be the ability to make radio backups





__
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

[Elecraft] S: Re: Elecraft Utilities

[Ken G Kopp]

Well said, Kevin!

This was my initial intent when I started this thread,
but you've done a better job of stating the obvious.

73!

Ken Kopp - K0PP


On Sat, Apr 9, 2016 at 12:32 PM, Kevin Stover 
wrote:

> And who gets to fix the radio, under warrantee of course, when this home
> brewed command

line utility bricks the radio? Through this whole discussion I've heard
> very little from proponents

   of open sourcing the utilities on this minor little point. Telling isn't
it.

This could be a profit center for Elecraft now that I think about it. If it
were me, I'd charge $1,500
to fix any Elecraft product which has had it's brains blown out by some
home brewed and unsupported
flash utility.





On 4/9/2016 1:13 PM, ei6iz.Brendan Minish wrote:

> I think that all most of us would need would be a command line utility that
>> can be used to update firmware and perhaps back up settings.
>> Either making this open source or just releasing the protocol spec would
>> be
>> all that's needed.
>> This would not require the firmware to be open sourced, it would just mean
>> that the Elecraft provided firmwares can be uploaded  to the radio.
>>
>> Icing on the cake would be the ability to make radio backups
>>
>>
> --
> R. Kevin Stover
> AC0H
> ARRL
> FISTS #11993
> SKCC #215
> NAQCC #3441
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> __
> 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 kengk...@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 arch...@mail-archive.com

Re: [Elecraft] S: Re: Elecraft Utilities

[Kevin Stover]

And who gets to fix the radio, under warrantee of course, when this home 
brewed command line utility bricks the radio? Through this whole 
discussion I've heard very little from proponents of open sourcing the 
utilities on this minor little point. Telling isn't it.


This could be a profit center for Elecraft now that I think about it. If 
it were me, I'd charge $1,500 to fix any Elecraft product which has had 
it's brains blown out by some home brewed and unsupported flash utility.





On 4/9/2016 1:13 PM, ei6iz.Brendan Minish wrote:

I think that all most of us would need would be a command line utility that
can be used to update firmware and perhaps back up settings.
Either making this open source or just releasing the protocol spec would be
all that's needed.
This would not require the firmware to be open sourced, it would just mean
that the Elecraft provided firmwares can be uploaded  to the radio.

Icing on the cake would be the ability to make radio backups



--
R. Kevin Stover
AC0H
ARRL
FISTS #11993
SKCC #215
NAQCC #3441


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

__
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

Re: [Elecraft] K3 Codecs and Remote Desktop

[Joe Subich, W4TV]

My question is "What is the difference between the Spectra-Vue codec
and the K3 codac? Why is the audio available on the SDR-14 but not on
the K3.


RF Space audio is data within the program DLL - there is no hardware
CODEC (you can't see SDR-14, SDR-IQ, etc. as a "sound card" in Windows
Device Manager)

The K3S USB audio is defined by the hardware on the specific PC (and
appears as a sound card in Windows Device Manger).

You *might* be able to find a "remote sound card driver" that will
mirror the K3S USB Audio CODEC onto a remote PC but good luck ... you
will probably have more luck using a VoIP package to transport the
audio from one sound card (the K3S) to the other (your laptop) than
installing the remote K3S sound card onto your laptop.

73,

  ... Joe, W4TV


On 4/9/2016 12:24 PM, wa9fvp wrote:

After installing the KIO3B, I had no problem passing audio to and from my W7
PC.  The speaker and microphone codec appear in the Sound Control panel.
When I try to use Remote desktop, the codecs a are gone and there's no sound
on my Dell laptop.  When I check the Sound Control the only sound device
that appears in the Playback tab is a Speaker and the Recording tab is
blank.When I check "Play on remote computer"  and launch RDT, The Sound
Control shows the K3 codecs and I can hear sound on the host computer.

Before I launched RDT, at the Local Resources tab/Settings I checked "Play
on this computer".  Here's my conundrum.  For a pan-adapter, I use an SDR-14
software defined receiver from RF-Space.  The Spectra-Vue software is
compatible with the K3.  I feeds off the K3's IF and it functions like the
P3 except the spectrum display is on the PC monitor.   Within the span it
can also serve as a 2nd or 3rd receiver and the audio from each demodulator
is fed separately to each speaker.   When I use Remote Desktop the audio is
passed to my Laptop and when I click on the Taskbar-Speaker icon, the
Spectra-Vue volume control is shown.

My question is "What is the difference between the Spectra-Vue codec and the
K3 codac?   Why is the audio available on the SDR-14 but not on the K3.



-
Jack WA9FVP

Sent from my TRS-80 :-)
--
View this message in context: 
http://elecraft.365791.n2.nabble.com/K3-Codecs-and-Remote-Desktop-tp7616124.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: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 arch...@mail-archive.com

Re: [Elecraft] S: Re: Elecraft Utilities

[ei6iz.Brendan Minish]

I think that all most of us would need would be a command line utility that
can be used to update firmware and perhaps back up settings.
Either making this open source or just releasing the protocol spec would be
all that's needed.
This would not require the firmware to be open sourced, it would just mean
that the Elecraft provided firmwares can be uploaded  to the radio.

Icing on the cake would be the ability to make radio backups
On 9 Apr 2016 16:28, "James Bennett"  wrote:

> After reading a half-bazillion posts on this I feel compelled to add my
> two cents worth.
>
> I've been around computers a very long time, starting my career back in
> the days of IBM's "big iron" mainframes. Have had my share of Windows-based
> PCs at work and at home, and ten years ago converted to being a "Mac head".
> Early last year I got my first Raspberry Pi and more recently acquired the
> newer version 3. I also run a Ubuntu Linux guest on my iMac under VMware
> Fusion. My primary reason for having these Ubuntu and RPi Linux instances
> was to set up WSJT-X, WSPR, and Quisk so I could experiment with and
> operate a tiny QRPp SDR while my K-line is used as my primary station rig.
>
> What I see as huge stumbling blocks in this whole Linux thing are twofold:
> the need in many cases to compile an application, and having to deal with
> pre-requisite packages. A pre-built package, with everything in it, is
> IMHO, the only way to go. I can't begin to count the number of hours I've
> spent dorking around with this pre-req crud and getting an application
> correctly compiled. These are hours I would have much sooner spent actually
> using the application instead of tracking down what the correct version of
> pre-req I need, where to get it, yada, yada. That stuff is fun for a while
> but not how I want to spend my time.
>
> Anyone new to Linux and used to simply downloading an application from the
> web or dropping a disk into their machine on Windows or a Mac will have a
> real eye opening experience when they first attempt compiling an
> application on Linux. The opportunity for failure is huge and thinking that
> Elecraft would consider for one second having to support this sort of thing
> - hahahahahaha Yeah, if you are a Linux guru it might be a piece of
> cake for you, but for the rest of us - major PITA.
>
>
>
> Jim Bennett / W6JHB
> Folsom, CA
> __
> 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 ei6iz.bren...@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 arch...@mail-archive.com

Re: [Elecraft] K3 Codecs and Remote Desktop

[lstavenhagen]

Most likely, the software device for the K3 sound card doesn't support Remote
Desktop. It looks like doing things like remote rendering of sound requires
specific support in the application on the server side via RDP (Remote
Desktop Protocol) and using the Remote Desktop API. 

Apparently this support has been added in the Spectra-Vue application which
would be why it can render sound on the RD client. Which is kind of
cool! 

See if there's a way to pass the K3 audio into the Spectra-Vue application
itself - then it might "pass through" to your remote machine using its RDP
support

73,
LS
W5QD





--
View this message in context: 
http://elecraft.365791.n2.nabble.com/K3-Codecs-and-Remote-Desktop-tp7616124p7616126.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: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

Re: [Elecraft] [k3] Isotropic Antenna

[Alan Bloom]

Years ago, a local ham who was acting as an Isotron distributor brought 
the 80 meter version to the club's Field Day.  I discovered I got out a 
lot better by unscrewing the shield of the coax connector and just using 
the feedline as an antenna.  :=)


Alan N1AL


On 04/09/2016 07:17 AM, Doug Person via Elecraft wrote:
The issue was June 1998.  The article was focused on how to construct 
one.  73 (Wayne Green) wasn't interested in all the tables of 
performance data.

...


On 4/8/2016 10:13 PM, Walter Underwood wrote:
The archives for 73 Magazine are online, so if you remember when, 
folks could read the article.


https://archive.org/details/73-magazine 



wunder
K6WRU
Walter Underwood
CM87wj
http://observer.wunderwood.org/ (my blog)

On Apr 8, 2016, at 8:05 PM, Doug Person via Elecraft 
 wrote:


...
They resonate, have good SWR bandwidth and generally radiate 5 watts 
of the 100 watts that goes into them. A "magnetic loop" blows it 
away.  I sold the sample Isotron I bought at a hamfest for $5. 
(Bottom line - they are, as we say in the software business, crapware)



On 4/7/2016 5:12 PM, Jim Brown wrote:
This so-called "antenna" is at best dumb, and at worst a rip-off. 

...
On Thu,4/7/2016 2:41 AM, Petr, OK1RP/M0SIS wrote:

I am sure that David talked about an Isotron antennas like this:
https://www.isotronantennas.com/

I intensively tested/used this antenna in 90's on 40m (product 
from Sigi,

DK9FN) and I have to say it is a nightmare in overall. From my own
experiences the performance of this toy was highly dependent to the
grounding availability, bandwidth was very small and tunning was 
influenced

by ground only but also by closed objects a lot.




__
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

[Elecraft] K3 Codecs and Remote Desktop

[wa9fvp]

After installing the KIO3B, I had no problem passing audio to and from my W7
PC.  The speaker and microphone codec appear in the Sound Control panel. 
When I try to use Remote desktop, the codecs a are gone and there's no sound
on my Dell laptop.  When I check the Sound Control the only sound device
that appears in the Playback tab is a Speaker and the Recording tab is
blank.When I check "Play on remote computer"  and launch RDT, The Sound
Control shows the K3 codecs and I can hear sound on the host computer.  

Before I launched RDT, at the Local Resources tab/Settings I checked "Play
on this computer".  Here's my conundrum.  For a pan-adapter, I use an SDR-14
software defined receiver from RF-Space.  The Spectra-Vue software is
compatible with the K3.  I feeds off the K3's IF and it functions like the
P3 except the spectrum display is on the PC monitor.   Within the span it
can also serve as a 2nd or 3rd receiver and the audio from each demodulator
is fed separately to each speaker.   When I use Remote Desktop the audio is
passed to my Laptop and when I click on the Taskbar-Speaker icon, the
Spectra-Vue volume control is shown.   

My question is "What is the difference between the Spectra-Vue codec and the
K3 codac?   Why is the audio available on the SDR-14 but not on the K3. 



-
Jack WA9FVP

Sent from my TRS-80 :-)
--
View this message in context: 
http://elecraft.365791.n2.nabble.com/K3-Codecs-and-Remote-Desktop-tp7616124.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: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

Re: [Elecraft] S: Re: Elecraft Utilities

[James Bennett]

After reading a half-bazillion posts on this I feel compelled to add my two 
cents worth. 

I've been around computers a very long time, starting my career back in the 
days of IBM's "big iron" mainframes. Have had my share of Windows-based PCs at 
work and at home, and ten years ago converted to being a "Mac head". Early last 
year I got my first Raspberry Pi and more recently acquired the newer version 
3. I also run a Ubuntu Linux guest on my iMac under VMware Fusion. My primary 
reason for having these Ubuntu and RPi Linux instances was to set up WSJT-X, 
WSPR, and Quisk so I could experiment with and operate a tiny QRPp SDR while my 
K-line is used as my primary station rig.

What I see as huge stumbling blocks in this whole Linux thing are twofold: the 
need in many cases to compile an application, and having to deal with 
pre-requisite packages. A pre-built package, with everything in it, is IMHO, 
the only way to go. I can't begin to count the number of hours I've spent 
dorking around with this pre-req crud and getting an application correctly 
compiled. These are hours I would have much sooner spent actually using the 
application instead of tracking down what the correct version of pre-req I 
need, where to get it, yada, yada. That stuff is fun for a while but not how I 
want to spend my time.

Anyone new to Linux and used to simply downloading an application from the web 
or dropping a disk into their machine on Windows or a Mac will have a real eye 
opening experience when they first attempt compiling an application on Linux. 
The opportunity for failure is huge and thinking that Elecraft would consider 
for one second having to support this sort of thing - hahahahahaha Yeah, if 
you are a Linux guru it might be a piece of cake for you, but for the rest of 
us - major PITA.



Jim Bennett / W6JHB
Folsom, CA
__
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

[Elecraft] Wanted K3

[Doug Ellmore]

I am interested in finding a used K3/100. Please contact me off list with
specs and price.

Must have at least 100w, one 8 pole 2.8 kHz filter, DVR, and ATU.

Doug NA1DX
__
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

Re: [Elecraft] S: Re: Elecraft Utilities

[Doug Person via Elecraft]

X86 processors are now being placed on Arduino sized boards.  There are 
also full X86 computers as small as an over sized dongle. The Raspberry 
Pi is a beautiful piece of engineering.  But, it is only a matter of 
time before you can buy an X86 in a similar package running Windows 10.  
Microsoft has already released Windows 10 for Raspberry PI and the Intel 
Edison is just the first shot at bringing X86 down to the Pi level.  
It's probably just a matter of months before you can choose a Pi or an 
Intel equipped X86 equivalent.


That said, jumping on the Pi train might be short-lived trip.  It's 
probably possible to diddle the compiler settings and get the Utilities 
working on Pi.  But, are there really enough interested parties to make 
that worth while?  Hard to say.


Meanwhile, I love my little Pi boxes and continue to be amazed at what 
they are capable of.


Doug -- K0DXV

On 4/9/2016 5:52 AM, Kevin Stover wrote:

Well
Elecraft have decided to do neither for the time being so

On 4/9/2016 3:20 AM, Andy McMullin wrote:

Don,

Just to clarify. The Raspberry Pi uses a range of completely standard 
Linux operating systems EXCEPT that it does not use the X86 range of 
processors. It uses the ARM range instead. It does not need to 
“emulate” Linux in all aspects — it IS Linux in all aspects. 
Applications that are correctly compiled work just like those for 
other Linux systems. For example, the standard FLDIGI source for 
Linux just recompiles under Linux on the Raspberry Pi and then works.


The designers of the Raspberry Pi are unlikely to rework their 
hardware to use a different processor — especially when the ARM one 
powers so many smartphones and other modern devices and the X86 one 
is hamstrung by needing to retain backwards compatibility with a 
design from over 30 years ago.


On the other hand, for the Elecraft Utilities to work on the Pi, all 
that would be required would be to compile the Linux source BUT for 
the ARM processor rather than the X86. Either Elecraft could do it 
or, as was suggested, they could release the source and (almost) 
anyone could do it.


—
Regards
Andy, G8TQH



On 8 Apr 2016, at 23:32, Don Wilhelm  wrote:

To ask Elecraft to provide Utilities for any and all small operating 
systems is unreasonable IMHO.  The mainstream OS of Windows, Mac and 
Linux *are* supported, but recently there have been a number of OS 
variants that have appeared on the horizon (and there are likely to 
be more to come) and that includes the Rasberry Pi, and several 
other 'computers' that have recently appeared on the hobbyist market.


Just because the most recent device can do RS-232 (or USB) 
communications does not mean it should be individually supported by 
hardware manufacturers.  It would be more productive to encourage 
those writing software for those devices to request that they 
emulate Windows, or Mac, or Linux in all aspects so one could use 
the applications written for those mainstream OS versions to run 
without problems on whichever platform those "hobby" devices may be 
using.


If the Rasberry Pi OS becomes stable over time, and is in use for a 
significant percentage of the Elecraft community, then it may 
eventually be supported on its own,  but for the time being, as I 
understand the Raspberry Pi, its OS is a version of Linux, but not 
everything works like the main Linux platform -- so until you can 
convince the Raspberry Pi developers to create a version of its OS 
that is compatible in all respects to Linux, you will not have 
success.  The market penetration for Raspberry Pi is just not great 
enough at this time for manufacturers to create software that will 
run on it.  Much to the dismay of those who have Raspberry Pi 
running and controlling their ham stations.


73,
Don W3FPR


__
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 kevin.sto...@mediacombb.net





__
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

Re: [Elecraft] [k3] Isotropic Antenna

[Doug Person via Elecraft]

The issue was June 1998.  The article was focused on how to construct 
one.  73 (Wayne Green) wasn't interested in all the tables of 
performance data.  He also wasn't interested in an excellent interview I 
did with Wayne and Eric early on.  In so many words he was pretty clear 
that unless Elecraft was going to be a regular advertiser, he wasn't 
going to devote space to promoting what was essentially a startup at the 
time.  Poor judgement on his part.  I think Wayne Green perfectly 
defined the term curmudgeon.


Doug -- K0DXV

On 4/8/2016 10:13 PM, Walter Underwood wrote:

The archives for 73 Magazine are online, so if you remember when, folks could 
read the article.

https://archive.org/details/73-magazine 


wunder
K6WRU
Walter Underwood
CM87wj
http://observer.wunderwood.org/ (my blog)


On Apr 8, 2016, at 8:05 PM, Doug Person via Elecraft  
wrote:

I wrote an article for 73 many years ago where I effectively remade the Isotron 
antenna with parts from Home Depot.  At the time, a 20 meter version could be 
built for about $15.  I tested my version extensively and for the most part a 
dipole made with two Hamsticks was quite superior.

They resonate, have good SWR bandwidth and generally radiate 5 watts of the 100 watts 
that goes into them. A "magnetic loop" blows it away.  I sold the sample 
Isotron I bought at a hamfest for $5. (Bottom line - they are, as we say in the software 
business, crapware)

Doug -- K0DXV

On 4/7/2016 5:12 PM, Jim Brown wrote:

This so-called "antenna" is at best dumb, and at worst a rip-off. As master 
antenna-designer N6BT wrote some years ago, "everything 'works,' even a light bulb." He 
demonstrated this by mounting a a light bulb on a wooden fencepost, feeding with coax that he had 
carefully choked so that the coax could not radiate, and working all continents with it.

As others have noted, antennas like magnetic loops, loaded whips (HamSticks, 
etc.), and long wires are the weapons of choice with limited space and/or 
requirements of minimal visibility. If the frame of the building is 
non-metallic, indoor antennas can work (but can also be mondo noisy on RX). If 
the frame is metallic, the antenna must be outside. The good news is that the 
building frame will work fine as a counterpoise (although it may block the 
antenna in the direction of the building).  A long wire launched away from the 
building is best -- small diameter enameled wire can be hard to see, and works 
fine as an antenna.

73, Jim K9YC

On Thu,4/7/2016 2:41 AM, Petr, OK1RP/M0SIS wrote:

I am sure that David talked about an Isotron antennas like this:
https://www.isotronantennas.com/

I intensively tested/used this antenna in 90's on 40m (product from Sigi,
DK9FN) and I have to say it is a nightmare in overall. From my own
experiences the performance of this toy was highly dependent to the
grounding availability, bandwidth was very small and tunning was influenced
by ground only but also by closed objects a lot.

__
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 k0...@aol.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 wun...@wunderwood.org

__
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 k0...@aol.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 arch...@mail-archive.com

Re: [Elecraft] [K3] Setting RF gain & AGC correctly

[lstavenhagen]

Agree, even I figured out how to twiddle the AGC settings once I found them.
They're not hard to find, just scroll until you see something that starts
with "AGC..." hi hi. If I can do it, anyone can.

As for the defaults, IMO, the K3/K3S AGC is plenty good enough to live with
them for quite a while even if you _don't_ manage to find the configuration
settings somehow. In fact, about all you'll notice is a slightly strange
occasional "pumping" action on AGC - S on CW sigs with a lot of QSB, which
may or may not make you scratch your head and send you to the manual.

On voice it might be a little fatiguing on AGC - F after a while; again that
may send you to the manual to look for settings or it may not. 

As for not sounding like your favorite other rig, you say that like it's a
bad thing hi hi. I'd rather not hear the squeal of the tuner-upper 1kc away
blowing through the filters at all, no matter how nice the audio of it may
be. That's what I get with my K's regardless of any other issues my hearing
may have

73,
LS
W5QD




--
View this message in context: 
http://elecraft.365791.n2.nabble.com/APF-audio-peaking-filter-on-the-K3-K3S-KX3-tp7613416p7616119.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: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

Re: [Elecraft] [K3] Setting RF gain & AGC correctly

[Kevin Stover]

I totally understand what your talking about but you have to be aware of 
the fur ball that happened on this list when the K3 was introduced.


"It doesn't sound like my (insert favorite Japanese Radio here)". There 
were people running around on different message boards claiming the K3's 
audio was terrible, even though it was configurable with said AGC 
settings and probably the best receiver any of them had ever heard. So 
what is a company to do, make the radio "sound better" out of the box or 
let the nattering nabobs of negativism continue to slander the rig?


They made the necessary anti-mush firmware changes and left the default 
alone. Pretty good middle of the road solution. DXer's and contestors 
are supposed to be our best and brightest, not counting some recent high 
profile DXpeditions (that's another thread), but can't keep on top of 
firmware changes and experiment with AGC settings?


We haven't ALL become appliance operators needing our hands held have we?

I'll bet the 4.51 changes were all over contesting.com within 10 minutes 
of being released. The changes were discussed on this list until the 
horse resembled glue. Claiming nobody knows/knew about them is silly.


On 4/9/2016 2:44 AM, Ian White wrote:

To clarify what Don and Al have said, I don't take any position in the
"Bad Audio" discussion. I doubt if any of us truly understands what the
other guy means by "bad audio" anyway.

My comments were specifically about the so-called "pileup mush" that
results from the poorly chosen default AGC settings; and also about the
lack of follow-through from Elecraft on this topic.

[What follows is a re-post of my earlier message referenced by Al (with
minor edits). For clarity, I don't have any disagreement with the views
of Don, Al or Barry N1EU.

I'm out the door now for the GM DX Convention, so I won't be able to
enter into detailed discussions for the next few days.]

***

The factory default AGC THReshold for the K3 and K3S is very, very low.
Measurements by KE7X [1] have shown that the default setting of THR=5
corresponds to an AGC onset at less than S3, whereas competing rigs have
a threshold of S7 or even higher. This very low AGC threshold is what
allows the AGC to be activated by band noise.

Elecraft's factory defaults of THR=5 and SLP=12 compress all signals
above the AGC threshold into a very narrow range of audio output levels
[see the measurements by KE7X]. This makes for comfortable
broadcast-style listening - but there is price to be paid. The default
settings greatly reduce the differences in the real-life strengths of
incoming signals - important differences that DXers and contesters
*need* to hear, in order to pick individual signals out of a pileup.

Following complaints from DXers, DXpeditioners and contesters about this
so-called "pileup mush", and following further series of measurements by
KE7X, Elecraft eventually did increase the available range of AGC
THReshold settings (the v4.51 firmware upgrade).

Following the release of FW v4.51, the consensus within the
[K3-contesting] Yahoo group about the most important settings for DXing
and contesting has been as follows.

* AGC THR: increase to at least 8 (from default = 5) and preferably to
12, and then take some time to become re-accustomed to the increased
range of audio levels [2]. (Some users recommend as high as 14, if your
ears can handle it.)

* AGC SLP: decrease to 8 or even less (from default = 12). Lower SLP
settings allow stronger signals to sound somewhat louder, and thus more
realistic, but the range of variation will be partly determined by the
THR setting already made; so always experiment with THR first, and with
SLP afterwards.

* AGC DCY = SOFT (not default=NOR). The User Manual claims that "The
SOFT setting can reduce IMD caused by traditional AGC, and is especially
useful in 'pileup' conditions, in some cases making it unnecessary to
turn AGC off."

The settings recommended above have essentially solved the problem of
"pileup mush" for those who have tried them... but regrettably, Elecraft
has done almost nothing to make DXers and contesters  aware that such
changes are possible.

More than 3 years after the firmware release notes boasted that v4.51
"greatly improves signal clarity in pile-ups and other high-noise or
dense-signal situations, especially with threshold set to 12 or higher",
that information is *still* missing from the User Manual. There is also
no information on how to create different 'profiles' of AGC settings for
different types of users.

Meanwhile, Elecraft's factory AGC defaults remain exactly as they were,
still optimized apparently for comfortable 'listening', while many DXers
and contesters remain unaware that their K3/K3S could actually be *so*
much better.



[1] http://www.ke7x.com/home/miscellaneous-k3-information

[2] It is important to give any increased AGC THReshold setting an
extended trial. To anyone accustomed to an artificially restricted range
of 

Re: [Elecraft] [K3] Setting RF gain & AGC correctly

[lstavenhagen]

So... Elecraft almost completely rewrites the AGC support in their
firmware... and that's a lack of follow-through? lots of hi hi's and smileys
here.. 

but seriously, I totally agree that the wrong AGC settings can make the APF
almost unusable. I personally have found that it works the best with the AGC
simply turned off. The cost is having to "ride" the volume control a little
bit in the QSB, but it becomes a razor blade without the AGC enabled at all
on a weak sig.

As for the AGC settings, after experimentation I've ended up with both SLP
and THR set to 10 on my K3 and K3S. That gives the best balance for my ears
between compression and "pumping" kinds of effects on fast AGC. YMMV.

As for "noisy K3", I'm not sure what that refers to. I've complained about
the quality of the audio, essentially the freq. response, in the past but
the K3 RX is probably the quietest on the market. Mine and my K3S both are
virtually silent out on my /p ops, out where I'm far away from man-made
industrial noise sources. Even before I upgraded the synthesizer, the K3 was
one of the quietest RX's I've ever used.

73,
LS
W5QD

gm3sek wrote
> To clarify what Don and Al have said, I don't take any position in the
> "Bad Audio" discussion. I doubt if any of us truly understands what the
> other guy means by "bad audio" anyway.
> 
> My comments were specifically about the so-called "pileup mush" that
> results from the poorly chosen default AGC settings; and also about the
> lack of follow-through from Elecraft on this topic.
> 
> [What follows is a re-post of my earlier message referenced by Al (with
> minor edits). For clarity, I don't have any disagreement with the views
> of Don, Al or Barry N1EU.
> 
> I'm out the door now for the GM DX Convention, so I won't be able to
> enter into detailed discussions for the next few days.]
> 
> ***
> 
> The factory default AGC THReshold for the K3 and K3S is very, very low.
> Measurements by KE7X [1] have shown that the default setting of THR=5
> corresponds to an AGC onset at less than S3, whereas competing rigs have
> a threshold of S7 or even higher. This very low AGC threshold is what
> allows the AGC to be activated by band noise.
> 
> Elecraft's factory defaults of THR=5 and SLP=12 compress all signals
> above the AGC threshold into a very narrow range of audio output levels
> [see the measurements by KE7X]. This makes for comfortable
> broadcast-style listening - but there is price to be paid. The default
> settings greatly reduce the differences in the real-life strengths of
> incoming signals - important differences that DXers and contesters
> *need* to hear, in order to pick individual signals out of a pileup.
> 
> Following complaints from DXers, DXpeditioners and contesters about this
> so-called "pileup mush", and following further series of measurements by
> KE7X, Elecraft eventually did increase the available range of AGC
> THReshold settings (the v4.51 firmware upgrade). 
> 
> Following the release of FW v4.51, the consensus within the
> [K3-contesting] Yahoo group about the most important settings for DXing
> and contesting has been as follows. 
> 
> * AGC THR: increase to at least 8 (from default = 5) and preferably to
> 12, and then take some time to become re-accustomed to the increased
> range of audio levels [2]. (Some users recommend as high as 14, if your
> ears can handle it.)
> 
> * AGC SLP: decrease to 8 or even less (from default = 12). Lower SLP
> settings allow stronger signals to sound somewhat louder, and thus more
> realistic, but the range of variation will be partly determined by the
> THR setting already made; so always experiment with THR first, and with
> SLP afterwards. 
> 
> * AGC DCY = SOFT (not default=NOR). The User Manual claims that "The
> SOFT setting can reduce IMD caused by traditional AGC, and is especially
> useful in 'pileup' conditions, in some cases making it unnecessary to
> turn AGC off."
>  
> The settings recommended above have essentially solved the problem of
> "pileup mush" for those who have tried them... but regrettably, Elecraft
> has done almost nothing to make DXers and contesters  aware that such
> changes are possible. 
>  
> More than 3 years after the firmware release notes boasted that v4.51
> "greatly improves signal clarity in pile-ups and other high-noise or
> dense-signal situations, especially with threshold set to 12 or higher",
> that information is *still* missing from the User Manual. There is also
> no information on how to create different 'profiles' of AGC settings for
> different types of users.
> 
> Meanwhile, Elecraft's factory AGC defaults remain exactly as they were,
> still optimized apparently for comfortable 'listening', while many DXers
> and contesters remain unaware that their K3/K3S could actually be *so*
> much better. 
> 
> 
> 
> [1] http://www.ke7x.com/home/miscellaneous-k3-information
> 
> [2] It is important to give any increased AGC THReshold setting an
> extended trial. To 

Re: [Elecraft] New KX3 S/N 8769 with a question

[Ken G Kopp]

Phil,

I used the tip of a drill bit the same size as the screw heads and -gently-
turned it with my fingers to countersink the holes in the battery holder.
Use caution, as a sharp bit can bite into the plastic and end up going all
the way through.

73

Ken Kopp - K0PP
On Apr 9, 2016 06:06, "Phillip Zminda"  wrote:

> I just completed the build on my new KX3 last night and have it up and
> running but ran into one problem with the build. My kit had the errata
> sheet with the change in screw length to 2-56 X 1/4 in long for the battery
> holders. I could not get the screws started on both ends of either battery
> holder. If I got one screw in, the other end was raised up and the other
> screw didn’t seem to go through far enough to get the threads started.
> After struggling for a while I ended up using one of the 9/32 in screws and
> on one of them and a pan-head screw on the other end of each battery
> holder. This was just to get the rig completed and tested. I do want to
> eventually use batteries on occasion so I do need to fix this. I can see
> where the screw heads sticking up can be a risk.
>
> I am looking for help on getting the battery holders mounted correctly
> with the screw heads seated into the plastic.
>
> Loving the rig, made my 1st QSO with it last night and hoping for some
> time with it this weekend.
>
> Thanks,
>
> Phil N3ZP
>
> __
> 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 kengk...@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 arch...@mail-archive.com

Re: [Elecraft] S: Re: Elecraft Utilities

[Kevin Stover]

Well
Elecraft have decided to do neither for the time being so

On 4/9/2016 3:20 AM, Andy McMullin wrote:

Don,

Just to clarify. The Raspberry Pi uses a range of completely standard Linux 
operating systems EXCEPT that it does not use the X86 range of processors. It 
uses the ARM range instead. It does not need to “emulate” Linux in all aspects 
— it IS Linux in all aspects. Applications that are correctly compiled work 
just like those for other Linux systems. For example, the standard FLDIGI 
source for Linux just recompiles under Linux on the Raspberry Pi and then works.

The designers of the Raspberry Pi are unlikely to rework their hardware to use 
a different processor — especially when the ARM one powers so many smartphones 
and other modern devices and the X86 one is hamstrung by needing to retain 
backwards compatibility with a design from over 30 years ago.

On the other hand, for the Elecraft Utilities to work on the Pi, all that would 
be required would be to compile the Linux source BUT for the ARM processor 
rather than the X86. Either Elecraft could do it or, as was suggested, they 
could release the source and (almost) anyone could do it.

—
Regards
Andy, G8TQH



On 8 Apr 2016, at 23:32, Don Wilhelm  wrote:

To ask Elecraft to provide Utilities for any and all small operating systems is 
unreasonable IMHO.  The mainstream OS of Windows, Mac and Linux *are* 
supported, but recently there have been a number of OS variants that have 
appeared on the horizon (and there are likely to be more to come) and that 
includes the Rasberry Pi, and several other 'computers' that have recently 
appeared on the hobbyist market.

Just because the most recent device can do RS-232 (or USB) communications does not mean 
it should be individually supported by hardware manufacturers.  It would be more 
productive to encourage those writing software for those devices to request that they 
emulate Windows, or Mac, or Linux in all aspects so one could use the applications 
written for those mainstream OS versions to run without problems on whichever platform 
those "hobby" devices may be using.

If the Rasberry Pi OS becomes stable over time, and is in use for a significant 
percentage of the Elecraft community, then it may eventually be supported on 
its own,  but for the time being, as I understand the Raspberry Pi, its OS is a 
version of Linux, but not everything works like the main Linux platform -- so 
until you can convince the Raspberry Pi developers to create a version of its 
OS that is compatible in all respects to Linux, you will not have success.  The 
market penetration for Raspberry Pi is just not great enough at this time for 
manufacturers to create software that will run on it.  Much to the dismay of 
those who have Raspberry Pi running and controlling their ham stations.

73,
Don W3FPR


__
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 kevin.sto...@mediacombb.net



--
R. Kevin Stover
AC0H
ARRL
FISTS #11993
SKCC #215
NAQCC #3441


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

__
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

Re: [Elecraft] Elecraft Utilities

[Bill]

This goes back to the unbeatable product support we get from Elecraft. I 
can honestly say that had I not received some really great support from 
the "home office" - I would not be the happy K-Line owner that I am 
today. That level of support is not available from any other ham radio 
manufacturer.


Bill W2BLC K-Line
__
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

Re: [Elecraft] K3 front panel switches

[Mike Reublin NF4L]

Fred,
Give the techs at Elecraft a call. They're REAL good at diagnosing problems, 
and suggesting fixes. If you don't feel comfortable doing the work, send it in.
73, Mike NF4L

> On Apr 8, 2016, at 6:44 PM, Fred Jensen  wrote:
> 
> My K3, S/N 642, has been slowly developing "front panel dementia" [as am I as 
> I accumulate birthdays].  A number of the switches are becoming intermittent, 
> and often, the first push of one causes a totally unrelated action [e.g. 
> tapping BAND UP turns on NR].  It doesn't happen with all of them and it 
> seems like the ones I use the most are pretty stable.  I find that a really 
> positive actuation, as in hard, often makes it work correctly.
> 
> My K3 is getting somewhat long in the tooth as the S/N would indicate, but I 
> was under the impression that the front panel switches were rated at 
> multi-millions of operations, and I'm sure I haven't come remotely close to 
> exceeding that.  My truck is 13 years old and is developing similar symptoms 
> [Tach says the engine is doing 6,000 RPM sitting in the driveway :-)]
> 
> Curious:
> 
> 1.  Anybody else experience this?
> 
> 2.  If so, what did you do?
> 
> 3.  How do I tell if it's time to send it into the Big E?
> 
> 73,
> 
> Fred K6DGW
> - Northern California Contest Club
> - CU in the Cal QSO Party 1-2 Oct 2016
> - www.cqp.org
> __
> 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 n...@comcast.net



73, Mike NF4L


__
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

[Elecraft] New KX3 S/N 8769 with a question

[Phillip Zminda]

I just completed the build on my new KX3 last night and have it up and running 
but ran into one problem with the build. My kit had the errata sheet with the 
change in screw length to 2-56 X 1/4 in long for the battery holders. I could 
not get the screws started on both ends of either battery holder. If I got one 
screw in, the other end was raised up and the other screw didn’t seem to go 
through far enough to get the threads started. After struggling for a while I 
ended up using one of the 9/32 in screws and on one of them and a pan-head 
screw on the other end of each battery holder. This was just to get the rig 
completed and tested. I do want to eventually use batteries on occasion so I do 
need to fix this. I can see where the screw heads sticking up can be a risk.

I am looking for help on getting the battery holders mounted correctly with the 
screw heads seated into the plastic.

Loving the rig, made my 1st QSO with it last night and hoping for some time 
with it this weekend.

Thanks,

Phil N3ZP

__
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

Re: [Elecraft] Elecraft Utilities

[Vic Rosenthal 4X6GP/K2VCO]

Reading this thread, I wonder how many actually do recognize this!

I was a field tester for the K3 and therefore also for the K3 utility.
I'm a retired software developer, and I had great respect for the 
developer of the K3 utility as I watched him great pains to develop a 
robust program with the ability to recover from almost anything that 
flaky serial and serial/usb connections could throw at it. Nobody wants 
to brick your K3/KX3, least of all Elecraft!


Remember, software is a cost center for them, not a profit center. And 
so is support. Do you think they want to take calls of the form "I built 
my firmware loader following the specifications to a T (except...) and 
now my K3 has become unresponsive?"


In my opinion Elecraft went over and above by providing versions for 
Windows, 32-bit Linux and Mac OS. Some manufacturers would give you 
Windows only, and it would be full of bugs, too!


73,
Vic, 4X6GP/K2VCO
Rehovot, Israel
http://www.qsl.net/k2vco/

On 8 Apr 2016 23:24, Jessie Oberreuter wrote:

Fortunately, we recognize that Elecraft is a /radio/ company, /not/ a
consumer software company, and we don't want to ask them to spend time
supporting dozens of firmware loaders.  Ideally, we would like to see
or, with access to the protocol documentation, develop an open-source
library for updating the firmware. Then we can build our own firmware
loaders for whatever platforms we choose.

__
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

Re: [Elecraft] S: Re: Elecraft Utilities

[Andy McMullin]

Don,

Just to clarify. The Raspberry Pi uses a range of completely standard Linux 
operating systems EXCEPT that it does not use the X86 range of processors. It 
uses the ARM range instead. It does not need to “emulate” Linux in all aspects 
— it IS Linux in all aspects. Applications that are correctly compiled work 
just like those for other Linux systems. For example, the standard FLDIGI 
source for Linux just recompiles under Linux on the Raspberry Pi and then works.

The designers of the Raspberry Pi are unlikely to rework their hardware to use 
a different processor — especially when the ARM one powers so many smartphones 
and other modern devices and the X86 one is hamstrung by needing to retain 
backwards compatibility with a design from over 30 years ago. 

On the other hand, for the Elecraft Utilities to work on the Pi, all that would 
be required would be to compile the Linux source BUT for the ARM processor 
rather than the X86. Either Elecraft could do it or, as was suggested, they 
could release the source and (almost) anyone could do it.

— 
Regards
Andy, G8TQH


> On 8 Apr 2016, at 23:32, Don Wilhelm  wrote:
> 
> To ask Elecraft to provide Utilities for any and all small operating systems 
> is unreasonable IMHO.  The mainstream OS of Windows, Mac and Linux *are* 
> supported, but recently there have been a number of OS variants that have 
> appeared on the horizon (and there are likely to be more to come) and that 
> includes the Rasberry Pi, and several other 'computers' that have recently 
> appeared on the hobbyist market.
> 
> Just because the most recent device can do RS-232 (or USB) communications 
> does not mean it should be individually supported by hardware manufacturers.  
> It would be more productive to encourage those writing software for those 
> devices to request that they emulate Windows, or Mac, or Linux in all aspects 
> so one could use the applications written for those mainstream OS versions to 
> run without problems on whichever platform those "hobby" devices may be using.
> 
> If the Rasberry Pi OS becomes stable over time, and is in use for a 
> significant percentage of the Elecraft community, then it may eventually be 
> supported on its own,  but for the time being, as I understand the Raspberry 
> Pi, its OS is a version of Linux, but not everything works like the main 
> Linux platform -- so until you can convince the Raspberry Pi developers to 
> create a version of its OS that is compatible in all respects to Linux, you 
> will not have success.  The market penetration for Raspberry Pi is just not 
> great enough at this time for manufacturers to create software that will run 
> on it.  Much to the dismay of those who have Raspberry Pi running and 
> controlling their ham stations.
> 
> 73,
> Don W3FPR


__
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

Re: [Elecraft] [K3] Setting RF gain & AGC correctly

[Ian White]

To clarify what Don and Al have said, I don't take any position in the
"Bad Audio" discussion. I doubt if any of us truly understands what the
other guy means by "bad audio" anyway.

My comments were specifically about the so-called "pileup mush" that
results from the poorly chosen default AGC settings; and also about the
lack of follow-through from Elecraft on this topic.

[What follows is a re-post of my earlier message referenced by Al (with
minor edits). For clarity, I don't have any disagreement with the views
of Don, Al or Barry N1EU.

I'm out the door now for the GM DX Convention, so I won't be able to
enter into detailed discussions for the next few days.]

***

The factory default AGC THReshold for the K3 and K3S is very, very low.
Measurements by KE7X [1] have shown that the default setting of THR=5
corresponds to an AGC onset at less than S3, whereas competing rigs have
a threshold of S7 or even higher. This very low AGC threshold is what
allows the AGC to be activated by band noise.

Elecraft's factory defaults of THR=5 and SLP=12 compress all signals
above the AGC threshold into a very narrow range of audio output levels
[see the measurements by KE7X]. This makes for comfortable
broadcast-style listening - but there is price to be paid. The default
settings greatly reduce the differences in the real-life strengths of
incoming signals - important differences that DXers and contesters
*need* to hear, in order to pick individual signals out of a pileup.

Following complaints from DXers, DXpeditioners and contesters about this
so-called "pileup mush", and following further series of measurements by
KE7X, Elecraft eventually did increase the available range of AGC
THReshold settings (the v4.51 firmware upgrade). 

Following the release of FW v4.51, the consensus within the
[K3-contesting] Yahoo group about the most important settings for DXing
and contesting has been as follows. 

* AGC THR: increase to at least 8 (from default = 5) and preferably to
12, and then take some time to become re-accustomed to the increased
range of audio levels [2]. (Some users recommend as high as 14, if your
ears can handle it.)

* AGC SLP: decrease to 8 or even less (from default = 12). Lower SLP
settings allow stronger signals to sound somewhat louder, and thus more
realistic, but the range of variation will be partly determined by the
THR setting already made; so always experiment with THR first, and with
SLP afterwards. 

* AGC DCY = SOFT (not default=NOR). The User Manual claims that "The
SOFT setting can reduce IMD caused by traditional AGC, and is especially
useful in 'pileup' conditions, in some cases making it unnecessary to
turn AGC off."
 
The settings recommended above have essentially solved the problem of
"pileup mush" for those who have tried them... but regrettably, Elecraft
has done almost nothing to make DXers and contesters  aware that such
changes are possible. 
 
More than 3 years after the firmware release notes boasted that v4.51
"greatly improves signal clarity in pile-ups and other high-noise or
dense-signal situations, especially with threshold set to 12 or higher",
that information is *still* missing from the User Manual. There is also
no information on how to create different 'profiles' of AGC settings for
different types of users.

Meanwhile, Elecraft's factory AGC defaults remain exactly as they were,
still optimized apparently for comfortable 'listening', while many DXers
and contesters remain unaware that their K3/K3S could actually be *so*
much better. 



[1] http://www.ke7x.com/home/miscellaneous-k3-information

[2] It is important to give any increased AGC THReshold setting an
extended trial. To anyone accustomed to an artificially restricted range
of audio signal levels, a higher setting will initially sound quite
'aggressive' - even though the new setting is much closer to real life. 



73 from Ian GM3SEK




73 from Ian GM3SEK


>-Original Message-
>From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of
>Don Wilhelm
>Sent: 09 April 2016 01:30
>To: elecraft@mailman.qth.net
>Subject: Re: [Elecraft] [K3] Setting RF gain & AGC correctly
>
>The K3/K3S AGC settings have a lot to do with the apparent "noisy K3"
>syndrome.
>IMHO, the K3 default AGC settings are not optimum.
>Look at my website www,w3fpr.com for information on how to customize
>your K3/K3S/KX3 AGC settings to optimum for your ambient noise and
>operating preferences.  You will find a 'different receiver' when you
>adjust the AGC parameters.
>
>Pay particular attention to the method of evaluating the results. You
>must do the evaluation on pauses in the SSB communications or
>word/sentence breaks in CW.  If you try to evaluate based on band noise
>alone, you will end up adjusting the parameters "backwards", and the
>result will be worse than when you started.
>
>73,
>Don W3FPR
>
>On 4/8/2016 8:04 PM, Al Lorona wrote:
>> Again and again, I have asked (privately) those