Hi Joe, 

Sorry, this is for JT65 and JT9. (I do use FT8 as well, but only about half the 
time. I’m one of those odd ones who kind of likes the pace of those earlier 
modes, not to mention the performance of JT9.) I don’t modify the signoff 
message for FT8.  (Good point on the CW ID on FT8, btw..)

In all of the cases where I customize the signoff message, I always end it with 
73. In the past, all of the following examples would have resulted in CW ID, 
auto-logging, and disabling transmit: 
RR FRED TU 73
TU BOB GE73
5W LOTW 73
<call> <call> RR73

Now the only one that I’ve seen work at all for me is the default “<call> 
<call> 73”. 

73,
Ivan, AI0IA

> On Feb 9, 2018, at 8:02 AM, Joe Taylor <j...@princeton.edu> wrote:
> 
> Hi Ivan,
> 
> On 2/8/2018 10:12 PM, I&N Yanasak AI0IA wrote:
>> With the latest GA version of WSJT-X (1.8.0), running Windows 10, I am 
>> running into the problem where the auto-logging and CW ID features are 
>> highly unreliable, at least using standard messages.
>> As far as I can tell, the only time that the 73 is detected is
>> 1) It must be at the end of the TX 5 line, and
>> 2) That line must not be modified from default (<call> <call> 73)
>> All other times, auto-logging, CW ID (and the transmit disable) do not 
>> occur. 
> 
> You don't mention what mode you are talking about.
> 
> Using CW ID is a bad idea in FT8 mode, and there's no need for you to do so.  
> Think about it: sending most callsigns takes around 5 seconds with 25 WPM CW. 
>  This is far longer than the "dead time" at the end of an FT8 transmission.
> 
> If you modify the default "73" message arbitrarily, you're on your own for 
> remembering to log the QSO.  The program is somewhat fussy about what it 
> takes to be a sure sign-off message.  For example, callsigns may include 73, 
> as in V73AT, E73FDE, and others that I find in my log.
> 
>       -- 73, Joe, K1JT
> 
> ------------------------------------------------------------------------------
> 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

Reply via email to