[aprssig] APRS demo

[Jeff N0JUH]

Thanks Keith!  From your explanation, I think I'm getting a better grasp 
of the issue.  This is probably a bigger problem out here in "flyover 
country" where there are no mountains and igates are relatively sparse.

I wonder if there would be a way to use findu data to analyze the 
distribution of I-Gates, and to suggest the best "local message hops" 
setting for each I-Gate?

Is the I-Gate function smart enough to send a message back along the 
same path on which it heard the recipient station?  I might feel better 
about asking an I-Gate op to bump up his local-message-hops if he 
wouldn't be blasting packets out in all directions.  Then again, aprs 
message packet volume is pretty low compared all the other aprs traffic 
out there, so it maybe it's not a big deal.

   --Jeff N0JUH

Keith VE7GDH wrote:
> Herb KB7UVC wrote...
>
> The only APRS client I am familiar with is UI-View. There is a setting
> in the "APRS Server Setup" to tell it to "gate local messages" and in
> IGATE.INI, there is a setting to tell it how many digi hops away a
> station can be and still be considered local. It is up to the IGate
> operator to be familiar with the APRS network around him - i.e. where
> are the other IGates, where are the digis, what is the topography like
> and so on - and determine what is a local station. If the IGate is on a
> mountain top, zero hops might be a local station. Most IGates "down in
> the valley" will probably want it set to 1 or 2. If it's a "long way"
> (more than two hops) to the next IGate, it should be set to a higher
> number. The chance of success will go down (more chance of
> collisions) but if it really is a long way to the next IGate (more
> than 2 digi hops), it's worth setting a higher value to try and reach
> mobile stations that are "half way" between there and the next IGate.
> 
> The path to be used for messages gated out to RF can't be determined
> by the sending station. They can only specify their own path. It's up to
> the IGate operator (at least in UI-View) to determine what is an
> appropriate path to use. For UI-View, the "default" path is the one
> entered in the station setup. In IGATE.INI it can also be set to a
> specific path or to use the "reverse digi path" that the station was
> last heard via at the IGate.
> 
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig