HMS Networks Intesis IN700-485 Series User manual

IN700-485 Series
INTESIS PROTOCOL TRANSLATOR WITH SERIAL AND IP SUPPORT
USER MANUAL
Version 1.0
Publicaon date 2022-10-27
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
2.4. Terminology .................................................................................................................... 3
3. General Introducon ................................................................................................................ 4
4. BACnet Server to Modbus Client ................................................................................................ 5
4.1. Specic Gateway Introducon ............................................................................................. 5
4.2. Funconality ................................................................................................................... 5
5. Modbus Server to BACnet Client ................................................................................................ 6
5.1. Specic Gateway Introducon ............................................................................................. 6
5.2. Funconality ................................................................................................................... 6
6. ASCII Server to BACnet Client .................................................................................................... 7
6.1. Specic Gateway Introducon ............................................................................................. 7
6.2. Funconality ................................................................................................................... 7
7. Gateway Capacity .................................................................................................................... 8
8. BACnet Interface ..................................................................................................................... 9
8.1. General Descripon .......................................................................................................... 9
8.2. BACnet Client .................................................................................................................. 9
8.3. Descripon ..................................................................................................................... 9
8.4. Points Denion .............................................................................................................. 11
8.5. BACnet Server ................................................................................................................. 11
8.6. Descripon .................................................................................................................... 11
8.7. BACnet IP ....................................................................................................................... 12
8.8. BACnet MSTP .................................................................................................................. 13
9. Modbus Interface ................................................................................................................... 14
9.1. General Descripon ......................................................................................................... 14
9.2. Modbus Server Interface ................................................................................................... 14
9.3. Descripon .................................................................................................................... 14
9.4. Funcons Supported ........................................................................................................ 14
9.5. Modbus RTU .................................................................................................................. 15
9.6. Modbus TCP ................................................................................................................... 15
9.7. Modbus Server Interface Points Denion ........................................................................... 16
9.8. Modbus Client Interface ................................................................................................... 16
9.9. Descripon .................................................................................................................... 16
9.10. Points Denion ............................................................................................................ 17
10. ASCII Interface ..................................................................................................................... 18
10.1. Descripon ................................................................................................................... 18
10.2. ASCII Serial ................................................................................................................... 18
10.3. ASCII TCP ...................................................................................................................... 18
10.4. Address Map ................................................................................................................ 18
10.5. Points Denion ............................................................................................................ 19
10.6. Messages ..................................................................................................................... 19
IN700-485 Series
USER MANUAL Version 1.0

11. Connecons ......................................................................................................................... 21
11.1. Power Supply ................................................................................................................ 21
11.2. Connecon Diagrams for each Applicaon .......................................................................... 22
11.3. Connecon to Modbus ................................................................................................... 25
11.4. Connecon to BACnet .................................................................................................... 26
11.5. Connecon to ASCII ........................................................................................................ 27
11.6. Console and USB Connecons .......................................................................................... 28
12. Set-up Process with the Conguraon Tool ............................................................................... 29
12.1. Prerequisites ................................................................................................................. 29
12.2. Intesis MAPS: Conguraon and Monitoring Tool ................................................................. 29
12.2.1. Introducon .......................................................................................................... 29
12.2.2. Template Selecon ................................................................................................. 30
12.2.3. Connecon Tab ...................................................................................................... 30
12.2.4. Conguraon Tab ................................................................................................... 31
12.2.5. Signals Tab ............................................................................................................ 31
12.2.6. Receive/Send Tab ................................................................................................... 31
12.2.7. Diagnosc ............................................................................................................. 32
13. Technical Specicaons ......................................................................................................... 33
14. Dimensions .......................................................................................................................... 34
IN700-485 Series
USER MANUAL Version 1.0

1. Order Codes
ORDER CODE LEGACY ORDER CODE
IN7004851000000 INMBSBAC1000000 INBACMBM1000000 -
IN7004852500000 INMBSBAC2500000 INBACMBM2500000 -
IN7004856000000 INMBSBAC6000000 INBACMBM6000000 INASCBAC6000000
IN7004851K20000 INMBSBAC1K20000 INBACMBM1K20000 -
IN7004853K00000 INMBSBAC3K00000 INBACMBM3K00000 INASCBAC3K00000
PRODUCT NAME ORDER CODE DESCRIPTION INTESIS MAPS TEMPLATE APPLICATION
IN700-485 IN700485xxx*0000 Intesis Protocol Translator
with Serial and IP Support
IN-BAC-MBM Modbus client to BACnet server
IN-MBS-BAC BACnet client to Modbus server
IN-ASCII-BAC BACnet client to ASCII server
*xxx denes the Intesis gateway capacity.
Order Codes IN700-485 Series
USER MANUAL Version 1.0 Page 1 of 36

2. General Informaon
2.1. Intended Use of the User Manual
This manual contains the main features of the Intesis gateway and the instrucons for its appropriate installaon,
conguraon, and operaon.
The contents of the manual should be brought to the aenon of any person who installs, congures, or
operates the gateway or 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 lead to serious harm to your health and also
may seriously damage the gateway and/or any other equipment connected to it.
Only technical personnel, following these instrucons and the country legislaon for the installaon of electric
equipment, is allowed to 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 power supply, if needed, and communicaon) 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 33) ).
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.
IN700-485 Series General Informaon
Page 2 of 36 USER MANUAL Version 1.0

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.
2.4. Terminology
Some terms generalize specic nomenclature to clarify some explanaons.
Term Descripon
Intesis gateway
Gateway
General term for this device
Applicaon Specic conguraon that allows the gateway to emulate a parcular protocol translator
Device or installaon What you're about to integrate
Control system System that controls the mechanical and electrical equipment of a building, for example, a Building Management System
(BMS).
Conguraon tool Soware used to congure the gateway
Terminology IN700-485 Series
USER MANUAL Version 1.0 Page 3 of 36

3. General Introducon
This Intesis® gateway allows you to integrate Serial and IP protocols easily.
This document describes the available applicaons for this gateway:
• Modbus® TCP & RTU Client to BACnet®/IP & MSTP Server
• BACnet/IP & MSTP Client to Modbus TCP & RTU Server
• BACnet/IP & MSTP Client to ASCII IP & Serial Server
IMPORTANT
This document assumes that the user is familiar with 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 BACnet, Modbus, or ASCII control and monitoring system on one side and a
Modbus or BACnet 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!
IN700-485 Series General Introducon
Page 4 of 36 USER MANUAL Version 1.0

4. BACnet Server to Modbus Client
4.1. Specic Gateway Introducon
This secon describes the integraon of Modbus RTU and/or Modbus TCP installaons into BACnet IP or MSTP
control and monitoring systems using the BACnet Server to Modbus Client applicaon.
This integraon allows a Modbus control system to access the signals and resources of BACnet systems as if they
were part of the Modbus system itself and vice versa.
The gateway conguraon is carried out through the conguraon tool.
Figure 1. Integraon of Modbus RTU or TCP devices into BACnet IP or MSTP control and monitoring systems
4.2. Funconality
From the Modbus point of view, the gateway connuously polls the installaon or devices, storing in its memory
the values of the points that you previously congured to be read. On the other hand, from the BACnet point of
view, the control and monitoring system reads and writes those stored points.
This is possible because, inside the gateway, all Modbus registers of the server devices are associated with
BACnet objects. This makes the BACnet control and monitoring system perceive the Modbus installaon (all the
server devices) as if it were a single BACnet device.
When the gateway polls the Modbus devices, if a non-response is detected, the corresponding virtual signal
inside the gateway will be acvated, indicang the communicaon error to the BACnet system.
The gateway has two EIA-485 ports for Modbus RTU integraon: Port A and Port B. This funcon allows you to
integrate up to 64 devices (32 in each port) with no addional repeaters in the network.
This funconality is disabled when BACnet MSTP is selected in Intesis MAPS, leaving only Port A available for
Modbus RTU connecvity and Port B for BACnet MSTP devices.
By default, Port A is congured for Modbus RTU and Port B for BACnet MSTP.
BACnet Server to Modbus Client IN700-485 Series
USER MANUAL Version 1.0 Page 5 of 36

5. Modbus Server to BACnet Client
5.1. Specic Gateway Introducon
This secon describes the integraon of BACnet MSTP and BACnet IP devices or installaons into Modbus RTU or
TCP systems using the Modbus server to BACnet client applicaon of the Intesis gateway.
This integraon allows a Modbus system to access the signals and resources of BACnet devices as if they were
part of the Modbus system itself and vice versa.
The gateway conguraon is carried out through the conguraon tool.
Figure 2. Integraon of BACnet IP or MSTP devices into Modbus TCP or RTU control and monitoring systems
5.2. Funconality
From the BACnet point of view, the gateway connuously polls the installaon or devices, storing in its memory
the values of the points that you previously congured to be read. With the change of value (COV) system, the
gateway can also subscribe to congured BACnet points, automacally receiving their values when they change.
On the other hand, from the Modbus point of view, the control and monitoring system reads and writes those
stored points.
This is possible because, inside the gateway, all BACnet objects of the server devices are associated with Modbus
registers. This makes the Modbus control and monitoring system perceive the BACnet installaon (all the server
devices) as if it were a single Modbus device.
When the gateway polls the BACnet devices, if a non-response is detected, the corresponding virtual signal inside
the gateway will be acvated, indicang the communicaon error to the Modbus system as error registers.
IN700-485 Series Modbus Server to BACnet Client
Page 6 of 36 USER MANUAL Version 1.0

6. ASCII Server to BACnet Client
6.1. Specic Gateway Introducon
This secon describes the integraon of BACnet/IP and MSTP devices into ASCII IP or Serial control and
monitoring systems using the ASCII Server to BACnet Client applicaon.
This integraon allows any ASCII system to access the signals and resources of BACnet devices as if they were
part of the system itself and vice versa.
The gateway conguraon is carried out through the conguraon tool.
Figure 3. Integraon of BACnet/IP or MSTP devices into ASCII TCP/IP or Serial control and monitoring systems
6.2. Funconality
From the BACnet point of view, the gateway connuously polls the installaon or devices, storing in its memory
the values of the points that you previously congured to be read. On the other hand, from the ASCII point of
view, the control and monitoring system reads and writes those stored points.
This is possible because, inside the gateway, all BACnet objects of the server devices are associated with ASCII
objects. This makes the ASCII control and monitoring system perceive the BACnet installaon (all the server
devices) as if it were a single ASCII device.
When the gateway polls the BACnet devices, if a non-response is detected, the corresponding virtual signal inside
the gateway will be acvated, indicang the communicaon error to the ASCII system.
ASCII Server to BACnet Client IN700-485 Series
USER MANUAL Version 1.0 Page 7 of 36

7. Gateway Capacity
Table 1. For BACnet server to Modbus client
Element 100 version 250 version 600 version 1200 version 3000 versions
Type of BACnet devices Those supporng communicaon with BACnet/IP and MSTP
Maximum number of BACnet objects 100 250 600 1200 3000
Maximum number of BACnet Subscripons (COV)
requests
200 500 1200 2400 6000
Type of Modbus server devices Those supporng communicaon over Modbus TCP/IP and RTU (EIA-485)
Number of Modbus server devices supported by the
device
Up to 5 Modbus TCP nodes/devices
Up to 255 Modbus RTU devices per TCP/RTU node
Table 2. For Modbus server to BACnet client
Element 100 version 250 version 600 version 1200 version 3000 version
Type of BACnet devices Those supporng communicaon with BACnet/IP and MSTP
Maximum number of BACnet devices 256
Maximum number of Modbus Registers 100 250 600 1200 3000
Modbus link layers supported Those supporng communicaon over Modbus TCP/IP and RTU (EIA-485)
Table 3. For ASCII server to BACnet client
Element 100 version 250 version 600 version 1200 version 3000 version
Type of BACnet devices Those supporng communicaon with BACnet/IP and MSTP
Maximum number of BACnet devices 256
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 (EIA-232/EIA-485) connecon
IN700-485 Series Gateway Capacity
Page 8 of 36 USER MANUAL Version 1.0

8. BACnet Interface
8.1. General Descripon
BACnet is a solid standard with many detailed concepts, but for this manual purposes, we will focus on the two
most fundamental concepts:
• BACnet client, which is the device that sends service requests to the server.
• BACnet server, which is the device that performs the requested service and reports the result back to the
client.
BACnet server devices are represented in the form of devices holding objects. Usually, every physical device
corresponds to a logical one. The objects can be of dierent types depending on the data and funconality they
represent: Analog input, Analog output, Digital input, etc.
NOTE
• Output objects are objects meant to be wrien in the direcon BACnet network to the device.
• Input objects are meant to oer status informaon of the BACnet device.
• Value objects are bidireconal.
Every object has dierent properes. The most meaningful one is the Present_Value property, which indicates
the real value of the object. Also, the gateway uses this property to read and write values. Every object of the
same type in a device is idened with its associated object instance.
8.2. BACnet Client
8.3. Descripon
The gateway implements a single BACnet object of its own: its BACnet Device Object, which contains its BACnet
Device Idener and basic properes of the gateway as a BACnet device (name, rmware version, etc.).
NOTICE
When acng as a client device, the Intesis gateway is classied under the device prole of a BACnet
Applicaon Specic Controller (B-ASC). For further details, check out the product website for the
BACnet client PIC statements.
The gateway emulates a client device in the BACnet system.
BACnet Interface IN700-485 Series
USER MANUAL Version 1.0 Page 9 of 36

These are the possible BACnet objects supported by the Intesis gateway:
Object Type Property Descripon
Analog Input Present Value Analog signal, for example, Ambient temperature
Analog Output Present Value Analog signal
Analog Value Present Value Analog signal, for example, Temperature set point
value
Binary Input Present Value Digital signal, for example, ON/OFF status
Binary Output Present Value Digital signal, for example, ON/OFF command
Binary Value Present Value Digital signal, for example, ON/OFF status/
command
Mulstate
Input
Present Value Mulstate signal, for example, Working mode
status
Mulstate
Output
Present Value Mulstate signal
Mulstate
Value
Present Value Mulstate signal, for example, Working mode
command
Accumulator Present Value
Loop Present Value
Every signal is idened with its associated Device + Object Type + Object Instance.
IMPORTANT
Though BACnet IP and BACnet MSTP physical layers are supported, only one physical layer can be
used at a me, i.e., if communicang to BACnet using BACnet IP, BACnet MSTP cannot be used, and
vice versa.
NOTE
Using the conguraon tool, it’s possible to scan the BACnet network for available devices and
their objects, which can later be directly added to your conguraon. This feature facilitates the
conguraon process, avoiding entering them manually.
IN700-485 Series Descripon
Page 10 of 36 USER MANUAL Version 1.0

8.4. Points Denion
Every point dened in the Intesis gateway has the following BACnet features associated with it:
Feature Descripon
BACnet Device BACnet device to which the point belongs (a list of 256
BACnet devices can be dened in the Intesis gateway).
For every BACnet device dened, a virtual signal is
created automacally in the gateway to report the
communicaon status with the BACnet device. Like the
rest of the points, this signal is also available from the
other protocol's interface.
BACnet object type • AI: Analog Input
• AO: Analog Output
• AV: Analog Value
• DI: Digital Input
• DO: Digital Output
• DV: Digital Value
• MI: Mulstate Input
• MO: Mulstate Output
• MV: Mulstate Value
• LOOP: Loop
• ACUM: Accumulator
IMPORTANT
Please read the documentaon of
the BACnet devices you're willing to
integrate to know their object types.
BACnet object instance BACnet object instance for the point on the external
BACnet device.
IMPORTANT
Please read the documentaon of
the BACnet devices you're willing to
integrate to know their object types.
8.5. BACnet Server
8.6. Descripon
NOTICE
When the Intesis gateway acts as a server device, it is classied under the device prole of a BACnet
Advanced Applicaon Controller (B-AAC). For further details, check out the product website for the
BACnet client PIC statements.
Using the conguraon tool, you can congure the object type associated with the signal on the other protocol.
Points Denion IN700-485 Series
USER MANUAL Version 1.0 Page 11 of 36

To facilitate the translaon towards BACnet, the following object type opons are available:
Object Type ID
Analog-Input 0
Analog-Output 1
Analog-Value 2
Binary-Input 3
Binary-Output 4
Binary-Value 5
Calendar 6
Device 8
Mulstate-Input 13
Mulstate-Output 14
Mulstate-Value 19
Nocaon-Class 15
Schedule 17
Trend-Log 20
Trend-Log-Mulple 27
Every signal of the Intesis gateway can have several objects. These objects and their properes can be congured
with the conguraon tool.
Depending on the eld device protocol, you can dene the signals using one of the following opons:
•Conguring them manually for each or mulple signals at the me.
•Imporng a le with the signals of the eld devices.
• Scanning the network of the devices if this is supported.
Example 1. Signals compability
You can choose an object from the BACnet server column that is compable with this signal. For example, a
writable register in the Modbus device can be an output object type on the BACnet server side; a readable and
writable register can be a value object type, etc.
NOTICE
The conguraon tool provides default templates that make this signals assignment process easier.
Also, you only have to click the Check table buon on the boom right corner of the window to
know if everything is correct or if there's some mistake. The project is also automacally checked
before you transfer it to the gateway.
All objects denion, BIBBs, and details about the implementaon can be found on the BACnet server PICS on
the product website.
8.7. BACnet IP
The UDP communicaon port is the main setup parameter for BACnet IP, besides basic IP sengs (IP, netmask,
default gateway). The Intesis gateway uses the 47808 (0xBAC0) port by default, which you can change through
the conguraon tool.
When using BACnet IP, the gateway can also act as a foreign device to communicate with devices in another
network domain. Alternavely, you can set it as a BBMD (Bacnet IP Broadcast Management Device). This
funconality facilitates the communicaon of devices placed in other networks with the devices in the gateway
network.
IN700-485 Series BACnet IP
Page 12 of 36 USER MANUAL Version 1.0

IMPORTANT
BACnet IP and BACnet MSTP communicaon can not be used simultaneously.
8.8. BACnet MSTP
When you choose BACnet MSTP (serial communicaon), you have to use the conguraon tool to associate the
gateway with a MAC address within the MSTP network segment.
Baud rates supported for MSTP line are: 9600, 19200, 38400, 76800, 115200, or Autobauding (autodetect).
Standard wiring guidelines for EIA-485 apply to the BACnet MSTP line.
IMPORTANT
BACnet MSTP and BACnet IP communicaon can not be used simultaneously.
BACnet MSTP IN700-485 Series
USER MANUAL Version 1.0 Page 13 of 36

9. Modbus Interface
9.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).
9.2. Modbus Server Interface
9.3. 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.
9.4. Funcons Supported
NOTICE
This part is common for both Modbus TCP and Modbus RTU.
Table 4. 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 the other protocol's 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
IN700-485 Series Modbus Interface
Page 14 of 36 USER MANUAL Version 1.0

9.5. 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.
9.6. 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.
Modbus RTU IN700-485 Series
USER MANUAL Version 1.0 Page 15 of 36

9.7. Modbus Server Interface Points Denion
The Modbus registers are fully congurable through the conguraon tool; any point in the gateway can be
freely congured with the desired Modbus register address.
Every point dened in the gateway has the following Modbus features associated with it:
Feature Descripon
#Bits • 1 bit
• 16 bits
• 32 bits
Data Coding
Format
• 16/32 unsigned
• 16/32 bits signed (one's complement – C1)
• 16/32 bits signed (two's complement – C2)
• 16/32 bits Float
• 16/32 bits Biields
• Error comm.
Byte Order • Big Endian
•Lile Endian
• Word Inverted Big Endian
• Word Inverted Lile Endian
Register Address The Modbus register address inside the server device for the point.
Bit inside the
register
Bit inside the Modbus register (oponal). The Intesis gateway allows bit decoding from generic
16 bits input/holding Modbus registers.
Some devices use the bit coding into 16 bits input/holding Modbus registers to encode digital
values. These registers are generally accessible using Modbus funcon codes 03 and 04 (read
holding/input registers).
Read/Write 0: Read
1: Write
2: Trigger
9.8. Modbus Client Interface
9.9. Descripon
The Intesis gateway acts as a client device in the Modbus TCP network, Modbus RTU client, or both.
IMPORTANT
Other Modbus devices connected to the network communicang with the gateway must always be
server devices.
The gateway supports communicaon with up to ve Modbus TCP server devices.
For every dened point belonging to a parcular Modbus TCP server device, a server address from 0 to 255
can also be freely congured. This feature oers great exibility for installaons. For example, when integrang
several Modbus RTU server devices connected in a serial line, with an RTU/TCP converter on top of this
serial line, it enables access to the RTU server points through TCP/IP. In this case, the RTU/TCP converter
communicang in TCP idenes the desnaon of the point (server address in the RTU network) by the contents
of the server address eld.
Modbus TCP server devices are characterized by their IP address and predened registers address map. This
address map species the address, type, and characteriscs of the Modbus server device's internal points
(commonly called registers). These registers are accessible using the Modbus TCP protocol.
Communicaon parameters of the Intesis gateway (IP address, netmask, default router address, and TCP port)
are fully congurable to adapt to any IP network and server device.
IN700-485 Series Modbus Server Interface Points Denion
Page 16 of 36 USER MANUAL Version 1.0