Domino
The DOMINO system is DUEMMEGI’s proprietary bus architecture for home automation. HSYCO fully integrates with this system through the DFCP or DFCP4 control and gateway module, and its FXP-XT serial communication protocol.
A serial connection between the DFCP and the HSYCO SERVER is required for the integration, either directly through the server’s RS-232 port or via the RS-232 port of a supported serial to IP gateway, including the WEBS module.
The DFCP4 can be connected via the integrated serial to IP gateway.
The Domino I/O Server requires DFCP firmware version 2.0 or later for normal operation. Firmware version 4.3 or later is required to support field upgrade of installed Domino modules. The DCPIDE configuration tools pass-through support for secure access to the DFCP via HSYCO requires DCPIDE version 3.2.1 or later.
Contents
- 1 Communication
- 2 HSYCO Configuration
- 3 Initialization and Connection Events
- 4 The Device Configuration Database
- 5 DFCP Virtual Data Points and Registers
- 6 DFCP Internal Clock
- 7 DOMINO Modules Events and Control
- 7.1 DF4I
- 7.2 DFCK3
- 7.3 DF8I
- 7.4 DF2R
- 7.5 DF4R, DF4RP
- 7.6 DF4RP/I
- 7.7 DFDM, DFDI, DFDI2, DFDI2B, DFDT
- 7.8 DFDMX
- 7.9 DFDALI
- 7.10 DFDV
- 7.11 DFTP
- 7.12 DFTP/I
- 7.13 DFTR
- 7.14 DF4IL
- 7.15 DF8IL
- 7.16 DFIGLASS
- 7.17 DF4I/V
- 7.18 DFAI
- 7.19 DFLUX, DFSUN
- 7.20 DFCT
- 7.21 DFTZ
- 7.22 DFRHT
- 7.23 DFMETEO
- 7.24 DFCC
- 7.25 DFANA
- 7.26 DFCC2
- 8 User Interface
- 9 Release Notes
Communication
Employ a DE-9 (often called DB-9) male-female RS-232 straight cable to connect the RS-232 DFCP port to the serial port on HSYCO SERVER or serial gateway.
RS-232 parameters:
| Baud rate | 9600, 38400, 57600 or 115200 bps (according to the DFCP serial port setting) |
| Data bits | 8 |
| Stop bit | 1 |
| Parity | none |
| Flow control | none |
A speed of 115200 bps is recommended to achieve good performance, particularly when the number of devices connected to the bus is large.
HSYCO Configuration
You can define and connect to more than one DOMINO bus using several DFCP gateways.
The DOMINO I/O Server also supports dual, redundant connections between HSYCO and DFCP.
If the main connection fails, HSYCO automatically re-routes the communication with DFCP through the fail-over connection.
Options
| ID | Default | Values | Description |
|---|---|---|---|
| startupevents | false | true | generate IO events also during the driver’s start-up phase |
| false | start generating events only after HSYCO is aligned with the current status of the system | ||
| inputdiscovery | false | true | auto-detects DOMINO’s input devices as configured in the DFCP, and automatically creates the list of all detected devices and individual data points in the systemtopo.txt file. Should be enabled to allow the automatic update of (button) objects’ states |
| false | auto-detect for input devices is disabled | ||
| outputdiscovery | true | true | auto-detects DOMINO’s output devices as configured in the DFCP, and automatically creates the list of all detected devices and individual data points in the systemtopo.txt file. Should be enabled to allow the automatic update of (button) objects’ states |
| false | auto-detect for output devices is disabled | ||
| virtualdiscovery | false | true | auto-detects DOMINO’s virtual points for input and output devices as configured in the DFCP, and automatically creates the list of all detected virtual data points in the systemtopo.txt file. Should be enabled to allow the automatic update of (button) objects’ states |
| false | auto-detect for devices’ virtual data points is disabled | ||
| virtualpoints | false | 1...2033 | enables polling for the first n virtual points of the DFCP. Enable this option only if you need to generate I/O events based on these virtual points |
| true | enables polling for all the 2032 virtual points of the DFCP | ||
| false | polling of the DFCP virtual data points is disabled | ||
| registers | false | 1...1024 | enables polling for registers R0-Rn of the DFCP. Enable this option only if you need to generate I/O events based on these registers |
| true | enables polling for registers R0-R127 of the DFCP | ||
| false | polling of the DFCP registers is disabled | ||
| powerdisplay | false | true | enables polling for registers R0-Rn of the DFCP. Enable this option only if you need to generate I/O events based on these registers |
| ≥ 0 (DFANA address) | enables the automatic display in the GUI of the total real power measured by a DFANA module connected to this DFCP. Note that, if you have more than one DFCP gateway, you should enable this option for one gateway only | ||
| false | power display disabled for this DFCP | ||
| powersensivity | 50 | ≥ 0 | measured power changes are reported only if the difference from last reading is equal or greater than the power sensivity option, in Watts |
| powerinterval | 1 | ≥ 0 | power polling interval for the DFCC meter, in seconds |
| detectevents | false | true | generate forced events when a device is detected at start-up |
| false | do not generate events when a device is detected at start-up | ||
| toolspassword | string | set this option with a long string (only letters and numbers) password to allow the remote connection of DFCP-IDE and other configuration tools to the DFCP gateways that are connected to HSYCO. For additional security, it is recommended to set this option only when required | |
| language | english | en it fr | language for all messages from the DOMINO system: English, Italian or French |
Initialization and Connection Events
| Event name | Value | Description |
|---|---|---|
| connection | online | connection established to the DFCP module |
| offline | HSYCO can’t connect to the DFCP module | |
| detected.input.<n>. |
model name | an input device of the type passed as value has been detected at address <n>, using |
| detected.output.<n>. |
model name | an output device of the type passed as value has been detected at address <n>, using |
The Device Configuration Database
The systemtopo.txt file contains the list of all devices and their individual input, output and virtual data points that could be directly associated to graphic object in the Web-based user interface. This file can be filled manually or automatically by HSYCO at start-up. To enable automatic discovery and automatic generation of devices’ information in the systemtopo file, use the inputdiscovery, outputdiscovery and virtualdiscovery options in Settings. The default behavior is to only discover devices with output data points.
This is an example of an automatically generated systemtopo.txt file:
(devices) domino.o10.1 : LIGHT ; LIGHT domino.o6.1 : LIGHT ; DIMMER domino.o7.2 : LIGHT ; LIGHT domino.o7.1 : LIGHT ; DIMMER domino.o9.2 : AUTOM ; VSHUT domino.o5.4 : LIGHT ; LIGHT domino.o9.1 : AUTOM ; VSHUT domino.o5.3 : LIGHT ; LIGHT domino.o5.2 : LIGHT ; LIGHT domino.o5.1 : LIGHT ; LIGHT
You should then manually add comments and other optional parameters:
(devices) domino.o10.1 : LIGHT ; LIGHT; main entrance light domino.o6.1 : LIGHT ; DIMMER; lobby dimmer domino.o7.2 : LIGHT ; LIGHT; kitchen workbench domino.o7.1 : LIGHT ; DIMMER; kitchen main dimmer
DFCP Virtual Data Points and Registers
The DFCP implements 2032 virtual points for binary (on/off) data and 1024 registers for positive scalar values (0-65535).
All the virtual points and the registers can optionally generate I/O events. You can also write to the virtual data points and registers using the IO action in EVENTS or ioSet() method in Java.
You cannot directly control the DFCP virtual data points and registers using GUI objects.
To enable polling of the current state of the DFCP’s virtual data points, enable the virtualpoints options in hsyco.ini.
To enable polling of the current state of the DFCP’s registers, enable the registers options in hsyco.ini.
If you only have to write to virtual points or registers, enabling polling is not strictly required.
| ID | Value | R/W | Description |
|---|---|---|---|
| v0.<n> | 0 | RW | virtual data point <n> off (<n>: 1-2032) |
| 1 | RW | virtual data point <n> on (<n>: 1-2032) | |
| r0.<n> | <x> | RW | register <n> off (<n>: 0-1023) set to value <x> (<x>: 0-65535) |
DFCP Internal Clock
The DFCP module has an integrated real-time clock. You can use the clock datapoint to read the DFCP date and time, and set the DFCP clock to HSYCO’s current time.
| ID | Value | R/W | Description |
|---|---|---|---|
| clock | yyyy-mm-dd hh:mm:ss | R | the DFCP clock current time |
| read | W | read the DFCP clock, and the delta with HSYCO’s time | |
| sync | W | set the DFCP clock to HSYCO’s current time | |
| clock.delta | integer number | R | the delta time in seconds between the DFCP and HSYCO clocks. A positive number means that the DFCP clock is ahead of HSYCO |
DOMINO Modules Events and Control
| Module Code | Description |
|---|---|
| DF4I | 4 digital inputs |
| DFCK3 | clock |
| DF8I | 2x4 digital inputs |
| DF2R | 2 outputs (relay) |
| DF4R, DF4RP | 4 outputs (power relay) |
| DF4RP/I | 4 generic inputs ON-OFF + 4 outputs |
| DF8RIT | multifunction module with 8 digital inputs, 8 outputs (power relay), 1 temperature sensor/controller |
| DFDI, DFDI2, DFDI2B, DFDM, DFDT | 1 output (dimmer) |
| DFDMX | DMX interface |
| DFDALI | DALI interface |
| DFDV | 1 output (1-10V - ballast) + 1 output (power relay) |
| DFTP | 2 outputs (shutters) |
| DFTP/I | 2 outputs (shutters) + 4 digital inputs |
| DFTR | 2 outputs (shutters) + 1 output (relay) |
| DF4IL | 4 digital inputs + 4 outputs (LED) |
| DF8IL | 8 digital inputs + 8 outputs (LED) |
| DFAI | 2 analog inputs |
| DFLUX, DFSUN | light sensor |
| DFCT/DFTZ | temperature sensor |
| DFRHT | temperature and humidity sensor |
| DFMETEO | weather module |
| DFANA | electric energy network analyser |
| DFCC | electric energy meter and load manager |
| DFCC2 | electric energy meter and load manager |
DF4I
The DF4I is an input module with 4 digital inputs.
It uses one address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.1 | 0 | R | input pin 1 off |
| 1 | R | input pin 1 on | |
| i<address>.2 | 0 | R | input pin 2 off |
| 1 | R | input pin 2 on | |
| i<address>.3 | 0 | R | input pin 3 off |
| 1 | R | input pin 3 on | |
| i<address>.4 | 0 | R | input pin 4 off |
| 1 | R | input pin 4 on |
DFCK3
The DFCK3 is an input module for managing up to 15 different zones with an integrated clock.
It uses one address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.1 | 0 | R | input pin 1 off |
| 1 | R | input pin 1 on | |
| i<address>.2 | 0 | R | input pin 2 off |
| 1 | R | input pin 2 on | |
| i<address>.3 | 0 | R | input pin 3 off |
| 1 | R | input pin 3 on | |
| i<address>.4 | 0 | R | input pin 4 off |
| 1 | R | input pin 4 on | |
| i<address>.5 | 0 | R | input pin 5 off |
| 1 | R | input pin 5 on | |
| i<address>.6 | 0 | R | input pin 6 off |
| 1 | R | input pin 6 on | |
| i<address>.7 | 0 | R | input pin 7 off |
| 1 | R | input pin 7 on | |
| i<address>.8 | 0 | R | input pin 8 off |
| 1 | R | input pin 8 on | |
| i<address>.9 | 0 | R | input pin 9 off |
| 1 | R | input pin 9 on | |
| i<address>.10 | 0 | R | input pin 10 off |
| 1 | R | input pin 10 on | |
| i<address>.11 | 0 | R | input pin 11 off |
| 1 | R | input pin 11 on | |
| i<address>.12 | 0 | R | input pin 12 off |
| 1 | R | input pin 12 on | |
| i<address>.13 | 0 | R | input pin 13 off |
| 1 | R | input pin 13 on | |
| i<address>.14 | 0 | R | input pin 14 off |
| 1 | R | input pin 14 on | |
| i<address>.15 | 0 | R | input pin 15 off |
| 1 | R | input pin 15 on |
DF8I
The DF8I is an input module with 2x4 digital inputs.
It uses two consecutive addresses in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.1 | 0 | R | input pin 1 off |
| 1 | R | input pin 1 on | |
| i<address>.2 | 0 | R | input pin 2 off |
| 1 | R | input pin 2 on | |
| i<address>.3 | 0 | R | input pin 3 off |
| 1 | R | input pin 3 on | |
| i<address>.4 | 0 | R | input pin 4 off |
| 1 | R | input pin 4 on | |
| i<address+1>.1 | 0 | R | input pin 1 off |
| 1 | R | input pin 1 on | |
| i<address+1>.2 | 0 | R | input pin 2 off |
| 1 | R | input pin 2 on | |
| i<address+1>.3 | 0 | R | input pin 3 off |
| 1 | R | input pin 3 on | |
| i<address+1>.4 | 0 | R | input pin 4 off |
| 1 | R | input pin 4 on |
DF2R
The DF2R is an output module with 2 relay outputs.
It uses one address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| o<address>.1 | 0 | RW | output pin 1 off |
| 1 | RW | output pin 1 on | |
| o<address>.2 | 0 | RW | output pin 2 off |
| 1 | RW | output pin 2 on |
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
DF4R, DF4RP
The DF4R (DF4RP) is an output module with 4 relay outputs.
It uses one address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| o<address>.1 | 0 | RW | output pin 1 off |
| 1 | RW | output pin 1 on | |
| o<address>.2 | 0 | RW | output pin 2 off |
| 1 | RW | output pin 2 on | |
| o<address>.3 | 0 | RW | output pin 3 off |
| 1 | RW | output pin 3 on | |
| o<address>.4 | 0 | RW | output pin 4 off |
| 1 | RW | output pin 4 on |
DF4RP/I
The DF4RP/I is an output module with 4 generic inputs and 4 relay outputs.
It uses one input address and one output address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.1 | 0 | R | input pin 1 off |
| 1 | R | input pin 1 on | |
| o<address>.1 | 0 | RW | output pin 1 off |
| 1 | RW | output pin 1 on | |
| i<address>.2 | 0 | R | input pin 2 off |
| 1 | R | input pin 2 on | |
| o<address>.2 | 0 | RW | output pin 2 off |
| 1 | RW | output pin 2 on | |
| i<address>.3 | 0 | R | input pin 3 off |
| 1 | R | input pin 3 on | |
| o<address>.3 | 0 | RW | output pin 3 off |
| 1 | RW | output pin 3 on | |
| i<address>.4 | 0 | R | input pin 4 off |
| 1 | R | input pin 4 on | |
| o<address>.4 | 0 | RW | output pin 4 off |
| 1 | RW | output pin 4 on |
DFDM, DFDI, DFDI2, DFDI2B, DFDT
The DFDM, DFDI, DFDI2, DFDI2B and DFDT are output modules with 1 dimmer output.
They use one address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| o<address> | program | R | program mode |
| fault | R | dimmer fault | |
| auto | R | auto mode | |
| man | R | manual mode | |
| o<address>.1 | off | RW | dimmer off |
| 1...100% | RW | percent dimmer level | |
| on | RW | dimmer on at last level | |
| o<address>.ramp | save | RW | saves the current ramp as default |
| 1...30 | RW | ramp value in seconds (1 sec steps up to 10 and 2 sec steps up to 30) | |
| 40, 50, 60 | RW | ramp value in seconds (10 sec steps) | |
| o<address>.setpoint | 0...1023 | RW | setpoint level |
| o<address>.hysteresis | 0...255 | RW | tolerance level |
| o<address>.time | 0...255 | RW | period (seconds) |
The dimmer level can be set using additional formats besides the standard percent values:
- absolute positive integer number between 0 and 100
- percent number, formatted as x%
- fractional format, formatted as “n/m”, where 0 <= n <= m.
DFDMX
The DFDMX is a DMX-512 protocol output module.
It uses one address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| o<address>.<command> | 0...255 | RW | commands and values according to the DFDMX programming manual |
DFDALI
The DFDALI is a DALI interface module. Using the DFDALI you can control up to 32 DALI devices.
You can control individual devices, groups or broadcast commands to all devices.
It uses one input (if enabled) and one output address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| o<address> | refresh | RW | queries the DFDALI module to update the current status of all DALI devices |
| o<address> | off | RW | broadcast off command |
| o<address>.all
o<address>.0 |
<level> | RW | broadcast level command |
| o<address>.group.<DALI group> | off | RW | broadcast off command |
| <level> | RW | group level command | |
| o<address>.<DALI address> | off | RW | turn off a single device |
| <level> | RW | set a single device to a specific level | |
| > 100 | RW | special functions, having values between 101 and 255, as defined in the DFDALI manual | |
| i<address>.polling | off | RW | polling mode is disabled |
| on | RW | polling mode is enabled | |
| i<address>.test | 0 | RW | test button not pressed |
| 1 | RW | test button pressed | |
| i<address>.dali | nopower | RW | power failure on the DALI bus |
| open | RW | DALI bus is open | |
| short | RW | DALI bus is shorted | |
| on | RW | DALI bus on | |
| i<address>.1 | fault | RW | DALI device 1 reporting a lamp failure |
| unknown | R | DALI device 1 status unknown |
The DALI level can be set using additional formats besides the standard percent values:
- absolute positive integer number between 0 and 100
- percent number, formatted as x%
- fractional format, formatted as “n/m”, where 0 <= n <= m
- special functions, having values between 101 and 255, as defined in the DFDALI manual.
DFDV
The DFDV is an output module with 1 output (1-10V for ballast) + 1 generic power relay output. It uses one address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| o<address>.1 | off | RW | dimmer off |
| 1 ... 100% | RW | percent dimmer level | |
| on | RW | dimmer on at last level | |
| o<address>.2 | 0 | RW | output pin 1 off |
| 1 | RW | output pin 1 on |
The dimmer level can be set using additional formats besides the standard percent values:
- absolute positive integer number between 0 and 100
- fractional format, formatted as “n/m”, where 0 <= n <= m.
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
DFTP
The DFTP is an output module for 2 shutters.
It uses one output address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| o<address>.1 | up | RW | shutter up command |
| down | RW | shutter down command | |
| stop | RW | shutter stop command | |
| unknown | R | unknown state | |
| offup | RW | shutter off, up position | |
| offdown | RW | shutter off, down position | |
| o<address>.2 | up | RW | shutter up command |
| down | RW | shutter down command | |
| stop | RW | shutter stop command | |
| unknown | R | unknown state | |
| offup | RW | shutter off, up position | |
| offdown | RW | shutter off, down position |
DFTP/I
The DFTP is an input/output module for 2 shutters and 4 generic inputs.
It uses one input and one output address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.1 | 0 | R | input pin 1 off |
| 1 | R | input pin 1 on | |
| o<address>.1 | up | RW | shutter up command |
| down | RW | shutter down command | |
| stop | RW | shutter stop command | |
| unknown | R | unknown state | |
| offup | RW | shutter off, up position | |
| offdown | RW | shutter off, down position | |
| i<address>.2 | 0 | R | input pin 2 off |
| 1 | R | input pin 2 on | |
| o<address>.2 | up | RW | shutter up command |
| down | RW | shutter down command | |
| stop | RW | shutter stop command | |
| unknown | R | unknown state | |
| offup | RW | shutter off, up position | |
| offdown | RW | shutter off, down position | |
| i<address>.3 | 0 | R | input pin 3 off |
| 1 | R | input pin 3 on | |
| i<address>.4 | 0 | R | input pin 4 off |
| 1 | R | input pin 4 on |
DFTR
The DFTR is an output module with 1 shutter output and 1 relay output.
It uses one address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| o<address>.1 | up | R | shutter up |
| down | R | shutter down | |
| unknown | R | unknown state | |
| offup | R | shutter offup | |
| offdown | R | shutter offdown | |
| o<address>.2 | 0 | R | output pin 2 off |
| 1 | R | output pin 2 on |
DF4IL
The DF4IL is an input/output module with 4 digital inputs and 4 digital open collector outputs for LEDs.
It uses one input and one output address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.1 | 0 | R | input pin 1 off |
| 1 | R | input pin 1 on | |
| o<address>.1 | 0 | RW | LED 1 off |
| 1 | RW | LED 1 on | |
| i<address>.2 | 0 | R | input pin 2 off |
| 1 | R | input pin 2 on | |
| o<address>.2 | 0 | RW | LED 2 off |
| 1 | RW | LED 2 on | |
| i<address>.3 | 0 | R | input pin 3 off |
| 1 | R | input pin 3 on | |
| o<address>.3 | 0 | RW | LED 3 off |
| 1 | RW | LED 3 on | |
| i<address>.4 | 0 | R | input pin 4 off |
| 1 | R | input pin 4 on | |
| o<address>.4 | 0 | RW | LED 4 off |
| 1 | RW | LED 4 on |
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
DF8IL
The DF8IL is an input/output module with 8 digital inputs and 8 digital open collector outputs for LEDs.
It uses 4 input and 4 output addresses in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.1 | 0 | R | input pin 1 off |
| 1 | R | input pin 1 on | |
| i<address>.2 | 0 | R | input pin 2 off |
| 1 | R | input pin 2 on | |
| i<address>.3 | 0 | R | input pin 3 off |
| 1 | R | input pin 3 on | |
| i<address>.4 | 0 | R | input pin 4 off |
| 1 | R | input pin 4 on | |
| i<address+1>.1 | 0 | R | input pin 5 off |
| 1 | R | input pin 5 on | |
| i<address+1>.2 | 0 | R | input pin 6 off |
| 1 | R | input pin 6 on | |
| i<address+1>.3 | 0 | R | input pin 7 off |
| 1 | R | input pin 7 on | |
| i<address+1>.4 | 0 | R | input pin 8 off |
| 1 | R | input pin 8 on | |
| i<address+2>.1 | 0 | R | LED 1 is off |
| 1 | R | LED 1 is on | |
| i<address+2>.2 | 0 | R | LED 2 is off |
| 1 | R | LED 2 is on | |
| i<address+2>.3 | 0 | R | LED 3 is off |
| 1 | R | LED 3 is on | |
| i<address+2>.4 | 0 | R | LED 4 is off |
| 1 | R | LED 4 is on | |
| i<address+3>.1 | 0 | R | LED 5 is off |
| 1 | R | LED 5 is on | |
| i<address+3>.2 | 0 | R | LED 6 is off |
| 1 | R | LED 6 is on | |
| i<address+3>.3 | 0 | R | LED 7 is off |
| 1 | R | LED 7 is on | |
| i<address+3>.4 | 0 | R | LED 8 is off |
| 1 | R | LED 8 is on | |
| v<address+2>.1 | 0 | RW | LED 1 is off |
| 1 | RW | LED 1 is on | |
| v<address+2>.2 | 0 | RW | LED 2 is off |
| 1 | RW | LED 2 is on | |
| v<address+2>.3 | 0 | RW | LED 3 is off |
| 1 | RW | LED 3 is on | |
| v<address+2>.4 | 0 | RW | LED 4 is off |
| 1 | RW | LED 4 is on | |
| v<address+3>.1 | 0 | RW | LED 5 is off |
| 1 | RW | LED 5 is on | |
| v<address+3>.2 | 0 | RW | LED 6 is off |
| 1 | RW | LED 6 is on | |
| v<address+3>.3 | 0 | RW | LED 7 is off |
| 1 | RW | LED 7 is on | |
| v<address+3>.4 | 0 | RW | LED 8 is off |
| 1 | RW | LED 8 is on |
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
Note that the first two output addresses are reserved and should not be used. Use address + 2 and address + 3 to control the LEDs.
DFIGLASS
The DFIGLASS is an input/output module with 6 touch buttons with addressable LEDs and a buzzer for audio feedback.
It uses 1 input and 1 output addresses in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.1 | 0 | R | button 1 off |
| 1 | R | button 1 on | |
| i<address>.2 | 0 | R | button 2 off |
| 1 | R | button 2 on | |
| i<address>.3 | 0 | R | button 3 off |
| 1 | R | button 3 on | |
| i<address>.4 | 0 | R | button 4 off |
| 1 | R | button 4 on | |
| i<address>.5 | 0 | R | button 5 off |
| 1 | R | button 5 on | |
| i<address>.6 | 0 | R | button 6 off |
| 1 | R | button 6 on | |
| i<address>.fault | 0 | R | no fault |
| 1 | R | touch keypad fault | |
| i<address>.led.1 | 0 | RW | led 1 off |
| 1 | RW | led 1 on | |
| i<address>.led.2 | 0 | RW | led 2 off |
| 1 | RW | led 2 on | |
| i<address>.led.3 | 0 | RW | led 3 off |
| 1 | RW | led 3 on | |
| i<address>.led.4 | 0 | RW | led 4 off |
| 1 | RW | led 4 on | |
| i<address>.led.5 | 0 | RW | led 5 off |
| 1 | RW | led 5 on | |
| i<address>.led.6 | 0 | RW | led 6 off |
| 1 | RW | led 6 on | |
| i<address>.backlight | 0 | RW | backlight off |
| 1 | RW | backlight on | |
| i<address>.buzzer | 0 | RW | buzzer disabled |
| 1 | RW | buzzer enabled |
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
DF4I/V
The DF4I/V is an input/output module with 4 digital inputs and 12 digital virtual outputs.
It uses four consecutive addresses in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.1 | 0 | R | input pin 1 off |
| 1 | R | input pin 1 on | |
| i<address>.2 | 0 | R | input pin 2 off |
| 1 | R | input pin 2 on | |
| i<address>.3 | 0 | R | input pin 3 off |
| 1 | R | input pin 3 on | |
| i<address>.4 | 0 | R | input pin 4 off |
| 1 | R | input pin 4 on | |
| v<address+1>.1 | 0 | RW | virtual pin 1 off |
| 1 | RW | virtual pin 1 on | |
| v<address+1>.2 | 0 | RW | virtual pin 2 off |
| 1 | RW | virtual pin 2 on | |
| v<address+1>.3 | 0 | RW | virtual pin 3 off |
| 1 | RW | virtual pin 3 on | |
| v<address+1>.4 | 0 | RW | virtual pin 4 off |
| 1 | RW | virtual pin 4 on | |
| v<address+2>.1 | 0 | RW | virtual pin 1 off |
| 1 | RW | virtual pin 1 on | |
| v<address+2>.2 | 0 | RW | virtual pin 2 off |
| 1 | RW | virtual pin 2 on | |
| v<address+2>.3 | 0 | RW | virtual pin 3 off |
| 1 | RW | virtual pin 3 on | |
| v<address+2>.4 | 0 | RW | virtual pin 4 off |
| 1 | RW | virtual pin 4 on | |
| v<address+3>.1 | 0 | RW | virtual pin 1 off |
| 1 | RW | virtual pin 1 on | |
| v<address+3>.2 | 0 | RW | virtual pin 2 off |
| 1 | RW | virtual pin 2 on | |
| v<address+3>.3 | 0 | RW | virtual pin 3 off |
| 1 | RW | virtual pin 3 on | |
| v<address+3>.4 | 0 | RW | virtual pin 4 off |
| 1 | RW | virtual pin 4 on |
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
DFAI
The DFAI is an input module (0-10V) with 2 analog inputs.
It uses two consecutive input addresses in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address> | 0...1000 | R | input voltage in Volt/100 |
| i<address+1> | 0...1000 | R | input voltage in Volt/100 |
DFLUX, DFSUN
The DFLUX and DFSUN are input modules with 1 analog light sensor.
They use one input address in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address> | 0...1023 | R | lux level (raw level, not translated to the lux range) |
DFCT
The DFCT is an input/output temperature sensor module.
It uses two consecutive input addresses and five consecutive output addresses in the DOMINO bus.
The DFCT uses three preset set point values, T1, T2 and T3. When using the Domino HSYCO I/O Server it is mandatory that T1 < T2 < T3. If the set points are not in order, you will not be able to control the DFCT using the (temp) GUI objects.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.mode | winter | R | winter mode |
| summer | R | summer mode | |
| i<address>.fan | min | R | min fan speed |
| med | R | medium fan speed | |
| max | R | max fan speed | |
| off | R | fan off | |
| i<address>.fan.mode | man | R | manual fan mode |
| auto | R | auto fan mode | |
| i<address>.setpoint | 1 | R | setpoint 1 |
| 2 | R | setpoint 2 | |
| 3 | R | setpoint 3 | |
| off | R | off | |
| man | R | manual setpoint | |
| i<address>.setpoint.mode | man | R | manual setpoint mode |
| auto | R | auto setpoint mode | |
| i<address>.temp | <temp> | R | temperature value (in C/10) |
| fault | R | temperature sensor fault | |
| i<address>.status | off | R | off |
| cooling | R | cooling status mode | |
| heating | R | heating status mode | |
| o<address>.mode | winter | RW | winter mode |
| summer | RW | summer mode | |
| o<address>.fan | min | RW | min fan speed |
| med | RW | medium fan speed | |
| max | RW | max fan speed | |
| off | RW | fan off | |
| o<address>.fan.mode | man | RW | manual fan mode |
| auto | RW | auto fan mode | |
| o<address>.setpoint | 1 | RW | setpoint 1 |
| 2 | RW | setpoint 2 | |
| 3 | RW | setpoint 3 | |
| 0 | RW | setpoint off | |
| man | RW | manual setpoint | |
| o<address>.setpoint.temp.1 | <temp> | RW | temperature setpoint 1 value (in C/10) |
| o<address>.setpoint.temp.2 | <temp> | RW | temperature setpoint 2 value (in C/10) |
| o<address>.setpoint.temp.3 | <temp> | RW | temperature setpoint 3 value (in C/10) |
| o<address>.setpoint.temp.man | <temp> | RW | temperature manual setpoint value (in C/10) |
| o<address>.program.summer o<address>.program.winter |
refresh | RW | forces to daily summer/winter program for all days of the week |
| o<address>.program.summer.<day> o<address>.program.winter.<day> |
refresh | RW | forces to daily summer/winter program for the reported day (mon:1, sun:7) |
| <s0>...<s47> | RW | 48 character represents the daily setpoint program divided in time slots of 30 minutes |
DFTZ
The DFTZ is an input/output temperature sensor module.
It uses 3 consecutive input addresses and 4 consecutive output addresses in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.mode | winter | R | winter mode |
| summer | R | summer mode | |
| i<address>.setpoint | comfort | R | comfort setpoint |
| eco | R | eco setpoint | |
| off | R | off | |
| i<address>.temp | <temp> | R | temperature value (in C/10) |
| fault | R | temperature sensor fault | |
| i<address>.status | off | R | off |
| cooling | R | cooling status mode | |
| heating | R | heating status mode | |
| o<address>.mode | winter | RW | winter mode |
| summer | RW | summer mode | |
| o<address>.setpoint | comfort | RW | comfort setpoint |
| eco | RW | eco setpoint | |
| 0 | RW | off | |
| o<address>.setpoint.temp.comfort | <temp> | RW | comfort setpoint value (in C/10) |
| o<address>.setpoint.temp.eco | <temp> | RW | eco setpoint value (in C/10) |
| o<address>.setpoint.temp.limit | <temp> | RW | summer/winter setpoint temperature limit (in C/10) |
DFRHT
The DFRHT is a temperature and humidity sensor.
It uses four consecutive input addresses and two consecutive output addresses in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.humidity | 0...100 | R | relative percent umidity |
| i<address>.temp | <temp> | R | temperature value |
| i<address>.dewpoint | <temp> | R | dew point value |
| i<address>.dewpoint.limit.1 | 0 | R | dew point is lower than limit 1 |
| 1 | R | dew point is higher than limit 1 | |
| <temp> | RW | dew point limit 1 | |
| off | RW | limit 1 not set | |
| i<address>.dewpoint.limit.2 | 0 | R | dew point is lower than limit 2 |
| 1 | R | dew point is higher than limit 2 | |
| <temp> | RW | dew point limit 2 | |
| off | RW | limit 2 not set |
DFMETEO
The DFMETEO is the weather sensor module.
It uses four consecutive input addresses and three consecutive output addresses in the DOMINO bus.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.temp | <temp> | RW | temperature value (in C/10) |
| off | RW | limit not set | |
| i<address>.lux | <lux*10> | R | lux level according to the DFLUX range |
| <lux> | RW | lux limit | |
| 0 | RW | limit not set | |
| i<address>.wind | 1 m/s /10 | R | wind value |
| m/s | RW | wind limit | |
| 0 | RW | limit not set | |
| i<address>.rain | 0 | R | no rain |
| 1 | R | rain | |
| i<address>.night | 0 | R | day |
| 1 | R | night | |
| i<address>.temp.limit | 0 | R | measured temp is less than limit |
| 1 | R | measured temp is greater than limit | |
| i<address>.lux.limit | 0 | R | measured lux is less than limit |
| 1 | R | measured lux is greater than limit | |
| i<address>.wind.limit | 0 | R | measured wind is less than limit |
| 1 | R | measured wind is greater than limit | |
| i<address>.light.south | 0 | R | light is not coming from south |
| 1 | R | light is coming from south | |
| i<address>.light.west | 0 | R | light is not coming from west |
| 1 | R | light is coming from west | |
| i<address>.light.east | 0 | R | light is not coming from east |
| 1 | R | light is coming from east | |
| i<address>.fault | 0 | R | sensor not fault |
| 1 | R | sensor fault |
DFCC
The DFCC is an energy meter and load manager module.
In the following table, <N> is the sequential index (1 to 3) of the DFCC module.
| ID | Value | R/W | Description |
|---|---|---|---|
| energy.<n>.power.real | 0...65535 | R | real power (Watt) |
| energy.<n>.power.reactive | -32768...+32767 | R | reactive power (var) |
| energy.<n>.power.apparent | -32768...+32767 | R | apparent power (VA) |
| energy.<n>.power.realavg | 0...65535 | R | average real power (Watt) |
| energy.<n>.power.reactiveavg | -32768...+32767 | R | average reactive power (var) |
| energy.<n>.cos | -1000...+1000 | R | cos(φ) * 1000 |
| energy.<n>.load.1 | 0 | R | load 1 disabled |
| 1 | R | load 1 enabled | |
| energy.<n>.load.2 | 0 | R | load 2 disabled |
| 1 | R | load 2 enabled | |
| energy.<n>.load.3 | 0 | R | load 3 disabled |
| 1 | R | load 3 enabled | |
| energy.<n>.load.4 | 0 | R | load 4 disabled |
| 1 | R | load 4 enabled | |
| energy.<n>.load.5 | 0 | R | load 5 disabled |
| 1 | R | load 5 enabled | |
| energy.<n>.load.6 | 0 | R | load 6 disabled |
| 1 | R | load 6 enabled | |
| energy.<n>.load.7 | 0 | R | load 7 disabled |
| 1 | R | load 7 enabled | |
| energy.<n>.load.8 | 0 | R | load 8 disabled |
| 1 | R | load 8 enabled |
DFANA
Network analyzer module for Domino bus.
Uses up to 20 consecutive input addresses and, if enabled, 1 output address equal to the base input address.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.v12 | [V] | R | chained voltage phase 1-2 |
| i<address>.v23 | [V] | R | chained voltage phase 2-3 |
| i<address>.v31 | [V] | R | chained voltage phase 3-1 |
| i<address>.vtm | [V] | R | average chained voltage |
| i<address>.i1 | [A] | R | current phase 1 |
| i<address>.i2 | [A] | R | current phase 2 |
| i<address>.i3 | [A] | R | current phase 3 |
| i<address>.itm | [A] | R | average current |
| i<address>.ptot | [W] | R | total active power |
| i<address>.ptotk | [kW] | R | total active power |
| i<address>.qtot | [W] | R | total reactive power |
| i<address>.qtotk | [kW] | R | total reactive power |
| i<address>.pf | [pf] | R | total power factor |
| i<address>.frequency | [Hz] | R | frequency |
| i<address>.v1n | [V] | R | voltage phase 1 |
| i<address>.v2n | [V] | R | voltage phase 2 |
| i<address>.v3n | [V] | R | voltage phase 3 |
| i<address>.p1 | [W] | R | active power phase 1 |
| i<address>.p1k | [kW] | R | active power phase 1 |
| i<address>.p2 | [W] | R | active power phase 2 |
| i<address>.p2k | [kW] | R | active power phase 2 |
| i<address>.p3 | [W] | R | active power phase 3 |
| i<address>.p3k | [kW] | R | active power phase 3 |
DFCC2
Energy meter and load manager module for Domino bus.
Uses 10 consecutive input addresses and, if enabled, 1 output address equal to the base input address.
| ID | Value | R/W | Description |
|---|---|---|---|
| i<address>.v | [V / 10] | R | measured RMS voltage |
| i<address>.i | [A / 10] | R | measured RMS current |
| i<address>.p | [W] | R | active power (signed) |
| i<address>.q | [VAR] | R | reactive power (signed) |
| i<address>.s | [VA] | R | apparent power |
| i<address>.pf | [x 1000] | R | power factor (signed: positive for inductive loads, negative for reactive loads) |
| i<address>.ae | [Wh] | R | total active energy |
| i<address>.1 | 0 | R | load 1 disabled |
| 1 | R | load 1 enabled | |
| i<address>.2 | 0 | R | load 2 disabled |
| 1 | R | load 2 enabled | |
| i<address>.3 | 0 | R | load 3 disabled |
| 1 | R | load 3 enabled | |
| i<address>.4 | 0 | R | load 4 disabled |
| 1 | R | load 4 enabled | |
| i<address>.5 | 0 | R | load 5 disabled |
| 1 | R | load 5 enabled | |
| i<address>.6 | 0 | R | load 6 disabled |
| 1 | R | load 6 enabled | |
| i<address>.7 | 0 | R | load 7 disabled |
| 1 | R | load 7 enabled | |
| i<address>.8 | 0 | R | load 8 disabled |
| 1 | R | load 8 enabled | |
| o<address>.1 | 0 | RW | load 1 control enabled |
| 1 | RW | load 1 always enabled | |
| o<address>.2 | 0 | RW | load 2 control enabled |
| 1 | RW | load 2 always enabled | |
| o<address>.3 | 0 | RW | load 3 control enabled |
| 1 | RW | load 3 always enabled | |
| o<address>.4 | 0 | RW | load 4 control enabled |
| 1 | RW | load 4 always enabled | |
| o<address>.5 | 0 | RW | load 5 control enabled |
| 1 | RW | load 5 always enabled | |
| o<address>.6 | 0 | RW | load 6 control enabled |
| 1 | RW | load 6 always enabled | |
| o<address>.7 | 0 | RW | load 7 control enabled |
| 1 | RW | load 7 always enabled | |
| o<address>.8 | 0 | RW | load 8 control enabled |
| 1 | RW | load 8 always enabled | |
| o<address>.buzzer | 0 | RW | buzzer disabled |
| 1 | RW | buzzer enabled | |
| o<address>.ae | reset | W | reset total active energy counter |
User Interface
All DOMINO devices data points that have been defined in the systemtopo.txt database are automatically listed in the Project Editor.
Adding a button to control a device output point requires just a few clicks and no additional EVENTS logic.
Besides the direct association of control buttons and data points, the DOMINO driver also automatically updates graphical objects that represent values or states of complex devices, like the DFCT temperature control unit. It will also automatically intercept buttons to manually set operation modes and temperature set-points.
DFDMX
You can define a standard HSYCO DMX server for each DFDMX module, then use the dmx and dmxrgb objects to control channels 1-64 of the DMX bus connected to the DFDMX module.
For example:
dmxServers = dmx dmxServersId.dmx = domino.o8
Note that, instead of defining the dmxServersIP parameter, the dmxServersId is used to associate the DMX server with the id of the DFDMX module.
DFCC
Setting the powerdisplay option to true in Settings enables the automatic display in the GUI of the total real power measured by all DFCC modules connected to this DFCP.
Note that, if you have more than one DFCP gateway, you should enable this option for one gateway only.
UISET Actions
You can use any object that accepts a text attribute, usually text but also marquee and others, to automatically display the average real power measured by all DFCC modules connected to the DOMINO bus. These objects are updated even when the powerdisplay option is false.
| ID | Attribute | Set to | |
|---|---|---|---|
| energy.<n>.power | value | real power, followed by “ W”. <n> is the sequential index (1 to 3) of the DFCC module. | |
DFCT
You can use the temp and tempmini objects to control DFCT devices.
UISET Actions
You can use any object that accepts a text attribute, usually text but also marquee and others, like images, to automatically display the relevant information of all DFCT modules.
| ID | Attribute | Set to | Description |
|---|---|---|---|
| <address>.mode | value | SUMMER | summer mode (cooling) |
| WINTER | winter mode (heating) | ||
| <address>.mode.label.summer | visible | true | the DFCT is in summer mode |
| <address>.mode.label.winter | visible | true | the DFCT is in winter mode |
| <address>.status | value | OFF | zone off |
| ON | zone on | ||
| <address>.status.label.cooling | visible | true | if the zone is cooling |
| <address>.status.label.heating | visible | true | if the zone is heating |
| <address>.fan | value | OFF | fan off |
| MIN | minimum fan speed | ||
| MED | medium fan speed | ||
| MAX | maximum fan speed | ||
| <address>.fan.label.min | visible | true | the fan speed is min |
| <address>.fan.label.med | visible | true | the fan speed is med |
| <address>.fan.label.max | visible | true | the fan speed is max |
| <address>.fan.mode | value | MAN | manual fan mode |
| AUTO | auto fan mode | ||
| <address>.setpoint | value | 1,2,3 | active setpoint |
| MAN | manual setpoint | ||
| OFF | zone off | ||
| <address>.setpoint.label.1 | visible | true | setpoint 1 is active |
| <address>.setpoint.label.2 | visible | true | setpoint 2 is active |
| <address>.setpoint.label.3 | visible | true | setpoint 3 is active |
| <address>.setpoint.label.man | visible | true | manual setpoint is active |
| <address>.setpoint.label.off | visible | true | zone is off |
| <address>.setpoint.mode | value | MAN | manual setpoint mode |
| AUTO | auto setpoint mode | ||
| <address>.setpoint.temp | value | <value> | the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| <address>.setpoint.temp.1 | value | <value> | the active setpoint 1 temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| <address>.setpoint.temp.2 | value | <value> | the active setpoint 2 temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| <address>.setpoint.temp.3 | value | <value> | the active setpoint 3 temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| <address>.setpoint.temp.man | value | <value> | the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| <address>.temp | value | <temp> | the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| FAULT | fault/error condition |
USER Commands
There are several predefined buttons. Use any ordinary user object, setting the name and param fields based on this table.
| Name | Param | Action |
|---|---|---|
| <address> | mode | cycle through summer and winter mode |
| mode.summer | set summer mode (cooling) | |
| mode.winter | set winter mode (heating) | |
| fan | cycle through fan speeds and modes (auto, off, man/min, man/med, man/max, auto) | |
| <address>.setpoint | mode | cycle through the manual, automatic and off operation modes |
| mode.man | set manual operation mode | |
| mode.auto | set automatic operation mode | |
| mode.off | off mode | |
| temp.1.up | increase setpoint 1 temperature in 0.5C steps | |
| temp.1.down | decrease setpoint 1 temperature in 0.5C steps | |
| temp.1.<t> | setpoint 1 set to temperature t, in C/10 (0 <= t <= 355) | |
| temp.2.up | increase setpoint 2 temperature in 0.5C steps | |
| temp.2.down | decrease setpoint 2 temperature in 0.5C steps | |
| temp.2.<t> | setpoint 2 set to temperature t, in C/10 (0 <= t <= 355) | |
| temp.3.up | increase setpoint 3 temperature in 0.5C steps | |
| temp.3.down | decrease setpoint 3 temperature in 0.5C steps | |
| temp.3.<t> | setpoint 3 set to temperature t, in C/10 (0 <= t <= 355) | |
| temp.man.up | increase manual setpoint temperature in 0.5C steps | |
| temp.man.down | decrease manual setpoint temperature in 0.5C steps | |
| temp.man.<t> | manual setpoint set to temperature t, in C/10 (0 <= t <= 355) | |
| <address>.fan | mode | cycle through the manual and automatic fan speed modes |
| mode.man | set manual fan speed mode | |
| mode.auto | set automatic fan speed mode | |
| up | increase fan speed | |
| down | decrease fan speed | |
| min | set min fan speed | |
| med | set med fan speed | |
| max | set max fan speed | |
| off | fan off |
DFTZ
You can use the tempmini object to control DFTZ devices.
You could also use the larger temp object, but some of its controls are not used with the DFTZ module.
UISET Actions
You can use any object that accepts a text attribute, usually text but also marquee and others, like images, to automatically display the relevant information of all DFTZ modules.
| ID | Attribute | Set to | Description |
|---|---|---|---|
| <address>.mode | value | SUMMER | summer mode (cooling) |
| WINTER | winter mode (heating) | ||
| <address>.mode.label.summer | visible | true | the DFTZ is in summer mode |
| <address>.mode.label.winter | visible | true | the DFTZ is in winter mode |
| <address>.status | value | OFF | zone off |
| ON | zone on | ||
| <address>.status.label.off | visible | true | if the zone is not cooling or heating |
| <address>.status.label.cooling | visible | true | if the zone is cooling |
| <address>.status.label.heating | visible | true | if the zone is heating |
| <address>.setpoint | value | COM | comfort setpoint |
| MAN | manual setpoint | ||
| OFF | zone off | ||
| <address>.setpoint.label.1 | visible | true | comfort setpoint is active |
| <address>.setpoint.label.2 | visible | true | eco setpoint is active |
| <address>.setpoint.label.off | visible | true | zone is off |
| <address>.setpoint.temp | value | <temp> | the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| <address>.setpoint.temp.1 | value | <temp> | the comfort setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| <address>.setpoint.temp.2 | value | <temp> | the eco setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| <address>.setpoint.temp.man | value | <temp> | the summer or winter setpoint temperature limit, in Celsius degrees with one decimal digit, followed by " °C" |
| <address>.temp | value | <temp> | the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C" |
| FAULT | fault/error condition |
USER Commands
There are several predefined buttons. Use any ordinary user object, setting the name and param fields based on this table.
| Name | Param | Action |
|---|---|---|
| <address> | mode | cycle through summer and winter mode |
| mode.summer | set summer mode (cooling) | |
| mode.winter | set winter mode (heating) | |
| <address>.setpoint | mode | cycle through the manual, automatic and off operation modes |
| mode.comfort | set comfort operation mode | |
| mode.eco | set eco operation mode | |
| mode.off | off mode | |
| temp.up | increase the active setpoint temperature in 0.5C steps | |
| temp.down | ddecrease the active setpoint temperature in 0.5C steps | |
| temp.<t> | active setpoint set to temperature t, in C/10 (0 <= t <= 355) | |
| temp.1.up | increase comfort setpoint temperature in 0.5C steps | |
| temp.1.down | decrease comfort setpoint temperature in 0.5C steps | |
| temp.1.<t> | comfort setpoint set to temperature t, in C/10 (0 <= t <= 355) | |
| temp.2.up | increase eco setpoint temperature in 0.5C steps | |
| temp.2.down | decrease eco setpoint temperature in 0.5C steps | |
| temp.2.<t> | eco setpoint set to temperature t, in C/10 (0 <= t <= 355) | |
| temp.man.up | increase setpoint temperature limit in 0.5C steps | |
| temp.man.down | decrease setpoint temperature limit in 0.5C steps | |
| temp.man.<t> | set-point temperature limit set to temperature t, in C/10 (0 <= t <= 355) |
Release Notes
3.5.0
- added support for DFCP4
- fixed a bug that could cause erroneous readings of DFCC's 2'complements values
3.4.0
- improved communication error logging
- improved support of tools remote access
- events generated during startup if startupevents=true are now executed sequentially
- DFCC2 module support
- DFH module support
- fix: DFTZ user commands mode.comfort, mode.eco, mode.off not working
3.2.2
bug fixes:
- the toolspassword optional parameter was incorrectly converted to lower case
- fixed a bug that prevented reading the input pins of DF4RP/I and DF4RPR/I
3.2.1
- support for DFTZ
3.2.0
- support for DFIGLASS
- new "detectevents" option, generates forced events when a device is detected at start-up
- support for the toolspassword option, to allow DFCP-IDE and other tools secure remote access to the DFCP via HSYCO
- new clock datapoint to read the DFCP internal clock and set it to HSYCO's time
3.1.2
bug fixes:
- the (temp) object's DFCT configuration function was broken in HSYCO 3.1.0
- energy metering data point were not updated
3.1.1
- added support for DF4RP/I and DFDT
3.1.0
- added support for DFANA energy meter module
3.0.3
- optimized performance of DFCP’s registers status polling
3.0.1
- you can now limit the number of virtual points and registers read and written by HSYCO, and have access to all of the 1024 registers; defaults are unchanged
- added support for DF8IL, DFDI2B and DFRHT modules
3.0.0
- update DFDMX state at startup
- support for failover mode
1.2.0
- fixed bugs related to the DFDM and DFDI modules
- integration with the DMX server engine
- enhanced GUI support for DFCC and DFCT
1.1.0
- automatic generation of the device map in systemtopo.txt
- Web Editor support
- support for DFCP’s virtual data points and registers
- support for serial connection to the DFCP through the serial ports of HWg PortBox and ERxx network devices
1.0.0
- initial release
HSYCO and Home Systems Consulting are registered trademarks of Home Systems Consulting SpA. Java and JavaScript are registered trademarks of Oracle and/or its affiliates. DOMINO and DUEMMEGI are registered trademarks of DUEMMEGI SRL. Other products or company names can be trademarks or registered trademarks of other companies and are used for demonstrative purposes only, with no violation intent.
