[aprssig] FW: FW: FREQ Object radio issues (d)

[Bob Bruninga]

REV-D.   Revising the format of this email for consistency in building the
COMPATIBILIITY MATRIX  Moved specific hardware comments at the end.
 
COMPATIBILITY MATRIX:
-------------------------------------------------------------

QSY's on FFF.FFxyz OBJs: (Y,N) (Early D710's require FFF.FFFyz), (FTM350=N)

QSY's on FFF.FFFMHz in Position text (Y,N) (FTM350 requires trailing space)

QSY's on >FFF.FFFMHz ... in STATUS packets (Y,N)

QSY, Tone and offset in STATUS (Y,N)
                                               
Translates FFF.FFF to 6.25 KHz splits (Y,N) (D72=Y)

Leading Space XMT: Before FFF.FFFMHz or before Tnnn (Y,N) (D710=N)

Leading Space RX:  (Requires, Ignores, requires-Not)

Requires "MHz" exact case:       (Y,N)  (FTM350=Y)

Requires "MHz_" trailing space:  (Y,N)  (FTM350=Y)

Transmits "MHz_" trailing space: (Y,N)  (Early D710 does not)

Transmits unprintable bytes: (Y,N)  (D710s programmed with RT software did.
Fixed)

Transmits offsets +xxx and -xxx   - (Y,N)

Responds to +xxx and -xxx offsets - (Y,N)

Allows +xxxX and -xxxX "0"s for humans - (Y,N) D72 allows (and ignores)
trailing "0"

-------------------------------
NOTES ON KNOWN ISSUES:

NON-PRINTABLE CHARACTERS in the D710 after the QSY Freq:  Traced to RT
Systems Software used to program their radios.  Fixed in new RT software.

Use of the "xyz" in the OBJECT NAME:

> FFF.FF0xy object is OK and QSY is OK
> FFF.FF5xy object is OK and QSY is OK
> FFF.FFxyz object will not QSY in early D710 models.  Now fixed.

> FFF.FFxyz objects of any format will not QSY the FTM-350 (confirm?)

Extra "0" on end of the +xxx or -xxx OFFSET format.  The THD72 will accept
extra characters after the required +xxx or -xxx.  These will all give the
proper offset:

> 440.000MHz tOFF +500 Bob's radio
> 440.000MHz tOFF +5000 Bob's radio
> 440.000MHz tOFF +5000Bob's radio
> 440.000MHz tOFF +5000000 Bob's radio
> 440.000MHz tOFF +500Bob's radio

BUT SHOULD NOT BE USED until confirmed all existing radios can tolerate it.
This was a proposed backwards-compatible future fix to making the offset
more human readable, because then we could recommend the use of +5000
instead of the +500.  But this CANNOT BE USED until we have surveyed all
radios to see if ALL radios can properly set the offset if the additional
"0" is included.  Or all radios are upgraded to do so