EasyManua.ls Logo

TSAT 3000 - 3.2.7 SOCK_OPTIONS [n]

Default Icon
124 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
TSAT 3000 - Telemetry and data transfer via SATellite
TSAT 3000 Configuration Parameter Description, January 2013 Page 33 of 124
3.2.7 SOCK_OPTIONS [n]
Default 0, Range 0…255 (0xFF)
Bit field to control miscellaneous SOCKET options.
Bit Mask Mnemonic Description Version
0
0x01
TCP_KEEPALIVE
Detect dead TCP connections.
1
0x02
TCP_DELAY
Delay and merge small TCP segments.
2
0x04
n/a
3
0x08
n/a
4
0x10
DEBUG_PRINT_RX
Print (to Console) all bytes received from SOCKET.
>= 30.4.0
5
0x20
DEBUG_PRINT_TX
Print (to Console) all bytes sent to SOCKET.
>= 30.4.0
6
0x40
n/a
7
0x80
LOOP
Loop all data sent and received to/from SOCKET.
TCP KEEPALIVE
Enable this option to make the transport protocol (TCP) initiate a timer to detect a dead
connection. This prevents an application from hanging on an invalid connection. The integrity of a
connection is verified by transmitting zero-length TCP segments triggered by a timer, to force a
response from a peer node. If the peer does not respond after repeated transmissions of the
KEEPALIVE segments, the connection is dropped, all protocol data structures are reclaimed, and
processes sleeping on the connection are awakened.
Applicable when
SOCK_PROTOCOL [n] is TCP, only.
There’s no reason to enable this feature when
SOCK_TYPE [n] is TSAT_NMS or
COMPORT_SERVER, because TSAT Socket-Protocols will always exchange data to detect
dead connections.
There’s also no reason to enable this feature when
SOCK_TYPE [n] is RAW_DATA and you
know that connected application always will send data at regular intervals. In this case, the
SOCK_IDLE_TIMEOUT [n] could be used to detect dead TCP and UDP connections.
TCP DELAY
Applicable when
SOCK_PROTOCOL [n] is TCP, only. By default, all TCP packets will be sent to
the peer node immediately. You can enable this option to avoid the congestion that can be
produced by a large number of small TCP segments. The TCP_DELAY algorithm attempts to
have no more than one outstanding unacknowledged segment in the transmission channel while
queuing up the rest of the smaller segments for later transmission. Another segment is sent only
if enough new data is available to make up a maximum sized segment, or if the outstanding data
is acknowledged.
DEBUG PRINT {RX | TX}
Ver <= 30.3.1
Not Implemented.
Ver >= 30.4.0
Print all data received and/or sent from/to SOCKET to Console.

Table of Contents