Skip to main content

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.

note

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.

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 rate9600, 38400, 57600 or 115200 bps (according to the DFCP serial port setting)
Data bits8
Stop bit1
Paritynone
Flow controlnone
note

A speed of 115200 bps is recommended to achieve good performance, particularly when the number of devices connected to the bus is large.

High Availability

  • Shutdown when inactive: defaults to false.

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

IDDefaultValuesDescription
startupeventsfalsetruegenerate IO events also during the driver’s start-up phase
falsestart generating events only after HSYCO is aligned with the current status of the system
inputdiscoveryfalsetrueauto-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
falseauto-detect for input devices is disabled
outputdiscoverytruetrueauto-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
falseauto-detect for output devices is disabled
virtualdiscoveryfalsetrueauto-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
falseauto-detect for devices’ virtual data points is disabled
virtualpointsfalse1...2033enables 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
trueenables polling for all the 2032 virtual points of the DFCP
falsepolling of the DFCP virtual data points is disabled
registersfalse1...1024enables polling for registers R0-Rn of the DFCP. Enable this option only if you need to generate I/O events based on these registers
trueenables polling for registers R0-R127 of the DFCP
falsepolling of the DFCP registers is disabled
powerdisplayfalsetrueenables 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
falsepower display disabled for this DFCP
powersensivity50≥ 0measured power changes are reported only if the difference from last reading is equal or greater than the power sensivity option, in Watts
powerinterval1≥ 0power polling interval for the DFCC meter, in seconds
detecteventsfalsetruegenerate forced events when a device is detected at start-up
falsedo not generate events when a device is detected at start-up
toolspasswordstringset 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
languageenglishen it frlanguage for all messages from the DOMINO system: English, Italian or French

Initialization and Connection Events

Event nameValueDescription
connectiononlineconnection established to the DFCP module
offlineHSYCO can’t connect to the DFCP module
detected.input.<n>.<s>model namean input device of the type passed as value has been detected at address <n>, using <s> addresses
detected.output.<n>.<s>model namean output device of the type passed as value has been detected at address <n>, using <s> addresses

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 Data Points

The DFCP implements 2032 virtual points for binary (on/off) data and 1024 registers and counters for positive scalar values (0-65535). The DFH doesn't support virtual points or registers.

All virtual points, registers and counters can optionally generate I/O events. You can also write to the virtual data points, registers or counters using the IO action in EVENTS or ioSet() method in Java.

You cannot directly control the DFCP virtual data points, registers or counters 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.

To enable polling of the current state of the DFCP’s counters, enable the counters options in hsyco.ini.

If you only have to write to virtual points or registers, enabling polling is not strictly required.

IDValueR/WDescription
busfault0Rno bus fault detected
1Rbus fault detected
modulefault0Rno modules fault detected
1Rmodules fault detected
v0.<n>0RWvirtual data point <n> off (<n>: 1-2032)
1RWvirtual data point <n> on (<n>: 1-2032)
r0.<n><x>RWregister <n> (<n>: 0-1023) set to value <x> (<x>: 0-65535)
c0.<n><x>RWcounter <n> (<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.

IDValueR/WDescription
clockyyyy-mm-dd hh:mm:ssRthe DFCP clock current time
readWread the DFCP clock, and the delta with HSYCO’s time
syncWset the DFCP clock to HSYCO’s current time
clock.deltainteger numberRthe delta time in seconds between the DFCP and HSYCO clocks. A positive number means that the DFCP clock is ahead of HSYCO

DFH redundant configuration for High Availability applications

When HSYCO is embedded in a DFH interface, high availability support can be configured to allow two DFH to be connected to the same Domino bus. In normal operations, the master unit will be active on the bus, while the slave unit will automatically block bus polling, to avoid traffic conflicts with the master unit.

note

DFH high availability support requires DFH firmware version 3.3 or above.

If the slave HSYCO becomes active, because it automatically detects a master's failure, the Domino I/O server will exit its idle state, and the slave DFH interface will resume polling the bus. The time required by the slave to take over the active role and become the bus master depends on the haTimeoutSeconds configuration parameter; its default is 4 seconds. A few seconds of bus polling overlapping are also normal when the master becomes active again.

In a typical configuration, the following high availability parameters should be set like:

haClientSessionsFailover = true
haDisableCommandEvents = true
haDisableFilesSync = false
haTimeoutSeconds = 4

Also, the ioServersShutdownInactive parameter of the Domino I/O server, on both master and slave, should be false (or default).

Without additional configuration, this setup will correctly address a total failure of the master DFH unit, but not other fault conditions, like a bus fault on the master unit, or LAN fault on the master or slave DFH.

If a bus fault occurs on the master DFH, HSYCO would still be active and the slave remains idle, as it would still sense the master's presence over the LAN. Also, if the master becomes disconnected from the LAN, it would still remain active, but the slave would also become active, causing polling conflicts on the Domino bus. To address these specific failure modes, add the following lines, or something similar, to the EVENTS file:

$HAMASTER$ = 1 and (IO domino.busfault = "1" or IO system.internet.connection = "offline") : { haActive(false); }
$HAMASTER$ = 1 and (IO domino.busfault = "0" and IO system.internet.connection = "online") : { haActive(true); }

The first rule forces the master to relinquish its active state in case of bus failure or when the internet connection is lost. You should probably replace the internet connection test with an equivalent command that tests local services on your LAN.

The second rule reacquires the master's active state when both the Domino bus and the LAN connections are up.

Another fault scenario that should be considered is the loss of LAN access from the slave DFH. In this case the master would remain active, but the slave HSYCO would also become active, not sensing the master. This should again be prevented, to avoid polling conflicts, with the following rules in EVENTS:

$HAMASTER$ = 0 and IO system.internet.connection = "offline" : { ioServersStop("domino"); }
$HAMASTER$ = 0 and IO system.internet.connection = "online" : { ioServersRestart("domino"); }

These rules will stop the Domino I/O server when the slave LAN is down, effectively blocking the slave DFH polling, and restart it when up.

note

Note that there could be other specific fault scenarios to be considered. The example presented here is only one of several possible ways to implement a DFH-based high availability configuration, and may not be adequate to handle all possible fault scenarios in an actual installation.

DOMINO Modules Events and Control

Each DOMINO module has its own set of read-only or read-write data points, mapping the specific set of features.

All modules also have a read-only "fault" data point, set to 1 if the DFCP has detected a module fault condition, or 0 if the module is working normally.

IDValueR/WDescription
i<address>.fault0Rinput module working normally
1Rinput module fault detected
o<address>.fault0Routput module working normally
1Routput module fault detected
Module CodeDescription
DF4I4 digital inputs
DFCK3clock
DF8I2x4 digital inputs
DF2R2 outputs (relay)
DF4R, DF4RP4 outputs (power relay)
DF4RP/I4 generic inputs ON-OFF + 4 outputs
DF4RI / DF4RIRmultifunction module with 4 digital inputs and 4 outputs (power relay)
DF8RITmultifunction module with 8 digital inputs, 8 outputs (power relay), 1 temperature sensor/controller
DFDI, DFDI2, DFDI2B, DFDM, DFDT1 output (dimmer)
DFDMXDMX interface
DFDALIDALI interface
DFDALI64DALI interface
DFDV1 output (1-10V - ballast) + 1 output (power relay)
DF4DV4 outputs (1-10V - ballast)
DFPID1 output (0-10V) + 2 outputs (power relay)
DFTP2 outputs (shutters)
DFTP/I2 outputs (shutters) + 4 digital inputs
DFTR2 outputs (shutters) + 1 output (relay)
DF4IL4 digital inputs + 4 outputs (LED)
DF8IL8 digital inputs + 8 outputs (LED)
DFIGLASS6 button touch keypad with optional temperature sensor
AURORA6 button touch keypad with optional temperature and humidity sensor
DFAI2 analog inputs
DFAM22 analog inputs
DFLS / DFLS-Pambient light sensor and presence detector
DFLUX, DFSUNlight sensor
DFCT/DFTZ/DFTZ2temperature sensor
DFMB-CModbus control interface for HVAC units
DFRHTtemperature and humidity sensor
DFMETEOweather module
DFANAelectric energy network analyser
DFANA-Melectric energy network analyser
DFANA-M/CCelectric energy meter and load manager
DFCCelectric energy meter and load manager
DFCC2electric energy meter and load manager
DFTA / DFTEtemperature sensor module

DF4I

The DF4I is an input module with 4 digital inputs.

It uses one address in the DOMINO bus.

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
i<address>.40Rinput pin 4 off
1Rinput 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.

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
i<address>.40Rinput pin 4 off
1Rinput pin 4 on
i<address>.50Rinput pin 5 off
1Rinput pin 5 on
i<address>.60Rinput pin 6 off
1Rinput pin 6 on
i<address>.70Rinput pin 7 off
1Rinput pin 7 on
i<address>.80Rinput pin 8 off
1Rinput pin 8 on
i<address>.90Rinput pin 9 off
1Rinput pin 9 on
i<address>.100Rinput pin 10 off
1Rinput pin 10 on
i<address>.110Rinput pin 11 off
1Rinput pin 11 on
i<address>.120Rinput pin 12 off
1Rinput pin 12 on
i<address>.130Rinput pin 13 off
1Rinput pin 13 on
i<address>.140Rinput pin 14 off
1Rinput pin 14 on
i<address>.150Rinput pin 15 off
1Rinput pin 15 on

DF8I

The DF8I is an input module with 2x4 digital inputs.

It uses two consecutive addresses in the DOMINO bus.

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
i<address>.40Rinput pin 4 off
1Rinput pin 4 on
i<address+1>.10Rinput pin 5 off
1Rinput pin 5 on
i<address+1>.20Rinput pin 6 off
1Rinput pin 6 on
i<address+1>.30Rinput pin 7 off
1Rinput pin 7 on
i<address+1>.40Rinput pin 8 off
1Rinput pin 8 on

DF2R

The DF2R is an output module with 2 relay outputs.

It uses one address in the DOMINO bus.

IDValueR/WDescription
o<address>.10RWoutput pin 1 off
1RWoutput pin 1 on
o<address>.20RWoutput pin 2 off
1RWoutput 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.

IDValueR/WDescription
o<address>.10RWoutput pin 1 off
1RWoutput pin 1 on
o<address>.20RWoutput pin 2 off
1RWoutput pin 2 on
o<address>.30RWoutput pin 3 off
1RWoutput pin 3 on
o<address>.40RWoutput pin 4 off
1RWoutput 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.

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
o<address>.10RWoutput pin 1 off
1RWoutput pin 1 on
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
o<address>.20RWoutput pin 2 off
1RWoutput pin 2 on
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
o<address>.30RWoutput pin 3 off
1RWoutput pin 3 on
i<address>.40Rinput pin 4 off
1Rinput pin 4 on
o<address>.40RWoutput pin 4 off
1RWoutput pin 4 on

DF8RIT

The DF8RIT is a multifunction module with 8 digital inputs, 8 outputs (power relay) and 1 temperature sensor/controller.

This module uses 1 to 7 input addresses and 1 to 10 output addresses, based on its configuration.

The module's configuration is automatically detected by HSYCO when connected to the DFCP.

Digital inputs section

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
i<address>.40Rinput pin 4 off
1Rinput pin 4 on
i<address>.50Rinput pin 5 off
1Rinput pin 5 on
i<address>.60Rinput pin 6 off
1Rinput pin 6 on
i<address>.70Rinput pin 7 off
1Rinput pin 7 on
i<address>.80Rinput pin 8 off
1Rinput pin 8 on

Relay outputs section 1-2

If automation 1 is not enabled (base address + 1 not used):

IDValueR/WDescription
o<address>.10RWoutput pin 1 off
1RWoutput pin 1 on
o<address>.20RWoutput pin 2 off
1RWoutput pin 2 on

If automation 1 is enabled (base address + 1 is used):

IDValueR/WDescription
o<address>.1upRWshutter up command
downRWshutter down command
stopRWshutter stop command
unknownRunknown state
offupRWshutter off, up position
offdownRWshutter off, down position
o<address + 1>0 ... 100%RWpercent position

Relay outputs section 3-4

If automation 2 is not enabled (base address + 2 not used):

IDValueR/WDescription
o<address>.30RWoutput pin 3 off
1RWoutput pin 3 on
o<address>.40RWoutput pin 4 off
1RWoutput pin 4 on

If automation 2 is enabled (base address + 2 is used):

IDValueR/WDescription
o<address>.3upRWshutter up command
downRWshutter down command
stopRWshutter stop command
unknownRunknown state
offupRWshutter off, up position
offdownRWshutter off, down position
o<address + 2>0 ... 100%RWpercent position

Relay outputs section 5-6

If automation 3 is not enabled (base address + 3 not used):

IDValueR/WDescription
o<address>.50RWoutput pin 5 off
1RWoutput pin 5 on
o<address>.60RWoutput pin 6 off
1RWoutput pin 6 on

If automation 3 is enabled (base address + 3 is used):

IDValueR/WDescription
o<address>.5upRWshutter up command
downRWshutter down command
stopRWshutter stop command
unknownRunknown state
offupRWshutter off, up position
offdownRWshutter off, down position
o<address + 3>0 ... 100%RWpercent position

Relay outputs section 7-8

If automation 4 is not enabled (base address + 4 not used):

IDValueR/WDescription
o<address>.70RWoutput pin 7 off
1RWoutput pin 7 on
o<address>.80RWoutput pin 8 off
1RWoutput pin 8 on

If automation 4 is enabled (base address + 4 is used):

IDValueR/WDescription
o<address>.7upRWshutter up command
downRWshutter down command
stopRWshutter stop command
unknownRunknown state
offupRWshutter off, up position
offdownRWshutter off, down position
o<address + 4>0 ... 100%RWpercent position

Temperature control section

If temperature control is enabled:

note

The D8RIT 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 D8RIT using the (temp) GUI objects.

IDValueR/WDescription
i<address + 5>.modewinterRwinter mode
summerRsummer mode
i<address + 5>.fanminRmin fan speed
medRmedium fan speed
maxRmax fan speed
offRfan off
i<address + 5>.fan.modemanRmanual fan mode
autoRauto fan mode
i<address + 5>.setpoint1Rsetpoint 1
2Rsetpoint 2
3Rsetpoint 3
offRoff
manRmanual setpoint
i<address + 5>.setpoint.modemanRmanual setpoint mode
autoRauto setpoint mode
i<address + 5>.temp<temp>Rtemperature value (in C/10)
faultRtemperature sensor fault
i<address + 5>.statusoffRoff
coolingRcooling status mode
heatingRheating status mode
o<address + 5>.modewinterRWwinter mode
summerRWsummer mode
o<address + 5>.fanminRWmin fan speed
medRWmedium fan speed
maxRWmax fan speed
offRWfan off
o<address + 5>.fan.modemanRWmanual fan mode
autoRWauto fan mode
o<address + 5>.setpoint1RWsetpoint 1
2RWsetpoint 2
3RWsetpoint 3
0RWsetpoint off
manRWmanual setpoint
o<address + 5>.setpoint.temp.1<temp>RWtemperature setpoint 1 value (in C/10)
o<address + 5>.setpoint.temp.2<temp>RWtemperature setpoint 2 value (in C/10)
o<address + 5>.setpoint.temp.3<temp>RWtemperature setpoint 3 value (in C/10)
o<address + 5>.setpoint.temp.man<temp>RWtemperature manual setpoint value (in C/10)
o<address + 5>.program.summer
o<address + 5>.program.winter
refreshRWreads the daily summer/winter programs for all days of the week from the DF8RIT module. This command requires a considerable amount of bus time and blocks all other commands until completed
o<address + 5>.program.summer.<day>
o<address + 5>.program.winter.<day>
refreshRWreads the daily summer/winter programs for a single day (mon:1, sun:7) from the DF8RIT module. This command requires a considerable amount of bus time and blocks all other commands until completed
<s0>...<s47>RW48 character representation of the daily setpoint program in time slots of 30 minutes

DF4RI / DF4RIR

The DF4RI and DF4RIR are multifunction module with 4 digital inputs and 4 outputs (power relay).

This module uses 1 to 3 input and output addresses, based on its configuration.

The module's configuration is automatically detected by HSYCO when connected to the DFCP.

Digital inputs section

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
i<address>.40Rinput pin 4 off
1Rinput pin 4 on

Relay outputs section 1-2

If automation 1 is not enabled (base address + 1 not used):

IDValueR/WDescription
o<address>.10RWoutput pin 1 off
1RWoutput pin 1 on
o<address>.20RWoutput pin 2 off
1RWoutput pin 2 on

If automation 1 is enabled (base address + 1 is used):

IDValueR/WDescription
o<address>.1upRWshutter up command
downRWshutter down command
stopRWshutter stop command
unknownRunknown state
offupRWshutter off, up position
offdownRWshutter off, down position
o<address + 1>0 ... 100%RWpercent position

Relay outputs section 3-4

If automation 2 is not enabled (base address + 2 not used):

IDValueR/WDescription
o<address>.30RWoutput pin 3 off
1RWoutput pin 3 on
o<address>.40RWoutput pin 4 off
1RWoutput pin 4 on

If automation 2 is enabled (base address + 2 is used):

IDValueR/WDescription
o<address>.3upRWshutter up command
downRWshutter down command
stopRWshutter stop command
unknownRunknown state
offupRWshutter off, up position
offdownRWshutter off, down position
o<address + 2>0 ... 100%RWpercent position

Virtual outputs

IDValueR/WDescription
v<address>.50RWvirtual output 5 off
1RWvirtual output 5 on
v<address>.60RWvirtual output 6 off
1RWvirtual output 6 on
v<address>.70RWvirtual output 7 off
1RWvirtual output 7 on
v<address>.80RWvirtual output 8 off
1RWvirtual output 8 on

DFDM, DFDI, DFDI2, DFDI2B, DFDT, DFDIM

The DFDM, DFDI, DFDI2, DFDI2, DFDT and DFDIM are output modules with 1 dimmer output.

They use one address in the DOMINO bus.

IDValueR/WDescription
o<address>programRprogram mode
faultRdimmer fault
autoRauto mode
manRmanual mode
o<address>.1offRWdimmer off
1...100%RWpercent dimmer level
onRWdimmer on at last level
o<address>.rampsaveRWsaves the current ramp as default
1...30RWramp value in seconds (1 sec steps up to 10 and 2 sec steps up to 30)
40, 50, 60RWramp value in seconds (10 sec steps)
o<address>.setpoint0...1023RWsetpoint level
o<address>.hysteresis0...255RWtolerance level
o<address>.time0...255RWperiod (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.

DF4DV

The DF4DV, is an input/output module with 4 ballast (1-10V) outputs.

The DF4DV uses 4 consecutive addresses in the DOMINO bus.

IDValueR/WDescription
o<address>programRprogram mode
o<address>.1offRWdimmer off
1...100%RWpercent dimmer level
onRWdimmer on at last level
o<address>.rampsaveRWsaves the current ramp as default
1...30RWramp value in seconds (1 sec steps up to 10 and 2 sec steps up to 30)
40, 50, 60RWramp value in seconds (10 sec steps)

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.

IDValueR/WDescription
o<address>.<command>0...255RWcommands 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.

IDValueR/WDescription
o<address>refreshRWqueries the DFDALI module to update the current status of all DALI devices. This command requires a considerable amount of bus time and blocks all other commands until completed
o<address>offRWbroadcast off command
o<address>.all o<address>.0<level>RWbroadcast level command
o<address>.group.<DALI group>offRWgroup off command
<level>RWgroup level command
o<address>.<DALI address>offRWturn off a single device
<level>RWset a single device to a specific level
> 100RWspecial functions, having values between 101 and 255, as defined in the DFDALI manual
i<address>.pollingoffRpolling mode is disabled
onRpolling mode is enabled
i<address>.test0Rtest button not pressed
1Rtest button pressed
i<address>.dalinopowerRpower failure on the DALI bus
openRDALI bus is open
shortRDALI bus is shorted
onRDALI bus on
i<address>.1faultRDALI device 1 reporting a lamp failure
unknownRDALI 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.

DFDALI64

The DFDALI64 is a DALI interface module. Using the DFDALI64 you can control up to 64 DALI devices, and 16 groups, or a single broadcast address.

You can control individual devices, groups or broadcast commands to all devices.

It uses 2 to 18 input addresses (if enabled) and one output address in the DOMINO bus.

note

The Dominio I/O Server requires the DFDALI64 to be configured with at least the two base input addresses, where the first address reports the broadcast level and general status information, while the next one is the on/off status of groups 1-16. If the DFDALI64 is configured with additional input addresses associated to group levels, the status of these groups will be based on the values of the input addresses.

IDValueR/WDescription
o<address>refreshRWqueries the DFDALI64 module to update the current status of all DALI groups. This command requires a considerable amount of bus time and blocks all other commands until completed
o<address>offRWbroadcast off command
o<address>.all o<address>.0<level>RWbroadcast level command
o<address>.raw<high byte>.<low byte>Wsend a 2 byte raw command to the DFDALI64 module, in decimal format
<high byte>.<low byte>Rraw command successfully sent
errorRraw command error
o<address>.group.<DALI group>offRWgroup off command
<level>RWgroup level command
unknownRDALI group unknown state
o<address>.<DALI address>offRWturn off a single device
<level>RWset a single device to a specific level
> 100RWspecial functions, having values between 101 and 255, as defined in the DFDALI manual
i<address>.group.<DALI group>0RDALI group off
1RDALI group on
unknownRDALI group unknown state
i<address>.on0Rall DALI devices are off
1Rat least one DALI device is on
i<address>.pollingoffRpolling mode is disabled
onRpolling mode is enabled
i<address>.test0Rtest button not pressed
1Rtest button pressed
i<address>.dalinopowerRpower failure on the DALI bus
openRDALI bus is open
shortRDALI bus is shorted
onRDALI bus on
i<address>.1faultRDALI device 1 reporting a lamp failure
unknownRDALI device 1 status unknown
offRDALI device 1 off
<level>RDALI device 1 level

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.

IDValueR/WDescription
o<address>.1offRWdimmer off
1 ... 100%RWpercent dimmer level
onRWdimmer on at last level
o<address>.20RWoutput pin 1 off
1RWoutput 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.

DFPID

The DFPID is an output module with 1 output (0-10V) + 2 generic power relay outputs, with integrated PID control logic. It uses one input and output address in the DOMINO bus, and another optional input address, that is ignored by HSYCO.

IDValueR/WDescription
o<address>.10RWrelay output 1 off
1RWrelay output 1 on
o<address>.20RWrelay output 2 off
1RWrelay output 2 on
o<address>.pidoffRWPID output off
1..100%RWpercent PID level
onRWPID on at last level
o<address>.pid.disable0RWPID control logic enabled
1RWPID control logic disabled
o<address>.modesummerRsummer mode
winterRwinter mode
o<address>.to.fail0Routside temperature sensor ok
1Routside temperature sensor failed
o<address>.ts.fail0Rtemperature sensor ok
1Rtemperature sensor failed
o<address>.ts.alarm0Rtemperature sensor value ok
1Rtemperature sensor value out of range

The PID 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". When set to "on", it restores the value as it was before being turned off.


DFTP

The DFTP is an output module for 2 shutters.

It uses one output address in the DOMINO bus.

Position status and control is supported, based on the module's configuration, that is automatically detected by HSYCO when connected to the DFCP.

A slider object can be used to directly show and control the position, creating the object with both ID and Address set to the o<address>.1 or o<address>.2 data point name.

note

When "Real Time Position" is enabled in the module's configuration, "Include Motor Status" must also be checked.

IDValueR/WDescription
o<address>.1upRWshutter up command
downRWshutter down command
stopRWshutter stop command
0 ... 100%Wpercent position
unknownRunknown state
offupRshutter off, up position
offdownRshutter off, down position
o<address>.1.value0 ... 100%RWpercent position
o<address>.2upRWshutter up command
downRWshutter down command
stopRWshutter stop command
0 ... 100%Wpercent position
unknownRunknown state
offupRshutter off, up position
offdownRshutter off, down position
o<address>.2.value0 ... 100%RWpercent 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.

Position status and control is supported, based on the module's configuration, that is automatically detected by HSYCO when connected to the DFCP.

A slider object can be used to directly show and control the position, creating the object with both ID and Address set to the o<address>.1 or o<address>.2 data point name.

note

When "Real Time Position" is enabled in the module's configuration, "Include Motor Status" must also be checked.

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
o<address>.1upRWshutter up command
downRWshutter down command
stopRWshutter stop command
0 ... 100%Wpercent position
unknownRunknown state
offupRshutter off, up position
offdownRshutter off, down position
o<address>.1.value0 ... 100%RWpercent position
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
o<address>.2upRWshutter up command
downRWshutter down command
stopRWshutter stop command
0 ... 100%Wpercent position
unknownRunknown state
offupRshutter off, up position
offdownRshutter off, down position
o<address>.2.value0 ... 100%RWpercent position
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
i<address>.40Rinput pin 4 off
1Rinput 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.

IDValueR/WDescription
o<address>.1upRshutter up
downRshutter down
unknownRunknown state
offupRshutter offup
offdownRshutter offdown
o<address>.20Routput pin 2 off
1Routput 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.

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
o<address>.10RWLED 1 off
1RWLED 1 on
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
o<address>.20RWLED 2 off
1RWLED 2 on
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
o<address>.30RWLED 3 off
1RWLED 3 on
i<address>.40Rinput pin 4 off
1Rinput pin 4 on
o<address>.40RWLED 4 off
1RWLED 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.

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
i<address>.40Rinput pin 4 off
1Rinput pin 4 on
i<address+1>.10Rinput pin 5 off
1Rinput pin 5 on
i<address+1>.20Rinput pin 6 off
1Rinput pin 6 on
i<address+1>.30Rinput pin 7 off
1Rinput pin 7 on
i<address+1>.40Rinput pin 8 off
1Rinput pin 8 on
i<address+2>.10RLED 1 is off
1RLED 1 is on
i<address+2>.20RLED 2 is off
1RLED 2 is on
i<address+2>.30RLED 3 is off
1RLED 3 is on
i<address+2>.40RLED 4 is off
1RLED 4 is on
i<address+3>.10RLED 5 is off
1RLED 5 is on
i<address+3>.20RLED 6 is off
1RLED 6 is on
i<address+3>.30RLED 7 is off
1RLED 7 is on
i<address+3>.40RLED 8 is off
1RLED 8 is on
v<address+2>.10RWLED 1 is off
1RWLED 1 is on
v<address+2>.20RWLED 2 is off
1RWLED 2 is on
v<address+2>.30RWLED 3 is off
1RWLED 3 is on
v<address+2>.40RWLED 4 is off
1RWLED 4 is on
v<address+3>.10RWLED 5 is off
1RWLED 5 is on
v<address+3>.20RWLED 6 is off
1RWLED 6 is on
v<address+3>.30RWLED 7 is off
1RWLED 7 is on
v<address+3>.40RWLED 8 is off
1RWLED 8 is on

You can also set the value to on or off, that is equivalent to 1 and 0.

note

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. If the optional temperature sensor is present, DFIGLASS will use one additional input address for the temperature.

IDValueR/WDescription
i<address>.10Rbutton 1 off
1Rbutton 1 on
i<address>.20Rbutton 2 off
1Rbutton 2 on
i<address>.30Rbutton 3 off
1Rbutton 3 on
i<address>.40Rbutton 4 off
1Rbutton 4 on
i<address>.50Rbutton 5 off
1Rbutton 5 on
i<address>.60Rbutton 6 off
1Rbutton 6 on
i<address>.led.10Rled 1 off
1Rled 1 on
i<address>.led.20Rled 2 off
1Rled 2 on
i<address>.led.30Rled 3 off
1Rled 3 on
i<address>.led.40Rled 4 off
1Rled 4 on
i<address>.led.50Rled 5 off
1Rled 5 on
i<address>.led.60Rled 6 off
1Rled 6 on
i<address>.fault0Rno fault
1Rtouch keypad fault
i<address>.slap0Rnormal operation
1Rmultiple keys touched at the same time
i<address>.proximity0Rno proximity detected
1Rproximity detected
o<address>.led.10Wled 1 off
1Wled 1 on
o<address>.led.20Wled 2 off
1Wled 2 on
o<address>.led.30Wled 3 off
1Wled 3 on
o<address>.led.40Wled 4 off
1Wled 4 on
o<address>.led.50Wled 5 off
1Wled 5 on
o<address>.led.60Wled 6 off
1Wled 6 on
o<address>.disable0RWnot disabled (normal mode)
1RWdisabled (cleaning mode)
o<address>.dim0RWhigh intensity backlight
1RWlow intensity backlight
o<address>.proximity0RWdisable proximity backlight
1RWenable proximity backlight
o<address>.backlight0RWbacklight off
1RWbacklight on
o<address>.buzzer0RWbuzzer disabled
1RWbuzzer enabled

You can also set the value to on or off, that is equivalent to 1 and 0.

Temperature sensor

IDValueR/WDescription
i<address>.temp<temp>Rtemperature value (in C/10)

AURORA

AURORA 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. If the optional temperature and humidity sensor is present, DFIGLASS will 1 one additional input address for temperature (if humidity is disabled), or 2 additional input addresses for temperature and humidity.

IDValueR/WDescription
i<address>.10Rbutton 1 off
1Rbutton 1 on
i<address>.20Rbutton 2 off
1Rbutton 2 on
i<address>.30Rbutton 3 off
1Rbutton 3 on
i<address>.40Rbutton 4 off
1Rbutton 4 on
i<address>.50Rbutton 5 off
1Rbutton 5 on
i<address>.60Rbutton 6 off
1Rbutton 6 on
i<address>.led.10Rled 1 off
1Rled 1 on
i<address>.led.20Rled 2 off
1Rled 2 on
i<address>.led.30Rled 3 off
1Rled 3 on
i<address>.led.40Rled 4 off
1Rled 4 on
i<address>.led.50Rled 5 off
1Rled 5 on
i<address>.led.60Rled 6 off
1Rled 6 on
i<address>.fault0Rno fault
1Rtouch keypad fault
i<address>.slap0Rnormal operation
1Rmultiple keys touched at the same time
i<address>.proximity0Rno proximity detected
1Rproximity detected
o<address>.led.10Wled 1 off
1Wled 1 on
o<address>.led.20Wled 2 off
1Wled 2 on
o<address>.led.30Wled 3 off
1Wled 3 on
o<address>.led.40Wled 4 off
1Wled 4 on
o<address>.led.50Wled 5 off
1Wled 5 on
o<address>.led.60Wled 6 off
1Wled 6 on
o<address>.disable0RWnot disabled (normal mode)
1RWdisabled (cleaning mode)
o<address>.dim0RWhigh intensity backlight
1RWlow intensity backlight
o<address>.proximity0RWdisable proximity backlight
1RWenable proximity backlight
o<address>.backlight0RWbacklight off
1RWbacklight on
o<address>.buzzer0RWbuzzer disabled
1RWbuzzer enabled

You can also set the value to on or off, that is equivalent to 1 and 0.

Temperature sensor

IDValueR/WDescription
i<address>.temp<temp>Rtemperature value (in C/10)
i<address>.humidity<RH>Rrelative humidity percentage (0-100)

Note that the address used for both the temperature and humidity data points is the same, equal to the AURORA base address + 1.


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.

IDValueR/WDescription
i<address>.10Rinput pin 1 off
1Rinput pin 1 on
i<address>.20Rinput pin 2 off
1Rinput pin 2 on
i<address>.30Rinput pin 3 off
1Rinput pin 3 on
i<address>.40Rinput pin 4 off
1Rinput pin 4 on
v<address+1>.10RWvirtual pin 1 off
1RWvirtual pin 1 on
v<address+1>.20RWvirtual pin 2 off
1RWvirtual pin 2 on
v<address+1>.30RWvirtual pin 3 off
1RWvirtual pin 3 on
v<address+1>.40RWvirtual pin 4 off
1RWvirtual pin 4 on
v<address+2>.10RWvirtual pin 1 off
1RWvirtual pin 1 on
v<address+2>.20RWvirtual pin 2 off
1RWvirtual pin 2 on
v<address+2>.30RWvirtual pin 3 off
1RWvirtual pin 3 on
v<address+2>.40RWvirtual pin 4 off
1RWvirtual pin 4 on
v<address+3>.10RWvirtual pin 1 off
1RWvirtual pin 1 on
v<address+3>.20RWvirtual pin 2 off
1RWvirtual pin 2 on
v<address+3>.30RWvirtual pin 3 off
1RWvirtual pin 3 on
v<address+3>.40RWvirtual pin 4 off
1RWvirtual 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.

IDValueR/WDescription
i<address>0...1000Rinput voltage in Volt/100
i<address+1>0...1000Rinput voltage in Volt/100

DFAM2

The DFAM2 is an input module (0-10V, 0-20mA, temperature) with 2 analog inputs.

It uses two consecutive input addresses in the DOMINO bus

IDValueR/WDescription
i<address>-32768...32767Rinput value in mV, mA x 100 or °C x 10
i<address+1>-32768...32767Rinput value in mV, mA x 100 or °C x 10

DFLS / DFLS-P

The DFLS and DFLS-P are modules for ambient light measurement with integrated brightness and occupancy (-P type) sensors.

They use two input addresses in the DOMINO bus.

IDValueR/WDescription
i<address>.10Rinput IN1 off
1Rinput IN1 on
i<address>.20Rinput IN2 off
1Rinput IN2 on
i<address>.30Rpresence with delay is off
1Rpresence with delay is on
i<address>.40Rpresence detector light on control enabled
1Rpresence detector light on control disabled
i<address + 1>0...1000Rlux level (raw level, not translated to the lux range)
i<address + 2>0...100Rpreset dimmer level (SMART mode only)
o<address>.10Rnot active
1RWforce the expiration of the presence detector deactivation delay
o<address>.20RWenable presence detector
1RWdisable presence detector
o<address>.30Rnot active
1RWpresence forced
o<address>.40RWnormal presence detector operation
1RWdisable light ON control from presence detector
o<address + 1>0...1000Rset the setpoint for the automatic brightness regulation
o<address + 2>0...65535Rset the presence detector delay in seconds

DFLUX, DFSUN

The DFLUX and DFSUN are input modules with 1 analog light sensor.

They use one input address in the DOMINO bus.

IDValueR/WDescription
i<address>0...1023Rlux 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.

note

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.

IDValueR/WDescription
i<address>.modewinterRwinter mode
summerRsummer mode
i<address>.fanminRmin fan speed
medRmedium fan speed
maxRmax fan speed
offRfan off
i<address>.fan.modemanRmanual fan mode
autoRauto fan mode
i<address>.setpoint1Rsetpoint 1
2Rsetpoint 2
3Rsetpoint 3
offRoff
manRmanual setpoint
i<address>.setpoint.modemanRmanual setpoint mode
autoRauto setpoint mode
i<address>.temp<temp>Rtemperature value (in C/10)
faultRtemperature sensor fault
i<address>.statusoffRoff
coolingRcooling status mode
heatingRheating status mode
o<address>.modewinterRWwinter mode
summerRWsummer mode
o<address>.fanminRWmin fan speed
medRWmedium fan speed
maxRWmax fan speed
offRWfan off
o<address>.fan.modemanRWmanual fan mode
autoRWauto fan mode
o<address>.setpoint1RWsetpoint 1
2RWsetpoint 2
3RWsetpoint 3
0RWsetpoint off
manRWmanual setpoint
o<address>.setpoint.modemanRWmanual setpoint mode
autoRWauto setpoint mode
offRWoff mode
o<address>.setpoint.temp.1<temp>RWtemperature setpoint 1 value (in C/10)
o<address>.setpoint.temp.2<temp>RWtemperature setpoint 2 value (in C/10)
o<address>.setpoint.temp.3<temp>RWtemperature setpoint 3 value (in C/10)
o<address>.setpoint.temp.man<temp>RWtemperature manual setpoint value (in C/10)
o<address>.program.summer
o<address>.program.winter
refreshRWreads the daily summer/winter programs for all days of the week from the DFCT module. This command requires a considerable amount of bus time and blocks all other commands until completed
o<address>.program.summer.<day>
o<address>.program.winter.<day>
refreshRWreads the daily summer/winter programs for a single day (mon:1, sun:7) from the DFCT module. This command requires a considerable amount of bus time and blocks all other commands until completed
<s0>...<s47>RW48 character representation of the daily setpoint program 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.

IDValueR/WDescription
i<address>.modewinterRwinter mode
summerRsummer mode
i<address>.setpointcomfortRcomfort setpoint
ecoReco setpoint
offRoff
i<address>.setpoint.temp<temp>Rcurrent setpoint value (in C/10)
i<address>.temp<temp>Rtemperature value (in C/10)
faultRtemperature sensor fault
i<address>.statusoffRoff
coolingRcooling status mode
heatingRheating status mode
o<address>.modewinterRWwinter mode
summerRWsummer mode
o<address>.setpointcomfortRWcomfort setpoint
ecoRWeco setpoint
0RWoff
o<address>.setpoint.temp.comfort<temp>RWcomfort setpoint value (in C/10)
o<address>.setpoint.temp.eco<temp>RWeco setpoint value (in C/10)
o<address>.setpoint.temp.limit<temp>RWsummer/winter setpoint temperature limit (in C/10)

DFTZ2

The DFTZ2 is an input/output temperature and humidity sensor module, with fan control.

It uses 5 consecutive input addresses and 6 consecutive output addresses in the DOMINO bus.

IDValueR/WDescription
i<address>.modewinterRwinter mode
summerRsummer mode
i<address>.setpointcomfortRcomfort setpoint
ecoReco setpoint
offRoff
i<address>.setpoint.temp<temp>Rcurrent setpoint value (in C/10)
i<address>.temp<temp>Rtemperature value (in C/10)
faultRtemperature sensor fault
i<address>.humidity0...100Rrelative percent umidity
i<address>.dewpoint<temp>Rdew point value
i<address>.statusoffRoff
coolingRcooling status mode
heatingRheating status mode
i<address>.fanminRmin fan speed
medRmedium fan speed
maxRmax fan speed
offRfan off
i<address>.fan.modemanRmanual fan mode
autoRauto fan mode
o<address>.modewinterRWwinter mode
summerRWsummer mode
o<address>.setpointcomfortRWcomfort setpoint
ecoRWeco setpoint
0RWoff
o<address>.fanminRWmin fan speed
medRWmedium fan speed
maxRWmax fan speed
offRWfan off
o<address>.fan.modemanRWmanual fan mode
autoRWauto fan mode
o<address>.setpoint.temp.comfort<temp>RWcomfort setpoint value (in C/10)
o<address>.setpoint.temp.eco<temp>RWeco setpoint value (in C/10)
o<address>.setpoint.temp.limit<temp>RWsummer/winter setpoint temperature limit (in C/10)
o<address>.dewpoint.limit.1<temp>RWdew point limit 1
offRWlimit 1 not set
o<address>.dewpoint.limit.2<temp>RWdew point limit 2
offRWlimit 2 not set

DFMB-C

The DFMB-C is a Modbus control interface for HVAC units.

It uses two consecutive input and output addresses in the DOMINO bus.

note

The DFMB-C uses four not mutually exclusive bits to set the fan speed, and four other bits to set the fan blades position, also not exclusive. These bits can also have different functions based on the connected HVAC unit. Refer to the DFMB-C data sheet for additional information.

IDValueR/WDescription
i<address>.poweronRthe unit is on
offRthe unit is off
faultRunit fault condition
i<address>.modeautoRautomatic mode
heatingRheating (winter) mode
coolingRcooling (summer) mode
fanRfan mode
dehumRdehumidifier mode
i<address>.temp<temp>Rtemperature value (in C/10)
i<address>.fan.speed.11Rfan speed 1 set
0Rfan speed 1 not set
i<address>.fan.speed.21Rfan speed 2 set
0Rfan speed 2 not set
i<address>.fan.speed.31Rfan speed 3 set
0Rfan speed 3 not set
i<address>.fan.speed.41Rfan speed 4 set
0Rfan speed 4 not set
i<address>.fan.position.11Rfan position 1 set
0Rfan position 1 not set
i<address>.fan.position.21Rfan position 2 set
0Rfan position 2 not set
i<address>.fan.position.31Rfan position 3 set
0Rfan position 3 not set
i<address>.fan.position.41Rfan position 4 set
0Rfan position 4 not set
i<address>.fan.swing1Rfan swing mode on
0Rfan swing mode off
o<address>.poweronWturn unit on
offWturn unit off
o<address>.modeautoWset automatic mode
heatingWset heating (winter) mode
coolingWset cooling (summer) mode
fanWset fan mode
dehumWset dehumidifier mode
o<address>.setpoint.temp<temp>RWtemperature setpoint value (in C/10)
o<address>.fan.speed.11Wset fan speed 1
0Wreset fan speed 1
o<address>.fan.speed.21Wset fan speed 2
0Wreset fan speed 2
o<address>.fan.speed.31Wset fan speed 3
0Wreset fan speed 3
o<address>.fan.speed.41Wset fan speed 4
0Wreset fan speed 4
o<address>.fan.position.11Wset fan position 1
0Wreset fan position 1
o<address>.fan.position.21Wset fan position 2
0Wreset fan position 2
o<address>.fan.position.31Wset fan position 3
0Wreset fan position 3
o<address>.fan.position.41Wset fan position 4
0Wreset fan position 4
o<address>.fan.swing1Wturn fan swing on
0Wturn fan swing off

DFRHT

The DFRHT is a temperature and humidity sensor.

It uses four consecutive input addresses and two consecutive output addresses in the DOMINO bus.

IDValueR/WDescription
i<address>.humidity0...100Rrelative percent umidity
i<address>.temp<temp>Rtemperature value
i<address>.dewpoint<temp>Rdew point value
i<address>.dewpoint.limit.10Rdew point is lower than limit 1
1Rdew point is higher than limit 1
<temp>RWdew point limit 1
offRWlimit 1 not set
i<address>.dewpoint.limit.20Rdew point is lower than limit 2
1Rdew point is higher than limit 2
<temp>RWdew point limit 2
offRWlimit 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.

IDValueR/WDescription
i<address>.temp<temp>RWtemperature value (in C/10)
offRWlimit not set
i<address>.lux<lux*10>Rlux level according to the DFLUX range
<lux>RWlux limit
0RWlimit not set
i<address>.wind1 m/s /10Rwind value
m/sRWwind limit
0RWlimit not set
i<address>.rain0Rno rain
1Rrain
i<address>.night0Rday
1Rnight
i<address>.temp.limit0Rmeasured temp is less than limit
1Rmeasured temp is greater than limit
i<address>.lux.limit0Rmeasured lux is less than limit
1Rmeasured lux is greater than limit
i<address>.wind.limit0Rmeasured wind is less than limit
1Rmeasured wind is greater than limit
i<address>.light.south0Rlight is not coming from south
1Rlight is coming from south
i<address>.light.west0Rlight is not coming from west
1Rlight is coming from west
i<address>.light.east0Rlight is not coming from east
1Rlight is coming from east
i<address>.fault0Rsensor not fault
1Rsensor 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.

IDValueR/WDescription
energy.<n>.power.real0...65535Rreal power (Watt)
energy.<n>.power.reactive-32768...+32767Rreactive power (var)
energy.<n>.power.apparent-32768...+32767Rapparent power (VA)
energy.<n>.power.realavg0...65535Raverage real power (Watt)
energy.<n>.power.reactiveavg-32768...+32767Raverage reactive power (var)
energy.<n>.cos-1000...+1000Rcos(φ) * 1000
energy.<n>.load.10Rload 1 disabled
1Rload 1 enabled
energy.<n>.load.20Rload 2 disabled
1Rload 2 enabled
energy.<n>.load.30Rload 3 disabled
1Rload 3 enabled
energy.<n>.load.40Rload 4 disabled
1Rload 4 enabled
energy.<n>.load.50Rload 5 disabled
1Rload 5 enabled
energy.<n>.load.60Rload 6 disabled
1Rload 6 enabled
energy.<n>.load.70Rload 7 disabled
1Rload 7 enabled
energy.<n>.load.80Rload 8 disabled
1Rload 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.

note

The module's firmware should be version 1.3 or later to support negative values for active power readings.

IDValueR/WDescription
i<address>.v12[V]Rchained voltage phase 1-2
i<address>.v23[V]Rchained voltage phase 2-3
i<address>.v31[V]Rchained voltage phase 3-1
i<address>.vtm[V]Raverage chained voltage
i<address>.i1[A]Rcurrent phase 1
i<address>.i2[A]Rcurrent phase 2
i<address>.i3[A]Rcurrent phase 3
i<address>.itm[A]Raverage current
i<address>.ptot[W]Rtotal active power
i<address>.ptotk[kW]Rtotal active power
i<address>.qtot[W]Rtotal reactive power
i<address>.qtotk[kW]Rtotal reactive power
i<address>.pf[pf]Rtotal power factor
i<address>.frequency[Hz]Rfrequency
i<address>.v1n[V]Rvoltage phase 1
i<address>.v2n[V]Rvoltage phase 2
i<address>.v3n[V]Rvoltage phase 3
i<address>.p1[W]Ractive power phase 1
i<address>.p1k[kW]Ractive power phase 1
i<address>.p2[W]Ractive power phase 2
i<address>.p2k[kW]Ractive power phase 2
i<address>.p3[W]Ractive power phase 3
i<address>.p3k[kW]Ractive power phase 3
i<address>.q1[W]Rreactive power phase 1
i<address>.q1k[kW]Rreactive power phase 1
i<address>.q2[W]Rreactive power phase 2
i<address>.q2k[kW]Rreactive power phase 2
i<address>.q3[W]Rreactive power phase 3
i<address>.q3k[kW]Rreactive power phase 3
i<address>.pf1[pf]Rpower factor phase 1
i<address>.pf2[pf]Rpower factor phase 2
i<address>.pf3[pf]Rpower factor phase 3
i<address>.s1[VA]Rapparent power phase 1
i<address>.s1k[kVA]Rapparent power phase 1
i<address>.s2[VA]Rapparent power phase 2
i<address>.s2k[kVA]Rapparent power phase 2
i<address>.s3[VA]Rapparent power phase 3
i<address>.s3k[kVA]Rapparent power phase 3
i<address>.stot[VA]Rtotal apparent power
i<address>.hours[hours]Rcounter
i<address>.temperature[°C]Rtemperature
i<address>.energy.active[kWh]Rpositive active energy
i<address>.energy.activeneg[kWh]Rnegative active energy
i<address>.energy.reactive[kVARh]Rpositive reactive energy
i<address>.energy.reactiveneg[kVARh]Rnegative reactive energy
i<address>.pm[W]Raverage positive active power
i<address>.qm[VAR]Raverage positive reactive power
o<address>.reset.energy1Renergy counter reset
0R
o<address>.reset.hours1Rcounter reset
0R

DFANA-M

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.

IDValueR/WDescription
i<address>.v12[V/10]Rchained voltage phase 1-2
i<address>.v23[V/10]Rchained voltage phase 2-3
i<address>.v31[V/10]Rchained voltage phase 3-1
i<address>.vtm[V/10]Raverage chained voltage
i<address>.i1[A/100]Rcurrent phase 1
i<address>.i2[A/100]Rcurrent phase 2
i<address>.i3[A/100]Rcurrent phase 3
i<address>.itm[A/100]Raverage current
i<address>.ptot[W]Rtotal active power
i<address>.ptotk[kW]Rtotal active power
i<address>.qtot[W]Rtotal reactive power
i<address>.qtotk[kW]Rtotal reactive power
i<address>.pf[pf/1000]Rtotal power factor
i<address>.frequency[Hz]Rfrequency
i<address>.v1n[V/10]Rvoltage phase 1
i<address>.v2n[V/10]Rvoltage phase 2
i<address>.v3n[V/10]Rvoltage phase 3
i<address>.p1[W]Ractive power phase 1
i<address>.p1k[kW]Ractive power phase 1
i<address>.p2[W]Ractive power phase 2
i<address>.p2k[kW]Ractive power phase 2
i<address>.p3[W]Ractive power phase 3
i<address>.p3k[kW]Ractive power phase 3
i<address>.q1[W]Rreactive power phase 1
i<address>.q1k[kW]Rreactive power phase 1
i<address>.q2[W]Rreactive power phase 2
i<address>.q2k[kW]Rreactive power phase 2
i<address>.q3[W]Rreactive power phase 3
i<address>.q3k[kW]Rreactive power phase 3
i<address>.pf1[pf/1000]Rpower factor phase 1
i<address>.pf2[pf/1000]Rpower factor phase 2
i<address>.pf3[pf/1000]Rpower factor phase 3
i<address>.s1[VA]Rapparent power phase 1
i<address>.s1k[kVA]Rapparent power phase 1
i<address>.s2[VA]Rapparent power phase 2
i<address>.s2k[kVA]Rapparent power phase 2
i<address>.s3[VA]Rapparent power phase 3
i<address>.s3k[kVA]Rapparent power phase 3
i<address>.stot[VA]Rtotal apparent power
i<address>.hours[hours]Rcounter
i<address>.temperature[°C]Rtemperature
i<address>.energy.active[kWh]Rpositive active energy
i<address>.energy.activeneg[kWh]Rnegative active energy
i<address>.energy.reactive[kVARh]Rpositive reactive energy
i<address>.energy.reactiveneg[kVARh]Rnegative reactive energy
o<address>.reset.energy1Renergy counter reset
0R
o<address>.reset.hours1Rcounter reset
0R

DFANA-M/CC

Energy meter and load manager module for Domino bus.

In single-phase configuration, it uses 10 consecutive input addresses and 1 output address equal to the base input address. In three-phase configuration, it uses 30 consecutive input addresses and 3 output address <address>, <address>+10, <address>+20.

IDValueR/WDescription
i<address>.v[V / 10]Rmeasured RMS voltage
i<address>.i[A / 100]Rmeasured RMS current
i<address>.p[W]Ractive power (signed)
i<address>.q[VAR]Rreactive power (signed)
i<address>.s[VA]Rapparent power
i<address>.pf[x 1000]Rpower factor (signed: positive for inductive loads, negative for reactive loads)
i<address>.ae[Wh]Rtotal active energy
i<address>.10Rload 1 disabled
1Rload 1 enabled
i<address>.20Rload 2 disabled
1Rload 2 enabled
i<address>.30Rload 3 disabled
1Rload 3 enabled
i<address>.40Rload 4 disabled
1Rload 4 enabled
i<address>.50Rload 5 disabled
1Rload 5 enabled
i<address>.60Rload 6 disabled
1Rload 6 enabled
i<address>.70Rload 7 disabled
1Rload 7 enabled
i<address>.80Rload 8 disabled
1Rload 8 enabled
o<address>.10RWload 1 control enabled
1RWload 1 always enabled
o<address>.20RWload 2 control enabled
1RWload 2 always enabled
o<address>.30RWload 3 control enabled
1RWload 3 always enabled
o<address>.40RWload 4 control enabled
1RWload 4 always enabled
o<address>.50RWload 5 control enabled
1RWload 5 always enabled
o<address>.60RWload 6 control enabled
1RWload 6 always enabled
o<address>.70RWload 7 control enabled
1RWload 7 always enabled
o<address>.80RWload 8 control enabled
1RWload 8 always enabled
o<address>.aeresetWreset total active energy counter

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.

IDValueR/WDescription
i<address>.v[V / 10]Rmeasured RMS voltage
i<address>.i[A / 100]Rmeasured RMS current
i<address>.p[W]Ractive power (signed)
i<address>.q[VAR]Rreactive power (signed)
i<address>.s[VA]Rapparent power
i<address>.pf[x 1000]Rpower factor (signed: positive for inductive loads, negative for reactive loads)
i<address>.ae[Wh]Rtotal active energy
i<address>.10Rload 1 disabled
1Rload 1 enabled
i<address>.20Rload 2 disabled
1Rload 2 enabled
i<address>.30Rload 3 disabled
1Rload 3 enabled
i<address>.40Rload 4 disabled
1Rload 4 enabled
i<address>.50Rload 5 disabled
1Rload 5 enabled
i<address>.60Rload 6 disabled
1Rload 6 enabled
i<address>.70Rload 7 disabled
1Rload 7 enabled
i<address>.80Rload 8 disabled
1Rload 8 enabled
o<address>.10RWload 1 control enabled
1RWload 1 always enabled
o<address>.20RWload 2 control enabled
1RWload 2 always enabled
o<address>.30RWload 3 control enabled
1RWload 3 always enabled
o<address>.40RWload 4 control enabled
1RWload 4 always enabled
o<address>.50RWload 5 control enabled
1RWload 5 always enabled
o<address>.60RWload 6 control enabled
1RWload 6 always enabled
o<address>.70RWload 7 control enabled
1RWload 7 always enabled
o<address>.80RWload 8 control enabled
1RWload 8 always enabled
o<address>.buzzer0RWbuzzer disabled
1RWbuzzer enabled
o<address>.aeresetWreset total active energy counter

DFTA / DFTE

The DFTA and DFTE are ambient temperature sensors. They use 1 input address in the DOMINO bus.

IDValueR/WDescription
i<address>.temp<temp>Rtemperature value (in C/10)

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.

Domino UI

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

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

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.

IDAttribute
energy.<n>.powervaluereal power, followed by W. <n> is the sequential index (1 to 3) of the DFCC module.

DFCT and DF8RIT

You can use the temp and tempmini objects to control DFCT or DF8RIT devices.

Domino UI

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.

IDAttributeSet toDescription
<address>.modevalueSUMMERsummer mode (cooling)
WINTERwinter mode (heating)
<address>.mode.label.summervisibletruethe DFCT is in summer mode
<address>.mode.label.wintervisibletruethe DFCT is in winter mode
<address>.statusvalueOFFzone off
ONzone on
<address>.status.label.coolingvisibletrueif the zone is cooling
<address>.status.label.heatingvisibletrueif the zone is heating
<address>.fanvalueOFFfan off
MINminimum fan speed
MEDmedium fan speed
MAXmaximum fan speed
<address>.fan.label.minvisibletruethe fan speed is min
<address>.fan.label.medvisibletruethe fan speed is med
<address>.fan.label.maxvisibletruethe fan speed is max
<address>.fan.modevalueMANmanual fan mode
AUTOauto fan mode
<address>.setpointvalue1,2,3active setpoint
MANmanual setpoint
OFFzone off
<address>.setpoint.label.1visibletruesetpoint 1 is active
<address>.setpoint.label.2visibletruesetpoint 2 is active
<address>.setpoint.label.3visibletruesetpoint 3 is active
<address>.setpoint.label.manvisibletruemanual setpoint is active
<address>.setpoint.label.offvisibletruezone is off
<address>.setpoint.modevalueMANmanual setpoint mode
AUTOauto setpoint mode
<address>.setpoint.tempvalue<value>the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.temp.1value<value>the active setpoint 1 temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.temp.2value<value>the active setpoint 2 temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.temp.3value<value>the active setpoint 3 temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.temp.manvalue<value>the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.tempvalue<temp>the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
FAULTfault/error condition

USER Commands

There are several predefined buttons. Use any ordinary [[user]] object, setting the name and param fields based on this table.

NameParamAction
<address>modecycle through summer and winter mode
mode.summerset summer mode (cooling)
mode.winterset winter mode (heating)
fancycle through fan speeds and modes (auto, off, man/min, man/med, man/max, auto)
<address>.setpointmodecycle through the manual, automatic and off operation modes
mode.manset manual operation mode
mode.autoset automatic operation mode
mode.offoff mode
temp.1.upincrease setpoint 1 temperature in 0.5C steps
temp.1.downdecrease setpoint 1 temperature in 0.5C steps
temp.1.<t>setpoint 1 set to temperature t, in C/10 (0 <= t <= 355)
temp.2.upincrease setpoint 2 temperature in 0.5C steps
temp.2.downdecrease setpoint 2 temperature in 0.5C steps
temp.2.<t>setpoint 2 set to temperature t, in C/10 (0 <= t <= 355)
temp.3.upincrease setpoint 3 temperature in 0.5C steps
temp.3.downdecrease setpoint 3 temperature in 0.5C steps
temp.3.<t>setpoint 3 set to temperature t, in C/10 (0 <= t <= 355)
temp.man.upincrease manual setpoint temperature in 0.5C steps
temp.man.downdecrease manual setpoint temperature in 0.5C steps
temp.man.<t>manual setpoint set to temperature t, in C/10 (0 <= t <= 355)
<address>.fanmodecycle through the manual and automatic fan speed modes
mode.manset manual fan speed mode
mode.autoset automatic fan speed mode
upincrease fan speed
downdecrease fan speed
minset min fan speed
medset med fan speed
maxset max fan speed
offfan off

Using slider objects for DF8RIT shutter's position

When shutter control is enabled on the DF8RIT multifunction module, up to four addresses are used to read and set the shutters' position (goto function).

You can use the slider objects, slider|sliderv and slider|sliderh, to display and control the position. Remember that the shutters' position addresses are base_address + 1 to base_address + 4, where base_address is the address of the module. Set both the slider's ID and address to <server_name>.<base_address + N>, with N from 1 to 4.

For example, assuming that domino is the I/O Server ID, and the DF8RIT base address is 121, the slider's ID and address to control the first shutter (relays 1 and 2) should be domino.122.

note

Note that you can set the inverse attribute of the slider|sliderv object to true, in order to have the cursor at the top instead of bottom of the slider when the position is 0.


Using slider objects for DF4RI / DF4RIR shutter's position

When shutter control is enabled on the DF4RI multifunction module, up to two addresses are used to read and set the shutters' position (goto function).

You can use the slider objects, slider|sliderv and slider|sliderh, to display and control the position. Remember that the shutters' position addresses are base_address + 1 and base_address + 2, where base_address is the address of the module. Set both the slider's ID and address to <server_name>.<base_address + N>, with N from 1 to 2.

For example, assuming that domino is the I/O Server ID, and the DF8RIT base address is 100, the slider's ID and address to control the first shutter (relays 1 and 2) should be domino.101.

note

Note that you can set the inverse attribute of the [[slider|sliderv]] object to true, in order to have the cursor at the top instead of bottom of the slider when the position is 0.


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.

Domino UI

UISET Actions

You can use any object that accepts a text attribute, usually text and others, like images, to automatically display the relevant information of all DFTZ modules.

IDAttributeSet toDescription
<address>.modevalueSUMMERsummer mode (cooling)
WINTERwinter mode (heating)
<address>.mode.label.summervisibletruethe DFTZ is in summer mode
<address>.mode.label.wintervisibletruethe DFTZ is in winter mode
<address>.statusvalueOFFzone off
ONzone on
<address>.status.label.offvisibletrueif the zone is not cooling or heating
<address>.status.label.coolingvisibletrueif the zone is cooling
<address>.status.label.heatingvisibletrueif the zone is heating
<address>.setpointvalueCOMcomfort setpoint
MANmanual setpoint
OFFzone off
<address>.setpoint.label.1visibletruecomfort setpoint is active
<address>.setpoint.label.2visibletrueeco setpoint is active
<address>.setpoint.label.offvisibletruezone is off
<address>.setpoint.tempvalue<temp>the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.temp.1value<temp>the comfort setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.temp.2value<temp>the eco setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.temp.manvalue<temp>the summer or winter setpoint temperature limit, in Celsius degrees with one decimal digit, followed by " °C"
<address>.tempvalue<temp>the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
FAULTfault/error condition

USER Commands

There are several predefined buttons. Use any ordinary [[user]] object, setting the name and param fields based on this table.

NameParamAction
<address>modecycle through summer and winter mode
mode.summerset summer mode (cooling)
mode.winterset winter mode (heating)
<address>.setpointmodecycle through the manual, automatic and off operation modes
mode.comfortset comfort operation mode
mode.ecoset eco operation mode
mode.offoff mode
temp.upincrease the active setpoint temperature in 0.5C steps
temp.downddecrease the active setpoint temperature in 0.5C steps
temp.<t>active setpoint set to temperature t, in C/10 (0 <= t <= 355)
temp.1.upincrease comfort setpoint temperature in 0.5C steps
temp.1.downdecrease comfort setpoint temperature in 0.5C steps
temp.1.<t>comfort setpoint set to temperature t, in C/10 (0 <= t <= 355)
temp.2.upincrease eco setpoint temperature in 0.5C steps
temp.2.downdecrease eco setpoint temperature in 0.5C steps
temp.2.<t>eco setpoint set to temperature t, in C/10 (0 <= t<= 355)
temp.man.upincrease setpoint temperature limit in 0.5C steps
temp.man.downdecrease setpoint temperature limit in 0.5C steps
temp.man.<t>set-point temperature limit set to temperature t, in C/10 (0 <= t <= 355)

DFTZ2

You can use the tempmini object to control DFTZ2 devices.

You could also use the larger temp object, but some of its controls are not used with the DFTZ2 module.

Domino UI

UISET Actions

You can use any object that accepts a text attribute, usually text but and others, like images, to automatically display the relevant information of all DFTZ2 modules.

IDAttributeSet toDescription
<address>.modevalueSUMMERsummer mode (cooling)
WINTERwinter mode (heating)
<address>.mode.label.summervisibletruethe DFTZ2 is in summer mode
<address>.mode.label.wintervisibletruethe DFTZ2 is in winter mode
<address>.statusvalueOFFzone off
ONzone on
<address>.status.label.offvisibletrueif the zone is not cooling or heating
<address>.status.label.coolingvisibletrueif the zone is cooling
<address>.status.label.heatingvisibletrueif the zone is heating
<address>.setpoint.modevalueCOMcomfort setpoint
ECOeco setpoint
OFFzone off
<address>.setpoint.label.1visibletruecomfort setpoint is active
<address>.setpoint.label.2visibletrueeco setpoint is active
<address>.setpoint.label.offvisibletruezone is off
<address>.setpoint.tempvalue<temp>the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.tempvisibletrueif mode is not off
<address>.setpoint.temp.1value<temp>the comfort setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.temp.2value<temp>the eco setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.setpoint.temp.manvalue<temp>the summer or winter setpoint temperature limit, in Celsius degrees with one decimal digit, followed by " °C"
<address>.tempvalue<temp>the current temperature, in Celsius degrees with one decimal digit, followed by " °C"
FAULTfault/error condition
<address>.humidityvalue<temp>the current relative humidity (%)
<address>.dewpointvalue<temp>the current dew point, in Celsius degrees with one decimal digit, followed by " °C"
<address>.limit.1value<temp>the dew point limit 1, in Celsius degrees with one decimal digit, followed by " °C"
<address>.limit.2value<temp>the dew point limit 2, in Celsius degrees with one decimal digit, followed by " °C"
<address>.fanvalue<temp>the fan speed: OFF, MIN, MED, MAX
<address>.fan.modevalue<temp>the fan mode: AUTO, MAN
<address>.fan.label.minvisibletrueif fan speed is MIN
<address>.fan.label.medvisibletrueif fan speed is MED
<address>.fan.label.maxvisibletrueif fan speed is MAX

USER Commands

There are several predefined buttons. Use any ordinary button object, setting the name and param fields based on this table.

NameParamAction
<address>fancycle through fan speeds
modecycle through summer and winter mode
mode.summerset summer mode (cooling)
mode.winterset winter mode (heating)
<address>.setpointmodecycle through the manual, automatic and off operation modes
mode.comfortset comfort operation mode
mode.ecoset eco operation mode
mode.offoff mode
temp.upincrease the active setpoint temperature in 0.5C steps
temp.downddecrease the active setpoint temperature in 0.5C steps
temp.<t>active setpoint set to temperature t, in C/10 (0 <= t <= 355)
temp.1.upincrease comfort setpoint temperature in 0.5C steps
temp.1.downdecrease comfort setpoint temperature in 0.5C steps
temp.1.<t>comfort setpoint set to temperature t, in C/10 (0 <= t <= 355)
temp.2.upincrease eco setpoint temperature in 0.5C steps
temp.2.downdecrease eco setpoint temperature in 0.5C steps
temp.2.<t>eco setpoint set to temperature t, in C/10 (0 <= t <= 355)
temp.man.upincrease setpoint temperature limit in 0.5C steps
temp.man.downdecrease 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.9.0

  • support of AURORA

3.8.0

  • support of DFAM2
  • support of DFANA-M/CC
  • support of DFMB-C
  • support of DFTZ2
  • support for DTCT firmware versions >= 10.0 for daily programs read/write
  • new "raw" datapoint allows to send a 2 byte raw command to the DFDALI64 module
  • improved support for DFCP/DFH firmware upload
  • fixed (temp) GUI object setpoint program
  • workaround for DFH with fw < 4.0 that caused the clock=sync command to set an incorrect time on Sundays

3.7.0

  • support of DFANA-M
  • support of DFDALI64
  • support of DFDIM
  • support of DFLS smart mode
  • support of DF4RI/DF4RIR virtual outputs
  • support of DF8RIT configuration with temperature input address enabled and temperature control disabled
  • support of position information and commands for DFTP, DFTP/I
  • support of DFCP counters
  • bus and modules fault detection
  • high availability support for redundant DFH installations
  • fixed "modulefault" data point of individual modules not working with DFH gateways

3.6.0

  • added support for DFTA and DFTE
  • DFIGLASS: added support for the optional temperature sensor, and other enhancements
  • improved compatibility with DF4DV
  • fixed a bug that could affect DF4RI/DF4RIR or DF8RIT modules with adjacent addresses and shutters defined

3.5.1

  • added support for DF4DV
  • added support for DF4RI / DF4RIR
  • added support for DF8RIT
  • added support for DFLS / DFLS-P
  • fixed a bug that could cause erroneous readings of DFCC2 2'complement values
  • DFANA updated to support negative active energy values (fw. 1.5 or later)

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.