On 5/8/2012 5:15 PM, Bob Bruninga wrote:
Where'd you get "cannot be formatted"? All I read is "non-standard", not "cannot be formatted" in:
If both the object name and the
It may WORK, but according to the SPEC, that's only allowed in the SECOND 10 characters of the comment!and the offset is not a defined part of the FREQUENCY OBJECT.It most certainly is. "Tnnn -xxx (or +xxx)" works as it should for a FREQ
2nd 10-BYTES Optional Added fields (with leading space)Yep, Bob just proved that the D710 and D72 are non-spec compliant because they're mixing the definitions of a FREQUENCY OBJECT with the attributes of a POSITION COMMENT without requiring the (optional) frequency to appear as the 1st 10 bytes of the packet.
Nope, show me, step by step, how the spec as currently written allows for a FREQUENCY OBJECT's comment to start with a tone and offset?I know the Kenwood will QSY without the second frequencydigipeaters.
We do have to figure out a solution. But I don't see how you can claim theAgreed. That's why we're pushing for a unified specification of ONE repeater frequency definition with an OPTIONAL (but recommended) frequency as the object name.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32