GC5 iSMA-B-FCU Programming EN v1.0

Download as pdf or txt
Download as pdf or txt
You are on page 1of 109

iSMA-B-FCU

User Manual

FCU programming

GC5 Sp. z o.o.


Poland, Warsaw
www.gc5.pl

Version 1.0 Page 1 / 109


1 Programing iSMA-B-FCU device ........................................................................................... 4
2 Sedona in WorkPlace .............................................................................................................. 6
2.1 Environment installation step by step ..................................................................... 6
2.2 Importing kits to Workplace ...................................................................................... 7
2.3 Installing ismaUI module ........................................................................................... 8
2.4 Connecting to iSMA-B-FCU device ........................................................................... 9
3 Sedona Tools .......................................................................................................................... 12
4 Sedona App component ....................................................................................................... 12
4.1Service component ................................................................................................... 14
Plat service.................................................................................................................. 14
4.2 Users service .............................................................................................................. 17
4.3 SOX protocol............................................................................................................... 19
5 Drivers component ................................................................................................................ 20
6 Logic folder.............................................................................................................................. 21
7 platFCU kit ............................................................................................................................... 21
7.1 NV components ......................................................................................................... 21
NVBooleanWritable ................................................................................................... 22
NVIntegerWritable ..................................................................................................... 23
NVNumericWritable .................................................................................................. 24
LocalIO ......................................................................................................................... 29
LocalIOConfig ............................................................................................................. 30
LocalIOFolder ............................................................................................................. 32
AODigital ...................................................................................................................... 33
AOVoltage ................................................................................................................... 34
DI ................................................................................................................................... 35
DICounter .................................................................................................................... 36
DO ................................................................................................................................. 37
SIDigital........................................................................................................................ 38
SIResistance ............................................................................................................... 39
SITemperature ........................................................................................................... 40
SIVoltage ............................................................................................................... 41
TODigital ................................................................................................................ 42
TOutPWM .............................................................................................................. 43
DIPSwitch .............................................................................................................. 44
In4Out ..................................................................................................................... 45
LedAlarm ............................................................................................................... 46
Watchdog .............................................................................................................. 47
7.2 Slave Network ............................................................................................................ 48

Version 1.0 Page 2 / 109


Slave Network Component ...................................................................................... 48
NV Net components.................................................................................................. 49
NV Net Numeric Component .................................................................................. 50
NV Net Boolean Component ................................................................................... 52
8 Modbus Async Network kit .................................................................................................. 54
8.1 Modbus Async Network component ..................................................................... 54
8.2 Modbus Async Device component ........................................................................ 57
8.3 Modbus Async Boolean Point ................................................................................. 59
8.4 Modbus Async Boolean Writtable .......................................................................... 60
8.5 Modbus Async Numeric Multi Point ...................................................................... 62
8.6 Modbus Async Numeric Point ................................................................................ 63
8.7 Modbus Async Numeric Writable ........................................................................... 64
8.8 Modbus Async Register Bit Point ........................................................................... 66
8.9 Modbus Async Register Bit Writable ..................................................................... 67
8.10 Modbus Folder ........................................................................................................... 68
9 BACnet Master Slave kit ....................................................................................................... 69
9.1 BacnetMasterSlaveNetwork .................................................................................... 69
9.2 AnalogValueRead ...................................................................................................... 71
9.3 AnalogValueWrite ...................................................................................................... 72
9.4 BinaryValueRead ....................................................................................................... 73
9.5 BinaryValueWrite ....................................................................................................... 74
9.6 BACnet Master Slave Folder.................................................................................... 75
10 FCU kit ...................................................................................................................................... 76
10.1 FCU_Antifrost ............................................................................................................. 76
10.2 FCU_ChangeOfStateDelay ....................................................................................... 77
10.3 FCU_EffectiveSetpointCalculator ........................................................................... 79
10.4 FCU_FanControl ......................................................................................................... 82
10.5 FCU_HeatingCoolingSwitch .................................................................................... 89
10.6 FCU_MasterSlave ...................................................................................................... 92
10.7 FCU_ModeCalculator ................................................................................................ 94
10.8 FCU_Multiply............................................................................................................... 97
10.9 FCU_OccupancyCalculator ...................................................................................... 98
10.10 FCU_OutputsSwitch ......................................................................................... 101
10.11 FCU_SensorFault .............................................................................................. 106
10.12 FCU_Temperature_Sensors_Switch .............................................................. 107

Version 1.0 Page 3 / 109


1 Programing iSMA-B-FCU device
Each brand new iSMA-B-FCU device has uploaded the default application, firmware and
kits. There is a possibility to modify default application for their own, use or create new,
custom application.

Modification of default application or creating a new one, can be done only online (in
real time), using SOX protocol and WorkPlace. Size of application cannot exceed 64 kB.
Value of available memory can be checked in Mem Available slot (under Plat
component).

Using FCU Updater, modificated or created application can be downloaded from one
iSMA-B-FCU device and upload to other iSMA-B-FCU device(s). iSMA-B-FCU device has
two built-in RS485 ports:
 COM1 – port with screw connector, port can be used to communication using
Modbus RTU/ASCII protocol or BACnet protocol (including BACnet Master Slave
communication)
 COM2 – port with two RJ12 connectors, port can be used to communication using
Modbus Async protocol.
Each iSMA-B-FCU device has set of kits, which are installed with firmware. These kits
are needed for the proper operation of default application and can be also used to create
custom application. The kits cannot be changed or delayed. iSMA-B-FCU device has the
following kits:
 sys – Sedona core system module
 control – Basic function block library
 inet – IP and UDP/TCP Socket APIs
 sox – Sox service for remote management
 iSMA_BACnetMasterSlave – Kit for Master - Slave communication
o iSMA-B-FCU device can work in defined groups where one device is master and
rest device (slaves) follows Master parameters.
o It is possible to sharing up to 100 points in this way
o This function is available only in BACnet MSTP protocol, using RS485 port
(COM1)
o Each master device can have up to 5 slave devices.

 iSMA_FCU – Kit includes components used to build FCU application. It consists


components for control temperature outputs, fan etc.
 iSMA_ModbusAsyncNetwork – Kit includes components for Modbus Async
communication

Version 1.0 Page 4 / 109


o Modbus Async can be used to communicate with other devices connected to
built-in RS485 port (COM2).
o It is possible to read/write up to 200 points in this way.
o There is no restriction about number of connected devices.

 iSMA_platFCU – Kit includes components to all types of inputs and outputs


servicing, components for communication with higher level system (using Slave
Network) and NV components.
o Slave Network component is used to management BACnet MSTP or Modbus
RTU/ASCII protocol, using RS485 port (COM1).
o Slave Network allows to share up to 200 numeric points and up to 200 boolean
points.
o Total number of memory cells for NV Numeric (and Integer) components
cannot exceed 230. Total number of memory cells for NV Boolean components
cannot exceed 240.

Note: Way of calculating memory cells for NV components is describe in Plat service
chapter.

The iSMA-B-FCU device has 18 built-in physical inputs and outputs:


 4x Special Inputs
 4x Digital Inputs
 3x Analogue Outputs
 4x Digital Outputs
 2x Triac Outputs
o CFG Dip Switch – it allows to read eight binary signals from CFG DipSwitch
mounted in iSMA-B-FCU device. Using Dip Switch is recommended to hand
configuration of device.
o Alarm LED – it allows to signalize defined in application states of working
iSMA-B-FCU device. For example, it can be used to signalizing alarms.

The components for service all inputs, outputs shown below are placed under
iSMA_platFCU palette.

Version 1.0 Page 5 / 109


2 Sedona in WorkPlace
Sedona device configuration and programming is based on the WorkPlace software.
Out of the box, WorkPlace has no plugin to handle Sedona devices and it should be
installed. Installation files can be downloaded from the "Niagara Central" website or
obtained from your distribution partner. WorkPlace version 3.7 and older require bundle
Sedona_Framework_TXS-1.2.28. WorkPlace version 3.8 and later use bundle
Sedona_Framework_TXS-1.2.100. To get Sedona Framework installation file go to
Niagara Central or contact to your distributor.

2.1 Environment installation step by step


Step 1 – In the menu bar, select the Tools tab and application Sedona Installer. The first
installation window pops up, where you choose the Sedona bundle file to select.

Step 2 – Click “Next” and move on to the terms and conditions of the license. To
continue, accept and confirm your installation by clicking Install.

Version 1.0 Page 6 / 109


Step 3 – Upon successful installation of Sedona environment, restart WorkPlace by
clicking the “Restart Workbench” option followed by the Finish button.

2.2 Importing kits to Workplace


To import files to WorkPlace it is recommended to use “Sedona Installer” from Tools
menu and choose “Import Sedona environment files”. The latest kits and kits bundle can
be downloaded from support.gc5.pl web site. There are two option to import kits to
Workplace:
 Singly – by choosing single kit file with kit extension

Open Sedona Installer from Tools menu in Workplace, mark option “Install Sedona
environment files” and select kit file. Press next button to finish importing process. This
process will copy this file to Sedona kits folder.
 Groups – by choosing prepared bundle file with zip extension

Version 1.0 Page 7 / 109


Open Sedona Installer from Tools menu in Workplace, mark option “Install Sedona
environment files” and select zip file. Press next button to finish importing process. This
process will copy all kit’s files from zip archives to Sedona kits folder.

2.3 Installing ismaUI module


ismaUI module is a special module which include WorkPlace views for Sedona
components.

To install ismaUI module download jar file from support.gc5.pl web site and copy
ismaUi.jar file to Niagara/module folder on local PC. To make changes, restart
WorkPlace.

Version 1.0 Page 8 / 109


2.4 Connecting to iSMA-B-FCU device

Warning: Before start programing iSMA-B-FCU device using SOX protocol. It is


recommended to connect device to 230 V AC power supply.
 Before connecting iSMA-B-FCU device to WorkPlace, run FCU Updater and go to
“SOX” tab.

Figure 1 FCU Updater - SOX tab

 Connect iSMA-B-FCU device to USB port in your computer – name of tab should
change to “USB - connected”, which means, that FCU Updater has got
communication with iSMA-B-FCU device.

Figure 2 FCU Updater - USB connection

Version 1.0 Page 9 / 109


 Click “Begin Communication” button.

Figure 3 FCU Updater - Beginning comunication


 Now, go to WorkPlace.
 In order to connect to the device, select the following in the menu:
File -> Open -> Open Device.

Figure 4. Device opening

Note! Should no option “Open Device” be available, no Sedona plugin has been installed
in WorkPlace. In this case, proceed to install the Sedona environment as described in
the previous section.

Version 1.0 Page 10 / 109


 After selecting the above option, a device connect window pops up.

Figure 5 Connect window

Please, enter the following values:


o IP address – 127.0.0.1
o Port – 1876

 Login to driver using following Username and Password:


o Username – admin
o Password – empty box (no characters)

Figure 6 Authentication window

Version 1.0 Page 11 / 109


3 Sedona Tools
Sedona Tools are not supported for iSMA-B-FCU devices.

4 Sedona App component


Sedona Application is made of services and components available from the Palettes.
Components are processed in every working cycle of the device. Services are certain
components enabling system functions such as user management. All items should be
placed under the App main component. When the application is modified, the App icon
is displaying with reminder that the application should be saved.

Figure 7 App component

Version 1.0 Page 12 / 109


The component has the following slots:
 Device Name – Device Name text,
 App Name – Application Name text,
 Scan Period – One cycle execution time,
 Scan Time – Real time of one cycle execution,
 Guard Time – Reserve time to finish system tasks,
 Time To Steady State - Time from app start to steady state,
 Hibernation Resets Steady State – not active in iSMA-B-FCU,
 Number Of Components – Number of components used in application.
The component has the following actions, available under the right mouse button:
 Save – save Sedona application in the device’s flash memory,
 Restart – restart application (Sedona Virtual Machine),
 Reboot – reboot device.

Under App component should be placed the following components:


 Service
 Drivers
 Logic
All these components are described in sections bellow.

Version 1.0 Page 13 / 109


4.1 Service component
Service component has been created to manage services. Under this components are
placed components, which does not take direct part in the operation of the application.
The component has to be placed under App component.

Plat service
The Plat service is a component, which shows device mains parameters. This
component is placed under the Service folder and is associated with device hardware.
The component has to be placed under Service component.

Figure 8 plat component

The component has the following slots:


 Status – Platform status,
 Platform ID – Platform ID,
 Platform Ver – Platform Version,
 Mem Available – Controller RAM memory available. Whole application for iSMA-B-
FCU device cannot exceed 64 kB,

Version 1.0 Page 14 / 109


 Cpu Usage – CPU usage from last 5 seconds,
 Firmware Version – Controller firmware version,
 Nv Behavior If Empty – Non-Volatile components after copy output value (Options
Leave 0, copy value from Default slot), default set to copy value from Default slot,
 Nv Free Numeric – number of available Numeric Non-Volatile components,
 NV Free Boolean – number of available Boolean Non-Volatile components.
Note: Number of components physically added to application does not have to be equal
to memory cells. It can be calculate in way shown below:
 Each added NV Numeric (or Integer) component (not NV Net component) use two
memory cells – one numeric cell for value and one Boolean cell for Hand/Auto
mode,
 Each added NV Boolean component (not NV Net component) use two Boolean
memory cells – one for value and one cell for Hand/Auto mode,
 Each NV Net Numeric component use one numeric cell – these components work
only Auto mode, so memory cell is needed only for value,
 Each NV Net Boolean component use one Boolean cell – those components work
only Auto mode, so memory cell is needed only for value,
 For Example: When we add to application 2 NV Numeric components, 3 NV Boolean
components, 4 NV Net Numeri components and 5 NV Net components, usage of
memory cells can be calculate like in the table below:

Number of Used Boolean memory Used Numeric memory


Type of commponent
components cells cells
2
2
NV Numeric 2 (for Auto/Hand
(for values)
modes)
6
(3 for Auto/Hand
NV Boolean 3 0
modes and 3 for
values)
4
NV Net Numeric 4 0
(for values)
5
NV Net Boolean 5 0
(for values)
Sum 13 6
Table 1 Memory cells calculation

According to the table, this application use 13 Boolean memory cells and 6 Numeric
memory cells. In this case, slots “Free NV Boolean” and “Free NV Numeric” (under
plat component) will display:
o Free NV Boolean: 227

227 = 240 (available Boolean memory cells) – 13 (Boolean memory cell


used in application)

Version 1.0 Page 15 / 109


o Free NV Numeric: 224

224 = 230 (available Numeric memory cells) – 6 (Numeric memory cell


used in application)

Figure 9 plat component - actions

The component has the following actions, available under right mouse button:
 Restart – restarts the application (Sedona Virtual Machine),
 Reboot – reboots the device,
 Copy From Nv To Default – copies values from Out slot to Default slot in all NV
components (see NV component chapter),
 Copy From Nv To User – copies values from Out slot to User slot in all NV

Version 1.0 Page 16 / 109


components (see NV component chapter),
 Copy From Default To NV – copies values from Default slot to Out slot in all NV
components (see NV component chapter),
 Copy From User To NV – copies values from User slot to Out slot in all NV
components (see NV component chapter),
 Set All Nv In Auto – sets all NV components in auto mode.

4.2 Users service


Users’ Service is a service responsible for supporting users. Here is where you add and
remove users as well as define their access rights to individual components. Each
Sedona application component has a Meta slot, used to assign it to one or more groups.
Sedona has 4 predefined groups. The component has to be placed under Service
component.

Figure 10 Users component

Version 1.0 Page 17 / 109


Users can have the following types of rights:
 Operator Read – Read components, read values of operator properties,
 Operator Write – Change values of operator properties,
 Operator Invoke – Invoke operator actions,
 Admin Read – Read values of properties, read links, generate components links,
 Admin Write – Change values properties, add components, sort dub components,
rename components, generate links to the components, delete links to the
components,
 Admin Invoke – Invoke admin actions of the components,
 Admin User – User management (read, write, edit, delete).

Provisioning Permissions:
 Can provision app – can read/write app.sab file,
 Can provision kits – can read/write kits.scode file,
 Can provision svm – can read/write SVM files.

Version 1.0 Page 18 / 109


4.3 SOX protocol
SOX is the standard protocol used to communicate with Sedona devices. In this case,
SOX is used to communicate iSMA-B-FCU device with WorkPlace, using USB
connection.

Note, that SOX is service type and it is execute after application components. So, if there
is little difference between Scan Period and Scan Time (see App component) the
services do not have time execute and the programing interface can slow down. SOX is
designed to be run over UDP/IP protocol (default port 1876), but in the case of iSMA-B-
FCU device, SOX protocol runs over USB interface.

The component has to be placed under Service component.

Figure 11 Sox component

The component has the following slots:


 Port – Sox UDP port (default value 1876),
 Receive Max – Max of number of messages in receiving window,
 Events Per Sec – Max of number of async events (telegrams) sent per second.

Version 1.0 Page 19 / 109


5 Drivers component
Drivers component has been created to manage networks used by application.

Under Drivers component have to be placed all components responsible for networks
and components associated with them, used by iSMA-B-FCU device. It could be Local
IO network (which manage physical inputs and outputs built-in iSMA-B-FCU device) or
networks responsible for protocols, which allows to communicate with other devices
(in the case of iSMA-B-FCU device: Modbus Async, Slave Network and BACnet Master
Slave).

The component has to be placed under App component.

Figure 12 Drivers component

Version 1.0 Page 20 / 109


6 Logic folder
Logic Folder is a folder for grouping components used to build logic of application, like
function blocks, NV components etc. These components can be placed everywhere
under App component, but it is recommended to placed them under Logic Folder – it
allows to easier interpretation of all application.

Logic folder is a component available from the sys kit palette, Folder component, which
is component of no properties and it is used exclusively to arrange applications visually.

To group logic components, can be also used Rate Folder component, also available
from the sys kit palette. Rate Folder component is a folder used to reduce the rate of
application performance. While developing major applications, it allows to reduce a
demand for processing power, consuming it for major or quick functions of the device
algorithm. The folder’s parameter “App Cycles To Skip” defines how frequently, in no. of
scanning cycles, components under the folder are processed.

7 platFCU kit
iSMA platFCU kit contains components for servicing physical inputs and outputs of
iSMA-B-FCU devices. It also contains Non-volatile components and Non-volatile Net
components for servicing Slave Network. All these components are described in
sections below.

7.1 NV components
 NV Components (Non-Volatile) are the components whose value can be recorded
in an EEPROM device’s non-volatile memory. Whenever, a device is restarted or the
power is down, the values of NV components remain saved. The device has three
types of NV components, which support the different types of variables: Boolean
variables - component NVBooleanWritable,
 Integer variables - component NVIntegerWritable,
 Numeric (float) variables - component NVNumericWritable.
NV components can operate in the Auto mode (the “In” slot values are transferred to
the “Out” slot) or in the Hand mode (the “Out” value is entered manually by the user and
cannot be changed by the application).

Version 1.0 Page 21 / 109


Since the values of the components are not stored in the Sedona application but in the
non-volatile memory of the device, when an application is copied between two devices,
output values are not saved and will assume the values stored in the local EEPROM
memory. To copy NV components to another device along with their values (e.g.
setpoint), use global actions of the plat component:

Step 1 - Use global action "Copy From NV The Default / Copy From NV To User"

Step 2 - Save the application and copy it to another device

Step 3 - Use global action on the target device "Copy From Default To NV / Copy From
User To Nv"

NVBooleanWritable
NVBooleanWritable is a component that stores the output value in non-volatile memory
of an EEPROM device. After rebooting the device or power failure, the component value
is restored from this particular memory. The occupied space meter for EEPROM is
embedded in the plat component.

Note: Way of calculating memory cells for NV components is described in Plat service
chapter.

The NVBooleanWritable component is also used to integrate Boolean variables from


various sources. It is done using the "reverse following the link" function. The Out slot is
connected to the In slots of various protocols, for example BACnet or Modbus variable.
Changing a value in one of the components, the device will perform the Set action on
the NV component to synchronize the values in all the connected components.

Figure 13 NVBoleanWritable component

Version 1.0 Page 22 / 109


The component has the following slots:
 Status – Point actual status Auto/Hand,
 Out – Output slot,
 In – Input Slot,
 User – User value slot (setting by Set action),
 Default – Default value slot (setting by global command from plat action),
 Default Trigger – Copying trigger from Default to Out.

The component has the following actions, available under the right mouse button:
 Set - this option sets User slot and In slot if there is no link on In slot,
 Set In Hand - this option sets the value on Out slot and blocks changing from any
other slots,
 Set In Auto - this option switches off the Hand mode and sets Out slot according to
the In slot’s value.

NVIntegerWritable
NVIntegerWritable is a component that stores the output value in non-volatile memory
of an EEPROM device. After rebooting the device or power failure, the component value
is restored from this particular memory. Space meter of the occupied EEPROM's
memory is located in the plat component.

Note: Way of calculating memory cells for NV components is described in Plat service
chapter.
The NVIntegerWritable component is also used to integrate integer variables from
various sources. It is done using the "reverse following the link" function. The Out slot
is connected to the In slots of various protocols, for example BACnet or Modbus
variable. Changing a value in one of the components, the device will perform the Set
action on the NV component to synchronize the values in all the connected
components.

Version 1.0 Page 23 / 109


Figure 14 NVIntegerWritable component

The component has the following slots:


 Status – Point actual status Auto / Hand,
 Out – Output slot,
 In – Input Slot,
 User – User value slot (setting by Set action),
 Default – Default value slot (setting by global command from plat action),
 Default Trigger – Copying trigger from Default to Out.

The component has following actions, available under the right mouse button:
 Set – this option sets User slot and In slot if there is no link on In slot ,
 Set In Hand – this option sets value on Out slot and block changing from any other
slots,
 Set In Auto – this option switches off Hand mode and sets Out slot according to In
slot value.

NVNumericWritable
NVNumericWritable is a component that stores the output value in non-volatile memory
of an EEPROM device. After rebooting the device or power failure, the component value
is restored from this particular memory. Space meter of the occupied EEPROM's
memory is located in the plat component.

Note: Way of calculating memory cells for NV components is described in Plat service
chapter.

Version 1.0 Page 24 / 109


The NVNumericWritable component is also used to integrate Numeric (float) variables
from various sources. It is done using the "reverse following the link" function. The Out
slot is connected to the In slots of various protocols, for example BACnet or Modbus
variable. Changing a value in one of the components, the device will perform the Set
action on the NV component to synchronize the values in all the connected
components.

Figure 15 NVNumericWritable component

The component has the following slots:


 Status – Point actual status Auto/Hand,
 Out – Output slot,
 In – Input Slot,
 User – User value slot (setting by Set action),
 Default – Default value slot (setting by global command from plat action),
 Default Trigger – Copying trigger from Default to Out.
The component has the following actions, available under the right mouse button:
 Set – this option sets User slot and In slot if there is no link on In slot,
 Set In Hand – this option sets value on Out slot and block changing from any other
slots,
 Set In Auto – this option switches off Hand mode and sets Out slot according to In
slot valueLocal IO components

Version 1.0 Page 25 / 109


The iSMA-B-FCU device has 18 built-in physical inputs and outputs. The figures below
show overview of all inputs and output of iSMA-B-FCU-HH and iSMA-B-FCU-HL devices:

Figure 16 iSMA-B-FCU-HH terminals and internal connection view

Figure 17 iSMA-B-FCU-HL terminals and internal connection view

Version 1.0 Page 26 / 109


4x Special Inputs

All Special inputs have 12-bit resolution which support the following types of inputs:
 Digital Input – Special Input works as a digital input dry contact and reactive
Boolean value false for open circuit and true for close circuit. Circuit status is
measured by 1 mA current,
 Analog Input - Special Input measures voltage in range from 0 to 10 V DC (10 000
mV) with the resolution of 6 mV,
 Resistance Input - Special Input measures resistance value by voltage driver. The
input works in range from 0 to 1000 kΩ (1 MΩ), with resolution ±20 Ω for 20 kΩ load,
 Temperature Input - Special Input measures NTC sensor resistance by voltage
driver and converts to temperature value. Special Input has built-in conversation
table for the following NTC sensors:
o The temperature sensor 10K3A1 NTC B=3975K
o The temperature sensor 10K4A1 NTC B=3695K
o The temperature sensor 10K NTC B=3435K Carel
o The temperature sensor 20K6A1 NTC B=4262K
o The temperature sensor 2,2K3A1 NTC B=3975K
o The temperature sensor 3K3A1 NTC B=3975K
o The temperature sensor 30K6A1 NTC B=4262K
o The temperature sensor SIE1
o The temperature sensor TAC1
o The temperature sensor SAT1

4x Digital Inputs

Digital Inputs support the following types of inputs:


 Dry contact inputs
 Digital Input can work as a counter which counts dry contact impulses up to 100
Hz. Counter value is saved in non-volatile EEPROM memory.
Note: During Restore to default process counters’ value is set to 0.
 Input working as Digital Output (in open collector mode).
3x Analogue Outputs

All Analog Outputs are equipped with 12-bit ADC provides 10 mV resolution and
accuracy less than ±0,5%. Analog Outputs support the following output types:
 Output 0-10 V DC
 Digital Output with maximum load up to 20 mA

Version 1.0 Page 27 / 109


4x Digital Outputs

All Digital Outputs are based on relays which can work with 230 V AC voltage. The iSMA-
B-FCU device has 2 types of Digital Outputs:
 O1-03, 05 – relay outputs connected directly to power supply terminal,
o O1, O2 and O3 are three relay outputs, dedicated to connected up to 3 speed
Fan. The common terminal of these outputs is connected directly to Power
Supply “L” terminal.

Note: Outputs O1-O3 and output O5 are protected by built-in 6 A fuse. Total current for
digital relays outputs O1-03, O5 cannot exceed 6 A. Using fuse with bigger current than
6 A is forbidden! Bigger current may permanently damage device and cause danger to
the user and equipment!

o O5 is a relay outputs, to which can be connected Electrical Heater for example.


This relay is separated from the rest of the control circuit. Current consumption
cannot exceed 10 A for 230 V AC power supply.

Note: This Digital Output has separate circuit with 10 A relay. This circuit
requires external fuse protection up to 10 A. The current bigger than 10 A
may permanently damage device and cause danger to the user and
equipment!

 O4 – relay separated from the FCU controller circuits. To O4 can be connected


Electrical Heater for example. This relay is separated from the rest of the control
circuit. Current consumption cannot exceed 10 A for 230 V AC power supply.

Note: This Digital Output has separate circuit with 10 A relay. This circuit requires
external fuse protection up to 10 A. The current bigger than 10 A may
permanently damage device and cause danger to the user and equipment!

2x Triac Outputs

The iSMA-B-FCU device has two Triac Outputs which are dedicated to heating and
cooling thermal valve actuators.Triac Outputs can be connected actuators with 230
V AC supply (for iSMA-B-FCU-HH ) or actuators with 24 V AC supply (for iSMA-B-
FCU-HL ) depend on the controller’s model.

Triac Output can work as typical binary outputs (for Binary Temperature Control) or
using PWM modulation. PWM mode has two parameters:

Version 1.0 Page 28 / 109


 Duration time in seconds (this value depends on valve parameters)
 Fill out, percentage value of signal fill out.

Note:

In case of iSMA-B-FCU-HH controller, the actuators connected to each Triac Output


can consumed up to 0,5 A.

In case of iSMA-B-FCU-HL controller, sum of power consumption of both Triac


Outputs and 24 V AC output cannot exceed 0,3 A (7 VA):

Imax = 0,3 A = ITO1 + ITO2 + I24VOut.

LocalIO
LocalIO is a main component servicing the physical I/O. Under this component have to
be placed all components used to reading or setting inputs or outputs. LocalIO
component has to be placed under Drivers component.

Figure 18 localIO component

Version 1.0 Page 29 / 109


LocalIOConfig
LocalCOnfig is a component designed to configure the physical input/output of the
device. This component has to be placed under LocalIO component.

Figure 19 LocalIOConfig component

Version 1.0 Page 30 / 109


The component has the following slots:
 SIx Type Integer – Integer value corresponding to the type of temperature sensor.
 SIx Type - The type of temperature sensor connected to special input; table stored
in the device allows you to convert the value of sensor resistance into
temperature.
o Available options: Voltage_Measurement, Temperature_10K3A1,
Temperature_10K4A1, Temperature_10K, Temperature_20K6A1,
Temperature_2_2K3A1, Temperature_3K3A1, Temperature_30K6A1,
Temperature_SEI1, Temperature_TAC1, Temperature_SAT1.

 SIx Filter - The time constant of the low pass filter (to eliminate signal noise)
 AOx Type - Integer value corresponding to analog output mode
 AOx Type - Analog Output Mode: Voltage 0-10 V or PWM
 Default State Of Analog Output x – The analogue output default value after your
reboot the controller expressed in mV.
 Default Digital State Of Analog Output x - The default value of the analogue output,
working in digital mode, when you reboot the device.
 TOx Type Int - Integer value corresponding to TOx Type.
 TOx Type - Triac Output Mode: Digital or PWM.
 Default State Of Triac Output x - The default value of the Triac Output, working in
PWM mode, when you reboot the device. Expressed in %.
 Default State Of Triac Digital Output x - The default value of the Triac Output,
working in digital mode, when you reboot the device.
 Mode - Slot can be set to NORMAL or FAN. If it is value FAN, Digital Outputs O1, O2
and O3, cannot be set to high state at the same time. When it is value NORMAL, this
protection is disabled.
 Default State Of Digital Output x - Digital Output default when you reboot the device.
Any settings of the LocalIOConfig component are carefully stored in the component and
can be transferred to other devices (quick setup of multiple devices).

Version 1.0 Page 31 / 109


LocalIOFolder
LocalIOFolder is a folder for grouping IO components.

Figure 20 LocalIOFolder component

Version 1.0 Page 32 / 109


AODigital
AODigital is a component for servicing analog output in the digital mode (false - 0V, true
- 10V). AODigital has to be placed under LocalIO component.

Figure 21 AODigital component

The component has the following slots:


 Status – Status of AODigital component,
 Fault Cause – Fault cause description,
 Address – Number of physical output of iSMA-B-FCU device (AO1, AO2, AO3),
 Out – Actual state of Output (true / false),
 In – Input slot.
The component has the following action, available under the right mouse button:
 Set– Write value to slot Out and sends it to the device.

Version 1.0 Page 33 / 109


AOVoltage
AOVoltage is a component for servicing Analog Output working as voltage output
(range 0mV – 10 000m V). AOVoltage has to be placed under LocalIO component.

Figure 22 AOVoltage component

The component has the following slots:


 Status – Status of AOVoltage component,
 Fault Cause – Fault cause description,
 Address – Number of physical output of iSMA-B-FCU device (AO1, AO2, AO3),
 Out – Actual value of Output (0mV – 10 000 mV),
 In – Input slot.

The component has the following action, available under the right mouse button:
 Set– Write value to slot Out and sends it to the device.

Version 1.0 Page 34 / 109


DI
DI is a component for reading Digital Input (true or false). DI has to be placed under
LocalIO component.

Figure 23 Di component

The component has the following slots:


 Status – Status of DI component,
 Fault Cause – Fault cause description,
 Address – Number of physical Input of iSMA-B-FCU device (DI1, DI2, DI3, DI4),
 Invert – Negation of Digital Output reading from iSMA-B-FCU device,
 Out – Actual value of Input (true or false).

Version 1.0 Page 35 / 109


DICounter
DICounter is a component reading high-speed counter of Digital Inputs. DICounter has
to be placed under LocalIO component.

Figure 24 DICounter component

The component has the following slots:


 Status – Status of DICounter component,
 Fault Cause – Fault cause description,
 Address – Number of physical Input of iSMA-B-FCU device (DI1, DI2, DI3, DI4),
 Out – Actual value of counter servicing selected Input.
 In – Value which can be set to Out slot, when Set Trigger slot has change from false
to true,
 Set Trigger – when state of slot has changed from false to true, value of In slot is
setting to Out slot.
The component has the following actions, available under the right mouse button:
 Set – Action allows to set value of counter. Set value is override to Out and In slots,
 Reset Counter– Action allows to set value 0. Set value is override to Out and In
slots.

Version 1.0 Page 36 / 109


DO
DO is a component for servicing digital output. DO has to be placed under LocalIO
component.

Figure 25 DO component

The component has the following slots:


 Status – Status of DO component,
 Fault Cause – Fault cause description,
 Address – Number of physical Output of iSMA-B-FCU device (O1, O2, O3, O4, O5),
 Out – Actual state of Output (true / false),
 In – Input slot.

The component has the following action, available under the right mouse button:
 Set– Write value to slot Out and sends it to the device.

Version 1.0 Page 37 / 109


SIDigital
SIDigital is a component for servicing Special Input in the Dry Contact read mode.
SIDigital component has to be placed under LocalIO component.

Figure 26 SIDigital component

The component has the following slots:


 Status – Status of SIDigital component,
 Fault Cause – Fault cause description,
 Address – Number of physical Input of iSMA-B-FCU device (SI1, SI2, SI3, SI4),
 Invert – Negation of special output reading from iSMA-B-FCU device,
 Out – Actual value of input (true or false).

Version 1.0 Page 38 / 109


SIResistance
SIResistance is a component for servicing special input in the resistance read mode.
SIResistance component has to be placed under LocalIO component.

Figure 27 SIResistance component

The component has the following slots:


 Status – Status of SIResistance component,
 Fault Cause – Fault cause description,
 Address – Number of physical Input of iSMA-B-FCU device (SI1, SI2, SI3, SI4),
 Out – Actual value of Input. If voltage measurement is enable, measuring of
resistance is disable and in slot Out is displayed last value of resistance.

Version 1.0 Page 39 / 109


SITemperature
SITemperature is a component for servicing special Input in the temperature read mode
(in order to get reliable reading, you must select the appropriate sensor type in the
component LocalIOConfig). SITemperature component has to be placed under LocalIO
component.

Figure 28 SITemperature component

The component has the following slots:

 Status – Status of SITemperature component,


 Fault Cause – Fault cause description,
 Address – Number of physical Input of iSMA-B-FCU device (SI1, SI2, SI3, SI4),
 Out – Actual value of Input. If voltage measurement is enable, measuring of
temperature is disable and in slot Out is displayed last value of temperature,
measured before switching to voltage measurement.

Version 1.0 Page 40 / 109


SIVoltage
SIVoltage is a component for servicing Special Input in the voltage read mode. To
proper work of component, type of servicing Input have to be set to
Voltage_Measurement. SIVoltage component has to be placed under LocalIO
component.

Figure 29 SIVoltage component

The component has the following slots:


 Status – Status of SIVoltage component,
 Fault Cause – Fault cause description,
 Address – Number of physical Input of iSMA-B-FCU device (SI1, SI2, SI3, SI4),
 Out – Actual value of Input. If temperature measurement is enable, measuring of
voltage is disable and in slot Out is displayed last value of voltage, measured before
switching to temperature measurement.

Version 1.0 Page 41 / 109


TODigital
TODigital is a component servicing Triac Output working in digital mode. TODigital
component has to be placed under LocalIO component.

Figure 30 TODigital component

The component has the following slots:


 Status – Status of TODigital component,
 Fault Cause – Fault cause description,
 Address – Number of physical Triac Output of iSMA-B-FCU device (TO1, TO2),
 Out – Actual value of output,
 In – Input slot.
The component has the following action, available under the right mouse button:
 Set– Write value to slot Out and sends it to the device.

Version 1.0 Page 42 / 109


TOutPWM
TOutPWM is a component for servicing Triac Output working in PWM mode. TOutPWM
component has to be placed under LocalIO component.

Figure 31 TOutPWM component

The component has the following slots:


 Status – Status of TOutPWM component,
 Fault Cause – Fault cause description,
 Address – Number of physical Triac Output of iSMA-B-FCU device (TO1, TO2),
 Out – Actual value of Output,
 In – Input slot.

The component has the following action, available under the right mouse button:
 Set– Write value to slot Out and sends it to the device.

Version 1.0 Page 43 / 109


DIPSwitch
DIPSwitch is a component for reading states of eight binary signals set by CFG DIP
Switch, mounted in iSMA-B-FCU device. Using CFG DIP Switch is recommended to hand
configuration of application. DIPSwitch component has to be placed under LocalIO
component.

Figure 32 DIPSwitch component

The component has the following slots:


 Status – Status of DIPSwitch component,
 Fault Cause – Fault cause description,
 Out1 – Out8 – Actual states of each binary signal from DIP Switch CFG, according
to the figure bellow:

Figure 33 DIPSwitch signals

Version 1.0 Page 44 / 109


In4Out
In4Out is a component servicing Digital Input 4 working as Digital Output. In4Out
component has to be placed under LocalIO component.

Figure 34 In4Out component

The component has the following slots:


 Status – Status of In4Out component,
 Fault Cause – Fault cause description,
 Out – Actual state of Output, which is send to iSMA-B-FCU device. State true
override low state (I4 terminal is connect to ground G0 – voltage between them is
equal 0 V DC). State false does not affect the operation of the component – voltage
between I4 and G0 is equal 5V DC.

The component has the following action, available under the right mouse button:
 Set– Write value to slot Out and sends it to the device.

Version 1.0 Page 45 / 109


LedAlarm
LedAlarm is a component for servicing Alarm LED, mounted in iSMA-B-FCU device. It
allows to signalize defined in application, states of working iSMA-B-FCU devices. For
example, it can be used to signalizing alarms.

LedAlarm component has to be placed under LocalIO component.

Figure 35 LedAlarm component

The component has the following slots:


 Status – Status of LedAlarm component,
 Fault Cause – Fault cause description,
 Out – Actual state of Alarm LED, which is send to iSMA-B-FCU device. State
true – LED lights; state false – LED is off.

The component has the following action, available under the right mouse button:
 Set– Write value to slot Out and sends it to the device.

Version 1.0 Page 46 / 109


Watchdog
Watchdog is a component for controlling communication by RS485 port (COM1) and
USB (only for communication with WorkPlace using SOX protocol or in case of
read/write Modbus Registers using USB connection). The component has to be placed
under LocalIO component.

Figure 36 Watchdog component

The component has the following slots:


 Status – Status of LedAlarm component,
 Fault Cause – Fault cause description,
 Watchdog Time - Time between receive valid messages, value 0 disable this
function,
 Out – Output of Watchdog. When Watchdog is disabled (Watchdog Time slot is set
to 0) or time between receive valid messages has not exceed Watchdog Time – Out
is set to false. When time between receive valid messages has exceed Watchdog
Time – Out is set to true.
The component has the following actions available under the right mouse button:
 Set– Write value to slot Watchdog Time.

Version 1.0 Page 47 / 109


7.2 Slave Network
Slave Network is used to communication iSMA-B-FCU with upper level systems (for
example BMS). Communication can by realized by Modbus RTU / ASCII or BACnet
MSTP protocol (depends of Dip Switch PROTOCOL configuration).

Slave Network Component


Slave Network component is used to management BACnet MSTP or Modbus
RTU/ASCII protocol, using RS485 port. Slave Network component has to be placed
under Drivers component.

Figure 37 Slave Network component

Version 1.0 Page 48 / 109


The component has the following slots:
 Status – Network status,
 Fault Cause – Fault cause description,
 Baud rate – Baud rate of communication (set by PROTOCOL Dip Switch),
 Data Bits – Displays number of data bits. Value is factory set to 8,
 Parity Bits – Configuration of Parity Bits: Parity_Disabled, Odd, Even,
 Stop Bits – Displays number of stop bits. Value is factory set to 1,
 Protocol – Displays protocol used to communication: Modbus or BACnet (set by
PROTOCOL Dip Switch),
 Slave Address – Displays actual address of device (set by MAC Dip Switch),
 Device Name – BACnet device name,
BACnet Id – Actual BACnet Id. Default value is equal 826000 + Slave Address.
BACnet Id can be set using “Set BACnet ID” action.

The component has the following action, available under the right mouse button:
 Set BACnet ID – set BACnet ID of device.

NV Net components
NV Net Components (Non-Volatile Net) are the components whose value can be
recorded in an EEPROM device’s non-volatile memory. Whenever, a device is restarted
or the power is down, the values of NV Net components remain saved. These
components can be also used to send values using BACnet MSTP or Modbus RTU
protocols (depend on Dip Switch PROTOCOL configuration). The device has two types
of NV components, broken down by the type of variables they support.

The components include:


 Boolean variables - component NVNetBoolean
 Numeric (float) variables - component NVNetNumeric
All NV Net components have to be placed under Slave Network component.

Note: iSMA-B-FCU device supports up to 200 NVNetNumeric and up to 200


NVNetBoolean components. Number of free NV memory cells can be checked under
platform properties.

Note: Way of calculating memory cells for NV components is described in Plat service
chapter.Since the values of the components are not stored in the Sedona application
but in the non-volatile memory of the device, when an application is copied between two

Version 1.0 Page 49 / 109


devices, Output values are not saved and will assume the values stored in the local
EEPROM memory. To copy NV Net components to another device along with their
values (e.g. setpoint), use global actions of the plat component:

Step 1 - Use global action "Copy From NV The Default / Copy From NV To User"

Step 2 - Save the application and copy it to another device

Step 3 - Use global action on the target device "Copy From Default To NV / Copy From
User To Nv"

NV Net Numeric Component


NVNetNumeric is a component that stores the Output value in non-volatile memory of
an EEPROM device. After rebooting the device or power failure, the component value is
restored from this particular memory. The NVNetNumeric component occupies a single
memory cell of the Numeric type.

The component has to be placed under Slave Network component.

Note: Way of calculating memory cells for NV components is described in Plat service
chapter.

The NVNetNumeric component is also used to integrate Numeric (float) variables from
various sources. It is done using the "reverse following the link" function. The Out slot is
connected to the In slots of various protocols, for example BACnet or Modbus variable.
Changing a value in one of the components, the device will perform the Set action on
the NV Net component to synchronize the values in all the connected components.
Option is enable only when Link Set slot is set to true.

Version 1.0 Page 50 / 109


Figure 38 NVNetNumeric component

The component has the following slots:


 Status – Actual status of component,
 Fault Cause – Fault case description,
 Units – BACnet unit of point,
 Data Type – Type of data: Int, Long, Float, SInt, SLong,
 Register Type - Register type for Master Device: Holding Register – read/write, Input
Register – read only,
 BACnet Divide By 10 – If slot is set to true and device communicate by BACnet
protocol, value of point which is read/write, is equal value from Out slot divide by
10,
 Analog Value Id – Id of BACnet object,
 Modbus Register – Displays number of Modbus register,
o Modbus Register = 100 + Analog Value Id

Version 1.0 Page 51 / 109


 Link Set – "reverse following the link" function activate,
 Out – Output slot,
 In – Input Slot,
 Cov Increment – minimal change of value,
 User – User value slot (setting by Set action),
 Default – Default value slot (setting by global command from plat action),
 Default Trigger – Copying trigger from Default to Out.

The component has the following action, available under the right mouse button:
 Set– The action sets User slot and In slot if there is no link on In slot.

NV Net Boolean Component


NVNetBoolean is a component which stores the Output value in non-volatile memory
of an EEPROM device. After rebooting the device or power failure, the component value
is restored from this particular memory. The NVNetBoolean component occupies a
single memory cell of the Boolean type.

The component has to be placed under Slave Network component.

Note: Way of calculating memory cells for NV components is described in Plat service
chapter.

The NVNetBoolean component is also used to integrate Boolean variables from various
sources. It is done using the "reverse following the link" function. The Out slot is
connected to the In slots of various protocols, for example BACnet or Modbus variable.
Changing a value in one of the components, the device will perform the Set action on
the NV Net component to synchronize the values in all the connected components.
Option is enable only when Link Set slot is set to true.

Version 1.0 Page 52 / 109


Figure 39 NVNetBoolean component

The component has the following slots:


 Status – Actual status of component,
 Fault Cause – Fault case description,
 Register Type - Register type for Master Device: Coil – read/write, Discrete Input –
read only,
 Binary Value Id – Id of BACnet object,
 Modbus Coil – Displays number of Modbus Coil
o Modbus Coil = 1200 + Binary Value Id,

 Link Set – "reverse following the link" function activate,


 Out – Output slot,
 In – Input Slot,
 User – User value slot (setting by Set action),

Version 1.0 Page 53 / 109


 Default – Default value slot (setting by global command from plat action),
 Default Trigger – Copying trigger from Default to Out.

The component has the following action, available under the right mouse button:
 Set– This action sets User slot and In slot if there is no link on In slot.

8 Modbus Async Network kit


This section provides a collection of procedures to use the iSMA-B-FCU Modbus drivers
to build networks of devices with Modbus points. The iSMA-B-FCU device has
twoRS485 ports. Port COM2 (with RJ12 connector) can be used as a Modbus
RTU/ASCII master. There is no software limitation of devices connected to Modbus
Async bus, but total number of all Modbus points cannot exceed 200.

8.1 Modbus Async Network component


Modbus network is a main component which is responsible for servicing RS485 port
(COM2). The component has to be placed under Drivers folder. ModbusNetwork sets
parameters such as communication baud rate and data format, testing etc. and keeps
statistic.

Version 1.0 Page 54 / 109


Figure 40 ModbusAsyncNetwork component

The component has the following slots:


 Status – Network status,
 Fault Cause – Fault cause description,
 Enable – this option switch on or switch off Modbus network ( „true”- Network
enable, „false”- Network disable),
 Steady Time – Network start up delay time after power up or reset,
 BaudRate – Modbus RS485 port baud rate, available options: 2400, 4800, 9600,
19200, 38400, 57600, 115200 bps,
 Stop Bits – Stop bit definition, available options: 1 bit, 2 bits
 Data Bits – Data bits definition, available options: 7 bits or 8 bits,
 Parity – Parity bit definition, available options: None, Odd, Even, Always1, Always0,

Version 1.0 Page 55 / 109


 Modbus Type – Modbus type definition, available options: RTU or ASCII
 Ping Enable – Enable devices connection testing function,
 Ping Frequency – Time between testing message to check device connection,
 Down Frequency – Time between testing message for devices or points which have
got status down,
 Write On Start – Do write action in device „Writable” components in Modbus
network after reset or power up,
 Write On Up - Do write action in device „Writable” components in Modbus network
after restore the connection with Modbus device,
 Write On Enable - Do write action in device „Writable” components in Modbus
network after enable the device,
 Fast Rate – Time between messages in „Fast” mode poll frequency,
 Normal Rate – Time between messages in „Normal” mode poll frequency,
 Slow Rate – Time between messages in „Slow” mode poll frequency,
 Average Poll Time – Average time for sending/receive one message,
 Busy Time – Percentage of Modbus network usage,
 Total Polls – Total number of messages,
 Fast Polls – Number of messages in sending „Fast” mode,
 Normal Polls – Number of messages in sending „Normal” mode,
 Slow Polls – Number of messages in sending „Slow” mode,
Timeouts – Number of lost messages, difference between sending and receiving
messages,,
 Errors – Number of error messages (for example with wrong CRC)
 Free points – Number of available physical points in Modbus Network.

The component has the following action, available under the right mouse button:
 Reset Stats – Reset statistics of Modbus Async Network,
 Enable – Enable Modbus Async Network,
 Disable – Disable Modbus Async Network.

Version 1.0 Page 56 / 109


8.2 Modbus Async Device component
ModbusDevice is a component which is responsible for servicing physical device
connected to Modbus network. The component has Ping action available under
the right mouse button, which sends test message to device to check device
status. Each ModbusDevice has a “Ping Address” container slot with 3 properties
slots (Address Format, Ping Address Reg, Ping Type). These properties specify a
particular data address (either Input register or holding register) to use as the
device status test (meaning “Monitor” ping requests). Ping requests are
generated at the network-level by the configurable network monitor
(ModbusNetwork -> Ping Enabled). When enabled, a network’s monitor
periodically pings (queries) this address. While receiving any response from the
device, including an exception response, this is considered proof of
communication, and the Modbus client device is no longer considered “down” if
it had been previously marked “down”.
Component has to be placed under Modbus Async Network component.

Figure 41 ModbusAsyncDevice component

Version 1.0 Page 57 / 109


The component has the following slots:
 Status – Device actual status (read Only),
 Fault Cause – Fault cause description,
 Fault Status – device error status (true – device communication error),
 Enable – Enable / Disable device,
 Device Address – Modbus device physical address (0 – network broadcast
address, 1-248 addressing range),
 Timeout – Max. device response time from device request,
 Inter Message Delay – Time between messages sending to device,
 Retry Count – Max. error messages (CRC error, lost messages),
 Address Format – Modbus address format (Modbus, Decimal),
 Ping Address Reg – Any register number Input or Holding type, with will be reading
for device connection test,
 Ping Type – Tested register type: Input/Holding,
 Byte Order – Byte order reading 32 bit: 3210 (Big endian), 1032 (Little endian).

The component has the following action, available under the right mouse button:
 Ping– Sends test message to device to check device status.

Version 1.0 Page 58 / 109


8.3 Modbus Async Boolean Point
Modbus Async Boolean Point is a component which is responsible for reading Boolean
values from device. The component has to be placed under Modbus Async Device
component.

Figure 42 ModbusAsyncBooleanPoint component

The component has the following slots:


 Status – Point status,
 Fault Cause – Fault cause description,
 Fault Status – Point error status (true – point read error),
 Enable – Point enable/disable ( „true”- Point enable, „false”- Point disable),
 Address Format – Register address format, available options: Modbus, Decimal,
 Address – Register address,
 Poll Frequency – Reading poll frequency, available options: Fast, Normal, Slow,
 Status Type – Type of reading register, available options: Input, Coil
 Out – Current value of read registry.

Version 1.0 Page 59 / 109


The component has the following action, available under the right mouse button:
 Read – Action forces the reading of the point.

8.4 Modbus Async Boolean Writtable


Modbus Async Boolean Writable is a component which is responsible for sending and
reading Boolean values from device. Component has to be placed under Modbus
Async Device component.

Figure 43 ModbusAsyncBooleanWritable component

The component has the following slots:


 Status – Point status,
 Fault Cause – Fault cause description,
 Fault Status – Point error status (true – point read/write error),
 Enable – Point enable/disable ( „true”- Point enable, „false”- Point disable),
 Address Format – Register address format, available options: Modbus, Decimal,
 Address – Register address,
 Poll Frequency – Reading poll frequency, available options: Fast, Normal, Slow,
 Write Type – Writing mode, available options: COV – only on Input change,
COV_PollFequrency – on Input change and periodically, PollFequrency – only
periodically, COV_LinkSet – only Input change, using the "reverse following the link"

Version 1.0 Page 60 / 109


function
 Trigger - Remote force sending trigger (on rising edge),
 Out – Output slot, current value of read/write registry,
 In – Input slot.

The component has the following action, available under the right mouse button:
 Set True/Set False – Write value to slot In and sends it to the device (not active
when slot In have connected link),
 Write – send value from slot In to the device,
 Read – read value from device and send to slot Out.

Version 1.0 Page 61 / 109


8.5 Modbus Async Numeric Multi Point
Modbus Async Numeric Multi Point is a component which is responsible for reading up
to 8-16 bits registers from the device in one message. Component use 0x16 Modbus

command. Component has to be placed under Modbus Async Device component.

Figure 44 ModbusAsyncNumericMultiPoint

The component has the following slots:


 Status – Point status,
 Fault Cause – Fault cause description,
 Fault Status – Point error status (true – point read error),
 Enable – Point enable/disable ( „true”- Point enable, „false”- Point disable),
 Address Format – Register address format, available options: Modbus, Decimal,
 Address – Register address,
 Poll Frequency – Reading poll frequency, available options: Fast, Normal, Slow,

Version 1.0 Page 62 / 109


 Reg Type – Type of reading register, available options: Input, Holding,
 Data Type – Read data type: Int (unsigned values), Sint (signed values),
 Number Of Registers – Number of reading register in one messages,
 Out1 – Out8 – Current values of read registry.

The component has the following action, available under the right mouse button:
 Read – Action forces the reading of the point.

8.6 Modbus Async Numeric Point


Modbus Async Numeric Point is a component which is responsible for reading numeric
values from the device. The component has to be placed under Modbus Async Device
component.

Figure 45 ModbusAsyncNumericPoint component

Version 1.0 Page 63 / 109


The component has the following slots:
 Status – Point status,
 Fault Cause – Fault cause description,
 Fault Status – Point error status (true – point read error),
 Enable – Point enable/disable ( „true”- Point enable, „false”- Point disable),
 Address Format – Register address format, available options: Modbus, Decimal,
 Address – Register address,
 Poll Frequency – Reading poll frequency, available options: Fast, Normal, Slow,
 Reg Type – Type of reading register, available options: Input, Holding,
 Data Type – Reading registry data type, available options: Int – 16-bits, Long – 32-
bits,
 Float – 32-bits float-point, SInt – 16-bits with sign, Slong – 32-bits with sign,
 Out – Current value of read registry.

The component has the following action, available under the right mouse button:
 Read – Action forces the reading of the point.

8.7 Modbus Async Numeric Writable


Modbus Async Numeric Writable is a component which is responsible for sending and
reading numeric values from device. Component has to be placed under Modbus Async
Device component.

Version 1.0 Page 64 / 109


Figure 46 ModbusAsyncNumericWritable component

The component has the following slots:


 Status – Network status,
 Fault Cause – Fault cause description,
 Fault Status – Point error status (true – point read/write error),
 Address Format – Register address format, available options: Modbus, Decimal,
 Address – Register address,
 Data Type – Read/write registry data type, available options: Int – 16-bits, Long –
32-bits, Float – 32-bits float-point, SInt – 16-bits with sign, Slong – 32-bits with sign,
 Poll Frequency – Reading poll frequency, available options: Fast, Normal, Slow,
 Write Type – Writing mode, available options: COV – only on input change,
COV_PollFequrency – on input change and periodically, PollFequrency – only
periodically, COV_LinkSet - only on input change, using the "reverse following the
link" function,
 Trigger – Remote force sending trigger (on rising edge),
 Out – Output slot, current value of device registry,
 In – Input slot.

Version 1.0 Page 65 / 109


The component has the following actions available under the right mouse button:
 Set– Write value to slot In and sends it to the device,
 Write – send value from slot In to the device,
 Read – read value from device and sends it to slot Out.
 Send Value – send value to the device, but without changing value on In slot.

8.8 Modbus Async Register Bit Point


Modbus Async Register Bit Point is a component which is responsible for reading
Boolean values from device. The component has to be placed under Modbus Async
Device component.

Figure 47 ModbusAsyncRegisterPoint component

The component has the following slots:


 Status – Point status,
 Fault Cause – Fault cause description,
 Fault Status – Point error status (true – point read error),
 Enable – Point enable/disable ( „true”- Point enable, „false”- Point disable),
 Address Format – Register address format, available options: Modbus, Decimal,
 Address – Register address,

Version 1.0 Page 66 / 109


 Nr Bit – Number of bit in register,
 Poll Frequency – Reading poll frequency, available options: Fast, Normal, Slow,
 Status Type – Type of reading register, available options: Input, Coil,
 Out – Current value of read bit.

The component has the following action, available under the right mouse button:
 Read – Action forces the reading of the point.
8.9 Modbus Async Register Bit Writable
Modbus Async Register Bir Writable is a component which is responsible for sending
and reading Boolean values from the device. The component has to be placed under
Modbus Async Device component.

Figure 48 ModbusAsyncRegisterBitWritable component

The component has the following slots:


 Status – Point status,
 Fault Cause – Fault cause description,
 Fault Status – Point error status (true – point read error),

Version 1.0 Page 67 / 109


 Enable – Point enable/disable ( „true”- Point enable, „false”- Point disable),
 Address Format – Register address format, available options: Modbus, Decimal,
 Address – Register address,
 Nr Bit – Number of bit in register,
 Poll Frequency – Reading poll frequency, available options: Fast, Normal, Slow,
 Write Type – Writing mode, available options: COV – only on input change,
COV_PollFequrency – on input change and periodically, PollFequrency – only
periodically, COV_LinkSet – only input change, using the "reverse following the link"
function,
 Trigger – Remote force sending trigger (on rising edge),
 Out – Current value of read bit,
 In – Input Slot.

The component has the following actions, available under the right mouse button:
 Set True/Set False – Write value to slot In and sends it to the device (not active
when slot In has connected link),
 Write – send value from slot In to the device,
 Read – read value from the device and send to slot Out,
 Send Value – send value to the device, but without changing value on In slot.

8.10 Modbus Folder


ModbusFolder is a component witch groups and organizes Modbus Async points
components.

Version 1.0 Page 68 / 109


9 BACnet Master Slave kit
iSMA-B-FCU device can work in defined groups where one device is master and rest
device (slaves) follows Master parameters. Single Master device can have up to 5 Slave
devices and it is possible to sharing up to 100 points with them.

Note: This function is available only in BACnet MSTP protocol, using RS485 port
(COM1).

9.1 BacnetMasterSlaveNetwork
BACnet Master Slave Network is a main component which is responsible for
communication between Master device and Slave’s devices by BACnet MSTP protocol,
using RS485 port (COM1). BACnet Master Slave Network sets parameters such as
Slave devices Id, communication parameters (such a Poll Frequancy or Max Write
Time) and read status of Slave devices. The component has to be placed under Drivers
folder.

Figure 49 BACnetMasterSlaveNetwork component

Version 1.0 Page 69 / 109


The component has the following slots:
 Status – Point status,
 Fault Cause – Fault cause description,
 Enable – Network enable/disable ( „true”- Point enable, „false”- Point disable),
 Slave1DeviceId – Slave5DeviceId – BACnet Id of slave devices,
 Slave Status1 – Slave Status5 – Statuses of slave devices,
 Poll Frequency – poll frequency off all read only points,
 Max Write Time – Max time between sending values off all writeable points: if value
is equal 0 values of writable points will be send only “on value change”,
 Ping Frequency – Time between testing message to check Slave device connection,
 Ping Trigger – Rising edge of value, force Ping action,
 Free Points – Number of free BACnet Master Slave points.

The component has the following action, available under the right mouse button:
 Ping– Sends test message to Slave devices to check devices’ statuses.

Version 1.0 Page 70 / 109


9.2 AnalogValueRead
Analog Value Read is a component which is responsible for reading analog values from
slave devices. Values are reading with time period define in Poll Frequency slot. Reading
can be also forced using Read action. The component has to be placed under BACnet
Master Slave component.

Figure 50 AnalogValueRead component

The component has the following slots:


 Status – Point status,
 Fault Cause – Fault cause description,
 Enable – Point enable/disable ( „true”- Point enable, „false”- Point disable),
 Object Id – BACnet Id of point,
 In1 – In5 – Slots storage values of points from corresponding slave devices.

Version 1.0 Page 71 / 109


Note: If communication with some Slave devices will be broken, corresponding slot
storages last value, which has been read and slot Status of component displays “Some
Points Down”.

The component has the following action, available under the right mouse button:
 Read – Action forces the reading of the point.

9.3 AnalogValueWrite
Analog Value Write is a component which is responsible for sending analog value to
slave devices. Value is written with period time defined by Max Write Time (only when
value of Max Write Time is higher than 0) and if value of In slot has changed. Writing
can be also forced by Set or Write action. The component has to be placed under
BACnet Master Slave component.

Figure 51 AnalogValueWrite component

Version 1.0 Page 72 / 109


The component has the following slots:
 Status – Point status,
 Fault Cause – Fault cause description,
 Enable – Point enable/disable ( „true”- Point enable, „false”- Point disable),
 Object Id – BACnet Id of point,
 In – Input slot; this value is sent to slave devices.

The component has the following actions, available under the right mouse button:
 Set– Write value to slot In and sends it to slave devices,
 Write – Send value from slot In to slave devices.

9.4 BinaryValueRead
Binary Value Read is a component which is responsible for reading binary values from
slave devices. Values are read with time period define in Poll Frequency slot. Reading
can be also forced using Read action. The component has to be placed under BACnet
Master Slave component.

Figure 52 BinaryValueRead component

Version 1.0 Page 73 / 109


The component has the following slots:
 Status – Point status,
 Fault Cause – Fault cause description,
 Enable – Point enable/disable ( „true”- Point enable, „false”- Point disable),
 Object Id – BACnet Id of point,
 In1 – In2 – States of points from slave devices.

The component has the following action, available under the right mouse button:
 Read – Action forces the reading of the point.

9.5 BinaryValueWrite
Binary Value Write is a component which is responsible for sending binary value to slave
devices. Value is written with period time defined by Max Write Time (only when value
of Max Write Time is greater/higher than 0) and if value of In slot has changed. Writing
can be also forced by Set or Write action. The component has to be placed under
BACnet Master Slave component.

Figure 53 BinaryValueWrite component

Version 1.0 Page 74 / 109


The component has the following slots:
 Status – Point status,
 Fault Cause – Fault cause description,
 Enable – Point enable/disable („true”- Point enable, „false”- Point disable),
 Object Id – BACnet Id of point,
 In – Input slot; this value is sent to slave devices.

The component has the following actions, available under the right mouse button:
 Set– Write value to slot In and sends it to slave devices,
 Write – Send value from slot In to slave devices.

9.6 BACnet Master Slave Folder


BACnet Master Slave Folder is a component witch groups and organizes BACnet
Master Slave points components.

Version 1.0 Page 75 / 109


10 FCU kit
iSMA_FCU kit includes dedicated components, which can be used in typical FCU
application.

10.1 FCU_Antifrost
FCU_Antifrost is a component used to protection against a drop in temperature of
space below the set threshold (with the hysteresis).

When value of space temperature drop below Threshold – Diff (6oC for values in figure
below) and there is no sensor fault, slot Antifrost will change to true. This Action will be
kept until room temperature increase above value equal Threshold + Diff (8oC for values
in figure below). When Temperature sensor is fault (slot Sensor Fault is set to true), slot
Antifrost will be always equal false – component is inactive.

Figure 54 FCU_Antifrost component

The component has the following slots:


 Antifrost – Output Boolean slot; true – “Antifrost”, false – “OK” (no antifrost),
 Sensor Fault – Input Boolean slot, information about fault of temperature sensor; If
slot has value true – Antifrost component is inactive (because value from
temperature sensor is fault and it will be incorrect) and value of Antifrost slot is set

Version 1.0 Page 76 / 109


to false; if Sensor Fault slot has value false – Antifrost component is active,
 Temperature – Value from temperature sensor for controlling space,
 Threshold – Threshold value of temperature,
 Diff – Differential for hysteresis.

10.2 FCU_ChangeOfStateDelay
FCU_ChangeOfStateDelay component allows delaying binary value for time defined in
Delay Time Slot. The component is extended version of On Delay and Off Delay – both
functions are used in one component and there is possibility to set defined by user
status to Output slot (during and after delay time).

Figure 55 FCU_ChangeOfStateDelay component

Version 1.0 Page 77 / 109


The component has the following slots:
 Output – Output Binary slot,
 Input – Input Binary slot; when state of slot has changed (no matter rising or falling
enge), the component starts counting delay time,
 Delay time – Value of delay time in seconds,
 After Delay Set Input Value – Component mode, available values:
o true – If state of Input slot has changed and counting delay time has left, Output
slot has changed to state from Input slot; If counting is progress, to slot Output
is set previous state. For example, if Input slot has state true and it will change
to false, it means that Output slot is still set to true (counting is in progress).
When delay time will be ended, Output slot will be set to false.
o false – If state of Input slot has changed and counting delay time has left, Output
slot has changed to state from End Delay Value slot; During the counting
process, Output slot is set opposite to state of End Value Slot.

 End Delay Value – State, which is set to Output slot, after end of counting process.
During counting process, Output slot is set opposite to state of End Value Slot.
Option is available only when After Delay Set Input Value slot has value false.

Version 1.0 Page 78 / 109


10.3 FCU_EffectiveSetpointCalculator
FCU_EffectiveSetpointCalculator is a component, which allows calculating value of
effective temperature setpoint, according to Setpoint value from higher level system
(for example BMS), offset of this value, occupancy mode and FCU mode (heating or
cooling).

Figure 56 FCU_EffectiveSetpointCalculator component

The component has the following slots:


 Effective Setpoint – Main output slot of component, value is equal to calculate
effective temperature setpoint, according to values of the other slots of component,
 Effective Setpoint Source – Slot displays information about way of calculation,
Effective Setpoint, according to occupancy status and FCU mode And Slot has the
following values:
o 1 – Occupied,
o 2 – Unoccupied_Heating,
o 3 – Unoccupied_Cooling,
o 4 – Standby_Heating,
o 5 – Standby_Cooling.

Version 1.0 Page 79 / 109


 Effective Setpoint Source Id – slot, which displays numeric value, which
corresponds to Effective Setpoint Source slot,
 Setpoint – main input of component, to which is connect value of temperature
Setpoint from higher level system,
 Offset – Value of setpoint offset,
 Occupancy Status – value corresponding to occupancy status:
o 0 – Unoccupied
o 1– Occupied
o 2 – Standby.

 Unoccupied Heat Offset – Value of offset subtracted from setpoint in Unoccupied


mode, when algorithm works in Heating mode.
 Unoccupied Cool Offset – Value of offset added to setpoint in Unoccupied mode,
when algorithm works in Cooling mode.
 Standby Heat Offset – Value of offset subtracted from setpoint in Standby mode,
when algorithm works in Heating mode.
 Standby Cool Offset – Value of offset added to setpoint in Standby mode, when
algorithm works in Cooling mode.
 Heating Cooling – Temperature mode, true – component works in Heating mode,
false – component works in Cooling mode.
 Offset In Occupied Only – Boolean value that sets whether the calculation Effective
Setpoint is to be taken into calculate the value of the Offset slot, if a component is
not in Occupied mode; true – for Unoccupied and Standby mode value of Offset
slot is not to be taken into calculate of Effective Setpoint; false – value of Offset slot
is to be taken into calculate of Effective Setpoint in all occupancy modes.

Version 1.0 Page 80 / 109


The ways of calculating Effective Setpoint value, according to settings of Effective
Setpoint Calculator component have been shown in table below:
Offset In
Heating Effective Setpoint
Occupancy Status Occupied Effective Setpoint
Cooling Source
Only

0 Effective Setpoint = Setpoint + Offset – Unoccupied 2 (Unoccupied


Heating False
(Unoccupied) Heating Offset Heating)

0 Effective Setpoint = Setpoint + Offset + Unoccupied 2 (Unoccupied


Cooling False
(Unoccupied) Cooling Offset Cooling)

0 Effective Setpoint = Setpoint – Unoccupied Heating 2 (Unoccupied


Heating True
(Unoccupied) Offset Heating)

0 Effective Setpoint = Setpoint + Unoccupied Cooling 2 (Unoccupied


Cooling True
(Unoccupied) Offset Cooling)

1 (Occupied) - - Effective Setpoint = Setpoint + Offset 0 (Occupied)

Effective Setpoint = Setpoint + Offset – Standby 2 (Standby


2 (Standby) Heating False
Heating Offset Heating)

Effective Setpoint = Setpoint + Offset + Standby 2 (Standby


2 (Standby) Cooling False
Cooling Offset Cooling)

Effective Setpoint = Setpoint – Standby Heating 2 (Standby


2 (Standby) Heating True
Offset Heating)

Effective Setpoint = Setpoint + Standby Cooling 2 (Standby


2 (Standby) Cooling True
Offset Cooling)
Table 2 Effective Setpoint calculation

Version 1.0 Page 81 / 109


10.4 FCU_FanControl
FCU_FanControl is a component, which allows to control the fan, based on space
temperature, setpoint, Fan mode, FCU mode etc. The component has been created for
fans with 1 speed, 2 speeds, 3 speeds and for fans with analog inputs (type of fan can
be selected by user).

Figure 57 FCU_FanControl component

Version 1.0 Page 82 / 109


The component has the following slots:
 Fan Status – Slot displays current status of fan. Available values:
o 0 – Off
o 1 – Speed 1 (Manual)
o 2 – Speed 2 (Manual)
o 3 – Speed 3 (Manual)
o 4 – Speed 1 (Auto)
o 5– Speed 2 (Auto)
o 6 – Speed 3 (Auto)

 Fan Status Id – Numeric value corresponding to Fan Status slot.


 Fan Analog Out – Output of component for fan with analog input, expressed in
percent. For fans with discrete inputs (Fan Type slot is set to 1, 2 or 3), value of Fan
Analog out is equal 0%.
 Speed 1, Speed 2, Speed 3 – Outputs for fans with binary inputs. For fans with
analog input (Fan Type slot is set to 0), states of Speed 1, Speed 2 and Speed 3 slots
are set to false and cannot be changed by algorithm of component.
Note: The FCU_FanControl component has built-in protection against enable few
speeds in the same time, what can damage physical fan, connected to iSMA-B-FCU
device. When current speed have to be changed to other one, all binary output
responsible for speeds are disabled for 1 second and after that, new speed is
enable.
 Fan Active – Binary output slot to confirm work of fan. If value of Fan Status slot is
/higher than 0, Fan Active slot is set to true. In other cases state of slot is set to
false.
 Fan Mode – Main input of described component. Available values:
o 0 – Off – Fan is disabled
o 1 – Manual Speed 1 – Fan works with speed 1, regardless of the temperature
values. If Fan Type slot is set to 0 (fan with analog input), value of Fan Analog
Out is set to value from Fan Speed 1 Threshold slot.
o 2 – Manual Speed 2 – Fan works with speed 2, regardless of the temperature
value. If Fan Type slot is set to 0 (fan with analog input), value of Fan Analog Out
is set to value from Fan Speed 2 Threshold slot.
o 3 – Manual Speed 3 – Fan works with speed 3, regardless of the temperature
values. If Fan Type slot is set to 0 (fan with analog input), value of Fan Analog
Out is set to value from Fan Speed 3 Threshold slot.
o 4 – Auto – Fan works in automatic mode, current speed depend on current
temperature of space and set Setpoint.

Version 1.0 Page 83 / 109


Note: Value of Fan Mode slot (or current speed, without change of Fan Mode
slot) can be overridden by function built-in algorithm of component, no matter
which value is set to Fan Mode slot. It can be the following cases:
 The component works in Unoccupied or Standby mode (value of Occupancy
Status slot is equal to 0 or 2) – Fan Mode slot is overridden to 4 (Auto mode).
The slot’s overridden will be stopped, when component will work in
Occupancy mode (value of Occupancy Status slot will be equal to 1).
 Window is Open (Window Status slot is set to false) – Fan Mode slot is
overridden to 0 (Off mode). Overridden will be stopped, when Window Status
slot will change to true.
 The component works in Antifrost mode (Antifrost slot is set to true, even
slot Window Status is set to false) – current speed will be overridden by
maximum value available for fan type (depending on value of Fan Type slot).
Overridden will be stopped, when Antifrost slot will change to false.
 The component works in Testing mode (value of Test Mode slot is not equal
to 0) – current speed will be overridden by maximum value available for fan
type (depending on value of Fan Type slot). Overridden will be stop, when Test
Mode slot will change to 0.

 Fan Type – numeric value corresponding to type of controlled fan. Available values:
o 0 – Fan with analog input
o 1 – Fan with 1 binary speed
o 2 – Fan with 2 binary speeds
o 3 – Fan with 3 binary speeds.

Note: The FCU_FanControl component has built-in protection against enable speeds
higher than these resulting from value of Fan Type slot. For example, if Fan Type slot
is set to 1 (fan with 1 binary speed), there is no possibility to enable speeds higher than
1. This protection concerns only fans with binary outputs.
 Occupancy Status – numeric slot corresponding to occupancy status of space.
Available values:
o 0 – Unoccupied
o 1 – Occupied
o 2 – Standby.

 Test Mode – numeric input slot for enable or disable Testing mode. This mode is
inactive when value of slot is equal to 0. In other cases, fan works in Testing Mode
– current speed will be overridden by maximum value available for fan type
(depending on value of Fan Type slot )

Version 1.0 Page 84 / 109


 Cv – value of space temperature, which is used in calculating of fan speed in Auto
mode
 Setpoint – value of space temperature setpoint, which is used in calculating of fan
speed in Auto mode
 Fan Demand – binary slot, used to force switch on of the fan, when it is off (Fan
Active slot is equal to false). If fan is Off (Fan Mode is set to 0) or works in Auto
mode (Fan Mode is set to 4), but calculated by algorithm speed is equal 0, fan can
be switched on by setting true to Fan Demand slot. In this case fan works with
speed 1 (for fans with binary inputs) or with analog value set to Fan Speed 1
Threshold slot (for fan with analog input). When speed (or analog output) calculated
by algorithm will be higher than speed 1 (or value from Fan Speed 1 Threshold slot,
for analog output), speed switches on using Fan Demand, will be overridden by this
value.
 Heating Cooling – binary input slot with information in which temperature mode
fan should actually works (Heating or Cooling); true – component is working in
Heating mode, false – component is working in Cooling mode.
 Antifrost – binary input slot to switch on Antifrost mode:
o true – Antifrost mode enable – current speed will be overridden by maximum
value available for fan type (depending on value of Fan Type slot)
o false – Antifrost mode disable.

 Window Status - binary input slot to switch on Window Is Open mode:


o true – Window Is Open mode disable
o false – Window Is Open mode enable – current value of Fan Mode slot will be
overridden by 0 (Off Mode).

Note: Window Is Open mode can be overridden only by Antifrost mode or Test mode.

 Fan Off Threshold, Fan Speed 1 Threshold, Fan Speed 2 Threshold, Fan Speed 3
Threshold – Values of threshold used to switching speeds of fan (in Auto mode, for
fans with binary inputs), calculating value of Fan Analog Out slot (in Manual modes,
for fan with analog output).
 Fan Scale – numeric input slot with value, which is used? in calculating of fan speed
in Auto mode.
Note: Calculating of fan speeds base on internal variable named Fan Control Value.
The way of calculate this value has been shown in the figures below:

Version 1.0 Page 85 / 109


Figure 58 Way of calculating Fan Control Value

Fan Control Value is used to calculating current speed of fan (for fans with binary
inputs) or value of Fan Analog Out slot (for fan with analog input). The ways of
calculating both values have been shown in the figures below:

Figure 59 Control of fan with analog input in Auto mode

Version 1.0 Page 86 / 109


Figure 60 Control of fan with binary inputs in Auto mode

 Heating Occupied Active – binary input slot, enable/disable function, which force
the fan work. Available values:
o True –function is enable – if fan works in Auto mode (Fan Mode slot is set to 4),
space is occupied (Occupancy Status slot is set to 1) and FCU_FanControl
component works in Heating temperature mode (Heating Cooling slot is set to
true), Fan will be always switch on, even if value of Setpoint slot is lower than
value of Cv slot and (according to the control algorithm) fan should be switched
off.
o False – function is disable.

 Cooling Occupied Active– binary input slot, enable/disable function, which force the
fan work. Available values:
o True –function is enable – if fan works in Auto mode (Fan Mode slot is set to 4),
space is occupied (Occupancy Status slot is set to 1) and FCU_FanControl
component works in Cooling temperature mode (Heating Cooling slot is set to
false), Fan will be always switched on, even if value of Setpoint slot is higher than
value of Cv slot and (according to the control algorithm) fan should be switched
off.
o False – function is disable.

Version 1.0 Page 87 / 109


Note: The way of calculating current speed of fan (for fans with binary inputs) or
value of Fan Analog Out slot (for fan with analog input), when Cooling/Heating
Occupied Active function is enable, has been shown in the figures below:

Figure 61 Heating/Cooling Occupied Active function for fan with analog input

Figure 62 Heating / Cooling Occupied Active function for fans with binary inputs

 Fan Delay Off – value of delay off time, expressed in seconds. Every time, when
value of slot Fan Status is higher than 0 and fan is need to be switched off, it works
with current speed by time equal value of this slot. After this time, Fan will switch
off. If slot is set to 0, function is disabled.

Version 1.0 Page 88 / 109


 Soft Start Time – time, during which fan is working in Soft Start mode, in seconds.
Value 0 disables this function.
 Soft Start Value – value for Soft Start mode, expressed in percent.
Note: Soft Start function is dedicated for fan with analog input. When fan start with
small control value ramp will last long time or it could be impossible which can cause
driver or motor overheat. In this function after fan start output value will be increased
to Fan Soft Star Value for time defined in “Fan Soft Star Time”. If time of soft start has
left, to Fan Analog Out slot is set to current value calculated by algorithm of the
component.

10.5 FCU_HeatingCoolingSwitch

The FCU_HeatingCoolingSwitch component allows switching between Heating and


Cooling temperature mode, according to the current temperature, its setpoint,
occupancy status etc.

Figure 63 FCU_HeatingCoolingSwitch component

Version 1.0 Page 89 / 109


The component has the following slots:
 Heating Cooling – main output of component. Available values:
o True – Heating mode
o False – Cooling mode

 Cv – controlled temperature,
 Setpoint – Setpoint of controlled temperature,
 Diff – Differential for hysteresis,
 Occupancy Status – value corresponding to occupancy status. Available values:
o 0 – Unoccupied
o 1 – Occupied
o 2 – Standby

 Fcu Mode – value corresponding to FCU mode, for example from higher level
system. Available values:
o 0 – Off – FCU is disabled; Heating Cooling slot is set to true.
o 1 – Auto – FCU works in Auto mode, it is possibility to switch between Heating
and Cooling mode.
o 2 – Heating Only – FCU works only in Heating mode; Heating Cooling slot is set
to true
o 3 – Cooling Only – FCU works only in Cooling mode; Heating Cooling slot is set
to false
o 4 – Fan Only – Only fan can work; Heating Cooling slot is set to true.

The FCU_HeatingCoolingSwitch component has predefined modes for values from Fcu
Mode slot:
 If Fcu Mode slot is set to 2 (Heating Only), slot Heating Cooling will be always set to
true (Heating Mode), regardless of the temperature and setpoint values.
 If Fcu Mode slot is set to 3 (Cooling Only), slot Heating Cooling will be always set to
false (Cooling Mode), regardless of the temperature and setpoint values.
 If Fcu Mode slot is set to 0 or 4 (Off or Fan Only), slot Heating Cooling will be always
set to true (Heating Mode), regardless of the temperature and setpoint values.
 If Fcu Mode slot is set to 1 (Auto), slot Heating Cooling is switching between
Heating and Cooling, according to the figure below:

Version 1.0 Page 90 / 109


Figure 64 Switching between Heating and Cooling mode

Note: Heating and Cooling mode can be switched only when Occupancy Status slot is
set to 1 (Occupied mode). If Occupancy Status slot has the other value, to Heating
Cooling slot is set last mode, which has been calculated in Occupied mode.

Version 1.0 Page 91 / 109


10.6 FCU_MasterSlave
The FCU_MasterSlave component allows to automatically calculate BACnet Device Id
of Slave devices in BACnet Master Slave Network, depending on the BACnet Device ID
of Master devices . This function is called Auto Binding. The table below shows values
of Master BACnet Device Id and corresponding to them BACnet Device Id of Slave
devices for Auto Binding Function:
Master Id Slave 1 ID Slave 2 ID Slave 3 ID Slave 4 ID Slave 5 ID

826101 826001 826002 826003 826004 826005


826102 826006 826007 826008 826009 8260010
826103 826011 826012 826013 826014 826015
826104 826016 826017 826018 826019 826020
826105 826021 826022 826023 826024 826025
826106 826026 826027 826028 826029 826030
826107 826031 826032 826033 826034 826035
826108 826036 826037 826038 826039 826040
826109 826041 826042 826043 826044 826045
826110 826046 826047 826048 826049 826050
826111 826051 826052 826053 826054 826055
826112 826056 826057 826058 826059 826060
826113 826061 826062 826063 826064 826065
826114 826066 826067 826068 826069 826070
826115 826071 826072 826073 826074 826075
826116 826076 826077 826078 826079 826080
826117 826081 826082 826083 826084 826085
826118 826086 826087 826088 826089 826090
826119 826091 826092 826093 826094 826095
826120 826096 826097 826098 826099 826100
Other 0 0 0 0 0
Table 3 Master Slave Id - Auto Binding

Auto Binding function can be disable (by setting value true to Local Remote Auto
Binding slot). In this case, Id of Slave devices has to be set by user (in slots Remote
Slave 1 Device Id – Remote Slave 5 Device Id).

Version 1.0 Page 92 / 109


Figure 65 FCU_MasterSlave

The component has the following slots:


 Slave1 Device Id – Slave5 Device Id – outputs of component, display calculated or
set Id of five Slave devices,
 Master Local Device Id – Id of Master device.
Note: If component uses Auto Binding function, value of Master Local Device Id slot
has to be set to value from range 826101 – 826120. For other values, all output slots
(Slave1 Device Id – Slave5 Device Id) will be set to 0.

 Local Remote Auto Binding – slot allows switching between Auto Binding and
Remote Binding, availablevalues:
o True – Remote Banding – Id of each Slave Device (slots Slave1 Device Id –
Slave5 Device Id) are set to corresponding to them value of Remote Id (slots
Remote Slave 1 Device Id – Remote Slave 2 Device Id)
o False – Auto Binding – Id of each Slave Device (slots Slave1 Device Id – Slave5
Device Id) are calculated according to the table above.

 Remote Slave 1 Device Id – Remote Slave 2 Device Id – slots with remote Id of


Slave devices. If slot Local Remote Auto Binding is set to true, these values are set
to corresponding outputs (slots Slave1 Device Id – Slave5 Device Id).

Version 1.0 Page 93 / 109


10.7 FCU_ModeCalculator
The FCU_ModeCalculator component allows switching main modes of application ( for
example override Fan Mode, according others values or enable/disable temperature
control), according to Fan Mode, Fcu Mode and type of temperature control (analog or
binary). The component can be used to protection against incorrect operation of FCU
device.

Figure 66 FCU_ModeCalculator component

The component has the following slots:


 Fan Mode Out – Output of Fan Mode value, calculated according to the algorithm
of component:
o If value of Fcu Mode slot is equal to 0 (FCU is switch Off from upper level
system), slot Fan Mode Out is also set to 0 (fan is also switch off).
o If value of Fan Mode slot is lower than 4 (Fan is Off or works in one of manual
modes) and value of slot Occupancy Status is not equal to 1 (the component
works in Unoccupied or Standby mode), slot Fan Mode Out is set to 4 (fan works
in Auto mode).
o In the other cases, value of Fan Mode Out slot is equal to value of Fan Mode slot.

Version 1.0 Page 94 / 109


 Occupancy Status – value corresponding to Occupancy Status; available values:
o 0 –Unoccupied,
o 1– Occupied,
o 2 – Standby.

 Temperature Binary Enable – output binary slot to enable or disable binary


temperature mode, according to the algorithm of component:
o If slot Temperature Control is set to false (Binary Control) and value of Fan Mode
Out is higher than 0 (fan is switch on), to Temperature Binary Enable slot is set
true.
o If slot Temperature Control is set to false (Binary Control) and slot Antifrost is
set to true (component works in Antifrost mode), to Temperature Binary Enable
slot is set true.
o In the other cases, Temperature Binary Enable slot is set false.

 Temperature Analog Enable – output binary slot to enable or disable analog


temperature mode, according to the algorithm of the component:
o If slot Temperature Control is set to true (Analog Control) and value of Fan Mode
Out is higher than 0 (fan is switch on), to Temperature Analog Enable slot is set
true.
o If slot Temperature Control is set to true (Analog Control) and slot Antifrost is set
to true (component works in Antifrost mode), to Temperature Analog Enable slot
is set true.
o In the other cases, Temperature Analog Enable slot is set false.

 Fcu Mode – numeric input with value corresponding to mode of FCU; available
values:
o 0 – Off
o 1 – Auto
o 2 – Heating Only
o 3 – Cooling Only
o 4 – Fan Only.

Note: If Fcu Mode slot is set to 4 (Fan Only) and Antifrost slot is set to false (no
Antifrost mode), slots Temperature Binary Enable and Temperature Analog Enable are
overridden to false.

Version 1.0 Page 95 / 109


 Fan Mode – numeric input with value corresponding to fan mode; available values:
o 0 – Off
o 1 – Manual Speed 1
o 2 – Manual Speed 2
o 3 – Manual Speed 3
o 4 – Auto

 Temperature Control – binary input slot to select mode of temperature control;


available values:
o True – Analog Control
o False – Binary Control

 Antifrost – binary input slot to enable/disable Antifrost mode;


o True – Antifrost mode enable
o False – Antifrost mode disable.

Version 1.0 Page 96 / 109


10.8 FCU_Multiply
The FCU_Multiply component allows to multiply up to 10 different values by the same
one value.

Figure 67 FCU_Multiply component

The component has the following slots:


 Output1 – Output10 – Outputs slots of the component,
 Input1 – Input10 – Inputs slots of the component,
 Multiply Value – Value, by which Inputs are multiplying,

Version 1.0 Page 97 / 109


10.9 FCU_OccupancyCalculator
The FCU_OccupancyCalculator component manages Occupancy Status, according to
the occupancy modes and states of presence sensor, card holders etc.

Figure 68 Fcu_OccupancyCalculator component

The component has the following slots:


 Occupancy Status – slot displays current Occupancy Status; available values:
o 0 – Unoccupied
o 1 – Occupied
o 2 – Standby

 Occupancy Status Id – output numeric value corresponding to Occupancy Status


slot

Version 1.0 Page 98 / 109


 Forced Occupied – binary output slot with information about occupancy status
source. Available values
o True – Occupied mode has been forced. It means, that component works in
Occupied mode (Occupancy Status Id slot is set to 1), but this mode has not
been calculated according to Occupancy Mode. Occupied mode can be forced
by Panel (value of Occupancy Mode Panel slot), presence sensor or card holder
(detecting rising edge on Presence Sensor Card Holder slot) or by remote trigger
(detecting rising edge on Remote Occupancy slot).
o False – Occupied mode has not been forced.

 Panel Mode Reset – binary output, which can be used to reset value from
component connected to Occupancy Mode Panel after switch off Occupancy Mode,
which has been forced by Panel. Panel Mode Reset slot has value false. It is set to
true for one application cycle, when time of Occupancy mode forced by panel has
left.
 Occupancy Mode – value corresponding to Occupancy mode set from upper level
system; available values:
o 0 – Unoccupied
o 1 – Occupied
o 2 – Standby

 Occupancy Mode Panel – value corresponding to Occupancy mode set from


external source (for example dedicated to iSMA-B-FCU device panel); available
values:
o 0 – Unoccupied
o 1 – Occupied

Note: Value of Occupancy Mode Panel slot allows to force Occupied Mode from panel.
If Occupancy Mode slot is set to 0 or 2 (Unoccupied or Standby), setting value of
Occupancy Mode Panel slot to 1 (Occupied) will force Occupied mode for time defined
in Occupancy Time For Remote Trigger slot. During this time Forced Occupied slot
has value true. After that time, value of Panel Mode Reset slot is set to true for one
cycle of application and component go back to previous Occupancy Mode. Occupied
mode forced in this way can be also cancelled by setting back Occupancy Mode Panel
slot to 0 (Unoccupied).

Version 1.0 Page 99 / 109


 Remote Occupancy Trigger – binary input (recommended for remote occupancy
trigger), which allows to force Occupied mode. If Occupancy Mode slot is set to 0
or 2 (Unoccupied or Standby), rising edge detected on this slot will force Occupied
mode for time defined in Occupancy Time For Remote Trigger slot. Counting of this
time starts, when on described slot will be detected falling edge. During this time
Forced Occupied slot has value true. After that time, the component goes back to
previous Occupancy Mode. Occupied mode forced in this way cannot be cancelled.
 Presence Sensor Card Holder – binary input (recommended for presence sensor or
card holder), which allows to force Occupied mode. If Occupancy Mode slot is set
to 0 or 2 (Unoccupied or Standby), rising edge detected on this slot will force
Occupied mode for time defined in Occupancy Time For Presence Sensor slot.
Counting of this time starts, when on described slot will be detected falling edge.
During this time Forced Occupied slot has value true. After that time, the
component goes back to previous Occupancy Mode. Occupied mode forced in this
way cannot be cancelled.
 Occupancy Time For Remote Trigger – Time of Occupancy mode forced by Panel
or Remote Trigger.
 Occupancy Time For Presence Sensor – Time of Occupancy mode forced by
presence sensor or card holder.

Version 1.0 Page 100 / 109


10.10 FCU_OutputsSwitch
The FCU_OutputSwitch component allows to manage outputs for temperature and fan
control, according to FCU configuration (2 or 4 pipe system, analog or binary
temperature control etc.).

Figure 69 FCU_OutputsSwitch compomnent

Version 1.0 Page 101 / 109


The component has the following slots:
 Heating Valve – Numeric output slot, which displays status of heating valve. Value
can be displayed in two ways:
o Displaying 0 or 1 – for temperature binary output (if Analog Output Enable slot
is set to false); 0 – valve close, 1– valve open
o Displaying value of Analog Heating In slot – for temperature analog output (if
Analog Output Enable slot is set to true).

 Cooling Valve – Numeric output slot, which displays status of cooling valve. Value
can be displayed in two ways:
o Displaying 0 or 1 – for temperature binary output (if Analog Output Enable slot
is set to false); 0 – valve close, 1– valve open
o Displaying value of Analog Cooling In slot – for temperature analog output (if
Analog Output Enable slot is set to true).
o

 Fan Value – Numeric output slot, which displays status of fan. Value can be
displayed in two ways:
o Displaying 0, 1, 2 or 3 – for fan binary outputs (if Fan Type slot is not equal to 0),
according to value of Fan Status slot; available values:

 0 – Off (if Fan Status slot is equal 0),


 1– Speed 1 (if Fan Status slot is equal 1 or 4),
 2– Speed 2 (if Fan Status slot is equal 2 or 5),
 3– Speed 3 (if Fan Status slot is equal 3 or 6).

o Displaying value of Fan Analog In slot – for fan analog output (if Fan Type slot is
equal to 0).

 Analog Heating Out – numeric output slot for analog heating valve.
o For 2 pipes system (slot Mode _2 Pipes is set to true), when slot Analog Outputs
Enable is set to true, Analog Heating Out slot displays value of Analog Heating In
slot or Analog Cooling In slot. It depends on which slot has value greater than 0
(this value is set to Analog Heating Out slot).
o For 4 pipes system (slot Mode _2 Pipes is set to false), slot Analog Heating Out
can only display value of Analog Heating In.
o If slot Analog Outputs Enable is set to false (the component use only binary
outputs), slot Analog Heating Out is set to 0.

Version 1.0 Page 102 / 109


 Analog Cooling Out – numeric output slot for analog cooling valve.
o For 4 pipes system (slot Mode _2 Pipes is set to false), slot Analog Cooling Out
displays value of slot Analog Heating In.
o If slot Analog Outputs Enable is set to false (the component uses only binary
outputs) or slot Mode _2 Pipes is set to false (for 4 pipes system), slot Analog
Cooling Out is set to 0.

 Second Stage Heating Out – binary output slot for second stage heating. Slot
displays value from slot Second Stage Heating In .
Note: If Heating Second Stage Enable slot is set to false or Heating Relay Enable
slot is set to false, Second Stage Heating Out slot cannot be set to true.

 Second Stage Cooling Out – binary output slot for second stage cooling. Slot
displays value from slot Second Stage Cooling In.
Note: If Cooling Second Stage Enable slot is set to false or Cooling Relay Enable
slot is set to false, Second Stage Cooling Out slot cannot be set to true.

 Digital Heating – binary output slot for digital heating (recommended to service
heating valve switched on/off by Triac).
o For 2 pipes system (slot Mode _2 Pipes is set to true), when slot Analog Outputs
Enable is set to false, Digital Heating slot displays value of Binary Heating In slot
or Binary Cooling In slot. It depends on which slot has true value (this value is set
to Digital Heating slot).
o For 4 pipes system (slot Mode _2 Pipes is set to false), slot Digital Heating can
only display value of Binary Heating In.
o If slot Analog Outputs Enable is set to true (the component use only analog
outputs), slot Digital Heating is set to false.

 Digital Cooling – binary output slot for digital cooling (recommended to service
cooling valve switched on/off by Triac).
o For 4 pipes system (slot Mode _2 Pipes is set to false), slot Digital Cooling
displays value of slot Binary Heating In.
o If slot Analog Outputs Enable is set to true (the component use only analog
outputs) or slot Mode _2 Pipes is set to false (for 4 pipes system), slot Digital
Cooling is set to false.

Version 1.0 Page 103 / 109


 Relay Heating – binary output slot for digital heating in 1st or 2nd stage
(recommended to service heating valve switched by relay output or electrical
heaters).
o If slot Heating Relay Enable is set to true and slot Heating Second Stage Enable
is set to false (heating in 1st stage only), to slot Relay Heating is set value from
slot Binary Heating In.
o If slot Heating Relay Enable is set to true, and slot Heating Second Stage Enable
is set to true (heating in 1st and 2nd stage), to slot Relay Heating is set value from
slot second Stage Heating In.
o If slot Heating Relay Enable is set to false (heating relay is disable), to slot Relay
Heating is set value false.

 Relay Cooling – binary output slot for digital cooling in 1st or 2nd stage
(recommended to service cooling valve switched by relay output or electrical
coolers).
o If slot Cooling Relay Enable is set to true and slot Cooling Second Stage Enable
is set to false (cooling in 1st stage only), to slot Relay Cooling is set value from
slot Binary Cooling In.
o If slot Cooling Relay Enable is set to true, and slot Cooling Second Stage Enable
is set to true (cooling in 1st and 2nd stage), to slot Relay Cooling is set value from
slot second Stage Cooling In.
o If slot Cooling Relay Enable is set to false (cooling relay is disable), to slot Relay
Cooling is set value false.

 Heating Second Stage Enable – binary input allows to enable or disable 2nd stage
heating; true – enable, false – disable,
 Cooling Second Stage Enable – binary input allows to enable or disable 2 nd stage
cooling; true – enable, false – disable,
 Heating Relay Enable – binary input allows to enable or disable relay for heating;
true – enable, false – disable,
 Cooling Relay Enable – binary input allows to enable or disable relay for cooling;
true – enable, false – disable,
 Mode _2 Pipes – binary input allows to switch between 2 pipes system and 4 pipes
system; true – 2 pipes system, false – 4 pipes system,
 Analog Outputs Enable – binary input allows to switch between analog or binary
control of temperature outputs; true – Analog Outputs, false – Binary Outputs,
 Analog Heating In – Numeric input of analog value for heating,
 Analog Cooling In – Numeric input of analog value for cooling,
 Binary Heating In – Input of binary value for 1st stage heating,
 Binary Cooling In – Input of binary value for 1st stage cooling,
 Second Stage Heating In – Input of binary value for 2nd stage heating,

Version 1.0 Page 104 / 109


 Second Stage Cooling In – Input of binary value for 2nd stage cooling,
 Fan Analog In – Numeric input of analog value for fan
 Fan Type – Numeric input of corresponding to type of fan; available values:
o 0 – fan with analog output
o Other values – fan with binary outputs.

 Fan Status – numeric input slot of current fan speed; available values:
o 0 – Off,
o 1 or 4 –Speed 1,
o 2 or 5 – Speed 2,
o 3 or 6 – Speed 3.

Version 1.0 Page 105 / 109


10.11 FCU_SensorFault
The FCU_SensorFault component allows to detect sensor fault according to value of
temperature.

Figure 70 FCU_SensorFault component

The component has the following slots:


 Fault – Binary output switch. If temperature from sensor (set to In slot) is lower
than value from Min Fault Value or higher than value from Max Fault Value slot for
longer than time set to Fault Delay Time slot, Fault slot is set to true (Sensor Fault).
In the other case, Fault slot is set to false (OK).
 In – Input for temperature value from sensor,
 Min Fault Value – Value of minimum acceptable temperature,
 Max Fault Value – Value of maximum acceptable temperature,
 Fault Delay Time – Delay time for detecting sensor fault.

Version 1.0 Page 106 / 109


10.12 FCU_Temperature_Sensors_Switch
The FCU_Temperature_Sensors_Switch component allows to switch temperature
sensors, according to selected source.

Figure 71 FCU_Temperature_Sensors_Switch component

The component has the following slots:


 Temperature Source – Slot displays information about source of temperature set
to Cv slot; available values:
o 0 – Sensor Fault (fault of sensor selected by Main Temperature Source slot)
o 1 – LCD Panel
o 2 – Simple Panel
o 3 – Return
o 4 – Net Temperature
 Temperature Source Id – Numeric output with value corresponding to Temperature
Source slot,

Version 1.0 Page 107 / 109


 Cv – Output value of temperature, switching according to value of Main
Temperature slot.
o If Main Temperature Source slot is set to 1 (LCD Panel) and:
 If panel is connected (slot Lcd Panel Connected is set to true), to slot Cv is
set value from Lcd Panel Temperature slot.
 If panel is not connected (slot Lcd Panel Connected is set to false), to slot Cv
is set value from Temperature When Sensors Are Fault slot.
o For the others sources:
 If it has not been detected fault of sensor selected by value of Main
Temperature Source value (corresponding to fault slot is set to false), to Cv
slot is set value from slot corresponding to selected temperature.
 If it has been detected fault of sensor selected by value of Main Temperature
Source value, to Cv slot is set value from slot Temperature When Sensors
Are Fault slot.
o If to Cv slot is set value from Return Temperature, it is possibility to switch
temperature from Remote to Space for defined time after switch off fan. Fan
Active and Fan Active With Delay slots are used to this function. If both slots
have different states, to slot Cv is set value from Space Temperature slot
(instead value from Return Temperature slot). If both slots have the same states
(true or false), to Cv slot is set value from Return Temperature slot.
Note: To proper work of function is required external component, which delays value
informing about fan status. Value without delay has to be connected to Fan Active
slot and value with delay has to be connected to Fan Active With Delay slot.

Note: If Return Temperature Fault slot is set to true (sensor fault), it is taken value
from Temperature When Sensors Are Fault (instead Return Temperature). If Space
Temperature Fault slot is set to true (sensor fault), function is inactive.
 Space Temperature Fault – Status of space temperature; true – fault, false – no
fault.
 Space Temperature – Output value of space temperature. It is calculated in the way
described below:
o Lcd Panel Temperature hasthe highest priority . If Panel is connected (Lcd Panel
Connected slot is set to true), to Space Temperature slot is set value from Lcd
Panel Temperature slot.
o If Panel is disconnected (Lcd Panel Connected slot is set to false) and there is
no fault of simple panel temperature sensor (Simple Panel Temperature Fault is
set to false), to Space Temperature slot is set value from Simple Panel
Temperature slot.
o If Lcd Panel is disconnected, Simple Panel sensor is fault and there is no fault of
temperature sensor which is used to calculate Cv value (value of Temperature

Version 1.0 Page 108 / 109


Source Id slot is greater than 0), to Space Temperature slot is set value from Cv
slot.
Note: In all cases described above, slot Space Temperature Fault is set to false
(there is no fault). In other cases, this slot is set to true.
 Main Temperature Source – Input numeric slot, which allows to select source of
temperature; available values:
o 0 – LCD Panel Temperature
o 1 – Simple Panel Temperature
o 2 – Return Temperature
o 3 – Net Temperature

 Return Temperature Fault – Binary input slot with status of Return Temperature
sensor; true – sensor fault, false – sensor operates correct,
 Return Temperature – Numeric input with temperature from Return Temperature
sensor,
 Lcd Panel Connected – Binary input slot with status of LCD Panel; true – Panel
connected, false – Panel disconnected,
 Lcd Panel Temperature – Numeric input with temperature from LCD Panel
Temperature sensor,
 Simple Panel Temperature Fault – Binary input slot with status of Simple Panel
Temperature sensor; true – sensor fault, false – sensor operates correct,
 Simple Panel Temperature – Numeric input with temperature from Simply Panel
Temperature sensor,
 Net Temperature Fault – Binary input slot with status of Net Temperature sensor;
true – sensor fault, false – sensor operate correct,
 Net Temperature – Numeric input with Net Temperature value,
 Fan Active – Binary input slot with status of fan; true – fan switches on, false – fan
switches off,
 Fan Active With Delay – Binary input slot with status of fan (with external delay);
true – fan switches on, false – fan switches off,
 Temperature When Sensors Are Fault – Value of temperature, which will be set to
Cv slot, if sensor selected by value of MainTemperature Source is fault.

Version 1.0 Page 109 / 109

You might also like