In the Qbus software you can select 5 timer modes:
- Timer 1 (“Forget timer”):
Each time the button is pressed, the timer is switched on or off. For example, in a hall, the button is pressed once to turn on the light for a certain period of time (set by clicking the "Properties" button and using the "Min" or "Sec" buttons to select the time in minutes or seconds), and a second time to extinguish the lights.
ATTENTION: work as long as possible in seconds (up to more than 4 minutes) to have an accuracy of 1 second. If you set the timer in minutes, the accuracy is 1 MINUTE.
- Timer 2 ("Staircase timer"):
Each time the button is pressed, the timer is reset to the set value. For example, if your timer is set to 3 minutes, the timer will run for 3 minutes each time you press the button. This timer does not work with motion detectors - motion detectors can only control toggle I/O’s and will continue to count down for the period set in the detector module.
From CTD FW3.08 the Timer2 has an extra parameter: When the “Automatic Reset” is turned on, this timer will be reset to its set value when it reaches 0. Such a timer can be useful for continuous testing in analogue logic.
- Timer 3 (“lazy timer”):
The timer is activated the first time the button is pressed. Pressing the button a second time switches on/off mode - the value set in the timer is then no longer relevant. A third press of the button switches the I/O off. For the front door, for example, you can use a timer, but you also have the option of leaving the light on indefinitely without the timer turning it off automatically. If you have selected Timer 3 and set it to, for example, 3 minutes, and you press the button, the timer will be activated for 3 minutes, and the light will turn off at the end of that period. If you press the button twice, the light will stay on until you press it a third time - then the light will go out.
- Timer 4:
This is a linked timer: an impulse (pressing a button, motion detection, ...) activates an I/O (e.g. I/O 1). After a certain period of time (can be set by the user), a second I/O is activated (e.g. I/O 2, selected by the user). When I/O 1 (the “master”) is turned off, I/O 2 (the “slave”) will also be turned off after a preset period. Example: When you come home in the evening, the motion detector outside turns on the front door lighting, and 1 minute later the hallway lighting.
To program this timer, you must assign the Timer4 master for the first I/O. When you click "enter", a drop-down screen will ask you to define the I/O that will be associated (with a certain delay) to this first I/O (will be defined as Timer4 slave). You can set the delay time by clicking "Properties".
The delay time can be set by pressing the “Properties” button.
Timer 5
With this timer you can link a manual input (switch) and a detector input. A detector activates an I/O only when it detects movement or when the light level falls below a set threshold (see below in MDI/MDO programming). In the Qbus system, a detector has priority over a switch. If you also want to control an I/O controlled by a detector with a switch, the I/O will not respond to the command of the switch if the parameters of the detector do not match (e.g. no movement detected or light level still too high - the detector turns your I/O off immediately after you command the switch to turn it on).
You can avoid this problem by using a Timer 5. A timer 5 is programmed as follows:
Step 1: Create a new I/O (Timer 5 Manual) on the switch you want to use to control that I/O. When you click "enter", you will be asked to name the I/O that you want to control with the detector (you will have two names for the same I/O, one for the manual control, the other for the detector - add the I/O "manual" or "detector" so you can distinguish between the two).
Step 2: You must also link Timer 5 Detector to the detector you want to use to control this I/O. If you program a SWC04M, you can link this Timer 5 Detector directly to first input key. However, if you use an MDI01 or SEN04 as a detector, you must create a fictitious bistable I/O, as an MDI01 or SEN04 can only control bistable I/O’s (no timers). In this case, first create a fictitious bistable I/O, and link this fictitious I/O to Timer 5 Detector via logic
Step 3: In the MDI01 or SEN04, use the fictitious I/O as one of the controlled I/O’s: when the detector now detects something, it will switch on the fictitious I/O, which in turn activates Timer 5 Detector (both are linked via an internal logic function ).
Step 4: In order to give priority to the manual control of the I/O over the Detector control, you must assign the manual I/O to the relay to which the I/O is connected. Your manual operation now takes precedence over your detector.