DEVICENET ROUTER SERIES B
A-DNTR/B
The DeviceNet Router/B provides intelligent data routing between either EtherNet/IP or Modbus TCP/RTU and a DeviceNet network. This allows the user to integrate DeviceNet devices into a Rockwell Logix platform (e.g., ControlLogix or CompactLogix) or any Modbus Client or Server device with minimal effort.
The module can be configured to be either a DeviceNet Scanner or a DeviceNet Device allowing the user to not only integrate DeviceNet devices into a Logix or Modbus system, but to also allow the user to use EtherNet/IP or Modbus devices in an existing DeviceNet network (by using the DeviceNet Router/B in device mode).
- Module can operate as a DeviceNet Scanner or Device.
- DeviceNet Scanner mode can configure and operate with up to 63 DeviceNet Devices with up to 256 bytes input and 256 bytes output per DeviceNet IO Device.
- DeviceNet Device mode can exchange up to 256 bytes of input and 256 bytes of output data with a DeviceNet Scanner.
- Supports DeviceNet Passthrough Messaging
- Supported DeviceNet Explicit Messaging
- Module has various Primary Interfaces:
- PCCC Client for connecting new Ethernet only PanelViews to an existing DeviceNet network.
- EtherNet/IP Target (Class 1 connection)
- Modbus Server (TCP, RTU232, and RTU485)
- Modbus Client (TCP, RTU232, and RTU485)
- 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).
- Slate software provides a DeviceNet and Modbus packet capture utility for better diagnosis of issues.
- Supports all DeviceNet Baud Rates (125k, 250k, 500k).
- 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 module can be configured to be either a DeviceNet Scanner or a DeviceNet Device allowing the user to not only integrate DeviceNet devices into a Logix or Modbus system, but to also allow the user to use EtherNet/IP or Modbus devices in an existing DeviceNet network (by using the DeviceNet Router/B in device mode).
- DeviceNet Mode:
DeviceNet Scanner
When the module operates as a DeviceNet Scanner, it can connect to a maximum of 63 DeviceNet Devices. The input and output data from each DeviceNet Device can be mapped to any of the operating interfaces (EtherNet/IP Target, Modbus Server, Modbus Client, or EtherNet/IP Originator).
DeviceNet Device
When the module is configured to be a DeviceNet Device, it will allow the module to have input and output data sizes of up to 128 bytes.
- Primary Interface:
The module can use one of four interface modes:
PCCC Client
The DeviceNet Router is able to asynchronously exchange data between a DeviceNet polling master (scanner) and an Ethernet PCCC device. The sizes of the DeviceNet’s produced and consumed data are independently configurable from 0 to 128 bytes each.
The consumed (DeviceNet) data can then be mapped to a PLC5 type address file, e.g. N33, and then read by an Ethernet device e.g. a PanelView. Similarly, the produced data (DeviceNet) can also be mapped to a PLC5 type address file, to which an Ethernet device could write.
EtherNet/IP Target
As a EtherNet/IP target, the module can use one of two methods to read and write data to and from the DeviceNet network:
EtherNet/IP Class 1 connection
Here a remote EtherNet/IP device (e.g. a Logix controller) establishes a number of Class 1 connections to the module. DeviceNet data can be mapped into two separate input and output class 1 cyclic connections to the Logix controller (allowing up to 1KB input and 1KB 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 DeviceNet network:
EtherNet/IP Explicit Messaging
This allows the DeviceNet Scanner or Devices 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 technology
This allows the DeviceNet Scanner or Devices to exchange data with a Logix controller without the need to write any application code (e.g. ladder) in Studio 5000. The DeviceNet data is directly read from, or written to, Logix tags.
EtherNet/IP Class 1 connection
DeviceNet data (from either DeviceNet Scanner or Devices) can be mapped to a maximum of 10 EtherNet/IP devices using input and output class 1 cyclic connections. This will allow the DeviceNet Router/B to “own” the EtherNet/IP target device and exchange DeviceNet data using the EtherNet/IP device’s input and output assemblies.
Modbus Server
The diagnostics and DeviceNet data (from either DeviceNet Scanner or Devices) will be written to, or read from, the module’s internal Modbus Registers (Holding or Input Registers). These registers can be accessed by a remote Modbus Client using either Modbus TCP, Modbus RTU232, or Modbus RTU485.
Modbus Client
The diagnostics and DeviceNet data (from either DeviceNet Scanner or Devices) will be written to, or read from, the module’s internal Modbus Registers (Holding or Input Registers). 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, or Modbus RTU485.
The module and Slate will allow the user to parameterize each DeviceNet Device according to the parameters provided in the DeviceNet Device EDS file. These parameters can be saved in the DeviceNet Device’s n.
The DeviceNet Router/B is configured using the Aparian Slate application. This program can be downloaded from www.aparian.com free of charge.
Application
Example of connecting DeviceNet Devices to a Logix Controller
Example of connecting DeviceNet Devices to a Modbus TCP Client or Server
Example of connecting DeviceNet Devices to a Modbus RTU Client or Server
Modbus TCP Device (Client or Server) operating as a DeviceNet Device
Modbus RTU Device (Client or Server) operating as a DeviceNet Device
Logix Controller operating as a DeviceNet Device via the DeviceNet Router
EtherNet/IP Drive and Smart Overload operating as a DeviceNet Device
Example of a typical network setup in PCCC Client Mode
Specification
Electrical
Specification | Rating |
Power requirements | Input: 10 – 32V DC |
Power consumption | 2.2 W (Max) Current:180 mA @ 10 V Current:85 mA @ 24 V |
Connector | 3-way terminal, 5.08mm pitch |
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 |
Ethernet
Specification | Rating |
Connector | RJ45 |
Conductors | CAT5 STP/UTP |
ARP connections | Max 100 |
TCP connections | Max 100 |
CIP connections | Max 15 |
Communication rate | 10/100Mbps |
Duplex mode | Full/Half |
Auto-MDIX support | Yes |
Embedded Switch | Yes, 2 x Ethernet ports |
Device Level Ring (DLR) | Supported |
Network Time Protocol (NTP) | Supported |
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 |
DeviceNet
Specification | Rating |
Connector | 5-way terminal, 5.08 mm pitch |
Modes | DeviceNet Scanner DeviceNet Device |
Passthrough Messaging | Supported |
Supported Baud Rates | 125k 250k 500k |
DeviceNet Terminator | 120 Ω - Software Enabled |
DeviceNet Scanner
Specification | Rating |
DeviceNet Device Count | 63 |
Set Target Device Node | Supported |
Set Target Device BAUD | Supported |
Device Discovery | Supported |
Explicit Messaging | Supported |
Connections Supported |
Polled Change of State (COS) |
DeviceNet Device
Specification | Rating |
Connections Supported |
Polled Change of State (COS) |
Input / Output Data Max |
256 bytes input 256 bytes output |
EtherNet/IP Target
Specification | Rating |
Class 1 Cyclic Connection Count | 4 |
Logix Direct-to-Tag Supported | Yes |
EtherNet/IP Originator
Specification | Rating |
Class 1 Cyclic Connections Supported | Yes |
Class 3 / UCMM Connections Supported | Yes |
Class 1 Connection Count | 10 |
Class 3 / UCMM Target Device Count | 10 |
Class 3 / UCMM Mapping Count | 50 |
Modbus Client
Specification | Rating |
Modes Supported | Modbus TCP, Modbus RTU2232, Modbus RTU485 |
Modbus RTU485 Termination | 125 Ω - Software Enabled |
Max Modbus Slave Devices | 20 |
Max Modbus Mappings | 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
Specification | Rating |
Modes Supported | Modbus TCP, Modbus RTU2232, Modbus RTU485(simultaneously) |
Modbus RTU485 Termination | 125 Ω - Software Enabled |
Mapping Ranges | Holding Register 0 – 65535 Input Register 0 – 65535 Input Status 0 – 65535, Coil Status 0 – 65535 |
Base Offset | Modbus (Base 0) |
Configurable Modbus TCP Port | Yes |
Certifications
Specification | Rating |
CE Mark | ![]() |
UL Listed FILE: E494895 |
CLASS 1, DIV 2, GROUPS A, B, C, D
|
UKCA | ![]() |
RoHS3 Compliant | ![]() |
Dimensions
Downloads
Documents



Examples
EDS Files

Firmware

