|
Yes, it will work quite well, _unless_ you configure to cross-band digipeat everything from the 9600 baud channel to the 1200 baud channel. Then you may be flooding the 1200-baud channel with more traffic than it can handle (although the issues that the author of DireWolf documents in his article indicates why 9600 isn't as fast as you think it should be). I would _not_ recommend enabling the standard WIDEn-N digipeat aliases on both RF ports.
Because APRS is not point-to-point addressed to specific destination stations, but deliberately multicasted to all stations within range for consistent Situational Awareness by maintaining a Common Operating Picture (called SA/COP in Emergency Management), the kind of logic that exists in a smart Ethernet switch cannot be applied to APRS, because everything is multicasted to all participating stations, so there is no logical way to restrict traffic to specific radio ports based on who is listening to those ports. Old-style connected-mode AX.25 packet didn't have these problems, because packets _were_ addressed to a single target station, using a specific (not generically aliased) and ordered set of digipeaters so that forwarded packets would only go in the correct direction to get to the final destination, rather than spreading flood-fill in all directions. More specific (regional) digipeat aliases slightly reduce the problem, but only slightly, because it simply puts a very fuzzy boundary on the outer perimeter of the digipeat area by stopping out-of-region digipeaters from forwarding, but not all in-region digipeaters may support the regional aliases, causing in-region drop-outs while still flooding a little way over the region boundary in other areas. Sure, people say "I addressed a text message to only one station", but none of the digipeating (or I-gating) stations know if that destination is truly for one station, or for a group of stations. And most APRS traffic is not addressed to a target station, but multicasted (such as position beacons, status messages, etc.) to all stations, so such target-port intelligence would be turned off anyway, and all you have left is the brute-force technique of selective support of individual digipeat aliases. So, it may work, but I won't guarantee it will get you what you want. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Ronny Julian Sent: Wednesday, December 16, 2020 10:50 PM Subject: Re: [yaac-users] 2m-70cm crossband messaging Andrew let me ride coat tails on this and ask you. If I set up what he has running now with two ports can I run 9600 bps on 70cm and 1200 on 2 meters? I have not tried but one radio port yet and wanted to ask before i buy a TNC and 70cm radio. Thanks! Ronny K4RJJ |
