Keyboard Shortcuts
Likes
Search
Short Path Heading
|
This is puzzling - The Short Path headings don't agree. I clicked on this spot in SC and that populated both Capture and Path Finder with this information. So which is correct and why are there two different headings in PF? Apologies to K1NMF for using his call in this example. Thanks and 73, Rod/w7zrc |
|
Sri, not sure the screen image came thru - here is an attachment
On Tuesday, March 3, 2020, 10:19:56 AM MST, Rod Greene via Groups.Io <w7zrc@...> wrote:
This is puzzling - The Short Path headings don't agree. I clicked on this spot in SC and that populated both Capture and Path Finder with this information. So which is correct and why are there two different headings in PF? Apologies to K1NMF for using his call in this example. Thanks and 73, Rod/w7zrc |
|
+ AA6YQ comments below
This is puzzling - The Short Path headings don't agree. I clicked on this spot in SC and that populated both Capture and Path Finder with this information. So which is correct and why are there two different headings in PF? Apologies to K1NMF for using his call in this example. + There are many sources of location information, and they don't always agree. Also, and application or web page that computes a beam heading needs to know your location; any differences will result in a different beam heading. + Without more detailed information (e.g. locations specified in previously logged QSOs, overrides, callbook being checked), I can't be more specific. 73, Dave, AA6YQ |
|
Thanks Dave, All the apps I am using: (SC, DXK, and PF) have my coordinates entered and they all agree. I'm just wondering why there would be a difference between the Capture window and the PathFinder window in the SP Heading? Don't they use the same source? 73, Rod
On Tuesday, March 3, 2020, 10:28:54 AM MST, Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below This is puzzling - The Short Path headings don't agree. I clicked on this spot in SC and that populated both Capture and Path Finder with this information. So which is correct and why are there two different headings in PF? Apologies to K1NMF for using his call in this example. + There are many sources of location information, and they don't always agree. Also, and application or web page that computes a beam heading needs to know your location; any differences will result in a different beam heading. + Without more detailed information (e.g. locations specified in previously logged QSOs, overrides, callbook being checked), I can't be more specific. ? ? ? ? 73, ? ? ? ? ? ? ? ? ? Dave, AA6YQ |
|
Think I understand it now - In DXV the box under the SP Heading is the heading of the last heading. As soon as I click on the SP Heading box to turn my rotor, then they agree and it resets the Capture az - path box to the Short Path instead of the last heading. This Last Heading info had me confused. Thanks again! 73, Rod/w7zrc
On Tuesday, March 3, 2020, 10:49:20 AM MST, Rod Greene via Groups.Io <w7zrc@...> wrote:
Thanks Dave, All the apps I am using: (SC, DXK, and PF) have my coordinates entered and they all agree. I'm just wondering why there would be a difference between the Capture window and the PathFinder window in the SP Heading? Don't they use the same source? 73, Rod
On Tuesday, March 3, 2020, 10:28:54 AM MST, Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below This is puzzling - The Short Path headings don't agree. I clicked on this spot in SC and that populated both Capture and Path Finder with this information. So which is correct and why are there two different headings in PF? Apologies to K1NMF for using his call in this example. + There are many sources of location information, and they don't always agree. Also, and application or web page that computes a beam heading needs to know your location; any differences will result in a different beam heading. + Without more detailed information (e.g. locations specified in previously logged QSOs, overrides, callbook being checked), I can't be more specific. ? ? ? ? 73, ? ? ? ? ? ? ? ? ? Dave, AA6YQ |
¿ªÔÆÌåÓý+ AA6YQ comments below ? All the apps I am using: (SC, DXK, and PF) have my coordinates entered and they all agree. ? + You cannot specify your coordinates in Pathfinder; if you have DXKeeper configured to use ¡°QRZ via Pathfinder¡± as a callbook, then you must specify your coordinates in QRZ. ? + When performing a lookup, DXKeeper and SpotCollector give top priority to the location specified in an Override. SpotCollector doesn¡¯t check for location information in previously logged QSOs (because it would take too long), but DXKeeper does if appropriately configured. ? + DXLab applications all use the same code to compute a heading from your QTH and a specified location, but another application? - like QRZ ¨C may perform the calculation with a different level of accuracy and the yield slightly differing results. If you cite specific examples (callsigns, headings), I can be more specific. ? I'm just wondering why there would be a difference between the Capture window and the PathFinder window in the SP Heading? Don't they use the same source? ? + Pathfinder does not compute headings. Pathfinder displays web pages (like QRZ.com) that can compute headings. ? ???????????? 73, ? ???????????????? Dave, AA6YQ ? |
|
+ AA6YQ comments below
Think I understand it now - In DXV the box under the SP Heading is the heading of the last heading. As soon as I click on the SP Heading box to turn my rotor, then they agree and it resets the Capture az - path box to the Short Path instead of the last heading. This Last Heading info had me confused. + Yes, it's the last heading sent to your rotator that is logged with your QSO (unless you check the "Report computed short path heading when disabled or on unsupported band" box at the top of DXView's Configuration window's "Rotator Control" tab. DXKeeper also logs the "antenna path" item based on whether you last turned your rotator by clicking the SP or LP button. 73, Dave, AA6YQ |
|
My apologies Dave. I think I was specifying Path Finder and should have said DXView
toggle quoted message
Show quoted text
Rod On Tuesday, March 3, 2020, 11:11 AM, Dave AA6YQ <aa6yq@...> wrote:
|