[RTTY] Tinyfsk, 2Tone and USOS

[V. Sidarau]

Andy,

Are you sure, it is all about USOS? I for one cannot recall the phenomenon
in question before. Looking back, we RTTYers used to use WF1B, RITTY, MMTTY,
MixW for years. The USOS issue was around for years, all horses in the
neighbourhood badly suffered from discussions about that. We all used to
know how to "look North-West", let alone the N1MM extra decoding tools were
also around. But now there is something new.

I don't know what to do and where to look at when totally weird characters
pop up.

Another guy has just sent me a part of his MixW decoding log. In a string of
QSOs a BIG contester sends like, 599 05 .- .- (that's <dit><dot>) instead of
the state of MA. So, the guy asks me, is it yet another tool for catching
cheaters, like these characters are non-decodable for sure and people would
have to check a callbook for a missing state?  

Once again, I don't recall problems like that before, albeit I might be
wrong. I can only correlate it with occurrence of new software, i.e. 2Tone
and Gritty. Or is it a hardware (newer radios) issue? 

OK I am using MMTTY as a single decoder. If 2Tone manages to read the weird
code, that's great but it would be good to know the culprit and what should
I do if I want to stay with MMTTY alone.

In any case something has to be done in this respect, I don't know what
particularly.

Thanks for reading.

73,

Vlad VE3IAE

-- 
  


-----Original Message-----
From: RTTY [mailto:rtty-bounces at contesting.com] On Behalf Of Andrew Flowers
Sent: Monday, September 28, 2015 9:31 PM
To: Mark n2qt; reflector RTTY
Subject: Re: [RTTY] Tinyfsk, 2Tone and USOS


> On Sep 28, 2015, at 7:51 PM, Mark n2qt <n2qt.va at gmail.com> wrote:
> 
> But when this happened to me, I'd hover the cursor over the offending 
> text and it didn't resolve to the correct letters, so I think it's 
> something more than just a LTR/FIG shift issue.

Mark,

What you are seeing is N1MM's incomplete implementation of the FIGS-to-LTRS
conversion. It's been this way since the dawn of time.

The top row (QWERTYUIOP) converts to the FIGS equivalent and vice versa, but
none of the other FIGS punctuation is converted in the FIGS-to-LTRS
direction...it works fine for serial numbers, but it's pretty much useless
for non-numeric stuff like names and states...unless you are in WI, WY, RI,
PR, PE (even PEI), UT, YU, PQ (but not QC).

I don't know what MMTTY converts to text for BEL, WRU, and/or the U.S. TTY
differences from ITA-2, if anything.  Hopefully it (and any other
demodulator that integrates with N1MM) spits out something unique otherwise
the folks in DE, DC, NC, SC, CA, CO, CT, and SD (twice!) will be at
disadvantage when things get noisy.  Now, those of you who like picking
strategic names for NAQP will have to play anagrams....but I secretly wonder
if NO3M and N5KO always knew this.

Anyway, if you feel strongly about this you might submit a bug/enhancement
request... I'm surprised nobody has done this in all these years.

This might also be good opportunity for contest software to force USOS on
receive (which is possible through the DLL interface, I understand) since
MMTTY apparently doesn't do it by default and even many experienced RTTY ops
either don't know to enable it, or end up disabling it somehow.  Meanwhile,
someone can compile MMTTY 1.69 with the USOS on by default in the "ham"
setting.  There's no reason for MMTTY's default to cause more repeated
exchanges in noisy conditions, not to mention longer SO2R delays because of
the extra shifts....does that join all the post-contest threads?

Andy K0SM/2
_______________________________________________
RTTY mailing list
RTTY at contesting.com
http://lists.contesting.com/mailman/listinfo/rtty