rbp28668 / skyechobridge Goto Github PK

Look at inbound FLARM messages to set system time - then GDL90 derived messages will have correct time (as will anything else).

If supplying data from secondary source, the TX bit is set in the PFLAU message. This pings the "tx" bit on the flarm display and might make you think Flarm is operating correctly when, in fact, flarm is inoperative but the data is coming from SkyEcho.

Probable solution - zero the TX bit in the secondary source (much simpler than messing about at merge time) - needs to be made configurable as for a standalone (no merge) deployment it should be set properly.

Whilst ADSB targets are unlikely to be circling (and if they are they're probably carrying Flarm anyway), ownship certainly will be and we want to detect this and change the collision avoidance algorithm at this point.