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.
The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer.
2. Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies
PART #
FS-8915-10 UTP cable (7 foot) for Ethernet connection1
Description
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.
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
Controller
Ethernet Interface
SITE
ETHERNET
FS-8915-10
FS-8915-10
(408)-262-2299
FIELDSERVER
BACNET IP
CONNECTION DIAGRAM
BASE NAME:
FILE NAME:
3
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
DATE: 12/28/
BY: MC
manual for details of the ports available on specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
4. Configuring 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.
4.1. Data Arrays/Descriptors
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.
Section Title
Data_Arrays
Column Title Function Legal Values
Data_Array_Name Provide name for Data Array
Data_Array_Format
Data_Array_Length
Example
// Data Arrays
Provide data format. Each Data Array
can only take on one format.
Number of Data Objects. Must be larger
than the data storage area required by the
Map Descriptors for data placed in this
array.
Up to 15 alphanumeric
characters
Float, Bit, Uint16, Uint32,
Sint16, Sint32, Packed_Bit,
Byte, Packed_Byte,
Swapped_Byte
4.4.1. FieldServer Related Map Descriptor Parameters
Section Title
Map Descriptors
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor
Name of Data Array where
Data_Array_Name
Data_Array_Offset Starting location in Data Array 0 to (“Data_Array_Length” -1)
Function
data is to be stored in the
FieldServer
Function of Client Map
Descriptor
Up to 32 alphanumeric
characters
One of the Data Array names
from “Data Array” section above
Rdbc, Wrbc, Wrbx, Ars
4.4.2. Driver Related Map Descriptor Parameters
Section Title
Map Descriptors
Column Title Function Legal Values
One of the Node_Names
Node_Name Name of remote Server Node.
Data_Type Data type
Object_ID Address of the object 0, 1, 2, 3, …4194303
Property* The BACnet property to be read
Data_Array_Low_Scale* Scaling zero in Data Array
Data_Array_High_Scale* Scaling max in Data Array
Node_Low_Scale* Scaling zero in Connected Node
Node_High_Scale* Scaling max in Connected Node
Allows the driver to specify the
Write_Priority*
Custom Type
Custom_Prop
write priority used to write an
output. See also Appendix B.2
This over-writes the Data_Type
with a numerical value for the
Data_Type. e.g. Analog Value =
2
This over-writes the Property with
a numerical value for the
property. e.g. Present Value = 85
specified in “Client Side Node
Descriptors” above
AI, AO, AV, BI, BO, BV, MI,
MO, MV5
Present_Value
-32767 to 32767, 0
-32767 to 32767, 100
-32767 to 32767, 0
-32767 to 32767, 100
1..16, 16
1..1023
1..4194303
4.4.3. Timing Parameters
Section Title
Map Descriptors
Column Title Function Legal Values
Scan_Interval* Rate at which data is polled
5
Refer to Appendix A.1 for further information.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com