Order Tray | Contact Us | Home | SIG Lists

[aprssig] Yaesu FREQ OBJECT workaround

Bob Bruninga bruninga at usna.edu
Wed May 9 18:12:24 UTC 2012

They should all parse out the PHGxxxx or any of the other fixed formats in
that location (if recognized) and then start "comment" processing (and
display) after it.  This dates all the way back to the first D7 in 1998.


-----Original Message-----
From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
Of Lynn W. Deffenbaugh (Mr)
Sent: Wednesday, May 09, 2012 1:50 PM
To: TAPR APRS Mailing List
Subject: Re: [aprssig] Yaesu FREQ OBJECT workaround

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

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
> 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
> 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
> 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

aprssig mailing list
aprssig at tapr.org

More information about the aprssig mailing list