Integrations · ASTERIX
ASTERIX
Radar plots and tracks.
Not available in this build
The ASTERIX receiver is not enabled yet.
What this gives you
| What arrives | CAT 048 and CAT 034 |
| What you can send | nothing. This one reports. |
| What it carries | radars |
Connect one
- Turn the protocol on. Settings → Integrations → ASTERIX → enable.
- Set the address, in the Multicast group field. There is no default, so this one has to be filled in.
- 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
ASTERIX runs over UDP multicast, UDP. These are the forms that parse:
| Transport | Form | What it means | Example |
|---|---|---|---|
| UDP multicast | udpmc:GROUP:PORT | Join a multicast group rather than dialling a host. | udpmc:239.1.1.1:8600 |
| 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 |
When it is working
The radar 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.