Gateways  >  EtherNet/IP and Modbus TCP Protocol Gateway Container
Find a Distributor Request Pricing
ELX-EIP-MBTCP

EtherNet/IP™ and Modbus® TCP Protocol Gateway Container

ELX-EIP-MBTCP

This product will be released soon. For more information Contact Us

The ELX-EIP-MBTCP is a Docker Container designed to provide protocol gateway conversion to the ProSoft Technology ELX3 hardware platform. This protocol gateway container facilitates the data exchange between the EtherNet/IP™ (EIP) and Modbus® TCP (MBTCP) protocols, supporting both Client and Server functionalities for each supported protocol.

The protocol gateway container is configured with the ProSoft Configuration Builder (PCB) software. PCB is also used to download and upload the EtherNet/IP and Modbus TCP network configurations to the container.

The EIP driver is tested and certified by the ODVA organization and includes a shared database between EtherNet/IP and Modbus TCP protocols, as is done with the ProSoft Technology PLX3x-EIP-MBTCP Communication Gateway.

Características y Beneficios

  • Webpage UI contains the container name (ELX-EIP-MBTCP), Project name loaded to the container, Container IP address, revision, Serial Number, Uptime (YY-MM-DD HH:MM:SS format), and FOSS BOM.
  • Diagnostics option contains protocol diagnostics, protocol configuration, and database data values.
  • ProSoft Configuration Builder (PCB) is used to configure the protocol gateway container. PCB simplifies the task of managing multiple configuration files for a variety of ProSoft Technology products.
  • ProSoft Discovery Service (PDS) is launched from PCB or as a standalone software and scans the network for all instances of ProSoft Technology protocol gateway containers.
  • EtherNet/IP™ Conformance Tested
  • Modbus® TCP Client and/or Server support

Especificaciones

EtherNet/IP™ Specifications

Specification

Description

Number of Class 3 Server Connections

5

Supported PLC Types

ControlLogix®, CompactLogix™

Supported Message Types

CIP

Class 3 Client Connections

Connected: 2 (100 commands per client connection)
Unconnected: 1

Number of Class 1 I/O Connections

8

I/O connection sizes

Input: 1 to 248
Output: 1 to 248

RPI Time Ranges

8 Connections: 10ms minimum RPI for all connections

CIP Services Supported

0x4C: CIP Data Table Read
0x4D: CIP Data Table Write
CIP Generic

Client Command List

Support for 100 commands per Client, each configurable for command type, IP address, register to/from addressing and word/bit count.

 

Modbus® TCP Specifications

Specification

Description

Supported Modbus
Function Codes

 

1: Read Coil Status
2: Read Input Status
3: Read Holding Registers
4: Read Input Registers
5: Force (Write) Single Coil
6: Preset (Write) Single Holding Register
8: Diagnostics, Sub-function
00: Echo (Server Only)

15: Force (Write) Multiple Coils
16: Preset (Write) Multiple Holding Registers
22: Mask Write Holding Register (Server Only)
23: Read/Write Holding Registers (Server Only)

 

Supported Clients

10

Client Command List

Up to 160 fully configurable Client commands
(Maximum 16 commands per Client)

Supported Servers

MBAP: 5
Encapsulated: 5

Status Data

Error codes reported individually for each command

Command List Polling

Each command can be individually enabled or disabled; write-only-on-data-change is supported