1. Elecraft-K3@groups.io
  2. Messages
   Date   
K5P Palmyra Isl DXpedition on the air with Elecraft rigs

Eric Swartz - WA6HHQ, Elecraft
 

K5P  Palmyra Island is on the air with with K3S transceivers, P3s and KPA500s. See:  http://www.dxsummit.fi/#/?dx_calls=K5P  and http://palmyra2016.org

Pic of K5P op positions in action at:
http://elecraft.com/DXpeditions/kp5ops.jpg

73,

Eric
elecraft.com
Re: K3 Remote No SSB output Power

Frank Davis
 

I discovered that CODEC INPUT ATTENTUATION parameter was set to YES in the Remote box.  How it got set to YES is unknown to me.  This didn't look right to me.... so I set it to NO  and also set the default values for CODEC OUTPUT GAIN and CODEC INPUT GAIN in both boxes.  I re- adjusted CODEC INPUT GAIN in the CONTROL box to 40 and may reduce it further upon more monitoring.

I now have SSB audio working again using both headsets...the Heil and the CM-500.!   The problem was the CODEC INPUT ATTENTUATION was turned on....I don't know how it got turned on or when.

I feel like a clutzh not having noticed this before.  I guess its an issue of understanding what all these settings are actually for.   It would have been helpful if there was a reference table listing out what the various settings are addressing.

Now that SSB is working and there is nothing wrong with the headsets I experimented with turing the BIAS OFF and then ON in the MAIN:MIC SEL rP.H  BIAS parameter in the K3 Mini.  Both headsets work whether BIAS is ON or OFF !...there is no change whatsoever!.  This is telling me that if both mikes require bias in order to work then the function of taping "2" on the K3 is not actually turning BIAS OFF....it is merely changing the display. Maybe this is something for Elecraft to address

I am very happy the issue is solved with help and comments from a number of people .  Your thoughs helped me correct the issue.

73 Frank VO1HP
Re: K3 Remote No SSB output Power

Frank Davis
 

OK JOhn

Many tnx for your two replies.   Your note got me to thinking about settings again in both RR boxes.

I discovered that CODEC INPUT ATTENTUATION parameter was set to YES in the Remote box.  How it got set to YES is unknown to me.  This didn't look right to me.... I set it to NO  and also set the default values for CODEC OUTPUT and CODEC INPUT GAIN in both boxes.  I adjusted CODEC INPUT GAIN in the CONTROL box to 40.  I now have SSB audio working again using both headsets...the Heil and the CM-500.!   The problem was the CODEN INPUT ATTENTUATION was turned on....I don't know how it got turned on or when.

I feel like a clutzh not having noticed this before.  I guess its an issue of understanding what all these settings are actually for.   It would have been helpful if there was a reference table listing out what the various settings are addressing.

Anyway thanks for your help and interest in replying to my post.  Your thoughs helped me correct the issue.

73 Frank VO1HP
Re: [Elecraft_K3] CW Losing first dit

Mike Heideman
 

 Hi Steve,
 
Since you're set up for SO2R you could try listening on the second or a higher harmonic of your signal on the other radio.
 
I happened to tune across my second harmonic during NAQP CW and noticed that one of the K3s was chopping off the beginnings of all the dits and dahs, making for very poorly weighted CW.  I made the TX Delay setting consistent with the other K3 which corrected the problem so that both K3s sounded good with the CW weight I'd set in the Winkeyer settings of the SO2R box.
 
73,
-Mike, N7MH
 
To: Elecraft_K3@...
From: Elecraft_K3@...
Date: Thu, 14 Jan 2016 07:47:33 -0900
Subject: RE: [Elecraft_K3] CW Losing first dit

 

Hi Victor:

 

I haven’t been able to isolate it yet ..since we had radio silence type propagation here yesterday …and I wasn’t available in the evening when I perhaps could have found someone locally.

 

73

Steve KL7SB

 
Re: [Elecraft_K3] CW Losing first dit

Stephen Bloom
 

Hi Jim:

 

VOX is already on.

 

Thanks/73

Steve KL7SB

 

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 4:13 PM
To: Elecraft_K3@...
Subject: Re: [Elecraft_K3] CW Losing first dit

 

 

Turn VOX on.  For some reason, not sure why, this cured my exact same problem using an external Winkeyer on the K3.  You don’t notice the lost first character on the cw monitor but is very apparent on a second receiver..  73s Jim K4JAF

 

Sent: Wednesday, January 13, 2016 7:02 PM

Subject: [Elecraft_K3] CW Losing first dit

 

 

Hey all:

Slight mystery here.  Was doing the CWOps CWT this morning ..and noticed that a number of ops were getting me as “UL7SB” rather than KL7SB ..which was followed by someone telling me directly that I was losing the first dit …first time having this problem that I am aware of ..speed varied from 28wpm to 34wpm ..didn’t seem to matter.

No immediately apparent reason why …

Configuration is K3 (with new the new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM  …the K3 TX Delay is ..and always has been the default of 8ms, the TX Lead time in N1MM (Winkey config tab) is 1 (meaning 10msec). operating semi break-in

Any thoughts?  No real way to test at the moment ..the lost dit isn’t noticeable using the tx mon.

73

Steve KL7SB
Re: [Elecraft_K3] CW Losing first dit

Stephen Bloom
 

Hi Victor:

 

I haven’t been able to isolate it yet ..since we had radio silence type propagation here yesterday …and I wasn’t available in the evening when I perhaps could have found someone locally.

 

73

Steve KL7SB

 

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 9:59 PM
To: Elecraft_K3@...
Subject: Re: [Elecraft_K3] CW Losing first dit

 

 

Hi Steve,
Does this phenomena appears when keying K3 barefoot or only when the linear is keyed as well?t

73, Victor Goncharsky US5WE/K1WE (UW5W in VHF contests), P.E.
UARL Technical and VHF Committies
DXCC Honor Roll #1 (Mixed, Phone)
DXCC card checker (160 meters).

--------------------------------------------
On Thu, 1/14/16, 'Stephen Bloom' sbloom@... [Elecraft_K3] <Elecraft_K3@...> wrote:

Subject: [Elecraft_K3] CW Losing first dit
To: Elecraft_K3@...
Date: Thursday, January 14, 2016, 3:02 AM

Hey all:  Slight mystery here.  Was doing
the CWOps CWT this morning ..and noticed that a number of
ops were getting me as “UL7SB” rather than KL7SB ..which
was followed by someone telling me directly that I was
losing the first dit …first time having this problem that
I am aware of ..speed varied from 28wpm to 34wpm ..didn’t
seem to matter.  No immediately apparent reason why
…  Configuration is K3 (with new the
new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM 
…the K3 TX Delay is ..and always has been the default of
8ms, the TX Lead time in N1MM (Winkey config tab) is 1
(meaning 10msec). operating semi break-in  Any thoughts?  No real way to
test at the moment ..the lost dit isn’t noticeable using
the tx mon.  73Steve KL7SB  









#yiv5865472783 #yiv5865472783 --
#yiv5865472783ygrp-mkp {
border:1px solid #d8d8d8;font-family:Arial;margin:10px
0;padding:0 10px;}

#yiv5865472783 #yiv5865472783ygrp-mkp hr {
border:1px solid #d8d8d8;}

#yiv5865472783 #yiv5865472783ygrp-mkp #yiv5865472783hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px
0;}

#yiv5865472783 #yiv5865472783ygrp-mkp #yiv5865472783ads {
margin-bottom:10px;}

#yiv5865472783 #yiv5865472783ygrp-mkp .yiv5865472783ad {
padding:0 0;}

#yiv5865472783 #yiv5865472783ygrp-mkp .yiv5865472783ad p {
margin:0;}

#yiv5865472783 #yiv5865472783ygrp-mkp .yiv5865472783ad a {
color:#0000ff;text-decoration:none;}
#yiv5865472783 #yiv5865472783ygrp-sponsor
#yiv5865472783ygrp-lc {
font-family:Arial;}

#yiv5865472783 #yiv5865472783ygrp-sponsor
#yiv5865472783ygrp-lc #yiv5865472783hd {
margin:10px
0px;font-weight:700;font-size:78%;line-height:122%;}

#yiv5865472783 #yiv5865472783ygrp-sponsor
#yiv5865472783ygrp-lc .yiv5865472783ad {
margin-bottom:10px;padding:0 0;}

#yiv5865472783 #yiv5865472783actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#yiv5865472783 #yiv5865472783activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#yiv5865472783 #yiv5865472783activity span {
font-weight:700;}

#yiv5865472783 #yiv5865472783activity span:first-child {
text-transform:uppercase;}

#yiv5865472783 #yiv5865472783activity span a {
color:#5085b6;text-decoration:none;}

#yiv5865472783 #yiv5865472783activity span span {
color:#ff7900;}

#yiv5865472783 #yiv5865472783activity span
.yiv5865472783underline {
text-decoration:underline;}

#yiv5865472783 .yiv5865472783attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px
0;width:400px;}

#yiv5865472783 .yiv5865472783attach div a {
text-decoration:none;}

#yiv5865472783 .yiv5865472783attach img {
border:none;padding-right:5px;}

#yiv5865472783 .yiv5865472783attach label {
display:block;margin-bottom:5px;}

#yiv5865472783 .yiv5865472783attach label a {
text-decoration:none;}

#yiv5865472783 blockquote {
margin:0 0 0 4px;}

#yiv5865472783 .yiv5865472783bold {
font-family:Arial;font-size:13px;font-weight:700;}

#yiv5865472783 .yiv5865472783bold a {
text-decoration:none;}

#yiv5865472783 dd.yiv5865472783last p a {
font-family:Verdana;font-weight:700;}

#yiv5865472783 dd.yiv5865472783last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#yiv5865472783 dd.yiv5865472783last p
span.yiv5865472783yshortcuts {
margin-right:0;}

#yiv5865472783 div.yiv5865472783attach-table div div a {
text-decoration:none;}

#yiv5865472783 div.yiv5865472783attach-table {
width:400px;}

#yiv5865472783 div.yiv5865472783file-title a, #yiv5865472783
div.yiv5865472783file-title a:active, #yiv5865472783
div.yiv5865472783file-title a:hover, #yiv5865472783
div.yiv5865472783file-title a:visited {
text-decoration:none;}

#yiv5865472783 div.yiv5865472783photo-title a,
#yiv5865472783 div.yiv5865472783photo-title a:active,
#yiv5865472783 div.yiv5865472783photo-title a:hover,
#yiv5865472783 div.yiv5865472783photo-title a:visited {
text-decoration:none;}

#yiv5865472783 div#yiv5865472783ygrp-mlmsg
#yiv5865472783ygrp-msg p a span.yiv5865472783yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#yiv5865472783 .yiv5865472783green {
color:#628c2a;}

#yiv5865472783 .yiv5865472783MsoNormal {
margin:0 0 0 0;}

#yiv5865472783 o {
font-size:0;}

#yiv5865472783 #yiv5865472783photos div {
float:left;width:72px;}

#yiv5865472783 #yiv5865472783photos div div {
border:1px solid
#666666;height:62px;overflow:hidden;width:62px;}

#yiv5865472783 #yiv5865472783photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#yiv5865472783 #yiv5865472783reco-category {
font-size:77%;}

#yiv5865472783 #yiv5865472783reco-desc {
font-size:77%;}

#yiv5865472783 .yiv5865472783replbq {
margin:4px;}

#yiv5865472783 #yiv5865472783ygrp-actbar div a:first-child {
margin-right:2px;padding-right:5px;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean,
sans-serif;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg table {
font-size:inherit;font:100%;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg select,
#yiv5865472783 input, #yiv5865472783 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg pre, #yiv5865472783
code {
font:115% monospace;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg * {
line-height:1.22em;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg #yiv5865472783logo {
padding-bottom:10px;}


#yiv5865472783 #yiv5865472783ygrp-msg p a {
font-family:Verdana;}

#yiv5865472783 #yiv5865472783ygrp-msg
p#yiv5865472783attach-count span {
color:#1E66AE;font-weight:700;}

#yiv5865472783 #yiv5865472783ygrp-reco
#yiv5865472783reco-head {
color:#ff7900;font-weight:700;}

#yiv5865472783 #yiv5865472783ygrp-reco {
margin-bottom:20px;padding:0px;}

#yiv5865472783 #yiv5865472783ygrp-sponsor #yiv5865472783ov
li a {
font-size:130%;text-decoration:none;}

#yiv5865472783 #yiv5865472783ygrp-sponsor #yiv5865472783ov
li {
font-size:77%;list-style-type:square;padding:6px 0;}

#yiv5865472783 #yiv5865472783ygrp-sponsor #yiv5865472783ov
ul {
margin:0;padding:0 0 0 8px;}

#yiv5865472783 #yiv5865472783ygrp-text {
font-family:Georgia;}

#yiv5865472783 #yiv5865472783ygrp-text p {
margin:0 0 1em 0;}

#yiv5865472783 #yiv5865472783ygrp-text tt {
font-size:120%;}

#yiv5865472783 #yiv5865472783ygrp-vital ul li:last-child {
border-right:none !important;
}
#yiv5865472783

Re: [Elecraft_K3] CW Losing first dit

Stephen Bloom
 

Hi Ian:

 

The thing that makes that seem unlikely is ..were that the case …it would only happen when I change frequency.  Easy enough to check ..I have the 2K-FA setup for SO2R ..so I can see if there is a similar problem with Radio 2 (TS590S, though I can also swap in another K3).

 

73

Steve

 

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 8:08 PM
To: Elecraft_K3@...
Subject: Re: [Elecraft_K3] CW Losing first dit

 

 

May be caused by the amp while it measures frequency and adjusts its ATU for the particular band segment. On my 1K-FA it would convert the first character of my callsign a G into a F. The solution was to stop using band data and make up the control cables so the amp reads the exact frequency of the radio when I QSY so the ATU in the amp is already set for the correct band segment before transmission starts. This avoids the need for the amp to adjust the ATU at the start of a transmission following a QSY and prevents it messing up the first character of  the callsign.

Ian Trusson


On 14 Jan 2016, at 02:43, Mike Flowers mike.flowers@... [Elecraft_K3] <Elecraft_K3@...> wrote:

 

Hi Steve,

 

At 28+ WPM, it's not going to take much of a delay introduced into the stack to cause a problem.   You'll likely not notice another 10ms. 

 

Another consideration is that any corrosion on a connector or less than ideal connection in the keying circuits could introduce an IR voltage drop that could result in delayed keying.   I've seen this as the cause of problems from time to time.   Easy to clean these up. 

-- Mike Flowers, K6MKF, NCDXC - "It's about DX!"


On Jan 13, 2016, at 5:49 PM, 'Stephen Bloom' sbloom@... [Elecraft_K3] <Elecraft_K3@...> wrote:

 

That makes sense …My guess is that  I can probably fix it by adding another 10msecs to the Tx Lead time in N1MM (or I could increase the Delay on the K3 ..but I’d realllly rather not do that), but I’d still like to know what changed.  One possibility is the T/R relay in the amp has gotten slightly slower, and what is happening is the amp isn’t kicking in ..in the 10msec ..no way to test it right now …current propagation here is pretty much radio silence.

 

73

Steve KL7SB

 

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 4:08 PM
To: Elecraft_K3@...
Subject: RE: [Elecraft_K3] CW Losing first dit

 

 

It appears to me that your first dash in K is being truncated into a dot, so the other stations are copying you as UL7SB – rather than losing the first dot.

 

And this sounds like a timing issue …

 

- 73 and good DX de Mike, K6MKF, President - NCDXC

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 5:03 PM
To: Elecraft_K3@...
Subject: [Elecraft_K3] CW Losing first dit

 

 

Hey all:

 

Slight mystery here.  Was doing the CWOps CWT this morning ..and noticed that a number of ops were getting me as “UL7SB” rather than KL7SB ..which was followed by someone telling me directly that I was losing the first dit …first time having this problem that I am aware of ..speed varied from 28wpm to 34wpm ..didn’t seem to matter.

 

No immediately apparent reason why …

 

Configuration is K3 (with new the new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM  …the K3 TX Delay is ..and always has been the default of 8ms, the TX Lead time in N1MM (Winkey config tab) is 1 (meaning 10msec). operating semi break-in

 

Any thoughts?  No real way to test at the moment ..the lost dit isn’t noticeable using the tx mon.

 

73

Steve KL7SB

 
Re: K3 Remote No SSB output Power

John K3TN
 

Frank, if the problem is that with the headset/mic plugged into the K3/Mini you find TX and RX audio to be way too low to be usable, I went through that - and even sent the Mini back to Elecraft. Unfortunately, their response was that is a feature of the K3 Mini.

They said the original Minis had problems with digital noise getting into the audio, so they put a big low pass filter in the audio circuit - which attenuates the audio. Their advice was to turn up the RX volume parameter in the local RRC to offset the loss in the Mini.

I'm not a big believer of amplifying, then attenuating - I wasn't wild about that answer, but that was the Elecraft recommendation to deal with the problem.

Try this and see if it solves the problem: Connect your headset to your Local RRC, vs. into the Mini. That solved my problem. This makes for less than elegant cabling, makes me wish again that I had bought a bare bones K3 vs. the Mini, but the audio is FB when you avoid going through the Mini.

73 John K3TN
Re: [Elecraft_K3] CW Losing first dit

Vic Goncharsky
 

Hi Steve,
Does this phenomena appears when keying K3 barefoot or only when the linear is keyed as well?t


73, Victor Goncharsky US5WE/K1WE (UW5W in VHF contests), P.E.
UARL Technical and VHF Committies
DXCC Honor Roll #1 (Mixed, Phone)
DXCC card checker (160 meters).


--------------------------------------------

On Thu, 1/14/16, 'Stephen Bloom' sbloom@acsalaska.net [Elecraft_K3] <Elecraft_K3@yahoogroups.com> wrote:


Subject: [Elecraft_K3] CW Losing first dit
To: Elecraft_K3@yahoogroups.com
Date: Thursday, January 14, 2016, 3:02 AM

Hey all:  Slight mystery here.  Was doing
the CWOps CWT this morning ..and noticed that a number of
ops were getting me as “UL7SB” rather than KL7SB ..which
was followed by someone telling me directly that I was
losing the first dit …first time having this problem that
I am aware of ..speed varied from 28wpm to 34wpm ..didn’t
seem to matter.  No immediately apparent reason why
…  Configuration is K3 (with new the
new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM 
…the K3 TX Delay is ..and always has been the default of
8ms, the TX Lead time in N1MM (Winkey config tab) is 1
(meaning 10msec). operating semi break-in  Any thoughts?  No real way to
test at the moment ..the lost dit isn’t noticeable using
the tx mon.  73Steve KL7SB  









#yiv5865472783 #yiv5865472783 --
#yiv5865472783ygrp-mkp {
border:1px solid #d8d8d8;font-family:Arial;margin:10px
0;padding:0 10px;}

#yiv5865472783 #yiv5865472783ygrp-mkp hr {
border:1px solid #d8d8d8;}

#yiv5865472783 #yiv5865472783ygrp-mkp #yiv5865472783hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px
0;}

#yiv5865472783 #yiv5865472783ygrp-mkp #yiv5865472783ads {
margin-bottom:10px;}

#yiv5865472783 #yiv5865472783ygrp-mkp .yiv5865472783ad {
padding:0 0;}

#yiv5865472783 #yiv5865472783ygrp-mkp .yiv5865472783ad p {
margin:0;}

#yiv5865472783 #yiv5865472783ygrp-mkp .yiv5865472783ad a {
color:#0000ff;text-decoration:none;}
#yiv5865472783 #yiv5865472783ygrp-sponsor
#yiv5865472783ygrp-lc {
font-family:Arial;}

#yiv5865472783 #yiv5865472783ygrp-sponsor
#yiv5865472783ygrp-lc #yiv5865472783hd {
margin:10px
0px;font-weight:700;font-size:78%;line-height:122%;}

#yiv5865472783 #yiv5865472783ygrp-sponsor
#yiv5865472783ygrp-lc .yiv5865472783ad {
margin-bottom:10px;padding:0 0;}

#yiv5865472783 #yiv5865472783actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#yiv5865472783 #yiv5865472783activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#yiv5865472783 #yiv5865472783activity span {
font-weight:700;}

#yiv5865472783 #yiv5865472783activity span:first-child {
text-transform:uppercase;}

#yiv5865472783 #yiv5865472783activity span a {
color:#5085b6;text-decoration:none;}

#yiv5865472783 #yiv5865472783activity span span {
color:#ff7900;}

#yiv5865472783 #yiv5865472783activity span
.yiv5865472783underline {
text-decoration:underline;}

#yiv5865472783 .yiv5865472783attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px
0;width:400px;}

#yiv5865472783 .yiv5865472783attach div a {
text-decoration:none;}

#yiv5865472783 .yiv5865472783attach img {
border:none;padding-right:5px;}

#yiv5865472783 .yiv5865472783attach label {
display:block;margin-bottom:5px;}

#yiv5865472783 .yiv5865472783attach label a {
text-decoration:none;}

#yiv5865472783 blockquote {
margin:0 0 0 4px;}

#yiv5865472783 .yiv5865472783bold {
font-family:Arial;font-size:13px;font-weight:700;}

#yiv5865472783 .yiv5865472783bold a {
text-decoration:none;}

#yiv5865472783 dd.yiv5865472783last p a {
font-family:Verdana;font-weight:700;}

#yiv5865472783 dd.yiv5865472783last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#yiv5865472783 dd.yiv5865472783last p
span.yiv5865472783yshortcuts {
margin-right:0;}

#yiv5865472783 div.yiv5865472783attach-table div div a {
text-decoration:none;}

#yiv5865472783 div.yiv5865472783attach-table {
width:400px;}

#yiv5865472783 div.yiv5865472783file-title a, #yiv5865472783
div.yiv5865472783file-title a:active, #yiv5865472783
div.yiv5865472783file-title a:hover, #yiv5865472783
div.yiv5865472783file-title a:visited {
text-decoration:none;}

#yiv5865472783 div.yiv5865472783photo-title a,
#yiv5865472783 div.yiv5865472783photo-title a:active,
#yiv5865472783 div.yiv5865472783photo-title a:hover,
#yiv5865472783 div.yiv5865472783photo-title a:visited {
text-decoration:none;}

#yiv5865472783 div#yiv5865472783ygrp-mlmsg
#yiv5865472783ygrp-msg p a span.yiv5865472783yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#yiv5865472783 .yiv5865472783green {
color:#628c2a;}

#yiv5865472783 .yiv5865472783MsoNormal {
margin:0 0 0 0;}

#yiv5865472783 o {
font-size:0;}

#yiv5865472783 #yiv5865472783photos div {
float:left;width:72px;}

#yiv5865472783 #yiv5865472783photos div div {
border:1px solid
#666666;height:62px;overflow:hidden;width:62px;}

#yiv5865472783 #yiv5865472783photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#yiv5865472783 #yiv5865472783reco-category {
font-size:77%;}


#yiv5865472783 #yiv5865472783reco-desc {
font-size:77%;}

#yiv5865472783 .yiv5865472783replbq {
margin:4px;}

#yiv5865472783 #yiv5865472783ygrp-actbar div a:first-child {
margin-right:2px;padding-right:5px;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean,
sans-serif;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg table {
font-size:inherit;font:100%;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg select,
#yiv5865472783 input, #yiv5865472783 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg pre, #yiv5865472783
code {
font:115% monospace;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg * {
line-height:1.22em;}

#yiv5865472783 #yiv5865472783ygrp-mlmsg #yiv5865472783logo {
padding-bottom:10px;}


#yiv5865472783 #yiv5865472783ygrp-msg p a {
font-family:Verdana;}

#yiv5865472783 #yiv5865472783ygrp-msg
p#yiv5865472783attach-count span {
color:#1E66AE;font-weight:700;}

#yiv5865472783 #yiv5865472783ygrp-reco
#yiv5865472783reco-head {
color:#ff7900;font-weight:700;}

#yiv5865472783 #yiv5865472783ygrp-reco {
margin-bottom:20px;padding:0px;}

#yiv5865472783 #yiv5865472783ygrp-sponsor #yiv5865472783ov
li a {
font-size:130%;text-decoration:none;}

#yiv5865472783 #yiv5865472783ygrp-sponsor #yiv5865472783ov
li {
font-size:77%;list-style-type:square;padding:6px 0;}

#yiv5865472783 #yiv5865472783ygrp-sponsor #yiv5865472783ov
ul {
margin:0;padding:0 0 0 8px;}

#yiv5865472783 #yiv5865472783ygrp-text {
font-family:Georgia;}

#yiv5865472783 #yiv5865472783ygrp-text p {
margin:0 0 1em 0;}

#yiv5865472783 #yiv5865472783ygrp-text tt {
font-size:120%;}

#yiv5865472783 #yiv5865472783ygrp-vital ul li:last-child {
border-right:none !important;
}
#yiv5865472783
Re: [Elecraft_K3] Re: K3 accessory connector

Ian White
 

Another alternative is to break out the 15-way cable to a piece of stripboard, allowing multiple connections to each of the 15 wires.

My K3 is raised above the desktop on a 1.5in deep base, which gives plenty of room for the breakout board inside and various patch connectors at the rear.


73 from Ian GM3SEK

-----Original Message-----
From: Elecraft_K3@yahoogroups.com
[mailto:Elecraft_K3@yahoogroups.com]
Sent: 13 January 2016 16:07
To: Elecraft_K3@yahoogroups.com
Subject: Re: [Elecraft_K3] Re: K3 accessory connector



Or do as I do and breakout the pins on DIN rail mounted boards and make
connections there. I hate a rats nest of Y connectors.

I use Winford Engineering products.

Just a happy customer.

73

Jim ab3cv
Re: [Elecraft_K3] CW Losing first dit

Ian G3RVM
 

May be caused by the amp while it measures frequency and adjusts its ATU for the particular band segment. On my 1K-FA it would convert the first character of my callsign a G into a F. The solution was to stop using band data and make up the control cables so the amp reads the exact frequency of the radio when I QSY so the ATU in the amp is already set for the correct band segment before transmission starts. This avoids the need for the amp to adjust the ATU at the start of a transmission following a QSY and prevents it messing up the first character of  the callsign.

Ian Trusson

On 14 Jan 2016, at 02:43, Mike Flowers mike.flowers@... [Elecraft_K3] <Elecraft_K3@...> wrote:

 

Hi Steve,

At 28+ WPM, it's not going to take much of a delay introduced into the stack to cause a problem.   You'll likely not notice another 10ms. 

Another consideration is that any corrosion on a connector or less than ideal connection in the keying circuits could introduce an IR voltage drop that could result in delayed keying.   I've seen this as the cause of problems from time to time.   Easy to clean these up. 

-- Mike Flowers, K6MKF, NCDXC - "It's about DX!"

On Jan 13, 2016, at 5:49 PM, 'Stephen Bloom' sbloom@... [Elecraft_K3] <Elecraft_K3@...> wrote:

 

That makes sense …My guess is that  I can probably fix it by adding another 10msecs to the Tx Lead time in N1MM (or I could increase the Delay on the K3 ..but I’d realllly rather not do that), but I’d still like to know what changed.  One possibility is the T/R relay in the amp has gotten slightly slower, and what is happening is the amp isn’t kicking in ..in the 10msec ..no way to test it right now …current propagation here is pretty much radio silence.

 

73

Steve KL7SB

 

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 4:08 PM
To: Elecraft_K3@...
Subject: RE: [Elecraft_K3] CW Losing first dit

 

 

It appears to me that your first dash in K is being truncated into a dot, so the other stations are copying you as UL7SB – rather than losing the first dot.

 

And this sounds like a timing issue …

 

- 73 and good DX de Mike, K6MKF, President - NCDXC

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 5:03 PM
To: Elecraft_K3@...
Subject: [Elecraft_K3] CW Losing first dit

 

 

Hey all:

 

Slight mystery here.  Was doing the CWOps CWT this morning ..and noticed that a number of ops were getting me as “UL7SB” rather than KL7SB ..which was followed by someone telling me directly that I was losing the first dit …first time having this problem that I am aware of ..speed varied from 28wpm to 34wpm ..didn’t seem to matter.

 

No immediately apparent reason why …

 

Configuration is K3 (with new the new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM  …the K3 TX Delay is ..and always has been the default of 8ms, the TX Lead time in N1MM (Winkey config tab) is 1 (meaning 10msec). operating semi break-in

 

Any thoughts?  No real way to test at the moment ..the lost dit isn’t noticeable using the tx mon.

 

73

Steve KL7SB

 
Re: [Elecraft_K3] CW Losing first dit

Mike Flowers
 

Hi Steve,

At 28+ WPM, it's not going to take much of a delay introduced into the stack to cause a problem.   You'll likely not notice another 10ms. 

Another consideration is that any corrosion on a connector or less than ideal connection in the keying circuits could introduce an IR voltage drop that could result in delayed keying.   I've seen this as the cause of problems from time to time.   Easy to clean these up. 

-- Mike Flowers, K6MKF, NCDXC - "It's about DX!"

On Jan 13, 2016, at 5:49 PM, 'Stephen Bloom' sbloom@... [Elecraft_K3] <Elecraft_K3@...> wrote:

 

That makes sense …My guess is that  I can probably fix it by adding another 10msecs to the Tx Lead time in N1MM (or I could increase the Delay on the K3 ..but I’d realllly rather not do that), but I’d still like to know what changed.  One possibility is the T/R relay in the amp has gotten slightly slower, and what is happening is the amp isn’t kicking in ..in the 10msec ..no way to test it right now …current propagation here is pretty much radio silence.

 

73

Steve KL7SB

 

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 4:08 PM
To: Elecraft_K3@...
Subject: RE: [Elecraft_K3] CW Losing first dit

 

 

It appears to me that your first dash in K is being truncated into a dot, so the other stations are copying you as UL7SB – rather than losing the first dot.

 

And this sounds like a timing issue …

 

- 73 and good DX de Mike, K6MKF, President - NCDXC

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 5:03 PM
To: Elecraft_K3@...
Subject: [Elecraft_K3] CW Losing first dit

 

 

Hey all:

 

Slight mystery here.  Was doing the CWOps CWT this morning ..and noticed that a number of ops were getting me as “UL7SB” rather than KL7SB ..which was followed by someone telling me directly that I was losing the first dit …first time having this problem that I am aware of ..speed varied from 28wpm to 34wpm ..didn’t seem to matter.

 

No immediately apparent reason why …

 

Configuration is K3 (with new the new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM  …the K3 TX Delay is ..and always has been the default of 8ms, the TX Lead time in N1MM (Winkey config tab) is 1 (meaning 10msec). operating semi break-in

 

Any thoughts?  No real way to test at the moment ..the lost dit isn’t noticeable using the tx mon.

 

73

Steve KL7SB

 
Re: [Elecraft_K3] CW Losing first dit

Stephen Bloom
 

That makes sense …My guess is that  I can probably fix it by adding another 10msecs to the Tx Lead time in N1MM (or I could increase the Delay on the K3 ..but I’d realllly rather not do that), but I’d still like to know what changed.  One possibility is the T/R relay in the amp has gotten slightly slower, and what is happening is the amp isn’t kicking in ..in the 10msec ..no way to test it right now …current propagation here is pretty much radio silence.

 

73

Steve KL7SB

 

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 4:08 PM
To: Elecraft_K3@...
Subject: RE: [Elecraft_K3] CW Losing first dit

 

 

It appears to me that your first dash in K is being truncated into a dot, so the other stations are copying you as UL7SB – rather than losing the first dot.

 

And this sounds like a timing issue …

 

- 73 and good DX de Mike, K6MKF, President - NCDXC

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 5:03 PM
To: Elecraft_K3@...
Subject: [Elecraft_K3] CW Losing first dit

 

 

Hey all:

 

Slight mystery here.  Was doing the CWOps CWT this morning ..and noticed that a number of ops were getting me as “UL7SB” rather than KL7SB ..which was followed by someone telling me directly that I was losing the first dit …first time having this problem that I am aware of ..speed varied from 28wpm to 34wpm ..didn’t seem to matter.

 

No immediately apparent reason why …

 

Configuration is K3 (with new the new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM  …the K3 TX Delay is ..and always has been the default of 8ms, the TX Lead time in N1MM (Winkey config tab) is 1 (meaning 10msec). operating semi break-in

 

Any thoughts?  No real way to test at the moment ..the lost dit isn’t noticeable using the tx mon.

 

73

Steve KL7SB

 
Re: [Elecraft_K3] CW Losing first dit

Jim Cox <jcox123@...>
 

Turn VOX on.  For some reason, not sure why, this cured my exact same problem using an external Winkeyer on the K3.  You don’t notice the lost first character on the cw monitor but is very apparent on a second receiver..  73s Jim K4JAF
 

Sent: Wednesday, January 13, 2016 7:02 PM
Subject: [Elecraft_K3] CW Losing first dit
 
 

Hey all:

Slight mystery here.  Was doing the CWOps CWT this morning ..and noticed that a number of ops were getting me as “UL7SB” rather than KL7SB ..which was followed by someone telling me directly that I was losing the first dit …first time having this problem that I am aware of ..speed varied from 28wpm to 34wpm ..didn’t seem to matter.

No immediately apparent reason why …

Configuration is K3 (with new the new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM  …the K3 TX Delay is ..and always has been the default of 8ms, the TX Lead time in N1MM (Winkey config tab) is 1 (meaning 10msec). operating semi break-in

Any thoughts?  No real way to test at the moment ..the lost dit isn’t noticeable using the tx mon.

73

Steve KL7SB
Re: [Elecraft_K3] CW Losing first dit

Mike Flowers
 

It appears to me that your first dash in K is being truncated into a dot, so the other stations are copying you as UL7SB – rather than losing the first dot.

 

And this sounds like a timing issue …

 

- 73 and good DX de Mike, K6MKF, President - NCDXC

 

From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Wednesday, January 13, 2016 5:03 PM
To: Elecraft_K3@...
Subject: [Elecraft_K3] CW Losing first dit

 

 

Hey all:

 

Slight mystery here.  Was doing the CWOps CWT this morning ..and noticed that a number of ops were getting me as “UL7SB” rather than KL7SB ..which was followed by someone telling me directly that I was losing the first dit …first time having this problem that I am aware of ..speed varied from 28wpm to 34wpm ..didn’t seem to matter.

 

No immediately apparent reason why …

 

Configuration is K3 (with new the new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM  …the K3 TX Delay is ..and always has been the default of 8ms, the TX Lead time in N1MM (Winkey config tab) is 1 (meaning 10msec). operating semi break-in

 

Any thoughts?  No real way to test at the moment ..the lost dit isn’t noticeable using the tx mon.

 

73

Steve KL7SB

 
Re: K3 Remote No SSB output Power

Frank Davis
 

I have discoveries  regarding my SSB audio output problem with my K3 Remote setup.  I reset both  RR BOXES to their DEFAULT PROFILES:

1.)  Issues are same for Yamaha CM500 and Heil Proset
2.)  With headsets plugged into the MIC and SPKRS jack on K3 Mini
I can now get SSB audio and power out if I set mike gain at 30 and COMPRESSION at 25. 
3.) Below 25DB COMP power out falls off dramatically. 
4.) At 0 COMP there is 0 power output no matter where the mike gain is
set.
5.) In MAIN:MIC SEL... rP.H BIAS....I can turn BIAS OFF and the mikes in each headset still work.  Turning BIAS on again doesn't change anything with the mikes.
6.) I used the external BIAS box that came with the CM500 and turned off internal rig BIAS....result is that the CM500 gives same audio level whether I use the BIAS box or not ...there is no difference with BIAS box in and out of the line terms of rig output when Mike gain is 30 and COMP is 25.
7)  The VOX does not work.  Have RTP Tx Mode set to CONTINUOUS in both RR boxes and also have FULL DUPLEX set YES.
8) I am using the PTT jack provided on the back panel of the K3 Mini.

Running COMP at 25 is too high....and I wonder why its has to be like that.  Did not have to set it that high when first setup the remote .  Something has changed.   Can anyone see anything relative to the BIAS that may not be right.?
CW Losing first dit

Stephen Bloom
 

Hey all:

 

Slight mystery here.  Was doing the CWOps CWT this morning ..and noticed that a number of ops were getting me as “UL7SB” rather than KL7SB ..which was followed by someone telling me directly that I was losing the first dit …first time having this problem that I am aware of ..speed varied from 28wpm to 34wpm ..didn’t seem to matter.

 

No immediately apparent reason why …

 

Configuration is K3 (with new the new synth boards), Expert 2K-FA Amp, Microkeyer, N1MM  …the K3 TX Delay is ..and always has been the default of 8ms, the TX Lead time in N1MM (Winkey config tab) is 1 (meaning 10msec). operating semi break-in

 

Any thoughts?  No real way to test at the moment ..the lost dit isn’t noticeable using the tx mon.

 

73

Steve KL7SB

 
Re: [Elecraft_K3] KXV3B Date

William Conkling <bconk75@...>
 

The K3S was introduced at Dayton last year. I am not sure that that are available for K3 updates yet.

The "A" version I believe was introduced when the 144 MHz internal transverter was introduced. 

...nr4c. bill


On Jan 13, 2016, at 3:24 PM, joe_word@... [Elecraft_K3] <Elecraft_K3@...> wrote:

 

About what date did the KXV3B replace the KXV3A in a new K3?

Thanks,

Joe  N9VX
Re: [Elecraft_K3] KXV3B Date

Bill Maddock
 

Back in the summer of 2015 - nice improvement in 12, 10 and 6 meters - has 20 db preamp won't need outside board with it installed 

73 

Bill N4ZI Munford TN 



Sent via the Samsung Galaxy S® 5 ACTIVE™, an AT&T 4G LTE smartphone


-------- Original message --------
From: "joe_word@... [Elecraft_K3]" <Elecraft_K3@...>
Date: 2016/01/13 14:24 (GMT-06:00)
To: Elecraft_K3@...
Subject: [Elecraft_K3] KXV3B Date

 

About what date did the KXV3B replace the KXV3A in a new K3?

Thanks,

Joe  N9VX
KXV3B Date

joe_word
 

About what date did the KXV3B replace the KXV3A in a new K3?

Thanks,

Joe  N9VX
10941 - 10960 of 36675