Technical Handbook

Technical Handbook
Systems features and software training book
Version: 21 February 2017
PROSOFT Suite 3.6
TELETASK Technical Handbook_EN_V249.docx
TELETASK Handbook
Content >
Table of content
Table of content ............................................................................... 3
Introduction .................................................................................... 10
1. The TELETASK domotics system ............................................................ 10
2. Hardware and Software ............................................................................ 12
2.1. PROSOFT Suite .....................................................................................................12
2.1.1. Introduction ....................................................................................................................... 12
PROSOFT ..................................................................................... 14
3. Introduction ............................................................................................... 14
3.1. The basic flow diagram of a configuration session ..................................................14
3.2. The full flow diagram ...............................................................................................16
4. Starting up a new project .......................................................................... 17
4.1. Collecting the project information ............................................................................17
4.1.1. The TELETASK central unit ............................................................................................. 17
4.1.2. The list of rooms ............................................................................................................... 17
4.1.3. The list of outputs ............................................................................................................. 17
4.1.4. The list of inputs................................................................................................................ 18
4.1.5. Information about the electrical contractor or system integrator. ..................................... 18
4.1.6. Information about the owner of the house ........................................................................ 18
4.2. Starting a project .....................................................................................................18
4.2.1. Installing PROSOFT on a PC ........................................................................................... 18
4.2.2. Starting PROSOFT the first time ...................................................................................... 19
4.2.3. Select the central unit which will be used in your project ................................................. 19
4.2.4. Saving project option on the PC ....................................................................................... 19
4.2.5. Project options (menu 'extra') ........................................................................................... 19
4.2.6. Cameras & Doors ............................................................................................................. 26
4.3. TELETASK CLOUD installation...............................................................................31
4.3.1. Introduction ....................................................................................................................... 31
4.3.2. Create a SI (System Integrator) account first ................................................................... 31
4.3.3. Connect the central unit to the TELETASK cloud service ................................................ 31
4.3.4. Create and configure the users ........................................................................................ 32
4.3.5. Cloud access .................................................................................................................... 33
4.3.6. Transmit the PROSOFT file to the central unit(s) ............................................................. 34
4.3.7. Camera’s on iSGUI without Dynamic DNS or fixed IP- address ...................................... 34
4.3.8. Network specifications (used ports) .................................................................................. 35
4.4. Use of passwords and codes ..................................................................................36
4.4.1. User code ......................................................................................................................... 36
4.4.2. PROSOFT password ........................................................................................................ 36
4.4.3. Technical code.................................................................................................................. 37
5. The rooms ................................................................................................. 38
5.1. Introduction .............................................................................................................38
5.2. Overview of the rooms ............................................................................................38
5.2.1. List of rooms ..................................................................................................................... 38
5.3. Adding rooms to the list of rooms ............................................................................39
5.3.1. The different parameters for every room .......................................................................... 39
6. 'O' Units: Outputs ...................................................................................... 40
6.1. General notes .........................................................................................................40
6.1.1. Output ............................................................................................................................... 40
6.1.2. Output unit ........................................................................................................................ 40
6.1.3. Output numbers ................................................................................................................ 40
6.1.4. 'O' Address (Output Address) ........................................................................................... 41
6.2. Adding Output units.................................................................................................42
3
TELETASK Handbook
Content >
6.2.1. In practice ......................................................................................................................... 42
6.3. Assigning TELETASK Outputs. ...............................................................................43
6.3.1. The different available parameters: .................................................................................. 43
6.3.2. In practice: ........................................................................................................................ 44
6.4. Overview of the available TELETASK Output units and their parameters ................45
6.5. List of output units of your project. ...........................................................................46
6.5.1. Generating Lists on the screen of your PC ...................................................................... 46
6.6. TDS13530 Fan coil unit interface ............................................................................49
6.6.1. General ............................................................................................................................. 49
6.6.2. Configuring a Fan coil unit interface ................................................................................. 49
6.7. TDS13609: Dimmer interface 8x 0-10V ...................................................................51
6.7.1. Introduction ....................................................................................................................... 51
6.8. TDS13610: Fluorescent Dimmer Interface ..............................................................51
6.8.1. Introduction ....................................................................................................................... 51
6.9. TDS13620: DALI / DSI / DMX interface ...................................................................52
6.9.1. Introduction ....................................................................................................................... 52
6.9.2. DSI mode .......................................................................................................................... 53
6.9.3. DMX mode ........................................................................................................................ 54
6.9.4. DALI mode ........................................................................................................................ 54
7. 'I' units: Inputs and others ......................................................................... 57
7.1. General notions .......................................................................................................57
7.1.1. 'I' interfaces: Inputs and others ......................................................................................... 57
7.1.2. 'I' Address: ........................................................................................................................ 58
7.2. Adding TELETASK 'I' interfaces ..............................................................................59
7.2.1. Parameters for adding new 'I' interfaces: ......................................................................... 59
7.3. General 'I' interfaces – Specific parameters ............................................................61
7.3.1. Common setting................................................................................................................ 61
7.3.2. Advanced settings for AURUS touch panels .................................................................... 65
7.3.3. AURUS-2 SENSE ............................................................................................................. 69
7.3.4. AURUS-4 TEMP (TDS12026) .......................................................................................... 72
7.3.5. AURUS-OLED (TDS12022) and AURUS-OLED PLUS (TDS12032) .............................. 78
7.3.6. AURUS-TFT (TDS12064) ................................................................................................. 86
7.4. Digital Input interfaces – Specific parameters..........................................................95
7.5. Analogue input interface – Specific parameters ......................................................97
7.6. Audio Interfaces – Specific parameters .................................................................105
7.7. Overview list of 'I' Interfaces of your domotics project. ..........................................106
7.8. TDS12116 Digital Input interface with Pulse counter sensor. ................................109
7.8.1. Hardware: ....................................................................................................................... 109
7.8.2. Software: ......................................................................................................................... 109
7.9. TDS14061 HVAC Modbus Master interface ..........................................................112
7.9.1. Adding a HVAC Modbus Master interface to the Interfaces list. .................................... 113
7.9.2. Modbus Slave interface selection ................................................................................... 114
7.9.3. Configure the AUTOBUS Address ................................................................................. 115
7.9.4. Configure Modbus Slave interface ................................................................................. 115
7.10. TDS14065 : IR-COOKIE INTERFACE ................................................................117
7.10.1. TDS14065: IR-COOKIE INTERFACE (HVAC AND A/V CONTROL) .......................... 117
7.10.2. INTRODUCTION .......................................................................................................... 117
7.10.3. CONFIGURATION........................................................................................................ 117
7.10.4. RECORD (=LEARN) THE IR-CODES (HVAC APPLICATION) ................................... 118
7.10.5. Batch recording:............................................................................................................ 121
7.10.6. USING THE IR-COOKIE ON BUTTONS, TOUCH PANELS, MOOD’S, … ................. 122
7.10.7. A/V INTEGRATION WITH THE IR-COOKIE INTERFACE .......................................... 123
7.10.8. VRF/VRV INSTEAD OF IR-FLASHER CONTROL ...................................................... 124
7.11. TDS15200 Airco Software license .......................................................................125
7.11.1. Daikin Integration .......................................................................................................... 125
7.11.2. Mitsubishi Electric Integration ....................................................................................... 127
7.12. Extra Parameters for External HVAC systems ....................................................128
7.12.1. Indoor unit properties .................................................................................................... 128
4
TELETASK Handbook
Content >
7.12.2. Mode & Speed .............................................................................................................. 128
7.12.3. Preset Temperature settings: ....................................................................................... 128
8. Functions overview ................................................................................. 129
8.1. The Relay functions ..............................................................................................129
8.2. The Dimmer functions ...........................................................................................130
8.3. Working with motors..............................................................................................133
8.3.1. Motor interfaces .............................................................................................................. 133
8.3.2. The Motor function .......................................................................................................... 138
8.4. The Fans: ..............................................................................................................140
8.5. The Fan functions: ................................................................................................141
8.6. The Timed functions..............................................................................................142
8.7. The Motion detector function .................................................................................144
8.8. The Sensor Functions ...........................................................................................146
8.9. The Fan (exhaust) function ...................................................................................149
8.10. The Local Mood function .....................................................................................151
8.11. The Timed Local Mood function ..........................................................................153
8.12. The General Mood function .................................................................................155
8.13. The Transparent function ....................................................................................156
8.14. The Messages and Alarms functions...................................................................157
8.15. The TP Buzzer functions .....................................................................................160
8.16. The 'If-Then-Else' function ...................................................................................161
8.17. The Process functions .........................................................................................164
8.18. The 'Flag' function ...............................................................................................166
8.19. The Condition......................................................................................................167
8.20. Calculation function .............................................................................................169
8.21. The Service functions ..........................................................................................170
8.22. The clock functions .............................................................................................171
8.23. The audio functions .............................................................................................173
8.24. Send IR/RS232 OR IP Code ...............................................................................175
8.25. The Auto start function ........................................................................................176
8.26. The Display Functions .........................................................................................177
8.27. Touch screen functions .......................................................................................179
8.28. The step function.................................................................................................179
8.29. The RGB function................................................................................................181
9. Communication ....................................................................................... 183
9.1. Connecting your PC with the central unit ...............................................................183
9.1.2. USB Communication ...................................................................................................... 184
9.1.3. Ethernet Communication ................................................................................................ 191
9.2. Connection trouble shooting ..................................................................................198
9.2.1. In practice ....................................................................................................................... 198
9.3. Communication with the DOIP central unit ............................................................199
9.3.1. Send ............................................................................................................................... 199
9.3.2. Receive ........................................................................................................................... 200
10. Overview of your domotic project ......................................................... 201
10.1. Print your project .................................................................................................201
10.2. Hierarchic List .....................................................................................................202
11. Diagnostics ........................................................................................... 203
11.1. General ...............................................................................................................203
11.2. Relays .................................................................................................................204
11.3. Dimmers .............................................................................................................205
11.4. Motors .................................................................................................................206
11.5. Digital Inputs .......................................................................................................207
11.6. Analogue Inputs ..................................................................................................208
11.7. Audio Zones ........................................................................................................208
11.8. Other Functions ..................................................................................................209
5
TELETASK Handbook
Content >
11.9. Interfaces ............................................................................................................210
11.10. Monitor ..............................................................................................................211
11.10.1. S (State changed) ....................................................................................................... 212
11.10.2. D (Digital Input Pressed) ............................................................................................ 212
11.10.3. A (Activate Function) .................................................................................................. 213
11.10.4. V (Analogue Value) .................................................................................................... 214
11.10.5. L (Led Feedback) ....................................................................................................... 214
11.10.6. I (Interface Started) ..................................................................................................... 214
11.10.7. F (Function Set) .......................................................................................................... 215
11.10.8. T (Tag) ........................................................................................................................ 215
11.10.9. Q (Quarter Total) ........................................................................................................ 215
11.10.10. P (Preset Changed) .................................................................................................. 216
11.10.11. B (Unknown Button Pressed) ................................................................................... 216
11.10.12. C (Central Unit Command) ....................................................................................... 217
11.10.13. H (Hour) .................................................................................................................... 217
TIMESOFT................................................................................... 218
12. Actions based on time programs .......................................................... 218
12.1. Introduction .........................................................................................................218
12.2. The different clock tables. ...................................................................................218
12.3. Start TIMESOFT. ................................................................................................219
12.4. Visualisation ........................................................................................................219
13. Defining a clock action .......................................................................... 221
13.1. Adding a new clock action ...................................................................................221
13.1.1. Add a clock action......................................................................................................... 221
13.1.2. The different available parameters ............................................................................... 221
13.2. Editing a clock action ..........................................................................................223
13.3. Remove a clock action ........................................................................................224
13.4. The 'Communication' menu in TIMESOFT ..........................................................224
CARDSOFT – PORTA ................................................................. 225
14. Introduction ........................................................................................... 225
15. Terminology .......................................................................................... 225
16. Steps to set up CARDSOFT-PORTA ................................................... 225
17. Access control options in PROSOFT .................................................... 225
18. Add Proximity readers........................................................................... 228
19. Create Users and Groups ..................................................................... 229
19.1. Users ..................................................................................................................229
19.2. Groups ................................................................................................................230
20. Define ‘Access rights’............................................................................ 231
21. Access management on users and groups .......................................... 234
22. Schedule E-mail reports with TIMESOFT (or a function) ...................... 235
GUISOFT ..................................................................................... 237
23. Personalised graphical control .............................................................. 237
23.1. Introduction .........................................................................................................237
23.1.1. Graphical User Interface (GUI) ..................................................................................... 237
23.2. Glossary ..............................................................................................................237
23.2.1. GUISOFT ...................................................................................................................... 237
23.2.2. iSGUI/GUI(+)/Control Tower client configuration ......................................................... 237
23.2.3. GUI Runtime (GUI/GUI+).............................................................................................. 237
23.2.4. iSGUI ............................................................................................................................ 238
23.2.5. Control Tower ............................................................................................................... 238
23.2.6. Target Device ............................................................................................................... 238
23.3. System Requirements .........................................................................................239
23.4. Schematic Configurations ...................................................................................240
23.4.1. Connect one target system with the domotics .............................................................. 240
6
TELETASK Handbook
Content >
23.4.2. Connect two or more target systems with the domotics. .............................................. 240
23.5. GUISOFT Licence ...............................................................................................242
23.5.1. TELETASK license system ........................................................................................... 242
24. Making a GUI/GUI+ .............................................................................. 244
24.1. Requirements Session workflow .........................................................................244
24.2. CREATING A GUI/GUI+ .....................................................................................245
24.3. GUI Selection ......................................................................................................245
24.4. GUI Properties ....................................................................................................246
24.5. GUISOFT Screen ................................................................................................248
24.5.1. The GUISOFT menu..................................................................................................... 248
24.5.2. The functions and symbols library ................................................................................ 248
24.5.3. The GUI Preview .......................................................................................................... 249
24.6. Adding items to the GUI ......................................................................................249
24.6.1. Drag and drop ............................................................................................................... 249
24.6.2. Positioning (grid) ........................................................................................................... 249
24.6.3. Edit the GUI Icon .......................................................................................................... 250
25. Creating a iSGUI ................................................................................... 253
25.1. Start with the GUISOFT ......................................................................................253
25.2. GUI Selection ......................................................................................................253
25.3. iSGUI Features ...................................................................................................254
25.4. GUISOFT Screen ................................................................................................255
25.4.1. The GUISOFT menu..................................................................................................... 255
25.4.2. The Functions ............................................................................................................... 255
25.4.3. The iSGUI preview........................................................................................................ 255
25.5. Adding items to the iSGUI. ..................................................................................256
25.5.1. Drag and drop. .............................................................................................................. 256
25.5.2. Edit the iSGUI Icon ....................................................................................................... 256
26. Creating a Control Tower ...................................................................... 257
26.1. Terminology ........................................................................................................257
26.2. Workflow .............................................................................................................257
26.3. Define Functions to monitor and control ..............................................................257
26.4. Create an initial PROSOFT file............................................................................257
26.5. Create a Control Tower configuration ..................................................................258
26.5.1. Control Tower configurator screen ............................................................................... 258
26.5.2. Define Central Units ..................................................................................................... 258
26.5.3. Define Alarms ............................................................................................................... 260
26.5.4. Control Tower settings .................................................................................................. 262
26.5.5. Add Central units to the overview page ........................................................................ 264
26.5.6. Saving and opening a Control Tower Configuration..................................................... 265
26.6. Event logs (alarms) .............................................................................................265
27. Get the GUI ready for use. .................................................................... 266
27.1. Importing an activation file. ..................................................................................266
27.2. Exporting the GUI files (only for GUI) ..................................................................266
27.3. Install 'GUI Runtime' ............................................................................................266
27.3.1. GUI/GUI+ ...................................................................................................................... 266
27.3.2. iSGUI (iPhone, iPod Touch, iPad) ................................................................................ 266
27.3.3. iSGUI (Android) ............................................................................................................ 266
27.3.4. iSGUI (BlackBerry) ....................................................................................................... 266
27.3.5. iSGUI (Windows PC, macOS) ...................................................................................... 266
27.3.6. Control Tower ............................................................................................................... 267
27.4. Copy GUI Files to the target device .....................................................................267
27.4.1. iSGUI (iOS, Android, BlackBerry, Windows PC, macOS) ............................................ 267
27.4.2. GUI+ (MS Windows) ..................................................................................................... 267
27.4.3. GUI ............................................................................................................................... 267
27.4.4. Control Tower ............................................................................................................... 267
27.5. Problem Solving ..................................................................................................268
7
TELETASK Handbook
Content >
28. Video door phone/Intercom on GUI+ and MAIOR Video door phone on
GUI+ (TDS12052 and TDS12053 only). ..................................................... 268
28.1. PROSOFT SUITE ...............................................................................................268
28.1.1. Create IP cameras / Doors ........................................................................................... 268
28.1.2. Create a GUI+ .............................................................................................................. 270
28.1.3. Add the video door phone item (optional) .................................................................... 270
28.2. GUI+ ...................................................................................................................272
28.2.1. Set Up VoIP server and VoIP user ............................................................................... 272
28.2.2. Assign a Fixed IP address to MAIOR ........................................................................... 273
AV-SOFT ..................................................................................... 274
29. Multi-Room Multi-Source ...................................................................... 274
29.1. Introduction .........................................................................................................274
29.2. Multi-room/Multi-source: the differences..............................................................275
29.3. Phase 1: Choose the wanted audio/video configuration ......................................276
29.3.1. Define the requirements ............................................................................................... 276
29.4. Phase 2: Assigning the RS232 Port and the IR flashers. .....................................279
29.5. Phase 3: Configuring the Universal RS232 AV or IP interface. ............................281
29.5.1. Assigning IR codes, RS232 strings or IP strings .......................................................... 281
29.5.2. Entering the audio configuration in AV-SOFT .............................................................. 281
29.5.3. Assigning Sources ........................................................................................................ 282
29.5.4. Assigning Zones ........................................................................................................... 283
29.5.5. Configuring the RS232 universal AV interface. ............................................................ 283
29.5.6. Configuring the AV-IP license. ...................................................................................... 284
29.6. Phase 4: Configuring the audio buttons of the domotics installation. ...................284
30. Edit library ............................................................................................. 286
30.1. Add and edit devices into the library. ...................................................................286
30.1.1. General setup ............................................................................................................... 286
30.1.2. Types of Codes............................................................................................................. 288
30.2. Record IR codes .................................................................................................289
30.3. Paste IR codes ....................................................................................................291
30.4. RS232/IP ............................................................................................................291
30.4.1. RS232/IP ‘send codes’ ................................................................................................. 291
30.4.2. Feedback Codes RS232 and IP ................................................................................... 292
30.5. Polling codes.......................................................................................................304
30.6. Special codes......................................................................................................305
30.6.1. EXTRA CODES for iSGUI V2.5 .................................................................................... 305
30.6.2. 'Link zone with' action ................................................................................................... 306
30.7. BACK-UP the AV-SOFT Library ..........................................................................307
31. Connection to the RS232 UNIVERSAL AV INTERFACE ..................... 308
31.1. RS232 connection ...............................................................................................309
31.2. Splitter Cable for audio system............................................................................309
32. Audio-IP software licence ..................................................................... 310
DALISOFT ................................................................................... 311
33. Configuring DALI ballasts with the TDS20620V2 DALI Tool ................ 311
Multiple DoIP Central Units .......................................................... 314
34. Coupling of multiple Central Units. ....................................................... 314
35. PROSOFT SUITE ................................................................................. 315
35.1. PROSOFT...........................................................................................................315
35.1.1. Central Unit bounded .................................................................................................... 315
35.1.2. Interfaces ...................................................................................................................... 315
35.1.3. General moods ............................................................................................................. 316
35.1.4. Step Functions .............................................................................................................. 316
35.1.5. Touch Panels ................................................................................................................ 316
35.2. TIMESOFT ..........................................................................................................316
8
TELETASK Handbook
Content >
35.3. CARDSOFT ........................................................................................................316
35.4. GUISOFT ............................................................................................................316
35.5. AV-SOFT ............................................................................................................316
35.6. Communication ...................................................................................................316
Energy management ................................................................... 317
36. Overview of energy visualisation .......................................................... 317
Application Examples................................................................... 319
37. Real examples ...................................................................................... 319
37.1. Introduction .........................................................................................................319
37.2. How to integrate a heating/cooling system ..........................................................319
37.2.1. De basic operation of a heating/cooling control ........................................................... 320
37.2.2. The available internal temperature control algorithms ................................................. 320
37.2.3. Setting up the output control of the heating/cooling system ......................................... 321
37.3. How to integrate a light sensor ............................................................................323
37.3.1. Scope ............................................................................................................................ 323
37.3.2. Application .................................................................................................................... 323
37.3.3. How to add a light sensor to your project ..................................................................... 323
37.3.4. The argument 'Hysteresis' ............................................................................................ 324
37.3.5. The TELETASK Lux-values table ................................................................................. 325
37.3.6. The meaning of a Lux value; practical approach.......................................................... 326
37.4. How to setup an access control system ..............................................................327
37.4.1. Description of the case study example ......................................................................... 327
37.4.2. Needed products: ......................................................................................................... 327
37.4.3. In practice ..................................................................................................................... 327
37.5. Configuring a NUVO installation with three RS232 interfaces..............................330
37.5.1. Phase 1: Define the desired audio/video configuration: ............................................... 330
37.5.2. Phase 2: Assigning the RS232 Port (s). ....................................................................... 330
37.5.3. Phase 3: Configuring the RS232 universal AV interface. ............................................. 331
37.6. B&O Integration ..................................................................................................333
37.6.1. Integration possibilities ................................................................................................. 333
37.6.2. Controlling B&O audio devices from TELETASK ......................................................... 334
37.6.3. Controlling TELETASK from the B&O Remote Control ................................................ 338
37.7. Implementing NuVo with Audio IP License (TDS15240) ......................................343
37.7.1. Necessary items: .......................................................................................................... 343
37.7.2. Integration: .................................................................................................................... 343
9
TELETASK Handbook
Introduction >
TDS
Introduction
1. The TELETASK domotics system
This guide provides an overview of how to configure a TELETASK Home Automation System (TDS). It
is a complete guide to the PROSOFT -Suite configuration software and other TELETASK products
with additions and tips for a state-of-the-art integration.
Prior to the configuration part you will find:
 Capturing the requirements and wishes of the end-user, in close cooperation with the
end-user, architect and/or interior designer.
 The Lighting plan
 Choosing the appliances, motors, etc which will integrated by the to the TDS.
 Choosing the appropriate heating/cooling system.
 Choosing the appropriate security system.
 Capturing the typical routes throughout the house, to be able to decide where to place
touch panels or screen.
Once all this is done, you can start configuring (also called 'programming') the system.
Comfort and flexibility are not only important for the user, but also for the integrator. The simplicity and
comfort for the installer of a TELETASK automation system is possible thanks to its unique
construction. The specific structure is characterized by the strict separation of inputs and outputs in the
system.
With this way of working there is still something missing because there is nothing which defines yet
that the push button on the wall is for example going to control the ceiling light in the dining room.
Therefore the system needs a relation which is to be defined between that particular input and the
related output.
In the TELETASK domotics systems the relation between inputs and outputs will be defined in the
central unit. This central unit becomes the heart of the system and is a far more powerful and reliable
solution than working with a decentralised approach which has by definition a more complex
configuration and a larger chance that information gets lost.
In large installations you will learn that a multi-central unit approach will offer you simplicity, highest
reliability and distributed intelligence without the need of a master-slave setup like traditional systems
use. With a TELETASK system there is no central unit behaving like a master, so there are no such
slaves either. In case of a failure, this guarantees no loss of functionalities except for the defect part
itself. In a decentralised setup where a master can fail, the whole system may go down or at least lose
a number of features which also effect non-defective parts of the system.
10
TELETASK Handbook
Introduction >
TDS
With a TELETASK domotics system, the central unit (with power supply) is the most important
component. The inputs and outputs can communicate with this central unit. These are connected via a
two-wire high-speed data cable (+ two wires for 12V power supply- which we call the 'AUTOBUS'
cable. In traditional installations this would require a whole bunch of cables.
This way the input-to-output relations become both simple and flexible, because they are not defined
as in a traditional solution, but by the powerful and flexible TELETASK software relations. These
relations are configured in the TELETASK PROSOFT Suite. PROSOFT is offered free of charge with
any TELETASK system and can be downloaded from the website.
As a result of this, when for example pushing a wall mounted momentary push-button (= the input), the
ceiling light in the dining room (= the output), can be switched (= the relation between the input and
the output) on/off.
The relations can be defined by you, by means of PROSOFT software. PROSOFT was specially
developed by TELETASK to make it possible to define the inputs, outputs and the relations between
them on a standard MS Windows based PC. As soon as your relations are defined, they can be
downloaded to the TELETASK central unit which will keep them in its non-volatile memory, where they
always remain after disconnecting the PC, even when power fails for short or long (unlimited) periods.
As soon as the relations are downloaded into the central unit, the PC can be disconnected from the
central unit and is no longer needed. You will be able to control all integrated (= connected) lights,
curtains, shutters, heating, cooling, audio, etc… as defined. You can control all these outputs by
means of standard buttons and specific touch panels, sensors, touchscreens or even by remote
control, by mobile phone or on a PC, PDA/Webpad via Ethernet over LAN/WAN wired- or wireless
connections.
11
TELETASK Handbook
Introduction >
Software
2. Hardware and Software
You will have noticed that there are both hardware and software items to be distinguished.
‘The hardware part’ contains the different TELETASK components and the connection to the central
unit(s). All hardware components have their own specific features and may behave as an input, an
output or sometimes even both of them. To find out more details about the hardware and its hardware
aspects, please refer to the TELETASK ''datasheets'.
‘The software part’ contains the creation of the relations between the inputs and outputs, defining
extra functions, setting up integrations like heating/cooling, audio, setting clocks, defining access
control, etc…
2.1. PROSOFT Suite
2.1.1. Introduction
With PROSOFT SUITE you can define all integrations within your home automation project. If
you install and run PROSOFT, you will see it consists of 5 different parts:
PROSOFT Suite
PROSOFT
This is the main and the most important software part. All
relations between inputs and outputs are defined in
PROSOFT. The file which is generated by PROSOFT is
also the basic file which is used in the other software
packages that are explained below.
TIMESOFT
In TIMESOFT you have an electronic calendar in which
you can enter actions (for example switching a light or
change the temperature at a certain time of the day)
based on the internal clock of the central unit.
Click the TIMESOFT icon to open the calendar and
configure the desired clock actions.
CARDSOFT
CARDSOFT is another part of the PROSOFT Suite which
is used to enter and edit the chip cards and tags which are
to be used at the integrated access control interfaces from
TELETASK. Click the CARDSOFT icon to define the
cards or tags for the actual project.
GUISOFT
GUISOFT is used to generate one or more GUI’s (both for
standard PC and/or smaller mobile devices). With these
GUI's you are able to control the TELETASK domotics
system based on floor plans or menu's depending on the
device you are using).
AV-SOFT
AV-SOFT is used to enter all needed parameters for the
integration of any audio, video or home theatre system
using the universal RS232 interface TDS14042 or an AVIP license TDS15240. In AV-soft you can use existing
protocols or add a custom protocol.
12
TELETASK Handbook
Introduction >
Software
 To edit older projects, IR-soft is used next to the PROSOFT Suite. IR-SOFT is only
needed for changes on older projects where the TDS14042 IR-Learnable Interface or the
TDS14045 Xantech Interface has been used.
For older installations (before V3.0):
 PROSOFT Suite makes the file management for every project easier because all
project data is stored in one file. The PROSOFT Suite '.nbt' file contains all data that
previously (existing installations) was stored in three different files ('.nbt', '.clk' and '.crt'
files). The file generated by IR-SOFT (if used) stays a separate file.
 PROSOFT Suite is able to read with ease all your old '.nbt' files starting from
PROSOFT V2.75. Files made in versions before PROSOFT V2.75 can be easily
converted by opening them in PROSOFT V2.75 and saving them with a new name in
that software version. Save the .nbt file in this software version with a new name.
Remarks: For this conversion you don't need upgrades (no new EEPROM chips).
 Your old TIMESOFT ('.clk') and CARDSOFT ('.crt') files can be imported in the
TIMESOFT and CARDSOFT mode of PROSOFT Suite by clicking respectively 'File>
Import clocks (old .clk)' or 'File'>Import cards (old .crt)'.
In this technical handbook you will find all software aspects of your TELETASK domotics
system explained in detail. Because the hardware and the software items are connected close
to each other, we will regularly refer to the DATA SHEETS handbook where you can find any
specific datasheet you may need.
You can always download the latest version of most of the documents from the TELETASK
website www.teletask.be. If you are using the latest version of the PROSOFT Suite, you can
also open this Technical Handbook and the Datasheets Handbook via the Help menu.
 The PROSOFT Suite uses the .NET (read 'dotnet') surrounding. When installing
PROSOFT from the supplied CD-rom it will be installed when needed. More recent PC's
contain the .NET surrounding by default.
 In exceptional cases it can be necessary to install this .NET surrounding separately.
That's when the PC doesn't contain it and when PROSOFT was downloaded from the
TELETASK website.
13
TELETASK Handbook
PROSOFT >
Introduction
PROSOFT
3. Introduction
PROSOFT is the main software package to configure a TELETASK domotics installation. In
PROSOFT you will define all the relations between all earlier defined outputs and inputs of your
system.
Before you can start making relations, you need to enter the hardware configuration of your
TELETASK domotics installation. All used parts will have to be entered and given some or more extra
parameters.
Although every TELETASK installation is different, there is a fixed road map to be followed step by
step. The different steps are covered in the headings below.
3.1. The basic flow diagram of a configuration session
Setting up the relation between an input and an output is basically very simple. There are only about
three steps to be done to define that for example a certain light is switched on/off by means of a
certain (momentary) push button on the wall:
1
2
3
Configure the light
(= an output relay of the
system. for example relay
nr. 1)
Configure the button
or touch panel button
(= an input, for example
the button in the kitchen
which is connected to the
system input nr. 1)
Define the relation
between the input
and the output
(example: 'SWITCH' on/off)
Another very powerful relation can be the control of a number of outputs (loads) by only one button.
This seems more complex, but you can define the relation between the button and the different
outputs in only three steps.
14
TELETASK Handbook
PROSOFT >
1
Configure the
connected lights
2
Configure the button
3
4
Introduction
(outputs)
(input)
Configure the
function which
contains all the
outputs
(ex: list of all outputs which
will have to be controlled at
once)
Define the necessary
relation between a
button and the
custom made
function
(ex. 'local mood')
All relations which are defined between the inputs and the outputs are always based on one of the two
flow diagrams above. It is the functionality of the chosen relation (sometimes this can be more than
one function) between the inputs and the outputs which may increase the level of complexity of your
work.
15
TELETASK Handbook
PROSOFT >
Introduction
3.2. The full flow diagram
The basic flow diagram above shows the simple basic task to be done in PROSOFT: defining relations
between inputs and outputs. Because there is also the opening of the program, sending the
configuration file to the central unit, etc… below there is the extended basic flow diagram which
contains all necessary steps to be taken to complete a TELETASK / PROSOFT task from scratch to
the end point where you can switch off your PC.
1
The start-up of a new
installation
2
Enter all the rooms of
your project.
3
Enter all outputs and
give them a name
(example: kitchen, office,
garage, toilet 1, garden,
etc.)
(R1 = light in toilet nr.1)
(R2 = wall socket on the
terrace)
4
5
6
7
Enter all inputs.
(Input 1 = "left button of the
double button panel in the
toilet nr. 1")
Define all necessary
functions
Define the relations
Save and send the
generated file from
the PC to the central
unit
Collect all project related information
Open the new project (start PROSOFT on
your PC)
Enter all rooms
Add all necessary output interfaces
Give a name to every single output
Add all necessary input interfaces
Enter the name of the input
Define the functions
Enter the relations
Save your file on the PC (CD-rom)
Send from PC to central unit
The different steps in this flow diagram will be explained in detail in the text below.

IMPORTANT: Don't forget to make a back-up of your .nbt file which is generated by the
PROSOFT Suite. It is important to keep this back-up file available over the full life-time of the
installation.
16
TELETASK Handbook
PROSOFT >
Start of a Project
4. Starting up a new project
4.1. Collecting the project information
Before starting up a new project, it is recommended to have all technical details of the TELETASK
hardware components which are needed in the project. This information is to be given by the system
integrator. The information is necessary to be able to use PROSOFT in a simple and straightforward
way. The information will also result in a correct documentation print-out of the full custom project.
Below you can find an overview of the information you need before you can proceed with the next
step.
4.1.1. The TELETASK central unit
You will have to define which central unit is going to be used in the project. As this is one of
the first items which is decided, you should easily find out which central unit is used for the
project. Please refer to the data sheets of the available central units.
4.1.2. The list of rooms
The 'list of rooms' contains an overview of all rooms in your project. Not only indoor rooms, but
also outdoor areas will be needed to be divided into 'rooms'. Rooms are best to be obtained
from the architectural drawings. The room names you use are important because the people
living in the house need to be able to understand them. A simple' bedroom' name will not be
sufficient as name if there are more bedrooms in the house. We recommend giving a more
detailed name. You can add the name of the person that will live in the bedroom to the word
'bedroom'. For example 'bedroom parents' or 'bedroom Maria' is better than 'bedroom 2'. Using
familiar names is better for a good communication with the occupants. It will save you time and
it increases the quality of the solution you are offering with TELETASK.
 PROSOFT makes no distinction between indoor and outdoor rooms.
4.1.3. The list of outputs
The 'list of outputs' gives an overview of all TELETASK output interfaces (for example relay
interfaces), with an overview of which output interface and contact is connected to which load.
This list is based on the electrical board information and is obtained from the electrical
contractor. This list may be, depending on the project, several pages long and is absolutely
needed before you can proceed. Please be sure that you have all information as listed below.
 Type of output: depending on the connected load and the desired control:
 Relay: used to switch on/off (for example a switchable light)
 Dimmer: used to dim (for example a dimmable light)
 Motor: used to control AC or DC motors (for example: opening/closing a curtain
of shutter).
 Fan interfaces: used to control fan (for example a ceiling fan or fan coil unit)
 Type of output interface: the specific type of interface (for example: ‘TDS13510’ for
a ‘Relay output’)
 Output number: for example Relay output nr. 1, or Dimmer nr. 10
 Extra Information:
 Room: This is the room where the connected load is installed (for example 'living
room'; to be chosen out of the 'rooms' list).
 Icon: describes which kind of load is connected: here you have the choice out of
a list: light, device (wall socket or other ON/OFF loads), motor or mood.
 Name: gives a more precise load description (for example work top, washing
table; reading light…)
More information about these items can be found in heading 'O-interfaces: outputs'.
17
TELETASK Handbook
PROSOFT >
Start of a Project
4.1.4. The list of inputs
The list of inputs contains all TELETASK input interfaces and the names (with location
indication) of the connected inputs such as window contacts, sensors, pushbuttons etc…
Having this full list (from the electrical contractor) is necessary before you can proceed. The
following information has to be available:
 Type of input: depending on kinds of signal, this input must be connected to a certain
type of input of the TELETASK system (only one of the different types below can
apply):
 General type of input: external (not in the MICROS+/PICOS central unit
housing) interface like for example a touch panel AURUS ref. TDS12021xx.
 Digital type of input: this is an input for all kind of voltage free contacts. For
example coming from a standard momentary push button, a window contact, a
motion detector contact or similar.
 Analogue type of input: this is an input for an analogue signal for example a
signal received from a TELETASK temperature sensor.
 AV type: for the integration of external AV systems
 Type of input interface used: this is the TELETASK interface type to which the
concerning input signal is to be connected. For example TDS12125 (Cookie with
feedback),
 Input number: for example digital input- or button number 1
 Extra information: custom note; for example 'push button in the kitchen next to the
stove'.
4.1.5. Information about the electrical contractor or system integrator.
To complete the report print-out, you need the name and the address of the electrical installer
or system integrator.
Add this information in PROSOFT menu 'Extra' - 'Options' - 'System Setup'
4.1.6. Information about the owner of the house
A project is always related to a house or building. You need the fill in the name and address of
the owners in the dedicated area in PROSOFT.
4.2. Starting a project
As soon as all project details are available, you can start configuring your TDS (TELETASK Domotics
System). This is by using the PROSOFT software.
4.2.1. Installing PROSOFT on a PC
PROSOFT Suite (V3.2 and higher) runs on Windows XP/Vista and Windows 7 / 8 (not RT).
You can find the installation package of the PROSOFT Suite on the CD-rom, included with a
DoIP Central unit or you can download it from www.teletask.eu from the 'Downloads' menu.
Remark: You may have to 'register' first before you can start downloading. Confirmation of
your registration might take 24 hours before you may be able to login and start downloading.
18
TELETASK Handbook
PROSOFT >
Start of a Project
4.2.2. Starting PROSOFT the first time





Click on the 'Start' button in the lower left corner on your screen.
Select 'Programs' in the start menu.
Select 'TELETASK' in the programs list.
Click on 'PROSOFT Vx.xx' in the TELETASK program list (x.xx stands for the
PROSOFT version).
PROSOFT starts now.
4.2.3. Select the central unit which will be used in your project
When PROSOFT has started, you will be asked if you want to start-up a new project or an
existing project for a specific central unit.
4.2.4. Saving project option on the PC
It is necessary to save the .NBT file on you PC. Don't forget to save it when working on it, not
only when you have finished it. TELETASK suggests to add a new file (version) number
(example: MyProject V01.nbt) each time and increase this number every time you've made
essential changes. This way you can easily go back to an older file version when the new
version contains a mistake. It is also a practical tool to make a difference between older and
newer back-up versions of the file. You can easily see which the old are and which the new
files are.
 Practical




Click on 'FILE' in the PROSOFT menu.
Click on 'SAVE' or 'SAVE AS' in the 'File' menu.
Give the project a name and add V01 (f.e. JAMES V01.NBT if you save this file
for the first time).
When you will save a new version, use regularly 'SAVE AS' and increase the
version number V01 to V02, V03,…. (f.e. JAMES V02.NBT,…)
 REMARKS
 Make regular backups of your .NBT file, save them on your CD-rom, DVD? USBstick,.. and keep them safely for future use.
 As soon as the project is finished, make a back-up of the latest version and
keep it safe (f.e. safe deposit box). The file can be very valuable because of all
the efforts which were made and possible private information such as entrance
code for the house, etc…
4.2.5. Project options (menu 'extra')
Click on 'OPTIONS' in the 'EXTRA' menu to fill in the project related details. The Option
window will appear on the screen.
In this window all the options are grouped in different tab pages. We will describe them here:
19
TELETASK Handbook
PROSOFT >
Start of a Project
 System setup
In the tab window System Setup you can fill in the global project details: the details of the
electrical installer and the details of the owner of the house/project.
Password protection can also be enabled.
20
TELETASK Handbook
PROSOFT >
Start of a Project
 Option
 'Language': here you can select the necessary language version you prefer for
PROSOFT Suite. You have to re-start the PROSOFT SUITE to activate changes. This
setting is no setting in the .NBT file but will be kept globally by the PROSOFT Suite.
 'Special':
 Relay delay: here you can determine which time has to be elapsed between the
switching of a relay (this to avoid problems with inrush current).
 Press Long bus interfaces: this determines how long you have to push on a
button before it will be recognized as 'Press Long'.
 Feedback LED's blink on error: if this option is checked the feedback led's of
the touch panels will start to blink when the function behind is in 'error' (f.e. when
an output interface could not be found on the AUTOBUS). This is very useful
during the start-up of the installation.

‘Service’:
 ‘Auto start function’: this function will always be executed when the central unit
is started (after sending from PROSOFT, after a voltage loss,) Thanks to this
function you can assure that some 'critical' functions always will be
executed/started (e.g. process functions).
 ‘No Action timer’: This time determines after which period the 'No-Action alarm'
will be executed. This timer can be put ON or OFF or RESET by the service
function.
 ‘No Action alarm’: Here you can define a function which has to be executed
after the 'No Action timer' has elapsed. A typical application is an emergency
alarm in service flats.
 Sensor
21
TELETASK Handbook
PROSOFT >
Start of a Project
 'Temperature settings':
 Heating system type’: Here you can set up the heating cycle (only applicable for
sensor zones with control method 'relay', 'flag' or 'local mood'). Standard there is
no cycle and hysteresis of 0.5C° used. In this case the heating is activated when
the temperature is 0.5C° lower than the demanded temperature and turned off
when the demanded temperature is reached. When you have activated a cycle,
the heating will be periodical ON. How long there will be heated depends on the
chosen cycle and the difference between the desired and measured temperature.
Via this method the temperature can be kept more optimal and the energy
consumption will be lower.
 'Cooling system type’: see 'Heating system type'
 Temperature zone ON if target is changed from Display interface: This option
determines whether a temperature zone will be switched on automatically when
the user changes the target temperature of that zone, using the UP / DOWN
buttons on a display interface. Display interfaces that support this are: AURUS-4
TEMP, AURUS-OLED (PLUS), AURUS-TFT, iSGUI, GUI+.
 Temperature / 10V or 100% time: this parameter is only applicable for a heating
system: with multistage control, analogue control and other methods of control
WITH regulated cycles. This parameter determines at which temperature
difference between the measured and the regulated temperature the
heating/cooling has to be controlled maximal. (high speed with multistage control,
10V for analogue control and 100% cycle for the others).
 Activate the 'AUTO' modus: when this parameter is checked, the system will
automatically be able to switch from heating to cooling or the other way around,
depending on the measured and regulated temperature. REMARK: if the 'AUTO'
mode is activated it is still possible to select the mode HEAT or COOL for every
zone, the system then will only heat or cool, it will never change the mode by
itself.
 Delta Hot/Cool: this is a temperature difference. If the measured temperature is
higher than the regulated temperature increased with Delta Hot/Cool, the system
22
TELETASK Handbook
PROSOFT >
Start of a Project
will go in AUTO mode and start cooling. The regulated temperature for cooling for
Day or Standby in a zone is the regulated temperature for heating in this zone
increased with Delta Hot/Cool.
 Freeze protection temperature: the temperature which has to be obtained
minimally, even when the zone is "OFF" or there is a window open in this zone, to
avoid frost damage.
 'Others':
 Hysteresis light sensor: the hysteresis which has to be used for a light sensor.
Because Lux values are a logarithmic scale this is not stipulated in absolute
values but in amount of steps.
 Hysteresis humidity sensor: the hysteresis for a humidity sensor
 RGB settings
Here you can define maximum of 10 basic colours for RGB functions as a kind of
general
colour pallet. These values can be used with the TDS12502 (remote control) via the
RGB button + ‘0 – 9’.
 Remark: an RGB zone needs to be defined for the touch panel that receives the
IR commands.
When you want to assign a colour to an RGB function in a Mood or from a button,
these colours will also show as the ‘Custom colours’. So once these colours are
defined to your wishes you can easily use them anywhere.
23
TELETASK Handbook
PROSOFT >
Start of a Project
 Time setting
 'Clock':
 Time zone: here you can define the time zone which has to be used by the
central unit. This time zone also contains information about the use (or not) of
summertime and when this starts and ends.
24
TELETASK Handbook
PROSOFT >
Start of a Project
 Adapt time automatically (via the Internet): this regulation is advised when you
have a continuous connection with the internet. This way your central unit clock
will be synchronised with the 'Time Servers' on the internet. This results in a very
accurate clock which always will be correct in the whole project (all touch panels
and screens).
 Synchronize de time of the central unit with the time of your PC: with this
regulation the clock of the central unit will be set even with the clock of your PC
when synchronising (each time when sending the .NBT file).
 'Workday': Select all the days in a week which are 'Workdays' for you. This is
important when the regime will be on 'Automatic'.
 E-MAIL
 ‘Report sender's name’: this name will be used as sender's name of an e-mail
whenever the central unit will send an e-mail.
 ‘Sender's e-mail address’: this address will be used as sender of an e-mail whenever
the central unit will send an e-mail. If the receiver of this e-mail replies at this
message, the message will be sent to this address.
 ‘SMTP Server (sent mails)’: the SMTP server address which has to be used for
sending the e-mails. This address is depending on the internet provider and can be
asked for at your internet provider.
 ‘SMTP port’: the port has to be used for the SMTP, normally this is port 25.
25
TELETASK Handbook
PROSOFT >
Start of a Project
 Local Settings
4.2.6. Cameras & Doors
If your project includes IP cameras or door phones you have to add them to PROSOFT to
integrate them into the TELETASK system. The cameras can be configured with or without
video-door-phone functionalities. It is also possible to add a door phone with speech only.
When integrating a video door phone system with multiple doors there are 2 possibilities:
 The video door phone system manages the different doors itself and there is only
1 outgoing video and phone connection. This type of video door phone system is
integrated as 1 IP camera. (This is typical for analogue video door phone systems
that are converted to IP using a TDS10119 and a video to IP convertor).
 The different outdoor units are accessible individually. When integrating this type
of video door phone system an IP camera is added in PROSOFT for each
outdoor unit.
 Analogue cameras can be converted to IP cameras by using additional hardware.
Check with your local camera supplier what is needed.
 Be sure that the selected IP camera supports Motion JPEG.
26
TELETASK Handbook
PROSOFT >
Start of a Project
 Practical



Click “Extra” in the main PROSOFT menu bar.
Click “IP Cameras”
Click the “Add” button to add a new camera
27
TELETASK Handbook
PROSOFT >
Start of a Project
 Parameters
IP Cam/Doors
 ‘Name’: Enter the name of the camera. For example ‘front door’ or ‘back garden’
 ‘Rooms’: Select in which rooms the camera is displayed on the target device (e.g. on
the AURUS-TFT).
 REMARK: by default a camera is available in all rooms
 ‘Video Doorphone settings’: Enter the camera features of the selected door. The
‘Video settings are optional, leave this part blank when integration a door phone or
intercom station that has no camera.
 ‘Camera URL’: Depending on the IP camera type this URL can contain the resolution
setting. See the remark of the resolution settings at the end of this chapter.
 ‘Motion JPEG mode’: Select the mode that this camera will use
28
TELETASK Handbook
PROSOFT >
Start of a Project
 Still Image: Use this mode when the Camera URL results in a still image in your
browser. The advantage of using ‘Still Image’ is the fast response for the first
image. Disadvantage is the lower frame rate
 Server Streaming: Use this mode when the Camera URL results in a video
stream in your browser. This mode takes somewhat longer (about 1s) to load the
first image but subsequent images are loaded at a higher framerate resulting in
more natural video.
 REMARK: The framerate of the video is depending on the camera settings
(framerate can be limited in most camera), the network (on the LAN a higher
framerate will be possible than when viewing the camera remotely), and the
device displaying the video (a PC running GUI+ will process video faster than an
AURUS-TFT).
 ‘Authentication’: Enter a user name and password to login to the camera (optional)
 REMARK: Authentication is not recommended for ‘Still Image’.
 ‘Test video’: Click this button to test the video settings
 REMARK: The ‘Test video’ will display the video in its original resolution. The
video may be scaled or clipped on the actual device (e.g AURUS-TFT, GUI+,
iSGUI).
 REMARK: Not all video options are available on all uses interfaces (see table
below)
Still Image
Server Streaming
Authentication
GUI+ (TDS15105)
V
V
V
iSGUI v2.5 (TDS15101)
V
V
V
AURUS-TFT (TDS12064)
V
V
V
iSGUI v1 (old)
V
X
X
GUI (old)
V
X
X
 ‘VoIP Settings’: These settings are used by GUI+ only. These settings are optional
 ‘VoIP Call ID’: Enter the Call ID of the (video) door phone or intercom station. The call
ID will be used by GUI+ to identify the caller.
 ‘DTMF accept call’: Optional. Some door phone systems require a DTMF code to
start the conversation. Enter this code here. This code is sent when an incoming call is
accepted by the user.
 ‘DTMF end call’: Optional. Some door phone systems require a DTMF code to end a
conversation, enter this code here. This code is sent when an call is terminated by the
user.
 ‘Door opener settings’: These settings are used by GUI+ and AURUS-TFT to open a
door. These settings are optional (e.g. when there is only an iSGUI or when this IP
camera is associated with an intercom station).
 ‘TELETASK function’: Select a function here that will open the door associated with
this IP camera. When integrating a single door or a video door phone system where
the individual doors are accessible, this function can be the electric door opener itself.
When integrating a video door phone system that manages the doors itself this can be
a relay connected to an input of the door phone system. This function can also be
used for other actions as well (e.g. a local mood that not only opens the gate but also
switches on the driveway lights).
 ‘DTMF door code’: (only to be used when a door phone system is connected to a
GUI+) Enter here the number(s) of the DTMF code(s) which are to be generated to
29
TELETASK Handbook
PROSOFT >
Start of a Project
open the door via the (video) door phone system. The DTMF code(s) is/are defined by
the brand and the type of door phone system. Ask the supplier of this system which
code(s) are to be generated to open the door. In most of the cases this is one or two
digits. Example: ‘*001’.
 REMARK: The TELETASK function and the DTMF door code can be used
together (e.g. the DTMF door code for the door and the TELETASK Function for
the driveway lights).
 REMARK: DTMF codes do not work across all VoIP system, so if possible use
the TELETASK function.
 All the IP Cameras added in PROSOFT will be available in the ‘Phone book’ on GUI+, so
for intercom functionality also add the intercom stations here (without camera).
 Be aware of the camera resolution. When you add a camera to display it on a AURUSTFT (TDS12064), select it to be as close as possible to the AURUS-TFT resolution of
480x272 (for example 480x320). The frame rate will drop with higher resolutions. See for
your IP camera configuration settings if you can select different resolutions.
 When the same camera is used for the AURUS-TFT (TDS12064) and for example also for
the MAIOR-19 (TDS12053), it is recommended to add the camera two times with
different resolution settings (URL address) matching the resolution of the target device
(e.g. 480x320 for the AURUS-TFT and 640x480 for the MAIOR). Depending on you IP
camera configuration possibilities, this can be displayed as a different URL address.
 IMPORTANT: When adding a camera with different resolution keep in mind that most
cameras only support encoding to 1 resolution at a time for each mode. So for example
add the low resolution as ‘Still Image’ for AURUS-TFT and the high resolution as
‘Server streaming for GUI+ and iSGUI.
30
TELETASK Handbook
PROSOFT >
Start of a Project
4.3. TELETASK CLOUD installation
4.3.1. Introduction
In this manual you can learn how to setup a connection to control your home/building from a
mobile device.
Therefore you need to:
 connect your TELETASK system to the TELETASK cloud service
 connect your mobile device (with ‘iSGUI’ app) to the TELETASK cloud service
Once these two connections are made, the mobile device will be able to talk with your
house/building via the TELETASK cloud service.
Requirements:
 PROSOFT 3.6.0.0 or higher.
 Remark: during this setup your PROSOFT PC needs to be connected both to the central
unit and to the internet.
The procedure to connect a central unit to the TELETASK cloud is divided into five different
steps:
1. Create a system integrator (SI) account on the TELETASK cloud server (with a
browser).
2. Create additional cloud users in PROSOFT and transmit the newly obtained
PROSOFT .nbt file to the central unit.
3. Activate a TELETASK cloud account(s) on the mobile device(s).
4. Create and configure the users
5. Use the iSGUI app on the mobile device(s).
4.3.2. Create a SI (System Integrator) account first
A system integrator account is the same as a standard user account, but when a TELETASK
installation is first connected to the TELETASK Cloud, the initial account automatically
becomes the system integrator account for that installation (required for every installation).
To create the SI account, go to cloud.teletask.be and click ‘create account’.
Or use the link provided by PROSOFT (see chapter Connect the central unit to the TELETASK
cloud) to go directly to the ‘create account’ page.
Enter the required information (name, e-mail, country and password) of the system integrator,
and click ‘create account’. The Si will receive an e-mail immediately. It contains a confirmation
link. Click on the link to activate the account.
 Remark: if the email is not found, it may be arrived in another mailbox (spam, clutter or
other…).
4.3.3. Connect the central unit to the TELETASK cloud service
This step is done in PROSOFT and requires a connection with the central unit and the internet.
To connect the central unit to the cloud:
 In PROSOFT, select ‘Communication’, ‘Cloud’
 The ‘Login to TELETASK cloud’ window appears.
 Enter your email address and password (created in the previous step, or if you have
not yet created an account, click create account).
31
TELETASK Handbook
PROSOFT >
Start of a Project
 Remark: you can optionally save your “user name” and “password” on the PC so that
you don’t need to enter them again for other installations (= other central units of other
customers) which you want to add to the TELETASK cloud service.
When the login is successful, the “Define installation” window appears
 Enter a name for the installation (customer name or for example ‘Home’, ‘Office’,
‘Cabinet’, ‘Shop’... We strongly recommend not to use the site address or building
name for security reasons). This name will appear on your iSGUI app screen.
 Click ‘Connect installation to cloud’
The installation is now added to the Cloud. If you visit cloud.teletask.be and log in with your SI
account, you will be able to see your new installation.
4.3.4. Create and configure the users
The next step is to configure the users. These are the persons who want to use the iSGUI app
on their device(s) and the persons who need to do the management of the rights of the users.
Most of the time it the owner who have all the rights and he/she is a user as well.
Configuring the (cloud) users is done in PROSOFT. To do this click the menu “Extra” and
“Users and settings”, the define users window appears.
User properties:
 “Name”: A user name (required; f.i. ‘Matheo’, ‘Sarah’…)
 “Email address”: the user’s email address (required if the user wants to use the
iSGUI app)
32
TELETASK Handbook
PROSOFT >
Start of a Project
 “Cloud access”: Can be ‘No access’, ‘Owner’ or ‘User’. Can only be set if an email
address has been assigned to the user. The different settings are explained in the
next paragraph.
 “Proximity tag”, “Proximity card”, “PORTA” and “Group”: are settings specific for
CARDSOFT, see the CARDSOFT chapter for more info
4.3.5. Cloud access
The TELETASK cloud defines 4 types of users: “System integrator”, “Owners”, “Users”, and
“None”.
 “System integrator”: The system integrator is the account which was used to initially
connect the installation to the cloud. The system integrator has access by default, but
an owner can switch this off. When switched off, the system integrator can’t use iSGUI
or edit users via the TELETASK Cloud website.
 Remark: The system integrator is obliged to give notice to the owners if he has
full right to manage the rights and the use of iSGUI (it is like having a spare key
of the main door). We recommend to make a written notice via e-mail and keep a
confirmation of agreement of the owner. We don’t recommend to do so to avoid
unwanted responsibilities to the system integrator. At the other hand, it is an
interesting feature to give maximum service to the owner(s).
 “Owner”: a type of user that has iSGUI access and who can change settings of other
users in the TELETASK Cloud.
 “User”: regular users who has iSGUI access but can’t change settings (like adding or
deleting another user or change his own or somebody else’s iSGUI rights).
 “None”: users without TELETASK Cloud access.
 Remark: the owner can change the status of any user at any time by simple login to the
cloud service (no need to use PROSOFT). This feature can for example be used to
activate (=’User’) or block (=’None’) the access to the iSGUI app for temporary
employees, external technical staff, lock-out of the system integrator when no services
are wanted, etc…
33
TELETASK Handbook
PROSOFT >
Start of a Project
4.3.6. Transmit the PROSOFT file to the central unit(s)
Once the previous steps are done, the PROSOFT- .nbt file is ready to be transmitted to your
central unit(s).
 This can be done in the usual way (for more details see ‘Technical Handbook’ in the
PROSOFT help menu). The central units will be notified that they should connect to the
TELETASK Cloud as soon as a network becomes available to them. If PROSOFT is
‘running’, you can track the connection status of each central unit in the bottom panels
in the PROSOFT screen.
4.3.7. Camera’s on iSGUI without Dynamic DNS or fixed IP- address
IP cameras do not connect to the TELETASK cloud directly. They still require port forwarding,
but the TELETASK cloud will make sure that a connection from the iSGUI application can be
made to the router on which the port forwarding is configured. So a VPN, Dynamic DNS
account or a fixed IP address from your ISP are no longer required.
There are many manufactures of IP-routers, so for information on how to setup port forwarding
on your device, please contact your network specialist.
When the port forwarding is set up, the only thing that you need to do is to add the ‘public port’
used for the port forwarding to each camera in PROSOFT.
34
TELETASK Handbook
PROSOFT >
Start of a Project
 Remark: For security it is important to use a password on camera’s that are used with
the TELETASK cloud.
 Remark: Normally the public port number will be different for every camera, unless
multiple camera’s are accessed through an intermediate device (e.g. a multi channel
analog to IP convertor or a DVR).
 Remark: The ‘test video’ functionality in PROSOFT only tests the ‘local operation’ of the
camera, not the remote access.
4.3.8. Network specifications (used ports)
Although the TELETASK cloud is designed to work with most networks, some networks
(offices, hotels,…) may block the ports used by the TELETASK cloud system. The ports used
differ between the central unit and a device (e.g. smartphone) that connects to the central unit.
 Central unit: outgoing traffic on ports 9000 and 9443 must be allowed on the network
on which the central unit is connected.
 iSGUI: outgoing traffic on ports 5671 and 8443 must be allowed on the WiFi network
to which the device is connected. If the device is connected on 4G (or another mobile
communication standard), these ports should be open by default.
The TELETASK cloud does not require VPN or port forwarding (with the exception of
cameras). The TELETASK cloud does not require a static IP or dyndns service (not even for
the cameras).
35
TELETASK Handbook
PROSOFT >
Start of a Project
4.4. Use of passwords and codes
4.4.1. User code
On certain graphical interfaces (like on the iSGUI and AURUS-TFT) it is possible to protect
specific items with a code. For the iSGUI it’s also possible to have a user code protection
during startup (see iSGUI properties in GUISOFT).
This code can only be changed inside PROSOFT and is the same for all AURUS-TFT’,
iSGUI’s, … except for the SERVUS and ILLUS. These last 2 interfaces store their ‘own’ user
code and can be changed and saved on the interface.
The user code is default 12345 and can only contain numbers (4 to 10 digits).

For configuration go to: Extra > User code
 Remark: This password configuration is not shared with the SERVUS. The SERVUS
user code can be changed any time by the user in the configuration menu of the
SERVUS.
4.4.2. PROSOFT password
The DoIP central as well as the .NBT file, can be protected with a password if desired. By
doing this you can prevent unauthorised access.
The password will be asked every single time you open a protected .NBT file or connect with a
protected DoIP central.
After the password has been set, it can only be changed or removed from inside PROSOFT
after giving the current password.
The password is alphanumeric (like a typical PC password).
36
TELETASK Handbook

PROSOFT >
Start of a Project
For configuration go to: Extra > Options > System setup
 ‘Security’: Check “Protect NBT file and central unit with password” if you wish to
prevent unauthorized access to the .NBT file. When the .NBT file is password
protected, it will be:
 impossible to open the NBT file without the correct password
 impossible to make a connection with the password protected central unit without
the correct password. This means that sending a new file, receiving the existing
file or using Diagnostics, will be impossible.
 Every time you change these settings, you will be asked to save the .NBT file.
 If you send a password protected .NBT file to a non-password protected central
unit, or if you send a non-password protected .NBT file to a password protected
central unit, both will get password protected.
 If the password of the .NBT file gets lost, the only solution will be to reset the
central unit back to factory settings and start a new .NBT file. See also the
remark below.
 IMPORTANT REMARK: By default the “Remove password on ‘Back to factory
settings’ ” is enabled. If you wish to keep the password when the central unit is
reset by pressing the SW1 and SW2 button, uncheck this mark. Be aware that if
you forget the password, you will not be able to create a new .NBT file. It can
only be reset by sending the central unit to TELETASK for repair!
4.4.3. Technical code
The technical code will give you access to certain configurations like AUTOBUS address, IP
address, … on some interfaces like the AURUS-TFT, SERVUS, etc. …
Ex.: with interfaces without rotary switches, you have to set the AUTOBUS address in the
configuration screen after giving the correct technical code.
This is always 09876 and it is impossible to change.
37
TELETASK Handbook
PROSOFT >
Rooms
5. The rooms
5.1. Introduction
Every home is divided in several rooms: the kitchen, living room, the office room, the bathroom(s), the
different sleeping rooms, the garden, etc… Because this is a clear and logical approach for every
home, PROSOFT also approaches your home by using the different rooms.

The defined rooms are also very important for the automatic generation program of some of
the menu operated TELETASK user interfaces (mobile phone iSGUI interface). It is very
important to insert the rooms correctly!
5.2. Overview of the rooms
5.2.1. List of rooms
In the list of rooms you have an overview of all available rooms. Every room is substituted of
the following information:
 'Code': Every room automatically gets a code which is used by the system. This code
is not changeable and is made out of:
 'RM': this is the abbreviation of 'Room'
 'Number': every room gets a number for internal system use. It starts with 01 and
is incremented (+1) every time you enter an additional room.
 'Name': contains the room name as entered in PROSOFT by the user.
When you want to change an existing room name, select the room in the list of rooms. It will
turn blue. Then double click on it or click the 'edit' button. Now you are able to change the
different parameters.
 Possible actions in the list of rooms menu
 'New': Click the 'New' button to add a room.
 'Edit': Click the 'Edit' button to edit the parameters of a room
 'Delete': Click the 'Delete' button to delete a room from the list of rooms.
38
TELETASK Handbook
PROSOFT >
Rooms
 In practice



Click 'Edit' in the PROSOFT menu bar.
Click 'Rooms'.
The 'list of rooms' window appears on the screen
5.3. Adding rooms to the list of rooms
5.3.1. The different parameters for every room
 'Name': Enter the name of the room (short and easy to understand and to locate).
 'Audio Zone': If you have an audio system integrated with your TELETASK system,
you will have to connect the room to a specific audio zone (amplifier).
 You will have to select this audio zone later, after the audio interface and the
audio zones on this interface have been defined. Please refer for more
information in the 'Audio Interfaces' chapter, but we recommend not doing this
right now.
 'Sensor Zone': If you are using TELETASK temperature sensors for heating and/or
cooling control (recommended), select the applying sensor zones with which the room
is to be related.
 The sensor zones are entered when the sensors are entered in PROSOFT. So
please also come back here later, as soon as the sensors for your project are
entered. For more information refer to the 'Analogue Input Interfaces' chapter.
 In practice






Click 'Edit' in the PROSOFT menu bar.
Click 'Rooms'.
The 'List of Rooms' window appears on the screen. In this screen the standard
rooms are reproduced.
Click the 'NEW' button to add a room to your project.
The 'Define Room' window appears on your screen. Set up the different
parameters for this room.
Click 'OK': now a room is added to your TELETASK domotics project. The
window 'Define Room' will disappear.
In the 'List of Rooms' which is visible again, the added room is displayed.
39
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
6. 'O' Units: Outputs
6.1. General notes
6.1.1. Output
An output connects one electrical load or circuit with the TELETASK system. Thanks to this
connection, you can control this load out of the domotics system. There are different groups of
outputs.
 'Relay': this output switches a load between the 'ON' (relay contact is closed) and the
OFF (relay contact is open) status.
 'Dimmer': this output varies an analogue output signal from 0 to 10Volt. This signal is
mostly used to control a power dimmer. 0V output means the dimmer is at 0% (load is
off). 10V on the output means the dimmer is at 100% (the load is ON). This means
that a light or group of lights connected to the power dimmer are OFF or ON or
dimmed somewhere between 0 and 100%.
Instead of 0-10V, this may also be 1-10V, 0-100% (for example when using a DMX
output interface).
 'Motor': this output controls a motor rotating left or right during a limited number of
seconds. The motor can also be stopped at any time. So this output can be set in the
LEFT/ RIGHT or STOP status. LEFT/RIGHT can also be considered as UP/DOWN,
depending on the connected motor (in most of the cases this is for control of electrical
motorised curtains, sun blinds and shutters).
 ‘Fan’: This output controls multi speed ventilator.
6.1.2. Output unit
Outputs with the same functionality and the same technical specifications are grouped per type
of output unit. The output units can be divided in two different breakdowns:
 Based on their function (relays, dimmers, motors)
 Based on the system relation (integrated in the MICROS+/PICOS central unit,
external but plug-in on the MICROS(+ upgrade version)/PICOS central unit and
externally connected via the AUTOBUS).
 System related classification
The output units can also be grouped depending on the way they are connected with
the TELETASK central unit. There are two system related categories:
 'Standard Output units': these output units are integrated in the central unit (only in
case of MICROS+/PICOS central units.
 'AUTOBUS Output units': these types of output units are all output interfaces with an
AUTOBUS connection. For example TDS13510, TDS13524, TDS13525,
TDS13609…).
 Remark: All AUTOBUS in- and output units are in general also called in- and
output 'interfaces'.
6.1.3. Output numbers
When an output interface is added to the project, all available outputs will automatically get an
output number. Once an output has been given an output number, this number cannot be
changed any more during the project, even if the address of an output interface (for addressing
see later in this text) would change during the project.
The numbering starts for the different groups (relays, dimmers, motors and fans) with number
'1'. Depending on the kind of output, PROSOFT will add an abbreviation in front of the number
e.g.: 'REL' for relay, 'DIM' for a dimmer, 'MOT' for a motor output and ‘FAN’ for a fan output.
40
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
When there are several central units connected, a letter which indicates to which central unit
the output is connected, will be added. (from A to J, because up to 10 central units can be
coupled to each other over IP).
6.1.4. 'O' Address (Output Address)
For all interfaces connected to the AUTOBUS, so also for the output interfaces on AUTOBUS,
it is necessary the system is able to distinguish the different interfaces from each other.
Therefore every AUTOBUS interface has a hardware address setting.
The address numbering starts at '00'. This address is reserved for the central unit.
So in a practical situation, the address setting will always start with a higher number. This is
also because the central unit has other predefined address settings for its internal (general)
outputs. The number of predefined (reserved for the system) addresses, depends on the type
of central unit you use and they will be reserved automatically in PROSOFT.
PROSOFT automatically assigns an address to every new defined output unit. You will have to
set the same address on the hardware interface (connected on AUTOBUS) as the address
given in PROSOFT. If the hardware AUTOBUS address of an interface has been set to a
certain address already, you can change the address in PROSOFT.
Additionally, PROSOFT assigns for internal use an 'O' letter to the address. This way it is
clearly noted that this concerns an Output address on an Output interface. This is necessary
because there are also AUTOBUS Input addresses. These 'I' addresses are independent of
the 'O' addresses. This means that 'O16' and 'I16' can exist on the same AUTOBUS. Within
the 'O' and 'I' addresses each address setting must be unique. So there can't be two 'O16'
addresses because the system cannot distinguish these two from each other and the system
will not behave properly in this case. Hardware damage will not occur due to double
addressing, but outputs behave unpredictable. Refer to the 'I interfaces' chapter for more
information on 'I' addressing.
The number of addresses available on the AUTOBUS is limited. The highest settable output
address ('O' address) is defined by the limits of the concerning central unit you use. Please
refer to the data sheet of your central unit for system limits.
 IMPORTANT REMARK: Using double addresses is not allowed and can generated
danger and non-secure situations. So always check very carefully before powering your
system if no double addressing occurs.
41
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
6.2. Adding Output units
When you start-up a new TELETASK project, you will have to choose for a certain central unit. By
selecting the central unit, PROSOFT automatically generates all standard available internal Output
Units of the central unit. When you need more output units than the ones available in the central unit
(MICROS+/PICOS), you will have to add extra output units. The AUTOBUS output interfaces have to
be added in PROSOFT by the user. When adding output units, there are two parameters to be set:
 'Name': enter in this field a short and understandable name for the output. In
most of the cases you can just leave the name as it is given by PROSOFT. If you
have more than one electrical cabinet at different locations in your project, we
recommend to add to the output numbers (for example '25-32') the name of the
floor of the electrical cabinet wherein the output unit is installed.
 'Address': This setting is done automatically by PROSOFT, but you can always
change the address if the concerned interface was already given another
(available) hardware address setting.
Tip: It is always easier and faster to change the address setting of an interface in
PROSOFT than changing it somewhere in an electrical cabinet or on a wall
mounted panel.
6.2.1. In practice










Click 'Edit' in the PROSOFT menu bar.
Click 'Outputs'
.
The 'List of Outputs' window appears on the screen. In this screen the standard
(internal) available output units are already there because they are automatically
predefined by PROSOFT.
Click the 'New' button to add an extra output unit.
The ‘Select interface’ window appears. The interfaces are grouped by their
function on this screen.
Select the correct interface and click OK
The 'Define Output' window appears on the screen. Enter the different
parameters for this interface.
Click 'OK': an additional Output unit is added to your TELETASK domotics
project. The 'Define Output' window closes.
In the 'List of Outputs' window, which appears again, the output unit is added.
Repeat this way of working for all TELETASK output units which are to be added
to your project.
42
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
6.3. Assigning TELETASK Outputs.
An important step to fluently parameterise your project is the assignment of a name for all individual
outputs (relays, dimmers, motors). In a later stage it will be a continuous job to use these assigned
names when defining relations and functions. The assigned name of an individual output will always
refer to the connected load or circuit.
For example: 'main light' (in the kitchen), 'wall sockets' (in the home office) or 'left curtain' (in the living
room).
6.3.1. The different available parameters:
In the 'Define Output' window of the concerned Output unit of which the output that has to be
assigned is part of, you can enter the name of all individual outputs. The name exists out of
three parameters which are to be defined:
 'Room': Select the room where the load is installed.
 If the room is not in the list of rooms yet, you can directly enter a new room via
the 'New' button.
 If you have to change the characteristics of an existing room, you can use the
'Edit' button.
 'Icon': This is a way of grouping outputs on graphical TELETASK interfaces like the
AURUS-TFT and iSGUI. The different available icons are:
 'Not visible': the output will not be visualized on graphical interfaces. This is to
be used for all technical outputs which are not to be controlled by the user. For
example: A water valve which is mostly controlled by timers and by the access
control functions.
 ‘Device': Select this option for outputs which are controlling wall sockets (all
general non dedicated wall sockets, cooker hood; micro wave, fans, coffee
machine, …) and other general on/off devices which are to be controllable by the
occupants of the project, like there are garden sprinklers, etc...
 'Light': Select this option if the concerned output is controlling a light or a group
of lights.
 'Heat/cool)': Assigning this icon to an output will not cause it to be displayed on a
Touch screen. It is only meant to sort outputs more easily by Icon
43
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
 ‘Motor’: Select this option for motors. This will be displayed on touchscreens.
 ‘Mood’: Select this option for moods. This will be displayed on touchscreens.
 'Motor (Power)': Only for relays that will be used in a ‘motor function’. Assigning
this icon to an output will not cause it to be displayed on a Touch screen. It is only
meant to sort outputs more easily by Icon.
 'Motor (Direction)': see motor power
 ‘Control': Only for flags, use this icon to display a flag as a read only item on a
Touchscreen in the motor Icon.
 Remark: TELETASK touch screens also define other Icons like
‘Thermostat’, ‘Audio’ and ‘Sensor’. Items like a Temperature sensor or an
Audio zone are automatically added to the correct icon if they are assigned
to a room.
 'Name': Enter a short name of the load/circuit which is connected to this individual
output. Remember that this name will appear on the graphical interfaces (if there are
any in your project) and there is a limited room on the screens to display this name.
So keep the name length as short as possible.
Examples:
 'light in the parents’ bedroom' is not a good name, because the room
identification is already done in the 'room' section, so it would be better to use
'main light' or 'main', because the user also already knows that it concerns a 'light'
because it has been assigned to this function.
 'Ambient light', 'left sockets', 'sprinklers left', 'staircase to cellar' are good names.
'Colour lights on staircase to first floor' is not good, because it is too long to be
displayed. 'Staircase light' would be better.
6.3.2. In practice:







Click 'Edit' in the PROSOFT menu bar.
Click 'Outputs' in the 'Edit' pull down menu
Select the desired Output unit by clicking on it. The selected output unit turns
blue.
Click the 'Edit' button. The 'Define Output' window appears.
Click on the picture of the interface the desired individual output. The selected
output turns yellow.
Select/enter in the 'Output name' field one by one the 'Room' of the load, the
related 'Icon' and enter the name you want to be displayed.
Click 'OK', the selected individual output is ready for later use.
44
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
6.4. Overview of the available TELETASK Output units and their
parameters
TDS ref
Functional
Address
Options
Relay contact
With rotary
switch
Power*
Dimmer control output
0-10V
With rotary
switch
Power*
Minimum
dim level
With rotary
switch
Power*
TDS13510
TDS13502
TDS13512
TDS13609
Dimmer 1-10V /
TDS13610
Dimmer 0-10V + relay
contact
TDS13620
Dimmer DALI / DSI / DMX
With rotary
switch
Power*
AC motor
With rotary
switch
See chapter
on motors
TDS13525
DC motor
With rotary
switch
See chapter
on motors
TDS13522
Fan speed control
With rotary
switch
Power*
TDS13530
Fan coil unit control (HVAC)
With rotary
switch
TDS13524
TDS13526
Speeds**
See chapter
on
TDS13530
 * Power: Information field. Can be entered for light bulbs so the information is printed
on the printed documents and can be used by occupants as lamp replacement
information. Values between 0 and 30000 can be entered in this field.
 ** Speeds: See 'Functions'- ‘Fans’
45
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
6.5. List of output units of your project.
6.5.1. Generating Lists on the screen of your PC
An overview of all output units and their individual output can be made in several sort modes.
You can find the lists in the 'list of outputs' window.
There are four different list types for searching individual outputs.
 List type ''O' Interfaces':
Content of the list:




The TELETASK output units can be reviewed in the 'list of outputs' list. The following
items are contained in this list:
‘Output’: the 'O' reminds you that this line is concerning an Output unit.
‘Address’: This is the software address of the concerning output unit.
‘Abbreviation’: for internal use by the system.
‘Description’: this is the name which you or the system gave to the output unit.
The available control buttons:
46
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
When you have selected the desired output unit (line turns blue), you have the
possibility to select one of the following actions:
 'New': to add an extra output unit.
 'Edit': to edit the parameters of an existing output unit.
 'Remove': to remove an existing output unit and all its parameters.
 Types of list: 'Relay List', 'Dimmer List', 'Motor list', ‘Ceiling fan list’, ‘Fan
coil unit list’
List information:
 ‘Functional Group’: indicates to which functional group the output belongs
 'REL': a relay (classified in the 'Relay list')
 'DIM': a dimmer (classified in the 'Dimmer list')
 'MOT': a motor (classified in the 'Motor list')
 ‘FAN’: a fan (classified in the 'Ceiling fan list')
 ‘FCU’: a fan coil unit (classified in the ‘fan coil unit list’
 'Output Number': contains the output number which was automatically given by
PROSOFT
 'Room': is the room to which the individual output is connected.
 'Icon': the icon to which the individual output is connected.
 'Name': the name of the individual output.
Actions
When you have located the desired individual output, you can select it by simply
clicking on it (turns blue). The following actions can be done from here:
 'New': The ‘select interface window’ will be shown.
 'Edit': click 'edit' to open the 'define output' window. You can now edit the parameters
of the selected individual output.
 'Test Online': when your computer is connected to an operational central unit, you
can control the selected output via this button (for relays, dimmers and motors). At the
same time the actual status of the output is displayed.
47
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
 Remark: While ‘Test online’ is useful to test a specific output, the advised
method is to use Diagnostics (see the chapter ‘Diagnostics’).
 Sorting of lists:
Possible list sorting
The list types of relays, dimmers and motors can be sorted as follows:
 'Sort by number': Sorted on output number (numerical order). This is the default
setting.
 'Sort by room, icon and name': All outputs are now sorted by room and secondarily
by icon and then by name (all in alphabetical order)
 'Sort by icon, room and name': All outputs are now sorted by icon and secondarily
by room and then by name (all in alphabetical order)
 'Sort by name': All outputs are now sorted by name.
In practice:




Click 'Extra' > 'Options' in the PROSOFT menu bar
Click the 'Local Settings' tab.
Select in 'Sort list by' the desired sorting mode.
Click 'close' and the sorting mode is active. You can see the outputs sorted in the
new mode now if you go to the list of outputs.
 Tip: You can also change the sorting method by using the ‘Alt-S’ keyboard
shortcut.

Remark: You can also sort the list on the list page by clicking the header of the
appropriate column.
48
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
6.6. TDS13530 Fan coil unit interface
6.6.1. General
A fan coil unit (FCU) is a simple device consisting of a heating/cooling coil and a fan. It’s part
of an HVAC system found in residential, commercial and industrial buildings. Heat is
transported from a central heater/chiller to the individual FCU’s using water (like with traditional
radiators).
Due to their simplicity, fan coil units are more economical to install than HVAC systems with air
handling units.
Typically an FCU is installed in every room (comparable to the indoor units in a VRV system).
An FCU doesn’t measure temperature, so a TELETASK temperature sensor needs to be used
e.g. from AURUS touch panel or a TDS12250 TELETASK temperature sensor.
FCU’s can be divided into two types:
 4-pipe systems: Systems where there are different pipes for hot and cold water.
This means that it’s possible to heat in one particular room and to cool in another
at the same time. 4-pipe systems are mainly used in larger buildings (industrial,
hotels, hospitals,…).
 2-pipe systems: Systems with only one set of pipes for hot or cold water. This
means that the entire system is either in heating or in cooling mode. It’s
impossible to heat in one room and cool in another at the same time. 2-pipe
systems are mainly used in smaller installations (private houses) or climates
where only cooling (or only heating) is necessary.
6.6.2. Configuring a Fan coil unit interface
To add a Fan coil unit interface to your TELETASK system, follow these steps:
 In PROSOFT Suite, go to the menu "Edit", "Outputs"
 Chose "New"
 Select "TDS13530 Fan coil unit interface" from the list of interfaces
 Enter a Name for the fan coil unit interface
 Enter the AUTOBUS address for the interface
 Enter a Name for the fan coil unit.
 System type: select ‘4 pipe system’ or ‘2 pipe system’.
 HVAC operation modes: Select the applicable modes for this FCU
 HVAC fan speed settings: Select the correct speed settings.
 Fan ON delay (heating): sets the delay between opening the heating valve and
activating the fan. Use this setting to avoid that unheated (cool) air is ventilated in
the room. This setting only applies in heating mode
 Fan OFF delay (cooling): Set the delay between closing the cooling valve and
deactivating the fan. Use this setting to avoid freezing of the coil.
 When this setting is set to 0s, it can damage the fan coil unit! Contact the
FCU supplier for the appropriate value for this setting.
49
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
To configure and link a temperature sensor in PROSOFT with a fan coil unit, select ‘Fan coil
unit’ as control method for the sensor and select the corresponding ‘Fan coil unit’.
If the selected fan coil unit has both ‘Heat’ and ‘Cool’ modes enabled, PROSOFT will
automatically select that fan coil unit for the heating and for the cooling output of that sensor.
50
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
6.7. TDS13609: Dimmer interface 8x 0-10V
6.7.1. Introduction
The TDS13609 Dimmer interface is an output interface that can be used to control eight 0-10V
dimmable power dimmers (or 0-10V LED drivers)
For some lights, dimming only works between a minimum voltage (e.g. 2.5V) and 10V. On the
TDS13609 you can therefore specify a ‘Minimum DIM level’ on each output individually. The
Minimum DIM level can be set from 0 to 4V.
E.g. if the ’Minimum DIM level’ is set to2.5V, the voltage on the output of the TDS13609 will be
2.5V for 1% dimming.
6.8. TDS13610: Fluorescent Dimmer Interface
6.8.1. Introduction
The Fluorescent Dimmer interface is an output interface that can be used as:
 Fluorescent Dimmer (1-10V)
 Dimmer (0-10V) and Relay (10A)
 Remark: This option assigned to a group of four outputs. The first till fourth are one
group and the fifth till the eighth are a second group.
51
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
 Remark: PROSOFT will automatically add an additional interface with the relays of the
TDS13610. For the dimmers that are defined as 0-10V, the relay is available for other
uses. E.g.: switching a light.
6.9. TDS13620: DALI / DSI / DMX interface
6.9.1. Introduction
The DALI / DSI / DMX interface is an output interface that can be used in DALI or DSI or DMX
mode.
Depending on the mode you can configure up to 64 dimmers to this interface.
52
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
6.9.2. DSI mode
DSI is a protocol with one master (the TDS13620) and up to 100 slaves (the ballasts). There is
no addressing for the individual ballasts and all ballasts are always on the same dimming level.
So DSI is very well suited for large rooms, where a lot of lights need to be in the same state.
For the TELETASK system you can add only 1 Dimmer (but 100 ballasts) per TDS13620.
53
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
6.9.3. DMX mode
DMX is a protocol with one master (the TDS13620) and up to 512 channels (e.g the
multicolour LED-strips). Each device on the DMX bus gets one or more addresses from 1 to
255 (for an RGB light this are 3 addresses, 1 for RED, 1 for GREEN and 1 for BLUE). The
TDS13620 supports 64 slaves in the DMX address range 1-255.
If you add multiple dimmers you can select the dimmer to edit in the list on the left (‘1’). The
properties of this dimmer are then shown on the right (‘2’).
2
2
1
1
6.9.4. DALI mode
DALI is a protocol with one master (the TDS13620) and up to 64 ballast. Each ballast has an
address from 0 to 63. The advantage of DALI is that the ballast can send error information to
the master e.g. Lamp defect, Power failure,…. This information is available from Diagnostics.
The ballasts can be addressed (see chapter DALISOFT) individually (as a single ballast) but
DALI also supports up to 16 ‘Ballast groups’. A ballast group is a group of dimmers that you
want to control simultaneously. For the TELETASK system a ‘ballast group’ is a dimmer like
any other. A ballast that is assigned to a ‘ballast group’ can’t be addressed individually by the
TDS13620.
For Dali ballasts, the TDS13620 will read the minimum dim level from the ballast, and
recalculate dimmer values (e.g. 50%) as for the TDS13609. The minimum dim level in the
TDS13620 is supported from version V018.
There are 500 outputs available on a DoIP central unit, if you have 64 ballasts which you want
to control individually this are 64 outputs, if you control these 64 ballasts as 1 DALI group this
is only 1 output for the TELETASK system.
There are some similarities between a DALI ‘ballast group’ and a TELETASK ‘local mood’:
They both set a group of outputs. But there are also some differences which will determine in
which case a ‘ballast group’ will be used and in which case a ‘local mood’ is more appropriate.
54
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
 You can add a dimmer to different ‘local moods’ but a DALI ballast can only be
assigned to 1 group.
 A DALI ballast group can be dimmed simultaneously, a local mood can’t (at this
moment).
When a new Dimmer is added, the first available ballast is assigned to this dimmer.
2
2
1
You can change the ‘Single Ballast’ to a ‘Ballast group’ to add more ballast to the dimmer. The
table with the ballasts has four columns:
 A checkbox to show if the ballast is assigned to the current dimmer.
 The DALI address for the ballast
 The name for the ballast, you can enter a name for the ballast in this column.
 Remark: Names for ballasts that are not assigned to a dimmer are not saved in
the .nbt file.
 The dimmer to which a ballast is assigned to (or empty if the ballast is not yet
assigned to a dimmer).
 Remark: ballast that are already assigned to the current dimmer are shown in
top rows of the table.
 REMARK: ballasts that are assigned to another dimmer than the dimmer that is
currently edited will be shown at the bottom of the table. You can’t assign these
ballasts to the current dimmer, if you would like to do this you need to
unassigned them from the dimmer to which they are assigned.
55
TELETASK Handbook
PROSOFT >
“O” Units: Outputs
56
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7. 'I' units: Inputs and others
7.1. General notions
Before you can enter all inputs and input units (= 'I' units) into your TELETASK project, it is essential to
have a good understanding of some basic items.
7.1.1. 'I' interfaces: Inputs and others
In contrast with the 'O' interfaces, the 'I' interfaces are less conveniently arranged because
there is a wider range of input units and input interfaces available. Additionally, interfaces
which may be both input and output are added to the inputs list.
As with the 'O' units, the 'I' units are divided in a functional as well as in a system related way.
 Functional classification
There are four different types of input units:
 'General Interface': these are all TELETASK (AUTOBUS connected) touch panels,
touchscreens, etc… (See more details in the overview list further in this text). When
somebody pushes a button on a touch panel, a command is sent to the central unit,
and the predefined action for this button is done.
 'Digital Input Interface': digital inputs are contact inputs for all kind of external on/off
signals like there are from standard voltage free push buttons (any brand), motion
detectors (often via a relay to be connected to the voltage free contact inputs of the
TELETASK input). When the concerned external contact is closed, the input unit or
interface generates the related command and the central unit processes this
command just like it was coming from a touch panel and the predefined action is done.
 'Analogue Inputs': analogue inputs are the connection between the TELETASK
system and the different kinds of TELETASK sensors. The sensors send their signal
to the analogue input (internal in the central unit or external on AUTOBUS). This
signal is continuously processed by the central unit and depending on the related
function, actions are taken at certain times.
 'AV - Interface': (Audio/Video) This is a whole family of different general and
dedicated (brand dependant) interfaces. All audio interfaces are AUTOBUS interfaces.
By these interfaces it becomes simple to control connected audio systems with
standard buttons and/or special touch panels and touchscreens.
 System classification
Beside of the functional classification, the 'I' interfaces can also be classified based on
the way they are connected with the TELETASK central unit.
There are two groups to be distinguished:
 'Direct or Internal 'I' Interfaces': these 'I' interfaces are integrated in the central unit.
Depending on the type of central unit you use, there may be different types of internal
'I' interfaces available in the central unit. Please refer to the concerning data sheet of
your central unit for more details.
 'AUTOBUS 'I' Interfaces': these 'I' interfaces are connected on the AUTOBUS. Most
of the 'I' interfaces are of this kind (TDS12116, 16 digital inputs for voltage free
contacts).
57
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.1.2. 'I' Address:
The address setting is necessary for the system to be able to communicate with the individual
interfaces and modules. Every 'I' unit and interface has its own address. All external
AUTOBUS connected 'I' interfaces have a hardware or software address setting on the
interface itself (just like Output interfaces).
The address numbering starts with an 'AUTOBUS number'. Then PROSOFT ads for internal
use an 'I' to the address. This way it will be very clear in PROSOFT that it concerns an 'I'
interface. This is necessary because there are also TELETASK AUTOBUS 'O' interfaces
which become an address (these are the output interfaces). These 'O' addresses are unrelated
of the 'I' addresses. This means that there can be an 'O16' and an 'I16'. In the 'O' and 'I'
address groups every address is unique. There can't exist 2 'O16' addresses or 2 'I16'
addresses.
The actual 'I' address starts with '00'; these are the Master functions on the remote control.
The first address which can be defined on an interface is '01'. PROSOFT automatically
generates an address for every new 'I' interface which is added to the system. Be sure that this
address is created for the 'I' interface or that the set-up in PROSOFT can be adapted to the
set-up of the 'I' interface. Differences between the hardware (on the interface) address setting
and the software (PROSOFT) address setting can result in incorrect and unpredictable
behavior of the system. Please check this before starting-up the TDS system.
 Some TELETASK interfaces use more than 1 address (e.g. the TDS12116 is a 16 input
digital input interface, and occupies two AUTOBUS addresses. Only the first address of
this input interface can be set-up in the hardware. The other addresses follow up this
hardware set-up address and will automatically be assigned by PROSOFT.
 To avoid errors in your configuration it is recommended to let PROSOFT decide what
the addresses are. PROSOFT automatically takes care of multiple addressing and will
avoid making errors about this.
 The standard 'I' interfaces (f.e. TDS10012 MICROS+) start on AUTOBUS 0.
 IMPORTANT REMARK: Using the same addresses twice on one bus is not allowed and
can generated dangerous and non-secure situations. So always check very carefully
before powering your system if no double addressing occurs (two or more interfaces
are set to the same hardware address).
58
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.2. Adding TELETASK 'I' interfaces
When you start a new TELETASK project you have selected the central unit type (MICROS+, NANOS
or PICOS). By doing this, PROSOFT automatically generates all standard available (internal) digital
and analogue inputs (and outputs) of the central unit.
PROSOFT also adds an input unit called 'Master' functions. These are the Master functions which can
be allocated for extra eight functions on the TELETASK remote control.
When you need additional inputs (like in most of the cases) than the ones standard available at a
central unit, you will have to add extra input interfaces.
When adding interfaces, there are four different parameters to be set:
7.2.1. Parameters for adding new 'I' interfaces:
 'Group': Choose the (functional) group to which the new 'I' interface belongs: 'General
Interface', 'Digital Input Interface', 'Sensor or Heat/Cool interface' or
'AV - Interface' (see 'I' interfaces: Inputs and others).
 Be sure to choose the correct group, because it is not possible to change an
interface from one group into an interface of another group any more. In such
case, you will have to delete the wrong interface first and then add the correct
one.
 'Interface type': select the interface you want to be added. The interfaces are shown
in the list sorted by their individual TDS reference.
 ‘Address’. The address can be changed by the user at any time if you want.
PROSOFT takes care of impossible or not allowed address settings. So if you change
the address to a not allowed address, PROSOFT will not allow you to do any changes
on the address setting.
 'Name': enter here a description of the location where the interface is installed
together with the inputs numbers which are already entered by PROSOFT (if it is a
contact input interface).
After all 'I' interfaces are added to your project, the different settable parameters of each of
them are to be configured. The parameters are different for the four groups of 'I' interfaces:
59
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 In practice:








Click on the ‘Inputs Icon’.
The 'List Interfaces' window appears on the screen. The standard 'I' interfaces
are displayed here.
Click the 'New' button to add a new 'I' interface to your project.
Click the desired interface in the ‘Select interface’ list and click OK..
The 'Define Interface Function' window appears on the screen. Configure the
parameters of the concerning interface (see below for more details).
Click 'OK': the 'I' interface is added to your TELETASK project and the window
'Define Interface Function' is closed.
The new interface is added in the 'Interfaces list' window.
Repeat this way of working for all TELETASK 'I' interfaces which you want to add
in your project.
60
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.3. General 'I' interfaces – Specific parameters
7.3.1. Common setting
 ‘Basic’ parameters which are available for every 'General interface':
 'Main IR enable': By default, the 'Main IR enable' is on. When this parameter is
marked ('V'), then every button can be controlled with the TELETASK infrared remote
control. If you don't want the panel to be controllable by IR remote, remove the 'V'
mark in this field.
The IR control can also be individually disabled for each button. See for more details
below at 'button' parameter settings.
 'Beep on IR command': Marked 'V' by default. When a function is controlled by the
TELETASK IR remote control, the panel buzzer will beep short when this parameter is
marked with 'V'.
This parameter is not yet available on all interfaces.
61
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 For some of the older interfaces this setting is done by hardware (refer to the
data sheet of the concerned interface). New interfaces support this 'Beep on IR'
by software.
 'Audio Zone': A 'General interface can be related to a certain 'Audio Zone'. This is
important when controlling audio functions on your TELETASK IR remote control
(TDS12502). Example: when you click the 'CD' button on your remote control, the
system needs to know in which audio zone the interface is installed, so it can start the
correct CD and the correct audio zone power amplifier. Select the audio zone from the
predefined zones. If you didn't yet entered the different audio zones in your project,
please do so first (in the PROSOFT screen of the concerning audio interface which
you are using in your project).
 'Sensor Zone': Familiar to the audio zone setting, you must connect the interface to a
certain sensor zone. When using a temperature control function on your remote
control (TDS12502), the interface (for example a touch panel) must me dedicated to a
certain heating/cooling zone for the system to be able to change the correct
temperature setting for you. Select the Sensor zone out of the sensor list which you
have entered already or, if not, add the temperature sensors and their zone names
first before proceeding here. Sensor zones are defined at the level of the analogue
(sensor) input unit. Look also in the thematical chapter 'setting up a heating/cooling
system' for more information on this subject.
 'RGB Zone': in this field you can link a multi-colour lighting zone (RGB) to a 'General
Interface'. This means that the selected RGB function will be controlled when you
activate it with the remote control when pointing at the IR receiver of the General
Interface. (when using the TDS12502)
 Parameter per individual button/input:
 Relations: The definition of the functional features of a 'General Interface' is mainly
defined by the relations between the inputs (for example the buttons of a touch panel
or contact inputs of a digital input interface) and the outputs (relays, dimmers,
motors…) of the system. Due to the characteristics of a relation, decide what the
actions are to be done after pushing a button or closing an input contact of a general
input interface. Additionally, there may be two different relations for every input (button
62
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
or contact). There is a possible relation for pushing 'short' and another relation for
pushing 'long' on the concerned button / contact:
 'Short': the function behind the 'short' action will be used to be processed when
the user pushes only briefly on the concerning button or when the concerned
input contact is only closed briefly.
 'Long': the function behind the 'long' action will be used to be processed when
the user pushes longer than 1,2s on the concerning button or when the
concerned input contact is closed for a 'long' time.
 Refer to the 'Extra' - 'Options' menu in this handbook for custom setting of
the 'short' time definition. TELETASK recommends not to change this
setting. There are two differences about time settings for short/long:


'LONG push on general interfaces': This time can only have two
settings: 1,2 or 3 seconds. This setting is automatically adapted to the
value of the direct input Long push.
'LONG pushing internal contact inputs': To be set between 1
second to 5 seconds in steps of 0.5 seconds. By default this time is 1
second.
 'Button': In this field there are two more settings possible for each individual
button/input:
!!! Take care about the important remark below in the frame!!!
 'Enable Remote Control': when this parameter is marked 'V' (default), then you
can control the individual button (short and long) or contact input which is
currently selected on the picture of the interface.
 Buttons/contacts 1 to 8 are on the picture of the interface and can be
selected by clicking on them with the mouse pointer. The IR remote control
activates the same buttons as the ones on the wall panel or input interface.
 This item is marked by default.
 If your 'I' interface has more than eight buttons or inputs, the IR remote
control controls the first 8 of them. There may be exceptions on this rule.
 IMPORTANT REMARK: Remove the ‘V’ mark when you control a door
opener or another security related item with that particular button.
Otherwise anybody having a remoter control and standing outside may be
able to open your door via a remote control which is transmitting through a
window or any other visual open surface. For security and safety reasons
this is absolutely not allowed and must be avoided in any case! It is the
responsibility of the programmer of the system that these and comparable
actions are to be blocked.
 'Enable Button Control': this parameter is available for the physical buttons on
the touch panel or the physical inputs on the input interface. It is similar to the
'enable Remote Control'. By default this parameter is marked for all individual
buttons/contacts. So when somebody pushes a button which is not marked at the
'Enable Button Control' nothing will happen. The relation of that button, although it
is defined, will not be processed because the button activity is disabled.
Disabling the button function is seldom used, but is for example usable if visitors
are not allowed to control something in the house. The occupant can for example
control that function with a remote control. Can be useful in public areas.
 'Info': This is a text field for your information only (on screen and on paper). You can
enter a specific description here about the location of the concerning button. This is
particularly useful on digital input interfaces. This text will displayed in the ‘Input list’ on
63
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
the ‘List interfaces’ window and in Diagnostics/Digital inputs.
Example: 'motion detector driveway' or 'push button hallway'.
 Clean button on AURUS touch panels
All AURUS touch panels have a (hidden) clean button which disables the operation for
a couple of seconds. Pressing short will switch the display ON (only for AURUS-4
TEMP and AURUS-OLED (PLUS)). When pressing for a couple of seconds, it will set
the Touch panel in clean mode. During this time the panel can be cleaned without
activating any buttons.
For the AURUS-1, AURUS-2, AURUS-2 SENSE, AURUS-4S, AURUS-4XL, AURUS-4
TEMP and AURUS-OLED, this hidden clean button is situated at the top in the middle.
For the AURUS-OLED PLUS it’s the middle dot on its left side.
For the AURUS-TFT it’s a wiper icon
page’:
on the ‘Home-page’ or the ‘Favorites-
or
64
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.3.2. Advanced settings for AURUS touch panels
An AURUS touch panel is similar to the other TELETASK touch panels. In this section we go
deeper into all the specific settings.
 Advanced tab
 'Orientation': Available on AURUS-2, AURUS-4XL and AURUS-OLED. Here you can
choice between 'Default' and 'Rotated'. This way you determine how you will mount
the touch panel horizontally or vertically.
 The default state of the AURUS-2 is with the two buttons horizontally
positioned.
Default
Rotated
65
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
This setting can always be changed. The configured functions of the buttons won't be
deleted.
 Pay attention: Always check if the notes are displayed completely on the
AURUS-OLED. By turning the AURUS-OLED the positions of the icons and the
notes will change.
 Check this in the 'Edit this screen'-menu.
 ‘Display Brightness’: Only available on the TDS12064. Switch between High
(default), Medium or Low. In a bright environment it is advised to keep it on High
where in a rather dark environment (e.g. bedroom) it is recommend to set the
brightness on Low.
 '(OLED) Display OFF after': Only for the TDS12022, TDS12032 and TDS12064.
Here you can change the default 15 min from 1 to 60 min (6h for TDS12064).
 Be aware that increasing the time the AURUS-TFT is ON will decrease the
display life time
 'Feedback LED’s ‘ON’ brightness': you can choose between ‘Maximum’ (Default),
‘Medium’ or ‘Minimum’.
 'Feedback LED’s ‘Night illumination’': you can choose between ‘Maximum’,
‘Medium’, ‘Minimum’ (Default) or ‘OFF’. It can be wisely to change the Night
illumination to OFF in a bedroom.
 'Feedback LED’s OFF when OLED if OFF': Only for the TDS12022 and TDS12032.
 'Auditive feedback on touch': by default the AURUS-TFT will give a click every time
a button is pressed. When preferred, this can be switched off.
 ‘Motion detection feedback on IR LED’: indicates that the IR LED of the TDS12025
will be on when motion is detected.
66
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
Setting
TDS12019 AURUS-1
TDS12020 AURUS-2
TDS12024 AURUS-4S
TDS12021 AURUS-4XL
TDS12026 AURUS-4 TEMP
TDS12022 AURUS-OLED
TDS12032 AURUS-OLED PLUS
TDS12025 AURUS-2 SENSE
TDS12064 AURUS-TFT
Compatibility list:
Orientation
NA
V
NA
V
NA
V
NA
V
NA
(OLED) Display OFF after
NA
NA
NA
NA
V
V
V
NA
V
Display Brightness
NA
NA
NA
NA
NA
NA
NA
NA
V
Feedback LED’s ‘ON’ brightness
V
V
V
Ver. 10
V
Ver. 20
V
V
NA
Feedback LED’s ‘Night illumination’
V
V
V
Ver. 10
V
Ver. 20
V
V
NA
Feedback LED’s OFF when OLED if
OFF
NA
NA
NA
V
V
V
NA
NA
Auditive feedback on touch
V
Ver. 4
V
Ver. 10
V
Ver. 27
V
V
V
Motion detection feedback on IR LED
NA
NA
NA
NA
NA
NA
NA
V
NA
NA
67
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 Built-in temperature sensor.
The AURUS-1, AURUS-2, AURUS-2 SENSE, AURUS-4S, AURUS-4XL, AURUS-4
TEMP, AURUS-OLED and AURUS-OLED PLUS contain a built-in temperature
sensor. This can be used as sensor zone through the complete Domotics project.
The built-in temperature sensor isn't activated by default. To activate, follow the
following instructions:



Click on the temperature sensor icon
Choose 'AURUS Temperature sensor' as ‘Sensor Type’ and give the sensor a
proper name: e.g.: Sensor AURUS-OLED Living.
If the sensor will be used to control a heating/cooling system, complete the
settings at 'Output properties':
68
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.3.3. AURUS-2 SENSE
The AURUS-2 SENSE with built-in motion and light sensor, can be set to the specific needs of
your project and to the specifications of the user.
 Motion detector:
69
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
For the ‘motion detector’ of the AURUS-2 SENSE there are two options:
 ‘Motion detector function’: This is the default option, where the ‘motion detector
function’ is defined directly on the AURUS-2 SENSE.
 ‘Link with other AURUS-2 SENSE’: Use this option if a ‘motion detector function’
was already created on another AURUS-2 SENSE and you want this AURUS-2
SENSE to work the same way. If you select this option, all that remains is to select the
‘other’ AURUS-2 SENSE from the drop down list.
To Define the motion detector function the following parameters need to be set:
 ‘Output’: This is the light (or other function) to be controlled by the motion detector
function.
 ‘Active time’: This is the time the output needs to be activated after the closing edge.
 ‘Light level’: Optional, this is the light level below which the motion detector function
needs to activate the output. If ‘None’ is selected here the motion detector function will
always activate the light when motion is detected.
 Remark: If a light level is selected the build-in light sensor will be activated
automatically (if necessary).
 Remark: The ‘motion detector function’ created by the AURUS-2 SENSE is also
available in the list of ‘motion detector functions’ so it can also be used by a
traditional motion detector that needs to work together with the AURUS-2
SENSE (see chapter ‘motion detector function’).
 Remark: The motion detector button is always edge triggered (see chapter
‘Digital Input interfaces – Specific parameters’).
 Remark: The motion detector button cannot be used from the TELETASK
remote controllers.
70
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 Built-in light sensor:
The AURUS-2 SENSE contains a built-in light sensor. This can be used as sensor
zone through the complete Domotics project.
The built-in light sensor isn't activated by default. To activate, follow the following
instructions:



Click on the light sensor icon
Choose 'AURUS Light sensor' as ‘Sensor Type’ and give the sensor a proper
name: e.g.: Sensor AURUS-2 SENSE Living.
If the sensor will be used to control a function, complete the settings at 'Output
properties':
71
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.3.4. AURUS-4 TEMP (TDS12026)
The AURUS-4 TEMP is designed to control the HVAC system of the installation. This can also
be a basic heating only or cooling only installation. Additional settings can be made to the
specific needs of the project and to the specifications of the user.
 Temperature sensor selection
72
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
When creating an AURUS-4 TEMP, a pop-up screen will ask to select the desired
temperature sensor zone that will be shown on the display.
There are 3 options:
 Use the internal temperature sensor of the AURUS-4 TEMP
 Select another sensor zone (only temperature sensors can be selected).
 Select “Ask me later” if you would like to use another sensor that is not yet
defined. As long there’s no sensor zone defined in the ‘select sensor zone’
window this pop-up screen will re-appear every time you enter the Define
Interface Window.
 To change this selection afterwards, you can click on “Customize this screen”
button.
After selecting the internal sensor you’ll need to complete the Sensor definition
window. This is identical to other temperature zones: fill in the Heat and/or Cool
method and set the Preset values.
73
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 Buttons and Display
The AURUS-4 Temp has 4 predefined buttons to control the HVAC installation. With
these the HVAC mode, fan speed, preset temperature, manual temperature setting
can be controlled and the temperature zone can be switched ON or OFF.
It also has room for two additional functions (e.g. lights, moods, …).
 Depending of the HVAC installation, some features can be unavailable.
Display layout:
The placement of the icons in combination with the predefined functions of the
buttons, give the end-user a user-friendly experience. The ‘Long press functions’
represent the icons in the respective corners of the screen.




1: HVAC Mode
2: Preset temperature selection
3: Temperature down + Fan speed setting
4: Temperature up + zone ON / OFF
74
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 The position of the icons is fixed and cannot be customized.
 The default configuration of the buttons can be changed if desired.
 When a dimmer function is selected for one of the buttons, the ‘predefined long
press function’ will be deleted.
Button 1 (HVAC mode):
 ‘Short press function’: can be any function that you want (e.g.: the main light in the
room).
 ‘Long press function’: is default set to select the mode of the HVAC system. It will go
to the next available mode in a loop.
AUTO
COOL
HEAT
VENT
DRY
 REMARK: Only modes that are supported by the HVAC installation will be
displayed. Configure these in the Sensor zone settings.
 Remark: For Airzone installations there are two additional modes available:
STOP and Heat P.
Button 2 (Preset temperature):
 ‘Short press function’: can be any function that you want (e.g.: a mood).
 ‘Long press function’: is default set to select the preset temperatures (Day, Night,
ECO). It will go to the next available preset in a loop.
Day
ECO
Night
Manual
Blanc
 REMARK: When the temperature is manually set, no icon will be shown.
75
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
Button 3 (Manual temperature setting + Fan speed):
 ‘Short press function’: is set to manually lower the temperature setting by default
(down arrow). When short pressed, the target value is shown (value is underlined).
When pressed again, the target setting will be changed. After 3 seconds the measured
value will be shown again.
 ‘Long press function’: is default set to scroll through the available fan speed
settings. It will go to the next available speed in a loop.
LOW
MEDIUM
HIGH
AUTO
 Remark: only Modes that are available on the Senor zone will be displayed.
Button 4 (Manual temperature setting + zone ON / OFF):
 ‘Short press function’: is set to manually increase the temperature setting by default
(up arrow). When short pressed, the target value is shown (value is underlined). When
pressed again, the target setting will be changed. After 3 seconds the measured value
will be shown again.
 ‘Long press function’: is default set to switch the temperature zone ON or OFF to
enable or disable the heating / cooling of the HVAC system.
ON
OFF
 REMARK: When the zone is switched OFF by a window open contact this Icon
will be shown:
 Remark: When lowering or increasing the temperature (short press button 3 of
4), the HVAC system will respectively immediately start cooling or heating and it
will also switch ON the temperature zone when it was OFF. This can be changed
in the sensor settings under Extra > Options > Sensor. This is standard enabled
in new .nbt files, but not in existing files that are upgraded to 3.4.7.0 or newer.
76
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
77
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.3.5. AURUS-OLED (TDS12022) and AURUS-OLED PLUS
(TDS12032)
 Main page and general notions.
The AURUS-OLED (PLUS) contains four pages with each eight different buttons. You
can thumb through these pages by turning them in a virtual manner. Just stroke with
your finger on the hidden buttons to thumb to the next or previous page.
As soon as the AURUS-OLED (PLUS) has been tipped, the main page will illuminate.
The eight functions which are defined on the main page must be the functions that the
end user needs the most.
In contrast with the sensor- and audio pages, there are no predefined buttons on the
main page. The Sensor- and Audio pages contain already all needed settings to
regulate the temperature or audio on a user-friendly way. The main page on the other
hand will always depend on the domotics project. It is possible to define a sensor or
audio function on this page when this function will be used very often.
 PAY ATTENTION: there is a difference between an audio-/sensor function and a
LCD/VFD (DISPLAY) FUNCTION!
 A sensor- or audio function is always linked to one sensor- or audio zone.
 A LCD/VFD (display) function regulates the sensor- and audio functions
depending on the selected zone on the display. Here you always have to
configure a zone-selection button (e.g. 'Display function: sensor: next zone').
 TIP: Configure on the first page a coupled sensor function 'preset down' and
'preset up', for the built-in sensor of the AURUS-OLED. This way you will have
an easy read out of the temperature in the room where the AURUS-OLED will be
placed.
78
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 Sensor Page
The sensor page, just like the main page, can be adapted to the customers' wishes.
As the AURUS-OLED (PLUS) is extremely suitable for the visualisation and regulation
of heating-, cooling-, or fan systems. TELETASK already predefined the functions.
The functions on these pages are all LCD/VFD (display) functions. This means that
they are depending on the 'zone' button (by default button 7)! A long press on the
'zone' button will lead the user to the page to predefine the temperature presets
How to show the “power consumption” on an AURUS-OLED (PLUS)
When you don’t change anything on the second page of an AURUS-OLED (PLUS), it
will automatically display all the different sensors in your project. Any type of sensor
will be listed here unless it was removed from the AURUS-OLED (PLUS) using the
“Customize this screen – sensor and audio zones” option.
Sometimes it could be interesting to bring forward one of even more of these
“sensors” and put them on the first page of the AURUS-OLED. One clear example is
to show the power consumption.
To do this, choose a button of the AURUS-OLED (PLUS) that you want convert to a
shown value and select “sensor function” under the short press. Next select the
sensor you want to display and choose the “show measured value” option.
You will now get the measured value shown underneath the icon. To bring forward the
sensor value even more, select the “couple horizontally/vertically” option!
 Audio page
The audio page can also be adapted to all the wishes of the end user, just like the
main page. As the AURUS-OLED (PLUS) is extremely suitable for the display and
control of audio-and video systems, TELETASK already predefined these functions.
The functions on this page are all LCD/VFD (display) functions. This means that they
are depending on the 'zone' button (by default button 7)!
For track feedback on the AURUS-OLED (PLUS), you have to couple the previous
and next buttons.
 Extra page
The fourth and last page is completely adjustable to the wishes of the end user, just
like the main page. This page contains no predefined functions.
 Delete or adapt order
79
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
It is always possible to adapt the order of the pages or to restrict the number of pages
on the AURUS-OLED (PLUS) to only three, two or even one page.
To move a page:


Click on the page you want to move and keep the mouse pressed.
Move the page to the new place.
When deleting a page, all functions on the page will be deleted and the page will be
moved at the back. A page on which no function is predefined and which is not
followed by a page with functions, will not be displayed on the AURUS-OLED (PLUS).
 PAY ATTENTION: this page will be displayed in the PROSOFT Suite. It doesn't
disappear completely.
 Coupling buttons
The AURUS-OLED (PLUS) offers the possibility to couple buttons with each other.
When mounting vertically the buttons can be coupled horizontally and when mounting
horizontally the buttons can be coupled vertically.
 Coupling buttons is only suitable for functions where it makes sense to split the
control over two buttons, e.g. control of a curtain/shutter, the control of a
dimmable light, the control of a temperature setting.
 TIP: always consider the correct way or direction for these functions: up/down,
open/close, less/more, in the 'Edit this screen' menu the corresponding arrows
can be selected!
80
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
Practical:





Click on the first of the two buttons you want to couple. E.g.: button 1.
Select under 'short' the first half of the double button combination, f.e. a dimmer
or a Display function like 'sensor down'.
Click on 'Couple horizontally'.
Check the functions which will be automatically defined on this coupled button. In
this example = button 2.
Click on 'Edit this screen' to finish the details of the coupled buttons: icon, note.
 Customize this screen-menu
In this 'Edit this screen'-menu you can adapt the visual details of the touch panels.
You can:





Change the page name.
See a realistic preview of the AURUS-OLED (PLUS) screen.
Change or create icons.
Adapt the notes.
Adapt the sensor- and audio zones.
81
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 ‘Page name’: the page name is only for use within the PROSOFT Suite.
 ‘Show Areas’: this way you can see which buttons are coupled and which button you
are editing.
 ‘Show preview’: you will see a visual example of the AURUS-OLED (PLUS) screen.
 ‘Text’: Every button is provided with an icon and two lines of text (note). The length of
the text is limited to the width of the icon. With coupled buttons there is more place for
notes. For some functions the second line will be reserved for the indication of the
status; e.g. a dimmer where the dim value is displayed in %.
 ‘Icon’: depending on the type of function which is coupled to a button, PROSOFT will
suggest an icon. If you want to change this icon, you can choose out of the
TELETASK library with existing icons (ranked in different categories) or you can draw
your own icon!
 ‘Sensor and audio zones’: in the underlying screen you can select and reorder the
sensor- and audio zones which have to be displayed on the AURUS-OLED (PLUS).
All available zones are selected by default.
 Draw an icon.
The AURUS-OLED (PLUS) offers the possibility to draw a personalized icon:
 Click on the work bar beneath the list of icons:

Here you can choose respectively 'new icon'- 'edit present icon'-'copy present
icon' and 'delete present icon'.
82
TELETASK Handbook


PROSOFT >
“I” Interfaces: Inputs and other
A new icon is always added to the list 'user'. Only the self-drawn icons can be
changed and/or deleted.
The TELETASK icons can be copied. They will be copied to the list 'users' with a
new name which was entered in the draw screen.
 TIP: the icons of the AURUS-OLED (PLUS) are saved in the .NBT file. They aren't
lost when the file is opened on another PC.
 Also the self-drawn icons are kept in the .NBT file.
Practical:



Click on 'new icon'
Give a name to the new icon.
Draw the new icon in the left drawing field:
83
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 ‘ON and OFF State’: Every icon knows two states: 'ON' and 'OFF'. Normally the 'OF'
status is automatically built based on the 'ON' status. This means: the 'OFF' status is
identical to the 'ON' status but less clear!
 'Draw a custom OFF status'. When this is selected the 'OFF' status won't be built
automatically. Now you can provide an adapted 'OFF' status. Example:
 TIP: by clicking a field with the left mouse button, you give the selected pixel the
selected colour (always 7 colours available).
 When clicking this field with the right mouse button you erase the colour of this
pixel!
 Displaying the Sensor and Audio zones.
In the 'edit this screen'-menu, you can, just like all the other control panels with a
display, adapt the displayed sensor- and audio zones. Check the selection field out if
you don't want to display the sensor or audio zone.
To change the order you have to select a zone and then click on the large arrow 'up'
or 'down'.
84
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 Delete the AURUS-OLED (PLUS) memory & demand the version number.
When the AURUS-OLED (PLUS) screen isn't built-up correctly, you can 'delete' this
(the icons will be saved in the intern memory of the AURUS-OLED by starting up or
after sending the NBT to the Central Unit):
Push LONG simultaneously on the two hidden 'thumb'-buttons until the screen turns
black and is re-built.

When re-starting the AURUS-OLED (PLUS), the version number of the intern
software of the AURUS-OLED (PLUS) will be displayed and the configuration
data will be reloaded automatically.
85
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.3.6. AURUS-TFT (TDS12064)
In PROSOFT there are different parameters which can be set to the specific needs of your
project and to the specifications of the user.
 Customize this screen:
86
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 Favorites tab: When you click this button, the “Define AURUS-TFT” window appears.
In this screen, you will find a simplified AURUS-TFT screen where you can edit the 8
AURUS-TFT favourites buttons to your personal needs. You can modify the names
and change the icons.
 Rooms & Items tab: In this window you can change the different control menus of the
AURUS-TFT.
 Sorting the menu items: you can change the order of appearance of the items
in the menus. If you want for example to display the ‘kitchen’ on top of the rooms
list, select the ‘kitchen’ button and drag the room to the desired place.
You can do the same sorting for the functions when you click the functions. Place
the most often used functions on top of the list and the seldom used functions at
the bottom.
 Visualisation: you can hide a room or function by removing the ‘V’ mark next to
it.
 !!! Be sure that all to be hidden functions are effectively hidden, because in
some cases this can generate unwanted results by fault use of the buttons
on the AURUS-TFT screen. An example of a function which is to be hidden
is a relay output which controls a heating valve or circulation pump or a fan
of a heating or cooling system. These kinds of relays are to be controlled
by the intelligence of the TELETASK system and are not to be controlled
directly by the user.
 A function will be automatically shown on the AURUS-TFT screen when the
parameters ‘room’, ‘icon’ and ‘name’ of the concerned function are entered.
 User code protection: A function can be user code protected. This means that
the function only can be controlled after clicking that function with your finger on
the AURUS-TFT touchscreen and after entering the correct user code.
87
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
To protect a function, just check the “Passcode” mark.
The standard factory user code is “12345”. This user code can be changed any
time in PROSOFT in the “Users & groups” configuration menu.
 Read only: This parameter is unchecked by default, when this is checked the
item will only show the status but cannot be controlled.
 Settings: In this window you can change the different control menus of the AURUSTFT.
 Configuration: Select if the user is allowed to make changes to the sensor
presets and clock actions.
 Not all clock actions can be edited on the AURUS-TFT. Only the clock
actions for a thermostat and clock actions for which the option ‘‘Allow user
to change this clock on Touchscreen” is checked can be edited (see
TIMESOFT).
 Screen saver type: The screensaver will be Default off. If desired, you can select
the “Clock screen saver” to display the time when the AURUS-TFT is in standby
mode. Regardless of the selected screensaver, the display will switch off after the
selected time (see the “Display OFF after” setting).
 Time format: Here you can switch 23:59 or AM-PM notation.
 Date format: The same as with the time format, here you can choose your
preference of the way the date displays on the Screensaver.
 Camera captures: Add an email address (max. 5 for every AURUS-TFT) if you
would like to receive an email with camera captures every time a screen capture
is made. If black, the camera capture functionality will be unavailable.
 All the above settings are to be set on each individual AURUS-TFT unit (in
PROSOFT). When you have more than one AURUS-TFT panel in your
project, every AURUS-TFT can be set in a different way. Example: In the
88
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
master bedroom all functions in all rooms may be accessible. But in the
guest room, only functions in the guest room and for example in the guest
bathroom are shown on the screen.
 The sensor and audio zones are only available in the ‘Edit screen’ window
when they are connected with a room in the ‘list room’ window. One audio
zone and up to five sensor zones can be connected to a room.
 Energy management
With the AURUS-TFT you can visualize the energy generation, consumption and
balance of your project in kW, kW/h or in the desired currency. Per installation you can
have one overview screen.
 If you visualize the values in kW, be aware that this will be the total of today
(starting at midnight) or the total of the last 24h. This depends of the sensor
‘Timebase’ which you can configure in the TDS12116.
Example:
89
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
How to configure the Energy balance screen


Go to Extra > Options > Sensor tab
Click on ‘Energy settings’ under ‘Energy management and Charts’
 Energy management window: In this window you can configure the energy
management parameters.
 Preview window: In the left corner you will see a preview of the energy balance
screen on the AURUS-TFT with at left, the energy generation visualised as PV
panels and at the right the house as consumer.
 Maximum production (kW): In order to have a correct scaling (balance)
between the production and consumption, you will have to fill in an assumption of
the possible maximum production (eg.: of you PV panels).
 Average Profit per kWh: Here you fill in the profit you will get when you put your
generated electricity back to the electricity grid.
 Pulse counter sensor for energy production: In this column you can select
which ‘kWh (pulse) sensor’ will act as the ‘Energy production’ counter. You can
select multiple.
90
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 To see something in this column you will have to add a sensor which is
defined as a ‘kWh (pulse)’ ‘Sensor Type’ on one of the inputs of a Digital
input interface TDS12116. See image below.
 Be sure that all sensors have the same ‘Timebase’ (last 24h or Today) to
prevent an incorrect balance.
 Currency: Type here your desired currency (eg.: €, $, £,…).
 The AURUS-TFT will display the currency as value/kWh.
 Maximum consumption (kW): In order to have a correct scaling (balance)
between the production and consumption, you have to fill in an assumption of the
possible maximum energy consumption.
 Average cost per kWh: Here you fill in the price you have to pay per kWh when
you buy it from your energy supplier.
 Pulse counter sensor for energy consumption: In this column you can select
which ‘kWh (pulse) sensor’ will act as the ‘Energy consumption’ counter. You can
select multiple.
 To see something in this column you will have to add a sensor which is
defined as a kWh (pulse) sensor type on one of the inputs of a Digital input
interface TDS12116.
 Chart visualisation
All types of sensors can be displayed on the AURUS-TFT as trend lines or block
diagrams to visualize gas consumption, rainfall, energy production, temperature, wind
velocity, light intensity, etc.
The AURUS-TFT can display sensor values per day, week, month, year and always
with a comparison of last day, week, month, year, in the background. Depending of
the type of sensor (analogue or digital) these will be visualized as a trend line with
min/max lines in the ‘month’ and ‘year’ screens, or as block graphs with totals per
hour, day, week or month.
91
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
Example:
 Up to 100 sensors can be visualized per central unit.
 The sensor data is collected and memorized in the DoIP central unit. So if the
AURUS-TFT is replaced, the sensor values will still be available.
 You can only visualize the current and last day in hours, the current and last
week in days and, the current and last month in weeks and the current and last
year in months. The AURUS-TFT cannot visualize for example the hours of a
particular day two weeks ago. On the GUI+ (TDS15105) this is possible. Refer to
the chapter of GUI+ for more details.
How to enable in PROSOFT:


Go to Extra > Options > Sensor tab
Click on ‘Energy settings’ under ‘Energy management and Charts’

Enable the sensors for which you want to have a chart available on the
AURUS-TFT.
92
TELETASK Handbook

PROSOFT >
“I” Interfaces: Inputs and other
The charts symbol will now be available on the sensor page on the AURUS-TFT
after you transmit the .nbt file to the DoIP central unit.
 AUTOBUS and network settings on the AURUS-TFT
 AUTOBUS
 Go to the home-screen and press the configuration icon (gears) at the bottom to
go to the configuration-screen.
 Press on the AUTOBUS address to make a change.
 Fill in the technical code: 09876
 Fill in the correct AUTOBUS address.
 Press OK
 Network configuration
 Go to the home-screen and press the configuration icon (gears) at the bottom to
go to the configuration-screen.
 Press on the ‘network configuration’
 Fill in the technical code: 09876
 Set everything as it should and press OK every time.
 Upgrading the AURUS-TFT software version:
To upgrade an AURUS-TFT, go to Extra  Diagnostics  Interfaces and look for the
AURUS-TFT in the list. If a new version is available, an “Upgrade” button will be
displayed in the “Version” table. In the ‘Upgrade interface’ window, the necessary
components will be automatically be selected. Click the Upgrade button to start the
upgrade process.
 The upgrade process can take up to 45min. Other interfaces will function as
normal but a small lag is possible.
 When the upgrade process is started, it is not possible to cancel the action.
93
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 Once the upgrade is started, you may close PROSOFT. The upgrade process
will continue.
 To see if the upgrade process is still running or has been finished, let
Diagnostics search the interfaces again to see the current status.
94
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.4. Digital Input interfaces – Specific parameters
 The different available parameters
The adjustable parameters of the digital input interfaces are the same as these of the 'General
Interfaces'. Depending on the selected interface, the following parameters can be added in the
'Button' field:
 'Invert Input': when this parameter is marked with a 'V', the input will work inverted.
So the central unit is not taking action when the contact is closed (for most of the
functions) but when the contact opens.
This is most often used when a NC (Normally Closed) contact is connected to the
input.
 'Edge triggered': when this parameter is marked with a 'V', the 'short' and 'long'
names will change into 'on closing' and 'on opening'.
 'On closing': the coupled action is processed at the moment that the contact
closes and for as long as the contact remains closed (or the button remains
pushed in case of a normal open contact).
 'On opening': the coupled action is processed on the moment that the contact
opens or the button is released (in case of a normal open push button contact).
When an input works ‘Edge triggered an ‘Extra function’ tab will be available on which a
second ‘on closing/on opening’ pair of functions can be defined.
95
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 Remark: For some functions the ‘Edge triggered’ option is automatically set e.g. motion
detector functions, transparent functions, … In these cases the ‘Edge triggered’ option
cannot be cleared.
96
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.5. Analogue input interface – Specific parameters
 'Sensor definition' field
 'Sensor Type': this parameter defines the type of sensor which is connected to the
concerning analogue input. There are several different types of sensors which can be
connected.
 'Temperature sensor.': Select this sensor if you have connected a TELETASK
temperature sensor TDS12250 or TDS12251 to your analogue input.
 By using a TDS12020/21/22/24/25/26 AURUS family touch panel, the built-in
temperature sensor will be configured the same way as another
temperature sensor.
 'Humidity sensor': Select this sensor if you have connected a TELETASK
humidity sensor TDS12260 to your analogue input.
 'Light sensor (dark)': Select this sensor if you have connected a TELETASK
light sensor TDS12270 to your analogue input, which is set (hardware setting) as
a 'dark' light sensor. Refer to the data sheet of the TDS12270 for details about
this setting.
 'Light sensor (normal)': Select this sensor if you have connected a TELETASK
light sensor TDS12270 to your analogue input, which is set (hardware setting) as
a 'normal' light sensor. Refer to the data sheet of the TDS12270 for details about
this setting.
 'Light sensor (sun)': Select this sensor if you have connected a TELETASK light
sensor TDS12270 to your analogue input, which is set (hardware setting) as a
'sun' light sensor. Refer to the data sheet of the TDS12270 for details about this
setting.
 Remark: the hardware settings of the light sensor are to be done by setting
the appropriate jumpers like described in the TDS12270 data sheet.
97
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 'DAIKIN, Airzone, Mitsubishi Electric sensor': These sensors are only
available on the specific interface (see chapter Airco Software license).
 'General linear sensor': these sensors are only available on the TDS12310.
With this every type of linear sensors can be read with a standard analogue
output signal (0-10V, 4-20mA,…) This sensor gives an average value (=sudden
changes are not directly noticed)
 'Wind sensor': These sensors are only available on the TDS12310. With this
every type of linear sensor can be read by an analogue output signal (0-10V, 420mA,) this sensor reports advanced changes immediately! (f.e. by measuring
blasts of wind)
 'Sensor Name' or 'Sensor zone': In this field you can enter the name of the sensor.
This should be the temperature / light or humidity zone for this sensor.
Example: 'ground floor', 'bath room', 'bedroom Lucas', 'South sensor', 'Twilight East'. If
it concerns a temperature sensor which controls only the temperature of the room
where the sensor is installed, then the name is the room name. If the T sensor
controls several rooms, than the name may be 'ground level' or 'sleeping area' or
something similar. Keep the name short, because this name is to be displayed on the
displays and touchscreens which have a limited number of characters available for the
name of the sensor zone.
 'Compensation': This parameter is only available when you selected a temperature
sensor in the sensor type field. The content of the compensation field defines an offset
to the measured temperature value. The TELETASK system can work with
compensation temperatures between -5°C and +5°C in steps of 0.5°C. This
compensation is default set to -2°C for TDS12250 and 0°C for TDS12251 and is
advised not to be changed.
 The 'Properties' field
After selecting a 'sensor type', different fields appear in the 'properties' window. The
possible parameters for this field are: The following parameters can be entered:
When a temperature sensor has been selected
 'Heat – Control method': this parameter defines what kind of heating control method
is to be used. You have the following choices:
 Standard relay control method: this is a traditional ON/OFF control. It means
that the concerned Temperature sensor will control the heating system by means
98
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
of one output relay of the TELETASK system. When the room has to be warmed
up, the relay (contact) will close and when the target temperature is reached the
relay contact is opened.
This is to control a valve, a circulation pump or a fan or similar item.
'On/off': select the relay which you want to use to control the
connected heating system. For example the relay that switches the
electrical valve of the heating zone 'ground floor'
 Analogue control: this is when your heating system is to be controlled by a 0 to
10 V analogue output.

'On/off': Select here the relay which is to be switched (when
necessary).
 'Analogue Output (5°C difference=100% heat/cool)': Select here the
analogue (dimmer-) output which is to be used as the Analogue
control output for this Temperature zone.
 4 speed (OR) control: To be used for multi speed (off/low/medium/high) fan
motors. This option is about an OR system, so it means that only one of the
controlled relays will be on at the same time.

'Low speed (at -0.5°C)': Select the relay which is to be activated (close
the contact) for low speed of the evolved fan.
 'Medium speed (at -2.5°C)': Select the relay which is to be activated
for medium speed of the fan.
 'High speed (at -5°C)': Select the relay which is to be activated for
high speed setting of the fan.
 4 speed (AND) control: To be used for multi speed (off /low/medium/high) fan
motors. Same as for the 4 speed 'OR' control, but the lower speed output relays
will stay on if a higher speed setting is set.

'Low speed (at -0.5°C)': Select the relay which is to be on for low fan
speed.
 'Medium speed (at -2.5°C)': Select the relay which is to on together
with the low speed relay, when medium fan speed is needed.
 'High speed (at -5°C)': Select the relay which should be on together
with the low and medium speed relay, when high fan speed is needed.
 Local Mood control: only for special applications.

'On/off': Select the local mood which is to be switched on/off when
temperature control is done.
 Flag control: only for special applications

'On/off': Select the flag which is to be controlled when temperature
control is done.
 Fan coil unit: select this type of control method to use a fan coil unit for your
heating/cooling system.

99
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
More information about the control of a heating system can be found in the thematical
applications chapter in the heading 'how to integrate a heating/cooling system' further
in this document and at the chapter about the 'extra menu' in this handbook.
 'Cool – control method': this parameter defines which type of cooling control is to be
used. At the selection of the control method, there are some extra parameters
available. You have the choice out of the same systems as for the heating control.
 'Day Temperature': This parameter is the threshold value of the sensor as set by the
'Day' preset temperature. This parameter can be set from 5°C to 30°C in steps of
0.5°C. By default, the 'day temperature is set by the system to 20°C.
The 'Day Temperature' is used by the TELETASK home automation system as a
threshold for the 'heat' system. The 'Day' temperature for the cooling algorithm is x °C
higher than the 'day' temperature parameter. The difference is defined by the 'Delta
Heat/Cool' parameter. In PROSOFT this 'day' temperature for the 'cool' system is
displayed in grey beside of the set 'Day' temperature which is shown at the left of
'Heat'.
The 'Delta Heat/Cool' is changeable in the 'Extra' - 'Options' menu under the 'sensor'
tab.
 ‘Stand-by Temperature' (economic energy saving preset): the 'Stand-by'
temperature is derived from the 'Day' temperature. Therefore the 'stand-by' parameter
is not the effective temperature but contains the difference to the 'day' temperature.
The 'stand-by' parameter can be set from 0.5°C to 5°C in steps of 0.5°C. Default the
'stand-by' parameter is set to 5°C.
 The 'Day/Stand-by Temperature' is used by your system as a threshold for the
'heat' system. The 'Day/Stand-by' temperature for the 'cool' system is a
changeable number of °C ('Delta Heat/Cool') plus the stand-by temperature
parameter higher. (For Stand-by this is the Day preset plus the stand-by
temperature plus the 'Delta hot/cool'). This 'Day/Stand-by' temperature of the
'cool' system is in PROSOFT displayed in grey beside to the 'stand-by' preset
100
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
before 'heat'. The 'delta heat/cool' parameter is changeable in the 'extra'
'options' menu, under the 'sensors' tab.
 'Night Temperature': this parameter defines the threshold value of the sensors as set
in the 'night temperature' parameter. This parameter can be set from 5°C to 30°C in
steps of 0.5 degrees Celsius. By default the 'night temperature' is set to 5°C.
 The 'Night Temperature' is used by the TELETASK system as a direct threshold
for the 'heat' system. In the 'cooling' system, there is an individual 'Night' value
available. This value can be set-up between 20 and 30°C but can never be less
than the set-up Night temperature for heating plus Delta Heat/Cool.
 Cooling at night: Unlike the day/standby cool presets which are related to
day/standby heat presets via the “Delta Heat/Cool”, the “Cooling at night”
preset can be modified for each sensor zone individually without any correlation
to another preset.
 With this new preset you can for example keep the bedrooms, but not the other
rooms, cool at the night. A good compromise between comfort and energy
saving.
When selecting a humidity sensor:
 'Humidity sensor': this parameter defines the function which is to be used at the
moment that the humidity sensor function has to be executed. Depending on the
integrated function, there will be more or less parameters to be set. Refer to the
explanation of the specific functions which can be used here in the 'functions' chapter
of this handbook. These are: 'Switch', 'Dim', 'Local Mood' and 'Flags' + 'process
function'. These functions are activated, whenever there is measured a value that is
lower than the set-up value (air is too dry!) For 'Moistening' you have to reverse it by
hardware.
 'Preset 1 (=day)': this parameter defines the 'day' threshold preset which is to be
used to control the related function. This parameter can be set from 0% humidity to
100% humidity in steps of 1%. By default this preset is set to 0%. The function will be
active as soon as the actual value is below the preset value (Low Action).
 'Preset 2 (=night)': this parameter defines the 'night' threshold preset which is to be
used to control the related function. This parameter can be set from 0% humidity to
100% humidity in steps of 1%. By default this preset is set to 0%. The function will be
active as soon as the actual value is below the preset value (Low Action).
101
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
When selecting a light sensor ('dark', 'regulating' or 'sun' sensor is set):
 'Light': this parameter defines the function which is to be executed on the moment
that the sensor function is activated. Depending on the function which has been
chosen, there are more or less parameters to be set. Refer to the description of the
specific functions in the 'functions' chapter. You can choose here between the
functions 'Switch', 'Dim', 'Local Mood' and 'Flags'.
 'Preset 1 (=day)': this parameter defines the threshold for the 'day' preset. This
parameter can be set from 0 to 944060 Lux, according to a non-linear scale. By
default this sensor is set to 0 Lux.
 'Preset 2 (=night)': this parameter defines the threshold for the 'night' preset. This
parameter can be set from 0 to 944060 Lux, according to a non-linear scale. By
default this sensor is set to 0 Lux.
102
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
When selecting a non-TELETASK humidity sensor (DAIKIN, AIRZONE,
Mitsubishi Electric):
 'Properties': here is made a link between the TELETASK addresses and the
addresses of the concerned system. See the manual of the concerning TELETASK
interface/licence for more information. Here also the set-up 'Day/Night/Stand-by'
presets are similar to the TELETASK temperature sensor.
When selecting a general linear sensor/Wind sensor:
 'Settings': here you chose the type of signal, the unity which has to be used, the
precision, and the minimum and maximum values depending on the Properties of the
sensor.
 'Low action': here you can, just like for other sensors, couple a function which will be
executed when the measured value is too low.
 'Preset 1 (=day): this parameter defines the 'day' preset threshold value.
 'Preset 2 (=night): this parameter defines the 'night' preset threshold value.
103
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 In practice







Click 'Edit' in the PROSOFT menu bar.
Click 'Inputs and other'.
Select the desired analogue input interface. The selected 'I' interface turns blue.
Click the 'Edit' button. The 'Define Interface Function' window appears on the
screen.
Select the desired input on the picture of the selected analogue input interface.
Select the desired sensor and set the different parameters depending on the
needs of your project.
Click 'OK' until you are back in the main PROSOFT screen. The analogue input is
defined. Don't forget to save your work regularly. TELETASK recommends
having an incremental counter in the file name you use. This way you can easily
go back to an older version if you think you have made an error in one of your last
saved versions.
104
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.6. Audio Interfaces – Specific parameters
 The different available parameters
 'Audio Zone': the audio zone is a room or a group of rooms wherein the audio can be
listened coming from one audio power amplifier. Following to this, the volume level of
the rooms in the same audio zone are depending on each other. As soon as you have
been entering a name in the 'audio zone' field, the audio functions for this audio zone
are released for use in PROSOFT.
Audio zone example names: 'Bath room', 'Kitchen', 'Office', 'Bathroom parents and
dressing', 'bath rooms ground floor', 'outdoor', etc…
Add as much audio zones as the used audio interface is able to control. See for more
details in the data sheet of the specific audio interface.
 For TDS14042, see chapter AV-SOFT.
 In practice







Click 'Edit' in the PROSOFT menu bar.
Click 'Inputs and other'.
Select the desired audio interface by clicking on it.
Click the 'Edit' button. The 'Define Interface Function' window appears on the
screen.
Select the desired audio zone on the picture of the audio interface.
Enter the name of the audio zone.
Click 'OK' until you are back in the main PROSOFT screen. The audio zone(s) is
(are) defined now.
105
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
7.7. Overview list of 'I' Interfaces of your domotics project.
An overview list of the 'I' interfaces, the different inputs, sensors and the audio zones in your project
are easily overviewed in the different available lists. These lists are shown in the 'list interfaces'
window. Click in the main PROSOFT menu 'Edit', 'Inputs and others' and select the desired on-screen
overview list.
There are different lists which can be displayed:
 List type 'I' Interfaces:
The list contains:
This list gives you an overview of the 'I' interfaces of your TELETASK project,
conveniently arranged. In this list the next items are displayed:
 'Address': In the first part of the first column there is the software address of the
concerned 'I' interface. PROSOFT adds the letter 'I' to remark that it concerns an input
interface.
 'Group': In the second part of the first column the input interface group abbreviation is
displayed.
 'Description': the name which you have been giving to the interface.
Actions:
When the desired 'I' interface is found, you can select it and the line becomes blue
when selected. The following actions can be taken starting from this list:
 'New': Click on the 'New' button to add an extra 'I' interface to your project.
106
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 'Edit': Click on the 'Edit' button to open the 'Define Interface Function' window where
you can change the settings of that interface.
 'Copy': there will be made a copy of the selected interface. All settings, except for the
address, are kept.
 'Remove': Click to remove the interface from your project. Be careful, there is no undo
button for this action, but PROSOFT will ask for a confirmation before it is finally
removed.
 List type 'Input list'
The list contains:
This list gives an overview of the TELETASK individual digital inputs used in your
project. Next items are displayed in this list:
 'INP': this abbreviation defines that the item displayed on that line is an input.
 'Number': the input number is divided into two parts. The first part is the AUTOBUS
address of the digital input interface. The second part is the individual input number on
that input interface (for example '4' is the fourth input of 8 or 16).
 'Description': contains the name you have been giving to this individual input...
Actions:
When the desired input is found, you can select it by clicking on it and it will turn blue.
The following actions can be done after selecting the input:
 'New': to add an extra input to the project.
 It will be necessary to add a new 'I' interface here before you can add an
individual input.
 'Edit': Click on the 'Edit' button to go to the 'Define Interface Function' window to be
able to change the parameters of the individual input.
 List type 'Sensor Zone' and 'Audio Zone'
The list contains:
These two lists give you an overview of all sensors and audio zones in your
TELETASK domotics project. You can find the following information in both these lists:
107
TELETASK Handbook
PROSOFT >
“I” Interfaces: Inputs and other
 'Type': defines whether it concerns a sensor zone ('SEN') or audio zone ('AZN').
 'Number': shows the number which was given to the sensor or the audio zone.
 'Description': contains the name you have been giving to the sensor or audio zone.
Actions
When the desired sensor or audio zone is located, you can select it by clicking on it
and it will turn blue to confirm that you have selected that line. The following actions
can be done in this case:
 'New': to enter an additional sensor or audio zone.
 It will also be necessary to define a new 'I' interface here.
 'Edit': Click on the 'Edit' button to change the parameters of a sensor or audio zone.
108
TELETASK Handbook
PROSOFT >
Overview
7.8. TDS12116 Digital Input interface with Pulse counter sensor.
A typical use for the Pulse counter is the measurement of the electricity consumption/production. But
there are also meters available for gas/water consumption with a pulse output.
7.8.1. Hardware:
The meter that generates the pulses, has to be connecter to the input of a TDS12116 (Digital
Input interface). This interface has to have software version V112 or higher.
 It is not possible to upgrade older interfaces!!!
 The meter has to stay under 5 pulses per second on maximum
consumption/generation. Keep this in mind when selecting the meter.
 ‘Meter output type’: Open collector (NECESSARY) (So output).
 ‘Connection’: So+ on the input, So on the common.
 ‘Cabling’: individual shielded (same as sensors/dimmer).
7.8.2. Software:
A pulse sensor can be created in PROSOFT Suite by selecting the option “Use as pulse
counter sensor” under the selected input on the TDS12116.
By default the sensor will be generated for the measurement of electricity consumption (kWh).
To measure other units you can change the sensor type to “Other”. To change the input back
to a ‘normal’ digital input, you can change the sensor type back to “digital”.
109
TELETASK Handbook
PROSOFT >
Overview
For a kWh sensor the following parameters apply:
 ‘Unit’: enter the number of pulses that need to be measured for 1 kWh.
 ‘Decimal places’: the number of decimal units you want to display on displays and
screens.
 ‘Timebase’: Select today if you want the value displayed on your displays and
screens to be the total power consumption since midnight. Select “last 24h”, if you
want the total value for the last 24 hours displayed.
 ‘Show Real Time value’: check this option if you want to display current use instead
of total use (e.g.: kW instead of kWh).
 Rem.: charts in GUI+ always show total use, regardless the setting.
For a custom pulse teller you have to insert the units and the number of inputs per unit (e.g.:
250 imp/ m³). If “Show Real Time value” is checked, the following parameters will be added:
 ‘Real Time unit’: the unit that has to be used to display Real Time values (e.g.: L/h).
 Rem.: The Timebase has to be in relation with the unit (eg.: for L/h the Timebase
has to be “Hour”, for L/min it has to be “Minutes”).
 ‘Real time units/unit’: the number of Real Time units per Unit (eg.: 1000L in 1m³).
110
TELETASK Handbook
PROSOFT >
Overview
Regardless the type of sensor you use (kWh or others) and regardless the selected option
“Show Real Time value”, you can link a “High Action” on this sensor. This means that this
action will be executed as soon as the measured value is higher than the preset value (the
action will be reset when the measured value is below the preset value).
Possible uses are: to inform the user when too much power is used (with messages and
alarms) or to keep the power consumption within limits during high peak usage by shutting
down high consumers (eg.; electrical boilers).
 Rem.: Be aware that this “High Action” is the opposite as with light, humidity or
standard linear sensors where we speak of “Low Action”.
Like with other sensors you can define two presets (day and night).
111
TELETASK Handbook
PROSOFT >
Overview
7.9. TDS14061 HVAC Modbus Master interface
TDS14061 is an AUTOBUS interface for controlling HVAC systems. Depending on the brand
and the specific unit(s), the interface can be configured to integrate up to 64 indoor units.
The TDS14061 requires communication over Modbus to a Modbus Slave interface:
TDS20061xx, TDS20062xx or TDS20063xx in order to control the HVAC system. The
interface is suited for controlling specific VRV/VRF and residential split units.
 Remark: In case that local wired remote controllers are installed in the system and they
are all located in one central place, make sure that the HVAC system uses the room
temperature measured by the indoor units and not the room temperature measured by
the local wired remote controllers.
112
TELETASK Handbook
PROSOFT >
Overview
7.9.1. Adding a HVAC Modbus Master interface to the Interfaces list.
 Bring up the Interfaces List and click on ‘New’.
 Select ‘TDS14061’ from the list as shown on the figure below.
113
TELETASK Handbook
PROSOFT >
Overview
7.9.2. Modbus Slave interface selection
 Select the correct Modbus slave type:










TDS20061DA:
TDS20061SY:
TDS20061TO:
TDS20061ME:
TDS20061HI:
TDS20061PA:
TDS20062MH:
TDS20062LG:
TDS20062SS:
TDS20063FU:
for DAIKIN HVAC systems
for SANYO HVAC systems
for TOSHIBA HVAC systems
for MITSUBISHI ELECTRIC HVAC systems
for HITACHI HVAC systems
for PANASONIC HVAC systems
for MITSUBISHI HEAVY HVAC systems
for LG HVAC systems
for SAMSUNG HVAC systems
for FUJITSU HVAC systems
114
TELETASK Handbook
PROSOFT >
Overview
7.9.3. Configure the AUTOBUS Address
 Select AUTOBUS number and set the interface AUTOBUS address.
7.9.4. Configure Modbus Slave interface
 Add the HVAC indoor units by clicking the ‘Add’ button.
115
TELETASK Handbook
PROSOFT >
Overview
For each indoor unit, a sensor has to be added to the list, configure the following
settings:
 Sensor Type: Modbus Sensor by default
 Sensor Name: This can be a free chosen name. Normally this name should represent
the location(zone) of the indoor unit.
Indoor unit properties
 HVAC group nr & HVAC zone nr: This represents the HVAC indoor unit address.
This setting must be the same as the address which was configured manually on the
HVAC indoor unit in that zone by the HVAC technician.
 Remark: Contact the HVAC technician to find out which HVAC address is given to
each indoor unit in the HVAC system.HVAC resolution: See Chapter ‘Extra
parameters for External HVAC systems’.
Mode & Speed: See Chapter ‘Extra Parameters for External HVAC Systems’
 If everything is set correctly, press ‘OK’.
116
TELETASK Handbook
PROSOFT >
Overview
7.10. TDS14065 : IR-COOKIE INTERFACE
7.10.1. TDS14065: IR-COOKIE INTERFACE (HVAC AND A/V
CONTROL)
The text below describes how you can configure the IR-COOKIE interface in PROSOFT
(starting from version 3.6.12.0).
If you are going to configure an IR-COOKIE for the first time, it is recommended to check
TELETASK SCHOOL for the IR-COOKIE training movie (part of “Skilled” trainings).
7.10.2. INTRODUCTION
The IR-COOKIE interface is an AUTOBUS connected interface which can transmit IR signals
to its IR-flasher (supplied with the unit) which can be used to control a single HVAC unit or
Audio/Video device. While the HVAC control has only one function with one or more modes
(cool and/or heat, ventilation, dry), the controlled A/V device may be a device with one or more
internal sources (amplifier with built-in tuner for example).
The IR-COOKIE can learn the necessary IR commands through its built-in IR-receiver.
Asking to transmit one or more IR-codes can be done from any TDS input like a momentary
push button (on a contact input), touch panel, touch screen, clock action (see TIMESOFT),
mobile device like a smart phone, etc.
7.10.3. CONFIGURATION
The IR-COOKIE configuration is done in three main steps:
1. You need a connected IR-COOKIE.
Connect the interface to a DoIP central unit and connect with the PROSOFT PC
(via wired or wireless LAN connection).
2. Record (=learn) the IR-COOKIE its IR-codes (see details in the next chapter
below).
Info: All recorded IR-codes are stored in the PROSOFT – IRDB library. You can
later re-use these codes in your other projects.
117
TELETASK Handbook
PROSOFT >
Overview
BACKUP: It may be important to make a backup of these codes by exporting the
IRDB file to your personal protected backup location (may be on a cloud server).
If you start a new project on another PC, you can then import the IRDB file.
3. Now configure the triggering devices (buttons, touch panels, …) to activate the IRCOOKIE to send one or more IR codes to the target device (HVAC or A/V).
TT SCHOOL: It is also very useful to learn the details via the TT SCHOOL movie “IR-COOKIE”
(part of the skilled trainings).
7.10.4. RECORD (=LEARN) THE IR-CODES (HVAC APPLICATION)
Open PROSOFT. Make sure that you are connected with the central unit and an IR-COOKIE
interface is connected to the AUTOBUS.

Now add the IR-COOKIE to the (existing) configuration (Edit menu > Inputs etc >
New > TDS14065).

Now add a new device (your HVAC split unit): (if not yet existing in your library)

Now define the properties of the HVAC unit which you want to control (see screen
capture below):
118
TELETASK Handbook


PROSOFT >
Overview
Enter the Brand name, Type reference, optional comments (like model year etc.)
and select the HVAC modes which are supported by the device. Only select the
ones you really want to use because selecting all (Heat, Cool, Ventilation and
Dry) will need a high number of IR-codes to be recorded. In most cases you may
only need “Cool” and optional “Heat” modes.
Now select the number of speeds of the HVAC device fan (most cases you will
have 3: Low, Medium and High speed).
 Remark: The new device you need to enter is more about the remote
control than about the HVAC device. A remote control can be the same for
different HVAC devices. So if you have the remote control information, use
this as the device name. We recommend to add the HVAC device
information in the comment field in such case.
 Remark:
1. For heating you can record temperature settings between 16 and 25°C.
2. For cooling this is between 21 and 30°C.



If your HVAC unit supports Auto speed mode, select the item (duplicates the
number of IR-codes to be recorded).
If swing control is supported, select the item (again duplicate the number of IRcodes to be recorded).
Click ‘OK’ to get the recording screen.
You can record the IR-CODES one by one, but for all temperature related commands (most of
them are) use the batch record which works much faster (see also the TT SCHOOL training
movie on IR-COOKIE).
119
TELETASK Handbook
PROSOFT >
Overview
Before you start recording, PROSOFT needs to have access to the IR-COOKIE which you
want to use for the recording. Therefore, PROSOFT has already searched for such IRCOOKIE on his AUTOBUS. On the screen capture above you can see that in this case an IRCOOKIE was found on address 10 (AUTOBUS 1).
If you want to use another IR-COOKIE, change the address setting accordingly.
Now select the first IR-code you want to record (‘OFF’) and click ‘Record code’ or ‘Batch
record’. Batch record is very useful but only to be used for codes with increasing temperatures
like all ‘cool…’ codes in the screen capture above.
 IMPORTANT REMARK: If your HVAC remote control doesn’t have a specific ‘OFF’
button but an ‘ON/OFF’ button, it means that you will never know in which status your
HVAC unit will come when activating a command to it. So you can’t use it in a mood like
‘leaving the house’. If you activate this mood and you send the ‘ON/OFF’ command, the
device will go ON if it was already OFF before. And that is not what you want.
Now you get the record screen. On top, you see the code you are to record and the green
record bar starts running. Now click the appropriate (in this case “OFF”-) button on your IRremote control of the HVAC device.
Remark: Your remote control should be faced to the IR receiver in the IR-Cookie interface
(distance 20 cm to 3 meter).
Once the IR-COOKIE has detected the end of the code, the code is checked and stored in to
the IRDB library.
120
TELETASK Handbook
PROSOFT >
Overview
Below on the screen you get a picture of the code construction. You don’t have to do anything
with that, but if the code would look erroneous, we recommend to record it again.
 Remark: In exceptional cases, you may like to cut the tail of the recorded code.
Therefore, you can go with you mouse pointer over the code signal picture and cut the
part behind your mouse pointer by clicking the left mouse button.
7.10.5. Batch recording:
For the temperature codes:
 Select the first code you want to record
 Make you IR remote control ready with the appropriate settings (in our capture
this is Cooling mode, temperature set to 20°C (first T minus 1°C) and fan speed
on LOW)
 Click Batch record
 Press the space bar to record the code and you click the Temperature-up button,
so the remote control transmits the settings for 21°C as the first IR-code.
 Then do the remaining other T-settings one by one by clicking the space bar.
PROSOFT will automatically ask for the next setting. Click space bar when you
are ready, etc…
121
TELETASK Handbook






PROSOFT >
Overview
After all codes are recorded, click ‘OK’ and the new device is added to the device
list.
Click ‘OK’ again to go into the IR-COOKIE configuration screen.
Enter the proper AUTOBUS address as will be used in the final installation (don’t
forget to change also the address setting on the IR-COOKIE if necessary)
Set the Sensor type to ‘IR-COOKIE temperature zone’ and give it the proper
name (the room of the AC device).
Optional: Set the day and night temperatures if you want them to be different then
default. The stand-by temperatures (you can call this ‘eco’ setting) are
automatically set based on the Stand-by preset (2°C is recommended). For
Heating this is Day minus the Stand-by T° and for Cooling this is Day plus the
Stand-by T°.
Click ‘OK’ to finalize this configuration.
If you have more IR-COOKIE interfaces in this project, do the same last configuration part for
all other IR-COOKIE interfaces. Be sure that every IR-COOKIE interface needs to have a
different AUTOBUS address.
Now you are ready to use the Temperature functions on your touch panels, screens, input
interfaces, smart phones, etc…
7.10.6. USING THE IR-COOKIE ON BUTTONS, TOUCH PANELS,
MOOD’S, …
As temperature settings and control most often needs feed-back on a display, we recommend
to have each temperature zone defined on at least one touch panel with display. For example,
on a AURUS-OLED or AURUS-TFT.
The AURUS-OLED and TFT have also the advantage that you can control all temperature
zones from only one unit (if you like).
See more details and examples in the TELETASK SCHOOL training movie on IR-COOKIE
(part of Skilled trainings).
 Important to remember: it is not possible to see the ‘measured’ temperature from an IRCOOKIE zone, as the temperature is just not available from the connected AC unit. The
IR signal is one directional. It can only transit to the AC unit and not receive from it.
122
TELETASK Handbook
PROSOFT >
Overview
At the other hand if you have a TELETASK temperature sensor in that room, you can
visualise it on your AURUS-OLED, AURUS-TFT and other display interfaces like iSGUI
and GUI+.
7.10.7. A/V INTEGRATION WITH THE IR-COOKIE INTERFACE
In an A/V application, add the IR-COOKIE in AV-SOFT (part of the PROSOFT Suite) first.


Enter ‘NEW’ and select the TDS14065 interface + ‘OK’.
Add an IR-flasher by clicking ‘Add Device’. You can assign one or more devices
to that flasher. You can Add a new device and record the IR-codes of that device
(see movie TELETASK SCHOOL IR-COOKIE for more details). We can also
recommend to learn to work with AV-SOFT first before you proceed.

If you want to control an audio unit which is amplifier with built-in tuner source,
you can now learn the IR-codes for both your amplifier and the internal tuner
source.
The IR-code learning process is the same as in the above text for a HVAC
device.

 IMPORTANT REMARK: If you’re a/V remote control doesn’t have a specific
‘OFF’ button but an ‘ON/OFF’ button, it means that you will never know in
which status your HVAC unit will come when activating such command to
it. So you can’t use it in a mood like ‘leaving the house’. If you activate this
mood and you send the ‘ON/OFF’ command, the device will go ON if it was
already OFF before. And that is not what you want.

If you have existing IR-codes from the IR-learnable interface TDS14042, you can
copy these codes to use them with the IR-COOKIE without the need to re-record
them.
123
TELETASK Handbook


PROSOFT >
Overview
Just select the existing device and click ‘Copy’
Now select “TDS14065” instead of “TDS14042” and rename the device type (add
for example ‘for IR-COOKIE’ instead of ‘COPY’).
The remaining part is the same as for using any device in AV-SOFT. See AV-SOFT training.
Remark: Before you are able to control the audio system which is connected to the IRCOOKIE, you need to tell the TDS system for which room this audio device is used for (=
audio zone). Therefore, go to PROSOFT top menu ‘PROSOFT’, go to ‘rooms’ and select your
room and select the specific audio zone in the ‘audio zone’ field.
Now you can use audio functions on any TDS buttons (contact input), touch panel, touch
screen, mobile device, but also as part of a mood.
e.g. mood ‘coming home’, ‘leaving’, ‘party’ or ‘going to bed’ are typical moods where HVAC
and or A/V actions may be taken together with other actions like light control or other.
We hope you will enjoy your new IR-COOKIE(s).
7.10.8. VRF/VRV INSTEAD OF IR-FLASHER CONTROL
If you need more than an IR-flasher solution, you may like to have bi-directional management
of high-end HVAC devices. You can select one of the many other HVAC interfaces available
from TELETASK. These are specifically made for integration with VRV/VRF systems. See
HVAC Master/slave interfaces for more details on the brands and types which are supported
by TELETASK.
124
TELETASK Handbook
PROSOFT >
Overview
7.11. TDS15200 Airco Software license
The TDS15200 is a TELETASK license for full integration with an Air-conditioning system, this license
is the same for different Air-conditioning brands (Daikin, Mitsuhishi Electric). The integration is
possible with the DoIP system, this means that the TELETASK central unit and the controller of the air
conditioner system are connected over Ethernet.
For full use the TDS15200 license needs to be activated. For test or demo purposes this license can
be used in ‘TEST Mode’ for three days.
The TDS15200 can be used to integrate with an “Intelligent gateway” to the AC system. This means
that the temperature measurement is done by the Airco system. The TELETASK DoIP central unit
reads the measured temperatures from the gateway, and sends the desired temperature, mode and
speed settings to the gateway, which controls the different zones.
The AC can be controlled on both the AC system and the TELETASK system.
A schematic drawing of the integration is given below:
7.11.1. Daikin Integration
The Integration with the DAIKIN AC system is done with the Daikin ‘intelligent Touch controller’
(iTouch, DCS601C51).
For the iTouch with software version 4.30.01R you need also the ‘Daikin Intelligent Touch
Controller Web Software License’ (DCS004A51).
If you use a iTouch with version 4.41.00 or higher you need the ‘Daikin Open Protocol License’
(DCS007A51)
Up to 128 DAIKIN indoor units can be controlled with a Daikin iTouch. So in PROSOFT Suite
an extra 128 sensor zones are available accordingly.
All Daikin systems that can be controlled from the iTouch can be integrated with the
TELETASK system e.g. Daikin VRII, Daikin VRIII, Daikin SKY AIR, Daikin HRV,…
 Remark: some Daikin systems need optional plug in boards to connect them with the
iTouch, connect your Daikin supplier for detailed information.
 Remark: not all Daikin units are 100% compatible with iTouch.
125
TELETASK Handbook
PROSOFT >
Overview
 Remark: Daikin touch panels need to be installed to ensure normal operation of the
HVAC installation.
 Configuring a Daikin Interface in PROSOFT Suite
To add a DAIKIN interface to your TELETASK system, follow these steps:
 In PROSOFT Suite, go to the menu "Edit", "Inputs"
 Choose "New", "Sensor or Heat/Cool Interface"
 Select "DAIKIN interface" from the list of interfaces
 Enter the correct IP address and IP port number of the Daikin iTouch unit
 Add all the indoor units as used in the DAIKIN iTouch unit and give each zone the
correct DAIKIN zone number and name (we advise to use the same names in
iTouch and PROSOFT Suite).
 Set the HVAC resolution: see Chapter ‘Extra parameters for external HVAC
systems.
 Mode & Speed: see Chapter ‘Extra parameters for external HVAC systems.
 Enter the presets for "Day", "Night" and "Standby"
 Save your .nbt file
 Transmit the nbt file to your central unit
126
TELETASK Handbook
PROSOFT >
Overview
7.11.2. Mitsubishi Electric Integration
 Remark: There are two different Mitsubishi Air-conditioning brands on the market:
‘Mitsubishi Electric’ and ‘Mitsubishi heavy Industries’. Only the ‘Mitsubishi Electric’ Airconditioning can be integrated with the TELETASK system.
The integration with the Mitsubishi Electric air-conditioning system is done with the
MITSUBISHI Electric Ethernet gateway AG150 or GB50.
With both these devices 50 zones can be controlled, so an extra 50 zones are available in
PROSOFT Suite.
 Configuring a Mitsubishi Electric Interface in PROSOFT Suite
 To add a Mitsubishi Electric interface to your TELETASK system, follow these steps:
 In PROSOFT Suite, go to the menu "Edit", "Inputs"
 Choose "New", "Sensor or Heat/Cool Interface"
 Select "Mitsubishi Electric interface" from the list of interfaces
 Enter the correct IP address and IP port number of the Mitsubishi Electric
Ethernet Gateway.
 Add all the indoor units as used in the Mitsubishi Electric Ethernet Gateway and
give each zone the correct Mitsubishi Electric group number and name.
 Set the HVAC resolution: see Chapter ‘Extra parameters for external HVAC
systems.
 Mode & Speed: see Chapter ‘Extra parameters for external HVAC systems.
 Enter the presets for "Day", "Night" and "Standby"
 Save your .nbt file
 Transmit the nbt file to your central unit
127
TELETASK Handbook
PROSOFT >
Overview
7.12. Extra Parameters for External HVAC systems
7.12.1. Indoor unit properties
 HVAC resolution: Depending on the type of HVAC indoor unit, the temperature
resolution can be set to 0,5°C or 1°C.
7.12.2. Mode & Speed
 HVAC operation modes: Select the supported Modes.
 Remark: For some systems, if one zone is selected in one particular operating
mode, all other zones will go to this operating mode. Contact the HVAC supplier
for more information about the possible operating modes and their options.
 External HVAC system supports ‘auto mode’: select this if the HVAC system
supports auto mode
 Remark: This option is only enabled if ‘auto mode’ is enabled in ‘extra’,
‘settings’, ‘Sensors’
 HVAC fan speed settings: Select the number of Fan speeds supported by the HVAC
indoor unit.
 Select checkbox ‘External system supports ‘auto fan speed’: select if the HVAC
system supports auto speed.
 Remark: Contact the HVAC technician or HVAC supplier or HVAC manufacturer
for the number of Fan speeds that are supported by the indoor unit.
7.12.3. Preset Temperature settings:
See Sensor Heat/Cool interface – Specific parameters.
128
TELETASK Handbook
PROSOFT >
Overview
8. Functions overview
8.1. The Relay functions
 Description
Relay functions modify the status of a relay between on and off. When somebody
pushes a button, the connected relay is switched (the status is changed from OFF to
ON or if already ON it is changed to OFF).
 The functioning of an interface:
 'Relay': this parameter defines the relay which is being switched by this function.
Option 'Switch On/Off' (standard)
 'Short': with a short push the relay is being switched. In particular this means that the
light switches ON when it was OFF and vice versa.
 'Long': with a long push the relay is being switched. In particular this means that the
light switches ON when it was OFF and vice versa.
Option 'Switch On'
 'Short': with a short push the relay is being switched on. In particular this means that
the light switches ON.
 'Long': with a long push the relay is being switched on.
Option 'Switch Off'
 'Short': with a short push the relay is being switched off. In particular this means that
the light switches off.
 'Long': with a long push the relay is being switched off.
129
TELETASK Handbook
PROSOFT >
Overview
 Behaviour when the function is used in another function
'Relay' type




When the relay is called from another function, the functioning depends on the set
target value. Following possibilities can occur:
'On': the relay switches ON when it was OFF and remains switched ON when it was
switched ON.
'Off': the relay switches OFF when it was switched ON and remains switched OFF
when it was switched OFF.
'On/Off': the relay switches ON or remains switched ON when activating the function
and switches OFF when the function is switched OFF.
'Off/Off': The relay switches OFF and remains switched OFF when the function is
switched ON. If the function is switched OFF, then the relay remains switched OFF.
 Not every function can be switched off. Consult for this matter the description
of the respective function.
 General Remarks
 If the function is used from an interface or from another function, if the direction
relay of a motor function is activated, then the respective motor function is
being executed. Consult the description of the motor function for more
information.
 If several relays are being switched simultaneously, then the central unit will
switch the different relays consecutively with an adjustable time delay between
the two actions. This time delay is adjustable in the 'Extra' 'Options' 'Specials'
'Relays delay' menu and is set by default to 50 msec.
8.2. The Dimmer functions
 Description
The dimming functions modify the status of the dimmer output between 0% (= 0V =
off) and 100% (= 10V = on) or an intermediate value
130
TELETASK Handbook
PROSOFT >
Overview
 The functioning of an interface:
 'Dimmer': this parameter defines the dimmer which is being controlled by the function.
Type 'Switch between LAST level/OFF'
 'Short': after a short push on the button, the dimmer will switch between 0% and the
last active status of the dimmer. When the light is burning at 40%, then with a short
push the light will go out (dimming to 0%). Again short pushing switches the light to
40%.
 'Long': functioning is identical to 'Short'.
 Under 'Long' this function is seldom used, only if due to lack of buttons from
one and the same button 2 dimmers can be controlled
Type 'Switch between: put level/OFF':
 'Short': after a short push on the button, the dimmer will switch between 0% and a
predefined state of the dimmer.
 'Long': working identical to 'Short'.
Type 'Define Level':
 ‘Short’: The dimmer will be switched to the predefined level.
 ‘Long’: working identical to 'Short'.
Type 'Define last level':
 ‘Short’: the dimmer will be switched to the last level when the dimmer is out.
 ‘Long’: working identical to 'Short'.
Type 'Define last level/100%.'
 ‘Short’: the dimmer will be set on the last level, when the dimmer is out. Otherwise the
dimmer will be set to 100%.
 ‘Long’: Working identical to 'Short'.
 This is usable when controlling a dimmer on the TDS12022 AURUS-OLED or
TDS12032 AURUS-OLED PLUS. See chapter AURUS-OLED (PLUS) for more
information.
'Continuously dimming' type
 'Short': This function type cannot be selected under 'Short'.
 'Long': when long pushing on the button, the dimmer will make a continuous linear
movement between 0% and 100%. With this function the light intensity can be
adjusted completely to your needs.
 When you are selecting under 'Short' a 'Switch between LAST level/OFF' type
for a particular dimmer, PROSOFT automatically selects under 'Long' the
131
TELETASK Handbook
PROSOFT >
Overview
'Continuously dimming' type for that dimmer. If afterwards the selected dimmer
is being modified under 'Short', then the dimmer will follow under 'Long'.
 If you want to operate another function under 'Long' then this automatic
suggestion can always be modified. Thus the automatic following is cut off.
'Dimming Up' type:
 'Short': This function type cannot be selected under 'Short'.
 'Long': when pushing long on a button, the dimmer will increase from the active status
till 100%.
'Dimming Down' type:
 'Short': this function type cannot be selected under 'Short.
 'Long': when pushing long on a button, the dimmer will decrease from the active
status till 0%.
 For optimal ease of use it is recommended to control only one dimmer for each
button.
 When the dimmer output has been set on a small value (smaller than 10%), then
when being reactivated with a short push, your TELETASK domotics system,
will set the status of the dimmer automatically at 10%. From this value on most
light points are softly lit, so that the 'on' status is visible.
 Behaviour when the function is used in another function
 'Target Value': this parameter defines the desired dim status. The Parameter can be
set from 0% till 100%. The target value is standard set on 100%. Following settings
are possible:
 ‘xx'%': when a function is activated the dimmer will go to the set target value (0100%).
 'xx'%/Off': when a function is activated the dimmer will go to the set target value
(0-100%). When the function is switched off the dimmer goes out (0%).
 Not every function can be switched off. Consult for this matter the
description of the respective function.
 Parameters
 'Fade in': this parameter defines the needed time to bring the dimmer output from 0%
to 100%. The 'Fade in' can be set on 16 fixed predefined times: 0,5 sec;1 sec; 2 sec; 3
sec; 4 sec; 7 sec; 10 sec; 15 sec; 30 sec; 1 min;2 min; 5 min; 15 min; 30 min; 1 hour.
Standard 'Fade in' is set on 1 sec.
 'Fade out': this parameter defines the needed time to bring the dimmer output form
100% to 0%. The 'Fade out' can be set on 16 fixed predefined times (identical to 'Fade
in'. Standard 'Fade out' is set on 3 sec.
 At an increase towards the desired status the dim speed is calculated in
accordance with the set 'Fade in': The dim speed amounts to 20% of the 'Fade
in' when the difference between the desired and the active status of the dimmer
is 20%.
132
TELETASK Handbook
PROSOFT >
Overview
 At a decrease towards the desired status the dim speed is calculated in
accordance with the set 'Fade out': The dim speed amounts to 20% of the 'Fade
out' when the difference between the desired and the active status of the
dimmer is 20%.
8.3. Working with motors
Motors can be controlled in two different (electrical) ways:
1. You can use a standard motor interface TDS13525 or TDS13526 (with internal
preconfigured “motor function”). See all details below in the chapter ‘Motor interfaces’
2. Make your own ‘motor function’ which will control standard output relay contacts. In this
case you only use output contacts from a MICROS+, PICOS or from TDS13510 – 13512
interfaces. Depending on the application, there may be 1, 2 or 3 relay contacts needed.
See all details below in the chapter 'motor function'.
8.3.1. Motor interfaces
Only applicable for TDS13525/TDS13526 - not for use with separated relay contact
outputs; in this case see next chapter.
 Description
The motors are used to control AC and DC motors as used in indoor/outdoor electrical
curtains, shutters, drapes, sun blinds, screens, etc…
The function can control the motor rotating left, right and in stop position. This
paragraph considers the Motors which are controlled by a Motor Interface (TDS13524,
TDS 13525, TDS13526). For Motors controlled by 1 to 3 independent relays, please
consult 'the motor function'.
 The different available parameters
Within the function:
133
TELETASK Handbook
PROSOFT >
Overview
 'Name Outputs': The name giving of a 'Motor' function is separated in 3 parts:
 'Room': The room where the motor is situated.
 'Icon': Not visible or Motor icon.
 'Name': Introduce here a short and clear description of the Motor function
(preferable max. 7 characters).
 ‘Settings’: In the settings tab you can select the type of motor, e.g. roller blinds,
curtains,.. controlled by the motor output. By selecting the type of motor some settings
will be automatically assigned. E.g. for a roller blind 0% will be set to ‘UP’ for a curtain
this will be ‘open’. Other settings on this tab page are:
 ‘0%’: a text to display for the ‘OPEN/UP’ position of the motor and an arrow to
display for running towards that position
 ‘100%’: a text to display for the ‘CLOSED/DOWN’ position of the motor and an
arrow to display for running towards that position.
 ‘Runtime 0% -> 100%’: The time the motor needs to run from its 0% position to
its 100% position.
 ‘Runtime 100% -> 0%’: The time the motor needs to run from its 100% position
to its 0% position.
 Set the runtimes as precise as possible. This will improve the
feedback/positioning of the motor. When running to the 0% or the 100%
position, the system will add an extra time to make sure that the motor
reaches its end position.
 For TDS13526 the runtimes can be auto-calibrated using ‘Diagnostics’ for a
more precise feedback/positioning.
 Max. runtime is 250s.
 ‘Total slat time’: (only available for ‘slatted’ motor types e.g. ‘Venetian blinds’).
The total time for the slats to rotate from its ‘up’ position to its ‘down’ position.
 ‘Advanced’: the following settings are available on this tab page
 ‘Invert motor direction’: Check this option to revert the direction of the motor.
 ‘Automatically adjust run times’: only available on interfaces that support ‘run
detection’(TDS13526). Check this option to automatically adjust the runtimes over
time (e.g. when motors start running slower due to wear).
 ‘Position indication’: select whether the positon must be displayed for ‘all
positions’, ‘only 0 and 100%’ or that the position must not be displayed.
 ‘Pre run 0%’: only available if the ‘position indication’ is set to ‘all positions’.
Select the time for the motor to run from 0% to 1% (or from 1% to 0%). E.g. if
blinds are mounted higher than the top of the window.
 ‘Post run 100%’: only available if the ‘position indication’ is set to ‘all positions’.
Select the time for the motor to run from 99% to 100% (or from 100% to 99%).
E.g. for a roller shutter it may take some time to stack the bars.
 ‘Limit standard UP/DOWN between’: only available if the ‘position indication’ is
set to ‘all positions’. Here you can define a limit for the UP (or OPEN) and the
DOWN (or CLOSED) position. The feedback will change to ‘UP’ or ‘Down’ when
this position is reached. E.g. for American stores.
 Remark: These UP/DOWN limits can be overruled with a ‘Motor go to
position’ function. This can be useful for cleaning purposes.
 ‘Sun Function’: On the sun function tab there are settings to automate the motor in
relation to the sunlight.
 ‘Condition to activate sun function’: a function that must be ‘TRUE’ to activate
the sun function.
 ‘Sun function motor position’: the position the motor will go to when the
condition is true.
 ‘Action delay’: default 5 minutes. A delay between the moment the ‘Condition’
became true (or false) and the moment when the sun function will be activated (or
deactivated). Use this delay to avoid that the sun function gets activated (or
deactivated) if the condition is only true (or false) for a brief period.
134
TELETASK Handbook
PROSOFT >
Overview
 ‘Minimum hold time’: default 20 minutes. A minimum delay between the
activation and deactivation (or vice versa) of the sun function. Use this function to
avoid that the sun function will be activated-deactivated repeatedly because the
condition changes frequently.
 The user can always control the motor manually when the sun function is
activated. Depending on the setting (PROSOFT options > Motors tab), the
sun function operation will be overruled if manually controlled by the user
for the rest of the day, or the sun function operation will resume after the
‘Minimum hold time’.
 If the ‘Sun function motor position’ is set to less than 100% (e.g. 75%) the
sun function will not start the motor if the motor is in a higher position (e.g.
85%).
 ‘Wind Protection’: On the wind protection tab there are settings to protect the motor
(of outdoor screens/blinds) against damage from wind. This can also be used for rain
protection.
 ‘Condition to activate the wind protection’: a function that must be ‘TRUE’ to
activate the wind protection.
 ‘Wind protection motor position’: the position the motor will go to when the
condition is true.
 ‘Minimum hold time’: default 30 min. The time the condition must be false to
deactivate the ‘Wind protection’.
 The wind protection is activated immediately when the condition becomes
true, to avoid damage to the blinds.
 The user cannot control the motor when the wind protection is activated
and the wind condition is TRUE (too much wind).
 IMPORTANT: Never set a motor that is in front of a door to the ‘DOWN’ or
‘CLOSED’ position for wind protection, as this may be a safety risk to the
people in the house (e.g. in case of a fire).
 ‘Limit switches’: on this tab page, inputs can be selected as feedback from limit
switches for this motor (typically for contacts used in the frame of a gate, garage door
system, …)
 ‘Limit switch 0%’: the digital input signal for 0%
 ‘Limit switch 100%’: the digital input signal for 100%
 Working from a touch panel button (or digital input)
 REMARK: for some options, PROSOFT will replace the ‘0%’ and ‘100%’ with the
text entered in de ‘settings tab’ of the motor interface. E.g. the option ‘Go
towards 0%’ will be called ‘Go towards UP’ or ‘Go towards OPEN’ or ….
Option 'START/STOP'
 'Short press': If the motor is running the motor will stop. If the motor is in a stationary
position, the motor will start to run in the opposite direction of its last run (if the last
run of the motor was towards the ‘100%’ position, the motor will start to run to the ‘0%’
position).
 'Long press'': working identical to 'Short press'.
Option ‘Go towards 0%'
 'Short press'': If the motor is running towards ‘0%’ the motor will stop. If the motor is
in a stationary position, or running towards 100%, the motor will start to run towards
the ‘0%’ position.
 'Long press'': working identical to 'Short press '.
Option ‘Go towards 100%’
 Similar to ‘Go towards 0% but inversed direction.
Option ‘Go to position’.
135
TELETASK Handbook
PROSOFT >
Overview
 'Short press'' Depending on the selected value this function will toggle the motor
between ‘a set position and 0%’ or between ‘a set position and 100%’. If the motor is
at the ‘0% position’ (or the ‘100% position’), the motor will go to the given position.
Otherwise the motor will go to the ‘0% position’ (or the ‘100% position’) (regardless of
whether the motor is running or not).
 'Long press'': working identical to ‘Short press’.
Option 'START/STOP continuous'.
 'Short press'' this type of function is not available under 'Short'.
 'Long press'': the motor will be activated reverse to the last executed direction. The
motor will keep running as long as the button is pressed. When you release the
button, the motor will be switched off.
 If the motor output is a ‘slatted type’ (e.g. venetian blinds), the motor will be
activated/deactivated repeatedly for short periods of time to allow the user to
precisely position the slats.
Option 'Go towards 0% continuous'
 Operation is similar to ‘START/STOP continuous’ but the motor will always start
towards 0%
Option 'Go towards 100% continuous'.
 Similar to ‘Go towards 0% continuous.
Option ‘Sun function’.
 ‘Short press’: Switches the sun function ON or OFF (this will not activate the motor
immediately. Depending on the status of the condition the motor may be activated
after the ‘action delay’)
 'Long press'': working identical to ‘Short press’.
 Function behaviour when used in another function
'Motor START/STOP' type
The action of the motor depends on the target parameter:
 ‘Start/Stop’: if the function is activated the motor will start in the opposite direction as
its last run direction. If the function is deactivated the motor will stop.
 'xx%': The motor is active for the given percentage of its runtime. The direction will be
the opposite of its last run.
 The ‘xx%’ target value is only selectable with a non ‘Toggle’ function.
 When the 'Local mood' controls several motors, with start/stop the direction will
be set by the first motor. All following motors will be activated in the same
direction.
'Motor Go to position' type
The action of the motor depends on the target parameter, not all target parameters are
available in all functions.
136
TELETASK Handbook
PROSOFT >
Overview
 'xx%/0%': The motor will go to the given position when the function is activated. When
the function is deactivated the motor will go to the 0% position.
 'xx%/100%': The motor will go to the given position when the function is activated.
When the function is deactivated the motor will go to the 100% position.
‘Set slat position' type
 ‘Set slat position’: only for slatted types. When the function is switched on, the slats
will go to the given position. When the function is deactivated the slats will go to 0%
 If you create a Local mood with a ‘Motor Go to position’ followed by a ‘Set slat
position’ and if this motor is controlled by a TDS13526, it will first complete the
first action, followed by the second. In other cases, you need to use a timed
local mood and add a long enough delay to perform the second action.
‘Sun function’ type
 ‘Sun function’: the operation is similar to the ‘Sun function’ operation from a button.
 Not every function can be switched off. Consult for this matter the description
of the respective function.
137
TELETASK Handbook
PROSOFT >
Overview
8.3.2. The Motor function
Not for TDS13525 – TDS13526. In this case see chapter above.
 Description
A motor function is used to control an AC or DC motor of e.g. electrical sun blinds,
curtains, shutters, … with standard relay output contacts (PICOS, MICROS+,
TDS13510, TDS13512, …). This paragraph considers the motors which are controlled
by 1 to 3 independent relays, but there are a lot of similarities with motors controlled
by a motor interface.
 Parameters.
 'Name', ‘Room’, ‘Icon’: the same as for Motor interfaces.
 ‘Output type’: this defines how the TELETASK relays are wired to the actual motor,
there are four types (for details on the different types see further in this chapter):
 ‘2 Relays (direction and power)’
 ‘2 Relays (up and down)’
 ‘3 Relays (up, down and stop)’
 ‘1 Relay (start, stop)’
 ‘Settings’: similar as for ‘Motors’, but slatted types are not supported for motor
functions
138
TELETASK Handbook
PROSOFT >
Overview
 ‘Advanced’: similar as for ‘Motors’, but ‘invert direction’ and ‘adjust runtimes’ are not
supported for motor functions.
 ‘Sun function’: similar as for motors
 ‘Wind protection’: similar as for motors
 ‘Limit switches’: similar as for motors
 Different output types
 ‘2 Relays (direction and power)’: this output type can be used to control an AC or
DC motor without internal driver electronics. The direction relay switches an external
change over (or double change over) relay. The power relay connects or disconnects
the motor from the power supply (see schematics of the motor unit).
 ‘2 Relays (up and down)’: this output type can be used to control motors with internal
driver electronics. When the motor needs to run up (or down) the UP (or down) relay is
switched ON. When the motor needs to stop the relay is switched off.
 ‘3 Relays (up, down and stop)’: this output type can be used to control motors with
internal driver electronics. When the motor needs to run up (or down) the UP (or
down) relay is pulsed (for 1.5s). When the motor needs to stop the ‘Stop’ relay is
pulsed.
 ‘1 Relay (start/stop)’: (not recommended because of lack of feedback information)
this output type can be used to control motors with internal driver electronics. When
the motor needs to start or stop, the relay is pulsed. This method is typically used for
motors that are also controlled by external remote controls (garage doors and gates).
This method only allows the basic ‘start/stop’ operation and the system does not know
in which direction the motor will start.
 For a motor with internal driver electronics, the preferred ‘output type’ to use is
the ‘2 Relays (up and down) because it is the most reliable and precise method.
The ‘3 Relays (up, down and stop)’ is also a reliable method but it may be less
precise (and it requires an extra relay). If possible, avoid the ‘1 Relay (start/stop)
method’ (but for low cost garage doors and gates it is sometimes the only
supported method).
 Function behaviour
The working is identical to the working of the Motor interface, with exception of the ‘set
slat position’ as this is not supported for the motor function.
139
TELETASK Handbook
PROSOFT >
Overview
8.4. The Fans:
 Description
The Fans are used to control multi speed fans like ceiling sweep fans, etc…
The function can control the fan speeds with a maximum of 4 speed (+OFF). This
paragraph considers the Fans which are controlled by a Fan Interface (TDS13522).
For Fans controlled by independent relays, please consult 'the fan (Ceiling sweep)
function'.
 The different available parameters
Within the function:
 'Name Outputs': See chapter ‘Assigning TELETASK Outputs’.
 ‘Speeds’: This determines the number of speeds available for this fan. Must be
compatible with the capacitor(s) of the fans supplied by the vendor of the fan. There
are 1 speed (+OFF) up to 4 speeds (+OFF) available.
 Working of an interface
Type 'Toggle between LAST level/OFF'
 'Short': after a short push on the button, the fan will switch between OFF and the last
active speed of the fan. When the fan is running at medium speed, then with a short
push the fan will go OFF. Again, a short push switches the fan to medium speed.
 'Long': operation is identical to 'Short'.
Type 'Toggle between: SET level/OFF':
 'Short': after a short push on the button, the fan will switch between OFF and a
predefined speed.
 'Long': operation identical to 'Short'.
Type 'SET Level':
 ‘Short’: The fan will be switched to the predefined level.
 ‘Long’: operation identical to 'Short'.
140
TELETASK Handbook
PROSOFT >
Overview
Type 'Fan speed NEXT (circular)':
 ‘Short’: The fan will go to the next speed
(OFF > LOW > MED > HIGH > MAX > OFF > …).
 ‘Long’: operation identical to 'Short'.
Type ' Fan speed UP':
 ‘Short’: The fan will go to a higher speed. (OFF > LOW > MED > HIGH > MAX)
 ‘Long’: operation identical to 'Short'.
Type ' Fan speed DOWN':
 ‘Short’: The fan will go to a lower speed. (MAX > HIGH > MED > LOW > OFF)
 ‘Long’: operation identical to 'Short'.
 Function behaviour when used in another function
 'SET level': this parameter defines the desired fan speed. The Parameter can be set
from OFF to Max. The target speed is set to High by default. Following settings are
possible:
 ‘speed X: when a function is activated the fan will go to the set speed (Off-Max).
 'speed X/Off': when a function is activated the fan will go to the set speed (OffMax). When the function is switched off the fan goes off.
 Not every function can be switched off. Consult for this matter the
description of the respective function.
8.5. The Fan functions:
 Description
Fans that are not compatible with the TDS13522 (2 wire fans), can be controlled using
individual relays (MICROS+, TDS13510, …). There are two fan types available:
 4-wire single phase AC motor: relays are switched in an OR configuration. For Low
speed the relay for Low is on and the others are off. Etc. At all times, maximum one
relay is switched on by the fan function.
 universal fan control: relays are switched in an AND configuration. For Low speed,
only the relay for Low will be on. For Med, the Low and Medium are on, etc.
 Make sure that no other functions control the relays used for the fan.
 The number of available speeds can be set from 1 to 3 (+OFF).
 Function behaviour
The operation is identical to the operation of the fan.
141
TELETASK Handbook
PROSOFT >
Overview
8.6. The Timed functions
 Description
The timed function switches another function during a predefined time to the desired
status. The timed function is optimized for use on push buttons, touch panels,
touchscreens and for use in other functions (e.g. Local mood, general mood,…).
 Parameters
Within the function
 'Name': Enter a short and clear name for the 'Timed function’ here.
 'Room': select here the room in which the Timed Function is to be activated
 'Icon': select here whether the Timed Function has to be represented on a
TELETASK touchscreen and if yes, under which icon.
 'Select Output': this parameter defines the de function which has to be activated for a
certain time. Depending on the function which is being integrated, more or less
parameters will be defined. Consult for this matter the description of the specific
functions. The functions which can be operated in accordance with a timer function
are : 'Relay', 'Dimmer', 'Local Mood', 'Fan', 'Flags', 'If-Then-Else' and 'Process'
 Use in a timed function only an output that can be switched off.
 'Status': this parameter defines the status to which the output has to be set for a
certain time. The status can be set at 'On', 'Off', or any applicable intermediate value
(e.g. for dimmers).
 'Duration': this parameter determines how long the output will have to remain
activated. When the duration has elapsed the output will be switched OFF (if
possible).
142
TELETASK Handbook
PROSOFT >
Overview
 Function behaviour when used on an interface
Option ‘SET ON’ (default)
 'Short': With a short push on the button the selected function is activated for the
whole duration, e.g. the lamp is switched on. When the duration has elapsed, the
'Timed' function will switch off the selected function.
 'Long': Operation is the same as for short.
Option ‘SET OFF’
 'Short': With a short push on the button the selected function is switched OFF. It the
timer is running it is stopped.
 'Long': Operation is the same as for short.
Option ‘Toggle ON/OFF’
 'Short': If the selected output is in the state described in the ‘Timed function’, the
output is switched OFF. If the selected output is not in the state described in the
‘Timed function’, the output is switched to this state and the timer is started. In both
case this is regardless of whether the timer was running or not.
 'Long': Operation is the same as for short.
 Activating the 'Timed' function when the previous duration has not yet elapsed,
will activate the 'Timed' function again without taking into account the previous
duration. Consequently the duration will be run through completely.
 If the 'Timed' function is ‘SET ON’ when the selected output is in the state
described in the ‘Timed function’, then the selected output will switch OFF when
the timer elapses.
 If the selected output is set to the state described in the ‘Timed funcion’ by
another function when the timer is running, then the selected output will NOT
switch OFF when the timer elapses. See schematic below:
 Function behaviour when used in another function
 The 'Timed' function can be selected from another function. When the other function is
switched on the 'Timed' function will behave as described in the ‘SET ON’ option for
the ‘function behavior when used on an interface’.
143
TELETASK Handbook
PROSOFT >
Overview
 The other function can be switched off only when all functions in the other
function are 'true'. For the 'Timed' function this implies that the timer has to be
active.
 Not every function can be switched off. Consult for this matter the description
of the respective function.
8.7. The Motion detector function
 Description
The motion detector function switches another function during a predefined time to the
desired status. The motion detector function is optimized for use on digital inputs to
which a ‘motion detector’ is connected and for the ‘motion detector in the AURUS-2
SENSE
 Parameters
Within the function
 'Name': Enter a short and clear name for the 'motion detector function’ here.
 ‘Smart’ Light level’: Set the light level at which the motion detector should start
working. The motion detector will only activate the output (light) if the current light level
is below this value. When the output (light) is active, the ‘Smart’ light level will be
adjusted, to compensate for the influence of the output on the light sensor.
 ‘Extra Condition’: Optional! Define a condition here that must be true before the
output of the motion detector function will be activated. The typical example is a light
level but more complex conditions are possible.
 'Select Output': this parameter defines the de function which has to be activated for a
certain time. Depending on the function which is being integrated, more or less
parameters will be defined. Consult for this matter the description of the specific
functions. The functions which can be operated in accordance with a timer function
are: 'Relay', 'Dimmer', 'Local Mood', 'Fan', 'Flags', 'If-Then-Else' and 'Process'
 Use in a motion detector function only an output that can be switched off.
 'Status': this parameter defines the status to which the output has to be set for a
certain time. The status can be set at 'On', 'Off', or any applicable intermediate value
(e.g. for dimmers)
144
TELETASK Handbook
PROSOFT >
Overview
 'Duration': this parameter determines how long the output will have to remain
activated. When the duration has elapsed the output will be switched OFF (if
possible).
 Remark: A 'motion detector' function cannot be switched off. This switches off
automatically when the duration has elapsed.
 Remark: If the selected output is switched by another function to the state as
described in the motion detector function then the state of the selected output
will not change when the timer of the motion detector has elapsed. In such case
it doesn’t matter if the selected output was first activated by the motion detector
function or by the other function.
e.g. when the light is switched by the motion detector function and that light is
again switched on by a local mood, then the light stays on after the timer has
elapsed.
 If motion detector function controls multiple outputs (e.g. by using a LMD) than
the remark above is applied to each of the outputs individually. E.g. When two
lights are switched by the motion detector function and one of the lights was
already ON, than that light will not be switched off by the motion detector if the
timer elapses. The other light will be switched OFF.
 If multiple motion detectors are configured to control the same ‘motion detector
function’ than the timer of the motion detector function will only start when no
motion is detected anymore on all of the motion detectors. See schematic
below:
 Function behaviour when used on an interface
When a 'Motion Detector' function is selected then the names 'Short' and 'Long' are
modified into 'When closing' and 'When opening'. This happens because the option
'edge triggered' with a 'Motion Detector' function is set automatically. Consult for this
function the chapter on “Digital Input Interfaces’.
 'On closing': When the motion detector detects a movement, the selected function
will be activated in accordance with the wanted status. As soon as no movement is
detected any more the respective output remains active for the set duration to switch
off afterwards.
 A 'Motion Detector' function can only be selected in the 'on closing' mode of a
digital input.
 The 'On opening' mode can still be set independently, but is used very seldom
used.
145
TELETASK Handbook
PROSOFT >
Overview
 A motion detector has always to be connected to a 'Motion Detector' function.
Connecting another function to a motion detector, will result in an unwanted or
faulty functioning of the motion detector.
 Function behaviour when used in another function
The motion detector function cannot be used from another function.
8.8. The Sensor Functions
 Description
The sensor functions activate (sensor) threshold values which your TELETASK
domotics system will use to execute certain actions. When the measurements of the
TELETASK temperature, humidity or light sensor exceed (below or beyond) these
values, a suitable action is taken.
 Parameters
The function itself
 'Sensor': this parameter defines the sensor or sensor zone, for which the different
sensor functions have to be represented. In this field you can only select the sensors
for which a control method was specified.
 'Sensor functions': select the sensor function. Depending on the type of sensor
different options can be selected here.
 'Temperature sensor': when a temperature sensor (TDS12250, TDS12251,
AURUS sensor, AIRZONE, Daikin, Mitsubishi electric, MODBUS) is selected, the
following sensor functions can be available depending on the type and
configuration of the sensor. See table below.



'On/Off': this function toggles the temperature measurement for the
corresponding zone between on/off. When off, the zone is inactive
which means that no heat or cool action will take place.
'Preset: Day': this function selects the 'Day' preset as active threshold
value.
'Preset: Night': this function selects the 'Night' preset as active
threshold value.
146
TELETASK Handbook
PROSOFT >









Overview
'Preset: Standby': this function selects the 'Standby' preset as active
threshold value.
'Preset: Frost protection': this function selects the 'Frost protection'
as active threshold value.
'Preset: Up': this function raises the valid threshold value with 1 step
= 0.5°C.
'Preset: Down': this function lowers the valid threshold value with 1
step = 0.5°C.
'Preset: Toggle Day/Night': this function switches the threshold
value between 'Day' (on) and 'Night' (off).
'Preset: Toggle Day/Standby': this function switches the threshold
value between 'Day' (on) and 'Standby' (off).
'Preset: Toggle Standby/Night': this function switches the threshold
value 'Standby' (on) and 'Night' (off).
‘Set specific temperature’: regardless of preset temperatures, you
can specify a specific temperature. This is not recommended. Please
use the preset temperature as much as possible. TELETASK advices
to use Preset Day, Night and standby for normal operation and to only
use this function in exceptional cases where the desired temperature
is different from all preset temperatures.
'Window open: Set frost protection': this function activates the
'Frost protection' as active threshold value, when a window is opened.
When the window is closed then this function will activate the latest
active preset 'Day', 'Night' or 'Standby'.
 This function is developed specifically to be used with a window
contact.

'Mode: Heat/Cool (auto)': This function activates the mode in which
the integrated cool/heat system will cool or heat when needed. This is
done automatically. It will set to cool when the room temperature
becomes too high and heat when it gets too cold in the room. Take
the Delta Heat / Cool setting into consideration specified in Extra 
Options  Sensor tab in the PROSOFT main menu. This will prevent
that the system will continuously switch between Heat and Cool.
 For energy saving reasons the ‘Mode: Auto’ is disabled by
default, you can enable this mode in the menu ‘Extra>Options’. In
de sensor tab you can check the ‘Enable Auto modus’ setting.










'Mode: Heat': This function activates the mode in which the integrated
cool/heat system will only heat when needed.
'Mode: Cool': This function activates the mode in which the
integrated cool/heat system will only cool when needed.
'Mode: Heat+': This function activates 'Heat+' mode as described by
the Airzone heat/cool system.
'Mode: Ventilation': This function activates the concerned
temperature zone in the ventilation function.
'Mode: Dry': This function activates the concerned temperature zone
in the dry function if available.
'Mode: Stop system': This function switches the complete Airzone
system off. No action will be taken caused by a measurement of any
sensor in a sensor zone.
‘Speed: Auto’: when this speed is selected, the speed of the
Heat/Cool system is automatically adjusted depending on the
difference between the measured temperature and the target
temperature.
'Speed: Slow': puts the speed of the Heat/Cool system at 'SLOW'.
'Speed: Medium': puts the speed of the Heat/Cool system at
'MEDIUM'.
‘Speed: Fast': puts the speed of the Heat/Cool system at 'FAST'
147
TELETASK Handbook

PROSOFT >
Overview
'Direction X': puts the air valve of the airco system towards a certain
direction or 'SWING'.
Availability of sensor functions:
Sensor type
TELETASK sensor
AIRZONE
sensor
DAIKIN,
MITSUBISHI
ELECTRIC,
MODBUS sensor
TDS12250
TDS12251
TDS12020
TDS reference number
TDS12021
TDS14060
TDS12022
TDS15200
TDS14061
TDS12024
TDS12026
Heat/Cool (auto)*
If relay Heat and Cool are
defined
NO
If Heat and Cool are
enabled in the sensor
configuration menu
Mode: Heat
If relay Heat is defined
YES
If Heat is enabled in the
sensor configuration menu
Mode: Cool
If relay Cool is defined
YES
If Cool is enabled in the
sensor configuration menu
NO
YES
NO
Mode: Ventilation
NO
YES
If Ventilation is enabled in
the sensor configuration
menu
Mode: Dry
NO
NO
If Dry is enabled in the
sensor configuration menu
Mode: Heat+
Mode: Stop System
Speed: Auto
Speed: Slow
Speed: Medium
If Speed mode is selected
as “2 Step” or “3 Step”
If “control method” for Heat
and/or Cool is selected as “4
Steps (OR)” or “4 Steps
(AND)”
NO
If Speed mode is selected
as “2 Step” or “3 Step”
Speed: Fast
Direction X
If Speed mode is selected
as “3 Step”
NO
NO
TDS15200 only
*Auto mode has to be enabled in PROSOFT
Extra  Options  Sensor tab  Enable Auto modus.
 ‘Other sensor': when a humidity, light, pulse or general analogue sensor is
selected, the following sensor functions are available.
148
TELETASK Handbook
PROSOFT >







Overview
'Preset: Off': the sensor value is switched off. The connected function
is not switched; manual operation of this function is possible.
'Preset: Day': this function selects the 'Day' preset as active threshold
value.
'Preset: Night': this function selects the 'Night' preset as active
threshold value.
'Preset: Up': this function raises the valid threshold value with 1 step
= 1% (humidity), nonlinear Lux value (light), dependant on the sensor
specific settings for pulse and general analogue sensors.
'Preset: Down': this function lower the valid threshold value with 1
step = see ‘preset up’.
'Preset: Toggle Day/Night': this function switches the threshold
value between the 'Day' value (on) and the 'Night' value (off).
'Preset: Toggle Day/Off': This function switches the threshold value
between the 'Day' value (on) and no threshold value (off).
 The sensor functions for the selected sensors are only available
when all parameters with the analogue interface have been
defined correctly.
When called from another function
All functions (i.e. Local Mood)
The sensor functions are selectable in other functions as i.e. a local mood. The
function of the sensor functions stays as described above.
The 'Condition' function
Not all the sensor functions described above are available in the ‘condition’ function,
the available functions are:
 'On/Off' (as above)
 'Preset: Day', 'Preset: Standby' ,'Preset: Night', 'Preset: Frost protection' (as
above)
 ‘Sensor levels’: this function is only available in the Condition, it allows to
compare the measured value of the sensor with a predefined value e.g ‘check if
the value of a light sensor is greater than 10000 lux’ (see the ‘condition function
for more information.)
 A condition that uses the ‘Sensor Level’ function will always be false if the
level of the sensors is unkown (e.g. when the sensor is defect, the interface
is not found on AUTOBUS, just after startup of the central unit,…)
8.9. The Fan (exhaust) function
 Description
The Fan (exhaust) function switches a function and leaves a relay, dimmer, flag or
local mood, in active mode for a preset time after the first function has been switched
off.
149
TELETASK Handbook
PROSOFT >
Overview
 Parameters
 'Name': Put in here a short and clear name for the 'Fan (exhaust)' function.
 'Select Light': this parameter defines the first function which is called when the 'Fan
(exhaust)' function is activated. 4 functions can be selected: 'Relay', 'Dimmer', 'Local
Mood' and 'Flags'. Depending on the selected function several specific function
parameters have to be put in. Consult for this matter the description of the specific
function.
 'Select Motor': this parameter defines the 2nd function which becomes or remains
active for a set duration when the first function is switched off 4 functions can be
selected: 'Relay', 'Dimmer', 'Local Mood' and 'Flags'. Depending on the selected
function several specific function parameters have to be put in. Consult for this matter
the description of the specific function.
 'Duration': this parameter is defined on the right hand side in the 'Select Motor' field.
The 'Duration' determines how long the 2nd function (motor) remains active after the
1st function (light) has been switched off. This parameter can be set from 0 sec. till
7200 sec. in steps of 1 sec. Standard the duration is set at 120 sec.
 'Options - Setting': This parameter determines when the 2nd function (motor) has to
be activated. In this case 2 settings are possible:
 'Ventilator ON when lights are switched off': with this setting the 2nd function
(motor) is activated when the light is switched off. The 2nd function is active only
for the set duration.
 'Ventilator ON when light is switched': with this setting the 2nd function (motor)
is activated simultaneously with the 1st function, when the 'Fan (exhaust)'
function is switched on. When the 1st function (light) has been switched off the
2nd function (motor) remains active for the set duration.
 Standard function behaviour on an interface
'Short': With a short push on the button the 1st function (light) is switched as defined
in the 'Fan (exhaust)' function. If set like that the 2nd function (motor) will be switched
as well.
When the function is switched off the 1st function (light) will be switched off and the
2nd function will remain active for the set duration.
 'Long': The functioning is the same as described under 'Short'.

 Function behaviour when operating in another function
'Fan (exhaust)' type
The 'Fan (exhaust)' function can be selected from another function. When the other
function is switched on, then the 'Fan (exhaust)' function will work as described in the
selected target value.
 'On': The 'Fan (exhaust)' function is activated. The 1st function is switched in
accordance with the settings and if set, the 2nd function will be activated as well.
 'Off': The 'Fan (exhaust)' function is switched off. This means that the 2nd function
(relay) will be activated during the set duration. If the 1st function (light) is switched on,
150
TELETASK Handbook
PROSOFT >
Overview
then this function is switched off. If the function was switched off, it will remain
switched off.
 'On/Off': The 'Fan (exhaust)' function is activated: the 1st function and (if set like that)
the 2nd function is switched. When the function is switched off, the 'Fan (exhaust)'
function will switch off as well: the 1st function is switched off and the 2nd function
remains active for the set duration.
 'Off/Off': The 'Fan (exhaust)' function is switched off. The 2nd function is activated for
the set duration. The 1st function is switched off or remains switched off.
When the function is switched off, the 'Fan (exhaust)' function will be switched off
again. The 2nd function will be activated again for the set duration. The 1st function
remains switched off.
 Not every function can be switched off. Consult for that matter the description
of the respective function.
 Application Example
 In a bath room, shower or toilet, a fan is activated when the light is switched on and
stays on for a number of minutes after the light is switched off again.
 In the lavatory of a company every toilet has his own light but the fan is for all the
toilets (there are several Fan (exhaust) functions made with another light but with the
same motor). The Fan (exhaust) function is so 'intelligent' to switch off the fan only
when the 'run time' of all Fan (exhaust) functions are finished.
8.10. The Local Mood function
 Description
A 'Local Mood' describes the desired status of maximum 10 functions. When the
'Local Mood' is activated the integrated functions in the local mood list will be executed
in the selected sequence in accordance with the set target status.
 Parameters
 'Name': The definition of a 'Local Mood' name is divided in 3 parts:
 'Room': select here the room in which the Local Mood is to be activated
151
TELETASK Handbook
PROSOFT >
Overview
 'Icon': select here whether the Local Mood has to be represented on a
TELETASK touchscreen and if yes, under what icon.
 'Name': a short and clear description of the Local Mood.
 ‘Dimmable’: this parameter determines whether the ‘Local Mood’ function can be
dimmed.
 'Toggle': this parameter determines whether the 'Local Mood' function can be
switched off (reversible), when it is switched on. When this parameter is ticked, the
'Local Mood' will 'toggle'. This means that the 'Local Mood' can be reversed.
 'Select Output': in this field up to 10 functions can be defined which will be executed
when the 'Local Mood' is switched on. Depending on the selected function for each
function some function specific parameters have to be put in. Consult for this matter
the individual function descriptions above in this document.
 Remark: A ‘dimmable’ mood has two states an ON/OFF state and a DIM state (0100%). The DIM state of a dimmable mood is calculated as the average of all the
Dimmers in the local mood.
 Remark: If a ‘dimmable’ mood has a Room and Icon assigned to it, two items
will appear on the TELETASK touchscreens: one to control the ON/OFF state of
the Mood and one to control the DIM state of the Mood.
 Remark: When ‘dimming’ a ‘dimmable mood’ UP or DOWN all dimmers will dim
with the same ramp speed. But it is not guaranteed that two dimmers that start
at the same percentage will stop at the same percentage, small variations (1 or 2
% ) are possible
 Remark: a dimmable mood can contain ‘non dimmable’ items e.g. Relays,
Motors,… These items are NOT switched ON or OFF while ‘Dimming’ the
‘dimmable mood’.
 Remark: The ON/OFF state for the local mood is ‘ON’ when all items are in the
defined status. This is the same for a ‘dimmable local mood’, so when a
‘dimmable local mood’ is ‘dimmed’ UP or DOWN its ON/OFF state will change to
false.
 Function behaviour when used on an interface
'Short': With a short push on the button the 'Local Mood' is activated. This ensures
that all selected functions are switched to the wanted status. When the 'Local Mood' is
switched off, the selected functions will be switched off as described in the respective
function.
 'Long': For a non-dimmable mood the functioning is the same as described under
'Short'. For a dimmable mood a ‘long press’ will Dim the mood UP or DOWN.

 Remark: A 'Local Mood' can only be switched off when the parameter 'Toggle' is
on.
 Function behaviour when operating in another function




A 'Local Mood' can be selected in another function. When the other function is
switched on, the Local Mood will switch in accordance with the set target value.
'On': The 'Local Mood' is activated: all functions within the 'Local Mood' switch to the
set status.
'Off': The 'Local Mood' is switched off: all functions within the 'Local Mood' switch off.
'On/Off': When activating the other function the 'Local Mood' will be activated. When
switching off the other function the 'Local Mood' will be switched off.
'Off/Off': When activating the other function the 'Local Mood' is switched off. When the
other function is switched off, the 'Local Mood' will remain switched off.
 Not every function can be switched off. Whether or not a function can be
switched off, is described with the different functions.
 A 'Local Mood' can only switched off when the parameter 'Toggle' is checked.
152
TELETASK Handbook
PROSOFT >
Overview
8.11. The Timed Local Mood function
 Description
A 'Timed Local Mood' describes the wanted status of maximum 10 functions. When
activating a 'Timed Local Mood' the described functions will be switched to the set
target status in accordance with a set time pattern.
 Parameters
Within the function
 'Name': The name of a 'Timed Local Mood' is divided into 3 parts:
 'Room': select here the room from which the Timed Local Mood will be activated
 'Icon': select here whether the Timed Local Mood has to be represented on a
TELETASK touchscreen and if so, under which icon.
 'Description': type here a short and clear description of the Timed Local Mood.
 'Select Output': in this field up to maximum 10 functions can be defined which will be
operated when the 'Timed Local Mood' is switched on. Depending on the selected
function some ‘function specific parameters’ have to be defined.
 'Waiting time': this parameter determines the delay between this and the previous
function. This parameter is put in at the right hand side in the function window. The
delay can be set from 0 sec till 7200 sec. in steps of 1 sec. By default the waiting time
for each function is set at 0 sec.
 Next to settable waiting time, the cumulative waiting time is indicated. This is
the waiting time for the respective function as from the moment the 'Timed
Local Mood' is switched on.
 'Repeat': This parameter determines whether or not the 'Timed Local Mood' will have
to be executed repeatedly. If this parameter is ticked, then the 'Timed Local Mood' will
start again and run through the described trajectory.
153
TELETASK Handbook
PROSOFT >
Overview
 Function behaviour when used on an interface
Option 'On/Off' (standard)
 'Short': With a short push (switch on) the timer of the 'Timed Local Mood' is started.
The selected function in the 'Timed Local Mood' will be switched consecutively in
accordance with the set waiting time to the wanted status. When the 'Timed Local
Mood' is switched off the active functions will be switched off as described in the
respective function.
 'Long': The functioning is the same as under 'Short'.
 A 'Timed Local Mood' can only be switched off when its timer has not expired.
This means before the function which was last selected was activated. If the
'repeat' parameter is ticked, then the 'Timed Local Mood' can always be
switched off.
 When the 'Timed Local Mood' is no longer active, and you want to switch off the
different functions quickly, then activate the 'Timed Local Mood' in order to
switch it off immediately afterwards (only when the 'On/Off' option is selected).
Option 'On'
 'Short': With a short push the timer of the 'Timed Local Mood' is started. The selected
function in the 'Timed Local Mood' will be switched consecutively in accordance with
the set waiting time to the wanted status.
When it was already switched on
 'Long': The functioning is the same as under 'Short'.
 In this option it is not possible to switch off the 'Timed Local Mood' during the
time it is active.
Option 'Off'
 'Short': With a short push the 'Timed Local Mood' is switched off. All the active
functions will be switched off as described in the respective function. If it was already
switched off, no action will happen.
 'Long': The functioning is the same as under 'Short'.
 Function behaviour when operating in another function




A 'Timed Local Mood' can be selected from another function. When the other function
is switched on the 'Timed Local Mood' will function as determined in the target value.
'On': The 'Timed Local Mood' is activated: the timer is started and the functions are
selected consecutively in accordance with the set time path.
'Off': The 'Timed Local Mood' is switched off: each active function is switched off as
described under the respective function description.
'On/Off': The 'Timed Local Mood' is activated when the other function is switched on.
When the other function is switched off, the 'Timed Local Mood' will switch off.
'Off/Off': When the other function is switched on, the Timed Local Mood will switch off.
When he other function is switched off the 'Timed Local Mood' will remain switched
off. Nothing happens.
 When the 'Timed Local Mood' is switched on while it is active, the 'Timed Local
Mood' will be restarted from the beginning.
 When the 'Timed Local Mood' has run through the set time path, then the active
status of the function in which the 'Timed Local Mood' is located, will be
automatically 'Not True' or 'Off'.
 Not every function can be switched off. Consult for this matter the description
of the respective function.
154
TELETASK Handbook
PROSOFT >
Overview
 Application example:
Controlling garden sprinklers is done in timed phases (not all sprinklers can be on at
the same time). The first group(s) is/are activated immediately, the second group after
30 minutes (and the first is switched off first), the next group thirty minutes later, etc…
8.12. The General Mood function
 Description
A 'General Mood' describes the wanted status of all relay and dimmer outputs in a
certain wanted situation. Next to that up to maximum 5 additional functions can be
called. A 'General Mood' function can only be activated and remains active as long as
no modification occurs to the status of an included output.
 Parameters
 'Name': The name giving of a 'General Mood' is divided in 3 parts:
 'Room': select here the room in which the General Mood will be activated
 'Icon': select here whether the General Mood has to be represented on a
TELETASK touchscreen and if so, under what icon.
 'Description': Introduce here a short and clear description of the General Mood.
 'Relay': In the relay tab page every relay can be selected and the wanted status can
be put in, to which the relay, when the 'General Mood' is activated, has to switch.
 'Not Controlled': if this parameter is selected, then the relay will not be included
in the 'General Mood'. This means that the status of the relay remains unchanged
when the 'General Mood' is activated. On top of that the relay can be switched on
and off, thus not influencing on the active status of the 'General Mood'.
 'On': if this parameter is selected, then the relay will be switched on when the
'General Mood' is activated.
 'Off': if this parameter is selected, then the relay will be switched off when the
'General Mood' is activated.
155
TELETASK Handbook
PROSOFT >
Overview
 'Dimmers': in the dimmers tab page each dimmer can be selected and the wanted
status to which the dimmer has to move, can be set when the 'General Mood' is
activated.
 'Not Controlled': if this parameter is selected, then the dimmer is not included in
the 'General Mood'. This means that the status of the dimmer remains unchanged
when the 'General Mood' is activated. On top of that the dimmer can be controlled
autonomously, thus not influencing the active status of the 'General Mood'.
 1% till 100% (on): if this parameter is selected, then the dimmer will be brought
to the set target value when the 'General Mood' is activated.
 0% (off): if this parameter is selected, then the dimmer will be switched off when
the 'General Mood' is activated.
 'Additional Functions': In a 'General Mood' up to maximum 5 additional functions
can be selected which will be switched to the set target value when the 'General
Mood' is activated.
 Select the function: Select here up to maximum 5 functions which will be
controlled when the 'General Mood' is activated. Following functions can be
selected: 'Timed', 'Motor UP/DOWN', 'Local Mood', 'Timed Local Mood',
'Messages and Alarms', 'TP buzzer', 'Audio', 'Sensor functions', 'Flags', 'Clock
functions', 'If-Then-Else functions', 'Process functions' and 'Service functions'.
Depending on the selected function for each function some function specific
parameters have to be put in. Consult for this matter the description of the
respective function.
 Function behaviour when used on an interface
'Short': With a short push, the 'General Mood' is activated. This means that all relays
and dimmers are brought to the status as defined in the 'General Mood'. Next to that
possible additional functions will be switched in accordance with the set target value.
When the function is switched off (push short again) nothing happens, since a'General
Mood' cannot be switched off.
 'Long': The operation is the same as described under 'Short'.

 Function behaviour when called from another function
A 'General Mood' can be selected in another function. When the other function is
switched ON the 'General Mood' will be switched as determined in the target value.
When the other function is switched OFF, this will not occur to the 'General Mood'
because this function cannot be switched off.
 Remark
 A 'General Mood cannot be switched off because this function brings the house
into a certain status for a longer period , which is often due to a human activity
typified by a significantly modified living pattern for several hours. Examples
are: going to bed, leaving the house, coming home, party, alarm, etc.
 For that reason, in most of the cases, a 'General Mood' will have a counterpart
bringing the house in a status of opposite activity. (Going to bed – Getting up;
Coming home – Leaving the house; etc.)
 When using several Central Units, the General Mood also will be extended with
a 'Global Mood' part. For more info, see 'Several Central Units'.
8.13. The Transparent function
 Description
The 'Transparent' function connects the status of the input directly to the status of the
selected function. When the input closes, the selected function is switched ON; when
the input opens the selected functions is switched OFF (in case the input is ‘inverted’
the selected function is switched ON when the input opens and OFF when the input
156
TELETASK Handbook
PROSOFT >
Overview
closes). The selected output can be controlled by another function, as long as the
input state does not change, the Transparent function will not control the output.
 Remark: At startup (or after download) the Transparent function will switch ON
the selected function if the input is ‘closed’, but it will not switch OFF the
selected function if the input is ‘open’.
 Parameters
 'Name': Introduce here a short and clear name for the 'Transparent' function.
 'Select Output': this parameter defines the function which has to be connected with
an input in a transparent way. Depending on the function which is being integrated,
some function specific parameters have to be set. Consult for this matter the
description of the individual function which you use.
 Function behaviour when used on an interface
When a 'Transparent' function is selected, then the names 'Short' and 'Long' modify
into 'When closing' and 'When Opening'. This is because the option 'Edge Triggered' is
set automatically with a 'Transparent' function. Consult for this function part 'Digital
Input Interfaces'.
 'On closing': When a connected button is pushed or a contact is closed, the selected
function is immediately activated. When the button is released or the contact is
opened the function is immediately switched off. Consequently the function is
activated immediately and lasts as long as the button is pushed (if the selected
function is not controlled by another function).
 'On opening': (= in case of a push button contact 'on releasing') Not applicable. The
transparent function cannot be selected in 'on opening'.
Also due to the specific function characteristics a 'Transparent' function is not
available under the 'Long' push mode.
 The 'On opening' mode can still be set autonomously, but is very seldom used.
 Function behaviour when called from another function
Not applicable: a 'Transparent' function cannot be called from another function due to
specific function characteristics.
 Remark
 The 'Transparent' function can be selected only under the 'On closing' mode of
an input.
8.14. The Messages and Alarms functions
 Description
The functions 'Messages and Alarms' contain text messages and/or beep tones which
inform that a certain situation has occurred. The 'Messages and Alarms' function is
only to be used on TELETASK interfaces with a display, on the GUI+ (TDS15105) and
via e-mail or sms-service.
157
TELETASK Handbook
PROSOFT >
Overview
 Parameters
 'Name': Introduce here a suitable short reference name for the real display text which
is to be entered below in the 'Data' field. Due to the short 'name' when working in
PROSOFT, you should be able to quickly find back the text message you are looking
for.
 'Data': Here the text message is put in which will be announced when a certain
situation will have occurred or at a certain moment. The text message can contain no
more than 2 text lines ('Line 1' and 'Line 2') of 16 characters each. It is recommended
to keep the text messages short and concise.
 'Alarm': Choose this parameter when dealing with an alarm. When an alarm occurs,
then the introduced text message will appear on the selected interfaces with
display/GUI+ and all interfaces will beep with the preset number of beep tones.
 An alarm always has to be switched off manually. Take care first that the cause
of the alarm is taken away.
 For the working of an alarm on the AURUS-OLED (TDS12022) or AURUS-OLED
PLUS (TDS12032), see chapter 'AURUS-OLED'.
 'Message on interface': Choose this parameter when the introduced text message
has an informative value. With this parameter you indicate as well on which interfaces
with display/GUI+the message has to be shown when the situation occurs.
 A message disappears automatically as soon as a new action occurs on the
respective interface. A new action can be activating a function, receiving
another message or alarm.
 'E-Mail': by activating this function, there will be sent an automatically e-mail to the
predefined e-mail addresses.
 This functionality requires a continue connection of the Central Unit with the
internet and that the e-mail settings were correctly imported (see also 'Extra''Options'-'E-mail').
 'Data' (Messages/alarm): here you enter the text message which will communicated
when a certain situation will appear or on a certain moment.
 'Text lines': the text message can contain 2 text lines at the most ('Line 1' and 'Line
2'). Line 1 can contain 16 characters at the most, Line 2 can contain 50 characters at
the most (only the first 16 of the 50 characters will be shown on the older touch panels
(see the data sheet for the concerned application). We suggest keeping the messages
short and to the point.
 'Number of beep tones': Select here the number of beep tones which have to
accompany the text message.
158
TELETASK Handbook
PROSOFT >
Overview
 'Interfaces': Select here the Interfaces/GUI+ on which the messages have to be
displayed.
 'Data e-mail': here you enter the e-mail that will be sent when occurring of a specific
situation or on a specific moment.
 'To': enter here the e-mail addresses to which the message has to be sent. Several
mail addresses have to be separated by ';'.
 'Subject': contains the subject of the e-mail.
 'Message': the length of the message is restricted to 140 characters.
 With the SERVUS the number of preset beep tones takes care of an appropriate
representation of the alarm or message.
 '0': the message or the alarm are spoken, but are not shown on the screen.
 '1'till '10': the message or the alarm are announced and expressed and shown on
the screen. The announcement which precedes depends on the pre set number
of beep tones:
 1 = 'Excuse me'
 2 = 'Hello'
 3 = 'I am sorry'
 4 = 'Please, Excuse me'
 5 = 'Good day'
 6 = 'Attention please'
 7 = 'One moment please'
 8 = 'An instant please'
 9 = 'Hello everybody'
 10 = 'Just listen'
 '11' or more: the present number of beep tones is generated and the message
appears on the screen. Nothing is said.
 Function behaviour when used on an interface
'Message' type
 'Short': With a short push the text message appears on the selected interfaces
accompanied with the preset number of beep tones. When you push short again on
the button, the message is sent again to the interfaces. The previous message is over
written.
 'Long': The operation is the same as described under 'Short'.
 A message cannot be switched off, it disappears automatically in the following
circumstances: after a predefined time or by executing an action on the touch
panel or by a new message/alarm.
'Alarm' type
 'Short': With a short push on the button the introduced text message appears on all
selected interfaces with a display/GUI+ accompanied with the pre set number of beep
tones. With a new short push on the button, the alarm is switched off.
 'Long': The operation is the same as described under 'Short'.
 An alarm is never over written. The latest alarm is always shown on the
interfaces. All preceding alarms can be checked by means of the 'following'
button. For more information consult the manual of the respective interfaces.
 An alarm is deleted either by switching off the alarm with the button or by
means of the 'delete' button on the respective interfaces. For more information
consult the manual of the respective interfaces.
'e-mail' type
 'Short:' when pushing short on the button the e-mail will be sent to all the predefined
e-mail addresses. When pushing again the e-mail will be re-sent.
 'Long': the working is the same as described under 'Short'.
 Function behaviour when operating in another function
159
TELETASK Handbook
PROSOFT >
Overview
'Message' type
A 'Message' can be selected in another function. When another function is activated
the message functions as follows:
 'On': The message appears on the selected interface with the accompanying number
of beep tones.
 'On/-': The message is sent with the accompanying beep tones to the respective
interface. When the function is switched nothing happens with the message.
 Since a message cannot be switched off, a target value cannot be put in. The target
value is indicated in pale grey to indicate the behaviour of the message in the
other function.
 The status of a message is always 'true (on)'. Therefore every function which
only contains a message(s) will also always be 'true (on)'.
'Alarm' type




An 'Alarm' can be selected in another function. When that other function is called the
alarm functions in accordance with the target value:
'On': The alarm is shown on all selected interfaces with a display/GUI+. All concerned
interfaces beep the preset number of times.
'Off': The alarm is switched off.
'On/Off': When the function is switched on the alarm is shown on all respective
interfaces with a display/GUI+ (preset number of beep tones included). When the
function is switched off the alarm will switch off.
'Off/Off': When the function is switched on the alarm is switched off. When the
function is switched off nothing happens or if the alarm became active again in the
meantime, the alarm will be switched off again.
'E-mail' type
 'ON': the e-mail will be sent to all predefined e-mail addresses.
 'ON/-': the e-mail will be sent to all predefined e-mail addresses.
 When switching off this function there will be no e-mail sent.
 Since an e-mail cannot be switched off, a target value cannot be put in. The
target value is indicated in pale grey to indicate the behaviour of the e-mail in
the other function.
 The status of an e-mail is always 'true (on)'. Therefore every function which only
contains an e-mail will always be 'true (on)'.
 Application examples
 A 'message' (disappears after a short time): when at home and late in the evening
there is somebody detected in the garden (motion sensor), not only the garden light is
automatically switched ON, but also a message appears on the display in the living
room 'somebody in the garden'.
 An 'alarm' (stays on the display until you clear the message): When the heating
system fails, the central heating unit goes into alarm status. Normally it will take a long
time (when it's getting cold in the house) before the occupants detect that the heating
system has failed. When using a sort message like 'heating system alarm – call
technician', it is easy for everybody to see immediately what is happening, long before
it gets cold in the rooms.
 In this last case you can also send a direct e-mail to your electrical contractor.
8.15. The TP Buzzer functions
 Description
The 'TP buzzer' function sends from another function an adjustable number of beep
tones to an adjustable interface.
160
TELETASK Handbook
PROSOFT >
Overview
 Parameters
Within the function
The function is only available in another function.
When called from another function
 ‘Interface’: This parameter defines the interface which has to beep. This setting is
only necessary with the 'TP Buzzer' type.
 ‘Target value’: Put in the number of beep tones which is sent to the selected
interface.
 Function behaviour when used on an interface
Not applicable
 Operation in another function
'TP Buzzer' type
A 'TP Buzzer' can only be selected in another function. This function sends a pre set
number of beep tones to a selected interface, when the other function is selected. The
number of beep tones is adjustable in the target value. Following target values are
available:
 'XX times': Select here the number of beep tones that the selected interface has to
produce, when the function is activated. XX can swing for each unit between 1 till 255.
By default the number of beep tones is set at 1.
 'XX times/-': Select here the number of beep tones that the selected interface has to
introduce, when the function is activated. XX can swing for each unit between 1 till
255. By default the number of beep tones is set at 1. When the function is switched off
nothing happens.
 Not every function can be switched off. Consult for that matter the description
of the respective function.
 Application examples:
 Every time that somebody rings at the entrance, one or more touch panels in the
house are beeping a predefined number of times.
 Every time when the front-door is opened the touch panels in the house are beeping
once. Every time when the back door is opened the beepers are beeping twice… just
to let you know.
 Every time when a message appears on a display (touch panel), the beeper of the
touch panel is activated. When it concerns an alarm, you can use a timed local mood
function, which is calling the beeper function to (for example) beep 5 times every 30
seconds, until the alarm is cleared by the user.
8.16. The 'If-Then-Else' function
 Description
Depending of the status of a 'If -Then-Else' condition, the 'If-Then-Else' function or the
'Then' function will be activated.
161
TELETASK Handbook
PROSOFT >
Overview
 The 'If-Then-Else' function controls the status of the 'If' only when activating the
'If-Else-Then' function. To have a continue control on the status of a condition;
use a 'Process' function.
 Parameters
 'Name': Introduce here a short and clear name for the 'If-Then-Else' function.
 'If Condition (TRUE)': see the ‘Condition’ function .
 'Status value of the conditional function': Select here the status on which the 'IfThen-Else' function has to control the conditional function. 2 statuses are possible:
 'On': If the status of the conditional function is 'on', then the 'Then' function will be
switched.
 'Off': If the status of the conditional function is 'off' is, then the 'Then' function will
be switched.
 'Select 'THEN'': Select here the function which is switched when the conditional
function is true (on). Depending on the selected function some function specific
parameters are put in. Consult the description of the specific function.
 'Select 'ELSE'': Select here the function which is switched when the conditional
function is not true (off). Depending on the selected function some function specific
parameters are put in. Consult for this matter the description of the specific function.
 For the calculation of the status of the 'If-Then-Else' function, there are following
possibilities:
 There is a 'Then' and an 'If' configured. When the 'If' is true, the status will be set
through the status of the 'Then'. When de 'If' is NOT true, the status will be set
through the status of the 'Else'.
 There is only a 'Then' or an 'Else' configured. The status of the 'If-Then-Else'
function will always be set through the status of the one available 'Then' or 'Else'.
 Function behaviour when used on an interface
Option 'On/Off'
 'Short': With a short push on the button the 'If-Then-Else' function checks what is the
actual status of the conditional function. If this is true (on), then the 'Than' function will
be activated in accordance with the preset status. If the conditional function is not true
(off), than the 'Else' function will be switched in accordance the preset status.
 'Long': The operation is the same as described under 'Short'.
Option 'On'
162
TELETASK Handbook
PROSOFT >
Overview
 'Short': With a short push on the button the 'If-Then-Else' function checks what is the
actual status of the conditional function. If this is true (on), then the 'Than' function will
be activated in accordance with the preset status. If the conditional function is not true
(off), than no action will be activated.
 'Long': The operation is the same as described under 'Short'.
Option 'Off'
 'Short': the 'If-Then-Else' function will be switched off; the status of the conditional
function will be controlled. Depending on this status the 'Then' or 'Else' function will be
activated according to the 'out' status of the set target value. When the function which
will be switched is already 'out', nothing will happen with this function.
 'Long': The operation is the same as described under 'Short'.
 The functioning of the 'Then' and 'Else' function depends on the selected
function. Consult the description of the respective function to know the correct
functioning.
 Function behaviour when operating in another function




An 'If-Then-Else' function can be selected in another function. Depending on the
preset target value the functioning will be as follows:
'On': The 'If-Then-Else' function is activated: the status of the conditional function is
checked. Depending on this status the 'Than' or 'Else' function will be activated in
accordance with the 'on' status of the preset target value. If the function which will be
switched is already 'on', nothing will happen with the function.
'Off': The 'If-Then-Else' function is switched off: the status of this conditional function
is checked. Depending on this status the 'Than' or 'Else' function will be activated in
accordance with the 'off' status of the preset target value. If the function which will be
switched is already 'off', nothing will happen with the function.
'On/Off': When the other function is activated, then the 'If-Then-Else' function is
activated. When the other function is switched off, then the 'If-Then-Else' function is
switched off.
'Off/Off': When the other function is activated then the 'If-Then-Else' function is
switched off. The status of the conditional function is checked. Depending on the
status the 'Than' or 'Else' function is switched in accordance with the 'off' status of the
pr set target value. If the respective function at that moment is already 'off', than
nothing will happen. When being switched off, this operation is repeated.
 Not every function can be switched off. Consult for this matter the description
of the specific function.
163
TELETASK Handbook
PROSOFT >
Overview
8.17. The Process functions
 Description
The 'Process' function monitors during the active status the status of an adjustable
function. This is the conditional function. Depending on the status of the conditional
function an adjustable function is switched. This is the active function.
Since the 'Process' function continuously monitors the status of the conditional
function, the 'process' function can be called an automating function.
 Parameters
 'Name': Introduce here a short and clear name for the 'process' function which is
being generated.
 'Select function to be monitored': Select the function here that has to be monitored
during the active status of the 'process' function. This is the conditional function.
Depending on the selected functions some function specific parameters have to be
specified. Consult for this matter the description of the selected function..
 'Status value of the conditional function': See the ‘Condition’ function
 'Select the function to be executed': Select here the function which has to be
switched depending on the status of the conditional function. Depending on the
selected function some function specific parameters have to be put in. Consult for this
matter the description of the selected function.
 'Operation when the function is switched on': This parameter determines in which
way manual control stays possible, next to the process function. Here 3 possibilities
can be selected:
 'Continuous monitoring (ON and OFF)': the 'Process' function switches the
status of the active function always equal to the wanted status of the conditional
function. Manual control to execute the function is here NOT possible.
 'Continuously on if TRUE': the 'Process' function switches the status of the
active function only when the status of the function to guard is equal to the set
status. Manual control is possible when the guarding function is NOT true.
 'ON if TRUE & OFF if NOTTRUE (all flanks)': In this case the active function
can be switched at any moment independent of the status of the conditional
function. The 'Process' function however will switch 'ON' the status of the active
function automatically if the conditional function becomes 'TRUE' or switch 'off' if
the conditional function becomes 'NOT TRUE'.
164
TELETASK Handbook
PROSOFT >
Overview
 See the examples for more information about the process functions!
 'Action when switching off function': this parameter determines what has to
happen with the function which has to be executed, when the 'Process' function is
switched off. Here 2 settings are possible:
 'When the process function is switched off: switch off output': this setting
switches off the connected function.
 'When the process function is switched off: not change output': this setting
conserves the status of the connected function when the 'Process' function is
switched off.
 Function behaviour when used on an interface
'Short': With a short push on the button the 'Process' function is switched on. From
that moment on the conditional function will be monitored. Depending on the status
the active function will be switched in accordance with preset parameters.
When switched off (again a short push) the process function will be switched off. The
conditional function will not be monitored any more. The status of the active function
will be switched off depending on the setting and is no longer monitored by the
'process' function.
 'Long': The operation is the same as described under 'Short'.

 Operation in another function
The 'Process' function is selected in another function. Depending on the pr set target
value the operation will be as follows:
 'On': The 'Process' function is switched on. The conditional function is being
monitored continuously and the active function is switched in accordance with
selected settings.
165
TELETASK Handbook
PROSOFT >
Overview
 'Off': The 'Process' function is switched off. The conditional function is no longer
monitored. The active function is switched off, if it was preset, and is no longer
controlled by the 'Process' function.
 'On/Off': When the other function is activated the 'Process' function is switched on.
When the other function is switched off the 'Process' function is switched off.
 'Off/Off': When the other function is activated the 'Process' function is switched off.
When the other function is switched off the 'Process' function remains switched off.
 Not every function can be switched off. Consult for that matter the description
of the function.
 Example: protect sun blinds against wind damage when manual control
stays possible.
To protect sun blinds against wind damage, a process function can be set. As
'guarding function' you can set a 'condition (e.g. named 'lot of wind') where the
measured results of an anemometer are checked.
When there is too much wind, the process function will raise all the sun blinds. When
using the option 'continue control (on&off)', the process function will drop the sun
blinds when there is less wind. This is not wanted. We want to have the choice
ourselves to decide when the sun blinds will drop.
Therefore we use the option 'continue on when 'TRUE'! When there isn't a lot of wind,
the process function won't execute any action and the sun blinds can be controlled
manually.
8.18. The 'Flag' function
 Description
The 'Flags' function signals the status of a situation by his 'on' or 'off' status.
It is only used as a condition whether or not to execute certain actions.
 Parameters
Within the function
 Function behaviour when used on an interface
Not applicable
166
TELETASK Handbook
PROSOFT >
Overview
 Function behaviour when operating in another function




A 'Flag' can be selected in another function. Depending on the preset target value the
operation will be as follows:
'On': The 'Flag' is on. The situation as described by the flag is 'On' or 'True'. If the
'Flag' was already 'On', then it remains 'On'.
'Off': The 'Flag' is out. The situation as described by the flag is 'Off' or 'Not True'. If the
'Flag' were already 'Off', then it remains 'Off'.
'On/Off': When activating another function the 'Flag' will be set 'on'. When the other
function is switched off, the 'Flag' will be set 'off'.
'Off/Off': When the other function is activated the 'Flag' will be set 'off'. When the other
function is switched off the 'Flag' remains switched off.
 Not every function can be switched off. Consult for that matter the description
of the respective function.
8.19. The Condition
 Description
The 'Condition' function describes the status of up to 5 functions and a relationship
between them. When the status and the relationship of the function(s) correspond
with what has been described in the 'Condition', then the condition is 'ON'.
A 'Condition' never results in an action, it can only be used as a condition for other
function types e.g. If-Then-Else function, Process function, …
The status of the condition is updated every time the status of one of the functions in
the condition changes.
 For functions with a status from 0-100% (dimmer and motor), the condition uses
the ‘target value’ of that function to calculate its state. Example: a condition that
defines a ‘dimmer state = 100%’, will be TRUE when the dimmer starts to dim to
100%. If the dimming stops before the dimmer reaches 100%, the condition will
return to false.
 Parameters
167
TELETASK Handbook
PROSOFT >
Overview
 'Name': put in here a clear name for the condition. Take care that the name clearly
describes the situation which occurs when the condition is active.
 'Conditional functions': Select here up to 5 functions which have to be monitored.
Depending on the selected functions some function specific parameters have to be put
in. Consult for that matter the description of the selected function.
 Comparison: This parameter determines how the conditional function has to relate to
the adjustable comparison value. This parameter can take different levels.
 '=': the conditional function has to be equal to the preset comparison value.
 '>': the conditional function has to be greater than the preset comparison value.
This level is meaningful only with numerical comparison values.
 '<': the conditional function has to be smaller than the preset comparison value.
This level is meaningful only with numerical comparison values.
 '>=': the conditional function has to be greater than or equal to the preset
comparison value. This level is meaningful only with numerical comparison
values.
 '<=': the conditional function has to be smaller than or equal to the preset
comparison value. This level is meaningful only with numerical comparison
values.
 Comparison value: This parameter determines the status or value with which the
conditional function is compared. The comparison value can take following shapes:
 Status: This shape determines a 'on or 'off' status with which the conditional
function is compared.
 Numerical: This shape determines a number or percentage with which the
conditional function is compared. This shape occurs only with the functions
'Dimmers' and 'Sensor Levels'.
 Relationship: This parameter determines the mutual relation between the functions.
Following levels can be adjusted:
 'AND': Both functions between which an 'AND' relation is defined, have to be
'true' in order to transmit the 'Condition OK' signal.
 'OR': One of both functions between which an 'OR' relation is defined, have to be
'true' in order to transmit the 'Condition OK' signal.
 At least 2 functions have to be selected before the 'Relation' parameter can be
set.
 When more than 2 functions are present in the 'Condition', than first the relation
between the first and the second function is reasoned. The result of this is
reasoned with a third function etc. This logic is very important when the
different 'Conditions' are defined. In particular when the 'AND' and 'OR' relations
are applied.
 Function behaviour when used on an interface
Since a 'Condition' monitors the status and the mutual relations of one or more
functions, this function cannot be called from an interface.
 Operation in another function
A condition is integrated in another function only as conditional function. This means
that the other function uses the 'Condition' as a condition in order to execute an action
or otherwise.
A condition can only be integrated in following functions: 'Condition', 'Process' and 'IfThen-Else'. Consult the description of the different functions about the operation and
the specific parameters within the function.
168
TELETASK Handbook
PROSOFT >
Overview
8.20. Calculation function
 Description
The calculation function can be used to calculate the difference between two
temperature sensor values. Its result can be used in a ‘condition function’.
 Parameters
 ‘Name’: the name of the function
 ‘Formula’: select two temperature sensors here. The second value will be
subtracted from the first value.
 Operation from another interface
Not applicable
 Operation in another function
The ‘Calculation’ function can only be used in a ‘Condition’ function (or other functions
that have a ‘condition’ like parameter: e.g. the ‘If’ of an ‘If-then-else’ function).
 “Calculation result”: The result of the calculation can be compared with a
temperature value.
169
TELETASK Handbook
PROSOFT >
Overview
8.21. The Service functions
 Description
The 'Service' function control a timer ('No-Action Timer') which starts as soon as no
action in the house is detected. When the timer has expired, an alarm ('No-Action
Alarm) is activated.
 Parameters
Within the function
The parameters for the Service functions are set in the PROSOFT 'option' menu.
Under the tab page 'Option', you will find in the 'Service field' following parameters:
 'No-Action Timer': This parameter sets the duration before the 'No-Action Alarm' is
activated. The 'No action Timer' is adjustable per 15 min from 00h 00min till 48h
00min. By default the time is set at 10h00min.
 'No Action Alarm': Select here the function which has to be activated when during
the 'No-Action Timer' no movement was recorded. Following functions can be
selected: 'Switch', 'Local Mood', 'Timed Local Mood', 'General Mood' and 'Process
Functions'. Depending on the selected function some function specific parameters are
necessary. Consult for this matter the description of the selected function.
 Operation from another interface
'No-Action Control ON/OFF' type
 'Short': With a short push on the button the 'No-Action Control' is switched on when
the function was 'OFF'. When the function is 'ON', the function is switched off. The
'No-Action Control' activates the 'No-Action Timer'.
 'Long': The operation is the same as described under 'Short'.
170
TELETASK Handbook
PROSOFT >
Overview
'No-Action Reset Timer' type
 'Short': With a short push on the button the 'No-Action Timer' is set back to the preset
time. The timer starts running again from the beginning.
 'Long': The operation is the same as described under 'Short'.
 When the 'No-Action Timer' was not started by the 'No-Action Control ON/OFF',
then the 'No-Action Reset Timer' will have no implications.
 Operation in another function
'No-Action Control ON/OFF' type




Depending on the preset target value the 'No-Action Control ON/OFF' will be
controlled as follows:
'On': When the other function is switched on the 'No-Action Control ON/OFF' will be
switched on: the 'No-Action Timer' starts.
'Off': When the other function is switched on the 'No-Action Control ON/OFF' will be
switched off: the 'No Action Timer' stops.
'On/Off': When the other function is switched on the 'No-Action Control ON/OFF' will
be switched on. When the other function is switched off the 'No-Action Control
ON/OFF' will be switched off.
'Off/Off': When the other function is switched on the 'No-Action Control ON/OFF' will
be switched off. When the other function is switched off the 'No-Action Control
ON/OFF' will be switched off.
'No-Action Reset Timer' type
With the 'No-Action Reset Timer' the target value is not adjustable. For information
purposes the target value is indicated in pale grey. Following target values are visible:
 'Reset': When the other function is activated the 'No Action Timer' is set again at the
initially introduced starting time. Said differently the actively running timer is deleted.
 'Reset/Reset': When the other function is activated and as well when it is switched off
the 'No Action Timer' is set again at the initially introduced starting time. Said
differently the actively running timer is deleted.
 Not every function can be switched off. Consult the description of the
respective function.
8.22. The clock functions
 Description
'Clock' functions activate the appropriate clock programs which are set in TIMESOFT.
 Parameters
Within the function
 'Clock Functions': Select here the wanted clock function to activate the appropriate
clock program. Following clock functions are standard available in PROSOFT :
 'Regime: Automatic Workday/Weekend day': This clock function automatically
activates the clock workday or weekend day.
 This regime or clock program is the standard active setting.
171
TELETASK Handbook
PROSOFT >
Overview
 'Regime: Workday': This 'Clock' function activates the clock 'Workday' even if
the active moment in PROSOFT (options) is defined as weekend day. When the
clock 'Work day' is active, the clock 'Weekend day' or 'Simulation' cannot possibly
be active.
 'Regime: Weekend day': This 'Clock' function activates the clock 'Weekend'
even if the active moment in PROSOFT (options) has been defined as week day
defined. When the clock 'Weekend day' is active, the clock 'Workday' or
'Simulation' cannot be possibly active.
 'Regime: Presence simulation': This 'Clock' function activates the simulation
program of your house. This clock is used in case of lengthy absence, to create
an impression of presence. When the clock 'Simulation' is active, the clock
'Weekend day' or 'Workday' cannot be possibly active.
 'Regime: None': This 'Clock' function switches off the clocks 'Weekend day',
'Workday' and 'Simulation'. The clock 'Custom' however remains unchanged.
 'Custom clock table on/off': This 'Clock' function will switch on or off the clock
'Custom'. This clock can be activated independently of the other clocks.
Consequently the 'Custom' clock can run simultaneously with the clock 'Weekday'
or the clock 'Weekend' or the clock 'Simulation'.
 'Next regime': switches to the next regime. The order of the regimes is: Auto →
workday →weekend→simulation→none→auto→…
 'Last regime': switches to the last regime.
 Next to these clock functions which are standard available no other clock
functions are available or need to be generated.
 The clock functions are directly connected to the different clock programs in
TIMESOFT. When no actions in the different clock programs are defined, then it
makes no sense to use the clock functions. Consult the TIMESOFT description
for more information about the clock programs.
 Function behaviour when used on an interface
'Clock functions: Regime'
172
TELETASK Handbook
PROSOFT >
Overview
 'Short': With a short push on the button the selected clock program is activated.
When switched off (again a short push), the standard active setting 'Regime:
automatic Weekday/Weekend day' is activated.
 'Long': The operation is the same as described under 'Short'.
'Clock functions: Custom' type
 'Short': With a short push on the button the 'Custom' clock program is activated when
it was 'off'. It will be switched off when it was 'on'.
 'Long': With a long push on the button the 'Custom' clock program is activated when it
was 'off'. It will be switched off when it was 'on'.
Type 'Clock functions: Next/Previous'.
 'Short': with a short push on the button the next/previous clock program is activated.
At the next push on the button the next/previous regime will be activated.
 'Long': the operation is the same as described under 'Short'.
 Function behaviour when operating in another function
'Clock functions: Regime' type
The target value is not adjustable for the 'Regime' clock functions. When the other
function is switched on the selected clock program will be activated. When the other
function is switched off, the standard active setting 'Regime: automatic
Weekday/Weekend day' will be activated.
'Clock functions: Custom'




The target value can be set for the 'Custom' clock function. Depending on the selected
target value the operation is as follows:
'On': The 'Custom' clock program is activated.
'Off': The 'Custom' clock program is switched off.
'On/Off': When the other function is activated the 'Custom' clock program is activated.
When the other function is switched off the 'Custom' clock program is switched off.
'Off/Off': When the other function is activated and when it is switched off the 'Custom'
clock program is switched off.
 Not every function can be switched off. Consult the description of the
respective function.
8.23. The audio functions
 Description
The 'audio' functions describe the actions which your audio installation has to execute.
'Audio' functions are standard available in PROSOFT, but are released only when the
TELETASK audio interface has been defined.
 Parameters
Within the function
 'Audio zone': this parameter defines the audio zone for which the different available
audio functions have to be represented. In this field you can select a value when an
audio zone has been defined with a TELETASK audio interface.
173
TELETASK Handbook
PROSOFT >
Overview
 'Audio function': Select here the wanted audio function which has to be activated.
Following audio functions are available for each audio zone:
 Zone Out
 Out extra (all zones out)
 ON/OFF
 Volume up
 Volume down
 Mute
 Source 1 to 8 (Play/Preset)
 Source 1 to 8 (Preset)
 Preset 1 to 9
 Preset 0
 Extra code 1 to 10
 In the most situations not all codes will be available. Only the codes which are
learned or put in in AV-Soft are here available.
 Function behaviour when used on an interface
 'Short': With a short push on the button the selected function is activated. If you push
again short on the button, then the function will be activated again.
 'Long': The operation is the same as described under 'Short'.
 'Volume Up': when pushed 'Long' the volume of the current status will increase
until the maximum value.
 'Volume Down': when pushed 'Long' the volume of the current status will
decrease until the minimum value.
 Function behaviour when operating in another function
When the other function is activated the audio function will be switched as indicated
for information purposes in the non-adjustable target value. Following target value can
occur:
 'On': The selected audio function is activated.
 'Off': The 'OFF' audio function is activated.
174
TELETASK Handbook
PROSOFT >
Overview
 'On/Off': When the other function is activated then the selected audio function will be
activated. When the other function is switched off then the 'OFF' audio function will be
activated.
 'On/-': When the other function is activated the selected audio function will be
activated. When the other function is switched off, no action is taken.
 'Off/Off': When the other function is activated the 'OFF' audio function is activated.
When the other function is switched off the 'OFF' audio function is activated.
 For more information about controlling audio systems, please see chapter AVSoft.
 Not every function can be switched off. Whether a function can be switched off,
is described in the different functions.
8.24. Send IR/RS232 OR IP Code
 Description
This function permits to control a non-audio appliance with infrared, RS232 OR IP.
Examples of such appliances are: Jacuzzi’s, gas fires. With this function you can also
control the extra codes on our audio source, independent of zones!
 Parameters
'Send IR/RS232 or IP code': selects the appliance that has to be controlled by IR,
RS232 or IP.
'Function'; selects the specific code which has to be sent to the appliance.
 Function behaviour when used on an interface
'Short': with a short push on the button the selected function will be activated. When
pushing shortly again, the function will be re-activated.
'Long': The operation is the same as described under 'Short'.
 Function behaviour when operating in another function
When activating the other function the IR/RS232/IP code will be sent. When switching
off the function, nothing will happen.
 For more information about controlling IR/RS232/IP systems, please see chapter
AV-Soft.
 Not every function can be switched off. Whether a function can be switched off,
is described in the different functions.
175
TELETASK Handbook
PROSOFT >
Overview
8.25. The Auto start function
 Description
The auto start function is a particular function which activates a selectable function
which is automatically executed when the power supply is switched ON or after a send
from PC to central unit.
 Parameters
The parameters for the Auto start function are set in the PROSOFT 'option' menu.
Under the tab page 'Option', you will find following parameters in the 'Service field':
 'Auto start Function': Select here the function which has to be started up
automatically when the tension is again put on your TELETASK central unit. Following
functions can be selected: 'None', 'Switch', 'Local Mood', 'Timed Local Mood', 'General
Mood' and 'Process Function'. Depending on the selected function some function
specific parameters have to be put in. Consult for this matter the description of the
specific function.
 There is only one auto start function present in PROSOFT. Several functions
can be started up automatically through a 'Local Mood', a 'Timed Local Mood or
a 'General Mood'.
 Operation
When the power of the central unit is restored after a power failure, the function which
was defined in the auto start function will automatically be executed. Also after
sending an .nbt file to the central unit, the 'auto-start-function' will be executed.
176
TELETASK Handbook
PROSOFT >
Overview
8.26. The Display Functions
 Description
The display functions are predefined special functions (e.g. menu selection etc.) on
TELETASK touch panels equipped with a display. The displays can be different,
depending of the type of touch panel with display.
 Overview
Type 'Sensor: Target Up/Down':
With a push on the button the target value of the selected sensor zone will be
increased or reduced.
Type 'Sensor Next/Previous Preset':
With a push on the button the next/previous preset (day/night/standby) of the selected
sensor zone is activated.
Type 'Sensor: Next/Previous Mode':
With a push on the button the next/previous mode (Heating/Cooling/Automatic/…) of
the selected sensor zone is activated (only for temperature sensors).
Type 'Sensor: Speed Up/Down':
With a push on the button the speed of the selected sensor zone increases or reduces
(only for temperature sensors with multi step control).
Type 'Sensor: Next/Previous Zone':
With a push on the button the next/previous zone is selected.
Type ' Sensor: On/Off'
With a push on the button the sensor function 'On/Off' for the linked sensor zone is
activated.
 This function is only useful when a temperature sensor zone is linked to the
touch panel.
Type ' Sensor: Menu'
With a push on the button the extra menu of the corresponding touch panel with
display is selected. In this menu you can set the several settings such as preset
values, time, etc. See the user manual of the different touch panels.
Type ' Sensor: Preset Day'
With a push on the button the sensor function 'Preset: Day' for the linked sensor zone
is activated. The active preset setting is visible on the display. Check out the user
manual of the touch panels for more information.
Type ' Sensor: Preset Night'
With a push on the button the sensor function 'Preset: Night' for the linked sensor
zone is activated. The active preset setting is visible on the display. Check out the
user manual of the touch panels for more information.
Type ' Sensor: Preset Standby'
With a push on the button the sensor function 'Preset: Standby' for the linked sensor
zone is activated. The active preset setting is visible on the display. Check out the
user manual of the touch panels for more information.
 This function is only useful when a temperature sensor zone is linked to the
touch panel.
Type ' Sensor: Toggle Mode'
177
TELETASK Handbook
PROSOFT >
Overview
With every push on the button the mode of the integrated cool/heat system will toggle
between the available modes. The mode can toggle between: 'Mode: Auto', 'Mode:
Cool Only', 'Mode: Heat Only', 'Mode: Heat+', 'Mode: Ventilation', 'Mode: Stop system'.
Type ' Sensor: Toggle Speed'
With every push on the button the speed of the integrated multi step cool/heat system
will toggle between the available speeds. The speed can toggle between: 'Speed:
Auto', 'Speed: Slow', 'Speed: Medium', 'Speed: Fast'.
 With older touch panels (OCTO, LATUS-LCD, …) the sensor display functions
can be slightly different. Please consult the user manuals of these interfaces.
Type 'Audio: Next/Previous source':
With a push on the button the next/previous source (FM/CD/MP3/…) of the selected
audio zone is activated.
Type 'Audio: Volume Up/Down':
With a push on the button the volume of the selected audio zone increases or
reduces.
Type 'Audio: Next/Previous track':
With a push on the button the next/previous preset (channel/track/..) of the active
source of the selected audio zone is activated.
Type 'Audio: Next/Previous Zone':
With a push on the button the next/previous zone is selected.
Type 'Audio: Mute':
The 'mute' code for the selected zone will be sent. If the zone was already in 'mute',
the 'mute' will be removed otherwise it will be set in 'mute'.
 Only when the codes 'mute on' and 'mute out' are the same for the selected
audio appliance!
Type 'Audio: On/Off':
The selected audio zone will be switched on or off.
178
TELETASK Handbook
PROSOFT >
Overview
8.27. Touch screen functions
 Description
The touch screen functions are some predefined special functions for i.e. display
on/off, Go to page etc. on the touch panels equipped with a display.
 Overview
Type 'Display':
The 'display' function can force a display to go OFF while bypassing the display sleep
timer. Or it can switch the display ON.
Type 'Go to page':
The 'go to page' function will switch the page to the desired one. This function is only
available on the AURUS-OLED (PLUS).
8.28. The step function
 Description
A 'Step' function contains up to 10 different functions. Each time the 'step' function is
called, the next step will be executed.
For example: switching between the 10 different RGB colours by using just one
button.
 Parameters
 'Name': the naming of a 'Step' function is divided in 3 parts:
 ‘Room’: select here the room where the 'step' function will be activated.
 ‘Icon’: select here if the 'step' function has to be reproduced on a TELETASK
touchscreen and if so, with the use of which icon?
179
TELETASK Handbook
PROSOFT >
Overview
 ‘Name’: Fill in a short but clear description of the 'step' function.
 'Select output': in this field you can define up to 10 functions which will be controlled
step by step when activating the 'step' function. Depending of the selected function,
per function you have to put in some function specific parameters. See the description
of the chosen function.
 'Add 'OFF' step': this parameter determines if after the last step the first step will be
repeated or if an 'OFF' step follows. If the 'OFF' step is used, all functions within the
'step' function will be switched off.
 Function behaviour when used on an interface
Type 'Step'
 'Short': with a short push on the button the 'Step' function is activated. This means that
the first function of the desired status will be switched. A next push will activate the
next step. The previous step won't be switched off explicit.
 'Long': The operation is the same as described under 'Short'.
Type 'Out'
 'Short': with a short push on the button the 'Step' function will be switched off. All steps
have to be switched of explicitly.
 'Long': The operation is the same as described under 'Short'.
 Function behaviour when operating in another function




A 'Step' function can be selected in another function. When activating the other
function, the 'Step' function will connect according the predefined target value.
'STEP': when activating the function the next step will be executed.
'OFF': when activating the function the 'step' function will be switched off. All steps will
be switched off explicitly.
'STEP/OFF': when activating the function, the next step will be executed, when
switching off the function, the 'step' function will be switched off. All steps will be
switched off explicitly.
'OFF/OFF': when activating or switching off a function the 'step' function will be
switched off. All steps will be switched off explicitly.
 Not every function can be switched off. If a function can be switched off is
marked at the different functions.
 When another function switches off the current step of the 'step' function, the
'step' function will be considered as switched off. This means that the 'step'
function later on will re-start at step 1 (the other steps are not switched off
explicitly).
 When a ‘step’ of a ‘step function’ is activated by another function the ‘current
step’ of the ‘step function’ will not be set to this ‘step’. (This is because it’s
possible that different ‘steps’ of a ‘step function’ are “ON” at the same time, e.g.
it’s is possible that both ‘a LMD in step 2’ and ‘a different LMD in step 5’ of a
‘step function’ are switched on by another function. Hence it is not possible to
define which ‘step’ of the ‘step function’ should be considered as the ‘current
step’).
180
TELETASK Handbook
PROSOFT >
Overview
8.29. The RGB function.
 Description
The 'RGB' function combines 3 dimmers for controlling multi colour lighting.
 Parameters


'Name': the naming of a 'RGB' function is divided in 3 parts:
 Name: insert here a short and clear description of the 'RGB' function.
 Room: select here the room in which the 'RBG' function is activated.
 Icon: select here whether the Local Mood has to be represented on a TELETASK
touchscreen and if yes, under what icon.
 'Select dimmers': in this field you can select the three dimmers which will control the
multicolour lighting. We foresee always 1 dimmer for the colour red, 1 for the colour
green and 1 for the colour blue.
 Function behaviour when used on an interface
 'Short': with a short push on the button the 'RGB' function will be set on the defined
colour. If the 'RGB' function was already set on this colour, it will be switched off (all
dimmers will be switched off).
181
TELETASK Handbook

PROSOFT >
Overview
'Long': The operation is the same as described under 'Short'.
 Function behaviour when operating in another function
When activating the other function the 'RGB' function will be controlled to the defined
colour.
When switching off the other function, the 'RGB' function will be switched off.
 Not every function can be switched off. If a function can be switched off is
marked at the different functions.
 We suggest working with bright colours for the 'RGB' function (you find them in
the upper side of the colour chart)
182
TELETASK Handbook
PROSOFT >
Overview
9. Communication
9.1. Connecting your PC with the central unit
For sending/receiving from PROSOFT to the DOIP central unit, there are two possible ways:
1. USB Connection (Short cable; temporary use)
With a USB cable (standard USB-B to USB-A, not included with the central unit) you can
connect the DOIP directly to the PC with USB 2.0 and USB1.1 compatible ports.
This is typically used for temporary connections (communication with PROSOFT and testing
I/O's). Remember that USB is not able to use long cables (about 5 meters).
2. Ethernet Connection (Long cables possible – up to 100 meter; temporary or permanent
connection)
Through the RJ45-Ethernet connector on the DOIP central unit you can connect to your LAN
(Local Area Network). This is typically used for a permanent connection with a PC, GUI-Device
(touchscreen PC) or any LAN application.
 Before you start:
Windows 7, XP and Vista:
This guide to communicate with the DOIP central unit is written for Windows 7. For
Windows XP/Vista the procedures are largely the same. Where needed, there will be
extra screen shots/Information for Windows Vista/XP.
Control Panel:
For some parts in the guide you will be asked to go to the control panel. We assume
that the control panel is set to the 'Classic view'. In Windows 7 you find this in the right
upper corner of the control panel. In both Vista and XP you can find button 'Classic
view on the left part of the control panel'. If the button is labelled 'Switch to category
view' you are already working in the classic view.
183
TELETASK Handbook
PROSOFT >
Overview
9.1.2. USB Communication
 To avoid possible problems it is recommended always to use the same USB-port on
your PC. Some PC's tend not to recognize the DOIP central unit if connected to another
port!
USB is the easiest way to connect your PC to the DOIP central unit. To be able to use this way
of communication, a specific USB driver should be installed first. Follow the steps below to
prepare your PC:
 Installing the necessary USB driver (Windows 7)

Make sure that the correct PROSOFT Suite version is installed on your PC.
Connect your PC to the DOIP central unit using a standard (A to B type) USB
cable
Windows will give a short message that the hardware couldn't be installed.




Go to the Control panel
Click on Device Manager
Look for the RNDIS/Ethernet Gadget (has a yellow triangle)
Click with the right mouse button on this item and choose update driver software.


184
TELETASK Handbook
PROSOFT >
Overview

Select in the next screen:' Browse my computer for driver software'.

Select in the next screen: ’Let me pick from a list of device drivers on my
computer'.
185
TELETASK Handbook
PROSOFT >
Overview

Select in the next screen: Have disk'.

Now browse to the installation folder of PROSOFT. Normally this should be
c:\Program Files (x86)\TELETASK\PROSOFT 3.2 and click ‘OK’.

Windows will give a warning about the installation of the driver, click 'Continue
anyway'
Windows will now install the correct driver for the DOIP central unit (this may take
some time)
Click Finish in the last screen of the 'Find New Hardware Wizard'.
Your computer is now ready for communication with the DOIP.



186
TELETASK Handbook
PROSOFT >
Overview
 Drivers are installed for each USB port separately, so if you use another USB
port of your PC (notebook) the next time you want to communicate with the
DOIP you will need to repeat this procedure.
 Installing the necessary USB driver (Windows XP)




Make sure that the correct PROSOFT Suite Version is installed on your PC.
Connect your PC with the DOIP Central Unit by a standard (A to B type) cable.
Windows will automatically start the 'New Hardware Wizard'.
Choose 'Not this time' and click on next.

Choose 'Install from a list or specific location (Advanced)' and click next
187
TELETASK Handbook
PROSOFT >
Overview

In the next screen, select 'Search for the best driver in these locations'
check 'Include this location in the search', click the browse button and select the
location of the PROSOFT Installation folder.

Windows will give a warning about the installation of the driver, click 'Continue
anyway'

Windows will now install the correct driver for the DOIP central unit (this may take
some time)
Click Finish in the last screen of the 'Find New Hardware Wizard'.

188
TELETASK Handbook

PROSOFT >
Overview
Your computer is now ready for communication with the DOIP.
 Drivers are installed for each USB port separately, so if you use another USB
port of your PC (notebook) the next time you want to communicate with the
DOIP you will need to repeat this procedure.
 Checking the connection
You can check if the USB cable is correctly connected to the TELETASK Central unit:


Go to Start, Control Panel, Network and sharing centre, Manage network
connections (in the bar on the left, 'Change Adapter Settings). For XP is this
Control Panel, Network connections.
There must be a connection with Device Name; TELETASK Central Unit
(RNDIS)...
Troubleshooting: If you have problem communicating with the DOIP via USB you can check
the following
 Check if the USB port is working properly with another device (e.g. mouse, keyboard,)
 Check if you can communicate via USB to another DOIP central unit (if available), if this
works, there might be a problem with the central unit, contact your TELETASK supplier.
 Make sure your Windows is updated (Service Pack 2 is necessary on XP)
 Check if it is possible to communicate to the DOIP using another USB port/Computer. If
this works there might be a problem with your USB port / computer, contact you PC
distributor.
189
TELETASK Handbook
PROSOFT >
Overview
 Reinstall the driver
Following section describes how you can install the driver when you cancelled the
normal procedure.


Make sure your PC is (still) connected to the DOIP with USB
Go to Device Manager (Start/Control Panel)

Probably you will find a device there with an exclamation mark
(this means: not correctly installed)
Right click on that item en choose 'uninstall'
Press OK to confirm the removal of the driver.
Remove the USB cable from the PC
Now you can go back to section A. Installing the driver




190
TELETASK Handbook
PROSOFT >
Overview
9.1.3. Ethernet Communication
Ethernet communication looks is a bit more complex than USB communication. In most cases
however setting up the Ethernet communication is as easy (or even easier) as setting up a
USB connection. This is the case when you have a simple LAN network to which your
computer is already connected.
You can connect the DOIP to your Network (switch/router) with a standard Ethernet patch
cable.
From the moment this cable is connected correctly, the Communication LED (LEDLINK) on the
DOIP printed circuit board will be on. If this LED is blinking continuously there is possibly
something wrong whit the cable (The LED will blink only when there is data-communication)
If your network is a 100Mbit network or more the 100Mb detection LED (LED100MB) will be lit
as well.
 Ethernet communicatie through LAN
The best way to connect a PC to the Central Unit through Ethernet is by using a hub,
switch or router. Most likely you already have a local network conencted to your PC.
Connect the DoIP, and if necessary your computer to the LAN. In order to establish a
communication between your computer and the Central Unit, follow these steps:






Restart the Central Unit once it is connected to the LAN (press the 'Restart'
button or remove the power for ten seconds).
Start Prosoft SUITE V3.1 (or higher); open the .NBT file you want to use (or
create a new one if required.)
Go to the menu 'Communication' and select 'Send'.
Within the communication window select 'Ethernet'
Click the 'Search button' and a Message box will appear asking you to press
'SW2' on the central unit. (The 'SW2' button on the DOIP is located at the right
side of the printed circuit board, above the battery. Press and release, this
button.)
To make sure that this functionality works your FIREWALL must allow that
PROSOFT can accept connections from the network, if you use 'Windows
Firewall' you will automatically get a 'Security Alert', you have to choose 'Unblock'
there. If you use another Firewall on your PC (ex. Norton Internet Security)
191
TELETASK Handbook
PROSOFT >
Overview
please look at the documentation of that software what to do (you can also
temporary disable the Firewall)

A new window will appear in PROSOFT in which you can set the communication
parameters. In most cases, the new window will look like this:

The text on the top describes the IP settings as they are at the moment, at the
bottom you can change the settings. For a new DOIP (or a DOIP on which the IPaddress is dynamically assigned) PROSOFT will make a proposal for new
settings. It is advised to accept the settings PROSOFT suggests.
There are two types of assigning an IP address: Dynamic or Static. With Dynamic
the TELETASK central unit will ask for an IP address on the network, the switch
or router will provide the IP address automatically. With a Static IP address the
central unit will always have the same IP address.
New DOIP central units always use 'Dynamic' so that they receive all necessary
information (IP address, Subnet Mask, Gateway and Name Server) from the
network. The disadvantage of this system is that the IP-address can change.
Therefore it is advisable to change it to a 'Static' IP-address, like PROSOFT
suggest. In this way the IP-address of the central unit will not change, which is
easier for sending, necessary for connecting GUI's, ..
If needed make changes to the settings, and click save to apply. (You can always
return to this screen to change the settings again).
The IP information is now inserted in your .nbt file (save the file to keep the
settings for further usage).
Your PC is now ready for communication with the DOIP (using the saved .nbt file)
In the communication screen of PROSOFT you can now connect to your central
unit.




192
TELETASK Handbook
PROSOFT >
Overview
 Remark: when you are connected to the central unit, the 'Search' button, changes to a
'Configure' button. When you click this button you immediately get the IP configuration
screen, and you can change your settings (if this is needed).
Trouble shooting: It is possible that procedure above will not work, this is the case if:
 The central unit is 'Static' set to an IP address in another network range than the range
of the LAN network. For most small networks IP addresses are in a different range
when the first three numbers are not the same (e.g. 192.168.0.10 and 192.168.0.11 are in
the same range, 192.168.0.10 and 192.168.1.11 are not).
 There is no DHCP server on the LAN (the DHCP server is responsible for giving IP
addresses to devices that ask for it, in most cases the Switch or router is also the
DHCP server.). In this case the DOIP will use the default IP address (192.168.0.200) and
it is possible that this IP address is in wrong network range for your LAN
 It is not possible to connect devices in a different IP range, so in both these cases you
cannot configure your central unit using Ethernet, use USB to set the IP settings of the
central unit to 'Dynamic', reset the central unit and restart this procedure.
 Alternatively you can push in SW1 and SW2 during 10 second. Herewith the Ethernet
settings of the DOIP central unit are brought back to factory settings (DHCP).
 PAY ATTENTION: it will also delete possible NBT information from the DOIP Central
Unit.
 Ethernet communication using a Crossed cable (not recommended)
 WARNING: In this procedure we will change the IP configuration of your
computer. So it is possible that your computer will no longer be able to connect
to your network or Internet (you will need to set your PC settings back to what
they were before you started this procedure in order to be able to connect
again).
TELETASK does not advise this procedure, we recommend using USB or Ethernet
using a LAN connection. However there can be situations where this procedure is
needed to communicate with the central unit (e.g. if there is no LAN, and you do not
have a USB cable with you).
The connection between the PC and the DOIP is normally done with a 'crossed CAT5'
cable. (Most recent network-cards of the PC's have an 'auto-cross/straight' detection,
then you can also use a straight patch cable)
The steps to set up a connection are:
 Find the IP-Address of your central unit
 Give the PC to an appropriate IP address
 Find the IP Address of your central unit
The default IP-Address of a new DOIP is 192.168.0.200. If you just unpacked your
DOIP you can skip this section


Connect the central unit and your PC
Open TELETASK PROSOFT Suite software, go to the communication screen,
click on the search button and press 'SW2' on the TELETASK central unit
(see Ethernet communication using LAN for a more detailed description of this
step).

There are two different possibilities of the result by pressing the SW2 switch
193
TELETASK Handbook
PROSOFT >
Overview
4. You get the IP configuration box:




Press 'Cancel'
The IP Address is automatically filled in
You can now press 'Connect' and then press 'Transmit' to send your
PROSOFT file
You can skip the rest of this document
5. You are in the wrong IP subnet:





PROSOFT Suite gives a message that it can't be connected with the
Central Unit.
Press 'OK'
The IP Address is automatically filled in
Note this IP address of the central unit
Close the PROSOFT Suite
 Give the PC an appropriate IP address (Windows 7).

Go to Start, Control panel, Network and sharing- change adapter settings). You
will have a window looking like this:

There might be more than one connection (Wireless connection, 1394
Connection,); you need to find the normal wired connection (not the wireless, nor
the 1394 connection).
'Right click' on the Local area connection and choose properties
In the new window, select 'Internet Protocol (TCP/IP)' Version 4 connection in the
list and click 'Properties'.


194
TELETASK Handbook

PROSOFT >
Overview
Now you will get a window where you can set the IP configuration for your
computer. Change the settings so it looks like this (Assuming that the IP address
of the Micros is 192.168.0.200. If not, make sure that the 3 first numbers are the
same as from the IP address of the DOIP and that the last number is different).
 Warning: Note the settings. Before changing them you might need them in
order to reconnect your computer to a network or Internet afterwards.



Click OK to save the new settings. Wait until MSWindows has applied the new
settings (this may take some time).
Open PROSOFT Suite, go to the communication screen, enter the IP address of
the DOIP and click 'Connect'.
Now you can press 'Transmit' to send your PROSOFT file to the DOIP central
unit.
 Give the PC an appropriate IP address (Windows XP)

Go to Start, Control panel, Network connections. You will have a window looking
like this:
195
TELETASK Handbook




PROSOFT >
Overview
There might be more than one connection (Wireless connection, 1394
Connection,); you need to find the normal wired connection (not the wireless, nor
the 1394 connection).
'Right click' on the Local area connection and choose properties
In the new window, select 'Internet Protocol (TCP/IP)' connection in the list and
click 'Properties'.
Now you will get a window where you can set the IP configuration for your
computer. Change the settings so it looks like this (Assuming that the IP address
of the Micros is 192.168.0.200. If not, make sure that the 3 first numbers are the
same as from the IP address of the DOIP and that the last number is different).
Warning: Note the settings. Before changing them you might need them in order
to reconnect your computer to a network or Internet afterwards.
196
TELETASK Handbook



PROSOFT >
Overview
Click OK to save the new settings. Wait until MS Windows has applied the new
settings (this may take some time).
Open PROSOFT Suite, go to the communication screen, enter the IP address of
the DOIP and click 'Connect'.
Now you can press 'Transmit' to send your PROSOFT file to the DOIP central
unit.
197
TELETASK Handbook
PROSOFT >
Overview
9.2. Connection trouble shooting
Follow this procedure when you lost your connection with the DOIP central unit. Don't worry if the
heartbeat LED on your central unit stopped blinking. This means a problem has been detected, not
that your central unit is down.
9.2.1. In practice
When using a LAN connection, trouble could not be related to the Central unit.
Try to connect with the Central unit using an USB connection.
 Reset the central unit by pushing the RESTART button or by disconnecting the
central unit from the main voltage. Wait up to 1' before the central unit has started
up completely.
 Start the PROSOFT Suite and open new file by selecting 'file' 'new' in the menu.
 Connect the PC with the central unit using a proper USB cable.
 In PROSOFT, go to communication and select USB. If this fails, one of the
following error might occur:
 USB on your PC is not working properly.
 USB is not properly connected (and installed).
 The Central Unit is defect.








If the connection succeeded, it should show 'connected' at the bottom of the
window.
Send the empty file you just created, towards the central unit.
It might happen that an error is show: 'Central unit did not start up correctly'. This
means there was a problem with the previous file sent tot the central unit.
RESTART the central unit a second time. This time the central unit will be
completely cleared and will be ready to be configurated. Check if the heartbeat
LED on the central unit blinks.
Now you can open and send a new file towards the central unit.
If the error occurs again, it means there is a problem with the file you try to send.
If your central unit is not responding, even when you send an empty file, it might
be defect.
 Problems in the nbt-file could make the central unit to stop, even after some time. This
means the central unit is working properly but you will have to make a new nbt-file.
198
TELETASK Handbook
PROSOFT >
Overview
9.3. Communication with the DOIP central unit
9.3.1. Send
This section explains how to send your .nbt file to the DOIP, if the connection to the central
unit is already working (USB or Ethernet).
 'Tables to send': Select in this field, the different tables which are to be sent to the
central unit.
 'Central unit’: upgrading to the newest version': This option is automatically marked if
the central unit needs to be upgraded to a newer software version. The new software
is send together with the .nbt file.
 'Basic': this option is marked 'V' by default and makes you send every change to the
TELETASK central unit. This table contains all relations between the different inputs
and outputs.
 'Tables, Clocks and Cards': this option is standard V-marked and sends all data to
the central unit.
 'Displays': Mark the displays whereto you want to re-send the data. The NOT sending
of these data can shorten the duration time of the sending.
 If the central unit needs to be upgraded, you cannot send the displays along.
You can do this, if needed, after the upgrade of the central unit.
 In practice:






Click 'Communication' in the PROSOFT menu bar
Click 'transmit…' and the 'Communication' window appears on the screen
Set the communication settings.
Select the desired information which has to be sent to the central unit.
Click 'OK'. Immediately the data file(s) is (are) sent to the central unit.
The progression bar/label identifies the status of the communication.
199
TELETASK Handbook
PROSOFT >
Overview
9.3.2. Receive
A special function in the communication menu is 'Receive'. When pushing this button, you can
read all the different relations in the TELETASK central unit. This may be a useful tool when
you lost the original PROSOFT file with the project data.
 Beware: Uploading of an .nbt file out of the central unit can only be used as an
emergency tool when you have lost the .nbt file! If the central unit is defect this file also
will be lost. Make sure you have ALWAYS an external back-up of your files on a CD-rom
or Memory Stick.
 'Get Log Info': here you can see the history of the use of the central unit. This info can
be very useful for rare software problems. Depending on the size of the history, the
getting of the log info can take a long time.
 'Restart': the software restarts the Central Unit. This can proceeds eventually when
you are not near the Central Unit.
 'Check SD': Check of the SD Card. For more info, please see the 'support & release
notes' document.
 'Format SD': Formatting of the SD Card. For more info, please see the 'support &
release notes' document.
 'Receive': receiving the .NBT file.
200
TELETASK Handbook
PROSOFT >
Overview
10. Overview of your domotic project
10.1. Print your project
When you want to have a quick look at a certain function or setting in your home automation project, it
is easy to have a paper version of your project in the electrical board, stored together with the other
electrical drawings. In PROSOFT there is a print feature to create a paper version of your home
automation project. Beside the general project settings as the filename, the settings from the installer
and the house itself… You are able to print an extended resume from your project. The subjects you
can print are settable and are divided in six groups:
 ‘Print all information’: all available information will be printed.
 ‘Print basic information’: All information concerning the Central Unit, the rooms, the
Audio Zones, the Sensor zones, the O-interfaces list, the I-interfaces; the Relays
outputs, the Dimmer outputs and the Motor outputs.
 ‘Print functions’: Print all available functions.
 ‘Print I-interfaces’: print the list of the I-interfaces + a detailed overview per Iinterface.
 ‘Print specific I-interface’: print the details of one or some of the chosen I-interfaces.
(handy to update your file).
 ‘Print adapted information’: choose which info you want to print.
 Practical



Click 'File' in the PROSOFT menu.
Click 'Print'
The 'Print .NBT File' window appears


Select the data to be printed.
Click 'OK'. Here you can change the printer on which you want to print the file.
201
TELETASK Handbook
PROSOFT >
Overview
10.2. Hierarchic List
The list you can print with the data of your domotic project, offers a good overview of the used and
available outputs. The hierarchic list shows an overview of every relay, dimmer, motor, sensor, audio
zone, flag, clocks, service functions and messages/alarm functions combined with the coupled
relations.

Only when an output or a function of this kind is defined in PROSOFT will this function appear
in the hierarchic list.

Functions who have no relations with an output (relay, dimmer, flag, …) are displayed in the list
under “Functions without output”. Examples: an empty local mood, a mood who is only used
to call up another mood who on his turn calls up another mood, …

If there are functions that have a relation with on output but are nowhere controlled, these will
be displayed in the list under “Not used functions”. Example: a local mood that controls a relay
and a dimmer that are not displayed.
Using the hierarchic list you can read that relay 1 is used in the local mood 'cooking' and that this relay
is also switched by touching button 1 on the touch panel located in the kitchen.
Thanks to hierarchic list you can search what happens when an output is acting strange or not as you
thought it would work. When you have found the problem in the hierarchic list you can easily solve it in
PROSOFT Suite by changing the function.
 In Practice


The hierarchic list is made by clicking the short key
.
Click this short key again to switch of the hierarchic list.
202
TELETASK Handbook
PROSOFT >
Overview
11. Diagnostics
11.1. General
Diagnostics is a tool within PROSOFT that allows the user to check the status of outputs, inputs and
interfaces of the central unit you are connected to. It also gives the possibility to change the status of
some of the outputs and functions. Real-time monitoring of events is also one of the possibilities.
It’s the ideal tool during the start-up of a project or it can be used for error detection.
Diagnostics is only enabled when PROSOFT is connected with a running Central Unit.
PROSOFT will automatically connect with the Central Unit when you open the .nbt file of that project if
the PC is on the same network.
When connection is established, the Diagnostics icon becomes green
→

.
REMARK: You can use diagnostics without a .nbt file. In that case, start PROSOFT and create a
new .nbt file with the corresponding type of Central unit (MICROS+, NANOS or). Complete the
communication procedure to connect with the Central unit but do not transmit. Diagnostics will
become enabled when the connection is established.
When you select Diagnostics from the Extra menu or click on the icon, PROSOFT will show a new
Window like below:
These buttons let you select the type of output, input or other function.
The relays windows will open automatically when Diagnostics is started.
203
TELETASK Handbook
PROSOFT >
Overview
11.2. Relays
This is the list of relays defined in the central unit:
Each relays is identified as (e.g.):
(A0 O00/1): 01 Room >> Icon >> Name
 ‘A’: Central unit. If multiple Central units are connected over Ethernet, this can be
another character. But in case of one Central unit it’s A.
 ‘0’: AUTOBUS Number: (0-4) 0 is internally in the Central unit (only possible with a
MICROS+/PICOS)
 ‘O’: Input (I) or Output(O): in the list of Relays this is “O”
 ‘00’: AUTOBUS Address of the interface.
 ‘/1’: number of the relays on the interface (1-8)
 ‘01’: internal relay number (only used in PROSOFT)
 ‘Room’: room in which this relay is defined
 ‘Icon’: Type of output
 ‘Name’: name of the relay
The Blue or Yellow Box on the left side of the relay description indicates the status of the Relay:
Blue is OFF,
Yellow is ON.
Clicking on the square will toggle the state of the relay between ON and OFF.
204
TELETASK Handbook
PROSOFT >
Overview
For all boxes which are marked with at red cross, it means that the Central unit is not sure
about the correct state. The blue or yellow colour indicated how the state should be. Additional
information about the error is indicated below the description of the relay in a red font if available.
11.3. Dimmers
This shows the state for each Analogue Output. A fader shows the state in percentages.
Clicking left or right from the fader position will set the fader 10% lower or higher than the current
percentage. Slide the fader into a new position is also possible.
A red cross on top of the fader indicates that the Central unit is not sure about the state of the
Analogue output, the fader position will indicate how the output is expected to be. Additional error
messages indicated in red will tell you more about the error.
205
TELETASK Handbook
PROSOFT >
Overview
11.4. Motors
The Motor window will show the state of the Motors and Motor functions. Only the internal motor
number is shown together with its room, icon and name.
The state of a motor is shown in three blocks:
 2 blocks left and right indicate the direction (up and down arrows )
 1 block in the middle indicates the status of the motor (motor running to 0% or 100%,
stationary at a position, calibrating or empty if position indication is not enabled for the
motor)
When the central block is blue, that means that the motor is not powered. The state of the
direction blocks indicates in which direction the motor has run the last time.
If the central block is Yellow, the motor is powered, the direction is indicated in text and with the
direction arrows.

REMARK: for the motor function with output type ‘1 relay (start/stop)’ the arrow blocks are not
available because the motor only supports basic start/stop operation.
Clicking on the arrow will start the motor in that direction. Clicking on the central block will start the
motor in the opposite direction of the last time or stop it when it was running. After a predefined
runtime, the motor will automatically stop.
Clicking the calibrate button will start a calibration of the run times for that motor.(only on motor
interfaces that support calibration (TDS13526)).
A red cross on top of the motor indicates that the Central unit is not sure about the state of the
motor, it only indicates how the motor state is expected to be. Additional error messages indicated in
red will tell more about the error.
206
TELETASK Handbook
PROSOFT >
Overview
11.5. Digital Inputs
The digital inputs show the state of the digital inputs of the Central Unit, TDS12116, TDS12124 and
TDS12125.
The first part of the ‘Input’ description is identical as a ‘Relay’. See chapter Relays. The only difference
is the ‘name’ which is defined in the ‘info’ field from the ‘Define interface function’ window. If the ‘info’
field is blank, it will get an internal input number.
Input is OPEN (or CLOSED for inverted input)
Input is CLOSED (or OPEN for inverted input)
Input is OPEN but has been closed (short Pulse) during the last 30 seconds (not possible for
edge triggered)

Clicking on the Inputs will not change the state of the input, they are “read only”.
207
TELETASK Handbook
PROSOFT >
Overview
11.6. Analogue Inputs
The Analogue Inputs window shows the state of the analogue inputs of the central unit, inputs of
TDS12309, TDS12310, temperature sensors of the AURUS touch panels and connected HVAC
systems (IP and/or Modbus).
The state shows an analogue value between the minimum and maximum predefined values.

The state is read-only and cannot be altered.
A red cross on top of the fader indicates that the Central unit doesn’t know the state of the input, it only
indicates “???”. Additional error messages indicated in red will tell more about the error.
11.7. Audio Zones
The Audio Zones Window shows the state of the different audio zones:
It shows “OFF” or the active source in that Audio zone.
The State is read-only and can’t be altered.
A red cross on top of state indicates that the Central unit doesn’t know the state of the zone, it only
indicates how the expected state should be. Additional error messages indicated in red will tell more
about the error.
208
TELETASK Handbook
PROSOFT >
Overview
11.8. Other Functions
When selecting “Other Functions” you need to make a choice which function type you want to select.
In this case we selected Local Mood and this gives you the list of function of that type.
The view is identical to the relay, showing the function number, Room, icon and name. the state can
be changed by clicking the square.
The view is identical for all types of “other functions”, only the condition type is read only, the others
can be changed state.

Remark: a function can only be in error if one of the devices (or other functions) used in this
function are in error.
209
TELETASK Handbook
PROSOFT >
Overview
11.9. Interfaces
The interface window shows the list of interfaces known by the Central unit. This means all interfaces
that are defined by the .nbt file that was transmitted, but also interfaces that are not defined but found
by the central unit. (when all is well configured, the last part should result in no errors).
When opening the window the PROSOFT starts an active search on the different busses starting with
AUTOBUS 1. It first start searching for input interfaces, followed by output interfaces. When Items are
defined on AUTOBUS 1, PROSOFT will continue the search on AUTOBUS 2, 3,... The bold line just
above the table indicates where the Central unit is searching. The search can be stopped and refined
by selecting busses and selecting Outputs and/or Inputs.
During the search the list will change from grey lines into white lines. The grey lines show the previous
state of the known interfaces (Preview). The white lines are the actual found results.
When the search is complete (all white) the table shows the state of the interfaces connected to the
Central unit. The state indicates OK or not OK with an error description. In some cases more info can
be found by pressing the details button. When the interface supports it the firmware version number
and AUTOBUS voltage are shown. When a new version of the firmware is available an upgrade button
appears. You can click on it to start the firmware update. When started you can close the diagnostics
or even PROSOFT. The Central Unit handles these updates autonomously. Additional information can
be shown by clicking the “Details” button.
210
TELETASK Handbook
PROSOFT >
Overview
11.10. Monitor
The Monitor window shows the activity of the Central unit. These are the same logs you can find in the
today.log when you choose “Get Log Info ” from the communication/receive Menu. Or from all logs
that are stored onto the PC when downloading the logs. The directory is located on:
“C:\ProgramData\TELETASK\LOGS\Serial number CENTRAL UNIT\2014\04” you find log files for
each day for that month.
Figuring out what is shown in these logs needs some practice. Each action starts with the time when it
occurred. In the monitor this is the Calculated Clock time of the Central Unit. In the stored log files this
is the UCT time (in milliseconds from 01/01/1970 0:00). So you need to distract a number of time
zones to get the real time.
The rest of the log line contains log data, information, warnings or errors.
A log data line starts with L followed by a Log Type (S,A,V,T,H,P,L,B,D), additional subtypes and
parameters.
211
TELETASK Handbook
PROSOFT >
Overview
11.10.1. S (State changed)
Tells you that the state of a function has changed.
L; S; 0, 9, 2, -1
State: (-1=ON, 0=OFF, %)
Function Nr.
Function Type (see list)
Central Unit nr (0= not linked to a CPU)
State Changed
Log
The State of Timed Local Mood nr 2 is ON.
11.10.2. D (Digital Input Pressed)
Tells that a digital input or pushbutton has been pressed.
L; D; 1, 52, 64, 1, 0
Additional info (e.g. 8 = IR command)
Function (Short =1, Long or rising edge=2, released
or falling edge=3)
Digital input Nr
Function Type (=52)
Central Unit nr
Digital Input Press
Log
Digital input 64 has been pressed shortly.
212
TELETASK Handbook
PROSOFT >
Overview
11.10.3. A (Activate Function)
Activates a certain function/device from a function/input.
Device/function that is activating
another device/function
Device/function that is activated
by another device/function
L; A; 1, 20, 2; 1, 1, 92
Function Nr
Function Type (see list)
Central Unit nr (0= not linked to a Central Unit)
Function Nr
Function Type (see list)
Central Unit nr (0= not linked to a Central Unit)
Activate Device
Log
Sensor zone nr 2 will act on relay 92.
L; A; 0, -40,
2;
1, 1,
2
Function Nr
Function Type (see list)
Central Unit nr (0= not linked to a Central Unit)
Function Nr (2 in case of -40 = active GUI nr)
Function Type (-40= GUI or diagnostics, 0 =
from other Central Unit)
Central Unit nr (0= not linked to a Central Unit)
Activate Function
Log
The second activated GUI (or Diagnostics) will switch relay 2.
 Remark: A log line with log type A does not contain info on what will happen to the
actual device (can be switched on or off or nothing may happen).
213
TELETASK Handbook
PROSOFT >
Overview
11.10.4. V (Analogue Value)
A sensor measured a new value.
L; V; 1, 20, 2; 2905
Value (Calculation see manual TDS15132)
Sensor Nr
Function Type (see list)
Central Unit nr
Value (sensor)
Log
Sensor 2 measured value 2905 = 17.5°C (2905/10 - 273).
11.10.5. L (Led Feedback)
Tells you that the feedback of a touch panel button changes state.
L; L; 1, 52, 192; -1
State (-1=ON, 0=OFF)
Touch panel Key Nr
Function Type (52 = Touch panel Key)
Central Unit nr
Led Feedback
Log
The feedback of touch panel button nr 192 is ON.
11.10.6. I (Interface Started)
Tells you that an interface is started up.
L; I; 1, 1, 30
AUTOBUS Address
AUTOBUS Nr
Central Unit nr (0= not linked to a Central Unit)
Interface started
Log
An interface has started up with address 30 on AUTOBUS nr 1.
214
TELETASK Handbook
PROSOFT >
Overview
11.10.7. F (Function Set)
A function has been activated from an TELETASK touch panel.
L; F; 1, 2, 87; 1, 1, 30
Function Nr
Function Type (see list)
Central Unit nr (0= not linked to a Central Unit)
AUTOBUS Address
AUTOBUS Nr
Central Unit Nr
Function Set (from TELETASK Touchscreen)
Log
Touch panel with Address 87 on AUTOBUS 2 will switch Relay 30.
11.10.8. T (Tag)
Tells you that an tag or card has been presented to a tag reader.
L; T; 1203620; -1 1, 1, 2
AUTOBUS address
AUTOBUS Nr
Central Unit Nr
Access (-1=allowed, 0=not allowed)
Tag number
Tag
Log
Tag number 1203620 has been presented to reader with Address 2 on AUTOBUS 1 and
access is allowed.
11.10.9. Q (Quarter Total)
Tells you the number of pulses a certain pulse sensor has detected for the last 15 minutes.
L; Q; 1, 20, 3; 1
Nr of pulses
Zone Nr
Function Type (20 = Sensor)
Central Unit nr
Quarter Total
Log
Pulse sensor 3 detected 1 pulse in the last 15 minutes.
215
TELETASK Handbook
PROSOFT >
Overview
11.10.10. P (Preset Changed)
Tells you that a Preset of a certain zone has been changed.
L; P; 3, 20, 22, 29; 2955
New Value (calculation see Manual
TDS15132)
Preset (29= Day, 27=Night, 88=ECO)
Zone Nr
Function Type (=20)
Central Unit nr
Preset change
Log
The Day preset of sensor 22 on central unit 3 has been set to 26,5°C.
11.10.11. B (Unknown Button Pressed)
A button has been pressed but the CENTRAL UNIT doesn’t have any information regarding
this touch panel. This indicates an error (probably an interface that is not configured in the .nbt
file).
L; B; 1, 1, 11; 5, 1, 0
Additional info
Function (see “D”)
Button Nr on interface
AUTOBUS Address
AUTOBUS Nr
Central Unit nr
Unknown Button Pressed
Log
Button 5 of Interface with address 11 on AUTOBUS 1 has been pressed shortly.
216
TELETASK Handbook
PROSOFT >
Overview
11.10.12. C (Central Unit Command)
Tells you that a function on another CENTRAL UNIT will be executed. (only available when
multiple CENTRAL UNIT are in one project).
L; C; 3, 1, 16; 3
Target Central Unit Nr
Function Nr
Function Type
Central Unit nr
Central Unit Command
Log
Relay 16 on CENTRAL UNIT 3 will be switched. (the log line on CENTRAL UNIT 3 would look
like: L;A;0,0;3;1,16).
11.10.13. H (Hour)
Indicates The CENTRAL UNIT has sent the current Date/Time to all interfaces. (after Start up
and every hour) synchronizes all clocks on touch panels.
L; H; 8
Hour (0-11)
Hour
Log
217
TELETASK Handbook
TIMESOFT
TIMESOFT
12. Actions based on time programs
12.1. Introduction
Timed actions need to be very flexible. TIMESOFT is the perfect tool if you want to have a fast
overview and if you need a powerful editing tool for the flexible clock system in your home automation
project. TIMESOFT is also ideal to manage the thermostat clock actions of the temperature sensor
zones.
12.2. The different clock tables.
To adapt reoccurring actions to your life pattern there are five time tables which we call ‘clock tables’
available. Every clock table has its own typical use and can contain several TELETASK outputs or
executable PROSOFT functions. In the remaining part of this chapter, these outputs and functions are
called ‘clock actions’.
The ‘Continuous’ clock table:
This table is always active. All clock actions entered in this table will be
executed at the defined time of the day without any exception. This
‘continuous’ clock table is particularly suitable for clock actions which are not
depending of your possible presence in the house or day of the week.
Typical application: every day 11pm, close all the curtains.
The ‘Working day’ clock table:
This clock table is only active (actions in it are processed) on the days which
you have defined as working days. The working day clock table has an OR
relation with the ‘weekend clock table and the ‘presence simulation’ clock
table. If one is activated, the other two are always deactivated automatically.
The ‘Weekend’ clock table:
This clock table is only active (actions in it are processed) on the days which
you have defined as weekend days (not working days). The weekend-day
clock table has an OR relation with the ‘working day’ clock table and the
‘presence simulation’ clock table. If one is activated, the other two are
always deactivated automatically.
The ‘Presence simulation’ clock table:
This clock table is only active (actions in it are processed) when the system
is in presence simulation status. The presence simulation clock table has an
OR relation with the ‘weekend clock table and the ‘working day’ clock tables.
If one is activated, the other two are always deactivated automatically.
The 'Special' clock table:
This clock table can be activated and deactivated when you want with any
button or even with a clock action. When active, the clock actions in this
table are executed and when not active, no actions are taken.
218
TELETASK Handbook
TIMESOFT
12.3. Start TIMESOFT.
Simply click the TIMESOFT icon in the PROSOFT Suite menu bar.
12.4. Visualisation
Every action which is added in one of the clock tables appears with a symbol on the weekly display of
your PC (main TIMESOFT window) and it is also displayed in the table overview at the right of the
TIMESOFT window. In some cases the clock actions can be numerous and therefore there are extra
table selection buttons at the top of the main window. Use the selection buttons to get a good
overview of the actions in the tables. A clock table is shown in the overview when the corresponding
selection button is highlighted in orange.
When a selection button is not highlighted, the corresponding clock actions will not be displayed in the
week display and the overview table. Although these actions are not displayed, they are still present in
the clock table
In the clock action overview table it is very easy to see to which clock table to a certain clock action
belongs due to the coloured square in front of the clock action.
Clock types:
Click to visualize all clocks. Default selected when TIMESOFT is
opened.
Click to only visualize all the clocks of a specified thermostat.
Click to only visualize all the ‘none thermostat’ clocks.
Clock tables:
Click to visualize the actions (for the shown week) in the
'continuous' clock table
Colour: Black
219
TELETASK Handbook
TIMESOFT
Visualization of the Work day clock table
Colour: Red
Visualization of the Weekend clock table
Colour: Blue
Visualization of the Presence Simulation clock table
Colour: Green
Visualization of the Special clock table
Colour: Yellow
 When you add a clock action which is repeated every x minute or x hour(s), than
the actions will only be displayed once a day at the moment the action takes
place for the first time that day.
At the other hand it is not recommended to add such fast repetitions, because
they may block the system or the actions may be executed with a delay.
 A maximum of 300 actions will be displayed on the main window. Hide clock
tables to have a better overview on the screen.
 When a clock action is selected (by clicking on it in the calendar overview or in
the table overview) you will see that the clock action symbol on the calendar
overview is filled (little triangle near the timeline). The calendar view will always
switch to the first appearance of the action starting from the current active
week.
 Hidden actions are still normally executed by the system.
220
TELETASK Handbook
TIMESOFT
13. Defining a clock action
13.1. Adding a new clock action
13.1.1. Add a clock action
 Using the 'Edit'-menu
You make a new continuous clock action by clicking the option 'New Continuous
Clock' in the 'Edit' menu. Make every new clock action for the other clock tables in the
similar way.
 Using the short keys
You also can add a new clock action by clicking the 'new clock action' short keys in
the TIMESOFT menu bar. For every clock table (Continuous, workday, weekend day,
simulation and special) is a 'new action clock’ available.
 Using the ‘Right’ mouse button.
‘Right click’ anywhere in the ‘week overview’ and select the clock table to which you
want to add a clock action. The time for this clock action will be set to the time on the
timeline where you ‘right clicked’ (rounded to the nearest quarter of an hour).
13.1.2. The different available parameters
 ‘Clock table’: In this drop down you can change the clock table for the clock action.
The action will only be executed when this clock table is active. Only the 'continues'
clock table is always active. Refer for more information to the 'clock functions' in the
'Functions' chapter in this handbook.
Depending on the selected clock table, the following parameters are available:
221
TELETASK Handbook
TIMESOFT
 ‘Function’: Select here the function which is to be executed at the set time of the day.
For more information about the different functions which can be selected and how they
work, refer to the 'Functions' chapter in this handbook.
 'Reference date & time': enter the reference (starting) date and time for the first
action of this repetition.
 'Repeat every': define here with which repetition the action has to be executed.
 ‘Time’: enter the time at which this action needs to be executed.
 ‘Execute this clock on’: check the days on which this has to be executed.
 ‘Allow user to change this clock on Touchscreen’: Enable this if the user is
allowed to make changes to the clock function.
 Make sure to add a clock name. This name will be used to display the clock on
the compatible touchscreens.
222
TELETASK Handbook
TIMESOFT
13.2. Editing a clock action

Select the clock action you want to change by clicking on it in the right overview
table.

Click the 'Edit action' short key in the TIMESOFT menu bar
. The window
with the parameters of the selected action appears on the screen.
 Shortcut: double click the action you want to change in the right overview
table.


Edit the desired parameters
Click 'OK', and the clock action is changed in the PC.
223
TELETASK Handbook
TIMESOFT
13.3. Remove a clock action

Click the clock action you want to be deleted in the overview table.

Click the 'Delete action' short key in TIMESOFT menu bar
or use the ‘Delete’
key on your keyboard.
On the screen appears a window asking for your confirmation to delete the
selected clock action.
After clicking 'OK' the action is deleted from the clock table.
13.4. The 'Communication' menu in TIMESOFT
To send the adjusted Clock information to the Central Unit, you have to send the .NBT file to the
Central Unit. Refer to the PROSOFT communication chapter for more information.

Before you send the data to the central unit it is recommended to save the project first.
224
TELETASK Handbook
GUISOFT
CARDSOFT – PORTA
14. Introduction
If access control is more than just opening a door to you, TELETASK has the right solution to fulfil your
needs and much more...
TELETASK is not only offering an access control system, but a fully integrated solution which is
reliable, safe, powerful and easy to use. Yes, you can open the door and switching on the lights, the
heating/cooling, switch on the water supply, the gas supply, lower the curtains and set the audio
system in the bath room and the kitchen to your favorite radio station… without even touching a
button. Only a small tag hanging at your car keys or a proximity chip card in your handbag is needed.
As soon as the TELETASK system recognizes you or your beloved ones being at the front door, the
house is at your service. When it’s dark, the lights are dimmed to 'welcome' you, etc…
Not only comfortably opening a gate, a door or a garage door is the result, but the TELETASK
solutions avoid that people can copy your door keys or some access tag/card can have limited or full
access. The gardener can only open the main gate at the street level, open the garage door and
activate the water supply (for a limited time). The cleaning wife is only allowed to enter the house on
Wednesday and Friday mornings between 7am and 11 am, etc…
To be able to set the appropriate settings for these possibilities, TELETASK developed the
CARDSOFT package to be used on any standard PC. The settings for access control items like chip
cards, tags and proximity cards are easily done in CARDSOFT.
15. Terminology
 CARDSOFT: the part of PROSOFT Suite where access control is configured
 PORTA: The App to monitor the access control actions.
 Proximity card: For this manual ‘proximity card’ can refer to a TELETASK card as
well as to a TELETASK tag.
 User: This refers to a person using (owning) the proximity card and/or tag
 Access attempt: refers to an attempt to gain access on a reader with a proximity card
or tag. An access attempt can either succeed (user has access) or fail (user has no
access).
 Access control: The set of rules that define where a user has access.
16. Steps to set up CARDSOFT-PORTA
1.
2.
3.
4.
5.
Set ‘Access control’ options (optional)
Add proximity readers
Create Users and Groups
Configure the ‘Access control’
Schedule automatic E-mail reports (optional)
17. Access control options in PROSOFT
The access control options can be accessed in PROSOFT through extra > option > Access control.
225
TELETASK Handbook
GUISOFT
Manage access control in CARDSOFT by:
 Groups: This is the default mode. In this case access is granted/denied on a group
base. All members of a group will have the same access rights. This option is suited
for most applications (both residential and industrial). By default, two groups are
already created: ‘family’ and ‘others’.
Examples:
 All users have the same rights
 User can be clearly divided in groups: e.g. ‘owners, family, house staff’, or
‘directors, executives, employees’
 Most users can be divided in groups, but a single user is different from all other,
e.g. add a gardener, grandma, concierge, or home assistant, etc… to the
examples above. In this case create a group for that single person.
 Users: In this case access is granted/denied on a single user base. Using this option
probably means a lot more configuration work (especially if there are a lot of users),
but also allows for extra functionalities.
Examples:
 An office building, where each user has its own office desk, but with a general
entrance. You can activate a personal office desk only when its user arrives (=
energy management)
226
TELETASK Handbook
GUISOFT
 Users & Groups: This is an advanced mode where access management is done both
on users and on groups. See the ‘Access management on users and groups’ chapter
for more info about this mode.
Examples:
 If there are users whose access rights are almost identical to those of a group,
you can use this mode to grant the user extra rights, on top of those of the group
(or deny some of the group rights).
 REMARK: Changing the ‘Manage access control’ mode can be useful, but may
result in the loss of data. Changes that will occur without loss of data:
 From ‘Groups’ to ‘User’: In this case the ‘Groups’ settings will be copied to the
individual users, this may be useful if you want to manage access control on a
‘single user’ base, but there are some common settings. Start with the ‘Groups’
mode, configure the common settings on the groups. After this switch to ‘User’
mode to copy the settings to all users.
 From rom ‘Groups’ OR ‘Users’ to ‘Users & Groups’: In this case no changes will
be made to the data.
 All other changes to the ‘Manage access control’ mode will result in the loss of
access settings defined on users or groups. E.g. When switching from ‘Users &
Groups’ to ‘Users’ all group specific settings will be lost (in this case user
specific settings will be retained).
 CARDSOFT logging e-mail recipients: add one or more E-mail addresses here if
you want, to receive E-mails containing an overview of the access attempts. These Emails can be sent on a regular base (defined in TIMESOFT), from a function e.g. Local
mood or automatically: the system will send an E-mail if there are 1250 access
attempts in its memory that have not yet been E-mailed. The number of E-mail
addresses is practically unlimited.
 REMARK: the automatic E-mails will always be sent if there are 1250 attempts
that have not yet been E-mailed. E.g. on average the number of access attempts
in a given installation is about 900/month, so an E-mail is sent at 0:00 at the first
of each month (configured in TIMESOFT). If in a certain month, for example by
the 28th there have already been 1250 attempts, an E-mail will already be sent at
that moment. On the first of the next month a new E-mail will be sent containing
an overview of the remainder of attempts for the past month.
227
TELETASK Handbook
GUISOFT
18. Add Proximity readers
Proximity readers can be added in PROSOFT like any other ‘input interface’: ‘Edit’, ‘Inputs’, ‘New’,
select ‘TDS12142: Proximity reader’.
Beside of the standard items like ‘Name’ and ‘Address’ the proximity reader only has a limited number
of parameters:
 Enable PORTA for this reader: This option is enabled by default. Use this option to
disable PORTA for this reader. If PORTA is disabled for a reader, no access attempts
on that reader will be stored in the memory, nor they will be shown in PORTA, nor will
they appear in the E-mail reports.
 REMARK: Access attempts, and their results on a reader, will always
(independent of this setting) be logged in the normal ‘log’ system (if it is
enabled) and diagnostics/monitor.
 Function: this is intended for the door lock opening function, usually a timed function
or timed local mood.
 Remark: It is not advised to add a conditional function (like if-then-else) to
grant/deny access here, conditions will be added later on.
 Remark: In some exceptional cases the function field needs to remain empty.
E.g. if two doors are operated by the same reader, and the door that needs to be
opened is defined by the user.
228
TELETASK Handbook
GUISOFT
19. Create Users and Groups
To define Users and Groups go to the menu Extra > Users & settings.
 User code: On certain graphical interfaces (like on the iSGUI and AURUS-TFT) it is
possible to protect specific items with a code. This is the ‘user code’. For more info on
the ‘user code’, see the chapter ‘Use of passwords and codes’.
19.1. Users
A user has the following properties:
 Name: The name of the user. In most cases this will be the name of an actual person,
but this can also be something like: ‘spare card’, ‘visitor’, ‘cleaning lady’,…
 Proximity tag /card: The ID nr for this card or tag (printed on the card/tag). Each user
can have a tag and a card. A card and a tag assigned to the same user will always
have exactly the same behavior on every reader.
 REMARK: A card/tag can only be assigned to a single user (as every card has a
unique ID)
 REMARK: If a user has two cards, but no tag, you can assign one of the cards to
the tag field. (and vice versa)
 REMARK: If a user needs more than two personal cards/tags, you need to add
multiple ‘users’ (e.g. james 1, james 2, james 3) for this person and then add
them to one group (e.g james or family members or …).
229
TELETASK Handbook
GUISOFT
 PORTA: Check this field to enable PORTA for this user. For privacy reasons this field
is disabled by default.
 REMARK: By enabling this option, you are responsible to inform the user that
their access attempts are monitored, and to inform them about what will be
done with this information.
 REMARK: Access attempts, and their results, for a user will always
(independent of this setting) be logged in the normal ‘log system’ (if it is
enabled) and diagnostics/monitor.
 Group: Defines to which group a user belongs. A user can be part of one group only.
19.2. Groups
Groups are a means to manage access control for multiple users at the same time. In residential
applications one group, that has access everywhere/ any time can suffice, but in industrial applications
you may have different groups, with different access rights on different parts of the building, plant,
clubhouse, etc…
A group only has a name to identify it.

REMARK: Groups are only used to facilitate the access control management, PORTA always
logs information about a specific user, not about a group.
230
TELETASK Handbook
GUISOFT
20. Define ‘Access rights’
Now that the readers, the users and the groups have been created, a set of rules needs to be
configured to define the access rights. This is done in CARDSOFT (part of the PROSOFT suite).
When clicking on the CARDSOFT button in PROSOFT Suite (in the bar on the left). Depending on the
‘Access control mode’ you will see an overview of the ‘Groups’, the ‘Users’ or the ‘Users and Groups’
For the ‘Groups’ or ‘Users’ mode the configuration is the same, the only difference is whether it applies
on a single user or on a group. In the remainder of this chapter the term ‘user’ will be used to denote
‘user/group’. For the ‘Users and Groups’ mode see the ‘Access management on users and groups’
chapter for more info.

‘Double click’ a user or group to edit its ‘Access settings’.
231
TELETASK Handbook
GUISOFT
The properties that can be set are:
 Access rights: Defines on which reader(s) you want to configure the access rights for
the user. The possibilities are:
 No access: the user has no access (this is the default setting), and can also be
used to temporarily deny access without deleting the card/user
 All readers: the user has access on all readers, a single condition and user
specific function can be defined
 Advanced configuration: The user can have different access rights on different
readers, for each reader a condition and user specific function can be defined
 Reader X: the user has access on a specific reader, for this specific reader a
condition and user specific function can be defined.
 REMARK: If the ‘Access rights’ field is set to ‘Advanced configuration (multiple
readers),a list of all readers will be shown with an indication on whether the
user has access on that reader and on whether a ‘condition’ and/or ‘User
specific function’ is defined. To edit the settings for a reader, select it from the
list and its details are shown.
Example: In the example below the user has access on all readers and a user specific
function’ is defined on one of the readers.
232
TELETASK Handbook
GUISOFT
 Access: Defines if a user has (conditional) access on a reader, this field is only
enabled if the ‘Access rights’ is set to ‘Advanced configuration (multiple readers)’.
 Condition: A condition that needs to be logical TRUE, in order for the user to gain
access. This field is only enabled if the ‘Access’ field is ‘marked’
 User specific function: An extra function that will be executed if the user gains
access (e.g. activate a light and/or heating/cooling when person arrives). This field is
only enabled if the ‘Access’ field is marked.
233
TELETASK Handbook
GUISOFT
21. Access management on users and groups
In some cases, where there are a lot of users and readers, it might be more convenient to
manage access control on both users and groups. While this mode allows for more advanced
configurations, it also adds some complexity. It is for example possible to grant a user access
on a reader while its group has no access on that reader. In such a case of conflicting access
rights there is one rule that defines what the result will be:
If a user presents his/her card to a reader, the system will first check if an access rule is
defined for that user reader combination. If so that rule will be executed. If not, the system will
check if an access rule for the users group exists. If so, it will execute this.
 REMARK: An access rule for the user can be ‘User has no access’ as well as ‘User has
access’. So it is possible to grant a group access on a set of readers, but to deny one or
more users from the group access on a subset of those readers.
 REMARK: The default ‘access setting’ (No Access) is not seen as a valid access rule on
the user in this case. In that case the group action will be executed (if it exists).
 REMARK: It is impossible to execute both the ‘user specific’ and the ‘group specific’
function as the group action will never be executed if an access rule for the user exists
(independent on whether this rule grants the user access or not).
When working in this mode, CARDSOFT will give an overview of both the users and the
groups. When a user is selected (from the list on the left), the users group will be highlighted in
yellow in the list of groups. Similarly, when a group is selected the users belonging to that
group will be highlighted.
CARDSOFT will also indicate if ‘Group’, ‘User’ or ‘User and Group’ rights are defined for each
user.
234
TELETASK Handbook
GUISOFT
22. Schedule E-mail reports with TIMESOFT (or a
function)
E-mail reports can be scheduled using TIMESOFT, or can be requested by the user (e.g. by activating
a local mood). The configuration is the same from TIMESOFT or a function: using the ‘Service
function’ (only available when there are one or more e-mail addresses defined in the access control
options in the CARDSOFT logging field of the Extra > options > Access control menu).
235
TELETASK Handbook
GUISOFT
236
TELETASK Handbook
GUISOFT
GUISOFT
23. Personalised graphical control
23.1. Introduction
23.1.1. Graphical User Interface (GUI)
GUI is the TELETASK Graphical User Interface, running on a target device to control your
domotic system. The software can run on most PC devices: a desktop computer
(GUI/GUI+/iSGUI), a tablet PC build in the wall (GUI/GUI+/iSGUI) but also on a Smartphone or
tablet (iSGUI),…
The GUI/GUI+ software allows you to control your entire TELETASK system in an intuitive way
based on the floor plans of your home or office. Each floor plan represents a part of your
house. This part can be a room, an entire floor, the entire house, or any other part.
With the GUI/GUI+ you can control all TELETASK domotic functions of your home and you
have the possibility to include IP-Camera's, dynamic HTML pages. The different functions are
divided in eight categories: 'Lights', 'Devices', 'Moods', 'Motors', 'Sensor', 'Audio', 'URL or IP
Camera' and 'All'.
The iSGUI has the same functionalities as the GUI/GUI+ but offers you the possibility to create
automatically a complete and personal application for your, Tablet or PC. Even the iSGUI can
integrate IP Camera's.
23.2. Glossary
23.2.1. GUISOFT
The GUISOFT is a part of the TELETASK PROSOFT Suite software. Using the GUISOFT you
will create one or more GUI's for your '.nbt project'.
23.2.2. iSGUI/GUI(+)/Control Tower client configuration
An iSGUI/GUI+/Control Tower client configuration is the visualization of the different control
screens on your target device. A GUI is created in GUISOFT by creating the 'GUI files'
containing all the data for the concerned GUI. The data contains images of the floor plans,
used icons…
23.2.3. GUI Runtime (GUI/GUI+)
GUI runtime is the software that needs to be installed on the target device. Without this
installation, the GUI will not work on the target device. The GUI runtime creates an
environment in which the GUI data is displayed on the target device.
 GUI+: TDS15105 only Microsoft Windows
 GUI: TDS15100 Microsoft Windows XP SP3 or higher, macOS, Linux,…
237
TELETASK Handbook
GUISOFT
23.2.4. iSGUI
Similar to the GUI Runtime. The iSGUI can work on different platforms:
 iOS: iSGUI V1 / V2.5 can be downloaded from the App Store.
 Android: iSGUI V2.5 can be downloaded from Google Play
 BlackBerry: iSGUI V2.5 can be downloaded from BlackBerry World
 Windows PC or macOS: The iSGUI V2.5 can be downloaded from the TELETASK
website.
 In some countries the ‘app-stores’ are or not (completely) available.
23.2.5. Control Tower
The "Control Tower" software runs on the building management PC, for technical alarm
processing and camera surveillance applications. The software is meant to be used by an
operator who is responsible for the technical surveillance of a number of apartments, houses
or buildings. Thanks to the Control Tower software, up to three (or six) operators can
simultaneously work from any location with an internet connection.
The main screen contains an overview of all houses or buildings. In case of an alarm, the
alarm message appears in a dedicated window and the concerned house/building is clearly
indicated by a flashing symbol. The alarm is also supported by an alert and a customized voice
message, asking for the operator’s urgent attention. With permission of the resident, the
supervisor can be given access to some of the basic functions of the house and other
additional services can be offered. A simple phone call to the operator would be sufficient. For
example: change the temperature in your holiday house.
Thanks to the TELETASK DoIP concept, the building can send automatic E-mail and SMS
messages to the resident(s), independent from the Control Tower operator.
23.2.6. Target Device
The target device is the PC, Tablet, SmartPhone, iPhone, iPod Touch, iPad on which the GUI
will run.
238
TELETASK Handbook
GUISOFT
23.3. System Requirements
The target device can be a PC, a laptop, a tablet PC, on which you create the GUI using GUISOFT.
The target device should run on MS Win XP, Vista, 7 (GUI/GUI+/iSGUI) or Apple macOS (GUI/iSGUI)
or LINUX (only GUI).
For the GUI the Java Runtime Environment 1.5 (JRE 1.5) or a better version should be installed on the
PC. If the JRE 1.5 is not installed on your PC, you can easily download it for free from the internet and
install it on your PC: http://www.java.com/
For the GUI+ there need to be installed a .NET framework v4.0 (or higher) on the target device. You
can download it from the internet: http://www.microsoft.com/NET/
The target system does not have to be the PC on which the GUI in GUISOFT was made.
For iSGUI V1 the target system can be an iPhone/iPod Touch/iPad with iOS 3.0 (or higher).
For iSGUI V2.5 the target system can be:
 iOS:
 iOS 6 or higher
 Android Smartphone or tablet:
 Adobe AIR compatible
 ARMv7 processor with vector FPU, minimum 550MHz, OpenGL ES 2.0, H.264
and AAC HW decoders
 Android™ 2.2 or higher
 256MB RAM
 min. Screen resolution 360x480
 BlackBerry:
 BlackBerry OS 10
 min. Screen resolution 360x480
 Windows PC:
 2.33GHz or faster x86-compatible processor or Intel® Atom™ 1.6GHz or faster
processor for netbooks
 Microsoft® Windows® XP Home, Professional, or Tablet PC Edition with Service
Pack 3; Windows Server® 2003; Windows Server® 2008; Windows Vista® Home
Premium, Business, Ultimate, or Enterprise (including 64-bit editions) with
Service Pack 2; Windows 7 or Windows 8 (not RT)
 512MB of RAM (1GB recommended)
 MAC OS:
 Intel Core™ Duo or faster processor
 macOS v10.6 or v10.7
 512MB of RAM (1GB recommended)
239
TELETASK Handbook
GUISOFT
23.4. Schematic Configurations
There are different possibilities to connect the target system on which the GUI runs with the
TELETASK central unit. Furthermore you have the possibility to connect more than one GUI to the
central unit. In this way you can control the house from several GUI's. The below drawn schematic
drawing explains the different configurations.
23.4.1. Connect one target system with the domotics
When you connect only one GUI target system with your domotic system the connections
between the target system and the central unit can be made in several ways.
 Via LAN
Connecting one target system with a GUI/iSGUI over the Ethernet with the central unit
is very simple.
Similar to a PC, we use an Ethernet patch cable (CAT5) or a wireless network to
connect the target system with a switch or router of the LAN. Connect also the
TELETASK central unit with an Ethernet patch cable to the LAN.
 Via USB (only supported in combination with Windows)
For Demo or testing you can connect the target system GUI/GUI+ with the domotics
system via a USB. We do not recommend this for a permanent connection.
23.4.2. Connect two or more target systems with the domotics.
Connecting 2 or more target systems with your DoIP Domotics Central Unit can be done
similar to 1 target system, if you have applied the correct LAN method for every target system.
Attention: all target systems, just like the DoIP Central Unit have to be coupled within the same
network. This means that the IP address of all systems have to start with the same first
numbers. The last numbers have to be different!
e.g. 192.168.0.100, 192.168 0.101 and 192.168.0.102,
240
TELETASK Handbook
GUISOFT
241
TELETASK Handbook
GUISOFT
23.5. GUISOFT Licence
The GUI/GUI+/iSGUI/Control Tower has to be activated before you can use them.
When you buy a GUI/GUI+/iSGUI/Control Tower license, you will receive a 'license code'. With this
license code and the serial number of your Central Unit, you can activate the GUI/GUI+/iSGUI/Control
Tower.
How to activate a license:



Go to www.teletask.be
Choose 'Login/Out' (header menu).
Log into your account or in case you don't have an account, create one
 Remark: an end-user account is made with a few clicks, to get an
professional account it will take somewhat more time.





You are automatically redirected to the 'download' section. Choose 'activation
files' (left hand menu).
Fill out the form correctly and click 'Activate license'
Your activation file will pop up. Download it and save it in your Project folder.
Import the activation file into your PROSOFT project: choose 'extra' - 'licenses'.
Save the .NBT file and transmit to the central unit
23.5.1. TELETASK license system
 GUI/GUI+
For every simultaneous working GUI/GUI+ you need an activated license. This
means that the GUI/GUI+ can be installed on an unlimited number of target systems.
However, there can only run as much GUI/GUI+ applications as there are licenses
installed.
For example: with 1 license you can activate 1 built-in touchscreen with GUI/GUI+
continuously. At the other hand the license which is used for the GUI/GUI+ on your
Desktop PC, can easily be used on your laptop on the road.
This means that when purchasing a new computer/touchscreen PC you don't need a
new license!
242
TELETASK Handbook
GUISOFT
For testing purposes you can use a GUI/GUI+/iSGUI for three days, without activation.
 iSGUI
For every five simultaneous working iSGUI apps you need an activated license.
This means that the iSGUI can be installed on an unlimited number of target systems.
However, this is limited to five iSGUI applications that run at the same time.
 Control Tower
For every project, only one TDS15110 Master license is needed.
For every Client building (= nbt file) a TDS15111 Client license is needed. Every Client
can be real-time connected with up to 3 Master PC’s. If more than 3 real-time Masters
are needed, a second Client license is needed in every Client building.
243
TELETASK Handbook
GUISOFT
24. Making a GUI/GUI+
The GUI is made with the help of the option GUISOFT in the PROSOFT Suite V2.80.1 or higher.
We suggest to make the GUI/GUI+ only after you have configured the complete domotics project in
PROSOFT. The GUISOFT will copy all the defined rooms, functions, outputs,…
24.1. Requirements Session workflow
When you want to install a GUI application, there are a number of steps to be taken. Below you find a
diagram with the different steps and in the next chapters they are described in detail.
1
Activate your license at
www.teletask.eu
2
Configure the GUI properties
and pages.
You will be able to download
the neccessary activation file.
www.teletask.eu - log in/out - downloads activation files
Start PROSOFT Suite opening the wanted
'.nbt'-project and click 'GUISOFT'
Configure the GUI properties in the GUI
properties window: resolution, pages…
! Do not forget to set the proper Ethernet
settings
Drag and drop the domotic and multimedia
functions onto the wanted pages.
3
Import the activation file.
Click 'Extra>Licenses'
Import the activation file
Click 'ok' to confirm the codes
4
Send NBT file to your DoIP
Central unit
5
Export the GUI data files (only
for GUI)
Click 'Communication>transmit
Click 'Communication>Create GUI Files' to
export the GUI data files
Choose a temporary folder to save the GUI
data files
Make a BACK-UP of your GUI files!
6
Install the GUI on the target
device
Download the GUI runtime from
www.TELETASK.eu (GUI/GUI+/iSGUI), Apple
App Store (iSGUI), Google Play (iSGUI) or
BlackBerry World (iSGUI)
244
TELETASK Handbook
7
Copy the 'Gui data' directory
and its content to the
TELETASK GUI directory on
the target device (only for GUI)
8
Connect the target device with
the TDS central unit (LAN / exp.
USB)
9
Start the GUI on the target
device by clicking the 'Start
GUI' icon on your desktop or in
the 'Start' menu.
GUISOFT
Copy paste the 'GUI Data' folder into the
TELETASK GUI installation fodlermap (on the
target device!).
24.2. CREATING A GUI/GUI+
Click on the GUISOFT button in the PROSOFT Suite-bar on the left. If you have not yet created a GUI
for this specific '.nbt' file you will be asked whether you want to create a new GUI. Click 'OK' to
proceed. The GUI properties window will appear on the screen.
24.3. GUI Selection
Start with selecting the correct GUI type.
 'TDS15105' GUI+: choose this GUI type for use on a Windows PC. Special features of
this GUI+ are:
 Support of the dynamic HTML pages
 Messages and alarms
 Availability of different types of skin.
 Charts
 'TDS15101' iSGUI: choose this GUI type for use on a Smartphone, PC or tablet. For
more information about creating an iSGUI, please see next chapter.
 'TDS15100' GUI: choose this GUI type for use on an Apple or Linux (or windows) PC.
245
TELETASK Handbook
GUISOFT
After you have selected the GUI type, you can start the configuration. In GUISOFT you need to start
with determine the necessary features for the new GUI, based on the target system: resolution,
connection, skin,

You can convert a GUI to a GUI+ or vice versa but not with an iSGUI!

The GUI type has to correspond with the licence type that's available.
24.4. GUI Properties
In this start-up screen you will define the resolution of the screen on which the GUI will be displayed
(target device), you will create the different pages of the GUI, import the needed floor plans etc. The
GUI properties start-up window looks like shown in the picture below.
The different GUI parameters that need to be set are:
 ‘GUI Name’: The name for the GUI e.g. 'GUI' First Floor, 'GUI' Living room, 'GUI'
Office... You need to enter a name before you can edit the GUI.
 ‘Target device resolution’: Select the screen resolution of the target device.
 Skin: choose the wanted skin. A skin determines the unity of the colour and
presentation of the GUI (only available at GUI+. GUI always works with Classic skin).
 ‘Run GUI full screen’: Check this parameter if you want to run the GUI as a full
screen application without any borders around the application. This will be typically
used for a dedicated PC with a touchscreen.
Uncheck this option if you want the GUI to run like any other application on your PC.
Choose this option when you want to use the GUI on your standard home office PC.
 This item only disables the window borders. The size of the GUI is still
determined by the 'Target device resolution'
 ‘Enable Audio Feedback’: Select this option if you want an auditive feedback when
you push a button.
 The target device need to be equipped with a speaker and sound volume must
be on.
246
TELETASK Handbook
GUISOFT
 ‘Type of Communication’: Select here the type of connection between your
TELETASK central unit and the target device.
 ‘Ethernet’: the connection between the central unit and the PC runs over the
LAN network. You will us this typically when your PC is connected to your
network or when you want to run the GUI on several PC's.
 IP-address Central unit: (only selectable with the Ethernet communication).
Insert here the IP-address of the Central Unit.
 IP-Port nr: Default 55956 (only selectable with the Ethernet communication).
Change this only in case of Port Forwarding. NOT RECOMMENDED!!!
 ‘USB’: the connection between the central unit and the PC is done directly
between the USB port of the TELETASK central unit and the PC on which the
GUI is active. This way you can connect maximum 1 GUI on your TDS (only for
temporary connections).
 ‘Define new page’: this button will add a new page to your GUI. A page can contain
anything you want. Still we suggest you to work with rooms, floors, the pages do not
have to correspond with the rooms you defined earlier in PROSOFT, and it is possible
to create a 'favorite' page in which you combine the most used functions (moods,
lights,) with the available camera pictures.
 ‘Page Name’: the name for the page, this name will be displayed in the GUI
 ‘Select Image’: this button allows you to import a background image for the page (the
floor plan of the part of the house this image refers to, a photo,). Depending on the
resolution and the full screen option the optimized image size for the page is indicated
at the left side of this 'Select Image' Button.
 The image file needs to be a .jpg, .gif, .png or .bmp file.
 ‘Select background colour’: this button allows you to set the background colour for
the selected page. TELETASK advises to use this option only when the background
colour of the image is other than white.
 ‘Arrow up or Arrow down’: using the arrow up or arrow down buttons below the list
of available GUI pages you can change the sorting position of the selected GUI page
in the list.
As soon as you have defined all pages and the communication settings are correct, click 'OK' to
continue. The GUISOFT screen will now appear on your screen.

You can always return to this screen to edit the page and or communication settings later by
clicking the 'GUI properties' button.
247
TELETASK Handbook
GUISOFT
24.5. GUISOFT Screen
The GUISOFT screen can be divided in three zones: the GUISOFT menu, the functions and symbols
library and the GUI preview area.
1
2
3
24.5.1. The GUISOFT menu
Using the GUISOFT specific menu you create a new GUI, select the GUI you want to change,
change the GUI properties of the selected GUI or delete the selected GUI.
 ‘New GUI’: It is possible to create more than one GUI for one '.nbt' project. This is
typically done when you want to control your domotic functions from several target
devices with different specifications (other resolution, other location in the house etc.).
When you want to create a new GUI, click the 'New GUI' button in the GUISOFT
menu. The GUI properties start-up window for the new GUI will appear on the screen.
 ‘Select GUI’: When you have more than one GUI created in a project you have to
select the correct GUI before editing anything at the GUI. In the 'Select GUI' drop
down list you can select the GUI you want to edit.
 ‘GUI properties’: To change the properties of the selected GUI, click the GUI
properties window. The GUI properties window will appear on the screen in which you
can change different setting as the GUI name, type of communication etc.
 ‘Delete GUI’: Clicking this button the selected GUI will be deleted. Before deleting it
definitely a remark will appear on the screen asking for your confirmation.
 The GUISOFT menu remains equal, independent to the GUI/GUI+/iSGUI you are
working in.
24.5.2. The functions and symbols library
 The functions library
Using the functions library you can browse in the different domotic functions which you
have made earlier in the PROSOFT session of the .NBT project.
 The symbols library
Using the symbols library you can choose a GUI icon to drop on the GUI preview.
248
TELETASK Handbook
GUISOFT
24.5.3. The GUI Preview
In the GUI preview (permanent displayed on your PC screen) you can partly see your GUI as it
will look like in daily use. The areas where fixed items of the GUI will be placed are shaded.
You can’t position anything else in these areas.
Depending on the resolution/skin of the screen a limited number of page buttons are
displayed. Choose the page in which you want to work, just like you would do when controlling
the GUI. At the left side of the preview area the different icons as known in PROSOFT are
displayed. Clicking on these buttons shows the corresponding functions dropped on the page.
The different icons are:
 ‘Light’: displays only the dropped lights of the selected page.
 ‘Devices’: displays only the dropped devices of the selected page.
 ‘Moods’: displays only the dropped moods of the selected page
 ‘Motors’: displays only the dropped motors (curtains, shutters, gates etc) of the
selected page.
 ‘Sensors’: displays only the dropped sensor functions of the current page
 ‘Audio’: displays only the dropped audio zone in the current page
 ‘Camera's and URL pages’: displays only the dropped camera and URL
functionalities of the current page
 ‘All’: displays all the dropped functions of the current page
24.6. Adding items to the GUI
24.6.1. Drag and drop
After the GUI pages have been defined, you can add several domotic functions you have
earlier defined in PROSOFT in the GUISOFT screen using the easy and user friendly drag and
drop concept: drag the domotic functions out of the functions or symbols library and drop them
on the preview of the preview area.
24.6.2. Positioning (grid)
To position the different items on the GUI screen, a positioning grid can be used. To
activate/show the grid, click the grid icon in the grid toolbar just below the standard toolbar. If
the grid is activated the icons you drag onto the GUI screen, will 'snap' to the grid points. The
grid can be adjusted to any interval of pixels preferred. Therefore the pixel interval is set in the
grid toolbar (standard = 10 pixels).
249
TELETASK Handbook
GUISOFT
24.6.3. Edit the GUI Icon
When you have dragged the function out of the functions library, a standard GUI icon is
assigned to the function on the GUI preview. However, you can change the icon image
settings. Right click the GUI icon in the preview and select 'Edit GUI Icon' from the drop down
list. The 'Edit Item' window will appear on the screen.
When you have dragged the symbol out of the symbols library and dropped it on the GUI
preview the 'Edit Item' window will appear automatically so you can assign the desired function
to the symbol.
In the 'Edit Item' window you can change some properties of the image and/or the function. In
the left part of the 'Edit Item' window you can define the appearance settings of the icon. In the
right part of the 'Edit Item' window the function of the GUI item can be changed.
 Appearance:
'Size & location'
The size of the touch sensitive zone (active zone) of the GUI item is defined by the
'Width' and the 'Height' parameter. Both parameters are defined in pixels. TELETASK
advices to set the width and height parameter at 32 pixels for an optimal user friendly
finger control on a standard 15' touchscreen (resolution: 1024x768).
The location of the GUI icon describes the place of the GUI icon on the devices screen
using the 'X' and 'Y' coordinates.
'Item Text'
Every GUI item can be accompanied by a declarative text. Define both the 'Text
location' and the 'text' to add a text to a GUI item.
 ‘Text Location’: This parameter defines the position of the text around the GUI item.
 ‘Text’: Enter here the text that appears near the GUI item. By default, the name given
in PROSOFT will appear in this field.
'Image'
Every GUI item has a default image. However, you can replace the default image of
the GUI item with an image out of the TELETASK image library.
 ‘Change Image’: Click this button to change the image with an image out of the
TELETASK image library.
 The 'Change Image' option can also be selected directly from the drop down
menu when you right click the GUI Icon.
250
TELETASK Handbook
GUISOFT
 ‘Scale Image (fill active zone)’: When this option is checked, the image will be
scaled to fit the 'active size'
 ‘Fixed Image Size (centred)’: This option allows you to enter a custom size for the
image in pixels. The fixed image size can only have the same or a smaller size than
the active size. When the image size is smaller than the active size, the image will be
placed in the centre of the active zone/size.
 ‘No Image’: Select this option when you don't want to display an image for an item
(transparent button).
To create GUI+ icons yourself you have to name the gif’s according to a
specific pattern:
Most items (lights, devices, ...) have two states "ON" and "OFF". The images for this
two states need to be named:
 ON status: MyImage-on.gif
 OFF status: MyImage-off.gif
For the part "MyImage" you can use your own image name and need to be the same
for the on and the off state. The parts "-on.gif" and "-off.gif" need to be exactly like this.
Motors have four states: "Closed", "Closing", "Opened", "Opening". These images
need to be named:




"Closed": MyImage-closed.gif
"Closing": MyImage-closing.gif
"Opening": MyImage-opening.gif
"Opened": MyImage-opened.gif
 Note: It is also possible to create "ON/OFF" images in the "motors" category.
These icons can be used for local moods that you want to display in the motor
icon.
 Items for Cameras, URLs and ‘Go-To-Page’ only show 1 state (the "ON" state),
but there need to be two images in the library, using the "ON" and "OFF"
naming convention. You can create an "ON" image, copy it and rename the copy
to "-off.gif".
 Function:
'Select Function Type'
This option allows you to choose or change the type of function you want to be
coupled to the (dragged) GUI Item. You can choose out of different function types:
 ‘Standard PROSOFT function’: Use this function to make the GUI item to control a
specific domotic function on your TELETASK central unit. The function you select
needs to be configurated in PROSOFT. Examples: switching a light, activating a
motor, change the sensor preset of the heating…
 ‘IP-Camera’: This function takes the URL of an IP camera's MJPEG file to be
displayed on the GUI screen, when you click the GUI item.
 Note that this functionality needs a camera that support MJPEG file stream. Not
all IP-Camera's support MJPEG file stream.
 ‘URL or Image’: Using this function type the GUI item will display a pure html page or
an image. The URL in the lower tab page has to be completed and can refer to a
location on the Internet (start the URL with 'http:// …') or to an image (start URL with
'file:/// …') which is located on the PC on which the GUI is active.(note 3 times the '/'
character, e.g. file:///c:/My documents/image.jpg).
 A dynamic HTML page is only available on the GUI+.
251
TELETASK Handbook
GUISOFT
 ‘Show chart’: Select this to display a Graph about a sensor or an output (Relay,
Dimmer, …).
 Add the output/sensor, for which you want a Graph, like for normal control of
the output. Then edit the item and change the function type to “Show chart”
 For a sensor you do not need to explicitly add the chart. If the sensor is added
to the GUI you will be able to see the graph (if you want the Graph for a sensor
to be ‘default open’).
 ‘Start external program’: use this function to start an external program inside the
GUI+ runtime.
 The behavior of this function is largely depending on the external program
itself!!!
 ‘Go-To GUI Page’: Using this function type, the GUI item will switch to another page
when it is touched.
'Icon'
Here you can set up the categories under which the GUI item must be visible. The
category is chosen by default from the coupled PROSOFT function. Camera's and
URL's arrive by default under the 'Camera' icon. The 'Go-To-GUI-Page' arrive by
default at the 'All' icon.
 !!!!Items of the category 'All' will always be displayed at the ALL category.
'Popup Window'
For some of the function types a 'Control Panel' will be displayed on the screen when
you touch the GUI item.
A 'Control Panel' popup appears when the GUI item is defined as a URL or Camera
function or when the PROSOFT function is a dimmer, a RGB control, an audio zone or
a sensor zone. In the 'Control Panel' popup some function type related information is
displayed.
 ‘URL/Camera function’: the webpage/camera will be displayed on the screen
 ‘PROSOFT function type’: the control panel displays additional control buttons for
the advanced control of the audio system, the dimmer, the heating/cooling
system…are displayed.
Normally you will need to touch the GUI item to display this 'Control Panel'. When you
want to have the control panel standard on the screen enable the 'Default Open' check
box in the 'Popup Window' area. Additionally you can set for Camera's and URL the
width and the height of the 'popup window'/ 'control panel'.
In the category 'All' the 'Default Open' items will only appear as icons, unless also the
option 'Default open at 'All' view' is marked.
 This option is only available in GUI+ (GUI will present 'default open' items
always as icons!).
For the 'Default Open' popup a popup position also needs to be entered. For the other
pop-up panels this is not mandatory. If you don't set up the position (position = auto);
the GUI will choose the most appropriate location.
 Only in the GUI+ you can position the not 'default open' panels manually.
252
TELETASK Handbook
GUISOFT
25. Creating a iSGUI
25.1. Start with the GUISOFT
Click on the GUISOFT button in the PROSOFT Suite bar at the left in the PROSOFT Suite
window. If you haven't created a GUI for this .NBT project, you will be asked to create a new
GUI. The GUI Selection screen will appear.
25.2. GUI Selection
Start with choosing the correct GUI type.
'TDS15105' GUI+: choose this GUI type for use on a Windows PC.
'TDS15101' iSGUI: choose this GUI type for use on a Smartphone, Tablet or PC. For
more info concerning creating an iSGUI, see next chapter.
 'TDS15100' GUI: choose this GUI type for use on an Apple or Linux (or windows) PC.


 For the iSGUI you can choose between:
 'Define the GUI manually': just like the GUI/GUI+ for PC, you can define the different
pages to your wishes. But for the iSGUI there is a quick and easy-to-use alternative.
 'Create the GUI based on the rooms and icons’: GUISOFT will by default define all
available domotic elements and organize them in the correct categories and rooms.
This is all based on the configuration in PROSOFT! After the automatic generation,
you are still able to change things about the configuration of the iSGUI.
 Once the GUI type is selected, it can't be changed!
 The GUI type has to correspond with the activated Licence type.
 The adjustments you make afterwards in PROSOFT are not automatically
implemented in the iSGUI configuration.
253
TELETASK Handbook
GUISOFT
25.3. iSGUI Features
In this start screen you can define the different pages of your iSGUI and you set up the connection
data. The GUI start screen looks like the figure here below:
The different iSGUI parameters which are defined are:
 ‘GUI Name’: give in a clear name for the iSGUI e.g. 'iSGUI Parents', 'iSGUI Children';
you have to give a name for the GUI.
 ‘Password protection’: check this mark to add a password when connecting the
iSGUI (to prevent unauthorised access to the iSGUI from people that have access to
the Wireless LAN). This user password can be changed any time in PROSOFT in the
“Users & groups” configuration menu.
 ‘IP setting’: With this setting the iSGUI uses the IP address entered on the target
device to connect to the central unit
 Only supported with iSGUI V2.5.
 ‘IP setting’: custom
 IP-address Central Unit: give in the IP-address of the Central Unit
 IP-Port number: give in the IP-Port number of the Central Unit (by default:
55956).
 To be used for iSGUI V1.
 ‘Define the new page’: using this button you can add a new page to the iSGUI. A
page can be any part of the house (a room, a floor, the garden, the complete house).
The pages do not have to correspond with the rooms you defined earlier in the
PROSOFT session.
 ‘Page Name’: give in the name of the page. This name will be visualised on the GUI.
 ‘Arrow up and Arrow down’: by using the arrow up or down you can change the
order of the selected GUI page.
 ‘Regimes’: mark this setting to protect the regime (workday, weekend, presence
simulation,…) buttons with password.
When you have defined all pages and set up all the communications settings correctly according to the
specific situation, click 'OK' to continue defining the iSGUI. The GUISOFT will appear on the screen.

You can always call the iSGUI property screen to change the page and communication
settings.
254
TELETASK Handbook
GUISOFT
25.4. GUISOFT Screen
The GUISOFT Screen is divided in 3 zones: the GUISOFT menu, the functions and the iSGUI
preview.
1
2
3
25.4.1. The GUISOFT menu
See the GUISOFT menu in the chapter concerning the GUI/GUI+.
25.4.2. The Functions
In the function library you page through the different domotic functions which were earlier
created in the PROSOFT session of the .NBT project. With the drop down menus of the rooms
and icons you can create search criteria to quickly find the wished function in the library.
25.4.3. The iSGUI preview
In the GUI preview you can see how the GUI would look like during daily use.
At the top of the GUI preview you see the actual page you have made earlier. When there are
more pages available, you can thumb through them by using the arrow left or arrow right. At
the left side of the GUI preview the different categories as known in PROSOFT are shown.
When you push these buttons the corresponding functions on this page are visualized. The
different icons are:
 ‘Lights’: shows the lights of the active page
 ‘Devices’: shows the devices of the active page
 ‘Moods’: shows the moods of the active page
 ‘Motors’: shows the motors (curtains, shutters, gates, etc.) of the active page
 ‘Sensors’: shows the sensor functions of the active page
255
TELETASK Handbook
GUISOFT
 ‘Audio’: shows the audio zones of the active page
 ‘Camera's’: shows the camera's of the active page
25.5. Adding items to the iSGUI.
25.5.1. Drag and drop.
After the iSGUI pages have been defined, you can add several domotic functions you have
earlier defined in PROSOFT in the iSGUISOFT screen using the easy and user friendly drag
and drop concept: drag the domotic functions out of the functions or symbols library and drop
them on the preview of the preview area.
25.5.2. Edit the iSGUI Icon
When you have dragged the function out of the functions library, the iSGUI icon is assigned to
the function on the iSGUI preview. However you can change the icon image settings. Right
click the iSGUI icon in the preview and select “Edit iSGUI Icon” from the drop down list. The
“Edit Item” window will appear on the screen.
256
TELETASK Handbook
GUISOFT
26. Creating a Control Tower
26.1. Terminology
 ‘Control Tower’: This is the equivalent of the GUI+ Runtime. This is the software in
which an operator can monitor and control the different connected Central Units.
 ‘Control Tower configurator’: This is the equivalent of GUISOFT in PROSOFT.
Within the ‘Control Tower Configurator’ the different Central Units are defined, the
audio messages for alarms are imported and the overview page with all the Central
Units is created.
 ‘Control Tower configuration’: This is the equivalent of the ‘GUI Data’. It contains all
information about the Central Units, the alarms and the overview page. But instead of
being part of a PROSOFT file, the Control Tower configuration is saved in a separate
Control Tower configuration file.
26.2. Workflow
To setup a Control Tower installation the following steps are essential:
 Define functions to monitor and control
 Create an initial PROSOFT file.
 Create a ‘Control Tower Configuration’
 Run the TELETASK Control Tower.
26.3. Define Functions to monitor and control
Before you begin the configuration of the Control Tower, you have to decide which functions you want
to monitor on all connected Central Units. These functions can be any type: relays, dimmers, sensors,
moods, alarms,… Charts are not accessible in the Control Tower.
For example: an ‘ALL OFF’ general mood, the HVAC system, …
Alarms are very useful functions for the Control Tower, they can provide the operator with information
on water leaks, HVAC system failure, fire alarms, etc.
26.4. Create an initial PROSOFT file
Once the list of functions to monitor from the Control Tower is complete, you can start creating an
initial PROSOFT file.
This file needs to contain:
 The necessary hardware for all the functions that need to be monitored from the
Control Tower (Relay, Dimmer, Motor modules, digital input interfaces, analogue
input interfaces,…)
 All functions to be monitored from the Control Tower (Moods, …)
 All common configuration (e.g if input X is closed, set alarm Y ON)
 A Control Tower client GUI. This is a GUI with only 1 page on which all the items
to be monitored / controlled by the Control Tower are placed.
 All the Alarms to be monitored on the Control Tower. For these alarms set the
type to ‘Alarm’ (not to Message). Pay particular attention to the number of beeps
for the alarms, the Control Tower uses this to define the alarm type. If desired the
Control Tower can play recorded voice messages for critical alarms (e.g. Fire
Alarm) so that even if the Control Tower operator is not looking at his screen at
that moment, he can still be informed through the audio message. So give each
alarm for which an audio message will be used a unique number of beeps (we
advise to use high numbers of beeps for this). If the Control Tower receives an
alarm with a number of beeps for which no audio message is present, the Control
Tower will simply play that many beeps. Make sure that the alarm is enabled on
the Control Tower client GUI.
257
TELETASK Handbook
GUISOFT
When the initial PROSOFT file is finished, save it for the different Central Units in the project. When
you start the configuration of the individual Central Units, start from this initial PROSOFT file and add
whatever is necessary. Create an individual .NBT file for each Central Unit.
26.5. Create a Control Tower configuration
A Control Tower configuration can be created on any PC, this does not have to be the PC that will run
the Control Tower. It is not necessary, but if possible advised, that the configuration PC can connect to
the different Central Units (this requires that the Central Units are already running and that the
PROSOFT files based on the ‘initial PROSOST file’ have already been transmitted to the different
Central Units).
26.5.1. Control Tower configurator screen
The Control Tower configurator screen.
1. The list of central units that are already added to the Control Tower configuration.
Click the Edit button at the bottom to add/remove central units to/from this list.
2. The list of alarms that are defined for this Control Tower. Click the Edit button at
the bottom to add/remove alarms to/from this list.
3. A preview of the overview page from the Control Tower Runtime. Click the Edit
button at the bottom to modify general Control Tower settings.
26.5.2. Define Central Units
The first step is to define the Central Units which will be monitored by the Control Tower. To do
so, click the ‘Central Units’ item in the edit menu (or the ‘Edit’ button below the list of Central
Units on the main Control Tower configurator window).
You will get a new window with an overview of all Central Units that are already defined in the
configuration (the first time, this list will be empty).
Click the ‘New’ button to add a new Central Unit. You will see the window below:
258
TELETASK Handbook
GUISOFT
A Central Unit is defined by a unique name for the Central Unit (e.g the number of the flat, the
address of the house,…), and the Url (or IP address) at which the Control Tower can connect
to the Central Unit.
For a central unit there are two optional information fields:
 Extra info: can be a (practical) unlimited amount of formatted text. Pictures can also
be added to this field, the maximum size for the pictures is 500x500 pixels, larger
pictures will be scaled while maintaining aspect ratio. This field can be visualized in
‘Control Tower’ on top of the main screen. Optionally the control tower operator can
modify information in this field during normal operation. This information field is saved
as a RTF file (Rich Text Formatting). These RTF files can also be created in external
programs (like Word). These files are stored at C:\ProgramData\TELETASK\Control
Tower\DoipInfo with the previously defined ‘Central unit name’ as filename.
 It’s advised that the externally created RTF files are smaller than 5MB. Files
larger than 10MB will not be loaded in the Control Tower.
At the bottom there is also information about whether the Control Tower configurator has
already downloaded the Control Tower Data for that Central Unit. When defining a new Central
Unit this will always be ‘not downloaded’. When finished click ‘OK’ to add a Central Unit with
259
TELETASK Handbook
GUISOFT
the given data. You will now return to the overview list and the Control Tower configurator will
try to download the Control Tower client data for the Central Unit.
After defining all Central Units, the overview may look like this:
For each Central Unit you will see the same information again: the name, the url and the ‘Data
state’. In this example the data for ‘House 1’ at url ‘192.168.0.83’ has been downloaded, for
the other Central Units the data has not been downloaded.
To retry to download the data for a Central Unit click the ‘Reload’ button. If the data for all
Central Units needs to be reloaded, click the ‘Reload All’ button.
26.5.3. Define Alarms
The next step is to define the alarms for which an audio message needs to be used. If you do
not want to use the audio messages, you can skip this step.
The recording of the messages itself is not done by the Control Tower configurator. There are
many tools available to do so (both free and commercial). The Control Tower supports the
audio formats .wav and .mp3.
To define the audio messages click the ‘Alarms’ button in the ‘Edit’ menu, or the ‘Edit’ button
below the alarms section.
In the alarms overview window you will see that there is already 1 alarm defined. This alarm is
a special alarm indicating that the connection to a Central Unit is lost (this can be caused by
network problems, Central Unit (power) failure, …). As this alarm is an alarm generated by the
Control Tower instead of coming from a Central Unit, the text for this alarm is defined in the
Control Tower configurator (for other alarms the text is defined in the PROSOFT file of the
dedicated Central Unit).
Preview of the ‘Define alarm’ window for the ‘No connection to Central Unit alarm:
260
TELETASK Handbook
GUISOFT
For this alarm, you cannot change the name, nor can you define an alarm type, but you can
set two lines of text for the alarm and browse for a corresponding audio message.
If no audio message is defined for this alarm, the Control Tower will not give any audible
feedback about this alarm.
For other alarms (the ones coming from a Central Unit) the ‘Define alarm’ window looks like:
261
TELETASK Handbook
GUISOFT
For these alarms you can define:
 Alarm name: This name is purely a description of the alarm and is only used in the
Control Tower configurator; it will not appear in the Control Tower itself.
 Alarm ID: This ID must match the number of beeps defined within the corresponding
alarm of the Central Unit where the alarm has been triggered (e.g. in this case the
Alarm that is switched on by the Central Unit when fire is detected needs to have 240
beeps assigned to it).
 It is highly recommended that you use a high ID number for alarms with a Voice
Message assigned to prevent a continuously beep in case the alarm has been
triggered.
 Extra info: can be a (practical) unlimited amount of formatted text. Pictures can also
be added to this field, the maximum size for the pictures is 500x500 pixels, larger
pictures will be scaled while maintaining aspect ratio. This field can be visualized in
the ‘Control Tower’ if an alarm is triggered. This fields can be used for procedures that
need to be followed when the alarms occur, useful phone numbers, … Optionally the
control tower operator can modify information in this field during normal operation.
This information field is saved as a RTF file (Rich Text Formatting). These RTF files
can also be created in external programs (like Word). These files are stored at
C:\ProgramData\TELETASK\Control Tower\AlarmInfo with the previously defined
‘Alarm ID’ as filename.
 Voice Message: Using the ‘Browse’ button you can browse for a Voice Message to
play for this alarm. With the ‘Play’ button you can have the Control Tower configurator
‘play’ the selected voice message.
After defining some alarms the Alarms overview window may look something like this:
Notice the ‘Voice Messages’ can be played directly from here (e.g. to verify that they are
correct). Also notice that for ‘Fire Alarm’ no voice message has been selected, in this case the
Control Tower will play 240 beeps when a fire alarm is received (when no voice message is
needed for an alarm, it is not necessary to add the alarm to the Control Tower configuration. It
can be useful though if in a later stage a voice message for that alarm is required).
26.5.4. Control Tower settings
Now the Central Units and alarms are defined, the actual Control Tower configuration can be
done. The first step is to set some general Control Tower settings. To do so, click the
‘Overview Page’ item in the ‘Edit menu’ or click the Edit button at the bottom of the page.
If you already have configured a GUI+, the settings on this page will look very familiar:
262
TELETASK Handbook
GUISOFT
 Target device resolution: the screen resolution of the device on which the actual
Control Tower will run.
 Run Control Tower full screen: whether the Control Tower needs to run full screen
or in window mode
 Audio feedback on touch/click: whether a sound needs to be played when an item
in the Control Tower is touched / clicked.
 Extended alarm/central unit info is editable by Control Tower Operator: Enable
this if the operator may change the Extra Info of the alarms and central units.
 Page name: the name that will be displayed for the overview page in the Control
Tower configurator.
 Page preview: Use the ‘Select Image’ button to select a background image for the
overview page (notice the recommended size for the image is displayed above the
preview for the image).
263
TELETASK Handbook
GUISOFT
26.5.5. Add Central units to the overview page
The main Control Tower configurator window will now look like this:
On the left you see the different Central Units defined in the configuration. To add a Central
Unit to the overview page, simply drag the Central Unit from the list to the overview page and
drop it to the overview page. A Central Unit can only be added once to the overview page, if
you add a Central Unit to the overview page again, the existing item for the Central Unit on the
overview page will be deleted. The
symbol next to ‘House 1’ and ‘House 2’ indicates that
these Central Units have already been added to the overview page House 3 is not yet added
to the overview page.
To customize the layout of a Central Unit item on the overview page, right click on the Central
Unit item and select ‘Edit item’ from the context menu.
On the new window that appears you can set the size for the Item, the exact location and if
necessary the appropriate location to display a text for this item.
TIP: the Control Tower configurator will use the last Width, Height and Text Location in this
window as default values for the next Central Units you drag on to the overview page. So if
you would like the Width and the Height for all Central Unit items to be 72, drag the first
Central Unit on the overview page, and change the size. When you drag the other Central
Units on the overview page their size will now be set to 72x72.
264
TELETASK Handbook
GUISOFT
26.5.6. Saving and opening a Control Tower Configuration
To save a Control Tower configuration, click the ‘Backup current configuration’ item in the ‘File’
menu. The Control Tower will now save all settings, including Control Tower client data
(received from the Central Units), Voice Messages and overview page background image to
one Control Tower configuration file.
When you open the Control Tower configurator it will automatically open the last Control Tower
configuration used on that pc. To open a different one, simply click the ‘Restore configuration
from backup’ item in the ‘File’ menu.
26.6. Event logs (alarms)
Every event is logged in a file on the Control Tower PC. The location of this file is:
C:\ProgramData\TELETASK\LOGS\Control Tower.
This events log file will contain:
 Trigger date and time
 Type of alarm,
 Who has cleared the alarm (operator or central unit)
 The date and time when the alarm was cleared
 The central unit on which the alarm occurred
The active alarms are visible in the Control Tower runtime in the ‘Active’ tab and the cleared
alarms can be seen in the ‘History’ tab. The history list is a list of the last 1000 alarms. The
alarms that have happened before, are stored in the log file on the computer.
265
TELETASK Handbook
GUISOFT
27. Get the GUI ready for use.
27.1. Importing an activation file.
For each GUI/GUI+/iSGUI you need to buy a license. You can buy a license from your local distributor.


One you have received the activation file for the licence, you have to import this
in the .NBT file. See Chapter 'Licences'.
Send the .NBT file to the Central Unit. See chapter 'Send' in PROSOFT.
27.2. Exporting the GUI files (only for GUI)
When the GUI is completed you need to create the GUI files. These GUI files need to be copied to the
target device on which the GUI will run. To create the needed GUI files follow the steps below:
 Save the '.nbt' project
 Select 'Communication' in the menu.
 Select 'Create GUI files (active GUI only)' in de drop down menu.
 You will be asked to choose a location where the GUI files will be saved. At this
location a folder with the name of the GUI will be made. This folder needs to be
copied to the target device on which the GUI will run.

Exporting of the GUI files is not needed when you use an iPhone, iPod Touch, iPad, here the
iSGUI will download the data straight from the Central Unit.

Exporting of the GUI files is not needed when you use an GUI+. Here the GUI+ will download
the data straight from the Central Unit.
27.3. Install 'GUI Runtime'
Before you can use the GUI on the specified target device, you have to install the 'GUI Runtime'. You
can download the latest version from www.teletask.eu.
27.3.1. GUI/GUI+


Download the latest version of the GUI/GUI+ installation program from
www.TELETASK.eu
Start the installation program (setup.exe) on the target device and go through the
complete installation.
27.3.2. iSGUI (iPhone, iPod Touch, iPad)

Download the TELETASK iSGUI V1 or V2.5 application by using the Apple App
Store.
27.3.3. iSGUI (Android)

Download the TELETASK iSGUI application by using Google Play.
27.3.4. iSGUI (BlackBerry)

Download the TELETASK iSGUI application by using BlackBerry World.
27.3.5. iSGUI (Windows PC, macOS)

Download and install the Adobe AIR platform from www.adobe.com.
266
TELETASK Handbook


GUISOFT
Download the latest version of the iSGUI installation program from
www.TELETASK.eu
Start the installation program (iSGUI.air) on the target device and go through the
complete installation.
27.3.6. Control Tower


Download the latest version of the Control Tower configurator installation
program from www.TELETASK.eu
Start the installation program (setup.exe) on the target device and go through the
complete installation.
27.4. Copy GUI Files to the target device
27.4.1. iSGUI (iOS, Android, BlackBerry, Windows PC, macOS)




Connect your device with the network which is connected with the Central Unit.
(See features of the device).
Start the iSGUI application.
The iSGUI will ask for the IP address of the Central Unit. Make sure you put in
the correct IP address.
The GUI data files will automatically be installed on the device.
 If you have added/changed items/pages in the iSGUI configuration (Using
PROSOFT Suite) you need to ‘Reload’ the GUI Data on your device to see
the new items. To do this:



Transmit your .nbt file to the central unit (PROSOFT Suite)
On the start screen of iSGUI press the settings button in the lower right corner
Click the ‘Reload GUI Data’ button
27.4.2. GUI+ (MS Windows)




Connect your target device with the network, connected to the Central Unit. (See
features of the device).
Start the GUI+ application.
The GUI data files will automatically be installed on the device.
The GUI+ will be automatically updated (when a new .nbt file has been
transmitted to the central unit).
27.4.3. GUI
After the GUI Runtime installation on the target device, a folder 'TELETASK GUI' will be added
at 'C:\' (or another location if you have specified it during the installation of the program).
 To this 'GUISOFT' directory you need to copy the 'GUI data' folder of the
concerned GUI which you have created in PROSOFT Suite (See export GUI
files).
27.4.4. Control Tower

See chapter ‘Creating Control Tower’
267
TELETASK Handbook
GUISOFT
27.5. Problem Solving
'GUI/GUI+'
 When a message box appears with the remark that no license is available for the
device
 Check the license codes in GUISOFT or buy a GUI license.
 Check whether you have copied the 'GUI data' directory to the correct location on
the target device.
 If the GUI does not start up and only a small black screen appeared very fast on the
screen you probably have not the correct Java Runtime Environment (JRE). To run
the GUI, you need JRE 1.5 or later on the target device to run the GUI properly. (only
applicable for the GUI, not for the GUI+).
 A sensor or audio zone does not appear on iSGUI.
 Check if the audio or sensor zone is assigned to a room (menu edit  rooms).
28. Video door phone/Intercom on GUI+ and
MAIOR Video door phone on GUI+ (TDS12052 and
TDS12053 only).
The TELETASK MAIOR (TDS12051, TDS12052 and TDS12053) is a “built in” PC with touchscreen
designed for GUI+. Besides the standard GUI+ functionalities, the TELETASK MAIOR also offers the
possibility to integrate an IP based video door phone system (TDS12052 and TDS12053 only).

Video door phone/intercom integration is also available on other touchscreens running GUI+ (if
they are equipped with a microphone and speakers).

This chapter contains instruction specific for MAIOR touchscreens, but integrating video door
phone / intercom on other touchscreens is similar.

Analogue video door phone systems can be integrated with TELETASK GUI+ if they are
converted to IP (see TDS10119).
The steps necessary for video door phone/intercom integration are:
 PROSOFT SUITE:
 Create IP cameras / Doors and Intercom stations (in the remainder of this chapter
both the door units and the Intercom stations will be referred to as ‘stations’,
unless the info is specific for one type of station.)
 Create a GUI+ for TELETASK (MAIOR)
 Add the Video door phone icon (optional)
 GUI+:
 Set up VoIP server and VoIP user
 Assign fixed IP to MAIOR
28.1. PROSOFT SUITE
28.1.1. Create IP cameras / Doors
See chapter “Cameras & Doors” under PROSOFT – Starting a project for detailed instructions.
268
TELETASK Handbook
AV-SOFT
269
TELETASK Handbook
AV-SOFT
28.1.2. Create a GUI+
The creation of a GUI+ configuration for a TELETASK MAIOR is similar to the creation of
another GUI+. Only the ‘Target Device resolution’ needs to be set to ‘TDS12051 MAIOR’,
“TDS12052 MAIOR” or “TDS12053 MAIOR”.
28.1.3. Add the video door phone item (optional)
By default the video door phone screen is displayed on the first GUI+ page (favourites) at the
moment someone rings the bell. After the conversation the video door phone screen
disappears again (when changing the page or executing another function on the GUI+).
If you would like to have the video door phone screen appear on another page or you would
like to use the intercom functionality, you can add the video door phone screen manually on
GUI+.
To do this select the icon “Camera and URL” and drag the video door phone image to the
desired place on the desired page.
270
TELETASK Handbook
AV-SOFT
The screen ‘Edit GUI Item’ opens automatically. Here you can change the image, the icon and
the ‘default open settings (like for any other GUI Item).
 REMARK: you can add the video door phone icon only once per GUI+ configuration. If
you delete the item, you can add it again (e.g. on a different page).
271
TELETASK Handbook
AV-SOFT
28.2. GUI+
28.2.1. Set Up VoIP server and VoIP user
For VoIP you need a VoIP server, this server acts as PBX (telephone exchange). Each device
that makes a connection on this server is a VoIP client.
The TELETASK MAIOR comes with a pre-configured VoIP server installed. If another VoIP
server is already present (e.g. in a hybrid analogue/VoIP telephone exchange) the VoIP server
in the TELETASK MAIOR is not needed. But if no VoIP server is present, no extra costs need
to be made for this.
If two or more TELETASK MAIOR devices are placed in the same installation, one of the
TELETASK MAIOR devices will act as VoIP server.
In the VoIP server on TELETASK MAIOR the following numbers are available:
 101-110: Numbers reserved for TELETASK MAIOR devices
 901-910: Numbers reserved for door units.
To configure the VoIP server and user on the TELETASK MAIOR start your GUI+, go to the
locations screen and click the ‘Settings’ button at the bottom.
Enter the VoIP server address and the VoIP User.
If the TELETASK MAIOR for which you are configuring the VoIP server is the VoIP server
itself, you can leave the address on 127.0.0.1 (this is the case if you have no other VoIP server
present and only one TELETASK MAIOR). In other cases add the IP address of the VoIP
server.
The VoIP user can be 101-110 (if the TELETASK MAIOR is the VoIP server).
272
TELETASK Handbook
AV-SOFT
28.2.2. Assign a Fixed IP address to MAIOR
If the MAIOR is used as VoIP server it is important to assign a static IP address to the MAIOR
touchscreen. Assigning a static IP address to a MAIOR touchscreen is the same as assigning
a static IP address to a Windows XP computer. But the MAIOR touchscreens are equipped
with special software to protect them from undesired (spyware, viruses) / incorrect (during
installation) changes to the operating system. When the MAIOR restarts all changes to the
operating system, including changes to the IP settings, are lost unless the MAIOR is restarted
using this special software.
After the IP address is changed to the correct static one, and the VoIP system is tested, use
the “call ewf tool” available from the “start” menu on the MAIOR to permanently save the
settings.
273
TELETASK Handbook
AV-SOFT
AV-SOFT
29. Multi-Room Multi-Source
29.1. Introduction
Making a multi-room multi-source system with full flexibility in quality, budget and features. From a few
rooms with back-ground music to the perfect and fully integrated home theatre.
To realize the integration of audio/video with the RS232 universal AV interface in a fast and correct
way, it is necessary to use a phased set-up. The different phases may look different than you would
expect at first sight. Start at the right with '1' on the figure below and step to the left to finalize the
installation process.
There are four phases to be distinguished:
1. Define the desired audio configuration: In this phase you will have to define the
used audio/video sources and amplifiers and how audio/video source signals are
connected to the amplifiers
2. Assigning the RS232 port and the IR flashers (infrared transmitters: 8 flasher
outputs/interface): In this phase each IR flasher is granted to an audio/video
component (sources and amplifiers).
3. Configuring the RS232 universal AV interface: In this phase, the interface is
configured to be able to control the multi- room multi- source audio system.
4. Configuring the audio/video buttons of the domotics installation: In this phase, the
different audio/video functions are defined on the necessary buttons in the
TELETASK system.
The four different phases from above are explained one by one in the text below, but first we give
some explanation about multi-room and multi-source
274
TELETASK Handbook
AV-SOFT
29.2. Multi-room/Multi-source: the differences
When you want to listen to different audio sources (tuner, CD, MP3, …) in different rooms at the same
time, you will need a power amplifier for every room (or better: 'audio zone'). This is called a 'multi
source – multi room' system. If you always have the same source in the different rooms at the same
time, this is called a 'multi room' system. The difference between these two kinds of audio installations
is shown in figure below.
Today there are several power amplifiers with built-in audio sources. In small tower systems you have
all common sources built-in, but even some higher range power amplifiers may have a built in radio
tuner or hard disk. The most important and typical feature of such systems, is that the built-in sources
are not to be shared with other power amplifiers. You can find a comparing illustration in figure 5.
Depending on the requirements of the user and the available budget, there is to be chosen for internal,
external or a mix of internal/external audio sources.

Remark: The tuner is a typical source where different persons listen to different broadcasting
stations at the same time. That is why it is particularly interesting to have several tuner
sources available at the same time. A good combination is to have every power Amplifier (for
every audio zone or room) equipped with a built-in tuner. This kind of amplifier/tuner
combination is easy to find and available at most of the brands.
275
TELETASK Handbook
AV-SOFT
29.3. Phase 1: Choose the wanted audio/video configuration
29.3.1. Define the requirements
The RS232 universal AV interface is able to control about all audio/video systems available on
the market.
Example: A TELETASK client wants music in the kitchen, the living room and the bath room.
He wants to be able to listen to the radio in the different rooms. In the living room and in the
kitchen, he wants to listen to the DVD player and he also plans to buy a MP3 player with three
streams (= up to three songs played at the same time).
The requirements of the user can be summarized in the table.
Based on the requirements of the user, the necessary audio components can be defined and
brought into a configuration drawing. For the used example, the schematic drawing should be
like in the figure above.
 When you select the components which you want to integrate through IR
with the domotics system, you need to take care about:
 The frequency can be between 36 – 38 KHz (most common) or 455 KHz.
 !!! The used audio components must support the so called 'discrete on/off codes'. A
discrete ON code, switches the audio component to ON. When the component is
already ON, when sending the discrete 'ON' code, the system stays in the ON status. A
discrete OFF code, switches the component to the OFF status. When the system was
already in the OFF status, it remains in that status.
 VERY IMPORTANT: Not all brands support these 'discrete ON/OFF' codes and within a
brand there are components which support these codes and other components which
do not. Therefore always ask your supplier if the device can process the controllable
infrared 'discrete ON- and OFF' codes. Also ask if these codes can be generated by the
remote control, so you can learn them to the RS232/learnable IR interface which needs
these codes for obvious reasons or if the HEX codes are available.
276
TELETASK Handbook
AV-SOFT
 When you select the components which you want to integrate through
RS232, take care about:
 The serial communication of the devices should work on one of the following
Baudrates = 9600 / 19200 / 38400 / 57600.
 The interface is always working with no parity, no handshaking, 8 data bits and 1 stop
bit.
 When you select the components which you want to integrate through IP,
take care about:
 Socket based serial HEX or ASCII string
 No high level protocols (http, xml, json,…)
 Like for the IR codes there should also be support for 'discrete on/off commands'
The protocol of the device should have a different string for ON and for OFF.
 To implement feedback codes, it is important that the receive code of the selected
device contains the information as well as what this information is about. E.g.: If you
would request volume feedback, the receive code must say: volume 50 and not just 50.
In our example the configuration drawing leads to the next set of audio components:
 3 separate power amplifiers with each having their own internal tuner: these
amplifiers are used to be connected with the speakers in the living room, the kitchen
and the bath room. The TELETASK RS232 universal AV interface will control the
different sources and amplifiers. In every room it is possible to listen to any tuner
frequency, independent from the other rooms.
 Remark: Although the user asked to be able to listen to the radio, you can offer
him an unlimited and independent radio choice. This solution is to be preferred,
because most home audio amplifiers for background music applications are
only a limited percentage more expensive with an included tuner. The final cost
of this may even be less expensive when compared to three power amplifiers
with one separate tuner.
Nevertheless, you may not forget to provide the necessary antenna amplifier /
splitter to provide the necessary tuner signal to the different tuner inputs of
every amplifier/tuner unit. In this example case, you need an antenna
amplifier/splitter with at least 3 antenna outputs.
 1 x DVD player: This one is external and is connected to the audio signal inputs of
both power amplifiers, to be able to listen in the different rooms to the DVD player
source.
 1 x RS232 MP3 player with 3 streams: This one is also an external audio source, to
be connected to every power amplifier. These can contain a huge number of music
tracks.
277
TELETASK Handbook
AV-SOFT
As soon as you have selected the necessary audio components, you can start setting up the
configuration drawing.
It is absolutely necessary to take good care for the making of this drawing. This will become an
important tool to obtain the final solution smoothly.
Optionally you can add the brand and type of the audio component to the drawing.
As soon as the audio configuration reaches its final version, half of the work is done.
Only with an excellent drawing in your hands, you can go for the next step.
This drawing is also necessary to guarantee the support of TELETASK support service.
278
TELETASK Handbook
AV-SOFT
29.4. Phase 2: Assigning the RS232 Port and the IR flashers.
With only the audio configuration, the audio system is not yet integrated. Therefore a connection must
be made with the TELETASK home automation system by interfacing the audio components with the
TELETASK RS232 universal AV interface. The pluggable IR flashers will generate the necessary
infrared signals for the audio components to be controlled.
Every audio component should get one IR flashers to transmit to his built-in IR receiver. Indicate the
flasher numbers on the configuration drawing.
Alongside of the IR flasher numbers, it is necessary to write down the audio related terms on the
drawing. Because of the evolution in the audio world, there can be confusion between traditional audio
terms like 'TAPE', 'CD', 'TUNER'; these are mentioned on the amplifier inputs and on the concerned
components sources which are connected to them. As an example, the MP3 player source is
connected to the VIDEO 1 input on the audio power amplifier.
Because audio integration was already possible at the beginning of domotics age, the traditional audio
terms are used. This may cause confusion. Therefore it is possible that the BLU-RAY drive is
controlled with the 'CD' button on the TELETASK remote control. Therefore it is necessary to clean-up
these confusions right from the beginning.
You will understand that the printed audio functions on the TELETASK remote control are fixed, so the
traditional audio source names are to be used 'FM' 'CD' 'HDD' 'MP3' 'DVD' 'VID' 'SAT' 'AUX'. You find
our clarifying example here below.
279
TELETASK Handbook
Sources
SRC 1
SRC 2
SRC 3
SRC 4
SRC 5
SCR 6
SCR 7
SCR 8
AV-SOFT
REMOTE CONTROL
FM
CD
HDD
MP3
DVD
VID
SAT
AUX
PROSOFT & Touchscreens
FM
DVD
MP3-1
MP3-2
MP3-3

The name on the Remote Control can't be changed.

But in PROSOFT you can choose the name you want to use for each source, a big advantage is
the fact that this name also will appear on your screen, your GUI and even your iSGUI.
PROSOFT will use your chosen name in the whole program.
With the assigning of the IR flashers and the RS232 Port and the clarification of the possible confusion
between audio terms, the schematic drawing is now finalised. In the next phase, this schematic is
used to integrate the whole installation into the TELETASK 'AV-SOFT' software.
280
TELETASK Handbook
AV-SOFT
29.5. Phase 3: Configuring the Universal RS232 AV or IP
interface.
After the two first phases, now is the time to program the RS232 universal or IP AV interface with A/VSOFT. With the configuration drawing at hand, it should be easy to walk through this third phase. The
configuring phase is divided in the following steps:
29.5.1. Assigning IR codes, RS232 strings or IP strings
Assigning IR code, RS232 strings or IP strings to the different components and their functions.
 Start PROSOFT and go to AV-SOFT.
 Select 'Edit' - 'Edit AV-SOFT Library'.
 You now see a list of pre-configured audio devices. If your device is listed go to
the next step.
 If not, add the new device(s) you need. For detailed information on how to do this,
see the chapter 'Edit AV-SOFT Library'.
29.5.2. Entering the audio configuration in AV-SOFT

Click 'NEW', and select the correct 'A/V - Interface' type.

At the top of the window you can set general properties about the AV interface
(name, AUTOBUS or IP address).
281
TELETASK Handbook
AV-SOFT
29.5.3. Assigning Sources
We strongly recommend to start with assigning the sources of the AV devices (multi-source),
followed by assigning the zones where these devices have to be active (multi-room).


Click on the button 'ADD DEVICE' at the RS232 port.
There will be a pop-up screen, named: 'Select audio device'. In this library you
chose the brand and type of audio device you want to connect with the RS232
universal AV interface. (e.g. Russound – SMS3). Click OK.

Now you can give the different sources a name: MP3-1, MP3-2, MP3-3
282
TELETASK Handbook

AV-SOFT
Then you can go to the correct flasher and do the same exercise for the JVC
DVD (flasher 1 was assigned to the JVC-DVD player).
 DON'T forget to save your files!
29.5.4. Assigning Zones
After having configured the different sources, you can now add the devices with different AV
zones.
 Choose a flasher and add the correct device to this flasher as you have done with the
sources.
 You can now enter a name for the audio zone, the internal tuner, connects the
sources to the correct input (example below shows the configuration for the bathroom,
as decided in phase 2, no source is connected to the second input).
29.5.5. Configuring the RS232 universal AV interface.
As soon as all IR codes are assigned to the total configuration, the memorized information can
be transmitted from the PC to the TELETASK RS232/IR learnable audio interface.
Therefore the RS232 universal AV interface should stay connected with the PC through the
RS232 connection.
If you don't have an RS232 COM-port on your PC, you can use the USB to RS232 interface
from TELETASK (TDS10117) to connect to the PC (USB). Be aware that the RS232/learnable
IR interface is powered through the applied mains adapter. In the figure below you can find the
schematic set-up.
283
TELETASK Handbook
AV-SOFT
If the connection is properly done, you can send the necessary AV-SOFT data which is stored
in the PC memory, to the interface:


Click on the 'Communication' button in the main menu bar of AV-SOFT.
Click on the 'Transmit to interface' button.
 As soon as the communication is completed, the interface is ready to be disconnected
from the PC and to be connected to the AUTOBUS.
 The data in the RS232/IR interface is stored in non-volatile memory, so even if the
interface is disconnected from the power supply it will still have the correct data when
it is connected again.
29.5.6. Configuring the AV-IP license.
For TDS15240, no additional configuration is needed. When you’re done, transmit the .nbt file
to the central unit.
29.6. Phase 4: Configuring the audio buttons of the domotics
installation.
You can assign the buttons or inputs to the required audio function.
284
TELETASK Handbook
AV-SOFT
If needed, assign an audio zone for this interface in the 'Audio zone' field. If you use the Audio buttons
on your TELETASK remote control (TDS12502) with this interface, the selected Audio zone will be
controlled.
Next click on the button which you want to use and choose the 'audio' function as the type of function,
plus the audio code you want to be generated (for example) 'start CD' (if available; the list is based on
your list of learned codes).

REMARK: if you configure a button like this, you will always control an AUDIO ZONE not an
AUDIO SOURCE, if needed the zone will relay the information to the correct source. Example: if
you select 'Living' and 'DVD', the Central Unit will relay the necessary commands: 'SWITCH ON
to zone living' + 'SELECT INPUT DVD to zone living' + 'PLAY to source DVD'.

In some rare cases you may want to control the source itself, this can be obtained with the
'Send IR/RS232 code' function (for normal use this is NOT recommended!)
285
TELETASK Handbook
AV-SOFT
30. Edit library
30.1. Add and edit devices into the library.
30.1.1. General setup
When you want to add or edit a device in the library, follow the next procedure:

Click on the Menu: 'Edit', 'Edit AV-SOFT Library'
You will see the list of devices of the TELETASK library and the user library (per brand). On
the right side of this screen you find four buttons: NEW, EDIT, COPY and DELETE. The
functions of these buttons are:
 NEW: you want to add a device which isn't in the list
 You need to enter the Brand and the Type of the device.
 You have to choose between two possibilities:
 Serial RS232, for devices connected through the serial port
 IP, for IP based devices
 IR, for devices controlled trough an Infrared flasher
 EDIT: you can edit the devices you have added yourself.
 Editing of a device out of the TELETASK library is NOT possible!
 When you need to make changes to a device from the TELETASK library, you
can create a copy of a device from the TELETASK library give it a new name and
then edit this device.
 COPY: you can copy a device and just modify the desired features
 DELETE: you can delete a device you have made.
On the bottom you can also see the features and some comments of the chosen device for
your information.
286
TELETASK Handbook
AV-SOFT
After choosing the correct device or after creating a new device you arrive in the screen:
'Define AV device'.
In this screen you can first add or adjust your personal comments for the chosen device in the
box:
 Comment: This information will be stored and you will see it each time you chose to
add this device.
Then you have to choose which type of device you want to configure:
 Amplifier: If the device is an amplifier (or more than one);
 Source: If the device is a source (or more than one);
 Other: (for non-audio devices);
When you choose to add or edit an amplifier you have to check the following options:
 Number of amplifiers
 Amplifier controls sources
 This means that the device has his own system to control the connected
sources (the sources will not need to be entered in AV-SOFT).
 When you check this box you get following extra options: PLAY-STOPPRESET+-PRESET- PRESET 0 -10 for each zone.
 Device has internal sources (e.g. a tuner)
 If so, check the box and give the number of internal sources.
When you choose to add or edit a source you have to enter the number of sources (e.g 1 for a
normal tuner, 3 for an MP3 player with three audio outputs).
 REMARK: you will not be able to change these settings later, if you want to change it
you will have to make a copy of the device.
Depending on the kind of device (RS232 or IR), you have to define some additional settings.
See the specific sections for those devices.
In the main part of the window you will have a tab-page for every amplifier, source or other
device (e.g. if you have created an AV-device with 4 amplifiers and 3 internal sources, you will
have 7 tab pages). On the different tab-pages you can enter or record the codes for that
specific amplifier, source or other device.
287
TELETASK Handbook
AV-SOFT
30.1.2. Types of Codes
The codes you can enter in AV-SOFT can be divided into three categories:
 Send codes
(required)
 Feedback codes
(optional)
 Polling codes
(optional)
‘Send codes’ are codes that are transmitted from TELETASK to the AV-device. ‘Send codes’
are available on IR, RS232 and IP. Per device type a different set of codes is available:
Amplifier functions
ON
OFF
SELECT SOURCE 1-8
VOLUME UP and DOWN
VOLUME SET 0-100%*
MUTE
Source functions
PLAY
STOP
NEXT
PREVIOUS
PRESET 0-9
EXTRA 1-10
Other functions
Code 1-40
* only available for IP devices
‘Feedback codes’ are codes that are transmitted from the AV-device to TELETASK. These
codes are only available on RS232/IP devices. This code can contain information from the
amplifier or source:
Amplifier info
Zone number *
Power status
Volume level
Source info
Source number*
Track or RDS info, Line 1
Track or RDS info, Line 2
Active source
* This is required for each code.
‘Polling codes’ are codes that are transmitted from TELETASK to the AV-device. These
codes can be used to request a status from a source or amplifier. They are only useful if the
feedback codes are defined. Some devices do not require polling codes, they send their status
automatically. ‘Polling codes’ are only available for RS232/IP devices.
288
TELETASK Handbook
AV-SOFT
30.2. Record IR codes
For an IR device you have to define which carrier frequency is use by the device: 36-38 kHz or 455
kHz (most devices use 36-38 kHz).
To record an IR code follow the procedure below:
 To be able to learn the IR-codes to the RS232/learnable IR generator unit, the unit
should be connected to the PC trough an RS232 cable. Alternatively this can be done
to the USB port of your PC. Therefore you will need the TELETASK RS232-USB
convertor.
 You are ready to record the IR-code. Make sure that both the audio remote control
and the TELETASK RS232/learnable interface are close at hand.

Select the correct function and then click the 'RECORD Code' button on your PC
screen.
 AV-SOFT will display a window with the 'connecting to interface' message. Prepare to
activate the button of the appropriate audio function on your audio remote control.
289
TELETASK Handbook

AV-SOFT
Hold the remote control about 30 cm (1 foot) away from the (dark red) transparent
front plate of the TELETASK interface.
 The 'Connecting to interface' screen changes into a window displaying 'Press remote
control now!' Then (you will see that the 4 led indicators on the interface front panel
are blinking) press on the remote control button you want to record in the TELETASK
interface. Only during the blinking of the 4 led's a code can be captured. When you are
too late you will have to try again.
 When the code is recorded, a message appears on the PC screen. Click on the OK
button.
 If something is not correct, a message will indicate that no code was recorded.
In this case, you can click on the 'Record code' again to try once more.
 After the code is properly recorded, the new code is added to the chosen function.
E.g. function SELECT SOURCE 3 corresponds with HDMI on the remote control.
Please fill in HDMI in the name field of this function.
 At the bottom of this screen: 'Recorded codes' a graphical representation of the
learned IR-code is displayed. This visualization has two purposes:
 It gives a visual control of the recorded code. When a non-expected pattern is
displayed, there may have been a disturbance while recording the IR signal and
the code will have to be recorded again.
 Remark: Even a minor error in the code can disturb the working of the
recorded code. If the pattern is not looking 'normal', we advise to learn the
code again.
 When you move the Mouse pointer over the graphical code pattern on the PC
screen, the pointer will become scissors. You can also see that a part of the
pattern becomes red. If you click on the left mouse button, the recorded IR- code
will be cut (the red part will disappear). This function is particularly useful to tune
codes to each other. This is important for functions like 'VOLUME UP' and
'VOLUME DOWN'. When arranging with the cut function you can make sure that
there is an equal number of IR blocks (for example 3), for both the volume up –
and volume down function so there will be the same volume level change for up
and down. This results in a better control as if the number of IR-blocks would be
different.
 Repeat the former steps for every Infrared code which is to be learned.
 When you need two or more infrared codes for one command click the 'chain' symbol
next to the name of the function. You will see a menu where you can add a new code
or a time to wait between two codes.
 To test if a code was recorded correctly select the code and press the 'Test IR code
on flasher' button. The code will now be send to the selected flasher and your device
should respond as expected. If your device does not do anything or does something
other than expected there may be something wrong with the IR code, please record it
again. If you have chained more than one function (and waits) all chained codes will
be sent to the device in the correct order and the wait times will be respected.
When all new infrared codes are memorized in the system, you can close the 'Record IR
Codes' window by clicking on the 'X' button in the upper-right corner. Now you are back in the
main window of AV-SOFT. This is the way to learn every infrared code. It makes the
TELETASK RS232/IR generator a unique interface at an affordable price level.
290
TELETASK Handbook
AV-SOFT
30.3. Paste IR codes
On the internet there are several libraries with IR codes in standard HEX format. You can copy these
codes there and paste them in the corresponding field of AV SOFT.
This is very convenient when certain codes can't be sent out by the remote control (e.g. discrete
ON/OFF codes).
If you have a device with multiple internal sources, the codes for preset 0 – 9 are probably the same
for all these sources. In that case you can just copy paste the recorded codes from one tab page to
the other.
30.4. RS232/IP
30.4.1. RS232/IP ‘send codes’
For an RS232/IP device you have to choose whether you will enter the codes in HEX or in ASCIIcode. If you select ASCII you can also select if a code should end with a Carriage return and/or a Line
feed.
For RS232 you also have to select the Baudrate: 9600, 19200, 38400 or 57600.
For IP you need to enter the IP port number.

All these settings are depending on the brand and type of device you are adding, refer to the
documentation of the manufacturer of the device.
 In the field display name you can enter a name (optional). You will see this name
when you configure the device in PROSOFT.
 For the functions 'SELECT SRC X' it is advised to enter the name of the input of the
device (if there is a mark on the device with AUX2 then type 'AUX2' in the display
name field).
 Then enter the HEX-codes or ASCII, which are described in the protocol of the device.
 It's possible to copy similar codes, so you only have to adjust the values where
needed.
 Next to the function you will see a 'chain-symbol'; if you click on it you can add a
second code to the chosen function. You can add up to 10 codes to one function. (e.g.
to add waiting time between 2 codes).
For RS232: at the bottom of this screen you can test the code by clicking on 'Test code from PC port':
There will be a test between your PC and the device without any interfering of the TELETASK
hardware.
For IP: at the bottom of this screen you can test the codes by selecting a code and click on ‘Send’.
You will also see the data received from the IP device.
After testing, click ok.
291
TELETASK Handbook
AV-SOFT
Your codes will be automatically saved in your custom AV-SOFT library 'custom3.3.irdb' file in
directory C:\ProgramData\TELETASK\PROSOFT. Whenever you make modifications or create new
AV-devices in your project, this file will be updated. The AV-devices that are inside your project will
also be saved inside the .nbt file.

REMARK: Be aware that your custom AV-SOFT library on your PC will be synchronised with
every .nbt file you open. If you would open an .nbt file which has an AV-device with another
configuration as on your AV-SOFT library from your PC, PROSOFT will ask you if you want to
keep the device from your library or use the one from the .nbt file with as option to make a
backup from the AV-device from your library.

REMARK: PROSOFT versions prior to PROSOFT 3.3.0.60 use the custom.irdb file. PROSOFT
will automatically create a copy of this file and save it as ‘custom3.3.irdb’ for use in newer
versions.
30.4.2. Feedback Codes RS232 and IP
 General
For an RS232 or IP device you can define feedback codes. This is optional but advisable if the
AV-device is also controlled directly (e.g. using the remote control from the device or an app
on a smartphone or tablet) or if you want to automatically display AV feedback (like volume
and track number) on a TELETASK display (like AURUS-OLED (PLUS), AURUS-TFT, etc.).
The data that can be received from an AV-device is:
 The power status of a zone (ON or OFF)
 The currently active source on a zone (source 1-8)
 The volume of a zone (0-100%)
 Two lines of track info or RDS info from a source.
 The TDS14042 supports up to 6 Feedback codes to receive this info from the AV-device.
 For the TDS15240, there is no limit on the number of the feedback codes.
To define ‘Feedback Codes’, check the option ‘Feedback codes’ and click the ‘Edit’ button.
You will now see the ‘Feedback codes’ window:
292
TELETASK Handbook
AV-SOFT
In this window there are two tab pages. One for the ‘Feedback codes’ and one for the ‘Polling
codes’ (which will be discussed in the next chapter).
At the right there are three buttons to create a new ‘Feedback code’, to edit an existing one or
to remove a feedback code.
At the bottom you need to enter a ‘Start of code character’ and ‘End of code character’. You
can enter an ASCII character or a hex code in this field. E.g. if you have an ASCII protocol in
which the codes starts with a ‘*’ and ends with a carriage return, you can enter * in the start of
code field and 0x0D in the end of code field (‘0x0D’ is the hexadecimal representation of
carriage return).
To create a new Feedback code, click on the ‘New’ button. You will now see the ‘Define
feedback code’ window:
At the top of the window you have these fields:
293
TELETASK Handbook
AV-SOFT
 Code Name: In this field you can enter a descriptive name for the receive code
 Sample Code: In this field you need to enter an ASCII code that can be received from
the AV-device. This code is automatically repeated as individual characters in the field
below the sample code.
 REMARK: for HEX devices the sample code field is not available. You need to
enter the individual bytes directly in the GRID
When the sample code is entered, we can define how the different variables can be obtained
from this code. Let’s have a closer look at the code in this example:
 *z1,ON,FM,24
 Remark: note that the sample code starts with a ‘*’. This is the start of code character
that was entered in the previous window.
 Remark: note that there is no ‘end of code character’ displayed in this sample code. It is
not necessary to add the ‘end of code character’ in this window.
This code contains 4 variables: the zone number (1), the power status (ON), the active source
(FM) and the volume (24). Depending on the brand and type of your AV-device the receive
codes can contain either multiple variables in one code (like in this example) or contain only
two variables per code but have more different codes. E.g. the codes from another brand could
be like this:
 @ZONE1:PWR=ON
 @ZONE1:SRC=FM
 @ZONE1:VOL=24
 IMPORTANT remark: Note that the three codes above all contain the zone number. If
your AV-device (that has multiple zones) use codes that do not contain zone numbers
the device is not compatible with the TDS14042.
 Receive code Protocols
To obtain a variable from a code, there are different ‘protocols’ available like Single possibility,
Position related, Determined by delimiter info, Display characters from position and Exact.
Depending on the type of variable (zone, source, power,..) and the type of code (HEX or
ASCII) the different AV interfaces support the protocols as indicated in the tables below:
294
TELETASK Handbook
AV-SOFT
RS232 interface TDS14042:
1) Position related
Zone
Source
Power
Volume
Hex, Ascii
Hex, Ascii
Hex, Ascii
Hex
2) Determined by
Delimiter info
Ascii
3) Display characters
from position
Line 1 or 2
Ascii
Hex, Ascii
4) Single possibility
Hex, Ascii
Hex, Ascii
5) Exact
Hex, Ascii
AV-IP License TDS15240:
Zone
Source
Power
Volume
1) Position related
Hex
Hex
Hex
Hex
2) Determined by
Delimiter info
Ascii
Ascii
Ascii
Ascii
3) Display characters
from position
4) Single possibility
Line 1 or 2
Ascii
Hex, Ascii
Hex, Ascii
Hex, Ascii
5) Exact
Hex, Ascii
Ascii
Hex, Ascii
 Remark: As you will see, in some cases there are different ways in which you can
obtain a variable from a code (using different protocols).
We will now have a look at the individual protocols.
1) Position related:
This mostly used protocol indicates that a specific variable can be found at a predefined
position in the code.
Example: If you have a device that uses the code:
*z1,ON,FM,24
You could get the zone number from this code as ‘Position related’ because the zone number
can be found at position 3.
 Remark: this protocol is limited to a single byte or character. But in some case you can
use it to get longer variables from the code. E.g. in the code above you can also get the
power status as ‘Position related’ because at position 6 there is an ‘N’ for ON and an ‘F’
for OFF
295
TELETASK Handbook
AV-SOFT
 Remark: this protocol cannot be used if a previous part of the code has a variable
length. E.g in the code above you cannot use this protocol for the active source
because ON and OFF have a different length
2) Determined by delimiter info:
This protocol is slightly more complex than the others but far more powerful if the different
code parts have different lengths. This protocol can only be used if different variables in the
code are delimited (separated) by the same character.
Example: If you have a device that uses the code:
 *z1,ON,FM,24
The delimiter is the ‘,’. The volume can now be obtained as the variable after the third
delimiter. You also need to define the ‘Stop character’ for this delimited info. In most cases the
‘stop character’ will be the same as the delimiter or will be the ‘End of code character’ but it
can also be any other character.
Beside the ‘delimiter’, the ‘Number of delimiter’ and the ‘stop character’ which are required, this
protocol has two extra, but optional, parameters:
 ‘Number of positions skipped after delimiter’: if the variable would not
immediately start after the delimiter.
 Maximum length: the maximum number of characters that can be part of the
variable.
Example: if the code would be:
 *z1,ON,FM,VOL24BASS3TREBLE2
The volume would be the variable that starts 3 positions after the third delimiter and is
terminated by a ‘B’ character.
3) Display characters from position:
This protocol is only available for track or RDS information from a source. It is very similar to
the ‘position related’ protocol but in this case you define a start position rather than an absolute
position. All characters beginning with the start character en terminated by the ‘end of code
character’ will be displayed as track information
Example: If you have a device that uses the code:
 *RDS1,FM,info
The ‘Line 1’ info for FM can be obtained from the code as all the characters starting at position
10.
 Remark: this protocol can only be used if the first part of the code has a fixed length. If
there would for example be a second tuner in the device that is referenced as FM2 in
the code this protocol cannot be used (in such a case you could use the ‘determined by
delimiter info’ protocol).
4) Single possibility:
296
TELETASK Handbook
AV-SOFT
This is a very basic protocol. It indicates that a specific variable has a specific value.
Example: If you have a device that uses the codes:
 *z1,ON,FM,24
 *z1,OFF,FM,24
You could define two receive codes for this and get the ‘Power status’ from this code as single
possibility.
 Remark: this protocol can sometimes be useful for the minimum or maximum volume
as some AV-devices send different codes (e.g. Mute, Max) for these values than for
other volume levels.
5) Display exact characters:
This protocol does not obtain any data from the code, instead it displays a predefined text on
‘Line 1’ or ‘Line 2’.
Example: If your AV-device sends the code:
 *RDS1,FM,RDS ERROR
To indicate that there is no RDS info available for the current radio station, you can display a
blank line or ‘No info available’ or ‘FM’ or ….
 Defining a receive code
Assume we have a device that uses the receive code from the examples below:
 *z1,ON,FM,24
This code contains info about the power, the source and the volume status of a particular zone
of this amplifier so in the ‘Define feedback code’ window we give this code the name ‘Power,
Source and Volume’.
297
TELETASK Handbook
AV-SOFT
We will now need to obtain all the variables from this code. When you create a new code for
every variable the ‘Protocol’ will be ‘Not defined’. This means that there is no information on
how to obtain that variable from the code.
In our example code there is no information about LINE1 or LINE2 so the protocol for this
variables will remain ‘Not defined’
Zone:
The zone variable can be obtained from the code as position related on position 3 for
this example.
To do this:




Select the ‘ZONE’ tab page
Select ‘Position related’ from the ‘Select Protocol’ dropdown list
Enter ‘3’ in the ‘Zone position in code’ field.
PROSOFT will try to obtain the correct character from the code and mark the
character in the grid. This allows you to easily verify the information entered in the
different fields.
At the bottom the is a ‘translation table’ in which you can define which variable
corresponds with each ‘TELETASK’ audio zone. These audio zones first have to be
configured in PROSOFT.
In this case we have a device with 4 zones that are referenced in the code as 1-4.
Other devices may us A, B, C and D or Main for the first zone and 2, 3 and 4 for the
others.
298
TELETASK Handbook
AV-SOFT
 Remark: This table can only contain 1 character for each zone. In the case that
the zones are referenced as Main, 2,3, and 4 you can use the characters ‘M’, ‘2’,
‘3’ and ‘4’ in this table.
Source:
The TDS14042 only supports obtaining the source as position related, but in this case
we have a problem, the position changes when the power changes from ON to OFF.
We will solve this by only obtaining the Source information when the amplifier is ON.
So we define the source as position related at position 8
To do this:



Select the ‘SOURCE’ tab page
Select ‘Position related’ from the ‘Select Protocol’ dropdown list
Enter ‘8’ in the ‘Zone postion in code’ field.
At the bottom we now have a translation table for the sources. Up to 8 sources can be
defined. In this example we have a device that has the sources FM, MP3, CD, DVD
and AUX.
 Remark: in some case it is impossible to get all the sources from the same
code. Suppose we have a device with an internal tuner that is referenced in the
code as FM and 4 inputs that are referenced in the code as IN1, IN2, IN3 and IN4.
In this case you need a code for FM and an additional code for the other inputs.
299
TELETASK Handbook
AV-SOFT
Power:
With this example code we cannot use the ‘position related’ protocol for the power as
this would generate a problem for the ‘Source info’. So for this code we will define the
power as single possibility ‘ON’
We will also create a second receive code ‘Power OFF’ from which:
 We obtain the zone number as ‘Position related’ on position 3,
 We define the ‘POWER’ variable as ‘Single Possibility’, OFF
 We don’t obtain other information
300
TELETASK Handbook
AV-SOFT
Volume:
The ‘volume’ variable can be obtained from the code using the ‘Determined by
delimiter info’ protocol.
To do this:




Select the ‘VOLUME’ tab page
Select the ‘Determined by delimiter info’ from the protocol dropdown list
Enter ‘,’ as the ‘Delimiter’
Enter ‘3’ as the ‘Number of delimiter’
At the bottom you can also define a ‘Min’ and ‘Max’ volume. In this case we have a
device that uses 0 as the ‘Min’ volume an ‘50’ as the ‘Max’ volume.
 Remark: You have to define the ‘Min’ and ‘Max’ volume (see technical data form
you AV device) to recalculate the volume from 0 to 100 for a correct display on
the TELETASK displays.
 Remark: Some devices display the volume in dB, e.g from -60dB to 0dB where 60dB is the minimum. In such a case enter ’60’ (without the ‘-‘) as the Minimum
and 0 as the Maximum.
301
TELETASK Handbook
AV-SOFT
‘Identifiers’ and ‘Variables or don’t care characters’
All our variables are now defined for this code, but we need a mechanism to recognize
this code. This is done by ‘Identifiers’ and ‘Variables or don’t care characters’.
An Identifier is a character that is always available in this code on a predefined
position. In our code (*z1,ON,FM,24) the Identifiers are:
 *, z, the first comma, O, N, and the second comma
A ‘Variable or don’t care character’ is a character that is either one of the ‘variables’ or
a character that can be different in different codes but that hasn’t got any meaning by
itself (‘a don’t care character’). In this code the variables are:
 1, F, 2 and 4 (the zone, source an volume variables)
The ‘don’t care characters are:
 M and the third comma.
The M is a ‘don’t care character’ because this can be different for the other sources.
The third comma is a ‘don’t care characters’ because its position in the code can vary
e.g. if the source value is AUX, the position of the third comma is 11 (instead of 10).
So if a receive codes that starts with *z and where the characters 4-7 are: ‘,ON,’ this
code will be recognized as the ‘Power, Source and Volume’ code name.
When entering a sample code, all characters are automatically marked as ‘Identifier’
(grey background)
The final thing we have to do is mark the ‘variable or don’t care characters’. To do this
select a character (or multiple surrounding characters) from the grid and click the
white ‘Variable or don’t care character’ square. You will see that the characters will
now get a white background.
Alternatively you can ‘right-click’ a character and mark it as ‘Variable or don’t care
character’ from the popup menu.
Our code should now look like this:
 Remark: when closing this window PROSOFT will check that all ‘Variables’ are
marked as ‘Variable or don’t care character’. If PROSOFT detects a ‘Variable’
302
TELETASK Handbook
AV-SOFT
that is not marked as such, it will mark that ‘Variable’ as ‘Variable or don’t care’.
PROSOFT will display a message that is has done this and give you the options
to accept or review the changes.
 Remark PROSOFT cannot detect ‘don’t care characters’ (like the M and the third
comma). You have to do it yourself.
 Remark: if you have accidently marked an ‘Identifier’ as a ‘Variable or Don’t
Care character’ you can mark it as Identifier again using the grey Identifier
square (or the right click menu).
 Remark: If you make any changes to the sample code all characters are marked
as Identifier again.
303
TELETASK Handbook
AV-SOFT
30.5. Polling codes
Polling codes are codes that are sent from the TELETASK system to the AV device to request the
status of a zone or source.

REMARK: Polling codes are optional, some AV system automatically inform connected system
when a status changes, other systems do not. See the documentation of your AV-device.

REMARK: Even if the Polling code requests that status of a specific zone, the feedback code
from the AV-device must include the zone identifier.

REMARK: It is possible to use one polling code to request the status of multiple zones, as long
as the feedback codes for the different zones are sent as individual messages.

REMARK: up to five polling codes can be used with TDS14042
To define a polling code, go to the ‘Feedback Codes’ window and select the tab page ‘Polling codes’
Click the new button to add a polling code, for each zone you can now enter a code (like for send
codes)
Example: if we can request the status of a zone with the code: *GET,z1; (where 1 is the zone number)
304
TELETASK Handbook
AV-SOFT
Our polling code will be:
30.6. Special codes
30.6.1. EXTRA CODES for iSGUI V2.5
On the iSGUI audio page you can add 10 additional functions to control your AV
source. To make them active you have to add these extra functions to the Recorded
codes list of your AV device.
Primary audio page
Detail page
Extra 1
Extra 2
Extra 3
Extra 4
Extra 5
Detail page
Extra 1
Extra 2
Extra 3
Extra 4
OK (Enter)
305
TELETASK Handbook
AV-SOFT
Extra 6
Extra 7
Extra 8
Extra 9
Up
Down
Left
Right
Extra 10
Not visible
 Important Remark: All of the extra codes can be recorded to hold any possible
functions BUT independent of the recorded IR codes, the extra codes 5 up to 10
will be displayed on iSGUI as arrows and OK, if they have a display name!
30.6.2. 'Link zone with' action
The 'Link zone with' action allows to Link the selected zone with another zone. When zones
are 'linked' they will always play the same audio stream. When the 'source' in one zone is
changed, the source in the other zone will also change.
As both zones need to have the same sources available, not all zones can be linked together.
The zones that can be linked (to zones of the same type) are:
 Zones on the same multi zone amplifier (e.g. MMA 8)
 Zones from the Nuvo P100/200/3000/3100/3500 players.
When zones are linked, they will remain linked until one of the zones is switched OFF.
It is possible to link more than two zones together. The only limitation is in the hardware of the
audio system:
 MMA4: 4 zones can be linked as one MMA4 has 4 zones available
 MMA8: 8 zones can be linked as one MMA8 has 8 zones available
 Nuvo: 16 zones can be linked.
For the Nuvo system, linking zones from TELETASK is the same as linking zones in the Nuvo
App.
306
TELETASK Handbook
AV-SOFT
30.7. BACK-UP the AV-SOFT Library
It is advised to back-up your library in case you want to install your PROSOFT to another PC.
The complete library is stored in de 'appdata' folder of your PC.
 For WINDOWS Vista/7: 'C:\ProgramData\TELETASK\PROSOFT\custom3.3.irdb'
 For WINDOWS XP: 'C:\Documents and Settings\All Users\Application
Data\TELETASK\PROSOFT\custom3.3.irdb'
After installing PROSOFT on a other PC, copy the 'custom3.3.irdb' file to the same folder on
the new PC. Alternatively, if the 'custom3.3.irdb' hasn't been back-upped, the RS232/IR/IP
codes can be extracted from a .NBT file in which they have been used!

Open an .NBT file containing the device. The device will automatically be
added to your current 'custom.irdb' file.
To send the RS232/IR/IP Codes to someone else, create an empty .NBT file, add an Universal
RS232/IR Learnable interface or an AV-IP license, add the devices you want to send to the AV
interface and save the .NBT file.
307
TELETASK Handbook
AV-SOFT
31. Connection to the RS232 UNIVERSAL AV
INTERFACE
There are several connections that need to be made between the learnable RS232 UNIVERSAL AV
INTERFACE, the TELETASK domotic system and the audio system.
In the schematic drawing below all connection are shown.
Because the learnable RS232 UNIVERSAL AV INTERFACE is a set top box, TELETASK has chosen
for a more aesthetical connection to the AUTOBUS. This connection runs over a short CAT5 patch
cable to a RJ45 plug in the wall. Behind the wall plug the AUTOBUS is available. In the table below
you can see how the pinning of the CAT5 cable corresponds with the AUTOBUS wires.
308
TELETASK Handbook
AV-SOFT
31.1. RS232 connection
In most cases, the connections between the third-party audio device en the Universal A/V interface is
done, using a null-modem type RS232 cable.
In some case though, the third party audio device requires a straight type RS232 cable to connect to
the Universal A/V interface! Both types of RS232 cable are included with the Universal RS232
interface.
To know which cable you need you can follow the next rule of thumb:
IF you need a straight cable to connect your device to the PC - a null-modem cable is required
between the audio device and the A/V interface.
IF you need a null-modem cable to connect your device to the PC - a straight cable is required
between the audio device and the A/V interface.
31.2. Splitter Cable for audio system
When you set up an audio integration with the TDS14042 RS232 UNIVERSAL AV INTERFACE you
will notice that the cabling between the different audio components and audio amplifiers is not that
simple. In the drawings you have made during the setup, you will notice that one audio source is
connected to several amplifiers etc. To make these connections you need special splitter cables.
These splitter cables are optional available with the ref. TDS90160. Below you can find a picture of
such a cable in a practical situation.
For more information about the splitter cable, please check out the TELETASK datasheets.
309
TELETASK Handbook
AV-SOFT
32. Audio-IP software licence
The audio-IP software licence has to be activated before you can use it.
When you buy a license, you will receive a 'license code'. With this license code and the serial number
of your central unit, you can activate the audio-IP licence.
How to activate a license:



Go to www.teletask.be
Choose 'Login/Out' (header menu).
Log into your account or in case you don't have an account, create one
 Remark: an end-user account is made with a few clicks, to get an
professional account it will take somewhat more time.





You are automatically redirected to the 'download' section. Choose 'activation
files' (left hand menu).
Fill out the form correctly and click 'Activate license'
Your activation file will pop up. Download it and save it in your Project folder.
Import the activation file into your PROSOFT project: choose 'extra' - 'licenses'.
Save the .NBT file and transmit to the central unit
310
TELETASK Handbook
Multiple DoIP Central units
DALISOFT
33. Configuring DALI ballasts with the
TDS20620V2 DALI Tool
 Connect the TDS20620V2
 If there is a TDS13620 connected to the DALI-bus, remove it first.

Connect the TDS20620V2 DALI configuration tool with the mains, DALI-bus and
you PC
 Start DALISOFT
311
TELETASK Handbook


Multiple DoIP Central units
Start PROSOFT and just select ‘New MICROS+’. Addressing DALI ballasts will
not make any changes on the .nbt project file. So this can be done independently
from the TELETASK project configuration.
Select “DALISOFT” at the left
 Search DALI devices
At the top right corner of the DALISOFT window, you have two possibilities to start the
DALI addressing configuration:
 “Search DALI devices”: select this to find all devices on the DALI bus without
changing their address. When the search is finished, the number of devices in the
list should match the number of the physical devices on the DALI bus.
 If the number doesn’t match, it’s possible that some ballasts have the same
address. In that case, you have to choose “Initialize DALI devices”.
 “Initialize DALI devices”: select this option to give all DALI ballasts a new
address.
 Be careful! This option will clear the addresses from all the devices on the
DALI bus. After the initialization is finished, you will get a list of all the
devices addressed with a random generated number, starting from zero.
 Check DALI Addressing
When the list is generated, you can scroll through the list with the mouse or with the
arrows of your keyboard. Each time a device is highlighted the corresponding (DALI)
312
TELETASK Handbook
Multiple DoIP Central units
light is switched to ON and the previous is switched to OFF. So it’s easy to see which
address is allocated to which device.
 Change DALI Address
If it’s necessary to readdress one or more devices, simply click in the list on the device
you want to change. Fill in the new address for that device and press “Change”.
If another address was already on this new address, the other device will get the old
address.
 Remark: readdressing is only possible if there is still one address available on
the DALI bus. This means if your bus is 100% occupied with 64 devices, you
have to remove one device from the DALI bus and configure this one separately.
 Finish
Addressing DALI ballasts will not make any changes on the .nbt project file. You can
simply close PROSOFT after the configuration.
313
TELETASK Handbook
Multiple DoIP Central units
Multiple DoIP Central Units
34. Coupling of multiple Central Units.
With one TELETASK DoIP Central Unit you can control a large number of in- and outputs. For very
large installations or installations where there exists a logical and/or physical division between the
different parts of the building/complex it can be necessary/desirable to work with several Central Units.
Examples:





Very large villa's ( several central units for the needed in- and outputs)
Professions (one central unit for the house and one for the practice).
Hotels
Company buildings
…
Up to ten DoIP central units can easily be connected to each other. It is recommended to situate the
central units on a separate part of the network, so the communication between the central units will not
be interrupted through internet traffic, copying of files from/to a network hard disk, printing to a network
printer,
The number of in- and outputs and the number of functions which can be controlled with a system with
several central units is simple the number of one central unit multiplied with the number of central
units.
For example: for one central unit max. 500 local moods, 2 central units: 1.000 local moods, 3 central
units: 1.500 local moods, 5 central units: 2.500 local moods, 10 central units: 5.000 local moods.
The split up of the intelligence of the several central units increases also the reliability of the system. If
one central unit drops out, the other central units can continue functioning, only the hardware (in- and
outputs) which are coupled with the defect central unit cannot be controlled any more.

Remark: In case you want to add a cool or heat relais (or dimmer) to a TELETASK sensor (with
TDS12309, TDS12310, AURUS, TDS10012, …), you have to make sure that this relais (or
dimmer) is on the same central unit as the one of which the sensor is connected to.
314
TELETASK Handbook
Multiple DoIP Central units
35. PROSOFT SUITE
For an installation with several central units, only one .NBT file has to be created which contains all
information of all central units.
35.1. PROSOFT
To create a file for several central units you start with a normal file for one central unit.



Adding a central unit: via 'Extra', 'Central units', 'Add'.
The added central unit gets automatically a letter (A-J) you can also choose a
name and type (MICROS+, NANOS or PICOS) for this central unit.
Additional central units can be added as described here above (with a maximum
of 10 central units).

Remark: Once the type (MICROS+, NANOS or PICOS) is chosen, it can't be changed afterwards.

Remark: you can use different types of central units in one installation with several central
units. (e.g. two MICROS+ central units, three NANOS central units and one PICOS).
35.1.1. Central Unit bounded
In- and outputs are bounded through hardware to a specific central unit. Either they are direct
in- and outputs of a MICROS+/PICOS central unit or they are located on a bus of a certain
central unit. Yet, all outputs can be controlled from any central unit.
The address of an interface will be preceded by the letter (A-J) of the central unit on which the
interface is connected:
 A1 I24 (Central unit A, bus 1, input interface at address 24)
 C3 O05 (Central unit C, bus 3, output interface on address 5)
In- and outputs are also preceded by the letter of the corresponding central unit:
 REL A23 (relays 23 at central unit A)
 REL B23 (relays 23 at central unit B)
 DIM C1(dimmer 1 at central C)
Contrary to the interfaces and in- and outputs, the functions are mostly not centrally bounded.
A local mood can perfectly control the outputs of different central units and also a local mood
can be controlled from any central unit.
Exceptions on this rule are the Motor function and the RGB function, these functions are
closely bounded with the hardware (2 relays or 3 dimmers) and are linked to a specific central
unit (the central unit on which the relays or dimmers are defined). Nevertheless these functions
can be controlled by every central unit.
 In PROSOFT one central unit will always be actif. The active central unit can be
changed in the menu bar of the main screen of PROSOFT.
35.1.2. Interfaces
If you go to the in- or outputs, you will only see the interfaces which are defined on the active
central unit. If you want to couple a relays to an input/function, you will only see the relays of
the active central unit (= same central unit as the central unit of the input). If wanted, you can
extend this list to a list of all relays by selecting the bottom item double arrow.
315
TELETASK Handbook
Multiple DoIP Central units
35.1.3. General moods
Using Moods in a multiple Central Unit project, a new function is added: the global mood. A
global mood can control all outputs of all central units. A general mood can only control
outputs of one central unit; While a general mood is bounded to one central unit, a global
mood is not. Similar to all functions general and global moods can be controlled from every
central unit. The number of global moods is restricted to 10.
 Remark: A general mood who has been defined as ‘global mood’, will be count on every
central. For example, if there are 45 General moods on central A, 20 for central B and 5
global moods, that you can still make 25 general moods for central B, but no more for
central A and also no more global moods.
35.1.4. Step Functions
The “active step” of a step function is saved seperatly on each central unit. So if the step
function is set to “step 1” on central unit A, activating the step function on central unit B will not
set the step function to “step 2” but to “step 1”. Activating the step function again on central
unit B will set the step function to “step 2” but it will reset the step function on central unit one.
Activating the step function on central unit one, will cause it to go to step 1 again.
35.1.5. Touch Panels
 All simple touch panels: TDS12116, cookie's, AURUS, AURUS-OLED, proximity
readers… can control every output of every central unit.
35.2. TIMESOFT
Every central unit has his own clock tables. From a clock table on a central unit you can control
outputs on another central unit. For editing clock tables of a specific central unit, this central unit must
be, similar as in PROSOFT, activated.

The active clock table (Automatic / Workday / Weekend / Simulation / None / Custom) is always
true for all central units!
35.3. CARDSOFT
Similar to the working of one central unit.
35.4. GUISOFT
A GUI/GUI+/iSGUI always connects to one central unit, but it is possible to control all functions of all
central units. This means for example that you only need 1 GUI+ license to control the entire
installation from a single Touchscreen.
35.5. AV-SOFT
Similar to the working of one central unit.
35.6. Communication
PROSOFT Suite sends the needed information to the different central units. For every central unit
there is a connection needed and therefore an Ethernet connection is needed when you want to work
with several central units.
316
TELETASK Handbook
Application examples
Energy management
36. Overview of energy visualisation
X
X
X
X
* c/g today or last
24h (totalized units)
Meter with pulse
output (TDS12116)
kWh, Ltr, m³ or in
currency
(€, $,£…)
X
X
X
X
X
X
Column chart
Total /h, /day /month
Meter with pulse
output (TDS12116)
kWh or Ltr or m³…
X **
X ***
Line chart
Any analogue
sensor
on a TDS analogue
input
°C, Lux, %, Ph,
km/h, m/s, bar, ...
X ****
X ***
Smart meter
parameters
Smart meter with
built-in webserver
kW, kWh, V, A,
cosPhi, m³, m³/h,
Pactive/
Preactive
Electricity balance
Electricity meters
with pulse output (on
contact inputs of
TDS12116)
(max. 1 meter per
.nbt file)
Real time
consumed +
generated +
balanced in
values and
currency
X
CONTROL TOWER
X
TDS15110
X
GUI+
kW or ltr/h or m³/h…
TDS15105
Meter with pulse
output (TDS12116)
iSGUI
TDS12022, 32
AURUS-OLED (PLUS)
* Real time c/g
(=flow)
TDS15101
Displayed unit
AURUS-TFT
Source of the
parameter
TDS12064
Item
TDS12015,16, 17, 12061,
12110, 14050
What can be displayed on the TELETASK user interfaces:
X
X
‘ ’
 X : feature is supported on this interface
 ‘c/g’: consumption or generation
 *: The flow or the total of one pulse input can be visualized. Connect the pulse meter at
two inputs of the TDS12116 if you want to display the flow as well as the total at the
same time.
 **: Totals/hour are memorized for up to 2 days (up to 2x 24 columns) ; totals/day are
memorized up to 2 months (up to 2 x 31 columns); totals/month are memorized up to 2
years (up to 2 x 12 columns).
 ***: All values are memorized over the last two years on the GUI+ PC (only).
 Remark: for this feature it is required that the “Enable LOG system” option in
PROSOFT is enabled.
317
TELETASK Handbook
Application examples
 ****:
 1. chart/day: one value is memorized in the central unit every 15 minutes for the
last 2 days
 2. chart/week: values per hour instead of /15’ for the last 2 weeks.
 3. chart/month: contains two line charts: min. and max. value reached per day for
the last two months.
 4. chart/year: contains two line charts: min. and max. value reached per month for
the last two years.
 Remark: With the start of every new day/week/month/year, the values of the
oldest day/week/month/year are deleted from the memory.
 Remark: The chart data for maximum 100 devices can be memorized per DoIP
central unit.
318
TELETASK Handbook
Application examples
Application Examples
37. Real examples
37.1. Introduction
In this chapter you can find a clarification concerning the use of different TELETASK components and
the corresponding software settings/program of a specific theme.
37.2. How to integrate a heating/cooling system
Thanks to the TELETASK solutions, the control of a heating/cooling system is much more intelligent
than with a conventional system. A TELETASK installation offers powerful integration for heating,
cooling and ventilation. Thanks to this integration it becomes simple to automatically switch off the
heating/cooling in a room when somebody opens a window or the access control system detects that
people are coming home and the heating/cooling system is set to the comfort level…
TELETASK possibilities are only limited by your own fantasy.
Because there are so many different cooling and heating systems on the market, it is not always easy to
integrate these systems with a general home automation system. TELETASK developed several
products and solutions which allow to integrate close to every system available on the market. Thanks to
a wide product range, the user can control the integrated system automatically, from standard push
buttons, special touch panels, special touch windows, prestigious touchscreens, by remote control, by
mobile telephone, via local computer on wired or wire-less Ethernet or even remote through the internet.
The user interfaces are not described in this chapter, but below, the different steps to set up this
integration are described more in detail.
Details of the different components are also to be found in the data sheet of the concerning components
or elsewhere in this handbook in the 'Sensor Functions' in the 'Functions' chapter.

Important: the explanation below is done for one temperature zone. Your project may have
several heating and/or cooling zones.
Example: If you have different temperature settings in room x and in room y, you will have two
temperature zones.
The basics of temperature control explained below are to be considered per zone. You can have
as many temperature zones as the maximum available on the central unit in your project.
319
TELETASK Handbook
Application examples
37.2.1. De basic operation of a heating/cooling control
When you have a heating and/or cooling system integrated in your TELETASK domotics system,
the basic operation is always the same:
1
The TELETASK system measures, with its temperature sensor, the
actual temperature in a room.
2
In the TELETASK system the measured actual temperature is
compared with the temperature which was set (is the target) by the
user.
3
If the actual temperature is lower than the target temperature, than
the internal TELETASK heating control system will control the
heating system to increase the temperature in the room. (Closing
the Relay of the Heating system is the simplest way of control, but
TELETASK has more intelligent control algorithms available).
4
Time after time, the actual temperature is measured. The
TELETASK system decides as soon as the target temperature is
reached, to open its output contact again, so the heating system is
deactivated.
In case of cooling, the control works the same way, but then about decreasing the temperature
instead of increasing.
Anyhow, the basic operation is always like above. It only differs in controlling the output. The
output control algorithm may be more complex (pulse with modulated output control with
predictive algorithm, analogue control, multi-speed fan control…), but the basic operation is
always about comparing the actual temperature with the set temperature.
37.2.2. The available internal temperature control algorithms
 Heating
There are five different control algorithms defined in the TELETASK domotics system.
Depending on the type of heating system, you will have to select one of the available
algorithms in the control menu.
 ‘Standard’: this is the most basic algorithm for temperature control. The heating output
relay is switched on/off when the actual temperature and the set temperature become
equal: the output relay contact is opened. When the actual temperature becomes lower
than the set temperature: the output contact is closed again. This output contact can be
used to control a valve, a fan or a circulation pump.
 'Air': this control algorithm is selected when you want to integrate a fan controlled
heating system in a more intelligent way. In this case the TELETASK system uses a
pulse width modulation method to control the connected fan. A cycle time of 10 minutes
is used. Depending of the difference between the actual and the set temperature, the
fan will be activated longer or shorter. This time is also depending on the Temperature.
10Volt = 100% time setting.
Example: The parameter is set to 5°C/10V and the difference between actual and set T
is 3°C. Than the heating time will be 6 minutes (3/5 of 10 minutes). After 10 minutes, the
difference in temperatures is measured again and a new cycle time is calculated and
will be used in the next cycle.
320
TELETASK Handbook
Application examples
 'Radiators 15min': this algorithm is to be selected when you use a heating system with
wall mounted (water) radiators of the 'high yield' type. The algorithm works like the 'Air'
algorithm, but with a cycle time of 15 minutes.
 'Radiators 20min': this algorithm is to be selected when you use a heating system with
traditional cast iron (water) radiators. The algorithm works like the 'Air' algorithm, but
with a cycle time of 20 minutes.
 'Floor heating': This is to be used when the output has to control a floor heating
system. The algorithm is the same as above, but with a cycle time of 30 minutes.
 Important: the slower the heating transfer process of your system, the longer the
cycle time needed.
 Cooling
For cooling, the three control algorithms which are available are 'Standard', 'Air 10min' and
'Air 15 minutes'. The working is equal to the heating algorithms above. The only difference is
that the output is activated when the measured temperature is too high instead of to low.
 In practice
These algorithms and their parameters can be configured in the following way:
 Click 'Options' in the PROSOFT menu bar
 Click the 'Sensor' tab.
 Define the different parameters
 Click 'OK' until you are back in the main PROSOFT window.
37.2.3. Setting up the output control of the heating/cooling system
It is not defined by the control algorithm which output components are used for the output and to
control the connected heating system, because there are a lot of different heating/cooling
systems. On top of this, every heating/cooling system is different. Therefore, the used
components of the TELETASK system have to be selected, linked with a temperature zone and
the connected parameters are to be set. How to set this relation is described in the 'Analogue
input interfaces' chapter in this handbook.
 A practical example
The family Jones made a wise decision and decided to install a TELETASK system in their
house. They also understood that the integration of the heating system was not an option, but
just one of the reasons why you should install a home automation system. They have four
temperature zones: the ground floor, first floor and two bath rooms with separate temperature
settings. Every room in the house is equipped with radiators. The distribution of the hot water is
done with four electromagnetic valves (open/close). There is one main water circulation pump.
 Needed TELETASK components




4 TELETASK temperature sensors (to be mounted on the best place and on the
correct height)
4 electrical zone valves (not from TELETASK) connected to four relay outputs of the
TELETASK system.
1 circulation pump from the heating system which is connected to an output relay of
the TELETASK system.
1 touch panel (or more) with a display for temperature control.
 Remark: the circulation pump will be ON as soon as at least one valve is OPEN.
As soon as all valves are closed, the circulation pump is to be stopped, to avoid
unnecessary energy consumption.
321
TELETASK Handbook
Application examples
 In practice

In PROSOFT go to the 'Extra' 'Options' 'Sensors' menu and select the 'Radiators
20 min' control algorithm.

In PROSOFT select the desired output unit and define each output relay for the
sensor zones which will have to control one of the four valves of the heating system
(for example relay output 1, 2, 3 and 4). So you will have to enter the names of the
four zones in the relay name fields (relay 1: 'ground floor valve', etc…

Define the relay which is to control the circulation pump (for example R 5) and add
the name 'main circulation pump'.

Go to the analogue input interface on which the T sensors will be connected and
define a first T sensor and give him the name 'Ground floor'.

In the Properties menu under the tab 'Heat' enter as control method 'standard
relay'.

Select in the On/off field the relay for valve control of the ground floor (R1 in this
case).

Enter the temperature settings for day, night and standby preset. These can always
be changed by the user.
 Remark: The frost protection is a general parameter which is the same for all
temperature zones. You can set this parameter in the 'Extra' 'Options'
'Sensors' menu. Standard this parameter is set to 5°C.

Repeat this for the other three temperature sensors.

Now make a condition function 'Heating ON' wherein the valves of the different T
zones (R1, R2, R3 and R4) are all noted with an 'OR' relation between them.

Make a process function which guards the condition function 'Heating ON' (=ON)
'continuous monitoring (ON and OFF)' and which controls the circulation pump
(R5).

Select this process function in the 'auto start' function: in PROSOFT main window,
select 'Extra' 'Options' 'Option' and you will find the 'automatic start function' field
there in the 'Service options'.

The whole heating system is now integrated and ready to be started.
322
TELETASK Handbook
Application examples
37.3. How to integrate a light sensor
37.3.1. Scope
This concerns both situations, being the use of a TDS12270 light sensor or a third party light
sensor.
In case of TDS12270, this one will be connected to a TDS12309, TDS12310, MICROS+ or
PICOS analogue input. In case of the third party sensor, it will be connected to a TDS12310
interface.
37.3.2. Application
A TDS12270 light sensor can be used for several reasons. Depending on the application, you
can use the 'day' and 'night' thresholds which can be set on the sensor board (jumper settings see datasheet). In other applications these thresholds cannot be used and the light sensor
signal is to be used in another way. In other words, the use of the light sensor and his hardware
and software settings are always related to the application.
37.3.3. How to add a light sensor to your project
Adding a light sensor is comparable to adding a temperature or humidity sensor. Also refer to
the chapter 'Analogue Input Interfaces'. In PROSOFT it is done as follows:
 Click 'Edit' 'Inputs' in de PROSOFT menu bar.
 Select an analogue input unit or interface or add a new input interface to the
system (AUTOBUS).
 Select the desired individual analogue input and select the desired light sensor
which will be connected to it. Three different types can be selected: 'dark', 'normal'
and 'sun' light sensor.
Specify the different available parameters depending on the type of the selected light sensor.
Below, there are two different applications described more in detail:
 CASE: Switching a light in twilight situations (often used case)
To be able to control a light point when it gets dark, there are no specific sensor settings. The
light sensor should be set (jumper settings on the sensor circuit board) to a 'dark' (twilight)
sensor.




Make a condition function which you can call 'dark', wherein the sensor value is set
to '< 10 Lux'.
Make a process function 'light ON when dark', in which the condition 'dark' (ON if
TRUE & OFF if FALSE (all edges)) is controlled and the desired light point is
switched ON when the condition is TRUE.
Optional: In TIMESOFT you can switch ON the process function for example every
day at 5pm and switch it off again at 11pm.
To switch OFF the light when the process function is switched OFF, set the
‘Deactivate handling’ to ‘When Process Function is de-activated: switch off output’.
 CASE: Control of motorised sun shields and sun screens
To close (or open) electrical sun shields when the light is higher than x lux, the light sensor must
be set to 'sun' type (jumper settings and sensor settings in PROSOFT). In this case, there are
extra sensor parameters to be set.




Go back to the sensor ('Inputs & Others' - 'Analogue input interface').
Put the Sensor type to: 'Light sensor (sun)'
Below, select 'Flags' from the dropdown box and add a flag. Call it 'No sun'.
Set the 'Preset 1 (day)' preset to 7078 Lux.
323
TELETASK Handbook






Application examples
Go to 'Extra' menu in PROSOFT  'Options'  'Option'-tab and add a 'Local Mood'
to the 'Auto Start Function'. In this 'Local Mood' add this light sensor and set it to
'Preset: Day' 'ON'.
Go to the motor definition to the ‘Sun function’ tab.
Add the Flag ‘No sun’ = ‘OFF’ to the ‘Condition to activate sun function’
Set the motor position and delays
Repeat the last two steps for other motors if necessary
Extra parameters which are influencing the sunshield control can be added trough extra
process functions combined with flags and clocks.
37.3.4. The argument 'Hysteresis'
When exceeding the 'day' threshold value, the light sensor will activate the function which is
related with it. When the sky is fleeced with clouds, the light values will differ from one moment
to another and the system may cross very frequently the preset Lux-threshold. In such case the
controlled lights or shields will constantly open/close. This is not what we expect from such
system. To solve this problem, the 'hysteresis' was introduced.
Hysteresis means some kind of Lux- window wherein nothing happens. Some kind of zone
wherein no threshold is crossed back as soon as it was crossed already. Both the 'day' and
'night' thresholds are provided with a hysteresis.
This means in our applications:
 The function or action which was selected in the data field is switched OFF when the
measured value is larger or equals the set value + the hysteresis value.
 The function or action which is selected in the data field is switched ON when the
measured value is smaller or equals the set value – the hysteresis value.
The result of using a hysteresis is that in case of balancing Lux values (in the Light sensor case)
around the threshold value doesn't result in a constant changing control of the connected output
(light, motor…). In practice this means that your light is not switching ON/OFF all the time and
the sun shields are not opening and closing all the time (refer to the figures above).
 The function which is switched by the light sensor is switched OFF when the following
errors occur (errors are also displayed on the display when selecting the concerned
sensor):
 'Data?' the sensor is in initialising mode or the central unit is waiting for sensor
information (lasts no longer than maximum a few minutes).
 'Sensor?' there is no sensor signal coming into the analogue interface of the
TELETASK system. This may be caused by a defect sensor or a cabling error.
 The hysteresis is only active on the set 'day' and 'night' thresholds. When a
sensor value is called for in another type of function (example: in a condition),
then the hysteresis is not used there.
 The hysteresis is to be set in general for all light sensors in the PROSOFT 'Extra
'> 'Options' > 'Sensor'. The hysteresis is to be set in steps (max. 10). In the
TELETASK LUX-table you can find all top and bottom values by using the number
of steps you have set.
324
TELETASK Handbook
Application examples
 Example: The hysteresis is set to 5 steps and the set 'day' threshold is 840 Lux. In the
TELETASK Lux table you can see that the bottom hysteresis value, which is in this
example 5 steps below, is 630 Lux and the top hysteresis level will be 5 steps up and is
1121 Lux.
37.3.5. The TELETASK Lux-values table
In this table you can find the working area of the different light sensor types (dark, normal and
sun). Beside of this, as a result of the hysteresis setting in PROSOFT, you can use the table to
find out about top- and bottom Lux values which are applicable in your case. For more details
about hysteresis, see the text on top if this.
D↓ - D↑
N↓ - N↑
S↓ - S↑
Work area of the 'dark' mode
Work area of the 'normal' mode; rarely used
Work area of the 'sun' mode
Step
Lux value
Step
Lux value
Step
Lux value
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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
0,06
0,12
0,19
0,26
0,33
0,41
0,50
0,58
0,68
0,78
0,88
1,00
1,10
1,20
1,40
1,50
1,70
1,80
2,00
2,20
2,30
2,50
2,80
3,00
3,20
3,50
3,70
4,00
4,30
4,60
5,00
5,30
5,70
6,10
6,50
6,90
7,40
7,90
8,40
9,00
9,60
10,20
10,90
11,60
12,30
13,10
14,00
14,80
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
17,80
19,00
20,10
21,00
23,00
24,00
26,00
27,00
29,00
29,00
31,00
32,00
34,00
37,00
39,00
41,00
46,00
49,00
52,00
55,00
59,00
62,00
66,00
70,00
74,00
78,00
83,00
88,00
93,00
99,00
105,00
111,00
118,00
125,00
132,00
140,00
149,00
157,00
167,00
177,00
187,00
199,00
210,00
223,00
236,00
250,00
265,00
281,00
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
334,00
354,00
375,00
397,00
421,00
446,00
472,00
500,00
530,00
561,00
595,00
630,00
667,00
707,00
749,00
793,00
840,00
890,00
943,00
999,00
1058,00
1121,00
1188,00
1258,00
1333,00
1412,00
1495,00
1584,00
1678,00
1777,00
1883,00
1994,00
2112,00
2238,00
2370,00
2511,00
2660,00
2817,00
2984,00
3161,00
3349,00
3547,00
3757,00
3980,00
4216,00
4466,00
4731,00
5011,00
D↓
N↓
S↓
Example
Hysteresis
-10
-9
-8
-7
-6
-5
-4
-3
-2
-1
Threshold
+1
+2
D ↑ +3
+4
+5
+6
+7
+8
+9
+10
Effective %
43,8 %
40,5 %
36,9 %
33,2 %
29,2 %
25,0 %
20,6 %
15,8 %
10,8 %
5,5 %
Threshold
5,9 %
12,3 %
18,9 %
25,9 %
33,4 %
41,4 %
49,7 %
58,7 %
68,0 %
78,0 %
Step
Lux values
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
5956,00
6309,00
6682,00
7078,00
7498,00
7942,00
8413,00
8912,00
9440,00
9999,00 N ↑
10592,00
11219,00
11884,00
12588,00
13334,00
14124,00
14961,00
15848,00
16787,00
17782,00
18835,0
19952,00
21134,00
22386,00
23713,00
25118,00
26606,00
28183,00
29853,00
31622,00
33496,00
35480,00
37583,00
39810,00
42169,00
44667,00
47314,00
50118,00
53087,00
56233,0
59565,00
63095,00
66833,00
70794,00
74988,00
79432,00
84139,00
89124,00
325
TELETASK Handbook
49
50
15,80
16,80
Application examples
99
100
298,00
315,00
149
150
5308,00
5622,00
199
200
94405,00
99999,00 S ↑
37.3.6. The meaning of a Lux value; practical approach.
When using a light sensor, the Lux values are very important. Everybody knows the 'Lux'
argument but for many among us, it is not clear what a certain value stands for. Therefore we
supply the table below for your information. Reference examples are included as a practical
approach.
Lux values area
Light source
Application field
20-50
General
Cinema room, a shaded museum…
50-100
General
Bed room, warehouse, not illuminated
exhibition hall …
100-200
General
Indoor at home on a clouded day
Spot
Work top in the kitchen, office desk, PC
table, …
Tasks: cutting vegetables, writing a
letter, computer work…
500-1000
Spot
Reading a book in a chair with a reading
light on, well lighted work top, PC table,
hobby area, lighting on a piece of art …
Tasks: reading a book, fine kitchen work,
sewing, measuring, PC work…
1000-2000
Spot
The hobby table, fine mechanical work.
Tasks: model- building, pot seedlings,
fine graphical work…
2000-5000
Spot + general
Blue sky on a spring day
5000-10000
Spot + general
Sun reflected on white walls
200-500
Based on this table you can decide the settings of your light sensors and the thresholds
depending on the application. For the control of a shun shield, the threshold value should be set
to 7000 Lux. The light sensor ten should be set to 'sun' (jumper setting).
In twilight situations, a threshold of 100 Lux should be good to control an in- or outdoor ambient
light. The sensor should be set to 'dark'.
326
TELETASK Handbook
Application examples
37.4. How to setup an access control system
To setup an access control system which is integrated with the home automation system, the different
TELETASK software packages are used in combination with each other. In this chapter, we will use a
case study where PROSOFT, TIMESOFT and CARDSOFT are used together.
37.4.1. Description of the case study example
In a family with four persons (mother, father, and two children), all of them can enter the house,
front door and back door, by using a TELETASK TAG. Every person has its own TAG unit,
hanging together with its car keys. When coming home, the front or back door is opened by
having the TAG in front of a proximity reader. At the same time the heating in the living room is
set to 'day' level.
The gardener and the cleaning women both have a TAG to, but they are only allowed to enter
the house at the backdoor and only on Thursdays between 7:00 am and 07:00 pm. In this case,
the heating is not switched to 'day' when they enter the house.
37.4.2. Needed products:





1 x TELETASK domotics central unit MICROS+/PICOS (for example: TDS10012)
1 x the necessary parts for the heating control: TELETASK temperature sensors,
output relays to control the door openers and the heating pump and valves.
2 x Proximity card reader (TDS12142)
2 x Electromagnetic door opener unit which are controlled from a TELETASK relay
contact from the central unit.
6 x Tag TDS12203.
37.4.3. In practice
 in PROSOFT:




Define the two magnetic door openers on relay 1 and relay 2
 Click 'Edit' in the PROSOFT menu bar.
 Click 'Outputs' and the 'List of Outputs' window appears
 Select 'MICROS+/PICOS OUTPUTS (1-8)'
 Select Relay 1 and define 'Room', 'Icon' and 'Name' (example: hall – motor –
front door). Do the same for the relay number 2.
 Click 'OK' until you are back in the main PROSOFT menu.
Add the two proximity card reader interfaces end set their AUTOBUS address
with the addresses 15 and 16.
 Click 'Edit' in the PROSOFT menu bar.
 Click 'Inputs'. The 'Inputs list' window appears.
 Click the button 'New'.
 Select 'General interface'
 Select 'TDS12142: Proximity Reader'
 Add the AUTOBUS address to the interface: '15' and enter a name for the
reader: 'Proximity reader Front door'
 Click 'OK' and repeat for the second proximity reader with address 16.
Make two 'Timer functions': 'front door opener' and 'back door opener'.
 Click 'Edit – Functions' in the PROSOFT menu bar.
 Select 'Timer functions'.
 Click 'New'.
 Add the 'Name': 'front door opener' in, Select relay 1 and add the opener
activation time in. For example: 3 seconds.
 Click 'OK' and Repeat for 'back door opener'.
Make a 'Flag' function and call it: 'Thursday 7am-5pm'.
 Click 'Edit – Functions' in the PROSOFT menu bar.
 Select 'Flag' functions.
 Click 'New'.
327
TELETASK Handbook




Application examples
 Enter the 'Name': 'Thursday 7am-5pm'
 Click 'OK' until back in the main PROSOFT menu
Make two 'Local Mood' functions: 'occupants access front door' and
'occupants access back door'
 Click 'Edit – Functions' in the PROSOFT menu bar.
 Select 'Local Mood' functions.
 Click 'New'.
 Enter the 'Name': 'occupants access' and eventually other parameters
 Add in the local mood the 'timed' function 'door opener front door' and the
'sensor' function 'day'
 Click 'OK' and Repeat for:
 'occupants access back door' with 'timed' function 'back door opener'
and sensor function 'Day'
Make a 'If-Then-Else' function: 'Employess limited access back door'
 Click 'Edit functions' in the PROSOFT menu bar.
 Select 'If-then-else' functions.
 Click 'New'.
 Enter the name 'Employess limited access back door'.
 Select for the 'IF Condition (True)': 'Flags', 'Thursday 7am-5pm'.
 Select 'THEN': the timer function 'back door opener'.
Connect the three functions to the two proximity reader units.
 Click 'Edit – Inputs' in the PROSOFT menu bar
 Double click the proximity reader with address 15 (front door)
 Select function button 1
 Select the 'Local Mood' function 'occupants access front door'.
 Click 'OK', Repeat for proximity reader with address16 (back door)
 Function button 1: 'occupants access back door'
 Function button 2: Select 'If-Then-Else' function 'back door opener'.
Save this file and send it to the central unit.
 In TIMESOFT
Go to TIMESOFT.
 Make a 'continuous' clock action 'Flag' 'Thursday 7am-5pm', which is
activated every week on Thursdays 7am.
 Click 'Add action'
 Select the 'Continuous' clock table
 Select the 'Flag' 'Thursday 7am-5pm'
 Select the 'Target value' 'ON'
 Select 'time of action' 7am
 Define the repetition of every Thursday
 Click 'OK'
 Make a 'continuous' clock action 'Flag' 'Thursday 7am-5pm', which is
deactivated every Thursday at 5pm.
 Click 'Action Add'
 Select the 'Continue' clock table
 Select the 'Flag' 'Thursday 7am-5pm'
 Select the 'Target Value' 'OFF'
 Enter time of action as 5pm.
 Set repetition to every Thursday
 Click 'OK'
 Save the TIMESOFT file.
328
TELETASK Handbook
Application examples
 In CARDSOFT



Add the parameters of the occupants Tags
 Click 'Add' and enter the 'ID' nr. of the TAG.
 Enter the name of one of the occupants
 Select the parameters:
 'Reader Add.': ALL
 'Function': 1
 Repeat this for 'Reader Add.': 16; 'Function: 1'
Enter the parameters of the TAG for the employees
 Click 'Add' and enter the 'ID' number of the employees Tags.
 Enter the name of the employee
 Select the parameters:
 'Reader Add.': ALL
 'Function': 2
Save the data on your PC and send it from PC to the connected central unit.
When these steps are done and all data is send to the central unit, the access control is
integrated and everything will work as described.
329
TELETASK Handbook
Application examples
37.5. Configuring a NUVO installation with three RS232
interfaces.
We also want to give you an example of an installation with three RS232 interfaces without the use of
IR-flashers. In this example we will use NUVO devices.
37.5.1. Phase 1: Define the desired audio/video configuration:
The schematic structure of the audio configuration.
In this example the configuration drawing leads to the next set of audio components:
 NUVO Concerto with built-in tuner. Has 8 zones
 NUVO 3M with built-in tuner which has 3 sources
 NUVO T2-FAM having 2 tuners.
 All the above NUVO devices will need a RS232 UNIVERSAL AV INTERFACE so you
can control them with your domotics installation.
37.5.2. Phase 2: Assigning the RS232 Port (s).
With only the audio configuration, the audio system is not yet integrated. Therefore a connection
must be made with the TELETASK home automation system by interfacing the audio
components with the TELETASK RS232 universal AV interfaces. For each NUVO device you
will need a RS232 interface.
330
TELETASK Handbook
Application examples
With the assigning of the RS232 Port and assigning names to the sources, the schematic
drawing is now finalized. In the next phase, this schematic is used to integrate the whole
installation into the TELETASK 'AV-SOFT' software.
37.5.3. Phase 3: Configuring the RS232 universal AV interface.
After the two first phases, now is the time to program the RS232 universal AV interface by
means of AV-SOFT. With the carefully prepared configuration drawing at hand, it should be easy
to walk through this third phase. Because the devices from our example (the NUVO devices) are
already in the TELETASK library we can continue directly with the configuration.
The configuring phase is divided in the following steps:
 Entering the audio configuration in AV-SOFT (from PROSOFT V3.2).
 Start PROSOFT and go to 'Inputs & Others.
 You are in the 'List of interfaces', choose ADD, Audio Interface.
 A new window: 'Define interface function' appears. Here you can give the device a
personalised name (which will appear similar in the 'List of interfaces').
 We do this 3 times and give our devices the following names:
RS232 NUVO 3M
RS232 NUVO T2FAM
RS232 NUVO CONCERTO
Then you give it the correct address, choose RS232 universal audio interface and then
click on 'Edit interface in AV-SOFT'.
 Dedicating Sources:
 Click on the button ADD DEVICE of the RS232 port
 There will be a pop-up screen, named: 'Select audio device'. In this case we first select
the NUVO NV-T2 FAM to connect with the RS232 universal AV interface. Click OK
 Now you can give the different sources a name: TUNER 1 and TUNER 2
 Then you repeat this above procedure for the NUVO NV-3M.
 Don't forget to save your work!
 Dedicating zones:
331
TELETASK Handbook
Application examples
Repeat the above procedure also for the NUVO CONCERTO NV-18GM.

In this window you will be able to dedicate the wanted sources in the specific
rooms/zones.
Finally you will have to follow the steps as written down in:
 Phase 4: configuring the audio buttons of the domotics installation.
332
TELETASK Handbook
Application examples
37.6. B&O Integration
37.6.1. Integration possibilities
There are two different types of integration between TELETASK and B&O:
1. Controlling B&O audio devices from TELETASK using the TDS15240 audio IP
license.
2. Controlling TELETASK from the B&O remote control using the TDS15132 open
DoIP protocol license.
The 2 types are independent from each other and are to be configured individually. The choice
to implement one or both of the options is up to the client. From the B&O side you will always
need the Masterlink gateway.
 Controlling B&O audio with TDS15240 audio IP license
TELETASK supports all standard TELETASK commands:
 Zone On/Off
 Zone Volume (Up, Down, Mute)
 Source selection
 Source control (next, previous, 1, 2, …)
 Audio Feedback is limited to volume feedback (if supported by the B&O interface).
 See http://mlgw.bang-olufsen.dk for the compatibility of the B&O audio devices
with their Masterlink gateway.
 Controlling TELETASK from the B&O remote control with TDS15132 open
DoIP protocol license
First the B&O Masterlink gateway (MLGW) needs to be configured. This is done from
the homepage of the MLGW. There’s a pre-configuration table that can be selected and
be used to link “Local Moods (1 - 99)” from TELETASK to “Events” from B&O. This can
be more than just the “Light” functions (e.g. switching a certain Audio Zone). Testing of
the link can also be done through the home page of the MLGW.
We will explain step by step how to integrate B&O and TELETASK for both possibilities.
333
TELETASK Handbook
Application examples
37.6.2. Controlling B&O audio devices from TELETASK
 Install B&O Masterlink Gateway
 Setup or find the IP-address of the gateway.
See manual “Installation and setting up guide for ML Gateway” of B&O.
The default IP address is 192.168.1.10.
 Configure B&O Masterlink gateway

Log in with a browser to the gateway and choose “Setup”

The default login/password is admin/admin
334
TELETASK Handbook
Application examples
 Assign all the B&O products
You have to configure all the Masterlink products.

Select Programming > BeoLink.
Please follow the B&O guidelines to assign the products with a MLN number.
At the end of the assignment procedure you must have something like this:
The MLN number is the number you will use afterwards in PROSOFT as zone number.
335
TELETASK Handbook
Application examples
 Setup the Masterlink Gateway Protocol

On the System tab, check if the MLGW protocol is configured on OP port 9000
9000 is the port number preconfigured in PROSOFT. If necessary it can be changed.
 Setup products
Depending of the product you may have the possibility of (limited) feedback information
to the Masterlink Gateway. Please check the Masterlink Gateway product compatibility
document for more information.
Example: for a BeoSound 4 you have to change in the setting menu “STATUS TO
MLGW (Master Link Gate Way)” to ON (default OFF).
 Settings in PROSOFT and AV-SOFT

In AV-SOFT make a new TDS15240: A/V IP License
 Remark: If you didn’t yet purchase a TDS15240 license for your central unit
you can use it for 3 days after downloading, there will be a test license
created automatically.
336
TELETASK Handbook
Application examples

Fill in the IP-address (in this example 192.168.0.107)

Add Device: BANG & OLUFSEN / ML Gateway 1701
This implementation can use a maximum of 8 B&O zones (MLN) and is preconfigured to use the
sources: RADIO, CD, A.MEM, N.RADIO, CDV/DVD, TV, AUX_V, AUX_A.
337
TELETASK Handbook


Application examples
You can now change the zone names and source names as you wish.
After this step you are able to use the audio zones in the rest of your TELETASK
system.
 Do not forget to assign the “Audio Zones” to “Rooms”.

Download to the Central Unit and test.
37.6.3. Controlling TELETASK from the B&O Remote Control




Go to the setup webpage of the gateway
Select ‘Programming’
In the “Devices” list select “Custom strings”
Press “Add device”



Fill in the Description field (e.g.: TELETASK)
In the IP-Address field, type the IP address of the Central Unit
In the IP-port enter 55957 which is the port number for the DoIP Protocol.
338
TELETASK Handbook



Application examples
Download the “DoIP B&O MLGW TELETASK Custom Strings” file from the
download section on www.teletask.be (first log in with your professional ID).
At the bottom “Browse” to the file “MLGW TELETASK Custom Strings.csv”
Press “Upload text file”
Now all commands for toggling local moods 1 to 99, are added as a resource to the gateway.
 Don’t forget to press the Test button and then the Save button.
Now you are able to use these commands through the B&O gateway.
Some examples:
Create buttons on the web page of the gateway:
 On the Programming > Devices page, add some buttons and give them a name
and an ID
 Place them on ‘Global’ room for testing.
339
TELETASK Handbook
Application examples



Go to the Macros page to add commands to the buttons.
Press “Add macro” to create an action
Give the macro a name.


Select “Virtual buttons” at “New event from driver”
Press “Add event”.
340
TELETASK Handbook
Application examples




Select the Virtual Button you have created and select as action “PRESS”
Press Finish
In the command section select “Custom strings: TELETASK”
And press “Add command”

Select the mood you want to test
 Don’t forget to press the Test button and then the Save button.
Afterwards you can go the webpanel http://192.168.0.107/webpanel/ and test your command:
341
TELETASK Handbook
Application examples
You can also add Macros for the remote control of B&O to trigger a mood.
Do this by repeating the previous steps but instead of selecting Virtual Buttons you select
“BeoLink” and select “Match LIGHT command”.
342
TELETASK Handbook
Application examples
37.7. Implementing NuVo with Audio IP License (TDS15240)
These steps describe how to integrate the NuVo Wireless Audio system (e.g.: P3500) with your
TELETASK installation by using the IP integration possibility with the Audio IP License TDS15240.
37.7.1. Necessary items:




TELETASK Central Unit (connected to a LAN)
NuVo System connected to the same LAN as the Central unit.
License for A/V control over IP (TDS15240)
A PC/Notebook running PROSOFT 3.4.14.0 or higher and physically connected
with the same network as the Central Unit and NuVo equipment.
 Using VPN or port-forwarding will not work!!!
 REMARK: The sources on the Nuvo devices must be configured correctly in
order to work with the TELETASK system. To use ‘Tune-In’ as a source you
must add Stations to the ‘My Favorites’ in the Nuvo App. To use ‘Deezer’ as a
source, you must add ‘Playlists’ to your Deezer account. To use ‘Library’ as a
source, you must have ‘Imported Playlists’. The Nuvo players will import
‘Windows Media player’ or ‘iTunes’ playlists from your library. If the
‘Imported playlists’ item in the ‘Library’ is empty, create a playlist, using
iTunes or Windows Media player, and copy that playlist to your network or
USB disk drive. That serves as a library source to the Nuvo system.
37.7.2. Integration:
Make sure that all components described above are up and running. Follow the ‘NuVo getting
started procedure’ from their app. After these steps, the different NuVo audio zones are defined
and have been given names. Please check that these are controllable from the NuVo app.







Start PROSOFT 3.4.14.0 or higher and open the .nbt file of the project.
Import the license activation file that you downloaded from the TELETASK website
with the license code and the serial number of the Central Unit to which the NuVo
will be connected.
Go to inputs and choose new.
Select TDS15240: A/V IP License
Choose “Edit interface in AV-Soft”
Click on the “Add Device” in the IP connection area.
Select the correct NuVo device that will be integrated.
PROSOFT will now search for the connected NuVo devices. You’ll receive a list of available
NuVo Devices (List of IP addresses).






Open the NuVo app and go to settings > general > about
You’ll find the same list of available devices.
Select one of the interfaces in the PROSOFT list. A NuVo device will be created in
the interface list and it will open in A/V-SOFT.
Give this interface the same name as in the NuVo app.
Do this two times: the Interface Name at the top of the window and the Zone Name
in the list of “OUTPUTS (AV-ZONES)”
If you defined favourites in “TuneIn” or Playlists in “Deezer” or in the NuVo Library,
you can fill in their names under the “Details” button of the matching sources.
343
TELETASK Handbook




Application examples
If a “LINE IN” is defined on the NuVo zone that you will not control with the
TELETASK installation, you can add this as an “uncontrolled source” (e.g. MP3
players,…).
If another “controllable” source is defined in AV-SOFT you can select this one as
well on the “LINE IN” input.
If desired you can disable the control of certain sources at this TELETASK Audio
Zone by enabling them.
Click OK and you can now use the standard audio functionalities within PROSOFT
to control the NuVo system.
 If you have more than one NuVo Zone (e.g.: P3500 has 3 Zones) you have to
repeat the same steps and create new interfaces from the input list for each
available NuVo Zone (e.g.: for the P3500 add 3 Audio IP interfaces).
 Don’t forget to link the “Audio Zones” to the “Rooms” in PROSOFT. Go to
rooms, select the desired room and select the corresponding Audio Zone.
This will enable the audio control on the TELETASK touchscreens and GUI’s.
 REMARK: If you want to control the Nuvo system from an AURUS-OLED
(PLUS), do not forget to ‘couple’ the ‘PREVIOUS’ and ‘NEXT’ buttons on the
‘Audio page’ of the AURUS-OLED (PLUS) (see the chapter on AURUS-OLED
(PLUS) for more information).
©, TELETASK, GENT, 2016
TELETASK can’t be responsible for potential errors in the data sheets and technical documentation.
Changes in the product features can be made at any time, without prior notice
344