CON-ENOC Application Guide Edition 2.1 CON-ENOC Application Guide Edition 2.1

Document Title: CON-ENOC Application Guide

Current Edition: 2.1

Date of current revision: September 2016

No part of this manual may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language (natural or computer), in any form or by any means, without the prior written permission of Delta Controls Inc. Limited permission is granted to reproduce documents released in Adobe Portable Document Format (PDF) electronic format in paper format.

Documents released in PDF electronic format may be printed by end-users for their own use using a printer such as an inkjet or laser device. Authorized distributors of Delta Controls Inc. products (Delta Partners) may print PDF documents for their own internal use or for use by their customers. Authorized Delta Partners may engage a printing or copying company to produce copies of released PDF documents with the prior written permission of Delta Controls Inc.

Information in this document is subject to change without notice and does not represent a commitment to past versions of this document on the part of Delta Controls Inc. Delta Controls Inc. may make improvements and/or changes to this manual/the associated software/or associated hardware at any time.

enteliZONE, enteliBUS, enteliMESH, enteliTOUCH, BACstat, ORCA, ORCAview, Virtual Stat and ORCAweb are registered trademarks of Delta Controls Inc.

Windows is a registered trademark of Microsoft Corporation in the United States and/or other countries. All other trademarks are the property of their respective owners.

BACnet® is a registered trademark of American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE).

EnOcean ®, alliance logo, alliance member logo and ingredient logo are registered trademarks of EnOcean GmbH and EnOcean Alliance Inc.

Thermokon is a registered trademark of Thermokon Sensortechnik GmbH.

All other product or service names are the property of their respective owners.

CON-ENOC Application Guide Edition 2.1

Table of Contents Product Description ...... 1 Intended Application ...... 1 About EnOcean ...... 1 Related Documents ...... 2 Principles of Operation ...... 2 Components of an EnOcean Wireless Solution ...... 2 Number of Sensors, Outputs and Repeaters Supported ...... 3 Supported EnOcean-Technology based Devices ...... 3 Sensors ...... 3 Outputs ...... 3 Repeaters ...... 3 Wireless Signal Frequencies Used ...... 3 Energy Harvesting Technology ...... 4 Material Penetration Limitations and Signal Strength Capabilities ...... 4 Repeaters ...... 4 Installation Guidelines for the EnOcean Wireless Solution ...... 4 Installing the CON-ENOC ...... 4 Installing the Wireless Devices ...... 4 Performing a Site Survey ...... 5 Using the EPM 300 ...... 5 Using DolphinView Basic and USB 300 ...... 5 How to Integrate the EnOcean Wireless Solution ...... 6 Main Steps to Integrate the EnOcean Wireless Solution ...... 6 Step 1: Upgrading the Delta Controller with Customized Firmware ...... 6 Step 2: Installing the Customized Object Dialogs on OWS ...... 6 Saving the customized GWT dialog for Version 3.33 ...... 7 Saving the customized GWT and GW dialogs for Version 3.40 R1...... 7 Step 3: Connecting and Configuring the CON-ENOC...... 7 How to Add a Transmitter Device to the Wireless Network ...... 8 Step 4: Adding a Transmitter Device to the Wireless Network ...... 8 Role of the Gateway Translation object...... 8 Learn function ...... 9 Adding a device to the wireless network ...... 9 Step 5: Choosing How to Configure the GWT Object to Translate Device Data ...... 10 Available BACnet input objects and limitations ...... 10 Step 6: Configuring the GWT Object Obtained from the EnOcean Wireless Solution Page on George ...... 11 Creating the BACnet input objects ...... 11 Step 7: Configuring the GWT Object You Created ...... 11 About EnOcean Equipment Profiles ...... 11 About the GWT object translation programming fields for sensor data ...... 12 About GWT Functions for Translating Sensor Data ...... 14 About the GWT Reliability Timer setting...... 16 Configuring data translation and BACnet objects ...... 17 Removing a Device from the Wireless Network ...... 20

How to Add an Output or Receiver Device to the Wireless Network ...... 21 Output or Receiver Devices Supported by Delta Controls ...... 21 EchoFlex www.echoflexsolutions.com ...... 21 ILLUMRA www.illumra.com...... 21 Spartan Peripheral Devices www.spartan-pd.com ...... 21 BACnet Objects Supported ...... 21 About the GWT object translation programming fields for output data ...... 22 About GWT Functions for Translating Output Data ...... 23 Adding the EchoFlex ERM Load Controller Module ...... 24 Main steps in adding the EchoFlex ERM Load Controller Module ...... 24 Step 2: Joining the EchoFlex ERM to the wireless network ...... 25 Step 3: Configuring the binary object to command the load controller relay ...... 26 Step 4: Configuring the binary object to receive status from the load controller relay ...... 27 Removing the EchoFlex ERM from a wireless network ...... 27 Adding the ILLUMRA E3R Relay ...... 28 Main steps in adding the ILLUMRA E3R Relay ...... 28 Step 2: Joining the ILLUMRA E3R to the wireless network ...... 28 Step 3: Configuring the binary object to command the relay ...... 29 Removing the ILLUMRA E3R from a wireless network ...... 30 Adding the Spartan ME83xx Zone Valve Actuator ...... 31 Main steps in adding the Spartan ME83xx Zone Valve Actuator ...... 31 Step 2: Joining the Spartan ME83xx to the wireless network ...... 31 Step 3: Configuring the analog object to command and monitor the actuator position ...... 33 Removing the Spartan ME83xx from a wireless network ...... 34 Adding an Unlisted Output or Receiver Device ...... 34 Managing GWT Object Configurations ...... 35 Saving the GWT Object ...... 35 Loading the GWT Object ...... 35 Monitoring Sensor Performance and Reliability ...... 35 Monitoring the signal strength of a sensor ...... 35 Monitoring the reliability of the connection to a sensor ...... 36 Understanding the CON-ENOC LEDs ...... 36 Power LED ...... 36 Wireless Activity LED ...... 37 RS-485 Activity LED ...... 37 Managing Different Gateways on One Site ...... 37 Version 3.33 and Different Gateways on One Site ...... 37 Version 3.40 R1 and Different Gateways on One Site ...... 37 Troubleshooting ...... 38 Document Control ...... 39 Appendix A – EnOcean Wireless Systems Range Planning Guide ...... 40

ii CON-ENOC Application Guide Edition 2.1

Product Description

The CON-ENOC is a component of the Delta Controls EnOcean Wireless Solution which integrates EnOcean-technology based wireless devices from multiple vendors into the Delta Building Automation System.

The EnOcean Wireless Solution consists of a Delta controller, a Delta CON-ENOC RS-485-to-EnOcean zone gateway and EnOcean-technology based wireless devices.

Wireless device data enters the BACnet system via the CON- ENOC to a Delta controller. The controller translates the data and makes it available in BACnet objects.

Intended Application The primary application for the EnOcean Wireless Solution is data monitoring. Although it is not recommended for critical equipment control, the EnOcean Wireless Solution also supports a limited selection of wireless output devices.

The EnOcean Wireless Solution is ideal for zone level wireless installations. It allows you to add multiple types of sensor data to an existing Delta installation without having to run additional wire.

About EnOcean

EnOcean GmbH (www.enocean.com) is the originator of patented wireless technology that is self-powered by energy harvesting. EnOcean technology allows fast development and marketing of new wireless solutions in building services, industry and other sectors. Standardized device profiles make for interoperability of the resulting products. Devices from different manufacturers can then communicate and cooperate with one another in one and the same system.

“The EnOcean Alliance is a consortium of companies working to further develop and promote self-powered wireless monitoring and control systems for sustainable buildings by formalising the interoperable wireless standard. The EnOcean Alliance has the largest installed base of field-proven wireless building automation networks in the world.” from www.enocean-alliance.org/en/profile , February 2013.

EnOcean Alliance members and other companies create products that incorporate EnOcean technology.

Page 1 of 40

Related Documents

Find these documents on the EnOcean Wireless Solution page on George.

. CON-ENOC Installation Guide . EnOcean Range Planning Guide, Appendix A of this document . EnOcean Radio Approval . CON-ENOC Release Notes for related firmware

Principles of Operation

The EnOcean Wireless Solution allows you to add multiple types of sensor data from EnOcean-technology based devices to an existing Delta installation without having to run additional wire. The EnOcean Wireless Solution also allows you to add certain EnOcean-technology based output devices to an existing Delta installation.

Components of an EnOcean Wireless Solution

The EnOcean Wireless Solution consists of the following components:

. Delta enteliBUS, DSC or DAC controller, and enteliZONE controller (programmable only) running version 2.2 firmware

. Custom Delta Gateway object and Gateway Translation objects residing in the Delta controller

. Delta CON-ENOC zone gateway that converts an EnOcean wireless signal to EnOcean over RS-485. There are three CON-ENOC models: CON-ENOC-868 for 868 MHz, CON-ENOC-315 for 315 MHz and CON-ENOC-902 for 902 MHz

The 902 MHz frequency improves range and penetration of building material compared to 315 MHz. Although 902 MHz is recommended over 315 MHz, at the time of writing of this document 315 MHz products are more readily available than 902 MHz products. In the long term, 315 MHz products will be replaced by 902 MHz products. . EnOcean-technology based wireless devices. See Number of Sensors, Outputs and Repeaters Supported for limitations

The CON-ENOC zone gateway converts EnOcean wireless communications to EnOcean over RS-485. The Delta controller and the Gateway Translation objects translate data from the wireless devices and represent it as BACnet objects in the BACnet network. The Delta controller and Gateway Translation objects also translate control data from output objects in the BACnet network and send it to the wireless output devices via the CON- ENOC.

The key to implementing a reliable EnOcean Wireless Solution system is the proper placement of the CON-ENOC, its antenna and the wireless devices. Radio frequencies used by the EnOcean-technology based products enhance their ability to penetrate typical building materials, however, building environments also change over time so a device that communicates before the space is occupied may not communicate after it is occupied.

It is strongly recommended that you review the EnOcean Range Planning Guide and perform a site survey prior to installing an EnOcean Wireless Solution.

Page 2 of 40 CON-ENOC Application Guide Edition 2.1

Delta DSC or DAC controllers with 4Mbit of memory don’t support the EnOcean Wireless Solution. See KBA 1579 for details about controller hardware versions and memory capacity.

Number of Sensors, Outputs and Repeaters Supported

The EnOcean Wireless Solution supports a limited number of EnOcean-technology based sensor and output devices per one CON-ENOC. Sensor devices are also referred to as transmitters and output devices are also referred to as receivers.

The following rules describe the limitations for the number of sensors, outputs and repeaters that are supported:

. Up to 32 devices can be joined to one CON-ENOC in any combination of sensor devices and output devices

. A sensor device with multiple sensors counts as one sensor device

. A sensor that is wired to an output device is not counted.

. A repeater between the CON-ENOC and a sensor or output device is not counted

Supported EnOcean-Technology based Devices The EnOcean Wireless Solution with the CON-ENOC is designed to work with any EnOcean-technology based device that is on the market. However, to provide a reliable and easy-to-implement solution, Delta Controls has focused our development and testing on products from the following manufacturers.

Sensors

. Echoflex – www.echoflexsolutions.com

. Thermokon – www.thermokon.de/EN/thermokon-sensortechnik-14/start.html

Outputs

. Echoflex – www.echoflexsolutions.com

. ILLUMRA – www.illumra.com

. Spartan Peripheral Devices – www.spartan-pd.com

See Output or Receiver Devices Supported by Delta Controls for a list of output devices that are supported.

Repeaters

. Echoflex – www.echoflexsolutions.com

Wireless Signal Frequencies Used

The EnOcean wireless signal uses the 315 MHz, 868 MHz and 902 MHz frequency bands which makes it suitable for worldwide use. Devices with 315 MHz or 902 MHz frequency are suitable for North America and other countries adopting the FCC specification. Devices with 868 MHz frequency are suitable for Europe and other countries adopting the R&TTE specification.

Review the EnOcean Radio Approval document before ordering any product. Certain countries have different approvals for the wireless radios in the product. In some cases local approval onsite may be required.

Page 3 of 40

These frequencies allow for better penetration through construction materials that are commonly found in most buildings, enabling greater distances while using less power. Further, wireless transmissions are brief and the packets are compact. Packets are transmitted in random intervals that reduce the probability of data collisions and therefore increase reliability.

Even with lower power consumption than conventional wireless systems, EnOcean-technology based devices communicate up to 30m inside buildings and up to 300m in the open. Each device comes with a unique 32-bit identification number to prevent any possibility of conflict with other devices.

Energy Harvesting Technology Instead of batteries, most EnOcean technology-based devices use miniaturized energy converters to supply their power. Using a technique known as energy harvesting, these devices receive power from their environment and therefore reduce the need for maintenance. Energy harvesting is implemented in the form of motion converters, solar cells and thermo converters. In some cases these power sources may not be sufficient and a battery can be used to supplement power.

Material Penetration Limitations and Signal Strength Capabilities EnOcean wireless signals can go through many materials with varying degrees of penetration.

The EnOcean wireless signal range varies depending on the materials the signal has to penetrate.

The Range Planning Guide, published by EnOcean, describes material penetration and signal range issues in detail. This document is available in Appendix A or from the EnOcean Wireless Solution page on George.

Repeaters In case of low wireless signal strength, it may be helpful to use a repeater. EnOcean repeaters do not require configuration and can be put into operation by connecting them to a power source. See the EnOcean Range Planning Guide in Appendix A of this document for details about repeaters. Delta recommends using the Echoflex ERM as a repeater.

Installation Guidelines for the EnOcean Wireless Solution

Where you locate and install the CON-ENOC and the wireless devices is important for a successful wireless network installation. Various site conditions such as building materials and floor layout can add complexity and decrease reliability.

Installing the CON-ENOC See the CON-ENOC Installation Guide on the EnOcean Wireless Solution page on George for a detailed description of how to install the CON-ENOC.

Installing the Wireless Devices

See Appendix A: EnOcean Wireless Systems Range Planning Guide which describes how to choose the best location for the CON-ENOC and the wireless devices. In this document, the term radio gateway means the CON- ENOC.

Page 4 of 40 CON-ENOC Application Guide Edition 2.1

Performing a Site Survey

A site survey is strongly recommended for every EnOcean Wireless Solution installation. A site survey is the process of planning and designing the wireless system so that it provides the required coverage and reliability.

The site survey usually involves an inspection of the facility to identify the locations of both the devices and the CON-ENOC. During the visit, site survey tools are used to test for signal strength at the locations and to identify sources of interference. As well, the building floor plans are analyzed to identify the effective range boundary within which the signal levels must be maintained.

Using the EPM 300 The EPM is a mobile field intensity meter that enables the installer to determine the ideal mounting positions for sensors, receivers and repeaters. Furthermore, faulty connections of devices already installed can be checked. The EPM 300 meter displays the field intensities of radio telegrams received and any interfering radio signals in the 868 MHz range, the EPM 300C in the 315 MHz range.

Even after careful site planning, the EPM field intensity meter should be used to verify proper reception at the receiver position during installation.

Use a Thermokon EPM 300 or EPM 300C field strength meter and a wireless light switch to perform a site survey.

Before you begin, review Appendix A: EnOcean Wireless Systems Range Planning Guide and the EPM300 data sheet.

To use the EPM300, position it where you intend to install the CON-ENOC. Take the wireless light switch to each location where you intend to install an EnOcean technology-based device and press the light switch. The signal strength is displayed on the EPM300. Make sure to test with the light switch positioned in the final installation location and place it flat on the wall or installation location to take all interference into account.

The EPM300 can be used in several ways.

. Hold Short – use with two people performing the site survey: one person is positioned at the EPM300, the other with the light switch. When the light switch is pressed, the signal strength is displayed immediately on the EPM300 for a few seconds.

. Hold Long – use with one person performing the site survey. When the light switch is pressed the signal strength is displayed immediately on the EPM300 and remains displayed for one minute. One minute provides enough time for the person to press the light switch and then to travel back to where the EPM300 is located.

. Repeater – use two EPM300s to find the best position for a repeater. EPM 300 #1 is used as the repeater and EPM300 #2 is used to monitor the signal at the receiver position.

. Radio Link Test – use with a second EPM300 with one person performing the site survey. The radio link will send a signal every two seconds and the second EPM300 receives the signal at the same rate.

Using DolphinView Basic and USB 300 EnOcean DolphinView Basic is a Windows-based software tool that visualizes and interprets EnOcean radio telegrams. It receives messages via a USB 300 device, displays telegram content and interprets EnOcean Equipment Profiles (EEP).

The USB 300 provides a bidirectional EnOcean radio and bidirectional USB interface to the world of EnOcean- technology based wireless products.

Page 5 of 40

With DolphinView, you can view a node list of the wireless devices and their radio signal strength level (dBm) as displayed by a signal bar and color.

The Telegram Log module is used for logging all EnOcean radio and serial telegrams. It offers basic analysis of a telegram via listing of all necessary information of the telegram such as time stamp, TYP, RORG/SORG, DATA, ID, RSSI, number of Sub-telegrams etc. The information is also logged to a XML file. The Telegram Log feature is useful for capturing and retaining a record of site performance at a particular date and time.

How to Integrate the EnOcean Wireless Solution

The EnOcean Wireless Solution is integrated into a building automation system via an enteliBUS, DSC or DAC controller, or an enteliZONE programmable controller running version 2.2 firmware. The DCU and enteliTOUCH don’t support EnOcean Wireless Solution integration.

Main Steps to Integrate the EnOcean Wireless Solution

To integrate the EnOcean Wireless Solution into a Delta building automation system, follow these main steps. Each step is detailed in sections titled Step1 ..., Step 2... and so on.

1. Upgrade the Delta controller with customized firmware that supports the EnOcean Wireless Solution. 2. Install the customized Gateway (GW) and Gateway Translation (GWT) object dialogs on the ORCAview workstation, depending on OWS version you are using. 3. Connect the CON-ENOC to the Delta controller via the RS-485 communications link and configure it using the GW object. 4. Add EnOcean-technology based devices to wireless network using GWT objects. 5. Configure the GWT object to translate data in the device’s telegram payload message. 6. Configure BACnet objects corresponding to the device data.

Step 1: Upgrading the Delta Controller with Customized Firmware Customized firmware is required to enable EnOcean Wireless Solution integration. See the EnOcean Wireless Solution page on George for this firmware.

To upgrade the controller firmware, use Flash Loader or System Loader.

When the firmware upgrade is completed, reset the controller to ensure that database contains the EnOcean Interface Gateway (GW1) object.

When you want to remove the customized controller firmware and revert to the standard firmware in the controller, contact Delta Technical Support for assistance.

Step 2: Installing the Customized Object Dialogs on OWS In ORCAview version 3.33 you need to install the customized Gateway Translation (GWT) object dialog.

In ORCAview version 3.40 R1, you need to install both the customized Gateway (GW) object and the Gateway Translation (GWT) object dialogs.

In ORCAview version 3.40 R2 and higher, the customized Gateway (GW) object and the Gateway Translation (GWT) object dialogs are installed by the Version 3.40 R2 and higher installer and, therefore, do not need to be installed separately.

Page 6 of 40 CON-ENOC Application Guide Edition 2.1

For Version 3.33 and Version 3.40 R1, you download the customized object dialogs from the EnOcean Wireless Solution page on George.

After the required customized dialog(s) has been downloaded and saved as described in following sections, restart ORCAview for the changes to take effect.

Saving the customized GWT dialog for Version 3.33 For Version 3.33 the dialog is saved to: C:\Program Files\Delta Controls\3.33\Dialogs\Vendor8\DAC

You may need to rename the dialog file; the required name after download is vn8dacv3gwt.dlg

Saving the customized GWT and GW dialogs for Version 3.40 R1 For Version 3.40 R1 the two dialogs are saved to:

. Windows 8/7/Vista – C:\Users\Public\Delta Controls\3.40\Dialogs\Vendor8\DAC

. Windows XP – C:\Documents and Settings\Public\Delta Controls\3.40\Dialogs\Vendor8\DAC

You may need to rename the dialog files. The required names after download are VN8dacv3gwt.dlg and VN8dacv3gw.dlg

Step 3: Connecting and Configuring the CON-ENOC

The CON-ENOC is wired to a Delta controller via RS485 cabling. See the EnOcean Wireless Solution Installation Guide for more information about this connection.

If NET1 is the only main communication port on the controller (for example on the enteliZONE controller), connect the CON-ENOC on NET2.

To configure the CON-ENOC: 1. After the CON-ENOC is connected to the controller and power is applied to it, reset the controller. 2. From ORCAview, open the EnOcean Interface3 (GW1) object and select the Setup tab. In the Setup section, make sure the Enable box is checked. In the Port Settings section set Port to the port that the CON-ENOC is connected to. The default is NET2. Reset the device after saving the GW1 settings if you choose to use NET1.

Page 7 of 40

3. Ensure that the Speed setting is set to 38,400 in the GW1 object to match the CON-ENOC. Click Apply. 4. To verify that the CON-ENOC is communicating to the controller, press a wireless switch that has the same frequency as the CON-ENOC. The switch does not need to be joined to the wireless network, however, you should position it within a few meters of the CON-ENOC. Select the Statistics tab and observe that the Total Received value increments as you press the wireless switch to indicate that proper communications is established. Ignore the dialog Header area when confirming communications with the CON-ENOC. In the Version 3.33 GW1 object dialog, you may see No Data Received; this is not relevant. 5. Click OK.

How to Add a Transmitter Device to the Wireless Network

A transmitter device is an EnOcean-technology based device, such as a temperature sensor, contact sensor or switch that sends or transmits information to the Delta controller via the CON-ENOC.

To add a receiver device such as an actuator or relay to the wireless network, see How to Add a Receiver Device to the Wireless Network.

Step 4: Adding a Transmitter Device to the Wireless Network

Before you can add a transmitter device to the wireless network, sometimes referred to as joining the device to the network, you need to know the device’s globally-unique factory-assigned address. The device address can be obtained in either of the two ways that are described later in this section in Adding a device to the wireless network .

Role of the Gateway Translation object The EnOcean Wireless Solution uses a custom Gateway Translation (GWT) object to represent an EnOcean- technology based device. One GWT object represents one device. Up to 32 GWT objects and therefore 32 devices can be created per CON-ENOC. Any combination of transmitter and receiver devices is supported.

A GWT object represents all the data elements that are available from one wireless transmitter device. For example, a transmitter device could send the following information:

. Temperature

. Setpoint

. Push button

The GWT object in this case contains three entries, one for each data element. Three corresponding BACnet objects are created in the Delta controller to represent the data elements.

The enteliZONE programmable controller running version 2.2 firmware supports up to 4 GWT objects per controller.

Page 8 of 40 CON-ENOC Application Guide Edition 2.1

Learn function Most devices have a Learn function which causes the device to transmit identification and EEP data to the CON-ENOC. The GW object dialog displays the information on its Description tab.

Most devices use a learn button that is located somewhere on the device. Sometimes this button is referred to as a Teach button. Other devices such as a light switches use a combination of switch presses to transmit identification and EEP data.

The GW object dialog doesn’t display the device information when the device has been added or joined to the network and a GWT object for the device exists.

Adding a device to the wireless network To add or join a transmitter device to wireless network: 1. If needed, create a Gateway Translation (GWT) object to represent the device. There are two methods for creating the GWT object, described below as method A and method B: A. Obtain the GWT object from the EnOcean Wireless Solution page on George and load it into the Delta controller. Using GWT objects from George is the recommended approach. These objects are configured by Delta for the data elements available from the device. B. Use ORCAview to create a GWT object to represent the device. This option is not available for the enteliZONE controllers. 2. Open the GWT object dialog and select the Setup tab. 3. Select Sensor from the Command Link list. 4. Click Apply. After a few seconds delay, Link Status displays Link Pending. 5. Press and release the learn button on the device. You have approximately five minutes to do this before the GWT object times out. 6. After a few seconds delay, the device address is displayed in the Name column of the first row. Link Status displays Link Active and Reliability displays Connected, as shown in the following screen capture.

Page 9 of 40

7. For a device that transmits a heartbeat message periodically, set Reliability Timer to the manufacturer’s recommended interval plus 5-10%. For a device such as a switch or contact that doesn’t heartbeat and transmits a message only when it detects a state change, set Reliability Timer to 0 seconds. Click Apply. 8. Click OK to save and close.

Step 5: Choosing How to Configure the GWT Object to Translate Device Data EnOcean-technology based transmitter devices transmit messages called telegrams containing various types of encoded information. The GWT object dialog includes multiple fields that you use to program it to translate the device data you are interested in and to expose the translated data through a BACnet input object.

There are two methods for configuring the GWT object to translate the device data: the recommended method and the basic method:

. Recommended method: After completing Step 4, because you obtained the GWT object from the EnOcean Wireless Solution page on George, the GWT object is ready-to-use and is configured to translate the device data. All you need to do is to map the data to BACnet input objects. Go to Step 6.

. Basic method: After completing Step 4, because you created the GWT object yourself, you therefore need to add the translation programming and then map the data to BACnet input objects. Go to Step 7

Available BACnet input objects and limitations A data element is represented by a BACnet input object as either a hardware point such as analog or binary input, or as a software point such analog, binary or multi-state variable. The data representation depends on which version of ORCAview and firmware you are using.

For Version 3.33 firmware the following BACnet input object types are supported:

. Analog Variable (AV) object

. Binary Variable (BV) object

. Multi-state Variable (MV) object

For Version 3.40 firmware the following BACnet input object types are supported:

. Analog Input (AI) object

. Analog Variable (AV) object

. Binary Input (BI) object

. Binary Variable (BV) object

. Multi-state Variable (MV) object

In Version 3.40 there are limitations on analog and binary input objects:

. 250 analog and binary input object instances are allowed. This limitation is typically not a problem even when the maximum of 32 GWT input objects per controller is used.

. Input object instance number range is restricted to 15001 to 15250 on a DSC or DAC controller. Use each instance number once only on a given controller.

Page 10 of 40 CON-ENOC Application Guide Edition 2.1

Step 6: Configuring the GWT Object Obtained from the EnOcean Wireless Solution Page on George No configuration is required; the translation programming is done for you in the GWT object. To verify that you selected the correct GWT object from George, observe that the GWT object dialog Value field changes as you manipulate the device. To understand in detail how the translation is implemented, review the section Step 7: Configuring the GWT object you created.

Now you need to specify and create the BACnet object that represents the data, as described in the following procedure.

Creating the BACnet input objects To create the BACnet input objects: 1. Open the GWT object dialog. Enter the input object reference in each row of the Reference column: See About the GWT object translation programming fields for sensor data for a description of the formats you must use when entering the reference. 2. Click Create BACnet Objects and then click Apply. The referenced objects are created and displayed in Navigator. The full name for the object is created by the GWT object when the object is created. The full name comprises the GWT object name, an underscore character, and the name in the Name column of the command packet row. For enteliZONE controllers, if the full name exceeds 36 characters in length, the name will be truncated by removing the extra characters at the end of the name. 3. Review the Description tab for possible errors when creating the BACnet objects. . The object name is greater than 67 characters.

. The object instance number is not in the specified range.

Step 7: Configuring the GWT Object You Created

Before you can start on the GWT configuration using the basic method, you need to understand how to translate the data contained in the EnOcean telegram data payload sent by the device.

About EnOcean Equipment Profiles The EnOcean Equipment Profiles (EEP) document found on the EnOcean Wireless Solution page on George specifies the profiles that EnOcean-technology based devices must conform to. In theory, conforming devices from different manufacturers can be integrated in a wireless network; in practice, the profiles leave room for interpretation which can result in differences between devices that conform to the same profile.

Each profile defines three profile elements:

. RORG – Radio ORG = identifier for telegram types (new with EEP Version 2.1) or ORG – identifier for telegram types (superseded by RORG in EEP Version 2.1)

. Function – Basic function of the data content, for example temperature sensor

. Type – Device characteristics, for example Temperature Sensor Range +10 deg C to +50 deg C

As specified by the profile’s RORG element, a device’s telegram data payload is formatted in a standard format referred to by acronyms such as RPS, 1BS, 4BS VLD and so on.

Page 11 of 40

For example, the 4BS format defines a four bytes payload arranged in the telegram and labeled as: DB_3, DB_2, DB_1, DB_0 (or as Data_byte3, Data_byte2, Data_byte1, Data_byte0), and the 1BS format defines a one byte payload labeled as DB_3 or as Data_byte3.

Typically, the manufacturer’s specification that comes with the device specifies its telegram format. For example, the Thermokon SRW01 door and window contact specification states:

The Thermokon SR06/07 room sensor uses telegram data payload type 4BS, as shown in the example specification below:

About the GWT object translation programming fields for sensor data The GWT object dialog provides several fields that you use to program the GWT to translate the device data before it is supplied to a BACnet input object. The fields are arranged in tabular form with multiple rows. The column headings and role in the translation are:

Name – Type the name you want for this data element. This field has a limit of 12 characters. The full name of the object is created in the form: GWT object name_GWT Name column text.

Reference – Specifies the object reference for the input object that receives the sensor data.

Reference for DSC and DAC controllers

AI and BI object reference convention: Enter the complete input object reference, such as BI15001. The object reference must be in the range 15001 to 15250. AI and BI objects are not supported for V3.33 firmware.

AV, BV or MV object reference convention: Enter the object reference in the abbreviated form of TTnn where TT is the object type AV, BV or MV and nn is the object reference number. Allow the GWT object to determine the complete object reference.

When the GWT object creates the input object, it expands the abbreviated object reference to its complete form of TT1GGnn where TT is the object type AV, BV or MV, GG is the GWT object reference and nn is the object reference. For example, AV2 created by GWT1 becomes AV10102.

Page 12 of 40 CON-ENOC Application Guide Edition 2.1

Reference for enteliBUS controllers

Enter the object reference in the abbreviated form of TTnn where TT is the object type AI, BI, AV, BV or MV and nn is the object reference number in the range 1 to 99. When more than two digits are entered, only the two least significant digits are retained. For example, AV2 or MV42. An object reference of 0 is not valid and will cause an error message in the Description field.

When the GWT object creates an input object, it expands the object reference to its complete form of TT14GG0nn when the controller is connected to Net1 and of TT15GG0nn when the controller is connected to Net2, where TT is the input object type AI, BI, AV, BV or MV, GG is the GWT object reference number and 0nn is the input object reference. For example, AV2 on Net1 and created by GWT1 becomes AV1401002.

DataByte – indicates which of the four bytes in the telegram data payload contains the data element you want to translate. Enter as 0, 1, 2, or 3. When there is more than one data element of interest such as temperature and setpoint as in Thermokon SR06/07 room sensor, use a separate row for each element.

Bit(s) – Further defines the format for a specific data element by masking out bits. For example, a window contact uses one bit in a data byte. Bit position is specified by entering 1 for the least significant bit, 128 for the most significant bit, and up to 255 for all eight bits. Leaving the Bit(s) blank or 0 also uses all 8 bits (common practice). Leave this field blank for analog values such as temperature which uses all eight bits.

When Function is set to 5, 6 or 7, then you can set Bit(s) to 128 to have the value in Parm1 be interpreted as a negative number. For example, when Bit(s) = 128 and Parm1 = 20, Parm1 is interpreted as -20.

Parm1 – provides parameter to the translation function. For example, when the data element is a temperature and you are associating the data element with an AV object, Parm1 sets the temperature value assigned to the low end of the sensor’s temperature range. The GWT object scales its value based on Parm1 and Parm2. However, if you are associating the data element with an AI object, set Parm1 and Parm2 to zero and use an AIC object to scale the value.

Parm2 – provides parameter to the translation function. For example, when the data element is a temperature and you are associating the data element with an AV object, Parm2 sets the temperature value assigned to the high end of the sensor’s temperature range.

Shifter –When a bit is defined in the data element the shifter can be used to move the specific bit along the data byte. For example you can enter 8 which bit masks bit 4. But if you shift it by 4 then bit 4 becomes bit 1. It is preferred to put the number in the data element directly because it’s easier to understand.

Function – specifies the GWT built-in data translation function to use, as described in the following section and Table 1.

Value – Displays the data element value supplied to the referenced BACnet object. That is, the data element value after the translation specified by Function, Parm1, Parm2, Bit(s) and Shifter is applied to the raw data element value transmitted from the device.

Reference for enteliZONE controllers

AI, BI, AV, BV or MV object reference convention: Enter the object reference in the abbreviated form of TTnn where TT is the object type AI, BI, AV, BV or MV and nn is the object reference number. Allow the GWT object to determine the complete object reference.

Page 13 of 40

When the GWT object creates the input object, it expands the abbreviated object reference to its complete form of TT1GGnn where TT is the object type AI, BI, AV, BV or MV, GG is the GWT object reference and nn is the object reference. For example, AV2 created by GWT1 becomes AV10102.

About GWT Functions for Translating Sensor Data To simplify the translation of data from EnOcean-technology based devices, Delta implemented functions in the GWT object to translate common device data element types. You enter the function number in the GWT object dialog Function column.

Table 1 GWT Object Functions for Translating Sensor Data

Function Description Application

0 Convert device value to Use this function with Analog Input objects. The device sends its Delta A to D value. value as 0-255 and the GWT object translates it to the Delta standard A to D range of 0-4095.

1 Pass device value Device sends its value as 0-255. The GWT object passes same value through to BACnet to BACnet object. Use this function in conjunction with an AV object. object. This function is also used when bit masking is required to isolate a specific bit from a data element. Can be used for digital devices.

2 Event based devices, Use data after Bit(s) mask and Shifter applied – generate update such as light switches event P1 = ON event P2 = OFF event

Uses Parm1 and Parm2 to define the events. This function can be used with light switches which define the ON, OFF and ON HOLD and OFF HOLD events. This is advanced functionality as there are other functions such as Functions 12-17 that do this directly.

3 Invert the first bit Use this function for digital inputs. Once the mask is applied (this determines which bit is being looked at) the value is inverted. This function can also be done on the BACnet object directly.

4 Fan Speed Based on a profile specification for multi-speed fan control similar

to: Translated values are Stage0=1, Stage1=2, Stage2=3, Stage3=4 and Auto=5. This data is typically represented by a MV object.

Page 14 of 40 CON-ENOC Application Guide Edition 2.1

Function Description Application

5 Linear, direct, 0-255 Direct acting, Parm1 sets the 0 value and Parm2 sets the 255 value. Use this function instead of a scale range in the controller, typically for temperature setpoint input.

Set Bit(s) to 128 to have the value in Parm1 be interpreted as a negative number.

6 Linear, reverse, 255-0 Reverse acting, function reverses value and then applies Parm1 and Parm2 to implement scale range. Parm1 sets the 255 value and Parm2 sets the 0 value. Use this function instead of a scale range in the controller, typically for temperature sensor input.

Set Bit(s) to 128 to have the value in Parm1 be interpreted as a negative number.

7 Linear, direct, 0-250 Direct acting, use Parm1 as the start value and Parm2 as the end value. Use this function instead of a scale range in the controller for devices have a scale range of 0-250.

Set Bit(s) to 128 to have the value in Parm1 be interpreted as a negative number.

8 - 11 Not used

12 Switch A On/Off Lighting control

13 Switch A Hold Up Blind control or dimming

14 Switch A Hold Down Blind control or dimming

15 Switch B On/Off Lighting control

16 Switch B Hold Up Blind control or dimming

17 Switch B Hold Down Blind control or dimming

18 RSSI Display the Received Signal Strength Indicator (RSSI) of the device. RSSI is a measurement of the power, in dBm, that is present in a received radio signal.

Page 15 of 40

About the GWT Reliability Timer setting The Reliability Timer setting informs the GWT object how often it should expect a telegram from the device. When the GWT object receives a telegram, it sets its Reliability status to Connected and resets the timer. When the GWT object doesn’t receive a telegram within the time interval, it sets its Reliability status to Not Connected.

By design, EnOcean-technology based devices are frugal users of energy and therefore transmit telegrams only when necessary. For devices that support a periodic heartbeat telegram, the device manufacturer specifies the transmission period or sending interval that you can use as a basis for its Reliability Timer setting. It is recommended that you add 5 – 10% to this value to allow for variations among devices.

Some devices include hardware jumpers that allow you to choose from several sending interval settings.

When the device doesn’t support a heartbeat telegram, set Reliability Timer to zero. Typically, switches and output devices don’t transmit packets regularly or support a heartbeat telegram.

Here are some example specifications and recommended Reliability Timer setting:

Thermokon SR07 Room Sensor Reliability Timer

The heartbeat is 1000 seconds, therefore set Reliability Timer to 1050 seconds.

EchoFlex MT-17 Temperature Sensor Reliability Timer

The heartbeat is 120 seconds, therefore set Reliability Timer to 130 seconds.

Thermokon SRW01 Contact Reliability Timer

The heartbeat is 30 minutes, therefore set Reliability Timer to 1900 seconds.

Page 16 of 40 CON-ENOC Application Guide Edition 2.1

Configuring data translation and BACnet objects This section describes how to program the GWT objects that you created to translate the data elements for two example devices: a contact sensor and a room sensor, and how to assign a BACnet object for each data element. It is assumed that you followed the procedure in Step 4: Adding a device to the wireless network to create the GWT object and to add the device address to it.

Example 1: configuring the Thermokon SRW01 door and window contact

To configure a GWT object for the Thermokon SRW01: 1. Open the GWT object dialog. In a row under the device address in the Name column, enter the name you want for the data element that is being represented by this row. The full name for the binary object is created by the GWT object when the binary object is created. The full name comprises the GWT object name, an underscore character, and the name you enter in the Name column of the command packet row. For example, when the GWT object name is Rm101 Window and you enter Contact in the Name field, then the full name given to the binary object is Rm101 Window_Contact. 2. In the Reference column in the same row, enter the object reference. See About the GWT object translation programming fields for sensor data for a description of the formats you must use when entering the reference.

3. In the DataByte column in the same row, enter 3. The manufacturer specified Data_byte3.

4. In the Bit(s) column in the same row, enter 1 to indicate that the contact state is in bit 0 of Data_byte3 as specified by the manufacturer.

5. In the Function column in the same row, enter 1 to retain the original Data_byte3 device value

6. Click Apply to save configuration.

7. Click Create BACnet Objects then click Apply to create the BACnet object.

8. Observe in Navigator that the BI/BV object is created. When you open and close the contact, the BI/BV object value changes between ON and OFF. The GWT object Value field changes between 0 and 1. The GWT configuration is shown below:

Page 17 of 40

Example 2: configuring the Thermokon SR06/07 room temp and setpoint

To configure a GWT object for the Thermokon SR06/07: 1. Open the GWT object dialog. In the row under the device address in the Name column, enter the name you want for the room temperature data element represented by this row. The full name for the analog object is created by the GWT object when it creates the analog object. The full name comprises the GWT object name, an underscore character, and the name you enter in the Name column of the command packet row. For example, when the GWT object name is Room101Stat and you enter Temperature in the Name field, then the full name given to the analog object is Room101Stat _Temperature. 2. In the Reference column in the same row, enter the object reference. See About the GWT object translation programming fields for sensor data for a description of the formats you must use when entering the reference. 3. In the DataByte column in the same row, enter 1 for the temperature data element. The manufacturer specified Data_byte1.

4. In the Bit(s) column in the same row, enter 0 to indicate that the temperature value uses all eight bits, as specified by the manufacturer.

5. In the Parm1 and Parm2 columns in the same row:

Leave Parm1 and Parm2 set to 0 when you are using an AI object because you will use an AIC object to set the scale range. Enter 0 for Parm1 and 40 for Parm2 to implement scale range in degrees Centigrade as specified by the manufacturer or 32 for Parm1 and 140 for Parm2 to implement scale range in degrees Fahrenheit when you are using an AV object. If Parm1 needs to be a negative number, set Bit(s) to 128. 6. In the Function column in the same row:

Enter 0 when you are using AIC object to convert the value to the A to D range that the AI object expects Enter 6 when you are using an AV object to allow the GWT object to implement the scale range using Parm1 and Parm2. 7. Click Apply to save configuration.

8. Click Create BACnet Objects. Click Apply to create the BACnet object.

9. Observe that the AI/AV object is created and that its name and object reference have been converted to a valid EnOcean Wireless Solution object name and reference number.

Page 18 of 40 CON-ENOC Application Guide Edition 2.1

10. When you are using an AV object, change its units to degrees C or degrees F; when you are using an AIC object, set its scale range accordingly.

11. In the row under the room temperature settings, in the Name column, enter the name you want for the setpoint data element represented by this row, such as SetpointAdjust.

12. In the Reference column in the same row, enter the object reference. See About the GWT object translation programming fields for sensor data for a description of the formats you must use when entering the reference. 13. In the DataByte column in the same row, enter 2 for the setpoint data element. The manufacturer specified Data_byte2.

14. In the Bit(s) column in the same row, enter 0 to indicate that the setpoint value uses all eight bits, as specified by the manufacturer.

15. In the Parm1 and Parm2 columns in the same row: When you are using an AI object, leave Parm1 and Parm2 set to 0 because you will use an AIC object to set the scale range. When you are using an AV object, you enter, for example, 18 for Parm1 and 22 for Parm2 to implement scale range in degrees Centigrade or 67 for Parm1 and 73 for Parm2 to implement scale range in degrees Fahrenheit 16. In the Function column in the same row:

Enter 0 when you are using AIC object to convert the value to the A to D range that the AI object expects. Enter 5 when you are using an AV object to allow the GWT object to implement the scale range using Parm1 and Parm2. 17. Click Apply to save configuration.

18. Click Create BACnet Objects then click Apply to create the BACnet object.

19. Observe that the AI/AV object is created and that its name and object reference have been converted to a valid EnOcean Wireless Solution object name and reference number.

20. When you are using an AV object, change its units to degrees C or degrees F; when you are using an AIC object, set its scale range accordingly.

Page 19 of 40

21. When you vary the room temperature or the setpoint, the BACnet object values change and GWT object Value fields display the data element values.

The following screen capture shows the resulting translation with AI objects. Temperature units and scale range are implemented with an AIC object.

The following screen capture shows resulting translation with AV objects, for degrees Centigrade.

The following screen capture shows resulting translation with AV objects, for degrees Fahrenheit.

22. Click OK to save and close.

Removing a Device from the Wireless Network

To remove a device from the wireless network:

. Delete the device address from associated GWT object

. Delete the GWT object.

The advantage of deleting the address from the GWT object rather than deleting the object is that the configuration can be retained as a template for a specific wireless device and used in another controller.

Page 20 of 40 CON-ENOC Application Guide Edition 2.1

How to Add an Output or Receiver Device to the Wireless Network

An output or receiver device is an EnOcean-technology based device that accepts commands from the Delta controller and then controls an output device such as a valve actuator or an electrical-load controller.

To add a transmitting device such as a sensor to the wireless network, see How to Add a Transmitter Device to the Wireless Network.

Compared to transmitting devices, receiver devices are more complex. To add a receiver device to the wireless network, you need more time and more detailed information about the device operation than for a sensor device.

Instead of attempting to provide a generalized procedure for adding a receiver device to the wireless network, this document describes in detail how to add the models of receiver devices that are supported by Delta Controls.

Output or Receiver Devices Supported by Delta Controls Delta Controls has focused its EnOcean Wireless Solution development and testing on the specific receiver devices listed below. If you want to add a device to the wireless network that is not listed below, see Adding an Unlisted Output or Receiver Device.

EchoFlex www.echoflexsolutions.com

. Load controller module, models ERM-DLC-LV, ERM-DL-LV

. Load controller module, models ERM-DLC-277, ERM-DL-277

. Load controller module, models ERM-DLC, ERM-DL

ILLUMRA www.illumra.com

. 3-wire relay, models E3R-02-3HOTP, E3R-12-3HOTP, E3R-24-3HOTP, E3R-27-3HOTP

. Plug-in relay, models E3R-R12GP, E3R-R12GP-Z

Spartan Peripheral Devices www.spartan-pd.com

. Control valve actuators, model ME83xx

BACnet Objects Supported

An output device receives its control value from a BACnet output object that resides in the controller to which the CON-ENOC is connected.

For Version 3.33 firmware, the following BACnet output object types are supported:

. Analog Variable (AV) object

. Binary Variable (BV) object

. Multi-state Variable (MV) object

Page 21 of 40

For Version 3.40 firmware the following BACnet output object types are supported:

. Analog Output (AO) object

. Analog Variable (AV) object

. Binary Output (BO) object

. Binary Variable (BV) object

. Multi-state Variable (MV) object

About the GWT object translation programming fields for output data The GWT object dialog provides several fields that you use to program the GWT object to translate the BACnet output object device data before it is sent to the EnOcean-technology based device. The fields are arranged in tabular form with multiple rows. The column headings and role in the translation are:

Name – Type the name you want for this data element. This field has a limit of 12 characters. The full name of the object is created in the form: GWT object name_GWT Name column text.

Reference – Specifies the object reference for the output object that controls the device.

Reference for DSC and DAC controllers

AO and BO object reference convention: Enter the complete object reference, such as BO15001. The object reference must be in the range 15001 to 15250. AO and BO objects are not supported for V3.33 firmware.

When the GWT object creates the output object, it expands the abbreviated object reference to its complete form of TT1GGnn where TT is the object type AV, BV or MV, GG is the GWT object reference and nn is the output object reference. For example, AV2 created by GWT1 becomes AV10102.

Reference for enteliBUS controllers

Enter the object reference in the abbreviated form of TTnn where TT is the object type AO, BO, AV, BV or MV and nn is the output object reference in the range 1 to 99. When more than two digits are entered, only the two least significant digits are retained. For example, AV2 or MV42. An object reference of 0 is not valid and will cause an error message in the Description field.

When the GWT object creates an output object, it expands the object reference to its complete form of TT14GG0nn when the controller is connected to Net1 and of TT15GG0nn when the controller is connected to Net2, where TT is the output object type AO, BO, AV, BV or MV, GG is the GWT object reference number and 0nn is the output object reference. For example, AV2 on Net1 and created by GWT1 becomes AV1401002.

DataByte, Bit(s), Parm1, Parm2, Shifter – specify how GWT object translates the object data to the output data. These settings are specific for each output or receiver device.

Function – specifies the GWT built-in data translation function to use, as described in Table 2 in the following section.

Value – Displays the data element value that is transmitted to the device. That is, the data element value after the translation specified by Function, Parm1, Parm2, Bit(s) and Shifter is applied to the reference object value.

Page 22 of 40 CON-ENOC Application Guide Edition 2.1

Reference for enteliZONE controllers

AO, BO, AV, BV or MV object reference convention: Enter the object reference in the abbreviated form of TTnn where TT is the object type AO, BO, AV, BV or MV and nn is the object reference number. Allow the GWT object to determine the complete object reference.

When the GWT object creates the output object, it expands the abbreviated object reference to its complete form of TT1GGnn where TT is the object type AO, BO, AV, BV or MV, GG is the GWT object reference and nn is the output object reference. For example, AV2 created by GWT1 becomes AV10102.

About GWT Functions for Translating Output Data To simplify the translation of data being sent to EnOcean-technology based output devices, Delta implemented functions in the GWT object to translate common device data element types. You enter the function number in the GWT object dialog Function column.

Table 2 GWT Object Functions for Translating Output Data

Function Description Application

100 0-100 pass-through for Use this function with an AO object. Spartan valve for AO object When the value of the AO object is less than 100, then that value Function 100 is not is sent to the device. supported in Version 3.33 When the value of the AO object is 100 or greater, then 100 is firmware. sent to the device.

101 Execute logical ORing When reference is a BO or BV object and its value is 1 then set the bits specified by Mask. AO and BO objects are not supported in Version 3.33 When reference is an AO or AV object and its value is not equal to firmware. zero then set the bits specified by Mask.

102 Add constant bits Set the bits specified by Mask, regardless of the output object’s value

103 Send Parm1 Use Parm1 as the constant data value that is sent to the device. Ignore the output object’s value.

104 Send either Parm1 or When the output object’s value is zero, then Parm1 is sent. When Parm2 the output object’s value is not equal to zero, then Parm2 is sent.

105 Scale the output data Data from output object is in the range 0 to 255. The GWT object range sends it to the device after scaling data to range Parm1 to Parm2.

When the object’s value is 0 then the smaller value of Parm1 or Parm2 is sent. When the object’s value is 255 then the larger value of Parm1 or Parm2 is sent. Object values between 0 and 255 are scaled and sent.

Page 23 of 40

Function Description Application

106 Scale the output data Data from output object is in the range 0 to 255. The GWT object range sends it to the device after scaling data to range Parm1 to Parm2.

When the object’s value is 0 then the larger value of Parm1 or Parm2 is sent. When the object’s value is 255 then the smaller value of Parm1 or Parm2 is sent. Object values between 0 and 255 are scaled and sent

107,108 Reserved

109 0-100 pass-through for Use this function with an AV object. Spartan valve for AV object When the value of the AV object is between 0 and 100, then the AV value is sent to the device.

When the value of the AV object is 100 or greater, then a value of 100 is sent to the device.

When the value of the AV object is 0 or smaller, then a value of 0 is sent to the device.

Adding the EchoFlex ERM Load Controller Module This section applies to all of the following EchoFlex devices: ERM-DLC, ERM-DL, ERM-DLC-277, ERM-DL-277, ERM-DLC-LV, and ERM-DLC-LV.

The EchoFlex ERM load controller modules are embedded wireless devices that automate the activation of a variety of electrical loads. These devices install in an electrical junction box, behind a receptacle, in a wall switch, in a ceiling fixture, or any other location where an electrical load is located.

The Delta Controls EnOcean interface provides open loop control that allows you to command the load controller relay through a binary object.

The EchoFlex ERM-DL Load Controller Module can be configured to transmit status information.

Main steps in adding the EchoFlex ERM Load Controller Module There are three mains steps in adding this device to the wireless network:

1. Complete steps 1, 2 and 3 in the section How to Integrate the EnOcean Wireless Solution. 2. Join the EchoFlex ERM to the wireless network. 3. Configure a binary object to command the load controller relay. 4. Configure a binary object to receive status from the load controller relay Steps 2, 3 and 4 are described in detail in the following sections.

Page 24 of 40 CON-ENOC Application Guide Edition 2.1

Step 2: Joining the EchoFlex ERM to the wireless network

1. Create a Gateway Translation (GWT) object to represent the device. There are two methods for creating the GWT object, described below as method A and method B: A. Obtain the GWT object from the EnOcean Wireless Solution page on George and load it into the Delta controller database. Using the GWT object from George is the recommended approach. This object is configured by Delta for the EchoFlex ERM. B. Use ORCAview to create a GWT object to represent the EchoFlex ERM. 2. Method A: Open the dialog and select the Setup tab. Verify that the information is the same as in the following screen capture. Go to Step 3: Configuring the binary object to command the load controller relay. Method B: Create a GWT object, open the dialog and select the Setup tab. Be sure that you have created the object by clicking Apply. Continue with the next step in this procedure. 3. Select EchoFlex ERM-DL or EchoFlex ERM-DL-LV in the Command Link list. Set the Reliability Timer to zero unless the device you are adding supports the capability to transmit status information and you want to monitor that status. Enter the learn packet information into the first row, exactly as shown in the following screen capture.

4. Press the Clear button on the device and keep it pressed for several seconds to erase the wireless network join information in the device. The red Power LED is illuminated without blinking when the device is not joined to a wireless network. 5. Press the Learn button on the device to start the learning process. The learning process continues for approximately 30 seconds. The green Learn LED is illuminated during the learning process. 6. While the learning process is in progress, click Apply on the GWT object dialog. Wait for the join process to be completed. You know that the join process is completed and that the device has joined the wireless network when the following conditions are present: . The Power LED on the device is blinking.

. The Learn LED on the device is extinguished.

Page 25 of 40

Step 3: Configuring the binary object to command the load controller relay

1. Enter the binary object name. The full name for the binary object is created by the GWT object when it creates the object. The full name comprises the GWT object name, an underscore character, and the name you enter in the Name column of the command packet row. For example, when the GWT object name is Room101Lighting and you enter Control, then the full name for the binary object is Room101Lighting_Control. 2. Enter the object reference for the output object that will be controlling the device, in the second row in the Reference field. With V3.40 firmware you can use either a BO object or a BV object. Unless you need to use the intrinsic alarming feature of the BO object, it is recommended that you use a BV object. The object reference convention for BO objects differs from that of the BV objects. See About the GWT object translation programming fields for output data for a description of the object reference conventions. 3. Enter the command packet information, the DataByte, Bit(s), Parm1, Parm2, Shifter, and Function fields, in the second row, exactly as shown in the following screen capture. 4. Click Create BACnet Objects and then click Apply to create the binary object. The full name for the object and the complete object reference are created and displayed as shown in the following screen capture.

5. Test that you can control the device by overriding the binary object between On and Off. Observe the LEDs on the CON-ENOC which blink when the command is transmitted. Observe that the EchoFlex ERM relay operates according to the command. 6. The EchoFlex ERM can be configured to transmit a status telegram every 100 seconds. By associating the status with a BV object, you can confirm that commands are received by the device.

Page 26 of 40 CON-ENOC Application Guide Edition 2.1

Step 4: Configuring the binary object to receive status from the load controller relay Receiving status from the load controller relay is option.

1. To enable the Status telegram on the Echoflex ERM relay, press and hold the Learn button and press the Clear button twice. The Learn LED will blink twice when enabling this telegram. 2. Monitor the GW object dialog Description tab. The Teach_in packet with EEP = 07-11-01 contains the address you need, as shown in the following screen capture.

3. Enter the address in the first row of GWT object under Name column in the GWT object, as highlighted in blue in the following screen capture. 4. Add another row to convert the status into BACnet object, as outlined in red in the following screen capture.

5. Click Create BACnet Objects and click Apply. A Status telegram is broadcast every 100 seconds or when the relay output changes. More detail on Status Feedback Telegram can be found on page 8 of Echoflex ERM datasheet.

Removing the EchoFlex ERM from a wireless network To remove or break the join of an EchoFlex ERM from a wireless network:

. Press and hold the Clear button for five seconds. The Power LED is illuminated but it is not blinking.

Page 27 of 40

Adding the ILLUMRA E3R Relay

This section applies to all of the following ILLUMRA devices: E3R-R12GP, E3R-R12GP-Z and E3R-Rxx-3HOTP.

The ILLUMRA E3R-R12GP and E3R-R12GP-Z Plug-in Relays provide on/off control of lights and other plug-in devices.

The ILLUMRA E3R-Rxx-3HOTP relays provide on/off control of lights and other loads.

The Delta Controls EnOcean interface provides open loop control that allows you to command the load controller relay through a binary object.

The ILLUMRA E3R relays don’t transmit information.

Main steps in adding the ILLUMRA E3R Relay There are three mains steps in adding this device to the wireless network:

1. Complete steps 1, 2 and 3 in the section How to Integrate the EnOcean Wireless Solution. 2. Join the ILLUMRA E3R to the wireless network. 3. Configure a binary object to command the relay. Steps 2 and 3 are described in detail in the following sections.

Step 2: Joining the ILLUMRA E3R to the wireless network Because the ILLUMRA E3R doesn’t transmit information, you don’t need to know a device address to add or join it to the wireless network.

There are no status LEDs on the ILLUMRA E3R. This procedure assumes you have a light plugged in to the relay.

To add an ILLUMRA E3R to wireless network: 1. Create a Gateway Translation (GWT) object to represent the ILLUMRA E3R. There are two methods for creating the GWT object, described below as method A and method B: A. Obtain the GWT object from the EnOcean Wireless Solution page on George and load it into the Delta controller database. Using the GWT object from George is the recommended approach. This object is configured by Delta for the ILLUMRA E3R. B. Use ORCAview to create a GWT object to represent the ILLUMRA E3R. 2. Method A: Open the dialog and select the Setup tab. Verify that the information is the same as in the following screen capture. Go to Step 3: Configuring the binary object to command the relay. Method B: Create a GWT object, open the dialog and select the Setup tab. Be sure that you have created the object by clicking Apply. Continue with the next step in this procedure.

Page 28 of 40 CON-ENOC Application Guide Edition 2.1

3. Select Illumra E3R-xx-3HOPTP or Illumra E3R-R12GP in the Command Link list. Set the Reliability Timer to zero. Enter the learn packet information into the first row, exactly as shown in the following screen capture.

4. Press and hold the Clear button on the device for several seconds and then release it. The wireless network join information in the device has been erased. When the relay starts to click open and closed audibly, the memory has been erased. 5. To prepare the device to join the wireless network, you must put it in Learn Mode 2. To enter Learn Mode 2, there are two steps: firstly press and hold the Learn button on the device for one second and then release it. The relay clicks open and closed audibly in the pattern shown below to indicate that it is in Learn Mode 1:

Learn Mode 1 relay open and close pattern Secondly, press and hold the Learn button on the device for three seconds and then release it. The relay clicks open and closed audibly in the pattern shown below to indicate that it is in Learn Mode 2:

Learn Mode 2 relay open and close pattern Now click Apply on the GWT object dialog. You should observe a momentary pause in the relay click pattern. Wait for the join process to be completed. You know that the join process is completed and that the device has joined the wireless network when the relay stops opening and closing.

Step 3: Configuring the binary object to command the relay

1. Enter identical binary object names in both the second and third row. The full name for the binary object is created by the GWT object when it creates the object. The full name comprises the GWT object name, an underscore character, and the name you enter in the Name column of the command packet row. For example, when the GWT object name is Room101Lamps and you enter Control, then the full name for the binary object is Room101Lamps_Control.

Page 29 of 40

2. Enter the identical binary object references for the object that will be controlling the device, in the Reference field, in both the second and third row. With V3.40 firmware you can use either a BO object or a BV object. Unless you need to use the intrinsic alarming feature of the BO object, it is recommended that you use a BV object. The object reference convention for BO objects differs from that of the BV objects. See About the GWT object translation programming fields for output data for a description of the object reference conventions. 3. Enter the command packet information, the DataByte, Bit(s), Parm1, Parm2, Shifter, and Function fields, in the second and third row, exactly as shown in the following screen capture. 4. Click Create BACnet Objects and then click Apply to create the binary object. The full name for the object and the complete object reference are created and displayed as shown in the following screen capture.

Removing the ILLUMRA E3R from a wireless network To remove or break the join of an ILLUMRA E3R from a wireless network:

. Press and hold the Clear button for five seconds.

Page 30 of 40 CON-ENOC Application Guide Edition 2.1

Adding the Spartan ME83xx Zone Valve Actuator

The Spartan ME83xx Zone Valve Actuator is an embedded wireless control valve actuator that can be modulated to be precisely positioned to flow requirement.

The Delta Controls EnOcean interface allows you to command the actuator position through an analog object and to receive position status through a second analog object.

Main steps in adding the Spartan ME83xx Zone Valve Actuator There are three mains steps in adding this device to the wireless network:

1. Complete steps 1, 2 and 3 in the section How to Integrate the EnOcean Wireless Solution. 2. Join the Spartan ME83xx Zone Valve Actuator to the wireless network. 3. Configure the analog object to command the actuator position and configure the analog object to receive the actuator position feedback. Steps 2 and 3 are described in detail in the following sections.

Step 2: Joining the Spartan ME83xx to the wireless network To add a Spartan ME83xx device to wireless network: 1. Create a Gateway Translation (GWT) object to represent the device. There are two methods for creating the GWT object, described below as method A and method B: A. Obtain the GWT object from the EnOcean Wireless Solution page on George and load it into the Delta controller database. Using the Spartan ME83xx GWT object from George is the recommended approach. This object is configured by Delta for the Spartan ME83xx. B. Use ORCAview to create a GWT object to represent the Spartan ME83xx. 2. Method A: Open the dialog and select the Setup tab. Verify that the information is the same as in the following screen capture. Go to Step 3: Configuring the analog object to command and monitor the actuator position. Method B: Create a GWT object, open the dialog and select the Setup tab. Be sure that you have actually created the object by clicking Apply. Continue with the next step in this procedure.

Page 31 of 40

3. Select Spartan Valve ME83xx in the Command Link list. Set the Reliability Timer to zero unless the device you are adding supports the capability to transmit status information and you want to monitor that status. Enter the learn packet information into the first row, exactly as shown in the following screen capture.

4. Press the Bind button on the Spartan ME83xx to start the learning process. The learning process continues for approximately 30 seconds. The red LED blinks continuously during the learning process. 5. While the learning process is in progress, click Apply on the GWT object dialog. Wait for the join process to be completed. You know that the join process is completed and that the device has joined the wireless network when the GWT object dialog Reliability displays Connected, Link Status displays Active and the device address is displayed in the Name column of the first row.

Page 32 of 40 CON-ENOC Application Guide Edition 2.1

Step 3: Configuring the analog object to command and monitor the actuator position

1. Enter the analog object name. The full name for the analog object is created by the GWT object when the analog object is created. The full name comprises the GWT object name, an underscore character, and the name you enter in the Name column of the command packet row. For example, when the GWT object name is Room101HeatValve and you enter Position, then the full name for the analog object is Room101HeatValve _Position. 2. Enter the object reference for the object that will be controlling the device, in the Reference field. With V3.40 firmware you can use either an AO object or an AV object. Unless you need to use the intrinsic alarming feature of the AO object, it is recommended that you use an AV object. The object reference convention for AO objects differs from that of the AV objects. See About the GWT object translation programming fields for output data for a description of the object reference conventions. 3. Enter the Command Flag row, the DataByte, Bit(s), Parm1, Parm2, Shifter, and Function fields, exactly as shown in the following screen capture. 4. Enter the analog object name and the object reference for the object that will be receiving the valve position feedback. Use same conventions as described above in steps 1 and 2. 5. Enter the command packet information, the DataByte, Bit(s), Parm1, Parm2, Shifter, and Function fields, in the second and fourth rows, exactly as shown in the following screen capture.

Page 33 of 40

6. Click Create BACnet Objects and then click Apply to create the analog variable object. The full name for the object and the complete object reference are displayed as shown in the following screen capture.

7. Test that you can control the device by changing the position analog variable value. Observe the LEDs on the CON-ENOC which blink when the command is transmitted. Observe that the valve changes position according to the command. Observe that the status value eventually is updated.

Removing the Spartan ME83xx from a wireless network To remove or break the join of a Spartan valve from a wireless network:

. Press and hold the Bind button for five seconds. The blue LED is extinguished.

Adding an Unlisted Output or Receiver Device When you want to add an output or receiver device that is not specifically supported by a selection in the GWT object Command Link list, you can use either the Other (1 click learn) or Other (3 click learn) selections on the Command Link list.

1 click learn and 3 click learn refer to how the device learns when a light switch is linked to it. The manufacturer specifies that you click the switch once (1 click learn) or three times (3 click learn) with the device in Learn mode.

Contact Delta Technical Support who will work with you to help you determine the learn packet information and command information for the device.

Page 34 of 40 CON-ENOC Application Guide Edition 2.1

Managing GWT Object Configurations

A typical EnOcean Wireless Solution network consists of many of the same manufacturer’s device such as, for example, the EchoFlex temperature sensor. After you have the first device added to the wireless network and the GWT translation programmed correctly, you want to duplicate the GWT object as a template to replicate this configuration to the other same devices.

Saving the GWT Object

To save a GWT object, right click on it and select Save As from the pop-up menu.

To save a GWT object as a template: 1. Open the GWT object dialog 2. Select the Description tab and enter documentation about the device such as its EEP information, what BACnet objects to create, and so on. 3. Click OK to save and close the dialog. 4. Right click on template GWT object and select Save As from the pop-up menu.

Loading the GWT Object To load a GWT object into a controller, right click on the controller and select Load from the pop-up menu.

Monitoring Sensor Performance and Reliability

Two features of Delta’s EnOcean Wireless Solution, as described in the following sections, allow you to monitor the performance and reliability of a sensor and to generate an alarm or event to notify the operator when required.

Monitoring the signal strength of a sensor To monitor the signal strength of a sensor, follow these main steps:

. In the GWT object, add a row that references an AV object and has Function set to 18. Set all other values in the row to zero.

. Configure the AV object with units set to None. The AV object holds the RSSI signal strength value for the sensor.

. Add an EV object to the database, configured to detect an Out of Range alarm, to generate an alarm or event when the signal strength is too low. For an indoor, office-like environment, -81 dBm or greater is reliable. When the value is, for example, -85 dBm or lower for a period of time, you may want to record an event. For an outdoor or line-of-sight environment, -91 dBm or greater is reliable.

Page 35 of 40

Monitoring the reliability of the connection to a sensor

For devices that support a periodic heartbeat telegram, you can use the Reliability status to monitor the wireless link status and cause an alarm when it goes to Not Connected state. Reliability status is available in the GWT object’s Flag property; Reliability status = Connected when Flag = 1; Reliability status = Not Connected when Flag = 0.

To implement alarm reporting for Reliability status: 1. For each GWT object for which you want to monitor Reliability status, create a BV object and a BDC object set up with Active State = Connected and Inactive State = Not Connected. 2. Create corresponding EV objects to report a Change of State alarm when a BV object transitions to the Not Connected state. 3. In a GLC+ program, include a statement as follows for each GWT object: BV# = GWT#.Flag where # is the object reference number

Understanding the CON-ENOC LEDs

The CON-ENOC zone gateway has three LEDs that can be used to monitor the functioning of an EnOcean Wireless Solution.

The LEDs are named and located as shown in the following illustration.

The function of each LED is as follows:

Power LED

The Power LED indicates that power is properly applied to the CON-ENOC. It is a green LED.

. Extinguished when supply voltage is below operational limit.

. Illuminated green without blinking when supply voltage is within operational limits

. Blinking green when CON-ENOC firmware is running properly

Page 36 of 40 CON-ENOC Application Guide Edition 2.1

Wireless Activity LED

The Wireless Activity LED indicates communications traffic on the wireless communications link between the CON-ENOC and the wireless devices that are joined to it. It is a green and red LED.

. Blinks green for every packet sent or received over the wireless communications link

. Illuminated red without blinking when a wireless communication error occurs, such as: - no radio (RSSI > -84 dBm) received for 10 minutes - mismatched frequencies

RS-485 Activity LED The RS-485 Activity LED indicates communications traffic on the wired communications link between the CON-ENOC and the Delta controller where the GWT object resides. It is a green and red LED.

. Blinks green for every packet sent or received over the RS-485 communications link

. Illuminated red without blinking when a RS-485 communication error occurs, such as no communication with controller for more than 60 seconds

Managing Different Gateways on One Site

This section about managing gateway object dialogs pertains to Version 3.33 and to 3.40R1 sites. Sites with 3.40R2 and higher do not have this situation because the OWS opens the correct GW/GWT dialog automatically.

Delta Controls, at the time this document was written, has three gateway products: Modbus, M-Bus® (Meter Bus) and EnOcean. Each gateway uses unique GW/GWT object dialogs that share the same object dialog file name.

A technician who services a site that includes different gateways must use the correct customized GW/GWT object dialogs for each gateway. As is described in section Step 2: Installing the Customized Object Dialogs on OWS , Versions 3.33 and 3.40R1 have different setups for the GW/GWT object dialogs. The technician needs to add and remove the customized GW/GWT object dialogs depending on which gateway he or she wants to service.

Version 3.33 and Different Gateways on One Site

For Version 3.33, ORCAview expects gateway dialogs to reside in the …\vendor8\DAC folder. This means that only one type of gateway can be used at a time because only one type of gateway can use the file names vn8dacv3gw.dlg and vn8dacv3gwt.dlg. The Modbus, Enocean and M-Bus dialogs need to be backed up for the technician to be able to swap between the three.

Version 3.40 R1 and Different Gateways on One Site For Version 3.40 R1, the Modbus dialogs are located in c:/program files/delta controls/3.40/dialogs.vendor8/dac. The EnOcean and M-Bus dialogs are placed in a different location which takes priority over the location where the Modbus dialogs are located. This means for Version 3.40R1, the Modbus dialogs never need to be touched, however, the Enocean and M-Bus dialogs must be treated the same way as described for Version 3.33.

Page 37 of 40

Troubleshooting

The following table describes common issues and their probable solution. If a solution to an issue isn’t listed here please consult https://support.deltacontrols.com.

Symptom Solution

CON-ENOC is not communicating with Delta Verify jumpers in CON-ENOC match settings on GW object controller setup tab and Installation Guide.

Reset the Delta controller.

EnOcean device profile data doesn’t display on Wireless device with that address is already represented by GW object dialog Description tab when Learn a GWT object. button pressed Incompatible frequencies between device and CON-ENOC

BACnet objects don’t create from a GWT object When object reference is already in use then object creation won’t complete. Solution: Change the reference or delete the existing reference object.

This also applies to objects with the same name. All object names in the controller must be unique.

When the name you specify is greater than 67 characters, then object creation won’t complete.

When one of the object references is specified incorrectly, then none of the objects is created.

AI or BI object is created but is in Fault This symptom is present when you attempt to use an AI or BI object with V3.33.

Solution: use an AV, BV or MV object with V3.33

Wireless device data isn’t displayed in the GWT You may not have the correct device address in the Name object dialog Value field. column, row 1.

Verify that the CON-ENOC is receiving data telegrams from the wireless device by observing the Wireless Activity LED. When the CON-ENOC receives data, the green LED illuminates briefly.

When the underscore character is used in the Underscore is a reserved character. Don’t use it in an object name, the name of the object that is created name. doesn’t include the underscore or preceding characters

After selecting Sensor or device from Command The GWT times out after approximately five minutes. You Link and clicking Apply, the GWT object times out need to put the device into join within five minutes after before device joins. clicking Apply.

Commands are sent to device when Command Known issue. Stop sending commands. Link is set to Idle and Reliability displays Not Connected.

Page 38 of 40 CON-ENOC Application Guide Edition 2.1

Symptom Solution

The GW object won't appear in the database Reload descriptors after you flash the controller to EnOcean firmware.

The GW object descriptor won't update after Reload descriptors upgrading the controller from one phase to another.

Immediately after joining an output device, the The output device is in Learn-In mode for about 30 output won't respond to commands. seconds. During this period, commands are ignored. Wait for approximately 30~45 seconds before commanding the output.

For output relays only: Reliability in GWT object This symptom occurs when the reliability timer is changed remains at Not Connected and never changes to to a non-zero value before the relay device is joined. Connected. To resolve this situation, delete the GWT, clear the device and join the device again. Be sure to keep the Reliability Timer setting equal to zero.

Document Control

Edition Date Changes

2.0 February 2013 Release edition for EnOcean Phase 3. First release for CON-ENOC.

2.1 September 2016 Added support for enteliZONE firmware 2.2 controllers.

Page 39 of 40

Appendix A – EnOcean Wireless Systems Range Planning Guide

Page 40 of 40

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

Wireless systems provide much simpler installation as well as the flexibility to relocate or add to a system, compared to installing wired systems. The easy recommendations in this planning guide are provided to ensure successful installation and reliable operation of robust EnOcean 868 or 315 MHz building radio networks.

Dipl. Ing. Armin Anders, EnOcean GmbH, VP Product Management

INTRODUCTION In buildings the following two major types of radio system installations are typically and will be mainly covered by this planning guide: a) Radio Sensors control the actuators directly (RF bus) In this case the radio paths to be covered are not very long. If needed a central radio repeater is installed for signal amplifying. Such installations are typically for e.g. residential homes:

b) Radio Sensors control the actuators via Automa- tion System Central placed radio gateways to an established building automation system (e.g. BACnet, TCP/IP, EIB/KNX, LON) are typically used in wide-area buildings, e.g. an office building:

Transmitter or Receiver

Table of content: 1. PRINCIPLES OF RADIO SIGNALS IN BUILDINGS page 2ff 2. PLANNING GUIDE FOR COMMERCIAL BUILDINGS page 7f 3. PLANNING GUIDE FOR RESIDENTIAL BUILDINGS page 9f 4. RADIO SYSTEM DEBUGGING page 11f

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

1. PRINCIPLES OF RADIO SIGNALS IN BUILDINGS

1.1 RANGE OF RADIO SIGNALS

Radio signals are electromagnetic waves, hence the signal becomes weaker the further it travels, the range is limited. The radio coverage is further decreased by specific materials found in the direction of the propagation. While radio waves can penetrate a wall, they are dampened more than on a direct line-of-sight path (LoS). In the following please find some examples of different types of wall:

Material Range reduction vs. LoS Tip 1 Wood, plaster, glass uncoated, without metal 0 - 10% Brick, press board 5 - 35% Ferro concrete 10 - 90% Metal, aluminium lining see 1.2

Figure: Range reduction of some typical in-door materials

Radio transmission shapes an ellipsoid, with Transmitter (Tx) and Receiver (Rx) in its both focal points. Because of that the geometric shape of a room determines the radio range. At 30 m range the theoretical diameter of the ellipsoid is around 10 m at 868 MHz and 17m at 315 MHz system frequency. So narrow floors with thick walls are unfavourable:

Figure: Radio transmission shapes an ellipsoid

Kind of antenna mounting and antenna distance from ceiling, floor and walls are a major influence for coverage. External antennas typically do have a better radio performance than internal antennas from in-wall receivers. People and other objects within a room also can reduce the radio range. Because of the big amount of different impacts, in practice the common specification of “30 m in-door range” should be considered more precisely. Reserve in the range planning is needed to achieve reliability of the radio system, even in case of several unfavourable conditions combined.

Tip 2 Reliable and robust in-door installation can be achieved through sufficient reserve in coverage. Recommendations from practice to provide this are: > 30 m under ideal conditions: Broad room, no obstacles, good antenna design and good antenna positions. Building is filled with furniture and people. And penetration through up to 5 dry walls or up to 2 brick walls or up to 2 aero concrete walls:

o > 20 m if transmitter and receiver do have good antenna design and good antenna positions.

o > 10 m if receiver is mounted into a massive wall. Or receiver is placed next to a room corner. And a small sized receiver with internal antenna is used. And switch or whip antenna is mounted on metall. Or range along a narrow floor. 1-2 metal-reinforced ceilings at upright penetration angle (in strong dependence of reinforcement density and antenna positions).

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

1.2 SCREENING

Massive objects made of metal, such as metallic separation walls and metal inserted ceilings, massive wall reinforcements and the metal foil of heat insulations, reflect electromagnetic waves and thus create what is known as radio shadow. However singularized small metal studs, e.g. the metal studs of a gypsum dry wall, don’t show a recognizable screening.

Metal separation walls: It can be noticed that radio transmission even works with metal indoor separation walls. This happens through reflections: Walls made of metal or concrete reflect the electromagnetic waves. The radio waves reach the next room or floor via a non metallic opening, e.g. a wooden door or an indoor glass window. Locally the radio range can be strongly reduced. Mounting an additional repeater at a suited location can easily provide an optional propagation path.

Tip 3 Important objects and factors that decreases or constraints coverage: Metal separation walls or hollow lightweight walls filled with insulating wool on metal foil Inserted ceilings with panels made of metal or carbon fibre Steel furniture, glass with metal coating (typically not used indoor) Switch mounted on metal surfaces (typically 30% loss of range) Use of metallic switch frames (typically 30% loss of range)) Fire-safety walls, elevator shafts, staircases and supply areas should be considered as screening. Avoid screening by repositioning the transmitting and/or receiving antenna away from the radio shadow, or by using a repeater.

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

1.3 PENETRATION ANGLE

The angle at which the transmitted signal hits the wall is very important. The effective wall thickness – and with it the signal attenuation – varies according to this angle. Signals should be transmitted as directly as possible through the wall. Wall niches should be avoided.

Tip 4 Avoid an unfavourable penetration angle by repositioning the transmitting and/or receiving antenna, or by using a repeater.

1.4 ANTENNA INSTALLATION

When using devices with an internal receiving antenna, the device should not be installed on the same side of the wall as the transmitter. Near a wall, the radio waves are likely to be subject to interfering dispersions or reflections. Consequently, the position of the antenna has to be on the opposite or connecting wall. When using devices with an external antenna, the ideal antenna installation place is a central location in the room. Where possible the antenna should be at least 10 – 15 cm away from the wall corner or concrete ceiling.

Tip 5 Avoid radio propagation along a wall (also given in a long narrow floor).

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

ACTIVE ANTENNA: A so-called active antenna is a radio unit with integrated antenna that communicates with the actuator unit via a simple multi-line cable (e.g. RS485). Thus no shielded antenna cable is needed, which would loose performance with increasing length and could be folded during installation. So an active antenna allows very simple failure test.

PASSVE ANTENNA: This kind of antenna is connected with the radio unit via a dedicated shielded antenna cable. A “Magnetic Antenna” needs to be placed on a large metallic surface to create an adequate anti-pole. A magnetic antenna can be very easily mounted at metallic objects, e.g. at an air tube behind a false ceiling. However a flat "Patch Antenna" (planar antenna) must be mounted away from metallic objects, e.g. onto a false ceiling made of gypsum or into a dry wall by using a wall box with a suited size (see picture). The patch antenna must not be mounted directly onto concrete which behaves similar to metal. Exception is the 868 MHz Metal Patch Antenna “MCA 1890MP“ from Hirschmann. Unobtrusively this flat antenna can be directly glued also onto a metal ceiling. More details about selection of suited passive antennas and antenna connectors can be found in the EnOcean Application Note „AN103 External Passive Antennas”.

Figure: Mounting a Magnetic Antenna Figure: Mounting a Patch Antenna

Tip 6 Do never flex a shielded antenna cable during installation. This can result in irreparable damage (performance reduction through change of impedance level)

1.5 DISTANCE BETWEEN RECEIVER AND SOURCES OF INTERFERENCE

The distance between EnOcean receivers and other transmitters (e.g. GSM / DECT / WLAN) or high- frequency sources of interference (computers, audio/video equipment) should be at least 50 cm. However, EnOcean transmitters can be installed next to any other high-frequency transmitter without any problem. Don’t use 868 MHz power RFID and 868 MHz EnOcean receivers in same room.

Tip 7 The distance of the EnOcean receiver to different high-frequency transmitters should be at least 50 cm, the transmitter position is not critical. No 868 MHz power RFID and 868 MHz EnOcean receivers in the same room.

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

1.6. USE OF REPEATERS

In case of poor reception, it may be helpful to use a repeater. EnOcean repeaters do not require any configuration (e.g. programming) and are put into operation simply by connecting them to the supply voltage. The various possibilities of use are shown by the illustrations in the chapters “Screening” and “Penetration”.

Tip 8 While planning, it may be worth considering retrofitting the system with a repeater (power supply available). Do not use too many repeaters as this is counterproductive (higher costs, telegram collisions).

A poor radio signal is received, refreshed and transmitted again, so nearly a double radio range can be achieved. 1-level EnOcean repeaters cannot be cascaded; telegrams already repeated are not repeated again. EnOcean repeaters which can be switched to 2-level function allow two repeaters to be cascaded which should be needed in extreme cases only.

1.7. FIELD INTENSITY METER

The EPM is a mobile field intensity meter enabling the installer to determine the ideal mounting positions for sensors and receivers. Furthermore, faulty connections of devices already installed can be checked. The EPM 300 meter shows the field intensities of radio telegrams received and any interfering radio signals in the 868 MHz range, the EPM 300C in the 315 MHz range. Please see chapter 4 “Radio System Debugging” and the EPM operating instructions for further information.

How to use the field intensity meter: Person 1 operates the radio sensor and generates radio telegrams by pressing the button. Person 2 checks the field intensity received on the display of the device and thus determines the ideal position.

Figure: Field intensity meter EPM 300

Tip 9 Even after careful planning, the EPM field intensity meter should be used to verify proper reception at the receiver position during installation. The EPM can be used for on-site determination of the ideal mounting position and for identification of an interfering transmitter (also see chapter 4 “Radio System Debugging”).

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

2. PLANNING GUIDE FOR COMMERCIAL BUILDINGS

The radio coverage in commercial buildings is usually restricted by fire safety walls that must be considered as screening. Inside the fire protected sections lightweight or glass partition walls are used with good radio wave propagation properties (except for metal reinforcements or metalized walls!). The following are two common installation architectures

Radio Sensors control the Actuators directly (RF bus) Usually, the radio paths to be covered are not very long (“cubicle installation”).

Radio Sensors control the Actuators via Automation System Central placed radio Gateways to the Building Automation System (e.g. BACnet, TCP/IP, LON, EIB) are used for system coverage. In the following a reliable radio planning is shown that can be done in quick time and using simple tools only:

STEP 1: Take a Building Floor Plan and a Drawing Circle

STEP 2: Mark relevant Radio Shadings into the Floor Plan Fire Protection Walls Lavatories, Staircases, Elevator Shafts, Supply Areas

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

STEP 3: Draw circles area wide The circle centre points are the ideal positions of the radio gateways. By that the gateways should be positioned in such a way that no screens block the connection to any corner inside the fire safety section (potential sensor positions).

Tip 10 For reliable range planning a sum of unfavourable conditions have to be assumed. The lessons learned from practice shows that planning with 10-12m range offers extensive reserve to avoid most typical bad conditions. Bad conditions also often come from later changes of the ambient (room filled with people, alteration of partition walls, furniture, room plants, etc.). Also a typical realization of the sensors or gateway real positions of 1 meter more or less against the plan doesn’t matter because of sufficient reserve.

Tip 11 For a highly robust radio transmission system it is advisable to implement a redundant radio receiver path. To do so, program two gateways for parallel reception of radio transmitters.

Tip 12 Even after careful planning, range tests should be done during installation with EPM radio level meter to verify proper reception at the receiver positions. Unfavourable conditions can be improved by changing of antenna position or using a repeater.

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

3. PLANNING GUIDE FOR RESIDENTIAL BUILDINGS

For applications restricted to one or two rooms (e.g. when retrofitting a switch or an awning) the direct transmission range is usually adequate. For applications “throughout” a building, the following differentiations must be made:

Installation in Multi-room Flat or One-family House of up to 400 sqm Larger residential units should be fitted with a repeater. The repeater should be centrally placed, e.g. in the centre of the middle floor. The exact repeater position is noncritical. EnOcean repeaters are designed in such a way that a second repeater can be added in case of heavy ceiling reinforcement or other screening. Please note that using too many repeaters is counterproductive (higher costs, telegram collisions).

Installation in Multifamily Unit or High-rise Building Use separate radio systems for each flat. One radio gateway per flat can be used for cross-property connection via an established automation system (e.g. BACnet, EIB/KNX, LON, TCP/IP, etc.).

3.1 SMALL RESIDENTIAL UNIT (up to 3 walls, 1 ceiling)

Transmitter or Receiver

Tip 13 For bedsits or up to 2 floors in a townhouse the direct transmission range is usually adequate.

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

3.2 MULTI-ROOM FLAT AND ONE FAMILY HOUSE (more than 3 walls, more than one ceiling)

Transmitter or Receiver

Tip 14 In a larger residential unit, it is generally advisable to install a central repeater to ensure radio coverage.

3.3 EXTREME EXAMPLE IN A ONE-FAMILY HOME

Transmitter or Receiver

Tip 15 In rare cases of heavily reinforced concrete ceilings or thick basement walls a second repeater may be necessary to ensure full coverage (both repeaters must be switched to 2-level function, see information in chapter 1.6).

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

4. RADIO SYSTEM DEBUGGING

The foregoing information on selecting the ideal place of installation for transmitters and receivers has been provided to ensure a smooth operation of the devices. If, however, you still have experience radio transmission problems, please refer first to the following table for troubleshooting:

Check with EPM100 Possible Cause and Remedy

Near the transmitter (distance Transmitter fails to send. around 20-50 cm) the EPM level meter does not receive a trans- Check the transmitter. Where neces- Transmitter re- mitter telegram. sary, ensure sufficient light for solar- ceived not at all operated transmitters (for a quick func- Activate transmission telegram, the tional test, briefly expose to daylight or green HI LED of the EPM fails to light place under a bright lamp). up.

Near the receiver antenna (dis- Transmitter is installed outside the tance around 20-50 cm) the EPM receiver range (or transmitter is does not receive a transmitter removed or maybe exchanged). telegram.

Reposition transmitter or receiver an- Activate transmission telegram, the tenna. following LED of the EPM fails to light up: Follow the notes given in chapter 1. • HI for in-wall mounted receivers • LO for receivers with external antenna.

Near receiver antenna (distance a) Transmitter not programmed or about 20-50 cm) the EPM has wrong transmitter programmed. good reception of transmission Reprogram transmitter into the re- telegrams. ceiver.

Activate transmission telegram, the b) Receiver does not receive. green HI LED of the EPM lights up. Check the receiver and the installation of the antenna and the antenna cable.

Not valid EnOcean telegrams are a) Low-power jammer near re- received permanently. ceiver. Move jammer (telephone, PC etc.) at One of the both HI/LO LEDS of the least 50 cm away from EnOcean re- EPM signals constantly, but not the ceiver. yellow VALID LED. b) High-power jammer present. Remove jammer.

APPLICATION NOTE 001

EnOcean Wireless Systems – RANGE PLANNING GUIDE

Check with EPM100 Possible Cause and Remedy

Transmitter in- Near receiver antenna (distance a) Receiver is placed at the limit of termittently not of around 20-50 cm) the EPM the transmitter’s range. received level meter receives transmission Remove transmitter or receiver an- telegrams only marginally. tenna, or use Repeater. Follow the notes given in chapter 1. Activate transmission telegram, the following LED of the EPM fails to light b) Transmitter not installed at the up: expected position (or wrong as- • HI for in-wall mounted re- signment Sender/Receiver). ceiver. Assign correctly. • LO for receiver with external antenna. c) The place of installation of the transmitter changes occasionally (e.g. transmitter not fitted). Choose a place of installation for the transmitter within the range of reception.

Near receiver antenna (distance Receiver does not receive. about 20-50 cm) the EPM has Check the receiver and the installation good reception of transmission of the antenna and the antenna cable. telegrams.

Not valid EnOcean telegrams are Jammer present. received temporarily. Remove jammer One of the both HI/LO LEDS of the EPM signals temporarily, but not the yellow VALID LED.

DISCLAIMER

The information provided in this document describes typical features of the EnOcean radio transmission system and should not be misunderstood as specified operating characteristics. No liability is assumed for errors and / or omissions. We reserve the right to make changes without prior notice. For the latest documentation visit the EnOcean website at www.enocean.com.