JT65A Mode not matched

Yes, sometimes it happens... Please report any bugs here
Post Reply
w9mdb
Old Man
Posts: 109
Joined: 13 Jul 2014, 12:05

JT65A Mode not matched

Post by w9mdb » 29 Jul 2017, 04:19

I had an eQSL download that refused to match a JT65 contact in log4om to an eQSL downloaded contact of JT65A.

The ModeList_user.csv contains
JT65A;JT65A;JT65;JT65A
Which I assume it what's used for matching.
I changed the entry to JT65A and the eQSL download then matched it.
This is version 1.28.0.0
I think this is the relevant portion of the log where it appears to be looking to match JT65A instead of JT65

-29 04:09:17.3517 INFO: FileManagement: VIEW CONFIGURATION begin load for SmallQSO
2017-07-29 04:09:17.3682 INFO: FileManagement: VIEW CONFIGURATION load completed
2017-07-29 04:09:17.3792 INFO: FileManagement: VIEW CONFIGURATION begin load for SmallQSO
2017-07-29 04:09:17.3867 INFO: FileManagement: VIEW CONFIGURATION load completed
2017-07-29 04:10:49.8070 ERROR: *** SmallListView: Object reference not set to an instance of an object. ******* [Function: #=qaUnLTGXIpdMlAdV8OAqrBc9tO2TMQrH$uWOU5BRjjlY=] System.NullReferenceException: Object reference not set to an instance of an object.
at ClusterViewControl.SmallListView.#=qaUnLTGXIpdMlAdV8OAqrBc9tO2TMQrH$uWOU5BRjjlY=(Object #=q9ZqT4eNCf9UYZbD9$9N3vQ==, EventArgs #=qyuftf$nQxLJz0S8_Cj_XEQ==)
2017-07-29 04:12:17.8302 INFO: Log4OMMainWindow: *Calling UPDATE QSO FORM on QSO Call: IW2DIW Date: 20170518 Time: 220600 Band: 20m Mode: JT65A*

Post Reply