Date   

Re: How do I connect DXlabs to CW Skimmer???

iain macdonnell - N6ML
 

Hi Brian,

See: http://www.dxlabsuite.com/dxlabwiki/CWSkimmer

73,

~iain / N6ML

On Fri, Jul 13, 2012 at 9:35 AM, Scouse <g0vax67@gmail.com> wrote:



Hi All,
I have been pulling what little hair I have out trying to connect the
DXLabb
s Suite to CW Skimmer,,,has anyone had success?? If so, how did you do in
(In an easy step by step way)

Many Thanks

Brian G0VAX


Re: How do I connect DXlabs to CW Skimmer???

Joe Subich, W4TV
 

There are several ways documented in the DXLab Suite WiKi. Your
particular installation will depend on the hardware (separate SDR,
LP-Pan, Softrock, etc.) being used for CW Skimmer.

73,

... Joe, W4TV

On 7/13/2012 12:35 PM, Scouse wrote:
Hi All,
I have been pulling what little hair I have out trying to connect the DXLabb
s Suite to CW Skimmer,,,has anyone had success?? If so, how did you do in (In an easy step by step way)

Many Thanks

Brian G0VAX



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

Yahoo! Groups Links




How do I connect DXlabs to CW Skimmer???

Brian Bowers G0VAX
 

Hi All,
I have been pulling what little hair I have out trying to connect the DXLabb
s Suite to CW Skimmer,,,has anyone had success?? If so, how did you do in (In an easy step by step way)

Many Thanks

Brian G0VAX


Re: DXK: Spurious text input control and other layout issues.

g4wjs
 

Hi again,

Forgot to mention than in all cases (I believe) resizing the Window fixes the broken layouts.

73
Bill
G4WJS.


DXK: Spurious text input control and other layout issues.

g4wjs
 

Hi,

I've recently been using DXK in 2-pane format.

On the Check Progess tab there is a spurious text input (Text1) located about 100px below the "Run Script" and "Recompute" buttons.

Also clicking the panel selector check boxes in dual pane mode is fairly badly broken. Many examples of broken layouts:

Select only "Contest" pane and then check and uncheck "Propagation" several times - log page display grows each time until screen is full - then "Propagation" overwrites "Contest".

Select only "User-defined" then select "Details" - "Details" overwrites log page display.

Select only "User-defined" then select/unselect/... "Propagation" - behaves like fist example with ever growing log page display.

Many others - most combinations do something unexpected.

73
Bill
G4WJS.


Re: How to fix this error

joe.wc4r <joe.wc4r@...>
 

Dave- Thanks you. That took care of the problem.
However, I now notice a message in the SpotCollector title bar. The contents are:
13-Jul-2012 14:34:52 > SpotCollector shutdown

13-Jul-2012 14:36:00 > SpotCollector version 6.1.0
13-Jul-2012 14:36:00 > App.Path : C:&#92;DXLab&#92;SpotCollector
13-Jul-2012 14:36:00 > App.exe : SpotCollector
13-Jul-2012 14:36:00 > Operating System : Windows 7 (64-bit) build 7601
13-Jul-2012 14:36:00 > Locale ID : 1033 (0x409)
13-Jul-2012 14:36:00 > ANSI CodePage : 1252
13-Jul-2012 14:36:00 > OEM CodePage : 437
13-Jul-2012 14:36:00 > Country : United States
13-Jul-2012 14:36:00 > Language : English
13-Jul-2012 14:36:00 > DecimalSeparator : .
13-Jul-2012 14:36:00 > ThousandSeparator : ,
13-Jul-2012 14:36:00 > DXLab Apps :
13-Jul-2012 14:36:02 > program error 3800 in module SpotDatabaseModule.OpenSpecialCallDatabase, State = 18: 'SpecialCallIndex' is not an index in this table.

I expect it has something to do with the deleted special call file.

OK as is or should I do more?
73 Joe

--- In dxlab@yahoogroups.com, "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] On Behalf Of
joe.wc4r
Sent: Saturday, June 30, 2012 12:31 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] How to fix this error

I get the error window at start up that says:
the specified local file &#92;ReleaseInfo.txt does not exist I click OK and it
runs fine. How can this be fixed?

On the Launcher's Configuration window, you have the "Distribution Site"
selector set to "local folder", but you have not provided the expected
ReleaseInfo.txt file on your PC. Change the "Distribution Site" selector to
"KY1V" or "DXLabSuite", and you'll be able to download and install upgrades
as they become available.

I also check and found this info in the error log:
30-Jun-2012 16:24:22 > SpotCollector version 6.0.3
30-Jun-2012 16:24:22 > App.Path : C:&#92;DXLab&#92;SpotCollector
30-Jun-2012 16:24:22 > App.exe : SpotCollector
30-Jun-2012 16:24:22 > Operating System : Windows 7 (64-bit) build 7601
30-Jun-2012 16:24:22 > Locale ID : 1033 (0x409)
30-Jun-2012 16:24:22 > ANSI CodePage : 1252
30-Jun-2012 16:24:22 > OEM CodePage : 437
30-Jun-2012 16:24:22 > Country : United States
30-Jun-2012 16:24:22 > Language : English
30-Jun-2012 16:24:22 > DecimalSeparator : .
30-Jun-2012 16:24:22 > ThousandSeparator : ,
30-Jun-2012 16:24:22 > DXLab Apps :
30-Jun-2012 16:24:23 > program error 3800 in module
SpotDatabaseModule.OpenSpecialCallDatabase, State = 18: 'SpecialCallIndex'
is not an index in this table.
30-Jun-2012 16:24:38 > program error 91 in module
SpotDatabaseModule.GetTags: Object variable or With block variable not set

SpotCollector's Special Callsign Database has been damaged. Have you
populated SpotCollector's Special Callsign List?

If not, then
1. terminate SpotCollector

2. using Windows Explorer, navigate to C:&#92;DXLab&#92;SpotCollector&#92;Databases

3. using Windows Explorer, delete the file SpecialCallsigns.mdb

4. start SpotCollector; no errorlog.txt file should be created

If you have populated SpotCollector's Special Callsign list, then place
the file

C:&#92;DXLab&#92;SpotCollector&#92;Databases&#92; SpecialCallsigns.mdb

Into a zip archive, attach that zip archive to an email message, and send
that email message to me via

aa6yq (at) ambersoft.com

so I can try to repair it for you.

73,

Dave, AA6YQ


Re: DXKeeper 10.3.2 is available

wb2nvr <wb2nvr@...>
 

Hi Dave -

DXKeeper 10.3.2; DXKeeper Configuration; Log: Backup folder:


&#92;&#92;NETGEARNAS&#92;backup&#92;W2RZS&#92;DXKeeper&#92;W2RZS


73,

Bob WB2NVR

--- In dxlab@yahoogroups.com, "Dave" <aa6yq@...> wrote:

Thanks. When you start DXKeeper, what appears the Backup pathname?

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@> wrote:

Thanks, Dave.

The file is:

"BackupDirectory"="&#92;&#92;NETGEARNAS&#92;backup&#92;W2RZS&#92;DXKeeper&#92;W2RZS"

73,

Bob

--- In dxlab@yahoogroups.com, "Dave AA6YQ" <aa6yq@> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
wb2nvr
Sent: Wednesday, July 11, 2012 5:48 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: DXKeeper 10.3.2 is available


Hi Dave -

Sorry for the delay in responding to your request.

I started DXK 10.3.2 for W2RZS. The backup location was J75RZ. I changed
the location to W2RZS, didn't do a backup, and closed DXK. I restarted DXK,
and the backup location remained W2RZS, as expected.

This confirms that the defect your reported was in fact corrected.
Versions of DXKeeper prior to 10.3.2 would have not updated the Windows
Registry to reflect the change in backup folder from W2RZS to J75RZ unless
you first initiated a backup.


I then updated the Work Space for W2RZS to save the backup location.

I then activated the WS for J75RZ, and opened DXK for J75RZ. The backup
location shows W2RZS.

The implication of this is that your J75RX Workspace specified the backup
location for W2RZS.


I changed it to J75RZ, closed DXK without making a B/U, re-opened DXK for
J75RZ, and confirmed that the B/U location was J75RZ.

Once again confirming that the defect was corrected.

I closed DXK, and updated the WS for J75RZ to save the B/U location.

I then activated the WS for W2RZS, opened DXK for W2RZS, and the B/U
location was J75RZ.

You confirmed that the Windows Registry entry for the backup location was
set to W2RZS when you restarted DXKeeper above. The question is why this
wasn't saved in the W2RZS Workspace when you updated it.

Using Notepad, navigate to the W2RZS folder in the Launcher's Workspaces
folder, and (with Notepad's "Files of Type" selector set to "All Files"),
open the file DXKeeper.reg

Be careful to make no changes in this file (in case you inadvertently
invoke the File:Save menu item)

Search for
BackupDirectory

You should find a line like
"BackupDirectory"="C:&#92;&#92;DXLab&#92;&#92;Archives&#92;&#92;Log Backups"

What does the line you find look like?
Terminate Notepad without saving changes.
73,

Dave, AA6YQ


Re: Sync LOTW QSO's Problem?

Earl Needham
 

Setting to KD5XB/M seemed to have no effect.

I'll take a look at the web page, but int he meantime, is there any
progress to be had by checking "Exclude station callsign when matching
downloaded QSOs & QSLs to logged QSOs"?

Also, I notice what may be an error on my part -- although uploaded with my
KD5XB/M certificate, all three callsign boxes in the aux panel show simply
"KD5XB". Should I change that and upload them again?

Thanks,
Earl


On Thu, Jul 12, 2012 at 7:59 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

**


AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
earl_needham
Sent: Thursday, July 12, 2012 3:32 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: Sync LOTW QSO's Problem?

No, that box is empty.

Set it to KD5XB/M and then try "Sync LotW QSOs" and "Sync LotW QSLs".
If you're using LotW with multiple station callsigns and/or operating
locations, I suggest a review of

<http://www.dxlabsuite.com/dxlabwiki/LotWMultipleCallsignsLocations>


73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "Dave" <aa6yq@...> wrote:

On the "QSL Configuration" window's LotW tab, do you have the "Limit Add
and Sync operations to this station callsign" box set to

KD5XB/M

?

73,

Dave, AA6YQ


--- In dxlab@yahoogroups.com, Earl Needham <earl.kd5xb@> wrote:

Thanks, Dave.

As usual, the DXCC program confuses me no end -- and LoTW is part of
that
program, so it is confusing me as well.

I followed the steps and I'm not sure I can see anything wrong with the
QSO's, unless that pesky /M is causing the problem. I have five
certificates -- KD5XB, KD5XB/M, HL9XB (limited date range), KA5NYT, and
KA5OBR. All the problem QSO's that I have were uploaded using the
KD5XB/M
certificate. It doesn't expire until March of 2014, and the date range
for
valid QSO's for this cert goes until the end of this year -- I'll have
to
update it in December.

All my problem QSO's were between 6/25 and 6/30 of this year.

I can SEE the QSO's in LoTW, and they look OK to me. Going to the "YOUR
QSOS" tab, and putting any of the problem callsigns in the search
window,
they all show up with the /M suffix, but I'm not sure if that;'s a
factor.
Shouldn't they all be downloaded when DXK synchronizes them?

Using one example, I search on JA3CZY, and LoTW shows this:

*Call sign* *Worked* *Date/Time* *Band* *Mode* *Freq* *QSL*
Details<https://p1k.arrl.org/lotwuser/qsodetail?qso=431949872>
KD5XB/M JA3CZY 2012-06-30 14:40:00 20M SSB 14.19
(Wow, I didn't realize I'd get the whole table!)

However, in the AUX panel, my callsign doesn't have the /M -- but
adding
/M
to the station call, op call, and owner call doesn't fix it, so maybe
I'm
looking in the wrong place.

Date & time is correct, band is correct, mode is correct.

Maybe I've looked at this so much that I can't see it -- do you see
anything wrong in this example?

Thanks,
Earl
KD5XB


On Thu, Jul 12, 2012 at 12:01 AM, Dave <aa6yq@> wrote:

**


AA6YQ comments below

--- In dxlab@yahoogroups.com, Earl Needham <earl.kd5xb@> wrote:

Dunno where the problem, but I have it, too.

Step-by-step instructions for dealing with this scenario can be
found in

<http://www.dxlabsuite.com/dxlabwiki/DebugUnacceptedLotW>

73,

Dave, AA6YQ



[Non-text portions of this message have been removed]
------------------------------------

Yahoo! Groups Links

-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1424 / Virus Database: 2437/5126 - Release Date: 07/11/12



[Non-text portions of this message have been removed]


QSL_RCVD='S'

Willem <k6nd@...>
 

I have my log filtered as above (222 QSO's), when I go to the QSL tab and do "QSL via" "ADIF file" do Add All it tells me :
DXKeeper 10.3.2-K6ND_New.mdb (filtered): 222 QSO's [QSL queue: 199 QSL's].
I made a printout from that .ADIF file and indeed only 199 QSO's are in there.

What am I missing?

Thanks
Will
K6ND


Re: Sync LOTW QSO's Problem?

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
earl_needham
Sent: Thursday, July 12, 2012 3:32 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: Sync LOTW QSO's Problem?


No, that box is empty.

Set it to KD5XB/M and then try "Sync LotW QSOs" and "Sync LotW QSLs".
If you're using LotW with multiple station callsigns and/or operating
locations, I suggest a review of

<http://www.dxlabsuite.com/dxlabwiki/LotWMultipleCallsignsLocations>

73,

Dave, AA6YQ


--- In dxlab@yahoogroups.com, "Dave" <aa6yq@...> wrote:

On the "QSL Configuration" window's LotW tab, do you have the "Limit Add
and Sync operations to this station callsign" box set to

KD5XB/M

?

73,

Dave, AA6YQ


--- In dxlab@yahoogroups.com, Earl Needham <earl.kd5xb@> wrote:

Thanks, Dave.

As usual, the DXCC program confuses me no end -- and LoTW is part of
that
program, so it is confusing me as well.

I followed the steps and I'm not sure I can see anything wrong with the
QSO's, unless that pesky /M is causing the problem. I have five
certificates -- KD5XB, KD5XB/M, HL9XB (limited date range), KA5NYT, and
KA5OBR. All the problem QSO's that I have were uploaded using the
KD5XB/M
certificate. It doesn't expire until March of 2014, and the date range
for
valid QSO's for this cert goes until the end of this year -- I'll have
to
update it in December.

All my problem QSO's were between 6/25 and 6/30 of this year.

I can SEE the QSO's in LoTW, and they look OK to me. Going to the "YOUR
QSOS" tab, and putting any of the problem callsigns in the search
window,
they all show up with the /M suffix, but I'm not sure if that;'s a
factor.
Shouldn't they all be downloaded when DXK synchronizes them?

Using one example, I search on JA3CZY, and LoTW shows this:

*Call sign* *Worked* *Date/Time* *Band* *Mode* *Freq* *QSL*
Details<https://p1k.arrl.org/lotwuser/qsodetail?qso=431949872>
KD5XB/M JA3CZY 2012-06-30 14:40:00 20M SSB 14.19
(Wow, I didn't realize I'd get the whole table!)

However, in the AUX panel, my callsign doesn't have the /M -- but adding
/M
to the station call, op call, and owner call doesn't fix it, so maybe
I'm
looking in the wrong place.

Date & time is correct, band is correct, mode is correct.

Maybe I've looked at this so much that I can't see it -- do you see
anything wrong in this example?

Thanks,
Earl
KD5XB


On Thu, Jul 12, 2012 at 12:01 AM, Dave <aa6yq@> wrote:

**


AA6YQ comments below

--- In dxlab@yahoogroups.com, Earl Needham <earl.kd5xb@> wrote:

Dunno where the problem, but I have it, too.

Step-by-step instructions for dealing with this scenario can be
found in

<http://www.dxlabsuite.com/dxlabwiki/DebugUnacceptedLotW>

73,

Dave, AA6YQ







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

Yahoo! Groups Links



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1424 / Virus Database: 2437/5126 - Release Date: 07/11/12


Re: DXKeeper 10.3.2 is available

Dave AA6YQ
 

Thanks. When you start DXKeeper, what appears the Backup pathname?

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@...> wrote:

Thanks, Dave.

The file is:

"BackupDirectory"="&#92;&#92;NETGEARNAS&#92;backup&#92;W2RZS&#92;DXKeeper&#92;W2RZS"

73,

Bob

--- In dxlab@yahoogroups.com, "Dave AA6YQ" <aa6yq@> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
wb2nvr
Sent: Wednesday, July 11, 2012 5:48 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: DXKeeper 10.3.2 is available


Hi Dave -

Sorry for the delay in responding to your request.

I started DXK 10.3.2 for W2RZS. The backup location was J75RZ. I changed
the location to W2RZS, didn't do a backup, and closed DXK. I restarted DXK,
and the backup location remained W2RZS, as expected.

This confirms that the defect your reported was in fact corrected.
Versions of DXKeeper prior to 10.3.2 would have not updated the Windows
Registry to reflect the change in backup folder from W2RZS to J75RZ unless
you first initiated a backup.


I then updated the Work Space for W2RZS to save the backup location.

I then activated the WS for J75RZ, and opened DXK for J75RZ. The backup
location shows W2RZS.

The implication of this is that your J75RX Workspace specified the backup
location for W2RZS.


I changed it to J75RZ, closed DXK without making a B/U, re-opened DXK for
J75RZ, and confirmed that the B/U location was J75RZ.

Once again confirming that the defect was corrected.

I closed DXK, and updated the WS for J75RZ to save the B/U location.

I then activated the WS for W2RZS, opened DXK for W2RZS, and the B/U
location was J75RZ.

You confirmed that the Windows Registry entry for the backup location was
set to W2RZS when you restarted DXKeeper above. The question is why this
wasn't saved in the W2RZS Workspace when you updated it.

Using Notepad, navigate to the W2RZS folder in the Launcher's Workspaces
folder, and (with Notepad's "Files of Type" selector set to "All Files"),
open the file DXKeeper.reg

Be careful to make no changes in this file (in case you inadvertently
invoke the File:Save menu item)

Search for
BackupDirectory

You should find a line like
"BackupDirectory"="C:&#92;&#92;DXLab&#92;&#92;Archives&#92;&#92;Log Backups"

What does the line you find look like?
Terminate Notepad without saving changes.
73,

Dave, AA6YQ


Re: upgrade

Dave AA6YQ
 

AA6YQ comments below
--- In dxlab@yahoogroups.com, "wa7zxd" <wa7zxd@...> wrote:

You have to load the QSL Queue separately for eQSL and LoTW. Would like to be able to upload both at the same time or not have to repopulate the Queue

It's best to keep these activities separate, as combining them would make handling the failure scenarios more complicated for the user -- e.g. "LotW is down" or "eQSL is down".
73,

Dave, AA6YQ


Re: Accuracy of RF Power reading in Commander

Dave AA6YQ
 

AA6YQ comments below
--- In dxlab@yahoogroups.com, "dxpedition2002" <whydoibother@...> wrote:

How accurate should this be considered?

Into a dummy load my rig shows 200 watts on its meter. Commander shows 150 watts.

It also indicates 150 watts when connected through my external auto tuner to my R7 vertical.

Does commander read peak or rms power?

Into my R7 vertical my MFJ-993B auto-tuner indicates 200 watts forward and 1.4 watts reflected.

Just curious from a contesting outlook as to whether I can consider myself as in the low-power rather than the high power category in ARRL contests or any others where 150 or below is considered low power.

Commander displays the transmit power reported by your transceiver.
73,

Dave, AA6YQ


Accuracy of RF Power reading in Commander

dxpedition2002
 

How accurate should this be considered?

Into a dummy load my rig shows 200 watts on its meter. Commander shows 150 watts.

It also indicates 150 watts when connected through my external auto tuner to my R7 vertical.

Does commander read peak or rms power?

Into my R7 vertical my MFJ-993B auto-tuner indicates 200 watts forward and 1.4 watts reflected.

Just curious from a contesting outlook as to whether I can consider myself as in the low-power rather than the high power category in ARRL contests or any others where 150 or below is considered low power.

73 de Walt, W6SA


Re: DxKeeper Capture showing AZ info - newbie question

edcatcay
 

Hi Dave, Thanks for the reply and the support! I completly understand how you coded this function now, how to use it and the logic behind it. I appreciate your kind guideance. Best 73's Ed

--- In dxlab@yahoogroups.com, "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
edcatcay
Sent: Wednesday, July 11, 2012 9:43 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: DxKeeper Capture showing AZ info - newbie question


Hi Dave,
Thank you so much for the rapid response and the wonderful software! My Dx
Lab suite works exactly as you specified in your response. If I understand
your response correctly the Capture AZ window will show the current heading
of the antenna and not the heading required for the new call entered?

Yes, the AZ window will show the antenna's actual heading -- which is
what should be logged. There is no point in logging the "theoretical"
shortpath heading.



To change the AZ to the heading required for the new call entered in
capture, you need to click either the sp/lp button in dx view which will
rotate the antenna and update Az box to the new heading to match the new
call in capture.

Correct.
I was hoping the az box in capture would show the new heading required and
not the current heading.

DXView does that: it displays the "theoretical" shortpath and longpath
headings to which you would initially rotate your antenna, and provides SP
and LP buttons to initiate rotation.

DXKeeper records the "actual" heading used during the QSO, which might be
identical to the "theoretical" heading, or might be different if you found
that the signal peaked on a skewed path.

Note that clicking on a logged QSO in DXKeeper's Log Page Display causes
DXView to display the "theoretical" shortpath and longpath headings for the
location logged with that QSO. So if you didn't log a heading with a QSO,
the "theoretical" headings are readily available.

73,

Dave, AA6YQ


Re: DxKeeper Capture showing AZ info - newbie question

edcatcay
 

Hi Dave, Thanks for the reply and the support! I completly understand how you coded this function now, how to use it and the logic behind it. I appreciate your kind guideance. Best 73's Ed

--- In dxlab@yahoogroups.com, "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
edcatcay
Sent: Wednesday, July 11, 2012 9:43 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: DxKeeper Capture showing AZ info - newbie question


Hi Dave,
Thank you so much for the rapid response and the wonderful software! My Dx
Lab suite works exactly as you specified in your response. If I understand
your response correctly the Capture AZ window will show the current heading
of the antenna and not the heading required for the new call entered?

Yes, the AZ window will show the antenna's actual heading -- which is
what should be logged. There is no point in logging the "theoretical"
shortpath heading.



To change the AZ to the heading required for the new call entered in
capture, you need to click either the sp/lp button in dx view which will
rotate the antenna and update Az box to the new heading to match the new
call in capture.

Correct.
I was hoping the az box in capture would show the new heading required and
not the current heading.

DXView does that: it displays the "theoretical" shortpath and longpath
headings to which you would initially rotate your antenna, and provides SP
and LP buttons to initiate rotation.

DXKeeper records the "actual" heading used during the QSO, which might be
identical to the "theoretical" heading, or might be different if you found
that the signal peaked on a skewed path.

Note that clicking on a logged QSO in DXKeeper's Log Page Display causes
DXView to display the "theoretical" shortpath and longpath headings for the
location logged with that QSO. So if you didn't log a heading with a QSO,
the "theoretical" headings are readily available.

73,

Dave, AA6YQ


upgrade

John K
 

You have to load the QSL Queue separately for eQSL and LoTW. Would like to be able to upload both at the same time or not have to repopulate the Queue


Re: DXKeeper 10.3.2 is available

wb2nvr <wb2nvr@...>
 

Thanks, Dave.

The file is:

"BackupDirectory"="&#92;&#92;NETGEARNAS&#92;backup&#92;W2RZS&#92;DXKeeper&#92;W2RZS"

73,

Bob

--- In dxlab@yahoogroups.com, "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
wb2nvr
Sent: Wednesday, July 11, 2012 5:48 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: DXKeeper 10.3.2 is available


Hi Dave -

Sorry for the delay in responding to your request.

I started DXK 10.3.2 for W2RZS. The backup location was J75RZ. I changed
the location to W2RZS, didn't do a backup, and closed DXK. I restarted DXK,
and the backup location remained W2RZS, as expected.

This confirms that the defect your reported was in fact corrected.
Versions of DXKeeper prior to 10.3.2 would have not updated the Windows
Registry to reflect the change in backup folder from W2RZS to J75RZ unless
you first initiated a backup.


I then updated the Work Space for W2RZS to save the backup location.

I then activated the WS for J75RZ, and opened DXK for J75RZ. The backup
location shows W2RZS.

The implication of this is that your J75RX Workspace specified the backup
location for W2RZS.


I changed it to J75RZ, closed DXK without making a B/U, re-opened DXK for
J75RZ, and confirmed that the B/U location was J75RZ.

Once again confirming that the defect was corrected.

I closed DXK, and updated the WS for J75RZ to save the B/U location.

I then activated the WS for W2RZS, opened DXK for W2RZS, and the B/U
location was J75RZ.

You confirmed that the Windows Registry entry for the backup location was
set to W2RZS when you restarted DXKeeper above. The question is why this
wasn't saved in the W2RZS Workspace when you updated it.

Using Notepad, navigate to the W2RZS folder in the Launcher's Workspaces
folder, and (with Notepad's "Files of Type" selector set to "All Files"),
open the file DXKeeper.reg

Be careful to make no changes in this file (in case you inadvertently
invoke the File:Save menu item)

Search for
BackupDirectory

You should find a line like
"BackupDirectory"="C:&#92;&#92;DXLab&#92;&#92;Archives&#92;&#92;Log Backups"

What does the line you find look like?
Terminate Notepad without saving changes.
73,

Dave, AA6YQ


Re: Sync LOTW QSO's Problem?

Earl Needham
 

No, that box is empty.

E.

--- In dxlab@yahoogroups.com, "Dave" <aa6yq@...> wrote:

On the "QSL Configuration" window's LotW tab, do you have the "Limit Add and Sync operations to this station callsign" box set to

KD5XB/M

?

73,

Dave, AA6YQ


--- In dxlab@yahoogroups.com, Earl Needham <earl.kd5xb@> wrote:

Thanks, Dave.

As usual, the DXCC program confuses me no end -- and LoTW is part of that
program, so it is confusing me as well.

I followed the steps and I'm not sure I can see anything wrong with the
QSO's, unless that pesky /M is causing the problem. I have five
certificates -- KD5XB, KD5XB/M, HL9XB (limited date range), KA5NYT, and
KA5OBR. All the problem QSO's that I have were uploaded using the KD5XB/M
certificate. It doesn't expire until March of 2014, and the date range for
valid QSO's for this cert goes until the end of this year -- I'll have to
update it in December.

All my problem QSO's were between 6/25 and 6/30 of this year.

I can SEE the QSO's in LoTW, and they look OK to me. Going to the "YOUR
QSOS" tab, and putting any of the problem callsigns in the search window,
they all show up with the /M suffix, but I'm not sure if that;'s a factor.
Shouldn't they all be downloaded when DXK synchronizes them?

Using one example, I search on JA3CZY, and LoTW shows this:

*Call sign* *Worked* *Date/Time* *Band* *Mode* *Freq* *QSL*
Details<https://p1k.arrl.org/lotwuser/qsodetail?qso=431949872>
KD5XB/M JA3CZY 2012-06-30 14:40:00 20M SSB 14.19
(Wow, I didn't realize I'd get the whole table!)

However, in the AUX panel, my callsign doesn't have the /M -- but adding /M
to the station call, op call, and owner call doesn't fix it, so maybe I'm
looking in the wrong place.

Date & time is correct, band is correct, mode is correct.

Maybe I've looked at this so much that I can't see it -- do you see
anything wrong in this example?

Thanks,
Earl
KD5XB


On Thu, Jul 12, 2012 at 12:01 AM, Dave <aa6yq@> wrote:

**


AA6YQ comments below

--- In dxlab@yahoogroups.com, Earl Needham <earl.kd5xb@> wrote:

Dunno where the problem, but I have it, too.

Step-by-step instructions for dealing with this scenario can be found in
<http://www.dxlabsuite.com/dxlabwiki/DebugUnacceptedLotW>

73,

Dave, AA6YQ



[Non-text portions of this message have been removed]


Re: Sync LOTW QSO's Problem?

Dave AA6YQ
 

On the "QSL Configuration" window's LotW tab, do you have the "Limit Add and Sync operations to this station callsign" box set to

KD5XB/M

?

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, Earl Needham <earl.kd5xb@...> wrote:

Thanks, Dave.

As usual, the DXCC program confuses me no end -- and LoTW is part of that
program, so it is confusing me as well.

I followed the steps and I'm not sure I can see anything wrong with the
QSO's, unless that pesky /M is causing the problem. I have five
certificates -- KD5XB, KD5XB/M, HL9XB (limited date range), KA5NYT, and
KA5OBR. All the problem QSO's that I have were uploaded using the KD5XB/M
certificate. It doesn't expire until March of 2014, and the date range for
valid QSO's for this cert goes until the end of this year -- I'll have to
update it in December.

All my problem QSO's were between 6/25 and 6/30 of this year.

I can SEE the QSO's in LoTW, and they look OK to me. Going to the "YOUR
QSOS" tab, and putting any of the problem callsigns in the search window,
they all show up with the /M suffix, but I'm not sure if that;'s a factor.
Shouldn't they all be downloaded when DXK synchronizes them?

Using one example, I search on JA3CZY, and LoTW shows this:

*Call sign* *Worked* *Date/Time* *Band* *Mode* *Freq* *QSL*
Details<https://p1k.arrl.org/lotwuser/qsodetail?qso=431949872>
KD5XB/M JA3CZY 2012-06-30 14:40:00 20M SSB 14.19
(Wow, I didn't realize I'd get the whole table!)

However, in the AUX panel, my callsign doesn't have the /M -- but adding /M
to the station call, op call, and owner call doesn't fix it, so maybe I'm
looking in the wrong place.

Date & time is correct, band is correct, mode is correct.

Maybe I've looked at this so much that I can't see it -- do you see
anything wrong in this example?

Thanks,
Earl
KD5XB


On Thu, Jul 12, 2012 at 12:01 AM, Dave <aa6yq@...> wrote:

**


AA6YQ comments below

--- In dxlab@yahoogroups.com, Earl Needham <earl.kd5xb@> wrote:

Dunno where the problem, but I have it, too.

Step-by-step instructions for dealing with this scenario can be found in
<http://www.dxlabsuite.com/dxlabwiki/DebugUnacceptedLotW>

73,

Dave, AA6YQ



[Non-text portions of this message have been removed]

99681 - 99700 of 208063