| |
G0FTD > MORSE 04.06.06 17:23l 25 Lines 935 Bytes #999 (0) @ WW
BID : 2D4765G0FTD
Read: GUEST DF1GG
Subj: Re: Small survey
Path: DB0FHN<DB0THA<DB0ERF<DB0MRW<DK0WUE<GB7FCR<GB7YKS<GB7SYP<GB7ESX<GB7NNA
Sent: 060604/1433z 08145@GB7NNA.#31.GBR.EU $:2D4765G0FTD [Witham, Esx]NNA V3.1
G3ZJO wrote:-
> Sure does on my old laptop when running WSJT and decoding. It GAINS time
> during the night when off then loses as much as 8 seconds during a long
> session in the day.
Considering that the IBP beacons use a *10 second slot*, I can imagine the
amount of duff reports sent about through erroneous timing.
For anything to work properly requires a standard time and frequency
receiver (like MSF in the UK), which is a hardware device attached to
a beacon timer.
> Whilst it's a good system, there is alway the margin for doubt that what
> you heard was actually what should have been there at that time. For me,
> read the morse and confirm, yes I indentified it.
I totally agree. There's only one way to confirm an ID, an that is to
read the Morse, not a bit of software with OS timing errors.
However an author who should know better is promoting a *software* solution,
which I think is a lousy idea.
- /\ndy -
Read previous mail | Read next mail
| |
