You can use the SmartServer as a BACnet server, BACnet client, and a BACnet router. Using the SmartServer BACnet Server, you can access the SmartServer from a BACnet workstation and other BACnet client applications. Using the SmartServer BACnet Client, you can interface with BACnet/IP and BACnet/MS-TP devices and interact with those devices using the SmartServer CMS and other IAP client applications. An external BACnet/IP to BACnet/MS-TP router is required for any BACnet/MS-TP devices. Using the SmartServer BACnet Router, you can route BACnet communication between one or more BACnet FT channels and up to two BACnet/IP over Ethernet channels. With the BACnet Router, you can interact with BACnet FT devices using a BACnet workstation and other BACnet client applications on one of the Ethernet channels.
For SmartServer 3.2 and higher, see (Optional) Setting up BACnet.
This section covers the following topics:
You can enable and disable BACnet support in the SmartServer. If you enable BACnet support, you can optionally enable or disable a BACnet diagnostic port and you can configure the IP interfaces used for BACnet. The diagnostic port can be used by BACnet diagnostic tools to monitor BACnet status. To enable the BACnet Server, BACnet Client, and BACnet Router, follow these steps:
You can use the SmartServer BACnet Server to provide a BACnet interface to datapoints on field devices you have provisioned with the SmartServer. You can also use the SmartServer BACnet Server to provide an interface to intrinsic reporting for the BACnet objects configured in the server. In addition, you can use the BACnet Server to interface with the IAP scheduler and calendar using BACnet Scheduler and BACnet Calendar objects. You can access the interfaces published by the BACnet server to interact with your field devices from a BACnet workstation or other BACnet client.
Using the SmartServer BACnet Server, you can provide a BACnet interface to any field devices available on your SmartServer, independent of the protocols used to communicate with the devices. As a result, you can provide a BACnet interface to LON, Modbus, and IOX devices that you have provisioned on your SmartServer. You can also provide a customized BACnet interface to BACnet devices that you have provisioned on your SmartServer.
The BACnet Server automatically creates BACnet Scheduler and BACnet Calendar objects for any schedules defined by IAP applications or the CMS Calendar widget. To provide a BACnet interface to any devices available on your SmartServer you must define the mapping of the datapoint XIF names for a device interface defined on your SmartServer to BACnet objects to be published by your SmartServer. You can define a BACnet mapping to any datapoint for a device using any protocol supported by the SmartServer. To create a BACnet type mapping definition for a device interface, create a BACnet type mapping file for the interface as described in the next section. You can create BACnet type maps for multiple device interfaces by creating a BACnet type mapping file for each.
The name of the BACnet Type Map file, without the .BTM extension, specifies the name of the device interface (XIF) to be mapped. For example, BACnet type map files named 6kEvbMultiSensor.btm and Ocean Controls KTA-275 RTU.btm define type maps for the 6kEvbMultiSensor and Ocean Controls KTA-275 RTU device interface (XIF) definitions. The file extension for a BACnet type map must be .btm. You cannot use a compound extension such as .btm.csv.
A BACnet type map file has the following three sections.
The following figure illustrates the top portion of a BACnet type map file.
The following sections describe the BACnet type map file sections:
The file type specification for a BACnet type map file is the following:
If you open a CSV file with this line in Excel, it is displayed as two cells, one with #filetype and one with bacnet_type_map.
The XIF details identify the device interface (XIF) mapped by the mapping file. The XIF details specification has the following contents:
If you open a CSV file with these lines in Excel, each line is displayed as two cells.
Specify the details as follows:
Following is an example XIF details specification for a 6K EVB MultiSensor:
Following is an example XIF details specification for an Ocean Controls KTA-275:
The datapoint list that specifies the XIF datapoints for the mapped device interface (XIF). The first line of the datapoint list is a header with column headings for a XIF datapoint list. Following is an example datapoint list with a single XIF datapoint defined:
Block Type,Block Handle,Point Name,bacnet_type,Instance,Name,Description,Units,SNVT Field,Type Definition
The following table describes the column contents for the datapoint list:
|Parameter||Required / Optional||Description|
|Block Type||Required||The block XIF name for the block containing the mapped datapoint as defined by the XIF definition.|
The block XIF index for the block containing the mapped datapoint as defined by the XIF definition. The block index is 0 for the first block of a given type.
|Point Name||Required||The datapoint XIF name for the datapoint to be mapped as defined by the XIF definition.|
The BACnet object type to be published for the mapped datapoint by the BACnet Server. The supported BACnet object types are AI, AO, AV, BI, BO, BV, MSI, MSO, and MSV. LON and Modbus inputs are considered BACnet outputs (AO, BO, MSO). LON and Modbus outputs are considered BACnet inputs (AI, BI, MSI).
The BACnet object instance number to be published for the BACnet object by the BACnet Server.
The BACnet object name property to be published for the BACnet object by the BACnet Server.
|Description||Optional||The BACnet object description property to be published for the BACnet object by the BACnet Server.|
The BACnet units property to be published for the BACnet object by the BACnet Server. Leave as blank ( ,, ) for BI, BO, BV, MSI, MSO, MSV BACnet objects. A value is optional for AI, AO, and AV BACnet objects. BACnet unit values are listed in the BACnet Units lists below.
The field name for a field within the mapped datapoint. Set to value for scalar datapoints. Set to the datapoint field name for structured datapoints.
|Type Definition||Optional||The IAP type for the XIF datapoint. This parameter can be used to supply an IAP type definition for a multi-state BACnet object (MSI, MSO, or MSV). If an enumeration type is supplied for a multi-state datapoint, the SmartServer translates BACnet numeric state values to the corresponding state text names defined in the IAP type definition. BACnet state values of 1 to 126 are mapped to IAP enumeration values of 1 to 126. BACnet state values greater than 126 are mapped to IAP enumeration values of 127 + <BACnet state value>. For example, BACnet state value 127 maps to IAP enumeration value 0 and BACnet state value 126 maps to IAP enumeration value -1. The SmartServer BACnet Server maps the IAP enumeration text names to BACnet state text properties using the IAP enumeration value as an index into the IAP enumeration definition.|
Following is an example BACnet type map file for a LON 6kEvbMultiSensor example.
Following is an example BACnet type map file for a Modbus Ocean Controls KTA-275 RTU.
You can use the SmartServer BACnet Client to interface with BACnet/IP and BACnet/MS-TP devices and interact with those devices using the SmartServer CMS and other IAP client applications. An external BACnet/IP to BACnet/MS-TP router is required to communicate with any BACnet/MS-TP devices. See (Optional) Add a BACnet Interface in SmartServer Getting Started for a description of the procedures to define, discover, and provision BACnet devices.
You can use the SmartServer BACnet Router to interact with BACnet FT devices using a BACnet workstation and other BACnet client applications on one of the Ethernet channels. BACnet FT devices communicate on a free topology (FT) twisted pair channel using the BACnet/IP protocol with a LON/IP transport. BACnet FT devices typically also have a LON FT interface. If your BACnet FT devices also have a LON FT interface, the procedure that you use to configure the BACnet Router depends on the LON management mode you are using. The two LON management modes are LON device management mode (DMM) and LON independent management mode (IMM). For LON DMM, your LON network is managed by the SmartServer. For LON IMM, your LON network is management by another tool such as the IzoT Commissioning Tool (CT). The next two sections describe the procedures for using the BACnet Router with LON DMM and LON IMM.
You can use the SmartServer BACnet Router to interface a BACnet workstation or other BACnet client application with BACnet FT devices managed using LON DMM. When using LON DMM, you can use either or both of the SmartServer Ethernet interfaces, but you can only use the BACnet Router with one FT interface.
To configure BACnet Routing for LON DMM, follow these steps:
LON IP address allocations must be unique within an intranet for LON DMM. To provision a system to use a specific domain, follow the steps below.
sudo nano /etc/supervisor/conf.d/echltx.conf
sudo cp /etc/supervisor/conf.d/echltx.conf /etc/supervisor/conf.d/echltx.template
To configure BACnet Routing for SmartServer IoT Independent Management Mode (IMM) for use with IzoT CT, perform the following steps:
At a minimum, you need a router to be set up between the external FT channel and the internal IP-70 channel and commissioned for BACnet routing to work. The steps that follow provide this minimal configuration.
The BACnet Router and the BACnet FT device will now be visible to BACnet/IP workstations and other BACnet client applications as well as to the LON infrastructure.