TSAT 3000 - Telemetry and data transfer via SATellite
TSAT 3000 Configuration Parameter Description, January 2013 Page 87 of 124
3.11.22 PHL_TX_RT_FREQUENCY_2
Ver <= 30.4.1: Default 0, Range 0 + 14.000.000…14.500.000
Ver >= 30.5.0: Default 0, Range 0 + 5.000.000…14.500.000
Set the Secondary Inbound carrier [kHz] in a Multi-Inbound-Link (MIL) network.
Ver <= 30.5.0
Not Used.
Note: The value must
be zero for correct HUB operation (RT doesn’t care).
Ver == 30.6.0 … 30.7.0
Not Used.
Note 1: The value must
be zero for correct HUB and RT operation.
Note 2: DSP will be reprogrammed 10 seconds after you’ve changed CURRENT value.
Ver >= 30.8.0 + RT DSP >= 2.3.1
HUB: Slave-HUB operation is enabled by a non-zero value.
RT: Multi-Inbound-Link (MIL) operation is enabled by a non-zero value. The RT will use
this Secondary Inbound carrier sending to Slave-HUB.
See also NET_{FIRST | START | LAST}_POLL_RT and PORT_TX_FREQUENCY_2 [n].
Note: DSP will be restarted 10 seconds after you’ve changed CURRENT value.
Ver >= 30.8.0: Restart of DSP is enabled by bit 2 (0x0004) in
UTL_UTILITY_MASK.
Configure MIL Network
• Define Slave-HUB by
PHL_TX_RT_FREQUENCY_2 <> 0 and PHL_INBOUND_IDENTITY_2.
• Define MIL-RT by
PHL_TX_RT_FREQUENCY_2 <> 0 and PHL_INBOUND_IDENTITY_2.
• Define range of MIL-RTs by
NET_FIRST_POLL_RT … NET_LAST_POLL_RT. These MIBs
should be set identical on Slave-HUB and all RTs that are going to send on the Secondary
Inbound carrier (
PHL_TX_RT_FREQUENCY_2) to this Slave-HUB. NET_RT_ADDRESS on the
RTs must be within this range.
• On RTs: Set
PORT_TX_FREQUENCY_2 [n] = 1 for all PORTs that shall send to Slave-HUB –
using the Secondary Inbound carrier.
• Define a communication link between each Slave-HUB and the corresponding Master-HUB,
as described on next page. It is recommended (not mandatory) to enable this
communication link.
- If a communication link between Slave-HUB and Master-HUB is
defined, the
NET_RT_ADDRESS of these HUBs cannot be the same. Preferable use the same HUB-
number as defined in NMS. The purpose of this communication link is:
a) Slave-HUB will request RTs to send packets continuously when it’s searching for the
RT-carrier.
b) Master-HUB will know the states of the Slave-HUBs, and send this information to the
RTs (in the
SYNC packet). This is required for full functionality of a Redundant MIL
network.
c) Application-Data received from any PORT on the Slave-HUB will be relayed to the
Master-HUB for transmission to the RTs.
- If the communication link between Slave-HUB and Master-HUB isn’t
defined, the Slave-
HUB cannot request the RTs to send packets continuously. It cannot
lock to RT-carrier,
unless you enable bit 4 (0x0010 –
UTILITY_SEARCH_LOCK_TO_FIRST_OK_PACKET) in
UTL_UTILITY_SEARCH_MASK.
To Next Page
Loading...