Ekinex EK-BN1-TP Instruction sheet

Gateway configuration manual
PROFINET Slave -
KNX TP
EK-BN1-TP

Gateway configuration manual
Profinet Slave/KNX TP – EK-BN1-TP
Revision 1.0.2 - Update: 10/12/2018 Configuration manual
© EKINEX S.p.A. – All rights reserved Page 2
Indice
Scope of the document.......................................................................................................................................3
1Product description........................................................................................................................................3
1.1 Main functions........................................................................................................................................4
1.2 Technical data ........................................................................................................................................4
1.3 Supply ....................................................................................................................................................5
1.4 System requirements for configuration software ...................................................................................5
1.1 Certifications ..........................................................................................................................................5
2Switching, display and connection elements.................................................................................................6
3Configuration and commissioning .................................................................................................................8
4Profinet protocol general information ............................................................................................................9
4.1 Tecnology...............................................................................................................................................9
4.2 Profinet CBA ..........................................................................................................................................9
4.3 Profinet IO ..............................................................................................................................................9
4.4 Addressing .............................................................................................................................................9
4.5 Real-time (RT) .....................................................................................................................................10
4.6 Isochronous real-time (IRT) .................................................................................................................10
5Configuration software................................................................................................................................. 11
5.1 Memory image structure ......................................................................................................................12
5.2 Creating a new project or modifying a saved project...........................................................................13
5.3 Software Options .................................................................................................................................14
5.4 Communication parameters.................................................................................................................15
5.5 KNX communication object configuration ............................................................................................17
5.6 Profinet registers configuration ............................................................................................................19
5.7 Configuration update............................................................................................................................20
6Warning........................................................................................................................................................23
7Other information.........................................................................................................................................23

Gateway configuration manual
Profinet Slave/KNX TP – EK-BN1-TP
Revision 1.0.2 - Update: 10/12/2018 Configuration manual
© EKINEX S.p.A. – All rights reserved Page 3
Scope of the document
This document describes the gateway (protocol converter) Profinet Slave – KNX TP. The gateway finds its
ideal applicaton in the integration of KNX devices over an Ethernet network in a Profinet-based automation
system (e.g.: Siemens PLC) for homes and buildings. This product belongs to a broad line of ekinex®
gateways designed to meet the needs for integration of the building automation most widely used protocols,
based on serial, Ethernet or proprietary infrastructures. For further informations about the available technical
solutions, please visit www.ekinex.com.
1 Product description
The ekinex® Profinet Slave EK-BN1-TP gateway is a KNX modular unit for panel mounting. It allows you to
exchange informations with one master devices over an Ethernet network through Profinet protocol. The
ekinex gateway acts as Profinet slave. The informations exchanged over the Profinet network are updated
over the KNX network by means of a twisted pair (TP) communication cable.
The device manages a two-way data stream: the Profinet registers can be cyclically read and their value
sent as a communication object over the KNX TP network through a multicast communication to configured
group addresses. The data update over the KNX network can be done cyclically and/or on event of change
of the data acquired by the Profinet network.
Likewise, the ekinex gateway can make requests to cyclically readings KNX communication objects or
acquire their values during data exchange over the bus. Cyclically or on event of change of the
communication objects, data are written on the Profinet registers of one or more configured devices.
As for KNX communication, 1-bit, 1-byte, 2-byte and 4-byte communication objects can be acquired: internal
conversion functions allow you to convert the informations from and to 16-bit floating point values (DPT
9.xxx).
Configuration is performed through a PC application software which communicates through the integrated
Ethernet port. The application software CGEKBN1TP is available for download at www.ekinex.com.

Gateway configuration manual
Profinet Slave/KNX TP – EK-BN1-TP
Revision 1.0.2 - Update: 10/12/2018 Configuration manual
© EKINEX S.p.A. – All rights reserved Page 4
1.1 Main functions
The gateway acts as a bidirectional protocol converter. Data streams are the following:
• Profinet network – Register writing: the writing command is issued to the gateway by the Profinet
master. The values of the read registers are stored in a 1440-byte volatile memory buffer (“Profinet
image memory”).
• KNX TP network – Sending of writing multicasting frames to configured group addresses. Data can
be sent cyclically over the bus (configurable refresh time), on event of change of the data contained
in the “Profinet memory image”, or both cyclically and on change. Internal conversion functions to the
most common types of KNX Datapoints are present.
• KNX TP network – Multicasting frame listening from configured group addresses (with selectable
filters on the area or network of interest) or cyclical sending of read request frames. The values of
the acquired communication objects are stored in a 1440-byte volatile memory buffer (“KNX image
memory”). This buffer is independent from the “Profinet image memory” buffer.
• Profinet network – Register reading from one or more KNX slave devices by Profinet master’s
request.
1.2 Technical data
Characteristic
Value
Power supply
8…24 Vac
12…35 Vdc
Power Absorption
At 24 Vdc: 3,5 VA
Application area
dry indoor environment
Environmental conditions
• Operating temperature: - 40 ... + 85°C
• Stock temperature: - 25 ... + 55°C
• Transportation temperature: - 25 ... + 70°C
• Relative humidity: 93% non-condensing
Programming elements
1 pushbutton and 1 LED (red) on the front
Display elements
4 status LEDs + 1 Ethernet connector LED
Configuration elements
1 1-way microswitches
• Microswitch A: OFF normal mode; ON Boot mode
Safety class
II
Installation
35 mm DIN rail (according to EN 60529)
Protection degree
IP20
Dimensions (WxHxD)
82 x 75 x 35 mm
Profinet/Ethernet interface (IEEE 802.3)
Connector
RJ45, minimum cable category: 5E
KNX TP interface
Communication port
KNX TP (twisted pair), 9600 baud, electrically isolated from power supply and RS485
communication port
Power supply
SELV 30 Vdc through bus KNX
Current absorption from bus
< 13 mA

Gateway configuration manual
Profinet Slave/KNX TP – EK-BN1-TP
Revision 1.0.2 - Update: 10/12/2018 Configuration manual
© EKINEX S.p.A. – All rights reserved Page 5
1.3 Supply
The supply includes the device and terminal blocks to connect to the KNX bus. An instruction sheet is also
supplied within the package.
1.4 System requirements for configuration software
Configuration and commissioning of the ekinex® gateway must be performed using the application program
CGEKBN1TP, available for download at www.ekinex.com.
The PC where the application program is installed must meet the following requirements:
• Desktop o laptop PC with Ethernet IEEE 802.3 port.
• 32/64 bit operating system, Microsoft Windows® XP, 7, 8.0, 8.1 e 10.
.NET Framework 4.0 system library installation is required.
1.5 Certifications
Compliance with the European directives is certified by the CE symbol on the product label and on the
documentation.
i

Gateway configuration manual
Profinet Slave/KNX TP – EK-BN1-TP
Revision 1.0.2 - Update: 10/12/2018 Configuration manual
© EKINEX S.p.A. – All rights reserved Page 6
2 Switching, display and connection elements
The device is equipped with a pushbutton and a KNX programming LED, with a status LED and terminal
blocks for KNX network connection. A port for RJ45 connector for Profinet network connection and device
configuration via Ethernet as well as one 1-way microswitches are also present.
Figure 1 - Switching, display and connection elements
1) KNX bus line terminal blocks
2) KNX programming pushbutton
3) KNX programming LED
4) Power supply terminal blocks
5) 1-way microswitch A
6) Ethernet port
7) Ethernet port LED
8) Device satus LED
9) Profinet communication LED
10) KNX communication LED
11) Device error LED
ON
1 2
8...24 Vac
+V 0V
POWER S.
12...35 Vdc
ETHERNET
Dev.
Line
Area
KNX
PROFINET
Device state
EK-BN1-TP
PROFINET
/ KNX TP Converter
Failure
1
2
5
4
6
7
8
9
10
11
3

Gateway configuration manual
Profinet Slave/KNX TP – EK-BN1-TP
Revision 1.0.2 - Update: 10/12/2018 Configuration manual
© EKINEX S.p.A. – All rights reserved Page 7
Command elements
• Pushbutton that switches between normal mode and KNX physical address programming.
1-way microswitches
• A - OFF: normal mode active. ON: Boot mode active
Display elements
The device can run according to two operating modes: Normal mode (configuration loaded, Profinet and
KNX communication running) and Boot mode (no configuration or still loading configuration).
LED
Normal mode
Boot mode
Green LED (8) – Device status Slow blinking (~1 Hz)
ON: device on
OFF: device off
Yellow LED (9) – Profinet communication Blinks when a frame is received on the
Ethernet port
Fast blinking: no configuration
Very slow blinking (~0,5 Hz): loading
configuration.
Yellow LED (10) – KNX communication Blinks when a frame is received.
Fast blinking: no configuration
Very slow blinking (~0,5 Hz): loading
configuration.
Yellow LED (11) – Device error
ON: at least one Profinet request did not
get a correct answer
OFF: no error
Fast blinking: no configuration
Very slow blinking (~0,5 Hz): loading
configuration.
Green LED (7) – Ethernet port
ON: Ethernet connector plugged
OFF: Ethernet connector unplugged
ON: Ethernet connector plugged
OFF: Ethernet connector unplugged
Red LED (3) – KNX programming
ON: physical address programming mode
on
OFF: physical address programming mode
off
Fast blinking: no configuration
Very slow blinking (~0,5 Hz): loading
configuration.
In the current version of the device, both KNX physical address programming and
configuration download must be performed through the configuration program: for KNX
physical address please refer to “Communication parameters” paragraph, “ID Device”
parameter.
i

Gateway configuration manual
Profinet Slave/KNX TP – EK-BN1-TP
Revision 1.0.2 - Update: 10/12/2018 Configuration manual
© EKINEX S.p.A. – All rights reserved Page 8
3 Configuration and commissioning
The device configuration requires the following tools:
•The documentation of the Profinet master
•The physical parameters of the Ethernet communication for BACnet IP (IP address, subnet mask,
gateway, port, delays)
•CGEKBN1TP application software to properly configure the gateway
•Knowledge of the ETS automation project, with particular attention to communication objects and
group addresses passing on the bus during the multicast communication between sensors and
actuators.
Configuration and commissioning of the ekinex® gateway require specialized skills about
KNX networks and knowledge of the specific ETS automation project. In order to acquire
such skills, it is essential to attend trainings and workshops organized at KNX-certified
training centers. For further information: www.knx.it.
i

Gateway configuration manual
Profinet Slave/KNX TP – EK-BN1-TP
Revision 1.0.2 - Update: 10/12/2018 Configuration manual
© EKINEX S.p.A. – All rights reserved Page 9
4 Profinet protocol general information
Profinet (Process Field Net) is a communication protocol based on Industrial Ethernet according to IEEE
802.xx directive.
4.1 Tecnology
There are three different protocol levels:
•TCP/IP for Profinet CBA, with about 100ms of reaction time
•RT (Real-time) protocol for applications based on Profinet IO and Profinet CBA, with up to 10ms
cycle time
•IRT (Isochronous Real-time) for applications based on Profinet IO in systems with cycle time inferior
to 1ms.
4.2 Profinet CBA
A Profinet CBA (Component Based Automation) system consists of several automation components. The
components are described through a PCD file (Profinet Component Description) written in XML language.
The basic idea of Profinet CBA is that an automation system can be divided into completely stand-alone
subsystems but with an identical or slightly different structure. Every component is usually controlled by a
specific number of inputs. Inside the component, a control program performs the component’s specific
function and generates he corresponding outputs, which are then sent to another controller.
4.3 Profinet IO
The peripheral interfacing is implemented by Profinet IO protocol.
Profinet IO defines the whole data exchange between master and slave devices, besides the parameter
settings and diagnostics. Profinet IO is a protocol designed to facilitate a fast data exchange between
Ethernet-based field devices and is ideal for applications with cycle time not greater than 10ms.
A Profinet IO based system consists of the following devices:
•An IO controller, which controls the communication (master)
•Field IO devices (slaves), monitored and controlled by the master
•An IO supervisor, tipically a networked PC software, which manages the parameter settings and
slave diagnostics.
The characteristics of an IO device (slave) are described in a GSD file (General Station Description) written
in XML language, issued by the device manufacturer. The GSD file gives the supervisor the tools tools to
plan the configuration of the Profinet IO system.
4.4 Addressing
Each module in a Profinet network has three addresses:
•A MAC address (physical address)
•An IP address
•A device name, e.g. a name which identifies the device at a logical level inside the system
configuration
MAC and IP are addresses typical of TCP/IP based devices. The MAC address changes only if the device is
replaced, while IP is a dynamic address. The device name is a static address.

Gateway configuration manual
Profinet Slave/KNX TP – EK-BN1-TP
Revision 1.0.2 - Update: 10/12/2018 Configuration manual
© EKINEX S.p.A. – All rights reserved Page 10
4.5 Real-time (RT)
In Profinet IO protocol, process data and alarms are always transmitted in real-time (RT). RT, in Profinet, is
based on IEEE and IEC specifications, which allow the execution of real time tasks only for a limited time
within the bus cycle time.
RT communication is the base for Profinet IO data exchange. Real time data are treated with a greater
priority than TCP/IP or UDP/IP data; this kind of data exchange allows to achieve cycle times inferior to 1ms.
4.6 Isochronous real-time (IRT)
IRT enabled devices can perform a data exchange with cycle time from hundreds of microseconds to few
milliseconds. The main difference between IRT and RT is that IRT communication is more deterministic: in
this latter one, it is possible to determine with precision the cycle starting time. Following cycles can have a
maximum jitter of 1 microsecond, which make IRT communication ideal for motion control applications.