eQSL.cc Forum
Help!  eQSL.cc Home  Forums Home  Search  Login 
»Forums Index »General Interest Support »Support - English speaking »Handling /P callsigns becoming a problem
Author Topic: Handling /P callsigns becoming a problem (6 messages, Page 1 of 1)

G0NUP Kevin
Posts: 3
Joined: Nov 10, 2000



Posted: Jul 13, 2010 04:46 PM          Msg. 1 of 6
Hi
I am a SOTA chaser (Summits On The Air). as such I keep a log, using Logger32 which is quite flexible.
I upload on a fairly regular basis into eQSL
I have a problem however.
SOTA activators (not all) when they are activating a summit use their call with a /p.
However when they are entering their data into the eQSL database they are omitting the /P for ease of entry....? (some do it correctly)
This in turn has a major problem on my INBOX, it show the normal stations worked, but almost all the SOTA callsigns who do not use the /P have the big red X and the green tick.
This means a whole load of additional work for me, and additional load on the database.

Now surely if a station is LLFLLL he is the same operator as LLFLLL/P only working from a different QTH. (LLFLLL letter Letter Figurel, letter,letter letter example only, others do exist hi hi)

All his/her details will be the same other than QTH.

What thoughts are there on this subject?
Are there any moves afoot to sort it out?

Regards
73
Kevin G0NUP

G0NUP Kevin

W5DET Doug Thompson
Posts: 76
Joined: Nov 16, 2009



Posted: Jul 14, 2010 03:57 AM          Msg. 2 of 6
Hi Kevin,
I certainly understand the problem, but it isn't of eQSL's making and I can't imagine what they would, could, or should do to change it. The problem is most properly addressed by the SOTA program by including instructions to activators in the ARM (Association Reference Manual for those unfamiliar with SOTA) about proper logging methods for eQSL, etc. For my part, I will draft such instructions for the USA (W5) ARM and submit them for inclusion in the next revision. Don't look for the revision any time really soon. We just got the Original submitted and approved on the first of this month. Mike, KD9SC, the W5 Association Manager, put in 100s of hours over 6 months drafting that release and is taking a breather.

73, Doug, W5DET
New Mexico Region Manager
Summits On The Air

What?!? You're still wasting time and money sending QSL cards via Snail Mail? Whatever for? Go Unpostal!

G0NUP Kevin
Posts: 3
Joined: Nov 10, 2000



Posted: Jul 15, 2010 06:57 PM          Msg. 3 of 6
Hi Doug,
thanks for the reply.
Well I think the point I'm making is that most logging programs nowadays will allow you to 'change operator' which in turn will allow you to output a list of contacts based on the operator. Which I do for special events.
However, I can't understand why eQSL does not treat G0NUP the same as G0NUP/P. With ref to SOTA, adding the location that was used in the 'comments' field.
This would mean that all G0NUP , G0NUP/P , G0NUP/M would all be in the log, after all the operator is the same and all his details (personal) are the same. The difference would be highlighted in the comments field.
Along the same lines when I operate as 5B4/G0NUP (5B/G0NUP) my log is now different as I'm 5B so this justifies a separate log database as it would if I was GW0NUP/P whilst in Wales.
This would also reduce the number of individual databases on the eQSL system.,
As a programmer, I can't see the difficulty in filtering the /P or /M off either side of a QSO and keeping a single logbook.??

Just thoughts for open discussion.

73 de Kevin

G0NUP Kevin

VE3OIJ P. Darin Cowan
Posts: 186
Joined: Jul 9, 2006


Posted: Jul 16, 2010 06:33 PM          Msg. 4 of 6
If the operator is putting it all in the same log, why is he bothering with /P or /M. By adding the /P or /M it is effectively a different callsign, and eQSL treats it as such.

It's mentioned somewhere on eQSL that QSOs on a given callsign are supposed to be within some smallish distance (25 km?), so if you're /P on some summit far from your home QTH, you are supposed to be entering it as a second account anyway. How many people actually bother is, perhaps, another discussion. I'm just saying...

Personally, I treat /P and /M as separate callsigns in my log, and in my uploads here. Always have, even before I joined.

VE3OIJ P. Darin Cowan

W5DET Doug Thompson
Posts: 76
Joined: Nov 16, 2009



Posted: Jul 18, 2010 04:55 AM          Msg. 5 of 6
Actually, the straightforward solution is for the Activators to create an attached account for each sortie. That is what I will be doing.

Because "Summits that are accessible by road can still be included in the programme, although operation from vehicles is not permitted (SOTA General Rules, 3.5.4)" there should never be an occurence of /M. If someone is properly signing /M, the activation is not valid and will not count for awards.

73, Doug, W5DET

What?!? You're still wasting time and money sending QSL cards via Snail Mail? Whatever for? Go Unpostal!

VE3OIJ P. Darin Cowan
Posts: 186
Joined: Jul 9, 2006


Posted: Aug 2, 2010 08:45 AM          Msg. 6 of 6
Heh.. that's true. You have to hoof it to a SOTA location, no vehicles allowed. I'd forgotten about that.

VE3OIJ P. Darin Cowan