DELTA GROUP EnOcean O3-DIN User guide

O3-DIN

EnOcean Gateway

Application Guide

Firmware 4.13

Edition 1.0

No part of this document 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.

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

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. Delta Controls may

make improvements and/or changes to this document at any time.

Document edition: 1.0

Contents

Introduction 5

EnOcean Basics 5

O3-DIN EnOcean Gateway Basics 5

O3-DIN EnOcean Gateway Specifications 6

Getting Started 8

Setting Up an EnOcean Network 8

Setting Up the O3-DIN EnOcean Gateway 9

Configuring Input Devices 10

Configuring Input Devices Using an O3 Hub 10

Configuring Input Devices Using a CON-ENOC 11

Manually Pairing an EnOcean Device 13

Resetting Pairing 13

Configuring Output Devices 14

Main Steps for Configuring Output Devices 14

Configuring Simple Relays 14

RPS Force Send 16

Configuring Load Controllers with Central Command Support 20

Setting Up Feedback 22

Configuring Radiator Valve Controllers 23

Monitoring Network Communication 26

Understanding the Link Status 26

Understanding the Reliability Timer 26

Monitoring Communication Statistics 27

Monitoring the Wireless Signal 28

Value of Signal Strength 28

Working With Range and Scale Values 29

Understanding Range and Scale Values 29

Using a BV Object to Show Off/On States 30

Working With Mapping Files 32

Modifying a Default Mapping File 32

Translation Table Details 33

Differences Between Current and Previous FIL Object Mappings 34

Creating a Custom XML Mapping File 35

Saving Mapping Data 36

Troubleshooting 37

Troubleshooting an O3 Hub 37

The O3 Hub is not communicating 37

Communications are unreliable 37

How to Determine the Sending ID of O3 Hub Packets 38

Troubleshooting a CON-ENOC 38

The CON-ENOC is not communicating 38

Communications are unreliable 38

Troubleshooting EnOcean Objects 39

EnOcean object values are not updating 39

The Device Address CSV object is not learning a new address 39

EnOcean object values are lost when a controller is shut down 39

Appendix B:FIL EEP Profiles 40

Revision History 43

Introduction

This section covers the following topics:

lEnOcean Basics

lO3-DIN EnOcean Gateway Basics

lO3-DIN EnOcean Gateway Specifications

EnOcean Basics

EnOcean is a wireless protocol for ultra-low power energy harvesting sensors, switches, and

controls. EnOcean devices offer batteryless, maintenance-free operation and come with

standardized communication profiles to ensure interoperability across manufacturers.

EnOcean devices use short, infrequent radio signals and can transmit over distances of up to

30m (100 ft) indoors. The signals are received and processed by line-powered devices such as

relay switch actuators, repeaters, or gateways.

For more information about the EnOcean wireless standard, see https://www.enocean.com and

https://www.enocean-alliance.org

O3-DIN EnOcean Gateway Basics

The O3-DIN EnOcean gateway connects wireless EnOcean devices to the BACnet building

network using a wired serial connection to an EnOcean-capable O3 Hub sensor hub or

CON-ENOC adapter. The communication protocol is defined by EnOcean Serial Protocol 3.0.

The gateway acts as both a receiver and a transmitter, reading from EnOcean input devices and

writing to EnOcean output devices. Structured View (SV) objects represent the EnOcean devices

on the network, with device data mapped to BACnet values according to a supplied XML

mapping file. Normally these mappings are based on an EnOcean Equipment Profile (EEP), but

custom mappings are also supported.

The gateway currently supports the following EEP types:

lF6: Repeated Switch Communication (RPS) Telegram — e.g., F6-02-01

lD5: 1 Byte Communication (1BS) Telegram — e.g., D5-00

lA5: 4 Byte Communication (4BS) Telegram — e.g., A5-20-01

For more information, see http://tools.enocean-alliance.org/EEPViewer.

Communication is established between the gateway and an EnOcean device through a pairing

process in which the device is put into learn mode and a "learn in" or "learn out" packet is sent

from the gateway to the device.

Introduction

6 O3-DINEnOcean Application Guide

Edition 1.0

O3-DIN EnOcean Gateway Specifications

The following table lists the specifications of the EnOcean gateway in O3 firmware version 4.13:

Gateway Capacity lUp to 32 devices per EnOcean radio

with device numbers in the range

01–32. Device SV instances in the

33–99 range are not supported.

lUp to 8 EnOcean-capable O3 Hubs

(O3-HUB-02-E8 or O3-HUB-O2-E9)

connected to an O3-DIN-CPU

controller or up to 2 EnOcean-

capable O3 Hubs connected to an

O3-DIN-SRC controller or 1 CON-

ENOC connected to either type of

O3-DIN controller.

lUp 32 EnOcean devices per O3 Hub

or CON-ENOC. With 8 O3 Hubs, a

total of 256 EnOcean devices are

possible.

lRecommend less than 13 points

per EnOcean device.

EnOcean Data Units Frame packet (physical layer),

subtelegram (data link layer), telegram

(network layer).

EnOcean Equipment Profiles 27 FIL object EEPs are included in the

firmware.

BACnet Objects Analog Value, Binary Value, Character

String Value

Introduction

Auto Mapping/Discovery lSupports auto learn feature for

inputs

lSupports one click learn out, three

click learn out, custom 4BS, and

4BS Variant 3 learn out for outputs

lAllows manual addressing

Supported EnOcean Devices l868 MHz (Europe) or 902 MHz

(North America) EnOcean input

(read) devices

l868 MHz (Europe) or 902 MHz

(North America) EnOcean output

(write) devices

EnOcean Communication Protocol Supports ESP3 (EnOcean Serial Protocol

3.0). Does not support older ESP

versions (e.g., ESP2).

Communication lCANbus (O3BUS) using the NET3

port (O3 Hub)

lRS-485 serial at 38400 baud over

NET1/2/3 (CON-ENOC)

Getting Started

This section covers the following topics:

lSetting Up an EnOcean Network

lSetting Up the O3-DIN EnOcean Gateway

Setting Up an EnOcean Network

Before installing EnOcean devices, conduct a site survey to assess optimal placement of

sensors and receivers.

To conduct a site survey:

1. Obtain a floor plan of the space.

2. Mark the locations of fire protection walls, staircases, elevator shafts, restrooms, server

rooms, and any other areas of the building that may block radio signals.

3. Using a compass, draw a circle around each proposed receiver location (where you plan to

install an O3 Hub or CON ENOC device). The circle represents the effective radio signal

range. Each circle should cover approximately 20 m (66 ft) and overlap as little as possible

with other circles.

EnOcean sensors should be located within a 10 m (33 ft) radius of the receiver. Ideally, the

wireless signal should have an unobstructed line-of-sight path to the receiver. It should not

cross any of the marked areas. For more details, see https://www.enocean.com/en/support.

As sensors are installed, conduct field tests with a handheld radio signal strength meter at each

receiver location and verify that the signal is properly received. In some cases, you may need to

8 O3-DINEnOcean Application Guide

Edition 1.0

Getting Started

move the sensors, change antenna positions, or add repeaters to achieve the desired result. As

each receiver location is verified, record the signal strength measurements on the floor plan.

Setting Up the O3-DIN EnOcean Gateway

The O3-DIN EnOcean Gateway requires a controller and an EnOcean receiver. The controller

can be an O3-DIN-CPU or an O3-DIN-SRC. The receiver can be an EnOcean-capable O3 Hub

(O3-HUB-02-E8 or O3-HUB-O2-E9) or a CON-ENOC adapter.

O3 Hub devices communicate with O3-DIN controllers over an O3BUS (CAN-based) network.

CON-ENOC devices communicate with O3-DIN controllers over an RS-485 connection at 38400

bps.

lThe O3 DIN-CPU controller can support up to 8 O3 Hub devices or 1 CON-ENOC.

lThe O3-DIN-SRC controller can support up to 2 O3 Hub devices or 1 CON-ENOC.

lYou cannot use O3 Hubs and CON-ENOCs together.

To set up an O3-DIN EnOcean Gateway with one or more O3 Hubs:

1. Shut off power to the controller.

2. Connect the O3 Hub’s O3BUS port to the controller’s NET3 port.

3. Connect the O3 Hub’s PWR input to PWR OUT 1 on an O3 DIN-CPU controller or to an

external 24 VDC power supply.

4. If you are connecting only one O3 Hub to the O3BUS network, leave the device address as

the default setting (2). If you are connecting more than one O3 Hub, wire the hubs in a daisy

chain and set each hub to a unique address between 2 and 9. The total length of the O3BUS

network must not exceed 70 m (230 ft).

5. The O3BUS network must be terminated at both ends. O3 Hubs and the latest O3-DIN

controllers have a built-in termination switch. Set the switch to TERM on the device at each

end of the daisy chain. (Older O3-DIN controllers need a 120 Ω termination resistor across

the NET3 port pins for termination.)

6. Turn on power to the controller and the O3 Hub(s). If an O3 Hub is being powered by the

controller (that is, it is connected to PWR OUT 1 on an O3 DIN-CPU), in enteliWEB,

command the BO1 object on the controller to On.

To set up an O3-DIN EnOcean Gateway with a CON-ENOC, connect the CON-ENOC to the

controller’s RS-485 port (NET1, NET2, or NET3 on an O3-DIN-CPU; NET1 on an O3-DIN-SRC).

For more information, refer to the product installation guides on support.deltacontrols.com.

Configuring Input Devices

This section covers the following topics:

lConfiguring Input Devices Using an O3 Hub

lConfiguring Input Devices Using a CON-ENOC

lManually Pairing an EnOcean Device

lResetting Pairing

Configuring Input Devices Using an O3 Hub

To configure EnOcean input devices using an O3 Hub:

1. In enteliWEB, open the NP3 object on the controller, set the Protocol Type to CANbus, save

the change, then activate the change (Device Actions > Activate Network Change).

2. Create object BV30s030 ("Enable EnOcean") to enable the EnOcean radio in the O3 Hub,

replacing s with the hub's rotary switch address (2–9), then command the object to On. If

you are using multiple hubs, create this BV object for each hub.

3. To verify that EnOcean is enabled, open the controller’s IOM object. You should see a new

virtual port representing the EnOcean network hosted by the O3 Hub. For example,

3200000.

4. Create an SV object for the EnOcean network. The object instance follows the format

3s00000, where s is the address of the O3 Hub. For example, if the address is 2, create

SV3200000. If the address is 9, create SV3900000. If you are using multiple hubs, create a

network SV object for each hub.

5. Create an SV object for each EnOcean input device (up to 32 per O3 Hub). The object

instance follows the format 3sDD000, where s is the address of the O3 Hub and DD is the

number of the EnOcean device in the range 01 to 32. For example, if the O3 Hub address is

2 and the number you've assigned to the EnOcean device is 01, create SV3201000.

The device number (

) is a number that you arbitrarily assign to the EnOcean device

to identify it. It is distinct from the device address/ID obtained during pairing, which is

a hexadecimal value.

6. Associate a mapping file with each device SV object.

10 O3-DINEnOcean Application Guide

Edition 1.0

Other manuals for EnOcean O3-DIN

Table of contents

Other DELTA GROUP Gateway manuals

DELTA GROUP

DELTA GROUP EnOcean O3-DIN User guide

Popular Gateway manuals by other brands

LST

LST M500RFE-AS Specification sheet

Kinnex

Kinnex Media Gateway quick start guide

2N Telekomunikace

2N Telekomunikace 2N StarGate user manual

Mitsubishi Heavy Industries

Mitsubishi Heavy Industries Superlink SC-WBGW256 Original instructions

ZyXEL Communications

ZyXEL Communications ZYWALL2 ET 2WE user guide

Telsey

Telsey CPVA 500 - SIP Technical manual

RTA

RTA 460A-NNA4 Product user guide

Shaw

Shaw Gateway HDPVR user manual

ABB

ABB VSN900 Commissioning manual

Commander

Commander Pulse owner's manual

2N Telekomunikace

2N Telekomunikace ATEUS EasyGate 501309E manual

NETGEAR

NETGEAR C6300BD installation guide

Amit

Amit CDW531AM user guide

HMS

HMS Netbiter EasyConnect EC150 user manual

Huawei

Huawei EchoLife HG620 user guide

AT&T

AT&T U-verse 3801 Replacement self-installation guide

Logic IO

Logic IO RTCU MX2 turbo Technical manual

Suttle

Suttle MediaMAX MXM-521 installation instructions