IQ3 Configuration Manual: Issue 3
IQ3 Configuration Manual: Issue 3
Issue 3
Author: Technical Publications
Issue: 3
Date: 28/01/2009
Part Number: TE200768
Copyright: © 2009 Honeywell Technologies Sàrl, ECC Division. All rights reserved.
All rights reserved. This manual contains proprietary information that is protected by copyright. No part of this manual
may be reproduced, transcribed, stored in a retrieval system, translated into any language or computer language, or
transmitted in any form whatsoever without the prior consent of the publisher.
Manufactured for and on behalf of the Environmental and Combustion Controls Division of Honeywell Technologies
Sàrl, Z.A, La Pièce, 16, 1180 Rolle,Switzerland by its Authorized Representative, Trend Control Systems Limited
For information contact:
Trend Control Systems Limited
P.O. Box 34
Horsham
W. Sussex RH12 2YF
NOTICE: Trend Control Systems Limited makes no representations or warranties of any kind whatsoever with respect to
the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular
purpose. Trend Control Systems Limited shall not be liable for any errors contained herein or for incidental or consequential
damages in connection with the furnishing, performance or use of this material. Trend Control Systems Limited reserves
the right to revise this publication from time to time and make changes in the content hereof without obligation to notify
any person of such revisions or changes.
Please send any comments about this or any other Trend technical publication to [email protected]
Table of Contents
TABLE OF CONTENTS
PART 1, SECTION 1: INTRODUCTION .......................................................................................................... 21
1.1 Aim .................................................................................................................................................................... 21
1.2 System ............................................................................................................................................................... 21
1.3 Using This Manual ............................................................................................................................................ 21
PART 1, SECTION 2: SYSTEM CONFIGURATION ........................................................................................ 23
2.1 System Levels ................................................................................................................................................... 23
2.1.1 Supervisor Level .............................................................................................................................. 23
2.1.2 IQ System Network .......................................................................................................................... 23
2.1.3 Controller Level ............................................................................................................................... 24
2.1.4 Input/output level ............................................................................................................................ 24
2.1.5 Field network ................................................................................................................................... 24
2.2 IQ System Network ............................................................................................................................................ 24
2.2.1 IQ System Lans ................................................................................................................................ 24
2.2.2 IQ System Internetwork ................................................................................................................... 25
2.3 Network Media .................................................................................................................................................. 25
2.3.1 Current Loop ................................................................................................................................... 25
2.3.2 Ethernet ............................................................................................................................................ 25
2.3.3 LONWORKS® ..................................................................................................................................................................... 26
2.4 IQ System Nodes ............................................................................................................................................... 26
2.5 Multiple Internetwork Segments ....................................................................................................................... 29
PART 1, SECTION 3: IQ3 COMMUNICATIONS ............................................................................................. 31
3.1 IQ3 Communications ......................................................................................................................................... 31
3.2 RS232 Port Communications ............................................................................................................................. 32
3.3 Ethernet Communications ................................................................................................................................. 33
3.3.1 Web Browser Access to IQ3 Controllers ........................................................................................ 33
3.3.2 Networks .......................................................................................................................................... 33
3.3.3 Stand Alone IQ3 .............................................................................................................................. 34
3.3.4 Supervisor Connection to IQ3 ......................................................................................................... 34
3.3.5 Supervisor Connection to IQ3 via a Router .................................................................................... 35
3.3.6 Using Routers to provide Multiple Sites ......................................................................................... 36
3.3.7 Configuring IQ3s to Cross Routers ................................................................................................. 36
3.3.8 When not to Cross Routers ............................................................................................................ 37
3.3.9 IQ3 with 3xtend/EINC L ................................................................................................................... 38
3.3.9.1 Supervisor Mode ............................................................................................................ 39
3.3.9.2 Alarm Mode ................................................................................................................... 39
3.3.10 IQ3s and IQView .............................................................................................................................. 40
3.3.11 Automatic IP Addressing ................................................................................................................ 41
3.3.11.1 DHCP Operation ............................................................................................................. 41
3.3.11.2 Link/Local Operation ...................................................................................................... 41
3.3.11.3 Host name ...................................................................................................................... 41
3.3.11.4 Email Server Address ..................................................................................................... 42
3.3.11.5 Crossing Routers if DHCP is operating .......................................................................... 42
3.3.11.6 Link/local Default Operation .......................................................................................... 42
3.3.11.7 Servers used in Auto-addressing .................................................................................. 42
3.3.11.8 Fixing a Device’s Address on a DHCP controlled System ............................................. 42
3.3.12 UDP .................................................................................................................................................. 43
3.3.13 FTP .................................................................................................................................................. 43
3.4 I/O Bus ............................................................................................................................................................... 44
3.5 Current Loop ..................................................................................................................................................... 44
3.6 Serial Interface ................................................................................................................................................... 45
3.7 BACnet .............................................................................................................................................................. 45
3.7.1 BACnet Protocol ............................................................................................................................. 46
3.7.2 BACnet Properties Supported ......................................................................................................... 47
3.7.2.1 BACnet Analogue Input Object .................................................................................... 48
3.7.2.2 BACnet Binary Input Object .......................................................................................... 49
3.7.2.3 BACnet Analogue Output Object .................................................................................. 50
3.7.2.4 BACnet Binary Output Object ....................................................................................... 51
3.7.2.5 BACnet Analogue Value Object .................................................................................... 52
3.7.2.6 BACnet Binary Value Object .......................................................................................... 52
This manual is specific to the IQ3 range of controllers; the IQ1xx and IQ2xx controllers are covered by the IQ
Configuration Reference Manual 90-1533 and its addendum TD200118.
The IQ3 v2 controller can only be fully configured using Trend’s System Engineering Tool (SET v6.2). Readers should
also refer to the SET Manual, TE200147.
1.2 System
The Trend IQ3 Controller is a microprocessor based configurable controller which is applicable to many types of
buildings and plant. It can be used in stand alone situations or in a system with up to 13,688 other IQ controllers. Such
systems are referred to as ‘sites’; larger supervisors (e.g. 963) can access multiple sites.
In general an IQ controller is designed so that one product can be configured to satisfy a wide range of control and
monitoring situations.
A small IQ may be fitted to each item of plant (unitary controller) or a larger IQ may be used to meet the control
requirements of a small building.
Any small system may be expanded as the need arises, by networking. In a networked system, the IQ has the capacity
of inter-controller communications. This means that information can be transferred between controllers, providing
a fully integrated system and retaining the considerable advantages of distributed control.
Using Wide Area Networks (WANs e.g. Internet, PSTN) a building can become one of many controlled entirely from
a central office anywhere in the world.
Some IQ Controllers have a local Display Panel (SDU, or IQView) to enable local monitoring and adjustment by an
operator.
An IQ System Supervisor or networked display panel can be used to monitor and adjust the IQ controllers via the network.
These have user-friendly displays which facilitate the understanding and adjustment of the system. There are different
types of supervisor software which can run on a range of computers. A portable computer may be connected to a
controller via its local supervisor connector, to give either access to a single controller, or access to the network.
Part 1 covers basic principles that apply across the strategy modules.
Remainder of manual.
Networked
Supervisor Display
Supervisor level
Panel
IQ system network
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
Local
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
Controller
Controller level Display
°C
Controller
AUTO
Panel SP ENG
24 V
24 V
EARTHED OK RX P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
Field network
Input/output level
sensor valve
Supervisor level: Supervisors (e.g. 963), Tools (e.g SET), or Networked Display Panels (e.g. IQView).
IQ system network: This network carries communications between the supervisors and controllers
Controller level: This is the level where local control of the BMS plant takes place. There is a variety of IQ system
controllers (e.g. IQ3) some of which may have local display panels (e.g. SDU).
Field network: This network carries communications between the controllers and the input/output devices. Some
devices are wired point to point (directly from device to the controller I/O terminal), whereas others connect via a field
network.`
Input/output level: This level contains all the input/output transducers connected to controllers. This includes sensors,
valves, relay modules and other interfaces (e.g. E to P convertor).
The international standard ISO16484 proposes a general structure for building automation systems. The diagram below
indicates this structure and shows how some of the IQ system devices fit in.
The network can be run over a number of different media including the IQ system current loop, Ethernet, and LonWorks.
IQ System Current Loop (see Network Engineering Manual 92-1375)
Ethernet (see IQ System Ethernet Products Engineering Manual TE200369)
LonWorks (see IQ System LonWorks Products Engineering Manual TE200292)
Autodialling-PSTN, PSDN, and other components can be used to access either Lans or internetworks that are not directly
connected to the main network, (see the Autodialling Reference Manual 90-1353 for more details).
Node
Device
An IQ system Lan is a number of IQ system devices that are grouped together because they have the same Lan number.
They must all be on the same subnetwork (e.g. the same Ethernet segment). The Lan can use the IQ system current loop,
Ethernet, or LonWorks to send the messages between the devices on the Lan, however it is not possible to mix media
on the same Lan. An IQ system Lan can also exist inside a single IQ system device if the device has more than one node,
e.g. a controller’s CNC and a virtual CNC.
Each device on the IQ system network must have a node to connect it to the network. The node is normally built into
the device, but can be a separate node connected to the device via an RS232 connection. Some devices have more than
one node e.g. those with virtual CNCs.
Each node on the Lan must have a unique network address. The address can be set in the range 0 to 128, however
addresses 0, 2, 3, 10, and >119 are not allowed on the Lan. This gives a maximum of 116 nodes.
The internetwork can use the IQ system current loop, Ethernet, or LonWorks to send the messages between the
internetwork devices. It may consist either of only one medium, or two, or a combination of all three media.
A Lan is connected to the internetwork by an Internetwork Node Controller, INC, class of device (e.g. INC2, EINC or
LINC). This type of device can also act as a media converter. (Note that IQ3 controllers have their own virtual INC.)
An INC automatically takes address 126 on the Lan. Its variable address setting is used to set the Lan’s address on the
internetwork, known as the Lan number. This address, like the node address on the Lan, can be set in the range 0 to 128,
but Lan numbers 0, 2, 3, 10, and >119 are not allowed on the internetwork. This gives a maximum of 116 Lans on the
internetwork.
Autodialling or TCP/IP dialup enable multiple sites, each of which may have an internetwork (see the Autodialling
Reference Manual (90-1353) for more details of autodialling).
There can only be one INC class node (INC2, EINC, LINC, or 3xtend/EINC L) on a Lan.
2.3.2 Ethernet
Using an Ethernet network to build a Lan or internetwork enables much faster communication speed between devices
than is available with the IQ system current loop. It also reduces the amount of cabling required, as Lans and internetworks
operate over the same piece of cable.
Ethernet and TCP/IP technology is the basis of the Internet, therefore, if required, the use of Ethernet enables information
from IQ controllers to be accessed from anywhere in the world. The Ethernet network may already be present, and
therefore the IQ system is able to make use of the existing infrastructure and thereby reduce installation cost.
Standard Ethernet devices such as routers, and hubs can be used to build the network to enable the TCP/IP connection to
be made between the devices providing great flexibility when installing a system. For example, modem routers could be used
to reach devices on another Ethernet network over a PSTN link.
IQ3 controllers that form a Lan with other IQ3 controllers do not require their baud rate to be set up because it is determined
by the Ethernet cabling. Because all IQ3 controllers on a Lan must be on the same Ethernet network segment, these baud
rates will be the same.
When IQ System devices (e.g. IQ3 controllers and IQView) form a Lan over an Ethernet network, the device with the lowest
address acts as an INC enabling links to other Lans in the normal way. An IQ3 controller that has not formed a Lan with
other IQ3 controllers will connect to the internetwork using its own virtual INC.
2.3.3 LONWORKS®
The LONWORKS network is an open system in that it enables different suppliers of equipment to use the same network (i.e.
coexist), thus saving the user the cost of installing severral different networks. It goes further in defining standards for
interoperability. The IQ system on the LONWORKS network may either be installed to share the network with other
suppliers’ products, or it may be the sole system on the LONWORKS network. IQ system products can be installed on
either a shared or a sole system without any specialised LONWORKS installation. The IQ system LONWORKS products
come with default settings that enable them to be installed on a LONWORKS network using traditional IQ network
knowledge; in this way they can coexist with other suppliers’ products.
Using a LONWORKS network to build a Lan or internetwork enables faster communication speed between devices than
is available with the IQ system current loop. It also reduces the amount of cabling required, as Lans and internetworks
operate over the same piece of cable. The LONWORKS network may already be present, and therefore the IQ system is
able to make use of the existing infrastructure and therefore reduce installation cost.
Proprietary LONWORKS sensors and output devices can be bound to the IQL strategy modules or to LONC variables.
In this case the LONWORKS network is being used as a field network, in addition to its use as IQ system network
For more details of how IQ System products can make use of LONWORKS networks see the see the IQ system LONWORKS
Products Engineering Guide (TE200292).
CNC2: This node (Communications Node Controller) is used to connect a supervisor to the current loop Lan. It has an
RS232 interface which can be connected to a PC running supervisory or tool software. It can be supplied in a box (NBOX),
or as a board for fitting in a (IQ1xx or IQ2xx) controller.
Local device
(e.g. Supervisor)
RS232 port
receive port transmit port
CNC2
current loop
IQ with CNC Lan CNC2 NDP
integral CNC IQ
IQ with CNC
integral CNC IQ
In the diagram a normal INC has the Lan on its ‘A’ side and the Internetwork on its ‘B’ side whereas an internetwork
repeater has internetwork on both A and B sides. Only the ‘B’ side may be set to 38k4 baud.
The TMN, EINC, LINC, and 3xtend/EINC L are used to extend the communications in various ways.
TMN: This node (Trend Modem Node) is used to extend the communications using autodialling (see autodialling manual).
EINC: This node (Ethernet Internetwork Node Controller) is used to connect a current loop section of the IQ system
network to an Ethernet section. Since IQ3s are able to connect directly to Ethernet*, it also enables communication
between IQ1xx, IQ2xx controllers and IQ3s. It acts in a similar fashion to an INC as described above. If its address (Lan
number) is <100, it connects a current loop Lan to the Ethernet internetwork, but if its address is =>100 it extends an existing
current loop internetwork onto the Ethernet.
Lan
address =>100
Lan INC
addresses <100 A IQ3
Ethernet
EINC I/N EINC
Ethernet address <100
EINC
IQ3 EINC INC
Lan
IQ Lan IQ IQ Lan IQ
IQ
EINCs connecting current loop Lans to EINC connecting current loop internetwork
Ethernet internetwork to Ethernet internetwork
It also contains 4 virtual CNCs (vCNCs) which enable Ethernet connected PCs running supervisors or IQ system tools
to connect to the IQ system Lans via IP addressing and controllers to send back alarms to the PCs.
Ethernet
Lan
IQ
This diagram shows the 4 virtual CNCs within the EINC, and also its virtual INC which allows the EINC to connect to
an internetwork on Ethernet
Pc A Pc B
IQ3
Ethernet
IQ3 Device
control Connections
EINC
Lan A
Lan B
IQ
This diagram shows the equivalent IQ system network structure. The EINC’s virtual CNCs (A to D) sit on Lan B and are
connected by current loop to an IQ2 controller. The PCs A and B connect to the virtual CNCs A and B using Ethernet
connections. The vINC in the EINC and the vINC in the IQ3 create an internetwork on Ethernet, and the IQ3’s CNC and
vINC create Lan A within the IQ3.
LINC: This node (LONWORKS Internetwork Node Controller) is used to extend the communications via the LONWORKS
network. This enables the LONWORKS network to be used as the IQ system internetwork, and acts in a similar fashion
to an INC as described above. If its address (Lan number) is <100, it connects a current loop Lan to the LONWORKS
internetwork (LONWORKS INC mode), but if its address is =>100, it extends an existing IQ system internetwork onto the
LONWORKS network (internetwork LONWORKS extension mode).
Lan
IQ
LINCs connecting current loop Lans to LINC connecting current loop internetwork
LONWORKS internetwork to L ONWORKS internetwork
It also acts as the interface to the IQLs (IQ system LONWORKS node controllers).
Lan 1
Lan 5 Lan 5 Lan 5
Address 20 Address 21 Address 22
LINC IQL IQL IQL
LONWORKS network
IQ3
NID
Serial No : : : : :
10
L
IQL
LAN O/S
Strategy
IQ3
NID
Serial No : : : : :
Current loop
1 2 3 4 5 6 7 8 9 10 LON SRV 11 12 13 14 15 24V
COM OK PIN
1 2 24V
3 4 24V
5 1 LON ac
Lan
IQ2 1 2
3
3 4
4
5 24V
5
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V
OK
Tx Rx
internetwork
1 2
3
3 4
4
5 24V
5
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V
OK
Tx Rx
IQ2
The above diagram shows the 3xtend/EINC L in INC mode (Lan number<100). It enables a current loop Lan of controllers
to connect via the internetwork to an IQ3 Lan on Ethernet, and an IQL Lan on the LONWORKS network. The 3xtend/EINC L
forms an internetwork with an IQ3 and an IQL both of which have virtual INCs as shown by the dashed line
The 3xtend/EINC L contains 8 virtual CNCs which enable Ethernet connected PCs running supervisors or IQ system tools
to connect to the IQ system Lans via IP addressing and controllers to send back alarms to the PCs.
EINC Ethernet
Lan EINC I/N LINC
LONWORKS
network
LINC
IQ3 IQ3 IQ3
LINC Lan
LONWORKS
network
LINC
Lan
The central EINC and LINC can be replaced by the 3xtend/EINC L in internetwork extension mode to simplify the system
as shown below:
IQL IQL IQL
3xtend/
Ethernet
Lan
EINC
EINC L LONWORKS
network
LINC
LINC Lan
LONWORKS
network
LINC
Lan
Note that the LONWORKS network is not to be used where a high level of network traffic is expected e.g joining
internetworks or where there are many IQ system devices on many IQ system Lans being accessed across an internetwork
routed through the LONWORKS network; an alternative topology should be used such as an Ethernet network.
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0 + 1 0 + 2 0 + 3 0 + 4 0 + 1 0 + 2 0 + 3 0 + 4 0
Local
Sensor/Knob, RS232 Ethernet
Supervisor/
Switches
100-240 V A 11 12 13 14 15 16 P 5 0 P 6 0 P 7 0 P 8 0 P 5 0 P 6 0 P 7 0 P 8 0
P 0 P 0 P 0 P 0 P 0 P 0
24 V
24 V
OK RX P 13 14 15 16 17 18 19 20 21 22 23 24 P 13 14 15 16 17 18 19 20 21 22 23 24
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
Tool Display Panel
RD-IQ IQView
SDU-XCITE
I/O Bus
Web browser/
Supervisor/
Tools
Only one RS232
device may be Additional IQ3s can be
connected IQView connected to Ethernet
wireless receiver
XW/R/IQ
Optional auxiliary boards provide additional current loop (/LAN option) and serial (/SER option) ports.
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0 100-240 V A 11 12 13 14 15 16
24 V
24 V
OK RX P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 P 0 P 0 P 0 P 0 P 0 P
0V
0
24 V
24 V
OK RX P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
This port is limited to communicating directly with its IQ3 if the address module supervisor port address = 0, but if the
supervisor port address is set greater than 0 it can communicate by way of the network using an internal CNC (supervisor
CNC, sCNC).
Ethernet: This is the main network for the IQ3 controller. It enables:
IP communications with the IQ3 (e.g. from a web browser (thin client))
Creation of Trend network on Ethernet (Lans and internetwork)
Trend communications from a supervisor or tool (thick client) by use of IQ3 virtual Communications Node
Controller (vCNC)
IC communications between controllers (peer to peer Ethernet communications)
Email alarms from IQ3
IP alarms from IQ3
Download from SET of strategy and all other configuration files
Remote PCs can communicate via standard IT networks (e.g. the Internet) using IP, enabling communication from
anywhere in the world if required.
When the /LAN option is fitted the IQ3 can no longer be part of an Ethernet Lan or internetwork, and can no longer
communicate over Ethernet using IC Communications. However, all other types of Ethernet communication listed above
still operate.
Extra Serial Interface: This is only available if the serial interface board option is fitted (/SER). The /SER option is only
available on versions of IQ3/XNC. The IQ3/XNC/SER option enables communication with a 3rd party system using the
external serial interface.
The extra serial interface may be either RS232, RS485 2 wire, or RS485 4 wire (which may also be used for RS422
communications)
This port can communicate directly with the IQ3, if the address module supervisor port address = 0, or to the network
via an sCNC connection if the supervisor port address is greater than 0. Setting the supervisor port address non-zero
creates the sCNC and it will not be seen on the network map (e.g. SET System View) if the address is zero.
IQView IQView
SDU-XCITE Local Supervisor/Tool
RD-IQ
Local Supervisor/Tool RS232 RS232
IQ3 IQ3
IQ3 IQ3
control control
CNC CNC sCNC
The RD-IQ will use the following settings by default: S9 (local temperature), K1 (setpoint), K6 (occupation status) and
K7 (fan speed status). These default settings may be changed using the RD’s front panel buttons.
Note that the strategy file may be uploaded or downloaded by SET by way of the RS232 port but not the other configuration
files: language, backdrop, and XNC (for IQ3/XNC versions only). SET is able to perform Live Edit, Live Values, and
Mapping via the RS232 port.
If the PC and the IQ3 are separated by routers, then the PC’s default router (default gateway) needs to be set up in the
PC and the IQ3’s default router (router 1 in address module) needs to be set up in the IQ3.
IP address: 192.168.2.2
IP address: 192.168.1.2
Default Gateway: 192.168.2.254
Router 1: 192.168.1.254
Router Router
Ethernet
IP address: 192.168.2.254 IP address: 192.168.1.254
Note that the default router is a router on the same segment as the device (i.e. not separated from the device by another
router).
There may be a firewall(s) between the PC and the IQ3, either at the PC end, the IQ3 end, or both. In this case ensure
that port 80 is open in both directions send, and receive, on the firewall(s), as IQ3 uses port 80 for its web server.
3.3.2 Networks
The IQ3 will create its own internal Lan which can include a node for its own controller, a supervisor CNC for its local
supervisor port (if supervisor port address is set non-zero), a virtual CNC, and a virtual INC (address 126).
IQ3
RS232
IQ3
control
vINC vCNC CNC sCNC
internal Lan
The above diagram shows the IQ3 control unit connected via its own CNC to a internal network including its supervisor
CNC (RS232), its virtual CNC, and its virtual INC.
Note that the virtual CNC has to be created by setting up its outstation address and port number, and it will not be seen
on the network map (e.g. SET System View) unless these are set up.
If multiple IQ3s with the same Lan number are connected to Ethernet, then an Ethernet Lan will form to include these IQ3s
and their internal nodes. They must be on the same Ethernet segment and in the same subnet and use the same UDP
port. The IQ3 with the lowest IP address also assumes the INC functionality (the other virtual INC(s) disappear) and is
responsible for maintaining the Lan across the IQ3s.
IQ3 IQ3
RS232 RS232
IQ3 IQ3
control control
vCNC CNC sCNC vINC vCNC CNC sCNC
Lan
If IQ3s have different Lan numbers they connect together via an internetwork on Ethernet. In this case the IQ3s with
the lowest IP address on each Lan retain their INCs, while any other IQ3s lose theirs. The vINCs are responsible for
constructing the internetwork.
IQ3
RS232
IQ3
control
vINC vCNC CNC sCNC
Lan
I/N
IQ3
RS232
IQ3
control
vINC vCNC CNC sCNC
Lan
Note that Trend Ethernet system devices (e.g. IQ3, EINC, 3xtend/EINC L) on the same Ethernet segment must all be
on the same subnet (unless they use different UDP settings - see 3.3.12 below).
IP address: 192.168.1.2
IQ 3 Controller Lan 24 Outstation 24
vCNC Outstation 25, port 10025
Ethernet
Note that if the IQ3 has a large strategy the IQ3 vCNC should not be used as the main supervisor connection to a large
system; this should be done using a 3xtend/EINC L (see section 3.3.9 below).
IQ3
RS232
IQ3
control
vINC vCNC CNC sCNC
Lan 24
Both the PC and IQ3 must be installed correctly on Ethernet (i.e. both have their own IP addresses and subnet masks
set up).
The IQ3 must also have the following setup:
IQ3 Lan number
IQ3 control CNC outstation address
vCNC outstation address
vCNC port number
Since the vCNC and the IQ3 control CNC are always on the same Lan, there is only one Lan number for the IQ3.
The vCNC port number is to distinguish an IP connection to the vCNC (e.g. at port 10025) from an IP connection to the
IQ3 control section (e.g. a web browser connection to port 80).
The supervisor can now connect to the vCNC using the vCNC’s IP address and port number (e.g. IP address: 192.168.1.2
port:10025). It is then a member of the IQ3’s Lan as far as IQ addressing goes and can send IQ system communications
via the vCNC to the IQ3 using Lan and outstation addressing (e.g. Lan 24, Outstation 24).
If the supervisor (e.g. IQView or 963) connection to the vCNC is permanent, then the IQ3 can send Trend Lan type alarms
(traditional IQ system alarms using Lan and outstation addressing) to the vCNC to which the 963 is connected.
However, if the supervisor (e.g. 963) connection is temporary (i.e. TCP/IP dial up), then there are 2 choices:
1. Send alarms as IP address type (recommended).
2. Use an EINC or 3xtend/EINC L vCNC in alarm mode (see section 3.3.9 below)
To send alarms as IP address type, the IQ3 alarm destination module needs to be set up with the supervisor’s IP address
and port number. On multi-site systems all IQ3s on a site must be setup with the same Site Identifier and GUID (which
are both unique to that site) in order for reliable receipt of IP address type alarms.
IQ 3
IP address: 192.168.2.2
IP address: 192.168.1.2
Default Gateway: 192.168.2.254
Router 1: 192.168.1.254
Router Router
Ethernet
IP address: 192.168.2.254 IP address: 192.168.1.254
There may be a firewall(s) between the PC and the IQ3, either at the PC end, the IQ3 end or both. In this case ensure that
the port used by the IQ3’s vCNC (e.g. 25 in 3.3.4 above) is open in both directions (send and receive) on the firewall(s).
Router
If the IQ3s are not configured to cross the router as described below, they will construct two separate networks one each
side of the router.
Only one internetwork is allowed on a site, but the 963 supervisor can treat the networks as separate sites and each site
may have an internetwork. The supervisor will change the IP address of the IQ3 vCNC to which it connects as it switches
sites. Note that there cannot be any IC comms between the sites.
IQ3 alarms can be sent to the supervisor directly as IP address type alarms.
This is an example of using the GUID to identify the site. IQ3A & IQ3B should both use the same GUID which will be
different from the GUID used by IQ3C & IQ3D.
IP Address: 1.1.1.2
This information enables IQ3A to construct an internetwork with IQ3B across the router.
If more than one router is involved, IQ3B will also have to be set up to create an internetwork with IQ3A:
e.g. IQ3B settings
Network module, Router 1: 1.1.2.2
Network module, remote Trend device n, IP address: 1.1.1.1
Network module, remote Trend device n, subnet mask: 255.255.255.0
If several IQ3s are connected one side of a router, the IQ3 with the lowest IP address (cross-router master) will attempt
to construct the network across the router if it has been set up correctly.
Router
In the diagram, if the cross router master is IQ3A, it should be set up with the information for an IQ3 the other side, e.g.
IQ3C. IQ3A will then construct the internetwork across the router. If IQ3C were to be switched off, the message from IQ3A
will no longer reach the remaining IQ3 on the far subnet (IQ3D).
To prevent this, IQ3D’s details should also be entered in the network module of IQ3A so that it can connect to IQ3D if
IQ3C is switched off.
To reduce the risk of losing communications due to the loss of power to one device, the two devices with the lowest
IP addresses from each subnet should be set up in the two devices with the lowest IP addresses on the local subnet.
Because IP addresses may not be fixed (see Automatic IP Addressing Mode -later) it may not be possible to specify which
controllers have the lowest IP addresses, so the details should be set up in every device on the subnet so that any device
may be able to become the cross-router master. If Automatic IP Addressing mode is being used, the remote devices will
be identified by host names rather then IP addresses.
It is recommended that the details of two devices (either IQ3s , 3xtend/EINC Ls, or IQViews) in the network from each
subnet the other side of a router (s) should be set up in every device (either IQ3s , 3xtend/EINC Ls, or IQViews) on the
local subnet. For increased reliability, details of additional devices should also be set up.
SET facilitates setting up the Remote Devices List. The Remote Devices should be set up in one controller in the Network
module dialogue box, and the ’Set Project Defaults’ button selected. The next controllers should then be selected and
the ‘Use Project Defaults’ button in its Network Module dialogue box selected; this will populate the Remote Devices’
details (see Pt. 2 section 20.1.2.3)
Note that the lowest IP address on each Lan will assume INC responsibility and join the internetworks, while the lowest
IP address on the subnet will become the cross router master (if remote Trend device set up) and attempt to cross the
router. Thus the cross router master will also have INC responsibility for its own Lan.
Building Trend system across routers is intended for use in Intranet applications where the quality of the service
between nodes on the network is permanently good. For wide area applications, or where there may be poor or
intermittent connectivity then multi-site networking using temporary vCNC connections into the sites is recommended.
If the WAN is a ‘good IP’ connection (i.e. permanent, good quality) then the internetwork over WAN is possible.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0 1 2 3 4 5 6 7 8 9 10
+ 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0
963
System Supervisor
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0 1 2 3 4 5 6 7 8 9 10
+ 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0
100-240 V A 11 12 13 14 15 16 100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
0V
100-240 V A 11 12 13 14 15 16 100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
0V
Router
Router
WAN
Router
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0 1 2 3 4 5 6 7 8 9 10
+ 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0
100-240 V A 11 12 13 14 15 16 100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
0V
The above diagram shows 3 networks connected via a WAN. One of them has a 963 supervisor.
The preferred method is to set the 963 to talk to each network using the IP address of a vCNC in one of the IQ3s in each
network. The 963 then treats each system as a separate site. (A similar method can be used for a web browser accessing
web pages.) The IQ3s can send their alarms to the 963 as IP alarms.
However, if the IQ3s have to talk to each other using IC Comms then an internetwork has to be constructed crossing the routers
using the methods described in 3.3.7 above; this can only be done if there is a good IP connection (e.g. intranetwork) .
If the 963 were replaced by an IQView then the IQView would not be able to easily change its IP connection (i.e. not be
able to access multiple sites). The 3 networks could be accessed using an IQView if they were connected via an
internetwork which crossed the routers with the same provisos as above.
Ethernet
Tool
B Web
Browser
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
Local Supervisor/
C
100-240 V A
P
11
0 P 0 P
12
0 P 0 P 0 P
13
0
14 15 16
Tool
24 V
24 V
OK RX P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
Supervisor/
D Tool
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
24 V
24 V
OK RX P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
3xtend/EINC L
CNC
3xtend/ Current Loop Lan
EINC L
LONWORKS network
OK OK OK
Tx Rx Tx Rx Tx Rx
1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V
3 4 5 3 4 5 3 4 5
IQL
IQL
The plain EINC is also able to create an internetwork as described here but is not able to work in an auto-addressing
environment (e.g. DHCP - see 3.3.11 below), neither can it support the LONWORKS bus.
Supervisor/ A B Web
Tool Browser
C Local Supervisor/
TCP/IP Tool
TCP/IP
IQ3 RS232
IQ3
control
vINC vCNC CNC sCNC
Lan
Alarms
by
I/N
TCP/IP
IQ3
IQ3
control
vINC vCNC CNC sCNC
Lan
Internetwork on Ethernet
Supervisor/
3xtend/EINC L D
Tool
Lan
OK OK OK
Tx Rx Tx Rx Tx Rx
1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V
3 4 5 3 4 5 3 4 5
IQL
vINC CNC
LONWORKS IQL
Lan network
The two IQ3s can connect together along with the 3xtend/EINC L via an Ethernet internetwork. The 3xtend/EINC L extends
this onto the LONWORKS network to connect to the IQL’s vINC. The 3xtend/EINC L also contains virtual CNCs which
appear on its Lan together with the IQ2 series controllers and supervisor/software tool PC D.
PC D can communicate with the IQ and IQL controllers, and all the controllers’ alarms can be sent to PC D.
Note that 3xtend/EINC L and EINC cannot be on the same current loop Lan as they both contain a virtual
INC. IQ3 cannot be on the same Ethernet Lan as either of these as their Lan numbers are for their local current
loop Lans, so the local Lan setting in the IQ3’s address module, the 3xtend/EINC L’s address switch setting,
! and the EINC’s address switch setting must all be different. (However, an IQ3/LAN could be on the same
current loop Lan as 3xtend/EINC L or EINC and note that the IQ3/LAN does not contain a vINC).
Note that if SET were running on PCD, it would be able to download a strategy file to an IQ3, but not the other
configuration files. The full configuration files download must be done via a vCNC Ethernet connection.
Since both 3xtend/EINC Ls and IQ3s can appear either side of a router, if there is a router separating the internetwork,
the lowest IP addresses either side of the router may be those of either or both IQ3, and 3xtend/EINC L. These details
would be set up in the IQ3’s network module and in the 3xtend/EINC L’s remoteEinc module. The same rules for setting
up the remote devices’ details quoted previously apply to both IQ3s and 3xtend/EINC Ls.
Note that if an IQ3 is added to an existing system with 3xtend/EINC Ls either side of a router and has the
lowest IP address then its virtual INC will become the cross-router master and must have its remote devices’
! details set up; failure to do this will stop system communications across the router.
The plain EINC (as opposed to 3xtend/EINC L) should not be used on a system using auto-addressing (e.g. DHCP - see
3.3.11 below).
The 3xtend/EINC L virtual CNCs can operate in either supervisor or alarm mode (unlike an IQ3 vCNC which can only
operate in supervisor mode).
equivalent to Pc A
Pc A Pc B
963
Pc B
Ethernet
Ethernet
Device
LONWORKS permanent
temporary
TCP dial up Connections
3xtend network
EINC L 3xtend/
EINC L
Lan
vINC vCNCA vCNCB vCNCC vCNCD
Lan
IQ
The Supervisor mode of a virtual CNC enables the connection between a PC running supervisory or tool software and
the IQ network to be made over Ethernet to the virtual CNC, rather than the normal RS232 connection to a standard CNC.
The supervisor/tool connects to the vCNC by using the 3xtend/EINC L’s/IQ3 controller’s IP address and the port address
as set up in the vCNC module. This enables the supervisor/tool to communicate with devices on the IQ network, and,
if the connection is permanent, for those devices to communicate with it (e.g. send an alarm).
The vCNC appears to be located on the controller’s local Lan and will respond to Lan mapping in this way. In order for
the vCNC to operate, its ‘CNC Address’ must be set up, until this is done the vCNC function is switched off.
The 962 v3 (or greater) or 963 has the ability to make temporary connections to vCNCs, treating each connection as a separate
site (TCP/IP dial up). It can optionally make a permanent connection as previously described. However, a temporary connection
will not allow the vCNC to send alarms back to the supervisor, instead a vCNC in alarm mode can be used. For IQ3s the use
of IP Destination Type alarms is recommended.
The IQ3 vCNC cannot operate in alarm mode. If an IQ3 wishes to send alarms to a 963 which is using temporary
connections, then it can either:
1. Send alarms as IP Address type (recommended)
2. Use a 3xtend/EINC L vCNC in alarm mode.
Supervisor/Tool
IQView
3xtend/
EINC L Current loop
IQ3
OK OK OK
Tx Rx Tx Rx Tx Rx
RJ45
1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V
3 4 5 3 4 5 3 4 5
Ethernet
IQ3
RS232
IQ3
control
vINC vCNC CNC CNC
Lan
Supervisor/
3xtend/EINC L A
Tool
Lan
OK OK OK
Tx Rx Tx Rx Tx Rx
1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V
3 4 5 3 4 5 3 4 5
This is a normal supervisor connection to IQ3 as described in 3.3.4 above and the IQView must be configured with its
own IP address, subnet mask, and default gateway, as well as the IP address of the IQ3 and the port number of the vCNC.
IQ3 IQView
RS232
IQ3
control
vINC vCNC CNC CNC vCNC
Lan
Supervisor/
3xtend/EINC L A
Tool
Lan
OK OK OK
Tx Rx Tx Rx Tx Rx
1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V 1 2 3 4 5 24V
6
24V
AC 7 8
24V
AC 9 10
24V
AC 11 230 V
3 4 5 3 4 5 3 4 5
The IQView has an internal vCNC. To use this the IQView must be configured to connect as Device/Ethernet Lan with
its own Ethernet IP Address, subnet mask, and default gateway. The IQView’s internal vCNC must have its Lan number
and outstation address set up.
Note that the IQView always makes a permanent IP connection to its vCNC. It cannot perform TCP/IP dial up, and
is not a multi-site supervisor like the 963.
The IQ3 will be set to automatic IP addressing mode by default. If the IP Addressing Mode parameter in the IQ3’s network
module is set to ‘Obtain Automatically’ (default setting) then the IP address will be generated automatically, if set to
‘Enter Manually’ then the IP address has to be configured manually.
If the controller is in automatic IP addressing mode and the DHCP server fails to respond, the IQ3 will enter link/local
mode where it will negotiate its IP address with the other devices on its Ethernet segment.
IP Addressing Mode IP addressing set up by
Obtain Automatically DHCP IP address may vary
Link/local
Enter Manually Manual IP address fixed
The devices on the segment which are set for automatic IP addressing (including IQView, 3xtend EINC L, and PCs which
could be running 963 or SET) will negotiate their IP addresses between themselves.
A PC (running supervisor or tool software) should be set up for auto-addressing. On DHCP failure it may take a very
long time to enter link/local and be able to communicate with the IQ3s, and there will appear to be communication failure.
This can be avoided by power cycling the PC which will cause it to enter link/local on power up.
In link/local mode the IP addresses start at 169.254.0.0, the subnet mask will be set to its default (255.255.0.0), and the
Router 1, WINS servers, and DNS servers will remain at their last settings. Any devices wanting to communicate with
an IQ3 in link/local using IP addressing must be on the subnet so defined.
If a WINS server does not exist, the host name can be used over the local segment only (i.e. not across routers).
The host name can also be used to communicate with the IQ3 if the IP Addressing Mode parameter (in network module)
is set to ‘Enter Manually’. This provides a user-friendly way of identifying the controller rather than remembering its
IP address.
Default Host Name: If the host name has not been set up, the IQ3 will power up with a default host name which is a function
of its MAC address (‘Trend’ plus the last six digits of the MAC address e.g. TREND_00_14_D0). The default host name
will always be operational (as well as its Hostname if it has been set up), unless the Default Hostname parameter (network
module) has been set to ‘Disabled’.
Thus if email alarms are being sent and the email server address is identified by a domain name then a DNS server must
be present on the system, and the DNS server address must be set up in the IQ3.
If the network is to cross a router, the details of two devices in the network from each subnet the other side of a router
should be set up in every device in the network on the local subnet. For increased reliability, details of additional devices
should also be set up.
Note that if any communication using a host name crosses a router(s), then a WINS server address must be set up.
Note that it is recommended that link/local only be used as normal operation on a single segment system, (not across
a router). Also note that any other device communicating with the IQ3 (e.g. a supervisor PC) must also be in link/local.
If host names are being used for IP addressing across a router, then a WINS server must be installed somewhere on the
system.
If email alarms are being sent, and the email server address is identified by Internet domain name, then a DNS server must
be installed somewhere on the system.
3.3.12 UDP
The most familiar transport communication protocol is TCP/IP. However, the IQ system on Ethernet also uses TCP/UDP.
UDP (User Datagram Protocol) is used by IQ system Ethernet devices to build Lans and the internetwork, and to cross
routers; it also is used by IC Comms.
Note that the 963 only uses TCP/IP protocol whereas IQView uses both TCP/IP and TCP/UDP as IQView may include
a vCNC which is able to connect to an IQ system Ethernet Lan.
To construct a network the Ethernet devices (3xtend/EINC L, IQ3s, IQView) must use the same UDP port.
Note that by default all 3xtend/EINC Ls, IQ3s, and IQViews use the same UDP port (57612).
Note that IQ3 a and IQ3 b are on the same Lan 20 on one site. EINC c Lan 20 is on a separate site. Having separate
sites enables the Lan number to be duplicated.
UDP xxxxx UDP yyyyy
Lan 20 Lan 20
EINC EINC
Lan 20 Lan 21
Ethernet
Same Subnet
As can be seen from the diagram below, the above diagram is equivalent to two independent sites. This has been achieved
without using a router.
Site 1 Site 2
UDP xxxxx UDP yyyyy
Ethernet
Lan 20 Internetwork
By using two UDP port numbers site 1 consists of Lan 20 with two IQ3s, and Site 2 consists of an internetwork with two
EINCs.
In section 3.3.2 above it was stated that Trend Ethernet system devices on the same network segment should all be on
the same subnet. However, if devices have different UDP ports they can be on the same segment but on different subnets;
the different subnets will now be different sites in a similar way to that shown in the diagram above.
3.3.13 FTP
FTP (File Transfer Protocol) is used to transfer files across Ethernet. It uses TCP/IP, (i.e. FTP/TCP/IP) and is used on
the IQ system by SET to transfer strategy files to and from IQ3s (amongst other things).
This is why SET must be connected to the same Ethernet network as the IQ system site for strategy file upload download.
Single IQ3/LAN: The internal Lan for a single IQ3 as described in 3.3.2 above remains virtually unchanged.
Supervisor/ A B Web
Tool Browser
alarms
by C Local Supervisor/
TCP/IP Tool
TCP/IP TCP/IP
IQ3/LAN
RS232
IQ3
control
vCNC CNC sCNC
The network schematic shown above is almost the same except that the INC has been removed. The IQ3/LAN is unable
to perform INC functions on the current loop Lan, (i.e. it cannot sit on the internetwork).
The other features remain: a supervisor or tool (A) can communicate by TCP/IP using the vCNC , a web browser (B) can
directly access the IQ3 using TCP/IP, and a supervisor or tool can communicate using the local supervisor RS232 port
(sCNC).
IQ3/LAN on the Lan: Once another IQ (IQ1, IQ2, or IQ3) is connected to the current loop, the two IQs form a Lan. This
can then be extended onto an internetwork in the normal way using an INC type node (e.g. INC2, LINC, 3xtend/EINC
L). It is important the Lan number of the IQ3 matches that of any INC type device, or TMN (ANC) on the local Lan.
Supervisor/ A B
Web
Tool Browser
C Local Supervisor/
TCP/IP Tool
TCP/IP
IQ3/LAN IQ IQ IQ
RS232
IQ3
control
vCNC CNC sCNC
Lan x
INC
Internetwork
INC INC
Lan y
Lan z
The above system shows an IQ3/LAN connected to a current loop Lan consisting of 3 other IQs and an INC. The INC
extends the network to two other Lans by way of the internetwork.
If a 3xtend/EINC L is used instead of an INC, then the internetwork (or a segment of it) can exist on Ethernet. This would
enable Ethernet Lans of IQ3s to be part of the same system network as an IQ3/LAN.
The 3xtend/EINC L also has a LonWorks bus connection enabling the internetwork to also be present on the LonWorks
bus, and hence connect to LonWorks Lans of IQLs
The diagram below shows a 3xtend/EINC L being used to connect the current loop Lan to an Ethernet internetwork. An
Ethernet Lan of IQ3s is also connected to the internetwork by an IQ3’s vINC.
Supervisor/ A B
Web
Tool Browser
C Local Supervisor/
TCP/IP Tool
TCP/IP
IQ3/LAN IQ IQ IQ
RS232
IQ3
control
vCNC CNC sCNC
Lan x
Current loop
3xtend/
EINC L
Internetwork Internetwork
Ethernet Lon
vINC (if required)
IQ3
Lan y
Ethernet
IQ3 IQ3
3.7 BACnet
Theoretically this should be in the Ethernet section (3.3) above, because IQ3/BAC is capable of BACnet IP (i.e. BACnet
communications using IP addressing on Ethernet), but BACnet really refers to the protocol rather than the medium. The
IQ3 controller has been BTL approved as a BACnet Application Specific Controller (B-ASC) - see 3.7.1 below.
All versions of IQ3 can be purchased with or without BACnet interoperability; the IQ3 with BACnet is referred to as IQ3/
BAC in this manual.
The Network module 3 (BACnet) is enabled by default (by SET) but can be changed in SET or on the web page. It must
be enabled for any of the BACnet communications to operate. The other additional modules and types listed above can
be configured in SET, but will not be operational until the Network module is enabled and correctly configured. Its default
configuration will enable satisfactory operation in most cases (see Pt. 2 section 20.3.4).
The Notification Class object is to do with alarm delivery, and has a Recipient List (list of alarm destinations) in which
each recipient maps to time zone, alarm route, and alarm destination modules.
The mapping of the BACnet properties to the Trend parameters is covered in the lists in section 3.7.2 below.
Each BACnet device supports a number of BIBBs (BACnet Interoperability Building Blocks) which are split into five
areas of interoperability:
data sharing (reading and writing of data including IC Comms)
alarm and event management (alarm generation and alarm log)
scheduling (time zones)
trending (logging/plotting -not supported in IQ3 v2.0)
device and network management (Network building, time synchronisation)
BIBBs generally come in pairs, designated A and B, that reflect the client/server nature of control system communication.
The ‘A’ BIBB represents the client or device that is trying to obtain information or command an action. The ‘B’ BIBB
represents the server or device that provides the data or carries out the commanded action.
If two devices support the complementary BACnet capabilities (the A and B side of the same BIBB), then they are
interoperable from the standpoint of that service.
ID BIBB Title
1.1 DS-RP-A Data Sharing-ReadProperty-A
1.2 DS-RP-B Data Sharing-ReadProperty-B
1.4 DS-RPM-B Data Sharing ReadPropertyMultiple-B
1.7 DS-WP-A Data Sharing-WriteProperty-A
1.8 DS-WP-B Data Sharing-WriteProperty-B
1.10 DS-WPM-B Data Sharing-WritePropertyMultiple-B
1.12 DS-COV-B Data Sharing-ChangeOfValue-B
2.2 AE-N-I-B Alarm and Event-Notification Internal-B
2.11 AE-INFO-B Alarm and Event-Information-B
4.2 T-VMT-I-B Trending-View ing and Modifying Trends Internal- B
4.5 T-ATR-B Trending_Automated Trend Retrieval-B
5.1 DM-DDB-A Device Management-Dynamic Device Binding-A
5.2 DM-DDB-B Device Management-Dynamic Device Binding-B
5.4 DM-DOB-B Device Management-Dynamic Object Binding-B
5.6 DM-DCC-B Device Management-DeviceCommunicationControl-B
5.12 DM-TS-B Device Management-TimeSynchronisation-B
5.14 DM-UTC-B Device Management-UTCTimeSynchronisation-B
Addendum L
3.4 SCH-R-B Scheduling Readable B
The IQ3 controller has been BTL approved as a BACnet Application Specific Controller (B-ASC) because it complies
with all the BIBBS required, but it supports more than this, and on a practical system can be treated as a BACnet Advanced
Application Controller (B-AAC).
The following sections list the BACnet properties supported in the IQ3:
The BACnet analogue input object supports COV and intrinsic reporting.
The BACnet binary input object supports COV and intrinsic reporting.
The BACnet analogue output object supports COV reporting but not intrinsic reporting.
The BACnet binary output object supports COV and intrinsic reporting.
The BACnet analogue value object supports COV reporting but not intrinsic reporting.
The BACnet binary value object supports COV reporting but not intrinsic reporting.
BP_RECIPIENT_LIST BT_LIST of R/W Each element in this list maps to an instance of Trend Destination module
BT_DESTINATION routed to from the Trend Group module (a direct mapping from the
notification class instance).
Write: the order of BACnet Recipients are taken to be the same as the
order of Trend Routes attached to the Trend Group.
BACnet Recipient
validDays BACnetDaysOfW- If a Time Zone is not used the Route, Enable on(E) dictates occupation:
eek If on(E) is 1, validDays are MTWTFSS, and from Time is 0:00, and to Time
is 23:59:59. The Enable must not be connected.
If on(E) is 0, validDays are nul, and from Time and to Time are 0:00.
If a Time Zone is connected to the Route Enable, the Time Zone must have
no Exceptions, for the days which are occupied, their on/off times must be
the same, there can only be one occupation period, (i.e 1 on time, 1 off
from Time Time time) and the Time Zone must not be connected to any other module.
The validDays are defined by those with occupation in the normal week.
The 'from Time' is the first occupied day's on Wn(P1(T)), and the 'to Time' is
the first occupied day's off time Wn(P2(T))
Note that a time of 24:00 is sent on BACnet as 23:59:59.
Write:
to Time Time If the Time Zone is not used, the occupation can only be set to either 7 days
no occupation or 7 days 24 hour occupation. This will set the Route, Enable
on(E) either to either 1 or 0.
For any other occupation profile the time zone must be connected. A 23:59
time will be set to 24:00. A To time of 0.00 will be set to 24:00
recipient BACnetRecipient Alarm Destination Module, Device Instance, en(D)
process Identifier Unsigned32 Alarm Destination Module, Process ID, en(R)
IssConfirmedNotifications BOOLEAN Inverse of Alarm Destination Module, Service Type, en(T)
transitions BACnetEventTran- Alarm Destination Module, Transitions en(R)
sitionBits Defines change in state that will generate alarms.
Three bit digital bit string:
Bit 2=to normal (clear alarms)
Bit 1=to fault
Bit 0=to offnormal
Note that the IQ3 BACnet schedule object is only compliant with the BACnet standard if the network module BTL
Compliance parameter is set to 1. This will prevent BACnet writes to the schedule module. BACnet writes to the schedule
module are not BTL compliant because:
1 Writes to individual array elements are not supported. Weekly Schedule, and Exception Schedule arrays can only be
written to as complete arrays; individual elements cannot be written to.
2 Day of week specifications (e.g. every thursday) are not supported.
Alerton BACnet
device
IQ3/BACs on BACnet
The BACnet IC Comms uses Trend Addressing to define its destination which is in fact a BACnet device. In order to
achieve this a Non-Trend Device module (NTD) has to be set up which will substitute a BACnet device address for the
Trend address.
Note that the BACnet Lan in the Device View is a Trend BACnet Lan using Trend addressing (Lan number and local
address) unlike the true BACnet network in the System View which uses BACnet Addressing (BACnet network and
device instance). A Trend BACnet Lan does not connect to the internetwork, however the Lan number must be unique.
The destination BACnet device has to be discovered by browsing the BACnet network so that it appears in the System
View. Its icon, , can then be dragged over and placed on the Trend BACnet Lan in the Device View. A node number
will be requested which is the Trend local address on the Trend BACnet Lan. Dragging the device across in this way
populates the NTD module with most of its parameters (see Pt. 2 section 21.3.1)
It is also possible to drag a whole BACnet network, across to create several NTD modules on a Trend BACnet Lan.
The NTD module can also be set up manually (see Pt. 2 section 21.3.1.
As mentioned above, an IQ3/BAC is able to be viewed both as a Trend device, and as a BACnet device because IQ3/
BAC performs both Trend and BACnet comms. Because of this, it is possible to send BACnet IC Comms between IQ3/
BACs. This is not recommended as a permanent installation, but it can be useful to prove that the BACnet IC Comms
setup works correctly (e.g. using web pages the change of values can be monitored in each IQ3).
It is also possible to send a BACnet IC Comms from an IQ3/BAC to itself; again this would not be for permanent installation
but as a method of practising setting up BACnet IC Comms.
The Device Instance is unique on the system and can be used like a hostname in that its IP address can be resolved (by
certain BACnet devices, see below).
The BACnet Address is a function of its IP address; it consists of BACnet Network Number and BACnet MAC address,
and the BACnet MAC address consists of IP address and UDP port.
If the IQ3 is set up for DHCP the Device Instance will not change, but from time to time its BACnet Address will (due
to change in IP address).
The IQ3 BACnet Alarm Destination module and the NTD module both have alternative methods of selecting the
recipient’s address, either by Device Instance, or by Network Number and MAC Address (i.e. BACnet Address). It is
generally recommended that the Device Instance be used as preference. If the remote devices use automatic IP
addressing, the Device Instance addressing must be used. Certain BACnet devices are unable to support Device
Instance addressing and so must have static IP addresses.
Remote devices in the BACnet system communicating with the IQ3 which have to be explicitly configured with the MAC
Address of the device they are communicating with (Static Device Binding) will no longer communicate with the IQ3 if
its IP address changes due to DHCP operation until their configuration is changed. In this case the IQ3 would have to
have fixed IP addressing (see section 3.3.11.8 above).
Remote devices in the BACnet system communicating with the IQ3 which resolve the BACnet MAC address at run-time
(Dynamic Device Binding) will be able to resolve the change in MAC address, but may themselves take a while to detect
that the address has changed (this time depends on the local algorithm used in the device for responding to failed
communication).
In short, if there are devices which only support static device binding in the BACnet system, or devices with unacceptable
delays in detecting MAC address changes then the IQ3’s must be set up with static IP addresses in order to ensure reliable
communications are maintained.
The IQ3 has COV reporting capabilty on its Analogue and Binary Inputs, Outputs, and Values (i.e. AI, BI, AO, BO, AV,
BV). The objects with analogue values each have a COV increment property so that the report is given when the change
in value since the last report exceeds the COV increment. For binary properties the report is sent on a change of state.
The COV report is not sent as a Trend alarm, and does not appear in the alarm log.
The Trend Item Type alarms have corresponding Clear alarms but the actual coresponding BACnet events are dependent
on the return path through the Trend alarm states as decribed in Pt.1 section 12.7.4.2.
BACnet Network Module: As explained above the for BACnet communications to operate the BACnet network module
must be enabled and correctly configured.
BTL Compliance Parameter: The BACnet network module, BTL Compliance parameter must be enabled for compliance;
this will disable BACnet writes to the schedule object as they are non-compliant.
Alarms over BACnet: The best way to ensure compliance is to use the SET BACnet Alarm Block which contains one
each of Trend Alarm Group, Alarm Route, Alarm Destination (type BACnet device), and Time Zone modules. The time
zone is optional; it is not required if the alarm is to be sent all day, seven days a week (see rule 4 below). Modifying the
alarm block may make the strategy non-compliant. It is possible to edit the times providing there is only one on/off period
in each day and the days are all the same, although any day may be off all day. Exceptions must not be applied to the
time zone. Only one alarm route module can be connected to the destination module, and the alarm route can only be
connected to a single time zone.
Plot module: Only the Periodic plot module is compliant, so there can be no synchronised or triggered plots. The Enable
input must be left unconnected so that it can be written to by BACnet and by the module itself (see StopWhen Full, Pt.
2 section 25.5).
Digital driver module with logic readback module: Any alarm delay must be implemented in the driver module (driver
Readback Alarm Delay), not in the logic readback module (logic Grace Time must be zero).
XCITE/TERM
main controller I/O Module
This photograph shows a single I/O module connected to the main controller using an XCITE/IC. The I/O bus is
terminated by an XCITE/TERM fitted in the I/O module.
I/O bus
connector
cover
DIN rail
clip
LED
indicators
100-240 V THIS UNIT
MUST BE
A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
24 V
24 V
EARTHED OK RX P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
Note that the auxiliary cover is also removed to replace the battery backup board lithium cell.
a
b
c
d
a b
Note that the auxiliary cover is removed to insert or replace the battery backup lithium cell.
This connector is not fitted to IQ3xact. IQ3xcites are supplied with an I/O bus terminator (XCITE/TERMINATOR)
fitted to the connector. This is used on IQ3XCITE/96 for connecting I/O modules.
terminator fitted to
IQ3xcite
If an I/O module is to be connected, the terminator has to be removed before fitting an I/O bus connector (e.g. XCITE/
INTERCONNECTOR). The flap can be pressed back into place after plugging in the interconnector.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
1 2 3 4 5 6 7 8 9 10 +
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
+ 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0
100-240 V A 11 12 13 14 15 16 100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P P 0 P 0 P 0 P 0 P 0 P 0 100-240 V A 11 12 13 14 15 16
0 P 0 P 0 P 0 P 0 P 0 P
OK RX 0
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
This exposes the input channel links and the input channel screen earth link (see 4.2.10 below). The cover is replaced
by pressing it back into place along the side edges.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
4.2.4 DIN Rail Fixings
The IQ3 is designed to be mounted on a DIN rail in a panel. It should be mounted the correct way up on a horizontal DIN
rail, not on its back or upside down. It can be mounted sideways on a vertical DIN rail if DIN rail end stops are fitted to
stop the IQ3 from slipping off the rail.
not on its back
mount sideways
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
100-240 V
1
1
2
3
0
+
4
2
5
6
0
7
3
8
9
0
10 11 12
+
4
0
13 14 15 16 17 18
+
RX
5
0
OK
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 P
0V
24 V
24 V
RX OK
24 V P 0 P 0 P 0 P 0 P 0 P 0
6
16 15 14 13 12 11 A 100-240 V
0V
A
24 V
P
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
P
19 20 21 22 23 24
A 11 12 13 14 15 16
+
100-240 V
0 P 0 P
11
P 0 P 0 P 0 P 0
7
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
0 P
0
+
12
8
0 P
0
13
25 26 27 28 29 30
0 P
+
9
14
0
0 P
+
10
15
0
0 P
0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 +
10 9 8 7 6 5 4 3 2 1
25 26 27 28 29 30 19 20 21 22 23 24 13 14 15 16 17 18 10 11 12 9 8 7 6 5 4 3 2 1
The IQ3 is mounted on the DIN rail by tilting the unit, hooking the upper hooked edge over the upper edge of the DIN
rail, pulling on the clip, and lowering the clip on the DIN rail, and releasing the clip.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
24 V
EARTHED OK RX P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
Ethernet LEDs
Power ( ): (green) ON when supply is connected. Flashes briefly at 1 second intervals if power supply fault;
return unit to supplier.
I/O bus error ( ): (red, not fitted on IQ3xact) ON if there is an I/O bus fault, (e.g. check for short circuit
between Data Hi or Data Lo and either of the power lines).
Input channel set: Each input channel has a yellow LED to monitor the input state when the input channel is set to a
digital input. The LED will illuminate when the associated input contact is closed.
Output channel set: Each output channel has a yellow LED to monitor the output state. The light intensity increases
with output voltage.
Ethernet LEDs: There are two Ethernet LEDs, OK and RX, fitted in the Ethernet socket.
OK (green) Rx (yellow)
OK: (green) Normally called LINK on Ethernet systems. ON indicates a good Ethernet connection. If OFF indicates faulty
Ethernet connection.
RX: (yellow) Flashes when packet of data is being received across the Ethernet.
4.2.6 Connectors
Two part connectors are used for the input power supply, auxiliary output supply, input and output channels, and for
the I/O bus. Input channel screens are only single part connectors. Special connectors are used for RS232 and Ethernet.
single part,
input channels screen terminals
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
100-240 V T H IS U N IT
M U S T B E
A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
E A R T H E D OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
The IQ3 variants have different numbers of I/O channels as listed in the table below:
Input Channels: There are up to 10 universal input channels numbered 1 to 10, left to right on the IQ3. Each channel
has 3 terminals labelled + (+24 Vdc from the IQ3), N (the input channel number - signal input), 0 (0 v in the IQ3). Also
associated with the input channel is a screen terminal (single part connector) which is connected to an internal screen
bus. See section 4.2.10 below for input connections.
Output channels: There are up to 6 analogue output channels on the IQ3 numbered 11 to 16. Each channel has a 3
terminals labelled P (the connection from the internal 24 V power bus), N (the output channel number - signal output,
0 to 10V), 0 (0 V in the IQ3). There is a facility to connect the internal power bus either from the IQ3 internal 24 Vdc
supply or from an external 24 Vac/dc supply. See section 4.2.11 below for output connections.
Note that for a /24V unit to comply with its UL rating, the input supply should be limited to 36 V maximum.
Auxiliary output supply: This consists of 2 off 2 wide connectors labelled ‘A’ for connection of the auxiliary output
supply, and for connection of supply to the power bus.
The auxiliary output supply has 2 terminals labelled 24V (24 Vdc from the IQ3) and 0V (0 V on the IQ3)
The other 2 terminals are for sourcing the output channel internal power bus either from the IQ3 auxiliary output supply
or from an external 24 Vac/dc supply; they are labelled 24V (24 Vdc from the IQ3), and P (input to internal power bus).
The power bus is normally supplied from the IQ3, 24 Vdc auxiliary output supply by fitting an external link between
the 24V and P terminals.
A
A 11
P 0
24 V
24 V P 31 32 33
0V
RS232 Local Supervisor Connector : This RJ11 (FCC68) socket is for connection of a local supervisor type device
or display (e.g. IQView, SDU-XCITE, RD-IQ, XW/R/IQ) or a local PC running supervisor or tool software (e.g.
915MDS, 916, 963 or SET). Only 1 device may be connected.
This port can communicate directly with the local IQ3 (address module local supervisor port address =0) or to the network
via an internal sCNC connection (local supervisor port address is greater than 0).
Ethernet Connector : This RJ45 socket is for connection to Ethernet. The IQ3 connector is for unshielded or shielded
twisted pair (UTP or FTP) cable 10 Mbps, 10 BASE-T. The IQ3 can connect to Ethernet via an adjacent hub. A local PC
(e.g. using 963, SET or IQView) can make a direct connection via the Ethernet connector using a standard Ethernet cable
and an Ethernet crossover adaptor XCITE/XA.
RJ45 RJ45
XCITE/XA crossover adaptors
(order separately)
standard Ethernet cable
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
/100-240
This requires 100 to 240 Vac ±10 %, 50/60 Hz, at 46 VA max. A 240 Vac 3 A switch or circuit breaker must be included
in the supply to the unit, and be in close proximity to it, and must be clearly marked as the disconnecting device for the
unit. 100-240 V
L N E
/24
This requires 24 to 60 Vdc (36 Vdc maximum for UL compliance), or 24 Vac at 50/60 Hz, at 40 VA max.
24-30 V
24 V
E 24 Vac
+24V 0V E 24 to 30 Vdc
Earthing
The IQ3 must be earthed via its power connector terminal. Both supply input terminals are isolated from earth.
The DIN rail must also be earthed.
The minimum power is for the core electronics without any I/O auxiliary power or additional I/O modules. The maximum
power for the IQ3xcite/000 includes core electronics and maximum auxiliary supply consumption, for the IQ3xact/012 and
IQ3xcite/016 it also includes maximum I/O consumption; the maximum for the IQ3xcite/96 and /128 includes core
electronics, maximum I/O consumption, and maximum auxiliary supply of 700 mA (which includes power to the I/O bus).
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
Standard Ethernet cable RJ45
100 m (max)
Cat 5e twisted pair
RJ45
Ethernet hub
The Ethernet connector is for unshielded (UTP) or shielded (FTP) twisted pair cable 10 Mbps, 10 BASE-T. A standard
cable can be up to 100 m and has an RJ45 plug at each end. The IQ3 will normally be connected to an Ethernet hub by
the standard cable.
A local PC (e.g. using 963, SET) or IQView can be connected to an adjacent Ethernet hub port using the standard cable,
or it can connect directly to the IQ3 using a standard cable in conjunction with the crossover adaptor XCITE/XA.
RJ45 RJ45
XCITE/XA crossover adaptor
standard Ethernet cable
Note if SET is connected directly using Ethernet, all its features are available.
The IQ system supplier can provide the crossover adaptor as XCITE/XA/5 (pack of 5 crossover adaptors).
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
As described in Pt. 1 Section 3.2, the RS232 port can either be connected solely to the IQ3 (by setting the supervisor
port address in the configuration address module to zero), or can be connected to the internal Lan via an sCNC (by setting
the supervisor port address to be greater than zero).
XW/R/IQ
IQView XW/R/IQ
SDU-XCITE IQView
RD-IQ Local Supervisor/Tool
Local Supervisor/Tool RS232 RS232
IQ3 IQ3
IQ3 IQ3
control control
CNC CNC sCNC
For the SDU-XCITE and RD-IQ the supervisor port address must be set to zero. These displays cannot communicate
via the network.
For IQView, XW/R/IQ, and local PC running a supervisor or tool, the supervisor port address can either be zero for local
IQ3 communications only, or greater than zero for communications via the network.
The IQView is a touch screen display with either surface mount or rear panel mount options and with either a colour or
mono screen.
In addition to its RS232 connector described above it can connect directly to an IQ system current loop Lan (via
its internal CNC), or it can connect via Ethernet either via its internal vCNC or via an external vCNC (see Pt. 1 Section
3.3.10).
As long as the IQView is connected via a CNC it can view all controllers on local or remote networks (not autodialled)
and can display all inputs, outputs, directories, alarms and logs (IQView can view synchronised plots only) and
facilitate adjustment of knobs, switches, time zones and time.
The IQView Mono version only has RS232 connectivity, the IQView (standard) version also has Ethernet and IQ
system current loop Lan connectivity.
IQView connects to the RS232 port via an RJ11 to RJ11 connector cable CABLE/EJ105650.
IQView
100-240 V THIS UNIT
MUST BE
EARTHED OK RX
RJ11 RJ11
It connects to the IQ3 via its RS232 port and communicates solely with that IQ3 (not the network). There are versions
of SDU for IQ2xx controllers (SDU-IQ) and IQL controllers (SDU-LON). The SDU can display all inputs, outputs,
directories, and alarms, and can facilitate adjustment of knobs, switches, time zones and time.
The RD-IQ (Room Display) is a wall mounted temperature sensor and 3 digit display.
It connects to the IQ3 via its RS232 port and communicates solely with that IQ3 (not the network). The RD-IQ
operates with IQ3, IQ2xx and some IQ1xx controllers; there is another version of RD, RD-IQL which operates with
IQL controllers.
The RD-IQ has the following variants:
RD-IQ/K: Room display with local temperature sensor and setpoint control.
RD-IQ/KOS: As RD-IQ/K plus occupation override and occupation status display.
RD-IQ/KOSF: As RD-IQ/KOS plus fan speed control.
By default it accesses fixed strategy items (although these can be changed using the front panel buttons):
Local temperature S9
Setpoint K1
Occupation status K6
Fan speed status K7
RD-IQ, and SDU-XCITE connect to the RS232 port via an RJ11 to RJ11 cable RD/SDU-IQ2 COMMSCABLE/3M
(3 m cable) or RD/SDU-IQ2 COMMSCABLE/10M (10 m cable).
The XW/R/IQ wireless sensor receiver enables up to 32 wireless sensors to send their values and status to nominated
analogue nodes within the IQ3; these nodes have to be created in SET.
It can be connected to the RS232 port and (like the IQView) can communicate either with the local IQ3 only, or to
the network via the IQ3’s sCNC.
RJ11
RD/SDU-IQ2 COMMSCABLE/3M (3 m)
RD/SDU-IQ2 COMMSCABLE/10M (10 m)
A local PC running a supervisor or tool can be connected to the RS232 port and (like the IQView) can communicate either
to the local IQ3 only, or (to the network) via the IQ3’s sCNC.
Browser access to IQ3 web pages is not possible via the RS232 port.
The 915MDS and 916 Supervisors are fully compatible.
The 963 Supervisor is fully compatible other than its access to web pages via a browser.
Note that SET is able to upload or download the strategy file by way of the RS232 port but not the other
configuration files: language, backdrop, and XNC (for IQ3/XNC versions only). SET is able to perform Live Edit,
Live Values, and Mapping via the RS232 port.
A PC connects to the RS232 port via RJ11 to 9 way ‘D type’ female cable CABLE/EJ101442.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
IQ3xact
IQ3xcite
There are 10 universal input channels numbered 1 to 10, left to right on the IQ3xcite. The IQ3xact has only channels 1
to 6.
5V 5V
yellow
10K
100K
V
1K
external earth link
T
internal 240R
I
D
internal screen + +24 Vdc
108K
bus (in) N
0
0V 0V
Each channel has 3 terminals labelled + (+24 Vdc from the IQ3), N (the input channel number - signal input), 0 (0 V from
the IQ3). Also associated with the input channel is a screen terminal (single part connector) which is connected to an
internal screen bus. Each 24 V supply terminal is limited to 22 mA.
The input terminal size is for 0.5 and 2.5 mm2 cross section area or 14 to 20 AWG cable (Cu only).
TP/1/1/22/HF/200 cable (Belden 8761 equivalent) is recommended for wiring inputs and is available from an IQ
system supplier.
screen
earth link linking pins
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
The linking pins can be seen below the associated input channel connector. The link should be moved to the appropriate
position.
The input channel screen terminals are connected to the internal screen bus which is normally connected to the internal
(mains) earth. If it is required to segregate the screen earthing, the screen earth link should be cut and the ‘spare’ screw
terminal connected to earth externally.
separate
earth
connection
1 2 3 4 5 6
+
1 0 +
2 0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
There are 6 analogue voltage output channels numbered 11 to 16 left to right in all IQ3s.
24V
24V 24V (Aux)
external link (not supplied)
P
P
22R 330R internal power
yellow
(out) N bus
0
100K
0V
100K 3K3
0V 0V
Each channel has 3 terminals labelled P (the connection from the internal power bus), N (the output channel number -
signal output, 0 to 10 V), 0 (0 V in the IQ3).
I<=20 mA
(0 V)
0 (0 to 10 Vdc, <=20 mA)
N (out) N (+24 V)
LOAD
P optional
The output terminal size is for 0.5 to 2.5 mm2 cross section area, or 14 to 20 AWG cable (Cu only).
TP/1/1/22/HF/200 cable (Belden 8761 equivalent) is recommended for wiring outputs and is available from an IQ
system supplier.
The output channels power bus is normally connected to the IQ3’s 24 Vdc auxiliary output supply via an external link
(not supplied) as shown below.
output channels
power bus A
A
P
11
0
24 V
24 V
0V P 31 32 33
External link
(not supplied)
If it is required to supply power to the power bus via an external power supply unit it should be connected to the P bus
input terminal.
A
A 11
P 0
24 V
24 V
P 31 32 33
0V
PSU
External power supply
(24 Vac/Vdc)
Note that the current in the internal power bus is limited to 1.6 A by a self resetting multifuse.
Note that if an external 24 Vac/dc power supply is used, it must be dedicated to I/O channel use, and it must comply
with the relevant EMC and safety standards.
The external supply can be either 24 Vac or 24 Vdc, but if the output devices require a mix of 24 Vac and 24 Vdc a
decision will have to be made over which supply to connect to the P bus; the other supply will need to be provided by
external wiring.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0
22 mA
max/
circuit breaker channel
1.6 A
150 mA max.
max. 500 mA
PSU 700 mA
(550 mA) max.
max. 22 mA
max/
channel
A
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
24 V
24 V
OK RX P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
RS232
auxiliary supply power bus (P bus)
output channels
24V 0V return
external link (not supplied)
power bus input
The P output terminals are used to supply the power to output devices. The internal power bus (P bus) is protected by
a 1.6 A self-resetting multifuse. As explained above, the power bus input terminal is normally supplied from the IQ3 24
Vdc auxiliary output supply by using an external link (not supplied), but it can be supplied from an external dedicated
isolated 24 Vac/dc power supply.
Note that the installer should note whether the P bus is 24 Vac, or 24 Vdc and only connect the appropriate loads.
The diagram below shows the way in which the IQ3’s 24 Vdc combined supply is distributed.
24 Vdc Combined Supply Input/Output Channels
700 mA (550 mA) maximum I/O Bus
Inputs T, V, D, I 0 mA
Example:
An IQ3XCITE/96 with an XCITE/IO/4UI/4AO I/O module, SDU-xcite, and its own I/O as follows: 4 loop powered
current inputs, 4 voltage inputs, 2 digital inputs, and 4 voltage outputs into 5 k loads, 2 voltage outputs into 1 k loads.
The P bus is linked to the 24 V auxiliary output supply and one of the P terminals supplies a 6RM at 86 mA The I/O
module consumes 72 mA. What remaining auxiliary current is available?
I/O Channels
4 loop powered current inputs at 20 mA = 80 mA
4 voltage inputs = 0 mA
2 digital inputs = 0 mA
4 voltage outputs at (5 k is 2 mA) = 8 mA
4 voltage outputs at (1 k is 10 mA) = 40 mA
I/O bus module consumption = 72 mA
RS232SDU-xcite = 15 mA
AUX output supply (linked to P bus) = 86 mA
Total = 301 mA
Since the unit is supplied at 230 Vac, the maximum 24 Vdc auxiliary current available is 700 mA. So remaining current
available is 700-301 = 399 mA. This could be used by additional I/O modules.
If this were not sufficient an additional power supply could be used to supply the I/O modules (see I/O bus section below).
However, RS232/auxiliary output supply consumption amounts to 101 mA (15+86); this is limited at 150 mA, so only
49 mA remains available from the 24 Vdc auxiliary output supply terminals. If this is not sufficient an additional power
supply could be used to supply the P bus as described above, releasing another 101 mA for use by the 24 V auxiliary
output supply.
service button
100-240 V A 11 12 13 14 15 16
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
0V
Flash Memory
Flash memory holds the application and all of the data files (strategy, back drops, language file). Changes made (e.g.
via web pages or text comms from supervisors) are written to Flash 15 seconds after the change.
In the case of power failure, changes made within the last 15 seconds could be lost.
Flash memory possesses a limited number of writes; the normal life of the memory within the IQ3 is a minimum of 10 years.
If a timemaster is not installed the IQ3 can be resynchronised using web pages. This will involve setting up time (hrs,
mins, secs), date (day, month, year), and day of week.
The battery can be provided by a battery backup auxiliary board (XCITE/BBC), or by fitting a battery to the current loop
Lan auxiliary board (fitted to IQ3/../LAN) or to the serial interface auxiliary board (fitted to IQ3/XNC/SER).
Note that the system can only have one time master so an IQ3 timemaster must also synchronise any IQ1s, IQ2s or IQLs.
CR 2032
The auxiliary board cover is replaced (see 4.2.1 above) The I/O can be reconnected, and IQ3 power restored.
The battery should be replaced if it discharges due to supporting the RTC during power failure, or routinely every 5 years.
The battery replacement mirrors the battery board installation (except that the board is already plugged in).
Note that battery backup may also be provided by fitting a battery to the current loop auxiliary board (fitted to IQ3/../
LAN, see 4.4 below) or to the serial auxiliary board (fitted to IQ3/XNC/SER, see 4.5 below).
1 2 3 4 5 6 7 8 9 10 11 12
upper I/O terminals
+ 1 0 + 2 0 + 3 0 + 4 0
DIN rail
LED indicators upper channel cover hook
I/O bus
I/O bus connector
connector cover
cover DIN rail
clip
LED indicators
The main features of an I/O module are similar to those of the IQ3, however the I/O terminals are protected by clear
polycarbonate flip up safety covers.
Upper and lower channel covers: These are similar to the input channel links cover of the IQ3 main controller. They
are removed and replaced in the same way.
I/O bus connector cover: The I/O module has 2 flip up I/O bus connector covers similar to the one on the IQ3 main
controller, enabling daisy chaining of the I/O bus by the I/O modules.
DIN rail fixings: Similar to the main controller only the I/O modules are the same height but about half the width (width
main controller: 263 mm , I/O module 120 mm).
The other main features are covered in the sections that follow.
16 Channels
address switch
flip up cover
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
flip up cover
16 Digital Inputs 8 Digital Inputs, 8 Thermistor Inputs
XCITE/IO/16DI XCITE/IO/8DI/8TI
(yellow)
1 2 3 4 5 6 7 8 + 1 0 + 2 0 + 3 0 + 4 0
5 6 7 8
screen earth link
+ 0 + 0 + 0 + 0
5 6 7 8
digital input LEDs 13 14 15 16 17 18 19 20 21 22 23 24
(yellow)
8 Digital Inputs 8 Universal Inputs
XCITE/IO/8DI XCITE/IO/8UI
(yellow)
24 V
+ 1 0 + 2 0 + 3 0 + 4 0 P 0 P 0 P 0 P 0
1 2 3 4
output LEDs 1 2 3 4
(yellow)
1 2 3 4
input links
4UI/4AO Excess Aux. 8AO
Current LEDs
(red)
5 6 7 8
output LEDs (yellow) 5 6 7 8
P 5 0 P 6 0 P 7 0 P 8 0
P 5 0 P 6 0 P 7 0 P 8 0
24 V
P 13 14 15 16 17 18 19 20 21 22 23 24
24 V
P 13 14 15 16 17 18 19 20 21 22 23 24
1
NC
2 3
C NC
4 5 6
C NC
7 8 9
C
10
NC
11 12
C
output status LEDs 1 2 3 4 5 6 7 8 9 10 11 12
1 2 3 4
(yellow)
NC C NC C NC C NC C
1 2 3 4
H
A
O
1 2 3 4 override LEDs
(red)
8DO 8DO
Hand, Off, Auto
switches
H
5 6 7 8 A
O
H
A
O
(yellow)
(yellow)
P 0 P 0 P 0 P 0 + 0 + 0
1 2 3 4
P 13 14 15 16 17 18
XCITE/IO/4AO
2 Universal Inputs, 2 Analogue Outputs
XCITE/IO/2UI/2AO
1 2 3 4 5 6 7 8 9 10 11 12
NC
1
C NC
2
C NC
3
C NC
4
C
output status LEDs (yellow)
H
A
O
override LEDs (red)
Note that some channel numbers are non-sequential. e.g. 2UI/2AO has channels 1, 2, and 5, 6 (gap of 3, 4 unused). This
enables a 4 channel unit to be changed for an 8 channel without changing channel numbers (e.g. upgrade 2UI/2AO to
4UI/4AO).
Each module has an address switch to define its address on the I/O bus. There are 3 LED indicators similar to the main
controller status set.
Universal Inputs
1 2 3 4 5 6 7 8 9 10 11 12
+ 1 0 + 2 0 + 3 0 + 4 0
input links
The Universal Input channels are similar to those of the main controller with D, I, T, V input links and a screened earth
link. There is a separate screen earth link for each group of four channels (i.e. the 8 universal input module has two links).
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 2 3 4 5 6 7 8
2.5 mA yellow
100K
red inverse 0V 0V
polarity
detection
0V
The input will be on when the input LED (yellow) is ON, and this is when the contact closes or AC voltage is applied.
This corresponds to an open collector input or logic input sinking current from the terminal.
There is an Input Polarity Error LED for each bank of 8 inputs. This LED (red) is ON if one (or more) of the digital
inputs are supplied by an ac voltage, which has been grounded on the wrong side with respect to the IQ3’s ground.
The volt free contact input has a nominal wetting current of 2.5 mA. The digital input is ON when the contact
is closed.
N
0 V
This can be an open collector or an open drain (FET) input. The collector or drain must be able to sink 3 mA.
When the transistor or FET conducts, the digital input will be ON.
Logic Input
e .g .
T T L
C M O S
3 m A N
0 V
The logic high level can be between 5 and 50 V (e.g. TTL, CMOS). The logic low level must be able to sink
3 mA. Note that the digital input will be ON when the logic input is low.
24 Vac Input
24 Vac ±20%
Load N
This type of digital input can monitor the state of a 24 Vac input. In this example it will be ON when the load
(e.g. a fan) is powered.
screen terminals
5V
10K
100K
(in) N
100nF
0
0V
Analogue Outputs
output LEDs
P 5 0 P 6 0 P 7 0 P 8 0
24 V
P 13 14 15 16 17 18 19 20 21 22 23 24
The 0 to 10 V Analogue Output channels are also similar to those of the main controller with output channel LEDs, and
a power bus input terminal. The power bus is normally supplied for the I/O module’s 24 Vdc auxiliary output supply
via the external link (supplied fitted by default).
Relay Outputs
output LEDs
C 5 NC C 6 NC C 7 NC C 8 NC
13 14 15 16 17 18 19 20 21 22 23 24
The Relay Output channels are only available on the I/O modules. They are single pole changeover relays with 3 terminals
(normally closed NC, normally open NO, and common C). Each channel has a status LED (yellow) which illuminates when
the relay is energized (NO connected to C).
N C
N N O
Analogue output
P 5 0 P 6 0 P 7 0 P 8 0
LEDs
24 V
P 13 14 15 16 17 18 19 20 21 22 23 24
There is an I/O module status set indicated by a silk screen on the cover, and LEDs for the input and output channels
(Universal Input, Auxiliary Output, and Relay Output).
I/O Module Status set: This collection of 3 LEDs, power ( ), watchdog ( ), and I/O bus ( ).
LEDs
Power
I/O bus
Watchdog
Power ( ): (green) ON when supply is connected. Flashes briefly at 1 second intervals if power supply fault; this is
probably due to too many I/O modules being supplied from the IQ3 and the controller is unable to supply the necessary
starting current.
I/O bus error ( ): (red) This LED will illuminate continuously for an I/O bus fault (e.g. check for short circuit between
Data Hi or Data Lo and either of the power lines). If the LED flashes at 1 second intervals, the I/O module has not been
in receipt of any valid comms for 30 secs, and the module will switch off any outputs. If the LED flashes faster it indicates
an address clash as described below (I/O Module Address Switch).
Note that both the red LEDs are illuminated momentarily when power is applied or after it had been interrupted.
Universal Input Channel LEDs: Each input channel has a yellow LED to monitor the input state when the input channel
is set to a digital input. The LED will illuminate when the associated input contact is closed.
Digital Input Channel LEDs: Each input channel has a yellow LED to monitor the digital input state. The LED will
illuminate when the associated input contact is closed, open collector transistor/open drain FET is on. A logic input sinks
current from the ~ terminal (logic low), or 24 Vac is applied.
Analogue Output Channel LEDs: Each output channel has a yellow LED to monitor the output state. The light intensity
increases with output voltage.
Relay Output Channel LEDs: Each output channel has a yellow LED to monitor the output status. The LED is ON
when the relay is energised.
Input Polarity Error LEDs: Each bank of 8 digital inputs has an Input Polarity Error LED (red) which is ON if one
(or more) of the digital inputs are supplied by an ac voltage, which has been connected with the wrong polarity.
Excess Aux. Current LEDs: The /8AO and /4AO modules have Excess Aux. Current LEDs (red) which will illuminate
if the auxiliary output supply current limit is exceeded. For the /8AO, both LEDs will illuminate if the limit of 300 mA
is exceeded and for the /4AO, the single LED will illuminate if the limit of 150 mA is exceeded.
Override LEDs: The relay outputs with Hand/Off/Auto facility (HOA) have an additional Overridden LED (red) which
indicates that the output has been overridden (either on Hand or Off). The other output LED (yellow) indicates into which
state it has been overridden (see 4.3.4 below).
+ 1 0 + 2 0 + 3 0 + 4 0
address switch
+ 0 + 0 + 0 + 0
5 6 7 8
13 14 15 16 17 18 19 20 21 22 23 24
The address switch consists of a 16 position rotary hexadecimal switch, labelled 0 to 9, A, B, C, D, E, F. Each I/O module
must be set to a unique address in the range 1 to F. A maximum of 15 I/O modules can be supported on the bus. Selecting
address zero disables the module. If there is an address clash on the I/O bus, the I/O bus error LEDs on all the modules
with the same address will flash; a module’s address can be corrected by setting its address switch to other addresses
until its LED stops flashing. When setting up the input and output channels in sensor, digital input, and driver software
strategy modules, the I/O module address and the channel number have to be entered; the main controller is referred
to as module zero.
4.3.4 Hand Off Auto Switch
The relay outputs with Hand/Off/Auto (HOA) facility are based on the standard relay outputs but also have a 3 position
HOA switch per channel.
This switch can be set to Hand ( H , manually overridden ON), Auto (A, under automatic control from the strategy),
or Off (O, manually overridden OFF). In addition to the yellow output status LED there is a red LED which is ON when
the output is manually overridden (i.e Hand or Off). The output status LEDs are nearest to the terminals and the
overridden LEDs are towards the centre of the unit. The output can thus be in one of four states which are shown in the
table below along with the switch and LED states.
State Switch Relay State Overridden Output LED
Postion LED (red) (yellow)
Manually Hand ON ON ON
overridden ON
The HOA switch position is fed back to the IQ3 strategy driver module from where it can be viewed using webpages,
SET, displays, or supervisors.
The IQ3xcite has a hinged plastic cover on it right hand side, and the I/O modules have hinged plastic covers on each
side. This enables the IQ3xcite to be mounted next to an I/O module and for it to be connected by a short rigid
interconnector, supplied with each I/O module. Spare interconnectors are available (XCITE/IC/5, pack of 5). The two
connectors on the I/O module enable the I/O bus to be daisy chained between the I/O modules. The bus should be
terminated at the furthest end from the controller; a terminator is supplied with each controller and fits inside the
controller under the hinged plastic cover. Spare terminators are available (XCITE/TERM/5, pack of 5). If no I/O
modules are used, the terminator must be fitted inside the IQ3xcite.
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0 + 1 0 + 2 0 + 3 0 + 4 0 + 1 0 + 2 0 + 3 0 + 4 0
100-240 V A 11 12 13 14 15 16 P 5 0 P 6 0 P 7 0 P 8 0 P 5 0 P 6 0 P 7 0 P 8 0
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 P 13 14 15 16 17 18 19 20 21 22 23 24 P 13 14 15 16 17 18 19 20 21 22 23 24
0V
I/O modules
IQ3 with 2 adjacent I/O modules using interconnectors
[The bus is terminated by fitting a 122 resistor between Data Hi and Data Lo terminals].
Interconnector Terminator
(XCITE/IC/5 pack of 5) (XCITE/TERM/5 pack of 5)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12
+
1 0 +
2 0 +
3 0 +
4 0 +
5 0 +
6 0 +
7 0 +
8 0 +
9 0 +
10 0 + 1 0 + 2 0 + 3 0 + 4 0
100-240 V A 11 12 13 14 15 16 P 5 0 P 6 0 P 7 0 P 8 0
P 0 P 0 P 0 P 0 P 0 P 0
OK RX
24 V
24 V
24 V
P 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 P 13 14 15 16 17 18 19 20 21 22 23 24
0V
The rigid bus interconnector connects the pins 1:1 with crossover (e.g. pin 1 to pin 5).
Note that the rigid bus connector includes a ground connection.
The connectors are physically polarised so the IQ3xcite, and I/O module right hand side connectors have the same
polarisation with the terminals numbered 1 to 5 (colour coded red, white, green, blue, black respectively).
The left hand side connector on the I/O module is fitted round the other way so it is numbered 5 to 1 (colour coded red,
white, green, blue, black). The interconnection rule is to connect red to red, white to white, etc.
For modules further apart within a metal enclosure, plug in screw terminals (XCITE/CC/10 - pack of 10) are available,
enabling the modules to be wired together. Belden 3084A cable should be used, the ground connector should be earthed
locally, and the cable screen should be grounded at the controller end.
XCITE/CC
Interconnecting cable type A
Note that the cable core colours shown are for the recommended cable, Belden 3084A.
This type of cable (type A) connects right hand side of one module to left hand side of another. It can be used for two
sections of DIN rail in a panel as shown below:
cable type A
terminator
Interconnecting cable type B must be used if the connection is between the same side of each controller (i.e. left to left
or right to right) due to the polarisation of the connectors.
cable type B
cable type B (right to right)
(left to left)
terminator
The diagram below shows cable type B connections (colour codes and terminal numbers) being used in a right to right
configuration.
No spurs are allowed. For example, in the multisection panel below, the DIN rail sections are connected in series to form
one single length of bus with termination at the farthest end from the controller.
type B L
N IN
L
N IN
terminator
PSR PSR
DC DC
ADJ. ADJ.
L+ L+
L+ L+
L- L-
L- L-
type A type B
The maximum I/O module currents are listed in the table below: these can be used to estimate the total current required
by the I/O modules. A more accurate current consumption can be calculated as described in section 4.3.7 below. .
4UI: 100 mA 4AO: 100 mA + Aux supply max 150 mA 8DO/HOA 100 mA
4DO/HOA 60 mA
If an external supply is required, then the normal bus connection between 24 Vdc terminals is not made, instead an isolated
24 Vdc supply is wired between the 24 Vdc and 0 V terminals of the unit(s) being supplied.
Note that if an external 24 Vdc power supply is used, its output must be isolated from earth (ground), and it must comply
with the relevant EMC and safety standards.
e.g.
24 Vdc
PSU
Black Red
IQ3 I/O module
+24 Vdc +24 Vdc
#
Data Hi White Data Hi
"
Ground Ground
! !
Data Lo Blue Data Lo
"
0V Black 0V
#
If the two devices are close together then connection is facilitated by the XCITE/PCON/50 cable: the cable leaves a 10
mm gap between the two devices for connection of the supply.
24 Vdc
PSU
Black Red
XCITE/PCON/50
+24 Vdc +24 Vdc
#
Data Hi White Data Hi
"
Ground Ground
! !
Data Lo Blue Data Lo
"
0V Black 0V
#
If the two devices are not adjacent, the XCITE/PCON/1000 cable can be used. This enables devices to be up to 1 metre
apart.
24 Vdc
XCITE/PCON/1000 (1 m, 1yd 3” cable) PSU
Black Red
IQ3 I/O module
+24 Vdc +24 Vdc
#
Data Hi White Data Hi
"
Ground Ground
! !
Data Lo Blue Data Lo
"
0V Black 0V
#
The PSR range of DIN rail mounted auxiliary power supplies (e.g. 1.3 A or 2.5 A) are available. They have isolated
outputs.
mains supply mains supply
Black
Blue
White
White
Black
Blue
L L
N IN N IN
"
! !
"
DC DC
#
ADJ. ADJ.
L+ L+
L+ Black Black L+
L- L-
L- L-
Note: The maximum current that can be passed through an I/O module via the 24 Vdc and 0 V terminals, from one module
to the next, is 2.5 A.
The 24 Vdc may need to be separately supplied to groups of I/O modules so that the maximum current through any one
module’s supply terminals does not exceed 1.6 A.
For example:
IQ3xcite/128 with 350 mA left available from its 24 Vdc combined supply. There are 14 I/O modules as follows:12x8AO,
2x8UI.
24 Vdc
PSU
(5A)
(300 mA)
(1.2A)
IQ3 8AO 8AO 8AO 8AO 8AO
(1.2A)
8AO 8AO 8AO 8AO
Separate feed to each group.
Each group <1.6 A.
(1.2A)
8AO 8AO 8AO 8UI 8UI
Maximum current consumptions were given in the table in section 4.3.6 above, but a more accurate current consumption
of an I/O module can be calculated as follows.
The I/O bus connector 24 Vdc terminal supplies the I/O module’s core electronics, its input/output channels, and the
24 Vdc auxiliary output supply terminal which is limited to 150 mA (typical). The auxiliary output supply is provided
so that it can be linked into the P connector to supply auxiliary power for use by output devices.
I/O channels
1 2 3 4 5 6 7 8 9 10 11 12 e.g. inputs
+ 1 0 + 2 0 + 3 0 + 4 0
22 mA
max
#
"
! !
150 mA
core "
#
power bus
max. electronics
1.6 A 22 mA
max. max.
P 5 0 P 6 0 P 7 0 P 8 0
P 13 14 15 16 17 18 19 20 21 22 23 24
The P bus can be supplied from the I/O module’s 24 Vdc auxiliary output supply by using an external link, or can be
externally supplied by a dedicated, isolated, 24 Vac/Vdc power supply. The I/O module is protected against the wrong
connection of a non-isolated external supply by a non-replaceable fuse.
Internal power bus
P 5 0 5
P 0
24 V
P 13 14 15
24 V
P 13 14 15
External link
PSU
Using internal power supply
Separate power supply (24 Vac/Vdc)
Note that if an external 24 Vac/dc power supply is used, it must be dedicated to I/O channel use, and it must comply
with the relevant EMC and safety standards.
The external supply can be either 24 V ac or 24 Vdc, but if the output devices require a mix of 24 Vac and 24 Vdc a
decision will have to be made over which supply to connect to the P bus; the other supply will need to be provided by
external wiring.
Note that the installer should note whether the P bus is 24 Vac, or 24 Vdc and only connect the appropriate loads.
150 mA (typical)
Example: An XCITE/IO/4UI/4AO I/O module has 2 digital inputs, and 2 external powered current inputs, and 4 voltage
outputs into 1 k loads. The P bus is linked to the 24 V Auxiliary Output Supply and one of the P terminals
supplies a 6RM at 86 mA.
I/O Channels
2 external powered current inputs = 0 mA
2 digital inputs = 0 mA
4 voltage outputs at (1 k is 10 mA + 3 mA) = 52 mA
Core Electronics = 20 mA
Auxiliary Supply out (linked to P bus) = 86 mA
Total = 158 mA
The total consumption from the 24 Vdc supply terminal is 158 mA which should be considered when calculating the
load on the main controller’s auxiliary supply. If the main controller cannot supply this current, an external 24 Vdc
supply should be connected to supply the I/O module.
The Auxiliary Output Supply consumption amounts to 86 mA; this is limited at 150 mA, so 64 mA remains available
from the 24 Vdc Auxiliary Output Supply terminal. If this were to exceed the 150 mA limit, an additional power supply
should be used to supply the P bus as described above.
Note that the 24 Vdc auxiliary output supply is normally about 19.8 V and will drop to about 18.4 V under full load.
TX RX
OK
Network
Address/
terminals
baud rate
switch
The auxiliary board also contains the circuit for a backup battery so it can also fulfil the function of XCITE/BBC as
described in 4.2.13 above. However, the CR2032 battery is not supplied so must be purchased separately if a battery
backup option is required.
The board contains the normal hardware for an IQ system current loop Lan node:
Address/Baud rate switch: The address on the Lan is set by poles 1 to 7 in range 1, 4 to 9, 11 to 119 and must
be unique on the Lan. The strategy address module Local Address parameter monitors the address switch settings and
is read only for IQ3/LAN. The baud rate is set by poles 8 to 10 to 9k6 or 19k2 and must match the other nodes on the
Lan. The Network 2 module monitors the baud rate switch settings which are read only. Note that the zero address reset
is not supported on IQ3 (unlike IQ2).
Address switch
0 SET
1
1 2 4 8 16 32 64
NOT SET
e.g. Address = 2 + 16 = 18
0 19k2
1
19K2
9K6
9k6
Network terminals: The network terminals facilitate connection of 2 off 4 wire cables (enabling a ‘weaving’
connection method).
Indicators: The standard LEDs are fitted (TX, RX, and network OK).
TX :(yellow) ON if current is flowing from the current loop network transmitter
RX :(yellow) ON if current is entering the current loop network receiver
OK :(green) ON if IQ3 successfully communicating over current loop network.
Bypass relays: The board contains 2 changeover relays which bypass the receive and transmit circuitry and
maintain network integrity during power fail.
RX
RTS/TXEN
CTS/RXEN
Communications type
RS485 RS485 RS232
LEDS
terminals
0V A B RA RB
T T
If the IQ3/XNC/SER controller and its slave units are in the same cabinet using the same power supply, each device
should have a good physical earth connection.
Single Cabinet (e.g. RS485 2 wire)
0V A B 0V A B 0V A B
IQ3/XNC/SER
RB
RA
B
T
A
T
0V
If the IQ3/XNC/SER controller and its slave units are in different cabinets or use different power supplies (e.g. different
UPSs), the cabinets should be isolated from each other. If the bus is likely to suffer from surge and grounding problems,
surge protection should be added. The isolator should be connected to the earth of the nearest device, the 0V of the
isolator and the surge protector should be connected together, and earth of the surge protector’s exposed side (e.g.
backbone bus) should be connected as directly as possible to the surge ground or earth bond.
Multiple Cabinets (e.g RS485 2 wire)
terminate at far end
0V A B
0V A B
A B 0V
Isolating
Repeater
A B 0V
Surge A B 0V
Protection
A B 0V
Surge Ground
or Earth Bond
Cabinet B
Cabinet A
RB
Isolating Surge
Repeater Protection
RA
T
B A
to more cabinets
T
A B A A A
0V 0V B B B
Backbone Bus terminate at far end
0V 0V 0V
RS485 2 wire
0V A B 0V A B 0V A B
IQ3/XNC/SER
RB
RA
B
T
terminator
0V
RS485 2 wire is multidrop, and half duplex. There may be up to 32 devices on the bus.
Note that only bus topology should be used (not loop or star), and any stubs should be kept short.
The bus should be terminated with a 120 ohm resistor across the single pair of lines at each end of the bus only (not at
any devices in the middle). The IQ3../.../XNC/SER/... has an integral terminator which should be switched into the
circuit (using the terminator switch) if it is at one end of the bus.
The cable used should be 24 AWG twisted pair, with a maximum length of 1200 m including stubs.
RS485 4 wire
RS485 4 wire
0V TA TB RA RB 0V TA TB RA RB 0V TA TB RA RB
IQ3/XNC/SER
120 ohm
terminators
RB
RA
B
T
T
A integral 120 ohm
0V terminators
RS485 4 wire is multidrop, and full duplex (although it may be used for half duplex signalling). There may be up to 32 devices
on the bus.
The IQ3../.../XNC/SER/... is the master and other units on the bus are slaves so that the IQ3’s transmit lines are connected
to the other devices’ receive lines, and all the other devices’ transmit lines are connected to the IQ3’s receive lines.
Note that only bus topology should be used (not loop or star), and any stubs should be kept short.
The bus should be terminated with a 120 ohm resistor across the two pairs of lines at each end of the bus only (not at
any devices in the middle). The IQ3../.../XNC/SER/... has integral terminators which should be switched into the circuit
(using the terminator switch) if it is at one end of the bus.
The cable used should be 24 AWG twisted pair, with a maximum length of 1200 m including stubs.
RS422
external 100 ohm
IQ3/XNC/SER terminator
0V
RB TA
RA TB
B RA
T
A
T
RB
0V 100 ohm terminator
RS422 is for a connection between 2 devices only, and full duplex (although it may be used for half duplex signalling).
The bus should be terminated with a 100 ohm resistor across the receiver pair of lines at each end of the bus only (not
at the transmit pair of lines). The IQ3../.../XNC/SER/... integral terminators should be switched out of the circuit (using
the terminator switch), and an external 100 ohm resistor connected across its receiver lines.
The cable used should be 24 AWG twisted pair, with a maximum length of 1200 m.
1 no connection
no connection 6 1 RX
2 RX 2 no connection
RTS 7
3 TX 3 CTS
CTS 8 4 RTS
4 (held high) 5 GND
no connection 9
5 GND
6 TX
Note that the 9 way D type terminal 4 (normally DTR) is held high so that the RS232 convertor used for the NBOX/
XNC220/485 or the ENC2/S can be powered from the connector; this facilitates upgrading the ENC2/S to IQ3../...XNC/
SER/...
Communication type LEDs: These consist of 2 RS485 LEDs and one RS232 LED. Using the TCL application the
interface type may be set to either RS232, RS485 2 wire or RS485 4 wire.
RS232 LED: This green LED is illuminated for RS232 and extinguished for either type of RS485
RS485 LEDs: These two green LEDs operate as a pair. The left LED is illuminated on its own for RS485 2 wire. This
indicates that the 2 terminals below it (TA, TB) should be used.
Both the left and right LEDs are illuminated for RS485 4 wire indicating that both pairs of terminals below the LEDs
should be used (TA, TB, RA, RB). Both LEDs are extinguished for RS232.
RS485 RS485
A B RA RB A B RA RB
0V T T T T
0V
A B TA TB RA RB
Communications LEDs: These 4 LEDs indicate the state of the communications through the serial interface:
TX: This yellow LED is illuminated when the interface is transmitting, and extinguished when it is receiving. It
normally flashes as communications proceed.
RX: This yellow LED is illuminated when the interface is receiving, and extinguished when it is transmitting.
It normally flashes as communications proceed.
RTS/TXEN: (green) For RS232 this LED is illuminated when the interface is ready to receive and handshaking
is selected . For RS485 4 wire, the LED is illuminated when the interface is enabled to Transmit. For RS485 2 wire the LED
is illuminated when the interface is in transmit mode and extinguished when it is in receive mode.
CTS/RXEN: (green) For RS232 this LED is illuminated when the connected equipment is ready to receive and
handshaking is selected. For RS485 4 wire, the LED is illuminated when the interface is enabled to Receive. For RS485
2 wire mode, the LED is permanently extinguished.
TX
LED 1 (yellow)
RX LED 2 (green)
RTS/TXEN
LED 3 (red)
CTS/RXEN
LED 4 (yellow)
Communications LEDs TCL LEDs
SET facilitates strategy creation by providing an indexed library of pre-configured strategy blocks; these may be viewed,
printed, or edited.
SET configuration files upload or download only operates fully via the IQ3’s Ethernet port*. In order for this to operate
the IQ3 must first be configured with its Ethernet address parameters. This is done using the IP Tool applet which runs
within SET.
Once the IQ3 can communicate via Ethernet, its Trend addresses can be set up using IPTool (within SET), and then the
configuration files can be downloaded by SET.
*Note that the strategy file may be uploaded or downloaded by SET by way of the RS232 port or the current loop network
(if the auxiliary board option, /LAN, option is fitted), but not the other configuration files: language, backdrop, and XNC
(for IQ3/XNC versions only).
Once the strategy is downloaded and running it can be modified using the web pages (parameter changes only), by SET
live Edit, or by downloading a subsequent strategy file.
Any changes made within the controller should be uploaded to SET as a backup file.
By default the IQ3 will automatically set up its IP addressing as explained below (also see Pt. 1 section 3.3.11) .
If a DHCP server is connected to its Ethernet segment and is properly configured, the server will set up the controller’s:
IP Address
Subnet Mask
Router 1 (default router)
WINS Servers (1 to 5)
DNS Servers (1 to 5)
If there is no DHCP server connected to its segment the IQ3 will go into link/local mode and autonegotiate its IP address
with the other members of its Ethernet segment; this will set up the controller’s:
IP Address (starting at 169.254.0.0)
Subnet Mask (set to its default, 255.255.0.0)
Router 1, WINS servers, and DNS servers will remain at their last settings.
The controller may be left in link/local but, as explained in Pt. 1 section 3.3.11.6, it is recommended that link/local only
be used as normal operation on a single segment system, (not across a router). Also note that any other device
communicating with the IQ3 (e.g. a supervisor PC) must also be in link/local.
While the controller is set to automatic addressing these IP addressing parameters may not be changed by SET or IPTool.
For configuration, the IQ3 and the PC running SET should be connected to Ethernet as described in Pt. 1 section 3.3.3.
For initial configuration the PC running SET must be on the same Ethernet segment as the IQ3 (i.e. not separated by any
routers).
Each IQ3 has a unique MAC (Media Access Control) address allocated to its Ethernet node. IP Tool can use this address
to identify the IQ3s on the segment and to access its parameters.
If there is no DHCP server and Link/Local operation is not satisfactory for the reasons explained above, the controller
should be set to ‘Enter Manually’ Addressing Mode, by de-selecting the device mode (Auto-ip-DHCP) check box in
IPTool.
In ‘Enter Manually’ Addressing Mode, the following need to be set up manually (best done using IPTool):
IP Address
Subnet Mask
Router 1
and optionally: WINS servers 1 to 6
DNS servers 1 to 6
SET can download its configuration files to the IQ3 using another vCNC (i.e. in a 3xtend/EINC L, or an EINC or in another
IQ3), but if it using the same IQ3s vCNC, the vCNC should be set up in the controller. This is done using IPTool to set
up the vCNC outstation address and port number.
Note that SET can download a strategy file to the IQ3 over the Trend current loop Lan (if /Lan option is fitted) but
the other configuration files (backdrops, languages, XNC program- /XNC only) can only be downloaded over
Ethernet.
SET can download the strategy files across a router if set up correctly as described above.
Once these parameters are written to the controller, SET can be used to download the strategy file. The strategy file is
created in SET as described in sections 5.2 to 5.16 below and downloaded as explained in Pt.2 sections 6.1, 6.2.
When SET v 6.1 or greater is connected to the controller it will offer to synchronise time and date. Prior to version 6.1
this can be done by the time module web page (see Pt. 2 section 32.2). System synchronisation is best done using a
timemaster (see Pt. 2 section 32.4.1).
The following parameters would normally be the same for all IQ3s on the same subnet:
Subnet Mask,
Router 1 (default router)
UDP Port
WINS server 1
Remote Devices
Once these are set up in one IQ3, IPTool enables them to be copied to other IQ3s. This is done by selecting Default Settings
and selecting the ‘Copy from Selected Device’ and then the ‘Save’ buttons.
Note that the Remote Devices can also be copied from one controller to another using SET (see Pt. 2 section 20.1.2.3)
Note that IPTool cannot make changes if a user module has been set up in the controller (other than indirectly using
a web browser to access web pages) - see Pt. 2 section 34 for setting up and deleting user modules.
IPTool can then be used to set up the controller host name, if auto addressing is selected, and host name needs to be
changed from default host name.
IQ3/BAC can be configured to communicate using BACnet protocol. The default settings of Network module 3 (type
5: BACnet) will normally allow the IQ3 to communicate over BACnet; special cases where the parameters need to be
changed are covered in Pt. 2 section 20.3.4. SET can be used to check that the IQ3 communicates over BACnet - see Pt.1
section 3.7.3.
There are certain issues with communicating over BACnet where the IQ3 is set up for automatic IP addressing - see Pt.
1 section 3.7.4.
2 Discover IQ system Ethernet products on a network segment*. By pressing the ‘Connect’ button all IQ
system Ethernet devices on the same network segment as IP Tool will be displayed.
3 View Remote Trend Devices: It is also possible to view IQ system Ethernet devices on the other side of
the router if a device on the local segment has its Remote Trend Devices table set up. The local device
is first selected, then select ‘Request details from the remote Trend device’.
4 Configure IQView and 3xtend/EINC Ls (and EINCs): Set up the above Ethernet parameters, Lan number,
Outstation Address. On 3xtend/EINC L (and EINC) the Remote Trend Devices table can also be set up.
5 Check Group Settings: Check that all devices on the same site (same UDP port) are set up correctly. Check
IP addresses are not duplicated, they have same subnet mask, they have compatible IP addresses, same
default router, checks if lowest IP address (cross router master) has Trend devices table set up, check none
of devices in stand-alone mode, checks for duplicate Lan, Node addresses.
6 View an IQ3 controller’s web pages. IP Tool will run up a browser to view the web pages.
7 Create a Trend Universal Address (TUA) for SET. The TUA determines a connection string for the IQ3’s
virtual CNC. This is then copied into SET’s site connections file, so that SET can communicate with the
IQ3 via its IP address and port numbers.
*Note that IP Tool will show all devices on its segment regardless of the devices’ UDP settings (i.e. it can operate on
a ‘multi-site’ system where devices use different UDPs on the same segment as described in Pt. 1 section 3.3.11).
Strategies are configured by setting up these modules and inter-linking their inputs and outputs. The module interlinking
may be drawn as a strategy diagram which is quickly and easily understood. The controller can be configured to perform
complex tasks without the use of a computer programming language.
5.3 Interconnections
The configuration of an IQ is best explained by imagining a collection of boxes, each box having a specific function.
The boxes can be interconnected in virtually limitless combinations, to achieve the required control strategies.
As with a traditionally hardwired system, it is necessary to ‘wire’ the system by connecting outputs to inputs.
Linking modules B1 B2 B3
In the above diagram a signal is passed from box B1 to box B2 and similarly another signal is passed from box B2 to box
B3.
In the diagram below it can be seen that the inputs to more than one box can be sourced from a single output: the output
of box B1 is connected to the inputs of boxes B2, B3, and B4.
B1 B2
Multiple destinations
B3
B4
Normally the input to a box will be sourced from one output, but it is possible (with special care being taken) to connect
more than one output to an input; this is termed ‘multiplexing’.
This is not recommended for IQ3 and should not be necessary as the controllers have plenty of capacity: it is described
in this manual so that strategies from earlier IQs may be understood (see section 5.6.8 below).
Multiplexing
Using SET, connections are made by clicking on an output and dragging the connection to the input. It will not allow
connection from outputs to outputs, or from inputs to inputs.
The conventional term for these boxes is modules (software modules) and from now on each box will be referred to as
a module.
In common with system hardware inputs and outputs to HVAC equipment, software interconnections are either analogue
or digital. An analogue connection is used to pass a value, whereas a digital connection is used to pass an ON/OFF status
(i.e. 1 or 0 respectively).
In order to differentiate between analogue and digital connections on controller strategy diagrams, digital and analogue
outputs are represented by small squares and circles respectively, whereas digital and analogue inputs are represented
by half squares and half circles respectively.
digital output digital input
B1 B2
B3 B4
Normally an analogue output cannot be connected to a digital input, nor can a digital output be connected to an analogue
input; SET will prohibit such attempts. An exception is the Plot module Source input which can be connected to either
an analogue or digital output and has a special symbol:
Sensor 2
S2V S P1
SYNC
15 Min Period
1000 Records
0 Notify Threshold
0 Log Level Group
In IQ3 all inputs can be sources or constants (i.e. either sourced from another point in the strategy, or given an internal
value within the module).
Making a connection to an input changes it to be a sourced input, the source is shown on the strategy icon and in the
SET dialogue box, and a constant value can no longer be entered in the SET dialogue box, the parameter being greyed
out.
If the input is a main input when it is a constant it loses its connection tail. However it can still be linked to an output.
49 49
F10 F10
0 E 1 E
2 D 2 D
0 G 1 G
SQUARE ROOT SQUARE ROOT
main inputs as default D=E*SQRT G D=E*SQRT G
main inputs set to constants
Input and output modules (drivers, sensors, digital inputs) have to be connected to the hardware input and output
channels. These connections are made using the SET dialogue box.
These connections consist of two parameters: the I/O Hardware Module and the Channel. The I/O Module can be set
in the range 0 to 15 where module 0 signifies the main controller and modules 1 to 15 signify external I/O modules.
I/O Channel
In the above external digital input module symbol the input from the hardware channel is shown with the two parameters
m (I/O module) and c (channel).
For external digital inputs, and external sensors (digital or analogue) if the input channel number is zero, the input is treated
as a constant, and its value can be set up on the web page (but not by SET).
1 Receiving inter controller communications (IC Comms) or for use with devices using text comms to nodes
(e.g. Wireless Sensor Receiver).
2 Provision of a constant value shared between several module inputs.
3 Compatibility with Supervisors set up for IQ1 or IQ2 strategies.
4 Detection of alarm status bits from function module outputs.
An analogue node is represented by a circle and the letter A. It has a node number (e.g. A2, analogue node 2). It acts
as a store for an analogue value.
20 V A1 D
Analogue
Read Alarm
Out. Limits Alarm
Low Alarm
High Alarm
Since an analogue node is always event driven (see 5.6.2 below), its output should never be connected back to its input.
SET prohibits this.
B2 a
,0 b
,1 c
,2
,3 d
,4 e
,5
,6 f
,7 g
Byte h
In IQ3 digital nodes exist in digital Byte modules (e.g. Bx). The byte consists of 8 bits (or digital nodes), bits 0 to 7. The
digital outputs corresponding to bits 0 to 7 are identified as a to h respectively.
Either the whole byte (e.g. B1(S=OOIIOIIO)) or a single bit (e.g. B1(S0=I)) may be written to using IC Comms.
These bits are transferred by analogue IC Comms, and are exposed by the analogue node receiving the IC Comms.
They are passed from module to module in the strategy and can be exposed anywhere in the strategy by connecting an
analogue node to that point.
See Pt. 1 section 12.4.3 for a description of the way these alarm bits affect the strategy.
A module has a defined functionality in the transfer function it applies between its inputs (and internal stored values)
and its outputs.
e.g. S1 = sensor
Each module has a number of parameters. These include connectable inputs, connectable outputs, internal configuration
parameters (e.g. Driver type, Logic module combination), and internal values (not connectable e.g. Loop module integral
part).
The modules are initially configured in SET. The module instance is created in SET as are the input and output
connections. Other parameters are initialized by SET but may later be modified (e.g. by Web pages).
The strategy data file produced by SET consists of all the strategy module instances, their parameters, and links. When
this is downloaded it is stored in the controller and then run using the controller firmware.
For example the SET symbol for an internal analogue sensor with all its parameters displayed is shown below.
sequence step
disable input
3
Sensor 2 label
S2
V
main input 0 S main output
INTERNAL
DegC Units
0 High Alarm Limit
0 Low Alarm Limit
0 High Alarm Delay
0 Low Alarm Delay
0 Out.Limits Delay
0 Read Alarm Delay
Disabled Read Alarm
Disabled Out. Limits Alarm
Disabled Low Alarm
Disabled High Alarm
0 Override Enable
0 Override Value
inputs outputs
The module symbol obeys the rule ‘inputs on the left and outputs on the right’.
For example the internal sensor module symbol displays the following:
Main input(s) :Internal sensor input; may either be sourced from an output or set to a value.
Main output(s) :Sensor value
Label :(defaulted to ‘Sensor 2’) Most types of modules have labels which can be customised.
Units :(defaulted to ‘Deg C’) only on Sensors and Knobs
The other Sensor parameters are shown as inputs; they may either be sourced from outputs, or set to a value:
The sequence step is shown on modules which are serviced via the sequence table (see section 5.6 below - Module
Servicing).
In SET connections are made by dragging lines between outputs and inputs, and the strategy page number and x, y co-
ordinates are defined by its position on the page. The other parameters can be entered in the module dialogue box.
display boxes
display buttons
For example the SET internal sensor dialogue box enables entry of:
Label, Units
High, Low Alarm Limits
High, Low, Out of Limits, Read Alarm Delays
High, Low, Out of Limits, Read Alarm Enables
Override Enable
Override Value
Source value: This is either sourced from another module, or can be entered into the box, or set up using the slider.
Read, Out of Limits, Low Alarm, High Alarm Groups: These are the groups to which these alarms are attached,
enabling them to be manipulated by the IQ3 alarm as part of the group.
The display box shown against each parameter in the dialogue box defines whether the module parameters are displayed
on the strategy page (a ticked box indicates that the parameter is displayed).
The display buttons give control over the display boxes:
Clicking will tick all the boxes (i.e. display all the parameters)
Clicking will return the display settings to the current defaults
Clicking will remove all the ticks from the display boxes (i.e display none of the parameters)
Clicking will save the current settings of the display boxes as the new defaults.
Only certain parameters may be modified; those parameters concerned with the strategy structure cannot be changed,
e.g. the following tasks cannot be performed using the sensor module web page:
Note that web pages will only show values to two decimal points, although the values may actually be accurate to many
more decimal points as described in the section for the particular module in Part 2 of this manual.
The alarms each have sub-module dialogue box which enables the following to be modified:
Alarm Enabled, Alarm Delay, Alarm Group
The synchronised plot modules are checked to see if they require to be updated at the beginning of the sequence table
cycle (i.e. once per second).
The time zone, OSS, schedule states are checked every minute. (There is a special mechanism for a time zone to increase
its timing accuracy).
The sequence table modules mentioned above (Sensor, Driver, Function Module, Logic Module, Schedule) can be set
to be event driven by taking them out of the sequence table. This is done by setting the sequence step blank in SET;
the sequence step will not then appear on the module’s web page.
On the module’s web page, if the module is sequence table driven it will have the Sequence Table parameter set to 1;
if it is event driven it will have the Sequence Table parameter set to zero.
It is recommended that an event driven sequence does not include a loop module, filter function module, or hours run
logic module.
An event driven module is not serviced until the input changes. The advantage is that the module will respond immediately
to the input change. Event driven modules connected together form a fast sequence; the modules will be serviced in the
order they are connected as the event ‘travels’ through them.
Z1
TIME ZONE
0 3 6 9 12 15 18 21 24
MON
TUE
WED
THU
FRI
SAT
SUN
G1 Driver 2
Z1V E G2 D2 L 0
I1S J or m0
Digital Input 1 I1S S D G1D F K or A 0
From Page 2 L or D G2D S
0 G M R
TIMER 0 H Alarm
DIGITAL M
0 On Delay COMB
3600 Minimum On E J Comb. 0 Start Delay
Disabled Invert
0 Off Delay F K Comb.
L Comb. Disabled Maint. Int. Enable
Disabled Readback Enable
M Comb. 0 Maint. Int. Alarm
0 Readback Alarm
0 Readback Delay
Hours Run
Starts
0 Override Enable
0 Override Value
The above modules (G1, G2, D2) are event driven as they do not have sequence steps. When Digital Input one is set
true, G1 ‘immediately’ starts a 1 hour pulse (3600s) which will switch the driver on during non-occupation; during
occupation the driver is on anyway.
Since analogue nodes, knobs, and switches are always event driven, their outputs should never be connected back to
their inputs. SET prohibits this.
A strategy that includes feedback with ‘fan out’ (i.e. which create two output events for one input event) would cause
the 600 module/s limit to be exceeded, and would generate a ‘Sequence Table Overrun’ alarm. The section becomes
non-event driven.
Counting both sequence table steps and events as ‘items’, there can be up to 900 items per second of which 600 can be
sequence table steps.
This input is either sourced from a digital output, or can be set up as a constant. When the input is set true the module
is disabled.
20 V A1 D
Analogue 3
Read Alarm Sensor 2
Out. Limits Alarm
Low Alarm S2
V
High Alarm 0 S
INTERNAL
DegC Units
20 High Alarm Limit
0 Low Alarm Limit
0 High Alarm Delay
0 Low Alarm Delay
0 Out.Limits Delay
0 Read Alarm Delay
Disabled Read Alarm
Disabled Out. Limits Alarm
Disabled Low Alarm
Disabled High Alarm
0 Override Enable
0 Override Value
The above sensor is disabled when the analogue node is in Read alarm.
Disabling can be used for strategy fault finding or in event driven sequences to prevent ‘run away’ operation.
A disabled module is no longer serviced so its output(s) and internal states are maintained at their values prior to disabling.
In general terms, modules are entered in the order of information flow in the control strategy:
Sensors before loops
Functions, logics, schedules and loops before drivers
Examples of where sequence table order is very important, are duty/standby selection (where the status of plant device
is required before a decision to select is made), and the example below where the change in meter output is being
calculated.
F5D E F5
Meter Count kWh 0 F D
0 B 10
GATE
D = F when B = 1
Meter Comms Healthy = 1 F5D E F7
F6D F
D Change in kWh
0 G
11 0 H ADD/SCLR
D = (E * G) + (F * H)
F5D E F6
0 F D
0 B
GATE
D = F when B = 1
In the above strategy, the meter count in kWh is connected through the gate F5 as long as the meter comms are healthy.
In the adder scaler F7, the old value is subtracted so the the output of F7 is the change since the last meter reading. F6
takes the old value and connects it through F6 to the input F of F7. It is important that F6 is serviced after F5 and F7
so that it retains the old value ready for the next sequence cycle.
When the strategy is first started the value of F7 input F will be zero, so that the output of F7 will be the full current count
of the meter. If the meter comms goes unhealthy, the gate F5 will recycle the old meter count so that the F7 output will
be zero, and when the comms returns, the output of F7 will include the change over the missed cycles.
In this strategy it was important the no energy consumption was lost.
This strategy is also used as an example of the effect of a power fail and restoration on a strategy (see section 5.6.8 below).
5.6.6 Multi-Sequencing
A module may be serviced more frequently than once per cycle by putting it in the sequence table more than once.
Separate entries into the sequence table are shown as separate lines on the web page. For example in the logic module
web page above there are two entries into the sequence table at steps 1 and 11.
Note that of the modules that require entry into the sequence table it is recommended that, counter type Logic modules
and Loop modules do not have their time reduced by multiple entry. In the case of counters, when counting external
inputs, their count is only transferred once per cycle (see Pt. 2 section18.7.3); for counting internal nodes multiple
entries will work correctly.
It is recommended that loops only be put in the sequence table once as their service time is specified by the reschedule
time and this cannot be less that the sequence table cycle time; inserting more than once alters the meaning of the integral
time constant and hence the integral term.
A whole sequence of modules (i.e. a sub strategy) may be put in the sequence table more than once to economise on
modules at the expense of sequence table entries. This is call Multiplexing.
5.6.7 Multiplexing
The general principle here is to have a common sub strategy with input and output points and to enter this many times
in the sequence table preceded by its source modules and succeeded by its destination modules.
Multiplexing is not recommended for IQ3 and should not be necessary as the controllers have plenty of capacity: it is
described in this manual so that strategies from earlier IQs may be understood.
14
Zone 2 12 15 18 16
0 E G7 Driver 4
J or W1D E G9 D4 L 0
0 F K or J or m0
L or D G7D... F K or A 0
0 G M L or D G9D S
W2D G M
0 H R
COMB 0 H Alarm
DIGITAL M
COMB
E J Comb.
17 Fg K Comb.
Zone 3 L Comb.
M Comb. 19
0 E G8 Driver 5
J or D5 L 0
0 F K or m0
L or D
0 A 0
G M G9D S
0 H R
COMB Alarm
DIGITAL M
Common Fail
W2
0
D
SWITCH
0 Pin Level
The above is a simple example to demonstrate the principle. Say we have 3 zones producing a demand calling for a zone
fan for each zone. But we want all the fans to come on for one manual override signal and all to be switched off during
normal running if there is a common fail condition.
Instead of requiring 3 logic modules we can use G9 three times by multiplexing it between the input and output modules.
Step
11 G6
12 G9
13 D3
14 G7
15 G9
16 D4
17 G8
18 G9
19 D5
Thus, first of all process input, then common modules, then the output.
This process saves 2 logic modules but, because G9 is multiplexed, viewing it in SET Live Values will show its value
at the point in the cycle hit by the communications. Thus fault finding a strategy like this is difficult, and the technique
should not be used unless it is necessary to save modules.
Note that modules whose current output depends on current input and previous output levels such as Loops (with
Integral), Function module type 1 (filter) or LoGic type 4 (counters), or type 6 (hours run) should not be multiplexed.
When an IQ3 module is serviced it takes whatever is in its input(s) and applies these values and any internal values to
its specified transfer function, sets up its outputs, and passes the outputs to its destination(s).
An earlier IQ would fetch its inputs from their sources (normally analogue or digital nodes), apply these values and any
internal values to its specified transfer function, set up its outputs, and pass the outputs to its destination nodes.
This difference has particular relevance for the way in which a strategy will run after a power cycle.
When an IQ3 powers down it will store the values held on the inputs and outputs according to specific criteria, the idea
being that the strategy should run correctly on the first sequence cycle after power is restored. The values that are stored
are called critical data and are selected according to the following rules;
1 Unconnected inputs (i.e. constants) are critical (because they cannot be restored by recalculating from earlier
modules in the sequence)
2 Connected inputs unless they are connected to a module that is earlier in the sequence table (because of same
reason as 1 above), excluding event driven connected inputs (because they will be generated correctly on the event driven
first pass)
3 Internal values
4 Special exceptions
Module outputs are non critical because they will always be recalculated.
The previous example used in calculating the change in meter output used in section 5.6.5 above can be used to illustrate
this point.
critical data
9
F5D E F5
Meter Count kWh 0 F D
0 B 10
GATE
D = F when B = 1
Meter Comms Healthy = 1 F5D E F7
F6D F
D Change in kWh
0 G
11 0 H ADD/SCLR
D = (E * G) + (F * H)
F5D E F6
0 F D
critical data 0 B
GATE
D = F when B = 1 critical data
In this example F6 input E, F7 input F, F7 inputs G and H, and F8 inputs F and G are critical data.
F6 input E, because it is connected to its own output so it cannot be serviced earlier.
F7 input F, because F8 is serviced after F7.
F7 inputs G and H, and F8 inputs F and G, because they are unconnected inputs.
So on the first pass after power up both F5 input E and F7 input F will have the last count. If the meter is not healthy,
the change will be zero, and if the meter is up and running the change since the last reading will be correctly calculated.
It is important that the modules generating the meter count and the meter comms healthy are in the sequence table before
these strategy modules, otherwise they will be critical data, and on the first pass will have their old values. This could
cause F6 to gate through a rogue value.
If overridden by SET or a web page, the module will be overridden while the address module override timer is true; once
an override is set, the address module override timer should be set to the required time, and it will start counting down
to zero at which point this override (and any other overrides set up) will be removed. This enables an engineer to check
the plant, confident that the override will be automatically removed.
If controlled by a connection, the module will be overridden while the connection is true.
Each of these input/output strategy modules has an Override Output Status (the override input which could be a
connection) to set the override condition as described above, and an Override Value/Status (which could also be a
connection) which is the value or status the output will assume while the override is on.
Whether the module has an Override Value, or Status depends on its type. e.g. an analogue driver will have an Override
Value, whereas a digital driver will have an Override Status.
40
Heating Valve Zone 1
D20 L 1
m2
Heating Valves Override L10D
A 0
Heating Loop Zone 1 L10D S
W8 From Page 5
0 R
D
Alarm
SW ITCH ANALOGUE M
W8D Override Enable
K8D Override Value
In the diagram above both analogue drivers have their Override Enable parameter connected to the output of a switch
(W8), and their Override Value parameter connected to the output of a knob (K8). As both drivers are analogue they have
an Override Value (not Status). When W8 is true the driver outputs are controlled by K8; when W8 is false the driver
outputs are controlled by their S inputs, Heating Loop Zone 1 and 2 respectively.
The available capacity is measured in brIQs. The total available capacity in an IQ3 varies with the type and is given in
the table below (along with maximum plot memory capacity).
Type: IQ3xcite IQ3xact IQ3xcite
I/O max.: 0 12 16 96 128
IQ3 briqs max. version not 10,000 30,000 30,000 37,000
available
plot memory max. (bytes) 100,000 500,000 500,000 500,000
IQ3/XNC briqs max. 45,000 20,000 version not 45,000 version not
available available
plot memory max. (bytes) 500,000 100,000 500,000
For synchronised logs (plots), each plot record requires 5 bytes, so IQ3xcite/128 can have up to 100,000 synchronised
plot records. For triggered or periodic plots, each record requires 10 bytes, so IQ3xcite/128 can have up to 50,000 triggered
or periodic plot records. Note that in SET a plot memory byte is referred to as a ‘log point’.
Each type of module has memory requirement in brIQs as listed below; SET also limits the number of modules as shown
in the table.
Size
Category Module SET max
(brIQs)
Group 9 500
Route 9 500
Alarm modules
Destination 14 (8)
Log§ 0 1
Function# 19 500
IC Comms# 19 250
L o g i c# 19 500
Loop 55 500
analoge node# 510
16
digital Byte# 1012
OSS 34 500
Sensor type 12 99
Control Modules
Driver# 57 500
Digital input# 28 1000
Knob 13 1000
Schedule 21 500
Sequence† 106 1(600 steps)
Sensor# 76 999
Switch 10 1000
Time Module 38 1
Time Zone* 566 100
Virtual CNC 9 1
Address 24 1
I/O module 14 15
P age 4 500
General Modules XNC Interface††† 130 1
Non-Trend Device 30 ††††
Network 0 §§
Option 0 §§
Program 0 1
Plots†† 12 500
†Display Directory 13 500
Modules Display 19 500
User 12 500
Notes:
# The actual size in (number of brIQs) varies with module type.
The largest size is shown here.
* The time zone brIQ count allows for an average of 20 exceptions.
†The sequence table takes 106 brIQs; the table includes a maximum of 600 steps.
IQ3 has an absolute limit of 4000 modules; the limits imposed by SET prevent this from being exceeded.
The IQ3 also limits the number of destination modules to 8 as shown above.
In SET, as the modules are created, a tally is kept of the brIQs and plot memeory bytes (log points) used and the amount
available to be used; this is indicated in the status bar at the bottom of the page.
plot memory bytes (log points) available to be used brIQs available to be used
If the limit is exceeded, then SET will prohibit the creation of further modules.
It is possible to create modules which are not numerically sequential so module lists can be non-continuous (e.g. L1,
L2, L5, L7...).
SET Modules are added to the strategy by adding them to a strategy page.
When configuring an IQ3 controller only the modules used in the strategy are added to the controller’s memory.
When a new IQ3 controller is created in SET, SET will automatically allocate 721 brIQs of memory for the address
module, time module, and sequence table. For an IQ3xcite this leaves 29279 brIQs of memory for the strategy.
Inputs:
- external sensor (analogue)
- internal sensor (analogue)
- external digital sensor
- internal digital sensor
- digital input
- knob
- adjustment knob (not used in IQ3)
- switch
- analogue node
- digital node
- Lookup
- Add
- Hysteresis Limits
- Proximity
- Power
- ABS (olute)
- TRUNC (ate)
- Trig (onometric)
Logic:
- Combination
- Timer
- Read back
- Counter
- Delay
- Hours Run
- Fan Out
- D to A
Other:
- To connective
- Connective
- Undefined connective
- Loop
- Schedule
- Time Zone
- OSS
- Plots
- Users
- Time module
IC Comms:
- Data from
- Data to
- Global to
- Minimum
- Maximum
- Sum
- Average
Alarm handling:
- Alarm Grouping
- Group
- Route
- Destination
- BACnet Alarm Block (IQ3/BACnet)
- Critical Alarms (not IQ3)
strategy
module
classes
Enter the code, press enter, move the cursor on the page and click, and the module will be placed on the page.
Module Command
ABS Function Module F24
Add Function Module F20
Adder/Scaler Function Module F8
Adjustment Knob Module KA
Alarm Destination Module ALARM DEST
Alarm Group Module ALARM GROUP
Alarm Route Module ALARM ROUTE
Analogue to Digital Function Module F18
Analogue Driver Module D2
Average Function Module F13
Binary Switch Driver Module D5
Combination Logic Module G1
Comparator Function Module F15
Counter Logic Module G4
D to A Logic Module G8
Delay Logic Module G5
Digital Driver Module D1
Digital Input Module I
Divide Function Module F10
Enthalpy Function Module F16
External Digital Sensor Module S3
External Sensor Module S1
Fan Out Logic Module G7
Filter Function Module F1
Gate Function Module F14
Hours Run Logic Module G6
Hysteresis Band Function Module F17
Hysteresis Limits Function Module F21
Internal Digital Sensor Module S4
Internal Sensor Module S2
Knob Module K
Limit at Function Module F4
Limit to Function Module F5
Log Function Module F6
Lookup Function Module F19
Loop Module L
Maximum Function Module F12
Minimum Function Module F11
Multiply Function Module F9
Plot Module P
Power Function Module F23
Proximity Function Module F22
Raise/Lower Continuous Driver Module D7
Raise/Lower End Driver Module D4
Readback Logic Module G3
Rescale from Function Module F2
Rescale to Function Module F3
Schedule Module H
Square Root Function Module F7
Switch Module W
If required the code entered into the command bar can also specify module numbers and sequence steps.
i.e. <module type>#<module number>#<sequence step>
e.g. F1#7#03 ENTER
will create filter function module number 7 with sequence step 3.
A single module or multiple modules are selected either by dragging a box around the required module(s), or by holding
down control and clicking on the modules. The module set can them be copied by right click/copy (e.g. Control C or
Edit/Copy).
Then paste by Control V, Edit/Paste or right click/paste and move the cursor to the required position and click.
The required strategy block can be found from the Strategy Library, or by using the Search Library section. The Search
Library section is selected from the strategy library page by using the icon. It enables keywords to be entered and
then searches all the strategy blocks and displays those with matching keywords
To add a strategy block page or a complete strategy block (i.e. may be several pages) to a strategy, select the strategy
block page or complete block in the Strategy Library or Search Library section and click and drag its icon and name
onto the strategy page. The new strategy page(s) will be added to the controller.
strategy block
strategy block page
Stategies relevant to the type of controller can be selected by using the (filter) icon.
The above diagram shows the default state of the Next Modules List. The ticked modules will not be allocated
automatically; when such a module is added it will request the next module number. The list also shows the next sequence
step number.
If it is required to change the next module or sequence step (e.g. to leave a gap), then the value can be changed by
highlighting the next entry and typing the new value.
The key can be used to check that the ‘next’ value is valid and unused.
Note that if a module’s number is to be changed after creation, this can only be done by deleting the module and creating
a new one with the new number.
The module’s sequence steps are shown on the left , and available steps are on the right. A step can be added by selecting
the step in the right hand box and pressing .
A step can be removed by selecting the step in the left hand box and pressing .
SET has a number of functions for dealing with changing sequence steps selected by top rail menu icons:
(or menu Tools/Sequence Steps/Move) This enables a group of modules to be moved to a new set of sequence steps.
(or menu Tools/Sequence Steps/Free) This enables modules to be removed from the sequence table. This will cause
IQ3 modules to become event driven.
(or menu Tools/Sequence Steps/Insert) This enables a gap to be inserted in the sequence table.
(or menu Tools/Sequence Steps/Skip) This enables a gap to be inserted in the sequence table when a new page is
added.
Moving: Once selected, left click on a module and drag it to the new position. All links between modules will be
automatically routed to avoid other modules and links.
Deleting: Once selected either press ‘DEL’, or right click on the page and select ‘Delete selection’.
Strategy creation in SET involves adding a page and then adding modules to that page.
This enables the page to contain an area of strategy functionality (or sub-strategy). Each page has a descriptive label
(up to 30 characters) to identify it and describe its function. A strategy page may be downloaded to a controller (see Pt.
1 sect. 6.2.5). A strategy page may be printed for hard copy. The icons on the bottom rails enable pages to be viewed
and added.
Right clicking on a strategy page and selecting Page from the drop down menu enables selection of deletion of a page
or access to page details.
The page details contain create date/name and modifications date/name, and a 2 line label. Line 1 label is the Page label
(up to 30 characters) which is stored in the page module in the controller and appears on the page is SET. Line 2 label
only appears in SET (is not stored in the page module in the controller).
Each strategy module has a page number parameter (p) and x and y coordinate parameters and these are stored in the
module in the controller. This enable strategy to be backwards engineered (if the strategy file is lost), by uploading from
the controller (see Pt. 1 section 6.4.1).
Modules which are not shown on strategy pages and hence do not have coordinates are:
sensor types, sequence table, address, I/O, display, directory, network, program, option, and page modules.
The x and y values determine the position of the top left hand corner of the complete module working from the bottom
left hand corner of the page. The scaling of the x and y coordinates can be seen from the diagram below.
The x coordinate has the range 0 to 255, and the y coordinate, 0 to 180.
1 8 0
2 8
G F 1
E D
F H Y S T L B
0
0 2 5 5
x
The position coordinates are automatically produced by SET and hence do not normally need to be changed.
5.14 Connectives
Connectives enable links to be made between modules on different strategy pages. They can also be used to link two
modules on the same strategy page where adding a full link between the modules would make the page confusing.
They are also used for linking to modules not shown on strategy pages (e.g. address module, power reset).
‘From Connective’ (referred to as ‘Connective’ in SET). This enables an input to be linked to one of a
selection of outputs, (and also an output to be linked to an XNC interface module input).
‘To Connective’. This enables an output to be shown on the page as being linked to another module. This
type of connective is cosmetic. The ‘Connective’(from Connective) actually makes the strategy link.
10
0 E G5
A1R
Rd - J or
A1R F K or
From Page 2 D G5D
L or
0 G M
0 H To Pages(s)
COMB
J Comb.
K Comb.
Note that the To Connectives’ positions on the page are not stored in the controller although the Connective (from
Connective) links are. If backwards engineering (see Pt. 1 section 6.4.1), the connectives must be redefined on their
respective pages.
A connective can be added to a page by using the connective icon or right click and select Other/Connectives.
The connective dialogue box is displayed.
Other
connectives for
a strategy
module (e.g S1)
The dialogue box enables a connective to be selected from the list of connectives. Analogue values are shown as circles,
and Digitals as squares. For example OA1D means Analogue Node 1 Destination (output). Some of the connectives will
be labelled.
For non-strategy modules (e.g. address module) all available connectives are shown.
For strategy type modules (e.g. sensor module), the main module output is shown (e.g. S1V); selecting this will show
the other available connectives for that module in the box below.
The connective should be selected by clicking on it, then selecting ‘Select’ button.
This cursor changes to a hand icond . . Move the cursor to the required point on the strategy page and click. The
connective will be placed at that position. The connective should then be linked to the module’s input in the normal way.
The list of possible connectives can be reduced by using the filter buttons provided in the dialogue box.
The possible connectives may also be reduced by using the type filter (e.g. L for loop), or label filter.
5.14.2 To Connectives
A ‘To Connective’ can be added to a page by using the to connective icon or right click and selecting Other/To
Connective. The cursor changes to the hand icond . , move the cursor to the required position on the strategy page. Click.
The ‘To Connective’ will be placed at that position. The connective should then be linked to the module’s output in the
normal way.
Strategy blocks are created from strategy entered into SET. When you create a strategy block all the links between
modules are retained, as is the relative position of the modules on the page.
The actual modules used are determined, at the time the strategy block is placed in the strategy.
Each strategy block can be made up of several pages of strategy, and it is possible to use the entire strategy block, or
just a particular page. When an entire strategy block is used SET will automatically add the pages necessary for the
modules. If an individual page is used the strategy block modules are added to the existing page.
Strategy blocks are stored in the Strategy Library separate from the project structure so that they may be used across
projects.
SET also features a Search Library facility which enables the a strategy block to be selected by keywords
The Custom library contains strategy blocks that the user has created. These may be modified or deleted.
The Standard Library contains the strategy blocks supplied with SET. They cannot be moved, modified, or deleted.
The Old Library contains any strategy blocks that were created in SET prior to version 6.0. They cannot be modified,
but they can be deleted, or moved into the Custom Library where they can be modified.
The Custom Library strategy blocks can be divided into groups and sub groups. These can be created, deleted, moved,
and named as required by the user.
search box
matching strategies
Create a strategy block group (if the correct one is not already available). Right click on the Custom Library and select
‘New Group’.
Create a strategy block. Right click on the group and select ‘New Strategy Block’.
The strategy block properties should then be set up in the Strategy Block Properties box. These include a Name, the type
of controller (IQ1-2 or IQ3), the Key Search words, and there is also space for details to be entered.
Note that IQ1-2 strategy blocks cannot be used in IQ3, and IQ3 strategy blocks cannot be used for IQ1 or IQ2.
Once the strategy block properties are set up a blank strategy page is displayed ready for the strategy to be entered in
the normal way.
The strategy block may consist of several pages, so further strategy pages may be created as required
Once the strategy block is complete closing the strategy page will cause it to be stored as a strategy block.
The actual modules used are determined, as the strategy block is placed in the strategy, by the ‘next module’ specified
for the module type. The order of the modules in the sequence table is determined by the order in which they are selected
when the strategy block is created. The ‘next sequence step’ determines the sequence step of first module in the sequence
table.
Note that when the strategy block is used, if SET finds a module with a label that matches with the label or a connective
in the plant block, the connective will be defined to use that module. This means that links between pages are kept
providing that link links backwards i.e. a module on page 2 can link to a module on page 1, but not a module on page
3. Any connectives unresolved are placed in the strategy as undefined connectives and have to be defined manually after
the addition of the strategy block is completed.
If a strategy block that uses connectives is to be used more than once in the same controller it is necessary to change
the label of any modules in the strategy that are linked using connectives. This ensures that a match is not found when
the strategy block is added next time. If this is not done SET will make the link to the module that is already in the strategy
not the one in the strategy block.
If there are any input, or driver modules in the strategy block, SET will prompt for the actual module that is to be used.
If the strategy block would cause the strategy to exceed any of its size limits, this is indicated to the user by highlighting
the module in red. The user should cancel the strategy block incorporation, correct the strategy, and try again.
5.16 Solutions
Solutions allow complete controller strategies to stored and re-used. They are stored in the solutions section of the
strategy library; selecting a solution from the library enables a pre-configured controller to be added to the project.
The solutions are either standard or custom.
The soluton is created by configuring the strategy in a controller, and then slecting that controller as a solution.
The configured controller is selected by right clicking on it in the Device View, and selecting ‘Copy to Solution’. The
Solution Properties Dialogue box is displayed.
This enables the solution’s name, group, sub-group, and key words (for searching the library) to be entered.
SET will create a sub directory for the project using the Project Name e.g. C:\Set Project\Project Name. It will then create
a project file using the project number e.g. 1234.TSET. in that directory. It also creates sub-directories to store upload
and download files.
Note that the details of remote devices can also be stored on a project basis (see Pt. 2 section 20.1.2.3)
The Project Details can be subsequently viewed by right clicking on the house in the Device View and selecting
Page Details
Lans can then be created by right clicking on the project name in the Device View and selecting Insert Lan. Each Lan
will have a sub-directory i.e. C:\Set Projects\Project Name\Lan nnn (where nnn is Lan number e.g. Lan013 for Lan 13).
When the dialogue box is completed, SET will create a SET strategy file for that controller within its Lan subdirectory.
e.g. C:\Set projects\Project Name\Lan nnn\L013n020.IQ.
The file name is L013n020.IQ
It will also enter the Site Name and GUID into the address module.
The graphIQ web page is defined using the directory module which has a backdrop parameter. When a backdrop is
referenced on this page it is required to be downloaded to that controller.
Note that an internal backdrop file should not be greater than 100 kbytes. It is not allowed to be greater that 200 kbytes.
The maximum memory available in the IQ3 to hold backdrops is 2Mbytes.
The language files required in the controller are specified using SET in the address module.
language selection
One language can be set as default, the others can either be ‘downloaded’ or ‘not Sent’.
Within the controller it is possible to select the current language via the address module web page (see Pt. 2 section
2.3.5).
Identifier, Local Lan and Local Node, Supervisor port address, IP Address (including Subnet Mask, UDP port, Router1)
They are excluded by clicking on the Not Sent box adjacent to their settings in the Address module dialogue box.
Other parameters can be excluded in the Network 1, Ethernet module (see Pt. 2 section 20).
This feature enables a generic strategy to be downloaded to several controllers, which may then have their individual
Lan/Node address, Supervisor Port Address, and IP address set up after the download (e.g. using IPTool). It is also useful
if these settings are not known at the time of writing the strategy or if these settings have already been configured using
IPTool.
Note that if the settings have been included in the download and are different to those previously made (e.g. using
IPTool) then when the file is downloaded the address parameters will change to those included in the file.
These ‘Not Sent’ settings are indicated in the .IQ3 strategy file name:
Lxxxnyyy.I.A.U.IQ3
These are referred to as <file info> in the rest of the manual. e.g. Lxxxnyyy<file info>.IQ3
where:
I indicates that the file contains the IP Address (and Subnet mask, UDP port, Router 1)
A indicates that the file contains the Local Lan and Local Node address
U indicates that the file contains the Supervisor Port Address
so a file which excludes these addresses will have the name:
Lxxxnyyy.IQ3
.IQF This is a binary format file which is used to upload from and download to IQ1xx and early IQ2xx controllers.
It is uninterpretable (e.g. by SET).
.LDF This is a strategy download file from SET to IQ1xx and early IQ2xx controllers.
.IQ2 This is a text communications format strategy file used to upload from and download to IQ2xx v2 (and
greater) controllers. It is interpretable by SET.
.IQ3 This is a coded form of strategy file used to upload from and download to IQ3 controllers. It is interpretable
by SET.
.IQ3 format files are the only strategy files used by IQ3 controllers.
The .IQ3 strategy file has to be created from the SET strategy file before the download. This can be done by selecting
‘Strategy/Create IQ3 file’ in SET, or as part of the download process as described in 6.2.1 below.
SET will automatically enter the Site Name, Lan number and node address from the IQ’s address module details, and
increment the Strategy Revision number.
The connection shows the connection details entered when the project was created (although they can now be edited
if required).
If security is set up in the controller the User Name, Password, and PIN must be set up correctly. They must match a user
name, password, and PIN set up in the controller, and must be set to level 95 or greater.
Clicking on OK will create the .IQ3 download file, zip up the backdrops file to create Lyyynxxx.backdrops, zip up the
language files to create Lyyynxxx.languages and store with the files in the download directory. The IQ3 file download
dialogue box is then displayed.
This shows the selected strategy file and the User Name and Password as set up previously.
This box enables the download of any combination of the following files:
Note that only the IQ3 strategy file can be downloaded over a current loop Lan (i.e. to an IQ3/LAN). If other types of
configuration files are selected, they will be ignored.
A strategy file for one controller may be downloaded to a different controller. The controller specific information in the
address module (i.e. Identifier, Lan number, node address, IP address, and individual languages, and Ethernet settings
described in Pt. 2 section 20), may be deselected in SET, so that they are not downloaded. A generic strategy file can
thus be downloaded to several controllers, and their controller specific information then set up appropriately.
Note that vCNC settings are also controller specific, but are not included in the strategy file. The vCNCs can only be
set by IP Tool, and are not download by SET (an uploaded file does contain vCNC information but it will be ignored by
the controller when it receives a download).
Note that to download a single file to multiple controllers or different files to multiple controllers the .IQ3 file,
backdrops, language, XNC files must have been created first.
This can be done as per the first part of the single file download described above, or by displaying a strategy page
and then selecting Strategy/Create IQ3 file. Files created in this way will be in the C:\Set Projects\Project Name\Download
directory.
It is also possible to download files which have been uploaded from controllers. These will be in the C:\Set Projects\Project
Name\Upload directory.
The file transfer dialogue box is obtained by right clicking on the site.
The controllers on the site are listed in the System View. They can be added to the Devices List by right clicking on them
and selecting ‘Add to Devices List’. The target devices are then selected from the Devices List in the above dialogue
box by clicking on them (to highlight) or by using the Select All button.
As before security can be set up by entering User Name, Password, and PIN.
This dialogue box also allows selection of which files to download from .IQ3 file, backdrops, language, and XNC (for
IQ3/XNC only) files. The file list should show ‘.IQ3’ and the required file to download is highlighted by clicking on it
in the file list .
If the download is to occur over the current loop Lan then click on ‘Use IQ3 Lan (IQ3 v1.3>)’. Note that only the .IQ3
file can be downloaded over the current loop Lan (IQ3/LAN only), and the other file types will be greyed out.
This procedure is the same as above except, the site is selected by right clicking (not individual controllers), and the
strategy files are selected from the file list by holding down the control key and clicking on them.
Note that if security is set up all the controllers must have the User Name, Password, and PIN set up the same.
The strategy page is sent by text comms, i.e. it does not involve the download of an .IQ3 file.
Note that within the IQ3, the strategy file corruption recovery process may require recourse to the original downloaded
strategy file, so changes covered by the strategy page download could be lost (see 6.5).
The strategy page download is selected by the page download icon on the icon rail .
The connections details dialogue box, also used for strategy download to a single controller (see above), is displayed.
The user should check or set the controller location (Site name, Lan number, node address), security (User Name,
Password), and Site connection details. Selecting OK will start the page download.
.IQF This is a binary format file which is used to upload from and download to IQ1xx and early IQ2xx controllers.
It is uninterpretable by SET.
.SCN This is a file which is uploaded by SET for IQ1xx or IQ2xx controllers and used to compare with the .IQ
strategy file.
.IQ2 This is a text comms format strategy file used to upload from and download to IQ2xx v2 (or greater). It is
interpretable by SET.
.IQ3 This is a text comms format strategy file used to upload from and download to IQ3 controllers. It is
interpretable by SET.
This will cause the Connection Details dialogue box to be displayed (see above). The user should check or set the
controller location (Site Name, Lan number, node address), Security (User name, Password) and Site Connection details.
Selecting OK will cause the IQ3 file Upload Dialogue Box to be displayed.
This shows the selected filename, and the User Name and Password set up above.
This box enables the upload of any combination of the following files:
IQ3 Strategy file
Backdrop files
Language files
Selecting the Start button will cause the upload to commence. The files will normally be uploaded into the Upload directory
within the project directory, unless the path has been changed.
The upload file name is Lxxxnyyy.IQ3 by default and it will contain all the excludable parameters (see 6.1.5 above).
However, if the uploaded file were to be downloaded, it would not write the excludable parameters into the controller,
as the <file info> is set to exclude their download. If these are required to be downloaded, the file should be imported
into SET (File/Import IQ3 File) and the .IQ3 file modified by SET to include the file info characters (I.A.U) by clearing
the ‘not sent’ boxes in the Address module.
The controllers on the site are listed in the System View. They can be added to the Devices List by right clicking on them
and selecting ‘Add to Devices List’. The target devices are those selected from the Devices List by clicking on them (to
highlight) or by clicking on the Select All button.
As before security can be set up by entering User Name, Password, and PIN.
Note that if security is set up, all the controllers must have the same User Name, Password, and PIN.
This dialogue box also allows selection of which files to upload from .IQ3 file, backdrops, language, and XNC files. The
file list should show ‘.IQ3’.
If the upload is to occur over the current loop Lan then click on ‘Use IQ3 Lan (IQ3 v1.3>)’. Note that only the .IQ3 file
can be uploaded over the current loop Lan (IQ3/LAN only), and the other file types will be greyed out.
Backward engineering: This enables a lost SET strategy file to be recovered, so that the strategy can be documented
and modified using SET.
Comparison: This enables the uploaded file to be compared with an existing strategy file in SET, to check for differences
(e.g. changes made to the controller using web pages), and if required to update the SET file to reflect the changes.
This points to the upload sub-directories for the selected project. Select the required file, and select open.
SET will import the file, create the controller, and put the strategy file in the correct location. Once the process is completed
SET will display the last strategy page.
Note that To Connectives are not produced on the strategy pages, although the module inputs are specified correctly.
The To Connectives must be redefined on the source module page. Note that Connectives (From Connectives) are fully
restored.
Note also that some modules may overlap and require the modules to be moved slightly to tidy up the page.
6.4.2 Comparison
This process involves:
Upload strategy file from controller to SET.
Compare with existing strategy file.
The upload process is described above.
This will display uploaded files from the current project (the user can navigate to another directory if they wish). Select
the required file and Select ‘Open’. The following dialogue box will be displayed.
Backup Database: this will backup the SET strategy file (creates Lxxxynnn.BAK). If Update Database is also selected,
the backup will be completed before the update so that if the updated file is unacceptable, the backup file could be restored.
Print Report File: this prints the report file which lists the differences between the SET strategy, and the file to be
compared. The report file will still be created if none of the options are selected. The report filename has the format
Lxxxnyyy.rep and is placed in the directory containing the strategy file, i.e. C:\Set Project\Project Name\Lanxxx.
After a Compare, the differences between the controller and project NTD (Non-Trend Device) modules have to be
resolved; this can be done using the dialogue box that will pop up (see Pt. 2 section 21.4.2).
Select the SET strategy files by displaying the Device View, and clicking on the little square adjacent to each controller
to select each device; this will place a blue tick in the required squares.
Select File/Compare and the Compare and Update dialogue box shown above is displayed.
After a Multiple Compare, the differences between the controller and project NTD (Non-Trend Device) modules have
to be resolved; this can be done by right clicking on a strategy page for each controller and selecting IC Comms/Show
NTD List (see Pt. 2 section 21.4.2).
This is done by opening the project, displaying the Device View, and selecting File/Import Backdrop File. The following
dialogue box is displayed.
This points to the upload sub-directory for the selected project. Select the required file, and select open.
SET will import the backdrops in the file into the backdrops directory of the current SET project.
A dialogue box will indicate the progress of the process, and when it is completed.
The IQ3 stores it strategy file, and any backdrops, languages, and XNC files in non-volatile memory (Flash).
An attempt to download a BACnet strategy file to a non-BACnet controller or an XNC strategy file to a non-XNC controller
will fail, and the Program module, Program State parameter will be set to ‘Feature Error’.
From time to time it stores back the strategy file. When it does so, it copies the Running.IQ3 file in Flash to Running.bak
in Flash first (so there is a second level backup), and then stores the file being executed in RAM back to Running.IQ3
in Flash.
When SET does an upload it will request the IQ3 to perform an archive before the upload and will then upload the strategy
file from Flash, so that the uploaded strategy file should be the latest.
It is good policy to perform a download after an upload to reset the Lxxxnyyy.IQ3 file to the new file in order to stop the
old file being loaded into RAM under fault conditions as explained in 6.5.2 above.
Resetting will clear down the strategy files and the XNC application file. This will set the following to defaults: Lan number,
outstation address, IP addressing mode, IP address, subnet mask, UDP port, identifier, Router 1, remote Trend devices,
vCNC. It will clear down all user modules (passwords, PINs etc), alarm logs, and plots. It will leave the Time and Date
at their current settings. It will not clear down the backdrop or language files
After the reset the IQ3 should be reconfigured from scratch and the strategy downloaded as explained in Pt. 1 section 5.1.
When upgrading controllers in this way, everything in the controller except the firmware, alarm log, and plots is backed
up. The strategy is then removed from the controller while the upgrade takes place. The files used for the upgrade are
obtained from a specified directory on the PC known as the ‘Autosetup’ directory. Once the upgrade is complete the
strategy will be copied back into the controller and restarted.
It is possible to stop the strategy being copied back by clearing the Restore Strategy to Controller after Upgrade check
box in the Advanced Settings dialogue box.
The backed up information is stored in a directory known as the ‘Backup Root’ directory. The information for each
controller is stored in its own uniquely identified directory within the ‘Backup Root’ directory according to the structure
shown below:
Caution
Because of the nature of the upgrade process, if the controller loses power during the upgrade process the upgrade
will fail and the controller may no longer function and will need to be replaced.
It is not possible to upgrade the controller remotely over an IP connection that uses a dial up modem router. Upgrading
the controller requires a high integrity IP link to the controller as loss of connection could leave the controller in a
state where it is not controlling the plant. For this reason remote upgrading is not recommended, and upgrading over
a dial up modem link is not supported.
The process of upgrading controllers with pre version 1.01 firmware can be unreliable. If you experience problems
upgrading these controllers it is recommended that you use a crossover adaptor to connect directly to the controller
(see Pt.1 section 4.2.8).
The upgrade process will cause any plots and the alarm log to be lost, so if this information is to be saved, the logged
data can be recorded using a 963 or other suitable tool, and all the pending alarms can be sent to a supervisor.
The update file is supplied as a zipped autosetup file and it should be unzipped into an empty directory on the PC which
should be specified as the Autosetup directory.
Using the SET System View, right-click on the controller that is to be upgraded, or the Lan containing controllers that
are to be upgraded and click Upgrade Controller. The TsetIq3Upgrader Warning dialogue box is displayed.
This enables the Username and Password to be entered in order to authorise the upgrade. This must match with one
in the controller and be of level 90 or above to enable the upgrade. If there are no users set up in any of the controllers
that are to be upgraded a username and password is still required if this is the case use ‘IQ3’ as the username, and ‘user’
as the password.
For controllers with version 1.3 firmware or greater a PIN must be entered in the Pin box. This must match with one in
the controller and be of level 90 or above to enable the upgrade.
Note that if more than one controller is being upgraded, only one username, password, and PIN can be specified; if the
controllers have different usernames passwords and PINs, the process will fail. It is therefore recommend that all the
controllers on a system have the same username, password, and PIN.
The box enables the Connection Speed, the Backup Root directory (see above), and the Autosetup Folder (this contains
the new firmware an other associated files) to be specified .
The Enable Advanced Settings check box should be disabled.
By clicking OK the IQ3 Upgrade Window is redisplayed.
If other controllers are to be upgraded they can be selected from the SET System View and dragged onto the IQ3 Upgrade
Window (clicking Clear List, clears the list).
It is recommended that initially you only upgrade one controller at a time until you are confident that the upgrade process
will complete successfully, and not cause any problems.
The Ethernet connection can be checked with each of their selected controllers by clicking Check Comms. Each of the
selected controllers will then be pinged to check that it is there.
The upgrade can be started by clicking Upgrade, and confirming that you wish to proceed.
Note that if any of the controllers being upgraded has pre version 1.01 firmware an additional warning box is displayed.
This warns of the problems that may be encountered upgrading pre version 1.01 controllers described above.
The upgrade will be carried out the progress of which is displayed in the progress bars in the Controller List and at the
bottom of the window. Clicking Abort stops the upgrade process. If a controller is in the process of being upgraded that
upgrade will be completed before the process is aborted.
After the upgrade, the upgraded controllers should be checked to see that they still communicate by deleting the
internetwork from the System View and then refreshing the entire Lan structure.
Each upgraded controller should be checked to confirm that the version number reports as expected on the web pages
and that the strategy and backdrops are in place.
The Trend Custom Language also enables additional controller functionality to be created that may be used to enhance
the strategy without recourse to a 3rd party system.
TCL is used to produce the TCL application. TCL applications are created by Trend Interface Specialists (TISs) who
can provide both bespoke applications and generic applications for commonly used equipment. The TIS may provide
the application in soft format, or pre-loaded into the IQ3. The application can be tied to one controller or available for
general download. Information about the TISs can be found on the Trend Partnernet website.
A security mechanism prevents applications written by a TIS from being used without the TIS’s authority. The TCL
application is encrypted to protect the source code. The application may be designated to run on any controller, or to
run on a particular controller (identified by its MAC address). The on site commissioning engineer is able to request
an unlock code from the TIS for a particular MAC address. The controller will check that the MAC address embedded
in the TCL application file matches its own MAC address before running the TCL application.
The device part (standard IQ3 firmware) consists of a number of standard IQ configuration modules, and operates in
exactly the same way as a standard IQ3 controller. These modules can be linked together to form a strategy in the normal
way and the strategy may be used to manipulate the data from the 3rd party system.
The XNC part runs a Trend Custom Language program (TCL application). It communicates with the 3rd party system,
passing information from the IQ3 to the 3rd party system, and writing values from the 3rd party system to the IQ3. It
can also communicate directly with IQ system devices. Communications with both 3rd party system and IQ system
devices may be by means of Ethernet, current loop network (if /LAN/.. option fitted), or RS232/RS485 (if /SER/.. option
fitted).
The XNC part (TCL application) is configured using TCLTool2 which runs within SET. This creates the XNC program
file which can be downloaded using TCLTool2 or SET itself.
TCLTool2 also creates an XNP file which defines the inputs and outputs required by the TCL application.
The device part of the IQ3/XNC uses the standard IQ3 configuration modules plus the XNC interface module which
are configured using SET. SET can import the XNP file and use it to populate the XNC interface module; the connections
between the other strategy modules and the XNC interface module are then made using SET and become part of the
strategy file. SET can download the strategy file to the IQ3 and can also upload the strategy file for backup purposes.
Note that the XNC program file should be downloaded before the strategy file is downloaded.
The strategy file and other configuration files (language, backdrop, and XNC) can be downloaded and uploaded across
Ethernet, but only the strategy file can be downloaded or uploaded through the current loop Lan (IQ3/LAN only).
vCNC. In order for the vCNC to operate, it must be configured using IPTool. The vCNC will normally be a
member of an Ethernet Lan, but for IQ3/XNC/LAN it will be a member of a current loop Lan.
Serial port (if /SER/... option fitted) set to either RS485 2 wire, RS485 4 wire, or RS232.
Note that although the TCL application may switch between RS232 and RS485 communications, only one of these
ports may be connected at one time in order to comply with Class B EMC emission standard (EN61000-6-3,
residential, commercial, and light industrial environments)-see note Pt. 1 section 4.6.
Note that the TCLTool2 and its documentation are only supplied to an individual on completion of the TCL training
course, and after signing an agreement to become a TIS.
TCL
Application
Outputs
Inputs
Communications
TCL Application:
This is the TCL code that has been written for the required application using TCLTool2. It obtains information
by reading from the inputs, stores, non-volatile data areas and by communicating with 3rd party systems. It
processes the information and updates the outputs and sends data by communications to 3rd party systems
and/or IQ system devices.
Stores:
These consist of up to 200 locations where user-defined constants are stored. They are defined using TCLTool2
when creating the TCL application and cannot be changed from the running application. They are re-
initialised after power failure.
SavedVars:
This consists of up to 100 locations where values, that may be written to and read from by the TCL application.
Their data will not be lost due to a power interruption.
Inputs:
These consist of up to *1000 points that can be connected to IQ3 module outputs using SET. They enable
the TCL application to use strategy values and labels.
Outputs:
These consist of up to *1000 points that can be connected to IQ3 module inputs using SET. They enable values
and labels from the TCL application to be used by the strategy.
Communications:
These are as defined above (Ethernet, RS232/485, or vCNC) and enable information to be read from and
written to 3rd party systems and IQ system devices.
*Note that there can only be up to a total of 1000 inputs or outputs taken together (e.g. 300 inputs and 700 outputs).
TCLTool 2 creates the XNP file which contains the reference to the TCL Code path, and details of Inputs, Outputs, and
Stores. During configuration using SET, the XNP file is uploaded into the XNC Interface module; the file’s data is used
to populate the parameter fields (Inputs, Outputs, default labels, values, and authoring details).
TCLTool2 also creates the XNC file which is the TCL application file for downloading to the IQ3.
This box enables the input and output links to be made. It facilitates links to knobs and switches (inputs) and sensors
and digital inputs (outputs). These can be added to the XNC Interface dialogue box and then dragged onto the required
XNC Interface module input or output. They also appear on the connectives list - see 7.2.3 below.
The inputs’ and outputs’ labels and values can also be changed from the dialogue box.
The Stores are displayed (each store has a number, name, and value), and the values (strings) may be changed.
The Re-load button can be used to return the inputs’, outputs’, and stores’ labels and values to their settings within the
TCL application.
The Application name, Version, Author, and ID are read only from the TCL code.
Alarm Labels 1 through to 6 are used by the TCL alarm generation function as the alarm description of each alarm. They
can be entered into the dialogue box from SET
In the above part of the connectives list, t1I1V is XNC Interface module (t1), input 1 (I1), value (V) and can be linked
to any output (analogue or digital) of any IQ3 strategy module.
Similarly t1O1V (TCL module output 1 value) can be linked to any input (analogue or digital) of any IQ3 strategy
module.
The data shown by this web page is described above in the XNC Interface module except for Program State, and Debug
Active which are both used by the TCL code programmer to debug the code.
Alarm Reporting Lan ,and Alarm Reporting OS are set up automatically by the TCLTool2 when debugging the
program so that any errors are reported to the TCLTool2. On completion the tool will clear these down.
The XNC Interface module consumes 130 brIQs, and the TCL application consumes brIQs as follows:
5 brIQS :per store location, non-volatile data location, input point, output point
20 brIQs :per line of TCL code
• Supervisor and Displays have methods of logging on a user with a particular set of access rights. The supervisor/
display needs to have the controller PIN set up so that if the user has access to that controller the correct PIN will be
used.
• Autodialling is protected by autodialler passwords that are set up in autodiallers that need access to each other.
• SET has its own system of users and access rights, but communication with an IQ3 requires entry of the IQ3 PIN.
The IQ3 security is supported by its user modules. By default no user module is set up, so when the first module is created
it must have access to all areas, by having a maximum user level of 99. Further user modules can then be created giving
restricted access.
The User name and Password are used for access to web pages, and Strategy File upload.
The PIN is used for most supervisor/display access, and SET Live Values/Live Edit. It is also used for inter controller
communications.
Note that Strategy File download requires User name, Password, and PIN.
The user level defines which parameters a user can adjust, and what can be seen on web pages. The user module also
specifies the home web page, and the web pages that the user can access (View Defaults). They are split into the following
categories: Alarms, Time Zones, Modules, GraphIQs Pages, GraphIQs Navigator.
Adjustment of knobs, switches, and time zones requires a user level defined separately in each module, so that adjustment
of knob 1 could be at a different level to adjustment of knob 2.
The levels are shown in the user module section (Pt. 2 section 34).
The user name ‘Guest’ has a special function. If a user module is set up with user name Guest (note the it must be a capital
‘G’, and lower case ‘uest’) and no password, then when a user accesses the IQ3 web pages without logging in, he will
be given the status of Guest, and whatever level is set for ‘Guest’. The Guest user module can also have a defined home
page and defined access to classes of web pages (View Defaults).
Note that if a Guest user is set up without a password, or if any user is created with with a password less than 99, it will
not be possible to download strategy files unless there is also a user set up with a password =>99. It is recommended
to always create an Administrator user with level 100, before creating any other users. If you try to create a first user
without a password =>99, SET will give the operator a warning.
This enables the designer to configure a user level for the casual visitor to web pages, and limit him to certain parts of
the site.
Summary:
If a user accesses web pages and selects login, then he is able to enter a user name and password. It must match that
set up in a user module and he will be given the user level of that module.
Once the user has finished he can logout to prevent unauthorised changes (although the login will time out automatically).
Web pages may also be accessed by Mobile smart phones (Windows Mobile 2003 Second Edition), and PDAs (Windows
CE4); note that Mobile smart phones and PDAs cannot display graphs and right to left languages
Note that the operating system environment in which Internet Explorer runs must support Java; A Sun Java runtime
environment J2SE5.0 or greater can be downloaded from Java.com.
Module parameters may be monitored and changed using web pages but module creation, deletion and linking can only
be done using SET.
The IQ3 is provided with a standard set of web pages which covers all accessible modules. Graphical display pages
(GraphIQs) which are configured using IQ3 display and directory modules, can also be accessed.
For further details of web pages see the IQ3 Web User Guide, TC200631, and the IQ3 Graphical Display Pages Editor
Manual, TE200629.
banner
Note that an
IQ3xact will have
the appropriate
logos shown here
The user will automatically be given the status of ‘System Guest’ or Guest and an appropriate user level that will restrict
access to the IQ3 according to its security set up in the user modules (see Pt. 1 section 8.2).
All the standard web pages have the banner across the top. The full banner carries buttons for:
Login, Alarms, Time Zones, Modules, and GraphIQs
However, the Alarms, Time Zones, Modules, and GraphIQs may be removed from the banner if the View Defaults for
‘System Guest’ or Guest have ben changed from the default.
If no user modules are set up the user will be a System Guest with access to everything (user level = 100).
If the user modules are set up the User may login (see 9.2 below).
9.2 Login/Logout
The user can log in with a User name and Password. These must match those set up in a user module in the IQ3. The
module will also have a user level set up which defines the modules that can be accessed (see Pt. 1 section 8.2).
Once the user has logged in, the login button changes to ‘logoff’ enabling the user to log off to prevent unauthorised
changes (although the login will timeout automatically).
The user module has a parameter ‘home page’ which defines the page which will appear when the user has logged in.
This may be one of the IQ3 standard web pages, one of the GraphIQs pages or any other HTML page (e.g. company
website page). If this has not been set up the Welcome Page is re-displayed.
CAUTION
The browser may enable the user to save the password in the browser’s
password list. If this is done anyone accessing the IQ3 from that PC will
be automatically logged in at that password’s user level.
If a password is forgotten, the ‘Forgotten your password? Click Here’ should be selected and a password key will be
given. This can be used to contact Technical Support to obtain a new password.
9.3 Modules
Selecting Modules from the banner produces the module type selection buttons down the left hand side of the screen.
The actual module buttons shown depend on the current password level. (A password with level 80 or above will give
a full list of module types).
Clicking on a module type selection button will produce an overview list of all the modules of that type from which a
particular module may be selected to view its parameters, and, if authorised, to change them.
This page can have a number of standard buttons allowing further access and adjustments:
: The refresh button in the top left of the banner will cause current values to be refreshed.
: The OK button sends changes to the controller. Values can be changed by highlighting them then typing
in the new value and selecting . If the write of values to the controller was OK, the ‘Value Write
SUCCESS’ statement will appear across the top of the display.
: The graph buttons will display a graph of the adjacent module’s output
It is possible to plot an output at different periods; each plot will be shown on a separate line on the display:
: These buttons enable previous and next parts of the list to be accessed.
: This will refresh the list starting from the number entered in the square.
The line in the module overview page will change colour according to the module’s status:
Red: In alarm
Grey: Disabled
Orange: Overridden (also HOA (Hand/Off/Auto) driver module overrides, i.e in Hand or Off.
The picture below shows the overview of a sensor in alarm
go to destination arrow
In the case of the knob shown here, the label, value, units, PIN level, and top and bottom of range can be changed, but
the destination, page, and x, y coordinates cannot be changed.
Module destinations and sources can be clicked on to jump to the details page of the destination or source module. This
is done by clicking on the connection arrow, but for destinations, the particular destination can be selected from a drop
down list before selecting the arrow.
in list
Go to destination
Got to source
top of page
Previous and next modules (in this case gives knob 2)
9.4 Graph
The graph page gives a graph of the values in the plot module, and a spot value which can be moved along the graph
trace.
A section of graph can be enlarged by the zoom feature (left click and drag). Right clicking allows selection of ‘Zoom
to original’, and a ‘Show trace value window’. With the trace value window selected, as the point is moved along the
graph its point value is displayed (as shown in picture above).
When viewing a web page graph the times may appear to show the incorrect time, this could be due to the UTC offset
parameter not being set up correctly. The UTC offset parameter in the time module must be set up correctly to reflect
the current offset from UTC that the controller is operating in (see Pt. 2 section 32.4).
The list of values used to create the graph (see below) can be seen by selecting the list tab.
9.5 GraphIQs
GraphIQs pages are bespoke web pages that enable defined values to be displayed against a graphical backdrop.
They can be created with a defined navigational hierarchy, and the items displayed can be role specific dependent on
the user’s password level.
The pages can have URL hyperlinks to other web pages , and displayed values can have hyperlinks to their modules’
details pages (see 9.3.2 above).
Navigator
Static
Display Item
Backdrop
Dynamic
Display Item
The display items are either static or dynamic. Static items are for labels and units, and dynamic items are for values from
the controller.
The pages are created using SET, and there is a special Graphical Display Page Editor applet within SET which facilitates
the editting of the individual pages.
On the left side is a table of Display Items which may be used for dynamic display items. This consists of all the
‘presentation’ modules:
Sensors
Digital Inputs
Knobs
Switches
Drivers
Time Zones
The filter buttons below this enable selection of the types of items to be displayed.
The central box is the display and directory view which will show the top level page by default. The ‘P0’ against it refers
to the default password setting of zero.
The individual pages are defined by directory modules, and the page shown is directory module 1 which is always the
root (top level page).
Another page can be created by right clicking on the top level icon and selecting ‘Insert Directory’. This 2nd page will
then have the root as its parent. By right clicking on the second level page a third level page can be created which has
the 2nd level page as its parent and so on.
This process enables the GraphIQs navigator to be created. The label of each directory module should be set up by right
clicking on the icon, selecting ‘Edit Parameters’ and entering the Title.
This will create the following navigator in the display and directory view:
Static items can be added by right clicking on the directory and selecting ‘Insert Static Display Item’. A label can then
be entered that will appear on the GraphIQs page.
The combination of display and directory items will be displayed in the Display and Directory View.
Root
GraphIQs page
level 3 Static Display items
This will show all the display items on that page against a background grid.
AHU1
Selecting ‘Change’ Backdrop will enable a backdrop bitmap to be selected for the web page.
Backdrops can be either .JPG or .GIF files. SET allows a maximum backdrop size of 200 kbytes, and a maximum capacity
for all backdrops of 2 Mbytes; it will warn if a backdrop exceeds 100 kbytes.
Once the backdrop is selected it will appear in the GraphIQs Editor. Each individual display item can then be moved to
its required position by left clicking and dragging it to its new position.
The URL for the web page can be entered by clicking on ‘Change’ Link Reference.
The URL type should be selected from the following types:
Email Link: This should be set to an email address (e.g. [email protected]). When the static item is selected, the
computer’s email application will be loaded with a new email with this defined email address set up.
Directory Link: This is for a link to one of this controller’s web pages.
Link type Enter
GraphIQ page trendModule: GraphIQs/<Directory Module Structure>.htm
Where <Directory Module Structure> is the path to the directory module that
defines the page.
e.g. trendModule:GraphIQs/Boiler/Boiler1.htm
Module List page trendModule: <Module Type>.htm
Where <Module Type> specifies the type of module using its module identifier
(e.g. S specifies sensor).
e.g. trendModule:S.htm
Module Details page trendModule: <Module Type><Module Number>.htm
Where <Module Type> specifies the type of module using its module identifier
(e.g. S specifies sensor), and <Module Number> is the module number.
e.g. trendModule:S1.htm (for sensor 1 details)
Welcome page Index.htm
Module page Modules.htm
Alarm page Alarms.htm
Diagnostic page ^.htm
A hyperlink to the module details page can be created for a dynamic display item. In the example in 9.5.2 above right clicking
on ‘Space Temperature xx.xx DegC’ and selecting ‘Properties’ will display a Styling Dialogue box of the type below.
Clicking on ‘Make a link to the item’s detail page’, and selecting OK will set the hyperlink.
These can be viewed non-graphically. This is the traditional way of viewing the display and directory modules as it was
the only way of viewing those from IQ2 controllers.
Supervisors and displays (IQView, 963, 916, SDU) use this non-graphical way of displaying the display and directory
modules.
When displayed non graphically the parameters which refer to graphical display features are ignored
The 963 will show the directory structure in the Device View, and the display items are shown in the Data Display area.
In order to view the Display and directory modules the SDU has to be configured to operate in a Display and Directory
Mode. In this mode it will show the first directory by default (or the Home page). Scrolling through the directories and
selecting the required directory module will show the first display item. This produces a display like that below.
Directory label
Office Area
Front Office Setpt
20.3 DegC Display item label
live values
right click,
Edit Parameters
right click,
Edit Parameters
The Live Values feature facilitates commissioning and fault finding on the ‘live’ controller.
It is possible to have live values from two controllers appear on the SET panel enabling the effect of inter-controller
communications to be monitored.
Note that when using this feature, changes made to knobs and switches may affect the plant to which the controller
is connected; used incorrectly it could result in damage to plant or injury to people.
To see the effects of the strategy changes on the strategy page the Live Value feature may also be selected . Using these
two features together enables any strategy design faults to be detected, modified, and the effects of the changes observed.
It is possible to have live values from two controllers appear on the SET panel enabling the effect of inter-controller
communications to be monitored.
Note that when using this feature, changes made to the strategy may affect the plant to which the controller is
connected; used incorrectly it could result in damage to the plant or injury to people.
The method of running Live Edit is similar to running Live Values described in Pt. 1 section 10, but the Live Edit icon
should be selected in steps 5, 6. Also module strategy changes require password level 90 or greater.
A useful feature of Live Edit is a module output override. For this to operate Live Values should also be selected and
the outputs that can be overridden are shown in cyan on the strategy page. The override is selected by double-clicking
on the module’s output and entering the required output value, or status into the dialogue box. This will disable the
module and set its output to the new value or status which will be picked up by modules linked to the module’s output.
Any module that is overridden is shown in red on the strategy page.
Click on ‘cyan’ output.
Produces dialogue box.
Change state, click OK.
When the override is no longer required, the output should be clicked on again and the disable module facility deselected
followed by OK.
If the modules are left overridden, on completing Live Edit a warning will be given enabling all modules to have their
overrides removed.
Note that the Live Edit override feature uses the module disable parameter described in Pt. 1 section 5.7. If this is connected
to another module’s output, and Live Edit output override is used, this could result in the module being enabled again,
and its output overwritten as the source module is serviced.
Note that the Address module Override Timer (see Pt. 2 section 2.3.9) can be set after applying an override. The timer
will count down and automatically remove any overrides after the time has expired. If the timer is left at zero there is
no automatic action. The timer action does not apply to overrides that are sourced from other strategy modules.
General Alarms and Item Alarms are sent to the alarm destination via group, route and destination modules and are stored
in the alarm log. They can be sent in either text, coded, or attribute format.
Item alarms may be individually disabled (i.e. on a per item basis). Both item and general alarms, are gathered into groups
and the groups may be individually disabled. Both these methods stop the alarm being reported, but the alarm condition
still remains (i.e. the alarm bit is set). The only way to affect the alarm condition is to alter the alarm limit or required state.
Item alarms have digital outputs which are available to be used in the strategy.
It will transmit the alarms to any supervisory device connected either via its supervisor port (RS232) or via its vCNC and
Ethernet.
Note that the IQ3 virtual INC does not have configurable local and remote alarm target addresses (unlike the INC2,
which does have these parameters). This means that IQ3 local network alarms cannot be sent to a remote alarm target
address, and IQ3 internetwork alarms cannot be sent to a local Lan alarm target address.
PC D1 PC D2 PC E1 PC E2
IQ3 D IQ3 E
RS232 RS232
IQ3 IQ3
control control
vINC vCNC CNC sCNC vCNC CNC sCNC
Lan 2
I/N
PC A1 PC A2 PC B1 PC B2 PC C1 PC C2
Lan 1
The above diagram shows 5 IQ3s. IQ3 A, B, C together form Lan 1, and IQ3 D, E form Lan 2. IQ3 B acts as the vINC for
Lan 1 and will have the lowest IP address on Lan 1. Similarly IQ3 D acts as a vINC for Lan 2 so IQ3 B and IQ3 D together
form the internetwork (I/N).
All the IQ3s have a supervisor PC connected via Ethernet to their virtual CNC (vCNC) and another connected via RS232
to the supervisor CNC (sCNC).
If a device is added to or removed from the Lan, the ‘Lan Changed’ alarm will be sent. So if IQ3 A is disconnected from
Ethernet, IQ3 B and IQ3 C will detect this as ‘Lan Changed’ and will each send it to their two connected PCs.
If an IQ3 becomes the sole resident on its Lan, it will generate a ‘Lan Broken’ alarm. So if both IQ3 A and IQ3 C were to
be removed from Lan 1, IQ3 B will generate a ‘Lan Broken’ alarm.
If a sole IQ3 detects another IQ3 on its Lan, it generates a ‘Lan OK’ alarm. So if after the ‘Lan Broken’ alarm condition,
IQ3 A were to be reconnected to Lan 1, then IQ3 B will generate a ‘Lan OK’ alarm.
Note that these alarms do not give details of which IQ3s are added to or removed from the network.
Note that local Lan network alarms cannot be sent to a remote Lan by IQ3B’s vINC.
Mechanism
When the Lan is built, each device knows the devices either side of it on its Lan arranged in IP address order, with the
Lan looping round at maximum and minimum IP address.
When a device detects one of its adjacent partners has changed, it generates a network build process which involves
all the devices on the Lan. This enables any device to detect the Lan Changed condition.
So if a device were to be added to the internetwork (IN), then both IQ3 B and, IQ3 D will report ‘Internetwork Changed’,
and similarly they will report the same alarm again if the new device were to be subsequently removed.
If IQ3 D were to be removed, then IQ3 B will become the sole device on the internetwork and will generate ‘Internetwork
Broken’.
If IQ3 D were to be reconnected after the internetwork broken condition above, then IQ3 B will generate ‘Internetwork
OK’.
Note that these alarms do not give details of which IQ3s are added to or removed from the network.
Note that internetwork network alarms cannot be reported to the connected Lans by the IQ3s vINC.
So if PC B1 were to be disconnected from IQ3 B, then IQ3B will generate a ‘Device Dead’ alarm to PC B2, and similarly
vice versa (if PC B2 were disconnected it will report to PC B1).
If a local device which was ‘Device Dead’ were to be reconnected, then the IQ3 will generate a ‘Device OK’ alarm.
So if PC B1 were to be reconnected to IQ3 B, the IQ3 will generate a ‘Device OK’ alarm to PC B2.
These alarms are only reported to the IQ3’s local connected device.
If IQ3A and IQ3B have the same device address on the Lan, then when the network is mapped both IQ3A and IQ3B will
generate a ‘Duplicate Address’ alarm.
If IQ3 B and IQ3 D have the same Lan number on the internetwork, then when the internetwork is mapped both IQ3 B
and IQ3 D will generate a ‘Duplicate Lan’ alarm.
These alarms are only reported to the IQ3s’ local connected devices.
Mechanism
When the network is mapped, the mapping message is passed around the network as a visitor message. As explained
above each device on the network knows its adjacent partners’ IP addresses, and when it receives the map message from
one partner it adds its own address and passes it on to the next partner. If an IQ3 discovers its own address in the mapping
message it generates a ‘Duplicate Address’ alarm.
Generated at power up if an IQ3 is not alone on local Lan or if it can communicate with another device on the local Lan
after a network broken alarm has been reported.
Generated if an IQ3 detects another device has been added to or removed from its local Lan.
Generated when an IQ3 acting as a virtual INC finds itself alone on the internetwork.
Generated at power up if an IQ3 acting as virtual INC is not alone on the internetwork, or if it can communicate with another
device on the internetwork after an internetwork broken alarm has been reported.
Generated if an IQ3 acting as virtual INC detects another device has been added to or removed from the internetwork.
Generated if a device connected either to the vCNC or the RS232 port which has been communicating ceases to
communicate.
Generated if a device connected either to the vCNC or the RS232 port which has ceased to communicate, starts to
communicate again.
Generated if the IQ3 detects another device on its local LAN with its own network device address.
Generated if an IQ3 acting as a vINC detects another device on the internetwork with its own network Lan number.
Generated if an IQ3 detects a node on the network which is sending messages but not receiving them. The characters
‘xxx.yyy’ will be the last sets of numbers in the deaf node’s IP address.
CODE TEXT
These alarms are described in detail in the Address module (Pt. 2 section 2). Currently only CONL, HELP, STOR, FRTC,
FARC, FLER are operational.
General alarms are sent to their destination(s) via group, route and destination modules.
All the general alarms are grouped together in the General Alarm Group which is set by default to group 0 (not sent).
If left in group zero they still get logged. For the alarms to be reported the group must by attached to a group module
(group module 1 onwards), and the group/route/destination module strategy must be set up (see below).
The address module alarm bits are available as connectives to be used in the strategy
The plot module BBUF alarm is considered an ‘Event’ rather than a true alarm, and does not have a corresponding clear
alarm.
Item alarms are sent to their destination(s) via group, route, and destination modules
(1) When the main module (e.g. sensor) detects an alarm condition it starts the alarm timer (Time in Alarm
(secs)).
(2) When the timer exceeds the alarm delay (Alarm Delay (secs)) the Alarm State is generated.
(3) If the alarm is Enabled the In Alarm state is set and the alarm is passed on to the group module (Alarm Sent).
(4) The Alarm Group parameter defines the group module to which the alarm is passed.
Alarm Sub-module
Alarm State
Alarm condition Delay
In the case of a clear alarm, it is passed immediately to the group module (i.e. independent of the alarm timer).
(1) When the main module (e.g. sensor) detects a clear alarm condition, if the alarm is Enabled and the Clear
alarm is Enabled, the clear alarm is passed on to the group module (Alarm Sent).
*Note that the Clear Alarm parameter is only present in Digital Input, Sensor, and Driver modules; for the Loop module
the Enabled parameter enables both alarms and clear alarms.
(2) The Alarm Group parameter defines the group module to which the clear alarm is passed.
Note that the alarm destination module can also inhibit clear alarms from being sent to its destination.
Alarm delays
For example the sensor dialogue box above has Delays, Enables, and Groups for all 4 sensor alarms.
The main module also has the criteria for generating its alarms. For the sensor there are the high and low alarm limits.
The other two alarms (OUTL and READ) are generated by the associated sensor type module.
3
Sensor 2 The high and low alarm limits and the four alarm delays are shown as analogue
S2 inputs to the sensor (i.e. they could either be sourced from elsewhere or could be
V
0 S
INTERNAL
internal constants). The alarm enable bits are shown as digital inputs (similarly
DegC
0
Units
High Alarm Limit
either sourced from elsewhere or internal constants). Note that clear alarm enable
0
0
Low Alarm Limit
High Alarm Delay
bits are not shown as inputs as they are constants (not connectable).
0 Low Alarm Delay
0 Out.Limits Delay
0
Disabled
Read Alarm Delay
Read Alarm
The four alarms are available as digital outputs, for use in the strategy. They can
Disabled Out. Limits Alarm
Disabled Low Alarm also be selected from the list of connectives.
Disabled High Alarm
0 Override Enable
0 Override Value
These four alarm bits are shown on the sensor module web page as Alarm State.
These alarm bits accompany the main sensor output (Value) as it is transferred to the next module.
These bits will travel through knobs, function modules, loops, and schedules without being exposed although the module
can take appropriate action if the status bits indicate that the input is invalid.
The bits are exposed by analogue sensor modules (as described above), and by analogue nodes; these modules make
the status bits available as outputs to be used in the strategy.
If the alarm bits are attached to a value, and that value is transferred by analogue IC Comms, the alarm bits are also
transferred (see Pt. 2 section 15.4.1). The alarm bits are exposed in the receiving analogue node
The Loop module can take a pre-defined sensor fail action if the input has either a Read or Out of Limits alarm (see Pt.
2 section 19.14).
The way in which a Function module behaves with respect to alarm bits on its input(s) varies with the function module
type. It may pass on the appropriate alarm bits to accompany its output. Some function modules will take action if an
input has a Read or Out of Limits alarm. This is described in detail in Pt. 2 section 14.2.4.
A Schedule module will transfer the alarm bits of the selected input to accompany its output (see Pt. 2 section 27.4.4).
alarms
filter buttons
This lists the alarms in two groups, the left hand group and the right hand group, and enables alarms to be moved from
one group to another. Initially all the alarms are in group one (except for the general alarms in group zero), so with group
one on the left, alarms can be moved into a new group on the right. The alarms shown can be filtered according to item
type by using the appropriate filter button (sensor, digin, loop, or driver).
The alarm enabled status is shown as a coloured dot adjacent to the module type (e.g. D2) and also in the relevant column
(Enabled/Disabled). The dot is green for enabled, and red for disabled. This status can be changed from this dialogue
box by right clicking on the alarm line and selecting enable or disable.
Address module alarms (general alarms) appear as type R1 (addRess module 1), and all the general alarms are grouped
together, designated by the letter G.
As the alarm reaches the destination module (via the route module) its priority is compared against the destination module
hold priority input (H).
If the priority is below the hold level it will be held. If the priority is above the hold level, it, and all held alarms, will be
sent. The destination will stay open to low priority alarms for 5 seconds after the last alarm was sent. In common with
other inputs, this parameter may either be an input or a constant; if an input it can be set by strategy; for example, this
enables the hold priority level to be lowered when comms demand is lower (say during non-occupation) to ensure that
all held alarms are sent (see also high water mark, section 13.9 below).
The group module has a New Alarm output (N) which goes true for one cycle whenever a new alarm which is attached
to the group is generated. This could be used by the strategy, for example, to turn on an annunciator whenever an alarm
occurs. If alarms are occurring faster than once per sequence cycle, the bit will be held high until one sequence cycle
after the last alarm occurred.
The route module has an Enable input (E) which enables the connection between group and destination if set to 1 (0
disables it). This allows strategy (comms, or manual intervention) to select the destination to which alarms are routed.
For example, an alternative destination can be used if the first one fails, In SET the enable input is set to 1 by default which
enables the route.
The alarm destination module enables an alarm destination to be set up. It has the responsibility to deliver the alarm to
its destination.
The destination module can only hold the one alarm it is trying to deliver (although other alarms may be waiting in a
‘stack’), and the Failed output (F) is set when the destination device fails to acknowledge the receipt of the alarm after
several retries (see Retry Interval, Pt. 2 section 3.4.2). Once the device starts acknowledging alarms, the failed bit will
be cleared, and the destination module can send another alarm.
This failed output can be used amongst other things to switch route modules to send alarms to alternative destinations
as mentioned above.
When an alarm occurs its source module places it, and its details of group number and priority, into the extended alarm
log. If the group module is not linked to a destination, then the alarm is just logged.
A group module can connect to several route modules, and several route modules can connect to the same destination
This flexibility enables groups of alarms to be sent to several destinations, and to share destinations with other groups.
o1
Alarm sent to two destinations G 1
D 1
e1
32,1
F
E 0,0
H 0
ALARM ROUTE
g1 ALARM DEST
R
H O
32,0
L
N
ALARM GROUP o2
G 1 e2
D 2 32,2
F
E 0,0
H 0
ALARM ROUTE
ALARM DEST
o6
R
g5 G 5
D 5
H O
32,5
L E 0,0
N
ALARM GROUP ALARM ROUTE
When an alarm condition occurs, the alarm source module places it in the extended alarm log which then looks at the
group module to see which routes are open. The group module will dynamically create the list of available routes
depending on which routes are enabled. If no routes are enabled, the alarm status will change to completed, and the alarm
will not be sent to a destination.
If any routes are enabled, the alarm will be sent to all the enabled destination modules accessed by the enabled routes,
which will send the alarm to the target device(s) (ignoring the effect of hold priority).
If a destination module is unable to deliver the alarm, after the allotted retries it will set its fail bit and continue to try and
send the alarm (even if the route to the destination module is subsequently disabled); this enables the resumption of
communication with the target device to be detected.
Once the destination module has received an acknowledge back from the target device, the acknowledged state in the
new alarm log record is set true for that destination module. Once all the acknowledge bits for all the destination modules
to which the alarm was set are set true, the alarm status is set to completed and not further attempts to send the alarm
will be made.
It should be understood that the destination module can be attempting to deliver one alarm, and if its receipt by the target
device is not being acknowledged, it is effectively blocked until the acknowledge is received.
(Technical note: It is possible to unblock a destination module by editing certain parameters using web pages or text
comms (e.g. SET Live Edit). The exact parameter depends on the destination type (see 12.7 below), but generally changing
it to a destination which will acknowledge the alarm allows the destination module to clear down).
The following examples describe the alarm handling operation and how it deals with delivery failure.
'
& '
$ #
"
# &
%#
! "
$
#
()
'
%!
*+;<;
$= *<* *> *<* *> *<* *>
!
?
$
"
&'
!
In this example, there is a single route, enabled by a time zone, so the route is enabled during time zone occupation. During
non-occupation alarms are logged, but not sent, as with no route open, they are considered completed as soon as they
are put in the log. If the destination is failing, it will hold the alarm it is retrying, and if during this time the time zone switches
to unoccupied, then any alarms stacked up in the log, and any further alarms will just be logged, not sent, and considered
completed. However, the original alarm will still be active until it is acknowledged. Once the destination receives its
acknowledge and occupation returns, the destination can start sending alarms again.
*
' *
$ #
"
# &
%#
! "
$
#
(&
'
%!
$= *<* *> *<* *> *<* *> ' +
!
+
#
%# ,) $
?
$
&
Q<
$
"
& # # "
V<
&'
$
<
# $
!
" # @I
QW
VW
W
W
This strategy is a development of the previous in that now there is an alternative destination during non-occupation
via a second route module (route 5). Alarms are sent to destination 4 during occupation, and to destination 5 during non-
occupation. If destination 4 is failing awaiting an acknowledge, and the time zone changes to unoccupied, then the failing
alarm will be sent to destination 5. If this is successful, any alarms stacked up will also be sent regardless of their original
alarm time.
o1
R
g1 G 1 e1
D 1 32,1
H O
32,0 F
L E 0,0
N H 0
ALARM GROUP ALARM ROUTE
ALARM DEST
o2
G 1 e2
D 2 32,2
F
E e1F
H 0
ALARM ROUTE
ALARM DEST
In this strategy, all alarms are sent to the first destination until it fails, at which point the Fail bit enables the second
destination, and the failing alarm and any subsequent alarms are sent to the second destination. Once the first destination
module receives its acknowledge, the Fail bit goes to zero., and the second route is disabled. At this point any alarms
that have been sent to the second destination in the meantime, will also now get sent to the first destination because
route 1 has never been disabled and thus during the time route 2 was enabled, those alarms had two destinations.
o6
R
g5 G 5 e6
D 6 33,4
H O
33,1 F
L E G2D
N H 0
ALARM GROUP ALARM ROUTE
Priority 0 ALARM DEST
1
o7
E e6F G2 G 5 e7
D 7 33,5
J or 21,1
F 0,0 K or F
E e6F
L or D
H 0
G 0,0 M ALARM ROUTE
ALARM DEST
H 0,0 COMB
J= e
K=
L=
M=
This strategy is a development of the previous, in that the first route (route 6) is disabled while the destination 6 is in
a Fail state. This swops the route enables so that if an alarm occurs while the second route (route 7) is enabled, there
is only one route open so it doesn’t get sent to route 6 when destination 6 recovers. Normally route 6 is enabled and
all alarms are sent to destination 6, but if destination 6 fails, the Fail bit enables destination 7 and disables destination
6, and the failing alarm and any subsequent alarms are sent to the destination 7. Once destination 6 module receives its
acknowledge, the Fail bit goes to zero, route 7 is disabled, and alarms are sent to destination 6 again.
This strategy is a combination of ‘Use second on fail’, and ’Occupied/unoccupied’. The second route (route 4) is used
both during non-occupation, and if the first route (route 3) fails during occupation. This is done by enabling route 3 during
occupation, and using the logic module to enable route 4 either during non-occupation, or when the destination 3 fail
bit is set.
As a result if route 3 fails during occupation, the failing alarm and any subsequent alarms will be sent to route 4. However,
like the example shown in 12.4.5.3 above, if destination 3 recovers during occupation, then any alarms sent to destination
4 will also get sent to destination 3, as the route is valid.
However, if destination 3 fails, and then occupation status changes, any alarms sent to destination 4 during the
unoccupied phase would not get sent to destination 3 after it recovers, and occupation returns.
&
$
-)
#
?X
?'@"
`Y*Zc
Y+h^
**]_
'
& &
$ #
"
# &
?X
! "
^+*&Y^]< $
[*\]<]
*
'
$
"
#
&
!
@[<*
+
'
# $ #
() &
%#
'
%!
*+;<; "
$= *<* *> *<* *> *<* *> $
!
&ZY^Y*Y_[+<
?
$
"
&'
!
This is an example of groups going to two destinations via two routes, (g1 via o1 and o2, and g3 via o4 and o5), and of
several routes connecting to one destination (o2, o3, and o4 connecting to e2).
The Maintenance alarms from g1 are sent to the Maintenance company via o1 and e1, and to the Remote Bureau via o2
and e2. The Plant Failure alarms from g2 are sent to Remote Bureau via o3 and e2.
When the engineer is on site, he switches switch 1 off, disabling the reporting of maintenance and plant failure alarms.
In this state the alarms will just get logged, but not reported.
The Comfort alarms from g3 are reported to the Facilities Manager supervisor via o5 and e3 during occupation as defined by
time zone 1 (bit 13,0). If the alarm being sent to the Facilities Manager is not acknowledged, then the Fail bit of e3 will enable
o4 to send it to the Remote Bureau via e2.
Note that in this case, if the Facilities Manager supervisor continues to fail to acknowledge alarms, the route o4 will
remain open after the original route o5 closes for non-occupation, and alarms will continue to be sent to the Remote
Bureau until the e3 alarms are acknowledged. Additional logic would be required to enable route o4 only if both
occupied and failed bit conditions were present.
"^;<Y<Y*=
&
&
$
"
#
#
!
^+*&Y^]<
<Y<Y*=
.'
& $
#
()
I %#
'
%!
c+Y[_
$= *<* *> *<* *> *<* *> $W&`c+IW
!
?
$
"
&'
!
This strategy has the alarms split into two groups, Maintenance at priority 10, and Plant Failure at Priority 50. The
destination module e1 has its priority switched between 0 and 20 by the action of time zone 1 on function module 3.
Z1 (phone times) has its occupation set to the period of cheaper phone tariff. Thus during ‘phone times’, the hold priority
level of e1 will be set to 0, so that maintenance alarms will be allowed to dial out, and all held alarms will be cleared. During
the non ‘phone times’ period, only Plant Failure alarms will be allowed to send alarms to the auto-dialled destination,
the Maintenance alarms will be held (unless a plant fail alarm causes a dial out). By carefully setting the time zone this
low priority dial out can be restricted say to one hour in the night, reducing the telephone costs.
Note that if a plant failure occurs during the day, any held maintenance alarms will also be sent.
If a supervisor is permanently connected then its CNC address (or its vCNC address) may be used. If the supervisor is
not permanently connected (e.g. using TCP/IP dial up) then a 3xtend/EINC L vCNC in alarm mode can be used (see 3.3.9);
however, sending alarms to a supervisor not permanently connected is best achieved by using the IP Address destination
type of alarm.
Network Module
Email Server Address: The IP address of the email server to be used. The IQ3 does not have its own email server (i.e.
DNS operation non included) so a separate SMTP service must be used.
Because the Email Server Address is not fixed on a DHCP system, it must be set to a host name or an Internet domain
name. Thus when an email alarm is to be sent the Email Server IPAddress is resolved by either a WINS or DNS server.
Destination Module
From Email: This should be set to the email address to which replies are to be sent (e.g. ‘failure to deliver’ reply).
To Email: This should be set to the email address to which the email alarm is to be sent.
Message: This is an optional text message of up to 256 characters which is appended to the alarm.
A l a r m
Item label Description
Controller identifier
Site Name
Group label
Controller identifier
Item label
Alarm description/Transition
Time/date
Extra text
These four module types are loaded as a block for compatibility with the BACnet Notification Class Object (see Pt. 1
section 3.8.2.8).
The BACnet Notification Class object maps to the Trend Alarm Group module.
The Recipient_List property within the Notification Class object is a list of BACnet destinations, which is a list of the
BACnet Alarm Destination modules the Group module is connected to (via Route modules). A BACnet destination also
has sub-properties associated with the time scheduling of the alarm; these are catered for by the Time Zone module in
the BACnet Alarm Block which is used to enable the Route module.
When the BACnet Alarm Block icon is selected the user is presented with the BACnet alarm configuration dialogue box:
This defines the days of the week and the period within the day for which the alarm may be sent. This basically specifies
how the time zone is set up. There is only a weekly pattern (which corresponds to the time zone Normal Week) with no
Exceptions. There is only one occupation period defined by a start time and an end time.
The ‘Use confirmed message delivery’ tick box sets up the Alarm Destination module Service Type parameter which
corresponds to the inverse of IssConfirmedNotifications BACnet sub-property within the Recipient_List property. If
the Service Type is clear (Confirmed), the alarm will be sent, and an acknowledgement will be expected from the Alarm
Destination BACnet device. If an acknowledgement is not received, the alarm will be sent again as defined Pt. 2 section
3.4.2; failure to acknowledge the second set of retries will cause the Alarm Destination module Failed Bit to be set. If the
Service Type is set (Unconfirmed) the IQ3 itself sets the acknowledge, so the alarm destination modulewill not retry, and
the Failed Bit will never be set.
The To-Normal, To-Fault, and To-OffNormal tick boxes define the types of alarm state transitions that can be used to
generate the alarm. These produce a 3 bit field as follows:
000
To-Normal To-OffNormal
To-Fault
The alarm state transitions are explained in section 12.7.4.2 below.
Once the BACnet alarm Block has been added to the strategy page in SET it can be modified.
In order for the BACnet Alarm Block modules to remain BTL (BACnet Testing Laboratory) compliant, there are strict
rules governing the changes the can be made and SET will check that any changes conform when it creates the strategy
download file (see Pt. 1 section 6.2.1); if the changes do not conform SET will give the user a warning and state reasons
for incompatibility.
As explained above each recipient in the recipient list is equivalent to a time zone/route/destination module combination.
The notification class object itself is equivalent to the group module, so if the notification class object has several
recipients this is equivalent to the group module being connected to several timezone/route/destination module
combinations. Thus having created a BACnet Alarm Block on the strategy page, additional destination modules can be
added by adding more Alarm Blocks and editing them so that the destination modules come from the same group module.
BACnet Alarm Route
BACnet Alarm Group BACnet Alarm Dest
o1
R
g1 g1O G e1
D o1D S
H O
Z1V F
L E
N 0 H
ALARM GROUP ALARM ROUTE
0 Priority BACnet ALARM DEST
0 Retry Pause Int.
Disabled Inhibit Cleared
0 Service Type
0 Process ID
111 Transitions
0 Device Instance
BACnet Time Zone Z1 0 Network Number
MAC Address
TIME ZONE
0 3 6 9 12 15 18 21 24
MON
TUE
WED
THU
FRI
SAT BACnet Alarm Route
SUN BACnet Alarm Dest
o2
g1O G e2
D o2D S
Z2V F
E
0 H
ALARM ROUTE
BACnet ALARM DEST
0 Retry Pause Int.
BACnet Time Zone Z2 Disabled Inhibit Cleared
0 Service Type
TIME ZONE 0 Process ID
0 3 6 9 12 15 18 21 24 111 Transitions
0 Device Instance
MON
TUE 0 Network Number
MAC Address
WED
THU
FRI
SAT
SUN
In the strategy diagram above, group module 1 is connected to 2 destination modules via the two route modules. Thus
there are two members in the Notification Class object’s Recipient List, see section 12.7.4.3 below.
The 3 bit field is used to enable/disable transitions to the BACnet states: Normal, Off Normal, and Fault. A “fault”
condition is a malfunction, nearly always representing a failure within the automation system itself. An “offnormal”
condition is a condition within the system that is not normally expected or is outside the bounds of ideal operation. A
“normal” condition is anything else.
*Only the digital driver readback alarm (SDGT) produces a BACnet alarm, the driver maintenance alarm (MINT) does
not produce a BACnet alarm. All other driver types do not produce BACnet alarms.
Thus an Out of Limits (OUTL) alarm is considered a Fault state so a transition from Normal to OUTL is a To-Fault transition.
Sensor HIGH and LOW alarms are both Off Normal, and OUTL and READ are both Fault.
Bacnet Protocol
Trend Protocol
To Normal To Normal
Normal
To Off Normal
OU
m
CL TL
ar
ala
al
EA
ar
H
rm
al
R
IG
OU
H
H
IG
TL
H
ala
AR
rm
LE
C
To Off Normal
HIGH OUTL
To Fault
To Fault
In Trend protocol the alarms are treated independently, each alarm has a clear alarm (excluding
the Plot module BBUF event), but in the BACnet protocol, the alarms follow paths between
Normal, OffNormal, and Fault. The possible BACnet transition paths, as shown in the diagram
above, are directly enabled/disabled by the three alarm destination module transition bits. Normal
The BACnet alarm also distinguishes the starting condition so there are two ‘To OffNormal’
alarms, ‘Fault To Off Normal’ and ‘Normal To OffNormal’. There are also possible alarms within
the transition states so a Trend change of state from OUTL to OUTL + READ will be represented
by a BACnet alarm ‘Fault to Fault’.
Of the types of modules generating BACnet alarms the sensor is the most complicated. Its BACnet HIGH
High Limit
LOW
Low Limit
flow is represented in the adjacent diagram. OffNormal
The transitions to and from the two OffNormal states, HIGH and LOW, actually generate separate
BACnet alarms, to and from High Limit and to and from Low Limit respectively, whereas the
transitions to and from the two Fault states, OUTL and READ, generate the same BACnet alarms
(to and from the Fault state).
OUTL
The diagram shows that sensor can transition from Normal to HIGH to OUTL to READ. For
BACnet it is preferable if the transition back to Normal takes the reverse of that route, READ to READ
OUTL to HIGH to Normal. It is also possible to go from Normal directly to one of the fault Fault
conditions as indicated by the outside arrows (e.g. Normal to OUTL, in which case the return
should be OUTL to Normal).
The recipients are put in the recipient list in the order of the route modules’ instances (i.e. Route module 1, Route module
2 etc.).
A BACnet device can write to the Recipient List but has to have the same number of recipients, i.e. it cannot increase
or decrease the number of recipients; this can only be done by editing the strategy (in SET). It can however change a
recipient’s properties (e.g. valiDays, times, or recipient’s address i.e. Dynamic Alarm Subscription).
CHANGE_OF_STATE
COMMAND_FAILURE
OUT_OF_RANGE
BUFFER_READY
Message Text: The equivalent Trend text message, see 12.8 below
Notify Type: Always set to ‘ALARM’ except for Plot module BBUF alarm when it is set to ‘EVENT’.
AckRequired: Always set to false
From State: Previous state, either Normal, Off Normal (or for a sensor, High Limit or Low Limit), or Fault
To State: Current state, either Normal, Off Normal (or for a sensor, High Limit or Low Limit), or Fault
Event Values: The Event Values sent depend on the Trend alarm condition as shown in the table below.
Event Values Current Value Current Value Current Value Current Value Current Value Current Value Current Value Source
Status Flags Status Flags Status Flags Status Flags Status Flags Status Flags Status Flags Last Notify Record
Deadband Deadband Deadband Deadband Feedback Value Previous Last-
High Alarm Level Low Alarm Level Upper or- Input channel- Notify record
Lower Limit Limit
The IQ3 is also able to respond to a BACnet request for alarm information (BACnet GetEventInformation Service). This
is a request for summary details all the relevant modules (i.e. sensor, digital input, driver) in alarm which in BACnet is
any module which is not in the ‘Normal’ state.
The response message (List of Event Summaries) contains the following information for each event:
Trend BACnet Status Flags
module object
Bi t 3 Bi t 2 Bi t 1 Bi t 0
Sensor AIn Out of Service, Overridden, Fault, In alarm,
always zero Sensor Overridden READ or OUTL HIGH or LOW
Digital Input DIn Out of Service, Overridden, Fault, In alarm,
always zero Digital Input Overridden always zero DI=0 or DI=1
Driver AOn Out of Service, Overridden, Fault, In alarm,
(any type except Digital, type 1) always zero Driver Overridden always zero always zero
Driver DOn Out of Service, Overridden, Fault, In alarm,
(Digital, type 1, only) always zero Driver Overridden SDGT always zero
Object Identifier: This comes from the source module’s equivalent BACnet object’s Object Identifier. e.g. AI8. The
BACnet object identifiers for the Trend modules are shown in the Status Flags table in section 12.7.4.3 above..
Event State: This defines the current alarm state. It roughly corresponds to the Trend In Alarm parameter and is explained
in the relevant table in Pt. 1 section 3.8.2. It is declared as Normal, OffNormal, Fault, High Limit, or Low Limit as explained
in section 12.7.4.2 above.
Acknowledged Transitions: The relevant bits are always set to 1 (i.e. acknowledged) as the IQ3 does not support the
BACnet acknowledge alarm service.
Event Time Stamps: A BACnet timestamp is year, date, time. This will give the time and date values of the last transitions
into OffNormal, Fault, and Normal states respectively. The relationship between these states and the Trend alarms is
explained in section 12.7.4.2 above.
Notify Type: Always set to ‘ALARM’ except for Plot module BBUF alarm when it is set to ‘EVENT’.
Event Enable: This comes from the source module’s equivalent BACnet object’s Event Enable property. These three bits
are the enable bits for To Normal, To Fault, and To OffNormal as defined in section 12.7.4.2 above.
Event Priorities: These are the priorities for the three types of alarm transitions from the Module Notification Class object
that transmitted the alarm. They are derived from the group module Hold Priority and are all set equal to 255 minus the
group module Hold Priority parameter
Coded: The coded alarm format just contains the alarm code and the date. It requires interpretation by a supervisor to
be understood by a normal user.
alarm code time
The alarm codes are given in section 12.3 (General) and 12.4 (Item).
Attribute: The attribute alarm format contains text communications from the alarm log record.
i.e.
v(O=S, U=1, P=0, V=24.04, R=1, H=16, N=22, S=4, D=30, M=5, Y=0, G=0, I=0)
These parameters O, U, P etc. are alarm log parameters and are explained in 12.9.
This form of alarm is for use by software applications that can parse the data and enter it into a database. The source
address of the controller is embedded in the alarm message and can be decoded by the application.
This ‘roll round’ alarm log has a maximum length of 300 alarms after which the earliest alarms are lost. For coded alarms
the protocol limits the item number to 255 maximum. For text alarms the maximum item label length is 20 characters (although
the 963 can be set up to use labels previously learnt).
Each logged alarm record is treated as a module. Text comms access enables the log to be searched using conditionals
like a database. Alarm module 1 is the most recent entry into the log.
The review alarm history, (V), is a view of the most recent 20 entries of this database (e.g. V20 will return the most recent
alarm).
Once the log is full, when a new alarm is added to the log, the oldest alarm will roll off the other end; the alarm will be
lost whether or not it has been sent. The alarm will be lost from the log, and no further attempts will be made to send it
(unless it has been sent to a destination module which is currently trying to deliver it to its destination).
In order to make maximum effort to send an unacknowledged alarm as it is about to roll off the log, there is a ‘high water
mark’ above which any alarms will be sent regardless of their priority i.e. this disables the hold priority in the alarm
destination module. The high watermark is set to 80% of the log size (i.e. 40 alarms).
When an alarm is created it will be placed in the alarm log. The destination(s) of the alarm are dynamic, in that they may
change during the life of the alarm in the log. The last element in the module, alarm status, indicates whether the alarm
is still waiting (active), or is sent (i.e. acknowledged by the destination(s) required at the time).
The full details of the alarm log are given in the alarm log module details section (see Pt. 2 section 5), but the log includes
the following details.
Alarm
Time *Transition Status
module number Date
module type
*Note that the Transition column shows the Reported state of the alarm if the alarm is either Occurred or Cleared, but
will state Event if it is an event type alarm (e.g BBUF).
Configured by
Module SET IPTool Web Pages
Address ✔ partial partial
Alarm Destinations ✔ ✔
Alarm Groups ✔ ✔
Alarm Log ✔ ✔
Alarm Routes ✔ ✔
Analogue Nodes ✔ ✔
Connectives ✔ ✔
Digital Bytes ✔ ✔
Digital Inputs ✔ ✔
Directories ✔ ✔
Displays ✔ ✔
Drivers ✔ ✔
Functions ✔ ✔
IC Comms ✔ ✔
IO Modules ✔ (+automatic) ✔
Knobs ✔ ✔
Logics ✔ ✔
Loops ✔ ✔
Networks ✔ partial partial
Non-Trend Device (NTD) ✔ ✔
Options (automatic - read only)
OSS ✔ ✔
Pages ✔
Plots ✔ ✔
Program (automatic - read only)
Schedules ✔ ✔
Sensors ✔ ✔
Sensor Types ✔ ✔
Sequence Table ✔ ✔
Switches ✔ ✔
Time ✔ ✔
Time Zones ✔ ✔
Users ✔ ✔
Virtual CNCs ✘ ✔ ✔
*XNC Interfaces ✔ ✔
* The XNC interface module is populated by the TCL application produced by TCLTool2.
1.2 Parameters
The module items shown in SET dialogue boxes and web pages are referred to as module parameters.
All parameters can be changed using text comms (see Appendix 3).
As shown in 1.1 above a few modules are configured using IPTool. All other modules (basically the strategy configuration)
are configured in SET. The XNC interface module is populated with inputs and outputs from the TCL application
produced by TCLTool2.
The structural module parameters (module instance, its type, its input and output connections) can only be configured
using SET, but other parameters can be changed using the web pages.
The module parameters are described in the following sections, and are classified as one of the following:
source/constant, constant, output, status
In IQ3 a module input is source/constant - either source or constant (with the exception of the alarm route module input
and alarm destination module input which can only be sources i.e. sourced from alarm group output, and alarm route
output respectively).
If an input has a connection then it is a source, if it has no connection then it is a constant.
A setting that cannot be connected is referred to as a constant because having no connection it cannot be changed by
the running strategy. (It can be changed by IC Comms, because they use text comms.)
A module output that may be connected (to other modules or output channels) is referred to as an output.
A module state or calculated value that can only be monitored (e.g. by web pages) and cannot be connected is referred
to as a status.
Each input or output has a value and a connection parameter. For example the driver module source has a value (text comms
S) and a connection (text comms Sc); the text comms connection parameter code is always defined by adding the suffix
‘c’ to the value parameter code. The connection parameter defaults to blank and is set to the connected input or output
parameter code as a result of a connection made in SET (e.g. the driver source may have Sc=F1D, Function 1 Destination).
To simplify the following sections the connection parameters are neither described in the text nor shown in the parameter
tables.
External input and output modules (external sensors, external digital inputs, and drivers) can be connected to the I/O
channels which are designated by hardware module number and hardware channel number. The hardware module is
designated by 0 to F where module 0 is the main IQ3 controller and module numbers 1 to F are external I/O modules
connected to the I/O bus. The hardware channel number can be set to be from channel 1 to the maximum number of
channels for that module; if an input channel is set to zero, it becomes a constant input and can have a constant value
set up on the web page (but not by SET).
Parameters are also classified by variable types either analogue, digital, or characters.
Digital parameters are binary digits having two states (0 or 1). If they are connectable parameters they can only be
connected to digital input or output points as appropriate.
Analogue parameters are any other numeric parameters other than those limited to binary digits. If they are connectable
parameters they can only be connected to analogue input or output points as appropriate.
At the beginning of each module’s parameters’ table in the following sections, the module’s overview parameters are
defined; these list the parameters shown when that module is used as a dynamic item on a graphIQ web page (e.g S1
will display S1$, S1V, S1% (label, value, units) - (see also Pt. 2 section 12.4.3).
Connectives
Project Details
Site Name
Site GUID
2.3 Parameters
2.3.1 Controller Identification
Identifier: (characters, constant) The Identifier is a 30 character label which describes the controller and is sent as part
of a text alarm message to identify its source and should be unique on the site. It is also used as controller attribute 1
for text communications.
Not Sent: Within SET the identifier can be excluded from being downloaded. This enables a strategy to be used
by several controllers (see Pt.1 section 6.1.6).
Certain supervisors and tools allow navigation through the system and will display the controllers’ identifiers (e.g. 963,
SET, IQView).
Attribute n: (characters, constant) There are six other device attributes (attributes 2 to 7) all up to 30 characters long.
The seven attributes (identifier plus 6 others) are used in text communications for two functions:
Message Reception: They allow the controller to be identified either uniquely or as part of a group, so that
it may receive relevant communications.
Message Transmission: They can be used by the IC comms module to identify a controller or group of
controllers with which this IQ wishes to communicate.
Within the attribute several characters are reserved for special functions
&|*?.
The following characters are NOT to be used in the attributes:
\/({;,:
Single letters should also be avoided (S, K, W etc)
For further details see IC Comms (Pt. 2 section 15.3.3).
Serial Number: (characters, constant) The serial number for the IQ3, also shown on the product label. Set up during
manufacture. If an earlier manufactured version is upgraded to v2.0 or greater, this parameter will be set to the controller
Ethernet MAC address (see Pt. 2 section 20.1.4.1)
Note that IQ3 does not have the time keeper functionality present in IQ1s or IQ2s so address 11 is not reserved for this
purpose, but is recommended for timemaster (see Pt. 2 section 32.4)
The local Lan number and local address together form the communication node attribute (e.g. L6O29) used in text
communications.
Not Sent: Within SET the local Lan can be excluded from being downloaded. This enables a strategy to be used
by several controllers (see Pt. 1 section 6.1.6).
The Site Name and Site GUID (see below) are created in SET in the project file (see Pt. 1 section 6.1.1). They can be managed
using the SET Site Code Manager Applet; this enables the Site Name and Site GUID (together known as Site Codes) to
be set the same for the complete site.
Site GUID: (characters, constant) This is a machine readable site identifier. It is a world wide unique code (GUID = Global
Unique Identifier) and all controllers on the site should have the same site GUID. It is specifically used in IP alarms to
identify the source on a multi-site system.
It is set up in the same way as the Site Name (see above).
If set to zero the device connected to the port can only communicate with the local IQ3. If set to a valid network address
(1, 4 to 119 excluding address 10) the internal CNC will assume that address and enable the connected device to talk over
the network.
2.3.5 Language
As explained in Pt. 1 section 6.1.4, SET enables language files to be downloaded to the controller. For a particular controller
a language file may be set up in SET to be either:
not sent
downloaded
default
English is embedded in the software, the other languages each have a file. Normally English is set as a default but an
alternative language may be set to default if required.
Once languages are downloaded, they may be selected as the current language (rather than the default) from the web
pages.
Language Selection: (characters, constant) This parameter specifies the language used for the display of web pages and
display and transmission of alarms. It normally defaults to English (see above). If another language is required the exact text
(not case sensitive) of the language name must be entered correctly. This text is not 8 bit (i.e. Francais not Français).
available selections: English
Arabic
Dansk
Deutsch
Espanol
Francais
Italiano
Russian
Simplified Chinese
Language Default/Download/Not Sent: Within SET the language files to be downloaded can be specified.
Default: Language used by IQ3 as default (the default language is always downloaded).
Download: Languages to be downloaded to IQ3 (English is always downloaded).
Not Sent: Languages not to be downloaded to IQ3.
2.3.6 Alarms
The address module alarms (known as general alarms) are collected together in the general alarm group.
General Alarm Group: (analogue, constant) The group containing the general alarms. By default set to group zero (group
0); alarms in group 0 are logged, but not sent. The alarms must be attached to another group (and the alarm strategy
constructed) in order to be sent, (see alarms Pt. 1 section 12.6). The address module alarms can be disabled by disabling
the group module to which the general alarm group is attached.
Controller Online (CONL): (digital, output) Generated when the controller starts due to power up or an internal soft
reset and loads up and runs a valid strategy.
The controller may restart due to detection of a fault condition (see below). The restart process for a soft restart is the
same as for a power up restart as explained in Pt. 1 section 6.5.2.
By itself, it is just an indication of the controller being re-powered and should not cause for concern, unless the frequency
of this alarm occurring is considered to be unreasonable, i.e. if a CONL occurs 3 times in the space of one hour- this
is unreasonable.
However, this alarm may be due to work being carried out elsewhere on the site. If a CONL occurs once a day, that also
is considered to be too frequent, but is unlikely to be due to a system malfunction. Check to see if the CONL is related
to time, or a particular item of equipment being switched ON or OFF. If related to time what is the relationship.
Generally, if the system is at fault, then alarms will be generated at very regular intervals. Under these conditions, contact
your Field Service representative.
If connected to another module’s digital input, the input’s details will be shown on the web page. It is available as a digital
connective (R1S0)
Corrupt Strategy (HELP): (digital, output) Generated when the controller starts due to power up or an internal soft reset
and is unable to load up and run a valid strategy. Under these conditions it is unlikely that an alarm will be sent as the
strategy will not run.
However, the alarm condition can be seen on the address module web page.
A valid strategy file should be downloaded to clear this status.
If connected to a module’s digital input, the input’s details will be shown on the web page. It is available as a digital
connective (R1S1).
Failed Peripheral Interface Adapter (FPIA): (digital, status) This alarm is not currently operational. A PIA is a device
that allow a microprocessor to interface with the outside world. It may be configured to be digital input, digital output,
or a combination of the two by setting an internal register accordingly. At power-up it defaults to all digital inputs.
At system power-up this device is set up according to the interface configuration; thereafter the setting is checked at
regular intervals. If for any reason the value has changed, the FPIA alarm is raised causing the controller to restart. This
will also generates a CONL alarm (if the strategy file is ok).
There are two main reasons why this alarm would be generated:-
1) Hardware Failure - a device has actually failed. Under these circumstances, the FPIA and CONL alarms
will be repeated continuously, until the fault is cured or the device removed from the system. Contact your
Field Service representative immediately.
2) Electrical Interference - usually due to switching plant on or off. If the problem is due to installation, then
it is important to point out the possibility of a hunting action. Consider the situation whereby the system
starts, the strategy runs and causes a particular item of plant to turn on. In turning on, a burst of interference
is generated that causes the PIA to lose its setting up information. This will be picked up by the
microprocessor, which will generate the FPIA alarm. The outputs will be disabled and this particular item
of plant will be switched off.
The system restarts and the whole cycle repeats. This problem should be picked up during the commissioning
phase and, as with hardware failure, the alarms will be repeated continually. If this should happen, contact
your Field Service representative immediately.
This device has to be interrogated at regular intervals by the microprocessor in order that this information can be used
by the controller. If for any reason, one of the RTC values is outside the range for that parameter an FRTC alarm is
generated. This alarm may occur at power up with the RTC in an uninitialised state. If the fail condition remains, the
FRTC alarm will be resent once every hour. This alarm does not cause a restart or CONL.
If connected to a module’s digital input, the input’s details will be shown on the web page. It is available as a digital
connective (R1S3).
Failed RAM (FRAM): (digital, status) This alarm is not currently operational. As part of its housekeeping, the IQ3
controller continuously checks that it can read from and write to RAM (random access memory), the read/write memory.
If it cannot, for any reason, an FRAM alarm is raised and the controller restarts.
As with FPIA, this alarm can be generated either through device failure or electrical noise, and the recommendations
stated in that section apply here.
Failed Software (FSWR): (digital, status) This alarm is not currently operational. Should a software action require the
use of memory outside the defined boundaries, e.g. stack overflow, this alarm will be generated.
This may occur as a result of device failure, electrical noise, or firmware datafile error. However, the recommendations
as stated for the FPIA alarm apply equally here.
Serial Comms Failure (FDRT): (digital, status) This alarm is not currently operational. This alarm indicates a failure on
the RS232 supervisor port. This will be a failure of the communication hardware (UART - Universal Asynchronous
Receiver transmitter). [Note that FDRT code refers to Fail Dual Asynchronous Receiver Transmission on IQ1 or IQ2 series
controllers].
Failed Prom (FPRM): (digital, status) This alarm is not currently operational. This alarm is generated if the EPROM
checksum is wrong at power up. This indicates that the processor board should be replaced.
Sequence Table Overrun (STOR): (digital, output) The controller is unable to complete the sequence of modules in the
required time. Reduce the number of modules. If connected to a module’s digital input, the input’s details will be shown
on the web page. It is available as a digital connective (R1E1).
Low Memory (LMWG): (digital, status) This alarm is not currently operational. If the controller runs low on RAM it will
send this alarm and reboot. Contact Technical Support.
IO Bus Failure (FCAN): (digital, status) This alarm is not currently operational. Communications failure on the I/O bus
(e.g. short circuit). Check wiring.
Low Flash (LFWG): (digital, status) This alarm is not currently operational. The amount of memory used by graphics
files (backdrops) is excessive. Reduce the size or number of files.
Archive Failure (FARC): (digital, output) The archiving of the running strategy file into flash memory has failed. Contact
Technical Support. It is available as a digital connective (R1E4).
Corrupt Time (FTIM): (digital, status) This alarm is not currently operational. This alarm indicates that the IQ3 is running
as a slave to the timemaster and it has failed to be synchronised by the timemaster.
File Error (FLER): (digital, status) The IQ3 is unable to load its current strategy file, or the backup to this file, and has
had to load the original file downloaded from SET. This means it will have lost any changes made since the download
(i.e. changes made using web pages or SET Live Edit). Contact Technical Support.
Note that of these alarms, only CONL, HELP, STOR, FRTC, FARC, FLER are currently generated by the IQ3. Also note
that FRTC is sent instead of FTIM.
Strategy Revision: (analogue, constant) The strategy revision is set up in SET and automatically updated by SET each
time the IQ3 download file is created (See Pt. 1 section 6.2.1)
Version: (characters, constant) The version of firmware in the IQ3 in terms of type, version, and date.
Build: (characters, constant) The full code of the development firmware version used in the IQ3.
Bootloader Version: (characters, constant) The version of firmware used in the bootloader (the piece of firmware which
on power up enables the main firmware to be loaded into the IQ3 processor).
Baseboard Version: (characters, constant) The version of firmware used in the baseboard.
File List: (characters, constant) This parameter is a number which refers to a particular list of files included in this version
of IQ3. It covers such options as IQ3xcite/IQ3xact, and branding version. It is only for use by Trend staff.
As the controller powers up or restarts with checksum OK the CONL alarm is generated, but if checksum is not OK the
corrupt strategy status is set.
The remedial action to overcome the corrupt strategy is to download a valid configuration data file.
Onboard IO: (analogue, status) This indicates the number of I/O channels available in the IQ3 (e.g. IQ3xcite has 16, and
IQ3xact has 12).
External IO Enabled: (digital, constant) This parameter indicates whether the external I/O modules may be connected
(i.e. IQ3xcite/96 will have this set to I whereas IQ3xact/12 will have it cleared to O).
External I/O Limit: (analogue, constant) This parameter is the maximum number of external I/O channels that may be
connected (e.g. IQ3xcite/96 has 80, IQ3xact/12 has 0).
External I/O Count: (analogue, status) This parameter is the number of I/O channels connected.
brIQ Capacity: (analogue, constant) The total strategy memory in the current controller (may change with firmware
version etc.). It is measured in ‘brIQs’ (see Pt. 1 section 5.8).
brIQs Used: (analogue, status) The amount of memory used for the current strategy (measured in ‘brIQ’s - see Pt. 1 section
5.8).
Plot Memory Size: (analogue, constant) Memory capacity for plots in bytes; one synchronised plotting record (1 value
at one time) requires 5 bytes, and one triggered or periodic plotting record requires 10 bytes..
Plot Memory Used: (analogue, status) The capacity of plot memory already used (in bytes as defined above).
2.3.9 Others
Override Timer (mins): (analogue, constant) The time in minutes for which a module set to override via SET Live Edit
or a web page will stay in override. If overridden by SET or a web page, the module will be overridden while the address
module override timer is true; once an override is set, the address module override timer should be set to the required
time, and it will start counting down to zero at which point this override (and any other overrides set up) will be removed.
This does not apply to overrides which are sourced from a strategy module (see Pt. 1 section 5.7). If the override timer
is set to zero there is no override timer action
Power Reset: (digital, output) A digital pulse generated on power up which lasts for 1 sequence table cycle. If connected
to a module’s digital input, the input’s details will be shown on the web page. It is available as a digital connective in
SET (R1p).
TYPE
Parameter Web Comms Comments
SET IPTool Code Low High
/pge
Controller Parameters
CONST
0 30 Text used to identify controller and as controller
Identifier R/W R/W R/W D null
attribute 1
characters
Supervisor Port
Lan. Unique on Lan. Valid range 0, 1, 4 to 119
(SET: Supervisor R/W R/W - U 0 119 0
excluding 10. Address 0 communicates only
Port Address)
with this IQ3
Defines language used for web pages and
see section set up in
Language selection R/W R/W - P alarms. Text must be exact - see section 2.3.5
2.3.5 above SET
above
Group for all address module (general) alarm
General Alarm
R/W R/W - g 0 max 0 bits. Group 0 specifies not sent. Set to group
Group
module number to send alarms
CONL alarm bit set to 1 when controller
Controller Online R R/W - S0 0 1 n/a restarts successfully. Can be connected to a
digital input. Available as a connective in SET.
HELP alarm bit set to 1 when checksum failure
indicates strategy is corrupt. Can be
Corrupt Strategy R R/W - S1 0 1 n/a
connected to a digital input. Available as a
connective in SET.
STATUS STATUS STATUSOUTPUTSTATUS
TYPE
Parameter Web Comms Comments
SET IPTool Code Low High
/pge
Controller Parameters
Not currently operational. FPRM alarm bit
STATUS
Failed PROM R R/W - S7 0 1 n/a set to 1 if PROM checksum is wrong at
power up
OUTPUT
STOR alarm bit set to 1 if all sequence
Sequence Table table isn't seviced in requred time. Can be
R R/W - E1 0 1 n/a
Overrun connected to a digital input. Available as a
connective in SET.
STATUS STATUSSTATUS
Not currently operational. LMWG alarm bit
Low Memory R R/W - E2 0 1 n/a
set to 1 if controller runs low on RAM
Not currently operational. FCAN alarm bit
IO Bus Failure R R/W - E0 0 1 n/a
set to 1 if communications fail on I/O bus
Not currently operational. LFWG alrm bit
Low Flash R R/W - E3 0 1 n/a set to 1 if memory used by graphics file is
excessive
OUTPUT
FARC alarm bit set to 1 if archive of
strategy to Flash has failed. Can be
Archive Failure R R/W - E4 0 1 n/a
connected to a digital input. Available as a
connective in SET.
STATUS CONSTSTATUSCONST CONSTCONST CONSTSTATUSCONST CONST CONSTCONST CONST CONST CONST STATUS STATUS
n/a Not currently operational. FTIM alarm bit
Corrupt Time R R/W - E5 0 1
set to 1 if time out of range
FLER alarm bit set to 1 if IQ3 unable to
File Error R R/W - E6 0 1 n/a load current or backup strategy file, and
has loaded original file.
IQ3xcite or
Type Name - R - y fixed Controller type name
IQ3xact
The revison of stategy. Incremented by
Set up in
Strategy Revision R/W R - d 1 SET each time strategy download file is
SET
created.
25 character string confirming controller
Version - R R C 25 n/a
type, firmware issue, and date
n/a
Build - R - B fixed Development firmware version used
n/a
Bootloader version - R - c fixed Bootloader version used
n/a
Baseboard version - R - b fixed Baseboard version used
n/a
XNC Enabled - R - x 0 1 Bit set for IQ3/XNC
n/a
Onboard IO - R - h 12 16 Number of I/O channels available in IQ3
TYPE
Parameter Web Comms Comments
SET IPTool Code Low High
/pge
Controller Parameters
OUTPUT
Bit set to 1 on power up for 1 sequence table
Power Reset R - - P 0 1 n/a cycle. Can be connected to a digital input.
Available as a connective in SET.
Local Node Not Sent R/W - - - 0 1 Local Node excluded from download if 1
3.1 Symbols
Alarm Dest 2 Alarm Dest 3
Source from Failed bit
alarm route module e2 e3
S o3D S
F F
0 H
Hold priority input H
ALARM DEST ALARM DEST
0 Message Format 0 Message Format
0 Retry Pause Int. 0 Retry Pause Int.
Disabled Inhibit Cleared Disabled Inhibit Cleared
0 Alarm Address IP =
0 Remote Lan 2774 Dest. Port
IQ system Lan
type parameters
IP Address type
parameters
Email Address
type parameters
BACnet Address
type parameters
Connectives
3.4 Parameters
3.4.1 Input and Outputs
Source: (source). This input to the alarm destination module is connected to an alarm route module. If connected to an
alarm route module output the output’s details will be shown on the web page. (i.e. onD where o = route module, n = route
module number, D = route module destination, e.g. o1D).
Hold Priority: (analogue, source/constant) This parameter can either be sourced from an analogue output or set to a
constant value. If connected to a module’s analogue output the output’s details will be shown on the web page.
The parameter value enables a priority level to be set below which alarms are held back by the destination module and
not sent. If an alarm comes in above this level, it, and all held alarms, will be sent. Each alarm has a priority level set in
its alarm group. The destination module will stay open to alarms with a priority level below the Hold Priority Level for
5 seconds after the last alarm was sent. If the parameter is an input it can be set by strategy; for example, this enables
the hold priority level to be lowered when comms demand is lower (say during non-occupation) to ensure that all held
alarms are sent (see also high water mark, Pt. 1 section 12.9).
Failed: (digital, output). This digital output is set when the destination device fails to acknowledge the receipt of an alarm
after the second retry (see Retry Interval, section 3.4.2 below). The destination module can only have one alarm it is
currently sending, and if the destination has failed the destination is blocked. The failed bit may be used to switch route
modules to send alarms to alternative destinations (see Pt. 1 section 12.6.1.3). If connected to a module’s digital input,
the input’s details will be shown on the web page. This output is shown as a connective in SET (enF where e = destination
module, n = destination module number, and F = Fail, e.g. e1F).
Note that the web page shows this bit as Read/Write, but it should be Read only.
Inhibit Clear (SET:Inhibit Clear Alarms): (digital, constant) This parameter stops clear alarms being sent to the destination
device (e.g. Sensor High (HIGH) would be sent, Clear Sensor High (CHIH) would not be sent). If the parameter is 0, clear
alarms will be sent, if set to 1, they will be inhibited.
Address (SET: Alarm Address): (analogue, constant) Destination device address on Lan.
Lan (SET: Remote Lan): (analogue, constant) Destination device Lan number.
Destination IP Address (SET: Destination): (characters, constant) The IP address of the destination.
Destination Port: (analogue, constant) The destination port number within the IP address.
To Email Address (SET: To Email): (characters, constant)The email address of the destination.
From Email Address (SET: From Email): (characters, constant) This should be set to an email address which
will be used to receive email messages from the destination (e.g. failure to deliver). If the from email address
is invalid, the email server may reject the email.
Extra Text (SET: Message): (characters, constant) This enables external text to be sent as part of the email
(up to 256 characters).
Email Server Address: This is only shown in SET and is read only; it is actually set up in the network module
(Type 1, Ethernet IP). For an email type destination to operate the Email Server Address should be set up
in the network module. The IQ3 does not have its own email server (i.e. DNS operation not included) so
a separate SMTP service must be used.
BACnet device: If BACnet device is selected, the alarm is sent as a BACnet notification to a BACnet device. The BACnet
device type of alarm destination module can only be added to the strategy page in SET by adding a BACnet alarm block,
see Pt.1 section 12.7.4, BACnet Device Alarm Destination Type, for details.
Process ID: (characters, constant) A 32 bit number that can be used in alarm messages to enable the device
receiving the alarm to identify it and treat it in a particular way, e.g. a particular ID could be used to identify
all HVAC alarms.
Transitions: (characters, constant) This specifies the changes in state for which the BACnet device can
receive alarms. It consists of 3 bits, each of which enables a type of transition:
Left Bit: To Normal transitions
Central Bit: To Fault transitions
Right Bit: To Off-normal transitions
See Pt. 1 section 12.7.4 for details
Device Instance: The destination BACnet device’s address on the BACnet system. This should be set
up by preference, but if this is not specified (set to zero), both the Network Number and the MAC Address
must be specified. The Device Instance must be used if the remote device is using automatic IP addressing
(see Pt. 1 section 3.7.4)
Network Number: The destination BACnet device’s Network Number. If the Device Instance is set to zero,
Network Number can be used in conjunction with the MAC Address to address the destination BACnet
device.
Note that in SET v6.3 the BACnet device can be specified by dragging a BACnet device from the System View or an NTD
from the Device View onto the required BACnet alarm destination module. This will set up whatever BACnet device
information that is available (Device Instance, Network Number, MAC Address).
Label: (characters, constant) The label shown in the module symbol on the SET strategy page and in the Web pages.
Page: (analogue constant) SET file strategy page number on which the module appears.
TYPE
Parameter Web comms Default
SET co d e Low High
page
Controller Parameters
Label R/W R/W $ 0 30 Alarm
CONST
D e st N The module identification label used
on the strategy page and in web
characters p a g e s.
SOURCE
Source R/W R Sc route module no This connection defines the route
only connection module from which alarms are
received.
SOURCE/CONST CONST
Type R/W R Y 1 IQ Lan 1 This defines the type of destination to
(SET: Destination 2 IP address IQ Lan which alarms are to be sent.Type 4,
Type) 3 Email BACnet only available on IQ3/BAC
4 BACnet controllers
Hold Priority R/W R/W* H O 255 0 The value defines the priority level
below which alarms are held back. If
an alarm is received above this level
it, and all held alarms, will be sent.
Can be connected to an analogue
output.
OUTPUT
Retry Interval R/W R/W R 0 32767 0 Sets the interval between batches of
(SET: Interval) attempts to send alarm to
minutes destination. Set to zero for
autodialling
CONST
Inhibit Clear R/W R/W C 0 1 0 If set to one will stop the alarm
(SET: Inhibit Clear destination module sending any
Alarms) alarms which declare an alarm
cleared status (clear alarms).
If set to zero clear alarms will be sent
CONST CONST CONST
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
Parameter Web comms Default
SET co d e Low High
page
Controller Parameters
Message Format R/W R/W M 0 C oded 0 This parameter is only used for IQ
1 Text Lan and IP address alarms. Coded
CONST
2 Attribute alarms are for decoding by
3 Enhanced supervisors. Text alarms are man-
(not used) readable. Attribue alarms give full
details from alarm log (see Pt. 1
section 12.8) for parsing by software.
Address R/W R/W A 0, 1, 4 to 119 0 This parameter is only used for IQ
CONST
(SET: Alarm excluding 10 Lan type alarms. Address of device
Address) to which alarms are to be sent (not
used if set to zero).
Lan R/W R/W N 0, 1, 4 to 119 0 This parameter is only used for IQ
CONST
(SET: Remote Lan) excluding 10 Lan type alarms. Lan number of
device to which alarms are to be
sent (Lan 0 is local Lan).
IP Address Type Alarm Parameters
Message Format R/W R/W M 0 C oded 0 This parameter is only used for IQ
1 Text Lan and IP address alarms. Coded
2 Attribute CONST alarms are for decoding by
3 Enhanced supervisors. Text alarms are man-
(not used) readable. Attribue alarms give full
details from alarm log (see Pt. 1
section 12.8) for parsing by software.
Destination IP R/W R/W i See IP 128.1.1.4
Address addresses
(SET: Destination) defined in Pt. This parameter is only used for IP
CONST
TYPE
Parameter Web comms Default
SET co d e Low High
page
Controller Parameters
BACnet Device Type Alarm Parameters
Service Type R/W R/W T 0 1 0 Defines whether module expects
Unconfirm- acknowledgement of alarm;
CONST
ed 0=Confirmed (expects
acknowledgement)
1= Unconfirmed (does not expect
acknowledgement)
CONST
Process ID R/W R/W P 0 4294- 0 An identifier for use in the destination
9672- device to identify the alarm as of a
95 particular type.
Transitions R/W R/W R 000 111 000 A 3 bit field used to enable particular
alarm types.
CONST
Left Bit: To Normal
Middle Bit: To Fault
Right Bit: To Off-normal
(see Pt.1 section 12.7.4)
Device Instance R/W R/W D 0 4194- 0 The destination BACnet device's
302 address on the BACnet system. If
this is left set to zero, both Network
CONST
Number and MAC Address must be
set up to specify destination device.
Device Instance must be set up if
remote device is using DHCP.
Network Number R/W R/W N 0 65534 0 The destination BACnet device's
CONST
4.1 Symbol
Alarm Group 4 group alarm output to route module
R
g4
priority level H O
L
N
ALARM GROUP
New alarm
0 Priority
Connectives
General Alarms all belong to the same ‘General Alarm Group’ which is set in the Address Module (see Pt. 1 section 12.3).
By default this is set to zero (group 0), which means that although the alarms are logged, they will not be sent. The general
alarms must be attached to another group in order to be sent. This can be done by changing the address module setting
using SET or via its web page.
As explained in Pt. 1 section 12.5, SET has a special alarms grouping dialogue box which lists all available alarms and
enables them to be allocated to alarm groups. It can also enable alarms to be enabled/disabled individually.
4.5 Parameters
4.5.1 Input and Outputs
Hold Priority (SET: Priority): (analogue, source/constant) The priority input may be set to any level with the range 0
to 255, where 255 is the highest priority. The priority is checked in the alarm destination module when alarms of a low
priority may be held (e.g. for a dialled alarm destination), until a higher priority alarm occurs which causes all the alarms
to be delivered.
This parameter can either be sourced from an analog output or set to a constant value. If connected to a module’s analogue
output the output’s details will be shown on the web page.
Output: (output) The group alarm output can be connected to one or more route modules. If connected to a route module
input the input’s details will be shown on the web page (i.e. onG, where o = route module, n = route module number, G
= input for group module, e.g. o1G). Each route module connects to an alarm destination module and has an enable/disable
input.
This output is shown as a connective in SET (i.e. gnO, where g = group module, n = group module number, O = Output,
e.g. g1O).
New Alarm: (digital, output) The new alarm digital output goes true for one sequence cycle whenever a new alarm, which
is attached to the group, is generated. This could be used by the strategy for example to switch on a annunciator whenever
an alarm occurs. If alarms are occurring faster that once per sequence cycle, the bit will be held high until one sequence
cycle after the last alarm occurred. If connected to a module’s digital input the input’s details will be shown on the web
page. This output is shown as a connective in SET (i.e. gnN, where g = group module, n = group module number, N =
New alarm, e.g. g1N).
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
Page: (analogue, constant) SET file strategy page number on which module appears.
TYPE
Parameter Web comms Default
SET co d e Low High
page
Controller Parameters
Label R/W R/W $ 0 30 Alarm
CONST
Group N The module identifier label used on the
strategy page and in web pages.
characters
Hold Priority R/W R/W* P 0 255 0 The value defines the priority of the alarm
SOURCE/CONST
(SET: Priority) in the group. 255 is the highest priority.
Can be connected to an analogue output.
OUTPUT
set to 1 and stay for one sequence table
cycle. If set to zero indicates no new alarm
occurred in last sequence table cycle.
* This source/constant parameter cannot be changed via the web page if it is set as a source.
The allarm log does not appear on the strategy page and does not need to be sequenced.
This roll around log has a maximum length of 300 alarms. A new alarm is always added as alarm 1; the other alarms ‘roll
on’ one position.
For coded alarms the protocol limits the item number to 255 maximum (i.e sensor 255). Fortext alarms the maximum
item length is 20 characters (although the 963 can be set up to use labels previously learnt).
Once the log is full, when a new alarm is added to the log, the oldest alarm will be deleted; this alarm will be lost whether
or not it has been sent. The alarm will be lost from the log, and no further attempts will be made to send it (unless it has
been sent to a destination module which is currently trying to deliver it to its destination).
In order to make maximum effort to send an alarm as it is about to be deleted as the oldest alarm, there is a ‘high water
mark’ above which any alarms will be sent regardless of their priority i.e. this disables the hold priority in the alarm
destination module. This level is set at 80% (i.e. the 241st alarm will trigger the high water mark and disable hold
priorities).
Because of this mechanism the alarm log contains up to the 50 most recent alarm changes (alarms and clear alarms).
The alarm destination module can only hold one alarm which it is trying to send to its destination (i.e. it is ‘blocked’).
It can have other alarms waiting in a stack. If an alarm is deleted as the oldest alarm in the alarm log it will also be deleted
from any destination modules’ waiting stacks.
However, if the destination module is currently trying to send the alarm, it will not be deleted from the destination
module.
If the alarm destination module has alarms waiting because they are not of sufficient priority, when the alarm log ‘high
water mark’ operates, the destination module will try to send these alarms.
The destination(s) of the alarm are dynamic, in that they may change during the life of the alarm in the log.
The last element in the module, alarm status, indicates whether the alarm is still waiting (active), or is sent (i.e.
acknowledged by the destination(s) required at the time).
If the alarm is being sent to multiple destinations it will remain ‘waiting’ until all destinations have acknowledged at
which point it will change to ‘sent’.
Each logged alarm record is treated as an alarm log module. Alarm log module 1 is the most recent entry in the log.
The alarm log is designed so that its database can be queried using text comms.
e.g. v1(*) will produce:
v1($="IQ23", T="Restart", O="G", U=1, P=0, V=0.00, R=1, H=14, N=28, S=22, D=13, M=9, Y=5, G=1, I=0,
L=1)
Text comms access enables the log to be searched using conditionals similar to searching a database.
e.g. v{O=S&U=1&P=3}(*) will fetch all occurrences of sensor 1 read alarms
*Note that the Transition column shows the Reported state of the alarm if the alarm is either Occurred or Cleared, but
will state Event if it is an event type alarm (e.g BBUF).
TYPE
Parameter Web comms Default
SET co d e Low High
page
Controller Parameters
STATUSSTATUS
Label - R $ 0 47 null Label of Module in alarm
characters
alarm Type - R T 0 11 null Text of alarm type e.g. 'High Value'
characters
module type - R O 'A' 'Z' null S = sensor
I = digital input
STATUS
L = loop
characters D = driver
G = general
STATUS
module number - R U 0 255 0 number of module generating alarm (not
used for general alarms).
alarm type - R P 0 8 0 Meaning varies with module type
S:0=high, 1= low, 2 =out of limits, 3=read
I: 0=digin off, 1=digin on
STATUS
L:0=SP dev, 1=PV fail
D:0=Readback, 1=maintenance
G:0=CONL, 1=data error, 2=failed PIA,
3=failed RTC, 4=failed RAM, 5=failed
SWR, 6=failed VART, 7=failed PROM
value - R V - - - Real number or bit status e.g. 22.24 or 0
STATUS STATUS STATUS STATUS STATUS STATUS STATUS STATUS STATUSSTATUS STATUS
6.1 Symbol
Alarm Route 4
output to alarm
input from alarm group module o4 destination module
G
D
1 E
enable
ALARM ROUTE
Enable
parameter
Connective
6.4 Parameters
6.4.1 Inputs and Outputs
Alarm Group: (source) The alarm group input can only be connected to an alarm group module output. This specifies
the group of alarms that the route module will deliver to the destination module(s). If connected to an alarm group module
output the output’s details will be shown on the web page.
Enable: (digital, source/constant) This input can be soucrced from a digital output or set to a constant status. If connected
to a module’s digital output, the output’s details will be shown on the web page. This input enables the connection
between the group and the destination if set to 1 (0 disables it). This allows strategy (comms or manual intervention)
to select the destinations to which alarms are routed. For example an alternative destination may be used if the first one
fails (see examples in Pt. 1 section 12.6.1). The enable input value is set 1 by default which enables the route.
Label: (characters constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
Page: (analogue, constant) SET file strategy page number on which module appears.
* This source/constant parameter cannot be changed via the web page if it is set as a source.
However in IQ3 analogue node modules are provided to fulfil several functions:
1. IC Comms for use with devices using text comms to nodes (e.g. Wireless Sensor Receiver).
2. Provision of a constant value shared between several module inputs.
3. Compatibility with Supervisors set up for IQ1 or IQ2 strategies.
4. Detection of alarm status bits from function module outputs.
Analogue nodes appear on the strategy page and are automatically event driven; they cannot be allocated a sequence
step. Since an analogue node is always event driven, its output should never be connected back to its input. SET prohibits
this.
Connectives
7.4 Parameters
7.4.1 Inputs and Outputs
Value: (analogue, source/constant) An analogue input which can either be a source or a constant. If connected to an
analogue output it will expose the status bits accompanying the analogue value (e.g. from function module). If configured
as a constant then it can provide a constant value for use by other modules. If connected to a module’s analogue output
the output’s details will be shown on the web page.
Alarm Status: (characters, status) The status attached to the analogue value.
The least significant four alarm bits (ROLH) correspond to the four alarm bits generated by the sensor module (see Pt.
2 section 28.5.6).
The web page shows 8 status bits; these can be accessed by text communications. Only the four lowest bits (ROLH)
are available as connectives and can be used in the strategy:
i.e.
OOOOOIOI
where: Bit 3 = Read (R)
Bit 2 = Out of Limits (O)
Bit 1 = Low (L)
Bit 0 = High (H)
Read Alarm (R): The sensor cannot obtain a value from the analogue to digital converter because the input is over range
(e.g. outside voltage 0 to 10 V).
Out of Limits (O): The sensor value is outside the range specified by the Top and Bottom or range values set up in the
associated sensor type module.
Low (L): The sensor value is below the sensor’s low limit.
High (H): The sensor value is above the sensor’s high limit.
Status bits 4 and 5 can be set up by an IC Comms from an IQ2, but can only be accessed by text comms.
Output: (analogue, output) The analogue value available of the output; it is equal to the input value. If connected to a
module’s analogue input the input’s details will be shown on the web page. This analogue output is shown as a
connective in SET (AnD where A= analogue node, n = analogue node number, and D=destination, e.g. A1D).
Read Alarm: (digital, output) The read alarm digital status bit (bit 3). If connected to a module’s digital input the input’s
details will be shown on the web page. This digital output is shown as a connective in SET (AnR where A= analogue
node, n = analogue node number, and R=Read, e.g. A1R).
Outside Limits Alarm: (digital, output) The out of limits alarm digital status bit (bit 2). If connected to a module’s digital
input the input’s details will be shown on the web page. This digital output is shown as a connective in SET (AnO where
A= analogue node, n = analogue node number, and O=Outside limits, e.g. A1O).
Low Alarm (SET: Low): (digital, output) The low alarm digital status bit (bit 1). If connected to a module’s digital input
the input’s details will be shown on the web page. This digital output is shown as a connective in SET (AnL where A=
analogue node, n = analogue node number, and L=Low, e.g. A1L).
High Alarm: (digital, output) The high alarm digital status bit (bit 0). If connected to a module’s digital input the input’s
details will be shown on the web page. This digital output is shown as a connective in SET (AnH where A= analogue
node, n = analogue node number, and H=High, e.g. A1H).
Label: (characters, constant) The label shown in the module symbol on the SET strategy page and in the Web pages.
Page: (analogue, constant) SET file strategy page number on which the module appears.
TYPE
Parameter Web comms Default
SET co d e Low High
page
Controller Parameters
Label R/W R/W $ 0 30 null The module identifier used on the strategy
CONST
pages and in web pages.
characters
SOURCE/CONST
-20
Value R/W R/W* V 10 10+20 0.0 The analogue value held by the analogue
node. Can be connected to an analogue
output. If not connected it acts as a
constant.
Alarm Status - R/W S 0000- 11111- 00000000 The alarm status associated with the value.
STATUS
0000 111
OUTPUT
Output R/W R D 10-20 10+20 0.0 The output value. Can be connected to an
analogue input.
Read Alarm R/W R 0 1 0 OUTPUT The read alarm output. Can be connected
to a digital input.
Out of Limits Alarm - R/W 0 0 1 0 The outside limits alarm output. Can be
OUTPUT
* This source/constant parameter cannot be changed via the web page if it is set as a source.
Set downloads the connections to the IQ3 controller, but the connectives as such only exist in SET. If the strategy is
uploaded for backwards engineering, then the connectives have to be redefined (see Pt. 1 section 6.4.1).
The connectives are explained more fully in the IQ3 Configuration section (Pt. 1 section 5.14), but a summary is given
here.
A ‘from connective’ (known as ‘Connective’ in SET) is shown on the SET page as an analogue or digital node with
the source module reference (e.g. R1p). It is set up by selecting the source from the Connectives dialogue box. This box
shows all connectives from non-strategy modules, and the main connectives from strategy modules. Clicking on the main
connective shows the other available connectives from that module in the supplementary dialogue box below (see section
8.2 below).
Note that the Connectives dialogue box also contains some destination connectives for the XNC interface module; these
are necessary as the XNC interface module does not appear on the strategy page.
A ‘to connective’ is added to the SET page to indicate that an output is connected to a module on another page.
8.1 Symbol 10
0 E G5
A1R
Rd - J or
A1R F K or
From Page 2 D G5D
L or
0 G M
0 H To Pages(s)
COMB
J Comb.
K Comb.
L Comb.
M Comb. to connective
from connective
Other
connectives for
selected
strategy module
(e.g. S1)
List of (from) Connectives in SET
9.1 Symbol
Output bit 0
B2 a
,0 b
,1 c
,2
,3 d
,4 e
,5
,6 f
,7 g
Byte h
Output bit 7
9.2 Web Page
Digital Byte Overview Page
9.4 Parameters
9.4.1 Input
Value: (characters, status) The digital byte status in binary form (e.g. OOOOIIII, Bit 7 through to Bit 0) showing all 8 bits
State: The SET equivalent of the Value but in decimal form (e.g. equivalent to above value would be 15)
Note that the input is normally set up by an IC Comm, but can be set up manually from SET or web page; this could be
used to test the strategy in the absence of the IC Comm.
Label: (characters, constant) The label shown in the module symbol on the SET strategy page and in the Web pages.
Page: (value, constant) SET file strategy page number on which the module appears.
Comments
Accessibility Range
Text
TYPE
Parameter comms Default
Web co d e
SET Low High
page
Controller Parameters
Label R/W R/W $ 0 30 null The module identifier used on the strategy pages
CONST
and in web pages.
characters
P age R/W R/W P 0 255 0 Number of page containing module in SET file.
10.1 Symbol
External Digital Input Internal Digital Input
IO Module number
IO Channel number
State In Alarm
parameter
additional parameters
Connectives
A count (number of starts) is kept of the number of transitions from 0 to 1 for each channel. A cumulative sum of the
time for which the input is in the on state (cumulative hours run) is also kept. Both these are maintained by the low level
software associated with the input channel.
The number of starts, hours run, and current state are communicated to the digital input module on the first and second
transitions. The second transition initiates a hold off for one second, so that if a third transition occurs within the one
second hold off, the values will not be communicated to the digital input module until that one second hold off has elapsed.
The Time of Hours Run Reset parameter is the last time (date and time) at which the hours run was reset to zero.
The hours run count and the number of starts can be displayed on the supervisor and used in the strategy.
A counter logic module can access the number of starts. An hours run logic module can access the hours run.
direct transfer
If a counter logic module is connected directly to an external digital input as shown above, the digital input module number
of starts is transferred directly to the counter module cumulative count output without scaling when the module is
serviced.
If the counter module is reset this will reset both the counter module cumulative count output and the digital input number
of starts. Similarly if the digital input number of starts is changed, this will be copied to the counter module cumulative
count output.
This special relationship between the two modules exists mainly for compatibility with IQ2 series controllers although
it also enables the number of starts to be reset, and for an input rate to be generated.
direct transfer
If an hours run logic module is connected directly to an external digital input as shown above, the digital input module
Hours Run is transferred directly to the hours run hours output when the module is serviced.
If the hours run module is reset this will reset both the hours run module hours output and the digital input Hours Run.
Similarly if the digital input Hours Run is changed, this will be copied to the hours run module hours output.
Again, this special relationship between the two modules exists mainly for compatibility with IQ2 series controllers,
although it also enables an hours run interval exceeded output to be generated.
The external digital input module has additional parameters to define the details of the external channel (I/O module,
channel number). If the channel number is set to non-zero, the status of the input is read only. If the channel number
is set to zero the input becomes a constant (rather than a source) and its value may be changed on the controller’s digital
input web page (but not in SET).
The cumulative hours run and number of starts operate at a lower level than the sequence table, or event driven timings
as described above.
An internal digital input module can be sourced from a digital output, or have its input set to a constant (i.e. on or off).
In this way the otherwise normally ‘invisible’ internal variable can be seen at the supervisor as a labelled value and have
an alarm associated with it. The is true of IQView, but the 963 can see any internal value by setting up a schematics page,
however, the digital input would be visible without any extra supervisor configuration.
Although Hours Run and Number of Starts are shown in the digital input module display, for an internal digital input,
they are not updated and remain at their original values; they can be produced for an internal digital by using hours run
and counter logic modules respectively.
input
Alarm Sub-module
Alarm State
Required State Compare Delay
Number of Starts
Starts
Count
Hours Run
Hours
Count
This diagram shows the way in which the various parameters described below interoperate.
The output State is normally connected to the input, but if the Override Output is set on, then the output State is connected
to the Override Status.
The Alarm Sub-module compares the output State with the Required State (if Enabled), so if the Override Output is set,
it will check the Override Status with the Required State. This then becomes the Alarm State if it is present longer than
the Alarm Delay. If the alarm is Enabled, it then sets the In Alarm state and it will the be reported to the alarm group module.
When the alarm clears the clear alarm will be reported if the alarm is Enabled and the Clear Enable is also set.
The Starts Count and Hours Count functions use the direct output of the digital input module as source so Number of
Starts and Hours Run are not affected by the Override function.
The BACnet alarm state transitions are explained in Pt. 1 section 12.7.4.2. The digital
input alarm (DI=0 or DI=1) is considered to be an OffNormal state and there are no Fault Normal
States, so the only transitions between states are To Normal and To OffNormal.
The transition from no alarms present into digital input alarm will generate a ‘From
Normal to OffNormal’ transition.
The clear of the digital input alarm would then generate a ‘From OffNormal to Normal’
transition.
The BACnet Event Time Stamps array contains three values which are the times (date
and time) that the last transitions into the BACnet alarm states occurred: digital input
n1: Time into OffNormal DI=0 or DI=1
n2: Time into Fault (always zero)
n3: Time into Normal OffNormal
10.8 Parameters
10.8.1 Inputs and Outputs
Hardware Module (SET: I/O Module): (analogue, constant) This parameter only exists in an external digital input module.
It defines the hardware I/O module which contains the digital input channel. Zero refers to the main IQ3 unit and module
numbers 1 to 15 can select an external I/O module.
Hardware Channel (SET: I/O Channel): (analogue, constant) This parameter only exists in an external digital input
module. It defines the hardware digital input channel which the digital input is monitoring. The range of channel numbers
available depends on the type of main IQ3 or I/O module used (see Pt. 2 section 16.6). If the channel number is set to
zero the input becomes a constant (rather than a source) and its value may be changed on the controller’s digital input
web page (but not in SET).
Source (SET: Status- internal digital input only): (digital, source/constant) This gives the current status of the input to
the digital input module. For an external digital input it is read only.
For an internal digital input it defines the source of the input; it can either be sourced from a digital output, or set to a
constant value (0 or 1). If connected to a module’s digital output, the output’s details will be shown on the web page.
State: (digital, output) The current digital input module output state. It includes the effect of the override parameter. If
connected to a module’s digital input, the input’s details will be shown on the web page.
This output is shown as a connective in SET (i.e. InS, where I = digital input module, n = digital input module number,
S = status, e.g. I1S).
Hours Run: (analogue, output) The cumulative number of hours for which the digital input source has been set to 1.
If connected to a module’s analogue input, the input’s details will be shown on the web page.
This output is shown as connective in SET (i.e. InH, where I = digital input module, n = digital input module number,
H = Hours run, e.g. I1H).
Number of Starts (SET: Starts): (analogue, output) The number of times the digital input source has transitioned from
0 to 1. If connected to a module’s analogue input, the input’s details will be shown on the web page.
This output is shown as a connective in SET (i.e. InN, where I = digital input module, n = digital input module number,
N = Number of starts, e.g. I1N).
Time of Hours Run Reset (not available in SET): (characters, status) The time that the cumulative hours run was last
reset to zero. In date and time format: yyy-mm-ddThh:mm:ss.
BACnet Event Time Stamps (not available in SET or on web pages): This is an array of three values (text comms codes:
n1 to n3) which hold the times of the last transitions into the BACnet alarm states OffNormal, Fault, and Normal. In date
and time format: yyy-mm-ddThh:mm:ss.
Required State: (digital, source/constant) This is the good (non-alarm) state of the input; it can either be sourced from
a digital output, or set to a constant value (0 or 1). If connected to a module’s digital output, the output’s details will
be shown on the web page.
In Alarm: (digital, status) This value indicates whether the digital input is in alarm, or has no alarm. It has accompanying
text shown in the list below which is shown on the digital input overview page in the ‘alarm’ column.
0 = No alarm
1 = Digital Input alarm
The alarm state is shown if the input is in alarm, i.e. the digital input State (this is the State parameter above, which includes
the effect of the override parameter) has been in the alarm condition for longer than the alarm delay time, and the alarm
is enabled to be reported. It will be set back to 0 immediately the alarm clears.
Digin: This indicates the Alarm State as defined below. Clicking on Digin on the web page will display the digital input
alarm sub-module. The way in which the sub-module declares alarms and clear alarms is described in section Pt. 1 section
13.4.1
Alarm State (SET: State Alarm): (digital, output) This will be 1 if the digital input State (this is the State
parameter above, which includes the effect of the override parameter) has been different to the Required State,
for longer than the alarm delay time. It takes no account of alarm enable.
If connected to a module’s digital input, the input’s details will be shown on the web page. This output is shown
as connective in SET (i.e. Ind1S, where I = digital input module, n = digital input module number, d1 = digital
input sub-module 1, S = status, e.g. I1d1S).
Enabled (SET: State Alarm Enable): (digital, source/constant) This is an input to the sub module which will
enable or disable the reporting of the alarm. Once the Alarm State is true the alarm will be reported; when the
alarm clears a clear alarm will be reported (if Clear Alarm below, is also enabled). This input can either be sourced
from a digital output, or set to a constant value (0 or 1). If connected to a module’s digital output, the output’s
details will be shown on the web page.
Alarm Sent: (digital, status) This indicates that the alarm has been sent to the group module. This will only
happen if the Alarm State has been present for longer than the Alarm Delay, and the alarm is Enabled to be
reported.
Alarm Delay (secs): (analogue, source/constant) This is the delay for which the input must be in alarm before
the Alarm State is declared. The alarm delay for the clear alarm state is always zero. This delay can either be
sourced from an analogue output, or set to a constant value. If connected to a module’s analogue output, the
output’s details will be shown on the web page.
Time in Alarm (secs): (analogue, status) This is the elapsed time since the Alarm State commenced.
Alarm Group (SET: Status Group): (analogue, constant) This is the alarm group module to which the alarm
will be sent.
Clear Alarm (SET: Clear Enable): (digital constant) This is an input to the sub module which will separately
enable or disable the reporting of the clear alarm. Once the Alarm State is true and the alarm is enabled, the
alarm will be reported; when the alarm clears a clear alarm will be reported only if Clear Alarm is also enabled.
This input can be set to a constant value (0, disable or 1, enable).
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
The digital input label can be used as an item attribute for text communications. This is explained for IC Comms in Pt.
2 section 15.4.
Special characters are as follows:-
? * .
The following characters should not be used in a label
\ / ( { ; , :
Single letters should also be avoided (e.g. S, K, W)
Page: (analogue, constant) SET file strategy page number on which module appears.
Disable Module (SET: ModuleState - Enabled/Disabled): (digital, source/constant) This input will disable the module,
i.e. prevent it from being serviced. Its internal states and output will be maintained at their values prior to disabling. This
input can either be sourced from a digital output, or set to a constant value (0 or 1). If connected to a module’s digital
output, the output’s details will be shown on the web page.
Override Output (SET: Override Enable): (digital, source/constant) This input will override the output to the override
status set in the next parameter. Note that the override also operates on the state used for alarm checking purposes. This
input can either be sourced from a digital output, or set to a constant value (0 or 1). If connected to a module’s digital
output, the output’s details will be shown on the web page (see Pt1. section 5.7).
Override Status (SET: Override): (digital, source/constant) This input is the status to which the output is overridden
when the override condition is present. This input can either be sourced from a digital output, or set to a constant value
(0 or 1). If connected to a module’s digital output, the output’s details will be shown on the web page.
Sequence Table: (digital, status) The digital input module is event driven. It cannot be put in the sequence table. Sequence
table 0 on the web page indicates that the module is event driven.
TYPE
Parameter comms Default
Web co d e
SET Low High
page
Controller Parameters
Label R/W R/W $ 0 30 null The module identifier used on the strategy
CONST
pages and in web pages. This can be used
as an item attribute for text comms and has
restricted characters see 10.7.4 above
characters
OUTPUT
State R R/W S 0 1 0 The state of the module output. Can be
connected to a digital input.
SOURCE/CONST
Disable Module - R/W* ~ 0 1 0 State of disable input. Can be connected to
(SET: Module State, a digital output.
Enabled/Disabled)
ly set up in 0=external
SET) 1=internal
SOURCE/CONST SOURCE/CONST SOURCE/CONST SOURCE/CONST
Override Status R/W R/W* v 0 1 0 The status to which the digital input module
(SET: Override) output state will be overridden. Can be
connected to a digital output.
Source R/W† R/W*† I 0 1 0 The state of the input to the digital module.
(SET:Status - only For internal digital input only, can be
for internal digital connected to a digital output.
input)
Required State R/W R/W* R 0 1 0 The required (non-alarm) state of the digital
input. Can be connected to a digital output.
1 to 9 = 1 to 9
A=10
B=11
C=12
D=13
E=14
F=15
Hardware Channel R/W R/W c 1 32 1 (External only)
CONST
* This source/constant parameter cannot be changed via the web page if it is set as a source.
† For external digital inputs this parameter is sourced from the input channel if channel number is non-zero; if channel number
is zero, the source may be set to a constant value (using web pages, not SET)
TYPE
Parameter comms Default
Web co d e
SET Low High
page
Controller Parameters
STATUS
present for longer than the delay time,
and the alarm is enabled(0= no alarm,
1=digital input alarm)
(Digin) - R d1(S) 0 1 0 Indicates the alarm condition has been
OUTPUT
Alarm State present for longer than the delay time
(SET: State Alarm) (independent of alarm enable). Can be
connected to a digital input.
SOURCE/CONST SOURCE/CONST
Enabled R/W R/W* d1(E) 0 1 0 This input enables the alarm to be
(SET: State Alarm reported. Can be connected to a digital
Enable) output.
Alarm Sent - R d1(K) 0 1 0 Set true if the alarm has been sent to the
alarm group module
Alarm Delay R/W R/W* d1(D) 0 172800 0 The time for which the alarm must be
(secs) present before the Alarm State is
STATUS
Alarm Group R/W R/W d1(G) 0 500 1 The alarm group module to which the
alarm is sent
Clear Alarm R/W R/W m1(C) 0 1 1 A separate enable for the clear alarm.
OUTPUT STATUS OUTPUT CONST
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
Parameter comms Default
Web co d e
SET Low High
page
Controller Parameters
CONST
P age R/W R/W p 0 255 0 Number of page containing module in
SET file.
CONST
X R/W R/W x 0 255 0
X co-ordinate of module on SET page.
co-ordinate
CONST
Y R/W R/W y 0 255 0
Y co-ordinate of module on SET page.
co-ordinate
SET Associated Parameters
Details R/W - - 0 65535 blank Additional information about the module
characters that appears in SET
In display panels and smaller PCs the display and directory modules can be used for generating lists of parameters for
each item of plant.
In IQ3, GraphIQs (graphical display web pages) are created from the Display and Directory modules’ structure. A directory
module can have a graphical backdrop onto which the display modules’ text can be placed. The display modules have
x and y coordinate parameters which enable them to be located at appropriate points in front of the backdrop. The directory
module also has a backcolour parameter which defines a colour to be used as background if there is no backdrop or the
browser cannot access the backdrop file.
The display module can be set to either static or dynamic. The dynamic items are automatically refreshed and the refresh
rate can be defined. Static items can be used for labels (on GraphIQs pages only).
The use of display and directory modules is explained in Pt1. section 10.5.
The directory module does not appear on the strategy page and does not need to be sequenced.
11.2 Hierarchy
Directory modules provide the hierarchy to enable the user to select the units of plant and items he wants to see (i.e.
provide a Navigator or Guide).
Directory modules have a paRent parameter which refers to the directory module above it in the hierarchy. Directory
module 1 is always the root of the structure (and its paRent should be set to 1 as paRent =0 is taken to mean the module
is not set up).
For example:
@1
directory 1 $ Main Plant
paRent 1 PIN 0
Main Plant
@2
directory 2 $ Boilers
+ Boilers paRent 1 PIN 50
@3
+ Chillers directory 3 $ Chillers
paRent 1 PIN 50
The above diagram shows three directory modules referred to by the @ symbol which is the text comms symbol for a
directory module. Directory 1 is at the top of the hierarchy (root). The two directory modules @2, @3, have directory
module 1 as the parent so form the second level of hierarchy i.e. the next level below directory 1.
This structure can be expanded by having further directory modules using @2 or @3 as parents.
e.g.
Main Plant
+ Boilers
@4 $ Boiler 1
paRent 2 PIN 50
+ Boiler 1
@5 $ Boiler 2
+ Boiler 2 paRent 2 PIN 50
+ VT Circuit
@6 $ VT Circuit
paRent 2 PIN 50
+ Chillers
The IQ will then reply with the label and paRent for each directory module. A display similar to that shown below can
then be created.
11.3 Items
Display modules enable items to be included in the views. Each display module has a paRent parameter which enables
it to be attached to a directory module.
In the above IQView display the Directory module ‘Ventilation’ has been selected. The three display modules shown
in the right hand portion of the display have the ‘Ventilation’ directory module as their parent.
The Item within a dynamic display module may be selected from the presentation modules.
S Sensor
I digital Input
K Knob
W sWitch
D Driver
Z time Zone
The item can also be set to various other types (see Pt. 2 section 12.4.3).
So when a user logs on to the supervisor and selects display modules he will only see the units of HVAC equipment and
items appropriate to his level.
11.5 GraphIQs
The GraphIQs pages (graphical web pages) for display in a web browser are defined by the display and directory
modules. There are additional parameters in these modules that need to be set up to create the GraphIQs pages.
The creation and use of the GraphIQs pages is described in Pt. 1 section 10.5.
These pages enable the display items (modules) to be placed on a Backdrop bitmap.
Static display items can have hyperlinks to other web pages, and dynamic display items can have hyperlinks to the appropriate
modules’ details web pages.
The extra parameters required for GraphIQs pages are ignored when the pages are used for display by a supervisor or
display (e.g. 963, IQView, 916, or SDU).
The above Display and Directory Setup dialogue box enables the Directories and Displays to be created in SET. Available
dynamic display items are shown in the Display Items list on the left. The directory structure and the associated display
modules are shown in the central Display and Directory View. Use of Directory and Display modules to create GraphIQs
pages is described in Pt1. section 9.5.1.
Right clicking on the particular directory icon in the Display and Directory View will produce the styling dialogue box
shown below. A similar styling box is shown by right clicking on a display item.
AHU1
The Select Colour Dialogue box enables either basic or custom colours to be selected. A custom colour can be selected
by choosing the Hue and Sat(uration) by dragging the ‘+ cursor’, and then dragging down the arrow on the Luminosity
scale. The Red, Blue, and Green components of the selected colour are shown on the directory module web page.
11.8 Parameters
11.8.1 Basic Parameters
These basic parameters are those used both for supervisors and displays and for GraphIQs pages
Label (SET: Title): (characters, constant) This is the label used for the directory module
User Level (SET: Pin Level): (analogue, constant) This is the PIN level at which the user must be logged on before the
directory becomes visible
Parent: (analogue, constant) This is the number of the directory module which is the parent of this module (i.e above
it in the hierarchy). The Root is always Directory 1, so a parent of 1 means that this module is in the next level below the
root. Directory 1 should itself have its root set to 1 as a parent of zero signifies that the directory module is not set up.
Backdrop: (characters, constant) This parameter is the filename of the bitmap to be used as a backdrop to the web page.
The bitmap is stored in the C:\Set projects\Project name\Backdrops directory in SET (see Pt.1 section 6.1.3) and can be
downloaded to the controller as part of the strategy download; it can also be uploaded from the controller to SET (see
Pt1. section 6.4.4).
Backdrops can be either .JPG or .GIF files, and SET allows a maximum backdrop size of 200 kbytes, and a maximum
capacity for all backdrops of 2 Mbytes. It will warn if a backdrop exceeds 100 kbytes. They should be sized to fit the
screen being used to display the backdrop (see width, height, and page size below).
Change (backdrop): In SET selecting the change backdrop button produces a box listing available backdrop files
from which the required backdrop can be selected (see 11.7 above).
Back Colour (SET: Background Colour): (characters, constant) This parameter defines the background colour to be used
if there is no backdrop file or for some reason the browser cannot access the backdrop file. In SET this parameter is either
to select or de-select a colour, the actual colour is selected using the Change button
Change (colour): In SET selecting the change colour button produces a colour selection box enabling the colour
to be selected from either a list of standard colours, or a custom colour (see 11.7 above).
Refresh rate: (analogue, constant) This defines the time in seconds between refreshing all the values on the web page.
Width: (analogue, constant) The width of the page in pixels (see page size below)
Height: (analogue, constant) The height of the page in pixels (see page size below)
Page size: This parameter appears only in SET and is the width of the page by its height (e.g. a width of 1024 pixels
and a height of 768 pixels gives a page size of 1024 by 768). In SET there is a dropdown box which enables selection
of either Custom size or one of three standard sizes (Custom, 640x480, 800x600, 1024x768).
The page size should be set one size down from the screen being used to display the webpage, so that it appears inside
the browser. The backdrop should be sized to match the selected page size.
If the GraphIQs pages are to appear on different size PCs, the user could select the smallest size, or select the size used
by most of the PCs and let the users with smaller screens (e.g. laptops) use the automatic scroll bars to scroll round the
page. A larger backdrop than the selected screen size will be clipped (top left corner).
TYPE
co d e
SET Web Low High
page
Controller Parameters
Label R/W R/W $ 0 30 null The module identifier used on the strategy
pages and in web pages. SDU will truncate
CONST
label to first 20 characters
characters
Parent R/W R/W R 0 500 0 The parent directory for this directory. Set
*This HTML RGB colour code shows each colour as two hex characters reflecting the colour intensity in the range 0
to 255. This is set by selecting the colour in the SETcolour dialogue box.
The way in which this is done is explained in Pt.1 section 9.5, and Pt. 2 section 11.
Display and Directory modules can be used both for displays on supervisors and display panels, and for display on a
web browser as GraphIQs pages .
The display module can be set to either static or dynamic. The dynamic items are automatically refreshed and the refresh
rate can be defined. Static items can be used for labels (in GraphIQs pages only).
On GraphIQs pages, static display items can have hyperlinks to other web pages, and dynamic display items can have
hyperlinks to the appropriate modules’ details web pages.
The extra parameters required for GraphIQs pages are ignored when the pages are used for display by a supervisor or
display (e.g. 963, IQView, 916, or SDU).
Display modules enable items to be included in the views. Each display module has a paRent parameter which enables
it to be attached to a directory module.
The Item within a dynamic display module may be selected from the presentation modules.
S Sensor
I digital Input
K Knob
W sWitch
D Driver
Z time Zone
They can also be set to show other modules (see 12.4.3 below)
The display modules a user can see depend on his PIN level. So when a user logs on to the supervisor and selects display
modules he will only see those items appropriate to his level.
The display module does not appear on the strategy page and does not need to be sequenced.
12.4 Parameters
12.4.1 Basic Display Module Parameters
These basic parameters are those used both for both dynamic and static display modules, and when used for both
supervisors and displays and for GraphIQs pages
User Level (SET: Pin Level): (analogue, constant) This is the PIN level at which the user must be logged on before the
display item becomes visible
Parent (analogue, constant): This defines the directory (page) in which this item is included
Left Position (SET: X): (analogue, constant) The left or x position of the top left corner of the item in pixels.
Top Position (SET: Y): (analogue, constant) The top or y position of the top left corner of the item in pixels. Notice that
the top (Y) position increments downwards
X position
0
0
page
Y position
Display Subtype: (analogue, constant) This is set to either Dynamic Text or Static Text in SET by selecting either a dynamic
or static display item respectively.
In the SET Display and Directory Setup box the items are shown under their parent directory and are distinguished by
different icons.
dynamic display item
Fore Colour (SET: Foreground Colour): (analogue, constant) The colour of the text on the graphical display page. Set
by default to be black.
In SET this parameter is used either to select or de-select a colour, the actual colour being selected using the Change
button
Change (colour): In SET selecting the change colour button produces a colour selection box (see Pt. 2 section
11.7) enabling the colour to be selected from either a list of standard colours, or a custom colour. The Red, Blue, and
Green components of the selected colour are shown on the directory module web page.
Back Colour (SET: Background Colour): (analogue, constant)The colour of the background to the text on the graphical
display page. Set by default to be transparent.
In SET this parameter is used either to select or de-select a colour, the actual colour being selected using the Change
button
Change (colour): In SET selecting the change colour button produces a colour selection box (see Pt. 2 section
11.7) enabling the colour to be selected from either a list of standard colours, or a custom colour. The Red, Blue, and
Green components of the selected colour are shown on the directory module web page.
Font Name (SET: Font Type): (analogue, constant)The type of font used to display the item. This can be set to either:
Serif
Sans-Serif
Cursive
Monospace
IQ3 Default Font
Width: (analogue, constant) The width of the displayed text box. If set to zero the width will be set automatically to suit
the text. If set non-zero it defines the width of the text box in pixels.
In SET the width can only be set if the ‘Auto’ check box is unchecked.
Auto: In SET checking this box sets the width to zero which defines automatic width setting, and greys out the
width entry box and the text alignment box.
Align (SET: Text Alignment): (analogue, constant) The alignment of the text within the text box. It can only be set up
if the width is set manually (not automatically). It can be set to either:
Left Aligned
Centre
Right Aligned
Item (SET: Item Reference): (characters, constant) This is the code to be used for the item whose value is to be displayed.
Using the SET Display and Directory Setup dialogue box, an item can be dragged from the display item list into the
required directory. This will automatically create a display module for that item.
Such items are limited to the presentation modules:
Sensor
Digital Input
Knob
Switch
Driver
Time Zone
Having created the display module it can then be edited, and the item can be changed to any of those above plus any
of the following:
Alarm Destination, Alarm Group, Alarm Route, Analogue Node, Digital Byte, Directory, Display, Function,
I/O Module, IC Comms, Logic, Loop, OSS, Plot, Sensor Type, Time module, User, Virtual CNC
Note that these additional types are only for use on GraphIQs pages. Their use in supervisors and displays may cause
problems.
If the basic item reference is used it will display the item’s overview parameters, so for S1, the display will show sensor
1’s label, value, units. A full list of overview parameters is given below.
Module Overview Parameter
If the parameter is fully specified it will only show that parameter, i.e S1$ will display the label of sensor 1
In Alarm Colour: (characters, constant) The colour in which the dynamic display item will be displayed when the item
is in alarm. If not set up the text colour will be the same as the foreground colour.
In SET this parameter is used either to select or de-select a colour, the actual colour being selected using the Change
button
Change (colour): In SET selecting the change colour button produces a colour selection box (see Pt. 2 section
11.7) enabling the colour to be selected from either a list of standard colours, or a custom colour. The Red, Blue, and
Green components of the selected colour are shown on the directory module web page.
Clickable: (digital, constant) This selects the ability for the user to click on the value so that it will jump to the item’s
details page. For example clicking on Sensor 1 will jump to sensor 1’s module details page (see Pt. 1 section 9.3.2). This
is set on (I) to enable the jump and off (O) to disable the jump.
In SET the function is enabled by checking the ‘Make a link to the item’s detail page’ check box.
These parameters apply to static display modules only. They only apply to GraphIQs pages as Static display items are
only used in GraphIQs pages.
URL (SET: Link Reference): (characters, constant) This parameter can be set up with a hyperlink, so that when the static
text is clicked on, the display will jump to another page.
In SET, by default the link type is set to ‘Unknown Link Type’ with a blank field
Change : In SET selecting the ‘Change’ Link Reference button produces drop down list enabling the selection
of the link type from the following types:
Unknown Link Type
Email link
Website link
Directory link
Unknown Link Type: This is for a URL type not covered by the other types (e.g FTP site).
Email Link: This should be set to an email address (e.g. [email protected]). When the static item
is selected, the computer’s email application will be loaded with a new email with this defined email
address set up. SET will automatically start the field with ‘mailto:’.
Website Link: This is for a link to an external website (e.g http://www.trend-controls.com). It can be to
a directory link in another IQ3 in which case the directory links below apply (e.g. http://
www.my_contollers_name/GraphIQs/Boilers/Boiler1/index.htm). SET will automatically start the field
with ‘http://’.
Directory Link: This is for a link to one of this controller’s web pages. SET will automatically start the
field with ‘trendModule:’.
Details of links to different web pages are given in the table below:
TYPE
co d e
SET Web Low High
page
Controller Parameters
User Level R/W R/W P 0 99 0 The user level at which the user must be
CONST
(SET: PIN level) logged on before the display item
becomes visible. Zero means no PIN
required
Left Position R/W R/W X 0 1600 0 (GraphIQs only). The position in pixels of
(SET: X) the top left of the text on the left to right
axis on the web page.
Top Position R/W R/W Y 0 1200 0 (GraphIQs only). The position in pixels of
(SET: Y) the top left of the text on thetop to bottom
axis on the web page.
Display Subtype R/W R/W T 1 2 se t b y (GraphIQs only).
CONST
(SET: Foreground HTML colour page. Set by default to black In SET the
Colour) format : colour is checked or unchecked, and the
#RRGGBB* required colour is selected by using the
Change button
Back Colour R/W R/W B standard blank (GraphIQs only) The background colour to
CONST
(SET: Background HTML colour the text. Defaults to transparent. In SET the
Colour) format : colour is checked or unchecked, and the
#RRGGBB* required colour is selected by using the
Change button
Font Name R/W R/W N 0 5 0 (GraphIQs only) The font used to display
(SET: Font Type) (serif) the text:
CONST
0 = Serif
1 = Sans-serif
2= Cursive
3= Monospace
4= IQ3 Default Font
CONST
Font size R/W R/W S 6 72 12 (GraphIQs only) The font size in points
used in the displayed text:
Width R/W R/W W 0 1600 0 (GraphIQs only) The width of the text box in
CONST
*This HTML RGB colour code shows each colour as two hex characters reflecting the colour intensity in the range 0
to 255. This is set by selecting the colour in the SETcolour dialogue box.
TYPE
co d e
SET Web Low High
page
CONST
Reference) referencefor item in dragging the item from the item list.
sensor, driver, SET e.g. S1 gives label, value, units
digital input, S1($) gives label only
knob, switch.
See 12.4.3
CONST
In Alarm Colour R/W R/W A standard foreground (GraphIQs only) The colour of the tex if the
HTML colour colour item is in alarm. Defaults to foreground
format : colour. In SET the colour is checked or
#RRGGBB* unchecked, and the required colour is
selected by using the Change button
CONST
Clickable R/W R/W C 0 1 (GraphIQs only) Setting this to 1 enables a
hyperlink to the item's module details
page.
Static Display Module Controller Parameters
CONST
URL R/W R/W U valid link blank (GraphIQs only) A link reference to either:
(SET: Link reference (see Unknown, Email, Website, or Directory
Reference) 12.4.5) type (see 12.4.5)
*This HTML RGB colour code shows each colour as two hex characters reflecting the colour intensity in the range 0
to 255. This is set by selecting the colour in the SETcolour dialogue box.
4 Raise Lower with End Stop Analogue Analogue and external relays or 2 digital channels
7 Raise Lower continuous Analogue Analogue and external relays or 2 digital channels
SET icons
Each driver type has two output channels each of which may be assigned to any of the hardware outputs of the IQ.
The driver module does appear on the strategy page and can be either sequence table driven, or event driven.
Connectives
Hours Run
Hours
Count
Invert
Override Output HOA State
The Value parameter monitors the input to the driver algorithm (digital for digital driver, analogue for all other drivers).
If the input is outside the range 0 to 100 it will be clipped to be within that range (but see special action of negative input
in section 13.6.5 below)
The driver algorithm drives the in phase and anti-phase outputs, and its operation varies with driver type.
The Invert input causes a logical inversion between the driver algorithm outputs and the output channels; the actual
effect on the outputs varies with driver type.
The Starts Count and Hours Run functions are shown here in the generic section although they are not present on
analogue and raise/lower driver types. These two functions use the driver algorithm in phase output (uninverted) as
source so that they take into account the override function.
D11l E G13
Digital Input 6
0 F
I6 S D
0 m I6S G
0 c
EXTERNAL 0 H
0 Override Enable READBK
0 Override Value 20 Grace Time
In the above, example, the output from loop L2 is driving binary hysteresis driver D11, whose output is used to drive
a pump ON or OFF through digital output 11. Digital input 6 accepts input from a flow switch. When the pump is in the
OFF state, the flow switch should also be in the OFF state and with the pump in the ON state, the flow switch should
be in the ON state. The readback logic module compares the two signals at its inputs E and G; when they are same i.e.
both ON or both OFF, no action is taken. However, if, after the grace time (20 s) has elapsed, the pump is driven ON and
the flow switch is OFF, or vice versa, there is a fault in the system and the readback module G13 output will go true.
The readback logic module output is connected to the driver readback alarm input.
If driver alarm condition is present for longer than the driver’s readback alarm delay then the driver’s Readback Alarm
State is set true (driver’s readback alarm digital output is true).
Note that the driver’s readback alarm delay is not necessary as its function can be achieved by adjusting the readback
logic module’s grace time, so should be left at zero. However, for BTL compliance a digital driver’s readback alarm
delay must be used, and the readback logic module’s grace time must be left at zero.
If the readback alarm Enable is set to status 1, a driver readback alarm will set the In Alarm state and an alarm message
will be generated and sent to the alarm group module and will get reported (dependent on the rest of the alarm strategy).
If the driver readback alarm enable input is set to status 0, the driver readback alarm will not be sent. The alarm reporting
mechanism is covered in Pt. 1 section 12.4.1. The driver readback alarm digital output can be used by other modules to
perform functions associated with the alarm condition. For example, to start a standby pump.
The Clear readback alarm (CDGT) is sent when the readback alarm clears, only if the readback alarm Enable and Clear
Alarm enable are both set.
0 A L4
32
0 P Driver 12
D12 L 0 fan
0 O
m0
nul A 0
U L4D
D S
0 L R
Alarm M
1 S LOOP BINARY HYST
Enabled Maint. Int. Enable
Enabled Readback Enable
G14N Maint. Int. Alarm maintenance interval
0 Readback Alarm
0 Readback Delay alarm digital output
33 0 Override Enable
Digital Input 7 0 Override Value
I7 S G14
0 m I7S S
0 c O
EXTERNAL 1000 I
0 Override Enable N
0 Override Value 0 A
HOURS RUN
In the above, example, the output from loop L4 is driving binary hysteresis driver D12, whose output is used to drive
a fan ON or OFF through digital output 12. Digital input 7 accepts input from a secondary contact on the fan contactor.
When the number of hours the fan has been running exceeds the hours run logic module Interval (I input) the module’s
interval output (N) will go true. The hours run logic module output is connected to the driver maintenance interval alarm
input.
If driver alarm condition is present for longer than the driver’s maintenance interval alarm delay then the driver’s
maintenance interval Alarm State is set true (driver’s maintenance interval alarm digital output is true).
Note that the driver’s maintenance interval alarm delay is not necessary as its function can be achieved by adjusting
the hours run logic module’s interval, so should be left at zero.
If the maintenance interval alarm Enable is set to status 1, a maintenance interval alarm will set the In Alarm state and
an alarm message will be generated and sent to the alarm group module and will get reported (dependent on the rest of
the alarm strategy). If the driver maintenance interval alarm enable input is set to status 0, the driver maintenance interval
alarm will not be sent. The alarm reporting mechanism is covered in Pt. 1 section 13.4.1. The driver maintenance interval
alarm digital output can be used by other modules to perform functions associated with the alarm condition. For example,
to start an alternative fan.
The Clear maintenance interval alarm (CMNT) is sent when the maintenance interval alarm clears, only if the maintenance
alarm Enable and Clear alarm enable are both set.
OffNormal
The BACnet Event Time Stamps array contains three values which are the times (date and time) that the last transitions
into the BACnet alarm states occurred:
n1: Time into OffNormal
n2: Time into Fault (always zero)
n3: Time into Normal
13.2.6 Override
The general use of overrides is covered in Pt. 1 section 5.7.
They can either be set up using SET (or a web page, or a supervisor e.g. 916 or later 963), or by strategy.
If set up using SET or a web page they can be used in conjunction with the address module override timer which will
remove the overrides once its time has expired.
An example of its use by strategy is given below:
40
Heating Valve Zone 1
D20 L 1
m2
Heating Valves Override L10D
A 0
Heating Loop Zone 1 L10D S
W8 From Page 5
0 R
D
Alarm
SW ITCH ANALOGUE M
W8D Override Enable
K8D Override Value
The Override Value for the analogue driver is analogue (the only driver type with a digital override value, status, is the
digital driver). Both drivers in the above example are switched into override by W8, and will take the override value from
knob 8.
13.2.7 Disable
The driver disable input will basically stop the driver being serviced by the program running in the IQ3. This generally
means that its outputs will remain at their last calculated value or status before the disable was put in place. In the case
of time proportional or raise/lower drivers they will continue to drive for their calculated time and then both channels
will turn off.
34
D13l S
G15 direct transfer
O
0 I
0 N
A
HOURS RUN
If an hours run module is connected directly to a driver (excluding analogue and raise/lower drivers) output channel as
shown above, the driver Hours Run is transferred directly to the hours run output when the module is serviced. If the
hours run module is reset, this will reset both the hours run module hours output, and the driver hours run. Similarly
if the driver hours run is changed this will be copied to the hours run logic module hours output.
The Time of Hours Run Reset parameter is the last time (date and time) at which the hours run was reset to zero.
36
G16
D14l R
S
999 direct transfer
0 A
M
COUNTER
5 Reschedule Time
1 Scale Factor
If a counter logic module is connected directly to a driver (excluding analogue and raise/lower drivers) output channel
as shown above, the driver number of starts is transferred directly to the counter module cumulative count output without
scaling when the module is serviced.
If the counter module is reset this will reset both the counter module cumulative count output and the driver number of
starts. Similarly if the driver number of starts is changed, this will be copied to the counter module cumulative count output.
The Time of Number of Starts Reset parameter is the last time (date and time) at which the number of starts was reset
to zero.
Value: (analogue/digital, status) This gives the current drive level. If the driver input is outside the range 0 to 100 it will
have been clipped to be within the range 0 to 100 (but see negative input, section 13.6.5 below). It includes the effects
of the override function, and the HOA feedback. (HOA feedback is ignored for analogue type driver.) If the in phase
output channel is in Hand or Off, the value is back calculated as follows:
Driver type Value type Value calculated
No Invert Invert
1 - Digital Digital In phase channel status Anti-phase channel status
2 - Analogue Analogue Ignored
3 - Time Proportional Analogue 100% x In phase channel status 100% x Anti-phase channel status
4 - Raise/Lower Analogue Estimate actuator position based on amount of time raise and lower
outputs have been overridden
5 - Binary Hysteresis Analogue 100% x In phase channel status 100% x Anti-phase channel status
6 - Time Proportional + Override Analogue 100% x In phase channel status 100% x Anti-phase channel status
7 - Raise/Lower Continuous Analogue Estimate actuator position based on amount of time raise and lower
outputs have been overridden
For a Digital type driver (type 1) the value will be a digital status (on/off), for all other types of drivers it is an analogue
value.
Module Status: (analogue, status) This parameter defines the current state of the module. It is shown on the modules’
overview page.
0 = Normal (auto) 3 = Hand (manually switched on)
1 = Override 4 = Off (manually switched off)
2 = Disabled 5= BACnet (BACnet in control)
In-Phase Hardware Channel (SET: In Phase Channel): (analogue, constant) This parameter defines the hardware output
channel driven by the in phase output. The range of channel numbers available depends on the type of main IQ3 or I/
O module used (see Pt. 1 section 8.5).
For Digital (type 1), Time Proportional (type 3), both Raise Lower (types 4, 7) and Binary Hysteresis (type 5) drivers, the
output channel should be digital, for a Time Proportional + Override (type 6) it should be analogue, for an Analogue Driver
(type 2) it can be analogue or digital.
Anti-Phase Hardware Channel (SET: Antiphase Channel): (analogue, constant) This parameter defines the hardware
output channel driven by the anti-phase output. The range of channel numbers available depends on the type of main
IQ3 or I/O module used (see Pt. 2 section16.6).
For Digital (type 1), Time Proportional (type 3), both Raise Lower (types 4, 7) and Binary Hysteresis (type 5) drivers, the
output channel should be digital, for a Time Proportional + Override (type 6) it should be analogue, for an Analogue Driver
(type 2) it can be analogue or digital.
In-Phase Output: (analogue/digital, output) The in-phase output value. For an analogue and time proportional plus
override drivers it is given in mV, for all other drivers it is given as ON or OFF. If connected to a module’s input (analogue
for analogue driver, digital for all others), the input’s details will be shown on the web page. The output channel number
is always shown (zero indicates no connection). This output is shown as a connective in SET (i.e. DnI, where D = driver
module, n = driver module number, I = In-phase output).
Anti-Phase Output: (analogue/digital, output) The anti-phase output value. For analogue and time proportional plus
override drivers it is given in mV, for all other drivers it is given as ON or OFF. If connected to a module’s input (analogue
for analogue driver, digital for all others), the input’s details will be shown on the web page. The output channel number
is always shown (zero indicates no connection). This output is shown as a connective in SET (i.e. Dna, where D = driver
module, n = driver module number, a = anti-phase output).
Invert: (digital, source/constant) If this is set to ON, it will cause the output to be logically inverted. It can either be sourced
from a digital output, or set to a constant value (0 or 1). If connected to a module’s digital output, the output’s details
will be shown on the web page.
Power On Delay (secs) (SET:Start Delay): (analogue, constant) A delay is incorporated in each driver to delay its
switching on when the controller powers up or performs a soft restart. During the delay analogue output channels will
be held at 0 V, and digital output channels will be off. This delay can be in the range 0-1275 secs, (21 minutes). This
can be used to stop all the plant switching on simultaneously when mains is returned to the controller, so each driver
should be given a different delay.
Active Priority Level: (analogue, output) This is the level in the driver priority array which is currently being input to
the driver algorithm. It can have a value in the range 0 to 16 where zero will only occur for an unconnected Source with
no other active inputs to the array. This enables the strategy to detect that the module has been overidden (e.g. due to
a BACnet communication). For example this could be done by checking that the Active Priority Level has not exceeded
the expected level using a Comparator function module. This output is shown as a connective in SET (i.e. Dnu, where
D = driver module, n = driver module number, u = Active Priority Level).
HOA State (SET: HAO Status): (analogue, output) This defines the Hand/Off/Auto status of the output channels. It
is the status fed back from the output channel electronics. Currently it applies to all driver types except analogue and
Time Proportional + Override (in this case it is left at Auto). In the case of the digital output modules with Hand/Off/Auto
(XCITE/IO/8DO/HOA and .../4DO/HOA), each digital output channel has a HOA switch (see Pt. 1 section 4.3.4); the
status of this switch is fed back to the driver module.
For a driver using the in phase output only or anti-phase output only, the HOA parameter indicates the channel’s HOA
switch position.
The terminology is:
Auto: Driven from the strategy
Hand: Manual override On by HOA switch
Off: Manual override Off by HOA switch
Hours Run: (analogue, output) The total time for which the in phase output (uninverted) has been on (see 13.2.8 above).
If connected to a module’s analogue input, the input’s details will be shown on the web page. This output is shown as
a connective in SET (i.e. DnH where D=driver module, n=driver module number, H=Hours Run). Not available on analogue
and raise/ lower drivers.
Time of Hours Run Reset (not available in SET): (characters, status) The time that the cumulative hours run was last
reset to zero. In date and time format: yyy-mm-ddThh:mm:ss. Not available on analogue and raise/lower drivers.
Number of Starts (SET: Starts): (analogue, output) The number of transitions from the off to on state of the in phase
output (uninverted) see 13.2.9 above. If connected to a module’s analogue input, the input’s details will be shown on
the web page. This output is shown as a connective in SET (i.e. DnN where D=driver module, n=driver module number,
N=Number of starts). Not available on analogue and raise/ lower drivers.
Time of Number of Starts Reset (not available in SET): (characters, status) The time that the number was last reset to
zero. In date and time format: yyy-mm-ddThh:mm:ss. Not available on analogue and raise/ lower drivers.
BACnet Priority Array (not available in SET or on web pages): This is an array of 16 values (text comms codes: o1 to
o16). The lowest numbered array element which is currently set up will be used to input to the driver algorithm. If an
array element is nulled, it will not be used.
BACnet Event Time Stamps (not available in SET or on web pages): This is an array of three values (text comms codes:
n1 to n3) which hold the times of the last transitions into the BACnet alarm states OffNormal, Fault, and Normal. In date
and time format: yyy-mm-ddThh:mm:ss.
13.2.10.2Module Type
Type: (analogue, constant) The driver module type:
1= Digital 2 = Analogue
3 = Time Proportional 4 = Raise Lower
5 = Binary Hysteresis 6 = Time Proportional Override
7 = Raise Lower (Cont.)
13.2.10.3Alarm Parameters
The driver module has two alarms and two clear alarms which are unusual in being detected outside the driver module
(see 13.2.5 above).
MINT: Maintenance Interval Alarm
SDGT: Readback Alarm (set driver grace time)
CMNT: Clear Maintenance Interval Alarm
CDGT: Clear Readback Alarm (clear driver grace time)
Readback Input (SET: Readback Alarm): (digital, source/constant) The readback alarm input to the driver module,
normally produced by a Readback logic module.
It can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s
digital output, the output’s details will be shown on the web page.
COV Increment: (analogue, constant) The amount by which the driver value has to change before a BACnet COV
notification message is sent to those subscribers in the List of Subscribers who have subscribed to this parameter. If
COV Increment is zero, notification is not sent. Not available on digital drivers.
In Alarm: (analogue, status) This status indicates that the driver is in alarm, i.e. either a Maintenance Interval, or a
Readback alarm, or has no alarm. It has accompanying text shown in the list below which is shown on the driver modules
overview page in the ‘alarm’ column.
0 = No alarm
8 = Maintenance
9 = Readback
The alarm state is shown if the alarm condition has been present for longer than that alarm’s delay time, and that alarm
is enabled to be reported. If both alarms are present the Maintenance alarm will be reported. It will be set back to 0
immediately both the alarms are in the clear state.
Maintenance: This indicates the maintenance interval Alarm State as defined below. Clicking on Maintenance on the
web page will display the maintenance interval alarm sub-module. The way in which the sub-module declares alarms and
clear alarms is described in Pt. 1 section 12.4.1.
(Maintenance Interval) Alarm State: (digital, output) This will be 1 if the maintenance interval alarm condition
has been present for longer than its alarm delay time. It takes no account of its alarm enable
If connected to a module’s digital input, the input’s details will be shown on the web page. This output is shown
as connective in SET (i.e. Dnm1S, where D = driver module, n = driver module number, m1 = maintenance alarm
sub-module 1, S = status, e.g. D1m1S).
(Maintenance Interval) Enabled (SET: Maintenance Int. Enable): (digital, source/constant) This is an input to the
sub module which will enable or disable the reporting of the alarm and clear alarm. Once the Alarm State is true
the alarm will be reported; when the alarm clears a clear alarm will be reported (if Clear Alarm, below, is also enabled).
This input can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected
to a module’s digital output, the output’s details will be shown on the web page.
(Maintenance Interval) Alarm Sent: (digital, status) This indicates that the alarm has been sent to the group
module. This will only happen if the Alarm State has be present for longer than the Alarm Delay, and the alarm
is Enabled to be reported.
(Maintenance Interval) Alarm Delay (secs) (SET: not present): (analogue, source/constant) This is the delay for
which the maintenance alarm input must be present before the Alarm State is declared. The alarm delay for the
clear alarm state is always zero.
Note: This parameter is not necessary, and should be left at zero.
This delay can either be sourced from a module’s analogue output, or set to a constant value. If connected to
a module’s analogue output, the output’s details will be shown on the web page.
(Maintenance Interval) Time in Alarm(secs): (analogue, status) This is the elapsed time since the Alarm State
commenced.
(Maintenance Interval) Alarm Group: (analogue, constant) This is the alarm group module to which the alarm
will be sent.
(Maintenance Interval) Clear Alarm (SET: Clear Enable): (digital, constant) This is an input to the sub module
which will separately enable or disable the reporting of the clear alarm. Once the Alarm State is true and the alarm
is enabled, the alarm will be reported; when the alarm clears a clear alarm will be reported only if Clear Alarm is
also enabled. This input can be set to a constant value (0, disable or 1, enable).
(Readback) Alarm State: (digital, output) This will be 1 if the readback alarm condition has been present for longer
than its alarm delay time. It takes no account of its alarm enable
If connected to a module’s digital input, the input’s details will be shown on the web page. This output is shown
as connective in SET (i.e. Dnr1S, where D = driver module, n = driver module number, r1 = readback alarm sub-
module 1, S = status, e.g.D1r1S).
(Readback) Enabled (SET: Readback Enable): (digital, source/constant) This is an input to the sub module which
will enable or disable the reporting of the alarm. Once the Alarm State is true the alarm will be reported; when the
alarm clears a clear alarm will be reported (if Clear Alarm, below, is also enabled). This input can either be sourced
from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s digital output, the
output’s details will be shown on the web page.
(Readback) Alarm Sent: (digital, status) This indicates that the alarm has been sent to the group module. This
will only happen if the Alarm State has be present for longer than the Alarm Delay, and the alarm is Enabled to
be reported.
(Readback) Alarm Delay (secs) (SET: Readback Delay): (analogue, source/constant) This is the delay for which
the readback input must be present before the Alarm State is declared. The alarm delay for the clear alarm state
is always zero.
Note: This is not necessary, and should be left at zero. However, for BTL compliance a digital driver’s readback
alarm delay must be used, and the readback logic module’s grace time must be left at zero.
This delay can either be sourced from a module’s analogue output, or set to a constant value. If connected to
a module’s analogue output, the outputs details will be shown on the web page.
(Readback) Time in Alarm(secs): (analogue, status) This is the elapsed time since the Alarm State commenced
(Readback) Alarm Group: (analogue, constant) This is the alarm group module to which the alarm will be sent.
(Readback) Clear Alarm (SET: Clear Enable): (digital, constant) This is an input to the sub module which will
separately enable or disable the reporting of the clear alarm. Once the Alarm State is true and the alarm is enabled,
the alarm will be reported; when the alarm clears a clear alarm will be reported only if Clear Alarm is also enabled.
This input can be set to a constant value (0, disable or 1, enable).
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
The driver label can be used as an item attribute for text communications. This is explained for IC Comms in Pt. 2 section
15.4.
Special characters are as follows:-
? * .
Page: (analogue, constant) SET file strategy page number on which module appears.
Disable Module (SET: ModuleState - Enabled/Disabled): (digital, source/constant) This input will disable the module,
i.e. prevent it from being serviced. Its internal states and output will be maintained at their values prior to disabling. This
input can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s
digital output, the output’s details will be shown on the web page.
Override Value/Status: (analogue/digital, source/constant) This input is the value/status (status for a digital driver,
value for all other types of driver) to which the output is overridden when the override condition is present. This input
can either be sourced from a module’s digital output or analogue output, or set to a constant value. If connected to a
module’s output, the output’s details will be shown on the web page.
Sequence Table: (digital, constant) This is set to sequence table 1 if the module is sequenced (in the sequence table).
It is set to table zero if the module is event driven
Sequence Step: (analogue, constant) The driver module can be either sequence table or event driven. If event driven
the step is set blank in SET, and the parameter does not appear on the web page. For sequence step driven modules this
defines the sequence step in the sequence table (see Pt. 1 section 5.6); the module may be entered into the sequence
table more than once.
The digital output driver has a single digital source address and provides a single digital output (with an optional anti-
phase output).
The digital output driver transfers the value of the digital input bit directly to the output address. The anti-phase bit would
be the inverse of this (e.g. if the input S were ON, then output L will go ON and output A will go OFF).
If the invert input is on then the in phase and antiphase channel states will be inverted (e.g. if the plant is driven via normally
closed relay contacts then the driver should be used in inverted mode).
The digital outputs are achieved by using either relays within the I/O modules or analogue voltage output channels and
external relay modules (SRMV).
13.3.1 Symbol
7
Driver 1
D1 L 0
m0
A 0
I3S S
R
Alarm
DIGITAL M
0 Start Delay
Disabled Invert
Disabled Maint. Int. Enable
Disabled Readback Enable
0 Maint. Int. Alarm
0 Readback Alarm
0 Readback Delay
Hours Run Specific digital driver parameters
Starts
0 Override Enable
0 Override Value
HOA Status
Active Priority Level
Hours Run
Time of Hours Run Reset
Number of Starts
Time of Number of Starts Reset
These parameters are covered by section 13.2.10.1 above.
The analogue output driver is normally used to drive such devices as valves or damper position actuators etc.
The analogue output driver has a single source variable in the range 0 to 100 % which represents the full range of the
analogue output. In order to drive actuators where the linear range of the actuator corresponds to an output voltage
range smaller than 0 to 10 V, offset and range constants can be applied to the input by configuring the driver module.
The analogue driver can be used to drive one of a range of external relay modules via an analogue output channel (i.e.
SRMV, 2RM, 3RM, 6RM). The strategy driving the driver can specify which relays are energised within the module by
setting the percentage input appropriately to match the relay’s switching voltage.
13.4.1 Symbol
13
Driver 2
D2 L 0
m0
A 0
0 S
R
Alarm
ANALOGUE M
0 Start Delay
0
100
Offset
Range
specific analogue driver parameters
Disabled Invert
Disabled Maint. Int. Enable
Disabled Readback Enable
0 Maint. Int. Alarm
0 Readback Alarm
0 Readback Delay
0 Override Enable
0 Override Value
HOA Status
Active Priority Level
0.25 COV Increment
specific analogue
driver parameters
The standard output voltage range is 0 to 10 V, where 0 volts represents an input of 0 % input and 10 V represents an
input of 100 %. If an offset of 0 and a range of 100 is specified then an input of 20 %, results in an output of 2 V.
For example an output voltage range of 2 to 8 V is required to drive a particular item of plant.
The total output voltage of 0 to 10 V gives a range of 10 V which represents an input of 10 % per volt output.
8V
RANGE = 100%
RANGE = 60%
ie 6 V
2V OFFSET = 20%
ie. 2 V
0 OFFSET = 0% 0V 0
When the input to the module is 100 %, the output voltage will be 8 V and when the input to the module is 0.01 %, the
output voltage will be 2 V. 0% will still give 0 V.
If an analogue output driver is inverted, its output level corresponds to its complement from 100% e.g. 80% inverted gives
20% output. If a range and offset are set up then the output is the complement of the range plus the offset. In the example
above with an offset of 20% and a range of 60%, if the input were 80% and the module inverted, the output is 20% of
the range (60%) plus the offset (20%).
Range: (analogue, source/constant) The percentage of the output which corresponds to the 0 to 100% input range (i.e.
a range of 60% means that an input range of 0 to 100% corresponds to an output range of 6 V). It can either be sourced
from a module’s analogue output, or set to a constant value. If connected to a module’s analogue output, the output’s
details will be shown on the web page.
MARK SPACE
O/P LEVEL
=50%
PERIOD TIME
This example shows the module in phase output where the driver input level is 50%. The output waveform shows an
ON pulse (mark) equal to half the period time. The period time is set in seconds.
This driver is similar to others in having an in-phase output channel (L) and an anti-phase output channel (A) which is
always the inverse of the (L) output.
The digital outputs are achieved by using either relays within the I/O modules or analogue voltage output channels and
external relay modules (SRMV).
If the driver is inverted the two output channel waveforms are simply inverted.
Note that disabling the driver (Disable Module set to 1) will allow the channels to continue to drive for their calculated
time to the end of the period before turning both channels off.
The time proportional driver input defines the ratio ON time/PERIOD time in percent.
The period time is configured in the driver module, and then the ON time, or the time that the output is in the MARK state
is determined by the input level taken as a percentage of the period time. The OFF time or time when the output is in
the SPACE state is then the remainder of the period (or period time minus ON time).
13.5.1 Symbol
15
Driver 3
D3 L 0
m0
A 0
0 S
R
Alarm
TIME PROP. M
0 Start Delay
0 Period
Disabled Invert
Disabled Maint. Int. Enable
Disabled Readback Enable
0 Maint. Int. Alarm specific time proportional driver parameters
0 Readback Alarm
0 Readback Delay
Hours Run
Starts
0 Override Enable
0 Override Value
HOA Status
Active Priority Level
0 COV Increment
With the module input at 100 %, the output will be in the ON state for 150 s and the OFF state for 0 s.
With the module input at 50 %, the output will be in the ON state for 75 s and the OFF state for 75 s.
With the module input at 10 %, the output will be in the ON state for 15 s and in the OFF state for 135 s.
As a general rule every time the module is serviced the input is examined and if the output is still ON, the time for which
it will remain ON is recalculated, however once the output has turned OFF it will remain OFF until the start of the next
period.
(There is a special exception to this action if the input is found to be 100 %, as explained later.)
For example if the input at the start of a 50 min period is at 10 %, then the output should remain ON for 5 min.
INPUT % 100
20
10
TIME
(Min)
turn off at 10 %
ON (100)
OUTPUT
turn off at 20 %
OFF (0)
0 4 5 10 50
If at 4 min the input has changed to 20 % then the output will be set to stay ON until the 10 min. However if the input
had changed to 5 % then the output will turn OFF immediately (as the ON period of 2½ min has been exceeded).
Similarly any change to 0 % will be actioned the next time the module is serviced.
INPUT % 100
Input changes
from 40% to 0%
at 30% into period
40
OUTPUT % 100
(30%) (40%)
0
0 15 20 50
EXAMPLE PERIOD (min) time (min)
In this example the output would stay ON for 20 min, but when the input changes to 0 % after 15 min, the output turns
OFF the next time the module is serviced.
INPUT % 100
Input changes
to
100% from 40%
40
OUTPUT % ON (100)
MIN
10%
5 min
OFF(0)
0 20 25 50
In this case the input changes from 40 % to 100 % after 22½ min. This means it turned OFF at 20 min, so it will not turn
ON again until it has exceeded the minimum OFF time of 5 min (10 % of 50 min). This point occurs at 25 min.
100
INPUT %
90
Input changes
from 90% to 100%
after turning off
0
time
5%
OFF (0)
0 45 50
NEXT
EXAMPLE PERIOD (min) PERIOD
In this case the input changes from 90 % to 100 % after 47½ min. The output has turned OFF at 45 min so it cannot complete
the minimum off time of 5 min until the start of the next period, so the output cannot turn ON again until the start of the
next period.
Hours Run
Time of Hours Run Reset
Number of Starts
Time of Number of Starts Reset
These parameters are covered by section 13.2.10.1 above.
It provides either two digital outputs or a single analogue output. Setting the anti-phase output channel number to 0
- selects a single analogue output; this enables it to drive an external raise lower or heat cool relay module by way of
an analogue output channel. Setting the anti-phase output channel to a number other than 0 - selects two digital outputs;
this enables it to drive internal relay outputs (I/O module relays).
The invert is ignored on a driver with a single analogue output channel (see 13.6.5 below). For a driver with 2 digital
outputs, the driver will invert both channels, but it doesn’t transpose the channels as the anti-phase channel is not
necessarily the inverse of the in phase channel. However if the driver is in the static phase, both channels are left at zero.
Note that disabling the driver (Disable Module set to 1) will allow the channels to continue to drive for their calculated
time to the end of the full scale drive time before turning both channels off.
The raise lower driver with end stop will do its best to ensure that the item it is driving has reached its end stop and then
stop driving the item, as opposed to the continuous driver (type 7) which will keep driving.
13.6.1 Symbol 16
Driver 4
D4 L 0
m0
0 S A 0
nul F
R
Alarm
RAISE LOWER END M
specific raise lower driver parameters 0
0
Start Delay
fs Drive
Disabled Invert
Disabled Maint. Int. Enable
Disabled Readback Enable
0 Maint. Int. Alarm
0 Readback Alarm
0 Readback Delay
Position
0 Override Enable
0 Override Value
HOA Status
Active Priority Level
0 COV Increment
13.6.2 Web Page
Connective
L raise
D
A lower
Raise - if the input = 100% or greater, or for a time period calculated by:-
Full scale drive time multiplied by any positive value determined by (input % minus last output position %).
Static - for any time period during which the requested output position is equal to the last output position.
37 R Raise
Driver 15
2RM
D15 L 12
(RLM
m0
0 S A 0 mode) L
Lower
nul F
R
Alarm
RAISE LOWER END M
100 fs Drive
Disabled Invert
Position
0 Override Enable
0 Override Value
HOA Status split phase valve motor
37 Heat Raise
Driver 15
D15 L 12
m0
0 S A 0 Cool
3RM Lower
nul F
R (HCM
Alarm mode)
RAISE LOWER END M
100 fs Drive
Disabled Invert
Position
0 Override Enable split phase valve motor
0 Override Value
HOA Status Fan Fan
full scale drive time
When using the raise lower driver with an analogue output channel the 2RM (set to RLM, raise lower module, mode)
or 3RM (set to HCM, heat cool module, mode) should be used to interface to HVAC equipment. The output of the raise
lower driver as measured at the terminals of the assigned output channel (set to voltage) will be:-
7 V - for any time period during which the requested output position is equal to the last output position.
0 V - as an overriding condition for any time period when the input is negative.
These voltages applied to Relay Modules will result in the following actions:-
13 11
C1 RLM Driver Value
2RM RLM Driver
RLM Value C1 E F3 D4 L 12
m0
-100 F D F3D S A 0
G2D B 0 F
GATE R
12 Alarm M
D = F when B = 1 RAISE LOWER END
Output Override Required
0 Start Delay
Connect overrides G2 RLM Low High 100 fs Drive
0 E
Rly 1 Rly 2 Disabled Invert
J or Disabled Maint. Int. Enable
0 F K or 0V O O
Disabled Readback Enable
L or D 4V I O 0 Maint. Int. Alarm
0 G M 7V O O 0 Readback Alarm
0 H 10V O I 0 Readback Delay
COMB Position
E J Comb.
F K Comb.
G L Comb.
H M Comb.
15 16
C2 Driver Value
3RM HCM Driver
HCM Value C2 E F4 D5 L 13
m0
-100 F D F4D S A 0
G3D B 0 F
GATE R
14 Alarm
D = F when B = 1 RAISE LOWER END M
Output Override Required
HCM Fan Cool Heat 0 Start Delay
Connect overrides 0 E G3 Rly 1 Rly 2 Rly 3 100 fs Drive
Disabled Invert
J or 0V O O O Disabled Maint. Int. Enable
0 F K or
D 4V I I O Disabled Readback Enable
L or 0 Maint. Int. Alarm
0 G M 7V I O O
0 Readback Alarm
10V I O I 0 Readback Delay
0 H
COMB Position
E J Comb.
F K Comb.
G L Comb.
H M Comb.
-1 0 0
t V 1
1 0
O u tp u t
7
( v o lts )
4
t V 2
0
tim e
For example in the above diagram a valve with a full drive time of 120 s is being driven, the input to the driver module
is 0 %, and the estimated valve position is 0 %. If the input to the driver module increases to 60 %, the raise output to
the driver module will be turned ON for 60 % of the drive time i.e. 72 s, moving the valve to 60 % open. If the input to
the driver module decreases by 40 % to 20 %, the lower output of the driver module will be turned ON for 40 % of the
full drive time i.e. 48 s, moving the valve to 20 % open.
The valve position will not be changed for input changes of less than 0.25 % unless the valve moves to or is at the 100
% or 0 % (endstop) positions.
If an error in estimated valve position develops then this will be corrected when it reaches the fully open or fully closed
limits (endstops).
There are two methods for this, one being used by a raise lower with end stop driver, (type 4), and one by a raise lower
continuous driver (type 7).
In a raise lower driver with end stop this is done by ensuring that when the input is at 0 %, the lower input will be energised
for the calculated time to reach the endstop plus the full scale drive time; a similar action takes place for the raise output
when the input is at 100 %.
The type 4 driver is used for actuators with reversible action motors without any built-in positioning or where there aren't
any built-in limit switches or clutches. The type 7 driver is used for all other types of actuators fitted with reversible action
motors.
Both of these methods ensure that the driver estimated position is reset to the real position (i.e. 0 % or 100 %) at these
boundaries. In general, in the midrange, inaccuracies will build up, but the overall closed loop feedback will ensure that
the real actuator position is correct for the required demand regardless of estimated position.
Note that the 2RM (RLM) and 3RM (HCM) do not energise the lower relay if the input is 0 volts i.e. if the input to the
raise/lower driver is less than 0 %. The estimated valve position is retained to be used when the input rises above 0 %.
Note that the full scale drive time must be set up when configuring the driver.
If a feedback input is used and the feedback sensor input has either an out-of-limits or a read alarm then the driver module
will revert to boundless control. The user should be aware that if positional information is incorrect, control may
deteriorate. The feedback input will be ignored if it is set to a constant value (is not connected to an output).
40
39
Sensor 4
0 A L3
S4
0 m V
S4V P 37 R
0 c
Driver 15
EXTERNAL 0 O
D15 L 12 2RM
nul U
D L3D S
m0
A 0
(RLM)
L
0 L S5V F
Z3 LOOP
R
Z3V S Alarm
RAISE LOWER END M
TIME ZONE
100 fs Drive
0 3 6 9 12 15 18 21 24
MON Disabled Invert
Position
TUE
WED 0 Override Enable
0 Override Value
THU HOA Status
FRI
SAT
SUN
41
Sensor 5
Valve position S5 V
0 m
potentiometer 0 c
EXTERNAL
From the above implementation it can be seen that the strategy operates like a cascade control system with the primary
loop L3 giving a position setpoint to the secondary loop D15 which compares this with its process variable, the
potentiometer S5, to energise the relevant raise or lower line.
In both boundless and feedback operation the driver response to a change in input is dependent on the current valve
position. If at either of its bounds, the driver first has to go to a static position (i.e. for one cycle time), before recovering
on the next cycle. If static in midrange, the driver will respond within one cycle time. If driving in one direction and then
reversing, the driver will wait for 5s.
Full Scale Drive (SET: fs Drive): (analogue, source/constant) The time it will take to drive the HVAC equipment item (e.g
valve actuator) over its full range (in seconds). It can either be sourced from a module’s analogue output, or set to a
constant value. If connected to a module’s analogue output, the output’s details will be shown on the web page.
Drive Position (SET: Position): (analogue, output) The current HVAC equipment item position as a percentage of it full
range as understood by the driver module. If there is no feedback (boundless) it is estimated, otherwise it will reflect the
feedback input. If connected to a module’s analogue input, the input’s details will be shown on the web page.
This output is shown as a connective in SET (i.e. DnP, where D = driver module, n = driver module number, P = position)
State: The current state of the raise lower module outputs. Only shown on the web page. The state can be one of the
following:
Off (0)
Stationary (1)
Lower (2)
Raise (3)
O F F
O F F O N
L E V E L IN P U T (S )
L E V E L
The input must rise above the on level for the output to switch on, and then must fall below the off level for the output
to switch off. The difference between the on and off levels is the hysteresis, and the input can fluctuate within this band
without the output changing. The ON and OFF switching levels can each be set between 0 and 255 although only 0 to
99 is operational.
When the module is first serviced (after a strategy download) the output is set to zero and if the input is between the
off and on levels then the output remains at zero.
If the binary driver is to be used as a switch with no hysteresis, the ON and OFF levels can be set to the same value.
However, the output may change rapidly as the input fluctuates about the on/off level.
This driver has an in-phase output channel (L) and an anti-phase output (A). The anti-phase will always be the opposite
of the in phase.
The digital outputs are achieved by using either relays within the I/O modules or analogue voltage output channels and
an external relay modules (SRMV).
Off level: (analogue, source/constant) The input level below which the driver output will switch off.
It can either be sourced from a module’s analogue output, or set to a constant value. If connected to a module’s analogue
output, the output’s details will be shown on the web page.
Hours Run
Time of Hours Run Reset
Number of Starts
Time of Number of Starts Reset
These parameters are covered by section 13.2.10.1 above.
When the override input is applied it will hold the channel output at 10 V, otherwise it time proportions the output in
a similar way to a time proportional driver but between 4 V (ON) and 7 V (OFF).
The principle application is to drive a time proportional refrigeration stub of the type used in supermarkets. In this
application, use of a raise lower module (2RM in RLM mode) halves the number of outputs and simplifies wiring.
When the override input is ON the output drives to 10 V and holds the defrost relay (RAISE) ON and the refrigerate relay
(LOWER) OFF.
When the override input is OFF the defrost relay (RAISE) is OFF and the refrigeration relay (LOWER) comes ON for
a time which is related to the period time by the input level (i.e. time proportional).
The anti-phase output is not normally used but it obeys the following rules. The anti-phase output channel (A) will be
the inverse of the in-phase channel but only with respect to the time proportional 4 V (ON) and 7 V (OFF) levels, so if
the override is ON the in-phase channel is at 10 V, i.e. the time proportional output is >7 V i.e. OFF so the anti-phase channel
is ON i.e. 4 V.
Note that disabling the driver (Disable Module set to 1) will allow the channels to continue to drive for their calculated
time to the end of the period before turning both channels off. If the override (O) input is on the in phase output will
continue to be held on.
13.8.1 Symbol
18
Driver 6
D6 L 0
m0
0 S A 0
0 O
R
Alarm
TIME PROP + O/R M
0 Start Delay
0 Period
Disabled Invert
specific time proportional + override Disabled Maint. Int. Enable
driver parameters Disabled
0
Readback Enable
Maint. Int. Alarm
0 Readback Alarm
0 Readback Delay
Hours Run
Starts
0 Override Enable
0 Override Value
HOA Status
Active Priority Level
0 COV Increment
Override: (digital, source/constant) This input will switch the module into override operation where it will drive the in
phase output to 10 V ( and hence the connected raise lower module raise output). It can either be sourced from a module’s
digital output, or set to a constant status. If connected to a module’s digital output, the output’s details will be shown
on the web page.
Hours Run
Time of Hours Run Reset
Number of Starts
Time of Number of Starts Reset
These parameters are covered by section 13.2.10.1 above.
Note that for Time Proportional + Override driver the hours run and number of starts are only counted if the output is
=> 7V pre-inversion.
Note that disabling the driver (Disable Module set to 1) will allow the channels to continue to drive for their calculated
time to the end of the period before turning both channels off. If the input is at 100% the in phase output will continue
to be held on; if the input is at zero the antiphase output will continue to be held on.
13.9.1 Symbol 19
Driver 7
D7 L 0
m0
0 S A 0
nul F
R
Alarm
specific raise lower continuous RAISE LOWER CONT. M
driver parameters 0
0
Start Delay
fs Drive
Disabled Invert
Disabled Maint. Int. Enable
Disabled Readback Enable
0 Maint. Int. Alarm
0 Readback Alarm
0 Readback Delay
Position
0 Override Enable
0 Override Value
HOA Status
Active Priority Level
0 COV Increment
Connective
As before if an error in estimated valve position develops then this will be corrected when it reaches the fully open or
fully closed limits (endstops).
In a type 7 driver when the input is 0%, the lower output will be energised and remain energised until the input goes above
0 %, and if the input increases to 100 % the raise output will be energised until the input falls below 100 %.
The type 7 driver is used for actuators with reversible action motors with built-in positioning or where there are built-
in limit switches or clutches.
Full Scale Drive (SET: fs Drive): (analogue, source/constant) The time it will take to drive the HVAC equipment item (e.g
valve actuator) over its full range (in seconds). It can either be sourced from a module’s analogue output, or set to a
constant value. If connected to a module’s analogue output, the output’s details will be shown on the web page.
Drive Position (SET: Position): (analogue, output) The current plant item position as a percentage of it full range as
understood by the driver module. If there is no feedback (boundless) it is estimated, otherwise it will reflect the feedback
input. If connected to a module’s analogue input, the input’s details will be shown on the web page.
This output is shown as a connective in SET (i.e. DnP, where D = driver module, n = driver module number, P = position).
State: (analogue, status) The current state of the raise lower module outputs. Only shown on the web page. The state
can be one of the following:
Lower (0)
Raise (1)
Stationary (3)
TYPE
SET Web Low High
co d e
page
Controller Parameters
SOURCE/CONST
Source R/W R/W* S 0 1 0 The value input to the driver. 0 to 1 for digital
or or driver, -1020 to +1020 for all other driver types. Can
-1020 +1020 be connected to a module's output (digital for a
digital driver, analogue for all other driver types)
In-Phase Output R/W R/W l 0 1 0 The value of the in phase output channel. -1020 to
+1020 for analogue and time proportional plus
OUTPUT
or or
-1020 +1020 override drivers, 0 to 1 for all other driver types.
Can be connected to a module's input (analogue
for an analogue driver, digital for all other driver
types)
Anti-phase Output R/W R/W a 0 1 0 The value of the in phase output channel. -1020 to
OUTPUT
or or +1020 for analogue and time proportional plus
-1020 +1020 override drivers, 0 to 1 for all other driver types
Can be connected to a module's input (analogue
for an analogue driver, digital for all other driver
types)
In-Phase Hardware R/W R L 0 32 0 The output channel on the specified IO module
CONST
1 to 9 = 1 to 9
A=10
B=11
C=12
D=13
E=14
F=15
Value - R V -1020 +1020 0 The value input to the driver algorithm.
STATUS
1 = Overidden
2 = Disabled
3 = Hand (manually set on)
4 = Off (manually set off)
5 = BACnet (BACnet in control)
SOURCE/CONST
Invert R/W* R/W I 0 1 0 If set to one the output will be logically inverted.
Can be connected to a module's digital output.
TYPE
co d e
SET Web Low High
page
Controller Parameters
COV Increment R/W R/W C 0 +1020 0 Not available on digital drivers. The amount
CONST
by which the driver value must change
before a BACnet notification is sent. If
zero, there is no notification.
Power on Delay R/W R/W T 0 1275 0 The period after the controller is powered
OUTPUT CONST
(secs) up before the driver output is switched on
(SET: Start Delay)
seconds
Hours Run - R H 0 87600 0 Not available on analogue or raise lower
(10 drivers. The time for which the in phase
yrs) output(prior to inversion) has been on. Can
Hours be connected to an analogue input.
Time of Hours Run - R t date&time; 0000-00-- Not available on analogue or raise lower
STATUS
Reset yyyy-mm-dd& 00T00:00:- drivers. The time that the cumulative hours
Thh:mm:ss 00 run was last reset to zero, in full date and
time format.
Number of Starts - R N 0 10 9 0 Not available on analogue or raise lower
OUTPUT
(SET: Starts) drivers. The number of times the in phase
output (prior to inversion) has been
transitioned from 0 to 1. Can be connected
to an analogue input.
Time of Number of - R e date&time; 0000-00-- Not available on analogue or raise lower
STATUS
Starts Reset yyyy-mm-dd& 00T00:00:- drivers. The time that the cumulative
Thh:mm:ss 00 number of starts was last reset to zero, in
full date and time format.
In Alarm - R/W ! 0 8,9 0 0=No driver alarm to be reported
8=Maintenance alarm to be reported
STATUS
Maintenance input R/W R/W* s 0 1 0 The maintenance interval alarm input to the
(SET: Maint. Int. driver module (normally from hours run
Alarm) logic module). Can be connected to a
digital output.
STATUS SOURCE/CONST STATUS SOURCE/CONST OUTPUT
(maintenance) is sent
(SET: Group)
Clear Alarm R/W R/W m1(C) 0 1 1 A separate enable for the clear alarm. The
CONST
TYPE
co d e
SET Web Low High
page
Controller Parameters
SOURCE/CONST
Readback input R/W R/W* b 0 1 0 The readback alarm input to the driver
(SET: Readback (normally from readback logic module).
Alarm) Can be connected to a digital output.
OUTPUT
Readback R/W R r1(S) 0 1 0 Indicates the alarm condition has been
Alarm State present for longer than the delay time
(readback) (independent of alarm enable). Can be
connected to a digital input.
SOURCE/CONST
Enabled R/W R/W* r1(E) 0 1 0 Thuis input enables the alarm to be
(readback) reported. Can be connected to a digital
(SET: Readback output
Enable)
Alarm Sent - R r1(K) 0 1 0 Set true if alarm has been sent to the alarm
STATUS
(readback) group
SOURCE/CONST
Alarm Delay R/W R/W* r1(D) 0 178200 0 The time for which the alarm must be
(secs) present before the alarm is declared. Can
(readback) be connected to an analogue output.
seconds
Time in Alarm - R/W r1(T) 0 178200 0 The elapsed time since the Alarm State
STATUS
(secs) commenced
(readback)
seconds
Alarm Group R/W R/W r1(G) 0 500 1 The alarm group module to which the alarm
CONST
(readback) is sent
(SET: Group)
Clear Alarm R/W R/W r1(C) 0 1 1 A separate enable for the clear alarm. The
CONST
Override Output R/W R/W* ^ 0 1 0 The status of the override input. Can be
(SET: Override connected to a digital input.
Enable)
SOURCE/CONST
Override R/W* R/W v 0 1 0 The status or value to which the output will
Status/Value or or be overridden. Status (0 or 1) for digital
-1020 +1020 driver, value (-1020 to +1020) for all others.
Can be connected to a module's output
(digital for a digital driver, analogue for all
other driver types).
Active Priority Level - R u 0 16 10 The currently active priority level in the
OUTPUT
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Offset R/W R/W* O 0 100 0 The percentage of the output to which the
zero % input corresponds. Can be
connected to an analogue output.
Full Scale Drive R/W R/W* D 1 32767 0 The time taken to drive the HVAC
(SET: fs Drive) (8 hrs) equipment item (e.g actuator) over its full
range. Can be connected to an analogue
seconds output.
Drive Position R/W R/W P 0 100 0 The current HVAC equipment item's
(SET: Position) position as understood by driver module.
Can be connected to an analogue input.
0 = Static
1 = Raise
2 = Lower
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Binary Hysteresis Driver (type 5) Parameters
SOURCE/CONST SOURCE/CONST
On level R/W R/W* O 0 100 0 The input level at and above which the
driver will switch on. Can be connected to
an analogue output.
Off level R/W R/W* F 0 100 0 The inputlevel at and below which the driver
will switch off. Can be connected to an
analogue output.
SOURCE/CONST
Period R/W R/W* P 0 32767 0 The amount of time being time
(8 hrs) proportioned.
seconds
In Phase output (mV), Anti-Phase output (mV) are as covered above but are shown in mV
Hours Run and Number of Starts are covered above
* This source/constant parameter cannot be changed via the web page if it is set as a source.
2 Rescale From Rescales input of 0 to 100 to user defined values and limits at these values
5 Limit To Will drive the output to 0 and 100 at user defined values
14 Analogue gate Digital input switches output between two analogue inputs
17 Hysteresis Band Creates digital output from analogue input using level and hysteresis band
18 Analog. to Digital Convert. Creates digital byte output from analogue input
21 Hysteresis Limits Creates digital output from analogue input using upper and lower hysteresis limits
22 Proximity Creates digital output which indicates if 2 analogue inputs are in defined band of each other
SET icons
The function module has up to four analogue inputs, depending on the function being performed and usually one
analogue output. For certain types of function the output (and/or an input) may be digital.
As is general in the IQ3 the inputs may be either sources or constants enabling such parameters as scaling factors to be
generated by the strategy.
In general if the calculation involves a divide by zero, the module will output the largest number it can handle (normally
1020).
The function module appears on the strategy page and can either be sequence table driven or event driven. The filter
function module (type 1) should not be event driven.
0 E F3
0 F
four inputs D
0 G single output
0 H ADD/SCLR
D = (E * G) + (F * H)
Connectives
This is used by all function modules except types 15, 17, 21, 22 (Comparator, Hysteresis Band, Hysteresis Limits,
Proximity) which have digital outputs and use the connective below, and type 18 (Analogue to Digital Converter) which
has 8 digital output bits - see Pt. 2 section 14.20.
88
0 E F38
0 G D F38D V A3 D
Read Alarm
Analogue
alarm bits
FILTER Out. Limits Alarm
D=E*D+(1-E)*G Low Alarm
High Alarm
In the above diagram the function module output alarm bits have been exposed by analogue node 8.
The alarm bits associated with the function module outputs are generated as follows:
1) Function modules types 1 to 10 and 16, 19, 20, and 23 to 26. The alarm bits on the inputs used are OR’ed together
(summed).
2) Function Modules types 11 to 13 (i.e. minimum, maximum, or average). With these modules, if inputs go into
out-of-limits (OUTL) or read (READ) alarms, they are ignored, and the status of the output indicates the OR’ed
function of high and low alarm bits on the remaining used inputs. If all the inputs have either out-of-limits or read
alarms then the output remains unchanged (as it was before the alarm) and the output alarm bits have the OR’ed
function of any of the inputs (i.e. any out-of-limits, read, high or low alarms are passed on).
3) Function Module Type 14. The alarm bits from the source in use are transferred to the output.
4) Function Module Types 15, 17, 18, 21, 22. All alarm bits are ignored.
Source F (SET: Input F): (analogue, source/constant) An input to the module. It can either be sourced from a module’s
analogue output, or set to a constant value. If connected to a module’s analogue output, the output’s details will be shown
on the web page.
Source G (SET: Input G): (analogue, source/constant) An input to the module; quite often the input to be acted on, the
‘input signal’. It can either be sourced from a module’s analogue output, or set to a constant value. If connected to a
module’s analogue output, the output’s details will be shown on the web page.
Source H (SET: Input H): (analogue, source/constant) An input to the module. It can either be sourced from a module’s
analogue output, or set to a constant value. If connected to a module’s analogue output, the output’s details will be shown
on the web page.
Destination: (analogue/digital, output) The value or state of the module’s output. This is usually an analogue output
but for function modules types 15, 17, 21, 22 (Comparator, Hysteresis Band, Hysteresis Limits, Proximity) this is a digital
output. Type 18 (Analogue to Digital Converter) has 8 digital output bits as described in Pt. 2 section 14.20.
If connected to a module’s input, the input’s details will be shown on the web page.
The output is shown as a connective in SET (e.g. FnD, where F=Function module, n = function module number, D =
destination).
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
Page: (analogue, constant) SET file strategy page number on which module appears.
Disable Module (SET: ModuleState - Enabled/Disabled): (digital, source/constant) This input will disable the module,
i.e. prevent it from being serviced. Its internal states and output will be maintained at their values prior to disabling. This
input can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s
digital output, the output’s details will be shown on the web page.
Sequence Table: (digital, constant) This is set to sequence table 1 if the module is sequenced (in the sequence table).
It is set to table zero if the module is event driven
Sequence Step: (analogue, constant) The driver module can be either sequence table or event driven. If event driven
the step is set blank in SET, and the parameter does not appear on the web page. For sequence step driven modules this
defines the sequence step in the sequence table (see Pt. 1 section 5.6); the module may be entered into the sequence
table more than once.
14.3.1 Symbol
43
0 E F4
0 G D
FILTER
D=E*D+(1-E)*G
Dn+1 = E x Dn + (1 - E) G
E, the filter factor, is normally in the range 0 to 1 where 0 gives no filter action, and 1 gives an infinite filter (i.e. no change
in output); in above equation applies over this range.
When the module is first serviced (after a strategy download) the output D starts at zero.
The unit step response of the output to a filter factor of 0.9048 (i.e. time constant of 10 s) can be seen in the graph below.
1.2
0.8
Value
0.6 Series2
0.4
0.2
0
1 11 21 31 41
Time (s)
It can be seen that the output reaches about 2/3rds (0.67) of its final value after 10 seconds (the time constant) and
thereafter its slope drops off as it tends exponentially to the value of 1.
14.4.1 Symbol
44
0 E F5
0 G D
0 F
RSCL FR
D=(G/100)(F-E)+E
G(F E)
DE
100
100
Where D = output
E = lower limit
F = upper limit OUTPUT
G = input
0 F INPUT E 100
69
70
Space Temp 72
0 A L5
S6 V 68
0 m
0 c
S6V P 0 A L6
EXTERNAL K1D O F29
20 E S7V P
Occupied Setpoint
K2D U L5D F29D
D G D O
K1
0 K3D L 80 F29D
D F U
RSCL FR D
KNOB Z4V LOOP
S 0
D=(G/100)(F-E)+E L
Unoccupied Setpoint 1 S LOOP
Manual
K3
0
D
KNOB
Z4
TIME ZONE
0 3 6 9 12 15 18 21 24
MON
TUE
WED
THU
FRI
SAT
SUN
In the above example, the output of loop L5 is fed to function module F29. Function module F29 rescales the 0 to 100
input signal from loop L1 to a 20 to 80 output signal, where 20 represents a 0 input and 80 represents a 100 input. The
rescaled signal is then used to provide the setpoint for loop L6.
14.5.1 Symbol
45
0 E F6
0 G D
0 F
RSCL TO
D=100(G-E)/(F-E)
100(G E)
D
FE
100
where D = Output
E = Lower value OUTPUT
F = Upper value
G = Input
Z5
TIME ZONE
0 3 6 9 12 15 18 21 24
MON
TUE
WED
THU
FRI
SAT
SUN
In the above example, simple AHU control is achieved. Space sensor S8 is monitoring the space temperature and providing
an input to loop L7. The output from loop L7 is in the range 0 to 100 percent, depending on the input from S8. When the
output from loop L7 is in the range of 40 to 0 percent, the output from the function module F31 will be in the range 0 to
100 percent so that when the input to function module F31 rises from 0 percent to 20 percent, the output of F31 will fall
to 50 percent.
When the output from loop L7 reaches 40 percent, the dampers will be fully closed. Function module F30 performs a
similar function to F31 but when an input to F30 is at 80 percent its output will be 50 percent which is used by driver
D17 to drive the valve open to 50 percent.
It will be noticed that there is a 20 percent difference between the lower limit of function module F31 (40) and the lower
limit of function module F30 (60). This difference is known as a dead band and is incorporated so that small changes around
the crossover point, where the dampers are fully closed and the valve starts to open, do not cause the valve/dampers
to keep changing state over a short duration.
1 0 0
F R E S H A IR
% D R IV E D A M P E R S
D E A D V A L V E
B A N D
0
4 0 6 0 1 0 0
L O O P O U T P U T %
14.6.1 Symbol
47
0 E F8
0 G D
0 F
LIMIT AT
IF G>E D=E IF G<F D=F
If G>E then D = E 1 0 0
If G<F then D = F E
else D=G
where D = output
E = upper limit O U T P U T
F = lower limit
G = input
F
0 F IN P U T E 1 0 0
G is the analogue variable that is to have limits applied, E is the upper limit where, when G is greater than E, the module
output goes to the value of E. F is the value of the lower limit where, when G is less than F, the module output goes to
the value of F. For all values between E and F, the module output will correspond to the value of G.
14.7.1 Symbol
48
0 E F9
0 G D
0 F
LIMIT TO
IF G>E D=100 IF G<F D=0
1 0 0
If G>E then D = 100
If G<F then D = 0
Else D=G
where D = output
E = upper value O U T P U T
F = lower value
G = input
0 IN P U T 1 0 0
F E
G is the analogue variable that is to have limits applied. E is the upper value where, when G is greater than E, the module
output goes to 100 percent. F is the lower value where, when G is less than F, the module output goes to 0 percent.
In the above example any input signal greater than 80 percent will cause the time proportional driver to switch ON for
79 80
Driver 19
F32 D19 L 0
80 E m0
A 0
0 G D F32D S
20 F R
LIMIT TO Alarm
TIME PROP. M
IF G>E D=100 IF G<F D=0
100 percent of the time period, preventing short OFF periods. Inputs of less that 20 percent will cause the time proportional
driver to switch OFF for 100 percent of the time period preventing short ON periods. For all values between E and F, the
module output will correspond to the value of G.
14.8.1 Symbol
46
F7
0 E
LOG D
0 G
LOG
D=E log10G
D = E log10G
where D = output
E = multiplier
G = input
The output D will be log to the base 10 of the input G, if the value of E is specified as a constant of 1.00. For the module
to provide the logarithm output, G must be greater than 0 (if G is zero or negative, log10G is calculated as -20).
This function module could be used to provide the correct input scaling to a loop, for a logarithmic type sensor.
Alternatively the module could be used to provide a logarithmic scaled output to an analogue driver, suitable to drive
a logarithmic actuator.
14.9.1 Symbol
49
F10
0 E
2 D
0 G
SQUARE ROOT
D=E*SQRT G
DE G
where D = output
E = multiplier
G = input
If the value of E is set to one, the output will be the square root of G.
Mass Flow = K P
85 86
81
K=1 Mass Flow
Differential Pressure F36 S10
1 E V
S9 V 2 D F36D S
0 m S9V G INTERNAL
0 c
EXTERNAL SQUARE ROOT
0 Override Enable D=E*SQRT G
0 Override Value
Internal sensor 10 is used to provide rescaled high and low alarm limits
14.10.1 Symbol
42
0 E F3
0 F
D
0 G
0 H ADD/SCLR
D = (E * G) + (F * H)
D = (E x G) + (F x H)
where D = output
E = input 1
F = input 2
G = input 3
H = input 4
If G and H represent the two inputs and E and F are multipliers, then if E and F are specified as a constant of 1.00, output
D will be the sum of G and H.
The Adder/Scaler function module can be used to perform the y = mx + c function where y is the output D, x is the input
G, m is constant E, and c is input H (multiplied by constant F which is set to 1).
Subtraction can be achieved using the Adder/Scaler module by setting constant E to +1 and F to -1.
i.e. D = 10 x 1+5 x -1
= 10 - 5 =5 (i.e. a Subtractor)
14.11.1 Symbol
50
0 E F11
0 G D
0 F
MULTIPLY
D=G*E*F
D = GxExF
where D = output
E = input 1
F = input 2
G = input 3
If one of the inputs is specified as 1, output D will be the product of the other two inputs.
e.g. if F=1
D=GxEx1
14.12.1 Symbol
51
0 E F12
0 G D
0 F
DIVIDE
D=F(G/E)
GxF
D
E
where D = output
E = divisor
F = input 1
G = input 2
This module divides the product of G and F by E. If the input F is specified as a constant of 1.00, the output D will be
the result of G divided by E.
NOTES: Set input F to 1 to produce G/E. The function will calculate the output and limit it to the largest number it
can handle (i.e. to cater for divide by zero).
14.13.1 Symbol
52
nul E F13
nul F
D
nul G
nul H MINIMUM
D = minimum value of E or F or G or H.
where D = output
E = input 1
F = input 2
G = input 3
H = input 4
If one of the inputs is specified as a constant, the module output will have a maximum limit of the constant value set.
NOTE: Unused inputs must be left blank on the web page. In SET the input is separately identified by a click box as
not used, and the input is shown with a null value on the module symbol.
selection for
unused inputs
14.14.1 Symbol
53
nul E F14
nul F
D
nul G
nul H MAXIMUM
D = maximum value of E or F or G or H.
where D = output
E = input 1
F = input 2
G = input 3
H = input 4
If one of the inputs is specified as a constant, the module output will have a minimum limit of the constant value set.
NOTE: Unused inputs must be left blank on the web page. In SET the input is separately identified by a click box as
not used, and the input is shown with a null value on the module symbol.
selection for
unused inputs
14.15.1 Symbol
54
nul E F15
nul F
D
nul G
nul H AVERAGE
where D = output
E = input 1
F = input 2
G = input 3
H = input 4
NOTE: Unused inputs must be left blank on the web page. In SET the input is separately identified by a click box as
not used, and the input is shown with a null value on the module symbol.
selection for
unused inputs
14.16.1 Symbol
55
0 E F16
0 F D
0 B
GATE
D = F when B = 1
D = F when B=1
D = E when B=0
where D = output
E = input 1
F = input 2
B = control bit
D
F
The output D is normally connected to E, but when the relay is energised (B=1) it is connected to F.
14.17.1 Symbol
66
F27
0 E
D
0 F
COMPARATOR
D = 1 when F > E
D = 1 when F > E.
D = 0 when F = or < E.
where D = output
E = input 1
F = input 2
14.18.1 Symbol
67
F28
0 E
h D
0 F
ENTHALPY
E=%RH F=degC
0.0275 F 1
D E 10 F
The specific enthalpy is a measure of the total heat content per unit mass of a gas. It can be used in an air conditioning
system to calculate the positions of dampers so that the least energy is used to control the temperature and humidity
of a space (i.e. to decide whether to condition the outside air or the recirculated air).
14.19.1 Symbol
56
0 E F17
0 G D
0 F
HYST BAND
E=Level F=Band
where D = output
E = level
F = band
G = input
O U T P U T D
H Y S T E R E S IS B A N D F
0
IN P U T G
E
C O M P A R A T O R
L E V E L
The above function can be seen on the graph above. As G increases the output D stays at zero until G exceeds E+F/2
when the output D = 1.
As the input G drops the output D stays at 1 until the input falls below E-F/2 where the output D=0.
In this module, E defines the threshold level and F defines the band around the level within which input changes have
no effect.
When the module is first service (after a strategy download), if E is within the band, then the output is zero.
If the band is set to zero then noise on the input may cause the drive to switch ON and OFF at random.
If the band is made negative so that the off level is greater than the on level, the module becomes a 2 second oscillator
when the input is between the levels.
14.20.1 Symbol
57
a Bit 0
F18
b Bit 1
c Bit 2
0 G D d Bit 3
e Bit 4
A TO D f Bit 5
g Bit 6
h Bit 7
The value of output byte, D, is equal to the input value of G, but limited to the range 0 to 255, and is rounded up to the
nearest integer.
Bit 76543210
e.g. if G = -10 D =0 Output byte MSB 00000000 LSB
=4 =4 00000100
= 27 = 27 00011011
= 211 = 211 11010011
= 255 = 255 11111111
= 350 = 255 11111111
The A to D function module can be used in conjunction with a Digital Input Expander (4DIX) to expand the number of
digital inputs that an IQ can monitor.
In this example a single analogue input channel is used to handle four digital inputs. The binary number produced by
the four inputs (inputs A to D) produces a combined analogue signal which is input to the IQ via channel 1, scaled by
Sensor 11 and decoded by the A to D function module which produces 8 digital outputs. The four most significant
outputs (bits 7 to 4, labelled h to e) correspond to the four DIX inputs A to E. These digital outputs can be connected
to internal digital inputs as shown, and can then be used to generate alarms.
Note: When used with a 4DIX, the sensor type must be calibrated as defined by the 4DIX Data sheet.
Due to the response of the IQ3 sensor module it is possible for the A to D to sample the sensor output value while the
4DIX is in transition between states, resulting in incorrect outputs. In order to avoid this, the strategy has to be modified
to eliminate the transient values.
The SET 4DIX strategy block is shown in the diagram below. This strategy compares the sensor’s current value with
its previous value and if the value is not changing it is passed to the A to D function module where it is decoded to set
internal inputs 1 to 4 to the same status as the physical input to the 4DIX. This filters unwanted changes due to the
response of the input.
3 4Dix Input A
4Dix Previous Value
2 4 I1 S
S1V E F2 Is 4Dix Value Changing 4Dix Stable Value F4h
INTERNAL
0 F D F2D E F1 F3D E F3
0 Alarm Delay
0 B S1V G D S1V F D 0 Required State
GATE Disabled State Alarm
D = F when B = 1 4 F F1D B Hours Run
PROXIMITY GATE Starts
E +/- F D = F when B = 1 0 Override Enable
1 0 Override Value
4Dix Module 4Dix Input B
S1 5 I2
V a S
0 m 4Dix Value Decoder F4g
1 c b
EXTERNAL
F4 INTERNAL
c
Units F3D G D d 0 Alarm Delay
1 Type 0 Required State
0 Offset Signal Stable 1 second before decoding e Disabled State Alarm
270 High Alarm Limit A TO D f Hours Run
-10 Low Alarm Limit Starts
300 High Alarm Delay bit h - Input A g 0 Override Enable
300 Low Alarm Delay bit g - Input B h 0 Override Value
0 Out.Limits Delay
bit f - Input C 4Dix Input C
0 Read Alarm Delay
Disabled Read Alarm bit e - Input D I3 S
Disabled Out. Limits Alarm F4f
Disabled Low Alarm INTERNAL
Disabled High Alarm
0 Override Enable
0 Override Value 0 Alarm Delay
0 Required State
Disabled State Alarm
Hours Run
Starts
0 Override Enable
0 Override Value
4Dix Input D
I4 S
F4e
INTERNAL
0 Alarm Delay
0 Required State
Disabled State Alarm
Hours Run
Starts
0 Override Enable
0 Override Value
On step 2, F1 checks to see if the sensor’s value is changing, by comparing the sensor’s current value with its previous
value (received from F 2). If the two values are within +/- 4 of each other the module decides that the sensor value is
not changing and sets its output (D) to ‘1’. If the two values are more than +/-4 apart the module decides that the sensor
value is changing and sets its output (D) to ‘0’.
On step 3, the current value of the sensor is then input by F2 which sets its output value to the new value so that it can
be used in the next comparison.
On step 4, F3 monitors the output of F1 along with the sensor’s current value. If the output of F1 is ‘1’ the output of F3
is set to the sensor’s current value. If the output of F1 is ‘0’ output of F3 is remains unchanged.
On step 5, the analogue to digital module (F4) takes the output (D) of F3 and outputs to 4 internal digital input modules
as in the original strategy above.
Connectives
The input/output characteristic table may have up to 20 points and is set up in a sensor type module whose Input Type
parameter must be set to Analogue Value (see Pt.2 section 29), and the sensor type module number (S) is referenced in
the function module. The table may have between 2 and 20 points which must be entered in the ascending order of the
input parameter (see example on next page).
The output value of the module is calculated by linearly interpolating between the relevant 2 points. If the input value
falls above or below the table range then the output value is calculated from the extrapolated straight line between the
first two points or the last two points respectively.
If the sensor type module’s Input Type is not set to Analogue Value, the function module output is set to 0.
14.21.1 Symbol
58
F19
0 G D
LOOKUP - 1
where D = output
G = input
14.21.2 Example
The graph below shows the non-linear relationship between the specific heat capacity and the temperature of water. This
could be used in heat metering as part of the calculation of Power (Watts) used from the volumetric flow rate and
temperature difference.
4240
4230
4220
4210
SPECIFIC
Heat Cap (J/kg)
4190
4180
4170
4160
4150
15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110
Temperature (Deg C)
Having calculated the mass flow rate, the specific heat capacity at a given temperature can then be used to calculate the
power used in Joules per second (i.e. Watts).
So the sensor type module will be set for 19 points, with temperature (°C) as the input, and specific heat capacity (J/kg)
at that temperature as the output using figures from the table of values below.
14.22.1 Symbol
59
0 E F20
0 F
D
0 G
0 H ADD
E+F+G+H
D = E+F+G+H
Where D = output
E = input 1
F = input 2
G = input 3
H = input 4
14.23.1 Symbol
60
0 E F21
0 G D
0 F
HYST LIMIT
E=Low F=High
Where D= output
E= low limit
F= high limit
G= input
When the module is first service (after a strategy download), if G is within the band, then the output is zero.
OUTPUT D
1
INPUT G
E F
LOW LEVEL HIGH LEVEL
The way the function operates can be seen from the graph above. As G increases the output D stays at zero until the
level F is reached when D switches to 1. As G decreases the output D stays at 1 until the level E is reached when D switches
to 0.
This enables the high and low levels to be set separately as shown in the diagram below:
Low Limit
82
K7
0
D
KNOB K7D E F37
0 G D
High Limit
K8D F
K8 HYST LIMIT
0 E=Low F=High
D
KNOB
If the high level is set below the low level, the module becomes an oscillator with a 2 second period.
14.24.1 Symbol
61
0 E F22
0 G D
0 F
PROXIMITY
E +/- F
D = 1 if |E -G| <= F
D = 0 if |E -G| > F
|E-G| is the unsigned (absolute value or modulus of) difference between E and G.
Where D = output
E = input 1
F = maximum difference (proximity)
G = input 2
See section 14.20.2 above for an example of the use of the proximity function module.
Note that the proximity, F, should not be set less than 0.1, otherwise it would be difficult to check the operation of the
module as the web page’s value resolution is limited to two decimal places.
14.25.1 Symbol
62
F23
0 E
EF D
0 F
POWER
Where D = output
E = input 1
F = index
The index may be a non-integer e.g. F = 2.56. This enables an anti-log function to be performed.
e.g. if log10x = 3.44, then we can find x by:
x = antilog (3.44) = 103.44
so using the power function module,
if E = 10, F = 3.44,
then D = 103.44 = antilog (3.44) = 2754
i.e. x = 2754
14.26.1 Symbol
63
F24
0 G D
ABSOLUTE
where D = output
G = input
14.27.1 Symbol
64
F25
0 G D
TRUNCATE
D = integer value of G
where D = output
G = input
or if G = -23.468, D = -23
14.28.1 Symbol
65
F26
0 G D
TRIG - SIN
Degrees
Where D = output
G = input
TRIG is a trigonometric function (either sine, cosine, or tangent)
The function module has a sub type parameter which selects the particular trigonometric function from either sine,
cosine, or tangent.
The function module also has an angle type parameter to set the units of angle to be either degrees or radians.
e.g.
Angle Type: (digital, constant) This defines the units of angle used. It can be set to either degrees of rotation or radians.
TYPE
comms
SET Web page Low High
co d e
Controller Parameters
Source E R/W R/W* E -1020 1 0 20 0 The value of input E to the function
SOURCE/
CONST
(SET: Input E) module. Can be connected to an
analogue output.
SOURCE/
CONST
(SET: Input F) module. Can be connected to an
analogue output.
SOURCE/
CONST
(SET: Input G) module. Can be connected to an
analogue output.
SOURCE/
CONST
(SET: Input H) module. Can be conneced to an
analogue output.
OUTPUT
-1020 1 0 20 function module types 15, 17 ,21, 22;
-1020 to +1020 for all others. Can be
connected to a module input (digital for
types 15, 17, 21, 22; analogue for all
others).
Type R/W R Y 1 26 specifically The type of function module. See table
CONST
characters
Sequence Step R/W R @ 0 500 specifically The sequence step at which the module
set up by is serviced. If left blank in SET the
CONST
SET file
* This source/constant parameter cannot be changed via the web page if it is set as a source.
In some types of function modules the inputs have specific roles as described in the table below. Check relevant previous
section for input roles for a particular type of function module.
Input 1 2 3 4/5 6/7 10 16 17 21 22 23
Filter Rescale From Rescale To Limit At/To Log/ Divider Enthalpy Hysteresis Hysteresis Proximity Power
Square Root Band Limits
E Filter factor Lower limit Lower value Upper limit Multiplier Divisor RH Level Low limit Input Input
F X Upper limit Upper value Lower limit X input Temp Band High limit Max Diff Index
G Input Input Input Input Input Input X Input Input Input X
H X X X X X x X X X X X
TYPE
comms
SET Web page Low High
co d e
SOURCE/
ONST
(SET: Input B) to a digital output.
OUTPUT
(SET a) byte. Can be connected to a digital
input.
OUTPUT
(SET b) byte. Can be connected to a digital
input.
OUTPUT
(SET c) byte. Can be connected to a digital
input.
OUTPUT
(SET d) byte. Can be connected to a digital
input.
OUTPUT
(SET e) byte. Can be connected to a digital
input.
OUTPUT
(SET f) byte. Can be connected to a digital
input.
being used
1 = cosine module
2 = tangent
Angle Type R/W R/W R 0 = degrees 0 The units of angle used
CONST
1 = radians
* This source/constant parameter cannot be changed via the web page if it is set as a source.
IC Comms should not be used across an auto-dialling connection. Their use across routers is covered by the statement
in Pt. 1 section 3.3.8.
The IC Comms module does appear on the strategy page and does not need to be sequenced. IC Comms initiated in other
controllers and received in this controller can be represented on the strategy page (see 15.2.4 below).
There are 9 types (Direction Classes) of IC Comms available in the IQ2 and IQ3.
Direction Class Initiated by IQ3 IC Description
Comms module
IQ3 SET
Title Class Title Class
Data To 1 Data To 1 Yes Send data to another controller
Minimum 3 Minimum 3 Yes Request the minimum value from a set of controllers
Maximum 4 Maximum 4 Yes Request the maximum value from a set of controllers
Sum 5 Sum 5 Yes Request the sum of values from a set of controllers
Average 6 Average 6 Yes Request the average of values from a set of controllers
Analogue Data From 7† Data From 0† Yes Request analogue data from another controller
Byte Data From 8† Yes Request digital byte data from another controller
Bit Data From 9† Yes Request digital bit data from another controller
In addition to the functionality of the IC Comms module to initiate IC Comms to both IQ controllers and BACnet devices,
this section also deals with the ability of the IQ3 to process IC Comms received from other IQ controllers.
Note that IC Comms with IQ1 v3 firmware controllers are similar to those with IQ2 controllers except the IQ3 can only
receive messages initiated by the IQ1 (e.g. Data To from IQ1), not send them. However, IC Comms with IQ1 v4.1 firmware
or greater controllers can be considered to be the same as those with IQ2 controllers.
In order to receive an Analogue Data To or Data From IC Comm addressed to an analogue node the IQ3 must have the
analogue node previously configured in SET.
In order to receive a Digital Byte Data To or Data From IC Comm the IQ3 must have the digital byte previously configured
in SET.
In order to receive a Digital Bit Data To or Data From IC Comm addressed to a digital bit the IQ3 must have the digital
byte previously configured in SET. The Digital Bit IC Comm will only set up one bit of the byte module.
In order to receive other direction classes the IQ3 may be required to have an analogue node or digital byte set up if the
IC Comm is addressed to a node or byte rather than another parameter.
N1 N2 a
A0V R L b
c
remote point Trend FROM analogue B0S d
R
(analogue) 0 Remote Address output e
0 Remote Lan
0 Message Interval remote digital f digital byte
Failed Bit byte g
output
h
Trend FROM
0 Remote Address
0 Remote Lan
0 Message Interval
Digital Bit Data From Failed Bit
Failed bit
N3
B0S0 R L
The Data From message is sent from one controller to another requesting a value from that controller. This controller
is identified by its address on the Lan. The variable can be analogue, digital byte, or digital bit.
Since the IQ3 byte module has no strategy input, Digital Byte Data From IC Comms between IQ3s are of little use. The
Digital Bit Data From IC Comms are similar if using byte/bit as item selection, but if using switch or digital input status,
they work fine.
In general it’s better to set up a Data To in the remote controller rather than a Data From in the local controller as a Data
From requires 2 messages whereas a Data To just requires one, and also when sending a Data To, the sender can choose
to send on a significant change whereas a Data From has to be sent at regular intervals.
Data From IC Comms are available in IQ3v2.0 or greater; earlier versions of IQ3 can only respond to Data From messages,
not initiate them. In versions of IQ3 prior to v2.0, in order for controller A to receive a value from controller B rather than
a Data From being set up in controller A, a Data To must be set up in controller B. An alternative is to use a Maximum
or Minimum IC Comms in which case the IC Comms can be set up in controller A; the disadvantage in using one of these
is the system communication overhead in using attribute addressing (i.e. the message is sent to a number of controllers,
each of which has to check its attributes).
N5
A1V R L N5L V A1 D
Analogue
Read Alarm
Trend FROM
22 Remote Address
Out. Limits Alarm
Low Alarm
alarm status bits
0 Remote Lan High Alarm
5 Message Interval
Failed Bit
The analogue Data From IC Comm also carries the alarm status bits associated with the remote analogue point. These
status bits (ROLH, see Pt. 1 section 12.4.3) will be passed through the strategy to be used downstream so that function
or loop modules can take specific action in the case of sensor failure. They can be exposed by connecting the IC Comms
module output to an analogue node module as shown above.
If a reply to a Data From is not received after 3 tries at about 15 s (see section 15.9 below) then the Failed bit is set; the
Read alarm status bit will also be set in the case of an analogue Data From.
N6 A0V N9 A0V
0 L R 0 L R
Significant change
Global To has ‘attribute’ instead
- only on analogue ‘To’ types
of ‘address’
B0S
N7 local point N8 B0S
0 L
R
(digital) 0 L R
remote point
local point Trend TO remote digital Trend TO (digital)
(analogue) 0 Remote Address byte 0 Remote Address
0 Remote Lan 0 Remote Lan
0 Message Interval 0 Message Interval
Failed Bit Failed Bit
The Data To message is sent from one controller to another. The remote controller is identified by its address on the Lan.
The variable can be analogue, digital byte, or digital bit. The significant change parameter is only available on analogue
variable types.
The Global To message is sent from one controller to a set of other controllers. The remote controllers are identified by
an address attribute; the message can be sent to a single Lan or every Lan (Lan 128). The variable can be analogue, digital
byte, or digital bit. The significant change parameter is only available on analogue variable types.
The disadvantage in using a Global To is the system communication overhead in using attribute addressing (i.e. the
message is sent to a number of controllers, each of which have to check their attributes).
Note that both analogue To types of IC Comms will also send accompanying alarm status bits (ROLH, see Pt. 1 section
12.4.3) if they are available. These bits would be exposed by the receiving analogue node.
N5
0 S L
local point
remote point MAX
0 Remote Attributes (analogue)
(analogue) 0 Remote Lan
0 Message Interval
Failed Bit
Note that if a receiving controller has a Read or Out of Limits alarm bit set it will not contribute to the reply.
Technical Note:
These types of IC Comms use visitor text communications.
The message has to travel from one controller to the next in the set of controllers involved. The controllers have each
to check for an attribute match before deciding whether they should contribute to the message.
For a maximum they will only substitute their value if it is greater than the current value.
For a minimum they will only substitute their value if it is less than the current value.
For a sum they will add their value to the current value.
For an average they will add their value to the current value but also increment the number of controllers contributing
count. The initiating controller will calculate the average by dividing the sum by the number of controllers count on receipt
of the return message.
It can be seen that there is a system communications overhead involved in visitor messages and that they should be
used with discretion.
SET provides a drawing symbol for a dummy IC Comms. This can be used to show the effect on the strategy of an IC
Comms initiated elsewhere. This symbol will only appear on the SET strategy page it will not be sent to the controller,
and therefore will not appear in an uploaded strategy file (see Pt. 2 sections 6.3, 6.4).
OAT
IQ24, Lan 6 A8
0 V D
S6, OAT Analogue
Read Alarm
Out. Limits Alarm
Low Alarm
High Alarm
In the above diagram an IC Comms from IQ outstation 24, Lan 6 is sending the Outside Air Temperature value from Sensor
6 to Analogue node 8. Note that S6’s alarm bits will be copied to A8’s.
The Protocol parameter in the IC Comms module can be set to either Trend, or BACnet. The selected protocol is shown
in the bottom left corner of the module symbol.
Trend Analogue Data To BACnet Analogue Data To
BACnet IC Comms supports Data From, Data To, and Global To Direction Classes, but not Minimum, Maximum, Sum,
or Average.
The Data From, Data To, and Global To BACnet IC Comms support Analogue and Digital Bit Variable Types, but not
Digital Byte.
In order to send a BACnet IC Comms, the network module type 5 (BACnet) must be set up (see Pt. 2 section 20), and
a Non-Trend Device module (NTD module, see Pt. 2 section 21) must be set up for the BACnet device being communicated
with.
The NTD module is allocated a Lan number (for the Trend BACnet Lan), a node address on that Lan, and address attributes
so that the controller selection process described on section 15.4 below operates similarly for both Trend and BACnet
protocol IC Comms. For a Trend protocol Global To, the Remote Lan can be set to 128 (a global message to every Lan,
i.e. a global global), but this is not allowed for BACnet protocol.
BACnet item selection is similar to that for the Trend protocol, except that BACnet variables must be specified; this is
explained in section 15.5.2 below.
As explained in Pt.1 section 3.7.3, because IQ3/BAC responds to BACnet comms, it is possible to send BACnet IC Comms
between IQ3/BACs. This is not recommended as a permanent installation, but it can be useful to prove that the BACnet
IC Comms setup works correctly (e.g. using web pages the change of values can be monitored in each IQ3).
Remote Lan
Lan number zero specifies the local Lan
Lan numbers 1 to 119 (excluding 2, 3, 10) specify Lans via the internetwork.
Lan number 128 is not permitted
Remote Address
Addresses 1 to 119 (excluding 2, 3, 10) can be selected.
Remote Lan
Lan number zero specifies the local Lan.
Lan numbers 1 to 119 (excluding 2, 3, 10) specify Lans via the internetwork.
Lan number 128 specifies every Lan. It may not be used with Max, Min, Sum, or Average messages (i.e. only Global To).
It may not be used with the BACnet protocol.
Remote Attributes
The Remote Address selection for direction type Data To, automatically changes to Remote Attributes selection for
directions Global To, Min, Max, Sum and Average.
Thus for one controller to communicate with other controllers, all must have a matching attribute set up in their respective
address modules.
Wildcards:
* ? & ¦ .
may be used - see section 15.4.3 below.
* is a wildcard character that can be included in an attribute to allow any character, no character, or group
of characters to match that position in the initiator’s attribute e.g.
The way the wildcard, *, works in Trend text comms is unusual. If the text comms request is S{$=”S* Fred”}($), this should
only match if the characters ’Fred’ come at the end of the label.
However in IQ3 the request will match with S1($=”Sensor 1") as the character ‘*’ is taken to mean any other characters
(so the ‘Fred’ element is ignored). In IQ2 abc*ghi will not match with abc*abc, in IQ3 it will match.
? is a wildcard character that can be included in an attribute to allow any single character to match that
position in initiator’s attribute (there must be a character) e.g..
& (ampersand) is a special character. When placed in an attribute, the message may only be delivered if the
destination has two separate attributes that match the characters either side of the ‘&’.
. is a special character. This special character only has special effects in IC Comms; when placed in an
attribute the text beyond the first fullstop is ignored and the full stop is replaced by a wildcard * e.g.
When the originating controller sends a message, the attribute is truncated to FL3*.
The attribute will work as normal for matching with incoming text messages, e.g. the supervisor can obtain
the average from this controller by requesting FL3.LEADER.
The item (analogue point, digital point, or digital byte) to which the communication is sent can be selected either
absolutely or by label matching.
Note that Data From Direction Classes IC Comms cannot be set up to use label matching item selection using SET.
However, they can be set up to use label matching from the web page by setting the Remote module to blank. The
addressed IQ3 will only match on the first occurrence of the label. From IC Comms cannot be sent to more than one
controller.
To use label item selection the Remote Module (in web page) or Remote Node (in SET) must be left blank. In SET this
is done by selecting the Remote Node Label Matching tick box.
The message will then be sent to point(s) of the correct variable type with a label that matches the label of the local point.
There is a controller overhead in using item label selection due to the load involved in checking all the controller labels
for a match. This may cause the IC Communication to take longer. Item label selection should be used with discretion.
If the local point doesn’t have a label, the IC Comms will not operate.
The only remote modules that are checked for label matching are Sensors, Digital Inputs, Knobs, Switches, and Drivers.
Data transference will be attempted with all the relevant modules in the destination controller(s) that have a label match.
If more than one of relevant remote modules have the matching label they will each act on the message.
The variable type transferred using label matching is either a value (V) for an analogue value, or a status (S) for a digital
status. The four alarm bits (ROLH, bits 3 to 0 respectively) are also transferred (if they exist e.g. they don’t exist for a
knob) along with the analogue value.
The item label may contain the wildcards (see 15.4.2 above):
? * .
The item label may not contain:
\ / ( { ; , :
Once the IC Comms message is received by one of the relevant modules with a matching label, the message will only
be processed further if the variable type (V, S or alarm bits) is present in the module.
For the Max, Min, Sum, and Average communications, the variables are always analogue. Since these functions ask for
analogue values which may be contributed to from a number of modules, if one of the modules has a value which has
associated Read or Out of Limits alarms then that module’s value will not contribute to the result.
In SET this is done by clicking on the ‘Look Up’ button. This produces a ‘Helper’ dialogue box which enables the selection
of the module type (which is an object type for BACnet) from a drop down list of appropriate types.
Trend IC Comms BACnet IC Comms
Basic module (object) types listed in the Helper dialogue boxes are shown in the table below:
Trend Protocol IC Comms Module Type Parameter C ode
Variable Type Direction Classes
Analogue Data To, Global To Analogue Node Value AnV
Knob Value KnV
Byte Data To, Global To Byte Status BnS
Bi t Data To, Global To Bi t Status BnSm
Switch Status WnS
Analogue Data From, Max, Min, Sum, Average Analogue Node Value AnV
Knob Value KnV
Sensor Value SnV
Byte Data From *Byte Status BnS
Bi t Data From *Bit Status BnSm
Switch Status WnS
Digital Input Status InS
BACnet Protocol IC Comms Object Type Property C ode
Variable Type Direction Classes
Analogue Data To, Global To, Data From Analogue Input Present Value AIn
Analogue Value Present Value AVn
Analogue Output Present Value AOn
Bi t Data To, Global To, Data From Binary Input Present Value BIn
Binary Value Present Value BVn
Binary Output Present Value BOn
*Since IQ3 byte modules have no strategy input, Digital Byte Data From IC Comms between IQ3s are of little use. Digital
Bit IC Comms using a bit as the item are the same (but switch or digital input status as items are fine).
The basic items are selected by selecting the appropriate module (object) type from the drop down list, and then entering
the module number (instance number for BACnet). In the case of a Bit, the module number is given by byte number and
bit number. The selected module reference is shown in the Reference box (read only).
The above table also lists the parameters/properties used when using the basic module types from the Helper; for Trend
protocol this is either Value or Status, whereas for BACnet protocol it is always the Present Value.
The Helper dialogue box also has an ‘Advanced’ button. Selecting this enables the item to be selected by entering an
item code in the Reference box.
Great care should be taken when entering item codes by using the Advanced button as misuse may cause the remote
controller’s strategy to change; the user should be familiar with text communications (for Trend protocol) and BACnet
properties (for BACnet protocol).
BACnet property item codes are specified by <object type><instance><property> e.g. AI2PV, analogue input, 2, present
value.
The item code can also be entered or editted on the IC Comm Web Page using the Remote Module parameter. These item
codes are the same as those which can be entered in SET using the Advanced button
Great care should be taken when entering or editting the Remote Module Parameter on the IC Comm Web Page as
misuse may cause the remote controller’s strategy to change; the user should be familiar with text communications
(for Trend protocol) and BACnet properties (for BACnet protocol).
The safest way to set up the item code is to use the Helper dialogue box in SET without selecting the Advanced button
as SET will ensure that the remote module matches the local module connection
Absolute item selection presents less of a system overhead than item label selection and should be used in preference.
IC Comms
1
Sensor 1
S1
V
S1V S
INTERNAL
DegC Units
0 Override Value
Similarly an IC Comms write to a digital input (as described in 15.5.1 above) would normally use the ‘S’ parameter which
is actually the digital input output. This will be overwritten as the digital input is serviced. This problem can be overcome
for an internal digital input by connecting the output back to the input (loopback).
IC Comms
Digital Input 1
I1 S
I1S
INTERNAL
Both external analogue sensors and external digital inputs can’t be looped back, so IC Comms to them will be overwritten
when serviced. External and internal digital sensors have an analogue output with a digital input so can’t be looped back
directly. For these reasons it is recommended not to send IC Comms writes to external analogue and external and internal
digital sensors, nor to external digital inputs.
Other parameters which are normally accessed by label are switch, knob, and driver. IC Comms writes to switches and
knobs will not be overwritten as the parameter being written to is the input to the module. Similarly analogue node and
digital byte or bit which are normally accessed by absolute item selection will not be overwritten for the same reason.
IC Comms writes to drivers can be overwritten and should not be used.
IC Comms IC Comms
Switch 1 Knob 1
W1 K1
0 0
D D
SWITCH KNOB
0 Pin Level Units
For this reason there is an interval which can be set up for each communication which should be set to be the maximum
communication period that the system can stand. This period defines the time in minutes between sending the
communications (updating the value).
For Data From communications the minimum period between sending the messager is 15 s so that if the interval is set
less than this it will be sent again after 15s anyway. This should be avoided because of the communications’ overhead
involved, so the interval should be set non-zero.
For Data To and Global To communications the message will be sent whenever there is significant change (i.e. not just
at the specified interval).
For an analogue Data To or Global To communication a significant change is where the current analogue value differs
from the last analogue value sent by more than the significant change value (which can be set up) or the analogue alarm
status (ROLH) differs from the last status value sent.
For a digital Data To or Global To communication (both byte and bit) a significant change is where the current digital
value differs from the last digital value by any bit change.
For all Data To and Global To communications if no significant change is found, or if the significant change parameter
is set to zero, it will be sent at the retransmission (message) interval. If the interval is set to zero the communication only
occurs when there is a significant change.
For all Data To and Global To communications, once sent the communication will not be sent again for at least 15 seconds
to avoid a fluctuating value causing excessive transmission.
For MAX, MIN, SUM, and AVERAGE communications (i.e. visitor messages) if the retransmission interval is set to zero,
the message is immediately resent after the visitor message returns. This should be avoided because of the communications’
overhead involved, so the interval should be set non-zero. If the message fails to return, it is resent after 2 minutes.
These messages will contain the Personal Identification Number (PIN) code specified for User 1 (user module number
1). Controllers that are to receive these messages must contain a matching PIN whose authority level is high enough
to permit the change requested unless there are no user modules set up in which case the change will be permitted.
The level required in the remote controller for the selected PIN must be 99 for a Global To and 95 for a Digital To ; for
a change to a knob or a switch it must be equal to or greater than the PIN level for that particular item.
If the User 1 PIN in the sending controller is not set up, the message will be sent without a PIN.
NOTE: The expression MOD15 means the remainder left after dividing by 15. For example controller 20 will have a
delay of (60+20MOD 15). The remainder after dividing 20 by 15 is 5, so the delay will be (60+5=65 secs). Controller
21 would then have a value of 66 seconds etc. Note that controller 35 will also have a delay of 65 seconds.
The above strategy shows two bits produced by a digital input and a switch being converted to an analogue value and
then sent as a byte Data To IC comms. In a receiving IQ3 controller a digital byte module must be used to receive this
message.
The analogue value can also be created using gate function modules as shown in the example in section 15.11 below.
It is possible to access the LONC analogue node status by the text comms code Ax(S), where x is the node number.
The method in IQ3 is to use SET to set up an analogue Data To to send the analogue value, and a digital byte Data To
to send the status. The advanced button can then be clicked on the digital Data To, and the Reference entered as AxS
to write to the analogue status.
129
130
Sensor 15
S15 V
N22 A10V
0 m S15V L R
0 c
EXTERNAL
DegC Units Trend TO
0 Override Enable 11 Remote Address
0 Override Value 22 Remote Lan
1 Message Interval
0.5 Significant Change
Assume Failed Bit
IC Comms N21 is set up to write to a byte, and the Advanced button is selected in the Helper dialogue box, so that A10S
can be entered. The input to N21 is created by either gating through the value of 16 to create bit 5, or the value of zero
(all bits zero), dependent on the switch setting. This will then send the status byte to the analogue node 10.
IC Comms N22 is set up to write the analogue value to the LONC analogue node (Analogue 10).
BACnet protocol
Digital Byte
From has Value
parameter as a
binary string
Digital Byte
From has eight
digital outputs
instead of
Remote Module
parameter
Connectives
N5
A1V R L N5L V A1 D
Analogue
Read Alarm
Trend FROM Out. Limits Alarm
22 Remote Address Low Alarm
0 Remote Lan High Alarm
5 Message Interval
Failed Bit
This will request the value of analogue node 1 in controller 22 on the local Lan every 5 mins. An IQ3 receiving this request
would need analogue node module 1 to be created in SET.
N15 a N15a E G1
b J or
N15b F K or
c L or D
d 0 G M
B18S R
e 0 H
COMB
f
J Comb.
g K Comb.
h L Comb.
Trend FROM M Comb.
22 Remote Address
5 Remote Lan
0 Message Interval
Failed Bit
This will request the value of controller 22 byte 18 on remote Lan 5 every 5 mins and make it available as 8 output bits
from the IC Comms module.
This will request the status of controller 22 switch 2 on remote Lan 5 every 10 mins and make it available as a digital output.
Digital Input 13
I13 S
N11 B32S3
0 m I13S L R
0 c
EXTERNAL
0 Alarm Delay Trend TO
0 Required State 37 Remote Address
Disabled State Alarm 101 Remote Lan
Hours Run 10 Message Interval
Starts Failed Bit
0 Override Enable
0 Override Value
This will send the status of digital input 13 to byte 32 bit 3 in controller 37 on Lan 101 at least every 10 mins. An IQ3 receiving
this would need byte module 32 to be created in SET.
124
0 E F65
N12 A45V
0 G D F65D L R
FILTER Trend TO
D=E*D+(1-E)*G 35 Remote Address
6 Remote Lan
10 Message Interval
1 Significant Change
Failed Bit
This will send the value of Function module 65 to analogue node 45 in controller 35 on Lan 6 whenever the value changes
by 1, and at least every 10 mins. An IQ3 receiving this would need analogue node 45 to be created in SET.
This will send the value of Sensor module 12 to the value of an analogue module(s) (sensor, knob, or driver) with label ‘Space
Temp’ (i.e. sensor 12’s label) in controller 42 on Lan 7 whenever the value changes by 1, and at least every 10 mins.
This transfers the analogue value from Sensor 13 to analogue node 5 of any controller (with an attribute which matches
attribute 2) on any Lan (Lan 128 specifies any Lan). This will be sent whenever the value changes by 0.5, and at least
every 10 mins. Since attribute 2 in the address module of this controller is set to XYZ Co then this attribute would have
to be in any controller to receive this message. An IQ3 receiving this would need analogue node 5 to be created in SET.
This transfers the status from Switch 4 to the status of a digital modules(s) (digital input, switch, or driver) with label
‘Manual’ (i.e. Switch 4’s label) in any controller (with an attribute which matches attribute 2) on the local Lan (Lan 0
specifies local Lan). This will be sent at least every 10 mins. Since attribute 2 in the address module of this controller
is set to XYZ Co then this attribute would have to be in any controller to receive this message.
This transfers the status of the digital inputs to logic 24 to byte 24 in any controller (with an attribute which matches
attribute 2) on the local Lan (Lan 0 specifies local Lan). Since attribute 2 in the address module of this controller is set
to XYZ Co then this attribute would have to be in any controller to receive this message. An IQ3 receiving this would
need byte 24 to be created in SET.
This will request the maximum value of any analogue module(s) (sensor, knob, or driver) with matching label to analogue
node 4 from any controller (with an attribute which matches attribute 3) on the local Lan (Lan 0 specifies local Lan) and
write it into analogue node 4. This will be sent every 5 minutes.
Since this controller’s address module attribute 3 = AHU3, it will send this message to any controller with attribute AHU3.
Since the label of this controller’s analogue node 4 is DAMPER.MAX, it will send the message to any analogue module(s)
(sensor, knob, or driver) with label DAMPER*. If addressed controllers have analogue module(s) (sensor, knob, or driver)
labelled DAMPER POSITION, they will contribute to the maximum.
Cooling demand
N18
S L N18L V A5 D
Analogue
Read Alarm
SUM Out. Limits Alarm
3 Remote Attributes Low Alarm
7 Remote Lan High Alarm
1 Message Interval
Failed Bit
This will request the sum of values from any analogue module(s) (sensor, knob, or driver) with matching label to analogue
node 5 from any controller (with an attribute which matches attribute 3) on Lan 7 and write it into analogue node 5. This
will be sent every minute.
Since this controller’s address module attribute 3 = AHU3, it will send this message to any controller with attribute AHU3.
Since the label of this controller’s analogue node 5 is Cooling demand. It will request the sum of the values of any analogue
module(s) (sensor, knob, or driver) with label Cooling demand.
Heat Demand
N19
S L N19L V A6 D
Analogue
Read Alarm
AVERAGE Out. Limits Alarm
2 Remote Attributes Low Alarm
7 Remote Lan High Alarm
1 Message Interval
Failed Bit
This will request the average of values from any analogue module(s) (sensor, knob, or driver) with matching label to
analogue node 6 from any controller (with an attribute which matches attribute 2) on Lan 7 and write it into analogue
node 6. This will be sent every minute.
Since this controller’s address module attribute 2 = XYZ Co, it will send this message to any controller with attribute XYZ
Co. Since the label of this controller’s analogue node 6 is Heat Demand. It will request the average of the values of any
analogue module(s) (sensor, knob, or driver) with label Heat Demand.
With an Average type message the returning message actually contains the sum plus the number of contributors to the
sum, and the average is calculated by the IC Comms module by dividing the sum by the number of contributors. The
resulting average value is placed in the specified local node.
N12
AI0 R L N12L V A2 D
Analogue
Read Alarm
BACnet FROM Out. Limits Alarm
6 Remote Address Low Alarm
9 Remote Lan High Alarm
10 Message Interval
Failed Bit
Protocol: BACnet
Direction: 0 (Data From) (selected by choosing the icon in SET)
Variable Type: Analogue (selected by the variable type box in SET)
[This is equivalent to Direction 7, Analogue Data From in the IQ3, e.g. on the web page]
Remote Controller: 6
Remote Lan: 9
[A Non-Trend Device module would have to be set up for controller 6 on Lan 9; this module will convert the Trend address
to the BACnet address, see Pt. 2 section 21]
Local Module: A2V (selected by dragging a connection line on the strategy page in SET)
Remote Module: AI0 (from Helper)
Retransmission Interval: 10
This will request the value of analogue input 0 from the BACnet device specified by the Non-Trend Device Module set
up as controller 6 on Lan 9 every 10 mins.
0 E G3
J or N18
0 F K or BV3
L or D G3D L R
0 G M
0 H BACnet TO
COMB 6 Remote Address
J Comb. 9 Remote Lan
K Comb. 5 Message Interval
L Comb. Failed Bit
M Comb.
Protocol: BACnet
Direction: 1 (Data To) (selected by choosing the icon in SET)
Variable Type: Bit (selected by the variable type box in SET)
Remote Controller: 6
Remote Lan: 9
[A Non-Trend Device module would have to be set up for controller 6 on Lan 9; this module will convert the Trend address
to the BACnet address, see Pt. 2 section 21]
Local Module: G3S (selected by dragging a connection line on the strategy page in SET)
Remote Module: BV3 (from Helper, label matching unticked in SET)
Retransmission Interval: 5
This will send the logic module 3 output status to the BACnet device specified by the Non-Trend Device Module set
up as controller 6 on Lan 9 every 5 mins.
0 E F1
N19 AO2
0 G D F1D L R
Protocol: BACnet
Direction: 2 (Global To) (selected by choosing the icon in SET)
Variable Type: Analogue (selected by the variable type box in SET)
Remote Attributes (Web page: Attribute): 6
Remote Lan: 9
[A Non-Trend Device module would have to be set up for controller 6 on Lan 9; this module will convert the Trend address
to the BACnet address, see Pt. 2 section 21]
Local Module: F1D (selected by dragging a connection line on the strategy page in SET)
Remote Module: AO2 (from Helper, label matching unticked in SET)
Retransmission Interval: 15
Significant Change: 0.5
This will send the function module 1 output value to the BACnet devices specified by the Non-Trend Device Modules
set up with an attribute ‘Aircon1’ on Lan 9. Note that this attribute should only be present on the BACnet NTDs (on
BACnet Lans) not on controllers on Trend Lans.
This will be sent when there is a change in Function 1’s output by 0.5, or after 15 minutes, whichever is the sooner.
128
Outside Temp.Orig
S14 V
N20
0 m S14V L R
0 c
EXTERNAL
DegC Units Trend GLOBAL TO
0 Offset 7 Remote Attributes
0 Override Enable 128 Remote Lan
0 Override Value 10 Message Interval
0.5 Significant Change
Failed Bit
The message is sent from this controller sensor 14 to any controller on any Lan (signified by Lan 128) with an attribute
which matches attribute 7 (which is a wildcard *), so it is sent to every controller. The remote node is selected by item
label attribute using the label of sensor 14 which is Outside Temp.Orig. This will be truncated to Outside Temp* which
will match with Outside Temp.Copy if set up in the receiving controllers.
This will be sent when there is a change in sensor 14’s value by 0.5, or after 10 minutes, whichever is the sooner.
The Digital Byte module in IQ3 has not a strategy input so the Digital Byte Data From between IQ3s is of little use.
IQ3 Data From, Data To, and Global To communications can be addressed to points other than analogue nodes, or digital
nodes or bytes (from the SET ‘Advanced’ button or the web page).
For an IQ3 to receive IC Comms addressed to analogue nodes, or digital nodes or bytes the analogue node or digital byte
must be created in SET. (In IQ2 they were all available by default.) In IQ3 for Data To and Global To Byte communications
the byte value has to be created from the digital bits by a D to A logic module or gate function modules.
IQ2 was able to send additional status bits along with an analogue IC Comms. IQ3 will only send the first 4 bits (bits 0
to 3).
IQ2 was able to use zone labels as device attributes. This is not supported on IQ3.
The IC Comms fail bits are available as module outputs in IQ3; they were available in the digital array in IQ2.
15.16 Parameters
15.16.1 Inputs and Outputs
Local Module (SET: Source - for entering a value for To type comms only): (analogue or digital, source/constant or
output). The local point to or from which the communication is to occur.
It is set up by making a connection between the local module and the IC Comms module in SET. The point has to be either
an analogue input or output, or a digital input or output dependent on the variable type and direction type.
In SET for Data To or Global To comms the input can either be sourced from a module’s output or set to a constant value;
if connected to a module’s output the output’s details will be shown on the web page.
For Data From and Max, Min, Sum, and Average comms Local Module is an output. If connected to a module’s input,
the input’s details will be shown on the web page.
It is available as a connective in SET (e.g. NnL, where N=IC Comms module, n = IC Comms module number, L = output).
BIT0 to BIT7 (SET a to h): (digital, output): The 8 digital outputs of a Digital Byte Data From IC Comms. Replaces Local
Module for Digital Byte Data From IC Comms. If any are connected to modules’ digital inputs, the inputs’ details will
be shown on the web page. They are available as connectives in SET (e.g. Nn,0 to Nn,7, where N=IC Comms module,
n = IC Comms module number, 0 to 7 are bits 0 to 7).
Remote Module (SET: Remote Analogue, Remote Byte, Remote Bit or Remote Node dependent on Variable Type): (string,
constant) The remote point to or from which the communication is to occur. It is entered in SET by using the Helper;
for Trend protocol comms a number of module types are available, and the module number has to be entered; for BACnet
protocol comms a number of BACnet objects are available and the object instance must be entered. The ‘Advanced’
button enables any compatible Trend parameter or BACnet property to be specified but see 15.5.2 above. The point has
to be either an analogue input or output, a digital byte input or output, or a digital bit input or output dependent on the
variable type and direction type.
If the point is set to zero the remote point is addressed by using the label of the local module as an attribute and the remote
point is found by a label match; in SET this is done by using the Label Matching tick box. Use of label matching item
selection causes a controller overhead, see 15.5.1 above.
Label Matching (SET only): If this tick box is ticked it forces label matching item selection and sets the remote module
to zero.
Remote Lan: (analog, source/constant) The Lan of the controller containing the Remote Module. If set to zero, the
controller is a member of the local Lan. For Trend protocol Global To IC Comms, the Lan number can be set to 128 which
will cause the IC Comms will be sent to all Lans (this is not available on other directions or for BACnet protocol).
It can either be sourced from a module’s analogue output or set to a constant value. If connected to a module’s analogue
output, the output’s details will be shown on the web page.
Remote Controller Address (SET: Remote Address): (analogue, constant) The address of the controller containing the
Remote Module on the Lan. It is only available on Data From or Data To communications.
It can either be sourced from a module’s analogue output or set to a constant value. If connected to a module’s analogue
output, the output’s details will be shown on the web page.
Attribute (SET: Remote Attributes): (characters, constant) The attribute used to select the controller(s) containing the
Remote Module on the Lan. The controller(s) is selected by label match between the remote attribute and one of its
attributes. Special characters may be used, see section 15.4.2 above. The attributes are 1: Identifier and 2 to 7 which are
attributes 2 to 7 in the address module. This is not available on Data To communications.
Failed Bit: (digital, output) If the time for an IC Comms retry has been reached as described in 15.9 above, and the last
try was not acknowledged, then the IC Comms Failed Bit output is set to one. If the most recent transmission was
acknowledged, the bit will be cleared to zero.
If connected to a module’s digital input, the input’s details will be shown on the web page. The output is shown as a
connective in SET (e.g. NnF, where N=IC Comms module, n = IC Comms module number, F = failed bit).
Comms Direction: (analogue, constant) The type of IC Comms. Set up in SET (not changeable on web page):
Direction classes in the controller are Data To, Global To, Maximum, Minimum, Sum, and Average, Analogue Data From,
Byte Data From, Bit Data From. In SET the Analogue Data From, Byte Data From, Bit Data From classes are all set up
as Data From, and the Variable Type is used to define the variable.
Variable Type: (analogue, constant) The type of variable being transferred. Can be set to analogue, digital bit, or digital
byte. In the controller Data From class IC Comms do not have a Variable Type parameter as the variable type is included
in the direction class.
Maximum, Minimum, Sum , and Average type comms can only be analogue. BACnet IC Comms can only be analogue
or digital bit.
Significant Change: (analogue, constant) Only used in analogue Data To and Global To IC comms. It defines the amount
by which the local point value has to change before the IC Comms is sent. It should be set as large as possible to minimise
communications traffic. If set to zero the IC comms will be sent at the retransmission interval. Digital Byte and Bit IC comms
are sent on change of status. All IC Comms are sent at retransmission interval anyway.
Time into the Interval: (analogue, status) The number of minutes since the start of the retransmission interval.
Last sent: (analogue, status) Only used on Data To and Global To type comms. The value or status of the local module
when last sent; for analogue and digital byte it will be a value, for digital bit it will be a status.
Label: The label shown in the module symbol in the SET strategy page and in the Web pages.
Disable Module (SET: Module State - Enabled/Disabled): This input will disable the module, i.e. prevent the IC Comms
form sending any messages. Its internal states and output will be maintained at their values prior to disabling. This input
can either be sourced from a digital output, or set to a constant value (0 or 1). If connected to an output the source address
will be shown on the web page.
Output Type: (used on IC Comms number box). The IC Comms variable type (analogue, digital byte or digital bit).
Module Type: (used on SET Helper box). This defines the module type (for Trend Protocol) or the object type (for BACnet
protocol) from a drop down list.
Number: (used on SET Helper box). This is the Trend module number or the BACnet object instance.
Reference: (used on SET Helper box). This is the full Trend parameter or BACnet object type code formed by combining
the Module type and number described above. For Trend protocol it also includes the parameter code (e.g. V:value,
S:status).
Advanced: (used on SET helper box) This button enables the full item code to be entered. Care should be taken if this
is used, see 15.5.2 above.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Local Module R/W R/W* L 0 1 0 The status or value of the local module
(SET: Source, for or or connection. 0 or 1 for digital bit; -1020 to
Data To or Global -1020 +1020 +1020 for analogue or digital byte type
To type comms comms.
only) For Data To or Global To type comms it can
SOURCE/CONST/OUTPUT
be either a source or constant input; it can
be connected to either an analogue output
for analogue or digital byte comms, or
digital output for digital bit comms.
For Digital Byte Data From type comms it
is replaced by output BITs 0 to 7, see
below.
For other Data From, or max, min, sum,
avge the output can be connected to an
analogueinput for analogue or digital byte
comms, or digital input for digital bit
comms.
BIT0 R R a 0 1 0 Digital status of output bit 0. For Digital
OUTPUT
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Remote Lan R/W R/W* N 0 119 0 Lan number of controller(s) being
(128) communicated with. Valid range 1, 4 to 119
SOURCE/CONST
excluding 10.
Lan 0: local Lan
Lan128: all Lans (only available on Global
To comms; not available on BACnet
Comms).
Can be connected to an analogue output.
SOURCE/CONST
Remote Controller R/W R/W* A 0 119 0 Address of controller being communicated
Address with (only available on Data From or Data
(SET: Remote To comms)
Address) Valid range 1, 4 to 119 excluding 10.
Can be connected to an analogue output
Attribute R/W R/W B 0 7 0 Attribute used to select remote controller.
(SET: Remote Attributes in address module.
CONST
Attributes) 1: Identifier
2 to 7: Attributes 2 to 7
0: comms disabled
Not used for Data From or Data To comms
Failed Bit - R/W F 0 1 0 Indicates the IC Comms has failed.
OUTPUT
0=OK
1=Failed
Can be connected to a digital input
Protocol R/W R/W P 0 1 0 The protocol bring used for the IC Comms:
CONST
0=Trend
1=BACnet (IQ3/BAC controllers only)
Comms Direction R/W R D 1 9 (specifical- The type of IC Comms:
ly set up in 0: Data From (SET only)
SET) 1: Data To
2: Global To
3: Minimum
4: Maximum
CONST
5: Sum
6: Average
7: Analogue Data From (controller only)
8: Byte Data From (controller only)
9: Bit Data From (controller only)
SET has type 0, Data From and then
enables variable type selection; the
controller has types 7, 8, 9 as above and
no variable type selection
Variable Type R/W R/W V 0 3 (specifical- Type of variable:
ly set up in 0: analogue
SET) 1: digital byte
CONST
2: digital bit
Comms types min, max, sum, average are
analogue only. Digital byte IC Comms are
not available in BACnet comms.
Variable type parameter is not used in the
controller for directions 7, 8, 9, see above.
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
comms
SET Web co d e Low High
page
Controller Parameters
Retransmission R/W R/W I 0 1440 1 Length of time (minutes) between
Interval instances of sending IC Comms. Data and
Global To comms may be more frequent
CONST
according to significant change. Set as
minutes large as possible.
if 0: To comms sent only on sig change,
Data From and max, min, sum, avge sent
as soon as reply received.
Significant Change R/W R/W S 0 3276 0 Analogue Data To and Global To only:
CONST
Amount by which local module value has to
change before IC Comms is sent. If set to
zero will be sent at Retransmission Interval.
Time into Interval - R/W T 0 +3276 0 Number of minutes since start of
STATUS
retransmission interval.
minutes
STATUS
(lower or or local module when last sent; value for
case L) -1020 +1020 analogue and digital byte, status for digital
CONST
bit comms
Label R/W R/W $ 0 30 null Label of module
characters
P age R/W R/W p 0 255 0 Number of page containing module in SET
CONST
file
SOURCE/CONST CONSTCONST
State parameter
I/O Module Details Page
I/O Setup
Connectives
If the a strategy I/O module at that address has already been created in SET, then it will not create a new one, but will
set the ‘actual type’ field in the SET created module (the default is a blank actual type field).
It will also set up the State, Failed, and Firmware version parameters.
Automatic strategy I/O module creation enables the engineer to see the details of the modules actually connected to
the I/O bus and their status. This is useful for I/O bus fault finding.
Note that an automatically created module will not be archived so it will disappear on a controller power cycle. This means
that if a hardware I/O module is added to the I/O bus and subsequently removed, the strategy I/O module will be
automatically created, but will exist only until the next power cycle.
If an automatically created strategy I/O module is edited (e.g. by text comms or by webpage) it will be archived and will
persist through power cycles.
Each module is given a module ID corresponding to its address switch setting, and module type (see 16.4 above), and
a 30 character label.
16.7 Parameters
Label: (characters, constant) A label shown in the SET dialogue boxes and the webpages. It is entered in SET into the
I/O module setup box, and appears on the SET I/O Setup box. If discovered by automatic identification and not set up
by SET, it defaults to the hardware module’s actual type (e.g. XCITE/IO/8UI).
Module ID (SET only): The module ID is the module address on the I/O bus. A module ID of zero is given to the main
controller and the I/O modules that can be added have the IDs 1 to F (corresponding to 1 to 15). This corresponds to
the module number on the webpage. The module address is set by its address switch; if its address switch is set to zero,
the module is disabled. This parameter is called I/O Module ID on the SET I/O Setup box, and here it shows both decimal
and hexadecimal representation: 0-0 (Base IO), 1-1 through to 9-9, then A-10, B-11, C-12, D-13, E-14, F-15
I F O F (SET only): These columns in the I/O Setup box indicate the I/O channels as follows:
I, inputs; F, free inputs; O, outputs; F, free outputs
Configured Type (SET: Module Type): (characters, constant) This is the type of module set up in SET. If the module has been
automatically created due to the I/O module’s discovery by the IQ controller, and not set up in SET, this parameter will be blank.
The type can be set to one of the following:
XCITE/IO/8UI (8 Universal Inputs)
XCITE/IO/4UI (4 Universal Inputs)
XCITE/IO/4UI/4AO (4 Universal Inputs plus 4 Analog Outputs)
XCITE/IO/2UI/2AO (2 Universal Inputs plus 2 Analog Outputs)
XCITE/IO/8DO (8 Relay Outputs)
XCITE/IO/4DO (4 Relay Outputs)
XCITE/IO/16DI (16 Digital Inputs)
XCITE/IO/8DI (8 Digital Inputs)
XCITE/IO/8DI/8TI (8 Digital Inputs plus 8 Thermistor Inputs)
XCITE/IO/8AO (8 Analog Outputs)
XCITE/IO/4AO (4 Analog Outputs)
XCITE/IO/8DO/HOA (8 Relay Outputs with Hand, Off, Auto)
XCITE/IO/4DO/HOA (4 Relay Outputs with Hand, Off, Auto)
Actual Type: (characters, status) The type which has actually been read from the I/O bus by the IQ3. This confirms that
the I/O module actually exists on the I/O bus. If the module has been created in SET but is not communicating on the
I/O bus, this parameter will be blank. The actual type will be set to one of the types in the list above (under Configured
Type).
State: (analogue, status) This defines the communication state of the I/O module. It can be set to one of the following:
0 not present - never been there since power up
1 self testing- reported by I/O module - exists briefly after I/O module power up
2 standby - reported by I/O module - exists briefly after I/O module self test
3 operational
4 recoverable fault - reported by I/O module (still communicating)
5 unrecoverable fault - this I/O module was communicating and has now failed to communicate
This parameter is first set up when the IQ3 automatically identifies the hardware I/O module and then whenever the
strategy initiates a communication to the module.
Failed: (digital, output) Set up by the IQ3 as the status of the last communication between the IQ3 and the hardware I/
O module. Set if the State is ‘not present’, ‘recoverable fault’, or ‘unrecoverable fault’. If connected to a module’s digital
input, the input’s details will be shown on the web page. This output is shown as a connective in SET (i.e. inF where
i=I/O module, n=I/O module number, F=Failed).
Firmware version: (characters, status) The firmware version of the I/O module discovered by the IQ3 communication.
Page, x co-ordinate, y co-ordinate: (analogue, constant) These are normal strategy module parameters, but since the
I/O Module is not shown on the strategy page they are not used.
Actual Type - R A Character string blank The type of module as found on the bus. See
STATUS
1 = self testing
2 = standby
3 = operational
4 = recoverable fault
5 = unrecoverable fault
Failed - R F 0 1 0 Status of last communication between IQ3 and
OUTPUT
firmware
The function performed by any knob is determined by the strategy within the controller.
The knob module appears on the strategy page and does not need to be sequenced. Since a knob is always event driven,
its output should never be connected back to its input. SET prohibits this.
17.1 Symbol
A knob is represented on the strategy as a variable analogue node.
Knob 2
K2
0
D
KNOB
Units
0 Pin Level
0 Top of Range
0 Bottom of Range
0 COV Increment
17.2 Web Page
Knob Overview Web Page
Connective
17.5 Range
The knob can only be adjusted over the range defined by the upper and lower adjustment limits.
In SET the value can be adjusted by overwriting the value in the value box, or by dragging the index in the window between
the lower and upper limits.
Parameters that are not available as inputs are normally items that one would not want to adjust from the strategy (e.g.
module type which should be specified in SET and not changed by the running strategy).
17.7 Parameters
17.7.1 Input and Output Parameters
Value: (analogue, source/constant) The current value of the knob. It can either be sourced from a module’s analogue
output or set to a constant value. If connected to a module’s analogue output the output’s details will be shown on the
web page.
Top Range (SET: Top of Range): (analogue, source/constant) This is the maximum value to which the knob can be set.
It can either be sourced from a module’s analogue output or set to a constant value. If connected to a module’s analogue
output the source address will be shown on the web page.
Bottom Range (SET: Bottom of Range): (analogue, source/constant) This is the minimum value to which the knob can
be set.
It can either be sourced from a module’s analogue output or set to a constant value. If connected to an analogue output
the output’s details will be shown on the web page.
Destination: (analogue, output) The value of the module’s output. If connected to a module’s analogue input, the input’s
details will be shown on the web page.
The output is shown as a connective in SET (i.e. KnD where K = Knob, n = knob module number, D = destination).
Units: (characters, constant) The units of the knob’s value (e.g. DegC). This enables units to be displayed on supervisors
alongside the knob’s value and label. For compatibility with BACnet the units should be chosen from the list of BACnet
units given in Appendix 2. If units other than these are used, they will betransmitted over BACnet as ‘no units’. In SET
selecting the BACnet Units button enables the units to be selected from the list.
COV Increment: (analogue, constant) The amount by which the knob value has to change before a BACnet COV
notification message is sent to those subscribers in the List of Subscribers who have sunscribed to this parameter. If
COV Increment is zero, notification is not sent.
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
The knob label can be used as an item attribute for text communications. This is explained for IC Comms in Pt. 2 section
15.4.
Special characters are as follows:-
? * .
Page: (analogue, constant) SET file strategy page number on which module appears.
TYPE
co d e
CONST
web pages. This can be used as an item attribute for
characters text comms and has restricted characters see 17.7.3
above
CONST
output.
Destination - R/W D -1020 +1020 0 The output value. Can be connected to an analogue
input.
User Level R/W R/W P 0 99 0 The level of PIN required to be entered before the
(SET: Pin Level) knob can be adjusted.
Top Range R/W R/W* T -1020 +1020 0 The maximum value to which the knob can be set.
CONST
Bottom range R/W R/W* B -1020 +1020 0 The minimum value to which the knob can be set.
CONST
COV Increment R/W R/W C 0 +1020 0 The amount by which the knob value must change
before a BACnet notification is sent. If zero, there is
no notification.
P age R/W R/W p 0 255 0 Page number containing module in SET file
* This source/constant parameter cannot be changed via the web page if it is set as a source.
2 Timer Applies on and off delays and a minimum on time to a single digital input
3 Readback Checks if two digital inputs follow each other within a grace time of one input changing
4 Counter Counts a pulse type digital input and also calculates its pulse rate
6 Hours Run Counts hours for which a digital input is on, and checks if an interval is exceeded
generic parameters
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
Page: (analogue, constant) SET file strategy page number on which module appears.
Disable Module (SET: ModuleState - Enabled/Disabled): (digital, source/constant) This input will disable the module,
i.e. prevent it from being serviced. Its internal states and output will be maintained at their values prior to disabling. This
input can either be sourced from a digital output, or set to a constant value (0 or 1). If connected to a module’s digital
output the output’s details will be shown on the web page.
Sequence Table: (digital, constant) This is set to sequence table 1 if the module is sequenced (in the sequence table).
It is set to table 0 (zero) if the module is event driven.
Sequence Step: (analogue, constant) The driver module can be either sequence table or event driven. If event driven
the step is set blank in SET, and the parameter does not appear on the web page. For sequence step driven modules this
defines the sequence step in the sequence table (see Pt. 1 section 5.6); the module may be entered into the sequence
table more than once. Counter and Hours Run logic modules should not be multiplexed.
100
Output Override Required
0 E G19
J or
0 F K or
L or D
0 G M
0 H
COMB
E J Comb.
F K Comb.
G L Comb.
H M Comb.
Connective
18.4.4 Function
P R O D U C T
F U N C T IO N S
E
F
G F U N C T IO N J
H A N D
F U N C T IO N K
A N D
D D IG IT A L D E S T IN A T IO N
O R
A D D R E S S
F U N C T IO N L
A N D
F U N C T IO N M
A N D
The logical combination of digital inputs allows four different logical combinations to be made of up to four digital inputs
(E, F, G, H). These logical combinations are designated functions J, K, L, and M.
Each function (J, K, L, M) can AND together any of the inputs (E, F, G, H) or the inverse of the inputs (represented by
the lower case letter, e, f, g, h).
Each of the four logical functions are evaluated and the four resultant terms are summed (logical OR) to create the module
output (i.e. J+K+L+M).
In this way the combination logic module allows the logical AND, NOT AND (NAND), OR, and NOT OR (NOR)
functions to be performed.
The output of the combination logic module at any time is determined entirely by the combination of input signals that
are present at that time. A combinational logic module can be made to produce and output an ON state, only for a
particular pattern or patterns of inputs.
The action of the combinational logic module is described by a boolean expression, which is a short way of showing
the module function. A Trend boolean expression uses the + symbol to represent the OR function, upper case,
(CAPITAL), letters to represent true state and lower case letters to represent the inverse state; letters are written side
by side (as in multiplication) to represent the AND function.
If the function is described as E, then if the bit data at the input is 1, the output will be 1; if, however, e is used, the output
will be zero (i.e. the inverse) when the input is 1.
In the above example, the logic OR function is being performed on inputs E and F. Where, if the state of input E or F is
1, then the module output state will be 1.
In the above example, the logic AND function is being performed on inputs E and F. Where if the states of inputs E and
F are both 1, then the module output state will be 1. If either or both input states are 0 the module output state will be
0.
In the above example the logic NOR function is being performed on inputs E and F. In this case the output is 1 if both
E and F are 0 or conversely the output is 0 if either E or F is 1; this function is E NOR F.
In the above example the logic NAND function is being performed on inputs E and F. In this case the output is 1 if either
E or F are 0 or conversely the output is 0 if both E and F are 1; this function is E NAND F.
Manual override on
OR Demand > 20% AND Building Occupied
OR Demand > 10% AND Building Non-occupied.
Manual Override ON =E
Demand > 20% =F
Building Occupied =G
Demand > 10% =H
E+FG+Hg
This is done in SET by selecting the inputs used by each function in the dialogue box:
0 E G3
J or
0 F K or
L or D
0 G M
0 H
logical combination functions
COMB
E J Comb.
FG K Comb.
gH L Comb.
M Comb.
To check that the function works correctly, the rigorous approach is to create a truth table.
For example, we wish to make a pulse generator, i.e. we want the output to change from 0 to 1 and back again every time
we service the module. We can have an enable input which will enable the pulse output if ON and disable it if OFF.
E G 1
D
E N A B L E
F C O M B
E F D
1 0 0 0
2 0 1 1
3 1 0 0
4 1 1 0
The left hand two columns show all possible combinations of inputs. This is best done by counting up in binary to the
number of binary digits available as inputs.
The right hand column D, shows the output for each combination of inputs.
Thus, in row 1, the output is at 0 and the module is disabled so the output stays at 0. In row two the module is now enabled
so we want the count to change i.e. D is 1. In row three the output is 1, but the module is disabled so we want the output
to be 0. In row four the output is at 1, the module is enabled so the output must become 0.
The next step is to write down the combinations needed for the output to be 1 and OR them together. There is only one
such output in this case for row 2.
D = F AND NOT E
= Fe
*Input E (SET: Source E): (digital, source/constant) One of the inputs used in the logical combination. It can either be
sourced from a module’s digital output, or set to a constant value. If connected to a module’s digital output, the output’s
details will be shown on the web page.
*Input F (SET: Source F): (digital, source/constant) One of the inputs used in the logical combination. It can either be
sourced from a module’s digital output, or set to a constant value. If connected to a module’s digital output, the output’s
details will be shown on the web page.
*Input G (SET: Source G): (digital, source/constant) One of the inputs used in the logical combination. It can either be
sourced from a module’s digital output, or set to a constant value. If connected to a module’s digital output, the output’s
details will be shown on the web page.
*Input H (SET: Source H): (digital, source/constant) One of the inputs used in the logical combination. It can either be
sourced from a module’s digital output, or set to a constant value. If connected to a module’s digital output, the output’s
details will be shown on the web page.
*Note that these inputs are set by default to zero, but are not used in the logical combination unless they are entered into
one of the functions (J, K, L, M).
Combination K (SET: K=): (characters, constant) One of the logical combinations OR’d into the result.
Combination L (SET: L=): (characters, constant) One of the logical combinations OR’d into the result.
Combination M (SET: M=): (characters, constant) One of the logical combinations OR’d into the result.
18.5.1 Symbol
G1
I1S S D
TIMER
0 On Delay
3600 Minimum On
0 Off Delay
Connective
Minimum On Time: This timer function switches the module output ON for at least the minimum on time. Only after
the time has elapsed, will the module output switch OFF if the input state has changed to OFF, otherwise the module
output remains ON until the input switches OFF. If the on delay is also set up, the minimum on time is applied after the
on delay has expired.
Off Delay: This timer function delays the module output from switching OFF, after the input has switched OFF, for the
duration of the off delay. The off delay only applies if the input remains in the OFF state (if the input switches back on
during the off delay, the off delay is reset to zero, so if it then switches back off the off delay restarts from zero). If the
minimum on time is operating the off delay is applied after the minimum on time has expired.
The following shows the timing diagrams for different timer functions where t represents time and t total is the total time.
t
example input S
duration of output D is t
N t-N
output D with on
delay (N) duration of output D is t-N
O N
D E L A Y
M IN IM U M
O N T IM E
O F F
D E L A Y
M F
output D with minimum duration of output D is
on time (M), and off max(M, t)+F
delay (F)
N M F
output D with on delay duration of output D is
(N), minimum on time max(M, t-N)+F
(M), and off delay (F)
The time range for each of these timer functions (on delay, minimum on time, off delay) is 0 to 32767 seconds (about
9 hours). The maximum output time ON is thus 65534 seconds (assuming t<M, or t-N<M) and is achieved by the M+F
or N+M+F combinations shown above.
Source: (digital, source/constant) The input being subjected to the timer functions. It can either be sourced from a
module’s digital output, or set to a constant value (0 or 1). If connected to a module’s digital output, the output’s details
will be shown on the web page.
On Delay (seconds): (analogue, source/constant)The time delay between the input switching ON and the output
switching ON. It can either be sourced from a module’s analogue output, or set to a constant value. If connected to an
analogue output, the source address will be shown on the web page.
Minimum On (seconds): (analogue, source/constant)The minimum time for which the output will be held ON. It can either
be sourced from a module’s analogue output, or set to a constant value. If connected to a module’s analogue output,
the output’s details will be shown on the web page.
Off Delay (seconds): (analogue, source/constant) The time delay between the input switching OFF and the output
switching OFF. If the minimum on time is operating, the off delay will not start until the minimum on time has expired.
It can either be sourced from a module’s analogue output, or set to a constant value. If connected to a module’s analogue
output, the output’s details will be shown on the web page.
18.6.1 Symbol
29
readback 2 0 H
READBK
20 Grace Time
Connective
18.6.4 Function
The logic readback module has two sets of inputs, i.e. two equipment drives and two readback inputs. Normally, only
one equipment drive and one readback input are used. If the second drive and readback are not used they should not
be connected in SET.
Considering one pair of inputs, they are compared when the module is serviced and if either of the two inputs (i.e. drive
and readback) differ then the grace timer is started and will be reset back to zero if the two inputs become the same. If
the two inputs remain different for the whole of the grace time, then the module output will be set.
The output is normally connected to the readback alarm input of the driver module being monitored.
The effect of this is that the HVAC equipment being controlled and monitored has the grace time in which to switch on
or off, without producing an alarm, and also if the equipment switches into the wrong state at any time, it must be in that
faulty condition for the whole grace time before an alarm is generated. This will filter out short term differences.
O U T P U T
S O U R C E
R E A D B A C K
T IM E R
S T A R T S T A R T S T A R T S T A R T
R E S E T R E S E T R E S E T R E S E T
In the above diagram the grace timer is started when the inputs differ and reset when the inputs are the same. If the period
from start to reset ever extends beyond the grace time then the module output will be set, which will cause a driver readback
alarm to be generated if the output is connected to a driver readback input.
If both pairs of inputs are used the two pairs work independently of each other, each pair having separate timers.
IQ3 operation
A
Timer 1
Ab + aB grace time
B
C
+
Timer 2
Cd + cD grace time
D
The logic combination Ab + aB (A AND NOT B OR B AND NOT A) indicates that it will produce an output state 1
when the inputs differ. This will trigger timer 1 which will produce an output state 1 when the grace time has expired.
If the inputs A and B become the same state at any time the timer will be reset and the timer output will produce a zero
state.
The same logic applies to the second pair of inputs C and D using their own timer 2.
The outputs from the two timers are OR’d to produce the module’s output (Destination).
A
IQ2 operation
B Ab + aB
Timer
C
+ grace time
D Cd + cD not retriggerable
[The IQ3 readback module operation differs slightly from IQ1 and IQ2 readback modules. The IQ1 and IQ2 readback
modules have only one timer and if one pair of inputs trigger the timer, then if the second pair come to differ the timer
will continue to count from its current value (i.e. it will not retrigger). The timer will only be reset and the output cleared
when both pairs of inputs no longer differ.]
The strategy diagram below shows the readback logic module being used to generate the readback alarm for a driver
module. This is described fully in Pt. 2 section 13.2.5.1.
26
27
Sensor 3
0 A L2
S3 V
28
0 m S3V P Driver 11
0 c
EXTERNAL 0 O D11 L 11 Pump
m0
0 Override Enable A
nul U 0
0 Override Value D L2D S
0 L R
Alarm
1 S LOOP BINARY HYST M
Enabled Maint. Int. Enable
Enabled Readback Enable
0 Maint. Int. Alarm
G13D Readback Alarm
0 Readback Delay
0 Override Enable
0 Override Value
29
D11l E G13
Digital Input 6
0 F
I6 S D
0 m I6S G
1 c
EXTERNAL 0 H
0 Override Enable READBK
0 Override Value 20 Grace Time
Source E (SET: Input E): (digital, source/constant) The first drive to be compared with its readback (input G). It can either
be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s digital output,
the output’s details will be shown on the web page.
Source F (SET: Input F): (digital, source/constant) The second drive to be compared with its readback (input H). It can
either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s digital
output, the output’s details will be shown on the web page.
Source G (SET: Input G): (digital, source/constant) The first readback input to be compared with its corresponding drive
(input E). It can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a
module’s digital output, the output’s details will be shown on the web page.
Source H (SET: Input H): (digital, source/constant) The second readback input to be compared with its corresponding
drive (input F). It can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected
to a module’s digital output, the output’s details will be shown on the web page.
Grace Time: (digital, source/constant) The time for which the difference in inputs must be present before the output
is set ON. It can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a
module’s digital output, the output’s details will be shown on the web page.
18.7.1 Symbol
36
G16
input to be counted R
rate
D14l S
0 999
A
reset M
cumulative output
COUNTER
5 Reschedule Time
1 Scale Factor
Connectives
18.7.4 Function
The counter will count the pulses on the input and multiply this count by the scaling factor to produce the cumulative
output.
The counter module also produces a rate output which is calculated by the change in count over the reschedule time.
If the input is sourced from an external digital input module or a driver output, then the counter module can access the
source module’s internal count; see section 18.7.4 below.
The counter module may be either sequence table driven or event driven.
If the module is sequence table driven, and the input is from an internal digital output (rather than from an external digital
input module), then it will only be monitored when the module is sequenced. In order to be monitored it must be ON
at least for the period between sequencing thus the maximum frequency is:
e.g. if the module is entered twice in the sequence table, maximum frequency is 2/2 , i.e. 1 pulse per second.
The scaling factor defines the value of each pulse i.e. it scales the counter and defines how much is added to the
cumulative count for each pulse counted. This can be a decimal number either less than or greater than one.
The reschedule time defines the period over which the rate is measured and the count is increased. The rate is defined
as the change in cumulative count over the reschedule time (i.e. it takes into account the scaling factor). At the end of
the reschedule period, the rate output is changed and the rate value (i.e. change in cumulative count) is added to the
cumulative output.
The reset bit resets the count to zero. If the reset bit is at a 1 state when the module is serviced, whether or not the
reschedule period has just ended, the cumulative output is set to zero.
If this occurs in the middle of a reschedule period, the change in count will be added to the cumulative output at the end
of the reschedule period. The effect will be that the cumulative count goes to zero when the module is serviced, and the
cumulative count shows the change in count since the last reschedule point at the end of the reschedule period. The rate
thus remains unaffected.
C u m u la tiv e
C o u n t
0
r e s c h e d u le tim e
p e r io d
r e s e t p o in t
Thus in general at the end of a reschedule period the cumulative output will not be zero even if the reset bit is set at that
time, because the value of the change in count since the last reschedule time is not zero. This ensures that pulses counted
during a reset period are not lost, so that the total count between resets would agree with the count of another device
(say an electricity meter).
5 6
4
kW
Pulse meter 4 E F4 S3 Sensor 3
I5 G2 V
0 m S R G2R G D F4D S S3V S P1
I5S S PLOT
0 c INTERNAL
EXTERNAL 999 1 F 15 Min Period
T1t A MULTIPLY kW Units
M 1000 Records
Hours Run
Starts D=G*E*F
COUNTER
900 Reschedule Time
0.48 Scale Factor
T1t
24 hour pulse
From Page 0
7
kWh
S4 Sensor 4
V
G2M S S4V S P2
INTERNAL PLOT
24 Hours Period
kWh Units
1000 Records
In the above example, the pulses from an electricity meter are being counted and their rate and cumulative count being
calculated.
The scaling factor F is 0.48 as each pulse is worth 0.48 kWh. The cumulative count will then be read in kWh and is reset
at midnight each day. The internal sensor S9 is logged at midnight each day to give a 96 day log.
1) The longer the time period, the more pulses are counted and the less the effect of, failure to count one pulse in
a period but counting it in the next instead, has on the value.
2) The shorter the time period, the more the rate can follow the actual fluctuations of the pulses. With a long period
of 1 hour, the rate is calculated over that period and will only change once per hour.
The selection of rate depends very much on the frequency of the input pulse.
In this example the final rate is to be in kW i.e. kWh/h. In order to do this the counter's reschedule time would be set
to one hour, (change in kWh count per hour), but in order to be able to see fluctuations within an hour the reschedule
time is set to 15 minutes.
This gives a rate of kWh/15 minutes. To achieve a rate of kW, the rate output of the counter is multiplied by 4 by the
function module F1. This is then monitored by S3 which is logged at 15 minute intervals, so that the daily rate graph
will show fluctuations every 15 minutes.
18.7.3 Function (continued)
The rate and cumulative count calculations are performed to a defined number of significant figures ( as with any
computer calculation), hence rounding errors can occur with very small numbers. If accuracy is of prime importance
there are several recommended procedures that will improve the situation.
a) Use a scaling factor of 1 and multiply and divide the cumulative and rate figures in subsequently connected
function modules. This stops rounding errors of many very small numbers being compounded.
b) If a scaling factor of less than 1 is to be used, then rounding errors will occur. To minimise this effect make the
reschedule time as large as possible. This means larger numbers are divided and less rounding errors are
compounded.
c) Try to reset the counter daily and then log the counts in an internal sensor for use with Supervisor Data Analysis
software etc. This stops very large numbers being generated and small numbers being added to large numbers.
direct transfer
If a counter logic module is connected directly to an external digital input as shown above, the digital input module number
of starts is transferred directly to the counter module cumulative output without scaling when the module is serviced.
If the counter module is reset this will reset both the counter module cumulative output and the digital input number of
starts. Similarly if the digital input number of starts is changed, this will be copied to the counter module cumulative
output. 35
Driver 14
D14 L 0
m0
A 0
0 S
R
Alarm M
DIGITAL
Disabled Invert
Hours Run
Starts
36
G16
D14l R
S
999
direct transfer
0 A
M
COUNTER
5 Reschedule Time
1 Scale Factor
If a counter logic module is connected directly to a driver output channel (excluding analogue or raise/lower drivers)
as shown above, the driver number of starts is transferred directly to the counter module cumulative output without
scaling when the module is serviced.
If the counter module is reset this will reset both the counter module cumulative output and the driver number of starts.
Similarly if the driver number of starts is changed, this will be copied to the counter module cumulative output.
These special relationships exist mainly for compatibility with IQ2 series controllers although they also enable the
number of starts to be reset, and an input rate to be generated.
Rate: (analogue, output) The value of the rate, being the change in cumulative count over the reschedule period. If
connected to a module’s analogue input the input’s details will be shown on the web page.
The output is shown as a connective in SET (GnR where G=logic module, n=logic module number, R=Rate).
Source: (digital, source/constant) The digital input being counted. It can either be sourced from a module’s digital
output, or set to a constant value (0 or 1). If connected to a module’s digital output, the output’s details will be shown
on the web page.
Reset: (digital, source/constant) The digital input used to reset the count. It can either be sourced from a module’s digital
output, or set to a constant value (0 or 1). If connected to a module’s digital output, the output’s details will be shown
on the web page.
Scale Factor: (analogue, source/constant) An analogue input used to define the value of each pulse. It can either be
sourced from a module’s analogue output, or set to a constant value. If connected to a module’s analogue output, the
output’s details will be shown on the web page.
18.7.6.2 Others
Reschedule Time: (analogue, source/constant) An analogue input used to define the period over which the rate is
calculated and the cumulative output is increased. It can either be sourced from a module’s analogue output, or set to
a constant value. If connected to a module’s analogue output, the output’s details will be shown on the web page.
18.8.1 Symbol
131
G25
0 E
0 D
G
DELAY
0 Grace Time
Connective
18.8.4 Function
In IQ1 and IQ2 the delay logic module is normally used with input E connected to an alarm condition, input G connected
to the particular alarm acknowledge digital node, and with output D connected to the strategy module’s alarm input.
131
G25
alarm condition 0 E
0 G
D alarm input to strategy
alarm acknowledge module
DELAY
0 Grace Time
It cannot be used in this way in IQ3 because the IQ3 does not have alarm acknowledge bits.
In IQ3 it can be used in a similar way to the readback logic module. The pair of inputs E and G operate like one of the
pairs in the readback logic module - see 18.6.4 above.
Source E (SET: Input E): (digital, source/constant) The first input which is compared with the second input (input G).
It can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s
digital output, the output’s details will be shown on the web page.
Source G (SET: Input G): (digital, source/constant) The second input which is compared with the first input (input E).
It can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s
digital output, the output’s details will be shown on the web page.
Grace Time: (analogue, source/constant) The time for which the difference in inputs must be present before the output
is set ON. It can either be sourced from a module’s analogue output, or set to a constant value. If connected to a module’s
analogue output, the output’s details will be shown on the web page.
The module also checks if the hours run has exceeded the interval limit and will set the interval limit alarm digital output
to a 1 when the limit is exceeded.
The hours run logic module should always use the sequence table, and not be event driven (see Pt. 1 section 5.6).
18.9.1 Symbol
34
Connectives
The hours run is incremented and checked to see if the interval has been exceeded each time the module is serviced.
When the reset input goes to a 1 state, the hours run output is set to zero and since the hours run of zero cannot now
exceed the interval, this also sets the interval exceeded output to zero.
If the input is sourced from an external digital input module or a driver output, then the hours run module can access
the source module’s internal count; see section 18.9.4 below.
1) Facilitate strategies which require the usage of HVAC equipment (e.g. pumps, boilers) to be cycled upon the basis
of hours run.
direct transfer
If an hours run logic module is connected directly to an external digital input as shown above, the digital input module
hours run is transferred directly to the hours run module hours run output without scaling when the module is serviced.
If the hours run module is reset this will reset both the hours run module hours run output and the digital input hours
run. Similarly if the digital input hours run is changed, this will be copied to the hours run module hours run output.
30
Driver 13
D13 L 0
m0
A 0
0 S
R
Alarm
DIGITAL M
Disabled Invert
Hours Run
Starts
34
D13l S
G15 direct transfer
O
0 I
0 N
A
HOURS RUN
If an hours run module is connected directly to a driver output channel (excluding analogue and raise/lower drivers) as
shown above, the driver hours run is transferred directly to the hours run module hours run output without scaling when
the module is serviced.
If the hours run module is reset this will reset both the hours run module hours run output and the driver hours run. Similarly
if the driver hours run is changed, this will be copied to the hours run module hours run output.
These special relationships exist mainly for compatibility with IQ2 series controllers although they also enable the hours
run to be reset, and the interval exceeded to be generated.
Hours Run: (analogue, status) (Web page only). Same value as Hours Run Output.
Interval Limit Alarm: (digital, output) The state of the interval exceeded output; if the interval is exceeded the output
will change to a 1 state. If connected to a module’s digital input the input’s details will be shown on the web page.
The output is shown as a connective in SET (GnN where G=logic module, n=logic module number, N=Interval exceeded
output).
Source: (digital, source/constant) The digital input whose hours run is being accumulated. It can either be sourced from
a module’s digital output, or set to a constant status (0 or 1). If connected to a module’s digital output, the output’s details
will be shown on the web page.
Interval: (analogue, source/constant) An analogue input used to check if it has been exceeded by the hours run. It can
either be sourced from a module’s analogue output, or set to a constant value. If connected to a module’s analogue output,
the output’s details will be shown on the web page.
Reset: (digital, source/constant) The digital input used to reset the hours run (and also the internal limit alarm output
indirectly). It can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to
a module’s digital output, the output’s details will be shown on the web page.
It is basically for compatibility with IQ2 strategies and has very little application in IQ3s
0 S
L
M
FAN OUT
Disabled Invert N
O
18.10.2 SET Dialogue Box
Connectives
18.10.4 Function
The state of the input is passed to the output bits when the module is serviced.
There is an invert parameter which allows the inverse state of the input to be passed to all the outputs.
In IQ2 this enabled a one to 6 connection to be made between nodes in the digital array without using 6 combinational
logic modules.
For example using an alarm inhibit condition to disable alarms in up to 6 modules to prevent consequential alarms.
J 4 1 5 ,1 D H W . F lo w T e m p . L o w A la r m E n a b le
L P H W B o ile r s L o c k o u t
G 1 K 4 1 1 ,1 O ffic e A H U . S u p p ly T e m p . L o w A la r m E n a b le
L 4 0 9 ,1 T o ile t A H U . S u p p ly T e m p . L o w A la r m E n a b le
S 1 M 4 1 6 ,1 V T C ir c u it. F lo w T e m p . L o w A la r m E n a b le
N 0 ,0
F A N O 0 ,0
In IQ3 this could be done using one combinational logic module to invert the lockout, and then connecting this to the
enable inputs of the various modules that require inhibiting.
Invert: (digital, source/constant) The state of the invert input; if set to 1 it will cause all 6 outputs to be the inverse of
the source input state, otherwise they will follow the source input state. It can either be sourced from a module’s digital
output, or set to a constant value (0 or 1). If connected to a module’s digital output, the output’s details will be shown
on the web page.
Outputs J to O: (digital, output) The state of the outputs J to O which are dictated by the state of the source and invert
inputs. If these outputs are connected to modules’ digital inputs their inputs’ details will be shown on the web page.
These outputs are shown as a connectives in SET (GnJ to GnO where G=logic module, n=logic module number, J to
O=Output J to output O).
18.11 D to A (type 8)
The D to A module converts up to 8 digital bits into one analogue value.
18.11.1 Symbol
123
I12S a G23
0 b
0 c
0 d
D
0 e
0 f
0 g
W3D h
D TO A
Connective
18.11.4 Function
Each input bit has a binary weighting so that the complete set of 8 digital inputs is treated as a binary number (a=Bit
0, through to h= Bit 7), and the output D is the analogue value of this binary number. This gives a unique analogue value
for every input combination.
where:
output = 1x(a) + 2x(b) + 4x(c) + 8x(d) + 16x(e) + 32x(f) + 64x(g) + 128x(h)
Thus if inputs a, d, and f are set to 1 and the others set to zero,
a + d+ f = Bit 0 + Bit 3 + Bit 5 = 1 + 8 + 32 = 41
i.e binary 00101001 = decimal 41
This module could be used to generate a single analogue value for display on a supervisor page which will give an
encoded value to report the HVAC equipment status.
133
Heating 0 a G27
Cooling 0 b 134
Boost 0 c Sensor 16
S16
0 d V
D G27D S
0 e INTERNAL
0 f
0 g
0 h
D TO A
This example shows the three states, heating, cooling and boost which have the values1, 2, 4 respectively. The output
is monitored by internal sensor S16 which can be logged. An example graph is shown below.
It could also be used to encode a number of digital nodes into a single analogue value to be sent to another controller
by a single IC Communication. The digital bits can then be decoded in the other controller using an A to D function module.
In IQ3 this type of application is used to encode digital bits for a digital byte Data To type IC Comms as shown in the
example below (see Pt. 2 section 15.9). If this IC Comms is being received by an IQ3 it must have a digital byte module
created to receive the message.
Bits 0 to 7 (SET: Inputs a to h): (digital, source/constant) The state of the digital input (0 or 1); each input has a weighting
in the D to A logic module’s analogue output (Destination, see above). Each input can be sourced from a module’s digital
output, or set to a consant value (0 or 1). If connected to a module’s digital output, the output’s details will be shown
on the web page.
Input a Bit 0 weighting: 1
Input b Bit 1 weighting: 2
Input c Bit 2 weighting: 4
Input d Bit 3 weighting: 8
Input e Bit 4 weighting: 16
Input f Bit 5 weighting: 32
Input g Bit 6 weighting: 64
Input h Bit 7 weighting: 128
TYPE
comms
SET Web Low High
co d e
page
Generic Logic Module Controller Parameters
CONST
Label R/W R/W $ 0 30 blank Label of module.
characters
Disable Module R/W R/W* ~ 0 1 0 State of disable input. Can be connected to
SOURCE/
CONST
(SET: Module State - a digital output.
Enabled/Disabled))
Sequence Step R/W R @ 0 500 specifically set The sequence step at which the driver is
CONST
up by SET serviced. If left blank in SET the module is
event driven. If event driven this parameter
is not shown on web page.
Sequence Table - R # 0 1 0 The sequence table used by this module. If
Combination J R/W R/W J Trend boolean of blank Logical combination or'd into output
CONST CONST CONST CONST
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
Parameter comms Default
Web co d e
SET Low High
page
Timer (type 2) Logic Module Controller Parameters
OUTPUT
Destination R/W R/W D 0 1 0 The state of the module output. Can be
connected to a digital input.
Off Delay R/W R/W* F 0 32767 0 Value of delay between input switching
off and output switching off. Can be
connected to an analogue output.
seconds
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
Parameter comms Default
Web co d e
SET Low High
page
Readback (type 3) Logic Module Controller Parameters (continued)
SOURCE/CONST
Grace Time R/W R/W* T 0 32767 0 Value of grace time, time for which
inputs can be different before output
seconds switches on. Can be connected to an
analogue output.
Counter (type 4) Logic Module Controller Parameters
Cumulative Output R/W R/W M -1020 +1020 0 The value of the output count. Can be
OUTPUT
connected to an analogue input.
-1020 +1020
OUTPUT
Rate R/W R/W R 0 The value of the calcuated rate. Can be
connected to an analogue input.
Scale Factor R/W R/W* F -1020 +1020 1 The value of each input pulse. Can be
connected to an analogue output.
Reschedule Time R/W R/W T 0 1275 5 Value of time between calculating rate
CONST
Grace Time R/W R/W* A 0 32767 0 Value of the grace time for which the
inputs can be different before the output
seconds switches on. Can be connected to an
analogue output.
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Hours Run Output R/W R/W O -1020 +1020 0 The value of hours run ouput. Can be
OUTPUT
connected to an analogue input.
STATUS
OUTPUT
Interval Limit Alarm R/W R/W N 0 1 0 The state of the interval exceeded output
(1=interval exceeded). Can be connected
to a digital input.
Interval R/W R/W* I -1020 +1020 0 The value of the interval. Can be connected
to an analogue output.
Source R/W R/W* S 0 1 0 The state of source input being fanned out.
Can be connected to a digital output.
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
Parameter comms Default
Web co d e
SET Low High
page
D to A (type 8) Logic Module Controller Parameters
Destination R/W R/W D -1020 +1020 0 Value of output. Can be connected to an
OUTPUT
analogue input.
* This source/constant parameter cannot be changed via the web page if it is set as a source.
The control loop compares the measured value, (input from a sensor or combination of sensors) with the current setpoint
value, (desired value). The control loop is capable of providing 3 types of control, proportional, proportional and integral
control (2-term), and proportional, integral and derivative control (3-term).
The loop module appears on the strategy page and must be sequence table driven, it cannot be event driven. It must
not be multiplexed.
19.1 Symbol 4
Manual Select 0 A L1
Process Variable 0 P
Occupied Setpoint 0 O
Unoccupied Setpoint 0 U
D
Manual Level 0 L
The Setpoint Select input selects either the Occupied or Unoccupied Setpoint. The loop compares the Process Variable
(measured value) with the selected setpoint and generates the new output using the proportional Gain, Integral Time,
Derivative Time and the previous output value. The Manual Select (Manual Address) input will override the output to
the Manual Level.
‘In Alarm’
parameter
Connectives
Process Variable
Setpoint Select
Loop
Unoccupied Algorithm
Output
Setpoint
Occupied Manual Override
Setpoint
SP Select
Manual Level
Error
Deviation
Setpoint Deviation
This diagram shows the basic operation of the loop module. The Setpoint Select selects the required setpoint from either
Unoccupied Setpoint or Occupied Setpoint . The loop algorithm compares the process variable with the selected setpoint
and generates the loop output. The Manual Select input can override the loop output to the Manual Level.
If the error between the Process Variable and the selected setpoint is greater than the Setpoint Deviation level the alarm
condition is passed to the Setpoint Deviation Alarm sub-module. If it exists longer than the Delay time the SP Dev Alarm
State output is generated. If the alarm is Enabled the alarm is reported and the In Alarm output is set non zero.
If the Process Variable input has either a Read or Outside Limits alarm status accompanying the value, the alarm
condition is passed to the Process Variable Fail Alarm sub-module. If it exists longer than the Delay time the PV Fail Alarm
State output is generated. If the alarm is Enabled the alarm is reported and the In Alarm output is set non zero. Note that
the loop module does not have a separate Clear Enable parameter unlike the digital input, driver, and sensor modules,
so that both the alarm and the clear alarm are enabled by the Enabled parameter.
HOT WATER
RADIATOR
In the above diagram, the sensor is measuring the temperature of an air space. The output of the sensor will be a signal
which varies in a defined way with the temperature.
The controller will decide from the temperature measurement whether more, less, or sufficient heat is being supplied and
either raise or lower the valve actuator by energising the relevant relay on the output side.
The valve will then move, the hot water flow will change and then so will the room temperature via the radiator.
20
19 21
deg C
strategy diagram
18 22
RADIATOR
The process by which the controller decides what the output level should be for a given input is described by the strategy
diagram as shown above. In the strategy diagram the software modules are represented by fixed shapes (see Pt. 2 sections
5.2 to 5.6).
In the above strategy the signal from the sensor is converted into a number which the sensor module will scale into
degrees centigrade. The sensor module also checks whether the sensor reading is within alarm limits. The value from
the sensor is the loop process variable. The loop compares the process variable with the required level or setpoint (O).
The setpoint is the required room temperature in deg C. In the general case the process variable and the setpoint are
in the same engineering units as the controlled variable.
The difference between the process variable and the setpoint is known as the error. In this example the error is the
setpoint minus the process variable.
Error = setpoint (O) - Process variable
E = O-P
If the process variable temperature is below the setpoint, a heating loop such as this will produce an output greater than
zero. The loop output is always measured in percent as this is a general ratio term which can be applied to any units being
measured or controlled.
Generally the loop output is a demand (here a heating demand), and 0% requires zero heating whereas 100% requires
maximum heating. In this range 0-100% various items of HVAC equipment may be sequenced i.e fans on at 20%, a
damper from 30% to 60%, and an electric heater on at 90%.
In this example, however, we are controlling a valve so that 0% means valve closed, 100% means valve fully open and
any intermediate percentage level corresponds to a valve position.
Since the temperature is below setpoint our loop will have some output, say 30% which will be passed to the driver
module. In this case the Raise/Lower driver module used knows the valve position. If the valve is positioned at 20% then
it needs to raise the valve position by 10%. This means it will pulse the raise line for 10% of the full drive time (see Pt.
2 section 13.6).
The valve will then be 30% open, more water will flow through the pipe, the radiator will emit more heat, and the air
space temperature will rise.
When the temperature sensor is next monitored by the loop module it may have reduced the error, so the loop output
may fall, the valve will close a bit and reduce the rate of heating.
This will produce a continual process of measure, calculate, output, change process, measure, calculate etc. This is a
closed loop. The Loop Module is the prime module in controlling the process variable, in this case the room temperature.
If the occupied temperature setpoint (O) were 20 deg C and the unoccupied setpoint (U) were 15 deg C, this could be
called Night Setback. If the unoccupied setpoint were 5 deg C it could be called Frost Protect. Sometimes this operation
is called Temperature Override but this implies the heating comes on at 100% whereas with the Trend loop, the heating
will come on at the level required.
Setpoint Select is a digital input which switches between setpoints. When set, that is 1, the occupied setpoint is selected.
Setpoint Select is usually derived from the optimum start/stop module. However, this signal may be derived from other
IQ logic; this facility to change the control setpoint dependent on other conditions is very powerful.
If the Unoccupied Setpoint is set to ‘not used’ in SET, the loop is turned off during non occupation: the loop output is
set to zero, the integal and derivative parts are also set to zero.
O F F O F F
0 % 0 %
P R O C E S S
V A R IA B L E
S E T P O IN T T IM E
O N O N
1 0 0 % 1 0 0 %
P R O C E S S P R O P O R T IO N A L
V A R IA B L E C O N T R O L
T IM E
S E T P O IN T
O U T P U T C O N T IN U A L L Y V A R IE S
T O R E D U C E E R R O R
For proportional control, the loop output is proportional to the difference between the setpoint and the measured value.
This difference is known as the error:
As the measured value increases towards the setpoint value, the error decreases and the loop output is reduced in
proportion to the error. Conversely, as the measured value decreases away from the setpoint value, the error increases
and the loop output is increased in proportion to the error.
Since the loop output is not allowed to go negative, the loop output stays at zero for negative errors.
The reason that the process variable overshoots the setpoint is that having selected zero output level, it takes some time
for the radiator (say) to cool down. During this time the room temperature may raise well above setpoint.
The loop output is not allowed to go above 100%, so once this is reached any further increase in error will have no effect
on the output.
Thus, the loop has a defined output band called the proportional band over which the output is proportional to the error.
When the measured value equals the setpoint, the loop output will be zero. As the error increases, the output will increase
linearly until the output reaches 100 percent which is at the end of the proportional band where the output will remain
constant until the error decreases. The relationship between error and loop output is known as Gain (G).
The maximum output will be reached when the error reaches 100/10 i.e. 10 deg C. Thus, the proportional band runs from
0 deg C error to 10 deg C error. The proportional band is thus 10 deg C and in general the proportional band can be
calculated from :-
9 0 G A IN 1 0
8 0
7 0
6 0
5 0
4 0 G A IN 5
3 0
2 0
G A IN 2
1 0
E R R O R
1 2 3 4 5 6 7 8 9 1 0
N O T E
E R R O R = S E T P O IN T -M E A S U R E D V A L U E
O U T P U T = E R R O R x G A IN
Because,
1) The loop output cannot go negative.
2) The loop output cannot go above 100%.
3) Loop output = G x (O - P) within range 0 -100%,
the loop gain must be set negative so that the loop output becomes positive for a negative error. So for a cooling loop
the gain is set negative.
T E M P
s .p .
T IM E
The temperature response is a very slow rise which drifts up to a steady level well below the setpoint (overdamped).
T IM E
The temperature now rises rapidly, overheats and falls below the setpoint. It then rises again to a level which is 1/4 the
height of the first peak above the final level. This is called 1/4 wave damping.
If the gain is further increased, as it increases the overshoot increases, more peaks appear and their magnitude increases
(Damped Oscillation sub-critical) until a point is reached where the output oscillates about the setpoint.
T E M P
s .p .
T IM E
When each peak is the same height as the previous; the critical stability limit has been reached. If the gain is further
increased, the succeeding peaks will increase (super-critical) until the loop output swings between 0% and 100%.
Optimum gain selection can be found by the methods outlined in loop tuning section 19.11 below.
It will be noticed that even the optimum gain produces a final steady level that is below the setpoint. This is generally
due to some heat input being required to maintain the building at temperature, and the proportional control settling with
a steady state error (or offset) where heat input is equal to heat loss. If the heat loss changes, the offset will also change.
To overcome this, an integral term is added to the proportional output to form a proportional and integral control (PI)
loop.
19.7.3 Example
If the building requires 20% of its output to keep the room at the temperature of 20 deg C on a particular day, then with
a gain of 10, the error will be given by:-
T E M P
O F F S E T
s .p .
T IM E
T E M P
s .p .
T IM E
The integral term, integrates (accumulates) the error over a time period and adds this accumulated sum to the loop output.
The integral time constant is defined as the time for which the loop output would have added to it an amount equal to
the product of the error and the proportional gain. Therefore, the shorter the integral time, the greater the integral action,
and the longer the integral time, the smaller the integral action. The integral time constant is expressed in minutes and
for a loop with unit gain and unit error, the output will change by one unit (i.e. gain x error) over the integral time period.
The integral term can be seen in configuration mode and is added as above if the integral time (I) is non-zero.
Just as increasing the gain produces instability, so does decreasing the integral time constant (increasing integral action)
and selecting the correct integral time is critical. (See loop tuning section 19.11 below).
If the integral time constant is non-zero, every time the loop is processed an amount is added to the output which is a
fraction of the level which would be added over the integral time, defined by the ratio of the reschedule time to the integral
time.
For example:-
if error E = 2 deg C
gain G = 20
reschedule time R = 1 min
integral time I = 10 mins
Using the example above for a fixed error of 2 deg C for 1 minute
To achieve optimum control the loop module reschedule time should generally be less than or equal to the plant response
time divided by 10. The plant response is normally several minutes, whereas loop reschedule time is in seconds
(minimum 1 s).
The sequence cycle time is also 1 s, so if the reschedule time is set to its minimum of 1 s, the loop output will be
recalculated every sequence table cycle.
The derivative term is proportional to the rate of change of the error and gives an output if the error is building up rapidly.
It similarly reduces the output if the error is falling rapidly. The derivative term is predictive looking at what might
happen, the integral looks at what has happened, and the proportional terms looks at what is happening. The derivative
term responds immediately to a change in process variable whereas both integral and proportional term require that an
error builds up.
As the process variable (Pv) starts to fall, its initial rate of change is high so the derivative will rise to a maximum, then
as the Pv rate of fall reduces, the derivative will start to drop until, when the Pv is steady again, the derivative is zero.
P V
T IM E
D E R IV A T IV E
The derivative term is shown subtracted because it is calculated from the rate of change of the process variable not the
rate of change of the error. It can be seen on the web page and is subtracted as above if the derivative time constant (T)
is non-zero.
Notice the bigger the derivative time constant, the bigger the derivative effect (i.e. unlike integral time constant).
The derivative used in the IQ is filtered by taking the average of the current value and last value.
The selection of optimum derivative time constant is also covered in the section 19.11 below.
The Loop Tuner Applet in SET is able to tune most loops. It will disable the loop and drive the output directly to observe the
system response before suggesting the values of parameters required. The following describes manual methods that may be
used if the Loop Tuner Applet proves unsatisfactory.
The rule of thumb of Ziegler and Nichols is by far the simplest procedure for such purposes, although it may give an
excess of overshoot. There are two methods, one is based on the step-input response pattern of a process and the other
utilises information obtained at the stability limit of a process under proportional control.
S e n s o r S e n s o r
r e a d in g r e a d in g
P C O N T R O L P C O N T R O L
S U B -C R IT IC A L T IM E S U P E R C R IT IC A L T IM E
S e n s o r
r e a d in g P c
( m in s )
P C O N T R O L
C R IT IC A L (S T A B IL IT Y L IM IT ) T IM E
Gc is the proportional gain at stability limit when the integral and derivative time are set to zero.
Go = optimum gain
Io = optimum integral time constant
To = optimum derivative time constant
S E N S O R M A X S L O P E
U N IT S T A N G E N T
U N IT - S T E P
IN P U T R E S P O N S E
O F A P R O C E S S
R
1
T IM E
L
R IN U N IT /M IN
L IN M IN
R is the maximum slope of a tangent drawn to the unit-step input response of the process to be controlled and
L is the time at which the tangent intersects the time axis. S is the change in manual output in percent.
Ziegler and Nichols recommended the following parameters for calculating optimum gain:-
Go = S for P control
RL
The Manual Level is unusual because its units must be the same as the loop output, i.e. percent, whereas the other main
loop analogue inputs (Process Varaiable, Occupied Setpoint, Unoccupied Setpoint) are in engineering units (e.g.
deg C).
When in manual, the integral value will be set to a value equal to the difference between the Manual Level and the sum
of the proportional and derivative terms so that when the manual state is removed, the loop output will initially be at
the level it was when set to manual. The integral function will then operate normally by gradually changing the loop
output to minimise the control error. This facility is called preloading the integral or sometimes preconditioning the
loop, and results in a `bump free' transfer from manual to closed loop control.
The manual facility is very useful when commissioning a system, in that the correct operation of all the output devices
can be verified in a methodical manner.
Because the manual state is selected by an internal logic signal, strategies can be devised which use the loop manual
facility to effect an automatic override or similar function.
Unoccupied setpoint
Unoccupied
setpoint
deviation NOC Occupation NOC Time
If the setpoint selection input for the loop is not optimum start (i.e. is set to OTP), then the warm-up time is effectively
reduced to zero so that a deviation alarm is likely to occur at the start of occupation. This could be overcome by disabling
the alarm with timer logic modules or by making the deviation limit larger than the difference between the setpoints.
The Default Value parameter defines the value used under the loop fail condition. Its actual meaning depends on the
Sensor Fail Action type selected.
In this case the control loop uses the Default Value as a fixed value for the process variable and calculates a loop output
to suit. This is usually used on single heating loops where a default reading might be set to, say 15 deg C on a loop with
an occupied setpoint of 20 deg C and a non occupied setpoint of 10 deg C. In this case, although the loop would not
control the heating, when there is a sensor failure it would produce 100% heating during occupied times and 0% heating
outside occupation. When the alarm condition clears, normal control resumes.
In this case the control loop uses the Default Value as a fixed value for its output. This value can be set anywhere from
0-100% and would ensure some safe level of heating (or cooling). For example, one might choose 66% output to run
two boilers out of three in the event of a sensor failure. Where 33% represents one boiler, 66% represents two boilers
and 99% represents three boilers. When the alarm condition clears, normal control resumes.
This is the same as Type 1 except the loop does not return to normal control automatically. Where this condition is
present the Default Action digital output is set.
To return the loop to normal control, it must be put into manual, and then returned to automatic control (i.e. set the
Manual Select bit to 1 then back to 0).
This form of alarm action would be used where it is necessary for the engineer to oversee the return of the plant to normal
running.
In this case, the loop output is held at its last output level before the alarm condition arose. This method is not
recommended since although it works well for short-lived failures (as the HVAC equipment continues without any major
disruption), if the failure happens outside occupation and continues for some time, then the loop would most likely be
held at zero output, and no heating would be achieved the next day. When the alarm condition clears, normal control
resumes.
Type 4: No Action
This type ignores the alarm status on the Process Variable and continues to attempt to control using the its value. Note:
for a READ alarm the last correctly received sensor value will remain in the sensor register, whereas for an out-of-limit
alarm (OUTL) the scaled value corresponding to the actual reading received will be put into the sensor register even
though this is beyond the normal range.
A
SPACE S1 99
TEMP P D1
1 Knob 1
OCC SP
O 1 SRM
NOC SP L1 S BINARY L
Knob 2 U 1
HYST.
0
S
ZONE 1, OSS
S1
HEAT
SOURCE P1
SPACE
The control loop acts just like a thermostat and has a distinct switch-on point and switch-off point. The extent of the
deadband between these two points is set up by varying the control loop gain term.
The output swing needed to switch the pump from ON to OFF or vice versa is 100. Therefore for a loop-gain of 100
the deadband would be 1 deg C; for a gain of 200 the deadband would be 0.5 deg C, etc. The graph of space temperature
will be of the form:-
S E T L E V E L
The control loop output will be continuously changing to match the measured temperature to the set temperature. In turn
the pump run time will be varied in a proportional manner to match the required heat load.
P E A K T O P E A K
C O N T R O L E R R O R
Installed systems using this method of control generally show peak error of less than 0.5 degC.
SPACE S1 PV
P 0-100
TEMP 1 OCC D1 DIGITAL
Knob 1 O SRM
1 OUTPUT
Knob 2 NOC
U
L1 S L 1
TO
TIME PROP.
PUMP
Period: 15 mins
GAIN ~20
INTEGRAL TIME 10 MINS
In the IQ this is achieved by reading the outside temperature (Sensor 2) and using a function module to calculate the
required flow temperature setting. The characteristic required is that at the lowest design temperature, the flow temperature
is set to its maximum and it reduces by approximately 30 deg C for every 10 deg C rise in outside air temperature. The
aim is to match the heat input to the building losses so both the slope and offset of the characteristic need to be modified
by experience.
FLOW
TEMP
A
S1
P 60
OUTSIDE AIR S2 G F1
3 D1
SRM
TEMP 3 -3 E -3G+75 L1 SBINARYL 1
75 O 1
H ADD/SCLR HYST
1 F U 30
S
ZONE 1
OTP
G F2 D2
1 E G-10 RLM
-1 S L 2 2
H ADD/SCLR
10 F
RAISE LOWER
END
Period 100 s
S1
V1
PRIMARY
HEAT
SOURCE P1 LOAD
y = mx + c
6 0
F L O W
S E T P O IN T
(D E G C ) 5 0
4 0
3 0
2 0
1 0
3 0 2 0 1 0 1 0 2 0 3 0
O U T S ID E A IR T E M P E R A T U R E (D E G C )
For the required response shown in the above graph:-
comparing
D=y, E=3, G=x, H=75 and set F=1
then D = -3G + 75
Which is the equation for the function module F1 in strategy diagram above.
The output from the function module is fed to the control loop OCC setpoint. The output of the loop controls the
modulation of the valve. The measured value for the loop is of course the flow temperature which will be controlled to
match the setpoint.
The diagram shows a second function module F2 which is used to subtract a value from the occupied setpoint and pass
the result to the non-occupied setpoint. This will reduce the flow temperature when the building is unoccupied.
A practical weather compensated strategy would be slightly more complicated if it was going to use optimum start
control. For this to work effectively, the flow temperature would need to be set to a maximum during warm-up time.
- -
S P A C E F L O W
S E N S O R S E N S O R S E C O N D A R Y
P R O C E S S
H E A T R O O M H E A T H O T W A T E R
The above example shows the primary process of heating a room requiring a secondary process of heating hot water
as a supply to the room heater.
The control is performed by applying a setpoint which is the required level for the space sensor. The first loop then
generates an output which is a heat demand level. This can be used to produce a setpoint which is the required level
for the hot water flow temperature sensor. This setpoint is a cascaded setpoint and is applied to the secondary or cascaded
loop which actually controls the secondary process (heating the water). The strategy is shown below:
S P A C E T E M P
L 1
S T P T
S T P T
S C A L E D
L 2
H T G W A T E R
T E M P E R A T U R E M IX IN G V A L V E
1) Disturbances arising within the secondary part of the process are corrected before they have much effect
on the primary variable.
2) The system is capable of responding much more quickly to set point changes than a single loop system.
3) It allows the flow of the mass of energy from the secondary process to be controlled safely within
prescribed limits e.g. in the example below the flow temperature setpoint would probably have setpoint
limits of 20 deg C to 80 deg C.
FLOW TEMP S1
SPACE TEMP SENSORS
S5
S2
S4
S3
2
1
1
1
1
H AVERAGE
G
F
E
F1
D
Knob 2
Knob 1
NOC SP
OCC SP
P
O L1
U
ZONE 1
OSS
A
G
RSCL FR E
FF2
20
80
SOURCE
PRIMARY
HEAT
P
U
O
L2
A
S
20
60
Period 100s
RAISE LOWER
BINARY
HYST
D2
END
D1 L
2
1
P1
S1
SRM
RLM
1
1
SPACE
S2
S5
S3
S4
Loop 1 controls the primary process and produces a heat demand which is rescaled from 0 to 100 by function module
F2 to a range from setpoint lower which is the minimum acceptable flow temperature (20 deg C) to setpoint upper which
is maximum acceptable flow temperature (80 deg C). The output of F2 is used as a setpoint for loop L2.
Sensor S1 measures the flow temperature and provides the process variable signal for loop L2. Loop L2 is the main loop
controlling hot water temperature by modulating valves/dampers and switching, pump/fans ON and OFF to maintain
the setpoint fed to it via S2, S3, S4, S5, F1, L1 and F2. The setpoint for Loop L2 is derived from the space temperature
using Loop L1.
Note that loop 2 has its occupied and unoccupied setpoints connected together so that its Setpoint Select input would
have no effect. The change in level with respect to occupation is performed by Loop 1.
Outside air temperature compensation is in fact anticipating that the space temperature will drop if the heating is not
increased. This is achieved by Feed Forward control where the outside air temperature drop is added into the loop output
to increase heat demand, and this is used to trim the setpoint.
S P A C E T E M P
O /S A IR
O /S A IR
*n
S T P T O /S A IR
R E S C A L E
S T P T
H T G W A T E R V A L V E
H T G W A T E R T E M P
Feed forward control changes the secondary loop setpoint before the primary variable detects the change (which would
normally be after some time lag).
A
S1 RAISE
Space Temp P
1 D1
L RLM
L1 S 1 ZONE VALVE
Knob 1 O 1 LOWER
Knob 2 U
RAISE LOWER
S END
Period 100 s
ZONE 1
OTP
SWITCH 1
E F9 AUTO/OFF
FROM OTHER F A
ZONE HEATING G G F10 P
LOOP DEMANDS 60 E D5
H MAXIMUM 1.2 1.2G-60 G F11 F12 0 L
F
ADD/SCLR 1 E L5 S 5 Calorifier Control
-1
H G+H G O
1 F
H ADD/SCLR LIMIT AT F U
Outside Air Temp S6 RAISE LOWER
F8 Knob 12 S
2 20 END
(20°C) Period 100 s
-1
-G+20
ADD/SCLR
1
Loop Module
414
Part 2 Section 19 Loop Module
The basic flow setpoint is derived from this maximum loop output by F10 which is set up to perform the function shown
in the graph below.
1 0 0
8 0
O U T P U T O F B A S IC F L O W S E T P O IN T
A D D /S C A L E R
F 1 0 6 0
4 0
2 0
IN P U T
2 0 4 0 6 0 8 0 1 0 0
M A X L O O P O U T P U T F R O M A R E A S S E R V E D
Thus when G = 60/1.2 = 50, the output = 0 and it rises to G = 1.2 x 100 - 60 = 60 when the input = 100.
This is then added to a value derived from the outside air temperature by module F8.
This outside air temperature (OAT) trim is calculated by module F8 which has the equation:- D=-G+20
O U T P U T F 8 2 0
T R IM
D E G C
-1 0 IN P U T
2 0
-1 0
O U T S ID E A IR T E M P D E G C
F 1 1
1 2 0 O U T S ID E
T E M P
C O M P E N S A T E D D E G C
F L O W 1 0 0 - 1 0
S E T P O IN T
D E G C 0
8 0
1 0
6 0 2 0
4 0
1 0
1 0
2 0
1 0
IN P U T
2 0 4 0 6 0 8 0 1 0 0
The trim will be zero at OAT of 20 deg C, and thus the graph at 20 deg C is the same as that shown previously for the
output of F10 above. As the OAT decreases in 10 deg C, steps the setpoint will have 10 deg C added to it.
This basic setpoint is then limited by F12 so that it cannot rise above 80 deg C. The lower limit is set by Knob 12 (node
232) which will normally be 20 deg C. The outside compensated setpoint fed to the calorifier loop L5 will then vary as
follows:-
O U T P U T
1 2 0
O U T S ID E
T E M P
C O M P E N S A T E D D E G C
F L O W 1 0 0
S E T P O IN T
D E G C
0
8 0
1 0
6 0 2 0
4 0
2 0
IN P U T
2 0 4 0 6 0 8 0 1 0 0
Note that loop 5 has an auto/manual control on its Manual Select (A) input; if this is set to 1 then the loop output will
go to 0% as specified by its Manual Level Input.
This can be achieved by having a continuous variable where 0% is full cooling and 100% is full heating and 50% selects
both OFF. It can be achieved by adding half the output of the heating loop (0 -100) to minus half the output of the cooling
loop (0 -100) and since the output must be 50 when both are zero, an input of 50 is added.
M A X H E A T
1 0 0 %
IN C R E A S E H E A T
5 0 % N O P L A N T
IN C R E A S E C O O L
0 %
M A X C O O L
1) If the primary aim of the system is to save energy, then it is very desirable to hold off the cooling plant
for as long as possible. This to a lesser extent also holds true for the heating plant. This is simply achieved
by ensuring a deadband between the heating and cooling setpoints, e.g. heating could be set to 19 deg C
cooling 22 deg C.
2) Better control can be achieved by virtue of being able to separately ‘tune’ the heating and cooling regimes.
3) Because of the way the signals are combined to form one output control signal, there will not be a situation
where the plant items will be fighting one another, i.e. heating and cooling plant on together.
HEATING LOOP
FUNCTION
MODULE
L E
F E-F
0.5
G 2 2
-0.5
H ADD/SCLR FUNCTION
MODULE
E
50
F E+50 HEAT/COOL
1
G DEMAND
L 1 H ADD/SCLR
COOLING LOOP
This can be achieved by two function modules as shown above. This combined demand can then drive dampers about
a centre point and separate heat and cool plant as below:-
D R RECIRC
F F 70 DAMPER
G S RLM (MIX RECIRC/
RAISE LOWER
RSCL FR E 30 END
L FRESH AIR)
Period 80 s
100 R
F F D
HEAT/COOL S RLM HEATING VALVE
DEMAND G D
RAISE LOWER
50
E RSCL TO END L
Period 100 s
0 F F D R
G S RLM COOLING VALVE
RAISE LOWER
50 E RSCL TO END
L
Period 80 s
This strategy will set the damper midway under conditions of zero demand. For maximum heat demand the dampers will
be at 70% recirculation with the heating valve fully open. For maximum cooling the recirculation dampers will be at 30%,
(70% fresh air), with the cooling valve fully open.
Manual Select (SET: Manual Address): (digital, source/constant) This digital input will switch the loop into manual
override if set true (Manual) where the loop output will be set equal to the Manual Level input. If set false (Automatic)
it will revert to automatic control. It can either be sourced from a module’s digital output or set to a constant value (0
or 1). If connected to a module’s digital output, the output’s details will be shown on the web page.
Process Variable: (analogue, source/constant) The measured value being controlled. The loop controls the process so
that the process variable moves towards the currently selected setpoint. It can either be sourced from a module’s analogue
output or set to a constant value. If connected to a module’s analogue output, the output’s details will be shown on the
web page.
Occupied Setpoint (SET: Occupation Setpoint): (analogue, source/constant) This is the setpoint used by the loop when
the Setpoint Select input is set true (to one). It can either be sourced from a module’s analogue output or set to a constant
value. If connected to a module’s analogue output, the output’s details will be shown on the web page.
Unoccupied Setpoint: (analogue, source/constant) This is the setpoint used by the loop when the Setpoint Select input
is set false (to zero). It can either be sourced from a module’s analogue output or set to a constant value. If connected
to a module’s analogue output, the output’s details will be shown on the web page.
Not Used (SET only): Checking this tick box will cause the Unoccupied setpoint to be set to ‘nul’ which means
that the loop will be turned off during non-occupation. When the loop is turned off the output is set to zero, and
integral and derivative parts are zeroed.
Manual Level: (analogue, source/constant) The level to which the loop output is driven when the Manual Select input
is set true (to one). It can either be sourced from a module’s analogue output or set to a constant value. If connected
to a module’s analogue output, the output’s details will be shown on the web page.
Setpoint Select: (digital, source/constant) This digital input will select the Occupied Setpoint to be the loop’s setpoint
when set true (Occupied), and will select the Unoccupied Setpoint when set false (Non occupied). If set false with the
Unoccupied Setpoint set to ‘nul’ by the Not Used checkbox in SET, the loop will be turned off. It can either be sourced
from a module’s digital output or set to a constant value. If connected to a module’s digital output, the output’s details
will be shown on the web page.
Integral Time (mins): (analogue, source/constant) The time after which the integral part (an accumulation of gain times
error) would be added to the output. If set to zero, there is no integral action. It can either be sourced from a module’s
analogue output or set to a constant value. If connected to a module’s analogue output, the output’s details will be shown
on the web page.
Derivative Time (mins): (analogue, source/constant) This defines the amount by which to multiply the gain times rate
of change of error (e.g. degC/min) to produce the derivative term. If set to zero, there is no derivative action. It can either
be sourced from a module’s analogue output or set to a constant value. If connected to a module’s analogue output,
the output’s details will be shown on the web page.
Integral: (analogue, constant) The integral part of the output (in percent) as calculated by the loop module.
Derivative: (analogue, constant) The derivative part of the output (in percent) as calculated by the loop module.
Reschedule Time: (analgue, constant) The interval (seconds) between loop output calculations.
Sensor Fail (SET: Fail Action): (analogue, constant) The loop fail action taken when the loop detects a PV Fail alarm.
The parameter is set in the range 0 to 4 (these are explained fully in section 19.14 above):
0 = Default PV (SET: default PV(Auto))
1 = Default OP (SET: Auto/Default Output)
2 = Stay at Default OP (SET:Default OP)
3 = Freeze OP (SET: maintain same output)
4 = No Action
Default Value: (analogue, source/constant) The default value used when loop fail action is taken. For loop fail action
type 1 it should be set to a value in engineering units (e.g degC). For loop fail actions type 1 and 2 it should be set to
a value in per cent. It is not used for loop fail actions type 3 and 4.
It can either be sourced from a module’s analogue output or set to a constant value. If connected to a module’s analogue
output, the output’s details will be shown on the web page.
Default Action: (digital, output) This digital output indicates that loop fail action type 2 (Stay at Default OP) has been
taken. It can be used as an indication that the loop will stay in this alarm action state after the alarm condition has recovered
until the manual override input is cycled on and off. If connected to a module’s digital input, the input’s details will be
shown on the loop details web page.
This output is shown as connective in SET (i.e. Lna, where L = loop module, n = loop module number, a = default action,
e.g. L1a).
Setpoint Deviation (SET: Setpoint Dev. Level): (analogue, source/constant) The maximum loop error value that can be
reached before an SP Deviation alarm is generated. Note that the maximum error can be greater during non-occupation
as explained in section 19.13 above. It can either be sourced from a module’s analogue output or set to a constant value.
If connected to a module’s analogue output, the output’s details will be shown on the web page.
In Alarm: (analogue, status)This value indicates whether the loop is in alarm, i.e. either a PV Fail, or a SP Deviation alarm,
or has no alarm. It has accompanying text shown in the list below which is shown on the loop overview page in the ‘alarm’
column.
0 = No alarm
6 = SP Deviation alarm
7 = PV Fail alarm
The alarm state is shown if the alarm condition has been present for longer than that alarm’s delay time, and that alarm
is enabled to be reported. If both alarms are present the SP Deviation will be reported. It will be set back to 0 immediately
both the alarms are in the clear state.
PV Fail: This indicates the (PV Fail) Alarm State as defined below. Clicking on PV Fail on the web page will display the
PV Fail alarm sub-module. The way in which the sub-module declares alarms and clear alarms is described in Pt. 1 section
12.4.1.
(PV Fail) Alarm State: (digital output) This will be 1 if the PV Fail alarm condition has been present for longer than
its alarm delay time. It takes no account of its alarm enable. If connected to a module’s digital input, the output’s
details will be shown on the loop details web page.
This output is shown as connective in SET (i.e. Lnf1S, where L = loop module, n = loop module number, f1 = PV
Fail alarm sub-module 1, S = status, e.g. L1f1S).
(PVFail) Enabled (SET: PV Fail Enable): (digital, source/constant) This is an input to the sub-module which will
enable or disable the reporting of the alarm. Once the Alarm State is true the alarm will be reported; when the alarm
clears a clear alarm will be reported. This input can either be sourced from a module’s digital output, or set to a
constant value (0 or 1). If connected to a module’s digital output the output’s details will be shown on the web
page.
(PV Fail) Alarm Sent: (digital status) This indicates that the alarm has been sent to the group module. This will
only happen if the Alarm State has been present for longer than the Alarm Delay, and the alarm is Enabled to be
reported.
(PV Fail) Alarm Delay (secs) (SET: PV Fail Delay): (analogue, source/constant) This is the delay for which the
PV Fail alarm input must be present before the Alarm State is declared. The alarm delay for the clear alarm state
is always zero.
The alarm delay can either be sourced from a module’s analogue output, or set to a constant value. If connected
to a module’s analogue output the output’s details will be shown on the web page.
(PV Fail) Time in Alarm (secs): (analogue, status) This is the elapsed time since the Alarm State commenced
(PV Fail) Alarm Group: (analogue, constant) This is the alarm group module to which the alarm will be sent.
SP Deviation: This indicates the (SP Deviation) Alarm State as defined below. Clicking on SP Deviation on the web
page will display the SP Deviation alarm sub-module. The way in which the sub-module declares alarms and clear alarms
is described in Pt. 1 section 12.4.1.
(SP Deviation) Alarm State: (digital, output) This will be 1 if the PV Fail alarm condition has been present for longer
than its alarm delay time. It takes no account of its alarm enable. If connected to a module’s digital input, the input’s
details will be shown on the loop details web page.
This output is shown as a connective in SET (i.e. Lns1S, where L = loop module, n = loop module number, s1 =
SP Deviation alarm sub-module 1, S = status, e.g. L1F1S).
(SP Deviation) Enabled (SET: Setpoint Dev. Alarm Enable): (digital, source/constant) This is an input to the sub-
module which will enable or disable the reporting of the alarm. Once the Alarm State is true the alarm will be reported;
when the alarm clears a clear alarm will be reported. This input can either be sourced from a module’s digital output,
or set to a constant value (0 or 1). If connected to a module’s digital output the output’s details will be shown on
the web page.
(SP Deviation) Alarm Sent: (digital status) This indicatesthat the alarm has been sent to the group module. This
will only happen if the Alarm State has be present for longer than the Alarm Delay, and the alarm is Enabled to
be reported.
(SP Deviation) Alarm Delay (secs) (SET: Setpoint Dev. Delay): (analogue, source/constant) This is the delay for
which the SP Deviation alarm input must be present before the Alarm State is declared. The alarm delay for the
clear alarm state is always zero.
The alarm delay can either be sourced from a module’s analogue output, or set to a constant value. If connected
to a module’s analogue output the output’s details will be shown on the web page.
(SP Deviation) Time in Alarm (secs): (analogue, status) This is the elapsed time since the Alarm State commenced
(SP Deviation) Alarm Group: (analogue, constant) This is the alarm group module to which the alarm will be sent.
Page: (analogue, constant) SET file strategy page number on which module appears.
Disable Module (SET: Module State - Enabled/Disabled): (digital, source/constant) This input will disable the module,
i.e prevent it from being serviced. Its internal states and output will be maintained at their values prior to disabling. This
input can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s
digital output the output’s details will be shown on the web page.
Sequence Table: (digital, constant) This is set to sequence table 1 if the module is sequenced (in the sequence table).
It is set to table zero if the module is event driven. Note that the loop module must not be event driven
Sequence Step: (analogue, constant) The loop module can be either sequence table or event driven. If event driven the
step is set blank in SET, and the parameter does not appear on the web page. For sequence step driven modules this
defines the sequence step in the sequence table (see Pt. 1 section 5.6); the module may be entered into the sequence
table more than once.
TYPE
co d e
SET Web Low High
page
Controller Parameters
SOURCE/CONST
Process Variable R/W R/W* P -1020 +1020 0 Measured value being controlled. Can be
connected to an analogue output.
OUTPUT
Output R/W R/W D 0 100 0 The value of the module's output. Can be
(SET: Destination) connected to an analogue input.
Occupied Setpoint R/W R/W* O -1020 +1020 0 Setpoint used when setpoint select set to
(SET: Occupation one).. Can be connected to an analogue
Setpoint) output.
Unoccupied Setpoint R/W R/W* U -1020 +1020 0 Setpoint used when setpoint select set to
or zero. If set to nul, never used. (see 'not used'
nul below). Can be connected to an analogue
output.
Manual Level R/W R/W* L -1020 +1020 0 Level to which loop output is driven if manual
select set to one. Can be connected to an
analogue output.
Setpoint Select R/W R/W* S 0 1 0 If set to one the occupied setpoint is used,
SOURCE/CONST
Gain R/W R/W* G -1020 +1020 0 Proportional gain of loop. Can be connected
to an analogue output.
Integral Time (mins) R/W R/W* I -1020 +1020 0 Time after which integral term is added to
output.
minutes Zero means no integral action.
Can be connected to an analogue output.
Derivative Time R/W R/W* T -1020 +1020 0 Amount to multiply gain times rate of change
(mins) of error to produce derivative part of output.
minutes Can be connected to an analogue output.
STATUS
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Controller Parameters
SOURCE/CONST
Reschedule Time R/W R/W* R 1 600 0 Interval between loop output calculations.
Zero means loop is disabled.
Can be connected to an analogue output.
seconds
Sensor Fail R/W R/W F 0 4 0 Action taken if loop detects PV Fail alarm.
(SET: Fail Action) 0=Default PV
CONST
1=Default OP
2=Stay at Default
3=Freeze OP
4=No action
SOURCE/CONST
Default Value R/W R/W E -1020 +1020 0 Default value used by fail action.
or or If action type 0 can be to -1020 to +1020.
0 100 If action type 1 or 2 can be 0 to 100.
Can be connected to an analogue output.
Default Action R R/W* a 0 1 0 Digital output indicating the fail action type 2
OUTPUT
has been taken. Requires manual
intervention to clear fail action.
Can be connected to a digital input.
SOURCE/CONST
Setpoint Deviation R/W R/W V -1020 +1020 0 The maximum error that can be reached
(SET: Setpoint Dev. before a SP Deviation alarm is generated.
Level) Can be connected to an analogue output.
Alarm Sent - R/W f1(K) 0 1 0 This indicates that Alarm has been sent to
(PV Fail) the group module
SOURCE/CONST
Alarm Delay (secs) R/W R/W* f1(D) 0 2730 0 The time for which the alarm must be present
(PV Fail) before the alarm state is declared.
(SET: PV Fail delay) seconds Can be connected to an analogue output.
Time in Alarm (secs) - R/W f1(T) -1020 +1020 0 Elapsed time since alarm state commenced
STATUS
(PV Fail)
seconds
CONST
Alarm Group R/W R/W f1(G) 0 500 0 Alarm group module to which alarm will be
(PV Fail) sent
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Controller Parameters
SP Deviation R R/W s1(S) 0 1 0 Indicates alarm condition has been present
OUTPUT
Alarm State for longer than the delay time. Independent of
(SP Deviation) alarm enable. Can be connected to a digital
input.
Alarm Delay (secs) R/W R/W* s1(D) 0 2730 0 The time for which the alarm must be present
(SP Deviationl) before the alarm state is declared. Can be
(SET: Setpoint Dev. seconds connected to an analogue output.
Delay)
Time in Alarm (secs) R/W R/W s1(T) -1020 +1020 0 Elapsed time since alarm state commenced
SP Deviation)
seconds
CONST CONST CONST CONST CONST
Alarm Group R/W R/W s1(G) 0 500 0 Alarm group module to which alarm will be
(SP Deviation) sent
Label R/W R/W $ 0 30 null The module identifier used on strategy pages
characters and web pages
* This source/constant parameter cannot be changed via the web page if it is set as a source.
Currently network module 1 is always type Ethenet IP, and network module 2 is always type IQ LAN and is only created
for IQ3/LAN; network module 3 is always type BACnet and is only available in IQ3/BAC controllers.
The network modules do not appear on the strategy page. A type 2, IQ LAN, network module does not appear in SET.
The other parameters are grouped into three sections which can be separately set to ‘Not Sent’. This is so that the strategy
file may be used for several controllers (see Pt. 1 section 6.1.6). If set to ‘Not Sent’ the boxes are greyed out. These sections
are:
Main Ethernet Parameters: IP Address, Subnet Mask, UDP Port, Default Router
DHCP Parameters: Hostname, Disable Default Hostname, WINS Servers 1 to 5, DNS Servers 1 to 5
Remote Devices: Remote Devices 1 to 20 (Addresses and Subnet Masks)
If the Addressing Mode is set to ‘Obtain Automatically’, the IP Address, UDP Port, Default Router, WINS Servers 1
to 20, and DNS Servers 1 to 20 are greyed out as these can be supplied automatically by the DHCP server.
For the Remote Device, the device may alternatively be identified by a host name. Remote Devices also need a subnet
mask to be set up. The Remote Device sub-dialogue box is shown below:
It is recommended that the details of two devices (either IQ3s , 3xtend/EINC Ls, or IQViews) in the network from each
subnet the other side of a router (s) should be set up in every device (either IQ3s , 3xtend/EINC Ls, or IQViews) on the
local subnet. For increased reliability, details of additional devices should also be set up.
For a particular project it is easier to create a table of Remote Device details that can be entered into all the devices on
the network. This is normally done in initial configuration using IPTool as explained in Pt. 1 section 5.1.
SET also enables this to be done with the ‘Set Project Defaults’ and ‘Use Project Defaults’ buttons. The Remote Device
details should be entered into one controller, and ‘Set Project Defaults’ should be selected which will save that list for
the project.
On the next controller, selecting ‘Use Project Defaults will set up its Remote Devices.
If the DHCP server is not operating, the outstation will enter Link/Local mode where the controllers on the subnet will
negotiate their IP addresses and set a default subnet mask. Router 1, WINS servers 1 to 6 and DNS servers 1 to 6 will
remain at their last settings (which in the case of defaults are all zero).
In order to become part of a Trend network and for SET to be able to download a strategy the Lan number and outstation
address need to be set up in each IQ3; this is best done using IPTool.
In IPTool the IQ3 is selected by clicking on the appropriate row in the lower part of the dialogue box, then the Lan number
(lan) and outstation address (node) can be edited and sent to the controller by selecting the WRITE DATA button.
Note that if the current loop Lan auxiliary board (/LAN option) is fitted the address switch setting will override the
configured outstation address setting.
The Lan number and Outstation address are also shown in the address module (see Pt. 2 section 2.3.2).
If there is no DHCP server and Link/Local operation is not satisfactory*, the controller should be set to ‘Enter Manually’
Addressing Mode, by de-selecting the device mode (Auto-ip-DHCP) check box in IPTool.
*Note that Link/Local operation cannot create a network across a router, and can only communicate with PCs who are
also in Link/Local and on the same segment.
In ‘Enter Manually’ Addressing Mode, the following need to be set up manually (best done using IPTool):
IP Address
Subnet Mask
Router 1
and optionally:
WINS servers 1 to 6
DNS servers 1 to 6
The IPTool should then be used to set up a vCNC in the controller so that SET can download the strategy.
Once these are set up in one IQ3, IPTool enables them to be copied to other IQ3s. This is done by selecting Default Settings
and selecting the ‘Copy from Selected Device’ and then the ‘Save’ buttons.
Once the next controller is selected the tick boxes next to the items required to be set from the Default settings should
be selected and the parameters will be set to the previously saved defaults.
IPTool has other uses (see Pt. 1 section 5.1). It can also be used to set up the following Ethernet IP Network module
parameter:
Host name: If auto addressing is selected, and the default host name will not suffice.
20.1.4 Parameters
Ethernet IP type network module parameters are mainly concerned with either basic Ethernet operation, or with DHCP
operation.
IP Address: (characters, constant) The IP (internet protocol) address of the controller. This must be unique. It is normally
specified by the persons responsible for the IT system. The following IP addresses should not be used:
• Addresses 127.x.x.x, reserved for loopback.
• The non masked part of the address cannot be all 1’s or 0’s e.g. if address is 1.2.x.x and subnet mask is 255.255.0.0
then x.x. cannot be either 255.255 or 0.0.
• Addresses 224.0.0.0 to 239.255.255.255, reserved for multicast.
• Addresses 240.0.0.0 to 247.255.255.255, reserved for experimentation and development.
Further addresses may not be suitable for a particular system; check with the company’s IT department.
Not Sent: Within SET the IP address can be excluded from being downloaded. This enables a strategy to be used
by several controllers (see Pt. 1 section 6.1.6). This Not Sent selection will also stop the following being sent to
the controller:
IP address, Subnet Mask, UDP port, Default Router (Router 1).
Subnet Mask: (characters, constant) The mask used to mask the IP address to produce a subnet. All IQ3s and EINCs
(3xtend/EINC Ls, IQViews) must be on the same subnet (and hence have the same subnet mask) in order to construct
a Lan or Internetwork. IQ3s on the other side of a router may have a different subnet mask. An invalid subnet mask (e.g.
0.0.0.0) should not be used.
Further subnet masks may not be suitable for a particular system; check with the company’s IT department.
UDP Port (IPTool: inet): (analogue, constant) The UDP (User Datagram Protocol) port defines the IP port used by the
IQ3. All the IQ3s and EINCs (3xtend/EINC Ls, IQViews) used to create Lans and an Internetwork must use the same UDP
port number. These devices can be set up with different UDP ports to create completely separate systems on the same
subnet.
Router 1 (SET: Default Router): (analogue, constant) This specifies the IP address of a router to which messages are
sent if the destination address is not on the local subnet. It should be set to the IP address of a router on the same subnet
as the controller.
Note that a change to address parameters (IP Address, Subnet Mask, UDP, Router 1) causes a general reset.
XML Server: (set by default to 0= Disabled). Not used. Placeholder for future development feature.
Default Hostname (SET: Disable Default Hostname): (digital, constant) The IQ3 will normally respond to its default host
name which is a function of its MAC address (see Pt. 1 section 3.3.11.3). If set to ‘Disabled’ (checked in SET), the default
host name can no longer be used to communicate with this IQ3 (e.g. for security reasons).
WINS Servers 1 to 5: (characters, constant) The IP addresses of WINS (Windows Internet Naming Service) servers.
A WINS server will respond to a host name with its IP address. One must be set up if using host names across routers.
DNS Servers 1 to 5:(characters, constant) The IP addresses of DNS (Domain Name System) servers. A DNS server will
respond to a domain name (e.g.atrendsite.com) with its IP address. One must be set up if using an internet domain name
for the email server address.
Remote Device Subnet 1 to 20: (characters, constant) The subnet masks of the remote devices whose IP addresses are
specified by the Remote Device 1 to 20 parameters above.
Device Instance: This is the address used for BACnet communications (see Pt. 1 section 3.7.4). It is unique on the BACnet
system. If Manual device instance (below) is set to Automatic, the instance is calculated automatically and the value
is greyed out as it cannot be changed. If set to Manual the instance can be set up manually.
Manual device instance: This defines whether the BACnet Device Instance is set up manually or automatically. If
determined automatically, the instance is calculated using the formula below:
(Lan Number x 1000)+Local Address (see Pt. 2 section 2.3.2). i.e. automatic instance 20021 is address 21 on Lan 20
UDP Port: This defines the UDP port used by the BACnet network to communicate using BACnet communications. All
BACnet devices on the same BACnet segment must use the same UDP port if they are to intercommunicate. It is normally
set to 47808 (Hex’BAC0’), but is allowed to be changed (e.g. if it is required to run two separate groups of BACnet devices
on the same IP subnet - cf. Pt. 1 section 3.3.12)
BBMD: This enables the IQ controller to become a BACnet, IP Broadcast Management Device (i.e. the device which
enables BACnet broadcast messages to cross routers). There must be one such device on each BACnet segment if
broadcast messages are to cross routers, hence the IQ3’s BBMD functionality can be enabled or disabled according to
whether or not there is an existing BBMD device on the segment. Enabling the IQ3’s BBMD functionality also enables
the BDT table to be set up (see below). Note that the BBMD functionality will not work with devices which use automatic
IP addressing (DHCP), and under such conditions should left disabled (see Pt. 1 section 3.7.4).
Send I-am at Startup: Specifies whether the IQ3 sends an ‘I am’ message at startup to notify other BACnet devices (e.g.
supervisors or software tools) of its presence on the network.
Network Number: (analogue, constant) The number of the BACnet network on which the IQ3 resides.
BTL Compliance: (digital, constant) This parameter is enabled by SET by default to make the IQ3 BTL compliant (for
compliance other strategy restrictions apply, see Pt. 1 section 3.7.7). However, it is disabled after a firmware upgrade (to
v2.1 or greater) so that the strategy will work the same way as it did before the upgrade. When this parameter is enabled,
BACnet writes to the schedule object are disabled as these writes are not BTL compliant. If it is required to write to the
BACnet schedule object over BACnet, the BTL Compliance parameter should be disabled, but the IQ3 will no longer
be BTL compliant.
BACnet writes to the schedule module are not BTL compliant because:
1 Writes to individual array elements are not supported. Weekly Schedule, and Exception Schedule arrays can only be
written to as complete arrays; individual elements cannot be written to.
2 Day of week specifications (e.g. every thursday) are not supported.
BDT Entry: The BDT (BACnet Distribution Table) contains details of up to 32 BBMD devices the other side of routers
so that the IQ3 manage broadcast messages across routers. Each entry in the table contains:
IP Address: The IP address of the remote BBMD device
Subnet Mask: The Subnet mask of the remote BBMD device
UDP Port: The UDP port of the remote BBMD device. This would normally be the BACnet default value (47808),
but it is possible for the BACnet devices the other side of a router to use a different UDP port.
TYPE
Parameter Web Comms Default
SET IPTool Code Low High
page
Controller Parameters
Network module 1 is always type 1.
Network module 2 (created if /LAN is fitted)
CONST
Automatically is type 4. Network module 3 (only available
Type - R - Y 1 4 set up in on IQ3/BAC) is type 5.
controller 1=Ethernet IP
4= IQ Lan
5=BACnet
Ethernet IP (type 1) Parameters
IP Addressing Specifies whether IP settings are
CONST
Mode generated automatically or manually
(Addressing R/W R/W R/W P 1 2 1 1=Obtain Automatically
Mode) 2=Enter manually
(device mode)
se e if manual IP address of controller.
CONST
addresses 128.1.1.3 If 'Obtain automatically' it will be set up
IP Address R/W* R/W* R/W* I defined in if link/local automatically
20.1.4.1 start at
above 169.254.0.0
see mask CONST Mask used on IP address to produce
Subnet Mask R/W* R/W* R/W* S in 20.1.4.1 255.255.0.0 subnet. If 'Obtain automatically' it will be set
above up automatically
Port used by all Trend Ethernet
CONST
WINS Servers 1 addresses, all 5 set to must be set up if using host names across
R/W* R/W* R/W* W
to 5 e.g. "0.0.0.0" routers. If 'Obtain automatically' it will be
"xx.xx.xx";"- set up automatically
xx.xx.xx.xx"
set of up to
5 IP IP address(es) of DNS server(s). One must
CONST
DNS Servers 1 addresses, all 5 set to be set up if using host names across
R/W* R/W* R/W* N
to 5 e.g. "0.0.0.0" routers. If 'Obtain automatically' it will be
"xx.xx.xx";"- set up automatically
xx.xx.xx.xx"
*These items cannot be changed if IP addressing Mode set to ‘Obtain Automatically’ as they are normally set up by
the DHCP server.
TYPE
Parameter Web Comms Default
SET IPTool Code Low High
page
Controller Parameters
Ethernet IP (type 1) Parameters (continued)
set of up to List of up to 20 device addresses or host
20 names for use with auto-addressing
addresses, Each item in list is either IP address or
e.g. host name of device other side of router
"xx.xx.xx.xx- with which this IQ is to construct aTrend
";"eric" network on Ethernet.
IP address,
CONST
se e
Remote Device all 20 set to
R/W R/W R/W b addresses
1 to 20 "0.0.0.0"
defined in
20.1.4.1
above
or
hostname
as
1 to 15
characters
set of up to LIst of up to 20subnet masks
20 masks, corresponding to remote devices'
e.g. CONST addresses above
"xx.xx.xx.xx"
Remote Device all 20 set to
R/W R/W R/W s ;"xx.xx.xx.xx-
Subnet Mask "0.0.0.0"
"
see mask
in 20.1.4.1
above
IP address IP address, host name, or internat domain
(see name of email server. Must be set up if
addresses sending email alarms.
defined in
20.1.4.1
CONST
above) or
Email Server
R/W R/W R/W L hostname 57612
Address
as
1 to 15
characters
or internet
domain
name
IQ LAN (type 4) Parameters
STATUS
set by /SER The baud rate on the current loop Lan. All
9600 or
Baud Rate - R - b board devices on current loop must have same
19200
switches baud rate
SET Associated Parameter
Disables IP Address, Subnet Mask, UDP
Not Sent
R/W - - - 0 1 0 Port, Default Router from being
(IP Address)
downloaded in strategy
Disables Host name, Disable Default Host
Not Sent
R/W - - - 0 1 0 name, WINS servers and DNS servers
(DHCP)
from being downloaded to controller
Not Sent Disables Remote Devices' addresses and
(Remote R/W - - - 0 1 0 subnet masks from being downloaded to
Devices) controller
TYPE
Comms
SET Web Code Low High
page
Controller Parameters
BACnet (type 5) Parameters (continued)
DISABLE R/W - ~ 0 1 0 Disables BACnet communications
Module 0=enabled (default)
CONST
(SET:Enable 1=disabled
BACnet
Module/Disable
BACnet Module)
Device Instance R/W R i 1 419- Calculated The controller's address on the BACnet system. If
CONST
4303 automatically Manual Device Instance below is set to automatic,
instance = (Lan numberx1000) + Local address
Manual device R/W R/W A 0 1 0 Specifies whether the Device Instance is calculated
CONST
instance automatically or set up manually.
0=automatic (default)
1=manual
UDP Port R/W R/W E 0 655- 47808 The UDP port used to send messages to other
CONST
35 devices on BACnet.All BACnet devices on the
same BACnet segment must use the same UDP
port to intercommunicate.
BBMD, R/W R/W e 0 1 0 Specifies whether or not the IQ3 acts as a
CONST
Network Number R/W R/W n 1 655- 1 BACnet network number of this IQ3
34
BTL Compliance R/W R/W c 0 1 1* Enables BTL Compliance:
1=enabled (disables BAcnet writes to schedule
CONST
object)
0=disabled (BACnet writes to schedule object
enabled)
*SET default is enabled, but default after a firmware
upgrade is disabled
BDT Remote IP R/W R/W bn(B)b set of up to all 32 set to List of up to 32 device addresses. Each item in list
Address 32 "0.0.0.0" is IP address of BBMD device the other side of a
IPaddress- router which is able to forward broadcast
CONST
e s, messages
se e
addresses
defined in
20.1.4.1
above
BDT Remote R/W R/W bn(S) set of up to all 32 set to List of up to 20subnet masks corresponding to
Subnet 32 masks, "0.0.0.0" remote IP addresses above
e.g.
CONST
"xx.xx.xx.xx"
;"xx.xx.xx.xx-
"
see mask
in 20.1.4.1
above
BDT Remote R/W R/W bn(E) set of up to all 32 set to List of up to 32 UDP ports corresponding to remote
CONST
It is also possible to drag a whole BACnet network from the System View to the Project/View/Device View; in this case
only the ‘Starting node number’ is requested, the other NTD modules will then be numbered consecutively.
The NTD can then be viewed by right clicking on the NTD icon on the BACnet Lan, and the Identifier and attributes
should be set up.
21.4 Sharing the NTD Modules between IQ3 controllers using SET
SET holds the NTD modules at project level so that they may be used by any IQ3 controllers within that project. If a
controller uses a particular NTD in its IC Comms then that NTD module will be included in the controller’s strategy file
and configured in the controller when the strategy file is downloaded.
21.4.2 Resolving Differences between the Controller’s NTDs and the Project NTDs
After performing a Compare function in SET on an IQ3 controller (see Pt.1 section 6.4.2), if differences have been found
between the NTD in the IQ3, and the corresponding NTD in the SET project file then the ‘NTD list for this Controller’
dialogue box will pop up. If a multiple compare has been performed (see Pt. 1 section 6.4.3) then the NTD list for each
contrller should be checked by right-clicking on each controller’s strategy page in SET and selecting ICComms/Show
NTD List.
The NTDs for the controller are shown in the top left hand column (Lan-Node), and any mismatch between the Project
file NTD and the IQ3 NTD are indicated by a coloured band; red indicating a difference, and blue indicating that the NTD
is missing from the controller.
If such an NTD is selected, the parameter fields in the bottom half of the dialogue box are populated with the parameters
of the NTD in the controller (uploaded strategy) on the left, an those of the NTD in the project file on the right. The
difference can the be resolved using the arrow buttons to copy the NTD parameters either from project file to controller
strategy or from controller strategy to project file.
If the NTD is copied from project file to controller then the controller needs to be updated either by selecting the NTD
SET dialogue box and selecting the ‘OK and Send to IQ3’s’ button as described above in 21.4.1 or by downloading the
strategy file.
If the NTD is copied from controller to project file then all IQ3s using this NTD need to be updated either by selecting
the NTD SET dialogue box and selecting the ‘OK and Send to IQ3’s’ button as described above in 21.4.1 or by
downloading the appropriate strategy file to each controller.
21.5 Parameters
21.5.1 Attributes
Identifier: (characters, constant)The Identifier is a 30 character label which describes the BACnet device and is used
as controller attribute 1 for inter-controller communications.
Attribute n: There are six other device attributes (attributes 2 to 7) all up to 30 characters long, used as controller attributes
for inter-controller communications.
The Identifier and Attributes 2 to 7 are used singly or together to identify the BACnet device either uniquely or as part
of a group, so that it may receive relevant communications.
For further details see IC Comms, Controller Selection (Pt. 2 section 15.5).
LAN: (analogue, constant) This is the Lan number of the NTD’s Lan. It should be set in the range 1, 4 to 119 excluding
10. It must be unique on the site. All devices on the same Lan should have the same Lan number.
Network Number: (analogue, constant) The BACnet network number of the BACnet device.
MAC address: (characters, constant) The BACnet MAC address of the BACnet device.
Note that the BACnet MAC address has no colon separators (e.g. A5C3A1BABAC0).
IP Address: The IP addressof the BACnet device with which the NTD is to communicate.
UDP Port:The UDP port of the BACnet device with which the NTD is to communicate.
Note that the IP Address and UDP Port are decoded by SET from the BACnet MAC address for use by the user if required.
Vendor Name: The name of the manufacturer of the BACnet device with which the NTD is to communicate.
Model Name: The model name of the BACnet device with which the NTD is to communicate.
Fimware Version: The firmware version of the BACnet device with which the NTD is to communicate.
Name: This is a label for the device and will appear next to its icon in the Device View. It remains in the SET file, and is
not downloaded to the controller.
TYPE
Parameter Web C o mm s Default
SET Low High
page C ode
Controller Parameters
Fixed at 1 (BACnet).
CONST
Type - - Y 1 1 fixed at 1 For future use.
CONST
Identifier R/W R/W D characters blank attribute 1 for inter-controller communications
CONST
Attribute 2 R/W R/W F characters blank
CONST
Attribute 3 R/W R/W G characters blank
min and max The BACnet MAC address of the BACnet device
values differ on the BACnet network
CONST
MAC address R/W** R/W a according to blank Note that the BACnet MAC address has no colon
network type separators (e.g. A5C3A1BABAC0)
characters
SET Associated Parameters
See addresses IP address of BACnet device. Decoded by SET
defined in Pt. 2 from MAC address.
IP Address R** - - blank
section
20.1.4.1
0 UDP port used by BACnet device. Decoded by
SET from MAC address.
UDP Port R** - - 65535 blank
*The Lan number is set up in SET by adding the NTD to a Trend BACnet Lan created in the Project View/Device View
**These parameters are set up by reading from the BACnet device if SET has BACnet comms to the device, and the device
has these parameters available.
TYPE
Parameter Web C o mm s Default
SET Low High
page C ode
SET Associated Parameters
0 xx The name of the manufacturer of the BACnet
Vendor Name R* - - characters blank device
*These parameters are set up by reading from the BACnet device if SET has BACnet comms to the device, and the device
has these parameters available.
characters
Card ID - R I 0 2 0 Board type (option type 1only):
0= Battery backup board (/BBC)
1= Current loop Lan board (/LAN)
2= Serial board (/SER)
Version - R V "issx.yz mmm d 0 Version. For feature options only (i.e. XNC or
yyyy" BACnet).
The OSS module may be applied to heating and/or cooling. The OSS module provides a self-adaptive routine that learns
the characteristics of the building by monitoring and comparing the outside air temperature against the inside air
temperature and also heating and/or cooling medium temperatures. The OSS module then calculates the optimum start
time; this is the time that the heating, (or cooling) system should be switched ON before occupation of the building to
achieve the temperature desired by the start of occupation, and the optimum stop time; the time that the heating ( or
cooling) can be turned off without diverging from comfort conditions until after the end of occupation.
The OSS module can also be used with any item of plant that has similar characteristics to a building (i.e. a domestic
hot water calorifier) provided that the necessary inputs are available for the OSS calculation.
Note that in the OSS module the Warmup period refers to the time between OSS start and OTP start, and the Cooldown
period refers to the time between OSS stop and OTP stop; their natural meaning is obvious for OSS heating mode, but
for OSS cooling mode their meaning is not obvious as the zone will be cooling down during the ‘Warmup’ period, and
heating up during the ‘Cooldown’ period.
The OSS symbol can appear on the strategy diagram but does not need to be sequenced as it operates directly from the
real time clock.
23.1 Symbol
Outside Temperature 0 O O1
OTP t
Inside Temperature 0 I OSS s
NOC n
Heating OSS Setpoint 0 S
W w
Heating Medium Temperature 70 A
OCC o
Cooling OSS Setpoint 0 S C d
MOD m
Cooling Medium Temperature 8 A
Disabled Adaption Inhibit
5 Loss Time Const.
360 Warm Up Limit
0 Cool Down Limit
-1 Htg Start Elevation
-1 Htg Stop Elevation
70 Ave. Htg Medium
10 Htg Gain Time
1 Clg Start Elevation
1 Clg Stop Elevation
8 Ave. Clg Medium
5 Clg Gain Time
Heating sub-module
Cooling sub-module
23.3 SET Dialogue Box
Connectives
23.4 Function
The module can operate in heating, cooling, heating and cooling, or neither (i.e. OTP only) modes. In SET the heating
and cooling modes for an OSS module are both enabled by default, but each mode can be separately disabled by checking
the appropriate ‘Not Used’ box. (The Not Used setting will null down the appropriate OSS Setpoint.)
The following parameters are shown on the module’s main web page and are set up once for use by both heating and
cooling modes:
Outside Temperature
Inside Temperature
Warmup Limit
Cooldown Limit
Loss Time Constant
There is a sub-module for each of the modes, heating and cooling. Each sub-module has the following parameters which
are set up separately for heating and cooling:
OSS Setpoint
Medium Temperature
Start Elevation
Stop Elevation
Gain Time Constant
Average Medium Temperature
If the Warmup Limit is set to zero it will effectively disable optimum start and if the Cooldown Limit is set to zero it
will effectively disable optimum stop.
*Outside Temperature (O): (analogue, source/constant) This should be the value of the outside temperature sensor.
If several outside temperature sensors are fitted, a function (e.g. average) of these values may be used, in which case,
the Outside Temperature input will be connected to the function module output.
*Inside Temperature (I): (analogue, source/constant) This should be the value of the inside temperature sensor. If
several inside temperature sensors are fitted, a function (e.g. minimum) of these values may be used. The Inside
Temperature input will be connected to the function module output.
*(Heating, Cooling) Medium Temperature (A): (analogue, source/constant) A separate medium temperature must be
specified for each of the modes being used, (i.e. heating or cooling). If a measurement of the medium temperature is
available, then this should only be connected to the input else an estimate of the average medium temperature during
the warmup period should be entered as a constant. The Heating Medium Temperature input would normally be
connected to the flow temperature of, for example, hot water feeding radiators. The Cooling Medium Temperature input
would normally be connected to the supply air temperature of an air conditioning system. Note that the OSS module will
calculate the (Heating, Cooling) Average Medium Temperature throughout the warmup period (if the medium temperature
has been entered as a constant, the average medium temperature will equal the medium temperature after the first warm
up).
Note that the previously adapted Average Medium Temperature is used for the OSS calculations, so if the Medium
Temperature is entered as a constant it can also be entered as the Average Medium Temperature to enable the first OSS
calculation to be more accurate.
*(Heating, Cooling) OSS Setpoint (S): (analogue, source/constant) A separate OSS setpoint input must be specified
for each of the modes being used, (i.e. heating or cooling). The mode’s OSS Setpoint should be the setpoint used by
its loops (i.e. heating or cooling) in the zone. If a mode’s OSS Setpoint is nulled, then OSS will be disabled for that mode.
* These inputs can either be sourced from modules’ analogue outputs or set to constant values. If an input is connected
to a module’s analogue output, the output’s details will be shown on the web page.
COOLING OPTIMUM
START TARGET COOLING OPTIMUM
STOP TARGET
COOLING START ELEVATION
COOLING STOP ELEVATION
COOLING
SETPOINT
HEATING
SETPOINT
HEATING START ELEVATION HEATING STOP ELEVATION
(NEGATIVE TO GIVE DROOP)
HEATING OPTIMUM
STOP TARGET
HEATING OPTIMUM
START TARGET
TIME
START OF OCCUPATION END OF OCCUPATION
Heating, Cooling Start Elevation, and Heating, Cooling Stop Elevation inputs can either be sourced from analogue
outputs or set to constant values. If connected to an output the source address will be shown on the web page
These inputs can either be sourced from modules’ analogue outputs or set to constant values. If an input is connected
to a module’s analogue output, the output’s deatils will be shown on the web page.
It may be estimated by using logs of the inside and outside temperature taken with no heating or cooling applied. This
is done from the graph of inside temperature against time by estimating the time where the tangent to the initial cool-
down curve reaches the outside temperature. The time constant is then the difference between this time and the end of
heating.
IN S ID E
T E M P E R A T U R E
A T E N D O F T A N G E N T T O A P P R O X IM A T E IN IT IA L S L O P E
O C C U P A T IO N
R O U G H V A L U E
O F O U T S ID E
T E M P E R A T U R E
T IM E
E S T IM A T E O F L O S S T IM E C O N S T A N T
E N D O F (H O U R S )
H E A T IN G
The Gain Time Constant can be estimated by using logs of the inside temperature and medium temperature during the
period immediately after the heating/cooling has been applied.
This is done from the graph of inside temperature against time by estimating the time where the tangent to the initial
warm-up curve reaches the heating/cooling medium temperature. The time constant is then the difference between this
time and the start of heating.
E S T IM A T E O F G A IN T IM E C O N S T A N T (H O U R S )
M E D IU M
T E M P E R A T U R E
T A N G E N T T O IN IT IA L S L O P E
T R E N D L O G O F IN S ID E S E N S O R
IN S ID E
T E M P E R A T U R E
A T S T A R T O F
O C C U P A T IO N
T IM E
S T A R T O F H E A T IN G
As before,
Loss Time Constant = Inside Temp - Outside Temp
Inside rate of temperature loss in °C/hr
therefore,
Loss time constant = 18-23 = 5 hrs
-1
A P P R O X IM A T E V A L U E
O F O U T S ID E T E M P E R A T U R E
T R E N D L O G O F
IN S ID E S E N S O R
IN S ID E T E M P E R A T U R E
A T E N D O F O C C U P A T IO N
E S T IM A T E O F L O S S T IM E
C O N S T A N T (H O U R S )
E N D O F T IM E
C O O L IN G
The estimate from the graph is done in a similar way to heating, but in this case space warms up after cooling is switched
off, so the time constant is the time between the end of cooling and the time when the tangent to the initial warmup curve
reaches the outside temperature.
O U T S ID E
T E M P E R A T U R E
T R E N D L O G O F IN S ID E S E N S O R
E S T IM A T E O F G A IN T IM E
M E D IU M C O N S T A N T (H O U R S )
T E M P E R A T U R E
S T A R T O F tim e
C O O L IN G
OTP State (OTP): (digital, output) Occupation tiime profile state - between the start of occupation and the end
of occupation. If connected to a module’s digital input, the input’s details will be shown on the web page.
This output is available as a connective in SET (Ont where O=OSS, n=zone number, t=OTP State).
OSS State (OSS): (digital, output) Optimum start stop occupation state - between optimum start time and optimum
stop time (used for switching OSS loops into occupied setpoint). If connected to a module’s digital input, the
input’s details will be shown on the web page. This output is available as a connective in SET (Ons where O=OSS,
n=zone number, s=OSS State).
Non Occupied State (NOC): (digital, output) The state between occupation stop time and optimum start time. If
connected to a module’s digital input, the input’s details will be shown on the web page. This output is available
as a connective in SET (Onn where O=OSS, n=zone number, n=Non Occupied State).
Warmup State (W): (digital, output) The state between optimum start time and the start of occupation. If connected
to a module’s digital input, the input’s details will be shown on the web page. This output is available as a
connective in SET (Onw where O=OSS, n=zone number, w=Warmup State).
Occupied State (OCC): (digital, output) The state between start of occupation and optimum stop time. If connected
to a module’s digital input, the input’s details will be shown on the web page. This output is available as a
connective in SET (Ono where O=OSS, n=zone number, o=Occupied State).
Cooldown Sate (C): (digital, output) The state between optimum stop time and the end of occupation time. If
connected to a module’s digital input, the input’s details will be shown on the web page. This output is available
as a connective in SET (Onc where O=OSS, n=zone number, c=Cooldown State).
Mode (MOD): (digital, output) This output indicates the mode in which the OSS module has decided it is operating.
If connected to a module’s digital input, the input’s details will be shown on the web page. It is set to status 0 for
heating OSS calculations and status 1 for cooling OSS calculations. This output is available as a connective in
SET (Onm where O=OSS, n=zone number, m=Mode).
These outputs are available for use within all schedules allocated to this zone without making external connections, but
any of the outputs can be used where required in the strategy (e.g. to switch loop setpoints).
OSS MODULE OTP OSS OTP OSS OTP
OUTPUT STATE START START STOP STOP
TIMING STOP
OTP
OSS
NOC
W
OCC
C
STATE
TIME
The State parameter shown on the OSS overview page shows whether the OSS module is currently calling for heating
or cooling.
State: This will indicate either Heating or Cooling from between the OSS Start and OSS Stop; outside this range it will
be in a Passive state.
WATER FLOW S2
3 A
A P BOILER
S1 DEMAND
INSIDE AIR P O
1
Knob 1
OCC SP
F 70 L2
O F1 TO DRIVERS
L1 U
NOC SP RSCL FR E 5
Knob 2 U S
S
ZONE 1
OSS
S3
OUTSIDE AIR
2
The building cools down at 1.2 deg C/hour when the inside temperature is at 20 deg C and outside temperature is at 5 deg C.
FLOW TEMP
S6
3 P
OCC SP BOILER DEMAND
Knob 1
O
L2
NOC SP
Knob 2 U
S
ZONE 2
OSS
S5 RAISE
1 P VALVE
DEMAND D4
Knob 3 O RLM ZONE
L3 4 1 VALVE
Knob 4 U LOWER
Raise Lower
OCCUPATION S
SET POINTS End
ZONE 2
OSS
S1 OUTSIDE AIR
2
Heating:
Heating Medium Temperature can be connected to Knob 1 since this sets the heating medium temperature during
occupation.
Heating OSS Setpoint is connected to Knob 3
Heating Start Elevation = -2 deg C
Heating Stop Elevation = -1 deg C
Note that estimates for Loss Time Constant and Heating Gain Time Constant will have to be entered.
Cooling:
Cooling is provided in three steps; full fresh air, cooling stage 1, cooling stage 2. However, in order to save energy when
fresh air alone is sufficient for cooling, the compressor is inhibited if the outside air temperature is less than the cooling
occupation setpoint.
A
INSIDE S5
AIR
1 P
Knob 5
OCC SP D1 FRESH
O SRM
L2 L 1 AIR
1
FAN
Knob 6 U
NOC SP
BINARY HYST
S
ZONE 2
OSS
D2
L 2 SRM COOLING
2 STAGE 1
F1 BINARY HYST
E
D
0 F
S1 GATE
OUTSIDE E F2
AIR 2 D3
OCC SP OUTSIDE AIR TEMP SRM
Knob 5 F COMPARATOR
L 3 COOLING
<COOLING SET POINT
3 STAGE 2
BINARY HYST
To OSS Clamp input
Cooling:
Cooling Medium Temperature sensor is not available so it is set to constant with an estimated value of the cooling
medium temperature (5 deg C).
Cooling Setpoint is connected to Knob 5
Cooling Start Elevation = 0 deg C
Cooling Stop Elevation = 3 deg C
Since the cooling mode uses the same Loss Time Constant as the heating mode it does not need to be entered again, but
a separate Cooling Gain Time Constant must be entered.
Note that the compressor is inhibited if the outside air is less than the cooling setpoint, so under these conditions the
OSS module’s adaption must be stopped. This can be done by connecting the F2 comparator output to an OSS clamp
as described in section 23.7 below.
The best method to use when setting up the OSS module for electric heating is to set the Heating Medium Temperature
to 0 and the Heating Average Medium Temperature to a comparatively high value, i.e. 100 deg C. The Heating Gain
Time Constant can be estimated as described in section 23.4.4.2 above.
The OSS module can exist in one of the three states as shown by the State parameter on the web page.
We can analyse these modes by starting in a zone non-occupied state with the OSS module passive.
If the next time is tomorrow it will reference it by adding 24 hours i.e. 32:00 hours is 8 am tomorrow. The time is
referenced to the previous midnight.
The module decides whether it is in heating mode or cooling mode. It will only be in cooling mode if the Cooling OSS
Setpoint is non-zero and the Inside Temperature is greater than the cooling target (i.e. Cooling OSS setpoint + Cooling
Start Elevation).
It will calculate the ‘warm-up’ time by measuring outside temperature, inside temperature, the medium temperature at
start of warm-up (or estimate if medium temperature is zero), and using the last adapted gain coefficient and average
medium temperature to calculate the warm-up time to the setpoint + start elevation.
It will limit this with the Warmup Limit and then the optimum start is the OTP start less the warm-up time.
During non-occupation the Optimum On Time shown is the next optimum start time and the Optimum Off Time is the
last optimum stop time.
23.6.2 Warm-Up
As soon as the current time equals the optimum start time it will change into the warm-up phase. During this phase, the
OSS module will adapt the appropriate Gain Time Constant. It will adapt by using:-
New time constant = 0.8 x old time constant + 0.2 x new estimate.
This adapts the values smoothly and holds some historical information i.e. the trend in weather or seasonal variation.
The gain time constant will not adapt after a period of 4 hours following start of warm up.
During the warm-up the Optimum On Time shown is the last optimum start and the Optimum Off Time is the last
optimum stop.
23.6.3 Occupied
During occupation the OSS module will calculate the optimum stop time. It does this by looking to the next OTP time.
This could be during the day ahead as for the start time.
At any time it will decide whether it is in heating or cooling mode and calculate the cool-down time accordingly. It
performs this by measuring the inside temperature, the outside temperature, and using yesterday’s adapted loss time
constant to calculate the cool-down time to occupied setpoint + stop elevation. It will limit the cool-down time to the
Cooldown Limit.
At any time the optimum stop time is the latest of OTP time less heating cool-down time or OTP less cooling cool-down
time.
During the occupation phase the Optimum On Time shown is the last optimum start and the Optimum Off Time is
the next optimum stop as calculated above.
23.6.4 Cool-down
During this phase, if the predicted inside temperature at the end of occupation is more than 1 deg C below the optimum
stop target (1 deg C above for cooling) then it will revert to OTP times.
The loss time constant will use the same method of adaption as the gain time constant i.e. new time constant = 0.8 x old
time constant + 0.2 x new estimate.
During cool-down the Optimum On Time shown is the last optimum start and the Optimum Off Time is the last
optimum stop.
One cause of this is if either the Outside Temperature sensor or the Inside Temperature sensor has alarm bits set, or if
either sensor is removed.
The alarm bits can be used to freeze the sensor value during failure and stop OSS adapting. This method of freezing the
sensor is known as an OSS clamp, and is shown in the strategy below.
F F
D
INSIDE S1
E
SENSOR 1 GATE INSIDE SENSOR VALUES TO OSS
This can also be done if an override such as a loop manual override or a caretaker override overrides the OSS time action.
In these cases the override bit can be used directly as the OSS clamp.
If the override or sensor fail is shorter than the period over which the OSS Module adapts, then it will start to adapt during
the remaining period as the sensor changes.
The logic clamp should thus be held for 4 hours at the start of warm-up and 3 hours at start of non occupation (because,
as stated in section 23.6 above, the Gain Time Constant does not adapt after a period of 4 hours, and the Loss Time
Constant does not adapt after a period of 3 hours). Additional logic is required to do this.
We can create these time periods by delaying the NON OCC rising edge for 3 hours and the NON OCC falling edge
(i.e. start of warm-up) for 4 hours e.g. by using a logic module with an on delay and an off delay..
1
N O N O C C (F )
0
3 H R S
N O N O C C D E L A Y E D (G )
4 H R S
3 H R P E R IO D (F g )
4 H R P E R IO D (G f)
B O T H P E R IO D S (F g + G f)
T IM E
We call the NON-OCC bit (F) and the delayed NON OCC bit (G). The three hour period is when F is there, and G is
not, F AND NOT G (Fg), and the four hour period is when G is there and F is not, G AND NOT F (Gf). To operate the
logic clamp the correct condition must be used, that is, Fg + Gf which is the last time graph above.
If the fault/override occurs during periods we want the gate to clamp, and we want it to stay clamped until the end of
that period.
(F g + G f)
E F g + E G f
H
Now we want it to stay clamped until the end of the period as shown by the graph H above. This can be done by feeding
back the output so that we hold the clamp on for the rest of the period:
i.e. for H AND (Fg + Gf)
= H(Fg + Gf)
= HFg + HGf
Fault or Override
E G
EFg+
Non Occupied State F EGf+
OSS CLAMP
D
HFg+
G HGf
H COMB
ON=3HRS
OFF=4HRS
TIMER
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
Page: (analogue, constant) SET file strategy page number on which module appears.
In IQ2 the heating mode is disabled by setting the Heating OSS Setpoint to zero, whereas in IQ3 it’s disabled by nulling
the OSS Setpoint (similar for cooling mode).
TYPE
co d e
SET Web Low High
page
Controller Parameters
State - R S 0 2 0 The current state of operation of the OSS
STATUS
module:
0=Passive
1=Heating
2=Cooling
Inside Temp R/W R/W* I 0 1 0 The value of the inside temperature. Can be
connected to an analogue output.
Warmup Limit R/W R/W* W 0 1439 0 The maximum limit of the warm up time. Can
(minutes) be connected to an analogue output.
Cooldown Limit R/W R/W* D 0 1439 0 The maximum limit of the cool down time.
(minutes) Can be connected to an analogue output.
Loss Time Constant R/W R/W* L 0 100 0 The Loss Time Constant of the system being
(hours) optimised. Adapted by OSS. Can be
connected to an analogue output.
Heating OSS R/W R/W* h1(S) -1020 +1020 0 The setpoint of the main control loop being
SOURCE/CONST
Heating Medium R/W R/W* h1(A) -1020 +1020 0 The temperature of the heating medium.Set
Temperature as a constantvalue if heating medium sensor
not available. Can be connected to an
analogue output.
Heating Start R/W R/W* h1(T) -100 +100 0 Amount by which temperature can differ from
Elevation setpoint at end of warmup. Set negative for
heating (i.e. droop). Can be connected to an
analogue output.
Heating Stop R/W R/W* h1(P) -100 +100 0 Amount by which temperature can differ from
Elevation setpoint at begining of cool down. Set
negative for heating (i.e. droop). Can be
connected to an analogue output.
Heating Gain Time R/W R/W h1(G) -100 +100 0 The Heating Gain Time Constant of the
CONST
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Cooling OSS R/W R/W* c1(S) -1020 +1020 0 The setpoint of the main control loop being
SOURCE/CONST
Setpoint switched into occupation by the OSS state
OSS Heating output. If set to null, it stops OSS cooling
Module mode operating. Can be connected to an
(SET: Cooling analogue output.
Setpoint)
OTP State R R/W t 0 1 0 The occupied state derived from the zone
start stop times. Can be connected to a
digital input
OSS State R R/W s 0 1 0 The OSS occupied state between start of
warmup and start of cooldown. Can be
connected to a digital input
Non Occupied State R R/W n 0 1 0 The non occupied state between OTP stop
and OSS start. Can be connected to a digital
input
Warmup State R R/W w 0 1 0 The warmup state between OSS start and
OTP start. Can be connected to a digital
input
Occupied State R R/W o 0 1 0 The occupied state between OTP start and
OSS stop. Can be connected to a digital
input
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Optimum Off Time - R F 00:00 48:00 00:00 The current calculated optimum off time
Label R/W R/W $ 0 30 null The module identifier used on strategy pages
CONST
and web pages
characters
P age R/W R/W p 0 255 0 CONST Number of page containing module in SET
file
There are a few parameters kept by SET, but only the label is sent to the controller in the strategy file. This is so that
the strategy pages may be backwards engineered (see Pt. 1 section 6.4.1) from the controller complete with their page
labels. The page module does not appear on the strategy page and is not sequenced.
Instead the page can be accessed using the URL or IP address for the controller followed by ‘p.htm’.
e.g. if the modules list page is :165.195.161.61/modules.htm,
then the page module’s list is :165.195.161.61/p.htm
24.3 Parameters
24.3.1 Controller Parameters
Label (SET: Description Line 1): This is the first line which appears in the Page Details box on the strategy page in SET.
It is sent to the controller as part of the strategy file, and can be retrieved from the controller
Label
Parent: This parameter is not used; for future use.
Details: This is a free field for the strategy creator to write some notes to aid understanding of the strategy.
Description Line 2: The second line of the description which appears in the Page Details box on the strategy page in
SET.
Last Modified, Date, Time, and By: Details of the last modification
TYPE
co d e
SET Web Low High
page
Controller Parameters
CONST
Both Triggered and Periodic types have an option to generate a Log Full output and cease logging, until the plot buffer
is cleared (Stop When Full option).
For BTL (BACNet Testing Laboratory) compliance only the Periodic plots should be used set up as per default (see later).
25.1 Symbols
Synchronised Plot
Sensor 2
S2V S P1
SYNC
15 Min Period
1000 Records
0 Notify Threshold
0 Log Level Group
Triggered Plot
Sensor 2
S2V S P2
0 G O
1 E TRIGGERED
1000 Records
0 Notify Threshold
0 Log Level Group
Disabled Stop When Full
Log Full
Periodic Plot
0 I
1 E PERIODIC
1000 Records
0 Notify Threshold
0 Log Level Group
Disabled Stop When Full
Log Full
Connectives
The plot module keeps a marker on its last record and when the supervisor accesses the module, the values are sent from
this marker forward, enabling the supervisor to construct a graph of the values in chronological order.
The plot module appears on the strategy page and is not sequenced as it operates directly from the real time clock.
S
Plot Channel
Rolling Records
The value of the source is recorded at the start of the sequence table cycle if the equivalent time module timing pulse
is set (see pt. 2 section 32.8.1).
Synchronised logging is performed at 10 different periods (1 s, 1 m, 5 m, 10 m, 15 m, 20 m, 30 m, 1 h, 6h, and 24 h). The
interval can be specified from any of those listed in the table below. The duration below is calculated for the maximum
of 1000 records.
Period Duration
1s 16 m 40 s
1m 16 h 40 m
5m 3 days 11 h 20 m
10 m 6 days 22 h 40 m
15 m 10 days 10 h
20 m 13 days 21 h 20 m
30 m 20 days 20 h
1h 41 days 16 h
6h 250 days
24 h 1000 days
The normal plot used for system monitoring is the 15 minute plot, the faster plots are used for fast moving systems or
control loop tuning, and the hourly plot for such functions as energy targeting or degree days.
Plots are also referred to as logs, hence logging. In supervisors it is sometimes referred to as ‘graphing’.
Each of the plot modules can be set up to log a given connectable output at one of the periods.
There is nothing to stop the same output being logged on different plot modules at different periods; later supervisors
enable the plot of an output to be selected from a table of plots at the different periods, so that graphs of the same output
at different periods can be seen.
A synchronised plot module can give Threshold Notification to supervisors (see section 25.6 below).
When the controller power is restored after power failure, the plot records which have been missed are filled in with the
last value taken prior to the power failure. This results in a flat response for the period of the power failure. The status
of each missed record is set to invalid (see Status bits, section 25.7 below).
Digital Input 5
I5 S
0 m
0 c
EXTERNAL
Disabled State Alarm
Hours Run
Starts
In the above strategy the meter pulse cumulative count is monitored by a sensor (S4) to make it easily available to
supervisors and displays. When the maximum demand occurs the triggered plot (P3) is triggered to take a reading of the
sensor, and the trigger output (P3O) then resets the counter ready for the next maximum demand period.
Triggered plots are useful in strategies because they allow plots to occur asynchronously to the time pulses, for example:
On status change (e.g. for recording digital values that change infrequently)
On change of value (e.g. a user adjustable setpoint).
Because triggered plot records are not taken regularly (as for synchronised plots), each record also contains a time stamp
(time and date e.g. 2007-12-18T09:28:31).
The plot has a defined number of records, and a triggered plot can either wrap (as for synchronised plots) or stop when
full as dictated by the ‘Stop When Full’ parameter. If the ‘Stop When Full’ parameter is set true, then the logging will
stop when the defined number of records (minus 1) is reached, and the Log Full output bit will be set true (see Stop When
Full section 25.5 below).
The Log Enable input can be used to start and stop the triggered logging. This is a connectable input. When the logging
is enabled or disabled, a record is kept in the plot with the appropriate status and time stamp.
A triggered plot module can give Threshold Notification to supervisors (see 25.6 below).
A trigger that occurs less than one second after the previous trigger will be ignored.
If a triggered input is connected to a time pulse, then it is effectively a synchronised plot, but also has ‘Stop When Full’
functionality. SET facilitates the connection to a timing pulse by providing a drop down list of timing pulse outputs for
the trigger parameter
Because periodic plot records are not taken regularly (as for synchronised plots), each record also contains a time stamp
(time and date e.g. 2007-12-18T09:28:31).
The plot has a defined number of records, and a periodic plot can either wrap (as for synchronised plots) or stop when
full as dictated by the ‘Stop When Full’ parameter. If the ‘Stop When Full’ parameter is set true, then the logging will
stop when the defined number of records (minus 1) is reached, and the Log Full output bit will be set true (see Stop When
Full section 25.5 below).
A periodic plot module can give Threshold Notification to supervisors (see 25.6 below).
Note that the Log Full output will be set true whenever the Record Count = Number of Records, regardless of the setting
of the ‘Stop When Full’ parameter.
This clearing of the Log Enable input is a requirement of BACnet, and it will not operate if the input is connected to an
output; for BTL compliance the Log Enable input must be unconnected.
Value V defined by
Type
Type Y Enum 0 10
Status S Bitstring 00000000 11111111
Record E Integer 0 232-1
Number
Timestamp T Timestamp yyyy-mm-ddThh:mm:ss
Time Offset O 0 3153600
(1 year)
supervisors and displays and on a graph webpage. The data can also be accessed by text comms or BACnet comms.
The plot record structure is shown in the table below:
Value: The data type of the value is determined by the Type (Y) parameter as defined below.
Type: This defines the type of record according to the following enumerations:
0, Log Status: This type of record is used to record the plot being disabled, enabled, or being cleared by a write
of zero to the record count. The Value parameter is set as below:
Value = 0: Plot being disabled
Value = 1: Plot being re-enabled
Value = 2: Plot record count being cleared
1, Digital Value: Plot is of a digital value, 0 or 1.
2, Analogue Value: Plot is of an analogue value
9, Time-change: Plot value contains the time change as an integral number of seconds (positive or negative)
Note that the other type enumerations (3 to 7, 10) are not currently used.
Note that for synchronised plots the Type is always analogue value (type 2).
Module type Bi t 7 Bi t 6 Bi t 5 Bi t 4 Bi t 3 Bi t 2 Bi t 1 Bi t 0
Digital input Disabled Overridden Invalid Data Daylight saving D i gi n
Sensor Disabled Overridden Invalid Data Daylight saving Read Out of Low High
Limits
Loop Disabled Invalid Data Daylight saving Default P V F ai l SP
O/P Deviation
Driver Disabled Overridden Invalid Data Daylight saving HOA Maintenace Readback
Override
Others Disabled Invalid Data Daylight saving Read Out of Low High
Limits
Bit 7, Disabled: This bit is set whenever the module sourcing the value being sampled is disabled (i.e. by the module’s
Disable Input).
Bit 6, Overridden: This bit is set when the input/output modules (sensor, digital input, driver) are being overridden
by using their Override Output and Override Value/Status parameters.
Bit 5, Invalid Data: This bit is set to indicate that this value was backfilled to cover an interruption in power supply
(see 25.x below). This only applies to synchronised plots.
Bit 4, Daylight Saving: This bit is set to indicate that the time module Daylight Savings Applied parameter was set
at the time this value was taken.
Bit 3 to Bit 0, Module Alarm Bits: Bits 3 to 0 reflect the source module’s alarm status. The meaning of these bits
varies with module type.
The BACnet Log_Buffer property includes Status_Flags which has the four flags:
IN_ALARM, which is true if any of the source module alarm bits are set (bits 0 to 3)
FAULT, which is true if Read, Out of Limits, or Maintenance status bits are set
OVERRIDDEN, Which is true if Overridden (Bit 6) or HOA Override bit is set
OUT_OF_SERVICE, which is true if Disabled (Bit 7) is set.
Record Number: This is the value of the total record count when the record was stored. This provides a fixed index for
the record where the times may not run in sequence due to time changes or daylight savings.
Timestamp: This is the time the record was taken in format yy-mm-ddThh:mm:ss. It is stored for triggered and periodic
plots, but not for synchronised plots. If the timestamp of a synchronised plot is requested it is generated by using the
most recent time and backcalculating using the fixed period, and daylight savings status and Time module ‘Daylight
Hours Change’ (Change By) parameter.
Time Offset: The offset in seconds from time of last record. Not recorded for synchronised plots, but generated when
requested.
Using the precision protocol, each value is sent as 6 ASCII characters (e.g. 999999, 9999.9, .00001).
Using the compact protocol values are sent as a percentage of maximum value minus the minimum value (i.e. maximum
error of 1%); these integer percentage values are each coded and communicated as one ASCII character, so can be sent
approximately 6 times faster than using the precision protocol.
Use of the precision protocol is not supported for sensor modules above sensor 99. Use of the compact protocol is not
supported for sensor modules above sensor 256. Plots for sensors above 99 cannot be viewed from 963, and sensors
above 256 can only be viewed from the IQ3 webpages.
Single precision is as for the traditional compact protocol. The values are sent as a percentage of maximum value minus
the minimum value (i.e. maximum error of 1%); these integer percentage values are each coded and communicated as one
ASCII character.
The values are sent back with the start time and period so that the time points are calculated in the supervisor. However,
the start time is in seconds so that the timing for the new 1 second compact plot is accurate and joining subsequent plots
together is OK.
Double precision plots use the same algorithm as for the single precision plots, but use two ASCII characters to code
the percentage value and thus have a maximum error of 0.01% (i.e. 0 to 9999). They take approximately twice the time to
communicate.
The new text comms protocols have a selectable number of decimal places (0 to 9). The 963 v3.1 allows the precision to
be selected by a setting in the INI file. It defaults to 2 decimal places.
Increasing the number of decimal places will increase the number of digits communicated, and hence slow down the
retrieval of plot data by the supervisor.
Text comms enable the supervisor/display to access all the data in the plot record; the supervisor can select the data
required for particular types of display. For synchronised plots, timestamps and time offsets are generated when they
are requested.
25.8.4 Graphs
The graph displays give a graph of the values in the plot module, and a spot value which can be moved along the graph
trace. As the point is moved along the graph its point value is displayed. A section of graph can be enlarged by the zoom
feature. A list of the values used to create the graph can also be seen, and in some supervisors can be exported as a text
file (e.g. for use by spreadsheet software). These graph features can be seen in Pt. 1 section 9.4.
In web pages the graph can be seen by clicking on the icon in either the plot module or the source module summary
pages. If a module’s output is plotted by more than one plot module, a line is added to the module overview page for
each plot, so each plot has a separate icon (see sensor overview below).
The maximum number of plot modules is limited at 500 for all versions of IQ3 , so in the case of IQ3xact the maximum would
be 500 x 40 point synchronised plots.
(See also Flexible Module Numbers, Pt. 1 section 5.8, and Plot Memory Size, Plot Memory Used in Address module - Pt.
2 section 2.3.8).
The effect of time synchronisation is dealt with differently for Synchronised, Triggered, and Periodic plots.
e.g. A 1 minute plot has been running for several days and the time is now 14:00. The time is to be re-synchronised to
14:30.
If the original graph ran from 12:30 to 14:00, the new graph will run from 13:00 to 14:30. The graph's first sample time
has been moved by 30 minutes to correct the graph to current time.
The effects on the various plot types and protocols is similar to the effects of time synchronisation as described above.
However the daylight savings status is saved for all plot types, so if using the new text comms protocol for synchronised
logs, the timestamps will be generated by the IQ3 taking into account the daylight saving information. This may result
in two records having the same timestamp (e.g. if the time change sets the time back by an hour).
The supervisor or display has access to the daylight saving status and the Time module ‘Daylight Hours Change’
(Change By) parameter and will be able to use these (if required) to resolve the record times.
25.12 Parameters
25.12.1 Input/Output Parameters
Source: (analogue/digital, source/constant) This is the value or status of the module output being logged. This input
can either be sourced from a module output or set to a constant value. If connected to a module’s output, the output’s
details will be shown on the web page.
Trigger Input: (digital, source/constant) The state of the plot trigger for triggered plots. The triggered plot will record
the source value on the rising edge of the trigger. This input can either be sourced from a digital output or set to a constant
value (0 or 1). If connected to a digital output, the output’s details will be shown on the web page. SET facilitates the
connection to a timing pulse by providing a drop down list of timing pulse outputs for the trigger parameter
Log Enable: (digital, source/constant) The state of the log enable. It is only available on triggered or periodic plots. The
plot will stop recording samples when the Log Enable is et to zero, and start recording when the Log Enable is set to one.
This input can either be sourced from a digital output or set to a constant value (0 or 1). If connected to a digital output,
the output’s details will be shown on the web page. For a BACnet compliant triggered plot, the Log Enable input should
not be connected to an output.
Interval: (analogue, source/constant) The interval in seconds between one sample and the next. It is only available on
periodic plots. This input can either be sourced from an analogue output or set to a constant value. If connected to an
analogue output, the output’s details will be shown on the web page.
Trigger Output: (digital, output) The trigger input passed to the output when the plot module is serviced. It is only
available on triggered plots. This ensures that the record has been taken before any ‘downstream’ modules act on the
trigger state. If connected to a module’s digital input the input’s details will be shown on the web page.
The output is shown as a connective in SET (PnO, where P=plot module, n=plot module number, O=output).
Log Full: (digital, output) This output indicates that the Record Count equals the Number of Records. It is only available
on triggered or periodic plots.
The output is shown as a connective in SET (Pn, where P=plot module, n=plot module number, F=Log Full).
Number Of Records: (analogue, constant) This is the maximum number of records for this plot module. It can be set in
the range 0 to 1000. Once the maximum record number is reached, the earliest record is overwritten when the next value
is recorded (i.e. a rolling record). However for triggered and periodic plots, the plot can be stopped if the ‘Stop When
Full’ parameter is set to ‘yes’.
Period: (analogue, constant) This is the time between records of the source’s value for synchronised plots only. It can
be set in the range 1 s, 1 m, 5 m, 10 m, 15 m, 20 m, 30 m, 1 h, 6h, and 24 h.
Stop When Full: (digital, constant) The parameter decides whether the plot will wrap round, or stop when the Record
Count equals the Number of Records (minus 1). It is only available on triggered or periodic plots. If ‘Stop When Full’
is set to one, the plot module will stop, but if it is set to zero, the earliest record is overwritten when the next value is
recorded.
Record Count: (analogue, status) This is the number of records recorded so far. This will start at zero and increase up
to the Number Of Records.
Total Record Count: (analogue, status) This is a unique number to identify the record. The number will start at zero after
a strategy download and will increase up to 232-1, when it will wrap back to one.
Time of Last Record: (characters, status) This is the timestamp for the last record taken (time and date e.g.2007-12-
18T09:28:31).
Notification Threshold (SET: Notify Threshold): (analogue, constant) This is the number of records since the last
notification at which the next notification (BBUF alarm) is due.
Records Since Last Notification: (analogue, status) This is the number of records taken since the last notification was
sent. When the number Records Since Last Notification equals the Notification Threshold, the BBUF alarm will be sent.
When the next record is taken, the Records Since Last Notification will be set to one.
Last Notify Record: (analogue, status) This is the value of the Total Record Count when the last BBUF alarm was sent.
Time of Last Notification: (characters, status) This is the timestamp for the last notification sent (time and date e.g.2007-
12-18T09:28:31).
Alarm Group (SET: Log Level Group): (analogue, constant) This is the alarm group to which the BBUF alarm will be sent
Page: (analogue, constant) SET file strategy page number on which module appears.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Trigger Output R/W R O 0 1 0 For triggered plots only. The state of the
OUTPUT
SET) 2=triggered
3=periodic
Only Periodic plots are BTL compliant
Period R/W R/W P 0 9 0 For synchronised plots only. The interval
between records:
0=1 hour
1=15 minutes
2=24 hours
CONST
3=1 minute
4=5 minutes
6=20 minutes
7=30 minutes
8=6 hours
9=1second
Note the 1 s compact plot timing inaccuracy
(see 25.4.2 above).
Number of Records R/W R/W N 0 1000 1000 The maximum number of records for this plot.
CONST
Stop When Full R/W R/W W 0 255 0 For triggered and periodic plots only. Defines
CONST
er of
Recor-
ds
* This source/constant parameter cannot be changed via the web page if it is set as a source.
STATUS
Time of Last Record - R T date&time; 0 The date and time of the last record taken.
STATUS
yyyy-mm-dd&
Thh:mm:ss
Notification R/W R/W n 0 232-1 0 The number of records since the last
STATUS
Threshold notification that buffer ready alarm (BBUF)
(SET: Notify will be sent
Threshold)
Records Since Last - R r 0 232-1 0 The number of records since the last
STATUS
Notification notification was sent
Last Notify Record - R l 0 232-1 0 The value of the Total Record Count when the
STATUS
(lower last BBUF alarm was sent
ca se L )
Time of Last - R b date&time; 0 The date and time the last BBUF alarm was
STATUS
Notification yyyy-mm-dd& sent
Thh:mm:ss
Alarm Group R/W R/W g 0 500 0 The alarm group module to which the BBUF
CONST
Label R/W R/W $ 0 30 null The module identifier used on strategy pages
characters and web pages
file
Plot Record Parameters (not available in SET or webpage - accessable by text comms, BACnet comms and as graphs)
STATUS
(1
year)
seconds
26.2 Parameters
Filename: (characters, status) Set up when a strategy file is transferred to or from the controller. It has standard filename
format Lyyynxxx.IQ3 where yyy is Lan number, xxx is outstation address.
Program State: (analogue, status) This shows the current state of the strategy file. The way in which the IQ3 uses the
strategy file is described in Pt. 1 section 6.5.:
Running (normal state)
No Strategy
Loading
Failed to Load (used on load failure if none of the specific failures below apply)
Primed for Command
Stopped
No File
File not Found
Bad File (checksum or length error)
File Version (invalid header)
brIQs exceeded (strategy too big)
External IO Exceeded
Onboard IO Exceeded
Feature Error (trying to load a BACnet strategy into a non-BACnet controller, or an XNC strategy into a non-XNC
controller).
Archive State: (analogue, status) Indicates whether the last archive to Flash memory of the running strategy file was
successful. The way in which the IQ3 archives strategy changes is described in Pt. 1 section 6.5.4. Archive states include:
Last Archive Successful (normal state)
Never archived (i.e. corresponds to Program State of No Strategy)
Archive Primed
Archive Active
Last Archive was bad
Progress Percent: (analogue, status) Percentage of way through file download process; 100% means file is fully loaded
which should be quickly followed by Program State/Running.
Last Strategy Error (analogue, status) This parameter is set up if there is a strategy download failure and describes which
module caused the strategy to fail (e.g. D1 - for Driver 1).
TYPE
Parameter co d e
SET Web Low High
page
Controller Parameters
Filename - R F Lyyyxnnn.IQ3 0 The filename of the current strategy file
STATUS
yyy=Lan number
xxx=outstation
address
Program State - R P 0 12 0 The current state of the strategy file:
0=No Strategy
1=Loading
2=Running
3=Failed to Load
4=Primed for Command
STATUS
5=Stopped
6=No File
7=File not Found
8=Bad File
9=File Version
10=brIQs Exceeded
11=External IO Exceeded
12=Onboard IO Exceeded
13= Feature Error
Archive State - R S 0 30 null The currentsituation with regard to the
STATUS
The schedule module contains a time based selector switch where the source address in current use depends on the time
input from the OSS module of the selected zone.
The schedule module appears on the strategy page and can be sequence or event driven.
27.1 Symbol
Manual Select 0 A H1
Non-Occupied Value 0 N
Warmup Value 0 W
D
Occupied Value 0 O
Cooldown Value 0 L
Manual Level 0 M
SCHED.
1 Type
0 Zone
0 Start Deviation
0 Stop Deviation
Connective
27.4 Function
27.4.1 Type
Type: (analogue, constant) There are two types of schedule:-
1) Occupation Time Profile (OTP). This type of schedule is controlled by occupation times set by the time
zone module. This allows up to ten sets of start and stop times for each day of the week.
2) Optimum Start/Stop (OSS). This type of schedule is controlled by the optimum start and stop times
calculated by the OSS module.
The schedule State will be in Non-Occupied if the time is between schedule stop time and schedule start time, otherwise
it will be Occupied.
For OTP the Warmup and Cooldown Values are greyed out in SET.
Non-Occupied - When time is between Scheduled OTP stop and Scheduled OSS start
Warmup - When time is between Scheduled OSS start and Scheduled OTP start
Occupied - When time is between Scheduled OTP start and Scheduled OSS stop
Cooldown - When time is between Scheduled OSS stop and Scheduled OTP stop
s ta rt s ta rt s to p s to p
d e v ia tio n d e v ia tio n d e v ia tio n d e v ia tio n
Z o n e O S S O T P O S S O T P tim e
T im e s S T A R T S T A R T S T O P S T O P
S c h e d u le d S c h e d u le d S c h e d u le d S c h e d u le d S c h e d u le d
N O T O C C U P IE D W A R M -U P O C C U P IE D C O O L D O W N N O T O C C U P IE D
S c h e d u le d S c h e d u le d S c h e d u le d S c h e d u le d S c h e d u le d
T im e s O S S ta rt O T P S ta rt O S S S to p O T P S to p
Start and Stop Deviations: (analogue, source/constant) These times are set in minutes, and may be either positive or
negative. Negative deviations enable scheduled times to be in advance of zone times.
The Start and Stop Deviations can either be sourced from modules’ analogue outputs or set to constant values. If
connected to a module’s analogue output, the output’s details will be shown on the web page.
Occupied Value, Warmup Value, Cooldown Value, and Non-occupied Value: (analogue, source/constant) These inputs
are connected to the output during the appropriate schedule state. These inputs can either be sourced from moduels’
analogue outputs or set to constant values. If connected to a module’s analogue output the output’s details will be shown
on the web page.
Output: (analogue, output) If connected to a module’s analogue input, the input’s details will be shown on the web page.
This is available as a connective in SET (HnD, where H=schedule, n=schedule number, D=output)
27.4.4 Manual
Manual Select: (digital, source/constant) If the manual select input is set to one (manual), then the schedule will be forced
into manual and the output level will be set to be the same as the manual level input. If manual select input is set to zero,
the schedule will run in automatic mode as described in section 27.4.1 above.
The Manual Select input can either be sourced from module’s digital output or set to a constant value (0 or 1). If connected
to a module’s digital output, the output’s details will be shown on the web page.
Manual Level: (analogue, source/constant). The level that is connected to the output when the schedule is set to manual.
The Manual Level input can either be sourced from module’s analogue output or set to a constant value. If connected
to a module’s analogue output, the output’s details will be shown on the web page.
Page: (analogue, constant) SET file strategy page number on which module appears.
TYPE
co d e
SET Web Low High
page
Controller Parameters
CONST CONST
Type R/W R Y 1 2 2 Schedule module type:
1=OSS
2=OTP (default)
OSS/OTP R/W R/W Z 1 100 0 The Zone or OSS module used by this
Connection schedule
(SET: Zone)
State - R S 1 4 0 The current state of the schedule module.
STATUS
1=Occupied
2=Warmup
3=Cooldown
4=Non-occupied
SOURCE/CONST
Start Deviation R/W R/W* T -1440 +1440 0 The difference between the start time from
the OSS or zone module, and the start time
used by the schedule. If the start deviation is
minutes
positive, the schedule start is delayed. Can
be connected to an analogue output.
Stop Deviation R/W R/W* P -1440 +1440 0 The difference between the stop time from
SOURCE/CONST
Manual Select R/W R/W* A 0 1 0 If set to one the output will be driven to the
manual level. Can be connected to a digital
output.
Manual Level R/W R/W* M -1020 +1020 0 The output level used when the Manual
Select input is set to one. Can be connected
to an analogue output.
Occupied Value R/W R/W* O -1020 +1020 0 The output level used during occupation
(SET: Occupation Can be connected to an analogue output.
input)
Warmup Value R/W R/W* W -1020 +1020 0 The output level used during the warmup
(SET: Warm Up phase (OSS only). Can be connected to an
input) analogue output.
Cooldown Value R/W R/W* L -1020 +1020 0 The output level used during the cooldown
(SET: Cool Down phase (OSS only). Can be connected to an
input) analogue input.
Non-Occupied Value R/W R/W* N -1020 +1020 0 The output level used during the non-
(SET: Non- occupied phase (OSS only). Can be
Occupation input) connected to an analogue input.
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Controller Parameters
OUTPUT
Output R/W R/W* D -1020 +1020 0 The module analogue output. Can be
connected to an analogue input.
Sequence Step R/W R @ 0 500 Specifically The sequence step at which the schedule is
CONST
set up by serviced. If left blank in SET the module is
SET event driven. If event driven this parameter is
not shown on the web page.
Label R/W R/W $ 0 30 null The module identifier used on strategy pages
CONST
and web pages
characters
CONST
file
There are 4 types of sensor module for use with different sources:
External Analogue Sensor (source: sensor value from an input channel)
Internal Analogue Sensor (source: analogue value from a module’s analogue output)
External Digital Sensor (source: digital status from an input channel)
Internal Digital Sensor (source: digital status from a module’s digital output)
The sensor module appears on the strategy page and can be either event driven or sequence table driven
28.1 Symbol
External Analogue Internal Analogue
6 20
Sensor 2 Sensor 5
S2 V
S5
0 m V
External 0 c 0 S
EXTERNAL INTERNAL
Analogue only DegC Units DegC Units
1 Type 0 High Alarm Limit
0 Offset 0 Low Alarm Limit
0 High Alarm Limit 0 High Alarm Delay
0 Low Alarm Limit
0 High Alarm Delay Analogue only 0
0
Low Alarm Delay
Out.Limits Delay
0 Low Alarm Delay 0 Read Alarm Delay
0 Out.Limits Delay Disabled Read Alarm
0 Read Alarm Delay
Enabled Read Alarm Disabled Out. Limits Alarm
Enabled Out. Limits Alarm Disabled Low Alarm
Enabled Low Alarm Disabled High Alarm
Enabled High Alarm 0 Override Enable
0 Override Enable 0 Override Value
0 Override Value 0 COV Increment
0.25 COV Increment
Type:
Read
Out of Limits
Low
High
Analogue Sensors
Input Types:
0: Analog
1: Internal Analog
Sensor connected to
another sensor
module
External
Analogue only
Digital Sensors
Input Types:
2: Digital
3: Internal Digital
Override
Status not
Value
Type is ignored
External for digitals
Digital only
Digital sensors
have no alarms
External
Analogue only
I n t e r n a l
Analogue only
Digital Sensors
External
Digital only
Digital sensors
have no alarms
Internal Digital
only
Connectives
An analogue input signal is generated by a hardware sensor; a physical device that converts a physical property (e.g.
temperature, pressure, humidity) into an electrical signal. The IQ3 input channels can accept several different types of
inputs as explained in Pt. 1 section 4.2.10 (e.g. current 0 to 20 mA, voltage 0 to 10 V). The way the input channel is connected
and linked defines the signal conditioning circuit used, and the conditioned signal is then converted to a digital value
by an analogue to digital convertor.
The sensor module then scales the value by reference to its Sensor Type module (see Pt. 2 section 29). This module
contains the information used for converting the input into engineering units and checking the value is within its
calibrated range. The Sensor Type modules act as a reference library of scaling types within the controller and hence
eliminate the need to set up the same type parameters in every sensor module.
The External Analogue Sensor module has an Offset parameter which is added to the measured value; this provision
allows the user to compensate for sensor reading errors due to, for example, thermal conduction. Thermal conduction
may apply when the mounting surface of the sensor is at a low or high temperature sufficient to cause the sensor to be
heated or cooled, resulting in inaccurate measurements. A negative or positive offset is applied to offset the measured
value and compensate for this heating or cooling effect.
If the channel number is set to zero, the source value (e.g. entered on web page) is treated as a constant.
The External Analogue Sensor also generates alarms: High, Low, Read and Out of Limits (see section 28.5 below)
Offset: (analogue, source/constant) The amount which is added to the sensor value to account for sensor reading errors.
It is in the same units as the sensor value, and can be positive or negative. This input can either be sourced from a module’s
analogue output or set to a constant value. If connected to a module’s analogue output, the output’s details will be shown
on the web page.
Hardware Channel (SET: I/O Channel): (analogue, constant) This parameter defines the hardware analogue input
channel which the external analogue input sensor is monitoring. The range of channel numbers available depends on
the type of main IQ3 or I/O module used (see Pt. 2 section 16.6). If the channel number is set to zero the input becomes
a constant (rather than a source) and its value, Source(mV), may be changed on the controller’s sensor web page (but
not in SET).
Hardware Module (SET: I/O Module): (analogue, constant) This parameter defines the hardware I/O module which
contains the analogue input channel. Zero refers to the main IQ3 unit and module numbers 1 to 15 can select an external
I/O module.
The Internal Analogue Sensor does not require the scaling or offset parameters used by the external analogue sensor
module as the input value is connected directly to its output. It will pass through the Read and Out of Limits alarms of
its source and generate its own Low and High alarms.
If the channel number is set to zero, the source status (0 or 1 e.g. entered on web page) is treated as a constant
Hardware Module (SET: I/O Module): (analogue, constant) This parameter defines the hardware I/O module which
contains the digital input channel. Zero refers to the main IQ3 unit and module numbers 1 to 15 can select an external
I/O module.
Hysteresis is automatically applied separately to each of sensor high or low limits. If the sensor alarm delay is non-zero
for one of the alarm limits then the hysteresis no longer applies to that limit. This effect works independently on each
alarm, so it is possible to have for example, a hysteresis applied to the high alarm and an alarm delay on the low alarm.
d e g re e s C
3 0
S e n s o r H ig h a la r m le v e l
2 9 .5 H y s te r e s is
1 0 .5 H y s te r e s is
1 0 S e n s o r L o w a la r m le v e l
T im e
Hysteresis will always be applied as a fixed percentage of the difference between the high and low alarm levels. Hysteresis
is calculated as follows:-
Low Alarm Level (SET: Low Alarm Limit): (analogue, source/constant) The sensor output level below which the low
alarm state is detected. Subject to hysteresis if the Low Alarm Delay is set to zero (see 28.5.5 above). This input can either
be sourced from a module’s analogue output or set to a constant value. If connected to a module’s analogue output,
the output’s details will be shown on the web page.
High Alarm Level (SET: Low Alarm Limit): (analogue, source/constant) The sensor output level above which the high
alarm state is detected. Subject to hysteresis if the High Alarm Delay is set to zero (see 28.5.5 above). This input can either
be sourced from a module’s analogue output or set to a constant value. If connected to a module’s analogue output,
the output’s details will be shown on the web page.
Alarm State: (characters, status) A display of the four alarm digital outputs as four bits.
e.g.
IOIO
Bit 3 = Read (R)
Bit 2 = Out of Limits (O)
Bit 1 = Low (L)
Bit 0 = High (H)
In Alarm: (analogue, status) This value indicates whether the sensor is in alarm, or has no alarm. It has accompanying
text shown in the list below which is shown on the sensor overview page in the ‘alarm’ column.
0 = No alarm
2 = High alarm
3 = Low alarm
4 = Out of Limits alarm
5 = Read alarm
The alarm state is shown if the alarm condition has been present for longer than that alarm’s delay time, and that alarm
is enabled to be reported. If more than one alarm is present the lowest numbered alarm will be reported. It will be set
back to 0 immediately all the alarms are in the clear state.
Read: This indicates the (Read) Alarm State as defined below. Clicking on Read on the web page will display the Read
alarm sub-module. The way in which the sub-module declares alarms and clear alarms is described in Pt. 1 section 12.4.1.
(Read) Alarm State: (digital, output) This will be 1 if the Read alarm condition has been present for longer than
its alarm delay time. It takes no account of its alarm enable. If connected to a module’s digital output, the output’s
details will be shown on the web page. This output is shown as a connective in SET (i.e. Snr1S, where S = sensor
module, n = sensor module number, r1 = Read alarm sub-module 1, S = status, e.g. S1r1S).
(Read) Enabled (SET: Read Alarm Enable): (digital, source/constant) This is an input to the sub-module which
will enable or disable the reporting of the alarm. Once the Alarm State is true the alarm will be reported; when the
alarm clears a clear alarm will be reported (if Clear Alarm, below, is also enabled). This input can either be sourced
from a digital output, or set to a constant value (0 or 1). If connected to a module’s digital output the output’s details
will be shown on the web page.
(Read) Alarm Sent: (digital status) This indicates that the alarm has been sent to the group module. This will only
happen if the Alarm State has been present for longer than the Alarm Delay, and the alarm is Enabled to be reported.
(Read) Alarm Delay (secs): (analogue, source/constant) This is the delay for which the Read alarm input must
be present before the Alarm State is declared. The alarm delay for the clear alarm state is always zero. The alarm
delay can either be sourced from a module’s analogue output, or set to a constant value. If connected to a module’s
analogue output, the output’s details will be shown on the web page.
(Read) Time in Alarm (secs): (analogue, status) This is the elapsed time since the Alarm State commenced
(Read) Alarm Group: (analogue, constant) This is the alarm group module to which the alarm will be sent.
(Read) Clear Alarm (SET: Clear Enable): (digital, constant) This is an input to the sub module which will separately
enable or disable the reporting of the clear alarm. Once the Alarm State is true and the alarm is enabled, the alarm
will be reported; when the alarm clears a clear alarm will be reported only if Clear Alarm is also enabled. This input
can be set to a constant value (0, disable or 1, enable).
Out of Limits: This indicates the (Out of Limits) Alarm State as defined below. Clicking on Out of Limits on the web
page will display the Out of Limits alarm sub-module. The way in which the sub-module declares alarms and clear alarms
is described in Pt. 1 section 12.4.1.
(Out of Limits) Alarm State: (digital, output) This will be 1 if the Out of Limits alarm condition has been present
for longer than its alarm delay time. It takes no account of its alarm enable. If connected to a module’s digital output,
the output’s details will be shown on the web page. This output is shown as connective in SET (i.e. Sno1S, where
S = sensor module, n = sensor module number, o1 = Out of Limits alarm sub-module 1, S = status, e.g. S1o1S).
(Out of Limits) Enabled (SET: Out of Limits Enable): (digital, source/constant) This is an input to the sub-module
which will enable or disable the reporting of the alarm. Once the Alarm State is true the alarm will be reported; when
the alarm clears a clear alarm will be reported (if Clear Alarm, below, is also enabled). This input can either be sourced
from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s digital output, the
output’s details will be shown on the web page.
(Out of Limits) Alarm Sent: (digital, status) This indicates that the alarm has been sent to the group module. This
will only happen if the Alarm State has been present for longer than the Alarm Delay, and the alarm is Enabled to
be reported.
(Out of Limits) Alarm Delay (SET: Out of Limits Delay) (secs): (analogue, source/constant) This is the delay for
which the Out of Limits alarm input must be present before the Alarm State is declared. The alarm delay for the
clear alarm state is always zero. The alarm delay can either be sourced from a module’s analogue output, or set
to a constant value. If connected to a module’s analogue output, the output’s details will be shown on the web
page.
(Out of Limits) Time in Alarm (secs): (analogue, status) This is the elapsed time since the Alarm State commenced
(Out of Limits) Alarm Group: (analogue, constant) This is the alarm group module to which the alarm will be sent.
(Out of Limits) Clear Alarm (SET: Clear Enable): (digital, constant) This is an input to the sub module which will
separately enable or disable the reporting of the clear alarm. Once the Alarm State is true and the alarm is enabled,
the alarm will be reported; when the alarm clears a clear alarm will be reported only if Clear Alarm is also enabled.
This input can be set to a constant value (0, disable or 1, enable).
Low: This indicates the (Low) Alarm State as defined below. Clicking on Low on the web page will display the Low alarm
sub-module. The way in which the sub-module declares alarms and clear alarms is described in Pt. 1 section 12.4.1.
(Low) Alarm State: (digital, output) This will be 1 if the Low alarm condition has been present for longer than its
alarm delay time. It takes no account of its alarm enable. If connected to a module’s digital output, the output’s
details will be shown on the web page. This output is shown as connective in SET (i.e. Snl1S, where S = sensor
module, n = sensor module number, ll (‘l’ as in ‘l’eather)= Low alarm sub-module 1, S = status, e.g. S1l1S).
(Low) Enabled (SET: Low Enable): (digital, source/constant) This is an input to the sub-module which will enable
or disable the reporting of the alarm. Once the Alarm State is true the alarm will be reported; when the alarm clears
a clear alarm will be reported (if Clear Alarm, below, is also enabled). This input can either be sourced from a module’s
digital output, or set to a constant value (0 or 1). If connected to a module’s digital output, the output’s details
will be shown on the web page.
(Low) Alarm Sent: (digital status) This indicates that the alarm has been sent to the group module. This will only
happen if the Alarm State has been present for longer than the Alarm Delay, and the alarm is Enabled to be reported.
(Low) Alarm Delay (secs): (analogue, source/constant) This is the delay for which the Low alarm input must be
present before the Alarm State is declared. The alarm delay for the clear alarm state is always zero.
If the low alarm delay is set to zero, the low alarm hysteresis will be applied (see section 28.5.5 above).
The alarm delay can either be sourced from a module’s analogue output, or set to a constant value. If connected
to a module’s output, the output’s details will be shown on the web page.
(Low) Time in Alarm (secs): (analogue, status) This is the elapsed time since the Alarm State commenced
(Low) Alarm Group: (analogue, constant) This is the alarm group module to which the alarm will be sent.
(Low) Clear Alarm (SET: Clear Enable): (digital, constant) This is an input to the sub module which will separately
enable or disable the reporting of the clear alarm. Once the Alarm State is true and the alarm is enabled, the alarm
will be reported; when the alarm clears a clear alarm will be reported only if Clear Alarm is also enabled. This input
can be set to a constant value (0, disable or 1, enable).
High: This indicates the (High) Alarm State as defined below. Clicking on High on the web page will display the High
alarm sub-module. The way in which the sub-module declares alarms and clear alarms is described in Pt. 1 section 12.4.1.
(High) Alarm State: (digital, output) This will be 1 if the High alarm condition has been present for longer than
its alarm delay time. It takes no account of its alarm enable. If connected to a module’s digital output, the output’s
details will be shown on the web page. This output is shown as connective in SET (i.e. Snh1S, where S = sensor
module, n = sensor module number, h1 = High alarm sub-module 1, S = status, e.g. S1h1S).
(High) Enabled (SET: High Alarm Enable): (digital, source/constant) This is an input to the sub-module which
will enable or disable the reporting of the alarm. Once the Alarm State is true the alarm will be reported; when the
alarm clears a clear alarm will be reported (if Clear Alarm, below, is also enabled). This input can either be sourced
from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s digital output, the
output’s details will be shown on the web page.
(High) Alarm Sent: (digital status) This indicates that the alarm has been sent to the group module. This will only
happen if the Alarm State has been present for longer than the Alarm Delay, and the alarm is Enabled to be reported.
(High) Alarm Delay (secs): (analogue, source/constant) This is the delay for which the High alarm input must be
present before the Alarm State is declared. The alarm delay for the clear alarm state is always zero.
The alarm delay can either be sourced from am module’s analogue output, or set to a constant value. If connected
to a module’s analogue output, the output’s details will be shown on the web page.
(High) Time in Alarm (secs): (analogue, status) This is the elapsed time since the Alarm State commenced
(High) Alarm Group: (analogue, constant) This is the alarm group module to which the alarm will be sent.
(High) Clear Alarm (SET: Clear Enable): (digital, constant) This is an input to the sub module which will separately
enable or disable the reporting of the clear alarm. Once the Alarm State is true and the alarm is enabled, the alarm
will be reported; when the alarm clears a clear alarm will be reported only if Clear Alarm is also enabled. This input
can be set to a constant value (0, disable or 1, enable).
The diagram shows possible sensor alarm state transitions with the downward
Normal
paths being alarms, and the upward paths being clear alarms.
The upward path should follow should follow the reverse of the downward
path.
The two OffNormal alarm states are treated separately so there are transitions
To/From High Limit, and To/From Low Limit.
The two Fault states are treated the same, so the transitions To/From Fault
apply to both Out of Limits and Read alarms. HIGH LOW
High Limit Low Limit
There are transitions within the Fault state, so a change from Out of Limits to
Read will generate a From Fault To Fault transition. OffNormal
It is also possible to go directly from Normal to Out of Limits which will create
a From Normal to Fault transition (in which case the return path should be From
Fault To Normal)
The BACnet Event Time Stamps array contains three values which are the
times (date and time) that the last transitions into the BACnet alarm states OUTL
occurred:
n1: Time into OffNormal READ
Value: (analogue, output) The output value of the sensor. For the External Analogue Sensor it is the scaled value in
engineering units. For analogue sensor modules it is an analogue value, for digital sensor modules it is an analogue value
of 0 or 1. If connected to a module’s analogue input, the input’s details will be shown on the web page.
The output is shown as a connective in SET (i.e. SnV where S = Sensor, n = sensor module number, V = Value).
COV Increment: (analogue, constant) (Analogue sensors only). The amount by which the sensor value has to change
before a BACnet COV notification message is sent to those subscribers in the List of Subscribers who have sunscribed
to this parameter. If COV Increment is zero, notification is not sent.
BACnet Event Time Stamps (not available in SET or on web pages): Applies to analogue sensor modules only. This
is an array of three values (text comms codes: n1 to n3) which hold the times of the last transitions into the BACnet alarm
states OffNormal, Fault, and Normal. In date and time format: yyy-mm-ddThh:mm:ss.
Units: (characters, constant) The units of the sensor output (e.g. degC). For compatibility with BACnet the units should
be chosen from the list of BACnet units given in Appendix 2. If units other than these are used, they will be transmitted
over BACnet as ‘no units’. In SET selecting the BACnet Units button enables the units to be selected from the list.
Page: (analogue, constant) SET file strategy page number on which module appears.
Override Output (SET: Override Enable): (digital, source/constant) This digital input will override the output to the
override value or status set in the next parameter. This input can either be sourced from a module’s digital output, or set
to a constant status (0 or 1). If connected to a module’s digital output, the output’s details will be shown on the web
page.
Override Value/Status (SET: Override): (analogue/digital, source/constant) This input is the value/status (value for
analogue sensor, status for a digital sensor) to which the output is overridden when the override condition is present.
This input can either be sourced from a module’s analogue or digital output, or set to a constant value. If connected to
a module’s output the output’s details will be shown on the web page.
Disable Module (SET: Module State - Enabled/Disabled): (digital, source/constant) This input will disable the module,
i.e. prevent it from being serviced. Its internal states and output will be maintained at their values prior to disabling. This
input can either be sourced from a module’s digital output, or set to a constant value (0 or 1). If connected to a module’s
digital output, the output’s details will be shown on the web page.
Sequence Table: (digital, constant) This is set to sequence table 1 if the module is sequenced (in the sequence table).
It is set to table zero if the module is event driven
Sequence Step: (analogue, constant) The sensor module can be either sequence table or event driven. If event driven
the step is set blank in SET, and the parameter does not appear on the web page. For sequence step driven modules this
defines the sequence step in the sequence table (see Pt. 1 sect 5.6); the module may be entered into the sequence table
more than once.
Selecting the icon will produce the graph from which the table of values may be selected if required.
The plot module summary page will also have the icon from which operates in the same way.
Trend supervisors are able to view the graphs and tables of values, and in some supervisors the table of values can be
exported as a spreadsheet file.
TYPE
co d e
SET Web Low High
page
Generic Sensor Module Controller Parameters
Input Type R/W R I 0 3 0 The type of module:
CONST
0=External Analogue
1= Internal Analogue
2= External Digital
3= Internal Digital
Label R/W R/W $ 0 30 null The module identifier used on strategy pages
CONST
and web pages. This can be used as an item
characters attribute for text comms and has restricted
characters see 28.6.2 above
Units R/W R/W % 0 4 null The units of the sensor output. For BACnet
CONST
should be chosen from list of units in
characters Appendix 2. In SET these can be found by
selecting BACnet Units button
Override Output R/W R/W* ^ 0 1 0 The status of the override input. Can be
(SET: Override connected to a digital output.
Enable)
Sequence step R/W R @ 0 500 specifically The sequence step at which the loop is
set up by serviced. If left blank in SET the module is
SET event driven. If event driven this parameter is
not shown on the web page
Generic Sensor Module SET Associated Parameter
Details R/W - - 0 255 blank Additional information about the module that
characters appears in SET
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Analogue Sensor Modules Controller Parameters
SOURCE/CONST SOURCE/CONST
High Alarm Level R/W R/W* H -1020 +1020 0 The level above which a sensor High alarm
(SET: High Alarm is generated. Can be connected to an
Limit) analogue output.
Low Alarm Level R/W R/W* L -1020 +1020 0 The level below which the sensor Low alarm
(SET: Low Alarm is generated. Can be connected to an
Limit) analogue output.
BACnet Event Time - - n1 to date&time; 0000-00-- BACnet only parameters. An arry of three
STATUS
Stamps n3 yyyy-mm-dd& 00T00:00:- parameters; the times of the last transitions
Thh:mm:ss 00 into alarm states:
n1: To OffNormal:
n2: To Fault
n3: To Normal
COV Increment R/W R/W C 0 +1020 0 The amount by which the sensor value must
CONST
change before a BACnet notification is sent.
If zero, there is no notification.
Alarm State - R M 0000 1111 0000 The alarm status of the 4 alarm digital
outputs:
Left to right:
STATUS
Bit 3=Read
four bits 0 Bit 2= Out of Limits
Bit 1=Low
Bit 0= High
In Alarm - R ! 0 5 0 Indicates an alarm has been present for
(Exc. longer than its delay time, and the alarm is
1) enabled.
STATUS
0=No alarm
2=High alarm
3=Low alarm
4=Out of Limits alarm
5=Read alarm
Alarm State - R r1(S) 0 1 0 Indicates the alarm has been present for
OUTPUT
Alarm Delay (secs) R/W R/W* r1(D) 0 178200 0 The time for which the alarm must be present
(Read) before the alarm state is declared. Can be
seconds connected to an analogue output.
Time in Alarm (secs) - R r1(T) 0 178200 0 The elapsed time since the alarm state
STATUS
(Read) commenced
seconds
Alarm Group R/W R/W r1(G) 0 500 1 The alarm group module to which the alarm
CONST
(Read) is sent
Clear Alarm R/W R/W m1(C) 0 1 1 A separate enable for the clear alarm. The
CONST
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Analogue Sensor Modules Controller Parameters
Alarm State - R o1(S) 0 1 0 Indicates the alarm has been present for
OUTPUT
(Out of Limits) longer than the delay time (independent of
alarm enable). Can be conected to a digital
input.
SOURCE/CONST SOURCE/CONST
Enabled R/W R/W* o1(E) 0 1 0 This input enables the alarm to be reported,
(Out of Limits) Can be connected to a digital output.
(SET: Out of Limits
Enable)
Alarm Sent - R o1(K) 0 1 0 Set true if the alarm has been sent to the
(Out of Limits) alarm group module
Alarm Delay (secs) R/W R/W* o1(D) 0 178200 0 The time for which the alarm must be present
STATUS
(Out of Limits) before the alarm state is declared. Can be
(SET: Out of Limits seconds connected to an analogue output.
Delay)
Time in Alarm (secs) - R o1(T) 0 178200 0 The elapsed time since the alarm state
STATUS
(Out of Limits) commenced
seconds
Alarm Group R/W R/W o1(G) 0 500 1 CONST The alarm group module to which the alarm
(Out of Limits) is sent
Clear Alarm R/W R/W m1(C) 0 1 1 A separate enable for the clear alarm. The
CONST
Alarm State - R l1(S) 0 1 0 Indicates the alarm has been present for
(Low) longer than the delay time (independent of
alarm enable). Can be connected to a digital
input.
SOURCE/CONST SOURCE/CONST
Enabled R/W R/W* l1(E) 0 1 0 This input enables the alarm to be reported.
(Low) Can be connected to a digital output.
(SET: Low Enable)
Alarm Sent - R l1(K) 0 1 0 Set true if the alarm has been sent to the
(Low) alarm group module
Alarm Delay (secs) R/W R/W* l1(D) 0 178200 0 The time for which the alarm must be present
STATUS
Time in Alarm (secs) - R l1(T) 0 178200 0 The elapsed time since the alarm state
STATUS
(Low) commenced
seconds
Alarm Group R/W R/W l1(G) 0 500 1 The alarm group module to which the alarm
CONST
(Low) is sent
Clear Alarm R/W R/W m1(C) 0 1 1 A separate enable for the clear alarm. The
CONST
* This source/constant parameter cannot be changed via the web page if it is set as a source.
TYPE
co d e
SET Web Low High
page
Analogue Sensor Modules Controller Parameters
Alarm State - R h1(S) 0 1 0 Indicates the alarm has been present for
OUTPUT
(High) longer than the delay time (independent of
alarm enable). Can be connected to a digital
input.
SOURCE/CONST SOURCE/CONST
Enabled R/W R/W* h1(E) 0 1 0 This input enables the alarm to be reported.
(High) Can be connected to a digital output.
(SET: High Alarm
Enabled)
Alarm Sent - R h1(K) 0 1 0 Set true if the alarm has been sent to the
(High) alarm group module
Alarm Delay (secs) R/W R/W* h1(D) 0 178200 0 The time for which the alarm must be present
(High) before the alarm state is declared. Can be
STATUS
seconds connected to an analogue output.
Time in Alarm (secs) - R h1(T) 0 178200 0 The elapsed time since the alarm state
STATUS
(High) commenced
seconds
Alarm Group R/W R/W h1(G) 0 500 1 The alarm group module to which the alarm
CONST
(High) is sent
Clear Alarm R/W R/W m1(C) 0 1 1 A separate enable for the clear alarm. The
CONST
Offset R/W R/W* O -1020 +1020 0 The amount added to the sensor to account
for sensor reading errors. Can be connected
to an analogue output.
A=10
B=11
C=12
D=13
E=14
F=15
OUTPUT SOURCE/CONST
Source(mV) - R/W*† S 0 10000 0 The value of the input channel. If the input
channel is set to zero this becomes a
constant. Channel number can only be set to
zero on the web page.
Value R R V -1020 +1020 0 The output of the sensor. The scaled value in
engineering units. Can be connected to an
analogue input.
* This source/constant parameter cannot be changed via the web page if it is set as a source.
† This Source(mV) parameter is a source if Hardware Channel is non-zero, otherwise it’s a constant. Hardware
Channel can only be set to zero on the web page.
TYPE
comms
co d e
SET Web Low High
page
Internal Analogue Sensor Module Controller Parameters
Type R/W R/W Y 0 99 1 - Not used
20 20
Offset R/W R/W* O -10 +10 0 - Not Used
OUTPUT SOURCE/CONST
Source(mV) R/W R/W* S -1020 +1020 0 The value of the input. It is not in mV. Can be
(SET: Source Value) connected to an analogue output.
CONST
(SET: I/O Channel) the Source input channel number. Channel
zero makes the input a constant.Channel
number can only be set to zero on the web
page
Hardware Module R/W R/W i 0 F 0 The address of the hardware IO module
(SET I/O Module) sourcing the digital input, hexadecimal
0=main controller
1 to 9 = 1 to 9
CONST
A=10
B=11
C=12
D=13
E=14
F=15
OUTPUT SOURCE/CONST
* This source/constant parameter cannot be changed via the web page if it is set as a source.
† This Source parameter is a source if Hardware Channel is non-zero, otherwise it’s a constant. Hardware Channel
can only be set to zero on the web page.
The scaling information and the limits used to check for an Out of Limits (OUTL) alarm are stored in a sensor type module.
As its name implies, each sensor type module within a controller is configured for a particular type of sensor (e.g. Trend
Thermistor Sensor). To avoid defining the scaling information and OUTL alarm limits in each sensor module, the sensor
type information is defined once only (in the sensor type module) and referenced by each individual sensor module
monitoring a sensor of that type.
SET is supplied with standard scaling tables (Sensor Library) for the sensors supplied by Trend which facilitate the
configuring of sensor type modules for the Trend Sensors. The sensor library has a separate section for user defined
scaling tables. The SET Strategy Library also has preconfigured sensor types for particular applications.
The sensor type module has another function, that of providing a characteristic table for use with the lookup type function
module (see Pt. 2 section 14.21). To be used in this way, the Input Type parameter must be set to Analogue Value. The
lookup function module has a Scaling Type parameter which cross-references a sensor type module. If the function
module cross-references a sensor type module which is not set to Analogue Value input type, the output is set to 0.
The sensor type module does not appear on the strategy page, and is accessed when the external analogue sensor
module, or lookup function module is serviced.
29.3 Function
The table may have between 2 to 20 points which must be entered in ascending order of the input. The Number of Points (Points
Used) must be specified.
Note that a sensor whose input channel is linked for thermistor may use either thermistor volts (V) - type 1, or thermistor
(k) - type 3. Normally the sensor characteristic will be given in kilohms, so type 3 would be used. However, thermistor
volts - type 1 enables a sensor’s characteristic to be produced by measuring voltage values at the input terminals and
entering them in the thermistor volts table. The thermistor volts input type is normally used because the voltage
characteristic is more linear which gives greater accuracy in the linear interpolation described below.
The output value of the module is calculated by linearly interpolating between the relevant 2 points. If the input value
falls above or below the table range then the output value is calculated from the extrapolated straight line between the
first two points or the last two points respectively.
The example below shows a 9 point table with the input ascending from 0.916 k to 55.34 k. The graph shows the
straight lines between the points, with the first and last straight lines extrapolated.
Linear Interpolation
Entry Input (kohm) Output (°C)
1 0.916 90 100
2 1.751 70 80
3 3.602 50
60
O - Output
4 5.326 40
40 O
5 8.058 30
20
6 12.49 20
7 19 . 9 10 0
0 20 40 60
8 32.66 0 -20
I - Input
9 55.34 - 10
29.4 Sensor Type Module Parameters
29.4.1 Sensor Type Configuration Parameters
Label (SET: Unique Sensor Reference): (characters, constant) The sensor type module label displayed on the web
page. In SET it is set to be the Unique Sensor Reference of the selected sensor scaling table. In SET the Unique Sensor
Reference of the sensor scaling table, is formed from sensor part and range, (e.g. Light I 20K). This unique sensor
reference is referred to in the sensor installation instructions.
Number (SET only): The module number; this has the Unique Sensor Reference added after it to aid recognition
Input Type: (analogue, constant) The type of input being scaled by this sensor type module. It has the following range
of values:
0 = Volts (V) - if sensor input channel linked for voltage (V)
1 = Thermistor Volts (V) - if sensor input channel linked for thermistor (T)
2 = Current (mA) - if sensor input channel linked for current (I)
3 = Thermistor Ohms (k) - if sensor input channel linked for thermistor (T)
4 = Analogue Value - if used with lookup function module
Upper Limit: (analogue, constant) The upper limit at which the Out of Limits alarm is detected by a sensor module. This
will normally be the upper working limit of the sensor. (Not used if the sensor type module is being used by a lookup
function module).
Lower Limit: (analogue, constant) The lower limit at which the Out of Limits alarm is detected by a sensor module. This
will normally be the lower working limit of the sensor. (Not used if the sensor type module is being used by a lookup
function module).
Inputs 1 to 20: (analogue, constant) These are the values of the input corresponding to the output values shown below
(i.e. input 1 corresponds to output 1). The input units correspond to the Input Type parameter (e.g. if set to Input Type
0, Volts, the input units will be in volts). If used for reference by a lookup function module these will be the analogue
input values.
Outputs 1 to 20: (analogue, constant) These are the values of the output corresponding to the input values shown above
(i.e. output 1 corresponds to input 1). The output will be in the engineering units of the variable being measured by the
sensor (e.g. degC). If used for reference by a lookup function module these will be the analogue output values.
Exponent (SET only - greyed out): Not used. This parameter is only shown in SET and is greyed out. The exponent was
required in IQ2 sensor types but is not needed in IQ3 as the values are given full range (-1020 to +1020).
Scaling (SET only): Not used. This parameter corresponds to the sensor type mode parameter in IQ2 which had 5 modes.
The fifth mode was ‘Characterise’. The IQ3 scaling is fixed at IQ2 mode 5, Characterise, and cannot be changed.
Sensor Part: This is the sensor order code for the type of sensor (e.g. LLS). It can be selected from the drop down menu;
it enables entry of a new order code to create a new sensor scaling table.
Scaling Range: The scaling range of the sensor (e.g. +0 to +20000 lux type 5). There may be several scaling ranges set
up for a sensor part
Filter: Enables selection of standard Trend sensor scaling table section of the library, or the user defined sensor scaling
table section.
Apply: Applies the selected scaling table to the sensor type module.
Edit: Enables entry of the sensor type module parameters used when setting up a new sensor scaling table, or modifying
an existing table
Save to Library: Adds a new sensor scaling table to the user defined section of the sensor library
Delete from Library: Deletes an existing sensor scaling table from the user defined section of the sensor library.
Refresh: This button refreshes the graph displayed in the dialogue box.
Example 1
T/PI platinum resistance temperature sensor has measurement range -10 to +40 degC with an output signal of 4 to 20 mA.
Note it is common practice for the lower limit signal to be 4 mA for a current output type sensor as then an open circuit
condition can be detected by a value of 0 mA which will give a value outside the working limits and hence an Out of
Limits alarm condition.
Points Used: 2
The upper and lower limits should be chosen to define the working range of the sensor:
Upper Limit: +40
Lower Limit: -10
Example 2
AV/D air velocity sensor set to its defaults of measurement range: 0 to 10 m/s, and output signal: 0 to 10 V.
Points Used: 2
The upper and lower limits should be chosen to define the working range of the sensor:
Upper Limit: 10.1
Lower Limit: 0
Here the upper limit is chosen as 10.1 as the upper limit of 10 V is a valid measurement; this shows that the upper and
lower limits can be outside the defined range, as the values outside the range are found by extrapolation.
Example 3
TB/TS/K ±20% Knob is often used to produce a -3 to +3 deg trim on the local space temperature setpoint.
1 kW ±5%
10 kW ±20%
Note that it is common practice for the lower limit signal to be 1 kohm for a potentiometer as then an open circuit condition
can be detected by a value of 0 kohm which will give a value outside the working limits and hence an Out of Limits alarm
condition.
Since great accuracy is not required the characteristic can be entered as temperature versus resistance and assume a
straight line:
Input Type Parameter: 3 = Thermistor Ohms (k)
Points Used: 2
The upper and lower limits should be chosen to define the working range of the sensor:
Upper Limit: +3.1
Lower Limit: -3.1
However if one wishes to guarantee a -3 to +3 trim, the resistance tolerances should be taken into account.
This is done by taking the highest minimum value and the lowest maximum value and allocating the trim range across
these values. Outside this range variations in resistance can be dealt with by tail-offs where the change in resistance
produces little change in trim.
+3.1
+3
950 1050
Resistance (ohms)
8950 13050
-3
-3.1
Points Used: 4
This is because the input channel accuracy swamps the sensor scaling accuracy so that the niceties described below are
not required. Hence the standard Trend thermistor scaling tables use the same input/output points but with different
upper and lower limits.
Theoretically for maximum linearisation accuracy the sensor scaling points should be chosen so that there are more
points covering the parts of the characteristic which are curved and fewer points over the straighter parts. This is because
a straight characteristic can be defined by two points as described above.
straighter sections
The above characteristic is for the standard Trend thermistor sensor over its full range (-30 to +110 deg C). It is shown
for a Thermistor Volts input type; it would be possible to directly enter the temperature versus resistance values using
the Thermistor Ohms(k) input type, but this would give greater inaccuracies due to the linear interpolation used by
the module as mentioned in section 29.3 above.
Also the number of points should be spread over the range to be used, so for the Trend thermistor sensor if the sensor
is only used indoors (e.g. TB/TS) the range can be reduced to 0 to 40 deg C, and the 20 points spread over that reduced
range.
TYPE
co d e
SET Web Low High
page
Generic Sensor Module Controller Parameters
Input Type R/W R I 0 4 0 The type of scalinge:
0=Volts (V)
CONST
1= Thermistor Volts (V)
2= Current (mA)
3= Thermistor Ohms (kohm)
4 = Analogue
CONST
Label R/W* R/W $ 0 30 null The module identifier used on web pages.
(SET: Unique Sensor
Reference) characters
CONST CONST
Number R/W - - 1 99 1 The units of the sensor output
(SET only)
Number of Points R/W R/W P 2 20 0 Number of points used in the conversion
(SET: Points Used) table
CONST CONST
Upper Limit R/W R/W U -1020 +1020 0 The Out of Limits alarm upper limit. Not used
if sensor type module used for lookup
function module
Lower Limit R/W R/W L -1020 +1020 0 The Out of Limits alarm lower limit. Not used
if sensor type module used for lookup
function module
CONST CONST CONST CONST
Inputs 1 to 20 R/W R/W In -1020 +1020 0 The input value of point 'n' in the conversion
table. (n = 1 to 20)
Outputs 1 to 20 R/W R/W On -1020 +1020 0 The output value of point 'n' in the conversion
table. (n = 1 to 20)
Exponent - - - - - - Not used. Greyed out in SET
(SET only)
Scaling - - - - - - Not used. Permanently set to 5,
(SET only) Characterise, in SET
SET Associated Parameters
Sensor Part - - - - - - Order code for type of sensor
Scaling Range - - - - - - The sensor range (e.g. 0 to 40 degC)
Filter - - - - - - This button selects either Trend standard part
or User defined par tofsensor library
Apply - - - - - - This button applies this scaling table to the
sensor type module.
Cancel - - - - - - This button clears down the sensor type
dialogue box.
E di t - - - - - - This button enablesd the sensor type module
parametes to be editted.
Save - - - - - - This button confirms the changes made to
the scaling table
Store to Library - - - - - - This button stores the changes made to the
sensor type module to the sensor library
Delete from Library - - - - - - This button deletes the currently displayed
scaling table from the sensor library
Refresh - - - - - - This button refreshes the graph displayed in
the dialogue box
The following types of modules may be entered into the sequence table:
Sensor
Loop
Function
Driver
Schedule
Logic
Each module is normally entered into the sequence table in the order of signal flow, so that the modules entered into
the table with the lowest sequence step number are serviced first. This order can be critical - see Pt. 1 section 5.6.5.
There is a maximum of 600 sequence table steps. The whole table is serviced in the fixed sequence table cycle time of
1 s.
On the strategy diagram, the module has a sequence table entry number shown above it in an oval shape.
30.1 Symbol
no sequence step
sequence step (event driven)
2
Sensor 1 Sensor 20
S1 S20 V
0 m V 0 m
6 c 0 c
EXTERNAL EXTERNAL
If the module is seuqenced the sequence step is shown in the oval. If it is not sequenced, the oval shape is left blank,
and the module will be event driven.
sequenced module
If the module is sequenced its sequence table step is shown on the web page and the sequence table parameter is set
to 1. If the module is not sequenced, there is no sequence step parameter shown on the web page, and the sequence table
is set to zero.
When a module is added to the strategy page the sequence step is normally added automatically. The sequence step
can be changed by right clicking on the module, and selecting ‘Sequence Step’. Sequence steps can then be added or
removed using the arrow keys (see Pt. 1 section 5.11).
135 203
Sensor 17 two entries in
S17 V sequence
EXT DIG table
Units
0 Override Enable
two entries into 0 Override Value
sequence table
Multiple entries should be distributed through the sequence table and separated by an equal number of steps to divide
the sequence table service time equally.
Separate entries into the sequence table are shown as separate lines on the web page. For example in the logic module
web page above there are two entries into the sequence table at steps 1 and 11. Similarly the strategy symbol shows the
multiple entries in the oval sequence step box.
Some modules should not be given multiple entries (see Pt. 1 section 5.6.6).
It is possible to put a whole sub strategy into the sequence table more than once to save on modules at the expense of
sequence table steps (see Multiplexing, Pt. 1 section 5.6.7).
Disabling can be used for strategy fault finding or in event driven sequences to prevent ‘run away’ operation.
A disabled module is no longer serviced so its output(s) and internal states are maintained at their values prior to disabling.
co d e
SET Web Low High
page
Controller Parameters
CONST
Last Sequence Step R R L 600 600 600 Sequence table size. Fixed at 600
Sequence Step 1 R/W R S1 sequence table blank The module serviced at sequence step 1
CONST
module text
comms code
e.g. D1
The function performed by any switch is determined by the strategy within the controller.
The switch module appears on the strategy page and is always event driven. Since a switch is always event driven, its
output should never be connected back to its input. SET prohibits this.
31.1 Symbol
A switch is represented on the strategy as a variable digital node.
Switch 6
W6
0
D
SWITCH
0 Pin Level
Connective
31.5 Parameters
31.5.1 Input and Output Parameters
Status: (digital, source/constant) The current state of the switch. It can either be sourced from a module’s digital output
or set to a constant status (0 or 1). If connected to a module’s digital output the output’s details will be shown on the
web page.
Destination: (digital, output) The state of the module’s output. If connected to a module’s digital input, the input’s details
will be shown on the web page. The output is shown as a connective in SET (i.e. WnD where W = Switch, n = switch
module number, D = destination).
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
The switch label can be used as an item attribute for text communications. This is explained for IC Comms in Pt. 2 section
15.4.
Special characters are as follows:-
? * .
Page: (analogue, constant) SET file strategy page number on which module appears.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Label R/W R/W $ 0 30 null The module identifier used on strategy pages
CONST
and web pages. This can be used as an item
characters attribute for text comms and has restricted
characters see 31.5.3 above
SOURCE/CONST
Status R/W R/W* S 0 1 0 The current state of the switch. Can be
connected to a digital output.
User Level R/W R/W P 0 99 0 The PIN level at which the user must be
CONST
* This source/constant parameter cannot be changed via the web page if it is set as a source.
The IQ3 real time clock is supported by a ‘supercap’ in the case of power failure. This will support the clock for up to
six days. When power is restored if the supercap is discharged (i.e. IQ3 has lost its time), the IQ3 will request time
synchronisation from an IQ3 Timemaster.
The IQ3 time module can be set up so that the IQ3 acts as a Timemaster; a Timemaster IQ3 should have a backup battery
board installed.
The time module produces timing outputs for use in the strategy.
The time module appears on the strategy page and is not sequenced, but is regularly serviced. When serviced it will read
the accurate time from the real time clock.
32.1 Symbol
SET 6.1, IQ3 v1.4 or greater
Connectives
UTC Time
UTC time, Coordinated Universal Time, is the agreed international atomic time (with minor corrections for earth’s rotation
etc.). This is approximately the same as GMT. BST, British Summer Time, is 1 hour ahead of UTC. BACnet protocol
includes time synchronisation (date and time) using UTC time, so that it can synchronise internationally across the time
zones.
The IQ3 controller supports this by using the UTC Offset (Mins) parameter.
CurrentTime (controller’s local time)=UTC time + Daylight Savings Offset - UTC Offset
Note that a web page graph may appear to show the incorrect times if the UTC offset parameter is not set up correctly.
The UTC offset parameter in the time module must be set up correctly to reflect the current offset from UTC that the
controller is operating in.
32.4.1 Timemaster
The Timemaster function is to maintain time and date synchronisation of all IQ controllers (time followers) and to effect
daylight saving time changes from a single source.
In addition to the time and date, a Timemaster will transmit UTC Offset, Daylight Savings Applied status, and Daylight
Savings Offset. These will enable the individual time follower controllers to respond to BACnet requests for the
controller’s UTC time.
The Timemaster will control the time and date synchronisation of all IQ controller real time clocks for an entire system
(with the exception of auto-dialled sites). It can thus synchronise remote Lans across the internetwork. The Timemaster
may be placed at any address on any Local Area Network. However, address 11 is recommended as IQLs require an IQ
to be at address 11 from which to request the time.
It is recommended that the timemaster should have the battery backup option fitted (XCITE/BBC, see Pt. 1 section 4.2.13)
so that it will maintain its own time for several years in the event of power failure.
To set up an IQ3 as a timemaster it should have its Time Master parameter changed from ‘no’ to ‘yes’.
The Timemaster will send a time and date update message to all devices on all Lans (except auto-dialled Lans) at the
following times:-
a) 00:05 hours each day
b) when it receives a request for time and date synchronisation from any Lan (not auto-dialled).
c) after any edit of its own time module time and date
d) after effecting a daylight saving time change (e.g. BST/GMT)
Remember a Timemaster is necessary for each section of the system separated from other sections by auto-dialled links.
On a combined system with IQ3s, IQLs, and earlier IQs (IQ1s, IQ2s) the Timemaster must be an IQ3 (as an IQ2 Timemaster
would not respond to an IQ3s request for synchronisation). IQ1s pre-1989 cannot be synchronised by an IQ3.
The IQ3 cannot fulfil the role of Timekeeper. This role was required for IQ90s (which did not have battery backed real
time clocks); they should be supported by an IQ2 or IQ1 Timekeeper controller at address 11 on their own Lan. These
Timekeeper controllers can then be synchronised by the IQ3 Timemaster so there is still the one central Timemaster.
The IQLs also have a Timekeeper which is normally at address 11 on their own Lan; it will request time synchronisation
from an IQ at address 11 on a specified Lan.
Note that there should only be one Timemaster on the system (excluding autodialled sections).
The IQ3 will not operate correctly with the IQ212/BOX/ATM as its Timemaster function cannot be reset by the ATM.
If required to operate with an ATM, its Time Master parameter should be set to No. The ATM cannot respond to a request
for synchronisation by an IQ3, but it sends out an hourly time synchronisation message, and hence in the worst case
an IQ3 will not become synchronised until one hour after power up.
The IQ3 time synchronisation message uses text comms and as such will be rejected by a controller which is password
protected unless there is a valid password in the synchronisation message. If the controller to be synchronised is
password protected, a User module in the Timemaster must be set up with a password that is also set up in the controller
to be synchronised and of sufficient authority level (level 80 or greater).
The Daylight Hours Change (SET: Change By) parameter defines the number of hours that will be added to the time at
the start date, and subtracted from the time at the end date. If the Daylight Hours Change parameter is set to zero there
will be no daylight saving changes. Similarly if the Start Day and/or End Day are left at their defaults of zero there will
be no daylight saving. If the Daylight Hours Change parameter is non-zero, a controller will copy its Daylight Hours
Change value into its Daylight Savings Offset parameter, and set its Daylight Savings Applied status appropriately.
The Daylight Hours Change parameter is added to the time on the start date at a time change +1 hour and subtracted
from it on the end date at time change +1 hour. So if the Daylight Hours Change parameter is set to 3, it will start on the
start date at 04.00 hours setting the time forward to 07.00 hours, and finish on the end date at 04.00 hours so setting the
time back to 01.00.
If daylight saving is required on a system with a Timemaster, the daylight saving should be set up in the Timemaster
only, all time follower controllers’ daylight saving should not be set up (Daylight Hours Change should be zero). The
Timemaster will synchronise a time follower controller’s time and date, and set up its UTC Offset, Daylight Savings
Applied status, and Daylight Savings Offset appropriately.
This enables the time follower controller to respond correctly to BACnet communications.
The IQ2 Change By parameter can only be set to 0, 1, 2, whereas in IQ3 it can be set to 0, 1, 2, 3.
The IQ3 time module can appear on the strategy page, and connections can be made to the Start day, Start Month, End
Day, End Month, and Change By (IQ3 v1.4, SET v6.1).
IQ3 can operate with UTC Time (BACnet), IQ2 can’t (IQ3 v2.0).
The 1 s pulse will last for the sweep of the sequence table, and then clear until the beginning of the next second.
Daylight Start Month (SET: Start Month): (analogue, source/constant) The month at which daylight saving should
commence. It can either be sourced from a module’s analogue output or set to a constant value. If connected to a module’s
analogue output, the output’s details will be shown on the web page.
Daylight End Day (SET: End Day): (analogue, source/constant) The day of the month at which daylight saving should
finish. It can either be sourced from a module’s analogue output or set to a constant value. If connected to a module’s
analogue output, the output’s details will be shown on the web page.
Daylight End Month (SET: End Month): (analogue, source/constant) The month at which daylight saving should finish.
It can either be sourced from a module’s analogue output or set to a constant value. If connected to a module’s analogue
output, the output’s details will be shown on the web page.
Daylight Hours Change (SET: Change By): (analogue, source/constant) The amount (in integral hours) by which the
time will change for daylight saving. It can either be sourced from a module’s analogue output or set to a constant value.
If connected to a module’s analogue output, the output’s details will be shown on the web page.
Day: (analogue, output) The current day of the month. If connected to a module’s analogue input, the input’s details
will be shown on the web page. The output is shown as a connective in SET (i.e. T1D where T1 = Time module, D = Day).
Month: (analogue, output) The current month. If connected to a module’s analogue input, the input’s details will be shown
on the web page. The output is shown as a connective in SET (i.e. T1M where T1 = Time module, M = month).
Weekday: The current day of the week (1 to 7, where 1= Monday, 7 = Sunday). The output is shown as a connective
in SET (i.e. T1W where T1 = Time module, W = weekday).
Current Time: (analogue, output) The current time in hh.mm. If connected to a module’s analogue input, the input’s
details will be shown on the web page. The output is shown as a connective in SET (i.e. T1c where T1 = Time module,
c = current time).
Minutes Past Midnight (SET: Minutes since Midnight): (analogue, output) The minutes elapsed since midnight. If
connected to a module’s analogue input, the input’s details will be shown on the web page. The output is shown as a
connective in SET (i.e. T1m where T1 = Time module, m = minutes past midnight).
Output pulses: (digital, output) The time module produces 13 timing output pulses. If one of these outputs is connected
to a module’s digital input, the input’s details will appear on the web page. They all appear as connectives in SET.
Second Pulse: Pulse every second, Connective: T1i
Minute Pulse: Pulse every minute, Connective: T1k
5 Minute Pulse: Pulse every 5 minutes, Connective: T1l
10 Minute Pulse: Pulse every 10 minutes, Connective: T1n
15 Minute Pulse: Pulse every 15 minutes, Connective: T1o
20 Minute Pulse: Pulse every 20 minutes, Connective: T1a
30 Minute Pulse: Pulse every 30 minutes, Connective: T1q
60 Minute Pulse: Pulse every 60 minutes, Connective: T1r
6 Hour Pulse: Pulse every 6 hours, Connective: T1s
24 Hour Pulse: Pulse every 24 hours, Connective: T1t
Weekly Pulse: Pulse every week, Connective: T1b
Monthly Pulse: Pulse every month, Connective: T1d
Yearly Pulse: Pulse every year, Connective: T1z
Minutes: (analogue, status) The current minutes past the hour (0 to 59)
Seconds: (analogue, status) The current seconds past the minute (0 to 59)
Time Master: (digital, constant) This parameter will enable the timemaster function if set to ‘yes’ (i.e. one).
UTC Offset (Mins): (analogue, constant) The local offset from international time (UTC, co-ordinated universal, time).
Can be set in the range -768 to + 768 (±12 hrs 48 mins offset).
Daylight Savings Applied (not available in SET): (digital, status) If set true, the controller’s time has been adjusted for
daylight savings. In a system with a Timemaster, the time follower controller’s Daylight Hours Change parameter is zero,
and a Timemaster can set and clear the Daylight Savings Applied parameter. On a system without a Timemaster, the local
controller’s Daylight Hours Change parameter can be set to non-zero, and then the controller will set and clear this
parameter.
Daylight Savings Offset (Mins) (not available in SET): (analogue, status) This is the amount by which the time is changed
for daylight saving. It can be set in the range zero to 240 minutes (0 to 4 hours). In a system with a Timemaster, the time
follower controller’s Daylight Hours Change parameter is zero, and a Timemaster can set up the Daylight Savings Offset
parameter. On a system without a Timemaster, the local controller’s Daylight Hours Change parameter can be set to non-
zero, and then the controller will copy its Daylight Hours Change parameter into its Daylight Savings Offset parameter.
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
Page: (analogue, constant) SET file strategy page number on which module appears.
TYPE
comms
co d e
SET Web Low High
page
Controller Parameters
Current Time - R c 00.00 23.59 00.00 The current time in hours hours. minutes
OUTPUT
hh.mm minutes. Can be connected to an analogue
hh= 00 to 23 input.
mm= 00 to 60
OUTPUT
Minutes Past - R m 0 1439 0 The number of minutes elasped since
Midnight midnight. Can be connected to an analogue
(SET: Minutes since input.
Midnight)
D ay - R/W D 1 31 1 The current day of the month. Can be
OUTPUT
TYPE
co d e
SET Web Low High
page
Controller Parameters
Second Pulse - R i 0 1 0
OUTPUT
The pulse generated every second. Can be
connected to a digital input.
OUTPUT OUTPUT
connected to a digital input.
OUTPUT
be connected to a digital input.
OUTPUT
be connected to a digital input.
OUTPUT
be connected to a digital input.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Daylight Start Day R/W R/W* S 0 31 0 The day of the month at which daylight saving
(SET: Start Day) should commence. Day 0 means no daylight
saving. Can be connected to an analogue
output.
Daylight Start Month R/W R/W* O 1 12 1 The month at which daylight saving should
(SET: Start Month) commence. Can be connected to an
analogue output.
Daylight End Day R/W R/W* E 0 31 0 The day of the month at which daylight saving
(SET: End Day) should finish. Day 0 means no daylight
saving. Can be connected to an analogue
output.
Daylight End Month R/W R/W* T 1 12 1 The month at which daylight saving should
(SET: End Month) finish. Can be connected to an analogue
output.
UTC Offset (Mins) R/W R/W U -780 +780 0 The amount by which the controller's local
CONST
Label R/W R/W $ 0 30 null The module identifier used on strategy pages
characters and web pages.
* This source/constant parameter cannot be changed via the web page if it is set as a source.
Each day has up to 10 occupation periods defined by start and stop time zone change times; there can be up to 20 change
times in a day (10 on, 10 off).
O T P N O C O C C N O C O C C N O C O C C
S T A R T 1 S T O P 1 S T A R T 2 S T O P 2 S T A R T 3 S T O P 3
N O C = N O T O C C U P IE D
C U R R E N T
O C C = O C C U P IE D
T IM E
C U R R E N T S T A R T C U R R E N T S T O P O T P (O C C U P A T IO N T IM E P R O F IL E )
O S S S T A R T O S S S T O P O S S (O P T IM U M S T A R T S T O P )
The time zone has a normal week to define the normal weekly occupation pattern; differences to the normal occupation
pattern are dealt with by creating exceptions which have start and stop dates, and can define a different daily occupation
pattern between these dates.
A time zone can be allocated to an area of a building which has a defined occupation pattern which is different from other
areas (e.g. factory, office, service bureau, canteen). It may also be beneficial to allocate separate zones to areas of the
building which normally have the same occupation times, but may have different exceptions.
A time zone module appears on the strategy page but is not sequenced as it is serviced automatically once a minute.
33.1 Symbol
The strategy graphic symbol can be set to ether graphic or data display by the radio buttons in the SET dialogue box.
Each day is capable of handling up to 10 occupation periods, each being defined by a start time and a stop time.
Each zone can also have up to 50 Exceptions. An exception is a single day’s profile that operates between a defined start
date and a stop date; if the exception is for a single day, the start and stop dates are the same. An exception day is like
a normal week day with up to 10 occupation periods, each being defined by a start time and a stop time.
The exceptions have a priority 1 to 16 where 1 is the highest. If exceptions overlap, the one with the highest priority is
used.
Exceptions also have a Use parameter; this enables the exception to be used every year, or just once in the year ahead.
The use parameter can be set to next, every, or free as follows:
Next: The exception will be used for the next period it occurs and will be set to Free use after its stop date.
Every: The exception will be used every year
Free: The exception will not be used
Normal Week
Exception
a ck
Exception Day g ob
k
A Day’s Occupation Times (either normal week or exception) b ac
go
Connective
The SET dialogue box then enables the times to be set up. A time period is added to an empty day by dragging the left
hand arrow at the end of the day’s line to the left to the required start time, the right hand arrow can then be dragged to
the required stop time. Further time periods can the be added by repeating this process.
SET 6.1 facilitates the creation of exceptions by providing a calendar. The user can click on the calendar on the start date
and then drag the bracket to a stop date. Clicking Add then creates the exception between these dates. Clicking Apply
saves the exception.
The individual exception can be edited by selecting it from the drop down list (entitled Label). The exception occupation
pattern is set out in the line below (labelled E). The exception day time periods can then be set up in the same way as
the normal week’s days described above.
If the day has no periods, the Create New Time Zone Period Module button enables the first change time to be entered.
Since the day’s default is ‘Off’, this first change is a start time whose value should be ‘On’. Selecting the Create New
Time Zone Period Module button again creates another change time which it will set by default to be time 0.00 and value
‘Off’, and place at the top of the list as it automatically sorts into time order. This change time should then be set to the
stop time whose value should be ‘Off’.
Selecting the button at the top of the page (entitled with the zone’s label) will redisplay the Normal Week page with the
new times shown for that day.
Once one day is set up it may be copied to another day by selecting the day to copy on the Normal Week page with the
radio button, and the day to copy to with the check box (tick). Selecting the copy button then causes the day’s
times to be copied to the other day.
To see the Exceptions for a time zone, select Exceptions from the Overview page.
If the Exception is new, select Create New Exception Profile, and the exception’s start and stop dates and other parameters
may be entered. Selecting the Times button , will show the exception day’s profile, and selecting ‘Times’ enables the
time to be entered (as for the Normal Week as described above).
Selecting the button at the top of the page (entitled with the exception’s label) will redisplay the exception day’s profile
page with the new times shown for that day.
Selecting the button at the top of the exception day’s profile (entitled with the time zone’s label) will redisplay the
exception profile overview.
3 If the start and stop times are made equal, the occupation period will be ignored.
4 In order for the zone to remain in uninterrupted occupation through midnight, the end of occupation for the first day
should be set to 24.00, and the start of occupation for the next day should be set to 0.00 as these two times are considered
to be coincident.
User Level (SET: Pin Level): (analogue, constant) This is the PIN level at which a user must be logged on to be able
to change the zone parameters.
Label: (characters, constant) The label shown in the module symbol in the SET strategy page and in the Web pages.
Page: (analogue, constant) SET file strategy page number on which module appears.
Day of Week: (analogue) The days of the week run from Monday to Sunday (shown in SET as M, T, W, T, F, S, S).
Change Time number: (analogue) Each day can have a number of change times, each time having two parameters, Time
and Value.
Time: (analogue, constant) The change time in form HH.MM (hours hours. minutes minutes) on a 24 hour clock.
Value: (analogue, constant) The value of the time zone output from this change time to the next change time, currently
a status, 0 or 1 (on or off).
Label: (characters, constant) The label shown in the SET dialogue box and in the Exception Web pages.
Priority: (analogue, constant) The priority of the exception. If two exceptions overlap the exception with the highest
priority is applied. Priority range is 1 to 16 with 1 being the highest priority.
Start Day: (analogue, constant) The day of the month when the exception starts.
Start Month: (analogue, constant) The month when the exception starts.
End Day (SET: Stop Day): (analogue, constant) The day of the month when the exception stops.
End Month (SET: Stop Month): (analogue, constant) The month when the exception stops.
Use: (analogue, constant) This can be set to either Next, Every, or Free
Next: The exception will be used for the next period it occurs and will be set to Free use after its stop date.
Every: The exception will be used every year
Free: The exception will not be used
Change Time number: (analogue) The exception day can have a number of change times, each time having two
parameters, Time and Value.
Time: (analogue, constant) The change time in form HH.MM (hours hours. minutes minutes) on a 24 hour clock.
Value: (analogue, constant) The value of the time zone output from this change time to the next change time, currently
a status, 0 or 1 (on or off).
TYPE
co d e
SET Web Low High
page
Controller Parameters
Value - R V 0 1 0 The current zone state according to its
OUTPUT
occupation time (0 or 1, Off or On). Can be
connected to a digital input.
User Level R/W R/W P 0 100 0 The PIN level required to change the time
Day of Week - - Wn n=1 n=7 1 The day of the normal week to which
1 = Monday following parameters apply
7 = Sunday
Change Time - - Wn(Pm) m=1 m=10 0 The change time number within the day
number
Time R/W R/W Wn(Pm(T)) 00.00 24.00 00.00 The change time based on 24 hour clock
CONST
hh.mm
hh=0 to 24
mm=0 to 59
CONST
Value R/W R/W Wn(Pm(V)) 0 1 0 The occupation state from the change time,
0=Off, 1=On
Controller Parameters - Exceptions
Exception - - Cn n=1 n=50 0 The exception day to which the following
parameters apply
Label R/W R/W Cn($) 0 30 0 The label of the exception used in Time zone
CONST
Start Day R/W R/W Cn(S) 1 31 1 The day of the month from which the
exception is to apply
Start Month R/W R/W Cn(O) 1 12 1 The month from which the exception is to
apply
End Day R/W R/W Cn(E) 1 31 1 The day of the month from which the
(SET: Stop Day) exception stops
End Month R/W R/W Cn(T) 1 12 1 The month in which the exception stops
(SET: Stop Month)
Use R/W R/W Cn(U) 0 2 0 The use of the exception:
CONST
TYPE
comms
co d e
SET Web Low High
page
Controller Parameters -Exceptions (continued)
Change Time - - CnD1(Pm) m=1 m=10 0 The change time number within the day
number
Time R/W R/W CnD1 00.00 24.00 00.00 The change time based on 24 hour clock
CONST
(Pm(T)) hh.mm
hh=0 to 24
mm=0 to 59
CONST
Value R/W R/W CnD1 0 1 0 The occupation state from the change time,
(Pm(V)) 0=Off, 1=On
SET Associated Parameters
Display Mode - - - - - - The display mode of the time zone strategy
symbol on the strategy page. Either Graphic
or Data.
Setting up a user module involves assigning it a 4 digit PIN (Personal Identification Number) and an authority Level (User
Level) in the range 0 to 100. It also has a Name, and a Password.
If a user module has been set up in a controller then the PIN is used to protect text communications with the controller
(e.g. supervisor changes, display panel changes, IC Comms, Timemaster synchronisation, SET Live Values/ Live Edit).
The Name and Password are used to protect browser access to Web Pages, and configuration file Upload and Download.
Some changes require authority at or above a certain fixed level before they can be made. Other changes have levels that
are configurable (e.g. Knob Value, Switch Status, Time Zone occupation parameters). Because of this there may be many
user modules set up in an IQ3 enabling different users to have different sets of parameters that they may change.
If a user forgets his PIN then a default PIN which has a level 99 may be supplied by the Trend Technical Support Dept.
for use on that day.
If a user forgets his Name and Password the Web page gives a security key (application key) which can be given to Trend
Technical support and they will return a temporary user name and password which can be used until midnight that day.
Once a user has logged in with the temporary user name and password and subsequently logged out, the application
key and temporary user name and password will change. They will also change at midnight.
Web page security is also protected by a password timeout, a defined Home page, and restriction of the banner links
to other pages (View Defaults).
The user module appears on the strategy page, but doesn’t require to be entered into the sequence table.
34.1 Symbol
user 1
U1
**** O
User
100 Level
15 Timeout
Security key
Changes by text comms directed to more than one controller on local Lan or all Lans
(i.e. local global or global global text comms) >=99
Configuration file download, module changes (excluding configurable user levels, see 34.4.2 below),
and text comms directed to one controller (i.e. directed text comms) >=95
Restricts the user to only view Sensors, Digital inputs, Knobs, Switches, Drivers, Time Zones, Time,
Plots, Users, and to only view Alarm enables, alarm levels, Label, Units on module details web pages: <80
Prevents changes to Knobs, Switches, and Time zones from being adjusted,
even if the user level required for adjustment is zero. -1
Note that if any user is created with with a password less than 99, or if a Guest user is set up without a password (see
34.6.1 below), it will not be possible to download strategy files unless there is also a user set up with a password =>99.
It is recommended to always create an Administrator user with level 100, before creating any other users. If you try to
create a first user without a password =>99, SET will give the operator a warning.
If a configurable user level is set up there must be a User module set up in the IQ3 with a user level equal to or greater
than the configured user level; if this is not done the parameter will not be able to be changed (unless there are no user
modules set up).
If the Knob, Switch, or Time Zone has a user level of 0, it is unprotected and can be altered without logging on. However,
if the user is logged on with a level of -1 the values cannot be changed (see 34.4.1 above).
1) Supervisor and Display Panel changes (e.g. 963, 916, IQView, SDU, RD)
2) Other Text Communications changes (e.g. IC Comms, Timemaster time synchronization message, SET Live
Values/Live Edit)
e.g. Timemaster synchronisation is directed to more than one controller on all Lans, so requires a PIN of level >=99.
When a controller initiates an IC communication, or when a Timemaster sends a time synchronisation message it will
include the PIN from User 1 module (if set up).
A user module must be set up in the receiving controller(s) with the same PIN and with an appropriate user level. A Data
To IC Comms will require a PIN level >=95, whereas a Global To IC Comms (or Min, Max, Sum or Average) or a Time master
synchronisation message will require a password level >=99.
e.g. Browser access to web pages to view all module types and parameters but to make no changes requires User Name
and Password of level >=80, <95.
e.g. SET Configuration file download requires User Name and Password of level >=95
Note that a download also requires a PIN to be set up as module parameters are changed by a download.
When a user accesses the Welcome web page of a controller with no user modules set up (i.e. no security) he will be
given the status of System Guest and a user level of 100; this gives total access as described above. However, if there
are any user modules set up he will be given a user level of -1 which will allow modules and their parameters to be viewed
but not adjusted.
In order to limit the access of a casual visitor further, a special user module with User Name, ‘Guest’, can be set up without
a password. This can have a defined Level, Home Page, and View Defaults. This enables the access of a casual visitor
to be limited. SET has the Guest User (Not Logged in) check box to facilitate creation of this type of user module.
Note that if this special Guest user module is set up with a Home Page, on accessing the site, the Home Page will be
displayed, not the Welcome web page.
If the Guest user module is set up with a password it loses its special purpose, and a casual visitor will become a System
Guest as described earlier.
When the user logs on to the web server a dialogue box is displayed requesting the user to provide both User Name
and Password. A match to one of the user modules gives the user the module’s user level and can direct the user to Home
Page (if defined in the user module). The pages the user can access via the links on the banner across the top of the page
and the Navigator on GraphIQs pages are restricted if the View Defaults are set up (see 34.6.1.1 below).
The login access will expire after a configured Timeout period of key inactivity (default 15 minutes after last key press).
In order for the user to securely logout, or login as a different user, the instance of web browser must close, therefore
once the logout button has been selected, the user is left with no option but to close down that instance of browser.
Likewise, once the user has successfully logged in, the login button is no longer available, and the user must load a new
browser instance to login as a different user.
Note that guest logins (System Guest or ‘Guest’ module without password) will only logout as a result of the timeout;
this is because the guest user password may be shared between multiple users.
Also note that the same user name and password may be used to gain access to the system on more than one browser
instance. However, if a user explicitly logs out, pressing keys to request further displays or changes on another browser
will result in a session expired error, and that browser will have to be closed.
Banner links
The last View Default is View Navigator which can be used to turn off the Navigator displayed on the GraphIQs pages.
Navigator
The removal of these links can be used to stop the user having easy access to other pages in the controller.
Note that the logon/logoff link shown in the banner cannot be turned off.
The Home Page is defined by a URL code that has to be entered. SET has a useful drop down list of codes, and selecting
the Home Page Browse button produces the GraphIQs pages navigator from which a GraphIQs page may be selected.
A module overview page is selected by a URL code of the form: <Module Type>.htm
e.g. S.htm will select the sensors module summary page
A module details page is selected by a URL code of the form: <Module Type><Module Number>.htm
e.g. S1.htm will select the sensor details for sensor 1.
The user module cam be both created and deleted in SET by changing and downloading the strategy file.
Password: (characters, constant) The Password used with the User Name for logging in on the web page; also used for
security on file upload/download. Underlined on the web page as it selects the web page create user/confirmation page
so that Password and User name are created together.
PIN: (analogue, constant) The PIN, 4 digit personal identification number, used for security on text comms; often required
to be entered into supervisors and display panels to enable the modification of controller parameters.
Level: (analogue, constant) The user level for this module. This defines the communications and changes that can be
made when logged on using this module’s User Name and Password, or using its PIN.
Home Page: (analogue, constant) This specifies the web page that is displayed after the user logs in on web pages, or
on entry with User Name, ‘Guest’ with no Password (see 34.6.1.2 above).
View Defaults
View Alarms: (digital, constant) Switching this off removes the Alarm Log link from the web page banner.
View Time Zones: (digital, constant) Switching this off removes the Time Zones link from the web page banner.
View Modules: (digital, constant) Switching this off removes the Modules link from the web page banner.
View GraphIQs: (digital, constant) Switching this off removes the GraphIQs link from the web page banner..
View Navigator: (digital, constant) Switching this off stops the user viewing the Navigator when accessing the
GraphIQs web pages. (The Navigator is normally shown on the GraphIQ page, see 34.6.1.1 above)
Guest User (Not Logged in) (SET only): This sets up the user module to be the Guest user module. This has the label
‘Guest’ and a blank password. The other parameters can be set up as required. The Guest user module enables the access
available to the casual visitor to be defined (e.g. by giving the user module a Level, Home Page, View Defaults) - see 34.6.1
above
Page: (analogue, constant) SET file strategy page number on which module appears.
TYPE
co d e
SET Web Low High
page
Controller Parameters
Logged On - R O 0 1 0 The logged on state. Indiactes a user is
OUTPUT
logged on using this module.
Logged On=1
Logged Off=0
Can be connected to a digital input.
User Name R/W R/W $ 0 30 blank Used with Password for logging on to web
CONST
(SET: Name) characters page; also used for file upload/download
Password R/W R/W W 0 30 blank Used with User Name for logging on to web
CONST
characters page; also used for file upload/download
PIN R/W R/W P 0000 9999 blank A 4 digit number used for security on text
CONST
communications, e.g. entered into
supervisors and display panels to change
controller parameters
Level R/W R/W L -1 100 100 The user level associated with the user
CONST module; defines what communications and
changes can be made when logged on with
this module
CONST
Timeout R/W R/W T 0 15 1 (Web pages) The time after last key press
minutes that user will be logged off
Home Page R/W R/W H valid URL blank (Web Pages) A URL of the page that will
CONST
View Alarms R/W R/W V 0 1 1 (Web Pages). Set to zero to remove alarm
log link from banner
View Time Zones R/W R/W Z 0 1 1 (Web Pages). Set to zero to remove time
zone link from banner
View Modules R/W R/W M 0 1 1 (Web Pages). Set to zero to remove module
link from banner
View GraphIQs R/W R/W G 0 1 1 (Web Pages). Set to zero to remove
P ages GraphIQs link from banner
View Navigator R/W R/W V 0 1 1 (Web Pages). Set to zero to remove
Navigator from GraphIQs pages
P age R/W R/W p 0 255 0 Number of page containing module in SET
file
X co-ordinate R/W R/W x 0 255 0 X co-ordinate of module on strategy page
Guest User (Not - - - 0 1 0 Selects this user module to be a' Guest' user
Logged in) module. (User Name: Guest, no Password)
System aspects of vCNCs are covered in Pt. 1 section 2.5, and the connection of a supervisor using the IQ3’s vCNC is
covered in Pt. 1 section 3.3.3.
The vCNC does not exist until it is created (i.e. until it has been given an address and port number).
SET can download its configuration files to the IQ3 using another vCNC (i.e. in a 3xtend/EINC L, or an EINC, or in another
IQ3), but if it is using the same IQ3’s vCNC, the vCNC must be configured before attempting to download configuration
files. This initial configuration is performed using IPTool as explained in Pt. 1 section 5.1.
Note that SET can download a strategy file to the IQ3 over the Trend current loop Lan without recourse to a vCNC
(if /Lan option is fitted) but the other configuration files (backdrops, languages, XNC program- /XNC only) can only
be downloaded over Ethernet.
The vCNC is not included in the strategy file, it does not appear on the strategy page, and it does not require a sequence
table entry.
The IQ3 vCNC does not exist until it is given an outstation (node) address and port number. Once these are set up it will
be shown on the network map (e.g SET navigator).
Note that IPTool cannot create a vCNC if the IQ3 has security set up (i.e. a user module set up).
The vCNC is created by double clicking on the controller row in the display and then selecting the Auto-Number vCNCs
button.
This will create a vCNC with Status ?, and auto-numbered Node (address) and Port (number).
The node address and port number can then be changed by double clicking on the vCNC’s row in the vCNC box which
displays the Virtual CNC Setup box.
This enables the Node (address) and Port (number) to be changed. If ‘Use Default Port’ is selected, the port number will
automatically be set to the node address plus 10000, otherwise the port number can be keyed in.
The vCNC information is then sent to the controller by selecting the WRITE DATA button. The data is successfully
written when the green tick is seen next to the Identifier box, and the vCNC Status changes to VC Avail(able).
When a device is connected the Status changes to ‘VC conn’, and the IP address or Hostname would show the details
of a connected device, however, the display of the IP address/Hostname does not operate in IQ3.
These details are also shown for the highlighted device in the vCNC box.
Port Number (IPTool: Port): (analogue, constant) The port number attached to the CNC. Since the virtual CNC and the
IQ3 are on the same IP address, they need different port numbers; the IQ3 uses port 80 (standard for web browsers), and
the virtual CNC needs to be set to a port number suitable for the IT system.
Label: (characters, constant) The label of the vCNC. It can only be viewed or changed in the web page.
Socket Timeout : (analogue, constant) This parameter is not use for IQ3. It is the timeout which the vCNC would use
for alarm mode which is not supported in IQ3.
IP Addr / Name: This parameter is not used on IQ3. It is used by 3xtend/EINC L or EINC where it is the IP address
or Hostname of the device connected to the vCNC.
co d e
IPTool Web Low High
page
Controller Parameters
CONST
Label - R/W $ 0 20 Virtual The label shown on the vCNC web page
characters CNC 1
Address R/W R/W A 1 119 101 Node address of this vCNC on the local Lan.
CONST
Port Number R/W R/W P 1 32767 10101 Port number of vCNC at IP address of IQ3.
(IPTool: Port) Defaults to 10000 plus node address
Socket Timeout R/W R/W T - - 65535 Not used on IQ3
The XNC Interface module SET Dialogue Box shows the available inputs and outputs provided by the TCL application
(created using the Trend Custom Language, TCL, in TCLTool2). These inputs and outputs are also available in SET
as connectives to be placed on the strategy page.
The XNC Interface module is not placed on the strategy page and does not require a sequence table entry.
The XNC Interface module web page displays information which can be used by the TCL programmer when debugging
his TCL application.
Connectives
The initial value of a Store, Input, or Output can be set up by double clicking on the appropriate value and editting it.
The label of an Input or Output can be set up by double clicking on the appropriate label and editting it.
Note that Stores’ names cannot be changed as they may be referenced in the TCL application.
If required to set the labels or values back to the settings specified in the XNP file, the Overwrite Labels button (or
Overwrite Values button) is first selected followed by the Reload button.
A connection between an XNC interface module input and a strategy module knob or switch output can be set up by
dragging a knob, or switch from the connective list to the appropriate input connection. Similarly a connection between
an XNC interface module output and a strategy module internal sensor or internal digital input can be set up by dragging
an internal sensor, or internal digital input from the connective list to the appropriate output connection.
Alternatively connections to these modules or to any other strategy modules’ inputs or outputs can be made by placing
the appropriate XNC interface connective on the strategy page and dragging a connection in the normal way. Note that
the XNC interface module input connectives are the only input connectives in the IQ3 connectives list.
The Add knobs, Add Switches, Add Sensors, or Add Digins enable additional modules to be created and added to the
connectives list without having to go back to the strategy page.
TYPE
comms
co d e
TCL SET Web Low High
Tool2 page
Controller Parameters
Label R/W R R/W $ 0 20 Program The label for the TCL application; The label
(SET: App. Name) Name used when TCL alarms are sent
CONST
(TCLTool2: Program characters set up in
Name) TCLTool-
2
CONST CONST
Program Author R/W R R a 0 30 null The author of the TCL application
characters
Program Version R/W R R n 0 30 null The version of the TCL application
characters
ID (SET only) R/W R - m - - set up in The TCL application identifier generated in
CONST
TCLTool- TCLTool2
2
Program State R - R P 1 10 3 The current state of the TCL application.
(Use in debugging)
1=Stopped
2=Loading
3=Running
STATUS
4=At breakpoint
5=Debug
6=Error
7=No File
8=File not found
9=Bad File
10=brIQs exceeded
Debug Active R - R D 0 1 0 TCLTool2 is running the TCL application (e.g.
STATUS
GENALARM command
characters
Last Error R - R l (lower 0 128 blank Number and description of last error found.
ca se L ) Errors are listed in IQ3/XNC TCL Manual
STATUS
TYPE
co d e
TCL SET Web Low High
Tool2 page
Controller Parameters
CONST
Input Label R/W R/W - In$ 0 30 null The label of the Input
characters
Input Value R/W R/W - InV -1020 +1020 0 The value of the Input. ('n' is input number 1
INPUT
to 1000). Can be connected to an analogue
or digital output.
Output Label R/W R/W - On$ 0 30 null The label of the output
CONST
Output Value R/W R/W - OnV -1020 +1020 0 The value of the Output. ('n' is output number
1 to 1000). Can be connected to an
OUTPUT
analogue or digital input.
Store-Name R/W R/W - Sn$ 0 30 null The name of the Store. ('n' is store number 1
characters to 200)
Store-String Value R/W R/W - SnV null The value of the Store
Inputs Total R/W R/W - - 0 1000 0 The number of inputs set up.
A1.1.2 Plots
The plot module now allows any connectable output to be logged rather than just sensor values.
Both Triggered and Periodic types have an option to generate a Log Full output and cease logging until the plot
buffer is cleared (Stop When Full option).
All plot types can be read over BACnet but only periodic plots are fully BTL (BACNet Testing Laboratory)
compliant.
See Pt. 2 section 25
A1.1.5 BACnet
A1.1.5.1 New BACnet BIBBS
Ref. 1.2 DS-COV-B Data Sharing-Change Of Value
See COV reporting below:
Ref. 4.2 T-VMT-I-B Trending-Viewing and Modifying Trends Internal-B
Ref. 4.5 T-ATR-B Trending-Automated Trend Retrieval-B
These two involve the use of the BACnet Trend Log object which corresponds to the Plot module.
The 3 bit field is used to enable/disable transitions to the BACnet states: Normal, Off Normal, and Fault.
000
To-Normal To-OffNormal
To-Fault
A “fault” condition is a malfunction, nearly always representing a failure within the automation system itself. An
“offnormal” condition is a condition within the system that is not normally expected or is outside the bounds of
ideal operation. A “normal” condition is anything else.
The way in which these transitions correspond to the various Trend alarms is shown in the table below is described
in Pt. 1 section 12.7.4.2
BACnet IC Comms supports Data From, Data To, and Global To Direction Classes, but not Minimum, Maximum,
Sum, or Average.
The Data From, Data To, and Global To BACnet IC Comms supports Analogue and Digital Bit Variable Types, but
not Digital Byte.
In order to send a BACnet IC Comms a Non-Trend Device module (NTD module, see 1.6.8 below) must be set up for
the BACnet device being communicated with.
(See Pt. 2 section 15.3)
A1.6.1.2 Link/Local
If the DHCP server fails to respond, the IQ3 will enter link/local mode where it will negotiate its IP address with the
other devices on the Ethernet segment. In this mode the subnet mask will be set to its default and the Router 1, WINS
servers, and DNS servers parameters will remain at their last settings.
Note that the link/local negotiated IP addresses start at 169.254.0.0 with subnet mask of 255.225.0.0. If a device wishes
to communicate with an IQ3 in link/local using IP addressing (e.g. to construct an IQ Lan on Ethernet), it must be on
the same subnet so defined.
TX RX
Address/
OK
Network
baud rate
This feature also enables the strategy file (but not other configuration files: language, backdrop, and XNC (for /XNC/
versions only)) to be downloaded from SET via the current loop. This change also enables the strategy (but not other
configuration files) to be downloaded from SET via the local supervisor (RS232) port.
The Lan auxiliary board is fitted in the auxiliary board slot, and has a special auxiliary board cover which enables access
to the auxiliary board switches and connectors.
The auxiliary board also contains the circuit for a backup battery so it can also fulfil the function of XCITE/BBC (battery
backup card). However, the CR2032 battery is not supplied so must be purchased separately if a battery backup option
is required.
The board contains the normal hardware for an IQ system current loop Lan node:
Address/Baud rate switch: The address on the Lan is set by poles 1 to 7 in range 1, 4 to 9, 11 to 119 and must
be unique on the Lan. The strategy address module Local Address parameter monitors the address switch settings
and is read only for IQ3/LAN. The baud rate is set by poles 8 to 10 in the range 9k6, 19k2 and must match the other
nodes on the Lan. The baud rate is the read only parameter in the network 2 module. Note that zero address reset
is not supported.
Network terminals: The network terminals facilitate connection of 4 wire cables (enabling a ‘weaving’ connection
method).
Indicators: The standard LEDs are fitted (TX, RX, and network OK).
Bypass relays: The board contains 2 changeover relays which bypass the receive and transmit circuitry and
maintain network integrity during power fail.
RTS/TXEN
CTS/RXEN
Communications type LEDs
RS485 terminals RS485 RS232
0V A B RA RB
T T
RS232 connectors: There are two RS232 connectors, the 9 way D type plug, and an RJ11 socket. They are connected
in parallel, and only one of these connectors should be used at a time. The maximum distance to the connected device
is 30 m.
The RS232 can be used with or without limited handshaking (CTS/RTS) as specified by the TCL application.
Note that the 9 way D type terminal 4 (normally DTR) is held high so that the RS232 convertor can be powered
from the connector (see Compatibility section below).
RS485 Terminator Switch: The terminator switch is used to switch the two 120 ohm terminating resistors in or out
of circuit. They should be switched into the circuit for RS485, and switched out for RS422 (not used for RS232).
A B RA RB A B RA RB
0V T T T T
0V
A B TA TB RA RB
TCL LEDs: These 4 LEDs are switched on and off by the TCL code they are referenced 1 to 4, top to bottom. There
is a space on the auxiliary board cover label on which to write the description of each LED’s function.
TX
LED 1 (yellow)
RX LED 2 (green)
RTS/TXEN
CTS/RXEN
LED 3 (red)
LED 4 (yellow)
Communications LEDs TCL LEDs
A1.6.4 IQ3../.../XNC/..
The IQ3../.../XNC/... provides a flexible way of interfacing the IQ system with 3rd party systems. It utilises both
standard IQ configuration modules, and the Custom Language (TCL) to present information from other systems as
though it were from an IQ controller. It also allows parameters within the 3rd party system to be adjusted from IQ system
Supervisor, and Tool software. The optional serial auxiliary board (/SER/) provides an additional RS232 or RS485 (2/
4 wire) (or also RS422) port for communicating with other devices.
The firmware within the IQ3/XNC consists of two parts: the device part, and the XNC part. The device part consists
of standard IQ3 firmware and operates in the normal way. The XNC part runs a Custom Language program (TCL
application). It communicates with the 3rd party system, passing information from the IQ3 to the 3rd party system,
and writing values from the 3rd party system to the IQ3. It can also communicate directly with IQ system devices.
Communications with the 3rd party system and IQ system devices may be via Ethernet, IQ system current loop network
(if /LAN/.. option fitted), or RS232/RS485 (if /SER/.. option fitted).
Note that the XNC part may also be used to enhance the strategy without recourse to a 3rd party system.
The XNC part can be created by Trend Interface Specialist (TIS) who can provide both bespoke applications and
generic applications for commonly used equipment. The TIS may provide the application in soft format, or pre-loaded
into the IQ3. The application can be tied to one controller or available for general download. Information about the
TISs can be found on the Trend Partnernet website
Note that the RS232 to RS485 convertor used in the NBOX/XNC220/485 or the ENC2/S may be connected directly
to the IQ3../.../XNC/SER/... RS232 connector without using the 9 way to 25 way D type cable supplied with these units.
This facilitates the upgrading of NBOX/XNC220/485 or ENC2/S to IQ3../.../XNC/SER/... .
Configuration: The XNC part is configured using the TCLTool2 which runs within SET; SET is then used to link the
TCL variables to strategy variables and to download the resulting XNC program file.
Note that the XNC program file should be downloaded before the strategy file is downloaded.
The strategy file and other configuration files (language, backdrop, and XNC) can be downloaded and uploaded via
Ethernet, but only the strategy file can be downloaded or uploaded via the current loop Lan (IQ3/LAN only).
Communications: The XNC part is able to communicate directly via the following ports:
Serial port (if /SER/... option fitted) set to either RS485 2 wire, RS485 4 wire, or RS232.
Ethernet using TCP/IP
CNC using IQ3’s vCNC.
Custom Language: This is a programming language, based on BASIC, which is used to write the TCL application.
Amongst other things it enables interfacing between the IQ System, and 3rd party systems. It is an enhanced version
of the language used in NBOX/XNC220. A full description of the language can be found in the IQ3/XNC Interface
Manual TE200918.
Note that the TCLTool2 and its documentation are only supplied on completion of the TCL training course.
The TCL language is for this version of IQ3 (see specification). A TCL application written for NBOX/XNC220 can
be modified to run on IQ3 using TCLTool2.
Modules: The IQ3/XNC includes all the standard IQ3 modules, plus the XNC Interface module.
The XNC Interface module contains the TCL Application, the Stores and SavedVars areas, and the inputs and
outputs.
The TCL application is the TCL code that has been written for the required application using TCLTool2. It reads
information from the inputs, stores, SavedVars areas and by communications with 3rd party systems. It processes
the information and outputs it to the outputs and by communications to 3rd party systems and/or IQ system
devices.
The Stores consist of 200 locations where user-defined constants are stored. They are defined using TCLTool2
when creating the TCL application and cannot be changed from the running application. They are re-initialised
after power failure.
The SavedVars consists of up to 100 locations where values (that will not be lost due to a power interruption)
may be written to and read from by the TCL application.
The Inputs consist of up to 1000 points that can be connected to IQ3 module outputs using SET. They enable
the TCL application to use strategy values and labels.
The Outputs consist of up to 1000 points that can be connected to IQ3 module inputs using SET, They enable
values and labels from the TCL application to be used by the strategy.
The number of these items used by the TCL application affects the available capacity of the IQ3 for strategy modules.
As explained in the IQ3 data sheet, the capacity is measured in brIQs. The TCL application consumes brIQs as follows:
5 brIQS :per store location, SavedVars location, input point, output point
20 brIQs :per line of TCL code
The IQ3/XNC has a greater number of brIQs than the standard IQ3 as shown in the table below:
1 2 3 4 5 6 7 8 9 10 11 12
output LEDs
NC
1
C NC
2
C NC
3
C NC
4
C State Switch Relay State Overridden Output LED
Postion LED (red) (yellow)
H
A
Manually Hand ON ON ON
O
override overridden ON
LEDs
Manually Off OFF ON OFF
overridden OFF
The HOA switch position is fed back to the IQ3 strategy driver module from where it can be viewed using webpages,
SET or supervisors.
Please note that with IQ3 v1.22, in order for the IQ3’s webpages to run correctly within Internet Explorer, the
operating system environment in which Internet Explorer runs must have the Sun Java virtual machine v1.1 or
greater installed (this can be downloaded from Java.com). If the system has the Microsoft version of the Java virtual
machine installed, it must be replaced by the virtual machine from Sun Microsystems.
Site Name
From email address
Alarm Description
Item label
Controller identifier
Site Name
Group label
Controller identifier
Item label
Alarm description/Transition
Time/date
Extra text
0 a G1
0 b
0 c
0
0 d N1
D G1D L
0 D
e
0 f TO
0 Remote Address
0 g 0 Remote Lan
0 Message Interval
0 h Failed Bit
D TO A
A byte IC Comm will be received at the far end by a digital byte module in an IQ3 or as a byte in an IQ2.
The result of items 8.3 and 8.4 changes the IC Comms compatibility table shown in the data sheet to that below:
Configured Configured Configured
IC Comms Type in IQ2 in IQ3xcite in IQ3xcite
to IQ3xcite to IQ2 to IQ3xcite
All IC Comms are now available with the exception of Data From comms (either initiating them or responding to them).
Note that IC Comms with IQ1 v3 controllers are similar to those with IQ2 controllers except the IQ3 can only receive
messages (i.e. Data To from IQ1), not send them. However, IC Comms with IQ1 v4.1 or greater controllers can be
considered to be the same as those with IQ2 controllers.
The receipt of IC Comms with an analog node or digital bit/byte is implemented by creating analogue node or digital
byte modules during the strategy creation process on SET.
A1.11.10 Performance
V1.2 provides access to logs, and faster general operation.
A1.11.12.2 RD:
RD-IQ can be used with IQ3. It is a wall mounting temperature sensor and 3 digit display. It has the following variants:
RD-IQ/K: Room display with local temperature sensor and setpoint control
RD-IQ/KOS: As RD/K plus occupation override and occupation status display.
RD-IQ/KOSF: As RD-IQ/KOS plus fan speed control.
It connects to the IQ3 via RS232, and it can communicate only with that IQ3, so the local supervisor port address
must be set to zero. By default it accesses fixed strategy items (although these can be changed using the front panel
buttons:
Local temperature S9
Setpoint K1
Occupation status K6
Fan speed status K7
A1.11.12.3 NDP
Note that the NDP is not compatible with IQ3; it will not recognise an IQ3 connected to its network.
A1.13.1 International
A software tool is available to IQ system international suppliers to enable language files to be created. The language
files are stored in SET v5.0, and the required files can be selected for each SET project. English is always available
in the controller but SET enables a default language as well as additional languages to be selected. The appropriate
language files will be downloaded to the controller when the strategy is downloaded. In the controller the Address
module has a new language parameter which will be set by default to the default language, but can be changed to
any one of the other available language files or English (e.g. change to English by setting the language parameter
to ‘english’ on the address module webpage)
A1.13.5 Webpages
There are various improvements:
In the GraphIQs pages a link to another controller no longer requires the user to log in again.
GraphIQs’ backdrops can now be cached by the web browser reducing the time required to re-display webpages (this
has significantly improved operation with a PSTN modem).
There is a new presentation format for PDAs and Windows CE browsers. GraphIQs pages are shown without the
configured backdrop. (Note that display of log graphs is not possible on these browsers)
A1.14.1 Ethernet
IQ3 uses Ethernet and TCP/IP networking technologies. Specifically the addressing is different, (See Data Sheet,
Ethernet Manual, IP Tool Manual). Also see Routers section below. IQ3 constructs virtual Lans on Ethernet, but
cannot directly access IQ system current loop Lans; this can be done via an EINC.
A1.14.7 Displays
The SDU-xcite (4 line display panel) is the local display panel for the IQ3. It enables the monitoring of modules, and
adjustments (knobs switches, time zones) under password control. The IQ3 does not support the 2 line display panel
(DP), or the networked display panel (NDP). (See IQ3 Data Sheet, SDU Data Sheet). IQView is the network display
for IQ systems including IQ3 systems
A1.14.14 Security
The user module has been extended to provide security for web access (See security section below). Note that if the
PINs or passwords are forgotten contact Trend Technical Support for assistance.
A1.14.16 IC Comms
IQ3 has a subset of IQ2 comms. In particular it does not have Data From comms. If it is due to receive values from
another controller, analogue or digital byte modules as appropriate must be created in SET. (See Data Sheet, SET
Manual). Note that the sensor alarm bit string is only 4 wide in IQ3 (ROLH) so only 4 alarm bits are sent with IC Comms.
A1.14.17 Timemaster
Timemaster functionality is slightly different. IQ3 will not provide timekeeper function for IQ90s. On a mixed system
with old IQs, an IQ3 must be timemaster. (See Data sheet). The switch to turn on the Timemaster function in the IQ3
controller is ‘Timemaster’ (on/off, I=ON; text comms A), as opposed to a non-zero ‘Change by’ parameter (text comms
G) in IQ2 controller
Code Property
CI COV_INCREMENT
CB COV_RESUBSCRIBE_INTERVAL
CT CURRENT_NOTIFY_TIME
DR DATABASE_REVISION
DT DATELIST
DS DAYLIGHT_SAVINGS_STATUS
DB DEADBAND
DC DERIVATIVE_CONSTANT
DU DERIVATIVE_CONSTANT_UNITS
DN DESCRIPTION
DH DESCRIPTION_OF_HALT
DV DEVICE_ADDRESS_BINDING
DY DEVICE_TYPE
DG DIRECT_READING
ED EFFECTIVE_PERIOD
ET ELAPSED_ACTIVE_TIME
EL ERROR_LIMIT
EE EVENT_ENABLE
EP EVENT_PARAMETERS
ES EVENT_STATE
EM EVENT_TIME_STAMPS
EY EVENT_TYPE
EH EXCEPTION_SCHEDULE
FV FAULT_VALUES
FB FEEDBACK_VALUE
FM ACCESS_METHOD
FS FILE_SIZE
FY FILE_TYPE
FR FIRMWARE_REVISION
GL GROUP_MEMBERS_LIST
HL HIGH_LIMIT
IT INACTIVE_TEXT
IO INSTANCE_OF
IC INTEGRAL_CONSTANT
IU INTEGRAL_CONSTANT_UNITS
IP IN_PROCESS
IN ISSUE_CONF_NOTIFICATIONS
LR LAST_RESTORE_TIME
LV LIFE_SAFETY_ALARM_VALUES
LM LIMIT_ENABLE
LD LOCAL_DATE
LT LOCAL_TIME
LN LOCATION
LB LOG_BUFFER
LP LOG_DEVICE_OBJ_PROP
LE LOG_ENABLE
LI LOG_INTERVAL
LL LOW_LIMIT
MQ MAINTENANCE_REQUIRED
MF MANIPULATED_VAR_REFERENCE
MS MAX_SEGMENTS_ACCEPTED
MO MAXIMUM_OUTPUT
MV MAXIMUM_VALUE
MT MAXIMUM_VALUE_TIMESTAMP
MA MAX_APDU_LENGTH_ACCEPTED
MI MAX_INFO_FRAMES
MM MAX_MASTER
MP MAX_PRES_VALUE
Code Property
MB MEMBER_OF
mF MINIMUM_OFF_TIME
mN MINIMUM_ON_TIME
mO MINIMUM_OUTPUT
mV MINIMUM_VALUE
mT MINIMUM_VALUE_TIMESTAMP
mP MIN_PRES_VALUE
ME MODE
ML MODEL_NAME
MD MODIFICATION_DATE
NC NOTIFICATION_CLASS
NT NOTIFICATION_THRESHOLD
NY NOTIFY_TYPE
NR NUMBER_OF_APDU_RETRIES
NS NUMBER_OF_STATES
OI OBJECT_IDENTIFIER
OL OBJECT_LIST
ON OBJECT_NAME
OR OBJECT_PROPERTY_REFERENCE
OY OBJECT_TYPE
OP OBJ_PROP_REFERENCES_LIST
OE OPERATION_EXPECTED
OT OPTIONAL
OU OUTPUT_UNITS
OS OUT_OF_SERVICE
PO POLARITY
PV PRESENT_VALUE
PY PREVIOUS_NOTIFY_TIME
PR PRIORITY
PA PRIORITY_ARRAY
PW PRIORITY_FOR_WRITING
PI PROCESS_IDENTIFIER
PG PROGRAM_CHANGE
PL PROGRAM_LOCATION
PS PROGRAM_STATE
PM PROFILE_NAME
PP PROPORTIONAL_CONST
PU PROPORTIONAL_CONST_UNITS
PN PROTOCOL_REVISION
PC PROT_CONFORMANCE_CLASS
PJ PROT_OBJ_TYPES_SUPPORTED
PD PROT_SERVICES_SUPPORTED
PT PROT_VERSION
RO READ_ONLY
RH REASON_FOR_HALT
RT RECIPIENT
RL RECIPIENT_LIST
RN RECORDS_SINCE_NOTIFICATION
RC RECORD_COUNT
RB RELIABILITY
RD RELINQUISH_DEFAULT
RQ REQUIRED
RV RESERVED_18
RS RESOLUTION
SM SEGMENTATION_SUPPORTED
SL SESSION_KEYS_LIST
SP SETPOINT
SR SETPOINT_REFERENCE
Code Property
SG SETTING
SD SILENCED
SA START_TIME
ST STATE_TEXT
SF STATUS_FLAGS
SO STOP_TIME
SW STOP_WHEN_FULL
SS SYSTEM_STATUS
TD TIME_DELAY
TA TIME_OF_ACTIVE_TIME_RESET
TS TIME_OF_STATE_COUNT_RESET
TR TIME_SYNC_RECIPIENTS
TC TOTAL_RECORD_COUNT"
TV TRACKING_VALUE
UN UNITS
UI UPDATE_INTERVAL
UO UTC_OFFSET
VS VALID_SAMPLES
VV VARIANCE_VALUE
VI VENDOR_IDENTIFIER
VN VENDOR_NAME
VC VT_CLASSES_SUPPORTED
WK WEEKLY_SCHEDULE
WI WINDOW_INTERVAL
WS WINDOW_SAMPLES
ZM ZONE_MEMBERS
The message MUST contain the Conditional request part: {M=OO??} or {S=????OO??}, and the Last address and visitor
count suffix: ;AD=0,CT=0.
The Label matching must be separated by a back slash \ NOT a forward slash /.
The IQ3 cannot process complex requests that contain more than 1 test e.g. AHU1\SpaceTemp{M=OO??}(V>0.00,
V<100.00);AD=0,CT=0.
However the request will match with S1($=”Sensor 1") as in IQ3 the character ‘*’ is taken to mean any other characters
(so the ‘Fred’ element is ignored).
Default output ................................................................................ 407 Driver module .............................................................. 82, 249, 517
Default output level ...................................................................... 407 driver types .................................................................................... 249
Default P.V. .................................................................................... 407 driver’s priority array ................................................................... 252
default password ............................................................................. 577 droop ............................................................................................... 453
default router .................................................................. 33, 95, 426 dumb/normal switch ........................................................................ 2 7
Default settings ...................................................................... 97, 429 dummy IC Comms
Default Value ........................................................................ 407, 419 symbol ........................................................................................ 326
degrees Duplicate Address ................................................................. 163, 164
of rotation ................................................................................. 320 Duplicate Lan ....................................................................... 163, 164
delay logic module ......................................................................... 378 duration
derivative term .............................................................................. 403 plot ............................................................................................. 473
derivative time constant ..................................................... 404, 418 DVDD ............................................................................................. 164
destination module ........................................................................ 111 DVOK ............................................................................................. 164
Destination Type dynamic item
alarm ................................................................................ 173, 197 (display) ................................................................ 149, 233, 241
deviation alarm .............................................................................. 406 E
Device Dead ......................................................................... 162, 164 Earthing ............................................................................................ 6 6
Device Instance ........................................................... 58, 198, 431 EINC ............................................. 26, 27, 38, 96, 97, 132, 555
NTD ................................................................................. 438, 441 Electric Heating ............................................................................. 459
device mode .................................................................................... 429 Email Alarm Destination ......................................... 174, 197, 576
Device Object ................................................................................... 5 3 email server .................................................................................... 174
Device OK ...................................................................................... 162 email server address ..................................................... 42, 198, 426
Device Online ................................................................................ 164 email type alarm .............................................................. 31, 42, 44
device part ...................................................................................... 139 Enable BACnet Module ................................................................ 431
device view ..................................................................................... 125 Enable route ......................................................................... 169, 211
DHCP ...................................................................... 41, 42, 95, 570 Enabled ............................................................ 166, 168, 228, 253
BACnet ................................................................................ 58, 97 enter manually ....................................................... 41, 42, 96, 428
DHCP server .................................................................................. 426 enthalpy function module ............................................................ 306
DI=0 ................................................................................................ 165 error ...................................................................................... 397, 399
DI=1 ...................................................................................... 165, 227 Ethernet ................................................ 25, 31, 33, 38, 555, 580
Digin (reqd state=0) ...................................................................... 165 connector ............................................................................ 65, 67
Digin (reqd state=1) ...................................................................... 165 switch ........................................................................................... 6 7
digital .............................................................................................. 184 Ethernet address .............................................................................. 9 5
digital array .................................................................................... 581 Ethernet IP
digital bit type IC Comms ............................................................ 219 network module ........................................................................ 425
digital byte module .............................................................. 100, 219 Ethernet Lan ............................................................................ 31, 44
digital byte status ........................................................................... 220 Ethernet LED .................................................................................. 6 4
digital byte type IC Comms .................................... 219, 334, 385 Ethernet MAC address .................................................................. 430
digital connection ............................................................................ 9 8 event driven modules .......................................................... 104, 223
Digital Driver Module ................................................................... 261 event driven servicing ......................................................... 104, 581
digital input alarm ............................................................... 226, 227 Event Time Stamp ..................... 226, 227, 254, 258, 500, 501
Digital input channel ............................................................. 79, 355 Every .............................................................................................. 536
Digital Input Expander ................................................................. 309 exceptions ............................................................................ 535, 581
digital input module ....................................................................... 223 Excess current LED ........................................................................ 8 1
external .............................................................................. 99, 224 Exponent .............................................................................. 495, 512
internal ....................................................................................... 225 External Analogue Sensor ............................................................. 494
digital node ..................................................................................... 100 External digital inputs .................................... 224, 375, 377, 380
DIN rail fixings ........................................................................ 63, 76 External Digital Sensor ................................................................. 495
Direct Module Interconnection ................................................... 581 External I/O Count ........................................................................ 190
Direction External I/O Limit ........................................................................ 190
IC Comms .................................................................................. 348 External IO Enabled ...................................................................... 190
directory module ....................................................... 111, 150, 233 External IO Exceeded ................................................................... 483
disable module input ............................................................ 105, 255 external power supply ..................................................... 72, 85, 87
Display and Directory modules .......................................... 233, 241 External Text Message ................................................................. 198
Display and Directory Setup ........................................................ 150 F
Display and Directory View .......................................................... 236 Failed ............................................................................................... 197
display box ..................................................................................... 102 Failed Bit
display buttons ............................................................................... 102 IC Comms ........................................................................ 324, 347
display item .................................................................................... 149 Failed output .................................................................................. 169
display module ..................................................................... 111, 241 Failed Peripheral Interface Adapter .................................. 165, 188
Display Panel ............................................................... 21, 143, 241 Failed PROM ........................................................................ 165, 189
Display Subtype ............................................................................. 243 Failed RAM .......................................................................... 165, 189
divide by zero ................................................................................. 285 Failed RTC ............................................................................ 165, 189
divider function module ................................................................ 300 Failed Software ..................................................................... 165, 189
divisor ............................................................................................. 300 Failed to Load ................................................................................ 483
DNS server ..................................................................... 42, 95, 426 fan out logic module ...................................................................... 382
domain name .................................................................................... 4 2 FARC ..................................................................................... 165, 189
Double precision logs .................................................................... 477 fast sequence .................................................................................. 104
downgrade firmware ...................................................................... 138 fault finding .................................................................................... 157
download ................... 31, 39, 43, 44, 96, 101, 143, 545, 555 Fault State ............................................................................. 226, 254
exclusions .................................................................................. 127 FCAN .................................................................................... 165, 189
strategy page ............................................................................. 130 FDRT .................................................................................... 165, 189
to multiple controllers ............................................................. 129 Feature Error ........................................................................ 134, 483
to single controller ................................................................... 128 Feed Forward Control ................................................................... 413
D P ................................................................................................... 581 Feedback ............................................................................... 269, 279
drive position ....................................................................... 273, 279 Field network ................................................................... 23, 24, 26
File Error alarm ........................................................ 135, 165, 189 high water mark ........................................................ 180, 197, 207
file info ........................................................................................... 127 HOA .............................................................................. 82, 252, 574
File List ........................................................................................... 190 hold priority .................................................... 169, 197, 204, 207
File not Found ................................................................................ 483 home page ............................................................................ 145, 551
File Version ..................................................................................... 483 host name ....................................................................... 41, 97, 426
Filename ......................................................................................... 483 default .................................................................................. 42, 97
filter factor ..................................................................................... 288 hours run count ......................................................... 224, 252, 255
filter function module ................................................................... 288 hours run logic module ............................................. 104, 224, 380
firewall ...................................................................................... 33, 35 hours run logic module interval ................................................... 254
Firmware ........................................................................................... 9 7 hyperlink
firmware upgrade ........................................................................... 136 web page ........................................................................... 152, 245
Firmware Version hysteresis .............................................................................. 274, 496
NTD ........................................................................................... 438 hysteresis band function module .................................................. 307
firmware versions .......................................................................... 565 Hysteresis Limits function module .............................................. 314
fixed address ..................................................................................... 4 2 I
flash memory ......................................................................... 75, 134 I/O Bus ............................................................ 31, 44, 72, 82, 580
FLER ..................................................................................... 165, 189 I/O bus ............................................................................................. 353
Font Name ..................................................................................... 243 I/O bus connector .................................................................... 62, 76
Fore Colour .................................................................................... 243 I/O Bus error LED ........................................................... 64, 81, 82
FPIA ...................................................................................... 165, 188 I/O channels ............................... 64, 72, 78, 99, 184, 353, 494
FPRM .................................................................................... 165, 189 I/O Module ..................... 61, 76, 99, 111, 269, 353, 494, 579
FRAM ................................................................................... 165, 189 I/O Module Power Supply ....................................................... 85, 86
Free ................................................................................................. 536 IC Comms ................................................................................. 31, 36
Freeze Output ................................................................................. 407 variable ....................................................................................... 324
from connective .................................................................. 120, 217 IC Comms Examples ..................................................................... 338
From Email Address ...................................................................... 198 IC Comms Fail Bit ......................................................................... 347
Frost Protect .................................................................................. 398 Identifier
FRTC ..................................................................................... 165, 189 NTD ........................................................................................... 441
FSWR .................................................................................... 165, 189 identifier ............................................................. 97, 186, 327, 441
FTIM .................................................................................... 165, 189 In Alarm ................................................. 166, 253, 396, 419, 497
F T P ................................................................................................... 4 3 In Alarm Colour ............................................................................. 245
full scale drive time ....................................................................... 273 in phase output .............................................................................. 252
fullstop ............................................................................................ 328 INC class node ......................................................................... 25, 44
function module ................................................................... 285, 517 INC2 .......................................................................................... 26, 27
function module alarm bits ........................................................... 287 index
G (power) ....................................................................................... 317
gain ............................................................................. 398, 399, 418 Inhibit Clear Alarms ...................................................................... 197
gain time constant ......................................................................... 453 input channel LED .................................................................. 64, 81
general alarm group ....................................................................... 188 input channel links .......................................................................... 7 1
general alarms ................................................. 165, 168, 188, 203 cover .................................................................................... 63, 71
generic driver module .................................................................... 249 input channels .......................................................................... 64, 70
generic logic module ...................................................................... 363 Input polarity LED ......................................................................... 8 1
Global To IC Comms ........................................................... 341, 342 Input Type ..................................................................................... 509
GMT ................................................................................................ 528 Inside Temperature ........................................................................ 452
grace time ....................................................................................... 371 instance ...................................................................... 101, 117, 123
grace timer ........................................................................... 253, 260 integral node .................................................................................... 2 6
graph ..................................................................................... 147, 477 integral term .................................................................................. 402
Graphical Display Page Editor ..................................................... 149 integral time ................................................................................... 418
GraphIQs ..................................... 145, 149, 235, 241, 551, 580 integral time constant ......................................................... 398, 402
GraphIQs navigator ....................................................................... 150 inter-controller communications .............................. 21, 157, 323
Group alarm output ....................................................................... 205 inter-controller communications.
Guest ........................................................................... 143, 145, 549 system aspects ............................................................................. 2 1
Guest User ....................................................................................... 549 interconnections
GUID ................................................................... 36, 125, 187, 576 between modules ......................................................................... 9 8
H interconnector
Hand/Off/Auto ................................. 81, 82, 184, 252, 355, 574 I/O Bus ................................................................................. 61, 82
Hardware Channel .................................................... 227, 257, 494 Interfacing ............................................................................ 140, 579
hardware module ......................... 184, 227, 257, 258, 355, 494 Internal Analogue Sensor .............................................................. 495
HCM ................................................................................................ 271 internal count ................................................................................. 375
heat meter ...................................................................................... 312 internal digital input module ........................................................ 225
Heating and Cooling ...................................................................... 416 Internal Digital Sensor .................................................................. 495
Heating and Cooling Loops .......................................................... 456 internal screen bus ........................................................................... 7 0
heating and cooling mode ............................................................. 452 internet domain name ..................................................................... 4 2
Heating Average Medium Temperature ....................................... 452 internetwork .................................................................................... 2 5
Heating Gain Time Constant ....................................................... 454 across router ................................................................................ 3 6
Heating Medium Temperature ..................................................... 452 internetwork alarms ...................................................................... 162
Heating mode ................................................................................. 452 Internetwork Broken .................................................................... 162
Heating OSS Setpoint .................................................................... 452 Internetwork Changed .................................................................. 162
HELP .................................................................................... 165, 188 Internetwork OK ........................................................................... 162
Helper internetwork repeater ..................................................................... 2 7
dialogue box ............................................................................... 330 interval ...................................................................... 254, 380, 473
Hierarchy ........................................................................................ 233 Interval Limit Alarm ................................................................... 382
HIGH ................................................................ 165, 177, 214, 495 intranet ............................................................................................. 3 7
High Alarm Level .......................................................................... 497 intrinsic reporting ......................... 48, 49, 50, 51, 52, 59, 174
High Limit alarm invert input .......................................................................... 252, 257
BACnet ...................................................................................... 177 IO Bus Failure ....................................................................... 165, 189
IP Address ..................................................... 58, 95, 97, 426, 555 Loading ........................................................................................... 483
NTD ........................................................................................... 438 local address ............................................................................ 89, 186
IP Address Alarm Destination ............................................ 173, 579 local device alarms ........................................................................ 162
IP Address alarms ................. 31, 35, 36, 39, 41, 44, 197, 556 local display panels .......................................................................... 2 3
IP Addressing Mode ............................................................... 41, 429 local Lan ......................................................................................... 187
IP Iwrk Broken .............................................................................. 163 local Lan alarms ............................................................................ 162
IP Iwrk Changed ............................................................................ 164 Local Module ................................................................................. 347
IP Iwrk OK ..................................................................................... 164 Local supervisor connector .................................................... 65, 68
IP LAN Broken ............................................................................. 163 Log Enable ................................................................ 474, 475, 479
IP LAN Changed ........................................................................... 163 Log Full ................................................................................. 475, 479
IP LAN OK .................................................................................... 163 Log function module ..................................................................... 295
IPTool ................................................. 23, 95, 97, 183, 428, 555 log off ................................................................................... 146, 549
IQ Controller ................................................................................... 2 1 log on ......................................................................... 143, 145, 549
IQ Lan log point ............................................................................... 110, 478
alarm type ................................................................................. 197 log record ........................................................................................ 475
IQ1xx .................................................. 24, 44, 95, 373, 378, 528 logarithmic actuator ...................................................................... 295
IQ2 IC Comms logarithmic type sensor ................................................................ 295
IQ3 differences ......................................................................... 346 logging ............................................................................................. 469
IQ2 OSS logging record numbers
IQ3 differences ......................................................................... 462 maximum ................................................................................... 110
IQ212/BOX/ATM ......................................................................... 529 logic input ......................................................................................... 7 9
IQ2xx ...................... 24, 26, 44, 95, 373, 378, 382, 528, 529 Logic Module ....................................................................... 363, 517
IQ3 ............................................................................................ 24, 26 logic module types ......................................................................... 363
IQ3 communications ....................................................................... 3 1 logical functions ............................................................................ 365
IQ3 internal Lan .............................................................................. 3 3 login ................................................................................................ 549
IQ3/BACnet .................................................... 174, 198, 326, 425 logout .............................................................................................. 549
IQ3/XNC ............................................................ 32, 139, 573, 574 LONC snvt-switch ......................................................................... 334
IQ3’s used in LonWorks ......................................................................... 26, 38, 45
NTD ........................................................................................... 439 Look Up
IQ3xact ........................................................................................... 578 Button ........................................................................................ 330
IQ3xcite .......................................................................................... 578 lookup function module ...................................................... 311, 509
IQL .......................................................................................... 24, 528 Loop Failure Action ...................................................................... 407
IQLTool2 .......................................................................................... 2 3 Loop module ............................................................. 104, 107, 517
IQView ................................................ 23, 32, 34, 40, 67, 68, 97 loop output ........................................................................... 399, 402
display and directory ...................................................... 154, 241 loop reschedule time ..................................................................... 403
item alarms ........................................................................... 165, 203 Loop Tuner Applet ....................................................................... 404
item code selection Loop Tuning .................................................................................. 404
IC Comms .................................................................................. 330 loss time constant ......................................................................... 453
item reference ................................................................................ 101 Loss Time Constant (Cooling) .................................................... 455
Items ............................................................................................... 234 LOW ................................................................ 165, 177, 214, 495
K Low Alarm Level ........................................................................... 497
knobs ................................................................ 143, 157, 359, 513 Low Flash ............................................................................. 165, 189
k W ................................................................................................... 376 Low Limit alarm
L BACnet ...................................................................................... 177
Label Matching Low Memory ....................................................................... 165, 189
IC Comms ........................................................................ 329, 347 Lower Limit ................................................................................... 512
Lan .................................................................................................... 2 4 Lxxnyyy.IQ3 file ........................................................................... 135
Lan auxiliary board M
44, 75, 89, 96, 139, 186, 428, 445, 555, 571 MAC Address
Lan Broken .................................................................................... 162 BACnet .............................................................................. 58, 199
Lan Changed .................................................................................. 162 NTD ................................................................................. 438, 441
Lan number .......................................... 25, 44, 96, 97, 187, 555 MAC address .............................................. 42, 95, 139, 187, 430
NTD ........................................................................................... 441 main controller ................................................................................ 6 1
Lan OK ........................................................................................... 162 Maintain Same Output .................................................................. 407
language file ........................................................ 96, 126, 576, 579 Maintenance Alarm Sub-module .................................................. 250
language selection .......................................................................... 187 Maintenance Interval Alarm ......................... 165, 254, 258, 381
Last Archive Successful ................................................................. 483 manual ............................................................................................... 2 1
Last Archive was bad ..................................................................... 483 Manual device instance ................................................................. 431
Last Strategy Error ........................................................................ 483 manual IP addressing mode ............................................ 41, 42, 96
LED indicators ................................................................. 63, 81, 92 Manual Level ............................................................ 393, 406, 418
Level ............................................................................................... 545 Manual Override ............................................................................ 406
LFWG ................................................................................... 165, 189 Manual Select ............................................................ 393, 406, 418
limit at function module ............................................................... 293 mass flow .............................................................................. 297, 312
limit to function module ............................................................... 294 maximum frequency ...................................................................... 375
LINC ......................................................................................... 26, 28 maximum function module .......................................................... 302
Linear Sensor Scaling .................................................................... 513 maximum I/O module current ........................................................ 8 5
link/local mode ............................................ 41, 42, 95, 428, 570 Maximum IC Comms .................................................................... 343
List of Event Summaries measured value ............................................................................... 393
BACnet ...................................................................................... 179 Medium Temperature .................................................................... 452
list of values memory .......................................................................................... 478
(graph) ............................................................................. 148, 478 meters ............................................................................................. 374
lithium cell ............................................................................... 61, 75 minimum function module ........................................................... 301
Live Edit ............................................................... 32, 69, 143, 159 Minimum IC Comms ..................................................................... 323
Live Values ........................................................................... 143, 157 Minimum on-Time ........................................................................ 370
LMWG .................................................................................. 165, 189 MINT .................................................................................... 165, 258
LNC2 ................................................................................................ 2 6