I suspect that the root cause is that he can't see any reports on psk reporter. This is probably for two reasons -- there is no locator in the CQ message (and so no psk report) and for other systems which do report this type of message, there is no locator in psk reporter database and so it cannot be displayed.
Philip On Tue, Jul 9, 2019 at 11:36 AM Black Michael via wsjt-devel < [email protected]> wrote: > Oops....so no disconnect...so now we have to find out what problem he's > having specifically. > > C:\WSJT\wsjtxrc7\bin>ft8code "CQ 3DA0VV EM49" > Message Decoded > Err i3.n3 > > ---------------------------------------------------------------------------------------------------- > 1. CQ 3DA0VV EM49 CQ 3DA0VV > * 4. Nonstandard calls > > de Mike W9MDB > > > > > On Tuesday, July 9, 2019, 10:22:10 AM CDT, Bill Somerville < > [email protected]> wrote: > > > On 09/07/2019 16:13, Black Michael via wsjt-devel wrote: > > There does seem to be a disconnect between the GUI and the coding software. > This is with RC7. > > [image: Inline image] > > But looks good here > C:\WSJT\wsjtxrc7\bin>jt9code "CQ 3DA0VV EM49" > Message Decoded Err? Type Expected > > ---------------------------------------------------------------------------- > 1. CQ 3DA0VV EM49 CQ 3DA0VV EM49 1:Std Msg EXACT > > de Mike W9MDB > > Mike, > > you appear to be confusing JT9 mode which uses a 75-bit protocol and has > special treatment for non-standard call and FT8 which has the new 77-bit > payload which has more general support for non-standard calls. > > 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 >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
