Date   

Re: Correcting the GT logbook

Dave AA6YQ
 

+ AA6YQ comments below
I made a mistake in serted some incorrect data in the log window of WSJTX that pops up after a successful QSO.  That informaton got passed along to QRZ, LOTW and eQSL as well as showing on the Grid Tracker logbook.  I have corrected QRZ and am not too concerned about LOTW and eQSL but I would like to correct the Grid Square in the GT Logbook.  So my question is - Is there any way to edit the GT logbook entries?

+ What is a "GT Logbook"?

      73,

           Dave, AA6YQ


Using Ethernet to communicate with equipment

Dave / NR1DX
 

All

I am struggling to move to the "next level" of passing information from DXLab to various pieces of hardware via an Ethernet connection.

My problem is not with DXLab per-se but rather that much of the documentation (from  both  DXLab and the hardware manufacturers) assumes the user knows might actually know something about Ethernet communications to begin with.... which I dont . I dont even know what half the terms mean let alone the intricacies of how to use them ....help

Can someone direct me to a site that is HAMRADIO ETHERNET FOR DUMMIES. What is a UDP?  what is an IP address and when and why does it need to be static and when does in need to be dynamic. What is a NET MASK and and why do I care? etc etc etc.

Dave
NR1DX
manuals@...
--
Dave Manuals@... www.ArtekManuals.com

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Correcting the GT logbook

WALTDEWS@...
 

I made a mistake in serted some incorrect data in the log window of WSJTX that pops up after a successful QSO.  That informaton got passed along to QRZ, LOTW and eQSL as well as showing on the Grid Tracker logbook.  I have corrected QRZ and am not too concerned about LOTW and eQSL but I would like to correct the Grid Square in the GT Logbook.  So my question is - Is there any way to edit the GT logbook entries?


Re: Telnet Access to IOTA Spots

Dave AA6YQ
 

# more AA6YQ comments below

Is there a telnet address for IOTA spots so I can add them to SpotCollector like I do SOTA?

+ Are you asking if there is a DXCluster that is dedicated to IOTA spots?
++ Yes, I was looking for a telnet access to the IOTA cluster, I should ask on the IOTA forum.  Just thought someone here might know.  

# I'm not aware of there being a dedicated IOTA cluster, but if you find one, please post the particulars here. Thanks!

         73,

              Dave, AA6YQ

 


+ SpotCollector identifies and extracts IOTA tags in the spot notes of all spot sources; these appear in the Spot Database's IOTA field. Today, for example, EA6/EI6DX is active from EU-004. SOTA and POTA tags are similarly identified and extracted.
++ This only works if someone posts a spot with the IOTA tag.  I worked two islands last night that were spotted on RBN and I didn't know they were islands until after I looked them up.


Re: Telnet Access to IOTA Spots

 

+ AA6YQ comments below

Is there a telnet address for IOTA spots so I can add them to SpotCollector like I do SOTA?

+ Are you asking if there is a DXCluster that is dedicated to IOTA spots?
++ Yes, I was looking for a telnet access to the IOTA cluster, I should ask on the IOTA forum.  Just thought someone here might know.  

+ SpotCollector identifies and extracts IOTA tags in the spot notes of all spot sources; these appear in the Spot Database's IOTA field. Today, for example, EA6/EI6DX is active from EU-004. SOTA and POTA tags are similarly identified and extracted.
++ This only works if someone posts a spot with the IOTA tag.  I worked two islands last night that were spotted on RBN and I didn't know they were islands until after I looked them up.  


Re: Group date change

Dave AA6YQ
 

+ AA6YQ comments below
Yes, immediately after I sent my last email to you I realized what I had done wrong and corrected it. Fortunately, I did back up the log before I'd started anything.  I used +1d and not +24hr but I would assume that was ok. 
+ Yes, that's fine too.
It seemed to work.

+ Good!

     73,

           Dave, AA6YQ


Re: Group date change

Marv Stasak
 

Yes, immediately after I sent my last email to you I realized what I had done wrong and corrected it. Fortunately, I did back up the log before I'd started anything.  I used +1d and not +24hr but I would assume that was ok.  It seemed to work.  Thanks for your help Dave.

73,
Marv, W5DT


Re: Group date change

Dave AA6YQ
 

Thanks Dave. I was able to make it work--sort of. I isolated the wrong dated QSOs and did set up the exchange for the dates but ended up zeroing out the start and end times in minutes and seconds. Apparently, I could not simply insert the date only as a replacement without adding a further instruction to ignore the time info but I don't know or see how to do that. In this case, it isn't that vital for my purposes.

+ Hopefully you made the backup copy of your log, as suggested in my previous post. Make a copy of the backup, and then restore the backup as your log. Then

1. Filter the Log Page Display to contain the QSOs with the incorrect date

2. in the "Modify QSOs" panel

2a. set the "Item Name" selector to "QSO_Begin"

2b. set the "Item new value" to +24h

2c. click the Mod button

2d. set the "Item Name" selector to "QSO_End"

2e. set the "Item new value" to +24h

2f. click the Mod button

73,

Dave, AA6YQ


Re: Group date change

Marv Stasak
 

Thanks Dave.  I was able to make it work--sort of.  I isolated the wrong dated QSOs  and did set up the exchange for the dates but ended up zeroing out the start and end times in minutes and seconds.  Apparently, I could not simply insert the date only as a replacement without adding a further instruction to ignore the time info but I don't know or see how to do that.  In this case, it isn't that vital for my purposes.

73,

Marv, W5DT


Re: Disappearing QSOs

Dave AA6YQ
 

+ AA6YQ comments below

All of my DXlab apps are up to date according to Launcher. In particular DXKeeper is 16.1.9.

This afternoon I working some FT8 on several bands and decided to check to see how many new QSOs I had to upload to LoTW. I went to the QSL tab and instructed it to Add Requested. 33 QSOs were added to the queue. I then clicked on the LOG QSOs tab and noticed the QSOs were no longer in the log display. I then went back to the QSL tab and uploaded the QSOs to LoTW. They were all uploaded but when I did a synch qsos after they showed up on LoTW the report showed that none of the QSOs were in the log. They are OK on LoTW but not in my DXK log.

So I have two questions. First I want to figure out what happened to the QSOs so I can avoid having it happen again. Secondly, I need to find out how down load the affected QSOs from LoTW and import them in to DXK. The DXK error log contains no recent entries.

+ The QSOs in question all remain present in Paul's log; evidently, the Log Page Display was filtered in a way that hid them.

73,

Dave, AA6YQ


an updated USAP database is available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window. If you have DXKeeper or SpotCollector running, terminate them; then
direct DXView to upgrade its USAP database.

The USAP database specifies a US State and Grid Square for 836,680 stations licensed by the US Federal Communications Commission
(FCC).

Many thanks to Tom KQ5S for preparing this update!

73,

Dave, AA6YQ


Re: Disappearing QSOs

Dave AA6YQ
 

+ AA6YQ comment below
Sorry, I forgot to mention that I had done that. I always do a ctrl click when I go back to the Log Qsos tab.
+ OK. Please place your log file (suffix .mdb) in a zip archive, attach the zip archive to an email message that describes the date/time-range or QSOs that are missing, and send the message to me via

aa6yq (at) ambersoft.com

      73,

            Dave, AA6YQ


Re: Disappearing QSOs

Paul W5PF
 

Sorry, I forgot to mention that I had done that. I always do a ctrl click when I go back to the Log Qsos tab.

Paul W5PF


On 7/16/2021 6:34 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
All of my DXlab apps are up to date according to Launcher. In particular DXKeeper is 16.1.9.

This afternoon I working some FT8 on several bands and decided to check to see how many new QSOs I had to upload to LoTW. I went to the QSL tab and instructed it to Add Requested. 33 QSOs were added to the queue. I then clicked on the LOG QSOs tab and noticed the QSOs were no longer in the log display. I then went back to the QSL tab and uploaded the QSOs to LoTW. They were all uploaded but when I did a synch qsos after they showed up on LoTW the report showed that none of the QSOs were in the log. They are OK on LoTW but not in my DXK log.

So I have two questions. First I want to figure out what happened to the QSOs so I can avoid having it happen again. Secondly, I need to find out how down load the affected QSOs from LoTW and import them in to DXK. The DXK error log contains no recent entries.
+ As a first step, please click the X button in the Filter panel at the bottom of the Main window's "Log QSOs" tab. Did your missing QSOs re-appear?

        73,

             Dave, AA6YQ


Re: Disappearing QSOs

Dave AA6YQ
 

+ AA6YQ comments below
All of my DXlab apps are up to date according to Launcher. In particular DXKeeper is 16.1.9.

This afternoon I working some FT8 on several bands and decided to check to see how many new QSOs I had to upload to LoTW. I went to the QSL tab and instructed it to Add Requested. 33 QSOs were added to the queue. I then clicked on the LOG QSOs tab and noticed the QSOs were no longer in the log display. I then went back to the QSL tab and uploaded the QSOs to LoTW. They were all uploaded but when I did a synch qsos after they showed up on LoTW the report showed that none of the QSOs were in the log. They are OK on LoTW but not in my DXK log.

So I have two questions. First I want to figure out what happened to the QSOs so I can avoid having it happen again. Secondly, I need to find out how down load the affected QSOs from LoTW and import them in to DXK. The DXK error log contains no recent entries.
+ As a first step, please click the X button in the Filter panel at the bottom of the Main window's "Log QSOs" tab. Did your missing QSOs re-appear?

        73,

             Dave, AA6YQ


Disappearing QSOs

Paul W5PF
 

All of my DXlab apps are up to date according to Launcher. In particular DXKeeper is 16.1.9.

This afternoon I working some FT8 on several bands and decided to check to see how many new QSOs I had to upload to LoTW. I went to the QSL tab and instructed it to Add Requested. 33 QSOs were added to the queue. I then clicked on the LOG QSOs tab and noticed the QSOs were no longer in the log display. I then went back to the QSL tab and uploaded the QSOs to LoTW. They were all uploaded but when I did a synch qsos after they showed up on LoTW the report showed that none of the QSOs were in the log. They are OK on LoTW but not in my DXK log.

So I have two questions. First I want to figure out what happened to the QSOs so I can avoid having it happen again. Secondly, I need to find out how down load the affected QSOs from LoTW and import them in to DXK. The DXK error log contains no recent entries.


Thanks,

Paul W5PF


Re: Commander and DXKeeper sequencing

Ed W2LCQ
 

Dave and Bob,

Thanks for taking the time and having the patience for those very complete explanations. I converted all my logs to DXL last year and haven’t looked back. DXL got me DXCC and WAS. I appreciate the ingenuity and creativity that made these interoperable programs a reality and enjoy using them every day. 

73, de Ed Jones W2LCQ

Frankford Radio Club
BUG CWops SKCC FISTS LICWC QCWA


On Jul 16, 2021, at 5:38 PM, Dave AA6YQ <aa6yq@...> wrote:

 + AA6YQ comments below

This discussion is beyond my level of understanding. However I frequently initialize DXK before Commander.  WSJT-X is brought up automatically by my launcher. When I close WSJT-X and bring up Commander, Commander passes frequency to DXK and communicates with DXK without any problems. 

+ The 8 DXLab applications are designed so that they can be started in any order, and will still succeed at identifying each other's presence and interoperating without operator intervention. I made this claim during a presentation to the Northern California DX Club last night. After the presentation, Bob W6OPO reported that on his system, DXKeeper and Commander only interoperated  if Commander was started first. I requested an errorlog.txt file, which showed that on his system, when DXKeeper was started first, it never received the "I'm alive" message from Commander. That's because Bob had 7 of his 8 DXLab applications configured to run with Administrator privileges -- required because he has them installed in a folder that Windows considers "protected", but did not have Commander configured to run with Administrator privileges. The security policy implemented on Windows means that a message sent by an application without Administrator privileges can't be delivered to an application with Administrator privileges; this is why Commander's "I'm alive" message was not delivered to DXKeeper. Starting Commander with Administrator privileges.

+ Installing the Launcher and its applications in a folder that Windows doesn't consider "protected" - like the default c:\DXLab - means that no DXLab applications need Administrator privileges in order to interoperate with their peers.

+ Note that the "you can start them in any order" property may not apply to non-DXLab applications that interoperate with DXLab applications.

      73,

             Dave, AA6YQ

 

 


Re: Group date change

Dave AA6YQ
 

+ AA6YQ comments below

Somehow, I screwed up on a CWT mini contest through N1MM this last Thursday, 7/14/2021. Somehow, all of the QSOs are dated 7/13 instead of 7/14 and I didn't notice it until I imported the .ADI file into DXkeeper. I need to do a group date change. I assume that has to be done using the Advanced Sorts, Filters, and Modifiers tab. I've looked at that and the wiki instructions but I am uncertain as to how to set up the change.

+ First, backup your log (Configuration window, Log tab, Backup button)

+ Next, filter the Log Page Display to contain only the QSOs whose dates are incorrect

+ Then user the "Modify QSOs" panel to correct the QSO_Begin and QSO_End fields by adding 24 hours to each. The 9th bullet in the "Using the Modify QSOs panel" section of

https://www.dxlabsuite.com/dxkeeper/Help/ModifyLog.htm

+ explains how to do this.

+ Note that articles in "Getting Started with DXLab" - aka "the Wiki" - provide step-by-step instructions for frequent usage scenarios, but do not provide a comprehensive description of all available functionality. For the latter, refer to the Reference documentation.

73,

Dave, AA6YQ


Group date change

Marv Stasak
 

Dave,
 Somehow, I screwed up on a CWT mini contest through N1MM this last Thursday, 7/14/2021. Somehow, all of the QSOs are dated 7/13 instead of 7/14 and I didn't notice it until I imported the .ADI file into DXkeeper.  I need to do a group date change.  I assume that has to be done using the Advanced Sorts, Filters, and Modifiers tab. I've looked at that  and the wiki instructions but I am uncertain as to how to set up the change.

73,

Marv, W5DT


Re: Commander and DXKeeper sequencing

Dave AA6YQ
 

 + AA6YQ comments below

This discussion is beyond my level of understanding. However I frequently initialize DXK before Commander.  WSJT-X is brought up automatically by my launcher. When I close WSJT-X and bring up Commander, Commander passes frequency to DXK and communicates with DXK without any problems. 

+ The 8 DXLab applications are designed so that they can be started in any order, and will still succeed at identifying each other's presence and interoperating without operator intervention. I made this claim during a presentation to the Northern California DX Club last night. After the presentation, Bob W6OPO reported that on his system, DXKeeper and Commander only interoperated  if Commander was started first. I requested an errorlog.txt file, which showed that on his system, when DXKeeper was started first, it never received the "I'm alive" message from Commander. That's because Bob had 7 of his 8 DXLab applications configured to run with Administrator privileges -- required because he has them installed in a folder that Windows considers "protected", but did not have Commander configured to run with Administrator privileges. The security policy implemented on Windows means that a message sent by an application without Administrator privileges can't be delivered to an application with Administrator privileges; this is why Commander's "I'm alive" message was not delivered to DXKeeper. Starting Commander with Administrator privileges.

+ Installing the Launcher and its applications in a folder that Windows doesn't consider "protected" - like the default c:\DXLab - means that no DXLab applications need Administrator privileges in order to interoperate with their peers.

+ Note that the "you can start them in any order" property may not apply to non-DXLab applications that interoperate with DXLab applications.

      73,

             Dave, AA6YQ

 

 


Re: Commander and DXKeeper sequencing

Bob - W6OPO
 

Works Ed because you are not running DXLab's apps from a protected directory like Program Files or Program Files (x86).  Using DXLab's Launcher and installing the programs in the default directory avoids all this.

73,
Bob - W6OPO

7121 - 7140 of 209562