QSO Not Saved

[WB5SKM]

Good morning. I have N1MM broadcast QSO's to Log4OM during contests. In state QSO parties, operators often indicate roaming in a different county by adding a /County identifier after their callsign. I need to delete the county designators when uploading. I pull up the QSO as seen below.

Screenshot 2024-10-16 060401.jpg (70.17 KiB) Viewed 951 times

I am using backspace to remove the county designator and the slash and I cannot save it. I get the error

QSO Not saved check Band/Mode/Callsign/Date

Any ideas why I can't save the modified QSO?

Screenshot 2024-10-16 060950.jpg (75.19 KiB) Viewed 951 times

Thanks,

Ken
WB5SKM

[KI5IO]

Ken,

Just looking at the QSO you tried to change that has the red warning in place ... there are a number of things amiss

1 - Incorrect PFX
2 - Incorrect grid ID
3 - Incorrect country

Looking at your 'sent' & 'receive' values it appears that this was an FTxx contact??? Was the data input to Log4OM from a combination of WSJTx, JTAlert, Gridtracker, etc.??

I don't think that KC2EGL was running in the PA QP from Japan. PM96 is near Takasaki, Japan.

OMs who add all the identifiers for county location, etc.. are great for knowing such when it comes to scoring for the respective QSO Party ... but such identifiers wreak havoc when it comes to (for example) an upload to LOTW ... Reason being is that such identifiers are not approved for use by the IDIF standards. Ergo some issues can happen there.

Maybe the FTxx APP massaged some of the values when it was ported into Log4OM V2??

At the least ... food for thought. Try correcting the 3 items I noted above and see if that works for that QSO with KC2EGL.

[N6VH]

Ken,

In N1MM+, don't include the county identifier in the Callsign field. I never do. Just enter it in the County field. Then only the actual call will be sent to Log4OM. I doubt if any QSO Party log checkers will ding you for not including the modifier in the callsign field.

73,

Jim N6VH