The Modbus IPBlock provides intelligent data routing between EtherNet/IP and Modbus networks. The module can operate as either a Modbus Client or Modbus Server and supports EtherNet/IP Target and Originator modes. It can also provide transparent communication between Modbus TCP and Modbus RTU RS-485 networks.

Modbus Client

In Modbus Client mode, the module can exchange data with up to 100 remote Modbus Server devices. The Modbus Auxiliary Map is used to configure the data exchange between the remote Modbus Servers and the module’s internal Modbus Registers. Communication can take place using Modbus TCP or Modbus RTU over RS-485.

Modbus Server

In Modbus Server mode, remote Modbus Clients can access the module’s internal Modbus Registers using Modbus TCP or Modbus RTU over RS-485. The module supports the full Modbus data range and can emulate multiple Modbus node addresses, allowing a single module to represent multiple Modbus devices.

The Modbus TCP communication port number can be configured to accommodate applications that use non-standard Modbus TCP ports.

The module supports two EtherNet/IP interface modes:

EtherNet/IP Target

A remote EtherNet/IP device, such as a Logix controller, establishes one or more Class 1 cyclic connections to the module. Modbus data can be mapped to the Logix controller’s input and output assemblies, allowing up to 2 KB of input data and 2 KB of output data to be exchanged at the configured Requested Packet Interval (RPI).

EtherNet/IP Originator

As an EtherNet/IP Originator, the module can use the following methods to read data from, and write data to, remote EtherNet/IP devices:

• EtherNet/IP Explicit Messaging

The module can exchange data with up to 10 EtherNet/IP devices using either Class 3 connected messaging or Unconnected Messaging (UCMM).

• Direct-To-Tag technology

Direct-To-Tag technology allows the module to read from, or write directly to, tags in a Logix controller without requiring additional application code, such as ladder logic, in Studio 5000.

• EtherNet/IP Class 1 connections

Modbus data can be mapped to a maximum of 10 EtherNet/IP devices using cyclic input and output Class 1 connections. This allows the Modbus IPBlock to own the EtherNet/IP target devices and exchange data using their input and output assemblies.

Modbus Media Conversion

The Modbus IPBlock can operate as a transparent bridge between different Modbus communication media. For example, a Modbus Client on a Modbus TCP network can communicate with Modbus Server devices connected over Modbus RTU RS-485, and vice versa.

The Modbus IPBlock is configured using the Aparian Slate application. This program can be downloaded from www.aparian.com free of charge.

Slate provides communication statistics, a Modbus packet capture utility, and internal Modbus Register monitoring to simplify commissioning, fault finding, and remote diagnosis.

The module is housed in an IP67-rated enclosure and uses industrial M12 connectors.

The module has three Ethernet ports. Two of the ports can be configured for Linear, Device-Level-Ring (DLR), or Split Dual-IP operation.

Network Time Protocol (NTP) is supported for synchronization with an external time source.

The module’s security services include:

• Configurable security levels
• Encrypted EtherNet/IP communication
• Fixed user roles and custom user accounts
• Configurable password rules
• User login expiry
• Failed-login cool-off and account-disable options
• Configurable global services and custom communication ports
• Optional IP address Access Control List
• Optional MAC address Access Control List
• Restrictions on reset commands
• Restrictions on device firmware update functions
• Security audit trail recorded in the Event Log