Difference between revisions of "Domino"

From HSYCO
Jump to navigation Jump to search
 
(24 intermediate revisions by 2 users not shown)
Line 313: Line 313:
 
|DF4RP/I
 
|DF4RP/I
 
|4 generic inputs ON-OFF + 4 outputs
 
|4 generic inputs ON-OFF + 4 outputs
 +
|-
 +
|DF4RI / DF4RIR
 +
|multifunction module with 4 digital inputs and 4 outputs (power relay)
 
|-
 
|-
 
|DF8RIT
 
|DF8RIT
Line 349: Line 352:
 
|DFAI
 
|DFAI
 
|2 analog inputs
 
|2 analog inputs
 +
|-
 +
|DFLS / DFLS-P
 +
|ambient light sensor and presence detector
 
|-
 
|-
 
|DFLUX, DFSUN
 
|DFLUX, DFSUN
Line 1,530: Line 1,536:
 
|R
 
|R
 
|input pin 4 on
 
|input pin 4 on
|-
 
 
|rowspan="2"|i<address>.5
 
|0
 
|R
 
|input pin 5 off
 
|-
 
|1
 
|R
 
|input pin 5 on
 
|-
 
 
|rowspan="2"|i<address>.6
 
|0
 
|R
 
|input pin 6 off
 
|-
 
|1
 
|R
 
|input pin 6 on
 
|-
 
 
|rowspan="2"|i<address>.7
 
|0
 
|R
 
|input pin 7 off
 
|-
 
|1
 
|R
 
|input pin 7 on
 
|-
 
 
|rowspan="2"|i<address>.8
 
|0
 
|R
 
|input pin 8 off
 
|-
 
|1
 
|R
 
|input pin 8 on
 
 
|-
 
|-
  
Line 1,718: Line 1,684:
 
|}
 
|}
  
==== Relay outputs section 5-6 ====
+
=== DFDM, DFDI, DFDI2, DFDI2B, DFDT ===
If automation 3 is not enabled (base address + 3 not used):
+
The DFDM, DFDI, DFDI2, DFDI2B and DFDT are output modules with 1 dimmer output.
 +
 
 +
They use one address in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,728: Line 1,696:
 
|-
 
|-
  
|rowspan="2"|o<address>.1
+
|rowspan="4"|o<address>
|0
+
|program
|RW
+
|R
|output pin 5 off
+
|program mode
 +
|-
 +
|fault
 +
|R
 +
|dimmer fault
 +
|-
 +
|auto
 +
|R
 +
|auto mode
 +
|-
 +
|man
 +
|R
 +
|manual mode
 
|-
 
|-
|1
+
 
 +
|rowspan="3"|o<address>.1
 +
|off
 
|RW
 
|RW
|output pin 5 on
+
|dimmer off
 
|-
 
|-
 
+
|1...100%
|rowspan="2"|o<address>.2
 
|0
 
 
|RW
 
|RW
|output pin 6 off
+
|percent dimmer level
 
|-
 
|-
|1
+
|on
 
|RW
 
|RW
|output pin 6 on
+
|dimmer on at last level
 
|-
 
|-
|}
 
  
If automation 3 is enabled (base address + 3 is used):
+
|rowspan="3"|o<address>.ramp
 
+
|save
{| class="wikitable"
+
|RW
!ID
+
|saves the current ramp as default
!Value
 
!R/W
 
!Description
 
 
|-
 
|-
 
+
|1...30
|rowspan="6"|o<address>.5
 
|up
 
 
|RW
 
|RW
|shutter up command
+
|ramp value in seconds (1 sec steps up to 10 and 2 sec steps up to 30)
 
|-
 
|-
|down
+
|40, 50, 60
 
|RW
 
|RW
|shutter down command
+
|ramp value in seconds (10 sec steps)
 
|-
 
|-
|stop
+
 
 +
|o<address>.setpoint
 +
|0...1023
 
|RW
 
|RW
|shutter stop command
+
|setpoint level
 
|-
 
|-
|unknown
+
 
|R
+
|o<address>.hysteresis
|unknown state
+
|0...255
|-
 
|offup
 
 
|RW
 
|RW
|shutter off, up position
+
|tolerance level
 
|-
 
|-
|offdown
+
 
 +
|o<address>.time
 +
|0...255
 
|RW
 
|RW
|shutter off, down position
+
|period (seconds)
 
|-
 
|-
|o<address + 3>
+
|}
|0 ... 100%
+
 
|RW
+
The dimmer level can be set using additional formats besides the standard percent values:
|percent position
+
*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.
  
==== Relay outputs section 7-8 ====
+
The DF4DV uses 4 consecutive addresses in the DOMINO bus.
If automation 4 is not enabled (base address + 4 not used):
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,800: Line 1,780:
 
|-
 
|-
  
|rowspan="2"|o<address>.1
+
|o<address>
|0
+
|program
|RW
+
|R
|output pin 7 off
+
|program mode
 
|-
 
|-
|1
+
 
 +
|rowspan="3"|o<address>.1
 +
|off
 
|RW
 
|RW
|output pin 7 on
+
|dimmer off
 
|-
 
|-
 
+
|1...100%
|rowspan="2"|o<address>.2
 
|0
 
 
|RW
 
|RW
|output pin 8 off
+
|percent dimmer level
 
|-
 
|-
|1
+
|on
 
|RW
 
|RW
|output pin 8 on
+
|dimmer on at last level
 
|-
 
|-
|}
 
  
If automation 4 is enabled (base address + 4 is used):
+
|rowspan="3"|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)
 +
|-
 +
 
 +
|}
 +
 
 +
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.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,830: Line 1,835:
 
|-
 
|-
  
|rowspan="6"|o<address>.7
+
|o<address>.<command>
|up
+
|0...255
 
|RW
 
|RW
|shutter up command
+
|commands and values according to the DFDMX programming manual
 
|-
 
|-
|down
+
|}
|RW
+
 
|shutter down command
+
----
|-
+
 
|stop
+
=== DFDALI ===
|RW
+
The DFDALI is a DALI interface module. Using the DFDALI you can control up to 32 DALI devices.
|shutter stop command
+
 
|-
+
You can control individual devices, groups or broadcast commands to all devices.  
|unknown
 
|R
 
|unknown state
 
|-
 
|offup
 
|RW
 
|shutter off, up position
 
|-
 
|offdown
 
|RW
 
|shutter off, down position
 
|-
 
|o<address + 4>
 
|0 ... 100%
 
|RW
 
|percent 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.
 
}}
 
  
 +
It uses one input (if enabled) and one output address in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,877: Line 1,858:
 
|-
 
|-
  
|rowspan="2"|i<address + 5>.mode
+
|o<address>
|winter
+
|refresh
|R
+
|RW
|winter mode
+
|queries the DFDALI module to update the current status of all DALI devices
|-
 
|summer
 
|R
 
|summer mode
 
 
|-
 
|-
  
|rowspan="4"|i<address + 5>.fan
+
|o<address>
|min
+
|off
|R
+
|RW
|min fan speed
+
|broadcast off command
 
|-
 
|-
|med
+
 
|R
+
|o<address>.all
|medium fan speed
+
o<address>.0
 +
|<level>
 +
|RW
 +
|broadcast level command
 
|-
 
|-
|max
+
 
|R
+
|rowspan="2"|o<address>.group.<DALI group>
|max fan speed
+
|off
 +
|RW
 +
|broadcast off command
 
|-
 
|-
|off
+
|<level>
|R
+
|RW
|fan off
+
|group level command
 
|-
 
|-
  
|rowspan="2"|i<address + 5>.fan.mode
+
|rowspan="3"|o<address>.<DALI address>
|man
+
|off
|R
+
|RW
|manual fan mode
+
|turn off a single device
 
|-
 
|-
|auto
+
|<level>
|R
+
|RW
|auto fan mode
+
|set a single device to a specific level
 
|-
 
|-
 
+
|> 100
|rowspan="5"|i<address + 5>.setpoint
+
|RW
|1
+
|special functions, having values between 101 and 255, as defined in the DFDALI manual
|R
 
|setpoint 1
 
|-
 
|2
 
|R
 
|setpoint 2
 
|-
 
|3
 
|R
 
|setpoint 3
 
 
|-
 
|-
 +
 +
|rowspan="2"|i<address>.polling
 
|off
 
|off
|R
+
|RW
|off
+
|polling mode is disabled
 
|-
 
|-
|man
+
|on
|R
+
|RW
|manual setpoint
+
|polling mode is enabled
 
|-
 
|-
  
|rowspan="2"|i<address + 5>.setpoint.mode
+
|rowspan="2"|i<address>.test
|man
+
|0
|R
+
|RW
|manual setpoint mode
+
|test button not pressed
 
|-
 
|-
|auto
+
|1
|R
+
|RW
|auto setpoint mode
+
|test button pressed
 
|-
 
|-
  
|rowspan="2"|i<address + 5>.temp
+
|rowspan="4"|i<address>.dali
|<temp>
+
|nopower
|R
+
|RW
|temperature value (in C/10)
+
|power failure on the DALI bus
 
|-
 
|-
|fault
+
|open
|R
+
|RW
|temperature sensor fault
+
|DALI bus is open
 
|-
 
|-
 
+
|short
|rowspan="3"|i<address + 5>.status
 
|off
 
|R
 
|off
 
|-
 
|cooling
 
|R
 
|cooling status mode
 
|-
 
|heating
 
|R
 
|heating status mode
 
|-
 
 
 
|rowspan="2"|o<address + 5>.mode
 
|winter
 
 
|RW
 
|RW
|winter mode
+
|DALI bus is shorted
 
|-
 
|-
|summer
+
|on
 
|RW
 
|RW
|summer mode
+
|DALI bus on
 
|-
 
|-
  
|rowspan="4"|o<address + 5>.fan
+
|rowspan="2"|i<address>.1
|min
+
|fault
 
|RW
 
|RW
|min fan speed
+
|DALI device 1 reporting a lamp failure
 +
|-
 +
|unknown
 +
|R
 +
|DALI device 1 status unknown
 
|-
 
|-
|med
+
|}
 +
 
 +
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.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 
 +
|rowspan="3"|o<address>.1
 +
|off
 
|RW
 
|RW
|medium fan speed
+
|dimmer off
 
|-
 
|-
|max
+
|1 ... 100%
 
|RW
 
|RW
|max fan speed
+
|percent dimmer level
 
|-
 
|-
|off
+
|on
 
|RW
 
|RW
|fan off
+
|dimmer on at last level
 
|-
 
|-
  
|rowspan="2"|o<address + 5>.fan.mode
+
|rowspan="2"|o<address>.2
|man
+
|0
 
|RW
 
|RW
|manual fan mode
+
|output pin 1 off
 
|-
 
|-
|auto
+
|1
 
|RW
 
|RW
|auto fan mode
+
|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.
  
|rowspan="5"|o<address + 5>.setpoint
+
{| class="wikitable"
|1
+
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 
 +
|rowspan="6"|o<address>.1
 +
|up
 
|RW
 
|RW
|setpoint 1
+
|shutter up command
 
|-
 
|-
|2
+
|down
 
|RW
 
|RW
|setpoint 2
+
|shutter down command
 
|-
 
|-
|3
+
|stop
 
|RW
 
|RW
|setpoint 3
+
|shutter stop command
 +
|-
 +
|unknown
 +
|R
 +
|unknown state
 
|-
 
|-
|0
+
|offup
 
|RW
 
|RW
|setpoint off
+
|shutter off, up position
 
|-
 
|-
|man
+
|offdown
 
|RW
 
|RW
|manual setpoint
+
|shutter off, down position
 
|-
 
|-
  
|o<address + 5>.setpoint.temp.1
+
|rowspan="6"|o<address>.2
|<temp>
+
|up
 
|RW
 
|RW
|temperature setpoint 1 value (in C/10)
+
|shutter up command
 
|-
 
|-
 
+
|down
|o<address + 5>.setpoint.temp.2
 
|<temp>
 
 
|RW
 
|RW
|temperature setpoint 2 value (in C/10)
+
|shutter down command
 
|-
 
|-
 
+
|stop
|o<address + 5>.setpoint.temp.3
 
|<temp>
 
 
|RW
 
|RW
|temperature setpoint 3 value (in C/10)
+
|shutter stop command
 
|-
 
|-
 
+
|unknown
|o<address + 5>.setpoint.temp.man
+
|R
|<temp>
+
|unknown state
|RW
 
|temperature manual setpoint value (in C/10)
 
 
|-
 
|-
 
+
|offup
|o<address + 5>.program.summer<br/>o<address + 5>.program.winter
 
|refresh
 
 
|RW
 
|RW
|forces to daily summer/winter program for all days of the week
+
|shutter off, up position
 
|-
 
|-
 
+
|offdown
|rowspan="2"|o<address + 5>.program.summer.<day><br/>o<address + 5>.program.winter.<day>
 
|refresh
 
 
|RW
 
|RW
|forces to daily summer/winter program for the reported day (mon:1, sun:7)
+
|shutter off, down position
|-
 
|<s0>...<s47>
 
|RW
 
|48 character represents the daily setpoint program divided in time slots of 30 minutes
 
 
|-
 
|-
  
 
|}
 
|}
 +
 
----
 
----
  
=== DFDM, DFDI, DFDI2, DFDI2B, DFDT ===
+
=== DFTP/I ===
The DFDM, DFDI, DFDI2, DFDI2B and DFDT are output modules with 1 dimmer output.
+
The DFTP is an input/output module for 2 shutters and 4 generic inputs.
  
They use one address in the DOMINO bus.
+
It uses one input and one output address in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,086: Line 2,081:
 
|-
 
|-
  
|rowspan="4"|o<address>
+
|rowspan="2"|i<address>.1
|program
+
|0
 
|R
 
|R
|program mode
+
|input pin 1 off
 
|-
 
|-
|fault
+
|1
 
|R
 
|R
|dimmer fault
+
|input pin 1 on
|-
 
|auto
 
|R
 
|auto mode
 
|-
 
|man
 
|R
 
|manual mode
 
 
|-
 
|-
  
|rowspan="3"|o<address>.1
+
|rowspan="6"|o<address>.1
|off
+
|up
 
|RW
 
|RW
|dimmer off
+
|shutter up command
 
|-
 
|-
|1...100%
+
|down
 
|RW
 
|RW
|percent dimmer level
+
|shutter down command
 
|-
 
|-
|on
+
|stop
 
|RW
 
|RW
|dimmer on at last level
+
|shutter stop command
 
|-
 
|-
 
+
|unknown
|rowspan="3"|o<address>.ramp
+
|R
|save
+
|unknown state
 +
|-
 +
|offup
 
|RW
 
|RW
|saves the current ramp as default
+
|shutter off, up position
 
|-
 
|-
|1...30
+
|offdown
 
|RW
 
|RW
|ramp value in seconds (1 sec steps up to 10 and 2 sec steps up to 30)
+
|shutter off, down position
 +
|-
 +
 
 +
|rowspan="2"|i<address>.2
 +
|0
 +
|R
 +
|input pin 2 off
 
|-
 
|-
|40, 50, 60
+
|1
|RW
+
|R
|ramp value in seconds (10 sec steps)
+
|input pin 2 on
 
|-
 
|-
  
|o<address>.setpoint
+
|rowspan="6"|o<address>.2
|0...1023
+
|up
 
|RW
 
|RW
|setpoint level
+
|shutter up command
 
|-
 
|-
 
+
|down
|o<address>.hysteresis
 
|0...255
 
 
|RW
 
|RW
|tolerance level
+
|shutter down command
 
|-
 
|-
 
+
|stop
|o<address>.time
 
|0...255
 
 
|RW
 
|RW
|period (seconds)
+
|shutter stop command
 
|-
 
|-
|}
+
|unknown
 
+
|R
The dimmer level can be set using additional formats besides the standard percent values:
+
|unknown state
*absolute positive integer number between 0 and 100
+
|-
*percent number, formatted as x%
+
|offup
*fractional format, formatted as “n/m”, where 0 <= n <= m.
+
|RW
 +
|shutter off, up position
 +
|-
 +
|offdown
 +
|RW
 +
|shutter off, down position
 +
|-
 +
 
 +
|rowspan="2"|i<address>.3
 +
|0
 +
|R
 +
|input pin 3 off
 +
|-
 +
|1
 +
|R
 +
|input pin 3 on
 +
|-
 +
 
 +
|rowspan="2"|i<address>.4
 +
|0
 +
|R
 +
|input pin 4 off
 +
|-
 +
|1
 +
|R
 +
|input pin 4 on
 +
|-
 +
 
 +
|}
  
 
----
 
----
  
=== DF4DV ===
+
=== DFTR ===
The DF4DV, is an input/output module with 4 ballast (1-10V) outputs.
+
The DFTR is an output module with 1 shutter output and 1 relay output.
  
The DF4DV uses 4 consecutive addresses in the DOMINO bus.
+
It uses one address in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,170: Line 2,189:
 
|-
 
|-
  
|o<address>
+
|rowspan="5"|o<address>.1
|program
+
|up
 +
|R
 +
|shutter up
 +
|-
 +
|down
 
|R
 
|R
|program mode
+
|shutter down
 
|-
 
|-
 
+
|unknown
|rowspan="3"|o<address>.1
+
|R
|off
+
|unknown state
|RW
 
|dimmer off
 
 
|-
 
|-
|1...100%
+
|offup
|RW
+
|R
|percent dimmer level
+
|shutter offup
 
|-
 
|-
|on
+
|offdown
|RW
+
|R
|dimmer on at last level
+
|shutter offdown
 
|-
 
|-
  
|rowspan="3"|o<address>.ramp
+
|rowspan="2"|o<address>.2
|save
+
|0
|RW
+
|R
|saves the current ramp as default
+
|output pin 2 off
 
|-
 
|-
|1...30
+
|1
|RW
+
|R
|ramp value in seconds (1 sec steps up to 10 and 2 sec steps up to 30)
+
|output pin 2 on
 
|-
 
|-
|40, 50, 60
+
 
|RW
+
|}
|ramp 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 ===
+
=== DF4IL ===
The DFDMX is a DMX-512 protocol output module.
+
The DF4IL is an input/output module with 4 digital inputs and 4 digital open collector outputs for LEDs.
  
It uses one address in the DOMINO bus.
+
It uses one input and one output address in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,225: Line 2,237:
 
|-
 
|-
  
|o<address>.<command>
+
|rowspan="2"|i<address>.1
|0...255
+
|0
 +
|R
 +
|input pin 1 off
 +
|-
 +
|1
 +
|R
 +
|input pin 1 on
 +
|-
 +
 
 +
|rowspan="2"|o<address>.1
 +
|0
 +
|RW
 +
|LED 1 off
 +
|-
 +
|1
 
|RW
 
|RW
|commands and values according to the DFDMX programming manual
+
|LED 1 on
 
|-
 
|-
|}
 
  
----
+
|rowspan="2"|i<address>.2
 
+
|0
=== DFDALI ===
+
|R
The DFDALI is a DALI interface module. Using the DFDALI you can control up to 32 DALI devices.  
+
|input pin 2 off
 
+
|-
You can control individual devices, groups or broadcast commands to all devices.
+
|1
 
+
|R
It uses one input (if enabled) and one output address in the DOMINO bus.
+
|input pin 2 on
 
 
{| class="wikitable"
 
!ID
 
!Value
 
!R/W
 
!Description
 
 
|-
 
|-
  
|o<address>
+
|rowspan="2"|o<address>.2
|refresh
+
|0
 
|RW
 
|RW
|queries the DFDALI module to update the current status of all DALI devices
+
|LED 2 off
 
|-
 
|-
 
+
|1
|o<address>
 
|off
 
 
|RW
 
|RW
|broadcast off command
+
|LED 2 on
 
|-
 
|-
  
|o<address>.all
+
|rowspan="2"|i<address>.3
o<address>.0
+
|0
|<level>
+
|R
|RW
+
|input pin 3 off
|broadcast level command
+
|-
 +
|1
 +
|R
 +
|input pin 3 on
 
|-
 
|-
  
|rowspan="2"|o<address>.group.<DALI group>
+
|rowspan="2"|o<address>.3
|off
+
|0
 
|RW
 
|RW
|broadcast off command
+
|LED 3 off
 
|-
 
|-
|<level>
+
|1
 
|RW
 
|RW
|group level command
+
|LED 3 on
 
|-
 
|-
  
|rowspan="3"|o<address>.<DALI address>
+
|rowspan="2"|i<address>.4
|off
+
|0
|RW
+
|R
|turn off a single device
+
|input pin 4 off
 
|-
 
|-
|<level>
+
|1
|RW
+
|R
|set a single device to a specific level
+
|input pin 4 on
|-
 
|> 100
 
|RW
 
|special functions, having values between 101 and 255, as defined in the DFDALI manual
 
 
|-
 
|-
  
|rowspan="2"|i<address>.polling
+
|rowspan="2"|o<address>.4
|off
 
|RW
 
|polling mode is disabled
 
|-
 
|on
 
|RW
 
|polling mode is enabled
 
|-
 
 
 
|rowspan="2"|i<address>.test
 
 
|0
 
|0
 
|RW
 
|RW
|test button not pressed
+
|LED 4 off
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
|test button pressed
+
|LED 4 on
 
|-
 
|-
 +
|}
  
|rowspan="4"|i<address>.dali
+
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
|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
 
|-
 
  
|rowspan="2"|i<address>.1
+
=== DF8IL ===
|fault
+
The DF8IL is an input/output module with 8 digital inputs and 8 digital open collector outputs for LEDs.
|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:
+
It uses 4 input and 4 output addresses in the DOMINO bus.
*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.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,359: Line 2,334:
 
|-
 
|-
  
|rowspan="3"|o<address>.1
+
|rowspan="2"|i<address>.1
|off
+
|0
|RW
+
|R
|dimmer off
+
|input pin 1 off
 +
|-
 +
|1
 +
|R
 +
|input pin 1 on
 
|-
 
|-
|1 ... 100%
+
 
|RW
+
|rowspan="2"|i<address>.2
|percent dimmer level
+
|0
 +
|R
 +
|input pin 2 off
 
|-
 
|-
|on
+
|1
|RW
+
|R
|dimmer on at last level
+
|input pin 2 on
 
|-
 
|-
  
|rowspan="2"|o<address>.2
+
|rowspan="2"|i<address>.3
 
|0
 
|0
|RW
+
|R
|output pin 1 off
+
|input pin 3 off
 
|-
 
|-
 
|1
 
|1
|RW
+
|R
|output pin 1 on
+
|input pin 3 on
 
|-
 
|-
|}
 
  
The dimmer level can be set using additional formats besides the standard percent values:
+
|rowspan="2"|i<address>.4
*absolute positive integer number between 0 and 100
+
|0
*fractional format, formatted as “n/m”, where 0 <= n <= m.
+
|R
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
+
|input pin 4 off
 
+
|-
----
+
|1
 
+
|R
=== DFTP ===
+
|input pin 4 on
The DFTP is an output module for 2 shutters.
 
 
 
It uses one output address in the DOMINO bus.
 
 
 
{| class="wikitable"
 
!ID
 
!Value
 
!R/W
 
!Description
 
 
|-
 
|-
  
|rowspan="6"|o<address>.1
+
|rowspan="2"|i<address+1>.1
|up
+
|0
|RW
+
|R
|shutter up command
+
|input pin 5 off
 
|-
 
|-
|down
+
|1
|RW
+
|R
|shutter down command
+
|input pin 5 on
 
|-
 
|-
|stop
+
 
|RW
+
|rowspan="2"|i<address+1>.2
|shutter stop command
+
|0
 +
|R
 +
|input pin 6 off
 
|-
 
|-
|unknown
+
|1
 
|R
 
|R
|unknown state
+
|input pin 6 on
 
|-
 
|-
|offup
+
 
|RW
+
|rowspan="2"|i<address+1>.3
|shutter off, up position
+
|0
 +
|R
 +
|input pin 7 off
 
|-
 
|-
|offdown
+
|1
|RW
+
|R
|shutter off, down position
+
|input pin 7 on
 
|-
 
|-
  
|rowspan="6"|o<address>.2
+
|rowspan="2"|i<address+1>.4
|up
+
|0
|RW
+
|R
|shutter up command
+
|input pin 8 off
 
|-
 
|-
|down
+
|1
|RW
+
|R
|shutter down command
+
|input pin 8 on
 
|-
 
|-
|stop
+
 
|RW
+
|rowspan="2"|i<address+2>.1
|shutter stop command
+
|0
 +
|R
 +
|LED 1 is off
 
|-
 
|-
|unknown
+
|1
 
|R
 
|R
|unknown state
+
|LED 1 is on
 
|-
 
|-
|offup
+
 
|RW
+
|rowspan="2"|i<address+2>.2
|shutter off, up position
+
|0
 +
|R
 +
|LED 2 is off
 
|-
 
|-
|offdown
+
|1
|RW
+
|R
|shutter off, down position
+
|LED 2 is on
 
|-
 
|-
  
|}
+
|rowspan="2"|i<address+2>.3
 +
|0
 +
|R
 +
|LED 3 is off
 +
|-
 +
|1
 +
|R
 +
|LED 3 is on
 +
|-
  
----
+
|rowspan="2"|i<address+2>.4
 
+
|0
=== DFTP/I ===
+
|R
The DFTP is an input/output module for 2 shutters and 4 generic inputs.
+
|LED 4 is off
 
+
|-
It uses one input and one output address in the DOMINO bus.
+
|1
 
+
|R
{| class="wikitable"
+
|LED 4 is on
!ID
 
!Value
 
!R/W
 
!Description
 
 
|-
 
|-
  
|rowspan="2"|i<address>.1
+
|rowspan="2"|i<address+3>.1
 
|0
 
|0
 
|R
 
|R
|input pin 1 off
+
|LED 5 is off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
|input pin 1 on
+
|LED 5 is on
 
|-
 
|-
  
|rowspan="6"|o<address>.1
+
|rowspan="2"|i<address+3>.2
|up
+
|0
|RW
+
|R
|shutter up command
+
|LED 6 is off
 
|-
 
|-
|down
+
|1
|RW
+
|R
|shutter down command
+
|LED 6 is on
 
|-
 
|-
|stop
+
 
|RW
+
|rowspan="2"|i<address+3>.3
|shutter stop command
+
|0
 +
|R
 +
|LED 7 is off
 
|-
 
|-
|unknown
+
|1
 
|R
 
|R
|unknown state
+
|LED 7 is on
|-
 
|offup
 
|RW
 
|shutter off, up position
 
|-
 
|offdown
 
|RW
 
|shutter off, down position
 
 
|-
 
|-
  
|rowspan="2"|i<address>.2
+
|rowspan="2"|i<address+3>.4
 
|0
 
|0
 
|R
 
|R
|input pin 2 off
+
|LED 8 is off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
|input pin 2 on
+
|LED 8 is on
 
|-
 
|-
  
|rowspan="6"|o<address>.2
+
|rowspan="2"|v<address+2>.1
|up
+
|0
 
|RW
 
|RW
|shutter up command
+
|LED 1 is off
 
|-
 
|-
|down
+
|1
 
|RW
 
|RW
|shutter down command
+
|LED 1 is on
 
|-
 
|-
|stop
+
 
 +
|rowspan="2"|v<address+2>.2
 +
|0
 
|RW
 
|RW
|shutter stop command
+
|LED 2 is off
 
|-
 
|-
|unknown
+
|1
|R
+
|RW
|unknown state
+
|LED 2 is on
 
|-
 
|-
|offup
+
 
 +
|rowspan="2"|v<address+2>.3
 +
|0
 
|RW
 
|RW
|shutter off, up position
+
|LED 3 is off
 
|-
 
|-
|offdown
+
|1
 
|RW
 
|RW
|shutter off, down position
+
|LED 3 is on
 
|-
 
|-
  
|rowspan="2"|i<address>.3
+
|rowspan="2"|v<address+2>.4
 
|0
 
|0
|R
+
|RW
|input pin 3 off
+
|LED 4 is off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|input pin 3 on
+
|LED 4 is on
 
|-
 
|-
  
|rowspan="2"|i<address>.4
+
|rowspan="2"|v<address+3>.1
 
|0
 
|0
|R
+
|RW
|input pin 4 off
+
|LED 5 is off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|input pin 4 on
+
|LED 5 is on
 +
|-
 +
 
 +
|rowspan="2"|v<address+3>.2
 +
|0
 +
|RW
 +
|LED 6 is off
 +
|-
 +
|1
 +
|RW
 +
|LED 6 is on
 +
|-
 +
 
 +
|rowspan="2"|v<address+3>.3
 +
|0
 +
|RW
 +
|LED 7 is off
 +
|-
 +
|1
 +
|RW
 +
|LED 7 is on
 +
|-
 +
 
 +
|rowspan="2"|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.
 +
 +
{{tip|Note that the first two output addresses are reserved and should not be used. Use address + 2 and address + 3 to control the LEDs.}}
  
 
----
 
----
  
=== DFTR ===
+
=== DFIGLASS ===
The DFTR is an output module with 1 shutter output and 1 relay output.
+
The DFIGLASS is an input/output module with 6 touch buttons with addressable LEDs and a buzzer for audio feedback.
  
It uses one address in the DOMINO bus.
+
It uses 1 input and 1 output addresses in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,579: Line 2,594:
 
|-
 
|-
  
|rowspan="5"|o<address>.1
+
|rowspan="2"|i<address>.1
|up
+
|0
 +
|R
 +
|button 1 off
 +
|-
 +
|1
 
|R
 
|R
|shutter up
+
|button 1 on
 
|-
 
|-
|down
+
 
 +
|rowspan="2"|i<address>.2
 +
|0
 
|R
 
|R
|shutter down
+
|button 2 off
 
|-
 
|-
|unknown
+
|1
 
|R
 
|R
|unknown state
+
|button 2 on
 
|-
 
|-
|offup
+
 
 +
|rowspan="2"|i<address>.3
 +
|0
 
|R
 
|R
|shutter offup
+
|button 3 off
 
|-
 
|-
|offdown
+
|1
 
|R
 
|R
|shutter offdown
+
|button 3 on
 
|-
 
|-
  
|rowspan="2"|o<address>.2
+
|rowspan="2"|i<address>.4
 
|0
 
|0
 
|R
 
|R
|output pin 2 off
+
|button 4 off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
|output pin 2 on
+
|button 4 on
 
|-
 
|-
  
|}
+
|rowspan="2"|i<address>.5
 
+
|0
----
+
|R
 
+
|button 5 off
=== DF4IL ===
+
|-
The DF4IL is an input/output module with 4 digital inputs and 4 digital open collector outputs for LEDs.
+
|1
 
+
|R
It uses one input and one output address in the DOMINO bus.
+
|button 5 on
 
 
{| class="wikitable"
 
!ID
 
!Value
 
!R/W
 
!Description
 
 
|-
 
|-
  
|rowspan="2"|i<address>.1
+
|rowspan="2"|i<address>.6
 
|0
 
|0
 
|R
 
|R
|input pin 1 off
+
|button 6 off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
|input pin 1 on
+
|button 6 on
 
|-
 
|-
  
|rowspan="2"|o<address>.1
+
|rowspan="2"|i<address>.fault
 
|0
 
|0
|RW
+
|R
|LED 1 off
+
|no fault
 
|-
 
|-
 
|1
 
|1
|RW
+
|R
|LED 1 on
+
|touch keypad fault
 
|-
 
|-
  
|rowspan="2"|i<address>.2
+
|rowspan="2"|i<address>.led.1
 
|0
 
|0
|R
+
|RW
|input pin 2 off
+
|led 1 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|input pin 2 on
+
|led 1 on
 
|-
 
|-
  
|rowspan="2"|o<address>.2
+
|rowspan="2"|i<address>.led.2
 
|0
 
|0
 
|RW
 
|RW
|LED 2 off
+
|led 2 off
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
|LED 2 on
+
|led 2 on
 
|-
 
|-
  
|rowspan="2"|i<address>.3
+
|rowspan="2"|i<address>.led.3
 
|0
 
|0
|R
+
|RW
|input pin 3 off
+
|led 3 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|input pin 3 on
+
|led 3 on
 
|-
 
|-
  
|rowspan="2"|o<address>.3
+
|rowspan="2"|i<address>.led.4
 
|0
 
|0
 
|RW
 
|RW
|LED 3 off
+
|led 4 off
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
|LED 3 on
+
|led 4 on
 
|-
 
|-
  
|rowspan="2"|i<address>.4
+
|rowspan="2"|i<address>.led.5
 
|0
 
|0
|R
+
|RW
|input pin 4 off
+
|led 5 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|input pin 4 on
+
|led 5 on
 
|-
 
|-
  
|rowspan="2"|o<address>.4
+
|rowspan="2"|i<address>.led.6
 
|0
 
|0
 
|RW
 
|RW
|LED 4 off
+
|led 6 off
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
|LED 4 on
+
|led 6 on
 
|-
 
|-
|}
 
  
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
+
|rowspan="2"|i<address>.backlight
 +
|0
 +
|RW
 +
|backlight off
 +
|-
 +
|1
 +
|RW
 +
|backlight on
 +
|-
 +
 
 +
|rowspan="2"|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.
  
 
----
 
----
  
=== DF8IL ===
+
=== DF4I/V ===
The DF8IL is an input/output module with 8 digital inputs and 8 digital open collector outputs for LEDs.
+
The DF4I/V is an input/output module with 4 digital inputs and 12 digital virtual outputs.
  
It uses 4 input and 4 output addresses in the DOMINO bus.
+
It uses four consecutive addresses in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,764: Line 2,802:
 
|-
 
|-
  
|rowspan="2"|i<address+1>.1
+
|rowspan="2"|v<address+1>.1
 
|0
 
|0
|R
+
|RW
|input pin 5 off
+
|virtual pin 1 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|input pin 5 on
+
|virtual pin 1 on
 
|-
 
|-
  
|rowspan="2"|i<address+1>.2
+
|rowspan="2"|v<address+1>.2
 
|0
 
|0
|R
+
|RW
|input pin 6 off
+
|virtual pin 2 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|input pin 6 on
+
|virtual pin 2 on
 
|-
 
|-
  
|rowspan="2"|i<address+1>.3
+
|rowspan="2"|v<address+1>.3
 
|0
 
|0
|R
+
|RW
|input pin 7 off
+
|virtual pin 3 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|input pin 7 on
+
|virtual pin 3 on
 
|-
 
|-
  
|rowspan="2"|i<address+1>.4
+
|rowspan="2"|v<address+1>.4
 
|0
 
|0
|R
+
|RW
|input pin 8 off
+
|virtual pin 4 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|input pin 8 on
+
|virtual pin 4 on
 
|-
 
|-
  
|rowspan="2"|i<address+2>.1
+
|rowspan="2"|v<address+2>.1
 
|0
 
|0
|R
+
|RW
|LED 1 is off
+
|virtual pin 1 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|LED 1 is on
+
|virtual pin 1 on
 
|-
 
|-
  
|rowspan="2"|i<address+2>.2
+
|rowspan="2"|v<address+2>.2
 
|0
 
|0
|R
+
|RW
|LED 2 is off
+
|virtual pin 2 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|LED 2 is on
+
|virtual pin 2 on
 
|-
 
|-
  
|rowspan="2"|i<address+2>.3
+
|rowspan="2"|v<address+2>.3
 
|0
 
|0
|R
+
|RW
|LED 3 is off
+
|virtual pin 3 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|LED 3 is on
+
|virtual pin 3 on
 
|-
 
|-
  
|rowspan="2"|i<address+2>.4
+
|rowspan="2"|v<address+2>.4
 
|0
 
|0
|R
+
|RW
|LED 4 is off
+
|virtual pin 4 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|LED 4 is on
+
|virtual pin 4 on
 
|-
 
|-
  
|rowspan="2"|i<address+3>.1
+
|rowspan="2"|v<address+3>.1
 
|0
 
|0
|R
+
|RW
|LED 5 is off
+
|virtual pin 1 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|LED 5 is on
+
|virtual pin 1 on
 
|-
 
|-
  
|rowspan="2"|i<address+3>.2
+
|rowspan="2"|v<address+3>.2
 
|0
 
|0
|R
+
|RW
|LED 6 is off
+
|virtual pin 2 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|LED 6 is on
+
|virtual pin 2 on
 
|-
 
|-
  
|rowspan="2"|i<address+3>.3
+
|rowspan="2"|v<address+3>.3
 
|0
 
|0
|R
+
|RW
|LED 7 is off
+
|virtual pin 3 off
 
|-
 
|-
 
|1
 
|1
|R
+
|RW
|LED 7 is on
+
|virtual pin 3 on
 
|-
 
|-
  
|rowspan="2"|i<address+3>.4
+
|rowspan="2"|v<address+3>.4
|0
 
|R
 
|LED 8 is off
 
|-
 
|1
 
|R
 
|LED 8 is on
 
|-
 
 
 
|rowspan="2"|v<address+2>.1
 
 
|0
 
|0
 
|RW
 
|RW
|LED 1 is off
+
|virtual pin 4 off
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
|LED 1 is on
+
|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.
  
|rowspan="2"|v<address+2>.2
+
{| class="wikitable"
|0
+
!ID
|RW
+
!Value
|LED 2 is off
+
!R/W
 +
!Description
 
|-
 
|-
|1
+
 
|RW
+
|i<address>
|LED 2 is on
+
|0...1000
 +
|R
 +
|input voltage in Volt/100
 
|-
 
|-
  
|rowspan="2"|v<address+2>.3
+
|i<address+1>
|0
+
|0...1000
|RW
+
|R
|LED 3 is off
+
|input voltage in Volt/100
 +
|-
 +
|}
 +
 
 +
----
 +
 
 +
=== 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.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
|1
+
 
|RW
+
|i<address>
|LED 3 is on
+
|0...1023
 +
|R
 +
|lux level (raw level, not translated to the lux range)
 
|-
 
|-
  
|rowspan="2"|v<address+2>.4
+
|rowspan="2"|i<address + 1>.1
 
|0
 
|0
|RW
+
|R
|LED 4 is off
+
|input IN1 off
 
|-
 
|-
 
|1
 
|1
|RW
+
|R
|LED 4 is on
+
|input IN1 on
 
|-
 
|-
  
|rowspan="2"|v<address+3>.1
+
|rowspan="2"|i<address + 1>.2
 
|0
 
|0
|RW
+
|R
|LED 5 is off
+
|input IN2 off
 
|-
 
|-
 
|1
 
|1
|RW
+
|R
|LED 5 is on
+
|input IN2 on
 
|-
 
|-
  
|rowspan="2"|v<address+3>.2
+
|rowspan="2"|i<address + 1>.3
 
|0
 
|0
|RW
+
|R
|LED 6 is off
+
|presence with delay is off
 
|-
 
|-
 
|1
 
|1
|RW
+
|R
|LED 6 is on
+
|presence with delay is on
|-
 
 
 
|rowspan="2"|v<address+3>.3
 
|0
 
|RW
 
|LED 7 is off
 
|-
 
|1
 
|RW
 
|LED 7 is on
 
|-
 
 
 
|rowspan="2"|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.
 
 
{{tip|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 ===
+
=== DFLUX, DFSUN ===
The DFIGLASS is an input/output module with 6 touch buttons with addressable LEDs and a buzzer for audio feedback.
+
The DFLUX and DFSUN are input modules with 1 analog light sensor.
  
It uses 1 input and 1 output addresses in the DOMINO bus.
+
They use one input address in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,984: Line 3,018:
 
|-
 
|-
  
|rowspan="2"|i<address>.1
+
|i<address>
|0
+
|0...1023
 
|R
 
|R
|button 1 off
+
|lux level (raw level, not translated to the lux range)
|-
 
|1
 
|R
 
|button 1 on
 
 
|-
 
|-
 +
|}
  
|rowspan="2"|i<address>.2
+
----
|0
+
 
 +
=== 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.
 +
}}
 +
 
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 
 +
|rowspan="2"|i<address>.mode
 +
|winter
 
|R
 
|R
|button 2 off
+
|winter mode
 
|-
 
|-
|1
+
|summer
 
|R
 
|R
|button 2 on
+
|summer mode
 
|-
 
|-
  
|rowspan="2"|i<address>.3
+
|rowspan="4"|i<address>.fan
|0
+
|min
 
|R
 
|R
|button 3 off
+
|min fan speed
 
|-
 
|-
|1
+
|med
 
|R
 
|R
|button 3 on
+
|medium fan speed
 
|-
 
|-
 
+
|max
|rowspan="2"|i<address>.4
 
|0
 
 
|R
 
|R
|button 4 off
+
|max fan speed
 
|-
 
|-
|1
+
|off
 
|R
 
|R
|button 4 on
+
|fan off
 
|-
 
|-
  
|rowspan="2"|i<address>.5
+
|rowspan="2"|i<address>.fan.mode
|0
+
|man
 +
|R
 +
|manual fan mode
 +
|-
 +
|auto
 
|R
 
|R
|button 5 off
+
|auto fan mode
 
|-
 
|-
 +
 +
|rowspan="5"|i<address>.setpoint
 
|1
 
|1
 
|R
 
|R
|button 5 on
+
|setpoint 1
 
|-
 
|-
 
+
|2
|rowspan="2"|i<address>.6
 
|0
 
 
|R
 
|R
|button 6 off
+
|setpoint 2
 
|-
 
|-
|1
+
|3
 
|R
 
|R
|button 6 on
+
|setpoint 3
 
|-
 
|-
 
+
|off
|rowspan="2"|i<address>.fault
 
|0
 
 
|R
 
|R
|no fault
+
|off
 
|-
 
|-
|1
+
|man
 
|R
 
|R
|touch keypad fault
+
|manual setpoint
 
|-
 
|-
  
|rowspan="2"|i<address>.led.1
+
|rowspan="2"|i<address>.setpoint.mode
|0
+
|man
|RW
+
|R
|led 1 off
+
|manual setpoint mode
 
|-
 
|-
|1
+
|auto
|RW
+
|R
|led 1 on
+
|auto setpoint mode
 
|-
 
|-
  
|rowspan="2"|i<address>.led.2
+
|rowspan="2"|i<address>.temp
|0
+
|<temp>
|RW
+
|R
|led 2 off
+
|temperature value (in C/10)
 
|-
 
|-
|1
+
|fault
|RW
+
|R
|led 2 on
+
|temperature sensor fault
 
|-
 
|-
  
|rowspan="2"|i<address>.led.3
+
|rowspan="3"|i<address>.status
|0
+
|off
|RW
+
|R
|led 3 off
+
|off
 +
|-
 +
|cooling
 +
|R
 +
|cooling status mode
 
|-
 
|-
|1
+
|heating
|RW
+
|R
|led 3 on
+
|heating status mode
 
|-
 
|-
  
|rowspan="2"|i<address>.led.4
+
|rowspan="2"|o<address>.mode
|0
+
|winter
 
|RW
 
|RW
|led 4 off
+
|winter mode
 
|-
 
|-
|1
+
|summer
 
|RW
 
|RW
|led 4 on
+
|summer mode
 
|-
 
|-
  
|rowspan="2"|i<address>.led.5
+
|rowspan="4"|o<address>.fan
|0
+
|min
 
|RW
 
|RW
|led 5 off
+
|min fan speed
 
|-
 
|-
|1
+
|med
 
|RW
 
|RW
|led 5 on
+
|medium fan speed
 
|-
 
|-
 
+
|max
|rowspan="2"|i<address>.led.6
 
|0
 
 
|RW
 
|RW
|led 6 off
+
|max fan speed
 
|-
 
|-
|1
+
|off
 
|RW
 
|RW
|led 6 on
+
|fan off
 
|-
 
|-
  
|rowspan="2"|i<address>.backlight
+
|rowspan="2"|o<address>.fan.mode
|0
+
|man
 
|RW
 
|RW
|backlight off
+
|manual fan mode
 
|-
 
|-
|1
+
|auto
 
|RW
 
|RW
|backlight on
+
|auto fan mode
 
|-
 
|-
  
|rowspan="2"|i<address>.buzzer
+
|rowspan="5"|o<address>.setpoint
|0
+
|1
 
|RW
 
|RW
|buzzer disabled
+
|setpoint 1
 
|-
 
|-
|1
+
|2
 
|RW
 
|RW
|buzzer enabled
+
|setpoint 2
 
|-
 
|-
 
+
|3
|}
+
|RW
 
+
|setpoint 3
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.
 
 
 
{| class="wikitable"
 
!ID
 
!Value
 
!R/W
 
!Description
 
 
|-
 
|-
 
|rowspan="2"|i<address>.1
 
 
|0
 
|0
|R
+
|RW
|input pin 1 off
+
|setpoint off
 
|-
 
|-
|1
+
|man
|R
+
|RW
|input pin 1 on
+
|manual setpoint
 
|-
 
|-
  
|rowspan="2"|i<address>.2
+
|rowspan="3"|o<address>.setpoint.mode
|0
+
|man
|R
+
|RW
|input pin 2 off
+
|manual setpoint mode
 
|-
 
|-
|1
+
|auto
|R
+
|RW
|input pin 2 on
+
|auto setpoint mode
 +
|-
 +
|off
 +
|RW
 +
|off mode
 
|-
 
|-
  
|rowspan="2"|i<address>.3
+
|o<address>.setpoint.temp.1
|0
+
|<temp>
|R
+
|RW
|input pin 3 off
+
|temperature setpoint 1 value (in C/10)
|-
 
|1
 
|R
 
|input pin 3 on
 
 
|-
 
|-
  
|rowspan="2"|i<address>.4
+
|o<address>.setpoint.temp.2
|0
+
|<temp>
|R
+
|RW
|input pin 4 off
+
|temperature setpoint 2 value (in C/10)
|-
 
|1
 
|R
 
|input pin 4 on
 
 
|-
 
|-
  
|rowspan="2"|v<address+1>.1
+
|o<address>.setpoint.temp.3
|0
+
|<temp>
 
|RW
 
|RW
|virtual pin 1 off
+
|temperature setpoint 3 value (in C/10)
 
|-
 
|-
|1
+
 
 +
|o<address>.setpoint.temp.man
 +
|<temp>
 
|RW
 
|RW
|virtual pin 1 on
+
|temperature manual setpoint value (in C/10)
 
|-
 
|-
  
|rowspan="2"|v<address+1>.2
+
|o<address>.program.summer<br/>o<address>.program.winter
|0
+
|refresh
 
|RW
 
|RW
|virtual pin 2 off
+
|forces to daily summer/winter program for all days of the week
|-
 
|1
 
|RW
 
|virtual pin 2 on
 
 
|-
 
|-
  
|rowspan="2"|v<address+1>.3
+
|rowspan="2"|o<address>.program.summer.<day><br/>o<address>.program.winter.<day>
|0
+
|refresh
 
|RW
 
|RW
|virtual pin 3 off
+
|forces to daily summer/winter program for the reported day (mon:1, sun:7)
 
|-
 
|-
|1
+
|<s0>...<s47>
 
|RW
 
|RW
|virtual pin 3 on
+
|48 character represents the daily setpoint program divided in time slots of 30 minutes
 
|-
 
|-
  
|rowspan="2"|v<address+1>.4
+
|}
|0
+
 
|RW
+
----
|virtual pin 4 off
 
|-
 
|1
 
|RW
 
|virtual pin 4 on
 
|-
 
  
|rowspan="2"|v<address+2>.1
+
=== DFTZ ===
|0
+
The DFTZ is an input/output temperature sensor module.
|RW
 
|virtual pin 1 off
 
|-
 
|1
 
|RW
 
|virtual pin 1 on
 
|-
 
  
|rowspan="2"|v<address+2>.2
+
It uses 3 consecutive input addresses and 4 consecutive output addresses in the DOMINO bus.
|0
+
 
|RW
+
{| class="wikitable"
|virtual pin 2 off
+
!ID
|-
+
!Value
|1
+
!R/W
|RW
+
!Description
|virtual pin 2 on
 
 
|-
 
|-
  
|rowspan="2"|v<address+2>.3
+
|rowspan="2"|i<address>.mode
|0
+
|winter
|RW
+
|R
|virtual pin 3 off
+
|winter mode
 
|-
 
|-
|1
+
|summer
|RW
+
|R
|virtual pin 3 on
+
|summer mode
 
|-
 
|-
  
|rowspan="2"|v<address+2>.4
+
|rowspan="3"|i<address>.setpoint
|0
+
|comfort
|RW
+
|R
|virtual pin 4 off
+
|comfort setpoint
 
|-
 
|-
|1
+
|eco
|RW
+
|R
|virtual pin 4 on
+
|eco setpoint
 
|-
 
|-
 
+
|off
|rowspan="2"|v<address+3>.1
+
|R
|0
+
|off
|RW
+
|-
|virtual pin 1 off
+
 
 +
|rowspan="2"|i<address>.temp
 +
|<temp>
 +
|R
 +
|temperature value (in C/10)
 
|-
 
|-
|1
+
|fault
|RW
+
|R
|virtual pin 1 on
+
|temperature sensor fault
 
|-
 
|-
  
|rowspan="2"|v<address+3>.2
+
|rowspan="3"|i<address>.status
|0
+
|off
|RW
+
|R
|virtual pin 2 off
+
|off
 +
|-
 +
|cooling
 +
|R
 +
|cooling status mode
 
|-
 
|-
|1
+
|heating
|RW
+
|R
|virtual pin 2 on
+
|heating status mode
 
|-
 
|-
  
|rowspan="2"|v<address+3>.3
+
|rowspan="2"|o<address>.mode
|0
+
|winter
 
|RW
 
|RW
|virtual pin 3 off
+
|winter mode
 
|-
 
|-
|1
+
|summer
 
|RW
 
|RW
|virtual pin 3 on
+
|summer mode
 
|-
 
|-
  
|rowspan="2"|v<address+3>.4
+
|rowspan="3"|o<address>.setpoint
 +
|comfort
 +
|RW
 +
|comfort setpoint
 +
|-
 +
|eco
 +
|RW
 +
|eco setpoint
 +
|-
 
|0
 
|0
 
|RW
 
|RW
|virtual pin 4 off
+
|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)
 
|-
 
|-
|1
+
 
 +
|o<address>.setpoint.temp.limit
 +
|<temp>
 
|RW
 
|RW
|virtual pin 4 on
+
|summer/winter setpoint temperature limit (in C/10)
 
|-
 
|-
 +
 
|}
 
|}
 
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
 
  
 
----
 
----
  
=== DFAI ===
+
=== DFRHT ===
The DFAI is an input module (0-10V) with 2 analog inputs.
+
The DFRHT is a temperature and humidity sensor.
  
It uses two consecutive input addresses in the DOMINO bus.
+
It uses four consecutive input addresses and two consecutive output addresses in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,329: Line 3,375:
 
|-
 
|-
  
|i<address>
+
|i<address>.humidity
|0...1000
+
|0...100
 
|R
 
|R
|input voltage in Volt/100
+
|relative percent umidity
 
|-
 
|-
  
|i<address+1>
+
|i<address>.temp
|0...1000
+
|<temp>
 
|R
 
|R
|input voltage in Volt/100
+
|temperature value
 
|-
 
|-
|}
 
  
----
+
|i<address>.dewpoint
 +
|<temp>
 +
|R
 +
|dew point value
 +
|-
  
=== DFLUX, DFSUN ===
+
|rowspan="4"|i<address>.dewpoint.limit.1
The DFLUX and DFSUN are input modules with 1 analog light sensor.
+
|0
 
+
|R
They use one input address in the DOMINO bus.
+
|dew point is lower than limit 1
 
 
{| class="wikitable"
 
!ID
 
!Value
 
!R/W
 
!Description
 
 
|-
 
|-
 
+
|1
|i<address>
 
|0...1023
 
 
|R
 
|R
|lux level (raw level, not translated to the lux range)
+
|dew point is higher than limit 1
 
|-
 
|-
|}
+
|<temp>
 
+
|RW
----
+
|dew point limit 1
 
+
|-
=== DFCT ===
+
|off
The DFCT is an input/output temperature sensor module.
+
|RW
 +
|limit 1 not set
 +
|-
 +
 
 +
|rowspan="4"|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
 +
|-
 +
 
 +
|}
  
It uses two consecutive input addresses and five consecutive output addresses in the DOMINO bus.
+
----
  
{{note|
+
=== DFMETEO ===
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 DFMETEO is the weather sensor module.
the DFCT using the (temp) GUI objects.
 
}}
 
  
 +
It uses four consecutive input addresses and three consecutive output addresses in the DOMINO bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,383: Line 3,445:
 
|-
 
|-
  
|rowspan="2"|i<address>.mode
+
|rowspan="2"|i<address>.temp
|winter
+
|<temp>
|R
+
|RW
|winter mode
+
|temperature value (in C/10)
 
|-
 
|-
|summer
+
|off
|R
+
|RW
|summer mode
+
|limit not set
 
|-
 
|-
  
|rowspan="4"|i<address>.fan
+
|rowspan="3"|i<address>.lux
|min
+
|<lux*10>
 
|R
 
|R
|min fan speed
+
|lux level according to the DFLUX range
 +
|-
 +
|<lux>
 +
|RW
 +
|lux limit
 +
|-
 +
|0
 +
|RW
 +
|limit not set
 
|-
 
|-
|med
+
 
 +
|rowspan="3"|i<address>.wind
 +
|1 m/s /10
 
|R
 
|R
|medium fan speed
+
|wind value
 
|-
 
|-
|max
+
|m/s
|R
+
|RW
|max fan speed
+
|wind limit
 
|-
 
|-
|off
+
|0
|R
+
|RW
|fan off
+
|limit not set
 
|-
 
|-
  
|rowspan="2"|i<address>.fan.mode
+
|rowspan="2"|i<address>.rain
|man
+
|0
 
|R
 
|R
|manual fan mode
+
|no rain
 
|-
 
|-
|auto
+
|1
 
|R
 
|R
|auto fan mode
+
|rain
 
|-
 
|-
  
|rowspan="5"|i<address>.setpoint
+
|rowspan="2"|i<address>.night
 +
|0
 +
|R
 +
|day
 +
|-
 
|1
 
|1
 
|R
 
|R
|setpoint 1
+
|night
 
|-
 
|-
|2
+
 
 +
|rowspan="2"|i<address>.temp.limit
 +
|0
 
|R
 
|R
|setpoint 2
+
|measured temp is less than limit
 
|-
 
|-
|3
+
|1
 
|R
 
|R
|setpoint 3
+
|measured temp is greater than limit
 
|-
 
|-
|off
+
 
 +
|rowspan="2"|i<address>.lux.limit
 +
|0
 
|R
 
|R
|off
+
|measured lux is less than limit
 
|-
 
|-
|man
+
|1
 
|R
 
|R
|manual setpoint
+
|measured lux is greater than limit
 
|-
 
|-
  
|rowspan="2"|i<address>.setpoint.mode
+
|rowspan="2"|i<address>.wind.limit
|man
+
|0
 
|R
 
|R
|manual setpoint mode
+
|measured wind is less than limit
 
|-
 
|-
|auto
+
|1
 
|R
 
|R
|auto setpoint mode
+
|measured wind is greater than limit
 
|-
 
|-
  
|rowspan="2"|i<address>.temp
+
|rowspan="2"|i<address>.light.south
|<temp>
+
|0
 
|R
 
|R
|temperature value (in C/10)
+
|light is not coming from south
 
|-
 
|-
|fault
+
|1
 
|R
 
|R
|temperature sensor fault
+
|light is coming from south
 
|-
 
|-
  
|rowspan="3"|i<address>.status
+
|rowspan="2"|i<address>.light.west
|off
+
|0
 +
|R
 +
|light is not coming from west
 +
|-
 +
|1
 
|R
 
|R
|off
+
|light is coming from west
 
|-
 
|-
|cooling
+
 
 +
|rowspan="2"|i<address>.light.east
 +
|0
 
|R
 
|R
|cooling status mode
+
|light is not coming from east
 
|-
 
|-
|heating
+
|1
 
|R
 
|R
|heating status mode
+
|light is coming from east
 
|-
 
|-
  
|rowspan="2"|o<address>.mode
+
|rowspan="2"|i<address>.fault
|winter
+
|0
|RW
+
|R
|winter mode
+
|sensor not fault
 
|-
 
|-
|summer
+
|1
|RW
+
|R
|summer mode
+
|sensor fault
 
|-
 
|-
 +
|}
  
|rowspan="4"|o<address>.fan
+
----
|min
+
 
|RW
+
=== DFCC ===
|min fan speed
+
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.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
|med
+
 
|RW
+
|energy.<n>.power.real
|medium fan speed
+
|0...65535
 +
|R
 +
|real power (Watt)
 
|-
 
|-
|max
+
 
|RW
+
|energy.<n>.power.reactive
|max fan speed
+
| -32768...+32767
 +
|R
 +
|reactive power (var)
 
|-
 
|-
|off
+
 
|RW
+
|energy.<n>.power.apparent
|fan off
+
| -32768...+32767
 +
|R
 +
|apparent power (VA)
 
|-
 
|-
  
|rowspan="2"|o<address>.fan.mode
+
|energy.<n>.power.realavg
|man
+
|0...65535
|RW
+
|R
|manual fan mode
+
|average real power (Watt)
|-
 
|auto
 
|RW
 
|auto fan mode
 
 
|-
 
|-
  
|rowspan="5"|o<address>.setpoint
+
|energy.<n>.power.reactiveavg
|1
+
| -32768...+32767
|RW
+
|R
|setpoint 1
+
|average reactive power (var)
 
|-
 
|-
|2
+
 
|RW
+
|energy.<n>.cos
|setpoint 2
+
| -1000...+1000
|-
+
|R
|3
+
|cos(φ) * 1000
|RW
 
|setpoint 3
 
 
|-
 
|-
 +
 +
|rowspan="2"|energy.<n>.load.1
 
|0
 
|0
|RW
+
|R
|setpoint off
+
|load 1 disabled
 
|-
 
|-
|man
+
|1
|RW
+
|R
|manual setpoint
+
|load 1 enabled
 
|-
 
|-
  
|o<address>.setpoint.temp.1
+
|rowspan="2"|energy.<n>.load.2
|<temp>
+
|0
|RW
+
|R
|temperature setpoint 1 value (in C/10)
+
|load 2 disabled
 +
|-
 +
|1
 +
|R
 +
|load 2 enabled
 
|-
 
|-
  
|o<address>.setpoint.temp.2
+
|rowspan="2"|energy.<n>.load.3
|<temp>
+
|0
|RW
+
|R
|temperature setpoint 2 value (in C/10)
+
|load 3 disabled
 +
|-
 +
|1
 +
|R
 +
|load 3 enabled
 
|-
 
|-
  
|o<address>.setpoint.temp.3
+
|rowspan="2"|energy.<n>.load.4
|<temp>
+
|0
|RW
+
|R
|temperature setpoint 3 value (in C/10)
+
|load 4 disabled
 
|-
 
|-
 
+
|1
|o<address>.setpoint.temp.man
+
|R
|<temp>
+
|load 4 enabled
|RW
 
|temperature manual setpoint value (in C/10)
 
 
|-
 
|-
  
|o<address>.program.summer<br/>o<address>.program.winter
+
|rowspan="2"|energy.<n>.load.5
|refresh
+
|0
|RW
+
|R
|forces to daily summer/winter program for all days of the week
+
|load 5 disabled
 
|-
 
|-
 
+
|1
|rowspan="2"|o<address>.program.summer.<day><br/>o<address>.program.winter.<day>
+
|R
|refresh
+
|load 5 enabled
|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
 
 
|-
 
|-
  
|}
+
|rowspan="2"|energy.<n>.load.6
 
+
|0
----
 
 
 
=== 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.
 
 
 
{| class="wikitable"
 
!ID
 
!Value
 
!R/W
 
!Description
 
|-
 
 
 
|rowspan="2"|i<address>.mode
 
|winter
 
 
|R
 
|R
|winter mode
+
|load 6 disabled
 
|-
 
|-
|summer
+
|1
 
|R
 
|R
|summer mode
+
|load 6 enabled
 
|-
 
|-
  
|rowspan="3"|i<address>.setpoint
+
|rowspan="2"|energy.<n>.load.7
|comfort
+
|0
 
|R
 
|R
|comfort setpoint
+
|load 7 disabled
 
|-
 
|-
|eco
+
|1
 
|R
 
|R
|eco setpoint
+
|load 7 enabled
|-
 
|off
 
|R
 
|off
 
 
|-
 
|-
  
|rowspan="2"|i<address>.temp
+
|rowspan="2"|energy.<n>.load.8
|<temp>
+
|0
 
|R
 
|R
|temperature value (in C/10)
+
|load 8 disabled
 
|-
 
|-
|fault
+
|1
 
|R
 
|R
|temperature sensor fault
+
|load 8 enabled
 
|-
 
|-
  
|rowspan="3"|i<address>.status
+
|}
|off
+
 
|R
+
----
|off
+
 
 +
=== 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.}}
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
|cooling
+
 
 +
|i<address>.v12
 +
|[V]
 
|R
 
|R
|cooling status mode
+
|chained voltage phase 1-2
 
|-
 
|-
|heating
+
 
 +
|i<address>.v23
 +
|[V]
 
|R
 
|R
|heating status mode
+
|chained voltage phase 2-3
 
|-
 
|-
  
|rowspan="2"|o<address>.mode
+
|i<address>.v31
|winter
+
|[V]
|RW
+
|R
|winter mode
+
|chained voltage phase 3-1
 
|-
 
|-
|summer
+
 
|RW
+
|i<address>.vtm
|summer mode
+
|[V]
 +
|R
 +
|average chained voltage
 
|-
 
|-
  
|rowspan="3"|o<address>.setpoint
+
|i<address>.i1
|comfort
+
|[A]
|RW
+
|R
|comfort setpoint
+
|current phase 1
 
|-
 
|-
|eco
+
 
|RW
+
|i<address>.i2
|eco setpoint
+
|[A]
 +
|R
 +
|current phase 2
 
|-
 
|-
|0
+
 
|RW
+
|i<address>.i3
|off
+
|[A]
 +
|R
 +
|current phase 3
 
|-
 
|-
  
|o<address>.setpoint.temp.comfort
+
|i<address>.itm
|<temp>
+
|[A]
|RW
+
|R
|comfort setpoint value (in C/10)
+
|average current
 
|-
 
|-
  
|o<address>.setpoint.temp.eco
+
|i<address>.ptot
|<temp>
+
|[W]
|RW
+
|R
|eco setpoint value (in C/10)
+
|total active power
 
|-
 
|-
  
|o<address>.setpoint.temp.limit
+
|i<address>.ptotk
|<temp>
+
|[kW]
|RW
+
|R
|summer/winter setpoint temperature limit (in C/10)
+
|total active power
 
|-
 
|-
  
|}
+
|i<address>.qtot
 +
|[W]
 +
|R
 +
|total reactive power
 +
|-
  
----
+
|i<address>.qtotk
 +
|[kW]
 +
|R
 +
|total reactive power
 +
|-
  
=== DFRHT ===
+
|i<address>.pf
The DFRHT is a temperature and humidity sensor.
+
|[pf]
 +
|R
 +
|total power factor
 +
|-
  
It uses four consecutive input addresses and two consecutive output addresses in the DOMINO bus.
+
|i<address>.frequency
 +
|[Hz]
 +
|R
 +
|frequency
 +
|-
  
{| class="wikitable"
+
|i<address>.v1n
!ID
+
|[V]
!Value
+
|R
!R/W
+
|voltage phase 1
!Description
 
 
|-
 
|-
  
|i<address>.humidity
+
|i<address>.v2n
|0...100
+
|[V]
 
|R
 
|R
|relative percent umidity
+
|voltage phase 2
 
|-
 
|-
  
|i<address>.temp
+
|i<address>.v3n
|<temp>
+
|[V]
 
|R
 
|R
|temperature value
+
|voltage phase 3
 
|-
 
|-
  
|i<address>.dewpoint
+
|i<address>.p1
|<temp>
+
|[W]
 
|R
 
|R
|dew point value
+
|active power phase 1
 
|-
 
|-
  
|rowspan="4"|i<address>.dewpoint.limit.1
+
|i<address>.p1k
|0
+
|[kW]
 
|R
 
|R
|dew point is lower than limit 1
+
|active power phase 1
 
|-
 
|-
|1
+
 
 +
|i<address>.p2
 +
|[W]
 
|R
 
|R
|dew point is higher than limit 1
+
|active power phase 2
 
|-
 
|-
|<temp>
+
 
|RW
+
|i<address>.p2k
|dew point limit 1
+
|[kW]
 +
|R
 +
|active power phase 2
 
|-
 
|-
|off
+
 
|RW
+
|i<address>.p3
|limit 1 not set
+
|[W]
 +
|R
 +
|active power phase 3
 
|-
 
|-
  
|rowspan="4"|i<address>.dewpoint.limit.2
+
|i<address>.p3k
|0
+
|[kW]
 
|R
 
|R
|dew point is lower than limit 2
+
|active power phase 3
 
|-
 
|-
|1
+
 
 +
|i<address>.q1
 +
|[W]
 
|R
 
|R
|dew point is higher than limit 2
+
|reactive power phase 1
 
|-
 
|-
|<temp>
+
 
|RW
+
|i<address>.q1k
|dew point limit 2
+
|[kW]
 +
|R
 +
|reactive power phase 1
 
|-
 
|-
|off
+
 
|RW
+
|i<address>.q2
|limit 2 not set
+
|[W]
 +
|R
 +
|reactive power phase 2
 
|-
 
|-
  
|}
+
|i<address>.q2k
 +
|[kW]
 +
|R
 +
|reactive power phase 2
 +
|-
  
----
+
|i<address>.q3
 +
|[W]
 +
|R
 +
|reactive power phase 3
 +
|-
  
=== DFMETEO ===
+
|i<address>.q3k
The DFMETEO is the weather sensor module.
+
|[kW]
 +
|R
 +
|reactive power phase 3
 +
|-
  
It uses four consecutive input addresses and three consecutive output addresses in the DOMINO bus.
+
|i<address>.pf1
 +
|[pf]
 +
|R
 +
|power factor phase 1
 +
|-
  
{| class="wikitable"
+
|i<address>.pf2
!ID
+
|[pf]
!Value
+
|R
!R/W
+
|power factor phase 2
!Description
 
 
|-
 
|-
  
|rowspan="2"|i<address>.temp
+
|i<address>.pf3
|<temp>
+
|[pf]
|RW
+
|R
|temperature value (in C/10)
+
|power factor phase 3
 
|-
 
|-
|off
+
 
|RW
+
|i<address>.s1
|limit not set
+
|[VA]
 +
|R
 +
|apparent power phase 1
 
|-
 
|-
  
|rowspan="3"|i<address>.lux
+
|i<address>.s1k
|<lux*10>
+
|[kVA]
 
|R
 
|R
|lux level according to the DFLUX range
+
|apparent power phase 1
 
|-
 
|-
|<lux>
+
 
|RW
+
|i<address>.s2
|lux limit
+
|[VA]
 +
|R
 +
|apparent power phase 2
 
|-
 
|-
|0
+
 
|RW
+
|i<address>.s2k
|limit not set
+
|[kVA]
 +
|R
 +
|apparent power phase 2
 
|-
 
|-
  
|rowspan="3"|i<address>.wind
+
|i<address>.s3
|1 m/s /10
+
|[VA]
 
|R
 
|R
|wind value
+
|apparent power phase 3
 
|-
 
|-
|m/s
+
 
|RW
+
|i<address>.s3k
|wind limit
+
|[kVA]
|-
+
|R
|0
+
|apparent power phase 3
|RW
 
|limit not set
 
 
|-
 
|-
  
|rowspan="2"|i<address>.rain
+
|i<address>.stot
|0
+
|[VA]
 
|R
 
|R
|no rain
+
|total apparent power
 
|-
 
|-
|1
+
 
 +
|i<address>.hours
 +
|[hours]
 
|R
 
|R
|rain
+
|counter
 
|-
 
|-
  
|rowspan="2"|i<address>.night
+
|i<address>.temperature
|0
+
|[°C]
 
|R
 
|R
|day
+
|temperature
 
|-
 
|-
|1
+
 
 +
|i<address>.energy.active
 +
|[Wh]
 
|R
 
|R
|night
+
|positive active energy
 
|-
 
|-
  
|rowspan="2"|i<address>.temp.limit
+
|i<address>.energy.activeneg
|0
+
|[Wh]
 
|R
 
|R
|measured temp is less than limit
+
|negative active energy
 
|-
 
|-
|1
+
 
 +
|i<address>.energy.reactive
 +
|[VARh]
 
|R
 
|R
|measured temp is greater than limit
+
|positive reactive energy
 
|-
 
|-
  
|rowspan="2"|i<address>.lux.limit
+
|i<address>.energy.reactiveneg
|0
+
|[VARh]
 
|R
 
|R
|measured lux is less than limit
+
|negative reactive energy
 
|-
 
|-
|1
+
 
 +
|i<address>.pm
 +
|[W]
 
|R
 
|R
|measured lux is greater than limit
+
|average positive active power
 
|-
 
|-
  
|rowspan="2"|i<address>.wind.limit
+
|i<address>.qm
|0
+
|[VAR]
 
|R
 
|R
|measured wind is less than limit
+
|average positive reactive power
 
|-
 
|-
 +
 +
|rowspan="2"|i<address>.reset.energy
 
|1
 
|1
|R
+
|W
|measured wind is greater than limit
+
|energy counter reset
 
|-
 
|-
 
|rowspan="2"|i<address>.light.south
 
 
|0
 
|0
|R
+
|W
|light is not coming from south
+
|
|-
 
|1
 
|R
 
|light is coming from south
 
 
|-
 
|-
  
|rowspan="2"|i<address>.light.west
+
|rowspan="2"|i<address>.reset.hours
|0
 
|R
 
|light is not coming from west
 
|-
 
 
|1
 
|1
|R
+
|W
|light is coming from west
+
|counter reset
 
|-
 
|-
 
|rowspan="2"|i<address>.light.east
 
 
|0
 
|0
|R
+
|W
|light is not coming from east
+
|
|-
 
|1
 
|R
 
|light is coming from east
 
 
|-
 
|-
  
|rowspan="2"|i<address>.fault
 
|0
 
|R
 
|sensor not fault
 
|-
 
|1
 
|R
 
|sensor fault
 
|-
 
 
|}
 
|}
  
 
----
 
----
  
=== DFCC ===
+
=== DFCC2 ===
The DFCC is an energy meter and load manager module.
+
Energy meter and load manager module for Domino bus.
  
In the following table, <N> is the sequential index (1 to 3) of the DFCC module.
+
Uses 10 consecutive input addresses and, if enabled, 1 output address equal to the base input address.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,912: Line 4,040:
 
|-
 
|-
  
|energy.<n>.power.real
+
|i<address>.v
|0...65535
+
|[V / 10]
 
|R
 
|R
|real power (Watt)
+
|measured RMS voltage
 
|-
 
|-
  
|energy.<n>.power.reactive
+
|i<address>.i
| -32768...+32767
+
|[A / 10]
 
|R
 
|R
|reactive power (var)
+
|measured RMS current
 
|-
 
|-
  
|energy.<n>.power.apparent
+
|i<address>.p
| -32768...+32767
+
|[W]
 
|R
 
|R
|apparent power (VA)
+
|active power (signed)
 
|-
 
|-
  
|energy.<n>.power.realavg
+
|i<address>.q
|0...65535
+
|[VAR]
 
|R
 
|R
|average real power (Watt)
+
|reactive power (signed)
 
|-
 
|-
  
|energy.<n>.power.reactiveavg
+
|i<address>.s
| -32768...+32767
+
|[VA]
 
|R
 
|R
|average reactive power (var)
+
|apparent power
 
|-
 
|-
  
|energy.<n>.cos
+
|i<address>.pf
| -1000...+1000  
+
|[x 1000]
 
|R
 
|R
|cos(φ) * 1000
+
|power factor (signed: positive for inductive loads, negative for reactive loads)
 
|-
 
|-
  
|rowspan="2"|energy.<n>.load.1
+
|i<address>.ae
|0
+
|[Wh]
 
|R
 
|R
|load 1 disabled
+
|total active energy
 +
|-
 +
 
 +
|rowspan="2"|i<address>.1
 +
|0
 +
|R
 +
|load 1 disabled
 
|-
 
|-
 
|1
 
|1
Line 3,958: Line 4,092:
 
|-
 
|-
  
|rowspan="2"|energy.<n>.load.2
+
|rowspan="2"|i<address>.2
 
|0
 
|0
 
|R
 
|R
Line 3,968: Line 4,102:
 
|-
 
|-
  
|rowspan="2"|energy.<n>.load.3
+
|rowspan="2"|i<address>.3
 
|0
 
|0
 
|R
 
|R
Line 3,978: Line 4,112:
 
|-
 
|-
  
|rowspan="2"|energy.<n>.load.4
+
|rowspan="2"|i<address>.4
 
|0
 
|0
 
|R
 
|R
Line 3,988: Line 4,122:
 
|-
 
|-
  
|rowspan="2"|energy.<n>.load.5
+
|rowspan="2"|i<address>.5
 
|0
 
|0
 
|R
 
|R
Line 3,998: Line 4,132:
 
|-
 
|-
  
|rowspan="2"|energy.<n>.load.6
+
|rowspan="2"|i<address>.6
 
|0
 
|0
 
|R
 
|R
Line 4,008: Line 4,142:
 
|-
 
|-
  
|rowspan="2"|energy.<n>.load.7
+
|rowspan="2"|i<address>.7
 
|0
 
|0
 
|R
 
|R
Line 4,018: Line 4,152:
 
|-
 
|-
  
|rowspan="2"|energy.<n>.load.8
+
|rowspan="2"|i<address>.8
 
|0
 
|0
 
|R
 
|R
Line 4,028: Line 4,162:
 
|-
 
|-
  
|}
+
|rowspan="2"|o<address>.1
 +
|0
 +
|RW
 +
|load 1 control enabled
 +
|-
 +
|1
 +
|RW
 +
|load 1 always enabled
 +
|-
  
----
+
|rowspan="2"|o<address>.2
 +
|0
 +
|RW
 +
|load 2 control enabled
 +
|-
 +
|1
 +
|RW
 +
|load 2 always enabled
 +
|-
  
=== DFANA ===
+
|rowspan="2"|o<address>.3
Network analyzer module for Domino bus.
+
|0
 +
|RW
 +
|load 3 control enabled
 +
|-
 +
|1
 +
|RW
 +
|load 3 always enabled
 +
|-
  
Uses up to 20 consecutive input addresses and, if enabled, 1 output address equal to the base input address.
+
|rowspan="2"|o<address>.4
 
+
|0
{{note|The module's firmware should be version 1.3 or later to support negative values for active power readings.}}
+
|RW
 
+
|load 4 control enabled
{| class="wikitable"
 
!ID
 
!Value
 
!R/W
 
!Description
 
 
|-
 
|-
 
+
|1
|i<address>.v12
+
|RW
|[V]
+
|load 4 always enabled
|R
 
|chained voltage phase 1-2
 
 
|-
 
|-
  
|i<address>.v23
+
|rowspan="2"|o<address>.5
|[V]
+
|0
|R
+
|RW
|chained voltage phase 2-3
+
|load 5 control enabled
 
|-
 
|-
 
+
|1
|i<address>.v31
+
|RW
|[V]
+
|load 5 always enabled
|R
 
|chained voltage phase 3-1
 
 
|-
 
|-
  
|i<address>.vtm
+
|rowspan="2"|o<address>.6
|[V]
+
|0
|R
+
|RW
|average chained voltage
+
|load 6 control enabled
 +
|-
 +
|1
 +
|RW
 +
|load 6 always enabled
 
|-
 
|-
  
|i<address>.i1
+
|rowspan="2"|o<address>.7
|[A]
+
|0
|R
+
|RW
|current phase 1
+
|load 7 control enabled
 
|-
 
|-
 
+
|1
|i<address>.i2
+
|RW
|[A]
+
|load 7 always enabled
|R
 
|current phase 2
 
 
|-
 
|-
  
|i<address>.i3
+
|rowspan="2"|o<address>.8
|[A]
+
|0
|R
+
|RW
|current phase 3
+
|load 8 control enabled
 
|-
 
|-
 
+
|1
|i<address>.itm
+
|RW
|[A]
+
|load 8 always enabled
|R
 
|average current
 
 
|-
 
|-
  
|i<address>.ptot
+
|rowspan="2"|o<address>.buzzer
|[W]
+
|0
|R
+
|RW
|total active power
+
|buzzer disabled
 
|-
 
|-
 
+
|1
|i<address>.ptotk
+
|RW
|[kW]
+
|buzzer enabled
|R
 
|total active power
 
 
|-
 
|-
  
|i<address>.qtot
+
|o<address>.ae
|[W]
+
|reset
|R
+
|W
|total reactive power
+
|reset total active energy counter
 
|-
 
|-
  
|i<address>.qtotk
+
|}
|[kW]
 
|R
 
|total reactive power
 
|-
 
  
|i<address>.pf
+
== User Interface ==
|[pf]
 
|R
 
|total power factor
 
|-
 
  
|i<address>.frequency
+
All DOMINO devices data points that have been defined in the systemtopo.txt database are automatically listed in the Project Editor.  
|[Hz]
 
|R
 
|frequency
 
|-
 
  
|i<address>.v1n
+
Adding a button to control a device output point requires just a few clicks and no additional EVENTS logic.
|[V]
 
|R
 
|voltage phase 1
 
|-
 
  
|i<address>.v2n
 
|[V]
 
|R
 
|voltage phase 2
 
|-
 
  
|i<address>.v3n
+
[[File:IO Servers Domino Project Editor.png]]
|[V]
 
|R
 
|voltage phase 3
 
|-
 
  
|i<address>.p1
 
|[W]
 
|R
 
|active power phase 1
 
|-
 
  
|i<address>.p1k
+
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.
|[kW]
 
|R
 
|active power phase 1
 
|-
 
  
|i<address>.p2
+
----
|[W]
 
|R
 
|active power phase 2
 
|-
 
  
|i<address>.p2k
+
=== DFDMX ===
|[kW]
 
|R
 
|active power phase 2
 
|-
 
  
|i<address>.p3
+
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.
|[W]
 
|R
 
|active power phase 3
 
|-
 
  
|i<address>.p3k
+
For example:
|[kW]
+
 
|R
+
<pre>
|active power phase 3
+
dmxServers = dmx
|-
+
dmxServersId.dmx = domino.o8
 +
</pre>
  
|}
+
{{tip|Note that, instead of defining the dmxServersIP parameter, the dmxServersId is used to associate the DMX server with the id of the DFDMX module.}}
  
 
----
 
----
  
=== DFCC2 ===
+
=== DFCC ===
Energy meter and load manager module for Domino bus.
+
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.
 +
 
 +
{{tip|Note that, if you have more than one DFCP gateway, you should enable this option for one gateway only.}}
 +
 
 +
==== UISET Actions ====
  
Uses 10 consecutive input addresses and, if enabled, 1 output address equal to the base input address.
+
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.
  
 
{| class="wikitable"
 
{| class="wikitable"
 
!ID
 
!ID
!Value
+
!Attribute
!R/W
+
!colspan="2"|Set to
!Description
 
 
|-
 
|-
  
|i<address>.v
+
|energy.<n>.power
|[V / 10]
+
|value
|R
+
|real power, followed by “ W”. <n> is the sequential index (1 to 3) of the DFCC module.
|measured RMS voltage
 
 
|-
 
|-
 +
|}
  
|i<address>.i
+
----
|[A / 10]
 
|R
 
|measured RMS current
 
|-
 
  
|i<address>.p
+
=== DFCT and DF8RIT===
|[W]
+
You can use the [[temp]] and [[tempmini]] objects to control DFCT or DF8RIT devices.
|R
+
 
|active power (signed)
+
 
 +
[[File:IO Servers Domino DFCT.png]]
 +
 
 +
 
 +
==== 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.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Attribute
 +
!Set to
 +
!Description
 
|-
 
|-
  
|i<address>.q
+
|rowspan="2"|<address>.mode
|[VAR]
+
|rowspan="2"|value
|R
+
|SUMMER
|reactive power (signed)
+
|summer mode (cooling)
 +
|-
 +
|WINTER
 +
|winter mode (heating)
 
|-
 
|-
  
|i<address>.s
+
|<address>.mode.label.summer
|[VA]
+
|visible
|R
+
|true
|apparent power
+
|the DFCT is in summer mode
 
|-
 
|-
  
|i<address>.pf
+
|<address>.mode.label.winter
|[x 1000]
+
|visible
|R
+
|true
|power factor (signed: positive for inductive loads, negative for reactive loads)
+
|the DFCT is in winter mode
 
|-
 
|-
  
|i<address>.ae
+
|rowspan="2"|<address>.status
|[Wh]
+
|rowspan="2"|value
|R
+
|OFF
|total active energy
+
|zone off
 +
|-
 +
|ON
 +
|zone on
 
|-
 
|-
  
|rowspan="2"|i<address>.1
+
|<address>.status.label.cooling
|0
+
|visible
|R
+
|true
|load 1 disabled
+
|if the zone is cooling
 
|-
 
|-
|1
+
 
|R
+
|<address>.status.label.heating
|load 1 enabled
+
|visible
 +
|true
 +
|if the zone is heating
 
|-
 
|-
  
|rowspan="2"|i<address>.2
+
|rowspan="4"|<address>.fan
|0
+
|rowspan="4"|value
|R
+
|OFF
|load 2 disabled
+
|fan off
 
|-
 
|-
|1
+
|MIN
|R
+
|minimum fan speed
|load 2 enabled
 
 
|-
 
|-
 
+
|MED
|rowspan="2"|i<address>.3
+
|medium fan speed
|0
+
|-
|R
+
|MAX
|load 3 disabled
+
|maximum fan speed
 
|-
 
|-
|1
+
 
|R
+
|<address>.fan.label.min
|load 3 enabled
+
|visible
 +
|true
 +
|the fan speed is min
 
|-
 
|-
  
|rowspan="2"|i<address>.4
+
|<address>.fan.label.med
|0
+
|visible
|R
+
|true
|load 4 disabled
+
|the fan speed is med
 
|-
 
|-
|1
+
 
|R
+
|<address>.fan.label.max
|load 4 enabled
+
|visible
 +
|true
 +
|the fan speed is max
 
|-
 
|-
  
|rowspan="2"|i<address>.5
+
|rowspan="2"|<address>.fan.mode
|0
+
|rowspan="2"|value
|R
+
|MAN
|load 5 disabled
+
|manual fan mode
 
|-
 
|-
|1
+
|AUTO
|R
+
|auto fan mode
|load 5 enabled
 
 
|-
 
|-
  
|rowspan="2"|i<address>.6
+
|rowspan="3"|<address>.setpoint
|0
+
|rowspan="3"|value
|R
+
|1,2,3
|load 6 disabled
+
|active setpoint
 +
|-
 +
|MAN
 +
|manual setpoint
 
|-
 
|-
|1
+
|OFF
|R
+
|zone off
|load 6 enabled
 
 
|-
 
|-
  
|rowspan="2"|i<address>.7
+
|<address>.setpoint.label.1
|0
+
|visible
|R
+
|true
|load 7 disabled
+
|setpoint 1 is active
 
|-
 
|-
|1
+
 
|R
+
|<address>.setpoint.label.2
|load 7 enabled
+
|visible
 +
|true
 +
|setpoint 2 is active
 
|-
 
|-
  
|rowspan="2"|i<address>.8
+
|<address>.setpoint.label.3
|0
+
|visible
|R
+
|true
|load 8 disabled
+
|setpoint 3 is active
|-
 
|1
 
|R
 
|load 8 enabled
 
 
|-
 
|-
  
|rowspan="2"|o<address>.1
+
|<address>.setpoint.label.man
|0
+
|visible
|RW
+
|true
|load 1 control enabled
+
|manual setpoint is active
 
|-
 
|-
|1
+
 
|RW
+
|<address>.setpoint.label.off
|load 1 always enabled
+
|visible
 +
|true
 +
|zone is off
 
|-
 
|-
  
|rowspan="2"|o<address>.2
+
|rowspan="2"|<address>.setpoint.mode
|0
+
|rowspan="2"|value
|RW
+
|MAN
|load 2 control enabled
+
|manual setpoint mode
 
|-
 
|-
|1
+
|AUTO
|RW
+
|auto setpoint mode
|load 2 always enabled
 
 
|-
 
|-
  
|rowspan="2"|o<address>.3
+
|<address>.setpoint.temp
|0
+
|value
|RW
+
|<value>
|load 3 control enabled
+
|the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
|-
 
|-
|1
+
 
|RW
+
|<address>.setpoint.temp.1
|load 3 always enabled
+
|value
 +
|<value>
 +
|the active setpoint 1 temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
|-
 
|-
  
|rowspan="2"|o<address>.4
+
|<address>.setpoint.temp.2
|0
+
|value
|RW
+
|<value>
|load 4 control enabled
+
|the active setpoint 2 temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
|-
 
|-
|1
+
 
|RW
+
|<address>.setpoint.temp.3
|load 4 always enabled
+
|value
 +
|<value>
 +
|the active setpoint 3 temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
|-
 
|-
  
|rowspan="2"|o<address>.5
+
|<address>.setpoint.temp.man
|0
+
|value
|RW
+
|<value>
|load 5 control enabled
+
|the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
|-
 
|1
 
|RW
 
|load 5 always enabled
 
 
|-
 
|-
  
|rowspan="2"|o<address>.6
+
|rowspan="2"|<address>.temp
|0
+
|rowspan="2"|value
|RW
+
|<temp>
|load 6 control enabled
+
|the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
|-
 
|-
|1
+
|FAULT
|RW
+
|fault/error condition
|load 6 always enabled
 
 
|-
 
|-
 +
|}
  
|rowspan="2"|o<address>.7
+
==== USER Commands ====
|0
+
There are several predefined buttons. Use any ordinary [[user]] object, setting the ''name'' and ''param'' fields based on this table.
|RW
+
 
|load 7 control enabled
+
{| class="wikitable"
|-
+
!Name
|1
+
!Param
|RW
+
!Action
|load 7 always enabled
 
 
|-
 
|-
  
|rowspan="2"|o<address>.8
+
|rowspan="4"|<address>
|0
+
|mode
|RW
+
|cycle through summer and winter mode
|load 8 control enabled
 
 
|-
 
|-
|1
+
|mode.summer
|RW
+
|set summer mode (cooling)
|load 8 always enabled
 
 
|-
 
|-
 
+
|mode.winter
|rowspan="2"|o<address>.buzzer
+
|set winter mode (heating)
|0
 
|RW
 
|buzzer disabled
 
 
|-
 
|-
|1
+
|fan
|RW
+
|cycle through fan speeds and modes (auto, off, man/min, man/med, man/max, auto)
|buzzer enabled
 
 
|-
 
|-
  
|o<address>.ae
+
|rowspan="16"|<address>.setpoint
|reset
+
|mode
|W
+
|cycle through the manual, automatic and off operation modes
|reset total active energy counter
 
 
|-
 
|-
 
+
|mode.man
|}
+
|set manual operation mode
 
+
|-
== User Interface ==
+
|mode.auto
 
+
|set automatic operation mode
All DOMINO devices data points that have been defined in the systemtopo.txt database are automatically listed in the Project Editor.
+
|-
 
+
|mode.off
Adding a button to control a device output point requires just a few clicks and no additional EVENTS logic.
+
|off mode
 
+
|-
 
+
|temp.1.up
[[File:IO Servers Domino Project Editor.png]]
+
|increase setpoint 1 temperature in 0.5C steps
 
+
|-
 
+
|temp.1.down
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.
+
|decrease setpoint 1 temperature in 0.5C steps
 
+
|-
----
+
|temp.1.<t>
 
+
|setpoint 1 set to temperature t, in C/10 (0 <= t <= 355)
=== DFDMX ===
+
|-
 
+
|temp.2.up
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.  
+
|increase setpoint 2 temperature in 0.5C steps
 
+
|-
For example:
+
|temp.2.down
 
+
|decrease setpoint 2 temperature in 0.5C steps
<pre>
+
|-
dmxServers = dmx
+
|temp.2.<t>
dmxServersId.dmx = domino.o8
+
|setpoint 2 set to temperature t, in C/10 (0 <= t <= 355)
</pre>
+
|-
 
+
|temp.3.up
{{tip|Note that, instead of defining the dmxServersIP parameter, the dmxServersId is used to associate the DMX server with the id of the DFDMX module.}}
+
|increase setpoint 3 temperature in 0.5C steps
 
 
----
 
 
 
=== 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.  
 
 
 
{{tip|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.
 
 
 
{| class="wikitable"
 
!ID
 
!Attribute
 
!colspan="2"|Set to
 
 
|-
 
|-
 
+
|temp.3.down
|energy.<n>.power
+
|decrease setpoint 3 temperature in 0.5C steps
|value
 
|real power, followed by “ W”. <n> is the sequential index (1 to 3) of the DFCC module.
 
 
|-
 
|-
|}
+
|temp.3.<t>
 
+
|setpoint 3 set to temperature t, in C/10 (0 <= t <= 355)
----
+
|-
 
+
|temp.man.up
=== DFCT and DF8RIT===
+
|increase manual setpoint temperature in 0.5C steps
You can use the [[temp]] and [[tempmini]] objects to control DFCT or DF8RIT devices.
 
 
 
 
 
[[File:IO Servers Domino DFCT.png]]
 
 
 
 
 
==== 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.
 
 
 
{| class="wikitable"
 
!ID
 
!Attribute
 
!Set to
 
!Description
 
 
|-
 
|-
 
+
|temp.man.down
|rowspan="2"|<address>.mode
+
|decrease manual setpoint temperature in 0.5C steps
|rowspan="2"|value
 
|SUMMER
 
|summer mode (cooling)
 
 
|-
 
|-
|WINTER
+
|temp.man.<t>
|winter mode (heating)
+
|manual setpoint set to temperature t, in C/10 (0 <= t <= 355)
 
|-
 
|-
  
|<address>.mode.label.summer
+
|rowspan="9"|<address>.fan
|visible
+
|mode
|true
+
|cycle through the manual and automatic fan speed modes
|the DFCT is in summer mode
 
 
|-
 
|-
 
+
|mode.man
|<address>.mode.label.winter
+
|set manual fan speed mode
|visible
 
|true
 
|the DFCT is in winter mode
 
 
|-
 
|-
 
+
|mode.auto
|rowspan="2"|<address>.status
+
|set automatic fan speed mode
|rowspan="2"|value
 
|OFF
 
|zone off
 
 
|-
 
|-
|ON
+
|up
|zone on
+
|increase fan speed
 
|-
 
|-
 
+
|down
|<address>.status.label.cooling
+
|decrease fan speed
|visible
 
|true
 
|if the zone is cooling
 
 
|-
 
|-
 
+
|min
|<address>.status.label.heating
+
|set min fan speed
|visible
 
|true
 
|if the zone is heating
 
 
|-
 
|-
 
+
|med
|rowspan="4"|<address>.fan
+
|set med fan speed
|rowspan="4"|value
 
|OFF
 
|fan off
 
 
|-
 
|-
|MIN
+
|max
|minimum fan speed
+
|set max fan speed
 
|-
 
|-
|MED
+
|off
|medium fan speed
+
|fan off
|-
 
|MAX
 
|maximum fan speed
 
 
|-
 
|-
 +
|}
 +
 +
==== Using slider objects for DF8RIT shutter's position ====
  
|<address>.fan.label.min
+
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).
|visible
+
 
|true
+
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.
|the fan speed is min
 
|-
 
  
|<address>.fan.label.med
+
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.
|visible
 
|true
 
|the fan speed is med
 
|-
 
  
|<address>.fan.label.max
+
{{tip|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.}}
|visible
 
|true
 
|the fan speed is max
 
|-
 
  
|rowspan="2"|<address>.fan.mode
 
|rowspan="2"|value
 
|MAN
 
|manual fan mode
 
|-
 
|AUTO
 
|auto fan mode
 
|-
 
  
|rowspan="3"|<address>.setpoint
+
----
|rowspan="3"|value
 
|1,2,3
 
|active setpoint
 
|-
 
|MAN
 
|manual setpoint
 
|-
 
|OFF
 
|zone off
 
|-
 
  
|<address>.setpoint.label.1
+
==== Using slider objects for DF4RI / DF4RIR shutter's position ====
|visible
 
|true
 
|setpoint 1 is active
 
|-
 
  
|<address>.setpoint.label.2
+
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).
|visible
+
 
|true
+
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.
|setpoint 2 is active
+
 
 +
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.
 +
 
 +
{{tip|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.
 +
 
 +
[[File:IO Servers Domino DFTZ.png]]
 +
 
 +
==== 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.
 +
 
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Attribute
 +
!Set to
 +
!Description
 +
|-
 +
 
 +
|rowspan="2"|<address>.mode
 +
|rowspan="2"|value
 +
|SUMMER
 +
|summer mode (cooling)
 +
|-
 +
|WINTER
 +
|winter mode (heating)
 
|-
 
|-
  
|<address>.setpoint.label.3
+
|<address>.mode.label.summer
 
|visible
 
|visible
 
|true
 
|true
|setpoint 3 is active
+
|the DFTZ is in summer mode
 
|-
 
|-
  
|<address>.setpoint.label.man
+
|<address>.mode.label.winter
 
|visible
 
|visible
 
|true
 
|true
|manual setpoint is active
+
|the DFTZ is in winter mode
 
|-
 
|-
  
|<address>.setpoint.label.off
+
|rowspan="2"|<address>.status
|visible
 
|true
 
|zone is off
 
|-
 
 
 
|rowspan="2"|<address>.setpoint.mode
 
 
|rowspan="2"|value
 
|rowspan="2"|value
|MAN
+
|OFF
|manual setpoint mode
+
|zone off
 
|-
 
|-
|AUTO
+
|ON
|auto setpoint mode
+
|zone on
 
|-
 
|-
  
|<address>.setpoint.temp
+
|<address>.status.label.off
|value
+
|visible
|<value>
+
|true
|the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|if the zone is not cooling or heating
 
|-
 
|-
  
|<address>.setpoint.temp.1
+
|<address>.status.label.cooling
|value
+
|visible
|<value>
+
|true
|the active setpoint 1 temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|if the zone is cooling
 
|-
 
|-
  
|<address>.setpoint.temp.2
+
|<address>.status.label.heating
|value
+
|visible
|<value>
+
|true
|the active setpoint 2 temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|if the zone is heating
 
|-
 
|-
  
|<address>.setpoint.temp.3
+
|rowspan="3"|<address>.setpoint  
|value
+
|rowspan="3"|value
|<value>
+
|COM
|the active setpoint 3 temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|comfort setpoint
 +
|-
 +
|MAN
 +
|manual setpoint
 +
|-
 +
|OFF
 +
|zone off
 
|-
 
|-
  
|<address>.setpoint.temp.man
+
|<address>.setpoint.label.1
|value
+
|visible
|<value>
+
|true
|the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|comfort setpoint is active
 
|-
 
|-
  
|rowspan="2"|<address>.temp
+
|<address>.setpoint.label.2
|rowspan="2"|value
+
|visible
|<temp>
+
|true
|the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|eco setpoint is active
 
|-
 
|-
|FAULT
+
 
|fault/error condition
+
|<address>.setpoint.label.off
 +
|visible
 +
|true
 +
|zone is off
 
|-
 
|-
|}
 
  
==== USER Commands ====
+
|<address>.setpoint.temp
There are several predefined buttons. Use any ordinary [[user]] object, setting the ''name'' and ''param'' fields based on this table.
+
|value
 +
|<temp>
 +
|the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 +
|-
  
{| class="wikitable"
+
|<address>.setpoint.temp.1
 +
|value
 +
|<temp>
 +
|the comfort setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 +
|-
 +
 
 +
|<address>.setpoint.temp.2
 +
|value
 +
|<temp>
 +
|the eco setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 +
|-
 +
 
 +
|<address>.setpoint.temp.man
 +
|value
 +
|<temp>
 +
|the summer or winter setpoint temperature limit, in Celsius degrees with one decimal digit, followed by " &deg;C"
 +
|-
 +
 
 +
|rowspan="2"|<address>.temp
 +
|rowspan="2"|value
 +
|<temp>
 +
|the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;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.
 +
 
 +
{| class="wikitable"
 
!Name
 
!Name
 
!Param
 
!Param
Line 4,673: Line 4,774:
 
|-
 
|-
  
|rowspan="4"|<address>
+
|rowspan="3"|<address>
 
|mode
 
|mode
 
|cycle through summer and winter mode
 
|cycle through summer and winter mode
Line 4,682: Line 4,783:
 
|mode.winter
 
|mode.winter
 
|set winter mode (heating)
 
|set winter mode (heating)
|-
 
|fan
 
|cycle through fan speeds and modes (auto, off, man/min, man/med, man/max, auto)
 
 
|-
 
|-
  
Line 4,691: Line 4,789:
 
|cycle through the manual, automatic and off operation modes
 
|cycle through the manual, automatic and off operation modes
 
|-
 
|-
|mode.man
+
|mode.comfort
|set manual operation mode
+
|set comfort operation mode
 
|-
 
|-
|mode.auto
+
|mode.eco
|set automatic operation mode
+
|set eco operation mode
 
|-
 
|-
 
|mode.off
 
|mode.off
 
|off mode
 
|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
 
|temp.1.up
|increase setpoint 1 temperature in 0.5C steps
+
|increase comfort setpoint temperature in 0.5C steps
 
|-
 
|-
 
|temp.1.down
 
|temp.1.down
|decrease setpoint 1 temperature in 0.5C steps
+
|decrease comfort setpoint temperature in 0.5C steps
 
|-
 
|-
 
|temp.1.<t>
 
|temp.1.<t>
|setpoint 1 set to temperature t, in C/10 (0 <= t <= 355)
+
|comfort setpoint set to temperature t, in C/10 (0 <= t <= 355)
 
|-
 
|-
 
|temp.2.up
 
|temp.2.up
|increase setpoint 2 temperature in 0.5C steps
+
|increase eco setpoint temperature in 0.5C steps
 
|-
 
|-
 
|temp.2.down
 
|temp.2.down
|decrease setpoint 2 temperature in 0.5C steps
+
|decrease eco setpoint temperature in 0.5C steps
 
|-
 
|-
 
|temp.2.<t>
 
|temp.2.<t>
|setpoint 2 set to temperature t, in C/10 (0 <= t <= 355)
+
|eco setpoint 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
 
|temp.man.up
|increase manual setpoint temperature in 0.5C steps
+
|increase setpoint temperature limit in 0.5C steps
 
|-
 
|-
 
|temp.man.down
 
|temp.man.down
|decrease manual setpoint temperature in 0.5C steps
+
|decrease setpoint temperature limit in 0.5C steps
 
|-
 
|-
 
|temp.man.<t>
 
|temp.man.<t>
|manual setpoint set to temperature t, in C/10 (0 <= t <= 355)
+
|set-point temperature limit set to temperature t, in C/10 (0 <= t <= 355)
 
|-
 
|-
  
|rowspan="9"|<address>.fan
+
|}
|mode
+
 
|cycle through the manual and automatic fan speed modes
+
== Release Notes ==
|-
 
|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
 
|-
 
|}
 
  
==== Using slider objects for DF8RIT shutter's position ====
+
=== 3.5.1 ===
 
+
*added support for DF4DV
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).
+
*added support for DF4RI / DF4RIR
 
 
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.
 
 
 
{{tip|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.
 
 
 
[[File:IO Servers Domino DFTZ.png]]
 
 
 
==== 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.
 
 
 
 
 
{| class="wikitable"
 
!ID
 
!Attribute
 
!Set to
 
!Description
 
|-
 
 
 
|rowspan="2"|<address>.mode
 
|rowspan="2"|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
 
|-
 
 
 
|rowspan="2"|<address>.status
 
|rowspan="2"|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
 
|-
 
 
 
|rowspan="3"|<address>.setpoint
 
|rowspan="3"|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 " &deg;C"
 
|-
 
 
 
|<address>.setpoint.temp.1
 
|value
 
|<temp>
 
|the comfort setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
|-
 
 
 
|<address>.setpoint.temp.2
 
|value
 
|<temp>
 
|the eco setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
|-
 
 
 
|<address>.setpoint.temp.man
 
|value
 
|<temp>
 
|the summer or winter setpoint temperature limit, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
|-
 
 
 
|rowspan="2"|<address>.temp
 
|rowspan="2"|value
 
|<temp>
 
|the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;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.
 
 
 
{| class="wikitable"
 
!Name
 
!Param
 
!Action
 
|-
 
 
 
|rowspan="3"|<address>
 
|mode
 
|cycle through summer and winter mode
 
|-
 
|mode.summer
 
|set summer mode (cooling)
 
|-
 
|mode.winter
 
|set winter mode (heating)
 
|-
 
 
 
|rowspan="16"|<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.1 ===
 
 
*added support for DF8RIT
 
*added support for DF8RIT
*added support for DF4DV
+
*added support for DFLS / DFLS-P
 
*fixed a bug that could cause erroneous readings of DFCC2 2'complement values
 
*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)
 
*DFANA updated to support negative active energy values (fw. 1.5 or later)

Latest revision as of 09:33, 27 October 2017

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.

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


Note 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 addresses
detected.output.<n>. model name an output device of the type passed as value has been detected at address <n>, using 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 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
DF4RI / DF4RIR multifunction module with 4 digital inputs and 4 outputs (power relay)
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)
DF4DV 4 outputs (1-10V - ballast)
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
DFLS / DFLS-P ambient light sensor and presence detector
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

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

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

Relay outputs section 1-2

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

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

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

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 + 1> 0 ... 100% RW percent position

Relay outputs section 3-4

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

ID Value R/W Description
o<address>.1 0 RW output pin 3 off
1 RW output pin 3 on
o<address>.2 0 RW output pin 4 off
1 RW output pin 4 on

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

ID Value R/W Description
o<address>.3 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> 0 ... 100% RW percent position

Relay outputs section 5-6

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

ID Value R/W Description
o<address>.1 0 RW output pin 5 off
1 RW output pin 5 on
o<address>.2 0 RW output pin 6 off
1 RW output pin 6 on

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

ID Value R/W Description
o<address>.5 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 + 3> 0 ... 100% RW percent position

Relay outputs section 7-8

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

ID Value R/W Description
o<address>.1 0 RW output pin 7 off
1 RW output pin 7 on
o<address>.2 0 RW output pin 8 off
1 RW output pin 8 on

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

ID Value R/W Description
o<address>.7 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 + 4> 0 ... 100% RW percent position

Temperature control section

If temperature control is enabled:

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.


ID Value R/W Description
i<address + 5>.mode winter R winter mode
summer R summer mode
i<address + 5>.fan min R min fan speed
med R medium fan speed
max R max fan speed
off R fan off
i<address + 5>.fan.mode man R manual fan mode
auto R auto fan mode
i<address + 5>.setpoint 1 R setpoint 1
2 R setpoint 2
3 R setpoint 3
off R off
man R manual setpoint
i<address + 5>.setpoint.mode man R manual setpoint mode
auto R auto setpoint mode
i<address + 5>.temp <temp> R temperature value (in C/10)
fault R temperature sensor fault
i<address + 5>.status off R off
cooling R cooling status mode
heating R heating status mode
o<address + 5>.mode winter RW winter mode
summer RW summer mode
o<address + 5>.fan min RW min fan speed
med RW medium fan speed
max RW max fan speed
off RW fan off
o<address + 5>.fan.mode man RW manual fan mode
auto RW auto fan mode
o<address + 5>.setpoint 1 RW setpoint 1
2 RW setpoint 2
3 RW setpoint 3
0 RW setpoint off
man RW manual setpoint
o<address + 5>.setpoint.temp.1 <temp> RW temperature setpoint 1 value (in C/10)
o<address + 5>.setpoint.temp.2 <temp> RW temperature setpoint 2 value (in C/10)
o<address + 5>.setpoint.temp.3 <temp> RW temperature setpoint 3 value (in C/10)
o<address + 5>.setpoint.temp.man <temp> RW temperature manual setpoint value (in C/10)
o<address + 5>.program.summer
o<address + 5>.program.winter
refresh RW forces to daily summer/winter program for all days of the week
o<address + 5>.program.summer.<day>
o<address + 5>.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

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

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

Relay outputs section 1-2

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

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

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

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 + 1> 0 ... 100% RW percent position

Relay outputs section 3-4

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

ID Value R/W Description
o<address>.1 0 RW output pin 3 off
1 RW output pin 3 on
o<address>.2 0 RW output pin 4 off
1 RW output pin 4 on

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

ID Value R/W Description
o<address>.3 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> 0 ... 100% RW percent position

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.

DF4DV

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

The DF4DV uses 4 consecutive addresses in the DOMINO bus.

ID Value R/W Description
o<address> program R program 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)

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

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.

ID Value R/W Description
i<address> 0...1023 R lux level (raw level, not translated to the lux range)
i<address + 1>.1 0 R input IN1 off
1 R input IN1 on
i<address + 1>.2 0 R input IN2 off
1 R input IN2 on
i<address + 1>.3 0 R presence with delay is off
1 R presence with delay is on

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.mode man RW manual setpoint mode
auto RW auto setpoint mode
off RW off mode
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.

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


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
i<address>.q1 [W] R reactive power phase 1
i<address>.q1k [kW] R reactive power phase 1
i<address>.q2 [W] R reactive power phase 2
i<address>.q2k [kW] R reactive power phase 2
i<address>.q3 [W] R reactive power phase 3
i<address>.q3k [kW] R reactive power phase 3
i<address>.pf1 [pf] R power factor phase 1
i<address>.pf2 [pf] R power factor phase 2
i<address>.pf3 [pf] R power factor phase 3
i<address>.s1 [VA] R apparent power phase 1
i<address>.s1k [kVA] R apparent power phase 1
i<address>.s2 [VA] R apparent power phase 2
i<address>.s2k [kVA] R apparent power phase 2
i<address>.s3 [VA] R apparent power phase 3
i<address>.s3k [kVA] R apparent power phase 3
i<address>.stot [VA] R total apparent power
i<address>.hours [hours] R counter
i<address>.temperature [°C] R temperature
i<address>.energy.active [Wh] R positive active energy
i<address>.energy.activeneg [Wh] R negative active energy
i<address>.energy.reactive [VARh] R positive reactive energy
i<address>.energy.reactiveneg [VARh] R negative reactive energy
i<address>.pm [W] R average positive active power
i<address>.qm [VAR] R average positive reactive power
i<address>.reset.energy 1 W energy counter reset
0 W
i<address>.reset.hours 1 W counter reset
0 W

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.


IO Servers Domino Project Editor.png


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.

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 and DF8RIT

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


IO Servers Domino DFCT.png


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

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, sliderv and 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 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, sliderv and 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 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.

IO Servers Domino DFTZ.png

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.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.