do-more designer - john schember_a1

Topic: DMD0187

Help File Version: 1.4.3.3

Getting Started

Welcome to the Help system for the Do-more Designer software for the line of Do-more PLCs. The Help file is organized into the following categories: Introduction contains Help topics dealing with warnings, warranty information, agency approvals, and product updates. System Configuration contains Help topics that deal with the System Configuration, and explains the PLC memory system and the data types that are available to work with. Do-more Designer Software - contains Help topics dealing with the programming environment, specifically the Launchpad, the Project Browser, the tabbed Ladder Views and the Tools provided to assist the programming effort. It also discusses the debugging utilities and troubleshooting tools. Programs and Tasks - contains Help topics that discuss the proper usage of the Program and Task code blocks. Instruction Set - contains Help topics for each of the Instructions and are available for use in ladder logic programs. PID Loops - contains Help topics with details on the proper usage of PID loops and the associated process control instructions. Also has topics for the utility programs for tuning the PID Loops and for runtime monitoring of PID loops. Stage Programming - contains Help topics that discuss the various aspects of using the Stage programming instructions to build sequential operations in ladder logic programs. Hardware - contains Help topics dealing with the Do-more controller's LEDs, DIP Switch Settings, Mode Switch Settings and on-board communication ports. Simulator (Virtual PLC) - contains discussion of how to use the built-in Do-more Simulator as a Virtual PLC. Communication Capabilities - contains Help topics for each of the external communications options available with Do-more CPUs. Reference - setting up User Accounts (with Passwords), managing the System Date and Time, both externally and at runtime, the types of Data that are available for use in Do-more projects, how to move a DirectSOFT project (for a DirectLOGIC PLC) to a Do-more project, handling software and firmware updates, and setting up Ethernet resources for communicating to externaldevices. Troubleshooting - contains help topics for the tools within Do-more Designer to help debug projects and handle error conditions at both development time and at runtime. Hardware Manuals - contains links to the online versions of the Hardware User Manuals for the Do-more Systems. Glossary - contains definitions of terms that are frequently used in the Do-more Designer programming software.

Topic: DMD0328


Warnings and Disclosures

WARNING

Thank you for purchasing automation equipment from AutomationDirect.com, doing business as AutomationDirect. We want your new automation equipment to operate safely. Anyone who installs or uses this equipment should read this publication (and any other relevant publications) before installing or operating the equipment. To minimize the risk of potential safety problems, you should follow all applicable local and national codes that regulate the installation and operation of your equipment. These codes vary from area to area and usually change with time. It is your responsibility to determine what codes should be followed, and to verify that the equipment, installation, and operation is in compliance withthe latest revision of these codes. At a minimum, you should follow all applicable sections of the National Fire Code, National Electrical Code, and the codes of the National Electrical Manufacturer's Association (NEMA). There may be local regulatory or government offices that can also help determine what codes and standards are necessary for safe installation and operation. Equipment damage or serious injury to personnel can result from the failure to follow all applicable codes and standards. We do not guarantee the products described in this publication are suitable for your particular application, nor do we assume any responsibility for your product design, installation, or operation. Our products are not fault-tolerant and are not designed, manufactured or intended for use or resale as on-line control equipment in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems, in which the failure of the product couldlead directly to death, personal injury, or severe physical or environmental damage ("High Risk Activities"). AutomationDirect specifically disclaims any expressed or implied warranty of fitness for High Risk Activities. For additional warranty and safety information, see the Terms and Conditions section of our catalog. If you have any questions concerning the installation or operation of this equipment, or if you need additional information, please call us at 770-844-4200. This publication is based on information that was available at the time it was printed. At AutomationDirect we constantly strive to improve our products and services, so we reserve the right to make changes to the products and/or publications at any time without notice and without any obligation. This publication may also discuss features that may not be available in certain revisionsof the product.

Topic: DMD0329


End User License Agreement and Warranty

License Agreement

Do-more Designer

IMPORTANT

BEFORE OPENING THIS PACKAGE AND USING THIS SOFTWARE YOU SHOULD CAREFULLY READ THIS AGREEMENT The enclosed Do-more Designer computer software program (the "Software") is the property of Automationdirect.com, inc. or its suppliers. Before installing this package, carefully read this Agreement. If you do not accept the terms and conditions of this Agreement, you should return the enclosed Software and any accompanying items (including any manuals, release notes,binders, etc.), unopened, to Automationdirect.com for a full refund. 1. LICENSE. Subject to the terms and conditions of this Agreement, when you install this software, Automationdirect.com grants you and you accept a non-exclusive license to use the following Software which you obtain from Automationdirect.com. The particular Software you have acquired and the type of license is specified in your purchase order as part of the part number forthe item. The following applies to each type of Software product and license:

Do-more Designer "Single User" License If you have acquired a Single User license for the Do-more Designer Software you may use one copy of the Do-more Designer product on any single computer, provided the Software is in use on only one computer at any time. The Do-more Designer Software is deemed "in use" on a computer when it is loaded into the temporary memory (i.e., RAM) or installed into the permanentmemory (i.e., hard disk, CD-ROM or other storage device) of that computer, except that a copy may be installed on a network server for the sole purpose of distribution to other computers for which you have obtained a license for the product and that are not currently &rdquor;in use. You must have a reasonable mechanism or process in place to ensure that the number of computersusing the Do-more Designer Software concurrently does not exceed the number of licenses, and obtain any required additional licenses from Automationdirect.com. However, if the Do-more Designer Software is permanently installed on the hard disk or other storage device of a computer (other than a network server) and one person uses that computer more than 80% of the time itis in use, then that person may also use the Do-more Designer Software on a single portable computer or a single computer at home. 2. COPYRIGHT. The Software is owned by Automationdirect.com or its suppliers and is protected by United States copyright laws and international treaty provisions. You shall not remove or alter, or permit any person to remove or alter, any of the copyright or other notices of Automationdirect.com or its suppliers on, stated in or affixed to the Software or any of the documentation,or on any CDs, covers or other packaging containing Software or the documentation. 3. RESTRICTIONS. You acknowledge that the Software and the related documentation delivered to you are and shall remain the property of Automationdirect.com or its suppliers and that no right is granted to you to (i) copy, print, transfer, transmit or display all or any part of the Software or the documentation except as specifically provided herein, (ii) modify the Software or merge orutilize all or any part of the Software with or into other computer programs, or (iii) compile, reverse compile or disassemble all or any part of the Software. You may, however, either make one copy of each of the Software products acquired by you in machine readable form for backup or archival purposes. 4. LIMITED WARRANTY.Automationdirect.com warrants that the Software will perform substantially in accordance with the written materials accompanying the Software for a period of ninety (90) days from the date of receipt. EXCEPT AS PROVIDED ABOVE, AUTOMATIONDIRECT.COM OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES OF ANY KIND,NATURE OR DESCRIPTION, EXPRESS OR IMPLIED, WITH RESPECT TO THE SOFTWARE OR ANY RELATED WRITTEN MATERIALS, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE, AND AUTOMATIONDIRECT.COM OR ITS SUPPLIERS HEREBY DISCLAIM THE SAME. This LimitedWarranty is void if failure of the Software results from accident, abuse, or misapplication or failure to use the Software in accordance with its documentation. 5. CUSTOMER REMEDIES.Automationdirect.com's entire liability and your exclusive remedy shall be, at Automationdirect.com's option, either refund of the price paid for the defective Software, or repair or replacement of the defective Software, in each case upon return to Automationdirect.com during the warranty period. You must return the defective Software product toAutomationdirect.com with a copy of your purchase receipt. Any replacement Software will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer. 6. LIMITATION ON LIABILITY. In no event shall Automationdirect.com or its suppliers be liable, whether in contract or in tort, or under any other legal theory (including, without limitation, negligence), for any indirect, special, consequential or incidental damages arising out of or in connection with the Software or any documentation, including, without limitation, lost profits orrevenues, loss of data or business information, costs for recreating lost data, business interruption, costs for replacement programs, or any similar damages, or for any claim made against you by any other party, even if Automationdirect.com has been advised of the possibility of such claim. In no event will the liability of Automationdirect.com or its suppliers for any Softwareexceed the price paid by you for the defective Software product. 7. NO TRANSFER. You may not rent or lease the Software, but you may transfer your rights under each copy of the Software products on a permanent basis with the prior written consent of Automationdirect.com, provided that you transfer this Agreement, the Software, and all accompanying written materials and retain no copies on any computer or other form of media. Any transferof the Software must include the most recent update and all prior released versions. Any transfer requires that you provide written notification to Automationdirect.com prior to the transfer, the prior written consent of Automationdirect.com, and the recipients agreement in writing to abide by the terms contained in this Agreement. Automationdirect.com reserves the right to rejectthe transfer if it is not in the best interest of Automationdirect.com, its customers or authorized resellers. 8. TERM AND TERMINATION. This Agreement and the licenses granted in this Agreement are effective until terminated. You may terminate this Agreement at any time by notifying Automationdirect.com, returning the Software and related documentation, and destroying all copies. This Agreement will also terminate upon your failure to comply with any of its terms, in which event youmust return the Software and the written materials to Automationdirect.com and destroy all copies. 9. U.S. GOVERNMENT RESTRICTED RIGHTS. The Software and accompanying documentation are "commercial computer software" and "commercial computer software documentation," respectively, with United States Government rights governed by DFAR Section 227.7202 and FAR Section 12.212, as applicable. Any use, modification, reproduction, release, performance, display ordisclosure of the Software and accompanying documentation by the United States Government shall be governed solely by the terms of this Agreement and shall be prohibited except to the extent expressly permitted by the terms of this Agreement. 10. MISCELLANEOUS. No failure or delay to exercise any right or remedy under this Agreement shall operate as a waiver, and a single or partial exercise of any right or remedy will not preclude the further exercise of such right or remedy or any other right or remedy. This Agreement supercedes any other oral or written agreement between you and Automationdirect.com or itssuppliers. This Agreement shall be construed and enforced in accordance with the laws of the State of Georgia, without regard to its rules regarding conflicts of law. ATLLIB01 1300696.2

Topic: DMD0330


Software Return Policy

The original licensee of the Do-more Designer Software can Return the software within thirty (30) days of purchase. The Do-more Designer Software requires a Return Authorization. Please call our Returns Department at (800) 633-0405 and follow the prompts. You may also use our online Pre-Authorization Form at:

http://www.automationdirect.com/adc/Return/Return(Please be aware that the web address shown is Case Sensitive!)

Topic: DMD0331


European Union (EU) Information

The Do-more PLCs have been tested under the CE Test Standard #EEN611312:2007, and is listed under UL File #NRAQ:E185989 and UL for Hazardous Locations Class 1 Div 2 Groups A,B,C,D NWGD:E200031. The Do-more PLCs are manufactured in compliance with European Union (EU) Directives and carry the CE mark. United States, Canada and the European Union require certain standards that MUST be followed, tested and approved, before any electronic piece of equipment can be offered and sold in the respective countries. AutomationDirect products follow these guidelines and are submitted through the testing and approval process in order to provide equipment that satisfies theserequirements. Information regarding Agency Listings, Certifications and more can be found on the AutomationDirect.com web site. For quick access to this information, please select from one of the links listed below. An internet connection is required to access these links. Products with Certification marks perform their required functions safely and adhere to relevant standards as specified by Agency Compliance Requirements, Certifications and EU Directives, provided they are used according to their intended purpose and that the instructions in the manual are adhered to. The protection provided by the equipment may be impaired if thisequipment is not used in accordance with the Do-more PLC User Manual. Only replacement parts supplied by AutomationDirect.com or its agents should be used. Consult the Do-more Designer Software Help File or you may find answers to your questions in the Programmable Logic Controller section of our web site at http://support.automationdirect.com. If you still need assistance, please call our Technical Support team at 770-844-4200 or fax us at 770-886-3199.

Topic: DMD0332


Copyright

Copyright 2014, Host Engineering Incorporated All Rights Reserved

No part of this help file or hard copy of the manual shall be copied, reproduced, or transmitted in any way without the prior, written consent by Host Engineering and AutomationDirect.com Incorporated. Host Engineering and AutomationDirect.com retain the exclusive rights to all information included in this help file.

Topic: DMD0333


Trademarks

This publication may contain references to products produced and/or offered by other companies. The product and company names may be Trademarks () or Registered Trademarks ( ) and are the sole property of their respective owners. AutomationDirect.com disclaims any proprietary interest in the marks and names of others. Microsoft and its products are registered trademarks. Windows is a registered Trademark of Microsoft Corporation.

Topic: DMD0359


The Help System

The left side of the Help System contains the following:

Table of Contents - double click a folder to expand that folder, the single click on a page to display that page in the section on the right. Index - shows a listing of keywords used in the Help system. Double click an item in the list and a dialog showing which topics contain that keyword will be displayed. select a topic in the dialog and click OK to have that topic displayed in the section to the right. Search - enter the word to search for in the space provided the click List Topics button. The names of all the Topics that contains the search word will displayed below. Select the desired topics from the list then either double click the topic or click the Display button to have that topic displayed in the section to the right.

The right side of the Help System contains the following:

Navigation Toolbar has the following buttons:

Expand All - if the Topic contains any expanding text, click this button to expand all of them. Collapse All - if the Topic contains any expanding text, click this button to collapse all of them. Quick Search- enter a word or phrase to search for in the currently displayed topic (not case sensitive) the click the Quick Search button to highlight the found words. Remove Search Highlights - click this to clear the highlighted words from previous Quick Searches. Back - as you move through the Help system topics, the Help system keeps track of the topics you've displayed. Back will to go back one topic in the browse history. Forward - to go forward one topic in the browse history. Stop - stop the loading of a topic. Refresh - reload the currently displayed topic. Home - display the Help System startup topic. Previous Topic - moves back one topic as listed in the Table of Contents. Next Topic - moves forward one topic as listed in the Table of Contents.

Topic ID - a number that uniquely identifies the currently displayed help topic. This number can be searched for, and used to report errors in the content of the topic. Feedback - a hyper-linked icon that will display the help topic that contains information on how to send comments on the help system and the help topics. Help File Version - the build version of the help file that is currently being displayed. The remainder of the right side is used to display the text for the currently selected Help Topic.

Topic: DMD0335


Help File Updates

This Help File for Do-more Designer is updated regularly with the intention of providing the most complete and up-to-date information available on the use of the Do-more Designer Software. Updated Help File versions are posted on our web site and the Automatic Update process will alert you when a new version of the Help file is available. To see the Version of the existing Help File, open any topic in the Help system and refer to the picture shown below which shows the location of the Version number of the existing Help File.

If the computer running Do-more Designer is connected to the internet, it will automatically check for an updated Help file each time the software is started. The check can also be run manually at any time through the Check for Updates menu selection. If a newer version is available, it can be downloaded to replace the older version.

Topic: DMD0334


Feedback

Help File Feedback and Comments

THIS FEEDBACK IS ONLY FOR THE DO-MORE DESIGNER HELP FILE!!!

As a continued effort to provide the best products to our Customers, we provide this Feedback Page where you, the User, can easily communicate to us any issues, suggestions, and comments (good or bad) about this Help File. Your input is very important to us! Please take a minute to Email us the information below. Thank you for helping us provide top quality products, and fortrusting us for your automation needs and services. To: [email protected] Subject: Use one of the following selections on the Subject line of the Email:

CorrectionAdd Content RequestReport an IssueSuggest FAQComment About Help File

The body of the Email should have the following information:

Your Full Name Your Company Respond via Email to (we will ONLY use this Email address if you request a reply) The Help Topic Version (located in the upper right corner) The Help Topic ID (if applicable, also located in the upper right corner, DMDxxxx) Your Comments for changes to the Do-more Designer Help file

Topic: DMD0253


System Configuration Overview

The System Configuration defines the available hardware and software resources that are available for Do-more Designer and the controller to work with. The System Configuration is integral to a Do-more Designer project and the controller where the project will be downloaded. It is imperative that the System Configuration in the project remain in sync with the one in the controller. Changes to the System Configuration can have drastic effects on the capabilities of the controller, so any changes to the System Configuration can only be safely written to the controller while it is in PROGRAM mode. The following is a list of the utilities provided by Do-more Designer to manage the individual sections of the System configuration. CPU Configuration - is used to set the modes supported by the onboard ports of a controller, to manage the Modbus/TCP Server setup, to configure the optional TimeSync feature, set the default watchdog time value, enable the Ethernet I/O Master function, and enable the ability to establish a programming session on an additional TCP/IP port number. I/O Configuration - provides a graphical view of the I/O modules in the base with the controller. It provides a facility to manually configure the I/O of a system which can also be used for offline programming. And also configures the Ethernet I/O Master network of Slave devices. Module Configuration - Intelligent modules that are programmable by ladder logic instructions require a Module Configuration. Also, some of the analog I/O modules that use software configuration options instead of on-board jumpers use a Module Configuration to store the configuration selections. A default Module Configuration is automatically created by the Do-more controller, thisdefault setup can be modified through a module-specific editor in the Module Configuration. Device Configuration - Devices are preconfigured interfaces that provide programmatic access to system resources. Most instructions operate on image register memory, although certain high-level instructions use devices. Any additional user configuration of the devices, for example baud rates for serial ports, is provided for in this dialog. Some devices are automatically created, andalthough they are listed here, they cannot be deleted or edited. I/O Mappings - The default setting for Do-more system is to automatically assign the I/O addresses.. This dialog will display the current I/O mapping for the I/O modules in the local base, and if enabled and configured, the address mapping for the I/O modules accessed through the Ethernet I/O Master. This dialog optionally allows the I/O mapping for modules in the Local base and/ormodules in any of the Ethernet I/O Slave bases to be manually configured. Memory Configuration - The memory configuration dialog displays each currently configured memory block and Heap Item . This dialog also provides a facility to change the existing memory configuration and/or create additional memory blocks and heap items.

Topic: DMD0247


CPU Configuration

This page of the System Configuration dialog provides the selections necessary to configure the on-board hardware of the Do-more controller. This includes the following: Serial Port Mode - setting the operational mode of the on-board serial port. Watchdog Timer - setting the default value of the Software Watchdog Timer. Internal Ethernet Port - setting the TCP/IP Address and the Node ID, Name and Description, and a Secondary Ethernet Port number for use with Port Forwarding. TimeSync - enable / disable the TimeSync function and setting its operational mode.Ethernet I/O Master - enable / disable the Ethernet I/O Master's use of the on-board Ethernet port. Modbus/TCP Server's - enable / disable the built-in Modbus/TCP Server's use of the on-board Ethernet port.

EtherNet/IP Explicit Message Server Configuration - enable / disable the built-in EtherNet/IP Explicit Message Server's use of the on-board Ethernet port.

On-board Serial Port Mode

The Serial Port Mode configuration selects the operational mode for the on-board serial port of the Do-more controller. The selections are mutually exclusive, meaning that the on-board serial port can only operate in one of the following modes at any given time.

Do-more Programming

Select this option to have the serial port use the Do-more native protocol. This protocol is used when the port is used as a programming port for Do-more Designer programming software, or when the port is used with an HMI such as a C-More, Point of View, etc. that is configured to use "Automationdirect Do-more Serial" protocol.

K-Sequence Server

Select this option to have the port use K-Sequence protocol to allow third-party devices that communicate via K-Sequence protocol to read and write the DirectLOGIC protocol-specific memory in the Do-more CPU. K-Sequence is a proprietary protocol used by Automationdirect (Koyo) hardware.

K-Sequence Protocol Settings - configuration settings used when this Device responds to K-Sequence Client requests: Station - designates the ID of the K-Sequence Server Device, this can be any constant from 1 to 90.

Devices that connect with the K-Sequence protocol will only have access to the following blocks of memory (these blocks are numbered in octal):

Block Name Description Default RangeDLX Inputs DLX0 - DLX777DLY Outputs DLY0 - DLY777DLC Control Relays DLC0 - DLC777DLV V-Memory DLV0 - DLV3777 Note: The size of the memory blocks available to the K-Sequence driver can be changed in the Memory Configuration.

Modbus RTU Server (Slave)

Select this option to have the serial port use Modbus protocol to allow a third-party device that communicates via Modbus/RTU protocol to read and write the Modbus protocol-specific memory in the Do-more CPU.

Modbus Protocol Settings- configuration settings used when this Device responds to Modbus/RTU Client requests: Unit ID - designates the Unit ID of the Modbus/RTU Server Device, this can be any constant from 0 to 255.

Devices that connect with the Modbus/RTU protocol will only have access to the following blocks of memory (these blocks are numbered in decimal):

Block Name Description Default RangeMI Modbus Inputs MI0 - MI1023MC Modbus Control Relays MC0 - MC1023MIR Modbus Input Registers MIR0 - MIR2047MHR Modbus Holding Registers MHR0 - MHR2047

Note: The size of the memory blocks available to the Modbus/RTU driver can be changed in the Memory Configuration.

The Modbus/RTU Server (Slave) supports the following function codes:

Function Code Description1 Read Coils2 Read Discrete Inputs3 Read Holding Registers4 Read input Registers5 Write Single Coil6 Write Single Register7 Read Exception Status15 Write Multiple Coils16 Write Multiple Registers22 Mask Write Register

Modbus RTU Client (Master)

Select this option to allow the on-board serial port to be used by the Modbus Network Read (MRX) and Modbus Network Write (MWX) instructions. If this option is selected the MRX and MWX instructions can select @IntSerModbusClient as a target Device.

Modbus Protocol Settings - configuration settings used when this Device is used in a Modbus Network Read (MRX) or Modbus Network Write (MWX) instruction: Timeout - how many milliseconds should the instruction wait for the remote Modbus RTU Server to respond, this can be any constant from 0 to 32767. Retries - how many times should the instruction retry the communication with the remote Modbus RTU Server, this can be any constant from 0 to 255. Inter-packet Delay - the amount of time (in microseconds) that will be placed between the Modbus RTU packets as they are sent. This can be any be any constant between 0 and 65535. The inter-packet delay creates the required "dead time" on the wire that Modbus uses to frame a packet. The Modbus specification requires this value to be a minimum of 3.5 characterstimes (based on baud rate). If the value entered is smaller than the required time, the Modbus RTU Client will use the minimum required time instead of the value that is entered. If the value entered is larger than the required time, the value entered will be used.

Use this formula to calculate the inter-packet delay (in microseconds) based on baud rate:( 3.5 * (number of bits in a character / baud rate) ) * 1,000,000

For example: using a 10-bit character (1 start bit, 8 data bits, no parity bit, and 1 stop bit) at 19200 baud:( 3.5 ( 10 / 19200 ) ) * 1,000,000 = 1823 microseconds

General Purpose

Select this option to allow the on-board serial port to be used by the Stream In Data from Device (STREAMIN) and Stream Out Data to Device (STREAMOUT) instructions for sending and receiving ASCII data, or implementing custom protocols. Once configured this way the STREAMIN and STREAMOUT instructions will have the option of selecting the @IntSerial as a target Device.

Device Name - displays the name of the on-board serial port. To change the device's name use the Device Configuration dialog.

Device Settings

After selecting the desired operational mode, click the Device Settings ... button to change the on-board serial port's hardware configuration. Baud Rate - 115200, 57600, 38400, 19200, 9600, 4800, 2400, 1200, 300 Data Bits - 7, 8 Stop Bits - 1, 2 Parity - None, Odd, Even Transmit Control - designates when data will be transmitted

Unconditional - data will be transmitted as soon as it reaches the output buffer.

Wait for CTS - data will be transmitted when the CTS line is asserted.

Delayed 5ms, Delayed 50ms, Delayed 250ms, Delayed 500ms - after data reaches the output buffer, the RTS line will be asserted, and the transmitting of the data will be delayed by the selected number of milliseconds.

RTS Control - selects how the RTS line will operate

Follows Transmitter - the RTS line is under the control of the transmitter.

Manual - allows programmatic control of the RTS line through the structure member IntSerial.RTS.

Off - forces the RTS line to always be OFF.

On - forces the RTS line to always be ON.

Default Watchdog Timeout

The Software Watchdog Timeout specifies the maximum amount of time (in milliseconds) to allow for a single scan in the controller to complete. If this value is exceeded, the controller will immediately transition to STOP mode, an error message will appear in the System Information log, and the ERR LED (H2-DM1x) or STAT LED (T1H-DM1x) on the front of the controller will be ON. The Default Watchdog Timeout value is written to the system watchdog timer location $WatchdogTimeVal (DST23) on each STOP-mode to RUN-mode transition. This value can be changed at runtime by moving a new value into this location.

Default Timeout - specifies the number of milliseconds to use as the default watchdog timeout. This can be any constant value between 50 and 65535. Note: controllers also have a Hardware Watchdog Timer that is used to put the controller into a safe mode if the operating system ever stops running for more than 2 seconds. Follow this link for details on Configuring the Hardware Watchdog Timer.

Internal Ethernet Port

IP: - the currently configured TCP/IP Address. Net Mask: - the currently configured Subnet Mask. Configure - opens the Setup Node And IP Address Information dialog where this configuration can be changed:

Module ID - the ID can be any positive constant number.

Name - the Name can be any 255 character combination of alphanumeric and punctuation characters. The Module ID and Names entered must be unique on the network where the controller will be connected.

Description - the Description can be any 255 character combination of alphanumeric and punctuation characters.

The TCP/IP Address information entered in the following three fields must be valid for the network where the controller will be connected. For Do-more CPUs that do not have an on-board Ethernet port these fields are not used for configuration purposes, but the data in these fields can still be used for identification by storing values in their associated status memory locations:$IPAddress (DST18), $NetMask (DST19), $Gateway (DST20).

IP Address - can be any valid TCP/IP Address. The IP Address entered must be unique on the network where the PLC will be connected. Subnet Mask - can be any valid TCP/IP Subnet Mask. Gateway - can be any valid TCP/IP address of a network Gateway.

Secondary Ethernet Connection When Do-more Designer establishes a TCP/IP programming session with a Do-more controller it uses the TCP/IP address assigned to the controller and the port's fixed TCP/IP port number of 28784 (0x7070). If the situation arises, the Ethernet-equipped Do-more controllers can be configured to allow a Do-more Designer programming session to be established on an additionalTCP/IP port number. Enable Secondary Ethernet Connection - click to enable processing of packets from the following additional UDP Port Number

UDP Port Number - the additional UDP Port Number to begin processing packets for. This can be any decimal value between 5000 and 65535, except for 28784 (the port number already used by Do-more Designer). The hexadecimal equivalent of the specified port number is displayed to the right.

Port Forwarding A common situation where this is utilized is allowing remote computers (for example, computers on the Internet) to connect to a Do-more controller on a private, local-area network. The network administrator configures the Internet Gateway so that an external network address / port number request is routed to a specific network address / port number on the internal, private network(this is typically referred to as Port Forwarding ). External hosts must know the IP address of the Internet Gateway and the port number assigned to the target device on the internal network.

Internet GatewayTCP/IP Address

UDP Port Number specified in Do-more Designer Link

Do-more Controller's Assigned TCP/IP Address

Do-more Controller'sSecondary UDP Port Number

12.69.41.166 28,785 (0x7071) 192.168.20.1 28,785 (0x7071)12.69.41.166 28,786 (0x7072) 192.168.20.2 28,786 (0x7072)12.69.41.166 28,787 (0x7073) 192.168.20.3 28,787 (0x7073)12.69.41.166 28,788 (0x7074) 192.168.20.4 28,788 (0x7074)

Using the example configuration table for an Internet Gateway shown above, setting up Do-more Designer to access the Do-more controllers that are configured to use a Secondary Ethernet Connection requires the following steps:

1. Edit the DmDesigner.Ini file to enable the option that allows the Link to contain a user-specified IP port number that Do-more Designer will use to establish the session.

1. Begin by double-clicking the "DmDesigner.Ini" selection in the Applications section of the Launchpad. This will open DmDesigner.Ini in Windows Notepad.

2. Search for the ";UDPPortNumEnable=1" entry in the "[DevEther.Dll]" section.

3. Remove the leading ";".

4. Save the changes, and close Notepad.

2. Close and Restart Do-more Designer to re-read the new DmDesigner.Ini file.

3. Create a new link in Do-more Designer for the controller, the Link Editor must be used to manually specify all of the connection parameters - the Link Wizard will not work to create this link.

4. On the PLC tab select the Do-more Series and the CPU type from the Family and Type groups

5. On the Port tab select Devices-> Ethernet, Transport Protocol-> UDP/IP, then click the Advanced Settings button and make changes to the following two entries:

1. Timeout: the default value of 250 ms is typically not high enough for connecting over the Internet. Use the following steps to determine an initial Timeout value:

1. Open a DOS Command Prompt (Start --> Programs --> Accessories --> Command Prompt)

2. Ping the IP address of the Internet Gateway device, for example "ping 12.69.41.166"

3. Increase the Maximum timeout value by at least 50% and enter this number as the "Timeout" setting.

2. UDP Port Number: this is the same number configured as the UDP Port Number in the Secondary Ethernet Connection option

6. On the Protocol tab make sure the Protocols-> Do-more is selected.

7. Click Auto to test the current link parameters. There will be an audible beep if the link test is successful. If the link test is NOT successful, increase the Timeout value. and try again.

8. Repeat steps 3 through 7 to create new Do-more Designer Links for the remaining controllers.

TimeSync Configuration

The TimeSync Configuration option allows the Ethernet-equipped controllers on a network to automatically synchronize their internal real-time clocks. A typical network will have one controller configured as a TimeSync Server, one or more controllers configured as TimeSync Alternates, and the remaining controllers configured as TimeSync Clients. TimeSync packets are generated by the Do-more controller that is operating as a TimeSync Server. These packets are automatically sent by the TimeSync Server at the specified Update Interval and any time the real-time clock on the TimeSync Server is manually changed, either manually by Do-more Designer, or by a NETTIME (SNTP Client) instruction in the controller. TheTimeSync packet contains the current time from the TimeSync Server and the Update Interval so that Clients and Alternates will know when to expect the next TimeSync packet. Note: This feature uses TCP/IP broadcast packets on port number 123 to synchronize the real-time clocks of the Clients and Alternates, which means that only Do-more controllers within the TimeSync Server's Broadcast Domain can be synchronized

A Do-more CPU can be configured to operate in a TimeSync network in one of the following possible modes:

Disabled - the TimeSync feature in this CPU is disabled, the controller's real-time clock will not be synchronized by a TimeSync Server. This is the default configuration.

Client - this CPU will process TimeSync messages that are sent from a TimeSync Server. Each time a Client receives a TimeSync message it will update it's real-time clock with the real-time clock information in the TimeSync packet, set it's Status Bit $TimeSynced (ST23) ON which indicates that the clocks have been synchronized, and begin timing down from the UpdateInterval so the Client will know when to expect the next TimeSync packet. Server - this CPU will generate TimeSync messages for other controllers on the network that are configured as Clients and Alternates. At each Update Interval or any time the Server's real-time clock is changed, a TimeSync Server will broadcast three TimeSync messages at five second intervals - three messages are sent to make sure that the Clients and Alternatesreceive at least one of the messages. Alternate - this CPU will normally function as a TimeSync Client but will promote itself to a TimeSync Server if there are no TimeSync packets received within the Update Interval. An Alternate will begin the process of promoting itself to a Server 15 seconds after the Update interval has expired. Update Interval - is used in the following three ways:

By a TimeSync Client - once a Client has its time synchronized, it sets its own $TimeSynced (ST23) status bit and will begin using the Update Interval value as a countdown timer to know when to expect the next TimeSync packet. If that packet is not received before the Update Interval expires the controller will reset it's $TimeSynced status bit to indicate that thetime is no longer synchronized. By a TimeSync Alternate - once an Alternate has its time synchronized, it sets its own $TimeSynced (ST23) status bit and will begin using the Update Interval value as a countdown timer to know when to expect the next TimeSync packet. If the next packet is not received before the Update Interval expires the Alternate will begin the process of promoting itself to aTimeSync Server. By a TimeSync Server - designates the frequency that TimeSync packets are broadcast on the network.

Ethernet I/O Master

Do-more controllers that are equipped with an on-board Ethernet port can be configured to use that port to expand the I/O in a Do-more system. Any mix of up to 16 H2-EBC100, T1H-EBC100, and / or GS-EDRV100 devices can be used as Ethernet I/O Slaves. Note: The Ethernet I/O Master function uses TCP/IP protocol is used to communicate between the on-board port and the Slaves; which means that the on-board port and all of the I/O Slaves must have a proper TCP/IP network configuration. Do-more Designer can setup the TCP/IP configuration of the on-board Ethernet port AND the TCP/IP configuration of the EBC100 Slave devicesthrough a connection to the Do-more CPU's USB port, Serial port, or on-board Ethernet port.

As much as possible, the Ethernet I/O Master handles Ethernet slave I/O in the same way it handles the local I/O. When the controller is in PROGRAM (STOP) mode, the input module status is read from the slaves and updated in the image register, just like it is local input module status. When the controller is in RUN mode the input module status is read from the slaves andupdated in the image register, and output data from the image register is written to each of the slaves; again, just like it is for local input module and output modules. The I/O Mapping for the modules in the slaves begins where the I/O Mapping for modules in the local base ends. If any of the slave I/O units loses power, the Do-more controller will drop out of RUN mode, this is the same thing that happens if an I/O module is pulled from the local base while the controller is in RUN mode. The Hot-Swap feature in the T1H-EBC100 is NOT supported, if a module in the base with the T1H-EBC100 is removed or added while the Do-more controller is in RUN mode, the controller will drop out of RUN mode.

As stated before, the Ethernet I/O Master handles Ethernet slave I/O with the same degree of importance as it handles the local I/O. One way it does this is by trying to keep the Ethernet slave I/O in sync with the local I/O. This can result in a very high volume of network traffic between the Ethernet I/O Master and it's I/O Slaves. For this reason, take note of the followingrecommendations:

The Ethernet Master I/O network (the on-board port and all of the Ethernet I/O Slaves) should be on an isolated network. Functions like the Modbus/TCP Server and TimeSync that are exclusive to the on-board Ethernet port should be disabled if they are not being used. External devices that require Ethernet connectivity to the Do-more CPU - such as Do-more Designer, C-More panels, or other HMI devices - should be connected by adding an ECOM100 module to the system. Ethernet-capable instructions such as DLRX - DirectLOGIC Network Read, DLWX - DirectLOGIC Network Write etc. should be configured to use an ECOM100 module. Ethernet-capable instructions like Send Email (EMAIL) that can only target the on-board Ethernet port (not an ECOM100 module) should be used as sparingly as possible.

The goal of having the Ethernet I/O Master operating on an isolated network is allowing the Ethernet I/O update rate to be as fast and as stable as possible. The aforementioned recommendations will minimize the volume of network traffic and the number of different types of network packets that appear on the network, which will allow the Ethernet port to concentrate on processingread and write requests for the Ethernet I/O Master. While it is true that the on-board Ethernet port Do-more controller can be configured to perform all of the aforementioned functions concurrently with the Ethernet I/O Master, having it do so can result in instability and / or poor performance which can show up in one or more of the following ways:

Increased scan time. Scan times that vary from scan to scan. Slow update rates for all of the operations involved. Ethernet I/O Slaves can timeout which will cause the Do-more controller to fall out of RUN mode.

Enable Ethernet I/O Master - click this option to enable the Do-more controller's on-board Ethernet I/O Master function. Enabling this option will create the system structure named $ETH_IO_MASTER, and creates the Ethernet I/O Master entry in the I/O Configuration.

Note: This is the first of the two steps required to properly configure the Ethernet I/O Master. This selection only enables and disables the Ethernet I/O Master function, it does not select the I/O Slaves, nor does it configure those Slaves; that part of the process is done in the I/O Configuration section. This option was not available in the original release of the Do-more products. If this option is grayed out on the CPU Configuration page it indicates that the current Do-more controller firmware does not support this function. The following minimum firmware versions are required to support this function:

Do-more Designer v1.1.0 or greater Do-more firmware v1.1.0 or greater

Use the Check for Updates feature of Do-more Designer to download any required updates.

After the Ethernet I/O Master is configured and running, the Ethernet I/O Monitor can be used to display the "health" of the currently configured network of Ethernet I/O Slaves.

Supported I/O Slave Controllers

Ethernet I/O Slaves can be any combination of up to 16 H2-EBC100s or T1H-EBC100, and GS-EDRV100s. These devices require the following minimum firmware versions to be used as Ethernet I/O Slaves:

H2-EBC100 must be firmware v4.0.593 or greaterRefer to Chapter 4 of the Do-more H2 Series PLC Hardware User Manual for any module placement restrictions and power budget calculations. T1H-EBC100 must be firmware v4.0.1393 or greater.Because the Terminator I/O systems do not have fixed-size I/O bases, refer to Chapter 4 of the Do-more T1H Series PLC Hardware User Manual for any module placement restrictions, and for base arrangements using multiple power supplies to deal with power budget issues. GS-EDRV100 must be firmware version v5.0.229 or greater

If any of your devices need a firmware update to make them useful for Ethernet I/O Slaves, use the Live Update feature of NetEdit 3 to download the needed firmware files and apply the required updates to these devices. H2-EBCs, H4-EBCs, and GS-EDRVs can NOT be used as Ethernet I/O Slaves; the only way these legacy modules can be used in a Do-more system is if they are Remote I/O slaves for an H2-ERM module.

Supported I/O Modules

All of the discrete and analog I/O modules that are supported in the Do-more's local base can be used as I/O in the Slave bases. Additionally, the CTRIO and CTRIO2 modules are also supported as I/O in the Slave bases. Communication modules (SERIO, ERM, and ECOM) modules are NOT support in the remote bases.

Ethernet Master I/O Startup and Shutdown Sequences

Once the Ethernet Master I/O configuration has been set the Do-more controller will perform the following sequences depending on the starting condition. Again, it is important to understand that the Do-more controller places the same importance on the Ethernet Master I/O that it does on the Local I/O Master. The Ethernet I/O Master configuration must remain consistent for the Do-more controller to operate normally. Power ON Initialization Sequence is executed each time the Do-more controller is powered ON.

Query Network to make sure the currently configured Slaves are present on the network.

If all Slaves are present, each Slave is then queried to make sure that the I/O modules that are currently found in each Slave match the I/O modules that are in the stored configuration.

If all of the I/O modules match the current configuration the Ethernet Master will download the module configuration for all of the I/O modules that have one, for example, the CTRIO module.

The ERR LED (H2-DM1x) or STAT LED (T1H-DM1x) will be rapidly blinking RED while the module configurations are being downloaded.

If all of the module configurations are downloaded successfully the initialization process is complete.

A unique value (called the Link Monitor) is written to each I/O Slave. This unique Link Monitor value is included as part of each data packet between the Master and its I/O Slaves. This allows the Ethernet I/O Master to verify that each response packet is from one of its own I/O Slaves, and each I/O Slave can know that each data packet it receives isfrom its own Master. At this point the Ethernet I/O Master will begin normal updates for the I/O modules in all of its I/O Slaves as described in the section below.

If any of the Module configurations fail to download the Do-more controller will NOT go into RUN mode until the problem is resolved

The ERR LED (H2-DM1x) or STAT LED (T1H-DM1x) will be solid RED.

The system Bit $IOError (ST152) - "One or more I/O Master are reporting a problem with a module" will be ON. The error message can be seen on the System Status tab of the System Info utility.

The corresponding Bit for each Slave that is reporting a module error will be ON in the system structure member $EthIOMaster.SlaveError.

The appropriate structure member ($EthIOMaster.Slave0ErrorInfo - $EthIOMaster.Slave7ErrorInfo) will contain the number of the first slot that has an I/O module that failed to download its Module configuration.

If one or more of the I/O modules is different than what is in the configuration (this could be a module that is missing or a module that is a different type), the Do-more controller will NOT go into RUN mode until the problem is resolved.


The system Bit $IOError (ST152) - "One or more I/O Master are reporting a problem with a module" will be ON. The error message can be seen on the System Status tab of the System Info utility.

The corresponding Bit for each Slave that is reporting a module error will be ON in the system structure member $EthIOMaster.SlaveError.

The appropriate structure member ($EthIOMaster.Slave0ErrorInfo - $EthIOMaster.Slave7ErrorInfo) will contain the number of the first slot that has an I/O module that is different than the configuration.

If one or more of the configured Slaves is NOT present on the network, the Do-more controller will NOT go into RUN mode until the problems is resolved.


The system Bit $IOError (ST152) - "One or more I/O Master are reporting a problem with a module" will be ON.

The system Bit $EthMasterError (ST153) - "The Ethernet I/O Master is reporting an error, most likely a slave is offline" will be ON. These error messages can be seen on the System Status tab of the System Info utility.

The corresponding Bit for each Slave that is NOT present will be ON in the system structure member $EthIOMaster.SlaveErrors.

The Ethernet I/O Master will continue to query the network for missing Slaves at 10 second intervals. If one of the missing Slaves appears on the network, it will be initialized as described above.

After all of the missing Slaves are located the remainder of the initialization process will run, if that process completes successfully the ERR LED (H2-DM1x) or STAT LED (T1H-DM1x) will go OFF and the Do-more controller can then be manually put into to RUN mode.

PROGRAM mode - to- RUN mode Sequence is executed each time the Do-more controller transitions from PROGRAM mode to RUN mode. The process is very similar to the power-on sequence but there are a couple of notable exceptions that are described below. The resolution to any problems is the same as described in the power-on sequence.

Query Network to make sure the currently configured Slaves are still present on the network.

If all Slaves are present, each Slave is then queried to make sure that the I/O modules that are currently found in each Slave match the I/O modules that are in the stored configuration.

If all of the I/O modules match the stored configuration the Ethernet Master will initialize the image register locations with the Module configuration data for any that require it, for example: the Terminator I/O analog output modules, and the F2-8AD4DA-x modules. The Module configurations for all I/O modules are NOT downloaded again, only image registerlocations that need to be initialized with Module configuration data get processed.

After all of the initialization is complete the Ethernet I/O Master will begin normal updates for the I/O modules in its I/O Slaves as described in the section below.

If one or more of the I/O modules is different than what is in the configuration (this could be a module that is missing or a module that is a different type), the Do-more controller will NOT go into RUN mode until the problems is resolved.

If one or more of the configured Slaves is NOT present on the network, the Do-more controller will NOT go into RUN mode until the problems is resolved.

RUN mode -to- PROGRAM mode - is executed each time the Do-more controller transitions from RUN mode to PROGRAM mode

All of the discrete outputs are turned OFF and a value of 0 is written to all of the channels of the analog output modules.

Ethernet Master I/O Update Cycle

Once it has been enabled and its Slaves configured, the Do-more controller allows the Ethernet I/O Master to run during the Diagnostics and Communication slice of each scan. Each time the Ethernet I/O Master function is allowed to run it will update all of the configured I/O slaves.

When the Do-more controller is in PROGRAM mode, only status data from the input modules in each I/O Slave is read. That data is then used to update the Do-more's local copy in the image register. Any I/O modules that have structures instead of I/O, the structures will be read and the image register will be updated with that data. This allows both the input modules from EthernetI/O Slaves and input modules in the local base to continue to update in PROGRAM mode. When the Do-more controller is in RUN mode, data for each output module is sent to the appropriate I/O Slave, and for I/O modules that have structures instead of I/O, the I/O modules will be updated with data from their structures. The status data from the input modules in each I/O Slave is read. Any I/O modules that have structures instead of I/O, the structures will be read and theimage register will be updated with that data. The data from the input modules is then used to update the Do-more's local copy in the image register.

Modbus/TCP Server Configuration

The Modbus/TCP Server Configuration options are used to setup and optimize the Modbus/TCP Server device driver in controllers that have an on-board Ethernet port. The Modbus/TCP Server can support up to 16 concurrent sessions with Modbus/TCP Clients.

Enable Modbus/TCP Server - this option completely enables or completely disables the controller's Modbus/TCP Server device driver. If this option is unchecked, the Modbus/TCP Server device driver is disabled, meaning the controller will not respond to any Modbus/TCP Client requests. Maximum Concurrent Sessions - This value designates how many concurrent Modbus/TCP Server connections the device driver can handle. Establishing a Modbus/TCP Server session requires processing time which will inevitably impact the scan time. If there are more Modbus/TCP Clients requesting connections than there are concurrent sessions available, part of thisprocessing includes shutting down the oldest session so that a new session can be opened. The need to forcibly close sessions so that new ones can be opened can be minimized by setting this value to the maximum number of individual Modbus/TCP Clients that will be connecting to this controller at any given time. This can be any constant value between 1 and 16. Client Inactivity Timeout - specifies how much time (in seconds) to wait before closing the connection for a Modbus/TCP Client that has stopped communicating. This can be any constant value between 0 and 65535. TCP Port Number (502 is default) - designates the TCP port number the Modbus/TCP Server device driver will accept connections on. The default value of 502 is the industry standard, and rarely will this value need to be changed. This can be any constant value between 0 and 65535. Devices that connect with the Modbus/TCP protocol will only have access to the following blocks of memory (these blocks are numbered in decimal):

Block Name Description Default RangeMI Modbus Inputs MI0 - MI1023MC Modbus Control Relays MC0 - MC1023MIR Modbus Input Registers MIR0 - MIR2047MHR Modbus Holding Registers MHR0 - MHR2047

Note: The size of the memory blocks available to the Modbus/TCP driver can be changed in the Memory Configuration.

The Modbus/TCP Server (Slave) supports the following function codes:

Function Code Description1 Read Coils2 Read Discrete Inputs3 Read Holding Registers4 Read input Registers5 Write Single Coil6 Write Single Register7 Read Exception Status15 Write Multiple Coils16 Write Multiple Registers22 Mask Write Register

EtherNet/IP Explicit Message Server Configuration

The EtherNet/IP Server Configuration options are used to setup and optimize the EtherNet/IP Server in PLCs that have an on-board Ethernet port. The EtherNet/IP Server can support up to 16 concurrent sessions with Explicit Unconnected EtherNet/IP Client devices. Note: this feature requires Do-more Technology Version 1.4 or later. This means that you can enable the feature in the offline project, but you cannot download a project has this feature enabled to a Do-more PLC that is running a firmware version older than v1.4.

Enable EtherNet/IP Server - this option completely enables or completely disables the controller's EtherNet/IP Explicit Message Server device driver. If this option is unchecked, the EtherNet/IP Explicit Message Server device driver is disabled, meaning the controller will not respond to any EtherNet/IP Client requests. EtherNet/IP Settings - clicking this button will open a dialog to configure the EtherNet/IP Explicit Message Server's operating parameters.

Server Settings - selections that control how the EtherNet/IP Explicit Message Server handles client connections.

Maximum Concurrent Sessions (1 - 16) - This value designates how many concurrent EtherNet/IP Server connections the device driver can handle. Establishing an EtherNet/IP session requires processing time which will inevitably impact the scan time. If there are more EtherNet/IP Clients requesting connections than there are concurrent sessions available, part ofthis processing includes shutting down the oldest session so that a new session can be opened. The need to forcibly close sessions so that new ones can be opened can be minimized by setting this value to the maximum number of individual EtherNet/IP Clients that will be connecting to this PLC at any given time. This can be any constant value between 1 and 16. Client Inactivity Timeout (seconds) - specifies how much time (in seconds) to wait before closing the connection for a EtherNet/IP Client that has stopped communicating. This can be any constant value between 0 and 65535. TCP Port Number (44818 is default) - designates the TCP port number the EtherNet/IP Explicit Message Server will accept connections on. The default value of 44818 is the industry standard, and value will rarely need to be changed. This can be any constant value between 0 and 65535. Device Name - up to 32 characters that will be returned in requests for the Identity Class. Runtime status of the EtherNet/IP Server is accessed through the built-in structure $IntEIPServer which has the following members:

.ActiveSessions - (read-only) - the number of concurrent open connections to EtherNet/IP clients. .LastError - last error reported to an EtherNet/IP client.

.Errors - total number of errors returned to all EtherNet/IP clients. .Transactions - total number or completed client requests to EtherNet/IP clients.

Data Blocks - there can be up to 8 data block made available to EtherNet/IP Clients. This section specifies the how many of those 8 data blocks will be used and configures each of the blocks.

Enable - enables the data block for use by the EtherNet/IP Explicit Message Server. Access Control - specify external access ability

Enable Reads (Get Single Attribute - Service Code: 0x0E) - allow EtherNet/IP Clients to read from this data block using Get Single Attribute. Enable Writes (Set Single Attribute - Service Code: 0x10) - allow EtherNet/IP Clients to write to this data block using Set Single Attribute.

Do-more Mapped Memory - specifies the first location in a data block in the Do-more PLC memory that will be accessed when requests with this Class/Instance/Attribute are received.

Element Type - select the memory block to use from the drop-down list of available numeric memory blocks. Starting Element - specify the first element in the memory block to use. Element Count - the number of successive Elements in the Do-more memory block to use. The maximum total size on an EtherNet/IP request is 500 bytes, so the maximum number of elements per block will depend on the size of the individual elements. Refer to the chart below:

Element Type Maximum Number of This Type perData BlockBit 4000

Byte 500Word 250

DWord 125Real 125

Mapped Range - displays the currently selected range of Elements Size - displays the size of the selected Element range in Bytes

Explicit Messaging Assembly Instance - displays the Path (class / instance / attribute) of the data block being configured.

Class - the Class of all these data blocks is fixed at 0x04 (assembly class). Instance - each of the 8 blocks is assigned a unique Instance as shown below:

Block Number Instance ID0 101 (0x65)1 102 (0x66)2 103 (0x67)3 104 (0x68)4 105 (0x69)5 106 (0x6A)6 107 (0x6B)7 108 (0x6C)

Attribute - The Attribute of each of these data blocks is fixed at 0x03.

Configuration Notes - contains information pertinent to configuration selections being made.

OK - click OK to save the configuration changes that have been made and return to the main CPU Configuration. Cancel - click Cancel to discard any changes that have been made and return to the main CPU Configuration.

Supported Paths

The EtherNet/IP Explicit Message Server supports the following Paths: (Class / Instance / Attribute)

Class Instance Attribute Description0x01 - Identity 1 1 Vendor ID 2 Device Type 3 Product Code 4 Revision 6 Serial Number 7 Product Name

0x04 - Assembly 101 (0x65) 3 Data Block 1 102 (0x66) 3 Data Block 2 103 (0x67) 3 Data Block 3 104 (0x68) 3 Data Block 4 105 (0x69) 3 Data Block 5 106 (0x6A) 3 Data Block 6 107 (0x6B) 3 Data Block 7 108 (0x6C) 3 Data Block 8

0xF5 - TCP/IP 1 1 Status 3 Configuration Control 3 Product Code 4 Physical Link 5 Interface Configuration

0xF6 - EthernetLink 1 2 Interface Flags

3 Physical Address

Error Codes

The following charts show the error responses that will be returned by the EtherNet/IP Explicit Message Server: CIP Level Errors Error Code

Extended Error Info

Description

1 (0x01) None Invalid Command - returned for any command that is not recognized, and from RegisterSession if the session is already been registered. 100 (0x64) None Invalid Session - returned if session hasn't been opened or if the session handle is wrong. 101 (0x65) None Invalid Length - returned if the request length is wrong or longer than can be handled. 105 (0x69) None Invalid Revision - returned from RegisterSession if the requested version is not 1. EIP Level Errors Error Code

Extended Error Info

Description

4 (0x04) None Bad Path Segment - returned if path segment is improperly formed. 5 (0x05) None Path Unknown - returned for any unknown path (class/instance/attribute). 8 (0x08) None Unsupported Service - returned for any unsupported service. 19 (0x13) None Not Enough Data - returned when using SetAttributeSingle (16, 0x10) if the data length is too short. 21 (0x15) None Too Much Data - returned when using SetAttributeSingle (16, 0x10 if the data length is too long.

See Also:

System Configuration Overview CPU Configuration I/O Configuration Module Configuration Device Configuration I/O Mappings Memory Configuration

Topic: DMD0249


I/O Configuration

I/O Configuration:

The Top level of the I/O Configuration dialog displays a graphical view of the I/O Bases that are currently configured. The top-most graphic will always be the base that contains the Do-more controller and the I/O modules that are in the local base. Additional graphics for any configured Ethernet I/O Slaves will follow in the order they were added in the Ethernet I/O Master configuration.

I/O Masters

Expanding the Top Level will display the list of the I/O Masters that are currently configured. This list will contain one or more of the following: Local I/O Master which controls backplane communication with I/O modules in the local base (the same base where the Do-more controller is installed)

DL205 Local I/O Master - controls the I/O module in the local base with a H2-DM1 or H2-DM1E controller Terminator Local I/O Master - controls the I/O modules in the local base with a T1H-DM1 or T1H-DM1E controller

Ethernet I/O Master will be present if the Ethernet I/O Master function is enabled in the CPU Configuration of Do-more controller that has an on-board Ethernet port. The Ethernet I/O Master allows communication to the following slave devices: the H2-EBC100, T1H-EBC100, or GS-EDRV100. Note: H2-EBCs, H4-EBCs, and GS-EDRVs are NOT compatible devices for use as Ethernet I/O Slaves.

Local I/O Master

Selecting any Local I/O Master shows the following configuration parameter for the I/O Configuration Mode:

Auto - in this mode the controller will scan the backplane for I/O modules and automatically create an I/O configuration that matches the modules found. Manual - in this mode the user can change the I/O Configuration by adding modules and / or deleting modules. On PROGRAM-mode to RUN-mode transitions the controller will compare the manually adjusted I/O configuration to the installed I/O modules list, and these must match before the controller can go into Run mode.

Ethernet I/O Master

On Ethernet equipped Do-more controllers that have the Ethernet I/O Master function enabled, selecting the Ethernet I/O Master displays the following configuration options:

The Ethernet Master Address Configuration section displays the current TCP/IP network configuration of the on-board Ethernet port. The on-board Ethernet port must be configured with at least a valid TCP/IP address and Subnet Mask before it can be used by the Ethernet I/O Master function. Click the Set Node and IP Configuration... button to open a dialog to changethese entries.

Module ID - set the ID to any positive constant number Name - set the name to any 255 character combination of alphanumeric and punctuation characters Description - set the description to any 255 character combination of alphanumeric and punctuation characters IP Address - set the TCP/IP address of the on-board Ethernet port Subnet Mask - set the Subnet mask for the TCP/IP address of the on-board Ethernet port Gateway - set the TCP/IP address of the Network Gateway used to resolve TCP/IP address that are not on the same TCP/IP network as the on-board Ethernet port.

Setup Slave IP Config... - is used to configure the TCP/IP network parameters for the EBC100 and EDRV100 devices that will be used as Ethernet I/O Slaves. Each EBC100 and EDRV100 device must be configured with a valid TCP/IP address and Subnet Mask before it can be used as an I/O Slaves by the Ethernet I/O Master. When the Setup Slave IP Configuration dialog is opened it queries the network that the on-board Ethernet port is connected to for any compatible I/O Slaves. All devices that are found will be displayed in the list. Click the Query Devices button to manually perform the query again. After all of the Slaves have been configured, click the Close button to return to the mainconfiguration dialog.

If you need to changed the current configuration of one of the devices in the list, highlight the device in the list and click the Setup Selected Slave... button to open a dialog that will allow the TCP/IP Networking parameters to be changed for that device.

Name - set the name to any 255 character combination of alphanumeric and punctuation characters. IP Address - set the TCP/IP address of the device's Ethernet port. Subnet Mask - set the Subnet mask for the TCP/IP address of the device's Ethernet port. Gateway - set the TCP/IP address of the Network Gateway for the device.

Click OK to close the dialog and save any changes that were made. Click Cancel to close the dialog and discard any changes that were made. Click NetEdit to launch the NetEdit utility.

The next two buttons are used to add Ethernet I/O Slaves to the configuration, either automatically via an Ethernet Query operation that will look for compatible Ethernet I/O Slaves on the currently connected network, or manually where the programmer enters the required I/O Slave parameters.

Add Multiple Slaves via Query... - uses an Ethernet broadcast to locate compatible Ethernet devices that are on the same network as the on-board Ethernet port. After the query is complete this dialog will present a list of the compatible devices. Any mix of up to 16 compatible devices can be added as Ethernet I/O Slaves. Compatible Ethernet devices are:

H2-EBC100s with firmware v4.0.583 or greater. T1H-EBC100 with firmware v4.0.1390 or greater. GS-EDRV100 with firmware v5.0.226 or greater.

10Base-T versions of the above devices (H2-EBCs, H4-EBCs, and GS-EDRVs ) cannot be used as Ethernet I/O Slaves. Use the Live Update feature of NetEdit 3 to download firmware files and apply any required updates to these units.

Note: If there are no devices in the list make sure the Slave devices have the minimum firmware version that is required to work as an Ethernet I/O Slave, and make sure the TCP/IP address assigned to the on-board port and to the I/O Slaves place them all on the same IP network

Click Query Slaves to perform the broadcast query again. Click the box in the Add column to the left of each compatible Slave device to add to the configuration then click Add Selected to save the selections and close the dialog. Click Cancel to close the dialog and discard any selections that were made.

Manually Add Single Slave... - opens a dialog that allows a Slave to be added to the configuration that is not currently accessible with the Ethernet Query mentioned above. Note: this selection only adds the Slave device to the configuration, it does NOT add any I/O modules for that Slave; the I/O modules for each slot must also be added manually. Adding I/O modules is done by expanding the Ethernet I/O Master, selecting the Slave that was manually added, then right-click on each slot in the DL205 base and selecting the appropriateI/O module for that slot. This process is discussed in detail in the How to Manually Add an I/O Module section below.

The first five items uniquely identify the Slave on the network, and describe the communication requirements.

Name - set the name to any 255 character combination of alphanumeric and punctuation characters. Slave Type - specify the type of device from the list, either an H2-EBC100, a T1H-EBC100, or a GS-EDRV100. IP Address - set the TCP/IP address of the on-board Ethernet port. Poll Rate - specifies the frequency (in milliseconds) at which the Ethernet I/O Master will read and write to the I/O modules in this slave device. This can be any value between 0 and 32767. The default value of 0 means as "often as possible". Timeout - specifies the amount of time (in milliseconds) the Ethernet I/O Master will wait on a response from a read or write operation before it retries that operation. This can be any value between 25 and 32767. Retries - specifies the number of times the Ethernet I/O Master will retry a read or write operation before it cancels that operation and returns an error. This can be any value between 25 and 32767.

The next three options specify what actions the controller will take when it encounters an error from this I/O Slave (the possible I/O Slave errors are listed here):

CPU remains in RUN mode on slave error - what action to take if the controller is in RUN mode and this I/O Slave reports an error.

Checked - the Do-more controller will remain in RUN mode Unchecked (default) - the Do-more controller will drop in to PROGRAM mode

Slave must be online to enter RUN mode - if the previous selection is enabled, this selection specifies whether the controller can go to RUN mode based on whether this I/O Slave is present on the network or not

Checked (default) - the controller can only go to RUN mode if this I/O Slave is present on the network Unchecked - the controller can go to RUN mode even if this I/O Slave is NOT present on the network

On slave error, inputs will ... - specifies what action to take with the current image register data for the discrete and analog input modules in this I/O Slave if an error is reported

Be cleared - if selected, the image register data for all discrete inputs will set to OFF, and the image register data for analog inputs will be set to 0

Hold last state (default) - if selected, the image register data for all of the discrete inputs and all of the analog inputs will retain the last values that were received

After an I/O Slave has been added to the configuration, this button allows that configuration to be modified.

Edit Slave... - Select one of the Slave devices from the list of Ethernet Slaves and click the Edit Slave... button to edit that slave's current configuration.

The first five items uniquely identify the Slave on the network, and describe the communication requirements.

Name - set the name to any 255 character combination of alphanumeric and punctuation characters. Slave Type - specify the type of device from the list, either an H2-EBC100, a T1H-EBC100, or a GS-EDRV100. IP Address - set the TCP/IP address of the on-board Ethernet port. Poll Rate - specifies the frequency (in milliseconds) at which the Ethernet I/O Master will read and write to the I/O modules in this slave device. This can be any value between 0 and 32767. The default value of 0 means as "often as possible". Timeout - specifies the amount of time (in milliseconds) the Ethernet I/O Master will wait on a response from a read or write operation before it retries that operation. This can be any value between 25 and 32767. Retries - specifies the number of times the Ethernet I/O Master will retry a read or write operation before it cancels that operation and returns an error. This can be any value between 25 and 32767.

The next three options specify what actions the controller will take when it encounters an error from this I/O Slave (the possible I/O Slave errors are listed here):

CPU remains in RUN mode on slave error - what action to take if the controller is in RUN mode and this I/O Slave reports an error.

Checked - the Do-more controller will remain in RUN mode Unchecked (default) - the Do-more controller will drop in to PROGRAM mode

Slave must be online to enter RUN mode - if the previous selection is enabled, this selection specifies whether the controller can go to RUN mode based on whether this I/O Slave is present on the network or not

Checked (default) - the controller can only go to RUN mode if this I/O Slave is present on the network Unchecked - the controller can go to RUN mode even if this I/O Slave is NOT present on the network

On slave error, inputs will ... - specifies what action to take with the current image register data for the discrete and analog input modules in this I/O Slave if an error is reported

Be cleared - if selected, the image register data for all discrete inputs will set to OFF, and the image register data for analog inputs will be set to 0

Hold last state (default) - if selected, the image register data for all of the discrete inputs and all of the analog inputs will retain the last values that were received

Delete Slave... - Select one of the Slave devices from the list of Ethernet Slaves and click the Delete Slave... button to remove that Slave and all of its bases, the I/O modules, and information from the I/O Mapping from the current System Configuration.

Note: any module configurations for Modules in the bases will be Disconnected. Any instructions in the ladder logic program that reference I/O modules that were removed will remain associated with the disconnected module configurations. Disconnected module configurations can be associated with other I/O modules by reassigning the configuration to a compatiblemodule though the Assign Config function on the Module Configuration page.

Click OK to remove the selected Slave with all of its bases and I/O modules from the current configuration. Click Cancel to close the dialog and retain the selected Slave as part of the current configuration.

Rescan Slave's I/O... - Select one of the Slave devices from the list of Ethernet Slaves and click the Edit Slave... button to have the Slave refresh its list of I/O Modules. Note: the number, type and position of the I/O Modules in the base determines the address mapping of those I/O modules. If the Rescan operation finds additional I/O modules, or if the Rescan can no longer find I/O modules that were previously there, this will cause the address mapping to change for this Slave and for every Slave that follows it in the list of Ethernet Slaves.The default I/O address mapping information can be viewed and changed on the I/O Mappings page.

Move Up - Select one of the Slave devices from the list of Ethernet Slaves and click the Move Up button to reposition that Slave one position closer to the top of the list of Slaves. Move Down - Select one of the Slave devices from the list of Ethernet Slaves and click the Move Down button to reposition that Slave one position farther from the top of the list of Slaves. Note: the position of the Slaves in the list determines the address mapping of the I/O modules. Moving a Slave up or down in the list will cause the address mapping to change for every Slave that follows the one being moved. The default I/O address mapping information can be viewed and changed on the I/O Mappings page.

Base Configuration:

Expanding any of I/O Master trees will display a graphical view of each configured base and the I/O modules that are installed in the bases. Hovering the mouse cursor over the top section of an I/O module will display the part number of the module in that slot. Since the DL205 system shares part numbers among modules with the same I/O, instead of a single part number, you will typically see a list of all the modules with the I/O that match the I/O detected in that slot. Hovering the mouse cursor over the top section of an I/O module will display the part number of the module in that slot. Be aware that both the DL205 and Terminator I/O systems have modules that share part numbers. When you hover the mouse cursor over one of these I/O modules, instead of a single part number, you will see a list of all the modules with the I/O footprint thatmatches the I/O detected in that slot.

While the cursor is hovering over an I/O Module, the right-click menu will display the following selections:

Optional - marks the I/O module as optional, this is discussed in detail below. Delete Module - remove this I/O module from the base (only applicable if the I/O Master's Configuration Mode is set to "manual") Read Module Name - reads the part number of an I/O module Configure Module - opens the appropriate configuration dialog (only enabled for I/O modules that must be configured prior to use) View Manual - opens a submenu where the actual part number of the I/O module can be selected, this will then open the default web browser, which will then open a page on Automationdirect's web site that contains links to the User Manual. This requires a functioning connection to the Internet. View Specs - opens a submenu where the actual part number of the I/O module can be selected, this will then open the default web browser, which will then open a PDF file on Automationdirect's web site that displays the specification pages from the catalog. The Spec pages contain hardware requirements and wiring diagrams. This requires a functioning connection to theInternet and a PDF viewer.

Manual I/O Configuration Options:

Manual Base Scan - If the I/O Master's Configuration Mode is set to "manual", click the Scan Base button to read the current base contents into the manual I/O configuration. Base Size - since the DL205 system cannot automatically detect the size (number of slots) in a given base, this selection provides a way to change the graphical view so that it matches the actual size of the base. Select the 3 Slot, 4 Slot, 6 Slot, or 9 Slot option from the drop-down list - the list of optional base sizes will change based on the number of modules detected in thebase.

How to Delete the Configuration for an Installed Module

If the I/O Master's Configuration Mode is set to "manual", right-clicking on the installed module's graphic and select Delete Module from the pop-up menu will remove the current I/O module definition from the I/O configuration.

Marking a Module Configuration as Optional

If the I/O Master's Configuration Mode is set to "manual", right-clicking on the installed module's graphic and select Optional from the pop-up menu will mark this module as Optional meaning that it will not be considered when the manual I/O configuration is compared to the I/O configuration read from the system during a Program-mode to Run-mode transition. The I/O spaceconsumed by a module configured as optional is retained so that the I/O mapping does not change. Note: The instruction HWINFO - Get Hardware Information can be used to detect the presence of I/O modules marked as 'Optional' as a way to programmatically control optional execution schemes. Note: I/O modules that are configured to be optional will be marked with the word "*Optional*" in yellow on the graphical view.

How to Manually Add a Module in a DL205 Base

The DL205 system uses bases that have a fixed number of I/O slots. Right-clicking on an Empty Slot will display the Add Module dialog, which will then display a selection of I/O Module classes. Select the appropriate class, and follow on to display a list of the I/O modules in that class. Select the desired module by part number in that list and that module will be added to theI/O Configuration.

How to Manually Add a Module in a Terminator I/O Base

Unlike the DL205 system, a Terminator I/O system (using either a T1H-DM1/E CPU or a T1H-EBC100 as an Ethernet I/O Slave) does not have a backplane with a fixed number of slots where I/O modules are inserted. I/O modules are physically added to the system by connecting their base pieces together in the desired order. Do-more Designer allows I/O Modules to be manually added to the I/O configuration by inserting a new module at the desired location in the base. This is done by hovering the mouse cursor over the left or right edge of the I/O Module where the new module will be inserted. This action will draw an empty rectangle with a blue outline. Right-clicking on that rectangle will displaythe Insert Module dialog; follow on to display a selection of I/O Module classes; follow on from there to display a list of the I/O modules in that class. Select the desired module by part number in the resulting list and that module will be inserted at that point in the I/O Configuration.

How to Manually Change the GS Drive Type

Right-clicking on the GS Drive picture will display the Select Drive Type dialog, follow on to display a list of the valid GS Drive types. Select the desired GS Drive type from the list and the drive picture will change to reflect the drive selected type.

Handling Errors from I/O Error Modules at Runtime

Do-more Designer provides the I/O System View to monitor errors from I/O modules when it is connected to the Do-more controller. This section details what the Do-more controller provides to programmers that need to handle runtime reporting of errors from the I/O Masters, and the I/O modules that are under the control of any of the I/O Masters. There is a three tiered reportingscheme that reports I/O Master and I/O module errors at increasing levels of definition. This allows the programmer to handle these error condition at whatever level is deemed appropriate.

First Tier Reporting

The highest level reported is done through the System Bit $IOError (ST152), which is a single location that will be ON any time any of the I/O Masters in the system is reporting an error from one or more of its I/O Slaves or I/O modules. The Warning indicator will also be visible on the Status Bar, and the text "One or more IO masters are indicating a problem with a module -$IOError (ST152)" will be logged in the Warning Message section of the System Information dialog.

Second Tier Reporting

The middle tier of reporting is done through the System structure $IOMasterErrors (DST28), which is a DWord (32-bit) location that has one bit assigned to each I/O Master in the system. The individual bit for an I/O Master will be ON if any I/O module controlled by that I/O Master is reporting an error. Bit 0 is assigned to the Local I/O Master. Bit 1 is assigned to the Ethernet I/O Master. Additional Bits are assigned to additional I/O Masters in the order that they appear in the I/O Configuration list.

Third Tier Reporting

The third tier of error reporting is done through a System structure for each I/O Master.

The Local I/O Master can manage up to 128 slots of I/O modules; its structure has the following four DWord (32-bit) locations, with one bit assigned to each slot:

LocalIOMaster.Slot0_31 - reports errors for slot 0 through slot 31LocalIOMaster.Slot32_63 - reports errors for slot 32 through slot 63LocalIOMaster.Slot64_95 - reports errors for slot 64 through slot 95LocalIOMaster.Slot96_128 - reports errors for slot 96 through slot 128

The following Data View shows these elements reporting the following error conditions:

There is an I/O Error ($IOError is ON). The I/O Master that is reporting the error is the Local I/O Master (bit 0 of IOMasterErrors is ON). The I/O Module that is reporting the error is in slot 5 (bit 5 of LocalIOMaster.Slot0_31 is ON).

The Ethernet I/O Master can manage up to

do-more designer - john schember_a1

Documents