4 Data Array Parameters ................................................................................................................................... 7
5 Configuring the FieldServer as a BACnet IP Client........................................................................................... 8
5.1Client Side Connection Parameters................................................................................................................... 8
5.2Client Side Node Parameters ............................................................................................................................. 9
5.3Client 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.4 Map Descriptor Example ........................................................................................................................ 12
6 Configuring the FieldServer as a BACnet IP Server ........................................................................................ 13
6.1Driver Specific FieldServer Parameters ........................................................................................................... 13
6.2Server Side Connection Parameters ............................................................................................................... 14
6.3Server Side Node Parameters .......................................................................................................................... 14
6.4Server 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.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
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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.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.5. Using Cimetrics Explorer ........................................................................................................................ 45
Appendix C.6. Trending using OniconTrend Log Objects............................................................................................. 46
Appendix C.6.2. Date and Time Synchronization .............................................................................................. 48
Appendix D. Reference ........................................................................................................................................ 49
Appendix D.1. FieldServer Vendor ID ............................................................................................................................ 49
Appendix D.4. Units ........................................................................................................................................................ 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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 Testi n g L aboratory
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/.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
2.1 Supplied by F i e ldServe r Technolo g i e s for this d river
2.2 Provided by t he Supplier o f 3
rd
Party Eq u i p m ent
2.2.1 Hardware
This cable is necessary for connection to the driver. It is shipped with the FieldServer and not separately with the driver.
Not all FieldServer models support 100BaseT. Consult the appropriate instruction manual for details of the Ethernet speed supported by
specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
It is possible to connect a BACnet/IP device using the N1 or the N23 network ports. These ports need to be
configured for BACnet/IP in the configuration file.
Configure the Controller according to manufacturer’s instructions
Not all ports shown are necessarily available on the hardware. Consult the appropriate Instruction manual for details of the ports available on
specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Specify the UDP port that will be used to communicate
with other BACnet Client devices.
Any legal IP port value (1 - 65535);
47808
// Client Side Connections
Connections
Adapter
, Protocol
, Poll_Delay
N1
, Bacnet_IP
, 0500s
4
5 CONFI G URING THE FI E LDSERVER A S A BACNET I P 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 C onnection Paramet e r s
Example
Consult the appropriate Instruction manual for details of the ports available on specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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
5.3.2 Driver Spec i f i c Map D e s criptor P a r ameters
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Specify a unique network number if there are multiple virtual Server
Nodes. Refer to Appendix A.2
1 – 65535, 5
// FieldServer Driver specific parameters
Bridge
Title
BACnet Server
6 CONFI G URING THE FI ELDSERVER A S A BACNET I P 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 Specif i c FieldSer v er Paramete r s
Example
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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
// Server Side Connections
Connections
Adapter
, Protocol
, Connection_Type
N1
, Bacnet_IP
, BBMD
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
6.2 Server Side C o nnection Paramete r s
Example
6.3 Server Side N o de Param e ters
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com