Академический Документы
Профессиональный Документы
Культура Документы
MCU
TCP/IP adapter
Contents
1 Safety instructions and used symbols............................................................ 8
2 General .......................................................................................................... 9
3 Bus systems/interfaces .................................................................................. 9
4 System requirements ..................................................................................... 9
5 Installation and commissioning................................................................... 10
5.1 Configuration of the network interface ....................................................... 10
5.1.1 Configuration of the network interface via TCP/IP........................................ 10
5.1.2 Configuration of the network interface via the MCU service software
(serial interface X100) ........................................................................................ 12
5.2 Hardware options ........................................................................................ 13
6 Web interface............................................................................................... 14
6.1 The start page .............................................................................................. 14
6.2 Initialization................................................................................................. 17
6.2.1 Configure presentation of active alarms .......................................................... 19
6.3 SNMP settings............................................................................................. 21
6.3.1 SNMP mib-2/system settings ............................................................................ 21
6.3.2 SNMP communities ............................................................................................ 22
6.3.3 SNMP traps .......................................................................................................... 22
6.3.4 Download DC-MCU-MIB ................................................................................. 24
6.4 Security........................................................................................................ 25
6.4.1 Password for the web interface ......................................................................... 25
6.4.2 Password for issuing remote commands through the web interface ............ 25
6.4.3 Password for the service software .................................................................... 25
6.5 Email............................................................................................................ 25
6.6 Remote commands ...................................................................................... 27
6.7 Encrypted access to the web interface......................................................... 29
6.8 RCCMD....................................................................................................... 30
Index of figures:
Figure 1 Network settings ......................................................................................................................................11
Figure 2 Confirmation of the network configuration .............................................................................................11
Figure 3 network configuration via the service software .......................................................................................12
Figure 4 jumper network interface .........................................................................................................................13
Figure 5 Start page of the web interface (1)...........................................................................................................14
Figure 6 Start page of the web interface (2)...........................................................................................................14
Figure 7 Structure of the web page ........................................................................................................................15
Figure 8 Web page Initialisation ............................................................................................................................17
Figure 9 Configuration of the display of active messages .....................................................................................19
Figure 10 Example for an active message in red....................................................................................................19
Figure 11 Example for the configuration of the display of active messages..........................................................20
Figure 12 Active message in yellow ......................................................................................................................20
Figure 13 Active message in green ........................................................................................................................20
Figure 14 SNMP settings .......................................................................................................................................21
Figure 15 SNMP mib-2/system settings.................................................................................................................21
Figure 16 SNMP Communities..............................................................................................................................22
Figure 17 SNMP trap receiver ...............................................................................................................................22
Figure 18 SNMP test trap.......................................................................................................................................23
Figure 19 SNMP trap (boost).................................................................................................................................24
Figure 20 dcAlarmTable ........................................................................................................................................24
Figure 21 Download link SNMP MIB ...................................................................................................................24
Figure 22 Email configuration ...............................................................................................................................25
Figure 23 Example of an email ..............................................................................................................................26
Figure 24 Remote commands of the web surface ..................................................................................................27
Figure 25 Remote command successfully executed...............................................................................................27
Figure 26 Error executing command......................................................................................................................28
Figure 27 Setting the time in the MCU ..................................................................................................................28
Figure 28 Safety instruction ...................................................................................................................................29
Figure 29: Client installation..................................................................................................................................31
Figure 30: Client installation..................................................................................................................................31
Figure 31: Client installation..................................................................................................................................32
Figure 32 Installation dialogue...............................................................................................................................32
Figure 33 Configuration dialogue ..........................................................................................................................33
Many different symbols are used for the individual components of the remote
monitoring system and in these operating instructions; the following table
shows the meaning of these symbols:
All further symbols and pictograms are explained at the appropriate places in
these operating instructions.
2. Ensure that only fully qualified and authorised personnel have access to
the system; only this personnel may open the unit.
3. When working with the unit, use only properly insulated tools which are
approved for the voltages in question.
4. All persons working with the unit must be familiar with first-aid measures
for accidents involving electricity.
5. Always observe the regulations of the local power supply company as well
as other safety regulations.
6. The passwords used for programming the unit must not be disclosed to
unauthorised persons.
2 General
The Remote Monitoring System MCU is a microprocessor-controlled
monitoring and control device. With this system, it is possible to monitor and
control all the main components of a power supply system.
For monitoring the power supply system via a computer network, the MCU can
be extended via the serial port with a TCP/IP adapter.
The MCU TCP/IP adapter therefore allows more rational and efficient
employment of maintenance and service personnel.
3 Bus systems/interfaces
The SUB-D interface X100* serves as interface to MCU 1. The RJ45 interface
X600 serves as interface to the Ethernet network. This is a 10 MBit interface.
The power supply of the adapter is effected via X500 (9 – 36V DC, 2W).
The optional interfaces X10, X200, X400, X401 are currently not supported.
4 System requirements
The remote monitoring system MCU consists of various hardware and software
components. Some components are absolutely necessary, others are optional.
The following description of the MCU TCP/IP adapter allows safe installation
and commissioning of the system.
1
can be changed to X101 (internal configuration)
Attention!
The safety instructions must be observed at all times during
assembly, connection and commissioning!
The components of the MCU are designed to be operated in closed dry rooms.
The maximum permissible ambient temperature is 55°C. Upon assembly,
attention must be paid that the components are not exposed to aggressive
substances and the passage of cooling air is not impaired.
To enable you to carry out the commissioning, the entire power supply system
with all the components belonging to the MCU has to be wired and connected
to the power supply system. The MCU TCP/IP adapter is connected to the
service interface of MCU (MCU 1000/2000+: X6, MCU 2500: X110)
(recommended cable connection: part no. 734624) and apart from the voltage
supply only requires the network interface to be configured. For the installation
of the top-hat rail, the adapter can be fitted with a support rail adapter (part no.
709232).
IP address: 10.10.10.10
The factory host name of the adapter with activated DHCP operation is: MCU
The password-protected service area of the adapter is accessible from the web
interface via "Network" (default password: benning):
2
can be changed to X101 (internal configuration)
X120 Function
3+5,4+6 IP configuration from software settings
1+3,4+6 Operation with static IP address 10.10.10.10
2+4,3+5 DHCP operation with host name MCU
1+3,2+4 reserved
6 Web interface
6.1 The start page
After successful linking into the network, the TCP/IP adapter is available under
the set IP address or the set host name (for DHCP):
current position
Measurements:
Show protocol: show current measured value and active messages of the
system
Settings:
Security 5: Password settings for the web interface and for access via
MCU service software.
E-Mail 6: Settings for the email receiver in the event of faults, and the
mail server configuration.
3
Access to these pages is password-protected (web password).
4
Access to these pages is password-protected (web password).
5
Access to these pages is password-protected (web password).
6
Access to these pages is password-protected (web password).
7
Access to this page is password-protected (remote command password).
8
Access to these pages is password-protected (web password).
9
Access to these pages is password-protected (web password).
6.2 Initialization
Basic settings for the operation of the TCP/IP adapter can be made via
Initialisation:
Upload picture and schematic: On a separate page, you are able to upload an
image or a wiring diagram of the system, if necessary.
Site info settings: Input fields describing the system at the site of installation.
Configure presentation of active alarms: Here, you are able to determine the
colour of the active MCU messages on the web interface.
MCU type selection: On this page, it is possible to select the MCU connected
to the adapter (DC-MCU or AC-USVMCU).
This allows a change of the display of active messages not indicating a fault of
the power supply system..
If this message is to be shown in the record display e.g. with a yellow LED,
this message must be configured as follows:
The access type must first be set under SNMP access control, and saved by
clicking Apply.
The user can then create his own individual settings in the respectively
activated access control range. Changed settings must always be confirmed by
clicking Apply. The new settings become active immediately after this
confirmation.
Under SNMP traps, a pool of SNMP trap receivers can be set up. After
entering the trap receivers, the pool must be saved by clicking Apply.
The button Send test trap sends a test trap to all entries in the pool, with the
test trap structured as follows:
Figure 20 dcAlarmTable
6.4 Security
6.4.2 Password for issuing remote commands through the web interface
The password for access to the remote commands through the web interface
can be set in this form.
Default setting: service
6.5 Email
Settings for sending emails in the event of errors in the system:
The adapter sends emails dependent on the MCU filter programming. This
refers to error protocols automatically sent by the MCU. If the adapter receives
an unrequested error protocol from the MCU, an email will be sent. In addition
to the latest measured values, this email also includes the active alarm
messages from the power supply system:
If a remote command has not been released by the internal MCU programming,
the message Error executing command appears:
Most remote commands require no further user input. Setting the time in the
MCU is an exception:
If the configuration data and other content of the web surface are security-
sensitive in their field of use, the BENNING TCP/IP adapter offers the
possibility of opening the web surface through the secure protocol HTTPS. In
this process, all data travelling in both directions is encrypted before
transmission, and only decrypted again by the receiver. This prevents any
interception of the content transferred.
In order to open the web surface of the TCP/IP adapter through an encrypted
connection, enter https:// in the address field of your browser instead of
http:// .
For advanced users: it is possible to check the certificate before establishing the
connection on the basis of its SHA1 fingerprint. The SHA1 fingerprint of the
certificate used is:
08:60:16:ca:d9:5b:64:da:15:51:bf:25:9e:30:ad:04:42:e8:73:fe
6.8 RCCMD
The RCCMD function of the TCP/IP adapter allows the user to manage events
in the connected system with a high degree of programming freedom. Using
the RCCMD service, it is possible for example to perform a controlled
shutdown of the IT system in the event of a fault with the power supply, or to
alert personnel.
For this purpose, the RCCMD client software needs to be installed on the target
system (e.g. on a Windows server), to use which the separate purchase of a
software licence is necessary. If a previously configured (error) state now
arises, a notification is sent to the RCCMD client through the TCP/IP adapter,
allowing it to react. The notification can contain the name of a batch file to be
executed, and further parameters such as the latest measured values.
In the following dialogue, enter the port that is to be used for receiving
RCCMD packets in the field "Use Port". The default number for this port is
6003. This must naturally also match the configuration of the receivers in the
TCP/IP adapter configuration (see below).
The "Configure" button can be used to configure the Shutdown.bat, i.e. the file
that is executed if a shutdown command is received. The following figure
shows the default after a successful installation on a Windows computer.
The client runs in the background and waits for commands arriving from the
RCCMD servers, e.g. from a USV-MCU.
For example, the pools can be used to perform a controlled shutdown of all
computers in a department in the event of a mains failure. For the
administration of the receiver pools, there is an input mask on the RCCMD
configuration page, which can be reached using the menu item "RCCMD".
In the text field RCCMD receivers, the individual computers in the pool can
now be specified. It must be ensured here that the input format specified is
adhered to. The receivers are addressed by reference to their IP addresses and
port numbers. The individual bytes of the IP address are specified separated by
dots, followed by a colon and the port number. The individual entries in the
pool are separated by commas. Example:
To set up a new task, this must be entered in a free line in the RCCMD task
table. There are a total of 20 lines, of which five are always displayed per page.
It is possible to navigate through the pages using the buttons "< previous page"
and "next page >".
Note: If changes have been made to the table, these must be saved
using the button "Apply changes" before navigating to the next
page.
Task no.
If the desired message is not included in the list, it is also possible to enter the
message protocol identification manually. To do this, the lower radio button
must be activated, and the identification must be entered in the adjacent input
field. Note: You should only use this variant if you are familiar with the
allocation and configuration of the message identifications in the MCU system.
=>This condition triggers the RCCMD task when a battery test has been started
and is running.
6.8.5.3. Receiver
In the receiver field, the receivers for an RCCMD task are specified. It is
possible here both to specify a single receiver by means of its IP address and
port number, or to specify a previously created pool of receivers (see section on
receiver pools).
If the RCCMD task is executed, the RCCMD packet is sent to all receivers
listed in the pool. A pool can contain up to 100 different receivers. It is thus
possible, e.g. in the event of a power supply failure, to perform a controlled
shutdown of a pool of servers or of all computers in a department or on a floor.
In the IP address field, the IP address is specified for the computer that is to
receive the RCCMD command – i.e. the computer on which the RCCMD client
software is installed. This can e.g. be a server that should automatically be shut
down in the event of a mains failure.
In the port field, the IP port is entered, on which the RCCMD software of the
receiver will receive the commands. The port is configured during the
installation of the RCCMD service and is preset to 6003 as default.
If you have not specifically changed the port number, enter 6003 here.
6.8.5.6. Parameters
It is possible to pass parameters to the RCCMD service on the target PC. These
parameters are normally used to execute a batch file, which then performs all
further desired actions. The filename of the batch file to be executed must be
the first entry in the parameters field. It must be remembered here that the
filename of the batch file must be specified relative to the installation directory
of the RCCMD client. For example, if the RCCMD service is installed on a
Windows computer under C:\RCCMD, and if the batch file to be executed has
the filename C:\RCCMD\BAT\mybatch.bat, the parameter entry must start
with "\BAT\mybatch.bat".
6.8.5.9. Active
The tick-box "Active" is used to determine whether the configured RCCMD
action should be evaluated or not. If this box is not ticked, the relevant
RCCMD action will be completely ignored and will never be executed.
Note: The original directory used in the RCCMD client installation on the
relevant client PC is always taken as the starting point when additional paths
are specified, or the batch file is searched for in the original directory itself if
no additional specifications are made.
Task no.: 1
IP address: 10.10.10.12
Delay[s]: 10
Frequency[s]: 60
The task number can be allocated freely by the user. It must lie within the
range of available tasks (1..20) and must not already be in use. Only one event
can be evaluated per task, or only one client can be serviced, or only one
distinct packet can be sent. The user must programme the reaction to the
message. The reaction to the message can be programmed as desired here, of
course, e.g. forward to other clients, send email etc.
A possible batch file NF.bat on the receiving client 10.10.10.12 might then
look as follows:
@echo off
rem ***** protocol log with date and time *****
echo.RCCMD Event: ********** >> c:\rccmd\Mainsfailure.log
echo. | date | c:\winnt\system32\find /V "new" >> c:\rccmd\
Mainsfailure.log
echo. | time | c:\winnt\system32\find /V "new" >> c:\rccmd\
Mainsfailure.log
echo. Mainsfailure: %1 UBatt: %2 V >> c:\rccmd\
Mainsfailure.log
rem ***** add empty line
echo. >> c:\rccmd\ Mainsfailure.log
IP address: 10.10.10.12
Delay[s]: 60
Frequency[s]: 0
The associated parameter in the RCCMD task would have to be configured e.g.
as follows:
Parameters: mymail.bat /N /L
The task would thus execute the file "mymail.bat" with the parameters
"Operation point identification" and the "Host name".
@echo off
call c:\rccmd\qblat -t "XYZ@Benning.de" -s "UPS E-Mail Event from %1"
"%1 at location %2 running in bypass mode"
echo on
To do this, the client PC that is to forward the RCCMD message needs to have
a corresponding batch file saved, which RCCMD starts with the parameter "-s"
or "-se".
The client PC must naturally be connected to a secure powered supply, so that
it can also forward the messages in the event of a fault.
@echo off
IP address: 10.10.10.12
Parameters: "rccmd_send.bat ”
Delay[s]: 10
Frequency[s]: 0
7.2 Modbusparameter
The Modbus server is available at tcp-port 502 with slave-ID 1.
The link print view displays the Modbus table view without the navigation bar
in a seperate browser window.
During Modbus table initialization (after activating the service or after a cold
boot), the Modbus table view is not available:
V1.00 TCP/IP-MCU
8.2 Set-up
For monitoring a power supply system with the TCP/IP adapter, the system
must be configured in the monitor software. Under the menu Settings, the
system parameters are entered under the menu item "systems". The TCP port is
49152 and the default password is "service".
8.3 Operation
After setting up the system the monitor software automatically connects to the
entered TCP/IP systems and waits for message protocols of the systems. In the
case of a fault / operating state change the MCU sends a MCU message
protocol to the monitor software via the TCP/IP adapter:
9.2 Operation
Operating procedure via the TCP/IP interface corresponds to the operating
procedure via the serial interface.
10 Firmware update
It is possible to install Firmware updates through the web interface:
Figure 52 Maintenance
The link "Firmware update" takes you to a web form for uploading firmware
files:
After selecting the firmware file and confirming with "send file", the update
takes place:
Note: The process can take several minutes and must never be
interrupted.
After successfully uploading the firmware, the adapter can be restarted with the
new firmware by clicking "Reboot":
11 Fault diagnosis
The TCP/IP adapter does not react to the IP configuration set:
12 General
The software incorporated into this product includes various software
components to which Benning or third parties own the proprietary rights.
http://service.benning.de/gpl/
Unfortunately we are not able to answer questions on the source code for the
open source software. The source code for software components in which
Benning holds the proprietary rights is not made available.
13 Appendix
13.1 Benning DC-MIB overview
MIB release: Jan, 22nd 2010
13.1.1 dcIdent
Figure 57 dcIdent
dcIdentManufacturer OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..31))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The name of the DC-power system
manufacturer."
::= { dcIdent 1 }
dcIdentModel OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..63))
MAX-ACCESS read-only
STATUS current
DESCRIPTION"The DC-power system model
description."
::= { dcIdent 2 }
dcIdentSerialNumber OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..31))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The serial number of the DC-power
system."
::= { dcIdent 3 }
dcIdentName OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..63))
MAX-ACCESS read-write
STATUS current
DESCRIPTION"A string identifying the DC-power
system.
This object should be set by the
administrator."
::= { dcIdent 4 }
dcIdentDescription OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..127))
MAX-ACCESS read-write
STATUS current
DESCRIPTION "A possibility for the administrator
to describe the power system."
::= { dcIdent 5 }
dcIdentSystemInstallationDate OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..15))
MAX-ACCESS read-write
STATUS current
DESCRIPTION "A string containing either the date
of system installation or acceptance
date (YYYY-MM-DD).
This string can be set by the
administrator."
::= { dcIdent 6 }
dcIdentNominalValues OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..127))
MAX-ACCESS read-write
STATUS current
DESCRIPTION "A string containing nominal output
power values of the system, e.g.
48 Volts / 3000 Amps / 3000 Ah.
This string can be set by the
administrator."
::= { dcIdent 7 }
13.1.2 dcPowerSystem
Figure 58 dcPowerSystem
-- UBBR i
dcPowerSystemBusbarVoltage OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.01 Volt DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the busbar voltage."
::= { dcPowerSystem 1 }
-- IRECTOTi
dcPowerSystemTotalRectCurrent OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.1 Amp DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the total rectifier current."
::= { dcPowerSystem 2 }
-- IBATTOTi
dcPowerSystemTotalBatteryCurrent OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.1 Amp DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the total battery current."
::= { dcPowerSystem 3 }
-- TPLAi
dcPowerSystemTemperature OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.1 degrees Centigrade/Fahrenheit"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The power system ambient temperature."
::= { dcPowerSystem 8 }
13.1.3 dcController
Figure 59 dcController
dcControllerSerialNumber OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..15))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The DC-power system's controller serial
number."
::= { dcController 1 }
dcControllerSoftwareVersion OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..15))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The DC-power system software version(s).
This variable can be different from the
dcControllerFirmwareVersion.
This variable may or may not have the same
value as dcControllerAgentSoftwareVersion
in some implementations."
::= { dcController 2 }
dcControllerAgentSerialNumber OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..15))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The DC-power system's (snmp) agent serial
number."
::= { dcController 3 }
dcControllerAgentSoftwareVersion OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..15))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The DC-power system agent software version.
This variable can be different from the
dcControllerAgentFirmwareVersion.
This variable may or may not have the same
value as dcControllerSoftwareVersion in
some implementations."
::= { dcController 4 }
13.1.4 dcRectifier
Figure 60 dcRectifier
dcRectifierNumRectifiers OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of rectifers or rectifier-shelfs
utilized in this system.
This variable indicates the number of rows in
the rectifier table."
::= { dcRectifier 1 }
dcRectifierTable OBJECT-TYPE
SYNTAX SEQUENCE OF DCRectifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A list of rectifier table entries.
The number of entries is given by the value of
dcRectifierNumRectifiers."
::= { dcRectifier 2 }
dcRectifierEntry OBJECT-TYPE
SYNTAX DCRectifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry containing information applicable to
a particular rectifier."
INDEX { dcRectifierIndex }
::= { dcRectifierTable 1 }
dcRectifierIndex OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The rectifier identifier."
::= { dcRectifierEntry 1 }
dcRectifierFirmwareVersion OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..15))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The rectifier's firmware version."
::= { dcRectifierEntry 2 }
-- RECXXOFFi:1 else:2
dcRectifierStatus OBJECT-TYPE
SYNTAX INTEGER {
off(1),
on(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The current state of the rectifier. Rectifiers
can be on or off. "
::= { dcRectifierEntry 3 }
-- UBBRXXi
dcRectifierVoltage OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.01 Volt DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the rectifier voltage."
::= { dcRectifierEntry 5 }
-- IRECXXi
dcRectifierCurrent OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.1 Amp DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the present rectifier
current."
::= { dcRectifierEntry 6 }
dcRectifierAddress OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The address of the rectifier in the system."
::= { dcRectifierEntry 7 }
13.1.5 dcBattery
Figure 61 dcBattery
dcBatteryNumBatteries OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of batteries.
This variable indicates the number of rows
in the battery table."
::= { dcBattery 2 }
dcBatteryTable OBJECT-TYPE
SYNTAX SEQUENCE OF DCBatteryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A list of battery table entries.
The number of entries is given by the value of
dcBatteryNumBatteries."
::= { dcBattery 3 }
dcBatteryEntry OBJECT-TYPE
SYNTAX DCBatteryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry containing information applicable to
a particular string of batteries."
INDEX { dcBatteryIndex }
::= { dcBatteryTable 1 }
dcBatteryIndex OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The battery identifier."
::= { dcBatteryEntry 1 }
-- UBATXXi
dcBatteryVoltage OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.01 Volt DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the battery voltage."
::= { dcBatteryEntry 3 }
-- IBATXXi
dcBatteryCurrent OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.1 Amp DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the present battery current."
::= { dcBatteryEntry 4 }
-- TBATXXi
dcBatteryTemperature OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.1 degrees Centigrade/Fahrenheit"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The battery temperature."
::= { dcBatteryEntry 5 }
dcBatteryModel OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..15))
MAX-ACCESS read-write
STATUS current
DESCRIPTION"A string identifying the battery string,
e.g. VHB/4/300Ah."
::= { dcBatteryEntry 6 }
dcBatteryAddress OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The address of the battery in the system."
::= { dcBatteryEntry 7 }
13.1.6 dcLoadDistribution
Figure 62 dcLoadDistribution
dcLoadDistributionNumLD OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of load distributions.
This variable indicates the number of rows
in the load distribution table."
::= { dcLoadDistribution 1 }
dcLoadDistributionTable OBJECT-TYPE
SYNTAX SEQUENCE OF DCLoadDistributionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A list of load distribution table entries."
::= { dcLoadDistribution 2 }
dcLoadDistributionEntry OBJECT-TYPE
SYNTAX DCLoadDistributionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry containing information applicable to a
particular load string."
INDEX { dcLoadDistributionIndex }
::= { dcLoadDistributionTable 1 }
dcLoadDistributionIndex OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The load distribution identifier."
::= { dcLoadDistributionEntry 1 }
-- ULOAXXi
dcLoadDistributionVoltage OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.01 Volt DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the particular load voltage."
::= { dcLoadDistributionEntry 2 }
-- ILOAXXi
dcLoadDistributionCurrent OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.1 Amp DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the particular load current."
::= { dcLoadDistributionEntry 3 }
-- WELEXXi
dcLoadDistributionPower OBJECT-TYPE
SYNTAX INTEGER
UNITS "Watts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The particular load power."
::= { dcLoadDistributionEntry 4 }
dcLoadDistributionDescription OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..15))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The description of the particular load string."
::= { dcLoadDistributionEntry 5 }
dcLoadDistributionAddress OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The address of the load distribution in
the system."
::= { dcLoadDistributionEntry 7 }
13.1.7 dcACBackup
13.1.7.1. dcBypass
Figure 63 dcBypass
dcBypassNumBypass OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of bypasses.
This variable indicates the number of rows
in the bypass table."
::= { dcBypass 1 }
dcBypassTable OBJECT-TYPE
SYNTAX SEQUENCE OF DCBypassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A list of bypass table entries."
::= { dcBypass 2 }
dcBypassEntry OBJECT-TYPE
SYNTAX DCBypassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry containing information applicable
to a particular bypass."
INDEX { dcBypassIndex }
::= { dcBypassTable 1 }
dcBypassIndex OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The bypass identifier."
::= { dcBypassEntry 1 }
dcBypassHardwareVersion OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..15))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The bypass hardware version."
::= { dcBypassEntry 2 }
-- UINVOUTXXi
dcBypassInputVoltageSource1 OBJECT-TYPE
SYNTAX INTEGER
UNITS "RMS Volts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the bypass input voltage
of the primary source."
::= { dcBypassEntry 5 }
-- UMAIXXi
dcBypassInputVoltageSource2 OBJECT-TYPE
SYNTAX INTEGER
UNITS "RMS Volts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the bypass input voltage
of the secondary source."
::= { dcBypassEntry 6 }
-- USBPOUTXXi
dcBypassOutputVoltage OBJECT-TYPE
SYNTAX INTEGER
UNITS "RMS Volts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the bypass output voltage."
::= { dcBypassEntry 7 }
-- ISBPOUTXXi
dcBypassOutputCurrent OBJECT-TYPE
SYNTAX INTEGER
UNITS "RMS Amps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the present bypass output
current."
::= { dcBypassEntry 8 }
-- FSBPXXi
dcBypassFrequency OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.1 Hertz"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The present bypass frequency."
::= { dcBypassEntry 9 }
-- PSBPXXi
dcBypassActivePower OBJECT-TYPE
SYNTAX INTEGER
UNITS "Watts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the present active bypass
power."
::= { dcBypassEntry 10 }
-- QSBPXXi
dcBypassReactivePower OBJECT-TYPE
SYNTAX INTEGER
UNITS "VAR"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the present reactive bypass
power."
::= { dcBypassEntry 11 }
-- SSBPXXi
dcBypassComplexPower OBJECT-TYPE
SYNTAX INTEGER
UNITS "VA"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the present complex bypass
power."
::= { dcBypassEntry 12 }
dcBypassAddress OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The address of the bypass in the system."
::= { dcBypassEntry 13 }
13.1.7.2. dcInverter
Figure 64 dcInverter
dcInverterNumInverter OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of inverters in the power system.
This variable indicates the number of rows
in the inverter table."
::= { dcInverter 1 }
dcInverterTable OBJECT-TYPE
SYNTAX SEQUENCE OF DCInverterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A list of inverter table entries. The number
of entries is given by the value of
dcInverterNumInverter."
::= { dcInverter 2 }
dcInverterEntry OBJECT-TYPE
SYNTAX DCInverterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry containing information applicable
to a particular inverter."
INDEX { dcInverterIndex }
::= { dcInverterTable 1 }
dcInverterIndex OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The inverter identifier."
::= { dcInverterEntry 1 }
dcInverterFirmwareVersion OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..15))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The inverter's firmware version."
::= { dcInverterEntry 2 }
-- 1:INVXXOFFi 2:sonst
dcInverterStatus OBJECT-TYPE
SYNTAX INTEGER {
off(1),
on(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The current state of the inverter."
::= { dcInverterEntry 3 }
-- UWRAXXi
dcInverterOutputVoltage OBJECT-TYPE
SYNTAX INTEGER
UNITS "RMS Volts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the inverter output voltage."
::= { dcInverterEntry 5 }
-- IINVOUTXXi, IINVXXi
dcInverterOutputCurrent OBJECT-TYPE
SYNTAX INTEGER
UNITS "RMS Amps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The magnitude of the present inverter output
current."
::= { dcInverterEntry 6 }
dcInverterAddress OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The address of the inverter in the system."
::= { dcInverterEntry 7 }
13.1.8 dcBatteryTest
Figure 65 dcBatteryTest
dcBatteryTestNumBatteries OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of batteries.
This variable indicates the number of rows
in the battery test table."
::= { dcBatteryTest 1 }
dcBatteryTestTable OBJECT-TYPE
SYNTAX SEQUENCE OF DCBatteryTestEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A list of battery table entries."
::= { dcBatteryTest 2 }
dcBatteryTestEntry OBJECT-TYPE
SYNTAX DCBatteryTestEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry containing information applicable
to a particular battery-string test."
INDEX { dcBatteryTestIndex }
::= { dcBatteryTestTable 1 }
dcBatteryTestIndex OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The battery test identifier."
::= { dcBatteryTestEntry 1 }
-- UVODXXi
dcBatteryTestEndVoltage OBJECT-TYPE
SYNTAX INTEGER
UNITS "0.01 Volt DC"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The battery string voltage at the end of
the battery test."
::= { dcBatteryTestEntry 2 }
-- ZVODi
dcBatteryTestDuration OBJECT-TYPE
SYNTAX INTEGER
UNITS "minutes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The duration of the last battery test in
minutes."
::= { dcBatteryTestEntry 3 }
-- CBATXXi
dcBatteryTestDischargedEnergy OBJECT-TYPE
SYNTAX INTEGER
UNITS "Ah"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This discharged energy during the last
battery test."
::= { dcBatteryTestEntry 4 }
dcBatteryTestType OBJECT-TYPE
SYNTAX INTEGER {
timeBased(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The type of the last battery test."
::= { dcBatteryTestEntry 5 }
-- 2:VODNEGi 1:sonst
dcBatteryTestResult OBJECT-TYPE
SYNTAX INTEGER {
ok(1),
failed(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The result of the last battery test."
::= { dcBatteryTestEntry 6 }
dcBatteryTestAddress OBJECT-TYPE
SYNTAX NonNegativeInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The address of the battery in the system."
::= { dcBatteryTestEntry 9 }
13.1.9 dcControl
Figure 66 dcControl
13.1.10 dcConfig
Figure 67 dcConfig
dcConfigFloatVoltage OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.01 Volt DC"
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The float voltage of the system."
::= { dcConfig 1 }
dcConfigBoostVoltage OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.01 Volt DC"
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The boost voltage of the system."
::= { dcConfig 2 }
dcConfigStandByVoltage OBJECT-TYPE
SYNTAX NonNegativeInteger
UNITS "0.01 Volt DC"
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The stand by-voltage of the system. E.g.
during a battery test."
::= { dcConfig 3 }
13.1.11 dcAlarm
Figure 68 dcAlarm
dcAlarmsPresent OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The present number of active alarm conditions."
::= { dcAlarm 1 }
dcAlarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF DcAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A list of alarm entries."
::= { dcAlarm 2 }
dcAlarmEntry OBJECT-TYPE
SYNTAX DcAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry containing information applicable to
a particular alarm."
INDEX { dcAlarmId }
::= { dcAlarmTable 1 }
dcAlarmId OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A unique identifier for an alarm condition
This value must remain constant."
::= { dcAlarmEntry 1 }
dcAlarmDescr OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION"A reference to an alarm description object.
The object referenced should not be
accessible, but rather be used to provide a
unique description of the alarm condition."
::= { dcAlarmEntry 2 }
dcAlarmTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION"The value of sysUpTime when the alarm condition
was detected. If the alarm condition was
detected at the time of agent startup and
presumably existed before agent startup,
the value of dcAlarmTime shall equal 0."
::= { dcAlarmEntry 3 }
dcAlarmDevice OBJECT-TYPE
SYNTAX PositiveInteger
MAX-ACCESS read-only
STATUS current
DESCRIPTION"This value shows the device that causes the
alarm or the value of a threshold level that
caused the alarm."
::= { dcAlarmEntry 4 }
13.1.11.1. dcWellKnownAlarms
Figure 69 dcWellKnownAlarms
dcAlarmAgentCommunication OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a communication problem
from the agent to the DC-power system."
::= { dcWellKnownAlarms 1 }
-- MAIRECXXi
dcAlarmACInputFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an alarm in the AC-input,
e.g. ac input fuse blown, ac input breaker
tripped or mains failure."
::= { dcWellKnownAlarms 2 }
-- RECXXi, RECi
dcAlarmRectifierFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an alarm of rectifiers,
e.g. broken rectifier, fan or temperature
alarm."
::= { dcWellKnownAlarms 3 }
-- BATi, BATXXi
dcAlarmBatteryFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an alarm of batteries,
e.g. fuse blown, symmetry or temperature."
::= { dcWellKnownAlarms 4 }
-- INVi, INVXXi
dcAlarmInverterFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an alarm of inverters,
e.g. input
fuse, fan."
::= { dcWellKnownAlarms 5 }
-- BATDISACTi, BATDISi
dcAlarmBattDischarge OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the battery is
in discharge mode."
::= { dcWellKnownAlarms 7 }
-- UBATLOWi, UBAT<UU.Ui
dcAlarmBatteryLow OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a low battery voltage."
::= { dcWellKnownAlarms 8 }
-- TBAT<TTi, TBAT>TTi
dcAlarmBatteryTemperature OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the battery
temperature is abnormal."
::= { dcWellKnownAlarms 10 }
-- LOAXXOFFi, COTLOAi
dcAlarmLoadDisconnected OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a disconnected load."
::= { dcWellKnownAlarms 11 }
-- RECOFFi
dcAlarmAllRectifierOff OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that all rectifiers are
off."
::= { dcWellKnownAlarms 12 }
-- N+1i, N+1RECi
dcAlarmNoRedundancy OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a loss of rectifier
redundancy."
::= { dcWellKnownAlarms 13 }
-- FUSBATi, FUSBATXXi
dcAlarmBatteryFuseTripped OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that a battery fuse has
tripped."
::= { dcWellKnownAlarms 16 }
-- FUSLOADCi, FUSLOAXXDCi
dcAlarmDCLoadFuseTripped OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that a dc load fuse
has tripped."
::= { dcWellKnownAlarms 17 }
-- VODi
dcAlarmBatteryTestInProgress OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the system is
in battery test mode."
::= { dcWellKnownAlarms 18 }
-- VODNEGi
dcAlarmBatteryTestFailed OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the battery test has
failed."
::= { dcWellKnownAlarms 19 }
-- RECCHGi
dcAlarmBoost OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the system is in
boost mode."
::= { dcWellKnownAlarms 20 }
-- GRSi, GRSXXi
dcAlarmGeneral OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a general alarm."
::= { dcWellKnownAlarms 21 }
-- NURERRi
dcAlarmNonUrgentError OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a non urgent error."
::= { dcWellKnownAlarms 22 }
-- URGERRi
dcAlarmUrgentError OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an urgent error."
::= { dcWellKnownAlarms 23 }
-- MCUBUSi
dcAlarmMcuHasNoSatbusContact OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the MCU unit has
no contact to the SATBUS."
::= { dcWellKnownAlarms 24 }
-- MODi
dcAlarmModemNotResponsing OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the modem does not
respond."
::= { dcWellKnownAlarms 25 }
-- DDCi, DDCXXi
dcAlarmDeepDischargeContactorDropped OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a dropped deep
discharge contactor."
::= { dcWellKnownAlarms 27 }
-- FANRECXXi
dcAlarmFanRectifierFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that a rectifier
fan failed. The device id is given in the
dcAlarmDevice field."
::= { dcWellKnownAlarms 28 }
-- FUSLOAi, FUSLOAXXi
dcAlarmLoadFuseTripped OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a tripped load fuse."
::= { dcWellKnownAlarms 29 }
-- FUSi
dcAlarmFuseTripped OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a tripped fuse."
::= { dcWellKnownAlarms 30 }
-- FUSLOAACi, FUSLOAXXACi
dcAlarmLoadFuseAcTripped OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a tripped AC load
fuse."
::= { dcWellKnownAlarms 31 }
-- FUSBATOFFi, FUSBATXXOFi
dcAlarmBatteryFuseOff OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a switched off battery
fuse."
::= { dcWellKnownAlarms 32 }
-- FUSLOAOFFi, FUSLOAXXOFi
dcAlarmLoadFuseOff OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a switched off load
fuse."
::= { dcWellKnownAlarms 33 }
-- FUSRECXXi
dcAlarmFuseRectifierTripped OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the fuse of the
rectifier given in field dcAlarmDevice has
tripped."
::= { dcWellKnownAlarms 34 }
-- RECXXOFFi
dcAlarmRectifierOff OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the rectifier
given as dcAlarmDevice is off."
::= { dcWellKnownAlarms 35 }
-- SVPi
dcAlarmSurgeVoltageProtectionTripped OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a tripped surge voltage
protection."
::= { dcWellKnownAlarms 36 }
-- THIGi
dcAlarmTemperatureHigh OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates the temperature is
high."
::= { dcWellKnownAlarms 37 }
-- TSEFAUi
dcAlarmTemperatureSensorFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a fault of the
temperature sensor."
::= { dcWellKnownAlarms 38 }
-- MAIi, MAIXXi
dcAlarmMainsError OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a mains error."
::= { dcWellKnownAlarms 39 }
-- DEVi
dcAlarmDeviceFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a device fault."
::= { dcWellKnownAlarms 40 }
-- BATSYMMONi
dcAlarmBatterySymmetryMonitoring OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an alarm in the
battery symmetry monitoring."
::= { dcWellKnownAlarms 41 }
-- EFAi
dcAlarmEarthFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an earth fault."
::= { dcWellKnownAlarms 42 }
-- EFA(-)i
dcAlarmEarthFaultMinusCircuit OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an earth fault in
the minus circuit."
::= { dcWellKnownAlarms 43 }
-- EFA(+)i
dcAlarmEarthFaultPlusCircuit OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an earth fault in
the plus circuit."
::= { dcWellKnownAlarms 44 }
-- CONXXi
dcAlarmDcDcConverterFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a DC-DC converter
fault."
::= { dcWellKnownAlarms 45 }
-- VODERRi
dcAlarmBatteryTestError OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a failed battery test."
::= { dcWellKnownAlarms 46 }
-- BCIi
dcAlarmBatteryCircuitFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a battery circuit
fault."
::= { dcWellKnownAlarms 47 }
-- BATEXDi
dcAlarmBatteryExhaustivelyDischarged OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the battery was
discharged exhaustively."
::= { dcWellKnownAlarms 48 }
-- BATNOAi
dcAlarmBatteryNotAvailable OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the battery is
not available."
::= { dcWellKnownAlarms 49 }
-- RESXXi
dcAlarmReserve OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a reserved error."
::= { dcWellKnownAlarms 50 }
-- DOOi
dcAlarmDoorContact OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a door contact alarm."
::= { dcWellKnownAlarms 51 }
-- BYSONi
dcAlarmBypassSwitchOn OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the bypass
switch is on."
::= { dcWellKnownAlarms 52 }
-- SBPSOVBLOi
dcAlarmStaticBypassSwitchoverBlocked OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the static
bypass switchover is blocked."
::= { dcWellKnownAlarms 53 }
-- SBPOVLi, SBPXXSOVBLi
dcAlarmStaticBypassOverload OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an overload of the
static bypass."
::= { dcWellKnownAlarms 54 }
-- UOUTSBPi
dcAlarmStaticBypassOutputVoltageFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a fault of the static
bypass output voltage."
::= { dcWellKnownAlarms 55 }
-- FANi
dcAlarmFanFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a fan fault."
::= { dcWellKnownAlarms 56 }
-- EMSi
dcAlarmEmergencyStop OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that an emergency
stop was executed."
::= { dcWellKnownAlarms 57 }
-- ILOAHIGi
dcAlarmLoadCurrentHigh OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the load current
is high."
::= { dcWellKnownAlarms 58 }
-- SWIMAIOFFi
dcAlarmMainsSwitchOff OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the mains switch
is turned off."
::= { dcWellKnownAlarms 59 }
-- UOUTHIGi
dcAlarmOutputVoltageHigh OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the output voltage
is high."
::= { dcWellKnownAlarms 60 }
-- COTCOCi
dcAlarmCounterCellContactorAktiv OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the counter cell
contactor is active."
::= { dcWellKnownAlarms 61 }
-- SESi
dcAlarmServiceSwitch OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates an activated service
switch."
::= { dcWellKnownAlarms 62 }
-- UPSi
dcAlarmUpsFault OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a fault of the UPS."
::= { dcWellKnownAlarms 63 }
-- UOUTLOWi
dcAlarmOutputVoltageLow OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates that the output voltage
is low."
::= { dcWellKnownAlarms 64 }
-- WHIGi
dcAlarmRippleHigh OBJECT-IDENTITY
STATUS current
DESCRIPTION "This object indicates a high ripple."
::= { dcWellKnownAlarms 65 }
13.1.12 dcAuxiliary
Figure 70 dcAuxiliary
13.1.13 dcTraps
Figure 71 dcTraps
dcTrapAlarmEntryAdded NOTIFICATION-TYPE
OBJECTS { dcAlarmId, dcAlarmDescr, dcAlarmDevice }
STATUS current
DESCRIPTION "This trap is sent upon a alarm in the system
appears. Binding in the trap is description
of alarm and the device that causes the alarm."
::= { dcTraps 1 }
dcTrapAlarmEntryRemoved NOTIFICATION-TYPE
OBJECTS { dcAlarmId, dcAlarmDescr, dcAlarmDevice }
STATUS current
DESCRIPTION "This trap is sent upon a alarm in the system
disappears. Binding in the trap is description
of alarm and the device that causes the alarm."
::= { dcTraps 2 }
i
assigned MCU alarm protocol shortcut