Difference between revisions of "DUELUX"
Jump to navigation
Jump to search
| (21 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | DUELUX is a lighting system based on the DALI-2 | + | DUELUX is a lighting system based on the DALI-2 industry-standard protocol for lighting control. HSYCO integrates this system and communicates with it through the DLCP gateway module via a TCP/IP connection. |
[[Category:I/O Server]] | [[Category:I/O Server]] | ||
== HSYCO Configuration == | == HSYCO Configuration == | ||
| − | Add an DUELUX I/O Server in the [[Settings#I/O Servers|I/O Servers section of the Settings]] and set its parameters | + | Add an DUELUX I/O Server in the [[Settings#I/O Servers|I/O Servers section of the Settings]] and set its parameters. |
| + | |||
| + | {{note|Note that the DUELUX I/O Server counts as 1/4 unit in the I/O servers license total.}} | ||
| + | |||
=== Communication === | === Communication === | ||
| Line 32: | Line 35: | ||
|rowspan="2"|groupdiscovery | |rowspan="2"|groupdiscovery | ||
| − | |rowspan="2"| | + | |rowspan="2"|true |
|true | |true | ||
|auto-detects DALI groups as configured in the DLCP, 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 | |auto-detects DALI groups as configured in the DLCP, 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 | ||
| Line 52: | Line 55: | ||
|rowspan="2"|false | |rowspan="2"|false | ||
|true | |true | ||
| − | |polls the DLCP areas/ | + | |polls the DLCP areas/scenarios set point and delay configuration settings |
|- | |- | ||
|false | |false | ||
| Line 118: | Line 121: | ||
|offline | |offline | ||
|R | |R | ||
| − | |HSYCO can't connect to the | + | |HSYCO can't connect to the DLCP |
| + | |- | ||
| + | |||
| + | |rowspan="3"|clock | ||
| + | |yyyy-mm-dd hh:mm:ss | ||
| + | |R | ||
| + | |the DLCP clock current time | ||
| + | |- | ||
| + | |read | ||
| + | |W | ||
| + | |read the DLCP clock, and the delta with HSYCO’s time | ||
| + | |- | ||
| + | |sync | ||
| + | |W | ||
| + | |set the DLCP clock to HSYCO’s current time | ||
| + | |- | ||
| + | |||
| + | |clock.delta | ||
| + | |integer number | ||
| + | |R | ||
| + | |the delta time in seconds between the DLCP and HSYCO clocks. A positive number means that the DLCP clock is ahead of HSYCO | ||
| + | |- | ||
| + | |||
| + | |rowspan="2" |a<n>.s<m>.auto | ||
| + | |0 | ||
| + | |R | ||
| + | |area <n> scenario <m> automatic control is off | ||
| + | |- | ||
| + | |1 | ||
| + | |R | ||
| + | |area <n> scenario <m> automatic control is on | ||
| + | |- | ||
| + | |||
| + | |rowspan="2" |a<n>.s<m>.delay | ||
| + | |rowspan="2" |0...65535 | ||
| + | |R | ||
| + | |area <n> scenario <m> delay in seconds (refreshed every 10 seconds) | ||
| + | |- | ||
| + | |W | ||
| + | |set area <n> scenario <m> delay in seconds | ||
| + | |- | ||
| + | |||
| + | |rowspan="2" |a<n>.s<m>.setpoint | ||
| + | |rowspan="2" |0...65535 | ||
| + | |R | ||
| + | |area <n> scenario <m> setpoint (refreshed every 10 seconds) | ||
| + | |- | ||
| + | |W | ||
| + | |set area <n> scenario <m> setpoint level | ||
| + | |- | ||
| + | |||
| + | |rowspan="1"|ai<n>.<m> | ||
| + | |0...255 | ||
| + | |R | ||
| + | |analog value for input <m> of device <n> | ||
| + | |- | ||
| + | |||
| + | |rowspan="4"|c<n> | ||
| + | |rowspan="2"|0 | ||
| + | |R | ||
| + | |binary command <n> off | ||
| + | |- | ||
| + | |W | ||
| + | |set command <n> off (setting value to "off" is equivalent to "0") | ||
| + | |- | ||
| + | |rowspan="2"|1 | ||
| + | |R | ||
| + | |binary command <n> on | ||
| + | |- | ||
| + | |W | ||
| + | |set command <n> on (setting value to "on" is equivalent to "1") | ||
|- | |- | ||
| Line 124: | Line 197: | ||
|0 | |0 | ||
|R | |R | ||
| − | |digital input <m> of device <n> is off | + | |digital input <m> of device address <n> is off |
|- | |- | ||
|1 | |1 | ||
|R | |R | ||
| − | |digital input <m> of device <n> is on | + | |digital input <m> of device address <n> is on |
|- | |- | ||
| Line 162: | Line 235: | ||
|rowspan="2"|off | |rowspan="2"|off | ||
|R | |R | ||
| − | | | + | |output is off |
|- | |- | ||
|W | |W | ||
| Line 177: | Line 250: | ||
|W | |W | ||
|set the light level of the output to the specified fraction (e.g. a value of 1/5 corresponds to 20%) | |set the light level of the output to the specified fraction (e.g. a value of 1/5 corresponds to 20%) | ||
| + | |- | ||
| + | |||
| + | |rowspan="1"|detected.input.ai<n>.<m> | ||
| + | |<type> | ||
| + | |R | ||
| + | |analog input <m> of device address <n> detected. Types: light sensor | ||
| + | |- | ||
| + | |||
| + | |rowspan="1"|detected.input.di<n>.<m> | ||
| + | |<type> | ||
| + | |R | ||
| + | |digital input <m> of device address <n> detected. Types: push-button, switch, occupancy sensor | ||
| + | |- | ||
| + | |||
| + | |rowspan="1"|detected.output.o<n> | ||
| + | |<type> | ||
| + | |R | ||
| + | |output address <n> detected. Types: lamp | ||
|- | |- | ||
|rowspan="1"|o<n>.time | |rowspan="1"|o<n>.time | ||
| − | | | + | |0...2^32 - 1 |
|R | |R | ||
|the amount of time the output has been turned on, in seconds (refreshed every 60 seconds) | |the amount of time the output has been turned on, in seconds (refreshed every 60 seconds) | ||
| Line 189: | Line 280: | ||
== User Interface == | == User Interface == | ||
All the devices that have been defined in the systemtopo.txt database are automatically listed in the Web Editor. Adding a slider to control a dimmer requires just a few clicks and no additional EVENTS logic. | All the devices that have been defined in the systemtopo.txt database are automatically listed in the Web Editor. Adding a slider to control a dimmer requires just a few clicks and no additional EVENTS logic. | ||
| − | |||
| − | |||
| − | |||
== Release Notes == | == Release Notes == | ||
Latest revision as of 10:24, 21 September 2020
DUELUX is a lighting system based on the DALI-2 industry-standard protocol for lighting control. HSYCO integrates this system and communicates with it through the DLCP gateway module via a TCP/IP connection.
Contents
HSYCO Configuration
Add an DUELUX I/O Server in the I/O Servers section of the Settings and set its parameters.
Note that the DUELUX I/O Server counts as 1/4 unit in the I/O servers license total.
Communication
- IP Address: host name or IP address of the DLCP gateway
- IP Port: TCP/IP port of the DLCP gateway (defaults to 80 if not set)
High Availability
- Shutdown when inactive: defaults to false.
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 | ||
| groupdiscovery | true | true | auto-detects DALI groups as configured in the DLCP, 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 DALI output devices as configured in the DLCP, 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 | ||
| areasconfiguration | false | true | polls the DLCP areas/scenarios set point and delay configuration settings |
| false | areas configuration polling disabled | ||
| 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 |
The Device Configuration Database
The systemtopo.txt file contains the list of all groups and individual outputs that could be directly associated to graphic objects in the Web-based user interface. This file can be filled manually or automatically by HSYCO at start-up. To enable automatic discovery, set the 'groupdiscovery' and/or 'outputdiscovery' option to true.
This is an example of an automatically generated systemtopo.txt file:
(devices) dlcp.g1 : LIGHT ; DIMMER ; G1 dlcp.g10 : LIGHT ; DIMMER ; G10 dlcp.g11 : LIGHT ; DIMMER ; G11 dlcp.g12 : LIGHT ; DIMMER ; G12 dlcp.g13 : LIGHT ; DIMMER ; G13 dlcp.g14 : LIGHT ; DIMMER ; G14 dlcp.g15 : LIGHT ; DIMMER ; G15 dlcp.g16 : LIGHT ; DIMMER ; G16 dlcp.g2 : LIGHT ; DIMMER ; G2 dlcp.g3 : LIGHT ; DIMMER ; G3 dlcp.g4 : LIGHT ; DIMMER ; G4 dlcp.g5 : LIGHT ; DIMMER ; G5 dlcp.g6 : LIGHT ; DIMMER ; G6 dlcp.g7 : LIGHT ; DIMMER ; G7 dlcp.g8 : LIGHT ; DIMMER ; G8 dlcp.g9 : LIGHT ; DIMMER ; G9 dlcp.o1 : LIGHT ; DIMMER ; O1 dlcp.o2 : LIGHT ; DIMMER ; O2 dlcp.o3 : LIGHT ; DIMMER ; O3 dlcp.o4 : LIGHT ; DIMMER ; O4
You should then manually add comments and other optional parameters.
Datapoints
| ID | Value | R/W | Description |
|---|---|---|---|
| connection | online | R | connection established |
| offline | R | HSYCO can't connect to the DLCP | |
| clock | yyyy-mm-dd hh:mm:ss | R | the DLCP clock current time |
| read | W | read the DLCP clock, and the delta with HSYCO’s time | |
| sync | W | set the DLCP clock to HSYCO’s current time | |
| clock.delta | integer number | R | the delta time in seconds between the DLCP and HSYCO clocks. A positive number means that the DLCP clock is ahead of HSYCO |
| a<n>.s<m>.auto | 0 | R | area <n> scenario <m> automatic control is off |
| 1 | R | area <n> scenario <m> automatic control is on | |
| a<n>.s<m>.delay | 0...65535 | R | area <n> scenario <m> delay in seconds (refreshed every 10 seconds) |
| W | set area <n> scenario <m> delay in seconds | ||
| a<n>.s<m>.setpoint | 0...65535 | R | area <n> scenario <m> setpoint (refreshed every 10 seconds) |
| W | set area <n> scenario <m> setpoint level | ||
| ai<n>.<m> | 0...255 | R | analog value for input <m> of device <n> |
| c<n> | 0 | R | binary command <n> off |
| W | set command <n> off (setting value to "off" is equivalent to "0") | ||
| 1 | R | binary command <n> on | |
| W | set command <n> on (setting value to "on" is equivalent to "1") | ||
| di<n>.<m> | 0 | R | digital input <m> of device address <n> is off |
| 1 | R | digital input <m> of device address <n> is on | |
| g<n> | on | W | set the light level of the group to the last level set before the off command |
| off | R | group is off | |
| W | switch group off | ||
| 1...100% | R | current light level | |
| W | set the light level of the group to the specified value (the % leading character is optional. Value range is from 0 to 100) | ||
| X/Y | W | set the light level of the group to the specified fraction (e.g. a value of 1/5 corresponds to 20%) | |
| o<n> | on | W | set the light level of a specific output address to the last level set before the off command |
| off | R | output is off | |
| W | switch output off | ||
| 1...100% | R | current light level | |
| W | set the light level of the output to the specified value (the % leading character is optional. Value range is from 0 to 100) | ||
| X/Y | W | set the light level of the output to the specified fraction (e.g. a value of 1/5 corresponds to 20%) | |
| detected.input.ai<n>.<m> | <type> | R | analog input <m> of device address <n> detected. Types: light sensor |
| detected.input.di<n>.<m> | <type> | R | digital input <m> of device address <n> detected. Types: push-button, switch, occupancy sensor |
| detected.output.o<n> | <type> | R | output address <n> detected. Types: lamp |
| o<n>.time | 0...2^32 - 1 | R | the amount of time the output has been turned on, in seconds (refreshed every 60 seconds) |
User Interface
All the devices that have been defined in the systemtopo.txt database are automatically listed in the Web Editor. Adding a slider to control a dimmer requires just a few clicks and no additional EVENTS logic.
Release Notes
3.7.0
- initial release
DUELUX is a registered trademark of DUEMMEGI SRL. DALI, the DALI Logo, DALI-2 and the DALI-2 Logo are trademarks in various countries in the exclusive use of the Digital Illumination Interface Alliance.
