I have two QTH's, both using my same Call Sign. One in my Home State of Pennsylvania and the other at my Beach House in Delaware. I keep two separate logs, allowing QSO's to get credit for the different states and counties. When I attempt to set up the second Account, I get an error message saving that it matches the first account and can not be set up, even though I give it a different address, etc.
How do I accomplish this?

---

KD3TB Irwin Darack

There are a couple of ways to do this. Perhaps the easiest way may be to sign "/P" or something similar while at the beach house, and set up an attached account (My Profile -> Other Accounts; form at bottom of page). Be sure you are logged in to the correct account (check at same page, My profile -> Other Accounts) before you upload each log.

---

NV2K John A Viggiano

The problem when you use /p is that not everyone saves the contact with /P and then eqsl rejects the contact.

On the other hand eqsl.cc does not allow you to use two QTH with the same callsign in the same date ranges. I use 2 qth, one during the week and the other on weekends and I haven't found a way to solve this in Eqsl.cc or maybe I'm doing something wrong, I don't know what you can suggest. LOTW has this problem completely solved, I can have several QTH and decide when I upload the logs to which QTH to associate them.

---

EA1NT GARCIA ROSALES

It would seem that creating an account/profile for each different location (using the same callsign) and then having eQSL match logs based on call signs, dates, band, etc would be a solution for the different locations/same callsign issue. It would require that eQSL index everyone's log files on more than just the callsign or just go through multiple files for each callsign.

It could become confusing with quite a few accounts/profiles for someone who regularly works POTA or SOTA but it is a fairly common issue that needs a solution.

---

KO4ZHO Jim Seaman

Are there any discussions to removing the overlapping dates restriction?

---

WX3P Jack Plum

I like eqsl.cc because I like getting QSL cards (pictures). It is special as buro does not work here and LoTW is so ugly... so I want EQSL work !

Let's take example: Greek regulations require that I use SV5/SP5NZF/P for ALL activities on Rodos (in any EU country principle is same just replace SV5 with respective are prefix). /P stays there whether I work from vacation house (kind of fixed location) or real portable going around SV5. I visited Rodos and worked (same days) :
1. From Vacation house, KM35WW, qsl card picture related to that location
2. From POTA SV-0258, grid KM35VV, qsl card picture related to POTA AND with POTA logo.

Same date range, same callsign, distinct QSL designs (only one has POTA logo), grids, descriptions

I understand that problem is that account = location (and eqsl needs to know where to "route" incomming qsl to).
The reali life is that account=callsign under which come locations.
So if structure of account would be Owner-> Callsign=Account -> Location=QSL card design and location info (grid, IOTA,....) then:
a) incoming card would go to Account (callsign+date)
b) outgoing cards would use Account(callsign)+Location to choose QSL card content

BTW it would simplify retrieving cards (if location is ignored by eqsl.cc; this could be account parameter).

Let me know if I can help by e.g. testing this fix.
73, Kuba, SP5NZF

---

SP5NZF Jakub Rusiecki
Edited by SP5NZF Jakub Rusiecki on Aug 27, 2022 at 07:08 PM

Good suggestion, similar to the way how LoTW handles certificate / call-sign / QTH's.
Hope eQSL can do improvement on this to benefit more hams and becomes more popular.
Maybe it is a database structure change which is not easy...

---

KG6YJ Jun Yang