HMS Networks Intesis INKNXMBM1000200 User manual

Modbus RTU Client to KNX TP Gateway
USER MANUAL
Version 1.0
Publicaon date 2023-02-16
ENGLISH

Copyright © 2023 Intesis
Important User Informaon
Disclaimer
The informaon in this document is for informaonal purposes only. Please inform HMS Networks of any
inaccuracies or omissions found in this document. HMS Networks disclaims any responsibility or liability for any
errors that may appear in this document.
HMS Networks reserves the right to modify its products in line with its policy of connuous product
development. The informaon in this document shall therefore not be construed as a commitment on the
part of HMS Networks and is subject to change without noce. HMS Networks makes no commitment to update
or keep current the informaon in this document.
The data, examples and illustraons found in this document are included for illustrave purposes and are only
intended to help improve understanding of the funconality and handling of the product. In view of the wide
range of possible applicaons of the product, and because of the many variables and requirements associated
with any parcular implementaon, HMS Networks cannot assume responsibility or liability for actual use
based on the data, examples or illustraons included in this document nor for any damages incurred during
installaon of the product. Those responsible for the use of the product must acquire sucient knowledge in
order to ensure that the product is used correctly in their specic applicaon and that the applicaon meets all
performance and safety requirements including any applicable laws, regulaons, codes and standards. Further,
HMS Networks will under no circumstances assume liability or responsibility for any problems that may arise as
a result from the use of undocumented features or funconal side eects found outside the documented scope
of the product. The eects caused by any direct or indirect use of such aspects of the product are undened and
may include e.g. compability issues and stability issues.

Table of Contents
1. Descripon and Order Codes ..................................................................................................... 1
2. General Informaon ................................................................................................................ 2
2.1. Intended Use of the User Manual ........................................................................................ 2
2.2. General Safety Informaon ................................................................................................ 2
2.3. Admonion Messages and Symbols ..................................................................................... 2
3. Overview ............................................................................................................................... 4
3.1. Inside the Package ............................................................................................................ 4
3.2. Gateway Main Features ..................................................................................................... 4
3.3. General Introducon ......................................................................................................... 4
3.4. Gateway Capacity ............................................................................................................. 5
4. Hardware ............................................................................................................................... 6
4.1. Mounng ........................................................................................................................ 6
4.2. Connecon Procedure and DIP Switch Seng ........................................................................ 7
4.3. LED Indicators .................................................................................................................. 8
4.4. Push Buon .................................................................................................................... 9
4.5. Technical Specicaons .................................................................................................... 10
4.6. Dimensions .................................................................................................................... 10
5. Communicaon Interfaces ....................................................................................................... 11
5.1. KNX Interface ................................................................................................................. 11
5.1.1. KNX Communicaon Objects ...................................................................................... 11
5.1.2. KNX Points Denion ................................................................................................ 12
5.2. Modbus Interface ............................................................................................................ 12
5.2.1. Modbus Points Denion .......................................................................................... 12
6. Conguraon ......................................................................................................................... 14
6.1. Prerequisites .................................................................................................................. 14
6.2. Conguraon Process with the ETS Tool ............................................................................... 14
6.3. General Conguraon Tab ................................................................................................. 15
6.4. Device Tab ..................................................................................................................... 17
6.5. Intesis Modbus Device Manager DCA .................................................................................. 18
6.6. Sending the Conguraon to the Gateway ........................................................................... 20
Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0

1. Descripon and Order Codes
Modbus RTU Client to KNX TP Gateway
ORDER CODE LEGACY ORDER CODE
INKNXMBM1000200 INKNXMBM1000100
Descripon and Order Codes Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0 Page 1 of 20

2. General Informaon
2.1. Intended Use of the User Manual
This manual contains the main features of this Intesis gateway and the instrucons for its appropriate
installaon, conguraon, and operaon.
The contents of this manual should be brought to the aenon of any person who installs, congures, or
operates this gateway or any associated equipment.
Keep this manual for future reference during the installaon, conguraon, and operaon.
2.2. General Safety Informaon
IMPORTANT
Follow these instrucons carefully. Improper work may seriously harm your health and damage the
gateway and/or any other equipment connected to it.
Only technical personnel, following these instrucons and the country legislaon for installing electrical
equipment, can install and manipulate this gateway.
Install this gateway indoors, in a restricted access locaon, avoiding exposure to direct solar radiaon, water, high
relave humidity, or dust.
All wires (for communicaon and power supply, if needed) must only be connected to networks with indoor
wiring. All communicaon ports are considered for indoor use and must only be connected to SELV circuits.
Disconnect power wires before manipulang and connecng them to the gateway.
Respect the expected polarity of power and communicaon cables when connecng them to the gateway.
2.3. Admonion Messages and Symbols
DANGER
Instrucons that must be followed to avoid an imminently hazardous situaon that, if not avoided,
will result in death or severe injury.
WARNING
Instrucons that must be followed to avoid a potenally hazardous situaon that, if not avoided,
could result in death or severe injury.
CAUTION
Instrucon that must be followed to avoid a potenally hazardous situaon that, if not avoided,
could result in minor or moderate injury.
IMPORTANT
Instrucon that must be followed to avoid a risk of reduced funconality and/or damage to the
equipment or to avoid a network security risk.
Modbus RTU Client to KNX TP Gateway General Informaon
Page 2 of 20 USER MANUAL Version 1.0

NOTE
Addional informaon which may facilitate installaon and/or operaon.
TIP
Helpful advice and suggesons.
NOTICE
Remarkable Informaon.
Admonion Messages and Symbols Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0 Page 3 of 20

3. Overview
3.1. Inside the Package
Items included:
• Intesis INKNXMBM1000200 protocol translator gateway
• KSN label
•Installaon sheet
3.2. Gateway Main Features
• Accredited with the main cercaons for electronic equipment, including the ocial KNX cercaon. To
know more, check the website's Technical Documentaon secon.
• Uses KNX standard datapoints (DPTs). This guarantees a smooth integraon in any KNX device or system.
• Programmable with the KNX ocial tool ETS.
• Flexible conguraon of devices and signals.
• Export and import device templates through a DCA for quick integraon.
• Every signal allows arithmec and logical operaons such as mulplicaon, division, equal to, greater than,
etc., to adapt them to the Modbus registers.
• Reduced dimensions (DxWxH): 32x36x92 mm.
• Up to 100 Modbus registers and 205 KNX communicaon objects.
• Up to 100 devices (when installing more than 32 devices, you will need a repeater. This is an inherent
limitaon of the Modbus protocol).
• Two visible LEDs indicate the local operang status.
3.3. General Introducon
This document describes how to integrate Modbus RTU server devices into a KNX TP installaon using the Intesis
Modbus RTU client to KNX TP gateway.
Figure 1. Integraon of Modbus devices into a KNX TP installaon
This gateway allows a KNX TP system to access the signals and resources of Modbus server devices. To do so,
the gateway is connuously polling the Modbus server devices and associates the Modbus signals to the KNX
communicaon objects; this way, the KNX TP system perceives all the Modbus devices as if they were one more
KNX device of the system and vice versa: the Modbus devices perceive the KNX system as if it was one more
Modbus server device of the network.
Modbus RTU Client to KNX TP Gateway Overview
Page 4 of 20 USER MANUAL Version 1.0

3.4. Gateway Capacity
Element 100 version
Modbus interface
Maximum number of Modbus
server devices supported 100 (see note below)
Type of Modbus server devices
supported
Those supporng Modbus protocol
communicaon over RTU (EIA-485)
Modbus addresses range 1 to 255
Maximum number of Modbus
signals 100
KNX interface
Maximum number of
communicaon objects
205 signal objects:
100 status objects
100 control objects
4 error status objects
1 oponal object for heartbeat
Maximum number of KNX
group addresses 700
Maximum number of possible
KNX associaons 700
NOTE
When installing more than 32 devices, you will need a repeater. This is an inherent limitaon of the
Modbus protocol.
Gateway Capacity Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0 Page 5 of 20

4. Hardware
4.1. Mounng
IMPORTANT
Before mounng, please ensure that the chosen installaon place preserves the gateway from direct
solar radiaon, water, high relave humidity, or dust.
IMPORTANT
Ensure the gateway has sucient clearances for all connecons when mounted.
NOTE
Mount the gateway over a DIN rail, preferably inside a grounded metallic industrial cabinet.
NOTE
This gateway’s prole (depth) may be thinner than other devices on the DIN rail. Check the local
regulaons since installing a blanking plate may be necessary to cover the gateway and avoid any
manipulaon through the gap.
DIN rail mounng
The back panel has a groove to t the gateway to the DIN rail using two stac tabs (top side) and a mobile clip
(boom side).
1. Insert the gateway in the upper edge of the DIN rail.
2. Use a screwdriver or similar to pull the boom clip down.
3. Fit the low side of the gateway in the DIN rail and let the clip switch back to its original posion, locking the
gateway to the rail.
4. Make sure the gateway is rmly xed.
Modbus RTU Client to KNX TP Gateway Hardware
Page 6 of 20 USER MANUAL Version 1.0

4.2. Connecon Procedure and DIP Switch Seng
CAUTION
Before connecng the gateway, disconnect the KNX bus from its power supply.
SW1
Use this DIP switch to congure the EIA-485 port:
• Switch 1:
– ON: 120 Ω terminaon acve
– OFF: 120 Ω terminaon inacve (Default)
IMPORTANT
If you install the gateway at one end of the EIA-485 bus, acvate the
terminal resistor funconality by seng switch 1 to the ON posion.
CAUTION
Make sure there are at most two end-of-line resistors on the EIA-485 bus.
Having more than that could cause electrical issues.
• Switches 2 and 3:
– ON: Polarizaon acve (Default)
– OFF: Polarizaon inacve
IMPORTANT
The bus must be polarized only at one point of the line, preferably on the
Client side. To disable the gateway's line polarizaon, set switches 2 and 3
to the OFF posion.
1. Connect the EIA-485 bus to connectors A3 (A+), A2 (B-), and A1 (SNGD) of the gateway’s
Port A.
2. Connect the KNX bus to the connectors + and - of the gateway’s KNX port. Respect the
polarity and use a KNX standard cable.
3. Reconnect the KNX bus to its power supply.
4. Connect all the devices of your installaon (the EIA-485 bus devices) to their power
supplies.
NOTE
This gateway gets the power from the KNX bus itself, so it does not need an external power supply. If
there is a power cut in the bus, the gateway will turn o.
Once the bus is powered again:
• The gateway turns on, keeping its parameter's conguraon.
• It polls the bus and updates all status objects for the Modbus devices connected to it.
Connecon Procedure and DIP Switch Seng Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0 Page 7 of 20

4.3. LED Indicators
There are two LEDs below the DIP switch.
LED ID and color Paern Descripon
KNX programming mode
RED
O Programming mode disabled
Steady On Programming mode enabled
Flashing To locate the device
Power/Modbus acvity
YELLOW
O No power
Steady On Device powered but without communicaon
Slow blinking Invalid answer or no answer received from a server device
Fast blinking Correct package received from a congured server device
Modbus RTU Client to KNX TP Gateway LED Indicators
Page 8 of 20 USER MANUAL Version 1.0

4.4. Push Buon
This buon acvates the gateway's programming mode,
which is needed for some ETS download variants:
•Download All: It downloads the Individual Address,
the Applicaon Program, the Parameters, and the
Group addresses.
•Download Individual Address.
The buon is also needed to use the Unload Applicaon
and Address funcon.
You can read a broader explanaon in these KNX arcles:
Download funcons:
hps://support.knx.org/hc/en-us/arcles/360007474340-Download-funcons
Unload device:
hps://support.knx.org/hc/en-us/arcles/4402998506386-Unload-Device
ETS soware will tell you when to push the buon:
Push Buon Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0 Page 9 of 20

4.5. Technical Specicaons
Enclosure
• Front side: PC (UL 94 V-0)
• Back side: PPO (UL 94 V-0)
• Net dimensions (DxWxH): 32x36x92 mm
Colors:
• Front side: light grey. RAL 7035
• Rear side: black
Mounng DIN rail (35 mm; two modules)
Power Supplied through KNX bus
KNX Port
1 x KNX TP-1 Plug-in terminal block (2 poles)
• 1500 VDC isolaon from other ports
• KNX power consumpon: 11 .. 22 mA
• Voltage rang: 21 .. 32 VDC
Port A
1 x Serial EIA-485 Plug-in screw terminal block (3 poles)
• A1: SNGD (Reference ground or shield)
• A2 (B-)
• A3 (A+)
2500 VDC isolaon from other ports
Push buon Acvates the gateway's programming mode
Operaonal temperature 0°C to +60°C
Operaonal humidity 5 to 95%, no condensaon
SW1
DIP switch for serial EIA-485 conguraon:
• Switch 1:
– ON: 120 Ω terminaon acve
– OFF: 120 Ω terminaon inacve (Default)
• Switches 2 and 3:
– ON: Polarizaon acve (Default)
– OFF: Polarizaon inacve
LED indicators
2 x Onboard LED indicators
• 1 x Power/Port A acvity
• 1 x KNX programming mode
4.6. Dimensions
Modbus RTU Client to KNX TP Gateway Technical Specicaons
Page 10 of 20 USER MANUAL Version 1.0

5. Communicaon Interfaces
5.1. KNX Interface
This Intesis gateway connuously checks the status of the KNX bus. The behavior of each signal point is dened
by the ags you set in the ETS conguraon tool. This means, for instance, that when the communicaon is
restored aer a blackout, the gateway will retransmit the status of all the KNX groups marked as Transmit (T) and
the update groups marked as Update (U).
NOTE
By default, the gateway's physical address is 15.15.255. If you change this value, the gateway will
reboot, keeping all its conguraon parameters and proceeding to poll the bus to update all status
objects for the Modbus devices connected to it.
IMPORTANT
If having communicaon issues in large installaons, check if a line coupler is ltering the telegrams
from/to the Intesis gateway.
5.1.1. KNX Communicaon Objects
Object
number Name Length
Datapoint type Flags
Funcon
DPT_Name DPT_ID R W T U
201 Status_Heartbeat 1 bit State 1.011 R T 1: Acve
202 Status_Error_Alarm 1 bit Alarm 1.005 R T 0: No alarm; 1: Alarm
203 Status_Modbus_Dev_
Error 2 bytes 2 byte signed value 8.xxx R T Address of the last Modbus server device that currently has an error
204 Status_Modbus_Reg_
Error 4 bytes 4 byte unsigned value 12.xxx R T Register address of the last Modbus server device that currently has an error
205 Status_Error_Text 14 bytes Character string
(ISO 9959-1) 16.001 R T
MBM Overload: an electric overload is
detected from the power supply.
Error Text: string message about the error
or the alarm in the format ss::aaaa:ee
• ss: server id (00 .. 3F)
•: funcon code (00 .. 10)
• aaaa: address (0000 .. FFFF)
• ee: excepon code (see tables below)
Table 1. Modbus excepon codes
Code Name Meaning
01 Illegal funcon The funcon code received in the query is not an allowable acon for the server. Example: The funcon code
only applies to newer devices and was not implemented in the selected device.
02 Illegal data address
The data address received in the query is not an allowable address for the server (the combinaon of the
reference number and transfer length is invalid). Example: The submied request aempts to operate on
registers 96, 97, 98, 99, and 100, and there is no register with address 100.
03 Illegal data value A value contained in the query data eld is not an allowable value for the server. This indicates a fault in the
structure of the remainder of a complex request, such as that the implied length is incorrect.
04 Server device failure An unrecoverable error occurred while the server aempted to perform the requested acon.
05 Acknowledge The server is processing the request, but it will require a long me to do so. This response is returned to
prevent a meout error on the client side.
06 Server device busy The server is processing a long–duraon program command. The client should retransmit the message later
when the server is free.
07 Memory parity error The server detected a parity error in the memory when reading the record le. The client may require service
on the server device to retry the request.
Communicaon Interfaces Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0 Page 11 of 20

Code Name Meaning
0A Gateway path
unavailable
The gateway could not allocate an internal communicaon path from the input to the output port for
processing the request. Example: The gateway is miscongured or overloaded
0B Gateway target device
failed to respond The target device does not respond. Example: The target device is not present on the network.
Table 2. Gateway excepon codes
Code Name Meaning
ER0 Unknown error The error type cannot be determined.
ER1 CRC error The cyclic redundancy check has detected an error in the response
structure.
ER2 Recepon length error The response length is not correct.
ER3 Recepon me out No response aer the meout.
5.1.2. KNX Points Denion
The internal datapoints have the following KNX properes:
Property Descripon
Acve
If enabled, this signal will be acve; if not, the behavior will be as if the point was not
dened. This allows you to deacvate points instead of deleng them, so that you can save
those points for future use.
#This is the number of the signal.
Object Name Descripve informaon about the signal. You can edit these names.
DPT This is the KNX data type used to code the signal's value, which depends on the type of signal
associated with the Modbus side.
5.2. Modbus Interface
This Intesis gateway acts as a client device in the Modbus RTU network. Other Modbus devices connected to the
same line and communicang with the Intesis gateway must always be server devices.
The Modbus protocol denes dierent types of funcon codes to read/write the registers of Modbus devices. It
also denes dierent data formats to encode values.
In the Modbus interface, you can congure the data encoding used for 16 bits registers (big-endian or lile-
endian). This is the byte order for data encoding (MSB .. LSB or LSB .. MSB)1. Although the Modbus protocol
species this data encoding as big-endian, it varies depending on the manufacturer and/or the type of server.
5.2.1. Modbus Points Denion
Each signal point dened in the Intesis gateway has the following associated Modbus features:
Feature Descripon
# Server Modbus server address where the point belongs to.
Funcon code
Read funcon
Write funcon
One of the following Modbus data coding formats can be used:
• 1 - Read Coils
• 2 - Read Discrete Inputs
• 3 - Read Holding Registers
• 4 - Read Input Registers
• 5 - Write Single Coil
• 6 - Write Single Register
• 15 - Write Mulple Coils
• 16 - Write Mulple Registers
1MBS: Most Signicant Bit
LSB: Less Signicant Bit
Modbus RTU Client to KNX TP Gateway Modbus Interface
Page 12 of 20 USER MANUAL Version 1.0

Feature Descripon
Data coding
format
One of the following Modbus data coding formats can be used:
• 16/32/48/64 bits unsigned
• 16/32/48/64 bits signed (one's complement - C1)
• 16/32/48/64 bits signed (two's complement - C2)
• 16/32/48/64 bits Float
• 16 bits Biields
Byte order
• Big-endian
•Lile-endian
• World inverted big-endian
• World inverted lile-endian
Register
address
The Modbus register address on the server device for the signal point.
Bit
You can decide where the signal starts in the register (oponal funcon). The gateway
allows bit decoding from generic 16 bits input/holding Modbus registers.
Bit coding into 16-bit input/holding Modbus registers is used to encode digital values
into the registers, being usually accessible using Modbus funcon codes 3 and 4 (read
holding/input registers).
# Bits Number of bits used by the signal.
Deadband Determine the change of value (COV) in a signal value.
Operaon
The following opons are available:
• No operaon
•Arithmec operaons: Operaons that can be applied to Modbus values before
sending them to the KNX control system. The inverse operaon is also applied to
KNX values before sending them to the Modbus installaon.
–Mulply by ( x )
– Divide by ( / )
• Logical operaons: Operaons that can be applied to read-only or write-only signals.
These operaons return “1” when the result matches the condion and “0” when it
doesn’t.
– Is equal ( == )
– Is dierent ( != )
– Is less than ( < )
– Is greater than ( > )
Operaon Value Value for the operaon formula.
Operaon
Denion
It shows the formula applied to the signal and the direcon (from Modbus to KNX or vice
versa).
Figure 2. Points denion window. See the dierent operaon opons in the last three columns
Modbus Interface Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0 Page 13 of 20

6. Conguraon
6.1. Prerequisites
For this integraon, you will need:
• The items supplied by HMS Networks:
– The Intesis gateway
– The gateway documentaon
– The gateway ETS database
• An ETS5 license (version 5.7.7 onwards).
• An operave KNX control system, properly connected to the KNX port of the Intesis gateway.
• The Modbus server device(s) or installaon you are about to integrate, connected to the Port A (EIA-485) of
the Intesis gateway.
• A Windows® computer to run the ETS conguraon tool.
6.2. Conguraon Process with the ETS Tool
This Intesis gateway is ocially cered by KNX. Use the standard KNX conguraon tool ETS to set up the
gateway. You can nd the ETS database for this gateway in the ETS catalog or download it from here.
NOTE
When imporng the gateway to the ETS soware for the rst me, it will show 10 Modbus acve
signals, each congured as a Read and Write signal. You can congure these signals later and adapt
them to your project needs.
Modbus RTU Client to KNX TP Gateway Conguraon
Page 14 of 20 USER MANUAL Version 1.0

6.3. General Conguraon Tab
Access this tab to congure the Modbus connecon parameters and the total number of signals to map.
Figure 3. General conguraon tab
•Read on Init Delay: Determines the me in seconds to wait before all values are uploaded to the KNX network.
IMPORTANT
This seng applies only to objects with the Read on Init ag enabled.
•Time Telegram Rate: Determines the me in milliseconds between telegrams when some data is updated
simultaneously.
•Heartbeat: Acvang this funcon, the device will report that it is online.
•Modbus connecon parameters:
–Baudrate: Denes the communicaon speed for the RTU communicaon (from 1200 to 115200 bps.)
–Data Type: Denes, in this order: the number of bits used for data (8bit), the parity of the communicaon
(None/Odd/Even), and the number of stop bits (1 or 2).
–Response meout: Determines the me in seconds to wait for a reply to a sent request
–Interframe meout: Determines the minimum me between received frame and sent frame.
–Poll Aer Write: Enables or disables a poll for a parcular signal aer sending a write command to it.
–Number of devices: Determines the number of Modbus devices you are integrang.
General Conguraon Tab Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0 Page 15 of 20

NOTE
ETS creates a tab for each device.
–Number of signals: Denes the number of Modbus signals to integrate. Once a signal is dened, ETS
automacally creates one or two KNX objects, depending on the selected funcon. When selecng both
write and read funcons, ETS creates two objects (one status object and one command object); but if you
only select the funcon write or the funcon read, ETS creates one single object (a command object for the
write funcon or a status object for the read funcon).
IMPORTANT
If you try to integrate more than 100 devices or signals, this message will popup:
The boom side of the window shows the Modbus device table, where you can:
• See each device and its name.
• Change the server address.
• Change the number of signals.
NOTE
You can change this from the Device Tab, also.
•Acvate or deacvate each device.
IMPORTANT
The signals of deacvated devices won't be transferred to the gateway.
Modbus RTU Client to KNX TP Gateway General Conguraon Tab
Page 16 of 20 USER MANUAL Version 1.0

6.4. Device Tab
On the top side of this window, you can see the device informaon:
•Device Name
•Device Server Address
•Device Signals Amount: Indicates the number of signals to integrate from the Modbus server device to the
KNX system. You can add up to 100 signals.
NOTE
By default, the list for the rst device shows ten signals. For the rest of the devices, only one signal
is shown. You can add more according to your needs.
•Device Deadband: Determines the minimum change of value (COV) for all signals to update it in the KNX
system.
IMPORTANT
Modifying this general value will overwrite the specic Deadband values of each signal on the
device conguraon page.
Below this informaon, you can see the list of all available KNX objects, their corresponding Modbus registers,
and other relevant parameters for every Modbus server device of the installaon.
Figure 4. Device tab
The rst four columns correspond to the KNX control system side. To know more about each parameter, see KNX
Points Denion (page 12).
The rest of the columns correspond to the Modbus installaon side. To know more about each parameter, see
Modbus Points Denion (page 12).
Device Tab Modbus RTU Client to KNX TP Gateway
USER MANUAL Version 1.0 Page 17 of 20