My guess, after many years of FD, is that MOST operators would have little idea
of what ANY indication of a clock-sync issue means. Many ops are sitting down
operating for the first time, getting their feet wet with (NOT A CONTEST) Field
Day. PLUS, as has been noted, many FD sites DO NOT have
You know, you can set a computer clock with WWV +/- propagation delay and
muscle reaction time. It works and is very much like what one might do in the
field on a bad day. Don't over think it.
73
-Jim
NU0C
On Sun, 23 Jun 2019 18:15:00 -0400
Topher Petty wrote:
> Example from a quick search:
Example from a quick search:
https://www.aliexpress.com/item/Aviation-Vehicle-Positioning-Receiver-G-MOUSE-Glonass-Navigation-USB-GPS-Module-Dongle-Tracking-Replacement-Alarm-Car/33006770294.html
73 de AI8W, Chris
On Sun, Jun 23, 2019 at 6:11 PM Topher Petty wrote:
> GPSD (Linux and OSX should
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. A cheap USB GPS
unit could then be purchased (I've seen them as low as $5 on US sites, and
around $2 on
You could use the DT of the received stations to adjust the clock.
Select a group with the largest agreement within a narrow range of a few tenths
of a second, and the program, or a program, can offer to adjust the time into
that range. Sort of like a wire protocol that derives its own clock sy
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
Perhaps drop the grid in FD mode and put in the Class letter.
I strongly support this modification.
This would allow us to select wanted/require call to complete our maps etc.
Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca
> On Jun 22, 2019, at 16:57, WB5JJJ wrote:
>
> I
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
Field Day Configuration. Still checking out rc7 since it hasn't locked out
so far. So why not run with it?
For some reason in FT8 and calling CQ, even though Call 1st is UNCHECKED,
about every other sequence an automatic response will be generated to a
random station calling me.
Sometimes this
On 6/23/19 12:53 PM, Palle Preben-Hansen, OZ1RH wrote:
Hi Palle,
Claude, at present this is not unwanted switching to EU VHF mode, but
the naming or wording of what is happening is misleading.
The situation seems to be that you work a station that is in a contest
requiring an exchange of a s
I've seen about 2 dozen clubs doing Field Day where their clocks are off.
We need to provide an indication in WSJT-X when clocks are off like this.
With concurrence I can do a patch for thismy idea is this.
At least 5 decodes where 60% or more > 0.5 seconds is an indication of bad
timing.A mes
Claude, at present this is not unwanted switching to EU VHF mode, but the
naming or wording of what is happening is misleading.
The situation seems to be that you work a station that is in a contest
requiring an exchange of a serial number and/or the full locator (a 6-digit
locator). In order to r
On 6/23/19 10:26 AM, Reino Talarmo wrote:
Returning to the STATE value that now contains Maidenhead locator as an EU
VHF contest exchange information. I also think that it is a mistake to use
the STATE field for that purpose. We have and that now contains
the same information.
Perhaps the use o
Returning to the STATE value that now contains Maidenhead locator as an EU
VHF contest exchange information. I also think that it is a mistake to use
the STATE field for that purpose. We have and that now contains
the same information.
Perhaps the use of the STATE field in the EU VHF contest is j
On 6/23/19 9:32 AM, Reino Talarmo wrote:
190622_095330 7.074 Tx FT8 0 0.0 1480 HB9CGH DJ0OT -04
190622_095400 7.074 Tx FT8 0 0.0 1480 HB9CGH R 550001 JN58TC
Some observations: 55 and 55 were not exchanged in
the QSO and they are typical FONE reports. According to the ADIF
>190622_095330 7.074 Tx FT8 0 0.0 1480 HB9CGH DJ0OT -04
190622_095400 7.074 Tx FT8 0 0.0 1480 HB9CGH R 550001 JN58TC
>Some observations: 55 and 55 were not exchanged in
the QSO and they are typical FONE reports. According to the ADIF specs, I
consider JN36RW as not valid.
Th
Hi all,
Please allow me to report about an unusual behaviour which I have
observed using 2.0.1.
Settings -> advanced -> special operating activity -> OFF
While operating in the usual way, on the 40 m band in FT8 mode, my
station was called and the mode switched automatically to the EU VHF
c
23 matches
Mail list logo
