Date   

QSL Sent/Received Status Cleared

wb2nvr <wb2nvr@...>
 

Hi Dave -

After running a Recompute, I noticed that my DXCC totals on the Summary dropped from 218 to 161. On checking further, I noticed that all of the Sent and Received selections (S, R, N...) in DXKeeper have been cleared. If a QSL was sent or received, the date is still shown, as is the QSL method.

I'm using DXK 7.9.5, and the latest entry in the Error Log is:

29-Jun-2009 20:45:11 > DXKeeper version 7.8.4
29-Jun-2009 20:45:11 > App.Path : C:&#92;Program Files&#92;DXLab Suite&#92;DXKeeper
29-Jun-2009 20:45:11 > App.exe : DXKeeper
29-Jun-2009 20:45:11 > Operating System: Windows XP build 2600
29-Jun-2009 20:45:11 > Country : United States
29-Jun-2009 20:45:11 > Language : English (United States)
29-Jun-2009 20:45:11 > DXLab Apps : [CC,PF,DXV,SC]
29-Jun-2009 22:01:21 > program error 6 in module DXLogModule.GetBandNameForFreq: Overflow
29-Jun-2009 22:22:47 > program error 6 in module DXLogModule.GetBandNameForFreq: Overflow
29-Jun-2009 23:04:52 > DXKeeper shutdown

Can you configure a script so that I can reset the QSL status to Sent and Received, based on the date in the corresponding field?

Thanks in advance!

73,

Bob WB2NVR


Error in plotting DX station in DXView

Phil & Anne Irons <irons@...>
 

Greetings, all...

Last night I was listening to VP2VQ on 20 metres, and thought I'd give him a try. When I selected that spot in SC, I noticed that the azimuth from my QTH was wrong. When I checked the World map plot, it showed that he was somewhere in the Indian Ocean! Taking a closer look at the DXV display, it turens out that for this station, the longitude is 65 degrees and some minutes EAST, rather than WEST. The DXCC database correctly shows -65 degrees, so there's a BUG somewhere...

Comments?

73,

Phil/VE1BVD
Sydney, NS


Re: EZ FIX Danny

FireBrick <w9ol@...>
 

I have an easy solution Danny.
Abolish Phone and revert to CW/FSK only.

On 7/7/2009 8:01:30 AM, DANNY DOUGLAS (n7dc@comcast.net) wrote:
Ive been on a one-man rampage against people NOT indicating their modes on

spots in both 160 and 6 meters. It doesnt matter how you set up your
definitions on these two bands, because someone is going to work a mode
which is not typically used on a particular sub-band. 160 is the worst of

all, as any mode is likely to be worked anywhere. With 6 opening up
recently, I find excatly that same problem, particularrly in the 50.100 to

50.115 range. On one page of spots you can find at least half the spots,

within that range, come up on the wrong mode. It would be so easy, if
people would just go below 50.1 for CW and stay on SSB above that mark-
but
they wont.

Previous to the recent expansion of 40 meters, throughout the rest of the

world, most of the DX was using both cw and ssb anywhere they pleased
from
7.00 upward. I was hoping they would get with the program and stop
using
SSB from 7.0 to 7.1 (at least), but of course that is not the case. They
do
not have to do so (no required sub-bands) so they do what they want, no
matter the inconvience to others. It is not going to happen, but would it


Re: 40 meter SSB not CW

DANNY DOUGLAS <n7dc@...>
 

Ive been on a one-man rampage against people NOT indicating their modes on spots in both 160 and 6 meters. It doesnt matter how you set up your definitions on these two bands, because someone is going to work a mode which is not typically used on a particular sub-band. 160 is the worst of all, as any mode is likely to be worked anywhere. With 6 opening up recently, I find excatly that same problem, particularrly in the 50.100 to 50.115 range. On one page of spots you can find at least half the spots, within that range, come up on the wrong mode. It would be so easy, if people would just go below 50.1 for CW and stay on SSB above that mark- but they wont.

Previous to the recent expansion of 40 meters, throughout the rest of the world, most of the DX was using both cw and ssb anywhere they pleased from 7.00 upward. I was hoping they would get with the program and stop using SSB from 7.0 to 7.1 (at least), but of course that is not the case. They do not have to do so (no required sub-bands) so they do what they want, no matter the inconvience to others. It is not going to happen, but would it not be nice to have international subbands!!!!!

Danny Douglas
N7DC
ex WN5QMX ET2US WA5UKR ET3USA
SV0WPP VS6DD N7DC/YV5 G5CTB

All 2 years or more (except Novice)
Pls QSL direct, buro, or LOTW preferred,
I Do not us, but as a courtesy do upload to eQSL for
those who do.

Moderator
DXandTALK
http://groups.yahoo.com/group/DXandTalk
DXandTALK@YAHOOGROUPS.COM

Moderator
Digital_modes
http://groups.yahoo.com/group/digital_modes/?yguid=341090159

----- Original Message -----
From: "Dave AA6YQ" <aa6yq@ambersoft.com>
To: <dxlab@yahoogroups.com>
Sent: Tuesday, July 07, 2009 12:41 AM
Subject: RE: [dxlab] 40 meter SSB not CW


If a spot's notes mention a mode, then SpotCollector uses that mode in the
Spot Database Entry. If no mode is mentioned in the spot notes, then
SpotCollector determines the mode by consulting your sub-band definition
file, which specifies ranges of frequencies (sub-bands) and defines a mode
for each. You can modify your sub-band definition file to reflect the normal
40m activity in your part of the world, or you can create multiple sub-band
definitions files -- each reflecting conditions during a particular kind of
contest or during a particular season -- and select the appropriate one to
use during each operating session. This is described in

<http://www.dxlabsuite.com/spotcollector/Help/ConfigurationGeneral.htm#Sub-b
and Definition panel>

You can also view this information by clicking one of SpotCollector's Help
buttons and navigating as follows:

Configuring SpotCollector > General > Sub-band Definition

73,

Dave, AA6YQ


-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of AD5VJ
Bob
Sent: Tuesday, July 07, 2009 12:00 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] 40 meter SSB not CW


For some reason spotcollector doesn't show a 40 meter dx station as SSB it
shows CW and that is not the correct mode therefore I
have to change the rig after clicking on a spot.

Bob AD5VJ



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

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.5/2220 - Release Date: 07/05/09
17:54:00



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

Yahoo! Groups Links



Re: Spot Collector / Spot Spy Configuration

Dave AA6YQ
 

OK. Please do the following:

1. on the Config window's General tab, check the "log debugging info" box

2. wait until 4 or 5 more 6m spots are announced

3. on the Config window's General tab, uncheck the "log debugging info" box

4. place the errorlog.txt file from your SpotCollector folder and your Spot
Database File in a zip archive, attach it to an email message, and send it
to me via aa6yq@ambersoft.com so I can see what's going on. You'll find the
pathname of your Spot Database file in the "Spot Database File" panel at the
top of the Config window's "Spot Database" tab.

Thanks...

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
vk3ajj
Sent: Tuesday, July 07, 2009 2:58 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: Spot Collector / Spot Spy Configuration


SMALL CORRECTION TO LAST POST

6M SPOTS ARE NOT APPEARING ON THE SCREEN - BUT THE VOICE ANNOUNCEMENTS FOR
6M SPOTS ARE STILL BEING MADE - THESE SPOTS ARE INCLUDING THE DX CALLSIGN
(FIRST ONE DROPPED THE CALL FOR SOME REASON BUT IT MAY HAVE JUST BEEN AN
ERRANT SPOT OR THAT PART OF THE AUDIO WAS LOST FOR SOME REASON).

THE LAST 4 OR SO 6M SPOTS HAVE BEEN ANNOUNCED CORRECTLY WITH DX CALL
INCLUDED

SETTINGS ON THE AUDIO SCREEN ARE:

FIRST 5 BOXES UNDER AUDIO ALARM ARE TICKED - LAST 4 BOXES NOT TICKED.
ALARM TRIGGER IS STILL FILTERED





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

On the Config window's Audio tab, what boxes are checked?

I assume the "Alarm trigger" panel is still set to Filtered.



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

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.5/2220 - Release Date: 07/05/09
17:54:00


Re: Spot Collector / Spot Spy Configuration

vk3ajj <vk3ajj@...>
 

SMALL CORRECTION TO LAST POST

6M SPOTS ARE NOT APPEARING ON THE SCREEN - BUT THE VOICE ANNOUNCEMENTS FOR 6M SPOTS ARE STILL BEING MADE - THESE SPOTS ARE INCLUDING THE DX CALLSIGN (FIRST ONE DROPPED THE CALL FOR SOME REASON BUT IT MAY HAVE JUST BEEN AN ERRANT SPOT OR THAT PART OF THE AUDIO WAS LOST FOR SOME REASON).

THE LAST 4 OR SO 6M SPOTS HAVE BEEN ANNOUNCED CORRECTLY WITH DX CALL INCLUDED

SETTINGS ON THE AUDIO SCREEN ARE:

FIRST 5 BOXES UNDER AUDIO ALARM ARE TICKED - LAST 4 BOXES NOT TICKED.
ALARM TRIGGER IS STILL FILTERED

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

On the Config window's Audio tab, what boxes are checked?

I assume the "Alarm trigger" panel is still set to Filtered.


Re: Spot Collector / Spot Spy Configuration

Dave AA6YQ
 

On the Config window's Audio tab, what boxes are checked?

I assume the "Alarm trigger" panel is still set to Filtered.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
vk3ajj
Sent: Tuesday, July 07, 2009 2:47 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: Spot Collector / Spot Spy Configuration


OK - I HAVE MADE THAT CHANGE

STRANGE RESULT HOWEVER
6M SPOTS NO LONGER APPEAR ON THE SCREEN (VERY GOOD) - HOWEVER VOICE
ANNOUNCEMENT FOR 6M STILL OCCURS BUT IT ONLY SAYS "DX 6 METRES SSB" - IE IT
DOES NOT GIVE THE STATION CALLSIGN ACTUALLY SPOTTED FOR 6 METRES.




If the ODX cell for the UT7IL spot is empty, that means that
SpotCollector doesn't know the location of SM7GVF, and thus can't compute
the distance between you and SM7GVF. On the Config window's General tab,
check the "Lookup missing location info" box, and SpotCollector will use
the
DXCC and USAP databases to determine the location of spotting stations so
it
can perform the filtering you seek.

73,

Dave, AA6YQ



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

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.5/2220 - Release Date: 07/05/09
17:54:00


Re: Spot Collector / Spot Spy Configuration

vk3ajj <vk3ajj@...>
 

OK - I HAVE MADE THAT CHANGE

STRANGE RESULT HOWEVER
6M SPOTS NO LONGER APPEAR ON THE SCREEN (VERY GOOD) - HOWEVER VOICE ANNOUNCEMENT FOR 6M STILL OCCURS BUT IT ONLY SAYS "DX 6 METRES SSB" - IE IT DOES NOT GIVE THE STATION CALLSIGN ACTUALLY SPOTTED FOR 6 METRES.


If the ODX cell for the UT7IL spot is empty, that means that
SpotCollector doesn't know the location of SM7GVF, and thus can't compute
the distance between you and SM7GVF. On the Config window's General tab,
check the "Lookup missing location info" box, and SpotCollector will use the
DXCC and USAP databases to determine the location of spotting stations so it
can perform the filtering you seek.

73,

Dave, AA6YQ


Re: Spot Collector / Spot Spy Configuration

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
vk3ajj
Sent: Tuesday, July 07, 2009 2:06 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: Spot Collector / Spot Spy Configuration


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

snip<
In the UT7IL spot database entry, what value is shown in the ODX column?
(if
UT7IL were spotted by SM7GVF but later spotted by VK3DX, then the low ODX
would correctly cause the spot database entry to be both visible and
announced).
THERE IS NO FIGURE SHOWING IN THE ODX COLUMN FOR THIS SPOT. VERY FEW SPOTS
ACTUALLY HAVE A NUMBER IN THIS COLUMN. IN THE OMDX COLUMN FIGURE IS 8000

If the ODX cell for the UT7IL spot is empty, that means that
SpotCollector doesn't know the location of SM7GVF, and thus can't compute
the distance between you and SM7GVF. On the Config window's General tab,
check the "Lookup missing location info" box, and SpotCollector will use the
DXCC and USAP databases to determine the location of spotting stations so it
can perform the filtering you seek.

73,

Dave, AA6YQ


Re: Spot Collector / Spot Spy Configuration

vk3ajj <vk3ajj@...>
 

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

At the bottom of SpotCollector's Main window, there is a Filter panel
labeled with the word "Filter" in blue in its upper left corner. What words
(if any) appear after the word Filter?
THERE ARE NO WORDS IN THIS BOX


In the UT7IL spot database entry, what value is shown in the ODX column? (if
UT7IL were spotted by SM7GVF but later spotted by VK3DX, then the low ODX
would correctly cause the spot database entry to be both visible and
announced).
THERE IS NO FIGURE SHOWING IN THE ODX COLUMN FOR THIS SPOT. VERY FEW SPOTS ACTUALLY HAVE A NUMBER IN THIS COLUMN. IN THE OMDX COLUMN FIGURE IS 8000





As an experiment, please change the 6m "Max origin DX" in the "Band Filter"
window from 8000 to 800 (you'll need to uncheck the 6m box and then check it
again after making the change). Does the UT7IL spot database entry
disappear, or is it still visible in the Spot Database Display?
OK - WILL GIVE THIS A TRY


Re: Spot Collector / Spot Spy Configuration

Dave AA6YQ
 

At the bottom of SpotCollector's Main window, there is a Filter panel
labeled with the word "Filter" in blue in its upper left corner. What words
(if any) appear after the word Filter?

In the UT7IL spot database entry, what value is shown in the ODX column? (if
UT7IL were spotted by SM7GVF but later spotted by VK3DX, then the low ODX
would correctly cause the spot database entry to be both visible and
announced).

As an experiment, please change the 6m "Max origin DX" in the "Band Filter"
window from 8000 to 800 (you'll need to uncheck the 6m box and then check it
again after making the change). Does the UT7IL spot database entry
disappear, or is it still visible in the Spot Database Display?

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
vk3ajj
Sent: Tuesday, July 07, 2009 1:41 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: Spot Collector / Spot Spy Configuration


Thanks Dave

Answers follow:

Does the Spot Database Display show 6m spots by stations outside your
8000 km radius?
(Yes - UT7IL just spotted sm7gvf on 6M - ut7il is outside of this radius -
he is 13,000 kms).

On the Config window's Audio tab, do you have the "Alarm trigger" panel
set to Filtered? (yes -I had this set correctly)





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

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.5/2220 - Release Date: 07/05/09
17:54:00


Re: Spot Collector / Spot Spy Configuration

vk3ajj <vk3ajj@...>
 

Thanks Dave

Answers follow:

Does the Spot Database Display show 6m spots by stations outside your
8000 km radius?
(Yes - UT7IL just spotted sm7gvf on 6M - ut7il is outside of this radius - he is 13,000 kms).

On the Config window's Audio tab, do you have the "Alarm trigger" panel set to Filtered? (yes -I had this set correctly)


Re: Spot Collector / Spot Spy Configuration

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
vk3ajj
Sent: Tuesday, July 07, 2009 1:05 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: Spot Collector / Spot Spy Configuration


Hello Dave
Thanks for the prompt reply.

I must be doing something wrong in respect to 6M spots -

Under spot collector band filter - I have the following settings:

Enable Start/ End & max origin filter box - ticked on

correct

6M enable box is ticked

correct

For 6 metres I have no start or end UTC time (left blank) and have put max
origin of dx as 8000 (kilometres).

I have nothing inserted into the sunrise / sunset boxes and the two "Ignore"
boxes are unticked.

Correct (its not relevant to your 6m setting, but if you run DXView, the
sunrise and sunset boxes will be automatically kept up-to-date on a daily
basis).


Despite this I am still getting voice announcements for all 6 metre spots.

Does the Spot Database Display show 6m spots by stations outside your
8000 km radius?

On the Config window's Audio tab, do you have the "Alarm trigger" panel
set to Filtered?


Is the origin distance relating to the spotter or the dx station actually
spotted?

A Spot Database Entry's Origin distance is the closest distance between
any station that spotted the Entry's DX station and your QTH.

73,

Dave, AA6YQ


Re: Spot Collector / Spot Spy Configuration

vk3ajj <vk3ajj@...>
 

Hello Dave
Thanks for the prompt reply.

I must be doing something wrong in respect to 6M spots -

Under spot collector band filter - I have the following settings:

Enable Start/ End & max origin filter box - ticked on
6M enable box is ticked
For 6 metres I have no start or end UTC time (left blank) and have put max origin of dx as 8000 (kilometres).

I have nothing inserted into the sunrise / sunset boxes and the two "Ignore" boxes are unticked.

Despite this I am still getting voice announcements for all 6 metre spots.

Is the origin distance relating to the spotter or the dx station actually spotted?

Once I have put the above settings in - is there anything else I need to do on other screens to make sure that I only get an alarm / voice announcement for the 6 metre spots within my geogrpahical vicinity

Cheers and Thanks
Paul



SpotCollector can be configured to
-- identify and announce needed 6m spots reported by stations whose distance
from your QTH does not exceed a specified value

-- identify and announce needed 160m and 80m spots based on time of day,
optionally referenced to your current and sunset time


For an introduction to filtering, see
<http://www.dxlabsuite.com/dxlabwiki/SpotDatabaseFilter>


For a comprehensive description, see
<http://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm>


SpotCollector automatically determines what's "needed" from your DXKeeper
log and from your specified DXing objectives; see

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

Thus manually populating and maintaining a 338x14 cell matrix is
unnecessary. DXKeeper uses the same information to automatically generate
outgoing QSL cards or labels for QSOs whose confirmation would advance your
DXCC award progress.

You can configure audible announcements to be "unworked only" or
"unworked or unconfirmed", but in SpotCollector this applies to all bands
and modes: it cannot be made band-specific or mode-specific. I don't know if
SpotSpy relieves this constraint.

As you review the above material, don't hesitate to post questions or
concerns here.

73,

Dave, AA6YQ


Re: 40 meter SSB not CW

Dave AA6YQ
 

If a spot's notes mention a mode, then SpotCollector uses that mode in the
Spot Database Entry. If no mode is mentioned in the spot notes, then
SpotCollector determines the mode by consulting your sub-band definition
file, which specifies ranges of frequencies (sub-bands) and defines a mode
for each. You can modify your sub-band definition file to reflect the normal
40m activity in your part of the world, or you can create multiple sub-band
definitions files -- each reflecting conditions during a particular kind of
contest or during a particular season -- and select the appropriate one to
use during each operating session. This is described in

<http://www.dxlabsuite.com/spotcollector/Help/ConfigurationGeneral.htm#Sub-b
and Definition panel>

You can also view this information by clicking one of SpotCollector's Help
buttons and navigating as follows:

Configuring SpotCollector > General > Sub-band Definition

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of AD5VJ
Bob
Sent: Tuesday, July 07, 2009 12:00 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] 40 meter SSB not CW


For some reason spotcollector doesn't show a 40 meter dx station as SSB it
shows CW and that is not the correct mode therefore I
have to change the rig after clicking on a spot.

Bob AD5VJ



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

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.5/2220 - Release Date: 07/05/09
17:54:00


40 meter SSB not CW

AD5VJ Bob <rtnmi@...>
 

For some reason spotcollector doesn't show a 40 meter dx station as SSB it shows CW and that is not the correct mode therefore I
have to change the rig after clicking on a spot.

Bob AD5VJ


Re: Dangerously close to ZOMBIES!

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Earl Needham
Sent: Monday, July 06, 2009 11:24 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Dangerously close to ZOMBIES!



I guess I messed up somewhere in the entire process.

The main reason is that I don't completely understand how to set up
different locations in DXKeeper. You may know that I have been roving
on 6 meters lately, through a few rare grids -- DM71, DM41, DM83, etc.

So I went into TQSL and created a location called DM71 and I used
TQSL to upload 3 QSO's from that grid into LoTW. Next, I created a
location called DM83 and used TQSL to upload 6 QSOs from that grid. So
far so good --

But when I went into DXKeeper and tried to get those QSOs into my
log, I was at a loss how to do so. Figuring I'd try SOMETHING, I
manually entered all of these same QSOs that I already uploaded to
LoTW.

Then, instead of simply changing the LoTW status to "Y", I didn't
think this whole arrangement would figure it all out, so I then used
DXKeeper to upload the same QSOs to LoTW. I hoped this would update
DXKeeper and keep LoTW the same. Instead, LoTW is still OK, but the
LoTW status on each of these QSOs is "U". I can go to the LoTW web site
and review all these QSOs and they show in the correct grid -- another
concern that has been salved -- but what should I do with DXKeeper?
Just wait a while and see if the status eventually updates? Or should I
change it manually???

Assuming that you entered the QSOs in DXKeeper exactly as you entered
them in TQSL, then on the Main window's QSL tab, set the "QSL Via" panel to
LotW and click the "Sync LotW QSOs" button. If LotW accepted the QSOs you
uploaded via TQSL, and if they exactly match what you re-entered in
DXKeeper, then each QSO's "LOTW QSL SENT" status should change from 'U'
(uploaded by not accepted) to 'Y' (accepted) once LotW processes your
uploaded QSOs. Then you can click "Sync LotW QSLs" to see what confirmations
were generated.

Entering those QSOs into TQSL and uploading them from there was not
problematic, but as you correctly determined, you must also enter them into
DXKeeper -- so it would have been less work (and less error-prone) to
capture them in DXKeeper and upload them from there. The correct set of
actions in this scenario is

1. direct TQSL to create station locations for DM71, DM41, DM82, etc. (as
you did)

2. in DXKeeper,

2a. create "my QTHs" for DM71, DM41, DM82, etc.

2b. log the QSOs in DXKeeper, assigning the appropriate "my QTH" identifier
for each

2c. filter the "Log Page Display" to contain only QSOs whose "my QTH"
identifier is DM71

2d. on the "QSL Config" window's LotW tab, set the TQSL panel's "station
location" to DM71

2e. on the Main window's QSL tab, set the "QSL Via" panel to LotW, and click
"Add Requested"; this should populate the QSL Queue with your QSOs made from
DM71

2f. click the "Upload to LotW" button

2g. repeat steps 2c through 2f for DM41, DM83, etc.

This dance is required because TQSL requires all QSOs in an uploaded
batch to be from the same Station Location. Automating the upload of a batch
of QSOs not all from the same station location is "on the list" -- it
requires adding an "LotW Station Location" to each "my QTH" so DXKeeper can
determine whether or not all QSOs to be uploaded are from the same station
location, and if they're not do the filtering, sub-dividing, and multiple
invocations of TQSL on your behalf.

73,

Dave, AA6YQ


Re: Feature request for Enity Overrides

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of DANNY
DOUGLAS
Sent: Monday, July 06, 2009 11:21 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] Feature request for Enity Overrides


Speaking of overrides. Today, and yesterday, I tried to do a right click on
a spot that wasnt coming up with a country (the TO8YY in FJ right now). The
"create an override for TO8YY" line (along with the rest of the drop down
selections) came up and I clicked on it. Results- nothing. The drop down
window just goes away. Happened several times. I then went to CONFIG -
ENTITY OVERRIDES and see there is no empty space for a new override. Took
one out, added the one I needed. So it appears if its all filled up, there
will be no positive action taken.

I modified the next version of SpotCollector to inform you that all
overrides are in use in that scenario. Thanks, Danny...

73,

Dave, AA6YQ


Re: DXLAB problem soved - another problem !!

Dave AA6YQ
 

I am unable to replicate this behavior -- with another PC on my network
displaying SpotCollector's Spot Database Display in a web browser, I can
prune or clear the Spot Database and then direct the web browser to refresh
with no need to restart SpotCollector's web server.

I've emailed you and Jose N1BAA a new version of SpotCollector that
automatically restarts its web server after the Spot Database is pruned or
cleared. Please let me know if this eliminates the problems you each have
reported. Thanks....

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Rainer Englert
Sent: Monday, July 06, 2009 4:47 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] DXLAB problem soved - another problem !!



Hi Dave,

thanks for your advice. It was not possible to install DXKeeper on my
nwo PC, it was a faulty Microsoft Windows Installer. I updated it and
now everything was OK.

I found another problem as follows:

I have a WEB PAD I use for emails and so on. I have activated the
WEB SERVER in SpotCollector. On my web pad i use the URL
192.168.123.202/spots and I can see the spots.

This works fine, but after a while the web werver does not produce
any more spots. The page itself is beeing refreshed, but no new spots
any more. I found out that there is a connection with the PRUNE
facility. When you prune or clear the spot database and restart the
web server, ist works fine gain - until the database fills again and
with 200-300 entries there are no more spots. What can be the reason
for that behaviour ? Is it perhaps a bug ?

vy 73 de Rainer DF2NU



--
GRATIS f�r alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01


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

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.3/2217 - Release Date: 07/05/09
05:53:00


Dangerously close to ZOMBIES!

Earl Needham
 

I guess I messed up somewhere in the entire process.

The main reason is that I don't completely understand how to set up different locations in DXKeeper. You may know that I have been roving on 6 meters lately, through a few rare grids -- DM71, DM41, DM83, etc.

So I went into TQSL and created a location called DM71 and I used TQSL to upload 3 QSO's from that grid into LoTW. Next, I created a location called DM83 and used TQSL to upload 6 QSOs from that grid. So far so good --

But when I went into DXKeeper and tried to get those QSOs into my log, I was at a loss how to do so. Figuring I'd try SOMETHING, I manually entered all of these same QSOs that I already uploaded to LoTW. Then, instead of simply changing the LoTW status to "Y", I didn't think this whole arrangement would figure it all out, so I then used DXKeeper to upload the same QSOs to LoTW. I hoped this would update DXKeeper and keep LoTW the same. Instead, LoTW is still OK, but the LoTW status on each of these QSOs is "U". I can go to the LoTW web site and review all these QSOs and they show in the correct grid -- another concern that has been salved -- but what should I do with DXKeeper? Just wait a while and see if the status eventually updates? Or should I change it manually???

Thanks, Dave -- and just keep calling me confused!
Earl

--
KD5XB -- Earl Needham
Clovis, New Mexico DM84jk
http://groups.yahoo.com/group/cw_bugs
Quoting from the Coast Guard: ZUT

137861 - 137880 of 207995