Automationdirect.com HX-ECOM Series Manual

Table of Contents

Quick Links

Download this manual

HX-ECOM Manual

Manual Number: HX-ECOM-M

Table of Contents

Troubleshooting

Need help?

Do you have a question about the HX-ECOM Series and is the answer not in the manual?

Questions and answers

Summary of Contents for Automationdirect.com HX-ECOM Series

Page 1 HX-ECOM Manual Manual Number: HX-ECOM-M...
Page 2 Copyright 2018, AutomationDirect.com Incorporated All Rights Reserved No part of this manual shall be copied, reproduced, or transmitted in any way without the prior, written consent of AutomationDirect.com Incorporated. AutomationDirect retains the exclusive rights to all information included in this document.
Page 3 Esta publicación puede contener referencias a productos producidos y/u ofrecidos por otras compañías. Los nombres de las compañías y productos pueden tener marcas registradas y son propiedad única de sus respectivos dueños. Automationdirect.com, renuncia cualquier interés propietario en las marcas y nombres de otros.
Page 4 Nulle partie de ce manuel ne doit être copiée, reproduite ou transmise de quelque façon que ce soit sans le consentement préalable écrit de la société Automationdirect.com Incorporated. AutomationDirect conserve les droits exclusifs à l’égard de tous les renseignements contenus dans le présent document.
Page 5 anual evisions Please include the Manual Number and the Manual Issue, both shown below, when communicating with Technical Support regarding this publication. Manual Number: HX-ECOM-M Issue: 3rd Edition Rev. D Issue Date: 12/18 Issue Date Description of Changes Original 4/98 Original Issue Added DL250-1 and DL260 references Removed DL250 references and made minor changes...
Page 6: Table Of Contents
able of onTenTs Chapter 1 - Introduction Introduction ....................... 1–2 The Purpose of this Manual ..................1–2 Other Reference Materials ..................1–2 Who Should Read this Manual ................. 1–2 Quality Technical Support ..................1–3 Conventions Used ...................... 1–3 Key Topics for Each Chapter ..................1–3 ECOM Module Introduction ..................
Page 7 Table of Contents ECOM Network Layouts ..................2–11 Network Cabling ...................... 2–13 ECOM Supports Two Standards ................2–13 10/100BaseT Networks ..................2–13 10/100BaseT Connections ..................2–14 UTP Cable ......................2–14 10BaseFL Connections .................... 2–14 Fiber Optic Cable ....................2–14 Fiber Optic Module ST Connector ................
Page 8 Table of Contents Chapter 4 - RLL Programming for Communications PLC-to-PLC Communications ..................4–2 How RLL is Used for Communications ..............4–2 Network Instructions ....................4–3 Read (RX) and Write (WX) Instructions ..............4–3 Building the Read (RX) and Write (WX) Routine ............4–3 The First LD Instruction ....................
Page 9 Table of Contents Second RX/WX Instruction ..................4–19 Third RX/WX Instruction ..................4–19 Shift Register ......................4–20 Store If Equal ......................4–20 First RX/WX Instruction ..................4–21 Second RX/WX Instruction ..................4–21 Third RX/WX Instruction ..................4–21 Chapter 5 - Modbus TCP for H0/H2/H4-ECOM100 Modbus TCP ......................
Page 10 Table of Contents Multiple Read and Write Interlocks ................. 5-21 ECOM100 IBOX ....................5-22 Modbus TCP Setup ....................5-24 Example Modbus TCP Program ................5-26 Troubleshooting: ....................5-26 H0/H2/H4 -ECOM100 System Memory ..............5-30 Chapter 6 - H0/H2/H4-ECOM100 DHCP & HTML Configuration H0/H2/H4 -ECOM100 DHCP ..................
Page 11 Table of Contents ACTIVE Indicator ...................... 7-6 ERROR Indicator ....................... 7-6 100MBIT Indicator ....................7-6 Using NetEdit3 for Troubleshooting ................. 7-7 Select a Module ....................... 7-7 Module Information ....................7-7 Change Protocol ...................... 7-8 Ethernet Stats ......................7-8 RX/WX Settings ......................7-9 Record the Module Settings ..................
Page 12: Chapter 1 - Introduction
hapter hapter hapter ntroductIon In This Chapter... Introduction ....................... 1–2 Conventions Used ...................... 1–3 Frequently Asked Questions ..................1–6...
Page 13: The Purpose Of This Manual
Chapter 1: Introduction Introduction The Purpose of this Manual This manual describes how to use the Ethernet Communication (ECOM) Modules. You will find information about: • Setting up the ECOM module • Network layouts • PC-to-PLC communications • PLC-to-PLC communications •...
Page 14: Quality Technical Support
If you have a comment, question or suggestion about any of our products, services, or manuals, please fill out and return the Suggestions card that was included with this manual.
Page 15: Ecom Module Introduction
Chapter 1: Introduction ECOM Module Introduction Several Ethernet Communication (ECOM) modules are currently available for use with DL05/06, DL205 and DL405 PLC systems. The ECOM modules are shown below. These modules provide a low-cost, high-speed Ethernet link for PLC systems. The modules are easy to set up and install on 10/100BaseT (twisted pair, copper wire) or 10BaseFL (fiber optic) Ethernet networks.
Page 16: Your Network Pc
You can use a personal computer equipped with a 10/100BaseT or 10BaseFL network adapter card and NetEdit3 software to configure the ECOM module over the network. You can also use NetEdit3 for troubleshooting certain communication problems. The NetEdit3 utility is available for download at http://www.automationdirect.com. Ethernet Communications Modules, 3rd Edition, Rev. D 1–5...
Page 17: Frequently Asked Questions
Chapter 1: Introduction Frequently Asked Questions . Q How can I speed up my ECOM communications? . A Try shortening the scan time of the PLC (the PLC allows only one ECOM transaction per scan). . Q What causes “Task code error response” with extended E353 error? .
Page 18 hapter hapter hapter etup and nStallatIon In This Chapter... ECOM Network Identifiers ..................2–2 Setting the Module ID with the DIP Switch ............. 2–5 Inserting the ECOM Module in the PLC Base ............2–7 ECOM Network Layouts ..................2–10 Network Cabling ...................... 2–12 Maximum Cable Length ..................
Page 19: Chapter 2: Setup And Installation
Chapter 2: Setup and Installation ECOM Network Identifiers This section describes network identifiers that can be assigned to the ECOM module. Each module must be assigned at least one unique identifier to make it possible for PCs or other ECOMs to recognize it on the network. Four methods of identifying the ECOM module give it the flexibility to fit most networking schemes.
Page 20: Module Id
Chapter 2: Setup and Installation Module ID A Module ID is required for PLC-to-PLC communications, and it can be set either of two ways. You can assign the Module ID: • Using the DIP switches on the module. • Using the configuration tools in NetEdit3 •...
Page 21: Example
Chapter 2: Setup and Installation An IP Address can be assigned to the ECOM module if your network requires one. Usually, the IP Address is required in cases where PLCs are sharing the same network with PCs, and some of the PCs are carrying out functions unrelated to PLC control.
Page 22: Setting The Module Id With The Dip Switch
Chapter 2: Setup and Installation Setting the Module ID with the DIP Switch The ECOM’s DIP switches contain eight individual slide switches, but not all of these are active. The individual slide switches are labeled 1 through 8 on the body of the DIP switch (upside down in the following figures).
Page 23: H0 / H2 Series Ecom Dip Switch
Chapter 2: Setup and Installation H0 / H2 Series ECOM DIP Switch If using the ECOM/ECOM100 module with Dataworx software, or the ECOM100 with IBox Communication instructions, then dipswitch 7 must be set to ON. The Module ID equals the sum of the binary values of the slide switches set in the ON position. For example, if you set slide switches 1, 2, and 3 to the ON position, the Module ID will be 14.
Page 24: H4 Series Ecom Dip Switch
Chapter 2: Setup and Installation H4 Series ECOM DIP Switch The Module ID equals the sum of the binary values of the slide switch set in the ON position. For example, if you set slide switches 0, 1, and 3 to the ON position, the Module ID will be 11.
Page 25: Inserting The Ecom Module In The Plc Base
Chapter 2: Setup and Installation 2- -7 Setup and Installation Inserting the ECOM Module in the PLC Base H0 Series ECOM Module Installation Inserting the ECOM Module in the PLC Base Before installing the option module in the DL05 option slot or any of the DL06 option slots, 2- -7 H0 Series ECOM Before installing the option module in the DL05 option slot or any of the DL06 option...
Page 26: H2 Series Ecom Module
Chapter 2: Setup and Installation H2 Series ECOM Module Module Type CPU - Base Usuable Slots H2-ECOM D2-240 D2-03B-1, D2-03BDC1-1, D2-03BDC-2 H2-ECOM100 D2-250-1 D2-04B-1, D2-04BDC1-1, D2-04BDC-2 1, 2 H2-ECOM-F D2-260 D2-06B-1, D2-06BDC1-1, D2-06BDC-1 1, 2, 3, 4 D2-262 D2-09B-1, D2-09BDC1-1, D2-09BDC-1 1, 2, 3, 4, 5, 6, 7 Retaining Clips Before installing the module, verify power to the PLC is turned off.
Page 27: Dl405 Slot Choices
Chapter 2: Setup and Installation DL405 Slot Choices For PLC systems with D4-430 and D4-440 CPUs, the ECOM modules can reside in any I/O slot but only in the CPU-base. The D4-450 and D4-454 CPUs allows the installation of the ECOM module in the CPU-base or in local expansion bases.
Page 28: H4 Series Ecom
Chapter 2: Setup and Installation H4 Series ECOM Before installing the ECOM module, verify power to the PLC is turned off. To insert the ECOM module in a DL405 base, place the bottom tab of the module into Module Installation the notch at the bottom of the base.
Page 29 Chapter 2: Setup and Installation Hub or Repeater 10/100BaseT 10BaseFL Star Topology Hubs or repeaters can connect together to make it possible to connect more devices to the network or to extend the range of the network 10BaseT Any Backbone 10Base2 10BaseFL 10Base5...
Page 30: Network Cabling
Chapter 2: Setup and Installation Network Cabling ECOM Supports Two Standards Two types of ECOMs are available. One type supports the 10/100BaseT cabling standard, and the other supports the 10BaseFL connection standard. The 10/100BaseT standard uses twisted pairs of copper wire conductors, and the 10BaseFL standard is for fiber optic cabling. 10/100BaseT 10BaseFL Unshielded...
Page 31: 10/100Baset Connections
Chapter 2: Setup and Installation 10/100BaseT Connections Most 10/100BaseT hubs or repeaters use a patch (straight-through) cable for connecting the network devices (PLCs or PCs). For hub-to-hub connections a crossover type cable is commonly required. The figures on the previous page show pin assignments and insulation color codes for patch (straight-through) and crossover type Ethernet cables.
Page 32: Maximum Cable Length
Chapter 2: Setup and Installation Maximum Cable Length The maximum distance per 10/100BaseT cable segment is 100 meters or 328 feet. Repeaters extend the distance. Each cable segment attached to a repeater can be 100 meters. Two repeaters connected together extend the total range to 300 meters. 10/100BaseT Distance Limitations 100 meters 100 meters...
Page 33: Maximum Number Of Ecom Modules On The Network
Chapter 2: Setup and Installation Maximum Number of ECOM Modules on the Network The maximum number of nodes that can be connected to a 10/100BaseT or 10BaseFL network is a function of the topology used in constructing the network. Therefore, it is not possible to state an absolute maximum number of nodes that would apply in all cases.
Page 34 NOTE: Please reference the BRX MPU system user manual (BX-USER-M) Appendix E for an updated guide to using the NetEdit utility. This manual can be downloaded at www.automationdirect.com. For the latest version and information on NetEdit, please visit www.hosteng.com, under the Utilities and FAQs sections.
Page 35: Chapter 3: Configuring Ecoms Using Netedit3
Installing NetEdit3 You can install NetEdit3 on Windows98/ME/2000/XPt or Windows NT4t. NetEdit3 is available online at www.automationdirect.com. After loading the software the following window will appear. Click on Install NetEdit3. A series of windows will step you through the installation process.
Page 36: Launching Netedit3
Chapter 3: Configuring ECOMs Using NetEdit3 Launching NetEdit3 There are three methods to launch NetEdit3. The three methods are: • using the Windows Start menu Programs>AutomationDirect Tools> NetEdit3 as shown below • launching DirectSoft (if installed), from the programming window, select PLC>Tools>NetEdit3 •...
Page 37: Adding Network Protocol Support To The Netedit3 Pc
Chapter 3: Configuring ECOMs Using NetEdit3 Adding Network Protocol Support to the NetEdit3 PC You may have already set up your PC with selected networking protocols for Ethernet communications. If not, you will need to select the protocols now for communication with the Ethernet modules.
Page 38: Using Netedit3
Chapter 3: Configuring ECOMs Using NetEdit3 Using NetEdit3 This section steps through the features and uses of NetEdit3. We will describe the individual segments of the NetEdit3 screen and the function of each. NOTE: Your PC-based Control software may be capable of configuring the EBC module. If so, please refer to the appropriate documentation for that software product to determine the best method to configure the EBC.
Page 39: Ethernet Address
Chapter 3: Configuring ECOMs Using NetEdit3 Ethernet Address The upper left section of the NetEdit3 screen displays the Ethernet Address of the modules currently on the network. If modules are added or removed from the network, click on the Scan Network button to update list.
Page 40: Module Info> General Information
Chapter 3: Configuring ECOMs Using NetEdit3 Module Info> General Information When the Module Info tab is selected, the General Info box lists the selected module’s Firmware Revision, Booter Revision, DIP Switch Setting, PWB Revision, PLD Revision and CPU Revision. This box is in the lower left section of the NetEdit3 screen. Module Info>...
Page 41: Ecom Settings> Configuration> General
Chapter 3: Configuring ECOMs Using NetEdit3 ECOM Settings> Configuration> General Clicking General button ECOM Settings>Configuration box brings up the General Settings window below. The General Settings box allows you to assign a Module ID. Module IDs must be unique for each ECOM, but they do not have to be in sequence.
Page 42: Ecom Settings> Configuration> Advanced
Chapter 3: Configuring ECOMs Using NetEdit3 ECOM Settings> Configuration> Advanced Clicking Advanced button ECOM Settings>Configuration box brings up the ECOM Advanced Settings window below. RX/WX - Settings box in this window provides a place to make changes that affect PLC-to-PLC communications. ACK Timeout - sets the time limit for receiving the acknowledge (ACK) response to an RX or WX instruction.
Page 43: Ecom Settings> Configuration> Peer To Peer
Chapter 3: Configuring ECOMs Using NetEdit3 ECOM Settings> Configuration> Peer to Peer This function allows you to configure the client H0/H2/H4 -ECOM(100) module to use an IP protocol packet to perform the RX/WX instruction, as opposed to a broadcast packet to locate the slave ECOM or MODBUS TCP server.
Page 44 Chapter 3: Configuring ECOMs Using NetEdit3 Clicking on the Find Hx-ECOM button in the Add Device Address window will display the Select ECOM window shown to the right. Highlight the server ECOM that you intend to communicate with peer to peer via the client ECOM(100) module.
Page 45: Ecom Settings> Utils>Test Cpu Access
Chapter 3: Configuring ECOMs Using NetEdit3 ECOM Settings> Utils>Test CPU Access Clicking the Test CPU Access button in the ECOM Settings>Utilities box brings up the window shown below. The ECOM has two distinct “sides”, the network side, which contains the network configuration settings, and the backplane side, which the ECOM uses to communicate with the PLC CPU.
Page 46: Filemenu> Live Update
Chapter 3: Configuring ECOMs Using NetEdit3 FileMenu> Live Update The Live Update will retrieve the latest firmware and boot loader files from the Host Engineering web site and place them in the NetEdit3 Images folder that was created during the install of NetEdit3. The feature requires that you have a functional Internet connection (dial- up or broadband).
Page 47 hapter hapter hapter RLL P RogRamming foR ommuniCations In This Chapter... PLC-to-PLC Communications ..................4–2 How RLL is Used for Communications ..............4–2 Network Instructions ....................4–3 Addressing the Different Memory ................4–6 Special Relays for Communications ................ 4–11 Program with One Read Instruction ............... 4–13 Example Program with One Write Instruction ............
Page 48: Chapter 4: Rll Programming For Communications
Chapter 4: RLL Programming for Communications PLC-to-PLC Communications This chapter steps you through the development of a Relay Ladder Logic (RLL) program to enable one PLC to communicate with another PLC. For the experienced programmer of DirectLOGIC PLCs, the communication programs presented in this chapter will be simple to follow.
Page 49: Network Instructions
Chapter 4: RLL Programming for Communications Network Instructions Read (RX) and Write (WX) Instructions The Read (RX) and Write (WX) instructions are used by the initiating PLC to Read a block of data from another PLC or Write a block of data to another PLC. To perform their functions, the RX and WX boxes must be preceded in the ladder logic program by two Load instructions and one Load Address instruction.
Page 50: The Second Ld Instruction
Chapter 4: RLL Programming for Communications The Second LD Instruction The second Load (LD) instruction determines the length of the data block to be transmitted during the Read or Write K114 communication. This instruction will also accept two data types. Use a “K” to designate the number as a constant. Use a “V”...
Page 51: Read (Wx) Instruction
Chapter 4: RLL Programming for Communications Read (WX) Instruction The Read (RX) instruction specifies the memory location to K114 be read from the responding PLC. A block of data is read that begins at the specified memory location and extends the number of bytes specified in the second LD instruction.
Page 52: Addressing The Different Memory
Chapter 4: RLL Programming for Communications Addressing the Different Memory Some data types are inherently 16 bits long, for example timer and counter current values. Other data types are 1 bit long, for example: discrete inputs and outputs. Word-length and bit-length data are mapped into Word Memory, also known as V-memory, which allows you to address any of the different memory types as 16-bit words.
Page 53: Directsoft Is Flexible
Chapter 4: RLL Programming for Communications DirectSOFT is Flexible You can address the different data types by any available convention shown in the tables that follow. The largest block of data that can be sent in a single Read or Write operation is 128 bytes.
Page 54: D2-240 Cpu
Chapter 4: RLL Programming for Communications NOTE: The D2-230 CPU does not support the ECOM modules. D2-240 CPU D2-240 CPU Data Type Bit Memory Word Memory Alias Timer Current Values V0 – V177 TA0 – TA177 Counter Current Values V1000 – V1177 CTA0 –...
Page 55: D2-260/D2-262 Cpu
Chapter 4: RLL Programming for Communications D2-260/D2-262 CPU D2-260/D2-262 CPU Data Type Bit Memory Word Memory Alias Timer Current Values V0 – V377 TA0 – TA377 Counter Current Values V1000 – V1377 CTA0 – CTA377 None V400 – V777 User Data Words V1400 –...
Page 56: D4-440 Cpu
Chapter 4: RLL Programming for Communications D4-440 CPU D4-440 CPU Data Type Bit Memory Word Memory Alias Timer Current Values V0 – V377 TA0 – TA377 Counter Current Values V1000 – V1177 CTA0 – CTA177 None V1400 – V7377 User Data Words None V10000 –...
Page 57: Special Relays For Communications
Chapter 4: RLL Programming for Communications Special Relays for Communications The DirectLOGIC PLCs provide internal contacts (bits) for monitoring the status of communications. The internal contacts are called Special Relays (there are other Special Relays used for other purposes). There are two Special Relays for each slot in the base that will accept the ECOM module.
Page 58 Chapter 4: RLL Programming for Communications D2-240, D2-250-1, D2-260 and D2-262 Special Purpose Communication Relays CPU Base Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Communication Busy SP122 SP124 SP126 SP130 SP132 SP134 SP136 SP123 SP125 SP127...
Page 59: Program With One Read Instruction
Chapter 4: RLL Programming for Communications Program with One Read Instruction The Ladder View screen below is the program development screen in DirectSOFT Programming Software. This four-rung program is explained in detail on page 4-14. This is a complete program although its function is very limited. There is also a two-rung program that runs in the responding PLC, and it is also explained on page 4-14.
Page 60 Chapter 4: RLL Programming for Communications Rung 1 In our example, the normally open contact labeled C0 is an internal control relay. When C0 is on, discrete output Y0 is energized. Rung 2 The second rung uses a Special Relay to identify a communication error.
Page 61: Example Program With One Write Instruction
Chapter 4: RLL Programming for Communications Example Program with One Write Instruction The Ladder View screen below is the program development screen in DirectSOFT Programming Software. This four-rung program is explained in detail on page 4-16. This is a complete program although its function is very limited.
Page 62 Chapter 4: RLL Programming for Communications Rung 1 In our example, the normally open contact labeled X0 is a toggle switch input to a discrete input module. When X0 is on, Control Relay C0 is energized. Rung 2 The second rung uses a Special Relay to identify a communication error.
Page 63: Integrating Multiple Read And Write Instructions
Chapter 4: RLL Programming for Communications Integrating Multiple Read and Write Instructions Multiple Read and Write instructions require interlocks for sequencing because only one RX/ WX instruction can be processed per CPU scan. Using interlocks, one RX/WX instruction is processed in each scan until all RX/WX instructions have been executed. After the last instruction, the sequence then begins again at the first RX/WX instruction.
Page 64: First Rx/Wx Instruction
Chapter 4: RLL Programming for Communications Our three RX/WX instructions can be Truth Table sequenced by the two contacts C50 and C51. Two contacts provide four different binary First RX/WX states: Second RX/WX Third RX/WX • Both off Fourth RX/WX •...
Page 65: Second Rx/Wx Instruction
Chapter 4: RLL Programming for Communications Second RX/WX Instruction SP122 C50 is normally open and C51 is normally closed. For this rung to be executed, the K109 C50 bit must be on and the C51 bit must be off, corresponding to the second row of the truth table.
Page 66: Shift Register
Chapter 4: RLL Programming for Communications Shift Register The Shift Register can be used for creating interlocks, as an alternative to using control relays. For a complete explanation of the function of the Shift Register, see the User Manual for your PLC.
Page 67: First Rx/Wx Instruction
Chapter 4: RLL Programming for Communications First RX/WX Instruction SP122 C60 is the interlocking contact. It is K114 turned on by the Store If Equal rung preceding this one. O40600 VC100 Second RX/WX Instruction SP122 C61 is the interlocking contact. It is turned on by the sequencing steps of K109 the Shift Register in a preceding rung.
Page 68: Modbus Tcp
hapter MODBUS TCP hapter hapter H0/H2/H4-ECOM100 In This Chapter... Modbus TCP ......................5-2 Supported Modbus Function Codes ................. 5-4 Network Server (Slave) Operation ................5-5 Network Client (Master) Operation ............... 5-15 H0/H2/H4 -ECOM100 System Memory ..............5-22...
Page 69: Client / Server Model
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Modbus TCP Modbus TCP is essentially the serial Modbus RTU protocol encapsulated in a TCP/IP wrapper. Modbus RTU is used for serial communications between a master and slave(s) devices. Modbus TCP is used for TCP/IP communications between client and server devices on an Ethernet network.
Page 70 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 This header provides some differences compared to the Modbus RTU application data unit used on serial line: • The Modbus “slave address” field usually used on Modbus Serial Line is replaced by a single byte “Unit Identifier” within the MBAP Header. The “Unit Identifier” is used to communicate via devices such as bridges, routers and gateways that use a single IP address to support multiple independent Modbus end units.
Page 71: Supported Modbu Function Codes
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 NOTE: ModScan32 is a Windows based application program that can be used as a Modbus master to access and change data points in a connected device (H0/H2/H4- ECOM100) The utility is ideally suited for quick and easy testing of Modbus TCP network slave devices.
Page 72: Network Server (Slave) Operation
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Network Server (Slave) Operation This section describes how other Modbus TCP clients on a network can communicate with an H0/H2/H4 -ECOM100 that you have configured for Modbus TCP protocol. A network client must send a Modbus function code and Modbus address to specify a PLC memory location the DL05/06/205/405 CPU.
Page 73: If Your Host Software Or Client Requires The Data Type And Address
Modbus starting address (as required). The following tables show the exact range used for each group of data. NOTE: For an automated Modbus/Koyo address conversion utility, download the file Modbus_conversion.xls from the www.automationdirect.com technical support website. PLC Range Modbus Modbus DL05 Memory Type (Dec.)
Page 74 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 PLC Range Modbus Modbus DL06 Memory Type (Dec.) (Octal) Address Range Data Type + Data Type For Discrete Data Types... Convert PLC Addr. to Dec. + Start of Range Inputs (X) X0 – X777 2048 –...
Page 75 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 PLC Range Modbus Modbus D2-250-1 Memory Type (Dec.) (Octal) Address Range Data Type + Data Type For Discrete Data Types... Convert PLC Addr. to Dec. + Start of Range Inputs (X) X0 – X777 2048 –...
Page 76 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Modbus D4-430 PLC Range Modbus Address Range Memory Type (Dec.) (Octal) Data Type (Decimal) For Discrete Data Types... Convert PLC Addr. to Dec. + Start of Range + Data Type Inputs (X) X0 – X477 2048 –...
Page 77 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 D4-450/D4-454 PLC Range Modbus Modbus Memory Type (Dec.) (Octal) Address Range Data Type + Data Type For Discrete Data Types... Convert PLC Addr. to Dec. + Start of Range Inputs (X) 1024 X0 – X777 2048 –...
Page 78: Example 1: V2100
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 The following examples show how to generate the Modbus address and data type for hosts which require this format. Example 1: V2100 PLC Addr. (Dec.) + Data Type Find the Modbus address for User V location V2100. V2100 = 1088 decimal 1.
Page 79: Example 4: C54
Modbus starting address (as required). The following tables show the exact range used for each group of data. NOTE: For an automated Modbus/Koyo address conversion utility, download the file Modbus_conversion.xls from the www.automationdirect.com website. Discrete Data Types* PLC Range Modbus...
Page 80 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Word Data Types* Registers (Word) PLC Range Modbus 40001 Modbus 30001 Access (V-Memory) (Dec.) (Octal) Address Range Address Range Timers V0 – V377 40001 – 40256 30001 – 30256 Counters V1000 – V1377 40513 – 40768 30513 –...
Page 81: Example 1: V2100
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 The following examples show how to generate the Modbus address and data type for hosts which require this format. Example 1: V2100 Find the Modbus address for User V location V2100. PLC Addr. (Dec.) + Mode Address V2100 = 1088 decimal 1.
Page 82: Network Client (Master) Operation
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Network Client (Master) Operation This section describes how the DL05/06/205/405 CPU can serve as a client on a Modbus TCP network using the H0/H2/H4 -ECOM100. This section discusses how to design the required ladder logic for network client operation. Client MODBUS TCP Servers Slave #1...
Page 83 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Modbus Function Codes Supported The H0/H2/H4 -ECOM100 supports the following Modbus function codes when acting as a Modbus TCP client. Modbus DL05/06/205/405 Function Function Code Data Types Available Read Output Table Y, C, T, CT Read Input Table X, SP Read holding registers (when addressing mode...
Page 84: Plc Memory Supported For Client Operation
PLC address in the appropriate PLC range. See the conversion examples on the following page. The following tables show the exact range used for each group of data. NOTE: For an automated Modbus/Koyo address conversion utility, download the file Modbus_conversion.xls from the www.automationdirect.com website. Discrete Data Types* PLC Range...
Page 85: Example 1: Calculating Word Plc Address
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 NOTE: Your PC’s Windows calculator can be used for number conversions (i.e. decimal to octal). The Windows calculator must be in Calculator>View>Scientific mode to enable number conversions capability. Example 1: Calculating Word PLC Address Find the PLC address to use to target Modbus address 41025 in a server device.
Page 86: Building The Read (Rx) Or Write (Wx) Routine
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Building the Read (RX) or Write (WX) Routine For network communications, you build the Read (RX) or Write (WX) instructions into a routine which requires the A aaa four instructions you see to the right. They must be used in the sequence shown.
Page 87: Step 2: Load Number Of Bytes To Transfer
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Step 2: Load Number of Bytes to Transfer (BCD) The second Load (LD) instruction determines the number of bytes which will be transferred between the master and slave in the subsequent WX or RX # of bytes to transfer instruction.
Page 88: Communications From A Ladder Program
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Communications from a Ladder Program SP123 Typically network communications will last longer than 1 scan. The program must wait for the communications SP122 to finish before starting the next transaction. K114 ECOM Communication Error ECOM Port Busy ECOM Port Busy Depending on which slot the ECOM is in, it has two...
Page 89: Ecom100 Ibox
There is a Modbus spreadsheet located on our Tech Support site that can be used to convert the Modbus addresses in the slaves to octal addressing that is required in the ECRX and ECWX boxes. Follow this link: http://support.automationdirect.com/docs/modbus_conversion.xls, or use this application note AN-MISC-010, which is located https://support.automationdirect. RX/WX Ok Count com/technotes.html and select AN-MISC-010 to download the spreadsheet.
Page 90 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 For the final steps, you must setup the ECOM100 IP settings and “Peer-Peer” table with NetEdit3. In the graphic above, double-click the ECOM100 desired. This will pull up the following General Settings box. Here, you can assign the IP address and subnet mask for his network. The Modbus slaves will need to have compatible settings of course.
Page 91: Modbus Tcp Setup
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Modbus TCP Setup To begin the Modbus TCP setup, highlight the desired ECOM100 module, and select the “ECOM Settings” tab in lower frame of NetEdit3 window, then click the button marked “Peer to Peer Config”. You will get the popup screen seen below: To add an entry, click the “Add”...
Page 92 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Make sure to check the box for “ModbusTCP” and make “Device #” equal to the “Slave ID” that was used in the ECxX box(s), and enter the IP address of the Modbus slave. Leave the UnitID at 255 and port at 502 unless your slave documentation instructs otherwise.
Page 93: Example Modbus Tcp Program
ModbusTCP tester at the link below. You might need to use one of these programs to test to your device, to make sure they can work successfully to the expected addressing. http://ftp.automationdirect.com/pub/Modbus_TCP_Master.zip To read Modbus Input Registers, you must change the number of bytes in any instruction to the next odd number.
Page 94 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 Network #1 uses the Hx-ECOM100 in Slot 1. This would be the only slot in 05, first slot in 06, and second slot in 205/405 models. It will use the range of V-memory from V400 - V502 as the working status, workspace and buffer.
Page 95 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 The ECRX will read from Slave ID "1", and will target address TA0 (V0) which is the Modbus equvalent address 40001 ( first Holding Register). It will get 4 bytes ( 2 registers) and place the data in V2000-2001. This data will likely be in decimal format if coming from 3rd party devices.
Page 96 Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 The next 2 rungs will count the Success and Errors of the IBOX's. V505 and V506 will contain the total count of each, respectively. SP1_ECRX_7_Ok INCB C100 RX/WX Ok Count V505 SP1_ECWX_7_Ok C102 Count failed ECRX and ECWX transactions. SP1_ECRX_7_Fail C101 RX/WX Fail Count...
Page 97: H0/H2/H4 -Ecom100 System Memory
Chapter 5: MODBUS TCP for H0/H2/H4-ECOM100 H0/H2/H4 -ECOM100 System Memory H0/H2/H4 - ECOM100 Modbus Address Range Words Word Descriptions Access (Decimal) (16-bit) 1 - OS Major Version 2 - OS Minor Version 317501 – 317506 3 - OS Build Version Read Only (417501 –...
Page 98 hapter hapter H0/H2/H4-ECOM100 hapter DHCP & HTML OnfiguraTiOn In This Chapter... H0/H2/H4 -ECOM100 DHCP ..................6-2 Using HTML Configuration ..................6-3...
Page 99: Chapter 6: H0/H2/H4-Ecom100 Dhcp & Html Configuration
Chapter 6: H0/H2/H4-ECOM100 DHCP & HTML Configuration H0/H2/H4 -ECOM100 DHCP DHCP Issues The H0/H2/H4- ECOM100 is configured at the factory to look for a DHCP (Dynamic Host Configuration Protocol) server at power up. DHCP provides a way to allocate IP address dynamically to devices on a local area network (LAN).
Page 100: Using Html Configuration
Chapter 6: H0/H2/H4-ECOM100 DHCP & HTML Configuration Using HTML Configuration The H0/H2/H4 -ECOM100 can be configured by using your PC’s internet browser to access the module’s HTML configuration page. This method of configuration uses the TCP protocol, so you must know the H0/H2/H4 -ECOM100’s IP address to establish communications. The IP address may have been assigned by a DHCP server (default) or may have been set by using NetEdit3.5 or later.
Page 101 Chapter 6: H0/H2/H4-ECOM100 DHCP & HTML Configuration Ethernet Address: this is the MAC Address. It is a factory-assigned address that is on the permanent label on the module. IP Configuration: Set IP Address, Subnet Mask and Gateway addresses. Click the Send button to write to the module flash memory.
Page 102: H0/H2/H4-Ecom100 Client Peer To Peer Configuration
Chapter 6: H0/H2/H4-ECOM100 DHCP & HTML Configuration H0/H2/H4-ECOM100 Client Peer to Peer Configuration Peer to Peer: The following are reasons or conditions of when to configure the H0/H2/H4- ECOM100 for peer to peer communications with a TCP/IP server device: • To eliminate network broadcast traffic when the ECOM100 is a client executing RX/WX network instructions.
Page 103 Chapter 6: H0/H2/H4-ECOM100 DHCP & HTML Configuration The Port Number and Unit ID are only used if the H0/H2/H4 -ECOM100 client is trying to communicate with a Modbus TCP server device through a firewall or an Ethernet- to- serial converter. Port Number: The Modbus TCP specification states that all Modbus TCP devices respond to (server) and send (client) on port 502.
Page 104 hapter hapter hapter aintenance and roubleshooting In This Chapter... Isolating a Communication Problem ................ 7-2 Troubleshooting Chart ....................7-2 ECOM Module Diagnostic LEDs ................7-4 Network Server (Slave) Operation ................7-5 Using NetEdit3 for Troubleshooting ................. 7-7 Replacing the ECOM Module .................. 7-10 Diagnosing Network Cable Problems ..............
Page 105: Chapter 7: Maintenance And Troubleshooting
Chapter 7: Maintenance and Troubleshooting Isolating a Communication Problem If you are experiencing a problem communicating with an ECOM module, the problem can usually be isolated to one of four components of the communication link: • ECOM module itself (hardware or firmware) •...
Page 106 Chapter 7: Maintenance and Troubleshooting Troubleshooting Chart (Continued) Legend: Flash ECOM Module LEDs Corrective Action ECOM100 ECOM(- -F) 1. Try another cable that you know works. Check pinouts (see page 2-12). OK / STATUS LINK/LINKGD LINKGD/LINK 2. Try another port on the hub or ACTIVE/ACT ERROR/ERR another hub.
Page 107: Ecom Module Diagnostic Leds
Chapter 7: Maintenance and Troubleshooting ECOM Module Diagnostic LEDs H0 Series Indicators The H0 series ECOM module has four status indicators. The table below explains the status for each indicator. Indicator Status Description ON - Green Module is powered up and functional OK (H0-ECOM only) Module power-up failed ON - Green...
Page 108: Network Server (Slave) Operation
Chapter 7: Maintenance and Troubleshooting Network Server (Slave) Operation H24-ECOM-(F) Indicators The table below describes the three status indicators on the H24- ECOM modules. Indicator Status Description ON - Green Properly connected to network LINKGD Not connected to network or incorrect configuration Flashes Red Active network data Network idle...
Page 109: H2/H4-Ecom100 Indicators
Chapter 7: Maintenance and Troubleshooting H2/H4-ECOM100 Indicators The H2/H4 -ECOM100 module has several status indicators. The table below explains the status for each indicator. Indicator Status Description ON - Green Module is powered up and functional STATUS (H2-ECOM only) Module power-up failed ON - Green Properly connected to network LINKGD...
Page 110: Using Netedit3 For Troubleshooting
Chapter 7: Maintenance and Troubleshooting Using NetEdit3 for Troubleshooting NetEdit3 is the software utility used to configure and troubleshoot Host Ethernet based devices. To review the procedures for running and using NetEdit3, see pages 3-5 through 3-12. NetEdit3 allows you to: •...
Page 111: Change Protocol
Chapter 7: Maintenance and Troubleshooting Change Protocol If you are experiencing a problem communicating from your PC to a module that does not appear on the list of active modules, try changing the protocol and clicking on Scan Network. You may be able to link to your module with the other protocol.
Page 112: Rx/Wx Settings
Chapter 7: Maintenance and Troubleshooting RX/WX Settings The RX/WX Settings box in this window provides a place to make changes that affect PLC-to-PLC communications only. Change these settings only if: • The LINK/LINKGD LED is on. • The ACT LED is flashing. •...
Page 113: Replacing The Ecom Module
Chapter 7: Maintenance and Troubleshooting Replacing the ECOM Module If you are experiencing a communication problem, and you think the ECOM may be defective, try replacing the ECOM module with a new one or one that you know is working properly. If that corrects the problem, then the original module is probably defective (assuming the replacement module was set up the same as the original and no changes have been made to the communication program or other network components).
Page 114: Diagnosing Network Cable Problems
Chapter 7: Maintenance and Troubleshooting Diagnosing Network Cable Problems If you are experiencing communication problems, swapping cables is one of the simplest diagnostic procedures you can perform. If the network operates correctly with a different cable, you have isolated and cured the problem. If possible, use a short run of cable to test the network because problems with longer cable runs can be more difficult to diagnose and are more often intermittent.
Page 115 ppendix ppendix ppendix eneral pecificationS In This Chapter... General Specifications ....................A-2 Ethernet Standards ....................A-4...
Page 116: Appendix A: General Specifications
Appendix A: General Specifications General Specifications ECOM Specifications H0-ECOM Module Type Intelligent Data Communications Module Quantity of Modules Per Base Defined by CPU and base configuration Diagnostics LEDs/Network Monitoring Software (NetEdit3) Communications 10BaseT Ethernet Data Transfer 10 Million bits per second Extension Port RJ45 OK Indicator (OK)
Page 117 Appendix A: General Specifications H0-ECOM100 Module Type Intelligent Data Communications Module Quantity of Modules Per Base Defined by CPU and base configuration Diagnostics LEDs/Network Monitoring Software (NetEdit3) Communications 10/100BaseT Ethernet Data Transfer 100 Million bits per second Extension Port RJ45 Link Good Indicator (LINK) Green LED Activity Indicator (ACT)
Page 118: Ethernet Standards
Appendix A: General Specifications H2-ECOM-F/H4-ECOM-F Module Type Intelligent Data Communications Module Quantity of Modules Per Base Defined by CPU and base configuration Diagnostics LEDs/Network Monitoring Software (NetEdit3) Communications 10BaseFL Ethernet (fiber optic) Data Transfer 10 Million bits per second Extension Port ST-Style fiber optic connector Link Good Indicator (LINKGD) Green LED...
Page 119 ppendix ppendix ppendix eerlink unction For 100 m odule In This Appendix... Peerlink Function for ECOM100 ................B-2 Peerlink Data-Sharing Network ................B-3...
Page 120: Peerlink Function For Ecom100
Appendix B: General Specifications Peerlink Function for ECOM100 Q. Q How is the Peerlink function used on the ECOM100? Q. A As of the following versions of ECOM100 firmware, a peerlink function was added. • H0-ECOM100 v4.0.334 • H2-ECOM100 v4.0.1808 •...
Page 121: Peerlink Data-Sharing Network
Appendix B: General Specifications The peerlink data-sharing network is limited to 16 publishing nodes but an unlimited amount of subscribing nodes. A data-sharing network could look like the graphic below. Peerlink Data-Sharing Network Ethernet Communications Modules, 3rd Edition, Rev. D...
Page 122: Configuration
Appendix B: General Specifications Configuration There are two ways to configure/edit the peerlink function in an ECOM100 (Do-more CPU utilizing the built-in Ethernet port do not require any configuration): • Start NetEdit3: 1. Right-click on your ECOM100 2. Select “Advanced...” 3.
Page 123: Parameters
Appendix B: General Specifications Parameters: • V Memory Address (octal): Enter the starting V-memory address of the first block. All 16 blocks of 16 words each will be allocated. In the above example notice V3000- 3377 are now utilized. • Peerlink Enabled: For the Peerlink function to work this box must be checked. If it is unchecked, no data exchange with the other nodes on the data-sharing network will occur.
Page 124: Dl05
Appendix B: General Specifications DL05 This configuration causes the H0-ECOM100 to: • Take whatever data is in the DL05's V2000-2017 and write (publish) it as Block Number 0. • Read (subscribe) to whatever data gets written to Block Number 1 and store it in the DL05's V2020-2037.
Page 125: Dl06
Appendix B: General Specifications DL06 This configuration causes the H0-ECOM100 to: • Take whatever data is in the DL06's V2020-2037 and write (publish) it as Block Number 1. • Take whatever data is in the DL06's V2040-2057 and write (publish) it as Block Number 2.
Page 126: Dl205
Appendix B: General Specifications DL205 This configuration causes the H2-ECOM100 to: • Take whatever data is in the DL205's V3060-3077 and write (publish) it as Block Number 3. • Take whatever data is in the DL205's V3100-3117 and write (publish) it as Block Number 4.
Page 127: Dl405
Appendix B: General Specifications DL405 This configuration causes the H4-ECOM100 to: • Take whatever data is in the DL405's V1140-1157 and write (publish) it as Block Number 6. • Take whatever data is in the DL405's V1160-1177 and write (publish) it as Block Number 7.
Page 128: Do-More
Appendix B: General Specifications Do-more This configuration causes the Do-more on-board Ethernet port to: • Take whatever data is in the Do-more's PL160-175 and write (publish) it as Block Number 10. • Read (subscribe) to all block data. The Do-more has specially allocated memory (PL = Peerlink memory) and cannot be configured to ignore any blocks as is indicated in the text of the PEERLINK instruction itself.
Page 129: Block Summary
Appendix B: General Specifications Block Summary Thus from a block data-sharing point of view, each block will contain data as shown in the following list. Any number of ECOM100s (or Do-more's) on the network can listen (subscribe) to any of this data. The important thing to remember is that only one PLC can write (publish) a particular block;...

This manual is also suitable for:

H2-ecom H0-ecom100 H0-ecom H2-ecom-f H4-ecom100 H2-ecom10 ... Show all

Automationdirect.com HX-ECOM Series Manual

Chapter 1 - Introduction

Introduction

Conventions Used

Frequently Asked Questions

Chapter 2: Setup and Installation

ECOM Network Identifiers

Setting the Module ID with the DIP Switch

Inserting the ECOM Module in the PLC Base

ECOM Network Layouts

Network Cabling

Maximum Cable Length

Maximum Number of ECOM Modules on the Network

Chapter 3: Configuring Ecoms Using Netedit3

Netedit3 Software

Chapter 4: RLL Programming for Communications

PLC-To-PLC Communications

How RLL Is Used for Communications

Network Instructions

Addressing the Different Memory

Special Relays for Communications

Program with One Read Instruction

Example Program with One Write Instruction

Integrating Multiple Read and Write Instructions

Chapter 5 - Modbus TCP for H0/H2/H4-ECOM100

Modbus TCP

Supported Modbu Function Codes

Network Server (Slave) Operation

Network Client (Master) Operation

H0/H2/H4 -ECOM100 System Memory

Chapter 6: H0/H2/H4-ECOM100 DHCP & HTML Configuration

H0/H2/H4 -Ecom100 Dhcp

Using HTML Configuration

Chapter 7: Maintenance and Troubleshooting

Isolating a Communication Problem

Troubleshooting Chart

ECOM Module Diagnostic Leds

Network Server (Slave) Operation

Using Netedit3 for Troubleshooting

Replacing the ECOM Module

Diagnosing Network Cable Problems

Appendix A: General Specifications

General Specifications

Ethernet Standards

Appendix B - Peerlink Specifications

Peerlink Function for ECOM100

Peerlink Data-Sharing Network

Quick Links

Troubleshooting

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Automationdirect.com HX-ECOM Series

Summary of Contents for Automationdirect.com HX-ECOM Series

This manual is also suitable for:

Table of Contents