IntesisBox IBOX-BAC-MBRTU-100 User manual
IntesisBox®BACnet/IP Server
Modbus RTU Master
User's manual
Issue Date: 17/12/2012
r14 eng
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
2 / 27
© Intesis Software S.L. All Rights Reserved.
Information in this document is subject to change without notice. The software described in
this document is furnished under a license agreement or nondisclosure agreement. The
software may be used only in accordance with the terms of those agreements. No part of
this publication may be reproduced, stored in a retrieval system or transmitted in any form
or any means electronic or mechanical, including photocopying and recording for any
purpose other than the purchaser’s personal use without the written permission of Intesis
Software S.L.
Intesis Software S.L.
Milà i Fontanals, 1 bis - 1º
08700 Igualada
Spain
TRADEMARKS
All trademarks and tradenames used in this document are acknowledged to be the copyright of their respective holders.
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
3 / 27
Gateway for the integration of Modbus RTU slave
devices into BACnet/IP control systems.
Models available for this gateway, with their following Order codes:
IBOX-BAC-MBRTU-100
Tiny model supporting connection to up to 254 Modbus slave devices and 110 internal
datapoints.
IBOX-BAC-MBRTU-A
Basic model supporting connection to up to 254 Modbus slave devices and 500 internal
datapoints.
IBOX-BAC-MBRTU-B
Extended model supporting connection to up to 254 Modbus slave devices and 3000 internal
datapoints.
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
4 / 27
INDEX
1. Description ...................................................................................................... 5
1.1 Introduction ................................................................................................. 5
1.2 Functionality................................................................................................. 6
1.3 Capacity of IntesisBox ................................................................................... 7
2. Interfaces........................................................................................................ 8
2.1 BACnet ........................................................................................................ 8
2.2 Modbus ........................................................................................................ 8
3. Quick Setup................................................................................................... 10
4. Connection .................................................................................................... 11
4.1 Power device .............................................................................................. 11
4.2 Connect to Modbus ...................................................................................... 12
4.3 Connect to BACnet ...................................................................................... 12
4.4 Connect to PC (LinkBoxBacnet) ..................................................................... 12
5. LinkBoxBacnet. Configuration & monitoring of IntesisBox BACnet series ................ 14
5.1 Project configuration.................................................................................... 14
5.1.1 Connection configuration........................................................................ 14
5.1.2 Signals configuration ............................................................................. 17
5.1.3 How to configure read/write points .......................................................... 22
5.1.4 Saving the configuration ........................................................................ 24
6. Mechanical & electrical characteristics ............................................................... 26
7. Dimensions.................................................................................................... 27
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
5 / 27
1. Description
1.1 Introduction
This document describes the integration of Modbus RTU Master systems with BACnet
ASHRAE 135 –2001 Annex J - BACnet protocol compatible devices or systems using the
gateway IntesisBox BACnet/IP Server - Modbus RTU Master.
This document assumes that the user is familiar with Modbus and BACnet/IP technology and
technical terms.
From now on, and with the aim of easy the read of this document, the words "gateway" or
“IntesisBox” are used instead of IntesisBox BACnet/IP Server - Modbus RTU Master. Any
other use of the word "gateway" not meaning IntesisBox BACnet/IP Server - Modbus RTU
Master will be specifically indicated.
The aim of this integration is to make accessible Modbus system signals and resources from
a BACnet/IP based control system or device, as if it was a part of the own BACnet system
and vice-versa. For this, the gateway acts as a BACnet/IP Server device in its BACnet
interface, allowing other BACnet/IP devices to perform subscription (COV) requests, and
also read and write its internal points. From the Modbus system point of view, IntesisBox
simulates a Modbus master device, the readings of the Modbus slave device(s) is performed
by IntesisBox by automatic continuous polling.
Figure 1.1 Integration of Modbus and BACnet/IP using IntesisBox BACnet/IP
Server - Modbus RTU Master gateway
Only needed for configuration
IntesisBox
LinkBoxBacnet
Configuration
software
RS232
Ethernet
BACnet/IP
BACnet/IP
system
Modbus
slave
Modbus
slave
Modbus
slave
RS485 (can be also RS232 for single slave connection)
Modbus RTU
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
6 / 27
1.2 Functionality
The integration operation is as follow:
From the Modbus system point of view, after the start up process, IntesisBox reads
continuously the points configured to be read in the Modbus slave devices, and updates in
its memory all the values received from the Modbus system.
From the BACnet system point of view, after the start up process, the gateway listen for any
subscription (COV) request, serves any polling request, or performs any writing request of
its internal points received from BACnet system. The values received from BACnet are
immediately written in the associated register of the corresponding Modbus slave device.
Every one of the Modbus registers in the slave devices is associated to a BACnet object,
with this, all the Modbus system (all the slave devices) is seen as a single BACnet device
with many objects from the BACnet system point of view, each object corresponding to a
Modbus slave/register address.
When a new value is read from Modbus for a given register, the new value is updated in the
gateway's memory and, if this signal is associated to a BACnet active subscription then the
new value will be sent to the subscripted BACnet device(s).
In the continuous polling of the Modbus devices, if a non response of the Modbus device is
detected, the corresponding virtual signal inside IntesisBox will be activated indicating
communication error with the Modbus device. These virtual signals indicating
communication status in real time with the Modbus devices are also accessible from BACnet,
like the rest of the points of IntesisBox.
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
7 / 27
1.3 Capacity of IntesisBox
Element
Tiny
version
Basic
version
Extended
version
Notes
Type of BACnet
devices
Only those supporting BACnet/IP.
Number of BACnet
points
110
500
3000
Maximum number of points that can be
defined in the virtual BACnet device
inside the gateway.
Number of BACnet
subscribers
8
8
8
Maximum number of BACnet
subscribers accepted by the gateway.
Number of BACnet
subscriptions
(COV) requests
220
1000
6000
Maximum number of BACnet
subscriptions (COV) requests accepted
by the gateway.
Type of Modbus
slave devices
Those supporting Modbus protocol.
Communication over RS485 network
(2-Wire) or RS232 point to point.
Modbus
Slave devices
254
254
254
Maximum number of Modbus slave
devices allowed by IntesisBox.
There are different models of IntesisBox BACnet/IP Server - Modbus RTU Master, with
different capacity every one of them.
Tiny model supporting connection to up to 110 internal data points.
Ref.: IBOX-BAC-MBRTU-100.
Basic model supporting connection to up to 500 internal data points.
Ref.: IBOX-BAC-MBRTU-A.
Extended model supporting connection to up to 3000 internal data points.
Ref.: IBOX-BAC- MBRTU-B.
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
8 / 27
2. Interfaces
This section gives the reader an idea on how a Modbus system/installation is integrated with
IntesisBox BACnet. It is not meant to provide an in-depth explanation on how BACnet or
Modbus technology work as understanding the protocol principles is assumed throughout
this document.
The IntesisBox behaves as a regular BACnet device inside the BACnet system integrating all
the KNX devices. Note that each datapoint defined on IntesisBox will have two associated
data types:
One data-type, related to the BACnet/IP protocol of the IntesisBox
And another data-type, related to Modbus side of IntesisBox
Conversions of data values from Modbus to BACnet/IP data-types (and vice versa) are
internally performed at application level of IntesisBox, and keeping the highest possible
level of precision, with the restrictions of the data-type itself. Further detail on behavior and
data-types of the BACnet/IP and Modbus interfaces of IntesisBox is given in the following
sections.
All configuration of IntesisBox BACnet is done using software tool LinkBoxBacnet. This tool,
covered in depth in section 5, is used to define the Modbus and BACnet related parameters
on each of the datapoints defined in IntesisBox.
2.1 BACnet
The IntesisBox integrates all the Modbus devices in a single BACnet device. The
communication with the other BACnet devices is done via the Ethernet port of the gateway
which implements the BACnet ASHRAE 135 –2001 Annex J - BACnet protocol.
The supported BACnet Objects and Building Blocks can be found in the PICS document
available on the web:
http://www.intesis.com/pdf/IntesisBox_BACnet_IP_Server_Modbus_RTU_master_PICS.pdf
Configuration of all BACnet/IP parameters of IntesisBox and their links to Modbus using
LinkBoxBacnet software tool is covered in section 5.1.
2.2 Modbus
Modbus RTU communication is characterised by the co-existence of just one master and one
or more slave devices in a given network, all of them interconnected, and every slave with a
unique address into the network. Different types of networks and network topologies are
allowed. The more commonly used for Modbus RTU communication are: point to point
communication using RS232, and point to multipoint communication using RS485 (2-wire or
4-wire).
IntesisBox acts as the master in the Modbus network, and the other Modbus devices
connected to the network must be always slave devices. Up to 254 slave devices can be
defined in IntesisBox. The types of networks supported by IntesisBox are:
RS485 2-wire (up to 254 slave devices are allowed by IntesisBox, thus up to 254 slave
devices in the same RS485 network can be integrated with just one IntesisBox, installing
additional line repeaters where necessary).
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
9 / 27
RS232 (for single slave integration).
Modbus slave devices are normally characterised by their communication parameters (baud
rate, data bits, parity), some of them sometimes configurable depending on the device, and
their predefined registers address map, this address map specifies the address, type and
characteristics of every internal point (commonly called register) of the Modbus slave
device, these registers being accessible using Modbus RTU protocol.
Communication parameters of IntesisBox's Modbus interface (baud rate, data bits, stop bits,
parity) are fully configurable to adapt to any slave device. Of course IntesisBox and all the
slave devices connected to the Modbus network must use the same communication
parameters.
Modbus RTU protocol defines different types of function codes to use to read/write different
type of registers that can be found in Modbus devices, and also different data formats to
encode values. All these are explained in section 5.1.2
Also the data encoding used for 16 bits registers (big-endian or little-endian) can be
configured in IntesisBox's Modbus interface. This is the byte order for data encoding
(MSB..LSB or LSB..MSB). This data encoding, although is specified as big-endian in Modbus
protocol specification, it varies depending on manufacturer/type of slave device.
All this gives great flexibility to integrate a wide range of Modbus slave devices that can be
found in the market.
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
10 / 27
3. Quick Setup
1. Install LinkBoxBacnet. Details in section 5
2. Install IntesisBox in the desired installation site (DIN rail mounting inside a metallic
industrial cabinet connected to ground is recommended).
3. Power up and connect the communication cables. Details in section 4.
4. Open LinkBoxBacnet, open a project or create a new one. Details in section 5.
5. Connect to the IntesisBox (details in section 5).
6. (optional) Configure the IntesisBox. Details in section 5.1.
7. Check if there is communication in both BACnet and Modbus buses (section 5)
8. The IntesisBox is ready to be used in your system.
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
11 / 27
4. Connection
The device uses a standard enclosure allowing DIN EN60715 TH35 rail mounting. Its plastic
meets standard PC UL 94 V0.
Figure 4.1 Device connection diagram
Ensure proper space for all connectors when mounted.
The items supplied by Intesis Software for this integration are:
IntesisBox BACnet/IP Server - Modbus RTU Master hardware
Console cable. Standard DB9F-DB9M cable 1.8 meter long.
Installation sheet, containing a link to the LinkBoxBacnet software and this
manual.
4.1 Power device
The first step to perform is to power up the device. To do so a power supply working with
any of the voltage range allowed is needed (check section 6). Once connected the ON led
(Figure 4.1) will turn on.
WARNING! In order to avoid earth loops that can damage the gateway and/or any other
equipment connected to it, we strongly recommend:
ON
Power
9 –30 Vdc
Max. 125mA
24 Vac
Max. 127mA
50-60Hz
-+
CMN 24Vac
PC Console
Area .
Line
.
Com
.
.
IntesisBox®
www.intesis.com
Serial Port
(Not used)
IBOX-BAC-MBRTU
BACnet/IP
ETH
10 Base-T
ACT
LNK
Power
PC (LinkBoxBacnet)
BACnet/IP
(Ethernet)
PC
Console
Tx
Rx
MODBUS RTU
EIA458
- + EIA232
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
12 / 27
The use of DC power supplies, floating or with the negative terminal connected to
earth. Never use a DC power supply with the positive terminal connected
to earth.
The use of AC power supplies only if they are floating and not powering any other
device.
4.2 Connect to Modbus
Connect the communication cable coming from the Modbus network to the port marked as
Modbus of IntesisBox (Figure 4.1). Two methods to connect to the Modbus network can be
used:
The RS485 port if the network is RS485 2-wire. Connect the + and the –to the
respective ports in the slave devices (polarity matters)
The RS232 port if the connection is point to point to one single slave.
IntesisBox
Modbus RTU
slave1
DB9 M
RS-232
DB9 F
TX
3
RX
RX
2
TX
GND
5
GND
Table 4.1 Modbus RS232 cable pinout
How to check if there is communication with the Modbus bus is explained in the
LinkBoxBacnet Manual (section 5).
4.3 Connect to BACnet
Connect the communication cable coming from the network hub or switch to the ETH port
(Figure 4.1) of IntesisBox. The cable to be used depends on where the IntesisBox is being
connected:
Connecting directly to a BACnet/IP device: crossover Ethernet UTP/FTP CAT5 cable
Connecting to a hub or switch of the LAN of the building: a straight Ethernet UTP/FTP
CAT5 cable
In case there is no response from the BACnet devices to the frames sent by IntesisBox,
check that they are operative and reachable from the network connection used by
IntesisBox. Check the IntesisBox Ethernet interface sending Pings to its IP address using a
PC connected to the same Ethernet network.
4.4 Connect to PC (LinkBoxBacnet)
This action allows the user to have access to configuration and monitoring of the device
(more information can be found in the LinkBoxBacnet User Manual [section 5]). Two
methods to connect to the PC can be used:
1
Check your Modbus device’s user’s manual provided by its respective manufacturer to know more details about pinout.
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
13 / 27
Ethernet: Using the ETH port (Figure 4.1) of IntesisBox. How to check connectivity is
explained in section 4.3.
Serial cable: To connect the device to the PC the serial cable supplied should be
plugged to the PC console port (Figure 4.1).
The cable is a RS-232 straight cable and its pinout is at explained in Table 4.2.
IntesisBox
PC
DB9 M
RS-232 (Straight)
DB9 F
TX
2
2
RX
RX
3
3
TX
GND
5
5
GND
Table 4.2 Configuration serial cable pinout
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
14 / 27
5. LinkBoxBacnet. Configuration & monitoring of IntesisBox BACnet
series
How to install and use the LinkBoxBacnet is explained in its Manual. It can be found in the
installation folder (if the Software is already installed) or it can be downloaded from the link
that can be found in the installation sheet supplied with the IntesisBox.
In this section only the specific project configuration for IntesisBox BACnet/IP Server -
Modbus RTU Master is going to be explained.
The External Protocol in this IntesisBox is Modbus
5.1 Project configuration
To configure the integration connection parameters, and the points list, click on Config in
the Button Bar (Figure 5.1). The Modbus Configuration window will be opened. For
integrations with a large number of points an alternative CSV based configuration method is
explained in the LinkBoxBacnet Manual.
Figure 5.1 Menu and Button Bar in LinkBoxBacnet
5.1.1 Connection configuration
Two subsets of information are configured using this window, the BACnet/IP parameters of
the IntesisBox, and the parameters of the Modbus interface.
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
15 / 27
Figure 5.2 Configuration: Connection Tab
BACnet/IP interface configuration parameters:
Figure 5.3 BACnet/IP interface Configuration
IP: Enter the IP address for the gateway (supplied by the network administrator).
NetMask: Enter the IP NetMask for the gateway (supplied by the network
administrator).
Gateway: Enter the Default Gateway address (router address) in case the gateway
(IntesisBox) is in a different sub network than other BACnet devices (supplied by the
network administrator). Leave blank if there is no need of router address.
BACnet Port: Enter the BACnet port number used by the gateway (by default
47808, which is BAC0).
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
16 / 27
Device: Enter the BACnet device number for the gateway (must be unique inside
the BACnet system).
Device Name: Select the BACnet device name for the gateway (by default "Modbus
Gateway"). This name will be collected by BACnet browsers among others.
Version: Select the gateway model used: tiny,basic or extended. You can check the
gateway model in the identification given by the device when it connects to
LinkBoxBacnet, it appears in the IntesisBox Communication Console window once
connected to the gateway
IntesisBox_Bacnet_Modbus-100…Tiny model
IntesisBox_Bacnet_Modbus-A…Basic model
IntesisBox_Bacnet_Modbus-B…Extended model
Frimware version: select the gateway firmware version. If not done correctly the
configuration is not going to work
Modbus interface configuration parameters:
Figure 5.4 Modbus interface Configuration
Connection: Type of connection used (RS232 or RS485).
Baud Rate: Baud rate used for the communication.
Data Bits: Data bits used.
Parity: Parity used.
Timeout polling: Timeout (in milliseconds) between two consecutive polling cycles.
Timeout interframe: Inter-frame timeout (in milliseconds), some devices need
inter-frame delay to communicate properly. Increase this timeout if you experience
communication problems with slaves.
Byte order (Modbus endianism): Byte order for data fields inside Modbus telegrams
(LSB..MSB or MSB..LSB). It will depend on the slaves, consult the slave
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
17 / 27
documentation for details. If unknown just try the two possible choices and see if the
read values make sense. This affects to all data fields of all slaves defined.
Devices: List of Modbus slave devices to communicate to. Check the devices you
want to activate. Select a device to configure its properties.
+/- : Use this button to define the number of Modbus slave devices to communicate
to (Up to 254 devices)
For every Modbus device defined, the following properties must be entered:
Name: Enter the device name (optional, just for identification purposes).
Slave #: Enter the slave number configured in the Modbus device.
5.1.2 Signals configuration
Select the Signals tab (Figure 5.5) to configure the signals list (the IntesisBox internal
points). More information about the meaning of the columns can be found in the tables
below.
Every row in the grid corresponds to a signal (point). Signals (rows in the grid) can be
added or deleted selecting the desired row and clicking Add or Delete buttons. Multiple
consecutive rows can be deleted too.
Figure 5.5 Signal list
# (Signal’s number)
Description
Enumeration of the rows in the grid (signals). If clicked on them the whole
row will be selected (
to be used to delete/add rows)
Restrictions
Cannot be edited
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
18 / 27
Dev
Description
Device number to which belongs the point. Referenced to the list of devices
defined in Connection Tab (Figure 5.4)
Values
From 1 to 254
Edit mode
Text edit or AutoEnumeration
Comments
This is not the slave number configured in the Modbus device itself, it is just
the order of the device (from top to bottom) in the devices list
Modbus Code
Description
Modbus function code to be used by IntesisBox to read, to write or to
read/write the point in the slave device.
Values
0- Communication Error
1- Read digital outputs
2- Read digital inputs
3- Read analog registers
4- Read analog inputs
5- Write 1 digital output
6- Write 1 analog register
7- Write multiple digital output
8- Write multiple analog registers
Restrictions
For Read only points function codes 1, 2, 3 or 4 can be used
For write only points, function codes 5, 6, 15 or 16 can be used
For read/write points, see section 5.1.3
Edit mode
Single / Multiple Values selection.
Comments
Consult documentation of Modbus device(s) to integrate for information about function codes
supported to read/write their internal points.
Format
Description
Modbus data format for the point.
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
19 / 27
Values
Generic:
1. 1 bit.
2. 16 bits uns: 16 bits unsigned.
3. 16 bits sig: 16 bits signed. The MSbit represents the sign.
4. 16 bits sig C2:16 bits signed (two’s complement).
5. 32 bits uns: 32 bits unsigned.
6. 32 bits sig: 32 bits signed.
7. 32 bits sig C2: 32 bits signed (two’s complement).
8. 32 bits IEEE: IEEE Standard for Floating-Point Arithmetic (IEEE 754).
9. 32 bits IEEE inv: 32 bits IEEE inverted (LSB..MSB).
10. 32 bits IEEE Winv: 32 bits IEEE word inverted (LSW..MSW).
Device Specific:
11. 16 bits digital: Bit coded into 16 bits register.
12. 32 bits Mod10K uns: Integer N as 2 16-bit integers A and B. where
N= (A * 10.000) + B
13. 48 bits Mod10K uns: Integer N as 3 16-bit integers A, B and C where
N= (A * 10.0002) +(B * 10.000) + C
14. 64 bits Mod10K uns: Integer N as 4 16-bit integers A, B, C and D
where N= (A * 10.0003) + (B * 10.0002) +(C * 10.000) + D
15. 32 bits Mod10K sig: as the unsigned but the MSb represents the sign.
16. 48 bits Mod10K sig: as the unsigned but the MSb represents the sign.
17. 64 bits Mod10K sig: as the unsigned but the MSb represents the sign.
18. 32 bits Mod10K ION: to be used with ION devices.
19. 32 bits ION sig: to be used with ION devices.
20. 32 bits Invertomatic: to be used with Invertomatic devices.
21. MSB*100 + LSB.
22. 32 bits uns Winv: 32 bits unsigned word inverted (LSW..MSW).
23. 32 bits sig C2 Winv: 32 bits signed (two’s complement).word inverted
(LSW..MSW).
Restrictions
1 bit format can only be used with digital Modbus codes (1,2,5 and 6)
All the other formats cannot be used with the abovementioned codes
Edit mode
Single / Multiple Values selection.
Comments
Formats 1 to 9 are generic Modbus data formats while formats 10 to 20 are
Device specific.
Consult documentation of Modbus device(s) to integrate for information about Modbus data
format of the points desired to integrate.
Address
Description
It's the Modbus register address to use by IntesisBox to read/write the point
into the Modbusdevice.
Edit mode
Text edit or AutoEnumeration
IntesisBox®BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox®is a registered trademark of Intesis Software SL
URL
Email
tel
20 / 27
Comments
Consult documentation of Modbus device(s) to integrate for information about register
addresses of the points desired to integrate.
Bit
Description
Bit used inside the Modbus register to encode the digital value for the point.
IntesisBox allows bit decoding from generic 16 bits input/holding Modbus
registers. Bit coding into 16 bit input/holding Modbus registers is used for
some devices to encode digital values into this type of registers.
Values
0 to 15
Restrictions
Only used with Format=11 (16 bits digital) and Code= 3 or 4 (read
holding/input registers).
To decode more than one of the bits of the 16 bits register all the decoding
rows should be grouped together in the table
Edit mode
Text edit
Frac
Description
Fractional part to consider for the point's value when read/write. Some
devices encode for example temperature values (integer + fractional part) in
common 2-bytes Modbus registers (using data format 16 bits signed two's
complement for example); the problem of using 2-bytes registers is that no
fractional part can be encoded.
To avoid this problem, the real value in the device is sent multiplied by 10 as
just integer part (a real value of 25.1 will be sent as 251). For this kind of
points for example you can specify a value of 1 in Frac column. Then the
value decoded by IntesisBox from the slave will be divided by 10, and the
value will be multiplied by 10 before writing to the slave, thus will be the
real value in the device (including integer and fractional part).
Edit mode
Text edit or AutoEnumeration
Bac.Name
Description
BACnet object name for the signal. This name is included into the BACnet's
Object_name property for the point and it will be collected by any BACnet
explorer.
Restrictions
Maximum 30 characters
Edit mode
Text edit
Comments
Recommended to give a descriptive name to each point with indication of
the Modbus slave/register associated
Bac.Type
This manual suits for next models
2
Table of contents
Other IntesisBox Gateway manuals
IntesisBox
IntesisBox IBOX-BAC-DALI Assembly instructions
IntesisBox
IntesisBox HS-AC-KNX-16/64 Assembly instructions
IntesisBox
IntesisBox SM-ACN-BAC-4 Assembly instructions
IntesisBox
IntesisBox IBOX-BAC-MBTCP-100 User manual
IntesisBox
IntesisBox HI-AC-MBS-16 Assembly instructions
IntesisBox
IntesisBox IBOX-MBS-MBUS Assembly instructions
IntesisBox
IntesisBox HS-AC-BAC-16/64 Assembly instructions
IntesisBox
IntesisBox PA-AC-BAC-16 Assembly instructions
IntesisBox
IntesisBox LG-AC-MBS-4 User manual
IntesisBox
IntesisBox PA-AC-BAC-128 Assembly instructions
IntesisBox
IntesisBox IBOX-BAC-DALI User manual
IntesisBox
IntesisBox LON-KNX User manual
IntesisBox
IntesisBox DK-RC-KNX-1i User manual
IntesisBox
IntesisBox PA-AC-MBS-128 Assembly instructions
IntesisBox
IntesisBox IBOX-ASCII-KNX Assembly instructions
IntesisBox
IntesisBox IS-IR-KNX-1i User manual
IntesisBox
IntesisBox IBKNXMEB0100000 User manual
IntesisBox
IntesisBox KNX-Toshiba AC User manual
IntesisBox
IntesisBox MBS-LON User manual
IntesisBox
IntesisBox PA-AC-MBS-16 Assembly instructions
Popular Gateway manuals by other brands
ZyXEL Communications
ZyXEL Communications P-661H-D Series Support notes
Moxa Technologies
Moxa Technologies MGate 5101-PBM-MN Quick installation guide
Wintec
Wintec WW-5D20 Connection guide
UfiSpace
UfiSpace S9501-18SMT Hardware installation guide
Graco
Graco 24N977 Instructions-parts list
Wieland
Wieland samos PRO manual
