Date   

Re: 13Colonies how to make SQL Spot Collector filter

Jim N7US
 

I’ve used SpotCollector SQL filters for the 13 Colonies, and they’ve worked well.

 

This year I decided to use N1MM with a User-Defined Contest module for 13 Colonies.  I’m trying to work each of the stations on CW on each band, and N1MM with its Available window is working well for that.

 

https://n1mmwp.hamdocs.com/mmfiles/13colonies-zip/

 

I’ll import the N1MM log into DXKeeper afterwards as I do with all contest logs.

 

73,  Jim N7US

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.io
Sent: Saturday, July 2, 2022 11:52
To: DXLab@groups.io
Subject: Re: [DXLab] 13Colonies how to make SQL Spot Collector filter

 

# More AA6YQ comments below

In the for what it's worth category, here is the SpotCollector filter I use, without using Special Callsigns or Tags. I'm trying to "triple-play" it, so work each one on digital, phone and CW. I remove the callsign from the appropriate line after I've worked it.

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

+ That expression can be simplified to

 

(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)))

# The suggested simplification is appropriate if your goal is to work those 15 stations once in any mode. If the goal is to work them in each of CW, SSB, and FT*, then your original expression is appropriate.

         73,

              Dave, AA6YQ


Re: 13Colonies how to make SQL Spot Collector filter

Dave AA6YQ
 

# More AA6YQ comments below
In the for what it's worth category, here is the SpotCollector filter I use, without using Special Callsigns or Tags. I'm trying to "triple-play" it, so work each one on digital, phone and CW. I remove the callsign from the appropriate line after I've worked it.

(CALLSIGN IN('K2A','K2B','K2C','K2D','K2E','K2F','K2G','K2H','K2I','K2J','K2K','K2L','K2M','WM3PEN','GB13COL','TM13COL') and <ORIGINFILTER> and MODE = 'CW' and <AGEFILTER> and SpotCount > 1) or (CALLSIGN IN('K2A','K2B','K2C','K2D','K2E','K2F','K2G','K2H','K2I','K2J','K2K','K2L','K2M','WM3PEN','GB13COL','TM13COL') and <ORIGINFILTER> and MODE = 'SSB' and <AGEFILTER>) or (CALLSIGN IN('K2A','K2B','K2C','K2D','K2E','K2F','K2G','K2H','K2I','K2J','K2K','K2L','K2M','WM3PEN','GB13COL','TM13COL') and <ORIGINFILTER> and MODE LIKE 'FT*' and <AGEFILTER> and SpotCount > 1)
+ That expression can be simplified to
 
(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)))

# The suggested simplification is appropriate if your goal is to work those 15 stations once in any mode. If the goal is to work them in each of CW, SSB, and FT*, then your original expression is appropriate.

         73,

              Dave, AA6YQ


Re: 13Colonies how to make SQL Spot Collector filter

Dave AA6YQ
 

+ AA6YQ comments below
but i thought i'd be able to readily just have it work like DXCC country does.
+ Implementing Realtime Award Tracking for a 1-week activity held once per year that involves working ~15 stations is not justified, given SpotCollector's filtering capabilities.

      73,

           Dave, AA6YQ


Re: 13Colonies how to make SQL Spot Collector filter

Dave AA6YQ
 

On Sat, Jul 2, 2022 at 04:17 AM, Jon KM8V wrote:
In the for what it's worth category, here is the SpotCollector filter I use, without using Special Callsigns or Tags. I'm trying to "triple-play" it, so work each one on digital, phone and CW. I remove the callsign from the appropriate line after I've worked it.

(CALLSIGN IN('K2A','K2B','K2C','K2D','K2E','K2F','K2G','K2H','K2I','K2J','K2K','K2L','K2M','WM3PEN','GB13COL','TM13COL') and <ORIGINFILTER> and MODE = 'CW' and <AGEFILTER> and SpotCount > 1) or (CALLSIGN IN('K2A','K2B','K2C','K2D','K2E','K2F','K2G','K2H','K2I','K2J','K2K','K2L','K2M','WM3PEN','GB13COL','TM13COL') and <ORIGINFILTER> and MODE = 'SSB' and <AGEFILTER>) or (CALLSIGN IN('K2A','K2B','K2C','K2D','K2E','K2F','K2G','K2H','K2I','K2J','K2K','K2L','K2M','WM3PEN','GB13COL','TM13COL') and <ORIGINFILTER> and MODE LIKE 'FT*' and <AGEFILTER> and SpotCount > 1)
+ That expression can be simplified to
 
(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)))
 
+ which has the advantage of reducing the "work" required after logging a QSO with one of those stations to deleting one instance of a callsign.

 
And to keep track of it, I built a Google Sheet a few years back, which is available for others to use if you like:

https://km8v.com/u/13colsblank

+ Using the <REPORT> and <APPENDREPORT> commands, you can define a DXKeeper script that generates a progress report by filtering the Log Page Display for QSOs with those 15 stations in each of the "modes of interest", sorted by callsign.

       73,

             Dave, AA6YQ

 


Re: 13Colonies how to make SQL Spot Collector filter

bob-w9zv
 

tnx all...

ya, ive been doing it with a simple spreadsheet for years... CW/SSB only as i despise FTx and what its done to 'twitterize' things... 

another is to simply use dxsummit URL, check 'em off one at a time as worked... 

http://www.dxsummit.fi/#/?dx_calls=K2A,K2B,K2C,K2D,K2E,K2F,K2G,K2H,K2I,K2J,K2K,K2L,K2M,GB13COL,WM3PEN,TM13COL
http://www.dxsummit.fi/#/?include_modes=CW&dx_calls=K2A,K2B,K2C,K2D,K2E,K2F,K2G,K2H,K2I,K2J,K2K,K2L,K2M,GB13COL,WM3PEN,TM13COL
http://www.dxsummit.fi/#/?include_modes=PHONE&dx_calls=K2A,K2B,K2C,K2D,K2E,K2F,K2G,K2H,K2I,K2J,K2K,K2L,K2M,GB13COL,WM3PEN,TM13COL 

but i thought i'd be able to readily just have it work like DXCC country does... once worked it automatically comes off the list since no longer "needed"... if i have to manually remove it, i may as well just keep either the spreadsheet/URL solution, as its about the same effort.

but thanks for suggestions.



Re: 13Colonies how to make SQL Spot Collector filter

Jon KM8V
 

In the for what it's worth category, here is the SpotCollector filter I use, without using Special Callsigns or Tags. I'm trying to "triple-play" it, so work each one on digital, phone and CW. I remove the callsign from the appropriate line after I've worked it.

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

And to keep track of it, I built a Google Sheet a few years back, which is available for others to use if you like:

https://km8v.com/u/13colsblank

Here's mine so far this year: https://km8v.com/u/13cols2022

I'll also mention my annual request for SpotCollector leaderboard functionality with an "ignore before date" capability :)

73 de KM8V Jon


Re: 13Colonies how to make SQL Spot Collector filter

RICH NU6T
 



On Friday, July 1, 2022 at 10:23:38 PM PDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

how can i create a filter on the SCollector that does 

Band and Mode and Callsign LIKE 'K2?'  and Unworked

when selected, i only want to see the 'K2?' stations that on cw or ssb are unworked ??? 

putzed a bit, reading help file... seems to work until i add "unworked"... also would like only spots from the last 30min only...  also how to work in GB13COL WM3PEN TM13COL stations in addition to K2?

+ Reviewing

http://www.13colonies.us/

+ the objective is to work 15 specific callsigns, on any band in any mode. If that's correct, then

 

1. add each of those 15 callsigns to SpotCollector's Special Callsigns list with the tag 13colonies

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


2. define a filter to find the stations you haven't worked on bands and modes on which you are QRV,:

(TAGS LIKE ('*13colonies*')) and (Bands in (list of bands I can work)) and (Modes in (list of modes I can work))

for example

(TAGS LIKE ('*13colonies*')) and (BAND in ('80m','40m','30m','20m','15m','10m','6m')) and (MODE in ('CW','SSB'))

3. When you work one of these 15 stations, remove it from SpotCollector's Special Callsign List

+ Good hunting!

      73,

              Dave, AA6YQ

 

 


Re: 13Colonies how to make SQL Spot Collector filter

Dave AA6YQ
 

+ AA6YQ comments below

how can i create a filter on the SCollector that does 

Band and Mode and Callsign LIKE 'K2?'  and Unworked

when selected, i only want to see the 'K2?' stations that on cw or ssb are unworked ??? 

putzed a bit, reading help file... seems to work until i add "unworked"... also would like only spots from the last 30min only...  also how to work in GB13COL WM3PEN TM13COL stations in addition to K2?

+ Reviewing

http://www.13colonies.us/

+ the objective is to work 15 specific callsigns, on any band in any mode. If that's correct, then

 

1. add each of those 15 callsigns to SpotCollector's Special Callsigns list with the tag 13colonies

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


2. define a filter to find the stations you haven't worked on bands and modes on which you are QRV,:

(TAGS LIKE ('*13colonies*')) and (Bands in (list of bands I can work)) and (Modes in (list of modes I can work))

for example

(TAGS LIKE ('*13colonies*')) and (BAND in ('80m','40m','30m','20m','15m','10m','6m')) and (MODE in ('CW','SSB'))

3. When you work one of these 15 stations, remove it from SpotCollector's Special Callsign List

+ Good hunting!

      73,

              Dave, AA6YQ

 

 


13Colonies how to make SQL Spot Collector filter

bob-w9zv
 

how can i create a filter on the SCollector that does 

Band and Mode and Callsign LIKE 'K2?'  and Unworked

when selected, i only want to see the 'K2?' stations that on cw or ssb are unworked ??? 

putzed a bit, reading help file... seems to work until i add "unworked"... also would like only spots from the last 30min only...  also how to work in GB13COL WM3PEN TM13COL stations in addition to K2?


Re: Undocumented updates

Peter Laws / N5UWY
 

n Fri, Jul 1, 2022 at 3:49 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I am an Icom fanboy and I will be the first to say that the company
does not document CI-V well.

+ Icom is better at documenting its CAT commands than most.
Well, that's discouraging!!

Thank you for putting in the work to let us use all these command sets.



--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: QSL "R"

Dave AA6YQ
 

On Fri, Jul 1, 2022 at 05:36 PM, Joe Subich, W4TV wrote:
+ An easier way to accomplish that is to set the "QSL Via" panel to cards or labels, and then click the "Add Needed" button;
I was thinking of the opposite action ... *clearing* QSL_SENT for QSOs
that were not needed.

+ On the "QSL Configuration" window's General tab,  the "Preset QSL Requested checkbox" and "Initialize QSL Sent to 'R' for each imported QSO" option should only be enabled if your intent is to send a QSL card to every QSO partner with whom you log a QSO.

+ These days, most ops only send a QSL card if asked by their QSO partner -- in which case you should check the Capture window's "QSL Requested" box.

+ When its time to print cards or labels, click the "Add Needed" button to generate outgoing QSL cards/labels for which a confirmation would advance your award progress, and then click the "Add Requested" button to generate outgoing QSL cards/labels for the QSO partners who requested one.

        73,

               Dave, AA6YQ 

 

 

 


Re: QRZ.COM lookup delay in importing logs

Dave AA6YQ
 

+ AA6YQ comments below

Living in a rural area, my internet service is pretty slow (~10 Mb/s).  When importing an ADI contest log and DXKeeper configured to look up calls on QRZ, the first few calls imported sometimes result in a “Callbook error for XXXXXX: Name not resolved.”

 

Could a buffering delay be added to compensate for the lookup delay?

+ You could try increasing the "QRZ.com timeout" setting on the Configuration window's Callbook tab, but if Windows reports "Name not resolved", there is nothing I can do about it.

        73,

              Dave, AA6YQ


Re: QSL "R"

Joe Subich, W4TV
 

+ An easier way to accomplish that is to set the "QSL Via" panel to cards or labels, and then click the "Add Needed" button;
I was thinking of the opposite action ... *clearing* QSL_SENT for QSOs
that were not needed.

73,

... Joe, W4TV

On 2022-07-01 7:27 PM, Dave AA6YQ wrote:
+ AA6YQ comments below


One *could* use the "Need" filter (see Help file) and filter the log for
QSOs that are not needed, then use the "Modify" feature on the Advanced
filters screen to clear QSL_SENT, if one did not want to "waste" a card
for unneeded QSOs. It might be possible to automate the operation by
writing a script (I have not tested the possibility) if it is done on a
regular basis.
+ An easier way to accomplish that is to set the "QSL Via" panel to cards or labels, and then click the "Add Needed" button; unconfirmed QSOs whose confirmations will advance the awards you configured DXKeeper to pursue will be added to the QSL card.
73,
Dave, AA6YQ


QRZ.COM lookup delay in importing logs

Jim N7US
 

Living in a rural area, my internet service is pretty slow (~10 Mb/s).  When importing an ADI contest log and DXKeeper configured to look up calls on QRZ, the first few calls imported sometimes result in a “Callbook error for XXXXXX: Name not resolved.”

 

Could a buffering delay be added to compensate for the lookup delay?

 

73,  Jim N7US

 


Re: QSL "R"

Dave AA6YQ
 

+ AA6YQ comments below
One *could* use the "Need" filter (see Help file) and filter the log for
QSOs that are not needed, then use the "Modify" feature on the Advanced
filters screen to clear QSL_SENT, if one did not want to "waste" a card
for unneeded QSOs. It might be possible to automate the operation by
writing a script (I have not tested the possibility) if it is done on a
regular basis.

+ An easier way to accomplish that is to set the "QSL Via" panel to cards or labels, and then click the "Add Needed" button; unconfirmed QSOs whose confirmations will advance the awards you configured DXKeeper to pursue will be added to the QSL card. 

     73,

            Dave, AA6YQ


Re: QSL "R"

Joe Subich, W4TV
 

On 2022-07-01 1:33 PM, Earl Needham wrote:
I have a habit of setting ALL QSL's to "R when I work somebody -- IOW
I request QSL via LoTW, card, and eQSL.
You can direct DXKeeper to *automatically* set QSL_Sent, LotW_QSL_Sent
and eQSL_QSL_Sent to 'R' by checking the appropriate boxes in the
General, LotW and eQSL tabs of the QSL Config respectively.

Typically, one would upload to LotW daily/weekly - that will also
automatically set LotW_QSL_RCVD = 'R'.

And second -- is there an automatic way to set the other two to, say,
a blank when I receive a QSL via any method?
No, confirming a QSO by one method will not clear QSL_Sent for the other
two. As Dave pointed out, in general, since eQSL confirmations do not
count for ARRL awards one would not want receipt of an eQSL
"confirmation" to clear requests for cards/LotW.

One *could* use the "Need" filter (see Help file) and filter the log for
QSOs that are not needed, then use the "Modify" feature on the Advanced
filters screen to clear QSL_SENT, if one did not want to "waste" a card
for unneeded QSOs. It might be possible to automate the operation by
writing a script (I have not tested the possibility) if it is done on a
regular basis.


73,

... Joe, W4TV

On 2022-07-01 1:33 PM, Earl Needham wrote:
I have a habit of setting ALL QSL's to "R when I work somebody -- IOW I
request QSL via LoTW, card, and eQSL.
Two questions -- first, is this ridiculous?
And second -- is there an automatic way to set the other two to, say, a
blank when I receive a QSL via any method?
Tnx,
Earl
KD5XB


Re: Undocumented updates

Dave AA6YQ
 

+ AA6YQ comments below
I am an Icom fanboy and I will be the first to say that the company
does not document CI-V well.

+ Icom is better at documenting its CAT commands than most. Recall that I had to write the initial documentation for the Flex Signature's ethernet API by asking questions of Flex engineers.

+ Until recently, I would have said that Yaesu is the worst at it - but then  I encountered Thetis, which is unbelievable poor.

+ Recall the FT-817/857/897 disaster, in which an undocumented command that writes to non-volatile memory addresses was used to modify radio parameters not accessible via the documented CAT command set. One logging application took advantage of this, ignoring the point that non-volatile memories have a finite "write budget". Exceed that budget, and the memory stops working, which bricks the radio. Evidently, Yaesu no longer has access to replacement parts, so those radios are not reparable.

de AA6YQ


Re: Undocumented updates

Peter Laws / N5UWY
 

On Fri, Jul 1, 2022 at 3:02 PM k6xt <k6xt@...> wrote:

Referring to our recent IC7300 XFC discussion how can I help you implement the discussed undocumented feature, should you decide to add it to your todo list? If you need one I'll send you my IC7300.

Incidentally my statement that the capability is undocumented referred to the user manual. Not a programmer, I don't know what assets are made available by Icom.
I am an Icom fanboy and I will be the first to say that the company
does not document CI-V well.

On my IC-910H, the CI-V command table is poorly rendered in the docs
and makes it appear that you can't turn on the transmitter via CI-V
... but you can ... and now Commander knows about this feature under
the name "IC-910HA". A fake ID because it's not clear which of the
versions of that radio supports it (910A, 910D, 910H, 911, etc) so
doing it like that is probably the best way to handle it.



--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: Undocumented updates

Dave AA6YQ
 

+ AA6YQ comments below
Reading the update notes for Commander 15.4.4 I see an undocumented feature on a Yaesu rig that wasn't ignored..

Referring to our recent IC7300 XFC discussion how can I help you implement the discussed undocumented feature, should you decide to add it to your todo list? If you need one I'll send you my IC7300.

Incidentally my statement that the capability is undocumented referred to the user manual. Not a programmer, I don't know what assets are made available by Icom.

+ "Supports the undocumented FT-757GXII meter reading CAT command" in Commander 15.4.4 was low risk: that radio's functionality cannot be changed via a firmware update, and the change supports a capability that isn't already present. If it were to fail due to a future action by Yaesu, users would be in no worse shape than they were before Commander 15.4.4.

+ Icom radios provide a Split mechanism that works well for working DX stations operating split. Exploiting undocumented commands in an Icom radio that is under active development with firmware updates to replicate functionality that already exists would be risky, and would not be a good use of my development time compared to alternative uses of that time.

          73,

               Dvae, AA6YQ

 


Undocumented updates

k6xt
 

Hi Dave

Reading the update notes for Commander 15.4.4 I see an undocumented feature on a Yaesu rig that wasn't ignored..

Referring to our recent IC7300 XFC discussion how can I help you implement the discussed undocumented feature, should you decide to add it to your todo list? If you need one I'll send you my IC7300.

Incidentally my statement that the capability is undocumented referred to the user manual. Not a programmer, I don't know what assets are made available by Icom.

73 Art K6XT/W7NTA

1521 - 1540 of 210374