IQSET Manual V7.60

IQSET Manual
Applies to v7.60 software

Author: Trend Technical Publications
Issue: 25
Date: 03-Feb-2020
Part Number: TE200147
Copyright: ©2019 Honeywell Products and Solutions SARL, Connected Building Division
This manual contains proprietary information that is protected by copyright. No part of this manual may be
reproduced, transcribed, stored in a retrieval system, translated into any language or computer language, or transmitted
in any form whatsoever without the prior consent of the publisher.
Manufactured for and on behalf of the Connected Building Division of Honeywell Products and Solutions SARL, ZA,
La Pièce, 16, 1180 Rolle, Switzerland by its Authorized Representative, Trend Control Systems Limited.
For information contact:
Trend Control Systems Limited
St. Marks Court
North Street,
Horsham
West Sussex
RH12 1BW
UK.
NOTICE: Trend Control Systems Limited makes no representations or warranties of any kind whatsoever with respect
to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular
purpose. Trend Control Systems Limited shall not be liable for any errors contained herein or for incidental or
consequential damages in connection with the furnishing, performance or use of this material. Trend Control Systems
Limited reserves the right to revise this publication from time to time and make changes in the content hereof without
obligation to notify any person of such revisions or changes.
Windows is a trademark of Microsoft Corporation. BACnet is a trademark of ASHRAE. The Java Runtime
Environment (JRE) is a product of Sun Microsystems, Inc.
Please send any comments on this or any other Trend technical publication to techpubs@trendcontrols.com.
Table of Contents
TABLE OF CONTENTS
1 ABOUT THIS MANUAL ............................................................................................................................... 15

1.1 Conventions Used in this Manual .............................................................................................................. 15
1.2 Contacting Trend........................................................................................................................................ 16
2 WHAT'S NEW IN VERSION V7.60............................................................................................................. 17
3 ABOUT IQSET ............................................................................................................................................... 19

3.1 The IQSET Window .................................................................................................................................. 20
3.1.1 Display Area ................................................................................................................................... 20
3.1.2 Item Selector ................................................................................................................................... 20
3.1.3 Menu Bar ........................................................................................................................................ 20
3.1.4 Project View ................................................................................................................................... 20
3.1.5 Search Library................................................................................................................................. 21
3.1.6 Status Bar ........................................................................................................................................ 21
3.1.7 Strategy Library .............................................................................................................................. 22
3.1.8 System View ................................................................................................................................... 23
3.1.9 Toolbars .......................................................................................................................................... 26
4 INSTALLATION ............................................................................................................................................ 27
4.1 Install IQSET ............................................................................................................................................. 27
4.1.1 Install the Software ......................................................................................................................... 27
4.1.2 License IQSET ................................................................................................................................ 28
4.1.3 Set up Users .................................................................................................................................... 30
4.1.4 Install the BACnet Network Driver ................................................................................................ 32
4.1.5 Install the USB Driver .................................................................................................................... 33
4.1.6 Install the LCI/USB Driver ............................................................................................................. 34
4.1.7 Customise IQSET ........................................................................................................................... 35
4.1.8 Connect to the IQ Network ............................................................................................................. 35
4.1.9 Connect to the BACnet Network .................................................................................................... 35
4.2 Transfer the Licence to a Different Location ............................................................................................. 35
5 SECURING IQSET ........................................................................................................................................ 37

5.1 Security Checklist ...................................................................................................................................... 37
5.2 Developing a Security Program ................................................................................................................. 37
5.3 Disaster Recovery Planning ....................................................................................................................... 37
5.4 Physical and Environmental Consideration ............................................................................................... 37
5.5 Security Updates and Service Packs .......................................................................................................... 37
5.6 Virus Protection ......................................................................................................................................... 37
5.7 Network Planning and Security.................................................................................................................. 37
5.8 Virtual Environments ................................................................................................................................. 38
5.9 Securing Wireless Devices ......................................................................................................................... 38
5.10 System Monitoring ..................................................................................................................................... 38
5.11 Windows Domains ..................................................................................................................................... 38
5.12 Securing Access to the Operating System .................................................................................................. 38
5.13 Security Features ........................................................................................................................................ 38
6 CUSTOMISE IQSET ..................................................................................................................................... 39

6.1 Configure Security Options ........................................................................................................................ 39
6.2 Enable/Disable the Controller and Identifier Check .................................................................................. 40
6.3 Enable/Disable the Controller Time/Date Check ....................................................................................... 41
6.4 Enable/Disable the Strategy Sync Check ................................................................................................... 42
6.5 Enable/Disable Background Compare ....................................................................................................... 43
6.6 Set up Default Labels ................................................................................................................................. 44
6.7 Set up the Sensor Library ........................................................................................................................... 46
6.7.1 Delete a Sensor Definition from the Library ................................................................................... 48
6.7.2 Edit a Sensor Definition .................................................................................................................. 49
6.8 Set up the Strategy Library ........................................................................................................................ 49
6.8.1 Set up Strategy Blocks .................................................................................................................... 50
IQSET Manual TE200147 Issue 25 : 03-Feb-2020 3

Table of Contents
6.8.2 Set up Solutions .............................................................................................................................. 60
6.8.3 Import Strategy Blocks and Solutions ............................................................................................ 62
6.9 Set up the States Category Library ............................................................................................................. 64
6.10 Specify Auto Edit ....................................................................................................................................... 65
6.11 Specify Company Information ................................................................................................................... 66
6.12 Specify File Backup Options...................................................................................................................... 68
6.13 Specify Module Tracking ........................................................................................................................... 69
6.14 Specify IQSET's Default Language ........................................................................................................... 70
6.15 Specify Standard Comms Connections ...................................................................................................... 71
6.15.1 Delete a Standard Comms Connection ........................................................................................... 72
6.15.2 Edit a Standard Comms Connection ............................................................................................... 72
6.16 Specify the Default Comms Connection .................................................................................................... 73
6.17 Specify the Default Controller for New Controllers .................................................................................. 74
6.18 Specify the Default Display Language ....................................................................................................... 75
6.19 Specify the Default Display Options .......................................................................................................... 76
6.20 Specify the Default Print Options .............................................................................................................. 77
6.21 Specify the Gap in the Sequence Table Between Pages ............................................................................. 78
6.22 Specify the Time Difference ...................................................................................................................... 79
6.23 Specify the Toolbar Theme ........................................................................................................................ 79
6.24 Specify IQ3 or IQ4 Directory Module Parameter Defaults ........................................................................ 80
6.25 Specify IQ3 or IQ4 Display Module Parameter Defaults........................................................................... 81
6.26 Specify the Loading and Saving of Site Data ............................................................................................. 82
6.27 Specify the Printer ...................................................................................................................................... 83
6.28 Specify the Priority Array Labels ............................................................................................................... 83
6.29 Specify the Refresh Options ....................................................................................................................... 84
6.30 Specify Where Strategy Blocks are Stored ................................................................................................ 85
6.31 Specify Where Projects are Stored ............................................................................................................. 86
6.32 Specify Module Prompts ............................................................................................................................ 87
6.33 Specify Whether the Tracker Window Displayed ...................................................................................... 87
6.34 Specify Which Toolbars Are Displayed ..................................................................................................... 88
6.35 Translate Print Labels ................................................................................................................................ 88
6.35.1 Import Translated Print Labels ....................................................................................................... 90
6.35.2 Export Translated Print Labels ....................................................................................................... 91
6.36 Turn Auto Routing ON/OFF ...................................................................................................................... 92
6.37 Turn Module Tool Tips ON/OFF ............................................................................................................... 93
6.38 Turn Tip of the Day ON/OFF .................................................................................................................... 93
7 QUICK TOURS .............................................................................................................................................. 95

7.1 Quick Tour 1 - The Basics ......................................................................................................................... 95
7.1.1 Lesson 1 - Starting IQSET .............................................................................................................. 96
7.1.2 Lesson 1 - Creating a New IQSET Project ..................................................................................... 96
7.1.3 Lesson 1 - Understanding the SET Window ................................................................................... 97
7.1.4 Lesson 2 - Adding a LAN ............................................................................................................... 98
7.1.5 Lesson 2 - Adding an IQ Controller ................................................................................................ 99
7.1.6 Lesson 2 - Setting Up the Address Module .................................................................................. 101
7.1.7 Lesson 2 - Setting Up the Ethernet IP Module ............................................................................. 102
7.1.8 Lesson 2 - Setting Up the Sensor Type Modules .......................................................................... 103
7.1.9 Lesson 3 - Adding Modules to the Strategy .................................................................................. 104
7.1.10 Lesson 3 - Moving Modules ......................................................................................................... 106
7.1.11 Lesson 3 - Editing Modules .......................................................................................................... 106
7.1.12 Lesson 3 - Linking Modules ......................................................................................................... 108
7.1.13 Lesson 3 - Adding Pages ............................................................................................................... 109
7.1.14 Lesson 4 - Defining the Strategy's Issue ....................................................................................... 110
7.1.15 Lesson 4 - Print Project Documentation ....................................................................................... 111
7.1.16 Lesson 5 - Creating an IQ4 File .................................................................................................... 111
7.2 Quick Tour 2 - Beyond Basics ................................................................................................................. 112
7.2.1 Lesson 1 - Loading an Existing Project ........................................................................................ 113
7.2.2 Lesson 1 - Linking Between Pages ............................................................................................... 115
7.2.3 Lesson 1 - Linking to a Specific Value ......................................................................................... 116
7.2.4 Lesson 2 - Adding Text to a Page ................................................................................................. 117
4 IQSET Manual TE200147 Issue 25 03-Feb-2020

Table of Contents
7.2.5 Lesson 2 - Using To Connectives ................................................................................................. 117
7.2.6 Lesson 3 - Principles of Display and Directory Modules ............................................................. 118
7.2.7 Lesson 3 - Adding Directory Modules .......................................................................................... 118
7.2.8 Lesson 3 - Adding Dynamic Display Modules ............................................................................. 119
7.2.9 Lesson 3 - Adding Static Display Modules ................................................................................... 120
7.2.10 Lesson 3 - Setting up Graphical Display Pages (Backdrops) ........................................................ 121
7.2.11 Lesson 3 - Setting up Graphical Display Pages (Moving Items) .................................................. 122
7.2.12 Lesson 3 - Setting up Graphical Display Pages (Linking Pages) .................................................. 123
7.2.13 Lesson 4 - Changing a Module's Sequence Step ........................................................................... 124
7.2.14 Lesson 4 - Event Driven Strategy ................................................................................................. 125
7.2.15 Lesson 5 - Principles of Using Strategy Blocks ............................................................................ 125
7.2.16 Lesson 5 - Using Strategy Blocks ................................................................................................. 126
7.3 Quick Tour 3 - Making IQSET Work for You ......................................................................................... 127
7.3.1 Lesson 1 - What is Backwards Engineering? ................................................................................ 127
7.3.2 Lesson 1 - Uploading the Strategy in the Required Format .......................................................... 128
7.3.3 Lesson 1 - Importing an IQ4 File .................................................................................................. 128
7.3.4 Lesson 2 - Principles of Strategy Blocks ...................................................................................... 128
7.3.5 Lesson 2 - Creating a Strategy Block ............................................................................................ 129
7.3.6 Lesson 3 - Adding a Sensor Definition to the Library .................................................................. 131
7.3.7 Lesson 4 - The Command Line Toolbar ....................................................................................... 132
7.3.8 Lesson 4 - Using the Command Line Toolbar to Find Modules ................................................... 132
7.3.9 Lesson 4 - Using the Command Line Toolbar to Add Modules ................................................... 133
7.3.10 Lesson 5 - Comparing Two Strategies .......................................................................................... 133
8 CREATE A BTL COMPLIANT STRATEGY .......................................................................................... 135
9 ENGINEER IQ CONTROLLERS .............................................................................................................. 137

9.1 Plan the System ........................................................................................................................................ 137
9.2 Specify the IQSET Project ....................................................................................................................... 137
9.2.1 Create a Project ............................................................................................................................. 138
9.2.2 Open a Project ............................................................................................................................... 139
9.2.3 Import a Project ............................................................................................................................ 139
9.2.4 Edit Project Details ....................................................................................................................... 140
9.2.5 Delete a IQSET Project ................................................................................................................. 140
9.2.6 Set up the Project's Default Remote Devices ................................................................................ 141
9.3 Create the Controllers .............................................................................................................................. 142
9.3.1 Add Controllers Manually ............................................................................................................ 142
9.3.2 Add Controllers Using Solutions .................................................................................................. 146
9.3.3 Add Controllers by Copying ......................................................................................................... 149
9.3.4 Add Controllers by Importing Files .............................................................................................. 150
9.3.5 Add Controllers Using Project Config .......................................................................................... 151
9.3.6 Delete a Controller ........................................................................................................................ 155
9.3.7 Edit a Controller............................................................................................................................ 155
9.3.8 Add a LAN.................................................................................................................................... 156
9.4 Configure Controller Strategy .................................................................................................................. 158
9.4.1 Configure an IQ4 Controller ......................................................................................................... 158
9.4.2 Configure an IQ3 Controller ......................................................................................................... 159
9.4.3 Configure an IQECO Controller ................................................................................................... 160
9.4.4 Configure a Pre IQ3 Controller ..................................................................................................... 160
9.4.5 Configure a Fixed Strategy Controller .......................................................................................... 161
9.4.6 Set up the Address Module ........................................................................................................... 163
9.4.7 Set up Network Configuration ...................................................................................................... 167
9.4.8 Configure the IQ LAN Network Module ...................................................................................... 168
9.4.9 Set up the Ethernet IP Module ...................................................................................................... 168
9.4.10 Set up the BACnet Network Module ............................................................................................ 172
9.4.11 Set up the BACnet IP Network Module ........................................................................................ 173
9.4.12 Set up the BACnet Application Network Module ........................................................................ 174
9.4.13 Set up the BACnet MSTP Network Module ................................................................................. 176
9.4.14 Set up Sensor Type Modules ........................................................................................................ 178
9.4.15 Add a States Category Module ..................................................................................................... 180
IQSET Manual TE200147 Issue 25 03-Feb-2020 5

Table of Contents
9.4.16 Set up an Interface Network Module ............................................................................................ 182
9.4.17 Set up a Type 2 (Wallbus) Interface Module ................................................................................ 184
9.4.18 Set up a Type 3 (Modbus) Interface Module ................................................................................ 186
9.4.19 Set up a Type 4 (M-bus) Interface Module ................................................................................... 188
9.4.20 Configure ADL Support ............................................................................................................... 189
9.4.21 Configure XNC Support for IQ2 Controllers ................................................................................ 191
9.4.22 Set up the XNC Interface Module................................................................................................. 193
9.4.23 Add Modules to a Strategy Page ................................................................................................... 197
9.4.24 Move Modules .............................................................................................................................. 201
9.4.25 Link the Modules .......................................................................................................................... 201
9.4.26 Set up the Alarm Handling Strategy ............................................................................................. 204
9.4.27 Add an I/O Module ....................................................................................................................... 210
9.4.28 Set up a Controller for Use with an External Display ................................................................... 211
9.4.29 Assign I/O Channels ..................................................................................................................... 212
9.4.30 Edit Modules ................................................................................................................................. 214
9.4.31 Set up the Sequence Table ............................................................................................................ 218
9.4.32 Set up Event Driven Strategy ........................................................................................................ 220
9.4.33 Set up Fast Sequencing ................................................................................................................. 220
9.4.34 Set up the Controller's Normal Occupation Time Profile ............................................................. 221
9.4.35 Set up Calendar Modules .............................................................................................................. 227
9.4.36 Set up Exceptions .......................................................................................................................... 229
9.4.37 Configure IC Comms .................................................................................................................... 237
9.4.38 Set up Controller Security ............................................................................................................. 249
9.4.39 Set up CNC User Modules ............................................................................................................ 254
9.4.40 Set up vCNC Modules .................................................................................................................. 254
9.4.41 Set up Display and Directory Modules ......................................................................................... 256
9.4.42 Set up Graphical Display Pages .................................................................................................... 276
9.5 Add Graphics and Text to Strategy Pages ................................................................................................ 277
9.5.1 Add Graphics to a Strategy Page .................................................................................................. 277
9.5.2 Add Text to Strategy Pages ........................................................................................................... 278
9.5.3 Delete Text and Graphics from a Strategy Page ........................................................................... 278
9.5.4 Move Text and Lines on a Strategy Page ...................................................................................... 278
9.6 Test the Strategy....................................................................................................................................... 278
9.6.1 Test the Strategy Using Simulation Mode .................................................................................... 278
9.7 Download the Strategy ............................................................................................................................. 280
9.8 Issue Project Documentation .................................................................................................................... 284
9.8.1 Define a Strategy's Issue ............................................................................................................... 284
9.8.2 Specify the Notes Printed on the Front Page ................................................................................ 285
9.8.3 Print Project Overview .................................................................................................................. 285
9.8.4 Print Project Documentation ......................................................................................................... 286
9.9 Backup the Project ................................................................................................................................... 287
10 IQ INTERFACING ...................................................................................................................................... 289
11 COMPARING STRATEGIES..................................................................................................................... 291

11.1 Compare Single Strategies ....................................................................................................................... 291
11.2 Compare Multiple Strategies .................................................................................................................... 293
11.3 Resolve NTD Differences ........................................................................................................................ 294
11.4 Restore a Strategy .................................................................................................................................... 296
12 UPDATE A PROJECT ................................................................................................................................. 297
13 COMMISSIONING WITH LIVE VALUES .............................................................................................. 299
14 LIVE EDITING ............................................................................................................................................ 301

14.1 Live Editing Mode ................................................................................................................................... 301
14.2 Live Adjustment Mode ............................................................................................................................ 304
15 EXPORT STRATEGY FOR CUSTOM ORDERING .............................................................................. 307
16 GENERAL OPERATIONS ......................................................................................................................... 309

Table of Contents
16.1 Add a Connective ..................................................................................................................................... 309
16.2 Add a Connective to Alarm Status Information ....................................................................................... 310
16.3 Add a Connective to System Information ................................................................................................ 311
16.4 Add a Module Using the Command Line Toolbar ................................................................................... 312
16.5 Add a Strategy Page ................................................................................................................................. 314
16.6 Add a To Connective ............................................................................................................................... 314
16.7 Add an IQECO Display Device ............................................................................................................... 315
16.8 Add an Undefined Connective to a Module ............................................................................................. 315
16.9 Add an Undefined Connective to a Node ................................................................................................. 316
16.10 Add System Performance Module Strategy Block ................................................................................... 317
16.11 Add Unplaced Modules to a Strategy Page .............................................................................................. 318
16.12 Authorise a TCL Application ................................................................................................................... 319
16.13 Backup IQ3 Controllers ........................................................................................................................... 320
16.14 Change a Controller's Type ...................................................................................................................... 322
16.15 Change a Node's Value ............................................................................................................................ 323
16.16 Close a Project ......................................................................................................................................... 323
16.17 Close a Strategy Page ............................................................................................................................... 323
16.18 Collect Controller Diagnostic Information ............................................................................................... 323
16.19 Convert Strategy ...................................................................................................................................... 324
16.20 Copy a Strategy Page ............................................................................................................................... 326
16.21 Copy and Paste Modules .......................................................................................................................... 326
16.22 Create a Data File ..................................................................................................................................... 327
16.23 Create Multiple Data Files ....................................................................................................................... 328
16.24 Create Plant Directories ........................................................................................................................... 328
16.25 Define an Undefined Connective's Destination ........................................................................................ 329
16.26 Delete a Connective ................................................................................................................................. 330
16.27 Delete a Link ............................................................................................................................................ 331
16.28 Delete a Plant Directory ........................................................................................................................... 331
16.29 Delete a Strategy Page ............................................................................................................................. 331
16.30 Delete an IQECO Display Device ............................................................................................................ 331
16.31 Delete Modules ........................................................................................................................................ 331
16.32 Disable a Module ..................................................................................................................................... 332
16.33 Display Information about Autodialling Devices..................................................................................... 332
16.34 Display Trend System Communications Information .............................................................................. 333
16.35 Display Keyboard Short Cuts ................................................................................................................... 333
16.36 Display the Item Selector ......................................................................................................................... 333
16.37 Display the Project View ......................................................................................................................... 333
16.38 Display the Strategy Library .................................................................................................................... 334
16.39 Display the System View ......................................................................................................................... 334
16.40 Display the Tracker Window ................................................................................................................... 334
16.41 Display the Tip of the Day ....................................................................................................................... 334
16.42 Dock Panes ............................................................................................................................................... 335
16.43 Download a Single Page of Strategy ........................................................................................................ 335
16.44 Download a TCL Application .................................................................................................................. 337
16.45 Edit an IQECO Display Device ............................................................................................................... 338
16.46 Enter Configuration Mode on Pre IQ3 Controllers .................................................................................. 338
16.47 Export Data to 963 ................................................................................................................................... 339
16.48 Export Data to an EDE File...................................................................................................................... 340
16.49 Export Data to IQVISION ....................................................................................................................... 341
16.50 Export the Project Overview .................................................................................................................... 341
16.51 Export Module Lists ................................................................................................................................. 342
16.52 Find a Module .......................................................................................................................................... 343
16.53 Find Fixed System Nodes ........................................................................................................................ 343
16.54 Find and Replace Labels .......................................................................................................................... 346
16.55 Find Where a Node is Used...................................................................................................................... 347
16.56 Find where a Sequence Step is Used ........................................................................................................ 347
16.57 Go to a Module ........................................................................................................................................ 347
16.58 Go to a Strategy Page ............................................................................................................................... 348
16.59 Import a Backdrop File ............................................................................................................................ 349

Table of Contents
16.60 Log in ....................................................................................................................................................... 349
16.61 Move Panes .............................................................................................................................................. 350
16.62 Perform an IQSET Command Using the Command Line Toolbar .......................................................... 350
16.63 Position the Toolbars................................................................................................................................ 350
16.64 Position the Windows .............................................................................................................................. 351
16.65 Print a Single Page of Strategy ................................................................................................................. 351
16.66 Print Strategy Blocks................................................................................................................................ 351
16.67 Redraw the Screen.................................................................................................................................... 352
16.68 Resize Panes ............................................................................................................................................. 352
16.69 Rename a Plant Directory ........................................................................................................................ 352
16.70 Reset an IQ3 Controller ........................................................................................................................... 352
16.71 Restore Backed Up Data .......................................................................................................................... 353
16.72 Run IQSET ............................................................................................................................................... 354
16.73 Select Modules ......................................................................................................................................... 356
16.74 Set up a PIN ............................................................................................................................................. 356
16.75 Set up Page Details................................................................................................................................... 357
16.76 Set up the Site Codes................................................................................................................................ 357
16.77 Specify the BACnet Write Priority .......................................................................................................... 358
16.78 Specify the Next Module Number ........................................................................................................... 359
16.79 Specify the Position of the Next Window ................................................................................................ 359
16.80 Specify Which Configuration Parameters are Displayed ......................................................................... 359
16.81 Turn the Status Bar ON/OFF ................................................................................................................... 359
16.82 Undo the Last Action ............................................................................................................................... 360
16.83 Use the Connection Wizard...................................................................................................................... 360
16.84 Use the BUA Editor ................................................................................................................................. 363
16.85 Use the TUA Editor ................................................................................................................................. 364
16.86 Upgrade IQ3 Controllers .......................................................................................................................... 367
16.87 Upload Strategy from an IQ Controller .................................................................................................... 369
16.88 View BACnet Communications ............................................................................................................... 372
16.89 View Device Details ................................................................................................................................ 372
16.90 View LAN Details ................................................................................................................................... 373
16.91 View Page Details .................................................................................................................................... 373
16.92 View Project Details ................................................................................................................................ 374
16.93 View Strategy Block Details .................................................................................................................... 374
16.94 View Strategy Block Page Details ........................................................................................................... 374
16.95 View Strategy Issues ................................................................................................................................ 375
16.96 View the Next Module List ...................................................................................................................... 375
16.97 Zoom IN/OUT .......................................................................................................................................... 376
17 BROWSE THE SYSTEM ............................................................................................................................ 377

17.1 Basic Browsing ........................................................................................................................................ 377
17.1.1 Connect to a Network ................................................................................................................... 377
17.1.2 Add Sites to the System View....................................................................................................... 380
17.1.3 Connect to a Site ........................................................................................................................... 386
17.1.4 Navigate the System ..................................................................................................................... 387
17.1.5 Refresh the System View .............................................................................................................. 388
17.1.6 Run an Applet ............................................................................................................................... 388
17.2 Configure an IQL Controller for use with an RD-IQL ............................................................................. 388
17.3 Configure vCNCs ..................................................................................................................................... 390
17.4 Display a List of Objects .......................................................................................................................... 391
17.4.1 Display a List of Device Contents ................................................................................................ 391
17.4.2 Display a List of Devices on a LAN ............................................................................................. 391
17.4.3 Display a List of Internetwork Devices ........................................................................................ 392
17.4.4 Display a List of Module Parameters ............................................................................................ 392
17.4.5 Display a List of Modules ............................................................................................................. 393
17.4.6 Display a List of the Site Content ................................................................................................. 393
17.5 Display Graphs ......................................................................................................................................... 394
17.5.1 Display a Chart ............................................................................................................................. 394
17.5.2 Display a Compact Graph ............................................................................................................. 394
17.5.3 Display a Precision Graph ............................................................................................................ 395

Table of Contents
17.6 Display Properties .................................................................................................................................... 395
17.6.1 Display Device Properties............................................................................................................. 395
17.6.2 Display a Trend Modules Properties ............................................................................................. 396
17.6.3 Display a BACnet Module Properties ........................................................................................... 396
17.6.4 Display Parameter Properties ........................................................................................................ 397
17.6.5 Display Site Properties .................................................................................................................. 398
17.7 Enter Configuration Mode on Pre IQ3 Controllers .................................................................................. 398
17.8 Manage the System View......................................................................................................................... 400
17.8.1 Delete a Site .................................................................................................................................. 400
17.8.2 Edit a Site ...................................................................................................................................... 400
17.8.3 Delete an Object from the System View ....................................................................................... 402
17.8.4 Add a User Node........................................................................................................................... 402
17.9 Map the System ........................................................................................................................................ 404
17.9.1 Display a Logical Map .................................................................................................................. 404
17.9.2 Display a Physical Map ................................................................................................................ 405
17.9.3 Display a System Map .................................................................................................................. 406
17.9.4 Display an Electrical Map ............................................................................................................. 407
17.10 Send a Text Comms Message .................................................................................................................. 408
17.11 Turn a User Node's Refresh ON/OFF ...................................................................................................... 409
17.12 Upload/Download Strategy ...................................................................................................................... 409
17.12.1 Download a Single Strategy to Multiple Controllers .................................................................... 409
17.12.2 Download Different Strategies to Multiple Controllers ................................................................ 413
17.12.3 Download to a Single Controller .................................................................................................. 416
17.12.4 Upload from a Single Controller ................................................................................................... 419
17.12.5 Upload from Multiple Controllers ................................................................................................ 420
17.13 View Alarms ............................................................................................................................................ 423
17.13.1 View Current Alarms .................................................................................................................... 423
17.13.2 View Historic Alarms ................................................................................................................... 424
17.13.3 View Incoming Alarms ................................................................................................................. 424
17.14 View a Controller's Web Pages ................................................................................................................ 424
APPENDICES ......................................................................................................................................................... 425
A1 IQ4 MODULES............................................................................................................................................. 427

A1.1 Common IQ4 Module Parameters............................................................................................................ 429
A1.2 IQ4 Address Modules .............................................................................................................................. 430
A1.2.1 IQ4 Address Module Parameters .................................................................................................. 430
A1.3 IQ4 Alarm Destination Modules .............................................................................................................. 434
A1.3.1 IQ4 BACnet Alarm Destination Modules ..................................................................................... 434
A1.3.2 IQ4 Trend Alarm Destination Modules ........................................................................................ 436
A1.4 IQ4 Alarm Group Modules ...................................................................................................................... 439
A1.4.1 IQ4 Alarm Group Module Parameters .......................................................................................... 439
A1.5 IQ4 Alarm Route Modules ....................................................................................................................... 440
A1.5.1 IQ4 Alarm Route Module Parameters........................................................................................... 440
A1.6 IQ4 Calendar Modules ............................................................................................................................. 441
A1.6.1 IQ4 Calendar Module Parameters ................................................................................................. 441
A1.7 IQ4 Directory Modules ............................................................................................................................ 443
A1.7.1 IQ4 Directory Module Parameters ................................................................................................ 443
A1.8 IQ4 Display Modules ............................................................................................................................... 444
A1.8.1 IQ4 Dynamic Display Modules .................................................................................................... 444
A1.8.2 IQ4 Static Display Modules .......................................................................................................... 446
A1.9 IQ4 Driver Modules ................................................................................................................................. 448
A1.9.1 IQ4 Analogue Driver Modules ..................................................................................................... 448
A1.9.2 IQ4 Binary Hysteresis Driver Modules......................................................................................... 452
A1.9.3 IQ4 Digital Driver Modules .......................................................................................................... 457
A1.9.4 IQ4 Multi Stage Digital Driver Modules ...................................................................................... 462
A1.9.5 IQ4 Raise/Lower Continuous Driver Modules ............................................................................. 471
A1.9.6 IQ4 Raise/Lower End Driver Modules ......................................................................................... 476
A1.9.7 IQ4 Time Proportional Driver Modules ........................................................................................ 482
A1.9.8 IQ4 Time Proportional + O/R Driver Modules ............................................................................. 486

Table of Contents
A1.10 IQ4 Function Modules ............................................................................................................................. 492
A1.10.1 IQ4 ABS Function Modules ......................................................................................................... 493
A1.10.2 IQ4 Add Function Modules .......................................................................................................... 493
A1.10.3 IQ4 Adder/Scaler Function Modules ............................................................................................ 494
A1.10.4 IQ4 Analogue Input Selector Function Modules .......................................................................... 495
A1.10.5 IQ4 Analogue to Digital Function Modules .................................................................................. 496
A1.10.6 IQ4 Average Function Modules .................................................................................................... 498
A1.10.7 IQ4 Comparator Function Modules .............................................................................................. 499
A1.10.8 IQ4 COV Function Modules ......................................................................................................... 499
A1.10.9 IQ4 Differencer Function Modules ............................................................................................... 500
A1.10.10 IQ4 Divide Function Modules ...................................................................................................... 501
A1.10.11 IQ4 Enthalpy Function Modules ................................................................................................... 502
A1.10.12 IQ4 Filter Function Modules ........................................................................................................ 503
A1.10.13 IQ4 Gate Function Modules .......................................................................................................... 504
A1.10.14 IQ4 Heat Meter Function Module ................................................................................................. 504
A1.10.15 IQ4 Hysteresis Band Function Modules ....................................................................................... 506
A1.10.16 IQ4 Hysteresis Limits Function Modules ..................................................................................... 506
A1.10.17 IQ4 Integrator Function Modules ................................................................................................. 507
A1.10.18 IQ4 Limit at Function Modules .................................................................................................... 508
A1.10.19 IQ4 Limit to Function Modules .................................................................................................... 509
A1.10.20 IQ4 Log Function Modules ........................................................................................................... 510
A1.10.21 IQ4 Lookup Function Modules ..................................................................................................... 510
A1.10.22 IQ4 Maximum Function Modules ................................................................................................. 511
A1.10.23 IQ4 Minimum Function Modules ................................................................................................. 512
A1.10.24 IQ4 Multiply Function Modules ................................................................................................... 512
A1.10.25 IQ4 Power Function Modules ....................................................................................................... 513
A1.10.26 IQ4 Proximity Function Modules ................................................................................................. 514
A1.10.27 IQ4 Psychrometrics Function Module .......................................................................................... 514
A1.10.28 IQ4 Rescale from Function Modules ............................................................................................ 515
A1.10.29 IQ4 Rescale to Function Modules ................................................................................................. 516
A1.10.30 IQ4 Sample and Hold Function Modules...................................................................................... 516
A1.10.31 IQ4 Square Root Function Modules ............................................................................................. 517
A1.10.32 IQ4 Sliding Window Function Modules ....................................................................................... 518
A1.10.33 IQ4 TRIG Function Modules ........................................................................................................ 519
A1.10.34 IQ4 TRUNC Function Modules .................................................................................................... 519
A1.11 IQ4 IC Comms Modules .......................................................................................................................... 521
A1.11.1 IQ4 Average IC Comms Modules ................................................................................................ 521
A1.11.2 IQ4 Data From Analogue IC Comms Modules ............................................................................ 522
A1.11.3 IQ4 Data From Bit IC Comms Modules ....................................................................................... 523
A1.11.4 IQ4 Data From Byte IC Comms Modules .................................................................................... 525
A1.11.5 IQ4 Data To IC Comms Modules ................................................................................................. 526
A1.11.6 IQ4 Global To IC Comms Modules .............................................................................................. 527
A1.11.7 IQ4 Maximum IC Comms Modules ............................................................................................. 528
A1.11.8 IQ4 Minimum IC Comms Modules .............................................................................................. 530
A1.11.9 IQ4 Sum IC Comms Modules ....................................................................................................... 531
A1.12 IQ4 Input Modules ................................................................................................................................... 533
A1.12.1 IQ4 Analogue Node Modules ....................................................................................................... 533
A1.12.2 IQ4 Digital Byte Modules ............................................................................................................. 534
A1.12.3 IQ4 External Digital Input Modules ............................................................................................. 535
A1.12.4 IQ4 External Digital Sensor Modules ........................................................................................... 536
A1.12.5 IQ4 External Sensor Modules ....................................................................................................... 537
A1.12.6 IQ4 Internal Digital Input Modules .............................................................................................. 541
A1.12.7 IQ4 Internal Digital Sensor Modules ............................................................................................ 543
A1.12.8 IQ4 Internal Sensor Modules ........................................................................................................ 544
A1.12.9 IQ4 Knob Modules ....................................................................................................................... 548
A1.12.10 IQ4 Switch Modules ..................................................................................................................... 549
A1.13 IQ4 Interface Modules ............................................................................................................................. 550
A1.13.1 IQ4 Type 1 (XNC) Interface Modules .......................................................................................... 550
A1.13.2 IQ4 Type 2 (Wallbus) Interface Modules ..................................................................................... 553

Table of Contents
A1.13.3 IQ4 Type 3 (Modbus) Interface Modules ..................................................................................... 555
A1.13.4 IQ4 Type 4 (M-bus) Interface Modules ........................................................................................ 559
A1.14 IQ4 I/O Modules ...................................................................................................................................... 562
A1.14.1 IQ4 I/O Module Module Parameters ............................................................................................ 562
A1.15 IQ4 Logic Modules .................................................................................................................................. 564
A1.15.1 IQ4 Change of State Logic Modules ............................................................................................. 564
A1.15.2 IQ4 Combination Logic Modules ................................................................................................. 565
A1.15.3 IQ4 Counter Logic Modules ......................................................................................................... 566
A1.15.4 IQ4 Delay Logic Modules ............................................................................................................ 567
A1.15.5 IQ4 Digital Input Selector Logic Modules .................................................................................... 568
A1.15.6 IQ4 D to A Logic Modules ........................................................................................................... 569
A1.15.7 IQ4 Fan Out Logic Modules ......................................................................................................... 570
A1.15.8 IQ4 Flip Flop Logic Modules ....................................................................................................... 571
A1.15.9 IQ4 Hours Run Logic Modules ..................................................................................................... 571
A1.15.10 IQ4 Latch Logic Modules ............................................................................................................. 572
A1.15.11 IQ4 Readback Logic Modules ...................................................................................................... 573
A1.15.12 IQ4 Timer Logic Modules ............................................................................................................ 574
A1.16 IQ4 Loop Modules ................................................................................................................................... 575
A1.16.1 IQ4 Loop Module Parameters ....................................................................................................... 575
A1.17 IQ4 Network Modules.............................................................................................................................. 578
A1.17.1 IQ4 BACnet Application Network Modules ................................................................................. 578
A1.17.2 IQ4 BACnet IP Network Modules ................................................................................................ 580
A1.17.3 IQ4 BACnet MSTP Network Modules ......................................................................................... 581
A1.17.4 IQ4 BACnet Network Modules .................................................................................................... 583
A1.17.5 IQ4 Ethernet IP Network Modules ............................................................................................... 584
A1.17.6 IQ4 LAN Network Modules ......................................................................................................... 589
A1.17.7 IQ4 Type 8 (Modbus Serial) Network Module ............................................................................. 590
A1.17.8 IQ4 Type 14 (Wallbus) Network Modules ................................................................................... 592
A1.17.9 IQ4 Type 15 (M-bus) Network Modules ...................................................................................... 592
A1.17.10 IQ4 Type 16 (Trend Client) Network Modules ............................................................................ 593
A1.17.11 IQ4 Type 17 (Trend Serial) Network Modules ............................................................................. 594
A1.17.12 IQ4 Type 19 (Modbus IP) Network Modules ............................................................................... 595
A1.18 IQ4 NTD Modules ................................................................................................................................... 596
A1.18.1 IQ4 NTD Module Parameters ....................................................................................................... 596
A1.19 IQ4 OSS Modules .................................................................................................................................... 598
A1.19.1 IQ4 OSS Module Parameters ........................................................................................................ 598
A1.20 IQ4 Page Modules .................................................................................................................................... 602
A1.20.1 IQ4 Page Module Parameters ....................................................................................................... 602
A1.21 IQ4 Plot Modules ..................................................................................................................................... 603
A1.21.1 IQ4 COV Plot Modules ................................................................................................................ 603
A1.21.2 IQ4 Synchronised Plot Modules ................................................................................................... 604
A1.21.3 IQ4 Periodic Plot Modules............................................................................................................ 606
A1.21.4 IQ4 Triggered Plot Modules ......................................................................................................... 607
A1.22 IQ4 Schedule Offset Modules .................................................................................................................. 609
A1.22.1 IQ4 Schedule Offset Module Parameters ...................................................................................... 610
A1.23 IQ4 Sensor Type Modules ....................................................................................................................... 611
A1.23.1 IQ4 Sensor Type Module Parameters ........................................................................................... 611
A1.24 IQ4 States Category Modules .................................................................................................................. 613
A1.24.1 IQ4 States Category Module Parameters ...................................................................................... 613
A1.25 IQ4 Time Modules ................................................................................................................................... 614
A1.25.1 IQ4 Time Module Parameters ....................................................................................................... 614
A1.26 IQ4 Time Schedule Modules.................................................................................................................... 617
A1.26.1 IQ4 Analogue Time Schedule Modules ........................................................................................ 617
A1.26.2 IQ4 Digital Time Schedule Modules ............................................................................................ 623
A1.26.3 IQ4 Multistate Time Schedule Modules ....................................................................................... 630
A1.27 IQ4 User Modules .................................................................................................................................... 636
A1.27.1 IQ4 Type 0 User Modules ............................................................................................................. 636
A1.27.2 IQ4 Type 1 CNC User Modules ................................................................................................... 638
A1.28 IQ4 Virtual CNC Modules ....................................................................................................................... 639

Table of Contents
A1.28.1 IQ4 Virtual CNC Module Parameters ........................................................................................... 639
A2 IQECO MODULES ...................................................................................................................................... 641

A2.1 Common IQECO Module Parameters ...................................................................................................... 642
A2.2 IQECO Address Modules ........................................................................................................................ 643
A2.2.1 IQECO Address Module Parameters ............................................................................................ 643
A2.3 IQECO Alarm Destination Modules ........................................................................................................ 646
A2.3.1 IQECO Trend Alarm Destination Modules .................................................................................. 646
A2.4 IQECO Alarm Group Modules ................................................................................................................ 648
A2.4.1 IQECO Alarm Group Module Parameters .................................................................................... 648
A2.5 IQECO Alarm Route Modules ................................................................................................................. 649
A2.5.1 IQECO Alarm Route Module Parameters ..................................................................................... 649
A2.6 IQECO Directory Modules ...................................................................................................................... 650
A2.6.1 IQECO Directory Module Parameters .......................................................................................... 650
A2.7 IQECO Display Modules ......................................................................................................................... 651
A2.7.1 IQECO Dynamic Display Module Parameters ............................................................................. 651
A2.8 IQECO Driver Modules ........................................................................................................................... 652
A2.8.1 IQECO Analogue Driver Modules ............................................................................................... 652
A2.8.2 IQECO Digital Driver Modules .................................................................................................... 653
A2.8.3 IQECO Multi Stage Digital Driver Modules ................................................................................ 654
A2.8.4 IQECO Raise/Lower End Driver Modules ................................................................................... 659
A2.8.5 IQECO Time Proportional Driver Modules .................................................................................. 661
A2.9 IQECO Function Modules ....................................................................................................................... 663
A2.9.1 IQECO Adder/Scaler Function Modules ...................................................................................... 663
A2.9.2 IQECO Analogue to Digital Function Modules ............................................................................ 664
A2.9.3 IQECO Average Function Modules .............................................................................................. 667
A2.9.4 IQECO Comparator Function Modules ........................................................................................ 667
A2.9.5 IQECO Divide Function Modules ................................................................................................ 668
A2.9.6 IQECO Filter Function Modules................................................................................................... 668
A2.9.7 IQECO Gate Function Modules .................................................................................................... 669
A2.9.8 IQECO Heat Meter Function Module ........................................................................................... 669
A2.9.9 IQECO Hysteresis Band Function Modules ................................................................................. 671
A2.9.10 IQECO Integrator Function Modules ........................................................................................... 671
A2.9.11 IQECO Minimum Function Modules ........................................................................................... 672
A2.9.12 IQECO Maximum Function Modules ........................................................................................... 673
A2.9.13 IQECO Multiply Function Modules ............................................................................................. 673
A2.9.14 IQECO Power Function Modules ................................................................................................. 674
A2.9.15 IQECO Proximity Function Modules ........................................................................................... 674
A2.9.16 IQECO Rescale from Function Modules ...................................................................................... 675
A2.9.17 IQECO Rescale to Function Modules ........................................................................................... 676
A2.9.18 IQECO Sample and Hold Function Modules ................................................................................ 676
A2.9.19 IQECO Square Root Function Modules ....................................................................................... 677
A2.10 IQECO IC Comms Modules .................................................................................................................... 678
A2.10.1 IQECO Data From Analogue IC Comms Modules ...................................................................... 678
A2.10.2 IQECO Data From Bit IC Comms Modules ................................................................................. 679
A2.10.3 IQECO Data From Byte IC Comms Modules .............................................................................. 681
A2.10.4 IQECO v1.0 Data To IC Comms Modules ................................................................................... 682
A2.10.5 IQECO v1.0 Global To IC Comms Modules ................................................................................ 683
A2.10.6 IQECO v2.0 Data To IC Comms Modules ................................................................................... 684
A2.10.7 IQECO v2.0 Global To IC Comms Modules ................................................................................ 685
A2.11 IQECO Input Modules ............................................................................................................................. 687
A2.11.1 IQECO Analogue Node Modules ................................................................................................. 687
A2.11.2 IQECO Digital Byte Modules ....................................................................................................... 688
A2.11.3 IQECO External Digital Input Modules ....................................................................................... 689
A2.11.4 IQECO External Sensor Modules ................................................................................................. 690
A2.11.5 IQECO Internal Sensor Modules .................................................................................................. 693
A2.11.6 IQECO Internal Digital Input Modules......................................................................................... 695
A2.11.7 IQECO Knob Modules ................................................................................................................. 696
A2.11.8 IQECO Switch Modules ............................................................................................................... 697
A2.12 IQECO Interface Modules ....................................................................................................................... 698

Table of Contents
A2.12.1 IQECO Type 2 (Wallbus) Interface Modules ............................................................................... 698
A2.13 IQECO I/O Modules ................................................................................................................................ 700
A2.13.1 IQECO I/O Module Parameters .................................................................................................... 700
A2.14 IQECO Logic Modules ............................................................................................................................ 701
A2.14.1 IQECO Combination Logic Modules ........................................................................................... 701
A2.14.2 IQECO Counter Logic Modules ................................................................................................... 702
A2.14.3 IQECO D to A Logic Modules ..................................................................................................... 703
A2.14.4 IQECO Flip Flop Logic Modules ................................................................................................. 703
A2.14.5 IQECO Hours Run Logic Modules ............................................................................................... 704
A2.14.6 IQECO Latch Logic Modules ....................................................................................................... 705
A2.14.7 IQECO Timer Logic Modules ...................................................................................................... 706
A2.15 IQECO Loop Modules ............................................................................................................................. 706
A2.15.1 IQECO Loop Module Parameters ................................................................................................. 706
A2.16 IQECO Network Modules ........................................................................................................................ 709
A2.16.1 IQECO BACnet Application Network Modules ........................................................................... 709
A2.16.2 IQECO BACnet MSTP Network Modules ................................................................................... 709
A2.16.3 IQECO Type 14 (Wallbus) Network Modules ............................................................................. 710
A2.17 IQECO NTD Modules ............................................................................................................................. 711
A2.17.1 IQECO NTD Module Parameters ................................................................................................. 711
A2.18 IQECO Plot Modules ............................................................................................................................... 713
A2.18.1 IQECO Synchronised Plot Modules ............................................................................................. 713
A2.19 IQECO Sensor Type Modules.................................................................................................................. 714
A2.19.1 IQECO Fixed Sensor Type Modules ............................................................................................ 714
A2.19.2 IQECO Configurable Sensor Type Modules ................................................................................ 715
A2.20 IQECO Time Modules ............................................................................................................................. 717
A2.20.1 IQECO Time Module Parameters ................................................................................................. 717
A2.21 IQECO User Modules .............................................................................................................................. 718
A2.21.1 IQECO User Module Parameters .................................................................................................. 718
A3 COMMAND LINE COMMANDS .............................................................................................................. 719

A3.1 Modules.................................................................................................................................................... 719
A3.2 IQSET Commands ................................................................................................................................... 723
A4 KEYBOARD SHORT CUTS ....................................................................................................................... 725
A5 3RD PARTY SOFTWARE LICENCES ..................................................................................................... 727

A5.1 License Text for the Microsoft Speech Platform - Runtime (Version 11) ............................................... 727
A5.2 Licence Text for FluentFTP ..................................................................................................................... 734
A5.3 Licence Text for the DotNetZip Library and Tools ................................................................................. 734
A5.4 Licence for SSH.NET .............................................................................................................................. 736
INDEX...................................................................................................................................................................... 739

Table of Contents

About this Manual
1 ABOUT THIS MANUAL

This manual applies to the System Engineering Tool (IQ™SET) version v7.60. It is designed to help you become
familiar with the principles of how to use IQSET to configure the strategies within IQ controllers. It is divided into
several sections.
 About IQSET- Describes IQSET.
 Installation - Describes how IQSET should be installed, and licensed.
 Connect to the Trend network - Describes how to connect to the Trend network.
 Connect to the BACnet Network - Describes the connection to the BACnet network.
 Customise IQSET - Describes how to change IQSET's preferences to suite your requirements.
 Quick Tours - Provides a tutorial that will get you started using IQSET.
 Create a BTL Compliant Strategy - Describes the requirements that must be meet to create a BTL compliant
strategy.
 Engineering IQ Controllers - Describes the process that should be followed to engineer a complete Trend
system from start to finish using IQSET.
 IQ Interfacing - Describes the process that should be followed to engineer a IQ interfacing using the standard
strategy block available in IQSET.
 Comparing Strategies - Describes how to use IQSET to compare strategies in IQ controllers with the strategy
held by IQSET.
 Commissioning with Live Values - Describes how to use IQSET to commission controllers using live values.
 Live Editing - Describes how to use IQSET to edit a controller's configuration parameters as the strategy is
drawn.
 General Operations - Describes general IQSET operations.
 Browsing the Trend System - Describes how to use IQSET to browse the Trend system to which it is
connected, and perform certain tasks.
1.1 Conventions Used in this Manual
There are numerous items and instructions in this manual, the conventions below are designed to make it quick and
easy to find and understand the information.
 Menu commands are in bold type.
 Buttons and options that you need to select are in bold type.
 The names of text boxes and dialogue boxes are in bold type.
 Key combinations that you should press appear in normal type. If joined with a plus sign (+), press and hold
the first key while you press the remaining one(s). For example, CTRL+P indicates holding down the control
key while pressing P.
 Text you should enter is in Italic type.

About this Manual
1.2 Contacting Trend

Head Office
St. Mark's Court
North Street,
Horsham
West Sussex
RH12 1BW
UK.
Tel: +44 (0) 1403 211888
Fax: +44 (0) 1403 241608
Details of regional offices can be found on our web site.
Internet
Our company web site (www.trendcontrols.com) provides information about our products and us. Accredited partners
should contact our support web site (https://partners.trendcontrols.com).
Technical Support
Our support department provides technical support during normal office hours. Before contacting them ensure that
you have your Technical Support PIN number available, without this we will be unable to provide you with any
support.
Tel: +44 (0) 1403 226600
Email: trendts@trendcontrols.com
Fax: +44 (0) 1403 226310
Technical Publications
Please send any comments on this or any other Trend technical publication to techpubs@trendcontrols.com.

What's New in Version v7.60
2 WHAT'S NEW IN VERSION V7.60

New Features
 Support for IQ4 v4.30 firmware.
 IQ Interfacing. (SET-6826).Type 15 (M-bus) Network and Type 4 (M-bus) Interface modules have been
added to enable the IQ4/INT variants to directly interface with M-bus devices over RS232 or RS485
networks.
 Number of vCNC modules increased to 8 for IQ4NCs.
 Dead alarm enable parameter added to vCNC module.
 Search Library improved.
 Place holder text added to strategy blocks. Placeholder text is replaced with text specified by the engineer
when the strategy block is used.
 Improvements IQSET's password rules to strengthen security.
 Improvements to web server configuration.
 Facility to duplicate a strategy block.
 Autolock feature which automatically lock the IQSET user interface after a specified period.
 Label and units of an Interface module's output is passed though to a linked display module (Sensor, Knob
and Switch).
 Backdrops used by a strategy block are copied to the project folder.
For more detail about new features, fixes, and known issues see the IQSET v7.60 Release Notes (TG200984).

What's New in Version v7.60

About IQSET
3 ABOUT IQSET
IQSET is a Windows® based tool providing a graphical method of configuring the strategy within an IQ controller.
It simplifies the task of engineering a Trend system. Whether a site with large numbers of controllers covering a wide
area, or a stand-alone controller, is being engineered, IQSET has the tools required to make life easier. It provides a
powerful way to create IQ control strategies and support documentation. IQSET’s method of constructing strategies
as strategy diagrams allows both data files (IQ4, IQ3, IQECO, LDF, and IQ2) and printable documentation to be
produced.
Its graphical representation of the strategy makes the strategy easy to follow, and plant views allow the strategy to be
selected by HVAC equipment rather than by controller. Common pieces of strategy can be stored, and used again and
again, not only in one controller, but also in other controllers or projects, using the strategy block concept.
IQSET understands controllers, automatically using standards for module inputs and outputs, automatically placing
modules in the sequence table, and prompting for essential information. The use of projects means that all information
relating to a site or job is automatically organised, saving time searching for the right file.
During the creation of a strategy, IQSET keeps track of module number, and sequence steps used automatically
assigning the next module and sequence step as modules are added. IQSET also uses the standard source and
destinations for individual modules. These parameters can be manually adjusted, but normally this will not be
necessary. IQSET also allows event driven strategy and fast sequencing of modules to be quickly set up. When
defining the links between modules, IQSET uses its understanding of Trend system devices to determine whether the
link is valid, if it is not, IQSET will not allow the link to be made.
The graphical representation of the strategy, used when creating and editing, consists of strategy pages. Strategy can
be linked across these pages using connectives, enabling even the most complex strategies to be created. IQSET
enables the module's parameters displayed on the screen to be specified. Intelligent routing of links between modules
ensures that the links do not run over the top of modules, allowing modules to be moved around on the screen without
having to re-route the module links.
IQSET knows where each device is on the system, and with which strategy it is associated. This means that it can
download strategy to the correct controller without having to be told where it is.
Sensor definitions speed up the definition of sensor type modules. IQSET allows new sensor definitions to be created
if the types of sensors being used do not match those already shipped with IQSET.

About IQSET
3.1 The IQSET Window

This section describes the different parts of the IQSET Window.
3.1.1 Display Area

The Display Area displays the information that has been requested. Items launched from IQSET are displayed in this
area as a separate window in their own tab. Windows in this area can be positioned as required either manually by
resizing, and moving or using the Tile command, or the Window Position toolbar.
3.1.2 Item Selector
The Item Selector appears above the System View, and is only visible when the System View is displayed. It enables
an object in the tree to be quickly located. Simply specify the site, and if necessary LAN, device, and module, and the
Item Selector will open the tree up at that point, and highlight the specified object. It also enables associated tasks to
be performed.
3.1.3 Menu Bar
The Menu Bar contains IQSET’s menus, which provide access to the application’s various features. The menus
available and the commands they contain will depend on the job currently being carried out by IQSET. For more
details of the individual menus and their commands.
3.1.4 Project View
The Project View displays information about the devices that have been added to the project, and the strategy
associated with them. It is divided into two separate areas:
Device View
The Device View contains all the controllers in the project arranged by LAN and the strategy pages that have been
created for each controller. It enables LANs, and controllers to be added, deleted, and edited. It also enables strategy
pages to be created, and provides access to modules such as the address module that do not appear on strategy pages.
Icons indicate the type of object.
Icon Description
Group of Strategy Pages
IQ1 Series Controller
NTD (Non-Trend Device)
LAN

About IQSET
Icon Description
BACnet LAN
Site
Strategy Page
Plant View
The Plant View enables the strategy within controllers to be located by HVAC equipment type. Once set up the
structure of the Plant View can be used to create display modules and directory modules. Icons indicate the type of
object.
Icon Description
Plant Directory
Strategy Page
3.1.5 Search Library
The Search Library displays a list of the strategy blocks that match the specified search criteria. It is divided into
three separate areas:
Search Area
The Search Area enables the search criteria to be specified.
Strategy Blocks Area
The Strategy Blocks Area contains list of the strategy blocks and solutions that match the specified search criteria. It
is divided into two columns:
Column Description
The name of the strategy block. Icons indicate the type of controller the strategy block or solution can
be used in.
- Standard solution
Block - Strategy block for an IQ4 controller
Name - Strategy block for an IQ3 controller
- Strategy block for a pre IQ3 controller
- Strategy block for an IQECO controller
- Strategy block for an unknown controller type, normally an old strategy block
Type Indicates the library that contains the strategy block, can be Custom, Standard, or Old.
Description Area
The Description Area contains a description of the selected strategy block or solution.
3.1.6 Status Bar
The status bar is located at the bottom of the display. It provides information about what IQSET is currently doing,
number of free modules, the number of free log points, free external I/O points, free brIQs, LAN and network address
of the controller, the page number, module position, and the current time.
Location Description
Address The network address of the selected controller.
Indicates the status of the current connection.
- vCNC link Authenticated and Encrypted
Connection - vCNC link Unauthenticated
Indicator - vCNC link Unauthenticated and Unencrypted
- vCNC link Disconnected
XXXXXXX- connected to SIMIQ
The number of free brIQs available in the current controller (if applicable). It provides an indication
Free brIQs
of the amount of memory left in the controller for strategy.

About IQSET
Location Description
Free External The number of free brIQs (if applicable), free I/O points on external I/O modules (if applicable)
I/O points available in the current controller.
The number of free log points available in the current controller (if applicable). This provides an
Free Log points indication of the amount of memory left in the controller for logging data. The number of log points
is displayed in red if there are not enough for the number of plot modules added to the strategy.
The number of modules available to be added to the strategy. Only available for IQECO controllers.
Free Modules
An error message is displayed when the maximum number of modules is exceeded.
LAN number The LAN number displays the LAN number of the selected controller.
Free Seq. Steps The number of free sequence steps in the strategy.
The co-ordinates of the top left corner of the selected module If more than one module is elected the
Module Co- co-ordinates are those of the top left corner of the current module. When the 'C' letter precedes the
ordinates co-ordinates, this indicates the cursor position. When the cursor is over a module the letter changes
to an ‘M’ and the value indicates the modules upper left position.
Information about the status of communications in and out of the node connecting IQSET to the
Network
Trend network. The indicators flash green when IQSET is receiving, or transmitting information. If
Comms Status
they appear grey, IQSET has been unable to locate the CNC. Clicking on the indicators displays the
Lights
Communications Window.
Page Number The number of the current strategy page.
Remote The status of any remote connection devices on the system. If grey, all the devices are available for
Connection use, if red, at least one of them is attempting to make a connection, and if green, at least one is
Indicator connected. Clicking on this icon displays the Remote Connection Window.
Note: The exact combination of these parameters depends on the controller type.
3.1.7 Strategy Library
The Strategy Library displays the reusable pieces of strategy (strategy blocks) and reusable strategies (solutions)
that have been created, and enables them to be used. It is divided into four separate areas:
Description Area
The Description Area contains a description of the selected strategy block or solution.
Strategy Blocks Area
Strategy Blocks Area contains the strategy blocks. It is organised into three different areas Custom Block Area,
Standard Block Area, and Old Block Area.
The Custom Block Area contains strategy blocks that you have set up, the Standard Block Area contains standard
strategy blocks that are supplied with IQSET, and the Old Block Area contains strategy blocks created with an earlier
version of IQSET. Strategy blocks in the Standard Block Area cannot be changed or deleted. Strategy blocks in the
Old Block Area can be deleted, or moved to the Custom Block Area. Icons indicate what the item is.
Icon Description
Standard Block Area
Custom Block Area
Old Block Area
Strategy block group
Old strategy block group
Strategy block sub group
Strategy block for an IQ4 controller
Strategy block for an IQ3 controller
Strategy block for a pre IQ3 controller
Strategy block for an IQECO controller
Strategy block for an unknown controller type, normally an old strategy block
Strategy Block Page
Solutions Area
The Solutions Area contains the solutions. It is organised into two different areas Custom Solution Area, and
Standard Solution Area.

About IQSET
The Custom Solution Area contains solutions that you have set up, and the Standard Solution Area contains
standard solutions that are supplied with IQSET. Solutions in the Standard Solutions Area cannot be changed or
deleted. Icons indicate what the item is.
Icon Description
Standard Solution Area
Custom Solution Area
Solution block group
Solution sub group
Standard solution
Custom solution
Toolbar
The toolbar contains buttons that enables the Strategy Library to be searched, or filtered.
Icon Description
Displays the Search Library, which enables the library of plant blocks to be searched
Enables the list of strategy blocks to be filtered
Refreshes the contents of the Strategy Library
Enables the strategy blocks and solutions to be printed
Enables the strategy blocks to be translated
Exports strategy blocks and solutions
Imports strategy blocks and solutions
3.1.8 System View
The System View displays the connections that are currently available, any sites, and user nodes that have been added,
and enables them to be browsed, and any relevant tasks performed. It is divided into two different areas:
Sites Area
The Sites Area contains a list of the sites that have been added, and the structure of those sites right down to the
individual modules in a tree structure. Right clicking on an object in the tree enables you to perform a task such as
enter a text comms session with the device, display a graph, or adjust a value. This tasks that can be carried out depend
on the device type. Icons indicate the type of object.
Icon Description
921 Supervisor
940 Supervisor
942 Supervisor
943 Supervisor
945 Supervisor
963 Supervisor, 962 Supervisor, S2 Supervisor, or ViewPoint
IQView
NDP
TCC Application
Trend X Application
Unknown Supervisor
ANC
BACnet device
BINC
CNC
EINC
FNC
Foreign device

About IQSET
Icon Description
IQ EYE Collector
ID200
INC
IQ3 Series Controller on BACnet network
IQECO Controller
IQL Series Controller
LERN
LINC
LONC
MNC
PNC
TOPS
TOPS BACnet Device
TOPS Logic 1Device
TOPS Unknown Device
Unknown Device
Unknown Internetwork Device
Virtual INC inside a device on LON
XNC
BACnet Site
BACnet Network
Foreign Site
Foreign LAN or network
Trend Site
Trend Internetwork
Trend LAN
Address modules
Alarm Destination modules
Alarm Group modules
Alarm Route modules
Analogue Node modules
Calendar modules
Core of a controller that has not yet been discovered
Critical Alarm modules
Digital Input modules
Digital node modules
Directory modules
Display modules
Driver modules
Function modules

About IQSET
Icon Description
IC Comms modules
Knob modules
Logic modules
Loop modules
Module Parameter
Non-Trend Device in TOPS
OSS modules
Page modules
Plot modules
Schedule Offset modules
Sensor modules
Sensor Type modules
Sequence Step modules
Switch Modules
Time modules
Time Schedule modules
Unknown Module
Unknown Module Family
User modules
A cross over the top of the icon indicates a problem, a black cross means that the comms have failed, and a grey cross
indicates that the value is old (value initialised from file).
Information from a site can be displayed by drilling down thorough the site to the required level. Once displayed,
information can be updated, and devices edited etc. depending on the functions available.
The values of parameters, and the network structure are learnt when the structure is refreshed. Learnt structures can
be saved enabling them to be viewed again quickly without the need for IQSET to communicate over the network. If
up to-date information is required, then just the part of the system containing that information can be refreshed,
reducing unnecessary communications and network traffic.
Objects (internetworks, LANs, devices, modules, and module parameters) can be removed from the site, preventing
them being accessed by the applets. The Sites section is available to all user roles, and provides the best way of finding
out about the system.
Each site specifies the name of the site, and the connection that is to be used to access the Trend network or devices
referred to by the site name. It is recommended that the site name describes the Trend network or Device that is being
accessed e.g. Albery House refers to the Trend network in Albery House, and the connection specified is the one that
will most often be used to connect to that site. For example, it may be possible to dial into the site, but you would
normally connect directly to the site over the company IT networks. In this case, you should add two connections, one
for the TCP/IP connection and another for the autodialled connection. When the site is created the TCP/IP connection
should be specified for the site, although if you need to access the site by autodialling, the sites connection can be
changed accordingly.
User Nodes Area
The User Nodes Area contains all the user nodes that have been added to the System View. User nodes are shortcuts
to items already in the System View and allow a user-defined structure to be created (to allow faster access to regularly
used parts of the system). Icons indicate the item type.
Icon Description
User Nodes
User Parameter
There is no limit to the number of user nodes that can be added. Each user node can contain other user nodes, or user
parameters. Access to user nodes (and some user parameters) can be restricted to specific user roles to prevent
unauthorised accessed and reduce confusion to lower-level users.

About IQSET
The user parameters contained within a user node can be from any point on the site, e.g. the value of a sensor, or a
controller or LAN. The user parameters in the user nodes are not restricted to a single controller, but can come from
several different controllers on different LANs, and even from different sites. The diagram below illustrates how user
nodes can be used.
The structure above shows user nodes accessing information from two different sites Albery House and Foundry Lane.
The information inside the Temperatures user node comes from different controllers. The structure has been designed
to enable quick access to the required information.
Note: Structures displaying user parameters referring to parameters in different sites may be grouped together under
one user node.
The user node controls the refresh of data in the user nodes. A user node has two parameters relating to data refresh.
The first is the Refresh is active parameter that determines whether the data is refreshed at all. By default, this setting
is OFF, which allows any communications traffic to be kept to a minimum. The second is the Refresh interval, which
specifies the interval between refreshes, if refreshing is active. The data can be refreshed manually if required.
In addition to user parameters a user node may have a reference to any system node (site, LAN, device, etc.) as a child
to enable favourite structures to be built.
3.1.9 Toolbars
IQSET has several toolbars that provide easy access to IQSET's functions. Individual toolbars can be
hidden/displayed, and positioned as required. For more details of the individual toolbars and their commands.

Installation
4 INSTALLATION
This section describes how IQSET should be installed to ensure that it operates correctly, and how to upgrade from a
previous version. Before installing, or upgrading ensure that the PC meets the system requirements see the IQSET
Data Sheet (TA200131).
Installing IQSET with 963
IQSET and 963 can be installed, and run on the same PC. However, if running both only one will be able to
communicate with a BACnet network. The rule is:
IQSET v6.2 or greater with the BACnet Network driver installed and TOPS (required for 963 BACnet
communications) cannot run on the same PC at the same time.
Both 963 and IQSET will start and stop their respective BACnet driver when they are opened and closed. Running
one at a time does not cause a problem. However, if both are to be run at the same time the one that is run first will be
able to communicate over BACnet and the other will not. It is possible for 963's BACnet communication service
(TOPS) to run on a different PC to 963 if this is the case then both 963 and IQSET can run on the same PC, and both
can access BACnet devices.
Securing IQSET
To maximise the security of the IQSET - refer to Securing IQSET, and the Security Best Practice for Trend Products
Information Sheet (TP201331).
4.1 Install IQSET
To install IQSET follow the procedure described below:
1. Install the software
2. License IQSET
3. Set up IQSET users
4. Install the BACnet network driver (if required)
5. Install the LCI/USB Driver (if required)
6. Customise IQSET (if required)
7. Connect to the Trend network
8. Connect to the BACnet network (if required)
9. Secure IQSET
Note: The installation of IQSET on a virtual machine is not supported.
Note: Ensure that any firewalls between IQSET and controllers to which strategy is to be uploaded/downloaded are
configured to allow FTP.
4.1.1 Install the Software
The installation of IQSET is performed by a step-by-step installation program.
To install the software:
1. Ensure that IQSET is not running, and close all programs (including virus protection applications).
2. Download the IQSET installation.
3. Run the IQSET install. The installation screen is displayed.
Note: If the PC has an active Ethernet connection, but does not have access to the internet IQSET may take
a long time to install. If this occurs remove the network cable, or disable the PC's wireless connection to
close the Ethernet connection.
4. Follow the instructions on the screen.
Note: In some cases, when using a very high resolution monitor, it may be necessary to adjust the custom text size.
4.1.1.1 Upgrade from a Previous Version
If a previous version of IQSET is already installed on the PC, it can be upgraded to the latest version. If upgrading
IQSET using a service pack supplied on disk, or downloaded from our web site, you should follow the instructions
provided with the service pack.
To upgrade from a previous version:
1. Ensure that IQSET is not running, and close all programs (including virus protection applications).
2. Download the IQSET installation.
3. Run the IQSET install. The installation screen is displayed.
4. Follow the instructions on the screen.

Installation
5. Once the installation of IQSET is complete, and any necessary files copied to the new location the previous
version of IQSET should be uninstalled using the Control Panel's Add/Remove Programs option.
Note: If upgrading from a licenced version of v6.91 or earlier it is necessary to re-licence IQSET. A bridging licence
is available to allow a valid licence to be obtained.
4.1.2 License IQSET
Before IQSET can be used, it must be licenced.
To licence IQSET:
1. Obtain an Unlock Code.
2. Enter the Unlock Code.
Note: If upgrading from a licenced version of IQSET 6.91 or earlier IQSET can be run using a bridging licence for
seven days to allow registration on the licencing portal.
Note: Adjustment to the PC’s date/time may cause the licence to become invalid.
4.1.2.1 Obtain an Unlock Code
To obtain unlock code:
1. Display the Licence Details dialogue box. This may be displayed when you run the software, or may need
to be displayed manually refer to the specific product documentation for details of how to display the Licence
Details dialogue box.
Note: IQSET may display a Bridging button if upgrading from 6.91 or earlier, and not all the fields are
available for all products.
2. Click to copy the site code on to the clipboard or make a note of it.
3. Click . This will open Pnet licencing portal.

4. Log in with your PNet user name and password.
5. Click Request licence keys.
6. Click the product you want to license.
7. Select the type of licence required from the The Feature required box.
8. Enter the details requested on the page. The site code - step (2) should be entered in The Site Code box.
9. Click Request Licence. The Site code will be displayed on the screen, and you will also receive an email
notification.

Installation
4.1.2.2 Enter the Unlock Code
To enter the unlock code:
1. Ensure you have the site key available.
2. Display the Licence Details dialogue box. This may be displayed when you run the software, or may need
to be displayed manually.
Note: Some software will display a Trial button and SET may display a Bridging button if upgrading from
6.91 or earlier, and not all the fields are available for all products.
3. In the Company Name box enter your company name.
4. In the User Name box enter your name (not required for all products and license types).
5. In the Building Name box enter the name of the building (not required for all products and license types).
6. In the Serial Number box enter the serial number (not required for all products and license types).
7. In the Site Key box enter the supplied site key.
8. If a licence file was received specify the licence file (not required for all products and license types).
 Copy the licence file to the PC running the software that is to be licensed.
 Click . The Open dialogue box is displayed.
 Navigate to the location the licence file has been copied to.

Installation
 Click the licence file.
 Click Open. The file will be copied to the required location, and can be deleted for the original location
if required.
9. Click Activate. If the software is activated successfully a message box is displayed, click OK to close
the Trend Licence Details dialogue box. If the activation fails an error message is displayed, click OK to
close the error message, the Trend Licence Details dialogue box will not be closed.
4.1.2.3 Display IQSET's Licence Dialogue Box
IQSET's Licence Details dialogue box will normally be displayed when an unlicensed version of IQSET is run. To
update the licence, or transfer it to another location it is necessary to display it manually.
To display the IQSET's Licence Details dialogue box:
1. On the Help menu click About SET.
2. Click Relicence.
4.1.3 Set up Users
IQSET enables users to be set up to so that the correct user can be assigned to the project, it also enables the information
that appears in the System View to be defined. Each user has a username, password, and associated user role. The
username will be added to descriptions of the things the user does, the password enables them to log on, and the user
role determines how information in the System View is presented to them.
Role Description
Browser A user who can view limited parameters on the system.
Operator A user who can view limited parameters on the system, and make simple adjustments.
Supervisor A user who can view parameters on the system, and make complex adjustments.
Administrator A user who can view parameters on the system, and make more complex adjustments.
Commissioning A user who can view parameters from an engineering point of view, and make complex
Engineer adjustments.
Engineer A user who has full access to the system.
Note: The first time IQSET is run it forces the creation of a single user 'Administrator' and requires a suitable
password to be specified. This user is only used to set up other users.
To add a user:
1. Run IQSET.
2. In the User Name box click Administrator.
3. In the Password box enter the password.
4. Click Edit/Add User. The Users dialogue box is displayed.
5. Click Add. The New User dialogue box is displayed.
6. Enter the name for the user in the Enter User Name box. Only characters a to z, A to Z, 0 to 9 or the space
character can be used accented characters are not supported.

Installation
7. Click OK. The User Setup dialogue box is displayed.
8. In the User Role box click required user role.

9. In the Password box enter the user’s password (minimum 10 characters). The password must contain at least
1 upper case letter, at least 1 lowercase letter, at least 1 digit, and must not be the same as the user name.
Only characters a to z, A to Z, 0 to 9 or the space character can be used, accented characters are not supported.
10. In the Verify box re-enter the user's password.
11. Click OK.
12. Click Exit to return to the Log onto SET dialogue box.
4.1.3.1 Delete a User
Users that are no longer required can be deleted.
To delete a user:
1. Run IQSET.
5. Click the user that is to be deleted.

6. Click Delete. IQSET prompts for confirmation of the deletion, click Yes.
7. Click OK.
8. Click Exit to return to the Log onto SET dialogue box.
4.1.3.2 Edit a User
If required users can be edited to change their password or user role.
To edit a user:
1. Run IQSET.

Installation
5. Click the user that is to be edited.
6. Click Edit. The User Setup dialogue box is displayed.
7. Change the parameters if the user as required.

8. Click OK to return to the Log onto SET dialogue box.
4.1.4 Install the BACnet Network Driver
If IQSET is to communicate with BACnet devices the BACnet network driver must be installed
Note: There may be several warning messages click OK to accept them.
To install the BACnet network driver:
1. If the BACnet Gateway is installed on the PC close the BACnet gateway, and run 'uninstall.exe' in the
'C:\Program Files\Trend Control Systems\BACnet gateway\Install' directory to uninstall the old version of
the BACnet driver used by the BACnet Gateway.
Don't worry once the new BACnet network driver supplied with IQSET is installed both IQSET and the
BACnet Gateway will use it.
2. Ensure IQSET is not running.
Important: When you close IQSET this help file will close. Ensure that you print out these instructions by
right clicking the help window and clicking Print before closing IQSET.
3. Run 'bacstac.msi'. This is in the 'C:\Program Files (x86)\Trend Control Systems\BACnet gateway\Install
directory. The Cimetrics BACstac Gateway Port Table dialogue box is displayed.

Installation
4. Click on the physical network (Port ID 1), and click Edit. The BACnet/IP Port Properties dialogue box is
displayed.
5. In the Adapter box select the network adaptor that is to be used to communicate over BACnet.
6. Click OK.
7. Click on the virtual network (Port ID 2), and click Edit. The Virtual Port Properties dialogue box is
displayed. Remember the port ID you will need it when adding a BACnet site.
8. In the Network Number box enter a network number for IQSET on the BACnet network. This must be
different from any other physical or virtual network on the BACnet system.
9. Click OK.
10. Click OK.
To change any of the settings specified during this procedure it is necessary to run 'baccfg.bat' from the 'c:\Program
Files\Cimetrics\BACstac v6.2d' directory which will display the Cimetrics BACstac Gateway v6d Port Table
dialogue box.
4.1.5 Install the USB Driver
The USB driver enables IQSET to connect to the Trend network over USB using a standard USB cable connected to
an IQECO or IQ4s engineering port.
On all supported operating systems, see the IQSET Data Sheet (TA200131), except Windows 8, Windows 8 Pro and
Windows 8 Enterprise the first time you connect the driver will be automatically installed. For windows 8 systems the
driver must be manually installed as described below.
To install the USB driver:
1. Go to \Program Files (x86)\Trend Control Systems\Support Files\IQ Drivers folder and run 'dpinst.exe' from
the appropriate sub folder. The User Account Control dialogue box is displayed.

Installation
2. Click Yes to continue. The Device Driver Installation Wizard is displayed.
3. Click Next. The Windows Security dialogue box is displayed.
4. Click Install. When the installation is complete the Device Driver Installation Wizard is displayed.
4.1.6 Install the LCI/USB Driver

The LCI/USB driver enables IQSET to connect to a LonWorks network via an LCI/USB.
To install the LCI/USB driver:
1. Connect the LCI/USB to the PC - see LCI/USB Installation Instructions (TG200817).
2. Display the Device Manager.
Windows 7
 Select the Windows Start button, type Device Manager in the Search box and then click Device
Manager from the list of results.
Windows 8 & 10
 Press the Windows key + X and then choose Device Manager.
3. Expand Other devices in the Device Manager.

Installation
4. Right-click Novar Trend LCI USB and select Update Driver Software….
5. Select Browse my computer for driver software.
6. Browse (or enter) the location where IQSET has been installed.
7. Click Next. A security warning is displayed.
8. Click Install. On successful completion, a message is displayed.
9. Click Close.
10. Right-click USB Serial Port and select Update Driver Software….
11. Select Browse my computer for driver software.
12. Browse (or enter) the location where IQSET has been installed.
13. Click Next. A security warning is displayed.
14. Click Install. On successful completion, a message is displayed. The LCI USB will now appear in the Device
Manager under Ports (COM & LPT). Make a note the COM port allocated to the device (e.g. COM3).
4.1.7 Customise IQSET
Once IQSET has been installed and is running, it should be customised to specify the name and address printed on the
strategy pages and other default settings - see 'Customise IQSET'.
4.1.8 Connect to the IQ Network
If IQSET is to communicate with IQ controllers to upload /download files or to access controllers in configuration
mode, it is necessary for IQSET to be connected the Trend network - see 'Connect to the Trend Network'.
4.1.9 Connect to the BACnet Network
If IQSET is to communicate with BACnet devices it is necessary for IQSET to be connected the BACnet network -
see 'Connect to the BACnet Network'.
4.2 Transfer the Licence to a Different Location
If you use the licence to a different PC or location it is necessary to transfer the licence to that location.
Note: The transfer license option is not available on virtual machines.
To transfer the licence:
1. Install IQSET in the new location.
2. Run IQSET from the new location. SET's Licence Details dialogue box is displayed. If it is not displayed it
can be displayed manually.
Note: IQSET may display a Bridging button if upgrading from 6.91 or earlier, and not all the fields are
available for all products.
3. If transferring the licence to a different PC connect the removable media that is to be used to transfer the
licence.

Installation
4. Click Register Media. The Browse for Folder dialogue box is displayed.
5. Click the location to which the licence is to be copied. If moving the licence to a different PC this is the
removable media. To create a new folder click Make New Folder.
6. Click OK. The following message is displayed, 'Transfer media 'Y:\' registered successfully'.
7. Click OK.
8. If transferring the licence to a different PC remove the removable media.
9. Run IQSET from the original location. IQSET's Licence Details dialogue box should be displayed, If it is
not displayed it can be displayed manually.
10. If transferring the licence to a different PC connect the removable media being used to transfer the licence.
11. Click Transfer Out. The Browse for Folder dialogue box is displayed.
12. Click the location specified in (5).
13. Click OK. A message is displayed, 'Licence has been transferred out to 'C:\Licence' successfully'.
Note: If the licence is being transferred to a shared network drive on a different PC you will be prompted for
the user name and password required to access it. Enter the user name a password and click OK.
14. Click OK. The licence will be moved to the specified location. IQSET is no longer licensed to run in that
location.
15. Run IQSET from the new location. IQSET's Licence Details dialogue box is displayed, If it is not displayed
it can be displayed manually.
16. If transferring the licence to a different PC connect the removable media being used to transfer the licence.
17. Click Transfer In. The Browse for Folder dialogue box is displayed.
18. Click the location where the licence has been stored in (13). Click OK. The following message is displayed,
'Licence has been transferred in from 'Y:\' successfully'.
Note: If the licence is being transferred from a shared network drive on a different PC you will be prompted
for the user name and password required to access it. Enter the user name a password and click OK.
19. Click OK. The licence will be moved to the new location. Software is now licensed to run in the new location.

Securing IQSET
5 SECURING IQSET
IQSET is a networked product and as such must have its security correctly configured to reduce the risk of
unauthorised access. For general information about securing Trend products see the General Security Best Practice
for Trend Products Information Sheet (TP201331).
Adopting normal installation and security best practice guidelines can mitigate the risk of a malicious IT attack from
a skilled and equipped IT individual.
5.1 Security Checklist
 Project files included in disaster recovery plan
 IQSET installation files included in disaster recovery plan
 PC running latest version of supported operating system with all updates
 PC running virus protection software
 Latest version of IQSET being used
 All system networks secured
 Appropriate user accounts set up on PC
 IQSET users configured as required
In addition to the actions described in the General Security Best Practice for Trend Products Information Sheet
(TP201331), the advice described in the following sections must be followed.
5.2 Developing a Security Program
Refer to the General Security Best Practice for Trend Products Information Sheet (TP201331).
5.3 Disaster Recovery Planning
When developing the disaster recovery plan ensure that it includes ALL data required to restore system operation.
You should ensure that the following folder is included:
C:\Users\Public\Documents\System Engineering Tool
5.4 Physical and Environmental Consideration
The PC running IQSET should, where possible, be secured against unauthorised physical access in accordance with
your company's IT policy.
5.5 Security Updates and Service Packs
Ensure the PC running IQSET has the latest operating system updates installed, and the latest version of IQSET is
being used.
Trend software is tested against the latest service packs and updates applicable at the time of release. For significant
operating system/service packs, please check the Trend Partner's web site (https://partners.trendcontrols.com) for
compatibility issues.
5.6 Virus Protection
Ensure the PC running IQSET is running virus protection software, and the virus definitions are kept up-to-date.
5.7 Network Planning and Security
Ethernet Network
If IQSET is to be connected to an Ethernet network, follow the guidelines in the General Security Best Practice for
Trend Products Information Sheet (TP201331).
It is recommended that the Ethernet network used by the BMS system is separated from the normal office network
using an air gap, or virtual private network. Physical access to the Ethernet network infrastructure must be restricted.
You must also ensure that the installation complies with your company’s IT policy.
The use of a Firewall and Intrusion Detection System (IDS) from a reputable provider of security products is
recommended. Follow best practice for the products chosen as well as any corporate IT policy where the installation
is made.

Securing IQSET
BACnet IP Network
Due to the insecure nature of the BACnet protocol if IQSET to communicate over BACnet IP the PC running IQSET
MUST not be connected to the internet under any circumstance. Physical access to the BACnet IP network
infrastructure must be restricted. If BACnet IP communications are not required, the do no install IQSET's BACnet
driver.
5.8 Virtual Environments
Follow best practice for the products chosen as well as any corporate IT policy where the installation is made.
5.9 Securing Wireless Devices
If a wireless network is being used it must be secured in accordance with your company’s IT policy.
5.10 System Monitoring
Trend Controls recommends the use of an Intrusion Detection System (IDS) from a reputable provider of security
products. Follow best practice for the products chosen as well as any corporate IT policy where the installation is
made.
5.11 Windows Domains
Not applicable to IQSET.
5.12 Securing Access to the Operating System
Ensure the PC running the IQSET is secured in accordance with your company's IT policy. In addition, you should
follow Microsoft's advice for securing your chosen operation system.
Ensure that the PC has suitable user accounts setup for each user. IQSET can be run when the user is logged onto the
PC as a user without admin rights. It is recommended that IQSET is run by a user with the lowest possible access
rights to the PC.
Ensure that users are set up in IQSET to ensure that any access to IQSET or changes require password or PIN
authorisation. For details of configuring user accounts see the operating system's documentation. For details of the
setting up IQSET users - see 'Set up Users'.
5.13 Security Features
IQSET enables users to be set up to restrict access to its features ensuring that an individual user only has access to
the appropriate features. Each user has a username, password, and associated user role. The username will be added
to descriptions of the things the user does, and the user role determines how information in the System View is
presented to them. For details of setting up IQSET users - see 'Set up Users'.
IQSET has other security features that must also be set up - see Configure Security Options.
IQSET can be run when the user is logged onto the PC as a user without admin rights. It is recommended that IQSET
is run by a user with the lowest possible access rights to the PC.

Customise IQSET
6 CUSTOMISE IQSET
This section describes how to change IQSET's preferences to suite your requirements.
6.1 Configure Security Options
IQSET's security options enable you to configure the following settings that make IQSET more secure.
Setting Description
Configuring autolock will cause IQSET to lock after a user defined period of inactivity. The user will
Autolock then be required to log back in. Enabling this feature will disable the remember my password feature. By
default autolock is enabled with a 15 minute timeout.
To configure the security options:
1. Run IQSET.
2. On the Tools menu click Security Options. The Security Options dialogue box is displayed.
3. Set up the required options.

Enable a timeout:
 Select Enable Timeout.
 Select the period of inactivity before IQSET locks.
4. Click OK.

Customise IQSET
6.2 Enable/Disable the Controller and Identifier Check

When IQSET attempts to communicate with a device to upload or download strategy it will check that the local node
number and identifier in the address module match the one in actual controller.
To enable/disable the controller and identifier check:
1. Run IQSET.
2. On the Tools menu click SET Options. The SET Options dialogue box is displayed.
3. Select/clear the Disable Outstation and Identifier Check check box.

4. Click Exit.

Customise IQSET
6.3 Enable/Disable the Controller Time/Date Check

When IQSET attempts to communicate with a device to upload or download strategy it will check that time in the
controller is within a specified amount of the PC clock. If there is a difference IQSET will then prompt you to update
the controller's time.
To enable/disable the controller time/date check:
1. Run IQSET.
3. Select/clear the Disable Time/Date Check check box.

4. Click Exit.

Customise IQSET
6.4 Enable/Disable the Strategy Sync Check

The IQSET strategy and the controller strategy must be identical or some of the values may not make sense. It will
check to see if there are any differences, and if necessary display a warning message. This check can be
enabled/disabled as required.
To enable/disable the strategy sync check:
1. Run IQSET.
3. Select/clear the Disable Strategy Sync Check check box.

4. Click Exit.

Customise IQSET
6.5 Enable/Disable Background Compare

IQSET checks that the module parameters and values in the controller are the same as those in IQSET for each module
on the page. Modules for which the data does not match are highlighted in red, those for which the data is the same
are highlighted in green. This check can be enabled/disabled as required.
To enable/disable background compare:
1. Run IQSET.
3. Select/clear the Disable Background Compare check box.

4. Click Exit.

Customise IQSET
6.6 Set up Default Labels

IQSET enables a list of commonly used labels to be defined. A different list can be defined for sensors, digital inputs,
knobs, units, drivers, switches, and general labels this saves time re-entering the same text when modules are added.
The label at the top of the list is used as the default label. IQSET is shipped with some labels already specified,
however more can be added, or existing labels removed.
To add a label to a list:
1. Run IQSET.
3. Click Sensor, Digin, Knob, Units, Driver, Switch, or General to specify the list to which the label is to be
added. The required list will be displayed in the box below.
4. Click in the list at the point the label is to be added, and if necessary press ENTER to add a new line.
5. Enter the required label.
6. Click Exit.

Customise IQSET
To remove a label from a list:
1. Run IQSET.
3. Click Sensor, Digin, Knob, Units, Driver, Switch, or General to specify the list from which the label is to
be removed. The required list will be displayed in the box below.
4. Highlight the required label.
5. Right-click the highlighted label, and click Delete.
6. Click Exit.
The position of a label in the list can be changed by highlighting it, right-clicking and clicking Cut, and then right-
clicking in the list at the new position, and clicking Paste. This method can also be used to copy labels between lists.

Customise IQSET
6.7 Set up the Sensor Library

IQSET is supplied with a library of sensor definitions that can be used to set up the sensor type modules in the IQ
controllers. Each definition in the library stores all the information required to correctly set up the sensor type modules
to scale the input of a sensor into engineering units.
The sensor library contains the definitions for all the standard Trend sensors. If you regularly use other sensors, the
definitions for these can be added to the library. Once a definition has been added to the library it will be available in
all projects.
To add a sensor to the sensor library:
1. Open a project.
2. Display a strategy page.
3. Right-click the page, point to Device and click Sensor Types, or on the Device menu click Sensor Types.
The Sensor Type dialogue box is displayed.
4. In the Number box click an unused sensor type module, i.e. one identified just by a number in the list.
5. In the Sensor Part Number box enter the part number of the sensor.
6. In the Scaling Range box enter the range of the sensor.
7. In the Unique Sensor Reference box enter the reference for the sensor. It is recommended that this reference
consist of the part number followed by the range (e.g. PIL/4).
8. Click Edit.
9. In the Scaling box click the scaling type. The dialogue box changes to allow the appropriate parameters to
be specified.
Option Description
This type of scaling must be used on IQ3 and IQ4 controllers. It allows a sensor’s
characteristics to be defined by specifying up to twenty scaling points between which it
Characterise
interpolates. This provides higher accuracy than the other scaling types for non-linear
scaling
characteristics. It is therefore recommended for use with all non-linear sensors providing the
controller has version 2.1 firmware or greater. It is also used for lookup function modules.

Customise IQSET
Option Description
This type of scaling cannot be used on IQ3 and IQ4 controllers. It should be used for sensors
Linear scaling providing either a voltage or current signal with a linear characteristic between the top and
bottom of the range.
This type of scaling cannot be used on IQ3 and IQ4 controllers. Can be used instead of
linearise thermistor volts. It should be used for non-Trend sensors where the
resistance/temperature characteristic is known, as it requires entry of ohms against
Linearise temperature directly from the characteristic. It enables the linearisation points on the
thermistor ohms temperature scale to be individually chosen so that they can be closer together over a part of
the characteristic where the gradient is changing rapidly, and further apart where the gradient
changes only gradually. It is not recommended for use with Trend sensors (use Linearise
thermistor volts for these).
Linearise
This type of scaling cannot be used on IQ3 and IQ4 controllers. It should be used for
thermistor volts
thermistor sensors providing a voltage signal that needs to be linearised.
scaling
Linearise volts This type of scaling cannot be used on IQ3 and IQ4 controllers. It should be used for
scaling thermistor sensors providing a voltage signal that needs to be linearised.
This type of scaling cannot be used on IQ3 and IQ4 controllers. It is not normally used; it is
Log scaling for sensors providing either a voltage or current signal with a logarithmic characteristic
between the top and bottom of range.
10. Enter the required values or click on the required options to specify the sensor's parameters. Clicking Refresh
will display a graph of the sensor’s characteristics as defined by the current parameters. This can be used at
any point to check how the sensor reading will be scaled.
11. Once the parameters are correctly specified, click Save to Library.
12. Repeat steps (5) to (12) to add the definitions for other sensors to the library.
13. Click Exit.
Note: When adding a definition to the library, the sensor type module you select will be assigned the parameters for
the definition that has just been created.

Customise IQSET
6.7.1 Delete a Sensor Definition from the Library
Unwanted sensor definitions can be deleted. It is not possible to delete the definitions originally supplied with IQSET.
To delete a sensor definition:
1. Open a project.
4. In the Unique Sensor Reference box click the required sensor definition.
5. Click Edit.
6. Click Delete From Library. A dialogue box is displayed asking for confirmation of the deletion; click Yes.
7. Repeat steps (4) to (6) to remove any other definitions from the library.
8. Click Exit.

Customise IQSET
6.7.2 Edit a Sensor Definition
To edit a sensor definition:
1. Open a project.
4. In the Number box click an unused sensor type module.

5. In the Sensor Part Number box or Unique Sensor Reference box click the sensor definition that is to be
edited.
6. Click Edit.
7. Enter the required values or click on the required options to specify the definition’s parameters.
8. Once the parameters are correctly specified, click Apply.
9. Repeat steps (5) to (8) to edit other sensors.
10. Click Exit.
Note: It is not possible to edit the sensor definitions supplied with IQSET.
6.8 Set up the Strategy Library
The Strategy Library contains strategy blocks, which are standard pieces of strategy that can be re-used, and solutions
which are entire configurations for individual controller types. It is therefore recommended that strategy blocks and
solutions be created as appropriate for all the pieces of strategy and entire controller strategies that are regularly used.
IQSET is supplied with standard strategy blocks and solutions that can be used, or you can build up a library of
different strategy blocks for all the different standard pieces of strategy you use. If required location of the strategy
library can be changed.

Customise IQSET
6.8.1 Set up Strategy Blocks
When a strategy block is created all the links between modules are retained, as is the relative position of the modules
on the page, and their order in the sequence table. A single strategy block can be made up of several pages of strategy
that can either be used individually, or as a whole. Strategy blocks can be kept in groups (e.g. all AHU strategy blocks)
so that they can be located quickly when required. If required, each group can be divided using subgroups. It is also
possible to determine specific characters in the block that can be replaced with specific text e.g. to specify module
labels, when the strategy block is used. The strategy blocks you create are stored in Custom Library; strategy blocks
shipped with IQSET are stored in the Standard Blocks Area.
To set up strategy blocks:
1. Add the required strategy block groups.
2. Add the required strategy blocks.
3. Set up Strategy Block Page Details.
4. If required set the module start numbers.
6.8.1.1 Add a Strategy Block Group
To add a strategy block group:
1. Open a project and display the Strategy Library.
2. Right-click Custom Block, and click New Group. The Enter Group Name dialogue box is displayed.
3. In the box enter the name of the group.

4. Click OK.
5. Create any required strategy block sub groups as described below.
To add a strategy block sub group:
2. In the Strategy Blocks Area, right-click the group to which the sub group is to be added, and click New Sub
Group. The Enter Subgroup Name dialogue box is displayed.
3. In the box enter the name of the sub group.

4. Click OK.
To delete a strategy block group or sub group:
2. In the Custom Block Area, right-click the group or sub group that is to be deleted, and click Delete Group
or Delete Subgroup. If the group is not empty a dialogue box asking if you are sure you want to delete the
group is displayed.
3. Click Yes.
To rename a strategy block group:
2. Right-click the strategy block group that is to be renamed, and click Rename. The Rename dialogue box is
displayed.
3. In the box enter the new name.

4. Click OK.

Customise IQSET
6.8.1.2 Add a Strategy Block
To add a strategy block:
1. Create the necessary strategy block groups.
2. In the Strategy Library, right-click the strategy block group in which the strategy block is to be placed and
click New Strategy Block. The Strategy Block Properties dialogue box is displayed.
3. In the Block Name box enter the name of the strategy block.
4. In the Controller Type box select the type of controller for which the strategy block is to be used.
5. In the Firmware Ver box select the firmware version of controller for which the strategy block is to be used.
6. In the Revision box enter the revision number of the strategy block.
7. In the Group box click the strategy block group to which the strategy block is to be added.
8. In the Sub Group box click strategy block sub group to which the strategy block is to be added.
9. In the Language box click the language used for the labels of sensors, digital inputs, knobs, switches and
drivers in the strategy block. If the required language is not available, it must be added.
10. In the Key Search box enter any keywords that can be used to search for the strategy block.
11. In the Details box enter a description of the strategy block.
12. If place holder questions are to be used specify the question(s) that are to be asked in the Question column
and the text to be replaced by the user's input in the Placeholder column.
Note: If the strategy contains Interface modules you will be prompted to specify the Network module when
the strategy block is used.
13. Click OK. The new strategy block is created, with a blank page ready for strategy to be added. The
background of the strategy page changes to .
Note: The strategy page is green to indicate that a strategy block is being edited.
14. Create the strategy for the strategy block. Additional pages can be created for strategy by clicking .
If placeholder questions are to be used add the text that is to be replaced in the required locations e.g. module
labels. The text to be replaced can be located in module labels, text on strategy pages, and page descriptions.

Customise IQSET
If connectives are to be used to link modules on different pages it is necessary to ensure that each connective
has a unique label, and that any modules to which it links have the same label. You should also ensure that
the links between pages are backwards, i.e. from page 2 to page 1, but not from page 2 to page 3. When the
strategy block is used IQSET matches the label of the connectives with the labels of modules already in the
strategy and if a match is found the link is made. The pages in the strategy block are added in order therefore
the modules on page 3 of the strategy block will not have been added to the strategy when IQSET is trying
to find a match for a connective on page 2. If a match is not found the connective will be added as an
undefined connective that must be defined after the strategy block has been used.
15. Once the strategy block is complete click to close the strategy page. A dialogue box is displayed asking if
you want to save the changes.
16. Click Yes.
6.8.1.2.1 Delete a Strategy Block
To delete a strategy block:
1. Display the Strategy Library.
2. Right-click the strategy block to be deleted, and click Delete Strategy Block. A dialogue box asking if you
are sure you want to delete the strategy block is displayed.
3. Click Yes.
Note: Deleting a strategy block will delete all the pages containing its strategy. Strategy blocks in the Standard Block
Area cannot be deleted.
6.8.1.2.2 Edit Strategy Block Properties
To edit strategy block details:
1. Open a project.
3. Right-click the strategy block that is to be edited, and click Properties. The Strategy Block Properties
dialogue box is displayed.
4. Edit the details as required.
5. Click OK.
6.8.1.2.3 Copy a Strategy Block to the Custom Library
To copy a strategy block to the Custom Library:
1. Open a project.

Customise IQSET
3. In the Standard Block, section right-click the strategy block that is to be copied to the Custom Library,
and click Copy to Custom Library. The Strategy Block Properties dialogue box is displayed.
6. In the Firmware Version box select the firmware version of controller for which the strategy block is to be
used.
13. Click OK.
Note: Strategy blocks created using version of IQSET earlier than v6.0 are stored in the Old Library and can be
copied into the Custom Library. This enables old strategy blocks to be edited.
6.8.1.2.4 Duplicate a Strategy Block
To duplicate a strategy block:
1. Open a project.

Customise IQSET
3. In the Custom Block, section right-click the strategy block that is to be duplicated, and click Duplicate
Strategy Block. The Strategy Block Properties dialogue box is displayed.
6. In the Firmware Version box select the firmware version of controller for which the strategy block is to be
used.
13. If place holder questions are to be used specify the question(s) that are to be asked in the Question column
and the text to be replaced by the user's input in the Placeholder column.
Note: If the strategy contains Interface modules you will be prompted to specify the Network module when the
strategy block is used.
14. Click OK.
6.8.1.2.5 Edit Strategy Block Strategy
The strategy used by a strategy block’s can be edited. It is only possible to edit the strategy blocks in the Custom
Library. To edit a strategy block in the Old Library it is necessary to copy it to the custom library.
To edit strategy block strategy:
1. Open a project.
3. In the Custom Block Area, right-click the strategy block that is to be edited, and click Edit/View. The
strategy pages for the strategy block are loaded. The background of the strategy page changes to .
4. Click or to display the required page.
5. Edit the strategy.
6. Click to close the strategy page. A dialogue box is display asking if you want to save the changes.
7. Click Yes.
6.8.1.3 Set up Strategy Block Page Details
Strategy pages in a strategy block can be titled, and a text describing them added.

Customise IQSET
To set up a strategy block page:
1. Open a project.
3. Right-click the strategy block page whose details are to be edited, and click Properties. The Page Properties
4. In the Title box enter a title for the page.

5. In Details box enter the required details.
6. Click OK.

Customise IQSET
6.8.1.4 Set the Module Start Numbers for a Strategy Block
The module start numbers for the modules used in a strategy block can be specified. This enables you to ensure the
module umbers used when a strategy block is added to a blank controller. If the specified module is not available
IQSET will take the next free module after the number specified.
To set the module start numbers for a strategy block:
1. Add the strategy block.
2. Open a project.
4. Right-click the strategy block for which the module start numbers are to be specified, and click Properties.
The Strategy Block Properties dialogue box is displayed.
5. Check the Set Module Start check box. The text boxes in the Module Start area change so that the module
number can be edited.
6. Edit the module start numbers as required.
7. Click OK.

Customise IQSET
6.8.1.5 Translate Strategy Blocks
The labels of Sensor, Digital Input, Knob, Switch and Driver modules can be translated. When the strategy block is
used IQSET's default language is used to determine the language of the labels used. If the block has been translated
into IQSET's default language the translated labels are used otherwise the original labels are used.
Note: To use the translated labels you must set IQSET's default language to the required language.
To translate strategy blocks:
2. Click the next to the strategy blocks that are to be translated. IQSET will indicate the selected one with a
.
3. Click . The Strategy Translate dialogue box is displayed.
Note: If a language has not been defined for any of the selected strategy blocks an error is displayed and you
are given the option of specifying the language. Having done this return to step (1).
4. In the Current Language box click the language of the strategy block you want to translate from.
5. In the Translated Language box click the language the strategy block is to be translated into. If the required
language is not available, it must be added.
6. Double click in the Translated Label column for each label that is to be translated, and enter the translated
label. If a label is not to be included in the translation, select it and click Remove Label(s). If more than one
label is select all the selected labels will be removed.
7. Once all the labels have been translated click Save Changes.
If labels a strategy block has already been translated they can be imported.

Customise IQSET
6.8.1.5.1 Import Translated Labels
If the labels for a strategy block have already been translated, they can be imported.
To import translated labels:
1. Export the labels onto the required removable media.
2. Connect the removable media containing the exported translated labels.
4. Click the next to the strategy blocks into which the labels are to be imported. IQSET will indicate the
selected one with a .
6. If existing labels are to be overwritten with the one that are to be imported select the Override Existing
Labels check box.
7. Click Import. The Select translated labels File dialogue box is displayed.
8. In the folder list click the file that is to be imported. To select a file stored in a different location, click the
drive, or folder in the Look in box that contains the file, double-click the folders in the folder list until file
is displayed.

Customise IQSET
9. Click Open. The labels will be imported; a dialogue box is displayed when the process is complete.
6.8.1.5.2 Export Translated Labels
If you have already translated labels for strategy blocks they can be exported for use on another PC.
To export translated labels:
1. Connect the removable media that is to be used.
3. Click the next to the strategy blocks from which the labels are to be exported. IQSET will indicate the
selected one with a .
5. Click Export. The Enter translated labels export name dialogue box is displayed.
6. In the File name box enter the required file name. To store the file in a different location, click the drive, or
folder in the Look in box that contains the file, and double-click the folders in the folder list until the file is
displayed.
7. Click Save.

Customise IQSET
6.8.2 Set up Solutions
Solutions enable the entire strategy for a controller to be stored and easily reused. Solutions can be kept in groups so
that they can be located quickly when required. If required, each group can be divided using subgroups. The solutions
you create are stored in Custom Solution Library; solutions shipped with IQSET are stored in the Standard Solution
Library.
To set up solutions:
1. Add the required solution groups.
2. Add the required solutions.
6.8.2.1 Add a Solution Group
To add a solution group:
2. Right-click Custom Solution, and click New Group. The Enter Group Name dialogue box is displayed.
3. In the box enter the name of the group.

4. Click OK.
5. Create any required solution sub groups as described below.
To add a solution sub group:
1. In the Solutions Area, right-click the group to which the sub group is to be added, and click New Sub Group.
The Enter Subgroup Name dialogue box is displayed.
2. In the box enter the name of the sub group.

3. Click OK.
6.8.2.1.1 Delete a Solution Group
To delete a strategy block group or sub group:
2. In the Custom Solution Area, right-click the group or sub group that is to be deleted, and click Delete
Group or Delete Subgroup. If the group is not empty a dialogue box asking if you are sure you want to
delete the group is displayed.
3. Click Yes.

Customise IQSET
6.8.2.2 Add a Solution
To add a solution:
1. Create the necessary solutions groups.
2. In the Device View right-click the controller that is to be added as a solution and click Copy to Solution.
The Solution Properties dialogue box is displayed.
3. In the Solution Name box enter the name of the solution.

4. In the Revision box enter the revision number of the solution.
5. In the Group box click the solution group to which the solution is to be added.
6. In the Sub Group box click sub group to which the solution is to be added.
7. In the Key Search box enter any keywords that can be used to search for the solution.
8. In the Details box enter a description of the solution.
9. Click OK.
6.8.2.2.1 Delete a Solution
To delete a solution:
2. Right-click the solution to be deleted, and click Delete Solution. A dialogue box asking if you are sure you
want to delete the solution is displayed.
3. Click Yes.
Note: Solutions in the Standard Solutions Area cannot be deleted.

Customise IQSET
6.8.3 Import Strategy Blocks and Solutions
If you have already set up strategy blocks and solutions on another PC they can be imported to your current PC.
To import strategy blocks and solutions:
1. Export the strategy blocks and solutions onto the required removable media.
2. Connect the removable media containing the exported strategy blocks and solutions.
4. Click . The Select block zip file to import dialogue box is displayed.
is displayed.
6. Click Open. The file will be imported. If a strategy block or solution already exist IQSET asks if it should
be overwritten.

Customise IQSET
6.8.3.1 Export Strategy Blocks and Solutions
If you have already set up strategy blocks and solutions, they can be exported for use on another PC.
To export strategy blocks and solutions:
3. Click the next to the strategy blocks and solutions that are to be exported. IQSET will indicate the selected
one with a .
4. Click . The Enter block zip file name dialogue box is displayed.
displayed.
6. Click Save. A dialogue box is displayed when the process is complete.

Customise IQSET
6.9 Set up the States Category Library

The States Category library contains predefined lists of states labels that can be used to define the states used by States
Category modules. IQSET is supplied with standard definitions that can be used, or you can build up a library of
different definitions to suite your requirements.
To set up the states category library:
1. Run IQSET.
2. On the Tools menu click States Category Library. The States Category Library dialogue box is displayed.
3. Set up the required states categories.

Add a states category:
 Click .
 Enter the label in the Label box.
 Select the required number of states in the Number of States box.
 Click in the State column for each state and enter the required text.
 Click .
Delete a states category:
 Select the state category in the Label box.
Note: The predefined states ( ) supplied with IQSET cannot be deleted.
 Click .
Edit a states category:
 Select the state category in the Label box.
Note: The predefined states ( ) supplied with IQSET cannot be edited.
 Edit the number of states and states text as required.
 Click .
Copy a states category:
 Select the state category that is to be copied in the Label box.
 Click . The new states category is added.
 Edit the label, number of states and states text as required.
 Click
Undo a change:
 Click .
Export a states category:
 Select the state category that is to be exported in the Label box.
 Click . The Save As dialogue box is displayed.

Customise IQSET
 In the File name box enter the required file name. To store the file in a different location, click the drive,
or folder in the Look in box that contains the file, and double-click the folders in the folder list until the
file is displayed.
 Click Save. The state category will be exported to a .sclx' file in the specified location.
Import a states category:
 Click . The Open dialogue box is displayed.
 Click the file that is to be imported. To select a file stored in a different location, click the drive, or folder
that contains the file.
 Click Open. The state category will be exported to a .sclx' file in the specified location.
4. Click Close.
6.10 Specify Auto Edit
When Auto Edit is enabled, IQSET will automatically display the relevant properties dialogue box when the module
is first placed on a strategy page.
To enable/disable Auto Edit:
1. Run IQSET.
3. Click Auto Edit.

4. Click Exit.

Customise IQSET
6.11 Specify Company Information

IQSET enables the company logo printed on the front sheet for each controller to be changed, to suit individual
requirements (e.g. your company’s logo). The company address can also be changed from the default to your
company's address.
Note: The company name is the name entered in the Licence box, and can only be changed by re-licenseing IQSET
specifying a different company name.
To specify the company logo:
1. Create the company logo using any graphics package. The final size of the logo should be 1718 x 500 pixels.
2. Save the file as a BMP file called company.bmp.
3. Move the file to the 'c:\Users\Public\Public Documents\System Engineering Tool\Company Info' directory,
to overwrite the existing file.
To specify the company address:
1. Run IQSET.

Customise IQSET
3. In the Company Details area click Edit. The Company Details dialogue box is displayed.
4. In the five Address Line boxes enter the company address.

5. In the Telephone box enter the telephone number.
6. In the Fax box enter the fax number.
7. In the Email box enter the Email address.
8. Click OK to return to the SET Options dialogue box.
9. Click Exit.

Customise IQSET
6.12 Specify File Backup Options

Whenever a project is closed IQSET is automatically makes a backup of the file. This backup is stored in the same
directory as the original file using the same filename but with the file extension .bak. If required this functionality can
be turned off, or IQSET can be made to keep two backups. If two backups are made, the second will have the file
extension .bak2.
To specify the file backup options:
1. Run IQSET.
3. In the File Backup Options area click the required option.

Option Description
1 Backup When selected, IQSET keeps only the latest backup.
2 Backups When selected, IQSET keeps the last two backups.
No Backup When selected, IQSET will not perform any automatic backups.
4. Click Exit.
To restore a backup, delete the original IQ, or TSET file, and rename the backup file.

Customise IQSET
6.13 Specify Module Tracking

IQSET can be configured so that during live edit the module selected on the strategy page is selected in the System
View.
To specify module tracking:
1. Run IQSET.
3. Click Track modules in Live Edit.

4. Click OK.

Customise IQSET
6.14 Specify IQSET's Default Language

IQSET's default language determines the language used for the labels of sensors, digital inputs, knobs, switches and
drivers in strategy blocks, and the language used for the text that appears on the front page, title blocks, and tables that
are printed out. If the required language is not available, it can be added as described below however new languages
cannot be used for the printouts.
Note: For the strategy blocks to use labels in IQSET's default language they must have been translated as described
in the 'Translate Strategy Blocks' section of this manual.
To specify IQSET's default language:
1. Run IQSET.
3. In the Default Language box click the required language. If the required language is not in the list, click
Add Language and enter the new language in the displayed dialogue box. To delete a language select it in
the Default Language box, and click Delete Language.
Note: New languages can only be used for translation of strategy blocks, deleting a language will delete all
translation for that language. If the language you require for the strategy print labels does not exist, contact
Trend via your normal channel.
4. In the Default language box click the required language.
5. Click Exit.

Customise IQSET
6.15 Specify Standard Comms Connections

A comms connection specifies how IQSET communicates with the Trend network, or with a directly connected IQ
controller. IQSET is supplied with several standard connections that cover the most common types of connection.
Connection Description
Comm 1 [19200]
Connection using COM 1 at 19200 baud.
Connection
Comm 1 [9600]
Connection
Comm 2 [19200]
Connection
Comm 2 [9600]
Connection
TCP/IP connection using a device with an IP address of 0.0.0.0. With ports 10004, 10005,
TCP Connection
10006, 100057 available for connection.
If these are not suitable, additional ones can be added.
Note: For the connection to work the appropriate physical connections must have been made.
To specify a comms connection:
1. Run IQSET.
2. On the Tools menu click ToolSET Options. The ToolSET Options dialogue box is displayed.
3. Click Add. This displays the TUA Editor Window.
4. Use the TUA Editor to specify the connection.

5. Click OK.

Customise IQSET
6.15.1 Delete a Standard Comms Connection
If there are standard comms connections that are not required, they can be deleted.
To delete a comms connection:
1. Run IQSET.
3. In the TUA box click the required connection.

4. Click Delete. The selected connection will be deleted.
5. Click OK.
6.15.2 Edit a Standard Comms Connection
Existing standard comms connections can be edited.
To edit a comms connection:
1. Run IQSET.
3. In the TUA box click the required connection.

Customise IQSET
4. Click Edit. The TUA dialogue box is displayed.
5. Use the TUA Editor to edit the connection.

6. Once the settings are correct click OK to return to the ToolSET Options dialogue box, and then click OK.
6.16 Specify the Default Comms Connection
IQSET allows different connections for the comms port to be stored, and recalled quickly.
To specify the default comms connection:
1. Run IQSET.
3. In the Default Comms Settings box click the required comms connection.
4. Click Exit.

Customise IQSET
6.17 Specify the Default Controller for New Controllers

The default device type, firmware version, hardware variant and options for each controller range used when a new
controller is added to the project can be specified. The default range cannot be specified, IQSET will use the range
used previously. This means that if you regularly use a controller type you can set it to be the default saving time when
adding new controllers.
To set up the default controller:
1. Display the Project View.
2. In the Device View right-click a LAN, point to Insert Device and click IQ Controller. The Controller
Selection dialogue box is displayed.
3. In the Range area click the required option (IQ1, IQ2, IQECO, IQ3, or IQ4) to specify the required range.
4. To only show choices for controllers with node controller functionality select the Node Controllers check
box.
5. In the Device Type box click the device type to be used as the default.
6. In the Firmware Version box click the firmware version to be used as the default.
7. In the Hardware Variant box click the hardware variant of the IQ controller to be used as the default.
8. In the Options area select the required check box(s) to specify the options (e.g. BACnet) to be used as the
default.
Note: These options are only displayed if available with the option selected in the Firmware Version box.
9. In the Controller area click Set Default.
10. Repeat steps (3) to (9) for each controller range.
11. Click Cancel to close the Controller Selection dialogue box.
The default device type, firmware version, hardware variant, and options can be set for each controller range by
repeating the steps above for each of the different controller ranges.

Customise IQSET
6.18 Specify the Default Display Language

Specify the Default Display Language for IQ3 and IQ4 Controllers
For IQ3 controllers with version 1.1 firmware or greater and IQ4 controllers the language used for the display of web
pages and alarms can be specified.
To specify the default display language:
1. Open a project.
2. Display a strategy page for the controller for which the default display language is to be specified.
3. On the Device menu click Address Module. The IQ Address Module dialogue box is displayed.
4. In the Available Display Languages box click the language that is to be the default.
5. Click .
6. Click OK.

Customise IQSET
Specify the Default Display Language for Pre IQ3 Controllers
Pre IQ3 controllers have a parameter in the address module, which specifies the language used by a Display Panel
connected to the controller, and the language in which text alarms are sent. The Network Display Panel also uses this
parameter to determine in which language to display its prompts.
The display language can be set to English, Spanish, Finnish, Swedish, Norwegian, Danish, German, Italian,
Portuguese or French. The default is English, and should be set to the language you require most often.
To specify the default display language:
1. Open a project.
2. Display a strategy page for the pre IQ3 controller for which the default display language is to be specified.
3. On the Device menu click Address Module. The IQ Address Module dialogue box is displayed.
4. In the Display Language box click the language that is to be the default.
5. Click .
6. Click OK.
6.19 Specify the Default Display Options
The configuration parameters displayed on the strategy page for each different type of module is different. The default
for each type of module is for all the parameters that can appear on the page to be displayed. If required, the default
for each type of module can be changed.
To set up the default display options:
1. Open a project.
2. Display a strategy page that contains a module of the type for which the default display options are to be
changed.
3. Right-click a module of the type for which the default display options are to be changed, and click Edit
Parameters. The Parameters dialogue box for that module type is displayed.
4. Select the appropriate check boxes on the left of the dialogue box to specify the module parameters that are
to be displayed. Clicking will select all the check boxes, clicking will clear all the check boxes, and
clicking will return the display setting to the current defaults.
5. Click .
6. Click OK.

Customise IQSET
6.20 Specify the Default Print Options

The default print options can be specified to save time when printing project documentation. The defaults will be used
when is selected.
To set up the default print options:
1. Open a project.
2. On the File menu click Print. The Print dialogue box is displayed.
3. In the Print what area, select the appropriate check boxes to specify the default print options. To select all
options click Select All.
Option Description
Prints a list of the strategy pages using the page details as a title sorted in page
Contents
order.
Strategy Prints strategy pages.
Sensor List Prints a list of all the sensors in the strategy.
Digital Inputs List Prints a list of all the digital inputs in the strategy.
Knobs List Prints a list of all the knobs in the strategy.
Switch List Prints a list of all the switches in the strategy.
Drivers List Prints a list of all the drivers in the strategy.
Time Schedule List Prints a list of all the time zones in the strategy.
Sequence List Prints the sequence table.
Plots List Prints a list of all the plot modules in the strategy.
IC Comms List Prints a list of all the IC comms modules in the strategy.
Analogue Nodes Used
Pre IQ3 controllers only. Prints a list of all the analogue nodes in the strategy.
List
Digital Nodes Used List Pre IQ3 controllers only. Prints a list of all the digital nodes in the strategy.
Module Used List Prints a list of all the modules used in the strategy.
Sensor Types Prints a list of all the sensor type modules in the strategy.
Directory Modules List Prints a list of all the directory modules in the strategy.
Display Modules List Prints a list of all the display modules in the strategy.
Alarm Groups Prints a list of all the alarm group modules in the strategy.
XNC Interface Module
/XNC controllers only: Prints a list of the XNC interface module in the strategy.
List

Customise IQSET
Option Description
Prints a list of the strategy pages using the page details as a title sorted in alphabetic
Index
order.
4. Click Set Default.
5. Click OK.
6.21 Specify the Gap in the Sequence Table Between Pages
When a new page is created after existing pages using the New Page button ( ) or from the Project View, IQSET
automatically leaves a gap in the sequence table. This means that modules can be added to one page without the need
to change the sequence steps of modules on the next. This gap is NOT inserted when a page is inserted before another.
E.g. If the last sequence step on page 2 was 20, and the number of sequence steps between pages to be skipped was
10, when page 3 is created a gap of 10 sequence steps would be left. This would mean that the sequence step of the
first module on page 3 would be 31.
Note: This setting applies to all projects. The gap is only left when the page is created; as modules are added to the
previous page, the gap will get smaller.
To specify the gap in the sequence table between pages:
1. Open a project.
3. Click , or on the Tools menu point to Sequence Steps and click Skip. The Sequence Steps to Skip
4. In the box enter the number of sequence steps that are to be skipped between pages. Range 0 to 50.
5. Click OK.

Customise IQSET
6.22 Specify the Time Difference

If the controller time/date check is enabled when IQSET attempts to communicate with a device to upload or download
strategy it will check that time in the controller is within a specified amount of the PC clock. If there is a difference
IQSET will then prompt you to update the controller's time. The difference of the controller's time to the PC time
before IQSET will prompt to update the time can be changed.
To specify the time difference:
1. Run IQSET.
3. In the Difference in Minutes box enter the required times difference in minutes.
4. Click Exit.
6.23 Specify the Toolbar Theme
The appearance of the toolbars can be changed by specifying a different theme.
To specify the toolbar theme:
1. Open a project.
2. On the View menu point to Theme and click the required theme.

Customise IQSET
6.24 Specify IQ3 or IQ4 Directory Module Parameter Defaults

The default values for directory module parameters can be specified.
To set up directory module parameter defaults:
1. Open a project.
2. Display a strategy page for an IQ3 or IQ4 controller.
3. Click , or on the Tools menu click Display and Directory Setup. The Display and Directory Setup
4. In the Themes area click Edit next to the Directory box. The Directory Themes dialogue box is displayed.
5. In the Pin level box enter the PIN level required to access the module. This can be in the range (1 to 99). The
can be used to set the required value.
6. Specify default background colour for the page by clicking Background Colour, clicking Change to display
the Color dialogue box, clicking the required colour and then clicking OK to return to the Directory Themes
dialogue box. Custom colours can be used by clicking Define Custom Colors>> in the Color dialogue box.
If a background colour is not required, clear the Background Colour check box.
7. In the Refresh Rate enter the default refresh rate in seconds.
8. Specify the size of the page. In the Width box enter the default width of the page in pixels, and in the Height
box enter default the height of the page in pixels. Alternatively, in the Page Size box click the default page
size.
9. Click OK to return to the Display and Directory Setup dialogue box.

Customise IQSET
6.25 Specify IQ3 or IQ4 Display Module Parameter Defaults

The default values for display module parameters can be specified.
To set up display module parameter defaults:
1. Open a project.
2. Display a strategy page for an IQ3 or IQ4 controller.
4. In the Themes area click Edit next to the Display box. The Display Themes dialogue box is displayed.
5. In the Pin level box enter the PIN level required to view or use the module. This can be in the range (1 to
99). The can be used to set the required value.
6. Specify the default foreground colour for the item by clicking Foreground Colour, clicking Change to
display the Color dialogue box, clicking the required colour and then clicking OK to return to the Styling
If a background colour is not required, clear the Foreground Colour check box.
7. Specify the default background colour for the item by clicking Background Colour, clicking Change to
display the Color dialogue box, clicking the required colour and then clicking OK to return to the Styling
If a background colour is not required, clear the Background Colour check box.

Customise IQSET
8. Specify the default colour used for the dynamic display modules when the item is in an alarm by clicking
InAlarm Colour, clicking Change to display the Color dialogue box, clicking the required colour and then
clicking OK to return to the Styling dialogue box. Custom colours can be used by clicking Define Custom
Colors>> in the Color dialogue box. If a background colour is not required, clear the InAlarm Colour.
9. In the Font Type box click the default font.
10. In the Font Size box click the default font size.
11. In the Width box enter the default width of the object in pixels. To size the text to fit click Width.
12. In Text Align box click the default text alignment that is used if a specific object width is specified. You
should ensure that the Width check box is clear.
13. Click OK to return to the Display and Directory Setup dialogue box.
6.26 Specify the Loading and Saving of Site Data
It is possible to specify what information from the System View is saved when IQSET is closed.
To specify the loading and saving of site data:
1. Run IQSET.
3. Click the required option.
Option Description
All Site Data All data in the System View will be saved.
No Data No information in the System View will be saved.
Site, LAN, and Controllers Only the basic LAN and controller structure of the site will be saved.
Site, LAN, and Controllers The basic LAN and controller structure of the site will be saved plus details of
and IO any I/O modules.
4. Click OK.

Customise IQSET
6.27 Specify the Printer

The printer used by IQSET to print out the project documentation can be specified. If a printer is not specified, IQSET
will use the Windows default printer.
To specify the printer:
1. Run IQSET.
2. On the File menu click Print Setup. The Print Set up dialogue box is displayed.
3. In the Name box click the printer. To set up the printer click Properties.
4. In the Size box click the paper size.
5. In the Source box click the paper source.
6. In the Orientation area click either the Portrait, or Landscape. Landscape is recommended.
7. Click OK.
6.28 Specify the Priority Array Labels
The default priority array label that is displayed on the driver module when in Live Values can be specified.
Note: Any labels that are left blank will appear as Level followed by the level number e.g. 'Level 3'.
To specify the priority array labels:
1. Run IQSET.
2. On the Tools menu click BACnet Options. The BACnet Options dialogue box is displayed.
3. Double click the label that is to be changed in the Label column and enter the new label (max 15-characters).
4. Click away from the label.
5. Click OK.

Customise IQSET
6.29 Specify the Refresh Options

The refresh options determine the way in which the System View is refreshed. There are two refresh options, the
'Refresh' action which determines the amount of information about the selected node that is discovered, and the 'Site
refresh action' which determine how much of a site is refreshed.
To specify the refresh options:
1. Run IQSET.
3. In the Refresh action area click the required option to specify the refresh action.
Option Description
Discover all sub node details Information about the selected node and nodes directly below it is discovered.
Discover types/Values of Information about the selected node is discovered along with the structure of
sub-nodes nodes directly below it.
Simple node discover Only information about the selected node is discovered.
4. In the Site Refresh action area click the required option to specify the site refresh action.
Option Description
Show internetwork Displays only an icon for the local LAN, and displays an icon for the internetwork (if
population available) along with the internetwork structure.
Show local lan Displays an icon for the local LAN along with its structure, there is no icon for the
population internetwork.
Show only basic site Displays only an icon for the local LAN, and one for the internetwork (if available).
structure The structure of the internetwork and local LAN is not discovered.
Note: The amount of information discovered about each of the devices displayed in the structure is
determined by the Refresh action.
5. Click OK.

Customise IQSET
6.30 Specify Where Strategy Blocks are Stored

All the files relating to a strategy block are stored in a sub-directory of the custom strategy library base directory.
Strategy blocks created using an earlier version of IQSET are stored in the old plant block directory. If required these
directories can be changed.
To specify where strategy blocks are stored:
1. Run IQSET.
3. To change the location of strategy blocks click Edit in the User Strategy Library Base Directory area. To
change the location of strategy blocks created in earlier version of IQSET click Edit in the Old Plant Block
Directory area. The Browse for Folder dialogue box is displayed.
4. Click the required directory. If necessary, use the scroll bars to move up/down the list. To create a new
directory, navigate to the required location and click Make New Folder.
6. Click Exit.

Customise IQSET
6.31 Specify Where Projects are Stored

All the files relating to a project are stored in a sub-directory of the base project directory (c:\set projects). The location
of the base project directory can be changed if required.
To change the location of the base project directory:
1. Run IQSET.
3. In the Base Project Directory area click Edit. This displays the Browse for Folder dialogue box.
4. Click the required directory. If necessary, use the scroll bars to move up/down the list.
6. Click Exit.

Customise IQSET
6.32 Specify Module Prompts

IQSET can be configured to prompt for the module number and sequence step of modules when they are added. A
separate setting is available for each type of module.
To specify module prompts:
1. Open a project.
3. Click , or right-click the page and click Next Module. The Next Module List dialogue box is displayed.
4. Click the check box next to each module type that will prompt for the module number and sequence step.
5. Click OK.
6.33 Specify Whether the Tracker Window Displayed
It is possible to specify whether the Tracker Window is displayed when IQSET is run.
To specify whether the Tracker Window is displayed:
1. Run IQSET.
3. Click Show Tracker Window to display the Tracker Window.

4. Click OK.

Customise IQSET
Note. The Tracker Window can always be displayed/hidden later clicking Tracker View on the View menu.
6.34 Specify Which Toolbars Are Displayed
The toolbars displayed by IQSET can be specified to suit individual requirements.
To specify which toolbars are displayed:
1. On the View menu click Toolbars, and then click the name of the toolbar that is to be displayed. For example,
to turn the Drivers toolbar OFF, on the View menu click Toolbars, and then click Drivers to remove the
tick. To display all the toolbars on the View menu click Toolbars, and then click Display All Toolbars.
If required, the toolbars can be moved by dragging them to the required position. When positioned on an edge of the
screen, they appear as normal toolbars, when positioned elsewhere, they appear as floating toolbars.
If a toolbar shrinks so that all its buttons cannot be displayed clicking will show all the hidden buttons.
6.35 Translate Print Labels
It is possible to translate the text that appears on the front page, title blocks, and tables that are printed out.
Note: This functionality is not available to all users, only approved Trend support personnel. This is to ensure there
is consistent labelling and the translation is only conducted once per language.
To translate print labels:
1. Run IQSET.

Customise IQSET
3. Click Translate Print Labels. The Strategy Translate dialogue box is displayed.
4. In the Translated Language box click the language the print labels are to be translated into. If the required
language is not available, it must be added.
5. Double click in the Translated Label column for each label that is to be translated, and enter the translated
label.
6. Once all the labels have been translated click Save Changes.
Note: To use the translated labels you must set IQSET's default language to the required language.

Customise IQSET
6.35.1 Import Translated Print Labels
If the print labels have already been translated they can be imported from another PC.
To import translated labels:
1. Export the labels onto the required removable media.
2. Connect the removable media containing the exported translated labels.
5. If existing labels are to be overwritten with the one that are to be imported select the Override Existing
Labels check box.

Customise IQSET
6. Click Import. The Select translated labels File dialogue box is displayed.
is displayed.
8. Click Open. The labels will be imported. A dialogue box is displayed when the process is complete.
6.35.2 Export Translated Print Labels
If the print labels have already been translated they can be exported for use on another PC.
To export translated labels:

Customise IQSET
4. Click Export. The Select translated labels File dialogue box is displayed.
displayed.
6. Click Open.
6.36 Turn Auto Routing ON/OFF
IQSET will automatically route the links between modules around the items on the page. If required, automatic routing
can be switched ON or OFF as required.
To switch auto routing ON/OFF:
1. Open a project.
3. Click , or on the Edit menu click Auto Routing.

Customise IQSET
6.37 Turn Module Tool Tips ON/OFF

When module tool tips are turned on, IQSET will automatically display the parameters for a module when the mouse
is placed over it. Module Tool Tips can be switched ON or OFF as required.
To turn module tool tips ON/OFF:
1. Run IQSET.
2. On the Tools menu click SET Options. This displays the SET Options dialogue box.
3. Select the Module Tool Tips check box.

4. Click Exit.
6.38 Turn Tip of the Day ON/OFF
If tip of the day is turned ON whenever IQSET is run the Tip of the Day dialogue box is displayed providing useful
information about IQSET and its use.
To turn tip of the day ON/OFF:
1. Run IQSET.
2. On the Help menu click Tip of the Day. This displays the Tip of the Day dialogue box.
3. Clear the Show Tips on StartUp check box to turn the tip of the day OFF, select it to turn tip of the day ON.
4. Click Close.

Customise IQSET

Quick Tours
7 QUICK TOURS
The Quick Tours are designed to show you the many features of IQSET. By following the tours, you will learn the
basics of using IQSET to engineer a Trend system.
There are three tours:
 The first Quick Tour 1 - The Basics: Shows you how to get started by creating a basic project, with simple
strategies, documenting it, and creating a file ready for downloading to the controller.
 The second Quick Tour 2 - Beyond Basics: Shows you to use the more advanced features of IQSET, such
as strategy blocks, Display and Directory modules, connectives, and editing the sequence table.
 The third Quick Tour 3 - Making IQSET Work for You: Shows you how to get the best out of IQSET by
creating your own strategy blocks, adding your own sensor definitions to the library, and using IQSET to
reverse engineer a controller.
If you require more information than that provided in the tours, the rest of this manual provides descriptions of all the
tasks that can be carried out using IQSET.
7.1 Quick Tour 1 - The Basics
This tour is a step-by-step tutorial that shows you how easy it is to use IQSET to engineer a Trend system. This tour
will show you how to create a simple project containing a single IQ controller, document it, and create an IQ4 file
ready for downloading to the controller.
Lesson 1- Creating an IQSET Project
In this lesson, you will learn how to run IQSET, and create a new project. You will also learn about the SET Window.
 Starting IQSET
 Creating a new IQSET Project
 Understanding the SET Window
Lesson 2 - Adding a controller
In this lesson, you will learn how to add a LAN, and an IQ controller to the project.
 Adding a LAN
 Adding an IQ controller
 Setting up the Address Module
 Setting up the Ethernet IP Module
 Setting up the Sensor Type Modules
Lesson 3 - Configuring the Strategy
In this lesson, you will learn how to add modules to the strategy, edit module parameters, link them together, and add
extra pages.
 Adding Modules to the Strategy
 Moving Modules
 Editing Modules
 Linking Modules
 Adding Pages
Lesson 4 - Documenting the Strategy
In this lesson, you will learn how to control the version of the strategy, and print out a comprehensive report
documenting the strategy.
 Defining the Strategy’s Issue
 Printing Project Documentation
Lesson 5 - Creating a Downloadable File
In this lesson, you will learn how create a file for an individual IQ controller that can be downloaded to the controller
using IQSET or another tool.
 Creating an IQ4 File

Quick Tours
7.1.1 Lesson 1 - Starting IQSET
Before you can use IQSET it is necessary to start it. See the 'Run IQSET' section of this manual for details. Once
started IQSET will display a dialogue box that provides access to the different functions of IQSET.
7.1.2 Lesson 1 - Creating a New IQSET Project
Every time you start IQSET, it lets you choose to open an existing project, create a new one, or to access other
functions. For this tour, you will start from scratch, and create a new project.
Creating a new project:
1. In the SET dialogue box, click Create New SET Project.
2. Click OK. The New Set Project dialogue box is displayed. This dialogue box allows the details of the project
to be specified.
3. In the Project Name box enter SET Tours to specify the name of the project.
4. In the Project Number box enter 12345678 to specify the project number.
5. In the Client box enter My Company Ltd to specify the client of the project.
6. In the Project Details box enter IQ4 SET Tour Project to specify the project details.
7. In the Site Name box enter SET Tour Project to specify the human readable site code for devices in the
project.
Note that all devices in the project will be assigned the same human readable site code.
8. Check the machine-readable site code displayed in the Site GUID box. A new code can be generated by
clicking Change. For the purposes of this tour use the one generated.
Note: All devices in the project will be assigned the same machine-readable site code.
9. Click OK.
IQSET will now create the project. A directory with the name specified as the project name is created in the 'Set
Projects' directory. In this case a directory called 'IQ4 SET Tours' will be created.

Quick Tours
7.1.3 Lesson 1 - Understanding the SET Window
Once the project has been created, IQSET will display the project in the SET Window. The SET Window has three
main areas:
 Strategy Library
The Strategy Library displays the reusable pieces of strategy (strategy blocks) and reusable strategies
(solutions) that have been created, and enables them to be used.
 Project View
The Project View displays information about the devices that have been added to the project, and the strategy
associated with them.
 Display Area
The Display Area displays the information that has been requested. Items launched from IQSET are
displayed in this area as a separate window in their own tab. Windows in this area can be positioned as
required either manually by resizing, and moving or using the Tile command, or the Window Position
toolbar.

Quick Tours
7.1.4 Lesson 2 - Adding a LAN
After the project has been created, the next step to engineering the system is to add the controllers to the project.
Before this can be done, the LANs on which they sit must be added to the project. For this tour, you will add a single
LAN (LAN 99).
Adding a LAN:
1. If the Project View is not displayed click to display it, and then in the Device View right-click SET
Tours and click Insert LAN. The Lan Details dialogue box is displayed.
2. In the Lan Number box enter 99 to specify the number of the LAN that is to be added.
3. In the Type box click Trend-IQ.
4. In the Label box enter SET Tours to define the label for the LAN.
5. In the Details box enter Contains controllers for the SET Tours to specify a description for the LAN.
6. Click OK. The LAN will be added to the Device View as shown.

Quick Tours
7.1.5 Lesson 2 - Adding an IQ Controller
Once the LANs have been added to the project, the controllers for which the strategy is to be created need to be added
to the Device View. For this tour, you will add a single IQ4E/16 v3.3 at address 24 on LAN 99.
Adding an IQ controller:
1. In the Device View right-click LAN 099, which is the LAN to which the controller is to be added, click
Insert Device and click IQ Controller. The Controller Selection dialogue box is displayed.
2. In the Range area click IQ4.

3. In the Device Type box click IQE to define the type of controller.
4. In the Firmware Version box click 3.5 to define the firmware version of controller.
5. In the Hardware Variant box click IQ4E/16 from to define the hardware variant of controller.
6. Click OK. The Device Details dialogue box is displayed.
7. In the Address box enter 24 to specify the network address of the controller.
The network address is the address of the controller on the Trend network, set on the controller’s address
switch. It can be set anywhere in the range 1 to 119 excluding addresses 2, 3, and 10. Each address on a LAN
must be unique.
8. In the Name box enter SET Tours Controller 1 to specify the name for the controller.
The details entered about the project have been automatically entered in the Details box if required this can
be changed. For this tour leave it unchanged.

Quick Tours
9. In the Details box enter SET Tours Controller 1.
10. In the Engineer box enter your own name to specify the name of the engineer who designed the strategy.
The engineer's name specifies the name of the engineer who has designed the strategy. This is useful if
someone other than the engineer who designed the strategy is creating the IQSET project.
11. Click OK. The IQ Address Module dialogue box is displayed. It is possible to specify the address module
parameters now, or leave it until later.
12. For the purposes of this tour, click OK to leave it until later, and move on to the next stage. The User
Parameters dialogue box is displayed. This enables you to set up the controller's security. IQSET will force
you to create an Admin User, and normal User.
13. The Name box enable the name for the admin user to be specified. For the purposes of this tour leave it as
'Admin User'.
14. In the Password box enter Tour Admin to specify the user's password.
15. In the Pin box enter 1234 to specify the user's PIN.
16. Leave the other parameters at their default values and click OK. The Sensor Type dialogue box is displayed.
This enables the sensor type modules to be specified now, or later.
17. For the purposes of the tour click Exit to leave it until later.
IQSET will now add the new controller to the Device View, and display a blank strategy page.

Quick Tours
7.1.6 Lesson 2 - Setting Up the Address Module
Before continuing with specifying the strategy for the controller, it is necessary to go back, and set up the Address
module. Normally, you would do this when the controller was added.
Setting up the Address module:
1. Currently the strategy page created for the controller should be displayed. On the Device menu click Address
Module. The Address Module dialogue box is displayed.
You will notice that several of the parameters are greyed out this is because this information would normally
be set up using the IP Tool. If the Not Sent check box next to a parameter is selected the parameter will be
greyed out and not included in the strategy file when it is created. For the purposes of this tour we shall
assume that the following parameters have been set up using IP Tool: Identifier, Local LAN, Local Node,
and Supervisor Port Address.
2. In the Attribute F (2) box enter FLR4:*.
This is an optional 30-character label for the controller, which allows the controller to be identified, either
uniquely, or as part of a group. It is used in conjunction with the identifier, and the other attributes.
All the other parameters are set up in a similar way by entering the required value into dialogue box, or
making selections from the list. The rest of the parameters do not need to be specified for this tour.
3. Click OK. The dialogue box is closed.

Quick Tours
7.1.7 Lesson 2 - Setting Up the Ethernet IP Module
After setting up the address module it is necessary to set up the Ethernet IP module.
Setting up the Ethernet IP module:
1. Currently the blank strategy page created for the controller should be displayed. On the Device menu click
Ethernet IP Module. The Ethernet IP Module dialogue box is displayed.
You will notice that some of the parameters are greyed out this is because this information would normally
be set up using IP Tool. If the Not Sent check box next to a parameter is selected the parameter will be greyed
out and not be included in the data file.
2. In the LAN Label box enter SET Tours.
3. Clear the Not Sent check box and in the Addressing Mode box select Obtain Automatically, to set the
controller to obtain its Ethernet settings from a DHCP server.
All the other parameters are set up in a similar way by entering the required value into dialogue box, or
making selections from the list. The rest of the parameters do not need to be specified for this tour.
4. Click OK. The dialogue box is closed.

Quick Tours
7.1.8 Lesson 2 - Setting Up the Sensor Type Modules
It is now necessary to set up the Sensor Type modules. The Sensor Type modules define how an electrical input is
scaled to provide a meaningful value in engineering units. IQSET uses a library of sensor definitions that contain all
the necessary settings to set up Sensor Type modules to correctly scale the value of a sensor that uses that sensor type.
Setting up the Sensor Type modules is simply a matter of selecting from which one of the sensor definitions in the
library the module should take its settings.
If required, additional definitions can be added to the library as described in 'Quick Tour 3- Making IQSET Work for
You'.
Setting up the sensor type modules:
1. On the Device menu click Sensor Types. The Sensor Type dialogue box is displayed.
2. In the Number box click 001- to select the sensor type module that is to be set up.
3. In the Sensor Part Number box click TE/TS to select the sensor definition that is to be used for sensor type
module 1 from the library.
4. Click Apply. The parameters for the sensor to be used by the sensor type module are displayed on the right
of the dialogue box, and the characteristics are shown in the graph.
5. Complete the setup of the sensor type modules by specifying two other modules as shown.
Module No. Value
Module 2 AQ/D range 0 to 100
Module 3 H/DT/H range 0 to 95
6. Click Exit.
The Filter button can be used to reduce the number of sensors that can be selected.
Note: If required, the parameters of the sensor type modules can be defined individually without using definitions
from the library.

Quick Tours
7.1.9 Lesson 3 - Adding Modules to the Strategy
Modules are added to the strategy by placing them onto a page.
Adding modules to a page:
1. Click to display the Project View and double-click Os 024 - SET Tours Controller in the Device
View (the controller whose strategy to which the modules are to be added). The tree structure will be
expanded.
2. Double-click Strategy Pages to display a list of all the pages created for the controller so far. The structure
should appear as shown below.
3. Currently there is only one page (P02 - Default Users) double-click it.
Note: IQSET labels the first page 'Page 2' because although page 2 is the first true strategy page, page 1 is
the title page of the strategy documentation.
The first module that is to be added to the page is Sensor 1, an external sensor.
4. Click to display the Next Module List dialogue box The Next Module List dialogue box is displayed
which enables the sequence step for the next module that is to be added to the page to be specified.
5. In the Next box in the Sequence Steps area enter 1.

6. Click OK.

Quick Tours
7. Right-click anywhere on the page, point to Inputs and click External Sensor. The Select Module dialogue
box is displayed allowing the sensor module number to be selected.
8. In the Module Number box enter 1 and click OK. The cursor changes to a hand , and the module appears
on the screen.
9. Move the cursor to the position where the module is to be placed and click. The module is placed on the
page. For now, just place the module anywhere. You will learn to move modules later in this lesson.
Note: The Parameters dialogue box for the module may be displayed. If this is the case, don’t worry, Auto
Edit is enabled; click OK to close the dialogue box.
10. Now add the modules listed in the table below to the page.
Module Type Nodule no Sequence Step

Inputs>Knob 1 N/A
Other>Loop 1 2
Drivers>Analogue 1 3
Note: Steps (2) and (3) can be replaced by right-clicking the controller and clicking Open. This will display
the first page of the controller's strategy.

Quick Tours
7.1.10 Lesson 3 - Moving Modules
All the modules for this part of the strategy are now on the page. However, positions will probably need to be changed
to make the strategy easy to understand. It is therefore necessary to move the modules around on the page. For the
purposes of this tour, you should move the modules until the page looks like the page below.
Moving modules:
1. Point to S1, (the module to be moved), and hold down the left mouse button.
2. Drag the module to its new location (the top left of the page).
3. Release the mouse button. Sensor 1 is now in the correct position.
4. Move the rest of the modules around on the page until it appears the same as the diagram.
7.1.11 Lesson 3 - Editing Modules

Now that the modules are in position, their configuration parameters can be edited so that they function as required A
full description of the parameters for each module is provided in the ‘IQ Modules’ section of this manual.
Editing Modules:
1. Double-click S1 (the module whose configuration parameters are to be edited) a dialogue box is displayed.

Quick Tours
2. In the Details box enter Space Temperature to specify further information about the module.
The details parameter for a module provides the ability to describe the module, how it functions, and how it
operates. This parameter is not sent to the controller.
3. In the Label box enter Space Temperature to specify the label for the module.
The label parameter is sent to the controller (defining the ‘$’ parameter). It specifies a user-friendly label for
the module, which can be up to 20-characters long.
4. In the I/O Module box click 0 – Base IO to specify the controller's on board I/O channels.
5. In the I/O Channel box click 1 to specify the channel supplying the sensors input.
6. In the Type box click 01 – Trend Thermistor to specify the sensor type module to be used by the sensor.
7. In the High Alarm Limit box enter 45 to specify the high alarm limit parameter.
8. In the Low Alarm Limit box enter 20 to specify the low alarm limit parameter.
9. Click OK.
The parameters for the other modules are defined in a similar way, by entering the required text in the
appropriate box, selecting from a list, clicking buttons, or selecting check boxes.
10. Specify the parameters of the other modules on the page as below by typing the value into the appropriate
box, or selected the required value from the list.
Module Parameter Value Tips

Occupied
Details
Setpoint
Occupied
Label
Setpoint
Units DegC
K1
Pin Level 99
Top of Range 30
Bottom of
15
Range
Value 22 Type the value into the appropriate box, or select the required
value from the list.
L1 Label Control Loop 1
Details AHU 1 Driver
Label AHU 1 Driver
I/O Module 01-Base IO
D1 in-phase
11
Channel
Antiphase
12
Channel
Start Delay 10

Quick Tours
7.1.12 Lesson 3 - Linking Modules
Editing the modules does not define all their configuration parameters. Parameters that come from other modules in
the strategy are specified by linking the modules together. Modules must be linked together so that the information
flows through the strategy correctly. IQSET uses its knowledge of modules to prevent silly mistakes such as
connecting a digital value to a point requiring an analogue value.
Linking Modules:
1. Click output V of S1, and drag the mouse to the source P of L1 (the parameter that is to be the destination).
The cursor will change to a green circle . If the source is not a suitable type for the destination, IQSET
will display a red cross ; if it is suitable, it will display a green circle .
2. Release the mouse button.
3. Make the other links in the same way until the links are as shown below.
Module Parameter> Linked to

K1 D L1 O
L1 D D1 S

Quick Tours
7.1.13 Lesson 3 - Adding Pages
The strategy may require more modules than can be placed on a single page, if this is the case, additional pages can
be added.
Adding pages:
1. Click located at the bottom of the SET Window. A new strategy page will be created for the controller.
If you move the mouse to the left of the window to display the Project View, you will see that a new page
(p03 - Page 3) is now visible in the Device View.
2. Now the new page has been created, practice what you have learned so far in the tour, and add the following
modules.
Module Parameter Value Tips

Space
Details
Temperature
Space
Label
Temperature
01- Trend
S2 Type
Thermistor
High Alarm
45
Limit
Low Alarm
20
Limit
Details Occupied Setpoint
Label Occupied Setpoint
Units DegC
Pin Level 99 Type the value into the appropriate box, or select the
K2 required value from the list.
Top of Range 30
Bottom of
15
Range
Output Value 22
L2 Label Control Loop 2
Label AHU 2 Driver
I/O Module 01-Base /O
D2 in-phase
13
Channel
Antiphase
14
Channel
Start Delay 10
3. Move, edit, and link them until the page looks like the one below.

Quick Tours
You can move between pages using the next and previous page buttons. Click to goto the previous page, or click
to goto the next page. Alternatively, you could double-click the required page from the Device View in the Project
View.
7.1.14 Lesson 4 - Defining the Strategy's Issue
Details about the strategy for a controller can be kept. They describe the current issue, and enable a description of the
changes made since the previous version to be recorded. These details are included on the strategy pages when they
are printed out.
Define the Strategy’s Issue:
1. Ensure that the page you have just created is displayed, and on the Device menu click Issue Details. The
Drawing Issue dialogue box is displayed.
2. This is the first issue of the strategy so click New to create a new issue. The issue number is incremented to
1. It is now necessary to specify any changes made, and any pages that were changed. Because this is the
first issue of the strategy, you will enter First Issue in both cases.
3. In the PCN/Details box enter First Issue.
4. In the Pages Affected box enter First Issue.
5. In the Date Approved box enter today’s date to specify the date the strategy was approved.
6. In the Approved box enter your name.
7. Click OK.

Quick Tours
7.1.15 Lesson 4 - Print Project Documentation
Once the issue details have been specified, you can print out the project documentation. It is possible to print out all
the pages for a controller, a selected range, or just the current page. IQSET also provides some tables for each
controller, which specify items, such as the sequence table etc., that do not appear on the strategy pages. It is possible
to print out either these tables or none.
For the purposes of this tour, you will print out everything.
Printing the Tables and Pages:
1. In the Device View double-click P02 - Default Users to display a strategy page for the controller for which
the project documentation is required.
2. Click .
7.1.16 Lesson 5 - Creating an IQ4 File
In the first five lessons of this tour, you have created a strategy for an IQ4E. That strategy must be downloaded to the
actual controller using IQSET. Before the strategy can be downloaded, a downloadable file must be created.
For the purposes of this tour, you will create an IQ4 file.
Creating an IQ4 file:
1. In the Device View double-click P02 - Page:2 to display a strategy page for the controller.
2. On the Strategy menu click Create Data File.
3. IQSET will display a warning message. Don't worry this is expected as you have not enabled the BACnet
functionality, click Yes to continue. Once IQSET has created the file, it displays a message indicating that
the file has been created.
4. Click OK.

Quick Tours
7.2 Quick Tour 2 - Beyond Basics

This tour is a step-by-step tutorial that takes you beyond the basic principles of using IQSET. It introduces features
that will enable you to control how the strategy operates, and to speed up the process of creating better strategy. It
builds on the project created in tour 1 using new techniques to expand the strategy.
Lesson 1- More on Linking Modules
In this lesson, you will learn more about linking modules, linking between pages, and linking to a specific value.
 Loading an Existing Project
 Linking Between Pages
 Linking to a Specific Value
Lesson 2 - Making Strategy Pages Easier to Understand
In this lesson, you will learn how to open a project created earlier, make the strategy easier to understand by adding
descriptive text to pages, and using TO Connectives.
 Adding Text to a Page
 Using TO Connectives
Lesson 3 - Setting Up Display and Directory Modules
In this lesson, you will learn how to set up display and directory modules to provide a structured way of accessing
information from a controller with devices such as a Network Display Panel, or to provide graphical display pages.
 Principles of Display and Directory modules
 Adding Directory Modules
 Adding Dynamic Display Modules
 Adding Static Display Modules
 Setting up Graphical Display Pages (Backdrops)
 Setting up Graphical Display Pages (Moving Items)
 Setting up Graphical Display Pages (Linking Pages)
Lesson 4 - Setting Up the Sequence Table
In this lesson, you will learn how edit the sequence table by changing the sequence steps.
 Changing a Module’s Sequence Step
 Event Driven Strategy
Lesson 5 - Using Strategy Blocks
In this lesson, you will learn how to re-use common pieces of strategy by making use of strategy blocks.
 Principles of Using Strategy Blocks
 Using Strategy Blocks

Quick Tours
7.2.1 Lesson 1 - Loading an Existing Project
This second tour uses the project you created in Tour 1, with additional modules and pages as a starting point.
Therefore, it is necessary to load that project first.
To load an existing project:
1. Run IQSET. The Log onto SET dialogue box is displayed.
2. In the User Name box click your name.

3. In the Password box enter your password.

Quick Tours
4. Click OK. The SET dialogue box is displayed.
5. Click Open Existing SET Project.

6. Click More Files and then click OK. The Open dialogue box is displayed.
7. Double-click Tours, and then double click SET Tour 2.

8. Click 12345678.tset.
9. Click Open.
Note: If IQSET is already running, you can still load an existing project by displaying the Project View, and on the
File menu clicking Open/New Project.

Quick Tours
7.2.2 Lesson 1 - Linking Between Pages
The nature of IQ strategies means that modules on one page may need to use the output from a module on another
page as an input. IQSET uses connectives to enable these links between pages.
Linking between pages:
1. Click to display the Project View and double-click Os 024 - SET Tours Controller in the Device
View. The tree structure will be expanded.
2. Double-click Strategy Pages to display a list of all the pages created for the controller so far.
3. Double click p03 - Page: 3 to go to the second page.
4. Right-click anywhere on the page, point to Other and click on Connective. The Connectives dialogue box
is displayed.
The list can be filtered by clicking the appropriate button at the bottom of the screen, making it easier to find
the required module.
All connectives
Analogue node connectives
Digital Input connectives
Digital node connectives
Knob connectives
Type 1 (XNC) Interface module connectives
Sensor connectives

Quick Tours
All connectives
Switch connectives
Undefined connectives
Time Module connectives
System connectives
5. Click S1V Space Temperature. You may need to use the scroll bars to locate it.
6. Click Select. The cursor changes to a hand .
7. Move the cursor to the position where the connective is to be placed. Position it to the left of L2.
8. Click the left mouse button. A connective to output (V) of module S1 is added to the page.
9. Now add a connective to I1S Manual Override, and place it above the connective to S1 and a connective to
Z1V Occupation Time Schedule and place it at the bottom of the page.
10. Click Exit.
It is now necessary to link the connective to the module to which it is supplying an input.
11. Click the connective to S1V, and drag the mouse to link it to the P attribute of L2.
12. Now link the connective to I1S to the A attribute of L2, and the connective to Z1V to the S attribute of L2.
7.2.3 Lesson 1 - Linking to a Specific Value
IQSET allows you link directly to a specific value by using an Analogue Node module. For this tour, you will add
link the U attribute of L1 to a specific node with a value fixed at 10.
Linking to a specific value:
1. Click to go to the first page (P02 - Page: 2).
2. Right-click anywhere on the page, and point to Inputs and click Analogue Node. This places an analogue
node module on the page.
3. Double-click the module that has just been added. The Analogue Module Parameters dialogue box is
displayed.
4. In the Label box enter Loop 1 Unoccupied Setpoint to specify the label for the node.
5. In the Value box enter 10 to specify the value of the node.
6. Click OK.
7. Move the module to the left of L1.
It is now necessary to link the module to the module to which it is supplying an input.
8. Click the output (D) of the module, and drag the mouse to link it to the U attribute of L1.
9. Now add the following Analogue Node modules to the strategy, and link them.
Page Label Linked to Value

P02 - Page: 2 Manual Level for Loop 1 L attribute of L1 15
P03 - Page: 3 Loop 2 Unoccupied Setpoint U attribute of L2 10
P03 - Page: 3 Manual Level for Loop 2 L attribute of L2 15

Quick Tours
7.2.4 Lesson 2 - Adding Text to a Page
IQ strategies can sometimes be difficult to understand; an engineer will regularly write on the strategy drawings to
explain of how a piece of strategy works. IQSET allows you to do this by entering text onto pages.
For the purposes of this tour, you will add a title to the top of each page, along with some explanatory text.
Adding Text to a Page:
1. Go to the first page (P02 - Page: 2).
2. Right-click anywhere on the page, and point to Draw and click Text. This displays the Display Text dialogue
box.
3. In the box enter SET Tour Page 1 of 3.

4. Click Size 5 to specify the size of the text.
5. Click Bold to make the text bold.
6. Click OK. The cursor changes to a hand .
7. Move the cursor to the top of the page in the centre.
8. Click the left mouse button. The text is placed on the page.
If you wish, lines, circles and rectangles can be added to the pages in a similar way.
9. Now enter the text listed in the table below.
Text Page Position Formatting

Control Loop 1 (P02 - Page: 2) Below L1 Size 1 not bold
SET Tour Page 2 of 3 (P03 - Page: 3) Top of page in Centre Size 5 bold
Control Loop 2 (P03 - Page: 3) Below L2 Size 1 not bold
7.2.5 Lesson 2 - Using To Connectives
When links are made between modules on different pages, the only indication of the link is the connective on the page
containing the destination module. There is no indication on the page supplying the value that a link exists. IQSET
allows you to indicate where a module is by providing a link to a module on another page using a To connective.
For the purposes of this tour you will add to connectives on the first page indicating links to modules on the other
page.
Using To Connectives:
2. Right-click anywhere on the page, and point to Other and click To Connective. The cursor changes to a
hand .
3. Move the cursor to the right of I1 to position the To connective, and click the left mouse button. The To
connective will be placed on the page.
4. Click the output S of I1.
Note: The pointer will change to a when it is moved over a parameter that can be linked.
5. Drag the mouse to the To connective. IQSET will display a green circle .
The To connective will now indicate the connection between the output of I1, and the A attribute - Manual
Override of L2 on page 3.
7. Now add some more To connectives to page 2 to indicate the other links to modules on page 3.

Quick Tours
Linked to Location
Output of S1 To the right of S1
Output of Z1 To the right of Z1
7.2.6 Lesson 3 - Principles of Display and Directory Modules
Display and directory modules provide the ability to create pages of information that are defined within the controller.
These pages can then be accessed from a web browser, or by supervisors/displays to present the user with meaningful
information from the controller without the need for separate configuration.
These displays are stored in a hierarchy, which enables the user to navigate to the required information. Directory
modules provide that hierarchy, and display modules define what information is displayed within the hierarchy.
The hierarchy below illustrates how display and directory modules are used.
7.2.7 Lesson 3 - Adding Directory Modules

The first stage in setting up display and directory modules is to create the hierarchy by adding directory modules. For
the purposes of this tour, you will create the hierarchy shown below:
Adding directory modules:


Quick Tours
3. In the Display and Directory View box right-click P0 and click Insert Directory. The Directory Item
4. In the Title box enter AHUs.

5. Leave the 0 in the Pin level box. This enables all users to access the module.
6. Click OK, a directory module called 'AHUs' is added.
7. Now add another directory module called 'AHU 1' one level down in the hierarchy, by right-clicking the
directory module you have just added (AHUs), clicking Insert Directory, and entering the name of the
module. Again, leave the PIN Level at 0.
8. Repeat the process to build up the hierarchy shown above.
9. Right-click P0 (the directory module) and click Edit Parameters and edit the title it so that it is called 'Main
Plant'.
The number of directory modules that have been added is shown in the Directory box at the bottom of the dialogue
box.
7.2.8 Lesson 3 - Adding Dynamic Display Modules
Now that the required hierarchy of directory modules has been created, the dynamic display modules need to be added
to define the values that are displayed.
Adding dynamic display modules:
1. In the Display Items box click S1 and drag it on onto the AHU 1 in the Display and Directory View box.
2. Release the mouse. A display module that displays the value of S1 is added.
3. Now add some more display modules until the structure in the Display and Directory View box appears as
shown below.
The number of display modules that have been added is shown in the Display box at the bottom of the dialogue box.

Quick Tours
7.2.9 Lesson 3 - Adding Static Display Modules
Now that the required hierarchy of directory modules and dynamic display modules need has been created, the static
display modules need to be added to define the other information that is to be displayed.
Adding Static Display Modules:
1. In the Display and Directory View box right-click AHU 1 and click Insert Static Display Item. The
Display Item dialogue box is displayed.
2. In the Label box enter Filter.

3. Click OK. The static display module is added that will display the text 'Filter'.
4. Add more static display modules until the structure appears as shown below.
The number of display modules that have been added is shown in the Display box at the bottom of the dialogue box.

Quick Tours
7.2.10 Lesson 3 - Setting up Graphical Display Pages (Backdrops)
Having added the display and directory modules, you will now set up their parameters to correctly define the
controller's graphical display pages. In this part of the tour you will specify a backdrop for the page.
Specify a backdrop:
1. Right-click AHU 1, and click Edit Web Page. The Graphical Display Page Editor is displayed as shown
below.
2. Right-click the page and click Properties. The Directory Item dialogue box is displayed.

Quick Tours
3. Click Change next to Backdrop. The Select Backdrop dialogue box is displayed.
4. Click Backdrop.jpg in the list.

5. Click OK.
6. Click OK.
7.2.11 Lesson 3 - Setting up Graphical Display Pages (Moving Items)
Having specified the backdrop, you will move the items on the page to the required position. When they are first added
to the IQSET places them in a table in the top left of the page.
Move the items:
1. Point to Space Temperature, (the item to be moved), and hold down the left mouse button.
2. Drag the item to its new location, (below the backdrop on the left).
4. Move the rest of the items around on the page until it appears the same as the diagram below.

Quick Tours
7.2.12 Lesson 3 - Setting up Graphical Display Pages (Linking Pages)
The page now looks as required it is now necessary to create a link between this page, and the page for AHU 2. You
will also create a link to the detail page for sensor 1.
Create a link to another graphical display pages:
1. Right-click AHU 2, and click Properties. The Display Item dialogue box is displayed.
2. In the Link Reference box enter trendModule: Views\Main Plant\Ahus\Ahu 2\Index.htm.

3. Click OK.
Create a link to a module detail page:
1. Right-click Space Temperature xx.xx DegC, and click Properties. The Display Item dialogue box is
displayed.
2. Click Make a link to the item's detail page.

3. Click OK.
4. Now create a link to the module detail page for driver 1.
5. Click OK to close the Graphical Display Page Editor.
6. Click OK to close the Display and Directory Setup dialogue box.

Quick Tours
7.2.13 Lesson 4 - Changing a Module's Sequence Step
If required, the position of a module in the sequence table can be changed. If you display the second page (P03 - Page:
3) you will notice that the sequence step of L2 is 5 (indicated by above the module) and D2 is located at step 7.
Although this does not really change the strategy, you will change the position of L2 in the sequence table to 6.
Changing a module’s sequence step:
1. Go to the second page (P03 - Page: 3).
2. Right-click L2, and click Sequence Step. The Sequence Step dialogue box is displayed.
3. In the Module’s Sequence box click 005.
4. Click . This will remove L2 from sequence step 5.

5. In the Sequence Table box click 006.
6. Click . '6' will now appear in the Module's Sequence box, indicating that the module is at sequence step
6 in the sequence table.
7. Click OK.
8. Now complete the modifications to the sequence table by moving D1 to sequence step 4, L1 to sequence step
3, and S1 to sequence step 2.

Quick Tours
7.2.14 Lesson 4 - Event Driven Strategy
Event driven strategy can be used to cause a piece of strategy to be processed when an event occurs. This is useful for
lighting strategies where the light must be turned on as soon as the switch is turned on.
Event driven strategy is a block of strategy that performs an isolated function. When any input in any module in that
block of strategy is changed, the strategy will be processed. Care should be taken to ensure that the output of a module
in the block does not change the input of a previous module otherwise the strategy will continue to be processed in a
loop. The modules in a block of event driven strategy do not appear in the sequence table.
For this tutorial, we will create a piece of strategy that turns the lights on during occupancy, and off during non-
occupancy, but also allows the lights to be turned on for a period during non-occupancy.
To set up event driven strategy:
1. Click located at the bottom of the SET Window to create another page.
2. Add the modules in the table below to the page, and edit their parameters by double-clicking them to display
the Parameters dialogue box.
Module Type Parameter Value

Time schedule Label Lighting Occupancy
Label Lighting
Details Lighting
Digital Driver
I/O Module 00 - Base IO
in-phase Channel 11
Label Light Switch
External digital Input I/O Module 00 - Base IO
in-phase Channel 2
Label Lighting
Logic Combination J E
K F
3. Link the modules as described in the table below:
Module Type Module Parameter Linked To

I2 S G1E
Z2 Output G1F
G1 D D3S
To make the strategy event driven all the modules must be removed from the sequence table, in this case G1,
and D3.
4. Remove the modules from the sequence table by clicking to change the pointer to a , and then clicking
G1, and D3.
5. Once the required modules have been removed from the sequence table, right-click. The cursor will change
back to normal.
For more details about removing modules from the sequence table see the 'Remove Modules from the Sequence Table'
section of this manual.
7.2.15 Lesson 5 - Principles of Using Strategy Blocks
Using strategy blocks will save a great deal of time if you regularly re-use pieces of strategy. It is possible to use an
entire strategy block in a strategy, or to use individual pages from the strategy block. The strategy blocks available
are displayed in the Strategy Library, and can simply be dragged into the strategy as required.

Quick Tours
7.2.16 Lesson 5 - Using Strategy Blocks
For this tour, you will use the alarm handling strategy blocks to add strategy.
To use a strategy block:
1. Display any of the strategy pages.
2. Click to display the Strategy Library.

3. Expand the tree to show the alarm handling strategy blocks. The Strategy Library will now look like the
diagram below.
4. Click Route - Time Enabled and drag it onto the strategy page.
The pointer will appear as a , and will change to a when over an area where the strategy block can
be placed.

Quick Tours
7.3 Quick Tour 3 - Making IQSET Work for You

This tour is a step-by-step tutorial that shows you how to use some of the more advanced features of IQSET, and how
it can be customised to suit your requirements.
Lesson 1 - Backwards Engineering an IQ Controller
In this lesson, you will learn how to upload the strategy in the required format, and then import that file into IQSET.
 What is Backwards Engineering?
 Uploading the Strategy in the Required Format
 Importing an IQ4 File
Lesson 2 - Creating Your Own Strategy Block
In this lesson, you will learn how to create your own strategy block.
 Principles of Strategy Blocks
 Creating a Strategy Block
Lesson 3 - Adding Sensor Definitions to the Library
In this lesson, you will learn how to add sensors to the library of sensors that can be used to quickly set up the
parameters for sensor type modules.
 Adding a Sensor to the Sensor Library
Lesson 4 - Using the Command Line Toolbar
In this lesson, you will learn about the Command Line toolbar, how to use it to find modules in the strategy, and how
to add modules to strategy pages.
 The Command Line toolbar
 Using the Command Line toolbar to Find Modules
 Using the Command Line toolbar to Add Modules
Lesson 5 - Comparing Strategy
In this lesson, you will learn how to compare the strategy held by IQSET with strategy in the actual controller.
 Comparing two Strategies
7.3.1 Lesson 1 - What is Backwards Engineering?
Backwards engineering is the process of taking an IQ controller for which there is no documentation of the strategy,
and getting it to a situation where the strategy can be documented and modified using IQSET. This means that
controllers engineered without IQSET, or for which the IQSET project has been lost, can be modified using all the
latest features of IQSET.
Backward engineering has two separate stages:
Uploading the strategy
Importing the strategy

Quick Tours
7.3.2 Lesson 1 - Uploading the Strategy in the Required Format
The controller that is to be backwards engineered the strategy must be uploaded from the controller in IQ4 format
using IQSET. Once the file is uploaded, ensure that the filename is in the format Lxxxnyyy.IQ4. Where 'xxx' specifies
the LAN number and 'yyy' specifies the network address. E.g. the file for controller 25 on LAN 24 would be
'L024n025.IQ4'.
For the purposes of this tour an IQ4 file has been provided in the 'C:\Set Projects\Tours\SET Tour 3\Upload' directory,
so it is not necessary to upload a file.
7.3.3 Lesson 1 - Importing an IQ4 File
Once the strategy has been uploaded in a suitable format, the next stage in the process is to import the file into the
required project. You will import the IQ4 file supplied for this tour located in the 'C:\Set Projects\Tours\SET Tour
3\Upload' directory.
Importing an IQF File:
1. Open the project in the 'C:\Set Projects\Tours\SET Tour 3' directory.
2. On the Project menu click Import and click IQ4 file. The Select IQ4 file to import dialogue box is
displayed.
3. Navigate to the 'C:\Set Projects\Tours\SET Tour 3\Upload' directory, and click L099n025.IQ4.
4. Click Open. IQSET will now import the file, creating the controller 25, adding four strategy pages, and
putting the strategy into the specified locations. Once the process is complete, IQSET displays the final page
containing strategy.
5. Compare the strategy of the controller that has just been imported with that of controller 24. You will notice
slight differences in the layout of the two strategies, the connectives are not reproduced (although the modules
inputs are all specified correctly), and some modules may be overlapping slightly.
The strategy can now be documented and engineered using IQSET.
7.3.4 Lesson 2 - Principles of Strategy Blocks
Strategy blocks allow standard pieces of strategy to be re-used without the need to recreate the strategy each time it is
required. You can build up a library of different strategy blocks for all the different standard pieces of strategy you
use.
When a strategy block is created all the links between modules are retained, as is the relative position of the modules
on the page.
The actual modules used are determined at the time the strategy block is used by the appropriate pointer (e.g. if a logic
module is used, and the logic pointer is set to 5, the first logic module used will be logic module 5). The sequence
pointer determines the sequence step of first module in the sequence table.
IQSET prompts for the actual module that is to be used when the strategy block used. Each strategy block can be made
up of several pages of strategy, and it is possible to use the entire strategy block, or just a page.

Quick Tours
7.3.5 Lesson 2 - Creating a Strategy Block
For this tour, you will create a plant block consisting of two pages, like the strategy in Tour 1.
Creating a strategy block:
1. Click to display the Strategy Library.

2. Right-click the Custom Block and click New Group. The Enter Group Name dialogue box is displayed.
3. In the box enter SET Tour as the name of the group.

4. Click OK.
5. Right click SET Tour and click New Strategy Block. The Strategy Block Properties dialogue box is
displayed.
6. In the Block Name box enter Tour 3 to specify the name of the strategy block.
7. In the Controller Type box click IQ4 to specify the type of controller for which the strategy block is to be
used.
8. In the Firmware Version box click 3.3 to specify the firmware version of controller for which the strategy
block is to be used.
9. In the Revision box enter 1 to specify the revision number of the strategy block.
10. In the Group box ensure that SET tour is selected.
11. In the Details box enter SET Tour 3 strategy block. For the purposes of this tour leave the other fields blank.
12. Click OK. IQSET will now create a strategy block called Tour 3 and open a blank strategy page ready for
strategy to be added.
Note: The strategy page is green to indicate that a strategy block is being edited.
13. Click to add a second page.

14. Add the following modules to the strategy pages.

Quick Tours
Module Page Parameter Value Links

Sensor Part H/DT/T
Sensor Type 1 N/A N/A
Scaling Range -40 t0 +110 Type 5
Mod ID 2
I/O Module N/A Module Type XCITE/IO/4UI/4AO N/A
Label I/O Module 2
Sequence Step 1
Details Space Temperature
Label Space Temperature
S1 1 V linked to L1 P
Type 01-Trend Thermistor
High Alarm Limit 45
Low Alarm Limit 20
Labels Occupied Setpoint
Units DegC
K1 1 Pin Level 99 D linked to L1 O
Top Of Range 30
Bottom of Range 15
Output Value 22
Sequence Step 2
L1 1 D linked to D1 S
Label Control Loop 1
Sequence Step 3
Label AHU 1 Driver
D1 1 I/O Module 02-I/O Module 2 N/A
in-phase Channel 5
Antiphase Channel 6
Start Delay 10
Sequence Step 4
Details Space Temperature
Label Space Temperature
S2 2 V linked to L2 P
Type 01-Trend Thermistor
High Alarm Limit 45
Low Alarm Limit 20
Label Occupied Setpoint
Units DegC
K2 2 Pin Level 99 D linked to L2 O
Top of Range 30
Bottom of Range 15
Output Values 22
Sequence Step 5
L2 2 D linked to D2 S
Label Control Loop 2
Sequence Step 6
D2 2 N/A
Label AHU 2 Driver
I/O Module 01-I/O Module 2

Quick Tours
Module Page Parameter Value Links

in-phase Channel 7
Antiphase Channel 8
Start Delay 10
15. Once the strategy block is complete click to close the strategy page. A dialogue box is displayed asking if
you want to save the changes.
16. Click Yes.
7.3.6 Lesson 3 - Adding a Sensor Definition to the Library
IQSET uses a library of sensor definitions, which enable Sensor Type modules to be defined quickly. This library
contains definitions that enable the sensor type module to be set up for all the standard sensors. If you regularly use
sensors for which definitions do not exist in the library, you can add them to the library so that they will always be
available for use. In this lesson, you will add a sensor definition to the library.
Adding a sensor definition to the library:
1. On the Device menu click Sensor Types. The Sensor Type dialogue box is displayed.
2. In the Number box click 04 - to specify an unused sensor type module (this could be any unused sensor type
module).
3. In the Sensor Part Number box enter Tour 3 to specify the part number for the sensor.
4. In the Scaling Range box enter 90 - 110, to specify the range for the sensor.
5. In the Unique Sensor Reference box enter Tour 3 90 - 110, to specify the reference for the sensor.
6. Click Edit. The dialogue box changes to allow the appropriate parameters to be specified. It is necessary to
define the output value for a specific input value. The number of values entered depends on the sensor’s
characteristics, and how accurate the reading needs to be.
7. In the first box in the Input (X) column enter 0.486, and in the first box in the Output (Y) column enter 110,
to specify the sensor’s scaling parameters.

Quick Tours
8. Specify the other parameters for the sensor to those listed below.
Input (X) Output (Y)

0.555 105
0.636 100
0.73 95
0.839 90
9. In the Input Type box enter Thermistor (KOhms) to specify the type of input for the sensor.
10. In the Upper Limit box enter 110 to specify sensor’s upper limit.
11. In the Lower Limit box enter 90 to specify sensor’s lower limit.
12. Once the sensor’s parameters are correctly specified, click Save to Library.
13. Click Exit.
Note: Sensor type module 4 in the controller has been set up to use the parameters specified. You may wish to remove
this setting, if you are only setting up the library.
7.3.7 Lesson 4 - The Command Line Toolbar
The Command Line toolbar, shown below, enables many of IQSET’s commands to be performed simply by entering
the appropriate command.
Using the Command Line toolbar can speed up use of IQSET enabling modules to be added to the strategy at a
specific sequence step, or modules to be located quickly. The Command Line toolbar also allows other IQSET
commands such as redrawing the screen, displaying another page, or zooming in and out. A full list of the commands
that can be entered in the Command Line toolbar is provided in the 'Command Line Commands' section of this
manual.
7.3.8 Lesson 4 - Using the Command Line Toolbar to Find Modules
The Command Line toolbar can be used to find modules in the strategy. By entering the item reference (e.g. S1) to
specify sensor 1) you can locate the page containing a specific module. For this tour, you will find the location of
Loop 1.
Using the Command Line toolbar to find modules:
1. If the Command Line toolbar is not already displayed, on the View menu click Command Line.
2. Click in the Command Line toolbar press CTRL+M, or on the Tools menu click Command Line to move
cursor to the Command Line toolbar.
3. In the Command Line toolbar enter L1, to specify the item reference for the module that is to be located.
4. Click . IQSET will now locate Loop 1 and display ‘L1 on Pages(s) 2’ in the Command Line toolbar
indicating that loop 1 is located on page 2.
5. Repeat the process to locate other modules in the strategy. The item reference should be in the format shown
below.
<Module Type><Module Number>
<Module Type> specifies the type of module using its module identifier and module number (e.g.,
S1specifies a sensor). For details of the module identifier see the appropriate module section of this manual.
<Module Number> specifies the number of the module (e.g. to find sensor 3 type S3).

Quick Tours
7.3.9 Lesson 4 - Using the Command Line Toolbar to Add Modules
The Command Line toolbar can be used to add modules to the strategy on the current strategy page. Adding modules
in this way enables a specific module to be added to the strategy at a specific sequence step. This saves time if you
wish to add a module completely out of sequence with the pointers.
For this tour, you will add loop module 5 to the first page of strategy at step 56 in the sequence table.
Using the Command Line toolbar to add modules:
1. Goto the first page of strategy for controller 24 (P02 - Page: 2)
4. In the Command Line toolbar enter L#5#56 to specify the module that is to be added.
5. Press Enter. The cursor changes to a hand and an outline of the module appears on the screen.
6. Move the cursor to the right of Z1 and click. The module is placed on the page.
7.3.10 Lesson 5 - Comparing Two Strategies
IQSET enables two strategies to be compared. It does this by comparing a strategy uploaded from an IQ controller
with the strategy held by IQSET. For the purposes of this tour, you will compare an IQ4 file that has been supplied
with the strategy for controller 24. When the comparison is performed, you can choose whether the strategy is updated
to reflect the changes, and whether a report listing the differences is printed.
To compare two strategies:
1. Display a strategy page for controller 24 on LAN 99.
2. On the File menu point to Compare. The Open dialogue box is displayed.
3. Click Compare.iq4 to select the file that is to be compared with the strategy held by IQSET.
4. Click Open. This displays the Compare and Update dialogue box.

Quick Tours
5. Select the Update Database, Backup Database, and Print Report File check boxes.
Option Description
Update
Causes IQSET to update its strategy to be the same as the chosen fil
Database
Backup Ensures that IQSET makes a copy of the existing strategy before updating it allowing the
Database strategy to be restored if the updated strategy is not suitable.
Print Report Causes IQSET to print out a report of the differences between the strategies on the specified
File printer.
6. Click Start.
IQSET will now compare the strategy in the file Compare.iq4 with the strategy stored by IQSET, and modify
the strategy in IQSET to be the same as the IQ4 file. It also prints out a report that describing the differences.
From this report, you can see that the settings for sensor type module 4 were different; in the IQ4 file the
module had not been set up, whereas in IQSET it had. If you now look at sensor type module 4 you will see
that it has been cleared down by the process. The report also shows that Loop 5 was not present in the IQ4
file, if you now check the first page of strategy 'L5' has been removed.

Create a BTL Compliant Strategy
8 CREATE A BTL COMPLIANT STRATEGY

To meet the requirements of BACnet testing laboratories several requirements that must be meet when creating the
strategy. These are described in the IQ3 Configuration Reference Manual (TE200768), or the IQ4 Configuration
Reference Manual (TE201263).
When IQSET creates the strategy file it performs the following checks to see if the strategy is BTL compliant.
IQ4 v3.50 or greater strategy:
 The following parameters in the BACnet Application Network module are enabled.
BACnet Backup/Restore
Reinitalise Device Service
BACnet Writable Properties
and the 'BO State Count And Active Time Properties' parameter is disabled
 Only one alarm route module is connected to each BACnet alarm destination module.
IQ3 v2.1 or greater or pre v3.50 IQ4 strategy:
 The BTL compliance parameter in the BACnet network module is enabled.
 Only one alarm route module is connected to each BACnet alarm destination module.
 A single time schedule module is connected to each BACnet alarm route module.
 Only one ON/OFF period is set for each day in Time Schedule modules linked to alarm route modules.
 The times for each day in Time Schedule modules linked to alarm route modules are the same unless the day
is set to OFF all day.
 There are no exceptions associated with Time Schedule modules linked to alarm route modules.
 There are no synchronised or triggered plot modules in the strategy.
 Periodic plot modules do not have a module connected to the enable input.
 Logic readback modules connected to digital driver modules do not have a grace time specified.

Create a BTL Compliant Strategy

Engineer IQ Controllers
9 ENGINEER IQ CONTROLLERS
This section describes the process of using IQSET to engineer IQ controllers.
Although IQSET can be used in the way that best suits individual needs, it is recommended that the procedure below
be followed:
Plan the System
Specify the IQSET Project
Create the Controllers
Configure the Controller Strategy
Add Text and Graphics to Strategy Pages
Test the Strategy
Download the Strategy
Issue Project Documentation
Backup the Project
9.1 Plan the System
Good planning is necessary prior to starting work because it reduces the actual amount of time spent engineering the
system, reduces the number of errors, and produces a better result. It is important to understand the HVAC equipment
that is being controlled, and the hardware that interfaces with it, to ensure that the strategy is written so that the
controller correctly interfaces with the HVAC equipment. The HVAC equipment will need to be maintained;
therefore, it is necessary to know the maintenance intervals of the pieces of HVAC equipment so that this can be built
into the strategy. It is also necessary to understand how the system is to be used so that the appropriate adjustments
can be included. This is helpful in deciding on the setpoints, OSS settings etc.
When engineering a system that uses the Trend network, it is not only necessary to understand the requirements of the
control strategy within individual controllers; it is also necessary to understand how various controllers interact with
each other. This enables ic comms to be set up, and the device's addresses can be set up correctly.
If the strategy is to be BTL compliant you should follow the advice in the 'Create a BTL Compliant Strategy' section
of this manual.
9.2 Specify the IQSET Project
Having planned the system, the next stage is to specify the IQSET project that is to be used. This is done by either:
Creating a new IQSET project
Opening an existing project
Importing a IQSET project
Once the project has been specified it is necessary to set up the project's remote devices.

9.2.1 Create a Project
Creating a new project will create a directory in the c:\Set Projects directory in which to store all the files relating to
the project. IQSET will automatically create sub-directories within it to store information (e.g. IQ4 files). If the default
location of this directory is not suitable, a more suitable one can be specified by changing the base project directory.
Create a project:
1. Run IQSET and log on.
2. When the SET dialogue box is displayed click Create New SET Project.
3. Click OK. The New Set Project dialogue box is displayed.
4. In the Project Name box enter the project name.

5. In the Project Number box enter the project number.
6. In the Client box enter the client name.
7. In the Project Details box enter the project details.
8. In the Site Name box enter human readable site code for devices in the project.
Note: All devices in the project will be assigned the same human readable site code.
9. Check the machine-readable site code displayed in the Site GUID box. If necessary (e.g. project is for a site
that already exists and it already has a site GUID) it can be specified by typing it into the box. A new code
can be generated by clicking Change.
Note: All devices in the project will be assigned the same machine-readable site code.
10. Click OK.
11. If necessary, edit the project details.
Note: It is possible to create a project while IQSET is running by displaying the Project View, and on the File menu
clicking Open/New Project to display the SET dialogue box.

9.2.2 Open a Project
IQSET projects can be opened as required.
To open a project:
2. When the SET dialogue box is displayed click Open Existing SET Project.
3. In the list at the bottom of the dialogue box click the required project. To display a list of projects in another
directory click Change, navigate to the directory containing the required project and click OK. The project
should now appear in the list. To open a file not in the list, click More Files then click OK to display the
Open dialogue box, click the required file and click Open. To select a file stored in a different location, click
the drive, or folder in the Look in box that contains the file, double-click the folders in the folder list until
file is displayed.
4. Click OK. The selected project will be opened.
To open a recent project or controller:
2. When the SET dialogue box is displayed click Open Recent SET File.
3. In the list at the bottom of the dialogue box click the required project (TSET files) or controller (IQ files). To
display a list of projects in another directory click Change, navigate to the directory containing the required
project and click OK. The project should now appear in the list.
4. Click OK. The selected project will be opened.
Note: If opening a controller that is a /XNC the XNP Update Settings dialogue box may be displayed if the
number of stores, inputs outputs and version stored in the SET file is different to those stored in the XNP file.
Click Update to use the values stored in the XNP file, or Ignore to use the values stored in the SET File.
TIP: It is possible to open a project while IQSET is running by displaying the Project View, and on the File menu
clicking Open/New Project to display the SET dialogue box.
9.2.3 Import a Project
The entire contents of a project can be imported from a SET.ZIP file. This enables a project to be restored from a
backup, or moved between computers.
To import a project:
2. When the SET dialogue box is displayed, click Import Zipped Project. The Select Project Zip File
3. In the folder list click the zip file for the required project. To select a file stored in a different location, click
the drive, or folder in the Look in box that contains the file, and double-click the folders in the folder list
until the file is displayed.

4. Click Open. A dialogue box is displayed to indicate the progress. When the process is complete, another
5. Click OK. If the project already exists, only information that is newer than the existing information will be
imported.
9.2.4 Edit Project Details
The project details describe the name of the project, the client name, and a reference number. They are specified when
the project is created, but can be edited later if necessary.
To edit the project details:
1. Open the required project.
3. In the Device View right-click the project name, and click Project Details. The Project Details dialogue
box is displayed.
4. Change the project details as required by entering the required text into the appropriate box.
5. Click OK.
9.2.5 Delete a IQSET Project
IQSET does not provide a facility for deleting a project. To remove a project from the system it is necessary to delete
the subdirectory for the required project and all its contents from the c:\set projects directory using Windows Explorer.

9.2.6 Set up the Project's Default Remote Devices
For projects containing for IQ4s or IQ3s v1.3 firmware or greater it is possible to specify a list of remote devices that
can be used for all the controllers in the project.
The remote device list should be placed in all devices on the network and contain as many devices (at least 2) from
each subnet as possible (i.e. divide the number of slots in the list by the number of subnets) and be put in every device
that supports the list. If automatic addressing is being used the devices must be specified using host names, and if
manual addressing is being used the list should contain the devices with the lowest IP addresses.
To set up the projects remote devices:
1. Display a strategy page for the controller for which the address module is to be specified.
2. Right-click the strategy page, point to Device, point to Network, and click Ethernet IP Module, or on the
Device menu click Ethernet IP Module. The Ethernet IP Module dialogue box is displayed.
3. In the Remote Devices area select clear the Not Sent check box.
4. In the Remote Devices box click the remote device that is to be set up. A is displayed.
5. Click . The Remote Device dialogue box is displayed.
6. In the Device Address box enter the host name or IP address of the remote device.
7. In the Subnet box enter the device's subnet mask.
8. Click OK.
9. Repeat steps (4) to (8) until all the required devices have been specified. There is a maximum of 20 devices.
10. Click Set Project Defaults.
11. Click OK.

9.3 Create the Controllers

9.3.1 Add Controllers Manually
IQ controllers must be added to the project before their strategy can be specified. Some controller functions require
specific options to be selected.
Option Required Setting

Device Type IQ4E
Firmware
3.3 or greater
IQ4E Version
Hardware IQ4E/16, IQ4E/32, IQ4E/64, IQ4E/96, IQ4E/128,
Variant IQ4E/160, IQ4E/192
Device Type IQ422
Firmware
3.3 or greater
IQ422/00 Version
Hardware
IQ422/00
Variant
Device Type IQ422
Firmware
3.3 or greater
IQ422/12 Version
Hardware
IQ422/12
Variant
Device Type IQ4NC
Firmware
3.2 or greater
IQ4NC Version
Hardware IQ4NC/00 or IQ4NC/12 - 3.2 or greater
Variant IQ4NC/16 or IQ4NC/32- 3.4 or greater
Device Type IQ422, IQ4E, IQ4NC
IQ422 - 3.3 or greater
Firmware
IQ4E - 3.3 or greater
Version
IQ4NC - 3.4 or greater
IQ4 with XNC support IQ422/00
IQ422/12
Hardware
IQ4E/96
Variant
IQ4NC/16
IQ4NC/32
Device Type IQ41x, IQ422, IQ4E, IQ4NC
Firmware
3.5 or greater
Version
IQ411
IQ412
IQ422/00
IQ422/12
IQ4E/16
IQ4 with B-BC Time Schedules IQ4E/32
Hardware
IQ4E/64
Variant
IQ4E/96
IQ4E/128
IQ4E/160
IQ4E/192
IQ4NC/00
IQ4NC/12
Option B-BC Sched


Firmware
4.2 or greater
Version
IQ411
IQ412
IQ422/12
IQ4E/16
IQ4E/32
IQ4 with IQ Interfacing (MODBUS Hardware IQ4E/64
only) Variant IQ4E/96
IQ4E/128
IQ4E/160
IQ4E/192
IQ4NC/00
IQ4NC/12
IQ Interfacing
Option
Do not select XNC
Firmware
4.3 or greater
Version
IQ411
IQ412
IQ422/12
IQ4E/16
IQ4 with IQ Interfacing (MODBUS & IQ4E/32
M-Bus) Hardware IQ4E/64
Variant IQ4E/96
IQ4E/128
IQ4E/160
IQ4E/192
IQ4NC/00
IQ4NC/12
Option IQ Interfacing
Device Type IQ3xx
Firmware
2.3 or greater
IQ3 Controller with BINC Version
functionality Hardware
IQ 3xact/12, IQ 3xact/00
Variant
Options BACnet and BINC
Device Type IQ 3xx
Firmware
1.3 or greater
IQ3 Controller with XNC support version
Hardware
IQ 3xcite/12, IQ 3xcite/16, IQ 3xcite/96
Variant
Device Type IQ 3xx
IQ3 Controller with XML Support Firmware
2.2 or greater
version
Device Type IQ 3xx
IQ3 Controller with BACnet support Firmware
2.0 or greater
version
Device Type IQ22x
Firmware
2.0 or greater
IQ22x Controller with ADL Support version
Hardware IQ 221 ADL, IQ 222 ADL, IQ 223 ADL, IQ 228 ADL, IQ
Variant 229 ADL


Device Type IQ 204
Firmware
3.0
IQ204 Controller with ADL Support version
Hardware
IQ 204 ADL
Variant
IQ2 Controller with ATM Device Type IQ 212-ATM
Device Type IQ22x
Firmware
1.0
IQ2 Controller with XNC Support version
Hardware
XNC 220, XNC 221, XNC 222, XNC 223, or XNC 229
Variant
For IQECOs to communicate with other Trend devices not on the MSTP network an IQ4NC must be added to the
LAN containing the IQECO controllers.
Note: Solutions can be used to add an entire controller that is already configured to the project. IQSET's project
config option can also be used to add multiple controllers easily or to import them from a spreadsheet.
To add a controller:
1. Add the LAN.
3. In the Device View right-click the LAN to which the controller is to be added, point to Insert Device and
click IQ Controller. The Controller Selection dialogue box is displayed.
box.
5. Click the required option (IQ1, IQ2, IQ3, IQ4, IQECO) in the Range area to specify the range of the
controller that is to be added. Clicking the Other option enables a custom controller type to be added,
providing the .IQD file exists in the 'C:\Program Files\Trend Control Systems\System Engineering
Tool\Devices' folder.
6. In the Device Type box click the required device type.
7. In the Firmware Version box click the firmware version of the controller that is to be added.
8. In the Hardware Variant box click the hardware variant of the controller that is to be added.
9. In the Options area select the required check box(s) to select any required options (e.g. BACnet). If Fixed is
selected, you must use a solution to add the strategy to the controller - see 'Add Controllers using Solutions'.
Important: Some features of Time Schedule modules in IQ4v3.50 firmware or greater are not compatible
with Trend supervisor products (963, IQ®VISION, IQ®VIEW8, and IQ®VIEW4). To maintain
compatibility with these products, ensure that the B-BC Sched option is NOT selected.

11. In the Address box enter the network address of the controller. (1 to 119 excluding addresses 2, 3, and 10).
Note: It is recommended that IQECOs are in the address range 11 to 64.
12. If more than one controller of the same type is to be added in the Controller Count box enter the number of
controllers that are to be added. The address of the first controller added is the one specified in the Address
box. The address is then incremented to the next valid address in the range (1 to 119 excluding addresses 2,
3, and 10) for the next controller that is added. This process is repeated for all the controllers that are to be
added.
13. In the Name box enter a name for the controller.
14. In the Details box enter details about the controller.
15. In the Engineer box enter the name of the engineer designing the strategy.
16. Click OK. The Address Module dialogue box is displayed. The appearance of this dialogue box will vary
depending on the type of controller being added.
17. Specify the address module parameters by entering the required value for each address module parameter
into the appropriate box, or clicking the required options.
18. Click OK. The User Parameters dialogue box is displayed.
19. Specify the Admin User. This user must have a PIN level of 100.
20. Click OK. For IQECO controllers the process is complete goto to step (27) for IQ4NC controllers the NC
Configuration dialogue box is displayed, goto step (21) for other types of controllers the Sensor Type
dialogue box is displayed goto step (23).
21. Specify the controller's network configuration.
22. Once all the network configuration is specified click OK.
23. Specify the sensor type modules as required.
24. Once all the required sensor types are specified, click Exit. For pre IQ3 controllers the process is complete
goto to step (25). For IQ3 controllers with I/O available the I/O Set up dialogue box is displayed goto step
(23).
25. If adding an IQ3 or IQ4E with external I/O available set up the I/O modules.
26. Once all the I/O modules are specified click Exit.
27. IQSET displays a blank strategy page for the new controller.
28. If more than one controller is being added steps (16) to (25) will be repeated for each controller being added.

9.3.2 Add Controllers Using Solutions
Solutions enable an entire pre-configured controller to be added to the project. This can save a great deal of time if
the project contains several controllers with the same configuration. IQSET is supplied with a library of pre-configured
solutions that can be used, or you can create your own. Time spent creating solutions will save time later in the project.
Fixed strategy controllers will only be able to run a strategy from the library it is licensed to use but IQSET will not
warn you that the solution is not compatible with the actual controller. Programmable controllers (no license
restrictions) will be able to run any solution designed for their controller type.
The device settings e.g. device type, and option such as fixed are taken from the solution. If these are not suitable e.g.
it is a fixed strategy it will be necessary to edit the device details as required once the controller has been added.
If the solution used is part of a licensed library the Fixed option will be set for the controller. If you intend to download
this strategy to a programmable controller you should edit the device details to clear the Fixed option. The controller
licence file is also copied to the project's 'License' directory and will be use when the strategy is downloaded to the
controller.
The available solutions are shown in the in the Strategy Library.
Add Controllers Using solutions from the Strategy Library
Add Controllers Using Solutions from the Search library
Add Controllers Using Solutions from the Device Details Dialogue Box
9.3.2.1 Add Controllers Using solutions from the Strategy Library
To add controllers using solutions from the Strategy Library:
2. If required filter the library.
 Click . The Filter dialogue box is displayed.
 Select the required options.

 Click OK.
3. Click the group/sub group in the Solutions area of the Strategy Library containing the required solution to
open it.
Note: The data sheet describing the solution can be displayed by right clicking the solution in the strategy
library, and clicking Data Sheet.
4. Right click the required solution, and click Copy to Project, or drag the solution on to the Display Area.
The Enter Destination dialogue box is displayed.
5. In the Lan box enter the LAN number for the new controller (0 to 119 excluding addresses 2, 3, and 10).
6. In the Node box enter the network address of the controller (1 to 119 excluding addresses 2, 3, and 10).
7. Click OK. The controller will be added to the project.

9.3.2.2 Add Controllers Using Solutions from the Search library
To add controllers using solutions from the Search library:
1. If the Search Library is not displayed, display the Strategy Library, and click .
2. Enter the keywords that are to be matched in the box, or select them.
Note: The List/Heatmap button toggles the keyword display between a list of heatmap.
 Drag the solution on to the Display Area. toggles the display of the block description. indicates
an IQ4 solution. The Enter Destination dialogue box is displayed.
6. Click OK. The controller will be added to the project.

9.3.2.3 Add Controllers Using Solutions from the Device Details Dialogue Box
To add a controller using a solution from the Device Details dialogue box:
1. Add the LAN.
3. In the Device View right-click the LAN to which the controller is to be added, point to Insert Device and
click IQ Controller. The Controller Selection dialogue box is displayed.
4. If required specify the required controller range, device type, firmware version and hardware variant in the
Device Type, Firmware Version and Hardware Variant boxes, and the options for the controller in the
Options area.
5. If the required controller range, device type, firmware version and hardware variant were specified in step
(4) click OK if not click Cancel. The Device Details dialogue box is displayed.
6. In the Address box enter the network address of the controller. (1 to 119 excluding addresses 2, 3, and 10).
Note: It is recommended that IQECOs are in the address range 11 to 64.
7. If more than one controller using the same solution is to be added in the Controller Count box enter the
number of controllers that are to be added. The address of the first controller added is the one specified in the
Address box. The address is then incremented to the next valid address in the range (1 to 119 excluding
addresses 2, 3, and 10) for the next controller that is added. This process is repeated for all the controllers
that are to be added.
8. In the Name box enter a name for the controller.

9. In the Details box enter details about the controller.
10. In the Engineer box enter the name of the engineer designing the strategy.
11. Click Select Solution. The Solution Selector dialogue box is displayed.
12. Select the required solution from the list. Details about the controller type, hardware variant, and options of
the controller for which the solution was designed are displayed along with a description of the solution's
functionality.
Solutions for older firmware versions can be hidden/displayed using the Hide Older Versions check box.
To display all the solutions in the library, clear the Show Compatible Solutions Only check box. The list
can be filtered to display only strategies designed for use in fixed strategy controllers by clearing the Show
Compatible Solutions Only check box and selecting the required library from the Licenced Library box.
Note: Fixed strategy controller will only be able to run a strategy from the library it is licensed to use but
IQSET will not warn you that the solution is not compatible with the actual controller. Programmable
controllers (no license restrictions) will be able to run any solution designed for their controller type.
13. Click OK to return to the Device Details dialogue box. The Select Device button is disabled to prevent the
controller type from being changed.
14. Click OK. The controller(s) will be added to the project.
If the solution used is part of a licensed library the Fixed option will be set for the controller. If you intend to
download this strategy to a programmable controller you should edit the device details to clear the Fixed
option. The controller licence file is also copied to the project's 'License' directory and will be use when the
strategy is downloaded to the controller.
9.3.3 Add Controllers by Copying
If several controllers are to use the same, or similar, strategy it is possible to duplicate controllers by copying them to
a different address. This method can only be used to duplicate controllers within the same project. Copying, and
renaming the .IQ files in the Set Projects directory using Windows Explorer enables controllers to be copied between
projects.
E.g. If controller 27 on LAN 24 was to use the same strategy as controller 26 on the same LAN, the file L024n026.IQ
in the Lan024 sub directory of the Set Projects directory should be copied into the same directory after renaming as
L024n027.IQ. When the project is loaded next time, the new controller will appear in the Project View. The two
controllers will now be identical, and if necessary, changes can now be made to the duplicate strategy.
TIP: If you regularly use the same controller configuration you could create a solution.
To copy a controller:
1. Open the project containing the controller that is to be duplicated.

3. In the Device View right-click the controller that is to be duplicated, and click Copy Device. The Enter
Destination dialogue box is displayed.
4. In the Project box click the project into which the controller is to be copied.
7. Click OK. A copy of the controller will be added to the project at the new address leaving the original
unchanged.
9.3.4 Add Controllers by Importing Files
IQ2 files from pre IQ3 controllers with version 2.1 firmware or above, IQ3 files, IQ4 and IQe files can be imported
into an IQSET project. This enables controllers for which the strategy is not available in IQSET to be added to an
IQSET project. This allows strategy modification, or documentation to be carried out using IQSET.
To add a controller by importing a file:
1. Open the required project, or create a new one.
If using an existing project, ensure that it does not already contain a controller with the same network address
as the one that is to be imported.
3. On the Project menu click Import IQ2 File (V2.1> Firmware Only), Import IQ3 File, Import IQ4 File,
or Import IQe File. A dialogue box is displayed.
If a file does not exist for the controller you can upload the required file from the controller using the System
View.
is displayed.
5. Click Open. The file will be imported, and the controller added to the project.
If the x, y, and page parameters have been defined in the modules, the appropriate pages will be created, and the
modules positioned accordingly. If the x, y, and page parameters are not defined, the modules will be added to the
strategy but will subsequently need to be placed on the strategy pages as required.

9.3.5 Add Controllers Using Project Config
Project Config enables controllers (IQ3 and IQ4 only) along with associated I/O Modules, and sensor, driver, digital
input, knob, switch modules, and to connectives to be quickly added to an IQSET project either by adding them
individually, or by importing the details from an Excel spreadsheet. Use of this feature requires Excel to be installed
on the PC running IQSET.
To add controllers using project config:
1. If information from a spreadsheet is going to be imported create the spreadsheet in the correct format.
2. Run IQSET and specify the IQSET Project.
3. On the Project menu click Project Config. The Project Config dialogue box is displayed.
4. Add the controllers individually, or by importing from a spreadsheet.

To add controllers individually:
 Click Select Controller Type. The Controller Selection dialogue box is displayed.

 Click the required option (IQ3, or IQ4) in the Range area to specify the range of the controller that is to
be added.
 To only show choices for controllers with node controller functionality select the Node Controllers
check box.
 In the Device Type box click the required device type.
 In the Firmware Version box click the firmware version of the controller that is to be added.
 In the Hardware Variant box click the hardware variant of the controller that is to be added.
 In the Options area select the required check box(s) to select any required options (e.g. BACnet).
 Click OK to return to the Project Config dialogue box.
 In the Lan box enter the LAN number of the controller. (1 to 119 excluding addresses 2, 3, and 10).
 In the Node box enter the network address of the controller. (1 to 119 excluding addresses 2, 3, and 10).
 If more than one controller of the same type is to be added in the Controller box enter the number of
controllers that are to be added. The address of the first controller added is the one specified in the
Address box. The address is then incremented to the next valid address in the range (1 to 119 excluding
addresses 2, 3, and 10) for the next controller that is added. This process is repeated for all the controllers
that are to be added.
 Click Add Controller.
To add controllers from a spread sheet:
 Click Import. The Open dialogue box is displayed.
 Click the required file. To select a file stored in a different location, click the drive, or folder in the Look
in box that contains the file, double-click the folders in the folder list until file is displayed.
 Click Open.
Note: Unwanted controllers can be deleted by selecting the required controller, and clicking Delete
Controller.
5. Specify I/O modules that are required. It is not possible to add I/O modules to all controller types. If this is
the case for the selected controller the option is disabled.
To add an I/O module:
 In the top box click the tab for the LAN containing the controller to which the I/O module is to be added,
and click the required controller.
 Click Add IO Module. The I/O Module Setup dialogue box is displayed.
 In the Mod ID box enter the module ID. This specifies the id of the I/O module. This must match the
CAN address set on the I/O module's address switch.
 In the Module Type box click the type of I/O module.
 In the Label box enter a label for the module.
 Click OK.
To delete an I/O module:
 In the top box click the tab for the LAN containing the controller to which the I/O module is to be added,
and click the required controller.
 Click the tab for the I/O module that is to be deleted.
 Click Delete IO Module.
6. Specify strategy modules.
To add strategy modules using quick module add:
 In the top box click the tab for the LAN containing the controller to which the strategy modules are to
be added, and click the required controller.
 Click the Internal tab.
 Click Quick Module Add. The Enter Module Range dialogue box is displayed.
 Select the type of module that is to be added. Selecting 'Undefined' will add modules without specifying
their type. This allows multiple modules to be added when they are to be of different types. The module
type must be specified as below before committing the changes.

 In the Start box enter the module number of the first module that is to be added. If adding more than
one module the module numbers are assigned sequentially.
 In the Total box enter the number of modules that are to be added.
 Click OK.
 Edit the modules as required. Important define any undefined modules.
To add strategy modules by pasting from a spreadsheet:
 Create a spreadsheet with the necessary information for each module in a separate row, with each
parameter in a separate column.
 Copy the required data from the spreadsheet.
 Right click on the area for module sand select Paste Rows from Clipboard.
 Edit the modules as required. Important define any undefined modules.
To delete strategy modules:
 In the top box click the tab for the LAN containing the controller from which the strategy modules are
to be deleted, and click the required controller.
 In the top box click the tab for the LAN containing the controller that is to be edited, and click the
required controller.
 Right click the module that is to be deleted and select Delete Selected Rows. To delete more than one
module hold down CTRL and click the required modules then right click the selection and select Delete
Selected Rows.
7. Edit controller information as required. Information that can be edited is highlighted in orange; information
that can't are highlighted in green.
The network address, device type, firmware version (Fw ver), Options, and label for the controllers can be
edited.
To edit controller information:
 Click the information that is to be changed.
 Enter the required value. Ensure that valid information and characters are used, and where appropriate
match the options available in IQSET. IQSET does not validate the data.
 Click away from the changed information.
8. Edit modules and channels as required. Information that can be edited is highlighted in orange; information
that can't are highlighted in green.
To edit parameters:
 Click the information that is to be changed.
 Enter the required value. Ensure that valid information and characters are used, and where appropriate
match the options available in IQSET. IQSET does not validate the data.
 Click away from the changed information.
To paste data from a spreadsheet:
 Create a spreadsheet with a single column of data with the data for each module/channel in a separate
row.
 Copy the required data from the spreadsheet.
 Right click the first cell in the range of cells that are to be changed and select Paste Column Items from
Clipboard.
Note: Module data can be copied for use in a spreadsheet by selecting the rows containing the required data,
right clicking and selecting Copy Rows to Clipboard to copy entre rows or right clicking the column containing
the data and selecting Copy Column Items to Clipboard to copy the data form the column of the select row.
9. Specify what is to be added to strategy pages by checking or clearing the Sensor, Digin, Drivers, Knobs,
Switches, and To Connective check boxes.

10. Click Commit Changes. The changes will be applied to the project.
9.3.5.1 Create the Spreadsheet
To import controllers into an IQSET project from information in a spreadsheet it is necessary to create the spreadsheet.
To create the spreadsheet:
1. Open the spreadsheet and create a spreadsheet with thirteen columns with the following headings: Device /
Module, Fw Ver, Options, Device Label, LAN, OS, I/O Mod, Channel, Module, Subtype, Label, Units and
Scaling. An example spreadsheet 'SET Import Example.xls' is available in the 'C:\Program Files\Trend
Control Systems\Support Files' folder.
2. Specify the controllers, I/O modules, sensor, driver, and digital input modules that are to be added to the
project.
To specify a controller:
 In a new row enter the hardware variant of the controller in the Device/Module column. This must match
the choices available in the Hardware Variant box of the Controller Selection dialogue box.
 In the same row enter the firmware version of the controller in the Fw Ver column. This must match the
choices available in the Firmware Version box of the Controller Selection dialogue box.
 In the same row enter the options for the controller in the Options column. This must match the choices
available in the Options area of the Controller Selection dialogue box.
 In the same row enter the label for the controller in the Device Label column.
 In the same row enter the controller's LAN number in the Lan column (range 1, 4-9, 11 to 119).
 In the same row enter the controller's address on the Trend network in the OS. column (range 1, 4-9, 11
to 119).
To specify an I/O module:
 In a new row enter the module type of the I/O module in the Device/Module column. This must match
the choices available in the Module Type box of the I/O module Setup dialogue box.
 In the same row enter the label for the I/O module in the Device Label column.
 In the same row enter the LAN number of the controller the module is to be connected to in the Lan
column (range 1, 4-9, 11 to 119).
 In the same row enter the address on the Trend network of the controller the module is to be connected
to in the OS. column (range 1, 4-9, 11 to 119).
 In the same row enter the module id of the I/O module in the I/Mod column. This must match the choices
available in the Mod ID box of the I/O module Setup dialogue box.
To specify sensor, driver, or digital input module:
 In a new row or on the first row of the controller in which the module is to be added, or I/O module it is
to connect to specify the number of the I/O module the module in the I/O Mod column. If connecting to
an I/O channel on the controller's main board enter '0'.
 In the same row specify the I/O channel the module is to connect to in the Channel column.
 In the same row specify the module using its module identifier and module number (e.g. S1 specifies
sensor 1) in the Module column. For details of the module identifier, see the appropriate module section
of this manual.
If specifying a multistage digital driver assign create a row for each channel and assign it to the digital
driver, see below:
 In the same row specify the module sub type in the SubType column, see below. For details of the
module identifier, see the appropriate module section of this manual.
Module Sub Type Module
1 Digital Driver
Drivers 2 Analogue Driver
3 Time Proportional Driver

Module Sub Type Module

4 Raise/Lower End Driver
5 Binary Hysteresis Driver
6 Time Proportional + O/R Driver
7 Raise/Lower Continuous Driver
8 Multi Stage Digital Driver
0 External Analogue Sensor
1 Internal Analogue Sensor
Sensors
2 External Digital Sensor
3 Internal Digital Sensor
0 External Digital Input
Digital inputs
1 Internal Digital Input
 In the same row specify the module's label in the Label column.
 In the same row specify the module's units in the Units column. (sensors only).
 In the same row specify the module's scaling in the Scaling column. (sensors only). This is the 'Unique
Sensor Reference' for the required sensor scaling as it appears in the Unique Sensor Reference box of
the Sensor Type dialogue box.
3. Repeat step (2) for until everything is defined.
4. Save the file.
9.3.6 Delete a Controller
Controllers that are no longer required in the project can be deleted.
To delete a controller:
2. In the Device View right-click the controller that is to be deleted, and click Delete Device. A dialogue box
is displayed asking for confirmation of the deletion.
3. Click Yes to delete it.
Remember that deleting a controller will also permanently delete the strategy pages and associated strategy.
9.3.7 Edit a Controller
The device details enable information about the controller, and who designed the strategy to be stored.
To edit a controller:
1. Display a strategy page for which details are to be edited.

2. On the Device menu click Device Details. The Device Details dialogue box is displayed.
3. In the appropriate boxes enter the required details.

4. Once the details have been specified, click OK.
9.3.8 Add a LAN
LANs must be added to the project to define the network structure of the site containing the actual controllers.
To add a LAN:
1. Specify the project.
3. In the Device View click the top level of the project.
4. Right-click, and click Insert Lan. The Lan Details dialogue box is displayed.
5. In the Lan Number box enter the number of the LAN (0 to 119 excluding addresses 2, 3, and 10). 0 specifies
a stand-alone LAN.
6. In the Type box specify the LAN type. For a LAN of BACnet NTDs select BACnet (NTDs are only required
if IC Comms messages are to be sent to BACnet devices.). For a LAN on MS/TP (for IQECOs) select Trend-
MSTP, otherwise select Trend-IQ. If an MSTP LAN is added an IQ4NC must be added to the LAN to
enable communications with devices on other LANs.
7. In the Label box enter a label for the LAN.
8. In the Details box enter a description for the LAN.
9. Click OK.

9.3.8.1 Delete a LAN
To delete a LAN:
2. Delete all the controllers on the LAN.
3. In the Device View right-click the LAN that is to be deleted, and click Delete Lan.
4. IQSET will ask for confirmation of the deletion, if you click Yes it will then ask it all the files associated
with the LAN are to be deleted. Clicking Yes will remove the LAN from the project, and delete any associated
files. Clicking No will remove the LAN from the project, but leave the files associated with it.
9.3.8.2 Edit LAN Details
It is possible to specify information about the LANs in the network structure, which can be viewed later. It is not
possible to change the LAN number or type.
To edit details for a LAN:
2. In the Device View right-click the LAN for which details are to be viewed, and click Lan Details. The Lan
Details dialogue box is displayed.

4. Once the details have been specified, click OK.

9.4 Configure Controller Strategy

IQSET enables the strategy for IQ controllers with to be configured by adding modules to strategy pages, linking them
together, and then editing the module’s configuration parameters to define the strategy. Once the strategy is complete,
files that can be downloaded to the controllers can be created.
Configure an IQ4 Controller
Configure an IQ3 Controller
Configure an IQECO Controller
Configure a Pre IQ3 Controller
9.4.1 Configure an IQ4 Controller
To configure an IQ4 controller:
1. Add a controller of the required type.
2. Set up the address module.
3. For IQ4NC controllers set up the network configuration.
4. For /LAN and IQ4NC controllers configure the IQ LAN Network Module.
5. For controllers that are to connect to an Ethernet network, set up the Ethernet IP module.
6. For IQ4NCs set up the BACnet MSTP network module.
7. For IQ4s that are to connect to a BACnet network, set up the BACnet IP network module.
8. For IQ4s that are to connect to a BACnet network, set up the BACnet Application network module.
9. Set up the sensor type modules.
10. Add a States Category Module. (IQ4 v3.50 or greater).
11. If configuring an /XNC variant that is to communicate with a 3rd Party system via a serial connection set up
a Type 17 (Trend Serial) Network module for each different serial connection that is to be used.
12. If a Wallbus device is to be connected to the IQ4 add a Type 14 (Wallbus) Network module to the strategy.
13. If a Wallbus device is to be connected to the IQ4 add a Type 2 (Wallbus) Interface module to the strategy for
each device that is to be connected.
Note: Strategy blocks are provided for the strategy configuration for all of Trend's Wallbus devices.
14. If configuring a /INT variant to communicate with a Modbus device add a Type 8 (MODBUS Serial)
Network module or Type 19 (MODBUS IP) Network module to the strategy.
15. If configuring a /INT variant (v4.30 or greater) to communicate with an M-bus device add a Type 15 (M-
busl) Network module to the strategy.
16. If configuring a /INT variant to communicate with a Modbus device add a Type 3 (Modbus) Interface Module
to the strategy for each device that is to be connected.
17. If configuring a /INT variant (v4.30 or greater) to communicate with an M-bus device add a Type 4 (M-bus)
Interface Module to the strategy for each device that is to be connected..
Note: Connection of an IQ4 to Modbus or M-bus devices is known as IQ Interfacing, strategy blocks are
provided for the necessary strategy configuration for common meters and VSDs - see IQ Interfacing for
details of using the IQ Interfacing strategy blocks.
16. If configuring a /XNC variant set up the XNC Interface Module.
17. Add the modules onto the pages Modules can also be added by copying and pasting from another page, or
by using strategy blocks to form the strategy. Strategy pages should be added as they are needed
18. Move the modules on the page so that the links can be easily made
19. Link the modules so that the information flows through the strategy correctly IQSET uses its knowledge of
modules to prevent mistakes such as connecting a digital value to a point requiring an analogue value, or
linking a module to one it is not allowed to be linked to. Connectives can be used to link to modules on other
strategy pages. If the strategy is using ic comms the link to an ic comms module in another controller can be
indicated by linking to a dummy ic comms module.
20. Set up the alarm handling strategy.
21. For IQ4E controllers if additional I/O modules are to be used add them to the strategy.
22. Assign I/O channels to the external sensors, external digital inputs and drivers.
23. Edit the module's configuration parameters
24. Set up the sequence table to ensure that the strategy is executed in the correct order.
25. If required set up event driven strategy.
26. Set up the controller's normal occupation time profile.
27. Set up Calendar modules. (IQ4 v3.50 or greater).
28. Set up any exceptions to the normal occupation time profile.
29. Set up ic comms.
30. Set up security.
31. Set up CNC User Modules. (IQ4v3.60 or greater)

32. Set up vCNC Modules. (IQ4v3.60 or greater)
33. Configure the Web Server.
34. Set up display and directory modules.
35. Set up graphical display pages.
Once the strategy is complete, an IQ4 file must be created, and downloaded to the controller.
9.4.2 Configure an IQ3 Controller
To configure an IQ3 controller:
1. Add a controller of the required type.
3. For controllers with version 1.3 firmware or greater that are to connect to an Ethernet network, set up the
Ethernet IP module.
4. For controllers with version 2.20 firmware or less that are to connect to a BACnet network, set up the BACnet
network module.
5. For controllers with version 2.30 firmware or greater that are to connect to a BACnet network, set up the
BACnet IP network module.
6. For IQ3/BACnet controllers with version 2.30 firmware or greater that are to connect to a BACnet network,
set up the BACnet Application network module.
7. For IQ3 controllers with BINC functionality set up the BACnet MSTP network module.
8. Set up the XNC interface module.
10. Add the modules onto the pages. Modules can also be added by copying and pasting from another page, or
by using strategy blocks to form the strategy. Strategy pages should be added as they are needed.
11. Move the modules on the page so that the links can be easily made.
12. Link the modules so that the information flows through the strategy correctly. IQSET uses its knowledge of
14. If additional I/O modules are to be used add them to the strategy.
15. Assign I/O channels to the external sensors, external digital inputs and drivers.
16. Edit the module's configuration parameters.
18. If required set up event driven strategy.
19. Set up the controller's normal occupation times.
20. Set up any exceptions to the normal occupation times.
24. Set up graphical display pages.
Once the strategy is complete, an IQ3 file must be created, and downloaded to the controller.

9.4.3 Configure an IQECO Controller
To configure an IQECO controller:
1. Add a controller.
3. Set up the BACnet MSTP network module.
4. IQECO controllers v2.0 or greater only. Set up the sensor type modules.
8. IQECO v2.0 or greater only. Set up the alarm handling strategy.
9. IQECO v2.30 or greater. If a Wallbus device is to be connected to the IQECO add a Type 14 (Wallbus)
Network module to the strategy, and add a Type 2 (Wallbus) Interface module to the strategy for each device
that is to be connected.
Strategy blocks are provided for Trend's Wallbus devices.
Note: IQECO v2.0 to 2.23 can be connected to a Wallbus display but a different method of configuration is
required - see Add an IQECO Display Device.
10. Edit the module’s configuration parameters.
Note: A module must only be included in the sequence table once.
Once the strategy is complete, an IQe file must be created, and downloaded to the controller.
9.4.4 Configure a Pre IQ3 Controller
Note: IQSET does not allow calendar and time modules to be set up for pre IQ3 controllers. These modules must be
set up using a piece of software that allows access to the calendar or time modules.
To configure a pre IQ3 controller:
1. Add a controller.
4. Set up ADL support.
5. Set up XNC support if the controller has it.
strategy pages. Undefined connectives allow links to be made to modules that have not yet been put in the
strategy, or links to be made to particular nodes. If the strategy is using ic comms, it is possible to show that
a module is linked to an ic comms module in another controller can be indicated by linking to a dummy ic
comms module.
10. Edit the module’s configuration parameters.
12. If required set up fast sequencing.
13. Set up the controller's normal occupation time profile.
Once the strategy is complete, an IQ2 or LDF file must be created, and downloaded to the controller.

9.4.5 Configure a Fixed Strategy Controller
For fixed strategy controllers, the strategy is specified when the controller is added from one of the solutions. It is not
possible to add, delete or move any of the modules. The only changes than can be made to the strategy are changes to
the modules parameters using the Edit Parameters command.
To configure a fixed strategy controller:
1. Add a controller manually or using a solution or ensure that the Fixed option is selected.
2. Edit the module's configuration parameters.
Note: It is possible to change the strategy of a fixed strategy controller by selecting another solution.
9.4.5.1 Change a Fixed Strategy Controller`s Strategy
It is possible to change the strategy of a fixed strategy controller by selecting another solution from the same library
without losing any changes that have been made to module parameters. The change can be made to an individual
controller as described in the 'Change a Single Fixed Strategy Controller's Strategy' section of this manual, or to
multiple controllers as described in the 'Change Multiple Fixed Strategy Controllers Strategies' section of this manual.
9.4.5.1.1 Change a Single Fixed Strategy Controller's Strategy
To change a single fixed strategy controller's strategy:
1. Display the device details for the controller whose strategy is to be changed. The Device Details dialogue
box is displayed.
Note: It is important that you only select a fixed function controller (Fixed option selected).
2. Click Select Solution. The Solution Selector dialogue box is displayed.
The dialogue box displays a list of strategies in the same library as the original strategy as it is only possible
to change the strategy to use a solution form the same library as the original. Solutions for older firmware
versions can be hidden/displayed using the Hide Older Versions check box.
3. Select the required solution from the list in the Solution box.
4. Click OK to return to the Device Details dialogue box.
5. Click OK. A message is displayed.
6. Click Yes to continue. A message is displayed asking if changes made to module parameters are to be kept.
7. Click Yes to preserve the changes or No to use the parameter values from the solution. After the selection,
the strategy is changed.

9.4.5.1.2 Change Multiple Fixed Strategy Controllers Strategies
To change the strategies of multiple fixed strategy controllers:
2. In the Device View click the next to the required controllers. IQSET will indicate the selected controllers
with a .
Note: It is important that you only select fixed function controllers (Fixed option selected).
3. On the Project menu click Change Fixed Strategies. The Project Strategy List dialogue box is displayed.
4. Select the check boxes for the controllers for which the strategies are to be changed. Only select controllers
with strategies from the same library. To select all the controllers with strategies from the same library right
click a controller with a strategy from the required library and select Select All In Library. To clear any
selection right click on a controller and select Unselect All.
5. Click Select New Strategy. The Solution Selector dialogue box is displayed. It displays a list of strategies
in the same library as the original strategy as it is only possible to change the strategy to use a solution form
the same library as the original. Solutions for older firmware versions can be hidden/displayed using the Hide
Older Versions check box.
6. Select the required strategy from the list.

7. Click OK to return to the Project Strategy List dialogue box.

8. To preserve any changes made to module parameters select the Preserve Configured Strategy Data check
box. Clear the Preserve Configured Strategy Data check box to use the parameter values from the solution.
9. Click OK. Each controller will be opened in turn and its strategy replaced with he selected one.
9.4.6 Set up the Address Module
The address module determines information about how the controller communicates over the network.
To set up the address module for an IQ controller:
1. Display a strategy page for the controller for which the address module is to be specified.
2. Right-click the strategy page, and point to Device and click Address Module, or on the Device menu click
Address Module. The IQ Address Module dialogue box is displayed. The appearance of this dialogue box
will vary depending on the type of controller being added.
Note: The appearance of this dialogue box will vary depending on the type and version of controller.
3. Specify the address module parameters: IQ4 and IQ3v1.3 or greater controllers, Pre v1.3 IQ3 controllers,
IQECO controllers, or Pre IQ3 controllers.
IQ4, and IQ3v1.3 or greater controllers:
 If the identifier is to be specified clear the Not Sent check box and enter the controller's identifier in the
Identifier box (30-characters).
Note: For these parameters to be included in the data file when it is created the Not Sent check box must
be cleared when the file is created.
 If Attributes F, G, H, I, J and K are to be specified in the Attribute boxes enter 30-character attributes
for the controller as required.
 If the LAN number and network address is to be specified clear the Not Sent check box and specify the
parameters. In the Local Lan box enter the required LAN number (1, 4 to 119 excluding 10) and in the
Local Node box enter the required network address (1, 4 to 119 excluding 10).
Note: Changing the LAN number and Local node in this way is not recommended, it will not move the
controller in the LAN structure, however these values will have downloaded to the controller.
be cleared when the file is created. Adding these parameters to the data file may cause duplicate
addresses when the file is downloaded.

 If the controller's local supervisors port and USB supervisor port address are to be set up clear the Not
Sent check box and specify the parameters. In the Supervisor Port Address box enter the address of
the local supervisor port. (0, 4 to 119 excluding 10). If set to 0 the device connected using the local
supervisor port will only be able to communicate with the local controller. IQ4 controllers only. In the
USB Supervisor Port Address box enter the address of the USB supervisor port. (0, 4 to 119 excluding
10).
be cleared when the file is created. Adding these parameters to the data file may cause duplicate
addresses when the file is downloaded.
 In the General Alarm Group box select the alarm group that is to be used for the controller's general
alarms.
 To specify the default display language, click the language in the Available Display Languages box
and click . The selected language will be displayed with a .

 IQ3 controllers only. To specify other languages that are to be downloaded to the controller click the
languages in the Available Display Languages box and click . Languages that are to be downloaded
are indicated by an . Languages that are not going to be downloaded are indicated by an . To specify
a language not to be downloaded click it and then click . The default language is always downloaded.
Pre v1.3 IQ3 controllers:
 If Attributes F (2), G (3), H (4), I (5), J (6) and K (7) are to be specified in the Attribute boxes enter 30-
character attributes for the controller as required.
 If the LAN number and network address is to be specified clear the Not Sent check box and specify the
parameters. In the Local Lan box enter the required LAN number (1, 4 to 119 excluding 10), and in the
Local Node box enter the required network address (1, 4 to 119 excluding 10).
Note: Changing the LAN number and Local node in this way is not recommended, it will not move the
controller in the LAN structure, however these values will have downloaded to the controller.
 If the controller's local supervisors port is to be set up clear the Not Sent check box and specify the
parameters. In the Supervisor Port Address box enter the address of the local supervisor port. (0, 4 to
119 excluding 10). If set to 0 the device connected using the local supervisor port will only be able to
communicate with the local controller.
 If the Ethernet information (IP address, subnet mask, default router, and UDP port) is to be specified
clear the Not Sent check box in the Ethernet area and specify the addressing information. In the
Addressing Mode box select Enter Manually, or Obtain Automatically to specify whether the
controller is to use automatic or manual addressing. If 'Obtain Automatically' is selected the IP Address,
Subnet Mask, WINS Servers, and DNS Servers boxes cannot be edited and the controller will obtain
their values from the DHCP server.
 If the addressing mode has been set to 'Enter Manually' specify the IP address, subnet mask, default
router, and UDP port.
To specify the UDP port:
 In the UDP Port box enter the UDP port number.
Note: It is recommended that the UDP port is not changed.
To specify the default router:
 Enter IP address of the router to which messages are sent if the destination address is not on the
local subnet in the Default Router box in the format below:
xxx.xxx.xxx.xxx

E.g. 128.1.24.34
To specify the subnet mask:
 Enter the controller's subnet mask in the Subnet Mask box in the format below:
xxx.xxx.xxx.xxx
E.g. 128.1.24.34
The subnet mask must ensure that all controllers for the same internetwork that are not separated by
routers are on the same subnet. It is therefore recommended that all controllers that are not separated by
routers have the same subnet mask.
To specify the IP address:
 Enter the controller's IP address in the IP Address box in the format below:
xxx.xxx.xxx.xxx
E.g. 128.1.24.34
The IP address for each controller must be unique to avoid address clashes. IP address in the following
ranges should not be used:
127.x.x.x.x - Reserved for loopback
Non-masked part of IP address - The non-masked part of the IP address cannot be all 1’s or 0’s e.g. if IP
address is 1.2.x.x and subnet mask is 255.255.0.0 then x.x. cannot be either 255.255 or 0.0.
224.0.0.0 to 239.255.255.255 - Reserved for multicast
240.0.0.0 to 247.255.255.255 - Reserved for experimentation and development
x.x.x.255 - Reserved for broadcast
alarms.
 If the controller is to send emails enter the IP address or host name of the email server that is to be used
in the Email Server Addr box.
 To specify the default display language, click the language in the Available Display Languages box
and click . The selected language will be displayed with a .

 To specify other languages that are to be downloaded to the controller click the languages in the
Available Display Languages box and click . Languages that are to be downloaded are indicated
by an . Languages that are not going to be downloaded are indicated by an . To specify a language
not to be downloaded click it and then click . The default language is always downloaded.
IQECO controllers:
 If Attributes F (2) and G (3) are to be specified clear the Not Sent check box and in the Attribute boxes
enter 30-character attributes for the controller as required.
 For IQECO v1.0 only if the alarm LAN and alarm address parameters are to be specified clear the Not
Sent check box and specify the parameters. In the Alarm Lan and Alarm Address boxes enter the LAN
number of the device to which alarms are to be sent (0, 4 to 119 excluding 10), and the network address
of the device to which alarms are to be sent. (0, 4 to 119 excluding 10). If the alarm LAN is set to 0
alarms are not sent to the local LAN. If the alarm address is set to 0 alarms are not sent if set to 2 alarms
are sent to the device directly connected to the controller.

 In the Strategy Name box enter a name for the strategy. (20-characters).
 IQECO v2.0 If the controller is to manage triac outputs to prevent large electrical demands on the
controller clicking the Disabled (Power Managed) button.
 IQECO v2.0. Specify the mode used to determine when the raise/lower drivers calculate the actual
location of the valve by selecting the required option in the Raise/Lower Sync box.
 In the Strategy Revision box enter the revision number of the strategy.
Pre IQ3 controllers:
 In the Identifier box enter the controller's identifier (15-characters)
 If required, in the Attribute F (2) box enter a 10-character attribute for the controller. This can be used
in conjunction with the identifier and the other attributes to identify the controller.
 If required, in the Attribute G (3) box enter a 10-character attribute for the controller. This can be used
 If required, in the Attribute H (4) box enter a 10-character attribute for the controller. This can be used
 If required, in the Attribute I (5) box enter a 10-character attribute for the controller. This can be used
 If required, in the Attribute J (6) box enter a 10-character attribute for the controller. This can be used
 If required, in the Attribute K (7) box enter a 10-character attribute for the controller. This can be used
 If the controller's local supervisors port is to be set up in the Supervisor Port Address box enter the
address of the local supervisor port. (0, 4 to 119 excluding 10). If set to 0 the device connected using the
local supervisor port will only be able to communicate with the local controller.
 If the controller's NDP port is to be set up in the NDP Port Address box enter the address of the NDP
port. (0, 4 to 119 excluding 10). If set to 0 the device connected using the NDP port will only be able to
communicate with the local controller.
 In the Alarm Address box enter the network address of the device to which alarms are to be sent. (0, 4
to 119 excluding 10). If set to 0 alarms are not sent if set to 2 alarms are sent to the device directly
connected to the controller.
 In the Remote Lan box enter the LAN number of the device to which alarms are to be sent. (0, 4 to 119
excluding 10). If set to 0 alarms are not sent to the local LAN.
 If alarms are to be sent in text format, select the Text Switch check box. If clear alarms are sent in coded
format.
 In the Display Language box select the language that is to be used by the controller.
alarms.
 IQ2 v3.1 of greater only. If the PIN of the day functionality is to be disabled, select the Pin of the Day
check box.
Caution: This feature should be used with caution should the PIN be forgotten and Pin of the day has been
disabled there is no way to unlock the controller.
4. Click OK.

9.4.7 Set up Network Configuration
For IQ4NC controllers the network configuration must be set up. It determines which networks the controller
communicates with and how it communicates over those networks. The mode of operation is determined by selecting
one of several predefined configurations, or by setting it up manually. It also provides access to the setup of the
individual network.
To set up the network configuration:
1. Display a strategy page for the controller for which the network configuration is to be set up.
2. Right-click the strategy page, and point to Device, point to Network and click NC Configuration, or on the
Device menu click NC Configuration. The NC Configuration dialogue box is displayed.
3. Select the required configuration from the selection on the left. To configure the configuration manually
select 'Manual' and set up the configuration as required by selecting the required options from the drop-down
list and entering the required values. Information that can be edited is highlighted in orange; information that
can't are highlighted in green.
Configuration Description
Configures the IQ4NC to interface (INC) between an internetwork running over an
Ethernet to MSTP Ethernet network and a LAN running on an MS/TP network. This is intended for
connecting a LAN of IQECO controllers to an internetwork on Ethernet.
Configures the IQ4NC to interface (INC) between an internetwork running over a Trend
Trend
current loop network and a LAN running on an MS/TP network. This is intended for
Internetwork to
connecting a LAN of IQECO controllers to an internetwork on a Trend current loop
MSTP
network.
Configures the IQ4NC to interface (INC) between an internetwork running over an
Ethernet to Trend Ethernet network and a LAN running on a Trend current loop network. This is intended
LAN for connecting a LAN of controllers on a Trend current loop network to an internetwork
on Ethernet.
Ethernet to Trend Configures the IQ4NC to interface (INC) between an internetwork running over an
Internetwork Ethernet network and an internetwork running on a Trend current loop network.
Enables the IQ4NC to be configured to operate in other modes not covered by the
Manual
standard configuration described above.

Note that a good understanding of Trend networking is required for this setup. It is strongly recommended
that only the standard configurations are used.
4. Click OK. To undo any changes, click Undo.
9.4.8 Configure the IQ LAN Network Module
IQ4 and controllers IQ3 v1.3 or greater the IQ LAN network module determines the parameters specific to the IQ
current loop network. It should only be set up for controllers that are to build LANs and internetworks on the Trend
current loop. For IQ4 controllers that are to build LANs and internetworks over the Ethernet network the IQ LAN
network module must be disabled. For IQ4 Ethernet only controllers this module must always be disabled.
To configure the IQ LAN network module:
1. Display a strategy page for the controller for which the IQ LAN network module is to be specified.
2. Right-click the strategy page, and point to Device, point to Network and click IQ LAN Network Module,
or on the Device menu click IQ LAN Network Module. The IQ LAN Network Module dialogue box is
displayed.
3. For IQ3 v2.3 controllers or greater and IQ4 controllers in the LAN Label box enter the label for the
controller's LAN.
4. For IQ3 v2.3 controllers or greater and IQ4 controllers in the Alarm Group box specify the alarm group to
which all IQ LAN network alarms are sent. If set to zero alarms only sent to connected supervisor devices.
5. If the module enable and baud rate are to be specified clear the Not Sent check box and specify the
information:
 Enable/disable the module as required by selecting or clearing the Module (Disabled) check box.
Note: For IQ4 Ethernet only controllers, and IQ4 controllers that are to build LANs and internetworks
over the Ethernet network this module must always be disabled.
 For IQ4 controllers specify whether the baud rate is to be determined automatically or entered manually,
by selecting or clearing the Autobaud (Enabled) check box.
 For IQ4 controllers when the 'Autobaud' option is disabled select the required baud rate from the Baud
Rate box.
Note: For these parameters to be included in the data file when it is created the Not Sent check box must be
cleared when the file is created.
6. Click OK.
9.4.9 Set up the Ethernet IP Module
The Ethernet IP module determines the Ethernet settings for IQ4 and IQ3 controllers with version 1.3 firmware or
greater. It needs to be to be set up if the controller is to connect to the Trend network using Ethernet, if its virtual CNC
is to be used, if IP alarms are to be used, or the controller’s web server is to be accessed. For details of the Ethernet IP
module see the IQ3 Configuration Reference Manual (TE200768) or IQ4 Configuration Reference Manual
(TE201263).
Note: For IQ4 controllers that are to build LANs and internetworks over the Ethernet network the IQ LAN network
module must be disabled.
To set up the Ethernet IP module:
1. Display a strategy page for the controller for which the Ethernet IP module is to be specified.

2. Right-click the strategy page, and point to Device, point to Network and click Ethernet IP Module, or on
the Device menu click Ethernet IP Module. The Ethernet IP Module dialogue box is displayed.
controller's LAN.
4. If the IP address is to be specified clear the Not Sent check box in the Ethernet area and enter the controller's
IP address in the IP Address box in the format below.
xxx.xxx.xxx.xxx
E.g. 128.1.24.34
The IP address for each controller must be unique to avoid address clashes. IP address in the following ranges
should not be used:
IP Address Reason
127.x.x.x.x Reserved for loopback.
The non-masked part of the IP address cannot be all 1’s or 0’s e.g. if IP address
Non-masked part of IP
is 1.2.x.x and subnet mask is 255.255.0.0 then x.x. cannot be either 255.255 or
address
0.0.
224.0.0.0 to
Reserved for multicast.
239.255.255.255
Addresses 240.0.0.0 to
Reserved for experimentation and development.
247.255.255.255
x.x.x.255 Reserved for broadcast.
cleared when the file is created. Adding these parameters to the data file may cause duplicate addresses
when the file is downloaded.
5. If the Ethernet information (subnet mask, default router, and UDP port) is to be specified clear the Not Sent
check box in the Ethernet area and specify the addressing information:

 specify whether the controller is to use automatic or manual addressing. If 'Obtain Automatically' is
selected the IP Address, Subnet Mask, WINS Servers, and DNS Servers boxes cannot be edited and the
controller will obtain their values from the DHCP server.
 If the addressing mode has been set to 'Enter Manually' specify the IP address, subnet mask, default
router, and UDP port.
To specify the UDP port:
 In the UDP Port box enter the UDP port number.
Note: It is recommended that the UDP port is not changed.
To specify the default router:
 Enter IP address of the router to which messages are sent if the destination address is not on the local
subnet in the Default Router box in the format below:
xxx.xxx.xxx.xxx
E.g. 128.1.24.34
To specify the subnet mask:
 Enter the controller's subnet mask in the Subnet Mask box in the format below:
xxx.xxx.xxx.xxx
E.g. 128.1.24.34
The subnet mask must ensure that all controllers for the same internetwork that are not separated by
routers are on the same subnet. It is therefore recommended that all controllers that are not separated by
routers have the same subnet mask.
To specify the IP Address:
 Enter the controller's IP address in the IP Address box in the format below:
xxx.xxx.xxx.xxx
E.g. 128.1.24.34
The IP address for each controller must be unique to avoid address clashes. IP address in the following
ranges should not be used:
127.x.x.x.x - Reserved for loopback
Non-masked part of IP address - The non-masked part of the IP address cannot be all 1’s or 0’s e.g. if IP
address is 1.2.x.x and subnet mask is 255.255.0.0 then x.x. cannot be either 255.255 or 0.0.
224.0.0.0 to 239.255.255.255 - Reserved for multicast
240.0.0.0 to 247.255.255.255 - Reserved for experimentation and development
x.x.x.255 - Reserved for broadcast
6. For IQ3 controllers with version 2.2 firmware or greater and IQ4 controllers (not IQ4NC) select the
Standalone Mode Enabled check box if the controller is to operate in standalone mode. This option should
only be selected if the controller is the only controller on the network as it prevents the controller from
attempting to find other controllers on the Ethernet network.
7. In the Web Server Mode box specify the web server operation.
Option Description
Off Both the HTTP and HTTPS web servers are OFF
HTTPS (HTTP HTTPS web server is ON and requests to the HTTP web server are redirected to the
Redirect) HTTP server, HTTP server is OFF
HTTPS Only HTTPS web server is ON, HTTP server is OFF
HTTP & HTTPS Both the HTTP and HTTPS web servers are ON (not recommended)
HTTP Only Only the HTTP web server is ON (not recommended)
8. If the HTTP web server is being used (not recommended) specify the port number for the HTTP web server
in the Web Server Port box.

9. If the HTTPS web server is being used specify the port number for the HTTPS web server in the Secure
Web Server Port box.
10. For IQ4 v3.60 controllers or greater if the default value for the SSH port used for secure vCNC connections
is not suitable specify a suitable value in the Secure Access Port box.
11. For IQ3 controllers with version 2.2 firmware or greater and IQ4 controllers select the required option from
the XML Web box to specify whether the controller's XML web services is to be enabled.
Option Description
XML interface
The controller's XML Web services are disabled.
OFF
Basic IQ
The controller's XML Web services are enabled.
authentication
Write IQ4 v3.1 or greater only. The controller's XML Web services are enabled, and writes to
authentication the controller using the XML web services are protected using HMAC_MD5 security.
Note: For IQ3 controllers the XML server functionality requires a licence. Contact Trend Customer Support
for details.
12. For IQ3 v2.3 controllers or greater and IQ4 controllers in the Alarm Group box specify the alarm group to
which all Ethernet IP network alarms are sent. If set to zero alarms only sent to connected supervisor devices.
13. If the controller is to send emails enter the IP address or host name of the email server that is to be used in
the Email Server Addr box.
14. For IQ3 v3.0 controllers or greater and IQ4 controllers if the controller is to send emails and the mail server
requires security enter the required user name and password in the Email User Name and Email Password
boxes.
15. For IQ4 v3.30 controllers or greater specify the TCP port used by the email server in the Email Port box.
16. For IQ4 v3.30 controllers or greater specify the security to be used for email alarms in the Email Security
box.
17. For IQ4 v3.30 controllers or greater specify whether Email certificates are to be ignored using the Email
Certificate ignore check box. It should normally be enabled, but can be disabled if the IQ4 has problem
authenticating the certificate.
18. Specify the minimum email TLS version in the Email Min TLS version box.
19. If the controller's host name, WINs servers, and DNS servers are to be specified clear the Not Sent check
box in the DHCP area and specify the information.
 In the Host Name box enter the controller's host name. It provides a network communication name for
the controller. It is separate from the Identifier. It must be unique on the network, and must not be greater
than 15-characters in length and can only contain 7-bit ASCII characters in the range A-Z, a-z or 0-9
plus ‘-‘ or ‘_. It must start with a character in the range A-Z or a-z and must not end with ‘-‘ or ‘_’.
 For IQ3 controllers only specify whether the controller's default hostname is enabled or disabled by
selecting/clearing the Disable Default Hostname check box.
 Click in the WINS Servers area, the WINS Server dialogue box is displayed. In the IP Address
box enter the IP address of the WINS server, and click OK.
 Click in the DNS Servers area, the DNS Server dialogue box is displayed. In the IP Address box
enter the IP address of the DNS server, and click OK..
20 If the internetwork is to be built across routers clear the Not Sent check box in the Remote Devices area and
specify the remote devices.
 In the Remote Devices box click the remote device that is to be set up a is displayed.
 Click the Remote Device dialogue box is displayed.
 In the Device Address box enter the IP address or host name of the remote device.
 In the Subnet box enter the device’s subnet mask.
 Click OK.
Or
 Click Use Project Defaults to use the list of remote devices specified for the project.

21 Click OK.
9.4.10 Set up the BACnet Network Module
IQ3/BACnet controllers with firmware v2.20 or below. The BACnet network module determines the controller's
BACnet settings. It needs to be to be set up if the controller is to connect to a BACnet network. For details of the
BACnet network module see the IQ3 Configuration Reference Manual (TE200768).
To set up the BACnet network module:
1. Display a strategy page for the controller for which the BACnet network module is to be specified.
2. Right-click the strategy page, point to Device and click BACnet Network Module, or on the Device menu
click BACnet Network Module. BACnet Network Module dialogue box is displayed.
3. If there is an Enable BACnet Module button click it to enable the module. If there is a Disable BACnet
Module button the module is already enabled.
4. In the Manual Device Instance box click Automatic or Manual to specify whether the controllers address
on then BACnet network is determined manually or automatically. If determined automatically the address
is calculated using the formula below:
(LAN Number*100) + Local node
5. If the address is to be specified manually in the Device Instance box enter the controller's address on the
BACnet network.
6. In the UDP Port box enter the UDP port of the controller. This defines the UDP port used by the controller
to send messages to other Trend system devices on BACnet.
7. In the Network Number box enter the controllers BACnet network number. Range = 0 to 65534. Only a
single network number is allowed on a single Ethernet subnet, and must be unique on the Ethernet network.
8. If the controller is to send an 'I am' message over the BACnet network when it powers up, click Disabled
(Send I-Am at Startup).
9. By default, the BBMD functionality is disabled which should be satisfactory in most cases, but if the BACnet
segment does not have a BBMD set up the IQ3 controller can act as the BBMD in which case the BDT list
must be set up. BBMDs enable BACnet devices to communicate across IP routers, only one BBMD device
is allowed on each IP subnet. The list should include the BBMD device for each IP subnet containing devices
that are to be communicated with.
To set up the BBMD list:
 Click Disabled (BBMD) to enable BBMD. If there is an Enable button BBMD is enabled.

 Double click an item in the BDT List, or right click an item in the list and click Edit. The BDT Item
 In the Remote BACnet IP Address box enter the IP address of the BBMD device that is being specified.
 In the Remote BACnet Subnet box enter the BACnet subnet of the BBMD device that is being
specified. It is recommended that this is set to 255.255.255.255.
 In the Remote BACnet UDP Port box enter the UDP port used by the BBMD device that is being
specified.
 Click OK.
To remove a device from the BDT list right click it and click Delete. Devices can be edited as described
above.
Note: Only one BBMD device is allowed on each IP subnet The BBMD functionality will not work with
devices that use automatic IP addressing (DHCP), and under such condition should be left disabled.
10. By default, BTL compliance is enabled which means that the controller's schedules are read only over
BACnet. To maintain BTL compliance ensure that the button next to 'BTL Compliance' is set to 'Enabled'. If
schedule offset modules are required to be read only over BACnet click Enabled (BTL Compliance) to
disable BTL compliance the button will change to Disabled.
Note: Disabling BTL compliance could cause problems if devices attempt to write to the Schedule Offset
modules over BACnet.
11. Click OK.
9.4.11 Set up the BACnet IP Network Module
IQ4/BACnet, IQ4NC controllers and IQ3/BACnet controllers with firmware v2.30 or greater. The BACnet IP network
module determines the controller's BACnet IP settings. It needs to be to be set up if the controller is to connect to a
BACnet network. For details of the BACnet network module see the IQ3 Configuration Reference Manual
(TE200768), or the IQ4 Configuration Reference Manual (TE201263).
To set up the BACnet IP network module:
2. Right-click the strategy page, point to Device, point to BACnet and click BACnet IP, or on the Device menu
click BACnet IP. The BACnet IP Module dialogue box is displayed.
3. In the Label box enter the module's label.

4. In the Network Number box enter the controllers BACnet network number. Range = 0 to 65534. Only a
single network number is allowed on a single Ethernet subnet, and must be unique on the Ethernet network.

5. Enable/disable the module as required by selecting or clearing the Module (Disabled) check box.
6. In the UDP Port box enter the UDP port of the controller. This defines the UDP port used by the controller
to send messages to other Trend system devices on BACnet.
7. By default, the BBMD functionality is disabled which should be satisfactory in most cases, but if the BACnet
segment does not have a BBMD set up the controller can act as the BBMD in which case the BDT list must
be set up. BBMDs enable BACnet devices to communicate across IP routers, only one BBMD device is
allowed on each IP subnet. The list should include the BBMD device for each IP subnet containing devices
that are to be communicated with. Only one BBMD device is allowed on each IP subnet The BBMD
functionality will not work with devices that use automatic IP addressing (DHCP), and under such condition
should be left disabled.
To set up the BBMD list:
 Click Disabled (BBMD) to enable BBMD. If there is an Enable button BBMD is enabled.
 Double click an item in the BDT List, or right click an item in the list and click Edit. The BDT Item
 In the Remote BACnet IP Address box enter the IP address of the BBMD device that is being specified.
 In the Remote BACnet Subnet box enter the BACnet subnet of the BBMD device that is being
specified. It is recommended that this is set to 255.255.255.255.
 In the Remote BACnet UDP Port box enter the UDP port used by the BBMD device that is being
specified.
 Click OK.
To remove a device from the BDT list right click it and click Delete. Devices can be edited as described
above.
8. Click OK.
9.4.12 Set up the BACnet Application Network Module
IQ4/BACnet, IQ4NC controller and IQ3/BACnet controllers with firmware v2.30 or greater. The BACnet Application
network module determines the controller's BACnet settings. It needs to be to be set up if the controller is to connect
to a BACnet network. For details of the module see the IQ3 Configuration Reference Manual (TE200768), or the IQ4
Configuration Reference Manual (TE201263).
To set up the BACnet application network module:
2. Right-click the strategy page, point to Device, point to BACnet and click BACnet Application, or on the
Device menu click BACnet Application. The BACnet Application Module dialogue box is displayed.

4. In the Manual Device Instance box click Automatic or Manual to specify whether the controllers address
on then BACnet network is determined manually or automatically. If determined automatically the address
is calculated using the formula below:
(LAN Number*100) + Local node
5. If the address is to be specified manually in the Device Instance box enter the controller's address on the
BACnet network.
6. If the controller is to send an 'I am' message over the BACnet network when it powers up, select the Send I-
Am at Startup check box.
7. IQv3.45 or lower. To maintain BTL compliance select the BTL Compliance Enabled check box.
8. IQ4 v3.50 or greater. If the Change_Of_State_Count and Elapsed_Active_Time properties on the BACnet
AO & BO Objects are to be disabled, select the Disable BO Count & Active Time check box.
Note: If a BTL compliant strategy is required the Disable BO Count & Active Time check box must be
selected.
9. If object name prefixes are not to be added to the object names when viewed from BACnet clear the Object
Name Prefixes check box.
10. IQ4 v3.50 or greater. If BACnet backup/restore is to be enabled select the Backup/Restore check box. A
warning message is displayed, click OK.
11. IQ4 v3.50 or greater. To enable the Cold & Warm Restart service select the Cold & Warm Restart check
box. A warning message is displayed, click OK.
12. IQ4 v3.50 or greater. To allow parameters to be written to over BACnet select the Bacnet Writable
Properties check box.
Caution: Enabling backup and restore, the Cold & Warm Restart service, or BACnet writes presents a
security risk to your data in the controller as well as the controller's running strategy. Only enable these
features if they are absolutely required, and only enable the required features.
13. IQ4 v3.50 or greater. If any of backup and restore, cold & warm start service or device communications
service are to be used specify the password required to authorise their use in the BACnet Services Password
box.
14. Click OK.
Note: For IQ4 v3.50 or greater to maintain BTL compliance follow the guidelines in Create a BTL Compliant to
configure the module’s parameters as necessary.

9.4.13 Set up the BACnet MSTP Network Module
The BACnet MSTP network module determines the MS/TP settings for IQ4NC and IQ3 controllers with BINC
functionality and IQECO controllers. For details of the MSTP network module see the IQ3 Configuration Reference
Manual (TE200768), IQ4 Configuration Reference Manual (TE201263) or the IQECO Configuration Reference
Manual (TE201089).
To set up the BACnet MSTP network module:
1. Display a strategy page for the controller for which the MSTP network module is to be specified.
2. Right-click the strategy page, point to Device point to Network and click BACnet MSTP, or on the Device
menu click BACnet MSTP. The MSTP Network Module dialogue box is displayed.
For IQ4NC and IQ3 controllers with BINC functionality
For IQECO controllers
3. For IQ3 controllers with BINC functionality and IQ4NC controllers. In the Module Label box enter a label
for the module (30-characters).
controller's LAN.
5. For IQ3 controllers with BINC functionality and IQ4NC controllers. In the Manual Network Number box
click Automatic or Manual to specify whether the controller's address on the MSTP network is determined
manually or automatically. If determined automatically the address is set to the number specified by the 'Lan
Number' parameter. If the network number is to be specified manually in the Network Number box enter
the controller's MSTP network number. (range 0 to 65534).
Note: It is strongly recommended that the network number is determined automatically.
6. Enable/disable the module as required by selecting or clearing the Module (Disabled) check box.
7. For IQ3 controllers with BINC functionality and IQ4NC controllers. In the Manual MAC Address box click
Automatic or Manual to specify whether the controller's MAC address on the BACnet MS/TP network is
determined manually or automatically. If determined automatically the MAC address set to '0'. If the
controller's MS/TP MAC address is to be specified manually in the MSTP MAC box enter the controller's
BACnet MS/TP MAC address. (range 0 to 255).
Note: It is strongly recommended that this be left as automatic. Setting to some other MAC address will
compromise system performance.

8. For IQ3 controllers with BINC functionality and IQ4NC controllers. In the MSTP Baud Rate box select the
baud rate on the MS/TP network. 76800 should be selected for best system performance. Baud rates below
38400 are not recommended for large systems, performance problems are likely.
9. For IQ3 v3.0 controllers with BINC functionality, IQ4NC controllers, and IQECO v2.0 or greater. In the
Max Info Frames box enter the maximum address polled to create a network on the MS/TP trunk. It is not
recommended that this parameter is changed from the default. For IQECO controllers the Not Sent check
box must be cleared to allow the parameter to be specified, and included in the strategy file.
10. In the Max Master box enter the maximum number of frames a node can send per rotation of the MS/TP
token. Do not change this from the default value except where expert BACnet system knowledge is available
to analyse system performance. For IQECO controllers the Not Sent check box must be cleared to allow the
parameter to be specified, and included in the strategy file.
11. For IQ3 v3.0 controllers with BINC functionality, IQ4NC controllers, and IQECO v2.0 or greater. In the
Service Class box select the required service class. This should normally be left as 'Unconfirmed' unless
there are communications issues. For IQECO controllers the Not Sent check box must be cleared to allow
the parameter to be specified, and included in the strategy file.
12. For IQ3 controllers with BINC functionality and IQ4NC controllers. In the Alarm Group box enter the
alarm group that is to be used for network alarms generated on the MS/TP network.
13. Click OK.

9.4.14 Set up Sensor Type Modules
Sensor Type modules can be set up in one of two ways:
using a sensor definition
manually
9.4.14.1 Set up Sensor Type Modules Using a Sensor Definition
Sensor type modules need to be set up to define how the sensors scale their inputs. IQSET allows the sensor type
modules to be defined using definitions stored in a library of sensor definitions, as described below. The parameters
can also be defined manually.
If the required sensor definition is not available in the library, definitions can be added to the library for that sensor.
Set up a sensor type module using a sensor from the library:
1. Display a strategy page for the controller for which the sensor type modules are to be defined.
2. Right-click the page and point to Device and click Sensor Types, or on the Device menu click Sensor Types.
3. In the Number box click the sensor type module that is to be defined.
4. In the Sensor Part Number or the Unique Sensor Reference box click the required definition,
5. In the Scaling Range box click the required range. The Filter button can be used to reduce the number of
sensors that can be selected. Click Filter to display the Sensor Type Filter dialogue box, and then click the
appropriate check boxes.
6. Click Apply. The parameters of the selected definition will be applied to the selected sensor type module.
The parameters for that sensor are displayed on the right of the dialogue box. The graph shows the sensors
characteristics.
7. Repeat steps (3) to (6) for each sensor type module that is to be set up.
8. Click Exit.

9.4.14.2 Set up Sensor Type Modules Manually
Sensor type modules need to be set up to define how the sensors scale their inputs. IQSET allows the sensor type
modules to be defined manually, as described below. They can also be defined using definitions stored in a library.
Note: Before setting up the Sensor Type modules in an IQSET project created with version of IQSET earlier than v1.1;
it is necessary to display a strategy page from the controller that is to be edited.
Set up a sensor type module manually:
1. Display a strategy page for the controller for which the sensor type modules are to be defined.
2. Right-click the page and point to Device and click Sensor Types, or on the Device menu click Sensor Types.
3. In the Number box click the sensor type module that is to be defined.
4. In the Sensor Part Number box enter the part number of the sensor.
5. In the Scaling Range box enter the range of the sensor. The drop-down list is empty when a new sensor is
being added to the library.
6. In the Unique Sensor Reference box enter the reference for the sensor. It is recommended that this reference
consist of the part number followed by the range (e.g. PIL/4).
7. Click Edit.
8. In the Scaling box click the scaling type. The Sensor Type dialogue box changes to allow the appropriate
parameters to be specified. For IQ3and IQ4 controllers you must use characterise scaling.
Option Description
This type of scaling must be used on IQ3 and IQ4 controllers. It allows a sensor’s
characteristics to be defined by specifying up to twenty scaling points between which it
Characterise interpolates. This provides higher accuracy than the other scaling types for non-linear
scaling characteristics. It is therefore recommended for use with all non-linear sensors providing
the controller has version 2.1 firmware or greater. It is also used for lookup function
modules.
Linear scaling sensors providing either a voltage or current signal with a linear characteristic between the
top and bottom of the range

Option Description
This type of scaling cannot be used on IQ3 and IQ4 controllers. Can be used instead of
linearise thermistor volts. It should be used for non-Trend sensors where the
resistance/temperature characteristic is known, as it requires entry of ohms against
Linearise
temperature directly from the characteristic. It enables the linearisation points on the
thermistor
temperature scale to be individually chosen so that they can be closer together over a part
ohms
of the characteristic where the gradient is changing rapidly, and further apart where the
gradient changes only gradually. It is not recommended for use with Trend sensors (use
Linearise thermistor volts for these).
Linearise
thermistor volts
thermistor sensors providing a voltage signal that needs to be linearised.
scaling
Linearise volts This type of scaling cannot be used on IQ3 and IQ4 controllers. It should be used for
scaling sensors providing voltage or current signals that need to be linearised.
This type of scaling cannot be used on IQ3 and IQ4 controllers. It is not normally used; it
Log scaling is for sensors providing either a voltage or current signal with a logarithmic characteristic
between the top and bottom of range.
9. Specify the sensor type's parameters by entering the required value for each parameter into the appropriate
box, or clicking the required options, or choosing the required value from a list.
Note: When entering the values in the Input (X) and Output (Y) boxes the value of the input points (X) must
increase, not decrease.
Clicking Refresh will display a graph of the sensor’s characteristics as defined by the current parameters.
This can be used at any point to check how the sensor reading will be scaled.
10. Once the parameters are correctly specified, click Save.
11. Repeat steps (3) to (10) to set up other sensor type modules.
12. Click Exit.
9.4.15 Add a States Category Module
IQ4 v3.50 or greater. States Category modules must be added if multistate values are to be used in the strategy.
Add a states category module:
1. Display a strategy page for the controller to which the module is to be added.
2. Right-click the page and point to Device and click States Categories, or on the Device menu click States
Categories. The States Categories dialogue box is displayed.
3. In the Module Number box click the module that is to be defined.

4. In the Number of States box specify the number of states the module is to define. The required number of
states will be added to the list below. The Edit button will display the States Category Library dialogue
enabling fast access to the set up of the States Category library.
5. In the Library box select the library the text for the states is to obtained from. This will automatically specify
the label and state text based on the selected library.
6. In the Label box enter or select the name for the module.
7. If a library is not providing the text for the sates or the text need to be changed click the State Text column
in the row of the state that is to be defined, and enter the required text for the state.
8. Click OK.
9.4.15.1 Delete a States Category Module
Delete a states category module:
1. Display a strategy page for the controller from which the module is to be deleted.
2. Right-click the page and point to Device and click States Categories, or on the Device menu click States
Categories. The States Categories dialogue box is displayed.
3. In the Module Number box click the module that is to be delete.

4. Click the Clear.
5. Click OK.

9.4.16 Set up an Interface Network Module
If a Wallbus device is to be connected to the IQ4 or it is necessary to add a Type 14 (Wallbus) Network module to the
strategy. For IQ4 /XNC variants that are to communicate with a 3rd Party system via a serial connection it is necessary
to set up a Type 17 (Trend Serial) Network module for each different serial connection that is to be used. For IQ4
/INT variants that are to communicate over MODBUS it is necessary to set up a Type 8 (MODBUS Serial) Network
module for MODBUS serial or Type 19 (MODBUS IP) Network module for MODBUS IP. For /INT variants v4.30
or greater that are to communicate with an M-bus device a Type 15 (M-bus) Network module must be added. IQSET
refers to these modules as Interface Network modules.
To set up an Interface Network module:
1. Display a strategy page for the controller for which the module is to be specified.
2. Right-click the strategy page, point to Interfaces and click Network Module Configuration. The Interface
Network Module dialogue box is displayed.
3. In the Network Type box select the required type of network.
Option Description
/XNC variants only. Adds a Type 17 (Trend Serial) Network module with the 'Mode'
XNCSerial -
parameter set to 'RS232'. For use with IQ4 /XNC variants that are to communicate via an
RS232
RS232 connection.
/XNC variants only. Adds a Type 17 (Trend Serial) Network module with the 'Mode'
XNCSerial -
parameter set to 'RS485'. For use with IQ4 /XNC variants that are to communicate via an
RS485
RS485 connection.
/INT variants only. Adds a Type 8 (MODBUS Serial) Network module'. For use with IQ4
MODBUS
/INT variants that are to communicate using MODBUS via a serial connection (RS232 or
Serial
RS485).
/INT variants only. Adds a Type 19 (MODBUS IP) Network module. For use with IQ4 /INT
MODBUS IP
variants that are to communicate using MODBUS via an IP connection.
/INT variants only v4.30 or greater. Adds a Type 15 (M-bus) Network module. For use with
MBus
IQ4 /INT variants that are to communicate using M-bus.
Adds a Type 14 (Wallbus) Network module, used when connecting a Wallbus device to an
Wall-bus
IQ4 or IQECO.
Note: The RS48, RS232 ports cannot be used for XNC, MS/TP, M-bus, or MODBUS at the same time.
4. In the Module label box enter the label for the module.
5. Configure the module's parameters (/INT variants only).
Modbus IP:
 In the Hostname/IP Address box enter the IP Address or host name of the Modbus device the IQ4 is to
communicate with.
 In the TCP Port box enter the TCP port for the Modbus communications.
 If the module is to be disabled select the Disable box.
Modbus Serial:
 In the Communication Channel box select the port (RS232, RS485, or Not used) connecting the IQ4
to the Modbus system.
 In the Communication Mode box select communication mode used by the Modbus connection.

 In the Baud Rate box select the required baud rate.
 In the Parity box select the required parity (Odd, Even).
 In the Timeout box enter the maximum wait time in ms for a response frame from a Modbus request.
 In the Interframe Pause box enter the pause in ms between frames sent by the controller on the Modbus
Network.
 In the Retires box enter the number of times to attempt a Modbus request before a communication error
is reported.
Mbus:
 In the Communication Channel box select the port (RS232, RS485, or Not used) connecting the IQ4
to the M-bus system.
 In the Communication Mode box select communication mode used by the Modbus connection.
 In the Baud Rate box select the required baud rate.
 In the Timeout box enter the maximum wait time in ms for a response frame from a M-bus request.
 In the Interframe Pause box enter the pause in ms between frames sent by the controller on the M-bus
Network.
 In the Retires box enter the number of times to attempt a M-bus request before a communication error
is reported.
6. Click OK.
To delete an Interface Network module:
3. Select the module that is to be deleted.
4. Click Remove.
5. Click OK.
To edit an Interface Network module:
3. Select the module that is to be edited.
4. Configure the module's parameters as required.
5. Click OK.

9.4.17 Set up a Type 2 (Wallbus) Interface Module
If a Wallbus device is to be connected to an IQ4 or IQECO add a Type 2 (Wallbus) Interface module to the strategy
for each device that is to be connected and configure its inputs and outputs as required.
To set up a Type 2 (Wallbus) Interface module:
2. Right-click the strategy page, point to Interfaces and click Wallbus. A Type 2 (Wallbus) Interface module
is added to the strategy page.
3. Double click the Type 2 (Wallbus) Interface module. The Wallbus Interface Module dialogue box is
displayed.
4. Click the button next to Module State to ensure that the module is enabled.
6. In the Network Module box select n12 - Wallbus.
7. In the Address box enter the devices address on the Wallbus (1 to 15).
8. In the Device Profile box enter a name for the configuration.
9. Specify the number of inputs.
 Select the Inputs tab.
 Click Change next to the Total box. The Change Input Total dialogue box is displayed.
 In the box enter the required number of inputs.

 Click OK. The required number of inputs will be added to the list.
10. Set up the inputs. The inputs link values in the strategy that are to be sent to the PV in the Wallbus device
 Specify which inputs are to appear on the module on the strategy page by selecting the required Display
check boxes.
 Double click the Label column for an input and enter the required label.
 Double click the Units column for an input and enter the required units.
 Double click the Value column for an input and enter the required value.
 Double click the PV Index column for an input and enter the PV Index in the Wallbus device to which
the value is to be written, refer to the device documentation for details.

 Double click the Interval 5, 10, 15.. column for an input and specify the interval at which the input's
value the value is written to the PV in the Wallbus device (5s, 10s, 15s, 20s, 25s, 30s, 35, 40s, 45s, 50s).
 Double click the Sig. Change.. column for an input and specify the amount by which the value of the
input must change before the value is written to the PV in the Wallbus device.
11. Specify the number of outputs.
 Select the Outputs tab.
 In the box enter the required number of outputs.

 Click OK. The required number of outputs will be added to the list.
12. Set up the outputs. The outputs link values that are to be read from the Wallbus to the required PV in the
Wallbus device to the PV in that device.
 Specify which outputs are to appear on the module on the strategy page by selecting the required Display
check boxes.
 Double click the Label column for an output and enter the required label.
 Double click the Units column for an output and enter the required units.
 Double click the Value column for an output and enter the required value.
 Double click the PV Index column for an output and enter the PV Index in the Wallbus device to which
the value is to be written, refer to the device documentation for details.
 Double click the Expiry Time column for an input and specify the time, in seconds, that the value of the
output is held for after the last communication from the Wallbus device.
13. Select either PV Index or Label to specify what is displayed in the module on the strategy page.
14. Click OK.

9.4.18 Set up a Type 3 (Modbus) Interface Module
If a Modbus device is to be connected to an IQ4 /INT variant add a Type 3 (Modbus) Interface module to the strategy
for each device that is to be connected and configure its inputs and outputs as required.
To set up a Type 3 (Modlbus) Interface module:
2. Right-click the strategy page, point to Interfaces and click Modbus. A Type 3 (Modbus) Interface module
is added to the strategy page.
3. Double click the Type 3 (Modbus) Interface module. The Modbus Interface Module dialogue box is
displayed.
6. In the Network Module box select the required Modbus network module to which the module is connected.
7. In the Address box enter the device's address on the Modbus (Serial = 1 to 247, IP = 1 to 255).
9. In the Byte Order box select the order of the bytes in the device.
10. In the Register Addr Mode box select the address mode used by the device.
11. Select either Decimal or Hex option to specify the required entry mode.
12. In the Inputs Base reg Addr box enter the base value to apply to all Inputs Register Addresses.
13. In the Outputs Base reg Addr box enter the base value to apply to all Outputs Register Addresses.
14. Specify the number of inputs.
 Select the Inputs tab.
 In the box enter the required number of inputs.

 Click OK. The required number of inputs will be added to the list.
15. Set up the inputs. The inputs link values in the strategy that are to be sent to the Modbus device to the value
in the Modbus device.
 Specify which inputs are to appear on the module on the strategy page by selecting the required Display
check boxes.

 Double click the Label column for an input and enter the required label.
 Double click the Units column for an input and enter the required units.
 Double click the Value column for an input and enter the required value.
 Double click the Reg Addr column for an input and enter the registry address in the Modbus device to
which the value is to be written, refer to the device documentation for details.
 Double click the Ref. Period column for an input and specify the time in seconds between refreshes. (0
to 1800, 0 = on change only).
 Double click the Sig. Change.. column for an input and specify the amount by which the value of the
input must change before the value is written to the PV in the Wallbus device.
 Double click the Scaling Factor column for an input and specify the power of 10 scaling factor to apply
to the register value to convert it to the required units. (-20 to +20).
 Double click the Data Type column for an input and specify the data type.

17. Set up the outputs. The outputs link values read from the Modbus device to values in the strategy.
check boxes.
 Double click the Reg Addr column for an output and enter the registry address in the Modbus device to
which the value is to be written, refer to the device documentation for details.
 Extended and Extended Base 1 Register Address Modes only - Double click the Register Type column
for an output and select the required register type, refer to the device documentation for details.
 Double click the Ref. Period column for an output and specify the time in seconds between refreshes.
(0 to 1800, 0 = on change only).
 Double click the Scaling Factor column for an output and specify the power of 10 scaling factor to apply
 Double click the Data Type column for an output and specify the data type.
18. Select either Register Addr or Label to specify what is displayed in the module on the strategy page.
19. Click OK.

9.4.19 Set up a Type 4 (M-bus) Interface Module
If a M-bus device is to be connected to an IQ4 /INT variant (v4.30 or greater) add a Type 4 (M-bus) Interface module
to the strategy for each device that is to be connected and configure its outputs as required.
To set up a Type 4 (M-bus) Interface module:
2. Right-click the strategy page, point to Interfaces and click M-Bus. A Type 4 (M-bus) Interface module is
added to the strategy page.
3. Double click the Type 4 (M-bus) Interface module. The M-Bus Interface Module dialogue box is displayed.
6. In the Network Module box select the required M-bus network module to which the module is connected.
7. In the Primary Address box enter the address on the M-bus of the device to be read. (1 to 15)
8. In the Enhanced Sec box enter the enhanced secondary address (serial number) on the M-bus of the device
to be read.
10. In the Refresh Period box enter the time in seconds between read requests (1 to 1800).

12. Set up the outputs. The outputs link values read from the M-bus device to values in the strategy.
check boxes.

 Double click the Data Item Index column for an output and select the type of data, refer to the device
documentation for details.
 Double click the Scaling Factor column for an output and specify the power of 10 scaling factor to apply
13. Select either Data Item Index or Label to specify what is displayed in the module on the strategy page.
14. Click OK.
9.4.20 Configure ADL Support
If the controller has ADL support, it is necessary to set up the following modules:
Autodial module
Modem module
Record module
9.4.20.1 Set up the Autodial Module
It is only necessary to set up Autodial modules for controllers with ADL support.
To set up the autodial module:
1. Display a strategy page for the controller for which the autodial module is to be specified.
2. On the Device menu click Autodial Module. The Autodial Module dialogue box is displayed.
3. In the Telephone Number box enter the telephone number that is to be used to access the controller (max
29-characters).
0 to 9 Dialling characters
ABCD#* Considered as dialling characters on some systems
J Wait for secondary dial tone
K 2 second pause
L Pulse dialling
M Tone dialling
4. In the Auto-dial Pin box enter the PIN used to validate connections using the modem (4-digits).
5. Click OK.
9.4.20.2 Set up the Modem Module
It is only necessary to set up modem modules for controllers with ADL support.
To set up the modem module:
1. Display a strategy page for the controller for which the modem module is to be set up.
2. On the Device menu click Modem Module. The Modem Module dialogue box is displayed.
3. In the Modem Initialise 1 box enter the initialisation string that is sent to the modem whenever it is re-
initialised. This can be up to 24-characters long and is set to 'ATH&F' by default. This should not normally
be changed.

4. In the Modem Initialise 2 box enter the initialisation string that is sent to the modem after the string defined
above. This can be up to 24-characters long and is set to 'ATS0=1' by default. This should not normally be
changed.
5. In the Version Request box enter the string that is sent to the modem to cause a version response. This can
be up to 16-characters long and is set to 'ATI3' by default. This should not normally be changed.
6. Click OK.
9.4.20.3 Set up the Record Module
It is only necessary to set up record modules for controllers with ADL support.
To set up the record module:
1. Display a strategy page for which the record module is to be set up.
2. On the Device menu click Record Module. The Record Module dialogue box is displayed.
3. In the Proxy Port box enter the network address of the modem that is to be used to send alarms.
4. In the LAN box enter the LAN number of the device to which the alarms are to be sent. Range 1 to 119
excluding addresses 2, 3, and 10.
5. In the Address box enter the network address of the device to which the alarms are to be sent. Range 1 to
119 excluding addresses 2, 3, and 10.
6. In the Telephone box enter the telephone number of the device to which the alarms are to be sent (max 29-
characters).
0 to 9 Dialling characters
ABCD#* Considered as dialling characters on some systems
J Wait for secondary dial tone
K 2 second pause
L Pulse dialling
M Tone dialling
7. Click OK.

9.4.21 Configure XNC Support for IQ2 Controllers
If the controller is an IQ2 with XNC support it is necessary to set up the following modules:
Comport Modules
Store Modules
9.4.21.1 Set up Comport Modules
Comport modules are only available on IQ2 controllers with XNC support. They are used on controllers with XNC
support to define the setup of serial ports used to communicate with the 3rd party system and ports used to enable the
TCL part to communicate directly over the Trend network.
To set up the comport modules:
1. Display a strategy page for the controller for which the Comport module is to be specified.
2. On the Device menu click Comports. The Comport Module dialogue box is displayed. This dialogue box
enables both Comport modules to be set up. Comport module 1 is on the left, and Comport module 2 is on
the right. The set up is the same for each.
3. In the Label box enter a label for the module.

4. In the Port Type box click the required port type. The dialogue box will change to grey out the parameters
that do not apply to the selected port type.
5. Specify the Serial port type parameters or Trend LAN port type parameters for each comport module.
For serial ports:
 In the Port number box enter the number of the COM port being used.
 In the Baud Rate box select the baud rate of the port.
 In the Data Bits box enter the required number of data bits for the port. (Range = 7 or 8).
 In the Parity Bits box select the parity that is to be used. (Range = Odd or Even).
 In the Stop Bits box enter the number of stop bits. (Range = 1, or 2).
 In the RX Termination box enter the RX terminator character. (Range 0 to 255).
 In the Timeout box enter the time out in milliseconds. (Range = 0 to 32767).
For Trend LAN ports:
 In the Own box enter the Trend network address of the port. (Range = 1 to 119 excluding addresses 2,
3, and 10).
 In the Dest box enter the network address to which the next message will be sent. (Range = 1 to 119
excluding addresses 2, 3, and 10).
 In the Dest Lan box enter the LAN. (Range = 1 to 119 excluding addresses 2, 3, and 10).
 In the TX Protocol box select the parity that is to be used. (Range = Odd or Even).
 In the Stop Bits box enter the number of stop bits. (Range = 1, or 2).
 In the RX Termination box enter the transmission protocol that is to be used.
6. Click OK.
For more details of the module see the IQ Configuration Reference Manual (90-1533).

9.4.21.2 Set up Store Modules
Store modules are only available on IQ2 controllers with XNC support. They are used to hold strings of information
that can be accessed by the TCL program.
To set up the store modules:
1. Display a strategy page for the controller for which the store module is to be set up. This must be a controller
with XNC support to be defined.
2. On the Device menu click Store Modules. The Store Module dialogue box is displayed.
3. In the Module column click the store module is to be set up. The module number is displayed in the Module
box.
4. In the Label box enter the required text (max. 40-characters).
5. Click Apply.
6. Click OK.
For more details of the module see the IQ Configuration Reference Manual (90-1533).

9.4.22 Set up the XNC Interface Module
If configuring an IQ4 or IQ3 /XNC variant it is necessary to set up the XNC Interface module. The XNC interface
module defines the alarm group module to which runtime alarms are to be sent, the user alarm labels, the initial value
of the stores strings, and the linking of the TCL application’s inputs and outputs to modules in the IQ strategy.
To set up the XNC interface module:
1. Display a strategy page for the device for which the XNC interface module is to be specified.
2. Right-click the strategy page, and point to Interfaces, and click XNC Interface Module. The XNC
Interface Module dialogue box is displayed.
3. Specify the number of inputs, outputs, and stores available by either linking the XNC application file (XNP
file) that is to be linked to the strategy, or specify the required inputs, outputs, and stores manually.
Note: If the XNC application file is not linked now it must be linked before the strategy and TCL code is
downloaded to the controller.
4. If interfacing with 3rd party system via a serial connection select, the Type 17 (Trend Serial) Network module
that is to be used from the Network Module box.
Note: This can be changed by the TCL application if the interface is to change between serial connections.
5. Specify the initial value of each of the stores by double-clicking the appropriate store's string and entering
the required value. Information can be copied and pasted by right-clicking on the label and clicking Copy
Label or Paste Label. Information can be pasted into more than one store by copying the required
information to the clipboard; the information for each store must be on a new line, selecting the required
stores, right-clicking, and clicking Paste. Clicking Select All will select all the values.
6. Specify the initial value of each of the inputs, and outputs by double-clicking on the value and entering the
value. If an XNC application file has been linked the values of the inputs, outputs, and stores can be reset to
those specified in the file by selecting the Overwrite Values check box and clicking Re-load.
7. Specify the labels of each of the inputs, and outputs by double-clicking on the label and entering the new
label. Labels can be copied and pasted by right-clicking on the label and clicking Copy Label or Paste Label.
Labels can be pasted into more than one input, or output by copying the required information to the clipboard,
the information for each input or output must be on a new line, selecting the required input or output, right-
clicking, and clicking Paste. Clicking Select All will select all the labels.
If an XNC application file has been linked the labels of the inputs and outputs can be reset to those specified
by the application file by selecting the Overwrite Labels check box and clicking Re-load.

8. In the Alarm Label boxes 1-6 enter values of the XNC interface module’s user alarm labels. These are the
labels used by TCL’s GENALARM function for the alarm description.
9. Add the knob or switch modules that are to be linked to the TCL application’s inputs to the strategy.
To add knobs or switches:
 Click Add Knobs or Add Switches as required. A dialogue box is displayed asking for the number of
the knob or switch modules that are to be added to the strategy.
 In the Start box enter the required module number. For a range of modules, enter the first module number
that is to be used; subsequent modules will be used for the other inputs in the range.
 In the Total box enter the total number of modules that are being added.
 Click OK. The specified modules linked to the inputs will be added to the strategy page. If the selected
strategy page already contains modules a new strategy page will be created.
10. Add the sensor or digital input modules that are to be linked to the TCL application’s outputs from the
strategy.
To add sensors or digital inputs:
 Click Add Sensors or Add Digins as required. A dialogue box is displayed asking for the number of the
sensor or digital input modules that are to be added to the strategy.
 In the Start box enter the required module number. For a range of modules, enter the first module number
that is to be used; subsequent modules will be used for the other outputs in the range.
 In the Total box enter the total number of modules that are being added.
 Click OK. The specified modules linked to the outputs will be added to the strategy page. If the selected
strategy page already contains modules a new strategy page will be created.
11. Link TCL application’s inputs and outputs to the required modules in the IQ strategy. If required modules
can be linked to the TCL application's inputs and outputs manually.
To link inputs and outputs:
 Click the module that is to be linked in the box underneath Add Switches, or Add Digins.
 Drag it onto the required input or output, and releasing the mouse button.
More than one module can be linked at a time by holding down the CRTL key and clicking on the modules
that are to be linked, and then dragging them onto the first input/output that is to be linked and releasing the
mouse button. The first module in the selection will be linked to the input/output the mouse was positioned
over when the mouse button was released, the other modules will be linked to the modules below that module.
12. Click OK.
9.4.22.1 Link TCL Inputs and Outputs to Modules Manually
The inputs and outputs of a TCL application need to be linked to parameters in the IQ strategy that apply to the TCL
application. This can be done manually by adding the modules and linking them to the TCL application's input/output
connectives as described below, or when setting up the XNC Interface Module.
Linking the inputs and outputs manually enables them to be linked to modules other than sensors, digital inputs, knobs,
and switches. It also enables them to be linked to any module parameter.
To manually link TCL inputs and outputs to IQ strategy:
1. Obtain the TCL application from the developer.
3. Add the module the input or output is to be linked to.
4. Add the connective to the TCL input or output. Connectives to TCL inputs and outputs are referred to in the
Connectives dialogue box with a lowercase ‘t’.
5. Link the module parameter to the connective.
6. Click OK.
9.4.22.2 Link the XNC Application File
To Link the XNC Application File:
1. Obtain the TCL application from the developer.
3. Right-click the strategy page, point to Interfaces, and click XNC Interface Module. The XNC Interface
Module dialogue box is displayed.

4. Click . The Select XNC App File dialogue box is displayed.
5. In the folder list click the XNC application file. To select a file stored in a different location, click the drive,
or folder in the Look in box that contains the file, double-click the folders in the folder list until file is
displayed.
6. Click Open. The TCL application will be loaded and the applications file name added to the XNC App box.
Details of the application’s name, author, and ID are also displayed in the appropriate boxes; these are read
only.
Note: If the number of stores, inputs, or outputs in the XNP file is different to the number specified by IQSET a dialogue
box asking if you want to continue is displayed. Click Yes to continue and update the settings in IQSET with those in
the XNP file or click No to cancel the process.
9.4.22.3 Specify Stores, Inputs and Outputs Manually
The stores, inputs and outputs of a TCL application can be specified manually, without the need for the TCL
application. This enables the IQ strategy for a specific TCL application to be produced before the application has been
completed.
To manually link TCL inputs and outputs to IQ strategy:

2. Right-click the strategy page and point to Device and click XNC Interface Module. The XNC Interface
Module dialogue box is displayed.
3. Click Change next to the Total box for the store, inputs, or outputs. The Change Total dialogue box is
displayed.
4. In the box enter the required number of stores, inputs, or outputs.

5. Click OK.
Note: If stores, inputs, or outputs already exist, if the new number is higher than the number already specified the last
one would be removed, if it were less additional stores, inputs, or outputs will be added.

9.4.23 Add Modules to a Strategy Page
Modules are added to the strategy by adding them to a strategy page.
When configuring an IQ4, IQ3 or IQECO controller only the modules used in the strategy are added to the controller’s
memory. This enables the number of each type of module to be adjusted to suit the requirements of the strategy, so
long as the memory capacity of the controller is not exceeded. The total available capacity in is dependent on the
controller type see the controller’s data sheet for details. IQSET keeps a tally of the memory used and the amount
available to be used. This is indicated in the status bar at the bottom of the page. If the limit is exceeded, then IQSET
will prohibit the creation of further modules.
For IQECO controllers there is also a maximum number of modules allowed in the strategy. IQSET limits the module
count to prevent this limit being exceeded.
When configuring a pre IQ3 controller the number of each type of module is predefined therefore IQSET will limit
the number of each type of module to ensure that the controller’s capacity is not exceeded.
To add a module to a strategy page:
1. Display the strategy page to which the module is to be added.
2. Click the required module type in the appropriate toolbar, or right-click the page where the module is to be
placed, point to the type of module (inputs, functions, logic, other, ic comms, alarms, or drivers) and click
the module. The cursor will change to a hand . E.g. to add a combination logic module right-click the page
where the module is to be placed, and point to Logic and click 1: Combination.
3. If IQSET has been configured to prompt for the module number and sequence step that is to be used for the
type of module being added a dialogue box is displayed. Specify the module number and sequence step in
the appropriate box. If required enter the required module number and sequence step in the appropriate box.
Clicking on will check to see that the module number is valid, and unused. When the information is
correct click OK to add the module.
When adding ic comms data to, data from and global to modules you will be prompted to specify the output
type. When adding OSS modules, you will be prompted to specify the whether heating or cooling is required.
For more details about using ic comms modules see the ‘Configure IC Comms’ section of this manual. The
next module for each module type can be specified in advance.
page. If the module is already in the strategy IQSET will automatically use a connective. If auto edit is
enabled, the Parameters dialogue box for the module will be displayed.
Modules can also be added to a strategy by using the Command Line toolbar or by copying and pasting modules.
Strategy blocks can be used to add pieces of reusable strategy.
9.4.23.1 Use Strategy Blocks
If the project is going to involve the re-use of pieces of standard strategy, the use of strategy blocks will save a great
deal of time. Time spent creating the strategy blocks may save time later in the project. If strategy blocks have been
created, they will already be in the Strategy Library.
When a strategy block is used, the actual modules included are determined by the appropriate pointer (e.g. if a Logic
module is used, and the logic pointer is set to 5 the first logic module used will be logic module 5). The order of the
modules in the sequence table is determined when the strategy block is created. The sequence pointer determines the
sequence step of the first module. When IQSET adds a connective from the strategy block it tries to match the
connective’s label with the label of modules already in the strategy and if one is found it defines the connective as a
link to that module.
The labels of sensors, digital inputs, knobs, switches and drivers can be translated. When the strategy block is used
IQSET's default language is used to determine the language of the labels used. If the block has been translated into
IQSET's default language the translated labels are used otherwise the original labels are used.
If a strategy block that uses connectives is to be used more than once in the same controller it is necessary to change
the label of any modules in the strategy that are linked using connectives. This ensures that a match is not found when
the strategy block is added next time. If this is not done IQSET will make the link to the module that is already in the
strategy not the one in the strategy block.
It is possible to use an entire strategy block in a strategy, or to use individual pages from the strategy block. When an
entire strategy block is used IQSET will automatically add the pages necessary for the modules. If an individual page
is used the strategy block modules are added to the existing page.

Note: Any links between pages are changed to undefined connectives. After the strategy block has been used, define
the destination of any undefined connectives. If a module with a label that matches with the label of the connective
the connective, will be defined to use that module.
To use a strategy block :
1. Check that the next module numbers that are to be used are correct by viewing the Next Module List, if not
change them.
2. Display the strategy page for the controller to which the strategy block page is to be added. If adding an
individual page from a strategy block you should select the page to which the modules are to be added.
3. Either:
 Display the Strategy Library.
 If required filter the library - click too display the Filter dialogue box, select the required options and
click OK.
Or:
 If the Search Library is not displayed, display the Strategy Library, and click .

 Enter the keywords that are to be matched in the box, or select them.
The List/Heatmap button toggles the keyword display between a list of heatmap.
toggles the display of the block description.

4. Add the strategy block.
 To use the entire strategy block drag it on to the strategy page and release the mouse button.
 Strategy Library only - To use a single page of a strategy block, click the required page in the strategy
block and drag it onto the page and release the mouse button.
- IQ4 strategy block

- IQ3 strategy block
- Pre IQ3 strategy block
- IQECO strategy block
5. The Strategy Block Questions and Answers dialogue box may be displayed.
 Enter the answer to the questions in the appropriate box.

The result of the text replacement for the selected question will be shown at the bottom of the dialogue
box. Items that the answer will cause to be truncated will be indicated in red text, this enables you to
adjust the answers to the question appropriately.
 Click OK.
Note: Clicking Preview will display all items in the that contain placeholder text.

6. The Strategy Block Settings dialogue box may be displayed if the module numbers of the modules in the
strategy block can be changed. If it is displayed goto (6), if not goto (10).
7. Check the module availability. The dialogue box lists the number of modules used by the strategy block, or
part of the strategy block that is being used; it also lists the number of available modules in the controller. If
there are not enough available modules the number of available modules will be in red, if there are enough it
will be in green. If this happens you should click Cancel and adjust the strategy so that the strategy block
will fit. In the case of IQ3 controllers if there are not enough I/O modules clicking I/O Setup will enable
additional I/O modules to be added. The list of modules can be sorted by module by clicking will sort the
modules by module type, and clicking will sort the list by module label.
8. Check the modules being added by clicking next to the required module.
 To change the module number, click , click the required module from the list in the dialogue box,
and click OK.
 To change the I/O module number, click , click the required I/O module from the list in the dialogue
box, and click OK.
 To change the channel number, click , click the required channel from the list in the dialogue box,
and click OK.
9. If the module parameters from the strategy block are to override the parameters of any modules that already
exist in the strategy select the Select/Override Module check box.
10. Click OK.
11. IQSET will now add the individual modules for the strategy block. Each time IQSET attempts to add a
module of a type for which IQSET has been configured to prompt for the module number and sequence step
a dialogue box is displayed. If required enter the required module number and sequence step in the
appropriate box. Clicking on will check to see that the module number is valid, and unused. When the
information is correct click OK to add the module.
If the Select/Override Module check box was selected when IQSET attempts to add a module that is already
in the strategy the Strategy Block Warning dialogue box is displayed. Click Yes to override the parameters
of the module in the strategy with those from the module in the strategy block or No to keep the parameters
of the module in the strategy.

9.4.24 Move Modules
IQSET allows either a single module, or a group of modules to be moved, so that the strategy is displayed in a way
that is easy to follow. The co-ordinates of the top left corner of the selected module are indicated in the status bar. If
more than one module is selected the co-ordinates are those of the top left corner of the current module. This can be
used to position modules precisely on the page.
Note: When modules are moved, the links between the modules are automatically routed to avoid other modules, and
links.
To move an individual module:
1. Display the strategy page containing the module to be moved.
2. Drag the module to its new location, and release the mouse button.
To move a group of modules:
1. Display the strategy page that contains the module to be moved.
2. Select the modules that are to be moved.
3. Drag the modules to their new location, and release the mouse button.
TIP: Hold the shift button while moving a module or modules to restrict the movement to horizontal or vertical.
To align modules:
1. Display the strategy page that contains the modules to be aligned.
2. Select the modules that are to be aligned.
3. Right-click any of the selected modules, and click Align Left Edge, or Align Top Edge.
9.4.25 Link the Modules
Modules must be linked together so that the information flows through the strategy correctly. IQSET uses its
knowledge of modules to prevent mistakes such as connecting a digital value to a point requiring an analogue value.
Links to modules on the same strategy page are very easy to create as explained below.
Connectives can be used to link to modules on other strategy pages. Undefined connectives allow links to be made to
modules that have not yet been put in the strategy, or links to be made to particular nodes. If the strategy is using ic
comms, it is possible to show that a module is linked to an ic comms module in another controller by linking to a
dummy ic comms module. These procedures are explained in the next few sections of this manual.
Alarm group modules can only be linked to the ‘G’ parameter of alarm route modules. They can be linked to as many
alarm route modules as required. The link between alarm route modules and alarm destination modules must be made
by dragging the link from the (input) of the alarm destination module to the ‘D’ parameter of the alarm route
module. An alarm route module can be linked to as many alarm destinations as required. Alarm group module zero
cannot be placed on the page for a link to be made; therefore the ‘G’ parameter of the alarm route module must be set
to ‘0’. ‘0’ is the default value when the module is first placed on the page, therefore ‘G’ can be left as the default, or
an existing link deleted to return ‘G’ to ‘0’.
To link the modules:
1. Display the strategy page containing the modules that are to be linked together.
2. Move the move over the parameter that is to be the start point of the link. The pointer will change to a
when it is moved over a parameter that can be linked.
3. Click on the parameter that is to be the start point of the link (normally the output of a module), and hold the
mouse button down.
4. Drag the mouse to the parameter that is to be the end-point of the link (normally the input to a module). If
the parameters can be linked the pointer will change to . If the parameter is not a suitable type to be linked
to the start point of the link the pointer will change to .
5. Release the mouse button. The link will be drawn between the modules, and the two module parameters
linked together in strategy. Links made between the outputs of two modules are drawn as dotted lines. The
link is automatically routed around the other modules and links on the page.
Note: When the output of an Interface module is linked to a display module (Sensor, Knob and Switch the label and
units of the Interface module's output are passed to the display module. Editing the label or unit in the display module
will not affect the Interface module.
9.4.25.1 Link Modules on Different Pages
Modules on different strategy pages can be linked using connectives.
To link to a module on another page:
1. Add a connective to the module that is to be linked to onto the strategy page.

2. Click the connective.
3. Drag the mouse to the parameter that is to be linked to the connective. If the parameter can be linked the
pointer will change to . If the parameter is not a suitable type to be linked the pointer will change to .
Note: The link is automatically routed around the other modules and links on the page.
If required, 'To connectives' can be used to indicate the other end of this link. However, 'To connectives' do not actually
make the connection; they just make the strategy easier to follow.
9.4.25.2 Link to a Module not in the Strategy
Links to modules not currently in the strategy are made using undefined connectives.
To link to a module not in the strategy:
1. Place an undefined connective onto the strategy page.
2. Click the undefined connective, hold the mouse button down, and drag the mouse to the parameter that is to
be linked to the undefined connective. If the parameter can be linked the pointer will change to . If the
parameter is not a suitable type to be linked the pointer will change to .
When the destination for the undefined connective is available, it should be defined - see 'Define an Undefined
Connective’s Destination'.
9.4.25.3 Link to a Node
For pre IQ3 controllers, links can be made to specific nodes in the strategy using undefined connectives. This enables
links to be made to nodes whose value is fixed, or to alarm bits.
To link to a node with a fixed value:
1. Place an undefined connective to the required node onto the strategy page.
2. Click the undefined connective, hold the mouse button down, and drag the mouse to the parameter to which
it is to be linked. If the parameter can be linked the pointer will change to . If the parameter is not a
suitable type to be linked the pointer will change to .
9.4.25.4 Link to Alarm Status Information
For IQ3 and IQ4 controllers the statuses of the module’s alarms are available as outputs from the module and can be
linked to in the normal way. If required a connective to the alarm status information can be added.
9.4.25.5 Link to a Specific Value
For IQ3, IQ4 and IQECO controllers, links can be made to a specific value by using an analogue node module.
To link to a specific value:
1. Add an analogue node module to the strategy page.
2 Double-click the module that has just been added. The Analogue Module Parameters dialogue box is
displayed.

2. In the Label box to enter a label for the node.
3. In the Value box enter the required value of the node.
4. Click OK.
5. Click the output (D) of the module, and drag the mouse to link it to the required place in the strategy. If the
parameter can be linked the pointer will change to . If the parameter is not a suitable type to be linked the
pointer will change to .
9.4.25.6 Link to an IC Comms Module in Another Controller
If the strategy is using ic comms, it is possible to show that a module is linked to an ic comms module in another
controller by linking it to a dummy ic comms module.
Note: Linking to a dummy ic comms module does not set up the ic comms module.
To link a module to a dummy IC comms module:
1. Display the strategy page containing the module that is to be linked to the dummy ic comms module.
2. Click , or right-click anywhere on the page, and point to Draw and click Dummy ICComm from the
menu that is displayed. The pointer changes to a .

3. Drag the pointer to the required position of the dummy ic comms module (next to the input of the module
parameter it is linked to), and click the mouse button.
9.4.25.7 Link to System Information
If required links to various pieces of system information such as time, timing pulses, day of year, month of year etc.
can be made connectives that are automatically created when the controller is added.
To link to system information:
1. Add a Connective to the piece of system information that is to be linked to onto the strategy page.
2. Click the connective.
3. Drag the mouse to the parameter that is to be linked to the connective. If the parameter can be linked the
pointer will change to . If the parameter is not a suitable type to be linked the pointer will change to .
9.4.25.8 Manually Route a Link
IQSET automatically routes links between modules to avoid other modules, and links. Sometimes however, it may be
necessary to route a link manually.
To manually route a link:
1. Display the strategy page that contains the link.
2. Right-click the link, and click Edit Link. The pointer changes to .
3. Drag the link along the route that is required. To change direction, click the left mouse button (a point will
be added to the link), and drag the link in the new direction.
4. Once the link has been routed as required, click the right mouse button.

9.4.26 Set up the Alarm Handling Strategy
For IQ4, IQ3 controllers, IQECO controllers with version 2.0 or greater firmware and pre3 IQ controllers with version
3.0 firmware or greater it is possible to set up strategy to handle alarms - see Configure Alarm Handling Strategy.
This provides the facility to send different alarms to different destinations, or to determine when the alarms are sent.
It also enables alarms to be sent to another destination if the preferred destination is not available. If a strategy is not
defined for alarm handling, all alarms will be sent to the alarm address defined in the address module.
IQ4/BACnet and IQ3/BACnet controllers can send alarms over a BACnet network to BACnet devices. IQSET enables
BACnet compatible alarm handling strategy to be easily created. The strategy created by IQSET conforms to BACnet
standard BIBB AE-N-I-B.
For IQ4s with v3.40 or greater firmware the BACnet Alarm Destination module has additional parameters that enable
compliant strategy to be created using Alarm Route, Alarm Group, and BACnet Alarm Destination modules - see
Configure Alarm Handling Strategy.
To send alarms to BACnet devices in IQ4 earlier than v3.40 and IQ3/BACnet controllers) see 'Configure BACnet
Compatible Alarm Handling Strategy for IQ3 and pre v3.40 IQ4'.
To configure alarm handling for IQ1x and pre-version v3.0 IQ2 controllers see 'Configure Alarm Handling for IQ1x
and pre-version v3.0 IQ2 Controllers'.
9.4.26.1 Configure Alarm Handling Strategy
To configure alarm handling strategy:
1. Add a strategy page.
Note: This is not necessary but it is recommended so that the alarm handling strategy is kept separate to the
control strategy.
2. Click on the Alarms toolbar, or right-click the page where the module is to be placed, point to Alarms,
and click Group to add an alarm group module for each required grouping of alarms.
and click Route to add an Alarm Route module for each group.
and click Trend Destination or BACnet Destination to add an Alarm Destination module for each device
to which alarms are to be sent.
Note: Do not add a BACnet Alarm Destination module as described above for pre IQ4 v3.40 controllers.
Tip: To quickly add an Alarm Group module, Alarm Route module and Alarm Destination module linked
together right click the page and select Alarms>Default or Alarm Block Alarms>BACnet Alarm Block.
5. Edit the module's configuration parameters. In the case of an alarm destination module, the node for the
destination failed status can be changed.
Note: If sending alarms to a 963 that has not learned the site it is recommended that the message format of
the alarm destination modules be set to 'Text'.
6. Add any other modules that are to provide inputs to the alarm route or alarm destination modules.
7. Link the modules together as required. Alarm Group modules can only be linked to the 'G' parameter of alarm
route modules. They can be linked to as many alarm route modules as required. The link between alarm route
modules and alarm destination modules must be made by dragging the link from the of the alarm
destination module to the ‘D’ parameter of the alarm route module. An alarm route module can be linked to
as many alarm destination modules as required.
Note: Alarm Group module zero cannot be placed on the page for a link to be made; therefore, the G
parameter of the alarm route module must be set to 0. 0 is the default value when the module is first placed
on the page, therefore, G can be left as the default, or an existing link deleted to return G to 0.
8. Enable/disable the required alarm.
9. Set up the alarm handling groups.

9.4.26.2 Configure BACnet Compatible Alarm Handling Strategy for IQ3 and pre v3.40 IQ4 Controllers
For IQ3 and pre v3.40 IQ4's a BACnet alarm block must be used to add the necessary facilities to ensure compliance.
To configure BACnet compatible alarm handling strategy for IQ3 and pre v3.40 firmware:
1. Add a strategy page.
Note: This is not necessary but it is recommended so that the alarm handling strategy is kept separate to the
control strategy.
2. Click , or right click on the strategy page, and point to Alarms, and click BACnet Alarm Block. The
BACnet Alarm Configuration dialogue box is displayed.
3. Select the Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, or Sunday check boxes to specify
the day's alarms are to be sent to the destination.
4. In the Start boxes enter the start of the period during which alarms are to be sent to the destination.
5. In the End boxes enter the end of the period during which alarms are to be sent to the destination.
6. If an acknowledgement of the alarm is expected select the Use confirmed message delivery check box.
When selected, the controller will expect an acknowledgement of the alarm, and will continue to send the
alarm until one is received, or it determines that a failure has occurred. When not selected, the controller will
send the alarm once and will not expect an acknowledgement. In this case the failed bit is never set as the
controller has no way of knowing is the alarm transmission was successful.
7. If alarms are to be sent when the value returns to the normal range, select the To-Normal check box.
8. If alarms are to be sent when the value changes to one in the fault range select, the To-Fault check box.
9. If alarms are to be sent when the value changes to one that is not in the normal range, select the To-
OffNormal check box.
10. Click OK. The BACnet alarm block is added to the strategy page.
Note: It is possible to make modifications to the strategy created by the BACnet alarm block; however,
changes may invalidate the BACnet compliance. If such changes are made IQSET will warn you when the
strategy file is created and give you the option to continue. See the 'Create a BTL Compliant Strategy' section
of this manual for more details.

11. Double-click the BACnet alarm destination module, or connective, or right-click it, and click Edit
Parameters. The BACnet Alarm Destination dialogue box is displayed.
12. In the Details box enter details about the module.

13. In the Label box enter a label for the module (max 30-characters).
14. In the Hold priority box enter the priority level below which alarms are held. If an alarm is received above
this level it, and all alarms will be sent. The destination will stay open to low priority alarm for 5 seconds
after the last alarm is sent. (range = 0 to 255).
Note: Alarm priority may come from the output of another module. If this is the case link it to the required
module output.
15. In the Interval box specify the time in minutes between attempts to send the message. (range = 0 to 32767).
16. Select or clear the Inhibit Clear check box to specify whether the destination will send clear alarms.
17. In the Process ID box enter the process ID that is to be included in the alarm message. This is an integer that
can be used in alarm messages to identify the alarm and enable the device receiving the alarm to process it
in a specific way, e.g. an ID could be used to identify all HVAC alarms.
18. Specify the device to which the alarms are to be sent. It is recommended that the device instance is used, and
if the device to which alarms are being sent uses automatic IP addressing the device instance must be used.
For devices that do not support device instance addressing the BACnet address is used. However, this is not
suitable when automatic IP addressing is being used.
Using the Device Instance:
 In the Device Instance box enter the device instance of the BACnet device to which the alarms are to
be sent. If set to 0 the Network Number and MAC Address parameters are used to address the BACnet
device. (Range 0 to 4194393).
Using the BACnet Address:
 In the Device Instance box enter 0.
 In the Network Number box enter the network number of the BACnet device to which the alarms are
to be sent. (Range 0 to 65534).
 In the MAC Address box enter the MAC address of the BACnet device to which the alarms are to be
sent.
The device instance, network number and MAC address parameters of the BACnet device to which alarms
are to be sent can be specified by dragging a BACnet device from the System View or an NTD from the
Device View on to the required BACnet alarm destination module.
19. Click OK.
20. Enable/disable the required alarms.
21. Set up the alarm handling groups to add the alarms that are to be sent to the BACnet.

9.4.26.3 Configure Alarm Handling for IQ1x and pre-version v3.0 IQ2 Controllers
For IQ1 and pre-v3.0 IQ2 controllers, all alarms will be sent to the alarm address defined in the Address module.
To set up the alarm handling for IQ1 and pre-version 3.0 IQ2 controllers:
1. Display a strategy page for the controller for which the alarm handling strategy is to be specified.
2. On the Device menu click Address Module. This displays the IQ Address Module dialogue box.
3. In the Alarm Address box enter the network address of the device to which alarms are to be sent. Range 1,
4 to 119 excluding 10. If set to 0, alarms are not sent. If set to 2, alarms are sent to a device that is directly
connected to the controller.
4. In the Remote Lan box enter the LAN number of the device to which alarms are to be sent. Range 1, 4 to
119 excluding 10. 0 specifies the local LAN.
5. Click OK.
6. Enable/disable the required alarms.

9.4.26.4 Enable/Disable Alarms
Each item alarm in an IQ controller can be individually enabled/disabled in the strategy. IQSET allows alarms to be
enabled from either the Parameters box for the individual module, or from the Alarm Grouping dialogue box.
Note: For pre IQ3 controllers with pre-version 3.0 firmware, the alarms can only be enabled/disabled from the
Properties box of the module.
To enable/disable an alarm from the module’s properties box:
1. Display the strategy page that contains the module for which the configuration parameters are to be changed.
2. Double-click the module, or connective, or right-click and click Edit Parameters. The Parameters dialogue
box for the module is displayed.
3. Click select or clear the Enable check box for the alarm that is to be enabled/disabled.
4. Click OK.
To enable/disable an alarm from the Alarm Grouping dialogue box:
1. Display a strategy page for the controller for which alarms are to be enabled/disabled as described in the ‘Go
to a Strategy Page’ section of this manual.
2. Click . The Alarm Grouping dialogue box is displayed.
3. In one of the lists at the top of the dialogue box click the alarm group module containing the alarms that are
to be enabled/disabled.
4. Click the alarms that are to be enabled/disabled. The selected alarms will be highlighted. More than one
alarm can be selected by dragging the mouse over the required alarms, and then releasing the mouse button,
or by holding down the CTRL key, and clicking the required alarms. A range of alarms can be selected by
holding down the SHIFT key, and then clicking the first and last alarm in the range. Clicking Select All will
select all the alarms in the group displayed above. If required, the alarms displayed can be filtered to show
types of alarms by clicking the appropriate button in the Filter area.
5. Right-click one of the selected alarms and click Enable Alarms or Disable Alarms.
6. Repeat steps (3) to (5) until the alarms have been enabled/disabled as required.
7. Click OK.

9.4.26.5 Set up the Alarm Handling Groups
For IQ4 and IQ3 controllers, IQECO controllers with version 2.0 firmware or greater or pre IQ3 controllers with
version 3.0 firmware or greater, alarm handling groups can be set up to group together alarms that are to be handled
in the same way. The way in which each group of alarms is handled must be first specified.
To set up the alarm handling groups:
2. Display a strategy page for the controller for which the alarm handling groups are to be set up.
3. Click . The Alarm Grouping dialogue box is displayed.
4. From the lists at the top of the dialogue box the click the 2 alarm group modules between which the alarms
are to be moved.
When initially setting up the alarm handling groups, all the alarms will be assigned to default alarm group
module (g1 for IQ3 and IQECO controllers, and g0 for pre IQ3 controllers). Therefore, initially one of the
modules selected above should be the default alarm group module.
5. Click the alarm(s) that are to be moved into a different group. The selected alarms will be highlighted. More
than one alarm can be selected by dragging the mouse over the required alarms, and then releasing the mouse
button, or by holding down the CTRL key, and clicking the required alarms. A range of alarms can be selected
by holding down the SHIFT key, and then clicking the first and last alarm in the range. Clicking Select All
will select all the alarms in the group displayed above. If required, the alarms displayed can be filtered to
show specific types of alarms by clicking the appropriate button in the Filter area.
6. Click or to move the selected alarms into the required group.

7. Repeat steps (4) to (6) until the alarm groups are set up correctly.
8. Click OK.
Note: Alarms can be added to groups when editing the module’s parameters.

9.4.27 Add an I/O Module
If additional I/O modules are to be used, they must be added to the strategy so that the input/output modules can be
connected to them.
To add an I/O module:
1. Display a strategy page for the controller to which the I/O modules are to be added.
2. Right-click the page and point to Device and click I/O Setup on the menu that is displayed, or on the Device
menu click I/O Setup. The I/O Setup dialogue box is displayed.
3. Click Add. The I/O Module Setup dialogue box is displayed the parameters available in this dialogue box
depend on the controller type.
4. Specify the I/O module.

 In the Mod ID box enter the module ID. This specifies the id of the I/O module. This must match the
module's CAN address.
 In the Module Type box click the type of I/O module.
 In the Label box enter a label for the module.
 Click OK to return to the I/O Setup dialogue box.
5. Click Exit.
9.4.27.1 Delete an I/O Module
To delete an I/O module:
1. Display a strategy page for the controller from which the I/O modules are to be deleted.
2. Right-click the page and point to Device and click I/O Setup, or on the Device menu click I/O Setup. The
I/O Setup dialogue box is displayed.
3. Click the I/O module that is to be deleted, to highlight it.
4. Click Remove.
5. A dialogue box is displayed asking for confirmation of the deletion. Click Yes.
6. Click Exit.
9.4.27.2 Edit an I/O Module
To edit an I/O module:
1. Display a strategy page for the controller containing the I/O module that is to be edited.
3. Click the I/O module that is to be changed, to highlight it.
4. Click Edit. The I/O Module Setup dialogue box is displayed.
5. Edit the module as required.

6. Click OK to return to the I/O Setup dialogue box.
7. Click Exit.

9.4.28 Set up a Controller for Use with an External Display
9.4.28.1 Set up a Controller for Use with a Wallbus Display
If an IQECO controller v2.0 or greater is to be connected to Trend Wallbus display the controller's strategy must be
configured appropriately.
To set up a controller for use with a Wallbus display:
1. Add a Type 14 (Wallbus) Network module to the strategy to enable Wallbus communications
2. Add a Type 2 (Wallbus) Interface module to the strategy for the display that is to be connected. The module's
inputs and outputs must be connected to the modules that they are to read values from, or write values to,
and each input and output must be connected to the appropriate Process Variable (PV) in the Wallbus device.
Refer to the Wallbus device's data sheet for details of the values that are available and the PVs used.
For details of an individual display's compatibility see the display's data sheet. Strategy blocks for each of the
supported Trend Wallbus devices are provided in IQSET to facilitate connection of those displays.
For IQECO v2.0 to v2.23 a different configuration is required.
In order for values in the controller to be sent to the display from the strategy the display device (I/O module 2) must
be added to the strategy, and the strategy configured to make the required values available in specific modules which
are read by the display, and if appropriate written to. For details of the values that can be shared between the controller
and the display and the required location of values in the controller see the Wallbus display's documentation.
If values from the display are to be read by the controller the display device (I/O module 2) must be added to the
strategy and the strategy configured to link the input channel of an external sensor to the appropriate output channel
on the display. For details of the values that can be read from the display see the display's documentation.

9.4.29 Assign I/O Channels
For IQ3 and IQ4 controllers the actual physical piece of hardware from which external sensors, and external digital
inputs obtain their inputs, and where drivers send their outputs to must be specified. This can be done in two ways:
using the I/O Setup dialogue box
by editing the modules
For IQECO v2.0 to IQECO v2.23 controllers if a value from a display is to be read into the strategy of an
IQECO controller the output from the display must be assigned to the input of the required sensor module.
This is done by editing the modules.
9.4.29.1 Assign I/O Channels Using the I/O Setup Dialogue Box
To assign I/O channels using the I/O Setup dialogue box:
1. Display a strategy page for the controller for which the I/O modules are to be setup.
3. In the I/O Module Setup box click the I/O module to which modules are to be assigned. If the required I/O
module is not available, it should be added.
4. In the I/O Assignment box click the module(s) that are to be assigned to the I/O module. To select a range
of modules, hold down the SHIFT key, and click the first and last module in the range. To select more than
one module, hold down the CTRL key, and click the required modules. Clicking Sensor, Digin, or Driver
will restrict the type of modules displayed in the I/O Assignment box. To restrict the display to modules that
have not been assigned to an I/O module click Not Set. To display the antiphase channel for a driver, select
the Show Antiphase check box. The list can be sorted by clicking on the top of each column.
5. Click Assign (IQ3/4). The selected modules will automatically be assigned to the I/O module using the next
spare I/O channels.
To assign a specific I/O channel to an input/output the I/O channel for the sensor, digital input or driver must
be specified by editing the module as described in the 'Assign I/O Channels By Editing the Modules' section
of this manual.

6. Click Exit.
9.4.29.2 Assign I/O Channels by Editing the Modules
To assign the I/O modules by editing the modules:
1. Display a strategy page for the controller for which the I/O channels are to be assigned.
2. Double-click the sensor or driver that is to be assigned to an I/O module to display the Parameters dialogue
box.
3. In the I/O Module Setup box click the I/O module to which the module is to be assigned.
4. In the I/O Channel box click the I/O channel for the module.
5. Click OK.
Note: It is necessary to add the required I/O modules before setting them up.
9.4.29.3 Unassign I/O Channels
To unassign I/O channels:
1. Display a strategy page for the controller for which the I/O channels are to be unassigned.
3. In the I/O Assignment box click the module inputs/outputs that are to be unassigned to the I/O module. To
select a range hold down the SHIFT key, and click the first and last item in the range. To select more than
one hold down the CTRL key, and click the required modules.
Clicking Sensor, Digin, or Driver will restrict the type of modules displayed in the I/O Assignment box.
To display the antiphase channel for a driver, select the Show Antiphase check box. The list can be sorted
by clicking on the top of each column.
4. Click Unassign.
5. Click Exit.

9.4.30 Edit Modules
9.4.30.1 Change a Module's Configuration Parameters
When a module is added to a strategy page the configuration parameters are set to the default values. It is therefore
necessary to set them up as required.
Note: If auto edit is enabled, the dialogue box that enables the configuration parameters to be defined is automatically
displayed.
To change a module’s configuration parameters:
1. Display the strategy page that contains the module or connective to the module for which the configuration
parameters are to be changed.
2. Double-click the module, or connective, or right-click it, and click Edit Parameters, or enter the module
type and number in the Command Line toolbar in the format <Module Type><Module Number> and click
. The Parameters dialogue box for the module is displayed.
3. Edit the module’s parameters as required. , , and enable the display attributes to be specified. Clicking
will check all the check boxes. Clicking will clear all the check boxes, and clicking will return the
display setting to the current defaults.
Note: Clicking will set the default display options for the module to the ones currently selected.
4. Once all the parameters have been set up correctly click OK.
Note: Performing this action on an undefined connective enables it to be defined.
The values of a group of parameters in the strategy to be set using group edit.

9.4.30.2 Change Multiple Parameters
The values of a selected group of parameters in the strategy to be set to a specific value.
To change multiple parameters:
1. Display a strategy page for the strategy that contains the parameters that are to be changed.
2. On the Tools menu click Group Parameter Edit. The Group Edit dialogue box is displayed.
3. In the Module Type box select the type of module that contains the parameter that is to be changed.
4. In the Parameter box select the parameter that is to be changed. The list only includes parameters common
to the selected module types.
5. If required the list of parameters can be filtered by value by entering the required value in the Filter box and
clicking on the =, >, or < buttons. C clears the filter. The parameter list now contains all the selected
parameters.
Button Description
Only parameters with a value equal to the value in the Filter box are displayed in the Parameters
=
list.
Only parameters with a value greater than the value in the Filter box are displayed in the
>
Parameters list.
Only parameters with a value greater than the value in the Filter box are displayed in the
<
Parameters list.
6. In the Parameters list click on the parameters that are to be changed. To select all parameters click Select
All, to deselect all parameter click Deselect All. To select more than one parameter hold down the CTRL
key and click the required parameters.
7. Once the required parameters have been selected enter the new value in the New Value box.
8. Click Apply New Value.
9. Click Close to close the dialogue box.
Group parameter edit can also be used live edit and live adjust mode in which case the values are sent straight to the
controller.

9.4.30.3 Change a Module's Destination
For pre IQ3 controllers IQSET automatically uses the standard values for the destination of each module. If this is not
suitable, a different destination can be specified. It is recommended that, as far as is possible, the values assigned by
IQSET be used.
Note: The destination of some modules (e.g. sensors) cannot be changed. If this is the case, the option will not be
available.
To change the destination (output) of a module:
1. Display the strategy page that contains the module or connective to the module for which the destination is
to be changed.
2. Right-click the module and click Change Destination. If the module has more than one output, a dialogue
box will be displayed asking which output is to be changed, click the required one, and click OK. This
displays the Analogue Node Array dialogue box for modules with an analogue destination, and the Digital
Node Array dialogue box for modules with a digital destination.
3. Click the required node or bit. If necessary, use the scroll bars to locate the required one. Its number, type,
status, and associated alarm bits are displayed in the dialogue box. The number specifies the node number,
the type specifies what the node is generally used for, the status specifies what is currently writing to the
module, and the associated alarm bits indicate alarm bits that are associated with the selected node. Icons
next to these parameters indicate this graphically.
Type
Convention. This node is normally used by the strategy for a specific purpose (e.g. storing
0). It can be used providing it is not required for its normal use.
Fixed system node. This module is always written to by a module in the strategy.
Unused
Free
Read only. This node is used for a special purpose (e.g. time) by the controller. Its value
can be read by the strategy, but not changed.
System defaults (e.g. alarm enable bits) can be used with care.
Status
Free to be used.
Used as a destination. Can be used again with care.
Associated
Alarm Bits
There are no alarm bits associated with the selected node
Free
Used as an alarm bit by the specified module.
4. Once the correct node has been selected, click OK.

9.4.30.4 Change a Driver's Output Channel
For pre IQ3 controllers it is possible to change both the output and antiphase channels of a driver (L and A).
To change a driver’s output channel:
1. Display the strategy page that contains the driver or connective to the required driver for which the output
channel is to be changed.
2. Right-click the driver, and click Change Channel. The Select Output dialogue box is displayed.
3. Click Channel, or Antiphase to specify whether the output channel or antiphase channel is to be changed.
4. Click OK. The Channel Output dialogue box is displayed.
5. Click the required channel. If necessary, use the scroll bars to locate the channel. Its number, type, and status
are displayed on the right of the dialogue box. The number specifies the channel number, the type specifies
whether it is analogue, digital, or internal, and the status specifies which driver is currently using the module.
Icons next to these parameters indicate this graphically.
Type
Analogue - can only be used for drivers with analogue outputs.
Digital Output - can only be used for drivers with digital outputs.
Universal output - can be used for drivers with either analogue, or digital outputs, providing the
hardware is set up accordingly.
Status
Free to be used
Used as a destination - Do not use again.
6. Click OK.

9.4.31 Set up the Sequence Table
Once the strategy has been defined it is necessary to check the sequence table to ensure that the strategy is executed
in the correct order. IQSET enables you to add modules to and remove modules from the sequence table as required,
or change a modules sequence step. To help with this process, IQSET provides the ability to insert a gap in the
sequence table to enable modules to be inserted in that position, or to move a module to a particular sequence step.
IQSET indicates modules that are not in the sequence table by highlighting the sequence step part of the module on
the strategy in orange for IQ3, IQ4 and in red for pre IQ3 and IQECO controllers.
Note: There are some module types which cannot be placed in the sequence table.
For pre IQ3 and IQECO controllers all sequenceable modules must have a sequence step for the strategy to operate
correctly. For IQ3 and IQ4 controllers not all sequenceable modules need to have a sequence step as unsequenced
modules become event driven - see 'Set up Event Driven Strategy'.
9.4.31.1 Add Modules to the Sequence Table
Although when a module is placed in the strategy its position in the sequence table is specified, it may be necessary
to add modules that do not normally appear in the sequence table (such as digital inputs for fast sequencing) into the
sequence table.
To add a module to the sequence table:
1. Display the strategy page containing the module that is to be added to the sequence table.
2. Right-click the module, and click Sequence Step. The Sequence Step dialogue box is displayed.
3. In the Sequence Table box click the required sequence step.
4. Click . This moves the selected sequence step to the Module's Sequence box.
Tip: If a module needs to be serviced more than once per cycle time, it can be added to the sequence table in more
than one place. However, it is recommended that this be done only in exceptional circumstances.
9.4.31.2 Change a Module's Sequence Step
Although when a module placed in the strategy its position in the sequence table is specified, it may be necessary to
change a module's sequence step to ensure that the strategy is executed in the correct order, or to set up fast sequencing
if it is required.
To change a module’s sequence step:
1. Display the strategy page containing the module whose sequence step is to be changed.
2. Right-click the module, and click Sequence Step. The Sequence Step dialogue box is displayed.

The position of the module in the sequence table is indicated in the Module's Sequence box. Free steps in
the sequence table are listed in the Sequence Table box.
3. To allocate a sequence step to the module, in the Sequence Table box click the required sequence step, and
then click . This moves the selected sequence step to the Module’s Sequence box, adding the module to
the sequence table at that step. To remove a module from a step in the sequence table, in the Module’s
Sequence box click the sequence step, and then click . This moves the selected sequence step to the
Sequence Table box, and removes the module from that sequence step in the sequence table.
Note: If a module in an IQ controller needs to be serviced more than once per cycle time, it can be added to
the sequence table in more than one place. However, it is recommended that this be done only in exceptional
circumstances.
Important - For a module that enables sequence steps to be specified, it must appear in the sequence table
at least once (does not apply to digital input modules, or strategy that is event driven).
4. Click OK.
9.4.31.3 Insert a Gap in the Sequence Table
A gap of a specified number of sequence steps can be inserted in the sequence table before a specified step. All the
modules in the sequence table above the point at which the gap is added are moved to make space for the gap.
To insert a gap in the sequence table:
1. Display the strategy page containing the module that is in the sequence table at the step before which the gap
is to be inserted.
2. Click or on the Tools menu point to Sequence Steps and click Insert. The Insert Sequence Steps
3. In the box enter the number of steps that are to be added.

4. Click OK. The pointer changes to a .
5. Click the module that is in the sequence table at the step before which the gap is to be inserted.
9.4.31.4 Move Modules in the Sequence Table
Modules can be moved to a specified step in the sequence table.
To move modules in the sequence table:
1. Display the strategy page containing the modules whose positions in the sequence table are to be changed.
2. Change the next sequence step in the Next Module List to the required sequence step.
3. Click or on the Tools menu point to Sequence Steps and click Move. The pointer changes to a .
4. Click the module that is to be moved in the sequence table. The module will be moved to the sequence step
specified by the sequence pointer and the pointer incremented by 1.
5. Repeat step (4) for all the modules that are to be moved in the sequence table.
6. Once the required modules have been moved, click anywhere on the page. The cursor changes back to
normal.
9.4.31.5 Remove Modules from the Sequence Table
When a module is placed on a strategy page, it is assigned a place in the sequence table. It is possible to remove a
module from the sequence table completely. This is useful if the order in which the modules are processed is to be
changed; several modules can be quickly removed from the sequence table, and then assigned a new place in the table.
Important – When configuring pre IQ3 controllers and IQECO a module must appear in the sequence table at least
once for it to function. When configuring IQ4 and IQ3 controllers removing a module from the sequence table will
cause it to be event driven.
IQSET indicates modules that are not in the sequence table by highlighting the sequence step part of the module on
the strategy in orange for IQ3, IQ4 and in red for pre IQ3 and IQeco controllers.
Note: There are some module types which cannot be placed in the sequence table.
To remove modules from the sequence table:
1. Display the strategy page containing the modules to be removed from the sequence table.

2. Click , or on the Tools menu point to Sequence Steps and click Free. The pointer changes to a .
3. Click each module that is to be removed from the sequence table in turn. Clicking on a module will remove
it completely from the sequence table.
4. Once the required modules have been removed from the sequence table, right-click. The cursor will change
back to normal.
9.4.32 Set up Event Driven Strategy
Event driven strategy can be used in IQ3 and IQ4 controllers to cause a piece of strategy to be processed when an
event occurs. It is designed for applications where which must have an immediate response to a digital input e.g. for
lighting strategies where the light must be turned on as soon as the switch operated.
Modules in an event driven strategy do not appear in the sequence table they are processed when any input in any
module in the event driven strategy is changed. To achieve instant response all modules from the input to the output
must be event driven.
Because event driven module will run whenever one or more of its inputs changes therefore care should be taken to
ensure that the output of a module in the block does not change the input of a previous module (loop back) otherwise
the strategy could go into an infinite loop, causing the controller to go through the event driven part of the strategy as
fast as possible forever. This will cause performance issues with the controller causing the other parts of the strategy
to run slowly or not at all.
IQ4 and IQ3 v3.0 controllers attempt to protect against this by limiting each event driven module to run a maximum
of 15 times per second.
Caution - The use of event driven strategy with a loop back is not recommended. If in doubt you don't use it.
To set up event driven strategy:
1. Create the required strategy as required ensuring that is standalone.
2. Remove the modules from the sequence table by clicking to change the pointer to a , and then clicking
each module that is to be removed from the sequence table. Once the required modules have been removed
from the sequence table, right-click. The cursor will change back to normal.
Unsequenced modules are indicated by an orange highlight on the sequence step part of the module icon.
9.4.33 Set up Fast Sequencing
Fast sequencing can be used in pre IQ3 controllers to reduce the time delay in processing strategy associated with a
digital input.
Digital inputs do not normally appear in the sequence table of pre IQ3 controllers because they are always serviced
every 15.6 msecs. However, the modules that process their inputs can only be serviced when their turn occurs in the
sequence table. To reduce this time delay, fast sequencing can be used to jump to the part of the sequence table that
contains the strategy that processes the digital input.
To set up fast sequencing:
1. If necessary, change the sequence steps of the modules in the part of the strategy that is to be fast-sequenced
so that they have sequential sequence steps, and are as near to the end of the sequence table as possible.
2. Display the strategy page containing the digital input that is to be fast sequenced.
3. Right-click the digital input, and click Sequence Step. The Sequence Step dialogue box is displayed.
4. In the Sequence Table box click the sequence step immediately before the first sequence step of the strategy
that is to be fast-sequenced, and click . This moves the selected sequence step to the Module's Sequence
box.

5. Click OK.
6. Right-click the last module in the piece of strategy that is to be fast-sequenced, and click Sequence Step.
The Sequence Step dialogue box is displayed.
7. Click Add Return Step.
8. Click OK. An R appears in the sequence indicator to indicate the return step.
9.4.34 Set up the Controller's Normal Occupation Time Profile
The controller's normal occupation time profile (occupation times) must be set up in the Time Schedule module. This
method is different depending on the controller type and firmware version.
B-BC Schedules (IQ4v3.50 or greater)
Non-B-BC Schedules (Pre IQ4 v3.50)
9.4.34.1 Set up the Controller's Normal Occupation Time Profile for B-BC Schedules
Only IQ4s with v3.50 or greater firmware can be configured with B-BC schedules providing the 'B-BC Sched' option
is selected when the controller is added to the project.
To set up the controller's normal occupation time profile for B-BC schedules:
1. Add the required Time Schedule modules.
Add a Digital Time Schedule:
 Right-click the page and point to Other and click Digital Time Schedule. The Digital Time Schedule

Add an Analogue Time Schedule:
 Right-click the page and point to Other and click Analogue Time Schedule. The Analogue Time
Schedule dialogue box is displayed.
Add a Multistate Time Schedule:

 Right-click the page and point to Other and click Multi-State Time Schedule. The Multistate Time
Schedule dialogue box is displayed.
2. Select the Schedule tab.

3. Specify whether the module is enabled or disabled by clicking the Enabled/Disabled. The button will read
'Enabled' when the module is enabled and 'Disabled' when it is disabled.
5. In the Pin Level box enter the PIN level required to make changes to occupation profile (1 to 99).
6. In the States Category box select the required States Category module (Multistate Time Schedule modules
only).
7. Specify the default value.
For a Digital Time Schedule:
 Select 'On' or 'Off' from the list in the Default Value box.
For an Analogue Time Schedule:
 Enter the required value in the Default Value box.
For a Multistate Time Schedule:
 Select the required state from the list in the Default Value box.
 Select 'On' or 'Off' from the list in the Default Value box.
 Enter the required value in the Default Value box.
 Select the required state from the list in the Default Value box.
8. Specify start of the period over which the occupation time profile is to apply.
To specify a specific start date:
 Clear the Use Wildcard check box.
 In the Start Date box select the start date.
To use wildcards:
 Check the Use Wildcard check box.
 To ignore the day part of the specified date, select 'Unspecified' in the Day box, to use it select 'As
Specified' in the Day box.
 To ignore the month part of the specified date, select 'Unspecified' in the Month box, to use it select 'As
Specified' in the Month box.
 To ignore the year part of the specified date, select 'Unspecified' in the Year box, to use it select 'As
Specified' in the Year box.
To use wildcards:
9. Specify end of the period over which the occupation time profile is to apply.
 In the End Date box select the end date.
To use wildcards:

To use wildcards:
10. Specify the occupation time profile.
To specify the value for the entire day:
 Right click the day and select Set value for entire day. The Add Time Value Pair dialogue box is
displayed.
Digital Time Schedules
Analogue Time Schedules
Multistate Time Schedules
 Leave the start time as '00:00'.

 Specify the value.
 Select 'On' or 'Off' from the list in the Value box.
 Enter the required value in the Value box.
 Select the required state from the list in the Value box.
To use the default value:
 Check the Use Default Value check box.
 Click OK.

To specify a time value pair:
 Right click the day and select Add Time Value Pair. The Add Time Value Pair dialogue box is
displayed.
 Specify the start time in the Start time box.
 Select 'On' or 'Off' from the list in the Value box.
 Enter the required value in the Value box.
 Select the required state from the list in the Value box.
To use the default value:
 Check the Use Default Value check box.
 Click OK.
Note the specified value will apply from the start time until the start time of the next time value pair or midnight
whichever is first.
Note: A maximum of 20 time value pairs can be added to each day.
To edit a time value pair:
 Right click the time value pair and select Edit Time Value Pair. The Add Time Value Pair dialogue
box is displayed.
 Edit the time and value as required.
 Click OK.
To delete a time value pair:
 Right click the time value pair and select Delete Time Value Pair.
To copy and paste a time value pair:
 Right click the time value pair and select Copy Time Value Pair.
Note: A time value pair can be cut and paste by selecting Cut Time Value Pair instead.
 Right click the day and select Paste Time Value Pair.
To copy and paste an entire day:
 Right click the day and select Copy Day.
Note: A time value pair can be cut and paste by selecting Cut Day instead.
 Right click the day and select Paste Day to paste the occupation time profile to that day, Paste for
working week to paste the occupation time profile to Monday to Friday, or Paste for week to paste the
occupation time profile to everyday.
To clear a day:
 Right click the day and select Clear Day.
11. Click OK.

9.4.34.2 Set up the Controller's Normal Occupation Time Profile for Non-B-BC Schedules
IQ1, IQ2, IQ3 and IQ4 earlier than v3.50 firmware only have non-B-BC schedules. IQ4s with v3.50 or greater
firmware can be configured with non-B-BC schedule providing the 'B-BC Sched' option is not selected when the
controller is added to the project.
To set up the controller's normal occupation time profile for non-B-BC schedules:
1. Right-click the page and point to Other and click Digital Time Schedule. The Time Schedule dialogue box
is displayed.
2. In the Label box at the top of the dialogue box enter or select the name for the Time Schedule module.
3. In the Pin Level box enter the PIN level required to make changes to occupation times (1 to 99).
4. Set up the operating times for each day as required by adding periods, and dragging each end of the bar to
specify the times. To add another period, click drag to the left, and then drag each end of the bar to specify
the times. The times can also be specified by clicking the required period and entering the start and stop times
in the Start Time and Stop Time boxes. To set occupation for the whole day, right-click the day and click
On all day. To set non-occupation for the whole day, right-click the day and click Off all day. Two periods
can be merged by right-clicking a period and clicking Merge Left, or Merge right. Occupation times from
one day can be copied and then pasted to another day, or the entire week, by right-clicking the day whose
times are to be copied, clicking Copy Day, right-clicking the day to which the times are to be pasted, and
clicking Paste Day. To paste the times to the entire week right-click and click Paste for week, and to paste
them just to the working week (Monday to Friday) week right-click and click Paste for working week. A
single period can be copied by right-clicking it, and clicking Copy, it can then be pasted where required in a
similar way to pasting the entire day. To set occupation for the entire week, right-click and click On all week.
To set non-occupation for the entire week, right-click and click Off all week.
Note: For pre IQ3 controllers there is a maximum of 3 periods.
6. Click Graphic or Data to specify the required display mode.
7. Click OK.

9.4.35 Set up Calendar Modules
IQ4 v3.50 or greater. Calendar modules enable the date(s) used for an exception to be specified. When the output of
the Calendar module is '1' the occupation profile specified by the exception is used.
To set up Calendar modules:
1. Right-click the page and point to Other and click Calendar. The Calendar dialogue box is displayed.
3. In the Pin Level box enter the PIN level required to make changes to occupation profile (1 to 99).
4. Specify date(s) the module's output is to be '1'.
Add a calendar entry:
 Click +.
 In the Label box enter a name for the entry.
 In the Date option box select the required option.
 Specify the date(s)
Date or date pattern
To specify a specific date:
To use wildcards:
 Select the required option in the Day box.
Option Description
Unspecified Ignores the day part of the specified date.
Last Day> Uses the last day of the specified month.
Odd Days Uses the odd days.
Even Days Uses the even days.
As Specified Uses the day specified in the Start Date box.
 Select the required option in the Month box.
Option Description
Unspecified Ignores the month part of the specified date.
Odd Uses the odd months (January, March, May, July, September, November).
Even Uses the even days (February, April, June, August, October, December).
As Specified Uses the month specified in the Start Date box.

 Select the required option in the Year box.
Option Description
Unspecified Ignores the year part of the specified date.
As Specified Uses the year specified in the Start Date box.
Range of dates
 Specify the start date:
To specify a specific date, clear the Use Wildcard check box and in the Start Date box select the start
date.
To use wildcards check the Use Wildcard check box. The Day, Month and Year boxes are displayed
with 'Unspecified' selected and this cannot be changed. When wild cards are used for the start date the
schedule will be ON from any date until the End Date.
 Specify the end date:
To specify a specific date, clear the Use Wildcard check box and in the End Date box select the end date.
To use wildcards check the Use Wildcard check box. The Day, Month and Year boxes are displayed
with 'Unspecified' selected and this cannot be changed.
Week and Day
 To use a specific day of the week, select the required day from the list in the Day of Week box. To use
any day, select 'Unspecified'.
 To use a specific week of the month, select the required week from the list in the Week of Month box.
To use any week, select 'Unspecified'.
 To use a specific month of the year, or any odd or even month select the required option from the list in
the Month of Year box. To use any month, select 'Unspecified'.
Note: Month of Year is a display name representing the 'Start Month' parameter.
Edit a calendar entry:
 Click the calendar entry.
 Edit the entry as necessary.
Delete a calendar entry:
 Click the calendar entry.
 Click -.
5. Click OK.

9.4.36 Set up Exceptions
For IQ4 and IQ3 controllers any times that the controllers are to be in occupancy that are different to the normal
occupation time profile can be specified by setting up exceptions.
B-BC Schedules
Non-B-BC Schedules
9.4.36.1 Set up Exceptions for B-BC Schedules
Only IQ4s with v3.50 or greater firmware can be configured with non-B-BC schedule providing the 'B-BC Sched'
option is selected when the controller is added to the project.
To set up exceptions for B-BC schedules:
1. If Calendar modules are to be used to specify dates for the exceptions set up the required Calendar modules.
2. Double-click the required Time Schedule module.
3. Select the Exceptions tab.
4. Click +.
5. Specify a label for the exception in the Label box.
6. Specify the priority in the Priority box (0 to 16).
7. Specify date(s) the exception is to apply.
Manual entry:
 Select the required option in the Date Option box.
 Specify the date(s)
Date or date pattern
To specify a specific date:
To use wildcards:
 Select the required option in the Day box.
Option Description
Unspecified Ignores the day part of the specified date.

Option Description
Last Day Uses the last day of the specified month.
Odd Days Uses the odd days.
Even Days Uses the even days.
As Specified Uses the day specified in the Start Date box.
Option Description
Unspecified Ignores the month part of the specified date.
Odd Uses the odd months (January, March, May, July, September, November).
Eve Uses the even days (February, April, June, August, October, December).
As Specified Uses the month specified in the Start Date box.
Option Description
Unspecified Ignores the year part of the specified date.
As Specified Uses the year specified in the Start Date box.
Range of dates
 Specify the start date:
 To specify a specific date, clear the Use Wildcard check box and in the Start Date box select the
start date.
 To use wildcards check the Use Wildcard check box. The Day, Month and Year boxes are
displayed with 'Unspecified' selected and this cannot be changed. When wild cards are used for the
start date the schedule will be ON from any date until the End Date.
 Specify the end date:
 To specify a specific date, clear the Use Wildcard check box and in the End Date box select the
end date.
 To use wildcards check the Use Wildcard check box. The Day, Month and Year boxes are
displayed with 'Unspecified' selected and this cannot be changed.
Week and Day
 To use a specific day of the week, select the required day from the list in the Day of Week box. To use
any day, select 'Unspecified'.
 To use a specific week of the month, select the required week from the list in the Week of Month box.
To use any week, select 'Unspecified'.
 To use a specific month of the year, or any odd or even month select the required option from the list in
the Month of Year box. To use any month, select 'Unspecified'.
Note: Month of Year is a display name representing the 'Start Month' parameter.
Using a Calendar module:
 Select the required Calendar module from the list in the Calendar box.
8. Specify the occupation time profile.
To specify the value for the entire day:
 Right click the day and select Set value for entire day. The Add Time Value Pair dialogue box is
displayed.
 Leave the start time as '00:00'.


 For a Digital Time Schedule - Select 'On' or 'Off' from the list in the Value box.
 For an Analogue Time Schedule - Enter the required value in the Value box.
 For a Multistate Time Schedule - Select the required state from the list in the Value box.
 To use null - Select the Use Null check box.
 Click OK.
To specify a time value pair:
 Right click the day and select Add Time Value Pair. The Add Time Value Pair dialogue box is
displayed.
 Specify the start time in the Start time box.
 For a Digital Time Schedule - Select 'On' or 'Off' from the list in the Value box.
 For an Analogue Time Schedule - Enter the required value in the Value box.
 For a Multistate Time Schedule - Select the required state from the list in the Value box.
 To use null - Select the Use Null check box.
 Click OK.
Note the specified value will apply from the start time until the start time of the next time value pair or
midnight whichever is first.
Note: A maximum of 20 time value pairs can be added to each day.
To edit a time value pair:
 Right click the time value pair and select Edit Time Value Pair. The Add Time Value Pair dialogue
box is displayed.
 Edit the time and value as required.
 Click OK.
To delete a time value pair:
 Right click the time value pair and select Delete Time Value Pair.
To clear a day:
 Right click the day and select Clear Day.
9. Click OK.

9.4.36.2 Set up Exceptions for Non-B-BC Schedules
IQ1, IQ2, IQ3 and IQ4 earlier than v3.50 firmware only have non-B-BC schedules. IQ4s with v3.50 or greater
firmware can be configured with non-B-BC schedule providing the 'B-BC Sched' option is not selected when the
controller is added to the project.
To set up exceptions for non-B-BC schedules:
1. Double-click the Time Schedule module. The Time Schedule dialogue box is displayed.
2. In the calendar click the days the exception is to apply to. To select an exception that last more than a day
drag over the required days.
3. Click Add. The exception is added.
4. In the Label box in the Exceptions area, enter the name for the exception.
5. Check the day of the month the exception is to start in the Start Day box
6. Check the month the exception is to start in the Start Month box, and if necessary change it.
7. Check the day of the month the exception is to stop in the Stop Day box, and if necessary change it.
8. Check the month the exception is to stop in the Stop Month box, and if necessary change it.
9. In the Priority box click the priority of the exception.
10. In the Use box specify whether the exception is to occur, once only, be repeated every year, or not used at all
by clicking on the required option.
Option Description
Next Exception will occur only once.
Every Exception will be repeated every year.
Free Exception will not be used.

11. Set up the operating times for the exception as required by adding periods, and dragging each end of the bar
to specify the times. To add another period, click drag to the left, and then drag each end of the bar to
specify the times. To set occupation for the whole day, right-click the day and click On all day. To set non-
occupation for the whole day, right-click the day and click Off all day. The times can be specified by clicking
the required period and entering the start and stop times in the Start Time and Stop Time boxes. Two periods
can be merged by right-clicking a period and clicking Merge Left, or Merge right. Occupation times from
one day can be copied and then pasted to another day, or the entire week, by right-clicking the day whose
times are to be copied, clicking Copy Day, right-clicking the day to which the times are to be pasted, and
clicking Paste Day. To paste the times to the entire week right-click and click Paste for week, and to paste
them just to the working week (Monday to Friday) week right-click and click Paste for working week. A
single period can be copied by right-clicking it, and clicking Copy, it can then be pasted where required in a
similar way to pasting the entire day.
12. Click Apply.
13. Repeat steps (2) to (12) for any other exceptions required for the time schedule.
Note: It is not possible to add another exception until you clicked Apply.
14. Click OK.
9.4.36.3 Delete Exceptions
To delete an exception for B-BC schedules:
1. Double-click the required Time Schedule module.
3. In the Exception Entry box in click the exception that is to be deleted.

4. Click -.
5. Click OK.

To delete an exception non-B-BC schedules:
2. In the Label box in the Exceptions area, or in the calendar, click the exception that is to be deleted.
3. Click Delete. The exception is deleted.
4. Click OK.

9.4.36.4 Edit Exceptions
To edit an exception for B-BC schedules:
1. Double-click the required Digital or Analogue Time Schedule module.
3. In the Exception Entry box in click the exception that is to be edited.

4. The exception can now be edited in a similar way to when it was created.

To edit an exception non-B-BC schedules:
2. In the Label box in the Exceptions area or in the calendar, click the exception that is to be edited.
3. The exception can now be edited in a similar way to when it was created.

9.4.37 Configure IC Comms
When setting up ic comms you should remember how ic comms from one controller interact with other controllers -
refer to the controller's documentation for details.
If an IQ3, IQ4 or IQECO v2.0 or greater controller is to receive a byte, or bit type data from ic comms message a
digital byte module must be added to hold the data that is to be sent in response to the ic comms message. However,
it is not possible to set the value of the digital byte module from the strategy.
If sending ic comms without label matching to pre IQ3 controllers, analogue, bit, and byte references must be used to
specify where data is read from, or written to.
For a full description of the modules see the IQ Configuration Reference Manual (90-1533), the IQECO Configuration
Reference Manual (TE201089), IQ3 Configuration Reference Manual (TE200768), or IQ4 Configuration Reference
Manual (TE201263).
9.4.37.1 Set Up IC Comms Over the Trend Network
To set up ic comms over the Trend network:
1. Add the required ic comms module to the strategy page.
2. Edit the ic comms the module's parameters.
Note: For IQ4/BACnet, IQ3/BACnet and IQECO v2.0 or greater controllers only Protocol must be set to
'Trend'.
3. Ensure that values written to or read from exist in the remote devices.
If sending data to, or global to ic comms messages from a pre IQ3 controller to an IQ4, IQ3 or IQ eco v2.0
or greater controller analogue node modules, or digital byte modules must be added to receive the data. E.g.
if an ic comms message is being sending to analogue node 104 is to be received by an IQ3 controller an
analogue node module number 104 must be added. In a similar way if it is to receive a bit or byte value from
a pre IQ3 controller that is to be written to byte 47 digital byte module number 47 must be added to the
strategy.
If receiving a byte, or bit type data from ic comms message a digital byte module must be added to hold the
data that is to be sent in response to the ic comms message. However, it is not possible to set the value of the
digital byte module from the strategy.
For a full description of the module, see the IC Comms Modules sections of this manual.
9.4.37.2 Set Up IC Comms Over BACnet
IC comms to non-Trend BACnet devices can only be set up from IQ4/BACnet, IQ3/BACnet controllers and IQECO
v2.0 controllers.
To set up IC Comms over BACnet:
1. Add NTDs for each BACnet device ic comms are to be sent.
2. Add the required IC comms module to the strategy page.
3. Edit the IC Comms the module's parameters.
Note: Protocol must be set to 'BACnet'. The ic comms messages must be directed at the Trend address of the
NTD linked to the BACnet device the message is aimed at.
4. Ensure that values written to or read from exist in the remote devices.
If receiving a byte, or bit type data from ic comms message a digital byte module must be added to hold the
data that is to be sent in response to the ic comms message. However, it is not possible to set the value of the
digital byte module from the strategy.

9.4.37.2.1 Add NTDs
9.4.37.2.1.1 Add NTDs Manually
To add NTDs manually:
1. Add a LAN for the NTDs ensuring that the LAN type is set to 'BACnet'.
3. In the Device View right-click the LAN to which the NTD is to be added, point to Insert Device and click
NTD (Non Trend Device). The NTD Parameters dialogue box is displayed.
4. In the Address box enter the Trend address of the NTD. (1 to 119 excluding addresses 2, 3, and 10).
5. In the Name box enter a name for the NTD.
6. In the Details box enter details about the NTD.
7. In the Identifier box enter the NTD's identifier (30-characters).
8. If required in the Attribute 2 box enter a 30-character attribute for the NTD. This can be used in conjunction
with the identifier and the other attributes to identify the NTD.
14. Specify the device to which the message is to be sent. It is recommended that the device instance is used, and
if the device to which the message is being sent uses automatic IP addressing the device instance must be
used. For devices that do not support device instance addressing the BACnet address is used. However, this
is not suitable when automatic IP addressing is being used.

Using the Device Instance:
 In the Device Instance box enter the device instance of the BACnet device to which the alarms are to
be sent. If set to 0 the network number and MAC address parameters are used to address the BACnet
device. (Range 0 to 4194393).
Using the BACnet Address:
 In the Device Instance box enter 0.
 In the Network Number box enter the network number of the BACnet device to which the alarms are
to be sent. (Range 0 to 65534).
 In the MAC Address box enter the MAC address of the BACnet device to which the alarms are to be
sent.
15. Click OK.
9.4.37.2.1.2 Add NTDs from the System View
To add NTDs from the System View:
1. Add a LAN for the NTDs ensuring that the LAN type is set to 'BACnet'.
2. Browse the site containing the BACnet devices for which NTDs are to be created so that the BACnet devices
are displayed. This may require a visit to the site.
3. Display the System View and navigate to the BACnet devices.
4. Drag the BACnet devices that are to be represented by NTDs from the System View to the BACnet LAN in
the Device View. The Node Number dialogue box is displayed.
NTDs can be quickly added for all the BACnet devices on a BACnet network by dragging the BACnet
network from the System View to the BACnet LAN in the Device View. This will display the Starting Node
Number dialogue box which enables the network address of the first NTD to be created to be specified. A
separate NTD will be added for each BACnet device, the network address being incremented for each one.
5. In the Node box enter the network address of the NTD, or if an entire BACnet network has been added the
network address of the first NTD.
6. If the MAC address information is to be included select the Include MAC address details in devices check
box.
Note: MAC addresses should only be included when device ID addressing is not supported by the BACnet
devices.
7. Click OK. The NTDs are created, the device instance, network number, MAC address, vendor name, model
name and firmware version are imported.
8. Edit the NTDs to specify their identifier and attributes.
9.4.37.2.1.3 Delete an NTD
To delete an NTD:
2. In the Device View right-click the NTD that is to be deleted, and click Delete Device. A dialogue box is
displayed asking for confirmation of the deletion.
3. Click Yes to delete it.

Note: Deleting a NTD will permanently remove it from the strategy of any controller using it, and any IC Comms that
use it will no longer work.
9.4.37.2.1.4 Edit an NTD
To edit an NTD:
2. In the Device View right-click the NTD that is to be edited, and click Device Details. The NTD Parameters

4. Once the details have been specified, it is possible to save the changes without sending them to the controllers
that use the NTD, or for IQ3 and IQ4 controllers to save the changes, and send them to the controllers that
use the NTD.
To save the changes without sending them to the controllers that use the NTD:
 Click OK.
Note that if changes are not sent to the controllers that use the NTD it is necessary to download the strategy.
To save the changes, and send them to the controllers that use the NTD:
 Click OK and Send to IQ3's. The Select Site Connection dialogue box is displayed.
 In the Site Connection box select the required site.

 In the Pin box enter the PIN required to authorise the change in the controller.
 If connected directly to a controller, or using a local supervisor port that does not provide network access
click Direct Connection.

 Click OK.
Note that this feature is not available for IQECO controllers. If changes have been made to NTDs in an
IQECO controller click OK to save the changes. The strategy must then be downloaded.
9.4.37.3 Add IC Comms Modules to a Strategy Page
To add an IC Comms module to a strategy page:
1. Display the strategy page to which the module is to be added. It is good practice to place ic comms modules
on a separate page.
2. Click the required module type in the IC Comms toolbar or right-click the page where the module is to be
placed, point to IC Comms, and click the module.
Icon Description
Enables a Data From IC Comms module to be added to the strategy page.
Enables a Data To IC Comms module to be added to the strategy page.
Enables a Global To IC Comms module to be added to the strategy page.
Enables a Minimum IC Comms module to be added to the strategy page.
Enables a Maximum IC Comms module to be added to the strategy page.
Enables a Sum IC Comms module to be added to the strategy page.
Enables an Average IC Comms module to be added to the strategy page.
The IC Comms Number dialogue box is displayed.
3. In the Module Number box specify the module's number. Clicking will check to see that the module
number is valid, and unused.
4. If adding data to, data from, or global to ic comms modules specify the output type by selecting the Analogue,
Byte, or Bit.
5. Click OK. The cursor will change to a hand .
page.
Note: If auto edit is enabled, the Parameters dialogue box for the module will be displayed.

9.4.37.4 Edit an IC Comms Module's Configuration Parameters
Note: If using data to or global to IC Comms module to send a specific byte pattern it is necessary to use a D to A
Logic module to convert the digital bits to an analogue value which can be linked to the source of the ic comms
module.
To edit an IC Comms module's configuration parameters:
1. Display the strategy page that contains the module or connective to the module that is to be edited.
2. Double-click the module, or connective, or right-click it, and click Edit Parameters. The Parameters
dialogue box for the module is displayed.
Dialogue box for IQ4 and IQ3 and Pre IQ3 Controllers
Dialogue box for IQECO Controllers

3. In the Label box enter a label for the module.
4. Specify the protocol - IQ4/BACnet, IQ3/BACnet and IQECO v2.0 or greater controllers only.
Data From, Data To, Global To
 In the Protocol box select the protocol that is to be used to send the IC Comms message. If set to Trend
the message is sent to devices on the Trend network. If set to BACnet the message is sent to devices on
the BACnet network.
Note: To send an IC Comms message over both the Trend network, and the BACnet network a separate IC
Comms module is required for each network i.e. the message must be sent twice once on the Trend network,
and once on the BACnet network.
5. Specify the remote address.
Data From
 In the Remote Address box enter the network address of the controller containing the information that
is to be read. If BACnet has been selected as a protocol this must be the address of the NTD linked to
the BACnet device that contains the required value. For IQECO v2.1 or greater with 'COV mode' enabled
this parameter specifies the address of NTD linked to the BACnet device sending the COV messages.
(Range = 1 to 119 excluding addresses 2, 3, and 10).
Data To
 In the Remote Address box enter the network address of the controller to which the information is to be
written. If BACnet has been selected as a protocol this must be the address of an NTD. (Range = 1 to
119 excluding addresses 2, 3, and 10).
6. Specify the remote attributes.
Global To, Minimum, Maximum, Sum, Average
 In the Remote Attributes box select the attribute that must match in all devices that are to respond to
the message. For IQ4, IQ3 and Pre IQ3 controller range = 0 to 7. 0=Comms Disabled, 1=identifier, 2=F
attribute, 3=G attribute, 4=H attribute, 5=I attribute, 6=J attribute, and 7=K attribute. For IQECO
controllers range = 0 - Comms Disabled, 1=identifier, 2=F attribute, 3=G attribute, 4=H attribute.
7. Specify the remote Lan.
Data From
 In the Remote Lan box enter the LAN number of the controller containing the information that is to be
read. For IQ4/BACnet and IQ3/BACnet controllers only if BACnet has been selected as a the protocol
this must be the LAN number of the NTD linked to the BACnet device that contains the required value.
For IQECO v2.1 or greater with 'COV mode' enabled this parameter specifies the LAN number of NTD
linked to the BACnet device sending the COV messages. (Range = 0 to 119 excluding addresses 2, 3,
and 10, 0 specifies the local LAN).
Data To, Global To, Minimum, Maximum, Sum or Average
 In the Remote Lan box enter the LAN number of the controller to which the information is to be written.
If BACnet has been selected as the protocol this must be the address of an NTD. (Range = 0 to 119
excluding addresses 2, 3, and 10, 0 specifies the local LAN).
8. In the Message Interval box enter the length of time (in minutes) between a message being sent and then
repeated. (Range 0 to 1440 for IQ4, IQ3 and IQECO controllers and 0 to 546 for pre IQ3 controllers. 0
specifies an interval of 15 seconds).
9. Specify whether the module is to listen for unconfirmed COV messages - IQECO v2.1 or greater and IQ4
v3.2 or greater using BACnet protocol.
Data From
 Select the COV Mode check box.
10. Specify the significant change.
Data To, Global To
 In the Significant Change box enter the amount the value of the source can change before a message is
sent (Range -3276 to+3276).
11. Specify the write priority - IQ4, IQ3 and IQ eco v2.0 or greater only.
Data To, Global To
 In the BACnet Write Priority box enter the priority that is to be used to write the value (Range 1 to 16).

12. Specify where the value is to be written.
Data To, Global To
 If label matching is to be used to specify where the value is to be written to select the Label Matching
check box.
Note: Label matching is not available if 'Protocol' is set to 'BACnet'. If label matching is specified, and the
module linked to the source (L) does not have a label the IC Comms will not work.
 If label matching is not being used, specify where the value is to be written to IQ4, IQ3 controllers,
IQECO controllers or Pre IQ3 controllers.
IQ3 and IQ4 Controllers:
 Click Look Up. The Module Reference Helper dialogue box is displayed.
 In the Module Type box select the type of module to which information is to be written.
 In the Number box enter the number of the module to which information is to be written.
 In the Parameter box specify the module parameter that is to be written. To specify other values, select
the Advanced check box, and in the Reference box enter the code for the required value.
Note that care should be taken when using the advanced option, to prevent making unwanted changes to
parameters.
If Protocol is Trend:
<Module>(<Module Parameter>)
<Module> specifies the type of module using its module identifier and module number (e.g., S1 specifies
sensor 1). For details of the module identifier, see the appropriate module section of this manual.
<Module Parameter> specifies the parameter within the module that is to be displayed (e.g. the value of
a sensor). The module parameter is specified using the parameter identifier (ID), and can be any
parameter available within the specified module.
E.g. K1V to specify the value of knob 1
If referencing a byte, the following format should be used:
B<Module Number>S
<Module Number> is the number of the module
E.g. B3S
If referencing a bit, the following format should be used:
B<Module Number>S<Bit Number>
<Module Number> is the number of the module. <Bit Number> is the number of the required bit.
E.g. B3S3
Note that if compatibility with pre IQ3 controllers is required Analogue, Bit, and Byte references must
be used.
If Protocol is BACnet:
<object type><instance><property>
<object type> specifies the type of object (e.g. AV specifies an analogue value object). <instance> is the
number of the required object. <property> specifies the parameter within the module that is to be
displayed (e.g. PV specifies the present value).

Note that <property> is optional and when omitted the present value (PV is used (i.e. AV1, and AV1PV
are the same).
 Click OK to return to the Parameters dialogue box.
IQECO Controllers:
Pre IQ3 Controllers
 For analogue type modules in the Remote Analogue box enter the number of the analogue node that is
to be written.
 For byte type modules in the Remote Byte box enter the number of the byte that is to be written.
 For bit type modules in the Remote Bit box enter the bit that is to be written in the form:
<nn>,<yy>
Where <nn> is the byte containing the bit that is to be written and <yy> is the bit.
Note: The value that is to be written to can be specified by dragging the value from the System View on to
the module in the strategy. If a value from a Trend device, or a BACnet device for which an NTD has been
specified is dragged on to a module the values of the Remote LAN, Remote Address, and Remote Node
parameters will be overwritten those of the dragged value. If an NTD has not been set up for a BACnet device
only the value of the Remote Node parameter will be overwritten.
13. Specify the value to be read.
Data From
 Specify the value that is to be read IQ4, IQ3 controllers, IQECO controllers or Pre IQ3 controllers.
IQ4, IQ3 Controllers
To specify normal values:
 If Protocol is Trend in the Module Type box select the type of module from which information is to be
read, or if Protocol is BACnet in the Object Type box select the type of BACnet object from which
information is to be read.
 If Protocol is Trend in the Number box enter the number of the module from which information is to be
read, or if Protocol is BACnet in the Instance box enter the instance of the BACnet object from which
information is to be read.
 If Protocol is Trend in the Parameter box specify the module parameter that is to be read.

To specify advanced values:
Care should be taken when using the advanced option, to prevent making unwanted changes to parameters.
 To specify other values, select the Advanced check box.
 In the Reference box enter the code for the required value.
E.g. K1(V) to specify the value of knob 1
B<Module Number>S
E.g. B3S
E.g. B3S3
Note: If compatibility with pre IQ3 controllers is required Analogue, Bit, and Byte references must be
used.
Note: <property> is optional and when omitted the present value (PV is used (i.e. AV1, and AV1PV are
the same).
Multiple parameters can be specified by using ';' to separate each parameter reference. e.g.
<parameter 1 object type><parameter 1 instance><parameter 1 property>;<parameter 2 object
type><parameter 2 instance><parameter 2 property>;<parameter n object type><parameter n
instance><parameter n property>
IQECO Controllers:
 In the Module Type box select the type of module from which information is to be read,
 In the Number box enter the number of the module from which information is to be read.

 In the Parameter box specify the module parameter that is to be read.
Note: For IQECO v2.1 or greater with 'COV mode' enabled this parameter specifies the BACnet parameter
sending the COV messages.
Pre IQ3 Controllers
 For analogue type modules in the Remote Analogue box enter the number of the analogue node from
that is to be read.
 For byte type modules in the Remote Byte box enter the number of the byte that is to be read.
 For bit type modules in the Remote Bit box enter the bit that is to be read in the form:
<nn>,<yy>
Where <nn> is the byte containing the bit that is to be read, and <yy> is the bit.
Note: The value that is to be read can be specified by dragging the value from the System View on to the
module in the strategy. If a value from a Trend device, or a BACnet device for which an NTD has been
specified is dragged on to a module the values of the Remote LAN, Remote Address, and Remote Node
parameters will be overwritten those of the dragged value. If an NTD has not been set up for a BACnet device
only the value of the Remote Node parameter will be overwritten.
Minimum, Maximum, Sum, Average:
 If label matching is to be used to specify the value to be read, select the Label Matching check box.
 If label matching is not being used, specify where the value is to be read IQ4, IQ3 controllers, or Pre IQ3
controllers.
IQ4, IQ3 Controllers:
 In the Parameter box specify the module parameter that is to be written. To specify other values, select
the Advanced check box, and in the Reference box enter the code for the required value.
Note that care should be taken when using the advanced option, to prevent making unwanted changes
to parameters.
E.g. K1V to specify the value of knob 1
B<Module Number>S
E.g. B3S

E.g. B3S3
Note that if compatibility with pre IQ3 controllers is required Analogue, Bit, and Byte references must
be used.
Note that <property> is optional and when omitted the present value (PV is used (i.e. AV1, and AV1PV
are the same).
Note: The value that is to be read from can be specified by dragging the value from the System View on to
the module in the strategy. If a value from a Trend device, or a BACnet device for which an NTD has been
specified is dragged on to a module the values of the Remote LAN, and Remote Node parameters will be
overwritten those of the dragged value. If an NTD has not been set up for a BACnet device only the value of
the Remote Node parameter will be overwritten.
14. Specify the value that is to be sent
Data To, Global To
 For IQ4, IQ3 controllers and IQECO v2.0 or greater controllers only, if the value that is to be sent
(source) is to be a constant value in the Source box enter the value (Range = -1020 to +1020).
Note: If the box is greyed out the value that is to be sent is being obtained from another module. If this is not
what is required deleted the link, and then specify the value.
15. Click OK.

9.4.38 Set up Controller Security
IQSET will force creation of a user called Admin' and the 'Guest' user when a controller is added. However, it is
necessary to ensure that this configuration is as required, and to create and additional User modules for other users.
To set up controller security:
1. For IQ4 and IQ3 controllers set up the Guest user.
2. Add the required user modules to the strategy.
Caution the controller’s security is enabled as soon as a user module is set up; it is therefore important that the
at least one user module has a PIN level of 99.
9.4.38.1 Set up the Guest User
For IQ4 and IQ3 controllers it is necessary to set up the Guest User. This defines what information a user can access
from the controller from a web browser and they don’t have a username and password.
Note: IQSET will add the Guest User when the strategy is created or edited.
To setup the Guest User:
1. If the Guest User has not been added to the strategy add a user to the strategy and select the Guest User (Not
Logged In) check box.
2. In the Home Page box select the required home page from the list. To specify a GraphIQ click and select
the required page from the dialogue box that is displayed. To specify other pages, enter the required code.
3. For IQ4 and IQ3 controllers with v1.3 firmware or greater specify the information the guest user has access
to when the controller is accessed from a web browser by selecting the required check boxes.
Alarms Specifies whether the user has access to alarms.

Time Schedules Specifies whether the user has access to Time Schedules.
Modules Specifies whether the user has access to module pages.
GraphIQs pages Specifies whether the user has access to graphical display pages.
GraphIQs Navigator Specifies whether the user has access to the navigator on graphical display pages.
4. Click OK.
Tip: The module's output that defines whether the user is currently logged in or not can be linked to other pieces of
strategy e.g. to perform a certain action when the user logs in.
User modules in IQ3 and IQ4 strategy can be edited and deleted just like any other module.
9.4.38.2 Add User Modules to the IQ3 or IQ4 Strategy
User modules in IQ3 or IQ4 strategy enable security to be set up, which prevents unauthorised changes from being
made to both the strategy, and items like setpoints. A user module defines the username and password, or PIN required
to log on, and the PIN level assigned to people who log in using that PIN. It also defines the page that is displayed
when a user logs in form a web browser, and how the period of inactivity before the user will automatically be logged
off.
Note: IQSET will add the Guest User and Admin User when the strategy is created or edited.
To add a User module to IQ3 or IQ4 strategy:
1. Display a strategy page for the controller for which user modules are to be set up.
2. Right-click anywhere on the page, point to Users and click User. The Select Module dialogue box is
displayed.
3. In the Module Number box enter the number of the user module that is to be added.
4. Click OK. The dialogue box will be closed.
page. If auto edit is enabled, the Parameters dialogue box for the module is displayed.

6. Double click the module to display the User Parameters dialogue box if it is not already displayed.
7. If the user is to be the Guest User select the Guest User (Not Logged In) check box.
8. IQ4 v3.30 or greater only. If the user is to only have access to the controller's web pages, select the Web Use
Only check box.
9. Enter the user module's username in the Name box.
10. Enter the user module's password in the Password box.
11. If Web Use Only is not selected enter the 4-digit number that must be entered by the user to log on from a
display, or must be sent by a tool /supervisor to authorise a change in the Pin box.
12. In the Level box enter the PIN level to be assigned to the guest user (Range = -1 to 99).
13. In the Timeout box enter the length of time in minutes after which the user will be automatically logged off
(Range = 1 to 15 minutes).
14. If editable select the required home page from the list in the Home Page box. To specify a GraphIQ, click
and select the required page from the dialogue box that is displayed. To specify other pages, enter the
required code.
15. For IQ4 and IQ3 controllers with v1.3 firmware or greater specify the information the user has access to
when the controller is accessed from a web browser by selecting the required check boxes.
Alarms Specifies whether the user has access to alarms.

Time Schedules Specifies whether the user has access to Time Schedules.
Modules Specifies whether the user has access to module pages.
GraphIQs pages Specifies whether the user has access to graphical display pages.
GraphIQs Navigator Specifies whether the user has access to the navigator on graphical display pages.
16. Click OK.
If required, the module's output that defines whether the user is currently logged in or not can be linked to other pieces
of strategy e.g. to cause a specific action when the user logs in.
For a full description of the user module see the 'User Modules' section of this manual. User modules in IQ3 and IQ4
strategy can be edited and deleted just like any other module.
9.4.38.3 Add User Modules to IQ2 Strategy
User modules in IQ2 strategy enable PIN protection to be set up, which prevents unauthorised changes from being
made to both the strategy, and items like setpoints. A user module defines the PIN required to log on, and the PIN
level assigned to people who log in using that PIN.
To add a User module to IQ2 strategy:

2. Right-click anywhere on the page, point to Users and click User. The User Pins dialogue box is displayed.
3. In the User Number box use the arrows to specify the user module that is to be defined.
4. In the Level box enter the required PIN level (0 to 99).
5. In the Pin box enter the PIN number (4-digits).
6. Repeat steps (3) to (5) until all the required user modules have been set up.
7. Click OK.
Caution the controller's security is enabled as soon as a user module is set up; it is therefore important that the
first user module set up has a PIN level of 99.
9.4.38.4 Add User Modules to IQECO Strategy
User modules in IQECO strategy enable PIN protection to be set up, which prevents unauthorised changes from being
made to both the strategy, and items like setpoints. A user module defines the PIN required to log on and authorise
the change.
To add a User module to IQECO strategy:
3. Click Disabled to enable the security. The button will change to Enabled and the Pin box made available.
4. In the Pin box enter the PIN number (4-digits).
Note: The PIN must not be set to '0000'.
5. Click OK.
9.4.38.5 Delete User Modules from IQ2 Strategy
To delete User modules from IQ2 strategy:
1. Display a strategy page for the controller for which user modules are to be deleted.
3. In the User Number box use the arrows to specify the user module that is to be deleted.
4. In the Level box set the PIN level to 0.
5. In the Pin box set the PIN to 0.
6. Click OK.
Caution if PIN protection is to be used at least one user module with a PIN level of 99 must be set up.
9.4.38.6 Delete User Modules from IQECO Strategy
To delete User modules from IQECO strategy:
1. Display a strategy page for the controller for which user modules are to be deleted.

3. Click Enabled to enable the security. The button will change to Disabled.
4. Click OK.
9.4.38.7 Edit User Modules in IQ2 Strategy
To edit user modules in IQ2 strategy:
3. In the User Number box use the arrows to specify the user module that is to be edited.
4. Specify the PIN level, and PIN number as required.
5. Click OK.
Note: Setting the PIN level and PIN number to 0 removes that user module from the strategy.
9.4.38.8 Edit User Modules in IQECO Strategy
To edit IQECO user modules:
1. Display a strategy page for the controller for which User modules are to be set up.
3. In the Pin box specify the PIN number as required.

4. Click OK.
9.4.38.9 Configure the Web Server
The IQ4 is shipped from the factory with its HTTP web server enabled. If the web servers are not required they should
be disabled. If the IQ4’s web server is required, the HTTPS web server should be used.

To configure the Web Servers:
1. Right-click the strategy page, and point to Device, point to Network and click Ethernet IP Module, or on
the Device menu click Ethernet IP Module. The Ethernet IP Module dialogue box is displayed.
2. In the Web Server Mode box specify the web server operation.
Option Description
Off Both the HTTP and HTTPS web servers are OFF
HTTPS (HTTP HTTPS web server is ON and requests to the HTTP web server are redirected to the
Redirect) HTTP server, HTTP server is OFF
HTTPS Only HTTPS web server is ON, HTTP server is OFF
HTTP & HTTPS Both the HTTP and HTTPS web servers are ON (not recommended)
HTTP Only Only the HTTP web server is ON (not recommended)
3. If the HTTP web server is being used (not recommended) specify the port number for the HTTP web server
in the Web Server Port box.
4. If the HTTPS web server is being used specify the port number for the HTTPS web server in the Secure
Web Server Port box.
Note: Use of the IQ4’s HTTP web server will reduce the IQ4’s security.
For details of Type 4 (Ethernet IP) Network modules and their parameters see Ethernet IP Network Modules.

9.4.39 Set up CNC User Modules
IQ4 v3.60 or greater. Type 1 CNC User modules specify the username and password required to connect to a vCNC
in the controller operating in secure mode.
To add a CNC User module:
1. Display a strategy page for the controller for which CNC User module is to be added.
2. Right-click anywhere on the page, point to Users and click CNC User. The Select Module dialogue box is
displayed.
3. In the Module Number box enter the number of the CNC User module that is to be added.
4. Click OK. The dialogue box will be closed.
page. If auto edit is enabled, the CNC User dialogue box is displayed.
6. Double click the module to display the User Parameters dialogue box if it is not already displayed.
7. Enter the CNC User module's name in the Name box.

8. Enter the CNC User module's password in the Password box.
9. Click OK.
For a full description of the Type 1 CNC user module see IQ4 Type 1 CNC User Modules. CNC modules can be
edited and deleted just like any other module.
9.4.40 Set up vCNC Modules
(IQ4 v3.60 or greater) The vCNC modules store information about the controller's virtual CNC.
To set up the vCNC modules for an IQ4 controller:
1. Display a strategy page for the controller for which the vCNC modules are to be specified.
2. Right-click the strategy page, and point to Device and click vCNC Modules, or on the Device menu click
vCNC Modules. The Configure vCNCs dialogue box is displayed listing the available vCNC Modules for
the controller.

3. If the vCNC configuration is to be downloaded to the controller when the strategy is downloaded clear the
Not Sent check box.
Note: If the vCNC configuration is downloaded the controller will reset and if the vCNC configuration is
significantly changed IQSET may not be able to reconnect until the connection is reconfigured to match the
new vCNC configuration.
4. Specify whether the vCNC port number is to be manually specified or use the default value (10000 + Address)
by selecting/clearing the Use Default Port box.
Note: The 'Use Default Port' setting applies to all vCNCs in the controller.
5. Enable/disable the required vCNCs by clearing/selecting the Disable check box, (selected = disabled) for
click OK.
6. Specify the label for the vCNC in the Label box.
7. Specify the network address of the vCNC in the Address box (range 1, 4 to 119 excluding 10). It must be
unique on the Local LAN.
8. If the default port is NOT being used specify the port for the vCNC in the Port box.
9. Specify the security mode in the Security Mode box.
10. If the vCNC is to send device dead alarms select Device Dead Alarm.
11. If any of the vCNCs are operating in 'Secure' mode and you have not already set up the required CNC User
Modules you MUST add one now.
 Enter the CNC User module's name in the Name box.
 Enter the CNC User module's password in the Password box
 Retype the password in the Retype Password box.
11. Click OK.

9.4.41 Set up Display and Directory Modules
Display modules and directory modules enable a set of displays to be defined within the controller. Each display can
show a mixture of different item types, e.g. sensor values, knob values etc. and, where appropriate, enable adjustments
to be made, and values to be graphed. They can then be viewed on Trend supervisory products. The display and
directory modules can be defined either by manually setting them up, or by automatically setting them up using the
Plant View.
PIN levels can set up for each directory module to prevent unauthorised use of those pages. When PIN levels have
been set up, users will only have access to a directory module when logged on to the supervisor at a level equal to or
above the directory module’s PIN level. IQSET will only allow display and directory modules to be set up if they
exist in that controller.
Note: If engineering directories that are to be navigated using an IQView then it is recommended that a maximum of
9 directory modules be used as more than this will cause scroll bars to be displayed which reduces the amount of
usable screen.
To set up the display and directory modules:
1. Display a strategy page for the controller for which the display and directory modules are to be setup.
2. Click or on the Tools menu click Display and Directory Setup. The Display and Directory Setup
3. If the Plant View has been set up, it can be used to form the structure required for the display and directory
modules. To do this in the Plant View box click the required part of the Plant View, and drag it onto the
Root area of the Display and Directory View box, and release the mouse button in the correct place.
4. Add any other directory modules that are required.
5. Add any other display modules that are required. The Free Modules Count area will display the number of
free display and directory modules. If you use more modules than are available in the controller, you will not
be allowed to continue until the module count is zero or greater.
6. If necessary, change the order of the display modules.
7. Edit the display and directory modules. See the 'Edit a Directory Module in IQ3 or IQ4 Strategy', 'Edit IQ2
Directory Modules', 'Edit IQ2 Display Module Parameters', 'Edit a Dynamic Display Module', and 'Edit a
Static Display Modules' sections of this manual for more details.
Note: The parameters of IQ3 and IQ4 display and directory modules can also be edited using the Graphical
Display Page Editor.
8. Click OK.
The display and directory module structure in another controller can be imported, to save time when setting up the
display and directory module structure.

9.4.41.1 Add Modules
9.4.41.1.1 Add a Directory Module to IQ3 and IQ4 Strategy
Directory modules form part of the description of a graphical display page.
Note: If engineering directories that are to be navigated using an IQView then it is recommended that a maximum of
9 directory modules be used as more than this will cause scroll bars to be displayed which reduces the amount of
usable screen.
To add a directory module to IQ3 or IQ4 strategy:
3. In the Display and Directory View box right-click P0, or the directory module to which the new module is
to be added, and click Insert Directory. The Directory Item dialogue box is displayed.
4. In the Title box enter the name for the directory module. Maximum length 30-characters.
5. In the Pin level box enter the PIN level required to access the module (1 to 99), or use to set it.
6. Select the Colour check box then click Change to display the Color dialogue box, then click the required
background colour and click OK to return to the Styling dialogue box. Custom colours can be used by
clicking Define Custom Colors>> in the Color dialogue box. If a background colour is not required, clear
the Colour check box.
7. If required specify the backdrop for the page by clicking Change and selecting the required backdrop from
the list in the dialogue box that is displayed.
8. In the Refresh Rate box enter the required refresh rate in seconds.

9. In the Width box enter the width of the page in pixels, and in the Height box enter the height of the page in
pixels, or alternatively in the Page Size box click the required.
10. Click OK.
9.4.41.1.2 Add a Dynamic Display Module
Dynamic display modules enable values from the controller to be included in the views. If required, the value can be
set to be a link to the 'Details' page of the module from which the value is sourced. Each display module has a parent
parameter, which is the directory module to which it is attached. This is specified automatically when the module is
created.
To add a dynamic display module:
3. If necessary, add the directory module to which the dynamic display item is to be added.
4. In the Display Items box click the item that the display module is to access and drag it on onto the required
directory module in the Display and Directory View box, and release the mouse. If required, the items
displayed in the Display Items box can be limited to specific item types by clicking the appropriate button.
Option Description
Digin Displays all digital inputs in the strategy.
Driver Displays all drivers in the strategy.
Knob Displays all knobs in the strategy.
Sensor Displays all sensors in the strategy.
All Displays all items in the strategy.
Switch Displays all switches in the strategy.
Time Schedule Displays all time schedules in the strategy.
5. Click OK.

9.4.41.1.3 Add a Static Display Module
Static display modules enable static text to be included on graphical display pages. If required, the static text can be
set to be a link to any specified URL. Each display module has a parent parameter, which is the directory module to
which it is attached. This is specified automatically when the module is created.
To add a static display module:
3. If necessary, add the directory module to which the static display item is to be added.
4. Right-click the directory module that is to contain the static display module and click Insert Static Display
Item. The Display Item dialogue box is displayed.
5. In the Label box enter the text that is to be displayed.

6. In the Pin level box enter the PIN level required to view or use the module (1 to 99), or use to set it.

7. If the text is to be a link click Change. The URL Editor dialogue box is displayed.
8. In the URL Type box click the required type of link from the list.
Option Description
Unknown Link Used to create a link to of a type not covered by the other URL types. E.g. a link to an FTP
Type site.
Used to create a link to a specified email address. When the link is selected the default email
Email Link
editor will be loaded with a new email loaded with the address already defined.
Website Link Used to create a link to a specified URL.
Directory Link Used to create a link to a page of information held within the controller itself.
9. In the URL box enter the destination of the link. What is entered depends on the type of URL selected above
see the table below for more information.
URL Type What needs to be Entered

Unknown Link
Enter the required destination.
Type
Email Link Enter the required email address E.g. john.smith@work.com
Enter the Website’s URL. E.g. http://www.trend-controls.com
To link to a page in another controller enter the URL for that page. If the destination
Website Link controller has security set up add ? autoLogin=TRUE to the end of the URL. This will pass
the current login information to the destination controller. It is then compared with the
users set up in the destination controller and if it matches access is granted.
Directory Link
to:
Enter trendModule:GraphIQs/<Directory Module Structure>/index.htm
Graphical
Where <Directory Module Structure> is the directory module structure of the Display
Display
module that defines the page.
Page
E.g. Enter GraphIQs/Boilers/Boiler1/index.htm
Enter trendModule:<Module Type>.htm
Where <Module Type> specifies the type of module using its module identifier (e.g. S
Module List
specifies sensor). For details of the module identifiers see the appropriate module section
Page
of this manual.
E.g. type S.htm to display the sensor module list page.
Enter trendModule:Module Type><Module Number>.htm
Where <Module Type> specifies the type of module using its module identifier (e.g. S
Module specifies sensor). For details of the module identifiers see the appropriate module section
Details Page of this manual.
<Module Number> specifies the number of the module.
E.g. to display the module details page for sensor 3 type S3.
Welcome
Enter index.htm
Page
Modules
Enter Modules.htm
Page
Alarm Page Enter Alarms.htm
Diagnostic
Enter ^.htm
Page
10. Click OK.

11. Specify the foreground colour for the item by selecting the Foreground Colour check box, clicking Change
to display the Color dialogue box, clicking the required colour and then clicking OK to return to the Styling
dialogue box. If a foreground colour is not required, clear the Foreground Colour check box.
12. Specify the background ground colour for the item by selecting the Background Colour check box, clicking
Change to display the Color dialogue box, clicking the required colour and then clicking OK to return to
the Styling dialogue box. If a background colour is not required, clear the Background Colour check box.
13. In the Font Type box click the required font.
14. In the Font Size box click the required font size.
15. In the Width box enter the width of the object in pixels. To size the text to fit click Width.
16. If the object width has been specified specifically in the Text Align box, click the required text alignment.
You should ensure that the Width check box is cleared.
17. Specify the position on the page in the X and Y boxes.
18. Click OK.
9.4.41.1.4 Add a Directory Module to IQ2 and IQECO Strategy
To add a directory module to IQ2 and IQECO strategy:
3. In the Display and Directory View box right-click Root, or the directory module to which the new module
is to be added, and click Insert Directory. The Display and Directory dialogue box is displayed.
4. In the Label box enter the name for the directory module (Max 20-characters).
5. In the Pin Level box enter the PIN level required to access the module (1 to 99).
6. Click OK.

9.4.41.1.5 Add a Display Module to IQ2 and IQECO Strategy
To add a display module to IQ2 and IQECO strategy:
3. If necessary, add the directory module to which the display module is to be added.
4. In the Display Items box click the item that the display module is to access and drag it on onto the required
directory module in the Display and Directory View box, and release the mouse. If required, the items
displayed in the Display Items box can be limited to specific item types by clicking the appropriate button.
Option Description
Digin Displays all digital inputs in the strategy.
Driver Displays all drivers in the strategy.
>Knob Displays all knobs in the strategy.
Sensor Displays all sensors in the strategy.
All Displays all items in the strategy.
Switch Displays all switches in the strategy.
Time Schedule Displays all Time Schedules in the strategy.
5. Edit the module's parameters.
6. For Time Schedules, it is necessary to specify whether the display module displays the standard week, or the
current week.

9.4.41.2 Change the Order of Display Modules
To change the order of the display modules:
3. In the Display and Directory View box navigate down the display and directory module structure until the
display module that is to be moved is displayed.
4. Hold down the SHIFT key and click the display module that is to be moved.
5. Drag the module up/down to the required position.
7. Click OK.
9.4.41.3 Edit Modules
9.4.41.3.1 Edit a Directory Module in IQ3 or IQ4 Strategy
The parameters of directory modules in IQ3 and IQ4 strategy can be edited.
Note: Editing these modules changes the graphic display page that the module defines.
To edit a directory module in IQ3 or IQ4 strategy:
1. Display a strategy page for the controller containing the directory module.

3. Double click the module or right-click and click Edit Parameters. The Directory Item dialogue box is
displayed.
4. Edit the module's parameters as described in 'Specify the name of the module, PIN level, background colour,
backdrop, refresh rate, and size.
To specify the module's name:
 In the Title box enter the name of the directory. Maximum length 30-characters.
Note that if engineering directories that are to be navigated using an IQView then it is recommended that
the length of the label does not exceed 12-characters
To specify the module's PIN level:
 In the Pin level box enter the PIN level required to access the module (1 to 99).
To specify the module's background colour:
 Select the Colour check box. If a background colour is not required, clear the Colour check box.
Note that clearing the Colour check box will disable the Change button as it is not necessary to specify a
colour.
 Click Change. The Color dialogue box is displayed.

 Click the required colour.
To specify the module's backdrop:
 Click Change to specify the backdrop. The Select Backdrop dialogue box is displayed.
 Select the required backdrop from the list. If the required backdrop is not in the list click Add New
Backdrop and navigate to the required backdrop file, click it and then click OK.
Note that the use of backdrop files larger than 100k is not recommended. Backdrops bigger than 200k will
be prevented from being downloaded, and the total size used by all backdrops in the controller limited to
2Mb.
To specify the module's refresh rate:
 In the Refresh Rate box enter the required refresh rate in seconds. Range 0 to 60 seconds.
To specify the page size:
 In the Width box enter the width of the page in pixels, and in the Height box enter the height of the page
in pixels, or alternatively in the Page Size box click the page size.
5. Click OK.
9.4.41.3.2 Edit a Dynamic Display Module
To edit a dynamic display module:
display module that is to be set up is displayed.

4. Right-click the module and click Edit Parameters. The Display Item dialogue box is displayed.
5. In the Item Reference box enter the required item reference. This should be in the form shown below:
<Module><Module Parameter>
<Module> specifies the type of module using its module identifier and module number (e.g. S1 specifies
sensor 1). For details of the module identifier see the appropriate module section of this manual.
<Module Parameter> specifies the parameter within the module that is to be displayed (e.g. the value of a
sensor). The module parameter is specified using the parameter identifier (ID), and can be any parameter
available within the specified module. For details of the parameters available for each module and their
identifier see the appropriate module section of this manual.
If the module parameter is not specified, the default overview parameters for the module type will be
displayed. E.g. S1 would display the sensor label, value, and units. The table below lists the overview
parameters for each module type.
Module Overview Parameters

Alarm Destination Label
Alarm Group Label
Alarm Route Label and Status
Analogue Node label and value
Digital Byte Label and Value
Digital Input Label and State
Directory> label
Display Nothing
Driver Label and Value/Status
Function Label and Output Value
I/O Module Label
IC Comms Label and Source Value
Knob Label, Value, and Units
Logic Label and Output Value
Loop Label and Output Value
OSS Label and State
Plot Label
Sensor Label, Value, and Units
Sensor Type Label
Switch Label and Status
Time Module Label
Time Zone Label and Value

Module Overview Parameters

User Label and Status
Virtual CNC Label
Note: Although multiple parameters are used as the default overview parameters it is only possible to specify
single parameters.
Note: Only sensor, knob, switch, digital input, driver, and time schedule modules are supported by devices
other than IQ4 and IQ3 controllers. If other modules are specified they will only appear on GraphIQ pages,
and may cause problems with other devices such as IQView.
6. In the Pin level box enter the PIN level required to view/use the module (1 to 99), or use to set it.
7. Specify the foreground colour for the item by selecting the Foreground Colour check box, clicking Change
to display the Color dialogue box, clicking the required, colour and then clicking OK to return to the Styling
dialogue box. If a foreground colour is not required, clear the Foreground Colour check box.
8. Specify the colour used for the item when it is in an alarm by selecting InAlarm Colour check box, clicking
Change to display the Color dialogue box, clicking the required, colour and then clicking OK to return to
the Styling dialogue box. If a background colour is not required, clear the InAlarm Colour check box.
9. Specify the background ground colour for the item by selecting the Background Colour check box, clicking
Change to display the Color dialogue box, clicking the required, colour and then clicking OK to return to
the Styling dialogue box. If a background colour is not required, clear the Background Colour check box
10. In the Font Type box click the required font.
11. In the Font Size box click the required font size.
12. In the Width box enter the width of the object in pixels. To size the text to fit click Width.
13. If the object width has been specified specifically in the Text Align box, click the required text alignment.
You should ensure that the Width check box is cleared.
14. If a link to the items detail page is required select the Make a link to the item’s detail page check box.
15. Specify the position on the page in the X and Y boxes.
16. Click OK.
17. Click OK.

9.4.41.3.3 Edit a Static Display Module
The parameters of static display modules can be edited.
To edit static display modules:
1. Display a strategy page for the controller containing the display module.
3. Double click the module or right-click and click Edit Parameters. The Display Item dialogue box is
displayed.
4. Edit the parameters as required - see 'Add a Static Display Module'.

5. Click OK.

9.4.41.3.4 Edit a Directory Module in IQ2 or IQECO Strategy
To edit directory modules in IQ2 or IQECO strategy:
directory module that is to be edited is displayed.
4. Right-click the module that is to be edited, and click Edit Parameters the Display and Directory dialogue
box is displayed which enables the module's parameters to be specified.
5. Edit the parameters as required.

6. Click OK.

9.4.41.3.5 Edit a Display Module in IQ2 or IQECO Strategy
To edit a display module in IQ2 or IQECO strategy:
display module that is to be edited is displayed.
4. Right-click the module that is to be edited, and click Edit Parameters. A dialogue box is displayed which
enables the module's parameters to be specified. For most this is just the PIN level required to access the
module, but for Time Schedules it is also access to specify whether the module displays the time schedule's
standard or current week.
Dialogue box for editing most modules.
Dialogue box for editing time schedules.
5. Edit the parameters as required.

6. Click OK.
7. Click OK.

9.4.41.4 Delete a Display Module
To delete a display module:
display module that is to be is to be deleted is displayed.
4. Right-click the module and that is to be deleted, and click Delete Display Module. The module will be
deleted.
5. Click OK.

9.4.41.5 Delete a Directory Module
To delete a directory module:
directory module that is to be is to be deleted is displayed.
4. Right-click the module and that is to be deleted, and click Delete Directory. The module will be deleted.
5. Click OK.
Note: Every item below that directory will also be deleted.

9.4.41.6 Export the Display and Directory Module Structure
The display and directory module structure can be exported to a file (DnD file) that can be imported into another
controller. This saves time if you have several controllers with a similar display and directory module structure.
To export the display and directory module structure:
1. Display a strategy page for the controller from which the display and directory modules are to be exported.
3. Ensure the structure is as required.

4. Click Export. The Save as box is displayed.
displayed.
6. Click Save.

9.4.41.7 Import the Display and Directory Module Structure
It is possible to import a display and directory module structure from another controller. This saves time if you have
several controllers with a similar display and directory module structure.
When a structure is imported, it is added to any existing structure. All the necessary directory modules are created to
create the structure. Display modules are created provide the module about which they are providing information is
in the strategy.
To import the display and directory module structure:
1. Export the display and directory structure that is required.
2. Display a strategy page for the controller into which the display and directory modules are to be imported
4. If the imported display and directory module structure is to be appended to the existing structure, select the
Append Import check box. If this box is not selected the imported data will replace any existing display and
directory module structure.

5. Click Import the Open dialogue box is displayed.
6. In the file list click the file that is to be imported. To select a file stored in a different location, click the drive,
or folder in the Look in box that contains the file, double-click the folders in the folder list until file is
displayed.
7. Click Open.

9.4.42 Set up Graphical Display Pages
IQ4 and IQ3 controllers can be set up to serve schematic pages (graphical display pages) to web browsers. These
views can contain graphics, and live values from the controller itself. The set up of these views is done using the
Graphical Display Page Editor that is supplied and installed with IQSET. Details of using the Graphical Display Page
Editor are provided in the Graphical Display Page Editor Manual (TE200629).
To set up graphical display pages:
1. Create the required graphics files for the view's backdrop using a suitable graphics package and save it in the
required format (JPG, and GIF files) in the Backdrops sub-directory of the directory in which IQSET is
installed. It is recommended that JPG files be used.
If required backdrops uploaded from a controller can be imported.
Note: The use of backdrop files larger than 100k is not recommended. IQSET will prevent backdrops bigger
than 200k being downloaded and limit the total size used by all backdrops in the controller to 2Mb.
2. Set up the display and directory modules to create the required page structure. A directory module is a page
and a display module specifies an item on the page.
3. Display a strategy page for the controller for which the graphical display pages are to be setup.
5. Right-click the directory module that represents the page that is to be set up and click Edit Web Page. The
Graphical Display Page Editor is displayed with the selected page.
6. Right-click the page and click Properties. The Directory Item dialogue box is displayed.
7. Specify the page’s title, PIN level, background colour, backdrop, refresh rate, and size.

8. Click OK.
9. Position the objects on the page as required by moving them, or aligning them.
10. Edit the objects as required, by right-clicking the required object clicking Properties.
11. If there are other pages to set up navigate to the required page as described in the 'Access Other Pages' section
of the Graphical Display Page Editor Manual (TE200629) and set up that page in the same way as described
above.
12. Once all the pages are correctly set up click OK.
9.5 Add Graphics and Text to Strategy Pages
9.5.1 Add Graphics to a Strategy Page
Graphics such as circles, lines, and rectangles can be added to a strategy page to highlight an area of the strategy, or
to make the page easier to understand.
To add a circle to a strategy page:
1. Display the strategy page.
2. Click , or right-click anywhere on the page, and point to Draw and click Circle from the menu that is
displayed. The pointer changes to a .
3. Drag the pointer to define the size of the circle, and release the mouse button.
To add a line to a strategy page:
1. Display the required strategy page.
2. Click , or right-click anywhere on the page, point to Draw and click Line from the menu that is displayed.
The pointer changes to a .

3. Drag the pointer to define the length of the line, and release the mouse button.
4. If required add more lines to the page.
5. Once all the lines have added click .
To add a dotted line to a strategy page:
2. Click , or right-click anywhere on the page, point to Draw and click Dotted Line from the menu that is

3. Drag the pointer to define the length of the line, and release the mouse button.
4. If required add more lines to the page.
5. Once all the lines have added click .
To add a rectangle to a strategy page:
2. Click , or right-click anywhere on the page, point to Draw and click Rectangle from the menu that is

3. Drag the pointer to define the size of the rectangle, and release the mouse button.

9.5.2 Add Text to Strategy Pages
Text can be added to the strategy page to title the page, to make it more understandable, or to describe the functionality
of that part of the strategy in more detail. Once on the page, the text can be moved to the required position, or deleted
when it is no longer required. Any text added to the page will be printed out when the page is printed.
To add text to a strategy page:
1. Display the required strategy page
2. Click , or right-click anywhere on the page, point to Draw and click Text. The Display Text dialogue box
is displayed.
3. In the box enter the required text.

4. Click the appropriate Size option to specify the size of the text.
5. If the text is to be bold select the Bold check box.
7. Move the cursor to the position where the text is to be placed and click. The text is placed on the page.
9.5.3 Delete Text and Graphics from a Strategy Page
To delete a text and graphics from a strategy page:
1. Display the strategy page containing the text or graphic that is to be deleted.
2. Right-click the text/graphic that is to be deleted, and click Delete Module.
9.5.4 Move Text and Lines on a Strategy Page
To move a piece of text or line:
2. Drag the text/line to its new location, and release the mouse button.
9.6 Test the Strategy
Once the strategy has been created for a controller, it should be tested using IQSET's simulation mode which simulates
of an IQ4, IQ3 or IQECO strategy inside IQSET to ensure that it functions as expected. The strategy is in the controller
it should be tested thoroughly to ensure that it operates as expected. The exact tests will depend on the strategy. It is
recommended that all the inputs be exercised, and the output of the drivers monitored. It is also important to check
that the strategy deals with any alarm conditions correctly.
9.6.1 Test the Strategy Using Simulation Mode
Simulation mode simulates an IQ4, IQ3 or IQECO controller running the current strategy it is not available for IQ2
controllers. It is recommended that the strategy is tested to ensure that it functions as it expected. The exact tests will
depend on the strategy; however, it is recommended that all the inputs be exercised and the outputs of the drivers
monitored. It is also important to check that the strategy deals with any alarm conditions correctly.
IQECO strategies can be simulated. All IQ4 and IQ3 strategies including GraphIQ pages can be simulated with the
following limitations. Simulation mode is not available for IQ3 and IQ4 /XNC variants. There is no communications
with other devices (i.e. IC Comms of BACnet comms).
When in simulation mode it is possible to make changes to the strategy in the same way as the strategy was created
and see the effect on the strategy. These changes may include parameter changes, deletion, and addition of modules,
and modification, deletion, or addition of connections.
To test a strategy using simulation mode:
1. Open the IQSET project containing the required controller.
2. Display the strategy page that contains the required piece of strategy.

3. Click or on the Comms menu click Simulation Mode. IQSET will enter simulation mode using the
current strategy. Once in simulation mode the background of the strategy page changes to to indicate
simulation mode with both Live Edit and Live Values, and new site is added to the System View which
contains a single controller with address 20 on the local LAN.
4. You can now make changes to the strategy such as editing module parameters, adding/deleting modules,
linking the strategy; in the same way as for engineering IQ controllers and the effects can be seen in the
strategy. The value of module outputs highlighted in blue can be set manually.
To set the value manually:
 Double click the value. The Output Override dialogue box is displayed.
 Select the required option.
Option Description
Normal
Sets the value to operate normally i.e. no override and module is enabled.
Operation
Disable Module,
Disables the module and sets the value with the one in the Override Value box.
Set Output
Sets the module into override using the value in the Override Value box. The
Use Override
default is to the override value set in the strategy, changing it will change the value
Value
in the strategy.
Note: Depending on the selected value not all the options will be available.
 Click OK
GraphIQs pages can be viewed by right clicking device 20 on the 'simIQ' site in the System View and
selecting Web page.
The current page including the live values can be printed by right clicking the page pointing to Page, and
clicking Print Page. A sensor or plot can be graphed by right clicking the module on the strategy page and
selecting Graph from the displayed menu. Live edit can be turned off by clicking . When in simulation
mode with Live Values only the background of the strategy page changes to .
5. To exit simulation mode, click . If the modules are left overridden or disabled a warning will be given
enabling all modules to have their overrides removed, or the module to be re-enabled.

9.7 Download the Strategy

IQSET can download strategy to IQ controllers over a network, or to a directly connected controller. IQSET
downloads the strategy using the appropriate file format (IQ4, IQ3, IQe, IQ2, or LDF) for the type of controller.
To download to an IQ controller using IQSET:
1. Connect the PC running IQSET to the Trend network, or directly connect to the controller’s supervisor or
direct connection port using a suitable cable as described in the controller's documentation.
2. Display a strategy page from the controller whose strategy is to be downloaded.
Note: This means that if the strategy for one controller (controller A) is to be downloaded to another
controller (controller B) you must select a strategy page from controller A.
3. Click , or on the Comms menu click Download. The Connection Details dialogue box is displayed.
IQSET automatically inserts the LAN number, and address of the controller whose strategy file is to be
downloaded.
To select a different controller:

 Edit the Lan, and Node boxes to contain address of the required controller.
Caution if downloading to a different controller, ensure that its firmware version is the same or higher
than the controller for which the strategy was created.
To connect to a different site:
 In the Site Name box click the required site. If a different comms connection is to be used select the
required one from the Standard Comms box. If none of the standard connections are suitable the
connection can be specified by clicking Edit Connection Details. This displays the Connection Wizard
which enables the connection to be specified using the TUA Editor, or using the Connection Wizard.
To change the connection using the TUA Editor:
 Click Edit Connection details. The Connection Wizard is displayed.
 Select the Launching TUA Editor option.
 Click Next>. The TUA Editor Window is displayed.
 Use the TUA Editor to specify the connection.
To change the connection using the Connection Wizard:
 Select the Launching Site Connection Wizard (Recommended) option.
 Click Next>. The wizard changes.
 Specify the connection as required.
Note: The connection specified here will only be used for that site; it will not be added to the list of standard
comms connections.

4. If connected directly to a controller, or using a local supervisor port that does not provide network access
5. If the controller has security enabled specify the password that will authorise the download.
IQ4 and IQ3 controllers:
 In the User Name box enter the username.
 In the Password box enter the matching password.
 For v1.3 or greater controllers in the Pin box enter the PIN.
Pre IQ3 and IQECO controllers:
 In the Pin box enter the PIN.
6. Click OK. IQSET will attempt to communicate with the controller. If connecting to a vCNC operating in
'Secure' mode you will be prompted for the user name and password of a CNC User module in the device.
For other scenarios IQSET may prompt for other information or display a message before allowing the
connection - see Connect to the site.
 IQSET will check that the identifier and controller address specified match the one to which IQSET is
connecting. If they don’t match a dialogue box asking if you want to continue is displayed. Click OK to
continue, or Cancel to cancel.
 IQSET will check that the controller's time is within one minute of the PC time if there is a difference.
If there is a difference a dialogue box asking if you want to set the controller's time to match the PC is
displayed. Click Yes to adjust the time or No to leave the controller's time unchanged.
The File Download dialogue box is displayed.
Note that the appearance of this dialogue box is different for different types of controller.

7. The download file is automatically determined by the address of the controller but can be changed if required.
If is displayed the download file cannot be located check the file exists, and is specified correctly.
To specify the download file:
 Click Change or . The Open dialogue box is displayed.
 Click the required file in the list. To select a different location, click the drive, or folder in the Look in
box, and double-click the folders in the folder list to select the required directory.
 Click Open.
 Click Open.

8. To force the use of IQF protocol select Use IQ Lan (not FTP>).
Note: Normally this should not be selected, the appropriate protocol is automatically selected. It should only
be checked if you want to force the use of IQF When selected the Backdrops, Language Files, and XNC File
boxes are greyed out.
9. Specify whether the strategy file is to be downloaded by selecting the Strategy File check box.
10. If downloading to IQ4 or IQ3 controllers specify whether the backdrop files required for the Graphical
Display Pages are downloaded by selecting the Backdrops check box.
Note: Backdrop files cannot be downloaded using the current loop. The use of backdrop files larger than
100k is not recommended. Backdrops bigger than 200k will be prevented from being downloaded, the total
size used by all backdrops in the controller limited to 2Mb.
11. If downloading to IQ4 v3.60 or greater controllers specify how users configured in IQSET and existing users
in the controller are handled by selecting the required option in the User Merge Option list.
Merge and Maintain - Merges the User modules being downloaded by IQSET with those already present
in the IQ4, leaving the User modules in the IQ4 unchanged if there are any duplicates (same user name and
type).
Replace All - Deletes all User modules in the IQ4 and replaces them with the User modules downloaded by
IQSET.
Merge and Overwrite - Merges all User modules downloaded by IQSET with those in the IQ4, overwriting
duplicate modules (same user name and type) in the IQ and leaving other User modules in the IQ4 unchanged.
Ignore - Ignores any User modules defined in IQSET leaving those in the IQ4 unchanged.
12. If downloading to IQ4 or IQ3 controllers with version 1.1 firmware or greater specify whether the language
files used for the display of web pages and alarms are downloaded by selecting the Language Files check
box.
Note: Language files cannot be downloaded using the current loop.
13. If downloading to IQ3 controllers with version 1.3 firmware or greater with XNC functionality enabled
specify whether the TCL program (.XNC file) is to be downloaded by selecting the XNC File(s) check box.
Note: The XNC file cannot be downloaded using the current loop.
14. If downloading to IQ1 and IQ2 version <= 2.0 controllers the Send IQL and Send LDF options are displayed
select the format of the strategy file that is to be downloaded to those controllers.
15. If downloading to IQ3 controllers or IQ4 controllers specify whether the network configuration (Trend Mode
and Lan label parameters) are to be downloaded by selecting the NC Configuration check box. The format
of the name of the strategy file being downloaded must be LXXXnXXX this allows IQSET to locate the
correct network configuration file (NCF) for the controller.
16. If downloading to IQ3 controllers or IQ4 controllers specify whether the network modules in the strategy are
to be downloaded by selecting the Network Modules check box. The format of the name of the strategy file
being downloaded must be LXXXnXXX this allows IQSET to locate the correct network configuration file
(NCF) for the controller.
Note: To download all the network module parameters both the NC Configuration and Network Modules
check boxes must be selected.
17. Specify whether the window is to be closed when the download is complete by selecting the Close this
dialogue box when download completes check box.
18. Click Start to begin the download. The progress is indicated at the bottom to the dialogue box. Clicking Stop
will stop the download. Once the download is complete the text 'Download Complete' is displayed at the
bottom of the dialogue box. If the download fails, or is stopped, the Start button will change to Retry,
clicking Retry; will attempt the download again.
If the Start button is greyed out, the specified file does not exit, and a different file must be specified as
described in step (9).
If IQSET is directly connected controller, the LAN, and Node settings are ignored, and the strategy will be
sent to the controller to which IQSET is connected. However, if it is connected to an IQ2 controller whose
supervisor port has been set up to allow communication over the network, the LAN, and Node settings will
be used, and the strategy downloaded to the specified controller over the network.

9.8 Issue Project Documentation

Once the project is complete it is necessary to issue the project documentation. This involves defining the strategy
issue for each device, printing the project overview, and printing out the project documentation for each controller in
the project.
9.8.1 Define a Strategy's Issue
Details about the strategy for a controller can be kept. They describe the current issue, and enable a description of the
changes made since the previous version to be recorded. These details are included on the strategy pages for the device
when they are printed out.
To add a new issue:
1. Display a strategy page for the controller for which issue details are to be specified.
2. On the Device menu click Issue Details. The Drawing Issue dialogue box is displayed.
3. Click New.
4. In the PCN/Details box enter details about the issue.
5. In the Pages Affected box enter the numbers of the strategy pages that have been changed since the last
issue.
6. In the Date Approved box enter the approval date.
7. In the Approved box enter the name of the person who approved the strategy.
8. Click OK.
To delete the previous issue details:
1. Display a strategy page for the controller for which issue details are to be deleted.
2. Right-click the page and click Issue Details, or on the Device menu click Issue Details. The Drawing Issue
3. Click Delete Last.
4. Click OK.

9.8.2 Specify the Notes Printed on the Front Page
The notes printed on the front page of the printout can be defined.
To define the notes printed on the front page:
1. Display a strategy page for the controller for which the notes are to be specified.
2. Right-click the page and point to Device and click Notes, or on the Device menu click Notes. The Notes
3. In the box enter the required notes.

4. Click OK.
9.8.3 Print Project Overview
The project overview provides an overview of all the controllers in the project. It lists the LAN number, address,
device type name, identifier, version and serial number/MAC address of each controller as well as the issue and
revision number of the strategy. The project name, number, details, client, site name, and site GUID are also printed.
The project overview can be exported to a Microsoft Excel file.
To print the project overview:
1. Display the Project View
with a .
On the Project menu point to Overview and click Print Overview. The Print dialogue box is displayed.
3. In the Number of copies box enter the number of copies required.

4. Click OK.

9.8.4 Print Project Documentation
IQSET enables the strategy pages for each controller to be printed out. It is possible to print out all the pages for a
controller, or selected controllers. IQSET also provides several tables for each controller, which specify items such as
the sequence table etc. that do not appear on the strategy pages which can also be printed out.
To print project documentation:
1. Display any strategy page for the controller whose project documentation is to be printed.
If the project documentation is to be printed for more than one controller display the Project View and In
the Device View click the next to the required controllers. IQSET will indicate the selected controllers with
a .
2. On the Project menu click Project Print. This displays the Print dialogue box.
3. In the Name box click the required printer. Clicking Properties enables the printer properties to be adjusted.
IQSET will default to the Windows default printer, if a different printer is to always be used, it can be
specified as the default printer for IQSET.
4. In the Print what area specify what is to be printed by selecting the appropriate check box. To select all
options click Select All.
5. In the Print range area click the appropriate option to specify the range of pages that are to be printed.
6. In the Order box click the appropriate option to specify if all, odd, or even pages in the range are to be
printed.
7. In the Number of copies box enter the number of copies required.
8. Click OK.
Tip: clicking will automatically print all the project documentation for the selected controller.

9.9 Backup the Project

Once the project is complete, it is recommended that all the files for a project be backed up and stored in a safe place
(e.g. firesafe). The entire contents of a project can be exported to a single SET.ZIP file, this enables a project to be
backed up, or moved between computers. Once a project has been backed up in this way it can be restored by importing
the project. It is advisable to make backups of the project as part of your normal working practice to prevent data
being lost.
To export a project:
2. When the SET dialogue box is displayed click Export Project. The Project Export (ZIP) dialogue box is
displayed.
3. In the Project box click the project that is to be exported from the list.
4. In the Destination box enter the destination of the zip file. Clicking on Browse displays the Browse for
Folder dialogue box, which allows the destination to be specified by viewing the directory structure on the
PC. To locate the required directory, click the directory, and then click OK to return to the Project Export
(ZIP) dialogue box.
5. To exclude all BAK file from the backup select the Exclude Backup Files check box.
6. Click OK. The project will be exported to a zip file named <Project Name>.Set.zip. A dialogue box is
displayed indicating the progress of the export. When the process is complete, another dialogue box is
displayed.
7. Click OK.
Note: It is possible to export a project a project while IQSET is running by displaying the Project View, and on the
File menu click Open/New Project to display the SET dialogue box.


IQ Interfacing
10 IQ INTERFACING
IQ interfacing (/INT) is an optional feature that enables easy integration of Serial (RS485)and IP MODBUS devices
to the IQ4 and M-bus for v4.30 or greater, enabling the IQ4 to read and write values directly. Standard strategy blocks,
available in IQSET, allow easy strategy configuration using drag & drop for common meters and VSDs.
For each device, there are two strategy blocks, one labelled 'Energy Only' the other just the name of the meter. The
'Energy Only' strategy block only obtain the meter’s energy reading. The other strategy block reads the most
commonly used parameters.
If the required device is not available as a strategy block, or the block does not completely suit your requirements it
is easy to create strategy to interface with it by:
 Adding and configuring an interface network module.
 Adding and configuring a Modbus Interface module.
To use the IQ interfacing strategy blocks:
1. Ensure the IQ4 that is to be used has the IQ interfacing feature licenced.
2. Create the controller in IQSET. Ensure that the firmware variant is set to 4.2 or greater, and the IQ
Interfacing option selected.
3. Add a Modbus Serial, Modbus IP or M-bus Interface network module for the communications port that is to
be used by the interface and configure it as necessary to enable communications with the device (e.g. Baud
Rate). Refer the device documentation for details.
Note: Only one interface network module can be connected to a physical port. Therefore all devices
connected to that port must be capable of operating with the same network settings, e.g. baud rate.
Note: The RS485, RS232 ports cannot be used for XNC, MS/TP, or MODBUS at the same time.

IQ Interfacing
4. Drag the strategy block for the required device from the Strategy Library onto a strategy page. The Strategy
Block Questions and Answers dialogue box will be displayed.
 Specify the network module, the one added above

 Enter the answer to the other questions in the appropriate boxes.
The result of the text replacement for the selected question will be shown at the bottom of the dialogue
box. Items that the answer will cause to be truncated will be indicated in red text, this enables you to
adjust the answers to the question appropriately.
 Click OK.
Note: Clicking Preview will display all items in the that contain placeholder text.
6. Locate the Modbus or M-bus Interface module for the device and ensure the Address is set to the address of
the device.
7. If there are parameters and functionality in the strategy block that are not required, you can delete the
unwanted strategy, and, if required, save it your own strategy block.

Comparing Strategies
11 COMPARING STRATEGIES
IQSET enables strategies to be uploaded from IQ controllers and compared with the strategy held by IQSET. The
compare process will compare any module parameter that can be configured in the IQSET strategy with the strategy
in the controller. IQSET can either compare a single strategy, or multiple strategies.
11.1 Compare Single Strategies
IQSET enables the strategy held in a project for an IQ controller to be compared with a data file uploaded from a
controller.
A tab delimited file (named LxxxNyyy.rep, where xxx = LAN number, and yyy = controller number) is produced
listing any differences between the strategy in the project, and the chosen file. If required, IQSET can update the
strategy in the project to make it the same as the file.
Note: It is only possible to compare a SCN file with a pre IQ3 controller with firmware below version 2.0, and to
compare an IQF file with a pre IQ3 controller with firmware of version 2.0 or above.
If required, the strategies of several controllers can be compared with the appropriate uploaded file.
To compare the strategy for a controller:
1. Upload the strategy from the required controller. For IQ4 controllers the file must be uploaded as an IQ4 file.
For IQ3 controllers the file must be uploaded as an IQ3 file For IQECO controllers the files the file must be
uploaded as an IQe file. For pre IQ3 controllers with version 2.0 firmware or greater, the file must be
uploaded as an IQ2 file. For pre IQ3 controllers with older firmware (less than v2.0) the file must be uploaded
in SCN format.
2. Display a strategy page for the controller for which the strategy is to be compared.
3. On the File menu point to Compare and. The Open dialogue box is displayed.
4. Select the required file type in the box on the right.

5. Navigate to the directory containing the required file.
6. Click the required file, and click Open. The Compare and Update dialogue box is displayed.

7. Click the required options. Update Database will cause IQSET to update its strategy to be the same as the
chosen file. Backup Database ensures that IQSET makes a copy of the existing strategy before updating it
allowing the strategy to be restored if the updated strategy is not suitable. Print Report File causes IQSET
to print out a report of the differences between the strategies on the specified printer.
Note that if none of the options are selected, a .rep file listing the difference between the strategies is created
in the directory for the LAN containing the device.
8. If the module positions are to be updated select the Update Module Positions check box. When selected,
modules will be relocated using the p, x, y values in the uploaded file. If unchecked unplaced modules with
p, x and y values will be placed onto the correct page, and all other modules will appear in the 'Unplaced
Modules' list. If a module already exists on a page its position will not change. Modules that do not exist in
the compared file will not be removed and remain as they are. Compare will report all module position
changes.
9. Click Start.
If Update Database is selected, IQSET will modify the strategy pages and linking to reflect the changes.
Modules already in the IQSET project (on a strategy page) are correctly positioned and linked as are modules
whose x, y, and page parameters have been specified (IQ4, IQ3 controllers and IQ2 firmware version 2.1 and
above). Modules not in the IQSET project (not on a strategy page) that do not have the x, y, and page
parameters will not be placed on a page, but will be added to the strategy as unplaced modules. These modules
are used in the strategy, and linked to other modules, but they do not appear on any of the strategy pages. It
is necessary to add any unplaced modules to a page and make any links manually. If there are differences
between NTD modules in the controller, and those in the IQSET database the NTD List for this Controller
dialogue box is displayed, this allows you to resolve any differences.
If a module is to be linked to a module on a different page, the connective will not be added by IQSET; this
must be done manually using the unplaced modules list.

11.2 Compare Multiple Strategies

IQSET enables a batch comparison of strategies. The strategy held in a project for each selected controller is compared
with the data file, or SCN file associated with each controller.
A tab delimited file (named LxxxNyyy.rep, where xxx = LAN number, and yyy = controller number) is produced for
each selected controller listing any differences between the strategy in the project, and the associated file. If required,
IQSET can update the strategy in the project to make it the same as the file.
To compare the strategy held by set for a controller with a file other than the one associated with it, using IQSET’s
single file comparison.
To compare multiple strategies:
1. Upload the strategy from the required controllers. It is possible to upload from more that on controller at a
time. For IQ4 controllers the file must be uploaded as an IQ4 file. For IQ3 controllers the file must be
uploaded as an IQ3 file. For IQECO controllers the files the file must be uploaded as an IQe file. For pre IQ3
controllers with version 2.0 firmware or greater, the file must be uploaded as an IQ2 file. For pre IQ3
controllers with older firmware (less than v2.0) the file must be uploaded in SCN format.
Note: The file must be in the Upload sub-directory of the project’s directory in the base project directory.
The file name must be in the format L<LAN Number>n<controller address>. E.g. the file for controller 25
on LAN 24 would be L024n025.IQ2. If the file is uploaded using IQSET, it will automatically be placed in
the correct place, and be named appropriately.
3. In the Device View click the next to each controller for which the strategy is to be compared. IQSET will
indicate the selected controllers with a .
4. On the Project menu click Project Compare. This displays a message box.
5. Click OK. The Compare and Update dialogue box is displayed.
6. Click the required options. Update Database will cause IQSET to update its strategy to be the same as the
chosen file. Backup Database ensures that IQSET makes a copy of the existing strategy before updating it
allowing the strategy to be restored if the updated strategy is not suitable. Print Report File causes IQSET
to print out a report of the differences between the strategies on the specified printer.
Note: If none of the options are selected, a .rep file listing the difference between the strategies is created in
the directory for the LAN containing the device.
7. If the module positions are to be updated select the Update Module Positions check box. When selected,
modules will be relocated using the p, x, y values in the uploaded file. If unchecked unplaced modules with
p, x and y values will be placed onto the correct page and all other modules will appear in the 'Unplaced
Modules' list. If a module already exists on a page its position will not change. Modules that do not exist in
the compared file will not be removed and remain as they are. Compare will report all module position
changes.
8. Click Start. The comparison will be performed. If IQSET cannot complete the comparison for one of the
selected controllers, a will be placed next to it in the Device View and a message box explaining the problem
displayed.
If the Update Database is selected, IQSET will modify the strategy pages and linking to reflect the changes.
Modules that have been added to the strategy will only be correctly positioned on the page, and linked if the
x, y, and page parameters have been specified (IQ4, IQ3 controllers and IQ2 firmware version 2.1 and above).
Modules that do not have the x, y, and page parameters will not be placed on a page, but will be added to the
strategy as unplaced modules. These modules are used in the strategy, and linked to other modules, but they
do not appear on any of the strategy pages. It is necessary to add any unplaced modules to a page and make
any links manually. If the strategy contains NTD modules there may be differences between NTD modules
in the controller, and those in the IQSET database, it is recommended that you view the NTD List for each
IQ3/BACnet controller that was compared and resolve any differences.

11.3 Resolve NTD Differences
For IQ4/BACnet and IQ3/BACnet and IQECO v2.0 or greater controllers the NTD List for the controller enables
differences between NTD modules in the controller, and the NTD modules in the IQSET database which can occur
when a compare has been carried out to be identified, and resolved.
To resolve NTD differences:
1. If a compare has been performed on a single strategy the NTD List for this controller will be displayed. If
multiple strategies have been compared it is necessary to display the dialogue box by right-clicking a strategy,
pointing to IC Comms and clicking Show NTD List.
Differences between the NTD modules in the controller and the NTD modules in the IQSET database are
indicated by different colours. Selecting the Show Mismatches Only check box will change the display so
that only NTD modules for which there are problems are displayed.
Colour Description
There are differences between the NTD modules in the controller and the NTD modules in the
Red
IQSET database.
Blue The NTD module is missing from controller.
2. Resolve any differences between the NTD modules in the controller, and the NTD modules in the IQSET
database. There 2 types of differences, missing modules, and modules with differences.
Missing modules:
 In the Controller List box click on the NTD module that is to be resolved. The details about the module
are displayed at the bottom of Controller NTD List dialogue box. The information from the controller
is displayed on the left (marked Strategy), and the information stored in the IQSET database is on the
right (marked Project).
 Review all the information and decide which is to be used. To use the information from the controller
click Copy to Project >>>>, to use the information from the IQSET database <<<< Copy to Strategy.

Modules with differences:
 In the Controller List box click on the NTD module that is to be resolved. The details about the module
are displayed at the bottom of Controller NTD List dialogue box. The information from the controller
is displayed on the left (marked Strategy), and the information stored in the IQSET database is on the
right (marked Project).
 Review all the information and decide which is to be used. To use the information from the controller
click Copy to Project >>>>, to use the information from the IQSET database <<<< Copy to Strategy.
3. Click OK.
For IQ3 and IQ4 controllers the changes can be sent to the affected controllers.
To send the changes to the controllers:
2. In the Device View right-click the NTD that has been changed, and click Device Details. The NTD
Parameters dialogue box is displayed.

4. Click OK and Send to IQ3's. The Select Site Connection dialogue box is displayed.
5. In the Site Connection box select the required site.

6. In the Pin box enter the PIN required to authorise the change in the controller.
8. Click OK.

Note: The dialogue box only shows the NTD List for the selected controller, therefore if multiple strategies have been
compared this process should be carried out for each controller.
11.4 Restore a Strategy
When IQSET compares a strategy with a data file and updates its strategy, a backup of the existing file can be
requested. This backup can be used to return the strategy to its original state before the compare was performed, if the
changes made during the compare process cause a problem.
To restore a strategy:
1. Run Windows Explorer, and goto the Set Projects directory.
2. Goto the subdirectory for the project, and then open the required LAN subdirectory.
3. Delete the .IQ file for the controller whose strategy was backed up.
4. Rename the .BAK file for the controller to .IQ.

Update a Project
12 UPDATE A PROJECT
The project update feature enables a project to be updated with information from strategy files (IQ4, IQ3, IQe, IQ2,
or SCN) uploaded for the site. It combines IQSET's import and compare functions. If a strategy file exists in the upload
directory, but there is no matching controller in the project it will be imported into the project (not SCN files), and if
the there is a matching controller in the project the uploaded file is compared with the strategy information in the
IQSET database.
A tab delimited file (named LxxxNyyy.rep, where xxx = LAN number, and yyy = controller number) is produced
listing any differences between the strategy in the project, and the chosen file. If required, IQSET can update the
strategy in the project to make it the same as the file.
Note: It is only possible to compare a SCN file with a pre IQ3 controller with firmware below version 2.0, and to
compare an IQF file with a pre IQ3 controller with firmware of version 2.0 or above.
To update a project:
1. Upload the strategy files from the controllers that are required in the project.
3. On the Project menu click Project Update. The Project Update dialogue box is displayed.
The dialogue box contains a list of the files available in the project's upload directory and the options available
for each one (import or compare). For compare the firmware version is also checked and an error message
displayed if the uploaded file's firmware version is greater than the firmware version of the strategy in
IQSET's database. The directory in which IQSET looks for the uploaded files can be changed.
To specify the directory:
 Click Change. The Browse For Folder dialogue box is displayed.
 Click the required folder in the list.

Update a Project
 Click OK.
4. In the Select column check the check box next to the files that are to be included in the update. Any files
shown with an error message will not be compared even if they are selected. To select all files right click the
lists and select Select All from the displayed menu. To unselect all, right click the list and select Unselect
All from the displayed menu.
5. Specify the required update options by selecting the required check boxes in the top right of the dialogue
box. If none of the options are selected, a .rep file listing the difference between the strategies is created in
the directory for the LAN containing the device.
Option Description
>Update
Causes IQSET to update its strategy to be the same as the chosen file.
Database
Backup Ensures that IQSET makes a copy of the existing strategy before updating it allowing the
Database strategy to be restored if the updated strategy is not suitable.
Print Report Causes IQSET to print out a report of the differences between the strategies on the specified
File printer.
When selected, modules will be relocated using the p, x, y values in the uploaded file. If
Update unchecked unplaced modules with p, x and y values will be placed onto the correct page and
Module all other modules will appear in the 'Unplaced Modules' list. If a module already exists on a
Positions page, then its position will not change. Modules that do not exist in the compared file will not
be removed and remain as they are. Compare will report all module position changes.
6. Click OK. The project will be updated accordingly.
If the Update Database is selected, IQSET will modify the strategy pages and linking to reflect the changes.
Modules that have been added to the strategy will only be correctly positioned on the page, and linked if the
x, y, and page parameters have been specified (IQ3 controllers and IQ2 firmware version 2.1 and above).
Modules that do not have the x, y, and page parameters will not be placed on a page, but will be added to the
strategy as unplaced modules. These modules are used in the strategy, and linked to other modules, but they
do not appear on any of the strategy pages. It is necessary to add any unplaced modules to a page and make
any links manually. If the strategy contains NTD modules there may be differences between NTD modules
in the controller, and those in the IQSET database, it is recommended that you view the NTD List for each
/BACnet controller that was compared and resolve any differences.

Commissioning with Live Values
13 COMMISSIONING WITH LIVE VALUES

IQSET enables you to connect to an IQ controller and display the live output values on the strategy page. In this mode,
the values of knobs and switches can be adjusted by editing the modules and changing the output values. The new
values are then sent to the controller and the results can be seen on the strategy page. Modules in an alarm condition
are displayed in yellow.
This feature can be used on more than one controller at a time. This is useful for checking ic comms across the system.
The IQ SET strategy and the controller strategy must be identical or some of the values may not make sense. IQ SET
will check to see if there are any differences, and if necessary display a warning message.
For IQ3, IQ4 and IQECO controllers IQSET will also perform a background compare which provides a detailed
comparison between the strategy in IQSET’s database, and the strategy running in the controller. IQSET checks that
the module parameters and values in the controller are the same as those in IQSET for each module on the page.
Modules for which the data does not match are highlighted in red, those for which the data is the same are highlighted
in green.
Warning when using this feature the controller will be controlling any HVAC equipment to which it is connected;
using incorrect strategy may result in damage to HVAC equipment or injury to people.
To commission a controller with live values:
2. Ensure that the strategy held by IQSET (displayed on the page) and that in the controller are identical by
downloading the strategy first, or running a compare.
4. Click or on the Comms menu click Live Values. The Connection Details dialogue box is displayed.
IQSET automatically inserts the LAN number, and address of the controller for which the strategy page is
displayed, and uses the current site, and the connection associated with it.
5. To select a different controller, edit the LAN, and Node boxes to contain address of the required controller.
6. To connect to a different site in the Site Name box click the required site.
7. The connection that is used will be the one specified for the currently selected site, if a different connection
is to be used in the Standard Comms box click the required connection. If none of the standard connections
are suitable the connection can be specified by clicking Edit Connection Details. This displays the
Connection Wizard which enables the connection to be specified using the TUA Editor or the Connection
Wizard.
To change the site's connection using the TUA Editor:

Commissioning with Live Values
To change the site's connection using the Connection Wizard:
comms connections.
9. If the controller has security enabled specify the password that will authorise any changes.
If an IQ4 or IQ3 controller has security enabled, it will request a username and password. The username and
password is sent must match with one in the controller and have a high enough level of authority.
If an IQ controller has PIN protection enabled, it will request a PIN. The PIN that is sent must match with
one in the controller that has a PIN Level of 99 or greater
10. In the Refresh Int box enter the required refresh rate for the values.
11. Click OK. If enabled IQSET will check to see that the identifier and controller address specified match the
one to which IQSET is connecting. If they don’t match a dialogue box asking if you want to continue is
displayed.
12. Click OK to continue, or Cancel to cancel. If OK was selected the output values from the controller will be
displayed on the strategy pages. The current page including the live values can be printed by right clicking
the page pointing to Page, and clicking Print Page.
IQSET can annunciate any value on the screen, click and place the cursor over the required value. A sensor
or plot can be graphed by right clicking the module on the strategy page and selecting Graph from the
displayed menu.
Changes can be made to knob and switch values by double clicking on the module to display Module
Parameters dialogue box and for knobs entering the required value in the Value box, and for switches
clicking the ON or OFF button to toggle the status, and then clicking OK to send the value directly to the
controller. If a change is made to any other parameter, or an attempt is made to add a new module a dialogue
box is displayed asking if you want to enable Live Edit or Live Adjustment for IQECOs. Clicking Yes will
start Live Edit or Live Adjustment (IQECOs) and send the changes to the controller. Selecting No causes
IQSET to remain in Live Values mode and the message will not appear again during the current Live Values
session.
For IQ4, IQ3, and IQeco controllers a dialogue box that provides a comparison between the value of
parameters in the IQ SET project and those in the controller can be displayed by right clicking on the module
and selecting Module Properties - compare. If required changes can be made to the values of the parameters
in the controller. It is not possible to modify the values in the IQ SET project.
13. To stop live values, click .

Live Editing
14 LIVE EDITING
14.1 Live Editing Mode
IQSET enables a strategy to be modified in the controller (not IQECOs) at the same time as the drawing on the strategy
page is modified.
The IQSET Live Edit feature not only enables knobs and switches to be changed like Live Values, but also enables
any strategy changes to be made. The changes made to the strategy page are then downloaded to the controller. These
changes may include parameter changes, deletion, and addition of modules, and modification, deletion, or addition of
connections.
To see the effects of the strategy changes on the strategy page the live value commissioning feature may also be
selected. Using these two features together enables any strategy design faults to be detected, modified, and the effects
of the changes observed.
The IQSET strategy and the controller strategy must be identical or some of the values may not make sense. IQSET
For IQ3 and IQ4 controllers IQSET will also perform a background compare which provides a detailed comparison
between the strategy in IQSET’s database, and the strategy running in the controller. IQSET checks that the module
parameters and values in the controller are the same as those in IQSET for each module on the page. Modules for
which the data does not match are highlighted in red, those for which the data is the same are highlighted in green.
Note: When using Live Edit on Time Schedule modules in IQ4 controllers with v3.40 and v3.41 firmware message
warning that parameter mismatches have been found with at least one module on the page. If this error occurs upgrade
the controller's firmware to the latest version.
To use live editing mode:
1. Open the project containing the required controller.
3. Ensure that there is a comms connection available that will enable IQSET to communicate with the controller.
5. Click or on the Comms menu click Live Edit. The Connection Details dialogue box is displayed. IQSET
automatically inserts the LAN number, and address of the controller for which the strategy page is displayed,
and uses the current site, and the connection associated with it.

 Edit the LAN, and Node boxes to contain address of the required controller.

Live Editing
 In the Site Name box click the required site. The connection that is used will be the one specified for the
currently selected site, if a different connection is to be used in the Standard Comms box click the
required connection. If none of the standard connections are suitable the connection can be specified by
clicking Edit Connection Details. This displays the Connection Wizard which enables the connection
to be specified using the TUA Editor or the Connection Wizard.
comms connections.
7. If the controller has security enabled specify the password that will authorise the any changes.
Pre IQ3 controllers:
If an IQ controller has PIN protection enabled, it will request a PIN. The PIN that is sent must match with
one in the controller that has a PIN Level of 99 or greater.
IQSET will check that the identifier and controller address specified match the one to which IQSET is
continue, or Cancel to cancel. When in live edit the background of the strategy page changes to .
Note: If the PIN specified is incorrect a message is displayed to indicate that you will be unable to make any
changed.
10. You can now make changes to the strategy such as editing module parameters, adding/deleting modules,
linking the strategy; in the same way as for engineering IQ controllers and they will be sent directly to the
controller. When in live edit the background colour changes to light blue. If required live values can be
displayed while in live edit mode by clicking . When in live edit mode with live values displayed the value
of module outputs highlighted in blue can be set manually.

Live Editing
To set the value manually:
 Double click the value. The Output Override dialogue box is displayed.
 Select the required option.
Option Description
Normal
Sets the value to operate normally i.e. no override and module is enabled.
Operation
Disable Module,
Disables the module and sets the value to the one in the Override Value box.
Set Output
Sets the module into override using the value in the Override Value box. The
Use Override
default is to the override value set in the strategy, changing it will change the value
Value
in the strategy.
Note: Depending on the selected value not all the options will be available.
 Click OK.
clicking Print Page. A sensor or plot can be graphed by right clicking the module on the strategy page and
selecting Graph from the displayed menu.
For IQ4, IQ3, and IQeco controllers a dialogue box that provides a comparison between the value of
parameters in the IQ SET project and those in the controller can be displayed by right clicking on the module
and selecting Module Properties - compare. If required changes can be made to the values of the parameters
in the controller. It is not possible to modify the values in the IQ SET project.
To stop live editing click . If the modules are left overridden or disable a warning will be given enabling
all modules to have their overrides removed, or the module to be re-enabled.

Live Editing
14.2 Live Adjustment Mode

Live Adjustment Mode is only available of IQECO controllers. It enables module parameters in a controller to be
modified directly from the strategy page. The changes made to the strategy page are sent downloaded to the controller.
Note: It is not possible to move, link, add, or delete modules. Modules labels can only be changed on IQECO v2.0 or
greater controllers.
To see the effects of the strategy changes on the strategy page the live value commissioning feature may also be
selected. Using these two features together enables strategy design faults to be detected, modified, and the effects of
the changes observed.
The IQSET strategy and the controller strategy must be identical or some of the values may not make sense. IQSET
IQSET will also perform a background compare which provides a detailed comparison between the strategy in
IQSET’s database, and the strategy running in the controller. IQSET checks that the module parameters and values in
the controller are the same as those in IQSET for each module on the page. Modules for which the data does not match
are highlighted in red, those for which the data is the same are highlighted in green.
To use live adjustment mode:
3. Ensure that there is a comms connection available that will enable IQSET to communicate with the controller.
5. Click or on the Comms menu click Live Adjust. The Connection Details dialogue box is displayed.
displayed, and uses the current site, and the connection associated with it.

 In the Site Name box click the required site. The connection that is used will be the one specified for the
currently selected site, if a different connection is to be used in the Standard Comms box click the
required connection. If none of the standard connections are suitable the connection can be specified by
clicking Edit Connection Details. This displays the Connection Wizard which enables the connection
to be specified using the TUA Editor or the Connection Wizard.

Live Editing
comms connections.
7. If the controller has security enabled in the Pin box enter the PIN that is to be use to authorise any changes.
continue, or Cancel to cancel. When in live adjustment the background of the strategy page changes to
.
Note: If the PIN specified is incorrect a message is displayed to indicate that you will be unable to make any
changed.
10. You can now edit module parameters in the same way as for engineering IQ controllers and they will be sent
directly to the controller. If required live values can be displayed while in live adjustment mode by clicking
.
clicking Print Page. A sensor can be graphed by right clicking the module on the strategy page and selecting
Graph from the displayed menu.
A dialogue box that provides a comparison between the value of parameters in the project and those in the
controller can be displayed by right clicking on the module and selecting Module Properties - compare. If
required changes can be made to the values of the parameters in the controller. It is not possible to modify
the values in the project.
To stop live adjustments, click .

Live Editing

Export Strategy for Custom Ordering
15 EXPORT STRATEGY FOR CUSTOM ORDERING

IQSET enables a strategy created for an IQECO controller to be exported as a custom strategy that can, at additional
cost, be included in IQECO controllers shipped from the factory. Controllers shipped in this way are programmable
controllers. This facility is useful as it enables controllers to be supplied to site with the correct strategy already saving
time in set up and commissioning.
To export a strategy for custom ordering:
1. Create the strategy for the IQECO controller.
2. Download the strategy to a programmable IQECO controller.
3. Test the strategy to ensure that it is working as required.
Important: Ensure that the strategy has been fully tested and is working as required. Any errors in the strategy
cannot be corrected once the order has been placed.
4. Display a strategy page for the controller containing the strategy that is to be exported for custom ordering.
5. On the Strategy menu click Export for Custom Strategy Ordering. The Custom Strategy Export
6. Click Terms and Conditions. The Terms and Conditions dialogue box is displayed.
7. Read the terms and conditions carefully. You must agree to them to be able to place an order for IQECO
controllers with a custom strategy.
8. If you agree with the terms and conditions the select the I agree to the above terms and conditions check
box. To continue with the order, you must agree to the terms and conditions and select the check box.
9. Click OK to return to the Custom Strategy Export dialogue box. The Export Directory box is now enabled.
10. If required change the directory to which the strategy file is to be exported by clicking , selecting required
directory from the dialogue box that is displayed and clicking OK.
11. If you do not want to launch your email client with a pre-configured email clear the Launch Email Client
with attached file check box.
12. Click OK. The strategy file will be exported and if the Launch Email Client with attached file check box
is selected an email will be displayed.
Do not rename the file that is created as the file name is used as part of the order process to verify that the
strategy has not been changed.
13. Complete the email with detail of the required order including order number, and number of controllers
required.
14. Send the email.

Export Strategy for Custom Ordering

General Operations
16 GENERAL OPERATIONS
16.1 Add a Connective
Connectives allow links to be made between modules on different pages, modules on the same page (where linking to
the module would make the strategy hard to understand), or to nodes that have been defined as connectives- see 'Add
an Undefined Connective to a Node' for pre IQ3 controllers, and to the various alarm status information (e.g. the status
of a loop’s PV Fail alarm) for other controllers.
To add a connective:
1. Display the strategy page to which the connective is to be added.
2. Click , or right-click the page where the connective is to be placed, point to Other and click Connective.
The Connectives dialogue box is displayed listing all the modules currently in the strategy, and any nodes
that have been defined as connectives.
3. Click the module parameter, or node to which the connective is to point. If configuring an IQ4, IQ3 or IQECO
controller when you click a module or node any associated connectives will be displayed in the Associated
Connectives box. If required these can be selected instead. The list can be filtered by clicking the appropriate
button making it easier to find the required module.
Icon Description
All connectives
Knob connectives
Sensor connectives

General Operations
Icon Description
Switch connectives
System connectives
The list can also be filtered by label or module. To filter by label, enter the required label in the box below
the Label Filter button, and then click Label Filter. To filter by module, enter the required module in the
box below the Type Filter button, and then click Type Filter. E.g. enter L to find all connectives relating to
loop modules, or L1 to find all connectives relating to loop 1.
4. Once the required module parameter is selected, click Select. The cursor changes to a hand .
5. Move the cursor to the position where the connective is to be placed and click. The connective is placed on
the page.
Note: There is no need to set up the parameters for the connective because it is a link to a module, which has
already been defined.
6. Repeat steps (3) to (5) for any other connectives.
7. Click Exit.
16.2 Add a Connective to Alarm Status Information
For IQ4, IQ3 and IQECO controllers, links to the various alarm status information (e.g. the status of a loop’s PV Fail
alarm) can be made using connectives that are automatically created when the module is placed on the page.
To add a connective to alarm status information:
1. Display the strategy page containing the module to which the alarm status is to be linked.
2. Click , or right-click the page where the connective is to be placed, point to Other and click Connective.
The Connective dialogue box is displayed listing all the modules currently in the strategy, and any
connectives that are available.

General Operations
3. Click the module for which the alarm status is required. Any connectives associated with the module will be
displayed in the Associated Connectives box. The list can be filtered by clicking the appropriate button
making it easier to find the required module.
Icon Description
All connectives
Knob connectives
Sensor connectives
Switch connectives
System connectives
The list can also be filtered by label or module. To filter by label, enter the required label in the box below
box below the Type Filter button, and then click Type Filter. E.g. enter L to find all connectives relating to
loop modules, or L1 to find all connectives relating to loop 1.
4. In the Associated Connectives box click the connective that represents the required alarm status to highlight
it.
5. Once the required connective is selected, click Select. The cursor changes to a hand .
the page.
7. Click Exit.
16.3 Add a Connective to System Information
Links to various pieces of system information such as time, timing pulses, day of year, month of year etc. can be made
using connectives that are automatically created when the controller is added.
To add a connective to system information:
1. Display the strategy page containing the module to which the system information is to be linked.

General Operations
2. Click , or right-click the page where the connective is to be placed, and point to Other and click
Connective. The Connective dialogue box is displayed listing all the modules currently in the strategy, and
any connectives that are available.
3. Click to filter the list of connectives so that it only shows connectives to system information
4. Click the connective that represents the required alarm status to highlight it.
5. Once the required connective is selected, click Select. The cursor changes to a hand .
the page.
7. Click Exit.
16.4 Add a Module Using the Command Line Toolbar
The Command Line toolbar enables modules to be added to a strategy page.
To add a module using the Command Line toolbar:
1. Display the strategy page to which the module is to be added.
3. Click in the Command Line toolbar, press CTRL+M, or on the Tools menu click Command Line to move
4. Specify the module that is to be added in the following format:
<Module Type>#<Module Number>#<Sequence Step Number>
<Module Type> is one of the commands that specifies a type of module.
Module Command
ABS Function Module F24
Add Function Module F20
Adder/Scaler Function Module F8
Adjustment Knob Module KA
Alarm Destination Module ALARM DEST

General Operations
Module Command
Alarm Group Module ALARM GROUP
Alarm Route Module ALARM ROUTE
Analogue Driver Module D2
Analogue to Digital Function Module F18
Average Function Module F13
Binary Hysteresis Driver Module D5
Combination Logic Module G1
Comparator Function Module F15
Counter Logic Module G4
D to A Logic Module G8
Delay Logic Module G5
Digital Driver Module D1
Digital Input Module I
Divide Function Module F10
Enthalpy Function Module F16
External Digital Sensor Module S3
External Sensor Module S1
Fan Out Logic Module G7
Filter Function Module F1
Gate Function Module F14
Hours Run Logic Module G6
Hysteresis Band Function Module F17
Hysteresis Limits Function Module F21
Internal Digital Sensor Module S4
Internal Sensor Module S2
Knob Module K
Limit at Function Module F4
Limit to Function Module F5
Log Function Module F6
Lookup Function Module F19
Loop Module L
Maximum Function Module F12
Minimum Function Module F11
Multiply Function Module F9
Plot Module P
Power Function Module F23
Proximity Function Module F22
Raise/Lower Continuous Driver Module D7
Raise/Lower End Driver Module D4
Readback Logic Module G3
Rescale from Function Module F2
Rescale to Function Module F3
Schedule Module H
Square Root Function Module F7
Switch Module W
Time Proportional + O/R Driver Module D6

General Operations
Module Command
Time Proportional Driver Module D3
Time Schedule Module TZ
Timer Logic Module G2
TRIG Function Module F26
TRUNC Function Module F25
<Module Number> is an integer that specifies the number of the module, and <Sequence Step Number>
specifies the location of the module in the sequence table.
E.g.
F1#7#103
This command would place function module 7 on the page as a filter module, and assign it to sequence step
103.
It is not necessary to type all parts of the code e.g. to add a type 1 function module using the next module
number and sequence step type F1.
5. Press ENTER to add the module to the page.
16.5 Add a Strategy Page
IQSET stores the strategy on strategy pages. Each strategy page is sized to ensure that the pages can be printed out.
Pages should be added as they are required. When a strategy page is added, IQSET inserts a gap in the sequence table
to allow modules to be added to the previous page without affecting the positions in the sequence table of the modules
on the new page. The size of this gap can be specified. This gap only included when the page is added using the New
Page button ( ) or from the Project View NOT when it is inserted before another.
Information about when a strategy page was created or modified is automatically stored. Text information can also be
stored about the page; e.g. to describe the function of the strategy on the page.
To add a strategy page from the Project View:
2. In the Device View, select the controller to which the strategy page is to be added.
3. Right-click Strategy Pages and click Insert Page. The new page will be added to the list of pages in the
Project View.
To add a strategy page using the New Page button:
1. Display a strategy page containing strategy for the required controller.
2. Click . The new page will be displayed.
To insert a strategy page before another:
1. Display the strategy page before another page is to be inserted.
2. Click , or right-click the page and point to Page and then click Insert Page. The new page will be
displayed.
Note: When a page is inserted in this way a gap in NOT inserted in the sequence table.
16.6 Add a To Connective
To connectives provide visual indication on the strategy page that a module is providing an input to modules on other
pages. They indicate all the modules on other pages linked to the module to which they are connected. They should
be added to strategy pages to make the strategy drawings easier to understand.
Note: Adding a To connective does not link modules together; they provide a visual indication of existing links.
To add a To connective:
1. Display the strategy page that contains the module providing the input to modules on other pages.
2. Click , or right-click anywhere on the page and point to Other and click To Connective. The cursor
changes to a hand .
3. Move the cursor to the position where the connective is to be placed and click.
4. Click the parameter that provides an input (source) to modules on other pages. The cursor will change to a
when it is moved over a parameter that can be linked.

General Operations
5. Drag the mouse to the To connective, and release the mouse button. IQSET will display a green circle
when the cursor is in the right place.
16.7 Add an IQECO Display Device
IQECO v2.20 to 2.23 only. In order for values in the controller to be sent to the display from the strategy the display
device (I/O module 2) must be added to the strategy, and the strategy configured to make the required values available
in specific modules which are read by the display, and if appropriate written to. For details of the values that can be
shared between the controller and the display and the required location of values in the controller see the Wallbus
display's documentation.
If values from the display are to be read by the controller the display device (I/O module 2) must be added to the
strategy and the strategy configured to link the input channel of an external sensor to the appropriate output channel
on the display. For details of the values that can be read from the display see the display's documentation.
To add an IQECO display device:
1. Display a strategy page for the controller to which the display device is to be added.
3. Click Add. The I/O Module Setup dialogue box is displayed.
4. In the Mod ID box enter the module ID of the display. I/O module 1 cannot be selected. The module ID
defaults to 2 but can be changed between 2 – F (2-15).
5. In the Module Type box click WMB Display.
6. In the Fan Config box specify the way in which the fan speed is displayed on the display by selecting the
required option.
8. Click Exit.
9. Assign I/O channels to the display device.
16.8 Add an Undefined Connective to a Module
An undefined connective to a module can be used to link a module to another that is not currently in the strategy.
Undefined connectives are indicated on the strategy page in red .
To add an undefined connective to a module:
1. Display the strategy page to which the undefined connective is to be added.
2. Click , or right-click the page where the connective is to be placed, and point to Other and click
Undefined Connective. The Undefined Connective dialogue box is displayed.
3. In the Label box enter the label for the undefined connective
4. Click Analogue, Digital, Sensor, Digital Input, Knob, or Switch to specify whether the connective is for
analogue or digital value, or specifically for a sensor, digital input, knob, or switch.
the page.
Note: As soon as the module the undefined connective represents is added to the strategy, the undefined connective
should be defined accordingly.

General Operations
16.9 Add an Undefined Connective to a Node

For pre IQ3 controllers an undefined connective to a node can be used to link the input of a module to a node (such
as an alarm bit), or a node with a constant value. Undefined connectives are indicated on the strategy page in red .
To add an undefined connective to a node:
1. Display the strategy page to which the undefined connective is to be added.
2. Click , or right-click the page where you want to put the connective point to Other and click Undefined
Connective. The Undefined Connective dialogue box is displayed.
3. In the Label box enter a label for the undefined connective.

4. Click either Analogue or Digital to specify whether the node is analogue or digital.
5. Click Array. This displays the Analogue Node Array dialogue box for analogue nodes, and the Digital
Node Array dialogue box for digital nodes.
6. Click the required node or bit. If necessary, use the scroll bars to locate the required node. The node number,
its type, and status are displayed on the right of the dialogue box. The type specifies what the node is generally
used for, and the status specifies what is currently writing to the module. Icons next to these parameters
indicate this graphically.
Icon Description
Type
Convention. The node is normally used by the strategy for a specific purpose (e.g. storing 0). It can
either be used for its conventional use, or if the conventional use is never required, it can be used for
another purpose.
Fixed system node. This module is always written to by a specific module in the strategy.
Free
Read only. This node is used for a special purpose (e.g. time) by the controller. Its value can be read
by the strategy, but not changed.
System defaults (e.g. alarm enable bits) can be used with care.
Status
Free to be used.
Used as a destination. Can be used again with care.
7. Once the correct node is selected, click OK to return to the Undefined Connective dialogue box.
8. If the node is to provide a constant value, enter that value into the Fixed Node box.
10. Move the cursor to the position where the connective is to be placed and click to place the connective on the
page.

General Operations
16.10 Add System Performance Module Strategy Block

For IQ4 controllers with v3.1 firmware or greater a block of strategy linking the IQ4 system performance module's
memory allocated, cpu usage %, memory usage %, and seq table execution time % parameters to plot modules can be
added to the strategy.
To add the system performance module strategy block:

1. Display the strategy page to which the strategy block is to be added.
2. Right-click the strategy page, and point to Device and click Diagnostic Plots.
3. Move the mouse to the required location of the strategy, and click the strategy page.

General Operations
16.11 Add Unplaced Modules to a Strategy Page

If the strategy stored by IQSET has been compared with a file uploaded from a controller, and modules without the x,
y, and page parameters defined have been added; the new modules will be regarded by IQSET as 'unplaced modules'.
Unplaced modules do not appear on any strategy page, although links to other modules are maintained, but not shown.
It is therefore necessary to add these unplaced modules to a strategy page, and link them accordingly. This ensures
that all the strategy is visible.
To add unplaced modules to a strategy page:
1. Display the strategy page onto which the modules are to be placed.
2. On the Tools menu click Unplaced Modules. The Unplaced Modules dialogue box is displayed.
3. Double-click the required module to place it on the page.

Note: It will now be necessary to link the module as required.
4. Once all the modules have been placed on the page, click Finished.

General Operations
16.12 Authorise a TCL Application

Sometimes the designer will lock a TCL application. To enable the application to be used in a specific controller it
must be authorised for use by that controller. Not all TCL applications are locked, and even if they are you may already
have been supplied with a file that will run on your controller. If you attempt to download a TCL application that is
not authorised to run on the selected controller an error message will be displayed.
Authorising a TCL application is a two-part process:
Obtaining an unlock code.
Entering the unlock code.
To obtain an unlock code:
1. Browse the system to display the device that is to run the application.
2. Right click on the IQ3/XNC and click Download XNC Application. The XNC dialogue box is displayed.
3. Click Open File. The Open dialogue box is displayed.

General Operations
4. In the folder list click the required file. The dialogue box will display the files in the ‘set projects\<project
name>\ xnc\downloads’ where <project name> is the name of the current IQSET project. To select a file
stored in a different location, click the drive, or folder in the Look in box that contains the file, and double
click the folders in the folder list until the file is displayed.
5. Click Open. The file is opened and details displayed in the XNC dialogue box.
6. Make a note of the controller's MAC address, the application title, and identity.
7. Send this information to the supplier of the TCL application, asking for an unlock code.
To enter the unlock code:
1. Obtain an unlock code as described above.
2. Browse the system to display the controller that is to run the application.
3. Right click on the controller and click Download XNC Application. The XNC dialogue box is displayed.
5. In the folder list click the application file for which you have the unlock code.
6. Click Open.
7. In the Key from application owner to enable this application on this controller box enter the unlock code
that has been supplied.
8. Click Enable. If the code is valid the application will be unlocked, and the MAC Address, Application
Title, and Identity boxes are hidden. If it is invalid a message is displayed. If an invalid code is entered 3
times it is necessary to restart the application before you can try again.
9. Click Save Enabled File to save the enabled file. The file will be saved in the same directory as the original
file, named in the following format:
L< xxx> n<yyy>.xnc
Where <xxx> specifies the LAN number of the device. <yyy> specifies the network address of the device.
Note: Closing the application without saving the enabled file will lose the unlocked application.
If required the file can be downloaded to the /XNC by clicking on Download this enables the application to be
downloaded, but not saved.
This process can also be used to change the device that a TCL application can be used on by selecting the new XNC
loading the unlocked file and obtaining an unlock code for the new device.
16.13 Backup IQ3 Controllers
It is possible to backup information in IQ3 controllers excluding the firmware, alarm log, and logged data.
The backed-up information is stored in a directory known as the backup root directory. The information for each
controller is stored in its own uniquely identified within the backup root directory in the structure shown below:
IQ3 Backup
|----Site Name
|----Date and Time
|----L<xxx>n<yyy> <Identifier> <IP Address>
Where <xxx> specifies the LAN number of the controller, <yyy> specifies the network address of the controller;
<Identifier> and <IP Address> are the controller’s identifier and IP address as defined in the address module.
Note: This backup procedure is only to provide a recovery facility if the firmware upgrade causes a problem. IQSET
should be used for standard strategy backup.
To backup IQ3 controllers:
1. View the site containing the controllers on the Trend system that are to be backed up.
2. Right-click the controller that is to be backed up, or the LAN containing controllers that are to be backed up
and click Upgrade Controller. The TsetIq3Upgrader Warning dialogue box is displayed.
3. Click Continue. The IQ3 Upgrade Window is displayed.

General Operations
4. Click Settings. The Settings dialogue box is displayed.
5. In the Username box enter the username, and in the Password box enter the matching password that is to
be used to authorise the backup. This must match with one in the controller and be of level 90 or above to
enable the backup.
If there are no users set up in any of the controllers that are to be backed up a username and password is still
required if this is the case use ‘IQ3’ as the username, and ‘user’ as the password.
6. If backing up controllers with version 1.3 firmware or greater in the Pin box enter a PIN. This must match
with one in the controller and be of level 90 or above to enable the backup.
Note: If more than one controller is being backed up, only one username, password and PIN can be specified,
if the controllers have different usernames passwords, and PINs the process will fail. It is therefore
recommended that all the controllers on a system have the same username, password and PIN.
If you want the username, password and PIN to be remembered for the next session select the Remember
Username, Password, and Pin check box.
7. In the Connection Speed box click Default to specify the of the connection speed. If problems are
encountered with communications the connection speed can be specified manually.
8. Click next to the Backup Root box and select the required directory from the dialogue box that is
displayed to specify the Backup Root directory that is to contain all the backups of the files from the
controllers.
9. Select the Enable Advanced Settings check box.
10. Click Advanced Settings. The Advanced Settings dialogue box is displayed.
11. Click Backup and/or Upgrade.

12. In the Upgrade Type area click None. This prevents the applet performing an upgrade.
13. Click either Strategy Folder Only, or Backup Everything to specify what information is to be backed up.
Option Description
Backup Everything Backs up everything in the controller except the firmware alarm log, and logged data.
Strategy Folder only Only backs up the strategy folder i.e. only the strategy information.
14. Click OK to return to the Settings dialogue box.
15. Click OK to return to the IQ3 Upgrade Window.
16. Select the controllers in the list that are to be upgraded, by clicking the check box next to them. Clicking
Select All will select all the devices in the list.
17. Click Check Comms to check that there is an Ethernet connection with each of the selected controllers. Each
of the selected controllers will now be pinged to check that it is there.
18. Click Upgrade. A dialogue box is displayed asking if you are sure you want to proceed with the backup.

General Operations
19. Click Yes. The backup will be carried out the progress of which is displayed in the progress bars in the
Controller List and at the bottom of the window. Clicking Abort stops the backup process. If a controller is
in the process of being upgraded that upgrade will be completed before the process is aborted.
20. Once the backup is complete a dialogue box will be displayed. Click OK.
Note: Once the process is complete you should disable the advanced settings by clearing the Enable
Advanced Settings check box.
16.14 Change a Controller's Type
IQSET enables the type of controller to be changed after it has been added to the network structure. However, it is not
recommended that this be done after strategy has been defined for the controller, because features available in the
original controller type may not be available in the new controller type.
Note: It is not possible to change a controller to be an IQECO.
To change a controller’s type:
1. Display a strategy page for the controller whose type is to be changed.
3. Click Select Device. The Controller Selection dialogue box is displayed.
box.

General Operations
5. Click the required option (IQ1, IQ2, IQECO, IQ3 or IQ4) in the Range area to specify the range of the
controller. Clicking the Other option enables a custom controller type to be added providing the .IQD file
exists in the 'C:\Program Files\Trend Control Systems\System Engineering Tool\Devices' folder.
7. In the Firmware Version box click the firmware version of the IQ controller.
8. In the Hardware Variant box click the hardware variant of the IQ controller.
9. In the Options area select the required check box(s) to select any required options (e.g. BACnet).
11. Click OK.
16.15 Change a Node's Value
If a node is being used in the strategy to provide a fixed value, the value can be changed.
To change the value of a node:
1. Display the strategy page that contains the connective that points to the node.
2. Right-click the connective pointing to the node, and click Edit Parameters. The Fixed Value Node dialogue
box is displayed.
3. In the Fixed Node box enter the value for the node.
4. Click OK.
16.16 Close a Project
If required a project can be closed without closing IQSET.
To close a project:
2. On the File menu click Close SET Project.
The appearance of the Trend system displayed in the System View is saved when IQSET is closed. What is saved
depends on how IQSET has been configured - see 'Specify the Loading and Saving of Site Data'.
16.17 Close a Strategy Page
To close a strategy page:
1. Click on strategy page's tab.
or
Display the strategy page that is to be closed, and on the File menu click Close Strategy.
16.18 Collect Controller Diagnostic Information
If you are having problems with a controller Trend technical support may request some diagnostic information. This
can be easily collected.
To collect diagnostic information:
1. Navigate to the required controller.
2. Right-click, and click Collect controller diagnostic information. A dialogue box is displayed.
3. In the Username box enter the required user name.
5. Click Examine the device. The applet will collect the diagnostic information. Once the information has been
collected a dialogue box is displayed.
6. Click OK to return to the original dialogue box.
7. Click Display Files. Windows Explorer opens shoeing the folder containing the collected files.
8. Send the files to Trend technical support e.g. by email.

General Operations
16.19 Convert Strategy

IQSET enables a strategy written for one controller type, or firmware version to be upgraded for use with another
controller of a different type, or firmware version.
General rules
 Only upgrade to a newer product e.g. IQ2 to IQ4 or to a new firmware version e.g. IQ3 v2.30 to IQ3 v3.0.
IQSET will prevent a strategy from being downgraded.
 It is only possible to upgrade IQECO strategy to a newer version of IQECO it is not possible to upgrade other
strategies to IQECO or to convert an IQECO strategy for use on type of IQ controller e.g. IQ4.
 With all strategy conversions, it is vital that the strategy is recommissioned.
What the conversion does
IQSET converts all modules to the equivalent modules for the new strategy where possible. However, when converting
an IQ1 or IQ2 strategy to an IQ3 or IQ4 strategy IQSET need to make some changes to the strategy:
 Alarm Handling: An additional page is inserted that contains strategy that replicates the alarm handling in
the IQ1 or IQ2 strategy. The alarm Address and Remote LAN in the destination module are set to the alarm
address values in the address module and the enable parameter of the route module is enabled if the Alarm
Address or Remote LAN are greater than zero. Any module that has an alarm parameter set to Enable, will
have the corresponding alarm group parameter set to alarm group 1.
 Sensor Type Modules: Sensor type modules that use any scaling other than characterise will be upgraded to
use a standard sensor definition from the library with the equivalent characterise scaling. If one does not exist
if will be necessary to manually configure the scaling.
The impedance of the voltage inputs on IQ4 controllers is different from IQ1, IQ2, and IQ3 controllers.
IQSET will attempt to find an equivalent scaling. If one does not exist if will be necessary to manually
configure the scaling. If the voltage input is being used with a potential divider e.g. the fan speed on
TB/TS/KOSF the strategy must be modified to ensure that the it operate correctly with the new values which
are approximately half of the IQ3 values.
 Adjustment Knobs: A knob linked to the parameter the adjustment knob was adjusting is added to the
strategy.
 Schedule Offset modules: When converting to an IQ3 v1.1 or greater or IQ4 strategy the modules are
converted. For IQ3 controllers with pre-version 1.1 firmware the modules are removed from the strategy.
 Fast sequenced strategy: An option is given to convert fast-sequenced strategy to event driven strategy. If
Yes is selected the fast-sequenced strategy is converted to event driven strategy. If No is selected the sequence
step is removed from the digital input and the return step turning the fast-sequenced strategy into normal
strategy.
 Data From IC comms Modules: When converting to an IQ3 v2.0 or greater or IQ4 strategy the modules
are converted. For IQ3 controllers with pre-version 2.0 firmware the modules are removed from the strategy.
 Analogue and digital nodes: An option is given to convert analogue nodes to analogue node modules, and
digital nodes to digital byte modules. If Yes is selected the modules nodes are converted. If No is selected
the nodes are removed from the strategy.
 Critical Alarm Modules: This feature is not supported by IQ3 or IQ4 controllers the module is removed
from the strategy.
 Autodial Modules: This feature is not supported by IQ3 or IQ4 controllers the module is removed from the
strategy.
 Comport Modules: This feature is not supported by IQ3 or IQ4 controllers the module is removed from the
strategy.
 Modem Modules: This feature is not supported by IQ3 or IQ4 controllers the module is removed from the
strategy.
 Record Modules: This feature is not supported by IQ3 or IQ4 controllers the module is removed from the
strategy.
 Store Modules: This feature is not supported by IQ3 or IQ4 controllers the module is removed from the
strategy.
 Alarm Bits: Those that can be converted are, those that can't be converted are removed from the strategy.
 Constants: Removed from strategy, the constant value they represent is placed in the appropriate module
parameter.
 I/O channels: When converting IQ3 strategy to IQ4 strategy input channels and output channels are mapped
as below:
IQ3 to IQ41x. Input channels 1 to 5 mapped to input channels 1 to5, output channels 11 to 16 mapped
to 6 to 11.

General Operations
IQ3 to IQ422/IQ4E. Input channels 1 to 6 mapped to Input channels 1 to 6, output channels 11 to 16 to
input channels 7 to 12.
All other channels are cleared from the modules.
 Deleted modules: Modules that have been removed from the strategy are placed on the page with a big red
cross through them, and any links that are invalid are shown as red.
To convert a strategy:
1. Display a strategy page for the controller whose strategy is to be converted.
3. Click Select Device. The Controller Selection dialogue box is displayed.
box.
5. In the Range area click the required option.
7. In the Firmware Version box click the required firmware version.
8. In the Hardware Variant box click the required hardware variant of the IQ controller.
9. In the Options area select the required check box(s) to select any required options (e.g. BACnet).
10. Click OK.

General Operations
11. Click OK. Once the strategy is converted a dialogue box is displayed. This lists parts of the strategy that
could not be converted, and any changes made to the strategy by the conversion process.
12. Review the strategy and adjust parts of the strategy that cannot be converted. The table below lists some
common problems and how they can be solved.
Sensor scaling could not be converted - Manually configure the sensor scaling as required, see 'Set up
Sensor Type Modules Manually'.
Knobs and switches as destination node - Link the input of the knob or switch to output of the module as
shown below.
IC Comms received from an IQ2 controller for an analogue node, or a digital bit/byte - Add an analogue
node, or digital byte module as required.
Data From IC Comms - This problem only occurs on pre v2.0 IQ3 controllers because Data from IC comms
messages are not supported. Configure the controller containing the required data to send it to the IQ3.
Digital Byte IC Comms to be sent to another controller - This problem only occurs on pre v1.2 IQ3
controllers because Digital Byte IC Comms messages are not supported. You should use a D to A module to
convert the value to an analogue and sent that, and convert it back to a digital in the receiving controller using
an A to D module.
16.20 Copy a Strategy Page
Strategy pages can be copied to the clipboard (in emf format) so that they can be pasted into other applications.
To copy a strategy page:
1. Display the strategy page containing the modules that are to be copied.
2. Right-click the page and point to Page and click Copy to Clipboard. The page is copied to the clipboard in
emf format.
16.21 Copy and Paste Modules
Modules can be added to a strategy page, by copying them from one strategy page, and pasting them onto the required
strategy page (this could be elsewhere on the same page). If modules copied from one device are pasted into a device
in which does not support them unsupported modules are not be pasted.
The sequence order used for the modules when they are pasted is defined by the order in which they were selected
starting with the next sequence step as defined by the sequence pointer. If the sequence step order is important, then
the modules should be selected using the CTRL key, and mouse method, not the block select, or select all methods.
Alternatively, the sequence table could be subsequently edited to ensure that the modules are ordered correctly.
To copy and paste modules:
1. Display the strategy page containing the modules that are to be copied.
2. Select the required modules.
3. Click , or right-click the selected module (s) and click Copy, or press CTRL+C, or choose on the Edit
menu click Copy. To cut modules, click , or right-click the selected module(s) and click Cut, or press
CTRL+X, or on the Edit menu click Cut.
4. Display the page onto which the modules are to be placed copied.
5. Check that the next module numbers that are to be used are correct by viewing the Next Module List, if not
change them.
6. Click , or press CTRL+V, or on the Edit menu click Paste. The modules are placed onto the current
strategy page using new module numbers and sequence steps as defined by the current values of the
appropriate pointers. A single module can be copied, or cut by right-clicking it, and clicking Copy or Cut.
Note: If modules are cut from a page, and not pasted back onto a page, they will not appear on any page, but IQSET
still thinks the modules are being used. If this is the case, it is necessary to add these unplaced modules onto the
relevant pages

General Operations
16.22 Create a Data File

IQSET can create data file (IQ4, IQ3, IQe, IQ2 - IQ2 controller v2.0 greater, or LDF file - pre IQ3 controller with
firmware earlier than version 2.0) for each controller in the project. The file can then be downloaded to the appropriate
controller using IQSET. The file is stored in the Download directory for the current project. If the strategy is from a
solution that is part of a licensed library the controller licence file is copied to the project's Download directory.
For IQ4, IQ3, IQe, and IQ2 files the filename is in the format:
L<xxx>n<yyy>.<File Info>.<zzz>
<xxx> specifies the LAN number of the controller. <yyy> specifies the network address of the controller.
<File Info> is only used for IQ4 and IQ3 files that contain the option addressing information. A different letter
indicates the type of information that is contained.
Option Description
I The file contains the controller's IP address, sub net mask, UDP port, and default router.
A The file contains the controller’s LAN and outstation numbers.
U The file contains the supervisor port
<zzz> indicates the file format (IQ4, IQ3 IQe, IQ2, or LDF), e.g. L099n020.IQ3 would be the file name given to the
file uploaded from controller 20 on LAN 99.
For LDF files two LDF files are created with filenames using two naming conventions:
<xxx><yyy>.ldf
and
L<xxx>n<yyy>.ldf
<xxx> specifies the LAN number of the controller. <yyy> specifies the network address of the controller.
<zzz> indicates the file format (IQ4, IQ3 IQe, IQ2, or LDF), e.g. L099n020.IQ3 would be the file name given to the
The first convention is where the first three characters of the file name specify the LAN number, and the next three
specify the controller’s address e.g. 024025.LDF would be the LDF file for controller 25 on LAN 24. This is the same
as that used by 822 Toolbox. The other format is that used by other tools, which includes an 'L' before the LAN
number, and an 'n' before the controller address e.g. the file for controller 25 on LAN 24 would be L024n025.LDF.
To create a data file:
1. Display a strategy page for the controller for which an IQ3 file is to be created.
2. Ensure that the required Identity boxes on the network and address modules are selected to include the
necessary parameters in the file. If they are not included they will not be downloaded even if the appropriate
check box is selected when the file is downloaded.
3. On the Strategy menu click Create Data File. Once IQSET has created the file, it displays a dialogue box
indicating that the file has been created.
4. Click OK. If any errors are detected when the file is created a dialogue box is displayed listing what they are
to continue creating the file with the errors, click Yes to abort the operation click No. To copy the error
messages to the clipboard click Copy to Clipboard.

General Operations
16.23 Create Multiple Data Files

IQSET can create the files required for downloading for more than one controller in a single step from Project View.
The files are stored in the download directory for the current project. If the any of the strategies are from a solution
that is part of a licensed library the controller licence file is copied to the project's Download directory.
To create multiple data files:
with a .
3. On the Project menu click Create Data Files. This displays a dialogue box asking for confirmation of the
action.
4. Click OK. A data file will be created for each of the selected controllers. The progress is indicated by a
dialogue box.
5. Once the process is complete a dialogue box is displayed, click OK.
16.24 Create Plant Directories
The plant directories are available from the Plant View, and enable strategy pages to be grouped together. This
grouping allows individual strategy pages to be located, in an alternative way to selecting the controller containing
the strategy, e.g. the HVAC equipment they control.
The structure of plant directories can also be used to set up the display modules and directory modules.
To create a plant directory:
2. In the Plant View right-click the top-level of the project, and click Insert Plant Directory.
3. Enter the name of the plant directory.
4. Click the mouse away from the text that has just been entered.
5. In the Device View select the strategy page that is to be put in the plant directory.
6. Click the left mouse button, and drag the strategy page into the required plant directory, or into the appropriate
directory in the Plant View.
Note: Plant directories can be sub-divided by adding directories within directories. In the Plant View, right-click the
plant directory to which more levels are to be added and click Insert Directory, then proceed from step (3) above.

General Operations
16.25 Define an Undefined Connective's Destination

If an undefined connective has been used to link to a module that is not yet in the strategy, as soon as the module is
added, the undefined connective should be defined. Undefined connectives are indicated on the strategy page in red
.
To define an undefined connective:
1. Display the strategy page that contains the undefined connective.
2. Double-click the undefined connective, or click , or right-click the page and point to Other and click
Connective. The Connectives dialogue box is displayed.
3. Click the undefined connective that is to be defined. The list can be filtered to only show undefined
connectives by clicking .
4. Click Define. The pointer changes to .
5. In the dialogue box click the module to which the connective is to point. The Confirm dialogue box is
displayed.
6. Confirm the selection. To define the connective as specified in the Confirm dialogue box click Yes. To select
an associated connective, click No the Confirm dialogue box closes and the pointer changes to , click
the associated connective in the Associated box. The Confirm dialogue box is displayed again, click Yes.

General Operations
16.26 Delete a Connective

To delete a connective:
1. Display the strategy page that contains the connective that is to be deleted.
2. Click , or right-click the page and point to Other and click Connective. The Connectives dialogue box
is displayed.
3. Click the connective that is to be deleted. The list can be filtered by clicking the appropriate button at the
bottom of the screen, making it easier to find the required module.
Icon Description
All connectives
Knob connectives
Sensor connectives
Switch connectives
System connectives

General Operations
The list can also be filtered by label or module. To filter by label, enter the required label in the box next to
box next to the Type Filter button, and then click Type Filter. E.g. enter L to find all connectives relating
to loop modules, or L1 to find all connectives relating to loop 1.
4. Click Delete. The selected connective will be deleted.
5. Click Exit.
16.27 Delete a Link
To delete a link:
1. Display the strategy page that contains the link.
2. Right-click the link, and click Delete Link.
16.28 Delete a Plant Directory
To delete a plant directory:
2. In the Plant View right-click the plant directory, or the directory that is to be deleted, and click Delete
Directory.
16.29 Delete a Strategy Page
To delete a strategy page:
1. Display the page that is to be deleted.
2. Click or right-click anywhere on the page, and point to Page and click Delete Page, or on the Edit menu
click Delete Page. A dialogue box is displayed asking for confirmation of the deletion.
3. Click Yes.
Caution: Deleting a strategy page will delete all the strategy on it. If an attempt is made to delete the first strategy
page (page 2), the page will not be deleted, only the strategy on it.
16.30 Delete an IQECO Display Device
To remove an IQECO display device:
1. Display a strategy page for the controller from which the display device is to be removed.
3. Click the display device that is to be deleted, to highlight it.
4. Click Remove.
5. A dialogue box is displayed asking for confirmation of the deletion. Click Yes.
6. Click Exit.
16.31 Delete Modules
IQSET allows either a single module, or a group of modules to be deleted from a strategy page.
To delete an individual module from a strategy page:
1. Display the strategy page containing the module that is to be deleted.
2. Right-click the module that is to be deleted, and click Delete Module. A dialogue box is displayed asking
for confirmation of the deletion.
3. Click Yes.
To delete a group of modules from a strategy page:
1. Display the strategy page containing the modules that are to be deleted
2. Select the modules that are to be deleted.
3. Press DEL, or right-click the page, and click Delete Selection. A dialogue box is displayed asking for
confirmation of the deletion.
4. Click Yes.

General Operations
16.32 Disable a Module

The output of a module can be prevented from influencing the rest of the strategy by disabling it. Modules are disabled
using the module state parameter. When the module is disabled its output is not updated, and is not passed on to any
linked modules. When a module is disabled it appears red on the strategy page.
To disable a module:
1. Display the strategy page that contains the module for that is to be disabled.
3. Click Enabled.
4. Click OK.
To enable the module again repeat the process and click Disabled. To enable all disabled modules in the strategy on
the Device menu click Re-Enable All Modules or right-click the strategy page and point to Device and click Re-
Enable All Modules.
Note: The module can also be enabled and disabled by the strategy by linking a digital value to the required modules
enable input.
16.33 Display Information about Autodialling Devices
Information all the autodialling devices on the network can be displayed in the Dialler Window.
To view information about autodialling devices:
1. Browse the system.
2. Right-click the sites name and click Dialler window, or click . The Dialler Window is displayed.
To close the window, click at the top right of the window. The display can be cleared by right-clicking in
the main area of the window, and clicking Clear All. It is also possible to drop a connection by right-clicking
the connection that is to be dropped and clicking Drop link of selected. The information in the window in
the window can be refreshed by right-clicking in the main area of the window, and clicking Re-Inquire
status.
Note: When the Dialler Window is displayed by clicking it will use the current connection to access the
Trend network.

General Operations
The Dialler Window is described in more detail in the Dialler Window Applet Manual (TE200530).
16.34 Display Trend System Communications Information
The communications IN and OUT of the node the application is using to connect to the Trend network can be displayed
in the Communications Window.
To view the communications information:
1. Browse the system.
2. Right-click the site name and click Comms window. The Communications Window is displayed.
Or
1. Click on the Basic Comms Display . The Communications Window for the current site is
displayed.
Note: When the Communications Window is displayed in this way it will use the current connection to access
the Trend network.
Communications IN are on the left, and communications OUT are on the right. Each of the boxes has horizontal and
vertical scroll bars, which enable more information to be accessed. To close the window, click at the top right of the
window. The display can be cleared by right-clicking in the main area of the window, and clicking Clear entries. The
communications can be paused, logged to file, blank lines inserted, and more details about a frame can be viewed by
double-clicking the frame.
The Communications Window is described in more detail in the Communication Window Applet Manual
(TE200531).
16.35 Display Keyboard Short Cuts
To display the list of keyboard shortcuts
1. Run IQSET and display the System View.
2. Click .
16.36 Display the Item Selector
To display the Item Selector:
1. Click to toggle the Item Selector ON/OFF.
16.37 Display the Project View
To display the Project View:
1. Click , click the Project View tab , press CTRL+N or on the View menu click Project View.
To expand/collapse a view in the Project View:
1. Click the title bar of the view that is to be expanded/collapsed. This will toggle the view between expanded
and collapsed.

General Operations
To hide the Project View:
1. Click the outside the Project View.
Note: If the Project View has been docked it must be undocked before it can be hidden.
16.38 Display the Strategy Library
To display the Strategy Library:
1. Click the System View tab , or on the View menu click Strategy Library.
To hide the Strategy Library:
1. Click the outside the Strategy Library.
Note: If the Strategy Library has been docked it must be undocked before it can be hidden.
16.39 Display the System View
To display the System View:
1. Click , click the System View tab , press CTRL+L, or on the View menu click System View.
To hide the System View:
1. Click the outside the System View or click .
Note: If the System View has been docked it must be undocked before it can be hidden.
16.40 Display the Tracker Window
If required a list of devices that displays the immediate children in the structure of the site, or user node of the object
currently selected in the System View can be displayed in the Tracker Window. As different devices are selected in
the System View the information displayed changes accordingly.
To display the Tracker Window:
1. On the View menu click Tracker View.
16.41 Display the Tip of the Day
If tip of the day is turned ON whenever IQSET is run the Tip of the Day dialogue box is displayed providing useful
information about IQSET and its use. It is possible to view the tip of the day at any time
To display the tip of the day:
1. Run IQSET.
2. On the Help menu click Tip of the Day. The Tip of the Day dialogue box is displayed.
3. If the Tell Me More button is available clicking it will display more information about the tip. To display
the next tip, click Next Tip.

General Operations
4. Click Close.
TIP: Clearing the Show Tips on StartUp check box prevents the tip of the day from being displayed when IQSET is
run.
16.42 Dock Panes
The Project View, Strategy Library, System View and Search Library can be docked which prevent them from
being hidden when you click outside.
To dock panes:
1. Click .
To undock panes:
1. Click .
16.43 Download a Single Page of Strategy
If required the strategy on a single strategy page can be downloaded to the controller (not IQECO) enabling minor
changes to be made to a strategy, and reducing the download time.
Note: Before making changes to a page that are to be downloaded using single page download you should ensure that
the strategy held by IQSET (displayed on the page) and that in the controller are identical by downloading the strategy
first, or running a compare.
To download a single page of strategy:
2. Display the strategy page that is to be downloaded.
3. Click or on the Comms menu click Download this Page, or right click the page, point to Page and click
Download Page. A dialogue box asking if you want to send the current page to the controller is displayed.
4. Click Yes. The Connection Details dialogue box is displayed.
displayed, and uses the current site, and the connection associated with it. These can be changed if necessary.
Caution: If downloading to a different controller, ensure that its firmware version is the same or higher
than the controller for which the strategy was created.

General Operations
 In the Site Name box click the required site. If a different comms connection is to be used select the
required one from the Standard Comms box. If none of the standard connections are suitable the
connection can be specified by clicking Edit Connection Details. This displays the Connection Wizard
which enables the connection to be specified using the TUA Editor or the Connection Wizard.
comms connections.
6. If the controller has security enabled specify the password that will authorise the upload.
IQ4 or IQ3 controllers:
 For IQ4 and IQ3 v1.3 or greater controllers in the Pin box enter the PIN.
connecting. If they don't match a dialogue box asking if you want to continue is displayed. Click OK to
IQSET will check that the controller's time is within one minute of the PC time if there is a difference. If
there is a difference a dialogue box asking if you want to set the controller's time to match the PC is displayed.
Click Yes to adjust the time or No to leave the controller's time unchanged.
The strategy on the page will be downloaded.

General Operations
16.44 Download a TCL Application

TCL applications can either be downloaded by IQSET with the strategy file or using the TCL Authorise Applet as
described below.
To download a TCL application using the TCL Authorise Applet:
1. Obtain an unlock code.
2. Browse the system to display the device that is to run the application.
3. Right click on the controller and click Download XNC Application. The XNC dialogue box is displayed.
5. In the folder list click the required application file. This file must be authorised to run on the selected /XNC.
6. Click Open.
7. Click Download. If the /XNC’s security is enabled a dialogue box is displayed asking for a username and
password. Enter a valid user name and password with a high enough authority and click OK. The file will be
downloaded. If the TCL application is not authorised to run on the selected /XNC an error message will be
displayed and the file will not be downloaded.

General Operations
16.45 Edit an IQECO Display Device

An IQECO Display Device's label and type can be changed.
To edit an IQECO display device:
1. Display a strategy page for the controller containing the I/O module that is to be edited.
3. Click the display device that is to be edited, to highlight it.
4. Click Edit. The I/O Module Setup dialogue box is displayed.
5. Edit the display as required.

7. Click Exit.
16.46 Enter Configuration Mode on Pre IQ3 Controllers
IQSET provides access to the configuration mode of pre IQ3 controllers on the network. Once the configuration mode
for a device has been entered, configuration commands can be entered and sent to the controller.
To enter configuration mode:
1. Display the strategy page for the controller that is to be accessed in configuration mode.
2. Click or on the Comms menu click Config. The Connection Details dialogue box is displayed. IQSET
is to be used in the Standard Comms Connection box click the required connection.
If suitable connection is not available an existing connection can be used as basis for new one that will be
associated with the site, by selecting the required connection from the Standard Comms Connection box,
and then clicking Edit Connection Details. This will display the TUA dialogue box that enables a connection
to be specified.

General Operations
Note: The connection specified here will not be added to the list of comms connections.
7. Click OK. IQSET will check to see that the identifier and controller address specified match the one to which
IQSET is connecting. If they don’t match a dialogue box asking if you want to continue is displayed.
8. Click OK to continue, or Cancel to cancel. If OK was selected the Config session window is displayed.
9. Type the required configuration command into the box at the bottom of the Config Session Window and
press ENTER or click Go to send the command to the device.
The system prompts the available functions; the uppercase character in each prompt is the key to be used to
select the function. Most functions also require an additional numeric value. To exit from any page of data
and save any changes, made, press X+ENTER. To exit from any page of data and not save any changes made,
press Q+ENTER. The commands are as explained in the IQ Configuration Reference Manual (90-1533) for
IQ controllers. If required keywords can be embedded in the commands to provide quicker access too
commonly used commands
It is also possible to send a previously used command or a favourite command to the controller, by selecting
the required command from the appropriate list, and pressing ENTER or clicking Go.
If a module is selected, the next and previous module of the same type can be viewed by clicking < or >. To
send a Q, or X to the controller click Q or X.
10. To close the session, click X at the top-level configuration prompts to exit configuration mode.
Note: If no commands are sent to the device for a period it will automatically exit configuration mode and
the Config Session Window will close.
For more details of using the Config Session Window see the Config/Text Comms/Mapping Applet Manual
(TE200536).
16.47 Export Data to 963
The labels etc. defined for a controller or specified controllers can be exported to a 963 database. This saves time
when engineering 963 and ensures that the labels etc. are correct.
To export data to the 963:
2. In the Device View click the next to each controller for which data is to be exported. IQSET will indicate
the selected controllers with a .

General Operations
3. On the Project menu point to Export and click Project Data to 963 v2 or Project Data to 963 v1.2
depending on the version of 963. The data will be exported to a file called s2.mdb in the set projects directory
for that project.
4. Move the file into the 963's install directory.
Caution: this will overwrite any system information already learned by 963.
16.48 Export Data to an EDE File
Strategy information to be exported as an Excel file, comma separated file, or tab separated file format EDE file. This
provides support for BACnet Engineering Data Exchange. For IQ4 and IQ3 v2.30 or greater IQSET will read the
value of the Object Name Prefixes parameter and if enabled the object name prefixes will be included in the EDE file.
If disabled, the prefixes will not be included. For IQ3 controllers earlier than v2.30 the prefixes are always included.
Note: This functionality requires Microsoft Excel® to be installed on the PC.
To export data to an EDE file:
2. Display a strategy page for the controller for which data is to be exported as an EDE file.
3. On the Strategy menu click Export EDE File (BACnet). The Export Options dialogue box is displayed.
4. Specify the type of file that is required by selecting the Excel, or CSV, or CSV (Unicode) Tab Separated
options.
5. Click OK. The Save As dialogue box is displayed.
displayed.
7. Click Save.

General Operations
16.49 Export Data to IQVISION

Information about devices in the project can be exported to an XML file that can be imported into IQVISION.
To export data for use in IQVISION:
2. In the Device View click the next to each controller for which data is to be exported. IQSET will indicate
the selected controllers with a .
3. On the Project menu point to Export and click IQVISION. The Save as box is displayed.
displayed.
5. Click Save. The data will be exported to a file called 'SET_Export.xml' in the specified location.
16.50 Export the Project Overview
The project overview provides an overview of all the controllers in the project. It lists the LAN number, address,
device type name, identifier, version, serial number/MAC address and presentation points (Sensor, Digital Input,
Knob, Switch, and Driver) of each controller. It also provides the total number of presentation points in the project
for use when calculating the required number of points for IQVISION.
To export the project overview:
with a .
3. On the Project menu point to Overview and click Export Overview. The Export Options dialogue box is
displayed.
4. Select the required format.

General Operations
displayed.
7. Click Save.
16.51 Export Module Lists
Lists of the sensor, digital input, knob, switch, driver, directory, and display modules in a strategy can be exported to
an Excel file, comma separated file, or tab separated file.
Note: This functionality requires Microsoft Excel® to be installed on the PC.
To export module lists:
2. Display a strategy page for the controller for which module lists are to be exported.
3. On the Strategy menu click Export Data. The Export Options dialogue box is displayed.
4. Specify the type of file that is required by selecting the Excel, or CSV, or CSV (Unicode) Tab Separated
options.
5. Specify which modules are to be included in the file by selecting the appropriate check boxes in the Tables
area. Click Select All to select all module types.

General Operations
displayed.
8. Click Save. The file is created. If CSV, or CSV (Unicode) Tab Separated was selected a separate file will
be created for each module type. If Excel was selected a single Excel file will be created.
16.52 Find a Module
IQSET allows modules used in the strategy to be located.
To find a module:
1. Display a strategy page for the controller containing the module that is to be located.
2. If the Command Line toolbar is not already displayed, on the View menu click Command Line to display
it.
4. In the Command Line toolbar enter the code for the module that is to be located, in the format below.
<Module Type><Module Number>
<Module Type> specifies the type of module using its module identifier (e.g. S specifies sensor). For details
of the module identifier see the appropriate module section of this manual. c specifies undefined connectives.
<Module Number> specifies the number of the module (e.g. to find sensor type S3).
5. Click or press CTRL. The Command Line toolbar will now display the page(s) containing that module.
6. To goto the module itself click or press CTRL again. If the module has been found on more than one
page, click the required page to highlight it, and then click .
16.53 Find Fixed System Nodes
When the Digital Node Array dialogue box is displayed, it is possible to find the location of fixed system nodes, and
nodes that have been placed in the strategy from either array.
To find a node:
1. Display the Digital Node Array dialogue box.
2. In the Find box enter the code for the required node. The codes for the individual parameters are described
below:
<Module Type><Module Number><Bit Code>
<Module Type> specifies the type of module using its module identifier (e.g. W specifies a switch). For
details of the module identifier see the appropriate module section of this manual.

General Operations
Note: For critical alarm modules, you must use CA not M which is the module identifier.
<Module Number> specifies the number of the module. <Bit Code> is a letter, or combination of letters that
define the bit required (e.g. to find the location of the sensor high alarm enable bit for sensor type S3EH.
Module
Letter Description
Type
Critical Device acknowledge bit
ADA
Alarms ASA
Acknowledge status bit
Digital E
A
Inputs R
V
Maintenance alarm acknowledge bit
AR
EM
Drivers AM
ER
M
R
IC Comms F Fail Bit
Process variable alarm acknowledge bit
AS
EP
Loops AP ES
O
P
S
High alarm acknowledge bit
AL
AO
AR
EH
EL
Sensors AH
EO
ER
H
L
O
R
Switches V Status bit
Note: If you select a user module e.g. U2 IQSET will find the bit that indicates whether that user is logged
on.
Certain information can be entered without specifying a <Module Type> and <Module Number>.
Code Description
0 Default location for 0
1 Default location for 1
15m 5 minute timing pulse

General Operations
Code Description
24h Daily minute timing pulse
60m Hourly timing pulse
CONL Controller on line alarm status bit
CONL INHIB Controller on line alarm inhibit bit
D1=INHIB Global Digital input alarm inhibit bit
DEF Emergency password in use bit
FAIL INHIB Global loop fail alarm inhibit bit
FBAT Battery failed status bit
FDRT Fail dual asynchronous receiver transmitter alarm status bit
FDRT INHIB FDRT alarm inhibit bit
FPIA Fail peripheral interface adapter alarm status bit
FPIA INHIB FPIA alarm inhibit bit
FPRM Fail programmable read only memory alarm states bit
FPRM INHIB FPRM alarm inhibit bit
FRAM Fail random access memory alarm status bit
FRAM INHIB FRAM alarm inhibit bit
FRTC INHIB FRTC alarm inhibit bit
FSWR Fail software alarm status bit
FSWR INHIB FSWR alarm inhibit bit
FTKA INHIB FTKA alarm inhibit bit
FTKP INHIB FTKP alarm inhibit bit
FTRC Fail real time clock alarm status bit
HELP Checksum failure alarm status bit
HELP INHIB Help alarm inhibit bit
HIGH INHIB Global Sensor high alarm inhibit bit
LOW INHIB Global Sensor low alarm inhibit bit
MINT INHIB Global maintenance interval alarm inhibit bit
Month Monthly timing pulse
OUTL INHIB Global Sensor out of limits alarm inhibit bit
READ INHIB Global Sensor read alarm inhibit bit
Reset Power reset bit
SDEV INHIB Global setpoint deviation alarm inhibit bit
SDGT INHIB Global driver grace time alarm inhibit bit
Test flag Alarm text flag
Week Weekly timing pulse
Year Yearly timing pulse

General Operations
16.54 Find and Replace Labels

The find and replace option enables labels to be replaced by specified text.
To find and replace labels:
1. Display a strategy page for the controller containing the labels that are to be replaced.
2. On the Tools menu click Label Find and Replace. The Label Find and Replace dialogue box is displayed
with a list of all module labels from the selected controller in the Module List box. This list defines the labels
that will be searched.
3. Select the modules that the find and replace is to search by holding down the CTRL key, and clicking the
required modules. To select a range, click the first module in the range, hold down the SHIFT key, and click
the last module in the range. To select all the modules click Select All.
The modules displayed in the Module List box can be reduced by filtering on the module type and label. To
filter on module type, enter the type of module using its module identifier (e.g. S specifies a sensor) in the
Module Filter box and click Apply Filter. For details of the module identifier see the appropriate module
section of this manual. To filter on module label, enter the module label in the Label Filter box and click
Apply Filter. To view all modules in the strategy click Show All.
4. In the Original text box enter the text that is to be replaced.
5. In the Replace with box enter the text that is to be used as the replacement.
Note: If required text can be copied and pasted into the Original text box and Replace with box.
6. Click Replace Partial Text in Selected module(s), or Replace Entire Label of Selected Module(s) to
specify whether the selected text or the entire label is to be replaced.
7. Click Replace.
8. Click Exit.
To replace labels using paste:
1. Copy the list of new labels. This can be done either from a text editor where the labels have been entered
(each label on a different line), or from another controller using this process but selecting Copy Label in step
(5).
2. Display a strategy page for the controller containing the labels that are to be replaced.
3. On the Tools menu click Label Find and Replace. The Label Find and Replace dialogue box is displayed
with a list of all module labels from the selected controller in the Module List box.

General Operations
4. Select the modules whose labels are to be changed by holding down the CTRL key, and clicking the required
modules. To select a range, click the first module in the range, hold down the SHIFT key, and click the last
module in the range. To select all the modules click Select All.
5. Click Paste Label.
6. Click Exit.
16.55 Find Where a Node is Used
IQSET allows you to find out where a node is used in the strategy.
To find where a node is used:
1. Display a strategy page for the controller containing the required node.
it.
4. Specify the node that is to be located. The command should be in the format shown below:
For analogue nodes:
A<Node Number>
<Node Number> specifies the number of the node
For digital nodes:
B<Byte Number>,<Bit Number>
<Byte Number> specifies the number of the byte containing the required bit. <Bit Number> is the number
of the bit that is required.
5. Click . The Command Line toolbar will display the module that uses the specified node.
6. To see which page that node is located on, click again. The Command Line toolbar will now display the
page(s) containing that module, to goto the module itself click again. If the module has been found on
more than one page, click the required page to highlight it, and then click .
16.56 Find where a Sequence Step is Used
IQSET allows the module located at a sequence step to be found.
To find where a sequence step is used:
1. Display a strategy page for the controller containing the required module.
it.
4. Specify the sequence step in the format shown below.
Q<Sequence Step Number>
<Sequence Step Number> is the sequence step that is to be found
5. Click . The Command Line toolbar will display the module located at the specified sequence step.
6. To see which page that module is located on, click again. The Command Line toolbar will now display
the page(s) containing that module to goto the module itself, and click again. If the module has been
found on more than one page, click the required page to highlight it, and then click .
16.57 Go to a Module
To go to modules connected to a module's output:
1. Right click the module's output and click the required module.
To go to the module references by a connective:
1. Right click the connective and click Goto Module.

General Operations
16.58 Go to a Strategy Page

It is possible to move to another strategy page in several different ways.
Using the Next and Previous Page buttons:
1. Click or press the PG UP key to go to the previous strategy page, or or press the PG DN key to go to
the next strategy page.
Note: The Command Line's commands NEXT and PREV can be used to perform these functions from the Command
Line toolbar.
Using the Go to button:
1. Click . A list of pages for the controller is displayed.
2. Click the required page.
From the Device View:
1. Display the Project View
2. In the Device View double-click the controller containing the required page. The view will expand to show
the contents of the controller.
3. Double-click Strategy Pages. The view will expand to show list the pages available for that controller.
4. Double-click the page that is to be displayed.
To display the first page of strategy for a controller:
2. In the Device View right click the controller containing the required page and click Open.
Using the Plant View:
2. In the Plant View double-click the required directories to expand the view until the required page is visible.
3. Double-click the page that is to be displayed.
Note: For XNCs the XNP Update Settings dialogue box may be displayed if the number of stores, inputs outputs and
version stored in the IQSET file is different to those stored in the XNP file. Click Update to use the values stored in
the XNP file, or Ignore to use the values stored in the IQSET File.
It is possible to specify the location of the strategy page.
If a strategy page has been displayed, but has been covered up by other windows, e.g. a page from another controller
has been displayed; it can be brought to the front by clicking the required page on the Window menu.
Pressing CTRL+F or clicking Full Screen on the View menu displays the current strategy full screen.

General Operations
16.59 Import a Backdrop File

If backdrop files have been uploaded from IQ4 or IQ3 controllers, they can be imported into the backdrop directory
of the current project so that they can be used.
To import a backdrop file:
3. On the Project menu click Import and click Backdrop File. The Select IQ3 Backdrop file to import
is displayed.
5. Click Open. The backdrops in the file will be imported into the backdrops directory for the current project.
A dialogue box is displayed indicating the progress of the process. Once the process is complete a dialogue
box is displayed.
16.60 Log in
If IQSET's autolock feature has been enabled and IQSET has locked due to a period of inactivity you will need to log
back in.
To log in:
1. If IQSET is locked the window below is displayed.
2. Enter the your password in the Password box.

3. Click OK.

General Operations
16.61 Move Panes

The Project View, Strategy Library, System View and Search Library can be moved.
To move panes:
1. Dock the pane.
2. Click the left/right edge of the pane and are displayed.
3. Drag the mouse on top of or to attach the pane to the side of the SET Window. To position the
pane as a floating box, drag the mouse to the required position.
16.62 Perform an IQSET Command Using the Command Line Toolbar
The Command Line toolbar enables many of IQSET's commands to be performed simply by typing a command.
To perform an IQSET command using the Command Line toolbar:
it.
3. Press CTRL+L, or on the Tools menu click Command Line to activate the Command Line toolbar.
4. Enter the required command.
Command Description
DUMMY Add a dummy IC comms module
TEXT Add text to a page
CIRCLE Draw a circle
LINE Draw a line
RECTANGLE Draw a rectangle
ELLIPSE Draw an ellipse
SQUARE Draw a square
EXTENT Fill the window with the used area of the strategy page.
NEXT Goto the next page
PREV Goto the previous page
REDRAW Redraw the screen
Z Zoom to a specific area
5. Press ENTER to carry out the command.
16.63 Position the Toolbars
The toolbars in the SET Window can be moved to any position on the screen to suit individual requirements. When
docked, the toolbars can appear on any edge of the window, when undocked, they are known as floating toolbars, and
can be positioned anywhere on the screen even outside the SET Window.
To move a toolbar:
1. Click on a docked toolbar, or click the title bar on a floating toolbar.

2. Drag the toolbar to the required position, and release the mouse button. If you drag the toolbar to the edge of
the SET Window, it becomes a docked toolbar.
To dock a toolbar:
1. Move the toolbar to the required position at the side of the SET Window.
To undock a toolbar:
1. Click on the toolbar and move it to the required position.

General Operations
16.64 Position the Windows

When a task that is performed displays a window the position of this window can be adjusted as required.
To move a window:
1. Click the window’s title bar.
2. Hold down the left mouse button, and drag the window to the required position.
To tile all windows:
1. On the Window menu click Tile Vertically or Tile Horizontally.
To cascade all windows:
1. On the Window menu click Cascade.
To make a window full screen:
1. Click .
To position a window in half of the screen:
1. Click , , , or depending on where the window is required.
To position a window in a corner of the screen:
1. Click , , , or depending on where the window is required.
To resize a window:
1. Move the mouse over one edge of the window. The pointer will change to a double-headed arrow (e.g.
).
2. Hold down the left mouse button, and move the mouse until the edge of the window is in the required position.
To lock the windows size and position:
1. Click .
16.65 Print a Single Page of Strategy
To print the strategy on a single strategy page:
2. Display the strategy page that is to be printed.
3. Right click the page and point to Page and then click Print Page.
16.66 Print Strategy Blocks
IQSET enables strategy block to be printed out to provide a paper record of the strategy block.
To print strategy blocks:
2. Click the next to the strategy blocks that are to be printed. IQSET will indicate the selected one with a .
3. Click in the Strategy Library's toolbar. The Print dialogue box is displayed.
4. In the Name box click the required printer. Clicking Properties enables the printer properties to be adjusted.
IQSET will default to the Windows default printer, if a different printer is to always be used, it can be
specified as the default printer for IQSET.
5. Specifies the required printing options.
6. Click OK.

General Operations
16.67 Redraw the Screen

The screen can be redrawn at any time.
To redraw the screen:
1. Right-click the strategy page (do not click a module), and click Redraw.
Note: The Command Line toolbar’s REDRAW command can be used to redraw the screen.
16.68 Resize Panes
The Project View, Strategy Library, System View and Search Library can be resized.
To resize panes:
1. Click the left/right edge of the pane and drag the mouse to the required position.
16.69 Rename a Plant Directory
To rename a plant directory, or directory within a Plant Directory:
2. In the Plant View right-click the plant directory that is to be renamed, and click Rename.
3. Enter the new name.
16.70 Reset an IQ3 Controller
It may be necessary to reset an IQ3 controller back to the factory defaults if you are unable to communicate with the
controller, download strategy, use IP Tool, or PING the controller. The process requires the PC to be directly
connected to the controller, using both an Ethernet, and serial connection.
To reset an IQ3 controller:
1. Power up the IQ3 controller that is to be reset to factory settings.
2. Power up the PC that is to perform the reset.
3. Connect a cross over Ethernet cable between the IQ3 controller, and the PC.
4. Connect the PC's COM port to the IQ3 controller's local supervisor port using cable EJ101442.
5. Ensure that the PC TCP/IP Ethernet connection being used has an automatically assigned IP address.
6. If the PC has more than one TCP/IP Ethernet connection (e.g. wireless connections) ensure that these are
disconnected.
7. Run IQSET.
8. On the Tools menu click Null down IQ3. The Warning dialogue box is displayed.
9. Click OK. The Reset IQ3 Applet Window is displayed.
10. In the Select COM port box click the COM port being used to connect to the controller.
11. In the Enter controllers MAC address box enter the controller’s MAC address. This can be found on the
label on the front of the controller.
12. In the Select Ethernet Connect box click the IP address of the network card being used to connect the PC
to the IQ3. If step (6) above has been followed there should only be IP address in the drop-down list along
with the word (Automatic), all other adaptors will have an IP address of 0.0.0.0. If this is not the case, ensure
that all other TCP/IP Ethernet connections are disconnected.
13. Power down the IQ3 controller, and click Go.

General Operations
14. When prompted power up the IQ3 controller.
15. The reset process will proceed to completion. The progress is indicated in the Feedback box, and the Status
Bar.
Note: This process can take several minutes.
16.71 Restore Backed Up Data
It is possible to restore the data that has been backed up to the controller.
To restore backed up data:
1. View the site containing the controller on the Trend system to which data is to be restored.
2. Right-click the controller to which data is to be restored click Upgrade Controller.
3. The TsetIq3Upgrader Warning dialogue box is displayed.

be used to authorise the operation. This must match with one in the controller and be of level 90 or above to
enable the backup.
If there are no users set up in the controller that is to be restored a username and password is still required if
this is the case use ‘IQ3’ as the username, and ‘user’ as the password.
7. If restoring a controller with version 1.3 firmware or greater in the Pin box enter a PIN. This must match
with one in the controller and be of level 90 or above to enable the backup. If you want the username,
password and PIN to be remembered for the next session select the Remember Username, Password, and
Pin check box.
9. Select the Enable Advanced Settings check box.
10. Click Advanced Settings. The Advanced Settings dialogue box is displayed.

General Operations
11. Click Restore Backup.
12. Click OK to return to the Settings dialogue box.
13. Click OK to return to the IQ3 Upgrade Window.
14. Click the controller to which data is to be restored to highlight it.
15. Click Restore. A dialogue box like the one shown below is displayed that allows you to specify the directory
containing the data that is to be restored.
16. Navigate to the required directory and click it.

17. Click OK. A dialogue box informing you what is about to be done is displayed.
18. Click Yes.
19. Once the process is complete a dialogue box will be displayed. Click OK.
16.72 Run IQSET
Note: The first time IQSET is run it forces the creation of a single user 'Administrator' and requires a suitable
password to be specified. This user is only used to set up other users.
To run IQSET:
1. Run Windows®.
2. Run IQSET.
For Windows 10
 Click the Start button, click All Programs, click Trend Control Systems, click System Engineering Tool
and then click System Engineering Tool.
For Windows 8
 Display the Start screen - refer to the Windows 8 documentation.
 Click System Engineering Tool.
For Windows 8.1
 Display the Apps view - refer to the Windows 8.1 documentation.
 Click System Engineering Tool.
Note if required IQSET and be pinned to the Start screen - refer to the Windows 8.1 documentation.
Note: The User Account Control dialogue box maybe displayed, click the appropriate option to enable
IQSET to run.

General Operations
The Log onto SET dialogue box is displayed.
3. Click your name in the User Name box.

4. In the Password box enter your password.
Note: When Remember last login is selected IQSET will remember the user name and password of the last
user and the next time IQSET is run it will automatically enter the user name and password. This will disable
IQSET's autolock feature and reduce IQSET's security allowing anyone to log in.
5. Click OK. The SET dialogue box is displayed.

General Operations
6. Specify the task that is to be performed by selecting the required option.
 To open a new site file and browse the system click Open New Site File, and then click OK.
 To open an existing site file and browse the system, click Open Existing Site File, select the required
file from the list at the bottom of the dialogue box, and then click OK. To browse the system without a
site file open, click Live Site.
 To open a new project, click Create New SET Project, and then click OK.
 To open existing project, click Open Existing SET Project, select the required file from the list at the
bottom of the dialogue box, and then click OK.
 To open existing project and display the strategy for a specific controller, click Open Recent File option,
select the required file IQ file from the list at the bottom of the dialogue box, and then click OK. This
list also contains project files that can be selected, and opened.
 To import a project that has been zipped click Import Project from ZIP and select the required file
from the dialogue box that is displayed.
 To export a project to a zip file click Export Project to ZIP and select the required project, and file
location from the dialogue box that is displayed.
Note: If IQSET detects untrusted applets on start-up it will prevent them being loaded, and display a dialogue box
asking for authorisation to run them. Only allow untrusted applets if you are sure they come from a reliable source.
16.73 Select Modules
IQSET allows modules to be selected so that operations (e.g. copying, or moving) can be performed on them. Modules
that have been selected will change to yellow.
To select modules by dragging:
1. Display the required strategy page containing the modules that are to be selected.
2. Drag the mouse around the required modules.
To select modules by clicking:
1. Display the strategy page containing the modules that are to be selected.
2. Hold down the CTRL key, and click the required modules.
To select all modules on a page:
1. Display the strategy page containing the modules that are to be selected.
2. Right-click anywhere on the page, and click Select All.
To deselect all selected modules:
1. Right-click anywhere on the page, and click Unselect All.
To deselect a single module:
1. Hold down the CTRL key, and click the required module.
16.74 Set up a PIN
A PIN can be specified for an entire site, LAN, or device.
To set up a PIN:
2. Ensure that the current user role is at least 'Commissioning engineer'.
3. Navigate to the required part of the system.
4. Right-click the part of the system for which a PIN is to be specified, and click Set pin. The Set PIN dialogue
box is displayed.
5. In the Pin box enter the required PIN.

6. Click Apply.

General Operations
16.75 Set up Page Details

Details about when a strategy page was created or modified is automatically stored. Text information can also be
stored about the page; this is used to describe the function of the strategy on the page.
To set up page details:
2. Goto the page whose details are to be set up.
3. Click . The Page Info dialogue box is displayed.
4. In either the Line 1 or Line 2 box enter a description for the page.
5. In Details box enter the required details.
6. Click OK.
16.76 Set up the Site Codes
This section describes how to set up the human readable and machine-readable (GUID) site codes for a site.
To setup the site codes:
1. Display the site for which the site codes are to be set up in the System View.
2. Right-click the site and click Site code manager. The Site Code Manager Window is displayed.
3. Click Discover site code(s). The Site Code Manager Applet will discover devices on the site.
4. If the site contains more than one human readable site code, or more than one machine-readable site code a
warning is displayed. Click Yes and goto (6) otherwise goto (5).

General Operations
5. Click Assign New site codes. The Assign new site code dialogue box is displayed.
6. In the Human readable site code box specify the human readable site code, either click the required code
in the box to select an existing site code or enter the required code.
7. In the Machine readable site code box specify the machine-readable site code, either click the required code
in the box to select an existing site code, or click New to generate a new machine-readable site code.
8. If any of the controllers have security enabled in the Pin box enter the PIN that will authorise the change.
Note: Only one PIN is sent therefore if the controllers have different PINs the change will fail.
9. Click OK. The '$' parameter of the address module in the devices will be set to the text in the Human
readable site code box, and the 'O' parameter of the address module in the devices will be set to the text in
the Machine readable site code box.
16.77 Specify the BACnet Write Priority
If a client site is to write information to the BACnet system a write priority must be defined for each value that is to
be written to the BACnet site. A write priority can be assigned to a site, LAN, device or parameter. The same write
priority can be assigned to everything below the selected item in the System View.
An object’s write priority is used to determine whether the write affects the value in the BACnet system. If the priority
is higher than the priority of the value of the BACnet parameter, the value will be changed. If it is lower the value will
remember the value and its priority so that it can be used if the priority associated with the property's value changes.
Write priority values should be set in accordance with the system integration requirements for the site. The designer
of the site integration will have determined what priority levels should be used for what types of equipment (e.g.
Safety interlocks may have been assigned 4, HVAC control 10, and user overrides 16). The specification for the site
should therefore be sought before assigning any write priorities.
The gateway defaults to no write priority being used (Which in most cases will result in the target device interpreting
the write as a write priority 16 request).
To specify the BACnet write priority:
1. Run IQSET.
2. Ensure that the current user role is at least Commissioning engineer.
3. Right click the site, LAN, device or module for which the write priority is to be set, and click Set Write
Priority. If the priority is set to 'None' a dialogue box is displayed click OK to proceed. A dialogue box is
displayed.
4. Click the required option to select the required write priority. To use the same priority as the object
immediately above the selected object in the network structure select Using Parent Priority.
5. Click Apply. To apply the write priority to all item below the selected object in the network structure click
Apply to ALL children.
6. If Apply to ALL children was selected a dialogue box is displayed asking if you are sure you want to make
the change, click Yes.
7. Click Close.

General Operations
16.78 Specify the Next Module Number

The next module of each type that will be used is determined in the Next Module List. This contains the next module
of each module type. It also specifies the sequence step for the next module that is added to the strategy. The next
module numbers are automatically incremented when a module is placed on a strategy page. Sometimes the
application will demand that a specific module is used, or the module needs to occur in a specific place in the sequence
table. It is therefore possible to change the numbers to ensure that a specific module or sequence step is used.
To specify the next module number:
1. View the Next Module List.
2. In the Next box for the required module type or sequence step enter the required number.
16.79 Specify the Position of the Next Window
When a task that is performed displays a window the position of this window can be specified before it is displayed.
To specify the position of the next window:
1. Hold down the CTRL key and click the appropriate button ( , , , , , , , , or ). The
selected button will appear depressed.
Note: The buttons can still be used to position other windows.
16.80 Specify Which Configuration Parameters are Displayed
The configuration parameters that are displayed on a strategy page are determined by specifying the display parameters
for each module. When the module is first placed on a page, the default display options for that module type are used.
The default display options should be configured to suite your requirements for each module type (Loop, Sensor etc.).
To specify which configuration parameters are displayed:
1. Display the strategy page that contains the module for which the configuration parameters that are to
displayed are to be specified.
3. Click Display on the left of the required configuration parameter. Selected indicates that the parameter will
be displayed.
Icon Description
Checks all the check boxes
Clears all the check boxes
Returns the display settings to the current defaults.
4. Click OK.
16.81 Turn the Status Bar ON/OFF
To turn the Status Bar ON/OFF:
1. On the View menu click Status Bar to tick/untick the option; a tick ( ) indicates it is turned ON.

General Operations
16.82 Undo the Last Action

To undo the last action:
1. Press CTRL+Z, or on the Edit menu click Undo Last.
Note: The undo facility does not undo all actions.
16.83 Use the Connection Wizard
The Connection Wizard provides an easy of creating a connection to a Trend site. It does not display any TUA
information. If a site with specific TUA or connection to a vCNC using a host name is required, the TUA Editor must
be used.
To use the Connection Wizard:
1. Run the Connection Wizard. This will vary depending on the exact task that is being performed. See the
appropriate section of this manual for details. The Connection Wizard is displayed.
2. Select the Launching Site Connection Wizard (Recommended) option.

3. Click Next>. The wizard changes.
4. In the Site Name box enter the site's name.

5. Specify the connection as required. Local site with Ethernet connection, local site with serial connection,
remote site with an Ethernet connection, remote site with an ADL or SANC connection, remote site with a
serial auto dial connection, remote site with an Ethernet auto dial connection.

General Operations
To specify a local site with an Ethernet connection:
 Select the Local Site option.
 Select the Ethernet (TCP/IP) option.
 In the list select the IP adapter that is to be used to make the connection. If only one IP adapter is available
this step will be missed.
 In the list select the Trend system that is to be connected to by clicking on a device from that system.
Devices on the same system have the same UDP port. If only one Trend system is available this step will
be missed.
 Select the vCNCs that are to be used to make the connection.
To use an existing vCNC:
 Select the Choose from available VCNC ports option and click the vCNC from the list. To select more
than one press CTRL and click the required vCNCs.
vCNCs from the device selected in the previous step are already selected. If there are no vCNCs in that
device vCNCs from another device on the same UDP network are selected. If more than one vCNC is
selected. they must all be from the same device.
Note: The vCNC is referenced using the IP address of its device NOT the host name. If the hostname is
to be used the connection must be specified using the TUA Editor.
To create and use IQSET's own vCNC:
 Select the Create an integrated SET VCNC port option, in the Lan box enter the vCNCs LAN address
(range 1, 4-9, 11-119, 125), and in the Node box enter its network address (range 1, 4-9, 11-119, 125).
To specify a local site with a serial connection:
 Select the Local Site option
 Select the Serial Port (COM Port) option.
 In the Please choose the Baud Rate you want to use list In the Baud rate box select the baud rate for
communications between the personal computer and the device. It must match the value set on the
device. When connection is made directly, this should be 9600.
 In the Please choose the COM port number you want to use list select the number of the COM port
connected to the device.
To specify a remote site with an Ethernet connection:
 Select the Remote Site option.
 Select the Connect to remote IP device via Ethernet option.
 In the Device Address box enter the IP address or host name of the device containing the virtual CNC
that is to be used to connect to the Trend network. If entering an IP address, it must be entered in the
format shown below.
xxx.xxx.xxx.xxx
E.g.
128.1.24.34.
 Specify the port numbers of the virtual CNCs to which to which the IQSET may connect by adding them
to the Remote IP Port List box. To add a port to the list, enter the required number into the box to the
right of Add and click Add. To remove a port from the list, select it in the Remote IP Port List box,
and then click Remove.
The software will be able to connect to the Trend network using any of the ports in the specified range.
Because each port has a specific address on the Trend network, the address of software on the Trend network
will vary depending on which port it uses. If alarms are to be sent to the software a single port should be
specified to ensure that the same network address is used.

General Operations
To specify a remote site with an ADL or SANC connection:
 Select the Dial into a remote site option.
 Select Auto Dial Lite (ADL) or Software ANC (SANC).
 In the Please provide the telephone number you want to dial into box enter the phone number of the
site that is to be connected to. The number may be up to 20-characters in length, and include the following
characters.
Item Description
0 to 9 Dialing characters.
ABCD#* Considered as dialing characters on some systems.
J or : Wait for secondary dial tone.
K or ; or , 2 second pause (Note on some autodiallers this may be a 1 second pause).
<- Pulse dialing.
M or = Tone dialing
To use a previously used number, click to display the Telephone Number dialogue box, click the
required number and then click Select.
 In the Please choose the Baud Rate you want to use list In the Baud rate box select the baud rate for
communications between the personal computer and the modem. For ADL, it should be 2400.
connected to the modem.
To specify a remote site with a serial auto dial connection:
 Select Auto Dial (TMN etc). This enables connection using TMN, MNC, TMNE, ANC, or XN28.
characters.
Item Description
<- Pulse dialing.
M or = Tone dialing
 Select the Serial Port (COM Port) option.
 In the Please choose the Baud Rate you want to use select the baud rate for communications between
the personal computer and the modem.
connected to the dialling device.
 In the list select the required dialler. The list can be filtered by dialler type by selecting the required
dialler type in the Filter by box. If only one dialler is available this step will be missed.
To specify a remote site with an Ethernet auto dial connection:

General Operations
 Select Auto Dial Lite (ADL).
characters.
 Select the Ethernet (TCP/IP) option.
 In the list select the Trend system that is to be connected to by clicking on a device from that system.
Devices on the same system have the same UDP port. If only one Trend system is available this step will
be missed.
 Select the Choose from available VCNC ports option and click the vCNC from the list. To select more
than one press CTRL and click the required vCNCs.
vCNCs from the device selected in the previous step are already selected. If there are no vCNCs in that
device vCNCs from another device on the same UDP network are selected. If more than one vCNC is
selected, they must all be from the same device.
Note that the vCNC is referenced using the IP address of its device NOT the host name. If the hostname
is to be used the connection must be specified using the TUA Editor.
 In the list select the required dialler. The list can be filtered by dialler type by selecting the required
dialler type in the Filter by box. If only one dialler is available this step will be missed.
6. Click Next>. The wizard changes to show a summary of the site and its connection.
7. Click Finish.
16.84 Use the BUA Editor
The BACnet Universal Editor (BUA Editor) enables connection details to be specified for BACnet sites.
To use the BUA Editor:
1. In the Site name text box enter a name for the site.
2. Click the Connection tab.

General Operations
3. Click either Server, or Client to specify whether the connection is a server or client. When set to Server,
information will only be accessible by BACnet clients. When set to Client information can be received from,
and sent to other BACnet devices (servers).
4. In the PortId box enter select the port number used to connect to the BACnet network this is normally '2'.
5. In the Nwrk Number box enter the network number of the BACnet network.
Note: Both the port number and network number must match the ones setup in the BACnet Stack.
6. Click OK.
For full details of using the BUA Editor see the BACnet Universal Address Editor Manual (TE200736).
16.85 Use the TUA Editor
The TUA Editor enables connections to the Trend system to be specified. It allows TUA strings to be quickly and
easily specified, allowing any physical Trend System item to be targeted
To use the TUA Editor:
1. Run the TUA Editor. This will vary depending on the exact task that is being performed. See the appropriate
section of this manual for details. The TUA Editor Window is displayed.
2. In the Site name text box enter a name for the connection.
3. Set up the CNC tab to define the connection.
 Click the CNC tab.
 Click the appropriate option to specify the type of connection that is to be used. The display will change
to display the parameters that need to be set up for the selected type of connection.
Connection Description
Serial Specifies connection to the Trend network using a serial port connection.
Specifies connection to the Trend network using a virtual CNC in a device such as IQ3
TCP/IP
controller or EINC over Ethernet (TCP/IP).
Specifies connection to the Autodial Lite Trend network with a personal computer
ADL
modem.
Specifies connection to the Trend network using a software ANC. This uses a personal
SANC computer modem for communications. The modem may connect to sites with ANC/TMN
controllers as their autodialled connection.
Specifies connection to the Trend network using a serial port connection, to a site accessed
over an autodialled link using an autodialling device on the Trend network. When selected
Serial+TMN
an additional tab Auto dialing is displayed. The information in this tab must also be set up
for the connection to work.
Specifies connection to the Trend network using a controller or XTEND over Ethernet
(TCP/IP) to a site accessed over an autodialled link using an autodialling device on the
TCP+TMN
Trend network. When selected an additional tab Auto dialing is displayed. The
information in this tab must also be set up for the connection to work.
 Specify the settings for the selected connection, Serial or Serial+TMN, TCP/IP or TCP+TMN, ADL
or SANC.

General Operations
Serial or Serial+TMN
 In the Baud rate box select the baud rate for communications between the personal computer and
the device. It must match the value set on the device. When connection is made directly, this should
be 9600.
 In the COM port number box enter the number of the COM port connected to the device.
 Check that the TUA Cnc data is valid check box is selected.
TCP/IP or TCP+TMN
 In the Device address box enter the IP address or host name of the device containing the vCNC that
is to be used to connect to the Trend network. If entering an IP address, it must be entered in the
format shown below.
xxx.xxx.xxx.xxx
E.g.
128.1.24.34
 Specify the port numbers of the virtual CNCs to which to which the software may connect by adding
them to the Remote IP port list. To add a port to the list, enter the required number into the box
above Add and click Add. To remove a port from the list, select it, and then click Remove.
If the list is empty, there will be no ports will be available used. If ports are specified in the list, then
only those in the list can be used to make the connection. The software will be able to connect to the
Trend network using any of the ports in the specified range. Because each port has a specific address
on the Trend network, the address of software on the Trend network will vary depending on which
port it uses.
If alarms are to be sent to the software a single port should be specified to ensure that the same
network address is used.
ADL or SANC
 In the Baud rate box click the baud rate for communications between the personal computer and
the modem from the list. For ADL, it should be 2400.
 In the COM port number box enter the number of the COM port connected to the modem.
 In the Site phone number box enter the phone number of the site that is to be connected to. The
number may be up to 20 characters in length.
Characters Description
< Pulse dialing
M or = Tone dialing.
 If required enter the phone number of the personal computer in the personal computer phone
number (optional) box. This can include the same characters as the site phone number.
 In the Link Pin box enter the four-digit code used to authorise the use of the CNC link.
4. If displayed, set up the Auto dialling tab to specify the autodialled connection. Ensure that the TUA auto
dialling data is valid check box is selected.
To set up the Auto dialing tab:
 Click the Auto dialing tab.
 Click the appropriate option to specify the type of dialler that is to be used.
Dialler Description
ANC Restricts the autodialling devices that can be used to the ANCs on the network.
ANY Enables any autodialling device on the network to be used.
MNC Restricts the autodialling devices that can be used to the MNCs on the network.
TMN Restricts the autodialling devices that can be used to the TMNs (not TMNE) on the network
TMNE Restricts the autodialling devices that can be used to the TMNEs on the network.
XN28 Restricts the autodialling devices that can be used to the XN28 s on the network.

General Operations
Note: If a TMNG is being used you should select ANC.
 In the Phone / connection number box enter the phone number of the site that is to be connected to.
The number may be up to 20-characters in length.
< Pulse dialing
M or = Tone dialing.
 Specify which autodialling devices can be used to make the connection to the specified number by adding
them to the Dialler List. To add a device to the list, enter the network address into the box above Add
and click Add. If the list is to specify diallers that CANNOT be used, the address should be prefixed
with a minus sign ‘-’. If the autodialling device is on the internetwork, select the check box next to it in
the list. To remove a device from the list, select it, and then click Remove.
If the list is empty any dialler that matches the technology type specified (Any, TMN, MNC, TMNE,
ANC, or XN28) will be used. If devices are specified in the list, then only those devices will be used to
make the connection. If required, the list can specify devices that cannot be used.
Note: Positive and negative addresses cannot be mixed in the list (the list can only contain either devices
that can be used or devices that cannot be used).
5. If the TUA requires a non-standard retry time or number of retry attempts to be specified, set up the
Messaging tab.
To set up the Messaging tab:
 Click the Identification tab.
 Click Show advanced settings. The TUA Editor Window is expanded to show the advanced settings.
 Click the Messaging tab.
 In the Retry time (secs) box enter the time in seconds between retries if a message has failed. The default
is 5 seconds, unless the connection is using an autodialled link (not ADL connection) in which case it is
15 seconds.
 In the Max number of attempts box enter the maximum number of times that an attempt to send a
message. The default is 3.
6. Click OK.
For full details of using the TUA Editor see the Universal Address Editor Manual (TE200445).

General Operations
16.86 Upgrade IQ3 Controllers

It is possible to upgrade the firmware and any other associated files in IQ3 controllers leaving the strategy unaffected.
When upgrading controllers in the way described below everything in the controller except the firmware, alarm log,
and logged data is backed up. The strategy is then removed from the controller while the upgrade takes place. The
files used for the upgrade are obtained from a specified directory known as the 'Autosetup' directory. Once the upgrade
is complete the strategy will be copied back into the controller and restarted.
Note: If you wish to upgrade the controller but do not want to copy the strategy back into the controller you should
clear the Restore Strategy to Controller after Upgrade check box in the Advanced Settings dialogue box.
The backed-up information is stored in a directory known as the ‘Backup Root’ directory. The information for each
controller is stored in its own uniquely identified directory within the ‘Backup Root’ directory in the structure shown
below:
IQ3 Backup
|----Site Name
|----Date and Time
|----L<xxx>n<yyy> <Identifier> <IP Address>
Where <xxx> specifies the LAN number of the controller, <yyy> specifies the network address of the controller;
<Identifier> and <IP Address> are the controller’s identifier and IP address as defined in the address module.
Caution
Because of the nature of the upgrade process if the controller loses power during the upgrade process the
upgrade will fail and the controller will probably no longer function and will need to be replaced.
It is not possible to upgrade the controller remotely over an IP connection that uses a dial up modem router.
Upgrading the controller requires a high integrity IP link to the controller as loss of connection could leave the
controller in a state where it is not controlling the plant. For this reason, remote upgrading is not recommended,
and upgrading over a dial up modem link is not supported.
The process of upgrading controllers with pre-version 1.01 firmware can be unreliable. If you experience
problems upgrading these controllers it is recommended that you use a crossover adaptor to directly connect
to the controller. For more details of upgrading version 1.00 controllers see the ‘Upgrading pre-version 1.01
Controllers’ section of this manual.
The upgrade process will cause any logged data and the alarm log to be lost.
To perform an autosetup upgrade:
1. If you wish to keep the sensor logs from the controller record them using 963 or another suitable tool.
2. Ensure all pending alarms are sent to a supervisor.
3. Obtain the zip file that contains the files necessary to perform the autosetup update and unzip it into an empty
directory on your PC. This directory is the one you should specify as the Autosetup directory.
4. Run IQSET and view the site containing the controllers on the Trend system that are to be upgraded.
5. Right-click on a controller that is to be upgraded, or the LAN containing controllers that are to be upgraded
and click Upgrade Controller. The TsetIq3Upgrader Warning dialogue box is displayed.

General Operations
be used to authorise the upgrade. This must match with one in the controller and be of level 90 or above to
enable the upgrade.
If there are no users set up in any of the controllers that are to be upgraded a username and password is still
required if this is the case use 'IQ3' as the username, and ‘user’ as the password.
9. If upgrading to controllers with version 1.3 firmware or greater in the Pin box enter a PIN. This must match
with one in the controller and be of level 90 or above to enable the upgrade.
Note: If more than one controller is being upgraded, only one username, password and PIN can be specified,
if the controllers have different usernames passwords, and PINs the process will fail. It is therefore
recommended that all the controllers on a system have the same username, password and PIN.
If you want the username, password and PIN to be remembered for the next session select the Remember
Username, Password, and Pin check box.
11. Click next to the Backup Root box and select the required directory from the dialogue box that is
displayed to specify the Backup Root directory that is to contain all the backups of the files from the
controllers.
12. Click next to the Autosetup Folder box and select the required directory from the dialogue box that is
displayed to specify the Autosetup directory that containing the new firmware and other associated files.
13. Clear the Enable Advanced Settings dialogue box.
14. Click on OK to return to the IQ3 Upgrade Window.
15. If necessary add other controllers that are to be upgraded to the list by navigating down the site to locate the
controllers, and dragging them onto the IQ3 Upgrade Window. Clicking Clear List clears the list.
16. Select the controllers in the list that are to be upgraded, by clicking the check box next to them. Clicking
Select All will select all the devices in the list.
It is recommended that initially you only upgrade one controller at a time until you are confident that the
upgrade process will complete successfully, and not cause any problems.
17. Click Check Comms to check that there is an Ethernet connection with each of the selected controllers. Each
of the selected controllers will now be pinged to check that it is there.
18. Click Upgrade. A dialogue box is displayed informing you what the applet is about to do and asking if you
are sure you want to proceed with the upgrade.
Note: If any of the controllers being upgraded has pre-version 1.01 firmware an additional warning box is
displayed. This warns of the problems that may be encountered upgrading pre-version 1.01 controllers.
19. Click Yes. The upgrade will be carried out the progress of which is displayed in the progress bars in the
Controller List and at the bottom of the window. Clicking Abort stops the upgrade process. If a controller
is in the process of being upgraded that upgrade will be completed before the process is aborted.
20. Once the upgrade is complete a dialogue box will be displayed. Click OK.
21. Verify that the controller(s) can still be accessed by deleting the internetwork from the System View and
then refreshing the entire LAN structure to check that the controller is still communicating over the Trend
network.

General Operations
22. For each upgraded controller confirm that the version number reports as expected on the web pages and that
the strategy and backdrops are in place.
16.87 Upload Strategy from an IQ Controller
IQSET can upload strategy from IQ controllers over a network, or from a directly connected controller. It uploads the
strategy in different formats depending on the controller. For IQ3 controllers it uploads IQ3 files, for IQ4 controllers
it uploads IQ4 files, for IQECO controllers it uploads IQe files, for pre IQ3 controllers with firmware earlier than v2.0
it uploads SCN files, and for other pre IQ3 controllers it uploads IQ2 files. The file is named in the following format:
L<xxx>n<yyy>.zzz>
Where <xxx> specifies the LAN number of the controller. <yyy> specifies the network address of the controller.
<zzz> indicates the file format (IQ4, IQ3, IQe, IQF, or SCN), e.g. L099n020.IQ4 would be the file name given to the
Note: If uploading from IQ4 and IQ3 controllers the uploaded file will contain the IP address and LAN and network
address numbers.
To upload strategy:
1. Connect the PC running IQSET to the Trend network, or directly connect to the controller’s supervisor or
direct connection port using a suitable cable as described in the controller’s documentation.
2. Display a strategy page from the controller whose strategy is to be uploaded.
3. Click , or on the Comms menu click Upload. The Connection Details dialogue box is displayed. IQSET
automatically inserts the LAN number, and address of the controller whose strategy file is to be uploaded.
7. If a different comms connection is to be used select the required one from the Standard Comms box. If none
of the standard connections are suitable the connection can be specified by clicking Edit Connection Details.
This displays the Connection Wizard which enables the connection to be specified using the TUA Editor
or the Connection Wizard.

General Operations
comms connections.
8. Click OK.
connecting. If they don't match a dialogue box asking if you want to continue is displayed. Click OK to
IQSET will check that the controller's time is within one minute of the PC time if there is a difference. If
there is a difference a dialogue box asking if you want to set the controller's time to match the PC is displayed.
Click Yes to adjust the time or No to leave the controller's time unchanged.
The File Upload dialogue box is displayed.

General Operations
Note that the appearance of this dialogue box is different for different type of controller.
9. The directory to which the uploaded file is stored is automatically determined but can be changed if required.
To specify the download directory:
 Click Change or . The Browse For Folder dialogue box is displayed.

 Click OK.
10. To force the use of IQF protocol select Use IQ Lan.
11. Specify whether the strategy file is to be uploaded by selecting the Strategy File check box.
12. If uploading from IQ4 or IQ3 controllers specify whether the backdrop files required for the graphical display
pages are uploaded by selecting the Backdrops check box.
Note: Backdrop files cannot be uploaded using the current loop. The use of backdrop files larger than 100k
is not recommended. Backdrops bigger than 200k will be prevented from being uploaded, the total size used
by all backdrops in the controller limited to 2Mb.
13. If uploading from IQ3 controllers with version 1.1 firmware or greater specify whether the language files
used for the display of web pages and alarms are uploaded by selecting the Language Files check box.
Note: Language files cannot be uploaded using the current loop.
14. If uploading from IQ3 controllers with version 1.3 firmware or greater that have the XNC functionality
enabled specify whether the TCL program (.XNC file) is to be uploaded by selecting the XNC File(s) check
box.
Note: The XNC file cannot be uploaded using the current loop.
15. If uploading from IQ1 and IQ2 version <= 2.0 controllers the Get IQF and Send SCN options are displayed
select the required option. By default, IQSET uses IQF files for IQ2 controllers earlier than v2.
16. Specify whether the window is to be closed when the upload is complete by selecting the Close this dialogue
box when upload completes check box.
17. Click Start to begin the upload. The progress is indicated at the bottom to the dialogue box. Clicking Stop
will stop the upload. Once the upload is complete the text 'Upload Complete is displayed at the bottom of the
dialogue box. If the upload fails, or is stopped, the Start button will change to Retry, clicking Retry; will
attempt the upload again.
If IQSET is directly connected controller, the LAN, and Node settings are ignored, and the strategy will be
sent to the controller to which IQSET is connected. However, if it is connected to an IQ2 controller whose
supervisor port has been set up to allow communication over the network, the LAN, and Node settings will
be used, and the strategy uploaded from the specified controller over the network.

General Operations
16.88 View BACnet Communications

The communications IN and OUT of the node the application is using to connect to the BACnet network can be
displayed in the BACnet Communications Window. The BACnet Communications Window is described in more
detail in the ‘The BACnet Communications Window’ section of this manual.
To view the BACnet Communications Window:
1. Browse the system to display the required BACnet site in as described in the System View.
2. Right-click the site name, and click Comms Window. The BACnet Communications Window is displayed.
Communications IN are on the left, and communications OUT are on the right. Each of the boxes has
horizontal and vertical scroll bars, which enable more information to be accessed. To close the window, click
at the top right of the window. The display can be cleared by right clicking in the main area of the window,
and clicking Clear entries from the displayed menu. The communications can be paused, logged to file,
blank lines inserted, and more details about a frame can be viewed by double-clicking the frame. The display
format can also be specified.
16.89 View Device Details
It is possible to view information about devices in the network structure.
To view details for a device:
1. Display a strategy page for which details are to be viewed.

General Operations
16.90 View LAN Details

It is possible to view information about the LANs in the network structure.
To view details for a LAN:
2. In the Device View right-click the LAN for which details are to be viewed, and click LAN Details. The Lan
Details dialogue box is displayed.
16.91 View Page Details

Information about when a strategy page was created, and modified is stored. The text information can be used to store
reminders about things that need to be done to the strategy on that page.
To view page details:
2. Click , or in the Device View right-click the page for which information is to be viewed, point to Page and
click Page Details. The Page Info dialogue box is displayed.

General Operations
16.92 View Project Details

It is possible to view information about the current project.
To view details for the current project:
2. In the Device View right-click the project name, and click Project Details. The Project Details dialogue
box is displayed.
16.93 View Strategy Block Details

Information about a strategy block can be viewed. This information is user definable, and could be used to describe
how the strategy works.
To view the details for a strategy block:
2. In the Strategy Blocks Area, right-click the strategy block for which details are to be displayed, and click
Details. The Strategy Block Details dialogue box is displayed.
16.94 View Strategy Block Page Details
To view strategy block page details:
1. Open a project.
3. Right-click the strategy block page whose details are to be displayed, and click Properties. The Page
Properties dialogue box is displayed.

General Operations
16.95 View Strategy Issues

The issue details enable a record of changes made to the strategy to be kept. They describe the current issue, and
contain a description of the changes made since the previous version. These details are included on the strategy pages
for the controller when they are printed out.
Note: The latest information is used for the print out.
To view issue details:
1. Display a strategy page for the controller for which issue details are to be viewed.
2. Right-click the page and click Issue Details, or the Device menu click Issue Details. The Issue Details
3. In the Number box use the arrows to select the required issue.
4. In the Revision box use the arrows to select the required revision.
16.96 View the Next Module List
When configuring a controller, it is possible view a list of modules that indicates the next module number for each
module type, and the next sequence step that will be used. It also shows how many modules of each module type are
still free for use.
To view next module list:
1. Display a strategy page for the controller for which the list is required.
2. Click , right-click the page and click Next Module, or on the Tools menu click Free/Next Module List.
The Next Module List dialogue box is displayed.

General Operations
16.97 Zoom IN/OUT

IQSET enables the strategy page to seen in more detail by zooming IN/OUT. One of the standard magnification levels
can be used, or you can zoom into a specific area.
To use one of the standard magnification levels:
2. On the View menu click the required magnification level. For example, to zoom to 2 times size, On the View
menu click Zoom 200%.
To zoom to a specific area:
2. Click , or on the View menu click Zoom Window, or right-click the strategy page (not on a module) and
click Zoom Window. The pointer changes to a magnifying glass. .
3. Hold down the left mouse button, and drag over the required area (indicated by a rectangle).
4. Once the required area is surrounded by the rectangle, release the mouse button.
Note: The Command Line toolbar’s command ZOOM can be used to perform this function from the Command
Line toolbar.
To fill the window with the used area of the strategy page:
2. Right-click the strategy page (not on a module), and click Zoom Extent.
Note: The Command Line toolbar's command EXTENT can be used to perform this function from the Command
Line toolbar.
To zoom with a mouse wheel:
2. Hold down the CTRL key and use the mouse wheel to zoom in and out. Moving the mouse around changes
the centre point of the zoom.
To zoom to a corner:
2. Click the icon, or press the appropriate function key.
Icon/Function Key Description

/F5 Zooms to the top left corner
/F6 Zooms to the top right corner
/F7 Zooms to the bottom left corner
/F8 Zooms to the bottom left corner

To return to actual size:
2. Click , or on the View menu click Zoom 100%, or right-click the strategy page (not on a module) and
click Zoom Extent from the menu that is displayed.

Browse the System
17 BROWSE THE SYSTEM

This section describes how to browse the system, and perform tasks, such as entering configuration mode on the
device, sending text comms, or displaying a map of the LAN.
There is a summary of using IQSET to browse system in the following section:
Basic Browsing
For a more detailed description of the different tasks, see the appropriate section of this manual.
17.1 Basic Browsing
This section describes the basic principles of browsing the system with the System View.
To browse the system:
1. Connect to the network.
2. Add Sites to the System View
3. Connect to the site.
4. Navigate down the tree structure to locate to display the required information. Objects with a + next to them
can be expanded by clicking + to reveal what is below them in the structure. IQSET will automatically learn
the system structure of the next level, and display it.
Note: If user nodes are being viewed, it may be necessary to turn on the automatic refresh.
If the object has not been identified, right-click and click Refresh, to identify the selected object, or click
Refresh all to identify all the objects on the next level down in the structure.
5. Once you have reached the required part of the system, you can run an applet by right-clicking it, and clicking
the required task.
It is possible to specify the location of the window that is displayed. Once displayed it is possible to position the
window.
17.1.1 Connect to a Network
IQSET can communicate over a Trend Network or a BACnet Network.
17.1.1.1 Connect to the Trend Network
If IQSET is to communicate with IQ controllers to upload /download files or to access controllers in configuration
mode, it is necessary for IQSET to be connected to the controllers, over the Trend network or directly. Connection to
the network can be made:
over Ethernet
over the Trend system current loop
using a software ANC (SANC)
over USB
17.1.1.1.1 Connect over Ethernet
IQSET can be connected to the Trend network over Ethernet using a standard Ethernet connection; this allows the
office IT network to be used to connect to the Trend network. Connecting in this way requires the use of a device
(which must be purchased separately) containing a virtual CNC (vCNC).
To connect to the Trend network over Ethernet:
1. If necessary install a device that contains a vCNC and ensure that a vCNC set up to operate in supervisor
mode. For details of this installation instructions supplied with the product.
2. Fit a standard Ethernet adaptor to the PC, following the PC manufacturer’s instructions, and the instructions
supplied with the adaptor.
3. Make the connection to the Ethernet network by plugging the Ethernet network cabling into the Ethernet
card, or if connecting to a wireless network configure the PC to connect to that network.
4. Configure Windows Networking to suit the Ethernet network.
Note: Assistance from the IT department responsible for the Ethernet network will normally be required.
5. Add a Trend system site connecting to the required vCNC.

Browse the System
17.1.1.1.2 Connect Using USB
IQSET can be connected to the Trend network over USB using a standard USB cable connected to an IQECO 31, 35,
38 or IQ4s engineering port.
For IQECO controllers when IQSET is connected in this way a temporary supervisor CNC (sCNC) is created at
address 125. This sCNC will appear on the local LAN and will give access to the other Trend devices on the MS/TP
trunk. When an IQ4NC is present, the sCNC will give access to the rest of the Trend system. If the PC running IQSET
is disconnected, then the temporary sCNC disappears.
For IQ4 controllers when IQSET is connected in this way a temporary supervisor sCNC is created at address 125 if
the address is not specified in the controller's address module. If the address is specified that address will be used.
This sCNC will appear on the local LAN and will give access to the rest of the Trend system. If the address is not
specified when the PC running IQSET is disconnected, then the temporary sCNC disappears.
To connect to the Trend Network using USB:
1. Connect a standard USB A to Micro USB B cable from the PC running IQSET to the IQECO's or IQ4's
engineering port.
 On all supported operating systems, see IQSET Data Sheet (TA200131), except Windows 8, Windows
8 Pro and Windows 8 Enterprise the first time you connect the driver will be automatically installed. For
windows 8 systems the driver must be manually installed.
 The driver will appear in the Device Manager under 'Ports (COM & LPT)' as 'Trend Controls IQECO
Supervisor Port (COM<n>) or 'Trend Controls IQ4 Supervisor Port (COM<n>) where <n> indicates the
COM port assigned to the driver.
 Make a note of this number as it will be need when connecting.
Note: A different driver is used for IQECOs, and IQ4s therefore the port number will be different.
2. Set up a standard serial comms connection using the COM port used by the USB connection at any baud rate
to connect to the controller's local supervisor port.
3. Add a Trend system site using the connection set up above.
17.1.1.1.3 Connect over the Current Loop
IQSET can be connected to the Trend network over the Trend system current loop using either a node controller e.g.
an NBOX/CNC2, or an IQ controller using the controller’s local supervisor port.
Note: If connecting to a controller, whose local supervisor port does not allow access to the Trend network, it will
only be possible to communicate with that controller, and the Direct Connection check box in the Connection Details
dialogue box must be selected when you attempt to make the connection.
To connect to the Trend Network over the current loop:
1. If necessary install the controller, or node controller as described in the installation instructions supplied with
it.
2. Connect the COM port being used to the controller’s local supervisor port, or the node's RS232 port using
the appropriate cables. For full details of connecting to specific controllers/node controllers refer to the
installation instructions for that device.
3. Set up a standard serial comms connection to connect to the controller’s local supervisor port, or the node's
RS232 port.
If connection to an autodialled site is required a TCP+TMN connection must be used instead. This allows
the connection to the controller's local supervisor port, or the node's RS232 port, the dialling device that is to
be used to make the connection, and the telephone number of the site to which the connection is required to
be specified.
If connection to a /ADL device is required, an ADL connection must be used instead. This allows the
connection to the controller’s local supervisor port, or the node’s RS232 port, and the telephone number of
the ADL device to which the connection is required to be specified.
4. Add a Trend system site using the connection set up above.
17.1.1.1.4 Connect using a SANC
A directly connected modem, connected to a landline, can be used to dial out to a modem on a specified Trend network
using a software ANC (SANC).
To connect to the Trend network using a SANC:
1. Fit a standard PC modem card into the PC, following the PC manufacturer's instructions for fitting an
expansion card, and the instructions supplied with the modem card.

Browse the System
Note: The modem must be a standard V90 modem (56K), and the Trend network to have an autodialling
device to which the PC can dial in.
2. Install the drivers for the card.
3. Connect the PC modem card to the telephone socket as described in the instructions supplied with the card.
4. Set up a standard SANC comms connection. This allows the modem, and the telephone number of the site to
be specified. TCC will set the modem up as required, but should you not be able to connect using SANC
ensure that the modem has the correct parameters defined.
Setting Value AT Command
Modem text messages ON ATV1
Speed of the serial port Locked AT&B1
Hardware (RTS/CTS) data flow control ON AT&H1
DSR when connected (DSR follows carrier) ON AT&S1
DCD control (DCD follows carrier) ON AT&C1
Error detection OFF AT&M0
Stores the settings in non-volatile memory profile 0 AT&W0
Stores the settings in non-volatile memory profile 1 AT&W1
Before making any of these changes it is recommended that the modem be rest to the factory default settings
(AT&F). After the settings have been made, the modem must be set to use the new settings (ATZ).
Note: The AT commands described above are for a US Robotics 56JK Faxmodem.
5. Add a Trend system site using the connection set up in above.
17.1.1.2 Connect to the BACnet Network
If IQSET is to communicate with a BACnet network the PC running IQSET must be connected to an Ethernet network
that has access to the BACnet network.
To connect to the BACnet network:
1. If necessary fit a standard Ethernet adaptor to the PC, following the PC manufacturer's instructions, and the
instructions supplied with the adaptor.
2. Make the connection to the Ethernet network by plugging the Ethernet network cabling into the Ethernet
card, or if connecting to a wireless network configure the PC to connect to that network.
3. Configure Windows Networking to suit the Ethernet network.
4. Ensure that the BACnet network driver has been installed.
5. Add a BACnet site using the connection set up above.

Browse the System
17.1.2 Add Sites to the System View
IQSET can connect to two different types of sites, a Trend System site, and a BACnet site. A Trend system site
specifies how IQSET communicates with a specific part of the Trend network. A BACnet site specifies how IQSET
communicates with a BACnet network.
If you want to browse the system you must add sites to the System View. This can be done in several ways from the
SET dialogue box or from the IQSET Window:
From the SET dialogue box:
Adding a Live Site without Creating a Site File
Add a Site and Create a Site File
Add a Site by Loading a Site File
From the IQSET Window:
Add a Site From the IQSET Window
17.1.2.1 Add a Site without Creating a Site File
IQSET can be run and connected to a live site without a site file being loaded or created.
To run set and connect to a live site:
1. Run IQSET and log on, or select the File menu and click Open/New Project. The SET dialogue box is
displayed.
2. Click Live Site.

Browse the System
3. Click OK. The Site Connections dialogue box is displayed.
4. In the Standard Comms Connections box click the required connection for the site. If none of the standard
connections are suitable the connection can be specified by clicking Edit Connection Details. This displays
the Connection Wizard which enables the connection to be specified using the TUA Editor or the
Connection Wizard.
comms connections.
5. Click OK. The site is added to the System View.
When a site is first added to the System View it does not automatically connect and learn the devices on the
site, it is necessary to make the connection manually.
6. Right-click the site click Refresh. IQSET will connect to the site and learn the top level of the site structure.
If connecting to a vCNC IQSET may prompt for additional information or display a message before allowing
the connection - see Connect to a site.
17.1.2.2 Add a Site and Create a Site File
A site file stores information about the devices on a site, and modules in those devices, as well as the connections for
the site. This process will create a blank site file, and IQSET can then browse the system to find out what devices are
available, and add them to the file.

Browse the System
To create a site file:
displayed.
2. Click Create New Site File.

3. Click OK. The SET Project dialogue box is displayed.
4. In the Project Name box enter a name for the project. If required the directory that the file is saved in can
be changed by clicking Change browsing to the required directory, and then clicking OK.
5. Click OK. The Site Name dialogue box is displayed.
6. In the Site Name box enter a name for the site. To change the location of the project click Change.
7. In the Type box select Trend.
8. Click OK. The Connection Wizard is displayed which enables the connection to be specified using the
TUA Editor or the Connection Wizard.
To specify the connection using the TUA Editor:
To specify the connection using the Connection Wizard:

Browse the System
comms connections.
9. Click OK. The Site Connections dialogue box is displayed.
10. Click OK. The site will be added to the System View and a site file created.
11. Right-click the site and click Refresh. IQSET will connect to the site and learn the top level of the site
structure. If connecting to a vCNC IQSET may prompt for additional information or display a message before
allowing the connection - see Connect to a site.
17.1.2.3 Add a Site by Loading a Site File
A site file stores information about the devices on a site, and modules in those devices, as well as the connections for
the site. If required a site file can be opened, enabling access to information about the site without having to refresh
objects, and saving time on unnecessary communications.
To load a site file:
displayed.
2. Select the required file.

To load any site file:
 Click Open Existing Site File. A list of the existing site files is displayed in the bottom of the dialogue
box.
 In the list at the bottom of the dialogue box click the required site file. To display a list of files in another
directory click Change, navigate to the directory containing the required project and click OK. The site
file should now appear in the list. To open a file not in the list, click More Files then click OK to display
the Open dialogue box, click the required file and click Open. To select a file stored in a different
location, click the drive, or folder in the Look in box that contains the file, double-click the folders in
the folder list until file is displayed.
To load a recent site file:
 Click Open Recent Site File.

Browse the System
 In the list at the bottom of the dialogue box click the required file. To display a list of files in another
directory click Change, navigate to the directory containing the required project and click OK.
3. Click OK. The selected site(s) specified by the site file will be loaded into System View.
If connecting to a vCNC operating in 'Secure' mode you will be prompted for the user name and password of
a CNC User module in the device. For other scenarios IQSET may prompt for other information or display
a message before allowing the connection - see Connect to a site.
17.1.2.4 Add a Site From the IQSET Window
To add a site from the IQSET Window:
3. Use your preferred method to add the site.
From the Project menu:
 On the Project menu click Sites. The Site Connections dialogue box is displayed.
 For Trend System sites, if the site is to use one of the standard comms connections select the required
connection in the Standard Comms Connections box.
 Click Add. The Site Name dialogue box is displayed.
 In the Site name box enter a name for the site.

 In the Type box select the type of site that is to be added.
 Click OK. If a Trend site was selected the Connection Wizard is displayed. If a BACnet site was
selected the BACnet Universal Address Editor dialogue box is displayed.

Browse the System
From the System View:
 In the System View right click Sites and click New Site. The Choose Type of site dialogue box is
displayed.
 In the Choose type of network box select the type of site that is to be added.
 Click OK.
If a Trend site was selected the New site connection details dialogue box is displayed.
 In the Site name box enter a name for the site.
 If the site is to use one of the standard comms connections select the required connection in the
Related connection box, and click OK, the site will be added to the System View. If the site is not
to use one of the standard connections, click Edit site details to display the Connection Wizard.
If a BACnet site was selected the BACnet Universal Address Editor dialogue box is displayed.
4. If the Connection Wizard or BUA Editor are displayed it is necessary to specify the connection. For
connections to a Trend network this is done using the TUA Editor or the Connection Wizard. For
connections to a BACnet network this is done using the BUA Editor.
To specify the connection using the TUA Editor:
Note: This is not necessary for Trend sites if a standard connection is being used. Connections specified here
will only be used for that site; it will not be added to the list of comms connections.
To specify the connection using the Connection Wizard:
 In the Site Name box enter the site's name.
To specify the BACnet connection:
 Use the BUA Editor to specify the connection.
After completing the steps above the site will have been added to the System View. When a site is first added
to the System View it does not automatically connect and learn the devices on the site, it is necessary to
make the connection manually.
If connecting to a vCNC IQSET may prompt for additional information or display a message before allowing
the connection - see Connect to a site.

Browse the System
17.1.3 Connect to a Site
IQSET needs to connect to a site to communicate with it. This may be initiate strategy upload/download, to retrieve
values from the system, perform a firmware upgrade etc or when a user manually refreshes a site. Sometimes IQSET
will connect to the site without any required action. However, if connecting to a vCNC IQSET may prompt for
additional information or display a message before allowing the connection.
Connect to a vCNC in 'Secure' mode with CNC users:
1. When IQSET attempts to make the connection the CNC User credentials dialogue box is displayed.
2. Enter the CNC User module's name in the Name box (user name of any CNC User module in the device
containing the vCNC).
3. Enter the CNC User module's password in the Password box (password for the CNC User module specified
above).
4. Click OK. The connection will be made.
Note: IQSET does not remember the security details between sessions so when connecting again after IQSET has
been started it will prompt for the username and password.
Connect to a vCNC in 'Secure' mode without CNC users:
1. When IQSET attempts to make the connection the Service Button Validation dialogue box is displayed.
2. Go to the device containing the vCNC and press its service button within 10 minutes to prove you have
physical access to the device. The Secure Site Configuration dialogue box is displayed which allows the
device's vCNC connections to be configured.

Browse the System
3. To continue with the just the existing vCNC in secure mode you MUST add a CNC User module,
alternatively you can configure the device's vCNCs.
To add a CNC User module.
 Enter the CNC User module's name in the Name box.
 Enter the CNC User module's password in the Password box
 Retype the password in the Retype Password box.
To configure the vCNC configuration.
 Specify whether the vCNC port number is to be manually specified or use the default value (10000 +
Address) by selecting/clearing the Use Default Port box.
 Enable/disable the required vCNCs by clearing/selecting the Disable check boxes, (selected = disabled).
 Specify the label for the vCNC in the Label box.
 Specify the network address of the vCNC in the Address box (range 1, 4 to 119 excluding 10). It must
be unique on the Local LAN.
 If the default port is NOT being used specify the port for the vCNC in the Port box.
 Specify the security mode in the Security Mode box.
 If any of the vCNCs are operating in 'Secure' mode and you have not already added a CNC User module
you MUST add one.
 Click Commit. A message is displayed once the changes have been successfully sent to the controller.
 Click to continue. If the CNC connection is still secure the CNC User credentials dialogue box is
displayed.
 Enter the CNC User module's name in the Name box (user name for the CNC User module that has just
been created).
 Enter the CNC User module's password in the Password box (password for the CNC User module that
has just been created).
 Click OK. The connection will be made.
Connecting to a vCNC that supports secure communications that is not operating in 'Secure SHH' mode:
1. When IQSET attempts to make the connection the Trend Security Warning dialogue box will be displayed.
2. Click to continue IQSET will connect securely (encrypted) without the need to specify a user name and
password.
Connecting to a vCNC that does not support secure communications:
1. When IQSET attempts to make the connection the Trend Security Warning dialogue box will be displayed.
2. Click to continue IQSET will connect.

17.1.4 Navigate the System
The Trend system can either be navigated by clicking the different areas of the system structure, to locate the required
part of the system, or by using the Item Selector.
To navigate the system by clicking the different areas:
1. Click + next to 'Sites' or 'User nodes' in the System View. If the required site is not available, a site should
be added.
2. Navigate down the tree structure to locate to display the required information. Objects with a + next to them
can be expanded by clicking + to reveal what is below them in the structure. IQSET will automatically learn
the system structure of the next level, and display it.
To navigate the system using the Item Selector:
1. Display the Item Selector.

Browse the System
2. In the list at the top of the Item Selector click the required site. If the required site is not available, a site
should be added.
3. In the Lan, Os and Mod boxes enter the required LAN number, network address, and module. It is only
necessary to specify the required level, e.g. if you want to view a specific LAN it is only necessary to specify
the LAN number.
The LAN number can be any integer in the range 0 to 119 excluding addresses 2, 3, and 10. 126 specifies the
internetwork. The network address can be any integer in the range 1 to 119 excluding addresses 2, 3, and 10.
The module specifies the type of module using its module identifier and module number (e.g., S1 specifies
sensor 1). For details of the module identifier see the appropriate module section of this manual.
4. Click Find. IQSET will go to the specified part on the system.
17.1.5 Refresh the System View
If required data in the System View can be refreshed manually.
To manually refresh data:
1. Right-click the object and click Refresh, to refresh the selected object, or Refresh all to refresh all the objects
on the next level down in the structure.
Clicking on has the same effect as clicking Refresh, and clicking has the same effect as clicking
Refresh all. To stop a refresh once it has been started click . To prevent automatic refreshing click
.
17.1.6 Run an Applet
Applets that are associated with a type of system object can be run from the System View or the Item Selector.
Applets that are not associated with a type of system object can be run from the Tools menu. This allows different
tasks such as entering configuration mode, or displaying information about a device, or uploading a file can be carried
out on the selected part of the system. The tasks that are available are dependent on the part of the system that is
selected. For example, if an IQ controller has been selected it is possible to go into configuration mode where as if a
LAN is selected, the LAN can be mapped.
Note: Applets are only accessible if the current user role is equal to or higher than that required for access to the
applet.
To run an applet from the System View:
2. Once you have reached the required part of the system right-click, and click the required applet.
To run an applet from the Item Selector:
1. Display the Item Selector.
2. In the Context box specify click the required part of the system. This tells IQSET what the object is e.g.
LAN, or device.
3. In the Action box click the required task from the list
4. Click Go.
To run an applet from the Tools menu:
1. On the Tools menu click the required applet.
If the applet opens a new window it is possible to move between then by clicking each window. The window can be
closed by clicking , or on the Window menu clicking More Windows to display the Arrange Windows dialogue
box, selecting the window in the list, and then clicking Close Window.
17.2 Configure an IQL Controller for use with an RD-IQL
If an RD-IQL is to be connected to an IQL controller the controller must be configured for use with the RD-IQL. The
RD-IQL is only compatible with IQL11+, IQL13+, and IQL15+ controllers. When using an RD-IQL certain features
of the controller are unavailable, depending on the type of RD-IQL being used. These are described below:
RD-IQL
Unavailable Features
Type
Precludes use of window contact on IQL11+, and PIR/pushbutton inputs on IQL11+, 131+, 151+. Fan
RD-IQL/K
speed control is inoperative on IQL13+, 15+.

Browse the System
RD-IQL
Unavailable Features
Type
RD- Precludes use of window contact on IQL11+, and PIR input on IQL11+, 131+, 151+. Fan speed control
IQL/KOS is inoperative on IQL13+, 15+.
RD-
Precludes use of PIR input.
IQL/KOSF
The controller must have a standard strategy or standard item allocations as described below.
Controller Standard Allocations
IQL11+ S1, S2, S3, S9, S10, and I9
IQL13+ S1, S2, S3, S7, S9, S10, S11 and I9
IQL15+ S1, S2, S3, S7, S9, S10, S11 and I9
To configure an IQL controller for use with an RD-IQL:
1. Connect to the LonWorks network segment containing the IQL controllers that are to be configured for use
with an RD-IQL.
2. Right-click the required controller and click Configure for RD a dialogue box is displayed.
3. Select the Uses RD check box. The dialogue box changes to allow the required options to be set up.
4. If available in the Local Temp Source area, select either the From RD or From Sensor check box depending
on where the RD-IQL is to get its local temperature.
5. If available in the fan speed select area select either the From RD or From Switch check box depending on
where the RD-IQL is to take its switch input.
6. Click Update.
7. Click .
The tool will send text comms messages to the selected controllers to configure them for use with an RD-IQL. Once
the changes are complete they will be written to flash memory, and the controller(s) restarted.
Note: It is also possible to perform this action from IQSET’s System View by connecting to the LonWorks network
segment as described above, navigating to the required controller, right clicking the controller, and clicking
Configure for RD-IQL.

Browse the System
17.3 Configure vCNCs

IQSET enables vCNCs in an IQ4 v3.60 or greater to be configured without the need to download an updated strategy.
To edit a controller's vCNCs:
1. View the site in the System View containing the controller for which the vCNCs are to be edited and navigate
to the Virtual CNCs folder.
2. Right-click the Virtual CNCs folder and select Configure vCNCs. The Configure vCNCs dialogue box is
displayed which allows the device's vCNC to be configured.
3. Specify whether the vCNC port numbers are to be manually specified or to use the default value (10000 +
Address) by selecting/clearing the Use Default Port box.
4. Enable/disable the required vCNCs by clearing/selecting the Disable check box, (selected = disabled).
5. Specify the label for the vCNC in the Label box.
6. Specify the network address of the vCNC in the Address box (range 1, 4 to 119 excluding 10). It must be
unique on the Local LAN.
7. If the default port is NOT being used specify the port for the vCNC in the Port box.
8. Specify the security mode in the Security Mode box.
9. If the vCNC is to send device dead alarms select Device Dead Alarm.
10. If any of the vCNCs are operating in 'Secure' mode and you have not already added a CNC User module you
MUST add one.
11. Enter the CNC User module's name in the Name box.
12. Enter the CNC User module's password in the Password box.
13. Retype the password in the Retype Password box.
14. If the controller has security enabled enter the PIN required to authorise the change in the PIN box.
15. Click OK.

Browse the System
17.4 Display a List of Objects

17.4.1 Display a List of Device Contents
If required a list of the contents of the device currently selected in the System View can be displayed.
To display a list of device contents:
1. Display the device whose content you want to display as a list.
2. Right-click on the device and click List device contents. The List View Window is displayed.
17.4.2 Display a List of Devices on a LAN

If required a list of devices on LAN currently selected in the System View can be displayed.
To display a list of devices on the LAN:
1. Display the LAN whose content you want to display as a list.
2. Right-click on the LAN and click List devices on lan. The List View Window is displayed.

Browse the System
17.4.3 Display a List of Internetwork Devices
If required a list of internetwork devices for the internetwork currently selected in the System View can be displayed.
To display a list of internetwork:
1. Display the internetwork you want to display as a list.
2. Right-click on the internetwork and click List Iwrk devices. The List View Window is displayed.
17.4.4 Display a List of Module Parameters

If required a list of the parameters for the module currently selected in the System View can be displayed.
To display a list of module parameters:
1. Display the module whose parameters you want to display as a list.
2. Right-click on the module and click List modules parameters. The List View Window is displayed.

Browse the System
17.4.5 Display a List of Modules
If required a list of the modules of the type currently selected in the System View can be displayed.
To display a list of modules:
1. Display the type of module in the required controller you want to display as a list.
2. Right-click on the module type and click List modules. The List View Window is displayed.
17.4.6 Display a List of the Site Content

If required a list of the content of the site currently selected in the System View can be displayed.
To display a list of the site content:
1. Display the site whose content you want to display as a list.
2. Right-click on the site and click List the site content. The List View Window is displayed.

Browse the System
17.5 Display Graphs

17.5.1 Display a Chart
It is possible to chart a value in an IQ controller.
Note: Not all parameters can be charted.
To chart values:
1. Display the parameter that you want to chart in the System View.
2. Right-click the parameter and choose Chart from the menu that is displayed. The Chart Interval dialogue
box is displayed.
3. In the box enter the interval, in seconds, between chart values.

4. Click OK. The selected value(s) will now be charted.
Clicking will close the graph. The refresh rate of the chart can be changed. To view the time and the value
for a point on the graph press CTRL and then move the mouse to that point, the time and value will be
displayed. You can zoom in and out of the graph. If required other traces can be added to, or removed from
the graph. The scaling of the Y-axis can be fixed. A graph can be printed, or copied to the clipboard.
17.5.2 Display a Compact Graph
It is possible for compact logs of a sensor in an IQ controller to be displayed as a graph. Each graph can show up to
1000 values.
To display a compact graph:
1. Display the sensor or plot module you want to display as a graph in the System View in the System View,
or in Live Edit/Live values.
2. Right-click the sensor that is to be graphed and click Graph. The Choose Log Interval dialogue box is
displayed.
If a graph is already displayed, you will be prompted whether the graph is to be in a new window or be added
to the existing graph. Click Yes to add the graph to the existing window, or No to display it in a new window.
3. In the Interval box click the interval at which the sensor is being logged.
4. Click Compact comms (FAST).
5. Click OK. The graph is displayed.

Browse the System
17.5.3 Display a Precision Graph
It is possible for precision logs of a sensor in an IQ controller to be displayed as a graph. Each graph can show up to
1000 values.
To display a precision graph:
1. Display the sensor or plot module you want to display as a graph in the System View in the System View,
or in Live Edit/Live values.
2. Right-click the sensor that is to be graphed and click Graph. The Choose Log Interval dialogue box is
displayed.
If a graph is already displayed, you will be prompted whether the graph is to be in a new window or be added
to the existing graph. Click Yes to add the graph to the existing window, or No to display it in a new window.
3. In the Interval box click the interval at which the sensor is being logged.
4. Click Longhand comms (ACCURATE).
5. Click OK. The graph is displayed.
17.6 Display Properties
17.6.1 Display Device Properties
Information about a selected device on the Trend System can be displayed in the Device Properties dialogue box.
To display device information:
1. Display the device for which information is required.
2. Right-click the device, and click Properties. The Device Properties dialogue box is displayed. The
information can be updated by clicking Read.

Browse the System
17.6.2 Display a Trend Modules Properties
Parameter values from a selected module on the Trend System can be displayed in the Module Properties dialogue
box.
Note: This feature is not available for IQ1 and IQ2 series controller Time Schedule modules.
To display module information:
1. Display the module for which information is required, right-click the module, and click Module Properties.
The Module Properties dialogue box is displayed.
Once the parameters are displayed in the grid the values of parameters in the controller can be:
 Refreshed manually
 Refreshed automatically
 Edited.
The columns can be fitted to the content
17.6.3 Display a BACnet Module Properties
Information about a selected BACnet module can be displayed in the Module Properties dialogue box.
To display module information:
1. Display the module for which information is required.

Browse the System
2. Right-click the module, and click Properties. The Module Properties dialogue box is displayed.
The information can be updated by clicking Read. The module’s parameters can be displayed by clicking
the Parameters tab. This also enables the parameters to be changed.
17.6.4 Display Parameter Properties
Information about a selected module parameter on the Trend System can be displayed in the Parameter Properties
dialogue box.
To display parameter information:
1. Display the list containing the parameter for which information is required.
2. Right-click the parameter, and click Properties. The Parameter Properties dialogue box is displayed.
The colour of the box around the parameter indicates its status. Clicking Key displays a dialogue box that
explains the meaning of each of the colours. The information can be updated. This also enables the value of
the parameter can be changed.

Browse the System
17.6.5 Display Site Properties
Information about a selected site on the Trend System can be displayed in the Site Properties dialogue box.
To display site information:
1. Display the site for which information is required.
2. Right-click the site, and click Properties. The Site Properties dialogue box is displayed.
If required a PIN can be specified for all the controllers on the site.
17.7 Enter Configuration Mode on Pre IQ3 Controllers
IQSET provides access to the configuration mode of pre IQ3 controllers on the network. Once the configuration mode
for a device has been entered, configuration commands can be entered and sent to the controller.
To enter configuration mode:
1. Display the strategy page for the controller that is to be accessed in configuration mode.
2. Click or on the Comms menu click Config. The Connection Details dialogue box is displayed. IQSET

Browse the System
is to be used in the Standard Comms Connection box click the required connection.
If suitable connection is not available an existing connection can be used as basis for new one that will be
associated with the site, by selecting the required connection from the Standard Comms Connection box,
and then clicking Edit Connection Details. This will display the TUA dialogue box that enables a connection
to be specified.
Note: The connection specified here will not be added to the list of comms connections.
7. Click OK. IQSET will check to see that the identifier and controller address specified match the one to which
IQSET is connecting. If they don’t match a dialogue box asking if you want to continue is displayed.
8. Click OK to continue, or Cancel to cancel. If OK was selected the Config session window is displayed.
9. Type the required configuration command into the box at the bottom of the Config Session Window and
press ENTER or click Go to send the command to the device.
The system prompts the available functions; the uppercase character in each prompt is the key to be used to
select the function. Most functions also require an additional numeric value. To exit from any page of data
and save any changes, made, press X+ENTER. To exit from any page of data and not save any changes made,
press Q+ENTER. The commands are as explained in the IQ Configuration Reference Manual (90-1533) for
IQ controllers. If required keywords can be embedded in the commands to provide quicker access too
commonly used commands
It is also possible to send a previously used command or a favourite command to the controller, by selecting
the required command from the appropriate list, and pressing ENTER or clicking Go.
If a module is selected, the next and previous module of the same type can be viewed by clicking < or >. To
send a Q, or X to the controller click Q or X.
10. To close the session, click X at the top-level configuration prompts to exit configuration mode.
Note: If no commands are sent to the device for a period it will automatically exit configuration mode and
the Config Session Window will close.
For more details of using the Config Session Window see the Config/Text Comms/Mapping Applet Manual
(TE200536).

Browse the System
17.8 Manage the System View

The way in which the System View appears is dependent on the current user role; however, it can be set up to display
only the devices and objects that are required by removing objects. User nodes can be added to enable fast access to
the required points on the system. Sites that use different connections can also be added to enable access to devices
on different parts of the system. This set up can be saved as site file for use later by other applications. Objects that
are not in System View will not be accessible.
To set up the System View:
2. Add the required sites.
3. Navigate down the structure of each site to identify the objects on the site. Objects with a + next to them can
be expanded by clicking the + to reveal what is below them in the structure.
4. Delete any unwanted objects (parameters, modules, or sites etc.) from the System View.
5. Add any user nodes that are required.
17.8.1 Delete a Site
If there are sites in the list that are not required, they can be deleted.
To delete a site:
3. In the System View right click the site that is to be deleted and click Delete.
Or
3. On the Project menu click Sites. The Site Connections dialogue box is displayed.
4. In the Site List box click the site that is to be deleted.

5. Click Delete. The selected connection will be deleted.
6. Click OK.
17.8.2 Edit a Site
If there is a site in the list that needs to be changed, it can be edited as required by changing the name, or changing the
connection used to communicate with it.
To edit a site:

Browse the System
3. On the Project menu click Sites. The Site Connections dialogue box is displayed.
4. In the Site List box click the site that is to be edited.

5. Edit the site as required, by changing the site's name, or changing the site's connection using a standard
comms connection, changing the site's connection using the TUA Editor, or the changing the site's
connection using the Connection Wizard, and for BACnet sites changing the site's connection using the
BUA Editor.
To change the site's name:
 Click Edit.
 Enter the new name in the Site Name box of the displayed dialogue box.
 Click OK.
To change a Trend system site's connection using a standard comms connection:
 Select the required standard comms connection in the Standard Comms Connection box.
comms connections.
 Click Edit Connection details. The Connection Wizard dialogue box is displayed.
To change a BACnet site's connection:
 Click Edit Connection details. The BACnet Universal Address Editor dialogue box is displayed.
6. Click OK.
Or
3. In the System View right click the site that is to be edited and click Edit. If a Trend site was selected the
Edit Site Connection Details dialogue box is displayed. If a BACnet site was selected the BACnet
Universal Address Editor dialogue box is displayed.

Browse the System
4. Edit the site as required, by changing the site's name, changing the site's connection using a standard comms
connection, changing the site's connection using the TUA Editor, or changing the site's connection using the
Connection Wizard, and for BACnet sites changing the site's connection using the BUA Editor.
To change the site's name:
 Enter the new name in the Site Name box.
To change a Trend system site's connection using a standard comms connection:
 Select the required standard comms connection in the Related Connection box.
 Click Edit site details. The Connection Wizard dialogue box is displayed.
comms connections.
 Click Edit site details. The Connection Wizard dialogue box is displayed.
To change a BACnet site's connection:
5. Click OK.
17.8.3 Delete an Object from the System View
If required, any object can be removed from the System View, preventing access to it by users with lower levels of
access. Once an object has been removed from the System View, the System View must be refreshed to add it back
in again.
Note: Deleting an object in the System View will mean that if cannot be accessed from a user node.
To delete an object from the System View:
4. Right-click the object that is to be removed, and click Delete.
17.8.4 Add a User Node
User nodes allow a user-defined structure to be created to allow faster access to regularly used parts of the system.
There is no limit to the number of user nodes that can be added. Each user node can contain other user nodes, or user
parameters. Access to user nodes (and some user parameters) can be restricted to specific user roles to prevent
unauthorised accessed and reduce confusion to lower-level users.
To add a user node:
3. Right-click User nodes, and click New user node. If the user node is to be inside another user node, right-
click the user node and click New user node. The Add or Edit User node dialogue box is displayed.
4. In the Name box enter the name for the user node.
5. In the Refresh interval(s) box enter the rate in seconds at which any values contained in a user node are
refreshed.

Browse the System
6. If the user node is to refresh the values, select the Refresh is active check box.
Note: If there is allot of user nodes in the tree view all refreshing their values, a large amount of unnecessary
network traffic may be created. Therefore, it is recommended that the refresh of user nodes is not active
unless they are being accessed.
7. In the User Role box click the lowest level user role that will have access to the user node.
8. Once the settings are correct click OK.
9. Add the required user parameters.
17.8.4.1 Add User Parameters to a User Node
User parameters are either modules or parameters that are to be collected under a user node for common refreshing.
To add user parameters to a user node:
3. Navigate down the user node structure to display the user node to which user parameters are to be added.
User nodes with a + next to them can be expanded by clicking the + to reveal what is below them in the
structure.
4. Navigate down the structure of the site to display the user parameter that is to be added to the user node.
Objects with a + next to them can be expanded by clicking the + to reveal what is below them in the structure.
5. Click the module/parameter that is to be added to the user node in either the System View, or the Tracker
Window, hold down the left mouse button and drag it on to the required user node. If multiple selections are
required, the selection must be made from the Tracker Window. Hold down the CTRL key, and then click
the required user parameters. To select a range, click the first one in the range, hold down the SHIFT key,
and click the last one in the range.
6. Release the mouse button. The selected parameters will be added to the user node, and no further action is
required. If a user parameter is a module or module parameter, a dialogue box will be displayed.
7. In the Name box enter the name for the user parameter.
8. In the Significant change box enter the amount by which the user parameter must change before it is updated
in the user node.
Note: If the refresh for the user node containing the user parameter is not active it will not be updated, even
if the value changes by more than the significant change value.
9. In the User Role box click the lowest level user role that will have access to the user parameter from the list.
10. Once the settings are correct, click OK. If more than one parameter is selected, you can click OK All to
accept the changes to all parameters.
17.8.4.2 Delete a User Node
To delete a user node:
3. Right-click the user node that is to be deleted, and click Remove.
17.8.4.3 Delete User Parameters from a User Node
To delete user parameters from a user node:
3. Navigate down the user node structure to display the user parameter that is be deleted. User nodes with a +
next to them can be expanded by clicking the + to reveal what is below them in the structure.
4. Right-click the user parameter that is to be deleted, and click Delete.

Browse the System
More than one user parameter can be deleted at a time by selecting them in the Tracker Window, right-clicking the
selection, and clicking Remove. To select more than one user parameter, hold down the CTRL key, and then click the
required user parameters. To select a range, click the first one in the range, hold down the SHIFT key, and click the
last one in the range.
17.8.4.4 Edit a User Node
To edit a user node:
3. Right-click the user node that is to be edited, and click Edit. The Add or Edit User node dialogue box is
displayed.
4. Edit the user node as required.

5. Once the settings are correct click OK.
17.9 Map the System
17.9.1 Display a Logical Map
Logical maps display the site logically clearly indicating the individual LANs and internetworks.
Note: The applet only displays devices that appear in the System View. To ensure the map is current refresh the
System View before mapping the network.
To display a logical map:
1. Run the Site Topology Applet.
2. Click Logical View. The logical map of the system is displayed.
To display a map of an individual LAN double click the LAN or right click and from the displayed menu
click Maximise Lan. To return to the view of the entire site double click inside the LAN, or right click and
from the displayed menu click Minimise Lan. The map can be refreshed by right clicking the map and on
the displayed menu clicking Refresh Lan or Refresh Internetwork.

Browse the System
To zoom in/out of the map move the slider below the Overview Area. The map can be arranged to make it
more readable, the tool tips can be turned ON/OFF, labels can be turned ON/OFF, the key can be displayed,
and applets can be run.
17.9.2 Display a Physical Map
Physical maps display the site clearly indicating the individual different media (Trend system current loop, Ethernet,
LonWorks etc.) being used.
Note: The applet only displays devices that appear in the System View. To ensure the map is current refresh the
System View before mapping the network.
To display a physical map:
1. Run the Site Topology Applet.
2. Click Physical View. The physical map of the system is displayed.
To display a map of an individual LAN double click the LAN or right click and from the displayed menu
click Maximise Lan. To return to the view of the entire site double click inside the LAN, or right click and
from the displayed menu click Minimise Lan. The map can be refreshed by right clicking the map and on
the displayed menu clicking Refresh Lan or Refresh Internetwork.
Individual parts of the system (LANs or a media segment) can be hidden by clicking the appropriate on
the map. Clicking the appropriate will display the part of the system that has been hidden. To zoom in/out
of the map move the slider below the Overview Area. The map can be arranged to make it more readable,
the tool tips can be turned ON/OFF, labels can be turned ON/OFF, the key can be displayed, and applets can
be run.

Browse the System
17.9.3 Display a System Map
The site can be displayed as a map. Once the site has been mapped, tasks such as entering configuration mode can be
performed from the map as required.
To map the site:
1. Browse the system to display the part that is to be mapped.
2. Right-click part of the system that is to be mapped and click Map LAN, or Map Internetwork. The Network
Device Map Window is displayed.
3. It is possible to view maps of the internetwork by double clicking Iwrk, or other LANs by mapping the
internetwork, and then double clicking the required LAN.
The information on the screen is automatically refreshed; this refresh can be stopped by clicking Stop, and
started by clicking Start. To force a refresh for a device, right-click it and click Refresh. Tasks can be
performed by right-clicking the object in the map (e.g. LAN) and clicking the required one.
Note: It may be necessary to identify the device first so that the tasks that apply to the device can be worked
out.
4. To close the map, click at the top of the window.

Browse the System
17.9.4 Display an Electrical Map
Electrical maps enable the display of devices on a LAN in their electrical order.
Only devices that support attribute addressing, or INC2s can be mapped electrically. It is only possible to electrically
map LANs using the Trend system current loop, not internetworks. Devices on Trend system current loop LANs that
do not electrically map are placed at the end of the electrical map, EINCs and 3xtend/EINC Ls will report their
upstream device in the summary view.
To display an electrical map:
1. Run the Site Topology Applet and display the LAN that is to be electrically mapped.
2. Right-click the LAN that is to be electrically mapped and on the displayed menu click Build electrical map.
3. If there are IQ3 controllers on the LAN a dialogue box is displayed asking if you want to check that there is
a sensor 1 in the IQ3s, this is because sensor 1 is required for the electrical mapping process. Click Yes to
perform the check and goto (4) or click No not to perform the check and goto (5).
Note: If the electrical mapping of the LAN has previously been aborted leaving the K attributes incorrectly
set a dialogue box is displayed asking if you want to restore them click Yes and follow the instruction on the
screen.
4. Once the check for sensor 1 is complete a dialogue box listing which controllers don’t have a sensor 1 and
asking if you want to continue with the electrical mapping is displayed. Click Yes to continue. Clicking No
will stop the process.
Note: IQ3/IQ4 controllers without sensor 1 will not electrically map and will be placed at the end of the map.
5. The Electrical Map Options dialogue box is displayed.
6. In the Universal Pin box enter the PIN that is to be used to provide the tool with the necessary access to
create the electrical map. If the PIN for each device is to be entered individually select the Prompt pin input?
check box. This will cause the applet to prompt for a PIN for individual controllers if the PIN required for
each controller is different.
7. In the Timeout (second) box enter the time allowed to build the electrical map. Sometimes on large LANs
it will be necessary to increase the amount of time allowed.
8. If the K attributes are to be logged to an XML file, select the Log the K attributes to xml file check box.
Caution: Turning this feature off will mean that if the process fails the applet will be unable to return the K
attributes back to their original state.
9. If the K attributes are to be restored to their original state if a failure occurs, select the On failure k value
auto restore check box.
10. If the LAN has a mixture of IQ3, IQ4 and pre IQ3 controllers and there are pre IQ3 controllers that have
previously failed to map electrically clear the Include IQ3s check box.
11. Click OK. The electrical mapping process is carried out. When complete the electrical map is displayed
along with a summary of the LAN. To abort the process right click and in the displayed menu click Abort
current sorting.
To zoom in/out of the map move the slider below the Overview Area. The map can be arranged to make it
more readable, the tool tips can be turned ON/OFF, labels can be turned ON/OFF, the key can be displayed,
and applets can be run.
Note: If the process fails, or is aborted the K attributes may be left as ‘RaTzZz’ or 'Not CATZZZ' in some
devices. In this case, it is necessary to manually set the attribute back to the original value.

Browse the System
17.10 Send a Text Comms Message

If required text comms requests or writes to be sent to the target controller, LAN, or internetwork. The target defines
the type of text comms message.
Destination Text Comms Description
Type
Device Directed Message is only sent to the specified device.
LAN Global Message is sent at the same time to all matching devices on the LAN.
Visitor Message is sent in turn to matching devices on the LAN.
Internetwork Global Global Message is sent at the same time to all matching devices on all LANs on the
internetwork.
To send a text comms message:
1. Display the part of the system for which a text comms session is required.
2. Right-click the device part of the system and click Text comms. The Text Comms Session Window is
displayed.
To send a directed text comms message, select the device. To send a global text comms message, select the
LAN. To send a global global text comms message select the internetwork. To send the text comms message
as a visitor message select the LAN, and specify the text comms session options to use visitor comms.
3. In the box at the bottom of the Text Comms Session Window enter the required text communications
message and press ENTER to send the command to the message.
The message will be sent as either a read, write with acknowledge, or write without acknowledge depending
on what has been set in the text comms session options. The default is Auto (REQ – OWH) which means if
the message contains an = it is sent as a write with acknowledge, otherwise it is sent as a read. If required
you can force the message to be sent as a read, or a write by clicking Read or Write.
It is also possible to send a previously used message, or a favourite message, by clicking the required message
from the appropriate list, and pressing ENTER. The last message sent can be repeated indefinitely by clicking
Repeat. Click Stop to stop the message repeating.
4. To close the session, click at the top right of the window.

Browse the System
17.11 Turn a User Node's Refresh ON/OFF

If there is allot of user nodes in the System View all refreshing their values, a large amount of unnecessary network
traffic may be created. Therefore, it is recommended that the refresh of user nodes is not active unless they are being
accessed.
To add turn a user node’s refresh rate ON/OFF:
3. Right-click the user node and click Edit. The Add or Edit User node dialogue box is displayed.
4. Select/clear Refresh is active check box. Selected indicates the refresh is on.
5. Once the settings are correct, click OK.
17.12 Upload/Download Strategy
17.12.1 Download a Single Strategy to Multiple Controllers
It is possible to download a single strategy to more than one controller over the network.
To download a single strategy to multiple controllers:
1. Create the file that is to be downloaded. Not required if a solution is to be used.
2. View the site in the System View containing the controllers to which the strategy is to be downloaded.
3. Right-click the site, LAN or device and click Add to Transfer List. The IQTool File Transfer Window is
displayed.
Note that the appearance of this window is different for different type of controller.
4. Select the Download option.

Browse the System
5. Specify the directory containing the file that is to be downloaded. Not required if a solution is to be used.
To specify the transfer directory:
 Click next to the Transfer Directory box. The Browse For Folder dialogue box is displayed.

 Click OK.
6. Specify the file that is to be downloaded.
To specify a strategy file:
 In the Select Download File area select the type of file that is to be downloaded from the drop-down
list.
 In the list of files click the file that is to be downloaded.
To use a solution:
 Click Select Solution. The Solution Selector dialogue box is displayed.
 Select the required solution from the list. Details about the controller type, hardware variant, and options
of the controller for which the solution was designed are displayed along with a description of the
solution's functionality.

Browse the System
The list can be filtered to display only strategies designed for use in fixed strategy controllers by selecting
the required library from the Licenced Library box. Solutions for older firmware versions can be
hidden/displayed using the Hide Older Versions check box.
Note: A fixed strategy controller will only be able to run a strategy from the library it is licensed to use but
IQSET will not warn you that the solution is not compatible with the actual controller. Programmable
controllers (no license restrictions) will be able to run any solution designed for their controller type.
 Click OK.
7. Add/Remove devices from the grid until it contains all the devices to which strategy is to be downloaded.
To add a single controller:
 Navigate the site to locate the controller.
 Right-click the controller, and click Add to Transfer List, or drag the controller from the System View
on to the File Transfer Window. The controller will be added to the grid.
Note: If the IQTool File Transfer window is not already displayed, this action will cause it to be displayed.
To add all the controllers on a LAN or site:
 Navigate to the site or LAN.
 Right-click the LAN or site, and click Add to Transfer List. All the controllers on the LAN/site will be
added to the grid.
It is possible to load a list of devices from a file saving the time required to create a list each time, and
ensuring that the same controllers are used for a site or group of controllers that use the same strategy.
To remove controllers:
 Delete the row(s) from the grid for the required controller(s). All device can be removed by clearing the
grid.
Once the grid has been set up it can be saved for use later, saving time creating a list each time, and ensuring
that the same devices are used.
8. Filter and sort the grid to make selection of the required devices easier. If a selected device is excluded by a
filter it will be automatically deselected.
9. In the Selection column check the check box next to the controllers to which the file is to be downloaded.
Icon Description
or press CTRL+A Selects all the devices in the grid. Devices excluded by a filter are NOT selected.
or press CTRL+U Unselects all controllers in the grid including any excluded by a filter.
10. If any of the controllers have security enabled specify the password that will authorise the download.
 For IQ4 or IQ3 v1.3 or greater controllers in the Pin box enter the PIN.
Pre IQ3 and IQeco controllers:
If an IQ controller has PIN protection enabled, it will request a PIN before a download is allowed. The PIN
that is sent must match with one in the controller that has a PIN Level of 99 or greater.
Note: Only one password or PIN is sent therefore if the controllers have different passwords, or PINs the
download will fail. It is therefore recommended that all the controllers on a system have the same username
and password, or PIN.
11. If downloading to IQ1 and IQ2 version <= 2.0 controllers the Send IQF and Send LDF options are displayed
12. To force the use of IQF protocol click and select Use IQ Lan.

Browse the System
13. If downloading to IQECO v2.0 or greater, IQ3 or IQ4 controllers specify whether the strategy file is to be
downloaded by selecting the Strategy File check box. If the Not Sent check box was selected in the
appropriate IQSET dialogue box when the strategy file was created that information will not be downloaded.
14. If downloading to IQ4NC controllers specify whether the network configuration (Trend Mode and Lan label
parameters) are to be downloaded by selecting the Node Controller check box. The network configuration
determines the way the controller routes messages between different network media e.g. between Ethernet
and MS/TP.
Module Module Parameter
Trend Mode (J)
Ethernet IP Module
LAN Label (K)
Trend Mode (J)
Trend LAN Network Module
LAN Label (K)
Trend Mode (J)
BACnet MSTP Network Module
LAN Label (K)
15. If downloading to IQ3 or IQ4 controllers specify whether the backdrop files required for the controller's
Graphical Display Pages are downloaded by selecting the Backdrops check box.
Option Description
Merges the User modules being downloaded by IQSET with those already present in the
Merge and
IQ4, leaving the User modules in the IQ4 unchanged if there are any duplicates (same user
Maintain
name and type).
Deletes all User modules in the IQ4 and replaces them with the User modules downloaded
Replace All
by IQSET.
Merges all User modules downloaded by IQSET with those in the IQ4, overwriting duplicate
Merge and
modules (same user name and type) in the IQ and leaving other User modules in the IQ4
Overwrite
unchanged.
Ignore Ignores any User modules defined in IQSET leaving those in the IQ4 unchanged.
17. If downloading to IQ3 controllers with version 1.1 firmware or greater specify whether the language files
used for the display of web pages and alarms are downloaded by selecting the Language Files check box.
Note: It is not necessary to download language files to IQ4 controllers as the necessary files are already in
the controller.
18. If downloading to IQ3 controllers with version 1.3 firmware or greater that have XNC functionality enabled
specify whether the TCL program (.XNC file) is to be downloaded by selecting the XNC File check box.
19. Click . IQSET will attempt to communicate with the controllers. If connecting to a vCNC operating in
 Clicking will stop the download for all devices. After the download process has started if there
are devices in the list for download that are no longer required they can be deselected by right clicking
on the device's row and selecting Abort Device(s) providing the download to the device has not started.
If a device has not been selected it can be selected after the download has started by right clicking on the
device's row and selecting Add Device(s) to Transfer.
Note: Once the process has started additional devices cannot be added to the grid.

Browse the System
If the process competes successfully all controllers will be disabled causing most of the interface to be
disabled.
17.12.2 Download Different Strategies to Multiple Controllers
It is possible to download strategy to more than one IQ controller over the network. A different strategy can be
downloaded to each controller. The format of the name of the strategy file is used to determine which device the file
is downloaded to; therefore, it is important that the strategy files are named appropriately.
To download different strategies to multiple controllers:
1. Create the filed that are to be downloaded. Not required if a solution is to be used.
2. View the site in the System View containing the controllers to which the strategy is to be downloaded.
3. Right-click the site, LAN or device and click Add to Transfer List. The IQTool File Transfer Window is
displayed.
4. Select the Download option.
5. Specify the directory containing the file that is to be downloaded. Not required if a solution is to be used.
To specify the transfer directory:
 Click next to the Transfer Directory box. The Browse For Folder dialogue box is displayed.

 Click OK.

Browse the System
6. Check that the strategy files that are to be downloaded are available.
Check the download files are in the download directory:
 In the Select Download File area select *.* from the drop-down list box.
 Check the files that are to be downloaded are in the directory, and in the format below.
L<xxx>n<yyy>.<zzz>
Where <xxx> specifies the LAN number of the controller. <yyy> specifies the network address of the
controller. <zzz> indicates the file format (IQ4, IQ3, IQe, IQF, or SCN), e.g. L099n020.IQ3 would be the
filename given to the file uploaded from controller 20 on LAN 99.
6. Add/Remove devices from the grid until it contains all the devices to which strategy is to be downloaded.
added to the grid.
grid.
8. In the Selection column check the check box next to the controllers to which the file is to be downloaded.
Icon Description
9. Ensure that a file is NOT selected in Select Download File area.
Note: Only one password or PIN is sent therefore if the controllers have different passwords, or PINs the
download will fail. It is therefore recommended that all the controllers on a system have the same username
and password, or PIN.

Browse the System
appropriate dialogue box when the strategy file was created that information will not be downloaded.
and MS/TP.
Trend Mode (J)
Ethernet IP Module
LAN Label (K)
Trend Mode (J)
LAN Label (K)
Trend Mode (J)
LAN Label (K)
Option Description
Merge and
Maintain
name and type).
Replace All
by IQSET.
Merge and
Overwrite
unchanged.
the controller.
19. If downloading to IQ3 controllers with version 1.3 firmware or greater that have XNC functionality enabled
specify whether the TCL program (.XNC file) is to be downloaded by selecting the XNC File check box.
 Clicking will stop the download for all devices. After the download process has started if there
are devices in the list for download that are no longer required they can be deselected by right clicking
on the device's row and selecting Abort Device(s) providing the download to the device has not started.
If a device has not been selected it can be selected after the download has started by right clicking on the

Browse the System
If the process competes successfully all controllers will be disabled causing most of the interface to be
disabled.
17.12.3 Download to a Single Controller
It is possible to download the strategy to a IQ controller.
To download to a single controller:
1. Create the file that is to be downloaded. Not required if a solution is to be used.
2. View the site in the System View containing the controller to which the strategy is to be downloaded.
3. Right-click the controller and click Send File to Device. The File Download dialogue box is displayed.
Note: The appearance of this dialogue box is different for different type of controller.
4. The download file is automatically determined by the address of the controller but can be changed if required.
 Click Open.
If is displayed the download file cannot be located check the file exists, and is specified correctly.
5. If the controller has security enabled specify the security details that will authorise the download.

Browse the System
select the format of the strategy file that is to be downloaded
appropriate IQSET dialogue box when the strategy file was created that information will not be downloaded.
and MS/TP.

Trend Mode (J)
Ethernet IP Module
LAN Label (K)
Trend Mode (J)
LAN Label (K)
Trend Mode (J)
LAN Label (K)
Option Description
Merge and
Maintain
name and type).
Replace All
by IQSET.
Merge and
Overwrite
unchanged.
the controller.

Browse the System
13. If downloading to IQ3 controllers with version 1.3 firmware or greater with XNC functionality enabled
specify whether the TCL program (.XNC file) is to be downloaded by selecting the XNC File(s) check box.
14. Specify whether the window is to be closed when the download is complete by selecting the Close this
dialogue box when download completes check box.
15. Click . IQSET will attempt to communicate with the controller. If connecting to a vCNC operating in
 The progress is indicated at the bottom to the dialogue box. Clicking will stop the download.
Once the download is complete the text 'Download Complete' is displayed at the bottom of the dialogue
box.
If is not available the specified file does not exit, and a different file must be specified before the
download can take place.

Browse the System
17.12.4 Upload from a Single Controller
It is possible to upload the strategy data file from an IQ controller in IQ4, IQ3, IQe, IQF, or SCN format. The file is
named in the following format:
L<xxx>n<yyy>.zzz>
Note: If uploading from IQ3 or IQ4 controllers the uploaded file will contain the IP address and LAN and outstation
numbers.
To upload from a single controller:
1. View the site in the System View containing the controller from which the strategy is to be uploaded.
2. Right-click the device in the System View and click Get File from Device. The File Upload dialogue box
is displayed.
Note: The appearance of this dialogue box is different for different type of controller.
3. Specify the directory in which the uploaded file is to be stored. It defaults to the Upload directory for the
current project.
To specify the upload directory:
 Click .The Browse For Folder dialogue box is displayed.
 Navigate to the required directory. A new directory can be created by clicking Make New Folder.
 Click OK.

Browse the System
5. To force the use of IQF protocol click and select Use IQ Lan .
6. If uploading from IQECO v2.0 or greater, IQ3 or IQ4 controllers specify whether the strategy file is to be
uploaded by selecting the Strategy File check box.
7. To upload IQF files from IQ2 controllers earlier than v2 instead of SCN files, select the Get IQF. By default,
IQSET uses IQF files for IQ2 controllers earlier than v2.
8. If uploading from IQ3 or IQ4 controllers specify whether the backdrop files required for the controller's
graphical display pages are uploaded by selecting the Backdrops check box.
9. If uploading from IQ4 or IQ3 controllers with version 1.1 firmware or greater specify whether the language
files used for the display of web pages and alarms are uploaded by selecting the Language Files check box.
10. If uploading from IQ3 controllers with version 1.3 firmware or greater that have XNC functionality enabled
specify whether the TCL program (.XNC file) is to be uploaded by selecting the XNC File(s) check box.
11. Specify whether the window is to be closed when the upload is complete by selecting the Close this dialogue
box when upload completes check box.
12. Click . IQSET will attempt to communicate with the controller. If connecting to a vCNC operating in
 The progress is indicated at the bottom to the dialogue box. Clicking will stop the upload. Once
the upload is complete the text 'Upload Complete is displayed at the bottom of the dialogue box.
17.12.5 Upload from Multiple Controllers
It is possible to upload strategy from more than one IQ controller over the network.
The upload will generate a single strategy file for each controller from which strategy is uploaded. These files are
stored in the upload directory, and named in the following format.
L<xxx>n<yyy>.zzz>
Note: If uploading from IQ3 or IQ4 controllers the uploaded file will contain the IP address and LAN number and
device address.
To upload strategy from multiple controllers:
1. View the site in the System View containing the controllers to which the strategy is to be uploaded.

Browse the System
2. Right-click the site and click Add to Transfer List. The IQTool File Transfer Window is displayed.
3 Specify the directory in which the uploaded files are to be stored. It defaults to the Upload directory for the
current project. The contents of the upload directory can be viewed by selecting Display Upload Dir.
To specify the upload directory:
 Click .The Browse For Folder dialogue box is displayed.
 Navigate to the required directory. A new directory can be created by clicking Make New Folder.
 Click OK.
4. Add/Remove devices from the grid until it contains all the devices from which strategy is to be uploaded.
added to the grid.

Browse the System
grid.
6. In the Selection column check the check box next to the controllers to which the file is to be uploaded.
Icon Description
8. If uploading from IQ1 and IQ2 version <= 2.0 controllers the Get IQF and Get SCN options are displayed
select the required option. By default, IQSET uses IQF files for IQ2 controllers earlier than v2.
10. If uploading from IQECO v2.0 or greater, IQ3 or IQ4 controllers specify whether the strategy file is to be
uploaded by selecting the Strategy File check box.
11. If uploading from IQ3 or IQ4 controllers specify whether the backdrop files required for the controller's
Graphical Display Pages are uploaded by selecting the Backdrops check box.
12. If uploading from IQ4 or IQ3 controllers with version 1.1 firmware or greater specify whether the language
files used for the display of web pages and alarms are uploaded by selecting the Language Files check box.
13. If uploading from IQ3 controllers with version 1.3 firmware or greater that have XNC functionality enabled
specify whether the TCL program (.XNC file) is to be uploaded by selecting the XNC File check box.

Browse the System
 Clicking will stop the upload from all controllers. After the upload process has started if there
are devices in the list for upload that are no longer required they can be deselected by right clicking on
the device's check box and selecting Abort Device(s) providing the upload to the device has not started.
If a device has not been selected it can be selected after the upload has started by right clicking on the
17.13 View Alarms
17.13.1 View Current Alarms
All the current alarms (i.e. alarms that have occurred and are waiting to be cleared) that have occurred on the Trend
network that the Alarm Monitoring Applet is monitoring since the applet was loaded can be viewed as they arrive on
the Current Alarms tab of the Alarm Monitoring Window.
To view current alarms:
1. Ensure the devices on the network are configured to send alarms to the address being used by the applet.
2. Display the site for which alarms are to be monitored in the System View.
3. On the Tools menu click Monitor Incoming Alarms. The Alarm Monitoring Window is displayed.
4. Click the Current Alarms tab.
The tab contains detailed information about each alarm, and is refreshed as new alarms occur. Colours are
used to indicate whether the alarm is a set alarm or a cleared alarm. A red bell indicates a set alarm, and a
green bell indicates a cleared alarm.

Browse the System
17.13.2 View Historic Alarms
All the alarms that have been cleared (i.e. all set alarms for which a clear alarm has also been received) can be viewed
on the Historic Alarms tab of the Alarm Monitoring Window. The alarms are grouped into set and cleared alarms;
i.e. the set alarm and its corresponding cleared alarm appear on the same line.
To view historic alarms:
4. Click the Historic Alarms tab.
The tab contains detailed information about each alarm, and displays the set alarm with its corresponding
cleared alarm on the same line.
17.13.3 View Incoming Alarms
All the alarms that have occurred on the Trend network that the Alarm Monitoring Applet is monitoring since the
applet was loaded can be viewed on the Incoming Alarms tab of the Alarm Monitoring Window.
To view incoming alarms:
4. Click the Incoming Alarms tab.
The tab contains detailed information about each alarm, and displays the set alarm with its corresponding
cleared alarm on the same line. Colours are used to indicate whether the alarm is a set alarm or a cleared
alarm. A red bell indicates a set alarm, and a green bell indicates a cleared alarm.
17.14 View a Controller's Web Pages
For IQ3 and IQ4 controllers it is possible to access the web pages made available to over an Ethernet network. These
pages provide information about the module parameters in the controller, and enable alarms and graphs to be viewed,
adjustments to be made, as well as access to the controllers Graphical Display Pages if they have been setup.
To view a controller's web pages:
1. Browse the system to display the controller whose web pages are to be displayed application.
2. Right click on the device and click Web page. Internet explorer will be loaded and the controller accessed.
Having accessed the controller, you can navigate around the various pages to view the required information and make
adjustments. Clicking on the different parts of the screen will enable you to perform different tasks the display will
make is clear what can be done. When a reference to a module is displayed with an underline clicking on it will display
the module’s detail page.

Appendices
Appendices
IQ4 Modules
IQECO Modules
Command Line Commands
Keyboard Short Cuts
3rd Party Software Licences

Appendices

IQ4 Modules
A1 IQ4 Modules
This section describes in detail all the configuration parameters for each module. For further information, see the IQ4 Configuration Manual (TE200768).
IQ4 Address Modules
IQ4 Alarm Destination Modules
IQ4 Alarm Group Modules
IQ4 Alarm Route Modules
IQ4 Calendar Modules
IQ4 CNC User Modules
IQ4 Directory Modules
IQ4 Display Modules
IQ4 Driver Modules
IQ4 Function Modules
IQ4 IC Comms Modules
IQ4 Input Modules
IQ4 Interface Modules
IQ4 I/O Modules
IQ4 Logic Modules
IQ4 Loop Modules
IQ4 Network Modules
IQ4 NTD Modules
IQ4 OSS Modules
IQ4 Page Modules
IQ4 Plot Modules
IQ4 Schedule Offset Modules
IQ4 Sensor Type Modules
IQ4 States Category Modules
IQ4 Time Modules
IQ4 Time Schedule Modules
IQ4 User Modules
IQ4 Virtual CNC Modules
Throughout this section module parameters will be referenced by their letter the E parameter would be referenced as E. The value of a module's parameter is referenced by the parameter
letter in brackets e.g. (E) refers to the actual Value of the E parameter.
For each module, the module identifier is listed which should be used when accessing the module with text comms, along with its default overview parameter, and size in brIQs. There
is also a description of how the module works and a table listing all the parameters associated with it, and a description of each parameter.

IQ4 Modules
The Type column of the tables in this section indicates the parameter type.
Parameter
Text Description
Type
Input parameters provide an input to the module. They can be linked to another module's output, or set to a specific value. If linked to another module their value is
I Input
changed by that module. If set to a specific value it will remain at that value.
Output parameters are outputs from the module. Most are available in the strategy and can be connected to the input of other modules. Some are only available to
O Output
text communications and BACnet communications.
Internal parameters control the way the module functions, they cannot be connected to another module. They will remain at the set value unless they are changed
N Internal
by a supervisor or tool, or another controller using an IC communications message. Some internal parameters are updated by the module as part of its operation.
Parameters are classified by data types.
Data Type Description
+Full analogue As for full analogue, but these parameters can only have zero and positive values.
Digital Binary digits having two states (0 or 1). If they are connectable parameters, they can only be connected to digital inputs or outputs as appropriate.
v3.30 firmware or greater: Double precision numeric parameters. If they are connectable parameters, they can only be connected to analogue inputs or outputs as
Double Precision appropriate.
A double precision analogue value has a negative excursion -1020 to 0 and positive excursion 0 to +1020. However, the resolution is 16 decimal digits.
Enum A special data type that is limited to a set of predefined constants. The variable must be equal to one of the values that have been predefined for it.
Floating point numeric parameters. If they are connectable parameters, they can only be connected to analogue inputs or outputs as appropriate.
A full analogue value has a negative excursion -1020 to 0 and positive excursion 0 to +1020. However, the resolution is 7.5 decimal digits (the actual number is
Full Analogue
16777215), so any further digits are represented by zeros. Thus, the number 98765432100 would be represented by 98765430000.
Other analogue parameters operate over a restricted range.
Integer Any whole number.
Strings Alphanumeric strings (e.g. used for labels).
Time The value is a time in the format hh:mm.
When configuring a controller only the modules used in the strategy are added to the controller's memory. This enables the number of each type of module to be adjusted to suit the
requirements of the strategy, so long as the memory capacity of the controller is not exceeded. The available capacity is measured in brIQs see the appropriate controller data sheet for
details of the capacity of each type of IQ4 controller. Each type of module has memory requirement - see the IQ4 Configuration Manual (TE201263).

IQ4 Modules
A1.1 Common IQ4 Module Parameters

This section provides a description of parameters common to most IQ4 modules.
Text
Parameter Description Range Default Type
Comms
0 or 1
Enables/disables the module. When disabled the module is not serviced. Its internal states and output will
Disable Module 1=Disabled 0 I ~
be maintained at their values prior to disabling.
0=Enabled
0 to 30-characters. Any ASCII
Label User-friendly label for the module. Blank N $
character except \/(){};,:
Page Page number containing the module. 0 to 255 0 N p
IQ41x: 0 to 300
IQ422: 0 to 600
IQ4NC/00/..: 0 to 600
IQ4NC/12/24VAC: 0 to 600
IQ4NC/16/XNC/...: 0 to 600
IQ4NC/32/XNC/...: 0 to 640
IQ4E: 0 to 600
The sequence step at which the module is serviced. It may be entered into the sequence table more than IQ4E/32: 0 to 600
Sequence Step 0 N @
once. If set to ‘0’ the module will be event driven. IQ4E/64: 0 to 640
IQ4E/96: 0 to 960
IQ4E/96/XNC: 1280
IQ4E/128: 0 to 1280
IQ4E/160: 0 to 1600
IQ4E/192: 0 to 1920
IQ422/00/XNC: 0 to 1280
IQ422/12/XNC: 0 to 600
0 or 1
Sequence Table Specifies whether the module is sequenced (in sequence table) or event driven. 1 = Sequenced 0 N #
0 = Event driven
X Co-ordinate Specifies the horizontal position of the module on a strategy page. 0 to 255 0 N x
Y Co-ordinate Specifies the vertical position of the module on a strategy page. 0 to 255 0 N y
Note: Although these parameters are common they may not all exist in all modules.

IQ4 Modules
A1.2 IQ4 Address Modules

Module Identifier R1
Size in brIQs 24
Default Overview Parameters None
The Address module is used to store the addressing data used for Trend communications. It also holds the general alarm status, the IQ4 type details, and details of memory available and
memory used. It does not appear on the strategy page and does not need to be sequenced.
A1.2.1 IQ4 Address Module Parameters
Text
Comms
0 or 1
Archive FARC alarm - Indicates if the archive of the running strategy file to flash memory
0 = OK 0 O E4
Failure has failed
1 = Failure
Attribute 2 Labels used with the identifier to help identify the IQ4. The seven attributes F
Attribute 3 (Attributes 2-7 plus the Identifier) are used in text communications for two G
functions:
Attribute 4 H
Option Description
Attribute 5 I
Message Allow the IQ4 to be identified either uniquely or as part of a
Attribute 6 Reception group, so that it may receive relevant communications. Any ASCII character except \/(){};,: Null N J
Can be used by the IC comms module to identify a controller
Message
or group of controllers with which this IQ4 wishes to
Transmission
Attribute 7 communicate. K
& | * ? . are reserved for special functions. Single letters should also be avoided
(S, K, W etc).
Baseboard
Baseboard version. Fixed - N b
version
Bootloader
Bootloader version used. Fixed - N c
version
brIQ capacity The total amount of strategy memory in the current IQ4. Measured in brIQs. - - N a
brIQs used The amount of memory used for the current strategy. Measured in brIQs. - - N t
Build Build number of the firmware version. Fixed - N B
0 or 1
Checksum
The status of the strategy data file in the IQ4. 1 = Strategy running - O e
OK
0 = Strategy not running

IQ4 Modules
Text
Comms
0 or 1
Controller on CONL alarm - Indicates when the IQ4 restarts successfully due to power up or
1 = Successful restart - O S0
Line an internal soft reset and loads up and runs a valid strategy.
0 = unsuccessful restart
HELP alarm - Indicates when there is a checksum failure (corrupt strategy). Set 0 or 1
Corrupt
when the IQ4 starts due to power up or an internal soft reset and is unable to load 0 = OK 0 O S1
Strategy
up and run a valid strategy. 1 = Failure
0 or 1
Device
Indicates whether the IQ4 has been discovered by a tool. 0 = Not discovered 0 O -
Discovered
1 = Discovered
External I/O
Total number of external I/O channels connected. 0 to 176 - N o
Count
0 or 1
External IO
Indicates whether the external I/O modules may be connected 0 = No external I/O modules - N k
Enabled
1 = External I/O modules maybe connected
External IO
The number of external I/O channels that may be connected. 0 to 176 - N l
Limit
0 or 1
FSSL alarm - indicates that an email alarm has not been sent due to an SLL
Fail SLL 0 = OK - N -
failure. When the fault is rectified a CSSL alarm is generated.
1 = Fail
0 or 1
FRTC alarm - Indicates if any of the parameters of the real-time clock are outside
Failed RTC 0 = OK - O S3
the range i.e. the RTC has failed.
1 = Fail
0 or 1
FLER alarm - Indicates if the IQ4 is unable to load its current strategy file, or the
File Error 0 = OK - O E6
backup to this file, and has had to load the original downloaded file.
1 = Fail
A number which refers to a list of files included in this version of IQ4. For Trend
File List - - N f
use only.
General 0 to 500
The Alarm Group module to which general alarms from the IQ4 are sent. 0 N g
Alarm Group 0 = not Sent
A label which describes the IQ4. It is sent as part of a text alarm message to
Identifier identify its source and should be unique on the site. It is also used as attribute 1 Any ASCII character except \/(){};,: Null N D
for text communications.

IQ4 Modules
Text
Comms
Arabic, Czech, Dansk, Deutsch, English, English US,
Language The language used for the display of web pages and display and transmission of Espanol, Francais, Hebrew, Italiano, Nederlands, Norsk,
English N P
selection alarms. Polski, Portugues, Romanian, Russian, Simplified
Chinese, Suomi, Svenska
Local
The network address of the IQ4. It must be unique on the Local LAN. 1, 4 to 119 excluding 10. 20 N L
Address
Local Lan The LAN number of the IQ4. 1, 4 to 119 excluding 10. 20 N N
Onboard IO
Number of I/O channels available in the IQ4 0 or 16 - N h
count
Override The time (minutes) for which a module set to override will stay in override before 0 to 1440
0 N T
Timer (mins) reverting to normal control. 0 = No override
IQ41x: 1000000
IQ422: 1000000
IQ4NC: 1000000
IQ4E: 1000000
Plot Memory IQ4E/32: 1000000
Memory capacity for plots (log points). - N V
Size IQ4E/64: 1000000
IQ4E/96: 1000000
IQ4E/128: 1000000
IQ4E/160: 1250000
IQ4E/192: 1500000
Plot Memory
The amount of memory already used for plots. - - N w
Used
Power Reset Set to '1' on power up for one sequence table cycle. 0 or 1 - O P
Send Service 0 or 1
Causes the IQ4 to send its service PIN message. 0 N !
PIN 1 = Send message
Sequence 0 or 1
STOR alarm - Indicates when the IQ4 is unable to complete the sequence of
Table 0 = OK - O E1
modules in the required time.
Overrun 1 = Fail
Serial
The serial number for the IQ4. Any ASCII character except \/(){};,: 0 - N M
Number
A unique machine readable alphanumeric code that identifies the site to a
Site GUID - Null N O
computer.

IQ4 Modules
Text
Comms
A human readable site identifier. All controllers on the site should have the same IQ4's MAC
Site Name 0 to 30-characters. Any ASCII character except \/(){};,: 0 N $
site name. Address
Strategy The revision of strategy. Incremented by IQSET each time strategy download file
1 to max 1 N d
Revision is created.
The network address of the local supervisor port on Local LAN. Unique on LAN.
Supervisor 0,4 to 119 excluding 10
If set to ‘0’ the device connected to the port can only communicate with the IQ4. 0 N U
Port 0 = Local device only
If set to non-zero it allows the connected device to talk over the network.
IQ41x,
IQ422,
Type Name The IQ4 type. IQ41x, IQ422, IQ4E, or IQ4NC N y
IQ4E,
IQ4NC
The network address of the sCNC associated with the local engineering (USB)
port. This port is for use by IQSET and enables it to access the whole network.
USB
If the set to ‘0’ a sCNC at address 125 is created for the period of the IQSET
Supervisor 0,4 to 119 excluding 10 0 N E
session. When the IQSET PC is removed the sCNC times out and no longer exists
Port
on the network. If set to non-zero, the sCNC remains on when the IQSET PC is
removed.
Version String indicating IQ4 type, firmware issue, I/O count and date. 25 characters. Any ASCII character except \/(){};,: 0 - N C
0 or 1
Indicates if XNC functionality is enabled - only applies to /XNC variants, set to
XNC Enabled 0 = Disabled - N x
‘0’ for all other variants.
1 = Enabled
For more details of the module see the IQ4 Configuration Reference Manual (TE201263).

IQ4 Modules
A1.3 IQ4 Alarm Destination Modules

Alarm Destination modules are used to define the destinations to which alarms can be sent. They specify where the alarms are to be sent; the format in which the alarm is sent, and can
determine when the alarms are sent. Alarms can either be sent to an address on the Trend network, to a specific IP address, or to a BACnet device.
IQ4 BACnet Alarm Destination Modules
IQ4 Trend Alarm Destination Modules
A1.3.1 IQ4 BACnet Alarm Destination Modules
Module Identifier e
Size in brIQs 14
Default Overview Parameters $, F
Available in IQ4/.../BAC
BACnet Alarm Destination modules define the destinations on the BACnet network to which alarms can be sent. They specify where the alarms are to be sent; the format in which the
alarm is sent, and can determine when the alarms are sent.
When an alarm is submitted for delivery the module will compare the priority of the alarm with the hold priority and if the alarm’s priority level is greater than the value of the hold
priority, the alarm will be sent. If the alarm is not sent, it will be stored until the priority of the alarm is higher than the hold priority. If an alarm is sent, then any other alarms being held
for that destination will also be sent. This allows calls to autodialled destinations to be limited to times when a high priority alarm is to be sent. The hold priority may be changed by a
time schedule to ensure that all low priority alarms are sent every day (e.g. during time of low call charges) if a high priority alarm is not generated.
A1.3.1.1 IQ4 BACnet Alarm Destination Module Parameters
The modules include the following parameters that are common to most modules: 'Label', 'Page', 'X co-ordinate' and 'Y co-ordinate' - see Common IQ4 Module Parameters, plus the
following:
Text
Comms
The BACnet device instance of the device to which the alarms are to be sent.
Device If set to ‘0’ the ‘Network Number’ and ‘MAC Address’ parameters are used to address the BACnet device to which the
0 to 4194393 0 N D
instance alarms are to be sent, otherwise it is addressed using the ‘Device instance’ parameter. It must be set up if remote device is
using DHCP.
IQ4v3.40 or greater. The end time of the period during which the alarms are to be sent to the destination in the format 00:00:00 to
End Time 00:00:00 I e
HH:MM:SS. 23:59:59
0 or 1
Indicates when the module is unable to reach the specified destination. Set to '1' when the destination device fails to
Failed 0 = Received 0 O F
acknowledge the receipt of an alarm after the second retry
1 = Failed
Hold The value defines the priority level below which alarms are held back. If an alarm is received above this level it, and all held
0 to 255 0 I H
Priority alarms, will be sent. It may be overridden if a high number of alarms are waiting to be sent.

IQ4 Modules
Text
Comms
0 or 1
0 = Clear
Inhibit Clear Specifies whether the Alarm Destination module will send clear alarms. alarms sent 0 N C
1 = Clear
alarms not sent
The BACnet MAC Address of the device to which the alarms are to be sent. When the 'Device instance' parameter is set to
MAC ‘0’ it is used in conjunction with the ‘Network Number’ parameter to address the BACnet device to which alarms are to be Valid MAC
Blank N M
Address sent. address
Note: BACnet MAC addresses do not have colon separators (e.g. A5C3A1BABAC0).
The network number of the BACnet device to which the alarms are to be sent. When the 'Device instance' parameter is set
Network
to ‘0’ it is used in conjunction with the ‘MAC Address’ parameter to address the BACnet device to which alarms are to be 0 to 65534 0 N N
Number
sent.
An integer that can be used in alarm messages to identify the alarm and enable the device receiving the alarm to process it 0 to
Process ID 0 N P
in a specific way, e.g. a specific ID could be used to identify all HVAC alarms. 4294967295
Retry The interval (in minutes) between batches of attempts to send alarm to destination. The interval should be set to '0' for
0 to 32767 0 N R
Interval autodialling to allow continual retries at 30 seconds.
0 or 1
0 = Outside
Schedule IQ4v3.40 or greater. Indicates if the module is in the period alarms are sent to the destination i.e. time of day is between the
period 0 O O
Output start and end time and the valid day bit is set.
1 = Inside
period
Defines whether the IQ4 expects an acknowledgement for the alarm (Confirmed) or will just send once and not expect an
0 to 1
acknowledgement (Unconfirmed). If set to Unconfirmed the IQ4 acknowledges the alarm itself so the ‘Failed’ parameter
Service 0 = Confirmed
will never get set to ‘1’ as the IQ4 has no way of knowing if the alarm transmission was successful. When set to confirmed, 0 N T
Type 1=
the IQ4 will expect an acknowledgement of the alarm, and will continue to send the alarm until one is received, or it has
Unconfirmed
determined that a failure has occurred.
No
Source The Alarm Route module(s) from which the Alarm Destination module accepts alarms. Route modules I Sc
connection
IQ4v3.40 or greater. The start time of the period during which the alarms are to be sent to the destination in the format 00:00:00 to
Start Time 00:00:00 I s
HH:MM:SS. 23:59:59

IQ4 Modules
Text
Comms
Specifies the changes in status that cause alarms to be sent. There are three different changes in alarm state that can generate
alarms:
State Change Description
To OffNormal The value has changed to one that is not in the normal range.
Transitions 000 to 111 111 N R
To Fault The value has changed to one that is the fault range.
To Normal The value has returned to the normal range.
It is bit field containing 3-bits: the left most bit enables/disables the To-Normal alarm, the middle bit enables/disables the
To-Fault alarm, and the right most bit enables/disables the To-OffNormal alarm.
The type of destination to which alarms are to be sent. It is set up in IQSET, and cannot be changed from the web page. The 4
Type 4 N Y
available parameters change with the destination type. 4 = BACnet
IQ4v3.40 or greater. The days during which the alarms are to be sent to the destination formatted as a bit string where the 0000000 to
Valid Days 0000000 I w
first bit represents Monday and last bit Sunday. E.g. 1000001 would be Monday and Sunday'. 1111111
A1.3.2 IQ4 Trend Alarm Destination Modules
Module Identifier e
Size in brIQs 14
Default Overview Parameters $, F
Trend Alarm Destination modules define the destinations on the Trend network to which alarms can be sent. They specify where the alarms are to be sent; the format in which the alarm
is sent, and can determine when the alarms are sent.
Alarms can either be sent to an address on the Trend network, to a specific IP address or host name, or an email address. The available parameters change with the destination type:
A1.3.2.1 IQ4 Trend Alarm Destination Module Parameters
following:

IQ4 Modules
Text
Comms
0 or 1
Indicates when the module is unable to reach the specified destination. Set to ‘1’ when the destination device fails to
Failed 0 = OK 0 O F
acknowledge the receipt of an alarm after the second retry.
1 = Failed
Hold The value defines the priority level below which alarms are held back. If an alarm is received above this level it, and all
0 to 255 0 I H
Priority held alarms, will be sent. It may be overridden if a high number of alarms are waiting to be sent.
0 or 1
0 = Clear alarms
Inhibit
Specifies whether the Alarm Destination module will send clear alarms. sent 0 N C
Clear
1 = Clear alarms
not sent
Retry The interval (in minutes) between batches of attempts to send alarm to destination. The interval should be set to '0' for
0 to 32767 0 N R
Interval autodialling to allow continual retries at 30 seconds.
No
Source The Alarm Route module(s) from which the Alarm Destination module accepts alarms. Route Modules I Sc
connection
1 to 3
The type of destination to which alarms are to be sent. It is set up in IQSET, and cannot be changed from the web page. 1 = IQ Lan
Type 1 N Y
The available parameters change with the destination type. 2 = IP Address
3 = Email
If Type is set to IQ Lan the module has the following additional parameters:
Text
Comms
0, 1, 4 to 119 excluding
Address The device address of the device to which alarms are to be sent. 10. 0 N A
0 = Not used
0, 1,4 to 119 excluding
LAN The LAN number of the device to which alarms are sent. 10. 0 N N
0 = Local LAN
0 to 3
The format of the alarm message. Coded and attribute alarms are for decoding by supervisors. Text alarms are
0 = Coded
Message man-readable.
1 = Text 0 N M
Format Always use Attribute alarms unless sending to a legacy supervisor or display that does not support them use in
2 = Attribute
which case ‘Text’.
3 = Enhanced (not used)

IQ4 Modules
If Type is set to IP Address the module has the following parameters:
Text
Comms
IP Address or host
Destination The IP address or hostname of the device to which alarms are to be sent. 128.1.1.4 N i
name
Destination
The TCP port on the device to which alarms are to be sent, where the receiving device will ‘listen’ for alarms. 0 to 65535 2774 N P
Port
0 to 3
0 = Coded
Message The format of the alarm message. Coded and attribute alarms are for decoding by supervisors. Text alarms are 1 = Text
0 N M
Format man-readable. 2 = Attribute
3 = Enhanced (not
used)
If Type is set to Email the module has the following additional parameters:
Parameter Description Range Default Type ID

Only available when 'Email' is selected. It specifies text added to the end of the email after the normal
Extra Text Any ASCII character except \/(){};,: Blank N e
alarm message (max 256 characters).
From Email Only available when 'Email' is selected. The email address which can receive email replies from the 0 to 64 characters. Any ASCII character
Blank N f
Address device to which alarms are to be sent. except \/(){};,: 0
To Email 0 to 64 characters. Any ASCII character
Only available when 'Email' is selected. The email address of the device to which alarms are to be sent. Blank N a
Address except \/(){};,: 0

IQ4 Modules
A1.4 IQ4 Alarm Group Modules

Module Identifier g
Size in brIQs 9
Default Overview Parameters $
Alarm Group modules are used to group together alarms that are to be handled in the same way. The module generating the alarm knows to which alarm group the alarm belongs. All
alarms for a group are assigned a priority that is used by the alarm destination modules to determine when they will be transmitted.
A1.4.1 IQ4 Alarm Group Module Parameters
The modules include the following parameter common to most modules: ‘Label’, - see Common IQ4 Module Parameters, plus the following:
Text
Comms
0 to 255
255 =
Hold Priority The priority of the alarm 0 I P
Highest
priority
Indicates when a new alarm occurs. It is set to ‘1’ for one sequence cycle whenever a new alarm, attached to the Alarm Group 0 or 1
New Alarm module, is generated. If alarms are occurring faster that once per sequence cycle, it will remain at ‘1’ until one sequence 1 = Alarm 0 O N
cycle after the last alarm occurred. 0 = No alarm
Alarm Route No
Output The Alarm Route module(s) used to route the alarms to their destination(s). O Oc
modules connection
User ACK
v3.50 or greater. Specifies which BACnet alarm state transitions require user acknowledgement. 000 to 111 000 O U
Enable

IQ4 Modules
A1.5 IQ4 Alarm Route Modules

Module Identifier o
Size in brIQs 9
Default Overview Parameters $, E
Alarm Route modules are used to specify to which destination alarms in a group are sent. The route will pass the alarm onto the alarm destination providing the enable bit is set. If the
enable bit is not set, the alarms will be stored in the alarm log, but will not be sent.
A1.5.1 IQ4 Alarm Route Module Parameters
following:
Parameter Description Range Default Type Text Comms

Alarm Group The Alarm Group module(s) for which it is to route alarms. Alarm Group modules Blank I Gc
Destination The Alarm Destination module to which the module will send alarms providing the enable input is set. Alarm Destination modules Blank O Dc
0 or 1
Enable Enables/Disables the route. 0 = Disabled 1 I E
1 = Enabled

IQ4 Modules
A1.6 IQ4 Calendar Modules

Module Identifier E
Size in brIQs -
Default Overview Parameters -
IQ4 v3.50 or greater
Calendar modules are designed to provide a Time Schedule module or exception with the date(s) it is to apply to. The output (Status parameter) is set to '0' or '1' depending on the
schedule set in the module. The schedule is made up of one or more Calendar entries each or which define a date or range of dates when the schedule is ON and the output set to '1'.
A1.6.1 IQ4 Calendar Module Parameters
A1.6.1.1 Module Properties
following:

Date List A list of Calendar Entries that have been added to the module. List of Calendar Entries - N D
0 or 1
Module Status The module's status. 0 O S
1 = Schedule indicates ON.
PIN Level The PIN level required before the module can be adjusted. 0 to 99 0 N P
A1.6.1.2 Calendar Entries
A Calendar module contains several Calendar Entries. Each calendar entry has a 'Label' parameter - see Common IQ4 Module Parameters, plus the following:
Text
Comms
0, 1, 2, 3, 4, 5, 6, 7
Day of the The day of the week when the schedule will come ON. When set to 'Unspecified'
0 = Unspecified - N A
Week any day is used. Only available when 'Use' is set to 'Week and Day'.
1 to 7 = Day of week (1 = Monday)
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
The day of the month when the schedule will go OFF. When set to 'Unspecified' 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31.
End Day - N E
any day is used. Only available when 'Use' is set to 'Range of Dates'. 0 = Unspecified
1 to 31 = Day of month
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
The month of the year when the schedule go OFF. When set to 'Unspecified' any
End Month 0 = Unspecified - N T
month is used. Only available when 'Use' is set to 'Range of Dates'.
1 to 12 = Month of year (1 = January)

IQ4 Modules
Text
Comms
The year when the schedule will go off. When set to 'Unspecified' any year is 0 to 9999
End Year - N R
used. Not used when 'Use' is set to 'Week and Date'. 0 = Unspecified
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14
The month of the year when the schedule will come ON. When set to 0 = Unspecified
Month of
'Unspecified' any month is used. Only available when 'Use' is set to 'Week and 1 to 12 = Month of year (1 = January) - N W
Year
Day'. 13 = Every odd month
14 = Every even month
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34.
0 = Unspecified
The day of the month when the schedule will come ON. When set to
Start Day 1 to 31 = Day of month - N S
'Unspecified' any day is used. Not used when 'Use' is set to 'Week and Date'.
32 = Last day of month
33 = Every odd day
34 = Every even day
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
0 = Unspecified
The month of the year when the schedule will come ON. When set to
Start Month 13 = Every odd month (January, March, May, July, September, - N O
'Unspecified' any month is used. Not used when 'Use' is set to 'Week and Date'.
November)
14 = Every even month (February, April, June, August,
October, December)
The year when the schedule will come ON. When set to 'Unspecified' any year 0, to 9999
Start Year - N Y
is used. Not used when 'Use' is set to 'Week and Date'. 0 = Unspecified
0, 1, 2, 3
1 = Date or Date Pattern
Date Option Specifies how the Calendar entry is to define the date(s). 1 N u
2 = Range of dates
3 = Week and Date

IQ4 Modules
A1.7 IQ4 Directory Modules

Module Identifier @
Size in brIQs 13
Directory modules, together with Display modules, enable views to be configured in an IQ controller for use by supervisors, commissioning tools, or display panels rather than having
to set them up separately in every device. Each module has a parent parameter, which refers to the directory module that precedes 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). When a PIN level is set, the user will need to be logged on at that PIN
level or higher to have access to the directory.
A1.7.1 IQ4 Directory Module Parameters
Text
Comms
Back The background colour for the page when displayed on a GraphIQ page. Specified using standard HTML colour format
# RRGGBB Blank N B
Colour using 2 hex characters in the range 0 to 255 reflecting the colour intensity.
The filename of the file (.JPG or .GIF) that is to be used as the background for the page when displayed on a GraphIQ
page. The filename cannot be longer than 34 characters.
Backdrop The use of backdrop files larger than 100k is not recommended. IQSET allows a maximum backdrop size of 200 Kbytes, Filename Blank N D
and a maximum capacity for all backdrops of 2 Mbytes. It will warn if a backdrop exceeds 100 Kbytes. They should be
sized to fit the screen being used to display the backdrop (see ‘Width’, ‘Height’ parameters).
Height Specifies the height of the page in pixels. 240 to 1200 768 N H
Label for the module. This is the title of the page when displayed on a GraphIQ page. 0 to 30-characters. Any
Label Note: If engineering Directory modules that are to be navigated using an IQView then it is recommended that the length ASCII character except Blank N $
of the label does not exceed 12-characters. SDU will truncate this to the first 20-characters. \/(){};,: 0
0 to 500
Parent The number of the directory module that is above this module in the hierarchy. 1 = Directory 1 (root) 0 N R
0 = Not configured
Refresh
The interval (in seconds) at which all values on a GraphIQ page are updated. 0 to 60 5 N E
Rate
0 to 99
User Level The user level required for the user to be able to view the directory. 0 N P
0 = No PIN required
Width The width of the page in pixels. 320 to 1600 1024 N W

IQ4 Modules
A1.8 IQ4 Display Modules

Display modules, together with Directory modules, enable views to be configured in an IQ controller for use by supervisors, commissioning tools, or display panels rather than having
to set them up separately in every device. Each Display module has a parent parameter, which is the Directory module to which it is attached.
There are two types of display module:
IQ4 Dynamic Display Modules
IQ4 Static Display Modules
A1.8.1 IQ4 Dynamic Display Modules
Module Identifier ~
Size in brIQs 19
Dynamic Display modules, together with Directory modules, enable views to be configured in an IQ controller for use by supervisors, commissioning tools, or display panels rather than
having to set them up separately in every device. They also enable values from the IQ4 controller to be included on the controller's graphical display pages. The value can be set to be a
link to the Details page of the module from which the value is sourced. Each display module has a parent parameter, which is the directory module to which it is attached; this is specified
automatically when the module is created.
A1.8.1.1 IQ4 Dynamic Display Module Parameters
Text
Comms
0 to 2
0 = Left
Align The alignment of the text on a GraphIQ page. Can only be set up if the ‘Width’ parameter is set to a value other than ‘0’. 1 N G
1 = Centre
2 = Right
Back The background colour for the text when it is displayed on a GraphIQ page. Specified using standard HTML colour format using
#RRGGBB #000000 N B
Colour 2 hex characters in the range 0 to 255 reflecting the colour intensity.
0 or 1
Clickable Specifies whether the value is a link to the detail page for the parameter that is being displayed. 1 = Link 1 N C
0 = No link
2
Display
Specifies the module type. 2 = Dynamic 1 N T
Subtype
Text

IQ4 Modules
Text
Comms
0 to 4
0 = Serif
1 = Sans-serif
Font Name The font used to display the text on a GraphIQ page. 0 N N
2 = Cursive
3 = Fantasy
4 = Monospace
Font size The size of the font (in points) used to display the text on a GraphIQ page. 6 to 72 12 N S
The colour the text is displayed in on a GraphIQ page. Specified using standard HTML colour format using 2 hex characters in
Fore Colour #RRGGBB #000000 N F
the range 0 to 255 reflecting the colour intensity.
In Alarm The colour of the text if the parameter from the IQ4 being displayed is in an alarm condition. Specified using standard HTML Fore
#RRGGBB N A
Colour colour format using 2 hex characters in the range 0 to 255 reflecting the colour intensity. colour
The module parameter that is to be displayed in the form:
<Module><Module Parameter>
<Module> specifies the type of module using its module identifier and module number (e.g., S1 for sensor 1).
Note: Only Sensor, Digital Input, Knob, Switch, Driver, and Time Schedule modules should be used. Other modules can be
used. However, they are only for use on GraphIQs; use in supervisors and displays may cause problems.
Valid module
Item <Module Parameter> specifies the parameter within the module that is to be displayed (e.g. sensor value). The module parameter Blank N I
parameter
is specified using the text comms identifier, and can be any parameter available within the specified module.
If <Module Parameter> is not specified, the default overview parameters for the module type are used. E.g. S1 would display
the sensor label, value, and units. The default overview parameters for each module are described in the module section of this
manual. Although multiple parameters are used as the default overview parameters it is only possible to specify single
parameters.
Left
The horizontal position of the top left corner of the value when it is displayed on a GraphIQ page. 0 to 1600 0 N X
Position
Parent The Directory module to which this item applies. 0 to 500 0 N R
Top
The vertical position of the top left corner of the value when it is displayed on a GraphIQ page. 0 to 1200 0 N Y
Position
0 to 99
User Level The level of the PIN required by the user to view the module. 0 = no PIN 0 N P
required
1 to 1600
Width The width of the text box in which the text is displayed. 0 N W
0 = Autosize

IQ4 Modules
A1.8.2 IQ4 Static Display Modules

Module Identifier ~
Size in brIQs 19
Static Display modules enable static text to be included on the controller's graphical display pages. The static text can be set to be a link to any specified URL. Each Display module has
a parent parameter, which is the Directory module to which it is attached; this is specified automatically when the module is created.
A1.8.2.1 IQ4 Static Display Module Parameters
Text
Comms
0 to 2
0 = Left
Align The alignment of the text on a GraphIQ page. Can only be set up if the ‘Width’ parameter is set to a value other than ‘0’. 1 N G
1 = Centre
2 = Right
Back The background colour for the text when it is displayed on a GraphIQ page. Specified using standard HTML colour format
#RRGGBB #000000 N B
Colour using 2 hex characters in the range 0 to 255 reflecting the colour intensity.
Display 1
Specifies the module type. 1 N T
Subtype 1 = Static Text
0 to 4
0 = Serif
1 = Sans-serif
Font Name The font used to display the text on a GraphIQ page. 0 N N
2 = Cursive
3 = Fantasy
4 = Monospace
Font size The size of the font (in points) used to display the text on a GraphIQ page. 6 to 72 12 N S
The colour the text is displayed in on a GraphIQ page. Specified using standard HTML colour format using 2 hex
Fore Colour #RRGGBB #000000 N F
characters in the range 0 to 255 reflecting the colour intensity.
0 to 30-characters.
Label Label for the module. Used as the text on a GraphIQ page. Any ASCII character Null N $
except \/(){};,: 0
Left
The horizontal position of the top left corner of the value when it is displayed on a GraphIQ page. 0 to 1600 0 N X
Position
Parent The Directory module to which this item applies. 0 to 500 0 N R
Top
The vertical position of the top left corner of the value when it is displayed on a GraphIQ page. 0 to 1200 0 N Y
Position

IQ4 Modules
Text
Comms
The URL accessed if the user clicks on the module on a GraphIQ page. This link can be to a page of information held
within the controller itself, a web site that is not the IQ4, or an email address.
If linking to a page of information held within the controller the reference should be entered in the format shown below:
trendModule:<Page>
Where <Page> specifies the page that is to be displayed. The format of <Page> varies depending on the destination.
If linking to a Graphical Display Page <Page> should be in the format below:
GraphIQs\<Directory Module Structure>\index.htm
Where <Directory Module Structure> is the directory module structure of the Display module that defines the page.
If linking to a Modules List Page <Page> should be in the format below:
<Module Type>.htm
Where <Module Type> specifies the type of module using its module identifier (e.g. S specifies sensor). For details of the
module identifiers see the appropriate module section of this manual.
URL Valid Link Blank N U
If linking to a Modules Details Page <Page> should be in the format below:
<Module Type><Module Number>.htm
Where <Module Type> specifies the type of module using its module identifier (e.g. S specifies sensor). For details of the
module identifiers see the appropriate module section of this manual.
If linking to an email address enter the required email address E.g. john.smith@work.com
If linking to a web site, enter the website’s URL. E.g. http://www.trendcontrols.com To link to a page in another IQ4
controller enter the URL for that page. If the destination controller has security set up add ? autoLogin=TRUE to the end
of the URL. This will pass the current login information to the destination controller. It is then compared with the users
set up in the destination controller and if it matches access is granted.
0 to 99
User Level The level of the PIN required by the user to view the module. 0 N P
0 = no PIN required
1 to 1600
Width The width of the text box in which the text is displayed. 0 N W
0 = Autosize

IQ4 Modules
A1.9 IQ4 Driver Modules

Driver modules are used to drive HVAC equipment using output channels. They 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/OFF.
IQ4 Analogue Driver Modules
IQ4 Binary Hysteresis Driver Modules
IQ4 Digital Driver Modules
IQ4 Multi Stage Digital Driver Modules
IQ4 Raise/Lower Continuous Driver Modules
IQ4 Raise/Lower End Driver Modules
IQ4 Time Proportional Driver Modules
IQ4 Time Proportional + O/R Driver Modules
A1.9.1 IQ4 Analogue Driver Modules
Module Identifier D
Size in brIQs 52
Default Overview Parameters $, l
The Analogue Driver module provides an analogue signal in the range 0 to 10 Vdc, or 0 to 20 mA depending on the hardware. It calculates the value of its output (L) by taking the value
of the input S, limiting it to 0 to 100, and then applying offset and range values if specified.
The module can be disabled using the module state parameter. When the module is disabled its output is not updated, and is not passed on to any linked modules.
The output of the module can be overridden to the value specified by the Override Status/Value parameter by setting the Override Output parameter to '1'.
A1.9.1.1 IQ4 Analogue Driver Module Parameters
The modules include the following parameters that are common to most modules: 'Disable Module', 'Label', 'Page', 'Sequence Step', 'Sequence Table', ‘X co-ordinate’ and ‘Y co-ordinate’
- see Common IQ4 Module Parameters, plus the following:
Text
Comms
0 to 16
0 = Source unconnected
and no other active input.
3 = HOA switch override.
The current priority level of the input to the module's algorithm. Normal strategy operation writes to
Active priority level 4 = Override 10 O u
priority level ‘10’. If a higher priority value comes in from BACnet, this controls the module.
9 = IC comms write
10 = Strategy
16 = BACnet
0 = highest priority

IQ4 Modules
Text
Comms
v3.70 or greater. The period (in seconds) for which the HOA input must be in an alarm condition before
Alarm Delay (secs)(HOA) 0 to 178200 0 I d1(D)
the maintenance alarm is generated.
The period (in seconds) for which the maintenance input must be in an alarm condition before the
Alarm Delay maintenance alarm is generated.
0 to 178200 0 I m1(D)
(secs)(maintenance) Note: Should normally be set to ‘0’ as the alarm is normally set by strategy which already includes a
delay.
The period (in seconds) for which the readback input must be in an alarm condition before the readback
Alarm Delay (secs) alarm is generated.
0 to 178200 0 I r1(D)
(readback) Note: Should normally be set to ‘0’ as it is normal practice to use a readback module to set the alarm
state which already includes a delay.
Alarm Group (HOA) v3.70 or greater. The Alarm Group module to which the HOA alarm will be sent. 0 to 500 1 N d1(G)
Alarm Group
The Alarm Group module to which the maintenance alarm will be sent. 0 to 500 1 N m1(G)
(maintenance)
Alarm Group (readback) The Alarm Group module to which the readback alarm will be sent. 0 to 500 1 N r1(G)
0 or 1
Alarm Sent (maintenance) Indicates if the maintenance alarm has been sent to the Alarm Group module. 0 = Not sent 0 O m1(K)
1 = Sent
0 or 1
Alarm Sent (readback) Indicates if the readback alarm has been sent to the Alarm Group module. 0 = Not sent 0 O r1(K)
1 = Sent
0 or 1
Alarm state (HOA) v3.70 or greater. The state of the HOA alarm condition. 0=No alarm 0 O d1(S)
1=Alarm
0 or 1
Alarm state (maintenance) The state of the maintenance interval alarm condition. 0=No alarm 0 O m1(S)
1=Alarm
0 or 1
Alarm State (readback) The state of the readback alarm condition. 1 = Alarm 0 O r1(S)
0 = No Alarm
Anti-phase Hardware 0 to 196
The output channel on the specified I/O module used by the driver’s anti-phase output. 0 N A
Channel 0=not connected
Anti-phase Output The value of the anti-phase output channel. 0 to 1000 0 O a

IQ4 Modules
Text
Comms
0 or 1
Clear Alarm (HOA) v3.70 or greater. Enables/disables reporting of the HOA clear alarm. 1=Enabled 1 N m1(C)
0=Disabled
0 or 1
Clear Alarm
Enables/disables reporting of the maintenance interval clear alarm. 1=Enabled 1 N m1(C)
(maintenance)
0=Disabled
0 or 1
Clear Alarm (readback) Enables/disables reporting of the readback clear alarm. 1=Enabled 1 N r1(C)
0=Disabled
Clear Alarm Delay (secs) v3.70 or greater. The period (in seconds) for which the HOA alarm must be cleared before the clear
0 to 178200 0 I d1(C)
(HOA) alarm is generated.
v3.50 or greater. The period (in seconds) for which the readback input must be cleared before the clear
Clear Alarm Delay (secs) alarm is generated.
0 to 178200 0 I r1(d)
state and this already includes a delay.
v3.50 or greater. The period (in seconds) for which the maintenance input must be cleared before the
Clear Alarm Delay clear alarm is generated.
0 to 178200 0 I m1(d)
delay.
The amount by which the driver value must change before a BACnet COV notification message is sent + Full analogue
COV Increment 0 N C
to those subscribers in the list of subscribers who have subscribed to this parameter. 0 = no notification
0 or 1
Enabled (HOA) v3.70 or greater. Enables/disables reporting of the HOA alarm. 1=Enabled 0 I d1(E)
0=Disabled
0 or 1
Enabled (maintenance) Enables/disables reporting of the maintenance interval alarm. 1=Enabled 0 I m1(E)
0=Disabled
0 or 1
Enabled (readback) Enables/disables reporting of the readback alarm. 1=Enabled 0 I r1(E)
0=Disabled
0 to 30
The address of the physical I/O module that contains the input channel providing the module’s input -
Hardware Module 0 = IQ4 0 N i
only applies to IQ4E, set to ‘0’ for all other types of IQ4.
1 to 30 = I/O modules

IQ4 Modules
Text
Comms
0, 1, 2, 3
The Hand/Off/Auto status of the module’s output if it is on an I/O module that supports Hand/Off/Auto 0 = Auto
HOA State operation. Always ‘0’ when the module’s output is on one of the IQ4’s on board outputs or on an I/O 1 = Hand 0 O h
module that does not support Hand/Off/Auto operation. 2 = Off
3 = Error
0, 8, and 9
The module’s alarm status. The alarm state is shown if the alarm condition has been present for longer 0 = No alarm
In Alarm 0 O !
than that alarm’s delay time, and that alarm is enabled to be reported. 8 = Maintenance Alarm
9 = Readback Alarm
in-phase Hardware 0 to 32
The output channel on the specified I/O module used by the driver. 0 N L
Channel 0=Disabled
in-phase Output The value of the in-phase output channel. 0 to 1000 0 O l
0 or 1
Invert Logically inverts the driver’s output. 1=Inverted 0 I I
0=Normal
0 or 1
Maintenance Input The maintenance interval alarm input to the Driver module. 0=No alarm 0 I s
1=Alarm
0 to 5
0 = Normal (automatic
control)
1 = Overridden
2 = Disabled
Module Status The module's status. 0 O _
3 = Hand (manually set
on)
4 = Off (manually set off)
5 = BACnet (BACnet in
control)
The percentage of the output to which the 0% input level corresponds (i.e. 20 % offset means that 0%
Offset 0 to 100 0 I O
input corresponds to 2V output).
0 or 1
Override Output Overrides the Driver module’s output to the override value or status set in 'Override' parameter. 1 = override 0 I ^
0 = no override
Override Value The value to which the module is overridden when the ‘Override Output’ parameter is set to ‘1’. Full analogue 0 I v

IQ4 Modules
Text
Comms
The period (in seconds) after the IQ4 is powered up or performs a soft restart before the driver output is
Power on Delay (secs) 0 to 1275 0 N T
switched on.
The percentage of the output which corresponds to the 0 to 100% input range (i.e. a range of 60% means
Range 0 to 100 0 I R
that an input range of 0 to 100 % corresponds to an output range of 6 V).
0 or 1
Readback Input The readback alarm input to the driver. 0=No alarm 0 I b
1=Alarm
Source The value input to the Driver module. Full analogue 0 I S
Time in Alarm (secs)
The elapsed time in seconds since the readback alarm state commenced. + Full analogue 0 O m1(T)
(maintenance)
The elapsed time in seconds since the HOA alarm state commenced. + Full analogue 0 O d1(T)
(HOA)
The elapsed time in seconds since the maintenance alarm state commenced. + Full analogue 0 O r1(T)
(readback)
Value The current drive level Full analogue 0 O V
A1.9.2 IQ4 Binary Hysteresis Driver Modules
Module Identifier D
Size in brIQs 54
The Binary Hysteresis driver module provides an ON/OFF type output from an analogue input. It has an analogue input S and provides a single digital output l with an optional antiphase
output a. The state of l is calculated by comparing the value of S with the ON and OFF switching levels. If (S) goes above the ON switching level, l will be set to 1, and if it is below the
OFF switching level, l will be set to 0. If an antiphase output is used the state of a will always be opposite to the state of l.
The binary hysteresis driver module supports connection to an HOA module (XCITE/IO/8DO/HOA or XCITE/IO/4DO/HOA). This enables the driver’s output to be set to ON (Hand)
or OFF or to use the calculated value (Auto) using a hardware switch connected to the module’s output channel(s).
The HOA parameter (h) indicates position of the switch. When only the in-phase channel is being used the HOA parameter (h) indicates the position of the switch for the output channel
the in-phase output (l) is connected to. When only the antiphase channel is being used the HOA parameter (h) indicates the position of the switch for the output channel the antiphase
phase output (a) is connected to. If both the in phase and antiphase channels are being used the HOA parameter (h) is set as per the table below:

IQ4 Modules
in-phase output Antiphase output Value of HOA Parameter (h)

Auto Auto Auto
Auto Hand Hand
Auto OFF OFF
Hand Auto Hand
OFF Auto OFF
Hand Hand Hand
Hand OFF Hand
OFF Hand Hand
If an error condition (3) is received from the I/O module, then the channel shall be assumed to be in Auto.
A1.9.2.1 IQ4 Binary Hysteresis Driver Module Parameters
Text
Comms
0 to 16
9 = IC comms write
10 = Strategy
16 = BACnet
v3.70 or greater. The period (in seconds) for which the HOA input must be in an alarm condition before
the maintenance alarm is generated.
0 to 178200 0 I m1(D)
delay.
0 to 178200 0 I r1(D)

IQ4 Modules
Text
Comms
Alarm Group
(maintenance)
0 or 1
1 = Sent
0 or 1
1 = Sent
0 or 1
1=Alarm
0 or 1
1=Alarm
0 or 1
0 = No Alarm
0 or 1
0=Disabled
0 or 1
Clear Alarm
(maintenance)
0=Disabled
0 or 1
0=Disabled
0 to 178200 0 I d1(C)

IQ4 Modules
Text
Comms
0 to 178200 0 I r1(d)
0 to 178200 0 I m1(d)
delay.
0 or 1
0=Disabled
COV Increment 0 N C
0 or 1
0=Disabled
0 or 1
0=Disabled
0 or 1
0=Disabled
0 to 30
0, 1, 2, 3
3 = Error
Hours Run The time (in hours) for which the in-phase output (prior to inversion) has been ON. 0 to 87600 0 O H

IQ4 Modules
Text
Comms
0, 8, and 9
In Alarm 0 O !
9 = Readback Alarm
Channel 0=Disabled
in-phase Output The value of the in-phase output channel. 0 or 1 0 O l
0 or 1
0=Normal
0 or 1
1=Alarm
0 to 5
control)
1 = Overridden
2 = Disabled
on)
control)
Number of Starts The number of times the in-phase output (prior to inversion) has been transitioned from ‘0’ to ‘1’. 0 to 109 0 O N
The input level at and below which the Driver module will switch OFF. Can be connected to an analogue
OFF Level 0 to 100 0 I F
output.
The input level at and above which the Driver module will switch ON. Can be connected to an analogue
ON Level 0 to 100 0 I O
output.
0 or 1
0 = no override

IQ4 Modules
Text
Comms
switched on.
0 or 1
1=Alarm
(maintenance)
(HOA)
(readback)
A1.9.3 IQ4 Digital Driver Modules
Module Identifier D
Size in brIQs 52
The Digital Driver module provides an ON/OFF type output controlled by the state of a digital bit. It has a single digital source S and provides a single digital output l with an optional
antiphase output a. The state of l is determined directly by the state of S; if used, the state of A is always opposite to (l).
The Digital Driver module supports connection to an HOA module (XCITE/IO/8DO/HOA or XCITE/IO/4DO/HOA). This enables the driver’s output to be set to ON (Hand) or OFF or
to use the calculated value (Auto) using a hardware switch connected to the module’s output channel(s).
phase output (a) is connected to. If both the in phase and antiphase channels are being used the HOA parameter (h) as per the table below:

Auto Auto Auto

IQ4 Modules

Auto Hand Hand
Auto OFF OFF
Hand Auto Hand
OFF Auto OFF
Hand Hand Hand
Hand OFF Hand
OFF Hand Hand
A1.9.3.1 IQ4 Digital Driver Module Parameters
Text
Comms
0 to 16
The current priority level of the input to the module's algorithm. Normal strategy operation 3 = HOA switch override.
Active priority level writes to priority level ‘10’. If a higher priority value comes in from BACnet, this controls the 4 = Override 10 O u
module. 9 = IC comms write
10 = Strategy
16 = BACnet
Alarm Delay v3.70 or greater. The period (in seconds) for which the HOA input must be in an alarm condition
0 to 178200 0 I d1(D)
(secs)(HOA) before the maintenance alarm is generated.
The period (in seconds) for which the maintenance input must be in an alarm condition before
Alarm Delay the maintenance alarm is generated.
0 to 178200 0 I m1(D)
(secs)(maintenance) Note: Should normally be set to ‘0’ as the alarm is normally set by strategy which already
includes a delay.
The period (in seconds) for which the readback input must be in an alarm condition before the
Alarm Delay (secs) readback alarm is generated.
0 to 178200 0 I r1(D)
(readback) Note: Should normally be set to ‘0’ as it is normal practice to use a readback module to set the
alarm state which already includes a delay.

IQ4 Modules
Text
Comms
Alarm Group
(maintenance)
0 or 1
1 = Sent
0 or 1
1 = Sent
0 or 1
1=Alarm
0 or 1
Alarm state
The state of the maintenance interval alarm condition. 0=No alarm 0 O m1(S)
(maintenance)
1=Alarm
0 or 1
0 = No Alarm
Anti-phase Output The value of the anti-phase output channel. 0 or 1 0 O a
Clear Alarm Delay (secs) v3.70 or greater. The period (in seconds) for which the HOA alarm must be cleared before the
0 to 178200 0 I d1(d)
(HOA) clear alarm is generated.
v3.50 or greater. The period (in seconds) for which the readback input must be cleared before
Clear Alarm Delay (secs) the clear alarm is generated.
0 to 178200 0 I r1(d)
(readback) Note: Should normally be set to ‘0’ as it is normal practice to use a readback module to set the
alarm state and this already includes a delay.
v3.50 or greater. The period (in seconds) for which the maintenance input must be cleared
Clear Alarm Delay before the clear alarm is generated.
0 to 178200 0 I m1(d)
(secs)(maintenance) Note: Should normally be set to ‘0’ as the alarm is normally set by strategy which already
includes a delay.

IQ4 Modules
Text
Comms
0 or 1
0=Disabled
0 or 1
Clear Alarm
(maintenance)
0=Disabled
0 or 1
0=Disabled
0 or 1
0=Disabled
0 or 1
0=Disabled
0 or 1
0=Disabled
0 to 30
The address of the physical I/O module that contains the input channel providing the module’s
input - only applies to IQ4E, set to ‘0’ for all other types of IQ4.
0, 1, 2, 3
The Hand/Off/Auto status of the module’s output if it is on an I/O module that supports 0 = Auto
HOA State Hand/Off/Auto operation. Always ‘0’ when the module’s output is on one of the IQ4’s on board 1 = Hand 0 O h
outputs or on an I/O module that does not support Hand/Off/Auto operation. 2 = Off
3 = Error
0, 8, and 9
The module’s alarm status. The alarm state is shown if the alarm condition has been present for 0 = No alarm
In Alarm 0 O !
longer than that alarm’s delay time, and that alarm is enabled to be reported. 8 = Maintenance Alarm
9 = Readback Alarm
Channel 0=Disabled

IQ4 Modules
Text
Comms
0 or 1
0=Normal
0 or 1
1=Alarm
0 to 5
control)
1 = Overridden
Module Status The module's status. 2 = Disabled 0 O _
3 = Hand (manually set on)
control)
The number of times the in-phase output (prior to inversion) has been transitioned from ‘0’ to
Number of Starts 0 to 109 0 O N
‘1’.
0 or 1
0 = no override
The value to which the module is overridden when the ‘Override Output’ parameter is set to
Override Status 0 or 1 0 I v
‘1’.
The period (in seconds) after the IQ4 is powered up or performs a soft restart before the driver
output is switched on.
0 or 1
1=Alarm
date&time;yyyy-mm- 0000-00-
Time of Hours Run Reset The time that the cumulative hours run was last reset to ‘0’, in full date and time format. O t
dd&Thh:mm:ss 00T00:00:00
Time of Last Value date&time;yyyy-mm- 0000-00-
The time that the output last changed state, in full date time format. O c
Change dd&Thh:mm:ss 00T00:00:00

IQ4 Modules
Text
Comms
Time of Number of Starts date&time;yyyy-mm- 0000-00-
The time that the cumulative number of starts was last reset to ‘0’, in full date and time format. O e
Reset dd&Thh:mm:ss 00T00:00:00
(maintenance)
(HOA)
(readback)
Value The current drive level 0 or 1 0 O V
A1.9.4 IQ4 Multi Stage Digital Driver Modules
Module Identifier D
Size in brIQs 61
Default Overview Parameters $, _
Multi Stage Digital Driver modules enable the controller to sequence multiple outputs and is ideal for controlling fan speed relays or boilers. They switch several outputs ON and OFF
as the input value (Source (S)) changes between stages. The driver changes between stages as the input value passes through each integer up to the maximum number of stages determined
by the Number of Stages parameter depending on the selected switching type.
Note: The driver requires consecutive outputs channels e.g. for 3 stages it will automatically take 3 consecutive inputs station from the output specified by the 'in-phase Hardware
Channel' parameter. These outputs cannot be spread across I/O modules.
The way in which the outputs are turned ON/OFF is determined by the Switching Type parameter which can be set to one of 3 modes:
Sequenced (One output is turned ON at a time in sequence.)
Cascaded (Outputs turned on in sequence leaving previous outputs ON (each step adds to the next).)
Binary (The input value is decoded to switch any combination of outputs.)
Sequenced
In sequence mode, only one output is ever enabled. As the Source (S) increases, or decreases, the output turns OFF before the next output turns ON. There is a delay of 300ms when
switching between stages to ensure that only one relay is active at a time.
The table below shows how the outputs are turned ON as the source (S) increases.
Source Value Value OP1 OP2 OP3 OP4 OP5 OP6 OP7 OP8
<0 0

IQ4 Modules
>=1<2 1 ON
>=2<3 2 ON
>=3<4 3 ON
>=4<5 4 ON
>=5<6 5 ON
>=6<7 6 ON
>=7<8 7 ON
>=8 8 ON
The first output turned ON (Lead Output) can be specified using the Lead Output parameter. The table below shows how the outputs are turned on if the Lead Output parameter is set
to '3'.
<0 0
>=1<2 1 ON
>=2<3 2 ON
>=3<4 3 ON
>=4<5 4 ON
>=5<6 5 ON
>=6<7 6 ON
>=7<8 7 ON
>=8 8 ON
The number of stages can be specified (maximum of 8) using the Number of Stages parameter. The table below shows how the outputs are turned ON as the source (S) increases when
the Number of Stages parameter is set to '3'.
Source Value Value OP1 OP2 OP3

<0 0
>=1<2 1 ON
>=2<3 2 ON
>=3 3 ON
The Lead Output and Number of Stages parameters can be used together to provide flexibility in how the outputs are turned ON and OFF. The table below shows how the outputs are
turned ON as the source (S) increases when the Number of Stages parameter is set to '5' and the Lead Output is parameter is set to 4.

IQ4 Modules
Source Value Value OP1 OP2 OP3 OP4 OP5

<0 0
>=1<2 1 ON
>=2<3 2 ON
>=3<4 3 ON
>=4<5 4 ON
>=5 5 ON
Cascaded
In cascade mode, the number of outputs turned ON increases as the Source (S) increases and decreases as the value falls. There is no time delay when switching between stages.
<0 0
>=1<2 1 ON
>=2<3 2 ON ON
>=3<4 3 ON ON ON
>=4<5 4 ON ON ON ON
>=5<6 5 ON ON ON ON ON
>=6<7 6 ON ON ON ON ON ON
>=7<8 7 ON ON ON ON ON ON ON
>=8 8 ON ON ON ON ON ON ON ON
to '3'.
<0 0
>=1<2 1 ON
>=2<3 2 ON ON
>=3<4 3 ON ON ON
>=4<5 4 ON ON ON ON

IQ4 Modules

<0 0
>=1<2 1 ON
>=2<3 2 ON ON
>=3 3 ON ON ON

<0 0
>=1<2 1 ON
>=2<3 2 ON ON
>=3<4 3 ON ON ON
>=4<5 4 ON ON ON ON
>=5 5 ON ON ON ON ON
Binary
In binary mode, the source value (Source (S)) is converted from an analogue value to a bit array. Each bit in the array corresponds to an output and they will reflect its status. E.g.
00001010 would indicate outputs 4 and 2 ON. There is no time delay between switching outputs. The lead output parameter is not supported in this mode. The source valve can be 0 to
255.
The table below shows how the outputs are turned ON as the source (S) increases from 0 to 8.
Source Value Value Bit Array OP1 OP2 OP3 OP4 OP5 OP6 OP7 OP8
<0 0 00000000
>=1<2 1 00000001 ON
>=2<3 2 00000010 ON
>=3<4 3 00000011 ON ON
>=4<5 4 00000100 ON

IQ4 Modules
>=5<6 5 00000101 ON ON
>=6<7 6 00000110 ON ON
>=7<8 7 00000111 ON ON ON
>=8<9 8 00001000 ON
As the value increases the outputs will be turned ON accordingly. E.g. if the source value is 230 the bit array would be '11100110' and the outputs would be turned ON as shown.
>=230<231 230 11100110 ON ON ON ON ON
The table below shows some more examples of which outputs are turned on for a specific value.
>=45<45 45 00101101 ON ON ON ON
>=67<68 67 01000011 ON ON ON
>=85<86 85 01010101 ON ON ON ON
>=101<102 101 01100101 ON ON ON ON
>=134<135 134 10000110 ON ON ON
>=158<159 158 10011110 ON ON ON ON ON
>=179<180 179 10110011 ON ON ON ON ON
>=200<201 200 11001000 ON ON ON
>=255 255 11111111 ON ON ON ON ON ON ON ON
the in-phase output (l) is connected to. The way the HOA parameter's value is determined depends on the module’s Switching Type mode. For Cascade and Binary Mode if any of the
Driver’s outputs are not in Auto, the HOA parameter is set to Hand. For Sequenced mode if any of the Driver’s outputs are not in Auto, the HOA parameter is set to Hand. All other
outputs that are in Auto are set to OFF by the Driver module as soon as the Hand condition is detected, and if an error condition (3) is received from the I/O module, the channel shall
be assumed to be in Auto.

IQ4 Modules
A1.9.4.1 IQ4 Multi Stage Digital Driver Module Parameters

Text
Comms
0 to 16
9 = IC comms write
10 = Strategy
16 = BACnet
v3.70 or greater. The period (in seconds) for which the HOA input must be in an alarm condition
before the maintenance alarm is generated.
0 to 178200 0 I m1(D)
delay.
0 to 178200 0 I r1(D)
Alarm Group
(maintenance)
0 or 1
1 = Sent
0 or 1
1 = Sent

IQ4 Modules
Text
Comms
0 or 1
1=Alarm
0 or 1
1=Alarm
0 or 1
0=Disabled
0 or 1
0 = No Alarm
0 or 1
Clear Alarm
(maintenance)
0=Disabled
0 or 1
0=Disabled
0 to 178200 0 I d1(d)
0 to 178200 0 I r1(d)
0 to 178200 0 I m1(d)
delay.
The amount by which the driver value must change before a BACnet COV notification message is + Full analogue
COV Increment 0 N C
sent to those subscribers in the list of subscribers who have subscribed to this parameter. 0 = no notification
0 or 1
0=Disabled

IQ4 Modules
Text
Comms
0 or 1
0=Disabled
0 or 1
0=Disabled
0 to 30
0, 1, 2, 3
3 = Error
0, 8, and 9
In Alarm 0 O !
9 = Readback Alarm
Channel 0=Disabled
Not binary. This defines the first output channel (relative to the In-phase Output) to be energised as
0 to maximum number of
Lead Output the input value increases from 0 (e.g. Lead Output = 2 with In-phase Output = 2, means channel 3 will 1 I D
stages
be energised first).
0 or 1
1=Alarm

IQ4 Modules
Text
Comms
0 to 5
control)
1 = Overridden
2 = Disabled
on)
control)
IQ41x = 0 to 6
IQ422 = 0 to 6
IQ4E = 0 to 8
The number of output channels used. The channels allocated will continue sequentially from the In-
Number of Stages IQ4NC/00. = 0 to 6 0 N R
Phase channel.
IQ4NC/12 = 0 to 6
IQ4NC/16/ = 0 to 8
IQ4NC/32 = 0 to 8
The number of transitions from the state where all the output channels are OFF to the state where any
Number of Starts of the output channels are on (i.e. from where the ‘State’ parameter is ‘0’ to where the ‘State’ parameter 0 to 109 0 O N
is non-zero).
The 8 status bits which indicate which output channels are energised (corresponds to the state
Output Status 000000000 to 11111111 00000000 O F
parameter).
0 or 1
0 = no override
The period (in seconds) after the IQ4 is powered up or performs a soft restart before the driver output
is switched on.
0 or 1
1=Alarm

IQ4 Modules
Text
Comms
The current state of output channels as an analogue value whose binary equivalent indicates the output
channels which are energised (e.g. a value of 10 indicates that channels 4 and 2 are energised).
State 0 to 255 0 O B
This output is coded such that it may be connected to a Type 18 (Analogue to Digital Converter)
Function module so that the energised channels can be decoded.
0, 1, or 2
0 = Sequenced
Switching Type The type of sequencing. 0 N P
1 = Cascade
2 = Binary
(maintenance)
(HOA)
(readback)
A1.9.5 IQ4 Raise/Lower Continuous Driver Modules
Module Identifier D
Size in brIQs 57
The Raise/Lower Continuous Driver module is designed to drive a split phase motor. It should be used for actuators with reversible action motors with built-in positioning, limit switches,
or clutches.
It provides either two digital outputs (L and A), or a single analogue output from a single analogue input S. Setting (A) to 0, selects a single analogue output. It also has the facility to
accept a feedback-input F.
When the driver is operating with two digital outputs, (L) will be set to 1 for a period if (S) is greater than the valve position, and (A) will be set to 1 for a period if (S) is less than the
valve position. This period is calculated as a percentage of the full-scale drive time. The actual percentage is determined by the difference between (S) and the valve position.
When operating with a single analogue output, the value of the output will be set to the appropriate value to drive the associated relay module. If (S) is greater than the valve position,
the output value will be set to 10 V to cause the associated relay module to raise for a period. If (S) is less than the valve position the output value will be set to 4 V causing the associated
relay module to lower for a period. This period is calculated as a percentage of the full-scale drive time. The actual percentage is determined by the difference between (S) and the valve
position. If (S) is equal to the valve position, the output value is set to 7 V. If (S) is negative the output value will be set to 0 V.

IQ4 Modules
The module needs to know the position of the valve. This can be done either by estimating the position, or by using a feedback-input. If the feedback-input F is set to 0, the position of
the valve is estimated by using the full-scale drive time and the sum of the amounts of time that the valve has been driven in each direction. (E.g. If the full-scale drive time is 10 s and
the valve has been driven open from the closed position for 8s and then driven closed for 3s making a total of 5s in the open direction (8-3). The estimated value position would be 50%
open, because the value has been driven open for half the full-scale drive time). The valve position is verified when the value is required to be fully closed or fully open (0% or 100) by
driving continuously in the required direction. This ensures that the valve has reached the end stop. If a feedback-input is used, the position of the valve will be known exactly. The
module then determines if the valve is where it is expected to be, and if not the output signal is changed to correct the error.
The Raise/Lower Continuous Driver module supports connection to an HOA module (XCITE/IO/8DO/HOA or XCITE/IO/4DO/HOA). This enables the driver’s output to be set to ON
(Hand) or OFF or to use the calculated value (Auto) using a hardware switch connected to the module’s output channel(s).

Auto Auto Auto
Auto Hand Hand
Auto OFF OFF
Hand Auto Hand
OFF Auto OFF
Hand Hand Hand
Hand OFF Hand
OFF Hand Hand

IQ4 Modules
A1.9.5.1 IQ4 Raise/Lower Continuous Driver Module Parameters

Text
Comms
0 to 16
3 = HOA switch
The current priority level of the input to the module's algorithm. Normal strategy operation writes to override.
Active priority level 10 O u
priority level ‘10’. If a higher priority value comes in from BACnet, this controls the module. 4 = Override
9 = IC comms write
10 = Strategy
16 = BACnet
0 to 178200 0 I m1(D)
delay.
0 to 178200 0 I r1(D)
Alarm Group
(maintenance)
0 or 1
1 = Sent
0 or 1
1 = Sent
0 or 1
1=Alarm

IQ4 Modules
Text
Comms
0 or 1
0 = No Alarm
0 or 1
Clear Alarm
(maintenance)
0=Disabled
0 or 1
0=Disabled
0 to 178200 0 I r1(d)
0 to 178200 0 I m1(d)
delay.
COV Increment 0 N C
The current HVAC equipment item’s position as a percentage of it full range as understood by the Driver
Drive Position module. If there is no feedback (boundless) it is estimated, otherwise it will reflect the ‘Feedback’ 0 to 100 0 O P
parameter.
0 or 1
0=Disabled
0 or 1
0=Disabled
A positional feedback input to the Driver module. This enables the HVAC equipment item’s actual
Feedback Full analogue 0 I F
position to be fed back to the Driver module. If set to a specific value, it will be ignored.

IQ4 Modules
Text
Comms
The time in seconds taken to drive the HVAC equipment item (e.g. actuator) over its full range. Can be 0 to 32767
full-scale Drive 0 I D
connected to an analogue output. 0 = Not enabled
0 to 30
0, 1, 2, 3
3 = Error
0, 8, and 9
In Alarm 0 O !
9 = Readback Alarm
Channel 0=Disabled
0 or 1
0=Normal
0 or 1
1=Alarm
0 to 5
control)
1 = Overridden
2 = Disabled
on)
control)

IQ4 Modules
Text
Comms
0 or 1
0 = no override
switched on.
0 or 1
1=Alarm
When enabled the behaviour of the raise and lower channels are swapped enabling the drive direction to 0 or 1
Reverse Operation be reversed i.e. the in-phase channel becomes the anti-phase channel and the anti-phase channel becomes 0 = Disabled 0 N E
the in-phase channel. The OFF situation is unchanged. 1= Enabled
0 to 3
0 = OFF
State The current state of the module’s outputs. 1 = Stationary 0 O B
2 = Lower
3 = Raise
(maintenance)
(readback)
A1.9.6 IQ4 Raise/Lower End Driver Modules
Module Identifier D
Size in brIQs 57
The Raise/Lower End Driver module is designed to drive a split-phase motor. It should be used for actuators with reversible action motors without any built-in positioning or where
there are no built-in limit switches, or clutches.
It provides either two digital outputs (L and A), or a single analogue output from a single analogue input S. Setting (A) to 0, selects a single analogue output. It also has the facility to
accept a feedback-input F.

IQ4 Modules
When the driver is operating with two digital outputs, (L) will be set to 1 for period if (S) is greater than the valve position, and (A) will be set to 1 for a period if (S) is less than the
the output value will be set to 10 V to cause the associated relay module to raise for a period. If (S) is less than the valve position the output value will be set to 4 V cause the associated
The module needs to know the position of the valve. This can be done either by estimating the position, or by using a feedback-input. If the feedback-input (F) is set to 0, the position
of the valve is estimated using the full-scale drive time and the sum of the amounts of time that the valve has been driven in each direction. (E.g. If the full-scale drive time is 10 s and
the valve has been driven open from the closed position for 8s and then driven closed for 3s making a total of 5s in the open direction (8-3). The estimated value position would be 50%
open because the value has been driven open for half the full-scale drive time). The valve position is verified when the value is required to be fully closed or fully open (0% or 100) by
additionally driving for the full-scale drive time in the required direction. This ensures that the valve has reached the end stop. If a feedback-input is used the position of the valve will
be known exactly. The module then determines if the valve is where it is expected to be, and if not the output signal is changed to correct the error.
The Raise/Lower End Driver module supports connection to an HOA module (XCITE/IO/8DO/HOA or XCITE/IO/4DO/HOA). This enables the drivers output to be set to ON (Hand)
or OFF or to use the calculated value (Auto) using a hardware switch connected to the modules output channel(s).

Auto Auto Auto
Auto Hand Hand
Auto OFF OFF
Hand Auto Hand
OFF Auto OFF
Hand Hand Hand
Hand OFF Hand
OFF Hand Hand
If an error condition (3) is received from the I/O module, the channel shall be assumed to be in Auto.

IQ4 Modules
A1.9.6.1 IQ4 Raise/Lower End Driver Module Parameters

Text
Comms
0 to 16
and no other active
input.
3 = HOA switch
Active priority level override. 10 O u
4 = Override
9 = IC comms write
10 = Strategy
16 = BACnet
Alarm Delay
maintenance alarm is generated. 0 to 178200 0 I m1(D)
(secs)(maintenance)
Note: Should normally be set to ‘0’ as the alarm is normally set by strategy which already includes a delay.
0 to 178200 0 I r1(D)
(readback) Note: Should normally be set to ‘0’ as it is normal practice to use a readback module to set the alarm state
which already includes a delay.
Alarm Group
(maintenance)
0 or 1
1 = Sent
0 or 1
1 = Sent
0 or 1
Alarm state
The state of the maintenance interval alarm condition. 0=No alarm 0 O m1(S)
(maintenance)
1=Alarm

IQ4 Modules
Text
Comms
0 or 1
0 = No Alarm
0 or 1
Clear Alarm
(maintenance)
0=Disabled
0 or 1
0=Disabled
0 to 178200 0 I r1(d)
(readback) Note: Should normally be set to ‘0’ as it is normal practice to use a readback module to set the alarm state
and this already includes a delay.
v3.50 or greater. The period (in seconds) for which the maintenance input must be cleared before the clear
Clear Alarm Delay
alarm is generated. 0 to 178200 0 I m1(d)
(secs)(maintenance)
Note: Should normally be set to ‘0’ as the alarm is normally set by strategy which already includes a delay.
The amount by which the driver value must change before a BACnet COV notification message is sent to + Full analogue
COV Increment 0 N C
those subscribers in the list of subscribers who have subscribed to this parameter. 0 = no notification
parameter’s value.
0 or 1
0=Disabled
0 or 1
0=Disabled
A positional feedback input to the Driver module. This enables the HVAC equipment item’s actual
Feedback Full analogue 0 I F
position to be fed back to the driver. If set to a specific value, it will be ignored.

IQ4 Modules
Text
Comms
0 to 30
The address of the physical I/O module that contains the input channel providing the module’s input - only
applies to IQ4E, set to ‘0’ for all other types of IQ4.
0, 1, 2, 3
3 = Error
0, 8, and 9
In Alarm 0 O !
9 = Readback Alarm
Channel 0=Disabled
0 or 1
0=Normal
0 or 1
1=Alarm
0 to 5
control)
1 = Overridden
2 = Disabled
Module Status The module's status. 3 = Hand (manually set 0 O _
on)
4 = Off (manually set
off)
control)

IQ4 Modules
Text
Comms
When enabled the module will drive the actuator closed for 1.5 times the full-scale drive time. This enables 0 or 1
Position Synchronisation the actual actuator position to be re-calibrated regularly to ensure correct control. Once the synchronisation 0 = Disabled 0 I Z
is complete the Driver module will return to the required control position. 1 = Enabled
0 or 1
0 = no override
switched on.
0 or 1
1=Alarm
When enabled the behaviour of the raise and lower channels are swapped enabling the drive direction to 0 or 1
Reverse Operation be reversed i.e. the in-phase channel becomes the anti-phase channel and the anti-phase channel becomes 0 = Disabled 0 N E
the in-phase channel. The OFF situation is unchanged. 1= Enabled
0 to 3
0 = OFF
2 = Lower
3 = Raise
(maintenance)
(readback)

IQ4 Modules
A1.9.7 IQ4 Time Proportional Driver Modules

Module Identifier D
Size in brIQs 53
The Time Proportional Driver module provides an output whose mark-space ratio is dependent on the input level. It has an analogue source S and provides a single digital output L with
an antiphase output A. The state of L is determined by the value of S, and the period time. If (S) is greater than 0, (L) will be set to 1 for a length of time. This length of time is calculated
as a percentage of the period time determined by the value of S. (A) will always be the opposite of (L).
The Time Proportional Driver module supports connection to an HOA module (XCITE/IO/8DO/HOA or XCITE/IO/4DO/HOA). This enables the driver’s output to be set to ON (Hand)

Auto Auto Auto
Auto Hand Hand
Auto OFF OFF
Hand Auto Hand
OFF Auto OFF
Hand Hand Hand
Hand OFF Hand
OFF Hand Hand

IQ4 Modules
A1.9.7.1 IQ4 Time Proportional Driver Module Parameters

Text
Comms
0 to 16
3 = HOA switch
The current priority level of the input to the module's algorithm. Normal strategy operation writes to override.
Active priority level 10 O u
priority level ‘10’. If a higher priority value comes in from BACnet, this controls the module. 4 = Override
9 = IC comms write
10 = Strategy
16 = BACnet
0 to 178200 0 I m1(D)
delay.
0 to 178200 0 I r1(D)
Alarm Group
(maintenance)
0 or 1
1 = Sent
0 or 1
1 = Sent
0 or 1
1=Alarm

IQ4 Modules
Text
Comms
0 or 1
0 = No Alarm
0 or 1
Clear Alarm
(maintenance)
0=Disabled
0 or 1
0=Disabled
0 to 178200 0 I r1(d)
0 to 178200 0 I m1(d)
delay.
COV Increment 0 N C
The current HVAC equipment item’s position as a percentage of it full range as understood by the
Drive Position Driver module. If there is no feedback (boundless) it is estimated, otherwise it will reflect the 0 to 100 0 O P
‘Feedback’ parameter’s value.
0 or 1
0=Disabled
0 or 1
0=Disabled

IQ4 Modules
Text
Comms
0 to 30
0, 1, 2, 3
3 = Error
0, 8, and 9
In Alarm 0 O !
9 = Readback Alarm
Channel 0=Disabled
0 or 1
0=Normal
0 or 1
1=Alarm
0 to 5
control)
1 = Overridden
2 = Disabled
on)
control)
The current number of times the driver has started. It can be used to provide an input to other modules
Number of Starts 0 to 109 0 Status N
by linking it to the required modules.

IQ4 Modules
Text
Comms
0 or 1
0 = no override
Period The amount of time (in seconds) being time proportioned. 0 to 32767 0 I P
The period (in seconds) after the IQ4 is powered up or performs a soft restart before the driver output
is switched on.
0 or 1
1=Alarm
0 to 3
0 = OFF
2 = Lower
3 = Raise
(maintenance)
(readback)
A1.9.8 IQ4 Time Proportional + O/R Driver Modules
Module Identifier D
Size in brIQs 54
The time proportional + override driver module is designed to operate a raise/lower relay module using an analogue output channel. Its output L can have one of 3 values 10 V, 7 V, or
4 V. The output (L) is set to 10 V when the override-input (O) is set to 1; otherwise the output is time-proportioned between 4 V (ON) and 7 V (OFF). It also has an antiphase output A,
which is not normally used, but is OFF when the value (L) is ON, and ON when the value of output (L) is OFF.

IQ4 Modules
The Time Proportional Driver module supports connection to an HOA module (XCITE/IO/8DO/HOA or XCITE/IO/4DO/HOA). This enables the driver’s output to be set to ON (Hand)

Auto Auto Auto
Auto Hand Hand
Auto OFF OFF
Hand Auto Hand
OFF Auto OFF
Hand Hand Hand
Hand OFF Hand
OFF Hand Hand
A1.9.8.1 IQ4 Time Proportional + O/R Driver Module Parameters
Text
Comms
0 to 16
9 = IC comms write
10 = Strategy
16 = BACnet
0 to 178200 0 I m1(D)
delay.

IQ4 Modules
Text
Comms
0 to 178200 0 I r1(D)
Alarm Group
(maintenance)
0 or 1
1 = Sent
0 or 1
1 = Sent
0 or 1
1=Alarm
0 or 1
0 = No Alarm
0 or 1
Clear Alarm (maintenance) Enables/disables reporting of the maintenance interval clear alarm. 1=Enabled 1 N m1(C)
0=Disabled
0 or 1
0=Disabled
0 to 178200 0 I r1(d)

IQ4 Modules
Text
Comms
0 to 178200 0 I m1(d)
delay.
COV Increment 0 N C
parameter’s value.
0 or 1
0=Disabled
0 or 1
0=Disabled
0 to 30
0, 1, 2, 3
3 = Error
0, 8, and 9
In Alarm 0 O !
9 = Readback Alarm
Channel 0=Disabled

IQ4 Modules
Text
Comms
0 or 1
0=Normal
0 or 1
1=Alarm
0 to 5
control)
1 = Overridden
2 = Disabled
on)
control)
The current number of times the driver has started. It can be used to provide an input to other modules
Number of Starts 0 to 109 0 N N
by linking it to the required modules.
0 or 1
Override Switches the module into override operation where it will drive the in-phase output to 10V. 1 = Override 0 I O
0 = No override
0 or 1
0 = no override
Period The amount of time (in seconds) being time proportioned. 0 to 32767 0 I P
switched on.
0 or 1
1=Alarm

IQ4 Modules
Text
Comms
0 to 3
0 = OFF
2 = Lower
3 = Raise
(maintenance)
(readback)

IQ4 Modules
A1.10 IQ4 Function Modules

Function modules allow mathematical calculations to be performed on several variables.
IQ4 ABS Function Modules
IQ4 Add Function Modules
IQ4 Adder/Scaler Function Modules
IQ4 Analogue Input Selector Function Modules
IQ4 Analogue to Digital Function Modules
IQ4 Average Function Modules
IQ4 Comparator Function Modules
IQ4 COV Function Modules
IQ4 Differencer Function Modules
IQ4 Divide Function Modules
IQ4 Enthalpy Function Modules
IQ4 Filter Function Modules
IQ4 Gate Function Modules
IQ4 Heat Meter Function Module
IQ4 Hysteresis Band Function Modules
IQ4 Hysteresis Limits Function Modules
IQ4 Integrator Function Modules
IQ4 Limit at Function Modules
IQ4 Limit to Function Modules
IQ4 Log Function Modules
IQ4 Lookup Function Modules
IQ4 Maximum Function Modules
IQ4 Minimum Function Modules
IQ4 Multiply Function Modules
IQ4 Power Function Modules
IQ4 Proximity Function Modules
IQ4 Psychrometrics Function Module
IQ4 Rescale from Function Modules
IQ4 Rescale to Function Modules
IQ4 Sample and Hold Function Modules
IQ4 Sliding Window Function Modules
IQ4 Square Root Function Modules
IQ4 TRIG Function Modules
IQ4 TRUNC Function Modules

IQ4 Modules
A1.10.1 IQ4 ABS Function Modules

Module Identifier F
Size in brIQs 12
Default Overview Parameters $, D
The ABS function module calculates its output (D) by converting the input (G) to a positive value. If (G) is already positive, no change is made.
The alarm byte associated with modules output is generated by OR'ing the alarm bits on the used inputs together. This information cannot be accessed directly, and an analogue node
module linked to the function module's output must be used. The function module's alarm bits will be replicated by the analogue node module's alarm bits.
A1.10.1.1 IQ4 ABS Function Module Parameters

Destination The value of the output. Full analogue 0 O D
Source G Specifies G in the calculation. Full analogue 0 I G
A1.10.2 IQ4 Add Function Modules
Module Identifier F
Size in brIQs 15
The Add Function module calculates its output (D) as the sum of four values (E), (F), (G), and (H). The module uses the following formula:
(D)= (E) + (F) + (G) + (H)
A1.10.2.1 IQ4 Add Function Module Parameters

Destination The output D of the module. Full analogue 0 O D

IQ4 Modules

Source E Specifies E in the calculation. Full analogue 0 I E
Source F Specifies F in the calculation. Full analogue 0 I F
Source H Specifies H in the calculation. Full analogue 0 I H
A1.10.3 IQ4 Adder/Scaler Function Modules
Module Identifier F
Size in brIQs 15
The Adder/Scaler Function module calculates the output (D) as the sum of two inputs (G and H) or the ratio of the two signals as per the formula:
(D) = ((E) x (G)) + ((F) x (H))
The alarm byte associated with modules output is generated by OR'ing the alarm bits on the used inputs together. controllers this information cannot be accessed directly, and an analogue
node module linked to the function module's output must be used. The function module's alarm bits will be replicated by the analogue node module's alarm bits.
A1.10.3.1 IQ4 Adder/Scaler Function Module Parameters

Destination The output D of the module. Full analogue 0 O D

IQ4 Modules
A1.10.4 IQ4 Analogue Input Selector Function Modules

Module Identifier F
Size in brIQs 14
Analogue Selector Function modules set their ‘Destination’ parameter to the value of one of up to eight analogue input parameters (‘Input a’, ‘Input b’, ‘Input c’, ‘Input d’, ‘Input e’,
‘Input f’, ‘Input g’, or ‘Input h’) depending on the ROUND of the value of the ‘Selector’ parameter minus the value of the ‘Offset’ parameter providing this value is 0, 1, 2, 3,4, 5, 6 or
7.
E.g. if ‘Selector’ parameter = ‘10.4’ and ‘Offset’ parameter = 5. This give a calculation of 10.4 - 5 = 5.4 which is rounded to ‘5 ‘
If the ROUND of the value of the ‘Selector’ parameter minus the value of the ‘Offset’ parameter is not 0, 1, 2, 3,4, 5, 6 or 7 the ‘Destination’ parameter is set to the value of the Default
Input’ parameter.
A1.10.4.1 IQ4 Analogue Selector Function Module Parameters
Text
Comms
Default Input The value used when the result of the calculation above is not 0, 1, 2, 3, 4, 5, 6 or 7. Full Analogue 0 I F
Destination D The module's output. Full Analogue 0 O D
Input a The value used when the result of the calculation above is ‘0’ Full Analogue 0 I a
Input b The value used when the result of the calculation above is ‘1’ Full Analogue 0 I b
Input c The value used when the result of the calculation above is ‘2’ Full Analogue 0 I c
Input d The value used when the result of the calculation above is ‘3’ Full Analogue 0 I d
Input e The value used when the result of the calculation above is ‘4’ Full Analogue 0 I e
Input f The value used when the result of the calculation above is ‘5’ Full Analogue 0 I f
Input g The value used when the result of the calculation above is ‘6’ Full Analogue 0 I g
Input h The value used when the result of the calculation above is ‘7’ Full Analogue 0 I h
The value subtracted form the value of the ‘Selector’ parameter. It allows support for base values of 0 and 1. It also supports
Offset Full Analogue 1 I O
the ability to cascade selector modules’. The default of 1 allows support for operation with BACnet multi-state objects.
Selector Determines which of the 8 analogue inputs is used for the ‘Destination’ parameter’s value. Full Analogue 0 I S

IQ4 Modules
A1.10.5 IQ4 Analogue to Digital Function Modules

Module Identifier F
Size in brIQs 119
The Analogue to Digital function module calculates its output by converting the value of its analogue input (G) to 8 digital outputs (a, b, c, d, e, f, g, and h).
From v4.20 firmware or greater the way in which the binary value is calculated can be determined using the ‘Mode’ parameter which can be set to one of four mode:
Binary
Binary + Overflow
Bit set
Cascade
Previous versions of firmware only support Binary mode.
Binary
Binary mode enables the conversion of 8 bit numbers (single byte).
Binary + Overflow
Binary + Overflow mode enables the conversion of multi-byte values by chaining 8 bit conversions The output (D) is calculated as the binary representation of G as 8 digital outputs in
the same way as for binary mode with the addition of an overflow output (O) that can be connected to the ‘Source’ parameter (G) of another Type 18 (Analogue to Digital Converter)
Function module operating in Binary + Overflow mode.
Bit Set
Bit set mode sets one output bit based on the value of the 'Source G' parameter. E.g. if the input is >=4 and <5 then bit 3 d) is set. All other output bits are cleared.
If the value of the 'Source G' parameter in the range 1 to 8 the output bits are set as below:
Bit
h 1
g 1
f 1
e 1
d 1
c 1
b 1
a 1
G 1 2 3 4 5 6 7 8
If the value of the ‘Source G’ parameter out of the range 1 to 8 all the output bits are set. to 0.

IQ4 Modules
Cascade
Cascade mode sets the output bits as the input value increases.
If the value of the ‘Source G’ parameter in the range 1 to 8 the output bits are set. as below
Bit
h 1
g 1 1
f 1 1 1
e 1 1 1 1
d 1 1 1 1 1
c 1 1 1 1 1 1
b 1 1 1 1 1 1 1
a 1 1 1 1 1 1 1 1
G 1 2 3 4 5 6 7 8
Alarm Byte
A1.10.5.1 IQ4 Analogue to Digital Function Module Parameters

Bit 1 Bit 1 of the output byte. 0 or 1 0 O a
Bit 2 Bit 2 of the output byte. 0 or 1 0 O b
Bit 3 Bit 3 of the output byte. 0 or 1 0 O c
Bit 4 Bit 4 of the output byte. 0 or 1 0 O d
Bit 5 Bit 5 of the output byte. 0 or 1 0 O e
Bit 6 Bit 6 of the output byte. 0 or 1 0 O f
Bit 7 Bit 7 of the output byte. 0 or 1 0 O g
Bit 8 Bit 8 of the output byte. 0 or 1 0 O h

IQ4 Modules

0, 1, 2, 3
0 = Binary
Mode v4.20 or greater. The mode in which the module is operating. 1 = Binary + Overflow 1 N M
2 = Bit set
3 = Cascade
4.20 or greater. The value left over after the conversion, can be passed to another module, calculated as below:
Binary + Overflow
O = TRUNC (G DIV 256)
Overflow BitSet and Cascade modes Full analogue 0 O O
O = min (0,TRUNC(G – 8)) : i.e. overflow cannot go negative.
Binary
O = 0.0
Source G Specifies the analogue value that is to be converted. Full analogue 0 I G
A1.10.6 IQ4 Average Function Modules
Module Identifier F
Size in brIQs 119
The Average function module calculates its output (D) as the average value of two, three, or four inputs (E), (F), (G), and (H).
If the module's 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). However, this information cannot be accessed directly, and an analogue node module linked
to the function module's output must be used. The function module's alarm bits will be replicated by the analogue node module's alarm bits.
A1.10.6.1 IQ4 Average Function Module Parameters


IQ4 Modules

A1.10.7 IQ4 Comparator Function Modules
Module Identifier F
Size in brIQs 13
The Comparator Function module calculates its output (D) as 0 or 1 by comparing two inputs (E and F). When (F)>(E), (D)=1, and when (F)=<(E), (D)=0. All alarm bits are ignored.
A1.10.7.1 IQ4 Comparator Function Module Parameters

Destination The value of the output. 0 or 1 0 O D
A1.10.8 IQ4 COV Function Modules
Module Identifier F
Size in brIQs 14
COV Function modules detect changes to an analogue value. They pulse the ‘Destination D’ parameter when the value of the ‘Source’ parameter differs from the ‘Last Value’ parameter
by more than the 'Significant change' parameter. The ‘Last Value’ parameter is set when a pulse is generated. The length of the pulse can be specified using the ‘Pulse Duration’
parameter.

IQ4 Modules
A1.10.8.1 IQ4 COV Function Module Parameters

Text
Comms
Destination D The module’s output. 0 or 1 0 O D
0 or 1
1=
Invert Output When set to ‘1’ then the normal status of the ‘Destination D’ parameter is ‘1’ and the output will pulse to ‘0’. 0 I I
Inverted
2 = Normal
Full
Last Value The value of the ‘Source’ parameter when the pulse was last generated. Set to the ‘Source’ parameter on power up 0 N L
analogue
The duration of the output pulse, in seconds. If this is set to ‘0’ then the pulse will last for one complete cycle of the sequence Full
Pulse Duration 0 N P
table and in the case of event based execution the OFF event will follow the ON event directly. analogue
Significant +ve
The amount the value must increase or decrease before the output is pulsed. 0 N C
change Analogue
Full
Source The value that is to be monitored for changes. 0 I S
analogue
A1.10.9 IQ4 Differencer Function Modules
Module Identifier F
Size in brIQs 14
Differencer Function modules calculate the difference between the value of the ‘Source Value at Last Reset’ parameter and the value of the ‘Source’ parameter e.g. to calculate an
incremental consumption value from a cumulative consumption value. Setting the ‘Reset’ parameter to ‘1’ sets the ‘Source Value at Last Reset’ parameter to the value of the ‘Source’
parameter effectively resetting the calculation.

IQ4 Modules
A1.10.9.1 IQ4 Differencer Function Module Parameters

Text
Comms
Double
Difference The difference between the value of the ‘Source Value at Last Reset’ parameter and the value of the ‘Source’ parameter. 0 O D
Precision
Double
Last Source Value The last value of the ‘Source’ parameter used in the calculation. It allows compensation following input changes 0 N Z
Precision
When set to ‘1’ sets the value of the ‘Source Value at Last Reset’ parameter to the value of the ‘Source’ parameter. Should
Reset 0 or 1 0 I F
be linked to a parameter that changes between ‘0’ and ‘1’ a at a regular interval.
Source Value at Double
The value of the ‘Source’ parameter when the ‘Reset’ parameter was last set to ‘1’. 0 I A
Last Reset Precision
Double
Source Value to be differenced. 0 I G
Precision
A1.10.10 IQ4 Divide Function Modules
Module Identifier F
Size in brIQs 14
The Divide Function module calculates its output (D) by dividing the input (G) by a value (E) and multiplying the result by another value (F). The module uses the following formula:
(D)= ((G)/(E))(F)
A1.10.10.1 IQ4 Divide Function Module Parameters

IQ4 Modules

Source E Specifies E in the calculation, divisor. Full analogue 0 I E
Source F Specifies F in the calculation, input. Full analogue 0 I F
Source G Specifies G in the calculation, input. Full analogue0 0 I G
A1.10.11 IQ4 Enthalpy Function Modules
Module Identifier F
Size in brIQs 13
The Enthalpy Function module calculates its output (D) as the enthalpy value in Kjoules/Kg of two inputs (E and F). (E) must be relative humidity and (F) the temperature in DegC. The
module uses the following formula:
(D)=(E)x10(0.0275(F)-1)+(F)
A1.10.11.1 IQ4 Enthalpy Function Module Parameters

Source E Specifies E (%RH) in the calculation. Full analogue 0 I E
Source F Specifies F (temperature in DegC) in the calculation. Full analogue 0 I F

IQ4 Modules
A1.10.12 IQ4 Filter Function Modules

Module Identifier F
Size in brIQs 13
The Filter Function module applies an exponential filter, filter factor, (E) to an input signal (G) to calculate the output (D). This is useful where electrical noise levels are high, and an
unfiltered signal would affect the operation of the system.
The module uses the following formula:
(D)= (E)x(D)+(1-(E))(G)
A1.10.12.1 IQ4 Filter Function Module Parameters
Text
Comms
Full
Destination The output (D) of the module. 0 O D
analogue
Specifies (E), filter factor, in the calculation. It is normally in the range 0 to 1 where 0 gives no filter action, and 1 gives an infinite Full
Source E 0 I E
filter (i.e. no change in output). analogue
Full
Source G Specifies (G) in the calculation. If it is not to be used in the calculation, it should be set to a constant value of 1. 0 I G
analogue

IQ4 Modules
A1.10.13 IQ4 Gate Function Modules

Module Identifier F
Size in brIQs 14
The Gate Function module selects its output (D) from one of two values ((E) or (F)) depending on the state of a digital control bit (B). When (B)=1, (D)=(F), and when (B)=0, (D)=(E).
The alarm bits from the source in use are transferred to the output. This information cannot be accessed directly, and an analogue node module linked to the function module's output
must be used. The function module's alarm bits will be replicated by the analogue node module's alarm bits.
A1.10.13.1 IQ4 Gate Function Module Parameters

Source B State of control bit. Can be connected to a digital output or set to a specific value. 0 or 1 0 I B
Source E Specifies (E) in the calculation. Full analogue 0 I E
Source F Specifies (F) in the calculation. Full analogue 0 I F
A1.10.14 IQ4 Heat Meter Function Module
Module Identifier F
Size in brIQs 16
IQ4 v3.0 or greater
The Heat Meter Function module enables the power used by the source to be calculated (e.g. kW. The module uses the following formula:
IF
(F)>=(E) (D)=0
ELSE
(D) = ((E)-(F))*(G)*(H)*(I)
G, H, and I are optional and if set to 'null' they are not used in the calculation.
The module can be disabled using the module state parameter. When the module is disabled its output value is not updated, and is not passed on to any linked modules.

IQ4 Modules
A1.10.14.1 IQ4 Heat Meter Function Module Parameters


Input I The value of input I. Full analogue 0 I I
Upper Temp E Specifies E (upper temperature) in the calculation. Full analogue 0 I E
Lower Temp F Specifies F in the calculation. Full analogue 0 I F
Examples
The module can be used in several different applications e.g.
Heat meter where flow and temperatures are available
For a heat meter where the flow and temperature are available the power is calculated as per the formula below:
Power = Temperature Different Supply and Return * Specific Heat Capacity of Medium * Mass Flow
If the heat meter was for heating plant the module would be used as follows:
Power kW (D) = (Supply Temp (E) – Return Temp (F)) * Flow dm3/s (G) * Mass of Flow kg/dm3(H) * Specific Heat Capacity kJ/kgK (I)
If the heat meter was for cooling plant the module would be used as follows:
Power kW (D) = (Return Temp (E) – Supply Temp (F)) * Flow dm3/s (G) * Density kg/dm3(H) * Specific Heat Capacity kJ/kgK (I)
Heat exchanger power estimation:
If the heat exchanger is for heating the power is calculated as per the following formula:
Power = (Heating medium temperature – Air on temperature) * Coil duty * Valve position / 100
The module could therefore be used as follows:
Power kW (D) = (Water Supply Temp (E) – Air On Temp (F)) * Coil Duty kW/degK (G) * Valve Position %(0-100)(H) * 0.01 (I)
If the heat exchanger is for cooling the power is calculated as per the following formula:
Power = (Air on temperature – Heating medium temperature) * Coil duty * Valve position / 100
Power kW (D) = (Air On Temp (E) – Water Supply Temp (F)) * Coil Duty kW/degK (G) * Valve Position %(0-100)(H) * 0.01 (constant)(I)

IQ4 Modules
A1.10.15 IQ4 Hysteresis Band Function Modules
Module Identifier F
Size in brIQs 14
The Hysteresis Band function module sets digital output state (D) to 1 if (G) rises above the value of (E)+(F/2) and then sets (D) to 0 if (G) falls below (E)-(F/2). This enables the state
of a digital node from an analogue input level. All alarm bits are ignored.
A1.10.15.1 IQ4 Hysteresis Band Function Module Parameters

Source E Specifies E (level) in the calculation. Full analogue 0 I E
Source F Specifies F (band) in the calculation. Full analogue 0 I F
A1.10.16 IQ4 Hysteresis Limits Function Modules
Module Identifier F
Size in brIQs 14
The Hysteresis Limits Function module sets digital output state (D) to 1 if (G) rises above (F) and then sets the output (D) to 0 if (G) falls below (E).

IQ4 Modules
A1.10.16.1 IQ4 Hysteresis Limits Function Module Parameters


Source E Specifies E (low limit) in the calculation. Full analogue 0 I E
Source F Specifies (F) in the calculation, high limit. Full analogue 0 I F
Source G Specifies F (high limit) in the calculation. Full analogue 0 I G
A1.10.17 IQ4 Integrator Function Modules
Module Identifier F
Size in brIQs 14
IQ4 v3.0 or greater
Used to convert power (kW) to energy consumption (kWh).
IF
(H)= 1 THEN (D)=0
ELSE
(D) = (D) + Delta Total
Delta Total =(G) * t/(F) where t is the between values in seconds.
The Total (D) can be reset to '0' by setting the Reset parameter (H) to '1'. If a plot module is logging the module's output, it should be triggered by the same pulse as the modules reset
H. Increases in the output that are smaller than about 1 part in 107 may not be shown but will still be accumulated accurately.
Note: If the module is disabled when the module is re-enabled it will start integrating from the latest output value i.e. the value when the module was disabled. If while the module is
disabled, the user changes the output value it will use that value when it is enabled.
A1.10.17.1 IQ4 Integrator Function Module Parameters

IQ4 Modules

Source F Specifies F (scale factor) in the calculation, the scale factor used to scale the total value before it is output. Full analogue 0 I F
Source G Specifies G (value which is to be accumulated) in the calculation. Full analogue 0 I G
0 or 1
Source H Resets the output D to ‘0’. 0 I H
1 = Reset
Examples
Power
To integrate power in kW to energy in kWh
Source (G) = kW, Scale factor (F) = 3600, Total (D)= kWh
To integrate power in kW to energy in MWh
Source (G) = kW, Scale factor (F) = 3600000, Total (D)= MWh
Flow
To integrate flow in litres per second to volume in litres
Source (G) = litre/s, Scale factor (F) = 1, Total (D) = litres
A1.10.18 IQ4 Limit at Function Modules
Module Identifier F
Size in brIQs 14
The Limit at Function module that takes an input (G) and limits the output (D) to a range between a lower limit (F) and an upper limit (E).
A1.10.18.1 IQ4 Limit at Function Module Parameters

IQ4 Modules

Source E Specifies E (upper limit) in the calculation. Full analogue 0 I E
Source F Specifies F (lower limit) in the calculation. Full analogue 0 I F
A1.10.19 IQ4 Limit to Function Modules
Module Identifier F
Size in brIQs 14
The Limit to Function module takes an input (G) and limits the output (D) to a range of 0 to 100% depending on a lower limit (F) and an upper limit (E). When (G)>(E), (D)=100, when
(G)<(F), (D)=0, and when (G) is between (E) and (F), output (D) is equal to the input (G).
A1.10.19.1 IQ4 Limit to Function Module Parameters

Source E Specifies E (upper limit) in the calculation. Full analogue 0 I E
Source F Specifies F (lower limit) in the calculation. Full analogue 0 I F

IQ4 Modules
A1.10.20 IQ4 Log Function Modules

Module Identifier F
Size in brIQs 13
The Log Function module calculates its output (D) as the logarithm of the input (G) multiplied by a value (E). The module uses the formula:
(D)=(E)log(G) (log to base 10)
A1.10.20.1 IQ4 Log Function Module Parameters

Source E Specifies E (multiplier) in the calculation. Full analogue 0 I E
A1.10.21 IQ4 Lookup Function Modules
Module Identifier F
Size in brIQs 13
The Lookup Function module scales the input (G) using the characteristics defined in the specified sensor type module.
A1.10.21.1 IQ4 Lookup Function Module Parameters

IQ4 Modules

Scaling Type Sensor Type module the module is using for reference. 0 to 99 0 N S
A1.10.22 IQ4 Maximum Function Modules
Module Identifier F
Size in brIQs 15
The Maximum Function module calculates its output (D) as the maximum value from two, three, or four inputs (E), (F), (G), and (H).
function of any of the inputs (i.e. any out-of-limits, read, high or low alarms are passed on). The function module's alarm bits will be replicated by the analogue node module's alarm
bits.
A1.10.22.1 IQ4 Maximum Function Module Parameters


IQ4 Modules
A1.10.23 IQ4 Minimum Function Modules

Module Identifier F
Size in brIQs 15
The Minimum Function module calculates its output (D) as the minimum value of two, three, or four inputs (E), (F), (G), and (H)
function of any of the inputs (i.e. any out-of-limits, read, high or low alarms are passed on). The function module's alarm bits will be replicated by the analogue node module's alarm
bits.
A1.10.23.1 IQ4 Minimum Function Module Parameters

A1.10.24 IQ4 Multiply Function Modules
Module Identifier F
Size in brIQs 14
The Multiply Function module calculates its output (D) as the input (G) multiplied by two values ((E) and (F)). The module uses the following formula:
(D)= (G)x(E)x(F)

IQ4 Modules
A1.10.24.1 IQ4 Multiply Function Module Parameters


A1.10.25 IQ4 Power Function Modules
Module Identifier F
Size in brIQs 13
The Power Function module calculates its output (D) as its input (E) to the power of its input (F). The module uses the following formula:
(D)=(E)(F)
A1.10.25.1 IQ4 Power Function Module Parameters

Source E Specifies E in the calculation, input. Full analogue 0 I E
Source F Specifies F in the calculation, index. Full analogue 0 I F

IQ4 Modules
A1.10.26 IQ4 Proximity Function Modules

Module Identifier F
Size in brIQs 14
The Proximity Function module sets its output (D) to 1 if (G) >= (E)-(F) or <= (E)+(F). It is used to see if (E) and (G) are approximately equal.
A1.10.26.1 IQ4 Proximity Function Module Parameters

Source F Specifies F (proximity) in the calculation. Full analogue 0 I F
Source G Specifies G in the calculation, input. Full analogue 0 I G
A1.10.27 IQ4 Psychrometrics Function Module
Module Identifier F
Size in brIQs 13
IQ4v3.30 or greater.
Psychrometrics Function modules calculate the saturated vapour pressure, vapour pressure, enthalpy, moisture content, and dew point based on the relative humidity, temperature, and
height above sea level.
A1.10.27.1 IQ4 Psychrometrics Function Module Parameters

Dew point The dew point (DegC or DegF) calculated by the module Full Analogue 0 O D

IQ4 Modules

Enthalpy The Enthalpy (KJ/Kg or BTU/lb) calculated by the module. Full Analogue 0 O E
Height The height above sea level (meters or feet) used by the module in its calculations. Full Analogue 0 I H
Moisture content The moisture content (g/kg or lb/1000lb) calculated by the module. Full Analogue 0 O M
Relative Humidity The relative humidity (% RH) used by the module in its calculations. Full Analogue 0 I R
Saturated Vapour Pressure The saturated vapour pressure (kPa or psi) calculated by the module. Full Analogue 0 O S
Temperature The temperature (DegC or DegF) used by the module in its calculations. Full Analogue 0 I T
0 or 1
Units The type of units (SI or imperial) used by the module in its calculations and outputs. 0 = SI 0 N U
1 = Imperial
Vapour Pressure The vapour pressure (kPa or psi) calculated by the module. Full Analogue 0 O P
A1.10.28 IQ4 Rescale from Function Modules
Module Identifier F
Size in brIQs 14
The Rescale From Function module calculates its output (D) by rescaling input (G) that can be between 0 and 100 to a range between a lower limit (E), and an upper limit (F). The
(D)= E+(((G)-(E))/((F)-(E))
Note: If the value of (G) is outside the range 0 to 100, it will be limited at these values.
A1.10.28.1 IQ4 Rescale from Function Module Parameters

Destination The output (D) of the module. Full analogue 0 O D
Source E Specifies E (lower limit) in the calculation. Full analogue 0 I E
Source F Specifies F (upper limit) in the calculation. Full analogue 0 I F

IQ4 Modules

A1.10.29 IQ4 Rescale to Function Modules
Module Identifier F
Size in brIQs 14
The Rescale to Function module rescales an input (G) that can vary between a lower limit (E), and an upper limit (F) to the output (D), which is limited to a percentage value between 0
and 100. The module uses the following formula:
(D)= 100((G)-(E))/((F)-(E)
A1.10.29.1 IQ4 Rescale to Function Module Parameters

Source E Specifies E (lower limit) in the calculation. Full analogue 0 I E
Source F Specifies F (upper limit) in the calculation. Full analogue 0 I F
A1.10.30 IQ4 Sample and Hold Function Modules
Module Identifier F
Size in brIQs 14
Sample and Hold Function modules allow an analogue value to be retained. They set the 'Destination D' parameter to the value of the 'Source' parameter when the 'Enable' parameter is
set to '1'.

IQ4 Modules
The 'Destination' parameter will remain at that value until the 'Enable' parameter is set to '1' again. The 'Destination D' parameter can be set to the value of the 'Default Value' parameter
by setting the 'Reset' parameter to '1'.
The module's status is retained when the IQ4 is powered down and when the IQ4 restarts it the module will adopt the status at power down.
A1.10.30.1 IQ4 Sample and Hold Function Module Parameters

Default Value The value to be used when the 'Reset' parameter is set to '1'. Full Analogue 0 N F
Destination D The output (D) of the module. Full Analogue 0 O D
Enable When set to ‘1’ sets the module’s output ‘D’ to the value of the ‘Source’ parameter ‘S’. 0 or 1 1 I E
0 or 1
Reset When set to ‘1’ sets the module’s output ‘D’ to the value specified by the ‘Default Value’ parameter. 0= no change 0 I R
1 = Reset
Source The value that is to be processed. Full Analogue 0 I S
A1.10.31 IQ4 Square Root Function Modules
Module Identifier F
Size in brIQs 13
The Square Root Function module calculates its output (D) as the square root of the input (G) multiplied by a value (E). The module uses the following formula:
(D)=(E)(G)
A1.10.31.1 IQ4 Square Root Function Module Parameters


IQ4 Modules

A1.10.32 IQ4 Sliding Window Function Modules
Module Identifier F
Size in brIQs 14
Sliding Window Function modules allow either Min, Max, Sum, Average, or Standard Deviation calculations to be applied to a specified range of data in a Plot module.
A1.10.32.1 IQ4 Sliding Window Function Module Parameters
Text
Comms
Data Ready Set to ‘0’ if there fewer samples than required stored in the Plot module, otherwise set to ‘1’. 0 or 1 0 O R
Destination D The output (D) of the module. Full Analogue 0 O D
0, 1, 2, 3, 4
0 – Min,
1 - Max
Function The type of calculation that is to be performed. 2 N F
2 – Sum
3 – Average
4 - SD
0 or 1
Hold If ‘1’ the value of the Destination parameter will be retained. 1 = Hold 0 I H
0 = No hold
Last Sample The index of the last sample to be used in the Plot module buffer – working backwards in time. 1 is the last (most recent) +Full
1 I L
Index in the buffer. Analogue
Number of The number of values from the Plot nodule that are to be used. If this is greater than the number available, then those
0 to 1000 10 I N
Samples samples available are used.
Source The Plot module containing the data to which the calculation is to be applied. Full Analogue 0 I S

IQ4 Modules
A1.10.33 IQ4 TRIG Function Modules

Module Identifier F
Size in brIQs 14
The TRIG Function module calculates the sin, cosine, or tangent of the input (G) in degrees, or radians.
A1.10.33.1 IQ4 TRIG Function Module Parameters

0 or 1
Angle Type The units of angle used. 0 = Degrees 0 N R
1 = Radians
0 to 2
0 = sine
Sub Type The trigonometric function used by the module. 0 N S
1 = Cosine
2 = Tangent
A1.10.34 IQ4 TRUNC Function Modules
Module Identifier F
Size in brIQs 14
The TRUNC Function module takes the value of its input (G), removes any digits after the decimal point and writes it to its output (D), e.g. 23.7654 would become 23.

IQ4 Modules
A1.10.34.1 IQ4 TRUNC Function Module Parameters



IQ4 Modules
A1.11 IQ4 IC Comms Modules

IC Comms modules provide the facility for communication between IQ controllers, where two or more networked controllers are in use. There are several different types to cope with
differing requirements.
IQ4 Average IC Comms Modules
IQ4 Data From Analogue IC Comms Modules
IQ4 Data From Bit IC Comms Modules
IQ4 Data From Byte IC Comms Modules
IQ4 Data To IC Comms Modules
IQ4 Global To IC Comms Modules
IQ4 Maximum IC Comms Modules
IQ4 Minimum IC Comms Modules
IQ4 Sum IC Comms Modules
A1.11.1 IQ4 Average IC Comms Modules
Module Identifier N
Size in brIQs 17
The Average ic comms module requests the value of an analogue node (remote node (R)) from all controllers that match the search criteria set up in the module, calculates the average
value, and places it in the destination.
A1.11.1.1 IQ4 Average IC Comms Module Parameters
The modules include the following parameters that are common to most modules: 'Disable Module' 'Label', 'Page', 'X co-ordinate' and 'Y co-ordinate' - see Common IQ4 Module
Parameters, plus the following:
0 to 7
0=comms disabled
1=identifier
2=F attribute
Attributes The attribute that must match in all devices for them to respond to the message. 3=G attribute 0 N B
4=H attribute
5=I attribute
6=J attribute
7=K attribute
0 or 1
Failed Bit Indicates whether the last message sent by the module was successful. 0 = OK 0 O F
1 = Failed

IQ4 Modules

Local Module The output of the module. Full analogue 0 O L
0 or 1
Module State Specifies whether the module is enabled, or disabled. 1=Disabled 0 I ~
0=Enabled
0 to 119 excluding addresses 2, 3, and 10.
Remote Lan Specifies the LAN of the devices to which the message is to be sent. 0 I N
0 = local LAN.
Remote Module Specifies the analogue parameter that is to be read. Any analogue module parameter. Blank N R
Retransmission Interval The length of time (in minutes) between a message being sent and then repeated. 0 to 1440 5 N I
Time into Interval Length of time (in minutes) since the start of the retransmission interval. 0 to 3276 0 N T
A1.11.2 IQ4 Data From Analogue IC Comms Modules
Module Identifier N
Size in brIQs 17
Default Overview Parameters $, S
The data from analogue ic comms module obtains the value of an analogue value (remote analogue (R)) in another controller and makes it available as an output (L).
Additional functionality for IQ4 or greater
When using BACnet protocol and the 'COV mode' parameter is enabled the module can receive unconfirmed COV messages (the unconfirmed COV service) from another BACnet
device. The 'Remote Address' and 'Remote Lan' specify the NTD module linked to the BACnet device sending the COV messages, and the 'Remote Module' parameter specifies the
actual value sending the COV messages. The modules failed bit is set to TRUE on power up and will remain TRUE until a matching unconfirmed COV message is received, after which
it becomes FALSE and will remain FALSE forever (or until the controller is powered up again). This can be used in strategy to gate through some default value into a strategy until an
unconfirmed COV message is received. The following data types are supported from the BACnet source: UINT, BOOL, BINARYPV, ENUM, INT and REAL.
A1.11.2.1 IQ4 Data From Analogue IC Comms Module Parameters
Text
Comms
0 or 1
IQ4 v3.2 or greater. Only available when the 'Protocol' parameter is set to 'BACnet'. It specifies
COV Mode 1=Enabled 0 N V
whether the module listens for unconfirmed COV messages from the specified BACnet device.
0=Disabled

IQ4 Modules
Text
Comms
0 or 1
Failed Bit Indicates whether or the last messages sent by the module was successful. 0 = OK 0 O F
1 = Failed
Local Module The value received from the remote controller. Full analogue 0 O L
0 or 1
0=Enabled
IQ4/BACnet. Specifies the protocol used to send the message. If set to Trend the message is sent 0 or 1.
Protocol to devices on the Trend network. If set to BACnet the message is sent to devices on the BACnet 0 =Trend 0 N -
network. 1 = BACnet.
The address of the remote controller. If BACnet has been selected as a protocol this must be the 0 to 119 excluding addresses 2, 3, and
Remote Address 0 I A
address of the NTD linked to the BACnet device that contains the required value. 10. 0 disables communications
The LAN of the device to which the message is to be sent. If BACnet has been selected as a 0 to 119 excluding addresses 2, 3, and
Remote Lan protocol this must be the LAN number of the NTD linked to the BACnet device that contains the 10. 0 I N
required value. 0 = local LAN.
Remote Module The analogue parameter the IC Comms message will access. Any analogue module parameter. Blank N R
Retransmission
The length of time (in minutes) between a message being sent and then repeated. 0 to 1440 5 N I
Interval
A1.11.3 IQ4 Data From Bit IC Comms Modules
Module Identifier N
Size in brIQs 17
The Data From Bit ic comms module obtains the value of a bit (remote bit (R)) from another controller, and makes it available as an output (L).
Additional functionality for IQ4 or greater
When using BACnet protocol and the 'COV mode' parameter is enabled the module can receive unconfirmed COV messages (the unconfirmed COV service) from another BACnet
device. The 'Remote Address' and 'Remote Lan' specify the NTD module linked to the BACnet device sending the COV messages, and the 'Remote Module' parameter specifies the
actual value sending the COV messages. The modules failed bit is set to TRUE on power up and will remain TRUE until a matching unconfirmed COV message is received, after which
it becomes FALSE and will remain FALSE forever (or until the controller is powered up again). This can be used in strategy to gate through some default value into a strategy until an
unconfirmed COV message is received. The following data types are supported from the BACnet source: UINT, BOOL, BINARYPV, ENUM, INT and REAL.

IQ4 Modules
Any numeric value greater than 0.5 equates to TRUE, other values to FALSE.
A1.11.3.1 Data From Bit IC Comms Module Parameters
Text
Comms
0 or 1
IQ4 v3.2 or greater. Only available when the 'Protocol' parameter is set to 'BACnet'. It specifies
COV Mode 1=Enabled 0 N V
whether the module listens for unconfirmed COV messages from the specified BACnet device.
0=Disabled
0 or 1
1 = Failed
Local Module The value received from the remote controller. 0 or 1 0 O L
0 or 1
0=Enabled
Protocol to devices on the Trend network. If set to BACnet the message is sent to devices on the BACnet 0 =Trend 0 N -
address of the NTD linked to the BACnet device that contains the required value. 10. 0 disables communications
The LAN of the device to which the message is to be sent. If BACnet has been selected as a 0 to 119 excluding addresses 2, 3, and
Remote LAN protocol this must be the LAN number of the NTD linked to the BACnet device that contains the 10. 0 I N
required value. 0 = local LAN.
Remote Module The bit the IC Comms message will access. Any analogue module parameter. Blank N R
Retransmission
Interval

IQ4 Modules
A1.11.4 IQ4 Data From Byte IC Comms Modules

Module Identifier N
Size in brIQs 17
The Data From Byte ic comms module obtains the value of a byte (remote byte (R)) from another controller, and makes it available as an output (L).
A1.11.4.1 IQ4 Data From Byte IC Comms Module Parameters
Text
Comms
0 or 1
Indicates whether or the last messages sent by the module was
Failed Bit 0 = OK 0 O F
successful.
1 = Failed
Local Module The value received from the remote controller. 1020to +1020 0 O L
0 or 1
0=Enabled
0 to 119 excluding addresses 2, 3, and 10. 0 disables
Remote Address The address of the remote controller. 0 I A
communications
Remote LAN The LAN of the device to which the message is to be sent. 0 I N
0 = local LAN.
Remote Module The bit the IC Comms message will access. Any digital byte module parameter. Blank N R
Retransmission The length of time (in minutes) between a message being sent and then
1 to 1440 5 N I
Interval repeated.
Length of time (in minutes) since the start of the retransmission
Time into Interval 0 to 3276 0 N T
interval.

IQ4 Modules
A1.11.5 IQ4 Data To IC Comms Modules

Module Identifier N
Size in brIQs 19
The Data To ic comms module sends the specified value to a node (remote node) in another controller (remote controller).
A1.11.5.1 IQ4 Data To IC Comms Module Parameters
Text
Comms
0 or 1
1 = Failed
Any valid Trend module parameter L
Local module The value that is sent. It can be an analogue value, or digital byte, or digital bit value. Blank I
code.
0 or 1
0=Enabled
Protocol to devices on the Trend network. If set to BACnet the message is sent to devices on the BACnet 0 =Trend 0 N
address of a NTD. 10. 0 disables communications
0 to 119 excluding addresses 2, 3, and
Specifies the LAN of the devices to which the message is to be sent. If BACnet has been selected
Remote Lan 10. 0 I N
as a protocol this must be the LAN of an NTD.
0 = local LAN.
Specifies where the value is to be written. If Label Matching is selected the remote node is selected
Any analogue, digital byte, or digital bit
Remote Module by a match with the label of the module’s source (L). Blank N R
module parameter.
Note: Label matching is not available if 'Protocol' is set to 'BACnet'.
Retransmission
Interval
Significant The amount the value of the source address can change before a message is sent. If set to '0' the
0 to 6500 1 N S
Change messages is only sent at the retransmission interval.

IQ4 Modules
Text
Comms
Write Priority IQ4/BACnet. The write priority used to write the value to the BACnet device. 0 to 16 9 N w
A1.11.6 IQ4 Global To IC Comms Modules
Module Identifier N
Size in brIQs 19
The Global to ic comms module sends a specified value and places it in a specified location in all controllers that match the search criteria set up in the module.
A1.11.6.1 IQ4 Global To IC Comms Module Parameters
Text
Comms
0 to 7
0=comms disabled
1=identifier
2=F attribute
4=H attribute
5=I attribute
6=J attribute
7=K attribute
0 or 1
1 = Failed
Local module The value that is sent. It can be an analogue value, or digital byte, or digital bit value. 1020to +1020/0 or 1 0 I L
0 or 1
Module State Specifies whether the module is enabled, or disabled 1=Disabled 0 I ~
0=Enabled

IQ4 Modules
Text
Comms
0 or 1.
IQ4/BACnet. Specifies the protocol used to send the message. If set to Trend the message is sent to
Protocol 0 =Trend 0 N
devices on the Trend network. If set to BACnet the message is sent to devices on the BACnet network.
1 = BACnet.
0 to 119, 128 excluding
Specifies the LAN of the devices to which the message is to be sent. If BACnet has been selected as a addresses 2, 3, and 10.
Remote Lan 0 I N
protocol this must be the LAN of an NTD. 0 = local LAN.
128 = all LANs
Specifies where the value is to be written. If Label Matching is selected the remote node is selected by
Any analogue, digital byte or
Remote Module a match with the label of the module’s source (L). Blank N R
digital bit module parameter.
Retransmission
Interval
The amount the value of the source address can change before a message is sent. If set to '0' the messages
Significant Change 0 to 6500 1 N S
is only sent at the retransmission interval.
IQ4/BACnet. The write priority used to write the value to the BACnet device. 0 sends the request with
Write Priority 0 to 16 9 N w
no priority.
A1.11.7 IQ4 Maximum IC Comms Modules
Module Identifier N
Size in brIQs 17
The Maximum ic comms module requests the value of an analogue node (R) from all controllers that match the search criteria set up in the module, calculates the maximum value, and
makes it available for use in the strategy.

IQ4 Modules
A1.11.7.1 Maximum IC Comms Module Parameters

Text
Comms
0 to 7
0=comms disabled
1=identifier
2=F attribute
Attributes The attribute that must match in all devices for them to respond to the message. 3=G attribute 0 C B
4=H attribute
5=I attribute
6=J attribute
7=K attribute
0 or 1
1 = Failed
Local Module The output of the module. -1020 to +1020 0 O L
0 or 1
0=Enabled
0 to 119 excluding
Remote LAN Specifies the LAN of the devices to which the message is to be sent. addresses 2, 3, and 10. 0 I N
0 = local LAN.
Specifies the analogue parameter that is to be read. If Label Matching is selected the remote node is selected Any analogue module
Remote Module Blank N R
by a match with the label of the module connected to module’s output (L). parameter.
Retransmission
Interval

IQ4 Modules
A1.11.8 IQ4 Minimum IC Comms Modules

Module Identifier N
Size in brIQs 17
The Minimum ic comms module requests the value of an analogue node (remote node (R)) from all controllers that match the search criteria set up in the module, calculates the minimum
value, and makes it available as an output (L).
A1.11.8.1 IQ4 Minimum IC Comms Module Parameters
Text
Comms
0 to 7
0=comms disabled
1=identifier
2=F attribute
4=H attribute
5=I attribute
6=J attribute
7=K attribute
0 or 1
1 = Failed
0 or 1
0=Enabled
0 to 119 excluding
Remote LAN Specifies the LAN of the devices to which the message is to be sent. addresses 2, 3, and 10. 0 I N
0 = local LAN.
Retransmission
Interval

IQ4 Modules
Text
Comms
A1.11.9 IQ4 Sum IC Comms Modules
Module Identifier N
Size in brIQs 17
The sum ic comms module requests the value an analogue node (remote node (R)) from all controllers that match the search criteria set up in the module, calculates the sum, and places
it in the destination.
A1.11.9.1 IQ4 Sum IC Comms Module Parameters
Text
Comms
0 to 7
0=comms disabled
1=identifier
2=F attribute
Attributes The attribute that must match in all devices for them to respond to the message. 3=G attribute 0 N A
4=H attribute
5=I attribute
6=J attribute
7=K attribute
0 or 1
1 = Failed
0 or 1
0=Enabled
0 to 119 excluding addresses
Remote LAN Specifies the LAN of the devices to which the message is to be sent. 2, 3, and 10. 0 I N
0 = local LAN.

IQ4 Modules
Text
Comms
Retransmission
Interval

IQ4 Modules
A1.12 IQ4 Input Modules

Input modules take an input from the outside world, to a point within the controller. There are several different types to cope with different types of input devices.
IQ4 Analogue Node Modules
IQ4 Digital Byte Modules
IQ4 External Digital Input Modules
IQ4 External Digital Sensor Modules
IQ4 External Sensor Modules
IQ4 Internal Digital Input Modules
IQ4 Internal Digital Sensor Modules
IQ4 Internal Sensor Modules
IQ4 Knob Modules
IQ4 Switch Modules
A1.12.1 IQ4 Analogue Node Modules
Module Identifier A
Size in brIQs 14
The analogue node module stores an analogue value.
A1.12.1.1 IQ4 Analogue Node Module Parameters
following:
Text
Comms
The alarm status of the analogue value connected to the value parameter. Remain sat the default if the value parameter 00000000 to
Alarm Status 00000000 O S
is set as a constant. 11111111
0 or 1
High The status of the high alarm. 0 = No alarm 0 O H
1 = Alarm
0 or 1
Low The status of the low alarm. 0 = No alarm 0 O L
1 = Alarm
0 or 1
Outside
The status of the outside limits alarm. 0 = No alarm 0 O O
Limits
1 = Alarm

IQ4 Modules
Text
Comms
0 or 1
Read The status of the Read alarm. 0 = No alarm 0 O R
1 = Alarm
Value The value of the analogue node. It can be a constant, or an input from another controller using IC Comms. -1020 to +1020 0 I V
20 20
Output The value of the module. -10 to +10 0 O D
A1.12.2 IQ4 Digital Byte Modules
Module Identifier B
Size in brIQs 16
The Digital Byte module stores a byte of information (8-bits values a, b, c, d, e, f, g, h e.g. 01010100).
A1.12.2.1 IQ4 Digital Byte Module Parameters
following:

Bit a The value of bit 0. 0 or 1 0 O a
Bit b The value of bit 1. 0 or 1 0 O b
Bit c The value of bit 2. 0 or 1 0 O c
Bit d The value of bit 3. 0 or 1 0 O d
Bit e The value of bit 4. 0 or 1 0 O e
Bit f The value of bit 5. 0 or 1 0 O f
Bit g The value of bit 6. 0 or 1 0 O g
Bit h The value of bit 7. 0 or 1 0 O h
Value The 8-bit digital status of the byte. It can be a constant, or an input from another controller using IC Comms. 00000000 to 11111111 00000000 N S

IQ4 Modules
A1.12.3 IQ4 External Digital Input Modules

Module Identifier I
Size in brIQs 28
The External Digital input module takes the status from a real digital device such as a pressure switch, connected to a digital input of the controller, checks the value against the required
state, and places its value into a digital node.
A1.12.3.1 IQ4 External Digital Input Module Parameters
Text
Comms
ACK Transactions v3.50 or greater. The status of the modules user alarm acknowledgement. 000 to 111 111 O U
Alarm Delay (secs) The length of time in seconds that the value must be in the wrong state before a digital input alarm is generated. 0 to 172800 0 I d1(D)
Alarm Group Specifies the alarm group module to which the status alarm is sent. 0 to 500 0 N d1(G)
0 or 1
Alarm Sent Indicates if the alarm has been sent to the alarm group. 0 = Not sent 0 N d1(K)
1 = Sent
Alarm State (Digin) The current state of the status alarm of the module. 0 or 1 0 O d1(S)
Clear Alarm Delay v3.50 or greater. The length of time in seconds that digital input alarm must be cleared before a clear alarm is
0 to 172800 0 I d1(d)
(secs) generated.
0 or 1
Clear Alarm Enable
Specifies whether the state clear alarm is enabled. 1=Enabled 0 N d1(C)
(State)
0=Disabled
0 or 1
Enabled (State) Enables/Disables the state alarm. 0 = Disabled 0 I d1(E)
1 = Enabled
0 to 32
Hardware Channel The input channel on the specified I/O module to be used by the input. 1 N c
0 = Disabled

IQ4 Modules
Text
Comms
0 to 30
0 = IQ4
Hardware I/O Module The I/O module to which the input is connected. 0 N i
1 to 30 = I/O
modules
The length of time (in hours) the input has been ON. It can be used to provide an input to other modules by
Hours Run 0 to 87840 0 O H
linking it to the required modules.
0 or 1
In Alarm Indicates an alarm condition has been present for longer than its delay time and the alarm is enabled. 0 = No Alarm 0 N R
1 = Alarm
0 or 1
Override Output When set to 1 output (S) of the module is set to the value specified by the Override Value parameter. 1=Override 0 I ^
0=No override
Override Status The status to which the output (S) of the module is set if the Override Output parameter is set to 1. 0 or 1 0 I v
Required State The status that the input should be. When the input is not in this state, an alarm will be generated. 0 or 1 0 I R
The current number of times the driver has started. It can be used to provide an input to other modules by linking
Starts 0 to 109 0 O N
it to the required modules.
The output (S) of the module. It can be used to provide an input to other modules by linking it to the required
State 0 or 1 0 O S
modules.
Time in Alarm (secs) The length of time in seconds since the alarm state started. 0 to +1020 0 I d1(T)
0 or 1
Type Specifies whether the input is an External Digital Input, or an External Digital Input. 0 = External 0 N Y
1 = Internal
A1.12.4 IQ4 External Digital Sensor Modules
Module Identifier S
Size in brIQs 68
Default Overview Parameters $, V
The External Digital sensor module is intended for use with universal inputs set to read digital values that require logging. Using this type of sensor ensures that the sensor logging the
input is tied to the digital input performing the alarm handling functions. It takes the reading from a digital device, such as a pressure switch, connected to an input of the controller, and
stores it as an analogue value.

IQ4 Modules
A1.12.4.1 IQ4 External Digital Sensor Module Parameters
Text
Comms
0 to 32
Hardware Channel The input channel on the specified I/O module to be used by the sensor. 0 N c
0=Disabled
0 to 30
Hardware I/O Module The I/O module to which the input is connected. 0 = IQ4 0 N i
0 or 1
Override Output When set to 1 output of the module is set to the value specified by the Override Value parameter. 1=Override 0 I ^
0=No override
Override Value/Status The status to which the output of the module is set if the Override Output parameter is set to 1. 0 or 1 0 I
Source The digital status of the input channel. If the input channel is set to 0 this becomes a constant. 0 or 1 0 I S
Units 4-character string that specifies the engineering units of the sensor’s value. Any ASCII character except ( { ; , : Blank N %
Value The output of the module. 0 or 1 0 O V
Important if using this type of sensor, the corresponding digital input module MUST be added to the strategy.
A1.12.5 IQ4 External Sensor Modules
Module Identifier S
Size in brIQs 76
Default Overview Parameters $, V, %
The External Sensor module takes the reading from a real sensor connected to the analogue input of the controller, scales it into engineering units, and checks the value against alarm
levels. The sensor type determines how the scaling is performed. The sensor type is a separate module that defines parameters for a type of sensor. An offset is used to allow the reading
to be adjusted to the actual value.

IQ4 Modules
A1.12.5.1 IQ4 External Sensor Module Parameters

Text
Comms
Alarm Delay (High) The period (in seconds) for which the High alarm must be present before the High alarm is generated. 0 to 178200 0 S h1(D)
Alarm Delay (secs)
The period (in seconds) for which the Low alarm must be present before the Low alarm is generated. 0 to 178200 0 S l1(D)
(Low)
Alarm Delay (secs) The period (in seconds) for which the Out of Limits alarm must be present before the Out of Limits alarm is
0 to 178200 0 S 01(D)
(Out of Limits) generated.
Alarm Delay (secs)
The period (in seconds) for which the Read alarm must be present before the Read alarm is generated. 0 to 178200 0 S r1(D)
(Read)
Alarm Group (High) Specifies the alarm group to which the High alarm is sent. 0 to 500 0 N h1(G)
Alarm Group (Low) Specifies the alarm group to which the Low alarm is sent. 0 to 500 0 N l1(G)
Alarm Group (Out of
Specifies the alarm group to which the Out of Limits alarm is sent. 0 to 500 0 N o1(G)
Limits)
Alarm Group (Read) Specifies the alarm group to which the Read alarm is sent. 0 to 500 0 N r1(G)
0 or 1
Alarm Sent (High) Indicates if the High alarm has been sent to the alarm group. 0 = Not sent 0 N h1(K)
1 = Sent
0 or 1
Alarm Sent (Low) Indicates if the Low alarm has been sent to the alarm group. 0 = Not sent 0 N l1(K)
1 = Sent
0 or 1
Alarm Sent (Out of
Indicates if the Out of Limits alarm has been sent to the alarm group. 0 = Not sent 0 N o1(K)
Limits)
1 = Sent
Clear Alarm Delay v3.50 or greater. The period (in seconds) for which the High alarm must have cleared before the clear alarm is
0 to 178200 0 I h1(D)
(secs) (High) generated.
Clear Alarm Delay v3.50 or greater. The period (in seconds) for which the Low alarm must have cleared before the clear alarm is
0 to 178200 0 I l1(D)
(secs) (Low) generated.
Clear Alarm Delay v3.50 or greater. The period (in seconds) for which the Out of Limits alarm must have cleared before the clear
0 to 178200 0 I o1(D)
(secs) (Out of Limits) alarm is generated.

IQ4 Modules
Text
Comms
Clear Alarm Delay v3.50 or greater. The period (in seconds) for which the Read alarm must have cleared before the clear alarm is
0 to 178200 0 I g1(D)
(secs) (Read) generated.
0 or 1
Alarm Sent (Read) Indicates if the Read alarm has been sent to the alarm group. 0 = Not sent 0 N r1(K)
1 = Sent
Alarm State The status of the 4 alarm outputs. 0000 to 1111 0000 N M
0 or 1
Alarm State (High) The status of the High alarm. 0 = No alarm 0 O h1(S)
1 = Alarm
0 or 1
Alarm State (Low) The status of the Low alarm. 0 = No alarm 0 O l1(S)
1 = Alarm
0 or 1
Alarm State (Out of
The status of the Out of Limits alarm. 0 = No alarm 0 O o1(S)
Limits)
1 = Alarm
0 or 1
Alarm State (Read) The status of the Read alarm. 0 = No alarm 0 O r1(S)
1 = Alarm
0 or 1
Clear Alarm Enable
Specifies whether the read clear alarm is enabled. 1=Enabled 0 N h1(C)
(High)
0=Disabled
0 or 1
Clear Alarm Enable
Specifies whether the read clear alarm is enabled. 1=Enabled 0 N l1(C)
(Low)
0=Disabled
0 or 1
Clear Alarm Enable
Specifies whether the read clear alarm is enabled. 1=Enabled 0 N o1(C)
(Out of Limits)
0=Disabled
0 or 1
Clear Alarm Enable
Specifies whether the read clear alarm is enabled. 1=Enabled 0 N r1(C)
(Read)
0=Disabled
Specifies the amount by which the value must change before a BACnet notification is sent. If set to '0' there is
COV Increment 0 to +1020 0 N C
no notification.

IQ4 Modules
Text
Comms
0 or 1
Enabled (High) Enables/Disables the High alarm. 0 = Disabled 0 I h1(E)
1 = Enabled
0 or 1
Enabled (Low) Enables/Disables the Low alarm. 0 = Disabled 0 I l1(E)
1 = Enabled
0 or 1
Enabled (Out of
Enables/Disables the Out of Limits alarm. 1=Enabled 0 I o1(E)
Limits)
0=Disabled
0 or 1
Enabled (Read) Enables/Disables the Read alarm. 0 = Disabled 0 I r1(E)
1 = Enabled
High Alarm Level The value above which a sensor high alarm will be generated. -1020 to +1020 0 I H
0 to 32
Hardware Channel The input channel to be used by the sensor. 0 N c
0=Disabled
0 to 30
0 = IQ4
Hardware I/O Module The I/O module to which the input is connected. 0 N i
1 to 30 = I/O
modules
0 to 5 (excluding 1)
0 = No alarm
2 = High Alarm
In Alarm Indicates an alarm condition has been present for longer than its delay time and the alarm is enabled. 3 = Low alarm 0 N !
4 = Out of Limits
alarm
5 = Read alarm
Low Alarm Level The value below which a sensor low alarm will be generated. -1020 to +1020 0 I L
20 20
Offset The amount by which the sensor reading is to be increased, or decreased to make it accurate. -10 to +10 0 I O
0 or 1
Override Output When set to 1 output of the module is set to the value specified by the Override Value parameter. 1=Override 0 I ^
0=No override
Override Value/Status The status to which the output of the module is set if the Override Output parameter is set to 1. -1020 to +1020 0 I v
Source (mV) The value of the input channel. If the input channel is set to 0 this becomes a constant. 0 to 10000 0 I S

IQ4 Modules
Text
Comms
The length of time in seconds since the alarm state commenced. 0 to +1020 0 N h1(T)
(High)
The length of time in seconds since the alarm state commenced. 0 to +1020 0 N l1(T)
(Low)
The length of time in seconds since the alarm state commenced. 0 to +1020 0 N o1(T)
(Out of Limits)
The length of time in seconds since the alarm state commenced. 0 to +1020 0 N r1(T)
(Read)
The sensor type module used by the sensor to convert the signal into engineering units. Sensor type modules
Type store information about certain types of sensor. Ensure that the sensor type module chosen correctly specifies 0 to 99 1 N Y
the sensor that is being used.
Any ASCII
Units 4-character string that specifies the engineering units of the sensor's value. character except ( { Blank N %
;,:
Value The output of the sensor. -1020 to +1020 0 O V
A1.12.6 IQ4 Internal Digital Input Modules
Module Identifier I
Size in brIQs 26
The Internal Digital Input module takes the status of a digital value in the controller, checks the value against the required state, and places its value into a digital node.
Note: For IQ4 v3.0 and greater the module must be sequenced if the hours run output is connected.

IQ4 Modules
A1.12.6.1 IQ4 Internal Digital Input Module Parameters

Text
Comms
Alarm Delay (secs) The length of time in seconds that the value must be in the wrong state before an alarm is generated. 0 to 172800 0 I d1(D)
Alarm Group Specifies the alarm group module to which the status alarm is sent. 0 to 500 0 N d1(G)
0 or 1
Alarm Sent Indicates if the alarm has been sent to the alarm group. 0 = Not sent 0 N d1(K)
1 = Sent
Alarm State (Digin) The current state of the status alarm of the module. 0 or 1 0 O d1(S)
Clear Alarm Delay
v3.50 or greater. The length of time in seconds that digital input alarm must be cleared before a clear alarm is generated. 0 to 172800 0 I d1(d)
(secs)
0 or 1
Clear Alarm Enable
Specifies whether the state clear alarm is enabled. 1=Enabled 0 N d1(C)
(State)
0=Disabled
0 or 1
Enabled (State) Enables/Disables the state alarm. 0 = Disabled 0 I d1(E)
1 = Enabled
0 to 32
Hardware Channel The input channel on the specified I/O module to be used by the input. 1 N c
0 = Disabled
The length of time (in hours) the input has been ON. It can be used to provide an input to other modules by linking it to
Hours Run 0 to 87840 0 O H
the required modules. For the hours run to work correctly the module must be sequenced.
0 or 1
0 = No
In Alarm Indicates an alarm condition has been present for longer than its delay time and the alarm is enabled. 0 S R
Alarm
1 = Alarm
0 or 1
1=Override
Override Output When set to 1 output of the module is set to the value specified by the Override Value parameter. 0 I ^
0=No
override
Override Status The status to which the output of the module is set if the Override Output parameter is set to 1. 0 or 1 0 I v
Required State The status that the input should be. When the input is not in this state, an alarm will be generated. 0 or 1 0 I R

IQ4 Modules
Text
Comms
The current number of times the driver has started. It can be used to provide an input to other modules by linking it to the
Starts 0 to 109 0 O N
required modules.
State The output of the module. It can be used to provide an input to other modules by linking it to the required modules. 0 or 1 0 O S
Source The input value of the module. 0 or 1 0 I I
Time in Alarm
The length of time in seconds since the alarm state started. 0 to +1020 0 I d1(T)
(secs)
0 or 1
Type Specifies whether the input is an External Digital Input, or an External Digital Input. 0 = External - N Y
1 = Internal
A1.12.7 IQ4 Internal Digital Sensor Modules
Module Identifier S
Size in brIQs 66
The Internal Digital Sensor module allows a digital node to be monitored. It takes the value of a specified digital node, and puts it into an analogue node. This allows digital values to
be logged.
A1.12.7.1 IQ4 Internal Digital Sensor Module Parameters
Text
Comms
0 or 1
When set to 1 output of the module is set to the value specified by the Override Value parameter.
Override Output 1=Override 0 I ^
S
0=No override
Override
The status to which the output of the module is set if the Override Output parameter is set to 1. 0 or 1 0 I
Value/Status
Source The digital status of the input. 0 or 1 0 I S

IQ4 Modules
Text
Comms
Any ASCII character except ( { ; ,
Units 4-character string that specifies the engineering units of the sensor’s value. Blank N %
:
Value The output of the module. 0 or 1 0 O V
A1.12.8 IQ4 Internal Sensor Modules
Module Identifier S
Size in brIQs 74
Default Overview Parameters $, S, %
The Internal Sensor module allows an analogue node to be monitored. It takes the reading from within the controller, scales it into engineering units, and checks the value against
alarm levels. Internal sensors have an exponent, and source instead of sensor type, and offset. The source defines the analogue node from which the sensor takes its value. The exponent
determines the number of decimal places before the decimal point.
A1.12.8.1 IQ4 Internal Sensor Module Parameters
Text
Comms
The period (in seconds) for which the High alarm must be present before the High alarm is
Alarm Delay (High) 0 to 178200 0 S h1(D)
generated.
The period (in seconds) for which the Low alarm must be present before the Low alarm is
Alarm Delay (secs) (Low) 0 to 178200 0 S l1(D)
generated.
Alarm Delay (secs) (Out of The period (in seconds) for which the Out of Limits alarm must be present before the Out of
0 to 178200 0 S 01(D)
Limits) Limits alarm is generated.
The period (in seconds) for which the Read alarm must be present before the Read alarm is
Alarm Delay (secs) (Read) 0 to 178200 0 S r1(D)
generated.
Alarm Group (High) Specifies the alarm group to which the High alarm is sent. 0 to 500 0 N h1(G)
Alarm Group (Low) Specifies the alarm group to which the Low alarm is sent. 0 to 500 0 N l1(G)

IQ4 Modules
Text
Comms
Alarm Group (Out of Limits) Specifies the alarm group to which the Out of Limits alarm is sent. 0 to 500 0 N o1(G)
Alarm Group (Read) Specifies the alarm group to which the Read alarm is sent. 0 to 500 0 N r1(G)
0 or 1
Alarm Sent (High) Indicates if the High alarm has been sent to the alarm group. 0 = Not sent 0 N h1(K)
1 = Sent
0 or 1
Alarm Sent (Low) Indicates if the Low alarm has been sent to the alarm group. 0 = Not sent 0 N l1(K)
1 = Sent
0 or 1
Alarm Sent (Out of Limits) Indicates if the Out of Limits alarm has been sent to the alarm group. 0 = Not sent 0 N o1(K)
1 = Sent
0 or 1
Alarm Sent (Read) Indicates if the Read alarm has been sent to the alarm group. 0 = Not sent 0 N r1(K)
1 = Sent
Alarm State The status of the 4 alarm outputs. 0000 to 1111 0000 N M
0 or 1
Alarm State (High) The status of the High alarm. 0 = No alarm 0 O h1(S)
1 = Alarm
0 or 1
Alarm State (Low) The status of the Low alarm. 0 = No alarm 0 O l1(S)
1 = Alarm
0 or 1
Alarm State (Out of Limits) The status of the Out of Limits alarm. 0 = No alarm 0 O o1(S)
1 = Alarm
Clear Alarm Delay (secs) v3.50 or greater. The period (in seconds) for which the High alarm must have cleared before
0 to 178200 0 I h1(D)
(High) the clear alarm is generated.
Clear Alarm Delay (secs) v3.50 or greater. The period (in seconds) for which the Low alarm must have cleared before
0 to 178200 0 I l1(D)
(Low) the clear alarm is generated.
Clear Alarm Delay (secs) (Out v3.50 or greater. The period (in seconds) for which the Out of Limits alarm must have cleared
0 to 178200 0 I o1(D)
of Limits) before the clear alarm is generated.
Clear Alarm Delay (secs) v3.50 or greater. The period (in seconds) for which the Read alarm must have cleared before
0 to 178200 0 I g1(D)
(Read) the clear alarm is generated.

IQ4 Modules
Text
Comms
0 or 1
Alarm State (Read) The status of the Read alarm. 0 = No alarm 0 O r1(S)
1 = Alarm
0 or 1
Clear Alarm Enable (High) Specifies whether the read clear alarm is enabled. 1=Enabled 0 O h1(C)
0=Disabled
0 or 1
Clear Alarm Enable (Low) Specifies whether the read clear alarm is enabled. 1=Enabled 0 O l1(C)
0=Disabled
0 or 1
Clear Alarm Enable (Out of
Specifies whether the read clear alarm is enabled. 1=Enabled 0 O o1(C)
Limits)
0=Disabled
0 or 1
Clear Alarm Enable (Read) Specifies whether the read clear alarm is enabled. 1=Enabled 0 O r1(C)
0=Disabled
Specifies the amount by which the driver value must change before a BACnet notification is
COV Increment 0 to +1020 0 O C
sent. If set to '0' there is no notification.
0 or 1
Enabled (High) Enables/Disables the High alarm. 0 = Disabled 0 I h1(E)
1 = Enabled
0 or 1
Enabled (Low) Enables/Disables the Low alarm. 0 = Disabled 0 I l1(E)
1 = Enabled
0 or 1
Enabled (Out of Limits) Enables/Disables the Out of Limits alarm. 0 = Disabled 0 I o1(E)
1 = Enabled
0 or 1
Enabled (Read) Enables/Disables the Read alarm. 0 = Disabled 0 I r1(E)
1 = Enabled
High Alarm Level The value above which a sensor high alarm will be generated. -1020 to +1020 0 I H

IQ4 Modules
Text
Comms
0 to 5 (excluding 1)
0 = No alarm
Indicates an alarm condition has been present for longer than its delay time and the alarm is 2 = High Alarm
In Alarm 0 N !
enabled. 3 = Low alarm
4 = Out of Limits alarm
5 = Read alarm
Low Alarm Level The value below which a sensor low alarm will be generated. -1020 to +1020 0 I L
20 20
Offset Not used. -10 to +10 0 N O
0 or 1
When set to 1 output of the module is set to the value specified by the Override Value
Override Output 1=Override 0 I ^
parameter.
0=No override
-1020to +1020
Override Value/Status The status to which the output of the module is set if the Override Output parameter is set to 1. IQ4 v3.30 or greater double 0 I v
precision
Source The value of the input channel. If the input channel is set to 0 this becomes a constant. 0 to 10000 0 I S
Time in Alarm (secs) (High) The length of time in seconds since the alarm state commenced. 0 to +1020 0 N h1(T)
20
Time in Alarm (secs) (Low) The length of time in seconds since the alarm state commenced. 0 to +10 0 N l1(T)
Time in Alarm (secs) (Out of
The length of time in seconds since the alarm state commenced. 0 to +1020 0 N o1(T)
Limits)
Time in Alarm (secs) (Read) The length of time in seconds time since the alarm state commenced. 0 to +1020 0 N r1(T)
Type The sensor type module used by the sensor to convert the signal into engineering units. 0 to 99 1 N Y
Any ASCII character except
Units 4-character string that specifies the engineering units of the sensor’s value. Blank N %
({;,:
Value The output (V) of the sensor. -1020 to +1020 0 O V

IQ4 Modules
A1.12.9 IQ4 Knob Modules

Module Identifier K
Size in brIQs 13
The Knob module enables an analogue value to be changed. It has user-defined limits between which its value can be adjusted. Use of the knob can be restricted by using the PIN level
to prevent unauthorised adjustments. A self resetting operation is available from v3.40 firmware.
A1.12.9.1 IQ4 Knob Module Parameters
The modules include the following parameters that are common to most modules: ‘Label’, ‘Page,’ 'Sequence Step', 'Sequence Table', ‘X co-ordinate’ and ‘Y co-ordinate’ - see Common
IQ4 Module Parameters, plus the following:
Text
Comms
Bottom Range The minimum value of the knob. -1020 to +1020 0 I B
0 or 1
Specifies whether the knob's output is set to the bottom range value or upper range value when the knob is adjusted 0 = adjustment not
Clip to Limits 0 N L
outside these limits, or the adjustment is not allowed. allowed.
1 = adjustment allowed
COV Specifies the amount by which the knob value must change before a BACnet notification is sent.
0 to +1020 0 N C
Increment The ‘COV Increment’ parameter must not be set to ‘0’.
Destination The output (D) of the knob. -1020 to +1020 0 O D
v3.40 or greater. The value to which the ‘Destination’ parameter is set when the ‘Reset to Default’ parameter is set
Default Value -1020 to +1020 0 I F
to ‘1’.
Reset to
v3.40 or greater. When set to ‘1’ the ‘Destination’ parameter is set to the default value. 0 or 1 0 I R
Default
PIN Level The PIN level required before the knob can be adjusted. 0 to 99 0 N P
Top Range The maximum value of the knob. -1020 to +1020 0 I T
Any ASCII character
Units 4-character string that specifies the engineering units of the knob's value. Blank N %
except ( { ; , :
Value The value of the knob. -1020 to +1020 0 N V

IQ4 Modules
A1.12.10 IQ4 Switch Modules

Module Identifier W
Size in brIQs 10
Default Overview Parameters $, V
The Switch module enables a digital value to be changed. A self resetting operation is available from v3.40 firmware.
A1.12.10.1 IQ4 Switch Module Parameters
The modules include the following parameters that are common to most modules: ‘Label’, ‘Page,’ 'Sequence Step', 'Sequence Table', ‘X co-ordinate’ and ‘Y co-ordinate’ - see Common
IQ4 Module Parameters, plus the following:
Text
Comms
Destination The output (D) of the knob. 0 or 1 0 N D
Default Status v3.40 or greater. The value to which the 'Destination' parameter is set when the ‘Reset to Default’ parameter is set to ‘1’. 0 or 1 0 I F
PIN Level The PIN level required before the switch can be adjusted. 0 to 99 0 N P
v3.40 or greater. The time (in seconds) after which the ‘Destination’ parameter back to the default status. When set to ‘0’ the -10 to
20
Pulse interval 0 I L
Destination’ parameter will not be changed. +1020
Reset to
v3.40 or greater. When set to ‘1’ the ‘Destination’ parameter is set to the default status. 0 or 1 0 I R
Default
Status The value of the switch. 0 or 1 0 N S

IQ4 Modules
A1.13 IQ4 Interface Modules

Interface modules are only available on IQ4 v3.30 or greater.
IQ4 Type 1 (XNC) Interface Modules
IQ4 Type 2 (Wallbus) Interface Modules
IQ4 Type 3 (Modbus) Interface Modules
IQ4 Type 4 (M-bus) Interface Modules
A1.13.1 IQ4 Type 1 (XNC) Interface Modules
Module Identifier t1
Size in brIQs 230 (5 brIQs must be added for each input, output, store, or savedVars. 20 brIQs are required for each line of code in the TCL program.
IQ4 v3.1 or greater, only available on IQ4…/…/XNC/..s.
Type 1 (XNC) Interface modules are only available on /XNC variants. They provide the ability to connect between the IQ4’s strategy and the TCL application.
A1.13.1.1 IQ4 Type 1 (XNC) Interface Module Parameters
Text
Comms
Any ASCII
Alarm Label 1 30-character label describing the nature of TCL User alarm 1. character except Blank N U1
\/(){};,:
Any ASCII
Alarm Label 2 30-character label describing the nature of TCL User alarm 2. . character except Blank N U2
\/(){};,:
Any ASCII
\/(){};,:
Any ASCII
\/(){};,:
Any ASCII
\/(){};,:

IQ4 Modules
Text
Comms
Any ASCII
\/(){};,:
Alarm Reporting The LAN number of the device to which the TCL application will report software errors while being tested and 0, 4 to 119
Blank N R
Lan debugged. excluding 10.
The network address of the device to which the TCL application will report software errors while being tested and 0, 4 to 119
Alarm Reporting OS Blank N
debugged. excluding 10.
Current line The current line number, 0 unless at breakpoint. 0 to 1000 0 N L
0 or 1
0 = Run by IQ4
Debug Active Indicates whether TCLTool 2 is running the application. 0 N D
1 = Run by
TCLTool 2
ID The TCL application identifier specified in TCLTool 2, and read only - - N -
Any ASCII
A 20-character label for the TCL application specified in TCLTool 2. This is the label that will be used when TCL
Label character except - N $
alarms are sent to the alarm group. Read only
\/(){};,:
Last Error Last Error reported as a free format text string. 0 to 128 Blank N l
Number of Lines The number of lines of cone in the TCL application. . 1 to 1000 0 N c
Any ASCII
Program Author The name of the application's author (30-characters) specified in TCLTool 2. character except - N a
\/(){};,:
Any ASCII
The version of the TCL application (30-characters) specified in TCLTool 2, and read from the TCL application.
Program Version character except - N n
Read only.
\/(){};,:
1 to 10
1 = Stopped
2 = Loading
Program State The current state of the TCL application. 3 = Running 3 N L
4 = At Breakpoint
5 = Debug
6 = Error
Size of Module The size of the XNC interface module (in brIQs) including the TCL application. Read only 1 to 2000 0 N Z
The XNC interface module can have up to 1000 inputs each of which will use 5 brIQs of the controller’s memory. The following parameters are repeated for each of the inputs.

IQ4 Modules
Text
Comms
Any ASCII
Label A 30-character label for the input. character except Blank N I<n>$
\/(){};,:
Value The value of the input. -1020 to +1020 0 I I<n>V
<n> specifies the number of the input.
The XNC interface module can have up to 1000 outputs each of which will use 5 brIQs of the controller’s memory. The following parameters are repeated for each of the inputs.
Text
Comms
Any ASCII
Label A 30-character label for the output. . character except Blank N O<n>$
\/(){};,:
Value The value of the output. -1020 to +1020 0 I O<n>V
<n> specifies the number of the output.
Note: The total number of Inputs/outputs supported by the XNC3 is 1000 i.e. 750 inputs 250 Outputs.
The XNC interface module can have 20 stores that contain a specific string, each of which will use 5 brIQs of the controller’s memory. The following parameters are repeated for each
of the stores.
Text
Comms
Any ASCII
Label A 30-character label for the store. character except Blank N S<n>$
\/(){};,:
Value The string the store contains. -1020 to +1020 0 O S<n>V
<n> specifies the number of the output.
The XNC interface module also has 100 spaces of non-volatile memory, known as savedVars, which can be used to store both string and numeric data, each of which will use 5 brIQs
of the controller’s memory.
The module also contains the TCL program.

IQ4 Modules
A1.13.2 IQ4 Type 2 (Wallbus) Interface Modules

Module Identifier t
Size in brIQs 230 (5 brIQs must be added for each input or output.
IQ4 v3.1 or greater.
Type 2 (Wallbus) Interface modules enable a Wallbus device to be connected to the IQ4. A different instance of the Type 2 (Wallbus) Interface module is required for each Wallbus
device connected to the IQ4.
A1.13.2.1 IQ4 Type 2 (Wallbus) Interface Module Parameters
Text
Comms
The address determines which of several Wallbus devices is associated with this module. A total of 14 devices
0, 1, 2, 3, 4, 5, 6, 7, 8, 9,
may logically be attached to a single cable. Address is 4 bit (0-15). 0 is reserved, and the controller itself has an
Address 10, 11, 12, 13, 14, 15 2 N -
address of 1 by default, but that may be overridden in the network module. In practice the maximum number of
0 = reserved
devices fitted will be lower.
Device
Firmware Read only. The firmware version of the Wallbus device connected using the module, read from the device. - - C C
Version
The name of the device profile. A profile is a specific set of parameter values that is matched to a specific function
Device Profile on a specific type of Wallbus device. E.g. there will be a profile for RD-WMB that defines the appropriate inputs - - N f
and outputs with no filename.
Device Type Read only. Type of the Wallbus device connected using the module, read from the device. - - C T
0 or 1
Disable Module Enables/disables the module. When disabled the Wallbus communications will not work. 0 = Disabled 0 N ~
1 = Enabled
0 or 1
Failed Indicates that comms to address interface device have timed-out 0 = OK 0 N e
1 = Timeout
The name of the configuration file to be sent to Wallbus device.
Filename - - N F
For non-programmable devices, leave this parameter empty.
0 to 30-characters. Any
Input Label The label of the Input. Each input has this parameter, ‘n’ is input number 1 to 1000. ASCII character except null N In$
\/(){};,: 0

IQ4 Modules
Text
Comms
- full analogue to + full
Input Value The value of the Input. Each input has this parameter, ‘n’ is input number 1 to 1000. 0 I InV
analogue
Inputs (PV The PV in the Wallbus device to which the input of the Interface module is connected. Each input has this
- - N InN
Index) parameter, n determines the input.
Inputs (Refresh Defines the interval at the Interface module writes its value to the PV in the Wallbus device. Each input has this 0s, 5s, 10s, 15s, 20s, 25s,
- N InP
Period) parameter, n determines the input. 30s, 35, 40s, 45s, 50s
Inputs
Defines the amount by which the value of the input must change before the value is written to the PV in the
(Significant - - N InC
Wallbus device. Each input has this parameter, n determines the input.
change)
Label The name of the interface. ASCII character except - N $
\/(){};,: 0
Network The network module of the network to which the interface is to be connected. Valid module number - N n
Output Label The label of the output. Each output has this parameter, ‘n’ is input number 1 to 1000. ASCII character except null N On$
\/(){};,: 0
Output Value The value of the Output. Each output has this parameter, ‘n’ is output number 1 to 1000. 0 I OnV
analogue
The time, in seconds, that the value of the output is held for after the last communication from the Wallbus device.
Outputs 0s, 5s, 10s, 15s, 20s, 25s,
‘0’ holds indefinitely. Any other value, nn, will cause the output’s value to be set to ‘FL_INVALID’ nn seconds - N OnM
(Expiry time) 30s, 35, 40s, 45s, 50s
after the last update is received from the Wallbus device, where nn is the value of this parameter.
Outputs (PV The PV in the Wallbus device to which the output of the Interface module is connected. Each output has this
- - N OnN
1, 2
Program Type The type of interface module. 1 = XNC 1 N Y
2 = Wallbus
Size of
Size of the module including any application file (e.g. TCL application). 1 to 2000 0 N Z
Modules
0, 1, 2
0 = Not Present
Status The status of interface device. 0 N t
1 = Operational
2= Not Communicating

IQ4 Modules
A1.13.3 IQ4 Type 3 (Modbus) Interface Modules

Module Identifier t
Size in brIQs 230 (5 brIQs must be added for each input,or output
IQ4 v4.20 firmware or greater /INT variants.
Type 3 (Modbus) Interface modules enable a Modbus device to be connected to the IQ4. A different instance of the Type 3 (Modbus) Interface module is required for each Modbus
device connected to the IQ4.
A1.13.3.1 IQ4 Type 3 (Modbus) Interface Module Parameters
Text
Comms
Serial = 1 to 247
Address The address determines which Modbus device is associated with this module. 2 N d
IP = 1 to 255
The byte order:
Big Endian
e.g. B1,B2,B3,B4 for a 32 bit integer value
0, 1, 2, 3
or B1,B2,B3,B4,B5,B6,B7,B8 for a 64 bit Integer value.
0 = Big Endian (B1,B2,B3,B4)
Little Endian
Byte Order 1 = Little Endian (B4,B3,B2,B1) O N B
e.g. B2,B1 or B4,B3,B2,B1 or B8,B7,B6,B5,B4,B3,B2,B1
2 = Big Endian/Word swap (B3,B4,B1,B2)
Big Endian with Word Swap
3 = Little Endian/Word swap (B2,B1,B4,B3)
e.g. B3,B4,B1,B2
Little Endian with Word Swap
e.g. B2,B1,B4,B3
The name of the device profile. A profile is a specific set of parameter values that is
Device Profile - - N f
matched to a specific function on a specific type of device.
0 or 1
Disable
Enables/disables the module. When disabled the communications will not work. 0 = Disabled 0 N ~
Module
1 = Enabled

IQ4 Modules
Text
Comms
00, 01, 02, 04, 05, 07, 09, 10, 11, 12, 13
00 = single bit. A value on I[n]V >= 0.5 is converted to 1.
Values < 0.5 are converted to 0.
01 = 2 byte unsigned Integer.
02 = 2 byte signed integer
04 = IEEE value. 4 byte format (float).
05 = IEEE value 8 byte format (double).
07 = BCD 2 byte integer
Inputs Data Determines how many consecutive registers are written, and how the value of I[n]V
09 = Allows a bit mask to be applied to a 16 bit word. E.g. 00 N InE
Format is converted to register values.
a bit mask retrieving bits 5 through 9 would be
0000001111100000. Bitmasks should only be defined as
either a single bit or multiple consecutive bits for any given
Output Instance.
10 = 4 byte unsigned integer
11 = 4 byte signed integer.
12 = 8 byte unsigned integer (64 bit)
13 = 8 byte signed Integer (64 bit)
Inputs Refresh Time in seconds between write. 0 to 1800
0 N InP
Period Each input has this parameter, n determines the input. 0 = on change only
The Modbus register address where the input’s value is written.
or
Inputs Defines a Modbus Digital Input or Input Register address from where the input’s
Register value is written. - - N InN
Address The number of consecutive addresses written will be determined by the data format
parameter for this Input.
Each input has this parameter, n determines the input.
Only for registers with a Data Format of 9 (Bitmask). It defines the bit(s) that will
be written to when the input value changes
Inputs
When applying bit masks to data being written to the register the current value of
Register - - N InM
the register must be read, and then the bit mask applied to preserve the data not
Bitmask
affected by the bitmask. Thus only affecting the data in the bits specified.

IQ4 Modules
Text
Comms
The power of 10 scaling factor to apply to the register value to convert it to the
required units. E.g. a scale factor of +2 would multiply the value by 100, a scale
Inputs Scaling
factor of -2 would multiply the value by 0.01. -20 to +20 0 N InF
Factor
Note: Restricted to integer values.
Inputs The difference between the current value of I[n]V and the last transmitted value of
Significant I[n]V that will cause the new value to be sent to the Modbus device. - - N InC
change Each input has this parameter, n determines the input.
Inputs Base
The a base value to apply to all Inputs Register Addresses. This allows register offset
Register 0 to 65535 0 N i
addressing mode to be used.
Address
00, 01, 02, 04, 05, 07, 09, 10, 11, 12, 13
00 = single bit
01 = 2 byte unsigned Integer.
02 = 2 byte signed integer
04 = IEEE value. 4 byte format (float).
05 = IEEE value 8 byte format (double).
07 = BCD 2 byte integer
Determines how many consecutive registers are read, and how the values are
Outputs Data 09 = Allows a bit mask to be applied to a 16 bit word. E.g.
combined to form the value of O[n]V. - - OnF
Format a bit mask retrieving bits 5 through 9 would be
Each output has this parameter, n determines the output.
0000001111100000 Bitmasks should only be defined as
either a single bit or multiple consecutive bits for any given
output
10 = 4 byte unsigned integer
11 = 4 byte signed integer.
12 = 8 byte unsigned integer (64 bit)
13 = 8 byte signed integer (64 bit)
Outputs Time in seconds between read requests. 0 to 1800
60 N OnP
Refresh Period Each output has this parameter, n determines the output. 0 = on change only
The Modbus coil or register address from where the value of O[n]V is read. The
Outputs
number of consecutive addresses read will be determined by the data format
Register - - N OnN
parameter for this output.
Address

IQ4 Modules
Text
Comms
Only for registers with a Data Format of 9 (Bitmask). It defines the bit(s) that will
be extracted from the register read operation and applied to the Outputs Value.
Outputs
When applying bit masks to data being written to the register the current value of
Register - 0000 N OnM
the register must be read, and then the bit mask applied to preserve the data not
Bitmask
affected by the bitmask. Thus only affecting the data in the bits specified.
Outputs Base
The a base value to apply to all Outputs Register Addresses. This allows register
Register 0 to 65535 0 N i
offset addressing mode to be used.
Address
Specifies whether the register can be written or just read. It is only used when the
'Register Addressing Mode' parameter is set to 1 or 2 (Extended Addressing or
Outputs Extended Addressing Base 1). 0, 1
Register When set to ‘0’ the register being addressed is a Holding Register or a Coil 0 = Read/Write 0 N OnT
Type depending upon the output's Data Format. 1 = Read Only
When set to ‘1’ the register being addressed is a Discrete or Analogue Input
depending upon the output’s Data Format.
The power of 10 scaling factor to apply to the register value to convert it to the
required units. E.g. a scale factor of +2 would multiply the value by 100, a scale
Outputs
factor of -2 would multiply the value by 0.01. -20 to +20 0 N OnE
Scaling Factor
Each output has this parameter, n determines the input.
0, 1, 2
0 = Standard Modbus addressing (e.g. 40001 to 49999 for
The addressing mode used by the module. holding registers,
Register When set to 1 or 2 it is combined with the 'Data Type' and 'Outputs Register Type' 30001 to 39999 for analogue Input registers etc.)
Addressing to determine which type of item is to be written/read. For example for a data type of 1 = Extended Addressing (e.g. 0 to 65535 used to specify 0 N m
Mode single bit, and output register type of Read Only a Discrete Input register would be address.
read. Whereas for a output register type of Read-Write a Coild would be read. 2 = Extended Addressing Base 1. This is the same as
Extended Addressing except that addresses are in the range
(1 – 65536)
0, 1, 2
0 = Not Present
1 = Operational

IQ4 Modules
A1.13.4 IQ4 Type 4 (M-bus) Interface Modules

Module Identifier t
Size in brIQs 230 (5 brIQs must be added for each output
Type 4 (M-bus) Interface modules enable a Modbus device to be connected to the IQ4. A different instance of the Type 4 (M-bus) Interface module is required for each M-bus device
connected to the IQ4.
A1.13.4.1 IQ4 Type 4 (M-bus) Interface Module Parameters
Text
Comms
id The identifier for the device being read. Two digit number - - i
The name of the device profile. A profile is a specific set of parameter values that is matched to a
Device Profile - - N f
specific function on a specific type of device.
0 or 1
Disable Module Enables/disables the module. When disabled the communications will not work. 0 = Disabled 0 N ~
1 = Enabled
Enhanced 0 to 30-characters. Any ASCII
Serial number of device to be read. 0 N B
Secondary Address character except \/(){};,:
Manufacturer Code 3-character code representing the manufacturer of the device being read. 3-character string - - m
Medium The medium the meter is monitoring e.g. Heat, Oil, Water String - N u

IQ4 Modules
Text
Comms
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,
12, 13, 14, 15
0 - Energy
1 - Energy
2 - Volume
3 - Mass
4 - Time : Not supported
5 - Power
Determines which of the data values returned from the device is written to O[n]V. 6 - Power
Outputs Data Index - - OnN
Each Output has this parameter, n determines the output. 7 - Volume Flow
8 - Volume Flow
9 - Volume Flow
10 - Mass Flow
11 - Flow Temperature
12 - Return Temperature
13 - Temperature Difference
14 - External Temperature
15 - Pressure
Time in seconds between read requests.
Note: Some battery powered meters will only respond at a minimum refresh rate of 2 hours (or more).
Outputs Refresh Once one refresh request has been made, a further request will receive no response until the meters 0 to 1800
60 N OnP
Period refresh. 0 = on change only
period has elapsed.
The power of 10 scaling factor to apply to the register value to convert it to the required units. E.g. a
scale factor of +2 would multiply the value by 100, a scale factor of -2 would multiply the value by
0.01.
Outputs Scaling All values read from the meter are in a normalised form for the type of value they are reading – e.g.
-20 to +20 0 N OnE
Factor Wh. So if the value should be presented as KWh – the value returned from the meter would need a
scaling factor of 3.
Primary Address Address of the device to be read. 0 to 15 0 N d
Secondary Address The serial number of device to be read. 8-decimal digit string value. - N D

IQ4 Modules
Text
Comms
0, 1, 2
0 = Not Present
1 = Operational

IQ4 Modules
A1.14 IQ4 I/O Modules

Module Identifier I
Size in brIQs 14
I/O modules specify any external I/O modules that are connected to the controller. A separate I/O module must be added for each physical I/O module connected to the controller.
Note: IQ41x, IQ422 and IQ4NC controllers do not support external I/O modules.
A1.14.1 IQ4 I/O Module Module Parameters
following:
Text
Comms
Actual Type The actual module type as found on the bus. Character String Blank N A
IQ4 v3.30 or greater. If connecting an IQ4/IO module the address is set by the strategy in the range 1 to 15. If
Address connecting XCITE I/O module the address is set by the I/O module’s address switch in the range 1 to 15 (labelled 0 to 15 N/A N M
1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F).
Configured
Specifies the type of I/O module that is to be connected to the controller. Character String Blank N Y
Type
0 or 1
Indicates if the I/O module is in a failed state i.e. state is 'not present' (0), 'recoverable fault' (4), or 'unrecoverable
Failed 0 = OK 0 N F
fault' (5).
1 = Failed
Firmware
IQ4 v3.30 or greater. The firmware version of the I/O module discovered by communication with the module. ASCII character except - N C
version
\/(){};,: 0
0 to F Module
Module ID Specifies the id of the I/O module. This must match the module's CAN address. 0 N
0 = main controller Number
Serial Any ASCII character except Factory
IQ4 v3.30 or greater. The serial number of the hardware I/O module, also printed on the module. N S
Number \/(){};,: set

IQ4 Modules
Text
Comms
0 to 8
0 = Not present
1 = Self testing
2 = Standby
3 = Operational
State IQ4 v3.30 or greater. The state of the I/O module. 4 = Major recoverable fault 0 N T
5 = Major unrecoverable
fault
6 = Unaddressed -
7 = Duplicate Address
8 = Upgrade
Version The I/O module's firmware version. Character string fixed N C
IQ4 v3.30 or greater. When set to ‘1’ the I/O module indicates its address by flashing its I/O Bus indicator.
When set to ‘1’ by pressing the I/O module’s Service button the I/O module will flash its address once. The value
0 or 1
remains at '1' and subsequent presses of the Service button will cause it to flash the address again. The value can
Wink 0 = No flash 0 N W
only be set back to '0' using IQSET, text comms or the IQ4’s web pages.
1 = Flash
When set to '1' using IQSET, text comms or the IQ's web pages the I/O module will repeatedly flash its address
until the I/O module’s Service button is pressed or it is set to ‘0’.

IQ4 Modules
A1.15 IQ4 Logic Modules

Logic modules allow outputs to be generated as a function of several digital values within a control strategy.
IQ4 Change of State Logic Modules
IQ4 Combination Logic Modules
IQ4 Counter Logic Modules
IQ4 Delay Logic Modules
IQ4 Digital Input Selector Logic Modules
IQ4 D to A Logic Modules
IQ4 Fan Out Logic Modules
IQ4 Flip Flop Logic Modules
IQ4 Hours Run Logic Modules
IQ4 Latch Logic Modules
IQ4 Readback Logic Modules
IQ4 Timer Logic Modules
A1.15.1 IQ4 Change of State Logic Modules
Module Identifier G
Size in brIQs 19
Change of State Logic modules pulse the ‘Destination D’ parameter when the value of the ‘Source’ parameter changes. The pulse can be initiated on either the rising edge of the change,
falling edge of the change or both.
A1.15.1.1 IQ4 Change of State Logic Module Parameters
Text
Comms
Destination The output (D) of the module. 0 or 1 0 O D
Falling Edge
When set to ‘1’ pulses the module’s ‘Destination D’ parameter on the falling edge of a change of value. 0 or 1 1 I F
Enable

IQ4 Modules
Text
Comms
0 or 1
1=
Invert Output When set to ‘1’ then the normal status of the ‘Destination D’ parameter is ‘1’ and the output pulse is set to ‘0’. Inverted 0 O I
0=
Normal
The duration of the output pulse, in seconds. If this is set to ‘0’ then the pulse will last for one complete cycle of the sequence
Pulse Duration +analogue 0 I P
table and in the case of event based execution the OFF event follows the ON event directly.
Rising Edge
When set to ‘1’ pulses the module’s ‘Destination D’ parameter on the rising edge of a change of value. 0 or 1 1 I R
Enable
Source The value that is to be monitored for changes. 0 or 1 0 I S
A1.15.2 IQ4 Combination Logic Modules
Module Identifier G
Size in brIQs 19
The Combination Logic module calculates its output (D) (0 or 1) as the logical combination of up to 4 logical functions (J), (K), (L), and (M). Each logical function is itself a function
of 4 digital values (E), (F), (G), and (H) which are AND’ed together ((E) AND (F) AND (G) AND (H)). An AND NOT function can also be achieved by specifying a lowercase letter
instead of uppercase. This allows combinations of AND, and NOT functions within each of the logical functions (J), (K), (L), and (M). The output (D) is the result of all logical functions
OR’ed together ((J) OR (K) OR (L) OR (M).
A1.15.2.1 IQ4 Combination Logic Module Parameters
Text
Comms
Logically combines up to 4 digital values (E), (F), (G), or (H) using AND, and AND NOT functions. uppercase letters indicate
Combination Boolean of
the true state, and lowercase letters indicate the false state (i.e. NOT). The result of this logical combination will be OR’ed with Blank N J
J EeFfGgHh
the results of the logical functions K, L, and M.
the true state, and lowercase letters indicate the false state (i.e. NOT). The result of this logical combination will be OR’ed with Blank N K
K EeFfGgHh
the results of the logical functions J, L, and M.

IQ4 Modules
Text
Comms
the true state, and lowercase letters indicate the false state (i.e. NOT). The result of this logical combination will be OR’ed with Blank N L
L EeFfGgHh
the results of the logical functions J, K, and M.
the true state, and lowercase letters indicate the false state (i.e. NOT). The result of this logical combination will be OR’ed with Blank N M
M EeFfGgHh
the results of the logical functions J, K, and L.
Input E Specifies (E) in the logical combination. 0 or 1 0 I E
Input F Specifies (F) in the logical combination. 0 or 1 0 I F
Input G Specifies (G) in the logical combination. 0 or 1 0 I G
Input H Specifies (H) in the logical combination. 0 or 1 0 I H
A1.15.3 IQ4 Counter Logic Modules
Module Identifier G
Size in brIQs 18
The Counter Logic module provides the facility for counting pulse type signals such as those provided by gas and electricity meters. It has two outputs rate (R) and cumulative count
(M). (M) is the total number of times the input (S) has been set to 1 since the reset input (A) was last set to 1 multiplied by the scaling factor (F). (R) is the change in (M) over the period
(T).
A1.15.3.1 IQ4 Counter Logic Module Parameters
Text
Comms
Cumulative IQ4 v3.30 or greater. The cumulative output (M) calculated by the module. It can be used to provide an input
Double precision 0 O M
Output to other modules by linking it to the required modules.
Last Cumulative
IQ4 v3.30 or greater. The value of the Cumulative Count when the module was last serviced. Full analogue 0 N l
Count
Page Specifies the strategy page containing the module. 0 to 255 0 N p

IQ4 Modules
Text
Comms
Power IQ4 v3.30 or greater. The power in either kW or Btu/hour. Full analogue 0 N P
The rate (R) calculated by the module. It can be used to provide an input to other modules by linking it to the
Rate -1020 to +1020 0 O R
required modules.
Reschedule Time Defines the time, in seconds, over which the rate is calculated. 0 to 32767 5 N T
Reset The state of the reset input. 0 or 1 0 I A
20 20
-10 to +10
Scale Factor The value of each input pulse. IQ4 v3.30 or greater 1 I F
Double precision
Source The value being counted. 0 or 1 0 I S
A1.15.4 IQ4 Delay Logic Modules
Module Identifier G
Size in brIQs 14
The Delay Logic module is specifically designed for interacting with the alarm reporting mechanism of the strategy allowing a grace time before alarms are reported. It calculates its
output (D) as 0 or 1 by comparing two inputs (E and G). If they are different for longer than the grace time, the output (D) will be set to 1. If they are the same, output (D) will be 0.
A1.15.4.1 IQ4 Delay Logic Module Parameters

Grace Time The delay (in seconds) on the change of the digital output or readback signals during which comparisons are not made. 0 to 32767 0 N A
Source E Specifies (E) in the calculation. 0 or 1 0 I E
Source G Specifies (G) in the calculation. 0 or 1 0 I G

IQ4 Modules
A1.15.5 IQ4 Digital Input Selector Logic Modules

Module Identifier G
Size in brIQs 18
Digital Input Selector Logic modules set their ‘Destination’ parameter to the value of one of up to eight digital input parameters (‘Input a’, ‘Input b’, ‘Input c’, ‘Input d’, ‘Input e’, ‘Input
f’, ‘Input g’, or ‘Input h’) depending on the ROUND of the value of the ‘Selector’ parameter minus the value of the ‘Offset’ parameter providing this value is 0, 1, 2, 3,4, 5, 6 or 7.
E.g. if 'Selector' parameter = '10.4' and 'Offset' parameter = 5. This give a calculation of 10.4 - 5 = 5.4 which is rounded to ‘5 ‘.
If the ROUND of the value of the ‘Selector’ parameter minus the value of the ‘Offset’ parameter is not 0, 1, 2, 3, 4, 5, 6 or 7 the ‘Destination’ parameter is set to the value of the 'Default
Input’ parameter.
A1.15.5.1 IQ4 Digital Input Selector Logic Module Parameters
Text
Comms
Default Full
The value used when the result of the calculation above is not 0, 1, 2, 3, 4, 5, 6 or 7. 0 I F
Input Analogue
Destination Full
The module's output. 0 O D
D Analogue
Input a The value used when the result of the calculation above is ‘0’ 0 or 1 0 I a
Input b The value used when the result of the calculation above is ‘1’ 0 or 1 0 I b
Input c The value used when the result of the calculation above is ‘2’ 0 or 1 0 I c
Input d The value used when the result of the calculation above is ‘3’ 0 or 1 0 I d
Input e The value used when the result of the calculation above is ‘4’ 0 or 1 0 I e
Input f The value used when the result of the calculation above is ‘5’ 0 or 1 0 I f
Input g The value used when the result of the calculation above is ‘6’ 0 or 1 0 I g
Input h The value used when the result of the calculation above is ‘7’ 0 or 1 0 I h
The value subtracted form the value of the ‘Selector’ parameter. It allows support for base values of 0 and 1. It also supports the Full
Offset 1 I O
ability to cascade selector modules’. The default of 1 allows support for operation with BACnet multi-state objects. Analogue
Full
Selector Determines which of the 8 analogue inputs is used for the ‘Destination’ parameter’s value. 0 I S
Analogue

IQ4 Modules
A1.15.6 IQ4 D to A Logic Modules
Module Identifier G
Size in brIQs 19
The D to A Logic module converts the digital inputs E, F, G, H, I, J, K, and L into a single analogue output D. The value of (D) represents the binary value of the input bits. E specifies
1 when set, F specifies 2 when set, G specifies 4 when set, H specifies 8 when set, I specifies 16 when set, J specifies 32 when set, K specifies 64 when set, and L specifies 128 when
set. e.g. with the following inputs (E)=1, (F)=0, (G)=1, (H)=0, (I)=1, (J)=0, (K)=0, (L)=0, output (D) would be 21. The module uses the following formula:
D=1x(E) + 2x(F) + 4x(G) + 8x(H) + 16x(I) + 32x(J) + 64x(K) + 128x(L)
A1.15.6.1 IQ4 D to A Logic Module Parameters
Text
Comms
Bit 0 Specifies (a) in the calculation, adds 1 to the output. 0 or 1 0 I a
Bit 1 Specifies (b) in the calculation, adds 2 to the output. 0 or 1 0 I b
Bit 2 Specifies (c) in the calculation, adds 4 to the output. 0 or 1 0 I c
Bit 3 Specifies (d) in the calculation, adds 8 to the output. 0 or 1 0 I d
Bit 4 Specifies (e) in the calculation, adds 16 to the output. 0 or 1 0 I e
Bit 5 Specifies (f) in the calculation, adds 32 to the output. 0 or 1 0 I f
Bit 6 Specifies (g) in the calculation, adds 64 to the output. 0 or 1 0 I g
Bit 7 Specifies (h) in the calculation, adds 128 to the output. 0 or 1 0 I h
20 20
Destination The output (D) of the module. -10 to +10 0 O D
Specifies the digital node from which the value used as (E) is read. If it is not to be used in the calculation it should be linked Any digital
Input E - I E
node 0,0. node

IQ4 Modules
A1.15.7 IQ4 Fan Out Logic Modules

Module Identifier G
Size in brIQs 18
The Fan Out Logic module takes its input S and writes the value to its in six outputs (J), (K), (L), (M), (N) and (O). If required, the value of the outputs can be set to be the opposite of
the input. The module uses the following formula:
(J)=(K)=(L)=(M)=(N)=(O)=(S)
A1.15.7.1 IQ4 Fan Out Logic Module Parameters

0 or 1
Invert Specifies whether the state of the outputs is the same, or opposite to the state of the input. 0 N I
1 = Enabled
Output J The output (J) of the module. 0 or 1 0 O J
Output K The output (K) of the module. 0 or 1 0 O K
Output L The output (L) of the module. 0 or 1 0 O L
Output M The output (M) of the module. 0 or 1 0 O M
Output N The output (N) of the module. 0 or 1 0 O N
Output O The output (O) of the module. 0 or 1 0 O O
Source The modules input. 0 or 1 0 I S

IQ4 Modules
A1.15.8 IQ4 Flip Flop Logic Modules

Module Identifier G
Size in brIQs 18
Flip Flop Logic modules set the 'Destination D' parameter (D) to '1' when the 'Set' parameter is set to '1' and will keep it set to '1' until the 'Reset' parameter is set to '1'. If both the 'Set'
and 'Reset' parameters are '1' the 'Destination D' parameter (D) is set to '0'. The 'Destination d' parameter (d) is always set to the inverse of the 'Destination D' parameter (D). The
operation can be inverted by setting the 'Invert inputs' parameter to '1'.
The module’s status is retained when the IQ4 is powered down and when the IQ4 restarts it the module will adopt the status at power down.
A1.15.8.1 IQ4 Flip Flop Logic Module Parameters

Destination d The inverse of the Destination d' parameter. 0 or 1 0 O d
Destination D The output (D) of the module. 0 or 1 0 O D
0 or 1
Invert Inputs Specifies whether the state of the outputs of the module is inverted. 0 = Normal 0 N P
1 = Inverted
Set When set to '1' sets the modules output (D) to '1' 0 or 1 0 I S
A1.15.9 IQ4 Hours Run Logic Modules
Module Identifier G
Size in brIQs 16
Default Overview Parameters $, O
The Hours run Logic module calculates its output (O) as the length of time in hours for which the source bit (S) has been ON since reset input (A) was last set to 1. It also calculates its
other output (N) as 0 or 1 by comparing output (O) with input (I) (which specifies an interval) and if (O)>I sets (N) to 1 (interval exceeded).

IQ4 Modules
A1.15.9.1 IQ4 Hours Run Logic Module Parameters

Text
Comms
Hours Run The cumulative number of hours run output (O) of the module run calculated by the module (O). It can be used to provide
-1020 to +1020 0 O O
Output an input to other modules by linking it to the required modules.
Interval The maximum number of hours run before an alarm is generated. -1020 to +1020 0 I I
0 or 1
Interval Limit Indicates when the hours run limit is exceeded. It can be used to provide an input to other modules by linking it to the
1 = Interval 0 O N
Alarm required modules. A
exceeded.
0 or 1
Reset Resets the count of hours and alarm condition. 0 I A
1 = Reset
Source The state of the module whose hours run are being accumulated. 0 or 1 0 I S
A1.15.10 IQ4 Latch Logic Modules
Module Identifier G
Size in brIQs 18
Latch Logic modules allow a digital state to be stored when a trigger input is set. The 'Destination D' parameter (D) is set to the value of the 'Source' parameter when the 'Trigger'
parameter is set to '1'. The 'Destination' parameter will remain at that value until the 'Trigger' parameter is set to '1' again. The 'Destination D' parameter (D) can be set to the value of
the 'Default Value' parameter by setting the 'Reset' parameter to '1'.
The module's status is retained when the IQ4 is powered down and when the IQ4 restarts it the module will adopt the status at power down.
A1.15.10.1 IQ4 Latch Logic Module Parameters

Default Value The value to be used when the 'Reset' parameter is set to '1'. 0 or 1 0 N D
Destination D The output (D) of the module. 0 or 1 0 O D

IQ4 Modules

0 or 1
Reset When set to '1' sets the module's 'Destination D' parameter to the value specified by the 'Default Value' parameter. 0 = no change 0 I R
1 = Reset
Source The value being processed. 0 or 1 0 I S
Trigger When set to '1' sets the module's output 'D' to the value of the 'Source' parameter. 0 or 1 0 I T
A1.15.11 IQ4 Readback Logic Modules
Module Identifier G
Size in brIQs 18
The Readback module calculates its output (D) as 0 or 1 by comparing two input signals (E) and (G). If the value of (E) and (G) differ for longer than the grace time, the output (D) is
set to 1. It will be set back to 0 again when (E) and (G) remain the same for longer than the grace time. Two other inputs (F and H) can also be used in the comparison. The module uses
the following formula to calculate its output:
D=E and NOT G OR G and NOT E OR F and NOT H OR H and NOT F
A1.15.11.1 IQ4 Readback Logic Module Parameters

Grace Time The length of time in seconds after the input changes that comparisons are not made. 0 to 32767 0 I T
Source E Specifies (E) in the calculation. If it is not to be used in the calculation, it should be set to a constant value of 0. 0 or 1 0 I E
Source F Specifies (F) in the calculation. If it is not to be used in the calculation, it should be set to a constant value of 0. 0 or 1 0 I F
Source G Specifies (G) in the calculation. If it is not to be used in the calculation, it should be set to a constant value of 0. 0 or 1 0 I G
Source H Specifies (H) in the calculation. If it is not to be used in the calculation, it should be set to a constant value of 0. 0 or 1 0 I H

IQ4 Modules
A1.15.12 IQ4 Timer Logic Modules

Module Identifier G
Size in brIQs 18
The Timer Logic module calculates its output (D) based on the state of its input (S) and the ON delay (N), minimum ON time (M), and OFF delay (F). If the input (S) is set to 1 the
output (D) will not change to 1 until the ON delay time has passed. It will then remain as 1 for at least the length of time specified by the minimum ON time. When the input (S) changes
to 0 the output (D) will only be set to 0 providing the minimum ON time has passed. If an OFF delay is set, the output will stay ON until the OFF delay has passed.
A1.15.12.1 IQ4 Timer Logic Module Parameters

Minimum On The minimum time in seconds that the output of a timer module is ON. 0 to 32767 0 I M
On Delay The length of time in seconds after the input of a timer is ON before the output is turned ON. 0 to 32767 0 I N
Off Delay The length of time in seconds after the input of a timer is OFF before the output is turned OFF. 0 to 32767 0 I F
Source The value being timed. 0 or 1 0 I S

IQ4 Modules
A1.16 IQ4 Loop Modules

Module Identifier L
Size in brIQs 55
Loop modules perform the mathematical calculations that determine, the value of output (D) based on present, and past values of measured variables. The loop module compares the
measured value (P) with the current setpoint. The difference between (P) and the current setpoint is the error. The loop then calculates the value of output (D) to reduce the error. The
choice of setpoint is dependent on the value of the setpoint select parameter (S). If set to 1 the occupied setpoint (O) is used, if set to 0 the unoccupied setpoint (U) is used. If the manual
select parameter (A) is set to 1 the loop will use the manual level (L) as the current output level, if set to 0 the calculated value will be used for the output.
A1.16.1 IQ4 Loop Module Parameters
Text
Comms
Alarm Delay (secs) (PV
The period (in seconds) loop input must be invalid before a PV Fail alarm is generated. 0 to 172800 0 I f1(D)
Fail)
Alarm Delay (SP The period (in seconds) the input must be not at the required setpoint before a Setpoint Deviation alarm is
0 to 172800 0 I s1(D)
Deviation) generated.
Alarm Group (PV Fail) Specifies which alarm group the PV Fail alarm is sent. 0 to 500 0 N f1(G)
Alarm Group (Setpoint
Specifies which alarm group the Setpoint Dev alarm is sent. 0 to 500 0 N s1(G)
Deviation)
0 or 1
Alarm Sent (PV Fail) Indicates if the PV fail alarm has been sent to the alarm group. 0 = Not sent 0 N f1(K)
1 = Sent
0 or 1
Alarm Sent (SP
Indicates if the setpoint deviation alarm has been sent to the alarm group. 0 = Not sent 0 N s1(K)
Deviation)
1 = Sent
0 or 1
Clear Alarm Enable
Specifies whether the process variable fail clear alarm is enabled. 1=Enabled 0 N f1(C)
(PV Fail)
0=Disabled
0 or 1
Clear Alarm Enable
Specifies whether the setpoint deviation clear alarm is enabled. 1=Enabled 0 N s1(C)
(SP Deviation)
0=Disabled

IQ4 Modules
Text
Comms
Clear Alarm Delay
v3.50 or greater. The period (in seconds) the PV Fail alarm must be cleared before the clear alarm is generated. 0 to 172800 0 I f1(d)
(secs) (PV Fail)
Clear Alarm Delay v3.50 or greater. The period (in seconds) the Setpoint Deviation alarm must be cleared before the clear alarm
0 to 172800 0 I s1(d)
(secs) (SP Deviation) is generated.
Specifies a range above and below the setpoint where the loop output is not changed when the process variable
Deadband is in that range e.g. 5 specifies 2.5 above and 2.5 below the setpoint. When enabled it filters out minor plant 0 to +1020 0 I B
disturbances and noise.
0 or 1
Default Action Indicates when the loop fail action type 2 is taken. 0 O a
1 = action type 2
If Sensor Fail = 0 -1020
The value to which the loop will control if the process variable fails, and the fail action is set to use the default to +1020
Default Value 0 I E
level. If Sensor Fail = 1 or 2
0 to 100
Derivative The derivative part of the output. -25 to +25 0 N d
The amount (in minutes) to multiply the result of the gain multiplied by the rate of change of error by to
Derivative Time (mins) -1020 to +1020 0 I T
produce the derivative part of the output.
0 or 1
Enabled (PV Fail) Specifies whether the process variable fail alarm is enabled. 1 = Enabled 0 I f1(E)
0 = Disabled
0 or 1
Enabled (SP Deviation) Specifies whether the setpoint deviation alarm is enabled. 1 = Enabled 0 I s1(E)
0 = Disabled
The proportional gain of the loop, defines the way the loop responds to changes in the process variable. For
Gain -1020 to +1020 0 I G
IQ4 v3.0 and greater controllers when set to 0 the loop uses integral only control.
0, 6 and 7
0 = No loop alarm
In Alarm Indicates an alarm condition has been present for longer than its delay time and the alarm is enabled. 0 N !
6 = SP Deviation alarm
7 =PV Fail alarm
Integral The integral part of the output. -100 to +100 0 N i
Integral Time (mins) The time (in minutes) after which the integral term is added to the output. -1020 to +1020 0 I I
0 or 1
Manual Select Specifies whether manual level is imposed on the loop. 0 I A
1 = Manual level

IQ4 Modules
Text
Comms
Manual Level The loop’s manual override setpoint. -1020 to +1020 0 I L
Occupied Setpoint The loop’s occupied setpoint. Used when setpoint select is set to '1'. 20
-10 to +10 20
0 I O
Output The output of the module. -1020 to +1020 0 O D
20 20
Process Variable The measured value being controlled. -10 to +10 0 I P
0 or 1
PV Fail Alarm State The status of the Process Variable Fail alarm. 0=No alarm 0 O f1(S)
1=Alarm
1 to 600
Reschedule Time The interval in seconds between loop output calculations. 0 N R
0 = Disabled
0 to 4
0 = Default PV
1 - Default OP
Sensor Fail The action that is taken when the process variable for a loop is invalid. 0 N F
2 - Stay in default OP,
3 - Freeze output
4 - No action
Setpoint Deviation The maximum loop error that can be reached before a setpoint deviation alarm is generated. -1020 to +1020 0 I V
0 or 1
0 = Unoccupied
Setpoint Select Specifies whether the loop controls to the occupied or unoccupied setpoint. 0 I S
Setpoint
1 = Occupied Setpoint
0 or 1
SP Deviation Alarm
The status of the Setpoint Deviation alarm. 1 = Alarm 0 O s1(S)
State
0 = No Alarm
The length of time in seconds since the PV alarm state started. 0 to +1020 0 N f1(T)
(PV Fail)
The length of time in seconds since the SP deviation alarm state started. 0 to +1020 0 N s1(T)
(SP Deviation)
Unoccupied Setpoint The loop’s unoccupied setpoint. Used when setpoint select is set to '0'. -1020 to +1020 0 I U

IQ4 Modules
A1.17 IQ4 Network Modules

Network modules are used to store the parameters specific to the type of physical network being used.
IQ4 BACnet Application Network Modules
IQ4 BACnet IP Network Modules
IQ4 BACnet MSTP Network Modules
IQ4 BACnet Network Modules
IQ4 Ethernet IP Network Modules
IQ4 Lan Network Modules
IQ4 Type 8 (Modbus Serial) Network Module
IQ4 Type 14 (Wallbus) Network Modules
IQ4 Type 15 (M-bus) Network Modules
IQ4 Type 16 (Trend Client) Network Modules
IQ4 Type 17 (Trend Serial) Network Modules
IQ4 Type 19 (Modbus IP) Network Modules
A1.17.1 IQ4 BACnet Application Network Modules
Module Identifier n6
Size in brIQs 0
IQ4/BACnet only
BACnet application network modules store the parameters specific to the BACnet network.
A1.17.1.1 IQ4 BACnet Application Network Module Parameters
The modules include the following parameter common to most modules: 'Label', - see Common IQ4 Module Parameters, plus the following:
Text
Comms
v3.50 or greater. The time – in seconds – that the IQ4 must wait before unilaterally ending the
Backup Failure Timeout 0 to 65535 30 N f
backup or restore procedure.

IQ4 Modules
Text
Comms
0, 1, 2, 3, 4, 5,
6
0 = Idle
1 = preparing
for backup
2 = preparing
for restore
Backup_and_Restore_state v3.50 or greater. The status of the BACnet backup/restore. 3 = performing 0 N t
a backup
4 = performing
a restore
5 = backup
failure
6 = restore
failure
0 or 1
BACnet Backup/Restore v3.50 or greater. Enables/Disables the IQ4’s BACnet backup and restore functionality. 1 = Enabled 0 N b
0 = Disabled
BACnet Backup Preparation v3.50 or greater. The amount of time in seconds that the IQ4 might remain unresponsive after the
0 to 65535 0 N u
Time response to a start backup procedure has been sent.
0 or 1
BACnet Writable Properties v3.50 or greater. Enables/Disables the ability to write to the IQ4’s parameters over BACnet. 1 = Enabled 0 N w
0 = Disabled
v3.50 or greater. Specifies whether the Change_Of_State_Count and Elapsed_Active_Time 0 or 1
BO State Count And Active
properties on the BACnet AO & BO Objects are enabled. 0 = Enabled 0 N c
Time Properties
Must be disabled if a BTL compliant strategy is required. 1 = Disabled
Not in v3.50 or greater. For earlier versions specifies whether the controller's BTL compliance is
enabled. When enabled the controller's schedule offset modules are read only over BACnet. 0 or 1
BTL Compliance Changes are still possible when access is over the Trend network. 1 = Enabled 1 N c
For the controller to be BTL compliant this option must be enabled i.e. Schedule Offset modules 0= Disabled
read only over BACnet.
0 or 1
Create/Delete Service v3.50 or greater. Enables the Create/Delete service. 1 = Enabled 0 N C
0= Disabled

IQ4 Modules
Text
Comms
The controller's address on the BACnet network. It can be specified manually or can be calculated
Calculated
Device Instance automatically using the following formula: 1 to 4194303. N i
automatically
Device Instance = (LAN Number*1000) + Local node
00:00:00 to
Last_Restore_Time v3.50 or greater. The last time the strategy was restored using a BACnet restore. 00:00:00 N m
23:59:59
0 or 1
Specifies whether the device instance is calculated automatically or manually specified. It is not
Manual Device Instance 1 = Manual 0 N A
recommended that this parameter is changed.
0= Auto
0 or 1
Specifies whether the object name prefixes are added to the object names when viewed from
Object Name Prefixes 1 = Added 1 N j
BACnet.
0= Not added
8 to 20-
BACnet Services Password v3.50 or greater. The password required to authorise use of the IQ4's BACnet services. - N K
character string
0 or 1
Cold & Warm Restart Service v3.50 or greater. Enables/Disables the IQ4's Cold & Warm Restart Service. 1 = Enabled 0 N r
0 = Disabled
0 or 1
1 = Message
Send I-am Specifies whether the IQ4 sends and 'I am' message on the BACnet network when it powers up. sent 0 N S
0 = Message
not sent
A1.17.2 IQ4 BACnet IP Network Modules
Size in brIQs 0
IQ4/BACnet only
BACnet IP network modules store the parameters specific to the BACnet IP network.

IQ4 Modules
A1.17.2.1 IQ4 BACnet IP Network Module Parameters

Text
Comms
0 or 1
1 =
Enables/disables the controller's BBMD functionality. The BBMD functionality will not work with devices that use
BBMD Enabled Enabled 0 N e
automatic IP addressing (DHCP), and under such condition should be left disabled.
0=
Disabled
BDT Remote IP A list of up to 32 devices addresses. Each item in the list is the IP address of a BBMD device the other side of a router IP All 32 set to
N bn(B)b
Address which can forward broadcast messages. Address 0.0.0.0
BDT Remote IP All 32 set to
A list of up to 32 subnets masks that correspond to the remote IP addresses specified in the BDT Remote IP Address. N b(n)s
Subnet Address 0.0.0.0
All 32 set to
BDT remote UDP A list of up to 32 UDP ports that correspond to the remote IP addresses specified in the BDT Remote IP Address. 0 to 65535 N Bn(E)
47808
The controller's network number on the BACnet IP network. Only a single network number is allowed on a single
Network Number 0 to 65534 0 N n
Ethernet subnet, and must be unique on the Ethernet network.
UDP Port The UDP port used by the controller to send messages to other Trend system devices on the BACnet IP network. 0 to 65535 47808 N E
A1.17.3 IQ4 BACnet MSTP Network Modules
Size in brIQs 0
BACnet MSTP network modules store the parameters specific to the BACnet MS/TP network.
A1.17.3.1 IQ4 MSTP Network Module Parameters
The modules include the following parameters common to most modules: ‘Label’ and 'Disable Module', - see Common IQ4 Module Parameters, plus the following:
Text
Comms
Alarm Group Specifies which alarm group to which network alarms generated on the MS/TP network are sent. 0 to 500 1 N g

IQ4 Modules
Text
Comms
Specifies the controller's network number on the BACnet MS/TP network. Can be specified automatically or
BACnet
manually. When 'Manual BACnet network number' is set to 'Automatic' it is read only and is set to the number LAN
network 0 to 65534 N n
specified by the 'Lan Number' parameter. When 'Manual BACnet network number' is set to 'Manual' it can be set number
number
to the required value. It is strongly recommended that this value is set automatically.
0,1,2,3,4
0=Disabled
Baud Rate Specifies the controller's baud rate on the MSTP network. 76800 should be selected for best system performance. 1=9600
76800 N b
Value Baud rates below 38400 are not recommended for large systems, performance problems are likely. 2=19200
3=38400
4=76800
Any ASCII character
Lan Label User-friendly label for the LAN. It can be up to 30-characters long. - N k
except \/(){};,:
The LAN number of the controller on the Ethernet network. It is the same as the Address module's 'Local Lan'
Lan Number parameter. Changing the value of this parameter will change the value of the Address module's 'Local Lan' 1, 4 to 119 excluding 10. 9 N N
parameter.
The MAC address of the controller on the BACnet MS/TP network. Can be specified automatically or manually.
MAC Address When 'Manual MAC address' is set to 'Automatic' it is read only and set to '0'. When 'Manual MAC address' is 0 to 255 0 N M
set to 'Manual' it can be set to the required value. It is strongly recommended that this value is set automatically.
Max Info
Specifies the maximum number of frames a node can send per rotation of the MS/TP token. 0 to 65534 20 N f
Frames
The maximum address polled to create a network on the MS/TP trunk. It is not recommended that this parameter
Max Master 1 to 127 127 N O
is changed from the default.
User-friendly label for the module. It can be up to 30-characters long. If the controller is to be accessed by an Any ASCII character
Module Label Blank N $
SDU-xcite only 20-characters can be used. except \/(){};,:
Manual
Specifies whether the controller's address on the BACnet MS/TP network is determined manually or 0 or 1
BACnet
automatically. If determined automatically the address is set to the number specified by the 'Lan Number' 1 = Automatic 1 N l
network
parameter. 0 = Manual
number
Specifies whether the controller's MS/TP MAC address determined manually or automatically. If determined 0 or 1
Manual MAC
automatically the MAC address is set to '0'. It is strongly recommended that this be left as automatic. Setting to 1 = Automatic 1 N L
address
some other MAC address will compromise system performance. 0 = Manual

IQ4 Modules
Text
Comms
0, 1, or 2
Specifies whether messages on the MSTP network require a low-level acknowledgement. When set to
0 = Unconfirmed
Service Class 'Confirmed' the device will require a low-level acknowledgement, when set to 'Unconfirmed' an 0 N a
1= Unused
acknowledgement is not required.
2 = Confirmed
None, LAN, IWRK
NONE = No Trend
network available on the
MSTP network
LAN = The Trend network
Trend Mode IQ4 v3.2 or greater. Determines how the associated MSTP network operates in a Trend system. - N T
on the MSTP network is a
LAN
IWRK = The Trend
network on the MSTP
network is an internetwork
A1.17.4 IQ4 BACnet Network Modules
Size in brIQs 0
BACnet Network modules store the parameters specific to the BACnet network.
A1.17.4.1 IQ4 BACnet Network Module Parameters
Text
Comms
0 or 1
Enables/disables the controller's BBMD functionality. The BBMD functionality will not work with devices that
BBMD Enabled 1 = Enabled 0 N e
use automatic IP addressing (DHCP), and under such condition should be left disabled.
0= Disabled
Specifies whether the controller's BTL compliance is enabled. When enabled the controller's Schedule Offset
0 or 1
modules are read only over BACnet. Changes are still possible when access is over the Trend network.
BTL Compliance 1 = Enabled 1 N c
For the controller to meet the requirements of the BACnet testing laboratory WSPCert this option must be
0= Disabled
enabled i.e. Schedule Offset modules read only over BACnet.

IQ4 Modules
Text
Comms
BDT Remote IP A list of up to 32 devices addresses. Each item in the list is the IP address of a BBMD device the other side of a All 32 set to
IP Address N bn(B)b
Address router which can forward broadcast messages. 0.0.0.0
BDT Remote A list of up to 32 subnets masks that correspond to the remote IP addresses specified in the BDT Remote IP All 32 set to
IP Address N b(n)s
Subnet Address. 0.0.0.0
BDT remote UDP A list of up to 32 UDP ports that correspond to the remote IP addresses specified in the BDT Remote IP Address. 0 to 65535 All 32 set to 47808 N Bn(E)
The controller's address on the BACnet network. It can be specified manually or can be calculated automatically
Calculated
Device Instance using the following formula: 1 to 4194303. N I
automatically
0 or 1
Manual Device
Specifies whether the device instance is calculated automatically or manually specified. 1 = Manual 0 N A
Instance
0= Auto
The controllers BACnet network number. Only a single network number is allowed on a single Ethernet subnet,
Network Number 0 to 65534 0 N n
and must be unique on the Ethernet network.
0 or 1
1 = Message
Send I-am Specifies whether the IQ4 sends and 'I am' message on the BACnet network when it powers up. sent 0 N S
0 = Message
not sent
UDP Port The UDP port used by the controller to send messages to other Trend system devices on BACnet. 0 to 65535 47808 N E
A1.17.5 IQ4 Ethernet IP Network Modules
Size in brIQs 0
Ethernet IP network modules store the parameters specific to the Ethernet network.

IQ4 Modules
A1.17.5.1 IQ4 Ethernet IP Network Module Parameters

Text
Comms
IQ4 v2.30 or greater. Specifies the alarm group to which all Ethernet IP network alarms are sent. If set
Alarm Group 0 to 500 0 N g
to zero alarms only sent to connected supervisor devices.
The IP address of the each of the DNS servers being used. IQ4 Max 5 addresses, IQ4 max 4 addresses.
DNS Servers 1 IP addresses separated
If Addressing Mode is Obtain Automatically this parameter is obtained automatically from DHCP 0.0.0.0 N N
to 5 by a ';'.
server if one is available. If a DHCP server is not available, it is not set.
Email The password required by the email server that the IQ4 is to use to send email. Only set up if required
0 - N A
Password by server.
Email Port IQ4 v3.30 or greater. The TCP port used by the email server. 0 to 65535 25 N O
0, 1, 2, 3
0 = No security
Email Security IQ4 v3.30 or greater. The security protocol used by the email server. 1 = SSL 3 N q
2 = STARTTLS
3 = Auto Secure
Email Server
The IP address or host name of the email server that the controller is to use to send email. IP Address - N L
Address
0, 1, 2, 3
Email Min 0 = TLS V1.0
The minimum version for email TLS.
TLS version 1 = TLS V1.1 0 N -
2 = TLS V1.2
3 = TLS V1.3
Email The user name required by the email server that the controller is to use to send email. Only set up if
0 - N o
Username required by server.
0 or 1
Enable Default
Specifies whether the controller will respond to its default hostname. 0 = Enabled 0 N h
Hostname
1 = Disabled
Ethernet MAC The MAC address of the controller. - Set by manufacturer N M
The controller’s host name. It provides a network communication name for the controller. It is separate Any 7 bit ASCII
from the Identifier. It must be unique on the network, and must not be greater than 15-characters in character in the range
Hostname Blank N $
length. It can include 'A'-'Z', 'a'-'z', '0'-'9', '-', or '_'. It must start with a character in the range 'A'-'Z', 'a'- 'A'-'Z', 'a'-'z' or '0'-'9'
'z' and must not end with '-' or '_'. plus '-' or '_'.

IQ4 Modules
Text
Comms
0 or 1
Ignore Email IQ4 v3.30 or greater. Causes IQ4 to ignore the SSL security certificate should normally be enabled,
0 = Disabled 0 N j
Certificate but can be disabled if the IQ4 has problem authenticating the certificate.
1 = Enabled
The IP address of the controller. The IP address for each controller must be unique to avoid address
clashes. IP address in the following ranges should not be used:
IP Address Reason
127.x.x.x.x Reserved for loopback.
The non-masked part of the IP address cannot be all 1’s or 0’s e.g. if IP
Non-masked part of IP
address is 1.2.x.x and subnet mask is 255.255.0.0 then x.x. cannot be either 128.1.1.3 if
address
255.255 or 0.0. Addressing mode = 0
IP Address 224.0.0.0 to IP Address Obtained N I
Reserved for multicast. automatically if
239.255.255.255
Addressing mode = 1
Addresses 240.0.0.0 to
Reserved for experimentation and development.
247.255.255.255
x.x.x.255 Reserved for broadcast.
If Addressing Mode is Obtain Automatically this parameter is obtained automatically from DHCP
server if one is available. If a DHCP server is not available, it automatically negotiated with other
devices on the segment.
1 or 2
IP Addressing 1 = Obtained
Specifies whether the IP settings are obtained automatically or specified manually. 1 N P
Mode automatically
2 = Specified Manually
A 30-character label for the controller's LAN. It is used by supervisor and tool to display a label for the
Any ASCII character
LAN Label LAN. It is only used when the controller is acting as the INC on the network. It is recommended that Blank N k
except \/(){};,:
it is set to the same value in all controllers on the same LAN.
IQ4 v3.2 or greater. The LAN number of the controller on the Ethernet network. It is the same as the
LAN Number Address module's 'Local Lan' parameter. Changing the value of this parameter will change the value 1, 4 to 119 excluding 10. 20 N N
of the Address module's 'Local Lan' parameter.
Redirect to IQ4 v3.30 or greater. Redirects any web server request made to the http web server to the https web 0 or 1
1 N n
HTTPS server. 1 = redirect
Remote 20 IP addresses
All 20 set to 0.0.0.0 N b
Device 1 to 20 separated by a ';'.

IQ4 Modules
Text
Comms
The IP address or host name and subnet mask of each of the other devices that are to form part of the
internetwork on Ethernet, allowing the internetwork to span routers. Known as the remote devices
table.
The table must be placed in all devices on the network and include the details of at least two devices 20 masks separated by a
All 20 set to 0.0.0.0 N s
from each subnet to be linked by the internetwork. For increased reliability details of additional devices ';'.
should be specified. If automatic addressing is being used the devices must be specified using host
names, and if manual addressing is being used the list should contain the devices with the lowest IP
addresses.
255.255.255.255 if
The IP address of the router to which messages are sent if the destination address is not on the local
Addressing mode = 0
subnet. It should be set to the IP address of a router on the same subnet as the controller.
Router 1 IP Address Obtained N R
automatically if
server if one is available. If a DHCP server is not available, it is not set
Addressing mode = 1
IQ4 v3.60 or greater. The port number used by the IQ4 for the SSH communications required for vCNC
Secure Access
connection. It should only be changed if the default is not suitable, i.e. already being used on the 0 to 65535 22 N T
Port
network for something else.
Secure Web 0 to 65535
Server Port IQ4 v3.30 or greater. The port number used by the IQ4 for its HTTPS web server. 0 = HTTPS web server 0 N e
Number OFF
When selected the controller's standalone mode is turned ON. When operating in standalone mode the
0 or 1
Standalone controller will not attempt to find other controllers on the Ethernet network. This option should only
0 = Enabled 0 N a
Mode Enabled be selected if the controller is the only one on the Ethernet network, or there is a requirement for it not
1 = Disabled
to communicate with other controllers. For IQ4NCs it is permanently disabled.
255.255.0.0 if
The subnet mask of the controller. The subnet mask must be the same for all devices not separated by
Addressing mode = 0
routers that are to build LANs or an internetwork. This ensures that they are on the same subnet.
Subnet Mask - Obtained N S
automatically if
server if one is available. If a DHCP server is not available, it is set to 255.255.0.0.
Addressing mode = 1

IQ4 Modules
Text
Comms
None, LAN, IWRK
NONE = No Trend
network available on the
Ethernet network
LAN = The Trend
IQ4 v3.2 or greater. Determines how the associated Ethernet network operates in a Trend system. It
Trend Mode network on the Ethernet - N T
can be set to:
network is a LAN
IWRK = The Trend
network on the Ethernet
network is an
internetwork
The UDP port of the controller. This defines the UDP port used by the controller to send messages to
UDP Port other Trend system devices. To construct an internetwork, the all the devices must use the same UDP
0 to 65535 57612 N E
(inet) port. If you are restricted to using one subnet, but wish to have separate sites on that subnet (i.e. more
than one internetwork), then you can set different UDP port numbers for each group of devices.
0 to 65535
Web Server
The Ethernet port number used by the IQ4 for its HTTP web server. 0 = HTTP web server 80 N w
Port Number
OFF
The IP address of the each of the WINS servers being used. IQ4 Max 5 addresses. IQ4 Max 5 addresses,
WINS Servers IQ4 max 4 addresses. IP addresses separated
0.0.0.0 N W
1 to 5 If Addressing Mode is Obtain Automatically this parameter is obtained automatically from DHCP by a ';'.
server if one is available. If a DHCP server is not available, it is not set.

IQ4 Modules
Text
Comms
Specifies whether the controller the controller's XML server is turned ON. The table below describes
the options:
Option Description
XML interface 0 to 3
The controller's XML Web services are disabled.
OFF 0 = XML interface OFF
Basic IQ 1 = Basic IQ
XML Server The controller's XML Web services are enabled.
authentication authentication 0 N u
Enabled
IQ4 v3.1 or greater only. The controller's XML Web services are enabled, and 2 = Write authentication
Write
writes to the controller using the XML web services are protected using 3 = Read/Write
authentication authentication
HMAC_MD5 security.
IQ4 v3.1 or greater only. The controller's XML Web services are enabled, and
Read/Write
read from and writes to the controller using the XML web services are protected
authentication
using HMAC_MD5 security.
A1.17.6 IQ4 LAN Network Modules
Size in brIQs 0
LAN network modules store the parameters specific to the Trend current loop network.
A1.17.6.1 IQ4 IQ LAN Network Module Parameters
The modules include the following parameters common to most modules: ‘Label’ and 'Disable Module', - see Common IQ4 Module Parameters, plus the following:
Text
Comms
Alarm IQ4 v2.30 or greater. Specifies the alarm group to which all Trend current loop LAN alarms are sent. If
0 to 500 0 N g
Group set to zero alarms only sent to connected supervisor devices.
0 or 1
Specifies whether the controller will negotiate its baud rate with other controllers on the network, or use
Autobaud 1 = Enabled 1 N A
the baud rate specified by the Baud Rate parameter.
0 = Disabled

IQ4 Modules
Text
Comms
Specifies the baud rate of the LAN. 2 or 3 Set by
Baud Rate Not available if Autobaud is enabled. When Autobaud is enabled the Baud Rate parameter is read only, 2=9600 hardware N b
and will be negotiated with other devices on the network. 3=19200 switch.
A 30-character label for the controller's LAN. It is used by supervisor and tool to display a label for the Any ASCII character except
LAN Label Blank N k
LAN. It is only used when the controller is acting as the INC on the network. \/(){};,:
IQ4 v3.2 or greater. The LAN number of the controller on the Ethernet network. It is the same as the
LAN
Address module's 'Local Lan' parameter. Changing the value of this parameter will change the value of 1, 4 to 119 excluding 10. 20 N N
Number
the Address module's 'Local Lan' parameter.
None, LAN, IWRK
NONE = No Trend network
available on the current loop
Trend LAN = The Trend network on the
IQ4 v3.2 or greater. Determines how the associated current loop network operates in a Trend system. - N T
Mode current loop is a LAN
IWRK = The Trend network on
the current loop is an
internetwork
A1.17.7 IQ4 Type 8 (Modbus Serial) Network Module
Module Identifier n
Size in brIQs 0
Type 8 (Modbus Serial) Network modules store the parameters specific to the Modbus serial connection.

IQ4 Modules
A1.17.7.1 IQ4 Type 8 (Modbus Serial) Network Module Parameters

The modules include the following parameters common to most modules: 'Label' - see Common IQ4 Module Parameters, plus the following:
Text
Comms
0, 1, 2, 3, 4, 5,
6, 7
0 = 1200
1 = 2400
2 = 4800
Baud Rate The baud rate of the Modbus. 4 N b
3 = 9600
4 = 19200
5 = 38400
6 = 57600
7 = 115200
0, 1, 2
Read only – Indicates the status of the selected port
0 =
Communication Unavailable – the channel is in use by another Resource
Unavailable 0 N t
Channel Status Available – the channel is available
1 = Available
In Use – the channel is being used by this Network Module.
2 = In Use
0, 1, 2
Communication 0 = Not Used
The port used for the Modbus communications. 0 N v
Channel 1 = RS232
2 = RS485
Interframe Pause The pause in ms between frames sent by the controller on the Modbus Network. 500 0 N i
0, 1
0 = Modbus
Modbus The communication mode used by the Modbus connection. It should be set to the value required by the other devices
RTU 1 N m
Communication Mode (slave device(s)) on the Modbus RTU and ASCII slaves should not be mixed on the same network port.
1 = Modbus
ASCII
0, 1, 2
0- None
Parity The parity required for the Modbus. 2 N P
1 - Odd
2 - Even
Re-tries The number of times to attempt a Modbus request before a communication error is reported. 0, 1, 2, 3 3 N r
Timeout The maximum wait time in ms for a response frame from a Modbus request. 0 to 65535 50 N T

IQ4 Modules
A1.17.8 IQ4 Type 14 (Wallbus) Network Modules

Module Identifier n
Size in brIQs 0
They store the parameters specific to the Wallbus network.
A1.17.8.1 IQ4 Type 14 (Wallbus) Network Module Parameters
Text
Comms
Local Address The address of the IQ4 on the Wall-bus network. 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 1 N a
The communication channel used by the Wallbus network, always
Communication Channel 4 4 N v
‘4’.
0, 1, 2
0 = Unavailable, the channel is in use by another
Communication Channel
The status of the selected communication channel. Resource 0 N t
Status
1 = Available, the channel is available
2 = In Use – the channel is being used by this module.
A1.17.9 IQ4 Type 15 (M-bus) Network Modules
Module Identifier n
Size in brIQs 0
Type 15 (M-bus) Network modules store the parameters specific to the M-bus connection.

IQ4 Modules
A1.17.9.1 IQ4 Type 15 (M-bus) Network Module Parameters

The modules include the following parameters common to most modules: 'Label' - see Common IQ4 Module Parameters, plus the following:
0, 1, 2, 3, 4, 5, 6, 7
0 = 300
1 = 600
2 = 1200
Baud Rate The baud rate of the M-bus. 3 = 2400 0 N b
4 = 4800
5 = 9600
6 = 19200
7 = 38400
Read only – Indicates the status of the selected port 0, 1, 2
Unavailable – the channel is in use by another Resource 0 = Unavailable
Communication Channel Status 0 N t
Available – the channel is available 1 = Available
In Use – the channel is being used by this Network Module. 2 = In Use
0, 1, 2
0 = Not Used
Communication Channel The port used for the M-bus communications. 0 N v
1 = RS232
2 = RS485
Interframe Pause The pause in ms between frames sent by the controller on the M-bus network. 0 to 500 100 N i
Retries The number of times to attempt a M-bus request before a communication error is reported. 0, 1, 2, 3 3 N r
Timeout The maximum wait time in seconds for a response frame from a M-bus request. 0 to 65535 10 N T
A1.17.10 IQ4 Type 16 (Trend Client) Network Modules
Module Identifier n
Size in brIQs 0
They are used by the IQ4 to communicate with its USB Local Engineering Port and RS232 Local Supervisor Port, they are always Network modules 10 and 11 (n10 and n11). n10 is
used for the USB Local Engineering Port and n11 is used for the RS232 Local Supervisor Port.

IQ4 Modules
Because they are used by the IQ4 they are created as required and cannot be edited. Both n10 and n11 are present in all variants of IQ4, however n11 is not present in /XNC variants but
will be created if the RS232 Local Supervisor Port is to be used as a supervisor port. If the port is to be used by the XNC to interface with a 3rd party system a Type 17 (XNC Serial)
Network module should be used.
A1.17.10.1 IQ4 Type 16 (Trend Client) Network Module Parameters

0 or 6
n11=1
Communication Channel The communication channel used by the module. 1 = Serial N v
n10=6
6 = USB
0, 1, 2
0 = Unavailable, the channel is in use by another Resource
Communication Channel Status The status of the selected communication channel. 0 N t
1 = Available, the channel is available
2 = In Use – the channel is being used by this module.
A1.17.11 IQ4 Type 17 (Trend Serial) Network Modules
Module Identifier n
Size in brIQs 0
IQ4 v3.30 or greater, only available on IQ4…/…/XNC/..s.
They store the parameters specific to the Serial port used by the interface.
A1.17.11.1 IQ4 Type 17 (Trend Serial) Network Module Parameters
Text
Comms
1 or 3
Communication Channel The number of the COM port assigned to the Serial port. 1 = RS232 1 N v
3 = RS485
Communication Channel The type of serial interface the port is to use. It is automatically set to match the
RS232 or RS485 - N m
Mode hardware of the port to which it is connected.

IQ4 Modules
Text
Comms
0, 1, 2
0 = Unavailable, the channel is in use by
Communication Channel another Resource
The status of the selected communication channel. 0 N t
Status 1 = Available, the channel is available
2 = In Use – the channel is being used by
this module.
A1.17.12 IQ4 Type 19 (Modbus IP) Network Modules
Module Identifier n
Size in brIQs 0
IQ4 Type 19 (Modbus IP) Network Module store the parameters specific to the Modbus IP connection. A Type 19 (Modbus IP) Network module is required for each Modbus device
the IQ4 is to communicate with.
Note: A maximum of 10 Type 19 (Modbus IP) Network modules can be added to the controller's strategy.
A1.17.12.1 IQ4 Type 19 (Modbus IP) Network Module Parameters
The modules include the following parameters common to most modules: 'Label' and 'Disable Module'- see Common IQ4 Module Parameters, plus the following:

0,1
Connection Status The connection status 0 = Disconnected 0 N t
1 = Connected
IP Address or Hostname The IP address or host name of the Modbus device. Valid IP address or host name 0.0.0.0 N I
TCP Port The TCP port used for the Modbus communications. 0 to 65535 502 N E

IQ4 Modules
A1.18 IQ4 NTD Modules

Module Identifier f
Size in brIQs 30
IQ4/BACnet only
NTD (Non-Trend Device) modules are used to enable IC comms between IQ controllers and NTDs.
A1.18.1 IQ4 NTD Module Parameters
Text
Comms
1 to 119 excluding
Address The Trend network address of the NTD. 0 N L
addresses 2, 3, and 10
Optional 30-character label for the NTD which allows it to be identified either uniquely, or as part of a group. It Any ASCII character
Attribute 2 Blank N F
is used in conjunction with the identifier, and the other attributes. except \/(){};,:
Attribute 3 Blank N G
Attribute 4 Blank N H
is used in conjunction with the identifier, and the other attributes. . except \/(){};,:
Attribute 5 Blank N I
Attribute 6 Blank N J
Attribute 7 Blank N K
Device The device instance of the BACnet device the NTD is to communicate with.
0 to 4194302 0 N d
Instance Note: If the device instance is not specified you must specify both the network number and MAC address.
Any ASCII character
Identifier 30-character label for the NTD. It is used as the first controller attribute for text communications. Blank N D
except \/(){};,:
1 to 119 excluding
Lan The Trend LAN number of the NTD. 0 N N
Any ASCII character
Model Name The model name of the BACnet device the NTD is to communicate with. - N m
except \/(){};,:

IQ4 Modules
Text
Comms
Network
The network number of the BACnet device the NTD is to communicate with. 0 to 65534 0 N n
Number
0 or 1
Type Indicates the type of NTD. 0 = Not used 1 N Y
1 = BACnet

IQ4 Modules
A1.19 IQ4 OSS Modules

Each Time Schedule has an OSS module and a set of occupation times associated with it. The OSS module can be applied to heating and/or cooling. It provides a self-adaptive routine
that learns the characteristics of the building by monitoring and comparing the outside air temperature against the inside air temperature, and the heating/cooling medium temperature.
The module derives a dynamic thermal (Physical) model of the building which it uses to calculate the time that the heating/cooling should be switched on before the occupation of the
building to achieve the desired temperature by the start of occupation (the optimum start time). It also calculates when the heating/cooling can be turned off before the end of occupation
without diverging from comfortable condition until after the end of occupation (the optimum stop time).
The module offers an alternative 'Statistical' algorithm. This derives a statistical relationship between the measured temperatures and the start and stop times. This reduces errors due to
any mismatch between the actual building and the physical model that may occur
The Adaptation Inhibit parameter enables the loss and gain time constants to be prevented from being updated.
A1.19.1 IQ4 OSS Module Parameters
following:
Text
Comms
Specifies the algorithm used by the module to predict the warm up and cool down times. Can be set to 'Physical' or
0 or 1
'Statistical'. When set to 'Physical' it will use the traditional algorithm used in all previous IQ controllers. When set to
Algorithm Type 1=Statistical 0 N Y
'Statistical' it will use a new algorithm which calculates the OSS times based on measurement of the start and stop
0=Physical
timing, and typically offers better accuracy.
Cooldown Limit The maximum period (in minutes) the heating/cooling can be turned off before the end of occupation (the cool down
0 to 1439 0 I D
(minutes) period).
Set between optimum stop time and the end of occupation. It can be used to provide an input to other modules by
Cooldown State 0 or 1 000 O d
An estimate of temperature of the cooling medium (e.g. supply air temperature) that is used if an actual measurement
Cooling Average
of the temperature is not available.
Medium -1020 to +1020 0 N c1(M)
This value is overwritten by the 'Cooling Medium Temperature' parameter. Therefore, there is no point in specifying
Temperature
it.
For the 'Physical' model this is the length of time (in hours) it would take the building temperature to achieve the
medium temperature.
Cooling Gain Time
For the 'Statistical' model this is the length of time (in hours) it would take the building temperature cool down by 1 -100 to +100 5 I c1(G)
Constant
Deg C on a typical day.
This parameter only needs to be specified if cooling is selected.
Cooling Medium
The temperature of the cooling medium. If set to 0 the value of the Cooling Medium Temp parameter will be used. -1020 to +1020 8 I c1(A)
Temperature

IQ4 Modules
Text
Comms
Cooling OSS
Specifies the temperature that must be achieved before occupation is read. -1020 to +1020 0 I c1(S)
Setpoint
Cooling Start The maximum variance (in DegC) of the actual temperature from the setpoint that is acceptable at the start of
-100 to +100 1 I c1(T)
Elevation occupation. This parameter only needs to be specified if cooling is selected.
Cooling Stop The maximum variance (in DegC) of the actual temperature from the setpoint that is acceptable at the end of
-100 to +100 1 I c1(P)
Elevation occupation. This parameter only needs to be specified if cooling is selected.
An estimate of temperature of the heating medium (e.g. supply air temperature) used if an actual measurement of the
Heating Average
temperature is not available.
Medium -1020 to +1020 70 N h1(M)
This value is overwritten by the 'Heating Medium Temperature' parameter. Therefore, there is no point in specifying
Temperature
it.
For the 'Physical' model this is the length of time (in hours) it would take the building temperature to achieve the
medium temperature.
Heating Gain Time
For the 'Statistical' model this is the length of time (in hours) it would take the building temperature warm up by 1 Deg -100 to +100 10 I h1(G)
Const (hours)
C on a typical day.
This parameter only needs to be specified if heating is selected.
Heating Medium
The temperature of the heating medium. If set to 0 the value of the Heating Ave Medium Temp parameter will be used. -1020 to +1020 70 I h1(A)
Temperature
Heating OSS
Specifies the temperature that must be achieved before occupation is read. -1020 to +1020 0 I h1(S)
Setpoint
Heating Start The maximum variance (in DegC) of the actual temperature from the setpoint that is acceptable at the start of
-100 to +100 -1 I h1(T)
Elevation occupation. This parameter only needs to be specified if heating is selected.
Heating Stop The maximum variance (in DegC) of the actual temperature from the setpoint that is acceptable at the end of
-100 to +100 -1 I h1(P)
Elevation occupation. This parameter only needs to be specified if heating is selected.
Inside Temp Specifies the inside temperature. 0 to 100 0 I I
The length of time (in hours) it would take the building temperature to equalise with the outside air temperature at the
Loss Time
end of occupation. It is continually adjusted by the OSS module to ensure accuracy at start and stop times. It should be 0 to 100 5 I L
Constant (hours)
set to a reasonable value to reduce the OSS module’s learning time.
0 or 1
Mode Current OSS mode. 0 = Heating 0 O m
1 = Cooling
Non Occupied Set between occupation stop and optimum start time. It can be used to provide an input to other modules by linking it
0 or 1 0 O n
State to the required modules.

IQ4 Modules
Text
Comms
Set between start of occupation and optimum stop time. It can be used to provide an input to other modules by linking
Occupied State 0 or 1 0 N o
Set between start of occupation, and end of occupation. It can be used to provide an input to other modules by linking
OTP State 0 or 1 0 O t
Set between optimum start time and optimum stop time (used for switching loops to occupied setpoint). It can be used
OSS State 0 or 1 0 O s
to provide an input to other modules by linking it to the required modules.
Outside Temp Specifies the outside air temperature. 0 to 100 0 I O
Optimum On Time The current calculated optimum ON time. 00:00 to 48:00 00:00 N N
Optimum Off Time The current calculated optimum OFF time. 00:00 to 48:00 00:00 N F
20 20
Start Time Error The current start time error in minutes. -10 to +10 - N E
‘Physical’
algorithm
0 to 2
0 = Passive
1 = Heating
2 = Cooling
‘Statistical’
algorithm
0 to 6
0 = Passive
State The current state of operation of the OSS module. 1 = Heating On 0 N S
2 = Cooling
On
3 = Heating
start
4 = Heating
stop
5 = Cooling
start
6 = Cooling
stop
Stop Time Error The current stop time error in minutes. -1020 to +1020 - N e

IQ4 Modules
Text
Comms
Valid module
IQ4 v3.30 or greater. Time Schedule module used the OSS to determine occupation status. OSS
number.
Time Schedule Note: In previous firmware versions, the Time Schedule module used is determined by module number. This can be module I Z
0 = use module
replicated by setting this parameter to ‘0’. number
number
Warm Up Limit The maximum period (in minutes) the heating/cooling can be turned on before the start of occupation (the warm up
0 to 1439 360 I W
(minutes) period).
Set between optimum start time and the start of occupation. It can be used to provide an input to other modules by
Warmup State 0 or 1 0 O w

IQ4 Modules
A1.20 IQ4 Page Modules

Module Identifier p
Size in brIQs 4
Page modules store the essential information for each strategy page used to display the modules in IQSET or other tools. IQSET defines a page module for each strategy page created
in IQSET.
A1.20.1 IQ4 Page Module Parameters

Parent Not used - - - -

IQ4 Modules
A1.21 IQ4 Plot Modules

Plot modules enable a connectable output value or status to be recorded at defined times to produce a graph or table of values.
IQ4 COV Plot Modules
IQ4 Synchronised Plot Modules
IQ4 Periodic Plot Modules
IQ4 Triggered Plot Modules
A1.21.1 IQ4 COV Plot Modules
Module Identifier P
Size in brIQs 12 plus log memory (5 bytes per record) IQ3 is limited to 100,000 logging records (e.g. 100 off 1000 point logs).
COV Plot modules only record a value when the value differs from the last logged value by more than the 'COV Increment' parameter. If connected to a digital value, the ‘COV
Increment’ parameter is not used and the value will be recorded whenever it changes. They record a value when the IQ4 is restarted or when the module is enabled to provide an initial
value to which the COV can be applied.
A1.21.1.1 IQ4 COV Plot Module Parameters
following:
Text
Comms
Alarm Group Specifies the alarm group to which the BBUF alarm is sent. 0 to 500 0 N g
0 or 1
Data Precision The precision of the recorded value. 0 = Single precision 0 N D
1 = Double precision
Last Notify Record The value of the ‘Total Record Count’ parameter when the last BBUF alarm was sent. 0 to 232-1 0 N l
0 or 1
Indicates whether the log is full i.e. the number of records has reached the value specified by
Log Enable 0 = Disabled 1 I E
the ‘Number of Records’ parameter.
1 = Enabled
Indicates whether the log is full i.e. the number of records has reached the value specified by 0 or 1
Log Full 0 N l
the ‘Number of Records’ parameter. 1 = Log full
Specifies the number of records after which the buffer level alarm is sent (e.g. if set to 200 the
Notification Threshold 0 to 232-1 0 N n
alarm would be sent every 200 values i.e. 200, 400, 600 etc).
Number of Records Specifies the number of records the module can store before the first is overwritten. 1 to 1000 1000 N N

IQ4 Modules
Text
Comms
Record Count The number of records recorded so far. 0 to Number of Records 0 N R
Records Since Last
The number of records since the last notification was sent. 0 to 232-1 0 N r
Notification
-1020 to +1020 for analogue outputs.
Source The value the plot module is recording. 0 I S
0 or 1 for digital outputs.
0 or 1
Stop When Full Specifies whether logging will stop when the log is full. 0 = Disabled 0 N W
1 = Enabled
Time of Last Date and time in the format yyyy-
The date and time the last BBUF alarm was sent. 0 N b
Notification mm-dd&Thh:mm:ss
Date and time in the format yyyy-
Time of Last Record The date and time of the last record. 0 N T
mm-dd&Thh:mm:ss
Indicates the total number of records that have been taken since the module started recording
Total Record Count 0 to 232-1 0 N C
values.
A1.21.2 IQ4 Synchronised Plot Modules
Module Identifier P
Synchronised plot modules are the traditional Trend plot; they can log up to 1000 records of the value at fixed intervals (from 1s up to 24 hours).
Synchronised plots on should not be used if BTL compliance is required.
A1.21.2.1 IQ4 Synchronised Plot Module Parameters
following:
Text
Comms
Last Notify
The value of the Total Record Count when the last BBUF alarm was sent. 0 to 232-1 0 N l
Record

IQ4 Modules
Text
Comms
Notification Specifies the number of records after which the buffer level alarm is sent (e.g. if set to 200 the alarm would be sent every
0 to 232-1 0 N n
Threshold 200 values i.e. 200, 400, 600 etc).
Number of
Specifies the number of records the module can store before the first is overwritten. 1 to 1000 1000 N N
Records
0 to 9
0 = 1 hour
1 = 15 minutes
2 = 24 hours
3= 1 minute
The interval between logs. The interval between logs. For controllers that store 96 values per plot only 1 hour, 15 minutes,
Period 4 = 5 minutes 0 N P
24 hours, and 1 minute intervals are available. For controllers that can store 1000 values per plot all intervals are available.
5=10 minutes
6=20 minutes
7=30 minutes
8=6 hours
9=1 second.
0 to Number of
Record Count The number of records recorded so far. 0 N R
Records
Records Since
Last The number of records since the last notification was sent. 0 to 232-1 0 N r
Notification
-1020 to +1020 for
analogue outputs.
0 or 1 for digital
outputs.
Date and time in
Time of Last the format yyyy-
Notification mm-
dd&Thh:mm:ss
Date and time in
The date and time of the last record. 0 N T
Record mm-
dd&Thh:mm:ss
Total Record
Indicates the total number of records that have been taken since the module started recording values. 0 to 232-1 0 N C
Count

IQ4 Modules
A1.21.3 IQ4 Periodic Plot Modules
Module Identifier P
Periodic Plot modules enable the value of a parameter to be recorded at the interval defined by the Interval input; so, the interval may change. Periodic plots can save memory since
more data can be recorded when important events are occurring, and less when there is nothing significant to record. After the maximum number of values is stored, the first will be
overwritten. There is an option to enable a Log Full output and cease logging, until the plot buffer is cleared (Stop When Full option).
A1.21.3.1 IQ4 Periodic Plot Module Parameters
following:
Text
Comms
Last Notify
Record
0 or 1
Log Enable Enables/Disables the recording of information. If BTL compliance is required, this must not be linked to another module. 0 = Disabled 1 I E
1 = Enabled
Indicates whether the log is full i.e. the number of number of records in the plot has reached the value specified by the 0 or 1
Log Full 0 O F
Number of Records parameter. 1 = Log full
Interval Specifies the interval in seconds between one sample and the next. 0 to 86400 0 I I
0 to 232-1 0 N n
Number of
Records
0 to Number of
Records
Records Since
Notification

IQ4 Modules
Text
Comms
-1020 to +1020 for
analogue outputs.
0 or 1 for digital
outputs.
0 or 1
Stop When Specifies whether logging will stop when the log is full. When enabled logging will stop when the number of values logged
0 = Disabled 0 N W
Full =number of records. When disabled, the log will wrap round when full overwriting the oldest value.
1 = Enabled
Date and time in
Notification mm-
dd&Thh:mm:ss
Date and time in
Record mm-
dd&Thh:mm:ss
Total Record
Indicates the total number of records that have been taken since the module started recording values. . 0 to 232-1 0 N C
Count
A1.21.4 IQ4 Triggered Plot Modules
Module Identifier P
Triggered Plot modules enable the value of a parameter to be recorded when the trigger input occurs (changes from 0 to 1). This allows recording of events at a specific time that could
otherwise be missed by synchronised or periodic plots. Triggered plotting maximises use of plot memory as it only records when required. After the maximum number of values is
stored, the first will be overwritten. There is an option to enable a Log Full output and cease logging, until the plot buffer is cleared (Stop When Full option).
Triggered plots should not be used if BTL compliance is required.

IQ4 Modules
A1.21.4.1 IQ4 Triggered Plot Module Parameters

following:
Text
Comms
Last Notify
Record
0 or 1
Log Enable Enables/Disables the recording of information. If BTL compliance is required, this must not be linked to another module. 0 = Disabled 1 I E
1 = Enabled
Indicates whether the log is full i.e. the number of number of records in the plot has reached the value specified by the 0 or 1
Log Full 0 O F
Number of Records parameter. 1 = Log full
0 to 232-1 0 N n
Number of
Records
0 to Number of
Records
Records Since
Notification
-1020 to +1020 for
analogue outputs.
0 or 1 for digital
outputs.
0 or 1
Stop When Specifies whether logging will stop when the log is full. When enabled logging will stop when the number of values logged
0 = Disabled 0 N W
Full =number of records. When disabled, the log will wrap round when full overwriting the oldest value.
1 = Enabled
Stop When
Full

IQ4 Modules
Text
Comms
Date and time in
Notification mm-
dd&Thh:mm:ss
Date and time in
Record mm-
dd&Thh:mm:ss
Total Record
Count
Trigger Input The value that triggers recording. Recording occurs when the value changes from 0 to 1 not when it changes from 1 to 0. 0 or 1. 0 N G
Trigger Output An output that Indicate the state of the trigger input. 0 or 1 0 O O
A1.22 IQ4 Schedule Offset Modules
Module Identifier H
Size in brIQs
OTP Schedule Modules 19
OSS Schedule Modules 21
They allow items to be turned off and on at times that are offset from the specified time schedule module’s occupation times. There are two different types of Schedule Offset module:
occupation time profile, and optimum start/stop. IQSET treats them as the same module with the Type parameter defining the modules type.
OTP
This type of Schedule Offset module is controlled by the occupation times set in the associated time schedule module + the start and stop deviation specified on the Schedule Offset
module itself. (I.e. the output is on during the occupation period, and off during the unoccupied period subject to the application of the start and stop deviations).
OSS
This type of Schedule Offset module is controlled by the optimum start and stop times calculated by the OSS module. (I.e. the output is on during the OSS on period, subject to the
application of the start and stop deviations).

IQ4 Modules
A1.22.1 IQ4 Schedule Offset Module Parameters

following:
Text
Comms
Specifies either the output level used during cool down, or the analogue node from which it is read.
Cooldown Value -1020 to +1020 0 I L
Note: This parameter is not used for OTP Schedule Offset modules.
Either specifies the output level used when the Schedule Offset is in manual control, or the analogue node from which
Manual Level -1020 to +1020 0 I M
it is read.
Manual Select The digital node that forces the module to manual control. 0 or 1 0 I A
Non-Occupied
Either specifies the output level used during non-occupation, or the analogue node from which it is read -1020 to +1020 0 I N
Value
Occupied Value Specifies either the output level used during occupation, or the analogue node from which it is read. S -1020 to +1020 0 I O
OSS/OTP
The Time Schedule module from which the schedule’s occupation times are taken. 1 to 100 0 N Z
Connection
Output The analogue node to which the module writes its output (D). -1020 to +1020 0 O D
The difference (in minutes) between the start time specified in the time schedule module and the start time used by
Start Deviation -1440 to +1440 0 I T
the schedule offset.
1 to 4
1 = Occupied
2 = Warmup
State The current state of the OSS module. 0 N S
3 = Cooldown
4 = Non-
occupied
The difference (in minutes) between the stop time specified in the time schedule module and the start time used by
Stop Deviation 1440 to +144 0 I P
the schedule offset.
1 to 2
Type The type of schedule offset module to be used. 1 = OSS 2 N Y
2 = OTP
Specifies either the output level used during warm up, or the analogue node from which it is read.
Warm Up Value -1020 to +1020 0 I W
Note: This parameter is not used for OTP Schedule Offset modules.

IQ4 Modules
A1.23 IQ4 Sensor Type Modules

Module Identifier Y
Size in brIQs 12
A Sensor Type module is a module within a controller that stores information about a certain type of sensor. They are used by the sensor and lookup function modules to convert the
input signal into engineering units.
A1.23.1 IQ4 Sensor Type Module Parameters
The number of leading digits before the decimal point. This parameter is not available when ‘Analogue Value’ is
Exponent -7 to +7 0 N E
specified as the input type.
I<n>
Inputs 1 to The input points specify the actual value of the electrical input signal from the sensor, or the analogue input value from
-1020 to +1020 0 N Where <n> =
20 the lookup function module.
input number
0 to 4
0 = Volts (V)
The type of input signal. It should be set to match the hardware-input channel connected to the sensor. If the input is 1 = Thermistor
from a lookup function module, it should be set to Internal Analogue Value. Thermistor input channels may use either Volts (V)
Input Type Thermistor Volts or Thermistor (KOhms). Normally the sensor characteristics will be given in kilohms so Thermistor 2 = Current 0 N -
(KOhms) should be used. However, Thermistor Volts enables a sensor’s characteristics to be produced by measuring (mA)
voltage values at the input terminals and entering them in the thermistor volts table. 3 = Thermistor
Ohms (Kohm)
4 = Analogue
Specifies the lowest rated value of the sensor (the out of limits alarm lower limit). Not used if the module is used for
Lower Limit -1020 to +1020 0 N L
lookup function module.
Number The sensor type module. 1 to 99 1 N -
Number of
The number of points used in the conversion table. 2 to 20 Blank N P
Points
O<n>
The output points specify the value of the output for the corresponding input point, or the analogue input value from the
Outputs 1 to Where <n> =
lookup function module. Up to twenty can be defined. -1020 to +1020 0 N
20 output
Note: An output point must be defined for each input point.
number
(Read only) The method used to interpret the reading from the sensor. It is set to 'Characterise' which allows a sensor’s
Scaling characteristics to be defined by specifying up to twenty scaling points between which it interpolates. This provides characterise characterise N S
higher accuracy than the other scaling types for non-linear characteristics. It is also used for Lookup Function modules.

IQ4 Modules

Specifies the highest rated value of the sensor (the out of limits alarm upper limit). Not used if the module is used for
Upper Limit -1020 to +1020 0 N U
Note: When entering the values in the Input (X) and Output (Y) boxes the value of the input points (X) must increase, not decrease.

IQ4 Modules
A1.24 IQ4 States Category Modules

Module Identifier y
Size in brIQs -
States Category modules enable several different states and associated text to be defined. They are used to specify the available states for modules that use multistate valued, e.g. Type
1 (Multistate) time Schedule modules.
Each State Category module can have up to 20 different states each represented by State sub-module which defined the state, and the associated text.
A1.24.1 IQ4 States Category Module Parameters
The parameters of a States Category module are made up of those from the main States Category module, and the parameters of the sub-modules that define the states (States sub-
modules).
A1.24.1.1 Main States Category Module Parameters
The main States Category Modules include the following parameter common to most modules: 'Label' - see Common IQ4 Module Parameters, plus the following parameter:

Number of States The number of states the module is to define. 1 to 20 1 N N
A1.24.1.2 States Sub-Module Parameters
Each of the States Category module contains up to 20 State sub-modules (state 1 is State sub-module 1, state 2 is State sub-module 2 etc.) that define the text associated with each state.
Each State sub-module has the following parameters:

State Text The text associated with the state. 0 to 30-characters. Any ASCII character except \/(){};,: 0 - N T<n>

IQ4 Modules
A1.25 IQ4 Time Modules

Module Identifier T
Size in brIQs 38
The Time module stores information about the current date and time.
A1.25.1 IQ4 Time Module Parameters
Text
Comms
10 Minute Pulse The pulse generated every 10 minutes. 0 or 1 0 O n
15 Minute Pulse The pulse generated every 15 minutes. 0 or 1 0 O o
20 Minute Pulse The pulse generated every 20 minutes. 0 or 1 0 O a
24 Hour Pulse The pulse generated every 24 hours. 0 or 1 0 O t
30 Minute Pulse The pulse generated every 30 minutes. 0 or 1 0 O q
5 Minute Pulse The pulse generated every 5 minutes. 0 or 1 0 O l
6 Hour Pulse The pulse generated every 6 hours. 0 or 1 0 O s
60 Minute Pulse The pulse generated every 60 minutes. 0 or 1 0 O r
00.00 to 23.59
hh.mm
Current Time The current time in hours and minutes. 00:00 O c
hh = 00 to 23
mm = 00 to 60
Day The current day of the month. 1 to 31 1 O D
Day Bit 5 The least significant bit of the 3-bit expression of Weekday. Set to 1 on Monday, Wednesday, Friday, and Sunday. 0 or 1 0 O u
Day Bit 6 The middle bit of the 3-bit expression of Weekday. Set to 1 on Tuesday, Wednesday, Saturday and Sunday. 0 or 1 0 O v
Day Bit 7 The most significant bit of the 3-bit expression of Weekday. Set to 1 on Thur, Fri, Sat and Sun. 0 or 1 0 O w
Day of year The day of the year. 1 to 266 1 O e
Daylight End The day of the month at which daylight stops. When the ‘DST Source’ parameter is set to ‘1’ (Auto) read only and calculated
1 to 31 0 I E
Day using the ‘Time zone’ parameter.
Daylight End The month when daylight saving stops. When the ‘DST Source’ parameter is set to ‘1’ (Auto) read only and calculated
1 to 12 1 I T
Month using the ‘Time zone’ parameter.

IQ4 Modules
Text
Comms
0 to 3
0 = no change
Daylight Hours The length of time (hours) by which the time is changed for daylight saving. When the ‘DST Source’ parameter is set to
1 = 1 hour 0 I G
Change ‘1’ (Auto) read only and calculated using the ‘Time zone’ parameter.
2 = 2 hours
3 = 3 hours
0 or 1
Daylight
Indicates whether the IQ4’s time has been adjusted for daylight saving. 1 = Time 0 O F
Savings Applied
adjusted
Daylight
Savings Offset The length of time (minutes) by which time is changed for daylight saving 0 to 240 0 O V
(Mins)
0 to 31
Daylight Start The day of the month when daylight saving starts. When the ‘DST Source’ parameter is set to ‘1’ (Auto) read only and
0 = No daylight 0 I S
Day calculated using the ‘Time zone’ parameter.
saving
Daylight Start The month when daylight starts. When the ‘DST Source’ parameter is set to ‘1’ (Auto) read only and calculated using the
1 to 12 1 I O
Month ‘Time zone’ parameter.
Determines whether the IQ4 calculates daylight saving based on the value of the ‘Time zone’ parameter (Auto) or uses 0 or 1
‘Daylight Start Day’, ‘Daylight Start Month’, ‘Daylight Stop Day’, and ‘Daylight Stop Month’ parameters to determine 0 = Manual
DST Source 0 N h
when daylight saving starts and stops, and the ‘Daylight Hours Change’ parameter to determine the amount the time Entry
changes (Manual). 1= Auto
Hours The hours part of the current time. 0 to 23 0 O H
Any ASCII
Label 30-character user-friendly label for the module. character except Blank N $
\/(){};,:
Minutes The minutes part of the current time. 0 to 59 0 O N
Minutes Past
The number of minutes elapsed since midnight. 0 to 1439 0 O m
Midnight
Minute Pulse The pulse generated every minute. 0 or 1 0 O k
1 to 12
Month The current month. 0 O M
1= January
Monthly Pulse The pulse generated every month. 0 or 1 0 O d
Page Specifies the strategy page containing the module. 0 to 255 0 N p

IQ4 Modules
Text
Comms
Seconds The seconds part of the current time. 0 to 59 0 O C
The pulse generated every second.
Second Pulse 0 or 1 0 O j
Note: The 1 second pulse (second pulse) should only be connected to event driven modules).
Time Server IQ4 v3.30 or greater. The IP address or hostname of the NTP server. Read only when the ‘Time Server Address Source’ Valid IP address
0.0.0.0 N g
Address parameter is ‘1’. or hostname
0 or 1
Time Server IQ4 v3.30 or greater. Only available if the ‘Time source’ parameter is set to ‘1’ (NTP). Specifies whether the address of
1 = DHCP 0 N f
Address Source the NTP server is to be obtained from the DHCP server, or entered manually in the ‘Time Server Address’ parameter.
0 = Manual
0, 1
Time Source IQ4 v3.30 or greater. The source of the IQ4s time. Can be set to use the IQ4’s RTC (internal) or an NTP server (NTP) 0 = Internal 0 N I
1 = NTP
0 or 1
Time Master Enables/disables the timemaster function 1 = Enabled 0 N A
0 = Disabled
IQ4 v3.30 or greater. The time zone in which the IQ4 is located. Used to determine the ‘Daylight Start Day’, ‘Daylight
Start Month’, ‘Daylight Stop Day’, ‘Daylight Stop Month’ and ‘Daylight Hours Change’ parameters when the ‘DST List of time Not
Time zone N Z
Source’ parameter is set to ‘1’ (Auto), and the ‘UTC Offset (Mins)’ parameter. Must be specified if an NTP server is to be zones used
used.
UTC Offset
The length of time (minutes) the IQ4’s local Time zone time differs from the UTC time -780 to + 780 0 N U
(Mins)
Weekly Pulse The pulse generated every week. 0 or 1 0 O u
1 to 7
Weekday The current day of the week. 1 O W
1 = Monday
X Co-ordinate Specifies the horizontal position of the module on a strategy page. 0 to 255 0 N x
Y Co-ordinate Specifies the vertical position of the module on a strategy page. 0 to 255 0 N y
Year The last two digits of the current year. 0 to 99 0 O Y
Yearly Pulse The pulse generated every year. 0 or 1 0 O z

IQ4 Modules
A1.26 IQ4 Time Schedule Modules

Time Schedule modules define the occupation time profile for the controller.
IQ4 Analogue Time Schedule Modules
IQ4 Digital Time Schedule Modules
IQ4 Multistate Time Schedule Modules
Note: In versions of firmware earlier than 3.1 the Time Schedule module was known as the Time Zone module, and other products may still use this terminology. In these situations,
'Time Schedule' and 'Time Zone' should be used interchangeably.
A1.26.1 IQ4 Analogue Time Schedule Modules
Module Identifier Z
Size in brIQs 566 (Includes 20 exceptions. If more exceptions are used, they require 13 brIQs each.)
v3.50 or greater. Analogue Time Schedule modules provide an analogue output that can be used to control plant at times entered by the user. Each module has a schedule of seven days
that define the occupation times for the individual days of the week. Each of these weekday profiles can contain 20 time value pairs. These pairs define a time, and a value for the output
at that time.
A1.26.1.1 IQ4 Analogue Time Schedule Module Parameters
The modules include the following parameters that are common to most modules: 'Disable Module' ‘Label’, ‘Page,’ ‘X co-ordinate’ and ‘Y co-ordinate’ - see Common IQ4 Module
Text
Comms
BACnet only
String representing a list of object property references. - - - R
references
2
Data Type Specifies the type of Time Schedule module. 2 N Y
2 = Analogue
Default Value The value output when the module is in the Null’ state. Full analogue 0 N D
Edit Timeout Internal use only - - N d
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18,
19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31
End Day The day of the month used for the end of the effective period. 0 N e
0 = Unspecified
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12.
End Month The month of the year used for the end of the effective period. 0 = Unspecified 0 N n

IQ4 Modules
Text
Comms
0, to 9999
End Year The year used for the end of the effective period. 0 N t
0 = Unspecified
Exceptions 1 Not Used. 0 0 N -
Exceptions List of Exceptions Index 1 to no max - N C
references List of object property references. - - - -
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18,
19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31.
Start Day The day of the month used for the beginning of the effective period. 0 N a
0 = Unspecified
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12.
Start Month The month of the year used for the beginning of the effective period. 0 = Unspecified 0 N m
0 to 9999
Start Year The year used for the beginning of the effective period. 0 N s
0 = Unspecified
User Level The level of the PIN required by the user to make changes to the occupation times. 0 to 100 0 N P
0 or 1
Value The status of the module. 0 = Unoccupied 0 O V
1 = Occupied
Week Day
The schedule, an array of 7 day profiles. Index 1 to 7 0 N W
Profiles
A1.26.1.2 Day of Week Sub-Module Parameters
The normal week consists of seven individual Day of week sub-modules which are identified in text comms as:
Z<n>(W<n>)
Where Z<n> specifies the Time Schedule module and W<n> specifies the day of the week sub-module (1, 2, 3, 4, 5, 6, 7 - Monday = 1). E.g. Z2(W1(*)) would read all the parameters
from Time Schedule module 2’s Monday’s day of the week sub-module.
A1.26.1.3 Day of Week TimeValue Sub-Module Parameters
Each of the Day of week sub-module contains up to 20 Day of Week TimeValue sub-modules that define a time and the Time Schedule’s occupation status at that time which are
identified in text comms as:
Z<n>(W<n>(P<n>))

IQ4 Modules
Where Z<n>W<n> specifies the Time Schedule module, and Day of week sub-module, and P<n> specifies the Day of Week TimeValue sub-module. E.g. Z2(W1(P1(*)) would read all
the parameters from the first Day of Week TimeValue sub-module from Time Schedule module 2’s Monday’s day of the week sub-module.
Day of Week TimeValue sub-module have the following parameters:
Text
Comms
Time The time of the change. 00.00 to 24.00 00.00 N T
2
Type The data type of the value 2 N Y
2 = Analogue
Value The occupation state for the change time. Full analogue 0 N V
A1.26.1.4 Exception Sub-Module Parameters
Each Time Schedule module can contain up to 50 Exception sub-modules that define when the IQ4 will operate different occupation times to those defined by the normal week which
are identified in text comms as:
Z<n>(C<n>)
Where Z<n> specifies the Time Schedule module and C<n> specifies the Exception sub-module. E.g. Z2(C1(*)) would read all the parameters from Time Schedule module 2 first
Exception sub-module.
Exception sub-modules also include the following parameter common to most modules: ‘Label’, plus the following parameters:

0, 1, 2, 3
0 = Legacy
Configuration
The use of the exception. If set to ‘0’ Legacy Configuration the ‘Use’ parameter will
BACnet Use 1 = Date or date 0 N u
be used to specify the exception’ use.
pattern
2 = Range of dates
3 = Week and Day
Valid Calendar
Calendar
The Calendar module that specifies the days the exception applies to. module instance 0 N C
Reference
number.
0, 1, 2, 3, 4, 5, 6, 7
The day of the week when the exception will apply. When set to ‘Unspecified’ any 0 = Unspecified
Day of Week - N A
day is used. Only available when ‘Use’ is set to ‘Week and Day’. 1 to 7 = Day of week
(1 = Monday)

IQ4 Modules

Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14,
15, 16, 17, 18, 19,
20, 21, 22, 23, 24,
25, 26, 27, 28, 29,
30, 31
1 to 31 = Day of
month
End Day The day of the month from which the exception stops. v3.50 or greater 1 N E
0, 1, 2, 3, 4, 5, 6, 7,
8, 9, 10, 11, 12, 13,
14, 15, 16, 17, 18,
19, 20, 21, 22, 23,
24, 25, 26, 27, 28,
29, 30, 31
1 to 31 = Day of
month
0 = Unspecified
Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12.
1 to 12 = Month of
year (1 = January)
End Month The month in which the exception stops. v3.50 or greater 1 N T
0, 1, 2, 3, 4, 5, 6, 7,
8, 9, 10, 11, 12
0 = Unspecified
1 to 12 = Month of
year (1 = January)
The year in which the exception stops. When set to ‘Unspecified’ any year is used. 0 to 9999
End Year 1 N R
Only available when ‘Use’ is set to ‘Range of Dates’. 0 = Unspecified

IQ4 Modules

IQ4 v2.0 or greater
1 to 16
The priority of the exception. In case of exception overlap, the exception with highest 16 = Highest priority
Priority 1 N P
priority level will be used. Pre IQ4 v2.0
1 to 6
6 = Highest priority
Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14,
15, 16, 17, 18, 19,
20, 21, 22, 23, 24,
25, 26, 27, 28, 29,
30, 31
1 to 31 = Day of
month
v3.50 or greater
0, 1, 2, 3, 4, 5, 6, 7,
8, 9, 10, 11, 12, 13,
Start Day The day of the month from which the exception is to apply. 1 N S
14, 15, 16, 17, 18,
19, 20, 21, 22, 23,
24, 25, 26, 27, 28,
29, 30, 31, 32, 33,
34.
0 = Unspecified
1 to 31 = Day of
month
32 = Last day of
month
33 = Every odd day
34 = Every even day

IQ4 Modules

Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12.
1 to 12 = Month of
year (1 = January)
v3.50 or greater
0, 1, 2, 3, 4, 5, 6, 7,
8, 9, 10, 11, 12, 13,
14.
0 = Unspecified
Start Month The month from which the exception is to apply. 1 to 12 = Month of 1 N O
year (1 = January)
13 = Every odd
month (January,
March, May, July,
September,
November)
14 = Every even
month (February,
April, June, August,
October, December.
0 to 9999
Start Year The year when the exception starts. When set to ‘Unspecified’ any year is used. - N Y
0 = Unspecified
0, 1, 2
0 = next (i.e. once
The use of the exception. From v3.50 this parameter is only used when the ‘BACnet
Use only) 0 N U
Use’ parameter is set to ‘0’ (Legacy Configuration).
1 = every (yearly)
2 = free (not used)
0, 1, 2, 3, 4, 5
0 = Unspecified
1 = First
The week of the month when the exception will apply. When set to ‘Unspecified’ any 2 = Second
Week of Month - N W
week is used. Only available when ‘Use’ is set to ‘Week and Day’. 3 = Third
4 = Forth
5 = Fifth
6 = Last

IQ4 Modules
A1.26.1.5 Exception TimeValue Sub-Module Parameters

Each of the Exception sub-modules contains up to 20 Exception TimeValue sub-modules that define a time and the Time Schedule module’s occupation status at that time which are
Z<n>(C<n>(D1(P<n>)))
Where Z<n>W<n> specifies the Time Schedule module, and Exception sub-module, and D1(P<n> specifies the Exception TimeValue sub-module. E.g. Z2(C2(D1(P1(*)))) would read
all the parameters from the first TimeValue sub-module of the second Exception sub-module.
Exception TimeValue sub-modules have the following parameters:

2
2 = Analogue
Value The occupation state for the change time. Full analogue 0 N V
A1.26.2 IQ4 Digital Time Schedule Modules
Module Identifier Z
Digital Time Schedule modules provide a digital output that can be used to control plant at times entered by the user. Each module has a schedule of seven days that define the occupation
times for the individual days of the week. Each of these weekday profiles can contain 20 time value pairs. These pairs define a time, and whether the Time Schedule is occupied, or
unoccupied at that time.
A1.26.2.1 IQ4 Digital Time Schedule Module Parameters
Text
Comms
BACnet only
v3.50 or greater. String representing a list of object property references. - - - R
references
0
0 = Digital

IQ4 Modules
Text
Comms
0 or 1
Default Value v3.50 or greater. The value output when the module is in the Null’ state. 0 = OFF 0 N D
1 = ON
Edit Timeout v3.50 or greater. Internal use only - - N d
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,
13, 14, 15, 16, 17, 18, 19, 20, 21, 22,
End Day v3.50 or greater. The day of the month used for the end of the effective period. 23, 24, 25, 26, 27, 28, 29, 30, 31 0 N e
0 = Unspecified
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12.
End Month v3.50 or greater. The month of the year used for the end of the effective period. 0 = Unspecified 0 N n
0, to 9999
End Year v3.50 or greater. The year used for the end of the effective period. 0 N t
0 = Unspecified
references v3.50 or greater. List of object property references. - - - -
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,
13, 14, 15, 16, 17, 18, 19, 20, 21, 22,
v3.50 or greater. The day of the month used for the beginning of the effective
Start Day 23, 24, 25, 26, 27, 28, 29, 30, 31. 0 N a
period.
0 = Unspecified
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12.
v3.50 or greater. The month of the year used for the beginning of the effective
Start Month 0 = Unspecified 0 N m
period.
0 to 9999
Start Year v3.50 or greater. The year used for the beginning of the effective period. 0 N s
0 = Unspecified
The level of the PIN required by the user to make changes to the occupation
User Level 0 to 100 0 N P
times.
0 or 1
1 = Occupied

IQ4 Modules
Text
Comms
Week Day
The schedule, an array of 7 day profiles. Index 1 to 7 0 N W
Profiles
Z<n>(W<n>)
Z<n>(W<n>(P<n>))

0
0 = Digital
0, 1, null
Value The occupation state for the change time. 0 = OFF 0 N V
1 = ON.
Z<n>(C<n>)

IQ4 Modules

0, 1, 2, 3
0 = Legacy
v3.50 or greater. The use of the exception and the ‘Use’ parameter is used instead. If Configuration
BACnet Use set to ‘0’ Legacy Configuration the ‘Use’ parameter will be used to specify the 1 = Date or date 0 N u
exception’ use. pattern
2 = Range of dates
3 = Week and Day
Valid Calendar
Calendar
v3.50 or greater. The Calendar module that specifies the days the exception applies to. module instance 0 N C
Reference
number.
0, 1, 2, 3, 4, 5, 6, 7
v3.50 or greater. The day of the week when the exception will apply. When set to 0 = Unspecified
Day of Week - N A
‘Unspecified’ any day is used. Only available when ‘Use’ is set to ‘Week and Day’. 1 to 7 = Day of week
(1 = Monday)
Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14,
15, 16, 17, 18, 19,
20, 21, 22, 23, 24,
25, 26, 27, 28, 29,
30, 31
1 to 31 = Day of
month
0, 1, 2, 3, 4, 5, 6, 7,
8, 9, 10, 11, 12, 13,
14, 15, 16, 17, 18,
19, 20, 21, 22, 23,
24, 25, 26, 27, 28,
29, 30, 31
1 to 31 = Day of
month
0 = Unspecified

IQ4 Modules

Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12.
1 to 12 = Month of
year (1 = January)
0, 1, 2, 3, 4, 5, 6, 7,
8, 9, 10, 11, 12
0 = Unspecified
1 to 12 = Month of
year (1 = January)
v3.50 or greater. The year in which the exception stops. When set to ‘Unspecified’ any 0 to 9999
End Year 1 N R
year is used. Only available when ‘Use’ is set to ‘Range of Dates’. 0 = Unspecified
IQ4 v2.0 or greater
1 to 16
The priority of the exception. In case of exception overlap, the exception with highest 16 = Highest priority
Priority 1 N P
priority level will be used. Pre IQ4 v2.0
1 to 6

IQ4 Modules

Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12, 13, 14,
15, 16, 17, 18, 19,
20, 21, 22, 23, 24,
25, 26, 27, 28, 29,
30, 31
1 to 31 = Day of
month
v3.50 or greater
0, 1, 2, 3, 4, 5, 6, 7,
8, 9, 10, 11, 12, 13,
14, 15, 16, 17, 18,
19, 20, 21, 22, 23,
24, 25, 26, 27, 28,
29, 30, 31, 32, 33,
34.
0 = Unspecified
1 to 31 = Day of
month
32 = Last day of
month
33 = Every odd day
34 = Every even day

IQ4 Modules

Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12.
1 to 12 = Month of
year (1 = January)
v3.50 or greater
0, 1, 2, 3, 4, 5, 6, 7,
8, 9, 10, 11, 12, 13,
14.
0 = Unspecified
Start Month The month from which the exception is to apply. 1 to 12 = Month of 1 N O
year (1 = January)
13 = Every odd
month (January,
March, May, July,
September,
November)
14 = Every even
month (February,
April, June, August,
October, December.
v3.50 or greater. The year when the exception starts. When set to ‘Unspecified’ any 0 to 9999
Start Year - N Y
year is used. 0 = Unspecified
0, 1, 2
0 = next (i.e. once
The use of the exception. From v3.50 this parameter is only used when the ‘BACnet
Use only) 0 N U
Use’ parameter is set to ‘0’ (Legacy Configuration).
1 = every (yearly)
2 = free (not used)
0, 1, 2, 3, 4, 5
0 = Unspecified
1 = First
v3.50 or greater. The week of the month when the exception will apply. When set to 2 = Second
Week of Month - N W
‘Unspecified’ any week is used. Only available when ‘Use’ is set to ‘Week and Day’. 3 = Third
4 = Forth
5 = Fifth
6 = Last

IQ4 Modules

Z<n>(C<n>(D1(P<n>)))

0
0 = Digital
0, 1, null
1 = ON.
A1.26.3 IQ4 Multistate Time Schedule Modules
Module Identifier Z
v3.50 or greater. Multistate Time Schedule modules provide a multistate output that can be used to control plant at times entered by the user. Each module has a schedule of seven days
that define the occupation times for the individual days of the week. Each of these weekday profiles can contain 20 time value pairs. These pairs define a time, and whether the Time
Schedule is occupied, or unoccupied at that time.
A1.26.3.1 IQ4 Multistate Time Schedule Module Parameters
Text
Comms
BACnet only
String representing a list of object property references. - - - R
references
1
1 = Multistate

IQ4 Modules
Text
Comms
Default Value The value output when the module is in the Null’ state. Multistate (Constrained by the ‘States Category module’ parameter). 1 N D
Edit Timeout Internal use only - - N d
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22,
23, 24, 25, 26, 27, 28, 29, 30, 31
End Day The day of the month used for the end of the effective period. 0 N e
0 = Unspecified
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12.
End Month The month of the year used for the end of the effective period. 0 = Unspecified 0 N n
0, to 9999
End Year The year used for the end of the effective period. 0 N t
0 = Unspecified
references List of object property references. - - - -
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22,
The day of the month used for the beginning of the effective 23, 24, 25, 26, 27, 28, 29, 30, 31.
Start Day 0 N a
period. 0 = Unspecified
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12.
The month of the year used for the beginning of the effective
Start Month 0 = Unspecified 0 N m
period.
0 to 9999
Start Year The year used for the beginning of the effective period. 0 N s
0 = Unspecified
States Category The States Category module used to provide the available
Valid States Category module instance number. 0 N g
module states for multistate values.
The level of the PIN required by the user to make changes to
User Level 0 to 100 0 N P
the occupation times.
0 or 1
1 = Occupied
Week Day Profiles The schedule, an array of 7 day profiles. Index 1 to 7 0 N W

IQ4 Modules

Z<n>(W<n>)
Z<n>(W<n>(P<n>))

1
1 = Multistate
Value The occupation state for the change time. Multistate (Constrained by the ‘States Category module’ parameter). 0 N V
Z<n>(C<n>)

IQ4 Modules
Text
Comms
0, 1, 2, 3
The use of the exception and the ‘Use’ parameter is used instead. If set to ‘0’ 0 = Legacy Configuration
BACnet Use Legacy Configuration the ‘Use’ parameter will be used to specify the exception’ 1 = Date or date pattern 0 N u
use. 2 = Range of dates
3 = Week and Day
Calendar
The Calendar module that specifies the days the exception applies to. Valid Calendar module instance number. 0 N C
Reference
0, 1, 2, 3, 4, 5, 6, 7
The day of the week when the exception will apply. When set to ‘Unspecified’
Day of Week 0 = Unspecified - N A
any day is used. Only available when ‘Use’ is set to ‘Week and Day’.
1 to 7 = Day of week (1 = Monday)
Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18,
19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31
0 = Unspecified
Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12.
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
0 = Unspecified
The year in which the exception stops. When set to ‘Unspecified’ any year is used. 0 to 9999
End Year 1 N R
Only available when ‘Use’ is set to ‘Range of Dates’. 0 = Unspecified
IQ4 v2.0 or greater
1 to 16
The priority of the exception. In case of exception overlap, the exception with 16 = Highest priority
Priority 1 N P
highest priority level will be used. Pre IQ4 v2.0
1 to 6

IQ4 Modules
Text
Comms
Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31
v3.50 or greater
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18,
19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34.
0 = Unspecified
32 = Last day of month
33 = Every odd day
34 = Every even day
Pre v3.50
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12.
v3.50 or greater
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14.
Start Month The month from which the exception is to apply. 0 = Unspecified 1 N O
13 = Every odd month (January, March, May, July,
September, November)
14 = Every even month (February, April, June, August,
October, December.
0 to 9999
Start Year The year when the exception starts. When set to ‘Unspecified’ any year is used. - N Y
0 = Unspecified
0, 1, 2
The use of the exception. This parameter is only used when the ‘BACnet Use’ 0 = next (i.e. once only)
Use 0 N U
parameter is set to ‘0’ (Legacy Configuration). 1 = every (yearly)
2 = free (not used)

IQ4 Modules
Text
Comms
0, 1, 2, 3, 4, 5
0 = Unspecified
1 = First
Week of The week of the month when the exception will apply. When set to ‘Unspecified’ 2 = Second
- N W
Month any week is used. Only available when ‘Use’ is set to ‘Week and Day’. 3 = Third
4 = Forth
5 = Fifth
6 = Last
Z<n>(C<n>(D1(P<n>)))

0
0 = Digital
0, 1, null
1 = ON.

IQ4 Modules
A1.27 IQ4 User Modules

User modules provide security for the IQ4. There are two types of User module.
IQ4 Type 0 User Modules
IQ4 Type 1 CNC User Modules
A1.27.1 IQ4 Type 0 User Modules
Module Identifier U
Size in brIQs 12
Type 0 User modules provide the controller's security. The controller’s security is enabled as soon as a user module is set up; it is therefore important that the first user module set up
has a user level of 99. If no Type 0 User modules are set up, the controller’s security is disabled.
Each module has a PIN, password, username and a user level. The user level determines what parameters a user can adjust, and what information they can see when on the controller’s
web pages. When a user attempts to make a change to a parameter in the controller that in PIN protected from a supervisor, a PIN that matches one in the controller with an associated
user level high enough to authorise the change must be sent to the controller. If it is not high enough to authorise the change, the change will not be allowed. For user to make a change
from one of the controller’s web pages, they must be logged on as a user with a user level high enough to make the change. The table below lists the user levels required for various
changes.
Task User Level

Defined in
Adjust the value of Knobs, Switches, and Time Schedules.
module.
Restricted
Prevent module details and values for Knobs, Switches, and Time Schedules, from being adjusted even if the user level required for adjustment in the module is 0.
Access
Restrict the user to only viewing Sensors, Digital inputs, Knobs, Switches, Drivers, Time Schedules, Time, Plots, and Users, and Alarm enables, Alarm levels, Label,
<80
Value, and Units on module detail pages.
View all module types and module parameters. >= 80
File upload >= 85
File download, Configuration changes, and directed text comms. >= 90
Text comms local global, or global global. >= 99
When a user first accesses the controller from a web browser, they will be logged in as a user called 'System Guest' with a user level of 100 which gives total access. However, if there
are any users set, the 'System Guest' user will only be able to view the module details and parameters. If a user called 'Guest' has been set up without a password, then the user will be
logged in as a user called 'Guest' with the level as set for the 'Guest' user. This is explained in the table below:
Configuration Description User Level
No users set up. The system will automatically log the user in as a user called 'System Guest'. 100.

IQ4 Modules
Configuration Description User Level

Type 0 User modules set up but a user called 'Guest' is not set up. The system will automatically log the user in as a user called 'System Guest'. Restricted Access
Type 0 User modules set up and the 'Guest' user has a password. The system will automatically log the user in as a user called 'System Guest'. Restricted Access
Type 0 User modules set up and the 'Guest' user has no password set up. The system will automatically log the user in as a user called 'Guest'. Defined in the 'Guest' user module
Normally a user cannot change any user module parameters (including their own password) if they have a user level less than 99. However, with the fixed function strategy option a
user may change the user module parameters of their own user module and that of any other user with a lower user level regardless of his own level.
Type 0 User modules in IQ4 v3.30 or greater controllers can be restricted to only having access to the controller's web pages (i.e. not able to authorise changes using text communications).
A1.27.1.1 IQ4 Type 0 User Module Parameters
The modules include the following parameters that are common to most modules: ‘Page’, ‘X co-ordinate’ and ‘Y co-ordinate’ - see Common IQ4 Module Parameters, plus the following:
Text
Comms
Specifies the URL of the page that is displayed when the user logs in from a web browser. This link can be to a page
of information held within the controller, or a web site that is not the IQ.
IQSET provides an easy way to specify the required URL, however the required format is described below.
If linking to a Graphical Display Page, the URL should be in the format below:
GraphIQs/<Directory Module Structure>/index.htm
Where <Directory Module Structure> is the directory module structure of the Display module that defines the page.
If linking to a Modules List Page, the URL should be in the format below:
<Module Type>.htm
Where <Module Type> specifies the type of module using its module identifier (e.g. S specifies sensor). For details
Home Page Valid URL Blank N H
of the module identifiers see the appropriate module section of this manual.
If linking to a Modules Details Page, the URL should be in the format below:
<Module Type><Module Number>.htm
Where <Module Type> specifies the type of module using its module identifier (e.g. S specifies sensor). For details
of the module identifiers see the appropriate module section of this manual.
If linking to web sites, enter the website’s URL. E.g. http://www.trendcontrols.com
0 or 1
Guest User IQ4 v3.30 or greater. Specifies that the user is the Guest user. 1 = User is the Guest 0 N g
user
Level The user level associated with the user module. 0 to 100 100 N L

IQ4 Modules
Text
Comms
0 or 1
Logged On Indicates whether user is currently logged in. 0 = Not logged on 0 O O
1 = Logged on
Any ASCII character
Password The 30-character password that must be entered by the user when logging in from a web browser. Blank N W
except \/(){};,:
The 4-digit number that must be entered by the user to log on from a display, or must be sent by a tool /supervisor
Pin 0000 to 9999 9999 N P
to authorise a change.
Timeout The length of time in minutes after which the user will be automatically logged off. 1 to 480 1 N T
Any ASCII character
User Name 30-character user-name. Blank N $
except \/(){};,:
View Alarms Specifies if the user can access alarm information when accessing the controller from a web browser. 0 or 1 1 N V
View GraphIQs
Specifies where the user can access graphical display pages when accessing the controller from a web browser. 0 or 1 1 N G
Pages
View Modules Specifies where the user can access module information when accessing the controller from a web browser. 0 or 1 1 N M
View Navigator Specifies where the user can access the navigator when accessing the controller’s graphical display pages. 0 or 1 1 N N
View Time
Specifies where the user can access time schedule information when accessing the controller from a web browser. 0 or 1 1 N Z
Schedules
IQ4 v3.30 or greater. Specifies whether the user only able to access the controllers web pages. When selected, the 0 or 1
Web Use Only 0 N w
user will not be able to authorise changes using text communications. 1 = Web use only
A1.27.2 IQ4 Type 1 CNC User Modules
Module Identifier U
Size in brIQs 12
v3.60 or greater. Type 1 CNC User modules contain the usernames and passwords that enable a client that supports secure communications to a vCNC operating in 'Secure SHH' mode
to connect to the vCNC. Each module has a password, and username which must be provided by a client to authorise the secure connection to the vCNC.

IQ4 Modules
A1.27.2.1 IQ4 Type 1 CNC User Module Parameters

The modules include the following parameters that are common to most modules: ‘Page’, ‘X co-ordinate’ and ‘Y co-ordinate’ - see Common IQ4 Module Parameters, plus the following:

0 or 1
Logged On Indicates whether user is currently logged in. 0 = Not logged on 0 O O
1 = Logged on
Password The 30-character password that must be entered by the user when logging in from a web browser. Any ASCII character except \/(){};,: Blank N W
User Name 30-character user-name. Any ASCII character except \/(){};,: Blank N $
A1.28 IQ4 Virtual CNC Modules
Module Identifier C
Size in brIQs 9
The virtual CNC modules store information about the controller's virtual CNC. Virtual CNCs enable the connection between a PC running supervisory or tool software and the Trend
network to be made over Ethernet to the virtual CNC.
Virtual CNC modules can operate in two modes, 'Secure SSH' and 'Unsecured' specified by the 'Security Mode' parameter.
A1.28.1 IQ4 Virtual CNC Module Parameters
Text
Comms
0, 1, 4 to 119 excluding 10
Address The network address of the vCNC. It must be unique on the Local LAN. 0 N A
0 = Disabled
0.0.0.0
Connected IP
IP address of connected device. 0.0.0.0 = Device not 0.0.0.0 O I
Address
connected.
10000 +
Port Number Port number of the vCNC. 1 to 32767 N P
Address
v3.60 or greater. The security mode of the vCNC. 0 or 1
Security Mode *Set to '1' when a new vCNC is created. Set to '0' if firmware is updated and vCNCs exist in the 0 = Unsecured *1 N M
strategy. 1 = Secure SSH
Socket Timeout The timeout of the CNC socket. 0 to 65535 0 N T

IQ4 Modules
Text
Comms
0 or 1
Status The connection status of the vCNC. 0 = Not connected 0 O S
1 = Connected

IQECO Modules
A2 IQECO Modules
This section describes in detail all the configuration parameters for each IQECO module. For further information, see the IQECO Configuration Reference Manual (TE201089).
IQECO Address Modules
IQECO Alarm Destination Modules
IQECO Alarm Group Modules
IQECO Alarm Route Modules
IQECO Directory Modules
IQECO Display Modules
IQECO Driver Modules
IQECO Function Modules
IQECO IC Comms Modules
IQECO Input Modules
IQECO Interface Modules
IQECO I/O Modules
IQECO Logic Modules
IQECO Loop Modules
IQECO Network Modules
IQECO NTD Modules
IQECO Sensor Type Modules
IQECO Synchronised Plot Modules
IQECO Time Modules
IQECO User Modules
Throughout this section module parameters will be referenced by their letter the E parameter would be referenced as E. The value of a module’s parameter is referenced by the parameter
letter in brackets e.g. (E) refers to the actual Value of the E parameter.
For each module, the module identifier is listed which should be used when accessing the module with text comms. There is also a description of how the module works and a table
listing all the parameters associated with it, and a description of each parameter.
The Type column of the tables in this section indicates how the parameter is defined.
Text Description
Const A module parameter that has no connection and therefore cannot be changed by running strategy, but may be changed by text comms. Can be read/write, or read only.
Source A module input that can be connected to other modules or output channels. Read/write.
Output A module output that can be connected. Read/write.
Status A module output that has no connection. Read only.
When configuring an IQECO controller only the modules used in the strategy are added to the controller’s memory. This enables the number of each type of module to be adjusted to
suit the requirements of the strategy, so long as the maximum number of modules (300) and the memory available for modules is not exceeded.

IQECO Modules
Note: There is a limit of 10 ic comms modules, and 20 Synchronised Plot modules.

A2.1 Common IQECO Module Parameters
This section provides a description of parameters common to most IQECO modules.
Text
Comms
Label User-friendly label for the module. Blank Const $
character except \/(){};,:
Sequence Step The sequence step at which the module is serviced. 0 to 200 0 Const @
Note: Although these parameters are common they may not all exist in all modules.

IQECO Modules
A2.2 IQECO Address Modules

Module Identifier R1
The Address module stores all the controllers addressing information and product specific non-network information (e.g. serial number).
A2.2.1 IQECO Address Module Parameters
Text
Comms
0, 4 to 119 excluding
Alarm Address IQECO v1.0 only. The device address to which alarms are sent. 10. 0 Const A
0 = Alarms not sent.
0, 4 to 119 excluding
Alarm Lan IQECO v1.0 only. LAN number of the device to which alarms are sent. 10. 0 Const R
0 = Local LAN
Any ASCII character
Optional 30-character label for the controller, which allows the controller to be identified either uniquely, except \/(){};,:
Attribute 2 Blank Const F
or as part of a group. It is used in conjunction with the identifier, and the other attributes. & | * ? are reserved
for special functions.
Any ASCII character
Optional 30-character label for the controller, which allows the controller to be identified either uniquely, except \/(){};,:
Attribute 3 Blank Const G
or as part of a group. It is used in conjunction with the identifier, and the other attributes. & | * ? are reserved
Build Development firmware issue used. Fixed N/A Const B
Device 0 or 1
Indicates whether the controller has been discovered by IQTool. 0 Const V
Discovered 1 = discovered
Any ASCII character
30-character label for the controller. It is sent as part of a text alarm message to identify its source and except \/(){};,:
Identifier - Const D
should be unique on the site. It is also used as controller attribute 1 for text communications. & | * ? are reserved
11 to 119 excluding
Local Address The network address of the controller. 20 Const/Output L
10.
The LAN number of the controller. It is set to the LAN number of the LAN's IQ4NC. If there is no IQ4NC 1, 4 to 119 excluding
Local Lan 20 Const/Output N
on the LAN, all IQECOs on the LAN will assume LAN 0 and form a local LAN. 10.
Memory Dependant on
The total strategy memory in the current controller (may change with firmware version etc). Fixed Const a
Capacity firmware version

IQECO Modules
Text
Comms
0 to maximum for Set by
Memory Used The amount of memory used for the current strategy Status t
controller type controller
Number of
Specifies the number of modules in the strategy. 0 to 300 0 Const >
Modules
0 or 1
Operation Status Indicates the status of the strategy. 0 = Not running 1 Const #
1 = Normal
IQECO v2.0 or greater. Determines whether the controller manages triac outputs to prevent large electrical 0 or 1
Power Managed demands on the controller. When enabled the controller powers up the triac outputs in turn to reduce the 0 = Disabled 0 Const W
risk of overloading the controller. 1 = Enabled
IQECO v2.0 or greater. Determines the mode used to determine when the raise/lower drivers calculate the
actual location of the valve.
Mode Description
Synchronisation occurs when the `Position Synchronisation` parameter in the
Disabled
raise/lower driver module is set to 1.
Synchronisation occurs when the controller is switched on, or when a soft reset
Automatic
occurs, or at midnight, for all raise/lower driver modules in the controller.
Synchronisation occurs when the controller is switched on, or when a soft reset
occurs, or at midnight plus a period calculated using the formula below:
0 to 2
Δt = Address MOD 64 x 10.5 + 0.5 s
0 = Disabled
Raise/Lower Automatic Where address MOD 64 is the remainder after integral division by 64 of the
1 = Automatic 0 Const Z
Sync mode Address Staggered controller's address. This gives a delay of between 0 seconds to 11 minutes 25.5
2 = Automatic
seconds.
Address Staggered
This ensures that all IQECO controllers in a system do not operate their valves and
dampers simultaneously.
The default setting is 'Disabled pa' this causes different behaviour to IQECO v1.0 and IQL controllers. To
ensure similar behaviour this parameter should be set as below:
IQECO 31 – Automatic
IQECO VAV P – Automatic Addressed Staggered
IQECO VAV P A – Automatic Addressed Staggered

IQECO Modules
Text
Comms
Read only. The controller's unique serial number, also shown on the product label. Set up during Any ASCII character
Serial Number - Const M
manufacture, and used to identify the controller in a service pin message. except \/(){};,:
Used to generate a service pin message. The IQECO will reset the parameter back to '0' after sending the 0 or 1
Service Pin service pin message. The service pin message can also be initiated by pressing the service pin button on 1 generates service 0 Const !
the IQECO. pin
Any ASCII character
Strategy Name 30-character name of the strategy. Blank Const H
except \/(){};,:
Strategy
Read only. The revision of the strategy. -1020 to +1020 - Const d
Revision
0,4 to 119 excluding
IQECO v2.0 or greater. The network address of the device connected to the network via the controller's 10
Supervisor Port 0 Const U
engineering port. 0 = Local device
only
Any ASCII character
Type Name The controller hardware type e.g. (IQECOVAV/../PA/, IQECOVAV/../P, or IQECO39. Fixed Const
except \/(){};,:
Version 25-character string containing controller type, firmware issue, and date Fixed - Const C
For more details of the module see the IQECO Configuration Reference Manual (TE201089).

IQECO Modules
A2.3 IQECO Alarm Destination Modules

Alarm Destination modules are used to define the destinations to which alarms can be sent. They specify where the alarms are to be sent; the format in which the alarm is sent, and can
determine when the alarms are sent.
IQECO Trend Alarm Destination Modules
A2.3.1 IQECO Trend Alarm Destination Modules
Module Identifier e
Only available in IQECO controllers with v2.0 firmware or greater.
Trend Alarm Destination modules define the destinations on the Trend network to which alarms can be sent. They specify where the alarms are to be sent; the format in which the alarm
is sent, and can determine when the alarms are sent.
A2.3.1.1 IQECO Trend Alarm Destination Module Parameters
The modules include the following parameter that is common to most modules: 'Label' - see Common IQECO Module Parameters, plus the following:
Text
Comms
Address Specifies the network address of the device to which alarms are sent. 10. 0 Const A
0 = Not used
Additional information about the module. If this parameter is not set up, IQSET will automatically set it to the
Any ASCII character
Details label. Blank Const -
except \/(){};,:
Note: This parameter does not exist in the controller it is for use in IQSET only.
0 or 1
Indicates when the module is unable to reach the specified destination. It can be used to provide an input to
Failed 0 = OK 0 Output F
other modules by linking it to the required modules.
1 = Failed
The priority level below which alarms are held. If an alarm is received above this level it, and all alarms will be
Hold Priority sent. The destination will stay open to low priority alarms for 5 seconds after the last alarm is sent. 0 to 255 0 Const/Source H
Note: Setting this to a constant prevents it being link to another module to allow linking again set to 0.

IQECO Modules
Text
Comms
0 or 1
0 = Clear alarms sent
Inhibit Clear Specifies whether the destination will send clear alarms. 0 Const C
1 = Clear alarms not
sent
Lan Specifies the LAN number of the device to which alarms are sent. 10. 0 Const N
0 = Local LAN
1 or 2
Message
The format of the alarm message. 1 = Text 0 Const M
Format
2 = Attribute
Retry The time in minutes between attempts to send the message. It should be set to 0 for autodialling to allow
0 to 32767 0 Const I
Interval continual retries.
Source The alarm route module(s) from which the destination accepts alarm. Route Modules only - Source S

IQECO Modules
A2.4 IQECO Alarm Group Modules

Module Identifier g
Alarm Group modules are used to group together alarms that are to be handled in the same way. The module generating the alarm knows to which alarm group the alarm belongs. All
alarms for a group are assigned a priority that is used by the alarm destination modules to determine when they will be transmitted.
A2.4.1 IQECO Alarm Group Module Parameters
The modules include the following parameter common to most modules: 'Label', - see Common IQECO Module Parameters, plus the following:
Text
Comms
Any ASCII
Additional information about the module. If this parameter is not set up, IQSET will automatically set it to the label.
Details character except Blank Const -
\/(){};,:
0 to 255
(Hold)
The priority of the alarm in the group. 255 = Highest 0 Source/Const P
Priority
priority
Indicates whether an alarm assigned to that module has occurred. The value is set to 1 for a single cycle of the sequence
0 or 1
table when an alarm allocated to the group occurs after that it is reset to 0. If alarms are occurring faster than once per
New Alarm 1 = Alarm 0 Output N
sequence cycle, the value will be set to 1 until one sequence cycle after the last alarm occurred It can be used to provide
0 = No alarm
an input to other modules by linking it to the required modules.
Route modules
Output The alarm route module(s) used to route alarms in the group. - Output O
only

IQECO Modules
A2.5 IQECO Alarm Route Modules

Module Identifier o
Alarm Route modules are used to specify which destination alarms in a specific group are sent. The route will pass the alarm onto the alarm destination providing the enable bit is set.
If the enable bit is not set, the alarms will be stored in the alarm log, but will not be sent.
A2.5.1 IQECO Alarm Route Module Parameters
Text
Comms
Alarm
The alarm group module(s) for which it is to route alarms. Alarm Group modules only Blank Input G
Group
Destination The alarm destination module(s) to which the module will send alarms providing the enable input is set. Destination modules only Blank Output D
0 or 1
Enable Enables/Disables the route. 0 = Disabled 1 Const/Source E
1 = Enabled

IQECO Modules
A2.6 IQECO Directory Modules

Module Identifier @
Directory modules, together with display modules, enable views to be configured in a controller for use by supervisors, commissioning tools, or display panels rather than having to set
them up separately in every device. Each module has a parent parameter, which refers to the directory module that precedes 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). When a PIN level is set, the user will need to be logged on at that PIN level or
higher to have access to the directory.
A2.6.1 IQECO Directory Module Parameters
Text
Comms
30-character user-friendly label for the module.
Label Note: If engineering directories that are to be navigated using an IQView then it is recommended that the length of Blank Const $
\/(){};,:
the label does not exceed 12-characters.
0 to 500
Parent The number of the directory module that is above this module in the hierarchy. 1 = Directory 1 (root) 0 Const R
0 = Not configured
User 0 to 99
The level of the PIN required by the user to view the module. 0 Const P
Level 0 = No PIN required

IQECO Modules
A2.7 IQECO Display Modules

Module Identifier ~
Display modules, together with Directory modules, enable views to be configured in a controller to be viewed by supervisors, commissioning tools, or display panels rather than having
to set them up separately in every device. Each module has a parent parameter, which is the directory module to which it is attached.
A2.7.1 IQECO Dynamic Display Module Parameters
Item The module parameter that is to be displayed. Valid module parameter Blank Const I
Parent The number of the directory module that is above this module in the hierarchy. 0 to 500 0 Const R
0 to 99
User Level The level of the PIN required by the user to view the module. 0 Const P
0 = no PIN required

IQECO Modules
A2.8 IQECO Driver Modules

Driver modules are used to drive HVAC equipment using output channels. They 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/OFF.
IQECO Analogue Driver Modules
IQECO Digital Driver Modules
IQECO Multi Stage Digital Driver Modules
IQECO Raise/Lower End Driver Modules
IQECO Time Proportional Driver Modules
A2.8.1 IQECO Analogue Driver Modules
Module Identifier D
The IQECO Analogue Driver module provides an analogue signal in the range 0 to 10 Vdc, or 0 to 20 mA depending on the hardware. It calculates the value of its output (l) by taking
the value of the input S, limiting it to 0 to 100, and then applying offset and range values if specified.
For IQECO v2.0 or greater the output of the module can be overridden to the value specified by the Override Status/Value parameter by setting the Override Output parameter to '1'.
A2.8.1.1 IQECO Analogue Driver Module Parameters
The modules include the following parameters that are common to most modules: 'Label', and 'Sequence Step', - see Common IQECO Module Parameters, plus the following:
Text
Comms
IQECO v2.0 or greater. The current priority level of the output being used by the driver. Normal strategy operation
Active priority writes to priority level 14. If a higher priority value comes in from BACnet, this controls the driver and the driver
0 to 16 14 Output u
level reports overridden in its Trend status (But not on BACnet). IC comms write to priority level 9, manual override
writes to level 8. '0' means the source is unconnected and there is no other active input to the array.
Any ASCII
Additional information about the driver.
Details character except - Const -
Note: This parameter is for use in IQSET only, it is not sent to the controller.
\/(){};,:
in-phase 0 to 32
The output channel to be used by the driver. 0 Const L
Channel 0=Disabled
in-phase
The value of the driver's in-phase output channel. -1020 to +1020 0 Output l
Output
0 or 1
Override IQECO v2.0 or greater. Specifies whether the output of the module is set to the value specified by the 'Override
1 = Enabled 0 Const Source ^
Output Value' parameter.
0 = Disabled
Override IQECO v2.0 or greater. The value to which the output of the module is set if the Override Output parameter is set
-1020 to +1020 0 Const/Source v
Status/Value to 1.

IQECO Modules
Text
Comms
Source The value input to the driver. -1020 to +1020 0 Const/Source S
20 20
Value The value input into the driver algorithm. -10 to +10 0 Status V
A2.8.2 IQECO Digital Driver Modules
Module Identifier D
The Digital Driver module provides an ON/OFF type output controlled by the state of a digital bit. It has a single digital source S and provides a single digital output l with an optional
antiphase output a. The state of l is determined directly by the state of S.
A2.8.2.1 IQECO Digital Driver Module Parameters
Text
Comms
IQECO v2.0 or greater. The current priority level of the output being used by the driver. Normal strategy operation
Active priority writes to priority level 14. If a higher priority value comes in from BACnet, this controls the driver and the driver
0 to 16 14 Output u
level reports overridden in its Trend status (But not on BACnet). IC comms write to priority level 9, manual override
writes to level 8. '0' means the source is unconnected and there is no other active input to the array.
Any ASCII
\/(){};,:
in-phase 0 to 32
The output channel to be used by the driver. 0 Const L
Channel 0=Disabled
in-phase
The output value of the driver. 0 or 1 0 Output l
Output
0 or 1
Override IQECO v2.0 or greater. Specifies whether the output of the module is set to the value specified by the Override
1 = Enabled 0 Const/Source ^
Output Value parameter.
0 = Disabled
Override IQECO v2.0 or greater. The value to which the output of the module is set if the Override Output parameter is set
0 or 1 0 Const/Source v
Status/Value to 1.
Source The value input to the driver. 0 or 1 0 Const/Source S
20 20

IQECO Modules
A2.8.3 IQECO Multi Stage Digital Driver Modules
Module Identifier D
Multi Stage Digital Driver modules enable the controller to sequence multiple outputs and is ideal for controlling fan speed relays or boilers. They switch several outputs ON and OFF
as the input value (Source (S)) changes between stages. The driver changes between stages as the input value passes through each integer up to the maximum number of stages determined
by the Number of Stages parameter depending on the selected switching type.
Note: The driver requires consecutive outputs channels e.g. for 3 stages it will automatically take 3 consecutive inputs station from the output specified by the 'in-phase Channel'
parameter.
The way in which the outputs are turned ON/OFF is determined by the Switching Type parameter which can be set to one of 3 modes:
Sequenced
Cascaded
Binary
Sequenced
In sequence mode, only one output is ever enabled. As the Source (S) increases, or decreases, the output turns OFF before the next output turns ON. There is a delay of 300ms when
switching between stages to ensure that only one relay is active at a time.
<0 0
>=1<2 1 ON
>=2<3 2 ON
>=3<4 3 ON
>=4<5 4 ON
>=5<6 5 ON
>=6<7 6 ON
>=7<8 7 ON
>=8 8 ON
to '3'.

IQECO Modules
<0 0
>=1<2 1 ON
>=2<3 2 ON
>=3<4 3 ON
>=4<5 4 ON
>=5<6 5 ON
>=6<7 6 ON
>=7<8 7 ON
>=8 8 ON
<0 0
>=1<2 1 ON
>=2<3 2 ON
>=3 3 ON

<0 0
>=1<2 1 ON
>=2<3 2 ON
>=3<4 3 ON
>=4<5 4 ON
>=5 5 ON
Cascaded
In cascade mode, the number of outputs turned ON increases as the Source (S) increases and decreases as the value falls. There is no time delay when switching between stages.

IQECO Modules
<0 0
>=1<2 1 ON
>=2<3 2 ON ON
>=3<4 3 ON ON ON
>=4<5 4 ON ON ON ON
to '3'.
<0 0
>=1<2 1 ON
>=2<3 2 ON ON
>=3<4 3 ON ON ON
>=4<5 4 ON ON ON ON

<0 0
>=1<2 1 ON
>=2<3 2 ON ON
>=3 3 ON ON ON

IQECO Modules

<0 0
>=1<2 1 ON
>=2<3 2 ON ON
>=3<4 3 ON ON ON
>=4<5 4 ON ON ON ON
>=5 5 ON ON ON ON ON
Binary
In binary mode, the source value (Source (S)) is converted from an analogue value to a bit array. Each bit in the array corresponds to an output and they will reflect its status. E.g.
00001010 would indicate outputs 4 and 2 ON. There is no time delay between switching outputs. The lead output parameter is not supported in this mode. The source valve can be 0 to
255.
The table below shows how the outputs are turned ON as the source (S) increases from 0 to 8.
<0 0 00000000
>=1<2 1 00000001 ON
>=2<3 2 00000010 ON
>=3<4 3 00000011 ON ON
>=4<5 4 00000100 ON
>=5<6 5 00000101 ON ON
>=6<7 6 00000110 ON ON
>=7<8 7 00000111 ON ON ON
>=8<9 8 00001000 ON
As the value increases the outputs will be turned ON accordingly. E.g. if the source value is 230 the bit array would be '11100110' and the outputs would be turned ON as shown.
>=230<231 230 11100110 ON ON ON ON ON
The table below shows some more examples of which outputs are turned on for a specific value.
>=45<45 45 00101101 ON ON ON ON

IQECO Modules
>=67<68 67 01000011 ON ON ON
>=85<86 85 01010101 ON ON ON ON
>=101<102 101 01100101 ON ON ON ON
>=134<135 134 10000110 ON ON ON
>=158<159 158 10011110 ON ON ON ON ON
>=179<180 179 10110011 ON ON ON ON ON
>=200<201 200 11001000 ON ON ON
>=255 255 11111111 ON ON ON ON ON ON ON ON
A2.8.3.1 IQECO Multi Stage Digital Driver Module Parameters
Text
Comms
The current priority level of the output being used by the driver. Normal strategy operation writes to priority
Active priority level 14. If a higher priority value comes in from BACnet, this controls the driver and the driver reports
0 to 16 14 Output u
level overridden in its Trend status (But not on BACnet). IC comms write to priority level 9, manual override writes
to level 8. '0' means the source is unconnected and there is no other active input to the array.
Additional information about the driver. Any ASCII character
Details - Const -
Note: This parameter is for use in IQSET only, it is not sent to the controller. except \/(){};,:
The output channel to be used by the driver for the first output stage. The channels for other stages are
in-phase automatically allocated the adjacent channels until each stage has a channel. 0 to 32
0 Const L
Channel Note: The driver requires consecutive outputs channels e.g. for 3 stages will automatically take 3 consecutive 0=Disabled
inputs station from the output specified by the 'in-phase Channel' parameter.
in-phase
The output value of the driver. ON ('1') when any stage is ON. 0 or 1 0 Output l
Output
Lead Output Specifies the output that is turned on at stage 1. Not supported if 'Switching Type' is binary. 1 to 8 1 Const D
Number of
The number of output stages or switching levels for the module. 0 to 8 0 Const R
Stages
The state parameter formatted as a bit string.
000000000 to
Output Status E.g. if stages 2 and 4 were ON it would be '00001010'. The bit string is read from right to left with the bit 00000000 Output F
11111111
indicating the status of stage 1 on the right. '1' indicates that a stage is on.

IQECO Modules
Text
Comms
0 or 1
Override
Specifies whether the output of the module is set to the value specified by the 'Override Value' parameter. 1 = Enabled 0 Const/Source ^
Output
0 = Disabled
Override
The value to which the output of the module is set if the Override Output parameter is set to 1. -1020 to +1020 0 Const/Source v
Status/Value
Indicates the status of the driver's output. It is an analogue value whose binary equivalent indicates the output
channels that are ON. '0' = OFF, '1' = ON. All energised outputs are added to produce an analogue value that
can be decoded to indicate which outputs are ON.
State 0 to 255 0 Output B
E.g. if stages 2 and 4 are energised the value would be '10' which could be decoded to a bit string of '00001010'.
The bit string is read from right to left with the bit indicating the status of stage 1 on the right. '1' indicates that
a stage is ON.
Specifies the way in which the outputs are turned ON/OFF. It can be set to one of 3 modes: 0, 1, 2
Switching Sequenced (One output is turned ON at a time in sequence.) 0 = 'Sequenced', 1 =
0 Const P
Type Cascaded (Outputs turned on in sequence leaving previous outputs ON (each step adds to the next).) 'Cascade', and 3 =
Binary (The input value is decoded to switch any combination of outputs.) 'Binary'
Value The value input into the driver algorithm. Not available in IQSET. -1020 to +1020 0 Status V
A2.8.4 IQECO Raise/Lower End Driver Modules
Module Identifier D
The Raise/Lower End Driver module is designed to drive a split-phase motor. It should be used for actuators with reversible action motors without any built-in positioning or where
there are no built-in limit switches, or clutches.
It provides either two digital outputs (L and A), or a single analogue output from a single analogue input S. Setting (A) to 0, selects a single analogue output.
When the driver is operating with two digital outputs, (L) will be set to 1 for period if (S) is greater than the valve position, and (A) will be set to 1 for a period if (S) is less than the
the output value will be set to 10 V to cause the associated relay module to raise for a period. If (S) is less than the valve position the output value will be set to 4 V cause the associated

IQECO Modules
The module needs to know the position of the valve. This is done either by estimating the position, by using the full-scale drive time and the sum of the amounts of time that the valve
has been driven in each direction. (E.g. If the full-scale drive time is 10 s and the valve has been driven open from the closed position for 8s and then driven closed for 3s making a total
of 5s in the open direction (8-3). The estimated value position would be 50% open because the value has been driven open for half the full-scale drive time). The valve position is verified
when the value is required to be fully closed or fully open (0% or 100) by additionally driving for the full-scale drive time in the required direction. This ensures that the valve has
reached the end stop.
Driving the valve for additional time when it is to be set to fully open or fully closed the controller will force the driver to drive the actuator closed for twice the full-scale drive time.
For v1.0 IQECO controllers this occurs at midnight. For IQECO v2.0 or greater the controllers the exact time this is determined by the 'Raise/Lower Sync mode' parameter in the address
module see the table below for details.
Mode Description
Disabled Synchronisation occurs when the `Position Synchronisation` parameter in the raise/lower driver module is set to 1.
Automatic Synchronisation occurs when the controller is switched on, or when a soft reset occurs, or at midnight, for all raise/lower driver modules in the controller.
Synchronisation occurs when the controller is switched on, or when a soft reset occurs, or at midnight plus a period calculated as per the formula below:
Δt = Address MOD 64 x 10.5 + 0.5 s
Automatic Address
Where address MOD 64 is the remainder after integral division by 64 of the controller's address. This gives a delay of between 0 seconds to 11 minutes
Staggered
25.5 seconds.
This ensures that all IQECO controllers in a system do not operate their valves and dampers simultaneously.
A2.8.4.1 IQECO Raise/Lower End Driver Module Parameters
Text
Comms
IQECO v2.0 or greater. The current priority level of the output being used by the driver. Normal strategy
Active priority operation writes to priority level 14. If a higher priority value comes in from BACnet, this controls the driver and
0 to 16 14 Output u
level the driver reports overridden in its Trend status (But not on BACnet). IC comms write to priority level 9, manual
override writes to level 8. '0' means the source is unconnected and there is no other active input to the array.
Anti-phase 0 to 32
Specifies the output channel to be used for the antiphase output channel (if used). 0 Const A
Channel 0=Disabled
Anti-phase
The antiphase output value of the driver. 0 or 1 0 Output a
Output
Any ASCII
\/(){};,:

IQECO Modules
Text
Comms
The current position of the actuator. It can be used to provide an input to other modules by linking it to the
Drive Position 0 to 100 0 Output P
required modules.
full-scale Drive The time (in seconds) taken for the actuator to move from one end stop to the other. 20 to 6500 90 Const/Source D
0 to 32
in-phase Channel The output channel to be used by the driver. 0 Const L
0=Disabled
in-phase Output The output value of the driver. 0 or 1 0 Output l
0 or 1
Invert Specifies whether the output of the driver is inverted. 1=Inverted 0 Const/Source I
0=Normal
0 or 1
IQECO v2.0 or greater. Specifies whether the output of the module is set to the value specified by the 'Override
Override Output 1 = Enabled 0 Const/Source ^
Value' parameter.
0 = Disabled
Override IQECO v2.0 or greater. The value to which the output of the module is set if the Override Output parameter is
-1020 to +1020 0 Const/Source v
Status/Value set to 1.
IQECO v2.0 or greater. When enabled the driver will drive the actuator closed for 1.5 times the full-scale drive 0 or 1
Position
time. This enables the actual actuator position to be re-calibrated regularly to ensure correct control. Once the 0 = Disabled 0 Source Z
Synchronisation
synchronisation is complete the driver will return to the required control position. 1 = Enabled
0, 1, or 2
State The current state of the raise/lower module outputs. 0 = Static, 1 = 0 Status B
Raise, 2 = Lower
A2.8.5 IQECO Time Proportional Driver Modules
Module Identifier D
The Time Proportional Driver module provides an output whose mark-space ratio is dependent on the input level. It has an analogue source S and provides a single digital output L. The
state of L is determined by the value of S, and the period time. If (S) is greater than 0, (L) will be set to 1 for a length of time. This length of time is calculated as a percentage of the
period time determined by the value of S.

IQECO Modules
A2.8.5.1 IQECO time Proportional Driver Module Parameters

Text
Comms
IQECO v2.0 or greater. The current priority level of the output being used by the driver. Normal
strategy operation writes to priority level 14. If a higher priority value comes in from BACnet,
Active priority level this controls the driver and the driver reports overridden in its Trend status (But not on BACnet). 0 to 16 14 Output u
IC comms write to priority level 9, manual override writes to level 8. '0' means the source is
unconnected and there is no other active input to the array.
Any ASCII
\/(){};,:
0 to 32
in-phase Channel The output channel to be used by the driver. 0 Const L
0=Disabled
in-phase Output The output value of the driver. 0 or 1 0 Output l
0 or 1
IQECO v2.0 or greater. Specifies whether the output of the module is set to the value specified
Override Output 1 = Enabled 0 Const/Source ^
by the Override Value parameter.
0 = Disabled
IQECO v2.0 or greater. The value to which the output of the module is set if the Override Output
Override Status/Value -1020 to +1020 0 Const/Source v
parameter is set to 1.
The length of time (in seconds) for which the output is on when the source of the module is at
Period 0 to 6500 0 Const/Source P
100%.
20 20

IQECO Modules
A2.9 IQECO Function Modules

Function modules allow mathematical calculations to be performed on several variables.
IQECO Adder/Scaler Function Modules
IQECO Analogue to Digital Function Modules
IQECO Average Function Modules
IQECO Comparator Function Modules
IQECO Divide Function Modules
IQECO Filter Function Modules
IQECO Gate Function Modules
IQECO Heat Meter Function Module
IQECO Integrator Function Modules
IQECO Hysteresis Band Function Modules
IQECO Maximum Function Modules
IQECO Minimum Function Modules
IQECO Multiply Function Modules
IQECO Power Function Modules
IQECO Proximity Function Modules
IQECO Rescale from Function Modules
IQECO Rescale to Function Modules
IQECO Sample and Hold Function Modules
IQECO Square Root Function Modules
A2.9.1 IQECO Adder/Scaler Function Modules
Module Identifier F
The Adder/Scaler Function module calculates the output (D) as the sum of two inputs (G and H) or the ratio of the two signals as per the formula:
(D) = ((E) x (G)) + ((F) x (H))
A2.9.1.1 IQECO Adder/Scaler Function Module Parameters
The modules include the following parameter that is common to most modules: 'Sequence Step', - see Common IQECO Module Parameters, plus the following:

Destination The output (D) of the module. -1020to +1020 0 Output D
Label Any ASCII character except \/(){};,: Blank Const -
Source E Specifies (E) in the calculation. -1020 to +1020 0 Const/Source E
20 20
Source F Specifies (F) in the calculation. -10 to +10 0 Const/Source F

IQECO Modules

20 20
Source G Specifies (G) in the calculation. -10 to +10 0 Const/Source G
20 20
Source H Specifies (H) in the calculation. -10 to +10 0 Const/Source H
A2.9.2 IQECO Analogue to Digital Function Modules
Module Identifier F
The Analogue to Digital Function module calculates its output by converting the value of its analogue input (G) to 8 digital outputs (a, b, c, d, e, f, g, and h).
From v2.40 firmware or greater the way in which the binary value is calculated can be determined using the ‘Mode’ parameter which can be set to one of four mode:
Binary
Binary + Overflow
Bit set
Cascade
Previous versions of firmware only support Binary mode.
Binary
Binary mode enables the conversion of 8 bit numbers (single byte).
Binary + Overflow
Binary + Overflow mode enables the conversion of multi-byte values by chaining 8 bit conversions The output (D) is calculated as the binary representation of G as 8 digital outputs in
the same way as for binary mode with the addition of an overflow output (O) that can be connected to the ‘Source’ parameter (G) of another Type 18 (Analogue to Digital Converter)
Function module operating in Binary + Overflow mode.
Bit Set
Bit set mode sets one output bit based on the value of the 'Source G' parameter. E.g. if the input is >=4 and <5 then bit 3 d) is set. All other output bits are cleared.
Bit
h 1
g 1
f 1
e 1
d 1
c 1
b 1

IQECO Modules
Bit
a 1
G 1 2 3 4 5 6 7 8
Cascade
Cascade mode sets the output bits as the input value increases.
Bit
h 1
g 1 1
f 1 1 1
e 1 1 1 1
d 1 1 1 1 1
c 1 1 1 1 1 1
b 1 1 1 1 1 1 1
a 1 1 1 1 1 1 1 1
G 1 2 3 4 5 6 7 8
A2.9.2.1 IQECO Analogue to Digital Function Module Parameters
Text
Comms
Bit 1 Bit 1 of the module's output byte. Available in IQSET as a connectable output labelled 'a'. 0 or 1 0 Output a
Bit 2 Bit 2 of the module's output byte. Available in IQSET as a connectable output labelled 'b'. 0 or 1 0 Output b
Bit 3 Bit 3 of the module's output byte. Available in IQSET as a connectable output labelled 'c'. 0 or 1 0 Output c
Bit 4 Bit 4 of the module's output byte. Available in IQSET as a connectable output labelled 'd'. 0 or 1 0 Output d
Bit 5 Bit 5 of the module's output byte. Available in IQSET as a connectable output labelled 'e'. 0 or 1 0 Output e
Bit 6 Bit 6 of the module's output byte. Available in IQSET as a connectable output labelled 'f'. 0 or 1 0 Output f
Bit 7 Bit 7 of the module's output byte. Available in IQSET as a connectable output labelled 'g'. 0 or 1 0 Output g

IQECO Modules
Text
Comms
Bit 8 Bit 8 of the module's output byte. Available in IQSET as a connectable output labelled 'h'. 0 or 1 0 Output h
0, 1, 2, 3
0 = Binary
Mode v2.40 or greater. The mode in which the module is operating. 1 = Binary + Overflow 1 Const M
2 = Bit set
3 = Cascade
v2.40 or greater. The value left over after the conversion, can be passed to another module, calculated
as below:
Binary + Overflow
O = TRUNC (G DIV 256)
Overflow -1020 to +1020 0 Output O
BitSet and Cascade modes
O = min (0,TRUNC(G – 8)) : i.e. overflow cannot go negative.
Binary
O = 0.0
Input G Specifies the analogue value to be converted. -1020 to +1020 - Const/Source G
30-character user-friendly label for the module. Any ASCII character except
Label Blank Const -
Note: This parameter is for use in IQSET only, it is not sent to the controller. \/(){};,:
20-character label for bit 1 (output a). Any ASCII character except
Label ,0-a Blank Const -
20-character label for bit 2 (output b). Any ASCII character except
Label ,1-b Blank Const -
20-character label for bit 3 (output c). Any ASCII character except
Label ,2-c Blank Const -
20-character label for bit 4 (output d). Any ASCII character except
Label ,3-d Blank Const -
20-character label for bit 5 (output e). Any ASCII character except
Label ,4-e Blank Const -
20-character label for bit 6 (output f). Any ASCII character except
Label ,5-f Blank Const -
20-character label for bit 7 (output g). Any ASCII character except
Label ,6-g Blank Const -
20-character label for bit 8 (output h). Any ASCII character except
Label ,7-h Blank Const -

IQECO Modules
A2.9.3 IQECO Average Function Modules
The Average function module calculates its output (D) as the average value of two, three, or four inputs (E), (F), (G), and (H).
A2.9.3.1 IQECO Average Function Module Parameters
Text
Comms
Destination The output (D) of the module. -1020 to +1020 0 Output D
30-character user-friendly label for the module. Any ASCII character
Label Blank Const -
Source E Specifies (E) in the calculation, divisor. -1020 to +1020 0 Const/Source E
20 20
Source F Specifies (F) in the calculation, input. -10 to +10 0 Const/Source F
20 20
Source G Specifies (G) in the calculation, input. -10 to +10 0 Const/Source G
Source G Specifies (G) in the calculation, input. -1020 to +1020 0 Const/Source H
A2.9.4 IQECO Comparator Function Modules
Module Identifier F
The Comparator Function module calculates its output (D) as 0 or 1 by comparing two inputs (E and F). When (F)>(E), (D)=1, and when (F)=<(E), (D)=0.
A2.9.4.1 IQECO Comparator Function Module Parameters

Destination The output (D) of the module. 0 or 1 0 Output D
20 20

IQECO Modules
A2.9.5 IQECO Divide Function Modules

Module Identifier F
The Divide Function module calculates its output (D) by dividing the input (G) by a value (E) and multiplying the result by another value (F). The module uses the following formula:
(D)= ((G)/(E))(F)
A2.9.5.1 IQECO Divide Function Module Parameters

20 20
20 20
20 20
A2.9.6 IQECO Filter Function Modules
Module Identifier F
The Filter Function module applies an exponential filter, filter factor, (E) to an input signal (G) to calculate the output (D). This is useful where electrical noise levels are high, and an
unfiltered signal would affect the operation of the system. The module uses the following formula:
(D)n+1= (E)x(D)n+(1-(E))(G)
A2.9.6.1 IQECO Filter Function Module Parameters
Text
Comms
Label Blank Const -
Sequence
The module's position in the sequence table. 0 to 200 0 Const -
Step
Specifies (E), filter factor, in the calculation. It is normally in the range 0 to 1 where 0 gives no filter action,
Source E -1020 to +1020 0 Const/Source E
and 1 gives an infinite filter (i.e. no change in output).

IQECO Modules
Text
Comms
Specifies (G), input, in the calculation. If it is not to be used in the calculation, it should be set to a constant
Source G -1020 to +1020 0 Const/Source G
value of 1.
A2.9.7 IQECO Gate Function Modules
Module Identifier F
The Gate Function module selects its output (D) from one of two values ((E) or (F)) depending on the state of a digital control bit (B). When (B)=1, (D)=(F), and when (B)=0, (D)=(E).
A2.9.7.1 IQECO Gate Function Module Parameters

20 20
Source B Specifies (B) in the calculation. 0 or 1 0 Const/Source B
20 20
A2.9.8 IQECO Heat Meter Function Module
Module Identifier F
IQECO v2.0 or greater.
The Heat Meter Function module enables the power used by the source to be calculated (e.g. kW). The module uses the following formula:
IF
(F)>=(E) (D)=0
ELSE
(D) = ((E)-(F))*(G)*(H)*(I)
G, H, and I are optional and if set to 'null' they are not used in the calculation.

IQECO Modules
A2.9.8.1 IQECO Heat Meter Function Module Parameters


20 20
Upper Temp E Specifies the upper temperature (E) in the calculation. -1020 to +1020 0 Const/Source E
20 20
Lower Temp F Specifies (F) in the calculation. -10 to +10 0 Const/Source F
20 20
-10 to +10
Source G Specifies (G) in the calculation. 0 Const/Source G
0=not used
1020 to +1020
Source H Specifies (H) in the calculation. 0 Const/Source H
0=not used
-1020 to +1020
Source I Specifies (I) in the calculation. 0 Const/Source I
0=not used
Examples
The module can be used in several applications e.g.
Heat meter where flow and temperatures are available
For a heat meter where the flow and temperature are available the power is calculated using the formula below:
Power = Temperature Different Supply and Return * Specific Heat Capacity of Medium * Mass Flow
If the heat meter was for heating plant the module would be used as follows:
Power kW (D) = (Supply Temp (E) – Return Temp (F)) * Flow dm3/s (G) * Mass of Flow kg/dm3(H) * Specific Heat Capacity kJ/kgK (I)
If the heat meter was for cooling plant the module would be used as follows:
Power kW (D) = (Return Temp (E) – Supply Temp (F)) * Flow dm3/s (G) * Density kg/dm3(H) * Specific Heat Capacity kJ/kgK (I)
Heat exchanger power estimation:
If the heat exchanger is for heating the power is calculated using the following formula:
Power = (Heating medium temperature – Air on temperature) * Coil duty * Valve position / 100
Power kW (D) = (Water Supply Temp (E) – Air On Temp (F)) * Coil Duty kW/degK (G) * Valve Position %(0-100)(H) * 0.01 (I)

IQECO Modules
If the heat exchanger is for cooling the power is calculated using the following formula:
Power = (Air on temperature – Heating medium temperature) * Coil duty * Valve position / 100
Power kW (D) = (Air On Temp (E) – Water Supply Temp (F)) * Coil Duty kW/degK (G) * Valve Position %(0-100)(H) * 0.01 (constant)(I)
A2.9.9 IQECO Hysteresis Band Function Modules
Module Identifier F
The Hysteresis Band Function module sets digital output state (D) to 1 if (G) rises above the value of (E)+(F/2) and then sets (D) to 0 if (G) falls below (E)-(F/2). This enables the state
of a digital node from an analogue input level.
A2.9.9.1 IQECO Hysteresis Band Function Module Parameters

Destination The output (D) of the module. Available 0 or 1 0 Output D
30-character user-friendly label for the module
Source E Specifies (E), level, in the calculation. -1020 to +1020 0 Const/Source E
20 20
Source F Specifies (F), band, in the calculation. -10 to +10 0 Const/Source F
20 20
Source G Specifies (G), input, in the calculation. -10 to +10 0 Const/Source G
A2.9.10 IQECO Integrator Function Modules
Module Identifier F
Used to convert power (kW) to energy consumption (kWh).
IF
(H)= 1 THEN (D)=0
ELSE
(D) = (D) + Delta Total
Delta Total =(G) * t/(f) where t is the between values in seconds.

IQECO Modules
The Total (D) can be reset to '0' by setting the Reset parameter (H) to '1'. If a plot module is logging the module's output, it should be triggered by the same pulse as the modules reset
H. Increases in the output that are smaller than about 1 part in 10 7 may not be shown but will still be accumulated accurately.
A2.9.10.1 IQECO Integrator Function Module Parameters

Reset (H) When set to 1 the module's output (Total (D)) is rest to '0'. 0 or 1 0 Const/Source H
Scale Factor Specifies the scale factor used to scale the total value before it is output. 0 0 Const/Source F
20 20
Source Specifies the value (G) which is to be accumulated. -10 to +10 0 Const/Source G
20 20
Total The accumulated value of the source after the scale factor (F) has been applied. 10 to +10 0 Const/Source D
Examples
Power
To integrate power in kW to energy in kWh
Source (G) = kW, Scale factor (F) = 3600, Total (D)= kWh
To integrate power in kW to energy in MWh
Source (G) = kW, Scale factor (F) = 3600000, Total (D)= MWh
Flow
To integrate flow in litres per second to volume in litres
Source (G) = litre/s, Scale factor (F) = 1, Total (D) = litres
A2.9.11 IQECO Minimum Function Modules
Module Identifier F
The Minimum Function module calculates its output (D) as the minimum value of two, three, or four inputs (E), (F), (G), and (H).
A2.9.11.1 IQECO Minimum Function Module Parameters


IQECO Modules

20 20
20 20
A2.9.12 IQECO Maximum Function Modules
Module Identifier F
The Maximum Function module calculates its output (D) as the maximum value from two, three, or four inputs (E), (F), (G), and (H).
A2.9.12.1 IQECO Maximum Function Module Parameters

20 20
20 20
20 20
A2.9.13 IQECO Multiply Function Modules
Module Identifier F
The Multiply Function module calculates its output (D) as the input (G) multiplied by two values ((E) and (F)). The module uses the following formula:
(D)= (G)x(E)x(F)
A2.9.13.1 IQECO Multiply Function Module Parameters

IQECO Modules

20 20
20 20
20 20
Source G Specifies (G) in the calculation. -10 to +10 0 Const/Source G
A2.9.14 IQECO Power Function Modules
Module Identifier F
The Power Function module calculates its output (D) as its input (E) to the power of its input (F). The module uses the following formula:
(D)=(E)(F)
A2.9.14.1 IQECO Power Function Module Parameters
Source E Specifies (E) in the calculation, input. -1020 to +1020 0 Const/Source E
20 20
Source F Specifies (F) in the calculation, maximum difference. -10 to +10 0 Const/Source F
20 20
A2.9.15 IQECO Proximity Function Modules
Module Identifier F
The Proximity Function module calculates sets its output (D) to 1 if (G) > (E)-(F) or < (E)+(F). It is used to see if (E) and (G) are approximately equal.
The module can be disabled using the module state parameter.

IQECO Modules
A2.9.15.1 IQECO Proximity Function Module Parameters


Source E Specifies (E) in the calculation, input. -1020 to +1020 0 Const/Source E
20 20
Source F Specifies (F) in the calculation, maximum difference. -10 to +10 0 Const/Source F
20 20
A2.9.16 IQECO Rescale from Function Modules
Module Identifier F
The Rescale From Function module calculates its output (D) by rescaling input (G) that can be between 0 and 100 to a range between a lower limit (E), and an upper limit (F). The
(D)= E+(((G)-(E))/((F)-(E))
Note: If the value of (G) is outside the range 0 to 100, it will be limited at these values.
A2.9.16.1 IQECO Rescale from Function Module Parameters

20 20
Source E Specifies (E), lower limit, in the calculation. -1020 to +1020 0 Const/Source E
20 20
Source F Specifies (F), upper limit, in the calculation. -10 to +10 0 Const/Source F
20 20

IQECO Modules
A2.9.17 IQECO Rescale to Function Modules

Module Identifier F
The Rescale To Function module rescales an input (G) that can vary between a lower limit (E), and an upper limit (F) to the output (D), which is limited to a percentage value between
0 and 100. The module uses the following formula:
(D)= 100((G)-(E))/((F)-(E)
A2.9.17.1 IQECO Rescale to Function Module Parameters

Source E Specifies (E), lower limit, in the calculation. -1020 to +1020 0 Const/Source E
20 20
Source F Specifies (F), upper limit, in the calculation. -10 to +10 0 Const/Source F
20 20
A2.9.18 IQECO Sample and Hold Function Modules
Module Identifier F
IQECO v2.30 or greater
Sample and Hold Function modules allow an analogue value to be retained. They set the 'Destination D' parameter to the value of the 'Source' parameter when the 'Enable' parameter is
set to '1'.
The 'Destination' parameter will remain at that value until the 'Enable' parameter is set to '1' again. The 'Destination D' parameter can be set to the value of the 'Default Value' parameter
by setting the 'Reset' parameter to '1'.
The module's status is retained when the IQECO is powered down and when the IQECO restarts it the module will adopt the status at power down.
A2.9.18.1 IQECO Sample and Hold Function Module Parameters
Text
Comms
Default Value The value to be used when the 'Reset' parameter is set to '1'. -1020 to +1020 0 Const F
20 20
Destination D The output (D) of the module. -10 to +10 0 Output D

IQECO Modules
Text
Comms
Enable When set to ‘1’ sets the module’s output ‘D’ to the value of the ‘Source’ parameter ‘S’. 0 or 1 1 Source
0 or 1
Reset When set to ‘1’ sets the module’s output ‘D’ to the value specified by the ‘Default Value’ parameter. 0= no change 0 Source
1 = Reset
Source The value that is to be processed -1020 to +1020 0 Source
A2.9.19 IQECO Square Root Function Modules
Module Identifier F
The Square Root Function module calculates its output (D) as the square root of the input (G) multiplied by a value (E). The module uses the following formula:
(D)=(E)(G)
A2.9.19.1 IQECO Square Root Function Module Parameters

20 20
Source E Specifies (E), multiplier, in the calculation. -1020 to +1020 0 Const/Source E
20 20

IQECO Modules
A2.10 IQECO IC Comms Modules

IC Comms modules provide the facility for communication between IQ controllers, where two or more networked controllers are in use. There are several different types to cope with
differing requirements.
IQECO is limited to a total of 10 ic comms modules.
IQECO Data From Analogue IC Comms Modules
IQECO Data From Bit IC Comms Modules
IQECO Data From Byte IC Comms Modules
IQECO v1.0 Data To IC Comms Modules
IQECO v1.0 Global To IC Comms Modules
A2.10.1 IQECO Data From Analogue IC Comms Modules
Module Identifier N
The Data From Analogue ic comms module obtains the value of an analogue value (remote analogue (R)) in another controller and makes it available as an output (L).
For IQECO controllers with v2.1 firmware or greater when the 'COV mode' parameter is enabled the module can receive unconfirmed COV messages (the unconfirmed COV service)
from another BACnet device. The 'Remote Address' and 'Remote Lan' specify the NTD module linked to the BACnet device sending the COV messages, and the 'Remote Module'
parameter specifies the actual value sending the COV messages. The modules failed bit is set to TRUE on power up and will remain TRUE until a matching unconfirmed COV message
is received, after which it becomes FALSE and will remain FALSE forever (or until the controller is powered up again). This can be used in strategy to gate through some default value
into a strategy until an unconfirmed COV message is received. The following data types are supported from the BACnet source: UINT, BOOL, BINARYPV, ENUM, INT and REAL.
A2.10.1.1 IQECO Data From Analogue IC Comms Module Parameters
Text
Comms
Indicates whether or the last messages sent by the module was successful. When 'COV mode' is
0 or 1
enabled it is set to TRUE on power up and will remain TRUE until a matching unconfirmed COV
Failed Bit 0 = OK 0 Output F
message is received, after which it becomes FALSE and will remain FALSE forever (or until the
1 = Failed
controller is powered up again).
Local Module The value received from the remote controller. 1020to +1020 0 Output L
0 or 1
Module State Specifies whether the module is enabled, or disabled. 1=Disabled 0 Const/Source ~
0=Enabled

IQECO Modules
Text
Comms
0 or 1.
Specifies the protocol used to send the message. If set to Trend the message is sent to devices on the
Protocol 0 =Trend 0 Const -
Trend network. If set to BACnet the message is sent to devices on the BACnet network.
1 = BACnet.
The address of the remote controller. If BACnet has been selected as a protocol this must be the
address of the NTD linked to the BACnet device that contains the required value. For IQECO v2.1 or
Remote Address 2, 3, and 10. 0 disables 0 Const/Source A
greater with 'COV mode' enabled this parameter specifies the address of NTD linked to the BACnet
communications
device sending the COV messages.
The LAN of the of the remote controller. If BACnet has been selected as a protocol this must be the
LAN number of the NTD linked to the BACnet device that contains the required value. For IQECO
Remote Lan 2, 3, and 10. 0 Const/Source N
v2.1 or greater with 'COV mode' enabled this parameter specifies the LAN number of NTD linked to
0 = local LAN.
the BACnet device sending the COV messages.
The analogue parameter the IC Comms message will access. For IQECO v2.1 or greater with 'COV Any analogue module
Remote Module Blank Const R
mode' enabled this parameter specifies the BACnet parameter sending the COV messages. parameter.
IQECO less than v2.1 = 1 to
The length of time (in minutes) between a message being sent and then repeated.
Retransmission 1440
For IQECO v2.1 or greater setting this parameter to 9999 causes the module to listen for unconfirmed 5 Const I
Interval IQECO v2.1 or greater = 1 to
COV messages from the specified BACnet device.
1440 and 9999
Time into
Length of time (in minutes) since the start of the retransmission interval. 0 to 3276 0 Status T
Interval
A2.10.2 IQECO Data From Bit IC Comms Modules
Module Identifier N
The Data From Bit ic comms module obtains the value of a bit (remote bit (R)) from another controller, and makes it available as an output (L).
For IQECO controllers with v2.1 firmware or greater when the 'COV mode' parameter is enabled the module can receive unconfirmed COV messages (the unconfirmed COV service)
from another BACnet device. The 'Remote Address' and 'Remote Lan' specify the NTD module linked to the BACnet device sending the COV messages, and the 'Remote Module'
parameter specifies the actual value sending the COV messages. The modules failed bit is set to TRUE on power up and will remain TRUE until a matching unconfirmed COV message
is received, after which it becomes FALSE and will remain FALSE forever (or until the controller is powered up again). This can be used in strategy to gate through some default value
into a strategy until an unconfirmed COV message is received. The following data types are supported from the BACnet source: UINT, BOOL, BINARYPV, ENUM, INT and REAL.
Any numeric value greater than 0.5 equates to TRUE, other values to FALSE.

IQECO Modules
A2.10.2.1 IQECO Data From Bit IC Comms Module Parameters

Text
Comms
0 or 1
Failed Bit Indicates whether or the last messages sent by the module was successful. 0 = OK 0 Output F
1 = Failed
Local Module The value received from the remote controller. 0 or 1 0 Output L
0 or 1
0=Enabled
0 or 1.
Specifies the protocol used to send the message. If set to Trend the message is sent to devices on the
Protocol 0 =Trend 0 Const -
Trend network. If set to BACnet the message is sent to devices on the BACnet network.
1 = BACnet.
The address of the remote controller. If BACnet has been selected as a protocol this must be the
address of the NTD linked to the BACnet device that contains the required value. For IQECO v2.1 or
Remote Address 2, 3, and 10. 0 disables 0 Const/Source A
greater with 'COV mode' enabled this parameter specifies the address of NTD linked to the BACnet
communications
device sending the COV messages.
The LAN of the of the remote controller. If BACnet has been selected as a protocol this must be the
LAN number of the NTD linked to the BACnet device that contains the required value. For IQECO
Remote Lan 2, 3, and 10. 0 Const/Source N
v2.1 or greater with 'COV mode' enabled this parameter specifies the LAN number of NTD linked to
0 = local LAN.
the BACnet device sending the COV messages.
The bit the IC Comms message will access. For IQECO v2.1 or greater with 'COV mode' enabled this Any analogue module
parameter specifies the BACnet parameter sending the COV messages. parameter.
IQECO less than v2.1 = 1 to
The length of time (in minutes) between a message being sent and then repeated. For IQECO v2.1 or
Retransmission 1440
greater setting this parameter to 9999 causes the module to listen for unconfirmed COV messages 5 Const I
Interval IQECO v2.1 or greater = 1 to
from the specified BACnet device.
1440 and 9999
Time into
Length of time (in minutes) since the start of the retransmission interval. 0 to 3276 0 Status T
Interval

IQECO Modules
A2.10.3 IQECO Data From Byte IC Comms Modules

Module Identifier N
The Data From Byte ic comms module obtains the value of a byte (remote byte (R)) from another controller, and makes it available as an output (L).
A2.10.3.1 IQECO Data From Byte IC Comms Module Parameters
Text
Comms
0 or 1
1 = Failed
Local Module The value received from the remote controller. 1020to +1020 0 Output L
0 or 1
0=Enabled
0.
Protocol Specifies the protocol used to send the message. 0 Const -
0 =Trend
The address of the remote controller. If BACnet has been selected as a protocol 0 to 119 excluding addresses 2, 3, and 10. 0
Remote Address 0 Const/Source A
this must be the address of a NTD. disables communications
The LAN of the device to which the message is to be sent. If BACnet has been 0 to 119 excluding addresses 2, 3, and 10.
Remote Lan 0 Const/Source N
selected as a protocol this must be the address of an NTD. 0 = local LAN.
Remote Module The bit the IC Comms message will access. Any digital byte module parameter. Blank Const R
Retransmission
The length of time (in minutes) between a message being sent and then repeated. 1 to 1440 5 Const I
Interval
Time into Interval Length of time (in minutes) since the start of the retransmission interval. 0 to 3276 0 Status T

IQECO Modules
A2.10.4 IQECO v1.0 Data To IC Comms Modules

Module Identifier N
IQECO v1.0 only
The IQECO v1.0 Data To ic comms module sends the value specified by the 'Local Module' parameter to a node (remote node (R)) in another IQ controller.
IQECO controllers are limited to a total of 10 data to and global to ic comms modules.
A2.10.4.1 IQECO v1.0 Data To IC Comms Module Parameters
Text
Comms
The module parameter or whose value is to be sent. It can be an analogue value, or
Local module Any valid Trend module parameter code. Blank Source L
digital bit value.
0 or 1
0=Enabled
0 to 119 excluding addresses 2, 3, and 10. 0
Remote Address The address of the remote controller. 0 Const/Source A
disables communications
Remote Lan Specifies the LAN of the devices to which the message is to be sent. 0 Const/Source N
0 = local LAN.
Specifies where the value is to be written. If Label Matching is selected the remote The output of any knob, switch, sensor, or
node is selected by a match with the label of the module’s source (L). digital input module.
0 to 1440
Retransmission
The length of time (in minutes) between a message being sent and then repeated. 0=message on sent on significant change 5 Const I
Interval
only
The amount the value of the source address can change before a message is sent. If
Significant Change 0 to 6500 1 Const S
set to '0' the messages is only sent at the retransmission interval.

IQECO Modules
A2.10.5 IQECO v1.0 Global To IC Comms Modules

Module Identifier N
IQECO v1.0 only
The IQECO v1.0 Global To ic comms module sends the value specified by the Local module parameter to a node (remote node (R)) in other IQ controllers that match the search criteria
set up in the module.
A2.10.5.1 IQECO v1.0 Global To IC Comms Module Parameters
Text
Comms
0 to 7
0=comms disabled
1=identifier
2=F attribute
The attribute that must match in all devices for them to respond to the
Attributes 3=G attribute 0 Const B
message.
4=H attribute
5=I attribute
6=J attribute
7=K attribute
Label Note: This parameter is for use in IQSET only, it is not sent to the Any ASCII character except \/(){};,: Blank Const -
controller.
The module parameter or whose value is to be sent. It can be an analogue
Local module Any valid Trend module parameter code. 0 Source L
value, or digital bit value.
0 or 1
0=Enabled
0 to 119, 128 excluding addresses 2, 3, and 10.
Remote Lan Specifies the LAN of the devices to which the message is to be sent. 0 = Local LAN 0 Const/Source N
128 = all LANs.
Specifies where the value is to be written. Specifies where the value is to The output of any knob, switch, sensor, or digital input
Remote Module be written. If Label Matching is selected the remote node is selected by module. If label matching is used to an IQ1, IQ2, or IQ3 Blank Const R
a match with the label of the module’s source (L). the value of a driver module can be specified.
Retransmission The length of time (in minutes) between a message being sent and then 0 to 1440
5 Const I
Interval repeated. 0=message on sent on significant change only

IQECO Modules
Text
Comms
Significant The amount the value of the source address can change before a message
0 to 6500 1 Const S
Change is sent. If set to '0' the messages is only sent at the retransmission interval.
A2.10.6 IQECO v2.0 Data To IC Comms Modules
Module Identifier N
A2.10.6.1 IQECO v2.0 Data To IC Comms Module Parameters
Text
Comms
0 or 1
1 = Failed
Local module The value that is sent. It can be an analogue value, or digital byte, or digital bit value. 1020to +1020/0 or 1 0 Const/Source L
0 or 1
0=Enabled
Specifies the protocol used to send the message. If set to Trend the message is sent to 0 or 1.
Protocol devices on the Trend network. If set to BACnet the message is sent to devices on the 0 =Trend 0 Const
BACnet network. 1 = BACnet.
The address of the remote controller. If BACnet has been selected as a protocol this must 0 to 119 excluding addresses 2, 3, and
Remote Address 0 Const/Source A
be the address of the NTD linked to the BACnet device that the value is to be sent. 10. 0 disables communications
Specifies the LAN of the devices to which the message is to be sent. If BACnet has been 0 to 119 excluding addresses 2, 3, and
Remote Lan selected as a protocol this must be the LAN of the NTD linked to the BACnet device that 10. 0 Const/Source N
the value is to be sent. 0 = local LAN.
Specifies where the value is to be written. If Label Matching is selected the remote node is
Any analogue, digital byte, or digital
Remote Module selected by a match with the label of the module’s source (L). Blank Const R
bit module parameter.

IQECO Modules
Text
Comms
Retransmission
Interval
Significant The amount the value of the source address can change before a message is sent. If set to '0'
0 to 6500 1 Const S
Change the messages is only sent at the retransmission interval.
0 to 16
Write Priority The write priority used to write the value to the BACnet device. 9 Const w
0 sends the request with no priority
A2.10.7 IQECO v2.0 Global To IC Comms Modules
Module Identifier N
A2.10.7.1 IQECO v2.0 Global To IC Comms Module Parameters
Text
Comms
0 to 7
0=comms disabled
1=identifier
2=F attribute
Attributes The attribute that must match in all devices for them to respond to the message. 3=G attribute 0 Const B
4=H attribute
5=I attribute
6=J attribute
7=K attribute
0 or 1
1 = Failed
Local module The value that is sent. It can be an analogue value, or digital byte, or digital bit value. 1020to +1020/0 or 1 0 Const/Source L

IQECO Modules
Text
Comms
0 or 1
0=Enabled
0 or 1.
Specifies the protocol used to send the message. If set to Trend the message is sent to devices
Protocol 0 =Trend 0 Const
on the Trend network. If set to BACnet the message is sent to devices on the BACnet network.
1 = BACnet.
0 to 119, 128 excluding addresses
Specifies the LAN of the devices to which the message is to be sent. If BACnet has been selected 2, 3, and 10.
Remote Lan 0 Const/Source N
as a protocol this must be the LAN of an NTD. 0 = local LAN.
128 = all LANs
Specifies where the value is to be written. If Label Matching is selected the remote node is
Any analogue, digital byte or
Remote Module selected by a match with the label of the module’s source (L). Blank Const R
digital bit module parameter.
Retransmission
Interval
The amount the value of the source address can change before a message is sent. If set to '0' the
Significant Change 0 to 6500 1 Const S
messages is only sent at the retransmission interval.
0 to 16
Write Priority The write priority used to write the value to the BACnet device. 0 sends the request with no 9 Const w
priority.

IQECO Modules
A2.11 IQECO Input Modules

Input modules take an input from the outside world, to a point within the controller. There are several different types to cope with different types of input devices.
IQECO Analogue Node Modules
IQECO Digital Byte Modules
IQECO External Sensor Modules
IQECO External Digital Input Modules
IQECO Internal Digital Input Modules
IQECO Internal Sensor Modules
IQECO Knob Modules
IQECO Switch Modules
A2.11.1 IQECO Analogue Node Modules
Module Identifier A
A2.11.1.1 IQECO Analogue Node Module Parameters
Text
Comms
The alarm status of the analogue value connected to the value parameter. Remain sat the default if the value 00000000 to
Alarm Status 00000000 Output S
parameter is set as a constant. 11111111
0 or 1
High The status of the high alarm. 0 = No alarm 0 Output H
1 = Alarm
0 or 1
Low The status of the low alarm. 0 = No alarm 0 Output L
1 = Alarm
0 or 1
Outside
The status of the outside limits alarm. 0 = No alarm 0 Output O
Limits
1 = Alarm
0 or 1
Read The status of the Read alarm. 0 = No alarm 0 Output R
1 = Alarm
Value The value of the analogue node. It can be a constant, or an input from another controller using IC Comms. -1020 to +1020 0 Const/Source V
20 20
Output The value of the module. -10 to +10 0 Output D

IQECO Modules
A2.11.2 IQECO Digital Byte Modules
Module Identifier B
The Digital Byte module stores a byte of information (8-bits values a, b, c, d, e, f, g, h e.g. 01010100).
A2.11.2.1 IQECO Digital Byte Module Parameters
Text
Comms
Bit a The value of bit 0. 0 or 1 0 Output a
Bit b The value of bit 1. 0 or 1 0 Output b
Bit c The value of bit 2. 0 or 1 0 Output c
Bit d The value of bit 3. 0 or 1 0 Output d
Bit e The value of bit 4. 0 or 1 0 Output e
Bit f The value of bit 5. 0 or 1 0 Output f
Bit g The value of bit 6. 0 or 1 0 Output g
Bit h The value of bit 7. 0 or 1 0 Output h
User-friendly label for output bit 0. It can be up to 30-characters long. Any ASCII character except
Label, 0-a Blank Const -
Note: This parameter does not exist in the controller it is for use in IQSET only. \/(){};,:
Label, 1-b Blank Const -
Label, 2-c Blank Const -
Label, 3-d Blank Const -
Label, 4-e Blank Const -
Label, 5-f Blank Const -
Label, 6-g Blank Const -

IQECO Modules
Text
Comms
Label, 7-h Blank Const -
The decimal value of the value. Enables the output value of the module to be easily specified.
State 0 to 255 0 Const -
The 8-bit digital status of the byte. It can be a constant, or an input from another controller using IC
Value 00000000 to 11111111 00000000 Const S
Comms.
A2.11.3 IQECO External Digital Input Modules
Module Identifier I
The External Digital Input module takes the status from a real digital device such as a pressure switch, connected to a digital input of the controller, checks the value against the required
state, and places its value into a digital node.
A2.11.3.1 IQECO External Digital Module Parameters
Text
Comms
Alarm Delay IQECO v2.0 or greater controllers. The length of time in seconds that the value must be in the wrong state before an
0 to 172800 0 Const/Source d1(D)
(secs) alarm is generated.
Alarm Group IQECO v2.0 or greater controllers. Specifies the alarm group module to which the status alarm is sent. 0 to 500 0 Const d1(G)
0 or 1
Alarm Sent IQECO v2.0 or greater controllers. Indicates if the alarm has been sent to the alarm group. 0 = Not sent 0 Status d1(K)
1 = Sent
Alarm State
IQECO v2.0 or greater controllers. The current state of the status alarm of the module. 0 or 1 0 Output d1(S)
(Digin)
0 or 1
Clear Alarm
IQECO v2.0 or greater controllers. Specifies whether the state clear alarm is enabled. 1=Enabled 0 Const m1(C)
Enable (State)
0=Disabled
0 or 1
Enabled (State) IQECO v2.0 or greater controllers. Enables/Disables the state alarm. 0 = Disabled 0 Const/Source d1(E)
1 = Enabled
Hardware 0 to 7, 101 to 108
The input channel to be used by the input. Channels 101 to 108 are used for IQECOs service PIN. 1 Const c
Channel 0 = Disabled

IQECO Modules
Text
Comms
IQECO v2.0 or greater. The current number of times the driver has started. It can be used to provide an input to other
Starts 0 to 109 0 Output N
modules by linking it to the required modules.
State The output (S) of the module. It can be used to provide an input to other modules by linking it to the required modules. 0 or 1 0 Output S
Time in Alarm
IQECO v2.0 or greater controllers. The length of time in seconds since the alarm state started. 0 to +1020 0 Const/Source d1(T)
(secs)
Type Specifies whether the input is an external digital input, or an external digital input. 0 0 Const Y
A2.11.4 IQECO External Sensor Modules
Module Identifier S
The External Sensor module takes the reading from a real sensor connected to the analogue input of the controller, scales it into engineering units, and checks the value against alarm
levels. The sensor type determines how the scaling is performed. The sensor type is a separate module that defines parameters for a specific type of sensor. An offset is used to allow
the reading to be adjusted to the actual value.
A2.11.4.1 IQECO External Sensor Module Parameters
Text
Comms
Alarm Delay (secs) IQECO v2.0 or greater controllers. The length of time in seconds that the sensor reading must be above the
0 to 178200 0 Const/Source h1(D)
(High) high alarm limit before a sensor high alarm is generated.
Alarm Delay (secs) IQECO v2.0 or greater controllers. The length of time in seconds that the sensor reading must be below the
0 to 178200 0 Const/Source l1(D)
(Low) low alarm limit before a sensor low alarm is generated.
Alarm Delay (secs) IQECO v2.0 or greater controllers. The length of time in seconds that the sensor reading must be outside
0 to 178200 0 Const/Source 01(D)
(Out of Limits) the specified limits before an out of limits alarm is generated.
Alarm Delay (secs) IQECO v2.0 or greater controllers. The length of time in seconds that the sensor reading must read an
0 to 178200 0 Const/Source r1(D)
(Read) invalid reading before an out of limits alarm is generated.
Alarm Group (High) IQECO v2.0 or greater controllers. Specifies the alarm group to which the High alarm is sent. 0 to 500 0 Const h1(G)
Alarm Group (Low) IQECO v2.0 or greater controllers. Specifies the alarm group to which the Low alarm is sent. 0 to 500 0 Const l1(G)
Alarm Group (Out
IQECO v2.0 or greater controllers. Specifies the alarm group to which the Out of Limits alarm is sent. 0 to 500 0 Const o1(G)
of Limits)
Alarm Group (Read) IQECO v2.0 or greater controllers. Specifies the alarm group to which the Read alarm is sent. 0 to 500 0 Const r1(G)

IQECO Modules
Text
Comms
0 or 1
Alarm Sent (High) IQECO v2.0 or greater controllers. Indicates if the High alarm has been sent to the alarm group. 0 = Not sent 0 Status h1(K)
1 = Sent
0 or 1
Alarm Sent (Low) IQECO v2.0 or greater controllers. Indicates if the Low alarm has been sent to the alarm group. 0 = Not sent 0 Status l1(K)
1 = Sent
0 or 1
Alarm Sent (Out of
IQECO v2.0 or greater controllers. Indicates if the Out of Limits alarm has been sent to the alarm group. 0 = Not sent 0 Status o1(K)
Limits)
1 = Sent
0 or 1
Alarm Sent (Read) IQECO v2.0 or greater controllers. Indicates if the Read alarm has been sent to the alarm group. 0 = Not sent 0 Status r1(K)
1 = Sent
Alarm State The status of the 4 alarm outputs. 0000 to 1111 0000 Status M
0 or 1
Alarm State (High) IQECO v2.0 or greater controllers. The status of the High alarm. 0 = No alarm 0 Output h1(S)
1 = Alarm
0 or 1
Alarm State (Low) IQECO v2.0 or greater controllers. The status of the Low alarm. 0 = No alarm 0 Output l1(S)
1 = Alarm
0 or 1
Alarm State (Out of
IQECO v2.0 or greater controllers. The status of the Out of Limits alarm. 0 = No alarm 0 Output o1(S)
Limits)
1 = Alarm
0 or 1
Alarm State (Read) IQECO v2.0 or greater controllers. The status of the Read alarm. 0 = No alarm 0 Output r1(S)
1 = Alarm
0 or 1
Clear Alarm Enable
IQECO v2.0 or greater controllers. Specifies whether the read clear alarm is enabled. 1=Enabled 0 Const h1(C)
(High)
0=Disabled
0 or 1
Clear Alarm Enable
IQECO v2.0 or greater controllers. Specifies whether the read clear alarm is enabled. 1=Enabled 0 Const l1(C)
(Low)
0=Disabled

IQECO Modules
Text
Comms
0 or 1
Clear Alarm Enable
IQECO v2.0 or greater controllers. Specifies whether the read clear alarm is enabled. 1=Enabled 0 Const o1(C)
(Out of Limits)
0=Disabled
0 or 1
Clear Alarm Enable
IQECO v2.0 or greater controllers. Specifies whether the read clear alarm is enabled. 1=Enabled 0 Const r1(C)
(Read)
0=Disabled
0 or 1
Enabled (High) Enables/Disables the High alarm. 0 = Disabled 0 Const/Source h1(E)
1 = Enabled
0 or 1
Enabled (Low) Enables/Disables the Low alarm. 0 = Disabled 0 Const/Source l1(E)
1 = Enabled
0 or 1
Enabled (Out of
Enables/Disables the Out of Limits alarm. 0 = Disabled 0 Const/Source o1(E)
Limits)
1 = Enabled
0 or 1
Enabled (Read) Enables/Disables the Read alarm. 0 = Disabled 0 Const/Source r1(E)
1 = Enabled
High Alarm Level The value above which a sensor high alarm will be generated. -1020 to +1020 0 Const/Source H
0 to 7
Hardware Channel The input channel to be used by the sensor. 0 Const c
0=Disabled
0 to 9, A, B, C, D, E,
and, F
0 = controller
A = 10
Hardware Module IQECO v2.0 or greater controllers. The I/O module to which the sensor is connected. B = 11 0 Const i
C = 12
D = 13
E = 14
F = 15
Low Alarm Level The value below which a sensor low alarm will be generated. -1020 to +1020 0 Const/Input L
20 20
Offset The amount by which the sensor reading is to be increased, or decreased to make it accurate. -10 to +10 0 Const/Source O
Sequence Step The module's position in the sequence table. 0 to 200 0 Const -

IQECO Modules
Text
Comms
Time in Alarm
The length of time in seconds since the alarm state commenced. 0 to +1020 0 Status h1(T)
(secs) (High)
Time in Alarm
The length of time in seconds since the alarm state commenced. 0 to +1020 0 Status l1(T)
(secs) (Low)
Time in Alarm
(secs) (Out of The length of time in seconds since the alarm state commenced. 0 to +1020 0 Status o1(T)
Limits)
Time in Alarm
The length of time in seconds since the alarm state commenced. 0 to +1020 0 Status r1(T)
(secs) (Read)
The sensor type module used by the sensor to convert the signal into engineering units. Sensor type modules
store information about certain types of sensor. Ensure that the sensor type module chosen correctly v1 = 0 to 10
Type specifies the sensor that is being used. v2.0 or greater = 0 to 1 Const Y
For IQECO controllers v2.0 or greater 1 to 99 are user configurable sensor. 101 to 111 are fixed sensor 111
type modules 100 is unused.
Any ASCII
Units 4-character string that specifies the engineering units of the sensor’s value. character except ( { ; Blank Const %
,:
Value The output of the sensor. -1020 to +1020 0 Output V
A2.11.5 IQECO Internal Sensor Modules
Module Identifier S
The Internal Sensor module allows an analogue node to be monitored. It takes the reading from within the controller, scales it into engineering units, and checks the value against alarm
levels. Internal sensors have an exponent, and source instead of sensor type, and offset. The source defines the analogue node from which the sensor takes its value. The exponent
determines the number of decimal places before the decimal point. An offset is used to allow the reading to be adjusted.
A2.11.5.1 IQECO Internal Sensor Module Parameters
Text
Comms
Alarm Delay (secs) IQECO v2.0 or greater. The length of time in seconds that the sensor reading must be above the
0 to 178200 0 Const/Source h1(D)
(High) high alarm limit before a sensor high alarm is generated.

IQECO Modules
Text
Comms
Alarm Delay (secs) IQECO v2.0 or greater. The length of time in seconds that the sensor reading must be below the
0 to 178200 0 Const/Source l1(D)
(Low) low alarm limit before a sensor low alarm is generated.
Alarm Group (High) IQECO v2.0 or greater. Specifies the alarm group to which the High alarm is sent. 0 to 500 0 Const h1(G)
Alarm Group (Low) IQECO v2.0 or greater. Specifies the alarm group to which the Low alarm is sent. 0 to 500 0 Const l1(G)
0 or 1
Alarm Sent (High) IQECO v2.0 or greater. Indicates if the High alarm has been sent to the alarm group. 0 = Not sent 0 Status h1(K)
1 = Sent
0 or 1
Alarm Sent (Low) IQECO v2.0 or greater. Indicates if the Low alarm has been sent to the alarm group. 0 = Not sent 0 Status l1(K)
1 = Sent
0 or 1
Alarm State (High) IQECO v2.0 or greater. The status of the High alarm. 0 = No alarm 0 Output h1(S)
1 = Alarm
0 or 1
Alarm State (Low) IQECO v2.0 or greater. The status of the Low alarm. 0 = No alarm 0 Output l1(S)
1 = Alarm
0 or 1
Clear Alarm Enable
IQECO v2.0 or greater. Specifies whether the read clear alarm is enabled. 1=Enabled 0 Const h1(C)
(High)
0=Disabled
0 or 1
Clear Alarm Enable
IQECO v2.0 or greater. Specifies whether the read clear alarm is enabled. 1=Enabled 0 Const l1(C)
(Low)
0=Disabled
Additional information about the sensor. Any ASCII character
Details Blank Const -
Note: This parameter does not exist in the controller it is for use in IQSET only. except \/(){};,:
0 or 1
Enabled (High) Enables/Disables the High alarm. 0 = Disabled 0 Const/Source h1(E)
1 = Enabled
0 or 1
Enabled (Low) Enables/Disables the Low alarm. 0 = Disabled 0 Const/Source l1(E)
1 = Enabled
High Alarm Level The value above which a sensor high alarm will be generated. -1020 to +1020 0 Const/Source H
20 20
Low Alarm Level The value below which a sensor low alarm will be generated. -10 to +10 0 Const/Input L

IQECO Modules
Text
Comms
Offset The amount by which the sensor reading is to be increased, or decreased to make it accurate. -1020 to +1020 0 Const/Source O
Sequence Step The module's position in the sequence table. 0 to 200 0 Const -
Source The value of the input channel. If the input channel is set to 0 this becomes a constant. 0 to 10000 0 Const/Source S
The length of time in seconds since the alarm state commenced. 0 to +1020 0 Status h1(T)
(High)
The length of time in seconds since the alarm state commenced. 0 to +1020 0 Status l1(T)
(Low)
Any ASCII character
Units 4-character string that specifies the engineering units of the sensor’s value. Blank Const %
except ( { ; , :
Value The output (V) of the sensor. -1020 to +1020 0 Output V
A2.11.6 IQECO Internal Digital Input Modules
Module Identifier I
The Internal Digital Input module takes the status of a digital value in the controller, checks the value against the required state, and places its value into a digital node.
A2.11.6.1 IQECO Internal Digital Module Parameters
Text
Comms
IQECO v2.0 or greater. The length of time in seconds that the value must be in the wrong state before an alarm is
Alarm Delay (secs) 0 to 172800 0 Const/Source d1(D)
generated.
Alarm Group IQECO v2.0 or greater. Specifies the alarm group module to which the status alarm is sent. 0 to 500 0 Const d1(G)
0 or 1
Alarm Sent IQECO v2.0 or greater. Indicates if the alarm has been sent to the alarm group. 0 = Not sent 0 Status d1(K)
1 = Sent
Alarm State (Digin) IQECO v2.0 or greater. The current state of the status alarm of the module. 0 or 1 0 Output d1(S)
0 or 1
Clear Alarm Enable
IQECO v2.0 or greater. Specifies whether the state clear alarm is enabled. 1=Enabled 0 Const m1(C)
(State)
0=Disabled

IQECO Modules
Text
Comms
0 or 1
0 =
Enabled (State) IQECO v2.0 or greater. Enables/Disables the state alarm. 0 Const/Source d1(E)
Disabled
1 = Enabled
IQECO v2.0 or greater. The length of time (in hours) the input has been ON. It can be used to provide an input to
Hours Run 0 to 87840 0 Output H
IQECO v2.0 or greater. The current number of times the driver has started. It can be used to provide an input to
Starts 0 to 109 0 Output N
State The module's output state. It can be used to provide an input to other modules by linking it to the required modules. 0 or 1 0 Output S
Source The status of the input to the digital input module. 0 or 1 0 Const/Source I
Time in Alarm (secs) IQECO v2.0 or greater controllers. The length of time in seconds since the alarm state started. 0 to +1020 0 Const/Source d1(T)
0 or 1
Type Specifies whether the input is an external digital input, or an external digital input. 0 = External 1 Const Y
1 = Internal
A2.11.7 IQECO Knob Modules
Module Identifier K
The Knob module enables an analogue value to be changed. It has user-defined limits between which its value can be adjusted. Use of the knob can be restricted by using the PIN level
to prevent unauthorised adjustments.
A2.11.7.1 IQECO Knob Module Parameters
The modules include the following parameters common to most modules: 'Label', and Sequence Step (IQECO v2.0 or greater) - see Common IQECO Module Parameters, plus the
following:
Text
Comms
Bottom
The minimum value of the knob. -1020 to +1020 0 Const/Source B
Range
0 or 1
Clip to Specifies whether the knob's output is set to the bottom range value or upper range value when the 0 = adjustment not
0 Const L
Limits knob is adjusted outside these limits, or the adjustment is not allowed. allowed.
1 = adjustment allowed
Destination The output (D) of the knob. -1020 to +1020 0 Output D

IQECO Modules
Text
Comms
Additional information about the sensor. Any ASCII character
Details Blank Const -
Note: This parameter does not exist in the controller it is for use in IQSET only. except \/(){};,:
PIN Level The PIN level required before the knob can be adjusted. 0 to 99 0 Const P
20 20
Top Range The maximum value of the knob. -10 to +10 0 Const/Source T
Any ASCII character
Units 4-character string that specifies the engineering units of the knob's value. Blank Const %
except ( { ; , :
v2 or greater
Value The value of the knob. -1020 to +1020 0 Const/Source V
v1 Const
A2.11.8 IQECO Switch Modules
Module Identifier W
The Switch module enables a digital value to be changed.
A2.11.8.1 IQECO Switch Module Parameters
The modules include the following parameters common to most modules: 'Label', and Sequence Step (IQECO v2.0 or greater) - see Common IQECO Module Parameters, plus the
following:

Destination The output (D) of the Switch. 0 or 1 0 Const D
Additional information about the Switch.
Details Any ASCII character except \/(){};,: Blank Const -
Note: This parameter is for use in IQSET only it is not sent to the controller.
v2 or greater Const/Source
Status The value of the switch. 0 or 1 0 S
v1 Const
User Level The PIN level required before the switch can be adjusted. 0 to 99 0 Const P

IQECO Modules
A2.12 IQECO Interface Modules

Interface modules are only available on IQECO v2.30 or greater they provide the ability to interface with different devices.
IQECO Type 2 (Wallbus) Interface Modules
A2.12.1 IQECO Type 2 (Wallbus) Interface Modules
Module Identifier t
Type 2 (Wallbus) Interface modules enables Wallbus devices to be connected to the IQECO.
A2.12.1.1 IQECO Type 2 (Wallbus) Interface Module Parameters
Text
Comms
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,
Address The address of the Wallbus device, and the controller itself has an address of 1. 12, 13, 14, 15 2 N -
0 = reserved
Device
Not currently supported. Read only. The firmware version of the Wallbus device connected using the module,
Firmware - - C C
read from the device.
Version
Not currently supported. The name of the device profile. A profile is a specific set of parameter values that is
Device Profile matched to a function on a specific type of Wallbus device. E.g. there will be a profile for RD-WMB that - - N f
defines the appropriate inputs and outputs with no filename.
Device Type Read only. Type of the Wallbus device connected using the module, read from the device. - - C T
0 or 1
Disable Module Enables/disables the module. When disabled the Wallbus communications will not work. 0 = Disabled 0 N ~
1 = Enabled
0 or 1
Failed Indicates that comms to address interface device have timed-out 0 = OK 0 N e
1 = timeout
Not currently supported. The name of the configuration file to be sent to Wallbus device.
Filename - - N F
For non-programmable devices, leave this parameter empty.
Input Label The label of the Input. Each input has this parameter, ‘n’ is input number 1 to 250. null N In$
character except \/(){};,: 0
Input Value The value of the Input. Each input has this parameter, ‘n’ is input number 1 to 250. 0 I InV
analogue

IQECO Modules
Text
Comms
Inputs (PV The PV in the Wallbus device to which the input of the Interface module is connected. Each input has this
- - N InN
Inputs (Refresh Defines the interval at the Interface module writes its value to the PV in the Wallbus device. Each input has 0s, 5s, 10s, 15s, 20s, 25s, 30s,
- N InP
Period) this parameter, n determines the input. 35, 40s, 45s, 50s
Inputs
Defines the amount by which the value of the input must change before the value is written to the PV in the
(Significant - - N InC
Wallbus device. Each input has this parameter, n determines the input.
change)
Label The name of the interface. - N $
The network module of the network to which the interface is to be connected.
Network For Type 1 (XNC) Interface modules this parameter is only required when interfacing using a serial Valid module number - N n
connection.
Output Label The label of the output. Each output has this parameter, ‘n’ is input number 1 to 250. null N On$
Output Value The value of the Output. Each output has this parameter, ‘n’ is output number 1 to 250. 0 I OnV
analogue
The time, in seconds, that the value of the output is held for after the last communication from the Wallbus
Outputs (Expiry device. 0s, 5s, 10s, 15s, 20s, 25s, 30s,
- N OnM
time) ‘0’ holds indefinitely. Any other value, nn, will cause the output’s value to be set to ‘FL_INVALID’ nn 35, 40s, 45s, 50s
seconds after the last update is received from the Wallbus device, where nn is the value of this parameter.
Outputs (PV The PV in the Wallbus device to which the output of the Interface module is connected. Each output has this
- - N OnN
2
Program Type The type of interface module. 2 N Y
2 = Wallbus
Size of Modules Size of the module including any application file. 1 to 2000 0 N Z
0, 1, 2
0 = Not Present
Status The Status of interface device. 0 N t
1 = Operational

IQECO Modules
A2.13 IQECO I/O Modules

Module Identifier I
IQECO I/O modules specify any external displays that are connected to the controllers Wallbus connection. A separate I/O module must be added for each physical display connected
to the controller.
Note: IQECO v2.30 introduced a different method of connecting Wallbus devices which provides more flexibility. However, IQECO I/O modules were retained to provide compatibility
with strategies configured for earlier firmware versions.
A2.13.1 IQECO I/O Module Parameters
Actual Type The actual display type as found on the bus. Character String Blank Status A
Configured Type Specifies the type of display that is to be connected to the controller. Character String Blank Const Y
0 or 1
Failed Indicates if the display is in a failed state. 0 = OK 0 Output F
1 = Failed
0, 1, 2, 3, 4, 5 and 6
0= No fan on home screen
1= 2 position fan (Off/On)
2= 3 position fan (Off, On, Auto)
Fan Configuration Specifies the way in which the fan speed is displayed on the display. 0 Const f
3= 4 position fan (Off, 1, 2, 3)
4= 5 position fan (Off, 1 ,2 ,3, Auto)
5 = blind 4 position (0, 1, 2, 3)
6 = blind 5 position (0, 1,2 ,3, 4)
0 to F
Module ID Specifies the id of the display. Must be set to '2'. 2 Const Module Number
0 = main controller
Version The display's firmware version. Character string fixed Const C

IQECO Modules
A2.14 IQECO Logic Modules

Logic modules allow outputs to be generated as a function of several digital values within a control strategy.
IQECO Combination Logic Modules
IQECO Counter Logic Modules
IQECO D to A Logic Modules
IQECO Flip Flop Logic Modules
IQECO Hours Run Logic Modules
IQECO Latch Logic Modules
IQECO Timer Logic Modules
A2.14.1 IQECO Combination Logic Modules
Module Identifier G
The Combination Logic module calculates its output (D) (0 or 1) as the logical combination of up to 4 logical functions (J), (K), (L), and (M). Each logical function is itself a function
of 4 digital values (E), (F), (G), and (H) which are AND’ed together ((E) AND (F) AND (G) AND (H)). An AND NOT function can also be achieved by specifying a lowercase letter
instead of uppercase. This allows combinations of AND, and AND NOT functions within each of the logical functions (J), (K), (L), and (M). The output (D) is the result of all logical
functions OR’ed together ((J) OR (K) OR (L) OR (M).
A2.14.1.1 IQECO Combination Logic Module Parameters
The modules include the following parameter common to most modules: Sequence Step - see Common IQECO Module Parameters, plus the following:
Text
Comms
Logically combines up to 4 digital values (E), (F), (G), or (H) using AND, and AND NOT functions. uppercase
letters indicate the true state, and lowercase letters indicate the false state (i.e. NOT). The result of this logical Blank Const J
J EeFfGgHh
combination will be OR’ed with the results of the logical functions K, L, and M.
letters indicate the true state, and lowercase letters indicate the false state (i.e. NOT). The result of this logical Blank Const K
K EeFfGgHh
combination will be OR’ed with the results of the logical functions J, L, and M.
letters indicate the true state, and lowercase letters indicate the false state (i.e. NOT). The result of this logical Blank Const L
L EeFfGgHh
combination will be OR’ed with the results of the logical functions J, K, and M.
letters indicate the true state, and lowercase letters indicate the false state (i.e. NOT). The result of this logical Blank Const M
M EeFfGgHh
combination will be OR’ed with the results of the logical functions J, K, and L.
Input E Specifies (E) in the logical combination. 0 or 1 0 Const/Source E

IQECO Modules
Text
Comms
Input F Specifies (F) in the logical combination. 0 or 1 0 Const/Source F
Input G Specifies (G) in the logical combination. 0 or 1 0 Const/Source G
Input H Specifies (H) in the logical combination. 0 or 1 0 Const/Source H
Any ASCII
Label character except Blank Const -
\/(){};,:
A2.14.2 IQECO Counter Logic Modules
Module Identifier G
IQECO v2.0 greater.
The Counter Logic module provides the facility for counting pulse type signals such as those provided by gas and electricity meters. It has two outputs rate (R) and cumulative count
(M). (M) is the total number of times the input (S) has been set to 1 since the reset input (A) was last set to 1 multiplied by the scaling factor (F). (R) is the change in (M) over the period
(T).
A2.14.2.1 IQECO Counter Logic Module Parameters
Text
Comms
Cumulative The cumulative output (M) calculated by the module. It can be used to provide an input to other
-1020 to +1020 0 Output M
Output modules by linking it to the required modules.
Label Blank Const -
The rate (R) calculated by the module. It can be used to provide an input to other modules by linking
Rate -1020 to +1020 0 Output R
Reschedule
Defines the time, in seconds, over which the rate is calculated. 0 to 1275 5 Const T
Time
Reset The state of the reset input. 0 or 1 0 Const/Source A
20 20
Scale Factor The value of each input pulse. -10 to +10 1 Const/Source F
Source The value being counted. 0 or 1 0 Const/Source S

IQECO Modules
A2.14.3 IQECO D to A Logic Modules

Module Identifier G
The D to A Logic module converts the digital inputs E, F, G, H, I, J, K, and L into a single analogue output D. The value of (D) represents the binary value of the input bits. E specifies
1 when set, F specifies 2 when set, G specifies 4 when set, H specifies 8 when set, I specifies 16 when set, J specifies 32 when set, K specifies 64 when set, and L specifies 128 when
set. e.g. with the following inputs (E)=1, (F)=0, (G)=1, (H)=0, (I)=1, (J)=0, (K)=0, (L)=0, output (D) would be 21. The module uses the following formula:
D=1x(E) + 2x(F) + 4x(G) + 8x(H) + 16x(I) + 32x(J) + 64x(K) + 128x(L)
A2.14.3.1 IQECO D to A Logic Module Parameters

Bit 0 Specifies (a) in the calculation, adds 1 to the output. 0 or 1 0 Const/Source a
Bit 1 Specifies (b) in the calculation, adds 2 to the output. 0 or 1 0 Const/Source b
Bit 2 Specifies (c) in the calculation, adds 4 to the output. 0 or 1 0 Const/Source c
Bit 3 Specifies (d) in the calculation, adds 8 to the output. 0 or 1 0 Const/Source d
Bit 4 Specifies (e) in the calculation, adds 16 to the output. 0 or 1 0 Const/Source e
Bit 5 Specifies (f) in the calculation, adds 32 to the output. 0 or 1 0 Const/Source f
Bit 6 Specifies (g) in the calculation, adds 64 to the output. 0 or 1 0 Const/Source g
Bit 7 Specifies (h) in the calculation, adds 128 to the output. 0 or 1 0 Const/Source h
20 20
A2.14.4 IQECO Flip Flop Logic Modules
Module Identifier G
Flip Flop Logic modules set the 'Destination D' parameter (D) to '1' when the 'Set' parameter is set to '1' and will keep it set to '1' until the 'Reset' parameter is set to '1'. If both the 'Set'
and 'Reset' parameters are '1' the 'Destination D' parameter (D) is set to '0'. The 'Destination d' parameter (d) is always set to the inverse of the 'Destination D' parameter (D). The
operation can be inverted by setting the 'Invert inputs' parameter to '1'.
The module’s status is retained when the IQECO is powered down and when the IQECO restarts it the module will adopt the status at power down.

IQECO Modules
A2.14.4.1 IQECO Flip Flop Logic Module Parameters


Destination d The inverse of the Destination d' parameter. 0 or 1 0 Output d
Destination D The output (D) of the module. 0 or 1 0 Output D
0 or 1
Disable Module Specifies whether the module is enabled, or disabled. 1=Disabled 0 Const/Source ~
0=Enabled
0 or 1
Invert Inputs Specifies whether the state of the outputs of the module is inverted. 0 = Normal 0 Const P
1 = Inverted
0 or 1
Reset Resets the module’s output (D) to '0'. 0 = no change 0 Source R
1 = Reset
Set When set to '1' sets the modules output (D) to '1' 0 or 1 0 Source S
A2.14.5 IQECO Hours Run Logic Modules
Module Identifier G
The Hours Run Logic module calculates its output (O) as the length of time in hours for which the source bit (S) has been ON since reset input (A) was last set to 1. It also calculates its
other output (N) as 0 or 1 by comparing output (O) with input (I) (which specifies an interval) and if (O)>I, sets (N) to 1 (interval exceeded).
A2.14.5.1 IQECO Hours Run Logic Module Parameters
Text
Comms
Hours Run The cumulative number of hours run output (O) of the module run calculated by the module (O). It can be
-1020 to +1020 0 Output O
Output used to provide an input to other modules by linking it to the required modules.
Interval The maximum number of hours run before an alarm is generated. -1020 to +1020 0 Const/Source I
Interval Limit Indicates when the hours run limit is exceeded. It can be used to provide an input to other modules by 0 or 1
0 Output N
Alarm linking it to the required modules. 1 = Interval exceeded.

IQECO Modules
Text
Comms
Label Blank Const -
0 or 1
Reset Resets the count of hours and alarm condition. 0 Const/Source A
1 = Reset
Source The state of the module whose hours run are being accumulated. 0 or 1 0 Const/Source S
A2.14.6 IQECO Latch Logic Modules
Module Identifier G
Latch Logic modules allow a digital state to be stored when a trigger input is set. The 'Destination D' parameter (D) is set to the value of the 'Source' parameter when the 'Trigger'
parameter is set to '1'. The 'Destination' parameter will remain at that value until the 'Trigger' parameter is set to '1' again. The 'Destination D' parameter (D) can be set to the value of
the 'Default Value' parameter by setting the 'Reset' parameter to '1'.
The module's status is retained when the IQECO is powered down and when the IQECO restarts it the module will adopt the status at power down.
A2.14.6.1 IQECO Latch Logic Module Parameters
Text
Comms
Default
The value to be used when the 'Reset' parameter is set to '1'. 0 or 1 0 Const D
Value
Destination
The output (D) of the module. 0 or 1 0 Output D
D
Label Blank Const -
0 or 1
When set to '1' sets the module's 'Destination D' parameter to the value specified by the 'Default Value'
Reset 0 = no change 0 Source R
parameter.
1 = Reset
Source The value being processed. 0 or 1 0 Source S
Trigger When set to '1' sets the module's output 'D' to the value of the 'Source' parameter. 0 or 1 0 Source T

IQECO Modules
A2.14.7 IQECO Timer Logic Modules

Module Identifier G
The Timer Logic module calculates its output (D) according to the state of its input (S) and the ON delay (N), minimum ON time (M), and OFF delay (F). If the input (S) is set to 1 the
output (D) will not change to 1 until the ON delay time has passed. It will then remain as 1 for at least the length of time specified by the minimum ON time. When the input (S) changes
to 0 the output (D) will only be set to 0 providing the minimum ON time has passed. If an OFF delay is set, the output will stay ON until the OFF delay has passed.
Note: There is a maximum of 10 Timer Logic modules.
A2.14.7.1 IQECO Timer Logic Module Parameters
Text
Comms
Label Blank Const -
Minimum
The minimum time in seconds that the output of a timer module is ON. 0 to 32767 0 Const M
On
On Delay The length of time in seconds after the input of a timer is ON before the output is turned ON. 0 to 32767 0 Const M
Off Delay The length of time in seconds after the input of a timer is OFF before the output is turned OFF. 0 to 32767 0 Const F
Source The value being timed. 0 or 1 0 Const/Source S
A2.15 IQECO Loop Modules
Module Identifier L
Loop modules perform the mathematical calculations that determine, the value of output (D) based on present, and past values of measured variables. The loop module compares the
measured value (P) with the current setpoint. The difference between (P) and the current setpoint is the error. The loop then calculates the value of output (D) to reduce the error. The
choice of setpoint is dependent on the value of the setpoint select parameter (S). If set to 1 the occupied setpoint (O) is used, if set to 0 the unoccupied setpoint (U) is used.
A2.15.1 IQECO Loop Module Parameters
Text
Comms
Alarm Delay (SP IQECO v2.0 or greater. The length of time in seconds that the loop input must be not at the required
0 to 172800 0 Const/Source s1(D)
Deviation) setpoint before a setpoint deviation alarm is generated.

IQECO Modules
Text
Comms
Alarm Group (Setpoint
IQECO v2.0 or greater. Specifies which alarm group the Setpoint Dev alarm is sent. 0 to 500 0 Const s1(G)
Deviation)
0 or 1
Alarm Sent (SP
IQECO v2.0 or greater. Indicates if the setpoint deviation alarm has been sent to the alarm group. 0 = Not sent 0 Status s1(K)
Deviation)
1 = Sent
0 or 1
Clear Alarm Enable
IQECO v2.0 or greater. Specifies whether the setpoint deviation clear alarm is enabled. 1=Enabled 0 Const s1(C)
(SP Deviation)
0=Disabled
Specifies a range above and below the setpoint where the loop output is not changed when the
Deadband 0 to +1020 0 Const B
process variable is in that range. When enabled it filters out minor plant disturbances and noise.
0 or 1
Disable Module Specifies whether the module is enabled, or disabled. 1=Disabled 0 Const/Source ~
0=Enabled
0 or 1
Enabled (SP Deviation) IQECO v2.0 or greater. Specifies whether the setpoint deviation alarm is enabled. 1 = Enabled 0 Source/Const s1(E)
0 = Disabled
The proportional gain of the loop. This defines the way the loop responds to changes in the process
Gain -1020 to +1020 0 Const G
variable. When set to 0 the Loop uses integral only control.
Integral The integral part of the output. 0 to +100 0 Status i
20 20
Integral Time (mins) The time (in minutes) after which the integral term is added to the output. -10 to +10 0 Const I
30-character label for the module. Any ASCII character
Label Blank Const -
0 or 1
Manual Select Specifies whether manual level is imposed on the loop. 0 Const/Source A
1 = Manual level
Manual Level The loop’s manual override setpoint. -1020 to +1020 0 Const/Source L
Occupied Setpoint The loop’s occupied setpoint. Used when setpoint select is set to 1. 20
-10 to +10 20
0 Const/Source O
Output The output of the module. 0 to 100 0 Output D
Process Variable The measured value being controlled. -1020 to +1020 0 Const/Source P
1 to 600
Reschedule Time The interval in seconds between loop output calculations. 0 Const/Source R
0 = Disabled
Setpoint Deviation The maximum loop error that can be reached before a setpoint deviation alarm is generated. -1020 to +1020 0 Const/Source V

IQECO Modules
Text
Comms
0 or 1
0 = Unoccupied
Setpoint Select Specifies whether the loop controls to the occupied or unoccupied setpoint. 0 Const/Source S
Setpoint
1 = Occupied Setpoint
0 or 1
SP Deviation Alarm
The status of the Setpoint Deviation alarm. 1 = Alarm 0 Output s1(S)
State
0 = No Alarm
The length of time in seconds since the SP deviation alarm state started. 0 to +1020 0 Status s1(T)
(SP Deviation)
Unoccupied Setpoint The loop’s unoccupied setpoint. Used when setpoint select is set to '0'. -1020 to +1020 0 Const/Source U

IQECO Modules
A2.16 IQECO Network Modules

IQECO network modules are used to store the parameters specific to the type of physical network being used.
IQECO BACnet Application Network Modules
IQECO MSTP Network Modules
IQECO Type 14 (Wallbus) Network Modules
A2.16.1 IQECO BACnet Application Network Modules
IQECO BACnet Application Network modules store the parameters specific to the BACnet network.
A2.16.1.1 BACnet Application Network Module Parameters
Text
Comms
The controller's address on the BACnet network. It can be specified manually or can be calculated
1 to Calculated
Device Instance automatically using the following formula: Const i
4194303. automatically
0 or 1
Manual Device Specifies whether the device instance is calculated automatically or manually specified. It is not
1 = Manual 0 Const A
Instance recommended that this parameter is changed.
0= Auto
A2.16.2 IQECO BACnet MSTP Network Modules
IQECO BACnet MSTP Network modules store the parameters specific to the MS/TP network.
A2.16.2.1 BACnet MSTP Network Module Parameters
Text
Comms
v1.0 0 to 65534
Max Info
Specifies the maximum number of frames a node can send per rotation of the MS/TP token. v2.0 or greater 1 20 Const f
Frames
to 255
IQECO v2.0 or greater only. The maximum address polled to create a network on the MS/TP trunk. It is not recommended
Max Master 1 to 127 127 Const O
that this parameter is changed from the default.

IQECO Modules
Text
Comms
0, 1, or 2
IQECO v2.0 or greater only. Specifies whether messages on the MS/TP network require a low-level acknowledgement. When
0 = Unconfirmed
Service Class set to 'Confirmed' the device will require a low-level acknowledgement, when set to 'Unconfirmed' an acknowledgement is 0 Const C
1= Unused
not required.
2 = Confirmed
A2.16.3 IQECO Type 14 (Wallbus) Network Modules
Module Identifier n
They store the parameters specific to the Wallbus network.
A2.16.3.1 IQECO Type 14 (Wallbus) Module Parameters
The modules include the following parameters common to most modules: 'Label' - see Common IQECO Module Parameters, plus the following:

Local Address The address of the IQ4 on the Wall-bus network. 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 1 Const a

IQECO Modules
A2.17 IQECO NTD Modules

Module Identifier f
NTD (Non-Trend Device) modules are used to enable IC comms between IQECO controllers and NTDs.
A2.17.1 IQECO NTD Module Parameters
Text
Comms
1 to 119 excluding
Address The Trend network address of the NT. Read only once the device has been created. 0 Const L
Optional 30-character label for the NTD which allows it to be identified either uniquely, or as part of a group. Any ASCII character except
Attribute 2 Blank Const F
It is used in conjunction with the identifier, and the other attributes. \/(){};,:
Attribute 3 Blank Const G
Attribute 4 Blank Const H
Attribute 5 Blank Const I
Attribute 6 Blank Const J
Attribute 7 Blank Const K
Device The device instance of the BACnet device the NTD is to communicate with.
0 to 4194303 0 Const d
Instance Note: If the device instance is not specified you must specify both the network number and MAC address.
Firmware The firmware version of the BACnet device the NTD is to communicate with. Any ASCII character except
- Const -
Version Note: This parameter is for information only in IQSET it is not sent to the controller. \/(){};,:
Identifier 30-character label for the NTD. It is used as the first controller attribute for text communications. Blank Const D
\/(){};,:
The IP address of the BACnet device the NTD is to communicate with.
IP Address - - Const -
Note: This parameter is for information only in IQSET it is not sent to the controller.
1 to 119 excluding
Lan The Trend LAN number of the NTD. 0 Const N

IQECO Modules
Text
Comms
The MAC address in hex of the BACnet device the NTD is to communicate with.
MAC Address Valid MAC in hex address - Const a
Model Name Read only. The model name of the BACnet device the NTD is to communicate with. - Const m
\/(){};,:
A user-friendly label for the NTD. Any ASCII character except
Name Blank Const -
Note: This parameter is for information only in IQSET it is not sent to the controller. \/(){};,:
Network
The network number of the BACnet device the NTD is to communicate with. 0 to 65534 0 Const n
Number
0 or 1
Type Indicates the type of NTD. 0 = Not used 1 Const Y
1 = BACnet
The UDP port of the BACnet device the NTD is to communicate with.
UDP Port - - Const -
The name of the manufacturer of the BACnet device the NTD is to communicate with. Any ASCII character except
Vendor Name - Const v
Note: This parameter is for information only in IQSET it is not sent to the controller. \/(){};,:

IQECO Modules
A2.18 IQECO Plot Modules

Plot modules enable a connectable output value or status to be recorded at defined times to produce a graph or table of values.
IQECO Synchronised Plot Modules
A2.18.1 IQECO Synchronised Plot Modules
Module Identifier P
IQECO Synchronised Plot modules enable analogue or digital values to be recorded at regular intervals. IQECO controllers are limited to a total of 20 synchronised plot modules.
Each plot can store up to 80 values. After the maximum number of values for the plot is exceeded the first value stored will be overwritten
IQECO v1.0
Each plot can store up to 1000 values. After the maximum number of values for the plot is exceeded the first value stored will be overwritten. The controller can store a maximum of
2000 values shared between the all the configured plot modules. E.g. a controller could have two plots configured to store 1000 values each, or 20 plots configured to store 100 values.
It is not necessary for each plot module to have the same number of records e.g. the controller could have one plot storing 100 values, and 10 plots each storing 100 values.
A2.18.1.1 IQECO Synchronised Plot Module Parameters
Text
Comms
Label 30-character user-friendly label for the module. Blank Const $
\/(){};,:
Number of IQECO v2.0 or greater controllers. Specifies the number of records the module can store before the first
0 to 1000 96 Const N
Records is overwritten.
0 to 8
0 = 1 hour
1 = 15 minutes
2 = 24 hours
Period The interval between logs. 3= 1 minute 0 Const P
4 = 5 minutes
5=10 minutes
6=20 minutes
7=30 minutes
8=6 hours
Record Count IQECO v2.0 or greater controllers. The number of records recorded so far. 0 to Number of Records 0 Status R
Source The sensor the plot module is recording. 0 to 9999 0 Source S
Total Record IQECO v2.0 or greater controllers. Indicates the total number of records that have been taken since the
0 to 232-1 0 Status C
Count module started recording values.

IQECO Modules
A2.19 IQECO Sensor Type Modules

A Sensor Type module is a module within a controller that stores information about a certain type of sensor. v1.0 IQECO controllers have only have fixed sensor type modules, v2.0
and greater IQECO have both fixed and configurable Sensor Type modules.
IQECO Fixed Sensor Type Modules
IQECO Configurable Sensor Type Modules
A2.19.1 IQECO Fixed Sensor Type Modules
IQECO Fixed Sensor Type modules are available in all IQECO versions. They have been configured for specific uses and they cannot be changed. IQECO controllers have 11 predefined
sensor type modules as are described below.
Module
Name in IQSET Description
Number
10kTherm DegC This is for the value output of the Trend TB thermistor sensor (10 kohm at 25 °C) with a scaling range of 2.5 °C to 60 °C. It has a conversion
101
TBTS accuracy of ±0.25 °C over the range 10 to 30 °C. The Lower and Upper limits for the Out of Limits alarm are -5 and 50 respectively.
Knob TB 0.5deg This is for the knob output of a standard Trend TBTS/K thermistor sensor (1 kohm to 11 kohm. The Lower and Upper limits for the Out of Limits
102
trim alarm are -0.6 and 0.6 respectively.
This is for fan output of the Trend TBTS/KEF thermistor sensor. The input resistance is set to one of five values and the sensor scaling produces
103 Fan TBTS/KEF 0, 1, 2, 3, and 4 for Off, Lo, Med, Hi, and Auto settings respectively. The Lower and Upper limits for the Out of Limits alar m are 4.5 and 0
respectively.
104 Current 4-20ma This scales the 4 to 20 mA input signal to the value 2 to 10. The Lower and Upper limits for the Out of Limits alarm are 2 and 10 respectively.
105 Volts 0-10V This scales the 0 to 10 V input signal to the value 0 to 10. The Lower and Upper limits for the Out of Limits alarm are 0 and 10 respectively.
Onboard DP
106 Differential pressure sensor input calibrated to give 0 to 2 inwc. The Lower and Upper limits for the Out of Limits alarm are x and y respectively.
1.5inwc
107 Onboard DP 375Pa Differential pressure sensor input calibrated to give 0 to 500 Pa. The Lower and Upper limits for the Out of Limits alarm are x and y respectively.
10k Therm DegF This scaling type is for standard Trend thermistor sensor (10 kohm at 77 °F) with a scaling range of 36.5 °F to 140 °F. It has a conversion accuracy
108
TBTS of ±0.45 °F over the range 10 to 30 °C. The Lower and Upper limits for the Out of Limits alarm are x and y respectively.
10k Therm DegC
109 This is the same as module 101 with out of limits set to 104 and -29.
OAT
10k Therm DegF
110 This is the same as 108 with out of limits set to 220 and -20.
OAT
v2.0 or greater IQECO controllers. This is for fan output of the Trend TBTS/KOF thermistor sensor. The input resistance is set to one of five
111 Fan TBTS KOF values and the sensor scaling produces 0, 1, 2, 3, and 4 for Off, Lo, Med, Hi, and Auto settings respectively. The Lower and Upper limits for the
Out of Limits alarm are 4.5 and 0 respectively.
v2.0 or greater IQECO controllers. This is inputs from a wall mounted display. It does not change the input value. The value is passed unchanged
112 WMD Prescaled
into the strategy.,

IQECO Modules
Note: For v1.0 IQECO v1.0 controllers the modules numbers 101, 102, 103, 104, 105, 106, 107, 108, 109, and 110 are numbered 1, 2, 3, 4, 5, 6, 7, 8, 9 and 10.
A2.19.2 IQECO Configurable Sensor Type Modules
Module Identifier Y
IQECO v2.0 controllers or greater.
Programmable Sensor Type modules enable sensor scaling to be set up to suite the specific application.
A2.19.2.1 IQECO Configurable Sensor Type Module Parameters
I<n>
Inputs 1 to The input points specify the actual value of the electrical input signal from the sensor, or the analogue input value from
-1020 to +1020 0 Const Where <n> =
20 the lookup function module.
input number
0 to 4
0 = Volts (V)
The type of input signal. It should be set to match the hardware-input channel connected to the sensor. If the input is from
1 = Thermistor
a lookup function module, it should be set to Internal Analogue Value. Thermistor input channels may use either
Volts (V)
Input Type Thermistor Volts or Thermistor (KOhms). Normally the sensor characteristics will be given in kilohms so Thermistor 0 Const -
2 = Current (mA)
(KOhms) should be used. However, Thermistor Volts enables a sensor’s characteristics to be produced by measuring
3 = Thermistor
voltage values at the input terminals and entering them in the thermistor volts table.
Ohms (Kohm)
4 = Analogue
Any ASCII
A 30-character reference for the sensor.
Label character except Blank Const -
Note: This parameter is for IQSET use only it is not written to the controller.
\/(){};,:
Specifies the lowest rated value of the sensor (the out of limits alarm lower limit). Not used if the module is used for
Lower Limit -1020 to +1020 0 Const L
Number The sensor type module. 1 to 99 1 Const -
Number of
The number of points used in the conversion table. 2 to 20 Blank Const P
Points
O<n>
The output points specify the value of the output for the corresponding input point, or the analogue input value from the
Outputs 1 to Where <n> =
lookup function module. Up to twenty can be defined. -1020 to +1020 0 Const
20 output
Note: An output point must be defined for each input point.
number
Part The part number for the sensor.
- - Const -
Number Note: This parameter is for IQSET use only it is not written to the controller.

IQECO Modules

The operating range of the sensor.
Range - - Const -
Note: This parameter is for IQSET use only it is not written to the controller.
The method used to interpret the reading from the sensor. It is set to 'Characterise' which allows a sensor’s characteristics
Scaling to be defined by specifying up to twenty scaling points between which it interpolates. This provides higher accuracy than - - Const -
the other scaling types for non-linear characteristics. It is also used for Lookup Function modules.
Specifies the highest rated value of the sensor (the out of limits alarm upper limit). Not used if the module is used for
Upper Limit -1020 to +1020 0 Const U
Lookup Function module.
Note: When entering the values in the Input (X) and Output (Y) boxes the value of the input points (X) must increase, not decrease.

IQECO Modules
A2.20 IQECO Time Modules

Module Identifier T
The Time module stores information about the current date and time.
A2.20.1 IQECO Time Module Parameters
Text
Comms
IQECO v2.0 or greater. The output is set to 1 at the end of each 1-second period for a single execution of the strategy and
1 second Pulse 0 or 1 0 Output j
then reset to 0.
1 minute Pulse The output is set to 1 at the end of each 1-minute period for a single execution of the strategy and then reset to 0. 0 or 1 0 Output k
5 minute Pulse The output is set to 1 at the end of each 5-minute period for a single execution of the strategy and then reset to 0. 0 or 1 0 Output l
10 minute Pulse The output is set to 1 at the end of each 10-minute period for a single execution of the strategy and then reset to 0. 0 or 1 0 Output n
15 minute Pulse The output is set to 1 at the end of each 15-minute period for a single execution of the strategy and then reset to 0. 0 or 1 0 Output o
20 minute Pulse The output is set to 1 at the end of each 20-minute period for a single execution of the strategy and then reset to 0. 0 or 1 0 Output a
30 minute Pulse The output is set to 1 at the end of each 30-minute period for a single execution of the strategy and then reset to 0. 0 or 1 0 Output q
1 hour Pulse The output is set to 1 at the end of each 1-hour period for a single execution of the strategy and then reset to 0. 0 or 1 0 Output r
6 hour Pulse The output is set to 1 at the end of each 6-hour period for a single execution of the strategy and then reset to 0. 0 or 1 0 Output s
24 hour Pulse The output is set to 1 at the end of each 24-hour period for a single execution of the strategy and then reset to 0. 0 or 1 0 Output t
Day The current day of the month. 1 to 31 1 Output D
Hours The current hours value. 0 to 24 0 Output H
Minutes The current minutes value. 0 to 59 0 Output N
Minutes Since 0 to
The number of minutes elapsed since midnight 0 Output m
Midnight 1440
Month The current month. 1 to 12 - Output M
Seconds IQECO v2.0 or greater. The seconds part of the current time. 0 to 59 0 Status C
Year The current year. 0 to 99 - Output Y

IQECO Modules
A2.21 IQECO User Modules

Module Identifier U
IQECO User modules provide the controller's security, and are either enabled or disabled. When enabled no changes will be possible to the IQECO unless a PIN that matches the one in
the controller is supplied.
A2.21.1 IQECO User Module Parameters
Text
Comms
0000 to 9999
IQECO v1.0. The number that must be entered by the user to log on as that user (password). It also enables/disables the 0000
00000 = security Const P
PIN controller's security. It is a 4-digit number.
disabled
IQECO v2.0. The number that must be entered by the user to log on as that user (password). It is a 4-digit number. 0000 to 9999 - - -
0 or 100
IQECO v1.0 Enables/disables the controller's security. 0 = disabled 0
PIN Level 100 = Enabled Const L
IQECO v2.0 or greater Always set to 100. 100 100

A3 Command Line Commands

This section lists all the commands that can be used in the Command Line toolbar.
A3.1 Modules
Module Command to Type
ABS Function Module F24
ABS Function Module FABS
Add Function Module F20
Add Function Module ADD
Add Function Module FADD
Adder/Scaler Function Module ADDER
Adder/Scaler Function Module FAD
Adder/Scaler Function Module F8
Adjustment Knob Module ADJUST
Adjustment Knob Module ADJUSTMENT KNOB
Adjustment Knob Module KA
Alarm Destination Module ALARM DEST
Alarm Destination Module DEST
Alarm Group Module ALARM GROUP
Alarm Group Module GROUP
Alarm Route Module ALARM ROUTE
Alarm Route Module ROUTE
Analogue Driver Module ANALOGUE
Analogue Driver Module D2
Analogue Driver Module DA
Analogue to Digital Function Module A TO D
Analogue to Digital Function Module FA/
Analogue to Digital Function Module F18
Average Function Module AVERAGE
Average Function Module F13
Average Function Module FAV
Binary Hysteresis Driver Module BIN HYST
Binary Switch Driver Module D5
Combination Logic Module COMB
Combination Logic Module G1
Combination Logic Module GCOM
Comparator Function Module FC
Comparator Function Module COMPARATOR
Comparator Function Module F15
Counter Logic Module COUNTER
Counter Logic Module GC
D to A Logic Module D TO A
D to A Logic Module G8
D to A Logic Module GDTO
Delay Logic Module G5


Delay Logic Module DELAY
Delay Logic Module GD
Digital Driver Module D1
Digital Driver Module DD
Digital Driver Module DIGITAL
Digital Input Module DIGIN
Digital Input Module DIGITAL INPUT
Digital Input Module I
Divide Function Module DIVIDE
Divide Function Module F10
Dummy IC Comms Module DUMMY
Enthalpy Function Module ENTHALPY
Enthalpy Function Module F16
Enthalpy Function Module FE
External Digital Sensor Module EXT DIG SEN
External Digital Sensor Module S3
External Sensor Module EXT SEN
External Sensor Module S1
Fan Out Logic Module G7
Fan Out Logic Module FANOUT
Fan Out Logic Module GF
Filter Function Module F1
Filter Function Module FF
Filter Function Module FILTER
Gate Function Module F14
Gate Function Module FG
Gate Function Module GATE
Hours Run Logic Module G6
Hours Run Logic Module GH
Hours Run Logic Module HOURS RUN
Hysteresis Band Function Module F17
Hysteresis Band Function Module FH
Hysteresis Band Function Module HYSTERESIS
Hysteresis Limits Function Module F21
Hysteresis Limits Function Module FHL
Hysteresis Limits Function Module HYSTERESIS LIMITS
Internal Digital Sensor Module INT DIG SEN
Internal Digital Sensor Module S4
Internal Sensor Module INT SEN
Internal Sensor Module INTERNAL SENSOR
Internal Sensor Module S2
Knob Module K
Knob Module KNOB
Limit at Function Module F4
Limit at Function Module FLA
Limit at Function Module LIMIT AT


Limit to Function Module F5
Limit to Function Module FLT
Limit to Function Module LIMIT TO
Log Function Module F6
Log Function Module FL
Log Function Module LOG
Lookup Function Module F19
Lookup Function Module FLK
Lookup Function Module LOOKUP
Loop Module L
Loop Module LOOP
Maximum Function Module F12
Maximum Function Module FMAX
Maximum Function Module MAXIMUM
Minimum Function Module F11
Minimum Function Module FMIN
Minimum Function Module MINIMUM
Multiply Function Module F9
Multiply Function Module FMU
Multiply Function Module MULTIPLY
Plot Module P
Plot Module PLOT
Power Function Module F23
Power Function Module FPOW
Power Function Module POWER
Proximity Function Module PROXIMITY
Proximity Function Module F22
Proximity Function Module FPROX
Raise/Lower Continuous Driver Module RAISE LOWER CONT
Raise/Lower Continuous Driver Module D7
Raise/Lower Continuous Driver Module DRLC
Raise/Lower End Driver Module DRLE
Raise/Lower End Driver Module RAISE LOWER END
Readback Logic Module G3
Readback Logic Module GR
Readback Logic Module READBACK
Redraw the screen REDRAW
Rescale from Function Module F2
Rescale from Function Module FRF
Rescale from Function Module RESCALE FROM
Rescale to Function Module F3
Rescale to Function Module FRT
Rescale to Function Module RESCALE TO
Schedule Offset module H


Schedule Offset module SCHED
Schedule Offset module SCHEDULE
Square Root Function Module F7
Square Root Function Module FSR
Square Root Function Module ROOT
Switch Module SWITCH
Switch Module W
Time Proportional + O/R Driver Module TIME PROP ORIDE
Time Proportional + O/R Driver Module TPO
Time Proportional Driver Module D3
Time Proportional Driver Module DTP
Time Proportional Driver Module TIME PROP
Timer Logic Module G2
Timer Logic Module GT
Timer Logic Module TIMER
TRIG Function Module F26
TRIG Function Module FTRG
TRIG Function Module TRIG
TRUNC Function Module F25
TRUNC Function Module FTR
TRUNC Function Module TRUNC
Time Schedule Module TIME
Time Schedule Module TIME ZONE
Time Schedule Module TZ

A3.2 IQSET Commands

IQSET Command Command to Type
Draw a line LINE
Draw a rectangle RECTANGLE
Draw a rectangle SQUARE
Draw an ellipse CIRCLE
Draw an ellipse ELLIPSE
Draw text TEXT
Fill the window with the used area of the strategy
EXTENT
page
Goto the next page NEXT
Goto the previous page PREV
Zoom to a specific area Z
Zoom to a specific area ZOOM


Keyboard Short Cuts
A4 Keyboard Short Cuts

The keyboard short cuts enable quick access to some of IQSET's features.
Shortcut Description
CTRL+A Select all
CTRL+ALT+I Create LDF
CTRL+C Copy
CTRL+F Displays the current strategy page full screen.
CTRL+L Displays the System View
CTRL+M Select the Command Line toolbar
CTRL+N Navigate window
CTRL+O Display version info
CTRL+T Display the Tracker Window
CTRL+U Deselect all
CTRL+V Paste
CTRL+X Cut
ESC Cancel edit
F1 Help
F3 Zoom
F4 Zoom to 100%
F5 Display top left
F6 Display top right
F7 Display bottom left
F8 Display bottom right

Keyboard Short Cuts

A5 3rd Party Software Licences

Honeywell product includes software code developed by third parties subject to their own terms and conditions. As
applicable, the terms of the third party software are available to you below:
A5.1 License Text for the Microsoft Speech Platform - Runtime (Version 11)
MICROSOFT SOFTWARE LICENSE TERMS MICROSOFT SPEECH PLATFORM RUNTIME 11
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates)
and you. Please read them. They apply to the software named above, which includes the media on which you received
it, if any.
The terms also apply to any Microsoft
 updates,
 supplements,
 Internet-based services, and
 support services for this software, unless other terms accompany those items. If so, those terms apply.
By using the software, you accept these terms. If you do not accept them, do not use the software.
If you comply with these license terms, you have the rights below.
1. INSTALLATION AND USE RIGHTS. You may install and use any number of copies of the software on your
devices to design, develop and test your programs.
2. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS. a. Distributable Code. You are
permitted to distribute the software in object code form (the “Distributable Code”) in programs you develop if
you comply with the terms below.
i. Right to Use and Distribute. The code and text files listed below are “Distributable Code.”
 Third Party Distribution. You may permit distributors of your programs to copy and distribute the
Distributable Code as part of those programs.
ii. Distribution Requirements. For any Distributable Code you distribute, you must add significant primary
functionality to it in your programs; for any Distributable Code having a filename extension of .lib, distribute
only the results of running such Distributable Code through a linker with your program; distribute
Distributable Code included in a setup program only as part of that setup program without modification;
require distributors and external end users to agree to terms that protect it at least as much as this agreement;
display your valid copyright notice on your programs; and indemnify, defend, and hold harmless Microsoft
from any claims, including attorneys’ fees, related to the distribution or use of your programs. iii. Distribution
Restrictions. You may not alter any copyright, trademark or patent notice in the Distributable Code; use
Microsoft’s trademarks in your programs’ names or in a way that suggests your programs come from or are
endorsed by Microsoft; distribute Distributable Code to run on a platform other than the Windows platform;
include Distributable Code in malicious, deceptive or unlawful programs; or modify or distribute the source
code of any Distributable Code so that any part of it becomes subject to an Excluded License. An Excluded
License is one that requires, as a condition of use, modification or distribution, that the code be disclosed or
distributed in source code form; or others have the right to modify it.
3. SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use
the software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this
limitation, you may use the software only as expressly permitted in this agreement. In doing so, you must
comply with any technical limitations in the software that only allow you to use it in certain ways. You may
not disclose the results of any benchmark tests of the software to any third party without Microsoft’s prior
written approval; work around any technical limitations in the software; reverse engineer, decompile or
disassemble the software, except and only to the extent that applicable law expressly permits, despite this
limitation; make more copies of the software than specified in this agreement or allowed by applicable law,
despite this limitation; publish the software for others to copy; rent, lease or lend the software; transfer the
software or this agreement to any third party; or
4. BACKUP COPY. You may make one backup copy of the software. You may use it only to reinstall the
software.
5. DOCUMENTATION. Any person that has valid access to your computer or internal network may copy and
use the documentation for your internal, reference purposes.

6. EXPORT RESTRICTIONS. The software is subject to United States export laws and regulations. You must
comply with all domestic and international export laws and regulations that apply to the software. These laws
include restrictions on destinations, end users and end use. For additional information, see
www.microsoft.com/exporting.
7. SUPPORT SERVICES. Because this software is “as is,” we may not provide support services for it.
8. ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-based services
and support services that you use, are the entire agreement for the software and support services.
9. APPLICABLE LAW.
a. United States. If you acquired the software in the United States, Washington state law governs the
interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles.
The laws of the state where you live govern all other claims, including claims under state consumer protection
laws, unfair competition laws, and in tort.
b. Outside the United States. If you acquired the software in any other country, the laws of that country apply.
10. LEGAL EFFECT. This agreement describes certain legal rights. You may have other rights under the laws
of your country. You may also have rights with respect to the party from whom you acquired the software.
This agreement does not change your rights under the laws of your country if the laws of your country do
not permit it to do so.
11. DISCLAIMER OF WARRANTY. The software is licensed “as-is.” You bear the risk of using it. Microsoft
gives no express warranties, guarantees or conditions. You may have additional consumer rights under your
local laws which this agreement cannot change. To the extent permitted under your local laws, Microsoft
excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.
12. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. You can recover from Microsoft
and its suppliers only direct damages up to U.S. $5.00. You cannot recover any other damages, including
consequential, lost profits, special, indirect or incidental damages. This limitation applies to anything related
to the software, services, content (including code) on third party Internet sites, or third party programs; and
claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other
tort to the extent permitted by applicable law. It also applies even if Microsoft knew or should have known
about the possibility of the damages. The above limitation or exclusion may not apply to you because your
country may not allow the exclusion or limitation of incidental, consequential or other damages.
Please note: As this software is distributed in Quebec, Canada, some of the clauses in this agreement are provided
below in French. Remarque : Ce logiciel étant distribué au Québec, Canada, certaines des clauses dans ce contrat sont
fournies ci-dessous en français. EXONÉRATION DE GARANTIE. Le logiciel visé par une licence est offert « tel
quel ». Toute utilisation de ce logiciel est à votre seule risque et péril. Microsoft n’accorde aucune autre garantie
expresse. Vous pouvez bénéficier de droits additionnels en vertu du droit local sur la protection des consommateurs,
que ce contrat ne peut modifier. La ou elles sont permises par le droit locale, les garanties implicites de qualité
marchande, d’adéquation à un usage particulier et d’absence de contrefaçon sont exclues. LIMITATION DES
DOMMAGES-INTÉRÊTS ET EXCLUSION DE RESPONSABILITÉ POUR LES DOMMAGES. Vous pouvez
obtenir de Microsoft et de ses fournisseurs une indemnisation en cas de dommages directs uniquement à hauteur de
5,00 $ US. Vous ne pouvez prétendre à aucune indemnisation pour les autres dommages, y compris les dommages
spéciaux, indirects ou accessoires et pertes de bénéfices. Cette limitation concerne : tout ce qui est relié au logiciel,
aux services ou au contenu (y compris le code) figurant sur des sites Internet tiers ou dans des programmes tiers ; et
les réclamations au titre de violation de contrat ou de garantie, ou au titre de responsabilité stricte, de négligence ou
d’une autre faute dans la limite autorisée par la loi en vigueur. Elle s’applique également, même si Microsoft
connaissait ou devrait connaître l’éventualité d’un tel dommage. Si votre pays n’autorise pas l’exclusion ou la
limitation de responsabilité pour les dommages indirects, accessoires ou de quelque nature que ce soit, il se peut que
la limitation ou l’exclusion ci-dessus ne s’appliquera pas à votre égard. EFFET JURIDIQUE. Le présent contrat décrit
certains droits juridiques. Vous pourriez avoir d’autres droits prévus par les lois de votre pays. Le présent contrat ne
modifie pas les droits que vous confèrent les lois de votre pays si celles-ci ne le permettent pas.
License text for the Microsoft Speech Platform - Runtime Languages (Version 11)
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY FOR MICROSOFT SPEECH PLATFORM
RUNTIME AND/OR MICROSOFT SPEECH PLATFORM SDK PLEASE NOTE:
Microsoft Corporation (or based on where you live, one of its affiliates) licenses this supplement to you. You may use
it with each validly licensed copy of Microsoft Speech Platform Runtime and/or Microsoft Speech Platform SDK
software (for which this supplement is applicable) (the “software”). You may not use the supplement if you do not
have a license for the software. The license terms for the software apply to your use of this supplement. Microsoft
provides support services for the supplement as described at www.support.microsoft.com/common/international.aspx.

MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY FÖR MICROSOFT SPEECH PLATFORM
RUNTIME OCH/ELLER MICROSOFT SPEECH PLATFORM SDK OBS! Microsoft Corporation (eller beroende
på var du bor, ett av dess koncernbolag) licensierar detta tillägg till dig. Du får använda det med varje giltigt licensierat
exemplar av Microsoft Speech Platform Runtime och/eller Microsoft Speech Platform SDK programvara (som
tillägget gäller för) (”programvaran”). Du får endast använda tillägget om du innehar en licens för programvaran.
Licensvillkoren för programvaran gäller för din användning av detta tillägg. Microsoft tillhandahåller supporttjänster
för tillägget enligt beskrivningen på www.support.microsoft.com/common/international.aspx.
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY ДЛЯ MICROSOFT SPEECH PLATFORM
RUNTIME И/ИЛИ MICROSOFT SPEECH PLATFORM SDK ПРИМЕЧАНИЕ. Корпорация Майкрософт (или
одно из ее аффилированных лиц, в зависимости от места вашего проживания) предоставляет вам данное
дополнение к лицензии. Вы имеете право использовать его с каждой лицензионной копией программного
обеспечения Майкрософт Speech Platform Runtime и/или Microsoft Speech Platform SDK (к которому относится
это дополнение) («программное обеспечение»). Вы не имеете права использовать дополнение, если у вас нет
лицензии на программное обеспечение. Условия лицензии на использование программного обеспечения
распространяются и на использование вами данного дополнения. Корпорация Майкрософт предоставляет
техническую поддержку дополнения, как указано на веб-узле
www.support.microsoft.com/common/international.aspxhttp://www.support.microsoft.com/common/international.as
px.
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY PARA MICROSOFT SPEECH PLATFORM
RUNTIME Y/O MICROSOFT SPEECH PLATFORM SDK TENGA EN CUENTA: Microsoft Corporation (o, en
función del lugar en el que usted resida, una de las sociedades de su grupo) le concede a usted la licencia de este
suplemento. Podrá utilizarlo con cada copia licenciada válida del software de Microsoft Speech Platform Runtime y/o
Microsoft Speech Platform SDK (aplicable para el presente suplemento) (el “software”). Queda prohibida la
utilización del software si no dispone de una licencia para el mismo. Los términos de la licencia para el software se
aplican al uso que usted haga de este suplemento. Microsoft presta servicios de soporte técnico para el suplemento,
tal y como se describe en www.support.microsoft.com/common/international.aspx. MICROSOFT SPEECH
RECOGNITION ENGINE - TELEPHONY PARA O MICROSOFT SPEECH PLATFORM RUNTIME E/OU
MICROSOFT SPEECH PLATFORM SDK OBSERVE QUE: A Microsoft Corporation (ou de acordo com o local
onde você reside, uma de suas afiliadas) licencia este suplemento para você. Você poderá usá-lo com cada cópia válida
licenciada do software da Microsoft Speech Platform Runtime e/ou Microsoft Speech Platform SDK (ao qual este
suplemento é aplicável) (o “software”). Você não poderá usar o suplemento se não tiver uma licença para o software.
Os termos da licença do software se aplicam ao uso deste suplemento. A Microsoft fornece serviços de suporte para
o suplemento conforme descrito em www.support.microsoft.com/common/international.aspx.
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY PARA MICROSOFT SPEECH PLATFORM
RUNTIME E/OU MICROSOFT SPEECH PLATFORM SDK NOTA: A Microsoft Corporation (ou dependendo do
país de residência do Adquirente, uma das suas afiliadas) licencia este suplemento para o Adquirente. Poderá utilizá-
lo com cada cópia licenciada de modo válido do software Microsoft Speech Platform Runtime e/ou Microsoft Speech
Platform SDK (ao qual se aplica este suplemento) (o “software”). O Adquirente não poderá utilizar este suplemento
se não tiver uma licença para o software. Os termos de licença para o software aplicam-se à utilização deste suplemento
por parte do Adquirente. A Microsoft fornece suporte técnico para o suplemento, conforme descrito em
www.support.microsoft.com/common/international.aspx.
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY DLA MICROSOFT SPEECH PLATFORM
RUNTIME I/LUB MICROSOFT SPEECH PLATFORM SDK UWAGA: Microsoft Corporation (lub w zależności
od miejsca zamieszkania licencjobiorcy jeden z jej podmiotów stowarzyszonych) udziela licencjobiorcy licencji na to
uzupełnienie. Licencjobiorca może go używać z każdą kopią oprogramowania Microsoft Speech Platform Runtime
i/lub Microsoft Speech Platform SDK, na którą uzyskał ważną licencję (do którego uzupełnienie się stosuje)
(„oprogramowanie”). Licencjobiorca nie może używać uzupełnienia, jeśli nie ma licencji na oprogramowanie.
Postanowienia licencyjne dotyczące oprogramowania stosują się do używania tego uzupełnienia. Microsoft świadczy
usługi pomocy technicznej dla uzupełnienia zgodnie z opisem znajdującym się pod adresem
RUNTIME OG/ELLER MICROSOFT SPEECH PLATFORM SDK MERK: Microsoft Corporation (eller et av dets
tilknyttede selskaper, avhengig av hvor du bor) lisensierer dette tillegget til deg. Du kan bruke det sammen med alle
gyldig lisensierte kopier av Microsoft Speech Platform Runtime og/eller Microsoft Speech Platform SDK
programvare (som dette tillegget gjelder for) (“programvaren”). Du har ikke rett til å bruke tillegget hvis du ikke har
lisens for programvaren. Lisensvilkårene for programvaren gjelder for din bruk av dette tillegget. Microsoft tilbyr
brukerstøtte for tillegget, som beskrevet på www.support.microsoft.com/common/international.aspx.

RUNTIME および/または MICROSOFT SPEECH PLATFORM SDK 注意 : Microsoft Corporation (以下「マイ
クロソフト」といいます) は、本追加ソフトウェアに関するライセンスをお客様に供与します。お客様は
、Microsoft Speech Platform Runtime および/または Microsoft Speech Platform SDK ソフトウェア (本追加ソ
フトウェアの対象となっているもの) の有効なライセンス取得済み複製 (以下「本ソフトウェア」といい
ます) 1 つごとに、これを使用できます。本ソフトウェアのライセンスを取得していない場合は、本追加
ソフトウェアを使用することはできません。本ソフトウェアのライセンス条項は、本追加ソフトウェア
の使用にも適用されます。マイクロソフトは、本追加ソフトウェアに対し
www.support.microsoft.com/common/international.aspx で説明されるサポートサービスを提供します。
RUNTIME 및/또는 MICROSOFT SPEECH PLATFORM SDK 참고: Microsoft Corporation(또는 거주 지역에
따라 계열사 중 하나)은 귀하에게 본 추가 구성 요소의 사용권을 부여합니다. 적법하게 사용권이 허여된
Microsoft Speech Platform Runtime 및/또는 Microsoft Speech Platform SDK 소프트웨어의 각 사본에 본 추가
구성 요소를(본 추가 구성 요소를 사용할 수 있는) (“소프트웨어”)와 함께 사용할 수 있습니다. 해당
소프트웨어 사용권이 없는 경우에는 추가 구성 요소도 사용할 수 없습니다. 본 추가 구성 요소 사용 시 해당
소프트웨어 사용권 조항 내용이 적용됩니다. Microsoft는
www.support.microsoft.com/common/international.aspx에 기술된 대로 추가 구성 요소에 대한 지원 서비스를
제공합니다.
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY PER MICROSOFT SPEECH PLATFORM
RUNTIME E/O MICROSOFT SPEECH PLATFORM SDK ATTENZIONE: Microsoft Corporation (o, in base al
luogo di residenza del licenziatario, una delle sue consociate) concede in licenza al licenziatario il presente
supplemento. Il licenziatario potrà utilizzarlo con ciascuna copia validamente concessa in licenza del software
Microsoft Speech Platform Runtime e/o Microsoft Speech Platform SDK (per il quale il presente supplemento è
applicabile) (il “software”). Il licenziatario non potrà utilizzare il supplemento qualora non disponga di una licenza
per il software. Le condizioni di licenza per il software si applicano all’utilizzo del presente supplemento da parte del
licenziatario. Microsoft fornisce servizi di supporto tecnico per il supplemento come descritto all’indirizzo
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY FÜR MICROSOFT SPEECH PLATFORM
RUNTIME UND/ODER MICROSOFT SPEECH PLATFORM SDK BITTE BEACHTEN SIE FOLGENDES:
Microsoft Corporation (oder eine andere Microsoft-Konzerngesellschaft, wenn diese an dem Ort, an dem Sie die
Software erwerben, die Software lizenziert) lizenziert diese Softwareergänzung an Sie. Sie sind berechtigt, die
Softwareergänzung mit jeder ordnungsgemäß lizenzierten Kopie von Software Microsoft Speech Platform Runtime
und/oder Microsoft Speech Platform SDK (für die diese Softwareergänzung anwendbar ist) (die „Software“) zu
verwenden. Sie sind nicht berechtigt, die Softwareergänzung zu verwenden, wenn Sie keine Lizenz für die Software
haben. Die Lizenzbestimmungen für die Software gelten für Ihre Verwendung dieser Softwareergänzung. Microsoft
stellt Supportleistungen für die Softwareergänzung bereit, die unter
www.support.microsoft.com/common/international.aspx beschrieben werden.
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY -OHJELMISTON MICROSOFT SPEECH
PLATFORM RUNTIME JA/TAI MICROSOFT SPEECH PLATFORM SDK HUOMAUTUS: Microsoft
Corporation (tai asiakkaan asuinpaikan mukaan määräytyvä Microsoft Corporationin konserniyhtiö) myöntää
asiakkaalle tämän täydennysosan käyttöoikeudet. Asiakas saa käyttää sitä kaikkien niiden Microsoft Speech Platform
Runtime ja/tai Microsoft Speech Platform SDK -ohjelmistosta tehtyjen kopioiden kanssa, joihin on voimassa olevat
käyttöoikeudet (jota tämä täydennysosa täydentää). Asiakas ei saa käyttää täydennysosaa, jos asiakkaalla ei ole
ohjelmistoon käyttöoikeutta. Täydennysosan käyttöön sovelletaan ohjelmiston käyttöoikeusehtoja. Microsoftin tähän
täydennysosaan tarjoamat tukipalvelut löytyvät osoitteessa www.support.microsoft.com/common/international.aspx.
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY POUR MICROSOFT SPEECH PLATFORM
RUNTIME ET/OU MICROSOFT SPEECH PLATFORM SDK REMARQUE : Microsoft Corporation (ou en
fonction du lieu où vous vivez, l’un de ses affiliés) vous accorde une licence pour ce supplément. Vous pouvez utiliser
une copie de ce supplément avec chaque copie concédée sous licence du logiciel Microsoft Speech Platform Runtime
et/ou Microsoft Speech Platform SDK (auquel s’applique ce supplément) (le « logiciel »). Vous n’êtes pas autorisé à
utiliser ce supplément si vous n’êtes pas titulaire d’une licence pour le logiciel. Les conditions de licence pour le
logiciel s’appliquent à l’utilisation de ce supplément. Microsoft fournit des services d’assistance technique pour le
supplément disponibles sur le site www.support.microsoft.com/common/international.aspx.

MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY VOOR MICROSOFT SPEECH PLATFORM
RUNTIME EN/OF MICROSOFT SPEECH PLATFORM SDK LET OP: Microsoft Corporation (of, afhankelijk van
waar u woont, een van haar gelieerde ondernemingen) geeft dit supplement aan u in licentie. U mag dit gebruiken bij
elk geldig in licentie gegeven exemplaar van Microsoft Speech Platform Runtime en/of Microsoft Speech Platform
SDK software (waarop deze aanvulling van voorwaarden van toepassing is) (de "software"). U mag dit supplement
niet gebruiken als u geen licentie hebt voor de software. De licentievoorwaarden voor de software zijn van toepassing
op uw gebruik van dit supplement. Microsoft biedt productondersteuning voor dit supplement zoals wordt beschreven
op www.support.microsoft.com/common/international.aspx.
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY TIL MICROSOFT SPEECH PLATFORM
RUNTIME OG/ELLER MICROSOFT SPEECH PLATFORM SDK BEMÆRK: Microsoft Corporation (eller,
afhængigt af hvor De bor, et af dets associerede selskaber) licenserer dette tillæg til Dem. De må bruge den sammen
med hver gyldigt licenseret kopi af Microsoft Speech Platform Runtime v10.1 og/eller Microsoft Speech Platform
SDK v10.1 softwaren (som dette tillæg er gældende for) (“softwaren”). De må ikke bruge dette tillæg, hvis De ikke
har licens til softwaren. Licensvilkårene for softwaren gælder for brug af dette tillæg. Microsoft yder support til
tillægget, som beskrevet på www.support.microsoft.com/common/international.aspx.
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY（适用于 MICROSOFT SPEECH PLATFORM
RUNTIME 和/或 MICROSOFT SPEECH PLATFORM SDK 请注意：Microsoft Corporation（或 Microsoft
Corporation 在您所在地的关联公司）现授予您本补充程序的许可证。您可以随 Microsoft Speech Platform
Runtime v10.1 和/或 Microsoft Speech Platform SDK v10.1 软件（即本补充程序适用的软件）（“软件”）的每
份获得有效许可的副本使用一份本补充程序。如果您没有软件的许可证，则不得使用本补充程序。该软件
的许可条款在您使用本补充程序时适用。Microsoft 为本补充程序提供支持服务；相关说明请参见
www.support.microsoft.com/common/international.aspx。
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY 之 MICROSOFT SPEECH PLATFORM
RUNTIME 及/或 MICROSOFT SPEECH PLATFORM SDK 請注意：Microsoft 公司 (或其關係企業，視貴用
戶所居住的地點而定) 授權貴用戶使用本增補程式。貴用戶擁有之每份有效授權的 Microsoft 軟體(適用
本增補程式之軟體) （「軟體」），均得使用一份 Microsoft Speech Platform Runtime 及/或 Microsoft Speech
Platform SDK 增補程式。若貴用戶未取得軟體授權，即不得使用本增補程式。使用本增補程式時，亦須
遵守軟體之授權條款。Microsoft 為「增補程式」提供支援服務之相關說明，請參閱
MICROSOFT SPEECH RECOGNITION ENGINE - TELEPHONY PER A MICROSOFT SPEECH PLATFORM
RUNTIME I/O MICROSOFT SPEECH PLATFORM SDK CAL TENIR EN COMPTE QUE: Microsoft Corporation
(o segons on visqueu, una de les seves filials) us autoritza a utilitzar aquest complement Podeu utilitzar-lo amb totes
les còpies vàlidament llicenciades dels programaris Microsoft Speech Platform Runtime i/o Microsoft Speech
Platform SDK (per als quals aquest complement és vàlid) (el “programari”). No podeu utilitzar el complement si no
disposeu d'una llicència per al programari. Els termes de la llicència per al programari s'apliquen a l'ús que feu del
complement. Microsoft proporciona serveis de suport tècnic per a aquest complement, tal com es descriu a la pàgina
MICROSOFT TEXT-TO-SPEECH - TELEPHONY FOR MICROSOFT SPEECH PLATFORM RUNTIME
AND/OR MICROSOFT SPEECH PLATFORM SDK PLEASE NOTE:
Microsoft Corporation (or based on where you live, one of its affiliates) licenses this supplement to you. You may use
it with each validly licensed copy of Microsoft Speech Platform Runtime and/or Microsoft Speech Platform SDK
software (for which this supplement is applicable) (the “software”). You may not use the supplement if you do not
have a license for the software. The license terms for the software apply to your use of this supplement. Microsoft
provides support services for the supplement as described at www.support.microsoft.com/common/international.aspx.
MICROSOFT TEXT-TO-SPEECH - TELEPHONY FÖR MICROSOFT SPEECH PLATFORM RUNTIME
OCH/ELLER MICROSOFT SPEECH PLATFORM SDK OBS! Microsoft Corporation (eller beroende på var du bor,
ett av dess koncernbolag) licensierar detta tillägg till dig. Du får använda det med varje giltigt licensierat exemplar av
Microsoft Speech Platform Runtime och/eller Microsoft Speech Platform SDK programvara (som tillägget gäller för)
(”programvaran”). Du får endast använda tillägget om du innehar en licens för programvaran. Licensvillkoren för
programvaran gäller för din användning av detta tillägg. Microsoft tillhandahåller supporttjänster för tillägget enligt
beskrivningen på www.support.microsoft.com/common/international.aspx.

MICROSOFT TEXT-TO-SPEECH - TELEPHONY ДЛЯ MICROSOFT SPEECH PLATFORM RUNTIME И/ИЛИ
MICROSOFT SPEECH PLATFORM SDK ПРИМЕЧАНИЕ. Корпорация Майкрософт (или одно из ее
аффилированных лиц, в зависимости от места вашего проживания) предоставляет вам данное дополнение к
лицензии. Вы имеете право использовать его с каждой лицензионной копией программного обеспечения
Майкрософт Speech Platform Runtime и/или Microsoft Speech Platform SDK (к которому относится это
дополнение) («программное обеспечение»). Вы не имеете права использовать дополнение, если у вас нет
лицензии на программное обеспечение. Условия лицензии на использование программного обеспечения
распространяются и на использование вами данного дополнения. Корпорация Майкрософт предоставляет
техническую поддержку дополнения, как указано на веб-узле
www.support.microsoft.com/common/international.aspxhttp://www.support.microsoft.com/common/international.as
px.
MICROSOFT TEXT-TO-SPEECH - TELEPHONY PARA MICROSOFT SPEECH PLATFORM RUNTIME Y/O
MICROSOFT SPEECH PLATFORM SDK TENGA EN CUENTA: Microsoft Corporation (o, en función del lugar
en el que usted resida, una de las sociedades de su grupo) le concede a usted la licencia de este suplemento. Podrá
utilizarlo con cada copia licenciada válida del software de Microsoft Speech Platform Runtime y/o Microsoft Speech
Platform SDK (aplicable para el presente suplemento) (el “software”). Queda prohibida la utilización del software si
no dispone de una licencia para el mismo. Los términos de la licencia para el software se aplican al uso que usted haga
de este suplemento. Microsoft presta servicios de soporte técnico para el suplemento, tal y como se describe en
MICROSOFT TEXT-TO-SPEECH - TELEPHONY PARA O MICROSOFT SPEECH PLATFORM RUNTIME
E/OU MICROSOFT SPEECH PLATFORM SDK OBSERVE QUE: A Microsoft Corporation (ou de acordo com o
local onde você reside, uma de suas afiliadas) licencia este suplemento para você. Você poderá usá-lo com cada cópia
válida licenciada do software da Microsoft Speech Platform Runtime e/ou Microsoft Speech Platform SDK (ao qual
este suplemento é aplicável) (o “software”). Você não poderá usar o suplemento se não tiver uma licença para o
software. Os termos da licença do software se aplicam ao uso deste suplemento. A Microsoft fornece serviços de
suporte para o suplemento conforme descrito em www.support.microsoft.com/common/international.aspx.
MICROSOFT TEXT-TO-SPEECH - TELEPHONY PARA MICROSOFT SPEECH PLATFORM RUNTIME E/OU
MICROSOFT SPEECH PLATFORM SDK NOTA: A Microsoft Corporation (ou dependendo do país de residência
do Adquirente, uma das suas afiliadas) licencia este suplemento para o Adquirente. Poderá utilizá-lo com cada cópia
licenciada de modo válido do software Microsoft Speech Platform Runtime e/ou Microsoft Speech Platform SDK (ao
qual se aplica este suplemento) (o “software”). O Adquirente não poderá utilizar este suplemento se não tiver uma
licença para o software. Os termos de licença para o software aplicam-se à utilização deste suplemento por parte do
Adquirente. A Microsoft fornece suporte técnico para o suplemento, conforme descrito em
MICROSOFT TEXT-TO-SPEECH - TELEPHONY DLA MICROSOFT SPEECH PLATFORM RUNTIME I/LUB
MICROSOFT SPEECH PLATFORM SDK UWAGA: Microsoft Corporation (lub w zależności od miejsca
zamieszkania licencjobiorcy jeden z jej podmiotów stowarzyszonych) udziela licencjobiorcy licencji na to
uzupełnienie. Licencjobiorca może go używać z każdą kopią oprogramowania Microsoft Speech Platform Runtime
i/lub Microsoft Speech Platform SDK, na którą uzyskał ważną licencję (do którego uzupełnienie się stosuje)
(„oprogramowanie”). Licencjobiorca nie może używać uzupełnienia, jeśli nie ma licencji na oprogramowanie.
Postanowienia licencyjne dotyczące oprogramowania stosują się do używania tego uzupełnienia. Microsoft świadczy
usługi pomocy technicznej dla uzupełnienia zgodnie z opisem znajdującym się pod adresem
MICROSOFT TEXT-TO-SPEECH - TELEPHONY FOR MICROSOFT SPEECH PLATFORM RUNTIME
OG/ELLER MICROSOFT SPEECH PLATFORM SDK MERK: Microsoft Corporation (eller et av dets tilknyttede
selskaper, avhengig av hvor du bor) lisensierer dette tillegget til deg. Du kan bruke det sammen med alle gyldig
lisensierte kopier av Microsoft Speech Platform Runtime og/eller Microsoft Speech Platform SDK programvare (som
dette tillegget gjelder for) (“programvaren”). Du har ikke rett til å bruke tillegget hvis du ikke har lisens for
programvaren. Lisensvilkårene for programvaren gjelder for din bruk av dette tillegget. Microsoft tilbyr brukerstøtte
for tillegget, som beskrevet på www.support.microsoft.com/common/international.aspx.

MICROSOFT TEXT-TO-SPEECH - TELEPHONY FOR MICROSOFT SPEECH PLATFORM RUNTIME および

/または MICROSOFT SPEECH PLATFORM SDK 注意 : Microsoft Corporation (以下「マイクロソフト」とい
います) は、本追加ソフトウェアに関するライセンスをお客様に供与します。お客様は、Microsoft Speech
Platform Runtime および/または Microsoft Speech Platform SDK ソフトウェア (本追加ソフトウェアの対象と
なっているもの) の有効なライセンス取得済み複製 (以下「本ソフトウェア」といいます) 1 つごとに、こ
れを使用できます。本ソフトウェアのライセンスを取得していない場合は、本追加ソフトウェアを使用
することはできません。本ソフトウェアのライセンス条項は、本追加ソフトウェアの使用にも適用され
ます。マイクロソフトは、本追加ソフトウェアに対し
www.support.microsoft.com/common/international.aspx で説明されるサポートサービスを提供します。
MICROSOFT TEXT-TO-SPEECH - TELEPHONY FOR MICROSOFT SPEECH PLATFORM RUNTIME 및/또는

MICROSOFT SPEECH PLATFORM SDK 참고: Microsoft Corporation(또는 거주 지역에 따라 계열사 중 하나)은
귀하에게 본 추가 구성 요소의 사용권을 부여합니다. 적법하게 사용권이 허여된 Microsoft Speech Platform
Runtime 및/또는 Microsoft Speech Platform SDK 소프트웨어의 각 사본에 본 추가 구성 요소를(본 추가 구성
요소를 사용할 수 있는) (“소프트웨어”)와 함께 사용할 수 있습니다. 해당 소프트웨어 사용권이 없는 경우에는
추가 구성 요소도 사용할 수 없습니다. 본 추가 구성 요소 사용 시 해당 소프트웨어 사용권 조항 내용이
적용됩니다. Microsoft는 www.support.microsoft.com/common/international.aspx에 기술된 대로 추가 구성
요소에 대한 지원 서비스를 제공합니다.
MICROSOFT TEXT-TO-SPEECH - TELEPHONY PER MICROSOFT SPEECH PLATFORM RUNTIME E/O
MICROSOFT SPEECH PLATFORM SDK ATTENZIONE: Microsoft Corporation (o, in base al luogo di residenza
del licenziatario, una delle sue consociate) concede in licenza al licenziatario il presente supplemento. Il licenziatario
potrà utilizzarlo con ciascuna copia validamente concessa in licenza del software Microsoft Speech Platform Runtime
e/o Microsoft Speech Platform SDK (per il quale il presente supplemento è applicabile) (il “software”). Il licenziatario
non potrà utilizzare il supplemento qualora non disponga di una licenza per il software. Le condizioni di licenza per
il software si applicano all’utilizzo del presente supplemento da parte del licenziatario. Microsoft fornisce servizi di
supporto tecnico per il supplemento come descritto all’indirizzo
MICROSOFT TEXT-TO-SPEECH - TELEPHONY FÜR MICROSOFT SPEECH PLATFORM RUNTIME
UND/ODER MICROSOFT SPEECH PLATFORM SDK BITTE BEACHTEN SIE FOLGENDES: Microsoft
Corporation (oder eine andere Microsoft-Konzerngesellschaft, wenn diese an dem Ort, an dem Sie die Software
erwerben, die Software lizenziert) lizenziert diese Softwareergänzung an Sie. Sie sind berechtigt, die
Softwareergänzung mit jeder ordnungsgemäß lizenzierten Kopie von Software Microsoft Speech Platform Runtime
und/oder Microsoft Speech Platform SDK (für die diese Softwareergänzung anwendbar ist) (die „Software“) zu
verwenden. Sie sind nicht berechtigt, die Softwareergänzung zu verwenden, wenn Sie keine Lizenz für die Software
haben. Die Lizenzbestimmungen für die Software gelten für Ihre Verwendung dieser Softwareergänzung. Microsoft
stellt Supportleistungen für die Softwareergänzung bereit, die unter
www.support.microsoft.com/common/international.aspx beschrieben werden.
MICROSOFT TEXT-TO-SPEECH - TELEPHONY -OHJELMISTON MICROSOFT SPEECH PLATFORM
RUNTIME JA/TAI MICROSOFT SPEECH PLATFORM SDK HUOMAUTUS: Microsoft Corporation (tai
asiakkaan asuinpaikan mukaan määräytyvä Microsoft Corporationin konserniyhtiö) myöntää asiakkaalle tämän
täydennysosan käyttöoikeudet. Asiakas saa käyttää sitä kaikkien niiden Microsoft Speech Platform Runtime ja/tai
Microsoft Speech Platform SDK -ohjelmistosta tehtyjen kopioiden kanssa, joihin on voimassa olevat käyttöoikeudet
(jota tämä täydennysosa täydentää). Asiakas ei saa käyttää täydennysosaa, jos asiakkaalla ei ole ohjelmistoon
käyttöoikeutta. Täydennysosan käyttöön sovelletaan ohjelmiston käyttöoikeusehtoja. Microsoftin tähän
täydennysosaan tarjoamat tukipalvelut löytyvät osoitteessa www.support.microsoft.com/common/international.aspx.
MICROSOFT TEXT-TO-SPEECH - TELEPHONY POUR MICROSOFT SPEECH PLATFORM RUNTIME
ET/OU MICROSOFT SPEECH PLATFORM SDK REMARQUE : Microsoft Corporation (ou en fonction du lieu où
vous vivez, l’un de ses affiliés) vous accorde une licence pour ce supplément. Vous pouvez utiliser une copie de ce
supplément avec chaque copie concédée sous licence du logiciel Microsoft Speech Platform Runtime et/ou Microsoft
Speech Platform SDK (auquel s’applique ce supplément) (le « logiciel »). Vous n’êtes pas autorisé à utiliser ce
supplément si vous n’êtes pas titulaire d’une licence pour le logiciel. Les conditions de licence pour le logiciel
s’appliquent à l’utilisation de ce supplément. Microsoft fournit des services d’assistance technique pour le supplément
disponibles sur le site www.support.microsoft.com/common/international.aspx.

MICROSOFT TEXT-TO-SPEECH - TELEPHONY VOOR MICROSOFT SPEECH PLATFORM RUNTIME
EN/OF MICROSOFT SPEECH PLATFORM SDK LET OP: Microsoft Corporation (of, afhankelijk van waar u
woont, een van haar gelieerde ondernemingen) geeft dit supplement aan u in licentie. U mag dit gebruiken bij elk
geldig in licentie gegeven exemplaar van Microsoft Speech Platform Runtime en/of Microsoft Speech Platform SDK
software (waarop deze aanvulling van voorwaarden van toepassing is) (de "software"). U mag dit supplement niet
gebruiken als u geen licentie hebt voor de software. De licentievoorwaarden voor de software zijn van toepassing op
uw gebruik van dit supplement. Microsoft biedt productondersteuning voor dit supplement zoals wordt beschreven op
MICROSOFT TEXT-TO-SPEECH - TELEPHONY TIL MICROSOFT SPEECH PLATFORM RUNTIME
OG/ELLER MICROSOFT SPEECH PLATFORM SDK BEMÆRK: Microsoft Corporation (eller, afhængigt af hvor
De bor, et af dets associerede selskaber) licenserer dette tillæg til Dem. De må bruge den sammen med hver gyldigt
licenseret kopi af Microsoft Speech Platform Runtime v10.1 og/eller Microsoft Speech Platform SDK v10.1 softwaren
(som dette tillæg er gældende for) (“softwaren”). De må ikke bruge dette tillæg, hvis De ikke har licens til softwaren.
Licensvilkårene for softwaren gælder for brug af dette tillæg. Microsoft yder support til tillægget, som beskrevet på
MICROSOFT TEXT-TO-SPEECH - TELEPHONY（适用于 MICROSOFT SPEECH PLATFORM RUNTIME 和/
或 MICROSOFT SPEECH PLATFORM SDK 请注意：Microsoft Corporation（或 Microsoft Corporation 在您所
在地的关联公司）现授予您本补充程序的许可证。您可以随 Microsoft Speech Platform Runtime v10.1 和/或
Microsoft Speech Platform SDK v10.1 软件（即本补充程序适用的软件）（“软件”）的每份获得有效许可的副
本使用一份本补充程序。如果您没有软件的许可证，则不得使用本补充程序。该软件的许可条款在您使用
本补充程序时适用。Microsoft 为本补充程序提供支持服务；相关说明请参见
MICROSOFT TEXT-TO-SPEECH - TELEPHONY 之 MICROSOFT SPEECH PLATFORM RUNTIME 及/或
MICROSOFT SPEECH PLATFORM SDK 請注意：Microsoft 公司 (或其關係企業，視貴用戶所居住的地點
而定) 授權貴用戶使用本增補程式。貴用戶擁有之每份有效授權的 Microsoft 軟體(適用本增補程式之軟
體) （「軟體」），均得使用一份 Microsoft Speech Platform Runtime 及/或 Microsoft Speech Platform SDK 增
補程式。若貴用戶未取得軟體授權，即不得使用本增補程式。使用本增補程式時，亦須遵守軟體之授權
條款。Microsoft 為「增補程式」提供支援服務之相關說明，請參閱
MICROSOFT TEXT-TO-SPEECH - TELEPHONY PER A MICROSOFT SPEECH PLATFORM RUNTIME I/O
MICROSOFT SPEECH PLATFORM SDK CAL TENIR EN COMPTE QUE: Microsoft Corporation (o segons on
visqueu, una de les seves filials) us autoritza a utilitzar aquest complement Podeu utilitzar-lo amb totes les còpies
vàlidament llicenciades dels programaris Microsoft Speech Platform Runtime i/o Microsoft Speech Platform SDK
(per als quals aquest complement és vàlid) (el “programari”). No podeu utilitzar el complement si no disposeu d'una
llicència per al programari. Els termes de la llicència per al programari s'apliquen a l'ús que feu del complement.
Microsoft proporciona serveis de suport tècnic per a aquest complement, tal com es descriu a la pàgina
A5.2 Licence Text for FluentFTP
Copyright (c) 2015 J.P. Trosclair
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so, subject to the following conditions:
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
A5.3 Licence Text for the DotNetZip Library and Tools
Software Licenses that apply to the DotNetZip library and tools
As DotNetZip includes work derived from other projects, you are required to comply with the terms and conditions
for each of them. These licenses include BSD, Apache, and zlib.

To use the software, you must accept the licenses. If you do not accept the licenses, do not use the software.
Original intellectual property in DotNetZip is provided under the Ms-PL:
Copyright (c) 2006 - 2011 Dino Chiesa
Copyright (c) 2006, 2007, 2008, 2009 Dino Chiesa and Microsoft Corporation.
Microsoft Public License (Ms-PL)
This license governs use of the accompanying software, the DotNetZip library ("the software"). If you use
the software, you accept this license. If you do not accept the license, do not use the software.
1. Definitions
The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here
as under U.S. copyright law.
A "contribution" is the original software, or any additions or changes to the software.
A "contributor" is any person that distributes its contribution under this license.
"Licensed patents" are a contributor's patent claims that read directly on its contribution.
2. Grant of Rights
(A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in
section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce
its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative
works that you create.
(B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in
section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed
patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in
the software or derivative works of the contribution in the software.
3. Conditions and Limitations
(A) No Trademark License- This license does not grant you rights to use any contributors' name, logo, or
trademarks.
(B) If you bring a patent claim against any contributor over patents that you claim are infringed by the
software, your patent license from such contributor to the software ends automatically.
(C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and
attribution notices that are present in the software.
(D) If you distribute any portion of the software in source code form, you may do so only under this license
by including a complete copy of this license with your distribution. If you distribute any portion of the
software in compiled or object code form, you may only do so under a license that complies with this license.
(E) The software is licensed "as-is." You bear the risk of using it. The contributors give no express warranties,
guarantees or conditions. You may have additional consumer rights under your local laws which this license
cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties
of merchantability, fitness for a particular purpose and non-infringement.
--------------------------------------------------------------
The managed ZLIB code included in Ionic.Zlib.dll and Ionic.Zip.dll is derived from jzlib.
jzlib ( https://github.com/ymnk/jzlib ) is provided under a BSD-style (3 clause)
Copyright (c) 2000,2001,2002,2003 ymnk, JCraft, Inc.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that
the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
The names of the authors may not be used to endorse or promote products derived from this software without
specific prior written permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JCRAFT, INC.
OR ANY CONTRIBUTORS TO THIS SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
--------------------------------------------------------------
The jzlib library, itself, is a re-implementation of ZLIB v1.1.3 in pure Java.
zlib is provided under the zlib license:
Copyright (C) 1995-2004 Jean-loup Gailly and Mark Adler
The ZLIB software is provided 'as-is', without any express or implied warranty. In no event will the authors
be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and
to alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original
software. If you use this software in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the
original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly jloup@gzip.org
Mark Adler madler@alumni.caltech.edu
--------------------------------------------------------------
The managed BZIP2 code included in Ionic.BZip2.dll and Ionic.Zip.dll is modified code, based on Java code in the
Apache commons compress library.
Apache Commons Compress ( http://commons.apache.org/proper/commons-compress/ ) is provided under the
Apache 2 license:
Apache Commons Compress
Copyright 2002-2014 The Apache Software Foundation
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See
the NOTICE file distributed with this work for additional information regarding copyright ownership. The
ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this
file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied. See the License for the specific language governing permissions and limitations under the License.
Many thanks to Julian Seward for the original C implementation of BZip2 ( http://www.bzip.org/ ).
A5.4 Licence for SSH.NET
shnet/SSH.NET is licensed under the MIT Licence.
MIT License
A short and simple permissive license with conditions only requiring preservation of copyright and license notices.
Licensed works, modifications, and larger works may be distributed under different terms and without source code.
The MIT License (MIT)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE


Index
INDEX
A Autodial Modules ...................................................................... 188

ABS Function Modules.............................................................. 492 Autodialler Information ............................................................. 331
Add Average Function Modules ....................................................... 497
Address Modules .................................................................. 162 Average IC Comms Modules .................................................... 520
Alarm Group Modules .......................................................... 208 B
Alarm Handling Groups ........................................................ 208 Backdrop Files
BACnet Application Network Modules ................................ 173 Import ................................................................................... 348
BACnet MSTP Network Modules ........................................ 175 Background Compare .................................................................. 42
BACnet Network Modules .................................................... 171 Backup
BACnet Sites ........................................................................ 383 Backup the Project......................................................... 290, 292
Connective to System Information ........................................ 310 Options ................................................................................... 67
Connectives .................................................................. 308, 309 Project .................................................................................. 286
Controllers .............................................................. 98, 141, 148 Restore ................................................................................... 67
Directory Modules ................................................ 117, 256, 260 Backwards Engineering .............................................. 126, 127, 149
Display Modules ........................................... 118, 119, 257, 261 BACnet ....................................................................................... 31
Dummy IC Comms Modules ................................................ 202 BACnet Alarm Destination Modules ......................................... 433
Ethernet IP Network Modules ............................................... 167 BACnet Application Network Modules...................... 173, 577, 708
Free Node ............................................................................. 315 BACnet Communications.......................................................... 371
Gap in Sequence Table ......................................................... 218 BACnet IP Network Modules.................................................... 579
Graphics ................................................................................ 276 BACnet MSTP Network Modules .............................. 175, 580, 708
IC Comms Modules .............................................................. 240 BACnet Network
IP Network Modules ............................................................. 167 Connect to .......................................................................34, 378
IQeco Display Devices.......................................................... 314 BACnet Network Driver
Language ................................................................................ 69 Install...................................................................................... 31
LANs ...................................................................................... 97 BACnet Network Modules ................................................. 171, 582
Modules ................. 103, 125, 132, 196, 240, 250, 258, 311, 325 BACnet Sites ............................................................................. 383
Modules to the Sequence Table .................................... 217, 219 Base Project Directory................................................................. 85
NTDs ............................................................................ 237, 238 BBMD ....................................................................................... 171
Plant Directories ................................................................... 327 BDT List ................................................................................... 171
Return Steps .......................................................................... 219 Binary Hysteresis Driver Modules ............................................ 451
Sensor Definitions................................................................. 130 Browse the System .................................................................... 379
Sensor Type Modules ................................................... 177, 178 BTL Compliant Strategy ........................................................... 134
Sites ...................................................................................... 383 BUA Editor ............................................................................... 362
Static Display Modules ......................................................... 258 C
Strategy Block Groups ............................................................ 49 Calendar Module/Set up ............................................................ 226
Strategy Issues ...................................................................... 283 Change
Strategy Pages ............................................................... 108, 313 Controller Address ............................................................... 148
Text ............................................................................... 116, 277 Controller Type ............................................................. 321, 323
TO Connectives .................................................................... 313 Driver Output Channel ......................................................... 216
Trend System Sites ............................................................... 383 Firmware Version .......................................................... 321, 323
Undefined Connectives ................................................. 314, 315 I/O Module ........................................................................... 209
Unplaced Modules ................................................................ 317 IQeco Display Device........................................................... 337
User Modules ........................................................................ 250 Labels ................................................................................... 345
User Parameters to a User Node ........................................... 402 Module Configuration Parameters ................................. 105, 213
Add Function Modules .............................................................. 492 Module Destination .............................................................. 215
Adder/Scaler Function Modules ........................................ 493, 662 Module Sequence Step .......................................... 123, 124, 217
Address Modules ............................................................... 429, 642 Next Module Number ........................................................... 358
Set up ............................................................................ 100, 162 Node's Value ........................................................................ 213
Adjust Order of Display Modules .................................................... 262
Live ....................................................................................... 303 Password ................................................................................ 30
ADL support ...................................................................... 188, 189 Sensor Definition.................................................................... 48
Alarm Group Modules ....................................................... 438, 647 Undefined Connective Label ................................................ 213
Alarm Handling Groups............................................................. 208 Change Multiple Parameters ..................................................... 214
Alarm Handling Strategy Change of State Logic Modules ................................................ 563
Set up .................................................................... 203, 206, 207 Change Strategy
Alarm Route Modules ........................................................ 439, 648 Fixed Strategy Controllers .................................................... 161
Alarm Status Information .......................................................... 309 Close
Alarms Project .................................................................................. 322
Disable .................................................................................. 207 Strategy Page ........................................................................ 322
Enable ................................................................................... 207 CNC User Modules ................................................................... 253
Align Modules ........................................................................... 200 Collapse
Analogue Driver Modules.................................................. 447, 651 Project View ......................................................................... 332
Analogue Node Modules ................................................... 532, 686 Strategy Library.................................................................... 333
Analogue to Digital Function Modules .............................. 495, 663 System View ........................................................................ 333
Annunciate Values ..................................................................... 298 Collect Controller Diagnostic Information ................................ 322
Applet Combination Logic Modules .............................................. 564, 700
Run ....................................................................................... 387 Command Line Toolbar
Auto Edit Add Modules ......................................................... 132, 311, 349
Disable .................................................................................... 64 Commands............................................................................ 718
Enable ..................................................................................... 64 Find Modules......................................................... 131, 342, 349
Auto Routing Find Nodes ........................................................................... 346
Disable .................................................................................... 91 Go to a Page ......................................................................... 347
Enable ..................................................................................... 91 Using .................................................................................... 131

Index
Commission With Live Values .................................................. 298 Modules ................................................................................ 325
Common IQ4 Module Parameters.............................................. 428 Strategy Blocks ...................................................................... 51
Comms Connection Strategy Page ........................................................................ 325
Delete ...................................................................................... 71 Counter Logic Modules ...................................................... 565, 701
Edit ......................................................................................... 71 COV Function Modules ............................................................ 498
Communications COV Plot Modules .................................................................... 602
Display.................................................................................. 332 Create
Communications Window ......................................................... 332 BACnet Sites ........................................................................ 383
Company Information Directory Modules ................................................................ 117
Address ................................................................................... 65 Display Modules............................................................ 118, 119
Logo........................................................................................ 65 Duplicate Controllers............................................................ 148
Specify .................................................................................... 65 IQ2 Files ............................................................................... 327
Comparator Function Modules .......................................... 498, 666 IQ3 Files ........................................................................ 110, 327
Compare Strategies IQ4 Files ............................................................................... 327
IQ2 Files ....................................................................... 290, 295 IQe Files ............................................................................... 327
IQ3 Files ............................................................................... 132 LDF Files ............................................................................. 327
Multiple Strategies ................................................................ 292 Multiple Data Files ............................................................... 327
Single Strategies ................................................................... 290 Plant Directories ................................................................... 327
Strategies .............................................................. 132, 290, 295 Projects ............................................................................95, 137
Undo ..................................................................................... 295 Re-usable Strategy ................................................................ 128
Comport Modules ...................................................................... 190 Sensor Type Modules ........................................................... 177
Configuration Mode Site Files ........................................................................ 379, 380
Enter ............................................................................. 337, 397 Sites ...................................................................................... 383
Send Commands ........................................................... 337, 397 Spreadsheet .......................................................................... 153
Window ........................................................................ 337, 397 Strategy ................................................................. 157, 158, 159
Configuration Parameters .......................................... 105, 213, 358 Strategy Block Groups ........................................................... 49
Configure Strategy Blocks .................................................................... 128
Alarm Handling Strategy .............................................. 203, 206 Strategy Pages ............................................................... 108, 313
Fixed Strategy Controllers .................................................... 161 Trend System Sites ............................................................... 383
IQ Controllers ....................................................................... 159 CSV Files .................................................................................. 341
IQ Lan Network Modules ..................................................... 167 Current Loop ............................................................................. 377
IQ3 Controllers ..................................................................... 158 Custom Library ........................................................................... 51
IQ3/XNC ...................................................................... 193, 194 Custom Strategy Ordering ......................................................... 306
IQ4 Controllers ..................................................................... 157 D
IQeco Controllers .................................................................. 159 D to A Logic Modules ............................................................... 568
Strategy ................................................................................. 161 Data Files .................................................................................. 326
XNC Interface Module.......................................................... 193 Comparing ............................................................................ 290
Connect Create ............................................................................ 110, 327
Over BACnet Network............................................................ 34 Download ............................................................................. 279
Over Current Loop ................................................................ 377 Import ............................................................................ 127, 149
Over Ethernet ........................................................................ 376 Data From Analogue IC Comms Modules ......................... 521, 677
To a Controller ...................................................................... 377 Data From Bit IC Comms Modules .................................... 522, 678
To a Land Line...................................................................... 377 Data From Byte IC Comms Modules ................................. 524, 680
To a live site.......................................................................... 379 Data To IC Comms Modules ..................................................... 525
To a Local Supervisor Port ................................................... 377 Default
To a Node Controller ............................................................ 377 Comms Connection ................................................................ 72
To the BACnet Network ....................................................... 378 Display Language ................................................................... 74
To the Trend Network ............................................................. 34 Display Options ...............................................................75, 358
Using a MODEM .................................................................. 377 IQ3 or IQ4 Directory Module Parameter Values .................... 79
Using SANC ......................................................................... 377 IQ3 or IQ4 Display Module Parameter Values ....................... 80
Using USB ............................................................................ 377 Labels ..................................................................................... 43
Connection Wizard .................................................................... 359 Print Options .......................................................................... 76
Connectives Printer ..................................................................................... 82
Add ............................................................... 308, 309, 310, 314 Default Controller ....................................................................... 73
Defining ................................................................................ 328 Default Language ........................................................................ 69
Delete .................................................................................... 329 Define
To Connectives ............................................................. 116, 313 Sensor Type Module............................................................. 177
Undefined ..................................................................... 315, 328 Strategy's Issue .............................................................. 109, 283
Contacting Trend ......................................................................... 15 Undefined Connective .......................................................... 328
Controller and Identifier Check ................................................... 39 Delay Logic Modules ................................................................ 566
Controller Time/Date Check .................................................. 40, 78 Delete
Controllers Connections ............................................................................ 71
Add ................................................................................. 98, 141 Connectives .......................................................................... 329
Backwards Engineer ..................................................... 126, 149 Controllers ............................................................................ 154
Change type .................................................................. 321, 323 Directory Modules ................................................................ 271
Configuration Mode ...................................................... 337, 397 Display Modules................................................................... 270
Configure .............................................................. 157, 158, 159 Exceptions ............................................................................ 232
Copy ..................................................................................... 148 Graphics ............................................................................... 277
Delete .................................................................................... 154 I/O Modules ......................................................................... 209
Download To ........................................................................ 279 IQeco Display Devices ......................................................... 330
Edit ....................................................................................... 154 Languages .............................................................................. 69
Enter Configuration Mode ............................................ 337, 397 LANs .................................................................................... 156
Firmware Version ................................................................. 321 Links .................................................................................... 330
Upload From ......................................................................... 368 Modules ................................................................................ 330
Conventions Used in this Manual ................................................ 14 Modules from the Sequence Table ....................................... 218
Convert Strategy ................................................................ 321, 323 NTDs .................................................................................... 238
Copy Objects from the System View ............................................. 401
Controllers ............................................................................ 148

Index
Plant Directories ................................................................... 330 IQ3 ....................................................................................... 110
Projects ................................................................................. 139 Draw.......................................................................................... 276
Sensor Definitions................................................................... 47 Driver Modules
Sites ...................................................................................... 399 Change Output Channel........................................................ 216
Solution Groups ...................................................................... 59 Dynamic Display Modules ................................................. 257, 443
Solutions ................................................................................. 60 E
Standard Comms Connection .................................................. 71 EDE File.................................................................................... 339
Strategy Blocks ....................................................................... 51 Edit
Strategy Pages ....................................................................... 330 Address Modules .................................................................. 162
Text ....................................................................................... 277 BACnet Application Network Modules ................................ 173
TUA ........................................................................................ 71 BACnet MSTP Network Modules ........................................ 175
User Modules ........................................................................ 250 BACnet Network Modules ................................................... 171
User Nodes ........................................................................... 402 Configuration Parameters ..................................................... 213
User Parameters from a User Node ....................................... 402 Connections ............................................................................ 71
Users ....................................................................................... 30 Controller Type .................................................................... 321
Device Controllers ............................................................................ 154
Change Type ......................................................................... 321 Directory Modules ................................................................ 262
Edit ....................................................................................... 154 Display Modules................................................................... 267
View Details ......................................................................... 371 Driver Output Channels ........................................................ 216
Digital Byte Modules ......................................................... 533, 687 Ethernet IP Network Modules .............................................. 167
Digital Driver Modules ...................................................... 456, 652 Exceptions ............................................................................ 234
Directory Module Parameter Defaults ......................................... 79 I/O Modules ......................................................................... 209
Directory Modules ............................................................. 442, 649 IQeco Display Device........................................................... 337
Add ....................................................................... 117, 256, 260 Labels ................................................................................... 345
Delete .................................................................................... 271 Lan Details ........................................................................... 156
Edit ....................................................................................... 262 Live ............................................................................... 300, 303
Export Structure .................................................................... 272 Modules ......................................... 105, 212, 213, 215, 216, 262
Import Structure .................................................................... 273 Multiple Parameters.............................................................. 214
Set up .................................................................................... 268 Next Module Number ........................................................... 358
Disable Node's Value ........................................................................ 213
Alarms .................................................................................. 207 NTDs .................................................................................... 239
Auto Edit................................................................................. 64 Page Details .......................................................................... 356
Auto Routing .......................................................................... 91 Project Details ...................................................................... 139
Controller Time/Date Check ................................................... 40 Sensor Definitions .................................................................. 48
Module Tooltips...................................................................... 92 Sequence Table ............................................. 123, 124, 217, 219
Modules ................................................................................ 331 Sites ...................................................................................... 399
Tip of the Day ......................................................................... 92 Standard Comms Connections ................................................ 71
Display Strategy Block Properties ....................................................... 51
Autodialling Information ...................................................... 331 Strategy Block Strategy .......................................................... 53
Communications Information ............................................... 332 TUAs ...................................................................................... 71
Configuration Parameters ..................................................... 358 User Modules ....................................................................... 251
Item Selector ......................................................................... 332 User Nodes ........................................................................... 403
Next Module List .................................................................. 374 Users ...................................................................................... 30
NTD List ............................................................................... 293 Value of a Node.................................................................... 322
Page Details .......................................................................... 372 Enable
Strategy Page ........................................................................ 347 Alarms .................................................................................. 207
System View ................................................................. 333, 379 Auto Edit ................................................................................ 64
Tip of the Day ....................................................................... 333 Auto Routing .......................................................................... 91
Toolbars .................................................................................. 87 Module Tool Tips ................................................................... 92
Tracker Window ..................................................................... 86 Modules ................................................................................ 331
Display and Directory Module Structure Tip of the Day ........................................................................ 92
Export ................................................................................... 272 Enter Configuration Mode.................................................. 337, 397
Import ................................................................................... 273 Enthalpy Function Modules....................................................... 501
Display Devices Ethernet
Add ....................................................................................... 314 Connect over ........................................................................ 376
Delete .................................................................................... 330 Ethernet IP Module ................................................................... 101
Edit ....................................................................................... 337 Ethernet IP Network Modules ............................................ 167, 583
Display Language ................................................................ 74, 162 Event Driven Strategy ........................................................ 124, 219
Display Modules ........................................................ 443, 445, 650 Excel files ................................................................... 339, 340, 341
Add ........................................................ 118, 119, 257, 258, 261 Exceptions
Change Order ........................................................................ 262 Delete ................................................................................... 232
Delete .................................................................................... 270 Edit ....................................................................................... 234
Edit ....................................................................................... 267 Expand
Set up ............................................................................ 264, 269 Project View ......................................................................... 332
Display Options ........................................................................... 75 Strategy Library.................................................................... 333
Divide Function Modules .................................................. 500, 667 System View ........................................................................ 333
Dock Export
Project View ................................................................. 332, 334 Data to 963 ........................................................................... 338
Search Library ...................................................................... 334 Display and Directory Module Structure .............................. 272
Strategy Library ............................................................ 333, 334 EDE File ............................................................................... 339
System View ................................................................. 333, 334 Module Lists......................................................................... 341
Download .................................................................................. 415 Project .................................................................................. 286
Single Page of Strategy ......................................................... 334 Project Overview .................................................................. 340
Strategy ................................................................................. 279 Solutions................................................................................. 62
To a Single Controller ........................................................... 279 Strategy Blocks ...................................................................... 62
To Multiple Controllers ........................................................ 279 Strategy for Custom Ordering .............................................. 306
Downloadable Files Translated Labels ................................................................... 58
Create Multiple ..................................................................... 327

Index
Translated Print Labels ........................................................... 90 Insert
External Digital Input Modules .......................................... 534, 688 Gap in the Sequence Table ................................................... 218
External Digital Sensor Modules ............................................... 535 Install
External Sensor Modules ................................................... 536, 689 BACnet Network Driver ......................................................... 31
F LCI/USB Driver ..................................................................... 33
Fan Out Logic Modules ............................................................. 569 Upgrade IQ SET ..................................................................... 26
Fast Sequencing ......................................................................... 219 USB Driver............................................................................. 32
Filter Function Modules ..................................................... 502, 667 Integrator Function Modules .............................................. 506, 670
Find Interface Network Module ........................................................ 181
Fixed System Nodes ............................................................. 342 Internal Digital Input Modules ........................................... 540, 694
Modules ................................................................ 131, 342, 349 Internal Digital Sensor Modules ................................................ 542
Object in the System View .................................................... 386 Internal Sensor Modules ..................................................... 543, 692
Sequence Step ....................................................................... 346 IQ Controllers
Where a Node is Used........................................................... 346 Configure............................................................... 157, 158, 159
Find and Replace IQ Lan Network Module
Labels ................................................................................... 345 Configure.............................................................................. 167
Firmware Version IQ2 Controllers
Change .................................................................................. 321 Backwards Engineer ............................................................. 149
Fixed Nodes Configure.............................................................................. 159
Change Value........................................................................ 322 Download To ........................................................................ 279
Fixed Sensor Type Modules ...................................................... 713 Engineer ............................................................................... 159
Fixed Strategy Controllers Enter Configuration Mode ............................................. 337, 397
Change Strategy .................................................................... 161 IQ3 Controllers
Configure .............................................................................. 161 Backwards Engineer ...................................................... 126, 149
Fixed System Nodes .................................................................. 342 Configure.............................................................................. 158
Free Download To ........................................................................ 279
Modules ................................................................................ 374 IQ4 Controllers
Nodes .................................................................................... 315 Backwards Engineer ...................................................... 126, 149
Function Modules ...................................................................... 494 Configure....................................................................... 157, 158
Download To ........................................................................ 279
G IQeco Controllers
Gap in the Sequence Table......................................................... 218 Backwards Engineer ............................................................. 149
Gate Function Modules ...................................................... 503, 668 Configure.............................................................................. 159
Global To IC Comms Modules .................................................. 526 IQeco D to A Logic Modules .................................................... 702
Go to a Module .......................................................................... 346 IQeco Display Device
Go to a Strategy Page................................................................. 347 Add ....................................................................................... 314
Graphical Display Pages .................................................... 120, 121 Delete ................................................................................... 330
Set up ............................................................................ 122, 275 Edit ....................................................................................... 337
Graphics IQeco Synchronised Plot Modules ............................................ 712
Add ....................................................................................... 276 IQeco v1.0 Data To IC Comms Modules .................................. 681
Delete .................................................................................... 277 IQeco v1.0 Global To IC Comms Modules ............................... 682
Move ............................................................................. 122, 277 IQeco v2.0 Data To IC Comms Modules ........................... 683, 684
Group Parameter Edit ................................................................ 214 IQSET
Guest User Default Language ................................................................... 69
Set up .................................................................................... 248 Run ..................................................................................95, 353
H Issue Details .............................................................................. 283
Heat Meter Function Modules ........................................... 503, 668 Item Selector ............................................................................. 332
Hide K
Project View ......................................................................... 332 Keyboard Short Cuts .......................................................... 332, 724
Status Bar.............................................................................. 358 Knob Modules .................................................................... 547, 695
Strategy Library .................................................................... 333
System View ......................................................................... 333 L
Historic Alarms .......................................................................... 423 Labels
Hours Run Logic Modules ................................................. 570, 703 Copy ..................................................................................... 345
Hysteresis Band Function Modules.................................... 505, 670 Default .................................................................................... 43
Hysteresis Limits Function Modules.......................................... 505 Export ................................................................................58, 90
Find & Replace..................................................................... 345
I Import Translated ................................................................... 57
I/O Channels .............................................................................. 212 Paste ..................................................................................... 345
Unassign ............................................................................... 212 Translated ............................................................................... 89
I/O Modules ....................................................................... 561, 699 LAN
Edit ....................................................................................... 209 Delete ................................................................................... 156
Remove ................................................................................. 209 Details ........................................................................... 156, 372
Set up .................................................................................... 212 Edit Details ........................................................................... 156
IC Comms Lan Network Modules ............................................................... 588
Set up .................................................................................... 236 Language
IC Comms Modules ................................................................... 236 Add ......................................................................................... 69
Add ....................................................................................... 240 Default .............................................................................69, 162
Identifier Check ........................................................................... 39 Default Display ...................................................................... 74
Import Delete ..................................................................................... 69
Backdrop Files ...................................................................... 348 Downloaded ......................................................................... 162
Display and Directory Module Structure............................... 273 LCI/USB Driver .......................................................................... 33
IQ3 Files ....................................................................... 127, 149 Licence
Projects ................................................................................. 138 IQSET .................................................................................. 353
Strategy Files ........................................................................ 127 Limit at Function Modules ........................................................ 507
Translated Labels .................................................................... 57 Limit to Function Modules ........................................................ 508
Translated Print Labels ........................................................... 89 Link
Inputs ......................................................................................... 194 Delete ................................................................................... 330

Index
Indicating .............................................................................. 313 N
Manually Route..................................................................... 202 Navigate the System .................................................................. 386
Modules not in the Strategy .......................................... 201, 314 Network Configuration
Modules on Different Pages .................................. 114, 116, 200 Set up ................................................................................... 166
Modules on the Same Page ................................................... 107 Network Modules
Strategy .......................................... 107, 114, 115, 201, 202, 330 Set up ............................................................................ 101, 171
TCL Inputs and Outputs to Modules Manually ............. 193, 194 New Project ................................................................................. 95
To a Dummy IC Comms Module .......................................... 202 Next Module List
To a Node ............................................................................. 201 View ..................................................................................... 374
To a specific value ................................................................ 201 Next Module Number ................................................................ 358
To a Value ............................................................................ 115 Node
To Alarm Status Information in an IQ3 Controller ............... 201 Edit Value............................................................................. 213
To System Information ......................................................... 202 Find where used ................................................................... 346
XNC Application File ........................................................... 193 Link To ................................................................................. 201
Live Adjustment ........................................................................ 303 NTD List ................................................................................... 293
Live Editing ............................................................................... 300 NTD Modules..................................................................... 595, 710
Live Values ................................................................................ 298 Add ................................................................................ 237, 238
Speech Annunciation ............................................................ 298 Delete ................................................................................... 238
Load Display List .......................................................................... 293
Existing Project ..................................................................... 112 Edit ....................................................................................... 239
Site Data ................................................................................. 81 Resolve Differences.............................................................. 293
Log Function Modules ............................................................... 509 Send to Controllers ............................................................... 239
Lookup Function Modules ......................................................... 509
Loop Modules .................................................................... 574, 705 O
Open
M Project ........................................................................... 112, 138
Manual Site File ......................................................................... 379, 382
Refresh .................................................................................. 387 Order of Display Modules ......................................................... 262
Routing of Links ................................................................... 202 OSS Modules ............................................................................ 597
Maximum Function Modules ..................................................... 510 Output Channel ......................................................................... 216
Maximum IC Comms Modules .................................................. 527 Outputs
Minimum Function Modules ..................................................... 511 Specify ................................................................................. 194
Minimum IC Comms Modules .................................................. 529 Override Module Output ........................................................... 300
Modem Module ......................................................................... 188
Module P
States Category ..................................................................... 180 Page
Module Lists Add ................................................................................ 108, 313
Export ................................................................................... 341 Add Graphics........................................................................ 276
Module Prompts........................................................................... 86 Add Text .............................................................................. 277
Module Tracking ......................................................................... 68 Add Unplaced Modules ........................................................ 317
Modules Close .................................................................................... 322
Add ............................................................... 240, 250, 260, 311 Copy to Clipboard ................................................................ 325
Add to Sequence Table ......................................................... 217 Delete ................................................................................... 330
Add to Strategy ...................... 103, 117, 118, 119, 132, 325, 349 Delete Graphics .................................................................... 277
Add Unplaced ....................................................................... 317 Delete Text ........................................................................... 277
Align ..................................................................................... 200 Display ................................................................................. 347
Change Destination ............................................................... 215 Go to..................................................................................... 347
Change Sequence Step .......................................... 123, 124, 218 Move Modules...................................................................... 200
Copy ..................................................................................... 325 Move Text and Lines ............................................................ 277
Delete ............................................................ 250, 270, 271, 330 Page Details
Disable .................................................................................. 331 Edit ....................................................................................... 356
Edit ........................................ 105, 209, 212, 213, 215, 216, 251 Set up ................................................................................... 356
Enable ................................................................................... 331 View ..................................................................................... 372
Find ............................................................... 131, 342, 346, 349 Page Modules ............................................................................ 601
Free ....................................................................................... 374 Password
Go to ..................................................................................... 346 Change ................................................................................... 30
Link ....................................................... 107, 114, 115, 200, 201 Paste
Modules ................................................................................ 125 Modules ................................................................................ 325
Move ............................................................................. 105, 200 Periodic Plot Modules ............................................................... 605
Next ...................................................................................... 374 PIN
Paste...................................................................................... 325 Protection ...................................................................... 250, 251
Remove ................................................................................. 209 Set up ................................................................................... 355
Remove from Sequence Table .............................................. 218 Plan Your System ...................................................................... 136
Select .................................................................................... 355 Plant Directory
States Category ..................................................................... 612 Create ................................................................................... 327
Move Delete ................................................................................... 330
Graphics ................................................................................ 277 Rename................................................................................. 351
Modules ........................................................................ 105, 200 Plant View ................................................................................. 327
Modules in the Sequence Table ............................................ 218 Plot Modules .............................................................. 603, 605, 606
Project View ......................................................................... 349 Position
Search Library ...................................................................... 349 Applets ................................................................................. 350
Strategy Library .................................................................... 349 Modules in the Sequence Table ............................................ 217
System View ......................................................................... 349 Windows ....................................................................... 350, 358
Text ....................................................................................... 277 Power Function Modules ........................................................... 512
Toolbars .......................................................................... 87, 349 Prevent a User Node Refreshing................................................ 408
Multi Stage Digital Driver Modules................................... 461, 653 Print
Multiply Function Modules ............................................... 511, 672 Options ................................................................................... 76
Pages and Tables ........................................................... 110, 285
Project Documentation .................................................. 110, 285

Index
Project Overview .................................................................. 284 Return Steps .............................................................................. 219
Report File ............................................................................ 290 Re-useable Strategy .................................................... 125, 127, 196
Single Page of Strategy ......................................................... 350 Reverse Engineer................................................................ 126, 127
Strategy Blocks ..................................................................... 350 Run
Strategy Pages ....................................................................... 285 Applets ................................................................................. 387
Printer IQSET .............................................................................95, 353
Set up ...................................................................................... 82 S
Settings ................................................................................... 82 SANC ........................................................................................ 377
Specify .................................................................................... 82 Save
Priority Array Labels ................................................................... 82 Site Data ................................................................................. 81
Project Schedule Offset Modules .......................................................... 608
Close ..................................................................................... 322 Search Library
Create.............................................................................. 95, 137 Dock ..................................................................................... 334
Delete .................................................................................... 139 Move .................................................................................... 349
Documentation ...................................................................... 284 Resize ................................................................................... 351
Export ................................................................................... 286 Securing IQSET .......................................................................... 36
Import ................................................................................... 138 Select
Open ............................................................................. 112, 138 Modules ................................................................................ 355
Print Documentation ............................................................. 285 Send NTD Changes to Controllers ............................................ 239
View Details ......................................................................... 373 Sensor Definition
Project Details Add ....................................................................................... 130
Edit ....................................................................................... 139 Delete ..................................................................................... 47
Print ...................................................................................... 110 Edit ......................................................................................... 48
View ..................................................................................... 373 Use ....................................................................................... 177
Project Documentation Sensor Library
Documentation ...................................................................... 110 Delete Sensor Definition ........................................................ 47
Print ...................................................................................... 285 Edit Sensor Definitions........................................................... 48
Project Overview Edit Sensors ............................................................................ 48
Export to XLS File ................................................................ 340 Sensor Type Modules ......................................................... 610, 714
Print ...................................................................................... 284 Define ..................................................................................... 47
Project Update ........................................................................... 296 Edit ......................................................................................... 48
Project View Set up .................................................................... 102, 177, 178
Collapse ................................................................................ 332 Sensors
Display.................................................................................. 332 Delete Definitions................................................................... 47
Dock ............................................................................. 332, 334 Edit Definition ........................................................................ 48
Expand .................................................................................. 332 Edit Library ............................................................................ 48
Hide ...................................................................................... 332 Sequence Step
Move ..................................................................................... 349 Change .......................................................... 123, 217, 218, 219
Resize ........................................................................... 332, 351 Find where used ................................................................... 346
Undock ................................................................................. 332 Return ................................................................................... 219
Proximity Function Modules ............................................. 513, 673 Sequence Table
Psychrometrics Function Modules ............................................. 513 Add Modules ........................................................................ 217
Q Add Return Step ................................................................... 219
Quick Edit.................................................................................. 213 Edit ................................................................ 123, 124, 217, 218
R Fast Sequencing.................................................................... 219
Raise/Lower Continuous Driver Modules .................................. 470 Insert Gap ............................................................................. 218
Raise/Lower End Driver Modules...................................... 475, 658 Move Modules...................................................................... 218
Readback Logic Modules .......................................................... 572 Remove Modules .................................................................. 218
Record Modules ......................................................................... 189 Return Step ........................................................................... 219
Redraw the Screen ..................................................................... 351 Set Up............................................................ 123, 217, 218, 219
Refresh Specify Gap ............................................................................ 77
Activate................................................................................. 408 Set Up
Automatically ....................................................................... 408 Alarm Handling Strategy ............................................... 203, 206
Manually ............................................................................... 387 BACnet MSTP Network Modules ........................................ 175
Options ................................................................................... 83 BACnet Sites ........................................................................ 383
System View ......................................................................... 387 Controller Security ................................................ 248, 249, 250
Turn ON/OFF ....................................................................... 408 Default Controller................................................................... 73
Remote Trend Devices Event Driven Strategy .......................................................... 219
Set up .................................................................................... 140 Graphical Display Pages ................................ 120, 121, 122, 275
Remove Guest User ............................................................................ 248
Controller .............................................................................. 154 I/O Modules ......................................................................... 212
NTDs .................................................................................... 238 IC Comms over the Trend network ...................................... 236
User Parameters from a User Node ....................................... 402 Network Configuration ......................................................... 166
Rename Page Details .......................................................................... 356
Plant Directories ................................................................... 351 PIN ....................................................................................... 355
Replace Labels ........................................................................... 345 Sites ...................................................................................... 383
Rescale From Function Modules ....................................... 514, 674 Strategy Block Page Details ................................................... 53
Rescale To Function Modules............................................ 515, 675 Trend System Sites ............................................................... 383
Resize User Modules ........................................................ 248, 249, 250
Project View ................................................................. 332, 351 Set Up Modules
Search Library ...................................................................... 351 Address Modules ........................................................... 100, 162
Strategy Library ............................................................ 333, 351 Alarm Group Modules .......................................................... 208
System View ................................................................. 333, 351 Autodial Module................................................................... 188
Resolve NTD Differences .......................................................... 293 BACnet Application Network Module ................................. 173
Restore ....................................................................................... 295 BACnet Network Module ..................................................... 171
Backups .................................................................................. 67 Comport Modules ................................................................. 190
Strategy ................................................................................. 295 Default Remote Devices ....................................................... 140

Index
Directory Modules ................................................................ 268 Square Root Function Modules .......................................... 516, 676
Display Modules ........................................................... 264, 269 Standard Comms Connection
Driver Modules ..................................................................... 216 Delete ..................................................................................... 71
Edit ....................................................................................... 251 Edit ......................................................................................... 71
Ethernet IP Modules ............................................................. 101 States Category Modules .................................................... 180, 612
Fast Sequencing .................................................................... 219 Static Display Modules ............................................................. 445
I/O Modules .......................................................................... 212 Status Bar .................................................................................. 358
IP Network Modules ............................................................. 167 Store Modules
Modem Modules ................................................................... 188 Set Up................................................................................... 191
Record Modules .................................................................... 189 Stores ........................................................................................ 194
Sensor Type Modules ........................................... 102, 177, 178 Strategy
Sequence Table ............................................................. 124, 219 BTL Compliant .................................................................... 134
Store Modules ....................................................................... 191 Commissioning..................................................................... 298
User Modules ........................................................................ 251 Compare ................................................................ 132, 290, 292
Set up vCNC Modules ............................................................... 253 Configure....................................................... 157, 158, 159, 161
Set up/Calendar Module ............................................................ 226 Convert ................................................................................. 323
SET Window ......................................................................... 19, 96 Define Issue ................................................................... 109, 283
Short Cuts .......................................................................... 332, 724 Delete Link ........................................................................... 330
Simulation.................................................................................. 277 Download ............................................................................. 279
Site Codes .................................................................................. 356 Event Driven ........................................................................ 124
Site Data ...................................................................................... 81 Export for Custom Ordering ................................................. 306
Specify Loading ...................................................................... 81 Import ................................................................................... 127
Specify Saving ........................................................................ 81 Link ....................................................................... 107, 200, 201
Site File Print ...................................................................................... 285
Create.................................................................................... 380 Restore ................................................................................. 295
Open ..................................................................................... 382 Update .................................................................................. 290
Sites Upload ........................................................................... 127, 368
Add ....................................................................................... 383 View Issue ............................................................................ 374
Create.................................................................................... 383 Strategy Block Groups
Delete .................................................................................... 399 Create ..................................................................................... 49
Edit ....................................................................................... 399 Strategy Block Module Start Numbers ........................................ 55
New ...................................................................................... 383 Strategy Block Page Details .................................................53, 373
Solution Groups Strategy Blocks
Delete ...................................................................................... 59 Copy to Custom Library ......................................................... 51
Solutions Create ................................................................................... 128
Delete ...................................................................................... 60 Delete ..................................................................................... 51
Export ..................................................................................... 62 Edit ......................................................................................... 53
Specify Edit Properties ........................................................................ 51
Auto Edit................................................................................. 64 Export ..................................................................................... 62
Background Compare ............................................................. 42 Location ................................................................................. 84
Backup Options....................................................................... 67 Principles .............................................................................. 127
COM Port ............................................................................... 72 Print ...................................................................................... 350
Company Information ............................................................. 65 Use ................................................................................ 124, 196
Controller and Identifier Check............................................... 39 Using .................................................................................... 125
Controller Time/Date Check ................................................... 40 View Details ......................................................................... 373
Default Comms Connection .................................................... 72 Strategy Library
Default Display Language ...................................................... 74 Collapse ................................................................................ 333
Default Display Options.......................................................... 75 Display ................................................................................. 333
Default Labels ......................................................................... 43 Dock .............................................................................. 333, 334
Default Language .................................................................... 69 Expand ................................................................................. 333
Gap in the Sequence Table Between Pages ............................. 77 Hide ...................................................................................... 333
Inputs .................................................................................... 194 Move .................................................................................... 349
IQ3 or IQ4 Directory Module Parameter Defaults .................. 79 Resize ............................................................................ 333, 351
IQ3 or IQ4 Display Module Parameter Defaults ..................... 80 Undock ................................................................................. 333
Lan Details ............................................................................ 156 Strategy Pages
Loading of Site Data ............................................................... 81 Add ................................................................................ 108, 313
Module Prompts...................................................................... 86 Add Graphics........................................................................ 276
Module Tracking..................................................................... 68 Add Text ....................................................................... 116, 277
Next Module Number ........................................................... 358 Add Unplaced Modules ........................................................ 317
Notes Printed on the Front Page............................................ 284 Close .................................................................................... 322
Outputs ................................................................................. 194 Copy to Clipboard ................................................................ 325
Page Details .......................................................................... 356 Delete ................................................................................... 330
Print Options ........................................................................... 76 Delete Graphics .................................................................... 277
Printer ..................................................................................... 82 Delete Text ........................................................................... 277
Priority Array Labels .............................................................. 82 Display ................................................................................. 347
Project Location ...................................................................... 85 Go to..................................................................................... 347
Refresh Options ...................................................................... 83 Move Modules...................................................................... 200
Saving of Site Data ................................................................. 81 Move Text and Lines ............................................................ 277
Stores .................................................................................... 194 Print ...................................................................................... 285
Strategy Block Location.......................................................... 84 Strategy Simulation ................................................................... 277
Strategy Block Module Start Numbers.................................... 55 Strategy Sync Check ................................................................... 41
Strategy Sync Check ............................................................... 41 Sum IC Comms Modules .......................................................... 530
Time Difference ...................................................................... 78 Switch Modules .................................................................. 548, 696
Toolbar Theme........................................................................ 78 Synchronised Plot Modules ....................................................... 603
Whether the Tracker Window is Displayed ............................ 86 System
Which Configuration Parameters are Displayed ................... 358 Information ........................................................................... 202
Which Toolbars Are Displayed ............................................... 87 Navigate ............................................................................... 386
Spreadsheet ................................................................................ 153 System Performance Module

Index
Strategy Block ...................................................................... 316 Undock
System View Project View ......................................................................... 332
Collapse ................................................................................ 333 Strategy Library.................................................................... 333
Delete Objects ....................................................................... 401 System View ........................................................................ 333
Display.......................................................................... 333, 379 Unplaced Modules.............................................................. 290, 317
Dock ............................................................................. 333, 334 Update a Project ........................................................................ 296
Expand .................................................................................. 333 Update Strategy ......................................................................... 290
Hide ...................................................................................... 333 Upgrade
Move ..................................................................................... 349 IQSET .................................................................................... 26
Refresh .................................................................................. 387 Upgrading.................................................................................. 366
Resize ........................................................................... 333, 351 Upload ....................................................................................... 419
Undock ................................................................................. 333 Strategy ......................................................................... 127, 368
T USB
TCL Connect over ........................................................................ 377
Inputs .................................................................................... 193 USB Driver
Outputs ................................................................................. 193 Install...................................................................................... 32
TCL Application ........................................................................ 336 Use
Test the Strategy ........................................................................ 277 Command Line Toolbar........................................................ 131
Text Strategy Blocks ..................................................... 124, 125, 196
Add ............................................................................... 116, 277 The Command Bar ............................................................... 311
Delete .................................................................................... 277 TO Connectives .................................................................... 116
Move ..................................................................................... 277 Use the BUA Editor .................................................................. 362
Time Difference ........................................................................... 78 Use the TUA Editor................................................................... 363
Time Modules .................................................................... 613, 716 User Modules ............................................................................ 717
Time Proportional + Override Driver Modules .......................... 485 Add ................................................................................ 248, 250
Time Proportional Driver Modules .................................... 481, 660 Delete ................................................................................... 250
Time Schedule Modules ............................................................ 622 Edit ....................................................................................... 251
Timer Logic Modules ........................................................ 573, 705 Guest User ............................................................................ 248
Tip of the day Set up ................................................................................... 251
Disable .................................................................................... 92 User Nodes
Enable ..................................................................................... 92 Activate Refresh ................................................................... 408
View ..................................................................................... 333 Add User Parameters ............................................................ 402
TO Connective Delete ................................................................................... 402
Add ....................................................................................... 313 Delete User Parameters ........................................................ 402
Using..................................................................................... 116 Edit ....................................................................................... 403
Tool Tips Refresh ................................................................................. 408
Disable .................................................................................... 92 User Parameters ........................................................................ 402
Enable ..................................................................................... 92 Users
Toolbars Delete ..................................................................................... 30
Display.................................................................................... 87 Edit ......................................................................................... 30
Move ..................................................................................... 349 V
Themes ................................................................................... 78 Values
TOPS ......................................................................................... 353 Link to .................................................................................. 201
Tracker Window View
Display.................................................................................... 86 Autodialling Information ...................................................... 331
Translate Communications Information ............................................... 332
Print Labels ............................................................................. 69 Device Details ...................................................................... 371
Translated Labels Free Modules ........................................................................ 374
Export ............................................................................... 58, 90 Lan Details ........................................................................... 372
Import ............................................................................... 57, 89 Module List .......................................................................... 374
Trend Alarm Destination Modules ..................................... 435, 645 NTD Differences .................................................................. 293
Trend Network ............................................................. 34, 376, 377 NTD List .............................................................................. 293
Trend System Sites .................................................................... 383 Page Details .......................................................................... 372
TRIG Function Modules ............................................................ 518 Project Details ...................................................................... 373
Triggered Plot Modules ............................................................. 606 Project View ......................................................................... 332
TRUNC Function Modules ........................................................ 518 Strategy Block Details .......................................................... 373
TUA Strategy Issues ...................................................................... 374
Delete ...................................................................................... 71 Strategy Library.................................................................... 333
Edit ......................................................................................... 71 Strategy Page ........................................................................ 347
TUA Editor ................................................................................ 363 Tip of the Day ...................................................................... 333
Type 14 (Wallbus) Network Modules ................................ 591, 709 Virtual CNC Modules ............................................................... 638
Type 16 (Trend Client) Network Modules ................................. 592 W
Type 17 (Trend Serial) Network Modules ................................. 593 Web page................................................................................... 423
Type 2 (Wallbus) Interface Modules ................................. 552, 697 What's New ................................................................................. 16
U Windows
Unassign Position.......................................................................... 350, 358
I/O Channels ......................................................................... 212 X
Undefined Connectives XLS Files ........................................................................... 340, 341
Add ....................................................................................... 314 XNC ........................................................................... 190, 193, 194
Defining ................................................................................ 328 Application File .................................................................... 193
Destination ............................................................................ 328 XNC Interface Modules ............................................................ 549
To a Module.......................................................................... 314 Link the XNC Application File ............................................ 193
To a Node ............................................................................. 315
Undo .......................................................................................... 359 Z
Compare................................................................................ 295 Zoom In/Out .............................................................................. 375

St. Mark's Court, North Street, Horsham, West Sussex, RH12 1BW, UK. Tel:+44 (0)1403 211888, www.trendcontrols.com

IQSET Manual V7.60

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

IQSET Manual V7.60

Hochgeladen von

Copyright:

Verfügbare Formate

IQSET Manual

Applies to v7.60 software

1 ABOUT THIS MANUAL ............................................................................................................................... 15

2 WHAT'S NEW IN VERSION V7.60............................................................................................................. 17

3 ABOUT IQSET ............................................................................................................................................... 19

5 SECURING IQSET ........................................................................................................................................ 37

6 CUSTOMISE IQSET ..................................................................................................................................... 39

IQSET Manual TE200147 Issue 25 : 03-Feb-2020 3

7 QUICK TOURS .............................................................................................................................................. 95

4 IQSET Manual TE200147 Issue 25 03-Feb-2020

8 CREATE A BTL COMPLIANT STRATEGY .......................................................................................... 135

9 ENGINEER IQ CONTROLLERS .............................................................................................................. 137

IQSET Manual TE200147 Issue 25 03-Feb-2020 5

10 IQ INTERFACING ...................................................................................................................................... 289

11 COMPARING STRATEGIES..................................................................................................................... 291

12 UPDATE A PROJECT ................................................................................................................................. 297

13 COMMISSIONING WITH LIVE VALUES .............................................................................................. 299

14 LIVE EDITING ............................................................................................................................................ 301

15 EXPORT STRATEGY FOR CUSTOM ORDERING .............................................................................. 307

16 GENERAL OPERATIONS ......................................................................................................................... 309

6 IQSET Manual TE200147 Issue 25 03-Feb-2020

IQSET Manual TE200147 Issue 25 03-Feb-2020 7

17 BROWSE THE SYSTEM ............................................................................................................................ 377

8 IQSET Manual TE200147 Issue 25 03-Feb-2020

APPENDICES ......................................................................................................................................................... 425

A1 IQ4 MODULES............................................................................................................................................. 427

IQSET Manual TE200147 Issue 25 03-Feb-2020 9

10 IQSET Manual TE200147 Issue 25 03-Feb-2020

IQSET Manual TE200147 Issue 25 03-Feb-2020 11

A2 IQECO MODULES ...................................................................................................................................... 641

12 IQSET Manual TE200147 Issue 25 03-Feb-2020

A3 COMMAND LINE COMMANDS .............................................................................................................. 719

A4 KEYBOARD SHORT CUTS ....................................................................................................................... 725

A5 3RD PARTY SOFTWARE LICENCES ..................................................................................................... 727

IQSET Manual TE200147 Issue 25 03-Feb-2020 13

14 IQSET Manual TE200147 Issue 25 03-Feb-2020

1 ABOUT THIS MANUAL

IQSET Manual TE200147 Issue 25 03-Feb-2020 15

1.2 Contacting Trend

16 IQSET Manual TE200147 Issue 25 03-Feb-2020

2 WHAT'S NEW IN VERSION V7.60

IQSET Manual TE200147 Issue 25 03-Feb-2020 17

18 IQSET Manual TE200147 Issue 25 03-Feb-2020

IQSET Manual TE200147 Issue 25 03-Feb-2020 19

3.1 The IQSET Window

3.1.1 Display Area

20 IQSET Manual TE200147 Issue 25 03-Feb-2020

IQSET Manual TE200147 Issue 25 03-Feb-2020 21

22 IQSET Manual TE200147 Issue 25 03-Feb-2020

IQSET Manual TE200147 Issue 25 03-Feb-2020 23

24 IQSET Manual TE200147 Issue 25 03-Feb-2020

IQSET Manual TE200147 Issue 25 03-Feb-2020 25

26 IQSET Manual TE200147 Issue 25 03-Feb-2020

IQSET Manual TE200147 Issue 25 03-Feb-2020 27

3. Click . This will open Pnet licencing portal.

28 IQSET Manual TE200147 Issue 25 03-Feb-2020

IQSET Manual TE200147 Issue 25 03-Feb-2020 29

5. Click Add. The New User dialogue box is displayed.

30 IQSET Manual TE200147 Issue 25 03-Feb-2020

8. In the User Role box click required user role.

5. Click the user that is to be deleted.

IQSET Manual TE200147 Issue 25 03-Feb-2020 31

7. Change the parameters if the user as required.

32 IQSET Manual TE200147 Issue 25 03-Feb-2020