Date   
Re: DXKeeper missing SFI info

Mike - AA1AR
 

Sam & Dave,

Since I wasn’t seeing any new data on ok4bx’s site, I had already created these scripts for the first 11 months of 2015.

I’ll do Dec. in the next day or two.

I had 2014 done last year but already deleted it.  I may still have the data in Excel.

73, Mike – AA1AR

 

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, January 11, 2016 11:28 AM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper missing SFI info

 

 

You're right, Sam, the modification can be accomplished with a script.

However, the only practical way to generate a script that updates SFI, A, and K for 730 days is with a program.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, January 11, 2016 11:20 AM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper missing SFI info

On 1/11/2016 8:57 AM, ' Dave AA6YQ' aa6yq@... [dxlab] wrote:
>>>> AA6YQ comments below
>>>> There is no way to fill in missing SFI/A/K information using a >>>> DXKeeper script.
> 73,
> Dave, AA6YQ

I beg to differ Dave, go to the files section file: DXK_Solar.zip

contains text files/scripts that will do what you say can't be done but they are only for the years 1997 - 2011

here is an example of the script:


Filter QSO_Begin BETWEEN #2011-01-01 0:00# and #2011-01-01 23:59# Modify SFI 91 Modify A_INDEX 3 Filter QSO_Begin BETWEEN #2011-01-01 0:00# and #2011-01-01 9:00# Modify K_INDEX 0 Filter QSO_Begin BETWEEN #2011-01-01 9:00# and #2011-01-01 21:00# Modify K_INDEX 1 Filter QSO_Begin BETWEEN #2011-01-01 21:00# and #2011-01-01 23:59# Modify K_INDEX 2 Filter QSO_Begin BETWEEN #2011-01-02 0:00# and #2011-01-02 23:59# Modify SFI 91 Modify A_INDEX 3 Filter QSO_Begin BETWEEN #2011-01-02 0:00# and #2011-01-02 6:00# Modify K_INDEX 1 Filter QSO_Begin BETWEEN #2011-01-02 6:00# and #2011-01-02 12:00# Modify K_INDEX 0 Filter QSO_Begin BETWEEN #2011-01-02 12:00# and #2011-01-02 18:00# Modify K_INDEX 1 Filter QSO_Begin BETWEEN #2011-01-02 18:00# and #2011-01-02 21:00# Modify K_INDEX 0 Filter QSO_Begin BETWEEN #2011-01-02 21:00# and #2011-01-02 23:59# Modify K_INDEX 1 Filter QSO_Begin BETWEEN #2011-01-03 0:00# and #2011-01-03 23:59# Modify SFI 92 Modify A_INDEX 4 Filter QSO_Begin BETWEEN #2011-01-03 0:00# and #2011-01-03 12:00# Modify K_INDEX 0 Filter QSO_Begin BETWEEN #2011-01-03 12:00# and #2011-01-03 15:00# Modify K_INDEX 1 Filter QSO_Begin BETWEEN #2011-01-03 15:00# and #2011-01-03 23:59# Modify K_INDEX 2

here is a snip from the scripts resulting log file:


Filter QSO_Begin BETWEEN #2010-01-30 0:00# and #2010-01-30 23:59#
Selected 23 QSOs

Modify SFI 75
Modified 23 QSOs
Selected 23 QSOs

Modify A_INDEX 4
Modified 23 QSOs
Selected 23 QSOs

Filter QSO_Begin BETWEEN #2010-01-30 0:00# and #2010-01-30 9:00#
Selected 0 QSOs

Modify K_INDEX 1
no QSOs selected, so none modified

Filter QSO_Begin BETWEEN #2010-01-30 9:00# and #2010-01-30 12:00#
Selected 6 QSOs

Modify K_INDEX 0
Modified 6 QSOs
Selected 6 QSOs

Filter QSO_Begin BETWEEN #2010-01-30 12:00# and #2010-01-30 21:00#
Selected 17 QSOs

Modify K_INDEX 1
Modified 17 QSOs
Selected 17 QSOs

Filter QSO_Begin BETWEEN #2010-01-30 21:00# and #2010-01-30 23:59#
Selected 0 QSOs

Modify K_INDEX 2
no QSOs selected, so none modified

Filter QSO_Begin BETWEEN #2010-01-31 0:00# and #2010-01-31 23:59#
Selected 14 QSOs

Modify SFI 75
Modified 14 QSOs
Selected 14 QSOs

Modify A_INDEX 3
Modified 14 QSOs
Selected 14 QSOs

Filter QSO_Begin BETWEEN #2010-01-31 0:00# and #2010-01-31 3:00#
Selected 0 QSOs

Modify K_INDEX 2
no QSOs selected, so none modified

Filter QSO_Begin BETWEEN #2010-01-31 3:00# and #2010-01-31 6:00#
Selected 0 QSOs

Modify K_INDEX 1
no QSOs selected, so none modified

Filter QSO_Begin BETWEEN #2010-01-31 6:00# and #2010-01-31 9:00#
Selected 0 QSOs

Modify K_INDEX 0
no QSOs selected, so none modified

Filter QSO_Begin BETWEEN #2010-01-31 9:00# and #2010-01-31 15:00#
Selected 14 QSOs

Modify K_INDEX 1
Modified 14 QSOs
Selected 14 QSOs

Filter QSO_Begin BETWEEN #2010-01-31 15:00# and #2010-01-31 18:00#
Selected 0 QSOs

Modify K_INDEX 0
no QSOs selected, so none modified

Filter QSO_Begin BETWEEN #2010-01-31 18:00# and #2010-01-31 23:59#
Selected 0 QSOs

Modify K_INDEX 1
no QSOs selected, so none modified


I just don't know how to write a script for 2014 & 2015. Nor do I know where the data was found to inject into the script when it is written.
I'm sorry if this is going beyond the scope of what the list is for. I was just in hopes that someone on the list might take interest and be able to fulfill me dream, hi hi. Feel free to just drop the thread if you like.

--
GB & 73
K5OAI
Sam Morgan
John 3:16 Ephesians 2:8-9 1 Peter 2:24 Acts 2:38

------------------------------------
Posted by: Sam Morgan <k5oai.sam@...>
------------------------------------

------------------------------------

Yahoo Groups Links

Re: Problem in QSL message text substitution

John E Bastin <bastinj@...>
 

On 11 Jan 2016, at 10:15, ' Dave AA6YQ' @AA6YQ [dxlab] <dxlab@...> wrote:

+++ The same code is used to "expand" commands found in the "QSL Message" item, whether the destination is a QSL card, a QSL label, an ADIF file, or a tab-delimited file. When I direct DXKeeper to generated an ADIF file from a QSO whose "QSL Message" item contains <contestid>, the result is correct. When I direct DXKeeper to generated an ADIF file from a QSO whose "QSL Message" item contains <contest_id>, the result is an "invalid command" error message.
OK, after repeated testing and massaging this file every which way, I now see the problem and why I’m getting the results I do.

I am *not* using the “ADIF file” selection in the QSL window to generate the file I’m sending to eQSL. Why not? Well, I cannot select eQSL and generate a queue using “Add Requested”, then change to “ADIF file” to print the queue. It won’t use ADIF with an eQSL-generated queue.

Therefore, when I do this, I generate a log display of the QSLs I want to upload, then use the “Export QSOs” tab and select “Export ADIF for eQSL.CC”. I then upload the generated ADIF file using the “Upload ADIF” selection on the eQSL page. After that, I click the “Update eQSL Sent” button in the “Export QSOs” window and the project is complete (in much less time than it takes to upload a queue of several hundred QSLs using the eQSL function in the QSL window).

While working with this, I thought of doing my manual log display selection and then selecting “Add All” in the ADIF part of the QSL window. I generated the file that way, and it *did* give me the proper results in the “QSLMsg” field. Unfortunately, when I then selected “Update Log” in the QSL window, it inserted a “Y” in the “QSL Sent” field of the log, as if I had just sent about 700 paper QSL cards. That definitely doesn’t suit.

So I guess I’ll keep generating the ADIF file the way I’m doing it, adjusting the inserts to something that works for that method.

Thanks, Dave, for letting me see the reason I was having the problem I was having and leading me to the work-around that does the job.

73,

John K8AJS
bastinj@...

Changing station callsign

Julio Peralta
 

I have just imported 7000+ q’s into DXlabs. The import went very smoothly. However now I find that there are about 1700 Q’s that have the wrong call sign associated with them. Prior to 1/9/2002 I held the call WB4OOJ. Those 1700 Q’s are now showing W4HY as the station call, WB4OOJ as the OP call and W4HY as the owner call. I think at least the Station Call should be WB4OOJ and maybe the Owners Call should be changed as well.

 

I want to make sure that incoming LOTW QSL’s will match up properly. Am I right to think those fields need to be changed?

 

If they should be changed can Dave or someone help me with making those changes.

 

Julio, W4HY  

Setting an override for Palmyra

W2IRT
 

Hi Dave/all,

It's been a while since I needed to do this but how do I tell DX Keeper and DX View to set an override so that K5P (temporarily) shows as Palmyra and not the lower-48? I set the override in Spot Collector but I'm not sure where to set it up in DX Keeper.

If I double-click a spot in SC then the Capture window of DXK shows KH5-P, as it should. If I enter the call manually in the Capture window and tab to the next field it just shows up as K, since that's how it's set up on QRZ.com. I obviosuly need to override this somehow, but I'm not sure how.

Thanks.
Pete, W2IRT


Re: Setting an override for Palmyra

Richard B Drake
 

No need to do anything with DXKeeper unless you have already recorded a QSO. In that case just correct the QSO(s) you entered. Any future QSO's should reflect the override you entered in DXView. Hopefully, you included an appropriate expiration date with the override.

73, Rich - W3ZJ
http://www.w3zj.com

On 1/11/2016 1:36 PM, peter@... [dxlab] wrote:
Hi Dave/all,

It's been a while since I needed to do this but how do I tell DX Keeper and DX View to set an override so that K5P (temporarily) shows as Palmyra and not the lower-48? I set the override in Spot Collector but I'm not sure where to set it up in DX Keeper.

Re: Setting an override for Palmyra

iain macdonnell - N6ML
 

On Mon, Jan 11, 2016 at 10:36 AM, peter@... [dxlab]
<dxlab@...> wrote:



Hi Dave/all,

It's been a while since I needed to do this but how do I tell DX Keeper and DX View to set an override so that K5P (temporarily) shows as Palmyra and not the lower-48? I set the override in Spot Collector but I'm not sure where to set it up in DX Keeper.

If I double-click a spot in SC then the Capture window of DXK shows KH5-P, as it should. If I enter the call manually in the Capture window and tab to the next field it just shows up as K, since that's how it's set up on QRZ.com. I obviosuly need to override this somehow, but I'm not sure how.
The QRZ.COM database entry for K5P is incorrect - it shows 'K' as the
DXCC entity.

It appears that a callbook match overrides an override in DXKeeper.
This seems like a defect to me - a user-provided override should be
the most authoritative source, since errors (evidently) can occur in
callbooks.

73,

~iain / N6ML

Re: Setting an override for Palmyra

W2IRT
 

I agree, Iain, and that's how I thought it worked, to be honest.

Re: Setting an override for Palmyra

Cliff Frescura
 

Right click on the spot in SC then select “Create an override for…”

 

73,

 

Cliff K3LL

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, January 11, 2016 10:37 AM
To: dxlab@...
Subject: [dxlab] Setting an override for Palmyra

 

 

Hi Dave/all,

It's been a while since I needed to do this but how do I tell DX Keeper and DX View to set an override so that K5P (temporarily) shows as Palmyra and not the lower-48? I set the override in Spot Collector but I'm not sure where to set it up in DX Keeper.

If I double-click a spot in SC then the Capture window of DXK shows KH5-P, as it should. If I enter the call manually in the Capture window and tab to the next field it just shows up as K, since that's how it's set up on QRZ.com. I obviosuly need to override this somehow, but I'm not sure how.

Thanks.
Pete, W2IRT

 

Re: Setting an override for Palmyra

Richard B Drake
 

That works but more options such as the ability to provide an expiration date are available if you do it via DXView.

73, Rich - W3ZJ
http://www.w3zj.com


On 1/11/2016 2:17 PM, 'Cliff Frescura' cf@... [dxlab] wrote:

Right click on the spot in SC then select “Create an override for…”

 

73,

 

Cliff K3LL


Re: Setting an override for Palmyra

Richard B Drake
 

I agree Iain. I wasn't aware that it worked that way but I think an override should be absolute.

73, Rich - W3ZJ
http://www.w3zj.com

On 1/11/2016 1:49 PM, iain macdonnell - N6ML ar@... [dxlab] wrote:
It appears that a callbook match overrides an override in DXKeeper.
This seems like a defect to me - a user-provided override should be
the most authoritative source, since errors (evidently) can occur in
callbooks.

73,

    ~iain / N6ML

SC Email Alarm

Rick Arzadon - N8XI
 

Thanks Dave,


I have Email being sent to my Cell Phone.
Just in case anyone needs it.
I have U-Verse and the Outgoing Mail Server
address is outbound.att.net, port is 465 and SSL encryption is checked.

The Cell Phone notification does seem to take awhile.


Question.
SC Config > Email Alarm/ no enable
Using SQL expression (Callsign='VP8STI')
pressing the test button results in a cell phone message
"SpotCollector Notification Test Message"
No Call, Band, etc.

Thanks
73, Rick - N8XI

Re: Setting an override for Palmyra

Julio Peralta
 

Does the override in DXView affect SC or would you have to do it both places?

 

Julio, W4HY

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, January 11, 2016 2:31 PM
To: dxlab@...
Subject: Re: [dxlab] Setting an override for Palmyra

 

 

That works but more options such as the ability to provide an expiration date are available if you do it via DXView.

73, Rich - W3ZJ
http://www.w3zj.com

On 1/11/2016 2:17 PM, 'Cliff Frescura' cf@... [dxlab] wrote:

Right click on the spot in SC then select “Create an override for…”

 

73,

 

Cliff K3LL

 

Re: Setting an override for Palmyra

iain macdonnell - N6ML
 


You can add overrides in either DXView or SpotCollector - they all end up in the same database. Once added using one, the new override should appear in the other. DXView provides access to the "Expiration" field, where SpotCollector does not.

73,

    ~iain / N6ML



On Mon, Jan 11, 2016 at 11:46 AM, 'Julio Peralta' jperalta4@... [dxlab] <dxlab@...> wrote:
 

Does the override in DXView affect SC or would you have to do it both places?

 

Julio, W4HY

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, January 11, 2016 2:31 PM
To: dxlab@...
Subject: Re: [dxlab] Setting an override for Palmyra

 

 

That works but more options such as the ability to provide an expiration date are available if you do it via DXView.

73, Rich - W3ZJ
http://www.w3zj.com

On 1/11/2016 2:17 PM, 'Cliff Frescura' cf@... [dxlab] wrote:

Right click on the spot in SC then select “Create an override for…”

 

73,

 

Cliff K3LL

 


Re: Setting an override for Palmyra

Richard B Drake
 

It works the same and updates the same override list it's just that DXView provides more options.

73, Rich - W3ZJ
http://www.w3zj.com

On 1/11/2016 2:46 PM, 'Julio Peralta' jperalta4@... [dxlab] wrote:

Does the override in DXView affect SC or would you have to do it both places?

 

Julio, W4HY


Re: Setting an override for Palmyra

Julio Peralta
 

Thanks for the clarification.



Julio



From: dxlab@... [mailto:dxlab@...]
Sent: Monday, January 11, 2016 2:54 PM
To: dxlab@...
Subject: Re: [dxlab] Setting an override for Palmyra





It works the same and updates the same override list it's just that DXView provides more options.

73, Rich - W3ZJ
http://www.w3zj.com

On 1/11/2016 2:46 PM, 'Julio Peralta' jperalta4@... [dxlab] wrote:

Does the override in DXView affect SC or would you have to do it both places?



Julio, W4HY

Re: Changing station callsign

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, January 11, 2016 12:50 PM
To: dxlab@...
Subject: [dxlab] Changing station callsign

I have just imported 7000+ q's into DXlabs. The import went very smoothly. However now I find that there are about 1700 Q's that
have the wrong call sign associated with them. Prior to 1/9/2002 I held the call WB4OOJ. Those 1700 Q's are now showing W4HY as the
station call, WB4OOJ as the OP call and W4HY as the owner call. I think at least the Station Call should be WB4OOJ and maybe the
Owners Call should be changed as well.

Either your imported QSOs specified incorrect Station and Owner callsigns for those dates, or your configured DXKeeper to set the
Station and Owner callsigns when you imported an ADIF file containing QSOs prior to 2002-01-09.

I want to make sure that incoming LOTW QSL's will match up properly. Am I right to think those fields need to be changed?

LoTW never sees a QSO's "Station Callsign" item; idetermines a QSO's Station Callsign from the "Callsign Certificate" used to
submit it.

However, if you want the correct "Station Callsign" printed on QSL cards or labels generated by DXKeeper, and in the interest of
good log hygiene and the avoidance of downstream confusion, you should correct the QSOs in your log with erroneous Station and Owner
callsigns.

Instructions for doing this are provided in
<http://www.dxlabsuite.com/dxlabwiki/QSOModifying>

Please do not skip step 1!
In step 2, filter the Log Page Display to contain only QSOs made prior to 2002-01-09 by using the "Advanced Sorts, Filters, and
Modifiers" window's UTC filter panel. Confirm that you've done this correctly by scrolling through the Log Page Display.

In your case, the specific actions to be taken in step 3 are
3a. set the "Item name" selector to "Station_Callsign"

3b. set the "Item new value" box to WB4OOJ

3c. click the Mod button

3.d change the "Item name" selector to "Owner_Callsign"

3.e click the Mod button.

73,

Dave, AA6YQ

Re: Setting an override for Palmyra

Dave AA6YQ
 

That is indeed a defect.

Iain, I've sent you a corrected version of DXKeeper to check; please let me know how it goes.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, January 11, 2016 1:49 PM
To: dxlab
Subject: Re: [dxlab] Setting an override for Palmyra

On Mon, Jan 11, 2016 at 10:36 AM, peter@... [dxlab] <dxlab@...> wrote:



Hi Dave/all,

It's been a while since I needed to do this but how do I tell DX Keeper and DX View to set an override so that K5P (temporarily) shows as Palmyra and not the lower-48? I set the override in Spot Collector but I'm not sure where to set it up in DX Keeper.

If I double-click a spot in SC then the Capture window of DXK shows KH5-P, as it should. If I enter the call manually in the Capture window and tab to the next field it just shows up as K, since that's how it's set up on QRZ.com. I obviosuly need to override this somehow, but I'm not sure how.
The QRZ.COM database entry for K5P is incorrect - it shows 'K' as the DXCC entity.

It appears that a callbook match overrides an override in DXKeeper.
This seems like a defect to me - a user-provided override should be the most authoritative source, since errors (evidently) can occur in callbooks.

73,

~iain / N6ML


------------------------------------
Posted by: iain macdonnell - N6ML <@N6ML>
------------------------------------


------------------------------------

Yahoo Groups Links

Re: Setting an override for Palmyra

iain macdonnell - N6ML
 

On Mon, Jan 11, 2016 at 3:15 PM, ' Dave AA6YQ' @AA6YQ
[dxlab] <dxlab@...> wrote:



That is indeed a defect.

Iain, I've sent you a corrected version of DXKeeper to check; please let me know how it goes.
Looks good!

73,

~iain / N6ML



-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, January 11, 2016 1:49 PM
To: dxlab
Subject: Re: [dxlab] Setting an override for Palmyra

On Mon, Jan 11, 2016 at 10:36 AM, peter@... [dxlab] <dxlab@...> wrote:



Hi Dave/all,

It's been a while since I needed to do this but how do I tell DX Keeper and DX View to set an override so that K5P (temporarily) shows as Palmyra and not the lower-48? I set the override in Spot Collector but I'm not sure where to set it up in DX Keeper.

If I double-click a spot in SC then the Capture window of DXK shows KH5-P, as it should. If I enter the call manually in the Capture window and tab to the next field it just shows up as K, since that's how it's set up on QRZ.com. I obviosuly need to override this somehow, but I'm not sure how.
The QRZ.COM database entry for K5P is incorrect - it shows 'K' as the DXCC entity.

It appears that a callbook match overrides an override in DXKeeper.
This seems like a defect to me - a user-provided override should be the most authoritative source, since errors (evidently) can occur in callbooks.

73,

~iain / N6ML

------------------------------------
Posted by: iain macdonnell - N6ML <@N6ML>
------------------------------------

------------------------------------

Yahoo Groups Links

Re: Problem downloading

Dave AA6YQ
 

Windows requires you to use the Windows Control Panel to uninstall an application *before* you delete the folder in which the application's files reside.

If you delete the folder without first uninstalling the application, then Windows consider the application to still be installed, but you can no longer uninstall it because you've deleted the files required to do so.

At this point, you have two choices:

1. take your chances with a "Registry Cleaner" application, directing it to remove all traces of each DXLab application

2. save all of your critical files, wipe your C: drive, reinstall Windows, and re-install your applications

#2 is onerous, but will leave your system in a known working state.

73,

Dave, AA6YQ

-----Original Message-----
From: Ronald Smith [mailto:rsmith7rd@...]
Sent: Monday, January 11, 2016 2:28 PM
To: @AA6YQ
Subject: RE: [dxlab] Problem downloading

Removed each folder, there is nothing on the hard drive that I can find.

Ron

Re: Setting an override for Palmyra

W2IRT
 

I think part of the problem was that their QRZ page manager listed K5P as the United States, not Palmyra. Since he's currently on the voyage to that island it's not likely to be fixed during the trip.