Any value in using a Stratux to translate ADS-B targets and relay them via SOftRF

[Ryan Dewsbury]

So my club is a bit behind the times but has decided to get some SoftRF devices in the form of T-echos running MB firmware. They will be running FLARM and ADS-L so they will only be seeing those targets.

We happen to be in the coverage area of pair of CFIB.ca stations so we could get a bunch of non-ADS-B targets relayed as TIS-B on 978mhz when at altitude if we had ASD-B reception. The relayed aircraft are mostly NemoScout but also OGN traffic. 

What I had in mind was to write some code for Stratux to send its traffic data to a T-echo and use that as a relay. Just wondering if this is a bad idea in general. Like will this much data overload the T-echo? Will the T-echo even accept data coming this way? Will this much relaying cause issues with OGN? Filtering data on the pi to limit range would be possible.

[Moshe Braner]

Some comments:

The T-Beam is easier to make wired connections to than the T-Echo.  For data input and output, and for a buzzer and/or strobe.

My SoftRF can accept external traffic data in the GDL90 format.  This is intended for an add-on ADS-B receiver.

My SoftRF can also relay such traffic data, for the benefit of other nearby SoftRF devices.  This relay is done in the '"Legacy" protocol, invisible to FLARMs.  This relaying is limited, only a few targets and only once in 15 seconds or so.

To avoid adding such relayed traffic into what OGN processes, I used to set the "no-track" flag on in such transmissions, telling OGN stations to ignore it.  Then I changed my mind, but may change it again.  What do you think?