How To Edit Station ID for Existing QSO's?

[w7btm]

I did my 1st portable activation recently, without access to my computer.

When I got home, I manually added the 15 or so QSO's I made.
Unfortunately, I did not use a portable call sign, nor did I use a new station ID when I entered the QSO's in Log4OM.

So I figured out how to add a 2nd Station configuration, but how do I edit each of my 15 portable QSO's to link them to the new station ID?

I also created a new station location in TQSL, but I did not use a "/P" suffix with my callsign for the QSO's.

(Being new to portable operation, I must say that managing logs is a confusing process....)

Thanks!

[G4POP]

Two answers

For the 15 QSO's that need changing use the QSO manager in Log4OM to bulk edit the data

Second answer
When I go portable I take my windows tablet, just a cheap Lynx 11 inch one, with Log4OM installed

The tablet has my portable details set in the program config including locator and My Ref if I am doing SOTA, POTA etc

The tablet and my home PC both have Google drive installed which means that when I get an internet connection for my tablet thos QSO's are saved to the cloud and the home PC automatically gets synchronsed next time its turned on.

This way there are no mistakes and no manual transfers or inputs are needed

[w7btm]

Thanks..

I did not know about the bulk edit feature.

However, it does not have a way to change the station configuration in one field which is surprising....

I did create a new configuration with a different gridsquare (and my home address). But the bulk editor has TWO gridsquare fields: "Gridsquare" and "MyGridsquare"... which one to change?

It would be much more logical for Log4OM to allow me to switch a QSO to a completely different station configuration.

So I'm still not sure what I need to change with the bulk editor before I upload these QSO's?

[G4POP]

Grid Square is the other stations grid square

MyGrid square is your stations grid square

You can have multiple configuratios - See user guide and program confuration/User configuration menu

[LB4MI]

Hi,
just a general advice from a mainly /P operator, SOTA/POTA:

there are very good options for logging portable, and then e-mail yourself the ADIF file after you are back in shack.
Then you can just:
1) Switch to correct profile in Log4OM, meaning the one you use for portable ops
2) Import the ADIF directly in to Log4OM.
Your (if relevant) SOTA/POTA reference will be transferred correctly. Any "Part to Park" or "Summit to summit" will be correct. Your station callsign will be correct. Just good stuff. The same ADIF also ready to upload to SOTA or POTA directly without any re-work.

The Portable Logger, https://ham2k.com/apps/polo/ , is really good for all portable ops. Fantastic app, I follow the developer versions which easily can be joined.
Another good alternative is HAMRS: https://hamrs.app/ , however I am not sure how often it is updated and if it contains the new POTA references after a change in the park codes recently. I used this before i found PoLo.

Logging on the cell phone, and e-mailing ADIF was a "game changer" to my portable ops. Before, I used more time with manual/paper logs -> digital log then doing the activation.

Good luck,
Helge.

[w7btm]

Thanks Helge,

I just created a new database in Log4OM, and imported the QSO's from my portable activation (only 15). I then used QSO manager to change the "MyGridsquare" field to the gridsquare of the portable location I was at (Timberline lodge on Mt. Hood!). I did not change ANYTHING else.

A few specific questions:

1. Will this be enough to satisfy LOTW and avoid confusing the confirmed stations, or should I change something else in each QSO?
2. Can I now upload the new database to LOTW using standard TSQL procedures (I already created a new location in TSQL)?
3. Is it really necessary to maintain separate QTH's in TSQL and setting the correct gridsquare in each QSO? Isn't that redundant?
4. How can I use the "worked before" feature if my QSO's are spread among multiple databases?

I guess I just want an "Easy Button"

Thanks.

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

Hi,
just a general advice from a mainly /P operator, SOTA/POTA:

there are very good options for logging portable, and then e-mail yourself the ADIF file after you are back in shack.
Then you can just:
1) Switch to correct profile in Log4OM, meaning the one you use for portable ops
2) Import the ADIF directly in to Log4OM.
Your (if relevant) SOTA/POTA reference will be transferred correctly. Any "Part to Park" or "Summit to summit" will be correct. Your station callsign will be correct. Just good stuff. The same ADIF also ready to upload to SOTA or POTA directly without any re-work.

The Portable Logger, https://ham2k.com/apps/polo/ , is really good for all portable ops. Fantastic app, I follow the developer versions which easily can be joined.
Another good alternative is HAMRS: https://hamrs.app/ , however I am not sure how often it is updated and if it contains the new POTA references after a change in the park codes recently. I used this before i found PoLo.

Logging on the cell phone, and e-mailing ADIF was a "game changer" to my portable ops. Before, I used more time with manual/paper logs -> digital log then doing the activation.

Good luck,
Helge.

[LB4MI]

Hi,

1. Will this be enough to satisfy LOTW and avoid confusing the confirmed stations, or should I change something else in each QSO?

The gridsquare of your portable operation is logged by the apps Polo or HamRS. This is either done by GPS on your location when logging, or by locator of e.g. the summit/park you have added as your reference. The apps might do this diffrently, but I never think about anything about grid location anymore.

2. Can I now upload the new database to LOTW using standard TSQL procedures (I already created a new location in TSQL)?

In TQSL you only need certificates for your callsigns. The gridsquare locator is sent to TQSL by Log4OM. So you do not need to change locator in TQSL again. (I did this for every /P operations earlier before uploading to LOTW...I don't miss that..).
I don't think you have to do anything special in Log4OM for this, but in Configuration -> User Configuration ->External Services -> LOTW, I have checked the "Send My Station updated data to LOTW" ticked ON. The next two is ticked OFF. The last one (Automatic upload on application close) is ticked ON.

3. Is it really necessary to maintain separate QTH's in TSQL and setting the correct gridsquare in each QSO? Isn't that redundant?

No. For my /P certificate I have entered the grid locator of my home QTH. However it is overwritten by Log4OM uploads so the locator there does not seem to matter. However if you upload ADIF using TQSL this is required I believe, but I only use Log4OM.

4. How can I use the "worked before" feature if my QSO's are spread among multiple databases?

If you use separate database, the "Worked before" does not work. I have actually addressed this before in a question on this forum. For the "Worked before" to work, you have to just add callsign to existing database. I use same database for home call, and portable call. You just add the /P callsign as a new "User configuration" in "Configuration"->"User configuration". Then you have one profile for home call, and one profile for /P call. And then you can update all the "External services" for upload to LOTW (or QRZ, Clublog, EQSL where I also have created /P profiles and I upload automatically to from Log4OM).

Hope this helps,
Best regards,
Helge.