Sutron Corporation X-Link Operations & Maintenance Manual, Rev 1.63 5/24/2016 pg. 154
9. If user login matches, X-Link enters command-line session.
10. Server issues pending commands, and X-Link processes and responds
accordingly.
11. When command processing complete, the server disconnects.
12. If the server does not log in, X-Link will time out after 30 seconds and
disconnect.
16.1.1.1. Session Type Code
Session type defines the processing that occurs on connection. Currently, there
is only one session type, 0. This type is defined by the Course of Events above,
and details that follow.
16.1.1.2. Report Type Code
Report Type code describes the purpose of the transmission:
0 = self-timed
2 = entering alarm
4 = exiting alarm
6 = no data, command session only
16.2. Iridium Telemetry Header
Every IRIDIUMLink transmission uses the header described below.
The header starts with a single byte in the ASCII printable range to make it easy
to interpret the content. Most transmissions will just have one header byte.
The header byte identifies the packet type in terms of the content of the packet,
e.g., self-timed, self-timed extended, entering alarm, entering alarm extended,
etc.
Iridium modem buffers are limited in size. "Extended" types mean multiple
packets are required to transmit the entire message. Extended packets have
information in the header that allows them to be stitched together easily. The
extended packet types include a comma-delimited sub-header to describe the
subset of data being sent. The first sub-header differs from all subsequent sub-
headers, in that it includes the total size of the data being sent.
The telemetry header may contain the station name if the setting Tx Station
Name is enabled. Please read below for more details.
16.2.1. Packet Structure
Packets are composed of
To Next Page