View Revisions: Issue #3584

Summary 0003584: FT4 Contacts not logged properly in Logbook to allow confirmations from LoTW
Revision 2019-11-14 06:38 by WA9PIE
Description FT4 has been designated as a submode of MFSK by the ADIF board. This puts the FT4 mode in the ADIF3 category which HRD Logbook does not currently support. Mike C and I have discussed this and here are Mike C's recommendations.

1 - create a new field in the database called COL_SUBMODE
2 - we add SUBMODE to the ALE under the existing "Mode" field
3 - correctly save data to Logbook coming from WSJT-X logging via the "QSO Forwarding" function.
4 - update the matching criteria for LOTW so that anything downloaded with MFSK as MODE and FT4 as SUBMODE will match

Revision 2019-11-14 06:26 by WA9PIE
Description FT4 has been designated as a submode of MFSK by the ADIF board. This puts the FT4 mode in the ADIF3 category which HRD Logbook does not currently support. Mike C and I have discussed this and here are Mike C's recommendations.

1 - create a new field in the database called COL_SUBMODE
2 - Update a table that contains MODE and SUBMODES as defined by the ADIF:
       http://www.adif.org/310/ADIF_310.htm#Mode_Enumeration
3 - we add SUBMODE to the ALE limited to the values in that last reference.... ...at this point, manual logging in the database is good.
4 - correctly save data to Logbook coming from WSJT-X logging via the "QSO Forwarding" function.
5 - update the matching criteria for LOTW so that anything downloaded with MFSK as MODE and FT4 as SUBMODE will match

Revision 2019-11-13 06:34 by KB3NPH
Description FT4 has been designated as a submode of MFSK by the ADIF board. This puts the FT4 mode in the ADIF3 category which HRD Logbook does not currently support. Mike C and I have discussed this and here are Mike C's recommendations.

1 - create a new field in the database for SUBMODE
2 - Update a table that contains MODE and SUBMODES as defined by the ADIF:
       http://www.adif.org/310/ADIF_310.htm#Mode_Enumeration
3 - we add SUBMODE to the ALE limited to the values in that last reference.... ...at this point, manual logging in the database is good.
4 - Verify WSJT-X logging from the "QSO Listener" function.
5 - update the matching critera for LOTW so that anything downloaded with MFSK as MODE and FT4 as SUBMODE will match