I had the same problem with a long earth lead.
David
G3UNA
- Original Message -
From: "Don Wilhelm"
To: "david beckwith"
Cc:
Sent: Thursday, November 25, 2010 2:21 AM
Subject: Re: [Elecraft] PTT stuck? Error?
> Dave,
>
> Put a balun on your antenna.
Dave,
Put a balun on your antenna.
Seriously, that is likely being caused by "RF in the shack", and the
only cure is to work on your antenna system to minimize it.
73,
Don W3FPR
On 11/24/2010 9:08 PM, david beckwith wrote:
> A quick question. I have a Heil Proset headset into the front of t
PTT RLS is the delay between you releasing the PTT and the K3 changing
from TX to RX. It is used in ARQ data modes such as Amtor or Pactor to
allow time to clear the data from the TX (DSP introduces delays in the
K3 IF). The values are in milliseconds, typically set to 012 for using
an SCS PTC Pact
First, Set the K3 just like you would for QSK (or semi-break-in,
if that's what you want), and get it working with your paddle or
bug. Now, without changing anything, set the K3 CONFIG:PTT-KEY to
OFF-DTR. Now, go into WriteLog and tell it to send CW on the same
COM port that you're using for ri
Roger Marrotte-2 wrote:
>
> I've been trying different DTR and RTS settings (CONFIG|PTT-KEY) to get
> PTT
> and CW to work with a serial port connecting my computer to my K3. In
> particular I've been trying to get Writelog and DX4WIN to work. I'm using
> a
> real serial port and a serial cabl
I think this is another case of a need for a simple block diagram.
Somehow this was made to appear complicated. It really isn't. Here are
the three rules:
1) If you want the transmitter on, press PTT.
2) If you want the receiver on, don't press PTT.
3) If you don't want to bother with PTT
I think this is another case of a need for a simple block diagram.
David
G3UNA
-
Email sent from www.virginmedia.com/email
Virus-checked using McAfee(R) Software and scanned for spam
___
Elecraft mailing list
Pos
Fred, you said it all!
Doug
W6JD
-- Original message --
From: Fred Jensen <[EMAIL PROTECTED]>
> I had absolutely no idea that PTT was this complex and required all
> these words to adequately describe it :-) The only complexity in PTT
> that I've ever known about is t
On Tue, Sep 25, 2007 at 10:43:33AM -0700, Fred Jensen wrote:
> I had absolutely no idea that PTT was this complex and required all
> these words to adequately describe it :-) The only complexity in PTT
> that I've ever known about is that it should stand for "push, then talk"
> since it's fair
Look at the break delay setting .. I use a pair of K2s with my V/U/SHF
rover, and set the break delay to about 300ms to get the same effect
as a hard key (so my amp relays don't get thrashed). I'm assuming
that's why you would need hard PTT .. but maybe I'm wrong?
de w1rt/john
On 8/2/06, Bob Eva
By "PTT on code" do you mean pushing a button or foot switch to change
between transmit and receive?
If so, when would that be preferable over QSK?
Ron AC7AC
-Original Message-
Has anyone heard of any movement by Elecraft to modify the K2's firmware to
allow PTT use on CW? I'd really
Ah! I see it now. Thanks Jim.
Kevin
N8IQ
-Original Message-
From: k4zm [mailto:[EMAIL PROTECTED]
Sent: Monday, March 13, 2006 2:06 PM
To: [EMAIL PROTECTED] List; Kevin Shaw
Subject: Re: [Elecraft] PTT Signal Question
Kevin:
Look on Page 1 of 1 of the Control Board on the bottom of
Kevin:
Look on Page 1 of 1 of the Control Board on the bottom of the page
Connector P3 Pins 17 & 18 are tied to 5 Volts through 82K resistors in RP4
(5&6 7&8) .
73
Jim Younce K4ZM
K2 SN: 18
___
Elecraft mailing list
Post to: Elecraft@mailman.q
101 - 113 of 113 matches
Mail list logo
