news in exo 2014 - regincontrols.com€¦ · news in exo 2016 ed 2 compared to ed 1 5 ... exo 2016...

News in EXO 2016 Edition 2

DISCLAIMER

The information in this manual has been carefully checked and is believed to be correct. AB Regin however, makes no

warranties as regards the contents of this manual and users are requested to report errors, discrepancies or ambiguities to

AB Regin, so that corrections may be made in future editions. The information in this document is subject to change

without prior notification.

The software described in this document is supplied under licence by AB Regin and may be used or copied only in

accordance with the terms of the licence. No part of this document may be reproduced or transmitted in any form, in

any fashion, electronically or mechanically, without the express, written permission of AB Regin.

COPYRIGHT

© AB Regin. All rights reserved.

TRADEMARKS

EXOdesigner, EXOreal, EXO4, EXOscada, EXOcompact, EXOflex and EXOline are registered trademarks of AB

Regin.

Windows, Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2012, SQL

Server 2008, SQL Server 2012 and Excel are registered trademarks of Microsoft Corporation.

Some product names mentioned in this document are used for identification purposes only and may be the registered

trademarks of their respective companies.

April 2016

Table of Contents

Chapter 1 Overview 5

News in EXO 2016 Ed 2 compared to Ed 1 5

News in EXO 2016 compared to EXO 2015 6

Chapter 2 Installation 12

Requirements 12

Supported web browsers for EXOscada 12

Alarm sending in EXOscada 12

EXO 2016 installation 12

Licenses 13

SQL Server 2014 13

Chapter 3 Compatibility 14

EXOscada 14

Using an existing EXOflex program for an EXOclever

EC-PU4 14

Time Channels 3.0 14

Modbus Slave 4.0 15

Alarms & Events 4.1 15

Display 5.0 15

Chapter 4 EXOdesigner 16

Support for new controllers EXOclever and EXOdos 16

Configuration of EXOclever EC-PU4 16

Configuration of EXOdos controllers 17

Modbus Slave 4.0 18

Adding Modbus Slave 4.0 to a controller 18

Configuring ports for Modbus Slave 4.0 18

Modbus Slave configuration tool 19

Adding objects directly from Controller Builder 23

Time Channels 24

Adding Time Channels (ver 3.0) to a controller 24

Time Channels tool 25

Controller Builder 36

Import I/O list 36

Export I/O list 36

New function blocks 36

Popup editor 44

EXOtrend 45

Display 48

Adding Display (ver 5.0) to a controller 48

Display tool 49

Chapter 5 EXOscada 59

Users Overview 59


Chapter 1 Overview

This document describes the new features in EXO 2016 Edition 1 and 2.

In addition to the new features and bug fixes described in this document, these editions also

contain many minor error corrections not described.

News in EXO 2016 Ed 2 compared to Ed 1 EXO 2016 Edition 2 has the following main news and bug fixes:

New modern Display tool. See section Display.

New real time chart, EXOtrend. See section EXOtrend.

New popup editor in Controller Builder and other tools. See section Controller Builder.

See also the detailed list of news and bug fixes below.

EXOdesigner

The Sum Alarm standard object is now compatible with Alarms and Events 4.1

Controller Builder

All twin pump blocks are updated with a new Run Indication Delay parameter,

necessary in applications where it might take a while for run indication to be received.

The Start Debug button will now debug All points or debug Connections, depending

on the type of debug that is selected in the Tools menu.

EXOscada

The EXOscada View Designer templates for RCP, Regio Midi and RCF have been

updated with an option to add a smaller “basic” Regio view instead of the ordinary view.

The basic view is intended for users who are not interested in advanced settings, room

illustration, central time channels etc. The basic view is also auto-adaptable to any

connected Regio model and its current configuration.

Italian and portuguese can now be chosen as languages when logging in to the

EXOscada site.

Bug fixes

System Function 2.0

If a controller was configured to have both a slave port and a master port, the Mode

attribute for the slave port was set to Slave, routing by table. It is now

correctly set to Slave, routing to port x instead.

It was not possible to set the Mode attribute for serial ports to Slave, routing to

port 2 and Slave, routing to port 3.

6 News in EXO 2016

The Format attribute for serial ports was in reality always set to Odd parity,

regardless of which type of parity was selected in the tool.

If a static IP address had been selected for a controller, it looked like the TCP/IP port

attribute Subnet Mask was configured to 255.255.255.0 in the tool as default even

though it wasn’t. The Subnet Mask attribute is now empty as default.

The Min PLA, Max PLA, Min ELA and Max ELA attributes configured automatically

by Project Builder were incorrectly shown as 0, 255, 0, 255.

Time Channels 3.0

A major bug in the advanced objects in the new time channels tool has been fixed. This

bug could cause a time channel to give a faulty output when advanced objects were

used.

If you have configured any controllers using advanced objects in the new time

channel tool, please open the time channels tool for those controllers in EXO 2016

Edition 2, save, and reload the controllers.

Controller Builder

A compatibility issue with non-EXOreal C controllers in the Acknowledge All Alarms

function block has been fixed.

News in EXO 2016 Ed 1 compared to EXO 2015 EXO 2016 Edition 1 has the following main news and bug fixes:

Support for EXOdos, EXOclever, Presigo and our new Modbus transmitters.

New tool for the native Modbus Slave function (TCP/IP and serial) in EXO controllers.

New modern Time Channels tool

Longer Alarm delay and new state variables in the Alarms & Events function

New view that shows currently logged in users in EXOscada, and has functionality for

Sysadmins to chat with other users.

Official support for Windows 10.

A lot of news and improvements in the standard template libraries.

See the detailed list of news and bug fixes below.

EXOdesigner

General

Support for the new EXOdos and EXOclever controllers. See more information in

chapter Support for new controllers EXOclever and EXOdos.

New Time Channels tool which replaces the old tool. See more information in chapter

Time Channels.

New tool Modbus Slave 4.0. See more information in chapter Modbus Slave 4.0.

EXOreal version 3.3-1-03 is included.

New version of the Alarms & Events function (ver 4.1) that is default for all controller

templates. It is compatible with ver. 4.0. There are two main news in this new version:


Alarm delay can be set to up to 504 hours (was max. 6 hours in ver. 4.0).

New state variable Variable_State that indicates whether the alarm is on

or off after the alarm delay (follows the Alarm Status, On if alarm is active or

acknowledged).

Several new Modbus Master templates are added, for:

Danfoss VLT FC Series (frequency inverter)

Regin CTHRC2/-D (new CO2, humidity and temperature transmitters)

Regin CTRC2/-D (new CO2 and temperature transmitters)

Regin TRTC5/-D (new temperature transmitters)

The RCP controller templates are updated with support for Regio Maxi 1.4.

Debug Browser now shows all areas and controllers on all levels in the items list in the

right side of the window when Debug Browser is opened.

Debug Browser now remains open when EXOtest is started.

In all tools, handling of shared templates has been improved.

There is a new button Change shared folder in both the Export… and Add…

dialog windows for changing the remote root folder of shared templates.

After clicking the Download shared templates button, the message now states

whether shared templates have been downloaded or if there were no shared

templates to download.

The attribute Bit rate (bps) of the Modbus Master object in Modbus Master tool can

now has some additional bit rates that can be chosen. The alternatives are now: 1200,

2400, 4800, 9600, 14400, 19200, 28800, 38400, 57600 and 76800.

New attribute Format added for serial ports in System Function 2.0. It is used to set the

type of parity (No parity, Even parity, Odd parity or No parity + 2

stop bits)

New attribute Message timeout added for TCP/IP ports in System Function 2.0.

Controller Builder

Configuration of Modbus Slave.

Configuration of I/O Modules for EXOclever.

Configuration of Universal Analog I/O:s (used in EXOdos controllers).

Active and inactive alarms now have different colored symbols.

Possibility to import a list of I/O:s. Functionality has been added to the Inputs and

Outputs dialog window to import a list of I/O points from a CSV file. This makes it

possible to export an I/O-list from Controller Builder, edit the I/O-list in for example

Microsoft Excel and then import it in Controller Builder. See more information in

chapter Controller Builder.

More historical values added to the Run-Time Meter function block.

Run-time outputs from function blocks now always show Hour and Minute separately,

so no decimal values of an hour are shown. The following blocks are updated:

8 News in EXO 2016

Device Start Control

Extended Operation

All Fan blocks

Optimizer

Rotating Exchanger

All single/twin pump blocks

New function blocks (See more information in chapter Controller Builder):

Presigo with 1 Sensor / Presigo with 2 Sensors.

Signal Trend Control

Acknowledge All Alarms

Care Taker

Time Channel (ver. 3.0)

All pump and fan function blocks are updated with a new parameter Status Switch

Delay which allows setting a delay before the Status output is changed.

Function blocks Set External … Variable are updated with an alarm signal output for

communication failure, Com. Failure Alarm. The number of communication attempts

executed before the alarm signal is set is specified by the No. of Attempts parameter.

Function blocks Read External … Variable are updated with an alarm signal output for

communication failure, Com. Failure Alarm. The number of communication attempts

executed before the alarm signal is set is specified by the No. of Attempts parameter.

As soon as Com. Failure Alarm is set, the value of the new input FallBack Value is

forwarded to the output.

Function blocks Transfer External … Variable are updated with alarm signal outputs

for communication failure, Com. Write Failure Alarm and Com. Read Failure

Alarm. The number of communication attempts executed before the alarm signal is set

is specified by the No. of Attempts parameter. As soon as Com. Read Failure Alarm

is set (communication from source unit is down), the value of the new input FallBack

Value is forwarded to the external variable specified by the input Set Variable.

The function block Degree Days have two new counters added for accumulating degree

days this year (This Year Degree Days) and degree days previous year (Previous Year

Degree Days). A Reset command is also added, which resets the counters Degree Days

and This Year Degree Days to their corresponding reset points (Reset Point Total,

Reset Point This Year).

EXOscada

A new view, Users Overview, is added for system administrators. It shows currently

logged in users and user info, with possibility to chat with them separately. The system

administrator can also make a forced logout of users, if e.g. maintenance is planned. See

more information in chapter Users Overview.

In order to get this view in a current project, the project needs to be upgraded. Select the

EXOscada object in Project Builder, then select Upgrade project to current

EXOscada version in the Tools menu.

An Add to trend view button is added to all relevant Operation popup views connected

to the different function blocks in Controller Builder. This gives the possibility to add

any signal(s) in this view to a real-time trend chart.

Trend diagrams now displays logged values instead of average values.

Several new EXOscada templates with connections to the Controller Builder blocks are

added:

Analog Signal Scale


Damped Analog Signal

Signal Limiter Continuous

Weekly Event

Heating Curve Points

Heating Curve with Adaptation

Night Setback

Occupation Type Setpoints

Room Compensation

Start-Stop Optimization

Thermal Disinfection

Fire Damper Control

Setpoint Limitation Cascade


Presigo with 1 Sensor

Presigo with 2 Sensors

Care Taker

Leakage Power Measurement

Pink and turquoise pipe symbols added in EXOscada View Designer.

Shortcuts for the Communication Channels and Communication Routings tools are

added to the menu that is displayed when right clicking on the EXOscada icon in the

Windows taskbar.

Added Title attribute for the Symbol element. This is important for the Add to Trend

Window function.

It is now possible to get line breaks in the Value field of Text elements in EXOscada

View Designer by pressing Ctrl + Enter.

Bug fixes

The following bug fixes are included in EXO 2016 Edition 1:

EXOdesigner

If Project Builder crashed while data were being saved to Project.Exo, some data

could be lost in the project. Project Builder now creates a backup file of

Project.Exo.bak that only exists while the save operation is ongoing.

If Project Builder should crash while saving, the project can be restored by renaming

Project.Exo.bak to Project.Exo.

Closing Project Builder could sometimes cause it to crash and give a popup window

saying “Project Builder has stopped working”.

In a controller with display, when editing a numerical value via the display by

incrementing digit-wise (Up key) from a negative value, the value could not become

greater than 0(without doing a special work-around).

Variables that were created in an EXOL Variables block were not shown in the EXOL

Browser.

Many bug fixes for EXO Browser were released in EXO 2015 Edition 1 Patch 1. All of

these are of course included in EXO 2016 Edition 1, along with more improvements and

fixes to EXO Browser.

10 News in EXO 2016

In the Ventilating Control standard object, an error could cause the Run Mode to go

into a startup loop during defrost control.

Multipage VPac variables weren’t shown in EXOtest when using Debug browser.

If a template included an icon in the wrong format, it could cause the tools to crash when

used. Only .ico files should be used for icons. If any other formats are used, a default

missing icon will be shown instead.

When using the old Inputs and Outputs tool to configure controllers with expansion

units, port 2 was used as EXOline Master regardless of which port was configured as

Master port or Expansion Unit port.

When debugging in M-Bus Master tool, if a question from the master didn’t receive an

answer from the slave, the question wasn’t shown either. Now the question is shown

even if there is no answer from the slave.

The Stop bits attribute in Modbus Master tool did not have the correct default value for

all controller types. It now has default value 2 for all controllers. For those older

controllers that don’t support 2 stop bits, 1 stop bit will even if configured to 2 stop bits.

Setting port modes for a controller gave a syntax error in Init.tse if the project didn’t

include a main computer.

Setting Slave port to TCP/IP port and Master port to none for a controller gave a

false error message.

Installing EXO could overwrite Nimbus settings in existing third party projects with

Nimbus purchased directly from Trosoft (not via Regin).

Adding a controller containing System Function 2.0 to a project caused an error if using

German Windows.

Controller Builder

The Find and Replace command did not find all instances of a search string in some

cases.

A bug that could cause Controller Builder to crash occasionally.

Adding the Controller Builder function to an EXOflex and then pressing the Config

button wrongly gave an error message.

It was not possible to move objects up and down in the object tree using Alt + arrow

keys.

The Increase-Decrease Control function block could calculate open/close times

smaller than the task cycle time. For more accurate control, it is recommended to put

this block in a fast task.

It was possible for the function block Sum Alarm to get stuck in an alarm loop. To

avoid this, the internal alarms are removed and logic alarm outputs added instead.

In the function block Ventilation Control, an error could cause the Run Mode to go

into a startup loop during defrost control.

There was a serious issue with run-time controlled start order in the Device Start

Control function block. It is strongly recommended to update old blocks if this feature

is used.

There was a serious issue regarding the start of the last pump in the start order in the

Pressure Control 2…4 Pumps function blocks. It is strongly recommended to update

old blocks.

EXOscada

Several bugs that could cause EXOscada runtime to crash occasionally have been fixed.

Large projects should also run more smoothly in EXOscada now.

Alarm handling in EXOscada runtime was very slow, and is now much faster.


Auto login in EXOscada didn’t work if “Delete browsing history” was selected in some

web browsers. Note that cookies must be enabled for auto login to work.

The possibility to filter on Area did not work for the Alarms Status view, Alarm

History view, User log view and Events log view. This filter has now been removed.

To only show results for a specific area, select that area in the tree view to the left before

opening the aforementioned views.

When acknowledging an alarm in the Alarm Status view, if the order of the alarms had

been changed in the view, the wrong alarm could sometimes be acknowledged.

Pictures in EXO4 Web views were vertically aligned to the middle instead of to the top

of the view.

Alarm texts longer than 80 characters were truncated in for example the Alarm Status

View. The max. number of characters displayed has been increased from 80 to 100.

The Standard energy report (meter readings) and Standard energy/temperature

chart (meter readings) report templates had their displayed values delayed by one time

period (a weekly report had values delayed one week, a monthly report one month and

so on). These templates have now been adjusted to use logged signals with the function

Single Sample (End of period) instead of Single Sample (Start of period) to solve

this. Note that report views based on the existing templates cannot be upgraded, but have

to be recreated to get this fix.

The date format of the Date field in the Standard Report template has been changed

from Swedish to international format, YYYY-MM-DD. This can be changed to other

formats in the Excel file if desired.

Decimals were not shown in the Control Curve element.

If two views contained elements that opened popup windows with the same name, an

error would occur when trying to have both popup windows open simultaneously.

During login, the off-line splash screen was shown for a couple of seconds.

In the Historical Chart view, if events had long names, the names weren’t displayed

correctly.

In the Historical Chart view, the Close button in the Add signals dialog window

couldn’t be reached when using a display resolution of 800x600. This is now fixed

completely in Internet Explorer. In other web browsers, if the size of the diagram

window is changed, the window has to be closed and opened again for the Add signals

dialog window to look correct.

In the Historical Chart view, if both a digital and an analog signal were displayed, the

analog chart was offset horizontally compared to the digital chart and the x-axis.

In the Historical Chart view, in the Add signals dialog window, the filter function did

not work correctly and is now replaced with a search function.

EXO4 to EXOscada converter

.esc files converted from .emd didn’t get correct arguments for sub views.

Paths starting with EXOanim were not converted.

When multiple fonts are used in for example man/auto texts, they were all converted to

normal instead of what was chosen in the style converter.

EXOopc Driver

A number of bugs in EXOopc Driver have been fixed. If you are experiencing any

problems with EXOopc Driver, we recommend upgrading to the latest version.

12 News in EXO 2016

Chapter 2 Installation

Requirements EXO 2016 can be installed on 64-bit computers with the following operating systems only:

Windows 7 Professional (or better), with Service Pack 1 (or later)

Windows 8 Pro (or better)

Windows 8.1 Pro (or better)

Windows 10 Pro (or better)

Windows Server 2008, with Service Pack 2 (or later)

Windows Server 2008 R2, with Service Pack 1 (or later)

Windows Server 2012

Windows Server 2012 R2

It is also recommended to install all Windows Updates on your computer before installing

EXO 2016.

Supported web browsers for EXOscada

The following web browsers are supported:

Internet Explorer 10 or higher

Google Chrome 30 or higher

Microsoft Edge 20 or higher

In all cases Adobe Flash Player 15 or higher is also required.

Alarm sending in EXOscada

Alarm sending in EXOscada requires SQL Express or SQL Server 2008 or later. All other

functions in EXOscada and EXO4 works with older versions of SQL Express and SQL

Server.

EXO 2016 installation EXO 2016 is packed in a single installation, including EXOdesigner, EXOscada, EXO4,

EXOopc Driver and Adobe Flash Player. You can select to install a Full installation,

EXOdesigner only or Custom, which allows you to select which features to install.

Chapter 2 Installation 13

You can upgrade a computer with any older version of EXO. EXO 2016 is compatible with

the previous versions. See chapter Compatibility below for more information.

When installing on a computer with older operating systems the installation might need

access to Internet, to download installations from Microsoft's web page.

If you have an antivirus program installed, make sure to put the Regin folder (e.g.

C:\Program Files\Regin\) in the list of trusted programs/file paths.

Licenses To run EXOscada 2016, a new EXOscada 2016 Base license is needed.

SQL Server 2014

Normally, EXO 2016 is used together with SQL Express 2012, which is available on

Regin’s FTP server. The below information ONLY applies if you buy SQL Server

2014 separately.

SQL Server 2014 is tested with EXO 2016, and it works equivalent to SQL Server 2008 and

SQL Server 2012, i.e. you have to download and install a compatibility package before use.

This compatibility package can be downloaded from http://www.microsoft.com/en-

us/download/details.aspx?id=15748. For 64-bit operating systems, the name of the file to

download is SQLServer2005_BC_x64.msi, and for other operating systems

SQLServer2005_BC.msi.

http://www.microsoft.com/en-us/download/details.aspx?id=15748

http://www.microsoft.com/en-us/download/details.aspx?id=15748

14 News in EXO 2016

Chapter 3 Compatibility

EXOscada Projects created in EXO 2015 are compatible with EXO 2016, but to be able to use the new

Users Overview view in EXOscada, they have to be upgraded before use. This is done with

the command Upgrade project to current EXOscada version.

To upgrade a current project do the following:

1. Select the EXOscada object in Project Builder.

2. Select Upgrade project to current EXOscada version in the Tools menu.

3. In the Upgrade tool, click the Upgrade button.

Using an existing EXOflex program for an EXOclever EC-PU4

If you have an existing EXOflex program that you want to use with an EXOclever EC-PU4,

do as follows:

1. Create a new controller using the Controller – with general functions template and

select controller model EXOclever EC-PU4 in the dialog window.

2. Add the Objects function to the EXOclever controller.

3. Copy the configurations made in all tools except the I/O configuration and Alarms and

Events configuration from the EXOflex controller to the EXOclever controller.

4. Select the EXOclever controller and start Controller Builder.

5. Open the Inputs & Outputs dialog window using the button in the top right of the

window.

6. Create and configure the I/O modules in the I/O Modules tab.

7. Configure the I/O points in the Inputs and Outputs tab. The I/O points must have the

same names and configuration as they had for the EXOflex controller.

8. Create alarm points in Controller Builder using the Add… dialog, and give them the

same names as they had for the EXOflex controller.

9. Copy the alarm Input conditions from the old controller, with an added * at the

beginning. Also set all other settings as in the old controller.

10. Load the program to the controller using Setup Controller.

Time Channels 3.0 All versions of EXOscada/EXO4 runtime are compatible with Time Channels 3.0

The old and the new Time Channels tool are fully compatible with each other.

A time channels program created in the old tool can be opened in the new tool, and it

will be fully functional. However, the program will consist of advanced objects.

A time channels program created in the new tool can be opened in the old tool. If it is

then saved in the old tool, and opened in the new tool again, it will consist of advanced

objects, regardless of how it was originally created.

Chapter 3 Compatibility 15

We recommend that advanced objects in time channels programs that were

originally created in the old Time Channels tool are kept, and not replaced by new

objects.

The reason for this is that the variable names of new objects will be different from

the advanced ones, and the new objects are not compatible with all standard objects

in the Objects tool.

Modbus Slave 4.0 Modbus Slave 4.0 is not compatible with former versions, 3 or earlier.

Modbus Slave 4.0 is compatible with Modbus Master 2.0 and can be used in the same

controller.

Alarms & Events 4.1 Alarms & Events 4.1 is compatible with Alarms & Events 4.0. To upgrade existing

controllers do as follows:

1. Add the Alarms & Events (Ver 4.1) function to the controller.

2. Remove the Alarms & Events (Ver 4.0) function from the controller.

3. Enter the Alarms & Events tool or Controller Builder and save.

Display 5.0 Display 5.0 is compatible with Display 4.0.

A display program created in the old Display tool can be opened in the new Display

tool, and it will be fully functional.

A display program created in the new Display tool can be opened in the old Display tool

but has the following limitations:

- A maximum of 8 (4 pairs) variables can be used in the old Display tool. Any

additional variables configured in the new tool will be lost.

The 8 allowed variables in the old Display tool are in reality 4 pairs of variables,

where each pair has to have the same min and max values in the case of Numeric

elements and the same text lists in the case of Text select elements. In the new

Display tool there can be up to 35 variables, and variables are automatically paired

together.

- The following parameters do not exist in the old tool, and will therefore be lost:

o Visible

o User description

o Update Cycle

16 News in EXO 2016

Chapter 4 EXOdesigner

Support for new controllers EXOclever and EXOdos

Configuration of EXOclever EC-PU4

Configuration of EXOclever EC-PU4 controllers is done in Controller Builder. To create and

configure the I/O modules, open the Inputs & Outputs dialog window in Controller Builder

using the button in the top right of the window.

Create and configure the I/O modules in the I/O Modules tab.

Configure the I/O points in the Inputs and Outputs tab.

Configuring I/O modules in Controller Builder

The Inputs and Outputs dialog window in Controller Builder has a new tab called I/O

Modules. It is only available for EXOclever controllers and is used to configure the I/O

modules of an EXOclever controller.

The I/O modules are shown in a tree structure to the left, and the attributes of the selected

module in a list to the right:


Each I/O module has the following attributes:

Attribute Description Default

Type The type of the element, i.e. I/O module. Required

Name The name of the object. Required

Address The address of the module, which corresponds to the

position of the PIFA unit in the expansion housing.

Each module must have a unique address. When a new module is created, it is automatically assigned the first

available number.

Required

Model The model name. Required

Priority The PIFA’s priority to transfer values of the inputs and

outputs of the PIFA unit and the EXOL variables in the

controller.

2

Type of activation Type of activation, Automatic or Manual,

determines if the PIFA will automatically go to active or passive mode when the PIFA and the controller are

powered up and have made contact.

Automatic

Comment Description that is only displayed in the tool for the configurator.

-

New I/O modules are added by clicking the Add button.

When I/O modules have been added, they are shown in the Inputs and Outputs tab, where

each I/O point for the modules can be configured.

Configuration of EXOdos controllers

Configuration of EXOdos controllers is done in a very similar manner as other controllers,

for example EXOcompact.

The one thing that is different for the EXOdos controllers is the Universal Analog I/O

functionality.

The EXOdos controllers have 2 Universal Analog I/O:s (UA) that can be configured as

0…10 V analog inputs (AI9 and AI10) or as 0…10 V analog outputs (AO1 and AO2).

This is handled in Controller Builder in the same way as Universal Inputs for EXOcompact.

In EXOreal it is configured in the following way:

To configure the first UA as input, set AIMode9 to 9 and AQMode1 to 0.

To configure the first UA as output, set AIMode9 to 0 and AQMode1 to 1.

To configure the second UA as input, set AIMode10 to 9 and AQMode2 to 0.

To configure the second UA as output, set AIMode10 to 0 and AQMode2 to 1.

18 News in EXO 2016

Modbus Slave 4.0 Modbus Slave 4.0 is a controller function for using the built-in Modbus Slave functionality

in EXOreal C.

Modbus Slave 4.0 can only be used for controllers with EXOreal 3.2 or later.

Adding Modbus Slave 4.0 to a controller

1. Select the controller you wish to add Modbus Slave 4.0 to in Project Builder

2. Add Modbus Slave 4.0 using Add/Remove Functions in the Config menu.

To use Modbus Slave 4.0, System Function 2.0 must also be added to the

controller.

Configuring ports for Modbus Slave 4.0

Modbus Slave can be used on both serial ports and TCP/IP ports. No special configuration is

required for TCP/IP ports for this.

For serial ports, the configuration is done in System Function 2.0:

1. Select the controller and open System Function 2.0.

2. Select the port in System Function 2.0 and set Mode to Modbus Slave

3. Make any other configurations you wish to make, such as bit rate and save.


Modbus Slave configuration tool

When the function is added, a Modbus icon will be visible in the tool field. Click on the icon

to open the Modbus Slave tool.

The Modbus Slave tool is navigated using the tree structure on the left hand side of the

window. It can contain the following object types:

Object type Icon Description

Modbus Slave

The root object.

Coil

Boolean variable, read- and writable

Discrete Input

Boolean variable, read-only

Holding Register

Numerical variable, read- and writable

Input Register

Numerical variable, read- only

Group

Automatic

20 News in EXO 2016

Objects

Modbus Slave object

The Modbus Slave object is the root object and has configuration attributes divided into three

tabs:

General tab

Attribute Default value

Description

Type Required The object type.

Modbus

device

address

1 The Modbus address of the device. Can be specified in

decimal or hexadecimal format (started with 0x).

Comment - Multiline text field for comments.

TCP/IP tab


Description

Enabled No Specifies whether Modbus Slave should be active on the

TCP/IP port. (Yes/No)

Max no of

sessions

3 Number of sessions that should be allocated to Modbus.

(1/2/3/4/5)

Keep alive

interval

75 Keep alive interval in seconds, between 0 and 1000

seconds. 0 to disable.

Security

enabled

No Enables Modbus TCP security. Will only allow the below 5

IP addresses.

Allowed IP 1 - Allowed IP address #1.





Serial ports tab


Description

Serial Ports - Always shows the text “Use System Functions tool”. The

command button starts System Function 2 tool.

Group object

Each Group object has the following configuration attributes:


Description

Name - The technical name of the object.




Coil and Discrete Input objects

Each Coil and Discrete Input object has the following configuration attributes:


Description



Modbus data

address

Required The Modbus data address of the object. Can be specified in


The first available number is used as default value.

Mapping 0 Type of mapping from the EXOL variable to the Modbus

register:

- One L variable to a register (0)

- One BPac L value to a register (1)

Variable None Binding to an existing L type EXOL variable, starting with a *.

Holding Register and Input Register objects

Each Holding Register and Input Register object has the following configuration attributes:


Description



Modbus data

address

Required The Modbus data address of the object. Can be specified in


The first available number is used as default value.

Mapping 4 Type of mapping from the EXOL variable to the Modbus

register:

- One R variable to a register (4)

- One R variable to two registers as float (IEEE)(9-10)

- One H variable to two registers as long integer (13-14)

- One X variable to a register (1)

- Two X variables to a register (2)

- One I variable to a register (5)

- One BPac R value to a register (7)

- One BPac R value to two registers as float (IEEE) (11-12)

- One BPacH value to two registers as long integer (15-16)

- One BPac X value to a register (8)

- One BPac X values to a register (17)

- One BPac I value to a register (3)

Variable None Binding to an EXOL variable (type according to the

Mapping attribute), starting with a *.

Scale 10 Scaling factor for conversion when transferring to Modbus

registers. (Only available if Mapping is 4 or 7).

Offset 0 Offset for conversion when transferring to Modbus

registers. (Only available if Mapping is 4 or 7).

22 News in EXO 2016

Templates

You can create your own templates consisting of one or more objects. They can then be used

in the same or in other controllers.

Export to template

1. Select the object(s) that you want to export as a template.

2. Click Export to Template… in the Tools menu.

3. Enter a name for your template. You can also select an icon and enter a description for it.

4. Click the Export button.

Cross-reference list

A cross-reference list in pdf format can be generated using the Print Cross-Reference

command.


Print Cross-Reference

1. Click Print Cross-Reference List in the Controller menu.

2. Select how the entries in the list should be sorted, one of the following alternatives:

- Modbus object type and data address

- EXOL variable name

- As configured (the entries are displayed in the same order as in the tool)

3. Select the page orientation; Portrait or Landscape.

4. Click Print to generate the pdf.

Adding objects directly from Controller Builder

It is possible to add an object to Modbus Slave 4.0 directly from Controller Builder. This is

done in the following way:

1. Right click on a connection point in Controller Builder.

24 News in EXO 2016

2. A dialog window is opened where selections can be made to create the object.

The following selections can be made:

Type: The type of Modbus object. Available selections are depending on data

type:

Data type L variables: Coil or Discrete Input

Data type X, I, R and H variables: Holding Register or Input

Register

Comment

Create in: Where the object should be created. Can be one of the following:

In the Root object

In a Group object named after the Controller Builder block name

3. Click OK when ready.

Time Channels There is a new Time Channels function, Time Channels (ver 3.0), which is a new version of

Time Channels (ver 2.0). Time Channels (ver 3.0) uses a new Time Channels tool.

The old and the new tool are fully compatible with each other, and it is possible to open a

program created in the new Time Channels tool with the old tool and vice versa:

A time channels program created in the old tool can be opened in the new tool, and it

will be fully functional. However, the program will consist of advanced objects.

A time channels program created in the new tool can be opened in the old tool. If it is

then saved in the old tool, and opened in the new tool again, it will consist of advanced

objects, regardless of how it was originally created.

Adding Time Channels (ver 3.0) to a controller

For new controllers, Time Channels (ver 3.0) is included in the template. But for older

controllers, Time Channels (ver 3.0) can be added by doing the following:

1. Select the controller you wish to add Time Channels (ver 3.0) to in Project Builder.


2. Add Time Channels (ver 3.0) using Add/Remove Functions in the Config menu.

A Warning message will be shown. Click OK to continue.

3. Remove the old Time Channels (ver 2.0) also using Add/Remove Functions in the

Config menu.

4. The new Time Channels function can then be configured for the controller either

through the Config menu or by clicking the icon.

It is important to do these steps in the correct order. If Time Channels (ver 2.0) is

removed before Time Channels (ver 3.0) is added, any configurations made in

Time Channels (ver 2.0) are lost.

Time Channels tool

The Time Channels tool is navigated using a tree structure on the left hand side of the

window containing all objects, and attributes for the selected object is shown to the right.

It can contain the following object types:

26 News in EXO 2016

Function

A Time channel is used for time control of switching on/off for example a pump, a fan,

lightning etc.). Each Time channel is linked to a Time Schedule.

A Time schedule consists of a number of Day plans, one for each day of the week and one

for holidays.

The Day plans specify a number of switch-on/off times for the various days of the week and

holidays. Each Day plan can contain a maximum of four time periods with start and stop

times.

There is also a Holiday calendar which can contain any number of Holiday calendar

periods.

Each Holiday calendar period defines a period during which the Holiday day plan will be

used instead of the regular weekday day plans.

Advanced objects

If you have need for a more advanced configuration of your time channels than can be

achieved with the above mentioned objects, there are also a number of advanced objects

available. The main additional configurations that can be made with these objects are:

A Time channel (advanced) can use more than one Time schedule (advanced) which

makes it possible to use different time schedules for different parts of the year. The

Time schedule attribute defines a Time schedule to be used as default, and the attributes

Special calendar 1-3 defines up to three calendar periods, (Calendar period

(advanced)), which in turn defines alternate time schedules or alternate day plans to be

used during the specified calendar periods.

A Time schedule (advanced) can contain any number of day plans and it is possible to

select which day plan should be used for which weekdays and for holidays. There are

three different types of advanced Day plans available:

Day plan (advanced): Has the same functionality as the regular Day

plan and can contain a maximum of four time periods with start and

stop times.

Object type Icon

Time channels

Group

Time channel

Time schedule

Day plan

Holiday calendar

Holiday calendar period

Time channel (advanced)

Time schedule (advanced)

Day plan (advanced)

Day plan run-time (advanced)

Day plan interval (advanced)

Holiday calendar period (advanced)

Calendar (advanced)

Calendar period (advanced)


Day plan run-time (advanced): Defined with up to four start times

and runtimes.

Day plan interval (advanced): Defined with a start interval runtime

and a reference time.

The Start time and End time attributes in the Holiday Calendar Period (advanced)

object can be set to any time, while in the Holiday Calendar Period object, Start time

must be 00:00 and End time 00:00 or 24:00 in the Holiday Calendar Period object.

Object attributes

Time channels (root object)

The Time channels object is the root object and has the following attributes:

Attribute Description

Type The object type.

Comment Multiline text field for comments for the integrator.

Group

Group objects can be placed in the root or in other Group objects. Each object has the

following attributes:


Name The technical name of the object.



Time channel

Time channel objects can be placed in the root or in a Group object. Each object has the






Title The title of the object, shown to the operator.

28 News in EXO 2016

Time schedule

Time schedule objects are placed in Time channel objects and cannot be created separately.

Each object has the following attributes:






Day plan

Day plan objects are placed in Time schedule objects and cannot be created separately.

To define a day plan which is never activated, define the same start time and stop time, for

example 00:00 to 00:00.

To define a day plan which is always activated, define the start time to 00:00 and the stop

time 24:00.







Time period

1 Start

The time for starting time period 1, in the format hh:mm.

Time period

1 End

The time for ending time period 1, in the format hh:mm.

If a time period extends to midnight, the time 24:00 is

entered.

Time period

2 Start The time for starting time period 2, in the format hh:mm.

Time period

2 End The time for ending time period 2, in the format hh:mm.


entered.

Time period

3 Start


Time period

3 End



entered.

Time period

4 Start


Time period

4 End



entered.

Holiday calendar

The Holiday calendar object is placed in the root and cannot be deleted or created. The

object has the following attributes:






Holiday calendar period

Holiday calendar period objects can be placed in the Holiday calendar object. Each object

has the following attributes:




Start date The start date, in the format MM-DD.

End date The end date, in the format MM-DD.

Start time The start time, in the format hh:mm.

Read-only, value set to 00:00

End time The end time, in the format hh:mm.

Only allowed values are 00:00 or 24:00.

30 News in EXO 2016

Time channel (advanced)

Time channel (advanced) objects can be placed in the root or in Group objects. Each object

has the following attributes:






Time

schedule

The name of a time schedule to be used. All objects of the

type Time schedule (advanced) are shown as alternatives.

(Special

calendar 1)

The name of a calendar to be used as special calendar 1. All

objects of the type Calendar (advanced) are shown as

alternatives.

(Special

calendar 2)



alternatives.

(Special

calendar 3)



alternatives.

Time schedule (advanced)

Time schedule (advanced) objects can be placed in the root or in Group objects. Each




If the name is changed, any references from other objects

are also changed. If the object is deleted, any references

from other objects are also deleted.




Mondays The name of a day plan that is to be used for Mondays.

Tuesdays The name of a day plan that is to be used for Tuesdays.

Wednesdays The name of a day plan that is to be used for Wednesdays.

Thursdays The name of a day plan that is to be used for Thursdays.

Fridays The name of a day plan that is to be used for Fridays.

Saturdays The name of a day plan that is to be used for Saturdays.

Sundays The name of a day plan that is to be used for Sundays.

Holidays The name of a day plan that is to be used for Holidays.


Day plan (advanced)

Day plan (advanced) objects can be placed in the root, in Group objects, in Time channel

(advanced) objects or in Calendar (advanced) objects.

To define a day plan which is never activated, define the same start time and stop time, for

example 00:00 to 00:00.

To define a day plan which is always activated, define the start time to 00:00 and stop time

24:00.




If the name is changed, any references from other objects are also changed. If the object is deleted, any references





Time period

1 Start


Time period

1 End



entered.

Time period


Time period

2 End



entered.

Time period

3 Start


Time period

3 End The time for ending time period 3, in the format hh:mm.


entered.

Time period

4 Start


Time period

4 End



entered.

Day plan run-time (advanced)

Day plan run-time (advanced) objects can be placed in the root, in Group objects, in Time

schedule (advanced) objects or in Calendar (advanced) objects. Each object has the










32 News in EXO 2016

Time period



entered.

Time period

1 run-time

The run time for time period 1, in the format hh:mm.

Time period

2 Start


Time period

2 run-time


Time period


Time period

3 run-time The run time for time period 3, in the format hh:mm.

Time period

4 Start


Time period

4 run-time


Day plan interval (advanced)

Day plan interval (advanced) objects can be placed in the root, in Group objects, in Time

schedule (advanced) objects or in Calendar (advanced) objects. Each object has the










Period length The start interval, in the format hh:mm. Synchronized with

Reference time.

Run time The run time for the interval, in the format HH:mm.

Reference

time Reference time, in the format HH:mm. Used to synchronize

the start time.

E.g. if the Reference time = 05.30 and Period Length = 01:00 the interval will begin every half-hour, (00:30, 01:30,

02:30 etc.).


Holiday calendar period (advanced)

Holiday calendar period (advanced) objects can be placed in the Holiday calendar object.








Read-only, value set to 00:00


Only allowed values are 00:00 or 24:00.

Calendar (advanced)

Calendar (advanced) objects can be placed in the root, in Group objects or in Time

channel (advanced) objects. Each object has the following attributes:





Calendar period (advanced)

Calendar period (advanced) objects can be placed in Calendar (advanced) objects. Each





Day plan The name of a day plan that is to be used for the calendar period.





(Time

schedule)

The name of a time schedule that is to be used. All objects

of the type Time schedule (advanced) are shown as

alternatives.

34 News in EXO 2016

Time Channel State, Status and Time left

All time channels have the variables State, Status and Time Left.

Variable Type Vpac Description

State L TimePro Indicates state of the time channel, i.e. if it is active or not.

Status X TimePro Indicates the status of the time channel;

0=Off

1=On

2=SemiOff

3=SemiOn

4=Auto

Time Left I TimePro Indicates the time left in minutes until the time channel changes

state.

For objects of the type Time Channel they are named as follows:

Variable Variable name

State TimeChannelName

Status TimeChannelName_Status

Time Left TimeChannelName_TimeLeft

For objects of the type Time Channel (advanced) they are named in two different ways

depending on the name of the object. If the name of the time channel starts with the text

TimeGroup, only the suffix is used in the variable names:

Variable Variable name if the object name

starts with TimeGroup

Variable name if the object name

doesn’t start with TimeGroup

State TimeChannelName TimeGroupTimeChannelName

Status TimeGroupStatusSuffixname TimeGroupStatusTimeChannelName

Time Left TimeGroupTLSuffixname TimeGroupTLTimeChannelName


Templates



Export to template



3. Select an existing template to overwrite or a location for the new template and click Next.



Synchronize

The Synchronize command compares the configuration of all parameters of the selected

objects in the Time Channels tool with the current settings in the physical controller. All

parameters that differ are listed in a window.

The window displays the parameters’ names and descriptions together with their values in

the tool and in the controllers. You can choose to update the tool or update the controller to

synchronize them. You can select which parameters you want to update.

36 News in EXO 2016

Controller Builder

Import I/O list

It is possible to import an I/O configuration in the form of a .csv file. This is done with the

Import… button in the Inputs and Outputs window in Controller Builder.

To be able to import a .csv-file this way, it must be correctly filled out. It must have the

following five columns:

A) I/O point

B) Name

C) Type

D) Scale

E) Comment

Values in the Type column must be numerical. Type corresponds to the Input type

attribute for analog and digital inputs, and the Output type attribute for digital

outputs. Analog outputs do not have a corresponding “type” attribute and is therefore

left empty.

Export I/O list

The Export function in the Inputs and Outputs dialog window for exporting I/O lists has

been changed. The exported .csv file now has the following columns:

A) I/O point

B) Name

C) Type

D) Scale

E) Comment

New function blocks

The following new function blocks are added in EXO 2016:


Presigo with 1 Sensor / 2 Sensors

General

Function blocks for EXOline communication with a Regin Presigo pressure transmitter with

one or two differential pressure sensors. In addition to the pressure values (PSA

Pressure/PSB Pressure) there are also values for the flow (PSA Flow/PSB Flow). The

Presigo has a terminal for connecting two universal inputs. These values are also read by the

block (UAI1/UDI1 and UAI2/UDI2).

Function

Pressure

The pressure unit can be changed between Pascal, mBar, mm H2O and Inch H2O, using

the PSA Pressure Unit / PSB Pressure Unit parameters.

Flow

The flow unit can be changed between m3/h, l/s and Ft3/min, using the parameters PSA

Flow Unit/PSB Flow Unit.

Universal Inputs

It is possible to set the mode on the two universal inputs. The options are Pt1000,

Ni1000-DIN, 0…10 V and Logic. When selecting Logic, the input works as a digital

input. These options are set in the UI1 Mode and UI2 Mode parameters.

Communication

The PLA:ELA address and the communication port to the Presigo is settable in the PLA,

ELA and ComPort parameters.

Signals

Operation

Signal Name Data Type

Signal Type Signal ID Def Description

Enable L Input Enable 1 This parameter enables (1) or disables (0) the

function.

PSA Pressure R Output PSA_Pressure - Pressure value for PSA sensor.

PSB Pressure R Output PSB_Pressure - Pressure value for PSB sensor.

PSA Flow R Output PSA_Flow - Flow value for PSA sensor.

PSB Flow R Output PSB_Flow - Flow value for PSB sensor.

Universal Analog Input 1

R Output UAI1 - Used when UI1 Mode is set to 1, 8 or 9.

38 News in EXO 2016

Universal Analog Input 2

R Output UAI2 - Used when UI2 Mode is set to 1, 8 or 9.

Universal Digital

Input 1

L Output UDI1 - Used when UI1 Mode is set to 6.

Universal Digital

Input 2

L Output UDI2 - Used when UI2 Mode is set to 6.

Communication



PLA X Parameter PLA 242 PLA address for communication with

Presigo unit.

ELA X Parameter ELA 1 ELA address for communication with

Presigo unit.

Communication Port

X Parameter ComPort 1 Port number for communication with Presigo unit.

Communication

Failure

L Output ComFailure - Is set if communication is failing.

Configuration

Signal PName Data Type


PSA Pressure Unit

X Bidir PSAPressur

eUnit 0 Pressure unit for PSA sensor.

0 = Pascal

1 = mBar

2 = mm H2O

3 = Inch H2O

PSB Pressure

Unit

X Bidir PSBPressur

eUnit 0 Pressure unit for PSB sensor.

0 = Pascal

1 = mBar

2 = mm H2O

3 = Inch H2O

PSA Flow Unit X Bidir PSAFlowUni

t

0 Flow unit for PSA sensor.

0 = m3/h

1 = l/s

2 = Ft3/min

PSB Flow Unit X Bidir PSBFlowUni

t

0 Flow unit for PSB sensor.

0 = m3/h

1 = l/s

2 = Ft3/min

UI1 Mode X Bidir UI1Mode 1 Mode for UI1 input.

0 = No Mode

1 = Pt1000

6 = Logic (digital input)

8 = Ni1000-DIN

9 = 0...10 V

UI2 Mode X Bidir UI2Mode 1 Mode for UI2 input.

0 = No Mode

1 = Pt1000

6 = Logic (digital input)

8 = Ni1000-DIN

9 = 0...10 V


Signal Trend Control

General

Blocks of the type Signal Trend Control calculates the trend (the derivate) of the Input

signal and adjusts a given Setpoint value depending on negative or positive trend. The new,

modified setpoint is forwarded to the Output.

Function

The adjustment is P-controlled with separate P-Bands for positive and negative trend;

parameters P Band Positive Trend and P Band Negative Trend. The maximum allowed

adjustment can be set in the Maximum Negative Correction and Maximum Positive

Correction parameters. By default, a new trend value is calculated every half hour. This is

configurable using the Time Period parameter.

A typical application is outdoor temperature trend control, where the temperature can rise or

drop quickly during morning and evening hours. The default setting for Maximum Positive

Correction is 0, since positive correction increases the energy usage. If positive setpoint

correction is desired, this setting must actively be changed.

Signals

Operation




function.

Blocked L Input Blocked - Blocks function output. Output = 0.

Input R Input Input - Signal for which the block monitors the

incremental / decremental speed.

Setpoint R Input Setpoint - The PID setpoint.

Output R Output Output - The adjusted setpoint value.

Configuration



Maximum

Positive Correction

R Parameter MaxPosCorrec

tion

0 Maximum positive correction of the setpoint.

Maximum

Negative

Correction

R Parameter MaxNegCorrec

tion

10 Maximum negative correction of the

setpoint.

Time Period I Parameter TimePeriod 180

0

Time period for trend calculations (seconds).

40 News in EXO 2016

Settings



P Band Negative Trend

R Parameter PbandNegTr

end 50 The proportional band of the setpoint

adjustment control loop, when the trend is

negative (and the setpoint will be adjusted

upwards).

P Band Positive

Trend

R Parameter PBandPosTr

end

20 The proportional band of the setpoint

adjustment control loop, when the trend is

positive (and the setpoint will be adjusted downwards).


General

Block for quick acknowledgement of all active alarms. Note that the block acknowledges

one alarm per program cycle, so it should be put in a task with fast cycle time.

Function

If there are active, unacknowledged alarms in the controller, the logic output

Unacknowledged Alarms will be set. When the command Acknowledge All Alarms is

activated, the block will start to acknowledge one alarm per program cycle, to avoid causing

the program task to stall. During the whole acknowledge process, the logic output In

Progress is active.

Signals

Operation




function.


L Command AcknowledgeA

ll -

Unacknowledged

Alarms

L Output Unacknowledg

edAlarms

- Indicates that there are unacknowledged

alarms.

In Progress L Output InProgress - Indicates that acknowledge process is

running.

Care Taker

General

Block type for monitoring the outdoor temperature and switching the Output into summer or

winter (“Normal”) mode.


Function

Active Output means summer mode. There are two Care Taker types; Comfort caretaker or

3-day-caretaker (set with the Care taker type parameter).

Different switch limits apply depending on occupancy. The block switches occupancy mode

depending on either of the inputs Occupation type (0 = Not Active, 1 = Occupation 1, 2 =

Occupation 2, 3 = Occupation 3, 4 = Occupation 4, 5 = Non Occupation, 6 = Special Non

Occupation) or Time Channel (0 = Non-Occupation, 1 = Occupation)

In Comfort mode, the Output is switched directly when the Outdoor Temp reaches the

applicable limit set in the Switch-Off Temp Occupation / Switch-On Temp Occupation

and Switch-Off Temp Non Occupation / Switch-On Temp Non Occupation.

In 3-day mode, the outdoor temperature is measured at a given time each day (parameters

Outdoor Temp Measuring Hour and Outdoor Temp Measuring Minute). If the outdoor

temperature reaches the applicable limit on 3 consecutive days, the Output is switched.

It is possible to use the direct outdoor temperature or a delayed outdoor temperature

(parameter Outdoor Temp Delayed Equipped)

Signals

Operation



Enable L Input Enable 1 This parameter enables (1) or disables (0) the function.

Blocked L Input Blocked - Blocks output.

Forced ON L Input ForcedON - Forces Output state to ON

Occupation type X Input Occupation - Occupation type;

0 = Not active

1 = Occupation 1

2 = Occupation 2

3 = Occupation 3

4 = Occupation 4

5 = Non Occupation

6 = Special Non Occupation

Time Channel L Input TimeChannel - Time Channel start input

Outdoor Temp R Input OutdoorTemp - The current outdoor temperature value (°C).

Outdoor Temp

Delayed

R Input OutdoorTempD

elayed - The delayed outdoor temperature value (°C).

Output L Output Output - Output indicating:

0 = Winter Mode

1 = Summer Mode

Settings

42 News in EXO 2016



Outdoor Temp

Measuring Hour

X Parameter OutdoorTempM

easHour

21 The hour at which the outdoor temp is

measured and stored.

Outdoor Temp

Measuring

Minute

X Parameter OutdoorTempM

easMinute

0 The minute at which the outdoor temp is

measured and stored.

Switch-Off Temp Occupation

R Parameter SwitchOffTem

pOcc 22 Switch-off temperature for Occupation time.

The temperature for which the Output is set

to 1 (= Summer mode), meaning switch-off

signal to control circuit.

Switch-Off Temp

Non Occupation

R Parameter SwitchOffTem

pNonOcc

18 Switch-off temperature for Non Occupation

time. The temperature for which the Output

is set to 1 (= Summer mode), meaning switch-off signal to control circuit.

Switch-On Temp

Occupation

R Parameter SwitchOnTemp

Occ

15 Switch-on temperature for Occupation time.

The temperature for which the Output is set to 0 (= Normal mode), meaning switch-on

signal to control circuit.

Switch-On Temp Non Occupation

R Parameter SwitchOnTemp

NonOcc 11 Switch-on temperature for Non Occupation

time. The temperature for which the Output

is set to 0 (= Normal mode), meaning switch-

on signal to control circuit.

Configuration



Care taker type X Parameter Type 2 Type of care taker:

0 = Not equipped

1 = Comfort

2 = 3-day

Outdoor Temp

Delayed Equipped

L Parameter OutdoorTem

pDelayedEq

uipped

- Outdoor temp delayed equipped.


Time Channel (ver. 3.0)

General

Blocks of the type Time Channel (ver. 3.0) are used as a graphic representation of a time

channel in Controller Builder. It reads variables from a specified time channel and displays

them as output signals. For use with the Time Channels 3.0 controller function.

Note that there is also a Time Channel (ver. 2.0) function block available for use

with the Time Channels 2.0 function.

Signals

General



State L Output State - Indicates the state of the time channel.

TimeLeft I Output TimeLeft - Time left for the time channel.

Status X Output Status - The status of the time channel:

0 = Of

1 = On

2 = SemiOff

3 = SemiOn

4 = Auto

44 News in EXO 2016

Popup editor

The popup editor is used in Controller Builder to edit EXOL code, and in the EXOscada

tools (EXOscada Area Views, EXOscada View Designer etc) to edit EXObasic code.

The new popup editor is much faster than the previous one, has improved handling of

multiple instances and supports Unicode characters.

As you type in the editor, suggestions of possible EXOL or EXObasic functions are shown

depending on whether you are editing EXOL or EXObasic code.

The popup editor contains many commands. The available commands include:

Indent and unindent lines. Several lines can be selected at once, and the tab length can

be set in Tools/Options…

Comment and Uncomment lines

An integrated Find and replace dialog

Possibility to bookmark lines

Commands for formatting text in different ways, such as font, case and color

The window can be split horizontally into two

Possibility to browse for variables, to add their names in the code

All commands can be reached through the menus and they also have keyboard shortcuts as

shown in the menus. Some of them are also shown as icons in the tool bar.

Bookmarking a line can be done by left clicking in the area directly to the right of the line

number. A blue marking represents the bookmark.


EXOtrend EXOtrend is a tool that can display trend charts of variables and is updated every second. As

long as the EXOtrend window is open, all values are saved for at least three days. When the

EXOtrend window is closed, the values are lost.

Analog signals are shown in a trend chart that can have two Y axes. Digital signals are

shown in a separate chart below the analog signal chart.

The time span shown in the window can be changed using the drop down menu in the tool

bar, and can be increased or decreased with the + and – keys.

It is possible to move forward or backward along the time axis using the

buttons in the tool bar or by using the slider in the bottom part of the window.

The limits of the Y axes are set to Auto as default, but can also be changed to any desired

limits using Y-Axes in the Trend menu.

The following properties of a displayed signal can be changed using Signals… in the Trend

menu:

46 News in EXO 2016

The title of the signal shown in the EXOtrend window.

Color, Line width and visibility for a displayed signal.

The number of decimals for logged values, as well as unit and a description of the

signal, shown when hovering the mouse pointer over the signal.

Creating a new EXOtrend window

A new EXOtrend window can be created in two ways:

1. Select any controller in Project Builder and select EXOtrend in the Tools menu.

2. Right click on a signal in Controller Builder and select Add to EXOtrend. In the dialog

window, click New.


Adding a signal to an EXOtrend window

A signal can be added to an existing EXOtrend window in two ways:

1. Select Add Signal to Left Y-Axis or Add Signal to Right Y-Axis in the Trend menu

in the EXOtrend window.

2. Right click on a signal in Controller Builder and select Add to EXOtrend. Select which

EXOtrend window in the dialog window.

Export to Image

The EXOtrend chart can be exported to an image file (PNG format) showing the currently

displayed chart. This is done with Export to Image in the Tools menu.

Export Data

The logged signal values can be exported to a tab separated text file, suitable for Microsoft

Excel. This is done with Export Data in the Tools menu.

48 News in EXO 2016

Display There is a new Display function, Display (ver 5.0), which is a new version of Display (ver

4.0). Display (ver 5.0) uses a new Display tool.

Adding Display (ver 5.0) to a controller

For new controllers, Display (5.0) is included in the template. For older controllers, Display

(ver 5.0) can be added by doing the following:

1. Select the controller you wish to add Display (ver 5.0) to in Project Builder.

2. Add Display (ver 5.0) using Add/Remove Functions in the Config menu.

A Warning message will be shown. Click OK to continue.

3. Remove the old Display (ver 4.0) also using Add/Remove Functions in the Config

menu.

4. Open the new Display function (either through the Config menu or by clicking the

icon) and save.

It is important to do these steps in the correct order. If Display (ver 4.0) is removed

before Display (ver 5.0) is added, any configurations made in Display (ver 4.0) are

lost.


Display tool

The Display tool is navigated using a tree structure on the left hand side of the window

containing all objects, and attributes for the selected object are shown to the right.

Below the object attributes is an emulator that displays a preview of what the currently

selected object will look like in the controller’s display, as well as navigation buttons that are

used to navigate in the display. When navigating in the display, the corresponding object is

selected in the tree structure. The keyboard can also be used to navigate by holding Ctrl and

pressing the arrow keys.

The emulator has green background color when a menu is displayed, and blue background

color when a dialog box is displayed. The display has room for 4 x 20 characters.

The variables in the emulator can be shown in three different ways:

Macros. Shows a variable as an @ followed by the Name of the variable.

Example values. Shows a variable as the configured Example value of the variable. The

example values can be updated to the values in the controller by using Synchronize.

Controller values. Shows the actual current values from the controller.

50 News in EXO 2016

Objects

The following object types can be used:

Object type Icon Description

Display

The root object.

Menu item

A menu item in a scrollable list where each item

corresponds to a navigation to a submenu or a series of

dialog boxes.

Dummy node Dummy node that is added automatically when converting

programs made in the old display tool to represent items

that are “disconnected” from the menu structure.

Alarm

history view

Pre-configured alarm history view.

Time

channels

view

Pre-configured time channel view.

Dialog box

A dialog box that can contain static texts, dynamic values

and arrows.

Numeric

Numeric element, which can be displayed with 0, 1, 2 or 3

decimals.

Password

Password element, a 4-digit number.

Text

Text element.

Text select

Text select element, which consists of two or more static

texts, e.g. Off, On, Auto.

Date

Date element that can be displayed in the format MM-DD

or YYYY-MM-DD.

Time

Time element, displayed in the format hh:mm.

Double

numeric

Double numeric element that consists of two variables, each consisting of two digits with a colon between them, e.g..

XX:YY.

Triple

numeric

Triple numeric element that consists of three variables, each

consisting of two digits with a colon between them, e.g.

XX:YY:ZZ.

Object attributes

For any object attributes that allow free text, like Text, Comment or User

description, it is possible to insert symbols (degree sign, superscript two and

superscript three) by placing the cursor at the desired insertion point and right

clicking to open a menu from which the symbol can be added.

Display (root object)

The Display object is the root object and has the following attributes:




Show arrows Specifies whether navigation arrows (up and down arrows)

should be shown in the display.

Update cycle Cycle time in seconds for updating the element values in the display. Can be specified with 1 decimal. Must be

divisible by 0.2 seconds and maximum 10 seconds.


Menu item

Menu item objects can be placed in the root, in Dialog box objects or in other Menu item

objects. Each object has the following attributes:





Text The text of the Menu item shown in the display.

User

description

Description of the object for the operator. Can be shown in the printed pdf.

Maneuver

access

Required access level to navigate to child objects of the

Menu item;

5: Everyone

4: Guest

3: Operator

2: Service

1: Admin

Visible access Required access level to see the object in the display;

5: Everyone

4: Guest

3: Operator

2: Service

1: Admin

Visible EXOL expression that states whether the object is visible in the display.

Dummy node

Dummy node objects can be placed in the root, in Dialog box objects or in Menu item





Alarm history view

Alarm history view objects can be placed in the root, in Dialog box objects or in Menu

item objects. Each object has the following attributes:




User

description

Description of the object for the operator. Can be shown in

the printed pdf.

Time channels view

Time channels view objects can be placed in the root, in Dialog box objects or in Menu

item objects. Each object has the following attributes:

52 News in EXO 2016




User

description

Description of the object for the operator. Can be shown in

the printed pdf.

Maneuver

access

Required access level to make changes in the time

channels;

5: Everyone

4: Guest

3: Operator

2: Service

1: Admin

Dialog box

Dialog box objects can be placed in the root, in other Dialog box objects or in Menu item






Text The static text of the dialog box shown in the display. Can

contain macros.

User

description

Description of the object for the operator. Can be shown in the printed pdf.

Maneuver

access

Required access level to navigate to child objects of the

Dialog box;

5: Everyone

4: Guest

3: Operator

2: Service

1: Admin

Visible access Required access level to see the object in the display;

5: Everyone

4: Guest

3: Operator

2: Service

1: Admin

Visible EXOL expression that states whether the object is visible in

the display.

Extra

function

States whether the dialog box has an extra function

(Yes/No).

Numeric element

Numeric element objects can only be placed in Dialog box objects. Each object has the






Controller The controller in which the designated variable is located.


Variable The variable whose value is shown in the display. Can be of

data type X, I or R.

Decimals Number of decimals. Can be set to 0, 1, 2 or 3.

Example

value

Example value that can be used in the emulator and in

printouts.

Maneuverabl

e

Specifies whether the value of the variable can be changed

in the display.

Min value The minimum allowed value if Maneuverable is set to Yes

Max value The maximum allowed value if Maneuverable is set to Yes

Password element

Password element objects can only be placed in Dialog box objects. Each object has the







Variable The variable whose value is shown in the display. Must be

of data type I.

Maneuverabl

e


in the display.

Text element

Text element objects can only be placed in Dialog box objects. Each object has the








of data type $ andin a text file.

Example

value


printouts.

Maneuverabl

e


in the display.

Text select element

Text select element objects can only be placed in Dialog box objects. Each object has the





54 News in EXO 2016



Variable The variable whose value is shown in the display. Can be

of data type L or X.

Example

value


printouts.

Maneuverabl

e

Specifies whether the value of the variable can be changed in the display.

Texts Comma separated list of texts that corresponds to different

numeric values of the attribute Variable. The first text

corresponds to the value 0. Thereafter the texts for the

values 1, 2, 3 etc.

It can be expanded with sub attributes that get the names Value 0, Value 1, Value 2 etc. and New value.

Date element

Date element objects can only be placed in Dialog box objects. Each object has the








of data type X.

Format Specifies the date format. The alternatives are MM-DD and

YYYY-MM-DD.

Maneuverabl

e


in the display.

Time element

Time element objects can only be placed in Dialog box objects. Each object has the








of data type X.

Maneuverabl

e


in the display.

Double numeric element

Double numeric element objects can only be placed in Dialog box objects. Each object has

the following attributes:








of data type X.

Maneuverabl

e


in the display.

Triple numeric element

Triple numeric element objects can only be placed in Dialog box objects. Each object has

the following attributes:







of data type X.

Maneuverabl

e


in the display.

Templates



Export to template



3. Select an existing template to overwrite or a location for the new template and click Next.

56 News in EXO 2016




Synchronize

Synchronize compares the configuration of all example values of the selected objects in the

Display tool with the current settings in the physical controllers. All parameters that differ

are listed in the window.

The window displays the parameters’ names and descriptions together with their values in

the tool and in the controller. Then you can choose to update the tool or the controller to

synchronize them. You can select which parameters you want to update.

The reason for using Synchronize is to update the example values in the tool for the emulator

and for printing a pdf file of the display tree using real values from the controller instead of

variable names.

To start Synchronize, select the objects you wish to synchronize and press the Synchronize

button in the Display tool window.

Print display tree

The display tree can be printed to a pdf file using the command Print display tree. The

display tree is shown as boxes representing menus and dialog boxes. Possible navigations are

shown with solid lines between the boxes.

There are a number of options available to customize the pdf:

Page size and orientation

Color or Black and white

Option to use a smaller font in the printed display screens to make room for more

display screens in each page

Optional page header that contains tool name, controller name, date and time it was

saved and the date and time the pdf was printed

Page numbers

58 News in EXO 2016

Extra wide left margin, suitable if the printed pdf will be put in a binder

Use of example values instead of variable names

Print reference names. Prints the Name of each object above their display screens.

Print user descriptions for the objects. Prints the User Description of each object as an

extra box with white background color below the display screen

Chapter 5 EXOscada 59

Chapter 5 EXOscada

Users Overview The Users Overview view shows currently logged in users and user info, with possibility to

chat with them separately. The system administrator can make a forced logout of users, if

e.g. maintenance is planned.

news in exo 2014 - regincontrols.com€¦ · news in exo 2016 ed 2 compared to ed 1 5 ... exo 2016...

Documents