TIS-A Traffic serial format

S

Samuel Seidel

Pre-takeoff checklist
Joined
Apr 16, 2020
Messages
110
Location
Georgia
Display Name
Sam
Home Airfield
KGVL
Does anyone know what the serial data from a transponder when receiving TIS-A targets looks like?

I want to feed in traffic to a GTN-650 by using rs232 serial and an esp32 (with adsb traffic) pretending to be a transponder.

But since, I think TIS-A service is fully discontinued, I don’t have a source of this data easily to see what the formatting is.
 
Samuel Seidel said:
Does anyone know what the serial data from a transponder when receiving TIS-A targets looks like?

I want to feed in traffic to a GTN-650 by using rs232 serial and an esp32 (with adsb traffic) pretending to be a transponder.

But since, I think TIS-A service is fully discontinued, I don’t have a source of this data easily to see what the formatting is.
Click to expand...
All transponder/traffic formats on Garmin units are proprietary, thus they are not published.
 
This is true. I am hoping someone has a recoding of the serial data so I can reverse engineer it. With TIS-A discontinued in my area, I don’t have a way to capture this data without emulating radar.

There are some other formats that the GTN650 accepts from other vendors, but I also don’t find any documentation on them either.

The data may be similar to this
Code: 
Absolute Traffic:
$PGAV5,<age_of_position_data>,<hexaddress>,<lat>,<lon>,<gnssAlt>,<baroAlt>,<flightid>,<track>,<groundspeed>,<verticalspeed>,<rssi>,<category>,<dataSource>,<rssiDistance>,<ageMDS>,<ageVelocity>,<agePosition>,<squawk>*<nmeachecksum>

Relative Traffic:
$PFLAU,<RX>,<TX>,<GPS>,<Power>,<AlarmLevel>,<RelativeBearing>,<AlarmType>,<RelativeVertical>,<RelativeDistance>,<ID>
 
More so for fun. I am actually working on reverse engineering a couple different avionics products. At then end I want to create some sort of demo showing the integration of products from two different vendors.

On a desk, it would be nice to show traffic from a controllable GDL90 source.

From an experimental side, it would be nice to have more documentation on the messages being exchanged between modules to be able to create additional features.

For one, I think an audible alert board for the Garmin G5 would be nice for bugged altitudes.
 
The ICD spec might be proprietary to iaco or ARINC. Clearly multiple vendors can read the data from over the air transmission, so there is something out there.

I wonder if one of the ADSB project git hubs would have something? They also have forums that would be great resources too.
 
You must log in or register to reply here.
Back
Top