Skip to main content

XANS - Network Status

Provides a compact network-status snapshot with three groups:

  • Group 1: air interface and APN credentials
  • Group 2: SIM, GSM, GPRS, bearer, and jamming status
  • Group 3: destination-point socket status list

Qualifiers

  • Q: query status (>QXANS<)
  • R: response (>RXANS...<)

Note: Antares parser currently accepts Q for command input and returns the R response format.

Format

Query:

>QXANS<

Response:

>RXANS{GROUP1};{GROUP2};{GROUP3}<

Groups are separated by semicolons.

Group 1 Fields (Air Interface + APN Credentials)

Format:

{AIR},{APN},{SIM_PIN},{GPRS_LOGIN},{GPRS_PASSWORD}
FieldDescription
AIRAir interface status: 0 down, 1 up
APNAPN
SIM_PINSIM PIN
GPRS_LOGINGPRS login
GPRS_PASSWORDGPRS password

Group 2 Fields (SIM/GSM/GPRS + Bearer + Jamming)

Format:

{SIM_INSERT},{SIM_STATE},{SIM_LOCK_REASON},{GSM_REG},{GSM_RSSI},{GPRS_ATTACHED},{GPRS_REG},{LOCAL_IP},{BEARER},{JAMMING}

SIM insert state

  • 0 = not inserted
  • 1 = inserted
  • 2 = SIM hardware off

SIM state

  • 1 = ready
  • 2 = SIM hardware off
  • 3 = SIM inserted
  • 4 = SIM removed
  • 5 = PIN error
  • 6 = waiting PIN
  • 7 = SIM lock
  • 8 = SIM error

SIM lock reason

Relevant only when SIM_STATE = 7:

  • SIM PIN = waiting for SIM PIN
  • SIM PUK = waiting for SIM PUK

GSM register state

  • 0 = not registered
  • 1 = registered
  • 2 = not registered, searching
  • 3 = rejected
  • 4 = error
  • 5 = registered, roaming

GSM RSSI

  • 0 = -113 dBm or less
  • 1 = -111 dBm
  • 2..30 = -109 to -53 dBm
  • 31 = -51 dBm or greater
  • 99 = not known / not detectable

GPRS attached state

  • 0 = not attached
  • 1 = attached

GPRS register state

  • 0 = not registered
  • 1 = registered
  • 2 = not registered, searching
  • 3 = rejected
  • 4 = error
  • 5 = registered, roaming

Local IP address

  • Carrier-assigned local IP address for the data session.

GPRS bearer state

  • 0 = bearer down
  • 1 = bearer up

Jamming state

  • -2 = normal state
  • 0..60 = jamming detection in progress
  • -3, -1 = jamming detected

Group 3 Fields (Destination Points Sockets)

Destination points are listed in chronological creation order (not by XADP index).

  • Destination points are separated by \
  • If no destination point is configured, this group is empty

Per destination point, fields are:

{ADDRESS},{SOCKET_STATE},{LOCAL_PORT},{REMOTE_IP},{REMOTE_PORT},{SOCKET_UP_TIME},{SOCKET_DOWN_TIME},{SOCKET_DOWN_LOG_TIMER}

Socket connection state:

  • 0 = not connected
  • 1 = connecting
  • 2 = closing
  • 3 = connected
  • 4 = connected, limited
  • 5 = closing, hold

Example

>RXANS1,intnet.cxn,,,;1,1,null,5,31,1,5,10.1.17.207,1;socket://visionairegps.com:8040,3,1024,66.228.127.212,8040,3,,\;,,,;3,1,1,0,4;<

Interpretation:

  • Air interface is up, APN is intnet.cxn, PIN empty.
  • SIM inserted and ready; GSM and GPRS registered and roaming; RSSI is 31; local IP is 10.1.17.207.
  • Destination point visionairegps.com:8040 is connected; local port 1024; remote IP 66.228.127.212; uptime 3 seconds.

Antares Implementation Notes

Current Antares implementation keeps response framing and field order above, with these practical details:

  • Command input supports Q only (>QXANS<).
  • Group 2 local IP may be returned empty depending on modem-state availability.
  • Group 3 currently populates destination address, mapped socket state, and configured port; remote endpoint and timing fields may be empty.