Date   

Re: Single QSO - Multiple Grid Confirmation

Dave AA6YQ
 

Thanks for testing and the report, Robie!

73,

Dave, AA6YQ

-----Original Message-----
From: Robie Elms [mailto:ruler55@...]
Sent: Wednesday, June 24, 2020 12:47 PM
To: Dave AA6YQ
Subject: Re: [DXLab] Single QSO - Multiple Grid Confirmation

Dave,

The new version of DXKeeper works properly.

Thanks for the quick resolution of the issue.

Robie - AJ4F


Re: how to setup dxkeeper for arrl fd?

Dave AA6YQ
 

+ AA6YQ comments below

how do I setup up dxkeeper for arrl field day thanks in

+ See

<https://www.dxlabsuite.com/dxlabwiki/ARRLFieldDay>

73,

Dave, AA6YQ


Re: Single QSO - Multiple Grid Confirmation

Scott Stembaugh
 

My experience was, I had only logged W7GJ with grid DN56.  The LotW report showed that he had also confirmed on 3 other grids.  I updated the QSO with those other grids, did an LotW Update on the QSO, and they all came back confirmed.  After the initial email from AJ4F I double checked RAT and it showed all 4 confirmed.

Just info for a data point.

--scott N9LJX


On Wed, Jun 24, 2020 at 12:01 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Thanks for the suggestion, however there is no change.

I looked at the LoTW entry  and see that he used 6 digit grid locators i.e. DN66XA.  I had also entered grids in the same fashion.  I experimented by changing two of my DXKeeper entries to 2 digit locators i.e. DN66 & DN65 then did an Update from LoTW and now DXKeeper indicates those grids are confirmed.  However, the remaining grid DN56 is indicated as Worked.  Grid DN55 was indicated as confirmed initially.  So some issue remains either with LoTW or DXKeeper. 

+ That's the result of a defect in multiple-grid confirmations recently reported by Iain N6ML that is corrected in the next (but not yet publicly released) version of DXKeeper. I've sent you this new version; please let me know how it goes.

        73,

               Dave, AA6YQ


On Wed, Jun 24, 2020 at 8:48 AM Seb <w4as@...> wrote:


        Select the QSO you had with W7GJ in DXKeeper, and right click, then select Update from LotW.  Lance has solved the issue he had with the initial upload and you should now see all the grids confirmed.

        73 de Sebastian, W4AS






                On Jun 24, 2020, at 9:21 AM, Robie <ruler55@...> wrote:

                Dave,

                On 6/20/2020 I worked W7GJ on 6 M FT8.  He was located at the junction of 4 grids DN55, DN56, DN65 & DN66, a really nice catch for a grid chaser!  I logged him with grids 1-4 containing the respective grids. On 6/23/2020 I received confirmation from W7GJ for the QSO in LoTW.  I performed the Sync LoTW QSLs action in DXKeeper and received a confirmation (LoTW rcvd = Y) for the QSO.  However, DXKeeper Realtime Award Tracking indicated the Grid  DN55 is confirmed (which I expected) but indicates that Grids DN56, DN65 and DN66 have been worked but not confirmed. In LoTW the confirmation lists all 4 grids as being confirmed. 

                I performed a DXKeeper recompute and saw no change.  I then performed an Update from LoTW action followed by a Recompute and again no change.

                I could not find any information in the DXLabs Wiki that helped me address this situation. 

                What steps should I take at this point?

                Robie - AJ4F






Re: Single QSO - Multiple Grid Confirmation

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for the suggestion, however there is no change.

I looked at the LoTW entry and see that he used 6 digit grid locators i.e. DN66XA. I had also entered grids in the same fashion. I experimented by changing two of my DXKeeper entries to 2 digit locators i.e. DN66 & DN65 then did an Update from LoTW and now DXKeeper indicates those grids are confirmed. However, the remaining grid DN56 is indicated as Worked. Grid DN55 was indicated as confirmed initially. So some issue remains either with LoTW or DXKeeper.

+ That's the result of a defect in multiple-grid confirmations recently reported by Iain N6ML that is corrected in the next (but not yet publicly released) version of DXKeeper. I've sent you this new version; please let me know how it goes.

73,

Dave, AA6YQ

On Wed, Jun 24, 2020 at 8:48 AM Seb <w4as@...> wrote:


Select the QSO you had with W7GJ in DXKeeper, and right click, then select Update from LotW. Lance has solved the issue he had with the initial upload and you should now see all the grids confirmed.

73 de Sebastian, W4AS






On Jun 24, 2020, at 9:21 AM, Robie <ruler55@...> wrote:

Dave,

On 6/20/2020 I worked W7GJ on 6 M FT8. He was located at the junction of 4 grids DN55, DN56, DN65 & DN66, a really nice catch for a grid chaser! I logged him with grids 1-4 containing the respective grids. On 6/23/2020 I received confirmation from W7GJ for the QSO in LoTW. I performed the Sync LoTW QSLs action in DXKeeper and received a confirmation (LoTW rcvd = Y) for the QSO. However, DXKeeper Realtime Award Tracking indicated the Grid DN55 is confirmed (which I expected) but indicates that Grids DN56, DN65 and DN66 have been worked but not confirmed. In LoTW the confirmation lists all 4 grids as being confirmed.

I performed a DXKeeper recompute and saw no change. I then performed an Update from LoTW action followed by a Recompute and again no change.

I could not find any information in the DXLabs Wiki that helped me address this situation.

What steps should I take at this point?

Robie - AJ4F


how to setup dxkeeper for arrl fd?

Craig Wallen
 

how do I setup up dxkeeper for arrl field day thanks in advanced


Re: Single QSO - Multiple Grid Confirmation

Robie
 

Seb,

Thanks for the suggestion, however there is no change.

I looked at the LoTW entry  and see that he used 6 digit grid locators i.e. DN66XA.  I had also entered grids in the same fashion.  I experimented by changing two of my DXKeeper entries to 2 digit locators i.e. DN66 & DN65 then did an Update from LoTW and now DXKeeper indicates those grids are confirmed.  However, the remaining grid DN56 is indicated as Worked.  Grid DN55 was indicated as confirmed initially.  So some issue remains either with LoTW or DXKeeper.  

Robie - AJ4F

On Wed, Jun 24, 2020 at 8:48 AM Seb <w4as@...> wrote:
Select the QSO you had with W7GJ in DXKeeper, and right click, then select Update from LotW.  Lance has solved the issue he had with the initial upload and you should now see all the grids confirmed.

73 de Sebastian, W4AS




On Jun 24, 2020, at 9:21 AM, Robie <ruler55@...> wrote:

Dave,

On 6/20/2020 I worked W7GJ on 6 M FT8.  He was located at the junction of 4 grids DN55, DN56, DN65 & DN66, a really nice catch for a grid chaser!  I logged him with grids 1-4 containing the respective grids. On 6/23/2020 I received confirmation from W7GJ for the QSO in LoTW.  I performed the Sync LoTW QSLs action in DXKeeper and received a confirmation (LoTW rcvd = Y) for the QSO.  However, DXKeeper Realtime Award Tracking indicated the Grid  DN55 is confirmed (which I expected) but indicates that Grids DN56, DN65 and DN66 have been worked but not confirmed. In LoTW the confirmation lists all 4 grids as being confirmed.  

I performed a DXKeeper recompute and saw no change.  I then performed an Update from LoTW action followed by a Recompute and again no change.

I could not find any information in the DXLabs Wiki that helped me address this situation.  

What steps should I take at this point?

Robie - AJ4F


Re: Single QSO - Multiple Grid Confirmation

Seb
 

Select the QSO you had with W7GJ in DXKeeper, and right click, then select Update from LotW.  Lance has solved the issue he had with the initial upload and you should now see all the grids confirmed.

73 de Sebastian, W4AS




On Jun 24, 2020, at 9:21 AM, Robie <ruler55@...> wrote:

Dave,

On 6/20/2020 I worked W7GJ on 6 M FT8.  He was located at the junction of 4 grids DN55, DN56, DN65 & DN66, a really nice catch for a grid chaser!  I logged him with grids 1-4 containing the respective grids. On 6/23/2020 I received confirmation from W7GJ for the QSO in LoTW.  I performed the Sync LoTW QSLs action in DXKeeper and received a confirmation (LoTW rcvd = Y) for the QSO.  However, DXKeeper Realtime Award Tracking indicated the Grid  DN55 is confirmed (which I expected) but indicates that Grids DN56, DN65 and DN66 have been worked but not confirmed. In LoTW the confirmation lists all 4 grids as being confirmed.  

I performed a DXKeeper recompute and saw no change.  I then performed an Update from LoTW action followed by a Recompute and again no change.

I could not find any information in the DXLabs Wiki that helped me address this situation.  

What steps should I take at this point?

Robie - AJ4F
_._,_._,_


Single QSO - Multiple Grid Confirmation

Robie
 

Dave,

On 6/20/2020 I worked W7GJ on 6 M FT8.  He was located at the junction of 4 grids DN55, DN56, DN65 & DN66, a really nice catch for a grid chaser!  I logged him with grids 1-4 containing the respective grids. On 6/23/2020 I received confirmation from W7GJ for the QSO in LoTW.  I performed the Sync LoTW QSLs action in DXKeeper and received a confirmation (LoTW rcvd = Y) for the QSO.  However, DXKeeper Realtime Award Tracking indicated the Grid  DN55 is confirmed (which I expected) but indicates that Grids DN56, DN65 and DN66 have been worked but not confirmed. In LoTW the confirmation lists all 4 grids as being confirmed.  

I performed a DXKeeper recompute and saw no change.  I then performed an Update from LoTW action followed by a Recompute and again no change.

I could not find any information in the DXLabs Wiki that helped me address this situation.  

What steps should I take at this point?

Robie - AJ4F


Re: ADIF file write on shutdown - request.

Jim - KR9U
 

Carl,

 

No, I use digital [WSJT-x] as well as CW, SSB.

For digital, I have JTAlert logging to DXK. 

I have Grid Tracker reading a manually exported ADIF file created in DXK that GT reads on startup.

I populate JTAlert’s log from DXK.

 

Jim – KR9U

 

 

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Carl - WC4H via groups.io
Sent: Tuesday, June 23, 2020 2:21 PM
To: DXLab@groups.io
Subject: Re: [DXLab] ADIF file write on shutdown - request.

 

Hi Jim.

I'm assuming you're working digital modes on WSJT-X.  If you want to mix in your SSB & CW QSO's, you'll need to do that manually.

If you want GridTracker to use the WSJT-X wsjtx_log.adi file, do the following On the GridTracker Setup under the Logging Tab:
In the first row where the Source/Sync is "GridTracker" chek the Startup Box.
In the next row where the Source/Sync is Local Files(s) check the Startup Box, click on Add and navigate to the WSJT-X file wsjtx_log.adi.

If you want Grid Tracker to Log the QSO to DXKeeper, scroll down the page to the Source/Sync "DXKeeper and check the Log box.

If you're running GridTracker, then don't run JTAlerts.

GridTracker will enter each QSO into DXKeeper and any of the other logs you specify as does JTAlerts.
GirdTracker can also give voice alerts but they are setup differently than in JTAlerts.

NOTE:  If you click on the "Log" Column in the first line, you will get a double entry in the wsjtx_log.adi file (one frorm wsjtx and one from GridTracker)..

If you're going to upload to LoTW, Clublog or eQSL you may want to do that via DXKeeper so that it can keep all the pertinent info for you award tracking.

73.
Carl - WC4H


Re: ADIF file write on shutdown - request.

Carl - WC4H
 

Hi Jim.

I'm assuming you're working digital modes on WSJT-X.  If you want to mix in your SSB & CW QSO's, you'll need to do that manually.

If you want GridTracker to use the WSJT-X wsjtx_log.adi file, do the following On the GridTracker Setup under the Logging Tab:
In the first row where the Source/Sync is "GridTracker" chek the Startup Box.
In the next row where the Source/Sync is Local Files(s) check the Startup Box, click on Add and navigate to the WSJT-X file wsjtx_log.adi.

If you want Grid Tracker to Log the QSO to DXKeeper, scroll down the page to the Source/Sync "DXKeeper and check the Log box.

If you're running GridTracker, then don't run JTAlerts.

GridTracker will enter each QSO into DXKeeper and any of the other logs you specify as does JTAlerts.
GirdTracker can also give voice alerts but they are setup differently than in JTAlerts.

NOTE:  If you click on the "Log" Column in the first line, you will get a double entry in the wsjtx_log.adi file (one frorm wsjtx and one from GridTracker)..

If you're going to upload to LoTW, Clublog or eQSL you may want to do that via DXKeeper so that it can keep all the pertinent info for you award tracking.

73.
Carl - WC4H


Re: User defined control question

Dave AA6YQ
 

+ AA6YQ comments below

is is possible to "comment out" a line is the command section?

Such as is done is a bat file?

It would assist in experimentation with commands.

+ Copy the command to its associated Note, and leave the command blank.

73,

Dave, AA6YQ


User defined control question

d_ziolkowski
 

Dave-
is is possible to "comment out" a line is the command section?

Such as is done is a bat file?

It would assist in experimentation with commands. 
Thanks

Dan KC2STA


Re: ADIF file write on shutdown - request.

Jim - KR9U
 

Thanks Dave,

 

Jim – KR9U

 

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Monday, June 22, 2020 7:22 PM
To: DXLab@groups.io
Subject: Re: [DXLab] ADIF file write on shutdown - request.

 

+ AA6YQ comments below

I have been doing the ADIF export every time before closing DXK, I do like many of the GT features, therefore, I was just asking if an option to automatically write the ADIF file on DXK exit would be possible.

+ I do not want to encourage the use of ADIF files containing every logged QSO for interoperation. If the developer of GridTracker would like to directly interoperate with DXLab, as more than 30 other application developers have done, I'll be happy to provide assistance.

       73,

               Dave, AA6YQ


Re: RTTY FSK ... again!

Rick Boswell
 

On Mon, Jun 22, 2020 at 05:45 PM, Jeff AC0C wrote:
other than the technical challenge of it
This. Have had RTTY AFSK working well for some time. Thought I would tackle FSK. Forced me to learn more about 7610/DXL/WW/MMTTY/EXTFSK64 etc. When I got started in amateur radio in the fifties as a teen, RTTY with electromechanical gear was very appealing but I never got to it before my temporary retirement of 50+ years from ham radio. I doubt that I will use RTTY significantly in either AFSK or FSK modes going forward as the charm is not there without a clattering teleprinter, and, RTTY seems to be predominantly used for contests these day, with average transmission times of a second or two. But then I may have to develop an app that adds teleprinter sounds to MMTTY somewhat like the synthetic exhaust sound being played through the audio system in modern performance cars. ;-)

Rick
K8EZB


Re: RTTY FSK ... again!

Jeff AC0C
 

Rick,

Something to consider.  If the 7610 works FB on FT8 (or PSK31, other "sound card" modes), then it should work fine as well on RTTY/AFSK.  There's no actual benefit to FSK with that rig.  And depending on the implementation, somewhere from no to potentially significant weak signal degradation by the guy trying to copy you on the other end. 

Opinions vary, but if your setup is working well under AFSK, there's no reason to try for FSK - other than the technical challenge of it.  I run a bit of RTTY myself and you may consider this as in the "good advice" category, as far as internet advice goes.

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com


On 6/22/20 7:30 PM, Rick Boswell wrote:

Found one setting in the 7610 menus to be incorrect. My fault but the (Icom) documentation was pretty vague. Anyhow, in monitoring my RTTY FSK  transmission on a separate receiver or with the 7610 monitor I am now hearing what sounds like a proper RTTY signal. With virtually no RTTY signals on 20m today, was unable to make a contact to confirm operation. One issue I dont yet understand: in RTTY FSK mode I am seeing ALC level at about 75% of the red zone on the 7610. Not sure what to expect for ALC in FSK mode; the Icom manuals seem to be silent on this topic..

Rick
K8EZB


Re: RTTY FSK ... again!

Dave AA6YQ
 

+ AA6YQ comments below

Found one setting in the 7610 menus to be incorrect. My fault but the (Icom) documentation was pretty vague. Anyhow, in monitoring my RTTY FSK transmission on a separate receiver or with the 7610 monitor I am now hearing what sounds like a proper RTTY signal. With virtually no RTTY signals on 20m today, was unable to make a contact to confirm operation.

+ Great! Perhaps Field Day will bring out a few RTTY ops this coming weekend.

73,

Dave, AA6YQ


Re: RTTY FSK ... again!

Rick Boswell
 

Found one setting in the 7610 menus to be incorrect. My fault but the (Icom) documentation was pretty vague. Anyhow, in monitoring my RTTY FSK  transmission on a separate receiver or with the 7610 monitor I am now hearing what sounds like a proper RTTY signal. With virtually no RTTY signals on 20m today, was unable to make a contact to confirm operation. One issue I dont yet understand: in RTTY FSK mode I am seeing ALC level at about 75% of the red zone on the 7610. Not sure what to expect for ALC in FSK mode; the Icom manuals seem to be silent on this topic..

Rick
K8EZB


Re: ADIF file write on shutdown - request.

Dave AA6YQ
 

+ AA6YQ comments below

I have been doing the ADIF export every time before closing DXK, I do like many of the GT features, therefore, I was just asking if an option to automatically write the ADIF file on DXK exit would be possible.

+ I do not want to encourage the use of ADIF files containing every logged QSO for interoperation. If the developer of GridTracker would like to directly interoperate with DXLab, as more than 30 other application developers have done, I'll be happy to provide assistance.

       73,

               Dave, AA6YQ


Re: ADIF file write on shutdown - request.

Jim - KR9U
 

Hi Dave,

I have been doing the ADIF export every time before closing DXK, I do like many of the GT features, therefore, I was just asking if an option to automatically write the ADIF file on DXK exit would be possible.

Jim - KR9U

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Monday, June 22, 2020 6:01 PM
To: DXLab@groups.io
Subject: Re: [DXLab] ADIF file write on shutdown - request.

+ AA6YQ comments below

As I'm working 6 meters this season, I started using the GridTracker https://tagloomis.com/grid-tracker/ program as an addition to WSJT/JTAlert and PSK Reporter. I know, right?
Grid Tracker must read an ADIF file to keep current on displayed grids worked/confirmed, which it can do on startup which is configured in the setup optoins.
I don't believe it is possible for Grid Tracker to read a DXKeeper log.
Could a simple option to create a standard ADIF be added to DXKeeper to accomplish this?

+ You can do that now using the "Export QSOs" tab on DXKeeper's Main window:

<https://www.dxlabsuite.com/dxlabwiki/QSOExport>

+ You might also review this article:

<https://www.dxlabsuite.com/dxlabwiki/GridPlottingDXAtlas>

+ DX Atlas is not free, but you'll be able to view your grid progress without exporting a new ADIF file each time you work or confirm a new grid.

73,

Dave, AA6YQ


Re: ADIF file write on shutdown - request.

Dave AA6YQ
 

+ AA6YQ comments below

As I'm working 6 meters this season, I started using the GridTracker https://tagloomis.com/grid-tracker/ program as an addition to WSJT/JTAlert and PSK Reporter. I know, right?
Grid Tracker must read an ADIF file to keep current on displayed grids worked/confirmed, which it can do on startup which is configured in the setup optoins.
I don't believe it is possible for Grid Tracker to read a DXKeeper log.
Could a simple option to create a standard ADIF be added to DXKeeper to accomplish this?

+ You can do that now using the "Export QSOs" tab on DXKeeper's Main window:

<https://www.dxlabsuite.com/dxlabwiki/QSOExport>

+ You might also review this article:

<https://www.dxlabsuite.com/dxlabwiki/GridPlottingDXAtlas>

+ DX Atlas is not free, but you'll be able to view your grid progress without exporting a new ADIF file each time you work or confirm a new grid.

73,

Dave, AA6YQ