Bill, According to Don Agro, MLDX author, he uses the N1MMLogger+ UDP feed.
You said "only the direct UDP messages sent to N1MM Logger+ and the WSJT-X ADIF log have the contest exchange information.” If MLDX uses the N1MM feed, shouldn’t it receive the context exchange info? Or am I missing something? David, WA1OUI On Dec 2, 2018, at 7:12 AM, Bill Somerville <[email protected]> wrote: On 02/12/2018 04:22, David Kaplan via wsjt-devel wrote: > I made a few QSOs with RC5 feeding MacLoggerDX the N1MM+ data. The main QSO > information came through fine, but there was no exchange data for my log.. > > An exchange of 539 NJ from K1JT is apparently built from <rst_rcvd:3>539 and > <STATE:2>NJ, > and 549 0044 for CE1OEB from <rst_rcvd:3>549 and <SRX:4>0044. > > It doesn’t seem as if you send a STX_STRING or SRX_STRING in the N1MM+ data > which MacLoggerDX would need to populate my log.. > > I can send the full ADIF if you want > > Am I interpreting this correctly? > > Thanks. > > David, WA1OUI Hi David, only the direct UDP messages sent to N1MM Logger+ and the WSJT-X ADIF log have the contest exchange information. No guarantees were offered for other routes like the WSJT-X UDP protocol that programs like JTAlert use. We hope to have the extra contest exchange information added to the WSJT-X UDP protocol for the WSJT-X v2.0.0 GA release but to make use of it the cooperating applications will also have to extract the new fields and allocate them to their logs and data feeds. 73 Bill G4WJS. _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
