Report Messages
The Antares 4G generates event reports in TAIP format that are sent to configured destination addresses.
The ;ID=<IMEI> field is always required in report messages.
Standard Event Report Format
>REVAABBBBCDDDDDsLLLLLLLLsOOOOOOOOOVVVHHHSS[;TAGS];ID=<IMEI><
Field Breakdown
| Field | Length | Description | Example |
|---|---|---|---|
>REV | 4 | Report header | >REV |
AA | 2 | Report index (00–99, wraps) | 01 |
BBBB | 4 | Number of weeks since 00:00 AM January 6, 1980 | 1447 |
C | 1 | Day of week. From 0 to 6 where 0 is Sunday | 6 |
DDDDD | 5 | Time of the generated report. Seconds since 00:00 of the current date | 54565 |
s | 1 | Latitude sign (+ N, - S) | + |
LLLLLLLL | 8 | Latitude × 100000 (8 digits) | 25782500 |
s | 1 | Longitude sign (+ E, - W) | - |
OOOOOOOO | 9 | Longitude × 100000 (9 digits) | 080281390 |
VVV | 3 | Speed in mph | 015 |
HHH | 3 | Heading in degrees (000–359) | 195 |
SS | 2 | GNSS Quality | 12 |
;TAGS | variable | Extended tag fields (optional) | ;AL=150;BL=3850 |
;ID= | variable | Device IMEI (mandatory) | ;ID=356612020083541 |
< | 1 | End delimiter | < |
Note: Extended tags are optional, but ;ID=<IMEI> is always present.
Example Messages
Basic position report
>REV001447147509+2578250-0802813901519512;ID=356612020083541<
With extended tags
>REV381447147349+2578250-0802813900000012;VO=1560;BL=3820;ID=356612020083541<
Minimum report (without extended tags)
>REV001447147509+2578250-0802813901519512;ID=356612020083541<
Destination Addresses
Reports are sent to configured destinations (see DA command and XADP command):
| Slot | Type | Description |
|---|---|---|
| 0–1 | TCP/UDP socket | Remote server destinations |
| 15 | Serial port | RS-232 output |
| 16 | Satcom | External satellite modem |
Configure with:
>SDA0;<DEST_POINT_INDEX>< ← Assign destination point to address 0
Report Delivery Buffer (Sockets)
When a report is sent to a server destination, Antares uses an internal delivery buffer.
What this means
- If connectivity is unstable, reports are kept temporarily instead of being lost immediately.
- When communication is available again, buffered reports are sent automatically.
When a report is buffered
- A report is buffered when it cannot be delivered right away.
- Valid outgoing reports are queued and delivered in order as the connection recovers.
Delivery and confirmation behavior
- For destinations that require confirmation, Antares retries delivery before giving up.
- If the destination does not require confirmation, reports are removed from queue after send.
- If delivery keeps failing for a long period, the system resets the connection and may discard old pending messages to continue operating.
Restart behavior
- Pending reports are preserved across reboots whenever possible.
- After restart, the device resumes delivery of previously buffered reports.
If the buffer fills up
- The oldest buffered reports are removed first to make room for newer ones.
- This helps keep the device reporting current information during long communication outages.
Event Message Format (REV)
When an event handler is set to send a report, the report type code in the response is REV (Report EVent).