On 6/24/19 12:11 AM, Topher Petty wrote:
Hi Topher and all,
GPSD (Linux and OSX should be able to run this) can sync time to the
computer from a GPS receiver... I've used that in the past on where
internet access is problematic and time sync was critical.
I can confirm that using gpsd and nt
should be to “ read the ___ manual” (you can place a rude
adjective in front of manual if you wish)
73 de Lee KX4TT
From: Fred Price [mailto:n...@hotmail.com]
Sent: Tuesday, 25 June, 2019 08:57
To: Black Michael ; WSJT software development
Subject: Re: [wsjt-devel] Field Day time problem
GM,
The Tampa ARC used Ublox8 GPS dongles and software (which allows for syncing
either by dongle or NTP Server) to sync to the GPS sats during the contest for
two stations; the third synced to WWV by ear and still stayed pretty close. $16
each from Amazon for the dongles is a real bargain……
Late to the party because I've had other things on my plate, but I like
this approach and fully support your efforts.
The operators on my station alerted me that my station's clock was off by 2
seconds, and I was more focused on fixing the issue quickly to get them
back on track, than asking them
Michael,
I been teaching other hams for a lot of years. I been a ham for 34+ years.
Sorry but I disagree about reading the manual. Almost at least if not more then
75% of questions I'm asked are in the manual and or any release notes and yes I
read everything that the WSJT dev group puts out.
I
It's completely reasonable (or should I say expected) that when one installs
software that it "works". In particular for the common operating mode.I've
found the most you can expect from an operator with 40+ years of ops is that
they know how to turn on their rig and plug in cables. They will
Because it seems a lot of ops want a set it and forget it piece of software.
The things I read on this list that ops want WSJT to do amazes me.
On Jun 25, 2019 7:31 AM, VE3FBZ wrote:
Why add complexity/code to the software app when the problem is the user - not
the software or the rest of the c
Why add complexity/code to the software app when the problem is the user - not
the software or the rest of the community?
Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca
> On Jun 25, 2019, at 04:51, DG2YCB, Uwe wrote:
>
> The old JT65-HF Comfort had one additional feature: W
All comments are true. The accumulation of errors when entering the average
value of dT is also true. But "auto dT" it must be for operator use. Then there
will be no significant difference in dT in callLog.
25 июня 2019, 05:33:43, от "Reino Talarmo" < reino.tala...@kolumbus.fi >:
>Why actua
All comments are true. The accumulation of errors when entering the average
value of dT is also true. But "auto dT" it must be for operator use. Then there
will be no significant difference in dT in callLog.
25 июня 2019, 05:51:21, от "Sergio Yes UT9LI" < ut...@ukr.net >:
Yes!
Adjustment d
Yes!
Adjustment dT can be organized in the program itself. Discarding values, for
example, dT greater than 0.7, calculate the average value of dT over all
accepted values in the "callLog" list and automatically enter this value by
analogy with the "+/- dT" button. In this case, the operator
Adjustment dT can be organized in the program itself. Discarding values, for
example, dT greater than 0.7, calculate the average value of dT over all
accepted values in the "callLog" list and automatically enter this value by
analogy with the "+/- dT" button. In this case, the operator will ge
>Why actually set the computer clock? Just compute an offset for the local
>clock based on the mean (or median) of the DT of the decoded messages. Then
>use this offset within WSJT-X to adjust the time used in the software from the
>actual computer clock.
Hi Jim
Consider what would happen, if
Why actually set the computer clock? Just compute an offset for the local
clock based on the mean (or median) of the DT of the decoded messages. Then
use this offset within WSJT-X to adjust the time used in the software from
the actual computer clock.
Jim Record
On Mon, Jun 24, 2019 at 2:11 AM D
Thanks for comments. I totally agree the GPS solution, just everybody
needs to do so! I have one.
Actually I did not proposed, at least not before testing, any addition
or change into WSJTX. I just proposed a method more useful here, the
other side of pond, were WWV etc. are not so strong and
Do not understand all the ragging about other people’s incorrect computer time.
It’s their problem, not ours (mine). I simply avoid them and they miss out on a
contact. Now that out of adjustment time is flagged, it’s a non issue.
BTW if all returns are flagged as out of sync it’s your computers
I also agree with Fred, why do we constantly focus on reinventing the wheel?
WWV or other world time services and a mouse click will even work. A Cheap
CASIO watch has NIST time in it for $30. (works well Stateside).
The GPS dongles are dirt cheap and some even come with time setting
software. An
All
This posting by Fred gets my vote - easy, fool proof and does not distract the
dev team.
--
73’s
Tom
GM8MJV (IO85)
On 24 Jun 2019, at 09:27, Fred Price wrote:
> You are all overthinking the problem. There are programs to set your computer
> clock by a GPS dongle. A good plug in don
You are all overthinking the problem. There are programs to set your computer
clock by a GPS dongle. A good plug in dongle from Amazon is $12USD and the
program I use BktTimeSync is a free download.
Also if the dev group keeps adding more n more WSJT will become bloatware. I'd
rather see improve
A very good idea to set up time beacons, Reino! I like this approach!
However, as a short-term solution IMO dev team should find a way to use the
EXISTING data set of DT values for a pop-up saying that very likely time is
not synced correctly, plus an option to correct time by one click. Look t
Hi,
We are amateurs and could provide another time distribution experiment
especially during Field Day events. I mean setting up time beacon or beacons
that send e.g. every 15 s a short pulse, say 100 ms, on the base carrier
frequency e.g. 14.080 MHz. Timing of that pulse could be 'minute mark
with anything requiring some rather deep learning. If you don’t do
something every month, you won’t remember it.
73 -- Larry -- W1DYJ
From: Black Michael via wsjt-devel
Sent: Sunday, June 23, 2019 16:43
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] Field Day time
ime into that range. Sort of like a wire protocol that derives its own
> >> clock sync from the data stream. The change mechanism could be a
> >> calculation or a manual slider.
> >>
> >>
> >>
> >> *From:* Jim Jennings
> >> *Sent:* Sunda
could be a
>> calculation or a manual slider.
>>
>>
>>
>> *From:* Jim Jennings
>> *Sent:* Sunday, June 23, 2019 14:15
>> *To:* Black Michael ; WSJT software development <
>> wsjt-devel@lists.sourceforge.net>
>> *Subject:* Re: [wsjt-devel]
nnings
> *Sent:* Sunday, June 23, 2019 14:15
> *To:* Black Michael ; WSJT software development <
> wsjt-devel@lists.sourceforge.net>
> *Subject:* Re: [wsjt-devel] Field Day time problem
>
>
>
> When one of our stations at Field Day was set up for FT8, it be
sync from
the data stream. The change mechanism could be a calculation or a manual
slider.
From: Jim Jennings
Sent: Sunday, June 23, 2019 14:15
To: Black Michael ; WSJT software development
Subject: Re: [wsjt-devel] Field Day time problem
When one of our stations at Field Day was set up for
When one of our stations at Field Day was set up for FT8, it became apparent
that a system time sync was needed before it could be used. One of our
participants was able to provide a NTP sync with his smart phone, and W6AF (2A
SV) managed a couple dozen contacts on 20 Meters with five watts (Y
Of all the DT drifeters I saw not one was running JTAlert.
Then again highlighting the DT values > 0.5 seconds might be a better solution
though once you get your clock set the I find the highlighting irritating as
all highlight should be calling your attention to something.
And based on watching
JTAlert already does that. Highlights in red.
Aug
AG5AT
Sent from my iPad
> On Jun 23, 2019, at 2:04 PM, Gary Hinson wrote:
>
> Instead of “Your clock is off” (which, to some, may mean “Your clock is
> turned off”) I suggest “Your clock is wrong” or better still the
> action-oriented “Che
The latest JTAlert has this feature. You can set several DT error time
limits to be highlighted in red in the WSJTx Band Activity window of the
drifting station's DT.
If a station sees lots of red in the DT column, hopefully they would take
notice and figure out they are out of sync.
WB5JJJ - Ge
Instead of “Your clock is off” (which, to some, may mean “Your clock is turned
off”) I suggest “Your clock is wrong” or better still the action-oriented
“Check your clock”.
And the proposed 3 out of 5 decodes being more than half a second wrong risks
triggering the message far too often when
Good idea to create a msg to those out of clock ..repeatedly it can be
seen writing it on the screen. 73 de Enrique PY2CP
Em dom, 23 de jun de 2019 13:34, Matthew Miller
escreveu:
> That does seem like it could be useful, I would imagine the problem is
> compounded by field day people in parks
That does seem like it could be useful, I would imagine the problem is
compounded by field day people in parks probably sync their clock before
leaving and that's it.
I do find it interesting sync thru my 4G connection in this park NTP estimates
less delay and jitter than on my normal cable ISP
Seems like the RC version color highlighting of excessive dt’s should do the
job once it becomes the stable release.
BTW, our club (W6JU) had a GPS NTP server incorporated in the N3FJP logging
server we used and that worked really well - as did the JTAlert N3FJP
auto-logging. Only thing we noti
34 matches
Mail list logo