Skip to main content

Destinations

The Antares 4G uses a two-level address system for routing outgoing reports.

Architecture​

Event (ED)
  └── Destination Address (DA0–DA9)
        └── Destination Point (XADP00–XADP01/P15-P16)
              └── IP:PORT (TCP/UDP) or Serial/Satcom

Destination Points (XADP)​

Destination points are the actual network endpoints. Configure with XADP:

>SXADP0000192.168.1.100;3838<         ← TCP
>SXADP0102tracking.example.com;5000<  ← UDP

Special indices:

IndexType
00–01Network (TCP/UDP)
15Serial (RS-232)
16Satcom

Destination Addresses (DA0–DA9)​

Destination addresses bind a DA slot to a destination point. Configure with DA:

>SDA0;P00<     ← DA0 → XADP00
>SDA1;P01<     ← DA1 → XADP01
>SDA2;P15<     ← DA2 → (Serial Port)

Using Destinations in Events​

In ED commands, the last character of the handler field selects the destination address:

>SED00NA0;F00+<    ← Send to DA0 when ignition turns on
>SED01NA1;F00-<    ← Send to DA1 when ignition turns off
>SED02NA2;F12+<    ← Send to DA2 (Serial Port) when motion detected

Example: Configure Two Destinations​

# 1. Set destination points
>SXADP0000192.168.1.100;3838<   ← TCP Destination Point NO ACK
>SXADP010210.0.0.50;5000<       ← UCP Destination Point NO ACK

# 2. Bind to destination addresses
>SDA0;P00<
>SDA1;P01<

# 3. Use in events
>SED00NA0;F00+<    ← Report ignition ON to server 1
>SED01NA1;F00-<    ← Report ignition OFF to server 2