The BACnet Master provides flexible integration between BACnet networks and EtherNet/IP or Modbus devices. The module supports up to 512 BACnet devices and 3,000 BACnet data points, with BACnet communication available over Ethernet, RS-485, and RS-232.

The module supports one of four Primary Interface modes:

EtherNet/IP Target

Here a remote EtherNet/IP device, such as a Logix controller, establishes Class 1 cyclic connections to the module. BACnet data can be mapped between the module and the Logix controller’s input and output assemblies, allowing up to 2 KB of input data and 2 KB of output data to be exchanged at the requested packet interval (RPI).

The module also supports passthrough messaging from Logix, allowing a controller to initiate supported BACnet communication through the BACnet Master.

EtherNet/IP Originator

As an EtherNet/IP Originator, the module can use one of three methods to read data from, and write data to, EtherNet/IP devices:

• EtherNet/IP Explicit Messaging

This allows BACnet data to be exchanged with up to 10 EtherNet/IP devices. The module can use either Class 3 connected messaging or Unconnected Messaging (UCMM) to get and set data in remote EtherNet/IP devices.

• Direct-To-Tag technology

This allows BACnet data to be exchanged directly with tags in a Logix controller without the need to write additional application code, such as ladder logic, in Studio 5000.

• EtherNet/IP Class 1 connection

BACnet data can be mapped to a maximum of 10 EtherNet/IP devices using cyclic input and output Class 1 connections. This allows the BACnet Master to own the EtherNet/IP target devices and exchange BACnet data using their input and output assemblies.

Modbus Server

BACnet data and module diagnostics are written to, or read from, the module’s internal Modbus Registers. These registers can be accessed by a remote Modbus Client using Modbus TCP, Modbus RTU over RS-232, or Modbus RTU over RS-485.

Modbus Client

BACnet data and module diagnostics are written to, or read from, the module’s internal Modbus Registers. The Modbus Auxiliary Map can then be used to configure data exchange between multiple remote Modbus Server devices and the module’s internal Modbus Registers using Modbus TCP, Modbus RTU over RS-232, or Modbus RTU over RS-485.

The module supports communication with up to 512 BACnet devices and can map up to 3,000 BACnet data points. BACnet communication is supported over BACnet/IP on Ethernet, BACnet MS/TP on RS-485, and BACnet Point-to-Point on RS-232.

When configured as an EtherNet/IP Target, Slate can generate an L5X file for import into Studio 5000. This provides the required UDTs, tags, and mapping logic to simplify access to BACnet device data from the Logix application.

The BACnet Master is configured using the Aparian Slate application. This program can be downloaded from www.aparian.com free of charge.

Slate provides BACnet and Modbus packet capture utilities, communication statistics, and internal Modbus and data table monitoring to simplify commissioning and diagnosis of communication issues.

The module has two Ethernet ports and supports Device-Level-Ring (DLR) architectures.

Network Time Protocol (NTP) is supported for synchronization with an external time source.

The module has a compact form factor and is designed for DIN-rail mounting.