Datasheets & Brochures
Compliances
PDU User Manual
Software
SPST software for Windows
SPST software for MAC
SPST software for Linux
Interfaces
Discover our dedicated download section for interface support of our PDUs, tailored to provide you with downloads and comprehensive documentation on key PDU interfaces such as SNMP, MODBUS, WEBAPI, and IPAPI. In addition to essential examples, protocol descriptions, and MIB files, we offer the SPDM register model. This document enables easy reading of PDU register values via our available interfaces.
Click here => Interfaces
Firmware
Our firmware download section is designed to provide the latest support for features and performance enhancements on our PDUs. Here you will find not only downloads for specific firmware versions that can be installed on the PDUs using the SPST software, but also the release notes and our PDU manual. Take advantage of the latest updates and features for improved performance of your PDUs.
Click here => Firmware
SPST
Download our PDU service tool for Windows, Linux, or Mac. With SPST (Schleifenbauer Products Service Tool), you can easily analyze and manage your network of Schleifenbauer PDUs. SPST provides the ability to update PDU firmware, perform mass configuration, import/export data, and provide an overview of all your devices on the data bus. Additionally, the release notes and SPST manual are available in our download section.
Click here => SPST (Schleifenbauer Products Service Tool)
Legacy
For support related to Classic PDUs (firmware 1.xx) and Gateways, we have a separate download section. Here you can download firmware files and tools for this generation, as well as manuals and interface documentation for our first-generation products.
Click here => Legacy
Frequently Asked Questions
Schleifenbauer is a European manufacturer of rack PDUs and intelligent energy meters for data centers, headquartered in ‘s-Hertogenbosch, the Netherlands.
Schleifenbauer’s headquarters and production facility are situated in ‘s-Hertogenbosch, Netherlands. From here, we are centrally located in the FLAP region (Frankfurt, London, Amsterdam, Paris).
Schleifenbauer is gespecialiseerd in rack en distributiepaneel Schleifenbauer specializes in rack and distribution panel power management solutions for data center and infrastructure applications. We assist facility and IT managers in constructing their premium, highly available, sustainable, and user-friendly energy distribution system by delivering uncompromising, tailor-made products and services.
Our products are ‘Made in Holland’. To ensure our quality, we oversee the production process in-house and in collaboration with our reputable and reliable local partners.
Schleifenbauer PDUs and energy meters are tailored to fit the infrastructure of your data center, rather than the other way around. You can liken our configuration and production process to that of Lego™: With only a limited number of building blocks, an infinite number of end products can be created.
Schleifenbauer primarily operates in the data center industry (commercial and residential) and various other sectors such as industrial production and yacht building. We primarily serve European clients, but we also supply to companies abroad.
The Schleifenbauer Intelligent Power Distribution Unit (PDU) is designed to distribute power seamlessly for years to come.
The PDU features a specially developed Schleifenbauer databus that enables the retrieval and management of multiple PDUs with a single IP address. Additionally, an Ethernet port is incorporated into each PDU, providing a wide range of new capabilities alongside the benefits of a databus. Schleifenbauer PDUs bridge the interests between IT and infrastructure, thus serving as genuine facilitators of collaboration.
Schleifenbauer is ISO 9001:2015 certified according to the international standard for quality management.
The Schleifenbauer Intelligent Power Distribution Unit (PDU) is designed to distribute power seamlessly for years to come.
Equipped with a specially developed Schleifenbauer databus, the PDU enables the retrieval and management of multiple PDUs with a single IP address. Additionally, an Ethernet port is incorporated into each PDU, providing a wide range of new capabilities alongside the benefits of a databus. Schleifenbauer PDUs bridge the interests between IT and infrastructure, thus serving as genuine facilitators of collaboration. The monitoring capabilities will be detailed in the following chapters of this manual.
The PDU can include:
– Measured outlets
– Switched outlets
– Measured and switched outlets
– Passive outputs
Customers can configure the number and types of outlets for their PDU according to their preferences by utilizing Schleifenbauer’s customization tool (Example PDU) when placing an order.
We provide 5 types of PDUs, each with different functionalities:
1. Basic PDU
This PDU offers ‘standard’ power distribution without metering and management options.
2. Metered PDU
This PDU offers ‘cumulative’ (input) metering.
3. Measured PDU
This PDU provides metering options per outlet.
4. Switched PDU
This PDU offers switching options per outlet.
5. Managed PDU
This PDU provides both metered and switched outlets.
Operation:
Temperature 0° to 60° Celsius
Altitude -30 to +2000 m
Relative humidity 10 to 90% non-condensing
Pollution degree 2
Environment Indoor IP20
Equipment class Class I
Protection class II
Operating conditions Continuous
Voltage: Single-phase 100-230 VAC; three-phase 230/400 VAC
Frequency: 50/60 Hz
Permissible load: Refer to product information on your PDU
Accuracy: EN 50470-1/3 class B, EN 62053-21: class 1, ± 1%.
Wire color code:
– L1 = BROWN
– L2 = BLACK
– L3 = GREY
– N (neutral) = BLUE
– PE = YELLOW/GREEN
Several interfaces are integrated into the PDU:
– (Embedded) web interface
– Modbus/TCP
– SNMP (Simple Network Management Protocol)
– (SP)API (Schleifenbauer Products Application Programming Interface).
In our manual (admin section), you will find information about the ‘Interfaces’ detailing the technology for communicating with the Schleifenbauer databus via your LAN (Local Area Network).
The PDU can measure several quantities, either at the input, output, or with an optional sensor.
The measured quantities are listed below:
We provide various types of connectors tailored to your situation:
– CEE 7/7 (Schuko/UTE)
– IEC320 C14
– IEC320 C20
– IEC60309 1 phase
– IEC60309 3 phase
– BS 1363
– GST 3/18
– T13
– T23
– Cable connection
– Terminal connection
For more information, please click here.
Certainly! You can select the cable entry location yourself:
– Top
– Bottom
– Front
– Rear
For more information, please click here.
Certainly! We can manufacture your PDU with an adjustable cable length according to your preferences.
Cable specifications:
– Adjustable cable length
– Low Smoke Zero Halogen (LSZH)
– Oversized diameter
For more information, please click here.
Certainly! We offer the housing of our PDUs in various colours.
Possible options:
– Black
– Green
– Orange
– Blue
– Red
– Yellow
For more information and our colour scheme, please click here.
In conjunction with a Schleifenbauer PDU, there is an unlimited choice of fuses available, including:
– Miniature Circuit Breaker (MCB)
– Thermal fuse
– Glass fuse holder
– PASCO cartridge holder
Moreover, surge protection is also possible, featuring the following characteristics:
– Protects PDU against voltage spikes
– Hot swap
– Can be replaced by a data center technician
Your PDU can be equipped with various types of outlets. Both the number and type of outlets can be customized according to your requirements.
Different types of outlets include:
– IEC320 C13 (also version with IEC-lock)
– IEC320 C19 (also version with IEC-lock)
– CEE 7/3 (Schuko)
– CEE 7/5 (UTE)
– IEC60309 1 phase (IP44/IP67)
– IEC60309 3 phase (IP44/IP67)
– BS 1363
– GST 18/3
– T13
– T23
For more information about PDU outlets, please click here.
We provide various types of mounting brackets:
– 19″ rack mounting brackets
– Table mounting brackets
– Mounting plates for flush mounting
– Profile clamps
– Tool-less mounting brackets
Yes, that is possible. We often laser customer logos onto the aluminium casing of rack PDUs.
With our Schleifenbauer Example PDU, you can easily choose and (if necessary) configure your PDU or energy meter.
Click here for our Example PDU.
You can request a quotation through our Schleifenbauer Example PDU, and we will send it to you within 1 business day.
If you have any questions or encounter issues while selecting or configuring your Schleifenbauer product, you can call us. Our Inside Sales team will assist you with your request.
You can reach us at: +31 (0)73 523 02 56 or send us an email at: info@schleifenbauer.eu
That is not necessary. If one of the suggested products in our Schleifenbauer Example PDU fits your needs, you can directly submit your quotation request.
Only if you want to modify one or more elements on the suggested product (PDU), you can choose configuration and customize it according to your preferences.
Certainly! If you have a project to discuss, you can schedule an appointment.
You can send your appointment request to info@schleifenbauer.eu, and your account manager will then contact you to arrange a date and time.
For more contact information, please click here.
Yes, we collaborate with various resellers across different European countries. For further information and details regarding this, please feel free to get in touch with us!
The Schleifenbauer Intelligent PDUs are shipped in a cardboard box. Please dispose of the packaging material responsibly, in accordance with local regulations. All materials used for packaging are recyclable. Immediately upon receipt, verify that you have received your order complete and undamaged.
Each PDU is supplied with the following:
– Mounting hardware: These can be attached to the PDU (19” or table mounting brackets), or supplied separately if ordered separately;
– Installation manual (one per shipment);
The PDU user manual can also be found online: Click here
After opening the cardboard box and removing the packaging material, the PDU should be visually inspected.
The PDU should not be put into operation if any damage is observed that could compromise safe and proper operation. In such cases, please contact Schleifenbauer Products BV.
Note that in the case of PDUs equipped with surge protection, the surge protection and associated overcurrent protection (if applicable) should be inspected regularly.
– After installation: standard passwords / RC4 keys MUST be changed (see manual, part III (administrator’s manual)
– The PDU must be installed in a restricted access location
– The socket must be installed near the equipment.
– Socket must be easily accessible
– Installation by qualified personnel only (adequately trained individuals according to NEN EN 50110-1, fully complying with the specifications of NEN EN 50110-1 and NEN 3140)
Before installing and commissioning the system, you should verify that the characteristics of the electrical system to which it will be connected match the product specifications.
– The Schleifenbauer Intelligent PDU is designed for connection to electrical systems that comply with IEC 60364 or, in the Netherlands, NEN 1010.
– The voltage, maximum allowable current, and number of phases must be correct. This information is stated on the front of the PDU.
– When considering the maximum allowable power, the maximum length and diameter of the connecting cable must be taken into account. The values and characteristics of the series protections must match those of the PDU and the protection elements contained therein.
– The environmental factors must match the product specifications.
The following tools are required to install the PDUs:
– Cage nuts with bolts and washers
– Suitable screwdriver
Each 19″ rack bracket of a PDU has 4 holes for horizontal mounting in 19″ racks. The holes are positioned in such a way that there is always a suitable mounting hole available for a PDU with a profile height of 1.5U. Mounting is possible using one or two of the 4 holes without wasting space.
For a PDU intended for vertical mounting, the power cord is passed through a hole in the top, bottom, or front.
Toolless mounting is achieved by creating attachment points on the rear of the PDU housing. A wide range of cabinet brackets is available, allowing you to hang the PDU without the need for tools.
Toolless Mounting can be for single or double PDUs (see illustration).
Mounting brackets can be custom-made by Schleifenbauer.
Tabletop mounting provides the profile with the ability to be mounted on a flat surface (tabletop). This setup is used for:
– Vertical mounting to the reinforcement bars in the 19″ cabinet
– Attachment to a mounting plate
– Mounting between the 19″ uprights: the profile is attached to the front of the uprights
The holes on the brackets are positioned as far outwards as possible, allowing the bolts to be applied and tightened even when a gland is positioned on the short side.
When power cables can block the flow of hot exhaust air, especially in the case of a 600 mm wide cabinet, it is necessary to create additional space for airflow. This can be achieved using the ‘flush installation brackets’. The shape of the bracket allows the profile to be partially ‘flush’ mounted in the cabinet, saving space.
These mounting plates can be used for many different cabinets.
The clamps, made of spring steel, can be installed in the position of your choice. The clamp fits around the PDU profile and is secured with a fastening screw. Our recommendation is to use one clamp per 50 cm of profile length.
10/100 Mbps LAN Ethernet Port
Connecting the PDU to a Local Area Network (LAN) enables communication via an Ethernet network. Multiple PDUs can share the same Ethernet connection by utilizing the data bus (Bridge or Hybrid mode). The RJ45 connector for the network cable should be connected to the silver Ethernet port:
Connect the RJ45 Ethernet cable to the Ethernet port of the PDU and to the Ethernet port of the LAN device; once connected, the orange LED – marked ‘lnk’ – will start blinking.
The intelligence of Schleifenbauer PDUs allows for remote device monitoring and management via IP. For instance, it is possible to access the data bus through the web interface, MODBUS, and SNMP.
The data bus offers a wide range of options: it provides ample support for custom configurations desired by the user.
Data bus and power distribution are separated in the Schleifenbauer PDU. All actions on the data bus DO NOT interfere with the power distribution to the connected equipment in the racks.
Advantages of the data bus:
– Easy to set up: Select a PDU and connect it to a local network, daisy chain the rest of the PDUs, and a data bus is created.
– Remote firmware updates.
Explanation of the image:
– The PDU connected to the LAN must be in ‘BRIDGE’ mode (red); this is the MASTER device.
– All ‘daisy-chained’ devices must be in ‘HYBRID’ mode (blue); these are the BRIDGED devices.
There are three black communication ports. One is marked as the sensor port, and the other two as data bus ports (in and out). The left data bus port is the ‘incoming’ data bus port. The right data bus port is ‘outgoing’. This is a MUST HAVE for devices in bridge mode. For devices in hybrid mode, it is a NICE TO HAVE. The serial data bus in the Schleifenbauer PDU uses CAT5 patch cables.
- Data will be transmitted and received through both ports, but to close the data bus ring, it is recommended to follow the connection scheme to ensure maximum performance.
In the above image, a small data bus ring is depicted with four PDUs connected to the Schleifenbauer Gateway.
The Classic PDU does NOT have an Ethernet port, so a (Schleifenbauer) Gateway is required to connect the PDUs to your LAN. The order of devices does not affect the performance of the Gateway or the data bus. More devices in the data bus mean more communication. However, this results in slightly slower data transfer.
Our advice is to always close the data bus ring. To do this, connect the last device in the data bus to the Gateway (blue lines in the image). In a closed data bus ring, the Gateway can reach all connected devices via the IN and OUT data bus ports (clockwise and counterclockwise).
Advantage: One IP address allows for collecting data from a number of connected Schleifenbauer devices (not only PDUs but also the Schleifenbauer DPM series (=energy meters).
Disadvantage: Gateway uses 1U of rack space.
Troubleshooting: If the Gateway fails, it is possible to switch to the following configuration: using the ‘bridge’ mode.
Note: Data bus communication takes 0.2 seconds per query (e.g., block with input measures). Therefore, we recommend creating rings with a maximum of 50 devices, meaning that querying each device once takes approximately ten seconds.
The image above depicts a small data bus ring with just four devices connected to a LAN: a Classic PDU and a PDU with an Ethernet port. The device connected to the LAN must have an Ethernet port and be in ‘BRIDGE’ mode. All other devices must be in ‘Hybrid’ mode. The BRIDGED device takes over the function of the Schleifenbauer Gateway.
It is possible to connect multiple Schleifenbauer devices to the device in BRIDGE mode: Both PDUs and DPM3’s (= three-channel energy meter) as well as Classic PDUs and DPM27 (= 27-channel energy meter).
The order of the devices does not affect the performance of the data bus ring. However, the more devices you place in the data bus ring, the slower the data transfer will be. The image shows that various Schleifenbauer devices can be connected in a ring, making the system easily scalable to the customer’s needs. It is advisable to close the data bus ring. Connect the last device in the data bus to the device in BRIDGE mode.
In a closed data bus ring, all connected devices are accessible via IN and OUT data bus ports (clockwise and counterclockwise).
Advantages:
– When only devices with Ethernet ports are used: only the device in BRIDGE mode uses one IP address.
– It is possible to select any device connected to the local network as long as it is in BRIDGE mode.
– Investing in a Schleifenbauer Gateway is not necessary.
– The system is easily scalable.
Disadvantage: MySQL and SMTP cannot be used.
Note: Data bus communication takes 0.2 seconds per query (e.g., input measures block). Therefore, we recommend creating rings with a maximum of 50 devices, meaning that querying each device once takes approximately ten seconds.
The PDU features an RJ12 connector sensor port to which one of the following sensors can be connected:
– a digital temperature sensor
– a combined temperature/humidity sensor
– one or more dry contact closures
Plug and play
Sensors are automatically recognized by the PDU and will update the display and menu accordingly.
Warning: Only use Schleifenbauer sensors.
The sensor port utilizes the RJ12 6P6C standard (= 6 positions, 6 conductors). To connect an NO/NC contact to the PDU sensor port, you should use pin 1 and pin 6; as shown in the diagram below.
Third-generation PDUs and DPMs are equipped with a USB port and can operate two NO/NC dry contact closures.
The current PHP API utilizes a single class for communication with SPBUS devices. It solely implements the IPAPI protocol. Further details regarding the utilized protocol can be found in the document titled “SPBUS Protocol v2.” To gain additional insight into the PHP API, please download the API from the Schleifenbauer website and examine its functionalities through provided examples and source code.
The Perl API utilizes a single package to communicate with SPBUS devices. It implements both the SPBUS and IPAPI protocols. Further information regarding the utilized protocols can be found in the document titled “SPBUS Protocol v2.” To gain additional insight into the Perl API, please download the API from the Schleifenbauer website and study its functionalities through provided examples and source code.
SNMP can be utilized to communicate with registers of an SPBUS device. At the time of writing this document, SNMP v1, v2, and v2c are supported. SNMP traps are also supported, for which a trap destination server can be configured on a device.
The current SNMP traps for SPBUS devices include:
– Network connection
– Failed SNMP authentication
– Device status code
– Temperature alarm
– Input current alarm
– Output current alarm
– Input voltage alarm
– Output current drop alarm
– Input current drop alarm
– Sensor change alarm
– Ring status change
All these SNMP traps can be enabled or disabled.
For information regarding SNMP OID (Object Identifier), MIB files (Management Information Base) can be found on the Schleifenbauer website. Further details on SNMP can be found in the SNMP RFCs.
The WebAPI functions as a RESTful API. It is possible to retrieve information from an SPBUS device using resource requests. The WebAPI is not dependent on a specific implementation and is therefore explained using messages sent to the SPBUS device via the TCP/IP connection. Please note that certain details (especially regarding the authentication token) have been omitted from this document.
Further information about the WebAPI can be found in the WebAPI documentation: Click here
Modbus is a communication protocol that enables various commands (functions), including reading/writing registers on a device in the Modbus network. Modbus is thus useful for communicating with SPBUS devices, as they utilize registers to communicate with their hardware. Further information regarding data communication of SPBUS devices via Modbus can be found in the document “Schleifenbauer hPDU Modbus Specification.”
A user can either implement their own API or directly integrate the communication of the SPBUS protocol into their custom software. For these individuals, a description of the SPBUS protocol is available. This document provides a detailed description of the SPBUS protocol. Please note that the SPBUS protocol can be utilized via RS485 or IPAPI, with IPAPI involving additional steps for packet construction.
SPBUS Protocol: Click here
The intelligent PDU features a display with scroll buttons, LEDs, and some ports for connecting accessories. Please note that PDUs may vary in configuration and whether or not they have a display.
- PDUs without an Ethernet port are referred to as Classic PDUs. The firmware for Classic PDUs lies within the FW1xxx series.
- This option is called “Local alert reset” and must be activated via the interfaces.
- USB port available only on g3 (generation 3); used for firmware upgrades and downgrades (from FW2.52 and newer).
Changing settings locally via the PDU itself is not possible! You must use one of the interfaces for this purpose.
Note: Refer to the ‘administrator section’ in our manual on how to change settings.
Since Firmware 2.50, alerts are displayed both on the display and on the web interface. For example:
The displayed text directly indicates which alert has occurred.
Why are alerts generated?
Alerts are signal flags after an event has occurred. For example, if the measured temperature and environmental conditions exceed a configured level or threshold, the PDU generates an alert. This manifests in:
– SNMP trap (optional).
– The PDU display starts flashing.
– The PDU display jumps to the Alert page, providing information about what happened.
After the temperature has dropped again, the event is cleared, but the alert remains. The display continues flashing until you “reset” the alert.
The LCD display only flashes when an alert is active.
Actions:
– Press any key to temporarily stop the flashing for a short period: the flashing stops so you can read the display.
– Resetting the alert can be done by simultaneously pressing both scroll buttons; when the alert is cleared, the screen stops flashing (Note: this capability must be activated on your device; see Admin section of this manual).
Note: You can reset the alert, but this does not resolve the cause of the alert! If the alert condition is still present, the alert will reappear.
The image displays three phases (L1, 2, and 3). Actual information is presented in amperes but is also graphically represented. The higher the load, the more the bar is filled. The graphical bar is related to the maximum PDU power (in the image, it is 32A). In this illustration, there is almost no load, only a small 0.1A on L3.
DS = status of NO/NC contact (O = open; C = closed)
Te = temperature (degrees Celsius)*
RH = relative humidity (%)*
*only visible if the corresponding sensor is connected.
If there are alerts, first clear these by pressing both scroll buttons (see: “How do I stop a flashing display via a local alert reset?”)
If the alerts are resolved or there are no alerts (no flashing display), press both scroll buttons (see arrows in image) to quickly jump to the first page.
In the “outlets” display, you can see how many outlets the PDU has and what their individual status is.
An overview of the possible states:
- 0= off
- 1= on
- s= scheduled to turn off
- S= scheduled to turn on
- p= power outage
Note: each row on the display shows the status of 9 outlets. So the first row ends with outlet 9, the second row starts with outlet 10.
With the scroll buttons, the user can navigate through the pages.
The total number of pages varies and depends on the configuration of the PDU. For example: The more outlets, the higher the total number of pages. In the example “input page,” page 4 of 29 is displayed.
In the bottom left corner of the “input page” example, the subject of the displayed information on this page is visible as “INPUT L2,” which is an abbreviation for input measurements of L2. So, when searching for outlets, you scroll through the pages until you reach the sections “outlets.” An example is shown in the “outlet page” image.
Displayed information may include:
- I= current [A]
- P= power [W]
- U= voltage [V]
- Pf= power factor [%]*
- Et= total energy [kW]
- Es= subtotal energy [kW]
(*Pf = real power ÷ apparent power)

Example: input page
Note: “Input x” shows the name of the input. This information can be configured from the web interface, Inputs tab, or from the other interfaces.

Example: outlet page
Option 1: Load Page
Sensors are displayed on the “Load” screen when fewer than three sensors are in use. When more sensors are added, one or more pages are added to the screen to display sensor readings (see image):
DS = status of NO/NC contact (O = open; C = closed)
Te = temperature (degrees C)
RH = relative humidity (%)
Option 2: Sensor Pages
The sensor measurements are displayed in the following format:
<channel number> <sensor type> = <value>
The sensor type is indicated by a letter. The letters are abbreviations for the sensor type as follows:
Analog:
- T = temperature [°C]
- H = humidity [%]
- R = residual current [mA]
- A = AC residual current [mA]
- D = DC residual current [mA]
- B = Phase residual current [mA]
Digital:
- I = dry contact
- S = fault status
- Y = activity
Example: Sensor page 1 of 2

Example: Sensor page 2 of 2
L1 + L2 + L3 + N > 0 mA …. THERE MAY BE A FAULT IN YOUR SYSTEM!
When the PDU is equipped with a residual current sensor (RCS), the residual current measurements are displayed on the sensor pages.
In parts of Europe, electrical installations must be equipped with devices to protect people and prevent fires: the residual-current device, or RCD. An RCD switches off the circuit if the total of the incoming and outgoing currents in the monitored phases and their neutral exceeds a threshold, for example: L1 + L2 + L3 + N > 30 mA.
Practice in data centres: Residual Current Monitoring Related to Residual Current Devices
Many devices in a data centre operate with a switching power supply. These power supplies usually leak some energy to the ground, so even without failing hardware, there will be some residual current. To exclude a single dangerous fault from a sum of harmless smaller faults, a network of RC sensors must be established and continuously monitored. RC monitoring can take many forms. The Schleifenbauer RC sensor offers class B measurement, allowing our customers to establish an RC monitoring system that prevents hazardous situations within the data centre.
Where to Measure Residual Current?
When monitoring residual current at one location, it is not possible to determine whether the measured value is a sum of many small currents or one larger (hazardous) one. Therefore, it contributes to the safety of personnel in a data centre if the residual currents are measured at multiple points.
You will find all customer-specific information about the PDU in the “Custom” display.
- Adr = address of this device on the databus
- Tag = vanity tag
- Nme = device name
- Loc = device location
Note: The device name and tag can be changed using the WEBAPI.
Schleifenbauer PDUs enable remote management, allowing users to toggle selected outlets on or off, monitor usage data, and set/receive alerts based on configured thresholds. Additionally, various connection parameters can be configured through different protocols.
The Schleifenbauer web interface serves as a user-friendly tool for PDU configuration.
By default, the web interface is enabled. To access the web interface, you can find the IP address and port number on the PDU display.
On the login screen, you can also choose English or German as your language.

Connected Devices (Bridge Mode Only)
The left section of the image below displays a list of connected devices on the databus. Also, databus management functions can be found in this section, such as:
– Scan databus
– Initialize zero addresses to sequence
– Reset all alerts
Device Information
Upon selecting a connected device, you will see measurements/information in the right pane and gain access to remote control functions.
The web interface is protected against accidental changes to settings. Depending on your user profile, you may have permission to modify information: see the “Permission Model”. To access secure cells, you must first click on the “Locked” icon, after which the status changes to “Editable”.
When finished, click on “Editable” or on the “Save Changes” icon if displayed, and the icon will change back to “Locked”.
SNMPv3 user settings can be configured in the web interface: navigate to the “Interfaces” tab, and locate the “User Management” section.
To modify the settings for a specific user, click on the “edit” button. Then, tick the box labelled ‘change SNMPv3 settings’ to adjust the SNMPv3 settings. Once done, click the ‘save user’ button.

Note: A Classic PDU without an Ethernet connection running firmware 1.xx does not have a device type register. As a result, some functions do not work via SNMP.
Not Supported with SNMP on a Classic PDU:
– Input subtotal reset per phase
– Restart outlet
– Power (W) and power (VA), invalid value (0.0)
The web interface displays a list of all devices connected to the bridge PDU in the left panel (or under the blue header when using narrower screens), only when the PDU is configured in Bridge mode.
Initially, this list is empty but populates as the web interface loads data from the bridge PDU. A user must click on the configuration icon to the right of the devices list and select “scan databus”. A selected device is highlighted – indicated by a yellow line – in the devices list (left panel). Users can switch between devices by simply clicking on the row in the devices list.
Information and settings about the currently selected device are visible in the right panel of the web interface. Adjacent to the configuration icon is the ring icon. This icon indicates whether your ring is properly closed or open.
The example below shows an open ring. The example at the bottom of this page shows a properly closed ring. It is closed by connecting the “out” of the last device in the ring to the “in” of the first device. A closed ring ensures redundancy of all data between the master “bridge” device and the addressed “hybrid” device.

Note: The devices list appears only if the connected device is in “bridge” mode.
Note: When using multiple devices in a ring, ensure that the device connected to the local network is in bridge mode and all others are in hybrid mode.
When new devices are added to a ring, the firmware may detect various devices with device address 0.
All connected devices require a unique device address to function properly. Duplicate device addresses result in warnings (see image).
It is not possible to set all addresses at once!
In this example (see image), four devices are found. Device [1] is the bridged device, so it is best to set this device address last. Therefore, start with [4], which is the device at the top of the list that was found first.
– Click on < set address >
– A new screen will appear; ensure the correct device is selected
– Enter the new < device address >
– Click < ok >
A “write error” will occur, which is correct: you have just changed the device address, so it can no longer be reached at its old device address. Click on
When you perform a rescan, you will see that all devices are correctly addressed.
The PDU user authentication model provides for five different accounts that can be used to access the web interface and SNMPv3.
In the web interface, the user accounts are in descending order of access rights: super, admin, power, user, and viewer.
It should be noted that super is intended for use by Schleifenbauer personnel only. The access rights of the different user accounts, along with databus and non-authenticated Ethernet, are shown in the table below:

The default password for each profile is initially the same as the profile’s username. For example, the default password for the “admin” user profile is “admin”.
Each user can change all less restrictive user passwords, in addition to their own password. Fill in the ‘Username’ and ‘Password’ fields accordingly and then click on login or press enter.
We advise our customers to change all default passwords during system installation to prevent unauthorized access.
Passwords can be changed in the “Interfaces” tab, “User Management” block.
There are five login profiles:
- Viewer = view only
- User = Viewer + reset warnings and switch outlets
- Power = User + reset subtotals
- Admin = all administrative rights
- Super = factory profile

The “Ethernet link speed and duplex mode” setting is default to auto negotiate. The link speed and duplex mode are automatically configured with the link partner (e.g., Network Switch).
You can also set the connection speed and duplex mode to a fixed setting. You can choose from the following options:
– Autonegotiation
– 10 Mbps Full Duplex
– 10 Mbps Half Duplex
– 100 Mbps Full Duplex
– 100 Mbps Half Duplex

Note: When this setting is changed, the configuration of the link partner must be changed accordingly! Deviations in speed/duplex modes prevent remote users from connecting to the PDU. If this setting is accidentally changed to an invalid value and users cannot connect, change the setting of the link partner to the same setting in the PDU to regain access to the PDU. If this does not solve the issue: try a factory reset.
Users have the capability to modify the hostname of their devices. A hostname typically consists of a Schleifenbauer prefix and the serial number.
There are three options:
– Custom hostname
– Schleifenbauer prefix combined with a sysname
– Back to default value
These options are available in the “Interfaces” section of the web interface.
Custom hostname: Change the value of the hostname, save it, and restart the PDU.
Schleifenbauer prefix and sysname: Add custom name to sysname value, save, and restart.
Back to default value (Schleifenbauer prefix and serial number): Clear sysname value, save, and restart. Or clear the hostname first and then the sysname.
The IP settings can be manually configured via the web interface:

Actions:
– Navigate to the <Interface> tab, <Network Configuration> block
– Disable DHCP
– Fill in the “Static IP Settings”
– Restart the CPU: go to the <System> tab, block “Reset”
When using “DHCP fallback to static IP,” it is recommended to enter a unique IP address for each PDU. This approach prevents all PDUs from being assigned the same IP address in case of a faulty DHCP server. This prevents PDUs from being assigned the same IP address.
Since firmware version FW2.44, IPv6 support has been introduced in the Schleifenbauer PDU. This feature is disabled by default.
An IPv6 address consists of 8 blocks of 4 hexadecimal digits separated by colons ( : ). Consecutive blocks of zeros can be replaced by a double colon ( :: ) and leading zeros can be omitted. The default static IP is “::”, which translates to 0000:0000:0000:0000:0000:0000:0000:0000.
Automatic IPv6 Configuration (SLAAC)
By default, the PDU attempts to obtain its IPv6 address through a process called “stateless local address auto-configuration” (SLAAC). This setting can be disabled in the web interface by setting “IPv6 Autoconfigure” to “disabled.” The PDU will attempt to find a router by sending solicitation packets via ICMPv6 using its link-local address. This requires a router compatible with IPv6 on the network and that it sends ICMPv6 router advertisement packets to enable the PDU to obtain a valid IPv6 address. When “IPv6 fallback to static IP” is enabled in the web interface, the PDU uses its configured static addresses as fallback when no router can be found.
Static IP
To use static IPv6 addresses, the PDU must have the “IPv6 Autoconfigure” setting disabled or “IPv6 fallback to static IP” enabled in the web interface. To change the static IPv6 addresses, enter a valid IPv6 address in the “IPv6 Address 1” and/or “IPv6 Address 2” fields; see the next chapter. These settings can be found under “interfaces → network configuration”.
IPv6 settings can be found in the web interface of the PDUs under the <Interfaces> tab, in the <Network Configuration> block.
The PDU always generates a Link-local address starting with “FE80::”.
This address is automatically generated and loses its scope at the first network hop encountered.
IPv6 addresses can be found on the web interface or on the “IPv6 Link” page on the PDU display, as shown in the image below.
To enable IPv6 support, the user must log in to the PDU using the IPv4 address displayed on the display. After logging in, select the “Interfaces” tab. In the network configuration section, there is a drop-down box called “IP Protocol select”. The default value of this drop-down box is “IPv4 Only”.
To enable IPv6, set this to “IPv6 Only” or “IPv4/IPv6 dual-stack”, which means that the PDU can communicate via both protocols.
If you select “IPv4 Only” or “IPv6 Only”, one of the filter ranges must be all zeros (allow all addresses). This is to prevent users from locking themselves out. Filter ranges can be configured afterwards when the user has connected to the bridged and/or hybrid PDU with the protocol specified earlier.
Enabling IPv6 adds an additional page to the PDU display called “IPv6 LINK” (see image). The current IP mode is also visible when the user navigates to the “IP INTERFACES” display.
Settings for IPv6 address filtering can be found on the <Interfaces> tab, under <Access Control> from the web interface.
In the web interface shown in the image below, users can specify three IP ranges that allow access; anything outside these IP ranges will be blocked. If the user wants to configure only one range, all three boxes with that range must be filled.
By setting any address with a prefix of “0”, every address is granted access to the PDU web interface, SNMP, Modbus, etc.
By setting the address to “::” (all zeros) and the prefix to a number between 0 and 128, the allowed IP range is limited to the network to which the PDU is connected. Filtering is then disabled.
Note: All “allowed IPv6 range” fields must be filled in to make the filter(s) work!
IPv6 Example
Setting a filter of A76F::D222:12FF:FEB0:F48/64 allows any address beginning with A76F:0000:0000:0000: (A76F::) but blocks other addresses such as A76A::32D4:731B:F17B:6. For a more detailed explanation, see the Wikipedia page on IPv6 subnetting. Note that filtering requires a complete and valid IP address to function properly.
IPv6 filter range.
PDUs current IPv6 addresses.
For enhanced security, communication can be encrypted using SSL certificates.
Key Generation
Certificates with a public and private key can be uploaded via the web interface. The certificates are used for the authentication phase of the handshake. These certificates can be generated in 3 steps:
– Generate a private key
– Generate a CSR (Certificate Signing Request) with the private key.
– Create a self-signed certificate with the CSR.
The following private keys are supported:
– RSA (1024 bit)
– Elliptic curve (secp256r1/prime256v1 and secp384r1)
– Supported TLS cipher suites:
The TLS cipher suites are enumerated in the following format (example):
– TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
– TLS prefix
– Key Exchange Algorithm (DHE) (Excluded for static keys)
– Authentication Algorithm (RSA)
– Encryption Algorithm (AES)
– Encryption Strength (256)
– Encryption Mode (GCM)
– MAC (SHA384)
The uploaded certificate is used for the “Authentication Algorithm” (RSA or Elliptic Curve). Other options (Key Exchange, Encryption, etc.) are selected based on what the client indicates as supported in the “Client Hello”. The following cipher suites are supported:
Static key with RSA:
– MBEDTLS_TLS_RSA_WITH_AES_128_GCM_SHA256
– MBEDTLS_TLS_RSA_WITH_AES_128_CBC_SHA256
– MBEDTLS_TLS_RSA_WITH_AES_256_CBC_SHA256
– MBEDTLS_TLS_RSA_MET_AES_128_CBC_SHA
– MBEDTLS_TLS_RSA_MET_AES_256_CBC_SHA
Ephemeral Elliptic-curve Diffie-Hellman with elliptic curve:
– MBEDTLS_TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
– MBEDTLS_TLS_ECDHE_ECDSA_MET_AES_256_CBC_SHA
– MBEDTLS_TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
– MBEDTLS_TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Diffie-Hellman with elliptic curve:
– MBEDTLS_TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
– MBEDTLS_TLS_ECDH_ECDSA_MET_AES_256_CBC_SHA
– MBEDTLS_TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
– MBEDTLS_TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256
Note on Self-Signed Certificates
Currently, only self-signed certificates are supported.
Certificate Generation
OpenSSL can be used to generate the private keys and certificates. Upon request, we can provide scripts for this purpose.
1. Open the “Webserver” section.
2. Select or add HTTPS to the webserver section “HTTP/HTTPS”.
3. Select the port (default: 443) you wish to use for HTTPS communication.
4. Click on “Save Changes”.
5. Unlock the “Certificates” section.
6. Enable “Use Custom Certificates”.
7. Load your certificate in an editor, select the text, and paste it into the appropriate field.
8.Load your private key in an editor, select the text, and paste it into the designated field.
9. Click on “Save Changes”.
10. Go to the system tab and restart the PDU to update your new configuration.
In the Firmware Updater Tool manual, you will find all the steps necessary for upgrading or downgrading.
To update the firmware, you need a tool available on our website’s download page. A manual is also provided on this page.
Actions:
The update manual provides detailed instructions for firmware upgrading. In summary:
– Download and first upgrade this Gateway firmware (if used in the databus); this firmware integrates an updater tool.
– Download the zip file of the Firmware Updater tool.
– Download the required firmware:
– Classic PDU: SPFW-01..- series
– PDU: SPFW-02.. -series
– Unzip the updater tool.
– Execute the updater tool; this tool downloads the firmware to all devices in the ring
The PDU firmware updater tool is available for Windows, Mac OS, and Linux. The Gateway firmware is available for Windows and Mac OS.
Starting from firmware version 2.40 and newer, it is possible to select a duration after which the alert will be cleared once the cause of the alert has been resolved. It is no longer necessary to manually clear the alert on the PDU or through an interface after the event that triggered the alert has been resolved.
Important: Alerts are always caused by issues that need to be addressed as soon as possible. Therefore, it is important that the alerts are recorded/logged in a management system.
This is an overview of Schleifenbauer Devices and Their Firmware Versions.
Generation 1
– Gateway: SPGWupdater_xxx_254
– Firmware version: EOL
– Device and firmware development status: This device is no longer for sale. Firmware development has been discontinued.
– Classic PDU
– Firmware version: FW1.50
– Device and firmware development status: EOL. This device is no longer for sale. Firmware development has been discontinued.
– DPM27
– Firmware version: FW1.50
– Device and firmware development status: EOL. This device is no longer for sale. Firmware development has been discontinued.
Generation 2
– PDU
– Firmware version: FW2.xx
– Device and firmware development status: This device has been replaced by the PDU G3, which is equipped with an additional USB port. Firmware development is ongoing and is based on the data model SPDM2xx.
– DPM3
– Firmware version: FW2.xx
– Device and firmware development status: EOL, but firmware development is still ongoing and is based on the data model SPDM2xx.
Generation 3
– PDU G3
– Firmware version: FW2.xx
– Device and firmware development status: The device is available and firmware development is ongoing, based on the data model SPDM2xx.
– DPM27/E
– Firmware version: FW2.xx
– Device and firmware development status: EOL, but firmware development is still ongoing and is based on the data model SPDM2xx.
* EOL = End of Life, product has been discontinued.
The development of PDU firmware is an ongoing process. With each new release, not only are issues resolved, but new features are also added. There will be various minor improvements and fixes, as well as general performance and stability enhancements. Always ensure that the firmware is up-to-date to ensure that the PDUs are equipped with the latest technology and features.
If devices are connected in a databus ring, upgrading all connected devices can be done remotely! During the upgrade process, power distribution is not interrupted. Our firmware, firmware tools, and manual can be downloaded from our website and are free to use.
If there is a Schleifenbauer Gateway present in the databus, make sure to upgrade the Gateway firmware first. This firmware is listed on the documentation page of the Schleifenbauer website. The latest firmware, manual, and updater tool are available on the support page of our website.
SPST stands for “Schleifenbauer Products Service Tool.”
This program is designed to assist customers in analyzing and maintaining their network of Schleifenbauer PDUs and DPM energy meters. SPST provides the following features:
– Users can quickly scan the status of the databus.
– Users can easily upgrade and downgrade firmware.
– Users can remotely configure databus devices in bulk.
– SPST reduces turnaround time for issue resolution.
SPST and its manual can be downloaded from our website. We advise our customers to read the manual before using SPST. One of the objectives of the SPST tool is to make firmware updates and bulk configuration easier.
All G3 products are equipped with a USB port near the PDU display. USB support is enabled by default unless explicitly disabled by the user. To initiate the update process, ensure that USB support is enabled in the web interface.
This can be done in the Settings section of the web interface. Alternatively, it is possible to enable or disable the USB interface via the Modbus or SNMP interface.
Download the latest firmware from https://docs.schleifenbauer.eu/?dir=Firmware.
The firmware is provided as a single ZIP archive. Extract the entire contents of this archive onto an empty FAT32-formatted USB flash drive. Safely remove this USB flash drive from the PC and insert it into a PDU. The upgrade will start automatically.
When interface settings are modified, the CPU must be restarted to adapt to the new settings. A pop-up appears in the web interface when a restart is necessary:
Remotely
A software reset can be performed in the web interface. It is important to understand that a software reset does not affect the power distribution of the PDU. Therefore, a reset can be performed at any time without interrupting the power supply and without losing the settings in the PDU.
Locally
The PDU can be restarted using a paperclip or a similarly sized object to press the reset button. This button is located behind the hole labeled ‘rst’ on the PDU next to the Ethernet port.
If the PDU is no longer accessible via the local network, for example, because the settings have been changed, it may be necessary to restore IP access.
The following procedure ensures that the PDU assumes various default values, allowing it to be rediscovered on the network without losing other settings in the PDU. However, the power supply must be interrupted to perform this recovery procedure! The procedure is described in five steps:
– Interrupt the power supply to the PDU.
– Restore the power supply.
– Wait a second, then press the reset button with a paperclip.
– Wait another second, then press the reset button again.
– Wait another second, then press the reset button again.
The PDU has now adopted the default values for the IP settings. The access control fields and the web server settings have also been reset to their default values.
Please note that by removing the power, the outlets will also be without power. Therefore, no measurements will be taken during this process.
Please also note that the kWh totals will NOT be reset during this process.
For example: The “overcurrent warning threshold” is set to 5.00A in the <Settings> tab. At a certain point, a warning appears on the dashboard of the web interface.
Check the Inputs tab and observe the peak current of 8.30A in this example:
Clear the warning locally or via the reset button in the <System> tab; the peak current will not be cleared.
This is done manually by clicking the button in the <System> tab section:
Please feel free to reach out to us if you have any inquiries about our products.
Submit a support request at the end of this page.