Page tree
Skip to end of metadata
Go to start of metadata
BACnet Router and Server Configuration is available with SmartServer 2.5 and higher.

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.

SmartServer 3.1 and prior releases

For SmartServer 3.1 or prior, see (Optional) Setting up BACnet (Release 3.1) in the Documents Archive area.

This section covers the following topics:

Enabling BACnet

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:

  1. Open the SmartServer Configuration page as described in Configure Your SmartServer.

  2. Click the BACnet tab.



  3. If there is no checkmark in the Enable BACnet Client, Router, and Server box, click the box so the checkmark appears.

  4. Click the Enable BACnet Diagnostic Port box to enable or disable the diagnostic port (this option was added in SmartServer 2.6).

  5. Set a unique UDP port number and BACnet network number for each interface listed in the interface table.  In the above example, the three interfaces are configured to use BAC0, BAC1, and BAC2 as the UDP port numbers and to use network numbers 112, 111, and 113.  You can change these numbers to any value within the ranges listed in the heading with the exception that you cannot assign the same port number or the same network number to two different interfaces.

  6. Click the Update button.

Configuring the BACnet Server

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.

Creating a BACnet Type Map (BTM) File

You can create a BACnet type map file with a .btm extension that defines the BACnet objects to be published by the BACnet Server in the SmartServer and to define how the BACnet objects are mapped to SmartServer datapoints.  The extension must be .BTM or .btm.  You cannot use a compound extension name such as .btm.csv. You can create multiple BACnet type map files.  Each BACnet type map file defines the BACnet objects for an IAP device interface (XIF) definition that you specify.  You can map multiple IAP XIF definitions by creating multiple BACnet type map files, one per IAP XIF definition. 

The name of the BACnet type map file, without the .btm extension, must be the same as the name of the device interface (XIF) to be mapped. For example, a BACnet type map file named 6kEvbMultiSensor.btm defines type mapping for the 6kEvbMultiSensor XIF definition, and VAV2-101801.btm defines type mapping for the VAV2-101801 XIF definition.

A BACnet type map file has the following three sections.

  • A file type specification that identifies the file as a BACnet type map.
  • An XIF details section that specifies the version and XIF name (repeated from the filename) for the BACnet type map.
  • A datapoint list that specifies the XIF datapoints to be mapped to the BACnet Server. The first line of the datapoint list is a header with column headings for a datapoint list.

The following example shows the top portion of a BACnet type map file.

#filetype,bacnet_type_map
#version,v7.0.0
#product_name,XL10_VAV2
#program_id,80:00:0C:50:0A:03:04:03
#manufacturer,Honeywell
#description,Variable Air Volume XL10 Controller
Block Name,Block Index,Datapoint Name,Address,IAP Type,IAP Field,BACnet Name,BACnet Units,Description,StateTextMap

File Type Specification

The file type specification for a BACnet type map file is the following:

#filetype,bacnet_type_map

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.

XIF Details

The XIF details identify the device interface (XIF) mapped by the mapping file.  The XIF details has the following contents: 

#version,<Version>
#product_name,<Product Name>
#program_id,<Program ID>
#manufacturer,<Manufacturer>
#description,<Description>

If you open a CSV file with these lines in Excel, each line is displayed as two cells.

Specify the details as follows:

  • <Version> – (optional) version of the mapped device.
  • <Product Name> – (optional) manufacturer's name for the mapped device.
  • <Program ID> – (optional) program ID for the mapped device.
  • <Manufacturer> – (optional) manufacturer of the mapped device.
  • <Description> – (optional) description of the mapped device.

Following is an example XIF details specification for a XL10 VAV Controller:

#filetype,bacnet_type_map
#version,v7.0.0
#product_name,XL10_VAV2
#program_id,80:00:0C:50:0A:03:04:03
#manufacturer,Honeywell
#description,Variable Air Volume XL10 Controller

Datapoint List

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 Name,Block Index,Datapoint Name,Address,IAP Type,IAP Field,BACnet Name,BACnet Units,Description,StateTextMap
VAV,0,nvoSpaceTemp,AI:1,SNVT_temp_p,,RmTemp,degrees-fahrenheit,Space Temperature,

The following table describes the column contents for the datapoint list: 

Parameter

Required/Optional

Description

Block NameOptional

Block XIF name for the datapoint. 

Prior to SmartServer 3.2, this parameter was called block Type.
Block IndexOptional

Specifies a numeric block index.  The block index can be any positive (>=0) integer value and is not required to be sequential.  If not specified, the block index will be zero.

For example: for a device with 8 digital outputs, you can define 8 blocks, each named DO, using indexes 0 through 7 (the index names may not be sequential, but they are in this example). 

Prior to SmartServer 3.2, this parameter was called block handle.

Datapoint Name

Required

The datapoint XIF name.  This is a descriptive name to identify the datapoint. The name must be unique for all the datapoints in a block containing (see Block Name). 

Multiple lines in the BTM file may specify the same block name, block index, and datapoint name. These lines specify the definition of a single IAP datapoint based on multiple BACnet objects. See IAP Type Mapping for more information

Prior to SmartServer 3.2, this parameter was called POINT NAME.
Address

Required for BACnet if the legacy Object Type and Object Instance fields are not specified, otherwise this parameter is optional

The BACnet address, specified as <BACnet object type>:<BACnet object instance number>. The supported BACnet object types are AIAOAVBIBO, BV, LAV, IV, MSI, MSO, MSV, and PIVLON and Modbus inputs are considered BACnet outputs (AOBOMSO). LON and Modbus outputs are considered BACnet inputs (AIBIMSI). The BACnet object instance number is the object instance number defined by the BACnet protocol. Do not include leading zeros. For example: AI:941001 is the BASremote Reset Status datapoint, but you cannot specify AI:00941001

Prior to SmartServer 3.2, this parameter was defined by two separate parameters called bacnet_type and instance.
IAP TypeRequired

IAP type that identifies how the data appears in IAP/MQ and identifies the datapoint type to be reported in IAP/MQ.  Multiple BACnet objects may be mapped to a single IAP datapoint. See IAP Type Mapping for more information.

Prior to SmartServer 3.2, this parameter was called SNVT type. 
IAP FieldOptional

Name of a field within the IAP type. The field is specified as a path in a nested structure. For example: the CIE luminance field in a SNVT_color_2 datapoint is named color_value/CIE1931_lumen/y. If not specified, the entire type is used.  

Prior to SmartServer 3.2, this parameter was called SNVT Field with a required field name or a value of value in the bacnet type map file.  Specifying "Value" for the entire field is not required starting with SmartServer 3.2. 
BACnet NameRequired

The BACnet object name property to be published for the BACnet object by the BACnet Server.

Prior to SmartServer 3.2, this parameter was called Name.
BACnet UnitsOptional

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 section below.

Prior to SmartServer 3.2, this parameter was called Units.
DescriptionOptionalProvides a human-readable freeform description of the datapoint or datapoint field.

StateTextMap

Required if the device interface has any multistate objects

Comma-separated list of LonWorks datapoint enumerated types and the StateTextMap value on the BACnet multistate object.

Format:

"{""<LonWorks datapoint enumerated type>"": ""<StateTextMap value>""}"

Example:

"{""HVAC_NUL"": ""Null"",""HVAC_AUTO"": ""Auto""}"

IAP Type Mapping

The BACnet Server maps native datapoints to and from IAP datapoints and datapoint fields. Type mapping is bidirectional so that the server will map received native values to IAP values, and will map received IAP value to native values. The IAP type mapping is performed as described in the following table.

Native TypeIAP TypeNative → IAP MappingIAP → Native Mapping
Any scalar typeAny scalar typeScaled native value

Scaled IAP value

Multistate

Enumeration

Native BACnet-compatible multistate values are mapped to IAP enumerations based on the multistate value corresponding to the multistate string as follows: starting with a native value of 1 for the first enumeration value, incrementing the native value by one for each subsequent enumeration value followed by the zero value followed by the -1 value which will be Invalid unless otherwise specified by the enumeration, followed by each negative value starting with -2.

For example, if an IAP enumeration defines values of -4, -2, 0, 1, 5, and 8, these will be mapped to native values as follows: 1 → 1, 5 → 2, 8 → 3, 0 → 4, -1 → 5, -2 → 6, and -4 → 7. 

The IAP values will be the enumeration strings associated with the mapped value. 

The reverse of the native to IAP mapping. 

For the example the mapping from IAP value to native values will be based on the enumeration value corresponding to the IAP value string as follows: 1 → 1, 2 → 5, 3 → 8, 4 → 0, -5 → -1, 6 → -2, and 7 → -4. 

The mapped value string will be the enumeration string for the IAP value.  

MultistateAny scalar type

Native BACnet-compatible multistate values are mapped to IAP scalars with the same value, with the multistate value corresponding to the multistate string.

The reverse of the native to IAP mapping.
Any scalar typeEnumerationAny native scalar type is mapped to an IAP enumeration type by setting the enumeration value to the scalar value, and the IAP value to the corresponding member name for the enumeration value.The reverse of the native to IAP mapping.

BACnet Units

The following tables provide a listing of names that can be listed in the BACnet Units parameter.

BACnet Units

    
square-meters
square-feet
milliamperes
amperes
ohms
volts
kilovolts
megavolts
volt-amperes
kilovolt-amperes
megavolt-amperes
volt-amperes-reactive
kilovolt-amperes-reactive
megavolt-amperes-reactive
degrees-phase
power-factor
joules
kilojoules
watt-hours
kilowatt-hours
btus
therms
ton-hours
joules-per-kilogram-dry-air
btus-per-pound-dry-air
cycles-per-hour
cycles-per-minute
hertz
grams-of-water-per-kilogram-dry-air
percent-relative-humidity
millimeters
meters
inches
feet
watts-per-square-foot
watts-per-square-meter
lumens
luxes
foot-candles
kilograms
pounds-mass
tons
kilograms-per-second
kilograms-per-minute
kilograms-per-hour
pounds-mass-per-minute
pounds-mass-per-hour
watts
kilowatts
megawatts
btus-per-hour
horsepower
tons-refrigeration
pascals
kilopascals
bars
pounds-force-per-square-inch
centimeters-of-water
inches-of-water
millimeters-of-mercury
centimeters-of-mercury
inches-of-mercury
degrees-celsius
degrees-kelvin
degrees-fahrenheit
degree-days-celsius
degree-days-fahrenheit
years
months
weeks
days
hours
minutes
seconds
meters-per-second
kilometers-per-hour
feet-per-second
feet-per-minute
miles-per-hour
cubic-feet
cubic-meters
imperial-gallons
liters
us-gallons
cubic-feet-per-minute
cubic-meters-per-second
imperial-gallons-per-minute
liters-per-second
liters-per-minute
us-gallons-per-minute
degrees-angular
degrees-celsius-per-hour
degrees-celsius-per-minute
degrees-fahrenheit-per-hour
degrees-fahrenheit-per-minute
no-units
parts-per-million
parts-per-billion
percent
percent-per-second
per-minute
per-second
psi-per-degree-fahrenheit
radians
revolutions-per-minute
currency1
currency2
currency3
currency4
currency5
currency6
currency7
currency8
currency9
currency10
square-inches
square-centimeters
btus_per-pound
centimeters
pounds-mass-per-second
delta-degrees-fahrenheit
delta-degrees-kelvin
kilohms
megohms
millivolts
kilojoules-per-kilogram
megajoules
joules-per-degree-kelvin
joules-per-kilogram-degree-kelvin
kilohertz
megahertz
per-hour
milliwatts
hectopascals
millibars
cubic-meters-per-hour
liters-per-hour
kilowatt-hours-per-square-meter
kilowatt-hours-per-square-foot
megajoules-per-square-meter
megajoules-per-square-foot
cubic-feet-per-second
watts-per-square-meter-degree-kelvin
percent-obscuration-per-foot
percent-obscuration-per-meter
milliohms
megawatt-hours
kilo-btus
mega-btus
kilojoules-per-kilogram-dry-air
megajoules-per-kilogram-dry-air
kilojoules-per-degree-Kelvin
megajoules-per-degree-Kelvin
newton
grams-per-second
grams-per-minute
tons-per-hour
kilo-btus-per-hour
hundredths-seconds
milliseconds
newton-meters
millimeters-per-second
millimeters-per-minute
meters-per-minute
meters-per-hour
cubic-meters-per-minute
meters-per-second-per-second
amperes-per-meter
amperes-per-square-meter
ampere-square-meters
farads
henrys
ohm-meters
siemens
siemens-per-meter
teslas
volts-per-degree-Kelvin
volts-per-meter
webers
candelas
candelas-per-square-meter
degrees-Kelvin-per-hour
degrees-Kelvin-per-minute
joule-seconds
radians-per-second
square-meters-per-Newton
kilograms-per-cubic-meter
newton-seconds
newtons-per-meter
watts-per-meter-per-degree-Kelvin

BACnet Units #if ( BACNET_PROTOCOL_REVISION >= 17 )


per-mille
grams-per-gram
kilograms-per-kilogram
grams-per-kilogram
milligrams-per-gram
milligrams-per-kilogram
grams-per-milliliter
grams-per-liter
milligrams-per-liter
micrograms-per-liter
grams-per-cubic-meter
milligrams-per-cubic-meter
micrograms-per-cubic-meter
nanograms-per-cubic-meter
grams-per-cubic-centimeter
becquerels
megabecquerels
gray
milligray
microgray
sieverts
millisieverts
microsieverts
microsieverts-per-hour
decibels-a
nephelometric-turbidity-unit
pH
grams-per-square-meter
minutes-per-degree-kelvin
ohm-meter-squared-per-meter
ampere-seconds
volt-ampere-hours
kilovolt-ampere-hours
megavolt-ampere-hours
volt-ampere-hours-reactive
kilovolt-ampere-hours-reactive
megavolt-ampere-hours-reactive
volt-square-hours
ampere-square-hours
joule-per-hours
cubic-feet-per-day
cubic-meters-per-day
watt-hours-per-cubic-meter
joules-per-cubic-meter
mole-percent
pascal-seconds
million-standard-cubic-feet-per-minute
standard-cubic-feet-per-day
million-standard-cubic-feet-per-day
thousand-cubic-feet-per-day
thousand-standard-cubic-feet-per-day
pounds-mass-per-day
millirems
millirems-per-hour

BTM File Example – XL10 VAV Controller with Enumerated Type

Following is an example BACnet type map file for Honeywell's XL10 VAV Controller that includes an enumerated type (StateTextMap parameter).

#filetype,bacnet_type_map
#version,v7.0.0
#product_name,XL10_VAV2
#program_id,80:00:0C:50:0A:03:04:03
#manufacturer,Honeywell
#description,Variable Air Volume XL10 Controller
Block Name,Block Index,Datapoint Name,Address,IAP Type,IAP Field,BACnet Name,BACnet Units,Description,StateTextMap
VAV,0,nvoSpaceTemp,AI:1,SNVT_temp_p,,RmTemp,degrees-fahrenheit,Space Temperature,
VAV,0,nvoEffectSetPt,AI:2,SNVT_temp_p,,RmTempSpt,degrees-fahrenheit,Space Temperature Setpoint,
VAV,0,nciSetPts,AO:3,SNVT_temp_setpt,occupied_cool,ClgOccSpt,degrees-fahrenheit,Cooling Occupied Setpoint,
VAV,0,nciSetPts,AO:4,SNVT_temp_setpt,occupied_heat,HtgOccSpt,degrees-fahrenheit,Heating Occupied Setpoint,
VAV,0,nciSetPts,AO:5,SNVT_temp_setpt,unoccupied_cool,ClgUnoccSpt,degrees-fahrenheit,Cooling Unoccupied Setpoint,
VAV,0,nciSetPts,AO:6,SNVT_temp_setpt,unoccupied_heat,HtgUnoccSpt,degrees-fahrenheit,Heating Unoccupied Setpoint,
VAV,0,nvoBoxFlow,AI:7,SNVT_flow,,SaFlow,cubic-feet-per-minute,Box Flow,
VAV,0,nvoFlowControlPt,AI:8,SNVT_flow,,FlowCtrlSpt,cubic-feet-per-minute,Box Flow Setpoint,
VAV,0,nvoUnitStatus,AI:9,SNVT_hvac_status,heat_output_primary,ReheatPos,percent,Heating Valve Position,
VAV,0,nvoCtlDataG,AI:10,UNVT_ctl_data,ubDamperPosS1,SaDmprPos,percent,Damper Position,
VAV,0,nvoTerminalLoad,AI:11,SNVT_lev_percent,,TermlLoad,percent,Terminal Load,
VAV,0,nvoUnitStatus,AI:12,SNVT_hvac_status,fan_output,StatusFan,percent,Fan Status,
VAV,0,nvoUnitStatus,MSI:13,SNVT_hvac_status,mode,StatusMode,,Mode,"{""HVAC_NUL"": ""Null"",""HVAC_AUTO"": ""Auto"",""HVAC_HEAT"": ""Heat"",""HVAC_MRNG_WRMUP"": ""MorningWarmup"",""HVAC_COOL"": ""Cool"",""HVAC_NIGHT_PURGE"": ""NightPurge"",""HVAC_PRE_COOL"": ""PreCool"",""HVAC_OFF"": ""Off"",""HVAC_TEST"": ""Test"",""HVAC_EMERG_HEAT"": ""EmergHeat"",""HVAC_FAN_ONLY"": ""FanOnly"",""HVAC_FREE_COOL"": ""FreeCool"",""HVAC_ICE"": ""Ice"",""HVAC_MAX_HEAT"": ""MaxHeat"",""HVAC_ECONOMY"": ""Economy"",""HVAC_DEHUMID"": ""Dehumid"",""HVAC_CALIBRATE"": ""Calibrate"",""HVAC_EMERG_COOL"": ""EmergCool"",""HVAC_EMERG_STEAM"": ""EmergSteam"",""HVAC_MAX_COOL"": ""MaxCool"",""HVAC_HVC_LOAD"": ""HvcLoad"",""HVAC_NO_LOAD"": ""NoLoad""}"

BTM File Example – 6K EVB MultiSensor

Following is an example BACnet type map file for Dialog Semiconductor's 6K EVB MultiSensor.

#filetype,bacnet_type_map
#version,v6.0.0
#product_name,6kEvbMultiSensor
#manufacturer,Dialog Semiconductor
#program_id, 9F:FF:FF:05:01:84:04:60
#description,MultiSensor example application for the FT 6050 EVB
Block Name,Block Index,Datapoint Name,Address,IAP Type,IAP Field,BACnet Name,BACnet Units,Description,StateTextMap
TempSensor,0,nvoTemperature,AV:1,SNVT_temp_p,,Space Temperature,degrees-celsius,Space temperature,
LightSensor,0,nvoLightlevel,AI:2,SNVT_lux,,Light Level,luxes,Light level,
Switch,0,nvoSwitch,AI:3,SNVT_switch,state,Switch 1 State,,Switch 1 reported state,
Switch,0,nvoSwitch,AI:4,SNVT_switch,value,Switch 1 Level,percent,Switch 1 reported level,
Switch,0,nviSwitchFb,AO:5,SNVT_switch,state,Switch 1 State FB,,Switch 1 state feedback,
Switch,0,nviSwitchFb,AO:6,SNVT_switch,value,Switch 1 Value FB,percent,Switch 1 level feedback,
Lamp,0,nviLamp,AO:7,SNVT_switch,state,Lamp 1 State,,Lamp 1 state control,
Lamp,0,nviLamp,AO:8,SNVT_switch,value,Lamp 1 Level,percent,Lamp 1 level control,
Lamp,0,nvoLampFb,AI:9,SNVT_switch,state,Lamp 1 State FB State,,Lamp 1 state feedback,
Lamp,0,nvoLampFb,AI:10,SNVT_switch,value,Lamp 1 Level FB Value,percent,Lamp 1 level feedback,

Configuring the BACnet Client

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.

Configuring the BACnet Router

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.

Using the BACnet Router with LON Device Management Mode (DMM)

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:

  1. Enable BACnet as described in Enabling BACnet.  Add a port and network number for one or both of your Ethernet interfaces and one of your LON interfaces if not specified.

  2. Open the SmartServer Configuration page as described in Configure Your SmartServer

  3. If you have multiple SmartServers in your system, click the Configuration page LON tab on each SmartServer and set the LON domain for each SmartServer to a unique domain ID as described in (Optional) Add a LON Interface.

  4. Click the Configuration page BACnet tab.  Clear the Overrride Standard (10.<domain>.<subnet>.<node>) option inLON/IP Class A Network and then click the Update button.

  5. Reboot you SmartServer as described in Rebooting Your SmartServer.

  6. Define your BACnet FT device type as described in Defining Device Types.

  7. Create your BACnet FT device as described in Discovering, Defining, or Importing Devices.

  8. Provision your BACnet FT device as described in Provisioning Devices.

  9. The BACnet Router and your BACnet FT device will now be visible to BACnet/IP workstations or browsers.  For example, a BACnet router and a BACnet FT device will appear as follows in the BACnet browser:








Using the BACnet Router with LON Independent Management Mode (IMM)

You can use the SmartServer BACnet Router to interface a BACnet workstation or other BACnet client application with BACnet FT devices managed using IzoT CT and LON IMM.  To configure BACnet Routing for SmartServer IMM, follow these steps:

  1. Switch to LON Independent Management Mode (IMM) as described in (Optional) Switch Off LON Management.

  2. On the Features configuration page, in the RNI Configuration table, set Enable  for lon0 and clickUpdate.  If you have multiple network interfaces, you can also use an internal IP-70 RNI.

  3. Make a note of the port specified for the RNI (typically 1628).

  4. Enable BACnet as described in Enabling BACnet.  Add a port and network number for one or both of your Ethernet interfaces and one of your LON interfaces if not specified.

  5. Open the SmartServer Configuration page as described in Configure Your SmartServer.  Click the BACnet tab.  Clear the Overrride Standard (10.<domain>.<subnet>.<node>) option inLON/IP Class A Network and then click Update.

  6. Reboot you SmartServer as described in Rebooting Your SmartServer.

  7. Set up a router from your external FT channel to your SmartServer's internal IP-70 channel.  To create the router, follow these steps–you can skip any steps you have already completed:
    1. Create an RNI entry in LonWorks Interfaces control panel applet on your computer using the SmartServer IPv4 address and the port you noted from the Features configuration page.

    2. Create an IzoT CT drawing using the RNI as the network interface.

    3. Once the drawing is created, it will have the RNI connected to the FT channel.

    4. Create a new IP-70 channel.

    5. Create a router between the FT channel and the IP-70 channel.

    6. Commission the router using the Service/Connect button for the specific U60 router on the System configuration page.

    7. Create the required BACnet FT device, attached to the FT channel, creating a new device template as you proceed.

    8. Commission the device, loading the application as required.


























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.



  • No labels