Intesis 700 Series User manual

IN701-KNX Series
INTESIS PROTOCOL TRANSLATOR WITH KNX, SERIAL, AND IP SUPPORT
USER MANUAL
Version 1.2
Publicaon date 2023-01-09
ENGLISH

Copyright © 2022 Intesis
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. 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. General Introducon ................................................................................................................ 4
4. Modbus Server to KNX ............................................................................................................. 5
4.1. Specic Introducon ......................................................................................................... 5
4.2. Funconality ................................................................................................................... 5
5. KNX to Modbus Client .............................................................................................................. 6
5.1. Specic Introducon ......................................................................................................... 6
5.2. Funconality ................................................................................................................... 6
6. BACnet Server to KNX .............................................................................................................. 8
6.1. Specic Introducon ......................................................................................................... 8
6.2. Funconality ................................................................................................................... 8
7. KNX to BACnet Client .............................................................................................................. 10
7.1. Specic Introducon ........................................................................................................ 10
7.2. Funconality .................................................................................................................. 10
8. ASCII Server to KNX ................................................................................................................ 11
8.1. Specic Introducon ........................................................................................................ 11
8.2. Funconality .................................................................................................................. 11
9. Gateway Capacity ................................................................................................................... 13
10. KNX Interface ....................................................................................................................... 14
10.1. Descripon ................................................................................................................... 14
10.2. Points Denion ............................................................................................................ 14
11. Modbus Interface ................................................................................................................. 15
11.1. General Descripon ....................................................................................................... 15
11.2. Modbus Server Interface ................................................................................................. 15
11.2.1. Descripon ........................................................................................................... 15
11.2.2. Funcons Supported ............................................................................................... 15
11.2.3. Modbus RTU ......................................................................................................... 16
11.2.4. Modbus TCP .......................................................................................................... 16
11.2.5. Modbus Server Interface Points Denion .................................................................. 17
11.3. Modbus Client Interface .................................................................................................. 17
11.3.1. Descripon ........................................................................................................... 17
11.3.2. Points Denion .................................................................................................... 18
12. BACnet Interface .................................................................................................................. 19
12.1. General Descripon ....................................................................................................... 19
12.2. BACnet Client ................................................................................................................ 20
12.2.1. Descripon ........................................................................................................... 20
12.2.2. Points Denion .................................................................................................... 21
12.3. BACnet Server ............................................................................................................... 22
IN701-KNX Series
USER MANUAL Version 1.2

12.3.1. Descripon ........................................................................................................... 22
12.3.2. BACnet IP ............................................................................................................. 23
12.3.3. BACnet MSTP ........................................................................................................ 23
13. ASCII Interface ..................................................................................................................... 24
13.1. Descripon ................................................................................................................... 24
13.2. ASCII Serial ................................................................................................................... 24
13.3. ASCII TCP ...................................................................................................................... 24
13.4. Address Map ................................................................................................................ 24
13.5. Points Denion ............................................................................................................ 25
13.6. Messages ..................................................................................................................... 26
14. Mounng ............................................................................................................................ 27
15. Connecons ......................................................................................................................... 28
15.1. Power Supply ................................................................................................................ 29
15.2. Connecon Diagrams for each Applicaon .......................................................................... 30
15.3. Connecon to KNX ......................................................................................................... 35
15.4. Connecon to BACnet .................................................................................................... 35
15.5. Connecon to Modbus ................................................................................................... 36
15.6. Connecon to ASCII ........................................................................................................ 37
15.7. Console and USB Connecons .......................................................................................... 38
16. Set-up Process with the Conguraon Tool ............................................................................... 39
16.1. Prerequisites ................................................................................................................. 39
16.2. Intesis MAPS: Conguraon and Monitoring Tool ................................................................. 39
16.2.1. Introducon .......................................................................................................... 39
16.2.2. Template Selecon ................................................................................................. 40
16.2.3. Connecon Tab ...................................................................................................... 40
16.2.4. Conguraon Tab ................................................................................................... 41
16.2.5. Signals Tab ............................................................................................................ 41
16.2.6. Receive/Send Tab ................................................................................................... 41
16.2.7. Diagnosc ............................................................................................................. 42
17. Technical Specicaons ......................................................................................................... 43
18. Dimensions .......................................................................................................................... 44
IN701-KNX Series
USER MANUAL Version 1.2

1. Order Codes
ORDER CODE LEGACY ORDER CODE
IN701KNX1000000 INMBSKNX1000000 INKNXMBM1000000 INBACKNX1000000 INKNXBAC1000000 -
IN701KNX2500000 INMBSKNX2500000 INKNXMBM2500000 INBACKNX2500000 INKNXBAC2500000 -
IN701KNX6000000 INMBSKNX6000000 INKNXMBM6000000 INBACKNX6000000 INKNXBAC6000000 INASCKNX6000000
IN701KNX1K20000 INMBSKNX1K20000 INKNXMBM1K20000 INBACKNX1K20000 INKNXBAC1K20000 -
IN701KNX3K00000 INMBSKNX3K00000 INKNXMBM3K00000 INBACKNX3K00000 INKNXBAC3K00000 INASCKNX3K00000
PRODUCT NAME ORDER CODE DESCRIPTION INTESIS MAPS TEMPLATE APPLICATION
IN701-KNX IN701KNXxxx*0000
Intesis Protocol Translator
with KNX, Serial, and IP
Support
IN-MBS-KNX KNX to Modbus server
IN-KNX-MBM Modbus client to KNX
IN-BAC-KNX KNX to BACnet server
IN-KNX-BAC BACnet client to KNX
IN-ASCII-KNX KNX to ASCII server
*xxx denes the Intesis gateway capacity.
Order Codes IN701-KNX Series
USER MANUAL Version 1.2 Page 1 of 44

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 electric
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.
Use SELV-rated NEC class 2 or limited power source (LPS) power supply.
Supply always a correct voltage to power the gateway. See Technical Specicaons (page 43).
Respect the expected polarity of power and communicaon cables when connecng them to the gateway.
CAUTION
Only an authorized installer is allowed to replace the baery. There's a risk of explosion if the baery
is replaced by an incorrect type. Dispose of used baeries according to local legislaon.
Safety instrucons in other languages can be found at hps://intesis.com/docs/manuals/v6-safety
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.
IN701-KNX Series General Informaon
Page 2 of 44 USER MANUAL Version 1.2

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.
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 IN701-KNX Series
USER MANUAL Version 1.2 Page 3 of 44

3. General Introducon
This Intesis® gateway allows you to integrate Serial and IP protocols to KNX easily.
This document describes the available applicaons for this gateway:
• KNX TP to Modbus® TCP & RTU Server
• Modbus TCP & RTU Client to KNX TP
• KNX TP to BACnet®/IP & MSTP Server
• BACnet/IP & MSTP Client to KNX TP
• KNX TP to ASCII IP & Serial Server
IMPORTANT
This document assumes that the user is familiar with KNX, BACnet, Modbus, and ASCII technologies
and their technical terms.
NOTE
Some secons provide general informaon common to all applicaons, while others highlight
specic dierences, capacies, or limitaons.
In general terms, you must have a KNX installaon or device on one side and a BACnet, Modbus, or ASCII
installaon or device on the other side (only one at a me).
IMPORTANT
The Intesis gateway can act as a server or client for BACnet and Modbus but only as a server for
ASCII.
As always, the conguraon process is fast and easy:
1. Launch the conguraon tool.
2. Select the template.
3. Connect the Intesis gateway to the PC.
4. Adjust the conguraon and signals to your project.
5. Send the conguraon to the gateway.
And you are ready to go!
IN701-KNX Series General Introducon
Page 4 of 44 USER MANUAL Version 1.2

4. Modbus Server to KNX
4.1. Specic Introducon
This secon describes the integraon of KNX systems into Modbus RTU and/or Modbus TCP systems using the
Modbus server to KNX applicaon of the Intesis gateway.
This integraon allows a Modbus control system to access the groups, objects, and associated devices of KNX
systems as if they were part of the Modbus system itself and vice versa.
The gateway acts as a Modbus TCP or RTU server device in its Modbus interface, allowing read/write points from
the Modbus client devices, and oering these points' values through its KNX interface, acng as one more KNX
device of the system.
The gateway conguraon is carried out through the conguraon tool.
Figure 1. Integraon of KNX TP devices into Modbus RTU or Modbus TCP control and monitor systems
4.2. Funconality
From the KNX system point of view, aer starng the gateway or performing a KNX bus reset, the Intesis gateway
polls the KNX signals and stores the received values in its memory, ready to be served to the Modbus system
when requested. It also listens for any KNX telegram related to the internal points congured in it and acts
accordingly to the conguraon of the related points.
From the Modbus system point of view, aer starng it, the gateway listens for any read or write request, serves
any read request, or performs any wring request of its internal points received from the Modbus system. The
values received from Modbus become available to be read by the KNX system and vice versa.
In the gateway, each Modbus point is associated with a KNX group address so that the KNX system sees
the whole Modbus system as if it was one more KNX device with the same conguraon and operaon
characteriscs.
When a Modbus point changes, the gateway sends a write telegram to the associated group address in the KNX
bus.
When the gateway receives a telegram from a KNX group address associated with a Modbus point, it sends a
message to the corresponding Modbus device to perform the related acon.
Modbus Server to KNX IN701-KNX Series
USER MANUAL Version 1.2 Page 5 of 44

5. KNX to Modbus Client
5.1. Specic Introducon
This secon describes the integraon of Modbus RTU installaons into KNX systems using the KNX to Modbus
client applicaon of the Intesis gateway.
This integraon allows a KNX control system or device to access the signals and resources of Modbus systems as
if they were part of the KNX system and vice versa.
The gateway acts as a Modbus RTU client device in its Modbus interface, reading/wring points from the
Modbus server devices by automac connuous polling. The gateway oers these points' values through its KNX
interface, acng as one more KNX device of the system.
The gateway conguraon is carried out through the conguraon tool.
Figure 2. Integraon of Modbus RTU or TCP devices into KNX control and monitoring systems
5.2. Funconality
From the Modbus system point of view, aer starng it, the Intesis gateway connuously reads the Modbus RTU
service devices, updang all the points' values received in its memory.
From the KNX system point of view, aer starng the gateway or performing a KNX bus reset, the Intesis gateway
polls the KNX signals and stores the received values in its memory, ready to be served to the Modbus system
when requested. It also listens for any KNX telegram related to the internal points congured in it and acts
accordingly to the conguraon of the related points.
In the gateway, each Modbus point is associated with a KNX group address so that the KNX system sees
the whole Modbus system as if it was one more KNX device with the same conguraon and operaon
characteriscs.
When a Modbus point changes, the gateway sends a write telegram to the associated group address in the KNX
bus.
When the gateway receives a telegram from a KNX group address associated with a Modbus point, it sends a
message to the corresponding Modbus device to perform the related acon.
IN701-KNX Series KNX to Modbus Client
Page 6 of 44 USER MANUAL Version 1.2

When polling the Modbus devices, if a non-response is detected, the corresponding virtual signal inside the
gateway will be acvated to indicate the communicaon error as a KNX group address.
Funconality IN701-KNX Series
USER MANUAL Version 1.2 Page 7 of 44

6. BACnet Server to KNX
6.1. Specic Introducon
This secon describes the integraon of KNX installaons into BACnet MSTP or BACnet IP compable devices and
systems using the BACnet server to KNX applicaon of the Intesis gateway.
This integraon allows a BACnet-based control system to access the signals and resources of KNX systems as if
they were part of the BACnet system itself and vice versa.
The gateway acts as a BACnet IP server or BACnet MSTP device in its BACnet interface, allowing other BACnet
devices to perform subscripon (COV) requests and readings/wrings to its internal points. From the KNX point
of view, the gateway emulates a KNX device.
The gateway conguraon is carried out through the conguraon tool.
Figure 3. Integraon of KNX devices into BACnet IP or BACnet MS/TP control and monitoring systems
6.2. Funconality
From the KNX system point of view, aer starng the gateway or performing a KNX bus reset, the Intesis gateway
polls the KNX signals and stores the received values in its memory, ready to be served to the BACnet system
when requested. It also listens for any KNX telegram related to the internal points congured in it and acts
accordingly to the conguraon of the related points.
From the BACnet system point of view, aer starng it, the gateway listens for any subscripon (COV) request,
serves any polling request, or performs any wring request of its internal points received from the BACnet
system. The values received from BACnet are immediately wrien in the associated KNX communicaon object if
allowed by the KNX sengs.
In the KNX part, one main group address and dierent listening group addresses can be dened for every point.
This way, every point can be addressed using its main group address and the other specied listening addresses.
Any change in a point in the gateway with the “T” ag acvated (in the KNX part) will force the transmission of
this point value with the corresponding telegram to the KNX system.
Any point with the “W” ag acvated (in the KNX part) can be wrien from the KNX system at any moment.
IN701-KNX Series BACnet Server to KNX
Page 8 of 44 USER MANUAL Version 1.2

Any point with the “R” ag acvated (in the KNX part) can be read from the KNX system at any moment.
Any point with the “Ri” ag acvated (in the KNX part) will be read aer every reset of the gateway.
Funconality IN701-KNX Series
USER MANUAL Version 1.2 Page 9 of 44

7. KNX to BACnet Client
7.1. Specic Introducon
This secon describes the integraon of BACnet MSTP and BACnet IP installaons into KNX systems using the
KNX to BACnet client applicaon of the Intesis gateway.
This integraon allows a KNX system to access the signals and resources of a BACnet system as if they were part
of the KNX system itself and vice versa.
From the BACnet point of view, the gateway acts as a BACnet client device, so it can subscribe (COV) or perform
periodic polling and wrings on congured BACnet objects. The BACnet points’ values are available through its
KNX interface, acng in the KNX system as one more KNX device.
The gateway conguraon is carried out through the conguraon tool.
Figure 4. Integraon of BACnet IP or MSTP devices into KNX control and monitoring systems
7.2. Funconality
From the BACnet system point of view, aer starng it, the gateway subscribes to congured BACnet points or
reads them connuously from their respecve BACnet server devices, updang in its memory the received value
of their Present_Value property.
Each Present_Value is associated with a KNX group object that, in turn, is associated with one or more KNX group
addresses.
When a KNX object changes, it is transmied to the KNX system with its corresponding group address.
Likewise, when a change is received in a write-enabled KNX group object, the change is wrien to the
Present_Value property of the corresponding BACnet object associated with it (using the WriteProperty BACnet
service).
Therefore, the Intesis gateway performs as a single KNX device in the KNX system, oering communicaon
objects to access the BACnet objects of the congured external BACnet devices.
When polling BACnet server devices, if a non-response is detected, the corresponding virtual signal inside the
gateway will be acvated to indicate the communicaon error to the KNX system as a KNX group object.
IN701-KNX Series KNX to BACnet Client
Page 10 of 44 USER MANUAL Version 1.2

8. ASCII Server to KNX
8.1. Specic Introducon
This secon describes the integraon of KNX installaons into ASCII serial (EIA-232 or EIA-485) or ASCII IP
compable devices and systems using the ASCII Server to KNX applicaon of the Intesis gateway.
This integraon aims to make KNX system signals and resources accessible from any programmable system
capable of reading/wring simple text messages through EIA-232 or EIA-485 serial port or Ethernet TCP/IP port
(for example, Extron, LiteTouch systems).
In its KNX interface, the Intesis gateway acts as a KNX device, reading/wring points from other KNX devices and
oering these points' values through its ASCII interface using simple ASCII messages.
The gateway conguraon is carried out through the conguraon tool.
Figure 5. Integraon of KNX devices into ASCII IP or ASCII serial control and monitoring systems
8.2. Funconality
From the KNX system point of view, aer starng the gateway or performing a KNX bus reset, the Intesis gateway
polls the KNX signals and stores the received values in its memory, ready to be served to the ASCII system when
requested. It also listens for any KNX telegram related to its congured internal points and acts accordingly to the
conguraon of the related point.
From the ASCII system point of view, aer starng it, the gateway listens for any read or write request, serves any
read request, or performs any wring request of its internal points received from the ASCII system. The values
received from ASCII become available to be read by the KNX system and vice versa.
In the gateway, each ASCII point is associated with a KNX group address, so the KNX system sees the whole ASCII
system as if it was one more KNX device, with the same conguraon and operaon characteriscs.
When an ASCII point changes, the gateway sends a write telegram to the associated group address in the KNX
bus.
ASCII Server to KNX IN701-KNX Series
USER MANUAL Version 1.2 Page 11 of 44

When the gateway receives a telegram from a KNX group address associated with an ASCII point, it sends a
message to the corresponding ASCII device to perform the related acon.
IN701-KNX Series Funconality
Page 12 of 44 USER MANUAL Version 1.2

9. Gateway Capacity
Table 1. For Modbus server to KNX
Element 100 version 250 version 600 version 1200 version 3000 version
Maximum number of KNX communicaon objects 100 250 600 1200 3000
Maximum number of KNX main group addresses 100 250 600 1200 3000
Maximum number of KNX associaons 200 500 1200 2400 6000
Type of Modbus client devices supported Those supporng Modbus protocol communicaon over TCP/IP and RTU (EIA-485 and
EIA-232)
Number of Modbus client devices supported One client device per RTU node
Up to 5 TCP connecons
Table 2. For KNX to Modbus Client
Element 100 version 250 version 600 version 1200 version 3000 version
Maximum number of KNX communicaon objects 100 250 600 1200 3000
Maximum number of KNX main group addresses 100 250 600 1200 3000
Maximum number of possible KNX associaons 200 500 1200 2400 6000
Type of Modbus server devices supported Those supporng Modbus protocol communicaon over TCP/IP and RTU (EIA-485)
Number of Modbus server devices supported Up to 255 Devices per Node (RTU and TCP)
Up to 5 TCP connecons
Table 3. For BACnet server to KNX
Element 100 version 250 version 600 version 1200 version 3000 version
Maximum number of BACnet objects 100 250 600 1200 3000
Maximum number of BACnet subscripons (COV)
requests
200 500 1200 2400 6000
Maximum number of KNX main group addresses 100 250 600 1200 3000
Maximum number of KNX associaons 200 500 1200 2400 6000
Type of BACnet devices supported Those supporng communicaon with BACnet IP and MS/TP
Table 4. For KNX to BACnet Client
Element 100
version
250
version
600
version
1200
version
3000
version
Maximum number of communicaon objects 100 250 600 1200 3000
Maximum number of main group addresses 100 250 600 1200 3000
Maximum number of KNX associaons 200 500 1200 2400 6000
Type of BACnet devices supported Those supporng communicaon with BACnet IP and MS/TP
Maximum number of BACnet devices 256
Table 5. For ASCII server to KNX
Element 100 version 250 version 600 version 1200 version 3000 version
Maximum number of KNX main group addresses 100 250 600 1200 3000
Maximum number of KNX associaons 200 500 1200 2400 6000
Maximum number of ASCII registers 100 250 600 1200 3000
ASCII link layers supported Those supporng communicaon with ASCII client with simple messages through a
TCP/IP or serial connecon (EIA-232 and EIA-485)
Gateway Capacity IN701-KNX Series
USER MANUAL Version 1.2 Page 13 of 44

10. KNX Interface
10.1. Descripon
The KNX interface of the gateway connects directly to the KNX bus performing as one more device in the KNX
system. In this way, the gateway can receive, manage, and send all telegrams related to its conguraon to the
KNX bus.
When the gateway receives write telegrams of KNX group addresses associated with internal datapoints, it sends
the corresponding messages to the internal system, keeping both systems synchronized at every moment.
When the gateway detects a change in a signal of the other side's protocol, it sends a write telegram to the KNX
bus (addressed with the group address associated with the corresponding group object), keeping both systems
synchronized at every moment.
Since the gateway connuously checks the KNX bus status, if a bus drop-down is detected, for example, due to a
failure in the bus power supply, once the KNX bus is restored, the gateway will send read telegrams to all group
objects marked with "Ri." The behavior of each point in the gateway is determined by the ags congured for the
point.
10.2. Points Denion
Every internal communicaon object has the following KNX properes:
Property Descripon
Descripon Descripve informaon about the communicaon object or signal.
Signal Signal descripon. Only for informave purposes (it facilitates the idencaon of the signal).
DPT KNX data type used to code the signal value. It will depend on the type of signal associated with the external system in every
case. In some integraons, it is selectable while, in others, it is xed due to the intrinsic characteriscs of the signal.
Group KNX group to which the point is associated. It is also the group to which the read (R), write (W), transmit (T), update (U), and
read on init (Ri) ags are applied. It is the sending group.
Addional
addresses
Addresses allowed to write on the group object, apart from the main group address.
RRead. If this ag is acvated, read telegrams of this group address will be accepted.
Ri Read on Init. If this ag is acvated, the object will trigger the corresponding read request (on the associated group address)
on inializaon.
WWrite. If this ag is acvated, write telegrams on this group object will be accepted.
TTransmit. If this ag is acvated, when the group object value changes due to a change in the external system, a write telegram
of the associated group address will be sent to the KNX bus.
UUpdate. If this ag is acvated, update telegrams (response to read telegrams) on this group object will be accepted.
Acve If acvated, the point will be acve in the Intesis gateway; if not, its behavior will be as if it was not dened. This property
allows deacvang points without deleng them, keeping them for future use if needed.
IN701-KNX Series KNX Interface
Page 14 of 44 USER MANUAL Version 1.2

11. Modbus Interface
11.1. General Descripon
The Modbus protocol is an applicaon-layer messaging protocol developed by Modicon in 1979. It is used to
establish master-slave/client-server communicaon between intelligent devices over dierent types of buses or
networks. The Intesis gateway supports Modbus TCP and RTU.
Modbus is a request/reply protocol and oers services specied by funcon codes. Modbus funcon codes are
elements of Modbus request/reply PDUs (Protocol Data Unit).
11.2. Modbus Server Interface
11.2.1. Descripon
The gateway acts as a server device in its Modbus interface, which can be:
• The Ethernet port for Modbus TCP.
• The EIA-485/EIA-232 ports for Modbus RTU.
NOTICE
Modbus RTU and TCP modes can be acve in the gateway one at a me or both simultaneously.
To access the gateway's points and resources from a Modbus client device, you must specify as Modbus register
addresses those congured inside the gateway corresponding to the signals on the eld device protocol.
11.2.2. Funcons Supported
NOTICE
This part is common for both Modbus TCP and Modbus RTU.
Table 6. Modbus funcons
#Funcon Read/Write
01 Read Coils R
02 Read Discrete Inputs R
03 Read Holding Registers R
04 Read Input Registers R
05 Write Single Coil W
06 Write Single Register W
15 Write Mulple Coils W
16 Write Mulple Registers W
If poll records are used to read or write more than one register, the range of addresses requested must contain
valid addresses; if not, the Intesis gateway will return the corresponding Modbus error code.
All registers are of 2 bytes, even if they are associated with signals of bit type on theKNX side. Its content is
expressed in MSB .. LSB.1
Modbus error codes are fully supported. They are sent whenever a non-valid Modbus acon or address is
required.
1MSB: most signicant bit; LSB: less signicant bit
Modbus Interface IN701-KNX Series
USER MANUAL Version 1.2 Page 15 of 44

11.2.3. Modbus RTU
Using the conguraon tool, you can set these parameters:
• Baud rate: 1200, 2400, 4800, 9600, 19200, 38400, 56700 and 115200 bps
• Data Bits: 8 bits
• Parity: none, even, or odd
• Stop Bits: 1 and 2 bits
• Modbus server address
• Physical connecon (EIA-232 or EIA-485)
IMPORTANT
• EIA-232 connector uses RX, TX, and GND lines.
• EIA-485 connector uses B-, A+, and SNGD.
11.2.4. Modbus TCP
Modbus TCP communicaon is characterized basically by the embedding of the Modbus RTU protocol into
TCP/IP frames, which allows faster communicaon and a longer distance between client and server devices in
comparison with RTU communicaon over a serial line. Another benet is using common TCP/IP infrastructure in
buildings and transming over WAN or the internet. It also allows the coexistence of one or more clients and, of
course, one or more server devices in a given network, all interconnected through a TCP/IP-based network.
Use the conguraon tool to congure the IP sengs of the gateway (DHCP status, own IP, netmask, and default
gateway) and the TCP port.
NOTE
The default port is 502.
IN701-KNX Series Modbus Server Interface
Page 16 of 44 USER MANUAL Version 1.2