I am also having problems with logging. FT8 is not recognized (yet). I listed it as 'SSB' and put "Mode=FT8" in the remarks, but that is just a stop gap measure. Log4OM initially accepted but then rejected FT8, and I haven't found a way to make that acceptable to Log4OM. I have to say though that I am very pleased with the auto-sequencing.
-----Original Message----- From: Laurie, VK3AMA [mailto:_vk3a...@vkdxer.net] Sent: Thursday, June 29, 2017 5:36 PM To: WSJT software development <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] FT8: Potential new mode for fast QSOs On 30/06/2017 7:41 AM, Dan Malcolm wrote: > I also notice that there is a > tilde between "Freq" and "Message" in the "Band Activity" window. Is > that an FT8 encoding indicator or a place holder? The "~" mode character will be a problem. It is the character chosen by JTDX for the T10 mode and would explain an earlier message that indicated that a FT8 spot on HamSpots appeared as T10 (likely came from JTAlert which spots "~" decodes as T10). de Laurie VK3AMA ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
