BACnet Server
Modbus RTU Master and Modbus TCP Client
USER MANUAL
Issue date: 06/2020 r1.9 ENGLISH
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
2 / 44
Important User Information
Disclaimer
The information in this document is for informational purposes only. Please inform HMS Industrial Networks of any
inaccuracies or omissions found in this document. HMS Industrial Networks disclaims any responsibility or liability for
any errors that may appear in this document.
HMS Industrial Networks reserves the right to modify its products in line with its policy of continuous product
development. The information in this document shall therefore not be construed as a commitment on the part of
HMS Industrial Networks and is subject to change without notice. HMS Industrial Networks makes no commitment
to update or keep current the information in this document.
The data, examples and illustrations found in this document are included for illustrative purposes and are only
intended to help improve understanding of the functionality and handling of the product. In view of the wide range
of possible applications of the product, and because of the many variables and requirements associated with any
particular implementation, HMS Industrial Networks cannot assume responsibility or liability for actual use based on
the data, examples or illustrations included in this document nor for any damages incurred during installation of the
product. Those responsible for the use of the product must acquire sufficient knowledge in order to ensure that the
product is used correctly in their specific application and that the application meets all performance and safety
requirements including any applicable laws, regulations, codes and standards. Further, HMS Industrial 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 functional side effects found outside the documented scope of the product. The effects
caused by any direct or indirect use of such aspects of the product are undefined and may include e.g. compatibility
issues and stability issues.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
3 / 44
Gateway for the integration of Modbus RTU and Modbus TCP
installations into BACnet MSTP or BACnet IP enabled monitoring
and control systems.
ORDER CODE
LEGACY ORDER CODE
INBACMBM1000000
IBBACMBM1000000
INBACMBM2500000
IBBACMBM2500000
INBACMBM6000000
IBBACMBM6000000
INBACMBM1K20000
IBBACMBM1K20000
INBACMBM3K00000
IBBACMBM3K00000
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
4 / 44
INDEX
1 Description ............................................................................................................................................... 6
Introduction ....................................................................................................................................... 6
Functionality ..................................................................................................................................... 8
Gateway’s capacity .......................................................................................................................... 8
2 Protocol Implementation Conformance Statement .................................................................................. 9
BACnet Standardized Device Profile (Annex L): .............................................................................. 9
Segmentation Capability: ................................................................................................................. 9
Data Link Layer Options: .................................................................................................................. 9
Device Address Binding: ................................................................................................................ 10
Networking Options: ....................................................................................................................... 10
Character Sets Supported .............................................................................................................. 10
Gateway ......................................................................................................................................... 10
3 BACnet Interoperability Building Blocks Supported (BIBBs) ................................................................. 11
Data Sharing BIBBs ....................................................................................................................... 11
Alarm and Event Management BIBBs ............................................................................................ 11
Scheduling BIBBs ........................................................................................................................... 12
Trending BIBBs .............................................................................................................................. 12
Network Management BIBBs ......................................................................................................... 12
Device Management BIBBs ........................................................................................................... 13
4 Service Types ........................................................................................................................................ 14
5 Objects ................................................................................................................................................... 15
Supported Object Types ................................................................................................................. 15
Objects and properties ................................................................................................................... 16
5.2.1 INBACMBM---0000 (Device Object Type) .............................................................................. 16
5.2.2 Analog Input Object Type ....................................................................................................... 18
5.2.3 Analog Output Object Type .................................................................................................... 19
5.2.4 Analog Value Object Type ...................................................................................................... 20
5.2.5 Binary Input Object Type ........................................................................................................ 21
5.2.6 Binary Output Object Type ..................................................................................................... 22
5.2.7 Binary Value Object Type ....................................................................................................... 23
5.2.8 Multistate Input Object Type ................................................................................................... 24
5.2.9 Multistate Output Object Type ................................................................................................ 25
5.2.10 Multistate Value Object Type .................................................................................................. 26
5.2.11 Calendar Object Type ............................................................................................................. 27
5.2.12 Schedule Object Type ............................................................................................................ 28
5.2.13 Notification Class Object Type ............................................................................................... 29
5.2.14 Trend Log Object Type ........................................................................................................... 30
5.2.15 Trend Log Multiple Object Type ............................................................................................. 31
6 Connections ........................................................................................................................................... 32
Powering the device ....................................................................................................................... 33
Connection to BACnet .................................................................................................................... 33
6.2.1 BACnet IP ............................................................................................................................... 33
6.2.2 BACnet MSTP ........................................................................................................................ 33
Connection to Modbus ................................................................................................................... 34
6.3.1 Modbus TCP ........................................................................................................................... 34
6.3.2 Modbus RTU ........................................................................................................................... 34
Connection to the configuration tool ............................................................................................... 34
7 Status LEDs and push buttons .............................................................................................................. 35
8 Set-up process and troubleshooting ...................................................................................................... 36
Pre-requisites ................................................................................................................................. 36
Intesis MAPS. Configuration & monitoring tool for Intesis BACnet series ..................................... 36
7.2.1 Introduction ............................................................................................................................. 36
7.2.2 Connection .............................................................................................................................. 36
7.2.3 Configuration tab .................................................................................................................... 38
7.2.4 Signals .................................................................................................................................... 38
7.2.5 Sending the configuration to Intesis ....................................................................................... 39
7.2.6 Diagnostic ............................................................................................................................... 40
Set-up procedure ............................................................................................................................ 42
9 Electrical & Mechanical Features ........................................................................................................... 43
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
5 / 44
10 Dimensions ............................................................................................................................................ 44
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
6 / 44
1 Description
Introduction
This document describes the integration of Modbus RTU and Modbus TCP installations into BACnet MSTP or BACnet
IP compatible devices and systems using the Intesis BACnet Server – Modbus Client gateway.
The aim of this integration is to make accessible Modbus system signals and resources from a BACnet based control
system or device, as if it was a part of the own BACnet system 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 subscription (COV) requests and reads/writes to its internal points. From the Modbus point of
view, Intesis simulates a Modbus RTU Master device and or Modbus TCP Client device. Readings of the Modbus
slave device(s) is performed by Intesis by automatic continuous polling.
Configuration is carried out using the configuration software IntesisTM MAPS.
This document assumes that the user is familiar with BACnet and Modbus technologies and their technical terms.
Integration of Modbus RTU Slaves or Modbus TCP Servers
to BACnet IP or MSTP control and monitoring systems
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
7 / 44
Integration of Modbus RTU Slaves or Modbus TCP Servers
to BACnet IP control and monitoring systems
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
8 / 44
Functionality
From the Modbus system point of view, after the start up process, Intesis reads continuously the points configured
to be read in the Modbus TCP Server and/or Modbus RTU Slave devices and updates in its memory all the values
received from the Modbus system.
There are 2 available ports for Modbus RTU integration. When enabling this functionality in Intesis MAPS, each RS485 port (Port A and Port B) integrates up to 32 Modbus RTU devices (up to 64 devices in total) without the need of
additional repeaters to the network.
This functionality is disabled when BACnet MSTP is selected in Intesis MAPS, leaving only port A available for
Modbus RTU connectivity and port B for BACnet MSTP devices.
For more information about product ports and connections please see Section 6. Connections.
The default configuration is Port A: Modbus RTU and Port B: BACnet MSTP.
From the BACnet system point of view, after the start up process, the gateway listens for any subscription (COV)
request, serves any polling request, or performs any writing request of its internal points received from the BACnet
system. The values received from BACnet are immediately written in the associated register of the corresponding
Modbus TCP Server or Modbus RTU Slave device.
All 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 BACnet device is detected, the
corresponding virtual signal inside Intesis 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 the gateway.
Gateway’s capacity
Intesis capacity is listed below:
Element
100
version
250
version
600
version
1200
version
3000
version
Notes
Type of BACnet
devices
IP / MSTP
Communication with BACnet IP
and MSTP
Number of BACnet
Objecs
100
250
600
1200
3000
Maximum number of points that
can be defined in the virtual
BACnet device inside the
gateway
Number of BACnet
Subscriptions (COV)
requests
200
500
1200
2400
6000
Maximum number of BACnet
subscriptions (COV) requests
accepted by the gateway
Type of Modbus
slave devices
Modbus RTU (EIA485)
Modbus TCP
Those supporting Modbus
protocol. Communication over
TCP/IP and RTU
Number of Modbus
Slave devices
Up to 5 Modbus TCP nodes/devices
Up to 255 Modbus RTU devices per TCP/RTU
node
Number of Modbus Slave
devices supported by the device
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
9 / 44
2 Protocol Implementation Conformance Statement
BACnet Protocol Implementation Conformance Statement (PICS)
Date: 2018-05-16
Vendor Name: HMS Industrial Networks S.L.U
Product Name: INBACMBM---0000
Product Model Number: INBACMBM---0000
Application Software Version: 1.0.3.0
Firmware Revision: 14.0.1.0
BACnet Protocol Revision: 14
Product Description:
Modbus – BACnet MS/TP & BACnet IP Gateway
Abstraction of Modbus Registers as BACnet Objects.
BACnet Standardized Device Profile (Annex L):
BACnet Operator Workstation (B-OWS)
BACnet Building Controller (B-BC)
BACnet Advanced Application Controller (B-AAC)
BACnet Application Specific Controller (B-ASC)
BACnet Smart Sensor (B-SS)
BACnet Smart Actuator (B-SA)
Additional BACnet Interoperability Building Blocks Supported (Annex K):
Reference of BIBBs List
Segmentation Capability:
Segmented request supported No Yes Window Size · 16 ·
Segmented responses supported No Yes Window Size · 16 ·
Data Link Layer Options:
BACnet IP, (Annex J)
BACnet IP, (Annex J), Foreign Device
ISO 8802-3, Ethernet (Clause 7)
ANSI/ATA 878.1, 2.5 Mb. ARCNET (Clause 8)
ANSI/ATA 878.1, RS-485 ARCNET (Clause 8), baud rate(s) ____
MS/TP master (Clause 9), baud rate(s): 9600, 19200, 38400, 57600, 76800, 115200
MS/TP slave (Clause 9), baud rate(s):
Point-To-Point, EIA 232 (Clause 10), baud rate(s):
Point-To-Point, modem, (Clause 10), baud rate(s):
LonTalk, (Clause 11), medium: _____
Other:
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
10 / 44
Device Address Binding:
Is static device binding supported? (This is currently necessary for two-way communication with
MS/TP slaves and certain other devices.) Yes No
Networking Options:
Router, Clause 6 - List all routing configurations, e.g., ARCNET-Ethernet, Ethernet-MS/TP, etc.
Annex H, BACnet Tunneling Router over IP
BACnet/IP Broadcast Management Device (BBMD)
Does the BBMD support registrations by Foreign Devices? Yes No
Character Sets Supported
Indicating support for multiple character sets does not imply that they can all be supported simultaneously.
ISO 10646 (UTF-8) IBM
/Microsoft DBCS ISO 8859-1
ISO 10646 (UCS-2) ISO 10646 (UCS-4) JIS X 0208
Gateway
If this product is a communication gateway, describe the types of non-BACnet equipment/network(s) that the gateway
supports:
Modbus RTU (EIA485) and TCP networks.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
11 / 44
3 BACnet Interoperability Building Blocks Supported (BIBBs)
Data Sharing BIBBs
BIBB Type
Active
BACnet Service
Initiate
Execute
DS-RP-A
Data Sharing-ReadProperty–A
ReadProperty
DS-RP-B
Data Sharing-ReadProperty–B
ReadProperty
DS-RPM-A
Data Sharing-ReadPropertyMultiple–A
ReadPropertyMultiple
DS-RPM-B
Data Sharing-ReadPropertyMultiple–B
ReadPropertyMultiple
DS-RPC-A
Data Sharing-ReadPropertyConditiona–A
ReadPropertyConditional
DS-RPC-B
Data Sharing-ReadPropertyConditional–B
ReadPropertyConditional
DS-WP-A
Data Sharing-WriteProperty–A
WriteProperty
DS-WP-B
Data Sharing-WriteProperty–B
WriteProperty
DS-WPM-A
Data Sharing-WritePropertyMultiple–A
WritePropertyMultiple
DS-WPM-B
Data Sharing-WritePropertyMultiple–B
WritePropertyMultiple
DS-COV-A
Data Sharing-COV–A
SubscribeCOV
ConfirmedCOVNotification
UnconfirmedCOVNotification
DS-COV-B
Data Sharing-COV–B
SubscribeCOV
ConfirmedCOVNotification
UnconfirmedCOVNotification
DS-COVP-A
Data Sharing-COVP–A
SubscribeCOVProperty
ConfirmedCOVNotification
UnconfirmedCOVNotification
DS-COVP-B
Data Sharing-COVP–B
SubscribeCOVProperty
ConfirmedCOVNotification
UnconfirmedCOVNotification
DS-COVU-A
Data Sharing-COV-Unsubscribed–A
UnconfirmedCOVNotification
DS-COVU-B
Data Sharing-COV- Unsubscribed -B
UnconfirmedCOVNotification
Alarm and Event Management BIBBs
BIBB Type
Active
BACnet Service
Initiate
Execute
AE-N-A
Alarm and Event-Notification–A
ConfirmedEventNotification
UnconfirmedEventNotification
AE-N-I-B
Alarm and Event-Notification Internal–B
ConfirmedEventNotification
UnconfirmedEventNotification
AE-N-E-B
Alarm and Event-Notification External–B
ConfirmedEventNotification
UnconfirmedEventNotification
AE-ACK-A
Alarm and Event-ACK–A
AcknowledgeAlarm
AE-ACK-B
Alarm and Event-ACK–B
AcknowledgeAlarm
AE-ASUM-A
Alarm and Event-Alarm Summary–A
GetAlarmSummary
AE-ASUM-B
Alarm and Event-Alarm Summary–B
GetAlarmSummary
AE-ESUM-A
Alarm and Event-Enrollment Summary-A
GetEnrollmentSummary
AE-ESUM-B
Alarm and Event-Enrollment Summary-B
GetEnrollmentSummary
AE-INFO-A
Alarm and Event-Information–A
GetEventInformation
AE-INFO-B
Alarm and Event-Information–B
GetEventInformation
AE-LS-A
Alarm and Event-LifeSafety–A
LifeSafetyOperation
AE-LS-B
Alarm and Event-LifeSafety–B
LifeSafetyOperation
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
12 / 44
Scheduling BIBBs
Trending BIBBs
Network Management BIBBs
BIBB Type
Active
BACnet Service
Initiate
Execute
SCHED-A
Scheduling–A
(must support DS-RP-A and DS-WP-A)
SCHED-I-B
Scheduling-Internal–B
(shall support DS-RP-B and DS-WP-B)
(shall also support ether DM-TS-B or DS-UTC-B)
SCHED-E-B
Scheduling-External–B
(shall support SCHED-I-B and DS-WP-A)
BIBB Type
Active
BACnet Service
Initiate
Execute
T-VMT-A
Trending - Viewing and Modifying Trends–A
ReadRange
T-VMT-I-B
Trending - Viewing and Modifying Trends Inernal–B
ReadRange
T-VMT-E-B
Trending - Viewing and Modifying Trends External–B
ReadRange
T-ATR-A
Trending - Automated Trend Retrieval–A
ConfirmedEventNotification
ReadRange
T-ATR-B
Trending - Automated Trend Retrieval–B
ConfirmedEventNotification
ReadRange
BIBB Type
Active
BACnet Service
Initiate
Execute
NM-CE-A
Network Management - Connection
Establishment–A
Establish-Connection-ToNetwork
Disconnect-Connection-ToNetwork
NM-CE-B
Network Management - Connection
Establishment– B
Establish-Connection-ToNetwork
Disconnect-Connection-ToNetwork
NM-RC-A
Network Management - Router Configuration–A
Who-Is-Router-To-Network
I-Am-Router-To-Network
I-Could-Be-Router-ToNetwork
Initialize-Routing-Table
Initialize-Routing-Table-Ack
NM-RC-B
Network Management - Router Configuration–B
Who-Is-Router-To-Network
I-Am-Router-To-Network
Initialize-Routing-Table
Initialize-Routing-Table-Ack
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
13 / 44
Device Management BIBBs
BIBB Type
Active
BACnet Service
Initiate
Execute
DM-DDB-A
Device Management - Dynamic Device Binding–A
Who-Is
I-Am
DM-DDB-B
Device Management - Dynamic Device Binding–B
Who-Is
I-Am
DM-DOB-A
Device Management - Dynamic Object Binding–A
Who-Has
I-Have
DM-DOB-B
Device Management - Dynamic Object Binding–B
Who-Has
I-Have
DM-DCC-A
Device Management - DeviceCommunicationControl–A
DeviceCommunicationControl
DM-DCC-B
Device Management - DeviceCommunicationControl–B
DeviceCommunicationControl
DM-PT-A
Device Management - PrivateTransfer–A
ConfirmedPrivateTransfer
UnconfirmedPrivateTransfer
DM-PT-B
Device Management - PrivateTransfer–B
ConfirmedPrivateTransfer
UnconfirmedPrivateTransfer
DM-TM-A
Device Management - Text Message–A
ConfirmedTextMessage
UnconfirmedTextMessage
DM-TM-B
Device Management - Text Message–B
ConfirmedTextMessage
UnconfirmedTextMessage
DM-TS-A
Device Management - TimeSynchronization–A
TimeSynchronization
DM-TS-B
Device Management - TimeSynchronization–B
TimeSynchronization
DM-UTC-A
Device Management - UTCTimeSynchronization–A
UTCTimeSynchronization
DM-UTC-B
Device Management - UTCTimeSynchronization–B
UTCTimeSynchronization
DM-RD-A
Device Management - ReinitializeDevice–A
ReinitializeDevice
DM-RD-B
Device Management - ReinitializeDevice–B
ReinitializeDevice
DM-BR-A
Device Management - Backup and Restore–A
AtomicReadFile
AtomicWriteFile
CreateObject
ReinitializeDevice
DM-BR-B
Device Management - Backup and Restore–B
AtomicReadFile
AtomicWriteFile
ReinitializeDevice
DM-R-A
Device Management - Restart–A
UnconfimedCOVNotification
DM-R-B
Device Management - Restart–B
UnconfimedCOVNotification
DM-LM-A
Device Management - List Manipulation–A
AddListElement
RemoveListElement
DM-LM-B
Device Management - List Manipulation–B
AddListElement
RemoveListElement
DM-OCD-A
Device Management - Object Creation and Deletion–A
CreateObject
DeleteObject
DM-OCD-B
Device Management - Object Creation and Deletion–B
CreateObject
DeleteObject
DM-VT-A
Device Management - Virtual Terminal–A
VT-Open
VT-Close
VT-Data
DM-VT-B
Device Management - Virtual Terminal–B
VT-Open
VT-Close
VT-Data
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
14 / 44
4 Service Types
Service type
Service name
Supported
Remarks
Alarm and Event
Services
AcknowledgeAlarm
ConfirmedCOVNotification
ConfirmedEventNotification
GetAlarmSummary
GetEnrollmentSummary
SubscribeCOV
File Access Services
AtomicReadFile
AtomicWriteFile
Object Access
Services
AddListElement
RemoveListElement
CreateObject
DeleteObject
ReadProperty
ReadPropertyConditional
ReadPropertyMultiple
ReadRange
WriteProperty
WritePropertyMultiple
Remote Device
Management
Services
DeviceComminicationControl
ConfirmedPrivateTransfer
ConfirmedTextMessage
ReinitializeDevice
Virtual Terminal
Services
VtOpen
VtClose
VtData
Security Services
Authenticate
RequestKey
Unconfirmed
Services
I-Am
I-Have
UnconfirmedCOVNotification
UnconfirmedEventNotification
UnconfirmedPrivateTransfer
UnconfirmedTextMessage
TimeSynchronization
UtcTimeSynchronization
Who-Has
Who-Is
LifeSafetyOperation
SubscribeCOVProperty
GetEventInformation
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
15 / 44
5 Objects
Supported Object Types
The objects supported are shown in the table below.
Object Type
ID
Supported
Management Point
Analog-Input
0
Analog-Output
1
Analog-Value
2
Averaging
18
Binary-Input
3
Binary-Output
4
Binary-Value
5
Calendar
6
Command
7
Device
8
Event-Enrollment
9
File
10
Group
11
Life-Safety-Point
21
Life-Safety-Zone
22
Loop
12
Multistate-Input
13
Multistate-Output
14
Multistate-Value
19
Notification-Class
15
Program
16
Schedule
17
Trend-Log
20
Trend-Log-Multiple
27
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
16 / 44
Objects and properties
5.2.1 INBACMBM---0000 (Device Object Type)
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Device, 246000)
R R Object_Name
CharacterString
"INBACMBM---0000"
R R Object_Type
BACnetObjectType
DEVICE (8) (Device Object Type)
R R System_Status
BACnetDeviceStatus
OPERATIONAL (0)
R R Vendor_Name
CharacterString
"HMS Industrial Networks S.L.U"
R R Vendor_Identifier
Unsigned16
246 R R
Model_Name
CharacterString
"INBACMBM---0000 "
R R Firmware_Revision
CharacterString
"1.0.0.0"
R
R
Application_Software_
Version
CharacterString
"1.0.0.0"
R
R
Location
CharacterString
"" O - Protocol_Version
Unsigned
1 R R
Protocol_Revision
Unsigned
12 R R
Protocol_Services_
Supported
BACnetServiceSupported
Refer to section 4 [Service Types]
R
R
Protocol_Object_Types_
Supported
BACnetObjectTypes
Supported
Refer to section 4 [Object Types]
R
R
Object_List
BACnetArray[N] of
BACnetObjectIdentifier
BACnetARRAY[N]
R
R
Structured_Object_List
BACnetArray[N] of
BACnetObjectIdentifier
- O -
Max_APDU_Length_
Accepted
Unsigned
480 when MSTP / 1476 when BACnet/IP
R
R
Segmentation_Supported
BACnetSegmentation
SEGMENTED-BOTH (0)
R R Max_Segments_accepted
Unsigned
16 O R
VT_Classes_Supported
List of BACnetVTClass
- O -
Active_VT_Sessions
List of BACnetVTSession
- O -
Local_Date
Date
Current date
O
R
Local_Time
Time
Current time
O R UTC_Offset
INTEGER
-
O - Daylight_Savings_Status
BOOLEAN
- O -
APDU_Segment_Timeout
Unsigned
3000 R R
APDU_Timeout
Unsigned
3000 R R
Number_of_APDU_
Retries
Unsigned
3 R R
List_Of_Session_Keys
List of
BACnetSessionKey
- O -
Time_Synchronization_
Recipients
List of BACnetRecipient
- O -
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
17 / 44
Max_Master * **
Unsigned
127 R W
Max_Info_Frames *
Unsigned
1 O R
Device_Address_Binding
List of
BACnetAddressBinding
NULL (empty)
R
R
Database_Revision
Unsigned
0 R R
Configuration_Files
BACnetArray[N] of
BACnetObjectIdentifier
- O -
Last_Restore_Time
BACnetTimeStamp
- O -
Backup_Failure_Timeout
Unsigned16
- O -
Active_COV_
Subscriptions
List of
BACnetCOVSubscription
List of BACnetCOVSubscription
O
R
Slave_Proxy_Enable
BACnetArray[N] of
BOOLEAN
- O -
Manual_Slave_Address_
Binding
List of
BACnetAddressBinding
- O -
Auto_Slave_Discovery
BACnetArray[N] of
BOOLEAN
- O -
Slave_Address_Binding
BACnetAddressBinding
- O -
Last_Restart_Reason
BACnetRestartReason
- O -
Time_Of_Device_Restart
BACnetTimeStamp
- O -
Restart_Notification_
Recipients
List of BACnetRecipient
- O -
UTC_Time_
Synchronization_
Recipients
List of BACnetRecipient
- O -
Time_Synchronization_
Interval
Unsigned
- O -
Align_Intervals
BOOLEAN
- O -
Interval_Offset
Unsigned
- O -
Profile_Name
CharacterString
- O -
* Only available when MSTP is used
** Configurable through the configuration tool.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
18 / 44
5.2.2 Analog Input Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Analog Input, 0)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config Tool
R
R
Object_Type
BACnetObjectType
ANALOG_INPUT (0)
R
R
Present_Value
REAL x R
R
Description
CharacterString
- O - Device_Type
CharacterString
- O -
Status_Flags
BACnetStatusFlags
{FALSE, FALSE/TRUE, FALSE, FALSE}
R
R
Event_State
BACnetEventState
STATE_NORMAL (0)
R
R
Reliability
BACnetReliability
NO_FAULT_DETECTED (0),
UNRELIABLE_OTHER (7)
O
R
Out_Of_Service
BOOLEAN
FALSE
R R
Update_Interval
Unsigned
- O -
Units
BACnetEngineeringUnits
Configurable through BACnet and Config Tool
R
R
Min_Pres_Value
REAL - O
-
Max_Pres_Value
REAL - O
-
Resolution
REAL - O
-
COV_Increment
REAL 0 O W
Time_Delay
Unsigned
- O R* Notification_Class
Unsigned
- O R*
High_Limit
REAL - O R*
Low_Limit
REAL - O R*
Deadband
REAL - O R*
Limit_Enable
BACnetLimitEnable
- O R* Event_Enable
BACnetEventTransitionBits
-
O R*
Acked_Transitions
BACnetEventTransitionBits
-
O
R*
Notify_Type
BACnetNotifyType
-
O R*
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
- O R*
Profile_Name
CharacterString
- O -
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
19 / 44
5.2.3 Analog Output Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Analog Output, 0)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config Tool
R
R
Object_Type
BACnetObjectType
ANALOG_OUTPUT (1)
R
R
Present_Value
REAL x W
W
Description
CharacterString
- O - Device_Type
CharacterString
- O -
Status_Flags
BACnetStatusFlags
{FALSE, FALSE, FALSE, FALSE}
R
R
Event_State
BACnetEventState
STATE_NORMAL (0)
R
R
Reliability
BACnetReliability
NO_FAULT_DETECTED (0)
O
R
Out_Of_Service
BOOLEAN
FALSE
R
R
Update_Interval
Unsigned
- O -
Units
BACnetEngineeringUnits
Configurable through BACnet and Config Tool
R
R
Min_Pres_Value
REAL - O
-
Max_Pres_Value
REAL - O
-
Resolution
REAL - O
-
COV_Increment
REAL 0 O
W
Priority_Array
BACnetPriorityArray
BACnetPriorityArray
R
R
Relinquish_Default
Unsigned
Configurable through BACnet and Config Tool
W
W
Time_Delay
Unsigned
- O R*
Notification_Class
Unsigned
- O R*
High_Limit
REAL - O R*
Low_Limit
REAL - O R*
Deadband
REAL - O R*
Limit_Enable
BACnetLimitEnable
-
O R*
Event_Enable
BACnetEventTransitionBits
-
O R*
Acked_Transitions
BACnetEventTransitionBits
-
O
R*
Notify_Type
BACnetNotifyType
-
O R*
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
- O R*
Profile_Name
CharacterString
- O -
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
20 / 44
5.2.4 Analog Value Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Analog Value, 0)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config Tool
R
R
Object_Type
BACnetObjectType
ANALOG_VALUE (2)
R
R
Present_Value
REAL x R
W
Description
CharacterString
- O - Status_Flags
BACnetStatusFlags
{FALSE, FALSE, FALSE, FALSE}
R
R
Event_State
BACnetEventState
STATE_NORMAL (0)
R
R
Reliability
BACnetReliability
NO_FAULT_DETECTED (0)
O
R
Out_Of_Service
BOOLEAN
FALSE
R R
Update_Interval
Unsigned
- O -
Units
BACnetEngineeringUnits
Configurable through BACnet and Config Tool
R
R
Min_Pres_Value
REAL - O
-
Max_Pres_Value
REAL - O
-
Resolution
REAL - O
-
COV_Increment
REAL 0 O W
Time_Delay
Unsigned
- O R*
Notification_Class
Unsigned
- O R*
High_Limit
REAL - O R*
Low_Limit
REAL - O R*
Deadband
REAL - O R*
Limit_Enable
BACnetLimitEnable
- O R*
Event_Enable
BACnetEventTransitionBits
-
O R*
Acked_Transitions
BACnetEventTransitionBits
-
O
R*
Notify_Type
BACnetNotifyType
-
O R*
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
- O R*
Profile_Name
CharacterString
- O -
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
21 / 44
5.2.5 Binary Input Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Binary Input, 0)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config
Tool
R
R
Object_Type
BACnetObjectType
BINARY_INPUT (3)
R
R
Present_Value
BACnetBinaryPV
INACTIVE (0) / ACTIVE (1)
R
R
Description
CharacterString
- O -
Device_Type
CharacterString
-
O
-
Status_Flags
BACnetStatusFlags
{FALSE, FALSE/TRUE, FALSE, FALSE}
R
R
Event_State
BACnetEventState
STATE_NORMAL (0)
R
R
Reliability
BACnetReliability
NO_FAULT_DETECTED (0),
UNRELIABLE_OTHER (7)
O
R
Out_Of_Service
BOOLEAN
FALSE
R
R
Polarity
BACnetPolarity
NORMAL (0)
R
R
Inactive_Text
CharacterString
Configurable through BACnet and Config
Tool
O
R
Active_Text
CharacterString
Configurable through BACnet and Config
Tool
O
R
Change_Of_State_Time
BACnetDatetime
- O R
Change_Of_State_Count
Unsigned
- O R
Time_Of_State_Count_Reset
BACnetDatetime
- O R
Elapsed_Active_Time
Unsigned
- O R Time_Of_Active_Time_Reset
BACnetDatetime
- O R
Time_Delay
Unsigned
- O R* Notification_Class
Unsigned
- O R*
Alarm_Value
BACnetBinaryPV
- O R*
Event_Enable
BACnetEventTransitionBits
-
O
R*
Acked_Transitions
BACnetEventTransitionBits
-
O
R*
Notify_Type
BACnetNotifyType
- O R*
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
- O R*
Profile_Name
CharacterString
- O -
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
22 / 44
5.2.6 Binary Output Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Binary Output, 0)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config
Tool
R
R
Object_Type
BACnetObjectType
BINARY_OUTPUT (4)
R
R
Present_Value
BACnetBinaryPV
INACTIVE (0) / ACTIVE (1)
W W
Description
CharacterString
- O -
Device_Type
CharacterString
- O -
Status_Flags
BACnetStatusFlags
{FALSE, FALSE, FALSE, FALSE}
R
R
Event_State
BACnetEventState
STATE_NORMAL (0)
R
R
Reliability
BACnetReliability
NO_FAULT_DETECTED (0)
O
R
Out_Of_Service
BOOLEAN
FALSE
R R
Polarity
BACnetPolarity
NORMAL (0)
R
R
Inactive_Text
CharacterString
Configurable through BACnet and Config
Tool
O
R
Active_Text
CharacterString
Configurable through BACnet and Config
Tool
O
R
Change_Of_State_Time
BACnetDatetime
- O R
Change_Of_State_Count
Unsigned
- O R
Time_Of_State_Count_Reset
BACnetDatetime
- O R
Elapsed_Active_Time
Unsigned
- O R
Time_Of_Active_Time_Reset
BACnetDatetime
- O R
Minimum_Off_Time
Unsigned32
- O -
Minimum_On_Time
Unsigned32
- O -
Priority_Array
BACnetPriorityArray
BACnetPriorityArray
R
R
Relinquish_Default
BACnetBinaryPV
INACTIVE (0)
W W
Time_Delay
Unsigned
- O R*
Notification_Class
Unsigned
- O R*
Feedback_Value
BACnetBinaryPV
- O W
Event_Enable
BACnetEventTransitionBits
-
O R*
Acked_Transitions
BACnetEventTransitionBits
-
O
R*
Notify_Type
BACnetNotifyType
-
O R*
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
- O R*
Profile_Name
CharacterString
- O -
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
23 / 44
5.2.7 Binary Value Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Binary Value, 0)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config
Tool
R
R
Object_Type
BACnetObjectType
BINARY_VALUE (5)
R
R
Present_Value
BACnetBinaryPV
INACTIVE (0) / ACTIVE (1)
W W
Description
CharacterString
- O -
Status_Flags
BACnetStatusFlags
{FALSE, FALSE, FALSE, FALSE}
R
R
Event_State
BACnetEventState
STATE_NORMAL (0)
R
R
Reliability
BACnetReliability
NO_FAULT_DETECTED (0)
O
R
Out_Of_Service
BOOLEAN
FALSE
R R
Inactive_Text
CharacterString
Configurable through BACnet and Config
Tool
O
R
Active_Text
CharacterString
Configurable through BACnet and Config
Tool
O
R
Change_Of_State_Time
BACnetDatetime
- O R
Change_Of_State_Count
Unsigned
- O R
Time_Of_State_Count_Reset
BACnetDatetime
- O R
Elapsed_Active_Time
Unsigned
- O R
Time_Of_Active_Time_Reset
BACnetDatetime
- O R
Minimum_Off_Time
Unsigned32
- O -
Minimum_On_Time
Unsigned32
- O -
Time_Delay
Unsigned
- O R*
Notification_Class
Unsigned
- O R*
Alarm_Value
BACnetBinaryPV
- O R*
Event_Enable
BACnetEventTransitionBits
-
O R*
Acked_Transitions
BACnetEventTransitionBits
-
O
R*
Notify_Type
BACnetNotifyType
-
O R*
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
- O R*
Profile_Name
CharacterString
- O -
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
24 / 44
5.2.8 Multistate Input Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Multi-state Input, 0)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config Tool
R
R
Object_Type
BACnetObjectType
MULTISTATE_INPUT (13)
R
R
Present_Value
Unsigned
x R R
Description
CharacterString
-
O -
Device_Type
CharacterString
- O -
Status_Flags
BACnetStatusFlags
{FALSE, FALSE/TRUE, FALSE, FALSE}
R
R
Event_State
BACnetEventState
STATE_NORMAL (0)
R
R
Reliability
BACnetReliability
NO_FAULT_DETECTED (0),
UNRELIABLE_OTHER (7)
O
R
Out_Of_Service
BOOLEAN
FALSE
R R
Number_Of_States
Unsigned
Configurable through BACnet and Config Tool
R
R
State_Text
BACnetArray[N] of
CharacterString
- O R
Time_Delay
Unsigned
- O R* Notification_Class
Unsigned
- O R* Alarm_Values
List of Unsigned
- O R*
Fault_Values
List of Unsigned
- O R*
Event_Enable
BACnetEventTransitionBits
-
O R*
Acked_Transitions
BACnetEventTransitionBits
-
O
R*
Notify_Type
BACnetNotifyType
-
O R*
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
- O R*
Profile_Name
CharacterString
- O -
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
25 / 44
5.2.9 Multistate Output Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Multi-state Output, 0)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config Tool
R
R
Object_Type
BACnetObjectType
MULTISTATE_OUTPUT (14)
R
R
Present_Value
Unsigned
x W W
Description
CharacterString
-
O
-
Device_Type
CharacterString
- O -
Status_Flags
BACnetStatusFlags
{FALSE, FALSE, FALSE, FALSE}
R
R
Event_State
BACnetEventState
STATE_NORMAL (0)
R
R
Reliability
BACnetReliability
NO_FAULT_DETECTED (0)
O
R
Out_Of_Service
BOOLEAN
FALSE
R
R
Number_Of_States
Unsigned
Configurable through BACnet and Config Tool
R
R
State_Text
BACnetArray[N] of
CharacterString
O R
Priority_Array
BACnetPriorityArray
BACnetPriorityArray
R
R
Relinquish_Default
Unsigned
1 W W
Time_Delay
Unsigned
- O R*
Notification_Class
Unsigned
- O R*
Feedback_Value
Unsigned
- O W
Event_Enable
BACnetEventTransitionBits
- O R*
Acked_Transitions
BACnetEventTransitionBits
- O R*
Notify_Type
BACnetNotifyType
- O R*
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
- O R*
Profile_Name
CharacterString
- O -
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
26 / 44
5.2.10 Multistate Value Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Multi-state Output, 0)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config Tool
R
R
Object_Type
BACnetObjectType
MULTISTATE_VALUE (19)
R
R
Present_Value
Unsigned
x W W
Description
CharacterString
-
O
-
Status_Flags
BACnetStatusFlags
{FALSE, FALSE, FALSE, FALSE}
R
R
Event_State
BACnetEventState
STATE_NORMAL (0)
R
R
Reliability
BACnetReliability
NO_FAULT_DETECTED (0)
O
R
Out_Of_Service
BOOLEAN
FALSE
R
R
Number_Of_States
Unsigned
Configurable through BACnet and Config Tool
R
R
State_Text
BACnetArray[N] of
CharacterString
O R
Time_Delay
Unsigned
- O R*
Notification_Class
Unsigned
- O R*
Alarm_Values
Unsigned
- O R*
Fault_Values
Unsigned
O R*
Event_Enable
BACnetEventTransitionBits
- O R*
Acked_Transitions
BACnetEventTransitionBits
- O R*
Notify_Type
BACnetNotifyType
- O R*
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
- O R*
Profile_Name
CharacterString
- O -
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
27 / 44
5.2.11 Calendar Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Calendar, 6)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config
Tool
R
R
Object_Type
BACnetObjectType
CALENDAR (6)
R
R
Description
CharacterString
- O -
Present_Value
BOOLEAN
- R R
Date_List
BACnetLIST of
BACnetCalendarEntry
- R W
Profile_Name
BACnetARRAY[N] of
BACnetPropertyIdentifier
-
O
-
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
28 / 44
5.2.12 Schedule Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Schedule, 17)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config
Tool
R
R
Object_Type
BACnetObjectType
SCHEDULE (17)
R
R
Present_Value
Any
- R R
Description
CharacterString
- O -
Effective_Period
BACnetDateRange
- R W
Weekly_Schedule
BACnetARRAY[7] of
BACnetDailySchedule
- R W
Exception_Schedule
BACnetARRAY[N] of
BACnetSpecialEvent
-
R
W
Schedule_Default
Any
- R W
List_Of_Object_Property_Refer
ences
BACnetLIST of
BACnetDeviceObjectProper
tyReference
- R R
Priority_For_Writing
Unsigned(1..16)
- R W
Status_Flags
BACnetStatusFlags
- R R
Reliability
BACnetReliability
-
R
R
Out_Of_Service
BOOLEAN
- R R
Event_Detection_Enable
BOOLEAN
-
O
-
Notification_Class
Unsigned
- O -
Event_Enable
BACnetEventTransitionBits
- O -
Event_State
BACnetEventState
- O -
Acked_Transitions
BACnetEventTransitionBits
- O -
Notify_Type
BACnetNotifyType
-
O
-
Event_Time_Stamps
BACnetARRAY[3] of
BACnetTimeStamp
- O -
Event_Message_Texts
BACnetARRAY[3] of
CharacterString
- O -
Event_Message_Texts_Config
BACnetARRAY[3] of
CharacterString
- O -
Reliability_Evaluation_Inhibit
BOOLEAN
- O -
Profile_Name
CharacterString
- O -
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
29 / 44
5.2.13 Notification Class Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Notification_Class, 15)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config
Tool
R
R
Object_Type
BACnetObjectType
NOTIFICATION_CLASS (15)
R
R
Description
CharacterString
- O -
Notification_Class
Unsigned
- R R
Priority
BACnetARRAY[3] of
Unsigned
- R R
Ack_Required
BACnetEventTransitionBits
-
R
R
Recipient_List
BACnetLIST of
BACnetDestination
- R R
Profile_Name
CharacterString
-
O
-
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
30 / 44
5.2.14 Trend Log Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Trend_Log, 20)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config
Tool
R
R
Object_Type
BACnetObjectType
TREND_LOG (20)
R
R
Description
CharacterString
- O -
Enable
BOOLEAN
R W
Start_Time
BACnetDateTime
O W
Stop_Time
BACnetDateTime
O W
Log_DeviceObjectProperty
BACnetDeviceObject
PropertyReference
O -
Log_Interval
Unsigned
O -
COV_Resubscription_Interval
Unsigned
O -
Client_COV_Increment
BACnetClientCOV
O -
Stop_When_Full
BOOLEAN
R R
Buffer_Size
Unsigned
R R
Log_Buffer
List of BACnetLogRecord
R R
Record_Count
Unsigned
R W
Total_Record_Count
Unsigned
R R
Notification_Threshold
Unsigned
O R*
Records_Since_Notification
Unsigned
O R*
Last_Notify_Record
Unsigned
O R*
Event_State
BACnetEventState
R R
Notification_Class
Unsigned
O R*
Event_Enable
BACnetEventTransitionBits
O R*
Acked_Transitions
BACnetEventTransitionBits
O R*
Notify_Type
BACnetNotifyType
O R*
Event_Time_Stamps
BACnetARRAY[3] of
BACnetTimeStamp
O R*
EventMessageTexts
BACnetARRAY[3] of
CharacterString
O R*
Profile_Name
CharacterString
O -
Logging_Type
BACnetLoggingType
R R
Status_Flags
BACnetStatusFlags
R R
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
31 / 44
5.2.15 Trend Log Multiple Object Type
Property Identifier
Property Datatype
Value
ASHRAE
IBOX
Object_Identifier
BACnetObjectIdentifier
(Trend_Log_Multiple, 27)
R
R
Object_Name
CharacterString
Configurable through BACnet and Config
Tool
R
R
Object_Type
BACnetObjectType
TREND_LOG_MULTIPLE (27)
R
R
Description
CharacterString
- O -
Enable
BOOLEAN
R W
Start_Time
BACnetDateTime
O W
Stop_Time
BACnetDateTime
O W
Log_DeviceObjectProperty
BACnetARRAY[10] of
BACnetDeviceObject
PropertyReference
O R
Log_Interval
Unsigned
O -
COV_Resubscription_Interval
Unsigned
O -
Client_COV_Increment
BACnetClientCOV
O -
Stop_When_Full
BOOLEAN
R R
Buffer_Size
Unsigned
R R
Log_Buffer
List of BACnetLogRecord
R R
Record_Count
Unsigned
R W
Total_Record_Count
Unsigned
R R
Notification_Threshold
Unsigned
O R*
Records_Since_Notification
Unsigned
O R*
Last_Notify_Record
Unsigned
O R*
Event_State
BACnetEventState
R R
Notification_Class
Unsigned
O R*
Event_Enable
BACnetEventTransitionBits
O R*
Acked_Transitions
BACnetEventTransitionBits
O R*
Notify_Type
BACnetNotifyType
O R*
Event_Time_Stamps
BACnetARRAY[3] of
BACnetTimeStamp
O R*
EventMessageTexts
BACnetARRAY[3] of
CharacterString
O R*
Profile_Name
CharacterString
O -
Logging_Type
BACnetLoggingType
R R
Status_Flags
BACnetStatusFlags
R R
* Only available when specific object has a Notification Class configured
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
32 / 44
6 Connections
Find below information regarding the Intesis connections available.
Power Supply
Must use NEC Class 2 or Limited Power Source (LPS) and
SELV rated power supply.
If using DC power supply:
Respect polarity applied of terminals (+) and (-). Be sure the
voltage applied is within the range admitted (check table
below). The power supply can be connected to earth but
only through the negative terminal, never through the
positive terminal.
If using AC power supply:
Make sure the voltage applied is of the value admitted (24
Vac). Do not connect any of the terminals of the AC power
supply to earth, and make sure the same power supply is
not supplying any other device.
Ethernet / BACnet IP / Modbus TCP
Connect the cable coming from the IP network to the connector
ETH of the gateway. Use an Ethernet CAT5 cable. If
communicating through the LAN of the building, contact the
network administrator and make sure traffic on the port used is
allowed through all the LAN path (check the gateway user
manual for more information). With factory settings, after
powering up the gateway, DHCP will be enabled for 30 seconds.
After that time, if no IP is provided by a DHCP server, the default
IP 192.168.100.246 will be set.
PortA / Modbus RTU
Connect the EIA485 bus to connectors A3 (A-), A4 (B+) and A1 or A2 (SNGD) of gateway’s PortA. Respect the
polarity.
PortB / BACnet MSTP / Modbus RTU
Connect the EIA485 bus to connectors B1 (B+), B2 (A-) and B3 (SNGD) of gateway’s PortB. Respect the polarity.
Note for PortA and PortB; Remember the characteristics of the standard EIA485 bus: maximum distance of 1200
meters, maximum 32 devices connected to the bus, and in each end of the bus it must be a termination resistor of
120 Ω. The gateway has an internal bus biasing circuit that incorporates the termination resistor. If you install the
gateway in one of the ends of the bus, then do not install an additional termination resistor in that end.
Console Port
Connect a mini-type B USB cable from your computer to the gateway to allow communication between the
Configuration Software and the gateway. Remember that Ethernet connection is also allowed. Check the user manual
for more information.
USB
Connect a USB storage device (not a HDD) if required. Check the user manual for more information.
Ensure proper space for all connectors when mounted (see section 10).
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
33 / 44
Powering the device
A power supply working with any of the voltage range allowed is needed (check section 9). Once connected the RUN
led (Figure above) 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:
• 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.
Connection to BACnet
6.2.1 BACnet IP
Connect the communication cable coming from the network hub or switch to the ETH port (Figure above) of Intesis.
The cable to be used shall be a straight Ethernet UTP/FTP CAT5 cable
In case there is no response from the BACnet devices to the frames sent by Intesis, check that they are operative
and reachable from the network connection used by Intesis. Check the Intesis Ethernet interface sending Pings to its
IP address using a PC connected to the same Ethernet network.
Check as well with the network admin that there are no limitations regarding UDP communication or ports blocked.
6.2.2 BACnet MSTP
Connect the EIA485 bus to connectors B1 (B+), B2 (A-) and B3 (SNGD) of gateway’s PortB. Respect the polarity.
Remember the characteristics of the standard EIA485 bus: maximum distance of 1200 meters, maximum 32 devices
connected to the bus, and in each end of the bus it must be a termination resistor of 120 Ω. The gateway has an
internal bus biasing circuit that incorporates the termination resistor. If you install the gateway in one of the ends of
the bus, then do not install an additional termination resistor in that end.
Note: BACnet MSTP only available when port B not used for Modbus RTU integration. Selectable by Intesis MAPS.
BACnet IP connection using switch/hub and straight cable
BACnet IP connection without switch/hub and crossed cable
Ethernet Crossed
Ethernet straight
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
34 / 44
Connection to Modbus
6.3.1 Modbus TCP
Connect the communication cable coming from the network hub or switch to the ETH port of Intesis. The cable to be
used shall be a straight Ethernet UTP/FTP CAT5 cable.
6.3.2 Modbus RTU
Connect the communication cable coming from the Modbus network to the port/s marked as Modbus of Intesis.
Connect the EIA485 bus to connectors A3 (A-), A4 (B+) and A1 or A2 (SNGD) of gateway’s PortA. Respect the
polarity.
If you use Port B as a Modbus RTU port, connect the EIA485 bus to connectors B1 (B+), B2 (A-) and B3 (SNGD) of
gateway’s PortB. Respect the polarity.
Remember the characteristics of the standard EIA485 bus: maximum distance of 1200 meters, maximum 32 devices
connected to the bus, and in each end of the bus it must be a termination resistor of 120 Ω. The gateway has an
internal bus biasing circuit that incorporates the termination resistor. If you install the gateway in one of the ends of
the bus, then do not install an additional termination resistor in that end.
Note: Modbus RTU only available when port B not used for BACnet MSTP integration. Selectable by Intesis MAPS.
Connection to the configuration tool
This action allows the user to have access to configuration and monitoring of the device (more information can be
found in the configuration tool User Manual). Two methods to connect to the PC can be used:
• Ethernet: Using the Ethernet port of Intesis.
• USB: Using the console port of Intesis, connect a USB cable from the console port to the PC.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
35 / 44
7 Status LEDs and push buttons
LED
Colour
Indication
Run
Off
No power
Green
Device powered and working.
Error
Off
No error
Red
Error
Port A (Tx/Rx) – Modbus RTU
Off
There is no activity on this port.
Tx - Blinking green
Every data packet sent to the network it
blinks
Rx – Blinking yellow
Every data packet received from a slave
device it blinks
Port B (Tx/Rx) – Modbus RTU
(Using BACnet/IP protocol)
Off
There is no activity on this port.
Tx - Blinking green
Every data packet sent to the network it
blinks
Rx – Blinking yellow
Every data packet received from a slave
device it blinks
Port B (Tx/Rx) – BACnet
(Using BACnet/MSTP protocol)
Off
There is no activity on this port.
Tx - Blinking green
Every data packet sent to the network it
blinks
Rx – Blinking yellow
Every data packet received from a slave
device it blinks
Button A – Modbus RTU
Off / Red
It doen’t have any functionality
Button B – Modbus RTU
(Using BACnet/IP protocol)
Off / Red
It doen’t have any functionality
Button B – BACnet
(Using BACnet/MSTP protocol)
Off / Red
On when link is detected:
- BACnetIP: ethernet is up & running,
the IBOX got an IP
- BACnetMSTP: token passing is
detected
Push button
Functionality
Button A – Modbus RTU
It doesn’t have any functionality. It can be configured from Intesis MAPS
software
Button B – Modbus RTU
(Using BACnet/IP protocol)
It doesn’t have any functionality. It can be configured from Intesis MAPS
software
Button B – BACnet
(Using BACnet/MSTP protocol)
Sends to Broadcast I-Am message
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
36 / 44
8 Set-up process and troubleshooting
Pre-requisites
It is necessary to have a BACnet IP client or MSTP device operative and well connected to the corresponding BACnet
port of Intesis and a Modbus RTU slave or Modbus TCP client connected to their corresponding ports as well.
Connectors, connection cables, PC to use the configuration tool and other auxiliary material, if needed, are not
supplied by HMS Industrial Networks S.L.U for this standard integration.
Items supplied by HMS Networks for this integration are:
• Intesis gateway.
• Link to download the configuration tool.
• USB Console cable to communicate with Intesis.
• Product documentation.
Intesis MAPS. Configuration & monitoring tool for Intesis BACnet series
7.2.1 Introduction
Intesis MAPS is a Windows® compatible software developed specifically to monitor and configure Intesis BACnet
series.
The installation procedure and main functions are explained in the Intesis MAPS User Manual. This document can
be downloaded from the link indicated in the installation sheet supplied with the Intesis device or in the product
website at www.intesis.com
In this section, only the specific case of Modbus to BACnet systems will be covered.
Please check the Intesis MAPS user manual for specific information about the different parameters and how to
configure them.
7.2.2 Connection
To configure the Intesis connection parameters press on the Connection button in the menu bar.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
37 / 44
Figure 8.1 MAPS connection
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
38 / 44
7.2.3 Configuration tab
Select the Configuration tab to configure the connection parameters. Three subsets of information are shown in this
window: General (Gateway general parameters), BACnet Server (BACnet interface configuration) and Modbus
Master (Modbus interface parameters).
Figure 8.2 Intesis MAPS configuration tab
7.2.4 Signals
All available objects, Object Instances, its corresponding Modbus register and other main parmaters are listed in the
signals tab. More information on each parameter and how to configure it can be found in the Intesis MAPS user
manual.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
39 / 44
Figure 8.3 Intesis MAPS Signals tab
7.2.5 Sending the configuration to Intesis
When the configuration is finished, follow the next steps.
1.- Click on Save button to save the project to the project folder on your hard disk (more information in Intesis
MAPS User Manual).
2.- You will be prompted to generate the configuration file to be sent to the gateway.
a.- If Yes is selected, the file containing the configuration for the gateway will be generated and saved
also into the project folder.
b.- If NO is selected, remember that the binary file with the project needs to be generated before the
Intesis starts to work as expected.
3.- Press the Send File button to send the binary file to the Intesis device. The process of file transmission
can be monitored in the Intesis Communication Console window. Intesis will reboot automatically once the
new configuration is loaded.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
40 / 44
Figure 8.4 Intesis MAPS Receive/Send tab
After any configuration change, do not forget to send the configuration file to the Intesis using button
Send File.
7.2.6 Diagnostic
To help integrators in the commissioning tasks and troubleshooting, the Configuration Tool offers some specific tools
and viewers.
In order to start using the diagnostic tools, connection with the Gateway is required.
The Diagnostic section is composed by two main parts: Tools and Viewers.
• Tools
Use the tools section to check the current hardware status of the box, log communications into
compressed files to be sent to the support, change the Diagnostic panels’ view or send commands
to the gateway.
• Viewers
In order to check the current status, viewer for the Internal and External protocols are available. It is
also available a generic Console viewer for general information about communications and the
gateway status and finally a Signals Viewer to simulate the BMS behavior or to check the current
values in the system.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
41 / 44
Figure 8.5 Diagnostic
More information about the Diagnostic section can be found in the Configuraion Tool manual.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
42 / 44
Set-up procedure
1. Install Intesis MAPS on your laptop, use the setup program supplied for this and follow the instructions given by
the Installation wizard.
2. Install Intesis in the desired installation site. Installation can be on DIN rail or on a stable not vibrating surface
(DIN rail mounted inside a metallic industrial cabinet connected to ground is recommended).
3. If using BACnet IP, connect the communication cable coming from the BACnet IP network to the port marked as
Ethernet on Intesis (More details in section 6).
If using BACnet MSTP, connect the communication cables coming from the BACnet MSTP network to the port
marked as Port B on Intesis. This configuration can be later changed in MAPS configuration (More details in
section 6).
4. If using, Modbus RTU, connect the communication cable coming from the EIA485 port of the Modbus RTU
installation to the port marked as Port A or B of Intesis. This configuration can be later changed in MAPS
configuration (More details in section 6).
If using, Modbus TCP, connect the communication cable coming from the Ethernet port of the Modbus TCP
installation to the port marked as Ethernet of Intesis (More details in section 6).
5. Power up Intesis. The supply voltage can be 9 to 30 Vdc or just 24 Vac. Take care of the polarity of the supply
voltage applied.
WARNING! In order to avoid earth loops that can damage Intesis and/or any other equipment connected to
it, we strongly recommend:
• 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.
6. If you want to connect using IP, connect the Ethernet cable from the laptop PC to the port marked as Ethernet of
Intesis (More details in section 6).
If you want to connect using USB, connect the USB cable from the laptop PC to the port marked as Console of
Intesis (More details in section 6).
7. Open Intesis MAPS, create a new project selecting a copy of the one named INBACMBM---0000.
8. Modify the configuration as desired, save it and download the configuration file to Intesis as explained in the
Intesis MAPS user manual.
9. Visit the Diagnostic section and check that there is communication activity, some TX frames and some other RX
frames. This means that the communication with the BACnet master device and Modbus Slave devices is OK.
In case there is no communication activity between Intesis and the BACnet and/or Modbus devices, check that
those are operative: check the baud rate, the communication cable used to connect all devices and any other
communication parameter.
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
43 / 44
9 Electrical & Mechanical Features
Enclosure
Plastic, type PC (UL 94 V-0)
Net dimensions (dxwxh): 90x88x56 mm
Recommended space for installation (dxwxh): 130x100x100mm
Color: Light Grey. RAL 7035
Battery
Size: Coin 20mm x 3.2mm
Capacity: 3V / 225mAh
Type: Manganese Dioxide Lithium
Mounting
Wall.
DIN rail EN60715 TH35.
Console Port
Mini Type-B USB 2.0 compliant
1500VDC isolation
Terminal Wiring
(for power supply and
low-voltage signals)
Per terminal: solid wires or stranded wires (twisted or with ferrule)
1 core: 0.5mm
2
… 2.5mm
2
2 cores: 0.5mm
2
… 1.5mm
2
3 cores: not permitted
USB port
Type-A USB 2.0 compliant
Only for USB flash storage device
(USB pen drive)
Power consumption limited to 150mA
(HDD connection not allowed)
Power
1 x Plug-in screw terminal block (3 poles)
9 to 36VDC +/-10%, Max.: 140mA.
24VAC +/-10% 50-60Hz, Max.: 127mA
Recommended: 24VDC
Push Button
Button A: Check the user manual
Button B: Check the user manual
Operation
Temperature
0°C to +60°C
Ethernet
1 x Ethernet 10/100 Mbps RJ45
2 x Ethernet LED: port link and activity
Operational
Humidity
5 to 95%, no condensation
Port A
1 x Serial EIA485 Plug-in screw terminal block (2 poles)
A, B
1 x Plug-in screw terminal block green (2 poles)
SGND (Reference ground or shield)
1500VDC isolation from others ports
Protection
IP20 (IEC60529)
LED
Indicators
10 x On board LED indicators
1 x Error LED
1 x Power LED
2 x Ethernet Link/Speed
2 x Port A TX/RX
2 x Port B TX/RX
1 x Button A indicator
1 x Button B indicator
Switch A
(SWA)
1 x DIP-Switch for serial EIA485 configuration:
Position 1:
ON: 120 Ω termination active
Off: 120 Ω termination inactive
Position 2-3:
ON: Polarization active
Off: Polarization inactive
PORT B
1 x Serial EIA232 (SUB-D9 male connector)
Pinout from a DTE device
1500VDC isolation from other ports
(except PORT B: EIA485)
1 x Serial EIA485 Plug-in screw terminal block (3 poles)
A, B, SGND (Reference ground or shield)
1500VDC isolation from other ports
(except PORT B: EIA232)
Switch B
SWB)
1 x DIP-Switch for serial EIA485 configuration:
Position 1:
ON: 120 Ω termination active
Off: 120 Ω termination inactive
Position 2-3:
ON: Polarization active
Off: Polarization inactive
IntesisTM BACnet Server – Modbus Client User Manual r1.9 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
44 / 44
10 Dimensions
Recommended available space for its installation into a cabinet (wall or DIN rail mounting), with space enough for
external connections
100 mm (h)
100 mm (w)
130 mm (d)
56 mm (h)
88 mm (w)
90 mm (d)
Loading...