[Dx4win] wrong heading for a specific call?
WA7AA
wa7aa at comcast.net
Wed Aug 31 19:38:52 EDT 2016
On 31-Aug-16 14:50, Jim Reisert AD1C wrote:
> On Wed, Aug 31, 2016 at 3:42 PM, Rick K0XB wrote:
>
>> I wonder if anyone has an idea why this is going on: I entered the callsign
>> "TZ4AM" into the main window on DX4WIN, and it told me the heading was 143
>> degrees. I'm in Minnesota, so this is obviously incorrect for TZ. But if I
>> enter any other TZ call, it tells me the heading is 78 degrees, which I
>> believe is correct. Why would it show an incorrect heading for a specific
>> call?
> DX4WIN probably inherited a grid square (or IOTA ?!?) from a previous
> QSO with TZ4AM.
>
Yeah, it looks like TZ4AM incorrectly loaded his LotW configuration with
FK52 instead of the IK52 grid, which puts him in the Aruba area. I still
don't understand why LotW doesn't implement some elementary
configuration verification checks, at least for zones and such.
73,
Zoran WA7AA
More information about the DX4WIN
mailing list