Date   

Re: Button sequence not being retained

Norm - KC1BMD
 

Well, I guess it's been a while and I completely forgot about the User-defined Control Sets that I had set up and obviously needed to edit!... he says as he slowly wipes the egg from his face.
--
73, Norm/KC1BMD


Re: Button sequence not being retained

Dave AA6YQ
 

+ AA6YQ comments below
I programmed several sequences a while ago and they work fine for two radios. When I load a new sequence from the Commander sequence folder for the first radio (which is powered up), it loads and runs OK. If I switch to the second radio (which is powered down) it also loads and runs fine. However, if I switch back to the first radio, the sequence/button is blank and non-functional. If I then switch to the second radio again, that sequence/button is also blank and non-functional. Any idea why this sequence cannot be retained for both radios? It happens to be the "ALT F9" button I am using

+ See this description of "User-defined control set":

https://www.dxlabsuite.com/commander/Help/ControllingMultipleRadios.htm#User-defined%20Control%20Set

      73,

           Dave, AA6YQ

 


Button sequence not being retained

Norm - KC1BMD
 

I programmed several sequences a while ago and they work fine for two radios. When I load a new sequence from the Commander sequence folder for the first radio (which is powered up), it loads and runs OK. If I switch to the second radio (which is powered down) it also loads and runs fine. However, if I switch back to the first radio, the sequence/button is blank and non-functional. If I then switch to the second radio again, that sequence/button is also blank and non-functional. Any idea why this sequence cannot be retained for both radios? It happens to be the "ALT F9" button I am using. 

--
73, Norm/KC1BMD


Re: Spotcollector Audio Alert Issues

Dave AA6YQ
 

+ AA6YQ comments below

I have Spotcollector set to give audio alerts for needed DX. I am having two issues with this.

1. The audio is so disjointed that it's hard to tell what the call sign is and what the related info is

2. The info for the audio alert spots never shows up in my Spotcollector display.

Do I have a setup issue? If so, what needs to be done to correct these issues.

+ Is this new behavior, Barry, or has SpotCollector always done this?

+ Starting with your first issue, please reboot Windows into "Safe Mode with Networking", and start SpotCollector by using Windows Explorer to navigate to your SpotCollector folder and double-clicking the entry for

SpotCollector.exe

+ Are SpotCollector's audio announcements still garbled?

73,

Dave, AA6YQ


Re: ITU Zones with leading 0 (Zero)?

Dave AA6YQ
 

+ AA6YQ comments below

+ In followup, DXKeeper imports <CQZ:2>02 as the single digit 2, and
<ITUZ:2>01 as the single digit 1 -- so however Norm got leading zeroes
in his CQZ and ITUZ items, it wasn't by importing them from an ADIF
file.
I have 79 such entries in my log - all of them are confirmed via LotW.
I suspect DXKeeper dutifully updated the entry from the LotW downloads.

I looked at one such call and the LotW "Details" shows:
"ITU Zone 08 (Inferred; user did not specify zone)"

+ Thanks, Joe. Your hypothesis is correct: LoTW is reporting both CQ zones and ITU zones with a leading zero, but DXKeeper is failing to remove the leading zero from the ITU zone before saving it in a QSO that did not specify an ITU zone.

+ I will correct this in the next version of DXKeeper. That next version will also include a script that users can run to eliminate the leading zeros in ITU zones.

+ The WITU progress report does correctly interpret ITU zones in logged QSOs that have a leading zero.

73,

Dave, AA6YQ


Spotcollector Audio Alert Issues

Barry Priddy
 


I have Spotcollector set to give audio alerts for needed DX.  I am having two issues with this.

1.  The audio is so disjointed that it's hard to tell what the call sign is and what the related info is

2.  The info for the audio alert spots never shows up in my Spotcollector display.

Do I have a setup issue?  If so, what needs to be done to correct these issues.

Barry Priddy - K5VIP


Re: ITU Zones with leading 0 (Zero)?

Norm - KC1BMD
 

Thanks Dave and Joe for the follow-up. I only saw the leading zeros with ITU Zone (not CQ Zone) and the majority were "07", "08". I edited them but understand they might come back depending on how updates from LoTW might affect it later. 

--
73, Norm/KC1BMD


Re: ITU Zones with leading 0 (Zero)?

Joe Subich, W4TV
 

+ In followup, DXKeeper imports <CQZ:2>02 as the single digit 2, and <ITUZ:2>01 as the single digit 1 -- so however Norm got leading zeroes in his CQZ and ITUZ items, it wasn't by importing them from an
ADIF file.
I have 79 such entries in my log - all of them are confirmed via LotW.
I suspect DXKeeper dutifully updated the entry from the LotW downloads.

I looked at one such call and the LotW "Details" shows:
"ITU Zone 08 (Inferred; user did not specify zone)"

73,

... Joe, W4TV


On 2021-03-21 9:14 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

For some reason after importing my HRD logbook into DXK I noticed that some ITU Zones that would ordinarily have a single digit contain a leading 0 (zero). There are no errors shown when pulling up the QSO in DXK., Is that going to cause any issues down the line for anything?

+ Not that I know of.
Me neither. The vast majority of my logged QSOs with zones 1-9 do not have the leading zero, but some do. I can't imagine it mattering for anything of significance.

If so, can someone suggest and easy way to search for these and correct them?

+ To change ITU Zone 01 to 1, en masse,

1. backup your log (Configuration window, Log tab, Backup button)

2. filter the Log Page Display with

ITUX='01'
I think you meant "ITUZ".
+ Yes, I meant ITUZ. My telepathic keyboard doesn't handle QRN well.
+ In followup, DXKeeper imports <CQZ:2>02 as the single digit 2, and <ITUZ:2>01 as the single digit 1 -- so however Norm got leading zeroes in his CQZ and ITUZ items, it wasn't by importing them from an ADIF file.
73,
Dave, AA6YQ


Re: ITU Zones with leading 0 (Zero)?

Dave AA6YQ
 

+ AA6YQ comments below

For some reason after importing my HRD logbook into DXK I noticed that some ITU Zones that would ordinarily have a single digit contain a leading 0 (zero). There are no errors shown when pulling up the QSO in DXK., Is that going to cause any issues down the line for anything?

+ Not that I know of.
Me neither. The vast majority of my logged QSOs with zones 1-9 do not have the leading zero, but some do. I can't imagine it mattering for anything of significance.


If so, can someone suggest and easy way to search for these and correct them?

+ To change ITU Zone 01 to 1, en masse,

1. backup your log (Configuration window, Log tab, Backup button)

2. filter the Log Page Display with

ITUX='01'
I think you meant "ITUZ".

+ Yes, I meant ITUZ. My telepathic keyboard doesn't handle QRN well.

+ In followup, DXKeeper imports <CQZ:2>02 as the single digit 2, and <ITUZ:2>01 as the single digit 1 -- so however Norm got leading zeroes in his CQZ and ITUZ items, it wasn't by importing them from an ADIF file.

73,

Dave, AA6YQ


Re: ITU Zones with leading 0 (Zero)?

Norm - KC1BMD
 

Thanks Iain, I had understood in step 2 to use "ITUZ" instead of "ITUX" and also in step 3 not "CQZ" since I was modifying IT Zones. Easy enough to do.
--
73, Norm/KC1BMD


Re: ITU Zones with leading 0 (Zero)?

iain macdonnell - N6ML
 

On Sun, Mar 21, 2021 at 10:24 AM Dave AA6YQ <aa6yq@ambersoft.com> wrote:

For some reason after importing my HRD logbook into DXK I noticed that some ITU Zones that would ordinarily have a single digit contain a leading 0 (zero). There are no errors shown when pulling up the QSO in DXK., Is that going to cause any issues down the line for anything?

+ Not that I know of.
Me neither. The vast majority of my logged QSOs with zones 1-9 do not
have the leading zero, but some do. I can't imagine it mattering for
anything of significance.


If so, can someone suggest and easy way to search for these and correct them?

+ To change ITU Zone 01 to 1, en masse,

1. backup your log (Configuration window, Log tab, Backup button)

2. filter the Log Page Display with

ITUX='01'
I think you meant "ITUZ".

73,

~iain / N6ML


3. use the "Modify QSOs" panel on the "Advanced Sorts, Filters, and Modifiers" window to change the CQZ items in each QSO in the Log Page Display to

1


+ Repeat the above steps for the other 9 single-digit ITU zones.


updated eQSL AG and LoTW databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ


Re: How Do I Designate a POTA QSO in DXK

Dave AA6YQ
 

+ AA6YQ comments below

Dave - OK, understand. Yes I did create the original category name with a slash

+ Thanks, Paul; that led me to the defect. It's corrected in the next version of DXKeeper.

73,

Dave, AA6YQ


Re: How Do I Designate a POTA QSO in DXK

w2eck
 

Dave - OK, understand. Yes I did create the original category name with a slash

73 Paul w2eck


Re: ITU Zones with leading 0 (Zero)?

Norm - KC1BMD
 

Thanks Dave!
--
73, Norm/KC1BMD


Re: How Do I Designate a POTA QSO in DXK

Dave AA6YQ
 

+ AA6YQ comments below

Dave - No, I did not use a script. Will that generate additional data ?

+ No, invoking the progress report from a script produces the same progress report as invoking it from the Main window's "Check Progress" tab. I'm trying to determine how the forward slash you placed in your report title was included in the report filename when there's code that should have automatically replaced it with an underscore.

73,

Dave, AA6YQ


Re: ITU Zones with leading 0 (Zero)?

Dave AA6YQ
 

For some reason after importing my HRD logbook into DXK I noticed that some ITU Zones that would ordinarily have a single digit contain a leading 0 (zero). There are no errors shown when pulling up the QSO in DXK., Is that going to cause any issues down the line for anything?

+ Not that I know of.

If so, can someone suggest and easy way to search for these and correct them?

+ To change ITU Zone 01 to 1, en masse,

1. backup your log (Configuration window, Log tab, Backup button)

2. filter the Log Page Display with

ITUX='01'

3. use the "Modify QSOs" panel on the "Advanced Sorts, Filters, and Modifiers" window to change the CQZ items in each QSO in the Log Page Display to

1


+ Repeat the above steps for the other 9 single-digit ITU zones.

73,

Dave,


Re: Final clean up of log

Jim Miller, AB3CV
 

Hi Dave

I understand. Credit onlys were generated before he decided to undertake a full gathering of old QSOs. 

I think we can look at the number of Credit Only QSOs by using the filter. Now that we know we can fall back on generating those if needed. We can just delete all the Credit Only QSOs, complete the import process and see where that takes us.

jim ab3cv


Re: Final clean up of log

Dave AA6YQ
 

+ AA6YQ comments below

A friend has been moving to DXLabs and slowly finding all his logs from previous software.

In the meantime even with a fairly large but still partial status on his DXK log he did a download of credits granted and allowed credit only QSOs to be created for any missing from his log. That was successful in that his Verified/Confirmed/Worked counts now agree between ARRL and the RAT summary table.

+ I would have strongly recommended against generating "credit-only QSOs" when there were more logs to be imported.

Now he believes he has found sufficient old log scraps that contain most of the previously missing QSOs that if imported to DXK would make those credit only QSOs duplicates.

He would like to find those and delete the credit only dupe and "move" the V to the actual valid QSO.

Is there a batch process that could work for this?

+ No. Automation is limited to recommended workflows.

73,

Dave, AA6YQ


Re: DxCommander and inadvertent Xmt

Dave AA6YQ
 

I set everything up initially per the WSJT-X users manual. The inability to log might have been that Spot Collector wasn't running. Not sure about that.

+ You need either SpotCollector or JT-Alert running. "Getting Started with K1JT modes and DXLab" summarizes the two topologies, and provides links to step-by-step instructions for configuring each:

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


However, the inadvertent transmission is being commanded by the Commander when first starting commander. For some reason, PTT is defaulting to Xmt. As I can see it, this is only related to Commander.

+ How is Commander connected to your FT991A?

+ To what are the DTR and RTS selectors set in the "Primary CAT Serial Port" panel on the Ports tab of Commander's Configuration window?

+ Please do the following:

1. reboot Windows

2. put your FT991A on a clear frequency and set its RF output power to 0

3. start Windows Explorer, navigate to your Commander folder, and double-click the entry for

CI-V Commander.exe

+ Does your FT991A switch from RX to TX?

+ If so, then

4. click the RX button in the PTT panel on Commander's Main window

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

6. terminate Commander

7. in Windows Explorer, navigate to your Commander folder, and double-click the entry for

CI-V Commander.exe

8. click the RX button in the PTT panel on Commander's Main window

9. on the Configuration window's General tab, uncheck the "Log debugging info" box

10. terminate Commander

11. attach the errorlog.txt file from you Commander folder to an email message that answers the questions posed above, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

3521 - 3540 of 204068