[aprssig] New MSG-OBJ format
Lynn W. Deffenbaugh (Mr)
ldeffenb at homeside.to
Tue Feb 21 16:10:13 CST 2012
BTW, I caved on the POI/OBJECT debate to do my hold-out on the explicit
desire to ADOPT and existing object by a new owner.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 2/21/2012 5:07 PM, Lynn W. Deffenbaugh (Mr) wrote:
> Not really. The message destination field is a fixed with in the spec
> format. If you don't send to a 9 character destination, it pads with
> spaces to 9. The reason we're sticking to 6 is that Yaesu's have an
> AX.25 compatibility restriction.
> The object name can be as long (up to 9) or short as you can make
> unique, but again, that will be going into an object packet that is
> also a fixed width of 9, so shorter object names in the message to
> OBJECT (or POI) won't really make the comment longer in the final
> packet necessarily.
> I'm also all for shorter, especially when targeting spin-n-click radio
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
> On 2/21/2012 4:59 PM, Stephen H. Smith wrote:
>> On 2/21/2012 4:54 PM, Lynn W. Deffenbaugh (Mr) wrote:
>>> Almost, but if the symbol is optional, then it must be delimited.
>>> Consider the following (I don't know if they're valid symbols, but
>>> hopefully you'll get the gist of my concern). These are the message
>>> body sent to OBJECT (yes, I'm caving in on POI).
>> Still think POI would be better -- It saves three letters (and the
>> hassle of entering them on clunky user interfaces like a Kenwood
>> radio) that can then be used in the freeform comment.
>> Stephen H. Smith wa8lmf (at) aol.com
>> Skype: WA8LMF
>> Home Page: http://wa8lmf.net
>> ***** NEW Precision Mapping 9 For UIview Released! *****
>> Vista & Win7 Install Issues for UI-View and Precision Mapping
>> 30-meter HF APRS over PSK63
>> "APRS 101" Explanation of APRS Path Selection & Digipeating
>> aprssig mailing list
>> aprssig at tapr.org
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig