ADS-B
Cooperative aircraft, from a receiver.
:::caution Not available in this build The ADS-B receiver is not enabled yet. :::
What it carries
Telemetry in. position and identity.
Control out. Nothing. This protocol reports and is never commanded.
On this protocol you connect receivers.
Connect one
- Turn the protocol on. Settings → Integrations → ADS-B → enable.
- Set the address, in the Connect to field. Leave it at
tcp:127.0.0.1:30003unless something else on the host already has that port. - Declare the device. Settings → Assets → ADD, find the product, pick this protocol. The address you set above is where it is expected to arrive.
The address format
ADS-B runs over TCP, UDP, Push. These are the forms that parse:
| Transport | Form | What it means | Example |
|---|---|---|---|
| TCP | tcp:HOST:PORT | We open a stream to the device or its server. | tcp:127.0.0.1:30003 |
| UDP | udpin:HOST:PORT | We bind and wait. The usual case: the device sends to us. | udpin:0.0.0.0:14550 |
| UDP | udpout:HOST:PORT | We send to a fixed address and receive on the same socket. | udpout:192.168.1.20:14550 |
| Push | push | The device or a sidecar posts to us. No address to configure. | push |
When it is working
The receiver appears in Settings → Assets with a live health state, and the Integrations row counts it. On the console, its returns start driving tracks within a few seconds.
If nothing arrives
| Symptom | Where to look |
|---|---|
| Nothing arrives, and the row looks healthy | Nothing is reaching the address. Check the device is sending to this host and that no firewall sits between them. |
| It connects, then drops | Two things are bound to the same port, or the device and the host disagree about which end dials. See the endpoint forms above. |
The protocol itself
This one has no public specification to link to.
Where to go next
- All integrations for the protocols this build speaks.
- Onboarding an asset for the add flow in full.
- Supported hardware for the products that use it.