HMS intesis BACnet User manual

BACnet Server
Modbus RTU Master and Modbus TCP Client
USER MANUAL
Issue date: 08/2021 r1.10 ENGLISH

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
2 / 41
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.

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
3 / 41
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

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
4 / 41
INDEX
1Description ...............................................................................................................................................6
Introduction.......................................................................................................................................6
Functionality .....................................................................................................................................8
Gateway’s capacity ..........................................................................................................................8
2Protocol 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
3BACnet Interoperability Building Blocks Supported (BIBBs) .................................................................11
Data Sharing BIBBs .......................................................................................................................11
Alarm and Event Management BIBBs............................................................................................11
Scheduling BIBBs...........................................................................................................................11
Trending BIBBs ..............................................................................................................................11
Device Management BIBBs ...........................................................................................................11
4Service Types ........................................................................................................................................12
5Objects...................................................................................................................................................13
Supported Object Types.................................................................................................................13
Objects and properties ...................................................................................................................14
5.2.1 INBACMBM---0000 (Device Object Type)..............................................................................14
5.2.2 Analog Input Object Type.......................................................................................................16
5.2.3 Analog Output Object Type ....................................................................................................17
5.2.4 Analog Value Object Type......................................................................................................18
5.2.5 Binary Input Object Type........................................................................................................19
5.2.6 Binary Output Object Type .....................................................................................................20
5.2.7 Binary Value Object Type.......................................................................................................21
5.2.8 Multistate Input Object Type...................................................................................................22
5.2.9 Multistate Output Object Type................................................................................................23
5.2.10 Multistate Value Object Type..................................................................................................24
5.2.11 Notification Class Object Type ...............................................................................................25
5.2.12 Calendar Object Type.............................................................................................................25
5.2.13 Schedule Object Type ............................................................................................................26
5.2.14 Trend Log Object Type...........................................................................................................27
5.2.15 Trend Log Multiple Object Type .............................................................................................28
6Connections ...........................................................................................................................................29
Powering the device.......................................................................................................................30
Connection to BACnet....................................................................................................................30
6.2.1 BACnet IP...............................................................................................................................30
6.2.2 BACnet MSTP ........................................................................................................................30
Connection to Modbus ...................................................................................................................31
6.3.1 Modbus TCP...........................................................................................................................31
6.3.2 Modbus RTU...........................................................................................................................31
Connection to the configuration tool...............................................................................................31
7Status LEDs and push buttons ..............................................................................................................32
8Set-up process and troubleshooting ......................................................................................................33
Pre-requisites .................................................................................................................................33
Intesis MAPS. Configuration & monitoring tool for Intesis BACnet series .....................................33
7.2.1 Introduction.............................................................................................................................33
7.2.2 Connection..............................................................................................................................33
7.2.3 Configuration tab ....................................................................................................................35
7.2.4 Signals....................................................................................................................................35
7.2.5 Sending the configuration to Intesis .......................................................................................36
7.2.6 Diagnostic...............................................................................................................................37
Set-up procedure............................................................................................................................39
9Electrical & Mechanical Features...........................................................................................................40
10 Dimensions ............................................................................................................................................41

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
5 / 41

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
6 / 41
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

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
7 / 41
Integration of Modbus RTU Slaves or Modbus TCP Servers
to BACnet IP control and monitoring systems

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
8 / 41
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 RS-
485 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

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
9 / 41
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.1.4.0
Firmware Revision: 14.1.2.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:

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
10 / 41
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.

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
11 / 41
3 BACnet Interoperability Building Blocks Supported (BIBBs)
Data Sharing BIBBs
BIBB Type
BACnet Service
Initiate
Execute
DS-RP-B
Data Sharing-ReadProperty–B
ReadProperty
DS-RPM-B
Data Sharing-ReadPropertyMultiple–B
ReadPropertyMultiple
DS-WP-B
Data Sharing-WriteProperty–B
WriteProperty
DS-WPM-B
Data Sharing-WritePropertyMultiple–B
WritePropertyMultiple
DS-COV-B
Data Sharing-COV–B
SubscribeCOV
ConfirmedCOVNotification
UnconfirmedCOVNotification
Alarm and Event Management BIBBs
BIBB Type
BACnet Service
Initiate
Execute
AE-N-I-B
Alarm and Event-Notification Internal–B
ConfirmedEventNotification
UnconfirmedEventNotification
AE-ACK-B
Alarm and Event-ACK–B
AcknowledgeAlarm
AE-ASUM-B
Alarm and Event-Alarm Summary–B
GetAlarmSummary
AE-INFO-B
Alarm and Event-Information–B
GetEventInformation
Scheduling BIBBs
Trending BIBBs
Device Management BIBBs
BIBB Type
BACnet Service
Initiate
Execute
SCHED-I-B
Scheduling-Internal–B
BIBB Type
BACnet Service
Initiate
Execute
T-VMT-I-B
Trending - Viewing and Modifying Trends Inernal–B
ReadRange
T-VMMV-I-B
Trending - Viewing and Modifying Multiple Vaues Inernal–B
ConfirmedEventNotification
ReadRange
BIBB Type
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-B
Device Management - Dynamic Object Binding–B
Who-Has
I-Have
DM-DCC-B
Device Management - DeviceCommunicationControl–B
DeviceCommunicationControl
DM-TS-B
Device Management - TimeSynchronization–B
TimeSynchronization
DM-RD-B
Device Management - ReinitializeDevice–B
ReinitializeDevice

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
12 / 41
4 Service Types
Service type
Service name
Remarks
Alarm and Event Services
AcknowledgeAlarm
Execute
ConfirmedCOVNotification
Initiate
ConfirmedEventNotification
Initiate
GetAlarmSummary
Execute
SubscribeCOV
Execute
Object Access Services
ReadProperty
Execute
ReadPropertyMultiple
Execute
ReadRange
Execute
WriteProperty
Execute
WritePropertyMultiple
Execute
Remote Device Management
Services
DeviceCommunicationControl
Execute
ReinitializeDevice
Execute
Unconfirmed Services
I-Am
Execute / Initiate
I-Have
Initiate
UnconfirmedCOVNotification
Initiate
UnconfirmedEventNotification
Initiate
TimeSynchronization
Execute
Who-Has
Execute
Who-Is
Execute / Initiate
GetEventInformation
Execute

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
13 / 41
5 Objects
Supported Object Types
The objects supported are shown in the table below.
Object Type
ID
Analog-Input
0
Analog-Output
1
Analog-Value
2
Binary-Input
3
Binary-Output
4
Binary-Value
5
Calendar
6
Device
8
Multistate-Input
13
Multistate-Output
14
Multistate-Value
19
Notification-Class
15
Schedule
17
Trend-Log
20
Trend-Log-Multiple
27

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
14 / 41
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
Configurable through BACnet and Config Tool
R
R
Object_Type
BACnetObjectType
DEVICE (8) (Device Object Type)
R
R
System_Status
BACnetDeviceStatus
OPERATIONAL (0)
R
R
Vendor_Name
CharacterString
" Intesis Software, SLU "
R
R
Vendor_Identifier
Unsigned16
246
R
R
Model_Name
CharacterString
"IN-BAC-MBM "
R
R
Description
CharacterString
“Modbus to BACnet Gateway”
O
R
Firmware_Revision
CharacterString
"14.1.2.0"
R
R
Application_Software_
Version
CharacterString
"1.x.x.x"
R
R
Protocol_Version
Unsigned
1
R
R
Protocol_Revision
Unsigned
14
R
R
Protocol_Services_
Supported
BACnetServiceSupported
Refer to section 4 [Service Types]
R
R
Protocol_Object_Types_
Supported
BACnetObjectTypes
Supported
Refer to section 5 [Object Types]
R
R
Object_List
BACnetArray[N] of
BACnetObjectIdentifier
BACnetARRAY[N]
R
R
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
Local_Date
Date
Current date
O
R
Local_Time
Time
Current time
O
R
APDU_Segment_Timeout
Unsigned
3000
R
R
APDU_Timeout
Unsigned
3000
R
R
Number_of_APDU_
Retries
Unsigned
3
R
R
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
-

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
15 / 41
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.

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
16 / 41
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 Config Tool
R
R
Object_Type
BACnetObjectType
ANALOG_INPUT (0)
R
R
Present_Value
REAL
x
R
R
Description
CharacterString
Configurable through Config Tool
O
R2
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
Units
BACnetEngineeringUnits
Configurable through Config Tool
R
R
COV_Increment
REAL
0
O
W
Time_Delay
Unsigned
-
O
R
1
Notification_Class
Unsigned
-
O
R
1
High_Limit
REAL
-
O
R
1
Low_Limit
REAL
-
O
R
1
Deadband
REAL
-
O
R
1
Limit_Enable
BACnetLimitEnable
-
O
R
1
Event_Enable
BACnetEventTransitionBit
s
{TRUE, TRUE, TRUE}
O
R
1
Acked_Transitions
BACnetEventTransitionBit
s
-
O
R
1
Notify_Type
BACnetNotifyType
-
O
R
1
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
-
O
R
1
Event_Detection_Enable
BOOLEAN
-
O
R
Property_List
BACnetARRAY[N] of
BACnetPropertyIdentifier
-
R
R
1Only available when specific object has a Notification Class configured
2 Only available in some models after activations on the configuration tool, review the specific model manual for
details.

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
17 / 41
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 Config Tool
R
R
Object_Type
BACnetObjectType
ANALOG_OUTPUT (1)
R
R
Present_Value
REAL
x
W
W
Description
CharacterString
Configurable through Config
Tool
O
R2
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
Units
BACnetEngineeringUnits
Configurable through Config Tool
R
R
Priority_Array
BACnetPriorityArray
BACnetPriorityArray
R
R
Relinquish_Default
Unsigned
Configurable through BACnet and Config Tool
W
W
COV_Increment
REAL
0
O
W
Time_Delay
Unsigned
-
O
R
1
Notification_Class
Unsigned
-
O
R
1
High_Limit
REAL
-
O
R
1
Low_Limit
REAL
-
O
R
1
Deadband
REAL
-
O
R
1
Limit_Enable
BACnetLimitEnable
-
O
R
1
Event_Enable
BACnetEventTransitionBits
{TRUE, TRUE, TRUE}
O
R
1
Acked_Transitions
BACnetEventTransitionBits
-
O
R
1
Notify_Type
BACnetNotifyType
-
O
R
1
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
-
O
R
1
Event_Detection_Enable
BOOLEAN
-
O
R
Property_List
BACnetARRAY[N] of
BACnetPropertyIdentifier
-
R
R
1Only available when specific object has a Notification Class configured
2 Only available in some models after activations on the configuration tool, review the specific model manual for
details

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
18 / 41
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 Config Tool
R
R
Object_Type
BACnetObjectType
ANALOG_VALUE (2)
R
R
Present_Value
REAL
x
R
W
Description
CharacterString
Configurable through Config Tool
O
R2
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
Units
BACnetEngineeringUnits
Configurable through Config Tool
R
R
COV_Increment
REAL
0
O
W
Time_Delay
Unsigned
-
O
R
1
Notification_Class
Unsigned
-
O
R
1
High_Limit
REAL
-
O
R
1
Low_Limit
REAL
-
O
R
1
Deadband
REAL
-
O
R
1
Limit_Enable
BACnetLimitEnable
-
O
R
1
Event_Enable
BACnetEventTransitionBits
{TRUE, TRUE, TRUE}
O
R
1
Acked_Transitions
BACnetEventTransitionBits
-
O
R
1
Notify_Type
BACnetNotifyType
-
O
R
1
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
-
O
R
1
Event_Detection_Enable
BOOLEAN
-
O
R
Property_List
BACnetARRAY[N] of
BACnetPropertyIdentifier
-
R
R
1Only available when specific object has a Notification Class configured
2 Only available in some models after activations on the configuration tool, review the specific model manual for
details

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
19 / 41
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 Config Tool
R
R
Object_Type
BACnetObjectType
BINARY_INPUT (3)
R
R
Present_Value
BACnetBinaryPV
INACTIVE (0) / ACTIVE (1)
R
R
Description
CharacterString
Configurable through Config Tool
O
R2
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 Config Tool
O
R
Active_Text
CharacterString
Configurable through Config Tool
O
R
Time_Delay
Unsigned
-
O
R
1
Notification_Class
Unsigned
-
O
R
1
Alarm_Value
BACnetBinaryPV
-
O
R
1
Event_Enable
BACnetEventTransitionBits
-
O
R
1
Acked_Transitions
BACnetEventTransitionBits
-
O
R
1
Notify_Type
BACnetNotifyType
-
O
R
1
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
-
O
R
1
Event_Detection_Enable
BOOLEAN
-
O
R
Property_List
BACnetARRAY[N] of
BACnetPropertyIdentifier
-
R
R
1Only available when specific object has a Notification Class configured
2 Only available in some models after activations on the configuration tool, review the specific model manual for
details

BACnet Server –Modbus Client User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL https://www.intesis.com
20 / 41
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 Config Tool
R
R
Object_Type
BACnetObjectType
BINARY_OUTPUT (4)
R
R
Present_Value
BACnetBinaryPV
INACTIVE (0) / ACTIVE (1)
W
W
Description
CharacterString
Configurable through Config Tool
O
R2
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 Config Tool
O
R
Active_Text
CharacterString
Configurable through Config Tool
O
R
Priority_Array
BACnetPriorityArray
BACnetPriorityArray
R
R
Relinquish_Default
BACnetBinaryPV
INACTIVE (0)
R
W
Time_Delay
Unsigned
-
O
R
1
Notification_Class
Unsigned
-
O
R
1
Event_Enable
BACnetEventTransitionBits
{TRUE, TRUE, TRUE}
O
R
1
Feedback_Value
BACnetBinaryPV
-
O
W
Acked_Transitions
BACnetEventTransitionBits
-
O
R
1
Notify_Type
BACnetNotifyType
-
O
R
1
Event_Time_Stamps
BACnetArray[N] of
BACnetTimeStamp
-
O
R
1
Event_Detection_Enable
BOOLEAN
-
O
R
Property_List
BACnetARRAY[N] of
BACnetPropertyIdentifier
-
R
R
1Only available when specific object has a Notification Class configured
2 Only available in some models after activations on the configuration tool, review the specific model manual for
details