DeviceNetRouterB DS PDF
DeviceNetRouterB DS PDF
DeviceNetRouterB DS PDF
The DeviceNet Router/B provides a powerful and easy to configure solution to exchange data between
DeviceNet™ and EtherNet/IP™, Modbus TCP/IP or Modbus RTU networks. The module can be
configured as a DeviceNet Scanner or a DeviceNet Device - allowing the user to not only integrate
DeviceNet devices into a Logix or Modbus system, it also allows EtherNet/IP or Modbus devices in an
existing DeviceNet network.
As a DeviceNet Scanner, the module can connect to over 63 DeviceNet devices where the cyclic
input/output data from each device can be mapped to an EtherNet/IP Target/Originator or a Modbus
Server/Client. The module can be configured to exchange explicit messages with DeviceNet nodes.
As a DeviceNet Device, the module supports input/output data sizes of up to 256 bytes using polled or
change-of-state connections.
In PCCC Client mode, the module can asynchronously exchange data between a DeviceNet Scanner
and an Ethernet PCCC device.
As an EtherNet/IP Target, the module supports the following method to read/write data from an
EtherNet/IP network.
• With support for EtherNet/IP Class 1 connection, DeviceNet data can be mapped to an input
and output Class 1 cyclic connection to the Logix controller.
As a EtherNet/IP Originator, the module supports three methods to read/write data from an
EtherNet/IP network:
• With support for EtherNet/IP Explicit messaging, the router can use Class 3 or unconnected
messages (UCMM) to send/receive data from remote EtherNet/IP devices.
• With support for Direct-To-Tag technology, DeviceNet data can be read from or written to
Logix tags without the need for code in the Logix controllers.
• With support for EtherNet/IP Class 1 connection, the router can own up to a maximum of 10
EtherNet/IP devices and exchange DeviceNet data using the device’s input/output
assemblies.
As a Modbus Server, DeviceNet data can be written to the module’s internal Modbus registers. These
registers can be accessed by a remote Modbus client using the Modbus TCP/IP or RTU protocol.
As a Modbus Client, DeviceNet data can be written to the module’s internal Modbus registers. The
integrated Modbus auxiliary mapping feature can be used to configure Modbus data exchange between
multiple Modbus server devices and the module’s internal Modbus registers using the Modbus TCP/IP
or RTU protocol.
The DeviceNet Router B is configured using the Slate Configuration Utility software tool.
The DeviceNet Router B includes a webserver to display DeviceNet operation and communication
statistics and advanced diagnostics functions like built-in packet capture for the various protocols. The
router has two Ethernet ports to support Device-Level-Ring (DLR) architectures.
Features
DeviceNet Scanner or DeviceNet Device
Support for multiple DeviceNet network baud rates (125K, 250K, 500K)
Support for DeviceNet pass-through or explicit messaging
PCCC client mode to connect to Ethernet-only PanelViews to an existing DeviceNet network
EtherNet/IP Target or Originator with support for Class 1 connections
Supports Modbus TCP/IP (Ethernet) and Modbus RTU (Serial) Client/Server
Direct-to-Tag Technology
Dual Ethernet ports with support for DLR (Device Level Ring)
Support for NTP (Network Time Protocol) for external clock synchronization
Advanced Diagnostics, including packet capture
Configuration
The Slate Configuration Utility software is used for configuration and troubleshooting of the module. The stand-alone
configuration utility allows users to define the setup and configuration of the DeviceNet Router module, connections
with controllers and devices.
The Slate Configuration Utility software can be downloaded from www.prosoft-technology.com
The following example shows the DeviceNet Router B, configured to connect DeviceNet Devices to an
EtherNet/IP-enabled device (e.g. Logix controller).
The following example includes a Modbus RTU device using the module to emulate a DeviceNet device to
communicate with the DeviceNet Controller.
The following example includes EtherNet/IP devices (Drive and Overload relay) using the module to emulate a
DeviceNet device to communicate with the DeviceNet controller (scanner).
Specifications
DeviceNet Network
Specification Description
Connector 5-way terminal, 5.08 mm pitch.
Modes Scanner, Target (or Device)
Baud Rate 125k, 250k, 500k
DeviceNet Terminator 120 Ω (Software enabled) Where Automation
Connects™
DeviceNet Scanner
Specification Description
Device Count 63 Global Distribution
Set Target Device Node Supported ProSoft Technology® products are
Set Target Device Baud Supported distributed and supported worldwide
Rate through a network of over 500
distributors in over 50 countries.
Device Discovery Supported Our knowledgeable distributors are
Explicit Messaging Supported familiar with your application needs.
Supported Connections Poll, Change of State (COS) For a complete list of distributors,
go to our website at:
www.prosoft-technology.com
DeviceNet Target
Specification Description
Supported Connections Poll, Change of State (COS) Global Support
Input / Output Data Max 256 bytes input or output, per message We are there for you
All ProSoft Technology products are
PCCC Network backed with free technical support.
Contact our worldwide Technical
Specification Description Support team directly by phone or
Max PCCC Connections 10 email.
Max PCCC Payload 1000 bytes
EtherNet/IP Network
Global Offices
We are where you are
Specification Description
Connector RJ45 ProSoft Technology has regional
offices worldwide available to help
Conductors CAT5 STP/UTP
you with all your industrial
ARP Connections Max 100 application needs. If you need help
TCP Connections Max 100 choosing a ProSoft Technology
Max 15 solution for your particular
CIP Connections
application check out our contact
Communication Rate 10/100 Mbps information under distributor sales
Duplex Mode Full / Half on the website at:
Auto-MDIX Support Yes www.prosoft-technology.com
Embedded switch Yes, 2 x Ethernet ports
Device Level Ring (DLR) Yes Whether your application is large or
Network Time Protocol Yes small, our technical professionals
(NTP) are there to help you choose the
right communication solution.
EtherNet/IP Originator
Specification Description
Class 1 Cyclic Connections Yes
Supported
Class 3 / UCMM Connections Yes
Supported
Class 1 connection count 10
Class 3 / UCMM Target Device 10 Where Automation
Count
Class 3 / UCMM Mapping Count 50 Connects™