Date   
Re: Label printer commendations?

Jim Miller, AB3CV
 

Thanks all!

Jim ab3cv

Re: Commander Help needed for ICOM (TUNE Button)

Dave AA6YQ
 

+ AA6YQ comments below

After 20x <wait> it worked.... is there a <wait,20> command?

+ No: there has been no previously-identified need. The number of <wait> instructions required will vary as a function of the Command Interval you've specified.

Is there a way to ask the radio if its back in standby before moving forward?
My tuner is fast but there are times where it might take extra time.

+ Does the Icom 7610's CI-V instruction set include a way to "test" the tuner to determine if it's completed its last operation?

+ What is the worst case amount of time that Icom states the tuner might take to complete an operation?

73,

Dave, AA6YQ

Re: Commander Help needed for ICOM (TUNE Button)

W8DSB
 

After 20x <wait> it worked.... is there a <wait,20> command?
Is there a way to ask the radio if its back in standby before moving forward?
My tuner is fast but there are times where it might take extra time.

Re: 4x6 QSL Cards are now too big?

WA8Y Steven
 

Got it working.
It was a printer issue.
Once I set the printer to match the DXK settings everything  printed as normal

4x6 QSL Cards are now too big?

WA8Y Steven
 

DXK 15.3.1
My QSL Cards are 4x6 inches.
Today, DXKeeper is telling me my "Specified QSL card height is too large (maximum is 3.883333 inches).
Clicking on "QSL Config" /Cards tab/ Card Dimensions" are set to;
Width   6 inches,    Side borders  0.25"
Height 4 inches.    Top border.    O.25"   
2nd row offset. 0.25"

Did something change?
Steve WA8Y

Re: Error code 1010

Dave AA6YQ
 

+ AA6YQ comments below

Looked thru all messages and documentation I could find before posting this...

I'm new to ClubLog and am trying to upload my log from DXK. I'm pretty sure I configured it correctly. The log contains 16,000 QSOs, so it parses them into groups of 5000. Using the Check Progress => Club Log K1TO button labeled Upload. But uploading the first one consistently returns this as soon as it reaches 5000: "Upload File to Club Log: error code: 1010". CTRL/click returns the same error code.

TIA for any help.

+ So that I can see what's going on, please do the following:

1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper

4. direct DXKeeper to upload your QSOs to Club Log

5. when the error message appears,

5a. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box

5b. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

Thanks!

73,

Dave, AA6YQ

Re: Commander Help needed for ICOM (TUNE Button)

Dave AA6YQ
 

+ AA6YQ comments below

Trying to setup my 7610 to tune using a Sequences. Every command seems to work on its own but when running them together it fails to turn the power back up. I tried installing a "wait" with no help.

+ <wait> only inserts one "command interval" of wait time. Try inserting ten <wait> instructions. Any difference in behavior?

73,

Dave, AA6YQ



TUNE MAIN VFO

<led red>
Select Main VFO
FEFE<CIV>E007D0FD
Set Power 35 %
FEFE<CIV>E0140A0090FD
Turn Tuner Off
FEFE<CIV>E01C0100FD
Turn Tuner On
FEFE<CIV>E01C0101FD
Tune Tuner
FEFE<CIV>E01C0102FD
Wait
<wait>
Tuned!!!
<led green>
Set Power 85 %
FEFE<CIV>E0140A0219FD
<END>

Error code 1010

Dan <k1to@...>
 

Looked thru all messages and documentation I could find before posting this...

I'm new to ClubLog and am trying to upload my log from DXK.  I'm pretty sure I configured it correctly.  The log contains 16,000 QSOs, so it parses them into groups of 5000.  Using the Check Progress => Club Log K1TO button labeled Upload.  But uploading the first one consistently returns this as soon as it reaches 5000:  "Upload File to Club Log: error code: 1010". CTRL/click returns the same error code. 

TIA for any help.

vy 73, Dan K1TO

Commander Help needed for ICOM (TUNE Button)

W8DSB
 

Trying to setup my 7610 to tune using a Sequences. Every command seems to work on its own but when running them together it fails to turn the power back up. I tried installing a "wait" with no help.

TUNE MAIN VFO
 
<led red>
Select Main VFO
FEFE<CIV>E007D0FD
Set Power 35 %
FEFE<CIV>E0140A0090FD
Turn Tuner Off
FEFE<CIV>E01C0100FD
Turn Tuner On
FEFE<CIV>E01C0101FD
Tune Tuner
FEFE<CIV>E01C0102FD
Wait
<wait>
Tuned!!!
<led green>
Set Power 85 %
FEFE<CIV>E0140A0219FD
<END>

Re: Label printer commendations?

Dave AA6YQ
 

+ AA6YQ comments below

I'm thinking of switching to roll labels with a smaller roll label printer. Up to now I've used my laser printer to print cards and outgoing and return envelopes.

Any recommendations on a printer for this to be driven by DXKeeper?

+ I use a Dymo "LabelWriter 450 Turbo". Prints well, and has been reliable.

73,

Dave, AA6YQ

Re: DXLab Apps With SDR-Bridge and CW Skimmer

Dave AA6YQ
 

+ AA6YQ comments below

Dave: re the origin filter -- I am setting it to only pass spots from [?] to just see my skimmer. I add "NAE" if I want to see what others in my part of the country are seeing. Sound correct?

+ The first rule of software engineering: "if it ain't broke, don't fix it!"

+ That said, you might filtering with the Network field a more robust way to identify Spot Database Entries created by your skimmer.

73,

Dave, AA6YQ

Re: Label printer commendations?

Tom LeClerc
 

Dymo label printers.  Very reliable and easy to set up.  Mine is the turbo 450 but I have used others with equal success...

73, Tom W1TJL 

On Fri, Dec 27, 2019, 13:23 Jim Miller, AB3CV <jtmiller47@...> wrote:
I'm thinking of switching to roll labels with a smaller roll label printer. Up to now I've used my laser printer to print cards and outgoing and return envelopes.

Any recommendations on a printer for this to be driven by DXKeeper?

Thanks

Jim ab3cv

Label printer commendations?

Jim Miller, AB3CV
 
Edited

I'm thinking of switching to roll labels with a small roll label printer. Up to now I've used my laser printer to print cards and outgoing and return envelopes.

I send out perhaps a card a month on average. All my buro cards go thru GlobalQSL. Most of my requests are via one of the OQRS services.

Any recommendations on a printer for this to be driven by DXKeeper?

Thanks

Jim ab3cv

Re: SC Filters

Rod Greene
 

Dave, (and Joe) -

Again thanks for your suggestions and explanations. This software is amazing extremely well designed. I will work through what you have suggested below.

73 and HNY - Rod/w7zrc

On Thursday, December 26, 2019, 5:46:57 PM MST, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

I have the SC Filter for the Origin field turned on (as well as the Band filter) for only NA; NA-E, NA-M and NA-W checked, but spots continue to show up with the Origin of other locations like EU, AS and AF. I only want to see spots from NA.

+ SpotCollector's Spot Database contains on entry for each active station operating in a particular mode near a particular frequency.

+ When a new spot arrives, SpotCollector checks to see if it already has an entry for the spot's callsign in the spot's mode near the spot's frequency. If so, it updates the existing Spot Database Entry with information obtained from the spot -- like the location of the spotting station. If there's no existing entry in the Spot Database, SpotCollector creates one, and populates it from the spot.

+ The Spot Database Display provides a filtered view of the Spot Database, e.g. "all active stations on 20m", or "all active stations in Asia operating in FT8", or "all active stations with whom a confirmed QSO would advance progress towards the awards specified on the Awards tab of DXKeeper's Configuration window.

+ SpotCollector divides the world into 8 regions: Europe (EU), Africa (AF), eastern North America (NA-E), central North America (NA-M), western North America (NA-W), Asia (AS), and Oceana (OC). The station associated with a Spot Database Entry will have been spotted from at least one of the regions, but may have been spotted from several regions. PY2XC on 30m FT8, for example has been spotted from Europe, Africa, all three regions of North  America, and Asia.

+ When you configure SpotCollector's Origin filter to show only active stations spotted from NA-E, NA-M and NA-W, you will only see entries whose NAE, NAM, or NAW fields in their Spot Database Entry contain a Y. The entry for PY2XC would be shown, even though it has been spotted from Europe and Asia: it's means the criterion of having been spotted from NA-E, NA-M and NA-W.

+ Note that a Spot Database Entry's Origin field shows the location of the most recent station to spot the entry's station. To fully understand from where an active station has been spotted, you must cojnsider its EU, AF, NAE, NAM, NAW, AS, and OC fields. Take a look at this annotated screenshot:

<https://www.dxlabsuite.com/Wiki/Graphics/SpotCollector/SpotDatabaseDisplayAnnotated.jpg>

+ If you only want to see active stations spotted form North America, the SQL expression to use would be

(NAE='Y') or (NAM='Y') or (NAW='Y')

+ This article expands on the information provided above:

<https://www.dxlabsuite.com/dxlabwiki/CollectingSpots>


Do I need to change my filter selections?

+ If you're a DXer, I suggest that you not filter by the location of spotting stations, as doing so will hide active DX stations that you could work. Just because P5DX is first spotted from Japan doesn't mean you won't be able to work it, but filtering with the above SQL expression would hide the P5DX entry from you until someone from North America spots P5DX.

+ If your goal is to hide Spot Database Entries for stations you are unlikely to hear, see

<https://www.dxlabsuite.com/dxlabwiki/HidingDXYouCantHear>


      73,


            Dave, AA6YQ




Re: DXLab Apps With SDR-Bridge and CW Skimmer

sv.pleiades
 

Dave:  re the origin filter -- I am setting it to only pass spots from [?] to just see my skimmer. I add "NAE" if I want to see what others in my part of the country are seeing.  Sound correct?

73, Tom
K1FR

Re: SpotCollector Font Color for unworked / unconfirmed

Curtis WX4W
 

Thanks for the explanation my friend.

Re: reconcile LOTW submission

Dave AA6YQ
 

+ AA6YQ comments below

When I click assemble submission in Dx keeper, I have 114 qsos to submit.....when I look on the LOTW website, I only have 109.....how can I find the "missing" 5 in DXK and mark them for no submission?

+ There are no "missing 5". LoTW is not aware of your award objectives, and the algorithm it uses to select confirmed QSOs to submit is suboptimal. I suggest that you direct LoTW to submit the QSOs identified by DXKeeper for submission, as described in step 3 of

<https://www.dxlabsuite.com/dxlabwiki/SubmitLotW>

+ In the unusual case that one of the QSOs that DXKeeper recommends for submission is not shown as confirmed in LoTW, clear that QSO's "LoTW QSL Rcvd" item, direct DXKeeper to generate a new submission, and again direct LoTW to submit the QSOs identified by DXKeeper.

73,

Dave, AA6YQ

Re: SpotCollector Font Color for unworked / unconfirmed

Dave AA6YQ
 

+ AA6YQ comments below

Dave those steps worked and I now do not see any enteries when I click ctrl-need. Thanks. I did have step 1 checked i.e. On the Awards tab of DXKeeper's Configuration window, check the "Automatically recompute realtime award tracking" box if it isn't already checked. I'm just curious why I had to do that since you note about Step 1 states I should not have had to do that?

+ Determining whether or not a QSO with a particular callsign on a particular band in a particular mode would advance your DXCC award progress can be straightforwardly accomplished: scan all QSOs in the log. When considering a newly-created Spot Database Entry, this procedure would take too long in a log containing 5K QSOs, much less 50K or 500K QSOs. Limiting the scan to logged QSOs with the callsign's DXCC entity would still be too slow given the rate at which new Spot Database Entries can be created.

+ For DXCC, DXLab solves this problem by maintaining a "DXCC Progress table" in your log. This table has one row for each DXCC entity, with columns for each band and mode valid for DXCC. Whenever you take an action that "increases" your DXCC award status - like logging a new QSO, or marking a QSO "confirmed by QSL card", or receiving an LoTW confirmation -- this DXCC progress is appropriately updated. If you take an action that potentially to reduces your DXCC award status -- like changing a logged QSO's DXCC country from X to Y, or marking a logged QSO as invalid for DXCC, or deleting a logged QSO - - the process of updating the log's DXCC Progress table is not straightforward.

+ Suppose, the P5 row in your DXCC Progress table shows a C (confirmed) in the 20m column and a C in the CW column. You are informed that your logged QSO with P5DX on 20m CW is invalid for DXCC, so you set its "QSL Rcvd" item to 'I'. Should this change the 20m and CW columns in the P5 row? The only way to tell is by examining all logged QSOs with P5. If you have a logged QSO with P5 on 40m CW, and another logged QSO with P5 on 20m SSB, for example, then no change to the P5 row would be required.

+ If you have the "Automatically recompute realtime award tracking" option enabled on the Awards tab of DXKeeper's Configuration window, DXKeeper will react to your marking your logged QSO with P5DX on 20m CW as "invalid for DXCC" by scanning all of your logged QSOs with P5, and updating the P5 row of your DXCC progress table accordingly. This is much faster than scanning every QSO in your log, and is only necessary after a change that potential reduces your award progress, which is not a frequent situation.

+ DXKeeper doesn't just maintain a DXCC progress table; it maintains one for IOTA, one for DX Marathon, one for VUCC, one for WAS, one for WAZ, and one for WPX. Collectively, this functionality is referred to as "Realtime Award Tracking"; it enables SpotCollector to quickly determine whether a newly-created Spot Database Entry should be considered "needed" with respect to your specified award objectives on the Awards tab of DXKeeper's Configuration window. Click the RAT button on the Main window's "Log QSOs" tab, and DXKeeper's "Realtime Award Tracking" window will appear. Each tab of this window provides a view on an award's progress table - with the ability to filter by band, mode, and award progress.

+ There are some actions for which performing automatic recomputation one QSO at a time would be slower than performing the action without automatic recomputation and then recomputing all award progress by scanning every QSO in the log. Examples: deleting a significant number of logged QSOs, or changing the DXCC entity of a significant number of logged QSOs using the "Advanced Sorts, Filters, and Modifiers" window's "Modify QSOs" tab. When you initiate such an operation, DXKeeper offers to not perform automatic recomputation after each QSO is deleted or modified, with the expectation if you agree that you will initiate a full Recomputation after completing all of your changes.

+ Given that you have the "Automatically recompute realtime award tracking" option enabled, I don't know what steps you might have taken that left your log in a state where its DXCC progress table was inconsistent with respect to your logged QSOs with respect to DXCC award progress. There are no reported but uncorrected defects in this functionality (or at this moment, anywhere else in DXKeeper). If the situation recurs, let me know and we'll track down the root cause.

73,

Dave, AA6YQ

Re: DXLab Apps With SDR-Bridge and CW Skimmer

Dave AA6YQ
 

+ AA6YQ comments below

Finally had some time to chase this down a bit more. Similar problems with the older version. Per Andy's (K3UC) suggestion (thanks Andy!) I tried Slice Master as well. Better, but still some instability with CW-Skimmer when DXLab apps were running. Found some references from other hams using similar lash up with Flex, and sounds like my experience may be fairly common. I do not have a coherent, definitive description of details, but it appears that the Flex API was being confused by multiple apps trying to control slice frequencies.

But - the bottom line good news? I was definitely making things too hard. A bit of reading on DXLab site made me realize I could do everything I wanted to do all within DXLab apps. I was wanting to use Skimmer to combine my spots with external spots and put them up on the Flex panadapter. Works like a champ as long as I check spot origins filters properly. Should have tried the easy route first.

+ I'm glad to hear that you've got things working as desired, Tom. Please elaborate on "Works like a champ as long as I check spot origins filters properly".

73,

Dave AA6YQ

reconcile LOTW submission

Jamie WW3S
 

When I click assemble submission in Dx keeper, I have 114 qsos to submit.....when I look on the LOTW website, I only have 109.....how can I find the "missing" 5 in DXK and mark them for no submission?