-Original Message-
From: Joe Taylor via wsjt-devel
Sent: 21 October 2021 14:48
To: wsjt-devel@lists.sourceforge.net
Cc: Joe Taylor
Subject: Re: [wsjt-devel] Time slip
Hi Conrad,
I think you need to work on your Linrad configuration to reduce the total
latency in data being sent to MAP65
Hi Conrad,
I think you need to work on your Linrad configuration to reduce the
total latency in data being sent to MAP65. I used a Linrad ==> MAP65
configuration for many years with excellent results, taking advantage of
(among other things) the Linrad noise blanker. Latency was well under
I have a problem with latency when using Linrad to produce H and V signals for
WSJT-X. In WSJT-10 there is a box called Dsec. It is very useful, please
reintroduce it. Time fudge is not an option because that would mess up WSJT-X
fed from my K3S as well as MAP65 where latency is very low. It is
Hi Stephen:
I have, in my dubious spare time, been working on a WSJT-X FAQ sanctioned by
Bill, G4WJS, and Joe, K1JT. Once it's up, it should reduce the repetition, and
the need for extra releases.
Now that Im letting the cat out of the bag, if anyone has a candidate FAQ
(hopefully with an
Hmmm I am looking at quite a number of messages here and a lot of "related
postings" seem to be coming up.
Is it perhaps time for another release of the work in progress to perhaps clear
some of the repetition?
___
wsjt-devel mailing list
JS8call implemented an DT synchronizer that automatically synchronizes the
DT of a station of interest based on user input of the start and end times
of a single transmission. I think it might be trivial to implement a
similar feature in WSJT-x that allows for time synchronization, but based
on
First off, I much prefer SSB phone to FT8, but with the current band
conditions, I find FT8 a great stop gap measure and certainly glad it's
available, otherwise my rigs would be collecting dust and cat fur. FT8
will probably be a cyclic operational mode as band conditions improve, but
it's big
>
>
> However, your attention to the issue gives me an idea... If an instance of
> WSJT-X sees that most (90%) of remote signals it sees are too far off from
> its own, the chances are is that it's *the local user's* clock that needs
> adjusting, and that user could be alerted to sync their clock
Hi Jesus,
I cannot reproduce the problem you describe. Please give us a
step-by-step recipe, beginning with program startup (in XXX mode?) that
will show the incorrect sequence length for FT4.
-- 73, Joe, K1JT
On 6/5/2019 11:19 AM, Jesús Gutiérrez Rodríguez wrote:
Good afternoon, I
Good afternoon, I observe when working on FT4, that, in reception, the
frames appear at intervals of 7/8 seconds, correct.
If you activate the transmission the frame indicates every 15 seconds, as
in FT8; When going back to reception, keep the frames to 15 seconds when it
should indicate 7/8
Essentially if everyone sets up some time sync process to a time standard then
the issues will be minimized.
Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca
> On Jun 4, 2019, at 15:14, Bill Frantz wrote:
>
>> On 6/3/19 at 4:56 AM, slotter+w3...@gmail.com (Dave Slotter)
On 6/3/19 at 4:56 AM, slotter+w3...@gmail.com (Dave Slotter) wrote:
It doesn't do much good to be "in-your-face" about clock synchronization
issues to the receivers of signals which are off by too high a delta,
because it's the sender that needs their clock adjusted, not the receiver.
However,
Claude wrote:
" as well as the propagation delay and the time needed to decode."
We may forget propagation time that is less than 0.1 s on globe, moonbounce
is another issue.
To my understanding dT is calculated based on message time sync location on
the received timeslot and is fully
On 6/3/19 1:56 PM, Dave Slotter wrote:
It doesn't do much good to be "in-your-face" about clock synchronization
issues to the receivers of signals which are off by too high a delta,
because it's the sender that needs their clock adjusted, not the receiver.
Exactly, Dave ! The DT, at the
Actually it's both. If your clock is spot on you have more "slop" in the time
then if your own clock is off by any amount.Yeah...it's mostly the sender when
it shows up far too high on the receiver side but it does work both ways.
The idea of this "majority" was brought up before but don't
Morning all, continued super support group.
I use Dimension 4 to keep my Win 10 laptop in sync.
I like the the red flag on an out of step clock. I simply avoid the call.
I’ve tried to inform the user in the past to no avail.
Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca
> On
Mike,
It doesn't do much good to be "in-your-face" about clock synchronization
issues to the receivers of signals which are off by too high a delta,
because it's the sender that needs their clock adjusted, not the receiver.
However, your attention to the issue gives me an idea... If an instance
Would probably be good if WSJT-X did what JTAlert has started
doing...highlighting DT values > 1.5 sec.
For FT4 perhaps highlight > 0.5 seconds since if both sides are off -.5 and 0.5
I assume that would be an unlikely decode.This is what JTAlert does now.Then,
also put some help in the manual
18 matches
Mail list logo
