[aprssig] IGate FIlter for AMSATS?
bruninga at usna.edu
Sun Feb 26 09:50:53 EST 2017
> So I guess maybe the held-until-not-seen-on-IS
> might be the only solution that covers all cases
> withouth having to be managed call-by-call?
But then Hessu points out delays are not good either?
And Delaying ALL Telemetry (direct packets) is shooting ourselves in the
foot since timeleness of telemetry is very important, while recording user
activity (digipeated packets) is not as timely.
Drats. Does it boil down then to having to reject all DIRECT packets while
then allowing exceptions by callsign for each new satellite..... argh...
On Sun, Feb 26, 2017 at 9:00 AM, Robert Bruninga <bruninga at usna.edu> wrote:
> Drats... I forgot that the telemetry from the sats themselves are
> direct! Grrrr...
> So although this is a great idea, most of the APRS satellites all DO
> transmit with a one hop path. They are transmitted via APRSAT so that any
> telemetry packet that might get heard by any other APRS satellite will be
> digipeated once. THis way we can get a two-hop over the horizon data.
> First time I saw it, the ISS was over North Africa, and heard by PCSAT over
> the atlantic (no one else in footprint) and the digipeated packet was heard
> in Maryland.
> So I guess maybe the held-until-not-seen-on-IS imight be the only solution
> that covers all cases withouth having to be managed call-by-call?
> Bob, WB4APR
> > As a compromise on #1, if the directly heard station has no path, it
>> could be
>> > passed to APRS-IS. This would solely prevent packets heard directly
>> with a path
>> > from being passed upstream, not all directly heard packets. This would
>> > hearing satellite packets directly since they should never have a path
>> or they
>> > should only show digipeated by their internal digipeater (either would
>> > acceptable).
>> aprssig mailing list
>> aprssig at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aprssig