Versions Compared

Old Version 102

changes.mady.by.user Wolfgang Granzer

Saved on

compared with

New Version 103

changes.mady.by.user Wolfgang Granzer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Functionality

The NETx LaMPS Module is an extension to the NETx BMS Server that has the aim to make the management of lighting control systems more easier. It consists of two parts: the first one provides general functionality for monitoring lighting circuits. It is possible to monitor the operating hours, and defining thresholds for triggering alarms. In addition it is possible to provide an approximation of energy and power calculation if no smart meter is available. 

The second part is dedicated to the management of DALI gateways and their devices. The Digital Addressable Lighting Interface (DALI) protocol is an application specific technology that is dedicated to lighting systems. Since it is a pure field level protocol without enhanced management features, it is integrated into other building automation technologies. The most important and most commonly used system for this integration purpose is KNX. So called KNX/DALI gateways are providing interfaces between the DALI devices and the KNX network. In addition to simply forwarding commands (e.g. on/off, dimming commands, ...) and information (e.g. on/off status, current brightness value), these KNX/DALI gateways provide sophisticated and enhanced functions. One of the most important feature is the testing of the functionality of the DALI devices.

However, the implementation of this function testing within the KNX/DALI gateways highly depends on the manufacturer of the gateway. Each vendor has its own way how function testing services are provided and how the test results are represented. This also concerns the mapping of this information to KNX communication objects. Even worse, most of the time a simple read and write to these KNX communication objects is not sufficient since a dedicated command sequence is necessary. A typical example is the reading of the fault status of a DALI device. First, the device has to be selected by sending the DALI number to a dedicated KNX group address and afterwards the fault status objects have to be read. This results in a complexity which is a major problem for system integrators and electrical engineers who have the task to provide such functionality.

To make the management of KNX/DALI gateways more easier, the NETx BMS Server is providing a dedicate module called LaMPS. The main goal of LaMPS is to provide a generic interface to initiate DALI tests independent of the used KNX/DALI gateway vendor. One of the most important functionality of KNX/DALI gateways is the possibility to monitor the fault state of DALI gateways and their DALI devices. This includes triggering of DALI device tests, the evaluation of test results and the monitoring of the fault states. Since each KNX/DALI gateway vendor are using their own KNX communication objects to provide this functionality, LaMPS provides an abstraction of these vendor-specific implementations. 

Currently, the following KNX/DALI gateways are supported:

  • ABB DG/S 1.1, DG/S x.64.1.1, DGN/S 1.16.1

  • EAE DA100, DA101

  • Gira/Insta DALI Gateway Plus REG 218000

  • Hager Dali gateway KNX TYA670D

  • Ipas DaliControl e64

  • Jung KNX DALI-Gateway Plus 2098 REGHE

  • MDT DaliControl IP Gateway SCN-DALI64.02

  • Merten KNX DALI-Gateway REG-K/1/16(64)/64/IP1 (MEG6725-0001)

  • Schneider KNX DALI-Gateway MTN6725-0001

  • Siemens KNX/DALI Gateway N 141/03, N 141/21, N 141/31

  • Siemens KNX/DALI Gateway N 141/02

  • Zennio DALIBOX Interface 64-32

 

Info

If you are using KNX/DALI gateways that are not yet supported, please contact us. Other DALI gateways from other manufacturers can be included on request.

Installation

LaMPS is provided for the NETx BMS Server as extension module. This means that it is not included within the setup per default. 

To install LaMPS, open the BMS Studio and shutdown the BMS Server. Afterwards, start the Extension Manager via the menu ("Extensions" --> "Manager" --> "Start Extension Manager ...").

Within the dialog, select "LaMPS" and press the "install" button. After having installed the LaMPS module, close the BMS studio and reopen it. Within the "Modules" menu of the BMS Studio you will find a new sub menu "LaMPS". It contains entries for all definitions that are necessary for configuration the LaMPS module.

Licensing

The LaMPS functionality is not included in a standard license for the NETx BMS Server. This means that an extra license has to be bought if the LaMPS module is required in your project. 

The price that has to be paid in addition to the normal fees of the BMS Server license of this extra fee is a fix amount which is independent of used amount of DALI gateways and DALI devices. In addition to this fix amount, 1 data point is counted for each DALI device that is used within the LaMPS module. These data points are subtracted from the total amount of available data points of your BMS Server license. For more information about the cost please contact our sales team.

The extra license itself is an option to the standard BMS Server licenses. This means the licensing process is exactly the same as for a normal BMS Server license. For a softlock license, the LaMPS option is encoded within your License ID and Unlock Code. For hardlock, the option is stored on your USB license dongle. 

Info

In order to test LaMPS, LaMPS is included within the demo license of the NETx BMS Server. This means that you can test the LaMPS module for 90 days for free.

Configuration

...

In the remainder of this section, the different definition files are explained in detail. 

...

Module configuration

Here common lighting circuits can be defined that shall be monitored by configuration settings for the NETx LaMPS Module .  

...

can be changed:

  • Function test timeout (s): timeout for DALI emergency function tests. If no test result is  received after this timeout is expired, the test fails. Default is 30 seconds.
  • Duration test timeout (s): timeout for DALI emergency duration tests. If no test result is  received after this timeout is expired, the test fails. Default is 10800 seconds (3 hours).
  • Partial during test timeout (s): timeout for DALI emergency partial duration tests. If no test result is  received after this timeout is expired, the test fails. Default is 10800 seconds (3 hours).
  • Battery test timeout (s): timeout for DALI emergency battery tests. If no test result is  received after this timeout is expired, the test fails. Default is 10800 seconds (3 hours).

Circuit definitions

Here common lighting circuits can be defined that shall be monitored by the NETx LaMPS Module.  

  • Name (string): name of circuit 
  • Path (string, optional, default: not used): alarm threshold for operating hours. If exceeded, the alarm alarm item will turn to true. The current threshold can also be changed during runtime via the corresponding item.Brightness ItemId  path used for structure within NETx BMS Server
  • OnOff ItemId (ItemID): ItemID that is used to turn on and off the circuit. If a separate status item is not used, this item also provides the status for calculating the operating hours
  • OnOff Status ItemId (ItemID, optional, default: not used): ItemID that can be used to change the brightness of a dimmable light. Brightness Status ItemId (ItemIDprovides the on/off status for this circuit. This status is also used for calculating the operating hours. If not used, the OnOff ItemID is used instead.
  • Operating Time Warning Threshold (number, optional, default: not used): ItemID that provides the current brightness value of a dimmable light.Brightness Scale Factor warning threshold for operating hours. If exceeded, the warning alarm item will turn to true. The current threshold can also be changed during runtime via the corresponding item.
  • Operating Time Alarm Threshold (number, optional, default: 1not used): scale factor for the brightness valueCurrent alarm threshold for operating hours. If exceeded, the alarm alarm item will turn to true. The current threshold can also be changed during runtime via the corresponding item.
  • Brightness ItemId (ItemID, optional, default: not used): if available the used current can be provided by this item.Current Scale Factor (numberItemID that can be used to change the brightness of a dimmable light. 
  • Brightness Status ItemId (ItemID, optional, default: 1): scale factor not used): ItemID that provides the current brightness value of a dimmable light.
  • Brightness Scale Factor (number, optional, default: 1): scale factor for the brightness value
  • Current ItemId (ItemID, optional, default: not used): if available the used current can be provided by this item.
  • Current Scale Factor (number, optional, default: 1): scale factor for the current. 
  • Current Lower Warning Threshold (number, optional, default: not used): here a lower warning threshold for monitoring the current can be specified. The current threshold can also be changed during runtime via the corresponding item.
  • Current Lower Alarm Threshold (number, optional, default: not used): here a lower alarm threshold for monitoring the current can be specified. The current threshold can also be changed during runtime via the corresponding item.
  • Current Higher Alarm Threshold (number, optional, default: not used): here a higher warning threshold for monitoring the current can be specified. The current threshold can also be changed during runtime via the corresponding item.
  • Current Higher Warning Threshold (number, optional, default: not used): here a higher alarm threshold for monitoring the current can be specified. The current threshold can also be changed during runtime via the corresponding item.
  • Voltage ItemId (ItemID, optional, default: not used): if availale the current voltage can be provided by this item.
  • Voltage Scale Factor (number, optional, default: 1): scale factor for the voltage.
  • Voltage Lower Warning Threshold (number, optional, default: not used): here a lower warning threshold for monitoring the voltage can be specified. The current threshold can also be changed during runtime via the corresponding item.
  • Voltage Lower Alarm Threshold (number, optional, default: not used): here a lower alarm threshold for monitoring the voltage can be specified. The current threshold can also be changed during runtime via the corresponding item.
  • Voltage Higher Warning Threshold (number, optional, default: not used): here a higher warning threshold for monitoring the voltage can be specified. The current threshold can also be changed during runtime via the corresponding item.
  • Voltage Higher Alarm Threshold (number, optional, default: not used): here a higher alarm threshold for monitoring the voltage can be specified. The current threshold can also be changed during runtime via the corresponding item.
  • Power ItemId (ItemID, optional, default: not used): if availabe the current power value can be provided by this item.
  • Power Scale Factor (number, optional, default: 1): scale factor for the power value.
  • Power Approximate (bool, optional, default: False): if enabled, an estimated power value based on the current and voltage is calculated. Note that this is calculation is only a rough estimation since the accuracy depends sending or polling interval of the current and voltage values.
  • Energy ItemId (ItemID, optional, default: not used): if availabe the current energy value can be provided by this item.
  • Energy Scale Factor (number, optional, default: 1): scale factor for the energy value.
  • Energy Approximate (bool, optional, default: False): if enabled, an estimated energy value based on the current and voltage is calculated. Note that this is calculation is only a rough estimation since the accuracy depends sending or polling interval of the current and voltage values.
  • Persistent (bool, optional, default: False): if set to true, all items are set to persistent i.e. the last values are restored after server startup.
  • Historical (bool, optional, default: False): if set to true, all values are stored within the historical database.
  • Redundant (bool, optional, default: True): if set to true, all items are synchronized with the backup server if available.

...

  • «common configuration options»
  • Fault Lamps (ItemId, KNX Object #19 or #1133, polled, mandatory): this communication object is true if there is a lamp error for at least 1 DALI device.
  • Fault Ballast (ItemId, KNX Object #20 or #1134, polled, mandatory): this communication object is true if there is a ballast error for at least 1 DALI device.
  • Fault DALI (ItemId, KNX Object #18 or #1132, polled, optional): this communication object is true if there is a general DALI error.
  • Fault addressed (ItemId, KNX Object #21 or #1135, mandatory): this communication object is used to trigger a normal DALI request and to get the test result.
  • Emergency Test Start (ItemId, KNX Object #40 or #1154, optional):  this communication object is used to trigger an emergency DALI test for a dedicated device.
  • Emergency Test Result (ItemId, KNX Object #42 or #1156, optional): this communication object is used to get the result of an emergency DALI test.
  • EmergencyTestTimeout (int, default 10000ms10s): specifies how long the driver will wait for an emergency test result, if the timeout expires the test will set to faultedbetween sending two emergency start requests.
  • «common configuration options»
Warning
 The group object "Emergency Test Start #40 or #1154) has to be configured for "Yes, DGN/S1.16.1 format" within ETS. Otherwise the emergency lighting tests will not work.


Info

The ABB DG/S x.64.1.1 gateway uses emergency test start and result objects for all devices on one changele – there are no individual objects for each emergency ballast as it is for other gateways. Therefore, there will appear no entry within the Emergency Mapping Definitions. If the emergency configuration is enabled it will appear within the ABB DG/S x.64.1.1 gateway definition.

ABB DGN/S 1.16.1

For each gateway the following configuration options are available:

  • «common configuration options»
  • Fault Lamps (ItemId, KNX Object #17, polled, mandatory): this communication object is true if there is a lamp error for at least 1 DALI device.
  • Fault Ballast (ItemId, KNX Object #18, polled, mandatory): this communication object is true if there is a ballast error for at least 1 DALI device.
  • Fault DALI (ItemId, KNX Object #19, polled, optional): this communication object is true if there is a general DALI error.
  • Diagnostics (ItemId, KNX Object #25, mandatory): this communication object is used to trigger a normal DALI request and to get the test result.
  • Emergency Test Start (ItemId, KNX Object #31, optional):  this communication object is used to trigger an emergency DALI test for a dedicated device.
  • Emergency Test Result (ItemId, KNX Object #33, optional): this communication object is used to get the result of an emergency DALI test.
  • Emergency Mode Active (ItemId, KNX Object #35, optional): if true, the DALI emergency lighting mode is active.
  • EmergencyTestTimeout (int, default 10000ms10s): specifies  specifies how long the driver will wait for an emergency test result, if the timeout expires the test will set to faulted«common between sending two emergency start requests.
  • «common configuration options»
Info

The ABB DGN/S 1.16.1 gateway uses emergency test start and result objects for all devices on one changele – there are no individual objects for each emergency ballast as it is for other gateways. Therefore, there will appear no entry within the Emergency Mapping Definitions. If the emergency configuration is enabled it will appear within the ABB DGN/S 1.16.1 gateway definition.

EAE DA 100

For each gateway the following configuration options are available:

  • «common configuration options»
  • Fault Lamp (ItemId, KNX Object #12, polled, mandatory): this communication object is true if there is a lamp error for at least 1 DALI device.
  • Fault Ballast (ItemId, KNX Object #13, polled, mandatory): this communication object is true if there is a ballast error for at least 1 DALI device.
  • Fault Converter (ItemId, KNX Object #14, polled, optional): this communication object is true if there is a converter error for at least 1 DALI device.
  • Fault gateway supply (ItemId, KNX Object #11,optional): this communication object is true if there is a general gateway supply error.
  • Fault mains connected supply (ItemId, KNX Object #16,optional): this communication object is true if there is a mains connected supply error.
  • Device Status (ItemId, KNX Object #3, mandatory): this communication object is used to trigger a normal DALI request and to get the test result.
  • Emergency Test Start (ItemId, KNX Object #4, optional):  this communication object is used to trigger an emergency DALI test.
  • EmergencyTestTimeout (int, default 10000ms10s): specifies  specifies how long the driver will wait for an emergency test result, if the timeout expires the test will set to faultedbetween sending two emergency start requests.
  • «common configuration options»

...

  • «common configuration options»
  • Fault Lamp (ItemId, KNX Object #14, polled, mandatory): this communication object is true if there is a lamp error for at least 1 DALI device.
  • Fault Ballast (ItemId, KNX Object #15, polled, mandatory): this communication object is true if there is a ballast error for at least 1 DALI device.
  • Fault Converter (ItemId, KNX Object #16, polled, optional): this communication object is true if there is a converter error for at least 1 DALI device.
  • Fault DALI (ItemId, KNX Object #12,optional): this communication object is true if there is a general DALI error.
  • Fault mains connected supply (ItemId, KNX Object #13,optional): this communication object is true if there is a mains connected supply error.
  • Device Status (ItemId, KNX Object #7, mandatory): this communication object is used to trigger a normal DALI request and to get the test result.
  • Emergency Test Start (ItemId, KNX Object #2, optional):  this communication object is used to trigger an emergency DALI test.
  • EmergencyTestTimeout (int, default 10000ms): specifies how long the driver will wait for an emergency test result, if the timeout expires the test will set to faulted
  • «common configuration options»

...

  • communication object is used to trigger a normal DALI request and to get the test result.
  • Emergency Test Start (ItemId, KNX Object #2, optional):  this communication object is used to trigger an emergency DALI test.
  • EmergencyTestTimeout (int, default 10s): specifies how long the driver will wait between sending two emergency start requests.
  • «common configuration options»

Gira/Insta DALI Gateway Plus REG 218000, Hager Dali gateway KNX TYA670D, Jung KNX DALI-Gateway Plus 2098 REGHE

For each gateway the following configuration options are available:

  • «common configuration options»
  • Fault General (ItemId, KNX Object #1524, polled, mandatory): this communication object is true if there is an error for at least 1 DALI device.
  • Fault Short Circuit (ItemId, KNX Object #1527, optional): true if there is a general short cut on the DALI bus
  • Fault Power Failure (ItemId, KNX Object #1525, optional): true if there is a power failure on the DALI bus
  • Emergency Mode Active (ItemId, KNX Object #1541, optional): true if DALI devices are in emergency mode.
  • Emergency Lighting Failure (ItemId, KNX Object #1542, polled, optional): true if there is an error for at least 1 emergency DALI device. This config element is optional. If it is not used, emergency lighting test features are not available.
  • Error per DALI Device (ItemId, KNX Object #1544, mandatory): KNX feedback object for DALI device errors
  • EmergencyTestTimeout (int, default 10s): specifies how long the driver will wait between sending two emergency start requests.
  • «common configuration options»

The objects Fault General (#1524) and Emergency Lighting Failure (#1542) can be configure as passive or active feedback objects. If at least one of them is set as passive, "Poll Device" should be set to true.

The objects Fault General (#1524) and Error per DALI Device (#1544) needs to be linked to a group address. Otherwise the dali gateway will be seen as "not used" and therefore be ignored for the export.

Since these gateways do not have a global KNX communication object for starting an emergency test and for getting the result (they have a separate object for each device), the ItemIDs has to be configured for each emergency lighting separately. This is done in the Emergency Test Mapping.

Ipas DaliControl e64, MDT DaliControl IP Gateway SCN-DALI64.02, Merten KNX DALI-Gateway REG-K/1/16(64)/64/IP1 (MEG6725-0001), Schneider KNX DALI-Gateway MTN6725-0001

For each gateway the following configuration options are available:

  • «common configuration options»
  • Fault General (ItemId, KNX Object #1524#8, polled polled, mandatory): this communication object is true if there is an error for at least 1 DALI device.
  • Fault Short Circuit DALI (ItemId, KNX Object #1527#9, optional): true if there is a general short cut on the DALI bus
  • Fault Power Failure Lamps (ItemId, KNX Object #1525#12, optional): true if there is a power failure on the DALI busEmergency Mode Active the amount of faulty devices with a lamps fault exceeds the configured threshold.
  • Fault Ballast (ItemId, KNX Object #1541#14, optional): true if DALI devices are in emergency mode.Emergency Lighting Failure the amount of faulty devices with a ballast fault exceeds the configured threshold.
  • Fault Converter (ItemId, KNX Object #1542, polled#16, optional optional): true if there is an error for at least 1 emergency DALI device. This config element is optional. If it is not used, emergency lighting test features are not available.Error per DALI Device the amount of faulty emergency lights with a converter fault exceeds the configured threshold.
  • Error Status Lamp/Ballast (ItemId, KNX Object #1544#20, mandatory): KNX feedback object for DALI device errorsEmergencyTestTimeout
  • EmergencyTestTimeout (int, default 10000ms10s): specifies  specifies how long the driver will wait for an emergency test result, if the timeout expires the test will set to faultedbetween sending two emergency start requests.
  • «common configuration options»

The objects Fault General (#1524) and Emergency Lighting Failure (#1542) can be configure as passive or active feedback objects. If at least one of them is set as passive, "Poll Device" should be set to true.

...


Info
 Since the communication objects #12, #14 and #16 are only getting true when a configured threshold is exceeded, it is of utmost importance to configure them correctly. In general, it is recommended to use a threshold of 1 in order to see all lamp faults.

 

Since these gateways do not have a global KNX communication object for starting an emergency test and for getting the result (they have a separate object for each device), the ItemIDs has to be configured for each emergency lighting separately. This is done in the Emergency Test Mapping.

...

in the Emergency Test Mapping.

Siemens KNX/DALI Gateway N 141/03, N 141/21, N 141/31

For each gateway the following configuration options are available:

...

  • «common configuration options»
  • Fault Power Failure (ItemId, KNX Object #12#34, optional): true if the amount of faulty devices with a lamps fault exceeds the configured threshold.
  • Fault Ballast Devices (ItemId, KNX Object #14, optional): true if the amount of faulty devices with a ballast fault exceeds the configured threshold.Fault Converter #30 or #32, polled, mandatory)
  • Fault Short Circuit (ItemId, KNX Object #16#31 or #33,  optional): true if the amount of faulty emergency lights with a converter fault exceeds the configured threshold.Error Status Lamp/Ballast optional)
  • Error Status (ItemId, KNX Object #20#37 or #736, mandatory)
  • EmergencyTestTimeout (int, default 10000ms10s): specifies  specifies how long the driver will wait for an emergency test result, if the timeout expires the test will set to faulted
  • «common configuration options»
Info
 Since the communication objects #12, #14 and #16 are only getting true when a configured threshold is exceeded, it is of utmost importance to configure them correctly. In general, it is recommended to use a threshold of 1 in order to see all lamp faults.

...

  • between sending two emergency start requests.
  • «common configuration options»

Since these gateways do not have a global KNX communication object for starting an emergency test and for getting the result (they have a separate object for each device), the ItemIDs has to be configured for each emergency lighting separately. This is done in the Emergency Test Mapping.

Siemens KNX/DALI Gateway N 141/

...

02

For each gateway the following configuration options are available:

  • «common configuration options»
  • Fault Power Failure (ItemId, KNX Object #34#6, optional)
  • Fault Devices (ItemId, KNX Object #30 or #32#5, polled, mandatory)
  • Fault Short Circuit (ItemId, KNX Object #31 or #33#7, optional)
  • Error Status (ItemId, KNX Object #37 or #736#11, mandatory)
  • EmergencyTestTimeout (int, default 10000ms10s): specifies  specifies how long the driver will wait for an emergency test result, if the timeout expires the test will set to faultedbetween sending two emergency start requests.
  • «common configuration options»

...