1. DXLab@groups.io
  2. Messages
   Date   
Re: Clublog

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Rich - W3ZJ
Sent: Sunday, August 05, 2012 11:24 AM
To: DXLab
Subject: [dxlab] Clublog


Two of my last three QSO's (D3AA on 15M CW and UN/UA4WHX on 17M CW) were
rejected by Clublog as Duplicates. I have never worked either of those
stations before on those bands/modes. I later did a manual upload to
Clublog and those were accepted as two "new" QSO's:

Dear W3ZJ,

Congratulations - your ADIF file has been imported without warnings. A total of 2 new QSOs have been uploaded.

* Software: DXKEEPER
* File name: ClubLogUpload.ADI (488 B)
* New QSOs: 2

I saw this once a couple of days ago also but didn't report it. Who is
messing up here DXLab or Clublog?

If there are no previous QSOs in your log and the ClubLogUpload.ADI file created by DXKeeper doesn't contain duplicates, then I don't see how it can be a DXKeeper problem.
73,

Dave, AA6YQ
Re: DXKeeper 10.3.7 won't launch

Dave AA6YQ
 

If Chkdisk can't correct the damage to DXKeeper 10.3.7, then the procedure
below will get you a new DXKeeper1037.exe

Unless there's some other explanation for the low-level damage to your
files, you might consider replacing your hard drive. This would certainly be
a good time to make -- and verify -- a full backup.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 4:34 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] DXKeeper 10.3.7 won't launch


OK, as soon as the check disk finishes I'll do that!

Thanks, Dave!!

On Sun, Aug 5, 2012 at 3:26 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

**


AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 9:59 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] DXKeeper 10.3.7 won't launch

Via Launcher it times out at 180 seconds, followed by the windows error
box
'DXKeeper has encountered an error and needs to close'. After that I
re-booted the PC, same behavior.

Double-clicking the DXKeeper.exe from Windows Explorer brings only the
same
error box.

Double-clicking the 1037 version from Windows Explorer brings only the
same
error box.

Double-clicking the 1032 version launches normally.

Also, sometimes the error box reads "Google Chrome has encountered an
error..." although Chrome is not running.

That is in addition to the DXKeeper error, not in place of.

For now, I've pointed the Launcher to version 10.3.2, and all is well.

If there's an errorlog.txt file in your Launcher and/or DXKeeper
folder,
please attach them to an email message and send them to

aa6yq (at) ambersoft.com

The most likely possibility is that your antivirus or firewall is
preventing DXKeeper 10.3.7 from starting; make sure these applications
consider DXKeeper "safe".

If that's not it, then in your DXKeeper folder,
1. delete DXKeeper1037.exe

2. make a copy of the file DXKeeper1032.exe and name this copy
DXKeeper.exe
(if you haven't done this already)

3. start the Launcher, and direct it to upgrade DXKeeper again

73,

Dave, AA6YQ




--


===================
Chuck Chandler
chandlerusm@gmail.com
===================






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

Yahoo! Groups Links



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1424 / Virus Database: 2437/5179 - Release Date: 08/05/12
Re: Update to DXKeeper 10.3.7 won't launch

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 4:33 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Update to DXKeeper 10.3.7 won't launch


I posted earlier that DXK 10.3.7 won't launch. I've done some more
checking.

First off, I've been away and had the radio PC off. I turned it on
Saturday and ran N1MM Logger to play a bit in the NAQP. This morning was
my first try to launch DXLabs, except I did have Spot Collector running
before the contest, as well as after.

Here's a list of what I've done so far.......

I determined that Google Chrome won't launch for some reason. It simply
keeps popping up '...needs to close' boxes and never launches.

I did another re-boot, and then realized the GMail notifier was running, so
I terminated that. Chrome still won't launch.

Next step: remove Chrome using Add/Remove in Control Panel. The radio PC
rarely, if ever, browses the web anyways. Followed by a re-boot.

DXKeeper 10.3.2 launches OK from the icon. 10.3.7 again fails with the
same error box. This time IE brought up a website saying the error was on
the hard drive. Using Eventviewer I got the event description:

Windows cannot access the file ...DXKeeper 1037 for one of the following
reasons:
Problem with network connection
Problem with disk
Problem with storage drivers
Disk is missing.

Checking the hard drive properties showed plenty of free space... 21 GB
used, 444 GB free. Next step is to error check and repair the disk.
So far, Windows has replaced bad clusters in the file
DXView/Databases/LOTW.mdb, in DXKeeper.exe, and in several other places.

Still working on the free space, which will take a while. I'll update when
done.....

Best of luck on the recovery, Chuck (fingers crossed here!). Does the
Windows event log indicate any history of disk errors, or was this a
one-time event?

73,

Dave, AA6YQ
Re: DXKeeper 10.3.7 won't launch

Chuck, WS1L
 

OK, as soon as the check disk finishes I'll do that!

Thanks, Dave!!

On Sun, Aug 5, 2012 at 3:26 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

**


AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 9:59 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] DXKeeper 10.3.7 won't launch

Via Launcher it times out at 180 seconds, followed by the windows error box
'DXKeeper has encountered an error and needs to close'. After that I
re-booted the PC, same behavior.

Double-clicking the DXKeeper.exe from Windows Explorer brings only the same
error box.

Double-clicking the 1037 version from Windows Explorer brings only the same
error box.

Double-clicking the 1032 version launches normally.

Also, sometimes the error box reads "Google Chrome has encountered an
error..." although Chrome is not running.

That is in addition to the DXKeeper error, not in place of.

For now, I've pointed the Launcher to version 10.3.2, and all is well.

If there's an errorlog.txt file in your Launcher and/or DXKeeper folder,
please attach them to an email message and send them to

aa6yq (at) ambersoft.com

The most likely possibility is that your antivirus or firewall is
preventing DXKeeper 10.3.7 from starting; make sure these applications
consider DXKeeper "safe".

If that's not it, then in your DXKeeper folder,
1. delete DXKeeper1037.exe

2. make a copy of the file DXKeeper1032.exe and name this copy DXKeeper.exe
(if you haven't done this already)

3. start the Launcher, and direct it to upgrade DXKeeper again

73,

Dave, AA6YQ




--


===================
Chuck Chandler
chandlerusm@gmail.com
===================


[Non-text portions of this message have been removed]
Update to DXKeeper 10.3.7 won't launch

Chuck, WS1L
 

I posted earlier that DXK 10.3.7 won't launch. I've done some more
checking.

First off, I've been away and had the radio PC off. I turned it on
Saturday and ran N1MM Logger to play a bit in the NAQP. This morning was
my first try to launch DXLabs, except I did have Spot Collector running
before the contest, as well as after.

Here's a list of what I've done so far.......

I determined that Google Chrome won't launch for some reason. It simply
keeps popping up '...needs to close' boxes and never launches.

I did another re-boot, and then realized the GMail notifier was running, so
I terminated that. Chrome still won't launch.

Next step: remove Chrome using Add/Remove in Control Panel. The radio PC
rarely, if ever, browses the web anyways. Followed by a re-boot.

DXKeeper 10.3.2 launches OK from the icon. 10.3.7 again fails with the
same error box. This time IE brought up a website saying the error was on
the hard drive. Using Eventviewer I got the event description:

Windows cannot access the file ...DXKeeper 1037 for one of the following
reasons:
Problem with network connection
Problem with disk
Problem with storage drivers
Disk is missing.

Checking the hard drive properties showed plenty of free space... 21 GB
used, 444 GB free. Next step is to error check and repair the disk.
So far, Windows has replaced bad clusters in the file
DXView/Databases/LOTW.mdb, in DXKeeper.exe, and in several other places.

Still working on the free space, which will take a while. I'll update when
done.....

73 de Chuck, WS1L





---------- Forwarded message ----------
From: Chuck Chandler <chandlerusm@gmail.com>
Date: Sun, Aug 5, 2012 at 8:58 AM
Subject: DXKeeper 10.3.7 won't launch
To: dxlab@yahoogroups.com


Via Launcher it times out at 180 seconds, followed by the windows error box
'DXKeeper has encountered an error and needs to close'. After that I
re-booted the PC, same behavior.

Double-clicking the DXKeeper.exe from Windows Explorer brings only the same
error box.

Double-clicking the 1037 version from Windows Explorer brings only the same
error box.

Double-clicking the 1032 version launches normally.

Also, sometimes the error box reads "Google Chrome has encountered an
error..." although Chrome is not running.

That is in addition to the DXKeeper error, not in place of.

For now, I've pointed the Launcher to version 10.3.2, and all is well.

73 de Chuck, WS1L

--


===================
Chuck Chandler
chandlerusm@gmail.com
===================




--


===================
Chuck Chandler
chandlerusm@gmail.com
===================
Re: SpotCollector colors not tracking

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Ken Bandy, KJ9B
Sent: Sunday, August 05, 2012 12:03 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] SpotCollector colors not tracking


I have noticed lately (the last week or so) that some of my spotted stations
colors in Spot Collector aren't showing up properly. For instance, some
entities that I have worked show up red (for needed), when they should be
black or green.

The next time this happens, right-click the Spot Database Entry in
question and select the "Display Award Tracking" menu item. An "Award
Tracking" window will appear that explains why SpotCollector colored the
entry as it did. If you find this explanation to be incorrect, let me know.

73,

Dave, AA6YQ
Re: LOTW/DXKeeper Station Location match

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
alanswinger
Sent: Sunday, August 05, 2012 12:00 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: LOTW/DXKeeper Station Location match


Dave - I did follow the LoTW Certif transfer insts, and had TQSL and TQSL
Cert saved on a DVD after I renewed them last yr. I also checked the
station_data files on both PCs and they were the same except for unique
computer user names. So, I Edited the Station Location file in TQSL Cert on
the new PC to make it is the same as the Old PC and the Station File, and
also made sure Keeper reflected the edit.
I uploaded all QSOs in Keeper since I put the new PC on line (7/5-8/5/12) to
LoTW this morning. LoTW confirmed receipt so I snch'd QSOs and QSLs, and got
the following message:
- LOTW OPerations: 4 QSLs processed; 4 Log entries updated, 0 errors. No new
confirmations of previously unconfirmed entity-bands or entity-modes.

I expected nothing new, so the message is correct from that aspect, and
appears that the upload and responses are correct. Also checked the LoTW
Sent Boxes and all show a Y and today's date.

Therefore, it appears that all is working properly. Other than receiving a
LoTW QSO confirmation, is there anything else to check?

That all sounds good, Alan, but the proof of the pudding will be when one
of the QSOs logged and uploaded from your new laptop gets confirmed via
LotW.

73,

Dave, AA6YQ
Re: DXKeeper 10.3.7 won't launch

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 9:59 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] DXKeeper 10.3.7 won't launch


Via Launcher it times out at 180 seconds, followed by the windows error box
'DXKeeper has encountered an error and needs to close'. After that I
re-booted the PC, same behavior.

Double-clicking the DXKeeper.exe from Windows Explorer brings only the same
error box.

Double-clicking the 1037 version from Windows Explorer brings only the same
error box.

Double-clicking the 1032 version launches normally.

Also, sometimes the error box reads "Google Chrome has encountered an
error..." although Chrome is not running.

That is in addition to the DXKeeper error, not in place of.

For now, I've pointed the Launcher to version 10.3.2, and all is well.

If there's an errorlog.txt file in your Launcher and/or DXKeeper folder,
please attach them to an email message and send them to

aa6yq (at) ambersoft.com

The most likely possibility is that your antivirus or firewall is
preventing DXKeeper 10.3.7 from starting; make sure these applications
consider DXKeeper "safe".

If that's not it, then in your DXKeeper folder,
1. delete DXKeeper1037.exe

2. make a copy of the file DXKeeper1032.exe and name this copy DXKeeper.exe
(if you haven't done this already)

3. start the Launcher, and direct it to upgrade DXKeeper again

73,

Dave, AA6YQ
Re: Lotw Multiple Station Locations

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Bob
Sent: Sunday, August 05, 2012 9:56 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: Lotw Multiple Station Locations


Dave

LOL

Been doing it for 8 years and have never made a mistake and created a
zombie. To be honest I am much more likely to make a mistake now since the
application fixes a location rather than asking me??

Immediately beneath the "Upload to LotW" button on the Main window's "Log
QSOs" tab, DXKeeper shows you both the selected "LotW Station Location" and
the "Station Callsign" it specifies.

DXKeeper will not upload a QSO to LotW unless the "Station Callsign"
specified in that QSO matches the "Station Callsign" specified in the
selected "Station Location".

Thus you can no longer create a Zombie by making a single mistake.
Creating a Zombie requires

1. logging the QSO with the wrong Station Callsign item

2. selecting the wrong "LotW Station Location" -- one that specifies a
"Station Callsign" that just happens to match the erroneous "Station
Callsign" item logged in the QSO being uploaded.


The blank selection is still there why not continue to have a selection when
it is set and label the upload selection as (user selection) rather than
having to do 2 menus down to reset it?

Because that would enable a user to upload a QSO to LotW with a "Station
Location" that doesn't match the QSO's "Station Callsign" item, which will
both create Zombies in LotW and cause "Sync LotW QSOs" and "Sync LotW QSLs"
to display "QSO not found in log" messages -- which frustrates users and
causes me to spend more time helping users debug and correct these scenarios
instead of adding new features to DXLab.

73,

Dave, AA6YQ
Re: County reporting in Pathfinder

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Paul Beringer
Sent: Sunday, August 05, 2012 9:39 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] County reporting in Pathfinder


After the NAQP contest yesterday, I imported the QSO's into DXK and did a
mass lookup using XML on QRZ. I noticed that many counties were reported as
invalid and had I to do 78 manual lookups to correct them. The counties that
failed came up as "state,zipcode" in the county field in DXK. For example,
"WA,98012" instead of "WA,Snohomish". I haven't noticed that type of county
reporting after a mass lookup. Of course there were the expected VA counties
that failed too but those are normal.

Note: when I enter a call into the DXK capture dialog, the county reporting
is OK.

What's an example of a callsign whose lookup yielded "State,ZIP" instead
of "State,County"?

Do you still have the ADIF file you imported? If so, open it with
Notepad, search for one of the 78 callsigns in question. Is there a CNTY tag
in that callsign's record? If so, what does it specify?

73,

Dave, AA6YQ
Re: Spotcollector /startup commands?

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
pa3c_aart
Sent: Sunday, August 05, 2012 7:26 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Spotcollector /startup commands?


Is it possible to start SC with initial commands or /paramameters? like
Spotcollector /filter=[sql-button]?

It's not, Aart.
73,

Dave, AA6YQ
Re: Winkey and <stop>

iain macdonnell - N6ML
 

On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@free.fr> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a ‘PTT off’ buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

73,

~iain / N6ML
Re: SpotCollector colors not tracking

iain macdonnell - N6ML
 

On Sun, Aug 5, 2012 at 9:02 AM, Ken Bandy, KJ9B <kj9b@arrl.net> wrote:



I have noticed lately (the last week or so) that some of my spotted
stations
colors in Spot Collector aren't showing up properly. For instance, some
entities that I have worked show up red (for needed), when they should be
black or green. Just for the heck of it, I did a "recompute" on DXKeeper,
thinking that might help, but it had no effect. I also have stopped and
restarted the suite, as well as rebooted the machine. Neither of these had
any effect either. I am running the entire suite.

Any help or suggestions would be appreciated.
A recompute in DXKeeper will not affect existing spot database
entries. If you want those to be updated, you will need to Recompute
in SpotCollector too (Config -> Spot Database).

Failing that, when you see a spot database entry that is coded
incorrectly, right-click on it and select "Display award tracking for
..." to see why it was coded as it was...

73,

~iain / N6ML
Re: request: special callsign in SC

iain macdonnell - N6ML
 

You might choose to hide a spot database entry for the special
callsign for some reason... perhaps it's EME, a mis-spot (it's
actually some other DX station, but the idiots keep repeating a bad
spot), etc.

73,

~iain / N6ML

On Sun, Aug 5, 2012 at 1:32 AM, pa3c_aart <pa3c@amsat.org> wrote:

A special callsign in never hidden: Hidden<>Y inside the brackets

(Hidden <> 'Y' and <BANDFILTER> and <NEEDFILTER> and <MODEFILTER> and
<CONTFILTER>)or Callsign = <SPECIALCALLSIGN>

Aart PA3C



To be more complete, you might try something like:
Hidden <> 'Y' and
((<BANDFILTER> and <NEEDFILTER> and <MODEFILTER> and <CONTFILTER>)

or Callsign = 'JW2US')

73,

~iain / N6ML
Re: Lotw Multiple Station Locations

Bob
 

Rich

Not a problem as we are now on the same page...

Peace

Bob

to mean that you were working stations with W1SLG and importing them to
your KB1ZJU log. As I look at it again I guess all you were saying is
that you have two station locations for KB1JZU which is perfectly OK. A
misunderstanding, Sorry.

73, Rich - W3ZJ
Re: Lotw Multiple Station Locations

Richard B Drake
 

OK, I took this comment:

I have separate logs for KB1JZU & W1SLG not a problem.
I do however work some folks from ME on my KB1JZU call and then add them to the log down here with a differnent location. About once a month.

Bob

to mean that you were working stations with W1SLG and importing them to your KB1ZJU log. As I look at it again I guess all you were saying is that you have two station locations for KB1JZU which is perfectly OK. A misunderstanding, Sorry.

73, Rich - W3ZJ

Bob wrote:
Rich

You are getting me upset.

Please read the notes before you respond!!!!!!

W1SLF was only mentioned because it illustrates why Dave's change is beneficial for those of us managing multiple INDEPENDENT logs.

Let me say it again: W1SLF & KB1JZU contacts are NEVER COMBINED!!!!

Let me say it again: W1SLF & KB1JZU contacts are NEVER COMBINED!!!!

Let me say it again: If I operate under the W1SLF call in Maine it goes into the W1SLF log ONLY. It NEVER is combined with KB1JZU

Since I have a second home in Maine when I log a contact as KB1JZU in Maine it is combined with my log at my other QTH in MA using a different location code to comply with award requirements. In these instances I am NOT USING A W1SLF Call!!!!

If you still don't understand drop me an email note and lets take this converstastion off line.

Bob KB1JZU
Re: FT900 Problems

Joe Subich, W4TV
 

Do you have an RS-232 to TTL conversion circuit in the cable? The CAT
input of the FT-900 is TTL (0/5V) and the typical serial port is RS-232
(+/-10V or more). In addition, the "sense" of the data (high/low) is
reversed between RS-232 and the Yaesu transceivers.

A simple two transistor converter is here: www.min.at/prinz/oe1rib/CAT/
If you ignore the "power source" switch and PTT circuit the interface
cab be powered from the serial port by setting RTS and/or DTR always
on in Commander.

73,

... Joe, W4TV

On 8/5/2012 11:17 AM, Richard Mogford wrote:
Hi

I have a Yaesu FT900. I downloaded Commander and made a serial cable to
go from my IBM Thinkpad T30 to the radio's CAT connector.

I have done this before with another FT900 which is on my sailboat, but
it has been a few years ago.

I looked up the pin outs for the radio and serial connector. I am using
the ground, serial (data) in, and serial (data out).

I have the data out from the radio connected to the data in pin on the
computer serial port. Likewise the data in at the ratio is connected to
the data out of the computer. And, of course, the third wire is ground.
(I used this approach with another device a few months ago, and it
worked OK.)

I looked up the serial port settings for my radio: 1 start bit, 8 data
bits, no parity, 2 stop bits, DTR and RTS off. I am using COM1 on the
computer.

With this set up, I cannot get the Commander to connect to the radio.
There is something wrong with my cable or setup.

I am sorry to bother you, but do you have any suggestions? I think I
must have missed something obvious.

Richard
AE6XO





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

Yahoo! Groups Links
SpotCollector colors not tracking

Ken Bandy, KJ9B <kj9b@...>
 

I have noticed lately (the last week or so) that some of my spotted stations
colors in Spot Collector aren't showing up properly. For instance, some
entities that I have worked show up red (for needed), when they should be
black or green. Just for the heck of it, I did a "recompute" on DXKeeper,
thinking that might help, but it had no effect. I also have stopped and
restarted the suite, as well as rebooted the machine. Neither of these had
any effect either. I am running the entire suite.

Any help or suggestions would be appreciated.

73,
Ken, KJ9B
Re: LOTW/DXKeeper Station Location match

Alan Swinger
 

Dave - I did follow the LoTW Certif transfer insts, and had TQSL and TQSL Cert saved on a DVD after I renewed them last yr. I also checked the station_data files on both PCs and they were the same except for unique computer user names. So, I Edited the Station Location file in TQSL Cert on the new PC to make it is the same as the Old PC and the Station File, and also made sure Keeper reflected the edit.
I uploaded all QSOs in Keeper since I put the new PC on line (7/5-8/5/12) to LoTW this morning. LoTW confirmed receipt so I snch'd QSOs and QSLs, and got the following message:
- LOTW OPerations: 4 QSLs processed; 4 Log entries updated, 0 errors. No new confirmations of previously unconfirmed entity-bands or entity-modes.

I expected nothing new, so the message is correct from that aspect, and appears that the upload and responses are correct. Also checked the LoTW Sent Boxes and all show a Y and today's date.

Therefore, it appears that all is working properly. Other than receiving a LoTW QSO confirmation, is there anything else to check?

Thanks,
Alan K9MBQ

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

AA6YQ comments below

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
alanswinger
Sent: Saturday, August 04, 2012 6:34 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: LOTW/DXKeeper Station Location match


Good catch - there was a spelling error which has been corrected, and I did
what Dave said and got the TQSL file (I think) in line with whats in the
Station data file. That said, when i upload nothing new happens . . . given
that when Iuploaded on the Old PC I received a msg about 2 pgs long of no
Matches with what I Uploaded on the New PC.

This is ridiculous and surely there must be a Simple solution for we
non-geeks! Hep - alan K9MBQ

There are step-by-step instructions for setting up LotW on a second PC in
<http://www.dxlabsuite.com/dxlabwiki/LotWMoveToAnotherPC>

Did you follow these instructions?
If not, how did you copy your certificates from one PC to another? If you
did not do this as described in the above instructions, then QSOs uploaded
from your new laptop may not have been accepted.

If you would like LotW to be simpler and easier to use, contact your ARRL
Director and express that sentiment.

73,

Dave, AA6YQ


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

Alan,
One of the things I noticed in your original email on this thread was
that Charlottesville was misspelled. I.E.:

Old Laptop: K9MBQ Charlottesville
New Laptop: Chatlottesville, VA
Maybe that's just a typo in the email but if not, that may be your
problem. That could not have happened if you followed step 5 in the
instructions Dave references below. If there is any difference at all in
the spelling of those station locations LoTW will consider them to be
different locations. Unlike humans who may look at that and say, "Oh,
that's the same place ", computers will take whatever you type
literally, letter for letter, coma for coma, space for space. So, if its
going to match it has to be EXACTLY the same :-)

73, Rich - W3ZJ

Dave AA6YQ wrote:
If both your "K9MBQ -K9MBQ Charlottesville" station location (on your
old
laptop) and your "K9MBQ -Charlottesville, VA" station location (on your
new
laptop) specify the same certificate file for K9MBQ, and if you properly
moved that certificate file from your old laptop to your new laptop as
described in

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

then QSOs uploaded from your new laptop with the
"K9MBQ -Charlottesville,
VA" station location should generated matches when your QSO partners
upload
their QSOs to LotW.

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/5177 - Release Date: 08/04/12
Re: Lotw Multiple Station Locations

Bob
 

Rich

You are getting me upset.

Please read the notes before you respond!!!!!!

W1SLF was only mentioned because it illustrates why Dave's change is beneficial for those of us managing multiple INDEPENDENT logs.

Let me say it again: W1SLF & KB1JZU contacts are NEVER COMBINED!!!!

Let me say it again: W1SLF & KB1JZU contacts are NEVER COMBINED!!!!

Let me say it again: If I operate under the W1SLF call in Maine it goes into the W1SLF log ONLY. It NEVER is combined with KB1JZU

Since I have a second home in Maine when I log a contact as KB1JZU in Maine it is combined with my log at my other QTH in MA using a different location code to comply with award requirements. In these instances I am NOT USING A W1SLF Call!!!!

If you still don't understand drop me an email note and lets take this converstastion off line.

Bob KB1JZU

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

OK but you cannot claim QSO's made by a club station as your own. They
belong to the Club, not you, even if you are the station trustee. That
is a violation of DXCC Rules and if you are interested also eQSL.cc
award rules. An eQSL awards manager will reject any individual award
application that combines contacts with a club station or contest group.

I have a life, abide by the rules!

73, Rich - W3ZJ

Bob wrote:
W1SLF is a legitimate club with a member list.
It has run in a number of contests Multi-op
I am the Trustee!!!! That is why I have the log.
I do operate solo in some contests so what.

Get a life

Bob
98821 - 98840 of 208010