Skip to main content

General I/O parameters

Most types of I/O's have some common parameters. These are explained below.

Qbus System Manager III Manual Update 04 2025 pdf image 144

Display: the 'short' name (max. 12 characters) that will appear on a display (e.g. TSC5.8, ViZiR, Tastu Display, RoomMate…)

Display Warning: Warning on a display when the I/O is still active. On a TSC 5.8. you can click -check the status- and you will get an overview of all I/O’s that are still active and that have been selected via their properties screen.

Simulation: Should this I/O be taken into account for the presence simulation tool, a standard part of the system? E.g. not helpful to have a thermostat outlet or a light in a hallway without outside windows as part of a simulation.

Switch Time: This graphical weekly overview provides an easy way to update the clock times of e.g. a thermostat.

Qbus System Manager III Manual Update 04 2025 pdf image 148

An I/O can be turned on (Yellow) or off (Black) at a specific time.
With a thermostat, the color of the regime is displayed.

Editing is possible via the grid. The name and time of the clock time can be changed. The desired status can be set, a weekday can be checked and unchecked. And in the last column, the full clock time can be temporarily switched on or off.

When a parameter is adjusted and there are other I/O’s in this clock time, you will be asked to adjust the entire clock time or create a new clock time, so that the time of the other I/O’s remains unchanged.

You can also remove or add a clock time with the - and + buttons, right above the table.

 

Logic / Link: used to create multilinks. A multilink is a setting where you can control several I/O’s with one switch. This is not the same as a scene - a scene allows you to set various I/O’s to a predetermined level. With a multilink you can control various I/O’s together (e.g. adjust the setting of all dimmers in your living room together; with a scene you can only set them to 1 value).

 

Events: If you set the button under 'Events' in the Properties screen to "on", all status changes will be saved to the SD card in the controller. Reading the event data from the SD-card is explained via 'extracting data from the CTD'.