UAT Translation from Dump978-fa

FlightAware ADS-B Flight Tracking
21

Hmm that might be why it’s a problem when you try and paste it here.

But it should be recognized as AVR by VRS.
Be sure to set the type to AVR.

1 Like
22

Just because this came up in another thread, compiling uat2esnt:

git clone https://github.com/flightaware/dump978.git /tmp/dump978 --depth 1
cd /tmp/dump978/legacy
make uat2esnt
sudo mkdir -p /usr/local/bin
sudo cp uat2esnt /usr/local/bin

You can now use uat2esnt either using the full path /usr/local/bin/uat2esnt or probably just by using the command uat2esnt
I’d recommend using the -t option to suppress TIS-B messages.

1 Like
23

Great command to see the live output

24

Or just connect to 30979 for json-format output (which is somewhat human-readable)

1 Like
25

It does show rssi…
socat -u tcp4-connect:127.0.0.1:30979,forever,interval=5 STDOUT
{“address”:“a555bc”,“address_qualifier”:“adsb_icao”,“airground_state”:“airborne”,“callsign”:“N44295”,“capability_codes”:{“es_in”:false,“tcas_operational”:false,“uat_in”:true},“east_velocity”:-10,“emergency”:“none”,“emitter_category”:“A1”,“geometric_altitude”:1075,“ground_speed”:134,“gva”:2,“metadata”:{“errors”:1,“received_at”:1567187728.264,“rssi”:-26.9},“mops_version”:2,“nac_p”:10,“nac_v”:2,“nic”:10,“nic_baro”:1,“nic_supplement”:false,“north_velocity”:-134,“operational_modes”:{“atc_services”:false,“ident_active”:false,“tcas_ra_active”:false},“position”:{“lat”:26.04828,“lon”:-80.37089},“pressure_altitude”:1200,“sda”:2,“sil”:3,“sil_supplement”:“per_hour”,“single_antenna”:true,“transmit_mso”:41,“true_track”:184.3,“uplink_feedback”:1,“utc_coupled”:false,“vertical_velocity_geometric”:64,“vv_src”:“geometric”}

A more readable version that alerts you something might show up in skyview978 - and also doesn’t disappear when the signal goes away
socat -u tcp4-connect:127.0.0.1:30979,forever,interval=5 STDOUT | grep -C “rssi”

{“address”:“a501da”,“address_qualifier”:“adsb_icao”,“airground_state”:“airborne”,“east_velocity”:-109,“ground_speed”:110,“metadata”:{“errors”:1,“received_at”:1567284218.572,“rssi”:-18.7},“nic”:9,“north_velocity”:-16,“position”:{“lat”:26.01537,“lon”:-80.19221},“pressure_altitude”:1000,“true_track”:261.6,“uplink_feedback”:0,“utc_coupled”:true,“vertical_velocity_geometric”:64,“vv_src”:“geometric”}
{“address”:“a501da”,“address_qualifier”:“adsb_icao”,“airground_state”:“airborne”,“east_velocity”:-108,“ground_speed”:108,“metadata”:{“errors”:5,“received_at”:1567284220.4,“rssi”:-21.6},“nic”:9,“north_velocity”:-14,“position”:{“lat”:26.01522,“lon”:-80.19333},“pressure_altitude”:900,“true_track”:262.6,“uplink_feedback”:0,“utc_coupled”:true,“vertical_velocity_geometric”:-64,“vv_src”:“geometric”}

26

jq is a very handy utility here, it can slice and dice the json and extract just the bits you care about.

e.g.

$ jq -c '{address,time:.metadata.received_at,rssi:.metadata.rssi}' <foo.json
{"address":"a555bc","time":1567187728.264,"rssi":-26.9}
1 Like
27

is the UAT range value “selected_sitedist” available to be extracted with jq? Tables of address, range vs rssi might be helpful for adjusting gain and optimizing adsb receiver.

28

There is no range value transmitted in the UAT messages; this is a derived value.

1 Like
29

I ran into the same issue noted above with the output of UAT2ESNT having output like this:

<000000000000FF96ACA65199005C8EB808091A7A9A;

I had compiled it with a straight ‘make’ executed in the folder I’d untarred into.

Following the compile instructions from wiedehopf in the posts above produced a ‘clean’ output like this:

*96A8EA94213B6DF4060820EA1813;

So now I have a good translation I’m trying to feed this to FR24 - anybody had any joy with that ?

30

Brows through this thread.
Better read all posts from 1st up to the last to get a clear picture.

Feed 1090ES + 978UAT to Different Sites

 

 

31

@DavidUnsworth

You can directly feed dump978-fa output (without translation by uat2esnt) to Radarbox24 feeder by method given by @dynamicpbx at Radarbox24 Forum:

 

Please also see this post for explanation of above method:
https://discussions.flightaware.com/t/comparison-of-different-dongles-for-978-mhz-uat-reception/54157/167
 

1 Like
32

Here’s an update for future folks who land on this thread like I did… Everything in this thread still applies regarding using uat2esnt, however, many of the referenced Git repos have commits that broke uat2esnt, at least for some integrations like Virtual Radar Server.

Specifically, there was a change “Emit messages with a magic UAT timestamp” which appends a constant value to every converted message. This breaks functionality with Virtual Radar Server, which was my goal.

This is the culprit commit: legacy/uat2esnt: emit messages with a magic UAT timestamp · flightaware/dump978@56d4c05 · GitHub. When I use a commit earlier than this one and compile according to the make instructions in this thread, I’m able to use uat2esnt to pipe the UAT feed into Virtual Radar Server as a AVR/Beast input.

1 Like