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:
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).
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:
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.
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).
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.
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.
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.
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.