Date   

Re: Lotw Multiple Station Locations

Richard B Drake
 

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


Clublog

Richard B Drake
 

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?

73. Rich - W3ZJ


Re: Lotw Multiple Station Locations

Bob
 

Joe

Basic got it!
The blank selection used to allow the selection (separate window) during upload. Dave changed it. It no longer does. I understand why.

Thanks Bob


Double click in the "Station Location" box on the main QSL tab. It
will open QSL Configuration to the LotW tab where you can select
Station Location and Station Callsign if the Station Location has
already been created in tQSL.

73,

... Joe, W4TV


On


FT900 Problems

Richard Mogford <rchrdm@...>
 

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


Re: Lotw Multiple Station Locations

Bob
 

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

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

W1SLF is listed by the FCC as belonging to Sugarloaf/USA Amateur Radio
Club and since current FCC rules prohibit any individual from holding
two callsigns we have to assume that it is a club station. However,
there is a loophole in the rules that you may be taking advantage of.
That is, while the rules require that a Club have at least 4 members it
doesn't require that they all be licensed or operate the club station.
So, perhaps you are the only operator of the club station but boy that's
a stretch of the rules and a in my opinion a violation of the intent..

73, Rich - W3ZJ

Bob wrote:
W1SLF contact ONLY take place from that location in Maine.


Re: Lotw Multiple Station Locations

Joe Subich, W4TV
 

More interesting is that last night in trying to upload a Maine
contact and figure out the change, I somehow got the selection menu
to come up (guess its still there) but could not reproduce what I did
to make it happen.
Double click in the "Station Location" box on the main QSL tab. It
will open QSL Configuration to the LotW tab where you can select
Station Location and Station Callsign if the Station Location has
already been created in tQSL.

73,

... Joe, W4TV


On 8/5/2012 9:56 AM, Bob wrote:
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??

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?

More interesting is that last night in trying to upload a Maine
contact and figure out the change, I somehow got the selection menu
to come up (guess its still there) but could not reproduce what I did
to make it happen.

Not a big issue. I just am amazed that alot of folks (mobile,
multiple QTHs, etc) aren't doing the same thing.

As alway one of the hardest thing to modifiy is the user
interface...

All the best

Bob KB1JZU


So are two extra mouse clicks each month not worth a higher
probability
of accurate LotW uploads, especially given that a busted upload
creates a Zombie that can't be repaired?

73,

Dave, AA6YQ



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

Yahoo! Groups Links


Re: Lotw Multiple Station Locations

Richard B Drake
 

W1SLF is listed by the FCC as belonging to Sugarloaf/USA Amateur Radio Club and since current FCC rules prohibit any individual from holding two callsigns we have to assume that it is a club station. However, there is a loophole in the rules that you may be taking advantage of. That is, while the rules require that a Club have at least 4 members it doesn't require that they all be licensed or operate the club station. So, perhaps you are the only operator of the club station but boy that's a stretch of the rules and a in my opinion a violation of the intent..

73, Rich - W3ZJ

Bob wrote:

W1SLF contact ONLY take place from that location in Maine.


Re: Lotw Multiple Station Locations

Bob
 

PS

Dave I do understand efficiency however!

As you pointed out, having to make a selection for 10s of thousands of QSOs for the benefit of a few hundred in my case is a good rationalization for me to shut up.

Bob


DXKeeper 10.3.7 won't launch

Chuck, WS1L
 

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
===================


Re: Lotw Multiple Station Locations

Bob
 

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??

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?

More interesting is that last night in trying to upload a Maine contact and figure out the change, I somehow got the selection menu to come up (guess its still there) but could not reproduce what I did to make it happen.

Not a big issue. I just am amazed that alot of folks (mobile, multiple QTHs, etc) aren't doing the same thing.

As alway one of the hardest thing to modifiy is the user interface...

All the best

Bob KB1JZU

So are two extra mouse clicks each month not worth a higher probability
of accurate LotW uploads, especially given that a busted upload creates a
Zombie that can't be repaired?

73,

Dave, AA6YQ


County reporting in Pathfinder

Paul Beringer
 

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.
Thanks
Paul NG7Z


Re: Lotw Multiple Station Locations

Bob
 

Jim/Rich

You are jumping into a conversation on a different topic (ie not club calls).

FYI They are totally separate and are NOT combined.

W1SLF contact ONLY take place from that location in Maine.

KB1JZU (as allowed by DXCC rules) can log contacts anywhere in NA.
KB1JZU (as allowed by WAS, TP,etc) can take place within a distance radius(50miles) that is why I use separate location codes.

73
Bob

--- In dxlab@yahoogroups.com, "Jim N7US" <n7us@...> wrote:

Contacts made from a club station can't be used for awards for the
individual's call, can they? If that's the case, I don't understand why one
would combine club call contacts in a personal log.

73, Jim N7US



-----Original Message-----

I'm not sure I understand you correctly but if you make contacts with your
own call, KB1JZU, and add them to the your club station log, W1SLG, they
will never be matched on LoTW because the stations you worked did not work
W1SLG and will never upload a QSO confirming such a contact.

73, Rich - W3ZJ

Bob wrote:
This might be a dup Yahoo doing some strange stuff...


How often do you change LotW station locations, Bob?
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


Re: Lotw Multiple Station Locations

Jim N7US
 

Contacts made from a club station can't be used for awards for the
individual's call, can they? If that's the case, I don't understand why one
would combine club call contacts in a personal log.

73, Jim N7US

-----Original Message-----

I'm not sure I understand you correctly but if you make contacts with your
own call, KB1JZU, and add them to the your club station log, W1SLG, they
will never be matched on LoTW because the stations you worked did not work
W1SLG and will never upload a QSO confirming such a contact.

73, Rich - W3ZJ

Bob wrote:
This might be a dup Yahoo doing some strange stuff...


How often do you change LotW station locations, Bob?
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


Spotcollector /startup commands?

aart wedemeijer PA3C
 

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

Tried to find in the help, but I only can find the initial cluster command.

73
Aart PA3C


Re: Lotw Multiple Station Locations

Richard B Drake
 

I'm not sure I understand you correctly but if you make contacts with your own call, KB1JZU, and add them to the your club station log, W1SLG, they will never be matched on LoTW because the stations you worked did not work W1SLG and will never upload a QSO confirming such a contact.

73, Rich - W3ZJ

Bob wrote:

This might be a dup Yahoo doing some strange stuff...


How often do you change LotW station locations, Bob?
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



Winkey and <stop>

f6gcp
 

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!).
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?

thanks


Re: request: special callsign in SC

aart wedemeijer PA3C
 

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: request: special callsign in SC

aart wedemeijer PA3C
 

That's the most simple solution, yes.

Aart PA3C


Hidden <> 'Y' and
(
Tags like '*SpecialNeed*' or
(<BANDFILTER> and <NEEDFILTER> and <MODEFILTER> and <CONTFILTER>)
)

and then add any pertinent Special Callsigns with "SpecialNeed" in the
Tag List. Seems to work for me.

Dave, I wonder if there's a case for a built-in "SpecialNeed" tag that
gets included in the "stock" <NEEDFILTER> ?

73,

~iain / N6ML


Re: LOTW/DXKeeper Station Location match

Dave AA6YQ
 

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



If you would like LotW to be simpler and easier to use,
contact your ARRL Director and express that sentiment.
I don't know how LotW could be much more simple than it already is once one
gets past the sign-up stage - particularly when using DXKeeper.

LotW would be easier to use if
1. each uploaded QSO could simply specify a "station callsign" (which would
select the LotW certificate used to encrypt the QSO) and the details of the
operating location (entity, primary subdivision, secondary subdivision,
grid, CQ zone, ITU zone, IOTA tag) without the need for users to define,
manage, and select "LotW Station Locations"

2. users could easily correct errors in uploaded QSOs that have not yet
generated a QSL

3. a programmatic interface were provided to indicate that a QSO had been
granted DXCC credit

4. a one-click procedure were provided to renew expiring certificates

5. a one-click procedure were provided to propagate LotW from one PC to
another

73,

Dave, AA6YQ


Re: LOTW/DXKeeper Station Location match

Joe Subich, W4TV
 

If you would like LotW to be simpler and easier to use,
contact your ARRL Director and express that sentiment.
I don't know how LotW could be much more simple than it already is once
one gets past the sign-up stage - particularly when using DXKeeper.

The tQSL "Station Location" is simply an XML "paragraph" in
.../AppData/Roaming/tQSL/station_data that specifies:

<StationData name="station location name">
<Call>(certificate)</CALL>
<DXCC><ADIF NUMBER)</DXCC>
<CQZ>(CQ zone)</CQZ>
<ITUZ>(ITU Zone)</ITUZ>
<GRIDSQUARE>(grid square)</GRIDSQUARE>
<US_COUNTY>(secondary administrative division)</US_COUNTY>
<US_STATE>(primary administrative division)</US_STATE>
<IOTA>(IOTA designator)</IOTA>
</StationData>

It would appear that only the certificate and ADIF Number are required.

Most loggers already contain all of that data - where certificate is
the Station Call Sign and the rest is contained in the QTH data - for
each QSO. It would seem that a logger could automate the generation of
the location data as part of the LotW upload process, eliminate the
requirement that the user maintain a separate list of "station
locations" in tQSL, and guarantee that every QSO is uploaded with the
the logged call and QTH. That would only require that the user log
with the proper call/QTH (which most should be able to accomplish
<G>).

Yes, the logger would need to limit uploads to a single QTH/callsign
pair at any one time but the programming necessary to recursively scan
the list of QSOs to be uploaded, collect QSOs made using a common
call/QTH, create the appropriate "station location", upload matching
QSOs, then return and repeat the process for any other QTH/callsign
pairs in the outbound queue would seem to be relatively basic data
manipulation - and would certainly be no more complex than creating an
optimized DXCC submission or matching QSL confirmations and DXCC
credits.

73,

... Joe, W4TV


On 8/4/2012 9:37 PM, Dave 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



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

Yahoo! Groups Links



95621 - 95640 of 204790