[Elecraft] K3 And WSJT-X FT8 Timing

[Bob McGraw K4TAX]

In as much as one only has 1 second minimum resolution, I'd say that is 
quite normal.  No,. the ALC/RF should not occur at the same time as the 
TX LED is illuminated.

In order to correctly determine accurate timing values, one needs to use 
a triggered dual trace scope to see exactly when things occur.   In my 
life, one second one way or the other makes absolutely no difference.

73

Bob, K4TAX


On 2/23/2018 1:16 PM, James Bennett wrote:
> Made changes to my “radio” tab as suggested below and I see some improvement, and wondering if this is what I should expect: At the “zero” time mark, the rig red TX light comes on and at the +1 second mark, RF /ALC is happening. Expected behavior? or should the RF/ALC start at the same time as the red TX light?
>
> Both the K3 and KX3 are exhibiting the same response.
>
> Jim / W6JHB
>
>> On Feb 23, 2018, at 10:32 AM, Walter Underwood <wunder at wunderwood.org> wrote:
>>
>> Systems haven’t used two stop bits for decades. I’ve never set a system to two stop bits and I was supporting a big UUCP node at Hewlett-Packard in the late 1980’s.
>>
>> wunder
>> Walter Underwood
>> wunder at wunderwood.org <mailto:wunder at wunderwood.org>
>> http://observer.wunderwood.org/ <http://observer.wunderwood.org/>  (my blog)
>>
>>> On Feb 23, 2018, at 9:58 AM, RIchard Williams via Elecraft <elecraft at mailman.qth.net <mailto:elecraft at mailman.qth.net>> wrote:
>>>
>>> When setting up radio settings in WSJT-X for the K3/K3S, I keep seeing different settings for the number of stop bits (one and two) popping up on the reflector.    Am not sure where TWO stop bits is coming from???  On page 20 of the K3S manual (page 18 of the K3 manual), left hand column, Serial Port Setup,  it states "Software should be set up at the same rate: 8 data bits, no parity, 1 stop bit".
>>> Have no idea why the Radio set window in WSJT-X defaults to TWO stop bits when you select Elecraft K3/K3S.   Initially, I did not catch this, and I was encountering problems with my K3S remaining in transmit mode more often than not after a transmission.  Once I changed to ONE stop bit, my problem magically went away.
>>>
>>> What I have set up is:
>>> Rig: Elecraft K3/K3S , Polling interval: 1sec
>>> CAT control: COM 13 (which is a virtual com port set up with LP-Bridge with my setup, your setting will be whatever com port are using).
>>> Baud rate: 38,400
>>> Data Bits, Stop Bits, and Handshake:  8, none, 1.
>>> PTT method: CAT
>>> Mode: Data/Pkt
>>> Split Operation:  Rig
>>>
>>> DIck, K8ZTT
>>> ______________________________________________________________
>>> 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 wunder at wunderwood.org <mailto:wunder at wunderwood.org>
>> ______________________________________________________________
>> Elecraft mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/elecraft <http://mailman.qth.net/mailman/listinfo/elecraft>
>> Help: http://mailman.qth.net/mmfaq.htm <http://mailman.qth.net/mmfaq.htm>
>> Post: mailto:Elecraft at mailman.qth.net <mailto:Elecraft at mailman.qth.net>
>>
>> This list hosted by: http://www.qsl.net <http://www.qsl.net/>
>> Please help support this email list: http://www.qsl.net/donate.html <http://www.qsl.net/donate.html>
>> Message delivered to w6jhb at me.com <mailto:w6jhb at me.com>
> ______________________________________________________________
> 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 rmcgraw at blomand.net