TSAT 3000 - 3.1.19 PORT_STREAM_RT_PORT [n]

TSAT 3000 - Telemetry and data transfer via SATellite
TSAT 3000 Configuration Parameter Description, January 2013 Page 28 of 124
3.1.19 PORT_STREAM_RT_PORT [n]
Default 1, Range 1…255
• Not Used when PORT_TYPE [n] is SERVICE.
In this case, RT-Port is included in received packets from NMS.
• Used when
PORT_TYPE [n] is STREAM, ADAPTER or NETWORK.
All User-Data received from this PORT will be sent to the Unit(s) defined by
PORT_STREAM_RT [n], and Port(s) as defined below:
Value Hex Description
1 … 64 0x01 … 0x40
PORT 1 … 64.
User-Data is sent to the (remote) PORT.
65 … 127 0x41 … 0x7F n/a – Reserved for internal addressing.
128 … 254 0x80 … 0xFE
BITMASK.
User-Data is sent to one or more (remote) PORTs 1 … 7,
defined by the bitmask of 7 lower bits (0x7F).
Note: You cannot send to all
7 PORTs, because this will give
the bitmask 0xFF, which is the MANAGEMENT Port.
255 0xFF
MANAGEMENT.
User-Data is sent to (remote) Management-module, which will
loop data back to originator.
Normally, this parameter isn’t used at RT.
Usage is dependent on
PORT_STREAM_RT [n], as shown in table below:
PORT_STREAM_RT_PORT
PORT_STREAM_RT
Leased Line
HUB RT
HUB to RT PORT(s) at remote RT
Don’t care
RT to RT n/a PORT(s) at remote RT
LOCAL
PORT(s) at Local Unit