Em Iqcon
Em Iqcon
REFERENCE MANUAL
RW/HA
Trend Control Systems LTD P.O. Box 34 Horsham West Sussex RH12 2YF Tel. : (0403) 211888
IQ CONFIGURATION REFERENCE MANUAL
All rights reserved. This manual contains proprietary information which 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.
NOTICE: Trend Control Systems Ltd. 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 Ltd. 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 Ltd 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.
1 INTRODUCTION
1.1 Aim
1.2 System
1.3 Using This Manual
2 PRINCIPLES OF CONFIGURATION
2.1 System Configuration
2.1.1 Display Panel
2.1.1.2 Local Supervision
2.1.1.3 Stand Alone Operation
2.1.2 Supervisor
2.1.2.1 Supervisor Mode
2.1.2.2 Configuration Mode
2.1.2.3 Upload/Download
2.1.3 Networked Display Panel (NDP)
2.1.4 Other Controllers
2.1.5 Controller Alarms
2.2 Hardware Configuration
2.2.1 Input Channels
2.2.1.1 Analogue Inputs
2.2.1.2 Digital Inputs
2.2.2 Output Channels
2.2.2.1 Analogue Outputs
2.2.2.2 Digital Output
2.2.3 Baud Speeds
2.2.4 Network Node Address
2.3 Strategy Configuration
2.3.1 Nodes and Modules
2.3.2 Digital Node Addressing
2.3.3 Interconnecting Modules
2.3.4 Sequence Table
2.3.5 Strategy Configuration Procedure
2.3.6 Module Parameters
2.3.7 Labels
2.3.8 Standard Symbols
2.3.9 Strategy Diagram Rules
2.3.10 Macros
2.4 Initialising an IQ
2.5 Completing Configuration
4 MODULE SELECTION
4.1 Introduction
4.2 Module Selection
5 ADDRESS
5.1 Local Address
5.2 own local LAN
5.3 Alarm Destination
5.4 Text Flag
5.5 Attributes
5.5.1 & (ampersand)
5.5.2 | (Pipe)
5.5.3 * (asterisk)
5.5.4 ? (question mark)
5.5.5 . (full stop)
5.6 Checksum OK/HELP
5.7 Miscellaneous
5.8 Display Panel Language
5.9 Addresses ‘R (CR)’
6 ALARMS
6.1 Alarm Types
6.2 Alarm Communications
6.3 Alarm Generation Mechanism
6.4 General Alarms
6.4.1 CONL
6.4.2 HELP
6.4.3 FPIA
6.4.4 FRTC
6.4.5 FRAM
6.4.6 FSWR
6.4.7 FDRT
6.4.8 FPRM
6.4.9 FTKA
6.4.10FTKP
6.5 General Alarms Acknowledged Status
6.6 Item Alarms
6.6.1 Driver Grace Time Alarm
6.6.2 Digital Input Alarm
6.6.3 Driver Maintenance Interval Alarm
6.7 Item Alarm Details
6.8 Control of Alarm Destination/Text Mode
6.9 Text Alarm Format
6.10 Global Alarm Inhibit
7 ANALOGUE ARRAY
7.1 Fixed Addresses
7.2 Unallocated Addresses
7.3 Status Bytes
7.4 Analogue Status: ‘A <analogue no.> (CR)’
8 CRITICAL ALARMS
8.1 Message Format
8.2 Destination Addresses
8.3 Operation
8.4 Example Supply Fan Failure Critical Alarm
8.5 Critical Alarms ‘M < critical alarm number > (CR)’
11 DIGITAL INPUTS
11.1 Cumulative Hours Run - Number of starts
11.2 Digital Alarms
11.3 Alarm Delay
11.4 External/Internal Digitals
11.5 Labels
11.6 Fast Sequencing
11.7 Digital Input Module: ‘I <digital input module number> (CR)’
12 DRIVER MODULE
12.1 Digital Output Driver (tYpe 1)
12.2 Analogue Output Driver (tYpe 2)
12.3 Time Proportional Driver (tYpe 3)
12.3.1 Example
12.3.2 Response to Changing Inputs
12.4 Raise/Lower Driver (tYpe 4 or tYpe 7)
12.4.1 Raise/Lower Driver module with two digital outputs.
12.4.2 Analogue output channel and Relay Module operation
12.4.3 Boundless Operation
12.4.4 Operation with Proportional Feedback
12.5 Binary Switch Driver (tYpe 5)
12.6 Time Proportional and Override Driver (tYpe 6)
12.7 Driver Alarms
12.8 Readback Checking
12.9 Driver Maintenance Interval Alarm
12.10 Cumulative Run Time
12.11 Number of Starts
12.12 Dummy Output Channels
12.13 Driver - Power On Delays
12.14 Driver Labels
12.15 Driver Module: ‘D <driver module number> (CR)’
13 FUNCTION MODULE
13.1 Type 1: First Order (‘Exponential’) Filter with Gain.
13.2 Type 2: Rescale From 0 to 100
13.3 Type 3 : Rescale To 0 to 100
13.4 Type 4 : Limit At
13.5 Type 5 : Limit To
13.6 Type 6 : Log
13.7 Type 7 : Square Root
13.8 Type 8 : Adder/Scaler
13.9 Type 9 : Multiplier/Scaler
13.10 Type 10 : Divider/Scaler
13.11 Type 11 : Minimum
13.12 Type 12 : Maximum
13.13 Type 13 : Average
13.14 Type 14 : Analogue Gate
13.15 Type 15 : Comparator
13.16 Type 16 : Enthalpy
13.17 Type 17 : Hysteresis
13.18 Type 18: Analogue to Digital
13.19 Function Module Alarm Bit Handling
13.20 Function Module: ‘F <Function module number> (CR)’
15 KNOBS
15.1 Analogue Mode
15.2 Adjustment Mode
15.3 Parameters that can be changed in Knob Adjustment Mode
15.4 Knob: ‘K <Knob number> (CR)’
16 LOGIC MODULE
16.1 Type 1 : Logical combination of Digital Variables
16.1.1 Example 1
16.1.2 Example 2
16.1.3 Example 3
16.1.4 Conditional Statement
16.2 Designing a Function
16.3 Type 2: Logic Timer Module
16.4 Type 3 : Logic Readback Module
16.5 Type 4 : Logic Counter Module
16.6 Type 5 : Logic Delay Module
16.7 Type 6 : Logic Hours Run Module
16.8 Example of Use of Logic Module
16.9 Logic Module: ‘G <loGic module number> (CR)’
16.10 Logic Module Type 1 Logical Combination: ‘Y1 (CR)’
16.11 Logic Module Type 2 Logic Timer: ‘Y2 (CR)’
16.12 Logic Module Type 3 Logic Readback: ‘Y3 (CR)’
16.13 Logic Module Type 4 Logic Counter: ‘Y4 (CR)’
16.14 Logic Module Type 5 Logic Delay: ‘Y5 (CR)’
16.15 Logic Module Type 6 Logic Hours Run ‘Y6 (CR)’
17 LOOP MODULE
17.1 A Control Loop
17.2 Setpoint Selection
17.3 Proportional Control
17.3.1 Cooling Control
17.3.2 Effect of changing Gain
17.3.3 Example
17.4 Proportional and Integral Control
17.5 Loop Rescheduling Time
17.6 Fast Loop Rescheduling
17.7 Proportional + Integral + Derivative (PID)
17.8 Loop Tuning
17.8.1 The Stability Limit Method
17.8.2 The Step Method
17.9 Manual Override
19 PLOT (LOGGING)
19.1 Controller Plot Facilities
19.2 Setting Up the Channels
19.3 Effect of Time Synchronisation on Logging
19.4 Effect of Temporary Power Failure
19.5 PLOT: ‘P<log channel >(CR)’
21 SCHEDULE MODULE
21.1 Occupation Time Profile (OTP)
21.2 Optimum Start Stop (OSS)
21.3 Service Timing
21.4 Manual
21.5 Alarm Bit Handling
21.6 Schedule Module: ‘H <scHedule module number> (CR)’
22 SENSOR MODULE
22.1 Sensor Alarms
22.2 Sensor Alarm Delay
22.3 Sensor Alarm Hysteresis
22.4 Sensor Labels/Units
22.5 Frequency of Sensor Sampling
22.6 Universal Input Channels
22.6.1 Structure of the Universal Input Channel
22.6.2 Universal Input - Sensor Module - Analogue Input mode
22.6.3 Universal Input - Sensor Module - Internal Analogue
22.6.4 Universal Input - Sensor Module - Digital Input Mode
22.6.5 Universal Input - Sensor Module - Internal Digital
22.6.6 Modules which Service Only Internals
22.7 Sensor Module:‘S <Sensor number> (CR)’
23 SEQUENCE TABLE
23.1 Sequence Table Steps
23.2 Servicing of Modules not specified in Sequence Table
23.3 Sequence Table Steps Usage
23.4 Multiple Entries
23.5 Multiplexing Nodes
23.6 Fast Sequencing
23.6.1 Implementation
23.6.2 Rules
23.6.3 Strategy Diagram
23.7 Sequence Number: ‘Q<seQuence step number> (CR)’
24 SWITCHES
24.1 Switch ‘W<sWitch number> (CR)’
25 TIME MODULE
25.1 Time Synchronisation
25.2 Timemaster
25.3 Timekeeper
25.4 Timemaster and Timekeeper
25.5 Operation without a Timekeeper
25.6 British Summer Time
25.7 Time Module: ‘T (CR)’
26 SENSOR TYPES
26.1 Exponent
26.2 Sensor Scaling Mode
26.2.1 Linear and Logarithmic Scaling
26.2.2 Linearisation Scaling
26.2.3 Scaling a Potentiometer input
26.2.4 Linear Sensor Calculation
26.3 Sensor Types: ‘Y <sensor tYpe number> (CR)’
27 USER - PIN
27.1 User PINs
27.2 Security Levels
27.2.1 Configuration
27.2.2 Display Panel
27.2.3 Text Communications
27.2.4 Upload/Download
27.3 User logged on Bits
27.4 Default PIN
27.5 Power Fail
27.6 User ‘U <User number> (CR)’
28 ZONE TIME
28.1 Standard Week and Current Week
28.2 Selection of Current Start and Stop Times
28.3 Setting up Occupation Times
28.4 Text Communications
28.5 Zone byte
28.6 Zone Module: ‘Z <Zone number> (CR)’
29 TEXT COMMUNICATIONS
29.1 Why Text Communications?
29.1.1 Benefits of Text Communications
29.2 Attribute Addressing
29.2.1 Device Attribute
29.2.2 Item Attribute
29.3 Text Matching
29.3.1 Special Characters
29.4 Combination of Attributes
29.5 Team Leaders and Team Members
29.6 Attribute Addressing In Advanced Building Control Systems
29.7 Application of IQ Controller Attributes
29.7.1 Identifier
29.7.1 Identifier (Continued)
29.7.2 Attributes
29.7.2.1 Communication Node Attribute
29.7.3 Attribute 2: Tenant Attribute
29.7.4 Attribute 3: First Plant Attribute
29.7.5 Attribute 4: Second Plant Attribute
29.7.6 Attribute 5: Time Zone Attribute
29.7.7 Attribute 6: Vertical Zone Attribute
29.7.8 Attribute 7
29.8 Attribute Addressing - Summary
A1 APPENDIX
A1.1 Modules and Parameters
A1.2 Specific Software Configuration Differences
A1.2.1 Real Time Clocks
A1.2.2 Digital Inputs - Fast Sequencing
A1.2.3 IQ7x Zone Inhibit
A1.2.4 IQ7x Single Zone
A1.2.5 Linearise Settings
A1.3 Input Channels
A1.3.1 Input Channel Types
A1.3.2 Analogue Only to Digital Conversion
A1.3.3 Accuracy on Input Channels
A1.4 Output Channels
A1.4.1 Output Channel Types
A1.4.2 IQ7x Output Channel Types
A1.4.3 IQ9x, IQ9x+, IQ10x Output Channel Types
A1.4.4 IQ10x+ Output Channel Types
A1.4.5 Output Ratings
A1.4.6 Output Accessory Signal Requirement
A1 APPENDIX (continued)
A1.5 Connections/Settings/Options
A1.5.1 Connections and Settings
A1.5.2 Baud Rate for Direct Connected Local Supervisor
A1.5.3 Options for Display Panels
A1.6 IQ Controller 24 Vdc Supply
A1.7 Issue Variants - Major Features
GLOSSARY OF TERMS
INDEX
1 INTRODUCTION
1.1 Aim
This manual describes the method of configuring an IQ controller i.e. the way the controller
can be set up to perform a control function or functions.
It is a general document, not specific to a particular IQ and certain values, limits and parameters
are left undefined. These items, which vary with controller type, are defined in the
documentation for that particular controller and are summarised in Appendix 1.
This manual supports all IQ types fitted with Firmware version 4,5, 6 or 7. It describes the
operation of firmware version 7 although it may be used as a guide for the earlier versions.
Major changes are shown in Appendix 1.
1.2 System
An IQ controller is designed so that one product can be configured to satisfy a wide range of
control and monitoring situations from very small, simple systems to large complex systems.
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 freely transferred between controllers, providing a fully integrated system and retaining the
considerable advantages of distributed control.
With the addition of an Autodial Modem (ADM) a building can become one of many
controlled entirely from a central office anywhere in the world where international dialling is
available.
A Trend Supervisor can be used to monitor and adjust the IQ controllers via the network. This
has 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
access to a single controller.
The design and features of the Trend system are presented in the Trend System Reference
Manual, and the user should be familiar with this before starting to design a system.
The reference section, section 4 to 28, is arranged in alphabetical order, but the novice should
read this manual in the following order:
Sections 1-4
Section 17 Loops
22 Sensors
12 Drivers
remainder of manual.
Before designing a strategy for a system using text communications (e.g. a unitary controller
system) the you should read section 29 which gives an introduction to these aspects.
2 PRINCIPLES OF CONFIGURATION
In order that the IQ performs its assigned functions it must first be configured. There are three
types of configuration to be considered. They are:
• System Configuration
• Hardware Configuration
• Strategy Configuration
In addition this section includes the procedure for initialising the controller prior to strategy
configuration and the procedure for completing configuration.
This manual describes the types of communications which are possible with an IQ controller.
The following devices may communicate with an IQ controller:-
Networked Inter
CNC Lan 1 INC INC Lan 4
Supervisor Network
CNC CNC
Local
Supervisor Device
Local Network
Display
IQ
Panel
Outstation
The IQ Display Panel may only be used with some IQ controllers (see Appendix); It may be
permanently mounted in the lid of the unit, panel mounted up to 3 metres away, or the hand-
held version can be plugged in from time to time as required. The Display Panel facilities are
designed to operate in two basic ways, local supervisor or stand alone.
On systems which have a supervisor the Display Panel may be used to monitor the system and
to enable adjustments to be made or occupation times to be extended to meet the day to day
needs of occupants. Alarms would be sent to the central supervisor.
The Display Panel and its IQ may be a self-contained system without the need for a separate
supervisor, (although some parameters must be set up initially using a supervisor as described
in the Display Panel Manual). For this reason the IQ has:
• An alarm messages buffer so that the Display Panel operator may monitor alarms.
• A calendar to set up special working times for the year ahead.
• Passwords to restrict Display Panel changes to authorised persons.
2.1.2 Supervisor
A supervisor is a personal computer programmed to allow a user access to data held within the
IQ controllers on a system. A supervisor may be connected directly to the local "supervisor"
connector on an IQ controller or via a Communications Node Controller (CNC) and the Trend
network. A direct connected supervisor may only speak to the local controller. The Supervisor
may communicate in three basic modes:
This mode is designed to enable an operator to monitor the control strategy and the plant and
to be able to change setpoints and operating times. Its full facilites depend on the supervisor
used, and the method of presentation varies greatly, ranging from a list parameters to a full
colour plant mimic. All changes are password protected. The facilities are described fully in
the particular Supervisors User Manual.
This mode is designed for an engineer to be able to change parameters or set up and
fundamentally modify the control strategy in the controller. It is password protected on
supervisors and all changes made in configuration mode require a valid controller password
to be entered, (once controller user passwords are set up). Configuration mode facilities are
described in this manual sections 3 onwards.
2.1.2.3 Upload/Download
This form of communication enables the user to take a copy (i.e. Upload) of the strategy-
defining data file from the controller memory into the memory of the supervisor and from there
to store it to floppy disk. This gives a permanent copy of the controller data file that can be safely
stored away.
Normally the data in the controller memory is protected by a battery, so that if the power fails
it will remain intact, and when the mains supply is restored the IQ will recommence control.
It is possible for the battery to fail, or physical damage to be done to the controller and in this
case, the data kept on floppy disk can be downloaded from the supervisor to the controller.
The Updown Utility is contained in an optional software utility known as the 822+/Toolbox which
can run on 921 and 94x hardware (see 822+/Toolbox manual for minimum hardware requirement).
The Inter-Controller communications module allows one controller to send data to or obtain
data from other controllers on the Trend network. Inter-Controller communications should not
be used over an auto-dial link.
Controller alarms are generated by a controller and can be sent either over the direct connection
or over the network to either a supervisor or networked printer. Alarms are covered in more
detail in section 6.
The hardware configuration details vary greatly with the IQ type so the user should read the
data sheet of the particular controller type for exact details. Generally, however, the
configuration can be split into four areas, although some IQ types will not need all of these.
The four areas are:
• Input Channels
• Output Channels
• Baud Speed
• CNC Address
The term Universal Input is used to define an input channel that may be configured to be either
analogue or digital.
IQ Configuration Manual Issue 6/A 1/6/93 Page 2 - 3
PRINCIPLES OF CONFIGURATION IQ CONFIGURATION MANUAL
Analogue inputs are used to make measurements of temperature, pressure, position or level etc.
The measurements are made by fitting the appropriate transducer (sensor) which produces a
continuous electrical signal that is proportional to the measurement being made. Generally a
link defines whether that channel input is either a current (I) or a voltage (V) input. On some
controllers there is also a (T) link selection for thermistors.
Digital Inputs are used to monitor the status of the plant and/or switches. This status will either
be open or closed, (OFF or ON). The standard configuration is for voltage free contacts to be
connected to the input terminals. The supply voltage (24V) used to energise the digital inputs,
is normally supplied by the IQ.
The output channels are configured either by external modules, board changing, or linking.
Generally outputs are either analogue or digital. Some IQ’s only have analogue output
channels although digital outputs may be accommodated as described below.
These are used to position valves and dampers etc. where a continuous voltage (V) or current
(I) is required. They are also used to drive multiple relay modules where the relay(s) selected
depend on output level.
These are used to switch plant ON or OFF. On an IQ with analogue only output channels they
are accommodated by adding an external relay module. Some IQ's have digital output relays
as an integral part of the output channel, others supply an on/off voltage.
The IQ controllers generally have two serial communications interfaces; these are intended for
use by:-
• Local Supervisor
• Network
The baud speed for each interface should be set to match the baud speed of the device with
which it communicates. Note that later IQ Controllers do not have a baud rate setting for the
local supervisor interface; the speed is fixed at 9600 (see Appendix for details).
The network node address defines the particular controller on the network and must be set to
a unique number on the LAN. It must be set correctly or the network communications will not
operate fully (see the Network Engineering Manual for details).
The network node address will be set either by a switch, and/or within the address module in
configuration mode (see Appendix for details). The switch will be located either within the IQ
or on the associated network node controller. (Note: where a switch and the address module
must both be set up, they should both be set to the same network node address number).
Strategies are configured by setting up these modules and inter-linking their inputs and outputs.
The linking of modules may be drawn as a strategy diagram in a way which is quickly and easily
understood. Thus the unit can be configured to perform complex tasks without the use of a
computer programming language.
As with a traditionally hardwired system, it is necessary to identify each wire or "node" of the
system. Each node of the system is given an arbitrary number, each number being unique to
its point in the control strategy.
56 57
B1 B2 B3
In Figure 2.2 a signal is passed from box B1 to box B2 using node 56 and similarly another
signal is passed from box B2 to box B3 using node 57.
In Figure 2.3 it can be seen that the inputs to more than one box can be sourced from a single
node: the output of box B1 is connected to the inputs of boxes B2, B3, and B4 via node 52.
51 52
B1 B2
B3
B4
Although one node can serve as the input to a number of boxes, the output from any single box
must have its own unique node. This rule can in fact be broken using the multiplexing nodes
method (see section 23.5).
The conventional term for these boxes is modules and from now on each box will be referred
to as a module.
In common with system hardware inputs and outputs to the plant, software interconnections
are comprised of analogue and digital nodes. Analogue nodes are used to store values whereas
digital nodes are used to store ON/OFF status (i.e. 1 or 0 respectively).
In order to differentiate between analogue nodes and digital nodes on control strategy
diagrams, digital nodes are identified by a small numbered square, whereas analogue nodes are
identified by a small numbered circle.
51
21,1 21,3
52 B1 B2
21,2
54
53 B3 B4
21,4
In Figure 2.4 the analogue nodes are recognised as circles 51 to 54. Digital nodes are designated
by two numbers and are recognised as squares 21,1 to 21,4.
The digital node address number system refers to the byte and bit number of the node. It is not
essential that the user is familiar with bytes and bits, these references should be looked upon
as an arbitrary number system to locate a particular digital node by giving it an address where
if a byte is compared to a street, the bit would be a house number.
7 6 5 4 3 2 1 0
Byte 20 7 6 5 4 3 2 1 0 20th Street House No.
Bits
Byte 21 21st Street
Byte numbers available for user designed strategies are from 32 to 36 inclusive; other byte
numbers are allocated to specific functions within the IQ (see section 10). Bytes can be set to
any value in the range 0-505 and bits in the range 0-7. Address 0,0 (i.e. byte 0, bit 0) does not
really exist and is used as a null address.
Each byte comprises eight bits of information numbered 0-7, each bit is 0 if in the OFF state
and 1 if in the ON state.
BIT 7 6 5 4 3 2 1 0
In the above example byte 21 bit 0, byte 21 bit 4, and byte 21 bit 6 are in the ON state and byte 21
bits 1, 2, 3, 5 and 7 are in the OFF state.
In Figure 2.7 it can be seen that the source address for module B1 is 13 and the destination
address is 65. Destination address 65 then becomes the source address for modules B2, B3 and
B4.
The analogue array acts as a storage area for the analogue values. A module picks up a value
from the array (i.e. its source) processes the value and stores it back in the array in another node
where it is available for another module to use it. (The digital array works in a similar way as
a storage area for digital values i.e. 1 or 0).
All one module knows is its sources and destinations; it knows nothing about the next module
it is linked to. In the above example, examining the details about module B1 in configuration
mode will reveal nothing about module B2 which is using the output of B1.
13 65 69
B1 B2
B3
B4
Thus as modules are set up, a separate diagram must be drawn (a strategy diagram) which
shows the linking between modules. If this information is not recorded it can be extremely
tedious to find as it will require a search through all the modules to find any which use the node
in question as a source or destination. (A utility is available which enables this information to
be obtained automatically. It is called the 821 Documentor and will run on 921 supervisor
hardware).
The microprocessor in the IQ performs a large number of tasks and in order to ensure that the
processor has enough spare time to cope with background demands, the processing of the
control and monitoring strategy is sequenced over a fixed cycle time.
Each module is assigned a position in the sequence table that defines the order in which the
modules will be processed. The order in which the modules are processed can be extremely
important for the control strategy to function correctly. The whole list of modules in the
sequence table is serviced every cycle. To reduce the response time to digital inputs, it is
possible to construct the sequence table so that a digital input can override the normal sequence
and perform a fast sequence.
The sequence table is a useful clue to the modules being used as it lists most of the modules
which use the nodes.
The process of strategy configuration can be seen as taking a brand new IQ which contains a
large number of modules (as listed in section 4) all of which are unused. The configuration is
then a process of plugging these modules together to build a particular strategy, rather in the
way a box of lego bricks can be plugged together to produce a building model.
Within the strategy, each module has to have its sources and destinations defined as either input
or output channels, (i.e. inputs and outputs to plant), or analogue or digital nodes. By using
a common node between connected modules, the modules are arranged to process strategy
information. Connected modules must be placed in the sequence table in the required order
of operation. Normally the order of sequence is determined by the order in which data flows.
Thus in the above example Figure 2.7 the modules would be in the sequence table as follows:-
slot 10 module B1
slot 11 module B2
As the configured controller steps through the sequence table it comes to slot 10; it picks up
the configuration data relating to module B1 and finds that node 13 is its source. It then fetches
the value from node 13 and processes it within the module; the program then finds that the
destination address for B1 is node 65 and it sends its output to that node. On the next sequence
step (11), that value is picked up and used by module B2 which delivers its output to node 69.
A complete strategy would be dealt with in just this way with the values passing from node to
node via the modules.
In addition to defining input and output addresses the internal parameters of each module must
be defined, e.g. sensor alarm levels, loop gains etc.
2.3.7 Labels
Certain modules may be labelled within configuration mode. The address module contains
labels to identify the controller (identifier and attributes 2-7). The labelling of the other
modules (S, I, K, W, D, Z) enables user friendly displays on the Display Panel and supervisors
so that the item can be identified by its geographic or function descriptive label.
Label Units
Sensors * *
Digital Inputs *
Knobs * *
Switches *
Drivers *
Zones *
On some IQ's with Universal Inputs, Sensors and Digital Inputs share the same label; the other
labels are as normal.
For text communications the correct selection and configuring of labels may be critical and
should be planned as part of the overall system plan (see section 29).
(0403)
phone 211888
MS MS
I
AN
TERM 'L
O ZONE SS
G
E
G L
E
S F
F
G
A H
G
ICC
H
S R
ICC
AN AN DIG ICC
TERM 'L NODES
All the modules listed in section 4 are represented on the strategy diagrams by standard
symbols. Each shape represents a different type of module and from the shape, the function
of the module can be interpreted. The shape can be produced with the aid of the Trend Stencil
which also provides Heating and Ventilation symbols.
There are also standard Trend Templates for Computer Aided Design use with In*A*Vision.
These are in the form of an In*A*Vision Drawing file called TRENDMOD.TPL which
includes many more symbols.
Q = +/- = Heat Exchanger
Valve general symbol Q
b + = Heat Battery
- = Cooling Battery
Electrical actuator
b= Electrical
Centrifugal Fan
Manual actuator
Dampers
S Sensor general symbol
Flow Indicators
Pump
Compressor
Ventiliator
IC Comms Remote
Storage Cylinder
Analogue Node
Schedule
Digital Node
Axial Fan Hardware Digital Input/Output
Digital Input
The standard symbols for various modules are shown in detail in section 4, but the following
general rules are used on strategy diagrams, to enable them to be understood more easily.
2) Any information which has to flow right to left or bottom to top should be marked with
an arrow.
3) All sensors, outputs and any other plant connections should be labelled with the
customers normal identification name.
4) All modules should have sequence table numbers, (except digital inputs, critical alarms,
IC comms). Where fast sequencing is used for digital inputs they must be put in the
sequence table.
e.g.
5) As far as possible each complete and self contained strategy function should be on one
drawing.
6) Show all inputs on left hand side and all outputs on the right hand side.
8) Constants on function module inputs can be shown by a value beside the input.
e.g. 10
2.3.10 Macros
The process of configuration can be made more efficient, (i.e. speeded up and simplified), by
using macros. A macro is a pre-defined strategy or sub-strategy, which is formed by a number
of pre-configured and inter-connected modules, which can be automatically downloaded to an
controller. During download the macro automatically assigns the next available modules of
the requisite type and automatically sets up their sequence table steps. The downloading of
macros is done with the aid of the 840 Macro Utility program which will run on IBM
compatible machines. The use and design of macros is explained in the 840 Macro Utility User
Manual.
Note: When using Macros in conjunction with manual configuration ensure that the conventions
described in the Macro Manual are complied with or strategies may be overwritten.
2.4 Initialising an IQ
This section gives the procedure for setting up a new un-initialised IQ.
(1) Connect the interface cable from the supervisor being used to the local supervisor
connector on the controller or connect the supervisor to the controller via the network.
(2) Set the correct baud speeds on whatever interface is being used i.e. to match the
supervisor on the local supervisor interface or to match the network or CNC on the
network interface.
(5) Check the network node address switch is set up correctly on the CNC or IQ controller
(see specific IQ documentation).
(7) Set up whichever supervisor is being used for downloading as explained in the 822
Updown Utility User Manual.
(9) Enter the local address of the controller which must be the same as the switch settings
if set up as above (use the address module see section 5.1).
(10) Enter the alarm address and the remote local area network. This is the network node
address of the device to which alarms will be sent (see address module in section 5.1).
If this address is set to zero, no alarms are sent, if set to 2 they will be sent to the local
supervisor socket, and any other valid network address setting will cause them to be sent
to the network.
(4) Set up any digital values, (e.g. switches, digital constant states and enable any alarms
required).
(6) Initially the controller passwords are not set up but if you want your controller to have
password protection then set up the passwords (Users) in configuration mode.
(7) If you are running the controller from a Display Panel without the use of a central
supervisor then you may wish to set up the holiday calendar dates and special days’ times.
(8) Again for the Display Panel, Networked Display Panel, 94x Series Supervisor, or Text
Communications the following parameters may be needed:
Labels
Units
Knobs Range and Password Levels
Switches Password Levels
(9) Be particularly careful about item labels, and address module identifier and attributes
with regard to their use in text communications (see section 29).
The symbol =? means that the IQ is awaiting an input. A selection is made by typing the capital
letter indicated in the prompt followed by a second character which is normally the module
number.
e.g. prompt = ?
enter S<CR> <CR> = Return or Enter
prompt =?
prompts - range 1 to v - here v is dependent on a particular IQ controller.
enter 1 <CR>
prompts - sensor 1 display
Alternatively, the IQ has multiple entry facility so that it will accept a string of several
characters finishing with (<CR>).
enter Q <CR>
It is important that the controller is not left in configuration mode. While in configuration mode
the only device that can communicate with the controller is the one which initiated entry into
configuration mode. All other devices including controllers requiring inter-controller
communications will be ignored.
WARNING
NO OTHER SUPERVISOR CAN COMMUNICATE WITH THE CONTROLLER, NO
ALARMS CAN BE SENT BY THE CONTROLLER, NO INTER-CONTROLLER
COMMUNICATIONS CAN OCCUR UNTIL CONFIGURATION IS EXITED OR IT
TIMES OUT.
Because of this, alarms are sent to the configuring supervisor in coded form after the top level
prompts. After the supervisor has caused the controller to exit from configuration mode, the
alarms are sent in the normal way.
If the controller is left in configuration mode for more than 15 minutes without any
communication from the supervisor, it will automatically exit and return to normal operation.
The IQ performs a Quit (see section 3.4.2) from the module that was displayed, so that data
is not updated erroneously.
If the controller is several layers of selection down in configuration mode, each level must be
Quit or eXited (only eXit works at the top level) until the message Exit from Utility is
received. The operator then knows he has exited correctly.
When the data has been entered and is correct, the new module data can be stored in the IQ
RAM by typing X <CR>, or the edit aborted by typing Q <CR>.
X will cause the changed module data to be saved on exit. The new data will be used when
the module is next sequenced. A valid password may be required in which case the prompt
"Enter PIN" is displayed. If an invalid PIN is entered the message "Edit inhibited" is
displayed, and the changed data discarded. When a correct PIN is entered the changed data
is saved on exit.
A new controller is supplied with six user passwords set to zero at zero level. In this condition
with null passwords, the controller allows changes to be made without entering a password.
As soon as a password is set up (see section 27.2.1 Users) the X command will not save
changed data unless a valid password of level 90 or greater is entered.
Once the password is entered, it holds the controller open for changes until configuration mode
is exited or the controller times out after 15 minutes.
Q causes a Quit action, i.e. any change made is ignored. It is important to use Q unless a
confirmed change has been made.
enter C2 30<CR>
The configuration mode then copies the sensor 1 parameters into sensor 2 through to sensor
30 inclusive and returns to the top level prompts. (Notice the space between 2 and 30.)
Hence the statement Ca b<CR> means copy module currently selected into a list of modules
starting at a and finishing at b.
WARNING
USING THE COPY FACILITY WRITES DIRECTLY INTO THE RUNNING MODULE
WITHOUT HAVING TO ENTER X OR A CHANCE OF USING Q FOR QUIT.
Because the copy function makes a change directly, if the controller has PIN's (passwords) set
up then it will require a password to be entered before a change is made.
e.g. C<CR>
Single item selection alpha characters or numbers do not need to be separated, but entry of a
label or text must be terminated with a <CR> or a space (or the text must be of maximum
length). A byte, bit address is separated by a comma or a space, whilst zone time information
will accept either a comma, space, or a colon to separate the hours and minutes.
e.g. S1H25X From the top level prompts; this will set S1 high alarm to 25 and saves data.
Note that no displays of sensor 1 are shown. Top level prompts are displayed after action is
completed.
e.g. L1A33,4X From top level prompts; this will set up loop 1 manual address bit to be byte
33, bit 4 and returns to the initial prompts.
3.7 Next/Previous
If a module is selected, then the next module of the same type may be selected with the > key.
This wraps around so that if the last sensor is selected then the > key will select sensor 1.
The < key can be used in a similar way to select the previous module.
e.g.
Pv 1 v20.8 s 0010
The node address is the address of the node which can be changed by the user in this module.
The value is the actual value of the data stored in the node and is monitor only.
The status is a bit pattern showing the alarm status associated with the analogue node value.
It is also monitor only; its meaning is described in 3.9.
The node address points to the location in the digital array where the data is stored. Thestatus
is the data value either 0 (OFF) or 1 (ON).
Status 0 0 0 0
If this pattern is 0 0 1 0, then a Process Variable Fail is present but the others are not. In the
case of the loop module only the two right-hand alarm conditions can report alarm messages
to the supervisor.
This is given in more detail when selecting from a list of types, so that the various types are
enumerated:
0=analogue input
1=internal analogue
2=digital input
3=internal digital
This user-friendly feature saves the operator from having to refer to lists of types and ranges.
They may be entered into the table more than once, see section 23.4 but only the first five entries
can be seen on the configuration mode display for that module.
If one of the modules has not been put into the sequence table, then in configuration mode a
list of the next four free steps are shown indicating where the module may be entered (free
steps).
3.12 Upload/Download
Once in configuration mode the special characters operate as follows:
The upload/download functions enable the strategy defining data files to be moved from
controller to supervisor and vice versa respectively see section 2.1.2.
Upload/Download over the network requires the entry of a User PIN with a level of at least
95 for download and 85 for upload. If the password is not of a high enough level the words
"inadequate PIN" will be displayed.
Upload/Download is usually achieved using the 822 Utility program. Before the data can be
downloaded to the controller the existing data file is completely cleared out (optionally the
attributes may be retained). The utility will prompt "Do you wish to overwrite existing IQ
attributes (Y/N, F1=Help)". If it is desired to preserve the attributes in the destination
controller then type N for no. Once a successful download is completed "Load OK" will be
received. If the download is unsuccessful then "Load ER" will be received. In this event the
data file will have been cleaned out!
4 MODULE SELECTION
4.1 Introduction
The following sections contain a list of each of the configuration mode selection prompts:
In each table the maximum and minimum allowable values of module parameters are shown.
Lower case v indicates that the value is dependent upon controller type. Such limits are listed
in Appendix 1 for all controller types.
Subsequent sections provide detailed information about the facilities provided by each
module, together with:
Range
Select Prompt Comments
Low High
GENERAL
5 ADDRESS
The address module page is used primarily to enter the addressing data used in communications.
• Present the IQ controller's communications node attribute (lan number and node
address) in replies to attribute communications requests.
• Correctly direct returning global global messages. Note: If the own local Lan number
is not set up (i.e. = 0) then global global messages originated by this controller, will be
received by it and actioned. If the own local Lan has been set up correctly then global
global messages originated by this controller, will be received by it but not actioned.
Global global messages will only work on a lan with an INC+.
The Remote lan address enables alarms to be sent to a remote Lan over a Trend Inter-network
(see the Trend System Manual). If set to zero, the alarm target address is on the local Lan;
otherwise it is a remote Lan.
If the alarm target device is autodialled then the alarm address and the Lan number have to be
set in the ANC+ number table. If the ANC+ is on the local Lan then the Remote lan address
must be zero, if the ANC+ is on the inter-network then the Remote lan address must be the true
Lan number. Details of use of the ANC+ are given in the Auto-Dialling Reference Manual.
The alarm destination may be controlled by the strategy in which case a module output
destination will be set up to be 255 so that addresses can be transferred to the node. The Alarm
destination Lan number and address are positioned as shown below:
N e tw o rk R e m o te L A N C N C N ode
The flag applies to general and item alarms (not critical alarms which are always sent as text)
and it enables these alarms to be received by devices which cannot interpret the coded alarm
form. The coded form is described in section 6.7 and can be received by Trend supervisors.
The text form is the same as that used in the alarm buffer display (see section 6.9), and can be
received by the 94x series supervisors, 921 supervisor or a printer.
The text flag is also set in digital byte 495 bit 0. (If bit=0, alarm is coded; if bit=1, alarm is text).
5.5 Attributes
The identifier is a 15 character label which describes this controller and is sent as part of every
critical alarm message to identify its source, therefore it should be unique to each controller on
a system. It is also shown on the Display Panel Status Page.
The identifier is also used as controller attribute 1 for text communications. This is described
more fully in section 29.
There are six other device attributes which can be selected by letters F to K. These attributes
are up to 10 characters long. These 7 attributes are used in two basic situations:
• Message reception:
They allow the controller to be identified either uniquely or as part of a group so that it
may receive the relevant messages.
• 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.
In situation 2 for one controller to talk to others, all must have the same attribute set up in their
respective address modules but within the attribute several characters are reserved for special
functions
& | * ? .
They are not appropriate in situation 1 above but are very useful in situation 2. They are
explained in section 29, but below is a summary.
This symbol performs a string AND function. It can be used to specify controllers which have
more than one required attribute e.g.
This symbol performs a string OR function. It can be used to specify controllers which have
either one or another required attribute e.g.
5.5.3 * (asterisk)
This symbol performs a wild card function. It can represent any character or group of characters
(or no character at all) e.g.
This symbol performs a wild card function. It can represent any single character (there must
be a character).
The full stop symbol in an attribute enables truncation of an attribute. This enables an attribute
to be used in both situations defined above. In the first situation the attribute works as normal
but in the second situation the attribute is truncated to the full stop and the full stop is replaced
by an asterisk e.g.
When the originating controller sends a message, the attribute is truncated to FL3*, but the
supervisor can obtain the average from this controller by requesting FL3.LEADER.
\ / ( { ;
The HELP status also causes a HELP alarm (see section 6.4).
The remedial action to overcome the HELP status is to download a valid configuration data file.
The checksum status may be set manually by using a lower case 'e' which will toggle between
checksum OK and HELP. It can be used to force a HELP status to stop the controller controlling
the plant and to freeze the outputs e.g. while changing the strategy. It must not be used to
override a HELP status as this could result in the controller driving the plant with a corrupted
data file.
5.7 Miscellaneous
The version/issue of firmware is shown.
On some IQ's there is a selection for Supply frequency which sets the frequency of the
Analogue to Digital Converter to reject mains pickup. Other IQ's have a selection forreference
Volts. This refers to the reference voltage supply used for voltage and current (i.e. Linear)
sensor scaling. This supply level needs to be known accurately by the firmware which assumes
a default value. The default is either 2.5 V or 5 V dependent on IQ type as shown in appendix
1. When the IQ is factory tested the actual reference voltage is measured and the value set up.
It may be recalibrated if an input inaccuracy is suspected, or after changing the battery or
firmware. The setting is unaffected by a strategy download. The value can be set in the range
2.5 V to 2.599 V or 4.8 V to 5.2 V for 2.55 V and 5 V defaults respectively. The recalibration
is performed by removing the cable on an input channel and selecting 'T' (thermistor) linking
on that channel. The voltage between the input signal terminal and 0 V should then be measured
with a voltmeter. The reference volts in the address module should be set to this value, and then
the channel restored to its previous configuration and re-connected. If the reference Volts entry
is set outside the permitted range the firmware assumes the default value and gives a display
of ref volts out of range.
addr switch xxx - displayed on controllers where the network node address is set on switches,
the value displayed at addr switch reflects the switch setting.
The Controller Display Panel Status page contains most of the above data, but does not show:
Note: Labels entered through configuration, such as sensor labels are not displayed in the
language selected. Such labels are displayed as entered by the user and are limited to ASCII
characters 0 to 127. (This does not permit accented characters).
*** the permitted range depends on the default setting which varies with controller type as
explained in Appendix 1. A 5 V default has range 4.8 to 5.2 V and 2.5 V default has range
2.5 to 2.599 V.
6 ALARMS
An alarm condition is generated within an IQ when a particular plant or self checking parameter
is other than a pre-defined range or state. This condition may then be used by the strategy and
may be monitored on a Display Panel, it may also be transmitted as an alarm message to display
devices such as a supervisor or printer to alert a system operator.
• General Alarms: generated by the controller when it detects a general alarm condition
within its own hardware or program.
• Item Alarms: generated by a particular controller module and normally due to a faulty
plant condition.
• Critical Alarms: special alarm conditions set up in the strategy which generate special
text messages.
• Network Alarms: generated by the CNC part of some controllers, are explained in the
Network Engineering Manual.
Only General Alarms and Item Alarms are stored in the alarm history buffer, they can either
be sent as text or in coded form as defined by the alarm text flag, byte 495 bit 0 (if bit=0, alarm
is coded, and if bit=1, alarm is text).
Item alarms may be individually disabled (i.e. on a per item basis). Both item and general
alarms may be globally inhibited within an IQ. 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 effect
the alarm condition is to alter the alarm limit.
The target alarm address and the mode of alarm transmission (text or coded) can be altered by
the strategy as explained in section 6.8.
In addition to the target supervisor alarm Address, critical alarms are also sent to a special
destination address (see section 5.2).
When the supervisor receives the alarm it will send a reply (an‘ACK’nowledge message) back.
When this is received by the controller it cancels the requirement to send the alarm again. If
the alarm is not acknowledged then the alarm will be resent 30 seconds after it was first sent,
and will continue to be resent at 30 second intervals until acknowledged.
The FTKA (Failed TimeKeeper Advice) alarm behaves differently in that it is sent to all
controllers on the local LAN. It is only sent once as it is automatically acknowledged when
sent from the buffer.
If the alarm condition is acknowledged then, when the alarm condition disappears, a clear
alarm is sent. The clear alarm obeys the same rules as an alarm condition i.e. it is resent until
acknowledged.
The acknowledge message referred to is sent automatically by the supervisor and has nothing
to do with the [Control] K operator acknowledge on some supervisors.
The alarm buffer on the controller means that alarms can be stored in the controller, the number
of alarms stored depends on the controller type (see Appendix 1). If these alarms are not
acknowledged then they will continue to be sent even if the alarm condition has disappeared.
An alarm in the alarm history buffer cannot be overwritten until the alarm is acknowledged.
The operation of this buffer is explained later (see section 20).
Thus the sensor module has a byte in the digital array for alarm conditions, another for alarm
enabling and a third for alarm acknowledge. In configuration mode for the sensor module,
these bits can be seen as follows:
Bit 3210
alarM status 0101
alarm eNabled 0001
alarm acKnowledge 0001
Note that for the purposes of this example we will ignore both the alarm delay which is dealt
with later, (see sections 22.2 and 11.3), and global alarm inhibits, see section 6.10.
The actual position of these bits in the digital node array is described in section 10, and the
meaning of the sensor alarms is shown in section 6.7.
In the above example a sensor high alarm condition is detected by the sensor module which sets
Bit 0 of the alarm status (a sensor outside limits alarm is also present).
Reporting of the sensor high alarm is enabled by Bit 0 of the alarm enable status. Reporting of
the other three alarms is disabled because the alarm enable status of Bits 1,2,3 is zero; thus the
sensor outside limits alarm condition will not be reported.
Note that, although the sensor outside limits alarm will not be reported, the condition is still
present, and if the bit is used in the strategy (e.g. as an input to a logic module), the strategy
will respond accordingly.
The alarm acknowledge status is `the last acknowledged alarm status’ and in this example
means that the high alarm has been reported to the buffer (Bit 0=1) and all other alarms have
been cleared and the clear alarm has been reported (Bits 1, 2, 3 = 0).
alarm 0100
enable 0001
acknowledge 0001
The alarm status now differs from the acknowledge status which means an alarm must be
reported to the buffer. In this case it is a Clear Alarm as bit 1 = 0. This will be done as it is enabled
(enable Bit 0=1). When the alarm is reported the acknowledged status is set to 0 (Bit 0=0), so
the three bit patterns become:-
alarm 0100
enable 0001
acknowledge 0000
Now the alarm status and acknowledge status are the same for the enabled alarm (Bit 0), and
hence the clear alarm will not be sent again.
If the outside limits alarm were to be enabled (enable Bit 2=1), then the bit pattern becomes:-
alarm 0100
enable 0101
acknowledge 0000
The enabled alarm now differs from the acknowledged status with Bit 2. Since the alarm bit is
1 (Bit 2=1) then an alarm must be reported (not a clear alarm). If this is successfully done then
the acknowledge bit will be set to 1 (Bit 2=1). This results in:-
alarm 0100
enable 0101
acknowledge 0100
Again the alarm status and the acknowledge status are now equal.
Generally reported means alarms are put into the buffer, but for critical alarms they are sent
directly and reported means that they have been sent to their destination and the automatic
alarm acknowledge message has been sent back to confirm their receipt.
Thus enabled alarms (or clear alarms) are only sent when the alarm status and acknowledge
status differs.
CONL alarm is generated at power up or if the system has restarted if the data file is correct.
HELP alarm is generated under conditions of data file corruption on power up or if the system
has restarted, and thereafter whenever an operator communicates in normal supervisor mode
(not configuration mode).
FPIA, FRAM, FSWR, FDRT, FPRM alarms cause a CONL to be generated by restarting
the configured controller strategy. If the alarm condition is present after the CONL then the
alarm will be sent.
FRTC is sent whenever the alarm condition is found, and until cleared, it is sent once an hour
thereafter.
FTKA alarm is sent to all controllers on the local LAN when the controller unsuccessfully
requests time/data synchronisation after power up, or after midnight.
The principle behind the controller general alarms is that the detected fault is transitory. It is
up to the user to decide if the frequency of occurrence indicates a hardware intermittency, or
a difficult environment, perhaps due to poor installation methods, or even a poor electrical
supply.
Thus the FPIA, FRAM, FSWR, FDRT, FPRM alarms may often be due to the corruption of
a working register by electrical noise, which will be cleared automatically by the controller
resetting itself. Thus they may be ignored unless their frequency interferes with control.
The FRTC alarm however cannot clear itself and the operator should check and, if necessary,
resynchronize the real time clock either in the supervisor or configuration mode (Time
Module).
The FTKA and FTKP messages are not self correcting and if they occur the problem should
be investigated.
6.4.1 CONL
Controller on line. The alarm will be raised each time the IQ controller is switched on
successfully or if the controller has restarted itself due to one of the other alarm actions.
By itself, it is just an indication of the controller being re-powered and should not be 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. From January 1985
all Trend IQ's have offered over 50 ms of hold up time from a nominal supply and 20 ms from
a 15% low supply.
However, before rushing to the telephone, ascertain whether this alarm is due to work being
carried out elsewhere on the site.
If a CONL occurs once a day, this 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 Services representative.
6.4.2 HELP
When the controller is powered down, (switched OFF), the very last action to take place is that
of calculating a checksum of the volatile memory (RAM) contents. This value is then stored
alongside all the other data.
When the controller is powered up, (switched ON), the checksum is again calculated and
compared with the stored value. If the two do not agree a HELP alarm will be raised, otherwise
a CONL is raised as above. This means the strategy is corrupted and the controller will cease
controlling (i.e. outputs will freeze, see section 5.6).
6.4.3 FPIA
Fail Peripheral Interface Adapter. A PIA is a device that allows 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 generate a CONL alarm.
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 Services 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 Services representative
immediately.
6.4.4 FRTC
Fail Real Time Clock - the Real Time Clock (RTC) is a battery backed device that maintains
the real time of day and date in terms of day, month and year. The timing source is a crystal
oscillator very similar to that used in modern digital watches and is not dependent upon mains
frequency.
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.
6.4.5 FRAM
Fail Random Access Memory - as part of its housekeeping, the IQ controller continuously
checks that it can read from and write to RAM, the read/write memory. If it cannot, for any
reason, a 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.
6.4.6 FSWR
Fail SoftWaRe - 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 equally apply here.
6.4.7 FDRT
This alarm indicates a failure of the DART (Dual Asynchronous Receiver Transmitter) i.e. a
communications hardware failure. It will cause a restart and an accompanying CONL alarm.
6.4.8 FPRM
This alarm is generated if the EPROM checksum is wrong at power up. This indicates that
the processor board should be replaced.
6.4.9 FTKA
Fail TimeKeeper Advice - This is only generated by IQ90 Controllers. It is generated within
a given time after power up if the controller is not synchronised, or has not received an FTKA
from another controller on the local LAN. It is also generated with similar conditions if a time
synchronisation message is not received between 00:00 and 00:10 hours.
It is sent to all other controllers on the local LAN to prohibit them sending another FTKP alarm
(see below) to the supervisor. It is sent once via the buffer, and automatically acknowledged.
6.4.10 FTKP
Fail TimeKeePer - This is generated directly after an FTKA as defined above (again only by
IQ90's). It is sent to the target supervisor in the normal way. The FTKP alarm is not self
correcting, and when it occurs the cause of the alarm should be investigated.
bit 7 6 5 4 3 2 1 0
FPRM FDRT FSWR FRAM FRTC FPIA HELP CONL
The general alarms acknowledged status is stored in byte 313 of the digital node array. These
bits work slightly differently from the normal acknowledge mechanism as explained in section
6.2.
When an alarm is to be sent, the bit status will be at zero. After an alarm has been successfully
sent, the receipt of the acknowledge message from the supervisor will set that bit to 1. Thus
under normal conditions the byte status should be all ones.
Although this byte may be configured as a digital destination address, it cannot be updated by
any module (i.e. a read only byte).
This alarm is detected by a Readback Logic Module and the destination of this module is set
to the address of the alarm bit for the driver module concerned (see section 12.8).
This alarm condition does not cause an alarm bit to be set, instead the condition has to
be deduced by comparing the required state bit with the actual state bit (see section 11.2).
This alarm is detected by an hours run logic module and the destination of this module is set
to the address of the alarm bit of the driver module concerned.
Code
Module Alarm Label Alarm Clear Comments
Driver Readback Alarm SDGT CDGT The readback input state differs from
(Driver Grace driver output after grace time has
Time) elapsed.
Maintenance MINT CMNT The plant item has been running for
Interval longer than the maintenance interval.
Digital Digital Input DI=n CDIn Input actual state differs from required
Alarm Where n = 0 or 1 state. If Required state = 0, then alarm
will be DI=1, clear alarm CDI1.
Digital node 495,0 will control the text flag. If a module writes a 1 into this bit then the text
feature will be turned on. If it writes a 0 then the text feature will be turned off. If a module
writes into analogue node 255 then the bottom bit of the associated alarm bits will write onto
495,0 and the text flag. In this way a schedule or gate module maybe used to switch between
address A with text on (e.g. gatehouse printer) and to address B with text off, (e.g. 921
supervisor).
1 0 0, 0
S =1 255
V =1 F
60 D a l ar m ad d r es s
61 F1
V =4 E te xt fl ag
GA TE
S =0 495.0
13,0
Z o ne 1 OTP
Figure 6.1 Use of Gate Module to Change Alarm Address and Text Flag
In this example, during occupation the alarms are diverted to a 921 at address 4 with text off,
and during non-occupation they are diverted to a 940 at address 1 with text on.
Note that the user may still change the alarm destination and the text flag using the
configuration mode address module. However if a module has been set up which overwrites
these nodes then the values set up in configuration will be overwritten when that module is
serviced.
1 15 16 17 36 37 38 57 58 59 64 65 72 73
74 81 82 83 86 87
O24_S10_ SHIH <CR>
Note:
1) Currently only 921, 94x series and remote printers can receive text alarms.
3) The alarm description is the description used on the Alarm History Buffer Display
for that alarm (see section 20). The alarm description is displayed in the language
configured for the Display Panel (see Section 5.7).
Byte 0 1 2 3 4 5 6 7 Type
498 CONL HELP FPIA FRTC FRAM FSWR FDRT FPRM General
499 FTKA FTKP General
500 HIGH LOW OUTL READ Sensor
501 DI= Digital Input
502 SDEV FAIL Loop
503 SDGT MINT Driver
Setting the appropriate bit to 1 will inhibit all alarms of that type, setting it to 0 will permit them.
e.g. Setting bit 500,0 to 1 will inhibit all sensor high alarms, setting the bit to 0 will permit
them.
7 ANALOGUE ARRAY
As explained in Section 2.3 , the analogue array acts as a storage area for analogue values. Each
value can be accessed by an address in the range 1 to 255.
The following is a list of analogue addresses within the IQ controller. It shows fixed and
recommended addresses for constants and module outputs. Where recommendations have
been made these should be adhered to:
All other modules including schedules use Free nodes. ACE+ searches in the following order:
Free nodes 93 to 97
53 to 60
Allocated nodes 92 to 75
220 to 180
74 to 61
179 to 101
Address 0 is a valid address. It can be used as a destination address for modules the output
of which are discarded i.e. dumped into address 0. On some modules using address 0 as a
source will cause that input to be ignored, for example Function module - Maximum.
In the example 17.11.4 (see Loops as shown in Figure 7.2) a failure on sensor S2 will be put
into the read alarm digital node corresponding to analogue node 2 (byte 42). Function module
F1 will then ignore this input and only use sensors 3,4,5 to calculate the average. If all four
sensors fail, then an alarm will be put in the digital node byte for analogue 101 (byte 141). Loop
L1 can then detect a failure on this node and take Pv fail action. It also passes it on to the status
byte for node 61, thence through module F2 to node 102 status byte. This is used by Loop 2,
so it too can take its Pv fail action.
Thus by passing the status from node to node, a loop at the end of a strategy can take action
for a sensor failure many modules back.
Analogue node 255 is coupled with digital node byte 495 bit 0 so that if a value is passed from
another analogue node to node 255 then the corresponding status bit 0 passes to byte 495 bit
0.
Each of the 8 alarm bits may be set to either the alarm state 1 or the non-alarm state 0. The 8
bits, reading from left to right, indicate:
Spare
Spare
Digital (node carries digital value 0 or 1)
Loop Fail type 2
Sensor read alarm
Sensor out-of-limits alarm
Sensor low alarm
Sensor high alarm (or Digital Input Alarm (if digital bit=1))
0 0 0 0 0 1 0 1
Each time a status is changed, values must be entered for all 8 alarm bits.
8 CRITICAL ALARMS
Critical Alarms are used to generate a user defined alarm message. The alarm condition is usually
produced by a logic module whose output destination address is within the alarm byte for the
specific critical alarm. Alarm conditions anywhere in the controller may generate the critical alarm
by configuring a module to detect the alarm(s) and output to the critical alarm byte.
The purpose of critical alarms is to provide an alarm message for the operator to report
occurrence of selected controller functions or plant failure, for example, fan or pump failure,
over temperature or over pressure, pump running or boilers running.
The transmission of critical alarms takes priority over normal alarms. A critical alarm is a
configurable text message that can be received and printed by a remote printer unit, in addition
to the system supervisor.
Current value of critical alarm byte Two hexadecimal characters which define the value
of the critical alarm byte.
Date dd/mm
Time hhmm
Critical alarm message The configured critical alarm text can be a maximum
of 47 characters. Any characters can be used.
8.2 Destination Addresses
Each critical alarm uses two destinations:
1) The normal alarm supervisor address is set up in the address module (Alarm address).
2) The special alarm destination address as set up in the critical alarm module
(destination).
The critical alarm is sent to both the special alarm destination address and to the normal alarm
supervisor address (e.g. to both a printer and the normal alarm supervisor). If these addresses
are the same the alarm is not repeated for each destination.
The 15 character controller identifier is set up within the address module as the source
identification of all critical alarms.
The special alarm destination address is defined by a node address and a LAN number. If the
address is set to 0, the alarm is disabled. If the LAN number is set to zero, the address is local.
For example, a remote controller may send a critical alarm to the local supervisor or printer,
and the alarm handling supervisor.
The alarm may be sent via an ANC+. The LAN number setting then depends on the ANC+
position, if on a local LAN the LAN number should be set to 0, if on an inter-network the LAN
number should be set to the destination LAN number. In both cases the alarm address and
destination LAN number must be set in the ANC+ number table.
8.3 Operation
Each critical alarm has a status byte (critical alarms status bytes start at byte 37) and if any bits
of the alarm status byte are set, a current critical alarm will be sent. When one bit has triggered
the critical alarm, another bit being set will not trigger it again i.e. it will only trigger the alarm
if all bits are initially zero. Similarly when all the bits of the alarm status byte are cleared a
‘cleared’ critical alarm message will be sent.
The value of this byte is sent in the alarm as two hexadecimal characters.
Critical alarms have two acknowledge bits, one for the alarm supervisor address and one for
the special alarm destination address.
These alarm acknowledge bits are all stored in byte 314 of the digital node array i.e. 4 critical alarm
channels x 2 bits = 8 bits = 1 byte. They work in a similar way to normal alarm acknowledge bits
as described in section 6.5, so a critical alarm to the target supervisor will continue to be sent at 30
second intervals until the target supervisor acknowledge bit is changed.
Critical alarms are processed cyclically, so that if an alarm handling device is not functioning,
other critical alarms may still be transmitted. One alarm (or IC communications) is sent at each
pass. On each pass the various categories of alarms are monitored in the folowing sequence
and the first alarm found is sent:
Critical alarms
Item and general alarms
IC comms
Each time critical alarms are checked, the check alternates between alarm for the normal
supervisor address and for the special alarm destination address. This ensures that the failure
to communicate to one alarm destination address does not block other communications.
Each bit of the critical alarm status bytes can be accessed through the digital array addressing
structure. For example, a logic module can provide complex alarm handling including logical
combination and timing functions.
There is a power on delay which is applied to IC Comms and Critical alarms. This prevents
all controllers communicating simultaneously on a system power up (see section 14.14).
NOTE:- A critical alarm condition exists if any bit of the alarm byte is set. A critical alarm
condition is cleared if all alarm byte bits are cleared.
The normal alarm supervisor address is defined by the alarm address and the remote lan
address as set up in the address module. The special alarm destination address is set up in this
module, using Destination and remote laN.
These are 20 holiday periods which can be set to a use type Null, Next or Every.
For a particular holiday every zone used must be set up with a day type. This can be set to:
The Display Panel holiday display page allows special days to be set up when selected for a
zone. A change to the special day (e.g. Special Day 1) will affect every holiday date and zone
allocation for which that Special Day is specified (i.e. there are five special days in total for
one controller).
The special days can also be set up in configuration mode zones display for Zone 0.
The controller holiday calendar is separate from the supervisor calendar and there is no
communication between the two. If a central supervisor is performing calendar functions, then
the Display Panel holiday calendar dates should be deleted and not used.
The times for a holiday day are transferred into the current week at midnight when the holiday
day becomes the sixth day ahead. Thus, holiday days must be set up a least 6 days in advance.
If this is not done they will not be put in the time zone's current week and hence will be ignored.
If special working times are to be set up less than 6 days in advance, they must be set up in the
time zone(s) current week.
The actual number of nodes used in some sections of the array varies from IQ to IQ. The array
details given below are for maximum array capablity.
Most of the array is allocated to specific uses such as digital inputs, switches, alarm status bytes
etc. Bytes 21-36 are unallocated and are conventionally used as logic module outputs.
The digital array allows access to all alarm states, acknowledge bits and enable bits. These can
be used to implement sophisticated alarm handling strategies.
The following table cross references the areas of the array which contain the alarm bytes,
acknowledge, and enable bytes for particular modules.
BYTE NUMBERS
1 363
Digital Inputs Loop Alarm Acknowledge Status
6 378
7 379
Digital Outputs Driver Alarms Acknowledge Status
12 394
18 401
Switches Digital Input Required State
20 406
41 487
Analogue Alarms Digital Inputs Alarms Enabled
280 492
281 493
Loop Alarms Timing Pulses/Day of Week
296 494
297 495
Driver Alarms Flags, bits and users logged on
312 497
Bit
0 1 2 3 4 5 6 7
byte
1 I1 I2 I3 I4 I5 I6 I7 I8
2 I9 I10 I11 I12 I13 14 I15 I16
DIGITAL INPUTS
3 I17 I18 I19 I20 I21 I22 I23 I24
4 I25 I26 I27 I28 I29 I30 I31 I32
5 I33 I34 I35 I36 I37 I38 I39 I40
6 I41 I42 I43 I44 I45 I46 I47 I48
7 1 2 3 4 5 6 7 8
8 9 10 11 12 13 14 15 16
DIGITAL OUTPUTS
9 17 18 19 20 21 22 23 24
10 25 26 27 28 29 30 31 32
11 33 34 35 36 37 38 39 40
12 41 42 43 44 45 46 47 48
13 OTP OCC OSS OCC NOC W OCC CD CM ZONE 1
14 OTP OCC OSS OCC NOC W OCC CD CM ZONE 2
15 OTP OCC OSS OCC NOC W OCC CD CM ZONE 3
16 OTP OCC OSS OCC NOC W OCC CD CM ZONE 4
17 OTP OCC OSS OCC NOC W OCC CD CM ZONE 5
BIT
OTP OCC: Occupation Time Profile, Occp'd :OTP start - OTP stop
0 ZONES
1 OSS OCC: Optimum Start Stop Occupied :OSS start - OSS stop
convention
19 W9 W10 W11 W12 W13 W14 W15 W16 20,4 = 0
20 W17 W18 W19 W20 0 1 20,5 = 1
21 G1 G2 G3 G4 G5 G6 G7 G8
22 G9 G10 G11 G12 G13 G14 G15 G16
23 G17 G18 G19 G20 G21 G22 G23 G24 allocated
24 G25 G26 G27 G28 G29 G30 G31 G32 by
LOGIC OUTPUTS
41 1 71 31 101 61 131 91 161 121 191 151 221 181 251 211
modules 1 to 120 use
42 2 72 32 102 62 132 92 162 122 192 152 222 182 252 212 analogue nodes 101 to 220.
43 3 73 33 103 63 133 93 163 123 193 153 223 183 253 213 Function module types 15,
44 4 74 34 104 64 134 94 164 124 194 154 224 184 254 214 17 have digital outputs and
45 5 75 35 105 65 135 95 165 125 195 155 225 185 255 215
by convention they use bit
46 6 76 36 106 66 136 96 166 126 196 156 226 186 256 216
47 7 77 37 107 67 137 97 167 127 197 157 227 187 257 217
'0' of the associated alarm
48 8 78 38 108 68 138 98 168 128 198 158 228 188 258 218 byte for their output.
49 9 79 39 109 69 139 99 169 129 199 159 229 189 259 219
50 10 80 40 110 70 140 100 170 130 200 160 230 190 260 220
e.g. Function module 10 is
51 11 81 41 111 71 141 101 171 131 201 161 231 191 261 221
52 12 82 42 112 72 142 102 172 132 202 162 232 192 262 222
type 15. What is its output
53 13 83 43 113 73 143 103 173 133 203 163 233 193 263 223 by convention?
54 14 84 44 114 74 144 104 174 134 204 164 234 194 264 224
55 15 85 45 115 75 145 105 175 135 205 165 235 195 265 225 Analogue node = 110
56 16 86 46 116 76 146 106 176 136 206 166 236 196 266 226
Alarm byte = 150
57 17 87 47 117 77 147 107 177 137 207 167 237 197 267 227
58 18 88 48 118 78 148 108 178 138 208 168 238 198 268 228 Output =150,0
59 19 89 49 119 79 149 109 179 139 209 169 239 199 269 229
60 20 90 50 120 80 150 110 180 140 210 170 240 200 270 230 Note:
61 21 91 51 121 81 151 111 181 141 211 171 241 201 271 231
The Trend Automated
62 22 92 52 122 82 152 112 182 142 212 172 242 202 272 232
63 23 93 53 123 83 153 113 183 143 213 173 243 203 273 233
Controller Engineering
64 24 94 54 124 84 154 114 184 144 214 174 244 204 274 234 package (ACE+) uses
65 25 95 55 125 85 155 115 185 145 215 175 245 205 275 235 digital bits starting at 32,0
66 26 96 56 126 86 156 116 186 146 216 176 246 206 276 236 for function module digital
67 27 97 57 127 87 157 117 187 147 217 177 247 207 277 237 outputs.
68 28 98 58 128 88 158 118 188 148 218 178 248 208 278 238
69 29 99 59 129 89 159 119 189 149 219 179 249 209 279 239
70 30 100 60 130 90 160 120 190 150 220 180 250 210 280 240
Bit/Byte 0 1 2 3 4 5 6 7
281 L1 L2 Bit Alarm Loop
282 L3 L4 SP
0
283 L5 L6 DEV
284 L7 L8 PV ODD
1
285 L9 L10 FAIL NOS
LOOP ALARMS
289 L17 L18 SP
4
290 L19 L20 DEV
301 D9 D10 2
302 D11 D12 3
DRIVER ALARMS
Bit
0 1 2 3 4 5 6 7
Byte
313 CONL HELP FPIA FRTC FRAM FSWR FDRT FPRM
CONL :Controller On Line: Controller has been powered up successfully.
HELP :Checksum failure; strategy corrupted - control ceased.
GENERAL ALARMS
FPIA :Fail Peripheral Interface Adaptor, setup changed, system restart.
FRTC :Fail Real Time Clock: Time/date outside normal range.
FRAM :Fail Random Access Memory: Read/Write failure, system restart.
FSWR :Fail Software; accessing memory outside range, system restart.
FDRT :Fail Dual Asynchronous Receiver Transmitter,coms fail, system restart.
FPRM :Fail Programmable Read Only Memory;processor board fault, system restart
CA1 CA2 CA3 CA4
CRITICAL
314
ALARM
ADA ASA ADA ASA ADA ASA ADA ASA
ACK
ADA :Alarm Device Acknowledge: received by special device
ASA :Alarm Supervisor Acknowledge: received by target Supervisor.
Byte Sensor Byte Sensor Byte Sensor Byte Sensor
315 S1 327 S13 339 S25 351 S37 Bit Alarm
Bit
0 1 2 3 4 5 6 7
Byte
379 D1 D2 Bit Alarm Driver
380 D3 D4 0 RDBK ODD
381 D5 D6 1 MINT NOS
ACK STATUS
396 I9 I10 I11 112 I13 I14 I15 I16
DIG INPUT
397 I17 I18 I19 I20 I21 I22 I23 I24
398 I25 I26 I27 I28 I29 I30 I31 I32
399 I33 I34 I35 I36 I37 I38 I39 I40
400 I41 I42 I43 I44 I45 I46 I47 I48
401 I1 I2 I3 I4 I5 I6 I7 I8
REQ STATUS
4
412 S6/G92 424 S18/G104 436 S30/G116 448 S42/G128 5
413 S7/G93 425 S19/G105 437 S31/G117 449 S43/G129 6
Logic
414 S8/G94 426 S20/G106 438 S32/G118 450 S44/G130 7
Output
457 L5 L6 G137 2
458 L7 L8 G138 3
459 L9 L10 G139 4 SP DEV EVEN
460 L11 L12 G140 5 PV FAILNOS
474 D7 D8 G154 2
475 D9 D10 G155 3
476 D11 D12 G156 4 RDBK EVEN
477 D13 D14 G157 5 MINT NOS
487 I1 I2 I3 I4 I5 I6 I7 I8
DIG I/P'S ENABLED
Bit
0 1 2 3 4 5 6 7
Byte
DAY OF WEEK BITS
TEXT FLAG
Text Flag:
1 = TEXT ON (Alarm sent as text)
0 = TEXT OFF(Alarm sent coded)
Also Alarm Bit for Analogue Node 255
IQ70
Power
496 Zone
Reset
Inhibit
POWER RESET
POWER RESET: This bit is set to 1 on power up or soft restart.
IQ70 INHIBIT
Can be used to initiate a start-up strategy which should then
reset the Bit.
IQ70 ZONE INHIBIT: This Bit stops IQ70 zone/OSS updating byte
13. This can be updated from elsewhere e.g. team leader by
ICCOMS
BIT 1 = 1 zone inhibited
BIT 1 = 0 zone enabled
497 U1 U2 U3 U4 U5 U6 DEF
LOGGED
These bits monitor state. Setting bits will not affect state.
498 CONL HELP FPIA FRTC FRAM FSWR FDRT FPRM GENERAL
499 FTKA FTKP GENERAL
GLOBAL ALARMS INHIBITS
FTKA: Fail Timekeeper Advice, sent when not updated by timekeeper to all other
controllers on Lan.
FTKP: Fail Timekeeper alarm, sent when not updated by timekeeper to supervisors.
GLOBAL ALARM INHIBITS STOP ALL ALARMS OF A PARTICULAR TYPE IF SET TO
1, SET TO 0 ENABLES ALARMS.
Set to 1 if IC COMS
IC COMS
504 IC1 IC2 IC3 IC4 IC5 IC6 IC7 IC8 retry sent. Cleared
when acknowleged.
FAIL
Table 10.10 Digital Status: 'B < byte, bit for this digital > (CR)'
Range
Select Prompt Comments
Low High
11 DIGITAL INPUTS
Digital inputs are simple on or off type inputs and may be derived from such devices as pressure
switches, feedback contacts on a motor starter, duty/standby changeover relays or from local
override switches for ventilation systems etc. Digital inputs will also accept pulse train type
signals such as those derived from meters (electricity, gas, water flow etc.), which in
conjunction with a counter module, can be used to supply such information as consumption,
flow rate etc. This will allow, for example, an electricity meter input to show total energy
consumption rate in Kilo-watts (KW) or total energy usage (KWh).
The connection of the digital input module to the universal input channel and its relationship
to the sensor module of the same number is described in section 22.5.
Digital inputs are checked every 15.6 milliseconds to facilitate monitoring pulse inputs of up
to 32 Hz (minimum pulse width 15.6 milliseconds). In order to be monitored, the input must
be on for 15.6 mS and off for 15.6mS (both minimum). A count is kept of the number of
transitions from 0 to 1 for each channel. The state of each digital input held in the digital array
is updated every four sequence steps.
The cumulative hours run count and the number of starts can be displayed on the supervisor
and monitored and changed in configuration mode. These counts cannot be directly used in the
strategy, but a counter logic module can access the number of starts count. An hours run logic
module can be used to provide hours run for use in the strategy. The user should be aware that
when a directly connected hours run logic module is reset, the hours run value in the digital
input module is also reset.
The input has a required state, so that if the input actual state differs from the required state
an alarm condition exists. An alarm will then be sent to the alarm buffer if it is enabled and
if it is present for longer than the delay explained below.
When an alarm is registered it will be put into the alarm buffer as explained in section 20. Thus
normally the alarm delay may be monitored by the strategy by the fact that the actual state differs
from the required state and the acknowledged state has not followed the alarm state. As soon as the
alarm delay has expired, the alarm will be put in the buffer and the alarm acknowledge state will
equal the alarm state. If the alarm buffer is full, or if a low level of configuration mode is being used
then the alarm will not go into the buffer and this rule will not operate.
If an associated sensor (as explained section 22) is set up as digital or internal digital then the
alarm state can be monitored directly by the strategy from Bit 0 of the Sensor Module (this will
also be set up after the delay has expired). Bit 5 of the Sensor Module will be set to 1 to indicate
a digital value.
Although Hours run and No 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 by using an hours run logic module.
11.5 Labels
A twenty character label is allocated to each Digital Input module.
Where outstations have Universal Inputs the state of a real digital input cannot be monitored
directly on the Display Panel. It can only be monitored indirectly by allocating it a sensor
module in digital mode, (see section 22.4.4). The sensor module can have its units and labels
set up in configuration mode (see section 22.3). These labels may only be set in the digital input
module but there is in fact only one label or unit per input channel which is shared by both the
sensor and digital input modules.
The label can be used as an item attribute for text communications. This is explained for IC
Comms in section 14.9 and more generally in section 29.
? * .
\ / ( { ;
Fast sequencing can reduce this time delay by jumping directly to that part of the sequence table
when the digital input occurs. This gives a delay of typically 200ms.
It can only be used on a maximum of 8 digital input channels in a specified location, the number
and location varies with the controller type. The full details of fast sequencing are given in
section 23.6.
12 DRIVER MODULE
Driver modules are used to drive plant via controller output channels. Drivers can be sourced
from control loops to provide a closed loop system or can have fixed input levels to provide load-
cycling or timed switch-ON or switch-OFF. Driver modules can be used with or without plant
feedback. If plant feedback is used, alarms can be raised if the plant does not respond within a
defined time period (Grace-time). Sequence control of plant can be achieved by coupling a
number of drivers together.
Each driver type has two output channels each of which may be assigned to any of the hardware
outputs of the IQ.
Note that on the IQ, the digital outputs are refreshed every 30mS giving a resolution of +/- 15
mS for Raise/Lower and Time Proportional Drivers.
The digital output driver has a single digital source address and provides a single digital output
(with an optional anti-phase output).
In all controllers except the IQ70, digital outputs are achieved by using either relays within the
controller or an analogue output channel and an external Single Relay Module (SRM). An
analogue output channel which is used to drive an SRM must be linked for current output. The
IQ70 provides a switched voltage output.
The analogue output driver is normally used to drive such devices as valve or damper position
actuators, chart recorders etc.
The analogue output driver has a single source variable in the range 0 to 100 percent 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 volts, offset
and range constants can be applied to the input by the user.
The standard output voltage range is 0 to 10 volts, where 0 volts represents an input of 0 percent
input and 10 volts represents an input of 100 percent. If an offset of 0 and a range of 100 is
specified then an input of 20 percent, results in an output of 2 volts.
For example an output voltage range of 2 to 8 volts is required to drive a particular item of plant.
The total output voltage of 0 to 10 volts gives a range of 10 volts which represents an input of
10 percent per volt output.
Therefore, for a 2 to 8 volt output, a range of 60 percent and an offset of 20 percent are required.
When the input to the module is 100 percent, the output voltage will be 8 volts and when the input
to the module is 0.01 percent, the output voltage will be 2 volts. 0 percent will still give 0 volts.
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%).
Period time may be shown in seconds i.e. 30s, or in minutes i.e. 30m.
Figure 12.5 Time Proportional Driver Figure 12.6 Mark Space ratio
This driver is similar to others in having an in-phase output channel (L) or an anti-phase output
(A) which is always the inverse of the (L) output. The time proportional driver input defines
the ratio ON time/PERIOD time in percent. The module uses a digital output which may either
use an internal relay or an external SRM.
12.3.1 Example
With the module input at 100 percent, the output will be in the ON state for 150 seconds and
the OFF state for 0 seconds.
With the module input at 50 percent, the output will be in the ON state for 75 seconds and the
OFF state for 75 seconds.
With the module input at 10 percent, the output will be in the ON state for 15 seconds and in
the OFF state for 135 seconds.
When the driver input is greater than 0 percent and at the start of the time period, the driver
assumes the ON state. The driver output state is updated every 30 milliseconds (so its turn off
time is accurate to 30 milliseconds), but it only monitors the input once per 15 seconds.
As a general rule every 15 seconds 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 minute period is at 10 %, then the output should remain
ON for 5 minutes.
Figure 12.7
If at 4 mins (multiple of 15 seconds) the input has changed to 20 % then the output will be set
to stay ON until the 10 minute time. However if the input had changed to 5 % then the output
will turn OFF immediately (as the ON period of 2½ minutes has been exceeded).
O UTP UT % 100
(30% ) (40% )
0
0 15 20 50
E XA M P LE P E RIO D (m ins )
In this example the output would stay ON for 20 minutes, but when the input changes to 0 %
after 15 minutes, the output turns OFF at the next 15 second point.
The exceptions to this action occur if the input has changed to 100 % when it is examined at
the next 15 second point. In this case if the output is ON it will stay ON, (as would be expected
from the general action described above), but if the output is OFF it will again turn ON if it
has been OFF for greater than the minimum off time of 10 % of the period. In the following
examples the period is set to 50 minutes.
In this case the input changes from 40 % to 100 % after 25 minutes. This means it turned OFF
at 20 minutes, so it will not turn ON again until it has exceeded the minimum OFF time of 5
minutes (10 % of 50 minutes). This point occurs at 25 minutes.
5%
0 45 50
E XA M P LE P E R IO D (m ins )
In this case the input changes from 95 % to 100 % after 47½ minutes. The output has turned
OFF at 47½ minutes so it cannot complete the minimum off time of 5 minutes until the start
of the next period, so the output cannot turn ON again until the start of the next period.
Full scale drive time may be shown in seconds or minutes, feedback is optional.
S D1 L 1 R AISE
100s FULL SCALE DRIVE TIME
FE E D B A C K
F R/ L A 2 LOWER
(OPTIONAL)
Figure 12.11 Strategy symbol - Raise/Lower Driver using two integral relays
From firmware version 4.6 the Raise/Lower driver module has been modified to operate the Heat
Cool relay Module (HCM); in this configuration a single valve and a fan may be driven. In firmware
version 5.5 and 6.4 the type 7 raise/lower driver is introduced. The types 4 and 7 raise/lower drivers
use different methods of resetting at the end limits as described in section 12.4.3.
In an IQ which has relays included on the circuit board, the raise/lower function is implemented
with two digital output channels. The raise/lower driver has one analogue source address and
provides two digital outputs. The first of the digital outputs is known as the in-phase or raise
output and the second digital output is known as the anti-phase or lower output.
R Rais e
D1 L RLM
S 100s L
Lower
R/L A
Figure 12.12 Analogue output channel and a Raise Lower relay module
Heat Rais e
D1 L
S 100s Cool
Lower
R/L A
HCM
F an Fan
Figure 12.13 Analogue output channel and a Heat Cool relay module
When using the raise/lower driver with an analogue output channel the Raise Lower relay Module
(RLM) or Heat Cool relay Module (HCM) should be used to interface to plant. (The recent versions
of these relays modules are known as 2RM and 3RM respectively). The output of the raise/lower
driver as measured at the terminals of the assigned output channel (set to voltage) will be:-
7 volts - for any time period during which the requested output position is equal to the
last output position.
0 volts - 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:-
If the feedback address is set to zero then the driver will operate using a calculated value
position. The calculation uses the full scale drive time and the sum of amounts of time that
the valve has been driven in each direction.
For example (see fig 12.14) we are using a valve with a full drive time of 120 seconds and 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 seconds, moving the valve to 60 % open. If the input to the driver
module decreases by 20 % to 40 %, the lower output of the driver module will be turned ON
for 20 % of the full drive time i.e. 24 seconds, moving the valve to 40 % 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 type 4 driver, and one by a type 7 driver.
In a type 4 driver 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 %.
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 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 RLM and 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 %. Previous to firmware version 4.6 a negative input would
have resulted in the lower relay being continuously energised.
If the valve has a position feedback potentiometer, this can be used to provide a feedback signal
to the driver module to determine the valve’s actual position at any point in time. Each time
the driver is serviced the position error is calculated. If the error is greater than 0.25% then
the appropriate output will be maintained for the time calculated to be necessary to reduce the
error to zero.
drive time = error % x full scale drive time
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.
From the above implementation it can be seen that the strategy operates like a cascade control
system with the primary loop L1 giving a position setpoint to the secondary loop D1 which
compares this with its process variable, the potentiometer S2, 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 one quarter of a full drive time (up to a maximum of 30s).
Figure 12.16 Strategy symbol - Binary switch driver Figure 12.17 Hysteresis
This driver has an in-phase output channel (L) and an anti-phase output (A). The binary switch
driver input value above which the driver goes from the OFF state to the ON state and vice versa
is known as the switching level. The ON and OFF switching levels can each be set between
0 and 255 although only 0 to 99 is operational.
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.
1 If the ON and OFF levels are set to the same value, noise on the input source signal may
cause the drive to switch ON and OFF at random.
2 If the ON and OFF levels are reversed so that the OFF level is greater than the ON level,
the module output will become a an oscillator with a period of twice the sequence scan
cycle time, when the input is between the ON and OFF levels.
The binary switch driver may be used as an internal driver to provide hysteresis on the digital
input nodes of other modules. However, remember to set the channel output to one that is not
being used (a dummy channel see Section 12.12) and preferably do not mix real drivers and
internal drivers; define all the real drivers first and then the internal ones.
When the override input is applied it will hold the channel output at 10v, otherwise it time
proportions the output between 4v (ON) and 7v (OFF) similar to a time proportional driver.
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 (RLM) halves the number of
outputs and simplifies wiring.
When the override input is ON the output drives to 10v 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 4v (ON) and 7v (OFF) levels, so if the override is ON the in-phase channel is at
10v, i.e. the time proportional output is >7v i.e. OFF so the anti-phase channel is ON i.e. 4v.
In the above, example, the output from loop L1 is driving binary switch driver D1, whose
output is used to drive a pump ON or OFF through digital output 1. Digital input 1 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
logic readback module compares the two signals at E and G of the logic readback module, when
they are same i.e. both ON or both OFF, no action is taken. If, however, after the grace time
(20s) has elapsed, the pump is ON and the flow switch is OFF or vice versa, there is a fault in
the system. The logic readback module generates an output which sets byte 297 bit 0, to status
1, which is the readback alarm bit for driver D1 as defined in the digital data array.
This data can be accessed over the communications network, not by the strategy. It can be
displayed in supervisor mode, or monitored and changed in configuration mode. Alternatively
the run time can be calculated by using an Hours Run Logic module as shown above. The user
should be aware that when the Hours Run Logic module is reset, the hours run value in the
Driver module is also reset.
This data can be accessed over the communications network. It can be displayed in supervisor
mode and monitored and changed in configuration mode. The number of starts can be accessed
by the strategy indirectly by using a Counter Logic Module.
? * .
\ / ( { ;
Range Comments
Select Prompt Low High
* With a driver type 4 or type 7 (Raise/Lower), if a single output channel is used to drive
the device via a Raise/Lower relay Module, or a Heat Cool relay Module then this address
should be 0 (zero).
V may be used to reference the Driver input level Sv using text communications. Sv is the
analogue or digital value at the source address.
Low High
13 FUNCTION MODULE
2 Rescale from (rescales an input of 0 to 100 to a user defined output and limits at these values).
3 Rescale to (rescales the input to the output of 0 to 100 and limits at 0 and 100).
5 Limit to (limits the output to 0 or 100 percent at values specified by the user).
6 Logarithm of input.
8 Add to input.
9 Multiply by input.
10 Divide input.
14 Analogue Gate (digital signal switches output between two analogue input signals).
15 Comparator (compares two inputs, when input F is greater than input E a one output is
produced otherwise the output is zero).
16 Enthalpy (calculates the enthalpy value from a temperature input and humidity input).
17 Hysteresis, only changes a digital state if the input changes outside a defined band.
The function module has up to four analogue variables as source inputs, depending on the
function being performed and usually one analogue destination address. A digital control
address may be specified for certain types of function.
Two of the analogue sources are specified by address, typically these will provide input to the
module i.e. G and H. The second two analogue sources E and F are specified as constants by
value (e.g. limits) but can be specified by a source analogue address to provide variable limits.
Note: G and H must always have a source address. E and F must always have a source address
if they are specified by source address. If any source address is specified as 0, the input is
disabled.
If E and F are specified as constants, the value must be entered in the Function module.
Dn+1 = F x (E x Dn + (1 - E) G)
Figure 13.2 Strategy symbol - First order ‘Exponential’ Filter with Gain
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). F is normally set to a constant value of 1.
Where D is the output, G is the input to have limits applied, E is the lower limit and F is the
upper limit.
In the above example, the output of loop L1 is fed to function module F1. Function module F1
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 L2.
In the above example, simple AHU control is achieved. Space sensor S1 is monitoring the space
temperature and providing an input to loop L1. The output from loop L1 is in the range 0 to 100
percent, depending on the input from S1. When the output from loop L1 is in the range of 40 to 0
percent, the output from the function module F2 will be in the range 0 to 100 percent so that when
the input to function module F2 rises from 0 percent to 20 percent, the output of F2 will fall to 50
percent. When the output from loop L1 reaches 40 percent, the dampers will be fully closed.
Function module F1 performs a similar function to F2 but when an input to F1 is at 80 percent its
output will be 50 percent which is used by driver D1 to drive the valve open to 50 percent.
It will be noticed that there is a 20 percent difference between the larger limit of function
module F2 (40) and the lower limit of function module F1 (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.
where D = output
E = upper limit
F = lower limit
If G>E then D = E
If G<F then D = F
else D=G
Figure 13.8 Strategy symbol - Limit At Figure 13.9 Sample graph of Limit At
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.
where D = output
E = upper limit
F = lower limit
G = input
Figure 13.10 Strategy symbol - Limit To Figure 13.11 Sample graph of Limit
To
In the above example, G is the analogue variable that is to have limits applied, E is the value
of the upper limit where, when G is greater than E, the module output goes to 100 percent. F
is the value of the lower limit where, when G is less than F, the module output goes to 0 percent.
The Limit To function module is often used to provide minimum ON times and minimum OFF times
with time proportional drivers.
In the above example any input signal greater than 80 percent will cause the time proportional
driver to switch ON for 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.
Output D = E log10G
where D = output
E = source/constant
G = input
The output D will be log to the base 10 of the input signal G, if the value of E is specified as
a constant of 1.00. For the module to provide output, E must be greater than 0.
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.
Output D = E √G
where D = output
E = source/constant
G = input
If the value of E is specified as one, the output will be the square root of the input value.
Square roots are most commonly used when calculating the mass flow of air or water. The
formula for mass flow is:
Mass Flow = K √ P
Internal sensor 32 is used to provide rescaled high and low alarm limits
Output D = (E x G) + (F x H)
where D = output
E = source/constant 1
F = source/constant 2
G = source 3
H = source 4
G and H represent the two inputs and E and F are constants. 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 = 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)
Output D = GxExF
where D = output
E = source/constant 1
F = source/constant 2
G = source 3
G represents the input, E and F are constants. If one of the constants is specified as 1, output
D will be the input G multiplied by the second constant.
i.e. D = G x E x 1
Output D = (G/E) x F
where D = output
E = source/constant 1
F = source/constant 2
G = source 3
G represents the input, E and F are constants. If the constant F is specified as a constant of 1.00,
the output D will be the result of G divided by E.
NOTE: Set unused constants to 1. If E is exactly equal to zero then the division will not take
place and the function will evaluate as D = G x F.
where D = output
E = source/constant 1
F = source/constant 2
G = source 3
H = source 4
If E and/or F are specified as a constant, the module output will have a maximum limit of the
constant value set.
where D = output
E = source/constant 1
F = source/constant 2
G = source 3
H = source 4
If E and/or F are specified as a constant, the module output will have a minimum limit of the
constant value set.
where D = output
E = source/constant 1
F = source/constant 2
G = source 3
H = source 4
where D = output
E = source/constant 1
F = source/constant 2
B = control bit
where D = output
E = source/constant 1
F = source/constant 2
Output D = Ex10(0.0275F-1)+F
where D = output
E = source 1 (RH%)
F = source 2 (Temp deg C)
Output D = unchanged, if the input G is in the band between levels (E-F/2) to (E+F/2).
where D = output
E = source/constant 1
F = source/constant 2
G = input
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 reaches 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.
If the band is set to zero then noise on the input source signal 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 10 second oscillator when the input is between the levels.
The value of output 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. The alarm byte associated with D will contain the binary
representation of D.
Example application
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.
It should be noted that when the A to D function module is sourced from a node corresponding to
a real sensor number, it only updates it’s output when two successive input readings are the same.
Note: When used with a 4DIX, the sensor type must be calibrated as defined by the 4DIX Data
sheet.
1) Function modules types 1 to 10 and type 16. 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 status 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 1. The alarm bits from the source in use are transferred to the output.
4) Function Module Types 15, 17. All alarm bits are ignored.
5) Function Module Type 18. The alarm bits of the destination analogue node are set to be
the binary representation of the destination analogue node value.
Y tYpe 0 17 0 =Null
1 =filterD=F*(E*D+(1-E)*G)
2 =rescale G from 0-100 to E-F
3 =rescale G to 0-100 from E-F
4 =limit at : F if G<F, E if G>E
5 =limit to : 0 if G<F, 100 if G>E
6 =log D = E* log (G)
7 =square root D=E*sqrt (G)
8 =add D = (E*G) + (F*H)
9 =multiply D = G*E*F
10 =divide D = (G/E)*F
11 =minimum
12 =maximum
13 =average
14 =gate D=E if 0, = F if 1
15 =comparator D=1 if F>E
16 =enth E=rh F=degC D=Kj/Kg
17 =hysteresis level E, band F
18 =analogue to digital
This list of function module types will generally exceed the display lines available in the
supervisor device, however initial prompts remain visible for long enough to make a selection.
Note that the symbol asterisk * in these function module definitions signifies multiplication.
E source E either
S analogue Source 0 255 address of analogue input or constant
or
Note: Source address 0 may be specified in Min, Max and Ave functions to disable that input.
Note: When setting up E or F the letter S (source) or C (constant) must be entered before the
number.
The IC Comms module is used to specify the node(s) from which the data is taken and to which
node(s) the data is sent. The communication may be from analogue node(s) to analogue
node(s) or from digital node(s) to digital node(s).
The communication may be set up with a controller on a remote LAN by entering the
destination LAN number.
14.1 Directions
The IC Comms module has 7 direction classes:-
In direction types 0,1 (data from or to) the remote controller is specified by network node
address (and remote LAN). In direction types 2-6 (global to, min, max, sum, and average) the
remote controller is defined by controller attribute (and remote LAN). Direction types 2-6
make use of text communications which are described more fully in section 29. IQ controller
attributes are set up in the address module as shown in section 5.4. Of these seven directions,
types 0, 3, 4, 5 and 6 transfer data from a remote controller(s) to the current controller (a
FROM communication) and in types 1 and 2, data is transferred to a remote controller(s) from
the local controller (a TO communication).
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 between sending the communications (updating the value).
For FROM communications in the special case where the interval is zero, the FROM
communication will be requested again as soon as the data is received which may be up to 6
times a second, so this setting is not recommended.
For TO and GLOBAL TO communications the message will be sent whenever there is
significant change (i.e. not just at the specified interval).
For all TO and GLOBAL TO communications if no significant change is found it will be sent
at the checking interval. If the interval is set to zero the communication only occurs when there
is a significant change.
For all 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 interval
is set to zero, the message is immediately resent after the visitor message returns. This should
be avoided by setting the interval to non-zero. If the the message fails to return, it is resent after
2 minutes.
0 = analogue
1 = digital byte
2 = digital bit
Only analogue type variables can use directions 3, 4, 5 and 6 (min, max, sum and average).
81 N1 62
21
TO
In the above example, (as shown on the control strategy for controller 20). Controller 20
analogue 81 value is being transmitted TO controller 21 analogue 62.
81 62
20
The above figure shows how the controller 20 TO communitcation would be represented in
the control strategy for controller 21.
81 N1 62
20
FROM
In the above example, (as shown on the control strategy for controller 21), controller 21
analogue 62 is requesting the analogue value FROM controller 20 analogue 81.
81 62
21
The above example, shows how the controller 21 FROM communication would be represented
in the control strategy for controller 20.
Analogue communications also cause the alarm status bytes for the source analogue node to
be transferred to the alarm status bytes for the destination analogue node. Only bits 0-5 are
sent; bits 6 and 7 are not sent.
Thus for the TO example above (Figure 14.1) there is also a hidden communication
represented by fig14.6.
BYTE BYTE
121 102
Although not specified the appropriate alarm byte is also transferred. There is a similar transfer
for a FROM communication as represented in Figure 14.7.
BYTE BYTE
121 102
bits 0-5 bits 0-5
20 N 1
FROM
BYTE 28 BYTE 3
N2 21
TO
Figure 14.8 IC Comms strategy symbol - Direction TO, Variable Digital Byte type
In the case of byte communications the diagram used in the strategy is shown as above. If
particular bits are used, these can be shown on the strategy.
BYTE 28 BYTE 30
G1
4 20 Id 4 E
FROM
COMB
Figure 14.9 IC Comms strategy symbol - Direction FROM, Variable Digital Byte type
Figure 14.10 IC Comms strategy symbol - Direction TO Variable Digital Bit type
Figure 14.11 IC Comms strategy symbol -Direction FROM Variable Digital Bit type
The above example shows how the above would be represented in the control strategy for
outstation 21.
14.7 Direction Types 2-6 (global to, min, max, sum, average)
These direction types make use of attributes to define the controller(s) and node(s) involved
in the communications. The data part is fixed, as IC Comms only supports communications
of node values. The two attributes required are those necessary to define the controller and
those necessary to define the item (in this case a node).
Thus for one controller to communicate with other controllers, all must have a matching
attribute set up in their respective address modules. (The wildcard may be used see 5.5.3).
The following special characters & | ? . * are permitted in the attribute. The functions of these
special characters are described in detail in section 5.5, a brief summary follows:-
This is used to specify two or more attributes which are both required to exist in the selected
controller(s). Note: & may be repeated in an attribute address.
14.8.2 | (pipe)
This is used to specify two or more attributes of which one or the other (or both) may exist in
the selected controller(s). Note: | may be repeated in an attribute address.
14.8.3 * (asterisk)
This wildcard specifies a match for any number of any characters including no characters (i.e.
zero length).
This wildcard specifies a match for any single character (but not no character).
This is used to truncate an attribute when being used to initiate a communication. The
characters after the full stop are ignored and the full stop is replaced with an asterisk which has
the wildcard meaning defined above.
Note as mentioned in 5.5 these reserved characters only make use of their special meanings
when being used to initiate a communication, if they are in the controller being communicated
with then they must have an exact match with the initiators attributes. The special characters
\ / ( { ;
should not be used in an attribute.
NORTH NORTh N
NORTH NORTH Y
NORT NORTH N
NORTH NORTHWEST N
NORTH NORTH* N
NORTH NORTH&STH N
NORTH NORTH|STH N
NORTH NORT? N
NORTH NORTH.STH N
NORTH&STH NORTH N
NORTH&STH NORTH
STH Y
NORTH&STH NORTH&STH N
NORTH&STH NORTH
NORTH&STH NORTH
WEST N
NORTH|STH NORTH Y
NORTH|STH STH Y
NORTH|STH NORTH
WEST Y
NORTH|STH NORT N
NORT* NORTH Y
N* NORTH Y
NORTH* NORTH Y
NORT? NORTH Y
NORTH? NORTH N
NORTH? NORTHS Y
NORTH? NORTHSTH N
N?* NORTH Y
N?* NO Y
NORTH&* NORTH
WEST Y
NORTH&W* NORTH
WEST Y
NORTH&W* NORTH
WILD Y
NORTH&W* NORTH
STH N
NORTH|W?* NORTH Y
NORTH|W?* WEST Y
NORTH|W?* WE Y
NORTH.STH NORTH* NORTH Y
NORTH.STH NORTH* NORTH.EAST Y
NORTH.STH NORTH* NORTHWEST Y
NORTH. NORTH* NORT N
NORTH.EAS NORTH* NORTHW Y
If the Remote address is set up (i.e. non zero) then the message is transferred to or from that
node (i.e. absolute specification). For analogue variables it transfers the value plus the
associated 8 bit alarm status, for digitals it transfers byte or bit as appropriate.
If the Remote address is 0, then the label associated with the Local node is used as an item
attribute. This only applies to Sensors, Knobs, Switches and Digital Inputs, and only to
analogue or digital bit variable types.
If the label of the Local node is used as an item attribute as described above, then a matching
label must also be set up in the module(s) associated with the remote node(s). The remote label
may be for the modules above i.e. sensors, knobs, digital inputs and switches, but it may also
be set up in drivers.
For a global to, if a match is found with any of the labels of these modules an attempt is made
to write into the module value and status for an analogue, and status only for a digital bit. Thus
for analogues (Sensor or Knob), it tries to set up the value V, and the alarm bits M whereas for
a digital bit (Digital Inputs or Switches) it tries to set up the status S. If the destination module
cannot accept these parameters then the data transfer will not occur.
Table 14.2 Showing parameters accepted or rejected by modules accessed by label matched
global messages.
This matching of labels creates a problem with IQ's which have universal inputs and hence share
one label between digital inputs and sensors (all IQ's except IQ151 or IQ151+). This can result
in invalid messages being returned which cause the IC comms to be retried repeatedly.
In these cases the module which replies to the message is dictated by the setting of the sensor
module mode. If the sensor module is set to analogue (analogue input or internal analogue
mode), then it will deal with the IC comms itself, but if it is set to digital (digital input or internal
digital mode) then it will pass the IC comms to the associated digital input module.
In the following examples we are assuming that a GLOBAL TO IC comms is sent from an IQ
controller by setting its Remote address to zero and setting its local node to 3,0. This forces it
to use the label of Digital Input 17 (I17$) as an attribute, and it will try to set the status (S).
N
GLOB
3,0 i17$ = LABEL
To work correctly:
For an analogue IC comms, the receiving sensor must be set to Analogue input or Internal Analogue.
For a digital IC comms, the receiving sensor must be set to Digital input or Internal digital.
If the GLOBAL TO (direction 2) message has its item defined absolutely for an analogue value
it will also send an alarm status of 8 bits, whereas, if the global to has a Remote address of zero,
and it uses the label associated with the Local address as its item attribute it will send a status
of 4 bits (bits 0 to 3).
14.9.2 Functions
For max, min, sum and average directions (functions), then the communications apply to
analogues only. In this case a value (V) is requested from the module(s) with matching labels.
Driver modules have a special ‘V’ parameter which is used to reply to text comms only (read
only), and the V values can also work from matching digital inputs or switches.
In addition, 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 an associated status byte
which has either Read or Out of Limits alarms indicated then that node’s value will not
contribute to the result.
For example to communicate with OUTSIDE AIR TEMP sensor, set up a sensor in this
controller (say Sensor 20) to have the label. Then the sensor(s) in the controller(s) to be
communicated with has to be set up with the same label.
Set up this controller’s and the other controller(s) device attributes to match and the direction
type should be 2 (global to).
The communication will now use item attribute OUTSIDE AIR TEMP to specify the node
to be communicated with and it will look for any identifiable module with this label (i.e.
Sensor, Knob, Driver, digital Input, or Switch).
It is important that the labels only match with the required modules.
? * .
and their use is as explained in 5.5. The following characters should not be used in a label
\ / ( { ;
In the case of global messages sent to the local LAN (local global) or all LAN’s (global global)
the message is received by the originating controller, unless the originating controller’s own
LAN has been set up.
Thus if the Remote address is set to zero and the local address is in the byte range 13 to 17 then
the label of the zone is taken as an attribute and ANDed with the selected device Attribute.
This means that the remote address is not specified by zone label as this is now a device
attribute. The actual remote address used is always specified absolutely as being byte 13.
Zone 2 label=Canteen
The device attribute becomes AHU1&Canteen. The communication item attribute becomes
byte 13. This facility can be used when a larger controller is a team leader to several IQ90s.
These IQ90s can constitute one zone of the team leader. They can be changed to another zone
by altering one of their device attributes to make the label of the required zone of the team
leader, avoiding the need to change the strategy.
Because the zone label can be used as a device attribute it too gives special meaning to the
characters
&|*?.
This use of zone labels has particular relevance when team leaders are sending occupation
times to team members as explained in section 29.5.
These messages will contain the Personal Identification Number (PIN) code specified for user
number 1. Controllers that are to receive these messages must contain a matching PIN whose
password level is high enough to permit the change requested unless there are no user
passwords 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 (bit only); 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
password.
Direction 0 from
Address 22 remote laN 0
timer 0 Interval 5
Var: analogue Remote 1
Local 33 v 12.01 s 0000
This transfers a value from controller 22 analogue node 1 on local LAN to node 33 in this
controller.
Direction 0 from
Address 22 remote laN 5
timer 0 Interval 5
Var: dig byte Remote 18
Local 33
This transfers a byte value from controller 22 byte 18 on remote LAN 5 to byte 33 in this controller.
This transfers a bit from controller 22 bit 18,3 on remote LAN 5 to bit 19,0 in this controller.
Direction 1 to
Address 37 remote laN 101
timer 0 Interval 10
Var: dig bit Remote 32,3
Local 22,4
last sent status 1
This transfers a bit from this controller bit 22,4 to controller 37 bit 32,3 on remote LAN 101.
Here the comms will be sent
a) every 10 minutes
b) whenever the last sent bit status differs from the current status.
Direction 1 to
Address 35 remote laN 6
timer 0 Interval 10
Var: analogue Remote 45
Local 9 v 56.48 s 0000
last sent v 56.32 s 0000
Sig change 1.00
This transfers a value from this controller node 9 to controller 35 node 45 on remote LAN 6.
Here the comms will be sent
LAN 9
N 36
TO
BYTE 1 BYTE 32
Direction 1 to
Address 36 remote laN 9
timer 0 Interval 30
Var: Dig byte Remote 32
Local 1
last sent status00010000
This transfers a byte from this controller byte 1 to controller 36 byte 32 on remote LAN 9. Here
the comms will be sent
a) every 30 minutes
b) and whenever the current byte status varies from the last sent status.
1 5
N @2=XYZCo
Direction 2 global
Attribute 2 remote laN 128
timer 0 Interval 10
Var: analogue Remote 5
Local 1 v 2.10 s 0000
last sent v 2.30 s 0000
Sig change 0.5
This transfers a value from this controller node 1 to node 5 of any controller with matching
attribute 2 on any LAN (LAN 128 specifies any LAN - i.e. global/global). If attribute 2 in
the address module of this controller were set to XYZ Co then this attribute would have to be
in any controller to receive this message.
The PIN of user 1 will be sent with this message and the destination controller(s) must have
this set up with a level of 99.
Direction 2 global
Attribute 2 remote laN 0
timer 0 Interval 5
Var: dig byte Remote 32
Local 32
last sent status 00100000
This transfers a byte from this controller byte 32 to byte 32 of any controller on this LAN
(remote LAN = 0) with attribute 2.
Direction 2 global
Attribute 2 remote laN 0
timer 0 Interval 1
Var: dig bit Remote 0
Local 1,3
last sent status0
This transfers a bit from this controller bit 1,3 to a remote bit defined by the local label set up
in bit 1,3 (i.e. digital Input 4 label). It sends it to any controller with matching attribute 2 on
the local LAN.
14.12.3 Directions (3, 4, 5 and 6) min, max, sum and average Examples
Direction 4 max
Attribute 3 remote laN 0
timer 0 Interval 5
Var: analogue Remote 0
Local 18 v 73.11 s 0000
This sends a message from this controller to any controller on the local LAN with matching
attribute 3. It asks for the maximum value of any analogue node in those controllers whose label
matches the label of Sensor 18 in this controller to be put in node 18 of this controller.
For instance if this controller’s address module attribute 3 = AHU3 and the label of this controller’s
sensor 18 isDAMPER.MAX. It would send a message to any controller with attributeAHU3 with
an item attributeDAMPER*. If addressed controllers have nodes labelledDAMPER POSITION,
then this controller will put maximum damper position in DAMPER.MAX.
Direction 5 sum
Attribute 3 remote laN 7
timer 0 Interval 1
Var: analogue Remote 0
Local 19 v 2240.6 s 0000
This sends a message from this controller to any controller on remote LAN 7 with matching
attribute 3. It asks for the SUM of value of any analogue nodes in those controllers whose label
is the same as the label of Sensor 19 in this controller to be put in node 19 of this controller.
For instance if this controller’s attribute 3=AHU3 and the label of Sensor 19 is Cooling
Demand then it will get the sum of all nodes labelled Cooling Demand in all controllers with
attribute AHU3 and put the resulting value into node 19.
14.12.3 Directions (3, 4, 5 and 6) min, max, sum and average Examples (Continued)
Direction 6 average
Attribute 2 remote laN 7
timer 0 Interval 1
Var: analogue Remote 0
Local 20 v 21.78 s 0000
This sends a message from this controller to any controller on remote LAN 7 with matching
attribute 2. It asks for the average value of any analogue nodes in these controllers whose label
is the same as the label of sensor 20 of this controller to be put in node 20 of this controller.
In this case the communication message actually returns 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 count. The resulting average value is placed in the specified local node.
If controller 37 on LAN 83 has an Outside Air Temperature sensor (No.5) labelled Outside
Temp.Orig, and this value is required to be distributed to all other controllers every 10 minutes,
each receiving controller may place the data in any sensor node with the labelOutside Temp.Copy.
Direction 2 global
Attribute 7 remote laN 128
timer 0 Interval 10
Var: analogue Remote 0
Local 5 v 13.11 s 0000
last sent v 13.12 0000
Sig change 0.5
The message is sent from this controller node 5 to any controller on any LAN with 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 5 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. The PIN’s must be set up appropriately.
Note this example demonstrates the use of the . (full stop) in an attribute, as this controller can
communicate with all Outside Temp.Copy nodes and the supervisor can communicate with
Outside Temp.Orig exclusively.
5 10
37 N
LAN 83 FROM
Figure 14.25 Strategy symbol - individual request - data from - analogue value
Direction 0 from
Address 37 remote laN 83
timer 0 Interval 10
Var: analogue Remote 5
Local 10 v 13.12 s 0000
This will cause this controller to request controller 37 on remote LAN 83 to send a value from
its node 5 to node 10 of this controller.
Absolute Addressing
NOTE: The expression MOD15 means the remainder left after dividing by 15. For example
controller 20 will have a critical alarm delay of (30+20MOD 15). The remainder after dividing
20 by 15 is 5, so the delay will be (30+5=35 secs). Controller 21 would then have a value of
36 seconds etc. Note that controller 35 will also have a delay of 35 seconds.
14.15 Retries
When an IC Comms channel message (output or request) is sent, the originating controller will
wait 13 or 15 seconds for a reply (13 seconds if the destination address is greater than the source
address, else 15 seconds). If no reply is received within the wait period, then the originating
controller will note this and mark the message accordingly. However, other channels will be
checked and actions taken before the message awaiting a reply is retried.
- if the source address is a sensor and the direction is 2 to7, an IC Comms message is
transmitted containing 4 alarm bits.
- if the source address is a free analogue node and the direction is 2 to 7, an IC Comms
message is transmitted containing 8 alarm bits.
D Direction 0 6 0 = from
1 = to
2 = global to
3 = min
4 = max
5 = sum
6 = average
For directions
1 and 2
(global and to)
comms.
Whenever there is a significant change (as
described below), the current values are
sent to the remote controller. Additionally
if there has been no significant change in the
interval and the interval is not zero,
the values are sent anyway. The comms are
not sent more frequently than once every
15 seconds. A change for analogue comms
is defined as:- the difference between the
last sent value and the current value being
greater than the significant change S or a
change in the analogue status since last
sent. A change for digital comms is a change
in status since the data was last sent.
15 KNOBS
Knobs enable access from supervisor or display panel to the analogue nodes, or module
parameters (adjustments).
The function performed by any knob is determined by the strategy within the controller. The
knobs allow analogue values A221 onwards to be changed.
The knob label can be used as an item attribute for text communications. This is explained for
IC Comms in section 14.9 and more generally in section 29. Special characters are as follows:-
? * .
In either mode the knob has a pre-set user password level to protect it from change by an
unauthorised person using the display panel. Supervisors also have pre-set user password
levels to prevent change of knob values by an unauthorised person.
i.e. IS1H<CR> selects Id (identity) followed by S1H for the adjustment of the Sensor 1 High
alarm value.
The range over which the parameter may be varied is the normal range of that parameter in
configuration mode.
Adjustment mode allows specified module parameters, which can normally be accessed only
in configuration mode, to be accessed (monitored and changed) via a knob.
1) Display Panel
2) Supervisor
3) Strategy i.e updated by making the knob node a destination of a module.
The parameter is updated by transferring values from the knob node to the module parameter.
This is done by using the configuration mode program routines. If an operator is using
configuration mode a change in the knob node value will not be transferred until the
configuration mode is exited. This also applies when setting up the Knob adjustment itself; the
values will not be transferred until the user leaves configuration mode and Exit from Utility
is received.
The Knob updating is also asynchronous to the sequence table and occurs between the
sequence table steps.
Because values are transferred from the knob node to the module parameter and not vice versa,
certain adjustments that may be used are not recommended. Although these adjustments are
permitted, the knob value would constantly be resetting the parameter and not allow it to be
automatically updated.
For example if the Knob Id is set to Timer Hours (TH) then the value of the hours will always
be the same as the knob node i.e. the real time clock cannot update the value.
calEndar Day
Month
Start/Stop dates
critical alarMs Destination ü
digital Input actual state
Required state ü
alarm Enabled ü
Delay ü
acKnowledged state
Hours run
No. of starts
Knob Value
Top of range ü
Bottom of range ü
Pin level ü
loGic module oN delay ü
tYpe 2 Timer Min on ü
oFf delay ü
tYpe 3 Readback grace Time ü
tYpe 4 Counter rescheduleTime ü
scale Factor ü
tYpe 5 Delay grace Time ü
tYpe 6 Hours Run Hours
sensor tYpes
sWitch Status ü
Pin level ü
Time module Hours
miNutes
Day of month
Month
Year
day of Week
Start day
start mOnth
End day
end monTh
chanGe by
User Level ü
Pin ü
Note: The Identity in Knob Adjustment mode is the normal configuration mode reference for
that parameter. (This can only be 4 characters long).
e.g. To adjust the high alarm for sensor 1 would need the entry: IS1H <CR>
16 LOGIC MODULE
The logic module allows outputs to be generated as a function of a number of digital values
within a control strategy. The resultant digital variable (output) is available for use by other
modules in the strategy. The logical functions available in the controller are:-
The logical combination of digital variables allows four different logical combinations to be
made of up to four digital variables (inputs) specified as source addresses. These logical
combinations are designated functions J, K, L, and M and can only be logical AND or AND
NOT functions as explained below.
Each of the four logical functions are evaluated and the four resultant product terms are
summed (logical OR). The result is fed to the module output digital destination address for
use by other modules in the controller.
In this way the combination logic module allows the logical AND, NOT AND (NAND), NOT
OR (NOR), and OR 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 a one 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.
The inputs that are to have logic applied are specified by digital source address, designated
source address E, F, G and H. Up to four logic functions (J, K, L and M) may be performed on
the four source addresses. Each function is OR’ed with the other functions used.
16.1.1 Example 1
Function J = E
Function K = F
O/P = E+F = E OR F
In the above example, the logic OR function is being performed on source values E and F.
Where, if the bit state of source address E or F is 1, then the module output bit state will be 1.
16.1.2 Example 2
Function J = EF
O/P = E.F = E AND F
In the above example, the logic AND function is being performed on source addresses E and
F. Where if the bit state of source addresses E and F is 1, then the module output bit state will
be 1. If either or both source address bit states are 0 the module output bit state will be 0.
16.1.3 Example 3
Function J = ef
O/P = e.f = NOT E AND NOT F
In the above example the logic function is being performed on source values E and F. Where
the output is 1 if both E and F are zero or conversely the output is zero if either E or F is 1.
A simple way to to derive the boolean expression for the required logical function is to write
down a conditional statement. Say, for example, we require to switch a fan on when there is
a manual override or when there is a demand greater than 20% and the building is occupied,
or when there is a demand greater than 10% and building is non-occupied. The conditions we
will have to monitor are:-
Manual Override ON
Demand > 20%
Building Occupied
Demand > 10%
Building Non-Occupied.
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
Now Building Non-occupied is the same as NOT Building Occupied. So the above conditional
statement can now be written as:-
E+FG+Hg
MA N OV ERRIDE E G1
E
DE M A ND > 20% F +
FG D
OCCUPIED G +
Hg
DE M A ND > 10% H COMB
To check that the function works correctly, the rigorous approach is to write down 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 counting if ON and disable it if OFF.
E G1
D
E NA B LE F CO 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 count is disabled so the output stays at 0. In row two
the count is now enabled so we want the count to change i.e. D is 1. In row three the output is
1, but the count is disabled so we want the output to be 0. In row four the output is at 1, the count
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
ON-Delay: This timer function switches on when the specified ON delay set by the user
has elapsed. This only applies if the module input is maintained in the ON state
throughout the delay period.
Minimum on-Time: This timer function switches the module output ON for at least the
preset time period (set by the user). 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.
OFF-Delay: This timer function delays the module output from switching OFF, after
the input has switched OFF, until the preset time delay (set by the user) has elapsed. The
OFF Delay only applies if the input remains in the OFF state.
G3
TIMER
20
o N de lay or N=20
20 Min im um on tim e or M=20
20
oF f d elay or F=20
The following shows the timing diagrams for different timer functions where t represents time
and t total is the total time.
00 00 00N00 00 00 00 t-N
00 00 00 00 00 00 00
00 00 00 00 00 00 00
ON
DELAY
M
000000000
000000000
000000000
000000000
000000000
000000000
MINIMUM
O N TIME
Figure 16.10 Minimum ON timer function where t total = M = Minimum on time and M>t.
Note if M is greater than t, the output will be ON for M and if M is less than t, the output will
be on for t.
t F
000
000
000
000
000
000
OFF
DE LA Y
Figure 16.11 OFF Delay timer function where t total = t + F, F = oFf Delay
The logic timer module allows timer functions to be used in combination as follows:-
00 0 0N0 0 0 0 0000
00 000 000 000 000 000 000
t-N F
0000
0000
0000
0000000 0000
0000
Figure 16.12 Timer functions provide an oN delay and oFf delay where t total = t - N + F
00 00 00N00 00000000000000
00 00 00 M
00 00 00 00 00000000000000
00 00 00
000000000000
0 0 0 0 0000000000000
000
000000000000
000000000000
Figure 16.13 Timer functions provide an oN Delay and minimum on Time where t total = M.
M F
000000000000
0000
000000000000
0000
000000000000
0000
000000000000
0000
000000000000
0000
000000000000
0000
Figure 16.14 Timer functions provide a minimum on time and an oFf Delay where t total =
M + F. This combination provides the maximum on time of 65534 seconds.
0 00 00N00 00 00 00 0000000000000
00 0 0 0 0 0 0 000000000000 M
0000
F
0000
00 00 00 00 00 00 00 0000000000000
0000
00000000000
0000
0 0 0 0 0 0 0 0000000000000000
00000000000
0000
Figure 16.15 Timer functions provide an oN delay, Minimum on time and an oFf delay.
Where t total = M+F.
The logic readback module has two source addresses that are used to specify the address of the
digital output and two source addresses that are used to specify the readback address of the plant
readback input. Normally, only one digital source address and one readback source address are
used. The second source and readback should be set to address 0,0 if unused.
G R A CE TIM E S HO W N H E R
DIGITA L SOURCE A DDRESS 1 E G3
DIGITA L SOURCE A DDRESS 2 (OPT) F
30s D A LA RM BIT DESTINA TION A DD
REA DBA CK SOURCE A DDRESS 1 G
REA DBA CK SOURCE A DDRESS 2 (OPT) H RDBK
Only show inputs used.
The inputs are compared whenever the logic module is serviced in the sequence table (see
Section 23) and if the two inputs (i.e. source 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 alarm output will be set.
The effect of this is that the plant being controlled and monitored has the grace time in which
to switch on, or off without producing an alarm, and also if the plant 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.
OUTPUT
SOURCE
RE A DB A CK
TIMER
S TA RT S TA RT S TA RT S TA RT
In the above diagram, if the period from start to reset ever extends beyond the grace time then
an alarm will be sent. An example of the use of the readback module is given in Section 12.8.
The logic counter module has two digital source addresses, digital Source and Reset and two
analogue output addresses, Rate and Cumulative.
G3 R RA TE
F=10 S C A LE F A CTO R
DIGITA L SOURCE S
RESCHEDULE TIME
T=900s
CNTR M CU M ULA TI
A
RESET
The digital source and reset addresses can be specified as any digital node, external or internal.
If the digital source is an external digital input node then the digital input module itself carries
a count of the number of starts which it monitors at 15.6 ms intervals. Thus the digital input
counts pulses which are on or off for greater than 15.6 ms (i.e period = 31.2 ms, maximum
frequency = 30Hz) - see section 11. Every sequence table cycle the change in count will be
transferred from the input module to the counter module.
NB: It is important that to achieve this transfer of fast count data, no other modules are placed
between the digital input module and the counter module. Also the number of starts should not
be changed or reset within the digital input module.
If the digital source is internal, then it will only be monitored every time 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: number of times module is sequenced
2 x cycle time.
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. At
the end of the reschedule period, the rate output is changed and the rate value (i.e. change in
count) is added to the cumulative output.
If the reset input address is set to 0,0 and the source is a real digital input or digital output then the
number of starts count is moved directly from digital input to the output node without scaling.
If the reset address is not 0,0 and the reset bit is at a 1 state (set) when the module is serviced
in the sequence table, whether or not the reschedule period has just ended, the cumulative
output is set to zero.
C u m u la tive
C o unt
0
re s c h e d u le tim e
p e rio d
re s e t p o int
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).
G1 R G F1
Gx4 S1 CURRE NT 15 m
F=0.48 4 E I A V ERA GE RA TE
P ULS E
1 S 1 F M ULT (kW)
METER
1,0 T=900
CNTR M S9
I 96 DA Y LOG
R
24 HO UR P ULS E
493,4
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.
The counter module, as with any computer, only performs mathematical calculations to a
limited number of significant figures, 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 reshedule 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.
G1
SOURCE E 30s
D
RDBK G
DEL
This logic module is specifically designed for interacting with the alarm reporting mechanism
of the strategy. In general, if the source changes state, it will clear the internal timer and the
output bit. After the grace time elapses, then the output bit will be set if the readback bit is not
equal to the source and will clear as soon as the readback is the same as the source.
G RA CE TIM E S HO W N
G1
(SOUR CE) A LA RM S TA TE E 30s
D A LA RM ENA BLE
(REA DBA CK) A LA RM G
A CKNOW LEDGE DEL
A LA RM STA TE
A LA RM E NA B LE
A LA RM A CK NO W LE DG E
As can be seen from Figure 16-22, when the alarm state occurs the grace timer is started. If the
alarm still exists when the grace time ends alarm reporting is enabled. Similarly, when the clear
alarm state occurs, the grace timer is started. If the clear alarm state still exists when the grace
time ends alarm reporting is enabled until acknowledgement received.
HOURS
G1 O DESTINA TION
SOURCE S
RESET
This module is designed to count the hours for which the source bit is on and send the output
to the hours destination.
The module also checks if the hours run has exceeded the interval limit and will set the interval
destination bit to a 1 when the limit is exceeded.
When the reset input node goes to a 1 state, the hours destination node is set to zero and since
the hours run is less than the interval this also sets the interval destination to zero.
If the source node is either an input channel node (from a real digital input) or a real output
channel node, the hours run will be accurate to the timing levels of these channels (to nearest
125 ms). This does not apply to internal digital inputs or internal driver outputs, however hours
run logic modules can still be used to give hours run accurate to the sequence table cycle time.
1) Facilitate strategies which require the usage of plant (e.g. pumps, boilers) to be cycled
upon the basis of hours run.
22,0
P UM P DE M A ND
2 2,1 D1 7,0 S RM
DUTY P U M P S E LE18,0
CT L P UM P 1
1
0= P UM P 1 DIG
1= P UM P 2
E G3
G5
F E
1,0 30s D
GCOMB 1 G
PUMP 1
RDB K 22,5
E G1 FLOW
F E+fg
G EFH 22,2
H CO M B
PUMP 1
FA IL
S E T A S DRIV E R 1
R/BACK ALARM BIT
PUMP 2
FA IL
S E T A S DRIV E R 1
R/BACK ALARM BIT
G G7 E G2
gE+GE F E+Fh
F +
Gf+gf G Efg 22,3
E H CO M B
COMB 2 2,7
1,1 G5
E G4 2 E
30s D
F EG+F PUMP 2 G
FLOW
RDBK
G COMB
DIG 7 ,1
S RM
L 2 PUMP 2
22,4 D1
E source address E
Byte 0 505 Address of digital input bit 1
Bit 0 7
F source address F
Byte 0 505 Address of digital input bit 2
Bit 0 7
G source address G
Byte 0 505 Address of digital input bit 3
Bit 0 7
H source address H
Byte 0 505 Address of digital input bit 4
Bit 0 7
D digital Destination
address
Byte 0 497 Address of digital
Bit 0 7 output bit
S Source address
Byte 0 505 Address of digital input bit.
Bit 0 7
D digital Destination
address
Byte 0 505 Address of digital output bit.
Bit 0 7
F scale Factor Real Number Sets the value of each pulse count.
Maximum count rate on internal digitals = one count every sequence table cycle time x2.
17 LOOP MODULE
Control loops perform the mathematical calculations that determine, on the basis of present and
past values of the measured or derived variables, how control instructions to other modules will
change.
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).
A
P = Process Variable Address
P
O = Occupancy Setpoint Address
O U = Unoccupied Setpoint Address
L1
U L = Manual Level Address
L
A = The Manual Select bit Address
S
S = The Setpoint Select bit Address
1) If A is set to address 0,0 then the manual level (L) need not be shown
2) If the occupied and unoccupied setpoints are connected together then an X can be shown
against the S address to indicate it has no effect.
3) If a zone time is used for the S input it should be fully labelled e.g. zone 1, OTP.
TE M P E RA TURE
S E NS O R
RA IS E
HO T W A TE R
RA DIA TO R
In the above diagram, the sensor is measuring the temperature of an airspace. The output of the
sensor will be a signal (current or voltage) which varies in a defined way with the temperature.
If the sensor produces a current it is converted to voltage by the input circuitry of the controller.
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
18
22
RADIATOR
The process by which the controller decides what the output level should be for a given input
is described by a diagram as shown above. In the strategy diagram the software modules are
represented by fixed shapes (see Section 5 et seq.).
In the above strategy the voltage level 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 whatever engineering units the controlled variable is measured.
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.
The loop will now generate an output which is designed to reduce the error (i.e. move the process
variable towards the setpoint). This output will be proportional to the error (the bigger the error, the
bigger the output) and may also increase as the error persists. The proportional output is set by the
gain constant, and the amount to overcome a persistent error is set by the integral constant.
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.
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 section 12.4).
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 would be called Night Setback. If the unoccupied setpoint were 5 deg C it would
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 status 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.
ON ON
100% 100%
If a sequenced heater is used so that for a large error two heating elements are switched on and for
a smaller error only one element is selected, then we can now select 100%, 50% and 0% heating.
If we add more heating stages we approach a condition where we only select the number of elements
needed at a particular level. This is approaching proportional control where the number of elements
is proportional to the error. This results in a smooth curve about the setpoint.
PROCESS P RO P O R TIO NA L
V A RIA BLE C O NTR O L
TIME
S ETPOINT
O U TP U T C O N TINU A LLY V A R IE S
TO REDUCE ERROR
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.
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 :-
Graph 17.6 shows the relationship of output to error for various gains
OUTPUT
100 GAIN 50 GAIN 25
90 GAIN 10
80
70
60
50
40 GAIN 5
30
20
GAIN 2
10
.
ERRO
1 2 3 4 5 6 7 8 9 10
NOTE
ERROR=SETPOINT-MEASURED VALUE
OUTPUT=ERRORxGAIN
Figure 17.6 Graph of Loop output to Error for various Loop Gains
In the case of cooling control loop output will occur when the process variable is above the
setpoint. That is the error is negative.
Because:-
The loop output must be made positive for a negative error by making the loop gain negative.
So for a cooling loop the gain is set negative.
The choice of loop gain is critical to the performance of the system and the loop’s response to
changes in process variable. The graph below shows the response of a system to an increase
in setpoint (e.g. from non occupied to occupied) with insufficient gain.
TEMP
s.p.
TIME
Figure 17.7 Graph of Temperature against time - Loop gain too small
The temperature response is a very slow rise which drifts up to a steady level well below the setpoint
(overdamped). If the gain is increased there comes a point as shown below where the second
oscillation is a quarter of the amptitude of the first. This is optimum loop gain for fastest response.
TEMP 2nd osc=1/4 1st
s.p.
TIME
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.
TEMP
s .p.
TIME
Figure 17.9 Graph of Temperature against time - Loop gain too high
When each peak is the same height as the previous; thecritical stability limithas 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 section 17.7 Loop Tuning.
It will be noticed that even the optimum gain produces a final steady level that is below the
setpoint. See figure 17.8. 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.
17.3.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:-
= 2 °C
Increasing the gain to 20 would decrease the error to 1 °C but may affect stability as explained
above.
TIME
The integral term, integrates (accumulates) the error over a time period and adds a proportion
of this accumulated sum to the loop output. The integral time constant is defined as the time
for which the loop output will 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.
∫
integral term = G (E.dt)
I
∫I
Thus Loop o/p = GE + G(E.dt)
Just as increasing the gain produces instability, so does decreasing the integral time constant
(increasing integral action) and selecting the integral term is critical. (See section 17.7 Loop
Tuning).
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
Loop o/p = ∫
GE + G (E.dt)
I
Change in loop o/p due to integral = G. E.dt.
I
Using the example above for a fixed error of 2 deg C for 1 minute
= 20 x 2 x 1
10
Chane in loop o/p = 4%
e.g. to achieve a 5 sec reshedule time on an IQ151+ from table in appendix 1; for IQ151+
minimum loop reshedule time = 15 secs therefore to achieve reschedule time of 5 secs
requires 3 entries in sequence table.
Since there are 400 steps in IQ151+ (see Appendix 1) entry points are at 400 steps.
3
e.g. step 1
step 134
step 267
Using multiple sequence table entries means that the integral part no longer truly reflects the
integral time constant.
PID control is a very effective technique, if the load on a control loop is changing rapidly. In
the same way as the integral term, the derivative term is expressed as a time constant in minutes.
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.
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 in configuration mode and
is subtracted as above if the derivative time constant (T) is non-zero.
Loop o/p = ∫
GE + GE.dt - GT d(Pv)
I dt
The derivative used in the IQ is filtered by taking the average of the current value and last value.
new Pv difference = current Pv difference - last Pv difference
2
The selection of optimum derivative time constant is also covered in the section below on
Tuning Control Loops.
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.
Set the integral time and derivative time to zero. Increase the proportional gain of the loop in
stages (say 5, 10, 15, 20 etc.) waiting each time to see the control result. When the loop is at
critical stability limit, note the proportional gain Gc and the period of one complete oscillation
Pc (minutes).
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
This method avoids the necessity of putting the loop into oscillation. Set the loop to manual
control at zero output and allow conditions to stabilise. Next increase the manual output by
a step S (say 10%) and plot the response as follows:-
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 all other analogue inputs are in engineering units (for this example, 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.
The error can be in the range of plus or minus the deviation alarm limit relative to the setpoint
during occupation, but during non-occupation it can be between the non-occupied setpoint
minus the deviation alarm limit and the occupied setpoint plus the alarm limit.
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
If the setpoint selection bit 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.
In configuration mode, a parameter ‘dEfault’ can be set up. Its actual meaning depends on the
Loop Fail type selected.
In this case the control loop uses 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 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.
This is the same as Type 1 except the loop does not return to normal control automatically.
Where this condition is present the loop alarm status default output (bit 2 or bit 6) is set.
To return the loop to normal control, it must be put into manual, and then returned to automatic
control (i.e. set A 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 the last correct scan level. This works well for short-
lived failures since the plant continues without any major disruption. However, it should
be noted that, if the failure happened outside occupation, then the loop would most likely
be held at zero output, and no heating would be achieved the next day.
Type 4: No Action
This type ignores the alarm status on the process variable (Pv) and continues to attempt to
control using the Pv 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.
This is the simplest control that can be applied. The control loop is set to have a high proportional
gain, no integral and no derivative terms. When the sensor reading is higher than the setpoint, the
loop output will be zero. When lower, it will be 100. The output signal is fed to a simple binary ON/
OFF driver, such that an input signal greater than 99 will switch the output on and a signal of less
than 1 will switch it off. (Note: this driver has hysteresis - see Driver Section).
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:-
This uses the same plant connections as in the previous example, but drives the pump in a
pseudo continuous manner by using a time proportioning driver. In this case a time period is
chosen for the driver to define the frequency at which the pump will be switched. The period
chosen must be a compromise between the best level of control and the level of acceptable wear
on the pump motor and contactor. In general the time constant of the heated space will be such
that a period of 15 to 30 minutes will give very acceptable results. The time proportioning driver
switches the pump on for a percentage of the period dependent upon the value of the input
signal, which in this case is the output of the control loop. If the period is less than one third
of the natural time constant of the space being controlled, control will appear to be continuous.
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.
Installed systems using this method of control generally show peak error of less than 0.5 degC.
This is a traditional way of controlling radiator heated buildings where obtaining a representative
space temperature reading is difficult. The flow temperature of the water passing through the
radiator is regulated by a three-way value. The temperature of this water is adjusted as a
function of the outside temperature.
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.
y = mx + c
comparing
then D = -3G + 75
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.
A cascade control system consists of two connected processes, a primary process and a
secondary process. These two processes are connected physically.
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 to perform this form of control would be set out as in Figure 17.23 above. The
reasons for using cascade control are:-
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.
This example (see figure 17.24) shows standard cascade control which is often used with variable
flow temperature heating systems and with AHU control. Measurements of the space temperature
are taken from sensors S2, S3, S4 and S5 and are averaged by function module F1, (F1 could be used
to take the maximum or minimum of sensors S2, S3, S4 and S5 as required). The output of module
F1 is then used as the process variable by Loop 1 which has space temperature setpoints, occupied
and unoccupied selected by the setpoint selection bit (Zone 1 OSS).
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 bit would have no effect. This is indicated by putting an X on the S bit. The change
in level with respect to occupation is performed by Loop 1.
It is possible to combine the advantages of cascade control with the compensation for outside
air temperature.
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.
Feed forward control changes the secondary loop setpoint before the primary variable detects
the change (which would normally be after some timelag).
The example shown in Figure 17.26 actually has 4 heating zones each with their own separate
control valves controlled by 4 loops. Only Loop 1 is shown but the other three zones are similar.
The loop output heat demand for the four zones is examined by function module F9 which will
calculate the maximum.
The basic flow setpoint is derived from this maximum loop output by F10 which is set up to
perform the function.
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
The function of F11 is to add the trim to the cascaded setpoint and this can be seen from the
family of straight lines shown below.
OUTPUT
F11
120 OUTSIDE
TEMP
COMPENSATED DEG C
FLOW 100 -10
SETPOINT
DEG C 0
80
10
60 20
40 10
10
20
10
INPUT
20 40 60 80 100
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 (Figure 17.26). 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:-
OUTPUT
120
OUTSIDE
TEMP
COMPENSATED DEG C
FLOW 100
SETPOINT
DEG C
0
80
10
60 20
40
20
INPUT
20 40 60 80 100
Figure 17.30 Outside Air Temp compensated set point fed to Loop module 5.
Note that loop 5 has an auto/manual control on its A bit; if this is set to 1 then the loop output
will go to 0% as specified by node 49.
As explained in section 17.3, Trend Loop modules are set to cooling loops by setting the
proportional gain to be negative. Thus the loops operate in heating mode only or cooling mode
only. When plant such as dampers which span both the heating and cooling regimes are
controlled by the Trend system, a way must be found to change from heating to cooling without
driving heating and cooling simultaneously.
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.
INCREASE HEAT
50% NO PLANT
INCREASE COOL
0%
MAX COOL
Figure 17.31 Loop output used for Heating and Cooling
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.
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:-
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
cool the recirculation dampers will be at 30%, (70% fresh air), with the cooling valve fully open.
When viewed in configuration mode the 4 bits for the loop are seen, but there are only two alarm
enable bits and two alarm acknowledge bits. The spare and Default o/p bits do not produce
alarms. So the left hand alarm Enable and Acknowledge bits refer to Pv Fail and the right hand
bits refer to SP Dev.
The default o/p bit is set when Pv Fail action is taken and the action specified is type 2 - Default
output level with manual return. If the Pv Fail alarm bit clears but the default output bit is still
present, it means that the operator has to manually intervene to return the system to automatic
control; this condition can be used to generate a critical alarm. The loop may be forced into its
PV Fail action by setting the PV Fail bit (bit 1, or bit 5) by an external source, (e.g. Logic
Module). It will return to normal operation when the bit is cleared.
Using the enable bit the SPDEV and PVFAIL alarms may be inhibited from being reported on
a per loop basis. Using byte 502, in the digital array, loop alarms may be globally inhibited
as explained in Section 6.10.
Note *: If the address of the selected setpoint is 0 then the loop is turned off. When the loop is
turned off, the output and the integral are set to 0.
E dEfault -32767 +32767 default level for sensor fail action. i.e.
either default PV or default o/p.
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.
It is not normally drawn on strategy diagrams. The output bits (defined in section 18.8) are
shown wherever they are needed on the diagram.
Note that the IQ70 Controller uses only one time zone and it is possible to enable or inhibit
this time zone using digital array 496, bit 1.
When this bit is set to 1 the time zone is inhibited so the occupation byte (in the case of the IQ70,
byte 13) is not updated, this leaves the byte free to be updated from elsewhere, normally from
a team leader, which has IC Coms set up to send out the zone byte to a team of IQ70's.
18.1 Configuration
The current values that the OSS module needs, (i.e. outside temperature, inside temperature,
medium temperature, and inside setpoints) are specific analogue addresses.
The module can operate in heating, cooling, heating and cooling, or neither (i.e. OTP only)
modes. The heating and cooling modes for an OSS module can be enabled separately by setting
up the appropriate setpoint. (i.e. if the heating mode setpoint is address 0 then the OSS heating
mode is disabled).
When viewing the module in configuration mode, either the heating or the cooling mode can
be seen at one time. The parameters at the top of the display are common to both modes and
have to be entered only once per OSS module.
The remaining parameters refer to the Heating mode, and typing M for ‘Medium selection’
will toggle the bottom half of the display between these two modes.
For either mode (Heat/Cool) the module may be set up for optimum start, optimum stop, both
or neither. The warm-up limit set to zero will disable optimum start and a cool down limit of
zero will disable optimum stop.
2) Inside address - this address should contain the value of the inside air temperature.
Typically it will be the address of the inside temperature sensor. If several inside
temperature sensors are fitted, a function (e.g. minimum) of these values may be used.
The address will be the function module destination address.
3) medium Address - a separate address must be specified for each of the modes, (i.e.
heating or cooling) required. If a measurement of the medium temperature is available,
then this should only be used if the medium is up to temperature at the start of the warm-
up period else set address to zero and use an estimate. In the case of the heating medium,
the medium address would normally be the flow temperature of, for example, hot water
feeding radiators. In the case of the cooling medium, the medium address would normally
be the supply air temperature of an air conditioning system. If the medium address is set
to zero, the initial value of medium temperature (set up as medium temperature in
configuration) will be used and not be updated.
If the medium address is set to zero, then the medium temperature estimate should be the
average flow temperature during warm-up.
The loss time constant will probably be between 5 hours for a very poorly insulated building and
30 hours for a very well insulated building. When adapted, it will tend to be shorter in winter than
in summer as the OSS adapts to seasonal variation. Loss time constant may be estimated as follows.
It may be estimated by using logs of the inside and outside temperature taken with no heating
or cooling applied. This is done in Figure 18.3 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.
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 in Figure 18.4 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.
The gain time constant will be shorter on a building which is well insulated and longer on a
poorly insulated building. The values will be in the approximate range from 5 hours (well
heated) to 50 hours (poorly heated).
The loss time constant is the same for heating and cooling, and is entered once for both modes.
However negative values are used as shown below:
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
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.
18.8 Outputs
The OSS module outputs are provided by seven bits that are set to 1 or 0 depending on the time
in relation to the OSS cycle. OSS module outputs are as follows:-
bit 0 = OTP OCCUPIED - Zone state during occupation - between the start of
occupation and the end of occupation.
bit 1 = OSS OCCUPIED - between optimum start time and optimum stop time (used for
switching OSS loops into occupied setpoint)
bit 2 = NON-OCCUPIED - between occupation stop time and optimum start time.
bit 3 = WARM-UP - between optimum start time and the start of occupation.
bit 5 = COOL-DOWN - between optimum stop time and the end of occupation time.
bit 6 = MODE - status 0 for heating OSS calculations and status 1 for cooling OSS
calculations. This bit shows the mode in which the OSS module has decided it is
operating.
These bits are connected as standard to all schedules allocated to this zone, but any of the bits
can be used where required in the strategy (e.g. to switch loop setpoints).
BIT
OTP OCC 0
OSS OCC 1
NOC 2
WU 3
OCC 4
CD 5
6
TIME
Figure 18.5 OSS Module Bit State Timing INDICATES BIT STATE 0
A heating system using boilers and radiators. Heating control is via cascaded loop as follows:-
outside address = 3
inside address = 1
medium address = 0 medium temp = 60
inside set point = 221
The building cools down at 1.2 deg C/hour when the inside temperature (analogue 1) is at 20
deg C and outside temperature (analogue 3) is at 5 deg C.
The medium address is set to 0 as the medium temperature varies throughout the warm up
period.
Heating:
The boiler provides constant flow temperature to the zone with a three-way valve controlling
air temperature.
outside address = 1
inside address = 5
Heating:
medium address = 0
medium temp = 60
inside setpoint = 223
start elevation = -2 deg C
stop elevation = -1 deg C
Note that estimates for gain time constant, loss time constant, and estimated medium
temperature will have to be given. The medium address is set to 0 as the medium temperature
varies throughout the warm up period.
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.
Cooling:
medium address = 0
medium temperature = 5 deg C
inside setpoint address = 226
start elevation = 0 deg C
stop elevation = 3 deg C
Because the loss coefficient is already entered, this is also used by the cooling mode, but a
separate cooling mode gain coefficient must be entered.
Note that in this example the true medium temperature is not available as a real analogue value
so that the medium temperature is entered as a fixed estimate of 5 deg C.
When electric heating is used, the rate of heat input to the building is not dependent on the inside
temperature but is fixed in that electric heaters are either ON giving maximum heat input or
OFF giving no heat input.
The best method to use when setting up the OSS module for electric heating is to set the medium
address to 0 and the medium temperature to a comparatively high value, i.e. 100 deg C. The
gain time constant can be estimated as described in section 18.6.
The OSS module can exist in one of the three states shown in configuration mode.
We can analyse these modes by starting in a zone non-occupied state with the OSS module
passive.
18.10.1 Non-occupied
The module will look to the next OTP start time, if none exists today, it looks for one tomorrow;
if none exists tomorrow it looks no further.
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 setpoint is non-zero and the inside temperature is greater than the cooling
target (i.e. cooling setpoint + cooling start elevation).
It will calculate the ‘warm-up’ time by measuring outside temperature, inside temperature, the
medium temperature at start of warmup (or estimate if medium address is zero), and using
yesterday’s adapted gain coefficient to calculate the warm-up time to the setpoint + start
elevation.
It will limit this with the warm up time limit and then the optimum start is the OTP start less
the warm up time.
The next estimated optimum start time and the last optimum stop time will be displayed.
18.10.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 Gain Coefficient. It will adapt by using:-
This adapts the values smoothly and holds some historical information i.e. the trend in weather
or seasonal variation.
The gain coefficient will not adapt after a period of 4 hours following start of warm up.
During the warm-up the optimum start time shown is the last optimum start and the optimum
stop is the last optimum stop.
18.10.3 Occupation
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 Cooldown
time accordingly. It performs this by measuring the inside temperature, the outside temperature,
and using yesterday’s adapted loss coefficient to calculate the cooldown time to occupied
setpoint + stop elevation. It will limit the cooldown time to the cool-down time limit.
At any time the optimum stop time is the latest of OTP time less Heating Cooldown time or
OTP less Cooling Cooldown time.
During the occupation phase the optimum start shown is the last optimum start and the
optimum stop is the last optimum stop as calculated above.
18.10.4 Cooldown
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 occupation.
The loss coefficient will use the same method of adaption as the Gain coefficient i.e. new
coefficient = 0.8 x old coefficient + 0.2 x new estimate.
During cooldown the optimum start time shown is the last optimum start and the optimum stop
is the last optimum stop.
This may occur if the Outside Air Temperature sensor or zone sensor has alarm bits set, or the
sensor is removed.
The heating/cooling mode setpoint address could manually be set to zero, and only OTP will
operate. The additional strategy below will freeze the sensor value during failure and stop OSS
adapting.
This circuit is known as an OSS clamp and it can also be used if an override such as a loop
manual override or a caretaker override overrides the OSS time action. In these cases, the
function module gate can be driven from the override bit.
If the override/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. 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.
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.
Now we want it to stay clamped until the end of the period. If we call our OSS clamp bit ‘H’,
then we want to clamp if H has been set and we are still in either period i.e.
Note: Medium temperature, Loss time constant and Gain time constant are all updated by the
OSS Module and only require setting to initial values on installation.
* These parameters must be entered for either heating mode and cooling mode or both (if
both modes are selected). If the setpoint address for a particular mode is set to zero, then
the mode is switched off.
19 PLOT (LOGGING)
The channel keeps a marker on its last sample and when the supervisor accesses the channel,
the values are sent from this marker forward, enabling the supervisor to construct a graph of
the values in chronological order.
Figure 19.1 Plot Channel rolling record
The normal log used for system monitoring is the 15 minute log, the tuning log is used for fast
moving systems or control loop tuning, and the monthly log for such functions as energy
targeting or degree days.
If the user wants to log the same sensor at different periods and get both graphs on the 921
supervisor, then he can allocate another internal sensor to source itself from the original sensor,
and log the internal sensor at the second sampling period.
Sensor 10 above is an internal sensor which is sourced from Sensor 1, i.e. it is not a real sensor,
and serves to duplicate the value at Sensor 1.
It is sometimes very useful to log parameters other than those of sensors, e.g. control outputs, valve
positions and counters. This can be achieved by passing their value to a sensor module which is only
used internally. Digital nodes can be monitored or logged by an internal digital sensor.
Initializing the logging takes the logging channels and sets them up to log the sensors starting
at number 1 and sets the sampling period to 15 minutes. Alternatively each channel can be set
up individually either in supervisor or configuration mode to a particular sensor and sampling
period.
Normally the controller strategy is designed so that the most likely sensors to be logged are in
the range of the logging channel numbers but there is the following problem say for a particular
controller:-
Thus there could easily be more sensors than logging channels so some sensors cannot be logged.
The normal practice is to initialize the logging channels and then individually set up those
which require a change of sensor or sampling period.
When re-synchronisation occurs the effective start time of the logging record is moved forward
or backward so that the current time is correct. This means that no logging data is lost, but the
original sample time is overwritten.
e.g. Say a 1 minute log has been running for several days and the time is now 14:00. The time
is to be re-synchronised to 14:30.
The original graph will run from 12:30 to 14:00 approximately. The new graph will run from
13:00 to 14:30 approximately. The graph's first sample time has been moved by 30 minutes
to correct the graph to current time.
1 It contains a record of the last twenty alarm state changes for the local user which may
obviate the need for a local supervisor or alarm printer.
2 If the alarm communications are faulty (e.g. network fault, supervisor missing etc.).
Then the alarms are stored in the buffer as they occur, and are transmitted from the buffer
when communications are restored along with the time and date of the alarm state
change.
If the alarm address (see address) is set to 0, then alarms are not transmitted, but are still stored
in the buffer.
If the alarm buffer fills up with alarms which are not acknowledged by the target supervisor
then it will not accept any more alarms. Transient alarms will then be lost. (This will not occur
if the alarm address is 0.)
The alarm history may be viewed using the configurationV option or Display Panel. The alarm
descriptions provided in the alarm history are also used for alarms sent in text form, see section
6.9. If alarms are sent to the supervisor in coded mode the alarm description given may differ
from the equivalent supervisor display.
The alarm description is displayed in the language configured for the Display Panel (see
Section 5.7).
21 SCHEDULE MODULE
The schedule module is used to generate an analogue variable which changes with occupation
state. It has five inputs that can be defined either as values or addresses (Constant or Source
respectively).
The schedule module is in effect 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. Two or more
of the source addresses may be the same.
2) Optimum Start/Stop (OSS). This type of schedule is controlled by the optimum start and
stop times calculated by the OSS module.
3) Fixed (ON). This type of schedule is not under time control. The schedule output
remains at the occupied level and can only be changed by a manual override. The fixed
type schedule is only ever implemented as a temporary measure to bring on plant
continuously that is normally controlled by a schedule.
The schedule will be in the non-occupied state if the time is between schedule stop time and
schedule start time, otherwise it will be in the occupied state.
The schedule OSS start and stop times are calculated as follows:
Non-Occupied state - When time is between Scheduled OTP stop and Scheduled OSS start
Warm-Up State - When time is between Scheduled OSS start and Scheduled OTP start
Occupied State - When time is between Scheduled OTP start and Scheduled OSS stop
Cooldown State - When time is between Scheduled OSS stop and Scheduled OTP stop
Note that the start and stop deviations may be either positive or negative. Negative deviations
enable scheduled times to be in advance of zone times.
21.4 Manual
If the manual select address is greater than 0,0 and this bit is set, then the schedule state will
be forced to manual and the output level will be set to be the same as the manual level.
A manual Address 0,0 505,7 address of digital that when set forces
this schedule to manual control. If set
to 0,0 manual control is disabled.
S either
analogue Source 1 255 address of analogue.
C or Constant
value 0 100 per cent.
either
S analogue Source 1 255 address of analogue
or
C Constant value 0 100 per cent
either
S analogue Source 1 255 address of analogue
or
C Constant value 0 100 per cent
either
S analogue Source 1 255 address of analogue
or
C Constant value 0 100 per cent
either
S analogue Source 1 255 address of analogue
or
C Constant value 0 100 per cent
22 SENSOR MODULE
The sensor module scales an analogue input reading into engineering units and checks the
value against alarm levels.
Analogue input signals are generated by a sensor; a physical device that converts a physical
property (e.g. temperature, pressure or humidity) into an electrical signal. The analogue
signals generated by transducers can be a current or voltage of any size. Before the analogue
signal can be read by the computer, it must be converted to a voltage with a range of 0 volts
to a maximum of 10 volts by a signal conditioning circuit and then converted from an analogue
signal to a digital signal acceptable to the computer by an analogue to digital convertor, at this
stage the signal can be read by the computer. The inputs accept a voltage in the range 0-10V,
or current in range (0-20mA). Trend standard sensors provide a signal of 4-20mA which is
converted to a voltage signal by the input resistor. (Note that IQ150 will only accept an input
range of -5 volts to +5 volts).
The input channels on some IQ's are universal inputs and are used by both sensor modules and
digital input modules. The ways in which these can be arranged is explained in section 22.6,
Universal Inputs. The actual hardware inputs may be linked in a number of ways to condition
the signals and this is explained in section 2.2.1
Each sensor module allows an offset to be 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.
1) Analogue Input
2) Internal Analogue
3) Digital Input
4) Internal Digital
This shows sensor 1 coming from analogue input 1 and having a destination of analogue node
1. Its sensor type is 1 (represented by the 1 below the line). The analogue input sensor cannot
be separated from its input node, nor its destination node so it is drawn thus:-
This shows that sensor 1 is internal being sourced from node 61. Note that it does not have a
type, and the I below the line signifies internal.
The sensor type for the analogue input mode is set up in a separate module. This contains the
information used for converting the input into engineering units and checking the value is
within its calibrated range. This set of sensor type modules then acts as a look up table for the
sensor modules to eliminate having to set up the same type parameters in every sensor module.
Note: In the configuration tables (22. 7) a real sensor (analogue input) has a type and offset.
The type is explained in section 26.
When changed to internal analogue the type and offset no longer apply but are replaced by
exponent and source. The exponent defines the number of decimal places before the decimal
point and this is used to define the arrangement of data for high and low alarms and logged data.
For a real analogue input the exponent is set up in the type module. A full explaination is given
in section 26.1.
Section 22.6 shows the various ways the sensor module could be set up in combination with
its associated digital module, for universal inputs.
If the sensor value falls outside the sensor limits, which form part of the sensor type parameters,
an Out-Of-Limits alarm is given. These limits should be the calibration limits of the sensor
and for the Trend sensors they would be the values of the parameter at 4mA and 20mA. In this
case, short circuited sensor wires can be detected by a current of greater than 20mA and an open
circuit sensor by a current of less than 4mA.
Additionally if the IQ cannot get a reading from the analogue to digital convertor due to over
range (input voltage outside 0v to 10v) then a Read alarm is raised. The alarm reporting
mechanism is explained in section 6.3 but some of the alarms will not be reported until the delay
is exceeded as below.
There is no delay associated with the clear alarm, so once the alarm condition has cleared it
will be reported immediately.
The time delay is in minutes but is accurate to 5 seconds. It is not possible to enter one alarm
state while the other state is timing out.
Note: A sensor alarm delay value other than zero will switch off sensor alarm hysteresis for
that alarm.
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.
degrees C
30
Sensor High alarm level
29.5 Hysteresis
10.5 Hysteresis
10 Sensor Low alarm level
Time
Hysteresis will always be applied as a fixed percentage of the difference between the high and
low alarm levels. Hysteresis is calculated as follows:-
On some supervisors it is possible to display the sensor module label alongside its value, on
others separate supervisor labels must be set up.
On controllers with Universal Inputs (e.g. IQ9x, IQ111, IQ131), the sensors which may be real
or internal are shown on the Display Panel Inputs Display and internal sensors (i.e. sensor
number greater than maximum input channel number) are shown on the Display Panel
Internals Display.
A controller which has separate sensor and digital inputs (e.g. IQ151) has separate Display
Panel displays for sensors and digital inputs.
The label can be used as an item attribute for text communications. This is explained for IC
Comms in Section 14 and more generally in Section 29. Special characters are as follows:
? * .
Generally speaking, for real Universal Input channels, the sensor module should be set up to
follow the type of input selected. This will then enable the Display Panel, Inputs and Internals
displays to show all Universal Inputs, but if the strategy requires, it may be necessary to source
the digital and sensor modules from different nodes. An exception would be if the digital inputs
were pulse inputs going to counters; in this case the input would not need to be monitored but
the sensor could be set to internal analogue mode and sourced from the counter cumulative
count output. Sensors whose number is greater than the number of input channels have to be
internal and again, generally, one should select each channel to be either digital or analogue
and use the sensor and digital input module in combination.
The digital input node is permanently connected to the input channel, and cannot be detached
from it either electrically or functionally.
The sensor module may, however, be set up for one of four sensor types of operation.
viz.
Types 2, 3 and 4 allow the sensor module to be detached from the analogue input channel by
the specification of its source address as other than the normally assigned input channel.
The supervisor/sensor display will show the analogue input value, but the digital input display
will be indeterminate. The digital input display should be edited to indicate a sensor input.
Logging would log the analogue input.
Now the sensor module will pick up the analogue value from the specified internal node,
process it and send it to its own node. This leaves the input channel free to be used as a digital
input by digital input n.
In this case the sensor display on the supervisor will show the internal value, and the digital
input display shows the input channel value ON (i.e. 1) or OFF (i.e. 0). Logging will log the
internal value.
The sensor module now picks up a value of 0.0 or 1.0 from its own input channel and sends
it to its own node.
The digital input module will also show the state of the input.
The alarm status attached to the analogue node n will have bit 5 set to 1, to indicate a digital
value, and bit 0 will show the state of the digital input alarm as detected by digital input n.
In this case, the supervisor sensor display will show 0.0 or 1.0 (this can be set to display 0 or
1 by removing the decimal point in supervisor edit) and the alarm state will also be indicated.
The digital display will show ON (i.e. 1) or OFF (i.e. 0). The sensor display label should be
edited to indicate a digital input.
Logging the sensor will now log the digital input value.
Although shown in this section for completeness, this configuration should not be used on a
real input channel as the sensor passes a digital status into the digital input node. It should only
be used on a sensor module which does not have an associated real input (i.e. sensor number
is greater than maximum channel number).
In this mode the sensor takes its value from the specified internal digital node, and sends itboth
to its own node and to the digital node corresponding to the internal digital input of the same
number as the sensor.
The alarm status attached to the analogue node n will now have bit 5 set to 1, to indicate a digital
value.
The sensor and digital displays are as above in section 22.5.4. Logging the sensor will now
log the internal digital input value.
A sensor module which does not have an associated real input channel (i.e. sensor number is
greater than maximum input channel input number) should only be used in one of two modes.
a) Internal Analogue
b) Internal Digital
It may be used to monitor a real digital input by setting the mode to internal digital and setting
the source address to the digital node corresponding to the digital input.
The configuration works in the same way as the corresponding configuration in section 22.6.4
except that the digital input module now always shows the value input to its node by the source
module.
-7 -0.000000032767 to +0.000000032767
-6 -0.00000032767 to +0.00000032767
-5 -0.0000032767 to +0.0000032767
-4 -0.000032767 to +0.000032767
-3 -0.00032767 to +0.00032767
-2 -0.0032767 to +0.0032767
-1 -0.032767 to +0.032767
0 -0.32767 to +0.32767
1 -3.2767 to +3.2767
2 -32.767 to +32.767
3 -327.67 to +327.67
4 -3276.7 to +3276.7
5 -32767 to +32767
6 -327670 to +327670
7 -3276700 to +3276700
Analogue Input
All Analogues
H High alarm see offset High alarm limit - When the sensor
value is above this limit a sensor high
alarms generated.
L Low alarm see offset Low alarm limit - when the sensor
value is below this limit a sensor
low alarm is generated.
23 SEQUENCE TABLE
The sequence table is used to specify the order in which modules are to be serviced. As
explained in 2.3.4, in order that the modules of the system may be serviced (updated with
information and provide outputs if required), each of the following module types must be
entered into a sequence table.
Sensor
Loop
Function
Driver
Schedule
Logic
Each module is 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. There are a defined
number of sequence table steps. The whole table is serviced in the fixed sequence table cycle time.
The number of sequence steps and the cycle time varies with IQ type.
On the strategy diagram, the module has a sequence table entry number shown by the side of
it in an oval shape. Previously this was represented by a diamond shape.
Sensor
Loop
Function
Driver
Schedule (pass through value)
Logic
Digital Inputs (for fast sequencing only)
In general terms, modules are entered in the order of information flow in the control strategy.
A typical example of where sequence table order is very important, is in duty/standby selection
where the status of plant device is required, before a decision to select is made.
Note that of the modules that require entry into the sequence tables 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 section 16.5); 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 than the sequence table cycle time;
inserting more than once alters the meaning of the integral time constant and hence the integral
term, however this can be accounted for, for fast acting plant (17.6).
For some controllers (IQ111, 131, 151, 131+, 151+) the sensor response may be improved by
the multiple entry technique. For others (IQ70's, 90's, 100's, 100+'s, 111+) the value is only
sampled once per cycle time, but on these controllers it is best to process the value as soon after
the sample as possible. The optimum sequence steps for the sensors depend on the timing of
the sequence steps relative to the sensor sampling times as shown on the table below:-
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 called
Multiplexing Nodes.
The above is a simple example to demonstrate the principle. Say we have five 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 5 logic modules we can use G1 five times by multiplexing the nodes
between the input and output modules.
Step
10 G2
11 G1
12 D1
13 G3
14 G1
15 D2
16 G4
17 G1
18 D3
etc.
This process saves four logic modules but, because the nodes 32,0 and 32,1 are multiplexed,
viewing them in configuration mode will show their 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 in a sub strategy.
The facility only applies to a maximum of eight digital input channels, the actual number and
their location varies with controller type, see Appendix 1.
It is inappropriate to use the fast sequencing facility to achieve a faster input frequency as it
does not increase frequency, only response to an infrequent input.
23.6.1 Implementation
The input which requires a rapid response is specified in the sequence table preceding the
sequence table steps containing the required response. In the event that a state change is
detected at the input, this sub-sequence will be implemented as soon as possible after the start
of the sequence table.
00 00 00 00 00 00 00
00 00 00 00 00 00 00
In this example (using an IQ131 with 148 sequence steps) a fast sequence has been added at
the end of the sequence table.
If the relevant digital input changes during the sequence table preceeding these steps, then the
sequence will be interrupted and jump to the fast sequence step for that digital input and
proceed through the fast sequence until a return is reached. The sequence will then proceed
from the next step after that from which it was interrupted.
00 00 00 00 00 00 00
00 00 00 00 00 00 00
00 0 0 0 0 0 0
00 000 000 000 000 000 000
Figure 23.4 Fast Sequence actioned during sequence table cycle
For example if the digital input occurs during step 50, then on completion of this step it will
jump to the start of the fast sequence at step 145 and then run through the fast sequence to step
148. It will then return to step 51 to resume its original sequence but it will not execute steps
145 to 148 again on this cycle instead it jumps from step 144 to step 1 on the next cycle.
Note the fast sequence merely jumps the queue, and will not be executed again that cycle. If
the same digital input occurs again during the same cycle it will be ignored until the start of
the next cycle.
For this reason the fast sequence should be as near to the end of the sequence table as possible,
so that it can be brought foward as far as possible for a fast initial response.
00 00 00 00 00 00 00 00 00
000000000
000000000
Figure 23.5 Bad Positioning of Fast Sequence
For example if the same fast sequence is instead placed between steps 51 to 54, and the digital
input change occurs between steps 1 and 50 then the fast sequence can be brought foward,
however once the sequence is executed normally, if the digital input change occurs after step
54 it will not cause the fast sequence to occur until the start of the next cycle.
23.6.2 Rules
b) Fast Sequence must start with a digital input number followed by modules and
terminated by a return.
c) Fast Sequence can only be actioned once per sequence table cycle, so place as near to the
end as possible.
d) If a number of simultaneous digital inputs occur which all require fast sequences, then
the fast sequences will occur in digital input order (i.e. lowest first).
When a fast sequence is represented on a strategy diagram, the digital input has a sequence step
shown, and the last module in the fast sequence has both its own sequence step and the return
sequence step. This is shown in figure 23.6 below:-
Sequence 144 I1
145 G1
146 G2
147 D1
148 R
e.g. L1 <CR>
24 SWITCHES
Switches enable access from the supervisor or Display Panel to the digital nodes. A switch
enables the node to be `switched' ON or OFF.
The function performed by any switch is determined by the strategy within the controller. The
switches allow digital nodes 18,0 onwards to be changed. A switch is represented on the
strategy as a variable digital node.
A switch has a user settable password level to prohibit it from being changed by an
unauthorised person on the Display Panel, by configuration mode, or by text communications.
This password level can be set up and changed in configuration mode.
The password level only limits the adjustment of the switch by the Display Panel or in
configuration mode. There are separate independent password levels which can be set up at
each supervisor.
The switch label can be used as an item attribute for text communications. This is explained
for IC Comms in 14.9 and more generally in Section 29.
25 TIME MODULE
Most IQ’s have a battery backed internal Real Time Clock (RTC); other IQ’s (IQ9x series)
have a software clock which is not battery backed (for details see Appendix 1).
These clocks keep track of the current time as a 24 hour clock, the day of the week, and the
date. The day of the week and the date are not related i.e. the IQ does not have the ability to
check if the day of the week corresponds to the date. The day of the week and the date are both
incremented at midnight.
For a battery backed RTC, if the mains fails, the clock is supplied by the battery, so the clock
continues to ‘tick’ away and when the mains supply is restored, the controller will take the
correct occupation state for the appropriate time and day of the week. If the clock is not battery
backed, then it will need synchronising on power up; this can be done automatically by a
Timekeeper at address 11 or a Timemaster.
a) By supervisor in supervisor mode [on some supervisor only i.e. 921, 945, 951: (94x
needs special user pages set up)].
c) By Display Panel.
d) By Timekeeper controller.
25.2 Timemaster
The Timemaster function is to maintain time and date synchronisation of all IQ controllers
and to effect seasonal time changes from a single source.
To qualify as a Timemaster the IQ controller must comply with the following requirements:-
b) have its time module change by value set to a value other than zero
The Timemaster will send a time and date update message to all devices on all Lans (except
auto-dialled Lans) at the following times:-
b) when it receives a request for time and date synchronisation from its local Lan
(only if at address 11, whereby it fulfills timekeeper functions as described below).
In this way the Timemaster can maintain the synchronisation of the entire system with a single
daily time and date update message at approximately 00:05 hours.
Summary.
Where a Timemaster is to be included into a system the following steps should be taken:
a) Set up only one IQ controller with a battery backed real time clock to be the Timemaster,
by configuring its time module change by value to a value other than zero. Remember
a Timemaster is necessary for each section of the system separated from other sections
by auto-dialled links.
b) Where a Timemaster is required but seasonal time changes are not observed. Set change
by value to be 1. Set start day to be 0 and end day to be 0.
c) Where a Lan is fitted with IQ90s, ensure a Timekeeper is established on the Lan (at
address 11). Also ensure that the Timekeeper’s time module change by value is set to
zero if time and date update messages from the Timemaster are to be implemented. If
there is more than one Lan ensure that each Lan has a timekeeper.
Note: On one Lan the Timekeeper and Timemaster may be the same IQ controller if its address
is set to 11, and the time module change by value is set to a value other than zero.
25.3 Timekeeper
The Timekeeper function is required on any Lan which contains controllers which do not
have battery backed RTC’s (i.e. IQ90's, not IQ90+'s), so they may be synchronised after
power failure.
To be a Timekeeper the controller must have:-
b) its local address set to 11. This is the local address accessed via the address module
in configuration mode. (Setting only the CNC address switch SW1 will be ineffective).
The timekeeper will send a time and date synchronisation message to all devices on its local
Lan only when it receives a request for time and date synchronisation from its local Lan.
IQs with non battery backed real time clocks expect to be synchronised between midnight and
00:10 hours each day: they also need synchronising after power up or soft restart. IQ
controllers with non battery backed real time clocks that do not receive either a synchronising
message or a Fail TimeKeeper Advice (FTKA) alarm send a request for time message to the
timekeeper (address 11).
The IQ controller originating a time request message will wait for a response. If either a
synchronisation message or FTKA alarm is received it will start normal operation otherwise
it will itself raise an FTKA alarm to all other controllers on the LAN, and a Fail TimeKeePer
(FTKP) alarm to the supervisor. The FTKA alarm stops other controllers from also sending
the FTKP alarm. After raising these alarms the controller will start normal activity. The time
between power up and commencing normal activity may be up to 5 minutes.
Note: FTKA and FKTP alarms will not be generated by any IQ controller with a battery backed
real time clock fitted with firmware versions 4.6 (or later).
LAN4 11
Timekeeper
11 LAN1 I/N LAN5 11
Timekeeper/Timemaster
LAN6 11
Timekeeper
In the above example the controller at address 11 on Lan 1 has its change by value non-zero
so it is a Timemaster, but because it has address 11 it is also a Timekeeper.
As a Timemaster it will synchronise all controllers on all Lan's at midnight (0:05 hours), when
it is synchronised etc, and as a Timekeeper it will repond to requests for synchronisation by
any IQ90's on its own Lan. It cannot however respond to requests for synchronisation from
IQ90's on other Lans since they are sent to address 11 on their own Lan.
Thus each of the other lans has a controller set to address 11 as a Timekeeper. This will
synchronise IQ90's when requested by them on its own Lan. These Timekeepers will also be
synchronised in turn by the Timemaster when it sends out a global global synchronisation
message.
a) The alarm supervisor will receive FTKP alarm at 00:10 hours each day from each Lan
without a timekeeper, unless this alarm is globally inhibited by setting byte 499 bit 1.
b) If the supervisor can synchronise time and date at 00:05 hours each day (e.g. on a report)
this can alleviate some of the problems. The supervisor cannot, however respond to
power up, or soft restart, time and date synchronisation requests.
0 = no change
1 = 1 hour
2 = 2 hours
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.
Thus if the change is set to 1 hour it will occur at 2 am, but if the change is 2 hours it will occur
at 3 am.
Note: Setting the time module change by value to be other than zero results in the IQ controller
becoming the system Timemaster. It also results in the IQ controller rejecting time and date
update messages from both timekeeper or timemaster.
N miNutes 0 59
M Month 1 12
Y Year 0 99
G chanGe by * 0 2 0 = no change
1 = 1 hour
2 = 2 hours
O start mOnth 1 12
T end monTh 1 12
Note: To make changes to any of the values entered on the time page using either configuration
mode or a display panel , a password or PIN of level 50 or higher will be required.
Note: If Change by is set to a value other than zero it establishes the IQ controller as a
Timemaster. Change by in association with start date and end date allows the user to establish
automatic Winter/Summer time changes. The time will have the change added to it on the start
date and have the change subtracted from it on the end date. The time it occurs is equal to
the change by amount +1 hour.
26 SENSOR TYPES
When a sensor input is converted from its electrical voltage or current level to its value in
engineering units (e.g. deg C for temperature), it is firstly converted to a number by the
analogue to digital converter. This number is then rescaled by the appropriate sensor module.
The actual value in engineering units which corresponds to each voltage or current value
depends on the type of sensor.
Each controller generally uses a limited number of sensor types. A sensor type may be used
many times in the same controller. To avoid defining the sensor type each time it is used, the
sensor type information is defined once only (in the sensor type module) and referenced by each
individual sensor of that type (ie sensor module type).
For each sensor type, the exponent has to be set up first of all:-
26.1 Exponent
The exponent value defines the number of leading digits before the decimal point that the
sensor module needs to carry the scaled analogue value. It is used for the arrangement of high
and low alarm limits, offset, and logged data. It can be in the range -7 to +7 and the range of
values that can be displayed at any exponent value ‘n’ is -0.32767 x 10n to + 0.32767 x 10n..
With an exponent value of -2, the scaling range will be:- 0.32767 x 10-2 to + 0.32767 x10-2
The complete ranges are shown in the table in Section 22.5. The exponent is used to set the
ranges over which a particular sensor operates.
The exponent (scaling range) should be chosen so that the Bottom of Range and Top of Range
values (see below) are within the scaling range of the exponent selected.
For Example:
A sensor is used for measuring pressure from 0 to 20 psi and has 4 to 20 mA output. The sensor
characteristics define a Top of Range of +20 psi and a Bottom of Range of -30. An exponent
of 2 is used, giving a scaling range of -32.767 to +32.767.
Another sensor may be used for measuring temperature from -10 deg C to +110 deg C and has
4 to 20 mA output. The sensor characteristics define a Top of Range of 110 deg C and a Bottom
of Range of -190 deg C. An exponent of 3 is used, giving a scaling range of -327.67 to +327.67.
The values specified for the Top and Bottom of range are different for an input channel
linked for voltage and an input channel linked for current.
If the channel is linked for current (I), then the Top and Bottom of range values are the
sensor values at +20 mA and -20 mA respectively independent of controller type.
If the channel is linked for voltage (V), then the Top and Bottom of range values are the
sensor value at plus and minus a prescribed voltage level respectively. This level is either
10 V or 5 V and depends on controller type as defined in Appendix 1.
This specifies the upper calibration limit of the sensor and is the upper level at which an
Outside Limits alarm is produced. This is normally set to the value at 20 mA for a Trend
4 to 20 mA sensor. If the measured value goes above this value, an Outside Limits alarm
is produced.
This specifies the lower calibration limit of the sensor and is the lower level at which an
Outside Limits alarm is produced. This is normally set to the sensor value at 4mA for a
Trend 4 to 20 mA sensor.
This form of scaling is used for thermistor input channels or any input requiring linearisation.
For an example graph as shown below, first enter the working range; T is the Top of Range and
B is the Bottom of Range, (both in engineering units).
For the above example T = 90, B = 10. We then divide the range into 4 equal engineering unit
ranges ( ).
i.e. = T-B
4
for this example = 90-10 = 20 deg C
4
The voltages corresponding to the five points so defined i.e. T,T - , T-2 , B+ , B, are then
entered.
In this example the five temperatures are 90, 70, 50, 30, 10, the corresponding voltages are
entered as follows:-
The outside limits alarm will then be given at T+ and B- (i.e. above 110 deg C and below
-10 deg C), or if the input level goes below 0.5 V. This lower limit of 0.5 V is to check for short
circuit thermistors.
For Trend thermistors, there are thermistor tables available for F, G, H, I, & J dependent on
temperature range and IQ type. There are three classes of IQ type: 10 V, LK/D (5V), and 2.55 V.
The relationship between IQ type and its thermistor table class is given in Appendix 1. LK/D is
reserved for those controllers which do not have thermistor linking available on the input channel.
Normally for thermistors, the resistance/temperature characteristic is known, and the voltage/
temperature characteristic would have to be calculated from corresponding resistance values
using the equations:
1
for Vref = 5 (LK/D), V = 5
( R +R4,700 ) 1
1
for Vref = 2.55, V = 2.55
( R +R10,000) 1
1
Whether Vref is a value of 10, 5, or 2.55 is dependent on controller type as defined in Appendix
1. R1 is the thermistor/resistance value at a given temperature.
e.g. Using a thermistor with the temperature/resistance characteristic given below. Calculate
the F, G, H, I, J points for a range of -10 °C to 110 °C for an IQ100.
Temperature °C Resistance Ω
-30 177000
-25 130400
-20 97120
-15 72980
-10 55340
-5 42340
0 32660
5 25400
10 19900
15 15710
20 12490
25 10000 (This table is actually that for Trend sensors).
30 8058
35 6532
40 5326
45 4368
50 3602
55 2986
60 2488
65 2082
70 1751
75 1480
80 1256
85 1071
90 916.4
95 787.4
100 679.2
105 588.0
110 510.8
From table corresponding resistance are: 510.8, 1256, 3602, 12490, 55340
Using the equation for Vref = 10v, the voltages can be calculated
i.e. V = 10
( R +R110,000 )
1
V = 10 55340
(55340 + 10,000 ) = 8.469 ~ 8.47
If a potentiometer is used, and the input is linked for a thermistor it can be treated in a similar
way. To eliminate the occurence of an Outside Limits alarm as the voltage input goes below
0.5 V (used to detect thermistor short circuits), it is usual to have a series resistor e.g. for 10
kΩ resistor a series resistor of 1 kΩ is used.
10 kΩ IN
IQ
1 kΩ
O
e.g Using a 10 kΩ linear potentiometer, with a required trim of ±4 (i.e. T = +4, B = -4) with
a series resistor of 1 kΩ on an IQ111+ .
Then = T-B = 2
4
The corresponding variation in resistance is 10 = 2.5 kΩ
4
The five points are 11, 8.5, 6, 3.5 and 1 kΩ for J, I, H G, F
4 x
Trim J
3
2 I
x
1
H
x
0 8.5
1 3.5 6 11
-1 Res (kΩ)
-2 G
x
-3
-4
F
x
V = 10 (10001000
+ 10000
) = 0.91 V
G = 2.59 V
H = 3.75 V
I = 4.59 V
J = 5.24 V
Normally the sensor is defined over its working range (i.e. its working limits are known). In
order to scale a sensor the values at the Top and Bottom of range are required. These values
(as described above) are at ±20 mA respectively for current inputs and at ± a prescribed voltage
level dependent on the controller type (see Appendix 1) for voltage inputs.
These Top and Bottom of range of values may be calculated from the working limits as follows:-
Current Output
For a current output sensor, T and B are the values of the measured value with sensor
output +20 mA and -20 mA respectively. For example using a sensor with the characteristic
graph below then U is the measured value at x2 mA, and L is the measure value at x1 mA.
y
T
U
L
-20 x1 x2 20 x (mA)
m = U-L
x2-x1
Using the equation y = mx+c and solve for c at the sensor lower limit y=L and x=x1
c = L - x1 m
B=20m+c
T=20m+c
Page 26 - 6 IQ Configuration Manual Issue 6/A 1/6/93
IQ CONFIGURATION MANUAL SENSOR TYPE
example:
m=U-L = 80-0 = 80
x2-x1 20-4 16
c=L-x1m=0-4x80=-20
16
B=-20m+c=-20x80-20=-120 °C
16
T=20m+c=20x80-20=+80 °C
16
Voltage Output
For a voltage output sensor, T and B are the values of the measured variable when the sensor output
is +10V (or 5V) and -10V (or -5V) respectively. The 10V or 5V is as shown in the table below.
Table of voltages (V, -V) for Top (T) and Bottom (B) of range. y
IQ70's, IQ90's, U
IQ151+, IQ111, IQ131,
IQ100's, IQ111+,
IQ151
IQ131+ L
T +10V +5V
B -10V -5V
-V x1 x2 v x(volts)
Using a sensor with the graph above, then U is the measured value at x2 volts and L is the
measured value at x1 volts.
Using the equation y=mx+c and solve for c at the sensor lower limit
B=-Vm+c
T=Vm+c
example.
For a sensor with a 0 to 10 Vdc output corresponding to a measured range of 0 to 250 Pa, fitted
to an IQ111+ (i.e. V=10). Hence U=250, L=0, x2=10, x1=0, V=10.
m = U-L = 250-0 = 25
x2-x1 10-0
c = L-x1m = 0-0x25 = 0
1. Linear Scaling
2. Log Scaling
3. Linearise
27 USER - PIN
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.
When a PIN is required or requested the PIN level determines whether or not a change will be
accepted, a higher level allowing access to more sensitive data.
27.2.1 Configuration
A PIN of level 90 or above will be required for the controller to update the data file when an
X is entered (see Section 3.3), except for the Time module which requires level 50. PIN level
99 is required to view and change the PIN levels. The PIN will be cancelled on exiting the
configuration mode or time out (automatically self-cancelled) after 15 minutes.
The protection does not operate unless at least one User PIN has been set up. It is recommended
that at least one PIN of level 90 or greater is always available in the controller, to prevent
unauthorised access and accidental lockout.
If you exit and there is no Pin level >50 present, you are prompted
WARNING SYSTEM WILL LOCK YOU OUT
Continue ? (Y/N)
If you exit and there is no PIN level > 89, but a PIN level >49 is present you are prompted
WARNING SYSTEM WILL LOCK YOU OUT
To all bar the Time page
Continue ? (Y/N)
Enter, Yes or No as appropriate.
When using the Display Panel, the following items have fixed PIN levels:
Knobs and switches can be edited in configuration mode to have any level between 0 and 99.
If the item has level 0 it is unprotected and can be altered without entering a PIN.
Changing a protected item is explained in the Display Panel Manual. The item cannot be
changed until a valid PIN is entered. Once the user has entered a valid PIN, items with a lower
level may also be accessed. The PIN will time out 2 minutes after the last key press.
The user PIN is also used in IC Comms, see Section 14.11. In the initiating controller the User
1 PIN is sent with a global to or data to (bit only) message.
The same PIN must also be set up in any receiving controller as follows:-
This rule also applies when the controller receives a text communication message from a
supervisor which is making changes to controller values. In the case of the 822 the password
can be entered by the user and then automatically sent at the front of any text communications
message and in any upload or download message.
27.2.4 Upload/Download
The upload/download of the data file over the network is also PIN protected. The user must
either be logged on or log on with an appropriate password level or the upload/download
message may incorporate the appropriate password (e.g 822). The password level must be
equal to or greater than:
In both the above cases a PIN is not required if the receiving controller has no PIN set up.
Bit 0 1 2 3 4 5 6 7
Byte 497 U1 U2 U3 U4 U5 U6 DEF
The bit will be 1 when that user is logged on and will only be cleared by strategy or maybe
cleared by the user in configuration mode.
The user can then contact Trend technical support to obtain the default PIN for that date. The
PIN so obtained is approximate to ±5, so that each PIN in the range ±5 must be tried till one
works. To try a PIN, a change is made e.g. TX (Timer module, eXit) and the PIN entered. Once
the PIN is accepted, a User PIN (say User 2) should be set up with a level of 99.
3) On some controllers there is a battery link and this may not be connected correctly.
4) On IQ90 series controllers a resistor must be inserted to ensure the battery is connected.
First the fault (if any) must be corrected. Then the easiest way to restore the controller to
working order is to download the strategy over the local supervisor connection. This can be
done without knowledge of the password or the address.
To download the strategy over the network, the address and password must both be known.
On an IQ111, since the address is set in RAM, this may be corrupted, and the only way it can
be checked is via a display panel or local supervisor connection. Once the address is known
the controller may be communicated with over the network, and the default password found
as described above. The download may then be performed.
28 ZONE TIME
The IQ's have a number of independent zone time modules (Zones) that can be used to switch
plant and control loops ON or OFF at times entered by the user:- these times being known as
Occupation Time Profile (OTP). Each of the time zones can be used with its associated
Optimum Start Stop (OSS) module and attached to schedule modules to provide occupation
dependent inputs to control strategies. Zone 0 is used to define special day types 1-5 which are
used in the holiday calendar for the Display Panel.
At midnight each day, the preceding day's occupation times are copied from the standard week
to the current week. Thus after seven days the current week equals the standard week.
Therefore, the current week can be set up for the week ahead (and may contain special times,
e.g. holidays), but by the end of this week (if not set up with further special times), it will have
been restored to the standard week’s times.
The controller calendar may also be used to setup the time zones see Section 9.
The zone times may be set up in supervisor mode; the supervisors have special calendars for
the year ahead that can download times. The zone times can also be set up in configuration
mode and by the Display Panel. The occupation periods must be in sequence and must not
overlap. If an occupation period is to be ignored, then the start and stop times are made equal.
If one’s day period ends at 24:00 and the next day starts at 0:00 then there is uninterrupted
occupation through midnight.
The current week is defined by day numbers 1 to 7 where 1 is Monday and 7 is Sunday. The
standard week is defined by day numbers 8 to 14 where 8 is Monday and 14 is Sunday. All
times are specified in the 24 hour clock in hours and minutes.
If the standard week is changed on the Display Panel (identified as Every week), then the
change is also made to the current week, (identified as Next week).
The zone label may be used as a device attribute in text comms as explained in section 29.3.
In this use the label may contain special characters
& | * ? .
The IQ70 has only one time zone, zone 1, which controls byte 13. The IQ70 zone inhibit stops
the IQ70 OSS module updating the zone byte, enabling it to be updated from elsewhere. This
would normally be done by a team leader which can use IC Comms to send out the zone byte
to a team of IQ70's (see section 29.5).
ZONE 0
special day 1 5 special day number
ZONE 1 - 5
day no. 1 7 for the current week Mon = 1 Sun = 7
E start time
1st period 00:00 24:00 hours / minutes
F stop time
1st period 00:00 24:00 “ “
G start time
2nd period 00:00 24:00 “ “
H stop time
2nd period 00:00 24:00 “ “
I start time
3rd period 00:00 24:00 “ “
J stop time
3rd period 00:00 24:00 “ “
Notes:
1. Arranges start/stop times in order so that when an early start/stop time is entered after
a late start/stop they are automatically re-arranged.
2. If the start/stop times are made equal then the times are ignored.
4. The copy facility will copy from one day to a list of days within the zone, not from one
zone to another.
29 TEXT COMMUNICATIONS
Note: Sections 29.1 to 29.8 give an introduction to attribute addressing and its relevance to
building management systems Section 29.9 onwards give details of text communications
syntax.
- allows immediate access to plain language data in response to plain language requests.
If we take the simple analogy of a railway with 10 stations, we may attach to each station one
or more station attributes relating to the services available. See Figure 29.1.
A message to all Express Parcels addressing attributes may be used to advise a related price
increase, and will be delivered to four destinations. (Leicester, Manchester, Winchester and
Birmingham).
By using a combination of station attributes ie. Travel Bureau OR Information Centre, the
message will be delivered to five destinations (Leicester, Manchester, Harwich, Winchester
and Birmingham); similarly Travel Bureau AND Information Centre will result in delivery
to three destinations (Manchester, Winchester and Birmingham).
A message using the special wildcard character *, e.g. *Parcels will result in the information
being delivered to both Express Parcels and Parcels addressing attributes, a total of ten
destinations (all stations).
Using attribute addressing it is possible to despatch information only to those destinations that
require it.
The power of attribute addressing is further enhanced by another level of selection. This is used
to select a class or type of data. Within the controller, the data available is divided into items,
so this selection is by item attribute.
This can be done in two ways i.e. by item identifier or item label.
item identifier This is the traditional method of selection and the normal identifiers are used
(e.g. S1 = sensor 1, L2 = loop2).
item label This alternative method uses a text attribute by selecting the item by its label.
In this case, wildcards (e.g. *) can be used.
Thus the request for *Space Temperature will select all items which have labels ending in
Space Temperature. In this way all the space temperatures in a building can be obtained.
Where string matching is used attempts are made to match the message initiator’s required
string against the attribute strings of the controller being communicated with. Computers and
micro-processors only recognise exact match conditions, and a near miss is considered to be
no match at all.
In addition to the simple matching of two text strings, special characters known aswildcards enable
the user to indicate that a pure match is not required, but some substitute characters are acceptable.
? is a wildcard character that can be included in attributes to allow a single character that
might match that position in initiators attributes.
. is a special character that can be included in an attribute or item label. Its special effects
only operate in IC Comms when the label is automatically included as an attribute in a
text message the text beyond the first fullstop is ignored and the full stop is replaced by
a wildcard *.
& (ampersand) is a special character. When placed between two attributes it indicates that
the message may only be delivered if the destination has both attributes.
| (pipe) is a special character. When placed between two attributes it indicates that the
message may only be delivered if the destination has one or other, or both of the
attributes.
These special characters provide great flexibility in device attribute or item attribute matching.
In the case of item attribute matching, where the item labels are:-
An either/or matching condition may be implied by the inclusion of a ‘|’ character between the
attributes. Eg. Red | Blue will only be delivered if the destination has one or other attribute
(or both).
The combined use of ‘&’ and ‘|’ in the same device attribute or item attribute is allowed.
Consequently Red | Blue & Green will result in the ‘|’ condition being observed and the ‘&’
condition being tested only if the first test passed correctly. It is recommended that only one
condition is used for clarity.
The maximum cooling demand of the team members could then be used by the team leader
to control the Air Handler. The task of team leader is to co-ordinate the collection and collation
of data. In this way duplication of effort may be avoided.
A single controller may be both team leader of one team and a team member of another. The
Air Handler unit controller may also be a team member for boiler and chiller plants, supplying
data to those plant controllers along with other Air Handler unit controllers to ensure that total
demand for all Air Handlers is met.
In figure 29.5 for simplicity all members of the team are situated on the same communications
network, however, a team may be spread around a multi-network system. It can be seen that
three teams exist, white black and grey teams. Device 6 is leader of the black team whilst also
being a member of both white and grey teams.
Splitting the system into teams simplifies the organisation of IC Comms so that information
required by the strategy can be exchanged between the relevant controllers.
The controller attributes relating to physical location, face of building and plant association
are unlikely to change and could remain fixed for the lifetime of the system, but those relating
to the occupation or tenant under whose control the controller comes may change at intervals
throughout the system lifetime.
To provide adequate attribute addressing the engineer should systematically sub-divide the
proposed system into areas based on the following criteria:-
common function
common occupier
common responsibility
common plant association
common environmental control
building geography
Consider figure 29.6. Two small commercial buildings are named Newbuilding 1 and
Newbuilding 2. For the purposes of this example it is assumed that they have identical floor
plans, HVAC plant and numbers of floors.
29.7.1 Identifier
Each networked controller must be set up to have a unique identifier and may have a maximum
of six attributes.
Let us first consider the long term requirements for controller identification.
Bearing these requirements in mind, each controller identity may be formed as follows:-
1FL3 C6 IQxxx
Using sub-sections of the identity e.g. *IQ91* enables the system user to obtain a count of the
IQ91 controllers connected to the system. The count being managed by summing of analogue
node 51 (=1) in all controllers.
The identifier used in this example is ideal for a commercial building having many floors and
a similar floor plan for each. A similar type of identifier may be used for a site having many
buildings with few floors, where the identifier emphasis is on the easy recognition of the
building rather than the floor of a building. Thus for a hospital site with many small buildings:-
Where the number of the controller indicates the floor of the building on which it is situated;
e.g. controllers 20 - 29 are on the ground floor, and controllers 30 - 39 are on the first floor etc.
29.7.2 Attributes
iDentifier 1FL3 L14 IQ92 iDentifier 1FL3 H12 IQ91 iDentifier 1FL3 H13 IQ92 iDentifier 1FL3 B14 IQ91
atrib2 (F) XYZ Co Ltd atrib2 (F) Control Co atrib2 (F) XYZ Co Ltd atrib2 (F) XYZ Co Ltd
atrib3 (G) AHU6 atrib3 (G) AHU8 atrib3 (G) AHU6 atrib3 (G) AHU7
atrib4 (H) atrib4 (H) atrib4 (H) atrib4 (H)
atrib5 (I)Office atrib5 (I)Services atrib5 (I)Office atrib5 (I)Office
atrib6 (J) P1SW atrib6 (J) atrib6 (J) P2SX atrib6 (J) P1SE
atrib7 (K) atrib7 (K) atrib7 (K) atrib7 (K)
Each IQ controller has a unique identity (identifier) and a unique communication node
attribute derived from address module local lan and local address data. IQ controller generated
responses to global text communications include the communications node address and the
identity in the reply message.
where L is followed by the LAN number and O by the node address and the identity. Thus
allowing easy identification of the IQ controller originating the reply, together with the
necessary addressing attribute should follow up communications be required.
The attributes used in this example are to show the power of attribute addressing. There is no
requirement to follow the sequence used here. However, to ensure a standard approach it is
recommended that Attribute 2 is always the Tenant attribute and so on.
Returning to examples Newbuilding 1 and 2 the attributes 2 to 7 may be used as shown on the
following page.
This addressing attribute may be the name of the tenant or company under whose control the
controller is placed.
Let us assume that three companies each have partial control in relation to Newbuildings 1 and
2.
ABC Co Ltd occupy Newbuilding 1 floors 1 and 2
XYZ Co Ltd occupy Newbuilding 1 floors 3 and 4 and Newbuilding 2 all floors
Control Co. are responsible for the control of and common services to both occupants on
behalf of the landlord.
Thus each controllers Attribute 2 will be either ABC Co Ltd, XYZ Co Ltd or Control Co
dependent on who is to supervise it. See figure 29.9.
Example 1.
Thus to change the setpoint of the area controlled by XYZ Co Ltd. The message will be formed
using:-
Example 2.
Should a tenant change, i.e. Newbuilding 1 floor 3 changes from ‘XYZ Co Ltd’ to ‘ABC Co
Ltd’ a combination of attribute addresses (Floor 3 and XYZ Co Ltd) will allow the system
Supervisor to change the tenants name for the affected controllers with a single message.
The key features of the message to achieve such a change would be:-
Device Attributes = Floor 3 & XYZ Co Ltd
Item Attribute = /R to select the address page
change value F = “ABC Co Ltd” would change XYZ Co Ltd to
become ABC Co Ltd (where F is used to specify
attribute 2)
reply format = (F,F=ABC Co Ltd,F)
providing a listing of all those controllers whose tenant attribute has been changed.
This device attribute may be used to define the plant to which the controller is linked. The
requirement to do this is demanded by the need for the plant to obtain and react to system data,
rather than the need for system interrogation by the human system controller.
Figure 29.10 shows that regardless of the physical arrangement of the communications LAN
used to cover each floor of the building, the plant may well be divided into two AHUs and their
associated controllers per floor. In order for essential information to be transferred between
the AHU and its associated VAV controllers, the attribute AHU1 should be applied to one
physical arrangement and AHU2 to the other. By use of the plant device attribute correct inter-
communications are assured.
For example AHU1 controller may distribute its supply air temperature to all of the VAV
controllers which it supplies.
This could be used for lighting circuit control, smoke control group, MD priority group etc.
This device attribute may be used to establish an occupation time zone for areas of common
occupation pattern.
Given that the use of the building or buildings requires a number of different heating and
lighting occupation time profiles the simplest method of achieving this is by the use of a time
zone attribute.
For example Newbuildings 1 and 2 may require the following occupation time zones.
For example Service areas may require heating and lighting for the longest period on normal
work days. Offices may have occupation time profiles of 0830 to 1800, whereas the Restaurant
is occupied from 1200 to 1430 , and the Kitchen time profile extends from 0730 to 1500.
To utilise the Optimum Start Stop facility in each team leader controller the OSS output must
be distributed to all controllers that require it as a part of their strategy. Where the team leader
controller is being used to output OSS, it has by default the capability of supporting a number
of time zones, each of which will have a label. The zone label will be used as the device
attribute whenever OSS data is required to be output.
This device attribute may be used to provide vertical zones through each building for the
control of common functions.
It may be that the key words to be used in this attribute are perimeter, north, south, east and
west. Because an controller may be positioned at the corner of the building, it could be that
its attributes reflect this by including perimeter, north and west.
The main function of this attribute may be to control the lighting for the purposes of energy
saving during periods of bright sunlight. Given that a compass direction may be introduced
as a qualifier, the dark and light sides of the building may be controlled independently.
The following example shows how to include the multiple attributes required within a single
structured attribute.
Therefore the attribute P2XE, will be delivered to all controllers controlling lights within 3-
6 metres of a window on the eastern face of the building. Similarly multiple attributes P2XE
& ??N? will be delivered to all controllers controlling lights within 3-6 metres of a window
on the north east corner of the building. See figures 29.17 and 29.18.
Figure 29.17 Attribute 6 - North OR West Figure 29.18 Attribute 6 - North AND West
29.7.8 Attribute 7
This device attribute could be used wherever the controller is originating Inter-Controller
communications messages for the purposes of broadcasting data or obtaining selected data
from other controllers.
A typical example would be the attribute ‘*’, which would allow the controller to address
messages to each and every controller.
Attribute ‘1FL3*’, would allow the controller to address messages to all controllers on Floor
3 of building 1.
Attribute ‘1FL3*&AHU1’, would allow the controller to address messages to all controllers
on Floor 3 of building 1, AND having an association with AHU1.
Attribute ‘1FL3*&AHU?’, would allow the controller to address messages to all controllers
on Floor 3 of building 1, AND having an association with AHU1 or 2.
Note: Although the message structure defined above is explicit regarding user entered data, the
tool used to enter the data will add information. The information added will provide the correct
characters to define the message start and end, and the message header (which defines the
message type). Without these additions the message will be unacceptable to the communications
network.
All items of one type may be selected by using the item type identifier i.e the normal
configuration mode reference for that item.
A text message changing knobs and switches node values must include a password of level
equal to or greater than the level set up in the relevant knob or switch module. Knob or switch
labels, PIN levels and ranges are protected by the levels described in the paragraph above.
More than one item parameter may be obtained with a single message.
Before text coms can be used to change system parameters, the appropriate password must be
set up. This is only needed if the message will change the device datafile and if the device has
a password set up. Controllers without user PINs set up can be changed without a password.
For a password to be valid it must exactly match the PIN in the controller. It is entered into the
822+/Toolbox or supervisor and automatically attached to the front of any text coms message.
When required, the level of the matching PIN in the controller must be high enough to enable
the change :
For changes to knob or switch settings the minimum level is set in the knob or switch
module
For controllers addressed by a specific node address, minimum level is 95
For controllers addressed globally (node address=0), minimum level is 99
System parameters can be changed by equating the parameter to the new value in the data part
of the message.
e.g. S1(H=25) - sets the sensor 1 high alarm level to 25
This will only be accepted if the new value is within the configuration mode range, and the
password is acceptable (see above).
Labels can be set up, but the text must be included in quotes
e.g. S1($="Space Sensor") - sets the label of sensor 1 to Space Sensor
It is useful to check the change by monitoring the parameter, changing it, and then monitoring it again.
e.g. S1($,$="Space Sensor",$) - will fetch the label, change it and the fetch the changed
label, thus confirming the change.
Page 29 - 18 IQ Configuration Manual Issue 6/A 1/6/93
IQ CONFIGURATION MANUAL TEXT COMMUNICATIONS
Restrictions:
1 Function modules inputs E and F cannot be changed, by specifying S for source and C
for constant in front of the node address or value respectively. e.g. E=S240 sets E as
source from node 240.
2 Must set sequence table type by number e.g. Q1(Y=2)
29.12 Conditionals
A conditional statement may be added optionally after the item selection to limit the number
of replies presented to the system operator.
e.g. S{V>19}(V) - gives values of all sensors with values greater than 19.
The normal MSDOS type wild card ?, may be used in a text or bit string to select any single
character (but there must be a single character). The ? may be used to select items according
to their alarm states
e.g. S{M=OO??}(V) - selects only those sensors without Read or Outside Limit
alarms.
The two operators & (and), | (or), may be used within the conditional statement to combine
conditionals.
e.g. S{V>25.0|V<19.0}(V) - selects only those sensors whose values are outside
the range 19 to 25
e.g. S{V<25.0&V>19.0}(V) - selects only those sensors whose values are within the
range 19 to 25
Restrictions:
1 Not recommended to use a conditional to select on label, because the label must be
padded to full length. Use item attribute instead - see later.
2 Must search sequence table type by letter.
e.g. Q{Y = F & N = 1} (*)
3 When selecting a parameter which is a byte, bit value using a conditional, the absolute
bit address is returned.
e.g. G{Y>0} (*)
gives G1 1 330 331 0 0 E F 168
whereas G1(*)
gives G1 1 41.2 41.3 0.0 0.0 E F 21.0
i.e. 330 = 41 x 8 + 2
Message Function
29.14 Attributes
An attribute is generally taken to be a quality or characteristic assigned to an item. In the case
of text communications its meaning is restricted to a label or identifier of a device or item.
The device attribute can define which controller or group of controllers are being communicated
with. Each controller has 7 device attributes plus its communication node attribute. The 7 device
attributes consist of the controller identifier and attributes 2 to7 as set up in the address module.
They are all text labels, but the identifier is up to 15 characters and the other attributes are up
to 10 characters long. The communications node attribute is made up of the lan number and
the outstation node address as seen in the address module. It is of the form:
As shown in the basic message structure, the device attribute is put in the front of the text
message, separated by a / or \. To be a valid controller, its attributes must match those of the
message. The match must be exact including spaces, and is case-dependent.
e.g. NORTH/S1(V) - requests the value of sensor 1 from all controllers who have any
one of their attributes set to NORTH, north would not match. Any
controller without a match will not reply.
The wildcards * and ? can also be used in an attribute to access a group of controllers.
* signifies any set of characters of any length (including null length)
? signifies any single character.
e.g. N*/S1(V) - will ask for value of sensor 1 from all controllers with any
attribute beginning with N.
e.g L6O2*/S1(V) - selects the value of sensor 1 from any controller in the network
address range 20 to 29 on lan 6.
Device attributes can be combined to produce a logical device attribute by using & and |
characters.
e.g. AHU1&AHU2/S1(V) - controllers which have both AHU1 and AHU2 attributes
e.g. AHU1|AHU2/S1(V) - controllers which have either AHU1 or AHU2 attributes
The device attribute must be more than 1 character or this may be misinterpreted.
Item selection is by item attribute and its purpose is to find a specific item by its label or absolute
reference, either to modify the associated value, copy the value to another location, or view
the value for the purposes of evaluating system performance.
In addition to the item identifier, and the item type identifier previously explained, the item
label may also be used to select an item for drivers, digital inputs, knobs, sensors and switches
only. When the label is used it behaves in a similar way to the device attribute with the selection
being made by matching labels, and the wildcards * and ? may be used.
e.g. WEST/OCC SP*(V) - the value of any item with label beginning with OCC
SP from any controller with attribute WEST
e.g. SPACE TEMPERATURE(V) - the value of any item with label SPACE
TEMPERATURE from any controller
When a selection is made by label, a search is made through the following module types :-
drivers, digital inputs, knobs, sensors, and switches. Only those modules who can accept the
data part will respond.
e.g. MANUAL SWITCH(V) - will not fetch a reply from a switch module with matching
labelMANUAL SWITCH becauseV is not a valid parameter.
To specify a type of module, the label may be combined with the type identifier
The attribute messages that have been considered so far have been global messages (i.e. sent
to network node address 0). In order for this type of message to be actioned by the correct
controller(s), every controller must check the message device attributes to see if it has been
selected, thus the message must be received by every controller. This type of message is known
as a global message, and on the network, each node must simultaneously reproduce the
message to its device and pass it on round the network.
If this were a global request for values, each controller which had the relevant attributes would
reply with a value, so a number of replies will normally be received.
For example if the function required is the minimum function. The requirement is satisfied
by passing a large value (999) through each selected controller and if that controller has a value
less than the current value it will overwrite it. Thus when the message is received back it will
have the minimum value.
e.g. Outstation 20 21 22 23 24
Value 30 29 32 28 28.5
Minimum 999 30 29 29 28 28 28
start finish
In the above example, as the message value passes through a controller, it only gets changed
if the controller value is less than the message value (i.e. at outstations 20, 21, and 23). In this
way the message returns a minimum value.
There are three types of function, maximum, minimum, and sum. In the case of sum each
selected controller adds its value to the total carried by the message.
The visitor message must go to each controller to have its device attributes checked just like
a global, but the value it carries must be updated in sequence, so the message cannot be
regenerated in parallel like a global, instead it has to travel through each controller and back
onto the network so that it visits each controller serially.
29.16 Functions
Functions to be performed on data can be specified within the data field of the message. The
available functions allow the user to implement simple tests to find maximum or minimum
values, or the sum total value of all addressed items. Functions can only be applied to real or
integer values. The format of the function field is defined as follows;-
(parameter identity function type value)
e.g. S1(V+0.0) - sum of all values of sensor 1 starting with sum of 0.0
e.g.K1(V<25) - minimum of all values of knob 1 if less than 25 (if no value
below 25 the minimum remains at 25).
Note:
a) IQ controllers will not service more than one function field in any one message.
b) An addressed value which has an associated read alarm or sensor out of limits
alarm will be inhibited from responding, only if {M=OO??} is sent within the
conditional field of the message.
Text communications function messages have an option for the reply to contain two extra
fields; address and count. These extra fields enable determination of a) the location of the last
controller to contribute, which in the case of maximum and minimum information is the
address of the device having the maximum or minimum, or b) the number of items which have
contributed which in the case of a sum function can be used to calculate the average. To action
this the following is added at the end of the message:
;AD=0,CT=0
Either of these fields may be added separately. In the reply, the address field is the address of
the last controller which contributed to the function and the count field is the number of times
the function has been contributed to.
message S1(V)
replies L6O21 1FL3 A1 IQ91 S1 23.45
L6O22 1FL3 A2 IQ91 S1 23.45
L6O23 1FL3 A3 IQ91 S1 23.45
L6O24 1FL3 A4 IQ92 S1 23.45
L6O25 1FL3 A5 IQ92 S1 23.45
L6O26 1FL3 A6 IQ92 S1 23.45
L6O27 1FL3 A7 IQ93 S1 23.45
L6O28 1FL3 A8 IQ93 S1 23.45
L6O29 1FL3 A9 IQ93 S1 23.45
L6O30 1FL3 A10 IQ93 S1 23.45
L6O31 1FL3 A11 IQ91 S1 23.45
L6O32 1FL3 A12 IQ91 S1 23.45
L6O33 1FL3 A13 IQ91 S1 23.45
L6O34 1FL3 A14 IQ131 S1 23.45
L6O35 1FL3 A15 IQ111 S1 23.45
L7O21 1FL4 A1 IQ91 S1 23.45
L7O22 1FL4 A2 IQ91 S1 23.45
L7O23 1FL4 A3 IQ91 S1 23.45
L7O24 1FL4 A4 IQ92 S1 23.45
L7O25 1FL4 A5 IQ92 S1 23.45
L7O26 1FL4 A6 IQ92 S1 23.45
L7O27 1FL4 A7 IQ93 S1 23.45
L7O28 1FL4 A8 IQ93 S1 23.45
L7O29 1FL4 A9 IQ93 S1 23.45
L7O30 1FL4 A10 IQ93 S1 23.45
29.17.1 Examples of obtaining and changing values using Text Comms (Continued)
Example 2: To obtain Sensor 5 label, value and units from one controller
alternative
Device attribute 1FL3 A6*
Item attribute D3
Conditional
Data part $,Ss [label, source status]
Example 4: To obtain input and output values of a Loop module from one controller
29.17.1 Examples of obtaining and changing values using Text Comms (Continued)
Example 6: To search Sensors for Space Temperature label and obtain label and value.
Device attribute
Item attribute S\Space Temperature
Conditional
Data part $,V [label, value]
message 1234\K2(V=23.0)
reply if used this would modify the value of all knob 2’s to be 23.0, but would
provide no reply indicating the value changed.
Example 8:To modify the value of a Specific Controller's Knob 2 and confirm the change
29.17.1 Examples of obtaining and changing values using Text Comms (Continued)
Device attribute
Item attribute Space Temperature
Conditional V>21.4 [value greater than 21.4]
Data part $,V,%
Device attribute
Item attribute Space Temperature
Conditional V<21.0|V>22.0 [Value less than 21.0, OR, Value
greater than 22.0]
Data part $,V,% (Label, value and units)
message 1FL3*\L{M=???I}(V)
reply L6O61FL3 A6 IQ91 L3 5.4
L6O91FL3 A9 IQ91 L2 3.7
29.17.1 Examples of obtaining and changing values using Text Comms (Continued)
Example 13: Obtain data on all sensors which have high alarms
Device attribute
Item attribute S\?* [only Sensors with a label of at least one
character]
Conditional M=???I
Data part $,V,% [Label, value, units]
message 1FL3*\S\?*{M=???I}($,V,%)
reply L6O91FL3 A9 IQ91 S4 Space Temperature 25.1 degC
Example 14: To modify all knobs labelled Occ Set Point to a common value.
Device attribute
Item attribute K\Occ Set Point
Conditional V<22.0|V>24.0 [Value less than 22.0, OR, Value
greater than 24.0]
Data part V,V=23.0,$,V,% [Previous value, make value
equal to, obtain label, value and units]
Example 2: (Continued)
29.17.3 System Example - Maintain Service area lighting whilst Office occupied
Example - to maintain for a common floor after OSS control has ended, Service (corridor)
lighting for a pre-determined period exceeding Office lighting. This allows the last office
occupant to leave a safely lit floor via the Service areas. Note: no provision is made to allow
office personnel to return to the office area after the office light has been extinguished.
- the facility is limited to a single common floor on which a single common LAN exists.
- lights for common corridors must be labelled ‘Lights’ and fall within the ‘Service’
occupation zone.
- a single team leader H5# is established to control the status of all common ‘Service’
lights in the event that their condition is required to change, and that the same team
leader is required to interrogate the lights within the ‘Office’ occupation zone.
- lights in office areas must be labelled ‘Lights’ and fall within the ‘Office’ occupation zone.
See figure 29.19 and figure 29.9 for the implementation of this example in Newbuilding 1 on
floor 3.
Figure 29.19 Message routing and delivery associated with Example 29.22
message Office/Lights(V>-999.99);AD=0;CT=0
reply Office/Lights(V>1);AD=21,CT=1
Note: when the value V becomes a zero, ie, the last office light has been extinguished, after an
appropriate delay the team leader (H5) will send the following message:-
message 1234\Services\Lights(S=0)
reply none
This example is typical of the request to change the occupation set point applicable to a single
company on a single floor of a building.
In all cases the Macro Utility has established the fixed portion of the label as OCC SP, and the
local identifier e.g. Store has been added.
Example 10 AHU3/Damper*{M=OO??}(V>-999);AD=0,CT=0
AHU3 = attribute 3
Damper.Max = label of Sensor 18, so it is sent as Damper*
{M=OO??} = conditional on there being no read or outside limits alarms
(V>-999) = requests value if greater than -999
AHU3 = attribute 3
Cooling Demand = label of sensor 19
{M=OO??} = conditional on there being no read or outside limits alarms
(V+0.0) = request sum starting at 0.0
XYZ Co = attribute 2
Space Temperature = Label of sensor 20
{M=OO??} = conditional on there being no read or outside limits alarms
(V+0.0) = request sum starting at 0.0
The IC Comms module calculates the average by dividing the sum by the count.
0/0 specifies node zero on LAN zero i.e. a local global message
0/n specifies node zero on LAN n i.e. a global message to a specified LAN, remote global.
0/128 specifies node zero on all LANs i.e. a global global message
Note: the global global (0/128) causes the message to branch at the INC so that it is received
in parallel by each LAN on the inter-network.
Ordinary global messages are sent in normal text mode whereas visitor messages are sent in
terse text mode. If a visitor message is sent in normal text mode it will cause network
problems. On the 822+/Toolkit, the Supervisor address must be correct for visitor messages
to work correctly.
29.20.1 Values
[security code/][device selection/] item selection [{conditional}] (data part) [;message data]
Multiple Items more than one item from selected device (s)
e.g. IFL3/S1($),S2($),S3($)
A1 APPENDIX
Module Type IQ7x IQ9x IQ9x+ IQ10x IQ10x+ IQ111 IQ111+ IQ131 IQ131+ IQ151 IQ151+
Sensor Type 3 6 8 8 8 8 8 8 8 12 12
Sensor 12 12 32 32 32 32 32 32 32 48 48
Digital Inputs 12 12 32 32 32 32 32 32 32 48 48
Fast sequencing on 1st 'n' inputs none 5 8 8 8 8 8 8 8 8 8
Loop 6 6 16 16 16 16 16 16 16 32 32
Logic 18 18 64 64 64 64 64 64 90 88 160
Function 30 30 64 64 64 64 64 64 90 88 160
Driver 8 6 12 12 12 12 12 12 12 32 32
Knob 6 6 25 25 30 25 25 25 30 30 30
Switch 6 6 20 20 20 20 20 20 20 20 20
Sequence Step 80 84 104 104 148 104 148 148 180 320 400
Zone 1 none 1 5 5 5 5 5 5 5 5
Schedule none none 8 8 8 8 8 8 8 32 32
Calendar none none 20 20 20 20 20 20 20 20 20
I/C Comms 4 4 16 16 16 16 16 16 16 16 16
Critical Alarms none none 4 4 4 4 4 4 4 4 4
Users (Passwords) 6 6 6 6 6 6 6 6 6 6 6
Logging Channels 6 8 16 16 20 16 20 20 32 32 40
Alarm History Records 10 10 20 20 20 20 20 20 20 20 20
Analogue Nodes 255* 255* 255* 255* 255 255* 255* 255* 255 255 255
Digital Nodes (bytes) 505 505 505 505 505 505 505 505 505 505 505
Labels On all sensors, drivers, knob, switches and zones
DigIn Labels (separate) - - - - - - - - 48 48 48
Parameters
min loop Reschedule time 5s 5s 5s 5s 5s 5s 5s 5s 5s 15s 15s
Sequence table cycle time 5s 5s 5s 5s 5s 5s 5s 5s 5s 15s 15s
Sensor tYpe Top/Bottom (linear) §±10V ±10V ±10V ±10V ±10V ±5V ±10V ±10V ±10V ±5V ±5V
Thermistor table (linearise) voltage # 10V 2.5V 10V 10V 10V 10V 10V 10V 10V ¶10V 10V
Ref Volts Setting (default) 5V 2.55V 5V 5V 5V = = 5V = = =
Vref for linearisation using equation # 10V 2.55V 10V 10V 10V 10V 10V 10V 10V ¶10V 10V
* Nodes associated with non-existant knobs do not exist (e.g.. node 246 in IQ131).
¶ Pre Jul'89 IQ151 controllers use LK/D (as there is no thermistor linking position), and
use V ref of 5 V.
§ On IQ70's, when using channels 1,2 in a linear mode use ±5 V, whereas for channel 3
use ±10 V.
# The Vref value is for insertion into linearisation equations (section 26.2.2).
The controller normally has a battery backed real time clock so that the clock will continue to run
during power failure whereas in the case of the IQ9x controllers, they have only a software clock
and need to be synchronised after power is resumed. (IQ9x+ Controllers do have a real time clock).
The fast sequencing normally occurs on the first 'n' inputs usually 1-8) as shown in the table
above, however on the IQ131+ this is no longer true. The first four input channels are analogue
only so that they cannot be used as digital inputs for fast sequencing, instead the first four fast
inputs are transferred to input channels 17-18. Input channels 5-8 do however have digital input
fast sequences as normal. This means that to start a fast sequence for digital input 17, the
reference I1 must be entered in the sequence table (not I17) whereas for digital input 5 it is I5.
This is shown in the table below.
Fast Sequence
Input Channel
Reference
5 I5
6 I6
7 I7
8 I8
17 I1
18 I2
19 I3
20 I4
e.g. To start a fast sequence for digital input channel 18 at sequence step 80 set Q80 to I2.
The IQ7x single zone has an inhibit bit in the digital array (byte 496 bit 1) which can be used to stop
the OSS and time clock updating by OSS and timeclock when set to 0 it permits it. This enables the
IQ7x to be run as a slave of another IQ controller which can control byte 13 by IC COms.
The IQ7x has a single zone operating from its OSS and time clock (Zone 1, byte 13)_. The other
conventional zone bytes (14 to 17, zones 2 to 5) are available and can be controlled by another
controller by IC Coms. These bytes can then be used in internal strategy (e.g. to control a loop
setpoint selection bit).
This table shows the settings (B, T, F to J) needed in the Sensor Type module when set for
linearisation for the standard Trend thermistors and their temperature ranges. The 10 V, LK/
D and 2.55 V tables depend on which controller is used as shown below the table.
-10 °C to 110 °C -10 °C to 40 °C -30 °C to 58.75 °C
10 V LK/D 2.55 V 10 V LK/D 2.55 V 10 V LK/D 2.55 V
Brange -10 -10 -10 -10 -10 -10 -30 -30 -30
Trange 110 110 110 40 40 40 58.75 58.75 58.75
F 8.47 4.61 2.15 8.47 4.61 2.15 9.47 4.87 2.41
G 5.55 3.63 1.41 7.42 4.30 1.89 8.31 4.56 2.12
H 2.65 2.17 0.68 6.11 3.83 1.56 6.20 3.86 1.60
I 1.12 1.05 0.28 4.73 3.28 1.21 3.91 2.83 1.00
J 0.49 0.49 0.12 3.48 2.66 0.89 2.15 1.78 0.55
10 V For all IQ's except those without thermistor links and IQ9x's. (IQ9x+
Controllers do use 10 V).
LK/D Use when the LK/D link header is used; this is needed on IQ's without
thermistor linking (IQ131 and IQ151 pre July 1989).
2.55 V For IQ9x series controllers only.
Analogue Digital
Controller type Total 0-10V 0-20mA Thermistor Status Pulse/Count
IQ71 3 3* - 1,2* - -
IQ72 3 3* - 1,2* - -
IQ73 3 3* - 1,2* - -
IQ91 6** or
IQ92 6** or
IQ93 6** or
IQ101 6 or
IQ102 6 or
IQ103 6 or
IQ111 8 or
IQ131 16 *** or
IQ151¶ 32+32 and
IQ111+ 8 or
IQ131+ 20**** or
IQ151+¶ 32 + 32 and
IQ91+ 6 or
IQ92+ 6 or
IQ93+ 6 or
IQ101+ 6 or
IQ102+ 6 or
* Note: Channel numbers given for the IQ7x series (e.g. channel 3 is 0-10V, V).
** Note: Channel 6 cannot be digital.
*** Note: To accomodate thermistors use appropriate Link Header (LK/D).
**** Note: On IQ131+, channels 1-4 are analogue only (not digital), channels 5-16 are universal,
channels 17-20 are digital only (not analogue).
¶ Note: On IQ151, IQ151+, there are 32 analogue only inputs and 32 digital only inputs.
It is possible to convert analogue only input channels to digital inputs. This is done by using
the analogue input sensor module to generate an alarm bit when the contact is closed, and clear
the alarm bit when open. This is then conected to an internal digital node via a logic module.
9+1
G
0V IN1 Thermistor input channel
41,0
A1 A2 high E E
9
comb 1,0
S1
1 1
switch 1 1
In this case the Sensor Type is set, S = 0 (linear), E=1 (exponent range -3 to +3)
T = 0 (value at + 5 V), B = 2 (value at -5 V)
U=1 (Upper limit 1,) L=0 (Lower limit 0)
Because of the anomalous action of the IQ7x series controllers (as explained in A1.1 above),
T and B for channels 1 or 2 are at ±5 V whereas for channel 3 they would be at ±10 V.
When the switch is open the input level is 5 V which is converted to 0, when closed it is 0 V
which is converted to 1. The high alarm limit should be set to 0.5.
The IQ131+ Analogue only inputs (channels 1-4) can be used in a similar way.
With the IQ151+ the sensor scaling needs to be adjusted for ±5 V Top and Bottom, and spare
internal digital must be used (i.e. For channel 1, node 1,0 cannot be used as it is already allocated
to digital input 1).
Accuracy
Thermistor Volts Current Resolution
IQ7x 1 % span ±1 % x 8 bit (39 mV)
8 bit with oversampling, equivalent
IQ9x 1 % span 300 mV 400 µA
to 11 bit (2048 steps)
8 bit with oversampling, equivalent
IQ9x+ 1 % span ±1 % ±1 %
11 bit (2048 steps)
8 bit with oversampling, equivalent
IQ10x 1 % span 300 mV 400 µA
to 11 bit (2048 steps)
8 bit with oversampling, equivalent
IQ10x+ 1 % span ±1 % ±1%
11 bit (2048 steps)
IQ111 0.5% span 50 mV 100 µA 12 bit resolution (4096 steps)
8 bit with oversampling, equivalent
IQ111+ 1 % span 300 mV 400 µA
to 11 bit (2048 steps)
IQ131 x 50 mV 100 µA 12 bit resolution (4096 steps)
IQ131+ 1 % span 50 mV 100 µA 12 bit resolution (4096 steps)
IQ151 0.5% span 50 mV 100 µA 12 bit resolution (4096 steps)
IQ151+ 0.5% span 50 mV 100 µA 12 bit resolution (4096 steps)
Analogue Digital
Raise/Lower (1
Controller 0-10 0-20 Single Pole
Total No Triac raise +1 lower PWM
type V mA Changeover Relay
channel)
IQ71 6 0 - - - 6 - -
IQ72 4 2 - - 2 - -
IQ73 4 0 - - - 2 - 2
IQ91 6 1 1 - 4*** -
IQ92 4 4 - - - -
IQ93 6 2* - - 4*** -
IQ101 6 1 1 - 4*** -
IQ102 4 4 - - - -
IQ103 6 2* - - 4*** -
IQ111 6 6 - - - -
IQ131 12 12 - - - -
IQ151 32** 32 or** 32 - - -
IQ111+ 8 8 - - - - -
IQ131+ 12 12 - - - - -
IQ151+ 32** 32 or** 32 - - -
IQ91+ 6 1 1 - 4*** -
IQ92+ 4 4 - - - -
IQ93+ 6 2* - - 4*** -
IQ101+ 6 1 5 - - -
IQ102+ 6 6¶ - - - -
¶ Note: On IQ102+, channels 1 to 4 are Analogue voltage only, whereas channels 5 and
6 are Analogue voltage or current.
* Note: Channel 5 can only be analogue voltage.
** Note: Output channel types are selected in units of eight.
*** Note: These four channels consist of two raise/lower pairs.
IQ101+ IQ102+
channel 1 SPCO Relay channel1 Analogue V
channel 2 SPCO Relay channel 2 Analogue V
channel 3 SPCO Relay channel 3 Analogue V
channel 4 SPCO Relay channel 4 Analogue V
channel 5 SPCO Relay channel 5 Analogue V/I
channel 6 Analogue V/I channel 6 Analogue V/I
Analogue Digital
Controller V I SPCO Triac R/Lpair PWM
type 0-10 V 0-20 mA - 24 Vac - 20 Vrms
IQ7x ¶ 20 mA - - 0.5 A** - 15 VA**
IQ9x ¶ 20/10 mA* 1100 Ω 250 Vac 5A resistive - 250 Vac 5A res -
IQ10x ¶ 20/10 mA* 1100 Ω 250 Vac 5A resistive - 250 Vac 5A res -
240 Vac, 28 Vdc
IQ10x+ 20 mA 1100 Ω 5 A resistive - - -
2 A inductive
IQ111 20 mA 1100 Ω - - - -
IQ111+ 20 mA - - - - -
IQ131 20 mA 1100 Ω - - - -
IQ131+ 20 mA - - - - -
IQ151 20 mA 1100 Ω 250 Vac, 5A resistive
240 Vac, 28 Vdc
IQ151+ 20 mA 1100 Ω 5 A resistive
2 A inductive
250 Vac, 5 A 250 Vac, 5A
IQ9x 20/10 mA* 1100 Ω resistive
-
res
* All channels are 20 mA except channel 5 on an IQ93, IQ103, IQ93+ (Analogue Voltage
only) which has a 10 mA current limit.
A1.5 Connections/Settings/Options
(Local) Network
Supervisor Node Device
1k2
4k8
H 9k6 H 19k2
IQ CNC+
L 1k2 L 1k2 9k6
RS232 RS232
19k2
(Local) Network
Supervisor
Baud Speed
IQ7x 9600
IQ9x 9600
IQ9x+ 9600
IQ10x 9600
IQ10x+ 9600
IQ111 1200 or 9600
IQ131 1200 or 9600
IQ151 1200 or 9600
IQ111+ 9600
IQ131+ 9600
IQ151+ 9600
1) Inputs - Some input devices need 24 Vdc (e.g. I inputs using Trend current sensors, volt
free contacts for digital inputs, 4 DIX module).
2) Outputs - Some output devices consume 24 Vdc via the output signal since both 0 -10
Vdc and 0 to 20 mA outputs are supplied from the 24 Vdc (e.g. relays SRMI or SRMV,
most relay modules 2RM, 3RM etc). In addition, most output interfaces require a
separate 24 Vdc supply, normally taken from the instrument supply.
4) Display Panel: This can be attached to some IQ controllers either via a connector or
integral in the lid. It consumes 60 mA.
* Note: The inputs and ouputs on an IQ7x series controller do not have any bearing on the
instrument supply, hence 50 mA is always available.
** Note: The channel 5 outputs of the IQ93, IQ93+, and IQ103 are limited to a maximum
of 10 mA.
§ Note: 250 mA per input board, and 250 mA max per analogue output board. If not all
boards are drawing current, more power may be taken from a board to 500 mA per board
(board fuses at 500 mA) and 1 A max overall.
¶ Note: 224 mA each input board, 160 mA each output board, in addition each analogue
output board may supply 24 Vdc for its 24 terminal as long as board maximum of 500
mA and overall maximum of 1750 mA is not exceeded.
The Trend interface module and node controllers 24 Vdc current requirements are listed below:
The total load (inputs, outputs and node controllers) must not exceed the total mA available
from an IQ controller. The 24 Vdc supply fuse may sometimes need to be changed, and this
is done at the users risk and should be clearly marked on the unit.
e.g. An IQ111+ has an integral MNC+ and 4 analogue current inputs, 2 analogue voltage
inputs, and 2 digital inputs. Can the controller drive 2 SRMV modules and 6 RLM modules.
Total current available for IQ111+ is 790 mA. Hence there is still 182 mA left.
The total current being taken from the fused supply terminal is 162 mA which is below the 200
mA fuse rating and hence the fuse need not be changed.
Issue IQ Changes
1 151, 131
2 151, 131 Firmware upgrade for Display Panel (Display Panel on
IQ131) to include module labels, alarm history, user
passwords, holiday calendar, knobs, switches.
Universal inputs supported by sensor mode (digital
and internal digital). Function module type 17
(hysteresis), logic module type 6 (hours run).
Supervisor comms to local supervisor connector.
GLOSSARY OF TERMS
Abbreviations
A
A Analogue or Universal Input Channel CNTR Counter module
reference COMB Combinational module
AANR Autodialled area not responding COMMS Communications
ABC Advanced Building Control CONL Controller on Line
ac. Alternating Current CPU Central Processor Unit
ACK Acknowledge CPVF Clear Process Variable Fail
ADA Alarm Destination Acknowledge CRM Cascade Relay Module
(Critical Alarms) CSDV Clear Setpoint Deviation
ADC Analogue to Digital Convertor Ctrl Control
ADD Adder/Scaler Module
ADM Autodial Modem D
AHU Air Handling Unit
D Driver module
A/I Analogue Input
AN Analogue Node DAC Digital to Analogue Convertor
dB Decibels
ANC+ Autodialled Node Controller
AONL Auto-dialler On Line dc. Direct Current
APL April dd/mm/yy Day/Month/Year
DDE Dynamic Data Exchange
A/O Analogue Output
AQ Air quality DEC December
DEV Deviation
ASA Alarm Supervisor Acknowledge (Critical
Alarms) Deg Degree
ASCII American Standard Code for DIG Digital
Information Interchange DIGIN Digital Input
AUG August DIM Digital Input Multiplexer
AUX auxiliary box DIGOUT Digital Output
DO Digital Output
DP Display Panel, Differential Pressure
B
DPCM Dual Phase Cut Module
B Knob or Output Channel on IQ DRW Micrografx format graphic file
controller or Bottom of Range or Digital
Bit Node
BEMS Building and Energy Management E
System E Error, Calendar
BIT Binary Digit EM Electricity Meter
BINSW Binary Switch ENTHY Enthalpy
BMS Building Management System EPROM Erasable Programmable Read Only
BSW Binary Switch Memory
BTNR British Telecoms Not Responding: Lines EXT External
Engaged or Telephone Fault EMA Energy Monitoring and Analysis
C
C Common or Copy F
CA Critical Alarm F Function Module, Off Time Delay,
CAD Computer Aided Drawing scaling Factor
CD Cooldown FCM Fan Coil Module
CDGT Clear Driver Grace Time FDP Front Panel Mounting Display Panel
CDIn Clear Digital Input (n=0 or 1) FDRT Fail Dual Asynchronous Receiver
CHIH Clear Sensor High Transmitter
CLOW Clear Sensor Low FEB February
CMNT Clear Maintenance Interval FNC Fieldbus Node Controller
CMOS Complimentary Metal Oxide Semi- FP Front Panel (Display Panel)
Conductor FPK Front Panel mounting kit (Display
CNC+ Communications Node Controller Panel)
CNCL+ Communications Node Controller FPIA Fail Peripheral Interface Adaptor
LanCard
FPRM Fail Programmable Read only Memory LAN Local Area Network
FRI Friday LCD Liquid Crystal Display
FRAM Fail Random Access Memory LED Light Emitting Diode
FRTC Fail Real Time Clock LIM Limit
FSWR Fail Software LK Link Header
FTKA Fail Timekeeper Advice LNC+ LanCard
FTKP Fail Timekeeper LO Low
log, LOG Logarithm, Logging Channel
G LRM Latching Relay Module
G Logic Module, Gain
M
H M Manual or Critical Alarm
mA Milliampere
H Schedule module MAINT Maintenance
hhmm Hours and Minutes max. Maximum
HCM Heat Cool Module min. Minimum
HDM Hayes Modem MCFnn Modular controller Fan Coil Unit
HDP Hand Held Display Panel Strategy
HEX Hexadecimal MCVnn Modular controller VAV Unit Strategy
HIGH Sensor High alarm limit MINT Maintenance Interval Alarm
HHDP Hand Held Display Panel MNC+ Modem Node Controller
HHT Hand Held Tool MON Monday
HLM High Lower Relay Module MONR Modem Not Responding Local Modem
HTG Heating Fault
HNC Hayes Node Controller MS-DOS Microsoft Disk Operating System
Hrs Hours Run Logic Module MULT Multiply logic module
HYST Hysteresis
Hz Hertz
N
I N On delay or Inter-Controller Comms
NC Normally closed
I Input, Current, Integral Time Constant NDP Network Display Panel
IC-COMMS Inter Controller Communications NETB Network Box
ID Internal Digital NETBB Battery Backed Network Box
IEC International Electrotechnical NO Normally open
Commission NOC Non Occupation
IIM Input Isolation Module NOV November
I/N Internetwork NUA Network User Address, on PSDN’s
I/O Input/Output
IP Input
O
IQ Range of Trend Controllers
INC+ Internetwork Node Controller O Occupational Setpoint or OSS or Offset
INT Internal OAT Outside Air Temperature
INV Inverted OCC Occupation Time
OCT October
J OK Alright
OP Output
J Adjustment OSL Outside Limits
JAN January OSS Optimum Start/Stop
JUL July OSTN Controller
JUN June OTP Occupational Time Profile
OUTL Outside Limits Alarm
K
K Knob P
kHz Kilohertz P Proportional or Plot (Logging)
kW Kilowatt PAD Packet Assembler Disassembler
kWh Kilowatt hour PCX Paintbrush format graphic file
PI Proportional, Integral control
L
L Loop, Manual Level, sensor lower limit
S
S Sensor
SAT Saturday
SDEV Setpoint Deviation
SDGT Set Drive Grace Time
SL Sensor Lower
SNC+ Supervisor Node Controller
SP Setpoint
SRM Single Relay Module
SS Setpoint Select
SU Sensor upper limit
SUN Sunday
T
T Type or Reschedule Time or Time
TRM Triple Relay Module
THU Thursday
TP Time proportional
TUE Tuesday
TX Transmitter
U
U Sensor Upper Limit or User (PIN -
Password)
Terms ANC+
Address The ANC+ (Autodial Node Controller) is a
small micro-processor based unit providing a
•A number that identifies a unique location in
a computer’s memory. node on the communications network to link
an auto-dial modem to the network; providing
LAN to LAN communication via a telephone
•A number that identifies a particular software
connection.
or hardware input/output.
Aspect
•A number that identifies another device on
the network (CNC+ Address). Part of the 945 navigator structure, provides
access to plant schematics.
Autodialling Modem
Attribute
Interfaces between an autodial node controller
(ANC+) and the telephone network. An attribute is generally taken as a quality or
characteristic ascribed to an item. In the case of
Alarm Address text communications its meaning is restricted to
a label or identifier of a device or item.
The address of the supervisor to which alarms
are sent.
Audible Alarm Unit
Alarm Delay A PNC+ mounted in an auxiliary box complete
The time duration for which an alarm condition with Latching Relay Module a lamp, alarm
has to be continuously present before an alarm annunciator , and push-button. When an alarm
condition is declared. is received by the PNC+ it will sound the alarm
and switch the light on.
Alarm Panel
Autodialler
A pop-up window that is displayed on the
screen when an alarm is received. A modem which can automatically dial a
telephone number. See ANC+ and modem.
Analogue
Autodialled
A variable which represents a physical
quantity. The analogue value varies as would Automatic telephone destination dialling,
the physical level (e.g. temperature, humidity). connection, and link confirmation by a modem
device.
Analogue Address
Autodialled LAN
The location of an analogue input/output value
in the memory analogue array in the range 0 A LAN that communicates with the reference
- 255. device by means of an autodialled telephone
link. The receiving autodial device is on the
Analogue Array same LAN as the destination device.
The area in memory where analogue values
Autodialled Remote LAN
are stored.
A LAN that communicates with the reference
Analogue to Digital Converter device by means of an autodialled telephone
link. The receiving autodial device is
Converts voltage (analogue) signal into a
connected to the destination device via an inter-
binary (digital) number which can be used by
network.
a micro-processor.
Download Firmware
To send the control strategy to the controller Software that is permanently stored and cannot
be changed by the operator; firmware is stored
Editing in ROM, PROM and EPROM.
The adjustment of parameters on the system.
Full Scale Drive Time
EPROM The time taken for devices such as valves to
Erasable Programmable Read Only Memory. move from one end stop to another.
A hardware form of non-volatile memory used
for data storage. Once programmed with data, Function
the entire contents can only be erased by the
The software module which performs specific
use of an ultra violet light source. An EPROM
calculations and manipulation of analogue
can be read from but not written into.
values depending on module type and
Error
configuration.
The difference between the setpoint and the
measured value in a control loop. •A Supervisor facility to provide an efficient
means of invoking a learned sequence of key
Exponent strokes, by use of a single key stroke, to provide
A mathematical function; raise to the power of. a defined output or system function.
A parameter to be entered in sensor type module.
•A part of a text comms message which can
Extension specify maximum, minimum, or sum of a set
of values.
The fullstop and three letters at the end of a
filename. An extension identifies the type of Gain
information a file contains.
Gain is normally equal to power out/power in.
Family icons However in a Trend loop the gain is
proportional part of output / Error.
The family icons are used to move up and
down the schematic aspect hierarchy. They Global Message
are normally displayed in the top left hand
A message sent to all controllers. Local global
corner of any schematic aspect.
on own LAN or Global Global to all LANs
Feed Forward Control
Grace Time
The adjustment of factors within the strategy
A user-entered time that delays checking a
to cope with predicted events.
state until the time has elapsed.
Fieldbus
Graph
A low cost relatively low speed
One value plotted against another using scaled
communication bus designed to routed around
axis. In the Trend system a graph generally
plant rooms, or the ‘field’ (e.g. a group of fan
plots a system value or values with respect to
coil units). A standard bus adopted by other
time.
suppliers.
Graphic
Filename
A graphic is any drawing that can be place on
The name of a file. a 945 schematic aspect.
The predetermined output level to which a A part of the firmware that contains all the
module output will change when the manual information related to a particular function.
state is selected.
IQ Configuration Manual Issue 6/A 1/6/93 Page G - 9
SECTION - GLOSSARY IQ CONFIGURATION MANUAL
RAM ROM
Random Access Memory. A hardware device Read Only Memory. A non-volatile form of
providing volatile data storage i.e. data stored data storage that can be read from but not
is lost in the event of power failure (unless written to.
battery backed). RAM can be written to and
read from. RS232
A defined standard for serial data communication.
Read
The process of obtaining data from an input, Run
memory or storage device. To start a program.
Real Time Clock Sample Period
A hardware device capable of accurate time The time interval between readings when a
measurement. Additional facilities keep track sensor value is logged.
of year, month, day, date, hours, minutes and
seconds. Save
Warm Up
The time period between the starting of plant
(heating or cooling) and occupation occurring
i.e. Optimum Start to OTP start.
Version
A number indicating one of a sequence of
versions. Used in conjunction with issue to
define exact product status. Format Issue X.x
where X = version number.
Watch Dog
A part of a unit which checks for correct
running of the rest of the unit.
Window
A rectangular area on the supervisor screen in
which you may view a program.
Windows
A user friendly environment used by the 945.
Symbols
& ............................ 5-3, 29-4, 29-19, 29-21, 29-35 Analogue Gate ............................................ 13-1, 13-11
* ................................. 5-3, 14-6, 29-1, 29-4, 29-35 analogue IC comms ................................................. 14-9
+ ................................................................ 29-24, 29-36 analogue input ............. 2-4, 14-9, 22-1, 22-6, A1-4
. ........................................................... 5-4, 14-6, 29-4 Analogue nodes .............................................. 2-6, 15-1
< .................................................. 29-19, 29-24, 29-36 Analogue Only to Digital Conversion ..................... A1-4
= ............................................................................. 29-19 analogue output .............................................. 2-4, 12-1
> ......................................... 3-4, 29-19, 29-24, 29-36 analogue output driver ............................................. 12-2
? ............................................. 5-4, 14-6, 29-4, 29-35 Analogue Status ......................................................... 7-4
| ............................... 5-3, 14-6, 29-4, 29-19, 29-21, Analogue to Digital ............................................... 13-13
29-35 Analogue to Digital converter ....................... 13-1, 26-1
1 (*) ....................................................................... 29-18 Analogue Variable type ........................................... 14-3
24 Vdc Supply ......................................................... A1-9 ANC+ ........................................................................ 8-2
2RM ......................................................................... 12-8 anti-phase output ............................ 12-3, 12-7, 12-10
3RM ......................................................................... 12-8 asterisk ..................................................................... 14-6
4DIX ...................................................................... 13-14 at steps ....................................................................... 3-6
822 .................................................. 2-12, 27-2, 29-20 attribute ........................................... 14-5, 29-1, 29-20
822 Utility ................................................................. 3-6 attribute 2 ................................................................... 5-6
822+/Toolbox ............................................... 2-3, 29-18 attribute addressing ...................................... 29-1, 29-6
Attributes ................................................................. 29-9
A Auto-Dialling Reference Manual .............................. 5-2
a raise/lower relay module .................................... 12-11 Autodial Modem ....................................................... 1-1
a secondary process ............................................... 17-21 Auxiliary Communication Node ............................. A1-9
absolute addressing ................................................. 29-1 average .................. 13-1, 13-10, 14-1, 14-5, 14-10,
Accessory Module .................................................A1-10 14-16, 29-29
Accuracy on Input Channels ................................... A1-5
B
ACK ........................................................................... 6-2
acknowledge bits ............................................ 8-2, 10-1 battery ................................................. 2-3, 2-12, A1-2
acknowledge status .................................................... 6-3 battery backed ......................................................... 25-1
actuators .................................................................. 12-2 battery backed clock ................................................ 25-1
Add .......................................................................... 13-1 battery fails .............................................................. 27-3
Adder/Scaler ............................................................ 13-8 Baud Rate ..................... 2-3, 2-4, 2-12, A1-8, A1-9
addr switch ................................................................ 5-6 Binary Switch Driver ............................................. 12-10
address ...................................................... 29-24, 29-36 binary/switch ........................................................... 12-1
address field .......................................................... 29-24 bit .................................................................... 2-6, 10-1
Address Module ............................................. 5-1, 27-3 bits ............................................................................. 2-7
Addresses .................................................................. 5-6 Boundless Operation ............................................... 12-8
Adjustment Id .......................................................... 15-1 British Summer Time .............................................. 25-4
Adjustment mode .................................................... 15-2 byte ................................................................. 2-6, 10-1
adjustments .............................................................. 15-1 Byte numbers ............................................................. 2-7
Alarm ......................................................................... 6-8
alarm address ... 2-12, 5-1, 5-2, 5-6, 6-1, 6-9, 7-1 C
alarm bits ............................................................... 13-14 Calendar..................................................................... 9-1
alarm buffer ............................................................. 20-1 calendar dates .......................................................... 2-13
Alarm Buffer Empty ................................................ 20-2 cascade control ........................... 17-20, 17-22, 17-24
alarm bytes ................................................... 10-1, 21-2 cascaded loop .......................................................... 18-8
alarm delay ......................................... 6-2, 11-2, 22-3 CDGT ........................................................................ 6-9
alarm enable .............................................................. 6-3 CDIn .......................................................................... 6-9
alarm generation ........................................................ 6-2 changing ................................................................ 29-25
alarm history buffer .............................. 6-1, 6-2, 20-1 Changing Data ....................................................... 29-18
alarm states .............................................................. 10-1 checksum ....................................... 5-4, 5-7, 6-5, 6-7
alarm status ................................................................ 3-5 CHIH ......................................................................... 6-8
alarm status byte ........................................... 8-2, 17-29 Clear Digital Input alarms ....................................... 11-2
Alarm Types .............................................................. 6-1 clock link ................................................................. 2-12
alarms ............................................................... 2-3, 6-1 CLOCK WRONG ................................................... 20-2
ampersand ................................................................ 29-4 closed loop .............................................................. 17-3
Analogue........................................................ 2-3, A1-3 CLOW ....................................................................... 6-8
Analogue Alarms ..................................................... 10-4 CMNT ....................................................................... 6-9
analogue array .................................................. 2-7, 7-1 CNC ......................................................................... 2-12
CNC Address ............................................................. 2-3
F I
Fail TimeKeePer ..................................................... 25-3 IC Comms ......................................... 5-3, 27-2, 29-33
Failed TimeKeeper Advice ............................ 6-2, 25-3 IC Comms Fail Bit ................................................ 14-20
fast response ............................................................ 23-4 IC COMSFAIL ........................................................ 10-9
fast sequencing ............. 2-8, 2-11, 3-6, 11-3, 23-4, identifier .............. 5-2, 5-6, 8-2, 14-5, 29-2, 29-7,
A1-2 29-10, 29-20
FDRT .................................................... 6-4, 6-6, 20-2 Initialising an IQ ...................................................... 2-12
Feed Forward Control ........................................... 17-24 Input Channels ............................................... 2-3, A1-3
Filter ............................................................. 13-1, 13-2 INPUT ERROR ....................................................... 20-2
Firmware .................................................................... 1-1 inside air temperature .............................................. 18-2
Fixed ........................................................................ 21-1 Integral CNC+ ......................................................... A1-8
FPIA ..................................................... 6-4, 6-5, 20-2 integral term ............................................................ 17-8
FPRM ................................................... 6-4, 6-7, 20-2 integral time ............................................................. 17-8
FRAM ............................................................... 6-4, 6-6 integral time constant .............................................. 17-8
Free nodes ................................................................. 7-1 inter-controller communications .......... 1-1, 2-3, 14-1
free steps .................................................................... 3-6 interconnection of modules ....................................... 2-7
FREESPACE ........................................................... 10-4 Internal Analogue .................. 14-9, 22-1, 22-6, 22-8
Freeze Output ........................................................ 17-16 Internal digital ........... 14-9, 22-1, 22-6, 22-7, 22-8
FRTC .................................................... 6-4, 6-6, 20-2 internal digital input ................................................ 11-2
FSWR ................................................... 6-4, 6-6, 20-2 internal digital node ................................................. A1-4
FTKA ............................... 6-2, 6-4, 6-7, 20-2, 25-3 internal sensor ......................................................... 22-2
FTKP ......................................... 6-4, 6-7, 20-2, 25-3 IQ Controller ............................................................. 1-1
full stop .................................................................... 14-6 IQ70 ......................................................................... 18-1
function .................. 7-1, 14-10, 23-1, 29-24, 29-36 issue ........................................................................... 5-5
Function Module ..................................................... 13-1 Issue Variants ........................................................A1-11
function type ............................................. 29-29, 29-30 Item Alarms ...................................................... 6-1, 6-8
item attribute........ 14-8, 29-3, 29-21, 29-22, 29-35
G
item identifier ........................................................ 29-35
gain .......................................................................... 17-6 item label .................................................... 29-3, 29-35
gain constant ............................................................ 18-4 item selection ......................................................... 29-17
Gain Time Constant (Cooling) ................................ 18-6 item type identifier ................................................ 29-35
general alarms .............................. 6-1, 6-4, 6-7, 10-6
global ....................................................................... 14-5
K
global alarm inhibits ........................... 6-2, 6-11, 10-9 Knob Adjustment Mode ............................... 15-3, 15-4
global global message .................................. 5-1, 29-34 knobs .................................................. 2-13, 7-1, 15-1
global messages ........................................ 29-22, 29-34 kW ......................................................................... 16-11
Global Output .......................................................... 14-8
global to ............................................ 14-1, 14-8, 27-2 L
grace timer ............................................................... 16-8 labels ...................................... 2-9, 22-4, 22-5, 29-20
H Lan ............................................................................. 5-1
Lan number ....................................................... 5-2, 8-2
hardware configuration ............................................. 2-3 LAN number 0 ......................................................... 14-1
Hardware Failure ....................................................... 6-5 LAN number 128 ..................................................... 14-1
HCM ........................................................................ 12-9 Limit at ......................................................... 13-1, 13-5
Heat Cool relay module .......................................... 12-7 Limit to ......................................................... 13-1, 13-5
Heating and Cooling .............................................. 17-28 limits ........................................................................ 26-1
Heating mode .......................................................... 18-2 linear ........................................................................ 26-2
Heating/Cooling Loops ........................................... 18-7 Linear Sensor ........................................................... 26-6
HELP ........................................... 5-4, 6-4, 6-5, 20-2 linearisation ................................................. 26-2, A1-3
HIGH .............................................................. 6-8, 20-2 linearise ................................................................... 26-2
High Alarm ................................................................ 6-8 list of types ................................................................ 3-5
HIGH VALUE ........................................................ 20-2 Load ER ..................................................................... 3-6
Holiday Calendar ....................................................... 9-1 Load OK .................................................................... 3-6
holiday dates .............................................................. 9-1 local address ............................ 2-12, 5-1, 5-6, 29-10
hours run ..................................................... 16-1, 16-12 local global message.............................................. 29-34
hysteresis ........................... 12-10, 13-1, 13-12, 22-3 local lan ................................................................. 29-10
local supervisor ....................................................... 2-12
log ................................................................. 13-6, 19-1
logarithmic .................................................... 13-1, 26-2
T W
team leader ..................................... 14-11, 28-2, 29-5 Warm-up ...................................................... 18-7, 18-11
team members ............................................. 14-11, 29-5 Weather Compensated Control ............................. 17-18
temperature ............................................................ 13-12 wildcard ........................................... 29-1, 29-4, 29-19
terse text mode ...................................................... 29-34 wildcards * and ? ................................................... 29-21
Text Alarm Format .................................................. 6-10 Z
text communications
1-2, 27-2, 29-1, 29-6, 29-7, 29-16, 29-25, zone ......................................................................... 18-1
29-35 zone inhibit .................................................. 28-2, A1-2
Text Flag......................................................... 6-9, 10-9 zone labels ..................................... 28-2, 14-10, 14-11
Text Matching ......................................................... 29-4 zone time modules ................................................... 28-1
text on/off ......................................................... 5-2, 5-6 Zones ............................................................ 10-3, 28-1
text string ................................................................. 29-4
Thermistor table (linearise) voltage ........................ A1-1
thermistors ...................................................... 2-4, 26-3
time .......................................................................... 2-13
time constant .......................................................... 17-10
Time module ............................................................ 27-3
time proportional ..................................................... 12-1
time proportional and override ................................ 12-1
Time Proportional and Override Driver (Type 6) 12-11
time proportional driver .......................................... 12-3
Time synchronisation ................................... 19-3, 25-1
Timekeeper ................................ 5-1, 6-7, 25-1, 25-3
Timemaster ................................................... 25-1, 25-4
timer .............................................................. 16-1, 16-5
TIMING PULSES/DAY OF WEEK ...................... 10-9
total time .................................................................. 16-6
Transient alarms ...................................................... 20-1
Transmission Interval .............................................. 14-2
Trend Stencil ........................................................... 2-10
trim ........................................................... 17-24, 17-27
truth table ................................................................. 16-4
type .......................................................................... 22-2
type 4 driver ............................................................ 12-9
type 7 driver ............................................................ 12-9
type identifier ........................................................ 29-22
RW/MK
Trend Control Systems Limited P.O. Box 34 Horsham Sussex RH12 2YF Tel:+44 (0)1403 211888
CONTENTS
All rights reserved. This manual contains proprietary information which 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.
CONTENTS
1. INTRODUCTION
1.1 About the Addendum
1.2 Top Level Prompts
5. SENSOR TYPES
5.1 Mode 0: Linear
5.2 Mode 1: Log
5.3 Mode 2: Linearise thermistor volts
5.4 Mode 3: Linearise volts
5.5 Mode 4: Linearise thermistor ohms
5.6 Mode 5: Characterise
6. MODULE POSITION
6.1 Position Coordinates
6.2 Page Module
6.2.1 page ‘p <page module number> (CR)’
8. AUTODIAL LITE
8.1 Initialisation
8.2 /ADL Default Configuration
8.3 /ADL General Configuration
8.4 Autodialling Modules
8.4.1 Top Menu
13. ARRAYS
13.1 Analogue Array
13.2 Digital Array
A1 APPENDIX - IQ MODULES
INDEX
1. INTRODUCTION
IQ2v3.1 firmware
• Increased Security (Sect. 11)
• IQ1xx Emulation (Sect. 12.7)
IQ2v3 firmware (Addendum version 3)
• Enhanced Alarm Handling (Sect. 2)
• Strategy Cleardown (Sect. 10)
• Autodialling Lite (Sect. 8)
IQ2v2.1 firmware (Addendum version 2)
• Top level prompts (see 1.2 below)
• Function Module Types 19 to 26 (Sect 3)
• Logic Module Types 7 and 8 (Sect 4)
• Sensor Type 5, Characterise (IQ2v2.1) and Types 0 to 4 (IQ2v1) (Sect. 5)
• Text Communications Extensions
• Module Positional Information (x, y, and p coordinates) (Sect. 6)
Addendum version 1
• Display and Directory Modules (IQ2v2) (Sect. 7)
• IQ2 File Format (IQ2v2) (Sect. 9)
• IQ2 Series Updates (IQ2v1) (Sect. 12)
I/O Card Summary
Engineers Journal
Address Module Changes
Sensor Log
Sundries
• IQ251 Extended Array (Sect. 12)
This does not completely update the Configuration Manual (e.g. the Appendix
lists of all IQ types are not updated), but it covers the major changes.
Note that the analogue and digital array upper limits are shown as 255 and
506,7 respectively, whereas for the IQ251 extended arrays, the upper limits
would be 510 and 1012,7 respectively.
Three new prompts have been added for enhanced alarm handling and are
covered in section 3:
Three new prompts have been added to the menu of a controller with autodial
lite functionality (/ADL) and are covered in section 8:
• More than one alarm destination address is supported by the new Alarm
Destination Module
• Alarms from different sources can be grouped together using the new
Alarm Group Module.
• The alarm groups can be linked to the alarm destinations by the new
Alarm Route Module.
• The alarm history database, as used for the old review alarm history log,
has been extended to create a new alarm log. The old review alarm
history still exists as a view on a subset of this database. The extended
alarm log is treated as a number of logged alarm modules and includes
critical alarms and the acknowledge status for each alarm destination.
• The extended alarm log is longer than the old review alarm history; the
length varies to suit each type of IQ.
• Each alarm group module has a digital output which becomes set for one
strategy cycle whenever a new alarm is generated. This would allow
strategy to turn on an alarm annunciator when an alarm occurs.
Enhanced alarm handling applies to item alarms and general alarms, not to
network or critical alarms. However, the extended alarm log collects item,
general, and critical alarms.
The alarm handling is basically achieved by grouping alarms using the alarm
group module, and connecting these alarms to the various alarm destinations
via route modules. The destinations are set up in destination modules.
o 1 e 1 F a ile d b it
g 1 G D O 2 3 /L 2 4 F
P = 5 0 A L A R M
N e w a la r m H D E S T N
A L A R M N E
E n a b le H o ld
G R O U P R O U T E
Group 10 10 10 10 10
Route 50 50 50 50 50
Destination 7 7 7 7 7
The group number is 0 by default and group zero is attached to the primary
alarm destination as set in the Address module [R(A, R), alarm Address and
remote Lan].
This would send read and out of limits alarms via group 1, low alarms via group
3, and high alarms via group 2.
This allows the group used by general alarms (CONL, HELP, FPIA etc) to be
specified by using lower case ‘g’.
The System Engineering Tool (SET) has a special grouping dialogue box
which facilitates the setting up of the alarm groups:
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 zero, so with group zero 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. L1) 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.
When an alarm occurs its source module places it in the extended alarm log,
but also sends details of group number and priority. If the group module is not
linked to a destination, or a single destination is disabled then the alarm is just
logged, but not reported (see section 2.6). The destinations currently linked are
indicated by the Enabled status byte.
The group module contains the following parameters as well as the coordinate
parameters (page, x, y).
The group label ($) is only used to identify the group to facilitate setting up
the alarm handling system.
The Enabled byte shows the current status of links to the destinations where
the extreme right digit refers to prime destination (as set up in address module)
and working to the left through destination module 1 to destination module 7
as the extreme left digit; 0 means link closed, 1 means link open.
The Priority (P) can be set in the range 0 to 255 where 255 is the highest
priority (and is the level given to critical alarms). The priority is checked in the
destination module where alarms of a low priority may be held (e.g. for a
dialled alarm destination). (The priority of an alarm gives additional areas of
development for supervisors where the level could be used for filtering and alarm
display.)
The New alarm (N) output 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.
Range
Select Prompt Type Default Comments
Low High
$ label string 0 20 chars "" e.g. "Maintenance alarms"
(Read only). The state of
links to the destinations
starting from the prime alarm
- Enabled byte OOOOOOOO IIIIIIII OOOOOOOO destination 0 on the RHS,
working left from destination
module 1 through to 7 on
LHS (one bit per destination)
P Priority integer 0 255 0 255 is highest priority
Destination address for new
digital alarm status output. True for
N New alarm 0,0 506,7 0,0
address 1 cycle after new alarm in
group.
p page integer 0 v 0 page number in SET file
x co- ordinate x integer 0 255 0 x co- ordinate on SET page
255
y co- ordinate y integer 0 0 y co- ordinate on SET page
(180 SET)
o 1 o4
g ro u p G D D e s tin a tio n G 0
D 0
E n a b le E E 0,0
SET symbol
R O U T E ALARM ROUTE
o1
G 1
32,1
e1
D 1
F
E 0,0
H 0
ALARM ROUTE
ALARM DEST
R
g1
H O
32,0
L
N
ALARM GROUP o2
G 1
32,2
e2
D 2
F
E 0,0
H 0
ALARM ROUTE
ALARM DEST
o5
R
g4 G 4 e5
D 5 32,3
H O
32,6 F
L E 0,0
N H 0
ALARM GROUP ALARM ROUTE
ALARM DEST
o6
R
g5 G 5
D 5
H O
32,5
L E 0,0
N
ALARM GROUP ALARM ROUTE
The route module has an Enable input 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 destinations to which alarms are routed.
For example, an alternative destination can be used if the first one fails. The
enable input address is set to 0,0 by default which enables the route (the value
of 0,0 is ignored)..
configuration mode prompt
Range
Select Prompt Type Default Comments
Low High
Group
G integer 0 10 0 Source group for alarms
number
Destination Destination module alarms to
D integer 0 7 0
number be sent to
Address of source node for
digital
E Enable input 0,0 506,7 0,0 enable input. 0,0 enables the
address
connection
p page integer 0 v 0 page number in SET file
x co- ordinate x integer 0 255 0 x co- ordinate on SET page
255
y co- ordinate y integer 0 0 y co- ordinate on SET page
(180 SET)
e 1 F a ile d b it e4
32,2
ro u te O 2 3 /L 2 4 F F
A L A R M
H D E S T N
H 0
SET symbol
H o ld ALARM DEST
The alarm destination module enables an alarm destination to be set up. The
linking between route and destination is done in the route module, so that more
than one route can be connected to a destination
The destination label ($) is only used to identify the destination to facilitate
setting up the alarm handling system.
Message format (M) is used to select text, coded, or attribute alarm format
to send to the destination.
The new attribute alarm format contains text comms from the extended alarm
log record (see 2.5).
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)
The destination device is defined by its Alarm address (A) and remote laN
(N) number.
The Hold priority (H) enables a priority level to be set below which alarms
are held. If an alarm comes in above this 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. This parameter is an input so that 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 2.5).
The retry pause Interval (I) sets the pause in minutes between batches of 30
second retries. The interval should be set to zero for autodialling to allow
continual retries at 30 seconds. After an alarm is first sent, if an acknowledge
is not received, the alarm will be retried as follows:
• Retry 5 times at 30 second intervals (i.e. a total of 6 times before the wait)
• Wait for configured retry pause interval
• Retry 6 times at 30 second intervals
• Set Failed output bit
• Repeat retry pause, and 6 retries until one acknowledge is received
• Clear Failed output bit
The Failed digital output bit (F) can be used amongst other things to switch
route modules to send alarms to alternative destinations as mentioned above
in 2.3. The destination module can only hold one alarm, and the Failed bit is
set when the destination device fails to acknowledge the receipt of the alarm
after several retries (see interval above). Once the device starts acknowledging
alarms, the failed bit will be cleared, and the destination module can send
another alarm.
The inhibit cLear alarms parameter (L) stops clear alarms being sent to the
destination device. If the parameter is 0, clear alarms will be sent, if set to 1,
they will be inhibited.
The review alarm history, (V), is a view onto the most recent 20 entries of this
database and still operates as before (e.g. V20 will return the most recent
alarm). However, since critical alarms are now included in the log they are now
also included in the review alarm history.
Once the log is full, when a new alarm is added to the log, the oldest alarm will
roll off the other end, however unlike the old log, the alarm will be lost whether
or not it has been acknowledged. 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 retrying its delivery - see section 2.6)
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 being sent (active), or is complete (i.e. acknowledged by the
destination(s) required at the time). The Acknowledged states byte shows to
which destination modules the alarm was successfully sent. Once the alarm is
complete, this byte will indicate all the destinations to which the alarm was
sent.
Each record in the extended log contains the information available in the review
alarm history, plus additional information:
• It contains the value or status of the module causing the alarm.
• The time stamp includes seconds.
• It contains new features associated with the enhanced alarm handling: alarm
group number, priority, acknowledged states, and alarm status.
The extended alarm log is designed so that its database can be queried using
text comms.
If any routes are enabled, the alarm will be sent to all the routed destination
modules 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, 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 sent are set true, the alarm status is set to completed,
and no further attempts to send the alarm will be made.
It should be understood that the destination module can only hold one alarm,
and if its receipt by the target device is not being acknowledged, it is effectively
blocked until the acknowledge is received.
!
'(
% # &'()(
"* &)& &+ &)& &+ &)& &+
, "
$%
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.
!
'%
% #
"* &)& &+ &)& &+ &)& &+ & *
*
" !
#! +(
, " $
>) "
$ ! !
?)
$% "
)
! "
! <=
>@
?@
@
@
o1
R G 1
32,1
g1 e1
D 1
H O
32,0 F
L E 0,0
N H 0
ALARM GROUP ALARM ROUTE
ALARM DEST
o2
G 1
32,2
e2
D 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.
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 enables all the alarms to be sent to another destination as well as
to the primary alarm address (as set in the address module). It relies on the fact
that all alarms are by default included in group zero which is always sent to the
primary alarm address; group zero may also be a source for a route module
which allows it to be connected to another destination.
The route module source group can be set to group zero in configuration mode.
In SET, the group module is normally linked to the route module by drawing
a link, but group zero cannot be placed on the page for the link to be made; so
as the default source group for a route module is group zero, the route module
can either be left at default, or can have an existing link deleted to return it to
group zero.
The failed output of the alarm destination module is set to 37,0 which is associated
with Critical Alarm 1. This critical alarm module is set up to send the critical
alarm ‘BMS Supervisor Not Responding’ to an alternative address.
%
! "
,(
,B
,% <
XC&IY
C'ZV
&&QW
&
% %
" !
! $
,B
V'&$CVQ) "
J&KQ)Q
)
&
"
!
$
<J)&
*
&
! " !
'( $
#!
% # &'()(
"* &)& &+ &)& &+ &)& &+ "
$ICVC&CWJ')
, "
$%
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.
V()C)C&*
%
%
"
!
!
V'&$CVQ)
)C)C&*
-&
$ "
!
= #!
'(
% # Y' CJW
"* &)& &+ &)& &+ &)& &+ "@$XY'=@
, "
$%
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.
L O O K U P LOOKUP - 1
The table may have up to 20 points and is set up in a sensor type module whose
scaling mode is set to 5, “characterise” (see section 5.6), 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).
4240
4230
4220
4210
Heat Cap (J/Kg K)
SPECIFIC
4200 HEAT CAP
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)
Graph showing the variation of the specific heat capacity of water with temperature
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 19, lookup
S Scaling 1 v sensor type module providing lookup table
G source G 0 255 address of analogue input
D Dest 0 255 address of analogue destination
p page 1 v page number in SET file
x co- ordinate x 0 255 x co- ordinate on SET page
255
y co- ordinate y 0 y co- ordinate on SET page
(180 SET)
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 20, adder D = E + F + G + H
Source E, either
S 0 255
E analogue Source Address of analogue input or constant
C or Constant value (real number)
Source F, either
S 0 255
F analogue Source Address of analogue input or constant
C or Constant value (real number)
G source G 0 255 address of analogue input
H source H 0 255 address of analogue input
D Dest 0 255 address of analogue destination
p page 1 v page number in SET file
x co- ordinate x 0 255 x co- ordinate on SET page
255
y co- ordinate y 0 y co- ordinate on SET page
(180 SET)
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:
HIGH F F1
G D
LOW E HYST LH
If the high level is set below the low level, the module becomes an oscillator
with a period of twice the cycle time.
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 21, hysteresis low E high F
Source E, either
S 0 255 Address of analogue input or constant
E analogue Source
which provides low level
C or Constant value (real number)
Source F, either
S 0 255 Address of analogue input or constant
F analogue Source
which provides high level
C or Constant value (real number)
G source G 0 255 address of analogue input
D Dest 0,0 506,7 address of digital destination
p page 1 v page number in SET file
x co- ordinate x 0 255 x co- ordinate on SET page
255
y co- ordinate y 0 y co- ordinate on SET page
(180 SET)
Note that the previous hysteresis module, type 17, is now referred to as
“Hysteresis Level E Band F”.
SET symbol
2
G F1 E 0 F1
141,0
LEVEL E D G 0 D
BAND F HYST LB F 0 HYST BAND
SET symbol 2
G F1 E 0 F1
141,0
LEVEL E D G 0 D
MAX DIFF F PROX F 0 PROXIMITY
E +/- F
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 22, proximity level E error F
Source E, either Address of analogue input or constant
S 0 255
E analogue Source which provides level with which input is
C or Constant value (real number) compared
F1 F1
NUMBER E E 0 101
EF D
D F 0
INDEX F POWER POWER
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
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 23, power : D = E^ F
Source E, either Address of analogue input or constant
S 0 255
E analogue Source which provides the number to be multplied
C or Constant value (real number) by itself
SET symbol 2
Where G = input
F1
D = output
F1
101
G D G 0 D
ABS
ABS
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 24, absolute : D = ABS G
G Source G 0 255 address of analogue input
D Dest 0 255 address of analogue destination
p page 1 v page number in SET file
x co- ordinate x 0 255 x co- ordinate on SET page
255
y co- ordinate y 0 y co- ordinate on SET page
(180 SET)
or if G = -23.468, D = -23
SET symbol 2
F1 F1
101
G D G 0 D
TRUNC TRUNC
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 25, truncate : D = TRUNC G
G Source G 0 255 address of analogue input
D Dest 0 255 address of analogue destination
p page 1 v page number in SET file
x co- ordinate x 0 255 x co- ordinate on SET page
255
y co- ordinate y 0 y co- ordinate on SET page
(180 SET)
Where G = input
D = output
The function module has a sub type parameter which Sub type Trig function selected
selects the particular trig function as follows: 0 Sine
The function will treat the input as degrees of rotation 1 Cosine
if the R toggle is set to degrees (default) and as radians 2 Tangent
if the R toggle is set to radians.
e.g if G = 90, R set to degrees, and sub type = 0 (sine), then D = 1 (i.e. Sine
90°)
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 26, trigonometry
Type of trigonometric function
0, D = SIN G
S Sub type 0 2
1, D = COS G
2, D = TAN G
G Source G 0 255 address of analogue input
switches between degrees or radians
R degRees/Radians - -
(default is degrees)
D Dest 0 255 address of analogue destination
p page 1 v page number in SET file
x co- ordinate x 0 255 x co- ordinate on SET page
255
y co- ordinate y 0 y co- ordinate on SET page
(180 SET)
Thus for an adder, the effect of setting one of the inputs to address zero will add
zero to the output, i.e. it will have no effect on the output value
A function module with an analogue destination address zero will send its value
to that address.
A function module with a digital source address of 0,0 (e.g. analogue gate, type
14) will read the status of digital bit 0,0 and use it.
A function module with a digital output address of 0,0 will send its output status
to that address.
Function modules types 19, 20, 23, 24, 25, 26, (i.e. all new function modules
with analogue ouputs). The alarm bits on the inputs used are OR’ed together.
Function modules type 21, 22 (i.e. all new function modules with digital outputs).
The alarm bits are ignored.
G 1 K G1 0,0
K
S L
1
0,0
M
S 0,0
L
N 0,0
F A N O FAN OUT M
0,0
Invert Disabled
N
write ‘I’ here, if inverted 0,0
O
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.
Ouputs not being used should be set to address 0,0 (set by default).
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
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 7, fan out
S Source 0,0 506,7 address of digital input bit
0 = logic not inverted
I Inverted 0 1
1 = logic inverted
J destination J 0,0 506,7 address of digital output bit
K destination K 0,0 506,7 address of digital output bit
L destination L 0,0 506,7 address of digital output bit
M destination M 0,0 506,7 address of digital output bit
N destination N 0,0 506,7 address of digital output bit
O destination O 0,0 506,7 address of digital output bit
p page 1 v page number in SET file
x co- ordinate x 0 255 x co- ordinate on SET page
255
y co- ordinate y 0 y co- ordinate on SET page
(180 SET)
4.2 Type 8: D to A
The D to A module converts up to 8 digital bits into one analogue value.
SET symbol
3
E E 0,0 G2
F G1 F 0,0
G G 0,0
H H 0,0 94
D D
I I 0,0
J J 0,0
K K 0,0
L D to A L 0,0 D TO A
Each input bit has a binary weighting so that the complete set of 8 digital inputs
is treated as a binary number (E=Bit 0, through to L= Bit 7), and the output D
is the analogue value of this binary number. This gives a unique analogue value
for every input combination.
Thus if inputs E, H, and J are set to 1 and the others set to zero,
E + H + J = Bit 0 + Bit 3 + Bit 5 = 1 + 8 + 32 = 41
i.e binary 10010100 = 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 plant status.
Heating E
Cooling F
Boost G
H S2
I D I
J
K
L 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 S2 whch
can be logged. A example graph is shown below.
Range
Select Prompt Comments
Low High
Monitor only. Sequence table step(s)
- at step(s) - - which are used by this module (up to 5
steps) or next free steps (up to 4)
Y tYpe 8, d to a
digital source
E 0,0 506,7 address of digital input bit 0 (value 1)
address E
digital source
F 0,0 506,7 address of digital input bit 1 (value 2)
address F
digital source
G 0,0 506,7 address of digital input bit 2 (value 4)
address G
digital source
H 0,0 506,7 address of digital input bit 3 (value 8)
address H
digital source
I 0,0 506,7 address of digital input bit 4 (value 16)
address I
digital source
J 0,0 506,7 address of digital input bit 5 (value 32)
address J
digital source
K 0,0 506,7 address of digital input bit 6 (value 64)
address K
digital source
L 0,0 506,7 address of digital input bit 7 (value 128)
address L
analogue
D 0 255 address of analogue output
Destination address
p page 1 v page number in SET file
x co- ordinate x 0 255 x co- ordinate on SET page
255
y co- ordinate y 0 y co- ordinate on SET page
(180 SET)
A logic module with an analogue destination address zero will send its calculated
value to that address.
A logic module with a digital source address of 0,0 will generally read the
status of digital bit 0,0 and use it. However, type 8, D to A will read input 0,0
as status 0 and thus the input will contribute nothing to the output.
A logic module with a digital output address of 0,0 will send its output status
to that address.
5. SENSOR TYPES
The IQ Series 2 firmware is inherently more accurate at thermistor temperature
measurement than IQ Series 1 as it measures both the reference voltage and the
voltage developed across the thermistor, and using a 0.1% bridge resistor then
calculates the thermistor resistance. The input channel linking (where appropriate)
must be set accordingly (i.e. T, thermistor; V, voltage; I, current; D, digital).
The IQ2v2.1 firmware has the following 6 sensor scaling modes. Earlier firmware
versions have less as shown in brackets:
The numbers of sensor type modules in the IQ range have changed in IQ2v2.1
firmware:
IQ IQ21x IQ22x IQ241/242 IQ246 IQ251
Number 5 10 15 15 20
Note that mode 2/mode 3 must be selected according to the input link header setting as
the scaling varies slightly with link position; so if linked for T (thermistor), mode 2 must
be selected, and if linked for I or V (current or voltage) non-linear sensors, mode 3 must
be selected.
Sensor Scaling
110
100
90
80
70
Z
60
50
Temperature °C
40
30Y
20
W
10
L K
0
O N M
V
-10
-20
U
-30
-40
0 20000 40000 60000 80000 100000 120000 140000 160000 180000
Ohms
The graph shows the temperature characteristic for a thermistor sensor. If the
sensor is to be used for temperature range -30 °C to +60 °C, then this defines
points U, K and Z, O. The other three points have now to be chosen.
The gradient changes most rapidly over the ‘knee’ of the characteristic therefore
around this area the points should be close together. The points are found by
drawing four straight lines, approximating as closely as possible to the curve.
Each of these lines should provide a best fit straight line approximation to the
curve segment. The actual point values should be obtained from a table rather
that a graph, for greater accuracy. The table for the above graph gives the
following points for the -30 °C to +60 °C example.
°C kΩ
U -30 K 177.00
V -10 L 55.34
W 10 M 19.98
Y 30 N 8.06
Z 60 O 2.49
The outside limit alarms are generated if the sensor reading goes outside the U
to Z range by greater than 10 %
The table may have between 2 to 20 points which must be entered in the ascending
order of the input. The number of points is specified by parameter P.
Scaling mode 5, characterise, may not only be used by sensor modules, but
may also be used by lookup function modules (see section 3.1). The lookup
function module has a Scaling parameter in its configuration table which cross-
references a sensor type module. If used by a function module the sensor type
module must have its Scaling mode set to 5, characterise, and its input tYpe
(see below) set to 4, analogue value. If the function module cross-references
a sensor type module which is not set to mode 5, the output is set to 0.
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.
Input type 4 (analogue value) is used when the type module is referenced by
a lookup function module (see section 3.1).
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.
Example 9 point table Graph of 9 point table
1 0.916 90 100
2 1.751 70
80
3 3.602 50
60
4 5.326 40
O - Output
5 8.058 30 40 O
6 12.49 20
20
7 19.9 10
0
8 32.66 0 0 20 40 60
Range
Select Prompt Comments
Low High
scaling mode:
0: Linear
1: Log
S Scaling 0 5 2: Linearise thermistor volts
3: Linearise volts
4: Linearise ohms
5: Characterise
Scaling mode 0: Line ar Scaling
select from table as shown in IQ
E Exponent -7 +7
configuration manual section 22.7
corresponds to value at prescribed voltage
T Top of range - 9,999,999 9,999,999 level for particular IQ for voltage sensor,
and value at +20 mA for current sensor
corresponds to value at prescribed voltage
B Bottom of range - 9,999,999 9,999,999 level for particular IQ for voltage sensor,
and value at - 20 mA for current sensor
sensor working range upper limit, sensor
dependent on outside limits alarm bit set at or above this
U sensor Upper
exponent set value (e.g. value at +20 mA for 4 to 20
mA current sensor)
sensor working range lower limit, sensor
dependent on outside limits alarm bit set at or below this
L sensor Lower
exponent set value (e.g. value at +4 mA for 4 to 20 mA
current sensor)
Scaling mode 1: Log Scaling
select from table as shown in IQ
E Exponent -7 +7
configuration manual section 22.7
T Top of range - 9,999,999 9,999,999 corresponds to value at +5 volts
B Bottom of range - 9,999,999 9,999,999 corresponds to value at +1 volt
sensor working range upper limit, sensor
dependent on
U sensor Upper outside limits alarm bit set at or above this
exponent set
value
sensor working range lower limit, sensor
dependent on
L sensor Lower outside limits alarm bit set at or below this
exponent set
value
Range
Select Prompt Comments
Low High
Scaling mode 2: Line aris e the rmis tor volts
T Top of range 0 327 sensor value at top of range
B Bottom of range 0 - 327 sensor value at bottom of range
F 0 10 voltage at bottom of range
G 0 10 voltage at bottom plus 25% of range
H 0 10 voltage at bottom plus 50% of range
I 0 10 voltage at bottom plus 75% of range
J 0 10 voltage at top of range
Scaling mode 3: Line aris e volts
The configuration mode settings are exactly the same as for scaling mode 2
Scaling mode 4: Line aris e the rmis tor ohms
the values of the sensor in its units (e.g.
U, V, temperature, °C) at the 5 points on the
W, Y, units real number characteristic corresponding to the
Z resistances (in kohms) of the sensor
entered as K, L, M, N, O respectively
the resistance values of the sensor in
K, L, kohms at the 5 points on the characteristic
M, N, kohms real number corresponding to the values (in its units
O e.g. temperature, °C) of the sensor
entered as U, V, W, Y, Z respectively
real number
Note that scaling modes 2, 3, and 4 (linearise thermistor volts, linearise volts, and
linearise thermistor ohms) do not have a configurable exponent; these scaling types
function as if the exponent were set to 3.
Range
Select Prompt Comments
Low High
Scaling mode 5: Characte ris e
the type of scaling required:
0 - volts (V)
1 - thermistor volts (V)
Y input tYpe 0 4 2 - current (mA)
3 - kohms (thermistor)
4 - analogue value (for use with function
module)
this will not appear for input type 4
(analogue value)
E Exponent -7 +7
select from table as shown in IQ
Configuration Manual section 22.7
0 (unused). Points range is 2 to 20
P Points used 0 20
Number of points on characteristic used
n = 1 to P the value of the sensor/input in the units
In Input n (above) selected by the input tYpe for each point
real number on the characteristic used
6. MODULE POSITION
IQ2v2.1 firmware (or greater) is able to record module positional and page
information as set up by the system engineering tool (SET). When strategies
are created using SET the strategy is set out on screen pages which can be
printed as strategy diagrams. This information is downloaded to the controller
as part of the strategy so that the strategy may be later uploaded into SET and
viewed on screen and printed in its original layout.
Modules which are not shown on strategy pages and hence do not have
coordinates are:
sensor types, sequence table steps, analogue nodes, digital nodes, time module,
user modules, address module, calendars, display modules, directory modules,
page modules.
Note that analogue and digital nodes are shown on the page if they are sources
or destinations of the printable 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 p coordinate defines the SET page number on which the module is shown.
It can be set in the range 0 to 255 where 0 effectively means the module is not
shown on a page, and page 1 is reserved for the SET header page so it is not
a valid page coordinate. The maximum page module in the controller varies
with IQ type, so although 255 is the configuration maximum, if the page is to
have a label and be part of a hierarchical structure, the p coordinate value
should not exceed the number of page modules in that controller type. A list
of the number of page modules in each controller type is shown below (see 6.2)
The coordinates are automatically produced by SET and hence do not normally
need to be changed in configuration mode. However, they may be viewed and
edited in configuration mode. Thus modules added to a strategy using
configuration mode may be positioned manually so that they appear in the
correct page when the uploaded strategy is imported into SET.
Range
Select Prompt Comments
Low High
$ label 0 20 characters long label for page module
P paRent 0 v not currently used; for future use
7.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).
e.g.
@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
This structure shows two directory modules (using the configuration mode
selection character “@”), i.e. @2, @3, which give the second level of hierarchy
i.e. the next level below directory 1.
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
Technical Note
This hierarchy can easily be obtained by a supervisor such as the NDP
which can send a message to all directory modules whose paRent is non-
zero, requesting label and paRent,
e.g. @/{R>0}($,R)
NDP
7.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.
e.g.
~1
display 1 Item S1
paRent 2 PIN 50
This will put Sensor 1 (e.g. “Outside Temperature”) on the directory 2 view level.
Technical Note
A supervisor like the NDP can ask the IQ controller for all display modules
attached to a directory module. So if the ‘Boilers’ (i.e. @2) had been
selected as described in section 2 above, then the supervisor could send a
text comms message:
~/{R=2}(I)
e.g.
NDP
Main Plant
- Albery House
-Boilers
Main Plant - Boilers
|- Boiler 1 1
- Boiler
- Boiler
|- Boiler 2 2
- VT- VT Circuit
Circuit
Flow Temp 81.36 degC
S1 attached Return
OutsideTempTemp 65.27
81.36 degC
Flow
Return Setpoint
Temp 82.00
65.27 degC
deg C
to @2
Hours Run
Flow Setpoint 16.12
82.00 hrs
degC
Boiler
HoursOveride
Run OFF
16.12 hrs
ESC
So when a user logs on to the supervisor and selects display modules he will
only see the pieces of plant and items appropriate to his level.
The numbers of directory modules for each controller type are as follows:
The numbers of display modules for each controller type are as follows:
8. AUTODIAL LITE
Some IQ2 series controllers incorporate the autodial lite (/ADL) functionality.
This allows the IQ to communicate via an autodialling modem. It is especially
useful for separated buildings which can be monitored and supervised via the
modem. The IQ2 with the /ADL functionality and one other controller on its
local Lan (e.g. Trend access controller) can communicate via the modem.
The modem is connected to the /ADL controller’s local supervisor port. This
means that with the modem directly connected, the controller can only be
configured either from the local Lan or from an autodialled Lan via the modem
8.1 Initialisation
The /ADL system must first be configured so that a supervisor can dial up and
communicate with the unit via the modem; any further configuration can then
be done via the modem or locally if required.
Required Configuration:
IQ address switch: set in range 11 to 117 (e.g. 16)
Default factory settings (also restored by strategy clear down):
supervisor port address: address switch + 1 (e.g. 17)
Record module proxy port: address switch + 1 (e.g. 17)
Link network connection via ‘loop back’ connector if controller stand-alone.
Set address of second accessible controller to be IQ address switch + 2; range
13 to 119 (e.g. 18).
Subsidiary Configuration:
A supervisor or software tool can now be used to dial into the /ADL controller
via the modem or to connect locally (in place of the modem, or on the local Lan)
and to configure the following:
Address module, Alarm address: set to record module proxy port address
(e.g. 17) to allow controller to send alarms via modem.
Record module, (the following parameters also allow controller to send alarms
via modem)
Address: set to supervisor address on its Lan
Lan: set to supervisor Lan number
Telephone number: set to telephone number of modem being used by supervisor
Autodial module, own telephone number: must be set to the IQ modem’s
telephone number if sending alarms to a supervisor (e.g. 945, 962).
The supervisor can now communicate with the controller and [controller address
+ 2], and the 2 controllers will send their alarms to the supervisor.
C o n t r o lle r 's S e c o n d S u p e r v is o r
C N C C N C T e le p h o n e N u m b e r S u p e r v is o r A d d r e s s
Modem CNC
Trend network Network linked
if stand-alone
The record module holds the dialling information and the proxy port address.
The controllers can send their alarms to the proxy port address on the local Lan;
the real supervisor device address, Lan number, and telephone number, are
added to the message, and then sent to the modem enabling it to dial out to the
supervisor.
The zero address/baud rate switch reset or null file strategy cleardown will
cause the firmware to restore both the supervisor port address and proxy port to
the factory defaults of address switch setting + 1 (unless adress switch is less than
11 in which case it is set to 200. This will enable the supervisor dialling in to talk
to the two controllers over the network, and for the controllers to send alarms
to the supervisor via the proxy port.
Using these defaults, communications via the modem use the network, so a
loop-back network connector should be fitted to the network connection for a
stand-alone controller.
To enable the /ADL controller to dial out alarms via the modem, both the Alarm
address (in the address module) and the record module should be set up. This
can be done via the supervisor over the PSTN link (or locally connected
supervisor if required). The user should configure the alarm address to be the
same as proxy port address and should also configure the address, Lan number,
and telephone number of the alarm target supervisor in the record module.
To enable the second controller at [switch address + 2] to dial out alarms via
the modem, its alarm address must be set up to be the same as proxy port
address.
With the modem connected, the autodialled supervisor can only talk to the two
designated controllers, but the /ADL controller can use IC Comms to
communicate to or from other controllers not directly accessible to the supervisor
enabling the sharing of information across the whole system. Note that Inter-
Controller Communications cannot be used to communicate via the modem.
C o n t r o lle r 's S e c o n d
C N C C N C
local supervisor port
The /ADL firmware will detect that a local supervisor is connected; the local
supervisor can communicate with all devices on the local network rather than
the two controllers to which modem communications are restricted. All local
Lan devices can report alarms to the local supervisor via the supervisor port
address.
If the supervisor is replaced by the modem, the /ADL firmware will detect this,
and re-initialise the modem by sending it the character string set up in the
modem module. It will also reinstate the two controller communication
restriction.
The top menu has an additional fifth line to show the generally accessible
/ADL modules:
sUpervisor port addr: This set equal to the address switch setting plus one by
factory default and strategy cleardown, (however, if the address switch is less
than 11, on cleardown it will be set to address 20).
Alarm addr: This is the destination address of the controller alarms. It is set
up as normal. However, if set to 2 alarms are sent directly to supervisor port
which can be either modem or local supervisor device. If modem is connected,
the record module proxy port address would also have to be set to 2 to enable
alarms to be sent via the modem.
To send alarms via modem the alarm address should be set to record module
proxy port address, i.e. address switch + 1 for default configuration.
AUTODIAL MODULE
own Tele 01403226369
Auto-dial password 0
last connection 01403226318
autodial status Modem detected
(Quit, eXit)
own Tele: (up to 29 characters) The phone number string for this outstation
should be entered here. This phone number is passed to the remote TMN and
can be used by a supervisor for group identification (e.g. alarm recognition and
acknowledgment).
Note that own Tele must be set up if sending alarms to a 945 supervisor
otherwise the alarms are not acknowledged which may result in large telephone
charges. The 962 uses the phone number to identify the source Lan number.
Auto-dial password: A 4 digit PIN used for validation of connections via the
modem. Setting the password to zero disables password checking. Required to
be connected to TMN V4.0 or greater to operate correctly. The PIN will only
be displayed if the user is logged on with a high enough controller password
(User module).
If the telephone fails due to Security Fail (password mismatch), an override
password may be obtained as described in the Autodialling Reference Manual;
however, note that this procedure can only be performed from the TMN side
of the connection (i.e. only the TMN shows a default generator number).
last connection: (up to 32 characters) This read-only field shows the telephone
number of the last incoming call that connected successfully, or the last number
dialled.
autodial status: (up to 48 characters) This read-only field shows the current
modem status:
“Local PC mode”
“Looking for modem”
“Idle”
“No dial tone”
“Local modem fault”
“Dialling”
“No answer far site”
“Link-Fail”
“Security Fail”
“Connected”
“Local modem ringing”
Note that this status may also be shown on the 2-line display panel (see 2-line
Display Panel, below)
RECORD 1
proxy Port 17
addR 9
LaN 1
Tele 01403226318
(Quit, eXit)
proxy Port: Communications sent to this address are delivered to the modem
using the address, Lan, and telephone number set within the record. This should
be set to the supervisor port address; the factory default and the zero address/
baud rate switch reset or the null strategy file download set both proxy port and
supervisor port address to address switch plus one; however, if the address
switch is less than 11, on reset they will be set to address 20. If the controller
alarms are being sent to address 2 (local supervisor), the proxy port address
should also be set to 2.
addR: This is the destination Trend network device (e.g. supervisor) address.
Selected by ‘l’ (note lower case ‘L’) from the top prompt.
DELAYLIST
atmpts time to (secs) ... tele
next attempt reset
2 100 6341 01403226318
(Quit, eXit, (z)ero)
time to next attempt: The number of seconds remaining before a new dial out
attempt may be made.
time to reset: The number of seconds remaining in the two hour reset period.
(When count reaches zero, delay list is reset - see below.)
zero delay list: (“z” lower case) A command to clear the delay list (see below).
The controller enters the destination telephone number into the delay list after
the first unsuccessful dial out attempt. The delays are as follows:
After attempt 1: 30 seconds (alarm retry delay)
After attempts 2 to 6: 2 min. each
After attempt 7: 2 hours from attempt 1 then reset delay list
The delay list is also reset by controller reset, or by successful connection to
the destination.
Selected by ‘m’ (note lower case) from the top prompt. This module is not
indicated in the top prompt.
MODEM
Modem init string (1) ATH&F
moDem init string (2) ATS0=1
modem Version request ATI3
modem version reported V1.7
(Quit, eXit)
Modem init string (1): (up to 24 characters) This is sent to the modem whenever
it is re-initialised. Set by default to “ATH&F” (do not change).
moDem init string (2): (up to 24 characters) This is sent to the modem after
init string (1). Set by default to “ATS0=1” (do not change).
[Note that changing the string to “ATS0=0”, causes the modem to ignore
incoming calls, and only to use the modem to dial out (i.e. to report alarms);
this enables it to share an existing line.]
modem version reported: This read-only string is sent by the modem to the
controller in response to the version request described above.
Note that an IQ2v2 controller will accept a download of a strategy file in the
old (.IQF) format; see section 9.4.
SET can be used to create a strategy file (IQ2) which can then be downloaded
to the controller and can be uploaded for backup purposes if connected to the
controller directly or via the network. PowerTool can be used to upload and
download IQ2 files if connected via a modem. However, when PowerTool
uploads an .IQ2 format file it gives it an IQF extension. 822+/Toolbox will only
download .IQ2 format files if their extension is changed to .IQF, and like
PowerTool it will upload them as .IQF files.
The .IQ2 file contains all strategy modules and the display panel settings; logs
(alarm logs, sensor logs), and engineers journal are not included.
9.3. Upload/Download
The upload/download protocol is exactly the same as that for the .IQF files,
thus existing updown tools can upload/download IQ2 files.
Start Config
File Header
default
C:\......\L104N04.IQF
IQ210.Iss2.03 Jan 21 1999
29/10/99 15.18.07
Downloading 29/10/99 15.18.07 (menu rail gives count-up as packets downloaded)
LOAD OK
Start Config
Uploading :L104N041.IQF (menu rail gives count as packets uploaded)
Saved...
9.4 Compatibility
The following table shows a compatibility matrix.
TO
From
IQ1 IQ2v1 IQ2v2
IQ1 .IQF .IQF .IQF
IQ2v1 N/A .IQF .IQF
IQ2v2 N/A N/A .IQ2
Thus IQ2v2 will accept a download of .IQF or .IQ2 format files but will only
respond to an upload request with an .IQ2 format file.
An engineer can then use various methods to clear down the strategy to an
empty (null) state. More recent versions of IQ are able to automatically clear
down the strategy.
The strategy file contains a checksum. After the download, the checksum is
recalculated, and if different from the checksum contained in the file, it assumes
corruption during transmission. If the download is not completed, the controller
will time out. In either case, it will clear down the strategy again, send “Load
ER” message to the downloading device (e.g. software tool), and put the
controller into a HELP condition.
The required strategy file, or a null file, can be downloaded to clear a help
condition (due to loss of data because of battery failure, battery replacement,
firmware upgrade, or an unsuccessful strategy file download). Note that after
a power interruption with battery failure, the time, date and day of week will
need to be synchronised (e.g. automatically by timemaster system) for the
strategy to operate correctly.
10.3 Power Up
10.3.1 Traditional Operation (IQ1 and IQ2 Series pre IQ2v3)
This condition causes the controller enter a checksum error (HELP) condition
which stops the strategy running.
On power down, the controller writes the checksum into memory and sets the
two byte checksum flag to the ‘checksum calculated’ state.
On power up the controller checks the checksum flag for the following states:
Checksum calculated
If the checksum flag is set to checksum calculated state, the controller will
recalculate the checksum and compare it against the checksum in memory.
This check results on one of two states:
Checksum error
If the two are different, it assumes a loss of some strategy data during
power fail (i.e. due to battery failure) and sets a checksum error (HELP)
condition which stops the strategy running.
Checksum OK
If the checksum is correct, it will set the checksum flag to the ‘checksum
checked’ state, enter a checksum OK condition, and start the strategy
running.
10.5.1 HELP
The HELP condition is generated when the unit powers up and detects a loss
of strategy data, or after a null or unsuccessful strategy file download. It indicates
that the controller requires its strategy to be configured (e.g. strategy file
download). The controller will not run the strategy, and text comms will not
operate; however, the controller will respond in configuration mode.
If the address module alarm address is set up then the HELP alarm will be sent
to the appropriate address; however, a loss of data often means that the alarm
addresses are not valid.
If the memory is corrupted the user PIN may have changed and hence a download
may not be permitted (see 10.6 below).
If the IQ2v3 controller has cleared down the strategy due to a checksum flag
invalid state, the user PIN will be nulled and a download enabled. The address
module ID and attributes will be set up as described in 10.3.2, and the controller
will be placed in a Checksum OK condition..
10.5.2 Checksum OK
The Checksum OK condition is generated when the unit powers up and detects
a valid strategy, after a firmware upgrade, after a successful strategy file
download, or after a soft reset. (Soft resets are caused by general alarm conditions
- FPIA, FRAM, FDRT.)
It generally means that the controller has restarted and is running a valid
strategy. After a firmware upgrade the strategy file will be a null file.
If the address module alarm address is set up, then a CONL (Controller On
Line) alarm will be sent to the appropriate address; however, it will not be set
up in a null strategy, and hence a null strategy will not send alarms.
A default PIN may be obtained from Trend Technical Support. This can then
be used to permit the download. The engineer will need to view the controller’s
address module in configuration mode.
IQ2v3 controllers will clear down the strategy after a checksum flag invalid
state is detected, and hence the PINs will be cleared down, and strategy file
downloads permitted.
This is performed by setting the address/baud rate switch to all zeros while
power is switched off, and then powering up. The controller detects that the
switches have been changed from a non-zero setting to an all zero setting and
will clear down the strategy, and enter a checksum OK condition.
The zero address/baud rate switch reset can be used to clear down the strategy
after a loss of strategy data (e.g. due to battery failure), and is normally
recommended as part of the battery replacement procedure for controllers
earlier than IQ2v3 (see 10.8).
The IQ251 controller has a battery status bit (byte 506 bit 0) which is set to one
if the controller detects the battery voltage has fallen below a threshold level
on power up and thereafter every midnight. This bit should be used to generate
a critical alarm.
This can be used to force a HELP condition in order to stop the controller
controlling the plant and to freeze the outputs.
If the controller is in a HELP condition, entry of lower case ‘e’ will toggle it
back to checksum OK state and will cause it to resume controlling the plant.
This is a very risky procedure as strategy data could have been lost, and
the plant could be damaged by running the strategy. It is recommended
that downloading a valid strategy file should be used to reset the HELP
condition.
In IQ2 v3.1 or greater, a default pin disable parameter is present in the address
module. Setting the disable parameter to one will disable the default PIN. The
default PIN disable parmeter can only be changed if a user is logged on via a
PIN with security level of 99.
ADDRESSES
Once the default pin disable parameter is set on, changes can only be made by
valid PINs, and the default PIN disable parameter can only be changed by a
user PIN of level 99.
If the default PIN is disabled and the PIN settings are unknown (e.g. PINs
forgotten, or after backup battery replacement), the unit can be restored by
clearing the strategy using the zero address/baud rate switch reset (see section
10.6) and then downloading the strategy.
Note that this procedure does not present a security risk because the controller
must be physically accessed and the power removed; this would generate a
network alarm and so can be detected.
Normally address 120 is not used, but if set will act like address zero and allow
the supervisor to communicate only with the local IQ. On IQ2v3.1 or greater
address 120 will disable the local supervisor port; there is no longer any local
access either to the IQ or the network.
The port can be enabled by setting the address to another value by configuration
mode or by text communications (R(U)).
sUperv port addr: This is the network address of the second CNC built-in to
the firmware. It is used by the local supervisor port for access to the local Lan.
This facility is not included in the IQ21x.
It can take the normal range of addresses on the local Lan as long as an address
is not duplicated. If set to address zero the supervisor port will only communicate
with its own IQ.
An IQ with /ADL functionality will have the supervisor address set non-zero
both by factory default and after a strategy cleardown (see section 8)
ndp pOrt addr: This is the network address of the third CNC built-in to the
firmware. It is fitted so that the second CNC can be used for a local supervisor,
and the third CNC can be used for an NDP, and that they both have access to
the network. It follows the same rules as the local supervisor port above. This
facility is only included in the IQ251, and IQ241/242
Supply frequency: If the unit is mains powered the problem of mains pick-up
is dealt with automatically by the firmware, and the measured mains frequency
is displayed.
Selecting Y displays:
0 - - - auto
1 - - - 50 Hz
2 - - - 60 Hz
This enables the user to select the local mains frequency used for 24 Vdc
controllers in order that it may reject mains hum. It will default to 50 Hz for dc
version and auto for the ac version.
(g)eneral alarm group: This is the alarm group to which the general alarms
(e.g. HELP, CONL, FPIA etc.) belong (IQ2v3 only - see section 2).
Loader Issue: This displays the issue and date of the download kernel that is
in the controller.
e.g. Loader iss 1.1.c Jul 10 1997.
It can be accessed with text comms using ‘R(c)’ (‘c’ must be lower case).
Serial number: This is factory set to the serial number on the main board. It
can be accessed with text comms using ‘R(s)’ (‘s’ must be lower case).
Identity: The configuration mode display shows the IQ controller type, prom
issue, and date:
e.g. IQ210 Iss 1.2d Sep 30 1997.
The IQ version can be accessed by text comms using ‘R(C)’ (‘C’ is upper case).
The IQ2xx will identify itself (e.g. to the 945 and NDP) as an ‘IQ2xxv1’. This
is so that early versions of these programs can operate with the IQ2.
If an IQ2 has a second or third CNC (see ‘superv port addr’, ‘ndp port addr’
above) and it recieves an identify request addressed to the port, it will identify
the attached device; if a device is not connected it will identify the port as a
CNC
e.g. IQ210
Channels 1 to 2 :Thermistor Inputs
Channel 3 :Universal Inputs
Channels 4 to 5 :Digital Inputs
Channels 6 to 7 :Voltage Outputs
Channels 8 to 11 :Digital Outputs
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
Although the IQ2 series controllers have 1000 values per logging channel,
some Trend display panel and supervisor/tool applications can only accept the
first 96 values of logs using 1 minute, 15 minute, 1 hour, and 24 hour time
intervals. This is shown in the table below.
All 921, 822, 942, 943, NDP, A c c e s s f i r s t 9 6 va l u e s o f 1
pre Issue 2.2, and 945 pre m i nu t e, 1 5 m i nu t e, 1 h o u r
Issue 2.0. and 24 hour logs.
A c c e s s a l l va l u e s f r o m a l l
945 Issue 2.0.
logs except 1 s.
Access first 96 values from
NDP 2.20 or later
all logs.
Not all Trend display panels, and supervisor/tool applications can set up or
change logging channels for the extended time bases. This is summarised in the
table below.
Can edit existing channels, and
set up new ones using 1
minute, 15 minute, 1 hour and
All 921, 822, 942, 943,
24 hour time inter vals unless
and 945 pre Issue 2.0.
any channel has been set up
using 1 second, 5 minute, and 6
hour time inter val.
Can edit existing channels, and
945 Issue 2.0. set up new ones using all time
inter vals except 1s.
Set up in configuration mode
962
only
PowerTool Set up using module viewer
The IQ251 has a channel reference such as AA1 where the first letter signifies
board position (A to H), the second letter signifies Analogue, A or Digital, D,
(outputs don’t have a second letter), and then the number is the connection
number on the board.
The other IQs have connection numbers as shown on the label (e.g. IQ241 or
242 connections 1 to 40).
Sensor n in n
S n analogue node n
internal digital ID
mode
Internal digital input n
n
In IQ2xx controllers the sensor in internal digital mode writes only to the node
corresponding to its sensor number, not to the corresponding digital input
node. If it is required that the sensor’s corresponding digital input node should
reflect the internal digital node, a logic module can be used to connect the
internal digital node to the digital input node (see also 12.7.1).
Note that the proviso that the digital input node must be for an internal digital
input still applies.
Internal digital node E G1
Internal digital input n
F E
G
n
HCOMB
Sensor n in n
internal digital Sn analogue node n
ID
mode
For IQ1xx controllers the default PIN was accurate to ±5, so that each number
in the range ±5 had to be tried until one worked. For IQ2xx controllers the
default PIN is accurate
The user PIN is used in text communications which involve changing values
in the receiving controller(s). This includes IC Comms (global to, and data to-
bit only), and text communications from supervisors. The header to the text
communication message must carry a PIN which matches a PIN set up in a user
module in the receiving controller, and this PIN must be of a sufficient authority
level in the receiving controller for the change to be made.
The PIN level sent with the message must be greater than or equal to the levels
given in the following table.
Knob or
Time and Zone Times Zone Times Holiday Holiday Other
Switch
date Current week Standard week date time parameter
value
As defined
in
Data to knob/switch
50 30 50 50 70 95
module
As defined
Global in
knob/switch
50 30 50 50 70 99
to
module
For IC Comms the User 1 PIN is sent with the message by the initiating controller,
so this must be of sufficient authority in the receiving controller. In the case of
the 822+/Toolbox and NDPv3, the password can be entered by the user and
then automatically sent at the front of any text communications message and
in any upload or download message.
As explained above in 12.5.6, IQ1xx and IQ2xx controllers treat internal digital
sensor outputs differently
In IQ2v3.1, in IQ204 and IQ23x only, Bit 506,1 is used to set IQ1xx Emulation
in an IQ2xx controller; the IQ2xx will treat such internal digital sensor outputs
in the same way as IQ1xx controllers.
Bit 506.1 should be set to 1 if an IQ1xx strategy using the internal digital sensor
output to a internal digital input feature is downloaded to an IQ2x controller.
It will then cause the sensor module to operate in the same way as IQ1xx
controllers. Setting the bit to zero restores IQ2xx mode.
13. ARRAYS
Because of the large number of I/O channels in the IQ251 it has extended
digital and analogue arrays.
* If function modules use digital outputs, they use bit 0 of corresponding alarm
byte in digital array (by convention).
Function modules with digital outputs (types 15 and 17) are allocated by
convention to use bit 0 of alarm byte for their normal analogue output node
[e.g. F1 would use alarm byte for A101 i.e. B141(0), F121 will use B647(0)].
TEXT/NEW ALARM
Alarm
Text Flag:
1= TEXT ON (Alarms sent as text)
2= TEXT OFF (Alarms sent coded)
Also alarm bit for Analogue Node 255
New Alarm: New alarm added to alarm log; true for one
sequence cycle.
Note that Byte 506 bit 0 is used to indicate battery failure, and is only functional on the
IQ251.
Bit
0 1 2 3 4 5 6 7
byte
506 FBAT IQ1xx
Emuln
FBAT: Bit=1 Battery failed, Bit=0 Battery OK
Battery voltage fallen below threshold, replace battery.
IQ1xx Emulation: Bit =1 Emulation on, Bit =0 Emulation off
(see section 12.7)
Note that Byte 506 bit 1 is used to enable IQ1xx emulation (IQ2v3.1 firmware).
DIGITAL INPUTS
508 I57 I58 I59 I60 I61 I62 I63 I64
509 I65 I66 I67 I68 I69 I70 I71 I72
510 I73 I74 I75 I76 I77 I78 I79 I80
511 I81 I82 I83 I84 I85 I86 I87 I88
512 I89 I90 I91 I92 I93 I94 I95 I96
513 49 50 51 52 53 54 55 56
DIGITAL OUTPUTS
514 57 58 59 60 61 62 63 64
515 65 66 67 68 69 70 71 72
516 73 74 75 76 77 78 79 80
517 81 82 83 84 85 86 87 88
518 89 90 91 92 93 94 95 96
519
520
FREE
521
522
523
524 W21 W22 W23 W24 W25 W26 W27 W28
SWITCHES
525 W29 W30 W31 W32 W33 W34 W35 W36
526 W37 W38 W39 W40 W41 W42 W43 W44
527 W45 W46 W47 W48 W49 W50 W51 W52
528 W53 W54 W55 W56 W57 W58 W59 W60
529
530
FREE
531
532
533
534 G161 G162 G163 G164 G165 G166 G167 G168
Allocated by convention
545
546
547 256 579 288 611 320 643 352 675 384 707 416 739 448 771 480
548 257 580 289 612 321 644 353 676 385 708 417 740 449 772 481
549 258 581 290 613 322 645 354 677 386 709 418 741 450 773 482
550 259 582 291 614 323 646 355 678 387 710 419 742 451 774 483
551 260 583 292 615 324 647 356 679 388 711 420 743 452 775 484
552 261 584 293 616 325 648 357 680 389 712 421 744 453 776 485
553 262 585 294 617 326 649 358 681 390 713 422 745 454 777 486
554 263 586 295 618 327 650 359 682 391 714 423 746 455 778 487
555 264 587 296 619 328 651 360 683 392 715 424 747 456 779 488
556 265 588 297 620 329 652 361 684 393 716 425 748 457 780 489
557 266 589 298 621 330 653 362 685 394 717 426 749 458 781 490
558 267 590 299 622 331 654 363 686 395 718 427 750 459 782 491
559 268 591 300 623 332 655 364 687 396 719 428 751 460 783 492
560 269 592 301 624 333 656 365 688 397 720 429 752 461 784 493
561 270 593 302 625 334 657 366 689 398 721 430 753 462 785 494
562 271 594 303 626 335 658 367 690 399 722 431 754 463 786 495
563 272 595 304 627 336 659 368 691 400 723 432 755 464 787 496
564 273 596 305 628 337 660 369 692 401 724 433 756 465 788 497
565 274 597 306 629 338 661 370 693 402 725 434 757 466 789 498
566 275 598 307 630 339 662 371 694 403 726 435 758 467 790 499
567 276 599 308 631 340 663 372 695 404 727 436 759 468 791 500
568 277 600 309 632 341 664 373 696 405 728 437 760 469 792 501
569 278 601 310 633 342 665 374 697 406 729 438 761 470 793 502
570 279 602 311 634 343 666 375 698 407 730 439 762 471 794 503
571 280 603 312 635 344 667 376 699 408 731 440 763 472 795 504
572 281 604 313 636 345 668 377 700 409 732 441 764 473 796 505
573 282 605 314 637 346 669 378 701 410 733 442 765 474 797 506
574 283 606 315 638 347 670 379 702 411 734 443 766 475 798 507
575 284 607 316 639 348 671 380 703 412 735 444 767 476 799 508
576 285 608 317 640 349 672 381 704 413 736 445 768 477 800 509
577 286 609 318 641 350 673 382 705 414 737 446 769 478 801 510
578 287 610 319 642 351 674 383 706 415 738 447 770 479
BYTES 547-801
BIT 5 SET (1): Analogue node used to store a digital value (value can
only be 0 or 1).
BIT 0: DIGIN - used to indicate a digital input alarm on
digital source.
BIT 5 CLEAR (0): Analogue node used to store an analogue value. Bits 0-
4 indicate analogue alarms on analogue source.
BIT 0: HIGH: Sensor High Alarm
BIT 1: LOW: Sensor Low Alarm
BIT 2: OSL: Sensor Outside Limits (limits High, Low, set
in tYpe).
BIT 3: READ: Sensor outside input channel range.
BIT 4: LOOPFAIL TYPE 2: Loop output to default level,
non automatic recovery.
BIT 0 (Bytes 647 to 766): By convention these are used for outputs by Function
modules F121 to F240 if they are types 15,17 (i.e. have
digital outputs). (This is alarm byte of normal analogue
output node).
DRIVER ALARMS
811 D49 D50 6
812 D51 D52 7
813 D53 D54
814 D55 D56
815 D57 D58
816 D59 D60
817 D61 D62
818 D63 D64
RDBK :Readback alarm: driver output differs from plant
feedback (after grace time elapsed) normally generated by
Readback Logic Module.
MINT:Maintenance Inter val: plant has been running for longer
than maintenance inter val, normally generated by Hours Run
Logic Module.
819
FREE
820
876
877
878
879
880
881
882
883
884
FREE
968
969
970
971
972
973
974
975
976
977 D33 D34 Bit Alarm Driver
978 D35 D36 0 RDBK ODD
979 D37 D38 1 MINT NOS
DRIVERS ALARMS ENABLED
FREE
1005
1006
1007
1008
1009
1010
1011
1012
G A IN F F 1 1 0 1
2 0 G
F IL T E R E F IL T E R
The note: ‘If E is exactly equal to zero then the division will not take place and
the function will evaluate as D = G x F’ only applies to IQ1 series. For IQ2
series divide by zero enumerates as a very large number 9.9 (recurring) x1037.
3) Function Module Type 1. The alarm bits from the source are transferred
to the output.
Range
Select Prompt Comments
Low High
Last acknowledged alarm status from alarm
alarm
K - - buffer. An alarm is generated when M=/ K
acKnowledge
and N=1 for par ticular alarm bit
A1 APPENDIX - IQ MODULES
The modules available in each IQ are listed below. This is at IQ2v3.1 firmware.
Note that the IQ250 remains at IQ250v8.2b firmware, and the XNC/220, ENC2,
and IQ220/TCL remain at IQ220v1.5 firmware.
XNC220
Module IQ21x IQ22x IQ23x IQ241/242 IQ246 IQ250 IQ251 IQ22x/TCL
ENC2
Sensor 12 32 48 48 48 48 96 32 32
Critical Alarm 4 4 4 4 4 4 4 4 4
Sensor Type 5 10 15 15 15 12 20 8 8
Alarm History 20 20 20 20 20 20 20 20 20
Loop 6 16 32 32 32 32 32 16 16
IC Comms 4 16 16 16 16 16 16 16 16
Function 40 90 160 160 160 160 240 90 90
Digital Inputs 12 32 48 48 48 48 96 32 32
Logic 40 90 160 160 160 160 240 90 90
Fast Sequence 8 8 8 8 8 8 8 8 8
Driver 8 12 32 32 32 32 64 12 12
Zone 5 5 5 5 5 5 5 5 5
Knob 10 30 30 30 30 30 60 30 30
Schedule 4 8 32 32 32 32 32 8 8
Switch 10 20 20 20 20 20 60 20 20
Calendar 20 20 20 20 20 20 20 20 20
Sensor Log (plot) 10 20 32 32 32 40 96 20 20
User Password 6 6 6 6 6 6 6 6 6
Sequence Step 100 240 400 400 400 400 560 240 240
Sequence Time 1s 1s 1s 1s 1s 5s 1s 1s 1s
Analogue Nodes 255 255 255 255 255 255 510 255 255
Digital Nodes 506 506 506 506 506 506 1012 505 505
Display 60 140 200 200 200 0 400 0 0
Directory 10 25 40 40 40 0 80 0 0
Page 15 30 50 50 50 0 80 0 0
Group 10 10 10 10 10 0 10 0 0
Route 50 50 50 50 50 0 50 0 0
Destination 7 7 7 7 7 0 7 0 0
New Alarm Log 40 100 200 200 200 0 300 0 0
INDEX
acknowledge bits ................................. 8-2, 10-1
Symbols acknowledge status ......................................... 6-3
acknowledged states byte ....... AD2-11, AD2-14
& ..................... 5-3, 29-4, 29-19, 29-21, 29-35
actuators ....................................................... 12-2
* .......................... 5-3, 14-6, 29-1, 29-4, 29-35
Add ............................................................... 13-1
+ ..................................................... 29-24, 29-36
Adder ........................................................ AD3-3
. .................................................. 5-4, 14-6, 29-4
Adder/Scaler ................................................. 13-8
.IQ2 ............................. AD9-1, AD9-3, AD10-1
addr ........................................................... AD8-7
.IQF ........................................... AD9-3, AD10-1
addr switch ..................................................... 5-6
.IQF files ..................................... AD9-1, AD9-2
address ........................................... 29-24, 29-36
/ADL ......................................... AD8-1, AD12-1
address 120 ............................................. AD11-2
< ......................................... 29-19, 29-24, 29-36
address field ................................................ 29-24
= .................................................................. 29-19
Address Module .................. 5-1, 27-3, AD8-5,
> ................................ 3-4, 29-19, 29-24, 29-36
AD11-1, AD12-1
? .................................... 5-4, 14-6, 29-4, 29-35
address switch .......................... AD8-1, AD10-5
@ .............................................................. AD7-1
address zero ............................................ AD12-1
| ............ 5-3, 14-6, 29-4, 29-19, 29-21, 29-35
address/baud switch ................ AD8-2, AD8-7,
~ ................................................................ AD7-3
AD10-5, AD10-6
1 (*) ............................................................ 29-18
Addresses ........................................................ 5-6
2-line display panel .................. AD8-7, AD8-10
Adjustment Id ............................................... 15-1
24 Vdc Supply ............................................. A1-9
Adjustment mode ......................... 15-2, AD14-3
2DP ........................................... AD8-7, AD8-10
adjustments ................................................... 15-1
2RM .............................................................. 12-8
Alarm .............................................................. 6-8
3RM .............................................................. 12-8
alarm acknowledged status .................... AD14-2
4DIX ........................................................... 13-14
alarm address ... 2-12, 5-1, 5-2, 5-6, 6-1, 6-9,
822 ......................... 2-12, 27-2, 29-20, AD12-5
7-1, AD8-1, AD8-4, AD8-5, AD10-4
822 Utility ...................................................... 3-6
alarm bits .................................... 13-14, AD3-14
822+/Toolbox ........ 2-3, 29-18, AD9-1, AD9-2
alarm buffer .................................................. 20-1
921 .......................................................... AD12-5
Alarm Buffer Empty ..................................... 20-2
942 .......................................................... AD12-5
alarm bytes ........................................ 10-1, 21-2
943 .......................................................... AD12-5
alarm delay ................................ 6-2, 11-2, 22-3
945 ............................ AD8-1, AD12-2, AD12-5
Alarm Destination Module ......... AD2-1, AD2-2
962 .............................. AD8-1, AD8-6, AD12-5
alarm dial out .............................. AD8-2, AD8-9
A alarm enable ................................................... 6-3
alarm generation ............................................. 6-2
a raise/lower relay module .......................... 12-11 Alarm Group Module. .............................. AD2-1
a secondary process .................................... 17-21 alarm group number ................................. AD2-2
absolute ................................................... AD3-10 alarm history buffer ..................... 6-1, 6-2, 20-1
absolute addressing ...................................... 29-1 alarm priority ............................................ AD2-5
access controller ....................................... AD8-1 Alarm Route Module .................. AD2-1, AD2-2
Accessory Module ..................................... A1-10 alarm states ................................................... 10-1
Accuracy on Input Channels ....................... A1-5 alarm status ..................................................... 3-5
ACK ................................................................ 6-2 alarm status byte ................................ 8-2, 17-29
Trend Control Systems Limited P.O. Box 34 Horsham Sussex RH12 2YF Tel:+44 (0)1403 211888 Fax:+44 (0)1403 241608 www.trend-controls.com