Thanks, Joe! Good info.
Andrew NO6E
Sent from BlueMail
On Dec 6, 2018, 09:22, at 09:22, Joe Taylor wrote:
>Hi all,
>
>A number of comments and questions have appeared here recently
>concerning the parameter DT displayed by the WSJT-X decoders.
>
>K6AVP:
>> Only a few have posted what range of
To summarize isn't it safe to say:
"As long most of your DT times are less than 1 second you will be able to
decode everybody else who is less than +/-1 second. WSJT-X allows 2.5 seconds
of difference so if both sides are off by 1 second in opposite directions that
would be 2 seconds of DT and
Hi all,
A number of comments and questions have appeared here recently
concerning the parameter DT displayed by the WSJT-X decoders.
K6AVP:
Only a few have posted what range of DT’s they mostly see ...
K9YC:
My memory is routinely seeing DTs in the range of +/_ 200msec, with occasional
ou
With 1.9.1 I saw a range of +/- 0.2-s. With rc5 I am seeing 0 to +0.35 and
no -. I understand that this is caused by a bug that will be fixed when
2.0.0 is released.
On Thu, Dec 6, 2018 at 8:36 AM George J. Molnar wrote:
> Thanks John!
>
> There is nothing to be gained by tweaking the last milli
Thanks John!
There is nothing to be gained by tweaking the last milliseconds out of timing.
Sure, it looks pretty and appeals to the perfectionist in us, but as long as it
-WORKS- call it good and have some fun.
George J Molnar
KF2T, Arlington, Virginia, USA
Please note my new email: geo...
Al,
I think the key question is are you otherwise getting satisfactory
performance? Are you making Q's? This subject is starting to take on the
tenor of the never ending quest for a 1:1 SWR. And as we used to like to
say, "If the SWR is less than 10:1, call 'CQ'!"
John
On Wed, Dec 5, 2018 at
On 12/5/2018 7:00 PM, Al Pawlowski wrote:
Only a few have posted what range of DT’s they mostly see
My most recent experience is with 1.9, and on 6M from the summer. My
memory is routinely seeing DTs in the range of +/_ 200msec, with
occasional outliers up to 2 sec or so. My sound card is a T
Only a few have posted what range of DT’s they mostly see when time.is (or
something else) says their PC clocks are right on the money. Mine is
consistently +0.35s. Do most peoples see something similar?
If I slow my clock by 0.35s, while sync’d to gps and nist.time and time.is says
it is right
On 05/12/2018 00:12, Al Pawlowski wrote:
I wonder if I should add in, or subtract, another 0.1s for the tx
delay I have set.
Hi Al,
the Tx delay does not change the timing of the signal. The Tx signal
synchronized with the PC clock at the start of a Tx period (interpolated
forwards if Tx sta
