On 25/06/2020 13:55, ve3ki wrote:
Strictly speaking this is about N1MM+, not WSJT-X, but we know that a lot of users of the N1MM+/WSJT-X combination monitor this group. If you're not going to operate FT8 or FT4 with the N1MM+/WSJT-X combination on Field Day, you can ignore the rest of this message. If you are going to operate FT8 or FT4 from the N1MM+/WSJT-X combination on Field Day, first make sure WSJT-X is version 2.2.2 (this version includes the new PE section). This morning the N1MM Development Team issued Update v1.0.8501. This version correctly logs the exchange from WSJT-X into N1MM+. The ARRL does not require stations to submit their Field Day logs, but if you are meticulous about accurate logging, you will want to update N1MM+ to this version. If you are not prompted to update to this version when you next launch N1MM+, you can manually perform an update by downloading the file from the N1MM+ web site at >Downloads >Program Files >Latest Update (shortcut: <https://n1mmwp.hamdocs.com/mmfiles/n1mm-logger-update-1-0-8501-jun-25-2020/>), and then executing the update program you just downloaded to update your copy of N1MM+.
73,
Rich VE3KI for the N1MM+ Development Team

Hi Rich and all,

further to this important information for those intending to use WSJT-X modes during Field Day, there is a known defect that has crept into WSJT-X v2.2.2 (sorry, that's my fault) that will impact new users and those setting up with N1MM Logger+ integration for the first time. WSJT-X v2.2.2 writes an invalid header to its own ADIF log file and will fail to read back that ADIF log file when it is restarted. Fortunately a simple one-off text edit of the ADIF file header will fix the issue. Look for the text <eh> on the first line, and change it to <eoh>.

A second note about the new RAC PE section for operators on Prince Edward Island during Field Day, the change to WSJT-X to support this in WSJT-X v2.2.2 does not just affect users using PE, it affects *all* stations trying to work them as well. The messages from PE stations will not be decoded unless you are using v2.2.2.

73
Bill
G4WJS.



_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to