Date   

Re: Spot Collector Spot Database Display Tooltips

Dave AA6YQ
 

+ AA6YQ comments below
I use two monitors, with all DXLab apps displayed on the secondary monitor. Spot Collector's tooltips for the various buttons, check boxes, etc are displayed on the secondary monitor, as I would expect. However, the tooltips for the Spot Database Display are displayed on the primary monitor, not as expected. This doesn't present much of a problem except I often operate remotely with a single physical monitor and only one virtual monitor may be displayed at once.  This makes it impossible to read the tooltips from the Spot Database Display.  Is there a setting that will correct this?
+ That's a defect in the commercial component that is used to implement SpotCollector's Spot Database Display, and DXKeeper's Log Page Display. Since upgrading to a new version of this component would require a large testing effort, and since the "explanatory popup on wrong display" is the only known defect, I have not initiated the upgrade.

       73,

             Dave, AA6YQ


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 

On Mon, Jul 4, 2022 at 09:26 PM, Joe Subich, W4TV wrote:
you can set
DXKeeper to ignore grids from any source except "by user"
Where ?

 
--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Robie - AJ4F
 

There are many erroneous pieces of data in both QRZ.COM and LoTW.  Recently, I've worked stations, uploaded to LoTW and have received a confirmation for an un expected CQ Zone, US State, Grid, etc.  When this happens I attempt to contact the call sign owner and explain the error I've found.  Some make corrections and re-upload to LoTW, however most never reply.  I see similar "errors" in the data provided by other databases.  I do not have the data to make a comment about how extensive these errors are.  When I work a station which is in an entity I am chasing for an award I make sure to enter the entity in DXKeeper which I think is correct and then follow up diligently to ensure I receive an appropriate confirmation/QSL.  

Robie AJ4F

On Mon, Jul 4, 2022 at 3:29 PM Stewart Wilkinson <stewart.g0lgs@...> wrote:

[Edited Message Follows]

Further more - I think QRZ is limiting the search for IO91VL Grids as the list appears to be sorted Alpha-Numerically, but stops a G0CAL which means there are the G1, G2, G3 ,G4, G5, G6, G7, G8 series and the M series calls not even showing.

This means using the values from QRZ for many thosands of calls in the UK is totally meaningless.

--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Joe Subich, W4TV
 

What if the person has no access to Update QRZ.com ?
If QRZ is using IO91vl as the default for "G", the details would
indicate the grid source as "from DXCC country" and you can set
DXKeeper to ignore grids from any source except "by user".

The record for G3MEH says "from grid" which indicates that the
user has set his grid - so he has at some time (even if it was
7+ years ago) set his own address and grid. It would be his
responsibility to update the record from that point.

73,

... Joe, W4TV


On 2022-07-04 3:54 PM, Stewart Wilkinson wrote:
[Edited Message Follows]
On Mon, Jul 4, 2022 at 08:45 PM, Joe Subich, W4TV wrote:


Then he should update his data in QRZ.com! Can't expect DXKeeper to
fix the problems generated by your QSO partner
What if the person has no access to Update QRZ.com ?
It seems that IO91VL is asummed to be the locator for any callsign in the UK that HAS NOT entered a real Grid.
As I already posted QRZ thinks there are also 5000 stations in the one small grid area.
--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 
Edited

Further more - I think QRZ is limiting the search for IO91VL Grids as the list appears to be sorted Alpha-Numerically, but stops a G0CAL which means there are the G1, G2, G3 ,G4, G5, G6, G7, G8 series and the M series calls not even showing.

This means using the values from QRZ for many thosands of calls in the UK is totally meaningless.

--
Stewart G0LGS


Spot Collector Spot Database Display Tooltips

Pete Ritter K5CPR
 

I use two monitors, with all DXLab apps displayed on the secondary monitor. Spot Collector's tooltips for the various buttons, check boxes, etc are displayed on the secondary monitor, as I would expect. However, the tooltips for the Spot Database Display are displayed on the primary monitor, not as expected. This doesn't present much of a problem except I often operate remotely with a single physical monitor and only one virtual monitor may be displayed at once.  This makes it impossible to read the tooltips from the Spot Database Display.  Is there a setting that will correct this?
Thanks


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 

On Mon, Jul 4, 2022 at 08:51 PM, Joe Subich, W4TV wrote:
However, since
the record for G3MEH says "Geo Source From Grid " it's using the
grid G3MEH supplied not the default "from DXCC Country"
I have just tried a few random queires for sataions that show as being in IO91VL and they ALL showed as "From Grid".

 
--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 
Edited

On Mon, Jul 4, 2022 at 08:45 PM, Joe Subich, W4TV wrote:
Then he should update his data in QRZ.com! Can't expect DXKeeper to
fix the problems generated by your QSO partner
What if the person has no access to Update QRZ.com ?

It seems that IO91VL is asummed to be the locator for any callsign in the UK that HAS NOT entered a real Grid.

As I already posted QRZ thinks there are also 5000 stations in the one small grid area.


--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Joe Subich, W4TV
 

QRZ simply uses IO91VL as the geometric center for the DXCC country
"G" if the user does not provide more accurate data. However, since
the record for G3MEH says "Geo Source From Grid " it's using the
grid G3MEH supplied not the default "from DXCC Country" .

73,

... Joe, W4TV

On 2022-07-04 3:33 PM, Stewart Wilkinson wrote:
Further to this I am informed that QRZ assumes that you are in IO91VL when you add any UK callsign - which means QRZ thinks there are currently 4998 calls that show as boing io IO91VL.
--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Joe Subich, W4TV
 

I seem to recall he was once in IO91VL, but that was several years
ago.
Then he should update his data in QRZ.com! Can't expect DXKeeper to
fix the problems generated by your QSO partner any more than I an
expect DXKeeper to reject bogus LotW state/county data from the LID
who has moved from New York to Florida or Washington to Arizona or
Alaska to Missouri and uploaded 30 years of QSOs with a new station
location.

73,

... Joe, W4TV

On 2022-07-04 3:26 PM, Stewart Wilkinson wrote:
[Edited Message Follows]
I know that - but it means DXKeeper gets the wrong Grid - even though I used the correct one.
I seem to recall he was once in IO91VL, but that was several years ago.
--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 
Edited

Further to this I am informed that QRZ assumes that you are in IO91VL when you add any UK callsign - which means QRZ thinks there are currently 4998 calls that show as being io IO91VL when they could be anywhere in the UK.

--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Dave AA6YQ
 

+ AA6YQ comments below
I have that selected and I believe it has been that way for some time.

To test - I have just deleted the last QSO with G3MEH and repeated the import process for that one and I still get notification that it changed the grid.

Change imported gridsquare for G3MEH from IO91QS to IO91vl

+ That means GM3MEH specified his gridsquare in QRZ as IO91vl.

      73,

             Dave, AA6YQ

      


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 

On Sun, Jul 3, 2022 at 10:33 PM, Dave AA6YQ wrote:
+ On the Configuration window's "Callbook" tab, do you have the QRZ panel's "Ignore geocoded grid squares" enabled? If not, consider enabling it, as doing so will eliminate a source of inaccurate location information.
I have that selected and I believe it has been that way for some time.

To test - I have just deleted the last QSO with G3MEH and repeated the import process for that one and I still get notification that it changed the grid.

Change imported gridsquare for G3MEH from IO91QS to IO91vl
 
--
Stewart G0LGS


Re: 13Colonies how to make SQL Spot Collector filter

Dave AA6YQ
 

+ AA6YQ comments below
I'm trying the following SQL filter in SpotCollector, and its showing SSB spots only.
 
(CALLSIGN IN ('K2A','K2B','K2C','K2D','K2E','K2F','K2G','K2H','K2I','K2J','K2K','K2L','K2M','WM3PEN','GB13COL','TM13COL')) and <ORIGINFILTER> and <AGEFILTER> and ((MODE = 'SSB') or (((MODE = 'CW') or (MODE LIKE 'FT*')) and (SpotCount > 1)))
 
I'm using the following SQL filter to see only the ones I have not worked, and its working fine
(CALLSIGN IN ('K2D','K2E','K2F','K2I','K2K','WM3PEN','GB13COL','TM13COL')).

+ The first expression will only show CW and FT* Spot Database Entries that have been spotted more than once, and that "survive" your Origin filter. 

+ If the second expression meets your needs, continue to use it!

        73,

               Dave, AA6YQ


Re: Why is DXKeeper changing some imported Grids?

Dave AA6YQ
 

+ AA6YQ comments below
I'm wondering how many of my grids have been changed, I do the same contests
as Stewart and import afterwards from ADIF with the grids from the contest
exchange which are teh ones I want to keep. If syncing LOTW QSLs gives teh
option, why not ADIF input as well.

+ If DXKeeper changes an imported grid, it notifies you of the change in the report it displays after the import operation completes. If no report was displayed, no changes were made.

        73,

              Dave, AA6YQ


Re: 13Colonies how to make SQL Spot Collector filter

Gordon LaPoint
 

I'm trying the following SQL filter in SpotCollector, and its showing SSB spots only.

(CALLSIGN IN ('K2A','K2B','K2C','K2D','K2E','K2F','K2G','K2H','K2I','K2J','K2K','K2L','K2M','WM3PEN','GB13COL','TM13COL')) and <ORIGINFILTER> and <AGEFILTER> and ((MODE = 'SSB') or (((MODE = 'CW') or (MODE LIKE 'FT*')) and (SpotCount > 1)))

I'm using the following SQL filter to see only the ones I have not worked, and its working fine
(CALLSIGN IN ('K2D','K2E','K2F','K2I','K2K','WM3PEN','GB13COL','TM13COL'))

Thanks for the help!
Gordon - N1MGO


On 7/4/2022 12:24 PM, Dave AA6YQ wrote:

+ AA6YQ comments below
When I use either filter all I get is the SSB spots, even though I see several for CW if I don't use any filter.
What have I done wrong??

+ Please post the filter you are using.

     73,

         Dave, AA6YQ



Re: Importing a Large DX4Win Log

Dave AA6YQ
 

+ AA6YQ comments below

 

I remain a new user! I've been using DXKeeper for about three years and have been working my way through a bunch of different learning curve issues.
 
But now it is time to bite the bullet and import my large DX4Win log.  It is about 120k QSOs.
 
The log is made up of combined logs from all my calls.  Primary use is award tracking - so for DXCC US locations were OK and I could pick dates for 5BWAS.
 
So the initial question is what is the best way to import the log?  I realize there is a special DX4Win import which (I assume) recognizes some of the field structures of DX4Win into DXKeeper. 

+ DX4WIN takes liberties with the ADIF specification; see

https://www.dxlabsuite.com/dxkeeper/Help/Import.htm#ADIF%20Style

 

But here are some specific issues/questions:
 
1)  myQTH ID does not have a date field.  Is that important?  My award selections for Callsign/QTH are date specific so it may not be.  But if it is pertinent then I have the complexity of having a call, changing the call, and then reapplying for the original call several years later so I have two date ranges for a single call sign with another call sign in between.  Should I break the imports in call/date specific segments.  QTH lat/long will vary for the same callsign.
 

+ Break the ADIF file you export from DX4WIN into segments whose QSOs were made from the same QTH using the same Station Callsign.

+ Before importing a segment, backup your log so you can easily recover if something goes awry.

+ When you import each segment into DXKeeper, use 

- the "Substitution Options" panel's  "Substitute for missing myQTH IDs" option on the Main window's "Import QSOs" tab to specify the appropriate myQTH ID

- the the "Replacement Options" panel's "Station Callsign" to specify the appropriate Station Callsign

 

2)  When it is imported and I want to update the LoTW status of the ENTIRE log, what is the best way?  I have LoTW and paper QSL cards for my Honor Roll and 8BDXCC.  I've read many posts about size of files that seem to choke LoTW and hit a policy brick wall.  I am not trying to fool the system, but want to get all the records straight.
 
+ Depressing the CTRL key while clicking the "Sync LoTW QSOs" button, and then depressing the CTRL key while clicking the "Sync LoTW QSLs" button is the way to update your log with LoTW status. However, the first operation may trigger LoTW's undocumented "download abuse detector", which to my knowledge remains in force. I can't predict what will happen, nor can I recommend updating your log in smaller chunks, as the chunk size required to fly below the download abuse detector's radar is not documented.
 
Is there a "step-by-step" guide for "dummies"? ;) 
 
+ Step-by-step instructions are here:
 
https://www.dxlabsuite.com/dxlabwiki/SwitchingToDXKeeper
 
There is a lot of info in 55 years of DXing and contesting.  Some may not be recoverable if I screw up because some of the original logs no longer exist or were done in software that I may not have a loadable copy.
 
+ If you make a new backup copy of your log prior to each step (and save these copies until the transition has been completed), you will be protected, and you will not have to start over from scratch if you make a mistake.
 
       73,

              Dave, AA6YQ


Re: Why is DXKeeper changing some imported Grids?

Brian D
 

"Stewart Wilkinson" <stewart.g0lgs@...> wrote:

+ There is no way for DXKeeper to know whether the gridsquare specified in
the QSO record came from an accurate source or a potentially inaccurate
source - like a Callbook record or a previously logged QSO.

So allow me to STOP DXKeeper from usign the wrong one !
I'm wondering how many of my grids have been changed, I do the same contests
as Stewart and import afterwards from ADIF with the grids from the contest
exchange which are teh ones I want to keep. If syncing LOTW QSLs gives teh
option, why not ADIF input as well.

--
Brian D
G3VGZ G8AOE G3T
IO94im


Re: 13Colonies how to make SQL Spot Collector filter

Dave AA6YQ
 

+ AA6YQ comments below
When I use either filter all I get is the SSB spots, even though I see several for CW if I don't use any filter.
What have I done wrong??

+ Please post the filter you are using.

     73,

         Dave, AA6YQ


Re: Importing a Large DX4Win Log

Joe Subich, W4TV
 

Rick,

The log is made up of combined logs from all my calls. Primary use
is award tracking - so for DXCC US locations were OK and I could pick
dates for 5BWAS.
Are all your calls from within the "lower 48" or do they include QSOs
made from multiple DXCC countries?

Does DX4Win include your callsign ("Station_Callsign") in its ADIF
export or is it a simple list of all QSOs?

If not, can you do multiple exports from DX4Win separating the data
by callsign?

1) myQTH ID does not have a date field. Is that important?
No. WAS and VUCC are based on distance among locations not by date.

2) When it is imported and I want to update the LoTW status of the
ENTIRE log, what is the best way? I have LoTW and paper QSL cards
for my Honor Roll and 8BDXCC.
There are two issues at play ... LotW (upload/confirmed/awarded) status
and DXCC credit status. There is documentation in "Getting Started with
DXLab Suite":
<http://www.dxlabsuite.com/dxlabwiki/GettingStarted>
that will walk you through those issues.

The first step is to get your import done and properly categorized by
callsign and QTH:
<http://www.dxlabsuite.com/dxlabwiki/SwitchingToDXKeeper>

After that you will want to look at:
<http://www.dxlabsuite.com/dxlabwiki/AwardTracking>
particularly the section on "Managing DXCC Credits" for sorting through
the HR/8BDXCC credits.

The number one piece of advice (and I've intentionally "buried the
lead") is *BACK UP YOUR LOG AT EACH STEP ALONG THE WAY*. That way
if some import/update/modification goes wrong you can take a step back
and go a different direction (or ask for help).

73,

... Joe, W4TV


On 2022-07-04 9:00 AM, Rick Heinrich wrote:
I remain a new user! I've been using DXKeeper for about three years and
have been working my way through a bunch of different learning curve issues.
But now it is time to bite the bullet and import my large DX4Win log. It
is about 120k QSOs.
The log is made up of combined logs from all my calls. Primary use is
award tracking - so for DXCC US locations were OK and I could pick dates
for 5BWAS.
So the initial question is what is the best way to import the log? I
realize there is a special DX4Win import which (I assume) recognizes some
of the field structures of DX4Win into DXKeeper. But here are some
specific issues/questions:
1) myQTH ID does not have a date field. Is that important? My award
selections for Callsign/QTH are date specific so it may not be. But if it
is pertinent then I have the complexity of having a call, changing the
call, and then reapplying for the original call several years later so I
have two date ranges for a single call sign with another call sign in
between. Should I break the imports in call/date specific segments. QTH
lat/long will vary for the same callsign.
2) When it is imported and I want to update the LoTW status of the ENTIRE
log, what is the best way? I have LoTW and paper QSL cards for my Honor
Roll and 8BDXCC. I've read many posts about size of files that seem to
choke LoTW and hit a policy brick wall. I am not trying to fool the
system, but want to get all the records straight.
I have been dragging my feet on this for over a year because I am
intimidated by the impact of missing a critical setting in the transfer or
misinterpretation of a setting or field. I don't want to screw up my
existing 3k QSO log that was started in DXKeeper in 2019.
Is there a "step-by-step" guide for "dummies"? ;) There is a lot of info
in 55 years of DXing and contesting. Some may not be recoverable if I
screw up because some of the original logs no longer exist or were done in
software that I may not have a loadable copy.
I graciously ask for the guidance from this key resource.
Rick N0YY

2241 - 2260 of 211173