TSAT 3000 - Telemetry and data transfer via SATellite
TSAT 3000 Configuration Parameter Description, January 2013 Page 71 of 124
3.10.4 NET_{FIRST | START | LAST}_POLL_RT
FIRST: Default 1, Range 1…4093
START: Default 1, Range 1…4095
LAST: Default 3, Range 1…4095
Requirement:
NET_FIRST_POLL_RT <= NET_START_POLL_RT <= NET_LAST_POLL_RT <= NET_NO_OF_RTS.
HUB: When the HUB is establishing the network, it will start
to poll NET_START_POLL_RT. If no
poll-acknowledge (
POLL_ACK) is received within NET_MAX_POLL_SECONDS, it will continue to
poll next RT, and so on. When
NET_LAST_POLL_RT has been polled, it will start all over again
with
NET_FIRST_POLL_RT, and so on. (START … LAST, FIRST … LAST, FIRST …)
When HUB is connected to NMS, it may tell HUB to exclude some RTs from the poll-range:
• RTs that are not
defined in the NMS.
• RTs that are reported UP on another HUB.
• RTs that are tagged “Out-of-Order” (NMS Ver >= 10.0.1).
When HUB has polled (NET_LAST_POLL_RT – NET_FIRST_POLL_RT + 1) number of RTs,
without being able to lock to any RT carrier, it will RESET itself.
After the HUB has got in-lock to one of the RTs, it will send a LINK_RESET packet (to Open the
link) to each RT in the range from
NET_FIRST_POLL_RT to NET_LAST_POLL_RT.
RT: Normally Not Used, but NET_FIRST_POLL_RT defines the CLUSTER Address of this RT. See
PORT_STREAM_RT [n].
Ver >= 30.8.0
NET_FIRST_POLL_RT … NET_LAST_POLL_RT are used to identify the CLUSTER of Multi-
Inbound-Link (MIL) RTs sending on Secondary Inbound carrier to Slave-HUB. These MIBs
must be set identical on Slave-HUB and all RTs that are sending to this Slave-HUB.
NET_RT_ADDRESS on these RTs must also be within this range.
See also
PHL_TX_RT_FREQUENCY_2 and PORT_TX_FREQUENCY_2 [n].