You need to enter a QSO record for each grid. This is easy to do -- just right-click the + button to duplicate the current record.

Tnx/73,

DH WH4AZY

This really complicates things -- I wish they hadn't done that. You could theoretically be in two DXCC countries at the same time. Are they going to handle that in one QSO too?

Can you find any documentation on this? I found this, which just mentions a grid square, which apparently comes from the station location.
https://lotw.arrl.org/lo.../UpdatingConfirmations/
And the station location setup only has a place for one gridsquare.

I guess a workaround would be to create a second (third? 4th?) grid square in LOGic as a user-defined field, using whatever field name the ARRL uses. But again, I can't find any documentation on this.

Let me know if you find out anything.

73,

DH

Peter/Dennis,

TQSL allows for up to four grids to be entered in a Station Location by separating them with a comma and a space, i.e., EN90, EN91, EN92, EN93. The multi-grid operator needs to create a Station Location with those multiple grids before uploading qso's to LoTW.

Only a single qso is logged to get credit for all four grids. The multi-grid operator uploads his logged qso (remember his Station Location defines the four grids) and the other operator uploads his logged qso no different than any other. LoTW looks at both qso's and if a match credits the operator with having worked the four grids as defined in the multi-grid operators Station Location.

This applies ONLY to VHF and up awards!!

So there you have it......chaos! Hi Hi....

73 de Brad, N8GLS

Dennis,

Can the "Grid" field be modified in a future update to accept 4 grids separated by commas? This would solve the issue for award tracking. Thanks for all the commenters that jumped in and help explain the issue.

73,
Frank
K6FW

Dennis,

Ha....don't forget it also depends on the wind direction too....hihi.

Ok, well, I should have tackled the ARRL rep and asked 20 more questions. His exact words were no ADIF fields are used in this process.

Having said that, I looked at the ADIF link you provided and see two fields explicitly for this purpose, MY_VUCC_GRIDS, and VUCC_GRIDS from Section III.C.I-ADIF defined fields.

MY_VUCC_GRIDS: Two or four adjacent Maidenhead grid locators, each four characters long, representing the logging station's grid squares that the contacted station may claim for the ARRL VUCC award program. Entered like EN91, EN90, EN92, EN93. So N8GLS as the logging station operating from a grid corner enters those grids in that field. BUT...I still must submit a Station Location identifying those grids before uploading to LoTW for LoTW to credit the contacted stations qso for all four grids as its only read from the grid square field in that file, not from ADIF (per ARRL).

VUCC_GRIDS: Two or four adjacent Maidenhead grid locators, each four characters long, representing the contacted station's grid squares credited to the QSO for the ARRL VUCC award program. Entered same as above. So N8GLS logging a qso with a station on a grid corner enters here the contacted stations multiple grids. In this instance, the burden is on the contacted station to submit a Station Location identifying those grids in order for N8GLS to get LoTW credit for them.

Maybe a call to them is in order. Thinking out loud, If I'm a rover jumping around to multiple grid corners, I'm gonna have to split up the log when I upload to LoTW cause each grid corner is gonna be a different Station Location....If I work from 4 different grid corners, that's 4 Station Locations. Does that make sense?

Regards,

Brad, N8GLS

Yes,

Agree with K6FW that LOGic doesn't have to know what grids are being operated from. The "capture" of that data in an ADIF format would be the only reason for me to want to do that, thus keeping it integrated with the log.

73 de,

Brad, N8GLS

I got it to handle multiple grid squares, but now CQ Field is broken. Continuing to work on it.

73,

Dennis

Ok, here it is! There is some other stuff in progress, so consider this a beta release. Also, the under-hood changes to LOGic were quite significant. I tested it, but would feel better if it had more usage before I release it officially.

This change is not specific to grid squares. It is now theoretically possible to set LOGic up to track multiple values for any award. States or even DXCC countries for example.

To track multiple grid squares with this release, some setup will be required. Perform the following steps:

*Make a backup. Copy your whole LOGic folder.

*Install this update.

*Go to tools/misc utilities/change size of log fields. Make the GRID field bigger. To store four 4-character grids, you will need 19 characters. If you want to store four 6-character grid squares, you will need 27 characters. I don't know that anyone would want to do that, but if you do....

*Go to Tools/Setup/Log Fields and navigate to GRID. On the Field Info page, look for the new DELIMITER FOR MULTIPLE AWARD VALUES. Enter a comma. This field will be moving to the Awards tab.

*Navigate to the CQFIELD field. Change CALCULATED FIELD EXPRESSION to

LEFTDELIM(GRID, 2, ",")

*Navigate to the FFMA field. Change CALCULATED FIELD EXPRESSION to

LEFTDELIM(GRID, 4, ",")


That should do it!

Tnx & 73,

Dennis WN4AZY

Thanks for the report. I forgot that the grid squares could affect contest scoring ... :-( Back to the drawing board.

73,

Dennis

I love the ability to be able to enter multiple grid squares in the grid field. Thank you very much.

One glitch is being able to find a record using the second, third or fourth grid entered into the grid field.

All grids entered show in the progress chart. If the grid in the progress chart is the first one in the field then when you click on the box the corresponding record is displayed. If the grid in the progress chart is the second, third or fourth grid entered into the field then when you click on the progress chart the corresponding record is not retrieved. If you use the search filter and look for the second, third or fourth grid entered into the field no records are returned.

This makes it impossible to find the QSO corresponding to the grid field unless it is the first grid entered into the field.

Hope the fix is easy.

Thank you,

Frank
K6FW