User manual

Configuration instructions,
ORION controller

www.deltapowersolutions.com
Table of contents
1 About configuration............................................................................................. 6
1.1 Overview of system configuration ............................................................ 6
1.2 User interface ........................................................................................... 7
1.2.1 Web user interface ..................................................................... 7
1.2.2 Local user interface ................................................................... 7
1.2.2.1 Basic gestures ............................................................ 7
1.2.2.2 Top level of the menu ................................................. 7
1.2.2.3 Sub menu ................................................................... 8
1.2.2.4 Password .................................................................... 8
1.2.2.5 Screen saver .............................................................. 8
1.2.3 User interface module UIM Touch ............................................. 8
1.3 Connecting a computer to ORION Touch ................................................ 9
1.3.1 Introduction ................................................................................ 9
1.3.2 Connecting computer to ORION Ethernet port .......................... 9
1.3.2.1 Connecting a computer using automatic mode .......... 9
1.3.3 Connecting computer to ORION via USB-Ethernet adapter ... 10
1.3.4 Connecting a computer or a smart phone to ORION via WLAN
................................................................................................. 10
1.3.4.1 Enabling WLAN AP in ORION.................................. 10
1.3.4.2 Connecting a computer or a smartphone to ORION
over WLAN ............................................................... 11
1.4 Connecting ORION to a LAN ................................................................. 12
1.4.1 Setting the Ipv4 network parameters manually ....................... 12
1.4.2 Setting the Ipv4 network parameters automatically ................. 12
1.4.3 Setting the Ipv6 parameters ..................................................... 13
1.4.4 IP filtering ................................................................................. 14
1.4.5 HTTPS ..................................................................................... 14
1.4.6 VLAN ........................................................................................ 15
1.5 Connecting ORION to a remote server .................................................. 15
1.5.1 Simple Network Management Protocol (SNMP) ..................... 15
1.5.1.1 Installing the software license key ............................ 16
1.5.1.2 Configuring SNMP .................................................... 16
1.5.1.3 Using a loadable MIB ............................................... 19
1.5.2 Modbus slave protocol ............................................................. 19
1.5.2.1 Configuring Modbus Slave TCP ............................... 20
1.5.2.2 Configuring Modbus Slave RTU or ASCII ................ 20
1.5.3 Syslog protocol ........................................................................ 21
1.5.3.1 Configuring syslog .................................................... 21
2 Configuration .................................................................................................... 23
2.1 Configuring ORION controller ................................................................ 23
2.1.1 Active setup ............................................................................. 23
2.1.2 Parameter scope: global and site specific parameters ............ 23
2.1.2.1 Saving the active setup as a setup file to PC ........... 24
2.1.2.2 Restoring the setup file from PC .............................. 24
2.1.2.3 Clearing the active setup .......................................... 24
2.1.2.4 Deleting the active setup .......................................... 24
2.1.3 Configuration management ..................................................... 25
2.1.4 User interface language ........................................................... 26
2.1.5 Meter panel .............................................................................. 26
2.2 Configuring batteries .............................................................................. 28
2.2.1 Supported battery types ........................................................... 28
2.2.2 Battery profiles ......................................................................... 29
2.2.3 Configuring and enabling of battery strings ............................. 30
2.2.4 Float charge ............................................................................. 31
2.2.5 Temperature compensation ..................................................... 31

Configuration instructions, ORION controller Table of contents

 2.2.5.1 Linear mode.............................................................. 32
2.2.5.2 Multi-stage ................................................................ 32
2.2.5.3 Thermal runaway protection ..................................... 33
2.2.5.4 Making the settings .................................................. 33
2.2.6 Equalize ................................................................................... 34
2.2.7 Boost charge ............................................................................ 36
2.2.8 Lithium battery handling ........................................................... 38
2.2.8.1 Connecting a lithium-ion battery to ORION Touch via
a GWM-Battery module ............................................ 38
2.2.8.2 Replacing a lithium-ion battery ................................. 38
2.2.8.3 Removing a lithium-ion battery ................................. 39
2.2.8.4 Connecting a lithium-ion battery to an RS485 port of
ORION Touch ........................................................... 39
2.2.8.5 Replacing a lithium-ion battery ................................. 40
2.2.8.6 Removing a lithium-ion battery ................................. 40
2.2.9 Hybrid battery management .................................................... 40
2.3 Battery supervision ................................................................................. 41
2.3.1 System voltage supervision ..................................................... 41
2.3.2 Middle point measurement ...................................................... 43
2.3.3 Block voltage measurement .................................................... 44
2.3.4 Temperature supervision ......................................................... 45
2.3.4.1 Temperature difference (Tdiff).................................. 45
2.3.4.2 High temperature alarm ............................................ 45
2.3.4.3 Temperature supervision parameters ...................... 45
2.3.5 Current difference (Idiff) ........................................................... 47
2.3.6 Loss of backup time ................................................................. 49
2.3.7 Low Voltage Disconnection of the battery ............................... 50
2.3.8 Partial Load Disconnection (PLD) ........................................... 51
2.3.9 Battery test ............................................................................... 52
2.3.9.1 The battery test parameters ..................................... 52
2.3.10 Separate charge and discharge............................................... 54
2.3.11 Battery life prediction ............................................................... 56
2.3.12 State of charge and remaining backup time estimation .......... 57
2.4 Configuring load string monitoring ......................................................... 58
2.5 Configuring rectifiers .............................................................................. 59
2.5.1 Overview of configuring rectifiers............................................. 59
2.5.2 Rectifier parameters ................................................................ 59
2.5.3 Rectifier alarms ........................................................................ 62
2.5.4 Installing Rectifiers ................................................................... 64
2.5.4.1 Web user interface ................................................... 64
2.5.4.2 Touch UI interface .................................................... 64
2.5.4.3 UIM interface ............................................................ 64
2.5.5 Removing rectifiers .................................................................. 65
2.5.5.1 Web user interface ................................................... 65
2.5.5.2 Touch UI interface .................................................... 65
2.5.5.3 UIM interface ............................................................ 65
2.5.6 Energy saving rectifier functions .............................................. 66
2.5.6.1 Rectifier efficiency cycling ........................................ 66
2.5.6.2 Event controlled standby .......................................... 67
2.5.7 Power limitation by event ......................................................... 68
2.5.8 Recharge power supervision ................................................... 69
2.5.9 Redundancy supervision ......................................................... 70
2.5.10 Rectifier AC measurement ....................................................... 70
2.5.11 Slot population ......................................................................... 70
2.6 Configuring DC/DC converters............................................................... 72
2.6.1 Overview of configuring DC/DC converters ............................. 72
2.6.2 DC/DC converter parameters .................................................. 72
2.6.3 DC/DC converter alarms.......................................................... 74

Configuration instructions, ORION controller Table of contents

 2.6.4 Installing DC/DC converters .................................................... 76
2.6.4.1 Web user interface ................................................... 76
2.6.4.2 Touch UI interface .................................................... 76
2.6.4.3 UIM interface ............................................................ 76
2.6.5 Redundancy supervision ......................................................... 77
2.7 Configuring PV chargers ........................................................................ 78
2.7.1 Overview of configuring PV chargers ...................................... 78
2.7.2 PV charger parameters ............................................................ 78
2.7.3 PV charger alarms ................................................................... 80
2.7.4 Installing PV chargers .............................................................. 82
2.7.4.1 Web user interface ................................................... 82
2.7.4.2 Touch UI interface .................................................... 82
2.7.4.3 UIM interface ............................................................ 82
2.8 Configuring Delta inverters ..................................................................... 83
2.8.1 Overview .................................................................................. 83
2.8.2 Inverter Operating Modes ........................................................ 83
2.8.3 Inverter Operating Profiles ....................................................... 83
2.8.4 Inverter parameters ................................................................. 84
2.8.5 Inverter alarms ......................................................................... 85
2.8.6 Installing Inverters .................................................................... 87
2.8.6.1 Web user interface ................................................... 87
2.9 Configuring Eltek Rectiverters................................................................ 88
2.9.1 Overview .................................................................................. 88
2.9.2 Supported system configurations and operating modes ......... 88
2.9.3 Rectiverter parameters ............................................................ 88
2.9.4 Rectiverter alarms .................................................................... 89
2.9.5 Installing Rectiverters into the system ..................................... 90
2.9.6 Removing Rectiverters from the system .................................. 90
2.9.7 Replacing Rectiverters ............................................................. 90
2.9.8 Operating the bypass switch.................................................... 91
2.10 Converter positioning ............................................................................. 93
2.10.1 Cabinet scheme ....................................................................... 93
2.10.1.1 Web user interface ................................................... 94
2.10.2 Shelf scheme ........................................................................... 94
2.10.2.1 Web user interface ................................................... 95
2.11 Configuring CE + T inverters .................................................................. 96
2.12 Configuring communication with 3rd party Modbus devices ................... 96
2.13 Configuring airconditioners .................................................................... 98
2.14 Configuring fan speed control units ....................................................... 99
2.15 Configuring alarms ............................................................................... 100
2.15.1 Alarm mapping ....................................................................... 100
2.15.1.1 Managing Alarm Events list .................................... 100
2.15.1.2 Mapping alarms to outputs ..................................... 101
2.15.1.3 Editing the output labels ......................................... 102
2.15.2 Alarm stop .............................................................................. 103
2.15.2.1 Web user interface ................................................. 103
2.15.2.2 Touch UI ................................................................. 103
2.15.3 Alarm latch reset .................................................................... 103
2.15.4 Alarm indication on Touch UI................................................. 104
2.16 Signal processing engine ..................................................................... 105
2.16.1 Measurements ....................................................................... 105
2.16.1.1 Web user interface ................................................. 106
2.16.2 Measurement processing ...................................................... 107
2.16.2.1 Web user interface ................................................. 108
2.16.3 Event definitions .................................................................... 108
2.16.3.1 Web user interface ................................................. 108
2.16.3.2 Touch UI/UIM interface .......................................... 109
2.16.4 Event processing ................................................................... 109

Configuration instructions, ORION controller Table of contents

 2.16.4.1 Web user interface ................................................. 113
2.16.4.2 Touch UI/UIM interface .......................................... 113
2.16.5 Inputs, outputs, LEDs and other indicators ............................ 113
2.16.5.1 Web user interface ................................................. 114
2.16.5.2 UIM interface .......................................................... 116
2.17 Configuring AC measurements ............................................................ 117
2.17.1 Selecting the AC measurement type ..................................... 117
2.17.1.1 Web user interface ................................................. 117
2.17.2 Configuring external AC measurement ................................. 117
2.17.3 Configuring internal AC measurement with single-phase
rectifiers ................................................................................. 118
2.17.3.1 Systems without converter positioning ................... 118
2.17.3.2 Web user interface ................................................. 118
2.17.3.3 Touch UI interface .................................................. 119
2.17.3.4 UIM interface .......................................................... 119
2.17.3.5 Systems with converter positioning ........................ 120
2.17.3.6 Web user interface ................................................. 120
2.17.4 Configuring internal AC measurement with three-phase
rectifiers ................................................................................. 120
2.17.4.1 Web user interface ................................................. 120
2.17.5 Display of AC measurement .................................................. 120
3 Logging function ............................................................................................. 121
3.1 Setting up the default log via web user interface ................................. 121
3.2 Checking the log .................................................................................. 121
3.2.1 Web user interface ................................................................. 122
3.2.2 Touch UI interface ................................................................. 122
3.2.3 UIM interface.......................................................................... 122
3.3 Storing log files to USB memory .......................................................... 122
4 User and session management...................................................................... 124
4.1 Default user profiles and access levels ................................................ 124
4.1.1 Delta’s recommendation for user profiles .............................. 125
4.1.1.1 Adding a complete set of user profiles by loading in a
user file ................................................................... 126
4.1.1.2 Adding a single user profile .................................... 126
4.1.1.3 Changing password ................................................ 126
4.1.1.4 Editing user profiles ................................................ 126
4.1.1.5 Deleting a user profile ............................................ 127
4.1.1.6 Saving the user profiles to PC ................................ 127
4.1.1.7 Deleting the user file ............................................... 127
4.2 Radius .................................................................................................. 127
4.2.1 Enabling and configuring RADIUS ........................................ 128
4.3 Session management .......................................................................... 128
4.3.1 Login control .......................................................................... 129
4.3.2 Common parameters ............................................................. 129
4.3.2.1 Editing common parameters .................................. 129
4.3.3 Priority of local access ........................................................... 130
5 Inventory report .............................................................................................. 131
5.1 Creating an inventory report................................................................. 131
6 Controller backup ........................................................................................... 132
6.1 Automatic Backup ................................................................................ 132
6.2 Enabling the automatic backup ............................................................ 132
6.3 Replacing a controller in field ............................................................... 133
6.4 Manual backup ..................................................................................... 133
6.4.1 Saving a backup manually to PC ........................................... 133
6.5 Restoring backup from PC ................................................................... 133
6.5.1 Saving backup manually to USB memory ............................. 134
6.5.2 Restoring backup manually from USB memory..................... 134
7 Document storage .......................................................................................... 136

Configuration instructions, ORION controller Table of contents

 Appendix 1 ........................................................................................... 137
Connecting ORION to a computer via LAN port using manual mode.. 137
Appendix 2 ........................................................................................... 138
Connecting to a computer with fixed IP address that the user cannot
change ................................................................................... 138

Configuration instructions, ORION controller Table of contents

1 About configuration
This document is valid for ORION software version V8.5x, where x represents minor
software change.

This document describes the configuration procedures required to enable the ORION
controller to control and monitor a power system and associated components.

Each procedure is described in the following way:

 Feature purpose: a brief description of the feature to be configured.

 Parameters: What parameters need to be set
 How?: the menu location for each user interface option and in complex cases
the steps required to configure the feature
 Reference: references to other information which may be of interest.

1.1 Overview of system configuration

The ORION controller is used to control and monitor power systems and their
components. A typical power system includes rectifiers, batteries, and DC distribution to
the load. The ORION also provides alarm monitoring, AC measurement, and logging
functions.

The power system is configured when it is installed. The system may also require
reconfiguring during its lifetime, for example, if components are added or removed, or if
the physical configuration of the system is rearranged.

The ORION offers three user interfaces; a web user interface (web browser), a Local
User Interface (UIT) with a touch display and an optional User Interface Module (UIM
Touch). The web user interface allows access to the full range of configuration and
supervision functions. The local interface UIT and UIM Touch allow access to the most
essential functions.

The web user interface is accessed through a web browser on a computer and made
through either a direct connection or over a network.

The local user interface Touch UI is integrated in the front panel of the ORION controller,
while the (optional) user interface module UIM Touch can be located anywhere at the
site, for example at system cabinet door.

Note! The local user has a higher priority than a WEB user. If the Touch UI or
UIM Touch user changes a parameter, the web session is terminated.

6 Configuration instructions, ORION controller About configuration

1.2 User interface

1.2.1 Web user interface

All configuration functions are available through the web user interface.

Access the web user interface with a standard browser and navigate with a normal
keyboard and mouse. Most of the displayed measurements and states are updated
automatically.

1.2.2 Local user interface

The local user interface is an easy to use and intuitive touch display which is operated by
simple, smartphone like gestures

1.2.2.1 Basic gestures

Tap on an active element or an icon to enter a sub-screen

or to execute an action.
Active elements/icons are the ones coloured in blue.

Long tap on the backspace icon in the Numeric Keypad

cancels the entire value.

Swipe left or right to navigate between the top level

screens.

Swipe right to dispose the current screen and go back to the

previous screen.
Note: A swipe right, that should returns to the top level,
always goes to the MENU screen.

Swipe up/down to scroll vertically.

1.2.2.2 Top level of the menu

There are four pages on the top level, and the user can navigate between them by
swiping left and right.

STATUS <> MENU <> ALARMS <> METER PANEL

STATUS
STATUS page shows the main parameters of the system and indicates if there is a
problem.
There is no need to scroll on the STATUS page, but the user can tap an icon to enter to a
sub menu such as RECTIFIER or BATTERY or tap theALARM icon to enter to the
ALARM page.

Configuration instructions, ORION controller About configuration 7

 MENU
The number of displayed icons on the MENU page depends on the configuration and
enabled features. To see them all the user can scroll the page by swiping up/down.
The user can tap an icon to enter to a sub menu.

ALARMS
The active Alarm Events and Issues are listed on this page. Issue list shows functions
that the user should look at. There might be something wrong with the function, but there
is no alarm configured to sindicate it. If the list is long, the user can swipe up/down to see
all items.

METER PANEL
The content of METER PANEL is configurable and the user can scroll the list by swiping
up/down to see all items. METER PANEL can be optionally configured to be the “Home
Page”. The selection can be done through the web page “Options”.

1.2.2.3 Sub menu

The user can enter to a sub menu by tapping an icon on the HOME or MENU page, and
come back by swiping from left to right. The sub menus contain typically both read-only
information and editable settings. The editable items are distinguished by blue color.

1.2.2.4 Password

When a password is required, a numerical keyboard will automatically appear. The

default password is 112443 but it can be changed by the user.

1.2.2.5 Screen saver

To extend the display life, ORION activates a screen saver after a time-out. In case there
are no active alarms, the display is dimmed and shows a slowly moving Delta logo. In
case there is an active alarm, a red bell is shown instead of the Delta logo. To catch
attention, the screen can additionally blink. This can be configured through the web Gui in
the options menu.

1.2.3 User interface module UIM Touch

UIM Touch is an optional user interface module for ORION Touch. It offers the same
menu structure and touch functionality as the local touch interface UIT, but in bigger size.
(3.5 inch) It is designed to be mounted on a cabinet door, and too support easy system
upgrades it fits into the same opening as the old UIM.

8 Configuration instructions, ORION controller About configuration

1.3 Connecting a computer to ORION Touch

1.3.1 Introduction

ORION can be connected to computer either through the Ethernet port or the USB port
using an USB to Ethernet adapter or a WLAN dongle.

ORION has the possibility to operate with IPv6 addresses and Ipv4 simultaneously. (Dual
stack). In case Ipv6 Mode is disabled only Ipv4 communication are possible.

1.3.2 Connecting computer to ORION Ethernet port

The Ethernet port of ORION supports two different operating modes: manual and
automatic. In manual mode the network parameters are set manually both in computer
and in ORION. In automatic mode, IP address and Subnet Mask are automatically set
according to RFC 3927 (Zeroconf).
As the most common way is to use automatic mode, the instructions concerning the
manual mode are found in the appendix at the end of this document.

1.3.2.1 Connecting a computer using automatic mode

Use this procedure to connect a computer directly to the Ethernet (LAN) interface of the
ORION:

Step 1 Make sure that the DHCP is enabled in the computer. (The network adapter is
configured to obtain the IP address automatically.)

Step 2 Enable the Automatic mode in ORION by using the local user interface.
Touch UI: MENU  Network  IPv4
UIM: NET CONFIG → ETHERNET → IPv4→ MODE.

Step 3 Connect the computer to ORION with an Ethernet cable.

Step 4 Wait for a while and let ORION and computer negotiate the network parameters.
This can take up to two minutes because the computer needs some time to
detect that there is no DHCP server in the network and start the address
autoconfiguration process.

Step 5 Open an internet browser.

Step 6 In the address bar of the internet browser, enter the IP address of ORION which
is shown at:
Touch UI: MENU  Network
UIM: NET CONFIG → ETHERNET → IPv4→ IP ADDRESS.

Step 7 When the ORION configuration and supervision tool login page loads, enter the
username and password, and click “Submit”.

Step 8 The web interface is now open and it is possible to change the configuration and
setting if necessary.

Step 9 Click “Logout” when you are ready.

Configuration instructions, ORION controller About configuration 9

 Note! Troubleshooting:

If the web server of ORION does not response, please check the following things:

1 Check that you entered the correct IP address to the browser.

2 Check the proxy server setting in the browser options. A proxy shall not be
used.

3 Check that the IP address and the network mask are correctly defined by
the autoconfiguration process. The IP address of your LAN adapter should
be 169.254.xxx.xxx, where x is any number and the network mask should
be 255.255.0.0. If the address is from a different range, check that your
network adapter is set to obtain the IP address automatically.

4 Deactivate other networks: WLAN, Wireless WAN etc. If there are other
network connections active, it might be that the active routings do not
support communication to the 169.254.. network.

5 Even if all the settings seem to be OK, reboot the computer and try once
more. If this does not help, follow the instructions in the appendix and use
the manual mode with fixed IP addresses.

1.3.3 Connecting computer to ORION via USB-Ethernet adapter

Use this procedure to connect a computer to ORION via USB port:

Step 1 Make sure that the DHCP is enabled in your PC.

Step 2 Plug in the USB to Ethernet adapter to the USB port of ORION.

Step 3 Connect your PC to the LAN port of the adapter by a cable.

Step 4 Open the web browser in your PC and enter the URL: http://orion.deltaww.com to
login to ORION.

1.3.4 Connecting a computer or a smart phone to ORION via WLAN

ORION is able to operate as WLAN access point making it possible to use tablets and
smartphones for local access.

1.3.4.1 Enabling WLAN AP in ORION

Use this procedure to enable WLAN AP in ORION using the web interface:

Step 1 Go to Configuration → System → Interface Setup → TCP/IP.

Step 2 Enable WLAN-AP by ticking the checkbox.

Step 3 Enable “Default WLAN Operation” by ticking the checkbox or define the “WLAN
SSID”, “WLAN Channel” and “WLAN PSK” manually.

10 Configuration instructions, ORION controller About configuration

 Step 4 Optionally enable Encryption.

1.3.4.2 Connecting a computer or a smartphone to ORION over WLAN

Step 1 Make sure that the DHCP and WLAN is enabled in your device.

Step 2 Plug in the WLAN adapter to the USB port of ORION. The menu for SSID and
PSK is shown on the LCD display of ORION (if it is not visible, it can be found in
the local user interface:
Touch UI: MENU  Network  WLAN
UIM: NET CONFIG → WIRELESS LAN).

Step 3 Connect your device to the new wireless network that just started.

Step 4 Check the PSK from ORION and enter it to your device.

Step 5 Open the web browser in your device and enter the URL:
http://orion.deltaww.com to login to ORION or use a smartphone app.

Configuration instructions, ORION controller About configuration 11

1.4 Connecting ORION to a LAN
The Ethernet port of ORION supports two different operating modes for Ipv4 network:
Manual and Automatic. In manual mode the network parameters of ORION are set
manually. In automatic mode, the network parameters are provided by the DHCP server
or selected according RFC 3927 Dynamic Configuration of Ipv4 Link-Local Addresses, if
there is no DHCP server running in the network.

1.4.1 Setting the Ipv4 network parameters manually

Use this procedure to connect the ORION to the local area network, using fixed IP
address.

The following parameters can be set

 IPv4 address
 IPv4 Subnet mask
 IPv4 Gateway address
 IPv4 DNS

Step 1 Enable the Manual mode in ORION using the local interface
Touch UI: MENU  Network  IPv4
UIM: NET CONFIG → ETHERNET → IPv4→ MODE

Step 2 Set the network parameters at:

Touch UI: MENU  Network  IPv4
UIM: NET CONFIG → ETHERNET→ IPv4.

Step 3 Connect the ORION to the LAN with the appropriate cable.

To check that the communication works correctly:

Step 1 Connect the computer to the LAN with the appropriate cable.

Step 2 Open an internet browser and connect to the defined IP address of the ORION.

Step 3 When the ORION login page loads, enter the username and password, and click
“Submit”.

Step 4 The web interface is now open and it is possible to change the configuration and
setting if necessary.

Step 5 Click “Logout” when ready.

1.4.2 Setting the Ipv4 network parameters automatically

Use this procedure to connect the ORION to the local area network, using DHCP server

The following parameters are automatically received from the DHCP server

12 Configuration instructions, ORION controller About configuration

  IPv4 address
 IPv4 Subnet mask
 IPv4 Gateway address
 IPv4 DNS

Additionally it is possible to enter the host name manually.

Step 1 Enable the Automatic mode in ORION by using the local user interface.
Touch UI: MENU  Network  IPv4
UIM: NET CONFIG → ETHERNET → IPv4→ MODE.

Step 2 Enter the host name for this ORION (without domain name). Allowed characters
are “a-z”, “A-Z”, “0-9” and “-“ (hyphen).

Step 3 Connect ORION to the LAN with the appropriate cable.

To check that the communication works correctly:

Step 1 Connect the computer to the LAN with the appropriate cable.

Step 2 Open an internet browser and connect to the IP address of the ORION. The IP
address is shown at:
Touch UI: MENU  Network
UIM: NET CONFIG → ETHERNET → IPv4→ IP ADDRESS.
Alternatively use the host name of ORION.

Step 3 When the ORION responds, enter the username and password, and click
“Submit”.

Step 4 The web interface is now open and it is possible to change the configuration and
setting if necessary.

Step 5 Click “Logout” when ready.

1.4.3 Setting the Ipv6 parameters

ORION has the capability to operate with Ipv6 addresses and Ipv4 simultaneously. (Dual
stack). If Ipv6 address is not used, the Ipv6 mode shall be “Disabled”. ORION supports
two different modes for Ipv6:

1 Automatic
 To be used when ORION is plugged into an Ipv6 ready network having
a router that supports “Stateless Address Auto configuration” (SLAAC,
RFC 4862) and the RA DNS option (RFC6106) or a DHCPv6 server.
2 Manual
 To be used when IPv6 Address, IPv6 Gateway Address and IPv6 DNS
are defined by the user.

Use this procedure to configure Ipv6 communication.

Step 1 Go to Configuration → System → Interface Setup → TCP/IP.

Configuration instructions, ORION controller About configuration 13

 Step 2 Change the IPv6 mode to Automatic or Manual depending on the level of IPv6
support of your network.

Step 3 Reboot the controller.

In automatic mode the following parameters are received from the router which
supports RFC 4862 and RFC 6106.

 IPv6 address
 IPv6 Prefix
 IPv6 gateway
 IPv6 DNS Auto

Step 4 Add the secondary DNS manually if needed.

Step 5 If manual mode is used, set the network parameters manually.

Step 6 Click “Accept Changes” when ready.

1.4.4 IP filtering

ORION allows filtering of the Ethernet traffic in 2 ways:

1 The ICMP communication can be disabled, then the controller will not reply to ping
requests anymore.
2 Allowed networks can be defined. If defined, only communication from those
networks will be accepted. It is possible to define four allowed networks.

Use this procedure to configure IP filtering:

Step 1 Go to Configuration → System → Interface Setup → TCP/IP.

Step 2 Optionally disable ICMP by ticking the check box.

Step 3 Optionally enable filtering by ticking the check box.

Step 4 Define the allowed networks using the CIDR notation. See RFC 4632 for the
details. For Ipv4 it looks like XXX.XXX.XXX.XXX/NN. Where XX.XXX.XXX.XXX is
a standard Ipv4 address notation and NN is a number from 0 to 32 representing
the number of bits to be masked from the IP address, starting from the MSB.
ORION checks the validity of the notation. For Ipv4, XXX.XXX.XXX.0\32 is not
allowed.

Step 5 Click “Accept Changes” when ready.

1.4.5 HTTPS

ORION supports Hypertext Transfer Protocol Secure (HTTPS) for secure communication.
HTTPS requires a key/certificate. There is a default certificate in ORION, but the user can
load in a customer certificate.

The user can define three different operating modes:

14 Configuration instructions, ORION controller About configuration

 1 HTTP
2 HTTPS (In this mode, the requests using HPPT will be ignored)
3 HTTP and HTTPS

The operating mode can be selected by using the web interface on the page
Configuration → System → Interface Setup → TCP/IP.

If customer certificate is used instead of the default certificate, the Key/Certificate shall be
pasted into the corresponding field as PEM format

1.4.6 VLAN

ORION is able to join into a single VLAN segment. This enables communication over
VLAN in trunk port mode.

The VLAN functionality can be activated and configured on the web page Configuration
→ System → Interface Setup → TCP/IP.
VLAN can be enable/disabled also via Touch UI at MENU > NETWORK.

1.5 Connecting ORION to a remote server

1.5.1 Simple Network Management Protocol (SNMP)

SNMP-based management system components are distributed throughout IP-based

networks in the form of agents and managers. ORION represents an SNMP agent entity,
making DC power system parameters available to an SNMP manager entity.

The ORION controller, as an agent, can send trap messages to the SNMP manager. The
ORION controller is able to send traps to ten IP addresses. For an SNMP manager to
understand a trap sent to it by an agent, the manager must have the Management
Information Base (MIB) for the specific traps loaded. As default ORION supports its own
enterprise MIB and partially MIB-2. As an option the own MIB can be replaced by loading
in a customized MIB Mapping file. Creating the mapping file requires advanced skills, so
this process is not covered by this document. To get a customized MIB, please contact
Delta.

The controller`s SNMP agent supports the SNMP V1, V2c, and V3 protocols. Since V3 is
different from V1 / V2c in terms of security the configuration of the access parameters is
different. The Web SNMP access configuration interface allows selecting between
‘V1/V2c’ or ‘V3’.

SNMP is activated by means of a software license key, which can be obtained from Delta
or authorized representative. Each controller needs an individual license key which is
based on MAC address of the controller. The MAC address can be read through WEB
GUI at Configuration → System → Interface Setup → TCP/IP. It can also be read locally
through the UIT at MENU > NETWORK, or from the product label on the controller.

SNMP can be activated either in the field with a laptop connected to the ORION, or
remotely over a LAN.

Configuration instructions, ORION controller About configuration 15

 Note! The software license key is not saved in the setup file and cannot be
copied from controller to controller.

1.5.1.1 Installing the software license key

Please follow the steps below to activate the SNMP:

Step 1 Go to Configuration → Options.

Step 2 Click “License Key”.

Step 3 Enter the license key code and click “Accept Changes”.

Step 4 Go to Status → Configuration → System → Interface Setup → TCP/IP, click

“Reboot”.

1.5.1.2 Configuring SNMP

1.5.1.2.1 Setting the access parameters for v1/v2c

Use this procedure to specify the global SNMP parameters when v1/v2c protocol is used.
Default values are: Read community = public Write community = private.

Step 1 Go to Configuration → System → Remote Monitoring → SNMP → Access.

Step 2 Select the version v1/v2c.

Step 3 If needed, modify the names of read and / or write community.

Step 4 Click “Accept Changes”.

1.5.1.2.2 Setting the access parameters for v3

Use this procedure to specify the global SNMP parameters when v3 protocol is used.

Step 1 Go to Configuration → System → Remote Monitoring → SNMP → Access.

Step 2 Select the version v3.

Step 3 Click “Add User”.

Step 4 Enter username, select the authentication and privacy protocols and enter
corresponding passwords.

Step 5 Click “Accept Changes”.

Step 6 Repeat steps from 3 to 5 if more than one user is needed.

1.5.1.2.3 Configuring alarm traps

16 Configuration instructions, ORION controller About configuration

 ORION is able to send four types of alarm traps. Three of the four alarm traps correspond
to the “S Non Urg Alarm”, “S Urgent Alarm”, and “S Critical Alarm” summary events.
ORION will send a trap if any of the sixteen input events for those OR-events changes
state.

The fourth type of alarm trap sends all the events which are defined as “alarm events” in
Alarm Setup. This trap is recommended to be used when the new alarm mapping
functionality is used instead of the “S Non Urg Alarm”, “S Urgent Alarm”, and “S Critical
Alarm”.

1.5.1.2.3.1 Trap destinations

To specify the SNMP trap destination addresses proceed as follows:

Step 1 Go to Configuration → System → Remote Monitoring → SNMP → Traps.

Step 2 Enter the IP address and Port number for each SNMP manager used. In case of
v3, select the usernames as well.

Step 3 Click “Accept Changes”.

1.5.1.2.3.2 Trap enabling and resend

Each of the four trap types can be enabled separately and additionally it is possible to
enable automatic resend with the defined interval.

To enable the traps and the automatic resend of traps proceed as follows:

Step 1 Go to to Configuration → System → Remote Monitoring → SNMP → Traps.

Step 2 Tick the “Enable” box for the trap types you want to enable.

Step 3 Tick the “Resend” box for the trap types you want to resend and define the
resend interval.

Step 4 Click “Accept Changes”.

1.5.1.2.4 Alarm table

The ORION has a generic alarm table with up to 16 entries. The user can map any of the
available events into this table. As this table is included in the MIB as a fixed place holder,
the status of the events in this table can be polled by the NMS any time.

To map the events into this table proceed as follows:

Step 1 Go to Configuration → System → Remote Monitoring → SNMP → Alarm Table.

Step 2 Use the drop-down lists to select the events.

Step 3 Click “Accept Changes”.

1.5.1.2.5 Control events

Configuration instructions, ORION controller About configuration 17

 The ORION has a configurable table for control events with up to 20 entries. The user
can map any RS Latch Event having no input events defined into this table. The status of
these events can be then changed remotely by using SNMP and locally via Maintenance
menu.

Note! SNMP write access is only granted if no other session with write access is
active. So if a user is logged into the WEB interface any SNMP write access
command fails and returns “No Access” as error code.

To map the events into this table proceed as follows:

Step 1 Go to Configuration → System → Remote Monitoring → SNMP → Control

Events.

Step 2 Use the drop-down lists to select the events.

Step 3 Click “Accept Changes”.

Step 4 Save the MIB file, provided by Delta, to the SNMP manager MIB file folder.

Step 5 Enable the SNMP connection to ORION.

When SNMP has been enabled the ORION controller sends information about the
system, and three alarms as default: Critical Alarm (CA), Urgent Alarm (UA) and Non-
Urgent Alarm (NUA).

1.5.1.2.6 Thresholds

The user can map up to 20 events that are defined on the page Configuration > Signal
Processing Engine > Event Definitions into this table to make it possible to edit the
thresholds remotely using SNMP.

To map the events into this table proceed as follows:

Step 1 Go to to Configuration → System → Remote Monitoring → SNMP → Thresholds.

Step 2 Use the drop-down lists to select the events.

Step 3 Click “Accept Changes”.

1.5.1.2.7 Timers

The user can map up to 20 timers that are defined on the page to Configuration > Signal
Processing Engine > Event Processing into this table to make it possible to edit the timer
parameters remotely using SNMP.

To map the timers into this table proceed as follows:

Step 1 Go to to Configuration → System → Remote Monitoring → SNMP → Timers.

Step 2 Use the drop-down lists to select the events.

18 Configuration instructions, ORION controller About configuration

 Step 3 Click “Accept Changes”.

1.5.1.2.8 Filters

The user can map up to 20 filter events that are defined on the page to Configuration >
Signal Processing Engine > Event Processing into this table to make it possible to edit
the timer parameters remotely using SNMP.

To map the timers into this table proceed as follows:

Step 1 Go to to Configuration → System → Remote Monitoring → SNMP → Filters.

Step 2 Use the drop-down lists to select the events.

Step 3 Click “Accept Changes”.

1.5.1.3 Using a loadable MIB

To use a lodable MIB instead of the default enterprise MIB proceed as follows:

Step 1 Go to to Configuration → System → File Manager to load in the MIB mapping file

Step 2 Select File Type “MIB Mapping” and click “Load File from PC”.

Step 3 Click “Browse” and select the correct file in your PC.

Step 4 Click “Start”.

1.5.2 Modbus slave protocol

As an option ORION controller can have Modbus slave protocol to support Modbus
communication with master in three different modes:

 RTU – using the controller’s serial line as an interface.

 ASCII – using the controller’s serial line as an interface. Similar to RTU but
with more data traffic and with less performance required from the serial line.
 TCP – communicating with the master through an Ethernet link.

The following Modbus functions are supported:

 Function 01 (0x01): Read Coils

 Function 02 (0x02): Read Discrete Inputs
 Function 03 (0x03): Read Holding Registers
 Function 04 (0x04): Read Input Registers
 Function 05 (0x05): Write Single Coil
 Function 06 (0x06): Write Single Register
 Function 15 (0x0F): Write Multiple Coils
 Function 16 (0x10): Write Multiple Registers
 Function 17 (0x11): Report Slave ID (ASCII or RTU mode only)
 Function 23 (0x17): Read/Write Multiple Registers

Configuration instructions, ORION controller About configuration 19

 ORION controller can be upgraded to support Modbus Slave protocol by configuring the
functionality via web interface and by loading in the Modbus Slave Mapping File.

Please contact Delta in case such upgrade is needed in order to provide the correct
mapping file. Delta needs the setup file of your ORION controller.

Note! A Modbus Slave Mapping File is dependent on the controller’s available

database elements. Therefore a Modbus Slave Mapping file must be deployed
only on ORIONs together with the appropriate setup file.

1.5.2.1 Configuring Modbus Slave TCP

Follow the process below to configure Modbus Slave TCP protocol.

Step 5 Go to Configuration → System → Remote Monitoring → Modbus Slave.

Step 6 Click “Change”.

Step 7 Select “TCP” and click “Accept Changes”.

Step 8 Change the “Listen Port” if necessary.

Step 9 Click “Accept Changes” and “Reload Values”.

The Protocol State shows “Wait for a valid Mapping File” and the Mapping File
State is “Missing”.

Step 10 Go to Configuration → System → File Manager to load in the mapping file.

Step 11 Select File Type “Modbus Slave Mappinge” and click “Load File from PC”.

Step 12 Click “Browse” and select the mapping file in your PC.

Step 13 Click “Start”.

Step 14 Check the default logo to see if there are messages concerning incompatible
mapping entries.

Note! The protocol will be running even in case there are some incompatible
mappings, but some registers might not provide the correct information.

Step 15 Go back to Configuration → System → Remote Monitoring → Modbus Slave.

The Protocol State should be “Running”.
The Mapping File State should be “OK”.

1.5.2.2 Configuring Modbus Slave RTU or ASCII

Follow the process below to configure Modbus Slave RTU or ASCII protocol.

Step 16 Go to Configuration → System → Remote Monitoring → Modbus Slave.

20 Configuration instructions, ORION controller About configuration

 Step 17 Click “Change”.

Step 18 Select “RTU” or “ASCII” and click “Accept Changes”.

Step 19 Change the “Slave ID” if necessary.

Step 20 Click “Accept Changes” and “Reload Values”.

The Protocol State shows “Wait for a valid Mapping File” and the Mapping File
State is “Missing”.

Step 21 Co to Configuration → System → Interface Setup → Serial

Step 22 Select the protocol “Modbus Slave” for any of the available serial ports

Step 23 Change the communication parameters if necessary and click “Accept Changes”

Step 24 Go to Configuration → System → File Manager to load in the mapping file.

Step 25 Select File Type “Modbus Slave Mapping” and click “Load File from PC”.

Step 26 Click “Choose File” and select the mapping file in your PC.

Step 27 Click “Start”. The mapping file will be loaded in.

Step 28 Go to Configuration → System → Remote Monitoring → Modbus Slave and verify

that the Protocol State is “Running” and the Mapping File State is “OK”.

1.5.3 Syslog protocol

Syslog is a protocol used to convey event notification messages. See RFC 5424 for more
information.

With ORION it is possible to define up to 128 events to be logged on up to 4 Syslog

servers. In addition it is also possible to log the system messages.

Parameter Description

Enable Enables or disables sending Syslog events.

Syslog Server URL or IP Syslog server URL or IP address. A DNS must be

configured in the system in order to resolve URLs.

Port Server listening port for Syslog protocol.

Facility This describes the source of the event, see RFC 5424
for more info.

1.5.3.1 Configuring syslog

To enable and configure Syslog functionality proceed as follows:

Step 1 Go to Configuration → System → Remote Monitoring → Syslog.

Configuration instructions, ORION controller About configuration 21

 Step 2 Tick the checkbox “Enable”.

Step 3 Click “Edit” to start Events selection.

Step 4 Tick the checkbox “System Messages” in case you want to send controller
system messages to Syslog server(s) and set the severity. The same severity
applies to all the system messages.

Step 5 Highlight one or more events in the “Events Selection” list and click one of the
“>>” buttons to move it to a column with an applicable severity class.

Step 6 Repeat step 5 for each event that you want to log into a Syslog server.
In order to deselect an event, select one or more events from a list and click the
“<<” button at the left side of the column. This will send the selected events back
to the “Events Selection” list.

Step 7 After all needed events are moved to applicable columns, click “Accept
Changes” and the “Back”.

Step 8 Enter an URL or an IP address for the server and select the proper server port
and facility. The facility is an information sent to the server to indicate the source
of the generated events, it applies for all events sent from the same controller.

Note! If you use an URL, a DNS server must be configured in the controller in
order to resolve the URL.

22 Configuration instructions, ORION controller About configuration

2 Configuration

2.1 Configuring ORION controller

2.1.1 Active setup

Each function of ORION has its own set of parameters which are stored in active setup.
When a parameter is changed it will be automatically saved. After the system has been
configured, the active setup can be stored on a computer as a setup file in xml format.
This file can be used to configure the system for example if the controller has been
replaced. The setup file can also be used where identical systems have been installed,
avoiding manual configuration in each installation. It can only be saved and restored
through the web user interface.

2.1.2 Parameter scope: global and site specific parameters

Each configuration parameter has a specific scope. A scope defines if the value for a
parameter should be taken from the loaded setupfile or is unique to the controller and
thus shall not be overwritten. A scope can be either “global” or “site”.

A parameter with scope “global” is a generic parameter that can be overwritten by loading
a new setup, activating a new configuration or restoring a backup. A parameter with the
scope “site” means the parameter is valid for specific site only and shall not be
overwritten by loading a new setup, activating a new configuration or restoring a backup.

Most of the parameters have a fixed scope set to “global”. Some have a fixed scope set
to “site”:

 GPS Coordinates

 Site Name

And some parameters have a configurable scope, so the user can decide whether the
parameter should get its value from the setup or not. The configurable parameters are:

 SNMP Trap Destinations

 SNMP Trap Ports
 RS 232 Serial Interface:
o Handshake
o Parity
o Baudrate
o Data-Bits
o Stop-Bits
 RS 485 Serial Interfaces
o Handshakes
o Parities
o Baudrates
o Data-Bits
o Stop-Bits

Configuration instructions, ORION controller Configuration 23

 The scope of the configurable parameters can ve set on the page Configuration →
System → Setup View, section “Parameter Scope”

Note! The scope setting is stored together with the parameter in the setup file.
While loading in a setup or activating a configuration, ORION looks at the scope
setting inside the new setup/configuration file and not the scope setting of the
active configuration.

2.1.2.1 Saving the active setup as a setup file to PC

Save the setup file in a specified directory on the computer.

Step 1 Go to Configuration → System → File Manager.

Step 2 Click “Save to PC” button beside the Setup file. The “Save As” dialogue
appears.

Step 3 Specify the directory, where the file should be stored and, if desired, modify the
file name.

Step 4 Click “Save”.

2.1.2.2 Restoring the setup file from PC

The setup file is loaded from the PC to the ORION.

Step 1 Go to Configuration → System → File Manager.

Step 2 From “File type” drop-down list select “Setup”.

Step 3 Click “Load File from PC”.

Step 4 In the “Load File from PC” dialogue click “Browse” and choose the desired setup
file.

Step 5 Click “Start”.

The transfer progress is displayed. After the setup is loaded and checked, it will
be activated automatically.

2.1.2.3 Clearing the active setup

The controller clears the setup configuration except network settings, user configuration,
calibration values, and license key features.

Step 1 Go to Configuration → System → Setup View.

Step 2 Click “Clear Setup”.

2.1.2.4 Deleting the active setup

24 Configuration instructions, ORION controller Configuration

 It is possible to remove the complete stored setup configuration by deleting the active
setup and subsequently rebooting the system. Please be aware that default network
settings are used after reboot and therefore it shall not be done remotely. In addition, the
old configuration cannot be retrieved anymore i.e. the complete configuration is lost
including settings such as SNMP and calibration values.

2.1.3 Configuration management

In addition to the active setup file the controller can have one or more alternative
configuration files (CFG_XYZ.xml) loaded in. This functionality is useful in cases where
the final system configuration is created at the site by combining system building blocks
together. The controller can have several ready-made configuration files in its memory to
support the different physical system variants.

When the user activates any of the configuration files, the active setup is updated by the
content of the chosen configuration file. When done, the state of the chosen configuration
file is “synchronized”. If the user changes any parameter in the system, the active setup is
automatically saved. The state of the activated configuration changes to “not
synchronized” indicating that the active setup is no more the same as the content of the
configuration file that was activated. The user has now the possibility to update the
activated configuration file by the parameters of the active setup, or he can keep the
original configuration file as a backup file. If the user updates the activated configuration
file, ORION creates automatically a backup of the previous file and stores it into the
controller. The name of the backup file is composed of the name of the file being updated
with an additional postfix number.

When the user loads in a Seup file, as described in the chapter “Restoring the setup file
from PC”, ORION does not only activate the setup automatically, but also creates and
activates a new Configuration file called CFG_”setup file name”.xml.

The different use cases and related user interfaces are shown in the table below:

Use case User interface Note

Load a configuration file from PC Web

Select and activate a configuration Web, Touch

UI, UIM

Deactivate a configuration and Web, Touch

activate another one UI, UIM

Revert changes in active setup by Web, Touch

reactivating a configuration file UI, UIM

Update an active setup to a Web, Touch

configuration UI, UIM

Delete a configuration file Web It is not possible to delete an

activated configuration

Save a configuration to PC Web It is not possible to save a

not synchronized
configuration to PC

Configuration instructions, ORION controller Configuration 25

 The applicable menu points are shown in the table below:

Interface Menu point

Web Configuration → System → Configuration Manager

Touch UI Menu → Device → Configurations

UIM Configuration → Conf Manager

2.1.4 User interface language

The user interface language can be selected from stored language files. The default
language is English. Three additional language files can be loaded by using the web
interface.

The applicable menu point for different actions are shown in the table below:

Use case User interface Menu point

Load a language file Web Configuration → System → File

Manager

Configure the language of a Web Configuration → System → User

web user Management

Configure the language of a Touch UI Menu → Device → Language

local user
UIM Configuration → System → Language

Delete a language file Web Configuration → System → File

Manager

2.1.5 Meter panel

The Meter Panel is a customizable page that allows the user to collect important events
and measurements for viewing on a single page. The measurements are also readable at
the UIM/UIL interface as a list.

To view the Meter Panel through the web user interface, go to Status → Meter Panel.

Each meter can be configured to represent almost any event or measurement required.
With optional Hour Meter setting also the active time of the events and with optional
Event Counter the number of transitions from “false” to “True” can be shown on the
Overview page.

When adding an item to the meter panel, the user can select an unique ID which has a
direct connection to the SNMP OID. By Using the meter panel functionality and the
manually selected IDs, the user can standardize the SNMP OIDs across his network also
for manually configured measurements such as “Wind speed” or “Fuel level”.

26 Configuration instructions, ORION controller Configuration

 Parameter Value range Description

ID 1 to 128 Unique identification number that defines

the SNMP OID

Name 1 to 15 characters Name of the new entry

Unit 0 to 15 characters Unit of the new entry

Input 1 -2147483.647 to Lower input value from the measurement

2147483.646 source.

Input 2 -2147483.647 to Upper input value from the measurement

2147483.646 source.

Output 1 -2147483.647 to Lower output value displayed on the

2147483.646 Meter panel.

Output 2 -2147483.647 to Upper output value displayed on the

2147483.646 Meter panel.

Fractional Digit(s) 0 to 3 Number of decimal places displayed.

Limit Values Boolean If the limit values are set, the output
values, which exceed the values set by
“Output 1” and “Output 2” are invalidated.

Table 1. Meter panel measurement parameters

Use this procedure to add measurements to the Meter Panel:

Step 1 Go to Status → Meter Panel.

Step 2 Select measurement from drop-down list.

Step 3 Click “Add Measurement”.

Step 4 Enter the required parameters described in Table 1.

Step 5 To save the changes, click “Accept Changes”.

Use this procedure to add events to the Meter Panel:

Step 1 Go to Status → Meter Panel.

Step 2 Select event from drop-down list.

Step 3 Click “Add Event”.

Step 4 Enable Hour Meter if necessary.

Step 5 To save the changes, click “Accept Changes”.

Configuration instructions, ORION controller Configuration 27

 To view the Meter panel measurements at the UIM/UIL interface, go to
STATUS → METER PANEL.

2.2 Configuring batteries

2.2.1 Supported battery types

In addition to lead-acid and nickel-cadmium batteries, ORION controller supports Lithium

batteries having built-in electronics for charging control, protection and digital
communication. ORION controller is able to communicate with Lithium batteries and use
the provided measurements instead of system measurements with shunts and Hall
sensors.

The available battery functions for different batteries are presented in the following table.

Function Lead-acid lithium nickel-

cadmium

Battery String Setup  

Battery Lithium Setup 

Charge Current Limitation   

Float Charge  

Temperature  
Compensation

Loss of Backup Time   

Battery Test   

Equalize  

Boost   

Separate Charge  

Middle Point  

Tdiff   

Idiff   

Event Controlled Charge   

Block Measurements  

Life Prediction   

LVD   

28 Configuration instructions, ORION controller Configuration

2.2.2 Battery profiles

Each battery management function uses a set of operating parameters. These

parameters can be edited manually according to the used battery type and size, and are
automatically stored as a part of the setup. Optionally the battery parameters can be
collected to a battery profile, which is stored as a file on ORION. The user can load in
several battery profile files which allow easy handling of different battery settings on the
same controller. The user can easily switch between different battery profiles using either
web interface or Touch UI. When using lithium batteries, ORION can activate a correct
battery profile automatically based on the detected battery type.

When the user activates any of the battery profiles, the active setup is updated by the
parameters of the chosen battery profile. When done, the state of the chosen battery
profile is “synchronized”. If the user changes any battery parameter in the system, the
active setup is automatically saved. The state of the activated battery profile to “not
synchronized” indicating that the active setup is no more the same as the activated
battery profile. The user has now the possibility to update the activated battery profile by
the battery parameters of the active setup, or he can keep the original battery profile as a
backup file. If the user updates the activated battery profile, ORION creates automatically
a backup of the previous file and stores it into the controller. The name of the backup file
is composed of the name of the battery profile being updated with an additional postfix
number.

The different use cases and related user interfaces are shown in the table below:

Use case User interface Note

Load a battery from PC Web All battery profile file names

have the prefix “BP_LA”,
“BP_NC” or “BP_LA”. If the
loaded file has the prefix LA_
or LI_, the controller adds
BP_ automatically at the very
beginning

Select and activate a battery profile Web, Touch

UI, UIM

Deactivate a battery profile and Web, Touch

activate an another one UI, UIM

Revert battery parameter changes in Web, Touch

active setup by reactivating a battery UI, UIM
profile

Update the battery parameters in Web, Touch

active setup to the active battery UI, UIM
profile

Delete a battery profile Web It is not possible to delete an

activated battery profile

Save a battery profile to PC Web It is not possible to save a

not synchronized profile to
PC

Configuration instructions, ORION controller Configuration 29

 The applicable menu points are shown in the table below:

Interface Menu point

Web Configuration → Battery → Profiles

Touch UI Menu → Battery → Battery Profiles

UIM Configuration → Battery → Profile

2.2.3 Configuring and enabling of battery strings

ORION is usually configured to use all the battery shunts that are installed in the system.
However, if all the battery connections are not needed, the unused battery strings can be
disabled to eliminate the non-relevant information on the user interface.

For the correct operation, ORION needs to know what kind of batteries are connected to
each string. For the optimum charging control, ORION needs to know the maximum
allowed charging current for the battery, and to estimate the state of charge, the expected
backup time and the remaining discharge time, ORION needs to know the battery
capacity.

Common Parameters Explanation

Hour Rating The nominal discharge time for the battery that
corresponds to the nominal capacity.

Peukert’s Exponent ORION uses Peukert’s model to estimate the available

capacity at different discharge rates. The Peukert’s
exponent is used as a parameter in this computation
model, and it influences to the accuracy of the SoC and
the remaining discharge time estimate.

Please do not change the default value unless you

know the correct parameter for the used battery.

Enable Battery Charging Checkbox to enable the charging current limit function
Current Limit

String Parameters Explanation

Max Ibatt Maximum allowed charging current, in amps or as a

percentage of the nominal capacity, depending on the
configuration

Capacity Nominal capacity of the battery that is connected to this

string/shunt

Enable Checkbox to enable a string.

An unused battery string can be disable to remove the
irrelevant information from the user interface.

30 Configuration instructions, ORION controller Configuration

 Interface Menu point

Web Configuration → Battery → String Settings

Touch UI Menu → Battery → Battery Strings

UIM Configuration → Battery → Batt Parameter

2.2.4 Float charge

After a battery has been fully charged, a slightly lower charge can be constantly applied
to compensate for self-discharge. This is the float charge. The parameters which affect
the usage of the float charge are described in Table 2.

Parameter Explanation

Usys@Tnom Voltage to regulate to at Nominal Temperature. If

temperature compensation is used, this voltage is
variable.

Nominal Temperature This is the battery operation nominal temperature. This

is used for the temperature compensation.

Voltage Within Ufloat± Deviation from float temperature compensated float

voltage. When voltage deviation is within limits, the
voltage returns to Float Charge.

Max Recharge Duration Maximum allowed time for recharge, after which the
voltage returns to Float Charge.

Table 2. Battery float charge configuration parameters

The applicable menu points are shown in the table below:

Interface Menu point

Web Configuration → Battery → Float Charge

Touch UI Menu → Battery → Float Charge

UIM Configuration → Battery → Float

Table 3. Menu points for the Float Charge setting parameters

2.2.5 Temperature compensation

The temperature compensation reduces the system voltage at high battery temperatures.
This function requires at least one temperature sensor into one of the battery racks. In
case of several temperature sensors, only the one returning the highest temperature will
be considered for compensation. This temperature is shown on the Home page and
available as a measurement called “Tbattmax”.

Configuration instructions, ORION controller Configuration 31

 While the temperature compensation is active, the status message on the home page will
be “active”, the event “S TComp Active” is true and the symbol “TC” is shown on LCD.
Active state means that the system voltage is not at the nominal setting point because of
the temperature compensation algorithm.

Two types of compensation are available: Linear and Multi-Stage. Additionally ORION
provides functionality for thermal runaway protection.

2.2.5.1 Linear mode

Linear mode is defined by four operating parameters:

Parameter Explanation

Slope Temperature compensation coefficient

Start Temp Temperature compensation limit, low temperature

Stop Temp Temperature compensation limit, high temperature

Max Voltage Maximum level where the temperature compensation

can increase the voltage

Table 4. Linear mode temperature compensation configuration parameters

2.2.5.2 Multi-stage

Type multi-stage is used when different slope is required at low and high temperatures.

The operation is defined by six operating parameters:

Parameter Explanation

Low Stop Voltage Maximum level where the temperature compensation

can increase the voltage at low temperature

Low Start Temp Temperature compensation limit, low temperature

Low Temp Slope Temperature compensation coefficient at low

temperatures

High Start Temp Temperature compensation starts at this temperature

High Temp Slope Temperature compensation coefficient at high

temperatures

High Stop Voltage Minimum level where the temperature compensation can
increase the voltage at high temperature

Table 5. Multi-stage temperature compensation configuration parameters

32 Configuration instructions, ORION controller Configuration

 Low Stop Voltage

High Stop Voltage

Runaway Voltage

Low Start High Start Runaway

Temp Temp Temp

2.2.5.3 Thermal runaway protection

The operation is defined by two operating parameters:

Parameter Explanation

Runaway Temp The temperature at which the controller will activate the
thermal runaway prevention feature by lowering the
output voltage to the Runaway Voltage parameter

Runaway Voltage The voltage to which the controller will immediately

lower the output voltage if the Battery temperature
exceeds the Runaway Temp parameter

Table 6. Thermal runaway protection configuration parameters

2.2.5.4 Making the settings

The parameters can be set at the following menu points:

Interface Menu point

Web Configuration → Battery → Temperature Compensation

Touch UI Menu → Battery → Float Charge

UIM Configuration → Battery → Temp Compensation

Note! The temperature compensation type can be set only via web interface.

Configuration instructions, ORION controller Configuration 33

2.2.6 Equalize

With flooded lead-acid batteries, it is possible to continue charging the batteries after they
are normally considered fully charged. This equalizes the voltages between battery cells
and stirs up the fluids within batteries, extending the battery life. This function is called
Battery Equalize. The parameters and settings which ensure that the procedure is carried
out safely and within certain limitations are described in Table 7.

Caution! Always check the battery specifications and instructions from the
battery manufacturer before setting the parameters.

Parameter Explanation

Voltage Battery Equalize voltage. Battery Equalize uses the

same settings for temperature compensation as for float
charge.

Duration Specifies the duration of the Battery Equalize charging

process.

Use Battery Room Fan To enable lead and lag time, select this checkbox.

Lead Time (Fan) Lead time for S BatteryFan event.

Time Lag (Fan) Time lag for S BatteryFan event.

Max Battery Temperature To supervise the battery temperature and stop Battery
Equalize if the battery temperature exceeds the following
limit, select this checkbox.

Max Battery Temperature If the battery temperature exceeds this value, the
charging process is stopped.

Alarm Suppression Voltage Deviation from float voltage to stop the alarm
suppression.

Alarm Suppression Time Maximum delay for S EqinProgress event.

Interval (Start Condition) Specifies the time between two battery charging
processes.

Start window Within this time window, a programmed Battery Equalize

can be started.

Inhibit after Boost (Start Minimum time between boost charge and Battery
Condition) Equalize.

Forbidden Periods During the given time windows, the programmed Battery
Equalize is not executed.

Forbidden Weekday At the selected weekdays, a programmed Battery

Equalize is not started.

Table 7. Battery equalize parameters

The Equalize Charge can be configured at the following menu points:

34 Configuration instructions, ORION controller Configuration

 Interface Menu point

Web Configuration → Battery → Equalize

Touch UI Menu → Battery → Equalize

UIM Configuration → Battery → Equalize

Configuration instructions, ORION controller Configuration 35

2.2.7 Boost charge

The battery can be boost charged automatically after a mains failure. With this procedure,
the system voltage is increased to a certain level to recharge the batteries faster. The
charging process is either controlled by time, current or energy depending on the
configuration.

Caution! Always check the battery specifications and instructions from the
battery manufacturer before setting the parameters.

Parameter Boost Charge Explanation

based on

Voltage All Boost Charge voltage. Boost Charge uses

the same settings for temperature
compensation as for float charge.

Istart Current Battery current value at which Boost Charge

starts. The setting is entered as amperes or
as a percentage of the nominal capacity
depending on the selected boost charge type

Istop Current Battery current value at which Boost Charge

stops. The setting is entered as amperes or
as a percentage of the nominal capacity
depending on the selected boost charge type

Factor (k) Time Factor (k) to calculate the Boost Charge

duration.

Factor (q) Energy Factor (q) to calculate the capacity to

recharge into the battery.

Uboostlow Time Limit to calculate the discharge duration.

Max Duration All Maximum allowed time for Boost Charge, to

prevent continuous charging of the battery.

Inhibit Time All Minimal time after last boost stop.

Inhibit Event All Event to block and stop boost charge.

SoC below All The boost charge starts only in case the
actual state of charge is equal or below the
entered threshold

Use Battery Room All To delay the battery fan event select this
Fan checkbox.

Time Lag (Fan) All Time lag for S BatteryFan event.

Max Battery All If the battery temperature exceeds this limit,

Temperature the boost process stops.

Alarm Suppression All Deviation from float voltage to stop the alarm
Voltage suppression.

36 Configuration instructions, ORION controller Configuration

 Alarm Suppression All Maximum delay for S BcinProgress event.
Time

Table 8. Battery boost charge parameters

The Boost Charge can be configured at the following menu points:

Interface Menu point

Web Configuration → Battery → Boost Charge

Touch UI Menu → Battery → Boost Charge

UIM Configuration → Battery → Boost

Configuration instructions, ORION controller Configuration 37

2.2.8 Lithium battery handling

ORION controller is able to communicate with lithium batteries over a digital bus. ORION
Touch supports two different concepts: 1) The lithium batteries are connected to ORION
via gateway module GWM-Battery. This module supports CAN and RS485/Modbus
communication and up to 16 batteries 2) The lithium batteries are connected to RS485
port of ORION Touch. The maximum number of batteries is 32.

2.2.8.1 Connecting a lithium-ion battery to ORION Touch via a GWM-Battery

module

Precondition:
1 The gateway module GWM-Battery is connected to the system and configured
properly.
2 The GWM module has a firmware that supports the used battery
3 The communication bus of the battery is connected to the gateway module.

Use the following procedure to add a new lithium-ion battery to the system.

2.2.8.1.1 Web user interface

Step 1 Go to Configuration → Battery → Lithium

Step 2 In Overview section, select the gateway module from the “Battery Interface”
drop-down list and click “Add”.

Step 3 Tick the “Enable” checkbox for the new battery.

Step 4 Optionally edit the battery name and select the fuse fault event to be shown
together with this battery on the Status page.

Step 5 Click “Accept Changes”

Step 6 In case the system is equipped with battery shunt(s) for battery current
measurement, go to Configuration → Battery → String Settings and enable the
shunt measurements and enable and set the total battery charging current limit.

2.2.8.1.2 UIT interface

It is possible to enable/disable batteries via local interface, but it is not possible to add
new ones.

Step 1 Go to BATTERY → Lithium Batteries

Step 2 Select the new battery and enable it.

2.2.8.2 Replacing a lithium-ion battery

Step 1 Disconnect the communication bus cable from the battery to be replaced.

Step 2 Set the old battery’s address to new battery and connect the bus cable. The
status of the battery should change to “ok”.

38 Configuration instructions, ORION controller Configuration

 Step 3 Go to Configuration → Battery → Lithium and set the installation date for the
new battery

2.2.8.3 Removing a lithium-ion battery

2.2.8.3.1 Web user interface

Step 1 Disconnect the communication bus cable from the battery to be removed.

Step 2 Go to Configuration → Battery → Lithium. The status of the battery should be

“missing”.

Step 3 Press the button on GWM-BATTERY to clear the disconnected battery from the
GWM-BATTERY ID table.

Step 4 Deselect the “Enable” checkbox for the removed battery.

2.2.8.3.2 UIT interface

Step 1 Go to BATTERY → Lithium Batteries

Step 2 Select the battery and disable it.

2.2.8.4 Connecting a lithium-ion battery to an RS485 port of ORION Touch

2.2.8.4.1 Web user interface

Step 1 Go to Configuration → File Manager and load in the “Lithium Battery Driver” file
that is compatible with the used battery type. It is possible to load in multiple
drivers to be prepared for different battery alternatives.

Step 2 Go to Configuration → Battery → Lithium and click “Add” in the “Battery Group”
section, enter the name for the new group, select the interface (serial port) and
select the driver. It is also possible to select “auto detect” to enable automatic
detection of the battery type.
There is also a button on this page to load in the battery drivers.

Step 3 Connect the battery to the RS485 port of ORION. ORION will detect the battery
and set the actual date as installation date.

Step 4 Go to Configuration → Battery → Lithium and confirm the new battery by ticking
the Enable checkbox in the “Overview” section. The status should change from
“New” to “OK”

Step 5 Optionally edit the battery name and select the fuse fault event to be shown
together with this battery on the Status page.

Step 6 In case the system is equipped with a battery shunt for battery current
measurement, go to Configuration → Battery → String Settings and enable the
shunt measurements and enable and set the total battery charging current limit.

2.2.8.4.2 UIT interface

Configuration instructions, ORION controller Configuration 39
 It is possible to enable/disable batteries via local interface, but it is not possible to add
new ones.

Step 1 Go to BATTERY → Lithium Batteries

Step 2 Select the new battery and enable it.

2.2.8.5 Replacing a lithium-ion battery

Step 1 Disconnect the communication bus cable from the battery to be replaced.

Step 2 Set the old battery’s address to new battery and connect the bus cable. The
status of the battery should change to “ok”.

Step 1 Go to Configuration → Battery → Lithium and set the installation date for the
new battery.

2.2.8.6 Removing a lithium-ion battery

2.2.8.6.1 Web user interface

Step 1 Disconnect the communication bus cable from the battery to be removed.

Step 2 Go to Configuration → Battery → Lithium. The status of the battery should be

“missing”.

Step 3 Deselect the “Enable” checkbox for the removed battery.

2.2.8.6.2 UIT interface

Step 3 Go to BATTERY → Lithium Batteries

Step 4 Select the new battery and disable it .

2.2.9 Hybrid battery management

ORION is able to manage the charging of lead acid and lithium batteries in the same
system. However, this requires specific system design with special transfer switches for
the batteries. The configuration of this functionality is not covered by this document.
Please contact Delta in case more information is needed.

40 Configuration instructions, ORION controller Configuration

2.3 Battery supervision
To recognize damages to the battery at an early stage, ORION provides different
methods to monitor the state of the batteries connected to the system.

2.3.1 System voltage supervision

The system voltage supervision function monitors the battery voltage and activates
events if the voltage exceeds the given limits.

S Ua high

Ua max
S Us high
Us max

Usys tc

Us min

S Us low
Ua min

S Ua low

Tbatt
Tc_low 20°C Tc_high

Figure 1. The behaviour of the system voltage supervision

Parameter Explanation

Ua max Upper limit for system alarm voltage. If system voltage

rises above this value the event S Ua high is activated.
Not temperature compensated.

Ua min Upper limit for system alarm voltage. If system voltage

falls below this value the event S Ua low is activated.
Not temperature compensated.

Us max Upper limit for system safety voltage. If system voltage

rises above this value the event S Us high is activated.
Temperature compensation optional.

Us min Upper limit for system safety voltage. If system voltage

falls below this value the event S Us low is activated.
Temperature compensation optional.

BoD S Battery on Discharge event is activated when the

system voltage falls below threshold “BoD”
Not temperature compensated.

Configuration instructions, ORION controller Configuration 41

 Hysteresis Difference between the activated and deactivated level
for the events.

Suppress S Us low during If this checkbox is activated the event S Us low is

mains failure suppressed during mains failure. *

Suppress S Ua low during If this checkbox is activated the event S Ua low is

mains failure suppressed during mains failure. *

Temperature compensation Checkbox to enable the automatic temperature

for Us min and Us max compensation for the Us thresholds (Us min, Us max)

* Events already activated remain active until the system voltage exceeds the
corresponding limit, regardless of these settings.

Table 9. System voltage supervision parameters

The System voltage supervision can be configured at the following menu points:

Interface Menu point

Web Configuration → Battery → System Voltage Supervision

Touch UI Menu → Battery → Sys. Volt. Supervision

UIM Configuration → Battery → Usys Supervi.

42 Configuration instructions, ORION controller Configuration

2.3.2 Middle point measurement

For the middle point measurement, the battery is divided into two blocks. The voltage of
the middle point is measured and compared with the calculated middle point value
computed out of the battery voltage value “Ubatt”. If the difference exceeds a given limit,
the battery is considered as faulty. The battery middle point voltage can be measured by
UM or Fuse inputs of ORION or through SENSN devices.

When the voltage difference exceeds the given limit for at least 20s, a log entry is
generated and the events S MP Failure and S BattFail MP are activated. The event
S MP Failure stays active as long as the voltage difference is too high. The event
S BattFail MP remains active until it is manually reset.

Parameter Explanation

Enable Checkbox. Enables battery middle point measurement.

To use this functionality, a battery string configuration
that supports middle point measurement must be
selected.

Number of Cells Total number of cells.

Note! Accessible only via web interface.

Measure Point Number of cells below the measuring point.

Note! Accessible only via web interface.

Udiff charge Maximum accepted voltage difference during float

equalize or boost.

Udiff discharge Maximum accepted voltage difference during discharge

or battery test.

Table 10. Middle point measurement parameters

The parameter setting and the results of the middle point measurements are available
through the Touch UI/UIM interface as well as the web user interface.

Interface Menu point

Web Configuration → Battery → Middle Point Measurement

Touch UI Menu → Battery → Middle Point Meas.

UIM Configuration → Battery → Middle Point

To check the middle point measurement status (or reset) go to:

Interface Menu point

Web Status → Battery → Middle Point Measurement

Touch UI Menu → Battery → Middle Point Meas.

UIM Status → Battery → Middle Point

Configuration instructions, ORION controller Configuration 43

2.3.3 Block voltage measurement

For the block measurement, the battery is divided into equally sized voltage blocks, which
are measured separately. These voltages are compared against the theoretical block
voltage calculated from the system voltage. If the difference exceeds a given limit, the
battery presents a symmetry failure and is considered as faulty.

Parameter Description

Enable Checkbox to enable battery block measurement.

Udiff charge Maximum accepted voltage difference during float,

equalize or boost.

Udiff discharge Maximally accepted voltage difference during discharge

or battery test.

Block Voltage Nominal voltage between two voltage tabs.

Note! Accessible only via web interface.

Table 11. Block voltage measurement parameters

The parameter setting and the results of the Block voltage measurements are available
through the Touch UI/UIM interface as well as the web user interface.

Interface Menu point

Web Configuration → Battery → Block Measurement

Touch UI Menu → Battery → Block Measurements

UIM Configuration → Battery → Block

To check the Block voltage measurement status (or reset) go to:

Interface Menu point

Web Status → Battery → Block Measurement

Touch UI Menu → Battery → Block Measurements

UIM Status → Battery → Block

44 Configuration instructions, ORION controller Configuration

2.3.4 Temperature supervision

2.3.4.1 Temperature difference (Tdiff)

Tdiff is the difference between battery temperature and ambient temperature. The
comparison is made continuously. If the two temperatures differ more than a certain value
for more than 2 minutes, a log entry is generated and the events S Tdiff Failure and
S BattFail T are activated. The event S Tdiff Failure remains active as long as the
temperature difference is too high. The event S BattFail T remains active until it is
manually reset.

The following information about the Tdiff measurement is displayed:

Parameter Explanation

Tdiff Current temperature difference between ambient and

battery temperature.

Status Status of the “Tdiff” measurement. The following terms

are possible: inactive, ok, occurred, fail.

Failure Event State of the event S BattFail T. The following terms are
possible: ok, active.
The event can be reset manually.

Table 1. Temperature difference measurement parameters

2.3.4.2 High temperature alarm

S High Battery Temp event is activated when the highest battery temperature
measurement exceeds the” High Temp” threshold.
S High Battery Temp event is deactivated when the highest battery temperature
measurement falls below “High Temp” threshold minus” High Temp hysteresis”.

2.3.4.3 Temperature supervision parameters

The user can configure the following parameters:

Parameter Explanation

Enable Tdiff Checkbox to enable Tdiff measurement.

Tdiff max Maximum acceptable temperature difference.

Tamb Input for ambient temperature. A temperature

measurement has to be assigned to this input.

High Temp Threshold for High Temperature alarm

High Temp hysteresis Hysteresis for the threshold

Table 2. Temperature supervision parameters

Configuration instructions, ORION controller Configuration 45

 The parameters can be set through the following menu points:

Interface Menu point

Web Configuration → Battery → Temperature Supervision

Touch UI Menu → Battery → Tdiff

Menu → Battery → Temp. Supervision

UIM Configuration → Battery → Temp Supervision

The status can be seet at:

Interface Menu point

Web Status → Battery → Temperature Supervision

Touch UI Menu → Battery → Tdiff

Menu → Battery → Temp. Supervision

UIM Status → Battery → Temp Supervision

46 Configuration instructions, ORION controller Configuration

2.3.5 Current difference (Idiff)

The Current difference (Idiff) measurement calculates the deviation from the calculated
current for each battery string. The calculation assumes that the total battery current is
shared by the strings based on the nominal capacities. A current difference higher than
the given limit can indicate a faulty battery. Idiff is monitored during charge and discharge
of the batteries. The threshold values for charging and discharging are independent of
each other.

If the current difference exceeds the threshold for more than 20 seconds, a log entry is
generated and events S Idiff Failure and S BattFail I are activated. The event S Idiff
Failure remains active, as long as the current difference is too high. The event S BattFail
I remains active until it is manually reset.

Parameter Explanation

Enable Checkbox. Enables Idiff measurement.

Idiffmax charge Allowed percentage of deviation during charge.

Idiffmax discharge Allowed percentage of deviation during discharge.

Table 3. Current difference parameters

The available information about the Idiff measurement is shown in Table 4:

Parameter Explanation

Idiff Highest deviation between a battery string current and

calculated average of all battery string currents.

Status Status of the “Idiff” measurement. The following terms

are possible: inactive, ok, occurred, fail.

Failure Event State of the event S BattFail I. The following terms are
possible: ok, active.
The event can be reset manually.

Table 4. Current difference measurement parameters

The parameters can be set through the following menu points:

Interface Menu point

Web Configuration → Battery → Idiff Measurement

Touch UI Menu → Battery → Idiff

UIM Configuration → Battery → Idiff

The status can be seet at:

Configuration instructions, ORION controller Configuration 47

 Interface Menu point

Web Status → Battery → Idiff Measurement

Touch UI Menu → Battery → Idiff

UIM Status → Battery → Idiff

48 Configuration instructions, ORION controller Configuration

2.3.6 Loss of backup time

The Loss of the Backup Time function provides an early warning in event an installed
battery does not provide the expected back-up time. Based on the set value for the
expected backup time and the calculated effective capacity, the ORION calculates a
corresponding maximum discharge current. For li-on batteries the calculation is done
based on nominal capacity. If the average load current during a period, which is equal to
the backup time, exceeds this calculated value the event S Backup Time Lost is
activated. This event remains active until the average load current is within the required
range and the operator has manually reset it.

Parameter Explanation

Enable Checkbox to enable the “Monitoring Loss of Backup

Time” function.

Expected Backup Time The expected backup time.

Table 5. Loss of backup time parameters

Parameter Explanation

Status Status of the “Monitoring Loss of Backup Time”. The

following terms are possible: inactive, not ok and ok.

Estimated Backup Time The estimated backup time.

Table 6. Loss of backup time results

The parameters can be set through the following menu points:

Interface Menu point

Web Configuration → Battery → Loss of Backup Time

Touch UI Menu → Battery → Loss of Backup Time

UIM Configuration → Battery → Backup Time

The status can be seet at:

Interface Menu point

Web Status → Battery → Loss of Backup Time

Touch UI Menu → Battery → Loss of Backup Time

UIM Control → Battery → Backup Time

Configuration instructions, ORION controller Configuration 49

2.3.7 Low Voltage Disconnection of the battery

The low voltage disconnection (LVD) function protects the battery from a deep discharge.
ORION supports two different LVD types:

U and t controlled LVD compares Usys to a voltage threshold. In case the voltage
falls below the threshold, ORION activates an event that drives the relay of the
battery disconnect. The disconnection can be delayed with an adjustable
parameter. The battery is disconnected from the load until the system voltage Usys
rises back to acceptable values.

Event Controlled LVD disconnects the battery based on the status of a control
event which is defined in the Signal Processing Engine.

Low Voltage Disconnection can only be configured through the web user interface and it
is normally configured at the Delta factory.

The parameters for U and t controlled LVD can be adjusted at:

Interface Menu point

Web Configuration → System Architecture → LVD

Touch UI Menu → LVD

UIM Configuration → Battery → LVD

The parameters for Event controlled LVD depend of the configured logic and can be
adjusted at:

Interface Menu point

Web Configuration → Signal Processing Engine

Touch UI Menu → LVD

UIM Configuration → Battery → LVD

The state of the LVD can be seen and the functionality can be disabled at:

Interface Menu point

Web Control → LVD

Touch UI Menu → Events → Event Thresholds

UIM Configuration → Event → Thresholds

50 Configuration instructions, ORION controller Configuration

2.3.8 Partial Load Disconnection (PLD)

The partial load disconnection function is used to prioritize separate load strings (for
example, difference types of equipment) during mains failure and battery discharge.

The PLD functionality is configured by using the LVD functionality of ORION, so for more
details, please see the previous chapter.

Configuration instructions, ORION controller Configuration 51

2.3.9 Battery test

ORION offers different procedures to check the state of the batteries. The user can select
between constant current and real load battery tests, depending on the system size and
the load conditions.

The Constant Current battery test discharges the battery with a constant current during
a certain time period. Load changes are balanced by the rectifiers. For a successful test,
the load current must be greater than the desired battery discharge current.

During the Real Load battery test, the battery is being discharged with the real load
current. To make the testing saf,e the rectifier output voltage is programmed to Usupport
voltage leve,l but the rectifiers remain in operation ready to support the load in case the
battery would fail.

It is possible to configure several tests. One test could be a short check that is done every
month and the second test could be a longer test that is done only oncew or twice a year.

2.3.9.1 The battery test parameters

The battery test is configured by the following parameters:

Parameter Test type Explanation

Type Selection of the test type

Name Both Name of the test instance

Usupport Both Support charge voltage for the battery.

Idischarge Const. Current Battery discharge current.

Duration Both Battery test duration.

Minimal Duration Both The value represents the minimum battery test
duration in minutes. During that time a battery
test is not stopped if a voltage is below the
support voltage or a current difference is higher
than the specified value.

Enable Natural Both When enabled, ORION considers every long

Battery Test enough discharge cycle a battery test. See the
following two parameters.

Voltage Level Both Voltage threshold for the Natural Battery Test

Monitoring Period Both Monitoring period for the Natural Battery Test

Battery Both A programmed battery test is executed only, if

Temperature the battery temperature is within this range.

Enable Auto Start Both Automatic start of the battery test at specified
intervals.

Voltage within Both To ensure that the battery is fully charged the
Ufloat system voltage must not differ for a certain time

52 Configuration instructions, ORION controller Configuration

 from the float voltage before the battery test.

Interval Both Minimal time between programmed battery

tests. To enable the programmed battery test
select the “Enable AutoStart” checkbox in the
Battery Test Parameter dialog (or select “Yes” in
the local display).
After a manually started battery test the
measurement of the interval restarts.

Start Time Between Both Within this time window, a programmed battery
And test can be started.

Inhibit input Both Battery test does not start while this event is
active.

Forbidden periods Both During the given time windows, the

programmed battery test is not executed.

Forbidden weekday Both At the selected weekdays a programmed

battery test is not started.

The parameters can be configured at:

Interface Menu point Note

Web Configuration → Battery → Battery Test

Touch UI Menu → Battery → Battery Tests Not all

parameters

UIM Configuration → Battery → Battery Test Not all

Configuration → Battery → Natural Test parameters

The test can be manually started at:

Interface Menu point

Web Configuration → Battery → Battery Test

Touch UI Menu → Battery → Battery Tests

UIM Control → Battery → Battery Test

The status and the results of the previous tests can be seen at:

Interface Menu point

Web Status → Battery → Battery Test

Touch UI Menu → Battery → Battery Tests

UIM Status → Battery → Battery Test

Configuration instructions, ORION controller Configuration 53

2.3.10 Separate charge and discharge

For maintenance of the system, a battery can be separated from the system; then be
discharged with a separate load and finally be recharging with separated rectifiers while
the system is running normally with the remaining battery or batteries.

There are two types of separate charge in the ORION: manual and semi-automatic.

With the manual separate charge and discharge, the separated battery is fully charged
before it is reconnected to the system. The float voltage for the separated battery can be
set to a value different from the system float voltage (=> boost voltage). After the battery
is fully charged, the float voltage is set to the same value as the system float voltage (or
lower). After the voltage of the separated battery has settled to the system voltage, the
battery can be reconnected to the system.

With the semi-automatic separate charge and discharge, the system voltage is reduced to
reconnect voltage “Urecon” during separate charging. After the voltage of the separated
battery has reached the system voltage, the system voltage tracks the separate charging
voltage for a short time and then the battery can be reconnected to the system. The
battery is then charged up to the system float voltage.

During separate charge mode, battery fuse alarms and Idiff measurement are
suppressed.

Parameter Explanation

Charge Voltage Charge voltage.

Reconnect Voltage Only with semi-automatic separate charge/discharge!

During the charge phase, the ORION reduces the
voltage of the remaining system to this value.

Max Ibatt Maximum charge current for separate battery.

Enable Input Input to activate separate charge and discharge.

Active: separate charge and discharge
Inactive: normal charge state
An event must be assigned to this input.

Mode Select Input Input to select the mode.

Active: separate discharge
Inactive: separate charge
An event must be assigned to this input.

Table 7. Battery separate charge and discharge parameters

The parameters can be configured at:

Interface Menu point Note

Web Configuration → Battery → Separate Charge

Touch UI No config
access

54 Configuration instructions, ORION controller Configuration

 UIM No config
access

The status can be seen at:

Interface Menu point

Web Configuration → Battery → Separate Charge

Touch UI Menu → Battery → Separate Charge

UIM Status → Battery → Sep Charge

Configuration instructions, ORION controller Configuration 55

2.3.11 Battery life prediction

The typical lead acid batteries for telecom applications are designed to last 10 years in
optimal environmental conditions. However, if the temperature is higher than the nominal
temperature, typically 20 °C or 25 °C, the life time will be shorter. Also, if the battery is
frequently discharged and recharged, it may limit the battery life.

The battery life prediction function gives information on the expected life time of the
battery in the actual operating conditions and helps in budgeting and planning battery
replacements.

In case the battery prediction time function is activated in a system with an old battery,
the Installation Date must be set according to the real installation date of the battery. As
the real history is not known by ORION, ORION just assumes that the average conditions
in the past were the same as they have been after activating the monitoring functionality.

Parameter Explanation

Enable Enable function “Battery Life Prediction”.

Design Life Design life of the battery.

Below Nominal temperature of the battery.

Expected Cycles @ 50 % Expected number of cycles at 50 % depth of discharge

DoD (DoD).

Remaining Days Notification Notification’s threshold for “S Life Prediction Failure”

event.

Activation Date The activation date of life prediction function.

It will be set to current date when enabling life prediction
if it has never been set before, or when pressing the
Reset button

Installation Date The real installation date of battery.

It will be set to the same with Activation Date
automatically if it has never been set before.
The Installation Date must be earlier or the same as
Activation Date

Table 8. Battery life prediction parameters

Some Li-on batteries have built in intelligence to indicate the State of Health with a scale
from zero to 100 %. When available, ORION uses this information to predict the lifetime
instead of external measurements of temperature and discharge cycles.

The applicable menu points are:

Interface Menu point Activity

Web Configuration → Battery → Life Prediction Setting the parameters

Resetting the Activation Date
Setting the Installation Date

56 Configuration instructions, ORION controller Configuration

 Seeing the status and
resetting the fail event

Touch UI Menu → Battery → Life Prediction Setting the parameters

Reseting the installation date
Seeing the status and
resetting the fail event

UIM Configuration → Battery → Life Prediction Setting the parameters

Control → Life Prediction → Installation Resetting the installation date

Control → Life Prediction → Fail Event Seeing the status and

resetting the fail event

Status → Battery → Life Prediction Seeing the remaining days

2.3.12 State of charge and remaining backup time estimation

ORION monitors the battery current continuously and estimates the State of Charge
(SoC). The SoC measurement is shown using a scale from 0 to 100%. SoC can be used
in signal processing and it can be assigned to a data log.

Based on the battery SoC and the actual load current, ORION estimates the Remaining
Backup Time. This measurement tells how long the system could still run on batteries
until they are fully discharged. The Remaining Backup Time measurement is dynamic.
Therefore the measurement will increase and decrease in case the lod current varies.

Note! SoC and Remaining Backup Time are estimates and shall not be
understood as an accurate measurements.

Configuration instructions, ORION controller Configuration 57

2.4 Configuring load string monitoring
ORION monitors each load string and triggers an event S Load String Overload in case
any of the string current exceeds the configurable threshold. The threshold is defined as
a percentage of the nominal string current. The automatically generated log entry
contains also the name of the overloaded string.

Parameter Explanation

Inom Nominal current of the string.

Imax Threshold for the Overload event defined as a

percentage of Inom

Table 9. Load string monitoring parameters

The load strings can be enabled and the parameters can be configured at:

Interface Menu point Note

Web Configuration → Load → String Settings

Touch UI Menu → Load → Load Strings

UIM Configuration → Load → Load Parameter

58 Configuration instructions, ORION controller Configuration

2.5 Configuring rectifiers

2.5.1 Overview of configuring rectifiers

The ORION offers a comprehensive set of functions to control and monitor different
rectifiers, enabling the user to adjust the behaviour of the rectifiers to meet the specific
requirements of the battery and load.

The following instructions describe the main functions from the ORION point of view.

2.5.2 Rectifier parameters

After communication is first established between the rectifiers and the controller, it is
possible to adjust the parameters with the controller. Without initial communication to the
power system controller, Delta’s rectifiers use their own default parameters. With the
controller the user can also adjust the default parameters, after the communication is first
established. The following parameters control the behaviour of the rectifiers when the
power system is not in normal operating mode, such as start-up or low input voltage
mode. The parameters for normal operating mode (float charge mode), and for the whole
power system, are adjusted elsewhere (for example, battery menu).

These parameters can only be viewed or configured through the web user interface.

Parameter Explanation

Rectifier type Selection of the rectifier type, for example rectifier

DPR 2400B-48.

Table 10. Selection

Parameter Explanation

Voltage Output voltage of the rectifiers

Current limit Current limit of the rectifiers

Power limit Power limit of the rectifiers

Table 11. Default parameters (in use when no connection to the ORION)

Parameter Explanation

Input low off Threshold (voltage) for shutting down the rectifiers when
input voltage is too low.

Input low on Threshold (voltage) for switching the rectifiers on, when
input voltage returns from low to acceptable values.

Configuration instructions, ORION controller Configuration 59

 Input high on Threshold (voltage) for switching the rectifiers on, when
input voltage returns from high to acceptable values.

Input high off Threshold (voltage) for shutting down the rectifiers when
input voltage is too high.

Table 12. Input voltage limits

Parameter Explanation

Voltage Start-up voltage for the rectifiers

Current limit Start-up current limit for the rectifiers

Power limit Start-up power limit for the rectifiers

Limit time The duration of the start-up parameters. After this

period, the normal parameters (float charge voltage and
so on) are taken into use.

Table 13. Start-up parameters

Parameter Explanation

Power Up Delay The delay in seconds, after which the first rectifier in the
group/system starts.

Power Up Time (Rectifier SW V1.xx): The total power-up time in

seconds, during which all rectifiers in the group/system
are started. ORION divides this time by the number of
rectifiers and starts each rectifier one by one with the
calculated delay.

Power up time (Rectifier SW V2.00 and higher): After power up delay,

all rectifiers start simultaneously delivering power. The
power limitation rises linearly from zero to the nominal
power during power up time.

Table 14. Sequential start-up / Ramp-up power start

Parameter Explanation

Umax off DC Voltage threshold to shut down rectifier.

Note: The maximum setting for Umax off is 62V.

However, the real upper limit can be different depending
on the selected rectifier type. If this is lower than the
ORION setting, the rectifier uses the internally defined
maximum value.

Table 15. Overvoltage protection parameter

The parameters can be configured at:

60 Configuration instructions, ORION controller Configuration

 Interface Menu point Note

Web Configuration → Rectifier → Parameter

Touch UI Menu → Rectifier → Parameter

UIM Configuration → Rectifier → Parameter

Configuration instructions, ORION controller Configuration 61

2.5.3 Rectifier alarms

If a rectifier malfunctions or fails, the ORION raises a rectifier failure alarm:

S Non Urg RFA or S Urgent RFA.

A rectifier is considered as faulty if at least one of the following criteria is fulfilled:

 Rectifier shut down by over-temperature protection (OTP), over-voltage

protection (OVP) or air flow failure
 Internal failure

Note! Some rectifier modules are able to distinguish between fan

failure and other internal failure. When fan failure is detected ORION
activates an event S RM Fan Failure.

 Input voltage outside range (open MCB or faulty AC cabling)

 Load sharing error (voltage mode only)
 No communication between ORION and the rectifier module

Note! It is possible to separate communication failure from the rectifier

failure by unticking the check box “Include Com Fail in RFA”.

The urgency of an alarm (Non-Urgent or Urgent) can be adjusted with thresholds

provided by the ORION.

Parameter Explanation

Failures for Non-Urgent A threshold for number of failed rectifiers that activates a
Alarm Non-Urgent Alarm for rectifier failure
(internal event: S Non Urg RFA)

Failures for Urgent Alarm A threshold for number of failed rectifiers that activates
an Urgent Alarm for rectifier failure
(internal event: S Urg RFA)

Include Com Fail in RFA When ticked, communication failure is included in the
RFA. If not, then a communication failure activates an
event S RM Com Failure.

Acknowledge New Rectifiers If checkbox “Acknowledge New Rectifiers Automatically”

Automatically is ticked, the user does not need to press the button
“Acknowledge” new rectifiers. New modules will be
automatically detected and acknowledged by ORION.

Table 16. Rectifier setup parameters

Rectifier Alarm State Cause

S Non Urg RFA Number of faulty rectifiers ≥ Failures for Non-Urgent

62 Configuration instructions, ORION controller Configuration

 (Non-Urgent Rectifier Failure Alarm
Alarm) Number of working rectifiers → Number of configured
rectifiers
Number of working rectifiers ≤ Number of configured
rectifiers – Failures for Non-Urgent Alarm

S Urgent RFA Number of faulty rectifiers → Failures for Urgent Alarm

(Urgent Rectifier Failure Number of working rectifiers ≤ Number of configured
Alarm) rectifiers – Failures for Urgent Alarm

Table 17. Rectifier alarm state

Note! If the event “S Urgent RFA” is activated, the “S Non Urg RFA” is
suppressed. During a mains failure both rectifier alarm events “S Urgent RFA”
and “S Non Urg RFA” are suppressed.

The parameters can be configured at:

Interface Menu point Note

Web Configuration → Rectifier → Setup

Touch UI Menu → Rectifier → Setup

UIM Configuration → Rectifier → Setup → RM Number

Configuration instructions, ORION controller Configuration 63

2.5.4 Installing Rectifiers

After installing new rectifiers, the new number of modules must be manually confirmed for
ORION, unless the checkbox “Acknowledge New Rectifiers Automatically” is ticked.

2.5.4.1 Web user interface

Step 1 Go to Configuration → Rectifier → Setup.

Step 2 Click “Acknowledge”.

This dialogue summarizes the status of the whole rectifier system with numbers
for installed, working (ok) and faulty rectifiers.

After Acknowledgment, the “Rectifier installed” field shows the updated number;
“Rectifier new:” must be 0.

Step 3 To avoid unexpected behaviour of the system, verify that none of the rectifiers
show an error. Go to Status → Rectifier. The Rectifier dialogue displays the
status and configuration status of each rectifier.

Step 4 To identify each rectifier module, click “Show module”.

The “Com”-LED of the related rectifier module blinks for over a minute, to allow
the module to be physically located.

Step 5 To view more details about each rectifier module, click “Details”.

2.5.4.2 Touch UI interface

Step 1 Go to Menu → Rectifier → Setup.

Step 2 Go to “Number of RM” , enter the password and update the number of modules

or

Go to “New” and acknowledge the new modules

2.5.4.3 UIM interface

Step 3 Go to CONFIGURATION → RECTIFIER → SETUP.

Step 4 Go to “RM NUMBER” (requires password).

Increment “Number” by the number of added rectifiers

or

Go to “RM NEW”.

64 Configuration instructions, ORION controller Configuration

 The number of added modules is shown and “Acknowledge” is highlighted.

Step 5 Press Enter and confirm again.

2.5.5 Removing rectifiers

After removal of rectifiers, the new number of modules must be confirmed for the ORION.
If this is not done within a certain time a non-urgent alarm arises.

2.5.5.1 Web user interface

Step 1 Configuration → Rectifier → Setup.

Step 2 Click “Acknowledge”.

Step 3 Verify that no rectifiers show an error.

Go to Status → Rectifier.

The Rectifier dialogue displays the status and configuration status of each
rectifier.

2.5.5.2 Touch UI interface

Step 1 Go to Menu → Rectifier → Setup.

Step 2 Go to “Number of RM” , enter the password and update the number of modules

or

Go to “Lost” and acknowledge the lost modules

2.5.5.3 UIM interface

Step 1 Go to CONFIGURATION → RECTIFIER → SETUP.

Step 2 Go to “RM NUMBER” (requires password).

Decrease “Number” by the number of removed rectifiers

or

Go to “RM LOST”.

The number of removed modules is shown and “Acknowledge” is highlighted.

Step 3 Press Enter and confirm again.

Configuration instructions, ORION controller Configuration 65

2.5.6 Energy saving rectifier functions

Rectifiers can communicate with the ORION using advanced communication protocols.
This allows optimising system performance by controlling the rectifiers individually. The
ORION software currently supports an Efficiency Cycling to adapt the power supply to a
momentary load, which reduces power losses and increases the system efficiency. In
addition, with the Forced Rectifier Cycling, it is possible to avoid always using the same
rectifiers to feed power to the system.

2.5.6.1 Rectifier efficiency cycling

The Rectifier Efficiency Cycling allows to run only as many rectifiers as needed for an
optimum overall system performance for a momentary load. Several parameters are
required to specify how many rectifiers are allowed to be turned off and still be able to
react on instantly increasing power demand. The rectifiers that are turned off are cycled
to make sure they are operating correctly, even if ORION has turned them off.

When using the Efficiency Cycling on systems with phase assigned rectifiers (in AC
Measurement Type “Internal – single phase RM” or “Automatic 3-PH slot assignment”),
the load is actively balanced among the phases. With “Internal – single phase RM” mode
all the rectifiers must be manually assigned to phases in order to insure the correct
balance. If the system has unassigned rectifiers then they will be chosen first to be
stopped and last to be started. This condition is indicated by an event S RM Un-assigned.

In case ORION cannot keep the phase loading balanced (= difference is more than one
rectifier module) an event S RM Efficiency Unbalanced is activated.

Parameter Explanation

Enable Checkbox for enabling the function.

Limit Switching Times Limits the number of maximum “OFF” commands per
day and per rectifier.

Force Cycling Every To force the efficiency mode at least once per selected
period to change the rectifiers currently switched on and
off. Choose from “never”, “day” or “30 days”.

Sweet Spot Target Rectifier Loading in %

Minimum Power Reserve This value must be set according to the load
requirements. With batteries, this value is not as critical.
But without batteries, it must be set to a value that the
load change within a period “T” never exceeds the value.
Otherwise the system power cannot be guaranteed.

Minimum Rectifier Power Minimum amount of rectifier power that is always

available.
This value helps in case the system has no batteries.

Inhibit Input The efficiency mode can be temporarily disabled by an

event

Table 18. Rectifier efficiency cycling parameters

66 Configuration instructions, ORION controller Configuration

 The operating parameters can be configured at:

Interface Menu point Note

Web Configuration → Rectifier → Energy Saving

Touch UI Menu → Rectifier → Energy Saving

UIM Configuration → Rectifier → Eff Cycling

2.5.6.2 Event controlled standby

In some hybrid applications where sufficient energy is provided by alternative sources
(i.e. PVC) there is a possibility to save grid energy by switching off all rectifiers. This can
be triggered by an event defined by the user. If this feature is enabled and a Stanby
Input is active all rectifiers will be shut down.

Parameter Explanation

Enable Checkbox for enabling the function.

Standby Input Event input to activate Event Controlled Standby mode

Table 1. Rectifier efficiency cycling parameters

The parameters can be configured at:

Interface Menu point Note

Web Configuration → Rectifier → Energy Saving

Touch UI No access

UIM No access

Configuration instructions, ORION controller Configuration 67

2.5.7 Power limitation by event

Power Limitation by Event allows the possibility to save costs by using under-
dimensioned generator sets for power supply during mains outages. In this case the
generator supplies only a part of the power needed, while the battery delivers the rest.
The battery is partially discharged but the backup time can be extended. This is achieved
by decreasing the rectifier output power during genset operation.

There are two possibilities: “Fixed” or “Dynamic” rectifier power limitation.

While the chosen control event is active and the “Fixed” rectifier power limitation is
enabled, the controller limits the total rectifier power to the given threshold Max.
Total Rectifier Power. If the checkbox No Battery Discharge is marked, the
controller prevents discharging of the battery due to this rectifier power limitation
configuration.

While the chosen control event is active and the “Dynamic” rectifier power limitation
is enabled, the controller limits the total rectifier power in a way that the power
taken from the measured source does not exceed the threshold Max. Generator
Power independent if other AC loads are connected to the same source. If the
checkbox No Battery Discharge is marked, the controller prevents discharging of
the battery due to this rectifier power limitation configuration.

The functionality is configured by the following parameters:

Parameter Type Explanation

Type Selection of the type, Fixed or Dynamic

Enable Both Enabling of the function

Max Total Rectifier Fixed Maximum allowed output power from the
Power rectifier system

Max Generator Dynamic Maximum output power taken from the

Power generator

Measurement Dynamic The source measurement that is used for

controlling the rectifier power

Activate Input Both Event to activate the functionality

No Battery Fixed Checkbox to prevent discharging of the battery

Discharge due to this rectifier power limitation
configuration.

The parameters can be configured at:

Interface Menu point Note

Web Configuration → Rectifier → Power Limitation by Event

Touch UI No access

UIM No access

68 Configuration instructions, ORION controller Configuration

2.5.8 Recharge power supervision

The controller monitors the power demand and reacts if the system is unable to recharge
the battery within the expected time. This happens, for example, if additional equipment
has been installed but the increase of power requirement has not been realized. If the
Estimated Recharge Time is greater than the Expected Recharge Time, the internal event
S RM Lack of Power is set. Additional rectifiers are required to correct this.

Recharge Power Supervision can only be configured through the web user interface. The
UIM/UIL interface can be used to view the status and the Estimated Recharge Time.

The functionality is configured by the following parameters:

Parameter Explanation

Enable Checkbox to enable the function

Expected Recharge Input field to enter the maximum allowed recharge time.
Time

Expected Backup Currently expected backup time

Time This parameter is part of the “Loss of Backup Time” calculation

The parameters can be configured and the Estimated Recharge Time can be seen at:

Interface Menu point Note

Web Configuration → Rectifier → Recharge Power

Supervision

Touch UI Menu → Rectifier → Recharge Power No

enable/disable

UIM Configuration → Rectifier → Recharge No

Status → Rectifier → Recharge enable/disable

Configuration instructions, ORION controller Configuration 69

2.5.9 Redundancy supervision

The controller measures the load power every minute and compares it to the available
power from the rectifiers and calculates the real number of redundant modules. If the
result falls in two adjacent samples below the given parameter Expected Number of
redundant RM, the internal event S RM Redundancy Lost is set and informs that
additional rectifiers are needed. The reason for lost redundancy could be the same as
mentioned in section 2.5.8 "Recharge Power Supervision".

ORION displays the actual number of redundant modules and also the number of
modules that should be added to reach the expected redundancy.

The functionality is configured by the following parameters:

Parameter Explanation

Enable Checkbox to enable the function

Required Number Input field to enter the minimum number of redundant modules.
of Redundant RM

The parameters can be configured and the actual number of redundant and lacking
modules can be seen at:

Interface Menu point Note

Web Configuration → Rectifier → Redundancy Supervision

Touch UI Menu → Rectifier → Recharge Power No

enable/disable

UIM Configuration → Rectifier → Redundancy No

enable/disable

2.5.10 Rectifier AC measurement

For information about AC Measurements using rectifiers, see section 2.10.3 "Internal AC
measurement".

2.5.11 Slot population

Each change in the rectifier slot population must be confirmed. The system controller
needs this information for error detection like incorrect cabling or faulty rectifiers. Click
“Acknowledge new” to mark a slot equipped with rectifier as populated. Click
“Acknowledge lost” to mark an empty slot as not populated. Commissioning, extending, or
reducing the system size, but also changing the physical position of a rectifier in the
system requires a confirmation of the slot population. Replacing rectifiers and using the
same slot does not require the confirmation.

70 Configuration instructions, ORION controller Configuration

Configuration instructions, ORION controller Configuration 71
2.6 Configuring DC/DC converters

2.6.1 Overview of configuring DC/DC converters

The DC/DC converters are configured to ORION by entering the number of DC/DC
modules into ORION.

The following instructions describe the main functions from the ORION point of view, with
step-by-step instructions.

2.6.2 DC/DC converter parameters

After communication is first established between the DC/DC converters and the
controller, it is possible to adjust the parameters with the controller. Without initial
communication to the power system controller, Delta’s DC/DC converters use their own
default parameters. With the controller the user can also adjust the default parameters,
after the communication is first established.

The following parameters control the behaviour of the DC/DC converters when the power
system is not in normal operating mode, such as start-up or low input voltage mode.

Parameter Explanation

Startup Delay Common delay for all DC/DCs for performing a

synchronized ramp-up. The range is from 0 to 60s. The
default is 0.

Table 2. Startup delay parameter

Parameter Explanation

DC/DC type Selection of the DC/DC converter type

Table 3. DC/DC type parameter

Parameter Explanation

Input Low Off Low input voltage for shutdown

Input Low On Low input voltage for startup

Ovp Limit Overvoltage protection

Table 4. Input characteristics

Parameter Explanation

Voltage Nominal output voltage

72 Configuration instructions, ORION controller Configuration

 Current limit Output current limit

Power limit Output power limit

Start Up Delay The delay for starting up after the input voltage is
connected

Table 5. Output parameters

Parameter Explanation

Stop Input Controller event input to disable all DC/DC modules

(when event activated)

Reset Reset button to restart blocked converter after failure

Table 6. Control parameters

The parameters can be configured at:

Interface Menu point Note

Web Configuration → DC/DC → Parameter

Touch UI Menu → DC/DC → Parameter

UIM Configuration → DC/DC → Parameter

Configuration instructions, ORION controller Configuration 73

2.6.3 DC/DC converter alarms

If a DC/DC converter malfunctions or fails, the ORION raises a DC/DC converter failure
alarm:

S Non Urg DFA or S Urgent DFA.

The DC/DC converter is considered as fault if at least one of the following criteria is
fulfilled:

 load share error

 input voltage outside range
 temporary internal off due to OVP or OTP
 internal off (latched, reason still present) due to OVP or OTP
 internal off (latched, reason not present) due to OVP, OTP or FF
 error (hardware defect)

The urgency of an alarm (Non-Urgent or Urgent) can be adjusted with thresholds

provided by the ORION.

Parameter Explanation

Failures for Non-Urgent A threshold for number of failed DC/DC converters that
Alarm activates a Non-Urgent Alarm for rectifier failure
(internal event: S Non Urg DFA). The default value is 1.

Failures for Urgent Alarm A threshold for number of failed rectifiers that activates
an Urgent Alarm for rectifier failure
(internal event: S Urgent DFA). The default value is 2.

Table 7. DC/DC alarm urgency parameters

DC/DC Alarm State Cause

S Non Urg DFA Number of faulty DC/DCs ≥ Failures for Non-Urgent

(Non-Urgent DC/DC Failure Alarm
Alarm) Number of working DC/DCs → Number of configured
DC/DCs
Number of working DC/DCs ≤ Number of configured
DC/DCs – Failures for Non-Urgent Alarm

S Urgent DFA Number of faulty DC/DCs → Failures for Urgent Alarm

(Urgent DC/DC Failure Number of working DC/DCs ≤ Number of configured
Alarm) DC/DCs – Failures for Urgent Alarm

Table 8. DC/DC alarm states

Note! If the event “S Urgent DFA” is activated, the “S Non Urg DFA” is
suppressed.

In addition to the above described two alarms ORION can activate the following events:

74 Configuration instructions, ORION controller Configuration

 Event Description

S DC/DC Pos Error Indicates error with physical slot addressing

S DC/DC new DC/DC Indicates that the user has plugged in a new module and
has not yet acknowledged it

S DC/DC Redundancy Lost Please see the chapter 2.6.5 "Redundancy supervision"

S DC/DC Setup Err The controller is not able to send a correct configuration
to the converter

The parameters can be configured at:

Interface Menu point Note

Web Configuration → DC/DC → Setup

Touch UI Menu → DC/DC → Setup

UIM Configuration → DC/DC → Setup → DC/DC Number

.

Configuration instructions, ORION controller Configuration 75

2.6.4 Installing DC/DC converters

After installing DC/DC converters, the new number of modules must be manually
confirmed for ORION, unless the checkbox “Acknowledge New DC/DC Converters
Automatically” is ticked.

After removal of DC/DC converters, the new number of modules must be confirmed for
ORION. If this is not done within a certain time a non-urgent alarm arises.

2.6.4.1 Web user interface

Follow this procedure to acknowledge new or lost DC/DC converters:

Step 1 Go to Configuration → DC/DC → Setup.

Step 2 Click “Acknowledge”.

This dialogue summarizes the status of the whole DC/DC system with numbers
for installed, working (ok) and faulty DC/DCs.
After Acknowledgment, the “DC/DC installed” field shows the updated number;
“DC/DC new:” must be 0.

Step 3 To avoid unexpected behaviour of the system, verify that none of the DC/DC
converters show an error. Go to Status → DC/DC. The DC/DC Monitor dialogue
displays the status and configuration status of each DC/DC converter.

Step 4 To identify each rectifier module, click “Show module”.

The “Com”-LED of the related DC/DC converter module blinks for over a minute,
to allow the module to be physically located.

Step 5 To view more details about each DC/DC converter module, click “Details”.

2.6.4.2 Touch UI interface

Step 1 Go to Menu → DC/DC → Setup.

Step 2 Go to “Number of DC/DC” , enter the password and update the number of
modules

or

Go to “New” or “Lost” and acknowledge the new or lostmodules

2.6.4.3 UIM interface

Step 1 Go to CONFIGURATION → DC/DC → SETUP.

Step 2 Go to “DC/DC NEW” or “DC/DC LOST”.

The number of added modules is shown and “Acknowledge” is highlighted.

Step 3 Press Enter and confirm

76 Configuration instructions, ORION controller Configuration

2.6.5 Redundancy supervision

The controller calculates the number of redundant DC/DCs by requesting the load power
and reserve power from the DC/DCs once a minute and comparing it the total number of
DC/DCs. If the result falls in two adjacent samples below the given parameter Expected
Number of redundant Redundant DC, the internal event S DC Redundancy
Lost is set.

The functionality is configured by the following parameters:

Parameter Explanation

Enable Checkbox to enable the function

Required Number Input field to enter the minimum number of redundant modules.
of Redundant
DC/DC

The parameters can be configured and the actual number of redundant modules can be
seen at:

Interface Menu point Note

Web Configuration → DC/DC → Redundancy Supervision

Touch UI Menu → DC/DC → Recharge Power No

enable/disable

UIM Configuration → DC/DC → Redundancy No

Status → DC/DC → Redundancy enable/disable

Configuration instructions, ORION controller Configuration 77

2.7 Configuring PV chargers

2.7.1 Overview of configuring PV chargers

The PV chargers are configured to ORION by entering or acknowledging the number of

PV chargers into ORION.

The following instructions describe the main functions from the ORION point of view, with
step-by-step instructions

2.7.2 PV charger parameters

After communication is first established between the PV chargers and the controller, it is
possible to adjust the parameters with the controller. Without initial communication to the
power system controller, Delta’s PV chargers use their own default parameters. With the
controller the user can also adjust the default parameters, after the communication is first
established.

The following parameters control the behaviour of the PV chargers when the power
system is not in normal operating mode, such as start-up or low input voltage mode.

Parameter Explanation

PV charger type Selection of the PV charger type

Table 9. PVC type parameter

Parameter Explanation

Input Low Off Threshold (voltage) for shutting down the PVCs when
input voltage is too low.

Input Low On Threshold (voltage) for switching the PVCs on, when
input voltage returns from low to acceptable values.

Table 10. Input parameters

Parameter Explanation

Voltage Default output voltage for the PVCs

Ovp Limit Output overvoltage protection threshold

Table 11. Output parameters

Parameter Explanation

VPGM+ Parameter defining how much higher the voltage setting

of the PVC modules is, compared to the rectifiers.

78 Configuration instructions, ORION controller Configuration

 Start Up Delay Common delay for all PV chargers

Start up “automatic”: The PVC starts or stops depending on the

sunshine only, independently from ORION
“controlled”: The PVC starts only when getting the
permission from the controller. This mode is preferred
when the system does not have a battery. The goal is to
prevent fast start / stop cycles of the PVC during a
mains outage if the load is too high.

Alarm Delay Delay to filter NUA and UA

Alarm Inhibit Input Inhibit event to block the failure alarms

Table 12. Control parameters

The parameters can be configured at:

Interface Menu point Note

Web Configuration → PVC → Parameter

Touch UI Menu → PVC → Parameter

UIM Configuration → PVC → Parameter

Configuration instructions, ORION controller Configuration 79

2.7.3 PV charger alarms

If a PV charger malfunctions or fails, the ORION raises a PV charger failure alarm:

S Non Urg PFA or S Urgent PFA.

The PV charger is considered as fault if at least one of the following criteria is fulfilled:

 input voltage outside range

 temporary internal off due to OVP or OTP
 internal off (latched, reason still present) due to OVP or OTP
 internal off (latched, reason not present) due to OVP, OTP or FF
 error (hardware defect)

The urgency of an alarm (Non-Urgent or Urgent) can be adjusted with thresholds

provided by the ORION.

Parameter Explanation

Failures for Non-Urgent Number of failed PVC modules triggering NUA

Alarm (internal event: S Non Urg PFA). The default value is 1.

Failures for Urgent Alarm Number of failed PVC modules triggering UA

(internal event: S Urgent PFA). The default value is 2.

Table 13. DC/DC alarm urgency parameters

PVC Alarm State Cause

S Non Urg PFA Number of faulty PVCs ≥ Failures for Non-Urgent Alarm
Number of working PVCs > Number of configured PVCs
Number of working DC/DCs ≤ Number of configured
DC/DCs – Failures for Non-Urgent Alarm

S Urgent PFA Number of faulty PVCs → Failures for Urgent Alarm

Number of working PVCs ≤ Number of configured PVCs
– Failures for Urgent Alarm

Table 14. PVC alarm states

Note! If the event “S Urgent PFA” is activated, the “S Non Urg PFA” is
suppressed.

In addition to the above described two alarms ORION can activate the following events
which can be mapped to remote alarms:

Event Description

S PVC Pos Error Indicates error with physical slot addressing

80 Configuration instructions, ORION controller Configuration

 S PVC new PVC Indicates that the user has plugged in a new module and
has not yet acknowledged it

S PVC Setup Err The controller is not able to send a correct configuration
to the converter

S PVC Input Low System event indicating that one of the converter has
been switched off because of input voltage outside the
range or breaker is open.

S PVC Fan Failure System event indicating that at least one of the PVC
reports fan failure.

S PVC Over-Temp System event indicating that at least one of the PVC
Protection reports OTP.

S PVC Over-Voltage System event indicating that at least one of the PVC
Protection reports OVP

The parameters can be configured at:

Interface Menu point Note

Web Configuration → PVC → Setup

Touch UI Menu → PVC → Setup

UIM Configuration → PVC → Setup → PVC Number

Configuration instructions, ORION controller Configuration 81

2.7.4 Installing PV chargers

After installing new PC chargers, the new number of modules must be confirmed for the
ORION.

2.7.4.1 Web user interface

Step 1 Go to Configuration → PVC → Setup.

Step 2 Click “Acknowledge”.

This dialogue summarizes the status of the whole PVC system with numbers for
installed, working (ok) and faulty PVCs.
After Acknowledgment, the “PVCs installed” field shows the updated number;
“PVCs new:” must be 0.

Step 3 To avoid unexpected behaviour of the system, verify that none of the PVC show
an error. Go to Status → PVC. The PVC Monitor dialogue displays the status
and configuration status of each PV charger.

Step 4 To identify each PVC, click “Show module”.

The “Com”-LED of the related PV charger module blinks for over a minute, to
allow the module to be physically located.

Step 5 To view more details about each PV charger, click “Details”.

2.7.4.2 Touch UI interface

Step 1 Go to Menu → PVC → Setup.

Step 2 Go to “Number of PVC” , enter the password and update the number of modules

or

Go to “New” or “Lost” and acknowledge the new or lost modules.

2.7.4.3 UIM interface

Step 1 Go to CONFIGURATION → PVC → SETUP.

Step 2 Go to “PVC NEW”.

The number of added modules is shown and “Acknowledge” is highlighted.

Step 3 Press Enter to confirm.

82 Configuration instructions, ORION controller Configuration

2.8 Configuring Delta inverters

2.8.1 Overview

ORION is able to communicate with Delta inverters over the IMBUS. The inverter
modules can be assigned into three phases with up to 32 inverters per phase.

2.8.2 Inverter Operating Modes

Battery:

In this mode, the inverter power comes from the DC bus / system batteries. This mode
provides the best output waveform regulation.

Bypass:

In this mode, the AC output is directly connected to the AC input, so the power comes
directly from the mains. This mode is the most efficient mode but the waveform quality is
highly dependent on the mains quality.

Online:

This mode is available only if the inverter has PFC function. The waveform regulation is
the same as the Battery mode, but the power comes from the AC input

2.8.3 Inverter Operating Profiles

The system will swithd between different oprtaion modes based on the chosen operating
profile:

Balanced:

In this profile, the 1st priority is Online, 2nd priority is Battery, and Bypass has lowest
priority. This profile provides good waveform / cost ratio. Once the AC is missing, the
source will change to battery and keep providing the power until the energy is exhausted.

Safe:

In this profile, the first priority is Battery, 2nd priority is Online, and Bypass has lowest
priority. This profile provides the best possible waveform but needs more rectifier capacity
because the inverters are normally powered from the DC bus.

Economic:

In this profile, the first priority is Bypass, 2nd priority in Online, and the last one is Battery.
This mode is the most economic one, but has the worst waveform regulation. This profile
is not suitable for regions with bad mains quality.

Configuration instructions, ORION controller Configuration 83

2.8.4 Inverter parameters

The behavior of the inverter system is defined by following parameters. In normal

operation the inverter are controlled by ORION. In order to have a defined behavior in
case there is no communication between the controller and the inverters, the default
settings are also stored in the inverter.

Parameter Explanation

Inverter type Selection of the inverter type

Table 15. PVC type parameter

Parameter Explanation

DC Input Low Off Turn off limit for the inverter Battery mode

DC Input Low On Turn on limit for the inverter Battery mode

AC Input Low Off Turn off limit for the inverter Online mode

AC Input Low On Turn on limit for the inverter Online mode

AC Input Frequency Low Off Turn off limit for the inverter Online mode

AC Input Frequency Low On Turn on limit for the inverter Online mode

Table 16. Input parameters

Parameter Explanation

Voltage Default output voltage for the inverters

Output Frequency Defualt output frequency

Table 17. Output parameters

Parameter Explanation

Operating Profile See above

Power Walk-In Slope Defines how quickly the output current can ramp up

Stop Input Event to stop the inverters

Suppress AC Input Alarms If checked, the AC input related alarms are suppressed

Table 18. Control parameters

The parameters can be configured at:

84 Configuration instructions, ORION controller Configuration

 Interface Menu point Note

Web Configuration → Inverter → Parameter

Touch UI Menu → Inverter → Parameter

UIM Configuration → Inverter → Parameter

2.8.5 Inverter alarms

If an inverter malfunctions or fails, ORION raises an inverter failure alarm:

S Non Urg IFA or S Urgent IFA.

The inverter is considered as fault if at least one of the following criteria is fulfilled:

 temporary internal off due to OTP, fan failure, short circuit, overload or
configuration changed
 internal off (latched, reason still present) due to OTP or fan failure
 internal off (latched, reason not present) due to OTP, fan failure, short circuit
or overload
 error (hardware defect)

The urgency of an alarm (Non-Urgent or Urgent) can be adjusted with thresholds

provided by the ORION.

Parameter Explanation

Failures for Non-Urgent Number of failed inverters triggering NUA

Alarm (internal event: S Non Urg IFA). The default value is 1.

Failures for Urgent Alarm Number of failed inverters triggering UA

(internal event: S Urgent IFA). The default value is 2.

Table 19. Inverter alarm urgency parameters

PVC Alarm State Cause

S Non Urg IFA Number of faulty inverters ≥ Failures for Non-Urgent Alarm
Number of working inverters > Number of configured inverters
Number of working inverters ≤ Number of configured inverters
– Failures for Non-Urgent Alarm

S Urgent IFA Number of faulty inverters → Failures for Urgent Alarm

Number of working inverters ≤ Number of configured inverters
– Failures for Urgent Alarm

Table 20. Inverter alarm states

Configuration instructions, ORION controller Configuration 85

 Note! If the event “S Urgent IFA” is activated, the “S Non Urg IFA” is
suppressed.

In addition to the above described two alarms ORION can activate the following events
which can be mapped to remote alarms:

Event Description

S Inv AC Outside Range One or more inverter indicate the AC input outside range

S Inv Com Failure Communication is lost between ORION and one or more
inverters

S Inv Fan Failure An inverter has detect a fain failure

S Inv Over Temp Protection One or more inverter indicate OTP

S Inv Overload One or more inverter indicate internal latched off due to
overload

S Inv Setup Err The controller is not able to send a correct configuration
to the inverter

The parameters can be configured at:

Interface Menu point Note

Web Configuration → Inverter → Setup

86 Configuration instructions, ORION controller Configuration

2.8.6 Installing Inverters

After installing new inverters, the new number of modules must be confirmed for the
ORION unless “Acknowledge New Inverters Automatically” is enabled.

2.8.6.1 Web user interface

Step 1 Go to Configuration → Inverter → Setup.

Step 2 Click “Acknowledge”.

This dialogue summarizes the status of the whole inverter system with numbers
for installed, working (ok) and faulty inverter modules.
After Acknowledgment, the “Inverters installed” field shows the updated number;
“Inverters new:” must be 0.

Step 3 To avoid unexpected behaviour of the system, verify that none of the inverters
show an error. Go to Status → Inverter. The Inverter Monitor dialogue displays
the status and configuration status of each Inverter.

Step 4 To identify each Inverter, click “Show module”.

The “Com”-LED of the related Inverter module blinks for over a minute, to allow
the module to be physically located.

Step 5 To view more details about each Inverter, click “Details”.

Configuration instructions, ORION controller Configuration 87

2.9 Configuring Eltek Rectiverters

2.9.1 Overview
The ORION version, ID:E3 with two CAN buses, is able to control and monitor Eltek
rectiverters (RCV) over CAN bus using eNexus protocol. RECTIVERTER™ is a three
ports module with an AC input port, an AC output port, and a bi-directional DC port. It is
capable of charging the 48V battery and simultaneously providing power for the AC and
DC loads. During mains failure AC loads are feed using energy stored in the battery.
Rectiverters can be used in a single phase or three phase systems. Up to 32 rectiverters
can be connected to ORION.

2.9.2 Supported system configurations and operating modes

Orion supports the following system configurations:

- Inverter without AC input – single phase

- Inverter without AC input – three phases
- Inverter with AC input – single phase
- Inverter with AC input – three phases
- Rectiverter – single phase
- Rectiverter – three phases

AC out AC out AC out

DC in DC in DC in/out

AC in DC out AC in DC out AC in DC out

a

Pure inverter with Delta RMs Inverter with Delta RMs Rectiverter without RMs

2.9.3 Rectiverter parameters

88 Configuration instructions, ORION controller Configuration

 Parameter Explanation

Rectiverter type Selection of the rectiverter type

Table 21. RCV type parameter

Parameter Explanation

DC Default Voltage Default target voltage for the DC output

DC OVP Limit Over voltage protection limit

AC Output Voltage Define the target AC output voltage

Output Frequency The default frequency for AC output

Walk-In Time

AC Input Frequency Low On Turn on limit for the inverter Online mode

Table 22. Configuration parameters

The parameters can be configured at:

Interface Menu point Note

Web Configuration → Rectiverter → Parameter

Touch UI Menu → Rectiverter → Settings

2.9.4 Rectiverter alarms

If a rectiverter malfunctions or fails, ORION raises a rectiverter failure alarm:

The urgency of an alarm (Non-Urgent or Urgent) can be adjusted with thresholds

provided by the ORION.

Parameter Explanation

Rectiverter Failures for Non- Number of failed rectiverters triggering NUA

Urgent Alarm (internal event: S Non Urg RCVFA). The default value is
1.

Rectiverter Failures for Number of failed rectiverters triggering UA

Urgent Alarm (internal event: S Urgent RCVFA). The default value is
2.

Table 23. Rectiverter alarm urgency parameters

Configuration instructions, ORION controller Configuration 89

 Note! If the event “S Urgent IFA” is activated, the “S Non Urg IFA” is
suppressed.

In addition to the above described two alarms ORION can activate the following events
which can be mapped to remote alarms:

Event Description

S RCV Bypass Active The system is running in bypass mode

S RCV Com Failure Communication is lost between ORION and one or more
rectiverters

The parameters can be configured at:

Interface Menu point Note

Web Configuration → Rectiverter → Setup

Touch UI Menu → Rectiverter → Functions → Setup

2.9.5 Installing Rectiverters into the system

This document assumes that the system is prepared and configured for rectiverters. The
user just needs to insert the modules to the shelves and adjust the operating parameters.

Rectiverters get their IDs automatically according to plug-in order. Therefore, insert the
rectiverter modules one by one in the desired ID order. After inserting new rectiverters,
the new number of modules must be confirmed to ORION unless “Acknowledge New
Rectiverters Automatically” is enabled.

The new rectiverters can be acknowledged at:

Interface Menu point Note

Web Configuration → Rectiverter → Setup

Touch UI Menu → Rectiverter → Functions → Setup

2.9.6 Removing Rectiverters from the system

If a rectiverter needs to be removed from the system, pull it out from the shelf and wait for
20 second until the controller recognizes that a module has been lost. Confirm the new
number of modules to ORION by acknowledging the lost module.

2.9.7 Replacing Rectiverters

90 Configuration instructions, ORION controller Configuration

 If several modules need to be exchanged, start from the module at the first physical
position. Pull it out from the shelf, and if it was operating, wait for 20 seconds until ORION
recognizes that the module is lost. Insert then the replacement module. This module will
automatically get the ID of the previously removed module. Repeat the procedule with all
rectiverters to be echanged.

Check that the number of new and lost rectiverters is zero and acknowledge if necessary:

Interface Menu point Note

Web Configuration → Rectiverter → Setup

Touch UI Menu → Rectiverter → Functions → Setup

2.9.8 Operating the bypass switch

The rectiverter system can be equipped with a bypass swtich that can be used to isolate
the rectiverters from the load and to transfer the load to the mains. The transfer can be
done without a break when a “make before break” switch is used. To inform ORION about
the position of the swich, an auxiliary contact is connected to ORION input.

Bypass Switch
(make before break)

AC out

DC in
Dig Input ORION
Auxiliary
Contact

AC in DC out

Use the following procedure to transfer the load to Mains:

Step 1 Press the “Activate” button either on Touch UI or web GUI.

Step 2 Wait until the status changes to “ready to switch”.

Step 3 Switch the bypass switch. The status changes to “active”

Interface Menu point Note

Web Control → Rectiverter → Bypass

Touch UI Menu → Rectiverter → Functions → Bypass

Configuration instructions, ORION controller Configuration 91

92 Configuration instructions, ORION controller Configuration
2.10 Converter positioning
Each converter, for example, a rectifier or a DC/DC converter, can be assigned a physical
location in the system. This is especially helpful for remote supervision of the system.
When a faulty converter is detected remotely with the help of its exact physical location in
the system (for example, second rectifier from the left in the third shelf from the top),
people without knowledge of the system can be sent to the site to replace the module
(pull out the faulty unit and plug in the new one, no further action necessary).

The positioning is based on location information (cabinet, shelf, and slot if applicable)
which is stored on each converter backplane in a dedicated EEPROM or generated by
jumpers and switches on the backplane. ORION supports positioning using the data
which it obtains via the converters.

2.10.1 Cabinet scheme

This type of arrangement is used if the shelf identification is not necessary (for example,
systems with DPR 7200B-48 rectifiers using one rectifier per shelf). With this scheme, up
to 43 cabinets are possible. Each cabinet has up to 16 slots. Although 256 different slot
addresses are possible, the system size is limited to 128 rectifiers. Each cabinet requires
its own RPGA board, or each backplane must be equipped with a memory device in which
the address is stored. The rectifier name consists of cabinet and slot address (for
example, DC 2.9, where DC is the name of the converter located in slot 9 of cabinet 2).

Cabinet 1 Cabinet 2 Cabinet 16

RM 1.1 RM 2.1 RM 16.1

RM 1.2 RM 2.2 RM 16.2

RM 1.3 RM 2.3 RM 16.3

RM 1.4 RM 2.4 RM 16.4

RM 1.5 RM 2.5 RM 16.5

RM 1.6 RM 2.6 RM 16.6

RM empty DC 2.7 DC empty

RM empty DC 2.8 DC empty

RM empty DC 2.9 not avail.

RM 1.10 DC 2.10 not avail.

not avail. DC empty not avail.

not avail. DC empty not avail.

Figure 2. Converter positioning – cabinet scheme

Configuration instructions, ORION controller Configuration 93

 Parameter Explanation

Cabinet ID Identifier of the cabinet. This number is used to generate

the rectifier name.

Name Name of the cabinet. This parameter will be used for a

future graphical representation of the system.

Converter Slots Checkboxes for the available slots.

Table 24. Converter positioning – cabinet scheme parameters

2.10.1.1 Web user interface

Step 1 Go to Configuration → Options and tick the checkbox for “Positioning”.

Step 2 Go to Configuration → System Architecture → Power Module Positioning.

Step 3 Click “Change”.

Step 4 Select the Scheme Type “cabinet”.

Step 5 Click “Accept Changes”.

Step 6 To add a cabinet, click “Add cabinet”.

Step 7 In the Converter Positioning Editor dialog, select the Converter Slots that are
available for use in the cabinet.

Change the cabinet name by entering the new name in the Name field.

Step 8 Click “Accept Changes”.

2.10.2 Shelf scheme

Shelf Scheme is used for systems with the converters arranged in shelves, for example,
systems with FR 48V-2000W-E, DPR 1200B-48, or DPR 600B-48… rectifiers. With this
scheme, up to 43 shelves are possible. A cabinet can be assigned to each shelf. Each
shelf consists of up to 16 slots. Although 4096 different slot addresses are possible, the
system size is limited to 128 converters. Each cabinet requires its own RPGA board, or
each backplane must be equipped with a memory device in which the address is stored.
The converter name consists of the cabinet address, shelf address and slot address (for
example, RM 1.3.7, where RM is the name of the rectifier located in slot 7 on shelf 3 of
cabinet 1).

94 Configuration instructions, ORION controller Configuration

 Cabinet 1 Cabinet x

RM RM RM RM
1.1.1 1.1.2 1.1.7 1.1.8
Shelf 1

RM RM DC Not
1.2.1 empty 1.2.7 avail.
Shelf 2

DC DC RM RM RM RM RM RM
1.3.1 1.3.2 1.3.7 empty
Shelf 3 x.14.1 x.14.2 x.14.7 1.16.8
x.14.8
Shelf 14

RM RM RM RM
x.15.1 x.15.2 x.15.7 1.16.8
x.15.8
Shelf 15

RM RM RM DC
x.16.1 x.16.2 x.16.7 empty
Shelf 16

Figure 3. Converter positioning – shelf scheme

Parameter Explanation

Shelf ID Identifier of the shelf. This number is used to generate

the rectifier name.

Name Name of the shelf. This parameter will be used for a

future graphical representation of the system.

Cabinet ID Identifier of the cabinet. This number is used to generate

the rectifier name.

Module Slots Checkboxes for the available slots.

Table 25. Rectifier positioning – shelf scheme parameters

2.10.2.1 Web user interface

Step 1 Go to Configuration → System Architecture → Power Module Positioning.

Step 2 Click “Change”.

Step 3 Select Scheme Type “shelf”.

Step 4 Click “Accept Changes”.

Step 5 Select “Shelf ID” from the drop-down list and click “Add Shelf”.

Step 6 In the Converter Positioning Editor dialog, select the converter slots
(checkboxes) that are available for use in the shelf.

Configuration instructions, ORION controller Configuration 95

 Step 7 Select “Cabinet ID” from the drop-down list.
The shelf name can be changed by entering the new name in the Name field.

Step 8 Click “Accept Changes”.

2.11 Configuring CE + T inverters

ORION is able to communicate with CE+T inverter systems equipped with T2S
monitoring device. T2S unit is connected to ORION via GWM-MODBUS gateway module.
ORION is able to display measurements and status information from the inverter system,
but the configuration is done by loading a configuration file directly into T2S via serial line
using CE+T terminal tool.

2.12 Configuring communication with 3rd party Modbus

devices
ORION is able to communicate with devices that support Modbus protocol over serial
line. ORION can read information, such as measurements, states and events and also
write to the Modbus registers of a device. ORION Touch has two RS485 and one RS232
port that can be used for the connection.Additionally it is possible to use GWM-MODBUS
module as an additional RS485 port. As each device uses different communication
protocol, ORION can be configured by loading in a protocol mapping file. Creating the file
requires advanced skills, so this process is not covered by this document. To get a
mapping file, please contact your Delta representative.

Parameter Explanation

Type The name of the module is the same as the name of the
mapping file

Name The name will be used as a prefix for the names of

measurements that are polled from the device

Interface The port where the device is connected to

Slave Id The Slave Id that is set into the module.

Table 26. Modbus device parameters

Follow the process below to configure communication with Modbus devices:

Step 1 Go to Configuration → System → File Manager to load in the mapping file.

Step 2 Select File Type “Modbus Master Mapping” and click “Load File from PC”.

Step 3 Click “Choose File” and select the mapping file that is stored in your PC.

Step 4 Click “Start”. The mapping file will be loaded in to ORION.

Step 5 Go to Configuration → HW Setup → Modules.

96 Configuration instructions, ORION controller Configuration

 Step 6 Select the device from the drop-down list for “Type”. The device is identified by
the name of the mapping file.

Step 7 Enter the “Name” for the device.

Step 8 Select the “Interface” and “Slave Id” and click “Add. The new module will appear
in the list of Modbus Slaves. Check that the Status of the module is OK

Configuration instructions, ORION controller Configuration 97

2.13 Configuring airconditioners
ORION is able to communicate with some airconditioners manufactured by Delta. The
user can set the default operating parameters and additionally configure up to five
alternative cooling plans with different set of parameters. The alternative cooling plans
are activated by a control event. The functionality of different aircon types is not exactly
the same, so all the control parameters are not applicable with all aircons.

Parameter Explanation

Plan Name Name of the alternative cooling plan

Priority Priority of the alternative cooling plan

Activation input Even to activate the alternative cooling plan

Target temperature Target room temperature

Start temperature Cooling start temperature. Used by TCTC-160-48

Hysteresis Cooling stop hysteresis. Used by TCTC-160-48

Operating mode Operating mode of the aircon. Can be “Normal”, “Silent”

or “Off”

Control Temperature Temperature measurement to be used for the

temperature control

Inside Fan Speed while Used by TCTC-160-48

Cooling

Inside Fan Speed while Used by TCTC-160-48

Heating

Outside Fan Speed while Used by TCTC-160-48

Cooling

Standby fan speed Defines the speed of the internal fan while the
compressor is off. “Low” or “High”.

Heater start temperature Temperature where the heater starts up

Hysteresis Stop hysteresis for the heater

Heater control In “Auto” mode the heater is controlled by the

temperature. In “Manual” mode the heater is controlled
by the digital inputs of the heater.

Table 27. Aircon control parameters

The parameters can be configured at:

Interface Menu point Note

Web Configuration → HW Setup → Modules

Touch UI No access

98 Configuration instructions, ORION controller Configuration

 UIM No access

The status can be seen at:

Interface Menu point Note

Web Status → Aircon

Touch UI No access

UIM No access

2.14 Configuring fan speed control units

FAN-CTRL is an add-on module to control two heaters and the speed of two cooling fans.
The IOM-X1 module is has also the capability to control the speed of fans. Once
configured via ORION web interface, the fan speed control will work independently, but
the modules communicate over IMUBS to transfer measurements and status information
to ORION. The user can set the default operating parameters and additionally configure
up to three alternative operating modes with different set of parameters.

Caution! The FAN-CTRL module and IOM-X1 module are configured in Delta
system factory, so please do not change any settings unless you are absolutely
sure about what you are doing. Wrong settings can result in over temperature of
the equipment.

Configuration instructions, ORION controller Configuration 99

2.15 Configuring alarms
Alarms are an important aspect of the reliability of a power system. Well designed alarm
handling can notify the user of an unexpected behaviour of the power system, in case of
a mains failure, low voltage, rectifier failure and so on. The ORION controller offers an
easy to use alarm mapping web page to assign alarms to outputs. The alarm events can
be system events generated by various controller functions, or user defined events
created by using the Signal Processing Engine.

2.15.1 Alarm mapping

Available alarm events (visible as horizontal lines) can be connected freely with the
outputs (visible as vertical lines). The outputs are grouped by module and all groups can
be collapsed and expanded. Any available event can be added to the list of alarm events
by clicking the icon.

2.15.1.1 Managing Alarm Events list

To be able to map an event to an output using the alarm mapping functionality, it has to
be selected to the list of alarm events. Defining an alarm event adds also additional
functionality and behaviour to it:

 The alarm events are internally inverted when used for driving relay outputs.
An active alarm event releases the relay, and therefore, even if the system is
not powered, the active alarm status is still indicated. In other words, when

100 Configuration instructions, ORION controller Configuration

 alarm is not active the Common (C) and Normally Open (NO) terminals are
connected and when alarm is activated the relay switches to Normally Closed
(NC).

 Only alarm events can be inhibited in the output relays with the function Alarm
Stop. This is useful during maintenance when alarms are expected, but do not
require any actions. The critical alarms are usually driving some relays that
activate external alarming systems. These alarms can be quickly inhibited
with the Alarm Stop function (button “Stop Alarms” at the top of the browser
window or menu “ALARM STOP” in the UIM/UIL interface).

 The alarm events are shown on the home page when active.

 The status of alarm events is always displayed on the page Alarm → Status.

Use the following procedure to manage the list of alarm events:

Step 1 Go to Alarm → Setup.

Step 2 Click on the icon.

Step 3 Select an event from the “Non-Alarm Events” list and click “Add”.

The event appears on the “Removable” user alarm events list. It is possible to
select multiple events at same time by using “Shift” and “Ctrl” keys.

Step 4 Click “Accept Changes”.

Note! The events defined as alarms receive automatically a prefix “A” in front of
the event name. However, on the alarm mapping page this prefix is not shown.

To remove an alarm from the “Removable” user alarm events list:

Step 1 Select an event from the “Non-Alarm Events” list and click “Remove”.

Note! The “Non-Removable” list is a list of events that are defined as alarms,
and have been taken into use by some function. Or mapped to an output. These
events cannot be removed from the alarm event list before they are disabled
from the use of the function or functions.

2.15.1.2 Mapping alarms to outputs

Available alarm events (visible as horizontal lines) can be connected freely with the
outputs (visible as vertical lines). One event can be mapped to several outputs and up to
64 events can be mapped to a single output. The outputs are grouped by module and all
groups can be collapsed and expanded by clicking the minus and plus icon.

Use the following procedure to map events to outputs:

Step 1 Go to Alarm → Setup.

Configuration instructions, ORION controller Configuration 101

 Step 2 To connect an event to an output click the crossing of the horizontal and vertical
line.

Step 3 To disconnect an existing connection click the circle on the crossing of the lines.

Note! Useful tips:

 To visualize clearly where an event is connected, highlight the connections by

clicking the event name.
 To highlight all the events connected to a specific output, click the output
name.
 To copy all the connections of a certain output to another output, drag the
output name onto another output name.
 To erase all the connections to a specific output, click the X below the output
name.
 To hide a complete module, click the minus sign at front of the module name.
To show it again, click the plus sign.
Note!: this functionality just hides the module from the display, but does not
erase the connections.
 To erase all connections to a module click the eraser icon which appears
when highlighting the module name.
 A column with dotted light-grey line means that this output is assigned to an
event and cannot be configured using this page.

Note! Various tooltips are shown when the user leaves the mouse over special
elements:

 “Edit Alarm Events” appears on the “edit” icon for the Alarm Events.
 “Collapse this group” appears on each “minus” icon in the expanded groups.
 “Expand this group” appears on each “plus” icon in the collapsed groups.
 “This group has some input/output mapping” appears on the “link” icon for a
collapsed group.
 “Clear all connections” appears in the “clear all” icon below a group title.
 On each connection a tooltip appears indicating the state of the connection:
 “S Urgent Alarm <---> OUT 1” indicates that the connection active.
 “S Urgent Alarm <-x-> OUT 1” indicates that the connection is not active.
 A tooltip shows the full name of a module, an output and an alarm when the
mouse is over the name (useful in case of truncated name).

2.15.1.3 Editing the output labels

For easier identification, it is possible to add a label such as “Urgent alarm” or “Mains
failure” for an output.

Use the following procedure to add labels:

Step 1 Go to Alarm → Setup.

Step 2 If the module is not shown, click it in the module list on the right of the page.

Step 3 Click the edit icon next to the module name

102 Configuration instructions, ORION controller Configuration

 Step 4 Enter the text in the field corresponding to the output you want to add a label.
Note that your modifications will be automatically be saved when you select
another field or click somewhere else in the page – there is no “Accept Changes”
button on this page.

Step 5 Click “Back” to return to the previous page.

2.15.2 Alarm stop

It is possible to block an alarm event from triggering a remote alarm. This may be
required during system upgrade, maintenance, or repair situations where events maybe
triggered, but alarms are not required. If an alarm is already active it is frozen in the active
state unless it is reset.

2.15.2.1 Web user interface

Use this procedure to block alarm events:

Step 1 Go to Alarm → Maintenance.

Step 2 For each alarm event, select “frozen”, or click “Stop Alarms” to block all alarm
events having the checkbox Alarm Stop selected.

Step 3 To save the changes, click “Accept Changes”.

Caution! When it is no longer necessary to block events or alarms, configure all

blocked events to “normal” or click “Activate Alarms”. If this is not done, genuine
alarm events may not be raised.

2.15.2.2 Touch UI

Use this procedure to block all alarm events by activating Alarm Stop.

Step 1 Go to the main page ALARM.

Step 2 Press Stop Alarms, enter a password and confirm.

Caution! When it is no longer necessary to block alarm events, activate the alarms
again by pressing Activate Alarms

2.15.3 Alarm latch reset

In case the Lach functionality of the signal processing engine is used to memorize
alarms, the user has a possibility to map a system event S Alarm Reset to the reset input
of the latches to reset these alarms.

This event can be activated at

Configuration instructions, ORION controller Configuration 103

 Interface Menu point Note

Web Alarm → Maintenance

Touch UI Alarm (“Reset Latched Alarms”)

UIM No access

2.15.4 Alarm indication on Touch UI

ORION indicates an active alarm by showing a red alarm bell at the right top corner of the
touch UI. In many cases there is also a small red symbol shown together with an icon on
the status page. The red alarm bel is also a link to the Alarm page that shows more
details about the active alarms.

While the screen saver is active, the active alarm is indicated by a red alarm bell that
moves slowly. Additionally the screen can blink if the blinking is enabled on the page
Configuration > Options.

104 Configuration instructions, ORION controller Configuration

2.16 Signal processing engine
The Signal Processing Engine consists of four parts: The Measurements, the
Measurement Processing, the Event Definitions and the Event Processing. Digital
Measurements may be used directly as Events. For Analogue and Temperature
Measurements a signal conditioning must be used by defining a Threshold and a
Hysteresis. Before using Measurements as Events they can be optionally passed through
the Measurement Processing stage which allows mathematical operations. Events may
be mapped to an output directly or used again as an input for further Signal Processing.
Besides attaching an Event to a relay directly, they can be defined as Alarm or LVD which
adds additional functionality and behaviour to them. Every Event may also be logged if
desired.

2.16.1 Measurements

All signals that are processed by the ORION controller must be defined as
measurements. Some of them (so-called system measurements) are predefined and
others are generated automatically by defining other system components. There are three
different types of measurements available: Digital, Analogue, and Temperature
measurements.

Digital Measurement

A digital measurement has an adjustable switching level for both directions using the
threshold and hysteresis setting. This can be used for conditioning even noisy signal
sources.

Analogue Measurement

The analogue measurement is used to monitor voltage signals. The measured voltage
may be corrected in a certain range by calibration.

Temperature Measurement

A temperature measurement converts the signal directly to a temperature value. The

measured temperature may be calibrated if necessary.

Scaled Measurement

The scaled measurement is used to convert voltage signals into power signals. The
measured voltage can be scaled by a linear conversion, which is defined by two
measurement points. Each measurement point is described by an input value and an
output value.

TIme Measurement

The time measurement measures how long an event has been active. This measurement
can be manually reset in the menu Control → Counter.

Configuration instructions, ORION controller Configuration 105

 Note! Before creating a measurement to the ORION check that the hardware
supports the measurement.

Parameter Type Explanation

Name All Name of the measurement

Inverted Digital Check the checkbox, if inversion is required

Threshold Digital Switching level

Hysteresis Digital Hysteresis between activation and

deactivation

Source Event Time

Table 28. Measurement type parameters

Measurements can only be created using the web user interface.

2.16.1.1 Web user interface

Step 1 Go to Configuration → Signal Processing Engine → Measurements.

From the New Measurement drop-down menu, select the measurement type:

 Digital
 Analogue
 Temperature
 Scaled
 Time

The following sequence describes the use of a digital measurement as

example. The treatment of analogue or temperature measurements is
accordingly.

Step 2 Click “Add”.

Step 3 Define the parameters in the Digital Measurement dialogue.

Step 4 Click “Accept Changes”.

Step 5 Go to Configuration → HW Setup.

Step 6 Select the ORION module that the measurement hardware is connected to, for
example, ORION.

106 Configuration instructions, ORION controller Configuration

 Figure 4. ORION I/O setup dialogue

Step 7 Select the measurement, created earlier, from the drop-down menu.

Step 8 Click “Accept Changes”.

2.16.2 Measurement processing

Measurement Processing is a generic block for applying different mathematical

operations to measurements (except digital measurements). Available operations are:

 The “Difference” measurement, which is the result of the difference of 2

selected inputs measurements.
 The “Summation” measurement, which is the sum of up to 32 selected inputs
measurements.
 The “Minimum” measurement, which is the lowest of up to 32 selected inputs
measurements.
 The “Maximum” measurement, which is the highest of up to 32 selected
inputs measurements.

Configuration instructions, ORION controller Configuration 107

  The “Average” measurement, which is the average calculation of up to 32
selected inputs measurements

Only input measurements with equal units are allowed and the same unit is automatically
selected as well for the output. The output can be used for signal processing in the same
way as any other measurement. The output measurement keeps the properties
(measurement type) of the input measurements, i.e. a Difference Measurement of two
Analogue Measurements has still the properties of the Analogue Measurements.

2.16.2.1 Web user interface

Step 1 Go to Configuration → Signal Processing Engine → Measurement Processing.

Step 2 Select the Processing type and click Click “Add”.

Step 3 Enter a name for the new measurement and select the processed
measurements.

Step 4 For “Difference” Select “Absolute Difference” if absolute value is needed.

Step 5 Click “Add New definition”.

2.16.3 Event definitions

To use the signal processing engine together with analogue (including temperature)
measurements, they must be digitized first. This is done by defining a threshold and a
hysteresis value for the measurement. Each definition must have a unique name. The
result of this definition is an event. In the ORION some internal system events are created
by default at the Delta factory. The threshold editor within the Event Definition allows
defining both polarities of events. As many different thresholds as needed per
measurement can be defined.

Parameter Explanation

Too High Event Name of the Too High event

Upper Threshold Value of the Too High event

Upper Threshold Hysteresis Hysteresis to deactivate the Too High event

Lower Threshold Hysteresis Hysteresis to deactivate the Too Low event

Lower Threshold Value of the Too Low event

Too Low Event Name of the Too Low event

Table 29. Event definition parameters

2.16.3.1 Web user interface

Step 1 Go to Configuration → Signal Processing Engine → Event Definitions.

Step 2 Select the required measurement from the New Event(s) on Measurement
drop-down list.

108 Configuration instructions, ORION controller Configuration

 Step 3 Click “Add”.

Step 4 In the Threshold Editor dialogue, enter a name or names for the new event(s)
and define the parameters (thresholds and hysteresis).

Step 5 Select the “UIM access” for the local user.

Step 6 Click “Add New Definition”.

2.16.3.2 Touch UI/UIM interface

The setting “UIM Access” defines if the parameters for the defined events can be seen
and/or edited through the Touch UI/UIM interface.

The parameters can be edited at:

Interface Menu point Note

Touch UI Menu → Events → Event Thresholds

UIM CONFIGURATION → EVENT → THRESHOLDS

2.16.4 Event processing

All events, including the system defaults and user-defined events can be processed with
each other. Boolean Logic (AND, OR, Inversion), RS Latching, timer, filter, counter and
time counter functions can be used to process events together or separately. The
maximum number of each function type is 256.

AND event

The AND event is active, if both source events are active.

Parameter Explanation

Event Unique name for the AND event.

1st source event Mandatory. Unique source name (event) required.

2nd source event Mandatory. Unique source name (event) required.

Table 30. AND event parameters

OR event

The OR event is active, if one or more of the source events are active.

Parameter Explanation

Event Unique name for the OR event.

Configuration instructions, ORION controller Configuration 109

 1st source event Mandatory. Unique source name (event) required.

2nd source event Mandatory. Unique source name (event) required.

3rd to 8th source event If necessary. Unique source names (event) required.

Table 31. OR event parameters

Inverted event

The Inverted event is active when the source event is not active and vice-versa.

Parameter Explanation

Event Unique name for the RS Latch event.

Function source event Mandatory. Unique source name (event) required.

Table 32. Inverted event parameters

RS latch event

The RS latch combines any two different events to produce an output event state
according to the following truth table:

SET Event RESET Event Output Event

FALSE FALSE FALSE

FALSE → TRUE FALSE FALSE → TRUE

TRUE FALSE TRUE

TRUE FALSE → TRUE TRUE

FALSE FALSE → TRUE TRUE → FALSE

Table 33. RS Latch logic

Parameter Name Description

Event Name of the new RS Latch Event.

Function Set Event input to set the output Event.

Function Reset Event input to reset the output Event. If the input Event is still
active, then the active reset Event has no influence. Optional.

Persistent If the checkbox is ticked, the state of the RS Latch is stored

persistent

Table 34. RS latch parameters

110 Configuration instructions, ORION controller Configuration

 The maximum number of RS Latch Setup entries is 256. The RS Latch Event States are
saved in the persistent memory and during the power-up sequence, their previous states
(before the reboot) and restored.

If a latch event is defined without input events, it can be mapped to the SNMP Control
Event Table and controlled remotely by SNMP protocol.

Timer event

This function allows creating time controlled events. The Timer event is activated based
on the weekday and the time. The Event is activated on the defined Start Time on every
selected Start Days. It is stopped on the defined End Time on every Selected End Days.

The Start Time and End Time depend on the time settings of ORION. It means that the
times represent the same time zone and daylight savings as the ORION.

Parameter Explanation

Event Name of the new filter event.

Start Time Time to set the event to TRUE.

Start Day Day of week to set the event to TRUE at Start Time.

End Time Time to set the event to FALSE.

End Day Day of week to set the event to FALSE at End Time.

Table 35. Timer event parameters

The maximum amount of timer setup entries is 256.

If there are two or more consecutive start or end moments, the current event state is
maintained until a corresponding end or start moment occurs. If a start moment has the
same value as the end moment, the event state is maintained.

Filtered event

The event follows the state of a source event only if/when the time thresholds TRUE and
FALSE are passed. Additionally it is possible to define the state of the output in case the
state of the input event is “indeterminate”.

Parameter Explanation

Event Unique name for the filtered event.

Function source event Mandatory. Unique source name (event) required.

TRUE for min. When the source event remains active for the specified
time (TRUE) the filtered event is activated.

FALSE for min. When the source event has been deactivated for the
specified time (FALSE) the filtered event is deactivated.

Configuration instructions, ORION controller Configuration 111

 Output when input is When the source event is indeterminate, the output state
indeterminate will be set to either True, False or Indeterminate.

Table 36. Filtered event parameters

Counter event

A Counter event is counting the false to true transitions of a configured Input event. When
the Counter value matches the counter threshold, the Counter event changes state.

The Counter event has an Enable event. As long as the Enable event is true, the Counter
event counts the false to true transitions of the Input event. If the Enable event is false,
transitions are not counted.

The Counter event has a Reset event. When the Reset event is true, the Counter event
state is set to false, it does not count transitions and the counter value is set to zero. If the
Reset event is false, the Counter event counts normally. The Reset Event has the priority
over the Enable event.

It is at anytime possible to reset the Counter event state and counter value from the Web
interface of the UIM. This kind of reset acts like the Reset event.

There are 2 modes of behaviour for a Counter event, standard and toggle. In standard
mode the Counter event counts until it reaches the threshold, then the Counter event
state is set to true and the counter does not count anymore. In toggle mode the Counter
event counts until it reaches the threshold, then the Counter event state is toggled, the
counter value is reset and the counting goes on.

Parameter Explanation

Event Unique name for the Counter event.

Input Event which false to true transitions are going to be

counted

Enable Event for enabling counting

Reset Event for resetting the state and counter value

Mode Standard or toggle

Threshold When the counter value reach this limit, then the
Counter event state is changed according to the mode

Time counter event

The Time counter event works exactly the same way the Counter event does, except it is
not counting any event transitions, but it is counting seconds. The operating parameters
are also the same except that there is no Input parameter.

Event processing can only be modified through the web user interface.

112 Configuration instructions, ORION controller Configuration

2.16.4.1 Web user interface

Use this procedure to configure event processing:

Step 1 Go to Configuration → Signal Processing Engine → Event Processing.

Step 2 In the Event Processing dialogue, select event type from the Event Type drop-
down menu (AND, OR, Inversion, Filter, RS Latch, Timer, Counter, Time
Counter).

Step 3 Click “Add”.

Step 4 In the open dialogue, enter a unique name for the new processed event and
define the parameters.

Step 5 Click “Add New Definition”.

Step 6 In the Event Processing dialogue, click “Accept Changes”.

2.16.4.2 Touch UI/UIM interface

The thresholds and hysteresis of source events, filter parameters and settings for timers
can be edited in the menu:

Interface Menu point Note

Touch UI Menu → Events

UIM CONFIGURATION → EVENT

2.16.5 Inputs, outputs, LEDs and other indicators

The internally defined events can be assigned a relay or an open collector output of
ORION or an add-on module for an external alarming system, and/or a LED integrated to
the UIM/UIL interface. However, in SW versions V6.20 and above, it is recommended to
use the Alarm Mapping functionality for configuring alarms instead of direct mapping of
events on various module specific pages. For more details, please look at the chapter
2.12 "Configuring alarms".

External alarms can be connected to the ORION and to the signal processing engine for
further processing, using the digital input interfaces of the ORION.

Alarm events for I/O cannot be configured through the UIM/UIL interface.

Configuration instructions, ORION controller Configuration 113

 Figure 5. An example of ORION alarm relay connections

2.16.5.1 Web user interface

2.16.5.1.1 Assign inputs/outputs

Step 1 Go to Configuration → HW Setup → ORION (or SSM).

Step 2 Select the signals for Digital Inputs/Temperatures/Middle Point Inputs from the
respective drop-down menu.

Step 3 Select the events for the Digital Outputs/Open Collector Outputs/LVD Outputs
from the respective drop-down menu.

Step 4 Ensure the cabling for external equipment is according to the required
configuration.

Note! It is recommended to use the alarm events differentiated by prefix “A” for
remote alarming. When assigned to relay outputs, the alarm events are
internally inverted. An active alarm event releases the relay, and therefore, even
if the system is not powered, the active alarm status is still indicated.

114 Configuration instructions, ORION controller Configuration

 Figure 6. ORION I/O setup dialogue

2.16.5.1.2 Assign LEDs and buzzer

It is recommended to do the mapping of alarms to LEDs using the Alarm Setup page.
Please see the chapter 2.12 "Configuring alarms". In older SW versions the mapping is
done in the HW module specific configuration pages using the following procedure:

Step 1 Go to Configuration → HW Setup → User Interface.

Step 2 Select the alarms or events that activate the LEDs.

Step 3 If a buzzer is required, (integrated in UIM but not in UIL), select the event that
activates the buzzer from the drop-down menu and untick the checkbox
“Disable”.

Step 4 To create a “Stop Alarms” button at the top of the browser page, select “Display
an Alarm Stop Button”.

Step 5 If required, disable Password for Battery Functions/Alarm Stop by means of the
appropriated checkbox.

Step 6 If required, activate numerical password for UIM / UIL by checking the
“Numerical” checkbox.

Step 7 Click “Accept Changes”.

Configuration instructions, ORION controller Configuration 115

 Note! Toggling from “Standard” to “Numerical” password and vice versa always
resets the default password.
(“Standard: Keys <↑> <↑> <↓> <EXIT> <EXIT> <ENTER>;
Numerical: Numbers <1> <2> <3> <4>).

Figure 7. User interface dialogue

2.16.5.2 UIM interface

2.16.5.2.1 LED assignment

The LED assignment of the ORION is displayed in the UIM.

Step 1 Go to ALARM → LED ASSIGNMENT.

Step 2 Select external input events for the correct ORION interfaces in this menu
(Digital Inputs). For the external events to appear in the drop-down menu, they
must be created in the event definition menu.

2.16.5.2.2 Enabling/disabling the buzzer

The buzzer can be enabled/disabled via UIM.

Step 1 Go to CONFIGURATION → SYSTEM → UIM BUZZER.

Step 2 Select either “Yes” or “No” for “Disable”.

2.16.5.2.3 Silencing an active buzzer

When the buzzer is active, the user can silence it for 30 minutes by pressing EXIT button.

116 Configuration instructions, ORION controller Configuration

2.17 Configuring AC measurements
ORION supports three different kind of AC measurements:

External

The AC parameters are measured by an external three-phase AC measurement device

which is connected over a gateway to the controller.

Internal

The rectifier or rectiverter modules measure the input AC voltage and these
measurements are used to show the input AC voltages of the system on web GUI and on
the display of the controller. With single-phase rectifiers, the assignment of modules to
the phases can be manual or automatic depending on the rectifier type and the system
HW. In single phase system or when using three phase rectifiers or rectiverters, no phase
assignment is needed.

HPS

The AC parameters are measured by the HPS ID:A1 module connected via IMBUS to the
controller.

2.17.1 Selecting the AC measurement type

AC measurements can only be configured through the web user interface.

2.17.1.1 Web user interface

Step 1 Go to Configuration → Options.

Step 2 Select “external”, “internal - single phase RM”, “internal three phase RM”, “HPS”,
“automatic 3-PH slot assignment”, “internal – single phase system” or
“rectiverter” from drop-down menu.

Step 3 Click “Accept Changes”.

If an AC Measurement Type is configured, Phase failure detection can be

enabled.

Step 4 Go to Configuration → Rectifier → AC Failure.

2.17.2 Configuring external AC measurement

The ACM1 is a gateway between the ORION and an external 3 phase AC-measurement
device, using RS 485 interface with MODBUS protocol. The commissioning procedure is
possible through the web user interface.

Step 1 Go to Configuration → Options.

Configuration instructions, ORION controller Configuration 117

 Step 2 Select “external” from drop-down menu for “AC Measurement Type”.

Step 3 Click “Accept Changes”.

Step 4 Adjust the communication parameters on the AC measurement device. Set the
Hex switch on ACM1 accordingly.

Step 5 Go to Configuration → HW Setup → ACM.

Step 6 In the ACM Devices, enter name of the external AC measurement device.

Step 7 Click “Add ACM”.

Step 8 Click “Accept Changes”.

After a successful configuration/installation, the dialogue looks as shown in the following

figure and the measured values can be displayed.

Figure 8. ACM devices dialogue (after installation)

Click “Details” to view the IMBUS Device details.

2.17.3 Configuring internal AC measurement with single-phase

rectifiers

2.17.3.1 Systems without converter positioning

In case physical addressing is not used in the system, the phase assignment of single-
phase rectifiers needs to be manually according to the following instructions. The purpose
of the assignment is to tell ORION which rectifier modules are connected to phases 1, 2
and 3.

2.17.3.2 Web user interface

Step 1 Go to Configuration → Options.

Step 2 Select “internal – single-phase RM” from drop-down menu for “AC Measurement
Type”.

Step 3 Click “Accept Changes”.

Step 4 Go to Configuration → Rectifier → AC Measurement.

118 Configuration instructions, ORION controller Configuration

 Step 5 Select the line where to assign rectifiers first.

Step 6 Click “Start”.

Step 7 For the rectifier connected to the selected phase, click “Config”.

Step 8 Click “Finish”.

Step 9 Select the next phase and repeat the steps 7 and 8.

Step 10 Verify the assignment status at the page Status → Rectifier

2.17.3.3 Touch UI interface

The selection of the AC Measurement Type cannot be done via Touch UI, but the phase
assignment is possible.

Step 1 Go to Menu → Rectifier → Phase Assignment

Step 2 Select the line where to assign the rectifiers

Step 3 Select “Start Assignment”

Step 4 For the rectifier connected to the selected line, press the “Config” button.

Step 5 Select “Finish Assignment”

Step 6 Repeat the steps 2-5 for all three lines.

Step 7 Verify that the Status has changed to “ok”.

2.17.3.4 UIM interface

The selection of the AC Measurement Type cannot be done via UIM, but the phase
assignment is possible.

Step 1 Go to CONFIGURATION → RECTIFIER → AC MEASUREMENT →

PARAMETER and press ENTER.

Step 2 Select the line where to assign rectifiers to

Step 3 Go to CONFIGURATION → RECTIFIER → AC MEASUREMENT → PHASE

ASSIGNMENT and press ENTER

Step 4 Select “Start” and press ENTER.

Step 5 For the rectifier connected to the selected line, click “Config”.

Step 6 Select “Finish”.

Step 7 Repeat the steps 1-6 for all three lines

Configuration instructions, ORION controller Configuration 119

 Step 8 Verify that the Status has changed to “ok”.

2.17.3.5 Systems with converter positioning

If the positioning of rectifiers is used and the AC measument type “Automatic 3-PH Slot
Assignment” is selected, the controller reads the three-phase voltages from the rectifiers
using following logic:

 L1 is read from the first, fourth, seventh, tenth... rectifier in the rectifier position
table
 L2 is read from the second, fifth, eight, eleventh... rectifier
 L3 is read from the third, sixth, ninth, twelfth... rectifier

The controller calculates the average voltage from the rectifiers connected to the same
phase. If the measurement is not plausible, it will be not considered in calculation.

2.17.3.6 Web user interface

Step 1 Go to Configuration → Options.

Step 2 Select “Automatic 3-PH Slot Assignment” from drop-down menu for “AC
Measurement Type”.

Step 3 Click “Accept Changes”.

2.17.4 Configuring internal AC measurement with three-phase

rectifiers

2.17.4.1 Web user interface

Step 1 Go to Configuration → Options.

Step 2 Select “Automatic 3-PH Slot Assignment” from drop-down menu for “AC
Measurement Type”.

Step 3 Click “Accept Changes”.

2.17.5 Display of AC measurement

The AC measurements can be seen at:

Interface Menu point Note

Web Status → AC Measurements

Touch UI Menu → AC Meas.

UIM STATUS → AC MEASUREMEN

120 Configuration instructions, ORION controller Configuration

3 Logging function
The Log function is used to store the system history in a persistent way. This functionality
writes measurements, events and built-in system messages to log files. The user has the
possibility to create several different log configurations. Each log configuration has a
name, a description, a set of measurements and events to be logged as well as the
sampling criteria and rules for the files management. The ORION can handle up to 18
user defined log configurations and additionally there is a Default Log to store system
messages. This document provides information about using the Default Log. To work with
user defined logs, see a separate logging manual.

Note! The logging function can only be configured through the web user
interface.

3.1 Setting up the default log via web user interface

Step 1 Go to Log → Setup.

Step 2 Click “Edit” button of the Default log.

Step 3 Click “Captured Events Selection”.

Step 4 Select the events to be captured and click “Add”.

Step 5 Click “Back” to return to the Log Editor page.

Step 6 Select the check box “Unix Time” in case you need to have the time stamp also
as Unix time in the log

Step 7 Select the language from the drop-down list.

Step 8 Set the maximum number of log entries in a log file (100 .. 10 000).

Step 9 Select the check box "Excel Compliant" to help Excel to open the log files
containing UTF-8 encoded characters

Step 10 Click “Accept Changes”.

3.2 Checking the log

When an event that has been defined as a Captured Event is activated, an entry is
recorded in the ORION log. The log can be read both from the web user interface and the
local display. The log entry records the date, time, and description of the event. The
description is in the form of the event name. The log differentiates between appearance
and disappearance of the event, as shown in Table 37.

Event Event state Description seen in the log of UIM & WEB

NameX True NameX

Configuration instructions, ORION controller Logging function 121

 False NameX – ok

Table 37. Log event descriptions

3.2.1 Web user interface

Follow this procedure to see the content of the default log:

Step 1 Go to Log → Status.

Step 2 Click the “Files” button for the Default log.

Step 3 Click the “View” button.

Follow this procedure to export the log file to PC.

Step 1 Go to Log → Status.

Step 2 Click the “Files” button for the Default Log.

Step 3 Click “Save to PC” and follow the instructions on the screen.

Follow this procedure to clear the default log:

Step 1 Go to Log → Status.

Step 2 Click the “Files” button for the Default Log.

Step 3 Select the check box “Delete”.

Step 4 Click “Accept Changes”.

3.2.2 Touch UI interface

Step 1 Go to MENU → LOG →SYSTEM to see the content of the default log

3.2.3 UIM interface

Step 1 Go to LOG → SYSTEM → ENTRIES. Press ENTER to open the log entries.

Step 2 To clear the log, go to LOG → SYSTEM → ENTRIES. Press ENTER.

3.3 Storing log files to USB memory

It is possible to store all log files into a USB memory, by using the Touch interface

122 Configuration instructions, ORION controller Logging function

 Step 1 Plug in a USB memory to ORION Touch. The File Manager opens automatically

Step 2 Select “Store Logs” from the list and follow the instructions on the screen

Configuration instructions, ORION controller Logging function 123

4 User and session management
To control access from different locations to the ORION Configuration and Supervision
Tool, ORION has a build in User and Session Management System. It enables creating
user profiles with different access rights, for example, for configuration, maintenance,
operating, and monitoring.

Each login generates a session, which runs until the user logs out or until ORION
terminates it under certain circumstances. ORION supports multiple concurrent sessions,
but only one user can have write access. To track the login/logout activities, a default log
entry is generated every time someone logs in or out of the controller.

The User and Session Management is located in the web user interface
(ORION Configuration and Supervision Tool) menu:

Configuration → System → User Management

Figure 9. User management dialogue

4.1 Default user profiles and access levels

ORION has only one default user named “Admin”. Admin can add and delete other users
and manage the settings of user/session parameters. Admin can export the user profiles
as a file to PC, and load such file from PC to ORION.

Table 38 describes the default users that are defined in the default user file stored in
ORION. We recommend that at least the passwords are changed after commissioning
the system. Each user can edit his own password. The administrator can edit all
passwords.

124 Configuration instructions, ORION controller User and session management

 Username Default password Access Profile

Admin orion Configuration

configuration orion Configuration

maintenance orion Maintenance

operator orion Operating

monitor orion Monitoring

Table 38. Default usernames

With different user profiles, the administrator can optimize the use of the ORION
Configuration and Supervision Tool for different user groups. The different access profiles
define the parameters and measurement displays editable/visible to the user.

Table 39 explains the differences between the possible access profiles.

Access Profile User rights

Configuration Enables the user to configure the system and edit all the
parameters.

Maintenance Enables the user to edit some configuration menus and

all the parameters.

Operating Enables the user to edit some parameters.

Monitoring Only view rights to ORION Web user interface.

Table 39. Access profiles and user rights

Note! Admin can configure users with any access profile as read-only.

4.1.1 Delta’s recommendation for user profiles

Note! Delta recommends that the default user profiles are only used as access
profiles during commissioning. The administrator should then create new user
profiles according to the organization and delete the default ones. The easiest
way to do this is to load in a new user file.

Use the following procedure when commissioning ORION power system.

Step 1 Change the password for “Admin” user profile.

Step 2 Create new user profiles one by one according to the organization requiring
access to the ORION, or load in the complete set of users as a user file.

Configuration instructions, ORION controller User and session management 125

 Step 3 Delete the default or unused user profiles.

Step 4 Distribute the new user profiles to the respective users, and instruct the users
how to log in and change their passwords.

4.1.1.1 Adding a complete set of user profiles by loading in a user file

Step 1 Go to Configuration → System → User Management.

Step 2 In the “Parameter” section, click “Load File from PC”.

Step 3 Choose a file and click “Start”.

Step 4 Wait until the new user file has been uploaded successfully.

4.1.1.2 Adding a single user profile

Step 1 Go to Configuration → System → User Management.

Step 2 In the “User Profiles” section, enter the name of the new user profile and click
“Add User”.

Step 3 Select “Access Profile” for the user.

Step 4 Select “Access”.

Step 5 Select language for the user (if other than English).

Step 6 Enter the password.

Step 7 Click “Accept Changes”.

4.1.1.3 Changing password

Step 1 Log in to the ORION Configuration and Supervision Tool as the user the
password change concerns.

Step 2 Go to Configuration → System → User Management.

Step 3 Click “Change Password”.

Step 4 In the Password Editor dialogue, enter the old password and the new password
(twice).

Step 5 Click “Accept Changes”.

4.1.1.4 Editing user profiles

Step 1 Go to Configuration → System → User Management.

Step 2 Click “Edit User Parameter”.

126 Configuration instructions, ORION controller User and session management

 Step 3 In the User Data Editor dialogue, select the “Access Profile”, “Access” and the
language for the user.

Step 4 Click “Accept Changes”.

4.1.1.5 Deleting a user profile

Step 1 Go to Configuration → System → User Management.

Step 2 Select the checkbox for the user profile you want to delete.

Step 3 Click “Accept Changes”.

4.1.1.6 Saving the user profiles to PC

Step 1 Go to Configuration → System → User Management.

Step 2 In the “Parameter” section, click “Save to PC”.

Step 3 Follow the instructions on screen.

Note! The user file can also be saved by using the file manager Configuration →
System → File Manager.

4.1.1.7 Deleting the user file

Step 1 Go to Configuration → System → File Manager.

Step 2 Select the checkbox for the user file.

Step 3 Click “Accept Changes”.

Note! Only Admin can delete the user file. As soon as the user file is deleted, all
running sessions of other users are terminated and the Admin profile parameters
are set to default values.

4.2 Radius
Remote Authentication Dial-In User Service (RADIUS) is a networking protocol that
provides centralized Authentication, Authorization and Accounting (AAA) management for
users who connect and use a network service. ORION can be configured to work as a
RADIUS client which is able to forward login authorization requests for a Remote Access
Server (RAS) in order to gain access to the ORION WEB GUI.

When RADIUS is enabled, but the authentication fails or the RAS is not reachable,
ORION falls back to the normal local user’s (built-in users) authentication process.

Configuration instructions, ORION controller User and session management 127

 Parameter Description

Server Address The RAS address

Server Port The RAS port number

Authentication PAP or CHAP. Please refer to RFC-2865.

Method

Server Shared The RAS shared secret

Secret

Group Configuration The RAS user role to map on the ORION Configuration role

Group Operation The RAS user role to map on the ORION Operation role

Group Monitor The RAS user role to map on the ORION Monitor role

Language The default language for all the users authenticated via RAS

Fallback Policy In case the “CLASS” (#25) is not available or there was not a
matching entry available the selected policy will be chosen

4.2.1 Enabling and configuring RADIUS

Step 1 Go to Configuration → Options.

Step 2 Tick the “RADIUS” checkbox.

Step 3 Click “Accept Changes”.

Step 4 Go to Configuration → User Management.

Step 5 Click “Edit RADIUS Parameters” and set the parameters according your RAS
setup.

Step 6 Click “Accept Changes”.

4.3 Session management

At login, a set of parameters are collected and monitored by the session manager.
Depending on the access profile, the following information can be available for the user.
The information is viewed as read-only.

Parameter Description

Session Owner Username of the session.

IP address IP address of the client (IPv4/IPv6. That is the computer running

the Browser).

Session Type Indicates from which channel the session was initiated. (Web,
REST-API, HTTP-API)

Session State Each session runs through a set of state between login and

128 Configuration instructions, ORION controller User and session management

 cleanup by ORION.

DB Access Indicates what database access this session has. Only one
session can have read-write access at the same time!

Last Access [s] Time in seconds since the last request for an object from the
web server.

Table 40. Available session manager information parameters

4.3.1 Login control

The controller manages unsuccessful login attempts in order to prevent misuse of existing
user accounts. For each user account, the controller counts the login attempts with
incorrect password. If too many incorrect passwords are typed in within a given time, the
user account is locked out.

The functionality is configured by three parameters.

Parameter Description

Allowed Retries Number of failed login attempts to cause lockout of the

account

within Timeframe for counting login attempts

or Lockout for Duration of the lockout of the account

Table 41. Parameters for Login control

4.3.2 Common parameters

With Administrator rights, the user can edit the Parameters of Session Manager, shown in
Table 42.

Parameter Description

Max sessions Total number of (WEB) sessions running at the same time.

Session Timeout After Determines the idle time to terminate a session.

Table 42. Session manager common parameters

4.3.2.1 Editing common parameters

Use the following procedure to edit a common parameter.

Step 1 Go to Configuration → System → Session Management.

Step 2 In the “Parameter” section, click “Edit”.

Configuration instructions, ORION controller User and session management 129

 Step 3 Edit the parameters and click “Accept Changes”.

4.3.3 Priority of local access

The local user has higher priority over the remote web users. As soon as the local user
changes the configuration via UIM/UIL, the remote session will be terminated.

130 Configuration instructions, ORION controller User and session management

5 Inventory report
After the commissioning of the system is completed, it is recommended to upload two
files to PC and store them into an archive:
 Setup file.
 Inventory report

The Inventory Report file contains a list of all modules connected to IMBUS. The following
data is saved for each module:

 Module type
 Part Number
 Serial Number
 HW Revision (Top Level)
 SW Version and Build Number

The following data is saved for the ORION controller:

 Part Number
 Serial Number
 HW Revision (Top Level)
 Software Version and Build Number

5.1 Creating an inventory report

Use the following procedure to create an inventory report and download it into PC:

Step 1 Go to Status → ORION Options.

Step 2 Click “Create”.

Step 3 Once the report is ready, click “Save to PC” and follow instructions on screen.

The created file is saved on the ORION controller. A previously created report will always
be overwritten when a new one is created. The Inventory Report file also appears in the
file manager, where it can be deleted or downloaded as well.

The file has a readable text format (ASCII) and all the labels are written in English.

It is possible to create an inventory report by using an SNMP command and retrieve it

from ORION by using HTTP API.

Note! Inventory information is gathered after the system boot from each
connected imbus module. Depending on the system size, collecting the
information can take 2 to 5 minutes. It is recommended to wait at least 5 min
after the system boot to get correct information.

Configuration instructions, ORION controller Inventory report 131

6 Controller backup
ORION supports two different backup functionalities that are designed for different
purposes: Automatic backup to microSD card and a manual backup to a PC or a USB
memory.

6.1 Automatic Backup

The automatic backup functionality keeps the full copy of ORION in a microSd card. This
backup can be used in field if the controller fails. The functionality of the old controller can
be moved into the new hardware by moving the microSD card, and no time consuming
manual configuration is required.

Note! The environmental conditions can be harsh which puts very high
requirements on the SD card to be used. Only high quality SLC memory cards,
developed for industrial applications, can guarantee the required data retention
at elevated operating temperatures. SC cards that are sold for consumer
products do not serve the purpose.

The SD card must support:

 SLC technology
 SD and SDHC standards (no SDXC)
 512MByte minimum space
 Temperature range from -40°C to +85°C.
 Read Retry including inbuilt threshold voltage shift to compensate high
temperature differences
 Built-in power fail protection

Delta recommends using the SLC 512MB S-450u, an industrial grade micro SD card from
Swissbit (p/n SFSD0512N1BM1TO-I-ME-221-STD; https://www.swissbit.com/). This card
is worldwide available from Digikey (http://www.digikey.com/) and other distributers.

6.2 Enabling the automatic backup

Use the following procedure to enable the automatic backup:

Step 1 Pull out the controller from the shelf

Step 2 Insert the microSD card into the card slot

Step 3 Insert the controller into the shelf.

Step 4 When the controller has started, log into the web interface and enable the
automatic backup at: Configuration → System → File Manager.

132 Configuration instructions, ORION controller Controller backup

6.3 Replacing a controller in field
Use the following procedure to replace a faulty controller in field:

Step 1 Pull out the old controller from the shelf and remove the microSD card.

Step 2 Insert the microSD card into the card slot of the new controller

Step 3 Insert the controller into the shelf.

Step 4 When the controller starts up, it will ask if the backup from the microSD card
should be used. Please confirm.

6.4 Manual backup

By using the manual backup the user can store the copy all files as one package into the
PC or a USB memory. This package can be used to clone one controller with all
configuration settings, language and all other files to another controller or to multiple
controllers.

When creating the backup, the user can choose whether to include the software file into
the backup or not. The backup withour the software is naturally smaller and thus easier to
distribute to the sites when doing functional upgrade, but the user has the responsibility to
make sure that the backup is compatible with the existing SW in the controller. With the
full backup file, there is no possibility for incompatibility.

When restoring the setup, the user can choose whether to overwrite the communication
settings or not. Keeping the communication settings is useful when upgrading the
controller configuration remotely by loading in a complete backup file. The user can also
choose whether to keep the “System Specific Settings” or not. These settings include
calibration and energy data and log files. This option is useful when upgrading controllers
SW and settings by using a backup file.

Backup/Restore procedure can be triggered either over Web or from USB device in case
a controller version with USB port is used.

6.4.1 Saving a backup manually to PC

Use the following procedure to create a backup and save it to PC:

Step 1 Go to Configuration → System → File Manager.

Step 2 Click Create Backup “Without Software” or ”With Software”and follow the
instructions on the screen.

6.5 Restoring backup from PC

Configuration instructions, ORION controller Controller backup 133

 Note! The possibility to create a backup file without SW was introduced in the
SW version V8.40. The earlier SW versions do not recognize this kinf of backup
file, so it cannot be loaded into controllers having SW vesion lower than V8.40.

Use the following procedure to restore the backup to ORION:

Step 1 Go to Configuration → System → File Manager.

Step 2 From the “File Type” drop-down list select “ORION Backup” and click “Load File
from PC”.

Step 3 Optionally select “Preserve Communication Settings” and/or “Preserve System

Specific Settings” if you do not want to overwrite the local system settings.

Step 4 Optionally select “Preserve Documents if you do not want to overwrite the locally
stored documents

Step 5 Click “Choose File” and choose the ORION Backup file to be transferred, and
select it.

Step 6 Click “Start”.

The progress of the restoration will be displayed. If an error occurs, the update procedure
will stop. Upon completion, the ORION will automatically reboot with the settings defined
in the backup file.

Note! Please be aware that all the previous settings will be lost if the options
“Keep Communication Settings” and/or “Keep System Specific Settings” are not
selected . Only the license key for Software features and the LCD contrast
settings will be kept.

6.5.1 Saving backup manually to USB memory

Use the following procedure to create a backup file and save it to a USB memory:

Step 1 Plug in the USB storage device.

Step 2 On the LCD screen, the menu FILE MANAGER appears automatically.

Step 3 Push the command “Create Backup With SW” or “Create Backup Without SW”
and wait until “Backup created” is shown.

Note! If you pull out the USB storage device while creating the backup, the
operation is interrupted and an error is shown.

6.5.2 Restoring backup manually from USB memory

Use the following procedure to restore the backup to ORION:

134 Configuration instructions, ORION controller Controller backup

 Step 4 Plug in the USB storage device having the backup file.

Step 5 On the LCD screen, the menu 6.11 FILE MANAGER appears automatically.

Step 6 Press the command “RESTORE BACKUP” or “RESTORE BKP NOCOM”.

Step 7 Choose the archive to load the backup from and wait until the controller reboots.

Note! If you pull out the USB storage device while restoring backup, the
operation is interrupted only if it cannot be finished without the USB device (i.e. if
the archive was already copied to the controller, the restore operation
continues).

Configuration instructions, ORION controller Controller backup 135

7 Document storage
ORION has a dedicated storage space that can be used for stroring documents such as
user manuals, circuit diagrams and installation and commission reports. The maximum
space is 50 MB. The user can upload and download the documents via web interface and
also open them directly in the web browser if the file type is supported by the browser.

There is a dedicated menu point “Documents” for document management, but the
documents are accessible also via File Manager.

136 Configuration instructions, ORION controller Document storage

 Appendix 1

Connecting ORION to a computer via LAN port using manual

mode

Use this procedure to set the IP address of the computer manually to enable
communication with ORION.

Step 1 Enable the manual mode in ORION by using the local user interface
Touch UI: MENU  Network  IPv4
UIM: NET CONFIG → ETHERNET → IPv4→ MODE.

Step 2 Set the IP address of the computer to the same network area as the computer.

Example: The IP address of ORION is 192.168.100.100. The IP address of the

PC can therefore be, for example, 192.168.100.101.

Step 3 Set the subnet mask of the PC to 255.255.255.0.

Step 4 Connect the computer to the ORION LAN connector with the appropriate cable.

Step 5 Open an internet browser and connect to the IP address of the ORION.

Note! If the IP address contains a zero or zeroes after a period, remove the
zeros, for example, 010.120.177.031 → 10.120.177.31.

Step 6 When the ORION login page loads, enter the username and password, and click
“Submit”.

Step 7 The web interface is now open and it is possible to change the configuration and
setting if necessary.

Step 8 Click “Logout” when you are ready.

Note! If the browser cannot connect to the ORION, check the proxy server
setting in the browser options. A proxy must not be used.

Configuration instructions, ORION controller Document storage 137

 Appendix 2

Connecting to a computer with fixed IP address that the user

cannot change

Use this procedure in case the user has no privileges to change the IP settings of the
computer and a fixed IP address is used.

Step 1 Enable the manual mode in ORION by using the local user interface
Touch UI: MENU  Network  IPv4
UIM: NET CONFIG → ETHERNET → IPv4→ MODE

Step 2 Set the IP address of the ORION using the local interface to the same network
area as the computer. Only the numbers in the last section of the IP address can
be different.

Example: The IP address of the computer is 170.20.110.101. The IP address of

the ORION can therefore be, for example, 170.20.110.102.

Step 3 Set the subnet mask of the ORION to 255.255.255.0

Touch UI: MENU  Network  IPv4
UIM: NET CONFIG → ETHERNET → IPv4→ SUBNET MASK

Step 4 Connect the computer to the ORION LAN connector with the appropriate cable.

Step 5 Open an internet browser and connect to the defined IP address of the ORION.

Note! If the IP address contains a zero or zeros after a period, remove the
zeros, for example, 010.120.177.031 → 10.120.177.31. When the ORION
configuration and supervision tool login page loads, enter the username and
password, and click “Submit”.

Step 6 The web interface is now open and it is possible to change the configuration and
setting if necessary.

Step 7 Click “Logout” when you are ready.

Note! If the browser cannot connect to the ORION, check the proxy server setting
in the browser options. A proxy must not be used.

138 Configuration instructions, ORION controller Document storage

Configuration instructions, ORION controller Document storage 139
140 Configuration instructions, ORION controller Document storage
*5017208000_06* 5017208000_06