[aprssig] SATgates ? (again)

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Mon Jan 25 07:11:57 CST 2016


But even if such a switch is implemented in the IGate code, only the 
first digipeated received packet will be propagated through the APRS-IS 
(and maybe show up at aprs.fi).  But then you'll be asking to see the 
double-digipeated packet that hit two APRS satellites in orbit before 
being received at the ground a second time and those would still be 
dupe-suppressed.

The only solution is a non-dupe-suppressing satellite-supporting APRS-IS 
parallel after which you'd have to persuade Hessu at aprs.fi to remove 
his further dupe-suppression to record and show all of the packets 
coming in from this parallel network.

That's a long up-hill battle you're barely at the start of IMHO.

If the purpose of the APRS satellites is to provide a super-long-range 
digipeater to ensure packet delivery from remote areas, then the current 
system is working fine.  If the purpose of the APRS satellites is to 
give people visibility that their packets actually traversed through 
space, then that's the same thing as asking to use the APRS-IS as an RF 
analysis tool which is beyond its design requirements.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/24/2016 6:28 PM, Robert Bruninga via aprssig wrote:
> I'm not trying to change the APRS-IS.  I'm trying to fix the satgate 
> problem by asking any author of IGate code to include a SATgate mode 
> that will ignore direct, undigipeated packets.  When any authors 
> respond with the feature, then we will have a SATgate we can recommend 
> for people to use.
>
> This is a SATgate only issue and it should not be included in 
> terrestrial operation.  Terrestrial APRS network has a different 
> objective.
>
> The people that we want to set up SATgates are Satellite folks first 
> and in far corners of the world and we want to eliminate this obscure 
> problem in that application by fixing it at hte SATgate..
>
> Bob, WB4APR'
>
> On Sun, Jan 24, 2016 at 4:43 PM, Jason KG4WSV <kg4wsv at gmail.com 
> <mailto:kg4wsv at gmail.com>> wrote:
>
>
>
>     On Sun, Jan 24, 2016 at 3:09 PM, Robert Bruninga via aprssig
>     <aprssig at tapr.org <mailto:aprssig at tapr.org>> wrote:
>
>         >... What you're describing is trying to use the APRS-IS as a
>         local RF analysis tool.
>
>         No, I'm trying to make the APRS satellites work as a useful
>         constellation and to have their integration into the APRS-IS
>         work in a consistent manner all over the world.
>
>
>     It does - it treats your hypothetical "satgate" just like any
>     other Igate.
>
>         I'm just trying to identify IGate code that has this SATgate
>         mode so that we can know what software to recommend for
>         SATgate use.
>
>
>
>     There isn't any.  But that's OK, since there isn't a special
>     version of APRS-IS stripped of deduplication running in your
>     hypothetical "satgate" mode to connect them to.
>
>     This is exactly the same non-problem as using APRS-IS for RF
>     propagation analysis.  APRS-IS simply isn't designed for that, and
>     the way it is designed actively prevents its use in that manner.
>
>     -Jason
>     kg4wsv
>
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20160125/a3317951/attachment.html>


More information about the aprssig mailing list