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
5. Configuring 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.
Adapter Adapter Name N1, N26
Protocol Specify protocol used BACnet_IP
Specify if this Connection should act as a BBMD
Connection_Type*7
IP_Port*
Example
Server on the network. Refer to Appendix B.5 for
more information.
Specify the UDP port that will be used to
communicate with other BACnet Client devices.
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 B.2. BACnet Priority Arrays
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.
Accessing Priority Array information
The Priority Array table and its “In_Use” (or Not Relinquished) state are stored internally to every Map
Descriptor, and cannot be accessed directly. If the following data arrays are specified, however, they
will maintain an exact copy of the Priority Array Table for the Map Descriptor. Thus the Priority Array
Table can be accessed.
Section Title
Map_Descriptors
Column Title Function Legal Values
Name of Data Array where the Priority Array Table
DA_Pri_Array
DA_Pri_Array_Offset* Starting location in Data Array.
DA_Pri_In_Use
DA_Pri_In_Use_Offset* Starting location in Data Array.
will be stored. Location 0 is the Relinquish Default
value and locations 1 to 16 the different entries of the
Priority Array Table.
Name of Data Array that indicates if a particular
Priority Value is in use. Location 0 indicates whether
the Relinquish Default has been set and locations 1
to 16 indicate whether the index is in use (1), or
Relinquished (0).
Up to 16
alphanumeric
characters
1-65535 ,0
Up to 16
alphanumeric
characters
1-65535, 0
Appendix B.3. Limitations of the BACnet Read_Property_Multiple service.
The BACnet PTP client driver can read multiple BACnet objects using the Read_Property_Multiple
service under the following conditions:
• The number of objects to be read must not exceed 29.
• No gaps must exist in the range of object to be read.
• The Map Descriptor function must be of the Read type. (e.g. Rdbc)
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
• The Map Descriptor property must be Present_Value.
Appendix B.4. IP Address Issues related to BACnet IP
It is not necessary to configure the IP address of the Server node in the Client Side Node Descriptor
in the configuration file since the BACnet Client will automatically discover the IP address based on
the Node_ID supplied. It is still necessary for the FieldServer itself to have a valid IP address,
however. Please refer to the FieldServer Utilities Manual for instructions on changing the FieldServer
IP address.
Appendix B.5. Network number
The default Network number of a FieldServer is 5. In order to ensure communication between the
BACnet Client and all Servers on a BACnet network, however, it may be necessary to assign a
unique network number to each FieldServer.
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, refer to Section 5.1
Appendix B.6. Using BBMD
BACnet/IP requires that a BBMD be defined on every subnet for cross-router communications. The
FieldServer can act as a BBMD for the subnet that it resides on. Setting the Connection_Type to
BBMD will enable this functionality on the FieldServer. Note that BBMD operation is not required if
there is already another BBMD on the network.
Setting up a Broadcast Distribution Table (BDT)
The FieldServer supports two methods of updating its internal broadcast distribution table.
•Trane’s Tracer Summit IP Validation utility can be used directly to upload and download a
Broadcast Distribution Table.
•The Broadcast Distribution Table can be configured using the bdt.ini file. The following file must
be created and downloaded to the FieldServer using the Ruinet “Download Configuration”
command.
//
BBMD IP_Address, BBMD port, BBMD subnet Mask
24.90.48.179, 47808, 255.255.255.255
64.80.115.156, 47808, 255.255.255.255
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Using the following configuration, a PC using BACnet explorer is able to browse and display the
contents of two FieldServers. The following image shows the BACnet explorer screen.
The following diagram shows the layout of the connections between the FieldServers and the PC via
a router.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
CMD_MI_01, MI, 1 Server DA_MI_01, 1, N1 11, 1, Fire_Alrm_Text
FS-8704-06 BACnet IP Driver Manual Page 21 of 24
Appendix C. Troubleshooting Tips
Appendix C.1. Debugging a BACnet connection
•If duplicate object instances are accidentally configured in the FieldServer, the second call of the
instance will overwrite the first one. This may cause a BACnet Object to be “lost.”
•If “Virtual_BCU_…” is not being indicated as the device description for the FieldServer on the
BACnet SCADA system, then the FieldServer is not communicating with the SCADA system. If
the Present_Value’s name is being indicated, but the Present_Value shows question marks, then
it is most likely that the Client side of the FieldServer is not communicating.
•Polling BACnet addresses that are not configured for Liebert systems may cause the connection
to fail in older versions of Liebert. Please contact your Liebert supplier for more information.
•Some of the BACnet IP features result in the creation of files (priarray.ini; desc.ini; alarms.ini) on
the FieldServer. Sometimes updates of firmware can result in these files becoming outdated.
Deleting these files will restore configuration defaults and may assist with configuration errors.
•Extra memory is required to store Map Descriptors that have the active/inactive text parameters
specified. If the defaults are appropriate, do not specify these parameters. This will save
memory and allow more Map Descriptors to be created
•McQuay Units are shipped with a default Device instance of the last 6 digits of the McQuay
Serial number.
Trane Specific Tips
•When new points are added to the FieldServer it is important to restart Summit Workstation or
BCU, otherwise these new points may not be seen by the FieldServer.
•Disconnect the FieldServer from the BACnet network when transferring images to the BCU.
Appendix C.2. BACnet Specific Statistics
Stat Description Resolution
It is normal to receive a few link control
messages. If the number is higher than the
transmit/receive messages, however, there
may be a problem with lost
communications..
This is not an error. BACnet clients often
poll all properties of a particular object to
determine which properties are supported.
This is not an error - the BACnet client will
use a different method to read data from
the FieldServer.
You should not see this message. It
normally indicates a configuration error.
This typically happens when trying to write
to an Input Object that is not Out-OfService. It is not possible to write to Input
Objects.
This may be a problem on the Client
system. Consult the PIC statement to
determine what services are supported.
Link Control
Unsupported
Properties
Segmentation
Not Supported
Sequence Error
Write Access
Denied
Exception
Errors
A “who-is” link control message
was send or received.
A request for an unsupported
property was received
Data was requested but the
response would have exceeded the
maximum size of the APDU and
could not be sent using an unsegmented message.
Invoke ID of a reply did not match
the Invoke ID of the poll.
A write to an object was denied.
A BACnet Service was denied
because it is not supported
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com