Well I had a problem with seemingly wrong headings and
distances too. By chance I found that ENLARGING the
Beam Headings window all of a sudden made everything right!
73 de Goetz
dj3iw@t-online.de
----- Original Message -----
From: <writelog-request@contesting.com>
To: <writelog@contesting.com>
Sent: Wednesday, February 26, 2003 5:22 PM
Subject: WriteLog Digest, Vol 2, Issue 59
>
> 1. Re: Beam Heading Problem (K4SB)
>
>
> ----------------------------------------------------------------------
>
To: <writelog@contesting.com>
> Date: Wed, 26 Feb 2003 16:27:22 +0000
> From: K4SB <k4sb@earthlink.net>
> To: writelog@contesting.com
> Subject: Re: [WriteLog] Beam Heading Problem
> Message-ID: <3E5CEAEA.C17D28BF@earthlink.net>
> References: <3E5CD982.2060804@crosslink.net>
> Content-Type: text/plain; charset=us-ascii
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Precedence: list
> Message: 1
>
> DaveK wrote:
> > Hello All,
> > Two weeks ago I got the latest version of WL. In loading in the Qth
> > coordinates, I find the beam heading to be way off. For example, from
> > Virginia to the UK, the beam heading is about 4 degrees and some 300
> > miles away. I discussed this with K4JA & K9JY Scot. I even used the
> > K4JA coordinates. Same problem.
> -------------------
>
> WOW, no wonder you guys further North whip the socks off us! ):>
>
> Seriously, there are 3 possibilities.
>
> 1. Your home data is not properly set, or WL is changing it into
> something else.
>
> 2. The UK data is not properly set, or WL is changing it.
>
> 3. The algorithm in that version of WL is wrong.
>
> And if I had to bet my boots, I'd vote for #3.
>
> 73
> Ed
>
> ------------------------------
|