CTD10

Controller for Qbus modules (expandable).

Execution:

Makes a stand-alone installation smart
Controls lighting, HVAC, energy, security, or a combination of all technologies
Includes free control via the renewed app or cloud
Compatible with all Qbus modules, regardless of generation
Suitable for small to large installations, expandable via extension cards
Easy configuration via free software

Technical info

Controller for 10, 40 or 2x75 Qbus modules, expandable with expansion cards (maximum 4 times 15 modules). With an ethernet port for programming and visualization of the Qbus Cloud, SD-card is securely located behind the cabinet's cover plate, accessible only to the installer. More energy-efficient due to the new bus control and limited heat development.

Frequently Asked Questions

The Ethernet connection with SMIII or Cloud is no longer working

The Ethernet connection depends on many factors. First and foremost, it should be verified whether communication on the local network (LAN) is still functioning perfectly. When the left status LED on the Ethernet connector lights up green, it indicates a good physical connection with a switch or router. The right LED will blink green upon data reception.

When the Ethernet interface is set to "AutoIP", it will only request (from a DHCP server) an IP address at the startup of the controller when the cable is already plugged in. Therefore, in the event of a complete power failure, it might happen that the controller starts up faster than the DHCP server (usually built into the router/modem). As a result, the controller may not have obtained an IP address and will need to be restarted. In the SMIII, the assigned IP address can be looked up via Utilities/Setup/Connection/TCP/IP Settings.

You can also configure the Ethernet interface with a fixed IP address. To establish a connection with the Cloud, a correctly configured Gateway and DNS are necessary. Ensure that the set IP address is chosen in the correct subnet, as connecting the controller to a different subnet may render it inaccessible.

Using the command prompt, you can now verify if the communication is running perfectly. For example: "PING 192.168.0.101 -t". If no timeout occurs after 1 minute, you have a perfect physical connection.

If the above rules are followed and no special firewall is present, the connection to the Cloud should also be in perfect order. If a Firewall is active, it is essential that all TCP communication via Port 80 to the Cloud is allowed.
My computer is not connecting via USB.

Normally, the USB driver is automatically installed when installing the Qbus System Manager III SW. However, if this is not the case, your computer will notify you that there is an issue installing the USB device when you connect to the controller. When this occurs, click on that message and choose to install the driver from a list or a specific location (search: C:\Program Files (x86)\Qbus\CTD USB driver if you have installed the program in the default location, otherwise select the location where you installed the program and this specific folder). This should properly connect the system.
The bus communication LED continues to burn

The "Bus" LED on the CTD shows when there is bus activity. A short heartbeat is shown every 5 seconds. When a module 'wakes up' the bus, the LED will be red. But it must turn off after a few seconds. However, if this "Bus" LED is continuously lit, this is probably due to a contradictory configuration or caused by a (broken) module on the bus.
In order to eliminate this last option, simply disconnect all bus wires and check the led...
A possible contradictory configuration can be: An input that is set as "Normally open" or "Normally closed" can not be forced. The same applies to an output that is connected to a detector. Or conflicting logic was used... This continuous bus communication must certainly be remedied.
How do you read an existing configuration?
This is a completely different procedure depending on the type of controller.
For the CTD controllers this goes as follows:
In the SMIII via "File" or "Utilities / Setup / SD card", click on "Recover QDB from SD".
After confirmation you choose the name and location where the file should be saved. The zipped QDB file is then read from the SD card of the CTD and saved. With a positive answer to the question "Unzip and open restored QDB?", All data will then be immediately available. If the data you were still working on was not sent or saved, you will first receive a notification to do so.

For a CTL controller follow the following procedure:
Because this controller does not yet have a large memory, only limited data can be recovered. Ao the names are abbreviated to 12 characters and serial numbers are not stored anywhere.
The first step is therefore to type in ALL serial numbers via SMII via "File / Modules". These 6-digit serial numbers can be found on every module (DIN rail, switch, detector, etc.). For the SWC0x switches, an extra option was provided to have them send their serial number via “Search for modules”.
When you then click on the "down arrow", you can read all this limited information.
Always use the latest software for configuration.

It is always recommended to use the most recent version. This version supports the newest modules and resolves all known bugs.
If, for example, you enter a serial number and the correct module information does not appear, you are likely not working with the most recent software.
A newer version will always be able to open the older files (.QDB) without data loss.
The latest version of the System Manager software, along with the user manual and version history, can be found in the knowledge center.
How to use the astronomical day clock?

All CTD controllers have a built-in annual calendar with the daily sunrise and sunset times. To use this, it is sufficient to assign a bistable output via the setup screen and select the location closest to the installation.
!! After you send the changes via the Red upload arrow, it is important to restart the CTD once to load the current times !!!
When uploading the data, a module always displays Err.255 (Module not found)
If Err.255 appears during the programming or verification of a module, this can have several causes:
First, verify whether the serial number was correctly entered as shown on the sticker on the module or its packaging. A serial number always consists of 6 digits or 10 hexadecimal characters (e.g., 0006B01ADE), with the first 4 determining the module type.
Conduct a test through “Utilities/Communication Check”. Enter the last 6 digits of the serial number here and click on “Start Module Test”. If communication with this module is perfect, you should see a nice flat line at 100%. If you see a flat low line, there is no communication. If the line is pulsed, communication is poor. Check whether the bus voltage (+/- 14V) is still correctly reaching the module or check the wiring. Try communicating with the module directly at the controller with 2 short bus wires (without any other connected module) before returning it via our RMA procedure.
Several modules can transmit their serial number:
All SWC variants can be searched via “File/Modules/Search for modules”. After clicking “Start search”, all connected switches will blink blue. Pressing any key on the switch will transmit its serial number.
All modules with a 10-character serial number can be read via “Utilities/Communication Check” if 1 and only 1 module of this new type is connected to the bus, by entering “FFFFFF” as a serial number.
How do you check if a DIN-Rail module is still functioning?

All recent DIN-rail modules are equipped with a fuse and status LED(s).
First, check if the upper PWR LED is still lit (green). If not, check the fuse and measure the power supply voltage. If both the fuse and the power supply voltage are correct, then the module power supply is defective and should be repaired or replaced.
First, always try a full reset: simultaneously disconnect both power and bus at the same time, then reconnect power (and bus if applicable).

The lower PWR will light up when the bus is correctly connected. In Stand-Alone mode, this PWR LED will remain OFF. The red status LED will briefly light up or blink when the module starts. However, if it continues to light up or blink, the firmware may be corrupted. Firmware can be updated via the SMIII under “Tools/Setup/Software/Modules: Firmware Upgrade”.

For end users, the installer is the first point of contact. They are familiar with the most common errors and will contact Qbus support for unknown issues.
If the module needs to be repaired or replaced, use our RMA procedure to return a module.

Technical info for installers

Function Description
The Qbus Controller can easily be used as an addition to a Qbus Stand-Alone (SA) system, but can also be used in installations where only bus wiring is provided.
This controller is suitable for all previous generations of Qbus modules.
For residential applications and SMEs, one controller is usually sufficient. In larger projects, multiple controllers can be linked and visualized via a network. This can be achieved through actions on Qbus Control for installations that need to be linked via the internet. Local connections between controllers can be made by adding Ubiebox or UbiePRO to the local network.
With the EQOmmand visualization software for Windows, you can visualize and control multiple installations via a local network or the internet. This requires activation per CTD.
The controller supplies all connected modules with the required power and data via a 2-wire bus. The firmware of the CTD is automatically updated, and the operation of the bus is not affected. This function can be set via System Manager III.
When connecting the modules, polarity does not matter. The term “Qbus module” encompasses every Qbus bus participant, or in other words, any Qbus component that has a BUS connection. Thus, a smart switch or a sensor is also referred to as a Qbus module. Distribute the load evenly across the buses by connecting approximately half of the modules to BUS1 and the other half to BUS2.
Depending on the version, a certain number of modules can be connected to the CTD. To allow for the use of a CTD in smaller installations, variants are available for a limited number of Qbus modules.
The following variants are available on the market:
CTDmax suitable for +/- 150 Qbus modules (75 per bus)
CTD40 for a maximum of 40 Qbus modules (expandable!)
CTD10 for a maximum of 10 Qbus modules (expandable!)
The CTD10 and CTD40 can be expanded with expansion cards (EXP15). Each expansion card allows for 15 additional modules to be connected. Once 4 expansion cards are added to CTD10 or 2 expansion cards to CTD40, these types of controllers become a full-fledged CTDmax. Thanks to this system, the CTD can grow with the installation.
There are several parameters that determine what a CTD can handle. First is the number of allowed modules (< CTDmax) and the total power consumption of these modules, as well as the number of addresses available to the controller. In the case of the CTDmax, the limitation lies in the current it can supply. CTDmax has 1000 mA for each bus, which means that an average of 75 Qbus modules can be connected to each bus.
Technical specifications
General Specifications CTD
Power Supply: 18VDC/3A SELV (Safety Extra-Low Voltage when grounded)
Ambient Temperature:
Operating Temperature: 10°C to 50°C
Storage Temperature: -10°C to 60°C
Maximum Humidity: 93%, no moisture condensation
Max. Installation Height: 2,000 meters.
CE
Bus: 18 VDC Safety Extra-Low Voltage
Non-toxic, compliant with WEEE/RoHS
Compliant with EN 60730-1:2000-11 +A11 2002
Physical Specifications
Enclosure: Plastic, self-extinguishing according to UL94-V0
Protection Grade: IP20, EN 60529
Installation: Quick installation on DIN-rail, width 4 modules
Dimensions (h x w x l): 62mm x 90mm x 72mm
Weight: approximately 140g
Sizing
Explanation of Symbols

Equipment where protection against the risk of electric contact is not only based on basic insulation but also on additional protection such as double insulation or reinforced insulation. There is no possibility for grounding.

Before connecting the device, it is mandatory to read the manual of the respective product. ISO7000-0434

Power supply connection (230V) to the power supply connector. IEC 60417-5036

CE conformity. All declarations of conformity are available upon request.
Warranty Provision

2 years from the date of delivery. The warranty becomes void if the module has been opened! The warranty period is extended by 2 years if it was installed by a certified Qbus installer.
In case of defects, Qbus support should be contacted by a certified installer. After registration with Qbus support, the defective module can be sent, unsealed and with a description of the defect, to our Qbus support.
Contact details:
Qbus NV
Joseph Cardijnstraat 19
B-9420 Erpe-Mere
Tel: +32 (0)53 60 72 10
Fax: +32 (0)53 60 72 19
Email: support@qbus.be

General

Safety instructions
Read the full manual before installing and activating the module.
WARNING
The CTD must be installed, started up and maintained by a certified electrical installer in accordance with the applicable legal regulations of the country.
This module is only suitable for DIN-rail installation EN50022. The module must be installed in a fireproof, enclosed control cabinet with ventilation slots.
Before working on the CTD, the voltage must be switched off.
Never connect external voltages (e.g. 230VAC) directly to the CTD or the Qbus bus! This will cause irreparable damage to the CTD and/or connected Qbus modules.
The CTD must not be opened. The warranty will be void if the controller is opened!

Installing and Wiring

Installation

Click the controller and power supply onto a DIN rail DIN EN50022.
Preferably place the CTD in a dry, lightly heated area and ensure sufficient distance between the controller and interference sources such as contactors, inverters, and power supplies. Ensure adequate ventilation in the distribution cabinet.
The required power supply is provided via a stabilized power source of 18VDC/3A (ref. CTDPWS/DIN standard included in the delivery of the CTD)
In case of a power interruption, a built-in non-volatile memory ensures that all data is retained for at least 10 years.
Power

A two-pole automatic circuit breaker with a maximum of C16A must be connected to the CTDPWS/DIN on the 230Vac side. However, automatic protection from C4A is sufficient. Always provide at least 5mm of free space next to the CTDPWS/DIN to ensure adequate ventilation. The correct mounting position for the power supply is vertical, with the input terminals at the bottom and the output at the top. Other mounting directions, such as upside down, horizontal, or on a tabletop, are not allowed.
Conductor cross-section: minimum 1.5mm² at 16A. Remove approximately 6mm of insulation from the conductors and screw the conductors into the L-N connectors.
Then connect the 18V side of the CTDPWS/DIN to the power terminals on the CTD. Remove approximately 6mm of insulation from the conductors and screw the conductors into the + and - connectors of the 18VDC power supply (CTDPWS/DIN).
Pay attention to polarity! Incorrect connections will render the CTD non-operational. Connect the + terminal of the CTDPWS/DIN to the + terminal of the CTD, and connect the - terminal of the CTDPWS/DIN to the - terminal of the CTD.
Remove approximately 7mm of insulation from the conductors and screw the conductors into the + and - terminals of the CTD.
Connect the ground terminal on the CTD to the general grounding! If grounding is not connected, the installation is not compliant!
WARNING: NEVER USE THE CTDPWS FOR OTHER PURPOSES SUCH AS POWERING LEDS.
BUS connection
The CTD has 2 independent buses. BUS1 and BUS2 must never be connected to each other!
Remove approximately 7mm of insulation from the conductors and screw the conductors into the BUS connectors of the CTD. Both solid and stranded wires of at least 1mm² can be used. For stranded wire, you must use ferrules that are crimped onto the wire ends with appropriate equipment. Each BUS connection is equipped with 4 screw terminals. Internally in the controller, per bus, a bridge is laid over the terminals A1 & A1 as well as at A2 & A2. Do not connect BUS1 and BUS2 to each other!
Qbus bus cabling:
Any shielded cable with conductors of at least 2 x 1 mm² can be used as bus cable. The recommended cable is the green shielded EIB cable when the conductors are twisted together in pairs to obtain a section of at least 2 x 1 mm². The shielding of the bus cable must, and may only, be connected at one end to the general grounding of the building.
The cable length between the CTD and a Qbus module can be up to 200m depending on the chosen topology. The bus topology can be laid out in the following forms:
Closed loop: up to 400m. The cable departs from the CTD and the returning cable from that loop is also connected to the same BUS of the same CTD
Multiple closed loops may be connected in parallel on the same bus terminals of the CTD.
Branches on a closed loop are allowed, as long as the cable length of this branch does not exceed 30m and the total cable length from CTD to Qbus module does not exceed 200m.
Star: The cable departs from the CTD to modules, and no returning cable is placed. In this topology, the maximum distance between the CTD and a Qbus module is 100m. The endpoint of a star cable should always stop at the last Qbus module.
Check the bus on the following points before connecting Qbus modules and/or the controller:
Ensure that the insulation resistance to earth is sufficiently large
Measure the closed loop on both conductors to detect any breaks.
Check the bus on the following points before and after connecting modules:
In a closed loop, verify that the polarity matches at the departing and returning bus cable.
When you power on the controller, a test procedure of 3 seconds is performed. Never switch the power on and off quickly. The minimum waiting time between power on and off is 5 seconds. Frequent and short power interruptions can cause the CTD to enter SAFE mode. The SAFE mode is stopped by performing the configuration and requested update via System Manager III.
Only power the CTD when the power supply can happen faultlessly.
LED indication:
! The LED indications are informative. The ranges listed below have a tolerance of +/- 5%.
18V LED power supply voltage indicator
GREEN: input voltage is between 16.5V<->20V
ORANGE: input voltage >20V
RED: input voltage <16.5V

16V LED bus voltage indicator
GREEN: always green when voltage is present

U LED bus voltage indicator
GREEN: bus voltage 16.5V<->20V
ORANGE: bus voltage >20V
RED: bus voltage <16.5V

I LED indicator bus current
GREEN: bus current 14mA<->900mA
ORANGE: bus current 900mA<->950mA
RED: bus current >950mA
OFF: bus current <14mA or bus short circuit (! indication available from firmware V4.11 - short-circuit resistance)

ETH LED for Ethernet communication
GREEN: during data transfer with communication interface
BUS LED for bus communication
GREEN: transfer to the bus is taking place
RED: data is being received from the bus
The Ethernet connector itself has LED indicators. These function as soon as the network connection is operational.

Connection diagram

Wiring diagram

The configuration of a CTDxx (and all modules from the QBUS-FULL) can be done by the free software System Manager III

Installation of System Manager III
The Qbus System Manager is the software you will use to configure the Qbus system. In the Qbus System Manager you can create I/O’s (on/off, timers, sequences, scenes, clock times, alarm systems, ...) and determine how those I/O’s will be controlled (which button on a switch/motion detector etc. activates each I/O) . All those settings are stored in a .qdb (Qbus DataBase) file.

The Qbus System Manager is available free of charge. You can download the latest version from THIS LINK. Once the System Manager has been downloaded and run, you will have a shortcut to the program on your desktop.

ATTENTION: the SYSTEM MANAGER III is ONLY used to program CTD controllers (CTD10, CTD40, CTDMax, CTD01Em, CTD01, CTD01E, CTD02E, CTD03E), AND IS NOT COMPATIBLE with CTL controllers (CTL16, CTL32. CTL64, CTL256). The configuration software for CTL controllers is the Serial Manager II, which can be downloaded from this link

Before installing the software, make sure that your PC meets the following requirements:
Supported Operating Systems: Windows 7, Windows 8, Windows 10, Windows 11
Processor: 1Ghz Pentium or equivalent recommended
RAM: minimum 1GB, preferably 4GB
Harddisk: 100 MB free space
Screen: 1024x768 (minimum) 1680x1050 of higher (recommended)
Ports: Ethernet port or WiFi
Communication with the CTD

Click in the menu bar of the System Manager IIIClick on the gear at the top right or via "Utilities" and then on "Setup" to configure the communication between the System Manager and the Controller.

You will then see the following screen:

In this screen you will see several tabs – click on the “Connection” tab to be able to connect to the Controller. The following screen will then be displayed:

When the correct IP address has been entered, by clicking on the button “Read Settings” in this screen you can see the status of the Controller in the first tab such as the temperature of the CTD, the load on each bus, the voltage on the bus,…If this is not visible, the correct communication method must first be chosen.
There are two ways to communicate with the Controller (CTD):
1.    over Ethernet: Only if the CTD has an Ethernet port – CTD10, CTD40, CTDMax, CTD01Em, CTD01E, CTD01E+, CTD02E, CTD03E.
2.    via USB: possible with the following 'older' CTDs: CTD01Em, CTD01, CTD01E, CTD01E+, CTD02E, CTD03E
If you wish to communicate via USB, click on the USB option in the setup screen. Make sure that the selected communication ports are set (default from COM1: to COM8:)
There are 2 ways to connect to the CTD via an Ethernet cable:
1.    If you are connecting to the CTD through a router, you must connect the controller to the router using a straight Ethernet cable (supplied with the CTD - usually yellow). It is important that the Ethernet cable is plugged in before the CTD is powered up. You will also need a straight cable to connect your computer to the router. If you have a wireless router, you can establish a wireless connection with your computer to this router.
2.    If you connect the ethernet port of the CTD directly to your computer, a straight ethernet cable will suffice in most cases. However, if the computer is a bit older, a crossover network cable (not included) is required. It is important that the Ethernet cable is plugged in and the computer is powered before the CTD is powered up.
With a correct physical connection, the left LED on the Ethernet port will light up green and the right LED will flash green when there is data traffic.
To operate the device via Ethernet, an IP address must be assigned.
When a device is powered up, it will only search for an IP address if there is already a good physical connection. When the CTD is connected via a router, this router has integrated DHCP, which ensures that each connected device is given an IP address.
To assign the correct IP address to the CTD, uncheck the USB and check the Ethernet option in the setup screen, then click "Search for CTD’s and settings…".

When you click on "Search for CTD’s and settings…”, the System Manager will search for CTD’s in your network via UDP broadcast. If the table remains completely empty, select the network interface in which the controller is located. When the desired CTD has been found, double click on the desired line to establish communication. If successful, the settings screen disappears, the correct IP address is entered in the "IP address or host name" field of the setup screen and the connection is established.
If you connect through a router, you will get an IP address that usually starts with 192.168.
When you connect to the Controller directly from your computer (without a router with DHCP server), you will get an IP address that starts with 169.254
The (Not-)connected status is always visible at the top right. Clicking on this icon connects or disconnects the USB/Ethernet connection to the controller.
ATTENTION!!
•    The local communication of the System Manager always takes place via port 8445, which is entered in the "setup" window, in the "Port" field next to the IP address.

Remark: Connect the network cable first, then power up the controller to request an IP address via DHCP. Of course, direct connection to a PC is possible, in which case a crossover cable is sometimes required (purchased separately at an IT specialist store).
Remark: you can give a fixed IP address to the Controller. In the TCP/IP Settings screen you can enter the desired IP address and then click on “Set IP / Gateway / DNS”. This is usually more interesting because in the event of a power failure, the CTD and other IP address can be assigned. Be sure to use an IP address that is not yet in use. If necessary, use the “PING” button to test this.

To set a password for the Ethernet connection:

The devices are delivered without a password. When the devices are connected to the Internet and you want to make changes over the Internet, a password must be set for security. To set a password, enter the old password and the new password twice and send it to the interface. This is done via the screen shown above; when you have entered a password twice, click on the option "send new password to the current connection".

If it is your first time using the software, we recommend that you read our knowledge center to configure new I/O's, modules, ...
Expand a CTD
Unlike previous series of CTD controllers, the bus load limitation with these controller types is not measured by the power consumption on the bus but by the exact number of connected modules.
The CTD is supplied as standard in 3 versions:
CTD10: maximum 10 modules
CTD40: maximum 40 modules
CTDmax: No limitation on number of modules. There is a maximum current consumption of 1000mA per bus
In terms of software, a CTD can be expanded per 15 modules. A CTD extended to 70 modules is equivalent to a CTDmax
When you have a network connection to the CTD, this can be done in two ways:

Online by entering the code of a purchased expansion card (EXP15):

You already have an account on Installer Dashboard or QbusControl:

From the setup screen in the System Manager III, click on the “Expansions” tab
Enter the case-sensitive code of the expansion card (3 times 4 characters)
And click on “Activate”.

If you are not yet connected to the Installer Dashboard, you will first be asked for the username and password:

If you already have an Installer Dashboard account, the CTD will be expanded immediately.
If you do not yet have an account on the Installer Dashboard, but do have an account on Qbuscontrol.com, this approval will be requested:

After entering your company name and VAT number, the Installer Dashboard is also activated and the CTD will also be expanded immediately.
If you do not yet have an account on the Installer Dashboard nor on QbusControl

Then you can create an account via https://installerdashboard.qbus.be
Afterwards follow the steps as mentioned above.

Offline: via telephone contact with a QBUS service employee

From the setup screen in the System Manager III, click on the “Expansions” tab
Click on the button “Add an expansion by phone” and the following screen will appear:

If you pass on your installer code from the Installer Dashboard together with the CTD serial number and the red key by telephone, the Qbus employee will provide you with a new 6-digit key. You will then receive an invoice for the requested number of licenses (15,30,45 or 60)
After entering the received key and clicking on “Activate”, the CTD will be expanded with the number of requested modules.
Connect a CTD to the Cloud (Qbus Control)

Click on “Read Settings” in the Setup Screen and you will be notified that the Controller is connected to the computer.
After that you can enter an e-mail address - once this is filled in click on the button “CTD -> Cloud” and the Controller is registered in the Qbus Cloud.
An activation code will now appear on the screen. You can copy this code when you add your controller in the QbusControl app or website!!!
If you want to add the CTD later to the account of the customer, the activation code will also be sent by e-mail to the specified e-mail address.

Register yourself on the Qbus Cloud:
Go to the site www.qbuscontrol.com and click the “Register” button.
SD-card and SD-banks

The SD card on the Qbus CTD has 10 memory banks. This means that you can save up to 10 configurations for your Qbus system on the SD card.
ALL data is stored separately for each bank. So the configuration, the list of modules, the events and the backup of the QDB file are saved separately per bank.
By clicking on the SD card tab, you can give these configurations different names – e.g. summer, winter, vacation, …

You can use analog logic to switch automatically between different SD banks, e.g. based on date and time (from summer to winter), or manually switch with a push button or by activating a scene. Note that you must have separate .qdb files with their own specific configurations to load into the various SD banks (for example, you create a "summer" configuration (e.g. summer.qdb) and a "winter" configuration (winter. qdb) and loads the summer configuration in SD Bank 1 and the winter configuration in SD Bank 2).
With the button 'Restore QDB from SD' the backup of the configuration file from the SD card can be transferred to the computer. After this action, you will be asked to unzip and open this QDB. After possibly saving the current data, the restored configuration will open immediately.
The button “Format SD” prepares a new SD card for use in the controller. This will erase all data.
All recent controllers with Bootstrap V2.2 or higher support SD cards of 4GB or more.
However, older controllers only support 1GB or 2GB SD cards.