4.2Setting the FieldServer Node_ID.................................................................................................................... 8
4.3Client Side Connection Descriptions .............................................................................................................. 8
4.4Client Side Node Descriptors ......................................................................................................................... 9
4.5Client Side Map Descriptors......................................................................................................................... 10
4.5.1 Driver Related Map Descriptor Parameters ......................................................................................... 10
5.3Server Side Connection Descriptions ........................................................................................................... 13
5.4Server Side Node Descriptors ...................................................................................................................... 13
5.5Server Side Map Descriptors........................................................................................................................ 14
5.5.1 FieldServer Specific Map Descriptor Parameters ................................................................................. 14
5.5.2 Driver Specific Map Descriptor Parameters ......................................................................................... 15
Appendix A. Useful Features ................................................................................................................................ 17
Appendix A.5. BACnet State Text Preload ............................................................................................................... 20
Appendix A.5.1. Method 1 – Using an Offset/User Table: ................................................................................ 20
Appendix A.5.2. Method 2 – Using a Single Data Array: .................................................................................. 21
Appendix A.5.3. Using Intrinsic Reporting for a Multistate Value .................................................................... 22
Appendix A.6. COV and Intrinsic Reporting ............................................................................................................. 22
Appendix A.6.1. Notes on COV configuration: .................................................................................................. 23
Appendix A.6.2. Notes on Intrinsic Reporting configuration: ........................................................................... 23
Appendix A.6.3. Map Descriptor Example - COV .............................................................................................. 24
Appendix A.6.4. Map Descriptor Example – Intrinsic Reporting ....................................................................... 24
Appendix A.6.5. Map Descriptor Example - Enable or Disable COV ................................................................. 24
Appendix B. Troubleshooting ............................................................................................................................... 25
Appendix B.1. Debugging a BACnet connection ...................................................................................................... 25
Appendix C. Vendor Information ......................................................................................................................... 26
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Appendix D. Reference ........................................................................................................................................ 27
Appendix D.3. Units ................................................................................................................................................. 29
Appendix D.4. BACnet Specific Statistics ................................................................................................................. 32
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 4 of 32
1 BACNET PTP 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.
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.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
It is possible to connect a BACnet device to any of the eight RS-2321 ports. These ports just need to be configured
for BACnet in the configuration file.
Configure the Device according to manufacturer’s instructions
1
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
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
// 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
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 PTP Server.
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.
4.1 Dat a Arrays/ Descriptors
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
Example
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 10 of 32
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 32 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
“Data_Array” section
Data_Array_Offset
Starting location in Data Array
0 to (“Data_Array_Length” -1)
Function
Function of Client Map Descriptor
Rdbc, Wrbc, Wrbx, Ars
Column Title
Function
Legal Values
Node_Name
Name of Node to fetch data from
One of the node names
specified in “Client Node
Descriptor”
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.2
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, -
Column Title
Function
Legal Values
Scan_Interval*
Rate at which data is polled
0-32000, 2s
4.5 Client Side Map Descriptors
4.5 .1 Driver Related Map Descriptor Parameters
4.5 .2 Timing P arameters
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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
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 PTP 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.
5.1 Driver Specific FieldSe r v er Paramete rs
Example
5.2 Dat a Arrays/D escriptors
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 17 of 32
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
// FieldServer Driver specific parameters
Bridge
Title
, Network_Number
BACnet Server
, 6
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 it’s 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:
Example
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.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 18 of 32
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Data_Type
, Object_ID
, Property
, Array_Index
CMD_AI_01
, DA_AI_01
, 0
, Rdbc
, DEV_01
, AO
, 1
, Priority_Array
, 7
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.
Details of the relevant BACnet properties and their associated arrays can be found in the BACnet Protocol Spec.
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.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 19 of 32
Section Title
Map_Descriptors
Column Title
Function
Legal Values
DA_Pri_Array
Name of Data Array where the Priority Array Table will be stored. Location 0 is the Relinquish Default value and
locations 1 to 16 the different entries of the Priority Array Table.
Up to 16 alphanumeric
characters
DA_Pri_Array_Offset*
Starting location in Data Array.
1-65535 , 0
DA_Pri_In_Use
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
DA_Pri_In_Use_Offset*
Starting location in Data Array.
1-65535, 0
// Analog Output Map_Descriptor for testing Priority Arrays
Map_Descriptors
Map_Descriptor_Name
, Data_Type
, Object_ID
, Function
, Data_Array_Name
, Data_Array_Index
, Node_Name
, Length
, Relinquish_default
, DA_Pri_Array
, DA_Pri_Array_Offset
, DA_Pri_In_Use
, DA_Pri_In_Use_Offset
CMD_AOP_1
, AO
, 1
, Passive
, DA_OUT
, 0
, N1 11
, 1
, 40.56
, DA_Pri_Array_1
, 0
, DA_Pri_in_use_1
, 0
Appendix A.4.1. Acc e s s in g Priority Arr a y i n formation
The Priority Array table and its “In_Use” (or Not Relinquished) state are stored internally to every Map Descriptor, and cannot be accessed directly. The information can
be accessed indirectly by specifying the following Data Arrays which will maintain an exact copy of the Priority Array Table for the Map Descriptor.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 20 of 32
//set up a look up table
Offset_Table
Offset_Table_Name
, Table_String
, Table_Index_Value
FIRE_ALRM_TEXT
, SYSTEM READY
, 1
FIRE_ALRM_TEXT
, ALARM
, 2
FIRE_ALRM_TEXT
, MAINTENANCE
, 3
FIRE_ALRM_TEXT
, OFF-LINE
, 4
FIRE_ALRM_TEXT
, IN SERVICE
, 5
FIRE_ALRM_TEXT
, OTHER
, 6 Data_Arrays
Data_Array_Name
, Data_Format
, Data_Array_Length
DA_MI_01
, UINT16
, 100
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, Node_Name
, Data_Type
, Object_ID
, Length
, State_Text_Array
CMD_MI_01
, DA_MI_01
, 0
, Passive
, N1 11
, MI
, 1
, 1
, Fire_Alrm_Text
Must be a positive
integer.
Appendix A.5. BACnet State Text Preload
BACnet Multistate Objects have a State_Text property. This property is defined as an array of character strings representing descriptions of all possible states
of the Present_Value. The number of descriptions matches the number of states defined in the Number_Of_States property. The P resent_Value, interpreted as
an integer, serves as an index into the array.
When Multistate Objects are configured on a BACnet Server it is necessary to define the State_Text property. This section illustrates how to define the
State_Text character strings and how to associate these definitions with Multistate Server Map Descriptors.
The maximum permitted length of any State_Text string is 50 characters.
Appendix A.5.1. Met h o d 1 – U sing an Offset/User Table:
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 22 of 32
//set up a look up table
Offset_Table
Offset_Table_Name
, Table_String
, Table_Index_Value
, Table_User_Value
FIRE_ALRM_TEXT
, SYSTEM READY
, 1
, 0
FIRE_ALRM_TEXT
, ALARM
, 2
, 1
FIRE_ALRM_TEXT
, MAINTENANCE
, 3
, 2
FIRE_ALRM_TEXT
, OFF-LINE
, 4
, 2
FIRE_ALRM_TEXT
, IN SERVICE
, 5
, 0
FIRE_ALRM_TEXT
, OTHER
, 6
, 2
Appendix A.5.3. Usi n g Intrinsic Repor t i n g for a Multist a t e Value
To use Intrinsic Reporting for a Multistate value, it is necessary to classify each of the states as either Normal,
Alarm or Trouble. This is done by adding another column to the Offset_Table, called Table_User_Value. Each state
is then classified by inserting one of the following values in its row:
0 = normal
1 = alarm
2 = fault
Note: The state value (Table_Index_Value) is an enumerated value greater than zero. Zero is not a valid value, but
since many client side configurations will wake up with values of zero, the BACnet Server will treat a value of zero
as a normal value (i.e. not as an alarm or fault value)
Appendix A.6. COV and Intrinsic Reporting
The COV (Change of Value) and Intrinsic Reporting services are two distinct ways in which point values can be
reported to a client workstation as they change, i.e. in an event-driven opposed to a polling method. This can
increase performance dramatically compared to polling method alone. It also reduces network traffic significantly.
For BACnet/MSTP, only MSTP Master Nodes support COV and Intrinsic Reporting
The services are suited to different purposes:
COV is suited to value updates. On analog points the sensitivity can be set using the COV_Increment
property. Only changes larger than the COV_Increment value will be reported.
Intrinsic Reporting is used for alarming. It is implemented via Notification_Class objects, which can
receive subscriptions from client workstations that add themselves to the RecipientList property of a
Notification_Class object. Notifications are done using ConfirmedEventNotification or
UnconfirmedEventNotification. Intrinsic Reporting also allows for alarms to be acknowledged (using the
AcknowledgeAlarm service) and for all subscribed client workstations to be notified of alarm
acknowledgements (using EventNotifications of type ACK_NOTIFICATION)..
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 23 of 32
Appendix A.6.1.Note s on COV configu ration:
COV functionality is not enabled by default for MSTP. The Node_Option parameter can be configured to
enable or disable COV. An example configuration is presented in Appendix A.6.5. Systems using
BACnet/IP or BACnet/Ethernet to BACnet/MSTP routers may not function reliably if COV functionality is
enabled as the router will make the MSTP device appear as a BACnet/IP or BACnet/Ethernet device, which
could lead the BACnet Workstation to expect unrealistic throughput performance when subscribing to
multiple points. It is recommended only to enable COV functionality on MSTP systems if the Client device
communicates directly via MSTP, or if the user knows that the throughput issue will not arise..
COV functionality (SubscribeCOV service) only applies to the Present_Value and Status_Flags properties of
BACnet Objects - the SubscribeCOVProperty service is not supported by the FieldServer.
For analog Server Map Descriptors the user may optionally configure a COV_Increment value to adjust the
reporting threshold. If it is not set the COV_Increment defaults to zero.
COV Notifications are generated for all data objects for which a remote client has issued a SubscribeCOV-
Request. The SubscribeCOV-Request regulates whether Notifications are Confirmed or Unconfirmed. The
remote Client may also write the COV_Increment property in order to control the deadband for changes
in analog values. The COV_Increment property can be initialized via the configuration file by setting the
COV_Increment Map Descriptor Property. The value set by the configuration is an initial value that is
loaded on startup. It would be replaced by any new value written by the Client
COV is not available on the ProtoCessor
Appendix A.6.2. Note s on Intrinsic Rep o r t ing c o n f iguration:
Intrinsic Reporting is managed by Notification Class objects. At least one Notification Class object must be
configured for Intrinsic Reporting to work.
Each Data_Object that is to be monitored by Intrinsic Reporting must be linked to a Notification Class
object via the Notification_Class Map Descriptor Property. For analog points alarm limits must be set up,
and for binary points, the Input_Alarm_State (specifying which binary value (0 or 1) to regard as the Alarm
state) must be set up.
The Notification_Class object contains properties that allow a client workstation to modify rules governing
event reporting, such as event_type, days of week, start and end times etc.
The RecipientLists are non-volatile, and subscriptions must be renewed on system restart.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 25 of 32
Appendix B. Troubleshooting
Appendix B.1. Debugging a BACnet connection
If duplicate Object_Instances are 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 the Node Name configured on the BACnet Server Side of the configuration is not being indicated as the
Device Name on the BACnet SCADA system, then the FieldServer is not communicating with the SCADA
system. If the Device Object's name is being indicated, but the Present_Value shows question marks,
then it is likely that the Client side of the FieldServer is not communicating.
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
When a BACnet_PTP connection is established, and the connection is broken abruptly (for instance a
power down), the DEVICE might not know immediately that this happened. If the FieldServer is then
powered up again, it might take several seconds (up to 60 seconds) before polling will start again.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 26 of 32
Appendix C. Vendor Information
Appendix C.1. McQuay
McQuay Units are shipped with a default Device instance of the last 6 digits of the McQuay Serial number.
Appendix C.2. Trane
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.
Disconnect the FieldServer from the BACnet network when transferring images to the BCU.
Connection to a Trane BCU requires the purchase of a RTS to DB9M convertor. This is available form FST (Part #
FS-8917-02)
Appendix C.3. Liebert
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.
Appendix C.4. Automated Logic Corporation.
When an ALC module is powered up, and it does not detect valid BACnet/MSTP traffic on its MSTP port, then the
module goes into a terminal mode and MSTP communications will not be intitiated.
When connecting the FieldServer to an ALC BACnet/MSTP module, always start the FieldServer first. Wait until the
RUN Led is flashing on the FieldServer before powering up the MSTP module.
Appendix C.5. Honeywell EBI
Honeywell EBI cannot process EventNotifications with ACK_Required set to 1. The ACK_Required property of
Notification Class Map Descriptors configured for use with EBI must therefore be set to 0.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 27 of 32
AI
ANALOG_INPUT
AO
ANALOG_OUTPUT
AV
ANALOG_VALUE
BI
BINARY_INPUT
BO
BINARY_OUTPUT
BV
BINARY_VALUE
MI
MULTI_STATE_INPUT
MO
MULTI_STATE_OUTPUT
MV
MULTI_STATE_VALUE
NC
NOTIFICATION_CLASS_OBJECT
Legal Value
Description
Object_Identifier
This property is a numeric code that is used to identify the object. It is unique within the
BACnet Device that maintains it.
Object_List
Relevant to Device Object Type. This property is a BACnetARRAY of Object_Identifiers, one
Object_Identifier for each object within the device that is accessible through BACnet
services. An Object_Identifier is composed of Object Type and Object Instance and must
be unique within a BACnet Device, e.g. Object Type = Analog Input, Object Instance = 3
Present_Value
This property contains the present value of the Input / Output / Value
Object_Name
Character string providing the name of a BACnet object. The set of characters used in the
Object_Name is restricted to printable characters. The Object_Name is determined by the
Map_Descriptor_Name.
Description
Character string describing a BACnet object. This can be defined by the user to give
additional detail about the Object.
Out_of_service
The Out_Of_Service property, of type BOOLEAN, is an indication whether (TRUE) or not
(FALSE) the physical input that the object represents is not in service. This means that the
Present_Value property is decoupled from the physical input and will not track changes to
the physical input when the value of Out_Of_Service is TRUE. In addition, the Reliability
property and the corresponding state of the FAULT flag of the Status_Flags property shall
be decoupled from the physical input when Out_Of_Service is TRUE. While the
Out_Of_Service property is TRUE, the Present_Value and Reliability properties may be
changed to any value as a means of simulating specific fixed conditions or for testing
purposes. Other functions that depend on the state of the Present_Value or Reliability
properties shall respond to changes made to these properties while Out_Of_Service is
TRUE, as if those changes had occurred in the physical input.
Event_State
The Event_State property, of type BACnetEventState, is included in order to provide a way
to determine if this object has an active event state associated with it. If the object
supports intrinsic reporting, then the Event_State property shall indicate the event state of
the object. If the object does not support intrinsic reporting, then the value of this property
shall be NORMAL. Other values: FAULT, OFF-NORMAL, HIGH-LIMIT, LOW-LIMIT, LIFESAFETY-ALARM
Units
This property contains the units associated with the Present_Value property.
FS-8700-16 BACnet PTP Serial Driver Manual Page 28 of 32
Legal Value
Description
Reliability
The Reliability property, of type BACnetReliability, provides an indication of whether the
Present_Value or the operation of the physical input in question is "reliable" as far as the
BACnet Device or operator can determine and, if not, why. The following values are
supported:
NO_FAULT_DETECTED, UNRELIABLE_OTHER
Priority_Array
This property relates to Output and Value Object Types and is a read only array that
contains prioritized commands or NULLs in the order of decreasing priority. The highest
priority (lowest array index) with a non-NULL value is the active command.
State_Text
Relevant to Multistate Object Types: This property is a BACnetARRAY of character strings
representing descriptions of all possible states of the Present_Value. The number of
descriptions matches the number of states defined in the Number_Of_States property. The
Present_Value, interpreted as an integer, serves as an index into the array.
Number_Of_States
Relevant to Multistate Object Types: this property sets the total number of states for which
descriptions will be returned as defined under the State_Text property. The number of
states will be determined automatically by the largest state number used when configuring
the Offset Table (Refer to Appendix A.5).
Max_Master
Relevant to BACnet MS/TP Device Object Type: The Max_Master property, of type
Unsigned, shall be present if the device is a master node on an MS/TP network. The value
of Max_Master specifies the highest possible address for master nodes and shall be less
than or equal to 127. If the Max_Master property is not writeable via BACnet services, its
value shall be 127.
Max_Info_Frames
Relevant to BACnet MS/TP Device Object Type: The Max_Info_Frames property, of type
Unsigned, shall be present if the device is a node on an MS/TP network. The value of
Max_Info_Frames specifies the maximum number of information frames the node may
send before it must pass the token. If Max_Info_Frames is not writable or otherwise user
configurable, its value shall be 1.
Active_Text
Relevant to Binary Object Types: This property, of type CharacterString, characterizes the
intended effect of the ACTIVE state of the Present_Value property from the human
operator's viewpoint. The content of this string is a local matter, but it is intended to
represent a human-readable description of the ACTIVE state. For example, if the physical
input is a switch contact, then the Active_Text property might be assigned a value such as
"Fan 1 On".
Inactive_Text
This property, of type CharacterString, characterizes the intended effect of the INACTIVE
state of the Present_Value property from the human operator's viewpoint. The content of
this string is a local matter, but it is intended to represent a human-readable description of
the INACTIVE state. For example, if the physical input is connected to a switch contact, then
the Inactive_Text property might be assigned a value such as "Fan 1 Off".
Description
A character string giving more information about the Object associated with the
Present_Value property.
Firmware_revision
The firmware revision of the application.
Relinquish_Default
This property is the default value to be used for the Present_Value property when all
command priority values in the Priority_Array property have a NULL value.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-16 BACnet PTP Serial Driver Manual Page 32 of 32
Stat
Description
Resolution
Link Control
A “who-is” link control message was
send or received.
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..
Unsupported
Properties
A request for an unsupported property
was received
This is not an error. BACnet clients often poll all
properties of a particular object to determine
which properties are supported.
Segmentation
Not Supported
Data was requested but the response
would have exceeded the maximum size
of the APDU and could not be sent using
an un-segmented message.
This is not an error - the BACnet client will use a
different method to read data from the
FieldServer.
Sequence Error
Invoke ID of a reply did not match the
Invoke ID of the poll.
You should not see this message. It normally
indicates a configuration error.
Write Access
Denied
A write to an object was denied.
This typically happens when trying to write to an
Input Object that is not Out-Of-Service. It is not
possible to write to Input Objects.
Exception Errors
A BACnet Service was denied because it
is not supported
This may be a problem on the Client system.
Consult the PIC statement to determine what
services are supported.
Appendix D.4. BACnet Specific Statistics
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com