Aha, Could it be that I used ONS in exchange instead of just ON? I
figured as we were mocking and ARRL contest I should use my proper
section, but not so in RU.
Jeff VE3CV

On 27 Sep 2018 18:07, Joe Taylor
wrote:
> Dave --
> 
> Please use the original (or at least an
informative) subject line
> rather than allowing your email client to
insert something like
> "Re: [wsjt-devel] wsjt-devel Digest, Vol 55,
Issue 106".
> 
> As best I can infer from information you've provided,
you must not
> have had a valid entry in the "Exch" field. Presumably
this should
> have been "ON" (for Ontario) -- nothing more, nothing
less. Are you
> sure this was true? Have you repeated the test to be
extra sure?
> 
> -- 73, Joe, K1JT
> 
> On 9/27/2018 4:26 PM, Jeff Wilson
VE3CV wrote:
>> Hi Dave and Joe
>> Yes, I had the truncated message
thing going on and could not figure it out. I spent the afternoon before
the constest using V2.0 in the normal FT8 mode and was busy DXing on 40
and 20 with no problem. During the contests I made 1 QSO (K5CM) with
difficulty and then nothing as I noticed my messages were severely
truncated.
>> All was set up with correct checks on the Advanced Tab and
the Red Notice on the main window. But I still could only transmit 13
characters. If a 6 character call, they only got KX1XXX_VE3CV_ (=13)
when I called them...no report at all.
>> If a 5 letter call they got
KX1XX_ VE3CV_ 5_ (=13)
>> I tried all permutations of checks on the
Advanced Tab. With the Exchange left blank I was able to send 23 or 25
characters when I used the Free Message entry window. Eg.,
KX1XXX_VE3CV_539_ONS_0001 ...or something like that.
>> Loved the
program and the contest, and glad (sad) to see I wasn't the only only
suffering the truncated message error.
>> Hope this helps
>> 73
>> Jeff
VE3CV
>> On 27 Sep 2018 10:06, Dave wrote:
>>
>>> First off, Joe and
team thank you for this great software. Also to Don for confirming what
I saw here. I can only assume that I have something set incorrectly but
it's actually rather simple to go from normal mode to RTTY RU
mode.
>>>
>>>
>>> From: "Don Hill AA5AU" <[email protected]
>>>
<mailto:[email protected]>>
>>> To: "'WSJT software development'"
>>>
<[email protected]
>>>
<mailto:[email protected]>>
>>>
>>> 3. I had two stations
(W3DLQ and VE3CV) call me where it appears their
>>> message wasn't
fully sent (see screenshot below for W3DLQ
>>> example). W3DLQ
>>>
answered me with "AA5AU W3DLQ 5" and VE3CV did the same thing
>>> "AA5AU
VE3CV
>>> 5". I'm guessing they didn't have something set up correctly
on
>>> their end?
>>>
>>>
>>> I'm using V2.0 rc-2. I have used this
version to make contacts with no contest selected so I know it is
working properly. I cloned my normal operating configuration and renamed
the clone to RTTY RU. When setting up for the ARRL RTTY Roundup I have
that ticked and have entered MDC in the Exch: box. I have "FT8 message
types" *Always generate* and *Decode only 77-bit messages* ticked.
Everything else is the same except I cleared all default frequencies and
added only 7.078 and 14.078.
>>>
>>> As soon as I click on OK the
messages are converted to RTTY RU mode. e.g. AA5AU W3DLQ 539 MDC and
Tx2.0 RTTY is highlighted in a red box on the main screen. This also
works when I enter a callsign in the DX Call box and click "Generate Std
Msgs" When I clicked on a CQ message the messages are changed to that
caller.
>>>
>>> When I clicked on a CQ in the Band Activity window, the
messages changed, and TX started. However, in the Rx Frequency window my
messages are truncated to *AA5AU W3DLQ 5.* This also shows in the last
message sent TX box.
>>>
>>> This occurs if either I send a CQ and the
program answers and sends the response message, I click on a CQ message
or I click on a message sent to me. In the exchange with AA5AU I clicked
on his call to me.
>>>
>>> I also clicked on a call *CQ RU K9OM EN65.*
My response TX to him was*K9OM W3DLQ 55.*
>>> **
>>> In summary, any TX
I make is truncated. I think I'm set up correctly or there is something
strange in my set up which is Windows 10 with a FLEX-6500. I was running
two slices last evening, one for 20M and the other for 40M. Nothing on
20M but many on 40M were decoded.
>>>
>>> Looked like fun but after I
saw what was happening when I transmitted I stopped participating. I
didn't want to get flamed for not reading the FTM, not following Joe's
directions for setting up the program or other smarta$$ comments.
Comments like Don's are appreciated. He made no accusations and merely
stated the facts.
>>> Dave W3DLQ
>>>
>>
>>
>>
>>
_______________________________________________
>> 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

Reply via email to