Date   
Re: LoTH Didn't Populate Completely

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Jim Studer
Sent: Tuesday, July 13, 2010 9:18 PM
To: dxlab@...
Subject: [dxlab] Re: LoTH Didn't Populate Completely


I would have sworn that I did all of the steps you suggested but I guess I
didn't.

Keep in mind that with respect to LotW confirmations, DXKeeper's log is
updated when you click the "Sync LotW QSLs" button. If you visit the LotW
web site several hours after clicking "Sync LotW QSLs", you may find new
confirmations that were generatd by LotW after you clicked "Sync LotW
QSLs" -- particularly if you recently uploaded a large batch of QSOs after a
contest weekend.

73,

Dave, AA6YQ

Re: LoTH Didn't Populate Completely

Jim Studer <jimstuder@...>
 

I would have sworn that I did all of the steps you suggested but I guess I
didn't. It worked this time. Thanks.



73,



Jim Studer, AK4I

770-485-6577 home

770-630-1278 cell

770-421-3555 work

<mailto:ak4i@...> ak4i@...



"Heresy is a cradle; orthodoxy a coffin."--- Robert Green Ingersoll

"Be thankful we're not getting all the government we're paying for," Will
Rogers

Storing frequencies

k8nxx <n4cla@...>
 

I am fairly new to this group as well as to DXlab. I have looked thru some of the documentation and tried to find things intuitively with little success. My question is this. I am using an FT-857D and am wondering if it is possible for the DXlab suite to store a frequency in some memory location somewhere that would include a transmit offset and sub-audible tone for 10m, 6m, 2m and 440 without storing them in the radio.

Thanks
Fred - N4CLA

Re: Grid Square

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Bill Aycock
Sent: Tuesday, July 13, 2010 7:24 PM
To: dxlab@...
Subject: Re: [dxlab] RE: Grid Square


Dave--
An incorrect Grid square is not an infrequent case, particularly for rural
locations. In my case, I am over 10 miles from the ZipCode center (that's
what the FCC database reports). Based on this, a lookup will report EM64up,
where, based on Latitude and Longitude, I am in EM64vr. QRZ has what I
reported, but a common lookup is often wrong.
This error can occur at any lever of the Grid Square notation, Capitol
letter pair, digits, or lower case pair.

The USAP database is now used by SpotCollector in several ways:
1. to determine a beam heading

2. to determine the distance between your station and a spotting station

3. to disambiguate the grid square information found in spot notes, e.g.

CM87ar <ES> PM85mb

"Center of zipcode" accuracy is fine for the above purposes, but one
cannot use the grid square returned by a USAP lookup to identify needed
grids for exactly the reasons you state above.

However, if when SpotCollector sees ambiguous spot notes like
CM87ar <ES> PM85mb

with both "Capture location info from notes" and "Lookup missing location
info" enabled,
it performs a USAP lookup on the spotting station that yields CM87bk, then
it knows that the spotting station is located in CM87ar and the DX station
in PM85mb. Unless the station posting the spot copied or spotted the DX
station's grid square incorrectly, PM85mb is an accurate DX grid square.

In the next version of SpotCollector, the "DX Grid" and "Origin Grid"
items are displayed as 4-character grid squares when they are the result of
a USAP database lookup. Grid squares are only displayed with 6-characters
when they are unambiguously determinable from spot notes (assuming the
"Capture location info from notes" option is enabled) or when they are
specified by an entity override.

73,

Dave, AA6YQ

Re: Grid Square

Richard J. Fiero II W5TFW <joeyw5tfw@...>
 

I'll second that emotion !

Joey

----- Original Message -----
From: Bill Aycock
To: dxlab@...
Sent: Tuesday, July 13, 2010 6:23 PM
Subject: Re: [dxlab] RE: Grid Square



Dave--
An incorrect Grid square is not an infrequent case, particularly for rural
locations. In my case, I am over 10 miles from the ZipCode center (that's
what the FCC database reports). Based on this, a lookup will report EM64up,
where, based on Latitude and Longitude, I am in EM64vr. QRZ has what I
reported, but a common lookup is often wrong.
This error can occur at any lever of the Grid Square notation, Capitol
letter pair, digits, or lower case pair.
Bill--W4BSG
--------------------------------------------------

Re: Grid Square

Bill Aycock <baycock2@...>
 

Dave--
An incorrect Grid square is not an infrequent case, particularly for rural locations. In my case, I am over 10 miles from the ZipCode center (that's what the FCC database reports). Based on this, a lookup will report EM64up, where, based on Latitude and Longitude, I am in EM64vr. QRZ has what I reported, but a common lookup is often wrong.
This error can occur at any lever of the Grid Square notation, Capitol letter pair, digits, or lower case pair.
Bill--W4BSG
--------------------------------------------------

Re: WinWarbler error message and FT-857D settings

Dave AA6YQ
 

AA6YQ comments below
--- In dxlab@..., "sv1dpp" <sv1dpp@...> wrote:

Dave all the "Allow" boxes (exept 1st and last) was checker. Unfortunately the problem is stil here

Then something else in the configuration of your Windows 7 system is preventing WinWarbler (and MMTTY) from creating and modifying files in your WinWarbler folder. The only other possibility I can think of is anti-malware software; if the anti-malware software you're using can prevent an application from creating or modifying files, you should adjust it to give each DXLab application the ability to create and modify files.
73,

Dave, AA6YQ

Re: WinWarbler error message and FT-857D settings

sv1dpp
 

Dave all the "Allow" boxes (exept 1st and last) was checker. Unfortunately the problem is stil here

Re: sc, audio announcements

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kenneth
Sent: Tuesday, July 13, 2010 4:27 PM
To: dxlab@...
Subject: [dxlab] sc, audio announcements


I just started playing with this.
On SC Audio page, I have checked Enable, Enable alarm after 15 min, ann
unconfirmed, include call signs, phonetic, unfiltered.
I push the test button and hear nothing.
Is there another hookup needed?

Please take a look at
<http://www.dxlabsuite.com/dxlabwiki/AudioAnnouncements>

If this doesn't get you going, please let me know.
73,

Dave, AA6YQ

sc, audio announcements

Kenneth <montannacowboy@...>
 

I just started playing with this.
On SC Audio page, I have checked Enable, Enable alarm after 15 min, ann unconfirmed, include call signs, phonetic, unfiltered.
I push the test button and hear nothing.
Is there another hookup needed?

Re: DXKeeper: confirming eqsl qsos

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Mike34230
Sent: Tuesday, July 13, 2010 12:46 PM
To: dxlab@...
Subject: [dxlab] DXKeeper: confirming eqsl qsos


I would like to confirm received eqsls only. Is there a way to sync eqsl
and have "eqsl sent" set to "R" (if it's not already "Y"), then use the "add
requested" button to add the newly received q's to the queue?

From an automation perspective, DXKeeper assumes that if you're
participating in eQSL.cc that you will upload every logged QSO to eQSL.cc.
You can do that by

- enabling the "Upload each QSO logged via the Capture window to eQSL.cc"
option

or

- enabling the "Initialize eQSL Sent to 'R' for each logged or imported QSO"
option and then periodically invoking "Add Requested" with the "QSL Via"
panel set to eQSL.cc to populate the QSL Queue with a batch of
not-yet-uploaded QSOs followed by "Upload to eQSL" to upload that batch.


To implement a "confirm received eQSLs only" policy, you would
1. on the Main window's QSL tab, set the "QSL Via" panel to eQSL.cc, and
invoke the "Sync eQSL.cc QSLs" function

2. filter the Log Page Display with the SQL expression

(APP_DXKEEPER_eQSL_QSL_SENT <> 'Y') and (APP_DXKEEPER_eQSL_QSL_RCVD IN
('Y','V'))

4. on the Main window's QSL tab,

4a. invoke the "Add All" function

4b. invoke the "Upload to eQSL.cc" function


This is more work than simply invoking "Add Requested" followed by
"Upload to eQSL.cc".

In my opinion, if you're going to participate in eQSL.cc, you should
peridocially upload all of your not-yet-uploaded QSOs; DXKeeper
intentionally makes it easy to do this.

73,

Dave, AA6YQ

Re: DXKeeper: confirming eqsl qsos

Richard B Drake
 

I don't think there is a way to do that but Dave might correct me. However, what I really wanted to say is that if everybody did that then nobody would ever receive an eQSL, so why do it?

73, Rich - W3ZJ

Mike34230 wrote:

I would like to confirm received eqsls only. Is there a way to sync eqsl and have "eqsl sent" set to "R" (if it's not already "Y"), then use the "add requested" button to add the newly received q's to the queue?

-Mike


DXKeeper: confirming eqsl qsos

Mike - AA1AR
 

I would like to confirm received eqsls only. Is there a way to sync eqsl and have "eqsl sent" set to "R" (if it's not already "Y"), then use the "add requested" button to add the newly received q's to the queue?

-Mike

Re: Moving DXLab from Win 7 x86 to Win 7 64 bit Computer

Dave AA6YQ
 

AA6YQ comments below
--- In dxlab@..., "Mack WB4MAK" <mccormick_mack@...> wrote:

I have a new computer for my hamshack that runs Win 7 64 bit OS. The old hamshack computer was running Win 7 32 bit OS.

I have completely reinstalled the DXLab apps on the new computer. I have backed up the DXLab registry and DXKeeper log files on the old computer.

What is the recommended procedure to move the contact log file to the new computer?

You'll find the procedure for doing this in
<http://www.dxlabsuite.com/dxlabwiki/MovingBetweenPCs>


Is it possible to import the registry settings to the new computer so that I don't have to reconfigure everything?

If DXLab is installed in the same folder on both PCs, e.g.
c:&#92;DXLab

then when you restore the saved Workspace in step 6 of the above procedure there will be no further configuration required. If DXLab on your new PC is installed in a different folder than it is on your old PC, you'll have to modify each setting that contains a pathname, for example the "Log pathname" that specifies the location of the current Log file on the Log tab of DXKeeper's Config window.
73,

Dave, AA6YQ

Re: WinWarbler Problem

Dave AA6YQ
 

Glad you got it going, Marty.

73,

Dave, AA6YQ

--- In dxlab@..., "Marty" <w8aks55@...> wrote:

Yes, success this trip around. I did an regedit and cleaned all register keys for WinWarbler. Followed your instructions below and reinstalled WW. I have it and running properly.
Thanks Dave, appreciate the help.
I'll put this in my DXlab folder.
73
Marty
W8AKS

----- Original Message -----
From: Dave AA6YQ
To: dxlab@...
Sent: Tuesday, July 13, 2010 1:49
Subject: RE: [dxlab] WinWarbler Problem



>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Martin Bluhm
Sent: Monday, July 12, 2010 6:16 PM
To: dxlab
Subject: [dxlab] WinWarbler Problem

Hi,
Ran into a problem with WinWarbler 6.7.9.
Trying to run CW on 20m but the operating mode has 2 modes selected : CW and
PSK125.

>>>The only explanation for this is that your WinWarbler installation has
been damaged. In this situation, you should

1. direct the Launcher to save WinWarbler's Registry Settings to a file
somewhere other than your WinWarbler folder (The process of uninstalling and
re-installing WinWarbler should leave your registry settings intact, but its
good to have a backup)

2. move the following files to a folder other than your WinWarbler folder

- PSKBands.txt (if you created it from DefaultPSKBands.txt)

- RTTYBands.txt (if you created it from DefaultRTTYBands.txt)

- any macros you've saved in files in WinWarbler's Scripts sub-folder

- any .wav files you created for phone voice keying (specified in the .wav
file folder setting on the Configuration window's Phone tab)

3. verify that you correctly save all the files listed in step 2

4. use the Windows Control Panel to uninstall WinWarbler

5. delete your WinWarbler folder

6. reboot Windows

7. direct the Launcher to install and update WinWarbler

8. restore the files you saved in step 2 to the appropriate locations in
your WinWarbler folder

9. start WinWarbler

10. let me know how it goes

73,

Dave, AA6YQ





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

Re: WinWarbler Problem

Marty Bluhm
 

Yes, success this trip around. I did an regedit and cleaned all register keys for WinWarbler. Followed your instructions below and reinstalled WW. I have it and running properly.
Thanks Dave, appreciate the help.
I'll put this in my DXlab folder.
73
Marty
W8AKS

----- Original Message -----
From: Dave AA6YQ
To: dxlab@...
Sent: Tuesday, July 13, 2010 1:49
Subject: RE: [dxlab] WinWarbler Problem



>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Martin Bluhm
Sent: Monday, July 12, 2010 6:16 PM
To: dxlab
Subject: [dxlab] WinWarbler Problem

Hi,
Ran into a problem with WinWarbler 6.7.9.
Trying to run CW on 20m but the operating mode has 2 modes selected : CW and
PSK125.

>>>The only explanation for this is that your WinWarbler installation has
been damaged. In this situation, you should

1. direct the Launcher to save WinWarbler's Registry Settings to a file
somewhere other than your WinWarbler folder (The process of uninstalling and
re-installing WinWarbler should leave your registry settings intact, but its
good to have a backup)

2. move the following files to a folder other than your WinWarbler folder

- PSKBands.txt (if you created it from DefaultPSKBands.txt)

- RTTYBands.txt (if you created it from DefaultRTTYBands.txt)

- any macros you've saved in files in WinWarbler's Scripts sub-folder

- any .wav files you created for phone voice keying (specified in the .wav
file folder setting on the Configuration window's Phone tab)

3. verify that you correctly save all the files listed in step 2

4. use the Windows Control Panel to uninstall WinWarbler

5. delete your WinWarbler folder

6. reboot Windows

7. direct the Launcher to install and update WinWarbler

8. restore the files you saved in step 2 to the appropriate locations in
your WinWarbler folder

9. start WinWarbler

10. let me know how it goes

73,

Dave, AA6YQ

Re: WinWarbler Problem

Marty Bluhm
 

Dave, I followed the following procedure with no joy. Both cw and psk125 modes are lit. I turned on the error report and saved it off and sending it to @AA6YQ.
Is this ok?
73
Marty
W8AKS

----- Original Message -----
From: Dave AA6YQ
To: dxlab@...
Sent: Tuesday, July 13, 2010 1:49
Subject: RE: [dxlab] WinWarbler Problem



>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Martin Bluhm
Sent: Monday, July 12, 2010 6:16 PM
To: dxlab
Subject: [dxlab] WinWarbler Problem

Hi,
Ran into a problem with WinWarbler 6.7.9.
Trying to run CW on 20m but the operating mode has 2 modes selected : CW and
PSK125.

>>>The only explanation for this is that your WinWarbler installation has
been damaged. In this situation, you should

1. direct the Launcher to save WinWarbler's Registry Settings to a file
somewhere other than your WinWarbler folder (The process of uninstalling and
re-installing WinWarbler should leave your registry settings intact, but its
good to have a backup)

2. move the following files to a folder other than your WinWarbler folder

- PSKBands.txt (if you created it from DefaultPSKBands.txt)

- RTTYBands.txt (if you created it from DefaultRTTYBands.txt)

- any macros you've saved in files in WinWarbler's Scripts sub-folder

- any .wav files you created for phone voice keying (specified in the .wav
file folder setting on the Configuration window's Phone tab)

3. verify that you correctly save all the files listed in step 2

4. use the Windows Control Panel to uninstall WinWarbler

5. delete your WinWarbler folder

6. reboot Windows

7. direct the Launcher to install and update WinWarbler

8. restore the files you saved in step 2 to the appropriate locations in
your WinWarbler folder

9. start WinWarbler

10. let me know how it goes

73,

Dave, AA6YQ

Moving DXLab from Win 7 x86 to Win 7 64 bit Computer

Mack WB4MAK <mccormick_mack@...>
 

Dave and others,

I have a new computer for my hamshack that runs Win 7 64 bit OS. The old hamshack computer was running Win 7 32 bit OS.

I have completely reinstalled the DXLab apps on the new computer. I have backed up the DXLab registry and DXKeeper log files on the old computer.

What is the recommended procedure to move the contact log file to the new computer? Is it possible to import the registry settings to the new computer so that I don't have to reconfigure everything?

Thanks in advance. I looked through the message archives here and didn't see the answer. Thank you also for continuing to provide the best general ham radio suite for use in my fully automated shack.

Vry 73,

Mack de WB4MAK

Re: Grid Square

aburkefl <aburkefl@...>
 

Nice link, Rich. Thanks!

Art - N4PJ

--- In dxlab@..., Rich - W3ZJ <rich@...> wrote:

Danny,

You need a new grid square map bot em68 and em69 are in Americas
heartland Indiana/Kentucky. Try this one:

http://www.levinecentral.com/ham/grid_square.php

73, Rich - W3ZJ

DANNY DOUGLAS wrote:
My grid map shows no land within grid em68, and just a sliver in em69. Thats probably why folks are interested in 68, but is there an island or something there? I dont know the answer, but do grid squares count with maritime mobile?
n7dc
Danny Douglas





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

Yahoo! Groups Links





Re: LoTH Didn't Populate Completely

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Jim
Sent: Monday, July 12, 2010 10:29 PM
To: dxlab@...
Subject: [dxlab] LoTH Didn't Populate Completely


I recently installed DXLab Suite on my computer and transfered all of my
contacts.

Welcome!

After the IRAU contest I uploaded my new contacts to LoTW and updated the
confirmed status of my QSO's.

Did you update the confirmed status of your QSOs by clicking the "Sync
LotW QSLS" button on the Main window's LotW tab?


For some reason, some of the confirmations didn't show up on my log, while
others did.

The confirmations that "showed up" were those registered in LotW at the
time you last clicked "Sync LotW QSLs".


I can go to LoTW and see the QSL confirmation but when I go to the log and
check the contact (same everything data) some don't show up.

If you click "Sync LotW QSLs", do the missing LotW confirmations appear
in your log?

73,

Dave, AA6YQ