I’ve made a couple of minor enhancements to the dump978 source for those utilizing it.
Two improvements have been made.
- RSSI measurements have been added. uat2text, uat2json, and uat2esnt all now provide rssi measurements.
- uat2text provides rssi on a line at the end of each message.
- uat2json provides rssi information for each aircraft.
- uat2esnt provides rssi with each ADSB ES message that is sent.
A few notes on this. uat2json provides the most recent UAT message’s RSSI. So it is more of an instantaneous rssi and not averaged over time. This means that if you are using uat2json and uat2esnt and looking at both maps at the same time they will not have the exact same RSSI. This is because dump1090 averages rssi over the last 8 ADS-B messages. Each UAT message is ~3 or 4 ADS-B messages. So dump1090 is really showing the average of the last 2 or 3 UAT messages.
The changes to uat2esnt have been tested with dump1090 and nothing else. Sending RSSI involves also sending the timestamp which I have not filled out appropriately. dump1090 ignores this field anyway so it doesn’t matter for it.
- Receiver position can now be set in uat2json (e.g. uat2json --rec-pos 12.56732,32.72354 /var/run/dump978)
This allows for both range rings and distance measurements for aircraft to be populated on the map.
If anyone is interested I would love to hear back if it works for them as well as it seems to be working for me.
Source located here: https://github.com/KeyserSoze1/dump978