|
That is an interesting concept. In theory, your assumption is correct; if you are running a sat-gate and a sat user is transmitting within direct receive range of you, it is possible that you could I-gate the packet before the ISS digipeater could send it back. But they would have to be within direct contact (non-digipeated) of your sat-gate for this to happen. YAAC doesn't presently support viscous digipeating, so it wouldn't skip ahead of the ARISS or ISS or RS0ISS digipeat callsign to digipeat your packets itself (assuming the sender was using bad practice by specifying a second ground digipeat alias after the ISS alias).
So how many satellite users can you hear directly (ground-wave) at your I-gate? I'm curious whether it's worth implementing such a receive I-gate filter. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of johnhaley3@... <johnhaley3@...> Sent: Thursday, May 13, 2021 10:43 PM To: [email protected] Subject: [yaac-users] Satellite filters? Useful or not necessary? I've been running an iGate for about 8-10 years now, but have just recently moved to YAAC running on Raspberry Pi with a TNC-Pi. I love this software, so easy to use. Anyway, I sort of inherited an ancient 2m rig that has something burned out on the transmit side, but that receives very well, and I thought I'd add a second port and do some sGate operations as well. I added a USB sound card and got it working with Direwolf, and both ports are getting along nicely. I have zero experience with ISS/Amsat ops, so my question is this: I know that on 144.390, terrestrial APRS, that most packets are transmitted with the end goal of being gated to the IS backbone, by whatever route the propagation chooses. But anyone trying to work a satellite or the ISS on 145.825 is assumed to be specifically trying to get a packet digipeated by the ISS. If my station happens to directly hear a packet on 145.825 and gate it, it won't ever register as having traversed the ISS hop, right? I would think a station would rather have a packet ignored by ground stations in the hope of hitting the ISS, vs. always getting intercepted by a ground station and gated, causing rejection of the packet with the ISS in the path. Is there a way to reject or ignore (or otherwise NOT gate) a packet with ARISS in the path, while dutifully gating packets in which the ARISS has been replaced with a *'d alias? My goal is to be as useful as possible to stations trying to work the ISS while NOT being detrimental. Is my logic sound? Is such filtering possible? More to the point, is it beneficial or necessary? John KG5BQX, West Texas |
