Appendix A.2. FieldServer implementation of BACnet priority Arrays ................................15
Appendix A.3. Accessing Priority Array information from other protocol drivers.................15
Appendix B. Troubleshooting ............................................................................................16
Appendix B.1. Debugging a BACnet connection: Hints and tips........................................16
Appendix B.2. BACnet Specific Statistics ...........................................................................16
Appendix C. Units................................................................................................................17
Page 3
FS-8704-02_BacnetEthernet.doc Driver Manual Page 3 of 20
1. BACnet Ethernet Description
The BACnet Ethernet driver allows the FieldServer to transfer data to and from devices over
Ethernet using BACnet Ethernet 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.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
FS-8704-02_BacnetEthernet.doc Driver Manual Page 5 of 20
3. Hardware Connections
It is possible to connect a BACnet Ethernet device using the N1 or the N2 network ports. These
ports just need to be configured for BACnet Ethernet in the configuration file.
Configure the Controller according to manufacturer’s instructions
Controller
Ethernet Interface
SITE
ETHERNET
FS-8915-10
FS-8915-10
FIELDSERVER
BACNET ETHERNET
CONNECTION DIAGRAM
BASE NAME:
FILE NAME:
(408)-262-2299
DATE: 6/29/04
BY: MC
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
FS-8704-02_BacnetEthernet.doc Driver Manual Page 6 of 20
4. Configuring the FieldServer as a BACnet Ethernet 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 Ethernet Server.
4.1. Data Arrays
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
Provide data format. Each Data Array
can only take on one format.
Number of Data Objects. Must be
Data_Array_Length
larger than the data storage area
required by the Map Descriptors for
the data being placed in this array.
FS-8704-02_BacnetEthernet.doc Driver Manual Page 8 of 20
4.4. Client Side Map Descriptors
4.4.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
4.4.2. Driver Related Map Descriptor Parameters
Column Title Function Legal Values
Node_Name
Name of Node to
fetch data from
Data_Type Data type
Property
Data_Array_Low_Scale*
Data_Array_High_Scale*
Node_Low_Scale*
Node_High_Scale*
The BACnet
property to be read
Scaling zero in
Data Array
Scaling max in Data
Array
Scaling zero in
Connected Node
Scaling max in
Connected Node
One of the node names specified in
“Client Node Descriptor” above
Note 2
Present_Value
-32767 to 32767, 0
-32767 to 32767, 10000
-32767 to 32767, 0
-32767 to 32767, 100
4.4.3. Timing Parameters
Column Title Function Legal Values
Scan_Interval Rate at which data is polled 0-32000s, 20s
Note 2
- ANALOG INPUT
AI
- ANALOG_OUTPUT
AO
- ANALOG_VALUE
AV
- BINARY_INPUT
BI
- BINARY_OUTPUT
BO
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
FS-8704-02_BacnetEthernet.doc Driver Manual Page 10 of 20
5. Configuring the FieldServer as a BACnet Ethernet 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 on the
driver CD).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a BACnet Ethernet Client
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for BACnet Ethernet 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. Data Arrays
Section Title
Data_Arrays
Column Title Function Legal Values
Data_Array_Name Provide name for Data Array Up to 15 alphanumeric characters
Data_Format Provides data format FLOAT, BIT
Data_Array_Length Number of Data Objects 1-10,000
FS-8704-02_BacnetEthernet.doc Driver Manual Page 12 of 20
5.4. Server Side Map Descriptors
5.4.1. FieldServer Specific 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 Server 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
Server
5.4.2. Driver Specific Map Descriptor Parameters
Column Title Function Legal Values
Node_Name
Name of Node to fetch
data from
Data_Type Data type in PLC
Object_ID Address of the object 0, 1, 2, 3, …
Property
The object property to
read
Units The object units
Data_Array_Low_Scale*
Data_Array_High_Scale*
Node_Low_Scale*
Node_High_Scale*
Active_Text2
Inactive_Text1
Scaling zero in Data
Array
Scaling max in Data
Array
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 Object
Specify the startup
Relinquish_Default1
Relinquish_Default
Property value for this
One of the node names
specified in “Server Node
Descriptor” above
Note 2
Present value
See Error! Reference source
not found.
-32767 to 32767, 0
-32767 to 32767, 100
-32767 to 32767, 0
-32767 to 32767, 100
Any legal BACnet ASCII string
Any legal BACnet ASCII string
Any legal BACnet ASCII string
Note 2
- ANALOG INPUT
AI
- ANALOG_OUTPUT
AO
- ANALOG_VALUE
AV
- BINARY_INPUT
BI
- BINARY_OUTPUT
BO
- DIGITAL_OUTPUT
DO
2
See the BACnet DFS to determine if a particular object supports this property
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
FS-8704-02_BacnetEthernet.doc Driver Manual Page 15 of 20
Appendix A. Advanced Topics
Appendix A.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 A.2. FieldServer implementation of BACnet priority Arrays
When writing to a BACnet Output Object, a write priority value must be specified. 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.
Appendix A.3. Accessing Priority Array information from other protocol
drivers
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
DA_Pri_Array
DA_Pri_Array_Offset Starting location in Data Array. 1-65535 (17)
DA_Pri_In_Use
DA_Pri_In_Use_Offset Starting location in Data Array. 1-65535 (17)
Table 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 Values is in use. Location 0
indicate if the Relinquish Default has been set
and locations 1 to 16 indicate if the index is in
use (1), or if it has been Relinquished (0).
Up to 16
alphanumeric
characters
Up to 16
alphanumeric
characters
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
FS-8704-02_BacnetEthernet.doc Driver Manual Page 16 of 20
Appendix B. Troubleshooting
Appendix B.1. Debugging a BACnet connection: Hints and tips
• Disconnect the FieldServer from the BACnet network when transferring BCU images to the
BCU.
• Should duplicate object instances be accidentally configured in the FieldServer, the second
call of the instance will overwrite the first one. This may result in a BACnet Object being
“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 to the SCADA system.
If the present value’s name is being indicated, but the present value shows question ma rks,
then it is most likely that the Client side of the FieldServer is not communicating.
•If new points are added to the FieldServer it is important to restart the Summit Workstation or
BCU, otherwise these new points might not be seen by the FieldServer.
Poll only the BACnet addresses that exist in the device when communicating with
•
Liebert systems. Polling addresses that are not configured in these systems will cause
the connection to fail. The newer versions of Lieberts do not suffer from this problem.
Please contact your Lieberts supplier for more information.
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
•
Appendix B.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 sent 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