User manual for Schleifenbauer PDU

User manual for Schleifenbauer PDU
User manual for
Schleifenbauer PDU
1. INTRODUCTION
DESCRIPTION
The Schleifenbauer Intelligent Power Distribution Unit (PDU) is designed to distribute the power. Schleifenbauer’s
data bus makes it possible to read and manage many PDUs with a single IP address. The PDU adds an Ethernet
port to this functionality, so that alongside the advantages of a data bus a whole range of new options has become
available. The Intelligent PDU brings together or merges the interests between IT and infrastructures, making it a real
bridge builder. The PDU may contain:
• metered outlets,
• switched outlets,
• metered and switched outlets or
• passive outlets.
Monitoring capabilities will be described in detail within this manual in coming sections.
ACCESSORIES
The following accessories can be purchased from Schleifenbauer, additionally. Please check the Installation Section
for more details regarding mounting brackets.
• C14/C20 plugs if C13/C19 outputs are used
• Different types of attachment brackets
• 19” rack mounting brackets
• Tabletop mounting brackets
• Mounting plates for sunken installation
• Profile clamps
• Toolless Mounts
• Customer Specific solutions related tools
• Please check www.schleifenbauer.eu for further details regarding the accessories.
FEATURES
The Schleifenbauer Intelligent PDU has many beneficial features:
• Ability to set different authority rights through Colocation Mode
• Possibility of configurable PDU
• Sustainable product with 100% Halogen Free production
• Ability to adapt to the customer needs
• Low operating costs
• Universal connection to the communication systems
• High build quality
• Twin Master Mode in order to reboot devices with redundant feeds from a distance (Ideal for Telecom hubs
spread across the country).
2
Schleifenbauer User Manual - v1
MEASUREMENTS
Measurements of the input and the outlet level can be found below:
• Energy (kWh) Total and Sub-total
• Voltage (V) with voltage dip registration
• Current (A) with peak value registration
• Power factor (%)
• Apparent power (VA)
• Real power (W)
• Temperature (°C) with optional sensor
• Relative humidity (%) with optional sensor
3
Schleifenbauer User Manual - v1
2. SAFETY WARNINGS
This manual contains important safety instructions that should be followed during installation and operation of
the PDU. Please read this manual carefully since there may be serious or fatal personal injury and damage to the
equipment if the safety instructions, warnings and directions are not followed. Please save this document for future
use.
EXPERT PERSONNEL
Installation, maintenance and inspection of the Schleifenbauer Intelligent PDU must be carried out by adequately
trained persons according to NEN EN 50110-1, with full observance of the specifications of NEN EN 50110-1 and NEN
3140.
LIFE-SUPPORTING POLICY
The Schleifenbauer PDU has been designed and built for use in data centres. The Intelligent PDU may not be applied
in surroundings where a malfunction in the PDU can have consequences for life support systems. Life support
systems include any devices designated as “critical” by the U.S. FDA. Such systems are found not only in medical
environments such as hospitals, but also on offshore platforms, in petrochemical plants, in air traffic control centres,
etc.
INTERNAL MAINTENANCE IS NOT AN OPTION
A Schleifenbauer Intelligent PDU may not be opened by unauthorised persons. In the event of malfunction or faults
in the PDU, please refer to the warranty conditions. Schleifenbauer Products BV will not accept warranty claims if the
PDU has been opened or alterations have been made.
ťť Please pay attention to the operation conditions before installation and operation of the Schleifenbauer PDU.
ťť The Schleifenbauer PDU has to be protected according to the valid installation guidelines.
ťť The rated value of the in-series protective device may not exceed the maximum value indicated on the product.
ťť The Schleifenbauer PDU may not be used in: a humid environment, in a seriously contaminated environment
or outdoors.
ťť The manufacturer’s warranty on the Schleifenbauer PDU becomes invalid when the QC sticker on the side of
the profile is broken.
ťť Before turning on the PDU for the first time, make sure that it has been allowed to acclimatise to the ambient
temperature for at least 24 hours. Major temperature fluctuations can lead to the formation of condensation
in the PDU if this guideline is not followed.
ťť Please keep in mind that maximum allowed temperature for a metal enclosure is 70 °C for installation in a
normal location and 90 ° C for installation in a restricted access location.
4
Schleifenbauer User Manual - v1
3. INSTALLATION
Please use the information in this chapter to inspect, install and connect the Schleifenbauer Intelligent PDU and all
optional mentioned accessories.
Please read the Safety Warnings Section, understand and take needed precautions before installation.
ťť This product should be installed in a restricted access location.
ťť Socket-outlet shall be installed near the equipment and shall be easily accessible
TECHNICAL INSTALLATION REQUIREMENTS
Before installing and putting the system into operation, check whether the characteristics of the electrical system to
which connection is to be made correspond to the product specifications.
• The Schleifenbauer Intelligent PDU has been designed for connection to electrical systems that comply with IEC
60364 orin the Netherlands, NEN 1010.
• The voltage, maximum permitted current and the number of phases must be correct. This information is displayed
on the front side of the PDU.
• The maximum permitted power must be taken into account with regard to the maximum length and the diameter
of the connecting lead.
• The values and characteristics of the in-series protective devices must match the PDU and the protective elements
included in it.
• The environmental factors must correspond to the product specifications.
VISUAL INSPECTION
After opening the cardboard box and removing the packaging material, the PDU should be checked visually. The PDU
should not be put into operation if damage is detected such that safe and proper operation cannot be guaranteed. In
such cases, please contact Schleifenbauer Products BV.
Note that, in the case of PDUs that are equipped with an over voltage protection, the over voltage protection and the
respective over current protection (if applicable) must be inspected on a regular basis.
TESTING
The Schleifenbauer PDU may be tested according to the NEN 3140 standard. For measurement of insulation resistance,
the measuring voltage used must be lower than or equal to the voltage according to the product specification.
CLEANING
The PDU may only be cleaned by wiping off the outside with a clean dry cloth.
5
Schleifenbauer User Manual - v1
INSTALLATION OVERVIEW
Contents of the package
The Schleifenbauer Intelligent PDUs are shipped in a GreenCart (rolling trolley) or are packaged in a cardboard box.
Where applicable, dispose of the packaging material in a responsible manner, in accordance with local regulations.
All of the materials used for packaging can be recycled. Please contact Schleifenbauer Products to arrange return of
your empty GreenCart. Immediately after receipt, check whether you have received all of the goods.
The following are delivered for each PDU:
• fixing materials: these can be attached to the PDU (19’’ or table-mounting brackets), or are delivered separately
if they have been ordered separately;
• the installation manual (1 per shipment);
• optionally: the user manual.
A Schleifenbauer PDU can be supplied in various models. The different models have different fixing clamps.
• Horizontal mounting in 19” racks with fixed 19” eyelet mounts.
• Fixing clamps for vertical mounting.
Additionally needed tools
The following tools are needed to install the PDUs:
• cage-nuts with bolts and washers,
• suitable screwdriver.
 Please note that the Schleifenbauer PDU User Manual can be found online at http://schleifenbauer.eu/en/
download.
Horizontal Mounting
Each 19’’ rack bracket of a PDU has 4 holes for
horizontal mounting in 19” racks. The holes are
positioned so that an appropriate fixing hole is
always available for a PDU with a profile height
of 1.5 U. Using one or two of the 4 holes allows
mounting without wasting space.
6
Schleifenbauer User Manual - v1
Vertical Mounting
In the case of an PDU for vertical mounting, the connection lead is fed through a hole in the upper, bottom or front
face. There are 4 options for horizontal mounting and these are Tabletop Mounting, Sunken Installation, Toolless
Mounting and Mounting with Profile clamps.
1. Tabletop mounting
Tabletop mounting gives the profile possibility to be
mounted to a flat surface (tabletop).
This arrangement is used for:
• vertical mounting to the bracing beams in the 19”
cabinet
• fixing to a mounting plate
• mounting between the 19” uprights: the profile
attaches to the front of the uprights
The holes on the brackets are located as far as possible
to the outside so that it can also fit and tighten the
bolts if a swivel gland has been placed on the short
side.
2. Sunken installation
Sunken mounting plates on the short side of the profile allow to ‘sink’ the
profile into the cabinet and save space. Particularly in the case of 60 cm wide
cabinets where the installation depth of the PDU is crucial as the power leads
might block the flow of hot exhaust air and create a ‘hotspot’ in the cabinet.
These mounting plates can be used for many different cabinets.
7
Schleifenbauer User Manual - v1
3. Toolless Mounts
‘Toolless Mounts’ are attachment points on the rear of the profile that allow
the PDU to be hung in the cabinet without using tools. Toolless Mounting can
be done as single PDU or double PDUs. However, the housing must feature
special holes for this mounting method. If required, supply brackets with the
appropriate mounting holes can also be supplied.
8
Schleifenbauer User Manual - v1
4. Mounting with Profile clamps
The clamps, which are made from spring steel, can be installed in the position of
your choice. The clamp can be fit around the profile and secured in place with a
fastening screw. To ensure adequate strength, one clamp must be fit for every 50
cm of profile length.
The clamps must fit tightly against the profile to avoid wasted space in the
cabinet.
 Note that for correct fitting using profile clamps, the back of the clamps must be mounted against a rear
partition. If there is only ‘support’ for the clamp in the area of the fastening bolt, it is recommended to fit a
partition first to which the clamp can be subsequently secured. An optional reinforcement plate is available
for this, as shown above.
 Please note that extra care is required when using the stainless steel profile clamps, which will be used for
vertical mounting.
 Please note that, due to the extensive number of possible methods for mounting PDUs in cabinets,
Schleifenbauer offers the option of developing tailor-made solutions in collaboration with the customer.
9
Schleifenbauer User Manual - v1
CONNECTING TO CABLING
Connecting the PDU to a 10/100 Mbps LAN Ethernet Port
Connecting the PDU to a Local Area Network (LAN) provides communication
through an Ethernet network, if the PDU is connected exclusively, or
simultaneously with the data bus. The RJ45 connector for the network cable
must be plugged into the Ethernet port.
• Obtain an Ethernet Cable (RJ45 connector)
• Connect one end of the Ethernet cable to the Ethernet port on the PDU and
second end to the Ethernet connector on the LAN device.
Connecting the PDU to a data bus
The serial data bus in the Schleifenbauer PDU uses CAT5 or better patch cables.
Each PDU features 2 RJ45 connectors, which make looping possible.
• Connect the RJ45 plug to one of the connectors labelled data bus. Since
both data bus connectors are identical, any of the connectors labelled as data
bus on PDU can be connected.
• Connect the other end of the patch cable to the nearest PDU that is already
connected to the data bus.
Connecting a sensor to the sensor port
The PDU has a sensor port for connecting a digital temperature sensor, one
dry switch contact or a combined sensor for temperature/humidity. The PDU
registers which sensor is connected and automatically adapts the menu in the
display to the sensor(s) that it has detected.
•
10
Connect the RJ12 connector to the PDU sensor port.
Schleifenbauer User Manual - v1
NETWORK COMMUNICATION CONFIGURATION
IP Network Configuration
The Dynamic Host Configuration Protocol (DHCP) protocol can configure the IP address, subnet mask, gateway
address, and Domain Name System (DNS) servers, dynamically. By default, the PDU is configured to get the IP address
from DHCP automatically. If the PDU does not receive an IP address within a set time, it will proceed using the default
address as 192.168.1.220 (and as subnet mask: 255.255.255.0). The IP settings can be manually configured if the
DHCP is disabled by using the web interface. Please check Web Interface Section for further details. The actual IP
address and settings can be seen on the LCD display.
ťť When using ‘DHCP fallback to static IP’, it is recommended to enter a unique IP address for each PDU. This
approach prevents all of the PDUs from being assigned the same IP address in the event of a faulty DHCP
server.
11
Schleifenbauer User Manual - v1
OPERATION
The Intelligent PDU features a display with scroll buttons, LEDs and some ports for connecting accessories. Please
keep in mind that PDUs may differ in configuration and may not have a display.
link
This LED is lit if a network connection has been established.
pwr
If the hPDU has been connected to
an appropriate power source, this
LED is lit and dims every 2 seconds
to indicate that the controller is
operating correctly. The LED flashes
when handling external requests
received via Ethernet or the data
bus and during a firmware upgrade
procedure.
kWh pulse led
This LED pulses at a speed of 3200
pulses per kWh.
data bus
2 RJ45 connectors for connecting
the data bus wiring.
10/100
Ethernet
sensor
RJ12 connector for connecting a
T/H sensor, or a dry contact or a
PDU Sensor Module for connecting
multiple sensors.
rst
Sunken reset button (use a paper
clip) to perform a hard reboot on
the hPDU. This has no effect on
power distribution!
LCD display
This display presents the measurement values and settings of the
PDU. You can scroll between the
pages using the scroll buttons.
scroll buttons
You can use these buttons to
scroll through the pages in the
LCD display.
ťPressing
ť
both buttons together will return you to the home/load page.
It is also used to reset the access and tcp/ip settings
12
Schleifenbauer User Manual - v1
KWH PULSE LED
An LED mounted at the top right of the LCD display, which flashes when current is drawn by the PDU. The speed at
which this LED flashes depends on the load on the PDU. It flashes at 3200 pulses for each kWh.
LCD SCREENS
Please note that this section applies for the Schleifenbauer PDUs, which have the LCD screen.
Many of the Schleifenbauer Intelligent PDUs are equipped with an LCD back light display. Next to the display two
buttons can be found, which allow for scrolling up and down through the pages of information, can be found. These
LCD pages provide information regarding the measurements as well as the product information and settings. At the
bottom of every page, the page number out of the total page number can be found (01/18 means 1st page of 18
pages). The amount of available pages depends on the configuration of the PDU.
 Please keep in mind that the PDU can not be controlled locally. To change the settings or take actions such
as switching an outlet, one of the interfaces should be used.
Load Page
This page contains the information of the Load per phase, temperature and humidity.
DS: S
hows the status of the dry switch contact. Every PDU contains one dry switch contact.
Te: Shows the temperature sensors’ measurement in degrees Celsius. This value will not be shown when there is no
temperature sensor connected.
Rh: Shows the humidity sensors’ measurement in relative humidity percentage. This value will not be shown when
there is no humidity sensor connected.
L1: Shows the load of the first phase in Amperes. The bar shows how much of the maximum rating is used.
MAX: Shows the maximum rating of the PDU. If the PDU has multiple phases, this is the maximum rating of each
single phase.
 Please note that this value is not a setting, it depends on the type of PDU.
 Please keep in mind that there can be up to 3 phases. According to the amount of phases, L1, L2 and L3 can
be shown with a bar next to each.
13
Schleifenbauer User Manual - v1
Outlets Page
This page shows the current state of the outlets. The state can be:
• 0= Off,
• 1= On,
• s= Scheduled to go off
• S= Scheduled to go on
• p= Power cycling.
 Please keep in mind that picture shows outlets from 1 to 18. When there are more than 9 outlets, all the outlets’
states will be shown in this page. First number in the line indicates first outlet number of the line. For example,
’01’ means the first outlet in the first line is the number 1. ’10’ in the second line means the first outlet in the
first line is the number 10.
Input Page
I: Shows input current in Amperes.
P: Shows input power in Watts.
U: Shows input voltage in Volts.
Pf: Shows input power factor (real power divided by apparent power) in percentage.
Et: Shows total energy in Kilowatt-hours.
Es: Shows subtotal energy in Kilowatt-hours.
Input x: Shows the name of the Input. This information can be configured from the Web Interface, Inputs tab or from
the other interfaces.
INPUT L2: Shows the phase, whose information is listed in this LCD page.
 Please keep in mind that for every phase there will be another LCD page. It can be up to 3 pages.
 Please note that in a single phase system L1 would show total consumption. L2 and L3 would be two separate
measurements if they are shown.
14
Schleifenbauer User Manual - v1
Outlet Page
I: Shows outlet current in Amperes.
P: Shows outlet power in Watts.
U: Shows outlet voltage in Volts.
Pf: Shows outlet power factor (real power divided by apparent power) in percentage.
Et: Shows total energy in Kilowatt-hours for this outlet.
Es: Shows subtotal energy in Kilowatt-hours for this outlet.
Outlet x: Shows the name of the outlet. This information can be configured from the Web Interface, Outlets tab or
from the other interfaces.
OUTPUT 17: Shows the outlet number, whose information listed in this LCD page.
 Please keep in mind that for every outlet, there will be another LCD page. There can be maximum 45 outlets,
hence 45 outlet LCD pages.
Sensor Page(s)
If a residual current sensor is connected, these new LCD page(s) will appear. First character next to the sensor channel
number shows the sensor type and second character shows the sensor measurement. For example, a temperature
sensor is connected to port number 13 and temperature value is 24 degrees Celsius. The types of the sensors can be
listed as:
Analog:
• T: temperature (°C)
• H: humidity (%)
• R: residual current (mA)
• A: AC residual current (mA)
• D: DC residual current (mA)
• B: branch residual current (mA)
Digital:
• I: dry switch contact
• S: error status
• Y: activity
15
Schleifenbauer User Manual - v1
Other:
• X: unused
 Please keep in mind that these pages will not be shown if residual current sensor is not connected to the PDU.
 Please note that humidity sensor is only available together with a temperature sensor.
Information pages
Adr: Shows the address of this unit on the data bus.
Tag: Shows the vanity tag.
Nme: Shows the device name.
Loc: Shows the location of the device.
 Please keep in mind that, when there is an active request to this unit on the data bus, the address turns white.
 Please note that unit address, vanity tag, unit name and unit location can be configured from the Web
Interface, System Tab, Settings Section or from the other interfaces.
Lnk: Shows the current Ethernet link status of the device.
St: Shows the IP status (DHCP: Acquiring/Bound, Static, Static fallback, or ‘-‘ when there is no link).
IP: Shows the IP address of the device.
NM: Shows the subnet mask of the device.
GW: Shows the IP address of the Gateway or Router.
MAC: Shows the MAC address of the device.
16
Schleifenbauer User Manual - v1
Mode: Shows the mode of this unit. For further information please see Databus Modes Section.
HTTP: Shows through which protocol and over which port the connection is provided for this interface. HTTP
interface cannot be disabled.
API: Shows through which protocol and over which port the connection is provided for this interface as well as the
status, such as off.
Modbus: Shows through which protocol and over which port the connection is provided for this interface as well as
the status such as off.
SNMP: Shows through which protocol and over which port the connection is provided for this interface as well as
the status such as off.
 Please keep in mind that, when there is active communication of the interface, that interface turns white as it
can be seen above.
Ver Shows the firmware version and build ID of the firmware of the device.
ID: Shows the unique hardware address of this device’s controller.
SN: Shows the unique sequential production serial number of this device. This number can also be found on the PDU.
Prt: Shows the product identification tag of this device. This number can also be found on the PDU.
Ord: Shows the reference order number for internal Schleifenbauer uses.
Ph: Shows the number of the phases of this device.
O: Shows the total number of outlets on this device.
S: Shows the number of switchable outlets on this device.
M: Shows the number of metered outlets on this device.
BLINKING LCD SCREEN
The LCD screen flashes when any alert is active. Pressing any button can stop the blinking for a limited time. To stop
the blinking motion, the cause of alert should be resolved, and the alert should be cleared. Clearing can be done by
pressing both buttons simultaneously, if this possibility is enabled in the PDU settings. The setting can be changed
from the Web Interface, Settings section or from the other interfaces.
17
Schleifenbauer User Manual - v1
DOWNGRADE/UPGRADE
The Schleifenbauer Intelligent PDU has the ability to be upgraded or downgraded.
 Please read the Firmware Updater tool Manual and related Release Notes before starting to upgrade/
downgrade.
 Please pay attention to the warnings given in the Release Notes before upgrade/downgrade.
1. Download Firmware updater tool and Firmware updater tool manual from http://documentation.schleifenbauer.
eu/firmware/PDU_firmware/
2. Download the desired SPFW bin file.
3. Apply the steps below, which are also given in Firmware Updater Tool Manual.
4. Run the updater tool by double clicking the file.
 If not using a Schleifenbauer Gateway, proceed with step 9.
5. Upgrade your Gateway to the latest version.
6. Make sure the data bus is OK and all devices are visible.
7. Disable all running interfaces (MySQL etc) except for API.​
8. Uncheck the ‘​R​ing redundancy’​c​heck box.
9. If upgrading a PDU running 2.10 through API without a gateway, make sure external applications (like DC Spyder)
don’t use the API at the same time.
10. Enter the full I​P address and type of your desired interface (Gateway/PDU/RS485 converter).
 Please note that during upgrading directly the PDU, it should be running 2.10 or higher and API should be
enabled.
11. Click on ‘Select bin file and upload’ to start the update process. The tool will first scan the bus to find all used
firmware versions. T​he update speed may vary depending on used interface and firmware versions found on the bus,
please be patient.
12. Make sure all devices were upgraded, by looking at the firmware versions shown after updating. If some units still
have the old version, you can first try to restart the devices again by clicking on “Restart all units” if that still does not
work you may try again.
 If not using a Gateway, you can skip this last step.
13. In some cases, some devices fail upgrading. This is a known issue, in these cases check the ‘​deep update’ o
​ ption.
This will send the firmware update in a more thorough fashion. Note that this takes considerably more time to finish.
14. Restore interfaces and ring redundancy if desired.
18
Schleifenbauer User Manual - v1
INTERFACES
Communication with the Schleifenbauer Intelligent PDU can be done with Modbus /TCP, Web Interface, Simple
Network Management Protocol (SNMP) and Schleifenbauer’s Application Programming Interface (API).
SNMP
SNMP defines a protocol to communicate with devices without defining where or how information is stored for supervision
and control. Enabling SNMP communication provides retrieving and setting information of the PDU. Schleifenbauer
Intelligent PDU supports SNMP v1 or v2c. Since SNMP v3 is still in the development phase, it is disabled. Through SNMP,
Management Information Base-2 (MIB-2) settings can be configured. The MIB file describes all the registers via SNMP.
Through Web Interface, SNMP section;
• enabling traps,
• destination IP addresses for the traps,
• SNMP behavior such as read only, read and scan or read-write as well as the target community,
• detailed traps settings ,which can be set separately, can be configured and maintained.  Please note that the SNMP listen port is configured as 161 and the trap port is configured as 162, by default.
To use different ports, please configure these port preferences.
 Please note that MIB objects are not described in this manual. A MIB browser tool should be used to get
descriptions of MIB objects and traps. The SCHLEIFENBAUER-DATABUS-MIB file can be downloaded from
www.documentation.schleifenbauer.eu/firmware/snmp.
For further details of settings please check Web Interface, SNMP section.
MODBUS/TCP
Modbus defines only a protocol to communicate with devices without defining where or how information is stored for
supervision and control. Transmission Control Protocol (TCP) and Internet Protocol (IP) are the transport protocols
for internet and they are used together for Modbus. All requests are sent via TCP/IP over port 502, by default.
Modbus/TCP access can be enabled from Web Interface. For further details regarding Modbus/TCP, please check the
Modbus document at appendix or Schleifenbauer website.
 Please note that enabling Modbus/TCP may create safety risks, since Modbus is designed to work for a trusted
network.
API
Application Programming Interface is a set of tools, protocols and routines for building software and applications.
Hence, it is for the use of programmers and provides facilities to developing applications for the system by using that
system’s programming language. Schleifenbauer has its own API that can be used to build custom applications to
communicate with a PDU.
 Please note that the Schleifenbauer API can be found at http://documentation.schleifenbauer.eu/firmware.
19
Schleifenbauer User Manual - v1
WEB INTERFACE
The web interface consists of an upper status bar and seven tabs. Any tab can be clicked to see the desired information
or settings.
Login
To reach the Web Interface, the IP address of the Schleifenbauer Intelligent PDU should be written to the address
bar of the browser. The web interface is protected by a login username and a password. The PDU has 5 user profiles:
• super,
• admin,
• power,
• user,
• viewer.
The default password for each profile equals the username of the profile. For example the default password for the
‘admin’ user profile is “admin”.
Please fill the ‘User Name’ and ‘Password’ fields accordingly and then click login or press enter.
 Please note that all user profile’s passwords should be changed at the first connection by the administrator,
according to the situation and planned usage such as colocation mode etc.
The PDU user authentication model provides 5 different accounts which can be used to access the web interface
and, in the future, SNMP v3. The user accounts are (in decreasing order of access rights): super, admin, power, user
and viewer. It should be noted that super is only intended for use by Schleifenbauer personnel or production/testing
software. The access rights of the different user accounts, together with data bus and unauthenticated ethernet, are
shown in the following table.
unit address
name, tag, location
import names
outl. & sens. names
alert settings
reset subtotals
switching
reset alerts / restart
viewing
FW upgrade
scan (bridge mode)
change PDU mode
interface settings
IP address
data bus
super / admin
power
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
user
x
x
x
x
Each user can change all lesser user passwords, in addition to their own password.
20
Schleifenbauer User Manual - v1
viewer
x
eth unauth.
x
x
x
x
x
x
x
x
x
x
x
In addition to the current permission model, the permissions of the user role can be modified only by the admin or
super role. The user role has a new optional permission: outlet & sensor names ( Please check above table). This
permission is disabled by default but can be enabled in the web interface. The permissions to switch outlets, reset
alerts/reset device and various settings like LCD etc. are enabled by default but can be disabled if needed. Please
check the Web Interface Section, Interfaces, User Management item 136 for the settings.
 Please keep in mind that ‘super’ user profile should never be used since it allows changing the configuration
of PDU. It’s password has to be changed on first installation.
 Please keep in mind that the session should be always terminated by clicking the logout tab, by refreshing the
web page or by closing the internet browser.
Status Bar
21
1.
2.
3.
4.
5.
6.
7.
Address: Shows the address of this unit on the data bus.
Name: Shows the device name, which can be configured from the System Tab, Settings Section.
Tag: Shows the vanity tag, which can be configured from the System Tab, Settings Section.
Location: Shows the location of the device, which can be configured from the System Tab, Settings Section.
FW Version: Shows the firmware version of the device.
S/N: Shows the serial number of the device.
Updated on: Shows the last time the Web Interface got updated with data from the unit. If the displayed data
is stale (such as connection problems), the box will turn red.
8.
9.
IP address: Shows the IP address of the device.
Master Device: This section shows the list of bridged devices on the data bus accessible over this device. Note
that this list will be empty if the device is not in the “Bridge Mode” or “Twin Master”.
Schleifenbauer User Manual - v1
Choosing another device from this list will display chosen device’s information and data in the Web Interface. Scanning
the data bus/updating this device list is done by selecting “…scan data bus…”. Since the unit will never perform this
action by itself scanning should be done for every change, which has been made to the data bus. After scanning
completes, the number of found devices will be shown, and three blue options will be available. “rescan” does the
scanning again. “arrow” widens the list of the units when there is a high amount of units. “X’’ closes the window.
When zero-addressed or duplicate units are detected, these will be shown in red and the user will be offered the
option to set a new address by clicking the “set address” button.
 Please keep in mind that the Interfaces section is not shown when viewing a bridged device, because none
of it’s contents can be retrieved or changed via the data bus.
Ring State: The data bus ring state is indicated in the orange box. To get more information about the current ring
state, you can hover the ring state text.
 Please keep in mind that If a PDU without ring redundancy is used, the data bus should be connected to
the right data bus connector.
Locked-Editable Button: Sections having this button are only editable when they are unlocked. The button shows
the current state. A section is unlocked by clicking the lock symbol and vice versa.
22
Schleifenbauer User Manual - v1
Dashboard
10. System Status: An overview of the device status can be found under this section.
11. Device Status Code: This code shows the status of the device in terms of errors. Possible device status code
messages are:
• 0 OK: Device status is OK.
• 1 Alert flagged: One or more alerts have been flagged. Please check the other alert fields to see the cause of the
alert. It can be one of the following sources:
• temperature alert
• input current alert
• output current alert
• input voltage alert
• output current drop alert
• input current drop alert
• sensor change alert
• 2 Setting(s) initialized: Some settings have been reset to default values. This may occur after a factory reset or
a firmware upgrade.
• 4 Power-on reset: The device booted after a power loss. It can be one of the following reasons:
• because of inserting the PDU power plug (mostly intentional. It can be unintentional if someone removed
the power plug accidentally),
• because of a power outage (unintentional),
• because of a defect in the internal power supply.
• 8 External reset: The device has been reset by pressing the reset button on the unit.
• 16 Watchdog timer caused reset: The device rebooted due to an internal error.
• 32 Brownout detected: The device rebooted because a voltage drop has been detected. This may indicate a
defect in the internal power supply or a dip in external power supply.
• 64 Controller error: A hardware error has been detected.
• 128 Slave module was reset: A communication issue has been detected with an outlet slave module.
23
Schleifenbauer User Manual - v1
 Please note that the device status code is the sum of all the active status codes.
• Example 1: When ‘Slave module was reset’ and ‘Power-on reset’ are active at the same time, the device
status code will be 132 (128+4).
• Example 2: When ‘Slave module was reset’, ‘Power-on reset’ and ‘Alert flagged’ are active at the same
time, the device status code will be 133 (128+4+1).
 Please keep in mind that when a non-zero code occurs, the cause should be found and resolved first and
then the alert should be reset from System Tab, Reset Section, Reset Alerts (item 61).
 Please note that if the code is frequently returning to the same device status code, this may indicate a
defect. Please contact Schleifenbauer support from support@schleifenbauer.eu.
12. Temperature Alert: Temperature alert raises for temperatures, which exceed the user’s maximum temperature
setting. It will be showing sensor number in the alert description and 0 if everything is all right. For the alert
settings please check System Tab and Settings Section, Maximum temperature.
13. Input Current Alert: Input current alert raises for inputs, which exceed the user’s maximum current setting
for that input. In case multiple inputs are in alert state, the highest input will be indicated as number of the
phase. ‘0’ is the indication of everything is all right. For the alert settings please check Inputs Tab, Alert Current.
14. Output Current Alert: Output current alert raises for outlets, which exceed the user’s maximum current
setting for that outlet. In case multiple outlets are in alert state, the highest outlet will be indicated as number
of outlet. ‘0’ is the indication of everything is all right. For the alert settings please check Outputs Tab, Alert
Current.
15. Input Voltage Alert: Input voltage alert raises in case the voltage on an input drops below normal operating
range, even if the drop is very short. In case multiple inputs are in alert state, the highest input will be indicated
as number of the phase. ‘0’ is the indication of everything is all right.
16. Output Current Drop Alert: Output current drop alert raises due to a sudden current drop for an outlet. In
case multiple outlets are in alert state, the highest output will be indicated. Please keep in mind that to be
able to use this alert it should be enabled from System Tab, Settings Section, Current Drop Detection.
17. Input Current Drop Alert: Input current drop alert raises due to a sudden current drop for an input. In case
multiple inputs are in alert state, the highest input will be indicated. Please keep in mind that to be able to use
this alert it should be enabled from System Tab, Settings Section, Current Drop Detection.
18. Sensor Change Alert: Sensor change alert raises when a sensor type has been changed. If multiple sensor
types have been changed the lowest sensor channel will be shown. For the alert setting please check System
Tab, Settings section, Sensor Change Alert.
19. Load: Shows the name, the load, and user’s alert setting of each input. The user’s alert setting is displayed
after the load bar, and also shown in the load bar. Input names and alert settings can be changed from the
inputs section. ‘max 16A’ refers to this unit’s physical current limit and cannot be changed.
20. Interfaces: Gives a summary of the interfaces and their status. Data shown here is read-only but these settings
can be changed at the interfaces section.
24
Schleifenbauer User Manual - v1
Sensors
 Please note that the number in the red circle shows the number of detected sensors.
21. Locked/Unlocked: Please check status bar section for detailed information.
22. Name: A name, which consists of maximum 8 characters, can be given to the each sensor. When additional
sensors are connected, they will also appear in the list. The sensors can be hidden in the User Interface by
starting their name with a “-” sign when it is not used or not connected.
23. Type: Shows the type of the sensor.
24. Value: Shows the value of the sensor measurement.
 Please check LCD screens, sensor pages for detailed information regarding the sensors can be connected.
Inputs
25. Inputs: This section shows the measurement values, their settings for the input phases and the number of
inputs of the PDU.
26. Name: A name, which consists of maximum 8 characters, can be assigned to a specific input for making the
identification easier. Inputs can be hidden in the User Interface by starting the name with a “-” sign when it is
not used or not connected.
27. Total: Shows the total amount of energy in Kilowatt-hours per input. This value is not resettable during the
lifetime of the device.
28. Subtotal: Shows the subtotal amount of energy in Kilowatt-hours per input. This value can be reset to zero
using the RESET button.
 Please note that a confirmation window will pop up before the reset.
29.
30.
31.
32.
33.
34.
35.
36.
25
Power (VA): Shows the power per input in Volt-Amperes.
Power (W): Shows the power per input in Watts.
PF: Shows the power factor (real power divided by apparent power) per input in percentage.
Current: Shows the actual current value in Amperes per input.
Peak Current: Shows highest current value in Amperes per input since last peak and dips reset.
Voltage: Shows the actual voltage per input in Volts.
Min Voltage: Shows voltage dip value per input in Volts since last peaks and dips reset.
Alert Current: Shows the value of the upper limit, which the actual current is allowed to reach. If the actual
current is higher than this for a time period as defined by Peak Duration, which can be configured from System
Tab-Settings Section, an input current alert is generated.
Schleifenbauer User Manual - v1
Outlets
37. Name: A name, which consists of maximum 8 characters, can be assigned to specific outlet for making the
identification easier. Outlets can be hidden in the User Interface by starting the name with a “-” sign when it
is not used or not connected.
38. Total: Shows the total amount of energy in Kilowatt-hours consumed per outlet. This value is not resettable.
39. Subtotal: Shows the subtotal amount of energy in Kilowatt-hours per outlet. This value can be reset to zero
using the RESET button.

Please note that a confirmation window will pop up before the reset.
40.
41.
42.
43.
44.
45.
46.
Power (VA): Shows the power per outlet in Volt-Amperes.
Power (W): Shows the power per outlet in Watts.
PF: Shows the power factor (real power divided by apparent power) per outlet in percentage.
Current: Shows the actual current value per outlet in Amperes.
Peak Current: Shows the highest current value in Amperes per outlet since last peak and dips reset.
Voltage: Shows the actual voltage per outlet in Volts.
Alert Current: Shows the value of the upper limit, which the actual current is allowed to reach. If the actual
current is higher than this for Peak Duration, which can be configured from System Tab-Settings Section, an
output current alert is generated.
47. Delay: Shows the amount of seconds to delay per outlet before switching on, when outlet power-up mode is
configured as ‘same state as power down, but delayed by individual outlet delay‘.
48. Power Cycle Time: Settings for the duration of the OFF state when an outlet is power cycled.
49. State: Shows the status of the outlet. It can be on, off, scheduled to switch on, scheduled to switch off or
power cycling.
26
Schleifenbauer User Manual - v1
50. Unlock: This button provides a protection for switching. In order to switch an outlet state or power cycle it,
it needs to be unlocked first before any switching activity is allowed. If the outlet is on, then switch off and
power cycle buttons will appear when it is unlocked. If the outlet is off, only the switch on button will appear.
Switch On/Off: After unlocking, an outlet can be switched to its opposite state.
Power Cycle: After unlocking, an outlet can be power cycled. An outlet with actual state ON will be switched
OFF and after a power cycle time it will automatically switch ON again. If the outlet is in the OFF state, it can
not be power cycled.
System
51.
52.
53.
54.
55.
56.
27
This section provides the identification information and configuration settings of the device.
Firmware Version: Shows the firmware version of this device.
SPDM Version: Shows the version of the Schleifenbauer Products Data Model (SPDM) of this device.
Sales Order Number: Shows the reference number for internal Schleifenbauer uses.
Product ID: Shows the product identification tag of this device.
Serial Number: Shows the unique sequential production serial number of this device.
Schleifenbauer User Manual - v1
57. Hardware Address: Shows the unique hardware address of this devices controller.
58. Unit Address: Shows the address of this unit on the data bus. This address is user defined and can be between
1 and 65535. When using Modbus, unit address can be between 1 and 247.
59. Reset: This section provides ways to reset alerts on the device, reset the peaks and dips information, and
restart its controller.
60. Restart Device: Restarting is a warm reboot and only restarts the controller. Since outlets remain intact, it has
no effect on the outlet status of switched outlets. Please note that an executed restarting the device will reset
ALL alerts and all peak registrations.
61. Reset Alerts: Clears all the alerts on this device. Note that if the cause of the alert has not been resolved, the
alert will immediately reappear after the reset.
62. Reset Peaks And Dips: Clears all the current peaks and voltage dips.
63. Configuration: These fields give the information on the specifications of the device. For example the PDU
supports up to 3 phases with a total of 45 individually switched and measured outlets.
64. Number Of Phases: Shows the number of the phases (inputs) on this device.
65. Number Of Outlets: Shows the total amount of the outlets (outputs) on this device.
66. Number Of Switchable Outlets: Shows the number of switchable outlets on this device.
67. Number of Metered outlets: Shows the number of metered outlets on this device.
68. Maximum Load (A): Shows the maximum load per phase.
69. Number Of Sensors: Shows the number of the sensors detected on the sensor port.
70. Settings: This section provides configuration of each device according to your specifications.
71. Device Name: A device name, which has maximum 16 characters, can be written in this section if wanted.
72. Device Location: A device location, which has maximum 16 characters, can be written in this section to
specify its location.
73. Vanity Tag: A vanity tag, which has maximum 20 characters, can be written in this section. This information
will be visible in the LCD display.
74. Local Alert Reset Allowed: Provides a possibility to reset alerts by pressing the Page Up and Page Down
buttons at the same time. In case this setting is set as NO, alerts can only be reset via gateway, any interface
or a monitoring application.
75. Display Backlight Timeout: Setting for switching off display backlight after certain set time. It can be
configured as 10 seconds, 1 minute, 2 minutes or 4 minutes.
76. Display Orientation: Setting for the orientation of the LCD display. It can be set as:
• no display
• vertical, display on top
• vertical, upside down
• horizontal, display at left side
• horizontal, display at right side
77. Peak Duration: Setting for the amount of time in milliseconds that a current overload should be detected
before an alert is raised. It is preferred to be long, such as 1000 milliseconds or more.
78. Current Drop Detection: Setting for enabling detection of sudden current drops in the inputs and outlets.
Can be set as:
• always off
• input(s) only
• outputs only
• both inputs and outputs
 Please note that current drop detection is working in the following way: When the actual current of a
channel (can be input or metered outlet) is greater then 0.5A (500mA) and drops with more than 50% of its
value, then an input/outlet current drop alert is raised. For example:
• Actual current = 0.4A, drops to 0A -> no alert
• Actual current = 1A, drops to 0.6A -> no alert
• Actual current = 1A, drops to 0.4A -> alert is raised
28
Schleifenbauer User Manual - v1
79. Fixed Outlet Delay: Setting for delay time between 2 switch actions in milliseconds. Default value is 100
milliseconds and values below 100 milliseconds are not accepted.
80. Outlet Powerup Mode: Shows the behavior of the outlets when a PDU is powered.
It can be set as:
• off: At powerup, all the outlets are kept in the off state.
• same state as power down: At powerup, all the outlets are set to their last known state by respecting the
fixed outlet delay.
• same state as power down, but delayed by the individual outlet delay: At powerup, all the outlets are
set to their last known state, but delayed by the individual outlet delay.
81. Maximum Temperature: Shows the value of the upper limit that the maximum temperature is allowed to
reach in degrees Celsius. An alert will be raised if the temperature of any connected temperature sensor
exceeds the set value. It can be disabled by defining it as ‘0’.
82. Sensor Change Alert: Informs about the change in sensors such as new sensor, disconnected sensor or
broken sensor for this device.
83. Outlet Unlock Override: Setting for overriding the outlet unlock registers. When this setting is enabled
outlets can be switched or power cycled without unlocking them first.
 Note that this makes it easier for the user to switch outlets using SNMP, Modbus and API, but also makes it
easier to switch the wrong outlet.
 Please keep in mind that this setting isn’t valid for the web interface. To be able to make a change through
web interface, the relevant part has to be unlocked first.
Interfaces
84. Network Status: Shows the live status of the network.
85. Access Control: Limits access to all network services (such as SNMP, web server, etc.) on this device. Only the
IP addresses listed in this section can connect. Access control is specified in CIDR notation.
29
Schleifenbauer User Manual - v1
 Please note that mistakes in configuration may lock you out of this PDU!
86. Web Client IP: Shows the IP address of the current browser.
87. Allowed IP Range(s): Shows the IP address ranges that are allowed to access this device over the network.
88. DHCP: Setting for enabling or disabling DHCP. Settings between 89 to 93 are valid only if this setting is
configured as disabled.
89. DHCP Fallback To Static IP: If the device fails to get an IP address from the DHCP server automatically, after a
configured delay time it will fallback to the static IP address configured in the DHCP & Static IP Settings. This
setting can be chosen as enabled or disabled and does not have any effect if DHCP is disabled.
90. DHCP Fallback Delay: Shows the delay time in seconds for the fallback to static IP.
91. IP Address: Static IP configuration of this device if DHCP is disabled, or if ‘DHCP fallback’ is enabled.
92. Subnet Mask: Shows the subnet mask address. This value may range from 0.0.0.0 to 255.255.255.255.
93. Gateway Address: Setting to specify the IP address of the Gateway or Router. Please note that this “Gateway’
is not the same as the Schleifenbauer “Gateway’ device.
94. Primary DNS: Setting to specify the IP address of the primary DNS server
95. Secondary DNS: Setting to specify the IP address of the secondary DNS server
96. Hostname: Shows the hostname of the device. This part is optional.
97. Device Mode: Shows the mode of the device.
• Data bus
• Hybrid
• Bridge
• Colocation (Data bus management)
• Colocation (Data bus viewer)
• Twin master
 Please check Section Data Bus Modes for further details.
98. SNMP: Configures the SNMP settings of this device.
99. SNMP v1/v2c: Setting for enabling or disabling SNMP v1 and v2c.
100. SNMP v3: Since SNMP v3 is not implemented yet SNMP v3 is disabled.
101. Listen Port: Shows the listening port on this device.
102. Traps: Provides the configuration of enabling/disabling SNMP traps on alerts and other system events.
Individual SNMP trap types can be enabled/disabled in the following Traps section.
103. Trap Port: Shows the port that the traps are sent to.
104. Trap Destination IP(s): Shows the IP address that traps are sent to.
105. SNMP Behavior: This setting is used to restrict SNMP to read-only access to prevent unauthorised actions on
the device since SNMP v1 / v2c is not a secure protocol even with community strings.
106. Read Community: Shows the SNMP community string for read access.
107. Write Community: Shows the SNMP community string for write access.
108. Trap Community: Shows the SNMP community string for traps.
109. MIB-2 Management Values: Shows the MIB-2 Management Values that are configured over the SNMP. These
values are used for the SNMP management software and cannot be changed using the web interface.
110. SysContact: Shows the contact person in charge of the system being contacted.
111. SysName: Shows the name assigned to the system.
112. SysLocation: Shows the location of the system.
113. Traps: Individual traps can be configured from this section. “SNMP Trap” option above should be enabled for
any traps to be sent. Please note that traps are only sent once when an alert is raised. This action sends SNMP
notifications to one or multiple IP addresses after the selected event occurs.
114. Network Connectivity: Sends a trap when the network connection is established or re-established.
115. SNMP Auth Fail: Sends a trap when an SNMP request with invalid credentials is attempted.
116. Device Status Code: Sends a trap when the device status code changes.
30
Schleifenbauer User Manual - v1
117. Temperature Alert: Sends a trap when the temperature alert is raised.
118. Input Current Alert: Sends a trap when the input current alert is raised.
119. Output Current Alert: Sends a trap when the output current alert is raised.
120. Input Voltage Alert: Sends a trap when the input voltage alert is raised.
121. Output Current Drop Alert: Sends a trap when the output current drop alert is raised.
122. Input Current Drop Alert: Sends a trap when the input current drop alert is raised.
123. Sensor Change Alert: Sends a trap when there is a change in the sensors such as new sensor, disconnected
sensor or broken sensor.
124. Ring State Changed: Sends a trap when the data bus ring state changed. This only applies when the PDU is
in Bridge or Twin mode.
125. HTTP: Indicates if the web interface is accessible through HTTP. Since HTTPS is not implemented yet, it cannot
be disabled. Please note that if HTTPS is enabled and HTTP is disabled, the web interface still be accessible
with encryption.
126. HTTP Port: Shows the port number that HTTP server watches and responds to. It is configured as 80 by
default and can be changed.
31
Schleifenbauer User Manual - v1
127. HTTPS: Indicates if the connection is encrypted. Since the configuration is in development phase, it is
disabled for now.
128. HTTPS Port: Shows the port number that HTTPS server watches and responds to
129. API: Please check Interfaces section, API part for the detailed information. This section enables the TCP/IP
socket, through which several external applications and scripts can access the data bus. This communication
is encrypted using RC4 and a 128-bit key.
 Please note that enabling this option without changing the key imposes a security risk! If API is enabled
then the PDU can be scripted.
130. API: Provides the configuration of enabling or disabling the API.
131. Port: Shows the API port. This port cannot be changed.
132. Key: Shows the RC4 encryption key for API communication. It must be 16 characters.
133. Modbus: Please check Interfaces section, Modbus part for detailed information. Please note that Modbus/
TCP is not a secure protocol and there is no authentication. Enabling Modbus/TCP on a non-trusted network
might create a security risk. Please check Modbus TCP Behavior below for read-only option.
134. Modbus TCP: Provides the configuration of enabling or disabling the Modbus/TCP server.
135. Modbus TCP Behavior: Provides the configuration of read-write or read only. This option can be used to
restrict Modbus/TCP clients to read-only mode to prevent accidental or malicious modifications on the device
using Modbus/TCP.
136. Modbus TCP Port: Shows the listen port of Modbus/TCP server.
137. User Management: Users’ details can be changed using this section. A user account can be disabled by
leaving the username field blank.
 Please note that only some user levels are allowed to do changes, and this section will not be displayed
for other users. In more detail, a user can only change its own and lower users name and passwords. For
example, admin can change user, but user can not change power or admin. For the user rights, please
check the Login part this manual in Web Interfaces.
Logout
138. Logout: Tab, which provides the termination of the session. After clicking this tab, a screen which has a
leading to login appears.
32
Schleifenbauer User Manual - v1
DATA BUS MODES
The Schleifenbauer PDU firmware provides different PDU mode settings to control data accessibility over its Ethernet
and data bus connections, and enables or disables the accessibility of the other units over the data bus.
1. DATA BUS MODE
The Schleifenbauer PDU works like a first generation Schleifenbauer PDU in this mode. In data bus mode all the
Ethernet interfaces are disabled except for the web server. The web server is used to configure the PDU mode. In this
mode the PDU should be connected to the data bus.
2. HYBRID MODE
Hybrid mode is a very similar mode to the data bus mode. Additional to the data bus mode, all the Ethernet interfaces
can be enabled. Each Intelligent PDU can be accessed via it’s Ethernet interface or the data bus, both simultaneously
and independently.
3. COLOCATION MODE
Colocation mode is a variation of the hybrid mode with some exceptions. There are two options in colocation mode:
• Data bus management colocation mode: In this mode outlet switching commands on the data bus will be rejected
by the PDU. This mode provides more control to the floor manager.
• Data bus viewer colocation mode: In this mode, any write command on the data bus, except unit address changes
and firmware upgrades, will be rejected by the PDU. This mode provides more control to the end user.
4. BRIDGE MODE
Bridge mode is a similar mode to the hybrid mode. The difference is; in the bridge mode the PDU is the bridge between
Ethernet and the data bus. All devices in the data bus can be accessed via the bridged PDU. In this mode the PDU can
be used instead of a Schleifenbauer Gateway or RS485 converter.
 Please keep in mind that only a single PDU is allowed to be in the bridge, cluster or twin mode in a single data
bus and other device like a Schleifenbauer Gateway or RS485 converter should not be connected.
 Please note that in the bridge mode one end of the data bus can be connected to the other end to form a ring.
This adds a redundant data bus path to the devices in case one of the data bus connections fails.
 In all firmware versions until version 2.34 both data bus ports of PDU were behaving the same in all device
modes. From version 2.34 on, data bus ports will be used as ‘port 0’ and ‘port 1’ when using Bridge or Twin
mode! During a data bus scan using the API, only devices on data bus port 0 (see image) will be found. Devices
on both ports will be found during a scan using the web Interface, SNMP or Modbus/TCP.
33
Schleifenbauer User Manual - v1
5. TWIN MASTER MODE
Twin master mode is a variation of the bridge mode. In this mode the outlet switching commands are synchronised
to the slave PDU over the data bus. Hence, when a switch command is given from the twin master PDU it will be
switched in the slave PDU, too.
 Please keep in mind that the twin PDUs should have the same amount of switchable outlets, and the slave
PDU should be the only PDU on the data bus. The unit address of the slave should be valid, e.g. not 0 and not
the same as master.
6. CLUSTER MODE (FUTURE MODE)
Cluster mode is also a variation of the bridge mode. As an addition aggregation of data from a limited number of data
bus PDUs is possible. The context of the mode may change with the customer needs.
34
Schleifenbauer User Manual - v1
MAINTENANCE & TROUBLESHOOTING
The Intelligent PDU is equipped with advanced electronics for running the software. Under exceptional circumstances,
a fault may arise in the software. In most cases, resetting the software will resolve the fault:
SOFTWARE RESET
Software reset can be done via the web interface and hardware reset via the button. It is important to understand
that a software reset has no impact on power distribution of the PDU. So a reset can be performed at any time
without having to interrupt the power supply and without losing the settings in the PDU. The software can be reset
using a paper clip or some other kind of thin and rigid rod to press the reset button. This button is mounted behind
the hole labelled as ‘rst’ on the PDU which is next to the Ethernet connection port.
RESTORE IP ACCESS
If the PDU can no longer be accessed via the LAN, for example, because settings have been changed, restoring IP
access may be needed. The following procedure causes the PDU to adopt various default values, which allows it to be
detected on the network again without losing any of the other settings in the PDU. However, the power supply must
be interrupted in order to perform this restore procedure! The procedure is described below:
1. Interrupt the power supply to the PDU.
2. Restore the power supply.
3. Wait for one second and afterwards press the reset button using a paper clip.
4. Wait for a further second and press the reset button again.
5. Wait for a further second and press the reset button again (Hence, it became 3 times in total).
The PDU has now adopted the default values for the IP settings. The access control fields and the web server settings
have also been returned to the standard values.
RECYCLING
Schleifenbauer Products aims to be a social responsible corporation. Therefore, it makes great effort to minimise the
impact of our products to our planet during production as well as during operation. Packaging consists of recyclable
materials and Schleifenbauer asks you to save them for later use or dispose them with applicable regulations.
35
Schleifenbauer User Manual - v1
PRODUCT SPECIFICATIONS
OPERATING
Temperature
Height
Relative humidity
Level of pollution
Environment
Installation category
Protective rating
Conditions of use
Voltage:
Frequency:
Permitted load: Accuracy: Wire colour code:
36
0° to 60° Celsius
-30 to +2000 m
10 to 90% NC
2
Indoors IP20
II
II
Continuous
single-phase 230 V; three-phase 230/400 V
50 Hz.
see product information.
EN 50470-1/3 class B, EN 62053-21: class 1, ± 1%
L1, L2, L3 (phases) = BROWN, BLACK and GREY,
N (neutral) = BLUE, PE = YELLOW/GREEN
Schleifenbauer User Manual - v1
SERVICE AND SUPPORT
In case you have any questions regarding our products, please contact us from the following addresses:
T: +31 73 5230256
F: +31 73 5212383
E-mail:support@schleifenbauer.eu
Website:http://schleifenbauer.eu/en
When a support request delivered to our support line, a case is created automatically with a unique case number.
This number is directly given to our customer. The request will be investigated in detail and proper actions will be
taken. Customer will be informed during this process. The progress can be followed with the given case number.
© Schleifenbauer is a registered trademark.
This publication is protected by copyright.
No part of it may be reproduced or transmitted in any form,
without prior consent in writing from Schleifenbauer Products BV.
37
Schleifenbauer User Manual - v1
APPENDICES
1. SCHLEIFENBAUER PDU MODBUS SPECIFICATION
1. 1 Introduction
This document describes the Modbus/TCP service implemented in Schleifenbauer Intelligent PDUs. The information
provided is applicable to firmware versions 2.14 and upwards.
This document does not describe the actual Modbus registers available on the device, rather how the Schleifenbauer
Products Data Model (SPDM) document is mapped to Modbus. Please refer to up-to-date SPDM document to see all
the available registers on the device, which are also accessible over Modbus by use of the information provided in
this document.
1.2. Configuration
Modbus/TCP related options can be configured from the Interfaces section of the PDU’s web interface. The following
settings affect how the Modbus/TCP operates:
Group
Name
Modbus
modbus TCP
Modbus
modbus TCP
behavior
Modbus
38
modbus TCP
port
Network
Configuration
PDU mode
Access Control
allowed IP
range
Description
Enables or disables the Modbus/TCP service. The PDU mode setting must be
Hybrid or Bridge.
Read-only or Read-write* access.
* Note that the Modbus protocol has no authentication or security built-in. It
is not recommended to enable the Read-Write access except for the trusted
networks.
TCP port. Defaults to 502.
If set to Data Bus, the Modbus/TCP cannot be enabled.
If set to Hybrid, the Modbus/TCP will only work for the local unit.
If set to Bridge, the Modbus/TCP will work for local unit as well as the remote
units on the data bus.
IP access restrictions common to all of the PDU services.
Schleifenbauer User Manual - v1
1.3. Connection
Default Modbus port is 502 as per Modbus/TCP specification.
The Schleifenbauer PDU supports multiple consecutive Modbus request/responses on the same TCP connection. But
it will keep only a single TCP connection active at a time. If a new connection comes in while the previous one is IDLE,
the previous connection will be dropped to favor the new connection.
1.4. Addressing Devices
To address any device on the data bus other than the unit itself, the PDU mode must be set to the Bridge or Twin
Master Mode.
The Schleifenbauer PDU data bus unit addresses are used as the Modbus addresses. The Modbus/TCP specification
limits addressable devices to be in the range from 0 to 247. Thus, only devices configured to have addresses from 1 to
247 would be accessible by Modbus.
To address the device itself, device’s own address as well as address 0 (or less preferably 255) can be used.
1.5. Schleifenbauer Products Data Model (SPDM)
The Modbus implementation exposes all the registers available on the Schleifenbauer Products Data Model. The
document describing the SPDM can be found in the downloads section of the Schleifenbauer web site;
http://documentation.schleifenbauer.eu/Modbus.
The SPDM divides the registers into groups. An example group “identification” is displayed below. Please see the
original document for the full list of available registers.
group
register
mnemonic
name
datatype
bytes repeats
size
access
identification
100
idspdm
SPDMVersion
int
2
1
2
ro
identification
102
idfwvs
firmwareVersion
int
2
1
2
ro
identification
104
idonbr
salesOrderNumber
ascii
16
1
16
rw
identification
120
idpart
productId
ascii
16
1
16
rw
identification
136
idsnbr
serialNumber
ascii
16
1
16
rw
identification
152
idchip
hardwareAddress
int
2
3
2
ro
identification
158
idaddr
unitAddress
int
2
1
2
rw
The SPDM exposes device’s internal information as a memory mapping. Each register in the SPDM has a starting
address, mentioned in the ‘register’ column. For example, the firmware version of a device starts at address 102,
and the unique hardware address starts at address 152.
39
Schleifenbauer User Manual - v1
A register can have multiple channels. An example is measurements of the multiple input phases. ‘repeats’ column
shows how many channels a register has.
Each channel of a register is ‘bytes’ register numbers long. For example, ‘hardwareAddress’ register starts at the
address 152 (‘register’), it has 3 channels (‘repeats’) and each channel is 2 bytes long (‘bytes’); which means its
individual channels start at the addresses 152, 154 and 156.
‘Datatype’ shows the type of the value stored in a single channel. It should be used together with the ‘bytes’ column.
For the purposes of Modbus, details of the individual SPDM data types are irrelevant. For Modbus, a mapping from
the SPDM to the Modbus data types is performed, which is explained in the next section.
Each register also has access permissions, where ‘ro’ denotes read-only, ‘wo’ denotes write-only and ‘rw’ denotes
read-write.
1.5.1. Extension layer
Some rows in the SPDM have an extension layer. This is shown in the ‘ext’ column of the SPDM table. An example is
the outlet rows, some of which are depicted below.
group
register ext
mnemonic
name
datatype bytes repeats
size
access
output_measures
4000
•
omkwht
kWhTotal
int
3
27
81
ro
output_measures
4081
•
omkwhs
kWhSubtotal
int
3
27
81
ro
output_measures
4162
•
ompfac
powerFactor
fd
2
27
54
ro
When a row has an extension layer, this means that specified row actually has twice the number of channels, which
needs to be addressed separately. For example, the kWhTotal row spans between 4000-4081, each channel is 3 bytes
long, having 27 channels addressable in this range (first channel is at 4000, 27th channel is at 4078). This row also has
an extension layer, which has the same address range (4000-4081), but this extension layer holds the channels from
28 to 54 (in case the device has more than 27 metered outlets). 28th channel is at address 4000 in the extension layer,
54th channel is at address 4078 in the extension layer.
Accessing data in the extension layer will be discussed separately in the following sections.
1.6. Modbus Data Types
This section explains the conversion between the SPDM document data types and the Modbus data types.
For Modbus, the minimum accessible data unit is a single SPDM channel. Smaller units than a single channel cannot
be read or written. Multiple SPDM channels, even multiple SPDM rows can be read or written.
40
Schleifenbauer User Manual - v1
Each data type in the SPDM is mapped to Modbus as in the following table.
SPDM Type
Modbus Type
Details
int, 1
1 register, integer
int, 2
1 register, integer
int, 3
2 consecutive registers, 32 bit integer*
Both registers must be accessed together.
int, 4
2 consecutive registers, 32 bit integer*
Both registers must be accessed together.
fd, 2
2 consecutive registers, 32 bit float*
Both registers must be accessed together.
(size/2) registers, string*
All registers must be accessed together.
ascii, even sized
* According to the Modbus specification, Modbus only supports 16-bit integer registers and some conventions are
used to represent larger data. 32-bit integers are transferred as 2 registers with least significant word first. 32-bit
floats are transferred as 2 registers in the IEEE floating point format. Strings are transferred as 2 bytes within each
Modbus register.
1.7. Modbus Register Mapping
Each SPDM register is mapped to the same address on Modbus. For example, ‘firmwareVersion’ register that
starts at address 102 in the SPDM can be read by reading the Modbus register at 102. Because the type of the
‘firmwareVersion’ is “int,2”, it maps to a single Modbus register. A single register must be read from the address 102.
The following diagram depicts the layout of the Modbus registers for the identification SPDM group, whose table
is provided above. According to the Modbus Data Types table, channels starting at 100, 102, 152, 154, 156 and 158
are 1 Modbus register long (they are all type “int,2”). Channels starting at 104, 120, 136 are 8 Modbus registers long
(they are all type “ascii,16”).
41
Schleifenbauer User Manual - v1
Blue boxes show the starting Modbus addresses of the individual channels (of the SPDM). Red boxes are not directly
accessible. Please keep in mind that not-mentioned numbers (such as 101 or 103) do not exist. These will be clarified
in the following subsections.
1.7.1. Accessing single channels
In the PDU, each channel of a SPDM register is mapped to Modbus by its starting address. For example, in the SPDM,
3 channels of hardwareAddress start at positions 152, 154 and 156. They are all single Modbus registers due to their
SPDM type “int,2”. To read only the second channel of ‘hardwareAddress’ using Modbus, a single register at address
154 must be read.
In the diagram depicted above, any of the blue boxes can be read by their starting address.
Note that each SPDM channel must be read as a whole. Partial reads are not possible.
For example registers 104, 120 and 136 (i.e salesOrderNumber, productId, serialNumber; which are all “ascii, 16”
SPDM types) are 8 Modbus registers long (due to their SPDM types). Thus they must be read with a single Read
command of 8 Modbus registers starting at 104 (or at 120, or at 136).
1.7.2. Accessing multiple channels of the same row
In the PDU, the Modbus registers do not have gaps between them, even though their starting addresses might say
otherwise. Starting from a valid starting address, and reading multiple registers will result in all following channels
in the SPDM to be read.
For example; Even if individual channels of ‘hardwareAddress’ row can be read as single Modbus registers at 152,
154 and 156 ; there are no gaps at Modbus positions 153, 155, or 157 -- all 3 channels of hardwareAddress are the
adjacent Modbus registers (see diagram). A 3 register read starting from address 152 will return 3 Modbus registers
representing channel 1, channel 2 and channel 3 of hardwareAddress.
 Note that this behavior is different than the Schleifenbauer Gateway’s Modbus/TCP implementation.
1.7.3. Accessing multiple rows
Multiple rows can be accessed in the same way as accessing multiple channels. All rows are adjacent to each other,
as well as their channels.
For example, according to the SPDM document, ‘SPDMVersion’ row starts at 100, ‘firmwareVersion’ row starts at 102,
and they are consecutive. According to the Modbus Data Types table, both of them are single Modbus registers. Thus,
to read these two rows together, a read of 2 Modbus registers starting at address 100 is sufficient.
Consistent with the previous subsections, in the diagram above, it can be seen that there is no Modbus register 101;
and 100 and 102 are consecutive, single Modbus registers.
Additionally, it is possible to start reading at any channel of a row, and continue reading on the next row. Depicted as
a green arrow on the diagram, a single Read of 3 registers starting at address 154 (2nd channel of hardwareAddress)
will return Modbus registers at 154, 156 and 158 (2nd and 3rd channels of ‘hardwareAddress’, and ‘unitAddress’
respectively).
1.7.4. Accessing extension layers
For rows that have an extension layer in the SPDM, there are 3 different ways to access data in the extension layers.
Any of these methods may be used interchangeably depending on the client application’s requirements.
42
Schleifenbauer User Manual - v1
1.7.4.1. As a continuation of base layer
Logically, channels in the extension layer lie after the channels in the base layer. Although they cannot be addressed
independently, a multichannel read command starting from the base layer can continue on to the channels in the
extension layer, as they are consecutive.
The diagram above depicts the Modbus registers of the SPDM rows kWhTotal (4000), kWhSubtotal (4081), and
powerFactor (4162). Channels of these rows are of type “int,3” or “fd,2” which makes them into 2 Modbus registers
each. Channels 28 to 54 lie on the extension layer, thus not accessible by starting addresses. Still, a single Modbus
read of 106 registers (53 channels) starting at register 4164 (2nd channel of powerFactor)) will return both the base
layer and the extension layer channels.
 Note that this method cannot be used on the Schleifenbauer Gateway’s Modbus implementation.
1.7.4.2. Directly addressed with an offset of 10000
If the application requires direct accessing of individual channels in the extension layer, an offset of 10000 can be
added to the base layer’s channels. For example, if channel 1 of kWhTotal lies at 4000, and channel 2 lies at 4002 ;
reading 2 Modbus registers at address 14000 will return channel 28, and reading at address 14002 will return channel
29.
* This method is compatible with the Schleifenbauer Gateway’s Modbus implementation.
1.7.4.3. Directly addressed with Read Input Registers (04) function code
In normal cases, Read Holding Registers (03) Modbus function is used to read the data from the device. If Read Input
Registers (04) is used instead, the PDU will return the data in the extension layers wherever possible.
For example, if 2 registers at address 4000 are read using Modbus function 03 ; channel 1 of kWhTotal (base layer) will
be returned. If the same range (4000,2) is read using Modbus function 04 ; channel 28 of kWhTotal (extension layer)
will be returned.
For the non-extension rows, both read function codes (03 and 04) behave the same.
 Note that this method cannot be used for writing.
* This method is compatible with the Schleifenbauer Gateway’s Modbus implementation.
1.8. Supported Function Codes
The Schleifenbauer PDU supports the following Modbus function codes. For their details, please consult the Modbus
protocol documentation.
1.8.1. Read Holding Registers (03)
Will read registers. Only entire channels can be read. Partial reads are not possible. For the register addressing and
the size of registers, please refer to the previous sections.
43
Schleifenbauer User Manual - v1
1.8.2. Read Input Registers (04)
For the non-extension SPDM registers, this will act exactly the same as the function Read Holding Registers (03). For
the SPDM registers with extensions, the extension layer’s data will be returned to the base layer’s address ranges.
1.8.3. Write Single Register (06)
This function is used to write a single-length Modbus register. Addressing is same as the Read Holding Registers (03).
 Note that, partial access to the SPDM channels is not possible, and this function can only specify a single
Modbus register -- thus cannot be used for the types larger than 1 Modbus register (for example, “fd,2” types
which map to 2 Modbus registers).
1.8.4. Write Multiple Registers (16, 0x10)
This function may be used to write multiple Modbus registers at once. Addressing is same as Read Holding Registers
(03).
This function is the only way to write to larger-than-1-register types (such as “fd,2” types which maps to 2 Modbus
registers, or strings) ; as well as to write simultaneously to multiple channels at once.
1.9. Examples
SPDM
mnemonic
Func
Code
Start
Length
in regs
Result
Read FW version
idfwvs
03
102
1
1 register
Read Input 1 Voltage
imvoac
03
3036
2
2 registers representing voltage as 32-bit
float
Read Input 1-3 RMS
Current
imcrac
03
3024
6
6 registers, representing 3x 32-bit floats in
pairs
Read Outlet 2’s voltage
omvoac
03
4326
2
2 registers, representing 1x 32-bit float
Read Outlet 29’s voltage
omvoac
04
4326
2
2 registers, representing 1x 32-bit float
Read Outlet 29’s voltage
omvoac
03
14326
2
2 registers, representing 1x 32-bit float
44
Schleifenbauer User Manual - v1
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising