Jay,I punched "reply" rather than "reply all". Here's a repeat of what I sent
to only you. Pretty much what Bruce, W9FZ and Don, NL7CO noted.
I operate as a Rover and haven't had any issues with xxxx/R in my general
logging program or LOTW. I use N1MM Plus for logging in the Rover then export
ADIF to DXKeeper. Once in DXKeeper I upload to LOTW. One of the caveats to
uploading Rover contacts to LOTW is to be sure you build a "Station Location"
in TSQL for each of the Grids you activated. I use the LOTW update feature in
DXKeeper and filter the log to QSOs from a specific Station Location/Grid then
upload those in one batch. Then repeat the process for each unique grid
activated. It's tedious but unless everyone does it you can't use LOTW for
VUCC credits.....Grid info will be missing.
After each contest I have a number of LOTW confirmations that are missing Grid
Square info. For fixed stations just review you home station location in TQSL
and be sure your Grid info is there and correct. For Rovers you have to go
through the tedium of building the Station Locations and uploading so others
will be able to use LOTW for confirmation of the new Grid you just gave them!
Building them is a onetime deal and after a while you have most already built.
I use a six digit grid for my station locations...allows determination if I was
within my 200km VUCC circle. Here's a example of a LOTW confirmation that has
grid info:Station
Call Sign W5VY/R
DXCC UNITED STATES OF AMERICA
CQ Zone 4
ITU Zone 7
Grid EM35EE
State Arkansas (AR)County Logan
Worked Station
Worked NL7CO/R
DXCC UNITED STATES OF AMERICA (291)
Grid EM04
State Oklahoma (OK)
Date/Time 2016-09-11 14:32:59
Mode SSB (PHONE)
Band 1.25M
Frequency 222.10000
QSL 2016-09-24 00:18:04
I agree that the /R is a odd suffix. I'm still a relative newbie to the VHF
world and don't know the history of /R from a FCC rules standpoint. I just
did a search and this is the only reference to the use of other indicators with
your call sign.
§97.119 Station identification (c) One or more indicators may be included with
the call sign. Each indicator must be separated from the call sign by the slant
mark (/) or by any suitable word that denotes the slant mark. If an indicator
is self-assigned, it must be included before, after, or both before and after,
the call sign. No self assigned indicator may conflict with any other indicator
specified by the FCC Rules or with any prefix assigned to another country.
I think the indicator to denote operation from the Russia Federation would
probably be more specific....R1, RA2, etc.
I hope to be out for the January Test with 6M through 23cm. Probably stay in
the central and western parts of Arkansas.
73,Pat, W5VY/REM34
From: Keith Morehouse <w9rm@calmesapartners.com>
To: "vhfcontesting@contesting.com" <VHFcontesting@contesting.com>
Sent: Thursday, January 5, 2017 3:20 PM
Subject: Re: [VHFcontesting] Logging Rovers vs the log checking robots
Thanks Joel.
The problem we're having is one some Rovers are familiar with. Stations
like me, who upload our contest logger (in my case N1MM+) .ADIF right into
LoTW, having all the Rover contacts as xxxx/R and the Rovers, many of which
do NOT get a separate LoTW certificate for the /R designation, having THEIR
LoTW entries without the /R. Results ? The contacts DO NOT appear to
match in LoTW and no confirmation happens.
I have heard through direct emails (remember VHF CONTESTING reflector
users, the default 'reply' is the original poster only, not the list) that
some (probably small) number of Rovers have applied and received a separate
LoTW certificate for xxxx/R and upload Rover logs using that certificate.
Results ? Those QSOs would match what I have in my LoTW database.
The problem may be that it's not common knowledge that one NEEDS a separate
LoTW certificate for a Rover to cover the almost universal practice (I
think...) of logging those Rover calls as xxxx/R. I never thought about it
until this week when a local Rover dropped what will be dozens of new
band/grids for me onto LoTW. . . .and NONE of them matched.
Jay W9RM
DM58 CO
Keith J Morehouse
Managing Partner
Calmesa Partners G.P.
Olathe, CO
On Thu, Jan 5, 2017 at 2:06 PM, Joel Harrison <w5zn@w5zn.org> wrote:
> An interesting question, Jay!
>
> I have no experience with any logging programs of recent years other than
> N1MM for contests and DX4Win for my every day logging. After a contest I
> do as you have noted below, export the N1MM file to an ADIF and then
> import it into my DX4Win station log. These work fine for rovers and
> "W9RM/R" is imported as a U.S. callsign with all the other info (grid,
> etc). So I have no issue here with those two logging programs. I just went
> and verified this with some rovers from the June contest.
>
> I can't speak for other logging programs but all good here with those two.
>
> 73 Joel W5ZN
>
>
>
> > I'm having a off-line discussion with a experienced Rover and a question
> > has come up...
> >
> > When I log a Rover (any Rover - as long as I know he's a Rover), it goes
> > into my log as xxxx/R. This is how I've always done it and never had a
> > problem with log checking robots at ARRL or CQ.
> >
> > But, what would the log checking bot think if I didn't include the /R and
> > then worked the same Rover in various grids (entering the proper exchange
> > for each one, of course). Would those QSOs get dinged or is the robot
> > 'smart' enough to know the call is (or could be) a Rover and is
> > permissible
> > as long as the grid mult is different.
> >
> > Funny thing is, a call like W9RM/R is not a valid USA callsign - it is
> > more
> > likely a call for the Russian Republic, and many general logging programs
> > insist on categorizing it that way.
> >
> > This question doesn't really have anything to do with submitting a
> contest
> > log. It's what happens when you try to use the contest log .ADIF for
> > something else (like LoTW...).
> >
> > Jay W9RM
> > DM58 CO
> >
> > Keith J Morehouse
> > Managing Partner
> > Calmesa Partners G.P.
> > Olathe, CO
> > _______________________________________________
> > VHFcontesting mailing list
> > VHFcontesting@contesting.com
> > http://lists.contesting.com/mailman/listinfo/vhfcontesting
> >
>
>
> www.w5zn.org
>
>
_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting
_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting
|