Different headings for same country

[WA2SQQ]

I'm wondering if someone can explain how two calls from the same country can show two distinctly different beam headings?

9M62MM shows 348 / 168
9M62MS shows 100 / 280
Both identify as East Malaysia

[WA2SQQ]

348 is the correct heading - FYI, both show the same heading according to QRZ.

[G4POP]

Short path and long path

Short path plus 180 degrees equals long path

[WA2SQQ]

I full understand long path and short path .... Compare the two short path headings for each of the two stations (in the same country). Checking on QRZ, they both come back the same.

[G4POP]

I full understand long path and short path .... Compare the two short path headings for each of the two stations (in the same country). Checking on QRZ, they both come back the same.

When checking QRZ for these 2 calls neither have a locator which we use to calculate headings and on QRZ details both stations show different headings anyway!

When no heading is returned from lookup Log4om uses an approximation for country as there is no accurate grid reference available.

[WA2SQQ]

Thanks for the fast response - very much appreciated.
Checked QRZ and I'm getting the same results for both stations
Perhaps a variable associated with web browsers?

Beam Headings.jpg (122.49 KiB) Viewed 6115 times

[G4POP]

Strangely I am getting the same result and as you can see log4OM provides the same data for both calls?????

qrz LOOKUP.jpg (95.33 KiB) Viewed 6110 times

[WA2SQQ]

Oh well, an unsolved mystery! Sri to take up so much of your time. I thought it might be of interest for the developers of the new version. Again, many thanks for your dedication to this great program. Not a big deal!

[WA2SQQ]

Terry, something is definitely going on with beam headings in the latest version. I just spotted EP2C on the cluster. LOG4OM shows a heading off 100 / 280. That seemed incorrect, so I checked it on QRZ and it shows 42 (short path). Verified it with another source and 42 it is. MY grid square is FN20wv in case you want to try it. H is active on the cluster now.

Not complaining, but I just wanted to make you aware in case the same code is being used in 2.0
More strange, most other stations are OK.

[G4POP]

I think that you either need to update the files like clublog or country files or something similar because as you will see I cannot emulate your issue in Version 1 or 2, they are the same as QRZ within a gnats whisker -the bearing in V2 is at the top

Untitled.jpg (176.12 KiB) Viewed 6058 times