The Babel Buster BB2-7020 BACnet IP to LonWorks gateway connects multiple BACnet IP devices to a LonWorks network, mapping BACnet objects to LonWorks network variables. The BB2-7020 is a standard LonWorks node with bindable network variables. The BB2-7020 BACnet IP to LonWorks gateway can be a BACnet IP client or server.

A large number of data objects gives you flexibility in mapping BACnet objects to scalar or structured LonWorks network variables. Multiple data objects may be mapped a single structured LonWorks network variable. Input, Output, and Value objects are supported for BACnet Analog, Binary, and Multi-state object types.

BB2-7020 BACnet IP to LonWorks Gateway Functionality

Data objects associated with Network Variable Outputs will poll their assigned BACnet object at the interval you specify, and provide the BACnet data to the LonWorks network as an NV update. Data objects associated with Network Variable Inputs will receive their data from the LonWorks network as an NV update. The received data will be written to the assigned BACnet objects periodically or upon NV update (user selected).

Feature Highlights
• Connect BACnet IP Devices to LonWorks Network
• BACnet IP to LonWorks gateway is a standard Managed LonWorks Node
• Configurable as BACnet IP client or server
• 120 Network Variable Inputs, 120 Network Variable Outputs
• Based on FT 5000, no installation credits required
• Up to 300 BACnet objects
• Free configuration software, download from csimn.com
• FCC/CE Mark, UL 916 Listed
• Software Included, No Drivers to Buy

BB2-7020 BACnet IP to LonWorks Gateway

Babel Buster BB2-7020 BACnet IP to LonWorks Gateway

Order code: BB2-7020
Retail price: $1,159.00

 Buy BB2-7020 Online Now!

 Save Even More
Sign Up for Wholesale

Are you going in the right direction?

The BB2-7020 puts a BACnet device on a LonWorks network. Do you need to put a LonWorks device on a BACnet network instead? If so, you want the BB2-7020-NB.

 

LonWorks to BACnet Data Flow

Control Solutions’ Babel Buster BB2-7020 is a bindable LonWorks® node that functions as a client or server on a BACnet IP network. A large number of data objects gives you flexibility in mapping BACnt objects to scalar or structured LonWorks network variables. Multiple data objects may be mapped a single structured LonWorks network variable. Input, Output, and Value objects are supported for BACnet Analog, Binary, and Multi-state object types.

Data objects associated with Network Variable Outputs will poll their assigned BACnet object at the interval you specify, and provide the BACnet data to the LonWorks network as an NV update.

Data objects associated with Network Variable Inputs will receive their data from the LonWorks network as an NV update. The received data will be written to the assigned BACnet objects periodically or upon NV update (user selected).

The BB2-7020 is most often used as a BACnet client, but it can operate as a server. This makes it possible to put LonWorks devices on a BACnet network (but does still require binding and network commissioning with LonMaker or equivalent).

The BB2-7020 provides a “pool” of 300 objects which may be allocated by the user to the object types desired. Any mix of Analog, Binary, and Multi-state Input, Output, and Value objects may be allocated. Output objects are commandable and include the standard priority array found in commandable BACnet objects.

LonWorks to BACnet Configuration Tool

The Gateway Node Configuration Tool is the most user friendly LonWorks gateway configuration tool to date. Connect the gateway to your laptop via a USB cable - no need for any adapters or “dongles”, and no need to have a functional network on either side of the gateway for initial setup.

Import BACnet object lists formatted as CSV files. Create your object list using any standard spreadsheet program, save as CSV, then import. The tool will then automatically create and assign network variables. Next, you export an XIF file representing your device. The XIF includes all configuration property file data and is ready to import into LonMaker.

You can also import an XIF file of a LonWorks device you want to provide BACnet access to. The tool will automatically assign BACnet objects, which is especially useful if the gateway will be a BACnet server.

LonMark Function Block for BACnet to LonWorks Gateway

The LonWorks Network Variables (NV’s) contained within the Babel Buster gateway are configured as standard sensor and actuator function blocks with user changeable network variable types. Each variable has been allocated the maximum of 31 bytes of memory, meaning any known LonWorks variable type (including UNVTs) can be used. The NV’s are bound to other nodes on the LonWorks network using LonMaker or other comparable network management tool.

LonWorks to BACnet Translation Diagram

Many LonWorks network variables are a single data value, such as temperature. However, many other LonWorks network variables are ‘structured’, meaning a single variable contains several related data values such as in the HVAC status variable. BACnet objects, on the other hand, always contain exactly one and only one data value. This means a single structured LonWorks variable cannot be translated to a single BACnet object. The single structured LonWorks network variable must be translated to or from multiple BACnet objects.

The method of making structured LonWorks data available to BACnet involves intermediary data ‘objects’ in the Babel Buster gateway. The LonWorks network variable input data structure is dispersed to multiple data objects. These data objects are, in turn, made accessible as BACnet objects after appropriate data scaling and reformatting.

The process is reversed for structured network variable outputs, with multiple data objects (BACnet objects) collected up and formatted into a single LonWorks structured variable.

 

BB2-7020 Features

• Read/Write standard BACnet objects via LonWorks® NV’s
    • 300 Data objects accessible as standard BACnet objects
    • 120 Network Variable Inputs
    • 120 Network Variable Outputs
• Supports structured network variables
• Free topology LonWorks network
• Based on FT 5000, no installation credits required
• 32-bit ARM co-processor for greater processing power
• Bidirectional LonWorks-BACnet communication
• Supports up to 300 BACnet objects, plus Device object
    • Analog Input, Analog Output, Analog Value
    • Binary Input, Binary Output, Binary Value
    • Multi-state Input, Multi-state Output, Multi-state Value
• BACnet client polling interval configurable per point
• Operation as BACnet server also possible, user selectable
• USB connection directly to PC for configuration
• Configuration software provided at no extra charge
• Internal flash card for simplified firmware updates
• 10/100BaseT Ethernet, RJ45 connector
• Powered by 12-24V DC/AC 50/60 Hz
• Power Consumption: 0.3A @ 24VDC
• DIN rail mounting, 100mm H x 70mm W x 60mm D
• Pluggable screw terminal blocks
• Operating temperature, standard -25°C to +85°C
• Operating temperature, extended -40°C to +85°C
• Humidity 5% to 90% non-condensing
• FCC, CE Mark, UL 916 Listed

 


• BB2-7020 Data Sheet

• BB2-7020 User Guide


• BB2-7020 Support Package
Contains configuration tool software, USB driver, documentation. XIF files are generated by the configuration tool.


• BACnet Tutorial
Introduction to BACnet

• LonWorks Tutorial
Basic overview of LonWorks, and "why is it so complicated?"

BB2-7020 Video Library

Watch these videos for an introduction to configuring the gateway. It's easier than reading!

Introduction to LonWorks BACnet Gateway Configuration Tool

Configuring LonWorks Gateway from CSV Object List

Configuring LonWorks Gateway from XIF File for Other LonWorks Device

Our most extensive technical support is provided by the same engineering staff that developed the products. Your personal attention from this staff is available via the support ticket system.

No user/password is required to open a new ticket. Once you open a ticket, you will immediately receive an email with your ticket number. Your ticket number becomes your login to review your ticket(s) later. Click the Support Ticket icon anywhere you see it. (If you do not get an email with your ticket number, within minutes, check your junk folder, spam settings, etc, and try again if necessary.)

 Open a Ticket