Onyxx^® Modbus to BACnet Bridge

Lynxspring’s Helixx^® software platform embedded on the Onyxx^® Modbus to BACnet Bridge (Onyxx-MB311), has revolutionized the construction and implementation of Modbus to BACnet network communication. Helixx takes Modbus to BACnet protocol translation to the next level by not only translating up to 1000 Modbus points to manageable BACnet points, but it also converts Modbus slave devices into BACnet virtual devices using virtual BACnet routing. Acting as the Master Modbus device, Helixx manages all Modbus RTU or TCP slave devices connected to it.

For every Modbus slave device that is added, Helixx creates a corresponding BACnet virtual device. The facility operator has the flexibility to name this BACnet virtual device and assign it a unique BACnet device instance or object ID that will identify it on the BACnet network. Desired Modbus points are simply added under the Modbus slave device of which Helixx automatically maps to the correct virtual BACnet point to its corresponding BACnet virtual device. The Onyxx MB311 supports a maximum of 1000 Modbus points, 32 Modbus RTU slave devices without a repeater or up to 246 with repeaters, 246 Modbus TCP slave devices per network segment, or a combination thereof.

With Helixx on board, third-party software is not needed to access and configure the Onyxx MB311 Bridge. A facility operator simply connects to the Onyxx MB311 Bridge utilizing a standard Internet browser. Helixx presents the operator with all of the configuration screens, documentation, device settings, help and software tools needed to complete a successful project.

Communication Capabilities

Network Communication The Onyxx Modbus to BACnet Bridge is connected to a network utilizing the 10/100 Mbps Ethernet port with auto-negotiation allowing for the use of either a Cat-5 straight-through cable or a crossover cable. Modbus Serial (RTU) Communication The optically isolated, transient protected RS-485 serial port located on the Onyxx MB311 Bridge allows for easy installation of either 2-wire (+ and -) or 3-wire (+, -, and Shield) RS-485 networks utilizing the 3-screw removable terminal block. Modbus TCP and BACnet IP Communication Modbus TCP and BACnet IP communication occur simultaneously through the Ethernet port. Once the Onyxx MB311 Bridge is connected to a network, Modbus TCP requests are sent on registered port 502 and BACnet IP communication occurs through UDP port 0xBAC0 (decimal 47808). Both the Modbus TCP and BACnet IP ports can be modified to support the project’s needs.

Easy Set-Up, Programming and Install

• Intuitive Internet standard browser user interface allows for easy set-up and configuration.
• No programming experience or third-party software tools are required.
• Documentation, configuration screens, device settings, and help guides are embedded on the controller.
• 10/100 Mbps Ethernet port with auto-negotiation allowing use of either a Cat-5 straight-through cable or crossover cable.
• Optically isolated, transient protected RS-485 serial port makes for easy install of 3-wire (+, -, and shield) RS-485 networks utilizing the 3-screw removable terminal block.
• LEDs indicate power status, unit health, transmission, and receipt of activity.

Features

• Modbus Serial (RTU) to BACnet IP, Modbus TCP to BACnet IP, or both Modbus Serial (RTU) and Modbus TCP to BACnet IP.
• Bridge models are available in capacities of 1000 or 2500 Modbus points to BACnet points.
• Converts any Modbus device to a virtual BACnet device object.
• Supports maximum of 2500 Modbus points, 32 Modbus RTU slave devices without a repeater or up to 246 with repeaters, 246 Modbus TCP slave devices per network segment, or a combo thereof.
• DIN rail/flat panel mounting options standard.
• To order, use the part number: Onyxx-MB311-1000 or Onyxx-MB311-2500