You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Stratux has rudimentary support for SoftRF. This is implemented by
starting a dump1090 process with --net-only
reading SoftrRF dump1090 output via Serial, forwarding it to dump19090
reading traffic from dump1090
This has a couple of drawbacks:
it interferes with the dump1090 process for the SDRs, so you can only have EITHER a SoftRF connection OR a 1090ES SDR enabled
We have two GPS in the device, the SoftRF one is ignored for Stratux
Is it worth implementing better Support for SoftRF (especially the T-Beam)?
Benefit:
We can easily transmit Flarm
We can also receive OGNTP and PilotAware if desired
We could use the SoftRF builtin GPS for Stratux
The second SDR would be free for UAT reception
Drawbacks:
SoftRFs Flarm reception range seems to be quite a bit worse than the OGN stack with an SDR
Another PCB - different case is needed (could provide a 3D printable model that fits a Stratux+SoftRF build)
Implementation:
I think it would make most sense to parse the SoftRF NMEA stream instead of the dump1090 stream, as it provides more information.
Another possibility would be to just slightly improve the current support to not start its own dump1090 if we already have 1090ES enabled - so that both work in parallel.
The text was updated successfully, but these errors were encountered:
Hi,
Stratux has rudimentary support for SoftRF. This is implemented by
This has a couple of drawbacks:
Is it worth implementing better Support for SoftRF (especially the T-Beam)?
Benefit:
Drawbacks:
Implementation:
I think it would make most sense to parse the SoftRF NMEA stream instead of the dump1090 stream, as it provides more information.
Another possibility would be to just slightly improve the current support to not start its own dump1090 if we already have 1090ES enabled - so that both work in parallel.
The text was updated successfully, but these errors were encountered: