DEV 2194 (Manual) PDF

User Manual
DEV 2194
L-Band Distribution Amplifier
DEV Systemtechnik GmbH

Grüner Weg 4A
61169 Friedberg
GERMANY
Tel: +49 6031 6975 100
Fax: +49 6031 6975 114
support@dev-systemtechnik.com
www.dev-systemtechnik.com
Revision: 2017-10-10
DEV 91-0102-C
User Manual DEV 2194
Table of Contents
1 Revision History ----------------------------------------------------------- 5
2 Introduction ---------------------------------------------------------------- 6
2.1 Warranty---------------------------------------------------------------------------------- 6
2.2 Limitation of Warranty ---------------------------------------------------------------- 6
2.3 Warnings ---------------------------------------------------------------------------------- 7
3 Product Description ------------------------------------------------------ 8
3.1 Product Features ----------------------------------------------------------------------- 8
3.1.1 Device Panel------------------------------------------------------------------------------ 8
3.1.2 Communication Features ------------------------------------------------------------- 9
3.1.3 Distribution Amplifier Operation Modes ---------------------------------------- 10
3.2 Product Drawings--------------------------------------------------------------------- 11
4 Installation Instructions ------------------------------------------------ 12
4.1 Scope of Delivery --------------------------------------------------------------------- 12
4.2 Installation of the Product --------------------------------------------------------- 12
4.2.1 Mechanical Assembly of the Product -------------------------------------------- 12
4.2.2 Grounding, Data Cables and Power Connection ------------------------------- 12
4.2.3 Connection of RF Signal Cables ---------------------------------------------------- 12
4.3 Device Factory Settings ------------------------------------------------------------- 13
4.3.1 Factory Settings for the Amplifiers ----------------------------------------------- 13
4.3.2 Factory Network Settings ----------------------------------------------------------- 14
4.3.3 Factory SNMP Settings --------------------------------------------------------------- 14
4.4 Communication Interface Configuration --------------------------------------- 15
4.4.1 Ethernet Interface -------------------------------------------------------------------- 15
4.4.1.1 Ethernet Connection---------------------------------------------------------------------------- 15
4.5 Maintenance of the Product ------------------------------------------------------- 15
5 Operation of the Product ---------------------------------------------- 16
5.1 Modes of Operation ----------------------------------------------------------------- 16
5.1.1 Local Mode ----------------------------------------------------------------------------- 16
5.1.2 Remote Mode ------------------------------------------------------------------------- 16
5.2 Initialization of the Device --------------------------------------------------------- 16
5.3 Operation via the Device Panel --------------------------------------------------- 16
5.4 Operation via the Web Interface ------------------------------------------------- 17
5.4.1 Start of the Web Interface ---------------------------------------------------------- 17
5.4.2 The Main Window and Common Features of the Main Tabs --------------- 19
5.4.3 Status Tab ------------------------------------------------------------------------------- 20
5.4.4 Control Tab ----------------------------------------------------------------------------- 21
5.4.4.1 Amplifier ------------------------------------------------------------------------------------------- 22
2  Copyright DEV Systemtechnik GmbH 2013-2017

5.4.5 Events Tab ------------------------------------------------------------------------------ 23

5.4.6 Recording Tab -------------------------------------------------------------------------- 24
5.4.7 Setup Tab ------------------------------------------------------------------------------- 28
5.4.7.1 User Setup ----------------------------------------------------------------------------------------- 29
5.4.7.1.1 Password and Language ------------------------------------------------------------------------------------ 29
5.4.7.1.2 User Management ------------------------------------------------------------------------------------------- 29
5.4.7.2 System Setup ------------------------------------------------------------------------------------- 31
5.4.7.2.1 Network--------------------------------------------------------------------------------------------------------- 31
5.4.7.2.2 SNMP ------------------------------------------------------------------------------------------------------------ 32
5.4.7.3 Feature Setup------------------------------------------------------------------------------------- 33
5.4.7.3.1 Recording ------------------------------------------------------------------------------------------------------- 33
5.4.7.4 Software Service --------------------------------------------------------------------------------- 34
5.4.7.4.1 Restore Factory Defaults ----------------------------------------------------------------------------------- 34
5.4.7.4.2 Data Backup --------------------------------------------------------------------------------------------------- 34
5.4.7.4.3 Firmware Update --------------------------------------------------------------------------------------------- 39
5.4.8 Info Tab ---------------------------------------------------------------------------------- 40
5.5 Control via Remote Interface: SNMP -------------------------------------------- 41
5.5.1 SNMP Overview ----------------------------------------------------------------------- 41
5.5.2 Private Enterprise Number, Device Index Number --------------------------- 41
5.5.3 The Switch MIB Tree ----------------------------------------------------------------- 42
5.5.4 MIB Objects ---------------------------------------------------------------------------- 43
5.5.4.1 .devSwitchTraps --------------------------------------------------------------------------------- 44
5.5.4.1.1 .devSwitchTraps.trapAlarmText -------------------------------------------------------------------------- 44
5.5.4.1.2 .devSwitchTraps.trapAlarm -------------------------------------------------------------------------------- 44
5.5.4.1.3 .devSwitchTraps.trapModeChange ---------------------------------------------------------------------- 44
5.5.4.2 .instrument ---------------------------------------------------------------------------------------- 45
5.5.4.2.1 .instrument.controllerMac -------------------------------------------------------------------------------- 45
5.5.4.2.2 .instrument.firmwareRevision ---------------------------------------------------------------------------- 45
5.5.4.2.3 .instrument.instrumentType ------------------------------------------------------------------------------ 45
5.5.4.2.4 .instrument.antennaControllerType -------------------------------------------------------------------- 45
5.5.4.3 .application ---------------------------------------------------------------------------------------- 46
5.5.4.3.1 .application.controlMode ---------------------------------------------------------------------------------- 46
5.5.4.3.2 .application.switchingControl ----------------------------------------------------------------------------- 47
5.5.4.3.3 .application.simultaneousMode ------------------------------------------------------------------------- 47
5.5.4.3.4 .application.numberOfSwitchGroups ------------------------------------------------------------------- 47
5.5.4.3.5 .application.switchGroupTable --------------------------------------------------------------------------- 47
5.5.4.3.5.1 .application.switchGroupTable.switchGroupEntry.swGroupIndex ----------------------------- 47
5.5.4.3.5.2 .application.switchGroupTable.switchGroupEntry.swGroupMembers ------------------------ 47
5.5.4.3.5.3 .application.switchGroupTable.switchGroupEntry.swMainRfStatus --------------------------- 48
5.5.4.3.5.4 .application.switchGroupTable.switchGroupEntry.swRedundancyRfStatus ----------------- 48
5.5.4.3.6 .application.numberOfSwitchUnits ---------------------------------------------------------------------- 48
5.5.4.3.7 .application.switchUnitTable ------------------------------------------------------------------------------ 48
5.5.4.3.7.1 .application.switchUnitTable.switchUnitEntry.swIndex ------------------------------------------- 48
5.5.4.3.7.2 .application.switchUnitTable.switchUnitEntry.swSize---------------------------------------------- 49
5.5.4.3.7.3 .application.switchUnitTable.switchUnitEntry.swMembers -------------------------------------- 49
5.5.4.3.7.4 .application.switchUnitTable.switchUnitEntry.swPosition ---------------------------------------- 49
5.5.4.3.8 .application.numberOfPorts------------------------------------------------------------------------------- 49
5.5.4.3.9 .application.portTable -------------------------------------------------------------------------------------- 49
5.5.4.3.9.1 .application.portTable.portEntry.portIndex ---------------------------------------------------------- 49
5.5.4.3.9.2 .application.portTable.portEntry.poEnable ----------------------------------------------------------- 50
5.5.4.3.9.3 .application.portTable.portEntry.poType -------------------------------------------------------------- 50
 Copyright DEV Systemtechnik GmbH 2013-2017 3

5.5.4.3.9.4 .application.portTable.portEntry.poHasRfSense----------------------------------------------------- 50
5.5.4.3.9.5 .application.portTable.portEntry.poRfSense---------------------------------------------------------- 50
5.5.4.3.9.6 .application.portTable.portEntry.poRfLimit ----------------------------------------------------------- 50
5.5.4.3.9.7 .application.portTable.portEntry.poHasBias ---------------------------------------------------------- 50
5.5.4.3.9.8 .application.portTable.portEntry.poBiasOnOff------------------------------------------------------- 51
5.5.4.3.9.9 .application.portTable.portEntry.poBiasCurrent ---------------------------------------------------- 51
5.5.4.3.9.10 .application.portTable.portEntry.poBiasLimitLo ----------------------------------------------------- 51
5.5.4.3.9.11 .application.portTable.portEntry.poBiasLimitHi ----------------------------------------------------- 51
5.5.4.3.9.12 .application.portTable.portEntry.poHasGain --------------------------------------------------------- 52
5.5.4.3.9.13 .application.portTable.portEntry.poGain -------------------------------------------------------------- 52
5.5.4.3.9.14 .application.portTable.portEntry.poHasTilt ----------------------------------------------------------- 52
5.5.4.3.9.15 .application.portTable.portEntry.poTilt ---------------------------------------------------------------- 52
5.5.4.3.9.16 .application.portTable.portEntry.poCardType ------------------------------------------------------- 52
5.5.4.3.9.17 .application.portTable.portEntry.poSlot --------------------------------------------------------------- 53
5.5.4.3.9.18 .application.portTable.portEntry.poRfSenseStatus ------------------------------------------------- 53
5.5.4.3.9.19 .application.portTable.portEntry.poBiasStatus ------------------------------------------------------ 53
5.5.4.3.9.20 .application.portTable.portEntry.poLightStatus ----------------------------------------------------- 53
5.5.4.3.9.21 .application.portTable.portEntry.poCardStatus ----------------------------------------------------- 53
5.5.4.3.9.22 .application.portTable.portEntry.poGainMode ------------------------------------------------------ 54
5.5.4.3.9.23 .application.portTable.portEntry.poOutputPowerSetpoint -------------------------------------- 54
5.5.4.3.9.24 .application.portTable.portEntry.poHasInputPower ----------------------------------------------- 54
5.5.4.3.9.25 .application.portTable.portEntry.poInputPower ---------------------------------------------------- 54
5.5.4.3.9.26 .application.portTable.portEntry.poInputPowerLimit ---------------------------------------------- 54
5.5.4.3.9.27 .application.portTable.portEntry.poHasOutputPower --------------------------------------------- 55
5.5.4.3.9.28 .application.portTable.portEntry.poOutputPower -------------------------------------------------- 55
5.5.4.3.9.29 .application.portTable.portEntry.poDWDMChannelNumber ------------------------------------ 55
5.5.4.3.10 .application.antennaStatus -------------------------------------------------------------------------------- 55
5.5.4.3.11 .application.antennaPosition ----------------------------------------------------------------------------- 55
5.5.4.3.12 .application.numberOfMatrixOutputs ------------------------------------------------------------------ 55
5.5.4.3.13 .application.numberOfMatrixInputs -------------------------------------------------------------------- 56
5.5.4.3.14 .application.selectCrosspointSwitchingMode -------------------------------------------------------- 56
5.5.4.3.15 .application.activeCrosspointSetting -------------------------------------------------------------------- 56
5.5.4.3.16 .application.crosspointStringTable ---------------------------------------------------------------------- 56
5.5.4.3.16.1 .application.crosspointStringTable.crosspointStringEntry.crosspointStringIndex ---------- 56
5.5.4.3.16.2 .application.crosspointStringTable.crosspointStringEntry.crosspointString------------------ 56
5.5.4.3.17 .application.crosspointTable ------------------------------------------------------------------------------ 57
5.5.4.3.17.1 .application.crosspointTable.crosspointEntry.outChNr -------------------------------------------- 57
5.5.4.3.17.2 .application.crosspointTable.crosspointEntry.inChNr ---------------------------------------------- 57
5.5.4.4 .surveillance --------------------------------------------------------------------------------------- 58
5.5.4.4.1 .surveillance.trapEnableMask----------------------------------------------------------------------------- 59
5.5.4.4.2 .surveillance.errorEnableMask --------------------------------------------------------------------------- 59
5.5.4.4.3 .surveillance.numberOfErrors ---------------------------------------------------------------------------- 60
5.5.4.4.4 .surveillance.errorTable ------------------------------------------------------------------------------------ 60
5.5.4.4.4.1 .surveillance.errorTable.errorEntry.errorIndex ------------------------------------------------------ 60
5.5.4.4.4.2 .surveillance.errorTable.errorEntry.errorNr ---------------------------------------------------------- 60
5.5.4.4.4.3 .surveillance.errorTable.errorEntry.errorCount------------------------------------------------------ 60
5.5.4.4.4.4 .surveillance.errorTable.errorEntry.errorDateTime ------------------------------------------------- 60
5.5.4.4.4.5 .surveillance.errorTable.errorEntry.errorPending --------------------------------------------------- 61
5.5.4.4.4.6 .surveillance.errorTable.errorEntry.errorAcknowledge-------------------------------------------- 61
5.5.4.4.5 .surveillance.numberOfPowerLines --------------------------------------------------------------------- 61
5.5.4.4.6 .surveillance.powerLineTable ----------------------------------------------------------------------------- 61
5.5.4.4.6.1 .surveillance.powerLineTable.powerLineEntry.powerLineIndex -------------------------------- 61
5.5.4.4.6.2 .surveillance.powerLineTable.powerLineEntry.powerLineStatus ------------------------------- 61
5.5.4.4.7 .surveillance.numberOfPowerSupplies ----------------------------------------------------------------- 62

5.5.4.4.8 .surveillance.powerSupplyTable ------------------------------------------------------------------------- 62

5.5.4.4.8.1 .surveillance.powerSupplyTable.powerSupplyEntry.powerSupplyIndex ---------------------- 62
5.5.4.4.8.2 .surveillance.powerSupplyTable.powerSupplyEntry.powerSupplyStatus --------------------- 62
5.5.4.4.9 .surveillance.numberOfFans ------------------------------------------------------------------------------ 62
5.5.4.4.10 .surveillance.fanTable --------------------------------------------------------------------------------------- 62
5.5.4.4.10.1 .surveillance.fanTable.fanEntry.fanIndex -------------------------------------------------------------- 63
5.5.4.4.10.2 .surveillance.fanTable.fanEntry.fanStatus ------------------------------------------------------------- 63
5.5.4.4.11 .surveillance.internalDeviceStatus ----------------------------------------------------------------------- 63
5.5.4.4.12 .surveillance.externalDeviceStatus ---------------------------------------------------------------------- 63
5.5.4.4.13 .surveillance.supportHardwareStatus ------------------------------------------------------------------ 63
5.5.4.4.14 .surveillance.errorDescription ---------------------------------------------------------------------------- 63
6 Error Indication ----------------------------------------------------------- 64

6.1 Software Error Indication ---------------------------------------------------------- 64
6.1.1 LED Unit Error -------------------------------------------------------------------------- 64
6.1.2 Amplifier Errors------------------------------------------------------------------------ 64
6.1.3 Other Errors ---------------------------------------------------------------------------- 64
7 Connectors ---------------------------------------------------------------- 65
8 Technical Data ------------------------------------------------------------ 65
9 Conformance Declarations -------------------------------------------- 66
9.1 Certificate of Conformance -------------------------------------------------------- 66
9.2 EU Declaration of Conformity ----------------------------------------------------- 69
10 Glossary -------------------------------------------------------------------- 70
11 Notes ------------------------------------------------------------------------ 71
1 Revision History
Revision (Date) Author Short Description
A (14-May-2013) WP First version
B (19-Jul-2017) WP Complete rework
C (10-Oct-2017) WP Minor changes

2 Introduction
Thank you for purchasing a DEV 2194 L-Band Distribution Amplifier.
This user manual is intended to familiarize you with the installation and with the
operation of the product.
The DEV 2194 for professional use can be configured via external patch cables to be
operated either as a dual 1:8 or as a single 1:16 distribution amplifier.
DEV Systemtechnik GmbH declares that this equipment meets all relevant
standards and rules. The unit carries a CE mark.
Please read all instructions before installation or usage of the product!
2.1 Warranty
The product has a warranty against defects in material and workmanship for a
period of two years from the date of shipment. During the warranty period
DEV Systemtechnik will, at its option, either repair or replace the product if it turns
out to be defective.
For warranty, service, or repair, the product must be returned to DEV System-
technik. The customer has to pay shipping charges to DEV Systemtechnik and
DEV Systemtechnik will pay shipping charges to return the product to the customer.
However, the customer is obliged to pay all duties, all taxes, and all other additional
costs arising from the shipment of the product.
DEV Systemtechnik warrants that the software and firmware designated by
DEV Systemtechnik for use with the product will execute its programming
instructions if installed properly. DEV Systemtechnik does not warrant that the
operation of the product, software, or firmware will be uninterrupted or error-free.
2.2 Limitation of Warranty

The preceding warranty does not apply to defects resulting from:
 improper site preparation or site maintenance;
 improper or inadequate interfacing of the product;
 unauthorized modification or misuse of the product;
 the application of software supplied by the customer;
 improper or inadequate maintenance of the product;
 operation beyond the environmental conditions specified for the product.

2.3 Warnings
The following safety measures must be observed during all phases of operation,
service, and repair of the device. Failure to comply with the safety precautions or
warnings in this document violates safety standards of design, manufacturing, and
intended use of the device and may affect the built-in protections.
DEV Systemtechnik shall not be liable for the failure of users to comply with these
requirements.
Disconnect the device from the external power line before opening of the housing.
In any case, the device is to be opened by trained service staff, only.
Environmental Conditions
The device is designed for indoor use and for an ambient temperature range.
Mechanical Integration
It is not permitted to fix the chassis on the rack mount flanges, only. Balanced
weight distribution of the chassis has to be ensured by placing it on a solid surface
or by using rack rails.
Sufficient airflow through the chassis must be ensured to achieve best cooling
results. Do not block or obstruct the airflow through the chassis at the front and at
the rear side, e.g. by placing large components close to the front side. It is
recommended to provide 1 RU space in the rack above and below the chassis to
ensure a good air circulation.
Heat Hazard
Top, bottom, and side surfaces may become hot when operating the device
continuously. To reduce the risk of injury from a hot surface, allow the surface to
cool before touching.
Grounding, AC Connection, Cables
To minimize shock hazard the device must be connected to an electrical ground via
a ground wire, please refer to chapter 4.2.2. For the AC connection, the device
must be connected to the AC power supply mains through a power cable with three
conductors and with the ground wire firmly connected to an electrical ground
(safety ground) at the power outlet. Any interruption of the protective ground con-
ductor will cause a potential shock hazard that might cause personal injury.
Do not connect the device to mains supply exceeding the specifications for input
voltage and frequency. The recommended AC cable to be applied is a standard high
temperature power cable with type IEC 60320-C13 appliance plug appropriately
rated to the conditions of the country where the device is operated.

3 Product Description
With the DEV 2194, DEV Systemtechnik has developed a flexible distribution ampli-
fier chassis that is equipped with two 1:8 distribution amplifiers.
An integrated 1:2 splitter permits the operation of the device as a single 1:16 distri-
bution amplifier instead.
At the front side of the chassis, the 16 female 75 Ohm BNC output ports of the two
distribution amplifiers are located. Additionally, two status LEDs are available here,
please refer to chapter 3.1.1.
The rear side of the device provides seven precision female 75 Ohm F connectors,
used as the input port and as an output monitor port for each of the two amplifiers
and as the input and the two outputs of the integrated 1:2 splitter.
Additionally, each amplifier provides three status LEDs, a push button for LNB
power, and a female 50 Ohm SMA connector to monitor the input signal.
Finally, on the left of the rear side of the chassis, the power inlet and the Ethernet
connector are located.
3.1 Product Features
3.1.1 Device Panel
For monitoring purposes, the device provides two status LEDs at the front side and
three status LEDs plus a push button per amplifier at the rear side of the chassis.
The two status LEDs located on the right of the front side are controlled by the
controller of the device:
O p e ra tio n
A la rm
3 4
The green "Operation" LED (3) is off after power on and after a device reset until the
DEV 2194 is operational. If there are pending and not acknowledged error(s), the
red "Alarm" LED (4) is on.
The three status LEDs and the "Bias" (LNB Power) push button of each amplifier are
located on the rear side of the device:
In 1 :1 6 M on In 1 :8 O ut 2 O ut 1 In 1 :8 M on
M on M on
B ia s O I B ia s O I
O p . R F B ia s O p . R F B ia s
A m p lifie r 1 A m p lifie r 2
7 9 10 13 15 1 71 8 21
 Operation status LED "Op." (7 & 15)

The LED is on and green if the (corresponding) amplifier is supplied with power
and if the amplifier circuits are working normally. The LED turns to red if circuits
of the amplifier are detected as being defective, i.e. the device has to be sent
to DEV Systemtechnik for repair. If the LED is off, this indicates that no power is
applied to the amplifier.

 "RF" level status LED (9 & 17)

With the integrated RF level monitoring functionality, the aggregated power
level of the RF signal is measured and compared with a threshold level. The
status of RF level monitoring is indicated via the "RF" LED: green means ok, red
indicates the signal level to be below the RF threshold level.
 "Bias" status LED (10 & 18)
The amplifiers provide LNB power with current monitoring, i.e. the amplifiers
are prepared to feed DC current through the (corresponding) RF input port in
order to supply LNBs or inline amplifiers with power. The current monitoring
functionality is applied for the surveillance of the current fed by the LNB power
supply. The "Bias" LED being off indicates that the LNB power supply is turned
off for this amplifier. If the LED is green, LNB power is fed to the RF input port
of the amplifier and the current is within the limits of the defined current
monitoring interval. If the lower limit (no or not enough current) or the upper
limit (too much current is drawn) is exceeded, the LED is red.
 "Bias" push button (13 & 21)
In Local Mode the enabled "Bias" push button can be used to turn on or off the
LNB power supply in VL mode (13 V, 0 Hz).
Note:
 A "Bias" push button is functional only if the button is enabled and if the
operation mode of the device is Local Mode. The operation mode can be
changed via Web Interface (please refer to chapter 5.4.2) or via SNMP (chapter
5.5.4.3.1). The "Bias" push button can be enabled or disabled via Web Interface
(chapter 5.4.4.1).
 With the "Bias" push button the LNB power supply can be turned on in VL mode
(13 V, 0 Hz), only.
The other LNB power supply modes (VH: 13 V, 22 kHz; HL: 18 V, 0 Hz; and
HH: 18 V, 22 kHz) are available via Web Interface (chapter 5.4.4.1) and via
SNMP (chapter 5.5.4.3.9.8).
 After the boot phase of the device and after an operation mode change, all
LEDs of each amplifier are blinking shortly as a receipt.
3.1.2 Communication Features
Additionally to the device panel, a Web Interface (please refer to chapter 5.4) is
available for operating the DEV 2194 in Local Mode. The Web Interface provides
features for checking the health status and for changing the setup of the device; it
provides full control in terms of setting up specific parameters, and it provides
access to the recording functionality.
The implementation of SNMP (Simple Network Management Protocol) via the
Ethernet interface permits remote monitoring and control of the device
(chapter 5.5).

3.1.3 Distribution Amplifier Operation Modes

With no patch cables applied, the DEV 2194 is operated as a dual 1:8 distribution
amplifier. The input signal is applied to the corresponding input port labeled
"In 1:8" at the rear side of the device. A monitor port (50 Ohm, SMA (f)) is provided
to monitor the input signal; a second monitor port (75 Ohm, F (f)) is intended to
monitor the processed input signal. The eight output ports of the corresponding
distribution amplifier are available at the front side of the device.
The block diagram below illustrates this operation mode:
1 :8 S p litte r
A m p lifie r 1 M o n [F (f)]
O u tp u t A m p lifie r 1 (1 )
A m p lifie r 1 M o n [S M A (f)]
DC
In p u t A m p lifie r 1 A m p lifie r 1 In 1 :8 O u tp u t A m p lifie r 1 (4 )

O u tp u ts A m p lifie r 1 (1 ...8 )
LNB Pow er M o n ito r A m p lifie r 1 :2 S p litte r
fu n ctio n a lity
(w ith g a in & tilt)
A m p lifie r 1 O u tp u t A m p lifie r 1 (7 )
O ut 1
1 :2 S p litte r
In 1 :1 6
1 :8 S p litte r
O ut 2 O u tp u t A m p lifie r 2 (1 )
A m p lifie r
fu n ctio n a lity
LNB Pow er M o n ito r (w ith g a in & tilt) 1 :2 S p litte r
O u tp u ts A m p lifie r 2 (1 ...8 )
In p u t A m p lifie r 2 A m p lifie r 2 In 1 :8 O u tp u t A m p lifie r 2 (5 )
DC
To operate the DEV 2194 as a 1:16 distribution amplifier, two patch cables (being
part of the delivery) have to be installed as shown in the next block diagram.
The input port in this operation mode is the input port of the internal 1:2 splitter,
which is labeled "In 1:16":
1 :8 S p litte r
DC
A m p lifie r 1 In 1 :8 O u tp u t A m p lifie r 1 (4 )
LNB Power M o n ito r A m p lifie r 1 :2 S p litte r
fu n ctio n a lity
(w ith g a in & tilt)
O ut 1
1 :2 S p litte r
In p u t In 1 :1 6 O u tp u ts 1 ...1 6
1 :8 S p litte r
O ut 2 O u tp u t A m p lifie r 2 (1 )
A m p lifie r
fu n ctio n a lity
LNB Power M o n ito r (w ith g a in & tilt) 1 :2 S p litte r
A m p lifie r 2 In 1 :8 O u tp u t A m p lifie r 2 (5 )
DC

3.2 Product Drawings

Front View:
2 x 1 :8 / 1 x 1 :1 6 D istrib u tio n A m p lifie r 7 0 0 ...2 3 0 0 M H z
O u tp u ts A m p lifie r 1 O u tp u ts A m p lifie r 2
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
O p e ra tio n
A la rm
D EV 2194
1 2 3 4
1 "Outputs Amplifier 1" "1"…"8": output ports Amplifier 1; 75 Ohm, BNC (f) connectors
2 "Outputs Amplifier 2" "1"…"8": output ports Amplifier 2; 75 Ohm, BNC (f) connectors
3 "Operation" LED
4 "Alarm" LED
Rear View:
W A R N IN G : 1 0 0 ...2 4 0 V E th e rn e t In 1 :1 6 M on In 1 :8 O ut 2 O ut 1 In 1 :8 M on
D is co n n e c t p o w e r 5 0 /6 0 H z
b e fo re o p e n in g ! 40 VA
M on M on
B ia s O I B ia s O I
O p . R F B ia s O p . R F B ia s
Fuse 2 A T A m p lifie r 1 A m p lifie r 2
1 2 3 4 5 6 7 8 9 10 11 12 13 1 41 5 1 61 71 8 1 9 20 21
1 Grounding bolt
2 AC power inlet
3 AC power fuse
4 "Ethernet" connector; RJ-45
5 "In 1:16": Input port internal 1:2 splitter; 75 Ohm, F (f))
6 "Mon": Monitor port for input signal of Amplifier 1; 50 Ohm, SMA (f)
7 "Op.": Operation status LED Amplifier 1
8 "Mon": Monitor port for output signal of Amplifier 1; 75 Ohm, F (f)
9 "RF": RF level status LED Amplifier 1
10 "Bias": LNB power supply status LED Amplifier 1
11 "In 1:8": Input port Amplifier 1; 75 Ohm, F (f)
12 "Out 2": Second output port internal 1:2 splitter; 75 Ohm, F (f)
13 "Bias": LNB power supply push button Amplifier 1
14 "Mon": Monitor port for input signal of Amplifier 2; 50 Ohm, SMA (f)
15 "Op.": Operation status LED Amplifier 2
16 "Out 1": First output port internal 1:2 splitter; 75 Ohm, F (f)
17 "RF": RF level status LED Amplifier 2
18 "Bias": LNB power supply status LED Amplifier 2
19 "In 1:8": Input port Amplifier 2; 75 Ohm, F (f)
20 "Mon": Monitor port for output signal of Amplifier 2; 75 Ohm, F (f)
21 "Bias": LNB power supply push button Amplifier 2

4 Installation Instructions
4.1 Scope of Delivery
1 * DEV 2194 L-Band Distribution Amplifier
2 * DEV 73-0188 patch cable; 75 Ohm, 2 * F (m); 0.2 m
1 * User Manual (this document)
4.2 Installation of the Product

4.2.1 Mechanical Assembly of the Product
Please refer to the warnings in chapter 2.3 regarding the mechanical integration of
the product. For the assembly in a 19" rack the rack slots must be prepared with
rails for the chassis. After inserting the chassis in the rack, fix the chassis with four
screws to the rack at its rack mount flanges.
4.2.2 Grounding, Data Cables and Power Connection
W A R N IN G : 1 0 0 ...2 4 0 V E th e rn e t
D is co n n e c t p o w e r 5 0 /6 0 H z
b e fo re o p e n in g ! 40 VA
F u se 2 A T
1 2 3 4
For the warnings with respect to "Grounding, AC Connection, Cables" please refer
to chapter 2.3.
The chassis needs to be connected to the 19" rack via a ground wire. The grounding
bolt is located on the left at the rear side of the product:
Take off the upper nut and the first washer of the grounding bolt (1) and connect
the grounding cable, which must have a ring tongue terminal matching for the M4
fastening bolt. After that, the washer and the nut have to be tightened again.
Establish the external Ethernet connection by plugging an Ethernet cable from your
network to the "Ethernet" port (4).
Finally, connect a power cord to the primary connector (2).
Note:
 It is highly recommended to power-up the device after the installation of all
signal cables (chapter 4.2.3).
 The power line is fused; the fuse holder (3) is located below the power inlet (2).
If the fuse has to be exchanged, unplug the device and use a 2 A T 5*20 mm
glass fuse for replacement only!
4.2.3 Connection of RF Signal Cables
Apply strain relieves to the external RF signal cables which are to be connected in a
way that the connectors of the device are not stressed mechanically.
If the DEV 2194 is already powered up and before RF signal cables are to be
connected to the chassis, the LNB power of the amplifiers is to be turned off!
Otherwise, there is a risk that a high impulse current degrades the RF performance
of the corresponding RF input connector.

First, connect the RF input cables (e.g. from the LNB) to the corresponding RF input
port(s); then connect the RF output cables (to the signal receivers) to the related
RF output ports.
When connecting RF cables to the chassis, each connector providing a thread is to
be tightened with a torque wrench. The torque applied to 75 Ohm F connectors
should not exceed 4.5 Nm (39.8 lbf-in). In case of 50 Ohm SMA connectors a torque
wrench adjusted to 1 Nm (8.85 lbf-in) is to be used. For the BNC connectors of the
output ports make sure that the bayonet of each BNC connector is locked.
Note:
 For 75 Ohm RF connectors, female 75 Ohm BNC connectors and female
precision F connectors are applied. Make sure, that the applied connectors are
male 75 Ohm BNC connectors and male precision F connectors (with thin inner
conductor).
 Each unused output port of a distribution amplifier has to be terminated with a
75 Ohm BNC load to achieve best amplitude frequency response.
 If all cables are connected, the device can be powered up.
 If the device is set up to operate as a 1:16 distribution amplifier (please refer to
chapter 3.1.3) and if the input is required to deliver LNB power, it is not recom-
mended to supply the sink (e.g. an LNB) with LNB power from both amplifiers
(i.e. parallel supply). Due to variations of parts, the current load for the ampli-
fiers will not be balanced and the current monitoring will not work properly.
4.3 Device Factory Settings
The product is delivered with factory settings as described in the following.
It is possible to restore these settings via Web Interface, please refer to
chapter 5.4.7.4.1.
4.3.1 Factory Settings for the Amplifiers
The amplifiers provide RF level monitoring functionality, i.e. the aggregated signal
power level of the RF signal is measured and compared with an RF threshold level.
If the signal level is below the threshold level, an alarm is triggered which is
indicated (e.g.) via LED. The factory setting for the RF threshold level is:
RF Threshold Level: (20 dB above lower limit)
Here the lower limit is -50 dBm, i.e. the factory setting for the RF threshold level
is -30 dBm. The RF threshold level can be adjusted via Web Interface (please refer
to chapter 5.4.4.1) or via SNMP (chapter 5.5.4.3.9.6).
The amplifiers are capable of providing LNB power (bias) at the RF input. With the
current monitoring functionality, the current delivered by the input is monitored. If
the measured current exceeds the defined interval, an alarm is triggered which is
indicated (e.g.) via LED. The factory settings for the current monitoring interval are:
Lower Limit: 100 mA
Upper Limit: 250 mA
The lower limit and the upper limit of the current monitoring interval can be
adjusted via Web Interface (chapter 5.4.4.1) and via SNMP (chapters 5.5.4.3.9.10 &
5.5.4.3.9.11).

Finally, the amplifiers provide gain control and slope (or tilt) adjustment capability.
It is not possible to make parameter adjustments locally; the adjustments are to be
performed via Web Interface (chapter 5.4.4.1) or via SNMP (chapters 5.5.4.3.9.13 &
5.5.4.3.9.15). The factory settings are:
Gain: +10.0 dB
Slope (or Tilt): 0 dB
4.3.2 Factory Network Settings
The factory network settings of the device are:
IP-Address: 192.168.0.11
Netmask: 255.255.255.0
Gateway: 192.168.0.99
For changing the network setup, please refer to chapter 5.4.7.2.1.
4.3.3 Factory SNMP Settings
The factory SNMP settings are configured as follows:
Read Community: public
Write Community: private
Local/Remote changeable via SNMP:
Additionally, the default community for all four Trap Destination IP Addresses is set
to public and all configurable traps are disabled. If an address is defined without
explicit port assignment, the standard SNMP trap port 162 is assigned implicitly.
For changing the SNMP setup, please refer to chapter 5.4.7.2.2.
There are software factory defaults for some SNMP objects, please refer to the
corresponding chapters:
 .application.controlMode chapter 5.5.4.3.1
 .application.portTable.portEntry.poEnable chapter 5.5.4.3.9.2
 .application.portTable.portEntry.poRfLimit chapter 5.5.4.3.9.6
 .application.portTable.portEntry.poBiasOnOff chapter 5.5.4.3.9.8
 .application.portTable.portEntry.poBiasLimitLo chapter 5.5.4.3.9.10
 .application.portTable.portEntry.poBiasLimitHi chapter 5.5.4.3.9.11
 .application.portTable.portEntry.poGain chapter 5.5.4.3.9.13
 .application.portTable.portEntry.poTilt chapter 5.5.4.3.9.15
 .surveillance.trapEnableMask chapter 5.5.4.4.1
 .surveillance.errorEnableMask chapter 5.5.4.4.2

4.4 Communication Interface Configuration

The Ethernet interface is used for the operation via Web Interface or via SNMP.
4.4.1 Ethernet Interface
The connector labeled "Ethernet" is an RJ-45 jack for the standard 100Base-TX
Ethernet interface; chapter 7 describes the pin assignment.
4.4.1.1 Ethernet Connection
If a standalone device is to be connected to a PC only, the connection can be
established via a direct Ethernet cable (or through a local hub/switch) between the
Ethernet connector of the device and the Ethernet connector of the PC. The net-
work setup of the PC is to be altered that it is in the same subnet as the device. If it
is intended to use the factory network settings, the IP address of the standalone PC
is to be set to 192.168.0.x, with x in the range 1…254, except 11, which is the address of
the device, e.g. set the IP address of the standalone PC to the default gateway
address 192.168.0.99.
If the device is to be connected to the local network, make sure to change the
network setup as required. Ask your network administrator for the details on
network parameters which are to be used.
The factory network settings are subject of chapter 4.3.2.
The network setup can be changed via Web Interface (please refer to chapter
5.4.7.2.1).
4.5 Maintenance of the Product

The product is maintenance-free.
Cleaning of the surface of the chassis should be done carefully with a dry lint-free
cloth.

5 Operation of the Product

After going through the installation steps as described above, the device is ready to
use. There are two possibilities for monitoring and control, please refer to
chapter 3.1.2. Before the operation via each of these possibilities is explained, the
different device operation modes are described:
5.1 Modes of Operation
Local Mode and Remote Mode define the manner how the device is controlled. The
operation mode can be changed via Web Interface (please refer to chapter 5.4.2)
and via SNMP (chapter 5.5.4.3.1).
Note:
 The factory setting for the operation mode is Remote Mode.
5.1.1 Local Mode
In Local Mode, the device executes commands that are issued via Web Interface.
The "Bias" push buttons at the device can be operated (if enabled, please refer to
chapter 5.4.4.1).
The SNMP remote interface is disabled for modifying the settings, but open for
status queries.
5.1.2 Remote Mode
The Remote Mode is implemented for the operation via SNMP.
In Remote Mode, the status of the DEV 2194 is still indicated via the LEDs at the
device and via Web Interface, but the "Bias" push buttons at the device are locked
and the control functionality of the Web Interface is disabled.
5.2 Initialization of the Device
The device performs a health check and a configuration check during power-up and
after a device reset. This takes about 60 seconds; there is no manual configuration
necessary, all settings (including the operation mode) after power-up or after a
reset remain unchanged.
5.3 Operation via the Device Panel
The local operation (via the "Bias" push buttons) and the status indication (via LEDs)
of the device panel were already explained; please refer to chapter 3.1.1.
Note:
 The factory default for the operation mode is Remote Mode. To operate the
"Bias" push buttons of the device panel, the device has to be switched to
Local Mode via Web Interface (chapter 5.4.2) or via SNMP (chapter 5.5.4.3.1).

5.4 Operation via the Web Interface

The Web Interface is a comfortable user interface for operating the product, i.e. the
device is controlled via a computer and a Web Browser as the communication
application. Several users (assumed the appropriate number of licenses) can access
the device at a time. The first license is included in the delivery. It is possible to
purchase additional license keys at any time, please contact DEV Systemtechnik.
5.4.1 Start of the Web Interface
To start the Web Interface open a web browser (recommended is Mozilla Firefox
(version 3.5 or higher) but also Chrome, Opera, Safari, or Internet Explorer (starting
with version 8, recommended is version 9 or higher) are supported) and type in the
URL (IP address) of the device:
http://<IP-of-the-device>/
After a moment the Start Screen of the Web Interface appears:
To log on the first time use the factory default account:

Username: ADMIN
Password: ADMIN
After entering username and password, click on .
Note:
 Both, username and password are case sensitive!
 Note the header in the Start Screen:
DEV 2194
SystemName
SystemLocation

The labels "SystemName" and "SystemLocation" are the SNMP variables

'System Name' and 'System Location'; both can be set within the SNMP setup
(please refer to chapter 5.4.7.2.2).
 If the Start Screen is not accessible, make sure that the computer accessing the
device is in the same subnet of the common network (chapter 4.4.1.1).
 If the network connection to the device gets lost during a session, a
corresponding notification will pop up. After confirmation, the web browser is
redirected to the Start Screen. If the device is accessible again, a new
authentication is required.
 During power-up or after a reset the device displays a different screen:
If the device is operational (again), the screen usually automatically changes to

the Start Screen, thus enables the input fields to be edited; if not, please use
the refresh functionality of your web browser (e.g. the function key F5).
 The Web Interface permits the definition of a number of users with different
permission (chapter 5.4.7.1.2) for accessing the Web Interface in parallel (in
accordance to the number of installed licenses). An additional user who tries to
log in receives a corresponding notification informing about the logged in
user(s), e.g.:
 It is recommended to add user(s) AND to change the password of the factory

default account. How this is to be done is subject of chapters 5.4.7.1.2 &
5.4.7.1.1.
 The language of the screenshots shown here is English, as a second language
currently German is available (chapter 5.4.7.1.1).

5.4.2 The Main Window and Common Features of the Main Tabs
After successful authentication the main window of the Web Interface shows up
with the Status Tab opened, which is the default view:
In the top of the window on the left side, the six tabs are located ("Status",
"Control", "Events", "Recording", "Setup", and "Info"). The active tab is highlighted;
clicking on an inactive tab opens the corresponding tab instead.
In the middle on the top of the window two buttons are located indicating that the
device is in Remote Mode (as shown in the screenshot above), or in Local Mode (as
shown in the screenshot of chapter 5.4.3).
Changing the operation mode of the device via Web Interface is performed by
clicking on the desired button, e.g. clicking in the situation above on the
button, highlights the button instead of the button.
Right to these buttons the currently logged in user (here: "ADMIN") and the
permission of the user (here: "admin") are shown. Please refer to chapter 5.4.7.1.2
for more information on this subject.
Then, the date and time of the device are displayed right to this information. The
correct date and time depend on the proper configuration of an NTP timeserver
and of the time zone (chapter 5.4.7.2.1). Note that if there was no timeserver
detected at power-up, the device sets the date and time to "01-Jan-2000 00:00".
In the right corner close to the company logo, the button is located. Clicking
on this button returns the Web Interface to the Start Screen.
Note:
 It is recommended to finish a Web Interface session by clicking on the
button. This instantaneously releases the allocated license and enables other
users to log in.
 A timeout feature (20 seconds) is implemented within the Web Interface, i.e. a
session is automatically terminated (and the allocated license is released) if a
user who is currently logged in closes the web browser.

 This means that a Web Interface session is kept open unless the button
is operated or if the web browser (in other words, the connection to the
device) is closed.
 It is possible to start a Web Interface session on another computer using the
same user account; naturally, this automatically terminates the session on the
preceding computer.
5.4.3 Status Tab
The upper part of the Status Tab shows a simplified representation of the front side
and of the rear side of the device. Thus, a quick overview is provided regarding the
operating status and regarding the health status of the device. The round indicators
are equivalent to the physical LEDs at the device (red = error, green = ok, or gray =
off), please refer to chapter 3.1.1 for details on the indicator information.
In the lower part of the Status Tab, the Active Events Window is located. This
window shows appearing and pending errors with the corresponding error message
and a date/time stamp. The error shown in the following screenshot was triggered
for demonstration purpose by pulling shortly the input RF connector of the first
amplifier. To obtain more details on the errors open the Events Tab (chapter 5.4.5).
Note:
 The status indication for the amplifiers in the symbolic representation is equiva-
lent to the physical display on the device. Additionally, if a communication
error is detected, the representation of the amplifier is highlighted in red.

5.4.4 Control Tab
The main purpose of the Control Tab is the change of amplifier specific settings.
On the left side, the "Amplifier Channels 1:1" functionality item contains two entries in
order to select a specific amplifier (panel) of the device. The names ("Amp X") are the
descriptive designators, which can be edited by double-clicking the specific item:
Note:
 If changes of settings (which are to be saved explicitly) are applied in a panel of
the Control Tab (or within an entry of the Setup Tab, please refer to chapter
5.4.7), they are highlighted in yellow. If a different panel within the Control Tab
(or if a different entry within the Setup Tab) is selected without saving the
change(s) in the current panel or entry, a corresponding warning message pops
up. The next screenshot shows this situation for selecting the "Amp 2" panel
after deactivating the "Surveillance Enable" check box in the "Amp 1" panel:

5.4.4.1 Amplifier
If an amplifier entry is selected on the left side of the Control Tab, the
corresponding panel appears on the right side. It consists of two sections:
1) In the upper "Status" section first the "Port Number" is shown as a reference to
the index of the SNMP .portTable (please refer to chapter 5.5.4.3.9) and if port
specific error messages are to be identified within the Events Tab
(chapter 5.4.5). In the line below, the "Module Type" is listed (here:
"DEV 11-0081"). Next, the "RF Level" status (red/green) and the measured level
(in [dBm]) are shown. Finally, since the amplifiers provide LNB power with
current monitoring, the "LNB Power Level" status (green, red, or gray) and the
measured current (in [mA] or "off") are indicated.
2) The "Setup" section permits changes on the parameters of the corresponding
amplifier. Note that after settings have been altered within this section in
Local Mode (!), a click on the button is necessary to apply the
changes:
• "Gain" and "Slope" can be adjusted roughly by clicking into the
corresponding control bar, or in discrete steps using the or
buttons. The current target setting is displayed via the (blue/green) colored
bar and via a numerical value next to the button.
• The "RF Threshold" for the RF level monitoring functionality can be
adjusted within a certain range.
• If LNB power is required at the RF input of an amplifier, the drop down list
"LNB Power Enable" needs to be operated. The default is "Off", to turn on
the LNB power, select one of the polarization/band entries:
"HL" (horizontal low: 18 V, 0 Hz), "HH" (horizontal high: 18 V, 22 kHz),
"VL" (vertical low: 13 V, 0 Hz), or "VH" (vertical high: 13 V, 22 kHz).
The current monitoring interval for the current monitoring functionality is
defined by "LNB Power Upper Limit" and "LNB Power Lower Limit". The

values of these entries may be altered within certain ranges.

The check box "LNB Power Button Enable" can be used to enable (default)
or to disable in Local Mode the functionality of the "Bias" push button of the
corresponding amplifier (chapter 3.1.1).
• The "Surveillance Enable" check box is used to enable (default) or to disable
error messages possibly caused by the specific amplifier.
5.4.5 Events Tab
The Events Tab displays a table of the errors, which were detected by the device.
The different errors are listed line-by-line, i.e. each error carries a Date/Time stamp
(in the format: "DDD DD MMM YYYY hh:mm:ss", here e.g. "Thu 13 Jul 2017 13:30:03") informing
about the last occurrence of that error. The second column is a Counter reporting
the number of occurrences of that error (here: "1"). The third column denotes
whether that error is Ack.nowledged ("X") or not (" ") (here: " ", i.e. <space>, meaning
not acknowledged). The fourth column shows whether that error is Pend.ing ("X")
or not (" ") (here: " ", i.e. not pending). The fifth and the sixth column inform about
the error code No. in Hexadecimal (here e.g. "7C00") and in Decimal (here e.g.
"31744") notation; the last column reports the corresponding Event Description
(here e.g. "RF Level Port 1"), please refer to chapter 6.1.
Below, the buttons and are located:
An error can be acknowledged by highlighting (i.e. clicking on) the related line and
by operating the button afterwards. The intention of the
acknowledgement of an error is to provide means to mask out a pending error of
the Active Events Window in the Status Tab (chapter 5.4.3) and to turn the "Alarm"
LED at the front side of the device (chapter 3.1.1) to green if all pending errors in
the table are acknowledged. If a confirmed error occurs again, the counter in the
table is increased and the acknowledgement is reset (i.e. the "X" disappears, the
Active Events Window reports the error again, and the "Alarm" LED becomes red).

An acknowledged and not pending error can be deleted from the list by highlighting
the corresponding line, followed by clicking on the button.
If a deleted error occurs again, a line added at the beginning of the table.
Note:
 It is possible to acknowledge (and to delete) more than one entry at a time by
highlighting more errors using the <Ctrl> or the <Shift> key of the keyboard in
combination with mouse click(s).
 Users with "read" permission only have no rights to acknowledge or to delete
error entries (chapter 5.4.7.1.2).
 The table content can be stored using the data backup functionality
(chapter 5.4.7.4.2).
5.4.6 Recording Tab
Some data of each amplifier is continuously captured in discrete intervals. The
Recording Tab permits the visualization and the external storage of this data. After
opening the Recording Tab for the first time in a Web Interface session, two empty
diagrams labeled "Overview" and "Details" are shown as in the next screenshot.
After selecting "RF Level" or "LNB Power" (for LNB power current monitoring data)
from the drop down list "Signal Type" and after selecting one to three "Signals" via
the three drop down lists, the recorded data shows up in both diagrams:

Note:
 The recording interval and thus the recording duration can be altered, please
refer to chapter 5.4.7.3.1. The data representation initially always comprises
the recorded data for the selected items, i.e. it is stretched if the full recording
duration is not reached yet, and the graphs indicate via gaps if the device was
turned off for a span of time.
 The check box labeled "Show Thresholds" enables the display of the related
present threshold(s) for the selected signals. If checked, each threshold is
shown as a separate horizontal line with an individual label.
It is possible to magnify the data by drawing a zoom window in either (!) diagram,
i.e. by clicking and holding the left mouse button while pulling the mouse over the
interesting area:

Instantaneously after releasing the left mouse button, the zoomed area appears in
the "Details" diagram while the "Overview" diagram is highlighting the zoomed
area:
Three buttons are located at the bottom of the Recording Tab:

If the recorded data of the selected items was zoomed as described above, the but-
ton resets the data representation to the initial state, i.e. all recorded
data for the selected signals is displayed in both diagrams.
The remaining two buttons provide the option to store the captured data externally
(without the possibly displayed thresholds!). stores the recorded data
of the currently selected signals and the button stores all recorded data of
the device, i.e. the available data of all signals. After operating one of the buttons, a
browser specific window pops up and suggests the storage of the data as
"recording.csv" and as "recording_all.csv", respectively. The csv (comma-separated values)
file format permits the data import e.g. into a MS Excel worksheet:
The csv-file is a text file modeling a table. Each line is interpreted as row containing
column information, here with the columns delimited by a semicolon (";") charac-
ter as the column separator.
The number of columns depends on the export method ( vs. )
and how many signals are currently presented if the button is chosen.
In any case, each signal consists of a "Time" and of a "Value" column; the number
of lines depends on the recording duration (over 17000 lines e.g. within 2 days with
the default 10 seconds recording interval).
The first line of the csv-file is the header line providing the column information. The
first entry is assigned to the first channel (e.g. "Amp 1", indicating the descriptive
designator of the first signal, please refer to chapter 5.4.4), concatenated with the
"Signal Type" (i.e. either "RF Level" or "LNB Power") and with "Time". After the
semicolon, the same entry is listed with "Values" instead of "Time". This sequence is
repeated for all columns that are part of the csv-file.

The actual data starts in the second line of the csv-file. Note that the time
information is stated in standard MS Excel format, i.e. the integral part of the
number defines the date (starting from 1 being the 01-Jan-1900, e.g. 42917
denotes the date 01-Jul-2017 and the fractional part defines the time within the
date (1/(24 * 60 * 60) = 00:00:01, e.g. .575 = 13:48:00).
In the following only the first few lines of a csv-file are listed which was created by
exporting the data shown in this chapter via the button ("⌡" and "⌠"
are symbolizing that the two consecutive lines are actually one line in the file):
Amp 1 RF Level Time;Amp 1 RF Level Values;⌡
⌠Amp 2 RF Level Time;Amp 2 RF Level Values
42917.568773148148148;-18.5;42917.568773148148148;-17.7;
42917.569467592592593;-18.5;42917.569467592592593;-17.8;
42917.570162037037037;-18.5;42917.570162037037037;-17.8;
42917.570856481481481;-18.5;42917.570856481481481;-17.7;
42917.571550925925926;-18.5;42917.571550925925926;-17.8;
42917.572245370370370;-18.5;42917.572245370370370;-17.8;
42917.572939814814815;-18.5;42917.572939814814815;-17.8;
42917.573634259259259;-18.5;42917.573634259259259;-17.8;
42917.574328703703704;-18.5;42917.574328703703704;-17.8;
42917.575023148148148;-18.5;42917.575023148148148;-17.8;
42917.575717592592593;-18.5;42917.575717592592593;-17.8;
After import and formatting the "Time" columns to the format

"DD-MMM-YYYY, hh:mm:ss" this results in the following table:
Amp 1 RF Level Time Amp 1 RF Level Values Amp 2 RF Level Time Amp 2 RF Level Values
01-Jul-2017, 13:39:02 -18.5 01-Jul-2017, 13:39:02 -17.7
01-Jul-2017, 13:40:02 -18.5 01-Jul-2017, 13:40:02 -17.8
01-Jul-2017, 13:41:02 -18.5 01-Jul-2017, 13:41:02 -17.8
01-Jul-2017, 13:42:02 -18.5 01-Jul-2017, 13:42:02 -17.7
01-Jul-2017, 13:43:02 -18.5 01-Jul-2017, 13:43:02 -17.8
01-Jul-2017, 13:44:02 -18.5 01-Jul-2017, 13:44:02 -17.8
01-Jul-2017, 13:45:02 -18.5 01-Jul-2017, 13:45:02 -17.8
01-Jul-2017, 13:46:02 -18.5 01-Jul-2017, 13:46:02 -17.8
01-Jul-2017, 13:47:02 -18.5 01-Jul-2017, 13:47:02 -17.8
01-Jul-2017, 13:48:02 -18.5 01-Jul-2017, 13:48:02 -17.8
01-Jul-2017, 13:49:02 -18.5 01-Jul-2017, 13:49:02 -17.8
Note:
 The decimal separator in the csv-file is the point character ("."), this has to be
considered during the data import of the csv-file e.g. into an Excel worksheet.
 For the data import into an empty MS Excel worksheet select the tab "Data"
and there the icon "From Text". Then locate the csv-file and follow the instruc-
tions of the text import wizard.
 The correct time information is dependent on the proper configuration of a
timeserver and of the time zone. The settings can be applied via the network
setup of the Setup Tab (chapter 5.4.7.2.1).
If no timeserver is configured for the device, the recording of the data starts at
01-Jan-2000, 00:00:00, after a device reset the time is reset to 01-Jan-2000,
00:00:00 as well, but the recording of the data is continued with the time of the
last sample.
If a timeserver was configured for the device, which is not available anymore
after a reset, the recording of the data is continued with the time of the last
sample as well. Otherwise, if the timeserver is available after a device reset, the
recording of the data is continued with the correct time; i.e. this causes a time
gap within the data.

5.4.7 Setup Tab

On the left side, the Setup Tab contains the menu items structuring the different
entries described in the following. Initially, the single entries are not displayed:
To demonstrate the available setup entries, all menu items above were folded out
in the following screenshot:

5.4.7.1 User Setup

The menu item User Setup on the left side of the Setup Tab provides access to the
Password and Language entry for all users and access to the User Management
entry for users with "admin" permission.
5.4.7.1.1 Password and Language
The input fields of the Password and Language entry enable the user who is cur-
rently logged in to change the password and to alter the personal language setting.
To change the password, enter the old password, the new password, and the con-
firmation of the new password.
To change the language, select an entry from the drop down list "Language".
A click on the button applies the changes made.
If the password has been changed, a confirmation window pops up.
Note:
 English and German are the languages supported by the current firmware.
5.4.7.1.2 User Management
The currently logged in user has to have "admin" permission to access the User
Management entry where users can be added or deleted and the permission can
be modified.
In the next screenshot, a user named TEST with "admin" permission is in the pro-
cess to be restricted to "read/write" permission. After a click on the
button, this user will then have all rights but only access to the Password and
Language entry within the Setup Tab. A user with "read" permission additionally is
not able to apply any changes within the other tabs of the Web Interface.

To add a new user click on the item "Add New User" and enter a name in the
appearing text field and click again. By default this new user has "read" permission
and no password is set for this user.
By activating an existing user, the permission category can be altered and a
password can be set for this user. A click on the button applies the
changes made. If the password has been changed, a confirmation window pops up.
To delete a user, click on the trash bin icon right to the user entry, a window pops
up for confirmation.
Note:
 As already mentioned, user names and passwords are case sensitive.
 Do not forget to click on the button to store the settings made
before selecting (or adding) another user.
 After adding a new user without assigning a password, this user logs on without
any password. The following message pops up during the login process:
 It is not possible to delete the ADMIN user but it is recommended to change

the default password.

5.4.7.2 System Setup

The menu item System Setup on the left side of the Setup Tab provides access to
the Network entry and to the SNMP entry for users with "admin" permission.
5.4.7.2.1 Network
For the network setup of the device, at least the fields "IP Address" and "Netmask"
have to contain valid entries.
"Gateway", "Nameserver 1", and "Nameserver 2" are to be specified by their IP
addresses; the "Nameserver" entries are used for the resolution of the "Time-
server" fields, only.
The "Timeserver" fields are used to specify one or two timeservers either via full-
qualified domain name or via IP address.
To specify the timezone select an entry from the drop down list "Timezone":


If the IP address has been changed, a confirmation window pops up informing
about the redirection of the browser to the new address, e.g.:
Note:
 The LED symbols right to the fields for the gateway, for the name servers, and
for the timeservers indicate whether the saved (!) entry is an available network
resource (green) or not (red).
5.4.7.2.2 SNMP
With the SNMP setup, the settings for "System Name" and for "System Location"
can be modified. A "System Administrator" can be defined and the passwords for
the "Read Community" and for the "Write Community" can be set. The check box
below these entries is used to enable the switching between Local Mode and
Remote Mode via SNMP, please refer to chapter 5.5.4.3.1.
Additionally, up to four Trap Destination IP Addresses can be defined via the IP
address and the port in the format <ip-address>{:<port>}, e.g. 192.168.0.148:121. If <port> is not
specified, the standard SNMP trap port 162 is assumed. The LED symbols right to
the IP addresses fields indicate (after the entries have been saved) whether the
addresses are available network resources (green) or not (red). The community for
each of the four entries can be altered from the default "public" as well.
The check boxes below the header "Enabled Traps" provide access to the SNMP
.trapEnableMask (chapter 5.5.4.4.1) via Web Interface.
Finally, a click on the icon initiates the download of the MIB of the device.

Note:
 The strings "System Name" and "System Location" are part of standard SNMP
functionality and are limited to 40 characters, each. The number of visible
characters in the text fields is limited by the field size.
 As mentioned, the strings "System Name" and "System Location" are also
displayed in the Start Screen of the Web Interface (chapter 5.4.1).
5.4.7.3 Feature Setup
The Feature Setup menu item on the left side of the Setup Tab provides access for
users with "admin" permission to the device specific setup entries, i.e. here to the
Recording entry, only.
5.4.7.3.1 Recording
The Recording entry permits the configuration of the interval for the signal
recording functionality; please refer to chapter 5.4.6.
Via the "Recording Interval" drop down list the interval for the regular data capture
can be selected. After an entry was picked, the "Resulting Recording Duration" is
displayed in the line below. The following choices are available:
Recording Interval Resulting Recording Duration
10 Seconds 2 Days
30 Seconds 6 Days
60 Seconds 12 Days
Note:
 After clicking on the button with a different recording interval
selected than the currently applied setting all stored recording data is deleted
instantaneously; the recording starts with the new recording interval setting.
 The default recording interval setting is 10 seconds; after a Restore Factory
Defaults (chapter 5.4.7.4.1), this setting is applied as well.

5.4.7.4 Software Service

The Software Service menu item on the left side of the Setup Tab provides access
for users with "admin" permission to the Restore Factory Defaults entry, to the
Data Backup entry, and to the Firmware Update entry.
5.4.7.4.1 Restore Factory Defaults
With a click on the button, the settings of the device are reset
to the factory values as described in chapter 4.3 including all changes on the
Web Interface. To maintain the network setup of the device, activate the check box
"Keep IP Settings" before operating the button. After a click on
, a device reset is initiated indicated via a pop up window, e.g.:
Note:
 Any data stored via the data backup functionality is not deleted, please refer to
chapter 5.4.7.4.2.
 Recorded data (chapter 5.4.6) is deleted only if a different recording interval is
applied than the recording interval default setting (chapter 5.4.7.3.1).
5.4.7.4.2 Data Backup
The data backup functionality provides means to manage various device data.
It is recommended to perform external backups of the device configuration data
("Module Data" and "Device Data", see below) periodically.
The data backup functionality shows up with a table providing ten lines ("slots")
and with five buttons below the table which are grayed out initially.

The first action is to activate one of the ten slots by clicking on it, which causes the
corresponding line to be highlighted. Additionally, depending on the content of the
selected slot, two to all of the five buttons become active, thus enabling the data
backup functionality:
After operating the button, the drop down list "Type", the text field
"Description", and a button labeled appear:
With the drop down list, the type of data to be saved can be chosen:
 "Module Data"
to store the following data categories for the installed amplifiers:
● "LNB Power Settings",
● "Gain Settings",
● "Slope Settings",
● "RF Threshold Settings", and
● "Channel Settings and Names".
Please refer to chapter 5.4.4.1 for details on these settings and to the "Restore"
section of this chapter for retrieving all or only a part of these settings.
 "Device Data"
to store device specific settings accessible via the Setup Tab:
● "IP Settings" (chapter 5.4.7.2.1),
● "User Setup" (chapter 5.4.7.1), and
● "General Setup (SNMP, Device Setup…)"
(chapters 5.4.7.2.2, 5.4.7.3, including the operation mode (chapter 5.1)).
Please refer to the chapters in parentheses for details on these settings and to
the "Restore" section of this chapter for retrieving all or only a part of these
settings.

 "Error Log"
to store the current content of the Events Tab (chapter 5.4.5).
Note that "Error Log" data can neither be restored nor be imported.
For better identification, it is recommended to enter a descriptive name for the
backup set in the "Description" text field before operating the button.
In the following screenshot, the first three slots are occupied with a backup set for
each type of data. These backup sets were created in the way as described above.
As indicated, the content of the selected slot determines which of the five buttons
is active or not. In the screenshot above the button is grayed out since it is
not possible to restore the content of an "Error Log" backup set. The
button is active only if either a slot with a backup set containing "Module Data" or
"Device Data" is selected.
Note:
 A backup set can only be restored to a device with the same product number.
Otherwise the message "Error: Backup created with different device" appears
instead of the button.
If a backup set containing "Module Data" is selected as shown in the following
screenshot and the button is operated, the available data categories (as
described above) are listed. It is possible to (de-)select particular categories via the
adjacent check boxes before operating the button.

If a backup set containing "Device Data" is selected as shown in the next screenshot
and the button is operated, the available categories (as described above)
are listed. It is possible to (de-)select particular categories via the adjacent check
boxes before operating the button.
After operating the button, the appearing "File" text field permits the
insertion of a filename including the path where the file resides. Alternatively, the
button can be used to locate the file. After the file was selected, a click on
the button activates the file transfer to the device.

Note:
 Precondition for the import is a valid backup set containing "Module Data" or
"Device Data", which was generated before via the button (see below),
or which was provided by DEV Systemtechnik.
 It is always possible to import a valid backup set containing "Module Data" or
"Device Data" to a selected slot. The information, which is possibly stored in
that slot, is overwritten without any confirmation!
 If the imported backup set is to be applied to the device, the button is
to be operated after the import.
After operating the button a browser specific window pops up and suggests
the storage of the data as "backup_slot_xx" (with "xx" being the number of the slot (i.e.
the line number 01…10 of the table) to be exported). If a backup set contains
"Module Data" or "Device Data", this data is stored in an encoded binary format.
The export of an "Error Log" backup set is stored in text format similar to the
appearance in the Events Tab (chapter 5.4.5).
With the button, the content of the selected slot is deleted without any
confirmation!

5.4.7.4.3 Firmware Update

The Firmware Update entry provides means to update the device firmware,
manuals etc., and/or to reset the device via Web Interface.
Precondition for updating the device firmware is a service package provided by

DEV Systemtechnik.
The input field permits the insertion of a filename including the path where the file
resides. Alternatively, the button can be used to locate the file. After the
selection of the file, a click on the button activates the file transfer to the
device. As soon as the upload is finished, the installation is started, please observe
the text output, which appears in the "Update Status:" text window.
If –for any reason– a device reset is required, the button can be used
to reset the device even without updating the firmware.
After a click on the button, a device reset is initiated indicated via a
pop up window, e.g.:

5.4.8 Info Tab

The Info Tab provides information regarding configuration and setup of the device.
This information is mainly intended for support purposes; part of this information
may be requested when contacting DEV Systemtechnik.
In the left column, the "Hardware Configuration" is described:

 Device, here: DEV 2194
 MAC Address, here: 00-D0-93-3F-5B-6A
In the right column on the top, the "Software Configuration" is described:
 Device Firmware version, here: 32-0059 R.02
 Linux Kernel version, here: 3.14.73-S
 SNMP Software version, here: 3.1.13
 the current IP Address of the device, here: 192.168.0.11
 Web Interface Licenses, here: 1
 SNMP Licenses, here: 1
An icon is located on the bottom right for downloading the electronic version of the
user manual.
Finally, in the right column in the middle the manufacturer's name, country, and
hyperlink are listed.

5.5 Control via Remote Interface: SNMP

5.5.1 SNMP Overview
The "Simple Network Management Protocol" (SNMP) essentially is a request-reply
protocol running over UDP (usually ports 161 and 162). SNMP is an asymmetric
protocol operating between two types of management units: managers and agents.
A manager is called "Network Management Station" (NMS), which is usually a
computer on which one or more management systems are running. On small NMS,
command line tools can be used. On larger NMS normally third-party software, also
called a "network management suite" collects the data and provides a graphical
user interface.
An agent or SNMP-agent is software, which runs on a "Network Element" (NE).
NEs in a SNMP environment are called "nodes". An agent collects and stores infor-
mation from the system, translates the information in SNMP-compatible form, and
makes this information available to the manager. The agents manage the "objects"
of the node. Each object has an own individual management "Object ID" (OID).
In the system, the objects are the variables, which can be simple values or tables.
The object information is stored in the "Management Information Base" (MIB).
Note:
 The iReasoning MIB Browser Personal Edition (including Trap Receiver) by
iReasoning Inc. is recommended to test the communication via SNMP.
5.5.2 Private Enterprise Number, Device Index Number
The Private Enterprise Number of DEV Systemtechnik GmbH is 21035.
This MIB is designed in SNMP v2 compliant format starting with the object sections
.sysDevModules and .devSysMibConformance, which are not described in this
context.
The actual MIB content for DEV Systemtechnik switch systems starts with the
object section .devSwitch, which has the Device Index Number 41.
This concatenates to the string (i.e. the numerical OID: .1.3.6.1.4.1.21035.41):
iso.org.dod.internet.private.enterprises.devSystemtechnik.devSwitch
1 . 3 . 6 . 1 . 4 . 1 . 21035 . 41
Note:
 The intention for this MIB design was to keep the structure universal that it can
be applied to numerous DEV Systemtechnik products. This implies that only a
subset of the MIB functionality is applicable for this type of device.

5.5.3 The Switch MIB Tree

The MIB is stored on the controller of the device and can be downloaded via the
SNMP setup of the Web Interface (please refer to chapter 5.4.7.2.2) or directly with
a web browser via the link:
http://<IP-of-the-device>/dev-switch.mib
As shown above, the section .devSwitch is divided in four branches:

• .devSwitchTraps (chapter 5.5.4.1),
• .instrument (chapter 5.5.4.2),
• .application (chapter 5.5.4.3), and
• .surveillance (chapter 5.5.4.4).
In the corresponding sub-chapter, the content of each branch is shown expanded
and each object within a branch is described.

5.5.4 MIB Objects

In the following, the objects of the section .devSwitch in the MIB tree are
described.
The complete name of an MIB object results out of the concatenation of the MIB-
string (please refer to chapter 5.5.2):
iso.org.dod.internet.private.enterprises.devSystemtechnik.devSwitch
and of the corresponding object.

E.g., complete textual OID of the object .instrument.controllerMac is ("⌡" and "⌠"
are symbolizing that the two consecutive lines are actually not separated):
iso.org.dod.internet.private.enterprise.devSystemtechnik⌡
⌠.devSwitch.instrument.controllerMac
Note:
• Some of the objects are set to a factory default chapter 4.3.3
• The following objects can be modified in Remote Mode only:
• .portTable.portEntry.poEnable chapter 5.5.4.3.9.2
• .portTable.portEntry.poRfLimit chapter 5.5.4.3.9.6
• .portTable.portEntry.poBiasOnOff chapter 5.5.4.3.9.8
• .portTable.portEntry.poBiasLimitLo chapter 5.5.4.3.9.10
• .portTable.portEntry.poBiasLimitHi chapter 5.5.4.3.9.11
• .portTable.portEntry.poGain chapter 5.5.4.3.9.13
• .portTable.portEntry.poTilt chapter 5.5.4.3.9.15
• And some objects can be modified in all modes of operation:
• .application.controlMode chapter 5.5.4.3.1
• .surveillance.trapEnableMask chapter 5.5.4.4.1
• .surveillance.errorEnableMask chapter 5.5.4.4.2

5.5.4.1 .devSwitchTraps
Aside from the SNMP standard trap 'Cold Start Trap', this MIB additionally supports
three specific traps:
Note:
 By default, all traps are disabled.
By setting the corresponding bit in the .trapEnableMask (please refer to
chapter 5.5.4.4.1) each trap can be enabled individually.
 Traps for specific error classes can be masked out by clearing the appropriate
bits in the .errorEnableMask (chapter 5.5.4.4.2).
5.5.4.1.1 .devSwitchTraps.trapAlarmText
This trap (number 3, OID: .1.3.6.1.4.1.21035.41.0.3) is triggered if the device
detects a new error. It delivers the appropriate error message (please refer to
chapter 6.1) obtained via .errorDescription (chapter 5.5.4.4.14).
To enable the trap, bit 6 (enum: errortext) in the .trapEnableMask is to be set.
5.5.4.1.2 .devSwitchTraps.trapAlarm
This trap (number 4, OID: .1.3.6.1.4.1.21035.41.0.4) is triggered if the device either
detects a new error or if a pending error disappears. The trap delivers the .errorNr
(please refer to chapter 5.5.4.4.4.2) and .errorPending (chapter 5.5.4.4.4.5) for the
corresponding entry in the .errorTable.
Bit 5 (enum: error) in the .trapEnableMask is to be set to enable the trap.
5.5.4.1.3 .devSwitchTraps.trapModeChange
This trap (number 5, OID: .1.3.6.1.4.1.21035.41.0.5) is triggered if the device
detects that an operation mode change was performed. The trap delivers the
.controlMode (please refer to chapter 5.5.4.3.1).
To enable the trap, bit 4 (enum: modechange) in the .trapEnableMask is to be set.

5.5.4.2 .instrument
5.5.4.2.1 .instrument.controllerMac
OID: .1.3.6.1.4.1.21035.41.1.1.0
Syntax: OCTET STRING (SIZE(18))
Access: read-only
Description: The individual MAC address of the controller of the device
in hexadecimal characters separated by dashes ("-").
Example: "00-D0-93-3F-5B-6A"
5.5.4.2.2 .instrument.firmwareRevision
OID: .1.3.6.1.4.1.21035.41.1.2.0
Access: read-only
Description: The device firmware revision.
Example: "R.02"
5.5.4.2.3 .instrument.instrumentType
OID: .1.3.6.1.4.1.21035.41.1.3.0
Access: read-only
Description: The device type.
For this product, "DEV2194" is returned.
5.5.4.2.4 .instrument.antennaControllerType
OID: .1.3.6.1.4.1.21035.41.1.4.0
Syntax: INTEGER {none (0), rc2000 (1), andrew (2), aks200 (3),
hmam (4), aks250 (5)}
Access: read-only
Description: The antenna controller type.
.antennaControllerType is not implemented for this type of device.

5.5.4.3 .application
5.5.4.3.1 .application.controlMode
OID: .1.3.6.1.4.1.21035.41.2.1.0
Syntax: INTEGER {local (1), remote (2), auto (3)}
Access: read-write OR read-only
Description: The device operation mode (chapter 5.1), possible values:
"1" Local Mode: local operation at the device or
via Web Interface;
"2" Remote Mode: remote operation via SNMP;
"3" Auto Mode: is not supported for this type of device.
Note:
 The value "3" (Auto Mode) is not supported for this type of device. The
behavior of the device is not predictable if .controlMode is set to "3".
 Via the SNMP setup of the Web Interface (please refer to chapter 5.4.7.2.2)
.controlMode can be set to read-write (default) or to read-only.
 The factory setting is "2" (Remote Mode).

5.5.4.3.2 .application.switchingControl
OID: .1.3.6.1.4.1.21035.41.2.2.0
Syntax: Integer32
Access: read-write
Description: .switchingControl is still present due to backward compatibility
reasons; i.e. it has no effect on the functionality of the device.
5.5.4.3.3 .application.simultaneousMode
OID: .1.3.6.1.4.1.21035.41.2.3.0
Syntax: INTEGER {simultaneous (1), individual (2)}
Access: read-write
Description: .simultaneousMode is not supported by this type of device;
i.e. it has no effect on the functionality of the device.
5.5.4.3.4 .application.numberOfSwitchGroups
OID: .1.3.6.1.4.1.21035.41.2.4.0
Syntax: Integer32
Access: read-only
Description: The number of switch groups within the device.
This type of device does not support switch groups, thus "0" is
returned.
Note:
 This value is used to determine the maximum index of the following table:
5.5.4.3.5 .application.switchGroupTable
The table is required for products that feature switch groups, i.e. it is not relevant
for this type of device.
Therefore and due to the fact that for .numberOfSwitchGroups (please refer to
chapter 5.5.4.3.4) "0" is returned, the .switchGroupTable is not available.
5.5.4.3.5.1 .application.switchGroupTable.switchGroupEntry.swGroupIndex
OID: .1.3.6.1.4.1.21035.41.2.5.1.1.x
Syntax: Integer32 (1..32)
Access: not-accessible
Description: A unique value for each table entry ranging between "1" and the
number of entries (defined by .numberOfSwitchGroups, please
refer to chapter 5.5.4.3.4).
Not applicable for this type of device, since the .switchGroupTable
is not available.
5.5.4.3.5.2 .application.switchGroupTable.switchGroupEntry.swGroupMembers
OID: .1.3.6.1.4.1.21035.41.2.5.1.2.x
Syntax: OCTET STRING
Access: read-write
Description: A comma separated string containing the indices of the switch units
being member of the corresponding switch group.
is not available.

5.5.4.3.5.3 .application.switchGroupTable.switchGroupEntry.swMainRfStatus
OID: .1.3.6.1.4.1.21035.41.2.5.1.3.x
Syntax: INTEGER {ok (1), notok (2), notapplicable (3)}
Access: read-only
Description: The RF signal status for the main ports of the switch units being
member of the corresponding switch group.
is not available.
5.5.4.3.5.4 .application.switchGroupTable.switchGroupEntry.swRedundancyRfStatus
OID: .1.3.6.1.4.1.21035.41.2.5.1.4.x
Access: read-only
Description: The RF signal status for the redundancy ports of the switch units
being member of the corresponding switch group.
is not available.
5.5.4.3.6 .application.numberOfSwitchUnits
OID: .1.3.6.1.4.1.21035.41.2.6.0
Syntax: Integer32
Access: read-only
Description: The number of switch units within the device.
This type of device does not support switch units, thus "0" is
returned.
Note:
5.5.4.3.7 .application.switchUnitTable
The table is required for products that feature switch units, i.e. it is not relevant for
this type of device.
Therefore and due to the fact that for .numberOfSwitchUnits (please refer to
chapter 5.5.4.3.6) "0" is returned, the .switchUnitTable is not available.
5.5.4.3.7.1 .application.switchUnitTable.switchUnitEntry.swIndex
OID: .1.3.6.1.4.1.21035.41.2.7.1.1.x
number of entries (defined by .numberOfSwitchUnits, please refer
to chapter 5.5.4.3.6).
Not applicable for this type of device, since the .switchUnitTable is
not available.

5.5.4.3.7.2 .application.switchUnitTable.switchUnitEntry.swSize
OID: .1.3.6.1.4.1.21035.41.2.7.1.2.x
Syntax: Integer32
Access: read-only
Description: The size of the switch unit.
not available.
5.5.4.3.7.3 .application.switchUnitTable.switchUnitEntry.swMembers
OID: .1.3.6.1.4.1.21035.41.2.7.1.3.x
Access: read-only
Description: A comma separated string that is interpreted as integers, con-
taining the indices of the ports in the .portTable (please refer to
chapter 5.5.4.3.9) being member of the switch unit.
not available.
5.5.4.3.7.4 .application.switchUnitTable.switchUnitEntry.swPosition
OID: .1.3.6.1.4.1.21035.41.2.7.1.4.x
Syntax: Integer32
Access: read-write
Description: The switching status of the related switch unit.
not available.
5.5.4.3.8 .application.numberOfPorts
OID: .1.3.6.1.4.1.21035.41.2.8.0
Access: read-only
Description: The number of ports with special properties within the device.
Each amplifier is considered as a single port, thus "2" is returned.
Note:
 This value determines the maximum index of the following table:
5.5.4.3.9 .application.portTable
The .portTable describes the special features and settings of each amplifier.
5.5.4.3.9.1 .application.portTable.portEntry.portIndex
OID: .1.3.6.1.4.1.21035.41.2.9.1.1.x
number of entries (defined by .numberOfPorts, chapter 5.5.4.3.8).

5.5.4.3.9.2 .application.portTable.portEntry.poEnable
OID: .1.3.6.1.4.1.21035.41.2.9.1.2.x
Syntax: INTEGER {disabled (1), enabled (2)}
Access: read-write
Description: Error messages possibly caused by the port are (or can be) enabled
or disabled.
Note:
 The factory setting is "2" (enabled).
5.5.4.3.9.3 .application.portTable.portEntry.poType
OID: .1.3.6.1.4.1.21035.41.2.9.1.3.x
Access: read-only
Description: The functionality of the port.
For this type of device, "0" is returned for all ports.
5.5.4.3.9.4 .application.portTable.portEntry.poHasRfSense
OID: .1.3.6.1.4.1.21035.41.2.9.1.4.x
Syntax: INTEGER {yes (1), no (2)}
Access: read-only
Description: The indication whether RF level information is provided or not.
For this type of device, "1" (yes) is returned for all ports.
5.5.4.3.9.5 .application.portTable.portEntry.poRfSense
OID: .1.3.6.1.4.1.21035.41.2.9.1.5.x
Syntax: Integer32
Access: read-only
Description: The measured RF level in [dBm/10].
"9999" means not available or not present.
Example: "-129" ≡ -12.9 dBm
5.5.4.3.9.6 .application.portTable.portEntry.poRfLimit
OID: .1.3.6.1.4.1.21035.41.2.9.1.6.x
Syntax: Integer32
Access: read-write
Description: The RF threshold level in [dBm/10].
Note:
 The factory setting is stated in chapter 4.3.1.
5.5.4.3.9.7 .application.portTable.portEntry.poHasBias
OID: .1.3.6.1.4.1.21035.41.2.9.1.7.x
Access: read-only
Description: The indication whether bias (i.e. LNB power) is provided or not.

5.5.4.3.9.8 .application.portTable.portEntry.poBiasOnOff
OID: .1.3.6.1.4.1.21035.41.2.9.1.8.x
Syntax: INTEGER {no (0), on (1), off (2), vertlow (3), horlow (4),
verthigh (5), horhigh (6)}
Access: read-write
Description: The LNB power (or bias) supply state can be read or set,
possible values:
"0" no: is not returned for this type of device;
"1" on: is supported only for some configurations (see below);
"2" off: LNB power is (to be) turned off;
otherwise (see below):
LNB power is (to be) turned on & (to be) set to polarization/band
"3" VL (vertical low: 13 V, 0 Hz),
"4" HL (horizontal low: 18 V, 0 Hz),
"5" VH (vertical high: 13 V, 22 kHz), or
"6" HH (horizontal high: 18 V, 22 kHz).
Note:
 The factory setting is "2" (off).
 In certain DEV 2194 configurations, .poBiasOnOff supports the value "1" (on)
for the VL mode (13 V, 0 Hz), instead of the polarization/band values "3"…"6".
5.5.4.3.9.9 .application.portTable.portEntry.poBiasCurrent
OID: .1.3.6.1.4.1.21035.41.2.9.1.9.x
Syntax: Integer32
Access: read-only
Description: The measured current in [mA/10].
Example: "1850" ≡ 185.0 mA
5.5.4.3.9.10 .application.portTable.portEntry.poBiasLimitLo
OID: .1.3.6.1.4.1.21035.41.2.9.1.10.x
Access: read-write
Description: The lower limit of the current monitoring interval in [mA/10].
Example: "1000" ≡ 100.0 mA
Note:
5.5.4.3.9.11 .application.portTable.portEntry.poBiasLimitHi
OID: .1.3.6.1.4.1.21035.41.2.9.1.11.x
Access: read-write
Description: The upper limit of the current monitoring interval in [mA/10].
Example: "2500" ≡ 250.0 mA
Note:

5.5.4.3.9.12 .application.portTable.portEntry.poHasGain
OID: .1.3.6.1.4.1.21035.41.2.9.1.12.x
Syntax: INTEGER {yes (1), no (2), (0)}
Access: read-only
Description: The indication whether gain control is provided or not.
5.5.4.3.9.13 .application.portTable.portEntry.poGain
OID: .1.3.6.1.4.1.21035.41.2.9.1.13.x
Syntax: Integer32
Access: read-write
Description: The gain control value in [dB/10].
Example: "50" ≡ +5.0 dB
Note:
5.5.4.3.9.14 .application.portTable.portEntry.poHasTilt
OID: .1.3.6.1.4.1.21035.41.2.9.1.14.x
Syntax: INTEGER {yes (1), no (2), (0)}
Access: read-only
Description: The indication whether slope (or tilt) control is provided or not.
5.5.4.3.9.15 .application.portTable.portEntry.poTilt
OID: .1.3.6.1.4.1.21035.41.2.9.1.15.x
Syntax: Integer32
Access: read-write
Description: The slope (or tilt) setting in [dB/10].
Example: "20" ≡ +2.0 dB
Note:
5.5.4.3.9.16 .application.portTable.portEntry.poCardType
OID: .1.3.6.1.4.1.21035.41.2.9.1.16.x
Access: read-only
Description: The DEV number of the module (here: amplifier) to which the port
belongs to.
"11-0081" (for a DEV 11-0081) is returned for all ports.

5.5.4.3.9.17 .application.portTable.portEntry.poSlot
OID: .1.3.6.1.4.1.21035.41.2.9.1.17.x
Access: read-only
Description: The "slot location" of the module (here: amplifier) to which the
port belongs to.
"Amp1" is returned for the first amplifier and "Amp2" is returned
for the second amplifier.
5.5.4.3.9.18 .application.portTable.portEntry.poRfSenseStatus
OID: .1.3.6.1.4.1.21035.41.2.9.1.18.x
Syntax: INTEGER {(0), ok (1), notok (2), notapplicable (3)}
Access: read-only
Description: The status of the RF level monitoring, possible values:
"0" is not returned for this type of device;
"1" ok: the RF level is above the RF threshold level;
"2" not ok: the RF level is below the RF threshold level;
"3" not applicable: is not returned for this type of device.
5.5.4.3.9.19 .application.portTable.portEntry.poBiasStatus
OID: .1.3.6.1.4.1.21035.41.2.9.1.19.x
Syntax: INTEGER {(0), ok (1), notok (2), notapplicable (3)}
Access: read-only
Description: The status of the LNB (bias) current monitoring, possible values:
"0" is not returned for this type of device;
"1" ok: the current is within the defined current monitoring
interval (or LNB power is turned off);
"2" not ok: the current exceeds the defined current monitoring
interval;
5.5.4.3.9.20 .application.portTable.portEntry.poLightStatus
OID: .1.3.6.1.4.1.21035.41.2.9.1.20.x
Access: read-only
Description: The light detection status.
For this type of device, "3" (notapplicable) is returned for all ports.
5.5.4.3.9.21 .application.portTable.portEntry.poCardStatus
OID: .1.3.6.1.4.1.21035.41.2.9.1.21.x
Access: read-only
Description: The health status of the module (here: amplifier) to which the port
belongs to, possible values:
"1" ok: no errors are reported for the module;
"2" not ok: an error was detected for the module;

5.5.4.3.9.22 .application.portTable.portEntry.poGainMode
OID: .1.3.6.1.4.1.21035.41.2.9.1.22.x
Syntax: INTEGER {notapplicable (0), manual (1), auto (2), mute (3)}
Access: read-write
Description: For this type of device, the gain mode can be read only, the only
possible value is
"1" manual: since the applied amplifiers provide manual gain
control functionality.
Note:
 The values "0" (not applicable), "2" (auto), and "3" (mute) are not supported by
this type of device.
5.5.4.3.9.23 .application.portTable.portEntry.poOutputPowerSetpoint
OID: .1.3.6.1.4.1.21035.41.2.9.1.23.x
Syntax: Integer32
Access: read-write
Description: The automatic gain control set point.
For this type of device, "9999" is returned for all ports.
5.5.4.3.9.24 .application.portTable.portEntry.poHasInputPower
OID: .1.3.6.1.4.1.21035.41.2.9.1.24.x
Access: read-only
Description: The indication whether input power measurement capability is
provided or not.
.poHasInputPower is not implemented for this type of device.
5.5.4.3.9.25 .application.portTable.portEntry.poInputPower
OID: .1.3.6.1.4.1.21035.41.2.9.1.25.x
Syntax: Integer32
Access: read-only
Description: The measured input power in [dBm/10].
.poInputPower is not implemented for this type of device.
5.5.4.3.9.26 .application.portTable.portEntry.poInputPowerLimit
OID: .1.3.6.1.4.1.21035.41.2.9.1.26.x
Syntax: Integer32
Access: read-write
Description: The lower limit of the input power in [dBm/10].
.poInputPowerLimit is not implemented for this type of device.

5.5.4.3.9.27 .application.portTable.portEntry.poHasOutputPower
OID: .1.3.6.1.4.1.21035.41.2.9.1.27.x
Access: read-only
Description: The indication whether output power measurement capability is
provided or not.
.poHasOutputPower is not implemented for this type of device.
5.5.4.3.9.28 .application.portTable.portEntry.poOutputPower
OID: .1.3.6.1.4.1.21035.41.2.9.1.28.x
Syntax: Integer32
Access: read-only
Description: The measured output power in [dBm/10].
.poOutputPower is not implemented for this type of device.
5.5.4.3.9.29 .application.portTable.portEntry.poDWDMChannelNumber
OID: .1.3.6.1.4.1.21035.41.2.9.1.29.x
Syntax: Integer32
Access: read-only
Description: The channel number for DWDM Tx modules.
.poDWDMChannelNumber is not implemented for this type of
device.
5.5.4.3.10 .application.antennaStatus
OID: .1.3.6.1.4.1.21035.41.2.10.0
Syntax: INTEGER {moving (1), rfok (2), rfnok (3), (0)}
Access: read-only
Description: The status of the motorized antenna.
.antennaStatus is not implemented for this type of device.
5.5.4.3.11 .application.antennaPosition
OID: .1.3.6.1.4.1.21035.41.2.11.0
Syntax: Integer32
Access: read-only
Description: The position of the motorized antenna.
.antennaPosition is not implemented for this type of device.
5.5.4.3.12 .application.numberOfMatrixOutputs
OID: .1.3.6.1.4.1.21035.41.2.12.0
Syntax: INTEGER (0..128)
Access: read-only
Description: The number of matrix output ports.
Not applicable for this type of device, thus "0" is returned.

5.5.4.3.13 .application.numberOfMatrixInputs
OID: .1.3.6.1.4.1.21035.41.2.13.0
Access: read-only
Description: The number of matrix input ports.
Not applicable for this type of device, thus "0" is returned.
5.5.4.3.14 .application.selectCrosspointSwitchingMode
OID: .1.3.6.1.4.1.21035.41.2.14.0
Syntax: INTEGER {tablemode (1), stringmode (2)}
Access: read-write
Description: The switching mode of the matrix.
.selectCrosspointSwitchingMode is not supported by this type of
device; i.e. it has no effect on the functionality of the device.
5.5.4.3.15 .application.activeCrosspointSetting
OID: .1.3.6.1.4.1.21035.41.2.15.0
Access: read-write
Description: The selection of a string from the .crosspointStringTable (please
refer to chapter 5.5.4.3.16) to apply the corresponding switching
scenario.
.activeCrosspointSetting is not supported by this type of device; i.e.
it has no effect on the functionality of the device.
5.5.4.3.16 .application.crosspointStringTable
The .crosspointStringTable is not implemented for this type of device.
5.5.4.3.16.1 .application.crosspointStringTable.crosspointStringEntry.crosspointStringIndex
OID: .1.3.6.1.4.1.21035.41.2.16.1.1.x
Access: read-only
number of entries (i.e. "16").
Not applicable for this type of device, since the
.crosspointStringTable is not implemented.
5.5.4.3.16.2 .application.crosspointStringTable.crosspointStringEntry.crosspointString
OID: .1.3.6.1.4.1.21035.41.2.16.1.2.x
Access: read-write
Description: A comma separated string that is interpreted as integers describing
a switching scenario of the matrix.
Not applicable for this type of device, since the
.crosspointStringTable is not implemented.

5.5.4.3.17 .application.crosspointTable
The .crosspointTable is not available for this type of device due to the fact that for
.numberOfMatrixOutputs (please refer to chapter 5.5.4.3.12) "0" is returned.
5.5.4.3.17.1 .application.crosspointTable.crosspointEntry.outChNr
OID: .1.3.6.1.4.1.21035.41.2.17.1.1.x
Access: read-only
number of entries (defined by .numberOfMatrixOutputs, please
Not applicable for this type of device, since the .crosspointTable is
not available.
5.5.4.3.17.2 .application.crosspointTable.crosspointEntry.inChNr
OID: .1.3.6.1.4.1.21035.41.2.17.1.2.x
Access: read-write
Description: The number of the input port to which the corresponding output
port is (to be) connected to.
Not applicable for this type of device, since the .crosspointTable is
not available.

5.5.4.4 .surveillance

5.5.4.4.1 .surveillance.trapEnableMask
OID: .1.3.6.1.4.1.21035.41.3.1.0
Syntax: BITS {unused4 (0), unused3 (1), unused2 (2), unused1 (3),
modechange (4), error (5), errortext (6), coldstart (7)}
Access: read-write
Description: Trap enable mask: A trap is enabled if the corresponding bit is set.
Note:
 The .trapEnableMask is defined as follows:
Hex 80 40 20 10 08 04 02 01
BITS 0 1 2 3 4 5 6 7
Trap unused4 unused3 unused2 unused1 modechange error errortext coldstart
I.e. only bits 4…7 are supported; please refer to chapter 5.5.4.1.
 Note the differences for the Set-method of the .trapEnableMask
(BITS has the reverse order vs. hex addressing via OCTET STRING
(e.g. writing of "0x0F" to enable all supported traps)).
 By default all traps are disabled, i.e. all bits are zero.
5.5.4.4.2 .surveillance.errorEnableMask
OID: .1.3.6.1.4.1.21035.41.3.2.0
Access: read-write
Description: Error enable mask: If all bits are 1, then all errors are enabled; the
errors are grouped into classes; each error class can be masked out
with its corresponding bit set to 0.
Note:
 The .errorEnableMask is defined as follows:
Hex 8000 4000 2000 1000 0800 0400 0200 0100 0080 0040 0020 0010 0008 0004 0002 0001
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Class ANT COM LNB OPT AMP MAT OUT INP SWI FAN POW INT
Bit Class Class Class Reference

Number Abbreviation Name (Chapter)
0 0 INT Internal Error 6.1.3
1 1 POW Power Supply (no reference)
2 2 FAN Fan (no reference)
3 3 SWI Switch Module (no reference)
4 4 INP Input Module 6.1.1
5 5 OUT Output Module (no reference)
6 6 MAT Matrix Module (no reference)
7 7 AMP Amplifier Module 6.1.2
8 8 OPT Optical Module (no reference)
9 9 LNB LNB Power 6.1.2
10 A COM Communication 6.1.3
11 B ANT Antenna Controller (no reference)
12 C (future use) (no reference)
13 D (future use) (no reference)
14 E (future use) (no reference)
15 F (future use) (no reference)
 If an error class is masked out, an appearing or disappearing error of this class is

not generating a trap and will not appear/disappear in the Active Events
Window of the Web Interface.

The error and its status (pending or not) are still stated in the .errorTable and in
the Events Tab of the Web Interface where the error can be acknowledged and
deleted (if it is not pending anymore).
 By default all errors are enabled, i.e. the .errorEnableMask is "65535".
5.5.4.4.3 .surveillance.numberOfErrors
OID: .1.3.6.1.4.1.21035.41.3.3.0
Syntax: Integer32
Access: read-only
Description: The number of errors.
Note:
5.5.4.4.4 .surveillance.errorTable
The .errorTable can contain entries that are classified by an error number. An error
count per entry indicates the number of occurrences of the specific error, and
furthermore there it is specified per entry when the last error of this type did occur,
whether the error is still pending, and whether the error was acknowledged or not.
If .numberOfErrors (please refer to chapter 5.5.4.4.3) is "0", the .errorTable is not
available.
5.5.4.4.4.1 .surveillance.errorTable.errorEntry.errorIndex
OID: .1.3.6.1.4.1.21035.41.3.4.1.1.x
number of entries (defined by .numberOfErrors, chapter 5.5.4.4.3).
5.5.4.4.4.2 .surveillance.errorTable.errorEntry.errorNr
OID: .1.3.6.1.4.1.21035.41.3.4.1.2.x
Syntax: Integer32
Access: read-only
Description: The error code.
Example: "31744" (for a "RF Sense Port 1" error, please refer to chapter 6.1)
5.5.4.4.4.3 .surveillance.errorTable.errorEntry.errorCount
OID: .1.3.6.1.4.1.21035.41.3.4.1.3.x
Syntax: Integer32
Access: read-only
Description: The number of occurrences of the error.
5.5.4.4.4.4 .surveillance.errorTable.errorEntry.errorDateTime
OID: .1.3.6.1.4.1.21035.41.3.4.1.4.x
Syntax: Integer32
Access: read-only
Description: The last occurrence of the error
(Unix time stamp, seconds since 01-Jan-1970 00:00:00 UTC).
Example: "1500397667" ≡ 18-Jul-2017 17:07:47 CEST

5.5.4.4.4.5 .surveillance.errorTable.errorEntry.errorPending
OID: .1.3.6.1.4.1.21035.41.3.4.1.5.x
Syntax: INTEGER {pending (1), gone (2)}
Access: read-only
Description: The last occurrence of the error is
"1" still pending, or
"2" not pending anymore, i.e. gone.
5.5.4.4.4.6 .surveillance.errorTable.errorEntry.errorAcknowledge
OID: .1.3.6.1.4.1.21035.41.3.4.1.6.x
Syntax: INTEGER {notAcknowledged (1), acknowledged (2)}
Access: read-only
Description: The last occurrence of the error is
"1" not acknowledged, or
"2" acknowledged.
5.5.4.4.5 .surveillance.numberOfPowerLines
OID: .1.3.6.1.4.1.21035.41.3.5.0
Syntax: Integer32
Access: read-only
Description: The number of power lines.
This type of device does not support monitoring for the power line,
thus "0" is returned.
Note:
5.5.4.4.6 .surveillance.powerLineTable
The .powerLineTable is required for products that support power line monitoring,
i.e. it is not relevant for this type of device. Therefore and due to the fact that for
.numberOPowerLines (please refer to chapter 5.5.4.4.5) "0" is returned, the
.powerLineTable is not available.
5.5.4.4.6.1 .surveillance.powerLineTable.powerLineEntry.powerLineIndex
OID: .1.3.6.1.4.1.21035.41.3.6.1.1.x
number of entries (defined by .numberOfPowerLines, please refer
to chapter 5.5.4.4.5).
Not applicable for this type of device, since the .powerLineTable is
not available.
5.5.4.4.6.2 .surveillance.powerLineTable.powerLineEntry.powerLineStatus
OID: .1.3.6.1.4.1.21035.41.3.6.1.2.x
Access: read-only
Description: The status of the related power line. Not applicable for this type of
device, since the .powerLineTable is not available.

5.5.4.4.7 .surveillance.numberOfPowerSupplies
OID: .1.3.6.1.4.1.21035.41.3.7.0
Syntax: Integer32
Access: read-only
Description: The number of power supplies.
This type of device does not support monitoring for the power
supply, thus "0" is returned.
Note:
5.5.4.4.8 .surveillance.powerSupplyTable
The .powerSupplyTable is required for products that support power supply
monitoring, i.e. it is not relevant for this type of device. Therefore and due to the
fact that for .numberOfPowerSupplies (please refer to chapter 5.5.4.4.7) "0" is
returned, the .powerSupplyTable is not available.
5.5.4.4.8.1 .surveillance.powerSupplyTable.powerSupplyEntry.powerSupplyIndex
OID: .1.3.6.1.4.1.21035.41.3.8.1.1.x
number of entries (defined by .numberOfPowerSupplies, please
Not applicable for this type of device, since the .powerSupplyTable
is not available.
5.5.4.4.8.2 .surveillance.powerSupplyTable.powerSupplyEntry.powerSupplyStatus
OID: .1.3.6.1.4.1.21035.41.3.8.1.2.x
Access: read-only
Description: The status of the related power supply.
Not applicable for this type of device, since the .powerSupplyTable
is not available.
5.5.4.4.9 .surveillance.numberOfFans
OID: .1.3.6.1.4.1.21035.41.3.9.0
Syntax: Integer32
Access: read-only
Description: The number of fans.
This type of device provides no fans, thus "0" is returned.
Note:
5.5.4.4.10 .surveillance.fanTable
The .fanTable is required for products that provide fans, i.e. it is not relevant for
this type of device. Therefore and due to the fact that for .numberOfFans (please
refer to chapter 5.5.4.4.9) "0" is returned, the .fanTable is not available.

5.5.4.4.10.1 .surveillance.fanTable.fanEntry.fanIndex
OID: .1.3.6.1.4.1.21035.41.3.10.1.1.x
number of entries (defined by .numberOfFans, please refer to
chapter 5.5.4.4.9). Not applicable for this type of device, since the
.fanTable is not available.
5.5.4.4.10.2 .surveillance.fanTable.fanEntry.fanStatus
OID: .1.3.6.1.4.1.21035.41.3.10.1.2.x
Syntax: INTEGER {ok (1), notok (2)}
Access: read-only
Description: The status of the related fan.
Not applicable for this type of device, since the .fanTable is not
available.
5.5.4.4.11 .surveillance.internalDeviceStatus
OID: .1.3.6.1.4.1.21035.41.3.11.0
Syntax: INTEGER {ok (1), notok (2)}
Access: read-only
Description: The internal device status (e.g. temperature, communication),
possible values:
"1" ok: no internal device errors are reported;
"2" not ok: an internal device error was detected.
5.5.4.4.12 .surveillance.externalDeviceStatus
OID: .1.3.6.1.4.1.21035.41.3.12.0
Access: read-only
Description: The status of external devices, e.g. of an antenna controller.
There are no external devices available for the DEV 2194, thus
"3" (notapplicable) is returned.
5.5.4.4.13 .surveillance.supportHardwareStatus
OID: .1.3.6.1.4.1.21035.41.3.13.0
Access: read-only
Description: The status of supporting hardware, e.g. of a digital interface
module. There is no supporting hardware available for the
DEV 2194, thus "3" (notapplicable) is returned.
5.5.4.4.14 .surveillance.errorDescription
OID: .1.3.6.1.4.1.21035.41.3.14.0
Syntax: OCTET STRING (SIZE(1..48))
Access: accessible-for-notify
Description: .errorDescription contains the latest error description string, which
is used for .trapAlarmText; please refer to chapter 5.5.4.1.1.

6 Error Indication
The indication of an error is realized via hardware, i.e. via red LEDs and additionally
via software, i.e. via Web Interface, via an SNMP trap, or by polling the
corresponding SNMP object(s). The hardware indication via LEDs is described in
chapter 3.1.1. The indication via Web Interface is subject of chapters 5.4.3 & 5.4.5;
the indication via SNMP is explained in chapters 5.5.4.1 & 5.5.4.4. The software
error indication (i.e. the error codes) is described in the following.
6.1 Software Error Indication
The device is capable to detect several types of errors that are reported to the Web
Interface and to the M&C system. Either the M&C system has to poll the device for
these errors or it is informed via an alarm trap, assuming that the specific SNMP
trap is enabled.
6.1.1 LED Unit Error
The communication with the LED unit at the front of the device is monitored and a
corresponding error is reported in case of a failure.
Error Code Description
Decimal Hexadecimal
16640 0x4100 Input Module 1
6.1.2 Amplifier Errors

Two amplifiers are installed in the DEV 2194. The different functionalities of the
amplifiers are monitored. Error indication is provided for the communication with
the amplifiers, for the temperature, for the amplifier supply current, for the RF
level functionality, and for the LNB power (or bias) current monitoring functionality.
Decimal Hexadecimal
30976…30977 0x7900…0x7901 Amplifier [i] (i = {1…2})
31232…31233 0x7A00…0x7A01 Overtemp Module [i] (i = {1…2})
31488…31589 0x7B00…0x7B01 Overcurr Module [i] (i = {1…2})
31744…31745 0x7C00…0x7C01 RF Sense Port [i] (i = {1…2})
36864…36865 0x9000…0x9001 Bias Limit Port [i] (i = {1…2})
6.1.3 Other Errors

For the sake of completeness, the other error codes that might be reported by the
device are listed here. If experiencing one of these errors, please contact
DEV Systemtechnik for assistance.
Decimal Hexadecimal
2560 0x0A00 Internal
41472 0xA200 No Communication Module 1

7 Connectors
AC Power Plug 2
Connector: IEC rubber connector (male) IEC 60320 C14 3
1
Connector screws: none
AC Power Plug
Pin Functionality
Pin 1 L (Live/Phase)
Pin 2 PE (Protective Earth)
Pin 3 N (Neutral)
Ethernet Connector
Connector: RJ-45
Connector assembly: none
Ethernet Connector
Pin Functionality
Pin 1 Tx+ 1 8
Pin 2 Tx-
Pin 3 Rx+
Pins 4…5 do not use
Pin 6 Rx-
Pins 7…8 do not use
• "do not use" means that normally the pin should be left open.
8 Technical Data
The technical data is stated in the DEV 2194 spec sheet; please refer to
www.dev-systemtechnik.com.

9 Conformance Declarations
9.1 Certificate of Conformance
Since DEV Systemtechnik develops and produces in Germany, the Certificate of
Conformance for each product or product series is to be issued in German
(as stated on the next page).
For the ease of comprehension, the harmonized standards that were taken into
consideration during development and production are listed here in English:
DIN EN 50083-2:2016-03 Cable networks for television signals, sound signals and interactive services -
Part 2: Electromagnetic compatibility for equipment;
German version EN 50083-2:2012 + A1:2015
DIN EN 55022:2011-12 Information technology equipment - Radio disturbance characteristics -
Limits and methods of measurement
(CISPR 22:2008, modified); German version EN 55022:2010
DIN EN 55024:2016-05 Information technology equipment - Immunity characteristics -
Limits and methods of measurement
(CISPR 24:2010 + Cor.:2011 + A1:2015); German version EN 55024:2010 + A1:2015
DIN EN 61000-3-2:2015-03 Electromagnetic compatibility (EMC) - Part 3-2: Limits -
Limits for harmonic current emissions (equipment input current ≤ 16 A per phase)
(IEC 61000-3-2:2014); German version EN 61000-3-2:2014
DIN EN 61000-3-3:2014-03 Electromagnetic compatibility (EMC) - Part 3-3: Limits -
Limitation of voltage changes, voltage fluctuations, and flicker in public low-voltage
supply systems, for equipment with rated current ≤16 A per phase and not subject to
conditional connection
(IEC 61000-3-3:2013); German version EN 61000-3-3:2013
DIN EN 62368-1:2016-05 Audio/video, information and communication technology equipment -
Part 1: Safety requirements
(IEC 62368-1:2014, modified + Cor.:2015);
German version EN 62368-1:2014 + AC:2015

Konformitätserklärung nach
EMV-Richtlinie (2014/30/EU)
Niederspannungsrichtlinie (2014/35/EU)
Der Hersteller: DEV Systemtechnik GmbH

Grüner Weg 4A
61169 Friedberg
erklärt hiermit in alleiniger Verantwortung, dass nachfolgend bezeichnetes Produkt in der von uns in Verkehr
gebrachten Ausführung:
Produktbezeichnung: Aktiver 2 * 1:8 oder 1:16 L-Band Splitter

Produktnummer: DEV 2194
Baujahr: ab 2013
auf das sich diese Erklärung bezieht, mit den folgenden Normen übereinstimmt.
Bei der Konzipierung und beim Bau des Gerätes wurden die folgenden harmonisierten Normen berücksichtigt:
DIN EN 50083-2:2016-03 Kabelnetze für Fernsehsignale, Tonsignale und interaktive Dienste -

Teil 2: Elektromagnetische Verträglichkeit von Geräten;
Deutsche Fassung EN 50083-2:2012 + A1:2015
DIN EN 55022:2011-12 Einrichtungen der Informationstechnik - Funkstöreigenschaften -
Grenzwerte und Messverfahren
(CISPR 22:2008, modifiziert); Deutsche Fassung EN 55022:2010
DIN EN 55024:2016-05 Einrichtungen der Informationstechnik - Störfestigkeitseigenschaften -
Grenzwerte und Prüfverfahren
(CISPR 24:2010 + Cor.:2011 + A1:2015); Deutsche Fassung EN 55024:2010 + A1:2015
DIN EN 61000-3-2:2015-03 Elektromagnetische Verträglichkeit (EMV) - Teil 3-2: Grenzwerte -
Grenzwerte für Oberschwingungsströme (Geräte-Eingangsstrom ≤16 A je Leiter)
(IEC 61000-3-2:2014); Deutsche Fassung EN 61000-3-2:2014
DIN EN 61000-3-3:2014-03 Elektromagnetische Verträglichkeit (EMV) - Teil 3-3: Grenzwerte -
Begrenzung von Spannungsänderungen, Spannungsschwankungen und Flicker in
öffentlichen Niederspannungs-Versorgungsnetzen für Geräte mit einem
Bemessungsstrom ≤16 A je Leiter, die keiner Sonderanschlussbedingung unterliegen
(IEC 61000-3-3:2013); Deutsche Fassung EN 61000-3-3:2013
DIN EN 62368-1:2016-05 Einrichtungen für Audio/Video-, Informations- und Kommunikationstechnik -
Teil 1: Sicherheitsanforderungen
(IEC 62368-1:2014, modifiziert + Cor.:2015);
Deutsche Fassung EN 62368-1:2014 + AC:2015
DEV Systemtechnik GmbH _____________________________

Friedberg, 18.07.2017 Jörg Schmidt
Managing Director

(This Page Intentionally Left Blank)

9.2 EU Declaration of Conformity

As original manufacturer of Electrical & Electronic Equipment (EEE)
DEV Systemtechnik GmbH

Grüner Weg 4A
61169 Friedberg
GERMANY
declares under sole responsibility that the
Product:
DEV 2194 L-Band distribution amplifier
to which this declaration refers to, is in conformity with Directive 2011/65/EU of the European Parliament and of
the Council of 8-Jun-2011 on the restriction of the use of certain hazardous substances in electrical and electronic
equipment (RoHS).
Signed for and on behalf of DEV Systemtechnik GmbH
Name: Jörg Schmidt
Position: Managing Director
Place and date of issue: Friedberg, 18-Jul-2017
Signature:

10 Glossary
AC Alternating Current
CEST Central European Summer Time
CET Central European Time
DC Direct Current
DWDM Dense Wavelength Division Multiplex (optical multiplexing technology)
HH Horizontal High (18 V, 22 kHz) (see also → HL, → VL, → VH): LNB power supply mode
HL Horizontal Low (18 V, 0 Hz) (see also → HH, → VL, → VH): LNB power supply mode
IP Internet Protocol
LED Light Emitting Diode
LNB Low Noise Block Converter
M&C System Management and Control System
MAC Media Access Control (address) is the hardware address for the
unique identification of a device within a network.
MIB Management Information Base
NE Network Element
NMS Network Management System
NTP Network Time Protocol
OID Object IDentifier
PC Personal Computer
RF Radio Frequency
RU Rack Unit: Units of vertical height. 1 RU = 1 ¾" = 44.45 mm
Sometimes simply referred to as "U" (Unit).
SNMP Simple Network Management Protocol
TCP Transmission Control Protocol
TCP/IP TCP/Internet Protocol
UDP User Datagram Protocol
URL Uniform Resource Locator
UTC Universal Time Coordinated
VH Vertical High (13 V, 22 kHz) (see also → HH, → HL, → VL): LNB power supply mode
VL Vertical Low (13 V, 0 Hz) (see also → HH, → HL, → VH): LNB power supply mode

11 Notes

DEV 2194 (Manual) PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

DEV 2194 (Manual) PDF

Caricato da

Copyright:

Formati disponibili

User Manual

L-Band Distribution Amplifier

DEV Systemtechnik GmbH

2  Copyright DEV Systemtechnik GmbH 2013-2017

5.4.5 Events Tab ------------------------------------------------------------------------------ 23

 Copyright DEV Systemtechnik GmbH 2013-2017 3

4  Copyright DEV Systemtechnik GmbH 2013-2017

5.5.4.4.8 .surveillance.powerSupplyTable ------------------------------------------------------------------------- 62

6 Error Indication ----------------------------------------------------------- 64

 Copyright DEV Systemtechnik GmbH 2013-2017 5

2.2 Limitation of Warranty

6  Copyright DEV Systemtechnik GmbH 2013-2017

 Copyright DEV Systemtechnik GmbH 2013-2017 7

 Operation status LED "Op." (7 & 15)

8  Copyright DEV Systemtechnik GmbH 2013-2017

 "RF" level status LED (9 & 17)

 Copyright DEV Systemtechnik GmbH 2013-2017 9

3.1.3 Distribution Amplifier Operation Modes

In p u t A m p lifie r 1 A m p lifie r 1 In 1 :8 O u tp u t A m p lifie r 1 (4 )

10  Copyright DEV Systemtechnik GmbH 2013-2017

3.2 Product Drawings

Fuse 2 A T A m p lifie r 1 A m p lifie r 2

 Copyright DEV Systemtechnik GmbH 2013-2017 11

4.2 Installation of the Product

12  Copyright DEV Systemtechnik GmbH 2013-2017

 Copyright DEV Systemtechnik GmbH 2013-2017 13

14  Copyright DEV Systemtechnik GmbH 2013-2017

4.4 Communication Interface Configuration

4.5 Maintenance of the Product

 Copyright DEV Systemtechnik GmbH 2013-2017 15

5 Operation of the Product

16  Copyright DEV Systemtechnik GmbH 2013-2017

5.4 Operation via the Web Interface

To log on the first time use the factory default account:

 Copyright DEV Systemtechnik GmbH 2013-2017 17

The labels "SystemName" and "SystemLocation" are the SNMP variables

If the device is operational (again), the screen usually automatically changes to

 It is recommended to add user(s) AND to change the password of the factory

18  Copyright DEV Systemtechnik GmbH 2013-2017

 Copyright DEV Systemtechnik GmbH 2013-2017 19

20  Copyright DEV Systemtechnik GmbH 2013-2017

5.4.4 Control Tab

 Copyright DEV Systemtechnik GmbH 2013-2017 21

22  Copyright DEV Systemtechnik GmbH 2013-2017

values of these entries may be altered within certain ranges.

5.4.5 Events Tab

 Copyright DEV Systemtechnik GmbH 2013-2017 23

24  Copyright DEV Systemtechnik GmbH 2013-2017

 Copyright DEV Systemtechnik GmbH 2013-2017 25

Three buttons are located at the bottom of the Recording Tab:

26  Copyright DEV Systemtechnik GmbH 2013-2017

After import and formatting the "Time" columns to the format

 Copyright DEV Systemtechnik GmbH 2013-2017 27

5.4.7 Setup Tab

28  Copyright DEV Systemtechnik GmbH 2013-2017

5.4.7.1 User Setup

 Copyright DEV Systemtechnik GmbH 2013-2017 29

 It is not possible to delete the ADMIN user but it is recommended to change

30  Copyright DEV Systemtechnik GmbH 2013-2017

5.4.7.2 System Setup

 Copyright DEV Systemtechnik GmbH 2013-2017 31

A click on the button applies the changes made.

32  Copyright DEV Systemtechnik GmbH 2013-2017