FS-8700-16 BACnet PTP Serial Driver Manual Page 3 of 20
1. BACnet Description
The BACnet PTP driver allows the FieldServer to transfer data to and from devices using the BACnet
protocol over a serial RS-232 physical layer. 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 #
Description
FS-8917-02 RJ45 to DB9F Connector adapter
FS-8917-03 Connector adapter – DB9M to DCE, RTS/CTS, DSR/DTR
FS-8700-16 Driver Manual.
2.2. Provided by supplier of 3rd party equipment
PART # DESCRIPTION
Building control unit (BCU)
BACnet client such as a workstation
1
2
1
If FieldServer used as BACnet Client.
2
If FieldServer used as BACnet Server
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 4 of 20
06
3. Hardware Connections
It is possible to connect a BACnet device to any of the eight RS-2323 ports. These ports just need to be
configured for BACnet in the configuration file.
Configure the PLC (or BCU) according to manufacturer’s instructions
8917-03 WIRE LIST
DB9M
FUNCTION FROMTOCOLOUR
RXRJ45-01 DB9M-02GREY
CTSRJ45-02 DB9M08 BROWN
DSRRJ45-03 DB9M-06 YELLOW
GNDRJ45-04 DB9M-05 GREEN
GNDRJ45-05RED
DTRRJ45-06 DB9M-04BLACK
RTSRJ45-07 DB9M-07 ORANGE
TXRJ45-08 DB9M-03BLUE
DB9F
RJ45 Connector
EIA232
RJ45 to
Connector
Note that connection to a Trane BCU requires the 8917-02 option.
8917-02 WIRE LIST
FUNCTION FROMTOCOLOUR
RxRJ45-01 DB9F-03WHITE
GNDRJ45-04 DB9F-05GREEN
TxRJ45-08 DB9F-02BLUE
(408)-262-2299
FIELDSERVER
BACNET PTP
CONNECTION DIAGRAM
BASE NAME:
FILE NAME:
DATE: 7/30/
BY: MC
3
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
FS-8700-16 BACnet PTP Serial Driver Manual Page 5 of 20
4. Configuring the FieldServer as a BACnet Client
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Instruction 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 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 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.
Node_Name Provide name for node Up to 32 alphanumeric characters
Node_ID Node ID of physical server node (the BCU) 1 - 4194303
Protocol Specify protocol used BACnet_PTP
Port Specify port P1-P8
Example
// Client Side Nodes
Nodes
Node_Name, Node_ID, Protocol, Port
BCU_1, 1, BACnet_PTP, P8
4
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
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.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 7 of 20
4.5. Client Side Map Descriptors
4.5.1. FieldServer Related Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name
Data_Array_Name
Data_Array_Offset
Function
Name of this Map
Descriptor
Name of Data Array
where data is to be stored
in the FieldServer
Starting location in Data
Array
Function of Client Map
Descriptor
Up to 32 alphanumeric
characters
One of the Data Array names
from “Data Array” section above
0 to maximum specified in
“Data Array” section above
RDBC, WRBC, WRBX
4.5.2. Driver Related Map Descriptor Parameters
Column Title Function Legal Values
One of the node names
Node_Name Name of Node to fetch data from
Data_Type Data type in FieldServer
Object_Instance Address of object 0, 1, 2, 3, …
Property* The BACnet property to be read
Data_Array_Low_Scale*
Data_Array_High_Scale*
Node_Low_Scale*
Node_High_Scale*
Length*
Write_Priority*
Custom_Type
Custom_Prop
Scaling zero in Data Array
Scaling max in Data Array
Scaling zero in Connected Node
Scaling max in Connected Node
Number of objects that will be polled
using the READ_PROPERTY_
MULTIPLE service. See Appendix B.3
Allows the driver to specify the 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
FS-8700-16 BACnet PTP Serial Driver Manual Page 9 of 20
5. Configuring the FieldServer as a BACnet 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” sample files provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to
communicate with a BACnet Client.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to
enable the FieldServer for BACnet 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.
FS-8700-16 BACnet PTP Serial Driver Manual Page 11 of 20
5.4. Server Side Map Descriptors
5.4.1. FieldServer Specific Map Descriptor Parameters
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
Function
data is to be stored in the
FieldServer
Function of Server Map
Descriptor
Up to 32 alphanumeric
characters.
One of the Data Array names
from “Data Array” section
0 to data_array_length-1 as
specified in “Data_Array”
section
Server
5.4.2. Driver Specific Map Descriptor Parameters
Column Title Function Legal Values
One of the node names
Node_Name Name of FieldServer Node
Data_Type Data type in BCU
Object_Instance Address of the object 0, 1, 2, 3, …
Units The object units
Data_Array_Low_Scale* Scaling zero in Data Array
Data_Array_High_Scale* Scaling max in Data Array
Node_Low_Scale*
Node_High_Scale*
Active Text
Inactive Text
Relinquish Default
Custom_Type
Custom_Prop
Scaling zero in Connected
Node
Scaling max in Connected
Node
Specify the Active Text
property of the Object
Specify the Inactive Text
property of the
Specify the startup
Relinquish_Default Property
value for this Object
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
FS-8700-16 BACnet PTP Serial Driver Manual Page 14 of 20
Appendix B. Advanced Topics
Appendix B.1. BACnet Object Names
When an external BACnet Client builds a list of Object Names, the BACnet Server Map Descriptor
name determines the BACnet Object Name. If the Map Descriptor length is greater than 1, then 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 will be stored 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 will
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.
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 ,17
Up to 16
alphanumeric
characters
1-65535, 17
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)
• The Map Descriptor property must be Present Value.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 15 of 20
Appendix B.4. 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
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FIRE_ALRM_TEXT, SYSTEM READY,0 FIRE_ALRM_TEXT, ALARM, 1 FIRE_ALRM_TEXT, MAINTENANCE,2 FIRE_ALRM_TEXT, OFF-LINE, 3 FIRE_ALRM_TEXT, IN SERVICE,4 FIRE_ALRM_TEXT, OTHER, 5
Data_Arrays
Data_Array_Name,
DA_MI_01, UINT16, 100
Map_Descriptors
Map_Descriptor_Name,
CMD_MI_01, MI, 1 Server DA_MI_01, 1, N1 11, 1, FIRE_ALRM_TEXT
FS-8700-16 BACnet PTP Serial Driver Manual Page 17 of 20
Appendix C. Troubleshooting Tips
Appendix C.1. Debugging a BACnet connection – Hints and Tips
• Disconnect the FieldServer from the BACnet network when transferring images to the BCU.
• 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.
• When new points are added to the FieldServer it is important to restart the Summit
Workstation or BCU, otherwise these new points may not be seen by the FieldServer.
•
Polling BACnet addresses that are not configured for Lieberts systems may cause the
connection to fail in older versions of Lieberts. Please contact your Lieberts supplier for
more information.
•
When a BACnet_PTP connection is established, and the connection is broken abruptly
(for instance a power down), the BCU might not know immediately that this happened. If
the FieldServer is the powered up again, it might take several seconds (up to 60
seconds) before polling will start again.
•
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
Link Control
Unsupported
Properties
Segmentation
Not Supported
Sequence Error
Write Access
Denied
Exception
Errors
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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.
Writing to an object was denied.
A BACnet Service was denied
because it is not supported
messages. If the number is higher than
the transmit/receive messages, 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.
FS-8700-16 BACnet PTP Serial Driver Manual Page 18 of 20