[Elecraft] K3 And WSJT-X FT8 Timing

[Richard]

Initially, I was using CAT. Now I’m trying RTS.

Just called CQ and the K3S never came out of transmit.

> On Feb 23, 2018, at 8:22 AM, Ted Bryant <w4nz at comcast.net> wrote:
> 
> I find the same transmit delay when using my Icom 756ProIII as when using my K3.  That indicates the transmit delay is coming from the software, not the radio.
> The delay is consistent, ~ 1 second.  Even so, to me a 1 second delay is not a problem.  On both radios manual PTT is instantaneous.
> 
> Richard, how are you doing PTT -  DTR? RTS? VOX?
> 
> 73, Ted W4NZ
> 
> 
> -----Original Message-----
> From: elecraft-bounces at mailman.qth.net [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Wayne Burdick
> Sent: Friday, February 23, 2018 12:20 AM
> To: Richard
> Cc: Elecraft Reflector
> Subject: Re: [Elecraft] K3 And WSJT-X FT8 Timing
> 
> RIchard,
> 
> There are no long delays inherent in the K3/K3S transmit timing. It should be ready to transmit RF within 5 to 15 ms of PTT assertion, depending on mode and other factors. 
> 
> My apologies; I have not been closely reading this thread. I’ll come up to speed and get back to you. 
> 
> If this is a transceiver problem, we’ll fix it ASAP. 
> 
> Wayne
> N6KR
> 
> ----
> http://www.elecraft.com
> 
>> On Feb 22, 2018, at 8:32 PM, Richard <FlatHat at comcast.net> wrote:
>> 
>> Maybe I’m missing something, but the “timing” problem with which some of us are fighting has nothing to do with computer clock accuracy. Even if the computer time is off, it’s the only time reference WSJT-X has to work with.
>> 
>> So the instant the computer tells the software it’s time to transmit, BANG! WSJT-X goes into transmit RIGHT NOW, as it should, late or not, the software doesn’t know and doesn’t care.
>> 
>> Our problem is that when WSJT-X goes into Transmit at the top of the new segment and tells the K3S to transmit, the K3S DOESN’T transmit. Its almost always late by 2 or 3, sometimes 4 or 5 full seconds. In my case, it eventually doesn’t transmit AT ALL!
>> 
>> That’s not a software problem or a computer clock problem. It looks like a K3S problem, and I’d sure like to see the solution before I dump this radio.
>> 
>> Richard - W4KBX
>> 
>>> On Feb 22, 2018, at 8:36 PM, Bob McGraw K4TAX <rmcgraw at blomand.net> wrote:
>>> 
>>> If you are seeing a majority of the decodes in which the DT is less than <0.5 seconds, your computer clock is close enough for reliable contacts and decodes.   The software should handle decodes with a DT up to 2.0 seconds, but in many cases this depends largely {very largely in fact} on signal quality.  Both as transmitted and received.
>>> 
>>> 73
>>> 
>>> Bob, K4TAX
>>> 
>>> 
>>> 
>>>> On 2/22/2018 7:28 PM, Nr4c wrote:
>>>> Check the clocks on the computers. Sync them to a time server.
>>>> 
>>>> Sent from my iPhone
>>>> ...nr4c. bill
> 
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at 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 flathat at comcast.net