BACnet Slave Server

The BACnet Slave Server configuration panel is used to specify the network settings to allow BACnet clients to query attribute
values published via the BACnet IP protocol. To configure Asset Manager to publish attribute values via BACnet, you will
need to install a BACnet license key on the License Key configuration panel using the Configuration > License Key sub-task.
Once a BACnet license key is installed, the server should be restarted. After the server has restarted, you will be able to
configure BACnet settings.

The BACnet Slave Server panel is used to configure the parameters BACnet clients will use to
BACnet server.

1. Navigate to Integration > BACnet Slave Server.

2. Check the Enabled checkbox.

3. Assign a Port.

NOTE: The Port attribute allows the administrator to configure the UDP port on which the Asset Manager BACnet
server is listening for BACnet client requests. The default value is 47808 which is the default UDP port for BACnet
UDP. Enter the Port number of the BACnet slave server.

4. Assign a BACnet Device ID.

NOTE: The BACnet Device ID allows the administrator to configure the unique ID used by the BACnet protocol
to identify a device. The device ID should not duplicate any other BACnet device ID used in a BACnet network. The
BACnet Device ID should be in the range of 0 to 4194303. Enter the BACnet Device ID. This can be set to any
arbitrarily chosen number.

5. Click the Save Changes button.

BACnet Slave Device

The BACnet Slave Device is used to configure a set of assets and attributes whose values will be published by the Asset
Manager BACnet server. BACnet clients can then query the current values of the attributes published for each of the BACnet
Slave Devices.

20 5
Navigate to Integration > BACnet Slave Devices, click the New button and configure the following fields below.

Basic Information

Name - Create a name for the Slave Device.

Description - Create a description for the Slave Device.

BACnet Slave Device Sensor Attributes

Attributes - The Attributes parameter allows the administrator to determine which attributes to publish via BACnet.
Currently, Asset Manager allows numeric (Float, Integer, and Enum) and Boolean attributes to be selected. The
BACnet object type for numeric attributes is analog input. The BACnet object type for Boolean attributes is binary
input. Select the attributes from your schema that you would like to publish using BACnet.

Asset Filter for Publishing BACnet Device Sensor Attributes

Filter Asset Type The Asset Filter is used to define the criteria for selecting which assets and their corresponding
attributes will be published by the BACnet server and therefore made available to BACnet clients. Select the asset type
when you wish to limit the filter to.
Filter Location - Select a location that you would like to filter by.
First Attribute - Choose an attribute that you would like to filter by.
First Attribute Value Operator - Choose the operator for the attribute you have selected.
First Attribute Value - Input the value that the first attribute should have for the filter.
Second Attribute - Choose a second attribute you would like to filter by.
Second Attribute Value Operator - Choose the operator for the attribute you have selected.
Second Attribute Value - Input the value that the second attribute should have for the filter.

BACnet Slave Object IDs

For each attribute value to be published by the BACnet Slave Devices, Asset Manager will automatically assign a unique

to view the value of the BACnet object IDs Asset Manager has assigned to each attribute published via BACnet.

20 6
 1. Navigate to Admin Console > Integration > BACnet Slave Object IDs.
On the right hand panel, there is a list of the currently defined BACnet Slave Devices.

2. The administrator can select a slave device and view the BACnet object IDs Asset Manager has assigned to each
attribute value.
There may be several Object IDs depending on the type and number of attributes that you specified.

3. The entire BACnet Object ID attribute mapping for a BACnet Slave Device can be exported in XML, CSV, or PDF
format to allow a BACnet administrator to conveniently configure BACnet client software. To export these Object
IDs use the Export XML, Export CSV or Export PDF buttons.

4. Access your BACnet system to configure your BACnet client software and complete the integration.

NOTE: For information regarding how to integrate your BACnet system please refer to your BACnet client manuals
or refer to the BACnet website http://www.bacnet.org/.

NOTE

Integrating with Modbus

Very similar to BACnet integration, exposing data from Asset Manager via Modbus TCP is done by following the steps below.
In general, Modbus configuration consists of licensing, enabling, configuring, and mapping Modbus features to those in Asset
Manager.

NOTE: If you have not already done so, contact your RF Code sales representative in order to obtain the license that enables
the Modbus integration module.
To license Modbus within Asset Manager, perform the following steps:

1. In the Admin Console go to Configuration > License Keys.

2. Enter the license key.

Modbus Slave Server

To enable Modbus integration and to set the Port, perform the following steps:

20 7