[aprssig] Re: TIGER maps what-s the problem?

[AE5PL Lists]

I would also recommend using third-party packets for Rhinos because of
this reason (9 character "callsign") and because they are not on the
APRS network.  In other words, use something like RHINO* for their
network indicator instead of TCPIP*.  We are doing this with the D-STAR
radios and it works well (DSTAR*).  An IGate for a RHINO network might
be the gate symbol with an R overlay (we are using the gate symbol with
a D overlay for a D-STAR IGate)?

I believe we have confirmed that all current APRS display software
allows for any 9 character callsigns in 3rd-party packets in a previous
thread.

73,

Pete Loveall AE5PL
mailto:pete at ae5pl.net 

> -----Original Message-----
> From: Robert Bruninga
> Posted At: Tuesday, June 13, 2006 3:36 PM
> Subject: Re: [aprssig] Re: TIGER maps what-s the problem?
> 
> Or send them as 3rd party with a full 9 character name.
> 
> This may or may not work depending on how the client software 
> treats a 3rd party pcaket.  APRSdos will receive the
> full 9 character name just fine.   Probaby most others will
> too, but be sure to check it before committing to this approach.
> 
> The only thing that REQUIRES a callsign to be 6 characters
> + SSID is a transmitting TNC.  On receipt, most software
> may not be so picky...