FieldServer FS-8704-06 Release note

Driver Version:
2.01
Document Revision:
4
A Sierra Monitor Company
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after March 2011
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8704-06 BACnet/IP

FS-8704-06 BACnet IP Driver Manual Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
TABLE OF CONTENTS
1BACnet IP Description .................................................................................................................................... 4
1.1 BTL Mark –BACnet Testing Laboratory ............................................................................................................ 4
2Driver Scope of Supply ................................................................................................................................... 5
2.1 Supplied by FieldServer Technologies for this driver....................................................................................... 5
2.2 Provided by the Supplier of 3rd Party Equipment ............................................................................................ 5
2.2.1 Hardware .................................................................................................................................................5
3Hardware Connections................................................................................................................................... 6
4Data Array Parameters................................................................................................................................... 7
5Configuring the FieldServer as a BACnet IP Client........................................................................................... 8
5.1 Client Side Connection Parameters................................................................................................................... 8
5.2 Client Side Node Parameters............................................................................................................................. 9
5.3 Client Side Map Descriptor Parameters............................................................................................................ 9
5.3.1 FieldServer Specific Map Descriptor Parameters .....................................................................................9
5.3.2 Driver Specific Map Descriptor Parameters ...........................................................................................10
5.3.3 Timing Parameters.................................................................................................................................11
5.3.4 Map Descriptor Example........................................................................................................................12
6Configuring the FieldServer as a BACnet IP Server........................................................................................ 13
6.1 Driver Specific FieldServer Parameters........................................................................................................... 13
6.2 Server Side Connection Parameters ............................................................................................................... 14
6.3 Server Side Node Parameters.......................................................................................................................... 14
6.4 Server Side Map Descriptor Parameters ........................................................................................................ 15
6.4.1 FieldServer Specific Map Descriptor Parameters ...................................................................................15
6.4.2 Driver Specific Map Descriptor Parameters ...........................................................................................16
6.4.3 Map Descriptor Example........................................................................................................................18
Appendix A. Useful Features................................................................................................................................ 19
Appendix A.1. BACnet object names............................................................................................................................. 19
Appendix A.2. Network number.................................................................................................................................... 19
Appendix A.3. Accessing Data from BACnet Properties comprising Arrays of Values .............................................. 20
Appendix A.4. FieldServer implementation of BACnet priority Arrays....................................................................... 20
Appendix A.4.1. Accessing Priority Array information......................................................................................21
Appendix A.5. Relinquishing Control of a Point as a Client ......................................................................................... 21
Appendix A.6. Using BBMD............................................................................................................................................ 22
Appendix A.6.1. Setting up a Broadcast Distribution Table (BDT)....................................................................22
Appendix A.6.2. BBMD Configuration Example................................................................................................22
Appendix A.7. BACnet State Text Preload .................................................................................................................... 26
Appendix A.7.1. Method 1 –Using an Offset/User Table:................................................................................26
Appendix A.7.2. Method 2 –Using a Single Data Array:..................................................................................27
Appendix A.7.3. Using Intrinsic Reporting for a Multistate Value....................................................................28
Appendix A.8. COV and Intrinsic Reporting .................................................................................................................. 28
Appendix A.8.1. Notes on COV configuration:..................................................................................................28
Appendix A.8.2. Notes on Intrinsic Reporting configuration: ...........................................................................29
Appendix A.8.3. Node Configuration Example - Enable or Disable COV...........................................................30
Appendix A.8.4. Map Descriptor Example - COV ..............................................................................................30
Appendix A.8.5. Map Descriptor Example –Intrinsic Reporting.......................................................................30

FS-8704-06 BACnet IP Driver Manual Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
Appendix A.8.6. Setting the Priority of Intrinsic Alarming................................................................................31
Appendix A.8.7. Map Descriptor Example –Set up a Permanent Static Recipient List ....................................32
Appendix A.9. Factors Determining the Reliability Property....................................................................................... 33
Appendix A.10. Specifying ReadPropertyMultiple and WritePropertyMultiple Transactions using Linked Map
Descriptors ...................................................................................................................................................................... 34
Appendix A.11. Update Property Function................................................................................................................... 37
Appendix A.11.1. Supported values:.................................................................................................................37
Appendix A.11.2. Mode of Operation when used for the Relinquish_Default property: ..................................37
Appendix A.11.3. Update Property Configuration Example: ............................................................................38
Appendix A.12. Disabling selected BACnet services .................................................................................................... 39
Appendix A.13. Using a .ini file to set the Vendor_ID and Vendor_Name of the Device Object ............................. 39
Appendix B. Troubleshooting............................................................................................................................... 40
Appendix B.1. Debugging a BACnet connection........................................................................................................... 40
Appendix B.2. COV Configuration ................................................................................................................................. 40
Appendix B.3. BACnet Specific Statistics....................................................................................................................... 40
Appendix B.4. BACnet Specific Error Messages............................................................................................................ 41
Appendix B.5. BACnet Error Response Decoding ......................................................................................................... 41
Appendix B.5.1. BACnet Error CLASS ................................................................................................................41
Appendix B.5.2. BACnet Error CODES for Error Class OBJECT...........................................................................42
Appendix C. Vendor Information ......................................................................................................................... 43
Appendix C.1. McQuay................................................................................................................................................... 43
Appendix C.2. Trane ....................................................................................................................................................... 43
Appendix C.2.1. Enabling Trane Alarming ........................................................................................................43
Appendix C.2.2. Example 1 –Analog input.......................................................................................................44
Appendix C.2.3. Example 2 –Binary Input........................................................................................................44
Appendix C.3. Liebert ..................................................................................................................................................... 45
Appendix C.4. Honeywell EBI......................................................................................................................................... 45
Appendix C.5. Using Cimetrics Explorer........................................................................................................................ 45
Appendix C.6. Trending using OniconTrend Log Objects............................................................................................. 46
Appendix C.6.1. Operating Statistics ................................................................................................................47
Appendix C.6.2. Date and Time Synchronization..............................................................................................48
Appendix D. Reference ........................................................................................................................................ 49
Appendix D.1. FieldServer Vendor ID............................................................................................................................ 49
Appendix D.2. Object_Type Legal Values –Abbreviation Descriptions...................................................................... 49
Appendix D.3. Property Legal Values ............................................................................................................................ 49
Appendix D.4. Units........................................................................................................................................................ 51

FS-8704-06 BACnet IP Driver Manual Page 4 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
1BACNET IP DESCRIPTION
The BACnet/IP driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet/IP
protocol. The FieldServer can emulate either a Server or Client.
All information in a BACnet system is represented in terms of objects. The Object_Identifier is a 32-bit code that
identifies the type of Object (also identified by the Object_Type Property) and its "Instance" number, which
together uniquely identify the Object within its BACnet device. Theoretically, a BACnet device could have over four
million Objects of a particular type. The Object_Name is a text string, which has a unique capability. BACnet
devices may broadcast queries for devices that contain Objects with a specific Object_Name. This can greatly
simplify project setup.
BACnet requires one Device Object to be present in every BACnet device. The Device Object makes information
about the device and its capabilities available to other devices on the networks. Before one BACnet device starts
control-related communications with another, it needs to obtain some of the information presented by the other
device's Device Object. Unlike other Objects, the Device Object's Instance number must be unique across the
entire BACnet internetwork because it is used to uniquely identify the BACnet devices. It may be used to
conveniently identify the BACnet device from other devices during installation.
Standard object types are used to hold real time data and other information. Each Object Type is referenced by a
number, for example 0 represents an Analog Input.
Each Object consists of a number of prescribed properties, the main property being the Present_Value. Objects
are monitored and controlled through their properties. The Analog Input Object is representative of the Objects
involved directly with control elements and many of its Properties reflect this.
The information that follows describes how to expand upon the factory defaults provided in the configuration files
included with the FieldServer.
1.1 BTL Mark –BACnet Testing Laboratory
The BTL mark is a symbol that indicates to a consumer that a product has passed a
series of rigorous tests conducted by an independent laboratory which verifies that the
product correctly implements the BACnet features claimed in the listing. The mark is a
symbol of a high-quality BACnet product. For more information about the BACnet
Testing Laboratory go to: http://www.bacnetinternational.net/btl/.

FS-8704-06 BACnet IP Driver Manual Page 5 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
2DRIVER SCOPE OF SUPPLY
2.1 Supplied by FieldServer Technologies for this driver
FieldServer Technologies PART #
Description
FS-8915-10
UTP cable (7 foot) for Ethernet connection1
2.2 Provided by the Supplier of 3rd Party Equipment
2.2.1 Hardware
Part #
Description
Ethernet 10/100 BaseT hub2
1
This cable is necessary for connection to the driver. It is shipped with the FieldServer and not separately with the driver.
2
Not all FieldServer models support 100BaseT. Consult the appropriate instruction manual for details of the Ethernet speed supported by
specific hardware.

FS-8704-06 BACnet IP Driver Manual Page 6 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
3HARDWARE CONNECTIONS
It is possible to connect a BACnet/IP device using the N1 or the N2
3
network ports. These ports need to be
configured for BACnet/IP in the configuration file.
Configure the Controller according to manufacturer’s instructions
FieldServer
FieldServer Part #
8915-10
UTP cable
Connect to an Ethernet Port
on the FieldServer
N1
18
Hub/Router
Remote BACnet IP
Device
3
Not all ports shown are necessarily available on the hardware. Consult the appropriate Instruction manual for details of the ports available on
specific hardware.

FS-8704-06 BACnet IP Driver Manual Page 7 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
4DATA ARRAY PARAMETERS
Data Arrays are “protocol neutral” data buffers for storage of data to be passed between protocols. It is necessary
to declare the data format of each of the Data Arrays to facilitate correct storage of the relevant data.
Section Title
Data_Arrays
Column Title
Function
Legal Values
Data_Array_Name
Provide name for Data Array
Up to 15 alphanumeric
characters
Data_Array_Format
Provide data format. Each Data Array can only take on one
format.
Float, Bit, Uint16, Uint32,
Sint16, Sint32, Byte
Data_Array_Length
Number of Data Objects. Must be larger than the data
storage area required by the Map Descriptors for data placed
in this array.
1-10, 000
Example
// Data Arrays
Data_Arrays
Data_Array_Name
, Data_Array_Format
, Data_Array_Length
DA_AI_01
, Float
, 200
DA_AO_01
, Float
, 200
DA_DI_01
, Bit
, 200
DA_DO_01
, Bit
, 200

FS-8704-06 BACnet IP Driver Manual Page 8 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
5CONFIGURING THE FIELDSERVER AS A BACNET IP CLIENT
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The
information that follows describes how to expand upon the factory defaults provided in the configuration files
included with the FieldServer (See “.csv” sample files provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to communicate
with a BACnet/IP Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable
the FieldServer for BACnet/IP communications, the driver independent FieldServer buffers need to be declared in
the “Data Arrays” section, the destination device addresses need to be declared in the “Client Side Nodes” section,
and the data required from the Servers needs to be mapped in the “Client Side Map Descriptors” section. Details
on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
5.1 Client Side Connection Parameters
Section Title
Connection
Column Title
Function
Legal Values
Adapter
Adapter Name
N1, N24
Protocol
Specify protocol used
BACnet_IP
Poll_Delay*
Time between internal polls
0-32000s; 0.25s
IP_Port*
Specify the UDP port that will be used to communicate
with other BACnet Client devices.
Any legal IP port value (1 - 65535);
47808
Example
// Client Side Connections
Connections
Adapter
, Protocol
, Poll_Delay
N1
, Bacnet_IP
, 0500s
4
Consult the appropriate Instruction manual for details of the ports available on specific hardware.

FS-8704-06 BACnet IP Driver Manual Page 9 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
5.2 Client Side Node Parameters
Section Title
Nodes
Column Title
Function
Legal Values
Node_Name
Provide name for Node
Up to 31 alphanumeric characters
Node_ID
BACnet device identifier of physical Server Node
0 - 4194303
Protocol
Specify protocol used
BACnet_IP
Adapter
Specify port Adapter used
N1, N24
Retries*
Number of timeouts before the Node goes offline.
0,1,2,3
Example
// Client Side Nodes
Nodes
Node_Name
, Node_ID
, Protocol
, Adapter
, Retries
DEV_01
, 1
, Bacnet_IP
, N1,
, 2
5.3 Client Side Map Descriptor Parameters
5.3.1 FieldServer Specific Map Descriptor Parameters
Section Title
Map Descriptors
Column Title
Function
Legal Values
Map_Descriptor_Name
Name of this Map Descriptor. This is used for
Object_Name Property. Refer to Appendix A.1.
Up to 37 alphanumeric
characters
Data_Array_Name
Name of Data Array where data is to be stored in
the FieldServer
One of the Data Array names
from Section 4.
Data_Array_Offset
Starting location in Data Array
0 to (Data_Array_Length-1) as
specified in Section 4
Function
Function of Client Map Descriptor. Refer to the
FieldServer Configuration manual for more
information.
Rdbc, Wrbc, Wrbx, Arcs

FS-8704-06 BACnet IP Driver Manual Page 10 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
5.3.2 Driver Specific Map Descriptor Parameters
Section Title
Map Descriptors
Column Title
Function
Legal Values
Node_Name
Name of remote Server Node.
One of the Node_Names
specified in Section 5.2
Object_Type
(Alias = Data_Type)
Type of object. Refer to Appendix D.1 for more
information.
AI, AO, AV, BI, BO, BV, MI, MO,
MV, NC
Object_Instance
(Alias = Address)
Instance of the object on the device.
0, 1, 2, 3, …4194303
Property
The BACnet property to be read.
Refer to Appendix D.3
Data_Array_Low_Scale*
Scaling zero in Data Array
-32767 to 32767, 0
Data_Array_High_Scale*
Scaling max in Data Array
-32767 to 32767, 100
Node_Low_Scale*
Scaling zero in Connected Node
-32767 to 32767, 0
Node_High_Scale*
Scaling max in Connected Node
-32767 to 32767, 100
Length*
Used to create an array of sequential
Object_Instances on an Object_Type.
1 to max point count of the
FieldServer, 1
Array_Index*
When referencing Multistate properties, allows
the user to specify the index of the property to
be read. If 1 is specified, the first one will be
read, if 2 is specified, the second will be read,
etc. If 0 is specified, the driver will return the
total number (count) of array items linked to
the property. If the parameter is not specified,
a list of all items will be returned. Refer to
Appendix A.3
0 to max number of array items
in the BACnet Property, -
Write_Priority*
Allows the driver to specify the write priority
used to write an output.
1..16, 16
Linked_Map_Descriptors*
This parameter allows the linking of Map
Descriptors to an active read or write Map
Descriptor in order to construct a
ReadPropertyMultiple or WritePropertyMultiple
transaction. Refer to Appendix A.10
The name of a previously defined
active Map Descriptor, -
Length*
When the optional Length parameter is set to a
value N, the Map Descriptor will include N
consecutive instances of the specified
Object_Type. For example, if a Map Descriptor
specifies Object_Type, Address 4 and Length 3,
this means that the AO instances 4, 5 and 6 will
be included in the read or write transaction. The
corresponding Data Array values are in
consecutive positions in the Data Array, starting
at the specified Data_Array_Offset.
Any positive integer that falls
between the range of the
Data_Array_Offset and the
Data_Array_Length as specified
in section 4, -
Refer also to Appendix A.10

FS-8704-06 BACnet IP Driver Manual Page 11 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: s[email protected]
5.3.3 Timing Parameters
Section Title
Map Descriptors
Column Title
Function
Legal Values
Scan_Interval*
Rate at which data is polled
0-32000s, 2s

FS-8704-06 BACnet IP Driver Manual Page 12 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
5.3.4 Map Descriptor Example
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Object_Type
, Object_Instance
, Property
, Scan_Interval
CMD_AI_01
, DA_AI_01
, 0
, Rdbc
, DEV_01
, AI
, 1
, Present_Value
, 20.000s
CMD_AI_02
, DA_AI_01
, 1
, Rdbc
, DEV_01
, AI
, 2
, Present_Value
, 20.000s
CMD_AI_03
, DA_AI_01
, 2
, Rdbc
, DEV_01
, AI
, 3
, Present_Value
, 20.000s
CMD_AO_01
, DA_AO_01
, 0
, Rdbc
, DEV_01
, AO
, 1
, Present_Value
, 30.000s
CMD_AO_02
, DA_AO_01
, 1
, Rdbc
, DEV_01
, AO
, 2
, Present_Value
, 30.000s
CMD_AO_03
, DA_AO_01
, 2
, Rdbc
, DEV_01
, AO
, 3
, Present_Value
, 30.000s
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Object_Type
, Object_Instance
, Property
, Scan_Interval
CMD_DI_01
, DA_DI_01
, 0
, Rdbc
, DEV_01
, BI
, 1
, Present_Value
, 15.000s
CMD_DI_02
, DA_DI_01
, 1
, Rdbc
, DEV_01
, BI
, 2
, Present_Value
, 15.000s
CMD_DI_03
, DA_DI_01
, 2
, Rdbc
, DEV_01
, BI
, 3
, Present_Value
, 15.000s
CMD_DO_01
, DA_DO_01
, 0
, Rdbc
, DEV_01
, BO
, 1
, Present_Value
, 30.000s
CMD_DO_02
, DA_DO_01
, 1
, Rdbc
, DEV_01
, BO
, 2
, Present_Value
, 30.000s
CMD_DO_03
, DA_DO_01
, 2
, Rdbc
, DEV_01
, BO
, 3
, Present_Value
, 30.000s

FS-8704-06 BACnet IP Driver Manual Page 13 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: s[email protected]
6CONFIGURING THE FIELDSERVER AS A BACNET IP SERVER
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The
information that follows describes how to expand upon the factory defaults provided in the configuration files
included with the FieldServer (See “.csv” files provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to communicate
with a BACnet/IP Client.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable
the FieldServer for BACnet/IP communications, the driver independent FieldServer buffers need to be declared in
the “Data Arrays” section, the FieldServer virtual node(s) needs to be declared in the “Server Side Nodes” section,
and the data to be provided to the Clients needs to be mapped in the “Server Side Map Descriptors” section.
Details on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
6.1 Driver Specific FieldServer Parameters
Section Title
Bridge
Column Title
Function
Legal Values
Title
FieldServer name
Text
Network_Number*
Specify a unique network number if there are multiple virtual Server
Nodes. Refer to Appendix A.2
1 –65535, 5
Example
// FieldServer Driver specific parameters
Bridge
Title
BACnet Server

FS-8704-06 BACnet IP Driver Manual Page 14 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: s[email protected]
6.2 Server Side Connection Parameters
Section Title
Connections
Column Title
Function
Legal Values
Adapter
Adapter Name
N1, N25
Protocol
Specify protocol used
BACnet_IP
Connection_Type*
Specify if this Connection should act as a BBMD Server on the
network. Refer to Appendix A.5 for more information.
BBMD, -
IP_Port*
Specify the UDP port that will be used to communicate with
other BACnet Client devices.
Any legal IP port value (1
- 65535); 47808
Example
// Server Side Connections
Connections
Adapter
, Protocol
, Connection_Type
N1
, Bacnet_IP
, BBMD
6.3 Server Side Node Parameters
Section Title
Nodes
Column Title
Function
Legal Values
Node_Name
Provide name for Node
Up to 31
alphanumeric
characters
Node_ID
BACnet station address of physical Server node
0 - 4194303
Protocol
Specify protocol used
BACnet_IP
Node_Option*
Enable or disable COV for this Node. Refer to Appendix A.8 for
further information.
COV_Enable,
COV_Disable, -
Node_Type*
Specific to Trane applications. The Node type can be defined.
Refer to Appendix C.2
BCU, Summit
Workstation, -
Disabled_Services*
Certain BACnet Services can be disabled on a BACnet Server Node
when specific requirements necessitate this. Refer to Appendix
A.12 for more information.
-, WPM, COV
Model_Name*
Sets the Model Name Property of the Device Object
Up to 32
alphanumeric
characters
5
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.

FS-8704-06 BACnet IP Driver Manual Page 15 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: s[email protected]
Example
// Server Side Nodes
Nodes
Node_Name
, Node_ID
, Protocol
, Node_Option
, Model_Name
6
Virtual_DEV_11
, 11
, Bacnet_IP
, COV_Enable
, WBA11M. MSTP BACnet-IP
6.4 Server Side Map Descriptor Parameters
6.4.1 FieldServer Specific Map Descriptor Parameters
Section Title
Map Descriptors
Column Title
Function
Legal Values
Map_Descriptor_Name
Name of this Map Descriptor. This is used for
Object_Name Property. Refer to Appendix A.1.
Up to 37 alphanumeric characters
Data_Array_Name
Name of Data Array where data is to be stored
in the FieldServer
One of the Data Array names from
Section 4
Data_Array_Offset
Starting location in Data Array
0 to (“Data_Array_Length” -1) as
specified in Section 4
Function
Function of Server Map Descriptor
Passive
6
Note that adapter is not declared under Server Side Nodes.

FS-8704-06 BACnet IP Driver Manual Page 16 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: s[email protected]
6.4.2 Driver Specific Map Descriptor Parameters
Section Title
Map Descriptors
Column Title
Function
Legal Values
Node_Name
Name of Node to fetch data from
One of the Node Names
specified in Section 6.3
Object_Type
(Alias = Data_Type)
Data type in Controller
AI, AO, AV, BI, BO, BV, MI, MO,
MV, NC. Refer to Appendix
D.1.
Object_Instance
(Alias = Address)
Instance of the Object on the Device.
0, 1, 2, 3, …4194303
Units*
The object units
Refer to Appendix D.4, m2
Data_Array_Low_Scale*
Scaling zero in Data Array
-32767 to 32767, 0
Data_Array_High_Scale*
Scaling max in Data Array
-32767 to 32767, 100
Node_Low_Scale*
Scaling zero in Connected Node
-32767 to 32767, 0
Node_High_Scale*
Scaling max in Connected Node
-32767 to 32767, 100
Active_Text7*
Specify the Active Text property of the Object
Any text string of length up to
40 characters, Active
Inactive_Text7*
Specify the Inactive Text property of the Object
Any text string of length up to
40 characters, Inactive
Relinquish_Default7
Specify the value to be returned as Present_Value
on startup or when control is relinquished. Must be
specified for outputs. Refer to Appendix D.3
Any Float value
Length*
Used to create an array of sequential
Object_Instances on an Object_Type.
1 to max point count of the
FieldServer, 1
Notification_Class*
Specify the Mapdescriptor_Name of the
Notification_Class Object that manages Intrinsic
Reporting for this Map Descriptor. Refer to
Appendix A.8.
One of the configured
Mapdescriptor_Names of type
NC (Notification Class).
Objects are not available to
any NC if left out.
Ack_Required*
For a Notification_Class Object, specify whether
EventNotifications require a user
Acknowledgement. Refer to Appendix A.8.
Yes, No
COV_Increment*
For a Server Map Descriptor of type AO or AI,
initialize the COV_Increment property. Refer to
Appendix A.8.
Any Float value, 0
Input_alarm_State*
For binary points the user can specify which of the
states (0 or 1) to regard as an alarm state.
0, 1
7
See the BACnet DFS to determine if a particular object supports this property

FS-8704-06 BACnet IP Driver Manual Page 17 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: s[email protected]
Section Title
Map Descriptors
Column Title
Function
Legal Values
Description*
Specify the object’s description property.
E.g. Room Temp –Refer to Appendix A.8.3
Any text string of length up to
40 characters, If not
configured, defaults to
Object_Name.
Update_Property*
The Update_Property Parameter may be configured
on a BACnet Server Map Descriptor to allow a
property other than the Present_Value to be
updated in addition to the Present_Value when the
Data Array Value changes. Warning: This is a highly
specialized function only to be used under very
particular circumstances by users with a detailed
understanding of BACnet. Refer to Appendix A.1
Present Value,
Relinquish_Default
Notification_Class_MD*
This is the Notification Class map descriptor
governing the sending of Event Notifications
(Intrinsic Alarming) Refer to Appendix A.8.7
Map Descriptor defined per
Appendix A.8

FS-8704-06 BACnet IP Driver Manual Page 18 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
6.4.3 Map Descriptor Example
// Server Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Object_Type
, Object_Instance
, Units
SMD_AI_01
, DA_AI_01
, 0
, Passive
, Virtual_DEV_11
, AI
, 1
, Degrees-Fahrenheit
SMD_AI_02
, DA_AI_01
, 1
, Passive
, Virtual_DEV_11
, AI
, 2
, Degrees-Fahrenheit
SMD_AI_03
, DA_AI_01
, 2
, Passive
, Virtual_DEV_11
, AI
, 3
, Degrees-Fahrenheit
SMD_AO_01
, DA_AO_01
, 0
, Passive
, Virtual_DEV_11
, AO
, 1
, percent-relative-humidity
SMD_AO_02
, DA_AO_01
, 1
, Passive
, Virtual_DEV_11
, AO
, 2
, percent-relative-humidity
SMD_AO_03
, DA_AO_01
, 2
, Passive
, Virtual_DEV_11
, AO
, 3
, percent-relative-humidity
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Object_Type
, Object_Instance
SMD_DI_01
, DA_DI_01
, 0
, Passive
, Virtual_DEV_11
, BI
, 1
SMD_DI_02
, DA_DI_01
, 1
, Passive
, Virtual_DEV_11
, BI
, 2
SMD_DI_03
, DA_DI_01
, 2
, Passive
, Virtual_DEV_11
, BI
, 3
SMD_DO_01
, DA_DO_01
, 0
, Passive
, Virtual_DEV_11
, BO
, 1
SMD_DO_02
, DA_DO_01
, 1
, Passive
, Virtual_DEV_11
, BO
, 2
SMD_DO_03
, DA_DO_01
, 2
, Passive
, Virtual_DEV_11
, BO
, 3

FS-8704-06 BACnet IP Driver Manual Page 19 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: s[email protected]
Appendix A. Useful Features
Appendix A.1. BACnet object names
When an external BACnet Client builds a list of Object Names, the BACnet Server Map Descriptor names determine
the BACnet Object Name. If the Map Descriptor length is greater than 1, the Object Name will be suffixed with the
index into the Map Descriptor. For example, if the Map Descriptor name is SMD_AI_01 and the length 3, then the
Object Names will be SMD_AI_01[0], SMD_AI_01[1] and SMD_AI_01[2].
Appendix A.2. Network number
If multiple BACnet Nodes are specified on the Server side, the FieldServer automatically defaults to virtual
operation. In effect, the FieldServer simulates a software router. BACnet identifies this FieldServer using a
combination of its network number and IP/MAC address. The default Network number of a FieldServer is 5. If
there is more than one FieldServer on a BACnet intranet with multiple nodes, the default network number of the
additional FieldServers will need to be changed and a unique number allocated to each.
A unique network number will need to be assigned if both of the following conditions are true:
The FieldServer has multiple BACnet Server nodes.
There is more than one FieldServer on a network which includes multiple BACnet nodes.
To override the FieldServer’s default network number 5 include the following in the configuration file:
Section Title
Bridge
Column Title
Function
Legal Values
Title
FieldServer name
Text
Network_number*
Specify a unique network number if there are multiple virtual Server nodes.
1-65534, 5
Example
// FieldServer Driver specific parameters
Bridge
Title
, Network_Number
BACnet Server
, 6
Note: While it is theoretically possible to have up to 65535 virtual nodes, it is recommended that a maximum of 32
is configured. If an application requires the configuration of more than 32 virtual nodes please consult FST.

FS-8704-06 BACnet IP Driver Manual Page 20 of 57
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [email protected]
Appendix A.3. Accessing Data from BACnet Properties comprising Arrays of Values
Some BACnet Object properties (e.g. Priority_Array) are arrays of values (the Priority_Array property is an array of 16 values). In order to read a specific array entry, the
Array_Index must be specified in the Map Descriptor. Array_Index is a Client Side Map Descriptor function
The following example shows a configuration that will read the Priority_Array value at Array_Index 7, belonging to Analog Output 1.
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Object_Type
, Object_Instance
, Property
, Array_Index
CMD_AI_01
, DA_AI_01
, 0
, Rdbc
, DEV_01
, AO
, 1
, Priority_Array
, 7
Details of the relevant BACnet properties and their associated arrays can be found in the BACnet Protocol Spec.
If no Array_Index is specified, then the entire property (i.e. the entire BACnet Array) is returned.
The Data_Index parameter functions as follows for ReadPropertyMultiple or WritePropertyMultiple requests when the Client Map Descriptor length N is greater than 1:
When an Array_Index is specified, the ReadPropertyMultiple or WritePropertyMultiple request will iterate through N successive Array_Index values for the given
Object and Property (e.g. Priority Array Index 1 to 16 of Analog Output 1)
When no Array_Index is specified, the ReadPropertyMultiple or WritePropertyMultiple request will iterate through N successive Object Instances, reading the
specified Property from each successive object (e.g. Present Value of Analog Output 1 to Analog Output 16)
Appendix A.4. FieldServer implementation of BACnet priority Arrays
When BACnet Output objects are written to the Server side of the FieldServer, an associated write priority is given to each write value. When the FieldServer receives the
write value, it stores it to the Map Descriptor Priority Array Table at the specified priority. The Priority Array Table is then scanned and the value with the highest priority
is stored to the Data Array location specified by the Map Descriptor.
When a Write “Relinquished” command is received, the value is removed from the Priority Array Table and the next highest value from the Priority Array Table is stored
to the Data Array.
If all values have been “Relinquished” from the Priority Array Table, then the Map Descriptors “Relinquish Default” value will be stored to the Data Array.