[aprssig] Correct PSAT & igating
kennethfinnegan2007 at gmail.com
Mon Jun 8 09:51:00 CDT 2015
What we're discussing here is trying to use the APRS-IS to analyze the
RF performance of a single digipeater.
The APRS-IS was not designed to give any insight into local RF
performance. I'm not going to support any hacks on aprx to try and
work around that fact.
If you want to perform RF analysis, you need to publish your raw RF
logs. For an example, see the Baldi digipeater page here:
On Mon, Jun 8, 2015 at 5:29 AM, Nagi Punyamurthula <n0agi at n0agi.com> wrote:
> So, related to this topic, I had a separate thread w/ the APRX user team and the APRX lead Ken Finnegan to explore if the current APRX software allows for incoming RF level filter to filter only those that have been digi'd by RS0ISS* call; and then use those packets for igating behavior. However, APRX does not have that support by design and is purpose built to disallow that feature (whether that's a feature or a misfeature is debatable).
> N0AGI, Nagi
> -----Original Message-----
> From: aprssig [mailto:aprssig-bounces at tapr.org] On Behalf Of Kai Gunter Brandt - LA3QMA via aprssig
> Sent: Monday, June 08, 2015 4:56 AM
> To: aprssig at tapr.org
> Subject: [aprssig] Correct PSAT & igating
> I'm running APRX to IGATE the ISS and PSAT etc
> My challange is that local users get IGATEd even if they have not been digipeated by i.e ISS
> Should i somehow filter this out? If so how?
> b`/]"4\}Erling,Bergen JP20QI=
> RS0ISS>CQ,qAR,LA3QMA-SG:>ARISS - International Space Station
> Kai Gunter
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig