TSAT 3000 - Telemetry and data transfer via SATellite
TSAT 3000 Configuration Parameter Description, January 2013 Page 52 of 124
Note 2: When AGC is enabled, the Tx-Detector will normally be fetched each second
, except
when any adjustments to the Tx-Gain DAC shall be done. In this case, the Tx-Detector is
fetched each time a packet
is sent – to speed up regulation time.
Note 3: An RT in “Multi Inbound Link” (MIL) network (See
PHL_TX_RT_FREQUENCY_2) may
send on both Primary and Secondary Inbound carriers. Due to ripple in Tx-SAW-filter, the
output level on Secondary Inbound carrier may be +/– 1 dBm, compared to the Primary
Inbound carrier. Therefore, the Tx-Detector will normally only
be fetched when packets are
sent on Primary Inbound carrier – and the configured output level is applied to the Primary
Inbound carrier.
Note 4: A Slave-HUB in “Multi Inbound Link” (MIL) network (see
PHL_TX_RT_FREQUENCY_2)
cannot transmit. CCU Ver >= 30.8.0 will then always set
GAIN_TX_REF = 1.0 (disable
AGC) when it’s booting.
ERROR 1:
GAIN_TX_REF should always be 1.0 (disable AGC) when CCU Ver >= 30.6.0 is
used together with COREAPP Ver <= 2.1.1 (i.e. Release <= 3.1.0). Otherwise, software
incompatibility could cause BUC and/or LNB to be turned OFF, and unit will reboot after
some time.
ERROR 2:
GAIN_TX_REF should preferable be 1.0 (disable AGC) when CCU Ver 31.0.0 or
31.0.1 is used together with DSP Ver <= 2.3.1 (i.e. Release <= 3.5.0). Otherwise, an
“Invalid Detector Sample” message will be issued each second.
3.7.2 GAIN_TX_OVERRIDE
Default 0, Range 0…4095
Set Tx-Gain DAC value.
Value Description
0 Don’t set Tx-Gain DAC. Keep value defined in “hw.conf”.
1 … 4095
Set Tx-Gain DAC to initial value. The setting will be refreshed:
• On HUB: When HUB is starting to search for own carrier.
•
On RT: When HUB carrier is found.
Note: A Slave-HUB in “Multi Inbound Link” (MIL) network (see
PHL_TX_RT_FREQUENCY_2)
cannot transmit. CCU Ver >= 30.8.0 will then always set
GAIN_TX_OVERRIDE = 1 (very low
output) when it’s booting.