1. Manuals
  2. Brands
  3. TSAT Manuals
  4. Microphone system
  5. 3000
  6. User manual

TSAT 3000 User Manual

Telemetry and data transfer via satellite
Hide thumbs
Table of Contents

Advertisement

Quick Links

Product: DOC3000X, Revision: 23
Telemetry and data transfer via SATellite
TSAT 3000 User Guide
Hub Station and Remote Terminal
Configuration Parameter (MIB) Description
C30.0.0 – C31.9.0
January 2013

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 3000 and is the answer not in the manual?

Questions and answers

Summary of Contents for TSAT 3000

  • Page 1 Product: DOC3000X, Revision: 23 Telemetry and data transfer via SATellite TSAT 3000 User Guide Hub Station and Remote Terminal Configuration Parameter (MIB) Description C30.0.0 – C31.9.0 January 2013...
  • Page 2 TSAT 3000 - Telemetry and data transfer via SATellite Document Status Product description: Hub Station and Remote Terminal Configuration Parameter Description Revision Date CCU Ver Reason for change 2007.11.01 30.1.1 First Revision. 2008.02.12 30.2.0 Changed UTL_UTILITY_MASK (UTILITY_CCU_LISTEN_TO_CCU DAC_TCXO_REF DAC_OCXO_REF Changed...
  • Page 3 TSAT 3000 - Telemetry and data transfer via SATellite 2008.12.01 30.6.0 Included “Named Destination” to all MIB parameters. ( PDF lookup Described to other HUBs) PORT_TYPE SERVICE Described to other HUBs) SOCK_TYPE SOCK_NMS Changed (Implemented this function) GAIN_TX_REF Changed (0 = default)
  • Page 4 TSAT 3000 - Telemetry and data transfer via SATellite 2009.07.30 31.0.1 Described (new calculation) DAC_{TCXO | OCXO}_REF (LNB impedance mismatch?) SWITCH_RX_10MHZ_DELAY (LNB impedance mismatch?) SWITCH_RX_LNB_POWER_DELAY 2009.12.02 31.1.0 Described >= 3.2.1) IP_LINGER_FTP KERNEL Described (DSP >= 2.0.1) PHL_SLOT_PHASE_MODE Described (RT DSP >= 2.3.1)
  • Page 5 TSAT 3000 - Telemetry and data transfer via SATellite 2012.08.16 31.8.0 (Slot Request and Reservation) MAC_SLOT_REQ_RSV_SOURCE Described (Source of data) MAC_SLOT_REQ_RSV Described (Ref PORT_PRIORITY PORT_OPTIONS Changed PORT_OPTIONS OPTION_PRIORITY_FIXED (App T.O. => Switch HUB) PORT_SWITCH_TIMEOUT Descr (Ref PHL_SWITCH_BACK_TO_MAIN_HUB PORT_SWITCH_TIMEOUT Descr (Ref...
  • Page 6 TSAT 3000 - Telemetry and data transfer via SATellite Documentation Comment Form TSAT AS encourages you to comment on the documentation supplied with our products. This information helps us to provide quality products to meet your needs. Edition Date: January 2013...

  • Page 7: Table Of Contents

    TSAT 3000 - Telemetry and data transfer via SATellite Table of contents 1. SCOPE................................11 2. GENERAL ............................... 11 3. MIB PARAMETER DESCRIPTION......................12 3.1 PORT PARAMETERS ............................ 12 3.1.1 PORT_MAX_PORTS..........................13 3.1.2 PORT_TYPE [n] ............................13 3.1.3 PORT_USE_SOCKET [n] ........................14 3.1.4 PORT_USE_COM [n] ..........................
  • Page 8 TSAT 3000 - Telemetry and data transfer via SATellite 3.5 ADC + DAC PARAMETERS.......................... 47 3.5.1 ADC_SAMPLE_COUNT.......................... 48 3.5.2 ADC_{1 | 2 | 3 | 4 | 5 | 6 | 7 | 8}_XXX...................... 48 3.5.3 DAC_{11 | 12 | 13 | 14 | 21 | 22 | 23 | 24}_XXX..................48 3.5.4 DAC_{TCXO | OCXO}_REF ........................
  • Page 9 TSAT 3000 - Telemetry and data transfer via SATellite 3.11 PHYSICAL LAYER PARAMETERS......................74 3.11.1 PHL_{OUTBOUND | INBOUND}_SYMBOLRATE ................74 3.11.2 PHL_{OUTBOUND | INBOUND}_MODULATION................74 3.11.3 PHL_{OUTBOUND | INBOUND}_FECRATE ..................75 3.11.4 PHL_{OUTBOUND | INBOUND}_FECTYPE..................75 3.11.5 PHL_{OUTBOUND | INBOUND}_FILTERTYPE ................76 3.11.6 PHL_{OUTBOUND | INBOUND}_FILTERALFA ................
  • Page 10 TSAT 3000 - Telemetry and data transfer via SATellite 3.15 UTILITY PARAMETERS .......................... 108 3.15.1 UTL_LOG_SIZE ..........................108 3.15.2 UTL_LOG_SAVE_INTERVAL ......................108 3.15.3 UTL_TASK_TIMEOUT........................108 3.15.4 UTL_MIRROR_CHANNEL........................109 3.15.5 UTL_{OUTBOUND | INBOUND}_PREFIX_BYTE ................110 3.15.6 UTL_DEBUG_MASK .......................... 111 3.15.7 UTL_DEBUG_MASK_B ........................113 3.15.8 UTL_DEBUG_IPC_MASK ........................

  • Page 11: Scope

    The purpose, and legal values, of each parameter is described. 2. GENERAL Unless otherwise stated, all MIB parameters described here are present in the TSAT 3000 CCU software versions C30.0.0 to C31.9.0. Generally, unless otherwise stated by some of the qualifiers...

  • Page 12: Mib Parameter Description

    = n/a USE_COM = n/a SOCKET 1 IP-STACK TYPE = TSAT_NMS Connect PORT 7, 8 and 9 to Remote COM 10, 11 and 12 at “TSAT Comport Server” PORT 7 PORT 8 PORT 9 TYPE = SERVICE TYPE = STREAM...

  • Page 13: Port_Max_Ports

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.1 PORT_MAX_PORTS Default 4, Range 1…64 Set number of PORTs. 3.1.2 PORT_TYPE [n] Default 0, Range 0…4 Set Type of data on this PORT. Value Mnemonic Description NONE Closed. Raw byte stream data. The input bytes are transferred STREAM transparently through the TSAT network.

  • Page 14: Port_Use_Socket [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.3 PORT_USE_SOCKET [n] Default 0, Range 0…32 Set SOCKET connection to this PORT. Usage is dependent on PORT_TYPE [n] Value Description PORT_TYPE [n] NONE Not Used when PORT is Closed. NETWORK Not Used when PORT is connected to IP-STACK.

  • Page 15: Port_Bit_Rate [N]

    Set Baud-Rate [bits / second]. • Not Used when PORT is connected to SOCKET or IP-STACK. • Used when PORT is connected to Local-COM, or Remote-COM via “TSAT Comport Server”. Note: Minimum Local-COM Baud-Rate is dependent on KERNEL version: KERNEL version Minimum Baud-Rate <= 3.2.1 –...

  • Page 16: Port_Parity [N]

    3.1.8 PORT_PARITY [n] Default 0, Range 0…2 Set Parity • Not Used when PORT is connected to SOCKET or IP-STACK. • Used when PORT is connected to Local-COM, or Remote-COM via “TSAT Comport Server”. Value Description NO parity EVEN parity ODD parity 3.1.9 PORT_FLOW_CTRL [n]...

  • Page 17: Port_Priority [N]

    STREAM ADAPTER NETWORK Received User-Data packet is assigned the , and this priority will follow the PORT_PRIORITY packet through the TSAT network, until it’s sent to a PORT. Value Description Note Very LOW priority LOW priority LOW priority in NMS is mapped (by NMS) to Priority 3.

  • Page 18: Port_Pkt_Timeout [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.11 PORT_PKT_TIMEOUT [n] Default 100, Range –1…5000 Set packet Timeout on this PORT, expressed in milliseconds. Usage is dependent on PORT_TYPE [n] Value Description PORT_TYPE [n] NONE Not Used when PORT is Closed.

  • Page 19: Port_Forward_Char [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.12 PORT_FORWARD_CHAR [n] Default –1, Range –1…255 (0xFF) Define the ASCII character that shall force an immediate sending of data (including the forward character) from this PORT. Usage is dependent on...

  • Page 20: Port_Max_Pkt_Size [N]

    Note 2: DATA-SIZE is defined to be the maximum number of User-Data bytes available in a Satellite-Link packet. I.e. – “TSAT Header”. The PKT_OUTBOUND_SIZE PKT_INBOUND_SIZE size of “TSAT Header” can be from 5 to 15 bytes, depending on several MIB parameters: • PKT_OUTBOUND_SIZE 1 or 2 bytes Data-Size. • PKT_INBOUND_SIZE 1 or 2 bytes Data-Size.

  • Page 21: Port_Tx_Queue_Size [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.14 PORT_TX_QUEUE_SIZE [n] Default 2000, Range 1000…65535 Sets max number of bytes that may be (temporary) stored in the connected INTERFACE – waiting for transmission to Application. Data can be received from satellite link faster that the COM or SOCKET interface is able to send them to Application.

  • Page 22: Port_Reply_Timeout [N]

    Application-Equipment (AE). When the other communication path is much faster than TSAT, the AE could be polled more often and would also reply more often. When reply is feed to both communication paths, TSAT RT would sent all these replies to HUB and possible saturate the inbound link.

  • Page 23: Port_Switch_Timeout [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.16 PORT_SWITCH_TIMEOUT [n] Default 0, Range 0…3600 Ver <= 31.7.1: Not Implemented. HUB Ver >= 31.8.0 Not Used RT Ver >= 31.8.0 The “Switch Timeout” facility is controlled by this MIB parameter, and is enabled for...

  • Page 24: Port_Options [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.17 PORT_OPTIONS [n] Default 0, Range 0…255 (0xFF) Bit field to control miscellaneous PORT options. Mask Mnemonic Description Version 0x01 0x02 Disable dynamic priority allocation. >= 31.8.0 0x04 PRIORITY_FIXED Enable Priority Send-Queue mechanisms.
  • Page 25 TSAT 3000 - Telemetry and data transfer via SATellite LOOP When enabled, data received from the satellite link and sent to PORT, will be (software) looped within the PORT module, and handled as it was received from the INTERFACE (i.e. sent back to satellite link and the other (remote) network node).

  • Page 26: Port_Stream_Rt [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.18 PORT_STREAM_RT [n] Default –1, Range –1…12287 (0x2FFF) • Not Used when PORT_TYPE [n] SERVICE In this case, RT-Address is included in received packets from NMS. • Used when PORT_TYPE [n]...
  • Page 27 TSAT 3000 - Telemetry and data transfer via SATellite • HUB RT Leased Line HUB: = RT, BROADCAST, GROUP or CLUSTER. PORT_STREAM_RT = PORT(s) at RT. PORT_STREAM_RT_PORT = HUB. PORT_STREAM_RT = Don’t care. PORT_STREAM_RT_PORT Ver <= 30.1.1: Leased Line to GROUP or CLUSTER doesn’t work correctly.

  • Page 28: Port_Stream_Rt_Port [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.19 PORT_STREAM_RT_PORT [n] Default 1, Range 1…255 • Not Used when PORT_TYPE [n] SERVICE In this case, RT-Port is included in received packets from NMS. • Used when PORT_TYPE [n] STREAM...

  • Page 29: Port_Max_Appl_Retries [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.1.20 PORT_MAX_APPL_RETRIES [n] Default 0, Range 0…64 The “Secure Link Facility” is enabled (for all data received from this PORT) by setting greater than zero. This sets the maximum number of attempts to...

  • Page 30: Socket Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.2 SOCKET PARAMETERS Define SOCKETs used for communication to/from this Main-Unit. The type of data on this SOCKET is defined by • SOCK_TYPE [n] … while Transport-Protocol and type of SOCKET is defined by: •...

  • Page 31: Sock_Max_Sockets

    TSAT 3000 - Telemetry and data transfer via SATellite 3.2.1 SOCK_MAX_SOCKETS Default 4, Range 1…32 Set number of SOCKETs. 3.2.2 SOCK_TYPE [n] Default 0, Range 0…3 Set Type of data on this SOCKET. Value Mnemonic Description NONE Closed. Raw byte stream data. The input bytes are transferred RAW_DATA transparently to the connected PORT.

  • Page 32: Sock_Local_Port [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.2.5 SOCK_LOCAL_PORT [n] Default 4000, Range 0…65535 Set LOCAL-PORT associated with this SOCKET. SOCK_ Type of Socket LOCAL_ Description PORT TCP Server Socket Wait for incoming connection to this < >.

  • Page 33: Sock_Options [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.2.7 SOCK_OPTIONS [n] Default 0, Range 0…255 (0xFF) Bit field to control miscellaneous SOCKET options. Mask Mnemonic Description Version 0x01 Detect dead TCP connections. TCP_KEEPALIVE Delay and merge small TCP segments.
  • Page 34 TSAT 3000 - Telemetry and data transfer via SATellite LOOP When enabled, data received from the satellite link and sent to SOCKET, will be (software) looped within the SOCKET module, and handled as it was received from the IP-STACK (i.e. sent back to PORT and the other (remote) network node).

  • Page 35: Sock_Idle_Timeout [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.2.8 SOCK_IDLE_TIMEOUT [n] Default 10, Range 0…3600 Set the Idle-Timeout (in seconds). Value Description NO Timeout. Idle Timeout in seconds. A timer will be re-started each time data is received from the SOCKET.

  • Page 36: Com Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.3 COM PARAMETERS Define COM Ports used for communication to/from this Main-Unit. 3.3.1 COM_MAX_COMS Default 2, Range 0…8 Set number of Local-COMs. I.e. COM ports on this Main-Unit. Note: The current COM-Driver does only support two COM ports, and you’ll not be allowed to Open COM [3 …8].

  • Page 37: Com_Signal_Out [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.3.3 COM_SIGNAL_OUT [n] Ver <= 30.7.0: Default 0, Range 0…3 Ver >= 30.8.0: Default 0, Range 0…5 Ver <= 30.7.0 Not Used. Ver >= 30.8.0 The state of COM’s DSR output signal (pin 6) is controlled by this parameter.

  • Page 38: Com_Signal_Data_Delay [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.3.4 COM_SIGNAL_DATA_DELAY [n] Default 0, Range 0…60000 Ver <= 30.7.0 Not Implemented. Ver >= 30.8.0 Controls the timing of COM’s DSR output signal (pin 6) when is 4 or 5. COM_SIGNAL_OUT [n]...

  • Page 39: Com_Options [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.3.6 COM_OPTIONS [n] Default 0, Range 0…255 (0xFF) Bit field to control miscellaneous COM options. Mask Mnemonic Description Don’t Close+Open COM when too many errors are 31.0.0 0x01 KEEP_OPEN rx’ed. Ignore Parity-, Framing- and Overrun-errors.

  • Page 40: Ip Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.4 IP PARAMETERS 3.4.1 IP_ADDRESS_{ETH1 | ETH2 | SAT} Default <nothing> Ver <= 30.1.1 Set IP-ADDRESS of Ethernet-A, Ethernet-B and Satellite interfaces. Note: These MIB parameters are only partly implemented: • You may read and change FILE value, but this will have no effect. The Main-Unit will always boot with values defined in “system.conf”.

  • Page 41: Ip_Address_{Lana | Lanb | Sat

    TSAT 3000 - Telemetry and data transfer via SATellite 3.4.3 IP_ADDRESS_{LANA | LANB | SAT} Default <nothing> Ver <= 30.1.1 Not Implemented. Ver >= 30.2.0 Set IP-ADDRESS and SUBNET-MASK of Ethernet-A, Ethernet-B and Satellite interfaces. You define both IP Address and Network Mask by a single MIB parameter, and it’s also possible to specify a default IP Address and Network Mask which will generate unique IP Addresses for HUB and all RTs in a satellite network.
  • Page 42 TSAT 3000 - Telemetry and data transfer via SATellite <mask2>: Same interpretation as <mask>. This <mask2> is only applicable when CCU is going to generate default IP Address for the interfaces. CCU will use default LANA LANB Network Mask2 when <mask2> is omitted: 0xFFFFFFF8 (i.e. 29 bits).
  • Page 43 TSAT 3000 - Telemetry and data transfer via SATellite Some examples may clarify how CCU will generate default IP Addresses: Default Network Address, Network Mask and Network Mask-2 LANA LANB Applied at Node 192.168.0.1 / 29 192.168.0.9 / 29 10.0.255.1 / 16 0.0.0.0 / 0...

  • Page 44: Ip_Route [N]

    TSAT 3000 - Telemetry and data transfer via SATellite 3.4.4 IP_ROUTE [n] Default <nothing> Ver <= 30.1.1 Not Used. Ver >= 30.2.0 The MIB parameters were defined in older CCU versions, but had no effect. IP_ROUTE [1…64] The maximum numbers of...
  • Page 45 TSAT 3000 - Telemetry and data transfer via SATellite <mask>: The Network Mask is also a 32 bit unsigned integer, with the restriction that all upper bits should be “1”, while all lower bits should be “0”. Normally, you just specify the number of upper “1” bits. Ex: “24”. However, it’s also possible specify <number>...

  • Page 46: Ip_Linger_Ftp

    TSAT 3000 - Telemetry and data transfer via SATellite 3.4.5 IP_LINGER_FTP Default 60, Range –1…120 Ver <= 30.6.1 Not Implemented. Ver >= 30.7.0 + KERNEL >= 3.2.1 This MIB is defining a timeout parameter of the local FTP server. It will set the maximum time from the FTP server has sent the last data-packet, until the ftp-data-socket will be closed.

  • Page 47: Adc + Dac Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.5 ADC + DAC PARAMETERS Main-Unit is equipped with 8 D/A-Converters ( ) and 8 A/D-Converters ( CYAN YELLOW LNB Voltage BUC Voltage LNB Current BUC Current 950 - 1450 Tx-RF Level...

  • Page 48: Adc_Sample_Count

    TSAT 3000 - Telemetry and data transfer via SATellite 3.5.1 ADC_SAMPLE_COUNT Default 1, Range 1…100 Used when the operator fetch a measurement from one of onboard A/D-Converters: ADC_{1 | 2 | . The A/D-Converter will be read the specified number of times, and the 3 | 4 | 5 | 6 | 7 | 8}_XXX average value returned.

  • Page 49: Dac_{Tcxo | Ocxo}_Ref

    TSAT 3000 - Telemetry and data transfer via SATellite 3.5.4 DAC_{TCXO | OCXO}_REF Default 0, Range 0…17391 Change these MIBs to modify the default TCXO and/or OCXO Oscillator settings defined in “hw.conf”, or just read-back CURRENT value. Ver <= 30.1.1 Not Implemented Ver >= 30.2.0:...

  • Page 50: Switch Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.6 SWITCH PARAMETERS Main-Unit is equipped with a number of switches to control miscellaneous functions. 3.6.1 SWITCH_{RX | TX}_XXX Default 0, Range 0…1 – Volatile Ver <= 30.3.1 Not Implemented. Ver >= 30.4.0 You can both read and write the CURRENT value of all onboard switches.

  • Page 51: Gain Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.7 GAIN PARAMETERS Rx/Tx Gain is controlled by reading onboard A/D-Converters, and writing to the onboard D/A- Converters. See description of MIB parameters below, and ADC + DAC PARAMETERS 3.7.1 GAIN_TX_REF Ver <= 30.4.1: Default 0.0, Range –50.0…...

  • Page 52: Gain_Tx_Override

    TSAT 3000 - Telemetry and data transfer via SATellite 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 –...

  • Page 53: Gain_Tx_End2End_Target

    TSAT 3000 - Telemetry and data transfer via SATellite 3.7.3 GAIN_TX_END2END_TARGET Default 0.0, Range 0.0 + 6.0…20.0 Control the “End-to-End Tx-Gain” facility. Value Description Disable “End-to-End Tx-Gain” facility. 6.0 … 20.0 Enable “End-to-End Tx-Gain” facility. When enabled, the Tx-Gain DAC is adjusted in small steps until the measured Receive-Level ) at the remote side is equal [dB].

  • Page 54: Gain_Tx_Dac_{Min | Max

    TSAT 3000 - Telemetry and data transfer via SATellite 3.7.4 GAIN_TX_DAC_{MIN | MAX} MIN: Default 1000, Range 0…4095 MAX: Default 3000, Range 0…4095 Control the “Automatic Tx-Gain” and “End-to-End Tx-Gain” facilities. Defines the minimum and maximum value of Tx-Gain DAC when one of these facilities are enabled ( <...

  • Page 55: Link Layer Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.8 LINK LAYER PARAMETERS Overview of CCU Transmission- and Send-Queues: TX to Satellite RX from Satellite Secure-Link RX Queue Priority Acknowledge Transmission Queue Queue Packetizer RX Queue MANAGEMENT Retransmission Queue ROUTE...
  • Page 56 TSAT 3000 - Telemetry and data transfer via SATellite Acknowledge Queue Sent Secure-Link packets are temporary stored in this queue, and removed when acknowledge from remote unit is received. Timeout (or request for retransmission) will make a copy of packet and put in Retransmission-Queue.

  • Page 57: Lcc_Tx_Que_Size

    TSAT 3000 - Telemetry and data transfer via SATellite 3.8.1 LCC_TX_QUE_SIZE Default 40, Range 10…250 Set the maximum number of packets that may be stored in the satellite link Transmission-Queue before transmission. Note: The flow control of COM ports (...

  • Page 58: Lcc_Window_Size

    TSAT 3000 - Telemetry and data transfer via SATellite 3.8.3 LCC_WINDOW_SIZE Default 16, Range 2…4096 HUB: Set the maximum number of satellite link packets that may be outstanding before acknowledge from the remote side is required. The packet sequence numbering is used in conjunction with the “Secure Link Facility”.

  • Page 59: Lcc_Max_Link_Retries

    TSAT 3000 - Telemetry and data transfer via SATellite 3.8.4 LCC_MAX_LINK_RETRIES Default 5, Range 0…255 Set the maximum number of attempts to retransmit a packet. LINK_RESET The retransmission timeout is defined by LCC_{MIN | MAX}_RESET_RETRANS_DELAY Value Description HUB will never stop retransmitting packets to RTs.

  • Page 60: Lcc_Management_Priority

    TSAT 3000 - Telemetry and data transfer via SATellite 3.8.6 LCC_MANAGEMENT_PRIORITY Default 7, Range 0…7 Set the default priority of packets containing Management-Data. Some Management packets may use other priorities. Note: For the moment, all Management-Data packets are assigned hardcoded priority 7.

  • Page 61: Media Access Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.9 MEDIA ACCESS PARAMETERS 3.9.1 MAC_TIMESLOTS_IN_FRAME Default 16, Range 2…240 HUB: Sets the number of Media Access timeslots in a frame. Note: When HUB is connected to NMS, this MIB variable will be replaced by the value configured in the NMS ‘Static Slot Access Schemes’...

  • Page 62: Mac_Slot_Map_{0 | 1 | 2 | 3

    TSAT 3000 - Telemetry and data transfer via SATellite 3.9.4 MAC_SLOT_MAP_{0 | 1 | 2 | 3} MAP 0: Default 3, Range 0…7 – Array of Bytes MAP 1: Default 5, Range 0…7 – Array of Bytes MAP 2: Default 3, Range 0…7 – Array of Bytes MAP 3: Default 5, Range 0…7 –...

  • Page 63: Mac_Slot_Map_Port

    TSAT 3000 - Telemetry and data transfer via SATellite Ver == 30.0.0 In addition to access granted by current Access-Scheme, the next slot after receiving packets are reserved to the polled RT. It will always reply with SYNC POLL POLL_ACK or other packet if any packets waiting for transmission.

  • Page 64: Mac_Slot_Req_Rsv

    Inbound slots to those RTs that (for a short or longer time) are in need of higher inbound throughput. The operation is very much like the 2100/50 implementation of this facility, and will also function when 3000 modem is operating in 2150-Compatibility mode. You can apply default configuration: • 0 = disable •...
  • Page 65 TSAT 3000 - Telemetry and data transfer via SATellite When enabled on the HUB, it will reserved (default 8) number of slots to this RT SRR_SLOTS each time it receives a request for Inbound slots. Maximum (default 8) RTs can...
  • Page 66 TSAT 3000 - Telemetry and data transfer via SATellite RT Configuration Bits Field Value Mnemonic Description SRR_PACKETS 0 – 7 0x0000.00FF 0 – 255 The transmit queue threshold value. I.e. the RT will request Inbound slots whenever it is sending an Application- or Management-...
  • Page 67 TSAT 3000 - Telemetry and data transfer via SATellite HUB Configuration Bits Field Value Mnemonic Description 0 – 6 0x0000.007F 0 – 100 SRR_PERCENT 0, 1 (default) => value 50 [%]. When is FALSE, the HUB will SRR_FIXED maximum allocate...

  • Page 68: Mac_Slot_Req_Rsv_Source

    TSAT 3000 - Telemetry and data transfer via SATellite 3.9.7 MAC_SLOT_REQ_RSV_SOURCE Default 0, Range 0…255 (0xFF) Ver <= 31.7.1 Not Implemented HUB Ver >= 31.8.0 Not Used RT Ver >= 31.8.0 This parameter controls which kind of packets that can request the “Slot Request and Reservation”...

  • Page 69: Mac_Timeslot_Length

    DSP is sending the packet on the satellite link. Normally, it’s recommended to use a value of approx. 3000 micro-seconds, as this will give the CCU a fair change to process the request for Tx-Data, and send them to DSP, in good time before packet is sent on the satellite link.

  • Page 70: Network Parameters

    See also PORT_STREAM_RT [n] PHL_SLOT_PHASE_MODE POW_WAKEUP_FIRST_TIME 3.10.3 NET_NAME Default <nothing> Ver <= 30.2.0 Not Implemented Ver >= 30.3.0 Null-terminated text string (max 64 char), identifying the TSAT Main Unit. TSAT 3000 Configuration Parameter Description, January 2013 Page 70 of 124...

  • Page 71: Net_{First | Start | Last}_Poll_Rt

    TSAT 3000 - Telemetry and data transfer via SATellite 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 .

  • Page 72: Net_Max_Poll_Seconds

    TSAT 3000 - Telemetry and data transfer via SATellite 3.10.5 NET_MAX_POLL_SECONDS Default 120, Range 30…3600 HUB: Number of seconds the HUB will search for an RT (without being able to get in-lock), before HUB is starting to poll the next RT. See...

  • Page 73: Net_Groups [1

    TSAT 3000 - Telemetry and data transfer via SATellite 3.10.6 NET_GROUPS [1…5] Default 0, Range 0…100 HUB: Not Used. Sets the GROUP information of an RT. An RT may belong to maximum 5 Groups, and each GROUP address may be in the range 1...100. Default is zero. I.e. None GROUPs.

  • Page 74: Physical Layer Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11 PHYSICAL LAYER PARAMETERS 3.11.1 PHL_{OUTBOUND | INBOUND}_SYMBOLRATE Default 64000, Range 300…512000 Set Symbol-Rate for Outbound carrier. PHL_TX_HUB_FREQUENCY Set Symbol-Rate for Inbound carrier. PHL_TX_RT_FREQUENCY Note: DSP will be restarted 10 seconds after you’ve changed CURRENT value.

  • Page 75: Phl_{Outbound | Inbound}_Fecrate

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.3 PHL_{OUTBOUND | INBOUND}_FECRATE Default 4, Range 1…5 Set FEC-Rate for Outbound carrier. PHL_TX_HUB_FREQUENCY Set FEC-Rate for Inbound carrier. PHL_TX_RT_FREQUENCY Value Description None 7 / 8 3 / 4 1 / 2 1 / 3 Note: DSP will be restarted 10 seconds after you’ve changed CURRENT value.

  • Page 76: Phl_{Outbound | Inbound}_Filtertype

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.5 PHL_{OUTBOUND | INBOUND}_FILTERTYPE Default 1, Range 1…3 Set Filter-Type for Outbound carrier. PHL_TX_HUB_FREQUENCY Set Filter-Type for Inbound carrier. PHL_TX_RT_FREQUENCY Value Description Flat Note: DSP will be restarted 10 seconds after you’ve changed CURRENT value.

  • Page 77: Phl_In_Out_Packet_Ratio

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.8 PHL_IN_OUT_PACKET_RATIO Default 1, Range 1…64 Set the ratio between Inbound and Outbound packets. I.e. the RTs may be told to send several packets to HUB (inbound) for each packet they receive from HUB (outbound).

  • Page 78: Phl_Slot_Phase_Mode

    There is no need to wait for the retransmission timer to expire. • Make it easier for the RT to log into the TSAT network after a restart (when there is a lot of Inbound traffic from the other RTs).
  • Page 79 “Pulse Position Reservation Facility”, at least on the Inbound link. (It is not necessary on the Outbound link). Otherwise, the TSAT network cannot guarantee the correct reception- order of Inbound packets from the RTs. Packets may also be lost due to collisions (or other reasons), even though most of the collided packet will be retransmitted by the PPR protocol.
  • Page 80 TSAT 3000 - Telemetry and data transfer via SATellite STRATEGY: HUB: Not Used. Define the position at which packets are to be transmitted to HUB. Normally, 0 or 1 is used. Other values are used to test PPR functionality. STRATEGY 0: Send packet in random position (0 …...
  • Page 81 TSAT 3000 - Telemetry and data transfer via SATellite RESERVED 1 and 2: Reserved for future usage. Should always be zero. Using the “PPR Facility” will affect the size of Outbound and Inbound data packets: Whenever slots are reserved to RTs (and RTs requested to retransmit), the number of bytes...

  • Page 82: Phl_Slot_Phase_Setpoint

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.11 PHL_SLOT_PHASE_SETPOINT Default 0, Range –32768…+32767 The MIB parameter is expressed in micro-seconds (i.e. range is +/– 32 ms). HUB: Not Used. RT: The Slot Phase Setpoint is used to specify the point of time at which the DSP shall start the transmission of a slot.

  • Page 83: Phl_Slot_Phase_Delay

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.12 PHL_SLOT_PHASE_DELAY Default –1, Range –1…64 HUB: Not Used. RT: In networks with small and RTs located very far away from each MAC_TIMESLOT_LENGTH other, it might be necessary to delay the sending from RTs one or more slots. The Access-...

  • Page 84: Phl_Target_Uw_Position

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.13 PHL_TARGET_UW_POSITION Default –1, Range –1…10.000.000 The MIB parameter is expressed in micro-seconds (i.e. range is 0…10 seconds). HUB: Used by the Slot Phase Setpoint Auto-Correction facility. The UW position (received from DSP) defines the point of time at which the HUB receives packets from RTs.

  • Page 85: Phl_{Outbound | Inbound}_Identity

    These identifiers must be set alike for the HUB and all RTs using the same carriers. They are used to prohibit the HUB and RTs to lock to a carrier of another TSAT system with frequencies within its search range.

  • Page 86: Phl_Tx_Hub_Frequency

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.18 PHL_TX_HUB_FREQUENCY Ver <= 30.4.1: Default 14.239.875, Range 14.000.000…14.500.000 Ver >= 30.5.0: Default 14.240.100, Range 5.000.000…14.500.000 Set the HUB TX frequency in kHz. Note: DSP will be restarted 10 seconds after you’ve changed CURRENT value.

  • Page 87: Phl_Tx_Rt_Frequency_2

    TSAT 3000 - Telemetry and data transfer via SATellite 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.
  • Page 88 Normally, PORT [4] is SERVICE, and is using SOCKET [1]. This is normally a TSAT_NMS Socket, using TCP/IP and Listening at local IP-port 4000. This Socket is normally used to connect the NMS to TSAT 3000 Main-Unit, but may also be used to establish connections between TSAT 3000 Main-Units.
  • Page 89 TSAT 3000 - Telemetry and data transfer via SATellite Configure Hardware – “hw.conf” The Slave-HUBs should be configured to not apply Power and 10 MHz reference to BUC and LNB. Disable (i.e. parameter value “no”) the following parameters in “hw.conf” configuration file: •...

  • Page 90: Phl_Tx_Rt_Frequency_2_Bkup

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.23 PHL_TX_RT_FREQUENCY_2_BKUP Ver <= 30.4.1: Default 0, Range 0 + 14.000.000…14.500.000 – No-Current Ver >= 30.5.0: Default 0, Range 0 + 5.000.000…14.500.000 – No-Current Set the Backup Secondary Inbound carrier [kHz] in a Redundant Multi-Inbound-Link (MIL) network.

  • Page 91: Phl_Tx_Frequency_Adjust

    RT is reported UP (i.e. is included in the poll-cycle for more than 10 poll-cycles). The HUB is selecting the Reference-RT after the following criteria: 1) Preferable the first TSAT 3000, or 2100 RT with DSP version <= P22.4.0, in poll-cycle is selected, because such RTs cannot adjust frequency.

  • Page 92: Phl_Tx_Frequency_Adjust_Bkup

    TSAT 3000 - Telemetry and data transfer via SATellite Debugging A) Messages: Some debug information is issued when you enable bit 22 or 23 (0xC0.000) in UTL_DEBUG_MASK_B • Bit 22 – 0x40.000 – – Receiving packet from RT. DEBUG_TX_FREQUENCY_ADJUST_RX_2150 • Bit 23 – 0x80.000 –...

  • Page 93: Phl_Switch_Back_To_Main_Hub

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.26 PHL_SWITCH_BACK_TO_MAIN_HUB Default 60, Range –1…10080 The “Auto RT Switch-Back to Main Hub” function is controlled by an option in NMS ‘Network Behaviour’ window. This parameter controls the RT behaviour when this option is enabled.

  • Page 94: Phl_Switch_Slave_Hub_Timeout

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.27 PHL_SWITCH_SLAVE_HUB_TIMEOUT Default 60, Range –1…86400 In a Redundant Multi Inbound Link (MIL) network, the RT may also switch between Main- and Backup-HUBs when it detects that the (current) Slave-HUB is DOWN. This function is controlled by this parameter.

  • Page 95: Phl_Delta_Search_Frequency

    TSAT 3000 - Telemetry and data transfer via SATellite 3.11.28 PHL_DELTA_SEARCH_FREQUENCY Ver <= 30.5.0: Default 60, Range 10…1000 Ver >= 30.6.0: Default 0, Range 0 + 10…1000 Half the frequency search range, expressed in kHz. The frequency search range should at least be some kHz larger than occupied bandwidth.

  • Page 96: Phl_Sat_Convert_Frequency

    Ver >= 30.5.0: Default 11.300.000, Range 2.000.000…16.000.000 Set the RX (LNB) Local Oscillator frequency [kHz]. The MIB value must match the connected LNB. Currently the following LNBs are used with TSAT 3000 Main Unit: [kHz] LNB – TSAT Part No...

  • Page 97: Packet Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.12 PACKET PARAMETERS 3.12.1 PKT_MAX_SIZE Ver <= 30.3.1: Default 256, Range 100…2100 – BOOT Ver >= 30.4.0: Default 256, Range 256…2100 – BOOT Set the size of the CCU’s internal packet structure, and must at least be 60 bytes larger than (which defines the actual satellite Link packet size).

  • Page 98: Pkt_Inbound_Size

    TSAT 3000 - Telemetry and data transfer via SATellite 3.12.3 PKT_INBOUND_SIZE Read-Only Read the number of bytes in a satellite Link packet from RT to HUB. It is calculated after the restart of the Main Unit (and when any of DSP configuration parameters are changed), and is a function of: •...

  • Page 99: Power Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.13 POWER PARAMETERS Power-Save functions are implemented in Ver >= 31.1.0. By use of these functions, the RT may save a lot of power. Typical example with 2W Zinwell Ku-band BUC: •...

  • Page 100: Pow_Wakeup_First_Time

    TSAT 3000 - Telemetry and data transfer via SATellite 3.13.1 POW_WAKEUP_FIRST_TIME Ver <= 31.0.1: Default 0, Range –1… 1440 Ver >= 31.1.0: Default 0, Range 0…10080 Ver <= 31.0.1 Not Used. Ver >= 31.1.0 Controls SLEEP mode operation. Used when the Main-Unit Power-Save function is enabled by POW_WAKEUP_INTERVAL >= 2...

  • Page 101: Pow_Wakeup_Interval

    TSAT 3000 - Telemetry and data transfer via SATellite 3.13.2 POW_WAKEUP_INTERVAL Ver <= 31.0.1: Default 0, Range 0…10080 Ver >= 31.1.0: Default 0, Range 0, 2…10080 Ver <= 31.0.1 Not Used. Ver >= 31.1.0 The Main-Unit Power-Save SLEEP function is enabled when >= 2.

  • Page 102: Pow_Listen_Hpa_Mode

    Note: When LISTEN mode is enabled, the RT will generate +6 dB noise at frequency given by +/– 1.5 x PHL_TX_RT_ FREQUENCY PHL_INBOUND_SYMBOL_RATE This will not make any problems for nearby TSAT carriers, but could perhaps disturb other nearby carriers. Debugging: Some debug information is issued when bit 9 (0x0200 - ) in DEBUG_RT_POWER_SAVE is enabled.

  • Page 103: Pow_Listen_Hpa_On

    TSAT 3000 - Telemetry and data transfer via SATellite 3.13.5 POW_LISTEN_HPA_ON Ver <= 31.0.1: Default 0, Range 0… 255 Ver >= 31.1.0: Default 0, Range 0…2000 Ver <= 31.0.1 Not Used. Ver >= 31.1.0 HUB: Not Used. Controls LISTEN mode operation.

  • Page 104: Pow_Listen_Poll

    TSAT 3000 - Telemetry and data transfer via SATellite 3.13.7 POW_LISTEN_POLL Default 0, Range 0…255 Ver <= 31.0.1 Not Used. Ver >= 31.1.0 During the exchange of messages, the RT will request the HUB to be LINK_RESET LINK_ACK included or excluded from the regular polling of all RTs. Two polling schemes are...

  • Page 105: System Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.14 SYSTEM PARAMETERS 3.14.1 SYS_IS_HUB Default 0, Range 0…1 – BOOT Identifies the CCU as HUB or RT Value Description Note: You cannot change this parameter via satellite link, but must be connected locally.

  • Page 106: Sys_Version

    TSAT 3000 - Telemetry and data transfer via SATellite 3.14.5 SYS_VERSION Read-Only Contains the following Read-Only null-terminated text string, identifying the CCU software version: “Cxx.yy.zz” Field Description identifies the CCU software Main revision number: 30 . . . 99 Minor revision number: 0 .

  • Page 107: Sys_Licence

    TSAT 3000 - Telemetry and data transfer via SATellite 3.14.8 SYS_LICENCE Default 0, Range 0…0xFFFF.FFFF Ver <= 31.8.2: Not Implemented. RT Ver >= 31.9.0: Not Used. HUB Ver >= 31.9.0: is used to restrict or enable miscellaneous functions in the satellite network.

  • Page 108: Utility Parameters

    TSAT 3000 - Telemetry and data transfer via SATellite 3.15 UTILITY PARAMETERS 3.15.1 UTL_LOG_SIZE Default 100, Range 10…1000 3 Logs are maintained by the CCU: • Error Log – Containing all s that will cause CCU to FATAL_ERROR RESET • Warning Log – Containing all s and s issued by the CCU.

  • Page 109: Utl_Mirror_Channel

    TSAT 3000 - Telemetry and data transfer via SATellite 3.15.4 UTL_MIRROR_CHANNEL Ver <= 30.4.1: Default 0, Range 0…8 + 11…14 + 21…24 + 100 Ver == 30.5.0…31.0.1: Default 0, Range 0…8 + 11…14 + 21…24 + 100 + 101 Ver >= 31.1.0: Default 0, Range 0…8 + 11…14 + 21…24 + 100 + 101 + 102...

  • Page 110: Utl_{Outbound | Inbound}_Prefix_Byte

    TSAT 3000 - Telemetry and data transfer via SATellite 3.15.5 UTL_{OUTBOUND | INBOUND}_PREFIX_BYTE Default 0, Range 0…255 (0xFF) Ver == 30.0.0: Not Implemented. Ver >= 30.1.0: For debugging and measurement purposes, it’s possible to specify that all Outbound and/or Inbound packets should be prefixed with a specified byte-value.

  • Page 111: Utl_Debug_Mask

    TSAT 3000 - Telemetry and data transfer via SATellite 3.15.6 UTL_DEBUG_MASK Ver <= 30.4.1: Default 0x102D, Range 0…0xFFFF.FFFF Ver >= 30.5.0: Default 0x170F, Range 0…0xFFFF.FFFF Bit field to control the output of debugging messages. Mask Mnemonic Description Enable MSGs. Global enable/disable of all other...
  • Page 112 TSAT 3000 - Telemetry and data transfer via SATellite 0x0001.0000 MSG when Application is flow-controlled. DEBUG_FLOWCONTROL MSG from all Link Queues (stored packets + age). • Transmission priority queue • Secure-Link Acknowledge queue 0x0002.0000 DEBUG_LINK_QUEUES • Secure-Link Receive queue •...

  • Page 113: Utl_Debug_Mask_B

    TSAT 3000 - Telemetry and data transfer via SATellite 3.15.7 UTL_DEBUG_MASK_B Default 0x0000, Range 0…0xFFFF.FFFF Bit field to control the output of debugging messages. Ver <= 30.3.1: Not Implemented. Ver >= 30.4.0: Mask Mnemonic Description 0x0001 Ver >= 30.7.0: MSG IP packets rx’ed from IP-Stack.

  • Page 114: Utl_Debug_Ipc_Mask

    TSAT 3000 - Telemetry and data transfer via SATellite 3.15.8 UTL_DEBUG_IPC_MASK Default 0, Range 0…0xFF Bit field to control output of debugging messages from IPC Link (between CCU and DSP): Mask Mnemonic Description 0x01 0x02 MSG when receive DATA from DSP.

  • Page 115: Utl_Utility_Mask

    TSAT 3000 - Telemetry and data transfer via SATellite 3.15.11 UTL_UTILITY_MASK Default 0x21, Range 0…0xFFFF.FFFF Bit field to control miscellaneous (debugging) functions. Mask Mnemonic Description RT + HUB ver <= 30.4.1: Enable “Absolute Frequency Control”, so that RT will send at exact correct UTILITY_ frequency –...
  • Page 116 TSAT 3000 - Telemetry and data transfer via SATellite Disable most of the CCU safety mechanisms. 0x0100 UTILITY_TUT_OG_KJOR NET_MAX_POLL_SECONDS Ver >= 30.2.0: Cannot be enabled via satellite link. CCU will normally send necessary Link-Data to DSP, and DSP will then fill remaining part of packet with semi-random data before packet is sent to satellite.
  • Page 117 TSAT 3000 - Telemetry and data transfer via SATellite RT Ver >= 30.2.0: Enable adjustments of local TCXO. 0x0001.0000 UTILITY_ADJUST_TCXO DAC_{TCXO | OCXO}_REF CCU will normally discard false CRC errors detected by DSP. I.e. Not report CRC errors with E <...

  • Page 118: Utl_Utility_Search_Mask

    TSAT 3000 - Telemetry and data transfer via SATellite 3.15.12 UTL_UTILITY_SEARCH_MASK Ver <= 31.7.0 Default 0, Range 0…0xFFFF Ver == 31.7.1 Default 0, Range 0…0x0003.FFFF Ver >= 31.8.0 Default 0, Range 0…0x0007.FFFF Bit field to control the Spectrum search operation.
  • Page 119 TSAT 3000 - Telemetry and data transfer via SATellite Mask Mnemonic Description 3 bits control Spectrum read operation: • 0 – Normal operation. • 1 – Do nothing at all. • 2 – Read Spectrum forever. • 3 – Read Spectrum and Search forever.
  • Page 120 TSAT 3000 - Telemetry and data transfer via SATellite Mask Mnemonic Description Ver >= 31.7.1: Use the Spectrum-Decode function UTILITY_SEARCH_ as used in 31.6.0 … 31.7.0. This function doesn’t 0x0001.0000 TEST_BW always work well for 9600 carriers. HUB Ver >= 31.7.1: Accept OCXO drift 10Hz/sec.

  • Page 121: Mib Index Summary

    TSAT 3000 - Telemetry and data transfer via SATellite 4. MIB INDEX SUMMARY The MIB index and Qualifiers associated with each MIB parameter is shown in the table below. Changes from one software version to another are indicated by GRAY colour.
  • Page 122 TSAT 3000 - Telemetry and data transfer via SATellite 30.0.0 30.1.0 30.1.1 30.2.0 30.3.0 30.4.0 30.5.0 30.7.0 30.8.0 31.0.0 31.0.1 31.1.0 31.1.2 31.4.0 31.8.0 31.9.0 30.3.1 30.4.1 30.6.0 31.1.1 31.1.3 31.5.0 31.8.1 30.6.1 31.2.0 31.5.1 31.8.2 31.2.1 31.5.2 MIB PARAMETER...
  • Page 123 TSAT 3000 - Telemetry and data transfer via SATellite 30.0.0 30.1.0 30.1.1 30.2.0 30.3.0 30.4.0 30.5.0 30.7.0 30.8.0 31.0.0 31.0.1 31.1.0 31.1.2 31.4.0 31.8.0 31.9.0 30.3.1 30.4.1 30.6.0 31.1.1 31.1.3 31.5.0 31.8.1 30.6.1 31.2.0 31.5.1 31.8.2 31.2.1 31.5.2 MIB PARAMETER...
  • Page 124 TSAT 3000 - Telemetry and data transfer via SATellite 30.0.0 30.1.0 30.1.1 30.2.0 30.3.0 30.4.0 30.5.0 30.7.0 30.8.0 31.0.0 31.0.1 31.1.0 31.1.2 31.4.0 31.8.0 31.9.0 30.3.1 30.4.1 30.6.0 31.1.1 31.1.3 31.5.0 31.8.1 30.6.1 31.2.0 31.5.1 31.8.2 31.2.1 31.5.2 MIB PARAMETER...

Table of Contents