[aprssig] Yaesu FREQ OBJECT workaround

[Lynn W. Deffenbaugh (Mr)]

Do you have confirmation that the new proposal of frequency after the 
PHG is actually parsed and acted on properly by all APRS-capable 
radios?  In both forms, a frequency object as well as a repeater-named 
station.

And I just noticed that any 10 character wide display that doesn't parse 
out the PHG is going to line-wrap the frequency as it starts at 
character 9, so 2 characters will end up on the first line with the 
remainder on the next line.  I don't have any of these small APRS radios 
(even the VX-8 enters in here, even if it doesn't QSY) so I don't know 
if any of them remove the PHG or not.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 5/9/2012 10:55 AM, Bob Bruninga wrote:
> The workaround for the FTM-350 not properly parsing the QSY in an APRS FREQ
> OBJECT is suggested as follows:
>
> 1) Continune FREQ OBJECTS as before with Tnnn oXXX Rxxm... in the object
> text. (if oXXX is omitted, then radios will use standard offsets).
>
> 2) For the FTM-350, also include the FFF.FFFMHz in the DIGIPEATERS beacon
> text after the PHG data.  For example for WB4APR-1 digipeater, I might use:
>
> PHG1234/147.105MHz T107 +060 R20m AARC
> PHG1234/146.76 MHz T156 -060 R34m BRATS
>
> OPEN ISSUE:  Does the FTM-350 properly decode the FREQUENCY when the "/"
> separator is used after the PHG data???  Do the Kenwoods?  If not, do they
> work with a SPACE separator?  If not, then we have to run them together.
>
> This should work fine as a workaround since the FTM-350 has a wider display
> and even if the DIGIPEATER CALLSIGN is used, the radio will still display
> the FREQ on the front panel too.
>
> The only thing we lose in the original DIGI text was "W2, SSn-N " which by
> now, everyone should understand to limit their hops to 2 or less
>
> Bob, WB4aPR
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>