Difference between revisions of "Contatto"

From HSYCO
Jump to navigation Jump to search
 
(287 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
The CONTATTO system is DUEMMEGI’s proprietary bus architecture for building automation. HSYCO fully integrates with this system through the MCP control and gateway module, and its FXP-XT serial communication protocol.
 
The CONTATTO system is DUEMMEGI’s proprietary bus architecture for building automation. HSYCO fully integrates with this system through the MCP control and gateway module, and its FXP-XT serial communication protocol.
−
A serial connection between the MCP 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.
+
 
 +
A serial connection between the MCPXT 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 MCP4 can be connected via the integrated serial to IP gateway.
 +
 
 +
{{note|
 +
The Contatto I/O Server requires MCP-XT firmware version 3.0 or later.
 +
The MCPIDE configuration tools pass-through support for secure access to the MCP via HSYCO requires MCPIDE version 3.2.3 or later.
 +
}}
 +
 
  
 
[[Category:I/O Server]]
 
[[Category:I/O Server]]
Line 6: Line 15:
 
== Communication ==
 
== Communication ==
  
−
Employ a DE-9 (often called DB-9) male-female RS-232 straight cable to connect the RS-232 MCP port to the serial port on HSYCO SERVER or serial gateway.
+
Use a DE-9 (often called DB-9) male-female RS-232 straight cable to connect the RS-232 MCPXT port to the serial port on HSYCO SERVER or serial gateway. You can also connect the MCPXT using the RS-485 port. The MCP4 can also be connected via the integrated serial to IP gateway.
−
The communication baud rate can be set to 9600, 38400, 57600 or 115200 bps, according to the MCP serial port settings. The protocol requires 8bit data, no parity, one stop bit, no flow control.
+
 
−
A speed of 115200 bps is recommended to achieve good performance, particularly when the number of devices connected to the bus is large.
+
RS-232 parameters:
 +
{| class="wikitable"
 +
| '''Baud rate'''
 +
| 9600, 38400, 57600 or 115200 bps (according to the MCP serial port setting)
 +
|-
 +
| '''Data bits'''
 +
| 8
 +
|-
 +
| '''Stop bit'''
 +
| 1
 +
|-
 +
| '''Parity'''
 +
| none
 +
|-
 +
| '''Flow control'''
 +
| none
 +
|}
 +
 
 +
{{tip|A speed of 115200 bps is recommended to achieve good performance, particularly when the number of devices connected to the bus is large.}}
 +
 
 +
 
 +
=== High Availability ===
 +
*'''Shutdown when inactive''': defaults to false.
  
 
== HSYCO Configuration ==
 
== HSYCO Configuration ==
 +
 +
You can define and connect to more than one CONTATTO bus using several MCP gateways.
 +
 +
The CONTATTO I/O Server also supports dual, redundant connections between HSYCO and MCP.
 +
 +
If the main connection fails, HSYCO automatically re-routes the communication with MCP through the fail-over connection.
  
 
=== Options ===
 
=== Options ===
Line 59: Line 96:
 
|rowspan="3"|virtualpoints
 
|rowspan="3"|virtualpoints
 
|rowspan="3"|false
 
|rowspan="3"|false
−
|1...2033
+
|1 ... 2032
 
|enables polling for the first n virtual points of the MCP. Enable this option only if you need to generate I/O events based on these virtual points
 
|enables polling for the first n virtual points of the MCP. Enable this option only if you need to generate I/O events based on these virtual points
 
|-
 
|-
Line 71: Line 108:
 
|rowspan="3"|registers
 
|rowspan="3"|registers
 
|rowspan="3"|false
 
|rowspan="3"|false
−
|1...1024
+
|1 ... 1024
 
|enables polling for registers R0-Rn of the MCP. Enable this option only if you need to generate I/O events based on these registers
 
|enables polling for registers R0-Rn of the MCP. Enable this option only if you need to generate I/O events based on these registers
 
|-
 
|-
Line 84: Line 121:
 
|rowspan="2"|false
 
|rowspan="2"|false
 
|≥ 0 (MODANA address)
 
|≥ 0 (MODANA address)
−
|enables the automatic display in the GUI of the total real power measured by a DFANA module connected to this MCP. Note that, if you have more than one MCP gateway, you should enable this option for one gateway only
+
|enables the automatic display in the GUI of the total real power measured by a MODANA or MODANAM module connected to this MCP. Note that, if you have more than one MCP gateway, you should enable this option for one gateway only
 
|-
 
|-
 
|false
 
|false
 
|power display disabled for this MCP
 
|power display disabled for this MCP
 +
|-
 +
 +
|rowspan="2"|disablemodhtpulsereset
 +
|rowspan="2"|false
 +
|true
 +
|disables automatic reset of MODHT pulse outputs (panic.reset, dnd.reset, service.reset, fan)
 +
|-
 +
|false
 +
|MODHT pulse outputs are automatically reset to 0 when found at level 1
 
|-
 
|-
  
Line 148: Line 194:
 
== The Device Configuration Database ==
 
== 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.
+
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 the hsyco.ini configuration file. The default behavior is to only discover devices with output data points.
+
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:
 
This is an example of an automatically generated systemtopo.txt file:
Line 174: Line 222:
 
</pre>
 
</pre>
  
−
== MCP Virtual Data Points and Registers ==
+
== MCP Data Points ==
 +
 
 +
The MCP implements 2032 virtual points for binary (on/off) data and 1024 registers and counters for positive scalar values (0-65535). All virtual points, registers and counters can optionally generate I/O events. You can also write to the virtual data points, registers and counters using the IO action in EVENTS or ioSet() method in Java.
  
−
The MCP 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 MCP virtual data points, registers or counters using GUI objects.
−
You cannot directly control the MCP virtual data points and registers using GUI objects.
+
 
−
To enable polling of the current state of the MCP’s virtual data points, enable the virtualpoints options in hsyco.ini.
+
To enable polling of the current state of the MCP’s virtual data points, enable the ''virtualpoints'' options in hsyco.ini.
−
To enable polling of the current state of the MCP’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.  
+
To enable polling of the current state of the MCP’s registers, enable the ''registers'' options in hsyco.ini.
 +
 
 +
To enable polling of the current state of the MCP’s counters, enable the ''counters'' options in hsyco.ini.
 +
 
 +
If you only have to write to virtual points, registers or counters, enabling polling is not strictly required.  
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 189: Line 243:
 
|-
 
|-
  
−
|rowspan="2"|v0.<n>
+
|rowspan="2"|busfault
 
|0
 
|0
−
|RW
+
|R
−
|virtual data point <n> off (<n>: 1-2032)
+
|no bus fault detected
 
|-
 
|-
 
|1
 
|1
−
|RW
+
|R
−
|virtual data point <n> on (<n>: 1-2032)
+
|bus fault detected
 
|-
 
|-
  
−
|r0.<n>
+
|rowspan="2"|modulefault
−
|<x>
+
|0
−
|RW
+
|R
−
|register <n> off (<n>: 0-1023) set to value <x> (<x>: 0-65535)
+
|no modules fault detected
 +
|-
 +
|1
 +
|R
 +
|modules fault detected
 +
|-
 +
 
 +
|rowspan="2"|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> (<n>: 0-1023) set to value <x> (<x>: 0-65535)
 +
|-
 +
 
 +
|c0.<n>
 +
|<x>
 +
|RW
 +
|counter <n> (<n>: 0-1023) set to value <x> (<x>: 0-65535)
 
|-
 
|-
  
Line 240: Line 320:
  
 
== CONTATTO Modules Events and Control ==
 
== CONTATTO Modules Events and Control ==
 +
 +
Each CONTATTO module has its own set of read-only or read-write data points, mapping the specific set of features.
 +
 +
All modules also have a  read-only "fault" data point, set to 1 if the MCP has detected a module fault condition, or 0 if the module is working normally.
  
 
{| class="wikitable"
 
{| class="wikitable"
−
!Module Code
+
!ID
 +
!Value
 +
!R/W
 
!Description
 
!Description
 
|-
 
|-
  
−
|MOD8I/A 8
+
|rowspan="2"|i<address>.fault
−
|digital input module for NO contacts in modular housing
+
|0
 +
|R
 +
|input module working normally
 
|-
 
|-
−
|MOD32I/A
+
|1
−
|32 digital input module for NO contacts in modular housing
+
|R
 +
|input module fault detected
 
|-
 
|-
−
|MOD8INP2/A
+
 
−
|8 digital input module for NO contacts
+
|rowspan="2"|o<address>.fault
 +
|0
 +
|R
 +
|output module working normally
 
|-
 
|-
−
|MOD8INP2/C
+
|1
−
|8 digital input module for NC contacts
+
|R
 +
|output module fault detected
 
|-
 
|-
−
|MOAN/I
+
|}
 +
 
 +
 
 +
{| class="wikitable"
 +
!Module Code
 +
!Description
 +
|-
 +
 
 +
|MOD8I/A
 +
|8 digital input module for NO contacts in modular housing
 +
|-
 +
|MOD32I/A
 +
|32 digital input module for NO contacts in modular housing
 +
|-
 +
|MOD32IL
 +
|32 digital input module for NO contacts in modular housing
 +
|-
 +
|MOD32IN
 +
|32 digital input module for NO contacts in modular housing
 +
|-
 +
|MOD8INP2/A
 +
|8 digital input module for NO contacts
 +
|-
 +
|MOD8INP2/C
 +
|8 digital input module for NC contacts
 +
|-
 +
|MOAN/I
 
|0÷10V analog input module
 
|0÷10V analog input module
 
|-
 
|-
Line 309: Line 428:
 
|4÷20mA analog output module
 
|4÷20mA analog output module
 
|-
 
|-
−
|MODLC
+
|MODLC, MODLC-P
 
|ambient light regulator module with integrated sensor
 
|ambient light regulator module with integrated sensor
 
|-
 
|-
Line 336: Line 455:
 
|DMX gateway
 
|DMX gateway
 
|-
 
|-
−
|MODDALI
+
|MODDALI
 
|4-channel DALI gateway
 
|4-channel DALI gateway
 +
|-
 +
|MODDALI8
 +
|8-channel broadcast DALI gateway
 
|-
 
|-
 
|CLIMA2
 
|CLIMA2
 
|module for the regulation of the ambient temperature
 
|module for the regulation of the ambient temperature
 
|-
 
|-
−
|MODANA
+
|MODANA
−
|network analyzer module for Contatto bus
+
|network analyzer module
 +
|-
 +
|MODANAM
 +
|network analyzer module
 
|-
 
|-
 
|MODPQ5
 
|MODPQ5
Line 356: Line 481:
 
|MODKB
 
|MODKB
 
|keypad access control module
 
|keypad access control module
 +
|-
 +
|MODDI
 +
|500W IGBT dimmer module
 +
|-
 +
|MODCL
 +
|temperature control module
 +
|-
 +
|MOD4TP/I
 +
|8 digital input and 4 roller shutters or blinds with detection of travel time
 +
|-
 +
|MODRHT
 +
|Temperature, relative humidity and dew point sensor
 +
|-
 +
|MODAM2
 +
|Multi-function, 2 inputs analog module
 +
|-
 +
|MODIGLASS, MODIGLASS3
 +
|6 button touch keypad
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MOD8I/A ===
 
=== MOD8I/A ===
  
 
8 digital input module for NO contacts in modular housing.
 
8 digital input module for NO contacts in modular housing.
 +
 
It uses one input address in the CONTATTO bus.
 
It uses one input address in the CONTATTO bus.
  
Line 371: Line 517:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|i<address>.1
 
|0
 
|0
 
|R
 
|R
Line 381: Line 527:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|rowspan="2"|i<address>.2
 
|0
 
|0
 
|R
 
|R
Line 391: Line 537:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="2"|i<address>.3
 
|0
 
|0
 
|R
 
|R
Line 401: Line 547:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="2"|i<address>.4
 
|0
 
|0
 
|R
 
|R
Line 411: Line 557:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.5
+
|rowspan="2"|i<address>.5
 
|0
 
|0
 
|R
 
|R
Line 421: Line 567:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.6
+
|rowspan="2"|i<address>.6
 
|0
 
|0
 
|R
 
|R
Line 431: Line 577:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.7
+
|rowspan="2"|i<address>.7
 
|0
 
|0
 
|R
 
|R
Line 441: Line 587:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.8
+
|rowspan="2"|i<address>.8
 
|0
 
|0
 
|R
 
|R
Line 451: Line 597:
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MOD32I/A ===
 
=== MOD32I/A ===
  
 
32 digital input module for NO contacts in modular housing.
 
32 digital input module for NO contacts in modular housing.
 +
 
It uses four addresses of the Contatto bus, one for each group of 8 inputs.
 
It uses four addresses of the Contatto bus, one for each group of 8 inputs.
  
Line 464: Line 613:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|i<address>.1
 
|0
 
|0
 
|R
 
|R
Line 474: Line 623:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|rowspan="2"|i<address>.2
 
|0
 
|0
 
|R
 
|R
Line 484: Line 633:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="2"|i<address>.3
 
|0
 
|0
 
|R
 
|R
Line 494: Line 643:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="2"|i<address>.4
 
|0
 
|0
 
|R
 
|R
Line 504: Line 653:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.5
+
|rowspan="2"|i<address>.5
 
|0
 
|0
 
|R
 
|R
Line 514: Line 663:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.6
+
|rowspan="2"|i<address>.6
 
|0
 
|0
 
|R
 
|R
Line 524: Line 673:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.7
+
|rowspan="2"|i<address>.7
 
|0
 
|0
 
|R
 
|R
Line 534: Line 683:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.8
+
|rowspan="2"|i<address>.8
 
|0
 
|0
 
|R
 
|R
Line 544: Line 693:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.1
+
|rowspan="2"|i<address+1>.1
 
|0
 
|0
 
|R
 
|R
Line 554: Line 703:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.2
+
|rowspan="2"|i<address+1>.2
 
|0
 
|0
 
|R
 
|R
Line 564: Line 713:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.3
+
|rowspan="2"|i<address+1>.3
 
|0
 
|0
 
|R
 
|R
Line 574: Line 723:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.4
+
|rowspan="2"|i<address+1>.4
 
|0
 
|0
 
|R
 
|R
Line 584: Line 733:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.5
+
|rowspan="2"|i<address+1>.5
 
|0
 
|0
 
|R
 
|R
Line 594: Line 743:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.6
+
|rowspan="2"|i<address+1>.6
 
|0
 
|0
 
|R
 
|R
Line 604: Line 753:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.7
+
|rowspan="2"|i<address+1>.7
 
|0
 
|0
 
|R
 
|R
Line 614: Line 763:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.8
+
|rowspan="2"|i<address+1>.8
 
|0
 
|0
 
|R
 
|R
Line 624: Line 773:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.1
+
|rowspan="2"|i<address+2>.1
 
|0
 
|0
 
|R
 
|R
Line 634: Line 783:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.2
+
|rowspan="2"|i<address+2>.2
 
|0
 
|0
 
|R
 
|R
Line 644: Line 793:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.3
+
|rowspan="2"|i<address+2>.3
 
|0
 
|0
 
|R
 
|R
Line 654: Line 803:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.4
+
|rowspan="2"|i<address+2>.4
 
|0
 
|0
 
|R
 
|R
Line 664: Line 813:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.5
+
|rowspan="2"|i<address+2>.5
 
|0
 
|0
 
|R
 
|R
Line 674: Line 823:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.6
+
|rowspan="2"|i<address+2>.6
 
|0
 
|0
 
|R
 
|R
Line 684: Line 833:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.7
+
|rowspan="2"|i<address+2>.7
 
|0
 
|0
 
|R
 
|R
Line 694: Line 843:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.8
+
|rowspan="2"|i<address+2>.8
 
|0
 
|0
 
|R
 
|R
Line 704: Line 853:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.1
+
|rowspan="2"|i<address+3>.1
 
|0
 
|0
 
|R
 
|R
Line 714: Line 863:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.2
+
|rowspan="2"|i<address+3>.2
 
|0
 
|0
 
|R
 
|R
Line 724: Line 873:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.3
+
|rowspan="2"|i<address+3>.3
 
|0
 
|0
 
|R
 
|R
Line 734: Line 883:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.4
+
|rowspan="2"|i<address+3>.4
 
|0
 
|0
 
|R
 
|R
Line 744: Line 893:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.5
+
|rowspan="2"|i<address+3>.5
 
|0
 
|0
 
|R
 
|R
Line 754: Line 903:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.6
+
|rowspan="2"|i<address+3>.6
 
|0
 
|0
 
|R
 
|R
Line 764: Line 913:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.7
+
|rowspan="2"|i<address+3>.7
 
|0
 
|0
 
|R
 
|R
Line 774: Line 923:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.8
+
|rowspan="2"|i<address+3>.8
 
|0
 
|0
 
|R
 
|R
Line 786: Line 935:
 
|}
 
|}
  
−
=== MOD8INP2/A ===
+
----
 +
 
 +
=== MOD32IL ===
 +
 
 +
32 digital input module for NO contacts in modular housing.
  
−
8 digital input module for NO contacts.
+
It uses one addresses of the Contatto bus and four channels, one for each group of 8 inputs.
−
It uses one input address of the Contatto bus.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 798: Line 950:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|i<address>.N
 +
N=1-32
 
|0
 
|0
 
|R
 
|R
−
|input pin 1 off
+
|input pin N off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 1 on
+
|input pin N on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|}
−
|0
+
 
−
|R
+
----
−
|input pin 2 off
+
 
−
|-
+
=== MOD32IN ===
−
|1
+
 
−
|R
+
32 digital input module for NO contacts in modular housing.
−
|input pin 2 on
+
 
 +
It uses one addresses of the Contatto bus and four channels, one for each group of 8 inputs.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="2"|i<address>.N
 +
N=1-32
 
|0
 
|0
 
|R
 
|R
−
|input pin 3 off
+
|input pin N off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 3 on
+
|input pin N on
 +
|-
 +
 
 +
|}
 +
 
 +
----
 +
 
 +
=== MOD8INP2/A ===
 +
 
 +
8 digital input module for NO contacts.
 +
 
 +
It uses one input address of the Contatto bus.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="2"|i<address>.1
 
|0
 
|0
 
|R
 
|R
−
|input pin 4 off
+
|input pin 1 off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 4 on
+
|input pin 1 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.5
+
|rowspan="2"|i<address>.2
 
|0
 
|0
 
|R
 
|R
−
|input pin 5 off
+
|input pin 2 off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 5 on
+
|input pin 2 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.6
+
|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
 +
|-
 +
 
 +
|rowspan="2"|i<address>.5
 +
|0
 +
|R
 +
|input pin 5 off
 +
|-
 +
|1
 +
|R
 +
|input pin 5 on
 +
|-
 +
 
 +
|rowspan="2"|i<address>.6
 
|0
 
|0
 
|R
 
|R
Line 858: Line 1,066:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.7
+
|rowspan="2"|i<address>.7
 
|0
 
|0
 
|R
 
|R
Line 868: Line 1,076:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.8
+
|rowspan="2"|i<address>.8
 
|0
 
|0
 
|R
 
|R
Line 878: Line 1,086:
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MOD8INP2/C ===
 
=== MOD8INP2/C ===
  
 
8 digital input module for NC contacts.
 
8 digital input module for NC contacts.
 +
 
It uses one input address of the Contatto bus.
 
It uses one input address of the Contatto bus.
  
Line 891: Line 1,102:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|i<address>.1
 
|0
 
|0
 
|R
 
|R
Line 901: Line 1,112:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|rowspan="2"|i<address>.2
 
|0
 
|0
 
|R
 
|R
Line 911: Line 1,122:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="2"|i<address>.3
 
|0
 
|0
 
|R
 
|R
Line 921: Line 1,132:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="2"|i<address>.4
 
|0
 
|0
 
|R
 
|R
Line 931: Line 1,142:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.5
+
|rowspan="2"|i<address>.5
 
|0
 
|0
 
|R
 
|R
Line 941: Line 1,152:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.6
+
|rowspan="2"|i<address>.6
 
|0
 
|0
 
|R
 
|R
Line 951: Line 1,162:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.7
+
|rowspan="2"|i<address>.7
 
|0
 
|0
 
|R
 
|R
Line 961: Line 1,172:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.8
+
|rowspan="2"|i<address>.8
 
|0
 
|0
 
|R
 
|R
Line 971: Line 1,182:
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MOAN/I ===
 
=== MOAN/I ===
  
 
0÷10V analog input module.
 
0÷10V analog input module.
 +
 
It uses one input address in the range 1 to 127 of the Contatto bus.
 
It uses one input address in the range 1 to 127 of the Contatto bus.
  
Line 985: Line 1,199:
  
 
|i<address>.1
 
|i<address>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|voltage value divided in 255 steps
 
|voltage value divided in 255 steps
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MOAN/I4 ===
 
=== MOAN/I4 ===
  
 
Quad 0÷10V analog input module.
 
Quad 0÷10V analog input module.
 +
 
It uses four consecutive addresses of the Contatto bus, one for each input.
 
It uses four consecutive addresses of the Contatto bus, one for each input.
  
Line 1,004: Line 1,221:
  
 
|i<address>.1
 
|i<address>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|voltage value divided in 255 steps
 
|voltage value divided in 255 steps
Line 1,010: Line 1,227:
  
 
|i<address+1>.1
 
|i<address+1>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|voltage value divided in 255 steps
 
|voltage value divided in 255 steps
Line 1,016: Line 1,233:
  
 
|i<address+2>.1
 
|i<address+2>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|voltage value divided in 255 steps
 
|voltage value divided in 255 steps
Line 1,022: Line 1,239:
  
 
|i<address+3>.1
 
|i<address+3>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|voltage value divided in 255 steps
 
|voltage value divided in 255 steps
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MI420 ===
 
=== MI420 ===
  
 
4÷20mA analog input module.
 
4÷20mA analog input module.
 +
 
It uses one input address in the range 1 to 127 of the Contatto bus.
 
It uses one input address in the range 1 to 127 of the Contatto bus.
  
Line 1,041: Line 1,261:
  
 
|i<address>.1
 
|i<address>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|current value divided in 255 steps
 
|current value divided in 255 steps
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MI420-X4 ===
 
=== MI420-X4 ===
  
 
Quad 4÷20mA analog input module.
 
Quad 4÷20mA analog input module.
 +
 
It uses four consecutive addresses of the Contatto bus, one for each input.
 
It uses four consecutive addresses of the Contatto bus, one for each input.
  
Line 1,060: Line 1,283:
  
 
|i<address>.1
 
|i<address>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|current value divided in 255 steps
 
|current value divided in 255 steps
Line 1,066: Line 1,289:
  
 
|i<address+1>.1
 
|i<address+1>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|current value divided in 255 steps
 
|current value divided in 255 steps
Line 1,072: Line 1,295:
  
 
|i<address+2>.1
 
|i<address+2>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|current value divided in 255 steps
 
|current value divided in 255 steps
Line 1,078: Line 1,301:
  
 
|i<address+3>.1
 
|i<address+3>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|current value divided in 255 steps
 
|current value divided in 255 steps
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MOD4AM12/V/I ===
 
=== MOD4AM12/V/I ===
  
 
4-channel 0÷10V or 4÷20mA (0÷21mA) analog input module.
 
4-channel 0÷10V or 4÷20mA (0÷21mA) analog input module.
 +
 
It uses one input address of the Contatto bus.
 
It uses one input address of the Contatto bus.
  
Line 1,097: Line 1,323:
  
 
|i<address>.1
 
|i<address>.1
−
|0...4095
+
|0 ... 4095
 
|R
 
|R
 
|measurement range divided in 4095 steps
 
|measurement range divided in 4095 steps
Line 1,103: Line 1,329:
  
 
|i<address>.2
 
|i<address>.2
−
|0...4095
+
|0 ... 4095
 
|R
 
|R
 
|measurement range divided in 4095 steps
 
|measurement range divided in 4095 steps
Line 1,109: Line 1,335:
  
 
|i<address>.3
 
|i<address>.3
−
|0...4095
+
|0 ... 4095
 
|R
 
|R
 
|measurement range divided in 4095 steps
 
|measurement range divided in 4095 steps
Line 1,115: Line 1,341:
  
 
|i<address>.4
 
|i<address>.4
−
|0...4095
+
|0 ... 4095
 
|R
 
|R
 
|measurement range divided in 4095 steps
 
|measurement range divided in 4095 steps
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MOD2PT ===
 
=== MOD2PT ===
  
 
Input module for two PT100 temperature probes.
 
Input module for two PT100 temperature probes.
−
It uses one or two addresses according to how the dip-switch is set. If both channels are enabled (IN1 and IN2), setting the n “base” address through the FXPRO programmer, the input address and address+1 (consecutive) will be automatically assigned to the module.   
+
 
 +
It uses one or two addresses according to how the dip-switch is set.  
 +
 
 +
If both channels are enabled (IN1 and IN2), setting the n “base” address through the FXPRO programmer, the input address and address+1 (consecutive) will be automatically assigned to the module.   
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,134: Line 1,365:
  
 
|i<address>.1
 
|i<address>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|range –40 ÷ +87.5°C: code 0 corresponds to  –40°C and code 255 corresponds to +87.5°C
 
|range –40 ÷ +87.5°C: code 0 corresponds to  –40°C and code 255 corresponds to +87.5°C
Line 1,140: Line 1,371:
  
 
|i<address+1>.1
 
|i<address+1>.1
−
|0...255
+
|0 ... 255
 
|R
 
|R
 
|range –40 ÷ +87.5°C: code 0 corresponds to  –40°C and code 255 corresponds to +87.5°C
 
|range –40 ÷ +87.5°C: code 0 corresponds to  –40°C and code 255 corresponds to +87.5°C
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MODCNT ===
 
=== MODCNT ===
  
 
4-channel counter module in modular housing.
 
4-channel counter module in modular housing.
 +
 
It uses one input address of the Contatto bus.
 
It uses one input address of the Contatto bus.
  
Line 1,159: Line 1,393:
  
 
|i<address>.1
 
|i<address>.1
−
|0...65535
+
|0 ... 65535
 
|R
 
|R
 
|number of pulses
 
|number of pulses
Line 1,165: Line 1,399:
  
 
|i<address>.2
 
|i<address>.2
−
|0...65535
+
|0 ... 65535
 
|R
 
|R
 
|number of pulses
 
|number of pulses
Line 1,171: Line 1,405:
  
 
|i<address>.3
 
|i<address>.3
−
|0...65535
+
|0 ... 65535
 
|R
 
|R
 
|number of pulses
 
|number of pulses
Line 1,177: Line 1,411:
  
 
|i<address>.4
 
|i<address>.4
−
|0...65535
+
|0 ... 65535
 
|R
 
|R
 
|number of pulses
 
|number of pulses
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MODNTC ===
 
=== MODNTC ===
  
 
Input module for ambient temperature sensors and potentiometers.
 
Input module for ambient temperature sensors and potentiometers.
 +
 
It uses one input address of the Contatto bus.
 
It uses one input address of the Contatto bus.
−
The temperature values measured by MODNTC module are reported as Kelvin degrees multiplied by 10; in other words, 0°C will be reported as 2730, 0.1°C will be reported as 2731 and so on. Concerning the potentiometer channels, the values read from the module will be 0 with the potentiometer at its minimum position and it will be 1000 with the potentiometer at its maximum position.
+
 
 +
The temperature values measured by MODNTC module are reported as Kelvin degrees multiplied by 10; in other words, 0°C will be reported as 2730, 0.1°C will be reported as 2731 and so on.  
 +
 
 +
Concerning the potentiometer channels, the values read from the module will be 0 with the potentiometer at its minimum position and it will be 1000 with the potentiometer at its maximum position.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,197: Line 1,437:
  
 
|i<address>.1
 
|i<address>.1
−
|0...4095
+
|0 ... 4095
 
|R
 
|R
 
|temperature value
 
|temperature value
Line 1,203: Line 1,443:
  
 
|i<address>.2
 
|i<address>.2
−
|0...4095
+
|0 ... 4095
 
|R
 
|R
 
|temperature value
 
|temperature value
Line 1,209: Line 1,449:
  
 
|i<address>.3
 
|i<address>.3
−
|0...4095
+
|0 ... 4095
 
|R
 
|R
 
|temperature value
 
|temperature value
Line 1,215: Line 1,455:
  
 
|i<address>.4
 
|i<address>.4
−
|0...4095
+
|0 ... 4095
 
|R
 
|R
 
|temperature value
 
|temperature value
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MOD4I/A ===
 
=== MOD4I/A ===
  
 
4-digital input module for NO contacts in modular housing.
 
4-digital input module for NO contacts in modular housing.
 +
 
It uses one input address in the range 1 to 127 of the Contatto bus.
 
It uses one input address in the range 1 to 127 of the Contatto bus.
  
Line 1,233: Line 1,476:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>
+
|rowspan="2"|i<address>
 
|0
 
|0
 
|R
 
|R
Line 1,243: Line 1,486:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>
+
|rowspan="2"|i<address+1>
 
|0
 
|0
 
|R
 
|R
Line 1,253: Line 1,496:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>
+
|rowspan="2"|i<address+2>
 
|0
 
|0
 
|R
 
|R
Line 1,263: Line 1,506:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>
+
|rowspan="2"|i<address+3>
 
|0
 
|0
 
|R
 
|R
Line 1,273: Line 1,516:
 
|-
 
|-
 
|}
 
|}
 +
 +
----
  
 
=== MOD4I/S ===
 
=== MOD4I/S ===
  
 
4-digital input module for NO contacts in 2M modular housing.
 
4-digital input module for NO contacts in 2M modular housing.
 +
 
It uses one address of the Contatto bus.
 
It uses one address of the Contatto bus.
  
Line 1,286: Line 1,532:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>
+
|rowspan="2"|i<address>
 
|0
 
|0
 
|R
 
|R
Line 1,296: Line 1,542:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>
+
|rowspan="2"|i<address+1>
 
|0
 
|0
 
|R
 
|R
Line 1,306: Line 1,552:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>
+
|rowspan="2"|i<address+2>
 
|0
 
|0
 
|R
 
|R
Line 1,316: Line 1,562:
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>
+
|rowspan="2"|i<address+3>
 
|0
 
|0
 
|R
 
|R
Line 1,327: Line 1,573:
 
|}
 
|}
  
−
=== 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.
+
=== MODLUX ===
 +
 
 +
Ambient light measurement module with sensor for ceiling mounting.  
 +
 
 +
It uses one address of the Contatto bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,338: Line 1,588:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|i<address>.1
−
|0
+
|0 ... 1023
 
|R
 
|R
−
|input pin 1 off
+
|ambient brightness value
−
|-
 
−
|1
 
−
|R
 
−
|input pin 1 on
 
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|}
−
|0
+
 
−
|R
+
----
−
|input pin 2 off
 
−
|-
 
−
|1
 
−
|R
 
−
|input pin 2 on
 
−
|-
 
  
−
|rowspan="2"|i.<address>.3
+
=== MODMETEO ===
−
|0
+
 
−
|R
+
Meteorological data detection module for Contatto bus.
−
|input pin 3 off
+
 
 +
It uses one input address and, if enabled by the configuration panel of MCP IDE, one output address with the same value.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
−
|1
+
 
 +
|i<address>.temp
 +
|<temp>
 
|R
 
|R
−
|input pin 3 on
+
|temperature value (in C/10)
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|i<address>.lux
−
|0
+
|<lux*10>
 
|R
 
|R
−
|input pin 4 off
+
|daylight value in tens of LUX
 
|-
 
|-
−
|1
+
 
 +
|i<address>.wind
 +
|1 m/s / 10
 
|R
 
|R
−
|input pin 4 on
+
|wind speed value
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.5
+
|rowspan="2"|i<address>.rain
 
|0
 
|0
 
|R
 
|R
−
|input pin 5 off
+
|no rain
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 5 on
+
|rain
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.6
+
|rowspan="2"|i<address>.night
 
|0
 
|0
 
|R
 
|R
−
|input pin 6 off
+
|day
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 6 on
+
|night
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.7
+
|rowspan="2"|i<address>.temp.limit
 
|0
 
|0
 
|R
 
|R
−
|input pin 7 off
+
|measured temperature <  threshold
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 7 on
+
|measured temperature >  threshold
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.8
+
|rowspan="2"|i<address>.lux.limit
 
|0
 
|0
 
|R
 
|R
−
|input pin 8 off
+
|measured daylight <  threshold
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 8 on
+
|measured daylight >  threshold
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.9
+
|rowspan="2"|i<address>.wind.limit
 
|0
 
|0
 
|R
 
|R
−
|input pin 9 off
+
|measured wind speed <  threshold
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 9 on
+
|measured wind speed >  threshold
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.10
+
|rowspan="2"|i<address>.light.south
 
|0
 
|0
 
|R
 
|R
−
|input pin 10 off
+
|light not from South
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 10 on
+
|light from South
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.11
+
|rowspan="2"|i<address>.light.west
 
|0
 
|0
 
|R
 
|R
−
|input pin 11 off
+
|light not from West
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 11 on
+
|light from West
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.12
+
|rowspan="2"|i<address>.light.east
 
|0
 
|0
 
|R
 
|R
−
|input pin 12 off
+
|light not from East
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 12 on
+
|light from East
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.13
+
|rowspan="2"|i<address>.fault
 
|0
 
|0
 
|R
 
|R
−
|input pin 13 off
+
|sensor works correctly
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 13 on
+
|sensor failure
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.14
+
|rowspan="2"|o<address>.temp
−
|0
+
|<temp>
−
|R
+
|RW
−
|input pin 14 off
+
|temperature threshold (in C/10)
 
|-
 
|-
−
|1
+
|off
−
|R
+
|RW
−
|input pin 14 on
+
|temperature threshold off
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.15
+
|rowspan="2"|o<address>.lux
−
|0
+
|<lux*10>
−
|R
+
|RW
−
|input pin 15 off
+
|daylight threshold
 +
|-
 +
|off
 +
|RW
 +
|daylight threshold off
 +
|-
 +
 
 +
|rowspan="2"|o<address>.wind
 +
|1 m/s / 10
 +
|RW
 +
|wind speed threshold
 
|-
 
|-
−
|1
+
|off
−
|R
+
|RW
−
|input pin 15 on
+
|wind speed threshold off
 
|-
 
|-
 +
 
|}
 
|}
  
−
=== DF8I ===
+
----
−
The DF8I is an input module with 2x4 digital inputs.
+
 
−
It uses two consecutive addresses in the DOMINO bus.
+
=== MOD8R ===
 +
 
 +
8 power relay output module.
 +
 
 +
It uses one output address of the Contatto bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,500: Line 1,766:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|o<address>.1
 
|0
 
|0
−
|R
+
|RW
−
|input pin 1 off
+
|output pin 1 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 1 on
+
|output pin 1 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|rowspan="2"|o<address>.2
 
|0
 
|0
−
|R
+
|RW
−
|input pin 2 off
+
|output pin 2 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 2 on
+
|output pin 2 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="2"|o<address>.3
 
|0
 
|0
−
|R
+
|RW
−
|input pin 3 off
+
|output pin 3 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 3 on
+
|output pin 3 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="2"|o<address>.4
 
|0
 
|0
−
|R
+
|RW
−
|input pin 4 off
+
|output pin 4 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 4 on
+
|output pin 4 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.1
+
|rowspan="2"|o<address>.5
 
|0
 
|0
−
|R
+
|RW
−
|input pin 1 off
+
|output pin 5 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 1 on
+
|output pin 5 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.2
+
|rowspan="2"|o<address>.6
 
|0
 
|0
−
|R
+
|RW
−
|input pin 2 off
+
|output pin 6 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 2 on
+
|output pin 6 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.3
+
|rowspan="2"|o<address>.7
 
|0
 
|0
−
|R
+
|RW
−
|input pin 3 off
+
|output pin 7 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 3 on
+
|output pin 7 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.4
+
|rowspan="2"|o<address>.8
 
|0
 
|0
−
|R
+
|RW
−
|input pin 4 off
+
|output pin 8 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 4 on
+
|output pin 8 on
 
|-
 
|-
 
|}
 
|}
  
−
=== DF2R ===
+
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
−
The DF2R is an output module with 2 relay outputs.
+
 
−
It uses one address in the DOMINO bus.
+
----
 +
 
 +
=== MODPNP ===
 +
 
 +
8 positive logic (PNP) “open collector” digital output module.
 +
 
 +
It uses one output address in the range 1 to 127 of the Contatto bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,592: Line 1,864:
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.1
+
|rowspan="2"|o<address>.1
−
|0<br/>off
+
|0
 
|RW
 
|RW
 
|output pin 1 off
 
|output pin 1 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
 
|output pin 1 on
 
|output pin 1 on
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.2
+
|rowspan="2"|o<address>.2
−
|0<br/>off
+
|0
 
|RW
 
|RW
 
|output pin 2 off
 
|output pin 2 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
 
|output pin 2 on
 
|output pin 2 on
 
|-
 
|-
−
|}
 
  
−
=== DF4R, DF4RP ===
+
|rowspan="2"|o<address>.3
−
The DF4R (DF4RP) is an output module with 4 relay outputs.
+
|0
−
It uses one address in the DOMINO bus.
+
|RW
 +
|output pin 3 off
 +
|-
 +
|1
 +
|RW
 +
|output pin 3 on
 +
|-
  
−
{| class="wikitable"
+
|rowspan="2"|o<address>.4
−
!ID
+
|0
−
!Value
+
|RW
−
!R/W
+
|output pin 4 off
−
!Description
+
|-
 +
|1
 +
|RW
 +
|output pin 4 on
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.1
+
|rowspan="2"|o<address>.5
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|output pin 1 off
+
|output pin 5 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|output pin 1 on
+
|output pin 5 on
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.2
+
|rowspan="2"|o<address>.6
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|output pin 2 off
+
|output pin 6 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|output pin 2 on
+
|output pin 6 on
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.3
+
|rowspan="2"|o<address>.7
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|output pin 3 off
+
|output pin 7 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|output pin 3 on
+
|output pin 7 on
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.4
+
|rowspan="2"|o<address>.8
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|output pin 4 off
+
|output pin 8 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|output pin 4 on
+
|output pin 8 on
 
|-
 
|-
 
|}
 
|}
  
−
=== DF4RP/I ===
+
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
−
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.
+
----
 +
 
 +
=== MODREL ===
 +
 
 +
8 relay output compact module in DIN 3M housing.
 +
 
 +
It uses one output address in the range 1 to 127 of the Contatto bus.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,676: Line 1,962:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|o<address>.1
 
|0
 
|0
−
|R
+
|RW
−
|input pin 1 off
+
|output pin 1 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 1 on
+
|output pin 1 on
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.1
+
|rowspan="2"|o<address>.2
 
|0
 
|0
 
|RW
 
|RW
−
|output pin 1 off
+
|output pin 2 off
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
−
|output pin 1 on
+
|output pin 2 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|rowspan="2"|o<address>.3
 
|0
 
|0
−
|R
+
|RW
−
|input pin 2 off
+
|output pin 3 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 2 on
+
|output pin 3 on
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.2
+
|rowspan="2"|o<address>.4
 
|0
 
|0
 
|RW
 
|RW
−
|output pin 2 off
+
|output pin 4 off
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
−
|output pin 2 on
+
|output pin 4 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="2"|o<address>.5
 
|0
 
|0
−
|R
+
|RW
−
|input pin 3 off
+
|output pin 5 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 3 on
+
|output pin 5 on
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.3
+
|rowspan="2"|o<address>.6
 
|0
 
|0
 
|RW
 
|RW
−
|output pin 3 off
+
|output pin 6 off
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
−
|output pin 3 on
+
|output pin 6 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="2"|o<address>.7
 
|0
 
|0
−
|R
+
|RW
−
|input pin 4 off
+
|output pin 7 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 4 on
+
|output pin 7 on
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.4
+
|rowspan="2"|o<address>.8
 
|0
 
|0
 
|RW
 
|RW
−
|output pin 4 off
+
|output pin 8 off
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
−
|output pin 4 on
+
|output pin 8 on
 
|-
 
|-
 
|}
 
|}
  
−
=== DFDM, DFDI, DFDI2, DFDI2B, DFDT ===
+
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
−
The DFDM, DFDI, DFDI2, DFDI2B and DFDT are output modules with 1 dimmer output.
 
−
They use one address in the DOMINO bus.
 
  
−
{| class="wikitable"
+
----
 +
 
 +
=== MOAN/U ===
 +
 
 +
0÷10V analog output module.
 +
 
 +
It uses one output address in the range 1 to 127 of the Contatto bus.
 +
 
 +
{| class="wikitable"
 
!ID
 
!ID
 
!Value
 
!Value
Line 1,768: Line 2,060:
 
|-
 
|-
  
−
|rowspan="4"|o.<address>
+
|o<address>
−
|program
+
|x/255
 
|R
 
|R
−
|program mode
+
|value in fractional format, where 0 &le; x &le; 255
 
|-
 
|-
−
|fault
+
 
−
|R
+
|rowspan="3"|o<address>
−
|dimmer fault
+
|<x%>
 +
|W
 +
|the percentage of signal (0÷100%) applied to the output
 
|-
 
|-
−
|auto
+
|0...255
−
|R
+
|W
−
|auto mode
+
|convert the 8 bits digital code received through the bus in the proper analog level.
 
|-
 
|-
−
|man
+
|x/y
−
|R
+
|W
−
|manual mode
+
|fractional format, formatted as “x/y”, where 0 &le; x &le; y
 
|-
 
|-
 +
|}
 +
 +
----
 +
 +
=== MO420 ===
 +
 +
4÷20mA analog output module.
 +
 +
It uses one output address in the range 1 to 127 of the Contatto bus.
  
−
|rowspan="3"|o.<address>.1
+
{| class="wikitable"
−
|off
+
!ID
−
|RW
+
!Value
−
|dimmer off
+
!R/W
−
|-
+
!Description
−
|1...100%
 
−
|RW
 
−
|percent dimmer level
 
−
|-
 
−
|on
 
−
|RW
 
−
|dimmer on at last level
 
 
|-
 
|-
  
−
|rowspan="3"|o.<address>.ramp
+
|rowspan="3"|o<address>
−
|save
+
|<x%>
 
|RW
 
|RW
−
|saves the current ramp as default
+
|the percentage of signal (0÷100%) applied to the output
 
|-
 
|-
−
|1...30
+
|0...255
 
|RW
 
|RW
−
|ramp value in seconds (1 sec steps up to 10 and 2 sec steps up to 30)
+
|convert the 8 bits digital code received through the bus in the proper analog level
 
|-
 
|-
−
|40, 50, 60
+
|x/y
 
|RW
 
|RW
−
|ramp value in seconds (10 sec steps)
+
|fractional format, formatted as “x/y”, where 0 &le; x &le; y
 
|-
 
|-
 +
|}
  
−
|o.<address>.setpoint
+
----
−
|0...1023
 
−
|RW
 
−
|setpoint level
 
−
|-
 
  
−
|o.<address>.hysteresis
+
=== MODLC and MODLC-P ===
−
|0...255
 
−
|RW
 
−
|tolerance level
 
−
|-
 
  
−
|o.<address>.time
+
Ambient light regulator module with integrated sensor.
−
|0...255
 
−
|RW
 
−
|period (seconds)
 
−
|-
 
−
|}
 
  
−
The dimmer level can be set using additional formats besides the standard percent values:
+
It uses one input address and, if enabled by the configuration panel of MCP IDE, one output address with the same value.
−
- 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,849: Line 2,126:
 
|-
 
|-
  
−
|o.<address>.<command>
+
|i<address>.lux
−
|0...255
+
|value equivalent to three times the brightness in lux detected by the sensor
−
|RW
+
|R
−
|commands and values according to the DFDMX programming manual
+
|the brightness value in lux detected by the MODLC
 
|-
 
|-
−
|}
 
  
−
=== DFDALI ===
+
|i<address>.level
−
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.
+
|calculated value for the automatic brightness regulation
−
It uses one input (if enabled) and one output address in the DOMINO bus.
+
|R
 +
|the value to be sent to the dimmer in order to execute the automatic regulation
 +
|-
  
−
{| class="wikitable"
+
|rowspan="2"|i<address>.mode
−
!ID
+
|auto
−
!Value
+
|R
−
!R/W
+
|automatic regulation
−
!Description
 
 
|-
 
|-
−
 
+
|man
−
|o.<address>
+
|R
−
|refresh
+
|manual regulation
−
|RW
 
−
|queries the DFDALI module to update the current status of all DALI devices
 
 
|-
 
|-
  
−
|o.<address>
+
|rowspan="2"|i<address>.in
−
|off
+
|0
−
|RW
+
|R
−
|broadcast off command
+
|digital input 2 (including presence delay) OFF
 
|-
 
|-
−
 
+
|1
−
|o.<address>.all
+
|R
−
o.<address>.0
+
|digital input 2 (including presence delay) ON
−
|<level>
 
−
|RW
 
−
|broadcast level command
 
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.group.<DALI group>
+
|rowspan="2"|i<address>.in1
−
|off
+
|0
−
|RW
+
|R
−
|broadcast off command
+
|digital input 1 OFF
 
|-
 
|-
−
|<level>
+
|1
−
|RW
+
|R
−
|group level command
+
|digital input 1 ON
 
|-
 
|-
  
−
|rowspan="3"|o.<address>.<DALI address>
+
|rowspan="2"|i<address>.in2
−
|off
+
|0
 +
|R
 +
|digital input 2 OFF
 +
|-
 +
|1
 +
|R
 +
|digital input 2 ON
 +
|-
 +
 
 +
|o<address>.setpoint
 +
|setpoint value
 
|RW
 
|RW
−
|turn off a single device
+
|set the setpoint for the automatic brightness regulation
 
|-
 
|-
−
|<level>
+
 
 +
|o<address>.preset
 +
|setpoint value
 
|RW
 
|RW
−
|set a single device to a specific level
+
|set the preset dimmer value (SMART mode only)
 
|-
 
|-
−
|> 100
+
 
 +
|o<address>.delay
 +
|setpoint value
 
|RW
 
|RW
−
|special functions, having values between 101 and 255, as defined in the DFDALI manual
+
|set the presence detector delay in seconds
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.polling
+
|rowspan="2"|o<address>.mode
−
|off
+
|auto
 +
|RW
 +
|set automatic control
 +
|-
 +
|man
 
|RW
 
|RW
−
|polling mode is disabled
+
|set manual control
 +
|-
 +
 
 +
|rowspan="2"|o<address>.in.reset
 +
|0
 +
|R
 +
|not active
 
|-
 
|-
−
|on
+
|1
 
|RW
 
|RW
−
|polling mode is enabled
+
|force the expiring of the deactivation delay time of the digital input
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.test
+
|rowspan="2"|o<address>.mode.reset
 
|0
 
|0
 
|RW
 
|RW
−
|test button not pressed
+
|not active
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
−
|test button pressed
+
|disable automatic control
 
|-
 
|-
  
−
|rowspan="4"|i.<address>.dali
+
|rowspan="2"|o<address>.full.reset
−
|nopower
+
|0
 
|RW
 
|RW
−
|power failure on the DALI bus
+
|not active
 
|-
 
|-
−
|open
+
|1
 
|RW
 
|RW
−
|DALI bus is open
+
|perform a full reset
 
|-
 
|-
−
|short
+
 
 +
|rowspan="2"|o<address>.v
 +
|0
 
|RW
 
|RW
−
|DALI bus is shorted
+
|virtual point off
 
|-
 
|-
−
|on
+
|1
 
|RW
 
|RW
−
|DALI bus on
+
|virtual point on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|o<address>.in.disable
−
|fault
+
|0
 
|RW
 
|RW
−
|DALI device 1 reporting a lamp failure
+
|normal presence detector operation (SMART mode)
 
|-
 
|-
−
|unknown
+
|1
 
|RW
 
|RW
−
|DALI device 1 status unknown
+
|disable light ON control from presence detector (SMART mode)
 
|-
 
|-
−
|}
 
  
−
The DALI level can be set using additional formats besides the standard percent values:
+
|rowspan="2"|o<address>.presence
−
- absolute positive integer number between 0 and 100
+
|0
−
- percent number, formatted as x%
+
|RW
−
- fractional format, formatted as “n/m”, where 0 <= n <= m
+
|not active
−
- 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
 
−
|dimmer off
 
−
|-
 
−
|1...100%
 
−
|RW
 
−
|percent dimmer level
 
−
|-
 
−
|on
 
−
|RW
 
−
|dimmer on at last level
 
−
|-
 
−
 
 
−
|rowspan="2"|o.<address>.2
 
−
|0
 
−
|RW
 
−
|output pin 1 off
 
 
|-
 
|-
 
|1
 
|1
 
|RW
 
|RW
−
|output pin 1 on
+
|presence forced
 
|-
 
|-
 
|}
 
|}
  
−
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.
+
=== MOD4-4S ===
−
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
+
 
 +
4 digital input and 4 power relay output multifunction module.
 +
 
 +
HSYCO supports two configurations only: four independent outputs, or two shutters.
 +
 
 +
When set as four independent outputs, the module must be configured with the same base address for input and output.
 +
 
 +
For example:
 +
<pre>
 +
(I20, O20)
 +
</pre>
 +
The input address must be enabled. Configuration switches must be set as SW1=OFF, SW2=OFF and SW5=ON.
  
−
=== DFTP ===
+
When set as two shutters, the module must be configured with the same base address for input and output.  
−
The DFTP is an output module for 2 shutters.
+
 
−
It uses one output address in the DOMINO bus.
+
For example:
 +
<pre>
 +
(I20, O20, O21)
 +
</pre>
 +
The input address must be enabled. Configuration switches must be set as SW1=ON, SW2=ON and SW5=ON.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,017: Line 2,298:
 
|-
 
|-
  
−
|rowspan="6"|o.<address>.1
+
|rowspan="2"|i<address>.1
−
|up
+
|0
−
|RW
+
|R
−
|shutter up command
+
|input pin 1 off
 
|-
 
|-
−
|down
+
|1
−
|RW
+
|R
 +
|input pin 1 on
 +
|-
 +
 
 +
|rowspan="2"|i<address>.2
 +
|0
 +
|R
 +
|input pin 2 off
 +
|-
 +
|1
 +
|R
 +
|input pin 2 on
 +
|-
 +
 
 +
|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
 +
|-
 +
 
 +
|rowspan="6"|o<address>.1
 +
|up
 +
|RW
 +
|shutter up command
 +
|-
 +
|down
 +
|RW
 
|shutter down command
 
|shutter down command
 
|-
 
|-
−
|stop<br/>off<br/>0
+
|stop
 
|RW
 
|RW
 
|shutter stop command
 
|shutter stop command
 
|-
 
|-
 
|unknown
 
|unknown
−
|RW
+
|R
 
|unknown state
 
|unknown state
 
|-
 
|-
 
|offup
 
|offup
−
|RW
+
|R
 
|shutter off, up position
 
|shutter off, up position
 
|-
 
|-
 
|offdown
 
|offdown
−
|RW
+
|R
 
|shutter off, down position
 
|shutter off, down position
 
|-
 
|-
  
−
|rowspan="6"|o.<address>.2
+
|rowspan="6"|o<address+1>.1
 
|up
 
|up
 
|RW
 
|RW
Line 2,052: Line 2,373:
 
|shutter down command
 
|shutter down command
 
|-
 
|-
−
|stop<br/>off<br/>0
+
|stop
 
|RW
 
|RW
 
|shutter stop command
 
|shutter stop command
 
|-
 
|-
 
|unknown
 
|unknown
−
|RW
+
|R
 
|unknown state
 
|unknown state
 
|-
 
|-
 
|offup
 
|offup
−
|RW
+
|R
 
|shutter off, up position
 
|shutter off, up position
 
|-
 
|-
 
|offdown
 
|offdown
−
|RW
+
|R
 
|shutter off, down position
 
|shutter off, down position
 
|-
 
|-
  
−
|}
+
|rowspan="2"|o<address>.1
−
 
 
−
=== 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.
 
−
 
 
−
{| class="wikitable"
 
−
!ID
 
−
!Value
 
−
!R/W
 
−
!Description
 
−
|-
 
−
 
 
−
|rowspan="2"|i.<address>.1
 
 
|0
 
|0
−
|R
+
|RW
−
|input pin 1 off
+
|output pin 1 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
−
|input pin 1 on
+
|output pin 1 on
 
|-
 
|-
  
−
|rowspan="6"|o.<address>.1
+
|rowspan="2"|o<address>.2
−
|up
+
|0
 
|RW
 
|RW
−
|shutter up command
+
|output pin 2 off
 
|-
 
|-
−
|down
+
|1
 
|RW
 
|RW
−
|shutter down command
+
|output pin 2 on
 
|-
 
|-
−
|stop<br/>off<br/>0
+
 
 +
|rowspan="2"|o<address>.3
 +
|0
 
|RW
 
|RW
−
|shutter stop command
+
|output pin 3 off
 
|-
 
|-
−
|unknown
+
|1
 
|RW
 
|RW
−
|unknown state
+
|output pin 3 on
 
|-
 
|-
−
|offup
+
 
 +
|rowspan="2"|o<address>.4
 +
|0
 
|RW
 
|RW
−
|shutter off, up position
+
|output pin 4 off
 
|-
 
|-
−
|offdown
+
|1
 
|RW
 
|RW
−
|shutter off, down position
+
|output pin 4 on
 +
|-
 +
|}
 +
 
 +
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
 +
 
 +
----
 +
 
 +
=== MOD2-2R ===
 +
 
 +
2 digital input and 2 power relay output module.
 +
 
 +
It uses one input address and one output address in the range 1 to 127 of the Contatto bus.
 +
 
 +
The input and the output addresses may be the same or they can be different each one to the other.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 
 +
|rowspan="2"|i<address>.1
 +
|0
 +
|R
 +
|input pin 1 off
 +
|-
 +
|1
 +
|R
 +
|input pin 1 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|rowspan="2"|i<address>.2
 
|0
 
|0
 
|R
 
|R
Line 2,128: Line 2,470:
 
|-
 
|-
  
−
|rowspan="6"|o.<address>.2
+
|rowspan="2"|o<address>.1
−
|up
+
|0
 
|RW
 
|RW
−
|shutter up command
+
|output pin 1 off
 
|-
 
|-
−
|down
+
|1
 
|RW
 
|RW
−
|shutter down command
+
|output pin 1 on
 
|-
 
|-
−
|stop<br/>off<br/>0
+
 
 +
|rowspan="2"|o<address>.2
 +
|0
 
|RW
 
|RW
−
|shutter stop command
+
|output pin 2 off
 
|-
 
|-
−
|unknown
+
|1
 
|RW
 
|RW
−
|unknown state
+
|output pin 2 on
 +
|-
 +
 
 +
|}
 +
 
 +
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
 +
 
 +
----
 +
 
 +
=== MOD4-4R ===
 +
 
 +
4 digital input and 4 digital output module.
 +
 
 +
It uses one input address and one output address in the range 1 to 127 of the Contatto bus.
 +
 
 +
The input and the output addresses may be the same or they can be different each one to the other.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
−
|offup
+
 
−
|RW
+
|rowspan="2"|i<address>.1
−
|shutter off, up position
+
|0
 +
|R
 +
|input pin 1 off
 
|-
 
|-
−
|offdown
+
|1
−
|RW
+
|R
−
|shutter off, down position
+
|input pin 1 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="2"|i<address>.2
 
|0
 
|0
 
|R
 
|R
−
|input pin 3 off
+
|input pin 2 off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 3 on
+
|input pin 2 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="2"|i<address>.3
 
|0
 
|0
 
|R
 
|R
−
|input pin 4 off
+
|input pin 3 off
 
|-
 
|-
 
|1
 
|1
 
|R
 
|R
−
|input pin 4 on
+
|input pin 3 on
 
|-
 
|-
  
−
|}
+
|rowspan="2"|i<address>.4
−
 
+
|0
−
=== DFTR ===
 
−
The DFTR is an output module with 1 shutter output and 1 relay output.
 
−
It uses one address in the DOMINO bus.
 
−
 
 
−
{| class="wikitable"
 
−
!ID
 
−
!Value
 
−
!R/W
 
−
!Description
 
−
|-
 
−
 
 
−
|rowspan="5"|o.<address>.1
 
−
|up
 
 
|R
 
|R
−
|shutter up
+
|input pin 4 off
 
|-
 
|-
−
|down
+
|1
 
|R
 
|R
−
|shutter down
+
|input pin 4 on
 
|-
 
|-
−
|unknown
+
 
−
|R
+
|rowspan="2"|o<address>.1
−
|unknown state
+
|0
 +
|RW
 +
|output pin 1 off
 
|-
 
|-
−
|offup
+
|1
−
|R
+
|RW
−
|shutter offup
+
|output pin 1 on
−
|-
 
−
|offdown
 
−
|R
 
−
|shutter offdown
 
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.2
+
|rowspan="2"|o<address>.2
 
|0
 
|0
−
|R
+
|RW
 
|output pin 2 off
 
|output pin 2 off
 
|-
 
|-
 
|1
 
|1
−
|R
+
|RW
 
|output pin 2 on
 
|output pin 2 on
 
|-
 
|-
  
−
|}
+
|rowspan="2"|o<address>.3
−
 
+
|0
−
=== DF4IL ===
+
|RW
−
The DF4IL is an input/output module with 4 digital inputs and 4 digital open collector outputs for LEDs.
+
|output pin 3 off
−
It uses one input and one output address in the DOMINO bus.
+
|-
−
 
+
|1
 +
|RW
 +
|output pin 3 on
 +
|-
 +
 
 +
|rowspan="2"|o<address>.4
 +
|0
 +
|RW
 +
|output pin 4 off
 +
|-
 +
|1
 +
|RW
 +
|output pin 4 on
 +
|-
 +
 
 +
|}
 +
 
 +
----
 +
 
 +
=== MOD2DM ===
 +
 
 +
2x300W dimmer module.
 +
 
 +
It uses 2 output addresses (one for each dimmer channel) and 2 input addresses.
 +
 
 +
HSYCO supports this module only when its dip-switches are set as SW1=ON, SW2=ON, SW3=ON, SW4=ON.
 +
 
 
{| class="wikitable"
 
{| class="wikitable"
 
!ID
 
!ID
Line 2,232: Line 2,610:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|i<address>
−
|0<br/>off
+
|0...100
 
|R
 
|R
−
|input pin 1 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|R
 
|R
−
|input pin 1 on
+
|dimmer off
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.1
+
|rowspan="2"|i<address+1>
−
|0<br/>off
+
|0...100
−
|RW
 
−
|LED 1 off
 
−
|-
 
−
|1<br/>on
 
−
|RW
 
−
|LED 1 on
 
−
|-
 
−
 
 
−
|rowspan="2"|i.<address>.2
 
−
|0<br/>off
 
 
|R
 
|R
−
|input pin 2 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|R
 
|R
−
|input pin 2 on
+
|dimmer off
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.2
+
|rowspan="3"|o<address>
−
|0<br/>off
+
|0...100
 
|RW
 
|RW
−
|LED 2 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|RW
 
|RW
−
|LED 2 on
+
|dimmer off
 +
|-
 +
|101...255
 +
|W
 +
|command (see MOD2DM commands table)
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="3"|o<address+1>
−
|0<br/>off
+
|0...100
−
|R
 
−
|input pin 3 off
 
−
|-
 
−
|1<br/>on
 
−
|R
 
−
|input pin 3 on
 
−
|-
 
−
 
 
−
|rowspan="2"|o.<address>.3
 
−
|0<br/>off
 
 
|RW
 
|RW
−
|LED 3 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|RW
 
|RW
−
|LED 3 on
+
|dimmer off
 
|-
 
|-
−
 
+
|101...255
−
|rowspan="2"|i.<address>.4
+
|W
−
|0<br/>off
+
|command (see MOD2DM commands table)
−
|R
 
−
|input pin 4 off
 
−
|-
 
−
|1<br/>on
 
−
|R
 
−
|input pin 4 on
 
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.4
 
−
|0<br/>off
 
−
|RW
 
−
|LED 4 off
 
−
|-
 
−
|1<br/>on
 
−
|RW
 
−
|LED 4 on
 
−
|-
 
 
|}
 
|}
  
−
=== DF8IL ===
+
The dimmer level can be set using additional formats besides the standard percent values:
−
The DF8IL is an input/output module with 8 digital inputs and 8 digital open collector outputs for LEDs.
+
*absolute positive integer number between 0 and 100
−
It uses 4 input and 4 output addresses in the DOMINO bus.
+
*percent number, formatted as x%
 +
*fractional format, formatted as “n/m”, where 0 <= n <= m.
 +
 
 +
----
 +
 
 +
=== MOD2DV ===
 +
 
 +
Dual 1-10V output for electronic ballast driving.
 +
 
 +
It uses 2 output addresses (one for each dimmer channel) and 2 input addresses.
 +
 
 +
HSYCO supports this module only when its dip-switches are set as SW1=ON, SW2=ON, SW3=ON, SW4=ON.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,324: Line 2,682:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|i<address>
−
|0<br/>off
+
|0...100
 
|R
 
|R
−
|input pin 1 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|R
 
|R
−
|input pin 1 on
+
|dimmer off
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|rowspan="2"|i<address+1>
−
|0<br/>off
+
|0...100
 
|R
 
|R
−
|input pin 2 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|R
 
|R
−
|input pin 2 on
+
|dimmer off
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="3"|o<address>
−
|0<br/>off
+
|0...100
−
|R
+
|RW
−
|input pin 3 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
−
|R
+
|RW
−
|input pin 3 on
+
|dimmer off
 +
|-
 +
|101...255
 +
|W
 +
|command (see MOD2DV commands table)
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="3"|o<address+1>
−
|0<br/>off
+
|0...100
−
|R
+
|RW
−
|input pin 4 off
+
|brightness level according to current ramp
 +
|-
 +
|off
 +
|RW
 +
|dimmer off
 +
|-
 +
|101...255
 +
|W
 +
|command (see MOD2DV commands table)
 
|-
 
|-
−
|1<br/>on
+
 
−
|R
+
|}
−
|input pin 4 on
+
 
 +
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.
 +
 
 +
----
 +
 
 +
=== MOD8IL ===
 +
 
 +
8 digital input – 8 LED output module for wall box.
 +
 
 +
It uses 1 input address and 1 output address.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.1
+
|rowspan="2"|i<address>.1
−
|0<br/>off
+
|0
 
|R
 
|R
−
|input pin 5 off
+
|input pin 1 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|R
 
|R
−
|input pin 5 on
+
|input pin 1 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.2
+
|rowspan="2"|i<address>.2
−
|0<br/>off
+
|0
 
|R
 
|R
−
|input pin 6 off
+
|input pin 2 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|R
 
|R
−
|input pin 6 on
+
|input pin 2 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.3
+
|rowspan="2"|i<address>.3
−
|0<br/>off
+
|0
 
|R
 
|R
−
|input pin 7 off
+
|input pin 3 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|R
 
|R
−
|input pin 7 on
+
|input pin 3 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+1>.4
+
|rowspan="2"|i<address>.4
−
|0<br/>off
+
|0
 
|R
 
|R
−
|input pin 8 off
+
|input pin 4 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|R
 
|R
−
|input pin 8 on
+
|input pin 4 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.1
+
|rowspan="2"|i<address>.5
−
|0<br/>off
+
|0
 
|R
 
|R
−
|LED 1 is off
+
|input pin 5 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|R
 
|R
−
|LED 1 is on
+
|input pin 5 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.2
+
|rowspan="2"|i<address>.6
−
|0<br/>off
+
|0
 
|R
 
|R
−
|LED 2 is off
+
|input pin 6 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|R
 
|R
−
|LED 2 is on
+
|input pin 6 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.3
+
|rowspan="2"|i<address>.7
−
|0<br/>off
+
|0
 
|R
 
|R
−
|LED 3 is off
+
|input pin 7 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|R
 
|R
−
|LED 3 is on
+
|input pin 7 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+2>.4
+
|rowspan="2"|i<address>.8
−
|0<br/>off
+
|0
 
|R
 
|R
−
|LED 4 is off
+
|input pin 8 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|R
 
|R
−
|LED 4 is on
+
|input pin 8 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.1
+
|rowspan="2"|o<address>.1
−
|0<br/>off
+
|0
−
|R
+
|RW
−
|LED 5 is off
+
|output pin 1 off
 
|-
 
|-
−
|1<br/>on
+
|1
−
|R
+
|RW
−
|LED 5 is on
+
|output pin 1 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.2
+
|rowspan="2"|o<address>.2
−
|0<br/>off
+
|0
−
|R
+
|RW
−
|LED 6 is off
+
|output pin 2 off
 
|-
 
|-
−
|1<br/>on
+
|1
−
|R
+
|RW
−
|LED 6 is on
+
|output pin 2 on
 
|-
 
|-
  
−
|rowspan="2"|i.<address+3>.3
+
|rowspan="2"|o<address>.3
−
|0<br/>off
+
|0
−
|R
 
−
|LED 7 is off
 
−
|-
 
−
|1<br/>on
 
−
|R
 
−
|LED 7 is on
 
−
|-
 
−
 
 
−
|rowspan="2"|i.<address+3>.4
 
−
|0<br/>off
 
−
|R
 
−
|LED 8 is off
 
−
|-
 
−
|1<br/>on
 
−
|R
 
−
|LED 8 is on
 
−
|-
 
−
 
 
−
|rowspan="2"|v.<address+2>.1
 
−
|0<br/>off
 
 
|RW
 
|RW
−
|LED 1 is off
+
|output pin 3 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|LED 1 is on
+
|output pin 3 on
 
|-
 
|-
  
−
|rowspan="2"|v.<address+2>.2
+
|rowspan="2"|o<address>.4
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|LED 2 is off
+
|output pin 4 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|LED 2 is on
+
|output pin 4 on
 
|-
 
|-
  
−
|rowspan="2"|v.<address+2>.3
+
|rowspan="2"|o<address>.5
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|LED 3 is off
+
|output pin 5 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|LED 3 is on
+
|output pin 5 on
 
|-
 
|-
  
−
|rowspan="2"|v.<address+2>.4
+
|rowspan="2"|o<address>.6
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|LED 4 is off
+
|output pin 6 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|LED 4 is on
+
|output pin 6 on
 
|-
 
|-
  
−
|rowspan="2"|v.<address+3>.1
+
|rowspan="2"|o<address>.7
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|LED 5 is off
+
|output pin 7 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|LED 5 is on
+
|output pin 7 on
 
|-
 
|-
  
−
|rowspan="2"|v.<address+3>.2
+
|rowspan="2"|o<address>.8
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|LED 6 is off
+
|output pin 8 off
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|LED 6 is on
+
|output pin 8 on
 
|-
 
|-
 +
|}
  
−
|rowspan="2"|v.<address+3>.3
+
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
−
|0<br/>off
+
 
−
|RW
+
----
−
|LED 7 is off
 
−
|-
 
−
|1<br/>on
 
−
|RW
 
−
|LED 7 is on
 
−
|-
 
  
−
|rowspan="2"|v.<address+3>.4
+
=== MOD4DV ===
−
|0<br/>off
 
−
|RW
 
−
|LED 8 is off
 
−
|-
 
−
|1<br/>on
 
−
|RW
 
−
|LED 8 is on
 
−
|-
 
  
−
|}
+
Quad 0-10V output module for generic applications or for external dimmers control.
  
−
Note that the first two output addresses are reserved and should not be used. Use address + 2 and address + 3 to control the LEDs.
+
It uses 4 consecutive output addresses (one for each dimmer channel) and 4 input addresses.  
  
−
=== DFIGLASS ===
+
HSYCO supports this module only when its dip-switches are set as SW1=ON, SW2=ON, SW3=ON, SW4=ON, SW5=OFF.
−
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.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,579: Line 2,932:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.1
+
|rowspan="2"|i<address>
−
|0<br/>off
+
|0...100
 
|R
 
|R
−
|button 1 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|R
 
|R
−
|button 1 on
+
|dimmer off
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|rowspan="2"|i<address+1>
−
|0<br/>off
+
|0...100
 
|R
 
|R
−
|button 2 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|R
 
|R
−
|button 2 on
+
|dimmer off
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="2"|i<address+2>
−
|0<br/>off
+
|0...100
 
|R
 
|R
−
|button 3 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|R
 
|R
−
|button 3 on
+
|dimmer off
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="2"|i<address+3>
−
|0<br/>off
+
|0...100
 
|R
 
|R
−
|button 4 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|R
 
|R
−
|button 4 on
+
|dimmer off
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.5
+
|rowspan="3"|o<address>
−
|0<br/>off
+
|0...100
−
|R
+
|RW
−
|button 5 off
+
|brightness level according to current ramp
 +
|-
 +
|off
 +
|RW
 +
|dimmer off
 
|-
 
|-
−
|1<br/>on
+
|101...255
−
|R
+
|W
−
|button 5 on
+
|command (see MOD4DV commands table)
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.6
+
|rowspan="3"|o<address+1>
−
|0<br/>off
+
|0...100
−
|R
+
|RW
−
|button 6 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
−
|R
+
|RW
−
|button 6 on
+
|dimmer off
 
|-
 
|-
−
 
+
|101...255
−
|rowspan="2"|i.<address>.fault
+
|W
−
|0<br/>off
+
|command (see MOD4DV commands table)
−
|R
 
−
|no fault
 
−
|-
 
−
|1<br/>on
 
−
|R
 
−
|touch keypad fault
 
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.led.1
+
|rowspan="3"|o<address+2>
−
|0<br/>off
+
|0...100
 
|RW
 
|RW
−
|led 1 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|RW
 
|RW
−
|led 1 on
+
|dimmer off
 +
|-
 +
|101...255
 +
|W
 +
|command (see MOD4DV commands table)
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.led.2
+
|rowspan="3"|o<address+3>
−
|0<br/>off
+
|0...100
 
|RW
 
|RW
−
|led 2 off
+
|brightness level according to current ramp
 
|-
 
|-
−
|1<br/>on
+
|off
 
|RW
 
|RW
−
|led 2 on
+
|dimmer off
 +
|-
 +
|101...255
 +
|W
 +
|command (see MOD4DV commands table)
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.led.3
+
|}
−
|0<br/>off
+
 
−
|RW
+
The dimmer level can be set using additional formats besides the standard percent values:
−
|led 3 off
+
*absolute positive integer number between 0 and 100
−
|-
+
*percent number, formatted as x%
−
|1<br/>on
+
*fractional format, formatted as “x/y”, where 0 <= x <= y
−
|RW
+
*values in the range 101÷255. Values and commands are described in the MOD4DV Programming Handbook (Operation from the bus, page 3).
−
|led 3 on
+
 
 +
----
 +
 
 +
=== MODDMX ===
 +
 
 +
ModDMX module allows to handle, through the Contatto bus, up to 32 DMX devices. ModDMX module makes possible the communication on the first 64 of 512 DMX channels allowed by this protocol.
 +
 
 +
It uses 1 output address, 1-channel 16-bit.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.led.4
+
|o<address>.<DMX address>
−
|0<br/>off
+
|0...100
−
|RW
 
−
|led 4 off
 
−
|-
 
−
|1<br/>on
 
 
|RW
 
|RW
−
|led 4 on
+
|Values and commands are described in the MODDMX Programming Handbook
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.led.5
+
|}
−
|0<br/>off
+
 
−
|RW
+
----
−
|led 5 off
+
 
 +
=== MODDALI ===
 +
 
 +
The ModDALI module supports 4 DALI lines, with up to 32 devices for each line.
 +
The ModDALI module with firmware version 6.x supports 2 DALI lines (channels 1 and 2), with up to 64 devices for each line.
 +
 
 +
It uses 1 output address and, if enabled, 1 input address with the same value.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
−
|1<br/>on
+
 
 +
|o<address>.<line>
 +
|refresh
 
|RW
 
|RW
−
|led 5 on
+
|queries the ModDALI module to update the current status of all DALI devices. This command requires a considerable amount of bus time and blocks all other commands until completed
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.led.6
+
|rowspan="2"|o<address>.<line><br/>o<address>.<line>.all<br/>o<address>.<line>.0
−
|0<br/>off
+
|off
 
|RW
 
|RW
−
|led 6 off
+
|switch off all available DALI devices
 
|-
 
|-
−
|1<br/>on
+
|<level>
 
|RW
 
|RW
−
|led 6 on
+
|set a level for all available devices
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.backlight
+
|rowspan="2"|o<address>.<line>.group.<DALI group>
−
|0<br/>off
+
|off
 
|RW
 
|RW
−
|backlight off
+
|switch off all DALI devices on that group
 
|-
 
|-
−
|1<br/>on
+
|<level>
 
|RW
 
|RW
−
|backlight on
+
|set a level for all DALI devices in that group
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.buzzer
+
|rowspan="5"|o<address>.<line>.<DALI address>
−
|0<br/>off
+
|off
 
|RW
 
|RW
−
|buzzer disabled
+
|switch off a single DALI device
 
|-
 
|-
−
|1<br/>on
+
|<level>
 
|RW
 
|RW
−
|buzzer enabled
+
|set a level for a single DALI device
 
|-
 
|-
−
 
+
|fault
−
|}
+
|R
−
 
+
|DALI device fault
−
=== 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
 
 
|-
 
|-
−
 
+
|unknown
−
|rowspan="2"|i.<address>.1
 
−
|0<br/>off
 
 
|R
 
|R
−
|input pin 1 off
+
|DALI device unknown state (or connection lost)
 
|-
 
|-
−
|1<br/>on
+
|>100
−
|R
+
|RW
−
|input pin 1 on
+
|special functions: possible values are described in the MODDALI Programming Handbook
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.2
+
|rowspan="2"|i<address>.<line>.polling
−
|0<br/>off
+
|off
 
|R
 
|R
−
|input pin 2 off
+
|polling disabled
 
|-
 
|-
−
|1<br/>on
+
|on
 
|R
 
|R
−
|input pin 2 on
+
|polling enabled
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.3
+
|rowspan="2"|i<address>.<line>.test
−
|0<br/>off
+
|0
 
|R
 
|R
−
|input pin 3 off
+
|test button not pressed
 
|-
 
|-
−
|1<br/>on
+
|1
 
|R
 
|R
−
|input pin 3 on
+
|test button pressed
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.4
+
|rowspan="4"|i<address>.<line>.dali
−
|0<br/>off
+
|nopower
 
|R
 
|R
−
|input pin 4 off
+
|DALI bus power supply failure
 
|-
 
|-
−
|1<br/>on
+
|open
 
|R
 
|R
−
|input pin 4 on
+
|DALI line broken
 
|-
 
|-
−
 
+
|short
−
|rowspan="2"|v.<address+1>.1
+
|R
−
|0<br/>off
+
|DALI line short circuit
−
|RW
 
−
|virtual pin 1 off
 
 
|-
 
|-
−
|1<br/>on
+
|on
−
|RW
+
|R
−
|virtual pin 1 on
+
|on DALI line
 
|-
 
|-
  
−
|rowspan="2"|v.<address+1>.2
+
|rowspan="4"|i<address>.<line>.1
−
|0<br/>off
+
|off
−
|RW
+
|R
−
|virtual pin 2 off
+
|ballast 1 off
 
|-
 
|-
−
|1<br/>on
+
|<level>
−
|RW
+
|R
−
|virtual pin 2 on
+
|ballast 1 level
 
|-
 
|-
−
 
+
|fault
−
|rowspan="2"|v.<address+1>.3
+
|R
−
|0<br/>off
+
|ballast 1 lamp failure
−
|RW
 
−
|virtual pin 3 off
 
 
|-
 
|-
−
|1<br/>on
+
|unknown
−
|RW
+
|R
−
|virtual pin 3 on
+
|ballast 1 lamp unknown state (or connection lost)
 
|-
 
|-
  
−
|rowspan="2"|v.<address+1>.4
+
|}
−
|0<br/>off
+
 
−
|RW
+
The DALI device level can be set using additional formats besides the standard percent values:
−
|virtual pin 4 off
+
*absolute positive integer number between 0 and 100
−
|-
+
*percent number, formatted as x%
−
|1<br/>on
+
*fractional format, formatted as “x/y”, where 0 <= x <= y
−
|RW
+
*values in the range 101÷255. Values and commands are described in the MODDALI Programming Handbook.
−
|virtual pin 4 on
+
 
−
|-
+
----
  
−
|rowspan="2"|v.<address+2>.1
+
=== MODDALI8 ===
−
|0<br/>off
+
 
−
|RW
+
The ModDALI8 module allows the management of 8 DALI lines, with up to 16 devices for each line (or channel).
−
|virtual pin 1 off
+
 
−
|-
+
It uses 2 consecutive input addresses and 1 input address with the same base value.
−
|1<br/>on
 
−
|RW
 
−
|virtual pin 1 on
 
−
|-
 
  
−
|rowspan="2"|v.<address+2>.2
+
{| class="wikitable"
−
|0<br/>off
+
!ID
−
|RW
+
!Value
−
|virtual pin 2 off
+
!R/W
−
|-
+
!Description
−
|1<br/>on
 
−
|RW
 
−
|virtual pin 2 on
 
 
|-
 
|-
  
−
|rowspan="2"|v.<address+2>.3
+
|rowspan="2"|o<address>.<line>
−
|0<br/>off
+
|off
 
|RW
 
|RW
−
|virtual pin 3 off
+
|off broadcast command
 
|-
 
|-
−
|1<br/>on
+
|<level>
 
|RW
 
|RW
−
|virtual pin 3 on
+
|level broadcast command
 
|-
 
|-
  
−
|rowspan="2"|v.<address+2>.4
+
|rowspan="2"|i<address>.<line>.polling
−
|0<br/>off
+
|off
 
|RW
 
|RW
−
|virtual pin 4 off
+
|polling disabled
 
|-
 
|-
−
|1<br/>on
+
|on
 
|RW
 
|RW
−
|virtual pin 4 on
+
|polling enabled
 
|-
 
|-
  
−
|rowspan="2"|v.<address+3>.1
+
|rowspan="2"|i<address>.<line>.test
−
|0<br/>off
+
|0
 
|RW
 
|RW
−
|virtual pin 1 off
+
|test button not pressed
 
|-
 
|-
−
|1<br/>on
+
|1
 
|RW
 
|RW
−
|virtual pin 1 on
+
|test button pressed
 
|-
 
|-
  
−
|rowspan="2"|v.<address+3>.2
+
|rowspan="4"|i<address>.<line>.dali
−
|0<br/>off
+
|fault
 
|RW
 
|RW
−
|virtual pin 2 off
+
|lamp failure
 
|-
 
|-
−
|1<br/>on
+
|open
 
|RW
 
|RW
−
|virtual pin 2 on
+
|no DALI device connected to this line
 
|-
 
|-
−
 
+
|short
−
|rowspan="2"|v.<address+3>.3
 
−
|0<br/>off
 
 
|RW
 
|RW
−
|virtual pin 3 off
+
|DALI line short circuit
 
|-
 
|-
−
|1<br/>on
+
|on
 
|RW
 
|RW
−
|virtual pin 3 on
+
|DALI line working correctly
 
|-
 
|-
  
−
|rowspan="2"|v.<address+3>.4
 
−
|0<br/>off
 
−
|RW
 
−
|virtual pin 4 off
 
−
|-
 
−
|1<br/>on
 
−
|RW
 
−
|virtual pin 4 on
 
−
|-
 
 
|}
 
|}
  
−
=== DFAI ===
+
<line> can be set from 1 to 8 to address a single line, or 0 to send commands to all DALI lines.
−
The DFAI is an input module (0-10V) with 2 analog inputs.
+
 
−
It uses two consecutive input addresses in the DOMINO bus.
+
 
 +
The line 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 “x/y”, where 0 <= x <= y
 +
*values in the range 101÷255. Values and commands are described in the MODDALI8 Programming Handbook.
 +
 
 +
----
 +
 
 +
=== CLIMA2 ===
 +
 
 +
Module for the regulation of the ambient temperature.
 +
 
 +
It uses 1 input and 1 output address that are equal each one to the other, so only a base address is needed.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,914: Line 3,276:
 
|-
 
|-
  
−
|i.<address>
+
|rowspan="2"|i<address>
−
|0...1000
+
|on
 
|R
 
|R
−
|input voltage in Volt/100
+
|zone on
 
|-
 
|-
−
 
+
|off
−
|i.<address+1>
 
−
|0...1000
 
 
|R
 
|R
−
|input voltage in Volt/100
+
|zone off
 
|-
 
|-
−
|}
 
  
−
=== DFLUX, DFSUN ===
+
|rowspan="2"|i<address>.mode
−
The DFLUX and DFSUN are input modules with 1 analog light sensor.
+
|summer
−
They use one input address in the DOMINO bus.
+
|R
−
 
+
|summer mode
−
{| class="wikitable"
 
−
!ID
 
−
!Value
 
−
!R/W
 
−
!Description
 
 
|-
 
|-
−
 
+
|winter
−
|i.<address>
 
−
|0...1023
 
 
|R
 
|R
−
|lux level (raw level, not translated to the lux range)
+
|winter mode
 
|-
 
|-
−
|}
 
  
−
=== DFCT ===
+
|rowspan="3"|i<address>.status
−
The DFCT is an input/output temperature sensor module.
+
|off
−
It uses two consecutive input addresses and five consecutive output addresses in the DOMINO bus.
+
|R
−
 
+
|off status
−
{| class="wikitable"
 
−
!ID
 
−
!Value
 
−
!R/W
 
−
!Description
 
 
|-
 
|-
−
 
+
|heating
−
|rowspan="2"|i.<address>.mode
 
−
|winter
 
 
|R
 
|R
−
|winter mode
+
|heating request
 
|-
 
|-
−
|summer
+
|cooling
 
|R
 
|R
−
|summer mode
+
|cooling request
 
|-
 
|-
  
−
|rowspan="4"|i.<address>.fan
+
|rowspan="4"|i<address>.fan
 +
|off
 +
|R
 +
|fan off
 +
|-
 
|min
 
|min
 
|R
 
|R
−
|min fan speed
+
|min speed
 
|-
 
|-
 
|med
 
|med
 
|R
 
|R
−
|medium fan speed
+
|med speed
 
|-
 
|-
 
|max
 
|max
 
|R
 
|R
−
|max fan speed
+
|max speed
 
|-
 
|-
−
|off
+
 
 +
|rowspan="2"|i<address>.temp
 +
|fault
 
|R
 
|R
−
|fan off
+
|NTC probe fault
 
|-
 
|-
−
 
+
|<temp>  
−
|rowspan="2"|i.<address>.fan.mode
 
−
|man
 
 
|R
 
|R
−
|manual fan mode
+
|ambient temperature value, in C/10
 
|-
 
|-
−
|auto
+
 
 +
|i<address>.setpoint.temp
 +
|<temp>
 
|R
 
|R
−
|auto fan mode
+
|real setpoint value, in C/10
 
|-
 
|-
  
−
|rowspan="5"|i.<address>.setpoint
+
|i<address>.knob
−
|1
+
|0 ... 1000
 
|R
 
|R
−
|setpoint 1
+
|position of rotary knob
 +
|-
 +
 
 +
|rowspan="2"|o<address>.mode
 +
|summer
 +
|RW
 +
|set summer
 
|-
 
|-
−
|2
+
|winter
−
|R
+
|RW
−
|setpoint 2
+
|set winter
 
|-
 
|-
−
|3
+
 
−
|R
+
|rowspan="2"|o<address>
−
|setpoint 3
+
|on
 +
|RW
 +
|zone on
 
|-
 
|-
 
|off
 
|off
−
|R
+
|RW
−
|off
+
|zone off
 
|-
 
|-
−
|man
+
 
−
|R
+
|o<address>.setpoint.temp
−
|manual setpoint
+
|0...400
 +
|RW
 +
|set and read the value of central setpoint (temp in C/10)
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.setpoint.mode
+
|o<address>.setpoint.delta.neg
−
|man
+
|<temp>
−
|R
+
|RW
−
|manual setpoint mode
+
|set and read the MAX negative delta
−
|-
 
−
|auto
 
−
|R
 
−
|auto setpoint mode
 
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.temp
+
|o<address>.setpoint.delta.pos
 
|<temp>
 
|<temp>
−
|R
+
|RW
−
|temperature value (in C/10)
+
|set and read the MAX positive delta
−
|-
 
−
|fault
 
−
|R
 
−
|temperature sensor fault
 
 
|-
 
|-
  
−
|rowspan="3"|i.<address>.status
+
|rowspan="4"|o<address>.led.1
−
|off
+
|red<br/>r
−
|R
+
|RW
−
|off
+
|LED 1 red
 
|-
 
|-
−
|cooling
+
|green<br/>g
−
|R
+
|RW
−
|cooling status mode
+
|LED 1 green
−
|-
 
−
|heating
 
−
|R
 
−
|heating status mode
 
 
|-
 
|-
−
 
+
|yellow<br/>y
−
|rowspan="2"|o.<address>.mode
 
−
|winter
 
 
|RW
 
|RW
−
|winter mode
+
|LED 1 yellow
 
|-
 
|-
−
|summer
+
|off
 
|RW
 
|RW
−
|summer mode
+
|set off
 
|-
 
|-
  
−
|rowspan="4"|o.<address>.fan
+
|rowspan="4"|o<address>.led.2
−
|min
+
|red<br/>r
 
|RW
 
|RW
−
|min fan speed
+
|LED 2 red
 
|-
 
|-
−
|med
+
|green<br/>g
 
|RW
 
|RW
−
|medium fan speed
+
|LED 2 green
 
|-
 
|-
−
|max
+
|yellow<br/>y
 
|RW
 
|RW
−
|max fan speed
+
|LED 2 yellow
 
|-
 
|-
 
|off
 
|off
 
|RW
 
|RW
−
|fan off
+
|set off
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.fan.mode
+
|rowspan="4"|o<address>.led.3
−
|man
+
|red<br/>r
 
|RW
 
|RW
−
|manual fan mode
+
|LED 3 red
 
|-
 
|-
−
|auto
+
|green<br/>g
 
|RW
 
|RW
−
|auto fan mode
+
|LED 3 green
 
|-
 
|-
−
 
+
|yellow<br/>y
−
|rowspan="5"|o.<address>.setpoint
 
−
|1
 
 
|RW
 
|RW
−
|setpoint 1
+
|LED 3 yellow
 
|-
 
|-
−
|2
+
|off
 
|RW
 
|RW
−
|setpoint 2
+
|set off
 
|-
 
|-
−
|3
+
 
 +
|rowspan="4"|o<address>.led.4
 +
|red<br/>r
 
|RW
 
|RW
−
|setpoint 3
+
|LED 4 red
 
|-
 
|-
−
|0 <br/> off
+
|green<br/>g
 
|RW
 
|RW
−
|setpoint off
+
|LED 4 green
 
|-
 
|-
−
|man
+
|yellow<br/>y
 
|RW
 
|RW
−
|manual setpoint
+
|LED 4 yellow
 
|-
 
|-
−
 
+
|off
−
|o.<address>.setpoint.temp.1
 
−
|<temp>
 
 
|RW
 
|RW
−
|temperature setpoint 1 value (in C/10)
+
|set off
 
|-
 
|-
  
−
|o.<address>.setpoint.temp.2
+
|}
−
|<temp>
+
 
−
|RW
+
You can also set the value to “on” or “off”, that is equivalent to 1 and 0.
−
|temperature setpoint 2 value (in C/10)
+
 
−
|-
+
----
  
−
|o.<address>.setpoint.temp.3
+
=== MODANA ===
−
|<temp>
 
−
|RW
 
−
|temperature setpoint 3 value (in C/10)
 
−
|-
 
  
−
|o.<address>.setpoint.temp.man
+
Network analyzer module for Contatto bus.
−
|<temp>
 
−
|RW
 
−
|temperature manual setpoint 1 value (in C/10)
 
−
|-
 
  
−
|o.<address>.program.summer<br/>o.<address>.program.winter
+
It uses, in dynamic mode, up to a maximum of 5 consecutive input addresses and, if enabled, 1 output address equal to the base address.
−
|refresh
 
−
|RW
 
−
|forces to daily summer/winter program for all days of the week
 
−
|-
 
  
−
|rowspan="2"|o.<address>.program.summer.<day><br/>o.<address>.program.winter.<day>
+
{{note|The module's firmware should be version 1.5 or later to support negative values for active power readings.}}
−
|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
 
−
|-
 
  
−
|}
+
{{tip|The module must be configured with the same base address for input and output.}}
  
−
=== DFTZ ===
+
For example:
−
The DFTZ is an input/output temperature sensor module.
+
<pre>
−
It uses 3 consecutive input addresses and 4 consecutive output addresses in the DOMINO bus.
+
(I7, O7)
 +
</pre>
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,163: Line 3,488:
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.mode
+
|i<address>.v12
−
|winter
+
|[V]
 
|R
 
|R
−
|winter mode
+
|chained voltage phase 1-2
 
|-
 
|-
−
|summer
+
 
 +
|i<address>.v23
 +
|[V]
 
|R
 
|R
−
|summer mode
+
|chained voltage phase 2-3
 
|-
 
|-
  
−
|rowspan="3"|i.<address>.setpoint
+
|i<address>.v31
−
|comfort
+
|[V]
 
|R
 
|R
−
|comfort setpoint
+
|chained voltage phase 3-1
 
|-
 
|-
−
|eco
+
 
 +
|i<address>.vtm
 +
|[V]
 
|R
 
|R
−
|eco setpoint
+
|average chained voltage
 
|-
 
|-
−
|off
+
 
 +
|i<address>.i1
 +
|[A]
 
|R
 
|R
−
|off
+
|current phase 1
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.temp
+
|i<address>.i2
−
|<temp>
+
|[A]
 
|R
 
|R
−
|temperature value (in C/10)
+
|current phase 2
 
|-
 
|-
−
|fault
+
 
 +
|i<address>.i3
 +
|[A]
 
|R
 
|R
−
|temperature sensor fault
+
|current phase 3
 
|-
 
|-
  
−
|rowspan="3"|i.<address>.status
+
|i<address>.itm
−
|off
+
|[A]
 
|R
 
|R
−
|off
+
|average current
 
|-
 
|-
−
|cooling
+
 
 +
|i<address>.ptot
 +
|[W]
 
|R
 
|R
−
|cooling status mode
+
|total active power
 
|-
 
|-
−
|heating
+
 
 +
|i<address>.ptotk
 +
|[kW]
 
|R
 
|R
−
|heating status mode
+
|total active power
 
|-
 
|-
  
−
|rowspan="2"|o.<address>.mode
+
|i<address>.qtot
−
|winter
+
|[W]
−
|RW
+
|R
−
|winter mode
+
|total reactive power
 
|-
 
|-
−
|summer
+
 
−
|RW
+
|i<address>.qtotk
−
|summer mode
+
|[kW]
 +
|R
 +
|total reactive power
 
|-
 
|-
  
−
|rowspan="3"|o.<address>.setpoint
+
|i<address>.pf
−
|comfort
+
|[pf]
−
|RW
+
|R
−
|comfort setpoint
+
|total power factor
 
|-
 
|-
−
|eco
+
 
−
|RW
+
|i<address>.frequency
−
|eco setpoint
+
|[Hz]
 +
|R
 +
|frequency
 
|-
 
|-
−
|0<br/>off
+
 
−
|RW
+
|i<address>.v1n
−
|off
+
|[V]
 +
|R
 +
|voltage phase 1
 
|-
 
|-
  
−
|o.<address>.setpoint.temp.comfort
+
|i<address>.v2n
−
|<temp>
+
|[V]
−
|RW
+
|R
−
|comfort setpoint value (in C/10)
+
|voltage phase 2
 
|-
 
|-
  
−
|o.<address>.setpoint.temp.eco
+
|i<address>.v3n
−
|<temp>
+
|[V]
−
|RW
+
|R
−
|eco setpoint value (in C/10)
+
|voltage phase 3
 
|-
 
|-
  
−
|o.<address>.setpoint.temp.limit
+
|i<address>.p1
−
|<temp>
+
|[W]
−
|RW
+
|R
−
|summer/winter setpoint temperature limit (in C/10)
+
|active power phase 1
 
|-
 
|-
  
−
|}
+
|i<address>.p1k
 +
|[kW]
 +
|R
 +
|active power phase 1
 +
|-
  
−
=== DFRHT ===
+
|i<address>.p2
−
The DFRHT is a temperature and humidity sensor.
+
|[W]
−
It uses four consecutive input addresses and two consecutive output addresses in the DOMINO bus.
+
|R
−
 
+
|active power phase 2
−
{| class="wikitable"
 
−
!ID
 
−
!Value
 
−
!R/W
 
−
!Description
 
 
|-
 
|-
  
−
|i.<address>.humidity
+
|i<address>.p2k
−
|0...100
+
|[kW]
 
|R
 
|R
−
|relative percent umidity
+
|active power phase 2
 
|-
 
|-
  
−
|i.<address>.temp
+
|i<address>.p3
−
|<temp>
+
|[W]
 
|R
 
|R
−
|temperature value
+
|active power phase 3
 
|-
 
|-
  
−
|i.<address>.dewpoint
+
|i<address>.p3k
−
|<temp>
+
|[kW]
 
|R
 
|R
−
|dew point value
+
|active power phase 3
 
|-
 
|-
  
−
|rowspan="4"|i.<address>.dewpoint.limit.1
+
|i<address>.q1
−
|0
+
|[W]
 
|R
 
|R
−
|dew point is lower than limit 1
+
|reactive power phase 1
 
|-
 
|-
−
|1
+
 
 +
|i<address>.q1k
 +
|[kW]
 
|R
 
|R
−
|dew point is higher than limit 1
+
|reactive power phase 1
 
|-
 
|-
−
|<temp>
+
 
−
|RW
+
|i<address>.q2
−
|dew point limit 1
+
|[W]
 +
|R
 +
|reactive power phase 2
 
|-
 
|-
−
|off
+
 
−
|RW
+
|i<address>.q2k
−
|limit 1 not set
+
|[kW]
 +
|R
 +
|reactive power phase 2
 
|-
 
|-
  
−
|rowspan="4"|i.<address>.dewpoint.limit.2
+
|i<address>.q3
−
|0
+
|[W]
 
|R
 
|R
−
|dew point is lower than limit 2
+
|reactive power phase 3
 
|-
 
|-
−
|1
+
 
 +
|i<address>.q3k
 +
|[kW]
 
|R
 
|R
−
|dew point is higher than limit 2
+
|reactive power phase 3
 
|-
 
|-
−
|<temp>
+
 
−
|RW
+
|i<address>.pf1
−
|dew point limit 2
+
|[pf]
 +
|R
 +
|power factor phase 1
 
|-
 
|-
−
|off
+
 
−
|RW
+
|i<address>.pf2
−
|limit 2 not set
+
|[pf]
 +
|R
 +
|power factor phase 2
 
|-
 
|-
  
−
|}
+
|i<address>.pf3
 +
|[pf]
 +
|R
 +
|power factor phase 3
 +
|-
  
−
=== DFMETEO ===
+
|i<address>.s1
−
The DFMETEO is the weather sensor module.
+
|[VA]
−
It uses four consecutive input addresses and three consecutive output addresses in the DOMINO bus.
+
|R
 +
|apparent power phase 1
 +
|-
  
−
{| class="wikitable"
+
|i<address>.s1k
−
!ID
+
|[kVA]
−
!Value
+
|R
−
!R/W
+
|apparent power phase 1
−
!Description
 
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.temp
+
|i<address>.s2
−
|<temp>
+
|[VA]
−
|RW
+
|R
−
|temperature value (in C/10)
+
|apparent power phase 2
 
|-
 
|-
−
|off
+
 
−
|RW
+
|i<address>.s2k
−
|limit not set
+
|[kVA]
 +
|R
 +
|apparent power phase 2
 
|-
 
|-
  
−
|rowspan="3"|i.<address>.lux
+
|i<address>.s3
−
|<lux*10>
+
|[VA]
 
|R
 
|R
−
|lux level according to the DFLUX range
+
|apparent power phase 3
−
|-
 
−
|<lux>
 
−
|RW
 
−
|lux limit
 
−
|-
 
−
|0
 
−
|RW
 
−
|limit not set
 
 
|-
 
|-
  
−
|rowspan="3"|i.<address>.wind
+
|i<address>.s3k
−
|1 m/s /10
+
|[kVA]
 
|R
 
|R
−
|wind value
+
|apparent power phase 3
−
|-
 
−
|m/s
 
−
|RW
 
−
|wind limit
 
−
|-
 
−
|0
 
−
|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
+
|hour-meter
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.night
+
|i<address>.temperature
−
|0
+
|[°C]
 
|R
 
|R
−
|day
+
|cabinet temperature
 
|-
 
|-
−
|1
+
 
 +
|i<address>.energy.active
 +
|[KWh]
 
|R
 
|R
−
|night
+
|positive active energy
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.temp.limit
+
|i<address>.energy.activeneg
−
|0
+
|[KWh]
 
|R
 
|R
−
|measured temp is less than limit
+
|negative active energy
 
|-
 
|-
−
|1
+
 
 +
|i<address>.energy.reactive
 +
|[KVARh]
 
|R
 
|R
−
|measured temp is greater than limit
+
|positive reactive energy
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.lux.limit
+
|i<address>.energy.reactiveneg
−
|0
+
|[KVARh]
 
|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"|o<address>.reset.energy
 
|1
 
|1
−
|R
+
|RW
−
|measured wind is greater than limit
+
|reset energies
 
|-
 
|-
−
 
−
|rowspan="2"|i.<address>.light.south
 
 
|0
 
|0
−
|R
+
|RW
−
|light is not coming from south
+
| ---
−
|-
 
−
|1
 
−
|R
 
−
|light is coming from south
 
 
|-
 
|-
  
−
|rowspan="2"|i.<address>.light.west
+
|rowspan="2"|o<address>.reset.hours
−
|0
 
−
|R
 
−
|light is not coming from west
 
−
|-
 
 
|1
 
|1
−
|R
+
|RW
−
|light is coming from west
+
|reset hour-meter
 
|-
 
|-
−
 
−
|rowspan="2"|i.<address>.light.east
 
 
|0
 
|0
−
|R
+
|RW
−
|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 ===
+
----
−
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"
+
=== MODANAM ===
−
!ID
+
 
 +
Network analyzer module for Contatto bus.
 +
 
 +
It uses, in dynamic mode, up to a maximum of 5 consecutive input addresses and, if enabled, 1 output address equal to the base address.
 +
 
 +
{{tip|The module must be configured with the same base address for input and output.}}
 +
 
 +
For example:
 +
<pre>
 +
(I7, O7)
 +
</pre>
 +
 
 +
{| class="wikitable"
 +
!ID
 
!Value
 
!Value
 
!R/W
 
!R/W
Line 3,473: Line 3,814:
 
|-
 
|-
  
−
|energy.<n>.power.real
+
|i<address>.v12
−
|0...65535
+
|[V]
 
|R
 
|R
−
|real power (Watt)
+
|chained voltage phase 1-2
 
|-
 
|-
  
−
|energy.<n>.power.reactive
+
|i<address>.v23
−
| -32768...+32767
+
|[V]
 
|R
 
|R
−
|reactive power (var)
+
|chained voltage phase 2-3
 
|-
 
|-
  
−
|energy.<n>.power.apparent
+
|i<address>.v31
−
| -32768...+32767
+
|[V]
 
|R
 
|R
−
|apparent power (VA)
+
|chained voltage phase 3-1
 
|-
 
|-
  
−
|energy.<n>.power.realavg
+
|i<address>.vtm
−
|0...65535
+
|[V]
 
|R
 
|R
−
|average real power (Watt)
+
|average chained voltage
 
|-
 
|-
  
−
|energy.<n>.power.reactiveavg
+
|i<address>.i1
−
| -32768...+32767
+
|[A]
 
|R
 
|R
−
|average reactive power (var)
+
|current phase 1
 
|-
 
|-
  
−
|energy.<n>.cos
+
|i<address>.i2
−
| -1000...+1000
+
|[A]
 
|R
 
|R
−
|cos(φ) * 1000
+
|current phase 2
 
|-
 
|-
  
−
|rowspan="2"|energy.<n>.load.1
+
|i<address>.i3
−
|0
+
|[A]
 
|R
 
|R
−
|load 1 disabled
+
|current phase 3
 
|-
 
|-
−
|1
+
 
 +
|i<address>.itm
 +
|[A]
 
|R
 
|R
−
|load 1 enabled
+
|average current
 
|-
 
|-
  
−
|rowspan="2"|energy.<n>.load.2
+
|i<address>.ptot
−
|0
+
|[W]
 
|R
 
|R
−
|load 2 disabled
+
|total active power
 
|-
 
|-
−
|1
+
 
 +
|i<address>.ptotk
 +
|[kW]
 
|R
 
|R
−
|load 2 enabled
+
|total active power
 
|-
 
|-
  
−
|rowspan="2"|energy.<n>.load.3
+
|i<address>.qtot
−
|0
+
|[W]
 
|R
 
|R
−
|load 3 disabled
+
|total reactive power
 
|-
 
|-
−
|1
+
 
 +
|i<address>.qtotk
 +
|[kW]
 
|R
 
|R
−
|load 3 enabled
+
|total reactive power
 
|-
 
|-
  
−
|rowspan="2"|energy.<n>.load.4
+
|i<address>.pf
−
|0
+
|[pf]
 
|R
 
|R
−
|load 4 disabled
+
|total power factor
 
|-
 
|-
−
|1
+
 
 +
|i<address>.frequency
 +
|[Hz]
 
|R
 
|R
−
|load 4 enabled
+
|frequency
 
|-
 
|-
  
−
|rowspan="2"|energy.<n>.load.5
+
|i<address>.v1n
−
|0
+
|[V]
 
|R
 
|R
−
|load 5 disabled
+
|voltage phase 1
 
|-
 
|-
−
|1
+
 
 +
|i<address>.v2n
 +
|[V]
 
|R
 
|R
−
|load 5 enabled
+
|voltage phase 2
 
|-
 
|-
  
−
|rowspan="2"|energy.<n>.load.6
+
|i<address>.v3n
−
|0
+
|[V]
 
|R
 
|R
−
|load 6 disabled
+
|voltage phase 3
 
|-
 
|-
−
|1
+
 
 +
|i<address>.p1
 +
|[W]
 
|R
 
|R
−
|load 6 enabled
+
|active power phase 1
 
|-
 
|-
  
−
|rowspan="2"|energy.<n>.load.7
+
|i<address>.p1k
−
|0
+
|[kW]
 
|R
 
|R
−
|load 7 disabled
+
|active power phase 1
 
|-
 
|-
−
|1
+
 
 +
|i<address>.p2
 +
|[W]
 
|R
 
|R
−
|load 7 enabled
+
|active power phase 2
 
|-
 
|-
  
−
|rowspan="2"|energy.<n>.load.8
+
|i<address>.p2k
−
|0
+
|[kW]
 
|R
 
|R
−
|load 8 disabled
+
|active power phase 2
 
|-
 
|-
−
|1
+
 
 +
|i<address>.p3
 +
|[W]
 
|R
 
|R
−
|load 8 enabled
+
|active power phase 3
 
|-
 
|-
  
−
|}
+
|i<address>.p3k
 +
|[kW]
 +
|R
 +
|active power phase 3
 +
|-
  
−
=== DFANA ===
+
|i<address>.q1
−
Network analyzer module for Domino bus.
+
|[W]
−
Uses up to 20 consecutive input addresses and, if enabled, 1 output address equal to the base input address.
+
|R
 +
|reactive power phase 1
 +
|-
  
−
{| class="wikitable"
+
|i<address>.q1k
−
!ID
+
|[kW]
−
!Value
+
|R
−
!R/W
+
|reactive power phase 1
−
!Description
 
 
|-
 
|-
  
−
|i.<address>.v12
+
|i<address>.q2
−
|[V]
+
|[W]
 
|R
 
|R
−
|chained voltage phase 1-2
+
|reactive power phase 2
 
|-
 
|-
  
−
|i.<address>.v23
+
|i<address>.q2k
−
|[V]
+
|[kW]
 
|R
 
|R
−
|chained voltage phase 2-3
+
|reactive power phase 2
 
|-
 
|-
  
−
|i.<address>.v31
+
|i<address>.q3
−
|[V]
+
|[W]
 
|R
 
|R
−
|chained voltage phase 3-1
+
|reactive power phase 3
 
|-
 
|-
  
−
|i.<address>.vtm
+
|i<address>.q3k
−
|[V]
+
|[kW]
 
|R
 
|R
−
|average chained voltage
+
|reactive power phase 3
 
|-
 
|-
  
−
|i.<address>.i1
+
|i<address>.pf1
−
|[A]
+
|[pf]
 
|R
 
|R
−
|current phase 1
+
|power factor phase 1
 
|-
 
|-
  
−
|i.<address>.i2
+
|i<address>.pf2
−
|[A]
+
|[pf]
 
|R
 
|R
−
|current phase 2
+
|power factor phase 2
 
|-
 
|-
  
−
|i.<address>.i3
+
|i<address>.pf3
−
|[A]
+
|[pf]
 
|R
 
|R
−
|current phase 3
+
|power factor phase 3
 
|-
 
|-
  
−
|i.<address>.itm
+
|i<address>.s1
−
|[A]
+
|[VA]
 
|R
 
|R
−
|average current
+
|apparent power phase 1
 
|-
 
|-
  
−
|i.<address>.ptot
+
|i<address>.s1k
−
|[W]
+
|[kVA]
 
|R
 
|R
−
|total active power
+
|apparent power phase 1
 
|-
 
|-
  
−
|i.<address>.ptotk
+
|i<address>.s2
−
|[kW]
+
|[VA]
 
|R
 
|R
−
|total active power
+
|apparent power phase 2
 
|-
 
|-
  
−
|i.<address>.qtot
+
|i<address>.s2k
−
|[W]
+
|[kVA]
 
|R
 
|R
−
|total reactive power
+
|apparent power phase 2
 
|-
 
|-
  
−
|i.<address>.qtotk
+
|i<address>.s3
−
|[kW]
+
|[VA]
 
|R
 
|R
−
|total reactive power
+
|apparent power phase 3
 
|-
 
|-
  
−
|i.<address>.pf
+
|i<address>.s3k
−
|[pf]
+
|[kVA]
 
|R
 
|R
−
|total power factor
+
|apparent power phase 3
 
|-
 
|-
  
−
|i.<address>.frequency
+
|i<address>.stot
−
|[Hz]
+
|[VA]
 
|R
 
|R
−
|frequency
+
|total apparent power
 
|-
 
|-
  
−
|i.<address>.v1n
+
|i<address>.hours
−
|[V]
+
|[hours]
 
|R
 
|R
−
|voltage phase 1
+
|hour-meter
 
|-
 
|-
  
−
|i.<address>.v2n
+
|i<address>.temperature
−
|[V]
+
|[°C]
 
|R
 
|R
−
|voltage phase 2
+
|cabinet temperature
 
|-
 
|-
  
−
|i.<address>.v3n
+
|i<address>.energy.active
−
|[V]
+
|[KWh]
 
|R
 
|R
−
|voltage phase 3
+
|positive active energy
 
|-
 
|-
  
−
|i.<address>.p1
+
|i<address>.energy.activeneg
−
|[W]
+
|[KWh]
 
|R
 
|R
−
|active power phase 1
+
|negative active energy
 
|-
 
|-
  
−
|i.<address>.p1k
+
|i<address>.energy.reactive
−
|[kW]
+
|[KVARh]
 
|R
 
|R
−
|active power phase 1
+
|positive reactive energy
 
|-
 
|-
  
−
|i.<address>.p2
+
|i<address>.energy.reactiveneg
−
|[W]
+
|[KVARh]
 
|R
 
|R
−
|active power phase 2
+
|negative reactive energy
 
|-
 
|-
  
−
|i.<address>.p2k
+
|rowspan="2"|o<address>.reset.energy
−
|[kW]
+
|1
−
|R
+
|RW
−
|active power phase 2
+
|reset energies
 +
|-
 +
|0
 +
|RW
 +
| ---
 
|-
 
|-
  
−
|i.<address>.p3
+
|rowspan="2"|o<address>.reset.hours
−
|[W]
+
|1
−
|R
+
|RW
−
|active power phase 3
+
|reset hour-meter
 
|-
 
|-
−
 
+
|0
−
|i.<address>.p3k
+
|RW
−
|[kW]
+
| ---
−
|R
 
−
|active power phase 3
 
 
|-
 
|-
−
 
  
 
|}
 
|}
  
−
== User Interface ==
+
----
  
−
=== DFDMX ===
+
=== MODPQ5 ===
  
−
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:
+
Q5 tags proximity reader and programmer module.
−
<pre>
 
−
dmxServers = dmx
 
−
dmxServersId.dmx = domino.o8
 
−
</pre>
 
  
−
Note that, instead of defining the dmxServersIP parameter, the dmxServersId is used to associate the DMX server with the id of the DFDMX module.
+
Uses 1 input address on the Contatto bus. Write operations are performed through direct writes to the module’s RAM.
−
 
 
−
=== DFCC ===
 
−
 
 
−
==== UISET Actions ====
 
  
 
{| class="wikitable"
 
{| class="wikitable"
 
!ID
 
!ID
−
!Attribute
+
!Value
−
!colspan="2"|Set to
+
!R/W
 +
!Description
 
|-
 
|-
  
−
|energy.<n>.power
+
|i<address>.data
−
|value
+
|style="white-space:nowrap"|0 <br/> <tag data>
−
|real power, followed by “ W”
+
|R
 +
|30 characters hexadecimal representation of the 15 bytes of tag data; “0” if the module is not seeing any tag
 
|-
 
|-
−
|}
 
  
−
=== DFCT ===
+
|rowspan="2"|i<address>.data.write
 +
|0
 +
|R
 +
|the tag has been removed from the programmer after writing, or the module is not seeing any tag
 +
|-
 +
|1
 +
|R
 +
|the tag write operation was successful
 +
|-
  
−
==== UISET Actions ====
+
|rowspan="2"|i<address>.reader.error
−
 
+
|0
−
{| class="wikitable"
+
|R
−
!ID
+
|reader/writer normal status
−
!Attribute
+
|-
−
!colspan="2"|Set to
+
|1
 +
|R
 +
|reader/writer module error (normally occurs when the reader is not connected to the MODPQ5 module)
 
|-
 
|-
  
−
|rowspan="2"|<address>.mode
+
|rowspan="2"|i<address>.tag.error
−
|summer
+
|0
−
|summer mode (cooling)
+
|R
 +
|the tag is valid
 
|-
 
|-
−
|winter
+
|1
−
|winter mode (heating)
+
|R
 +
|the tag is not valid
 
|-
 
|-
  
−
|<address>.mode.label.summer
+
|rowspan="2"|i<address>.request.error
−
|visible
+
|0
−
|the DFCT is in summer mode
+
|R
 +
|no request or handshake errors detected
 
|-
 
|-
−
 
+
|1
−
|<address>.mode.label.winter
+
|R
−
|visible
+
|handshake error
−
|the DFCT is in winter mode
 
 
|-
 
|-
  
−
|rowspan="2"|<address>.status
+
|rowspan="2"|i<address>.data.error
−
|off
+
|0
−
|zone off
+
|R
 +
|tag data ok
 
|-
 
|-
−
|on
+
|1
−
|zone on
+
|R
 +
|tag data errors detected
 
|-
 
|-
  
−
|<address>.status.label.cooling
+
|rowspan="2"|i<address>.unknown.error
−
|visible
+
|0
−
|if the zone is cooling
+
|R
 +
|no unknown errors
 
|-
 
|-
−
 
+
|1
−
|<address>.status.label.heating
+
|R
−
|visible
+
|unknown error detected
−
|if the zone is heating
 
 
|-
 
|-
  
−
|rowspan="4"|<address>.fan
+
|rowspan="2"|i<address>.write
−
|off
+
|<tag data>
−
|fan off
+
|R
 +
|tag data write successful
 
|-
 
|-
−
|min
+
|error
−
|minimum fan speed
+
|R
 +
|tag data write error
 
|-
 
|-
−
|med
+
 
−
|medium fan speed
+
|o<address>.write
−
|-
+
|<tag data>
−
|max
+
|W
−
|maximum fan speed
+
|30 characters hexadecimal representation of the 15 bytes data to be written on the tag
 
|-
 
|-
 +
|}
 +
 +
----
  
−
|<address>.fan.label.min
+
=== MODHT ===
−
|visible
 
−
|the fan speed is min
 
−
|-
 
  
−
|<address>.fan.label.med
+
MODHT is the hotel room controller module.  
−
|visible
 
−
|the fan speed is med
 
−
|-
 
  
−
|<address>.fan.label.max
+
It uses 1 input and 1 output address.  
−
|visible
 
−
|the fan speed is max
 
−
|-
 
  
−
|rowspan="2"|<address>.fan.mode
+
Tags configuration data are written to the module’s EEPROM (persistent internal memory).
−
|man
 
−
|manual fan mode
 
−
|-
 
−
|auto
 
−
|auto fan mode
 
−
|-
 
  
−
|rowspan="3"|<address>.setpoint
+
{| class="wikitable"
−
|1,2,3
+
!ID
−
|active setpoint
+
!Value
 +
!R/W
 +
!Description
 
|-
 
|-
−
|man
+
 
−
|manual setpoint
+
|rowspan="2"|i<address>.door
 +
|0
 +
|R
 +
|door closed
 
|-
 
|-
−
|off
+
|1
−
|zone off
+
|R
 +
|door open
 
|-
 
|-
  
−
|<address>.setpoint.label.1
+
|rowspan="2"|i<address>.window
−
|visible
+
|0
−
|setpoint 1 is active
+
|R
 +
|window closed
 +
|-
 +
|1
 +
|R
 +
|window open
 
|-
 
|-
  
−
|<address>.setpoint.label.2
+
|rowspan="2"|i<address>.panic
−
|visible
+
|0
−
|setpoint 2 is active
+
|R
 +
|panic request not active
 
|-
 
|-
−
 
+
|1
−
|<address>.setpoint.label.3
+
|R
−
|visible
+
|panic request
−
|setpoint 3 is active
 
 
|-
 
|-
  
−
|<address>.setpoint.label.man
+
|rowspan="2"|i<address>.busy
−
|visible
+
|0
−
|manual setpoint is active
+
|R
 +
|room is free
 
|-
 
|-
−
 
+
|1
−
|<address>.setpoint.label.off
+
|R
−
|visible
+
|room is occupied
−
|zone is off
 
 
|-
 
|-
  
−
|rowspan="2"|<address>.setpoint.mode
+
|rowspan="2"|i<address>.1
−
|man
+
|0
−
|manual setpoint mode
+
|R
 +
|input pin 1 off
 
|-
 
|-
−
|auto
+
|1
−
|auto setpoint mode
+
|R
 +
|input pin 1 on
 
|-
 
|-
  
−
|<address>.setpoint.temp
+
|rowspan="2"|i<address>.2
−
|<value>
+
|0
−
|the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|R
 +
|input pin 2 off
 +
|-
 +
|1
 +
|R
 +
|input pin 2 on
 
|-
 
|-
  
−
|<address>.setpoint.temp.1
+
|rowspan="2"|i<address>.ev
−
|<value>
+
|0
−
|the active setpoint 1 temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|R
 +
|EV output off
 
|-
 
|-
−
 
+
|1
−
|<address>.setpoint.temp.2
+
|R
−
|<value>
+
|EV output on
−
|the active setpoint 2 temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
 
|-
 
|-
  
−
|<address>.setpoint.temp.3
+
|rowspan="2"|i<address>.aux
−
|<value>
+
|0
−
|the active setpoint 3 temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|R
 +
|AUX output off
 
|-
 
|-
−
 
+
|1
−
|<address>.setpoint.temp.man
+
|R
−
|<value>
+
|AUX output on
−
|the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
 
|-
 
|-
  
−
|rowspan="2"|<address>.temp
+
|rowspan="2"|i<address>.dnd
−
|<temp>
+
|0
−
|the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|R
 +
|do not disturb not active
 
|-
 
|-
−
|fault
+
|1
−
|fault/error condition
+
|R
 +
|do not disturb
 
|-
 
|-
−
|}
 
  
−
==== USER Commands ====
+
|rowspan="2"|i<address>.service
−
 
+
|0
−
{| class="wikitable"
+
|R
−
!Name
+
|room service request not active
−
!Param
+
|-
−
!Action
+
|1
 +
|R
 +
|room service request
 
|-
 
|-
  
−
|rowspan="4"|<address>
+
|rowspan="2"|i<address>.booked
−
|mode
+
|0
−
|cycle through summer and winter mode
+
|R
 +
|room is not booked
 
|-
 
|-
−
|mode.summer
+
|1
−
|set summer mode (cooling)
+
|R
 +
|room is booked
 
|-
 
|-
−
|mode.winter
+
 
−
|set winter mode (heating)
+
|rowspan="2"|i<address>.mode
 +
|summer
 +
|R
 +
|summer mode
 
|-
 
|-
−
|fan
+
|winter
−
|cycle through fan speeds and modes (auto, off, man/min, man/med, man/max, auto)
+
|R
 +
|winter mode
 
|-
 
|-
  
−
|rowspan="16"|<address>.setpoint
+
|rowspan="5"|i<address>.fan
−
|mode
+
|off
−
|cycle through the manual, automatic and off operation modes
+
|R
 +
|fan set to off
 
|-
 
|-
−
|mode.man
+
|auto
−
|set manual operation mode
+
|R
 +
|fan speed set to auto
 
|-
 
|-
−
|mode.auto
+
|min
−
|set automatic operation mode
+
|R
 +
|fan speed set to minimum
 
|-
 
|-
−
|mode.off
+
|med
−
|off mode
+
|R
 +
|fan speed set to medium
 
|-
 
|-
−
|temp.1.up
+
|max
−
|increase setpoint 1 temperature in 0.5C steps
+
|R
 +
|fan speed set to max
 
|-
 
|-
−
|temp.1.down
+
 
−
|decrease setpoint 1 temperature in 0.5C steps
+
|rowspan="2"|i<address>.fan.status
 +
|0  
 +
|R
 +
|fan is off
 
|-
 
|-
−
|temp.1.<t>
+
|1
−
|setpoint 1 set to temperature t, in C/10 (0 <= t <= 355)
+
|R
 +
|fan is on (cooling or heating)
 
|-
 
|-
−
|temp.2.up
+
 
−
|increase setpoint 2 temperature in 0.5C steps
+
|i<address>.temp
 +
|<temp>
 +
|R
 +
|ambient temperature value (in C/10)
 
|-
 
|-
−
|temp.2.down
+
 
−
|decrease setpoint 2 temperature in 0.5C steps
+
|i<address>.setpoint.temp
 +
|<temp>
 +
|R
 +
|setpoint value (in C/10)
 
|-
 
|-
−
|temp.2.<t>
+
 
−
|setpoint 2 set to temperature t, in C/10 (0 <= t <= 355)
+
|i<address>.tag.door
 +
|1...5
 +
|R
 +
|type of tag that is opening the door (1 to 4 are service tags; 5 is a customer tag). After 5 seconds the value is reset to 0
 
|-
 
|-
−
|temp.3.up
+
 
−
|increase setpoint 3 temperature in 0.5C steps
+
|rowspan="2"|i<address>.tag.room
 +
|0
 +
|R
 +
|no tag present in room’s reader
 
|-
 
|-
−
|temp.3.down
+
|1...5
−
|decrease setpoint 3 temperature in 0.5C steps
+
|R
 +
|type of tag inserted in the room’s reader (1 to 4 are service tags; 5 is a customer tag)
 
|-
 
|-
−
|temp.3.<t>
+
 
−
|setpoint 3 set to temperature t, in C/10 (0 <= t <= 355)
+
|i<address>.tag.<n>
 +
|<tag data>
 +
|R
 +
|24 characters hexadecimal representation of the 12 bytes data matching service N tags (N from 1 to 5) stored in module’s EEPROM. Updated on o<address>.tag.<n>=read command
 
|-
 
|-
−
|temp.man.up
+
 
−
|increase manual setpoint temperature in 0.5C steps
+
|rowspan="2"|i<address>.pcam.error
 +
|0
 +
|R
 +
|PCAM module ok
 +
|-
 +
|1
 +
|R
 +
|PCAM module error
 
|-
 
|-
−
|temp.man.down
+
 
−
|decrease manual setpoint temperature in 0.5C steps
+
|rowspan="2"|i<address>.tpr.error
 +
|0
 +
|R
 +
|TPR/H module ok
 
|-
 
|-
−
|temp.man.<t>
+
|1
−
|manual setpoint set to temperature t, in C/10 (0 <= t <= 355)
+
|R
 +
|TPR/H module error
 
|-
 
|-
  
−
|rowspan="9"|<address>.fan
+
|i<address>.mask
−
|mode
+
|style="white-space:nowrap"|<mask data>
−
|cycle through the manual and automatic fan speed modes
+
|R
 +
|24 characters hexadecimal representation of the 12 bytes tag mask stored in module’s EEPROM. Updated on o<address>.mask=read command
 
|-
 
|-
−
|mode.man
+
 
−
|set manual fan speed mode
+
|i<address>.data.door
 +
|0<br/><tag data>
 +
|R
 +
|30 characters hexadecimal representation of the 15 bytes of tag data being read from the door reader; “0” if the module is not seeing any tag (this data point is available with MODHT firmware 5.3 or newer)
 
|-
 
|-
−
|mode.auto
+
 
−
|set automatic fan speed mode
+
|i<address>.data.room
 +
|0<br/><tag data>
 +
|R
 +
|30 characters hexadecimal representation of the 15 bytes of tag data being read from the room reader; “0” if the module is not seeing any tag (this data point is available with MODHT firmware 5.3 or newer)
 
|-
 
|-
−
|up
+
 
−
|increase fan speed
+
|i<address>.setpoint.summer.<n> <br/> i<address>.setpoint.winter.<n>
 +
|<temp>
 +
|R
 +
|winter/summer setpoint <n> (1...3) current value (in C/10). Updated on o<address>.setpoint.summer.<n>=read and  o<address>.setpoint.winter.<n>=read commands
 
|-
 
|-
−
|down
+
 
−
|decrease fan speed
+
|i<address>.setpoint.delta.summer.low <br/> i<address>.setpoint.delta.summer.high <br/> i<address>.setpoint.delta.winter.low <br/>  i<address>.setpoint.delta.winter.high
 +
|style="white-space:nowrap"|<temp delta limit> <br/> 1...9
 +
|R
 +
|the current temperature setpoint low/high limits for winter and summer modes (in C). Updated on o<address>.setpoint.delta=read command
 
|-
 
|-
−
|min
+
 
−
|set min fan speed
+
|rowspan="2"|o<address>.tag.<n>
 +
|<tag data>
 +
|R
 +
|tag data write successful
 
|-
 
|-
−
|med
+
|error
−
|set med fan speed
+
|R
 +
|tag data write error
 
|-
 
|-
−
|max
+
 
−
|set max fan speed
+
|rowspan="2"|o<address>.mask
 +
|<mask data>
 +
|R
 +
|mask data write successful
 
|-
 
|-
−
|off
+
|error
−
|fan off
+
|R
 +
|mask data write error
 
|-
 
|-
−
|}
 
  
−
=== DFTZ ===
+
|rowspan="2"|o<address>.setpoint.summer.<n> <br/> o<address>.setpoint.winter.<n>
−
 
+
|<temp>
−
==== UISET Actions ====
+
|R
−
 
+
|winter/summer setpoint N (1-3) write successful (in C/10)
−
{| class="wikitable"
+
|-
−
!ID
+
|error
−
!Attribute
+
|R
−
!colspan="2"|Set to
+
|setpoint write error
 
|-
 
|-
  
−
|rowspan="2"|<address>.mode
+
|rowspan="2"|o<address>.setpoint.delta.summer.low <br/> o<address>.setpoint.delta.summer.high <br/> o<address>.setpoint.delta.winter.low <br/>  o<address>.setpoint.delta.winter.high
−
|summer
+
|<temp delta limit> <br/> 1...9
−
|summer mode (cooling)
+
|R
 +
|setpoint min/max limit for winter/summer write successful (in C)
 
|-
 
|-
−
|winter
+
|error
−
|winter mode (heating)
+
|R
 +
|setpoint limit write error
 
|-
 
|-
  
−
|<address>.mode.label.summer
+
|rowspan="2"|o<address>.ev.enable
−
|visible
+
|0
−
|the DFTZ is in summer mode
+
|W
 +
|EV output disabled
 
|-
 
|-
−
 
+
|1
−
|<address>.mode.label.winter
+
|W
−
|visible
+
|EV output enabled
−
|the DFTZ is in winter mode
 
 
|-
 
|-
  
−
|rowspan="2"|<address>.status
+
|rowspan="2"|o<address>.aux.enable
−
|off
+
|0
−
|zone off
+
|W
 +
|AUX output disabled
 
|-
 
|-
−
|on
+
|1
−
|zone on
+
|W
 +
|AUX output enabled
 
|-
 
|-
  
−
|<address>.status.label.off
+
|rowspan="2"|o<address>.panic.reset
−
|visible
+
|0
−
|if the zone is not cooling or heating
+
|W
 +
|panic request reset off
 +
|-
 +
|1
 +
|W
 +
|panic request reset (pulse command)
 
|-
 
|-
  
−
|<address>.status.label.cooling
+
|rowspan="2"|o<address>.busy
−
|visible
+
|0
−
|if the zone is cooling
+
|W
 +
|set room status to free
 +
|-
 +
|1
 +
|W
 +
|set room status to occupied
 
|-
 
|-
  
−
|<address>.status.label.heating
+
|rowspan="2"|o<address>.ev
−
|visible
+
|0
−
|if the zone is heating
+
|W
 +
|EV output off
 +
|-
 +
|1
 +
|W
 +
|EV output on
 
|-
 
|-
  
−
|rowspan="3"|<address>.setpoint
+
|rowspan="2"|o<address>.aux
−
|com
+
|0
−
|comfort setpoint
+
|W
 +
|AUX output off
 
|-
 
|-
−
|man
+
|1
−
|manual setpoint
+
|W
−
|-
+
|AUX output on
−
|off
 
−
|zone off
 
 
|-
 
|-
  
−
|<address>.setpoint.label.1
+
|rowspan="2"|o<address>.dnd.reset
−
|visible
+
|0
−
|comfort setpoint is active
+
|W
 +
|do not disturb reset off
 
|-
 
|-
−
 
+
|1
−
|<address>.setpoint.label.2
+
|W
−
|visible
+
|do not disturb reset (pulse command)
−
|eco setpoint is active
 
 
|-
 
|-
  
−
|<address>.setpoint.label.off
+
|rowspan="2"|o<address>.service.reset
−
|visible
+
|0
−
|zone is off
+
|W
 +
|service reset off
 +
|-
 +
|1
 +
|W
 +
|service reset (pulse command)
 
|-
 
|-
  
−
|<address>.setpoint.temp
+
|rowspan="2"|o<address>.booked
−
|<value>
+
|0
−
|the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|W
 +
|set room as not booked
 +
|-
 +
|1
 +
|W
 +
|set room as booked
 
|-
 
|-
  
−
|<address>.setpoint.temp.1
+
|rowspan="2"|o<address>.mode
−
|<value>
+
|summer
−
|the comfort setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|W
 +
|set room to summer mode
 +
|-
 +
|winter
 +
|W
 +
|set room to winter mode
 
|-
 
|-
  
−
|<address>.setpoint.temp.2
+
|rowspan="2"|o<address>.fan
−
|<value>
+
|off
−
|the eco setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|W
 +
|set fan off (pulse command)
 
|-
 
|-
−
 
+
|auto
−
|<address>.setpoint.temp.man
+
|W
−
|<value>
+
|set fan to auto mode (pulse command)
−
|the summer or winter setpoint temperature limit, in Celsius degrees with one decimal digit, followed by " &deg;C"
 
 
|-
 
|-
  
−
|rowspan="2"|<address>.temp
+
|rowspan="2"|o<address>.comfort
−
|<temp>
+
|0
−
|the manual setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
+
|W
 +
|force comfort set-point off
 
|-
 
|-
−
|fault
+
|1
−
|fault/error condition
+
|W
 +
|force comfort set-point on
 
|-
 
|-
−
|}
 
  
−
==== USER Commands ====
+
|rowspan="2"|o<address>.3
−
 
+
|0
−
{| class="wikitable"
+
|W
−
!Name
+
|output pin 3 off
−
!Param
+
|-
−
!Action
+
|1
 +
|W
 +
| output pin 3 on
 
|-
 
|-
  
−
|rowspan="3"|<address>
+
 
−
|mode
+
|rowspan="2"|o<address>.fan.heating.min
−
|cycle through summer and winter mode
+
|0
 +
|W
 +
|reset heating speed limit
 
|-
 
|-
−
|mode.summer
+
|1
−
|set summer mode (cooling)
+
|W
−
|-
+
|limit heating speed to min
−
|mode.winter
 
−
|set winter mode (heating)
 
 
|-
 
|-
  
−
|rowspan="16"|<address>.setpoint
+
|rowspan="2"|o<address>.fan.cooling.min
−
|mode
+
|0
−
|cycle through the manual, automatic and off operation modes
+
|W
 +
|reset cooling speed limit
 
|-
 
|-
−
|mode.comfort
+
|1
−
|set comfort operation mode
+
|W
 +
|limit cooling speed to min
 
|-
 
|-
−
|mode.eco
+
 
−
|set eco operation mode
+
|rowspan="2"|o<address>.tag.<n>
 +
|read
 +
|W
 +
|read the 12 bytes stored in module’s EEPROM for service N tags (<n> from 1 to 5)
 
|-
 
|-
−
|mode.off
+
|<tag data>
−
|off mode
+
|W
 +
|24 characters hexadecimal representation of the 12 bytes data matching service N tags (N from 1 to 5), to be stored in module’s EEPROM. After writing data, you should wait approximately 150ms before sending a read command
 
|-
 
|-
−
|temp.up
+
 
−
|increase the active setpoint temperature in 0.5C steps
+
|rowspan="2"|o<address>.mask
 +
|read
 +
|W
 +
|read the 12 bytes mask stored in module’s EEPROM
 
|-
 
|-
−
|temp.down
+
|<mask data>
−
|ddecrease the active setpoint temperature in 0.5C steps
+
|W
 +
|24 characters hexadecimal representation of the 12 bytes tag mask, to be stored in module’s EEPROM. After writing data, you should wait approximately 150ms before sending a read command
 
|-
 
|-
−
|temp.<t>
+
 
−
|active setpoint set to temperature t, in C/10 (0 <= t <= 355)
+
|rowspan="2"|o<address>.setpoint.summer.<n> <br/> o<address>.setpoint.winter.<n>
 +
|read
 +
|W
 +
|read winter/summer setpoint <n> (1-3)
 
|-
 
|-
−
|temp.1.up
+
|<temp>
−
|increase comfort setpoint temperature in 0.5C steps
+
|W
 +
|set winter/summer setpoint <n> (1-3)
 
|-
 
|-
−
|temp.1.down
+
 
−
|decrease comfort setpoint temperature in 0.5C steps
+
|o<address>.setpoint.delta
−
|-
+
|read
−
|temp.1.<t>
+
|W
−
|comfort setpoint set to temperature t, in C/10 (0 <= t <= 355)
+
|read winter and summer, low and high setpoint limits
 +
|-
 +
 
 +
|o<address>.setpoint.delta.summer.low <br/> o<address>.setpoint.delta.summer.high <br/> o<address>.setpoint.delta.winter.low <br/> o<address>.setpoint.delta.winter.high
 +
|<temp delta limit>
 +
|W
 +
|set winter/summer, low/high setpoint limit (in C)
 +
|-
 +
 
 +
|}
 +
 
 +
----
 +
 
 +
=== MODCA ===
 +
 
 +
MODCA is the access control module.
 +
 
 +
It uses 1 input and 1 output address.
 +
 
 +
Tags configuration data are written to the module’s EEPROM (persistent external memory).
 +
 
 +
Site codes and the tags mask are written to the internal EEPROM.
 +
 
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 
 +
|rowspan="2"|i<address>.1
 +
|0
 +
|R
 +
|input pin 1 off
 
|-
 
|-
−
|temp.2.up
+
|1
−
|increase eco setpoint temperature in 0.5C steps
+
|R
 +
|input pin 1 on
 
|-
 
|-
−
|temp.2.down
+
 
−
|decrease eco setpoint temperature in 0.5C steps
+
|rowspan="2"|i<address>.2
 +
|0  
 +
|R
 +
|input pin 2 off
 
|-
 
|-
−
|temp.2.<t>
+
|1
−
|eco setpoint set to temperature t, in C/10 (0 <= t <= 355)
+
|R
 +
|input pin 2 on
 
|-
 
|-
  
−
|temp.man.up
+
|rowspan="2"|i<address>.blocked
−
|increase setpoint temperature limit in 0.5C steps
+
|0  
 +
|R
 +
|access control enabled
 +
|-
 +
|1
 +
|R
 +
|access blocked
 
|-
 
|-
−
|temp.man.down
+
 
−
|decrease setpoint temperature limit in 0.5C steps
+
|rowspan="2"|i<address>.tpr.error
 +
|0  
 +
|R
 +
|TPR module ok
 
|-
 
|-
−
|temp.man.<t>
+
|1
−
|set-point temperature limit set to temperature t, in C/10 (0 <= t <= 355)
+
|R
 +
|TPR module error
 
|-
 
|-
  
 +
|rowspan="2"|i<address>.access.granted.1
 +
|0
 +
|R
 +
|no tag present at antenna 1
 +
|-
 +
|1
 +
|R
 +
|access granted to tag at antenna 1
 +
|-
 +
 +
|rowspan="2"|i<address>.access.granted.2
 +
|0
 +
|R
 +
|no tag present at antenna 2
 +
|-
 +
|1
 +
|R
 +
|access granted to tag at antenna 2
 +
|-
 +
 +
|rowspan="8"|i<address>.access.denied
 +
|0
 +
|R
 +
|access denied flags reset
 +
|-
 +
|site
 +
|R
 +
|access denied due to site code error
 +
|-
 +
|code
 +
|R
 +
|access denied due to user code error
 +
|-
 +
|total.limit
 +
|R
 +
|access denied due to exceeded total number of access grants
 +
|-
 +
|daily.limit
 +
|R
 +
|access denied due to exceeded daily number of access grants
 +
|-
 +
|time
 +
|R
 +
|access denied due to time range violation
 +
|-
 +
|day
 +
|R
 +
|access denied due to weekday violation
 +
|-
 +
|expired
 +
|R
 +
|access denied due expired tag
 +
|-
 +
 +
|i<address>.denied.code
 +
|<tag code>
 +
|R
 +
|the tag code (decimal value of selected two bytes of the tag data) that was denied access
 +
|-
 +
 +
|i<address>.granted.1.code
 +
|<tag code>
 +
|R
 +
|the tag code (decimal value of selected two bytes of the tag data) that was granted access at antenna 1
 +
|-
 +
 +
|i<address>.granted.2.code
 +
|<tag code>
 +
|R
 +
|the tag code (decimal value of selected two bytes of the tag data) that was granted access at antenna 2
 +
|-
 +
 +
|i<address>.site.<n>
 +
|style="white-space:nowrap"|<site data>
 +
|R
 +
|16 characters hexadecimal representation of the 8 bytes data representing the Nth site code (N from 1 to 4) stored in module’s EEPROM
 +
|-
 +
 +
|i<address>.mask
 +
|style="white-space:nowrap"|<mask data>
 +
|R
 +
|16 characters hexadecimal representation of the 8 bytes site code mask stored in module’s EEPROM
 +
|-
 +
 +
|i<address>.mask
 +
|<mask data>
 +
|R
 +
|16 characters hexadecimal representation of the 8 bytes site code mask stored in module’s EEPROM
 +
|-
 +
 +
|i<address>.user.<n>
 +
|<user data>
 +
|R
 +
|32 characters hexadecimal representation of the 16 bytes data for user <n> (N from 1 to 2000) stored in module’s EEPROM
 +
|-
 +
 +
|rowspan="2"|o<address>.site.<n>
 +
|<site data>
 +
|R
 +
|site data write successful
 +
|-
 +
|error
 +
|R
 +
|site data write error
 +
|-
 +
 +
|rowspan="2"|o<address>.mask
 +
|<mask data>
 +
|R
 +
|mask data write successful
 +
|-
 +
|error
 +
|R
 +
|mask data write error
 +
|-
 +
 +
|rowspan="2"|o<address>.user.<n>
 +
|<user data>
 +
|R
 +
|user data write successful
 +
|-
 +
|error
 +
|R
 +
|user data write error
 +
|-
 +
 +
|rowspan="2"|o<address>.relay
 +
|0
 +
|W
 +
|relay output off
 +
|-
 +
|1
 +
|W
 +
|relay output pulse on, with pulse length according to the MODCA configuration (with firmware versions before 1.3 this data point remains at 1 and should be reset to 0 with an explicit command; with firmware 1.3 the data point value follows the relay state, and is automatically reset to 0 at the end of the pulse period)
 +
|-
 +
 +
|rowspan="2"|o<address>.relay.forced
 +
|0
 +
|W
 +
|forced relay mode not set (default behaviour)
 +
|-
 +
|1
 +
|W
 +
|forced relay mode set: the relay remains closed until the relay.forced command is reset (available with MODCA firmware version 2.0 or later)
 +
|-
 +
 +
|rowspan="2"|o<address>.block
 +
|0
 +
|W
 +
|enable access control
 +
|-
 +
|1
 +
|W
 +
|block access control
 +
|-
 +
 +
|rowspan="2"|o<address>.access.granted.code
 +
|0
 +
|W
 +
|reset
 +
|-
 +
|1
 +
|W
 +
|allow access even when site code is not valid
 +
|-
 +
 +
|rowspan="2"|o<address>.access.granted.total.limit
 +
|0
 +
|W
 +
|reset
 +
|-
 +
|1
 +
|W
 +
|allow access even when the total limit of access grants has been exceeded
 +
|-
 +
 +
|rowspan="2"|o<address>.access.granted.daily.limit
 +
|0
 +
|W
 +
|reset
 +
|-
 +
|1
 +
|W
 +
|allow access even when the daily limit of access grants has been exceeded
 +
|-
 +
 +
|rowspan="2"|o<address>.access.granted.time
 +
|0
 +
|W
 +
|reset
 +
|-
 +
|1
 +
|W
 +
|allow access even outside of the allowed timeframe
 +
|-
 +
 +
|rowspan="2"|o<address>.access.granted.day
 +
|0
 +
|W
 +
|reset
 +
|-
 +
|1
 +
|W
 +
|allow access even outside of the allowed weekdays
 +
|-
 +
 +
|rowspan="2"|o<address>.access.granted.expired
 +
|0
 +
|W
 +
|reset
 +
|-
 +
|1
 +
|W
 +
|allow access even when the tag is expired
 +
|-
 +
 +
|rowspan="2"|o<address>.site.<n>
 +
|read
 +
|W
 +
|read the 8 bytes stored in module’s EEPROM for site N code (<n> from 1 to 4)
 +
|-
 +
|<site data>
 +
|W
 +
|16 characters hexadecimal representation of the 8 bytes data of site N code (N from 1 to 4), to be stored in module’s EEPROM. After writing data, you should wait approximately 100ms before sending a read command
 +
|-
 +
 +
|rowspan="2"|o<address>.mask
 +
|read
 +
|W
 +
|read the 8 bytes mask stored in module’s EEPROM
 +
|-
 +
|<mask data>
 +
|W
 +
|16 characters hexadecimal representation of the 8 bytes site code mask, to be stored in module’s EEPROM. After writing data, you should wait approximately 100ms before sending a read command
 +
|-
 +
 +
|rowspan="3"|o<address>.user.<n>
 +
|read
 +
|W
 +
|read the 16 bytes stored in module’s EEPROM for user N (<n> from 1 to 2000)
 +
|-
 +
|<user data>
 +
|W
 +
|16 characters hexadecimal representation of the first 8 bytes of access control data for user N (N from 1 to 2000) , to be stored in module’s EEPROM
 +
|-
 +
|<reset>
 +
|W
 +
|reset to 0 the total and daily counters for user <n>
 +
|-
 +
 +
|o<address>.users
 +
|erase
 +
|W
 +
|deletes all users data. This action requires up to about 27 seconds to be completed. It also deletes all i<address>.user.<n> and o<address>.user.<n> data points
 +
|-
 
|}
 
|}
 +
 +
----
 +
 +
=== MODKB ===
 +
 +
MODKB is the keypad access control module.
 +
 +
It uses 1 input and 1 output address.
 +
 +
PIN configuration data are written to the module’s EEPROM (persistent memory).
 +
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 +
|rowspan="2"|i<address>.1
 +
|0
 +
|R
 +
|input pin 1 off
 +
|-
 +
|1
 +
|R
 +
|input pin 1 on
 +
|-
 +
 +
|rowspan="2"|i<address>.2
 +
|0
 +
|R
 +
|input pin 2 off
 +
|-
 +
|1
 +
|R
 +
|input pin 2 on
 +
|-
 +
 +
|rowspan="2" style="white-space:nowrap"|i<address>.access.granted.<n>
 +
|0
 +
|R
 +
|reset
 +
|-
 +
|1
 +
|R
 +
|access granted to PIN <n> (<n> from 1 to 30)
 +
|-
 +
 +
|i<address>.pin
 +
|style="white-space:nowrap"|<pin code>
 +
|R
 +
|the last pin code entered on the keypad (from 1 to 65535). Reset to 0 after programmed code persistence time
 +
|-
 +
 +
|rowspan="5"|i<address>.access.granted.<n>
 +
|0
 +
|R
 +
|access denied flags reset
 +
|-
 +
|site
 +
|R
 +
|access denied due to site code error
 +
|-
 +
|code
 +
|R
 +
|access denied due to user code error
 +
|-
 +
|time
 +
|R
 +
|access denied due to time range violation
 +
|-
 +
|day
 +
|R
 +
|access denied due to weekday violation
 +
|-
 +
 +
|i<address>.pin.<n>
 +
|style="white-space:nowrap"|<pin data>
 +
|R
 +
|16 characters hexadecimal representation of the 8 bytes data for PIN <n> (<n> from 1 to 30) stored in module’s EEPROM
 +
|-
 +
 +
|rowspan="2"|o<address>.pin.<n>
 +
|<pin data>
 +
|R
 +
|pin data write successful
 +
|-
 +
|error
 +
|R
 +
|pin data write error
 +
|-
 +
 +
|rowspan="2"|o<address>.relay
 +
|0
 +
|W
 +
|relay output off
 +
|-
 +
|1
 +
|W
 +
|relay output on (pulse output, resets to 0 immediately after the relay is closed, usually before the relay closure time)
 +
|-
 +
 +
|rowspan="2"|o<address>.lock.all
 +
|0
 +
|W
 +
|reset
 +
|-
 +
|1
 +
|W
 +
|disables access to all PINs
 +
|-
 +
 +
|rowspan="2"|o<address>.lock.<n>
 +
|0
 +
|W
 +
|reset
 +
|-
 +
|1
 +
|W
 +
|disables access to PIN <n> (<n> from 1 to 30)
 +
|-
 +
 +
|rowspan="2"|o<address>.pin.<n>
 +
|read
 +
|W
 +
|read the 8 bytes stored in module’s EEPROM for PIN <n> (<n> from 1 to 30)
 +
|-
 +
|<pin data>
 +
|W
 +
|16 characters hexadecimal representation of the 8 bytes data for PIN <n> (<n> from 1 to 30), to be stored in module’s EEPROM
 +
|-
 +
 +
|}
 +
 +
----
 +
 +
=== MODDI ===
 +
 +
500W IGBT dimmer module.
 +
 +
It uses 1 output address.
 +
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 +
|rowspan="3"|o<address>
 +
|0...100
 +
|RW
 +
|brightness level according to current ramp
 +
|-
 +
|off
 +
|RW
 +
|dimmer off
 +
|-
 +
|101...173
 +
|W
 +
|command (see MODDI commands table)
 +
|-
 +
 +
|rowspan="2"|o<address>.noline
 +
|0
 +
|R
 +
|AC line detected
 +
|-
 +
|1
 +
|R
 +
|AC line fault
 +
|-
 +
 +
|rowspan="2"|o<address>.overcurrent
 +
|0
 +
|R
 +
|normal
 +
|-
 +
|1
 +
|R
 +
|overcurrent protection
 +
|-
 +
 +
|rowspan="2"|o<address>.overvoltage
 +
|0
 +
|R
 +
|normal
 +
|-
 +
|1
 +
|R
 +
|overvoltage protection
 +
|-
 +
 +
|rowspan="2"|o<address>.overtemperature
 +
|0
 +
|R
 +
|normal
 +
|-
 +
|1
 +
|R
 +
|overtemperature protection
 +
|-
 +
 +
|}
 +
 +
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.
 +
 +
----
 +
 +
=== MODCL ===
 +
 +
Temperature control module.
 +
 +
It uses 1 input and one output address.
 +
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 +
|rowspan="2"|i<address>
 +
|on
 +
|R
 +
|zone on
 +
|-
 +
|off
 +
|R
 +
|zone off
 +
|-
 +
 +
|rowspan="2"|i<address>.mode
 +
|winter
 +
|R
 +
|winter mode
 +
|-
 +
|summer
 +
|R
 +
|summer mode
 +
|-
 +
 +
|rowspan="4"|i<address>.fan
 +
|min
 +
|R
 +
|min fan speed
 +
|-
 +
|med
 +
|R
 +
|medium fan speed
 +
|-
 +
|max
 +
|R
 +
|max fan speed
 +
|-
 +
|off
 +
|R
 +
|fan off
 +
|-
 +
 +
|rowspan="2"|i<address>.fan.mode
 +
|man
 +
|R
 +
|manual fan mode
 +
|-
 +
|auto
 +
|R
 +
|auto fan mode
 +
|-
 +
 +
|rowspan="5"|i<address>.setpoint
 +
|1
 +
|R
 +
|setpoint 1
 +
|-
 +
|2
 +
|R
 +
|setpoint 2
 +
|-
 +
|3
 +
|R
 +
|setpoint 3
 +
|-
 +
|off
 +
|R
 +
|off
 +
|-
 +
|man
 +
|R
 +
|manual setpoint
 +
|-
 +
 +
|rowspan="2"|i<address>.setpoint.mode
 +
|man
 +
|R
 +
|manual setpoint mode
 +
|-
 +
|auto
 +
|R
 +
|auto setpoint mode
 +
|-
 +
 +
|rowspan="2"|i<address>.temp
 +
|<temp>
 +
|R
 +
|temperature value (in C/10)
 +
|-
 +
|fault
 +
|R
 +
|temperature sensor fault
 +
|-
 +
 +
|rowspan="3"|i<address>.status
 +
|off
 +
|R
 +
|off
 +
|-
 +
|cooling
 +
|R
 +
|cooling status mode
 +
|-
 +
|heating
 +
|R
 +
|heating status mode
 +
|-
 +
 +
|rowspan="2"|o<address>
 +
|on
 +
|RW
 +
|zone on (writing on to this datapoint doesn't turn the zone on, it simply resets the off command)
 +
|-
 +
|off
 +
|RW
 +
|zone off
 +
|-
 +
 +
|rowspan="2"|o<address>.mode
 +
|winter
 +
|RW
 +
|winter mode
 +
|-
 +
|summer
 +
|RW
 +
|summer mode
 +
|-
 +
 +
|rowspan="3"|o<address>.setpoint.mode
 +
|man
 +
|RW
 +
|manual mode
 +
|-
 +
|auto
 +
|RW
 +
|auto mode
 +
|-
 +
|off
 +
|RW
 +
|zone off
 +
|-
 +
 +
|rowspan="5"|o<address>.setpoint
 +
|1
 +
|RW
 +
|setpoint 1
 +
|-
 +
|2
 +
|RW
 +
|setpoint 2
 +
|-
 +
|3
 +
|RW
 +
|setpoint 3
 +
|-
 +
|0
 +
|RW
 +
|setpoint off
 +
|-
 +
|man
 +
|RW
 +
|manual setpoint
 +
|-
 +
 +
|o<address>.setpoint.temp.1
 +
|<temp>
 +
|RW
 +
|temperature setpoint 1 value (in C/10)
 +
|-
 +
 +
|o<address>.setpoint.temp.2
 +
|<temp>
 +
|RW
 +
|temperature setpoint 2 value (in C/10)
 +
|-
 +
 +
|o<address>.setpoint.temp.3
 +
|<temp>
 +
|RW
 +
|temperature setpoint 3 value (in C/10)
 +
|-
 +
 +
|o<address>.setpoint.temp.man
 +
|<temp>
 +
|RW
 +
|temperature manual setpoint value (in C/10)
 +
|-
 +
|}
 +
 +
----
 +
 +
=== MOD4TP/I ===
 +
 +
8 digital input and 4 roller shutters or blinds with detection of travel time.
 +
 +
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 +
|rowspan="2"|i<address>.<N>
 +
|0
 +
|R
 +
|input pin N off
 +
|-
 +
|1
 +
|R
 +
|input pin N on
 +
|-
 +
 +
|rowspan="10"|o<address>.<N>
 +
|up
 +
|RW
 +
|shutter N up command
 +
|-
 +
|down
 +
|RW
 +
|shutter N down command
 +
|-
 +
|stop
 +
|rowspan="2"|W
 +
|rowspan="2"|shutter N stop command
 +
|-
 +
|off
 +
|-
 +
|up1
 +
|W
 +
|shutter N up one step command
 +
|-
 +
|down1
 +
|W
 +
|shutter N down one step command
 +
|-
 +
|unknown
 +
|R
 +
|shutter N unknown state
 +
|-
 +
|offup
 +
|R
 +
|shutter N off, up position
 +
|-
 +
|offdown
 +
|R
 +
|shutter N off, down position
 +
|-
 +
|0-100
 +
|R
 +
|shutter N current position
 +
|-
 +
 +
|rowspan="2"|o<address>.calibration.<N>
 +
|0
 +
|R
 +
|shutter N normal operations
 +
|-
 +
|1
 +
|RW
 +
|shutter N calibration command
 +
|-
 +
 +
|-
 +
|o<address>.position.<N>
 +
|0-100
 +
|RW
 +
|shutter N position command
 +
 +
|-
 +
|o<address>.slats.<N>
 +
|0-100
 +
|W
 +
|shutter N slats position command (no feedback available)
 +
|-
 +
 +
|}
 +
 +
----
 +
 +
=== MODRHT ===
 +
 +
Temperature, relative humidity and dew point sensor.
 +
 +
It uses one input address and, if enabled by the configuration panel of MCP IDE, one output address.
 +
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 +
|i<address>.temp
 +
|<temp>
 +
|R
 +
|temperature value (in C/10)
 +
|-
 +
 +
|i<address>.rh
 +
|<%RH>
 +
|R
 +
|relative humidity percentage (0-100)
 +
|-
 +
 +
|i<address>.dewpoint
 +
|<temp>
 +
|R
 +
|dew point (in C/10)
 +
|-
 +
 +
|rowspan="2"|i<address>.dewpoint.1
 +
|0
 +
|R
 +
|dew point lower than dew point threshold 1
 +
|-
 +
|1
 +
|R
 +
|dew point equal or greater than dew point threshold 1
 +
|-
 +
 +
|rowspan="2"|i<address>.dewpoint.2
 +
|0
 +
|R
 +
|dew point lower than dew point threshold 2
 +
|-
 +
|1
 +
|R
 +
|dew point equal or greater than dew point threshold 2
 +
|-
 +
 +
|o<address>.dewpoint.1
 +
|<temp>
 +
|RW
 +
|dew point threshold 1 (in C/10)
 +
|-
 +
 +
|o<address>.dewpoint.2
 +
|<temp>
 +
|RW
 +
|dew point threshold 2 (in C/10)
 +
|-
 +
 +
|}
 +
 +
----
 +
 +
=== MODAM2 ===
 +
 +
Multi-function, 2 inputs analog module.
 +
 +
Uses one input address.
 +
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 +
|i<address>.1
 +
|<value>
 +
|R
 +
|input 1 value (-32768 to +32767)
 +
|-
 +
 +
|i<address>.2
 +
|<value>
 +
|R
 +
|input 2 value (-32768 to +32767)
 +
|-
 +
|}
 +
 +
----
 +
 +
=== MODIGLASS and MODIGLASS3 ===
 +
 +
MODIGLASS 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 address.
 +
 +
{| class="wikitable"
 +
!ID
 +
!Value
 +
!R/W
 +
!Description
 +
|-
 +
 +
|rowspan="2"|i<address>.1
 +
|0
 +
|R
 +
|button 1 off
 +
|-
 +
|1
 +
|R
 +
|button 1 on
 +
|-
 +
 +
|rowspan="2"|i<address>.2
 +
|0
 +
|R
 +
|button 2 off
 +
|-
 +
|1
 +
|R
 +
|button 2 on
 +
|-
 +
 +
|rowspan="2"|i<address>.3
 +
|0
 +
|R
 +
|button 3 off
 +
|-
 +
|1
 +
|R
 +
|button 3 on
 +
|-
 +
 +
|rowspan="2"|i<address>.4
 +
|0
 +
|R
 +
|button 4 off
 +
|-
 +
|1
 +
|R
 +
|button 4 on
 +
|-
 +
 +
|rowspan="2"|i<address>.5
 +
|0
 +
|R
 +
|button 5 off
 +
|-
 +
|1
 +
|R
 +
|button 5 on
 +
|-
 +
 +
|rowspan="2"|i<address>.6
 +
|0
 +
|R
 +
|button 6 off
 +
|-
 +
|1
 +
|R
 +
|button 6 on
 +
|-
 +
 +
|rowspan="2"|i<address>.led.1
 +
|0
 +
|R
 +
|led 1 off
 +
|-
 +
|1
 +
|R
 +
|led 1 on
 +
|-
 +
 +
|rowspan="2"|i<address>.led.2
 +
|0
 +
|R
 +
|led 2 off
 +
|-
 +
|1
 +
|R
 +
|led 2 on
 +
|-
 +
 +
|rowspan="2"|i<address>.led.3
 +
|0
 +
|R
 +
|led 3 off
 +
|-
 +
|1
 +
|R
 +
|led 3 on
 +
|-
 +
 +
|rowspan="2"|i<address>.led.4
 +
|0
 +
|R
 +
|led 4 off
 +
|-
 +
|1
 +
|R
 +
|led 4 on
 +
|-
 +
 +
|rowspan="2"|i<address>.led.5
 +
|0
 +
|R
 +
|led 5 off
 +
|-
 +
|1
 +
|R
 +
|led 5 on
 +
|-
 +
 +
|rowspan="2"|i<address>.led.6
 +
|0
 +
|R
 +
|led 6 off
 +
|-
 +
|1
 +
|R
 +
|led 6 on
 +
|-
 +
 +
|rowspan="2"|i<address>.proximity
 +
|0
 +
|R
 +
|no proximity detected
 +
|-
 +
|1
 +
|R
 +
|proximity detected
 +
|-
 +
 +
 +
|rowspan="2"|o<address>.led.1
 +
|0
 +
|W
 +
|led 1 off
 +
|-
 +
|1
 +
|W
 +
|led 1 on
 +
|-
 +
 +
|rowspan="2"|o<address>.led.2
 +
|0
 +
|W
 +
|led 2 off
 +
|-
 +
|1
 +
|W
 +
|led 2 on
 +
|-
 +
 +
|rowspan="2"|o<address>.led.3
 +
|0
 +
|W
 +
|led 3 off
 +
|-
 +
|1
 +
|W
 +
|led 3 on
 +
|-
 +
 +
|rowspan="2"|o<address>.led.4
 +
|0
 +
|W
 +
|led 4 off
 +
|-
 +
|1
 +
|W
 +
|led 4 on
 +
|-
 +
 +
|rowspan="2"|o<address>.led.5
 +
|0
 +
|W
 +
|led 5 off
 +
|-
 +
|1
 +
|W
 +
|led 5 on
 +
|-
 +
 +
|rowspan="2"|o<address>.led.6
 +
|0
 +
|W
 +
|led 6 off
 +
|-
 +
|1
 +
|W
 +
|led 6 on
 +
|-
 +
 +
|rowspan="2"|o<address>.disable
 +
|0
 +
|RW
 +
|not disabled (normal mode)
 +
|-
 +
|1
 +
|RW
 +
|disabled (cleaning mode)
 +
|-
 +
 +
|rowspan="2"|o<address>.dim
 +
|0
 +
|RW
 +
|high intensity backlight
 +
|-
 +
|1
 +
|RW
 +
|low intensity backlight
 +
|-
 +
 +
|rowspan="2"|o<address>.proximity
 +
|0
 +
|RW
 +
|disable proximity backlight
 +
|-
 +
|1
 +
|RW
 +
|enable proximity backlight
 +
|-
 +
 +
|rowspan="2"|o<address>.backlight
 +
|0
 +
|RW
 +
|backlight off
 +
|-
 +
|1
 +
|RW
 +
|backlight on
 +
|-
 +
 +
|rowspan="2"|o<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.
 +
 +
----
 +
 +
== User Interface ==
 +
 +
All CONTATTO 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.
 +
 +
 +
[[File:IO_Servers_Contatto_Project_Editor.png|center|border|600px]]
 +
 +
 +
Besides the direct association of control buttons and data points, the CONTATTO driver also automatically updates graphical objects that represent values or states of complex devices, like the CLIMA2 temperature control unit. It will also automatically intercept buttons to manually set operation modes and temperature set-points.
 +
 +
----
 +
 +
=== CLIMA2 ===
 +
 +
You can use the [[temp]] and [[tempmini]] objects to control CLIMA2 devices.
 +
 +
 +
[[File:UI Object clima2.png|border]]
 +
 +
 +
The fan button, in the bottom right-hand corner, is not enabled because the manual control of the fan speed is not available. The M button, in the top right-hand corner, allows to switch the module on or off.
 +
 +
You can also easily create customized controls for the CLIMA2, using standard graphic objects that are automatically set to show the device’s status and intercepted to send user commands.
 +
 +
==== UISET Actions ====
 +
{| class="wikitable"
 +
!ID
 +
!Attribute
 +
!Set to
 +
!Description
 +
|-
 +
 +
|rowspan="2"|<address>.mode
 +
|value
 +
|SUMMER
 +
|summer mode (cooling)
 +
|-
 +
|value
 +
|WINTER
 +
|winter mode (heating)
 +
|-
 +
 +
|<address>.mode.label.summer
 +
|visible
 +
|true
 +
|if CLIMA2 is in summer mode
 +
|-
 +
 +
|<address>.mode.label.winter
 +
|visible
 +
|true
 +
|if CLIMA2 is in winter mode
 +
|-
 +
 +
|rowspan="2"|<address>.status
 +
|value
 +
|OFF
 +
|zone off
 +
|-
 +
|value
 +
|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="4"|<address>.fan
 +
|value
 +
|OFF
 +
|fan off
 +
|-
 +
| value
 +
|MIN
 +
|minimum fan speed
 +
|-
 +
| value
 +
|MED
 +
|medium fan speed
 +
|-
 +
| value
 +
|MAX
 +
|maximum fan speed
 +
|-
 +
 +
|<address>.fan.label.min
 +
|visible
 +
|true
 +
|minimum fan speed
 +
|-
 +
 +
|<address>.fan.label.med
 +
|visible
 +
|true
 +
|medium fan speed
 +
|-
 +
 +
|<address>.fan.label.max
 +
|visible
 +
|true
 +
|maximum fan speed
 +
|-
 +
 +
|<address>.setpoint.label.on
 +
|visible
 +
|true
 +
|zone is on
 +
|-
 +
 +
|<address>.setpoint.label.off
 +
|visible
 +
|true
 +
|zone is off
 +
|-
 +
 +
|rowspan="2"|<address>.setpoint.mode
 +
|value
 +
|ON
 +
|zone is on
 +
|-
 +
|value
 +
|OFF
 +
|zone is off
 +
|-
 +
 +
|<address>.setpoint.temp
 +
|value
 +
|<value>
 +
|the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 +
|-
 +
 +
|rowspan="2"|<address>.temp
 +
|rowspan="2"|value
 +
|<temp>
 +
|the measured temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 +
|-
 +
|FAULT
 +
|fault/error condition
 +
|-
 +
 +
|}
 +
 +
==== USER Commands ====
 +
 +
{| class="wikitable"
 +
!Name
 +
!Param
 +
!Action
 +
|-
 +
 +
|rowspan="4"|<address>
 +
|on
 +
|module on
 +
|-
 +
|off
 +
|module off
 +
|-
 +
|mode.summer
 +
|set summer mode (cooling)
 +
|-
 +
|mode.winter
 +
|set winter mode (heating)
 +
|-
 +
 +
|rowspan="6"|<address>.setpoint
 +
|temp.up
 +
|increase setpoint temperature in 0.5C steps
 +
|-
 +
|temp.down
 +
|decrease setpoint temperature in 0.5C steps
 +
|-
 +
|0...400
 +
|set the setpoint to the defined value (in C/10)
 +
|-
 +
|mode
 +
|cycle through on and off modes
 +
|-
 +
|mode.on
 +
|module on
 +
|-
 +
|mode.off
 +
|module off
 +
|-
 +
 +
|}
 +
 +
 +
----
 +
 +
=== MODCL ===
 +
 +
You can use the [[temp]] and [[tempmini]] objects to control MODCL devices.
 +
 +
 +
The fan button, in the bottom right-hand corner, is not enabled because the manual control of the fan speed is not available. The M button, in the top right-hand corner, allows to switch the module to auto or manual mode, or off.
 +
 +
You can also easily create customized controls for the MODCL, using standard graphic objects that are automatically set to show the device’s status and intercepted to send user commands.
 +
 +
==== UISET Actions ====
 +
{| 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
 +
|if MODCL is in summer mode
 +
|-
 +
 +
|<address>.mode.label.winter
 +
|visible
 +
|true
 +
|if MODCL 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="4"|<address>.fan
 +
|rowspan="4"|value
 +
|OFF
 +
|fan off
 +
|-
 +
|MIN
 +
|minimum fan speed
 +
|-
 +
|MED
 +
|medium fan speed
 +
|-
 +
|MAX
 +
|maximum fan speed
 +
|-
 +
 +
|<address>.fan.label.min
 +
|visible
 +
|true
 +
|minimum fan speed
 +
|-
 +
 +
|<address>.fan.label.med
 +
|visible
 +
|true
 +
|medium fan speed
 +
|-
 +
 +
|<address>.fan.label.max
 +
|visible
 +
|true
 +
|maximum fan speed
 +
|-
 +
 +
|rowspan="3"|<address>.setpoint
 +
|rowspan="3"|value
 +
|1, 2, 3
 +
|setpoint N is active
 +
|-
 +
|MAN
 +
|manual setpoint is active
 +
|-
 +
|OFF
 +
|zone is off
 +
|-
 +
 +
|<address>.setpoint.label.1
 +
|visible
 +
|true
 +
|setpoint 1 is active
 +
|-
 +
 +
|<address>.setpoint.label.2
 +
|visible
 +
|true
 +
|setpoint 3 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
 +
|-
 +
 +
|rowspan="3"|<address>.setpoint.mode
 +
|rowspan="3"|value
 +
|AUTO
 +
|automatic mode
 +
|-
 +
|MAN
 +
|manual mode
 +
|-
 +
|OFF
 +
|zone is off
 +
|-
 +
 +
|<address>.setpoint.temp
 +
|value
 +
|<value>
 +
|the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 +
|-
 +
 +
|rowspan="2"|<address>.temp
 +
|rowspan="2"|value
 +
|<temp>
 +
|the measured temperature, in Celsius degrees with one decimal digit, followed by " &deg;C"
 +
|-
 +
|FAULT
 +
|fault/error condition
 +
|-
 +
 +
|}
 +
 +
==== USER Commands ====
 +
 +
{| class="wikitable"
 +
!Name
 +
!Param
 +
!Action
 +
|-
 +
 +
|<address>
 +
|mode
 +
|cycle summer/winter modes
 +
|-
 +
|rowspan="2"|<address>.mode
 +
|mode.summer
 +
|set summer mode (cooling)
 +
|-
 +
|mode.winter
 +
|set winter mode (heating)
 +
|-
 +
|rowspan="2"|<address>.setpoint.temp
 +
|up
 +
|increase current setpoint temperature in 0.5C steps
 +
|-
 +
|down
 +
|decrease current setpoint temperature in 0.5C steps
 +
|-
 +
|rowspan="3"|<address>.setpoint.temp.N
 +
|up
 +
|increase setpoint N temperature in 0.5C steps
 +
|-
 +
|down
 +
|decrease setpoint N temperature in 0.5C steps
 +
|-
 +
|0...400
 +
|set setpoint N to the given value (in C/10)
 +
|-
 +
|rowspan="3"|<address>.setpoint.temp.man
 +
|up
 +
|increase manual setpoint temperature in 0.5C steps
 +
|-
 +
|down
 +
|decrease manual setpoint temperature in 0.5C steps
 +
|-
 +
|0...400
 +
|set manual setpoint to the given value (in C/10)
 +
|-
 +
|<address>.setpoint
 +
|mode
 +
|cycle through auto, manual and off modes
 +
|-
 +
|rowspan="6"|<address>.setpoint.mode
 +
|auto
 +
|set auto mode
 +
|-
 +
|man
 +
|set manual mode
 +
|-
 +
|off
 +
|zone off
 +
|-
 +
 +
|}
 +
 +
----
 +
 +
=== MOD4TP/I ===
 +
 +
==== Using slider objects for MOD4TP/I shutter's position ====
 +
 +
You can use the slider objects, [[slider|sliderv]] and [[slider|sliderh]], to display and control the position. Set both the slider's ''ID'' and ''address'' to <server_name>.<address>.<N>, with N from 1 to 4.
 +
 +
{{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.}}
 +
 +
== Release Notes ==
 +
 +
=== 3.8.0 ===
 +
*new option "disablemodhtpulsereset", disables automatic reset of MODHT pulse outputs (panic.reset, dnd.reset, service.reset, fan)
 +
*improved support for MCP firmware upload
 +
*fixes to MODANA and MODANAM: energy data points not updated when energy not changing on all three phases
 +
*fixes to MODPQ5 write commands, that failed when another device on the bus had the same output address of MODPQ5 input address
 +
 +
=== 3.7.0 ===
 +
*support of MODRHT
 +
*support of MODAM2
 +
*support of MODIGLASS, MODIGLASS3
 +
*support of MODLC firmware version 3.2
 +
*support of MODDALI firmware version 6.x
 +
*support of MCP counters
 +
*bus and modules fault detection
 +
*fixes to the MODDALI ballast 1 status data point
 +
 +
=== 3.6.0 ===
 +
*added support for MOD32IL
 +
*added support for MOD4TP/I
 +
*added support for MODDALI8
 +
*added support for MODANAM
 +
*fixed a bug that could cause erroneous readings of MODANA's ptotk datapoint when total active power is negative
 +
 +
=== 3.5.1 ===
 +
*MODANA updated to support negative active energy values  (fw. 1.5 or later)
 +
 +
=== 3.5.0 ===
 +
*added support for MCP4
 +
*added support for MODCA firmware version 2.0, with new "relay.forced" datapoint
 +
*added support for MOD32IN
 +
*MODPQ5 is now identified with its unique ID. Use MCPIDE 3.2.3 or later to program the MCPXT/MCP4 to allow HSYCO to correctly identify this module
 +
 +
=== 3.4.0 ===
 +
*improved communication error logging
 +
*improved support of tools remote access
 +
*events generated during startup if startupevents=true are now executed sequentially
 +
*support for MODDI
 +
*support for MODCL
 +
 +
=== 3.2.2 ===
 +
bug fixes:
 +
*the toolspassword optional parameter was incorrectly converted to lower case
 +
*fixed a bug that prevented reading the last 3 addresses of MOAN/I4 and MI420-X4 modules
 +
=== 3.2.1 ===
 +
*added support for MODHT set-point delta limits read and write
 +
*the lux datapoint name was incorrectly set to ID.i<addr>.1 instead of ID.i<addr>.lux
 +
=== 3.2.0 ===
 +
*support for MODCA, MODHT, MODKB, MODPQ5
 +
*new "detectevents" option, generates forced events when a device is detected at start-up
 +
*support for the toolspassword option, to allow MCP-IDE and other tools secure remote access to the MCP via HSYCO
 +
*new clock datapoint to read the MXP-XT internal clock and set it to HSYCO's time
 +
=== 3.0.3 ===
 +
*optimized performance of MCP’s registers status polling
 +
*the server failed to initialized when an unsupported device was configured in the MCP
 +
=== 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
 +
=== 3.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. CONTATTO 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.''

Latest revision as of 16:28, 27 April 2023

The CONTATTO system is DUEMMEGI’s proprietary bus architecture for building automation. HSYCO fully integrates with this system through the MCP control and gateway module, and its FXP-XT serial communication protocol.

A serial connection between the MCPXT 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 MCP4 can be connected via the integrated serial to IP gateway.

The Contatto I/O Server requires MCP-XT firmware version 3.0 or later. The MCPIDE configuration tools pass-through support for secure access to the MCP via HSYCO requires MCPIDE version 3.2.3 or later.

Communication

Use a DE-9 (often called DB-9) male-female RS-232 straight cable to connect the RS-232 MCPXT port to the serial port on HSYCO SERVER or serial gateway. You can also connect the MCPXT using the RS-485 port. The MCP4 can also be connected via the integrated serial to IP gateway.

RS-232 parameters:

Baud rate 9600, 38400, 57600 or 115200 bps (according to the MCP 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.


High Availability

  • Shutdown when inactive: defaults to false.

HSYCO Configuration

You can define and connect to more than one CONTATTO bus using several MCP gateways.

The CONTATTO I/O Server also supports dual, redundant connections between HSYCO and MCP.

If the main connection fails, HSYCO automatically re-routes the communication with MCP 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 CONTATTO’s input devices as configured in the MCP, 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 CONTATTO’s output devices as configured in the MCP, 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 CONTATTO’s virtual points for input and output devices as configured in the MCP, 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 ... 2032 enables polling for the first n virtual points of the MCP. 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 MCP
false polling of the MCP virtual data points is disabled
registers false 1 ... 1024 enables polling for registers R0-Rn of the MCP. 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 MCP
false polling of the MCP registers is disabled
powerdisplay false ≥ 0 (MODANA address) enables the automatic display in the GUI of the total real power measured by a MODANA or MODANAM module connected to this MCP. Note that, if you have more than one MCP gateway, you should enable this option for one gateway only
false power display disabled for this MCP
disablemodhtpulsereset false true disables automatic reset of MODHT pulse outputs (panic.reset, dnd.reset, service.reset, fan)
false MODHT pulse outputs are automatically reset to 0 when found at level 1
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
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 MCP-IDE and other configuration tools to the MCP 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 CONTATTO system: English, Italian or French

Initialization and Connection Events

Event name Value Description
connection online connection established to the MCP module
offline HSYCO can’t connect to the MCP 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)
contatto.o10.1 : LIGHT ; LIGHT
contatto.o6.1 : LIGHT ; DIMMER
contatto.o7.2 : LIGHT ; LIGHT
contatto.o7.1 : LIGHT ; DIMMER
contatto.o9.2 : AUTOM ; VSHUT
contatto.o5.4 : LIGHT ; LIGHT
contatto.o9.1 : AUTOM ; VSHUT
contatto.o5.3 : LIGHT ; LIGHT
contatto.o5.2 : LIGHT ; LIGHT
contatto.o5.1 : LIGHT ; LIGHT

You should then manually add comments and other optional parameters: 

(devices)
contatto.o10.1 : LIGHT ; LIGHT; main entrance light
contatto.o6.1 : LIGHT ; DIMMER; lobby dimmer
contatto.o7.2 : LIGHT ; LIGHT; kitchen workbench
contatto.o7.1 : LIGHT ; DIMMER; kitchen main dimmer

MCP Data Points

The MCP implements 2032 virtual points for binary (on/off) data and 1024 registers and counters for positive scalar values (0-65535). All virtual points, registers and counters can optionally generate I/O events. You can also write to the virtual data points, registers and counters using the IO action in EVENTS or ioSet() method in Java.

You cannot directly control the MCP virtual data points, registers or counters using GUI objects.

To enable polling of the current state of the MCP’s virtual data points, enable the virtualpoints options in hsyco.ini.

To enable polling of the current state of the MCP’s registers, enable the registers options in hsyco.ini.

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

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

ID Value R/W Description
busfault 0 R no bus fault detected
1 R bus fault detected
modulefault 0 R no modules fault detected
1 R modules fault detected
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> (<n>: 0-1023) set to value <x> (<x>: 0-65535)
c0.<n> <x> RW counter <n> (<n>: 0-1023) set to value <x> (<x>: 0-65535)

MCP Internal Clock

The MCP module has an integrated real-time clock. You can use the clock datapoint to read the MCP date and time, and set the MCP clock to HSYCO’s current time.

ID Value R/W Description
clock yyyy-mm-dd hh:mm:ss R the MCP clock current time
read W read the MCP clock, and the delta with HSYCO’s time
sync W set the MCP clock to HSYCO’s current time
clock.delta integer number R the delta time in seconds between the MCP and HSYCO clocks. A positive number means that the MCP clock is ahead of HSYCO

CONTATTO Modules Events and Control

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

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

ID Value R/W Description
i<address>.fault 0 R input module working normally
1 R input module fault detected
o<address>.fault 0 R output module working normally
1 R output module fault detected


Module Code Description
MOD8I/A 8 digital input module for NO contacts in modular housing
MOD32I/A 32 digital input module for NO contacts in modular housing
MOD32IL 32 digital input module for NO contacts in modular housing
MOD32IN 32 digital input module for NO contacts in modular housing
MOD8INP2/A 8 digital input module for NO contacts
MOD8INP2/C 8 digital input module for NC contacts
MOAN/I 0÷10V analog input module
MOAN/I4 quad 0÷10V analog input module
MI420 4÷20mA analog input module
MI420-X4 quad 4÷20mA analog input module
MOD4AM12/V/I 4-channel 0÷10V or 4÷20mA (0÷21mA) analog input module
MOD2PT input module for two PT100 temperature probes
MODCNT 4-channel counter module in modular housing
MODNTC input module for ambient temperature sensors and potentiometers
MOD4I/A 4-digital input module for NO contacts in modular housing
MOD4I/S 4-digital input module for NO contacts in 2M modular housing
MODLUX ambient light measurement module with sensor for ceiling mounting
MODMETEO meteorological data detection module for Contatto bus
MOD8R 8 power relay output module
MODPNP 8 positive logic (PNP) “open collector” digital output module
MODREL 8 relay output compact module in DIN 3M housing
MOAN/U 0÷10V analog output module
MO420 4÷20mA analog output module
MODLC, MODLC-P ambient light regulator module with integrated sensor
MOD4-4S 4 digital input and 4 power relay output multifunction module
MOD2-2R 2 digital input and 2 power relay output module
MOD4-4 4 digital input and 4 digital output module
MOD2DM 2x300W dimmer module
MOD2DV dual 1-10V output for electronic ballast driving
MOD8IL 8 digital input – 8 LED output module for wall box
MOD4DV quad 0-10V output module for generic applications or for external dimmers control
MODDMX DMX gateway
MODDALI 4-channel DALI gateway
MODDALI8 8-channel broadcast DALI gateway
CLIMA2 module for the regulation of the ambient temperature
MODANA network analyzer module
MODANAM network analyzer module
MODPQ5 tags proximity reader and programmer
MODHT hotel room controller
MODCA access control module
MODKB keypad access control module
MODDI 500W IGBT dimmer module
MODCL temperature control module
MOD4TP/I 8 digital input and 4 roller shutters or blinds with detection of travel time
MODRHT Temperature, relative humidity and dew point sensor
MODAM2 Multi-function, 2 inputs analog module
MODIGLASS, MODIGLASS3 6 button touch keypad

MOD8I/A

8 digital input module for NO contacts in modular housing.

It uses one input address in the CONTATTO 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

MOD32I/A

32 digital input module for NO contacts in modular housing.

It uses four addresses of the Contatto bus, one for each group of 8 inputs.

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+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
i<address+1>.5 0 R input pin 5 off
1 R input pin 5 on
i<address+1>.6 0 R input pin 6 off
1 R input pin 6 on
i<address+1>.7 0 R input pin 7 off
1 R input pin 7 on
i<address+1>.8 0 R input pin 8 off
1 R input pin 8 on
i<address+2>.1 0 R input pin 1 off
1 R input pin 1 on
i<address+2>.2 0 R input pin 2 off
1 R input pin 2 on
i<address+2>.3 0 R input pin 3 off
1 R input pin 3 on
i<address+2>.4 0 R input pin 4 off
1 R input pin 4 on
i<address+2>.5 0 R input pin 5 off
1 R input pin 5 on
i<address+2>.6 0 R input pin 6 off
1 R input pin 6 on
i<address+2>.7 0 R input pin 7 off
1 R input pin 7 on
i<address+2>.8 0 R input pin 8 off
1 R input pin 8 on
i<address+3>.1 0 R input pin 1 off
1 R input pin 1 on
i<address+3>.2 0 R input pin 2 off
1 R input pin 2 on
i<address+3>.3 0 R input pin 3 off
1 R input pin 3 on
i<address+3>.4 0 R input pin 4 off
1 R input pin 4 on
i<address+3>.5 0 R input pin 5 off
1 R input pin 5 on
i<address+3>.6 0 R input pin 6 off
1 R input pin 6 on
i<address+3>.7 0 R input pin 7 off
1 R input pin 7 on
i<address+3>.8 0 R input pin 8 off
1 R input pin 8 on

MOD32IL

32 digital input module for NO contacts in modular housing.

It uses one addresses of the Contatto bus and four channels, one for each group of 8 inputs.

ID Value R/W Description
i<address>.N

N=1-32

0 R input pin N off
1 R input pin N on

MOD32IN

32 digital input module for NO contacts in modular housing.

It uses one addresses of the Contatto bus and four channels, one for each group of 8 inputs.

ID Value R/W Description
i<address>.N

N=1-32

0 R input pin N off
1 R input pin N on

MOD8INP2/A

8 digital input module for NO contacts.

It uses one input address of the Contatto 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

MOD8INP2/C

8 digital input module for NC contacts.

It uses one input address of the Contatto 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

MOAN/I

0÷10V analog input module.

It uses one input address in the range 1 to 127 of the Contatto bus.

ID Value R/W Description
i<address>.1 0 ... 255 R voltage value divided in 255 steps

MOAN/I4

Quad 0÷10V analog input module.

It uses four consecutive addresses of the Contatto bus, one for each input.

ID Value R/W Description
i<address>.1 0 ... 255 R voltage value divided in 255 steps
i<address+1>.1 0 ... 255 R voltage value divided in 255 steps
i<address+2>.1 0 ... 255 R voltage value divided in 255 steps
i<address+3>.1 0 ... 255 R voltage value divided in 255 steps

MI420

4÷20mA analog input module.

It uses one input address in the range 1 to 127 of the Contatto bus.

ID Value R/W Description
i<address>.1 0 ... 255 R current value divided in 255 steps

MI420-X4

Quad 4÷20mA analog input module.

It uses four consecutive addresses of the Contatto bus, one for each input.

ID Value R/W Description
i<address>.1 0 ... 255 R current value divided in 255 steps
i<address+1>.1 0 ... 255 R current value divided in 255 steps
i<address+2>.1 0 ... 255 R current value divided in 255 steps
i<address+3>.1 0 ... 255 R current value divided in 255 steps

MOD4AM12/V/I

4-channel 0÷10V or 4÷20mA (0÷21mA) analog input module.

It uses one input address of the Contatto bus.

ID Value R/W Description
i<address>.1 0 ... 4095 R measurement range divided in 4095 steps
i<address>.2 0 ... 4095 R measurement range divided in 4095 steps
i<address>.3 0 ... 4095 R measurement range divided in 4095 steps
i<address>.4 0 ... 4095 R measurement range divided in 4095 steps

MOD2PT

Input module for two PT100 temperature probes.

It uses one or two addresses according to how the dip-switch is set.

If both channels are enabled (IN1 and IN2), setting the n “base” address through the FXPRO programmer, the input address and address+1 (consecutive) will be automatically assigned to the module.

ID Value R/W Description
i<address>.1 0 ... 255 R range –40 ÷ +87.5°C: code 0 corresponds to –40°C and code 255 corresponds to +87.5°C
i<address+1>.1 0 ... 255 R range –40 ÷ +87.5°C: code 0 corresponds to –40°C and code 255 corresponds to +87.5°C

MODCNT

4-channel counter module in modular housing.

It uses one input address of the Contatto bus.

ID Value R/W Description
i<address>.1 0 ... 65535 R number of pulses
i<address>.2 0 ... 65535 R number of pulses
i<address>.3 0 ... 65535 R number of pulses
i<address>.4 0 ... 65535 R number of pulses

MODNTC

Input module for ambient temperature sensors and potentiometers.

It uses one input address of the Contatto bus.

The temperature values measured by MODNTC module are reported as Kelvin degrees multiplied by 10; in other words, 0°C will be reported as 2730, 0.1°C will be reported as 2731 and so on.

Concerning the potentiometer channels, the values read from the module will be 0 with the potentiometer at its minimum position and it will be 1000 with the potentiometer at its maximum position.

ID Value R/W Description
i<address>.1 0 ... 4095 R temperature value
i<address>.2 0 ... 4095 R temperature value
i<address>.3 0 ... 4095 R temperature value
i<address>.4 0 ... 4095 R temperature value

MOD4I/A

4-digital input module for NO contacts in modular housing.

It uses one input address in the range 1 to 127 of the Contatto bus.

ID Value R/W Description
i<address> 0 R input pin 1 off
1 R input pin 1 on
i<address+1> 0 R input pin 1 off
1 R input pin 1 on
i<address+2> 0 R input pin 1 off
1 R input pin 1 on
i<address+3> 0 R input pin 1 off
1 R input pin 1 on

MOD4I/S

4-digital input module for NO contacts in 2M modular housing.

It uses one address of the Contatto bus.

ID Value R/W Description
i<address> 0 R input pin 1 off
1 R input pin 1 on
i<address+1> 0 R input pin 1 off
1 R input pin 1 on
i<address+2> 0 R input pin 1 off
1 R input pin 1 on
i<address+3> 0 R input pin 1 off
1 R input pin 1 on

MODLUX

Ambient light measurement module with sensor for ceiling mounting.

It uses one address of the Contatto bus.

ID Value R/W Description
i<address>.1 0 ... 1023 R ambient brightness value

MODMETEO

Meteorological data detection module for Contatto bus.

It uses one input address and, if enabled by the configuration panel of MCP IDE, one output address with the same value.

ID Value R/W Description
i<address>.temp <temp> R temperature value (in C/10)
i<address>.lux <lux*10> R daylight value in tens of LUX
i<address>.wind 1 m/s / 10 R wind speed value
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 temperature < threshold
1 R measured temperature > threshold
i<address>.lux.limit 0 R measured daylight < threshold
1 R measured daylight > threshold
i<address>.wind.limit 0 R measured wind speed < threshold
1 R measured wind speed > threshold
i<address>.light.south 0 R light not from South
1 R light from South
i<address>.light.west 0 R light not from West
1 R light from West
i<address>.light.east 0 R light not from East
1 R light from East
i<address>.fault 0 R sensor works correctly
1 R sensor failure
o<address>.temp <temp> RW temperature threshold (in C/10)
off RW temperature threshold off
o<address>.lux <lux*10> RW daylight threshold
off RW daylight threshold off
o<address>.wind 1 m/s / 10 RW wind speed threshold
off RW wind speed threshold off

MOD8R

8 power relay output module.

It uses one output address of the Contatto 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
o<address>.5 0 RW output pin 5 off
1 RW output pin 5 on
o<address>.6 0 RW output pin 6 off
1 RW output pin 6 on
o<address>.7 0 RW output pin 7 off
1 RW output pin 7 on
o<address>.8 0 RW output pin 8 off
1 RW output pin 8 on

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

MODPNP

8 positive logic (PNP) “open collector” digital output module.

It uses one output address in the range 1 to 127 of the Contatto 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
o<address>.5 0 RW output pin 5 off
1 RW output pin 5 on
o<address>.6 0 RW output pin 6 off
1 RW output pin 6 on
o<address>.7 0 RW output pin 7 off
1 RW output pin 7 on
o<address>.8 0 RW output pin 8 off
1 RW output pin 8 on

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

MODREL

8 relay output compact module in DIN 3M housing.

It uses one output address in the range 1 to 127 of the Contatto 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
o<address>.5 0 RW output pin 5 off
1 RW output pin 5 on
o<address>.6 0 RW output pin 6 off
1 RW output pin 6 on
o<address>.7 0 RW output pin 7 off
1 RW output pin 7 on
o<address>.8 0 RW output pin 8 off
1 RW output pin 8 on

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

MOAN/U

0÷10V analog output module.

It uses one output address in the range 1 to 127 of the Contatto bus.

ID Value R/W Description
o<address> x/255 R value in fractional format, where 0 ≤ x ≤ 255
o<address> <x%> W the percentage of signal (0÷100%) applied to the output
0...255 W convert the 8 bits digital code received through the bus in the proper analog level.
x/y W fractional format, formatted as “x/y”, where 0 ≤ x ≤ y

MO420

4÷20mA analog output module.

It uses one output address in the range 1 to 127 of the Contatto bus.

ID Value R/W Description
o<address> <x%> RW the percentage of signal (0÷100%) applied to the output
0...255 RW convert the 8 bits digital code received through the bus in the proper analog level
x/y RW fractional format, formatted as “x/y”, where 0 ≤ x ≤ y

MODLC and MODLC-P

Ambient light regulator module with integrated sensor.

It uses one input address and, if enabled by the configuration panel of MCP IDE, one output address with the same value.

ID Value R/W Description
i<address>.lux value equivalent to three times the brightness in lux detected by the sensor R the brightness value in lux detected by the MODLC
i<address>.level calculated value for the automatic brightness regulation R the value to be sent to the dimmer in order to execute the automatic regulation
i<address>.mode auto R automatic regulation
man R manual regulation
i<address>.in 0 R digital input 2 (including presence delay) OFF
1 R digital input 2 (including presence delay) ON
i<address>.in1 0 R digital input 1 OFF
1 R digital input 1 ON
i<address>.in2 0 R digital input 2 OFF
1 R digital input 2 ON
o<address>.setpoint setpoint value RW set the setpoint for the automatic brightness regulation
o<address>.preset setpoint value RW set the preset dimmer value (SMART mode only)
o<address>.delay setpoint value RW set the presence detector delay in seconds
o<address>.mode auto RW set automatic control
man RW set manual control
o<address>.in.reset 0 R not active
1 RW force the expiring of the deactivation delay time of the digital input
o<address>.mode.reset 0 RW not active
1 RW disable automatic control
o<address>.full.reset 0 RW not active
1 RW perform a full reset
o<address>.v 0 RW virtual point off
1 RW virtual point on
o<address>.in.disable 0 RW normal presence detector operation (SMART mode)
1 RW disable light ON control from presence detector (SMART mode)
o<address>.presence 0 RW not active
1 RW presence forced

MOD4-4S

4 digital input and 4 power relay output multifunction module.

HSYCO supports two configurations only: four independent outputs, or two shutters.

When set as four independent outputs, the module must be configured with the same base address for input and output.

For example: 

(I20, O20)

The input address must be enabled. Configuration switches must be set as SW1=OFF, SW2=OFF and SW5=ON.

When set as two shutters, the module must be configured with the same base address for input and output.

For example: 

(I20, O20, O21)

The input address must be enabled. Configuration switches must be set as SW1=ON, SW2=ON and SW5=ON.

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
o<address>.1 up RW shutter up command
down RW shutter down command
stop RW shutter stop command
unknown R unknown state
offup R shutter off, up position
offdown R shutter off, down position
o<address+1>.1 up RW shutter up command
down RW shutter down command
stop RW shutter stop command
unknown R unknown state
offup R shutter off, up position
offdown R shutter off, down position
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

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

MOD2-2R

2 digital input and 2 power relay output module.

It uses one input address and one output address in the range 1 to 127 of the Contatto bus.

The input and the output addresses may be the same or they can be different each one to the other.

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

MOD4-4R

4 digital input and 4 digital output module.

It uses one input address and one output address in the range 1 to 127 of the Contatto bus.

The input and the output addresses may be the same or they can be different each one to the other.

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

MOD2DM

2x300W dimmer module.

It uses 2 output addresses (one for each dimmer channel) and 2 input addresses.

HSYCO supports this module only when its dip-switches are set as SW1=ON, SW2=ON, SW3=ON, SW4=ON.

ID Value R/W Description
i<address> 0...100 R brightness level according to current ramp
off R dimmer off
i<address+1> 0...100 R brightness level according to current ramp
off R dimmer off
o<address> 0...100 RW brightness level according to current ramp
off RW dimmer off
101...255 W command (see MOD2DM commands table)
o<address+1> 0...100 RW brightness level according to current ramp
off RW dimmer off
101...255 W command (see MOD2DM commands table)

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.

MOD2DV

Dual 1-10V output for electronic ballast driving.

It uses 2 output addresses (one for each dimmer channel) and 2 input addresses.

HSYCO supports this module only when its dip-switches are set as SW1=ON, SW2=ON, SW3=ON, SW4=ON.

ID Value R/W Description
i<address> 0...100 R brightness level according to current ramp
off R dimmer off
i<address+1> 0...100 R brightness level according to current ramp
off R dimmer off
o<address> 0...100 RW brightness level according to current ramp
off RW dimmer off
101...255 W command (see MOD2DV commands table)
o<address+1> 0...100 RW brightness level according to current ramp
off RW dimmer off
101...255 W command (see MOD2DV commands table)

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.

MOD8IL

8 digital input – 8 LED output module for wall box.

It uses 1 input address and 1 output address.

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
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
o<address>.5 0 RW output pin 5 off
1 RW output pin 5 on
o<address>.6 0 RW output pin 6 off
1 RW output pin 6 on
o<address>.7 0 RW output pin 7 off
1 RW output pin 7 on
o<address>.8 0 RW output pin 8 off
1 RW output pin 8 on

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

MOD4DV

Quad 0-10V output module for generic applications or for external dimmers control.

It uses 4 consecutive output addresses (one for each dimmer channel) and 4 input addresses.

HSYCO supports this module only when its dip-switches are set as SW1=ON, SW2=ON, SW3=ON, SW4=ON, SW5=OFF.

ID Value R/W Description
i<address> 0...100 R brightness level according to current ramp
off R dimmer off
i<address+1> 0...100 R brightness level according to current ramp
off R dimmer off
i<address+2> 0...100 R brightness level according to current ramp
off R dimmer off
i<address+3> 0...100 R brightness level according to current ramp
off R dimmer off
o<address> 0...100 RW brightness level according to current ramp
off RW dimmer off
101...255 W command (see MOD4DV commands table)
o<address+1> 0...100 RW brightness level according to current ramp
off RW dimmer off
101...255 W command (see MOD4DV commands table)
o<address+2> 0...100 RW brightness level according to current ramp
off RW dimmer off
101...255 W command (see MOD4DV commands table)
o<address+3> 0...100 RW brightness level according to current ramp
off RW dimmer off
101...255 W command (see MOD4DV commands table)

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 “x/y”, where 0 <= x <= y
  • values in the range 101÷255. Values and commands are described in the MOD4DV Programming Handbook (Operation from the bus, page 3).

MODDMX

ModDMX module allows to handle, through the Contatto bus, up to 32 DMX devices. ModDMX module makes possible the communication on the first 64 of 512 DMX channels allowed by this protocol.

It uses 1 output address, 1-channel 16-bit.

ID Value R/W Description
o<address>.<DMX address> 0...100 RW Values and commands are described in the MODDMX Programming Handbook

MODDALI

The ModDALI module supports 4 DALI lines, with up to 32 devices for each line. The ModDALI module with firmware version 6.x supports 2 DALI lines (channels 1 and 2), with up to 64 devices for each line.

It uses 1 output address and, if enabled, 1 input address with the same value.

ID Value R/W Description
o<address>.<line> refresh RW queries the ModDALI module to update the current status of all DALI devices. This command requires a considerable amount of bus time and blocks all other commands until completed
o<address>.<line>
o<address>.<line>.all
o<address>.<line>.0 		off RW switch off all available DALI devices
<level> RW set a level for all available devices
o<address>.<line>.group.<DALI group> off RW switch off all DALI devices on that group
<level> RW set a level for all DALI devices in that group
o<address>.<line>.<DALI address> off RW switch off a single DALI device
<level> RW set a level for a single DALI device
fault R DALI device fault
unknown R DALI device unknown state (or connection lost)
>100 RW special functions: possible values are described in the MODDALI Programming Handbook
i<address>.<line>.polling off R polling disabled
on R polling enabled
i<address>.<line>.test 0 R test button not pressed
1 R test button pressed
i<address>.<line>.dali nopower R DALI bus power supply failure
open R DALI line broken
short R DALI line short circuit
on R on DALI line
i<address>.<line>.1 off R ballast 1 off
<level> R ballast 1 level
fault R ballast 1 lamp failure
unknown R ballast 1 lamp unknown state (or connection lost)

The DALI device 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 “x/y”, where 0 <= x <= y
  • values in the range 101÷255. Values and commands are described in the MODDALI Programming Handbook.

MODDALI8

The ModDALI8 module allows the management of 8 DALI lines, with up to 16 devices for each line (or channel).

It uses 2 consecutive input addresses and 1 input address with the same base value.

ID Value R/W Description
o<address>.<line> off RW off broadcast command
<level> RW level broadcast command
i<address>.<line>.polling off RW polling disabled
on RW polling enabled
i<address>.<line>.test 0 RW test button not pressed
1 RW test button pressed
i<address>.<line>.dali fault RW lamp failure
open RW no DALI device connected to this line
short RW DALI line short circuit
on RW DALI line working correctly

<line> can be set from 1 to 8 to address a single line, or 0 to send commands to all DALI lines.


The line 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 “x/y”, where 0 <= x <= y
  • values in the range 101÷255. Values and commands are described in the MODDALI8 Programming Handbook.

CLIMA2

Module for the regulation of the ambient temperature.

It uses 1 input and 1 output address that are equal each one to the other, so only a base address is needed.

ID Value R/W Description
i<address> on R zone on
off R zone off
i<address>.mode summer R summer mode
winter R winter mode
i<address>.status off R off status
heating R heating request
cooling R cooling request
i<address>.fan off R fan off
min R min speed
med R med speed
max R max speed
i<address>.temp fault R NTC probe fault
<temp> R ambient temperature value, in C/10
i<address>.setpoint.temp <temp> R real setpoint value, in C/10
i<address>.knob 0 ... 1000 R position of rotary knob
o<address>.mode summer RW set summer
winter RW set winter
o<address> on RW zone on
off RW zone off
o<address>.setpoint.temp 0...400 RW set and read the value of central setpoint (temp in C/10)
o<address>.setpoint.delta.neg <temp> RW set and read the MAX negative delta
o<address>.setpoint.delta.pos <temp> RW set and read the MAX positive delta
o<address>.led.1 red
r 		RW LED 1 red
green
g 		RW LED 1 green
yellow
y 		RW LED 1 yellow
off RW set off
o<address>.led.2 red
r 		RW LED 2 red
green
g 		RW LED 2 green
yellow
y 		RW LED 2 yellow
off RW set off
o<address>.led.3 red
r 		RW LED 3 red
green
g 		RW LED 3 green
yellow
y 		RW LED 3 yellow
off RW set off
o<address>.led.4 red
r 		RW LED 4 red
green
g 		RW LED 4 green
yellow
y 		RW LED 4 yellow
off RW set off

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

MODANA

Network analyzer module for Contatto bus.

It uses, in dynamic mode, up to a maximum of 5 consecutive input addresses and, if enabled, 1 output address equal to the base address.

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


Note The module must be configured with the same base address for input and output.

For example: 

(I7, O7)
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 hour-meter
i<address>.temperature [°C] R cabinet temperature
i<address>.energy.active [KWh] R positive active energy
i<address>.energy.activeneg [KWh] R negative active energy
i<address>.energy.reactive [KVARh] R positive reactive energy
i<address>.energy.reactiveneg [KVARh] R negative reactive energy
i<address>.pm [W] R average positive active power
i<address>.qm [VAR] R average positive reactive power
o<address>.reset.energy 1 RW reset energies
0 RW ---
o<address>.reset.hours 1 RW reset hour-meter
0 RW ---

MODANAM

Network analyzer module for Contatto bus.

It uses, in dynamic mode, up to a maximum of 5 consecutive input addresses and, if enabled, 1 output address equal to the base address.

Note The module must be configured with the same base address for input and output.

For example: 

(I7, O7)
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 hour-meter
i<address>.temperature [°C] R cabinet temperature
i<address>.energy.active [KWh] R positive active energy
i<address>.energy.activeneg [KWh] R negative active energy
i<address>.energy.reactive [KVARh] R positive reactive energy
i<address>.energy.reactiveneg [KVARh] R negative reactive energy
o<address>.reset.energy 1 RW reset energies
0 RW ---
o<address>.reset.hours 1 RW reset hour-meter
0 RW ---

MODPQ5

Q5 tags proximity reader and programmer module.

Uses 1 input address on the Contatto bus. Write operations are performed through direct writes to the module’s RAM.

ID Value R/W Description
i<address>.data 0
<tag data> 		R 30 characters hexadecimal representation of the 15 bytes of tag data; “0” if the module is not seeing any tag
i<address>.data.write 0 R the tag has been removed from the programmer after writing, or the module is not seeing any tag
1 R the tag write operation was successful
i<address>.reader.error 0 R reader/writer normal status
1 R reader/writer module error (normally occurs when the reader is not connected to the MODPQ5 module)
i<address>.tag.error 0 R the tag is valid
1 R the tag is not valid
i<address>.request.error 0 R no request or handshake errors detected
1 R handshake error
i<address>.data.error 0 R tag data ok
1 R tag data errors detected
i<address>.unknown.error 0 R no unknown errors
1 R unknown error detected
i<address>.write <tag data> R tag data write successful
error R tag data write error
o<address>.write <tag data> W 30 characters hexadecimal representation of the 15 bytes data to be written on the tag

MODHT

MODHT is the hotel room controller module.

It uses 1 input and 1 output address.

Tags configuration data are written to the module’s EEPROM (persistent internal memory).

ID Value R/W Description
i<address>.door 0 R door closed
1 R door open
i<address>.window 0 R window closed
1 R window open
i<address>.panic 0 R panic request not active
1 R panic request
i<address>.busy 0 R room is free
1 R room is occupied
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>.ev 0 R EV output off
1 R EV output on
i<address>.aux 0 R AUX output off
1 R AUX output on
i<address>.dnd 0 R do not disturb not active
1 R do not disturb
i<address>.service 0 R room service request not active
1 R room service request
i<address>.booked 0 R room is not booked
1 R room is booked
i<address>.mode summer R summer mode
winter R winter mode
i<address>.fan off R fan set to off
auto R fan speed set to auto
min R fan speed set to minimum
med R fan speed set to medium
max R fan speed set to max
i<address>.fan.status 0 R fan is off
1 R fan is on (cooling or heating)
i<address>.temp <temp> R ambient temperature value (in C/10)
i<address>.setpoint.temp <temp> R setpoint value (in C/10)
i<address>.tag.door 1...5 R type of tag that is opening the door (1 to 4 are service tags; 5 is a customer tag). After 5 seconds the value is reset to 0
i<address>.tag.room 0 R no tag present in room’s reader
1...5 R type of tag inserted in the room’s reader (1 to 4 are service tags; 5 is a customer tag)
i<address>.tag.<n> <tag data> R 24 characters hexadecimal representation of the 12 bytes data matching service N tags (N from 1 to 5) stored in module’s EEPROM. Updated on o<address>.tag.<n>=read command
i<address>.pcam.error 0 R PCAM module ok
1 R PCAM module error
i<address>.tpr.error 0 R TPR/H module ok
1 R TPR/H module error
i<address>.mask <mask data> R 24 characters hexadecimal representation of the 12 bytes tag mask stored in module’s EEPROM. Updated on o<address>.mask=read command
i<address>.data.door 0
<tag data> 		R 30 characters hexadecimal representation of the 15 bytes of tag data being read from the door reader; “0” if the module is not seeing any tag (this data point is available with MODHT firmware 5.3 or newer)
i<address>.data.room 0
<tag data> 		R 30 characters hexadecimal representation of the 15 bytes of tag data being read from the room reader; “0” if the module is not seeing any tag (this data point is available with MODHT firmware 5.3 or newer)
i<address>.setpoint.summer.<n>
i<address>.setpoint.winter.<n> 		<temp> R winter/summer setpoint <n> (1...3) current value (in C/10). Updated on o<address>.setpoint.summer.<n>=read and o<address>.setpoint.winter.<n>=read commands
i<address>.setpoint.delta.summer.low
i<address>.setpoint.delta.summer.high
i<address>.setpoint.delta.winter.low
i<address>.setpoint.delta.winter.high 		<temp delta limit>
1...9 		R the current temperature setpoint low/high limits for winter and summer modes (in C). Updated on o<address>.setpoint.delta=read command
o<address>.tag.<n> <tag data> R tag data write successful
error R tag data write error
o<address>.mask <mask data> R mask data write successful
error R mask data write error
o<address>.setpoint.summer.<n>
o<address>.setpoint.winter.<n> 		<temp> R winter/summer setpoint N (1-3) write successful (in C/10)
error R setpoint write error
o<address>.setpoint.delta.summer.low
o<address>.setpoint.delta.summer.high
o<address>.setpoint.delta.winter.low
o<address>.setpoint.delta.winter.high 		<temp delta limit>
1...9 		R setpoint min/max limit for winter/summer write successful (in C)
error R setpoint limit write error
o<address>.ev.enable 0 W EV output disabled
1 W EV output enabled
o<address>.aux.enable 0 W AUX output disabled
1 W AUX output enabled
o<address>.panic.reset 0 W panic request reset off
1 W panic request reset (pulse command)
o<address>.busy 0 W set room status to free
1 W set room status to occupied
o<address>.ev 0 W EV output off
1 W EV output on
o<address>.aux 0 W AUX output off
1 W AUX output on
o<address>.dnd.reset 0 W do not disturb reset off
1 W do not disturb reset (pulse command)
o<address>.service.reset 0 W service reset off
1 W service reset (pulse command)
o<address>.booked 0 W set room as not booked
1 W set room as booked
o<address>.mode summer W set room to summer mode
winter W set room to winter mode
o<address>.fan off W set fan off (pulse command)
auto W set fan to auto mode (pulse command)
o<address>.comfort 0 W force comfort set-point off
1 W force comfort set-point on
o<address>.3 0 W output pin 3 off
1 W output pin 3 on
o<address>.fan.heating.min 0 W reset heating speed limit
1 W limit heating speed to min
o<address>.fan.cooling.min 0 W reset cooling speed limit
1 W limit cooling speed to min
o<address>.tag.<n> read W read the 12 bytes stored in module’s EEPROM for service N tags (<n> from 1 to 5)
<tag data> W 24 characters hexadecimal representation of the 12 bytes data matching service N tags (N from 1 to 5), to be stored in module’s EEPROM. After writing data, you should wait approximately 150ms before sending a read command
o<address>.mask read W read the 12 bytes mask stored in module’s EEPROM
<mask data> W 24 characters hexadecimal representation of the 12 bytes tag mask, to be stored in module’s EEPROM. After writing data, you should wait approximately 150ms before sending a read command
o<address>.setpoint.summer.<n>
o<address>.setpoint.winter.<n> 		read W read winter/summer setpoint <n> (1-3)
<temp> W set winter/summer setpoint <n> (1-3)
o<address>.setpoint.delta read W read winter and summer, low and high setpoint limits
o<address>.setpoint.delta.summer.low
o<address>.setpoint.delta.summer.high
o<address>.setpoint.delta.winter.low
o<address>.setpoint.delta.winter.high 		<temp delta limit> W set winter/summer, low/high setpoint limit (in C)

MODCA

MODCA is the access control module.

It uses 1 input and 1 output address.

Tags configuration data are written to the module’s EEPROM (persistent external memory).

Site codes and the tags mask are written to the internal EEPROM.

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>.blocked 0 R access control enabled
1 R access blocked
i<address>.tpr.error 0 R TPR module ok
1 R TPR module error
i<address>.access.granted.1 0 R no tag present at antenna 1
1 R access granted to tag at antenna 1
i<address>.access.granted.2 0 R no tag present at antenna 2
1 R access granted to tag at antenna 2
i<address>.access.denied 0 R access denied flags reset
site R access denied due to site code error
code R access denied due to user code error
total.limit R access denied due to exceeded total number of access grants
daily.limit R access denied due to exceeded daily number of access grants
time R access denied due to time range violation
day R access denied due to weekday violation
expired R access denied due expired tag
i<address>.denied.code <tag code> R the tag code (decimal value of selected two bytes of the tag data) that was denied access
i<address>.granted.1.code <tag code> R the tag code (decimal value of selected two bytes of the tag data) that was granted access at antenna 1
i<address>.granted.2.code <tag code> R the tag code (decimal value of selected two bytes of the tag data) that was granted access at antenna 2
i<address>.site.<n> <site data> R 16 characters hexadecimal representation of the 8 bytes data representing the Nth site code (N from 1 to 4) stored in module’s EEPROM
i<address>.mask <mask data> R 16 characters hexadecimal representation of the 8 bytes site code mask stored in module’s EEPROM
i<address>.mask <mask data> R 16 characters hexadecimal representation of the 8 bytes site code mask stored in module’s EEPROM
i<address>.user.<n> <user data> R 32 characters hexadecimal representation of the 16 bytes data for user <n> (N from 1 to 2000) stored in module’s EEPROM
o<address>.site.<n> <site data> R site data write successful
error R site data write error
o<address>.mask <mask data> R mask data write successful
error R mask data write error
o<address>.user.<n> <user data> R user data write successful
error R user data write error
o<address>.relay 0 W relay output off
1 W relay output pulse on, with pulse length according to the MODCA configuration (with firmware versions before 1.3 this data point remains at 1 and should be reset to 0 with an explicit command; with firmware 1.3 the data point value follows the relay state, and is automatically reset to 0 at the end of the pulse period)
o<address>.relay.forced 0 W forced relay mode not set (default behaviour)
1 W forced relay mode set: the relay remains closed until the relay.forced command is reset (available with MODCA firmware version 2.0 or later)
o<address>.block 0 W enable access control
1 W block access control
o<address>.access.granted.code 0 W reset
1 W allow access even when site code is not valid
o<address>.access.granted.total.limit 0 W reset
1 W allow access even when the total limit of access grants has been exceeded
o<address>.access.granted.daily.limit 0 W reset
1 W allow access even when the daily limit of access grants has been exceeded
o<address>.access.granted.time 0 W reset
1 W allow access even outside of the allowed timeframe
o<address>.access.granted.day 0 W reset
1 W allow access even outside of the allowed weekdays
o<address>.access.granted.expired 0 W reset
1 W allow access even when the tag is expired
o<address>.site.<n> read W read the 8 bytes stored in module’s EEPROM for site N code (<n> from 1 to 4)
<site data> W 16 characters hexadecimal representation of the 8 bytes data of site N code (N from 1 to 4), to be stored in module’s EEPROM. After writing data, you should wait approximately 100ms before sending a read command
o<address>.mask read W read the 8 bytes mask stored in module’s EEPROM
<mask data> W 16 characters hexadecimal representation of the 8 bytes site code mask, to be stored in module’s EEPROM. After writing data, you should wait approximately 100ms before sending a read command
o<address>.user.<n> read W read the 16 bytes stored in module’s EEPROM for user N (<n> from 1 to 2000)
<user data> W 16 characters hexadecimal representation of the first 8 bytes of access control data for user N (N from 1 to 2000) , to be stored in module’s EEPROM
<reset> W reset to 0 the total and daily counters for user <n>
o<address>.users erase W deletes all users data. This action requires up to about 27 seconds to be completed. It also deletes all i<address>.user.<n> and o<address>.user.<n> data points

MODKB

MODKB is the keypad access control module.

It uses 1 input and 1 output address.

PIN configuration data are written to the module’s EEPROM (persistent memory).

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>.access.granted.<n> 0 R reset
1 R access granted to PIN <n> (<n> from 1 to 30)
i<address>.pin <pin code> R the last pin code entered on the keypad (from 1 to 65535). Reset to 0 after programmed code persistence time
i<address>.access.granted.<n> 0 R access denied flags reset
site R access denied due to site code error
code R access denied due to user code error
time R access denied due to time range violation
day R access denied due to weekday violation
i<address>.pin.<n> <pin data> R 16 characters hexadecimal representation of the 8 bytes data for PIN <n> (<n> from 1 to 30) stored in module’s EEPROM
o<address>.pin.<n> <pin data> R pin data write successful
error R pin data write error
o<address>.relay 0 W relay output off
1 W relay output on (pulse output, resets to 0 immediately after the relay is closed, usually before the relay closure time)
o<address>.lock.all 0 W reset
1 W disables access to all PINs
o<address>.lock.<n> 0 W reset
1 W disables access to PIN <n> (<n> from 1 to 30)
o<address>.pin.<n> read W read the 8 bytes stored in module’s EEPROM for PIN <n> (<n> from 1 to 30)
<pin data> W 16 characters hexadecimal representation of the 8 bytes data for PIN <n> (<n> from 1 to 30), to be stored in module’s EEPROM

MODDI

500W IGBT dimmer module.

It uses 1 output address.

ID Value R/W Description
o<address> 0...100 RW brightness level according to current ramp
off RW dimmer off
101...173 W command (see MODDI commands table)
o<address>.noline 0 R AC line detected
1 R AC line fault
o<address>.overcurrent 0 R normal
1 R overcurrent protection
o<address>.overvoltage 0 R normal
1 R overvoltage protection
o<address>.overtemperature 0 R normal
1 R overtemperature protection

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.

MODCL

Temperature control module.

It uses 1 input and one output address.

ID Value R/W Description
i<address> on R zone on
off R zone off
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> on RW zone on (writing on to this datapoint doesn't turn the zone on, it simply resets the off command)
off RW zone off
o<address>.mode winter RW winter mode
summer RW summer mode
o<address>.setpoint.mode man RW manual mode
auto RW auto mode
off RW zone off
o<address>.setpoint 1 RW setpoint 1
2 RW setpoint 2
3 RW setpoint 3
0 RW setpoint off
man RW manual setpoint
o<address>.setpoint.temp.1 <temp> RW temperature setpoint 1 value (in C/10)
o<address>.setpoint.temp.2 <temp> RW temperature setpoint 2 value (in C/10)
o<address>.setpoint.temp.3 <temp> RW temperature setpoint 3 value (in C/10)
o<address>.setpoint.temp.man <temp> RW temperature manual setpoint value (in C/10)

MOD4TP/I

8 digital input and 4 roller shutters or blinds with detection of travel time.


ID Value R/W Description
i<address>.<N> 0 R input pin N off
1 R input pin N on
o<address>.<N> up RW shutter N up command
down RW shutter N down command
stop W shutter N stop command
off
up1 W shutter N up one step command
down1 W shutter N down one step command
unknown R shutter N unknown state
offup R shutter N off, up position
offdown R shutter N off, down position
0-100 R shutter N current position
o<address>.calibration.<N> 0 R shutter N normal operations
1 RW shutter N calibration command
o<address>.position.<N> 0-100 RW shutter N position command
o<address>.slats.<N> 0-100 W shutter N slats position command (no feedback available)

MODRHT

Temperature, relative humidity and dew point sensor.

It uses one input address and, if enabled by the configuration panel of MCP IDE, one output address.

ID Value R/W Description
i<address>.temp <temp> R temperature value (in C/10)
i<address>.rh <%RH> R relative humidity percentage (0-100)
i<address>.dewpoint <temp> R dew point (in C/10)
i<address>.dewpoint.1 0 R dew point lower than dew point threshold 1
1 R dew point equal or greater than dew point threshold 1
i<address>.dewpoint.2 0 R dew point lower than dew point threshold 2
1 R dew point equal or greater than dew point threshold 2
o<address>.dewpoint.1 <temp> RW dew point threshold 1 (in C/10)
o<address>.dewpoint.2 <temp> RW dew point threshold 2 (in C/10)

MODAM2

Multi-function, 2 inputs analog module.

Uses one input address.

ID Value R/W Description
i<address>.1 <value> R input 1 value (-32768 to +32767)
i<address>.2 <value> R input 2 value (-32768 to +32767)

MODIGLASS and MODIGLASS3

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

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>.led.1 0 R led 1 off
1 R led 1 on
i<address>.led.2 0 R led 2 off
1 R led 2 on
i<address>.led.3 0 R led 3 off
1 R led 3 on
i<address>.led.4 0 R led 4 off
1 R led 4 on
i<address>.led.5 0 R led 5 off
1 R led 5 on
i<address>.led.6 0 R led 6 off
1 R led 6 on
i<address>.proximity 0 R no proximity detected
1 R proximity detected
o<address>.led.1 0 W led 1 off
1 W led 1 on
o<address>.led.2 0 W led 2 off
1 W led 2 on
o<address>.led.3 0 W led 3 off
1 W led 3 on
o<address>.led.4 0 W led 4 off
1 W led 4 on
o<address>.led.5 0 W led 5 off
1 W led 5 on
o<address>.led.6 0 W led 6 off
1 W led 6 on
o<address>.disable 0 RW not disabled (normal mode)
1 RW disabled (cleaning mode)
o<address>.dim 0 RW high intensity backlight
1 RW low intensity backlight
o<address>.proximity 0 RW disable proximity backlight
1 RW enable proximity backlight
o<address>.backlight 0 RW backlight off
1 RW backlight on
o<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.

User Interface

All CONTATTO 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 Contatto Project Editor.png


Besides the direct association of control buttons and data points, the CONTATTO driver also automatically updates graphical objects that represent values or states of complex devices, like the CLIMA2 temperature control unit. It will also automatically intercept buttons to manually set operation modes and temperature set-points.

CLIMA2

You can use the temp and tempmini objects to control CLIMA2 devices.


UI Object clima2.png


The fan button, in the bottom right-hand corner, is not enabled because the manual control of the fan speed is not available. The M button, in the top right-hand corner, allows to switch the module on or off.

You can also easily create customized controls for the CLIMA2, using standard graphic objects that are automatically set to show the device’s status and intercepted to send user commands.

UISET Actions

ID Attribute Set to Description
<address>.mode value SUMMER summer mode (cooling)
value WINTER winter mode (heating)
<address>.mode.label.summer visible true if CLIMA2 is in summer mode
<address>.mode.label.winter visible true if CLIMA2 is in winter mode
<address>.status value OFF zone off
value 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>.fan value OFF fan off
value MIN minimum fan speed
value MED medium fan speed
value MAX maximum fan speed
<address>.fan.label.min visible true minimum fan speed
<address>.fan.label.med visible true medium fan speed
<address>.fan.label.max visible true maximum fan speed
<address>.setpoint.label.on visible true zone is on
<address>.setpoint.label.off visible true zone is off
<address>.setpoint.mode value ON zone is on
value OFF zone is off
<address>.setpoint.temp value <value> the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.temp value <temp> the measured temperature, in Celsius degrees with one decimal digit, followed by " °C"
FAULT fault/error condition

USER Commands

Name Param Action
<address> on module on
off module off
mode.summer set summer mode (cooling)
mode.winter set winter mode (heating)
<address>.setpoint temp.up increase setpoint temperature in 0.5C steps
temp.down decrease setpoint temperature in 0.5C steps
0...400 set the setpoint to the defined value (in C/10)
mode cycle through on and off modes
mode.on module on
mode.off module off


MODCL

You can use the temp and tempmini objects to control MODCL devices.


The fan button, in the bottom right-hand corner, is not enabled because the manual control of the fan speed is not available. The M button, in the top right-hand corner, allows to switch the module to auto or manual mode, or off.

You can also easily create customized controls for the MODCL, using standard graphic objects that are automatically set to show the device’s status and intercepted to send user commands.

UISET Actions

ID Attribute Set to Description
<address>.mode value SUMMER summer mode (cooling)
WINTER winter mode (heating)
<address>.mode.label.summer visible true if MODCL is in summer mode
<address>.mode.label.winter visible true if MODCL 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>.fan value OFF fan off
MIN minimum fan speed
MED medium fan speed
MAX maximum fan speed
<address>.fan.label.min visible true minimum fan speed
<address>.fan.label.med visible true medium fan speed
<address>.fan.label.max visible true maximum fan speed
<address>.setpoint value 1, 2, 3 setpoint N is active
MAN manual setpoint is active
OFF zone is off
<address>.setpoint.label.1 visible true setpoint 1 is active
<address>.setpoint.label.2 visible true setpoint 3 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 AUTO automatic mode
MAN manual mode
OFF zone is off
<address>.setpoint.temp value <value> the active setpoint temperature, in Celsius degrees with one decimal digit, followed by " °C"
<address>.temp value <temp> the measured temperature, in Celsius degrees with one decimal digit, followed by " °C"
FAULT fault/error condition

USER Commands

Name Param Action
<address> mode cycle summer/winter modes
<address>.mode mode.summer set summer mode (cooling)
mode.winter set winter mode (heating)
<address>.setpoint.temp up increase current setpoint temperature in 0.5C steps
down decrease current setpoint temperature in 0.5C steps
<address>.setpoint.temp.N up increase setpoint N temperature in 0.5C steps
down decrease setpoint N temperature in 0.5C steps
0...400 set setpoint N to the given value (in C/10)
<address>.setpoint.temp.man up increase manual setpoint temperature in 0.5C steps
down decrease manual setpoint temperature in 0.5C steps
0...400 set manual setpoint to the given value (in C/10)
<address>.setpoint mode cycle through auto, manual and off modes
<address>.setpoint.mode auto set auto mode
man set manual mode
off zone off

MOD4TP/I

Using slider objects for MOD4TP/I shutter's position

You can use the slider objects, sliderv and sliderh, to display and control the position. Set both the slider's ID and address to <server_name>.<address>.<N>, with N from 1 to 4.

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.

Release Notes

3.8.0

  • new option "disablemodhtpulsereset", disables automatic reset of MODHT pulse outputs (panic.reset, dnd.reset, service.reset, fan)
  • improved support for MCP firmware upload
  • fixes to MODANA and MODANAM: energy data points not updated when energy not changing on all three phases
  • fixes to MODPQ5 write commands, that failed when another device on the bus had the same output address of MODPQ5 input address

3.7.0

  • support of MODRHT
  • support of MODAM2
  • support of MODIGLASS, MODIGLASS3
  • support of MODLC firmware version 3.2
  • support of MODDALI firmware version 6.x
  • support of MCP counters
  • bus and modules fault detection
  • fixes to the MODDALI ballast 1 status data point

3.6.0

  • added support for MOD32IL
  • added support for MOD4TP/I
  • added support for MODDALI8
  • added support for MODANAM
  • fixed a bug that could cause erroneous readings of MODANA's ptotk datapoint when total active power is negative

3.5.1

  • MODANA updated to support negative active energy values (fw. 1.5 or later)

3.5.0

  • added support for MCP4
  • added support for MODCA firmware version 2.0, with new "relay.forced" datapoint
  • added support for MOD32IN
  • MODPQ5 is now identified with its unique ID. Use MCPIDE 3.2.3 or later to program the MCPXT/MCP4 to allow HSYCO to correctly identify this module

3.4.0

  • improved communication error logging
  • improved support of tools remote access
  • events generated during startup if startupevents=true are now executed sequentially
  • support for MODDI
  • support for MODCL

3.2.2

bug fixes:

  • the toolspassword optional parameter was incorrectly converted to lower case
  • fixed a bug that prevented reading the last 3 addresses of MOAN/I4 and MI420-X4 modules

3.2.1

  • added support for MODHT set-point delta limits read and write
  • the lux datapoint name was incorrectly set to ID.i<addr>.1 instead of ID.i<addr>.lux

3.2.0

  • support for MODCA, MODHT, MODKB, MODPQ5
  • new "detectevents" option, generates forced events when a device is detected at start-up
  • support for the toolspassword option, to allow MCP-IDE and other tools secure remote access to the MCP via HSYCO
  • new clock datapoint to read the MXP-XT internal clock and set it to HSYCO's time

3.0.3

  • optimized performance of MCP’s registers status polling
  • the server failed to initialized when an unsupported device was configured in the MCP

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

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

Retrieved from "https://wiki.hsyco.com/3.8/index.php?title=Contatto&oldid=10896"