Date   

Re: DXK versus Adif export

eddy on5jk
 

Yes Dave, today it is working fine. Maybe because of the updated DXK?

Anyway i can restart exporting all filtered logpages, sorted by WWFF, WCA,  LH etc.

Then finaly i can upload all ADIFs to GMA, without missing several QSOs.

To proove i was not dreaming or so, i sent you two screenshots, one of the ADIF dated November, and one dated December (today). A big difference.

For WWFF refs (starting after April 2012) i had 17.962 QSOs in the filtered log, and 17.962 are exported to ADIF.

Thanks a lot to you and Iain for support.

Don't know what happened, but to me "the answer is blowing in the wind"but problem solved!

Happy NY to all.

Eddy ON5JK

Op 24/12/2020 om 19:56 schreef Dave AA6YQ:

There's an error in the SQL expression that Dave provided (it would only match if the QSO occurred at exactly 00:00 UTC on that date). Try this one instead:

Call='F8GGZ/P' and DateValue(QSO_Begin) = '2020-08-25'

Apply that filter, then export, and send the ADIF to Dave.

+ Iain, Eddy informed me via email that the SQL expression I sent him didn't work, and I sent him back

(call=’F8GGZ/P') and (QSO_BEGIN>#2020-08-25#) and (QSO_BEGIN<#2020-08-26#)

+ He then sent me the ADIF record for this QSO, as I requested. The ADIF record looks fine.

+ Eddy, after importing the ADIF file you sent me into my log, filtering with the SQL expression

COMMENT LIKE '*WWFF*'

+ works correctly. Does it not work for you?

73,

Dave, AA6YQ








Re: Duplicate log records to DXKeeper from JTDX

neil_zampella
 

How are you connecting the program with DXKeeper?  Are you using a bridge program?

Neil, KN3ILZ


Re: WSJT-X Time Sync--Request for Document Change

CSM&#92;(r&#92;) Gary Huber - AB9M
 

I've been using NTP and BKT Time Sync with a West Mountain Radio USB GPS Module (for those times when the internet link is down or not available) .

I know, belt and suspenders, but it keeps the computer clock in synch.

73, 
Gary ~ AB9M

From: DXLab@groups.io <DXLab@groups.io> on behalf of Joe Subich, W4TV <lists@...>
Sent: Thursday, December 24, 2020 8:31 PM
To: DXLab@groups.io <DXLab@groups.io>
Subject: Re: [DXLab] WSJT-X Time Sync--Request for Document Change
 

Dave,

My favorite reference on implementing the Meinberg NTP is:
   <https://www.satsignal.eu/ntp/setup.html>

Here is the application I use to monitor the NTP server performance:
<https://www.meinbergglobal.com/english/sw/ntp-server-monitor.htm>

73,

    ... Joe, W4TV


On 2020-12-24 8:47 PM, Dave AA6YQ wrote:
> * AA6YQ comments below
>
>> + Re "The Meinberg time application sets the internal Windows time mechanism to adjust the value of the tick, not the clock"
>>
>> + What is the difference between "the value of the tick" and "the clock"?
>
> normally a full implementation of the NTP protocol will slew the system clock frequency to guarantee that the clock is monotonic. SNTP implementations tend to simply step the clock now and again to force time synchronization. Audio streams are synchronized with the system clock, so discontinuities from a non-monotonic clock are likely to cause discontinuities in them.
>
> * So Meinberg's implementation of the full NTP protocol results in more frequent updates to the computer's clock that only move the clock forward in time, avoiding larger changes or "time reversals" that could prevent correct decoding of time-sensitive protocols like FT8 and FT4. Correct?
>
> * I tried installing Meinberg per the updated instructions. The installer complained that all was not well and instructed me to "check my event log". Wandering into the NTP/bin folder (a time warp back to command line interpreters), I managed to start the NTP server. How does one monitor the server's operation to confirm that it is behaving correctly?
>
>      73,
>
>                Dave, AA6YQ
>
>
>
>
>
>






Re: WSJT-X Time Sync--Request for Document Change

Dave AA6YQ
 

+ AA6YQ comments below

My favorite reference on implementing the Meinberg NTP is:
<https://www.satsignal.eu/ntp/setup.html>

Here is the application I use to monitor the NTP server performance:
<https://www.meinbergglobal.com/english/sw/ntp-server-monitor.htm>


+ Thanks, Joe! The first URL should be referenced by the Wiki article. The second provides the functionality I was expecting to see.

73,

Dave, AA6YQ


Re: WSJT-X Time Sync--Request for Document Change

Dave AA6YQ
 

@ more AA6YQ comments below

+ Re "The Meinberg time application sets the internal Windows time mechanism to adjust the value of the tick, not the clock"

+ What is the difference between "the value of the tick" and "the clock"?

normally a full implementation of the NTP protocol will slew the system clock frequency to guarantee that the clock is monotonic. SNTP implementations tend to simply step the clock now and again to force time synchronization. Audio streams are synchronized with the system clock, so discontinuities from a non-monotonic clock are likely to cause discontinuities in them.

* So Meinberg's implementation of the full NTP protocol results in more frequent updates to the computer's clock that only move the clock forward in time, avoiding larger changes or "time reversals" that could prevent correct decoding of time-sensitive protocols like FT8 and FT4. Correct?

Not necessarily. NTP clients should adjust the clock frequency, no the clock value. When starting up an NTP client can be configured to make step adjustments to quickly synchronize the clock with the elected remote time server, after that it will attempt to characterize the system clock drift and allow the clock to free run. If the clock is stable it may turn out that an NTP client will make less adjustments than an SNTP client, either way it will not step the clock backwards nor forwards in normal operations, just adjust the clock frequency.

@ Thanks, I understand now.

@ When I was designing minicomputers back in the 1970s, we used AC power zero crossings for long-term clock accuracy, since power companies ensured the correct number of zero crossings per day.


* I tried installing Meinberg per the updated instructions. The installer complained that all was not well and instructed me to "check my event log". Wandering into the NTP/bin folder (a time warp back to command line interpreters), I managed to start the NTP server. How does one monitor the server's operation to confirm that it is behaving correctly?

When you install the Meinberg NTP Client it should have added a "Quick NTP Status" start menu entry, it shows the current status of the group of time servers selected for synchronization.


@ It didn't.

The line with a '*' prefix is the currently elected server to synchronize with.

Here's a sample output:

Checking current status of NTP service with ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
-time.cloudflare 10.21.8.19 3 u 864 1024 377 18.870 19.749 8.220
-138.68.183.179 217.114.59.3 3 u 863 1024 375 20.199 22.219 5.218
+85.199.214.98 .GPS. 1 u 674 1024 277 20.325 21.871 3.905
-85.199.214.100 .GPS. 1 u 816 1024 377 21.069 22.056 6.667
*mail.classdesig .PPS. 1 u 345 512 377 19.377 12.428 6.712
+raspberrypi.cla .PPS. 1 u 898 512 376 22.690 14.646 10.550

In my case the selected server is my own GPS stratum 0 time server, it is showing my system is estimated as 12.428 milliseconds ahead with a clock jitter estimated at 6.712 milliseconds. This is my laptop on WiFi so synchronization is not as good as it could be with a wired Ethernet connection to the time server. I also have the uk.pool.ntp.org configured to select time servers for when I am away fro my local network.

@ There's an ntpstatus.bat in the NTP/Bin folder that invokes

ntpq -p,

which displays the above information.

@ Thanks!

73,

Dave, AA6YQ


Re: WSJT-X Time Sync--Request for Document Change

Joe Subich, W4TV
 

Dave,

My favorite reference on implementing the Meinberg NTP is:
<https://www.satsignal.eu/ntp/setup.html>

Here is the application I use to monitor the NTP server performance:
<https://www.meinbergglobal.com/english/sw/ntp-server-monitor.htm>

73,

... Joe, W4TV

On 2020-12-24 8:47 PM, Dave AA6YQ wrote:
* AA6YQ comments below

+ Re "The Meinberg time application sets the internal Windows time mechanism to adjust the value of the tick, not the clock"

+ What is the difference between "the value of the tick" and "the clock"?
normally a full implementation of the NTP protocol will slew the system clock frequency to guarantee that the clock is monotonic. SNTP implementations tend to simply step the clock now and again to force time synchronization. Audio streams are synchronized with the system clock, so discontinuities from a non-monotonic clock are likely to cause discontinuities in them.
* So Meinberg's implementation of the full NTP protocol results in more frequent updates to the computer's clock that only move the clock forward in time, avoiding larger changes or "time reversals" that could prevent correct decoding of time-sensitive protocols like FT8 and FT4. Correct?
* I tried installing Meinberg per the updated instructions. The installer complained that all was not well and instructed me to "check my event log". Wandering into the NTP/bin folder (a time warp back to command line interpreters), I managed to start the NTP server. How does one monitor the server's operation to confirm that it is behaving correctly?
73,
Dave, AA6YQ


Re: WSJT-X Time Sync--Request for Document Change

g4wjs
 

Hi Dave,

comments in line below.

On 25/12/2020 01:47, Dave AA6YQ wrote:
* AA6YQ comments below

+ Re "The Meinberg time application sets the internal Windows time mechanism to adjust the value of the tick, not the clock"

+ What is the difference between "the value of the tick" and "the clock"?
normally a full implementation of the NTP protocol will slew the system clock frequency to guarantee that the clock is monotonic. SNTP implementations tend to simply step the clock now and again to force time synchronization. Audio streams are synchronized with the system clock, so discontinuities from a non-monotonic clock are likely to cause discontinuities in them.

* So Meinberg's implementation of the full NTP protocol results in more frequent updates to the computer's clock that only move the clock forward in time, avoiding larger changes or "time reversals" that could prevent correct decoding of time-sensitive protocols like FT8 and FT4. Correct?
Not necessarily. NTP clients should adjust the clock frequency, no the clock value. When starting up an NTP client can be configured to make step adjustments to quickly synchronize the clock with the elected remote time server, after that it will attempt to characterize the system clock drift and allow the clock to free run. If the clock is stable it may turn out that an NTP client will make less adjustments than an SNTP client, either way it will not step the clock backwards nor forwards in normal operations, just adjust the clock frequency.

* I tried installing Meinberg per the updated instructions. The installer complained that all was not well and instructed me to "check my event log". Wandering into the NTP/bin folder (a time warp back to command line interpreters), I managed to start the NTP server. How does one monitor the server's operation to confirm that it is behaving correctly?

When you install the Meinberg NTP Client it should have added a "Quick NTP Status" start menu entry, it shows the current status of the group of time servers selected for synchronization. The line with a '*' prefix is the currently elected server to synchronize with.

Here's a sample output:

Checking current status of NTP service with ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
-time.cloudflare 10.21.8.19       3 u  864 1024  377   18.870   19.749   8.220
-138.68.183.179  217.114.59.3     3 u  863 1024  375   20.199   22.219   5.218
+85.199.214.98   .GPS.            1 u  674 1024  277   20.325   21.871   3.905
-85.199.214.100  .GPS.            1 u  816 1024  377   21.069   22.056   6.667
*mail.classdesig .PPS.            1 u  345  512  377   19.377   12.428   6.712
+raspberrypi.cla .PPS.            1 u  898  512  376   22.690   14.646  10.550

In my case the selected server is my own GPS stratum 0 time server, it is showing my system is estimated as 12.428 milliseconds ahead with a clock jitter estimated at 6.712 milliseconds. This is my laptop on WiFi so synchronization is not as good as it could be with a wired Ethernet connection to the time server. I also have the uk.pool.ntp.org configured to select time servers for when I am away fro my local network.

As an aside, my GPS time server (Raspberry Pi Model 3+ and GPS receiver with PPS output) is a member of the pool.ntp.org service. This service has many contributors around the Globe, the service monitors and grades contributors and only keeps them in the pool while they show consistent and accurate time. Here's the NTP peer status on the time server itself:

pi@raspberrypi:~ $ ntpq -p
     remote                                   refid      st t when poll reach   delay   offset   jitter
=======================================================================================================
*SHM(1)                                  .PPS.            0 l   20   64  377   0.0000  -0.0378   0.0005
-SHM(0)                                  .GPS.           10 l   58   64  377   0.0000 -103.226 108.6767
 uk.pool.ntp.org                         .POOL.          16 p    -   64    0   0.0000   0.0000   0.0019
 wallace                                 .STEP.          16 u    -  68m    0   0.0000   0.0000   0.0019
-time.rdg.uk.as44574.net                 225.250.232.207  3 u  473 1024    1  19.0613   0.1362   0.1744
-ns4.turbodns.co.uk                      90.187.99.165    2 u  126  128  153  23.3696   0.9894   0.3462
+time.cloudflare.com                     10.21.8.19       3 u   33   64  377  17.0019  -0.5259   0.1454
+183.ip-51-89-151.eu                     18.118.244.103   3 u   51   64  377  17.3613   0.4036   0.0892
-ntp1.exa-networks.co.uk                 185.134.196.169  2 u   66  128  137  24.8810  -0.7166   0.4960
-time.cloudflare.com                     10.21.8.19       3 u   92  128  377  17.4720  -0.6846   1.5002

You can see that it is estimated as 37.8 microseconds behind the received GPS PPS clock with a jitter estimated at 0.5 microseconds.


    73,

              Dave, AA6YQ



--
73

Bill

G4WJS.


Re: Capture Window Azimuth Rotor Control

Dave AA6YQ
 

+ AA6YQ comments below

Tell me what I am supposed to see. At this point, I can put ten different call signs in the call box. I can hit look up. I get all the stations information in the capture window (but) the SP and LP direction. DXV has all the station's information, lp and sp.

But "Az" in the capture window is whatever direction the antenna is pointing. The SP drop down is the same as the antenna. The LP drop down is the same as the antenna plus 180 degrees. There is absolutely nothing in the "Az' window or the the drop downs that changes when I change call signs in the capture window.

+ Do you have DXView configured to rotate a directional antenna? If so, what boxes are checked on the "Direct Acceptance by Band" panel on DXView's Configuration window's "Rotator Control" tab?

+ On DXView's Configuration window's "Rotator Control" tab, do you have the "Report computed short path heading when disabled or on unsupported band" box checked?

+ On DXKeeper's Configuration window's Defaults tab, do you have the "Antenna Path" selector set to 'S'?


+ Unless you have DXKeeper configured to control a directional antenna, and are clicking DXView's SP or LP buttons to rotate that antenna, DXView doesn't know whether your directional antenna is pointed towards the short path or the long path. Configuring DXKeeper to assume "short path" is the best that can be done; when logging a QSO via the long path, change the Capture window's path selector to L before logging the QSO, or correct the logged path in the Propagation panel on the "Log QSOs" tab of DXKeeper's Main window after logging the QSO.

73,

Dave, AA6YQ


Re: WSJT-X Time Sync--Request for Document Change

Dave AA6YQ
 

* AA6YQ comments below

+ Re "The Meinberg time application sets the internal Windows time mechanism to adjust the value of the tick, not the clock"

+ What is the difference between "the value of the tick" and "the clock"?
normally a full implementation of the NTP protocol will slew the system clock frequency to guarantee that the clock is monotonic. SNTP implementations tend to simply step the clock now and again to force time synchronization. Audio streams are synchronized with the system clock, so discontinuities from a non-monotonic clock are likely to cause discontinuities in them.

* So Meinberg's implementation of the full NTP protocol results in more frequent updates to the computer's clock that only move the clock forward in time, avoiding larger changes or "time reversals" that could prevent correct decoding of time-sensitive protocols like FT8 and FT4. Correct?

* I tried installing Meinberg per the updated instructions. The installer complained that all was not well and instructed me to "check my event log". Wandering into the NTP/bin folder (a time warp back to command line interpreters), I managed to start the NTP server. How does one monitor the server's operation to confirm that it is behaving correctly?

73,

Dave, AA6YQ


Re: Capture Window Azimuth Rotor Control

wb6bee
 

Dave

Tell me what I am supposed to see.    At this point, I can put ten different call signs in the call box.  I can hit look up.   I get all the stations information in the capture window (but) the SP and LP direction.   DXV has all the station's information, lp and sp.

But "Az" in the capture window is whatever direction the antenna is pointing.    The SP drop down is the same as the antenna.  The LP drop down is the same as the antenna plus 180 degrees.    There is absolutely nothing in the "Az' window or the the drop downs that changes when I change call signs in the capture window.

Christmas eve, we can pick this up later

Have a great Christmas, Dave and thank you for what you have done

Don


Re: WSJT-X Time Sync--Request for Document Change

g4wjs
 

On 25/12/2020 01:02, Dave AA6YQ wrote:
+ Re "The Meinberg time application sets the internal Windows time mechanism to adjust the value of the tick, not the clock"

+ What is the difference between "the value of the tick" and "the clock"?

73,

Dave, AA6YQ
Hi Dave,

normally a full implementation of the NTP protocol will slew the system clock frequency to guarantee that the clock is monotonic. SNTP implementations tend to simply step the clock now and again to force time synchronization. Audio streams are synchronized with the system clock, so discontinuities from a non-monotonic clock are likely to cause discontinuities in them.



--
73

Bill

G4WJS.


Re: WSJT-X Time Sync--Request for Document Change

Dave AA6YQ
 

+ AA6YQ comments below

On Thu, Dec 24, 2020 at 2:57 PM w6de <v8dave@...> wrote:

Dave and group, in this WIKI article:

http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTA
lert

it states:

If you aren't already running an application that synchronizes your computer clock with an internet-accessible time standard, install one and initiate it:

Dimension 4

Meinberg

Net Time

I believe this should be re-written as follows:

If you aren't already running an application that synchronizes your computer clock with an internet-accessible time standard; download the Meinberg software and run it.



The Meinberg software can be obtained free from: the Meinberg Software Download web site. On the left side select NTP for Windows. This will take you to the NTP for Windows XP and Newer, with IPv6 support web page. Click to download the highlighted ntp #version.exe file. This file will work for both 32 bit and 64 bit version of Windows. Note the web site comment below the download regarding Visual Studio Redistributable package. More information about the Meinberg installation is available further down the web page.
If we're updating that page, it should really refer to the software as "Meinberg NTP [for Windows]". Meinberg is a company. The NTP software for Windows is just one of their products.


You may select a time server for Meinberg to work with from one of these sources:

https://tf.nist.gov/tf-cgi/servers.cgi

https://timetoolsltd.com/information/public-ntp-server/

The second site provides time server locations WorldWide.
I would strongly suggest using a server pool (https://www.ntppool.org/en/), rather than individual servers.
Meinberg NTP supports this. When I install Meinberg NTP, the only non-default that I specify is to use the US server pool. I then forget all about NTP, since it "just works", always.

[snip]

Finally, It may be appropriate to write a separate WIKI article about Time, Clocks and Computers for the WIKI instead of sticking all this into the Getting Started with K1JTModes With JTAlert WIKI article.
+ If someone sends me text for a new Wiki article, I will be happy to format it and add it to "Getting Started with DXLab" under your byline(s), and then modify the two "Getting Started with K1JT modes" articles to reference it.

73,

Dave, AA6YQ


Re: WSJT-X Time Sync--Request for Document Change

iain macdonnell - N6ML
 

On Thu, Dec 24, 2020 at 5:02 PM Dave AA6YQ <aa6yq@...> wrote:
+ Re "The Meinberg time application sets the internal Windows time mechanism to adjust the value of the tick, not the clock"

+ What is the difference between "the value of the tick" and "the clock"?
https://kb.meinbergglobal.com/kb/time_sync/ntp/ntp_and_windows_history

Other "clock sync" applications may periodically (e.g. once a day, or
hour) set the clock to the correct time, which causes a sudden jump.

73,

~iain / N6ML


Re: WSJT-X Time Sync--Request for Document Change

iain macdonnell - N6ML
 

On Thu, Dec 24, 2020 at 2:57 PM w6de <v8dave@...> wrote:

Dave and group, in this WIKI article:

http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert

it states:

“If you aren't already running an application that synchronizes your computer clock with an internet-accessible time standard, install one and initiate it:

· Dimension 4

· Meinberg

· Net Time”

I believe this should be re-written as follows:

If you aren't already running an application that synchronizes your computer clock with an internet-accessible time standard; download the Meinberg software and run it.



The Meinberg software can be obtained free from: the Meinberg Software Download web site. On the left side select NTP for Windows. This will take you to the NTP for Windows XP and Newer, with IPv6 support web page. Click to download the highlighted ntp #version.exe file. This file will work for both 32 bit and 64 bit version of Windows. Note the web site comment below the download regarding Visual Studio Redistributable package. More information about the Meinberg installation is available further down the web page.
If we're updating that page, it should really refer to the software as
"Meinberg NTP [for Windows]". Meinberg is a company. The NTP software
for Windows is just one of their products.


You may select a time server for Meinberg to work with from one of these sources:

https://tf.nist.gov/tf-cgi/servers.cgi

https://timetoolsltd.com/information/public-ntp-server/

The second site provides time server locations WorldWide.
I would strongly suggest using a server pool
(https://www.ntppool.org/en/), rather than individual servers.
Meinberg NTP supports this. When I install Meinberg NTP, the only
non-default that I specify is to use the US server pool. I then forget
all about NTP, since it "just works", always.

[snip]

Finally, It may be appropriate to write a separate WIKI article about Time, Clocks and Computers for the WIKI instead of sticking all this into the “Getting Started with K1JTModes With JTAlert” WIKI article.
Agreed.

73,

~iain / N6ML


Re: WSJT-X Time Sync--Request for Document Change

Dave AA6YQ
 

+ AA6YQ comments below

Dave and group, in this WIKI article:

http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert

it states:

“If you aren't already running an application that synchronizes your computer clock with an internet-accessible time standard, install one and initiate it:

· Dimension 4 <http://www.thinkman.com/dimension4/download.htm>

· Meinberg <https://www.meinbergglobal.com/english/sw/ntp.htm>

· Net Time <http://www.timesynctool.com/> ”

I believe this should be re-written as follows:

If you aren't already running an application that synchronizes your computer clock with an internet-accessible time standard; download the Meinberg software and run it.

The Meinberg software can be obtained free from: the Meinberg Software Download web site. On the left side select NTP for Windows. This will take you to the NTP for Windows XP and Newer, with IPv6 support web page. Click to download the highlighted ntp #version.exe file. This file will work for both 32 bit and 64 bit version of Windows. Note the web site comment below the download regarding Visual Studio Redistributable package. More information about the Meinberg installation is available further down the web page. You may select a time server for Meinberg to work with from one of these sources:

https://tf.nist.gov/tf-cgi/servers.cgi

https://timetoolsltd.com/information/public-ntp-server/

The second site provides time server locations WorldWide.

The Meinberg time application sets the internal Windows time mechanism to adjust the value of the tick, not the clock; so there are no radical shifts in the clock which can cause issues in processes. This includes WSJT-X timing (both TX and tone timing).

W6DE’s comments: I found out about the tick vs clock Issue with WSJT-X and the Meinberg solution in a discussion with Rick NK7I. I also believe Joe W4TV has pointed out this issue in the past too. Although, I didn’t ‘get it’ until my discussion with Rick, NK7I.

Dimension 4 and Net Time fail to adjust the ticks. I had previously been using NetTime with my own GPS Disciplined Time Server. I now use Meinberg synced to my GPS Time Server.

Finally, It may be appropriate to write a separate WIKI article about Time, Clocks and Computers for the WIKI instead of sticking all this into the “Getting Started with K1JTModes With JTAlert” WIKI article.

+ Re "The Meinberg time application sets the internal Windows time mechanism to adjust the value of the tick, not the clock"

+ What is the difference between "the value of the tick" and "the clock"?

73,

Dave, AA6YQ


Re: Capture Window Azimuth Rotor Control

Dave AA6YQ
 

+ AA6YQ comments below

" There's a "Report computed short path heading when disabled or on unsupported band" option on the "Rotator Control" tab of DXView's Configuration window that if enabled causes DXView to report the computed short path heading to DXKeeper's Capture window."

When I check this box there is nothing transmitted to the "az" box on the capture window. The antenna is set at 40 degrees and I can put ten different stations and "az" stays at 40 degrees. Nothing appears in the capture window related to the station. The only thing in the capture window is whatever the antenna is then pointing.

+ Type a callsign into the Capture window's call box, and then strike the Enter or Tab key.

73,

Dave, AA6YQ


Re: Capture Window Azimuth Rotor Control

Dave AA6YQ
 

+ AA6YQ comments below

"other" is notably missing from the "control explanation" (tooltip) for the path drop-down.

+ Corrected in the next version of DXKeeper. Thanks!

73,

Dave, AA6YQ


Re: Capture Window Azimuth Rotor Control

iain macdonnell - N6ML
 

On Thu, Dec 24, 2020 at 4:04 PM wb6bee <wb6bee@...> wrote:

This is not working for me

" There's a "Report computed short path heading when disabled or on unsupported band" option on the "Rotator Control" tab of DXView's Configuration window that if enabled causes DXView to report the computed short path heading to DXKeeper's Capture window."

When I check this box there is nothing transmitted to the "az" box on the capture window. The antenna is set at 40 degrees and I can put ten different stations and "az" stays at 40 degrees. Nothing appears in the capture window related to the station. The only thing in the capture window is whatever the antenna is then pointing.
Is rotator control disabled, or are you on a band for which rotator
control is not supported? If not, that option does not apply (IIUC)


This link says the page doesn't exist

<https://www.dxlabsuite.com/dxlabwiki/QSODistance>;
You picked up a '>' by accident - the link is:

https://www.dxlabsuite.com/dxlabwiki/QSODistance

73,

~iain / N6ML


Re: Capture Window Azimuth Rotor Control

wb6bee
 

This is not working for me

" There's a "Report computed short path heading when disabled or on unsupported band" option on the "Rotator Control" tab of DXView's Configuration window that if enabled causes DXView to report the computed short path heading to DXKeeper's Capture window."

When I check this box there is nothing transmitted to the "az" box on the capture window.  The antenna is set at 40 degrees and I can put ten different stations and "az" stays at 40 degrees.   Nothing appears in the capture window related to the station.  The only thing in the capture window is whatever the antenna is then pointing.

This link says the page doesn't exist

<https://www.dxlabsuite.com/dxlabwiki/QSODistance>;


Don 
WB6BEE



Re: Capture Window Azimuth Rotor Control

iain macdonnell - N6ML
 

On Thu, Dec 24, 2020 at 1:53 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

In the Capture window, the "az" field shows the current azimuth setting on the rotor. Next to that is a drop down menu that has "S", "L", "G" and "O". Not sure what the "O" stands for, but the others are Short path, long path and Gray line, all supposed to be the antenna direction to the other QSO partners location.

+ As described in

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm#sp%20or%20lp>

+ "O" in the "Antenna Path" item (abbreviated as "path" in the Capture window), is an abbreviation for "other". You might employ this to record a skew path.
"other" is notably missing from the "control explanation" (tooltip)
for the path drop-down.

73,

~iain / N6ML

12821 - 12840 of 211155