How do I set up Logic 9 to log a special event station I operate for a weekend and upload to LOTW keeping it all separate from my normal W7GTF log?

Tnx,Ron/W7gtf

Dennis;

I try the prescribed method. However when trying to modify the shortcut, this error message appears: http://sdrv.ms/Kr60O4

Pse advise.

73
Chris / LA8OM

Dennis,

Back to the question of operating as a special event station(W1AW/7, for example) and keeping it separate. I notice in Setup for a Contest, there is the option to use a different call sign. Could I set up my operating as a contest and separate it that way and be able to upload to LOTW at the end of my operating time?

Thanks and 73,
Ron

I have a similar issue. Over the years, I have used ex-calls and also now use my current call. However, I have recently started using JT65 which does not support my use of /6 on my 5-Area call. Consequently, I have many LoTW QSLs which are for NT5A, even though they are for my CA QTH. LoTW confirms the contact, but Logic adds the (duplicate) contact with NT5A as operator instead of NT5A/6.

I have always used the Operator field as my record of where the contact was made from, and it has worked well up until this time. Now I am accumulating duplicate records in my log and if/when I work from Texas again, my awards tracking will be completely messed up as I will no longer be able to filter by the Operator field.

Is there a better way to keep track of one's transmitting location? It seems like filtering by Grid Square would be a good option ... but that would mean (for me) adding my grid square to some 6000 existent records - some for CA, some for TX and some for UT. I cannot be the first person to run into this. Is there a better way???

Thank you for the help!

73 de NT5A Bob

Yeah, this is a bit complicated and confusing. The situation has evolved and I think involves a basic difference in philosophy between LoTW and the awards tracking procedure in Logic.

1. My LoTW account is set up geographically. Two ex-calls and my current call are identified as San Dimas CA. I have two TSQ keys for this location, NT5A and NT5A/6. This was done on the advice of the folks at LoTW because "not all hams are fastidious about including the /6". As time evolved, I started dropping the /6 on contests ... and now my JT65 contacts do not support "suffixes".

2. I have two other LoTW locations: Hill County TX and Park City UT. None of the records for Hill County used a suffix (of course) and the Park City records were all identified as NT5A/7.

The key thing here, is that LoTW only really cares about location, and does not seem to care about the operator, so long as the records are "signed" by the identifying "key" when they are uploaded. They "encourage" uploading the contacts twice if there is any concern that the matching records might be missing the suffix - this to improve the probability of a confirmed contact.

For a while, I thought that all was well, and then I noticed that I was downloading contacts which were "not in my log". I looked at them and recognized that they were valid contacts, so I pushed the button to add them to my log - and scratched my head, wondering why this was happening. Later, I noticed that these duplicate entries were listed with a different operator - in this case, NT5A instead of NT5A/6.

I figured that this was not really a problem ... until I started running reports for my 5BWAS progress and found that (of course) things were messed up on the reports. Contacts that I knew I had were not showing up on the NT5A/6 reports. When I discovered that, I manually went through and "fulfilled" the LoTW QSL on the NT5A/6 log pages that had matching confirmed NT5A pages. Of course there is no apparent way to exclude these "duplicate" records when I run a report on my TX contacts. Do you see the mess I am in?

If the reports only track the "operator" field, I see no way to fix my problem. I would imagine that sorting the reports by location instead of operator would solve my problem. But of course, I have no idea how to do that.

Any ideas? Thank you!