[aprssig] New Project: WHERE-IS
Lynn W. Deffenbaugh (Mr)
ldeffenb at homeside.to
Thu Mar 9 10:47:06 CST 2017
Pete is correct that the base APRS message protocol for 3rd party
packets fully supports RF messaging to/from non-AX.25-compatible -SSIDs
on the APRS-IS. The Kenwood line of APRS-capable radios fully support
this. However Yaesu's APRS radios cannot message to non-AX.25 -SSIDs
nor will they ack messages received in 3rd party packets from such -SSIDs.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 3/9/2017 10:11 AM, Pete Loveall AE5PL Lists wrote:
> The reason for the different SSIDs was because there were (may still be) misbehaving IGates that would not properly gate non-zero-through-15 SSIDs to RF. The 3rd party header permits (and your D72 supports) non-numeric SSIDs in messages as long as the IGate supports non-numeric SSIDs being gated to RF. Direct gating to RF (not using 3rd party format) is not supported by APRS-IS due to loops and other issues that occur.
> Hope this helps.
> Pete Loveall AE5PL
> pete at ae5pl dot net
>> -----Original Message-----
>> From: aprssig [mailto:aprssig-bounces at tapr.org] On Behalf Of Fred Hillhouse
>> Sent: Thursday, March 09, 2017 8:07 AM
>> Cc: 'TAPR APRS Mailing List' <aprssig at tapr.org>
>> Subject: Re: [aprssig] New Project: WHERE-IS
>> Since WHO-IS and WHO-15 have the same response, why not use WHERE-IS
>> and WHERE-15?
>> The WHO -15 is useable from a mobile while I don’t believe WHO -IS works.
>> The 15 is made into a 4-bit code for TX whereas the IS will not resolve to four
>> bits. But I haven’t tried this from my D72 so I can’t be sure. From an internet
>> only client it doesn’t matter which one is used.
>> Best regards,
>> Fred N7FMH
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig