MODBUS ROUTER SERIES B
A-MBR/B
Modbus, Modbus RTU, Modbus TCP, ControlLogix, CompactLogix, Automation, Controller, Data, Migration, Interface, Protocol
The Modbus Router provides intelligent data routing between EtherNet/IP and Modbus (serial Modbus-RTU232, Modbus-RTU485, and Ethernet Modbus-TCP). The Modbus Router allows the user to integrate Modbus devices into a Rockwell Automation Logix platform (ControlLogix or CompactLogix) or PLC (SLC or MicroLogix) with minimal effort.
- Operate as a Modbus Client or Modbus Server.
- Modbus Client mode can communicate with up to 100 Modbus Servers.
- Supports Module Security (authentication, encryption, etc.)
- Supports Modbus passthrough messaging.
- Modbus Server mode supports full Modbus data range.
- Modbus Server mode supports emulating multiple Modbus nodes.
- Configurable Modbus TCP Port numbers.
- Supports EtherNet/IP Target and Originator modes:
- EtherNet/IP Target (Class 1 connection)
- EtherNet/IP Originator (Class 1 connection with up to 10 EtherNet/IP devices and Explicit Messaging, including Direct-To-Tag Logix tag access, with up to 10 EtherNet/IP devices).
- Supports CIP USB interface for Logix controllers.
- EtherNet/IP Class 1 target connections support 2kbyte input and 2kbyte output data to Logix input and output assemblies.
- Supports Modbus media conversion allowing for a transparent link from one media to another (e.g., Modbus TCP to Modbus RTU232).
- Slate provides a Modbus packet capture utility for better diagnosis.
- Dual Ethernet ports which support Device-Level-Ring (DLR).
- Network Time Protocol (NTP) supported for external time synchronization.
- Small form factor – DIN rail mounted.

Overview
The Modbus Router provides intelligent data routing between EtherNet/IP and Modbus (serial Modbus-RTU232, Modbus-RTU485, and Ethernet Modbus-TCP). The Modbus Router allows the user to integrate Modbus devices into a Rockwell Automation Logix platform (ControlLogix or CompactLogix) or PLC (SLC or MicroLogix) with minimal effort.
The module can be configured in one of six router modes:
Scheduled Tag
The MBR/B operates as a Modbus Client and transfers data between a Modbus device and a number of Logix tags, using a preconfigured scheduled. No Logix or remote device configuration is required. The MBR/B can execute up to 100 Modbus message instructions (e.g., Modbus Holding Register Read) and exchange the Modbus data with Logix tags in up to three Logix Controllers. Each Modbus Message instruction is executed at one of four configured rates. The Modbus data is exchanged using only one of the available ports (Ethernet TCP, RTU232, or RTU485).
Reactive Tag
The MBR/B operates as a Modbus Server and transfers data between Modbus Clients and a number of Logix tags, using a preconfigured tag map. No Logix or remote device configuration is required. The MBR/B can map up to 100 Modbus message instructions (e.g., Modbus Holding Register Read) and exchange the Modbus data with Logix tags in up to three Logix Controllers. The Modbus data is exchanged using only one of the available ports (Ethernet TCP, RTU232, or RTU485).
Unscheduled
The MBR/B operates as a Modbus Client and sends Modbus messages to Modbus devices when receiving a Logix Message Instruction. This provides the user with complete control (from Logix) of which Modbus instructions must be sent and at which frequency. The Modbus data is exchanged using only one of the available ports (Ethernet TCP, RTU232, or RTU485).
Enhanced
The user can decide if the MBR/B is operating as a Modbus Client or Server as well as if the MBR/B is operating as an EtherNet/IP Target or EtherNet/IP Originator.
In Enhanced Mode the MBR/B can be configured in any one of the four combinations:
Modbus Client - EtherNet/IP Target
Modbus Client - EtherNet/IP Originator
Modbus Server - EtherNet/IP Target
Modbus Server - EtherNet/IP Originator
Modbus Mode
Modbus Server
The data from the configured EtherNet/IP devices (using either Class 1 Assemblies, Explicit messaging or Logix Direct-to-Tag reads/writes) will be written to, or read from, the module’s internal Modbus Registers using the Internal Map. These registers can be accessed by a remote Modbus Client using either Modbus TCP, Modbus RTU232, Modbus RTU485, or any simultaneous combination of these.
Modbus Client
The data from the configured EtherNet/IP devices (using either Class 1 Assemblies, Explicit messaging or Logix Direct-to-Tag reads/writes) will be written to, or read from, the module’s internal Modbus Registers using the Internal Map. The Modbus Auxiliary Map can then be used to configure the Modbus data exchange between multiple remote Modbus Server devices and the module’s internal Modbus registers. The Modbus communication can be via Modbus TCP, Modbus RTU232, Modbus RTU485, or any simultaneous combination of these.
EtherNet/IP Mode
EtherNet/IP Target
As an EtherNet/IP target, the module can exchange the Class 1 data with devices on the Modbus network:
EtherNet/IP Class 1 connection
Here a remote EtherNet/IP device (e.g. a Logix controller) establishes between 1 and 5 Class 1 connections to the module. Modbus data can be mapped into four separate input and output class 1 cyclic connections to the Logix controller (allowing up to 2KB input and 2KB output to be exchanged at the requested packet interval – RPI).
EtherNet/IP Originator
As an EtherNet/IP originator, the module can use one of two methods to read and write data to and from the Modbus network:
EtherNet/IP Explicit Messaging
This allows the MBR/B to exchange data with up to 10 EtherNet/IP devices. The module can use either Class 3 or Unconnected Messaging (UCMM) to Get and Set data in the remote EtherNet/IP devices.
Direct-To-Tag
This allows the MBR/B to exchange data with a Logix controller without the need to write any application code (e.g. ladder) in Studio 5000. The Modbus data is directly read from, or written to, Logix tags.
EtherNet/IP Class 1 connection
Modbus data can be mapped to a maximum of 10 EtherNet/IP devices using input and output class 1 cyclic connections. This will allow the MBR/B to “own” the EtherNet/IP target device and exchange Modbus data using the EtherNet/IP device’s input and output assemblies.
Bridge
The MBR/B can operate as a transparent link for Modbus between different media (TCP, RTU232, and RTU485). This allows a Modbus client on Modbus TCP to communicate with Modbus devices on RS232 or RS485 and vice versa.
Concentrator
In Concentrator Mode, the MBR/B will collect data from a number of Modbus devices and provide the consolidated data to one or more Modbus Clients. The MBR/B will be a Modbus Server on one port, and Modbus Clients on the other ports. This will allow a Modbus SCADA to efficiently read the data from multiple Modbus devices, because the data from the various Modbus devices have been concentrated into the MBR/B.
The Modbus Router is configured using the Aparian Slate application. This program can be downloaded from www.aparian.com free of charge.
The module provides a range of statistics, a Modbus packet analyzer, and an Internal Modbus Register viewer to help fault find any problems.
The Modbus Router supports Modbus on three ports which can be configured from the Slate environment: Modbus-RTU232 (Serial), Modbus-RTU485 (Serial), and Modbus-TCP (Ethernet).
The Modbus Router uses isolated RS232 and isolated RS485 for Modbus serial communication providing better noise immunity. The RS232 and RS485 ports use a terminal block for convenient installation.
The MBR/B supports security services allowing the user to configure various levels of module security.
The module has two Ethernet ports and supports Device-Level-Ring (DLR) architectures.
A built-in webserver provides detailed diagnostics of system configuration and operation, including the display of Modbus operation and communication statistics, without the need for any additional software.
Application
Enhanced mode as a Modbus Client and EtherNet/IP Target
Enhanced mode as a Modbus Server and EtherNet/IP Target
Enhanced mode as a Modbus Server and EtherNet/IP Originator
Bridge Mode - from Modbus TCP to Modbus RTU232/RTU485
Concentrator Mode – Modbus TCP SCADA interfacing with Modbus RTU devices
Example of a typical network setup in Scheduled/Unscheduled Mode:
Typical network setup with using the USB Connection:
Typical network setup in reactive mode:
Redundant Logix Controller setup using USB:
Specification
Electrical
Specification | Rating |
Power requirements | Input: 10 – 32V DC, (121 mA @ 24 VDC) |
Voltage Fluctuations | Voltage Fluctuations <±10% Transient Over-Voltages up to the levels of OVERVOLTAGE CATEGORY I |
Power consumption | 3.1 W (including full load on USB of 200mA) 300mA maximum |
USB Power | 5V, Maximum load of 200mA (1W) |
Connector | 3-way terminal |
Conductors | 24 – 18 AWG |
Enclosure rating | IP20, NEMA/UL Open Type |
Temperature | -20 – 70 °C |
Earth connection | Yes, terminal based |
Emissions | IEC61000-6-4 |
ESD Immunity | EN 61000-4-2 |
Radiated RF Immunity | IEC 61000-4-3 |
EFT/B Immunity | EFT: IEC 61000-4-4 |
Surge Immunity | Surge: IEC 61000-4-5 |
Conducted RF Immunity | IEC 61000-4-6 |
Environmental
Specification | Rating |
Enclosure rating | IP20, NEMA/UL Open Type Indoor use only |
Temperature | -20 to 70°C |
Relative Humidity | 5% to 90% - No condensation |
Pollution Degree | 2 |
Altitude | < 2000 m |
Ethernet
Specification | Rating |
Connector | RJ45 |
Conductors | CAT5 STP/UTP |
ARP connections | Max 40 |
TCP connections | Max 40 |
CIP connections | Max 10 |
Communication rate | 10/100Mbps |
Duplex mode | Full/Half |
Auto-MDIX support | Yes |
Controller Support | ControlLogix, CompactLogix, MicroLogix, SLC |
Embedded Switch | Yes, 2 x Ethernet ports |
Serial Port (RS232)
Specification | Rating |
Connector | 9-way terminal (shared with RS485) |
Conductor | 24 – 18 AWG |
Electrical Isolation | 1000 Vdc |
BAUD | 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 |
Parity | None, Even, Odd |
Data bits | 8 |
Stop bits | 1 |
Serial Port (RS485)
Specification | Rating |
Connector | 9-way terminal (shared with RS232) |
Conductor | 24 – 18 AWG |
Electrical Isolation | 1500 Vrms for 1 minute |
BAUD | 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 |
Parity | None, Even, Odd |
Data bits | 8 |
Stop bits | 1 |
USB Port
Specification | Rating |
USB supported | USB 2.0 |
Module USB Connector | Type-A |
Recommended USB Cable | Type-A (male) to Type-B (male) |
Modbus - Reactive / Scheduled Mode
Specification | Rating |
Reactive Tag Mode | Max 100 Mapping Items |
Scheduled Tag Mode | Max 100 Mapping Items |
Application Functions Supported | Read Coil, Read Discrete Input, Read Holding Register, Write Coil, Write Register |
Maximum Logix Controller support | 3 (when using Ethernet) 1(when using USB) |
Protocols | Modbus RTU (RS232 or RS485), Modbus TCP |
Modbus Client - Enhanced Mode
Specification | Rating |
Modes Supported | Modbus TCP, Modbus RTU232, Modbus RTU485 |
Modbus RTU485 Termination | 125 Ω - Software Enabled |
Max. Modbus Server Devices | 100 |
Max. Modbus Mapping | 100 |
Mapping Ranges |
Holding Register 0 – 65535 Input Register 0 – 65535 Input Status 0 – 65535 Coil Status 0 – 65535 |
Base Offset |
Modbus (Base 0) PLC (Base 1) |
Configurable Modbus TCP Port | Yes |
Data Reformatting Supported |
BB AA BB AA DD CC CC DD AA BB DD CC BB AA |
Modbus Server - Enhanced Mode
Specification | Rating |
Modes Supported | Modbus TCP, Modbus RTU232, Modbus RTU485 (simultaneous) |
Modbus RTU485 Termination | Software set |
Mapping Ranges |
Holding Register 0 – 65535 Input Register 0 – 65535 Input Status 0 – 65535 Coil Status 0 – 65535 |
Base Offset |
Modbus (Base 0) PLC (Base 1) |
Configurable Modbus TCP Port | Yes |
Certifications
Specification | Rating |
CE Mark | ![]() |
UL Listed FILE: E494895 |
CLASS 1, DIV 2, GROUPS A, B, C, D
|
ODVA Conformance | ![]() |
RoHS3 Compliant | ![]() |
UKCA | ![]() |
Dimensions
Downloads
Documents




Examples


EDS Files


Firmware

