1. Manuals
  2. Brands
  3. Comtrol Manuals
  4. Gateway
  5. DeviceMaster EtherNet/IP-Modbus EIP-MOD
  6. User manual

Comtrol DeviceMaster EtherNet/IP-Modbus EIP-MOD User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
DeviceMaster
®
EIP-MOD
®
EtherNet
®
/IP - Modbus
User Guide

Advertisement

Table of Contents
loading

Related Manuals for Comtrol DeviceMaster EtherNet/IP-Modbus EIP-MOD

Summary of Contents for Comtrol DeviceMaster EtherNet/IP-Modbus EIP-MOD

  • Page 1 DeviceMaster ® EIP-MOD ® EtherNet ® /IP - Modbus User Guide...
  • Page 2 Copyright © 2019. Pepperl + Fuchs Comtrol, Inc.  All Rights Reserved. Pepperl + Fuchs Comtrol, Inc. makes no representations or warranties with regard to the contents of this document or to the suitability of the Pepperl + Fuchs Comtrol, Inc. product for any particular purpose.

  • Page 3: Table Of Contents

    Table of Contents Chapter 1. Introduction......................7 1.1. EtherNet/IP-Modbus Gateway Overview..................7 1.2. System Architecture ..........................9 1.3. EtherNet/IP to Modbus Translation Layer Architecture............10 1.4. Translation Layer Connections ......................11 1.4.1. Connection Methods Table......................11 1.4.2. EtherNet/IP Controllers Class1 to/from Shared Memory ............12 1.4.3.
  • Page 4 2.2.4.4. Common Services ........................31 2.2.5. TCP Object (F5 Hex - 1 Instance) ....................31 2.2.5.1. Class Attributes ........................31 2.2.5.2. Instance Attributes ....................... 31 2.2.5.3. Common Services ........................33 2.2.6. Ethernet Link Object (F6 Hex) ...................... 33 2.2.6.1. Class Attributes ........................33 2.2.6.2.
  • Page 5 Chapter 8. Diagnostic Menus ....................91 8.1. Serial Communication Statistics Page.................... 92 8.2. Modbus RTU/ASCII over Ethernet TCP Statistics Page ............. 94 8.3. Serial Interface Logs ........................... 96 8.4. Known Modbus Slave Device List ....................97 8.5. Modbus/TCP and Serial Modbus Master Statistics Page ............100 8.6.
  • Page 6 6 - Table of Contents DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 7: Chapter 1. Introduction

    Chapter 1. Introduction This document describes how to configure the DeviceMaster EIP-MOD for the EtherNet/IP-Modbus after basic DeviceMaster EIP-MOD installation and configuration procedures. • EtherNet/IP Interface Profile (ControlLogix) on Page 21 • Configuration Overview on Page 41 • Serial Menus on Page 47 •...
  • Page 8 EtherNet/IP-Modbus Gateway Overview Via Read-from-Tag/File and Write-to-File/Tag configurations The most extensive Modbus functionality in the industry: • Up to 96 Modbus/TCP connections • Support up to eight unique Modbus TCP socket port numbers. (i.e. 502, 503, 505, etc.) • Multiple Modbus/RTU and/or Modbus/ASCII over Ethernet TCP connections •...

  • Page 9: System Architecture

    System Architecture 1.2. System Architecture The DeviceMaster EtherNet/IP-Modbus firmware utilizes the following architecture. The firmware architecture is designed to take full advantage of a broad range of EtherNet/IP and Modbus routing functionality supported by the DeviceMaster EtherNet/IP-Modbus gateway. DeviceMaster EIP-MOD User Guide: 2000664 Rev. A Chapter 1.

  • Page 10: Ethernet/Ip To Modbus Translation Layer Architecture

    EtherNet/IP to Modbus Translation Layer Architecture 1.3. EtherNet/IP to Modbus Translation Layer Architecture The following image illustrates the EtherNet/IP to/from Modbus translation layer. 10 - Chapter 1. Introduction DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 11: Translation Layer Connections

    Translation Layer Connections 1.4. Translation Layer Connections The following connections are possible through the translation layer. 1.4.1. Connection Methods Table This table lists the possible connections and the methods available for a wide variety of EtherNet/IP and Modbus interfaces. Write (To) EtherNet/IP PLC(s) via Class1 Connection EtherNet/IP PLC(s) via Tag/...

  • Page 12: Ethernet/Ip Controllers Class1 To/From Shared Memory

    EtherNet/IP Controllers Class1 to/from Shared Memory 1.4.2. EtherNet/IP Controllers Class1 to/from Shared Memory The following provides information about EtherNet/IP controllers Class1 to and from shared memory. • Combined with the Data Mapping Modbus to Modbus functionality: Local serial Modbus/RTU and Modbus/ASCII slave devices. Remote serial Modbus/RTU and Modbus/ASCII slave devices (via additional gateways).

  • Page 13: Ethernet/Ip Controllers Cip Modbus Object Via Msg Instructions

    EtherNet/IP Controllers CIP Modbus Object via MSG Instructions 1.4.4. EtherNet/IP Controllers CIP Modbus Object via MSG Instructions The following provides information about EtherNet/IP controller CIP Modbus object via MSG instructions. • Directly to/from Modbus slave devices: Local serial Modbus/RTU and Modbus/ASCII slave devices. Remote serial Modbus/RTU and Modbus/ASCII slave devices (via additional gateways).

  • Page 14: Terms And Definitions

    Terms and Definitions 1.5.1. Terms and Definitions This section uses the following terms and definitions. Term Definition Otherwise called implicit messaging, is a method of communication between EtherNet/IP controllers and devices that: Class 1 • Uses Ethernet UDP messages. • Is cyclic in nature.
  • Page 15 Terms and Definitions Term Definition (Continued) The standard Modbus messages, in hexadecimal format, that are typically transmitted over serial lines but can also be transmitted over other communication methods such as wireless or Ethernet TCP/IP socket Modbus/RTU connections. Note: Modbus/RTU over Ethernet TCP/IP is not the same as Modbus TCP. An ASCII, or character based, form of Modbus.

  • Page 16: What Is Modbus

    What is Modbus? 1.6. What is Modbus? This subsection discusses: • Modbus/RTU • Modbus/ASCII on Page 17 • Modbus/TCP on Page 18 1.6.1. Modbus/RTU Modbus/RTU is native Modbus in hexadecimal format. These are the base Modbus messages that contain simple read and write requests. The format is as follows: Where: •...

  • Page 17: Modbus/Ascii

    Modbus/ASCII 1.6.2. Modbus/ASCII Modbus/ASCII is native Modbus in ASCII format. This protocol is used primarily by legacy devices and is no longer supported as widely as Modbus/RTU. Like Modbus/RTU, Modbus/ASCII contains the base Modbus messages that contain simple read and write requests.

  • Page 18: Modbus/Tcp

    Modbus/TCP 1.6.3. Modbus/TCP Modbus/TCP is an Ethernet network based protocol that contains a Modbus/RTU message, with the exception of the 2-byte CRC. The Modbus/TCP message contains a header with information designed to provide message identification and routing information. The format is as follows: Where: •...

  • Page 19: Locating The Latest Software And Documentation

    1.7. Locating the Latest Software and Documentation You can use the links in this table to check for updated software or documentation. Software and Documentation Use PortVision DX to manage Pepperl+Fuchs Comtrol, Inc. Ethernet- attached devices to: • Scan the network for attached devices •...
  • Page 20 Locating the Latest Software and Documentation 20 - Chapter 1. Introduction DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 21: Chapter 2. Ethernet/Ip Interface Profile (Controllogix)

    Chapter 2. EtherNet/IP Interface Profile (ControlLogix) This section describes the EtherNet/IP objects included in the ControlLogix EtherNet/IP interface and supported by the DeviceMaster EIP-MOD. 2.1. Modbus Object (44 Hex, 1 Instance) The Modbus Object provides an interface to the data and functions within a Modbus device or the Shared memory on the DeviceMaster EtherNet/IP-Modbus gateway.

  • Page 22: Object Specific Services (Instance Specific)

    | Modbus Object (44 Hex, 1 Instance) | Object Specific Services (Instance Specific) | | 2.1.4. Object Specific Services (Instance Specific) These services are provided to implement the supported Modbus functions. All Modbus Object services, as specified in Volume 7: Integration of Modbus Devices into the CIP Architecture, are supported as well as several additional services.

  • Page 23: Read Holding Registers Service (4E Hex)

    | Modbus Object (44 Hex, 1 Instance) | Object Specific Services (Instance Specific) | | 2.1.4.0.4. Read Holding Registers Service (4E Hex) This service reads one or more holding registers from the Modbus Holding Register table. This service results in the DeviceMaster EIP-MOD issuing a Read Holding Registers function (function code 0x03) to either the Shared Memory or the Modbus Message Routing subsystem.

  • Page 24: Vendor Specific Read/Write Holding Registers (73 Hex)

    The following table provides information about the Identity Object (01 hex, 1 Instance) Instance Attributes. Attribute ID Name Data Type Data Value(s) Access Rule Vendor ID UINT 909 (Pepperl+Fuchs Comtrol, Inc.) Device Type UINT 43 (Generic product device) As defined by Pepperl+Fuchs Product Code UINT Comtrol, Inc.

  • Page 25: Status Word

    | Informational Objects | Identity Object (01 Hex, 1 Instance) | Status Word | Attribute ID Name Data Type Data Value(s) Access Rule Product Name Structure of: Name Length USINT Length of string Name String STRING See below 2.2.1.3. Status Word Refer to Page 52 of Volume 3.5 of the CIP Common Specification.

  • Page 26: Common Services

    If the major fault is not corrected with a system reset or a power cycle, refer to the Troubleshooting and Technical Support on Page 155 or call Pepperl+Fuchs Comtrol, Inc. support. 12-15 Reserved. 2.2.1.4. Common Services This table displays Common Services for Identity Object (01 hex, 1 Instance).

  • Page 27: Message Router Object (02 Hex)

    | Informational Objects | Message Router Object (02 Hex) | Class Attributes | 2.2.2. Message Router Object (02 Hex) The Message Router Object provides a messaging connection point through which a client may address a service to any object or instance residing in the physical device. 2.2.2.1.

  • Page 28: Connection Manager Object (06 Hex)

    | Informational Objects | Connection Manager Object (06 Hex) | Class Attributes Object (06 hex) | 2.2.3. Connection Manager Object (06 Hex) The Connection Manager Object provides services for connection and connection-less communications. 2.2.3.1. Class Attributes Object (06 hex) The following table displays the Class Attributes for the Connection Manager Object (06 hex). Attribute ID Name Data Type Data Value(s)

  • Page 29: Port Object (F4 Hex - 1 Instance)

    | Informational Objects | Port Object (F4 Hex - 1 Instance) | Class Attributes | 2.2.4. Port Object (F4 Hex - 1 Instance) The Port Object enumerates the CIP ports on the DeviceMaster EIP-MOD. 2.2.4.1. Class Attributes This table displays Class Attributes for Port Object (F4 hex - 1 Instance). Attribute Access Name...

  • Page 30: Instance Attributes (F4 Hex, Instance 2)

    | Informational Objects | Port Object (F4 Hex - 1 Instance) | Instance Attributes (F4 Hex, Instance 2) | Attribute Access Name Data Type Data Value(s) Rule 17 hex: • Bit 0: Routing of incoming Unconnected Messaging supported • Bit 1: Routing of outgoing Port Routing Capabilities UDINT Unconnected Messaging supported •...

  • Page 31: Common Services

    | Informational Objects | TCP Object (F5 Hex - 1 Instance) | Common Services | 2.2.4.4. Common Services This table displays Common Services for Port Object (F4 hex, Instance 2). Service Code Implemented in Class Implemented in Instance Service Name 01 hex Get_Attribute_All 0E hex...
  • Page 32 | Informational Objects | TCP Object (F5 Hex - 1 Instance) | Instance Attributes | Attribute Access Name Data Type Data Value(s) Rule Physical Link Object Structure of: Path Size UINT Path Array of USINT [0]=20 hex [1]=F6 hex [2]=24 hex [3]=01 hex Interface Configuration Structure of:...

  • Page 33: Common Services

    | Informational Objects | Ethernet Link Object (F6 Hex) | Common Services | 2.2.5.3. Common Services This table shows the Common Services for the TCP Object (F5 hex - I Instance). Service Code Implemented in Class Implemented in Instance Service Name 01 hex Get_Attribute_All 02 hex...

  • Page 34: Instance Attributes

    | Informational Objects | Ethernet Link Object (F6 Hex) | Instance Attributes | 2.2.6.2. Instance Attributes This table displays the Instance Attributes for the Ethernet Link Object (F6 hex). Attribute Name Data Type Data Value(s) Access Rule 10=10 Mbit Interface speed (Current UDINT operational speed) 100=100 Mbit...

  • Page 35: Common Services

    | Informational Objects | Assembly Object (For Class 1 Interface) | Common Services | 2.2.6.3. Common Services This table displays the Common Services for Ethernet Link Object (F6 hex). Service Code Implemented in Class Implemented in Instance Service Name 01 hex Get_Attribute_All 0E hex Get_Attribute_Single...

  • Page 36: Instance Attribute Definitions: Attribute 3-Request/Write Data

    | Informational Objects | Assembly Object (For Class 1 Interface) | Common Services | 2.2.7.2.1. Instance Attribute Definitions: Attribute 3-Request/Write Data Dependent on the instance number, this is either the PDI data block and/or the PDO data block. 2.2.7.2.2. Instance Attribute Definitions: Attribute 4-Data Length This is the maximum data length for each Assembly instance.

  • Page 37: All Available Instance Definitions

    | Informational Objects | Assembly Object (For Class 1 Interface) | Instance Definitions | Assembly Output Instances Assembly Access Instance Description Data Type Data Values Rule Number WORD Array Write data to Shared Memory 0-FFFF (hex) Holding Registers Block 2 Length = 200 WORD Array Write data to Shared Memory...
  • Page 38 | Informational Objects | Assembly Object (For Class 1 Interface) | Instance Definitions | Assembly Input Instances (Continued) Assembly Access Instance Description Data Type Data Values Rule Number WORD Array Read data from Shared 0-FFFF (hex) Memory Coils Block 4 Length = 20 Words (320 coils) WORD Array Read data from Shared...
  • Page 39 | Informational Objects | Assembly Object (For Class 1 Interface) | Instance Definitions | Assembly Output Instances (Continued) Assembly Access Instance Description Data Type Data Values Rule Number WORD Array Write data to Shared Memory 0-FFFF (hex) Coil Block 4 Length = 20 Words (320 coils) WORD Array Write data to Shared Memory...
  • Page 40 | Informational Objects | Assembly Object (For Class 1 Interface) | Instance Definitions | 40 - Chapter 2. EtherNet/IP Interface Profile (ControlLogix) DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 41: Chapter 3. Configuration Overview

    Chapter 3. Configuration Overview This chapter provides an overview of these topics: • 3.1. Home Page on Page 41 • 3.2. Serial Port - Configuration Overview on Page 43 3.1. Home Page If you have not configured the network information into the DeviceMaster EIP-MOD during initial setup, you must configure the network information before configuring serial/socket port characteristics.
  • Page 42 Home Page EtherNet/IP-Modbus Home Page Firmware EtherNet/IP-Modbus firmware version currently running on the DeviceMaster. You can enter a Device Name in the Network | Configuration page, which will Device Name display in this field. Serial Number The DeviceMaster EIP-MOD serial number. This is the MAC address of this DeviceMaster EIP-MOD, which is located on the MAC Address compliance label on the DeviceMaster EIP-MOD.

  • Page 43: Serial Port - Configuration Overview

    Serial Port - Configuration Overview 3.2. Serial Port - Configuration Overview Use the following steps to access the serial port configuration pages. 1. Open the DeviceMaster EIP-MOD web page using the IP address in your browser or PortVision DX. 2. Click the Serial menu, which opens the Serial Port Overview page. DeviceMaster EIP-MOD User Guide: 2000664 Rev.
  • Page 44 Serial Port - Configuration Overview 3. Click the port number that you want to configure and the Serial Settings | Port Configuration page appears. 4. Change the serial port configuration properties (Page 48) as required for your site. 5. Click the Save button. 44 - Chapter 3.

  • Page 45: Modbus Over Tcp Overview - Configuration Overview

    Modbus Over TCP Overview - Configuration Overview 3.3. Modbus Over TCP Overview - Configuration Overview Use the following overview to configure the Modbus device. 1. Click the Modbus menu, which opens the Modbus over TCP Overview (not Modbus/TCP) page. 2. Click the appropriate Socket number to access the Modbus over TCP (not Modbus/TCP) Socket Configuration page for that port.
  • Page 46 Modbus Over TCP Overview - Configuration Overview 3. Change the socket configuration properties (Page 53) as required for you site. 4. Click the Save button after completing the changes. 5. Repeat the previous steps for each serial port and Modbus device. 46 - Chapter 3.

  • Page 47: Chapter 4. Serial Menus

    Chapter 4. Serial Menus This section discusses the 4.1. Serial Port Overview Page 4.2. Serial Port Configuration Page on Page 48, which are located under the Serial menu. 4.1. Serial Port Overview Page The Serial Port Overview page displays information about the configured serial settings for each port. Valid Rcvd Msg Device ID Range (1-255) –...

  • Page 48: Serial Port Configuration Page

    Serial Port Configuration Page 4.2. Serial Port Configuration Page To access the Serial Port Configuration page, click Serial | Port x. 48 - Chapter 4. Serial Menus DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...
  • Page 49 Serial Port Configuration Page The following tables provide information about serial configuration settings. Serial Configuration Page Serial Configuration User-definable string used to describe the serial interface. Valid characters include Port Name (Default = a-z, A-Z, 0-9, underscores, spaces and dashes. All other characters are discarded. blank) The Port Name supports up to an 80 character ASCII string.
  • Page 50 Serial Port Configuration Page Serial Configuration Page (Continued) Rx Timeout Between Receive time-out (0-65535) between packets in msec. This is the maximum spacing Packets (ms) (Default between received bytes allowed before the received Modbus serial message is = 200) expected to be complete. On or Off: If selected, the DeviceMaster EIP-MOD drops all packets received with parity, framing, or overrun errors.
  • Page 51 Serial Port Configuration Page Serial Configuration Page (Continued) • 0 = disables Device ID Offset functionality. 1-254 = dependent on the Device ID Offset Mode, is added to or subtracted from • Device ID Offset the message device ID before the Modbus message is transmitted out the serial port.
  • Page 52 Serial Port Configuration Page 52 - Chapter 4. Serial Menus DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 53: Chapter 5. Modbus Menus

    Chapter 5. Modbus Menus This chapter discusses the following Modbus web pages: • 5.1. Modbus over TCP (not Modbus/TCP) Overview • 5.2. Modbus over TCP (not Modbus/TCP) Socket Configuration Page on Page 54 • 5.3. Modbus/TCP Configuration Page on Page 56 •...

  • Page 54: Modbus Over Tcp (Not Modbus/Tcp) Socket Configuration Page

    Modbus over TCP (not Modbus/TCP) Socket Configuration Page 5.2. Modbus over TCP (not Modbus/TCP) Socket Configuration Page Access the Modbus over TCP (not Modbus/TCP Socket Configuration page by clicking Modbus | TCP/IP Configuration | Socket x. The following table provides information about each configuration setting. Modbus over TCP (not Modbus/TCP) Socket Configuration Page TCP Configuration Modbus/RTU-to-Master –...
  • Page 55 Modbus over TCP (not Modbus/TCP) Socket Configuration Page Modbus over TCP (not Modbus/TCP) Socket Configuration Page (Continued) The Listen Port values are 1-65535. Listen Port  If Enable and Listen are both selected, allows acceptance of: (Defaults:  • Up to six connections from external applications if there is no active Port 1=8000...

  • Page 56: Modbus/Tcp Configuration Page

    Modbus/TCP Configuration Page 5.3. Modbus/TCP Configuration Page Access the Modbus/TCP Interface Configuration page by clicking Modbus | Modbus/TCP Configuration. The following table provides information about each configuration setting. Modbus/TCP Configuration Page Modbus TCP/IP Port 1 Enabled Always enabled. Cannot be disabled. TCP/IP Port The standard Modbus TCP/IP port of 502.

  • Page 57: Remote Modbus/Tcp Device Configuration

    Remote Modbus/TCP Device Configuration 5.4. Remote Modbus/TCP Device Configuration All Modbus devices not configured remotely are assumed to be local, or connected to this gateway. The location of all local Modbus devices is determined automatically. 1. Access the Remote Modbus/TCP Device Configuration page by clicking Modbus | Remote Modbus Configuration.
  • Page 58 Remote Modbus/TCP Device Configuration Remote Modbus/TCP Device Configuration Page (Continued) If selected, will disable broadcasts to this remote device. Disable Broadcast Note: If multiple remote devices are accessed through another gateway, then Messages (Default = this option must be selected for all remote devices configured to that Off) gateway to prevent broadcast messages from being sent to those devices.

  • Page 59: Modbus Alias Configuration

    Modbus Alias Configuration 5.5. Modbus Alias Configuration You can configure up to four alias device IDs at one time. 1. Access the Modbus Alias Device ID Configuration page by clicking Modbus | Alias Configuration. 2. Click the Add Alias Configuration button. The following configuration options apply: Modbus Alias Device ID Configuration Page The device ID (also often called the unit ID) of the received message...
  • Page 60 Modbus Alias Configuration 60 - Chapter 5. Modbus Menus DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 61: Chapter 6. Network Menus

    Chapter 6. Network Menus This section discusses the pages under the Network menu, which includes: • 6.1. Network Configuration Page on Page 61 • 6.2. Password Page on Page 63 • 6.3. Security Settings Page on Page 64 • 6.4. Key and Certificate Management Page on Page 65 •...
  • Page 62 Network Configuration Page The following table provides information about the Network Configuration fields. Network Configuration Page General You can enter a 16-character Device Name to identify this DeviceMaster EIP-MOD on Device Name the Home page. The TCP protocol has a keepalive feature where the two network stacks periodically ping each other to make sure the connection is still up.

  • Page 63: Password Page

    Password Page 6.2. Password Page You can easily set up a password to secure the DeviceMaster EIP-MOD. There is no password set from the factory. Use the following information to configure a password for this DeviceMaster EIP-MOD. 1. If necessary, click Network | Password. 2.

  • Page 64: Security Settings Page

    Encrypted access to the web server via port 443 (https:// URLs) is still allowed. Config Mode • Administrative commands that change configuration or operating state which are received using the Pepperl+Fuchs Comtrol, Inc. proprietary TCP driver protocol on TCP port 4606 are ignored. • Administrative commands that change configuration or operating state that are received using the Pepperl+Fuchs Comtrol, Inc.

  • Page 65: Key And Certificate Management Page

    For secure operation, the DeviceMaster EIP-MOD uses a set of three keys and certificates. These keys and certificates are user configurable. Note: All DeviceMaster EIP-MOD units are shipped from the factory with identical configurations. They all have the identical self-signed, Pepperl+Fuchs Comtrol, Inc. Server RSA Certificates, Server RSA Keys,  and Server DH Keys.
  • Page 66 Key and Certificate Management Page Key and Certificate Management Page This is a private/public key pair that is used for two purposes: • It is used by some cipher suites to encrypt the SSL/TLS handshaking messages. Possession of the private portion of this key pair allows an eavesdropper to both decrypt traffic on SSL/TLS connections that use RSA encryption during handshaking.

  • Page 67: Ethernet/Ip Stack Configuration

    EtherNet/IP Stack Configuration 6.5. EtherNet/IP Stack Configuration The default settings on the EtherNet/IP Stack Configuration page are recommended for most systems. Access the the EtherNet/IP Stack Configuration page by clicking Network | EtherNet/IP. EtherNet/IP Stack Configuration Page This is the network routing parameter that allows EtherNet/IP messages to be routed between different subnets.
  • Page 68 EtherNet/IP Stack Configuration EtherNet/IP Stack Configuration Page (Continued) Session Encapsulation Timeout The session encapsulation timeout instructs the DeviceMaster (0=disable; 1-3600 sec: EtherNet/IP-Modbus gateway how long to wait with no activity Default = 120 before timing out a session. If selected, The DeviceMaster EtherNet/IP-Modbus gateway provides support for the Vendor Specific Modbus Object Services.

  • Page 69: Chapter 7. Data Mapping Menus

    Chapter 7. Data Mapping Menus This chapter discusses the following web pages: • 7.1. Modbus to EtherNet/IP Tag/File Configuration Page on Page 69 • 7.2. EtherNet/IP Tag/File to Modbus Configuration Page on Page 72 • 7.3. Modbus to Modbus Configuration Page on Page 75 •...

  • Page 70: Modbus To Ethernet/Ip Tag/File Configuration Page

    Modbus to EtherNet/IP Tag/File Configuration Page The following table provides information about the options on this page. Modbus to EtherNet/IP Tag/File Configuration Page This is the configuration line number. • If the configuration entry has been saved, the line number is not directly modifiable.
  • Page 71 Modbus to EtherNet/IP Tag/File Configuration Page Modbus to EtherNet/IP Tag/File Configuration Page (Continued) Specifies the PLC type to write to: • ControlLogix – This selection enables the full CIP supported interfaces that provide CIP table read/write capabilities. The ControlLogix PLC family of PLCs includes the Rockwell ControlLogix, FlexLogix, SoftLogix and other advanced PLCs.

  • Page 72: Ethernet/Ip Tag/File To Modbus Configuration Page

    EtherNet/IP Tag/File to Modbus Configuration Page 7.2. EtherNet/IP Tag/File to Modbus Configuration Page Need supporting information. 1. Click Data Mapping | Tag/File to Modbus to open the EtherNet/IP Tag/File To Modbus Configuration page. 2. Click the Add Default Configuration button. The following table provides information about the options on this page.
  • Page 73 EtherNet/IP Tag/File to Modbus Configuration Page EtherNet/IP Tag/File To Modbus Configuration Page (Continued) EtherNet/IP (Read) Specifies the type of PLC to read from: • ControlLogix – This selection enables the full CIP supported interfaces that provide CIP table read/write capabilities. The ControlLogix PLC family of PLCs includes the Rockwell ControlLogix, FlexLogix, SoftLogix and other advanced PLCs.
  • Page 74 EtherNet/IP Tag/File to Modbus Configuration Page EtherNet/IP Tag/File To Modbus Configuration Page (Continued) Enter the Modbus address in Base 1 format. (The address of the tables starts at Address (Base 1) 1, instead of 0 for Base 0). (Default = 1) Enter only the lower 16 bits of the address (1-65536).

  • Page 75: Modbus To Modbus Configuration Page

    Modbus to Modbus Configuration Page 7.3. Modbus to Modbus Configuration Page Need supporting information. 1. Click Data Mapping | Modbus to Modbus to open the Modbus to Modbus Configuration page. 2. Click the Add Default Configuration button. The following table provides information about the options on this page. Modbus to Modbus Configuration Page This is the configuration line number.
  • Page 76 Modbus to Modbus Configuration Page Modbus to Modbus Configuration Page (Continued) Modbus (Read) The Modbus Device ID to be read. • If access to the Shared Memory is desired: The Shared Memory must be enabled. Device ID The Shared Memory device ID must be entered. •...
  • Page 77 Modbus to Modbus Configuration Page Modbus to Modbus Configuration Page (Continued) When this button is clicked: • The settings are verified. Save • Any changes are saved. • The Data Mapping process immediately is reconfigured and begins performing the configured operations. If selected, the entry is deleted from the list when Save is selected.

  • Page 78: Shared Memory Configuration Page

    Shared Memory Configuration Page 7.4. Shared Memory Configuration Page The Shared Memory functionality enables multiple methods for communicating between a wide variety of EtherNet/IP controllers, Modbus masters and Modbus slave devices. The Shared Memory interface contains eight 200 Holding Register blocks and eight 320 Coil blocks. •...
  • Page 79 Shared Memory Configuration Page This table shows the supported Coil Block Function Codes: Function Code Description Read Coils Read Discrete Inputs Write Single Coil Write Multiple Coils Click Data Mapping | Shared Memory to open the Shared Memory Configuration page. DeviceMaster EIP-MOD User Guide: 2000664 Rev.
  • Page 80 Shared Memory Configuration Page The following table provides details about the configuration options. Click the Display button to view detailed information about a specific block or coil. Shared Memory Configuration Page Enable Shared Memory (Default If selected, enables the Shared Memory functionality. = Off) The Device ID (also often called the unit ID) of the Shared Memory Shared Memory Device ID...
  • Page 81 Shared Memory Configuration Page Shared Memory Configuration Page (Continued) Indicates which master(s) have write access to the Shared Memory block. All (Except Class1) – Except for Class1 connections, all Modbus • masters, Modbus Object and Data Mapping functions have write access to the block.
  • Page 82 Shared Memory Configuration Page Shared Memory Configuration Page (Continued) Indicates which master(s) have write access to the Shared Memory block. All (Except Class1) – Except for Class1 connections, all Modbus • masters, Modbus Object and Data Mapping functions have write access to the block.

  • Page 83: Ethernet/Ip Class 1 Page

    EtherNet/IP Class 1 Page 7.5. EtherNet/IP Class 1 Page The DeviceMaster EIP-MOD provides a highly informative Class1 interface web page designed to provide easily understand information to aid the PLC programmer: • Instance numbers • Data offsets for each instance •...

  • Page 84: All Shared Memory Class1 Interface Page

    All Shared Memory Class1 Interface Page 7.5.2. All Shared Memory Class1 Interface Page If the Display All Shared Memory button is clicked, the following page displays. This page is provided to show the relationships of the active Class1 interface with the rest of the Shared Memory blocks. The following table provides information about this page.

  • Page 85: Data Mapping Verification Page

    Data Mapping Verification Page 7.6. Data Mapping Verification Page The Verify Data Mapping page is used to check for the following configuration problems. Configuration Issue Description Write conflicts to This occurs when two or more Data Mapping configurations can write to the EtherNet/IP PLCs same PLC tag or File locations.
  • Page 86 Data Mapping Verification Page • There are two separate conflicts writing to the same Shared Memory addresses. Conflicting settings are highlighted in red. 86 - Chapter 7. Data Mapping Menus DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 87: Shared Memory Map Page

    Shared Memory Map Page 7.7. Shared Memory Map Page The Shared Memory Map page is provided to show the Built-in Configuration and Class1 access to each Shared Memory block. Write conflicts are shown highlighted in red as shown in the second image. DeviceMaster EIP-MOD User Guide: 2000664 Rev.
  • Page 88 Shared Memory Map Page 88 - Chapter 7. Data Mapping Menus DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...
  • Page 89 Shared Memory Map Page Access the Data Mapping Shared Memory Map page by clicking Data Mapping | Shared Memory Map. 1. Select the shared holding register or coil block that you want to review. 2. Select Write Access or Read Access. DeviceMaster EIP-MOD User Guide: 2000664 Rev.
  • Page 90 Shared Memory Map Page 90 - Chapter 7. Data Mapping Menus DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 91: Chapter 8. Diagnostic Menus

    Chapter 8. Diagnostic Menus You can access the following diagnostic and statistics pages from the Diagnostics menu: This section discusses the following pages: • 8.1. Serial Communication Statistics Page on Page 92 • 8.2. Modbus RTU/ASCII over Ethernet TCP Statistics Page on Page 94 •...

  • Page 92: Serial Communication Statistics Page

    Serial Communication Statistics Page 8.1. Serial Communication Statistics Page The default Diagnostics menu page is the Serial Communication Statistics page. The following table provides detailed information about the Serial Communications Statistics page. Serial Communication Statistics Page TX Byte Count (To Device) Displays the number of bytes transmitted out the serial port.
  • Page 93 Serial Communication Statistics Page Serial Communication Statistics Page (Continued) Displays the number of framing errors received on the serial port. Framing Error Count Typically occurs due to an incorrect baud rate or stop bit setting. Displays the number of overrun errors received on the serial port. This Overrun Error Count typically occurs to one of the following events: incorrect flow control, incorrect baud rate, incorrect data size, or incorrect stop bit setting.

  • Page 94: Modbus Rtu/Ascii Over Ethernet Tcp Statistics Page

    Modbus RTU/ASCII over Ethernet TCP Statistics Page 8.2. Modbus RTU/ASCII over Ethernet TCP Statistics Page Click Diagnostics | Communication | TCP Statistics to access the Modbus RTU/ASCII over Ethernet TCP Statistics page. The following table provides information about Ethernet TCP/IP interface statistics on the Modbus RTU/ ASCII over Ethernet TCP Statistics page.
  • Page 95 Modbus RTU/ASCII over Ethernet TCP Statistics Page Modbus RTU/ASCII over Ethernet TCP Statistics Page (Continued) The number of messages from the application(s) that were dropped to: Dropped Invalid or • Containing an invalid Modbus message format. Incomplete RX Messages • Containing an incomplete Modbus message.

  • Page 96: Serial Interface Logs

    Serial Interface Logs 8.3. Serial Interface Logs Access the Serial Interface Logs page by clicking Diagnostics | Communication | Serial Logs. The Serial Interface Logs page provides a log of received and transmitted serial port messages. Up to 512 bytes per message and up to 32 messages are logged. It is intended to help with debugging serial connectivity problems, determining the proper start and end of transmission bytes, and diagnosing device problems.

  • Page 97: Known Modbus Slave Device List

    Known Modbus Slave Device List 8.4. Known Modbus Slave Device List The Known Modbus Slave Device List page provides device specific status and statistics for each device connected locally to one or more of the serial ports or remotely through a remote Modbus/TCP device configuration.
  • Page 98 Known Modbus Slave Device List Known Modbus Slave Device List Page - Public Devices (Continued) Displays the status of device: Yes means that the last request received a valid response and did not time out. • Active? No means that the last request timed out or the device has not yet received a •...
  • Page 99 Known Modbus Slave Device List Known Modbus Slave Device List Page - Private Devices (Continued) Requests Displays the number of private requests addressed to this Modbus device. Responses Displays the number of private responses from this Modbus device. Displays the number of private requests/responses addressed to/from this Modbus Req Or Resp? device that could not be identified specifically as either a request or a response.

  • Page 100: Modbus/Tcp And Serial Modbus Master Statistics Page

    Modbus/TCP and Serial Modbus Master Statistics Page 8.5. Modbus/TCP and Serial Modbus Master Statistics Page Click Diagnostics | Modbus Diagnostics | Modbus/TCP Interface to access the Modbus/TCP and Serial Modbus Master Statistics page, which is explained in the following table. Note: The Modbus/TCP interface uses the standard socket port of 502.
  • Page 101 Modbus/TCP and Serial Modbus Master Statistics Page Modbus/TCP and Serial Modbus Master Statistics Page Modbus/TCP Slave Mode Specific Statistics Active Modbus/TCP Slave Displays the current number of active Modbus/TCP slave connections. Connections These connections were initiated by a controller to the DeviceMaster. Modbus/TCP Slave Connections Displays the total number of Modbus/TCP slave connections that have Opened...
  • Page 102 Modbus/TCP and Serial Modbus Master Statistics Page Modbus/TCP and Serial Modbus Master Statistics Page (Continued) Remote Modbus/TCP Device Displays the number of messages to remote devices that were Timeouts determined to have timed out by this gateway. Unexpected Responses From Displays the number of responses received when no response was Modbus/TCP Slave(s) expected.
  • Page 103 Modbus/TCP and Serial Modbus Master Statistics Page Modbus/TCP and Serial Modbus Master Statistics Page (Continued) Non-Mode Specific Statistics/Diagnostics Displays the number of connections aborted when there are no available Modbus/TCP connections. This error occurs when the No Available Modbus/TCP maximum number of Modbus/TCP connections has been reached and Connection Errors the DeviceMaster EIP-MOD is attempting to form another Modbus/ TCP connection.

  • Page 104: Modbus/Tcp Connections Page

    Modbus/TCP Connections Page 8.6. Modbus/TCP Connections Page Access the Modbus/TCP Connections page by clicking Diagnostics | Modbus Diagnostics | Modbus/TCP Connections. Modbus/TCP Connections Page Slave Mode (From Master) Modbus/TCP Connections Note: Only displayed if active connections. Remote The Modbus/TCP master connection in IP Address:Port Number format Connection (xxx.xxx.xxx.xxx:pppp).
  • Page 105 Modbus/TCP Connections Page Modbus/TCP Connections Page (Continued) Master Mode (To Slave) Modbus/TCP Connections Note: Only displayed if active connections. Remote The Modbus/TCP master connection in IP Address:Port Number format Connection (xxx.xxx.xxx.xxx:pppp). Displays the number of Modbus requests that have been transmitted since the Tx Requests connection was opened.

  • Page 106: Modbus Alias Device Id Statistics Page

    Modbus Alias Device ID Statistics Page 8.7. Modbus Alias Device ID Statistics Page Access the Modbus Alias Device ID Statistics page by clicking Diagnostics | Modbus Diagnostics | Alias Diagnostics. Modbus Alias Device ID Statistics Page Displays the device ID (also often called the unit ID) of the received message Rx Device ID from a master.

  • Page 107: Shared Memory Contents

    Shared Memory Contents 8.8. Shared Memory Contents This page displays the contents of a Shared Holding Register and Shared Coil blocks. Access this page by clicking Diagnostics | Modbus Diagnostics | Shared Memory and select the Holding Register Block or Shared Coil Block that you want to display in the drop list. 8.8.1.
  • Page 108 Shared Holding Block Register Blocks Shared Memory Contents Page Shared Memory Click this button to jump to the Shared Memory Configuration page. Config button Click this button to reset the following: • Write messages Reset Statistics button • Read messages •...

  • Page 109: Shared Coil Blocks

    Shared Coil Blocks 8.8.2. Shared Coil Blocks This page displays the contents of the selected Shared Coil block. Access this page from the Shared Memory Configuration page and click Display next to the Coil block that you want to display. Shared Memory Contents Page - Shared Coil Blocks Buttons Shared Memory...
  • Page 110 Shared Coil Blocks Shared Memory Contents Page - Shared Coil Blocks (Continued) Drop Lists and Fields Shared Coil Block Use this drop list to display data for a specific Shared Holding Register Block or Drop List Shared Coil Block. Write Messages Displays the number of successful write messages to this Shared Memory block.

  • Page 111: Ethernet/Ip Interface Statistics Page

    Ethernet/IP Interface Statistics Page 8.9. Ethernet/IP Interface Statistics Page Access the EtherNet/IP Interface Statistics page by clicking Diagnostics | EtherNet/IP Diagnostics. EtherNet/IP Interface Statistics Page The number of active Ethernet/IP sessions. A session can: • Support both Class 1 I/O and Class 3 Messages Active Session Count •...
  • Page 112 Ethernet/IP Interface Statistics Page EtherNet/IP Interface Statistics Page (Continued) Broadcasts Messages Displays the number of broadcast messages received from the PLC(s). Received Class 3 Messages/ Displays the number of messages and responses sent to the PLC(s). Responses Transmitted Class 1 Output Updates The number of Class 1 output data updates received from the PLC or PLCs.

  • Page 113: Modbus To Ethernet/Ip Tag/File Diagnostics Page

    Modbus to EtherNet/IP Tag/File Diagnostics Page EtherNet/IP Interface Statistics Page (Continued) Displays the number of invalid message data errors. These errors occur when Invalid Message Data the DeviceMaster EIP-MOD receives a message that cannot be performed due Errors to invalid data. Displays the number of system resource errors.
  • Page 114 Modbus to EtherNet/IP Tag/File Diagnostics Page Modbus to EtherNet/IP Tag/File Diagnostics Page (Continued) Displays the number of no path conditions. No path conditions occur when any of the following occur: • There is no valid destination to send the Modbus message. No Path There are no serial ports configured as slave ports.

  • Page 115: Ethernet/Ip Tag/File To Modbus Diagnostics Page

    EtherNet/IP Tag/File to Modbus Diagnostics Page 8.11. EtherNet/IP Tag/File to Modbus Diagnostics Page Access the EtherNet/IP Tag/File to Modbus Diagnostics page by clicking Diagnostics | Data Mapping Diagnostics | Tag/File to Modbus. EtherNet/IP Tag/File to Modbus Diagnostics Page Line Displays the configuration line number. PLC Type Displays the EtherNet/IP PLC type that is being read from.

  • Page 116: Modbus To Modbus Diagnostics Page

    Modbus to Modbus Diagnostics Page EtherNet/IP Tag/File to Modbus Diagnostics Page (Continued) Reset Statistics Resets the statistics to all zero. 8.12. Modbus to Modbus Diagnostics Page Access the Modbus to Modbus Diagnostics page by clicking Diagnostics | Data Mapping Diagnostics | Modbus to Modbus.
  • Page 117 Modbus to Modbus Diagnostics Page Modbus to Tag/File Diagnostics Page Function code Displays the function being used to perform the write operation. Address (base 1) Displays the Modbus address in Base 1 format. Displays the number of write messages transmitted to the Shared Memory or Tx Messages Modbus device.

  • Page 118: System Log

    System Log 8.13. System Log The System Log page provides system level information, which is updated every 10 seconds. Click the Refresh button to view the latest system log information. • Click the Clear button to restart a new system log file. •...

  • Page 119: Chapter 9. System Menus

    Note: Optionally, you can use PortVision DX to upload firmware after unpackaging the .msi file. Use the following procedure to upload the latest firmware onto the DeviceMaster EIP-MOD. 1. If necessary, download the firmware from the Comtrol download site. 2. Execute the enetipmodbus-x.x.msi file.
  • Page 120 Update Firmware An Update In Progress pop up notifies you with the upload duration, not to reset or disconnect the device or to close the page. 120 - User Guide: 2000664 Rev. A Chapter 9. System Menus...

  • Page 121: Configuration File Page

    Configuration File Page 9.2. Configuration File Page You can use the Save Configuration option to save a DeviceMaster EIP-MOD configuration file for recovery purposes or to quickly configure other DeviceMaster EIP-MODs that require the same configuration using the Load Configuration option. Note: Optionally, you can use PortVision DX to save and load configuration files.

  • Page 122: Loading A Configuration File

    Loading a Configuration File 9.2.2. Loading a Configuration File You can use this procedure to load a previously saved DeviceMaster EIP-MOD configuration file. 1. Click System | Configuration File. 2. Click the Browse button, highlight the configuration file you want to load, and click the Open button. 3.

  • Page 123: System Snapshot Page

    System Snapshot Page 9.3. System Snapshot Page You can use the System Snapshot page to download a snapshot of the device status, log, and configuration. You may find the information can help you diagnose a problem with the DeviceMaster EIP-MOD. In addition, this information may be requested by technical support if you have called for assistance.

  • Page 124: Restore Defaults Page

    Restore Defaults Page 9.4. Restore Defaults Page You can easily some or all of your settings to factory defaults by using the procedure below. 1. Open your browser and enter the IP address of the DeviceMaster EIP-MOD. 2. Click System | Restore Defaults. 3.

  • Page 125: Reboot

    Reboot 9.5. Reboot You can reboot the DeviceMaster EIP-MOD remotely using the Reboot web page. 1. Click System | Reboot. 2. Click the Reboot Now button or wait the 10 seconds for it automatically reboot. Chapter 9. System Menus User Guide: 2000664 Rev. A - 125...
  • Page 126 Reboot 126 - User Guide: 2000664 Rev. A Chapter 9. System Menus...

  • Page 127: Chapter 10. Plc Programming For Modbus Object (44 Hex)

    Chapter 10. PLC Programming for Modbus Object (44 Hex) The CIP Modbus Object is supported on the DeviceMaster EtherNet/IP- Modbus gateway. This functionality provides the ability to send read and write messages directly to the Shared Memory or a Modbus slave device.
  • Page 128 | Read Discrete Inputs Service (4B Hex) Parameter Value Description Class 44 Hex Modbus Object Attribute Not used Source Element RdDiscreteInputsReqData Tag of structure type RdDiscreteInputsRequest Source Length Length in bytes of RdDiscreteInputsReqData Destination RdDiscreteInputsRespData Tag of structure type RdDiscreteInputsResponse Parameter Data Type Range...

  • Page 129: Read Coils Service (4C Hex)

    | Read Coils Service (4C Hex) 10.2. Read Coils Service (4C Hex) This service reads one or more coils from the Modbus Coils table. This service results in the DeviceMaster EIP-MOD issuing a Read Coils function (function code 0x01) to either the Shared Memory or the Modbus Message Routing subsystem.
  • Page 130 | Read Coils Service (4C Hex) Parameter Data Type Range Description startAddress INT (16 bit WORD) 0 to FFFF hex Starting address base 0 numCoils INT (16 bit WORD) 1 to 2000 (7D0 hex) Number of coils represented by a single bit. Parameter Data Type Range...

  • Page 131: Read Input Registers Service (4D Hex)

    | Read Input Registers Service (4D Hex) 10.3. Read Input Registers Service (4D Hex) This service reads one or more input registers from the Modbus Input Register table. This service results in the DeviceMaster EIP-MOD issuing a Read Input Registers function (function code 0x04) to either the Shared Memory or the Modbus Message Routing subsystem.
  • Page 132 | Read Input Registers Service (4D Hex) Parameter Data Type Range Description startAddress INT (16 bit WORD) 0 to FFFF hex Starting address base 0 numRegisters INT (16 bit WORD) 1 to 125 (7D0 hex) Number input registers to read. Parameter Data Type Range...

  • Page 133: Read Holding Registers Service (4E Hex)

    | Read Holding Registers Service (4E Hex) 10.4. Read Holding Registers Service (4E Hex) This service reads one or more holding registers from the Modbus Holding Register table. This service results in the DeviceMaster EIP-MOD issuing a Read Holding Registers function (function code 0x03) to either the Shared Memory or the Modbus Message Routing subsystem.
  • Page 134 | Read Holding Registers Service (4E Hex) Parameter Data Type Range Description startAddress INT (16 bit WORD) 0 to FFFF hex Starting address base 0 numRegisters INT (16 bit WORD) 1 to 125 (7D0 hex) Number holding registers to read. Parameter Data Type Range...

  • Page 135: Write Coils Service (4F Hex)

    | Write Coils Service (4F Hex) 10.5. Write Coils Service (4F Hex) This service writes one or more coils to the Modbus Coils table. This service results in the DeviceMaster EIP- MOD issuing a Write Multiple Coils function (function code 0x0F) to either the Shared Memory or the Modbus Message Routing subsystem.
  • Page 136 | Write Coils Service (4F Hex) Parameter Data Type Range Description startAddress INT (16 bit WORD) 0 to FFFF hex Starting address base 0 numCoils INT (16 bit WORD) 1 to 1968 (7b0 hex) Number of coils represented by a single bit. coilData SINT array 00 to FF hex...

  • Page 137: Write Holding Registers Service (50 Hex)

    | Write Holding Registers Service (50 Hex) 10.6. Write Holding Registers Service (50 Hex) This service writes one or more holding registers to the Modbus Holding Registers table. This service results in the DeviceMaster EIP-MOD issuing a Write Multiple Registers function (function code 0x10) to either the Shared Memory or the Modbus Message Routing subsystem.
  • Page 138 | Write Holding Registers Service (50 Hex) Parameter Data Type Range Description startAddress INT (16 bit WORD) 0 to FFFF hex Starting address base 0 numRegs INT (16 bit WORD) 1 to 123 Number holding registers to write. registerData INT array 0-FFFF hex Holding register data Parameter...
  • Page 139 | Write Holding Registers Service (50 Hex) DeviceMaster EIP-MOD does not attempt to perform any endian conversion on the bytes in the data stream (either request or response). Refer to CIP Standard Vol1_3.22 Section 5B-3 and/or MODBUS Application Protocol Specification V1.1b3.pdf at www.modbus.org for more details.
  • Page 140 | Write Holding Registers Service (50 Hex) Parameter Data Type Range Description Modbus Message to be passed through. Byte 0: Function Code Bytes 1-n: Message parameters Note: data SINT array 0 to FF hex • PLC operates in little endian format. •...

  • Page 141: Vendor Specific Write Single Coil Service (70 Hex)

    | Vendor Specific Write Single Coil Service (70 Hex) 10.7. Vendor Specific Write Single Coil Service (70 Hex) This service writes one coil to the Modbus Coils table. This service results in the DeviceMaster EIP-MOD issuing a Write Single Coil function (function code 0x05) to either the Shared Memory or the Modbus Message Routing subsystem.
  • Page 142 | Vendor Specific Write Single Coil Service (70 Hex) Parameter Data Type Range Description address INT (16 bit WORD) 0 to FFFF hex Coil address base 0 0 = Off data INT (16 bit WORD) Coil data to write 1 = On Parameter Data Type Range...

  • Page 143: Vendor Specific Write Single Register Service (71 Hex)

    | Vendor Specific Write Single Register Service (71 Hex) 10.8. Vendor Specific Write Single Register Service (71 Hex) This service writes one holding register to the Modbus Holding Registers table. This service results in the DeviceMaster EIP-MOD issuing a Write Single Registers function (function code 0x06) to either the Shared Memory or the Modbus Message Routing subsystem.
  • Page 144 | Vendor Specific Write Single Register Service (71 Hex) Parameter Data Type Range Description address INT (16 bit WORD) 0 to FFFF hex Holding register address base 0 data INT (16 bit WORD) 0 to FFFF hex Register data to write Parameter Data Type Range...

  • Page 145: Vendor Specific Write Mask Register (72 Hex)

    | Vendor Specific Write Mask Register (72 Hex) 10.9. Vendor Specific Write Mask Register (72 Hex) This service performs a write mask operation on one holding register in the Modbus Holding Registers table. This service results in the DeviceMaster EIP-MOD gateway issuing a Write Mask Register function (function code 0x16) to either the Shared Memory or the Modbus Message Routing subsystem.
  • Page 146 | Vendor Specific Write Mask Register (72 Hex) Parameter Data Type Range Description address INT (16 bit WORD) 0 to FFFF hex Holding register address base 0 andMask INT (16 bit WORD) 0 to FFFF hex And mask orMask INT (16 bit WORD) 0 to FFFF hex Or mask 1.
  • Page 147 | Vendor Specific Write Mask Register (72 Hex) Parameter Data Type Range Description address INT (16 bit WORD) 0 to FFFF hex Holding register address base 0 andMask INT (16 bit WORD) 0 to FFFF hex And mask orMask INT (16 bit WORD) 0 to FFFF hex Or mask DeviceMaster EIP-MOD User Guide: 2000664 Rev.

  • Page 148: Vendor Specific Read/Write Holding Registers (73 Hex)

    | Vendor Specific Read/Write Holding Registers (73 Hex) 10.10. Vendor Specific Read/Write Holding Registers (73 Hex) This service performs first write and then read operations on multiple holding registers in the Modbus Holding Registers table. This service results in the DeviceMaster EIP-MOD gateway issuing a Read/Write Holding Registers function (function code 0x17) to either the Shared Memory or the Modbus Message Routing subsystem.
  • Page 149 | Vendor Specific Read/Write Holding Registers (73 Hex) Parameter Data Type Range Description startRdAddress INT (16 bit WORD) 0 to FFFF hex Start read holding register address base 0 numRdRegs INT (16 bit WORD) 0 to 125 Number of registers to read startWrAddress INT (16 bit WORD) 0 to FFFF hex Start write holding register address base 0 numWrRegs INT (16 bit WORD) 0 to 121...
  • Page 150 | Vendor Specific Read/Write Holding Registers (73 Hex) 150 - Chapter 10. PLC Programming for Modbus Object (44 Hex) DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 151: Chapter 11. Class 1 Interface Definition

    Chapter 11. Class 1 Interface Definition The EtherNet/IP Class 1 interface web page displays the Class 1 parameters. Where the following Class1 interfaces are supported: Instance Length (in bytes) Input (To PLC) Holding Register Block 1 Only 1 - 400 Coil Block 1 Only 1 - 40 Both Holding Register Block 1 and Coil Block 1...
  • Page 152 | Configuring an I/O Ethernet Module on a ControlLogix PLC 3. Scroll down and select Generic Ethernet Module. 4. Click OK. The following pane appears. a. Enter a Name. b. Select the Comm Format as Data-INT. Enter the IP Address of the gateway. d.
  • Page 153 | Configuring an I/O Ethernet Module on a ControlLogix PLC 5. Click OK. The following pane will appear. a. The fastest allowable RPI is 10 ms. b. Both Unicast, (point-to-point), and Multicast, (one-to-many), connections are supported. 6. Click OK. The module will be added. 7.
  • Page 154 | Configuring an I/O Ethernet Module on a ControlLogix PLC Output tag: 154 - Chapter 11. Class 1 Interface Definition DeviceMaster EIP-MOD User Guide: 2000664 Rev. A...

  • Page 155: Chapter 12. Troubleshooting And Technical Support

    Chapter 12. Troubleshooting and Technical Support This section contains troubleshooting information for your DeviceMaster EIP-MOD. You should review the following subsections before calling Technical Support because they will request that you perform many of the procedures or verifications before they will be able to help you diagnose a problem. •...

  • Page 156: General Troubleshooting

    General Troubleshooting • Reboot the system and the DeviceMaster EIP-MOD. • If you have a spare DeviceMaster EIP-MOD, try replacing the device. 12.2. General Troubleshooting This table illustrates some general troubleshooting tips. Note: Make sure that you have reviewed the Troubleshooting Checklist (Page 155). General Condition Explanation/Action Indicates that boot program has not downloaded to the unit.

  • Page 157: Daisy-Chaining Devicemaster Eip-Mod Units With Two Ethernet Ports

    Ethernet standards and will be determined by your own environment and the conformity of your network to these standards. Pepperl+Fuchs Comtrol, Inc. has tested with seven DeviceMaster EIP-MOD units daisy-chained together using 10 foot CAT5 cables, but this is not the theoretical limit. You may experience a performance hit on the devices at the end of the chain, so it is recommended that you overload and test for performance in your environment.

  • Page 158: Technical Support

    If you need technical support, use one of the following methods. Pepperl+Fuchs Comtrol, Inc. Contact Information Downloads http://downloads.comtrol.com/html/DM_EIP_MOD_main.htm...

Table of Contents