Date   

Re: Short Path Azimuth not shown on DX Keeper for imported Qs

Rod Greene
 

Thanks Dave! 73, Rod

On Sunday, September 19, 2021, 03:43:57 PM MDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

DXK does not display the azimuth for Qs that I have imported from N1MM+ (imported .adif file). Qs that I log from the Capture window do display the azimuth okay. I have probably missed an option to do a lookup for azimuth when I do the import. I am using the "ANT_AZ" database item in the Log Page Display.

Have done some checking but not found the option so far. Please point me in the right direction.

+ The intent of a logged QSO's Azimuth item is to record the actual heading of your antenna during that QSO. If N1MM didn't include that information in the ADIF file you exported, then this information has been lost unless you remember it or wrote it down, in which case you can manually update the logged QSO in DXKeeper.

+ If you worked a station via the long path, it's certainly worth setting the logged QSO's "Antenna Path" item to L .

+ Selecting a logged QSO in DXKeeper causes DXView's Main window to display the great-circle short path and long path headings from your QTH to your QSO partner's QTH -- so there's no compelling need to update a logged QSO with an empty Azimuth item to record the great-circle heading. If you wish to do so, however, see the instructions here:

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


      73,


                Dave, AA6YQ







SC : Prune the database

3a2mw Franco Lucioni
 

Hi Dave and the group.
I wanted to prune the SC's database having 12k entries, so I clicked on SC Configuration/Spot Database/Prune and a label appeared : Do you really want to CLEAR the Spot Database?
Yes, and the database was cleared, not Pruned as asked.
Checked 3 times, always the same result.
My regulations for Size Control:
Prune entries older... 0.04
Prune on Startup Yes
Prune Spot Database hourly Yes
Clear Spot Database on startup NO

Thanks and 73
Franco 3A2MW


Re: Short Path Azimuth not shown on DX Keeper for imported Qs

Dave AA6YQ
 

+ AA6YQ comments below

DXK does not display the azimuth for Qs that I have imported from N1MM+ (imported .adif file). Qs that I log from the Capture window do display the azimuth okay. I have probably missed an option to do a lookup for azimuth when I do the import. I am using the "ANT_AZ" database item in the Log Page Display.

Have done some checking but not found the option so far. Please point me in the right direction.

+ The intent of a logged QSO's Azimuth item is to record the actual heading of your antenna during that QSO. If N1MM didn't include that information in the ADIF file you exported, then this information has been lost unless you remember it or wrote it down, in which case you can manually update the logged QSO in DXKeeper.

+ If you worked a station via the long path, it's certainly worth setting the logged QSO's "Antenna Path" item to L .

+ Selecting a logged QSO in DXKeeper causes DXView's Main window to display the great-circle short path and long path headings from your QTH to your QSO partner's QTH -- so there's no compelling need to update a logged QSO with an empty Azimuth item to record the great-circle heading. If you wish to do so, however, see the instructions here:

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

73,

Dave, AA6YQ


Re: Short Path Azimuth not shown on DX Keeper for imported Qs

Rod Greene
 

DXK does not display the azimuth for Qs that I have imported from N1MM+ (imported .adif file). Qs that I log from the Capture window do display the azimuth okay. I have probably missed an option to do a lookup for azimuth when I do the import. I am using the "ANT_AZ" database item in the Log Page Display.

Have done some checking but not found the option so far. Please point me in the right direction. Thanks and 73, Rod/w7zrc

 


Re: Short Path Azimuth not shown on Spotcollector anymore

Dave AA6YQ
 

+ AA6YQ comments below

The short path Azimuth to a spotted station that I was displaying on Spotcollector has disappeared. The column is empty.
Short and long path Azimuth is still shown on DXview. No problem there. I must have had some issue last night as all the spot sources were disabled this morning also.

+ The spontaneous loss of settings is not good. I suggest checking the Windows event logs for reports of hardware or software failures.

Enabling them got things going again and all seems fine, except for the azimuth display.
I'm guessing something needs to be turned back on, but I've run out of places to look?

+ Look here:

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

73,

Dave, AA6YQ


Re: Short Path Azimuth not shown on Spotcollector anymore

Joe Subich, W4TV
 

Try "Look up missing location info" and/or "Automatic DXView Lookup"
on Config -> General


73,

... Joe, W4TV

On 2021-09-19 3:34 PM, aschnabolk wrote:
Hi Dave ,
The short path Azimuth to a spotted station that I was displaying on Spotcollector has disappeared. The column is empty.
Short and long path Azimuth is still shown on DXview. No problem there. I must have had some issue last night as all the
spot sources were disabled this morning also. Enabling them got things going again and all seems fine, except for the azimuth display.
I'm guessing something needs to be turned back on, but I've run out of places to look? Any help would be appreciated.
Thanks
Allan W2OIB


Short Path Azimuth not shown on Spotcollector anymore

aschnabolk
 

Hi Dave ,
The short path Azimuth to a spotted station that I was displaying on Spotcollector has disappeared. The column is empty.
Short and long path Azimuth is still shown on DXview. No problem there. I must have had some issue last night as all the 
spot sources were disabled this morning also. Enabling them got things going again and all seems fine, except for the azimuth display. 
I'm guessing something needs to be turned back on, but I've run out of places to look? Any help would be appreciated.

Thanks
Allan W2OIB


Re: special characters

Jeff Tostenrude K5UHF
 

Looks like I got all the missing QSOs sorted out. Thank you again for all the assistance. Let's hope they get the bug fixed on the Gridtracker side.

73,
Jeff


Re: FT8 Bridge

dl8le
 

Thanks a lot for your fast replies, Bill and Dave! The Wiki-information is very clear, got it now. Sorry for not reading it carefully enough ... 

73

Juergen, DL8LE


Re: DXLabs won't start after computer shut down

Larry Bryan
 

+ I'm glad that your recovery was smooth, Larry. Did you find the root cause?

Not really, I looked at the error log and it was still pointing to the Tabctl32.ocx file. I explored that error message on the net and followed MS instructions on how to fix it, but that did not work. So I made a copy of the DXLab directory on my backup drive in case I needed something, and then uninstalled each program. I was hoping that a fresh install would re-register that OCX file since it is shared by several programs and it did.

I'm still leaning toward the Winzip install/upgrade as the time in the error log is about the time I was working on that issue.

Larry
W8LIG


Re: I'd like to use SpotCollectors Text Message Alert Function

Dave AA6YQ
 

+ AA6YQ comments below

Dave and all who replied to my request for help,

Thanks to all for the outpouring of helpful information. I now have email and SMS functions working.

What worked for me:
In the Email Alarm Tab:
enable checked
From email address my gmail address
To email address: my gmail address
Include spot notes checked
SMS-optimized messagess checked
In the Outgoing Mail Server Box
Address smtp.gmail.com
Server requires authentication checked
User name my gmail address
Password the APP PASSWORD I created in my Google Account Note - When asked what you want it for choose "Select app" From drop down choose "other", then enter SpotCollector and finally click "generate." When you enter the app password as your password here, don't include the spaces.

+ using Larry K4KGG's notes above, I have updated

https://www.dxlabsuite.com/spotcollector/Help/ConfigurationNotifications.htm#Settings%20for%20popular%20outgoing%20email%20servers

+ to include step-by-step instructions for obtaining and using an "App Password" that will enable Gmail's outgoing mail server to accept messages sent by your instance of SpotCollector. The option to obtain an "App Password" is only provided if your Gmail account is configured to employ 2-step verification.

73,

Dave, AA6YQ


Re: Spot collector

Robert galambos
 

THANKS that helped


On Fri, Sep 17, 2021 at 3:07 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Can some share their spot sources coming. With me?

+ See

http://www.dxcluster.info/telnet/index.php

+ I use

K1RFI:   K1RFI.com  port 7300

EI7MRE: mayodx.ath.cx port 7300

N6WS: n6ws.ddns.net port 7300

JH1RFM: jh1rfm.ddo.kp port 7300

       73,

                Dave, AA6YQ








Re: FT8 DXKeeper question

Dave AA6YQ
 

+ AA6YQ comments below

Hi Guys..I had WSJT and JTAlert working with DXkeeper to log my FT8 contacts a few nights ago.

Today for some reason, I make the contacts and I get the confirmation window opening

But the contacts are not transferred automatically to DXKeeper anymore.

Did I miss something here??

+ Either one of the settings was changed, or an anti-malware application has begun preventing your applications from communicating.
The settings are documented here:

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


Where is the log file in WSJT that holds the contacts

+ In the WSJT-X File menu, click the "Open log directory" command. Windows Explorer will display a folder containing the file

wsjtx_log.adi

+ which contains an ADIF record for each logged QSO.

How do I retrieve them or get them transferred now???

+ Locate the ADIF record in wsjtx_log.adi for each QSO that was not logged to DXKeeper. Copy these records to a text file, name the
file

missing.adi

+ and when all "not logged" QSOs have been copied, close the file and direct DXKeeper to import it.

73,

Dave, AA6YQ


Re: FT8 DXKeeper question

Bill Pence
 

Wsjt file menu "open log directory" will get you to the files. Wsjt log is there in adif format.

If you are only missing a few ft8, I think you can enable dupe checking in dxkeeper and just import.  Only the new qso's should then end up in the dxkeeper log.

Also you can use an adif edit program such as ADIF Master 
"ADIF Master - advanced application for working with Ham Radio logbooks" http://www.dxshell.com/adif-master.html

To get just the qso's you need and make a file to import.


As for why they did not get transferred,
Are you sure you had jtalert open?
I've made that mistake. Could so m.j ethinyl BBC else interfere with the TCP port between jtalert and dxkeeper?  Unless its multicast, that is a 1 source 1 destination pipe...




On Sat, Sep 18, 2021, 5:03 PM Ted Boerkamp <tboerkamp@...> wrote:

Hi Guys….I had WSJT and JTAlert working with DXkeeper to log my FT8 contacts a few nights ago.

Today for some reason, I make the contacts and I get the confirmation window opening

But the contacts are not transferred automatically to DXKeeper anymore.

Did I miss something here?? Where is the log file in WSJT that holds the contacts and

How do I retrieve them or get them transferred now???

Any help is appreciated.

Thanks  Ted VE3SS


Re: special characters

Jeff Tostenrude K5UHF
 

Thank you for investigating this. I have not looked at the GT forum yet to see if this had previously been reported.

The QSO does get logged to LoTW (from GT), so I was hoping that by using the Sync LoTW QSOs function, it would record the QSO in DXKeeper, but it does not. (It works fine for all other QSOs.)

73,
Jeff

On Sat, Sep 18, 2021 at 3:09 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I am using Gridtracker to send the logs to DXKeeper

+ Thanks for the errorlog you sent me. It shows that when a "Log QSO" directive conveying an ADIF record that contains one or more "special characters" is received from GridTracker, the directive incorrectly specifies the total number characters in the ADIF record. As a result, the required <EOR> tag at the end of the ADIF record is truncated, causing DXKeeper to reject the directive.

+ I am copying a Jonathan KF5QHQ, a member of the GridTracker team, so that he can convey this defect report.


when I try to download the QSOs from LoTW, there is still an issue.

+ Why are you downloading QSOs from LotW? What steps are you taking to do this? What leads you to conclude that "there is still an issue"?

+ The appropriate action after submitting QSOs to LoTW is to invoke DXKeeper's "Sync LoTW QSOs" function to update your logged QSOs to reflect their acceptance by LoTW, and then invoke its "Sync LoTW QSLs" to update your QSOs to reflect their confirmation by LoTW. See

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

        73,

               Dave, AA6YQ



FT8 DXKeeper question

Ted Boerkamp
 

Hi Guys….I had WSJT and JTAlert working with DXkeeper to log my FT8 contacts a few nights ago.

Today for some reason, I make the contacts and I get the confirmation window opening

But the contacts are not transferred automatically to DXKeeper anymore.

Did I miss something here?? Where is the log file in WSJT that holds the contacts and

How do I retrieve them or get them transferred now???

Any help is appreciated.

Thanks  Ted VE3SS


Re: special characters

Dave AA6YQ
 

+ AA6YQ comments below

I am using Gridtracker to send the logs to DXKeeper

+ Thanks for the errorlog you sent me. It shows that when a "Log QSO" directive conveying an ADIF record that contains one or more "special characters" is received from GridTracker, the directive incorrectly specifies the total number characters in the ADIF record. As a result, the required <EOR> tag at the end of the ADIF record is truncated, causing DXKeeper to reject the directive.

+ I am copying a Jonathan KF5QHQ, a member of the GridTracker team, so that he can convey this defect report.


when I try to download the QSOs from LoTW, there is still an issue.

+ Why are you downloading QSOs from LotW? What steps are you taking to do this? What leads you to conclude that "there is still an issue"?

+ The appropriate action after submitting QSOs to LoTW is to invoke DXKeeper's "Sync LoTW QSOs" function to update your logged QSOs to reflect their acceptance by LoTW, and then invoke its "Sync LoTW QSLs" to update your QSOs to reflect their confirmation by LoTW. See

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

73,

Dave, AA6YQ


Re: DXLabs won't start after computer shut down

Dave AA6YQ
 

+ AA6YQ comments below
Fixed by removing DXLabs suite, restarting and reinstalling. Program picked up my workspace and I'm up and running again.

+ I'm glad that your recovery was smooth, Larry. Did you find the root cause?

     73,

          Dave, AA6YQ


Re: FT8 Bridge

Dave AA6YQ
 

+ AA6YQ comments below

after a very long time of nearly no activity in amateur radio I am coming back now with a huge work load in front of me in setting up my antennas, pa's etc. again.

+ Welcome back, Juergen; it's great to see your callsign here again!

So I have started to use low power modes with WSJT-X and JTDX with a Hermes Lite II a little bit when I was in Germany. Now I am starting to see if I cannot set up my Hermes Lite II with different instances of WSJT-X running at the same time and feed the information into Spotcollector. This would be very helpful and can give me a good impression of the actual situation at my own station and not somewhere else. With my low output of about 3 W this is even more important.

+ There are two ways to connect WSJX-X to DXLab: directly (via SpotCollector) and via JT-Alert; these are summarized here:

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

+ The direct connection does not support JTDX, as it does not implement the necessary programmatic interfaces provided by WSJT-X. I also dislike JTDX being a "hostile fork" of WSJT-X.

When I open the configuration of Spotcollector, however, there is only one entry for WSJT-X. Question: What can I do if I want to run more than one instance simultaneously? As all of my instances will use port 2237 could it still be possible to use the information of all the instances in Spotcollector? Or is there a possibility that Spotcollector will complain if messages are coming from different instances, e.g. DL8LE-1, DL8LE-2 and DL8LE-3 or similar? A brief reply would be nice. Thanks in aövance.

+ As stated in the "Starting an Instance of WSJT-X" section of

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

+ SpotCollector will accept connections from up to 16 instances of WSJT-X. If more than one instance of WSJT-X is running on the same computer, each instance on that computer must have a distinct ID; this can be accomplished by specifying a unique rig name in a command line used to start WSJT-X.

+ I have only tested this capability with 2 instances of WSJT-X; if you employ more instances than that, please post a report here. Thanks!

73,

Dave, AA6YQ


Re: DXLabs won't start after computer shut down

Larry Bryan
 

Fixed by removing DXLabs suite, restarting and reinstalling. Program picked up my workspace and I'm up and running again.

Larry
W8LIG

2381 - 2400 of 205819